headers
Mike Tancsa | 2 Jan 2009 16:19

Re: Strange nanobsd issue

At 12:10 PM 7/4/2007, Mike Tancsa wrote:
>I ran into a rather strange problem I dont understand.  With my 
>nanobsd image, if I comment out
>
>hint.sio.0.flags="0x10"
>or
>hint.uart.0.flags="0x10"
>from /boot/device.hints
>
>I get the RAM disks mounted twice ?!
>
>eg.
>
># df
>Filesystem  1K-blocks  Used  Avail Capacity  Mounted on
>/dev/ad0s1a    245239 98076 127544    43%    /
>devfs               1     1      0   100%    /dev
>/dev/md0         4526  1784   2380    43%    /etc
>/dev/md1        27990   124  25628     0%    /var
>/dev/md2         4526  1788   2376    43%    /etc
>/dev/md3        27990   436  25316     2%    /var
>
>/boot.config is empty and /boot/loader.conf has
>
>hw.ata.ata_dma=0
>hw.ata.atapi_dma=0
>beastie_disable="YES"           # Turn the beastie boot menu on and off
>#comconsole_speed="19200"
>#console="nullconsole"
>autoboot_delay="4
(Continue reading)

Permalink | Reply | 3 comments |
headers
Paul Schenkeveld | 2 Jan 2009 22:56
Picon

Re: Strange nanobsd issue

On Fri, Jan 02, 2009 at 10:19:44AM -0500, Mike Tancsa wrote:
> At 12:10 PM 7/4/2007, Mike Tancsa wrote:
>> I ran into a rather strange problem I dont understand.  With my nanobsd 
>> image, if I comment out
>> 
>> hint.sio.0.flags="0x10"
>> or
>> hint.uart.0.flags="0x10"
>> from /boot/device.hints
>> 
>> I get the RAM disks mounted twice ?!
>> 
>> eg.
>> 
>> # df
>> Filesystem  1K-blocks  Used  Avail Capacity  Mounted on
>> /dev/ad0s1a    245239 98076 127544    43%    /
>> devfs               1     1      0   100%    /dev
>> /dev/md0         4526  1784   2380    43%    /etc
>> /dev/md1        27990   124  25628     0%    /var
>> /dev/md2         4526  1788   2376    43%    /etc
>> /dev/md3        27990   436  25316     2%    /var
>> 
>> /boot.config is empty and /boot/loader.conf has
>> 
>> hw.ata.ata_dma=0
>> hw.ata.atapi_dma=0
>> beastie_disable="YES"           # Turn the beastie boot menu on and off
>> #comconsole_speed="19200"
>> #console="nullconsole"
(Continue reading)

Permalink | Reply | 2 comments |
headers
Mike Tancsa | 3 Jan 2009 03:13

Re: Strange nanobsd issue

At 04:56 PM 1/2/2009, Paul Schenkeveld wrote:
> >>
> >> having nullconsole doesnt seem to matter any.  The device.hints
> >> modification seems to be the single thing that effects this behavior.
>
>Apparently something goes wrong during /etc/rc processing if there's
>no console at all.  Having a dcons_load="YES" in loader.conf creates
>a console even if there's no hardware attached to it.  I think that
>boot_multicons="YES" can even be omitted here.
>
>Could you please do one more test?  Add rc_debug="YES" to rc.conf
>and take boot_multicons="YES" and dcons_load="YES" out of loader.conf.
>This should give you two /etc and two /var mounts again.  Then post the
>output of dmesg -a as it should reveal when and probably also why these
>filesystems get mounted twice.

Hi,
         You are right about having just the dcons. Thats all that is 
needed.  In terms of dmesg -a, it doesnt haven anything when I dont 
have a console of some sort defined :(

Is there any other way to get rc to save its output elsewhere ?

         ---Mike
Permalink | Reply | 1 comment |
headers
FreeBSD bugmaster | 5 Jan 2009 12:06
Picon
Favicon

freebsd-embedded@...

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o kern/101228  embedded   [nanobsd] [patch] Two more entries for FlashDevice.sub
o misc/52256   embedded   [picobsd] picobsd build script does not read in user/s
o kern/42728   embedded   [picobsd] many problems in src/usr.sbin/ppp/*  after c
o misc/15876   embedded   [picobsd] PicoBSD message of the day problems

4 problems total.
Permalink | Reply | 1 comment |
headers
Bruce M. Simpson | 5 Jan 2009 14:58
Picon
Favicon

freebsd-embedded@...

FreeBSD bugmaster wrote:
> S Tracker      Resp.      Description
> --------------------------------------------------------------------------------
> o kern/101228  embedded   [nanobsd] [patch] Two more entries for FlashDevice.sub
>   

This should probably go in (phk?)

> o misc/52256   embedded   [picobsd] picobsd build script does not read in user/s
> o kern/42728   embedded   [picobsd] many problems in src/usr.sbin/ppp/*  after c
> o misc/15876   embedded   [picobsd] PicoBSD message of the day problems
>   

Can't we just parcel this stuff off into a separate category?

BugZilla would make that somewhat easier, of course I don't maintain 
GNATS so I can't speak for that either, though it seems to me we have 
been fast running into its operational limitations for years now.

PicoBSD is pretty old hat, IMHO. Of course I can't speak for everyone, I 
just don't really have any interest in maintaining PicoBSD now that 
floppies are pretty much obsolete, and the code to generate USB bootable 
NanoBSD images is in the 7.x train.

cheers
BMS
Permalink | Reply | 0 comments |
headers
Nick Hibma | 5 Jan 2009 12:32
Favicon
Gravatar

Re: Strange nanobsd issue

This sounds similar to the problem I described in the following PR.

Perhaps you could describe your work-around in it.

	http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/102515

Cheers,

Nick

> At 04:56 PM 1/2/2009, Paul Schenkeveld wrote:
> > >> having nullconsole doesnt seem to matter any.  The device.hints
> > >> modification seems to be the single thing that effects this
> > >> behavior.
> >
> >Apparently something goes wrong during /etc/rc processing if there's
> >no console at all.  Having a dcons_load="YES" in loader.conf creates
> >a console even if there's no hardware attached to it.  I think that
> >boot_multicons="YES" can even be omitted here.
> >
> >Could you please do one more test?  Add rc_debug="YES" to rc.conf
> >and take boot_multicons="YES" and dcons_load="YES" out of loader.conf.
> >This should give you two /etc and two /var mounts again.  Then post the
> >output of dmesg -a as it should reveal when and probably also why these
> >filesystems get mounted twice.
>
> Hi,
>          You are right about having just the dcons. Thats all that is
> needed.  In terms of dmesg -a, it doesnt haven anything when I dont
> have a console of some sort defined :(
(Continue reading)

Permalink | Reply | 0 comments |
headers
Markus Hitter | 12 Jan 2009 01:31
Picon

7.1 Release broke my box


Hello all,

it's me again :-)

Last Friday, after seeing ext2fs doesn't work with the 7.0 kernel, I  
decided to do yet another step and upgrade to 7.1 Release. The  
virtual machine for building tinybsd setup and ran flawlessly, but a  
tinybsd image built from it doesn't like networking any longer. The  
non-working box is a Geode-based Flepo Alpha, which uses the re  
network driver.

The tinybsd settings and set of files is exactly the same as the one  
which worked flawlessly in 7.0 Release. Yet, the symptoms are:

- DHCP doesn't catch the DHCP server's response any longer.

- Setting up networking manually helps to get this up.

- I can ssh out of the box, but not into the box.

- If I start telnetd on the box manually in the console, I can telnet  
into the box.

- lighttpd refuses to pick up his work.

- The odd is: Not a single error message in sight, connections just  
hang or time out.

- /var/log doesn't contain a hint.
(Continue reading)

Permalink | Reply | 6 comments |
headers
John Hein | 12 Jan 2009 03:51
Picon

Re: 7.1 Release broke my box

Markus Hitter wrote at 01:31 +0100 on Jan 12, 2009:
 > Last Friday, after seeing ext2fs doesn't work with the 7.0 kernel, I  
 > decided to do yet another step and upgrade to 7.1 Release. The  
 > virtual machine for building tinybsd setup and ran flawlessly, but a  
 > tinybsd image built from it doesn't like networking any longer. The  
 > non-working box is a Geode-based Flepo Alpha, which uses the re  
 > network driver.

What happens if you build a kernel with the 7.0 version of
sys/dev/re/if_re.c?  You may have to roll back sys/pci/if_rlreg.h too.

What happens to the link light while these things are happening?
Permalink | Reply | 3 comments |
headers
Markus Hitter | 12 Jan 2009 09:52
Picon

Re: 7.1 Release broke my box


Am 12.01.2009 um 03:51 schrieb John Hein:

> Markus Hitter wrote at 01:31 +0100 on Jan 12, 2009:
>> Last Friday, after seeing ext2fs doesn't work with the 7.0 kernel, I
>> decided to do yet another step and upgrade to 7.1 Release. The
>> virtual machine for building tinybsd setup and ran flawlessly, but a
>> tinybsd image built from it doesn't like networking any longer. The
>> non-working box is a Geode-based Flepo Alpha, which uses the re
>> network driver.
>
> What happens if you build a kernel with the 7.0 version of
> sys/dev/re/if_re.c?  You may have to roll back sys/pci/if_rlreg.h too.

The exactly same (had to roll back sys/pci/if_rl.c as well).

> What happens to the link light while these things are happening?

The green light stays on, the yellow one flickers, just like expected.

Obviously, the transmission gets interrupted at some higher level. Do  
I really have to bisect the entire kernel with it's 10,000 revisions  
now? *sigh*


MarKus

- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
(Continue reading)

Permalink | Reply | 2 comments |
headers
FreeBSD bugmaster | 12 Jan 2009 12:06
Picon
Favicon

freebsd-embedded@...

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o kern/101228  embedded   [nanobsd] [patch] Two more entries for FlashDevice.sub
o misc/52256   embedded   [picobsd] picobsd build script does not read in user/s
o kern/42728   embedded   [picobsd] many problems in src/usr.sbin/ppp/*  after c
o misc/15876   embedded   [picobsd] PicoBSD message of the day problems

4 problems total.
Permalink | Reply | 0 comments |

Gmane