[pkg-fso-maint] linux-2.6 2.6.39-1gta021 call for testing

Gilles Filippini pini at debian.org
Sat Nov 5 01:26:19 UTC 2011

Timo Juhani Lindfors a écrit , Le 05/11/2011 00:46:
> Gilles Filippini <pini at debian.org> writes:
>>> My guess is this is due to the kernel change related to device names
>>> reported by linux-base during its configuration.
> Yeah but since linux-base does not pass device names to qi or linux it
> should not be able to cause any of this.

You're right. It was a wrong guess. Read below.

>>> mmcblk0: mmc1:b368 USD   7.51 GiB
>>> mmcblk0: detected capacity change from 0 to 8067743744
>>> mmcblk0: unknown partition table
>> What could be missing to recognize the partition table?
> Good question. My guess is that the SD card read is returning only
> zeroes for some reason.

It has eventually booted after I played with boot parameters in
/boot/append-GTA02. I've ended up with:
 rootwait glamo_mci.sd_max_clk=5000000 glamo_mci.sd_drive=3

And I removed the root=UUID part which didn't work after the successful
mmcblk0 initialization.

> Can you try booting with an initramfs? I tested that if I generate it with
> sudo mkinitramfs -o /boot/initrd-GTA02.bin
> it is able to boot using qi patches that enable initramfs support (I
> sent those to openmoko-kernel just today). If you use qi-bootmenu you
> probably can specify initramfs to the kexec call?

I don't know how to do that. Any pointers?



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-fso-maint/attachments/20111105/a9ba02fe/attachment-0001.pgp>

More information about the pkg-fso-maint mailing list