Has anyone else seen issues booting on the Trimslice?
Basically it boots through but seems unable to fine the rootfs so just hangs.
Peter
On Mon, Jan 21, 2013 at 5:39 AM, Peter Robinson pbrobinson@gmail.comwrote:
Has anyone else seen issues booting on the Trimslice?
Basically it boots through but seems unable to fine the rootfs so just hangs.
Peter
Yes, the first thing to try is changing to boot.scr to have root=/dev/sda3 or root=/dev/mmcblkop3, or root=LABEL=rootfs
On 21 Jan 2013 18:47, "Jon" jdisnard@gmail.com wrote:
On Mon, Jan 21, 2013 at 5:39 AM, Peter Robinson pbrobinson@gmail.com
wrote:
Has anyone else seen issues booting on the Trimslice?
Basically it boots through but seems unable to fine the rootfs so just
hangs.
Peter
Yes, the first thing to try is changing to boot.scr to have
root=/dev/sda3 or root=/dev/mmcblkop3, or root=LABEL=rootfs
My point is this is suppose to just work. I know I can specify labels or partitions instead of uuid but for our supported platforms I shouldn't need to it needs to "just work". This is a blocker, oh and beagle is not better. 2/2 fail!
On Mon, Jan 21, 2013 at 4:19 PM, Peter Robinson pbrobinson@gmail.comwrote:
On 21 Jan 2013 18:47, "Jon" jdisnard@gmail.com wrote:
On Mon, Jan 21, 2013 at 5:39 AM, Peter Robinson pbrobinson@gmail.com
wrote:
Has anyone else seen issues booting on the Trimslice?
Basically it boots through but seems unable to fine the rootfs so just
hangs.
Peter
Yes, the first thing to try is changing to boot.scr to have
root=/dev/sda3 or root=/dev/mmcblkop3, or root=LABEL=rootfs
My point is this is suppose to just work. I know I can specify labels or partitions instead of uuid but for our supported platforms I shouldn't need to it needs to "just work". This is a blocker, oh and beagle is not better. 2/2 fail!
What firmware level is the trimslice? What fedora image was used (link plz)?
Will attempt to reproduce
On Mon, Jan 21, 2013 at 5:40 PM, Jon jdisnard@gmail.com wrote:
On Mon, Jan 21, 2013 at 4:19 PM, Peter Robinson pbrobinson@gmail.com wrote:
On 21 Jan 2013 18:47, "Jon" jdisnard@gmail.com wrote:
On Mon, Jan 21, 2013 at 5:39 AM, Peter Robinson pbrobinson@gmail.com wrote:
Has anyone else seen issues booting on the Trimslice?
Basically it boots through but seems unable to fine the rootfs so just hangs.
Peter
Yes, the first thing to try is changing to boot.scr to have root=/dev/sda3 or root=/dev/mmcblkop3, or root=LABEL=rootfs
My point is this is suppose to just work. I know I can specify labels or partitions instead of uuid but for our supported platforms I shouldn't need to it needs to "just work". This is a blocker, oh and beagle is not better. 2/2 fail!
What firmware level is the trimslice?
It's in the fpaste output. The newer one that supports DT what ever that was.
What fedora image was used (link plz)?
The one linked in the beta announcement.
Will attempt to reproduce
I just "xzcat img > /dev/blah" and shoved the card in the mmc slot on the front and tried to boot it.
Peter
On 01/21/2013 03:39 AM, Peter Robinson wrote:
Has anyone else seen issues booting on the Trimslice?
Basically it boots through but seems unable to fine the rootfs so just hangs.
I've seen this when booting a trimslice with usb sata and updated firmware. Works fine with mmc, just not usb sata. The root= thing is a red herring. Am hoping 3.7 with an updated dtb will work.
----- Original Message -----
From: Brendan Conoboy blc@redhat.com To: arm@lists.fedoraproject.org Cc: Sent: Monday, January 21, 2013 3:04 PM Subject: Re: [fedora-arm] Issues on Trimslice with F18 beta
On 01/21/2013 03:39 AM, Peter Robinson wrote:
Has anyone else seen issues booting on the Trimslice?
Basically it boots through but seems unable to fine the rootfs so just
hangs.
I've seen this when booting a trimslice with usb sata and updated firmware. Works fine with mmc, just not usb sata. The root= thing is a red herring. Am hoping 3.7 with an updated dtb will work.
The updated dtb isn't going to help that case much.
The link you sent has:
Kernel command line: mem=384M@0M mem=512M@512M nvmem=128M@384M vmalloc=248M video=tegrafb console=ttyS0,115200n8 root=UUID=679506b3-6b4e-4427-90ea-1f7c91d69093 ro rootwaitThe root=UUID=679506b3-6b4e-4427-90ea-1f7c91d69093 Isn't going to work on much of anything since that is a unique id.
You have a much better shot with root=/dev/sda3 or whatever you are trying to boot from.
On 21 Jan 2013 20:04, "Brendan Conoboy" blc@redhat.com wrote:
On 01/21/2013 03:39 AM, Peter Robinson wrote:
Has anyone else seen issues booting on the Trimslice?
Basically it boots through but seems unable to fine the rootfs so just
hangs.
I've seen this when booting a trimslice with usb sata and updated
firmware. Works fine with mmc, just not usb sata. The root= thing is a red herring. Am hoping 3.7 with an updated dtb will work.
That was mmc
Brendan Conoboy / Red Hat, Inc. / blc@redhat.com _______________________________________________ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
-
Brendan Conoboy -
Jon -
Peter Robinson -
Sean Omalley