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: Charles Manning
Date:  
To: balloon
Subject: Re: [Balloon] What happened to setup? --> not booting with initrd
On Friday 21 May 2010 04:00:28 Wookey wrote:
> +++ Charles Manning [2010-05-20 13:52 +1200]:
> > On Thursday 20 May 2010 13:39:31 Wookey wrote:
> > > 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)
> >
> > Yup, you're right.
> >
> > Both are almost exactly the same size:
> > 1569560 zImage
> > 1569556 zImageInitrd
> >
> > Looks like the gluing didn't work.
> >
> > With no initial fs it falls through to yaffs.
> >
> > If I delete zImageInitrd and redo make dist there are various errors but
> > the build keeps going until falling over because the cpld image is
> > missing. IIRC you said that's far enough to do TheRightThing (TM). Log
> > attached with file info at the bottom.
>
> aha. I know what it is: for 2.6.31 or later you need to uncomment from
> extra INITRAMFS options in Makefile.inc (or add them to Makefile.local):
>
> in Makefile.inc it says:
> # uncomment line below for 2.6.31 and later initramfs builds
> #INITRAMFSOPTS:=CONFIG_INITRAMFS_SOURCE=usr/initramfs.cpio
> CONFIG_INITRAMFS_COMPRESSION_BZIP2=y


Thanks. Thatgets me over one hurdle.
I now get a proper initramfs.

setup is there but the modprobes don't work. :-(.

/lib/modules/2.6.31-pxa270/modules.dep contains
kernel/drivers/usb/gadget/g_ether.ko: kernel/drivers/usb/gadget/pxa27x_udc.ko
kernel/drivers/usb/gadget/g_serial.ko: kernel/drivers/usb/gadget/pxa27x_udc.ko
kernel/drivers/usb/gadget/pxa27x_udc.ko:
kernel/drivers/usb/core/usbcore.ko:
kernel/drivers/usb/host/ohci-hcd.ko: kernel/drivers/usb/core/usbcore.ko
kernel/drivers/usb/storage/usb-storage.ko: kernel/drivers/usb/core/usbcore.ko
kernel/drivers/scsi/scsi_mod.ko
kernel/drivers/pcmcia/pxa2xx_balloon3.ko: kernel/drivers/pcmcia/pxa2xx_core.ko
kernel/drivers/pcmcia/pcmcia_core.ko
kernel/drivers/pcmcia/pxa2xx_core.ko: kernel/drivers/pcmcia/pcmcia_core.ko
kernel/drivers/pcmcia/pcmcia_core.ko:
....

The modes are there eg.
/lib/modules/2.6.31-pxa270/kernel/drivers/usb/core/usbcore.ko

Would modprobing work properly if these were full path names?



-- Charles