Re: [Balloon] What happened to setup? --> not booting with i…

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Wookey
Date:  
To: balloon
Subject: Re: [Balloon] What happened to setup? --> not booting with initrd
+++ Charles Manning [2010-05-20 09:57 +1200]:
> On Thursday 20 May 2010 05:47:37 Wookey wrote:
> > +++ Charles Manning [2010-05-19 09:21 +1200]:
> > > Building happens...
> >
> > Hooray! :-)
> >
> > > But I now have problems trying to load the fs off the USB stick because
> > > there is no setup.
> > > setup
> > >
> > > ooops not there
> >
> > Hmm, we've not seen that here.
> >
> > Which svn vintage are you using?
> >
> > r1062 built and tested nicely for me here for both base build (which
> > you've been testing, and -tcl-sl40 variant)
>
> svn info tells me I have r1062


OK that's good.

> I did a make
>
> then make dist


> After a "boot flash"
>
> balloon:~# ls /lib/modules/
> 2.6.29.1-pxa270
> balloon:~# uname -a
> Linux balloon 2.6.31-pxa270 #2 Mon May 17 17:55:32 NZST 2010 armv5tel
> GNU/Linux
> balloon:~# cat /lib/modules/2.6.29.1-pxa270/modules.dep
> /lib/modules/2.6.29.1-pxa270/kernel/sound/usb/snd-usb-lib.ko: /lib/modules/2.6.29.1-pxa270/kernel/drivers/usb/core/usbcore.ko /o
> /lib/modules/2.6.29.1-pxa270/kernel/sound/usb/snd-usb-audio.ko: /lib/modules/2.6.29.1-pxa270/kernel/sound/core/snd-pcm.ko /lib/o
> /lib/modules/2.6.29.1-pxa270/kernel/sound/soundcore.ko:
> ....
>
> but sniffing around in distro/binaries shows that both the initrd and rootfs
> have /lib/modules/2.6.31-pxa270
>
> the stale 2.6.29 stuff is coming from a yaffs partition


so mount says you have a yaffs root? That shouldn't happen after a
"boot flash"

> It was my understanding that doing
>
> utils/bbl --installer That loads up the kernel + initrd right?


Correct (into NOR).

The file that bbl uploads is defined in bblrc:
INSTALLER="kernel/zImageInitrd" or on the command line with
--bootloaderfile <filename>

One thing to clarify - despite the terminology/filenames throughout
the boot technically uses an initial ramfs as opposed to an initrd
on /dev/initrd (see Documentation/initrd.txt)

> followed by
>
> boot flash That boots the kernel with initrd right?


Correct

> would boot the initrd and deliver up the fresh 2.6.31 goods but that does not
> seem to be happening. Closer inspection indicates that the bootloader starts
> off thinking about initrd, then changes its mind.
>
> .....
> root_filesystem_name=initrd
> Grabbed linuxargs, argc = 00000001
> Using mach_type 00000405
> setting boot parameters to
> nointrd root=/dev/mtdblock1 init=/sbin/init /quiet console=ttyS2,115200


That's a red herring - the bootloader has that line stored and always
prints that out. Even when booting into initrd.

The clue for being in initrd world is:
"Welcome to the Balloon3 installer/bootstrap/buildroot environment"
and mount after logging in says:
rootfs on / type rootfs (rw)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /tmp type tmpfs (rw)

>
> Can someone please explain what I should do using words of one syllable or
> less?


Well you really do seem to be getting a yaffs rootfs even when doing
'boot flash'. I'm not sure how that's possible.

Here's my 'boot flash' log to compare with:
The only significant difference, seems to be that yours mounts a
yaffs rootfs at the end.

We do have different kernel options but in my experience that stuff
doesn't matter much. board=2.05 is just ancient cruft from balloon2
vintage. and specifying 'root=/dev/mtdblock1' is normally just
ignored when doing an initramfs boot.

I really don't know why you are getting this behaviour. The kernel
option do tell it to do what you are getting (root=/dev/mtdblock1)
but that's just not what normally happens.

You could mess with the boot parameters. You can set the current boot
params without saving them and making them permanent:
set linuxargs=noinitrd root=/dev/mtdblock1 init=/sbin/init console=ttyS2,115200

does it behave if you change that to
set linuxargs=init=/sbin/init console=ttyS2,115200 ?
then do 'boot flash'

"params show" lists current settings
"params save" makes them permanent
"help" is informative.

Actually - maybe your zImageInitrd doesn't actually _have_ an
initrd in it so it is falling back to the yaffs root? It should be
about 3.2 in size? (with zImage being 1.6MB)

I guess this explains why you didn't have 'setup' present either.
You are looking at the yaffs rootfs, not the initramfs.

boot> boot flash

booting kernel from partition >kernel<
kernel partition base 50200000
kernel_magic=E1A00000
kernel_region_words[9]=016F2818
Linux ELF flash_imgstart=50200000 size=00400000 dest=A0000000 offset=00008000
MMU Control=00000079
MMU PIDVAM=00000000
copying Linux kernel ... done
A0008000: E1A00000
A0008004: E1A00000
A0008008: E1A00000
A000800C: E1A00000
A0008010: E1A00000
A0008014: E1A00000
A0008018: E1A00000
A000801C: E1A00000
A0008020: EA000002
A0008024: 016F2818
root_filesystem_name=initrd
Grabbed linuxargs, argc = 00000001
Using mach_type 00000405
setting boot parameters to
nointrd root=/dev/mtdblock1 init=/sbin/init
/quiet console=ttyS2,115200
Making core tag at A0000100
Making cmdline tag at A0000114
Making mem32 tag at A00001CC
Making mem32 tag at A00001DC
Making mem32 tag at A00001EC
command line is: nointrd root=/dev/mtdblock1 init=/sbin/init /quiet console=ttyS2,115200 rootfstype=yaffs2
cpufreq=59000-206400 machine_id=0000000000000000 board=2.05 build=E1 lcd=480x144x4
linuxEntryPoint=A0008000
Booting Linux image
Uncompressing
Linux...............................................................................................
Linux version 2.6.29.1-pxa270 (wookey@triumph) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #2 Sun0
CPU: XScale-PXA270 [69054114] revision 4 (ARMv5TE), cr=0000397f
CPU: VIVT data cache, VIVT instruction cache
Machine: Balloon3
Memory policy: ECC disabled, Data cache writeback
Run Mode clock: 208.00MHz (*16)
Turbo Mode clock: 520.00MHz (*2.5, active)
Memory clock: 104.00MHz (/2)
System bus clock: 104.00MHz
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 64768
Kernel command line: nointrd
root=/dev/mtdblock1 init=/sbin/init /quiet console=ttyS2,115200 rootfstype=yaffs2 c
PID hash table entries: 1024 (order: 10, 4096 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 128MB 128MB = 256MB total
Memory: 254848KB available (2660K code, 196K data, 1844K init)
Calibrating delay loop... 519.37 BogoMIPS (lpj=2596864)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 884 bytes
NET: Registered protocol family 16
Initialising Balloon3
bio: create slab <bio-0> at 0
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
NET: Registered protocol family 1
PXA CPU 27x max frequency not defined
(pxa27x_maxfreq), assuming pxa271 with 416000kHz maxfreq
PXA CPU frequency change support initialized
NetWinder Floating Point Emulator V0.97 (double precision)
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
yaffs May 16 2010 02:34:11 Installing.
msgmni has been set to 498
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Console: switching to colour frame buffer device 60x40
pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 22) is a FFUART
pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 21) is a BTUART
pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 20) is a STUART
console [ttyS2] enabled
NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit)
4 NAND chips detected
Scanning device for bad blocks
Bad eraseblock 288 at 0x000002400000
Bad eraseblock 839 at 0x0000068e0000
Bad eraseblock 1397 at 0x00000aea0000
Bad eraseblock 6995 at 0x000036a60000
Bad eraseblock 6996 at 0x000036a80000
Bad eraseblock 7136 at 0x000037c00000
Bad eraseblock 7273 at 0x000038d20000
cmdlinepart partition parsing not available
Creating 2 MTD partitions on "balloon3-nand":
0x000000000000-0x000000400000 : "Boot"
0x000000400000-0x000040000000 : "Root fs"
mice: PS/2 mouse device common for all mice
pxa-rtc pxa-rtc: rtc core: registered pxa-rtc as rtc0
cpuidle: using governor ladder
Registered led device: balloon3:green:idle
Registered led device: balloon3:green:nand
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
XScale iWMMXt coprocessor detected.
pxa-rtc pxa-rtc: setting system clock to 2000-01-01 00:00:09 UTC (946684809)
Freeing init memory: 1844K
mount: mounting proc on /proc failed
mount: mounting sysfs on /sys failed
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
pxa27x-ohci pxa27x-ohci: PXA27x OHCI
pxa27x-ohci pxa27x-ohci: new USB bus
registered, assigned bus number 1
pxa27x-ohci pxa27x-ohci: irq 3, io mem 0x4c000000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
usbcore: registered new interface driver asix
usbcore: registered new interface driver dm9601
pegasus: v0.6.14 (2006/09/27),
Pegasus/Pegasus II USB Ethernet driver
usbcore: registered new interface driver pegasus
usbcore: registered new interface driver libusual
SCSI subsystem initialized
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
Driver 'sd' needs updating - please use bus_type methods
modprobe: module led_class not found
modprobe: failed to load module led_class
modprobe: module pxa2xx_cs not found
modprobe: failed to load module pxa2xx_cs
modprobe: module rtc-sa1100 not found
modprobe: failed to load module rtc-sa1100
pxa27x_udc: version 2008-04-18
g_ether gadget: using random self ethernet address
g_ether gadget: using random host ethernet address
usb0: MAC fa:41:04:c7:44:7d
usb0: HOST MAC ba:80:04:93:91:8c
g_ether gadget: Ethernet Gadget, version:
Memorial Day 2008
g_ether gadget: g_ether ready
pxa27x-udc pxa27x-udc: UDC connecting
I2C: i2c-0: PXA I2C adapter
Initializing random number generator... done.
Starting network...
ip: RTNETLINK answers: File exists
Generating RSA Key...
Will output 1024 bit rsa secret key to '/etc/dropbear/dropbear_rsa_host_key'
Generating key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAAAgwCT9oCfgtQy0aVmSFn0BZcNk+TNMd0qRCyzpQVEiLbwrJiSh3f0Y+AH7Y2LJ86jqUKvEyT58Fe9N@
Fingerprint: md5 ae:3b:a3:58:6a:4d:39:80:75:7d:4b:c7:3c:d7:e7:46
Generating DSS Key...
Will output 1024 bit dss secret key to '/etc/dropbear/dropbear_dss_host_key'
Generating key, this may take a while...
Public key portion is:
ssh-dss AAAAB3NzaC1kc3MAAACBAM0q8pFFM9VmW5NTDswoP5R5PzGUSoyd3dbKko/KIsey30T92Jks/42brEzEYPn5k/rOO9lsz6c15p+wDb+wT@
Fingerprint: md5
7b:7d:2c:df:15:90:fc:a0:02:b8:e5:ab:01:d1:d9:0d
Starting dropbear sshd: OK



Welcome to the Balloon3 installer/bootstrap/buildroot environment.

login:


-------------------
Charles's log


> boot> boot flash
> booting kernel from partition >kernel<
> kernel partition base 50200000
> kernel_magic=E1A00000
> kernel_region_words[9]=016F2818
> Linux ELF flash_imgstart=50200000 size=00400000 dest=A0000000 offset=00008000
> MMU Control=00000079
> MMU PIDVAM=00000000
> copying Linux kernel ... done
> A0008000: E1A00000
> A0008004: E1A00000
> A0008008: E1A00000
> A000800C: E1A00000
> A0008010: E1A00000
> A0008014: E1A00000
> A0008018: E1A00000
> A000801C: E1A00000
> A0008020: EA000002
> A0008024: 016F2818
> root_filesystem_name=initrd
> Grabbed linuxargs, argc = 00000001
> Using mach_type 00000405
> setting boot parameters to
> nointrd root=/dev/mtdblock1 init=/sbin/init /quiet console=ttyS2,115200
> Making core tag at A0000100
> Making cmdline tag at A0000114
> Making mem32 tag at A00001CC
> Making mem32 tag at A00001DC
> command line is: nointrd root=/dev/mtdblock1 init=/sbin/init /quiet
> console=ttyS2,115200 rootfstype=yaffs
> linuxEntryPoint=A0008000
> Booting Linux image
> Uncompressing
> Linux........................................................................................
> Linux version 2.6.31-pxa270 (charles@qcore) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #2 Mon May 17 17:55:320
> CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=0000397f
> CPU: VIVT data cache, VIVT instruction cache
> Machine: Balloon3
> Memory policy: ECC disabled, Data cache writeback
> Run Mode clock: 208.00MHz (*16)
> Turbo Mode clock: 520.00MHz (*2.5, active)
> Memory clock: 104.00MHz (/2)
> System bus clock: 104.00MHz
> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 64768
> Kernel command line: nointrd root=/dev/mtdblock1 init=/sbin/init /quiet console=ttyS2,115200 rootfstype=y
> PID hash table entries: 1024 (order: 10, 4096 bytes)
> Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
> Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
> Memory: 128MB 128MB = 256MB total
> Memory: 256384KB available (2748K code, 203K data, 112K init, 0K highmem)
> NR_IRQS:208
> Console: colour dummy device 80x30
> Calibrating delay loop... 519.37 BogoMIPS (lpj=2596864)
> Mount-cache hash table entries: 512
> CPU: Testing write buffer coherency: ok
> NET: Registered protocol family 16
> Initialising Balloon3
> bio: create slab <bio-0> at 0
> Switched to NOHz mode on CPU #0
> NET: Registered protocol family 2
> IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
> TCP established hash table entries: 8192 (order: 4, 65536 bytes)
> TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
> TCP: Hash tables configured (established 8192 bind 8192)
> TCP reno registered
> NET: Registered protocol family 1
> PXA CPU 27x max frequency not defined (pxa27x_maxfreq), assuming pxa271 with 416000kHz maxfreq
> PXA CPU frequency change support initialized
> NetWinder Floating Point Emulator V0.97 (double precision)
> VFS: Disk quotas dquot_6.5.2
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> yaffs May 17 2010 16:33:00 Installing.
> msgmni has been set to 501
> io scheduler noop registered
> io scheduler anticipatory registered (default)
> io scheduler deadline registered
> io scheduler cfq registered
> Console: switching to colour frame buffer device 60x40
> Samosa device registration
> Samosa bus registration
> Samosa services initialised.
> VHDL logic version (memread):00004F15
> pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 22) is a FFUART
> pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 21) is a BTUART
> pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 20) is a STUART
> console [ttyS2] enabled
> NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V
> 8-bit)
> 4 NAND chips detected
> Scanning device for bad blocks
> Bad eraseblock 45 at 0x0000005a0000
> Bad eraseblock 3091 at 0x000018260000
> Bad eraseblock 4926 at 0x0000267c0000
> Bad eraseblock 5598 at 0x00002bbc0000
> Bad eraseblock 6734 at 0x0000349c0000
> cmdlinepart partition parsing not available
> Creating 2 MTD partitions on "balloon3-nand":
> 0x000000000000-0x000000400000 : "Boot"
> 0x000000400000-0x000040000000 : "Root fs"
> mice: PS/2 mouse device common for all mice
> pxa-rtc pxa-rtc: rtc core: registered pxa-rtc as rtc0
> cpuidle: using governor ladder
> cpuidle: using governor menu
> Registered led device: balloon3:green:idle
> Registered led device: balloon3:green:nand
> TCP cubic registered
> NET: Registered protocol family 17
> RPC: Registered udp transport module.
> RPC: Registered tcp transport module.
> XScale iWMMXt coprocessor detected.
> pxa-rtc pxa-rtc: setting system clock to 2000-01-01 00:00:08 UTC (946684808)
> yaffs: dev is 32505857 name is "mtdblock1"
> yaffs: passed flags ""
> yaffs: Attempting MTD mount on 31.1, "mtdblock1"
> block 14 is bad
> block 3060 is bad
> block 4895 is bad
> block 5567 is bad
> block 6703 is bad
> yaffs_read_super: isCheckpointed 0
> VFS: Mounted root (yaffs2 filesystem) on device 31:1.
> Freeing init memory: 112K
> modprobe: FATAL: Could not load /lib/modules/2.6.31-pxa270/modules.dep: No
> such file or directory
>
> INIT: version 2.86 booting
> .udev/ already exists on the static /dev! (warning).
> Starting the hotplug events dispatcher: udevd.
> Synthesizing the initial hotplug events...done.
> Waiting for /dev to be fully populated...done.
> Setting the system clock.
> Activating swap...done.
> save exit: isCheckpointed 1
> Checking root file system...fsck 1.41.3 (12-Oct-2008)
> fsck: fsck.auto: not found
> fsck: Error 2 while executing fsck.auto for /lib/init/rw/rootdev
> done.
> Setting the system clock.
> Cleaning up ifupdown....
> Loading kernel modules...FATAL: Could not
> load /lib/modules/2.6.31-pxa270/modules.dep: No such file or diry
> Checking file systems...fsck 1.41.3 (12-Oct-2008)
> done.
> Setting kernel variables (/etc/sysctl.conf)...done.
> Mounting local filesystems...mount: /sys already mounted or /sys busy
> mount: according to mtab, sysfs is already mounted on /sys
> failed.
> Activating swapfile swap...done.
> Setting up networking....
> Configuring network interfaces...Internet Systems Consortium DHCP Client
> V3.1.1
> Copyright 2004-2008 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/sw/dhcp/
>
> modprobe: FATAL: Could not load /lib/modules/2.6.31-pxa270/modules.dep: No
> such file or directory
>
> modprobe: FATAL: Could not load /lib/modules/2.6.31-pxa270/modules.dep: No
> such file or directory
>
> SIOCSIFADDR: No such device
> modprobe: FATAL: Could not load /lib/modules/2.6.31-pxa270/modules.dep: No
> such file or directory
>
> SIOCSIFADDR: No such device
> modprobe: FATAL: Could not load /lib/modules/2.6.31-pxa270/modules.dep: No
> such file or directory
>
> eth0: ERROR while getting interface flags: No such device
> modprobe: FATAL: Could not load /lib/modules/2.6.31-pxa270/modules.dep: No
> such file or directory
>
> eth0: ERROR while getting interface flags: No such device
> modprobe: FATAL: Could not load /lib/modules/2.6.31-pxa270/modules.dep: No
> such file or directory
>
> Bind socket to interface: No such device
> Failed to bring up eth0.
> Internet Systems Consortium DHCP Client V3.1.1
> Copyright 2004-2008 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/sw/dhcp/
>
> modprobe: FATAL: Could not load /lib/modules/2.6.31-pxa270/modules.dep: No
> such file or directory
>
> modprobe: FATAL: Could not load /lib/modules/2.6.31-pxa270/modules.dep: No
> such file or directory
>
> SIOCSIFADDR: No such device
> modprobe: FATAL: Could not load /lib/modules/2.6.31-pxa270/modules.dep: No
> such file or directory
>
> SIOCSIFADDR: No such device
> modprobe: FATAL: Could not load /lib/modules/2.6.31-pxa270/modules.dep: No
> such file or directory
>
> eth1: ERROR while getting interface flags: No such device
> modprobe: FATAL: Could not load /lib/modules/2.6.31-pxa270/modules.dep: No
> such file or directory
>
> eth1: ERROR while getting interface flags: No such device
> modprobe: FATAL: Could not load /lib/modules/2.6.31-pxa270/modules.dep: No
> such file or directory
>
> Bind socket to interface: No such device
> Failed to bring up eth1.
> done.
> INIT: Entering runlevel: 2
>
> Debian GNU/Linux 5.0 balloon ttyS2
>
> balloon login:
>

Wookey
--
Principal hats: iEndian - Balloonboard - Toby Churchill - Emdebian
http://wookware.org/