Hi there,
I'm trying to boot Fedora 17 from an SD card on my TrimSlice. Unfortunately the it hangs at this part of boot process:
[ 4.547850] Waiting for root device LABEL=rootfs... [ 4.926999] mmc1: new high speed SDHC card at address 0002 [ 4.934075] mmcblk0: mmc1:0002 3.74 GiB [ 4.942731] mmcblk0: p1 p2
The full log is available at http://fpaste.org/2KV6/
Interestingly enough, it doesn't quite hang, as it can notice that I eject or re-insert the SD card:
[ 13.065893] mmc1: card 0002 removed [ 15.485660] mmc1: new high speed SDHC card at address 0002 [ 15.492582] mmcblk0: mmc1:0002 3.74 GiB [ 15.501062] mmcblk0: p1 p2
Anyone has seen this sort of error? Any ideas how to resolve it?
I tried a 4G card and a 32G card, and two different SD readers to make sure that it's not hardware fault on the producer end. It still could be a hardware fault in my TrimSlice though, so I'm wondering, what would it make to adjust the boot scripts to read from the side slot instead. Anyone tried that?
Thank you, PM
On Fri, Sep 21, 2012 at 11:30 AM, Brendan Conoboy blc@redhat.com wrote:
On 09/21/2012 09:23 AM, Petr Machata wrote:
Anyone has seen this sort of error? Any ideas how to resolve it?
Are you using the latest uboot? We've had trouble with F17 GA on the recently released uboot.
From his fpaste:
U-Boot 1.01 (Jul 11 2011 - 17:59:32)
For some reason I cannot find that version on the website: http://www.trimslice.com/wiki/index.php/Trim-Slice_Firmware_Updater
Perhaps I'm mistaken here, hopefully.... that 2011 firmware looks unique.
My suggestion is to install "v2010.09-1.03" from the above link.
Brendan Conoboy blc@redhat.com writes:
On 09/21/2012 09:23 AM, Petr Machata wrote:
Anyone has seen this sort of error? Any ideas how to resolve it?
Are you using the latest uboot? We've had trouble with F17 GA on the recently released uboot.
I don't think I meddled with this at all. The machine is at least a year old, so the firmware is more likely to be obsolete than too recent.
PM
On 09/21/2012 09:42 AM, Petr Machata wrote:
I don't think I meddled with this at all. The machine is at least a year old, so the firmware is more likely to be obsolete than too recent.
There have been reports that changing the bootargs root= to directly identify the root device instead of using a volume label works with the newer uboot. Perhaps you'll get a similar benefit? Something like this:
setenv bootargs console=ttyS0,115200n8 ro root=/dev/mmcblk0p2 rootwait ext2load mmc 0:1 4080000 uImage-tegra ext2load mmc 0:1 8400000 uInitrd-tegra bootm 4080000 8400000
Brendan Conoboy blc@redhat.com writes:
On 09/21/2012 09:42 AM, Petr Machata wrote:
I don't think I meddled with this at all. The machine is at least a year old, so the firmware is more likely to be obsolete than too recent.
There have been reports that changing the bootargs root= to directly identify the root device instead of using a volume label works with the newer uboot. Perhaps you'll get a similar benefit? Something like this:
setenv bootargs console=ttyS0,115200n8 ro root=/dev/mmcblk0p2 rootwait ext2load mmc 0:1 4080000 uImage-tegra ext2load mmc 0:1 8400000 uInitrd-tegra bootm 4080000 8400000
I upgraded to v2010.09-1.03 and it all seems to work now.
Thanks everyone, PM