I've been able to boot Fedora 19 on my Wandboard quad. It is very rough - I basically cross-compiled uboot and the Freescale 3.0.35 kernel separately, and constructed an SD card image from that, plus the rootfs from Fedora-KDE-armhfp-19-1-sda.raw.xz.
I naturally had to edit the fstab to match the partitions I created on my SD card.
Anyway, a few pictures are here: http://www.sfalco.us/fedora
It's a start...
Steve
On 09/08/2013 05:59 PM, Steven Falco wrote:
I've been able to boot Fedora 19 on my Wandboard quad. It is very rough - I basically cross-compiled uboot and the Freescale 3.0.35 kernel separately, and constructed an SD card image from that, plus the rootfs from Fedora-KDE-armhfp-19-1-sda.raw.xz.
I naturally had to edit the fstab to match the partitions I created on my SD card.
Anyway, a few pictures are here: http://www.sfalco.us/fedora
It's a start...
Arrrg - looks like you have to go to http://www.sfalco.us/fedora/fedora.html Apparently, Optonline gets confused without the full file name.
Or, just go to http://www.sfalco.us and click the fedora link at the bottom of the page.
Steve
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
El Sun, 08 Sep 2013 18:03:22 -0400 Steven Falco stevenfalco@gmail.com escribió:
On 09/08/2013 05:59 PM, Steven Falco wrote:
I've been able to boot Fedora 19 on my Wandboard quad. It is very rough - I basically cross-compiled uboot and the Freescale 3.0.35 kernel separately, and constructed an SD card image from that, plus the rootfs from Fedora-KDE-armhfp-19-1-sda.raw.xz.
I naturally had to edit the fstab to match the partitions I created on my SD card.
Anyway, a few pictures are here: http://www.sfalco.us/fedora
It's a start...
Arrrg - looks like you have to go to http://www.sfalco.us/fedora/fedora.html Apparently, Optonline gets confused without the full file name.
Or, just go to http://www.sfalco.us and click the fedora link at the bottom of the page.
Fedora 20 kernel is working just fine, however there is currently no framebuffer support. we have u-boot built for all the wandboards in Fedora 19 and 20. but good to see some people running fedora on their wandboards
Dennis
Whoa! You have graphics working, but kernel 3.0.35! Does that kernel have all the filesystem capabilities to make Fedora happy? Extended attr's, ACLs, selinux, cgroups, etc....
Does anybody know what it would take to get frame buffer support in 3.11 or 3.12? Maybe we just enable Stephen Warren's simple framebuffer driver? (aka SIMPLE_FB) Just wondering....
-Jon Disnard
On Sun, Sep 8, 2013 at 10:34 PM, Dennis Gilmore dennis@ausil.us wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
El Sun, 08 Sep 2013 18:03:22 -0400 Steven Falco stevenfalco@gmail.com escribió:
On 09/08/2013 05:59 PM, Steven Falco wrote:
I've been able to boot Fedora 19 on my Wandboard quad. It is very rough - I basically cross-compiled uboot and the Freescale 3.0.35 kernel separately, and constructed an SD card image from that, plus the rootfs from Fedora-KDE-armhfp-19-1-sda.raw.xz.
I naturally had to edit the fstab to match the partitions I created on my SD card.
Anyway, a few pictures are here: http://www.sfalco.us/fedora
It's a start...
Arrrg - looks like you have to go to http://www.sfalco.us/fedora/fedora.html Apparently, Optonline gets confused without the full file name.
Or, just go to http://www.sfalco.us and click the fedora link at the bottom of the page.
Fedora 20 kernel is working just fine, however there is currently no framebuffer support. we have u-boot built for all the wandboards in Fedora 19 and 20. but good to see some people running fedora on their wandboards
Dennis -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (GNU/Linux)
iEYEARECAAYFAlItQcMACgkQkSxm47BaWffGFACfa2EmFXy2s7t8Xd/FbzOu9MEb DpcAn1G7LqbzeBKtdW/qQvvTuaDaCEUs =SxWt -----END PGP SIGNATURE----- _______________________________________________ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On 09/09/2013 12:08 PM, Jon wrote:
Whoa! You have graphics working, but kernel 3.0.35! Does that kernel have all the filesystem capabilities to make Fedora happy? Extended attr's, ACLs, selinux, cgroups, etc....
I have not tried to enable anything beyond what is in the wandboard_defconfig from Tapani's kernel tree here:
git://repo.or.cz/wandboard.git
It should not be difficult to do so. But I gather that the community is more interested in the mainline 3.12+ kernels (as am I, actually), so I guess I shouldn't waste much more of my time on 3.0.35. I simply started there, because that is what Freescale provides.
Steve
On Mon, 2013-09-09 at 11:08 -0500, Jon wrote:
Whoa! You have graphics working, but kernel 3.0.35! Does that kernel have all the filesystem capabilities to make Fedora happy? Extended attr's, ACLs, selinux, cgroups, etc....
I've been shipping a 3.0.35 kernel with the F18/F19 images used by the Community Squeeze project since we switched to a Fedora based image back in February. www.communitysqueeze.org
I'm guessing if I factor in that most of our users have downloaded at least 3 images, we currently have 20, maybe 30, Wandboard users running a Fedora based distro. I expect this will be 100's, (rather than 10's), of users at the point that our hardware (John Swenson designed DAC carrier board) is manufactured and available.
Does anybody know what it would take to get frame buffer support in 3.11 or 3.12? Maybe we just enable Stephen Warren's simple framebuffer driver? (aka SIMPLE_FB) Just wondering....
Robert Nelsons 3.11 kernel build has Wandboard HDMI output working with this patch....
https://github.com/RobertCNelson/armv7-multiplatform/blob/v3.11.x/patches/im...
No idea whether that has been submitted to the gregkh staging tree yet.
Regards
Clive
On Tue, Sep 10, 2013 at 8:36 AM, Clive Messer clive.m.messer@gmail.com wrote:
On Mon, 2013-09-09 at 11:08 -0500, Jon wrote:
Whoa! You have graphics working, but kernel 3.0.35! Does that kernel have all the filesystem capabilities to make Fedora happy? Extended attr's, ACLs, selinux, cgroups, etc....
I've been shipping a 3.0.35 kernel with the F18/F19 images used by the Community Squeeze project since we switched to a Fedora based image back in February. www.communitysqueeze.org
I'm guessing if I factor in that most of our users have downloaded at least 3 images, we currently have 20, maybe 30, Wandboard users running a Fedora based distro. I expect this will be 100's, (rather than 10's), of users at the point that our hardware (John Swenson designed DAC carrier board) is manufactured and available.
Does anybody know what it would take to get frame buffer support in 3.11 or 3.12? Maybe we just enable Stephen Warren's simple framebuffer driver? (aka SIMPLE_FB) Just wondering....
Robert Nelsons 3.11 kernel build has Wandboard HDMI output working with this patch....
https://github.com/RobertCNelson/armv7-multiplatform/blob/v3.11.x/patches/im...
No idea whether that has been submitted to the gregkh staging tree yet.
The author "Tony Prisk" on the wandboard forums has been working on ^^^^ driver. I'm getting the feeling he is more interested in getting it perfect first before sending it out to the staging tree.
Regards,
On 10/09/13 15:36, Clive Messer wrote:
On Mon, 2013-09-09 at 11:08 -0500, Jon wrote:
Whoa! You have graphics working, but kernel 3.0.35! Does that kernel have all the filesystem capabilities to make Fedora happy? Extended attr's, ACLs, selinux, cgroups, etc....
I've been shipping a 3.0.35 kernel with the F18/F19 images used by the Community Squeeze project since we switched to a Fedora based image back in February. www.communitysqueeze.org
I'm guessing if I factor in that most of our users have downloaded at least 3 images, we currently have 20, maybe 30, Wandboard users running a Fedora based distro. I expect this will be 100's, (rather than 10's), of users at the point that our hardware (John Swenson designed DAC carrier board) is manufactured and available.
Thanks Clive for shipping community squeeze!
It was a good starter for me, and I think it's awesome, someone did this using Fedora instead of using anything else.
What do you think about porting community squeeze to a standard Fedora 20?
On Sun, Sep 8, 2013 at 10:59 PM, Steven Falco stevenfalco@gmail.com wrote:
I've been able to boot Fedora 19 on my Wandboard quad. It is very rough - I basically cross-compiled uboot and the Freescale 3.0.35 kernel separately, and constructed an SD card image from that, plus the rootfs from Fedora-KDE-armhfp-19-1-sda.**raw.xz.
I naturally had to edit the fstab to match the partitions I created on my SD card.
Anyway, a few pictures are here: http://www.sfalco.us/fedora
It's a start...
We have initial out of the box support for all of the WandBoard devices with F-20 alpha without having to do anything out of the ordinary. Support will only improve with the 3.12 kernel as there's a lot of improvements for i.MX6 landing in there.
Peter
On 09/09/2013 05:14 PM, Peter Robinson wrote:
On Sun, Sep 8, 2013 at 10:59 PM, Steven Falco <stevenfalco@gmail.com mailto:stevenfalco@gmail.com> wrote:
I've been able to boot Fedora 19 on my Wandboard quad. It is very rough - I basically cross-compiled uboot and the Freescale 3.0.35 kernel separately, and constructed an SD card image from that, plus the rootfs from Fedora-KDE-armhfp-19-1-sda.__raw.xz. I naturally had to edit the fstab to match the partitions I created on my SD card. Anyway, a few pictures are here: http://www.sfalco.us/fedora It's a start...We have initial out of the box support for all of the WandBoard devices with F-20 alpha without having to do anything out of the ordinary. Support will only improve with the 3.12 kernel as there's a lot of improvements for i.MX6 landing in there.
Peter
That is good to know. I haven't seen much discussion on this list regarding Wandboards yet. I'll have to grab a copy of F-20 and try it out. Thanks!
I guess the tricky part is the Vivante graphics engines. My understanding is that they are binary-only, which is why I am using the 3.0.35+ Freescale kernel - that appears to be the only one with support right now.
Steve
I guess the tricky part is the Vivante graphics engines. My understanding is that they are binary-only, which is why I am using the 3.0.35+ Freescale kernel - that appears to be the only one with support right now.
At the moment it is but the reverse engineering project etna_viv [1] is coming along pretty quickly so it might not be a problem for long.
On 09/09/2013 05:14 PM, Peter Robinson wrote:
On Sun, Sep 8, 2013 at 10:59 PM, Steven Falco <stevenfalco@gmail.com mailto:stevenfalco@gmail.com> wrote:
I've been able to boot Fedora 19 on my Wandboard quad. It is very rough - I basically cross-compiled uboot and the Freescale 3.0.35 kernel separately, and constructed an SD card image from that, plus the rootfs from Fedora-KDE-armhfp-19-1-sda.__raw.xz. I naturally had to edit the fstab to match the partitions I created on my SD card. Anyway, a few pictures are here: http://www.sfalco.us/fedora It's a start...We have initial out of the box support for all of the WandBoard devices with F-20 alpha without having to do anything out of the ordinary. Support will only improve with the 3.12 kernel as there's a lot of improvements for i.MX6 landing in there.
Peter
I'm afraid I'm going to need a bit of a pointer here. I downloaded Fedora-Minimal-armhfp-20-Alpha-TC1-1-sda.raw.xz, uncompressed it, and dd'ed it to an SD card. I then dd'ed my U-Boot build for the Wandboard Quad onto the SD card, beginning at offset 1k (where the iMX6 bootrom expects it), and started the board running.
From there, I did "ext2load mmc 0:1 12000000 boot.scr" (where 12000000 is the address where I normally load the kernel), and followed that with "source 12000000".
At that point, I got "Welcome to a-b-c 0.57." followed by a list of commands. Now I'm stuck. I tried using dtblist, but it doesn't find anything:
=> run dtblist
Device Tree Blob (DTB) list
Kernel has the following dtbs available: (Currently selected: )
Type 'run dtbX' where X is the dtb number to use.
I then tried (making up addresses without any idea of the right ones to use):
=> setenv u_k_addr 12000000 => setenv u_ramfs_addr 16000000 => setenv u_dtb_addr 1c000000 => setenv u_dtb imx6q-wandboard.dtb
Then I tried "boot", and got: => boot ** File not found /uImage- ** ** File not found /uInitrd- ** ** File not found /dtb-/imx6q-wandboard.dtb ** Failed to mount ext2 filesystem... ** Unrecognized filesystem type **
and a whole bunch more errors. I'm guessing this is because I have not specified whether to use lpae or not, but I don't know how to do that.
Any guidance greatly appreciated.
Steve
On 09/10/2013 04:58 PM, Steven Falco wrote:
Any guidance greatly appreciated.
Do "run klist" before "run dtblist". The dtbs that are available depend upon the kernel to be used. Sounds like a bug though- dtblist should complain no kernel is selected.
On 11/09/13 01:58, Steven Falco wrote:
I'm afraid I'm going to need a bit of a pointer here. I downloaded Fedora-Minimal-armhfp-20-Alpha-TC1-1-sda.raw.xz, uncompressed it, and dd'ed it to an SD card. I then dd'ed my U-Boot build for the Wandboard Quad onto the SD card, beginning at offset 1k (where the iMX6 bootrom expects it), and started the board running.
From my experience, you should take a later snapshot. Recently, I
started to write the process up a bit.
https://fedoraproject.org/wiki/User:Mrunge/Wandboard_quad
Please note, it's a wiki. If anything is missing or wrong, I encourage you to correct it.
On 09/11/2013 02:26 AM, Matthias Runge wrote:
On 11/09/13 01:58, Steven Falco wrote:
I'm afraid I'm going to need a bit of a pointer here. I downloaded Fedora-Minimal-armhfp-20-Alpha-TC1-1-sda.raw.xz, uncompressed it, and dd'ed it to an SD card. I then dd'ed my U-Boot build for the Wandboard Quad onto the SD card, beginning at offset 1k (where the iMX6 bootrom expects it), and started the board running.
From my experience, you should take a later snapshot. Recently, I started to write the process up a bit.
https://fedoraproject.org/wiki/User:Mrunge/Wandboard_quad
Please note, it's a wiki. If anything is missing or wrong, I encourage you to correct it.
Thank you! I was unaware that Fedora had built a U-Boot for the Wandboard!
I tried following your wiki briefly - I'm out of time for this morning.
I got much further, but I appear to have an older version of the kernel than what you quoted.
Mine is vmlinuz-3.11.0-0.rc6.git4.1.fc20.armv7hl while you have vmlinuz-3.11.0-3.fc20.armv7hl.
Below is what happened. Everything was fine, but no output from the kernel. I'll do more digging tonight.
U-Boot 2013.07-rc3 (Jul 19 2013 - 01:52:13)
CPU: Freescale i.MX6Q rev1.2 at 792 MHz Reset cause: POR Board: Wandboard DRAM: 2 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 *** Warning - bad CRC, using default environment
In: serial Out: serial Err: serial Net: FEC [PRIME] Warning: FEC using MAC address from net device
Hit any key to stop autoboot: 0 => run bootcmd mmc0 is current device Retrieving file: /boot/extlinux/extlinux.conf ** File not found /boot/extlinux/extlinux.conf ** Error reading config file Retrieving file: /extlinux/extlinux.conf 524 bytes read in 194 ms (2 KiB/s) Ignoring malformed menu command: autoboot 1: Fedora (3.11.0-0.rc6.git4.1.fc20.armv7hl) 20 (Null) Enter choice: 1 1: Fedora (3.11.0-0.rc6.git4.1.fc20.armv7hl) 20 (Null) Retrieving file: /initramfs-3.11.0-0.rc6.git4.1.fc20.armv7hl.img 10841835 bytes read in 643 ms (16.1 MiB/s) Retrieving file: /vmlinuz-3.11.0-0.rc6.git4.1.fc20.armv7hl 5152408 bytes read in 351 ms (14 MiB/s) append: console=ttymxc0,115200 root=UUID=ac77ed30-9586-4ffe-94c0-7bd5eaebcdfa ro rhgb quiet LANG=en_US.UTF-8 Retrieving file: /dtb/imx6q-wandboard.dtb 23567 bytes read in 153 ms (150.4 KiB/s) (nothing more printed out...)
Thanks again, Steve
On 11/09/13 14:07, Steven Falco wrote:
Hit any key to stop autoboot: 0 => run bootcmd mmc0 is current device Retrieving file: /boot/extlinux/extlinux.conf ** File not found /boot/extlinux/extlinux.conf ** Error reading config file Retrieving file: /extlinux/extlinux.conf 524 bytes read in 194 ms (2 KiB/s) Ignoring malformed menu command: autoboot 1: Fedora (3.11.0-0.rc6.git4.1.fc20.armv7hl) 20 (Null) Enter choice: 1 1: Fedora (3.11.0-0.rc6.git4.1.fc20.armv7hl) 20 (Null) Retrieving file: /initramfs-3.11.0-0.rc6.git4.1.fc20.armv7hl.img 10841835 bytes read in 643 ms (16.1 MiB/s) Retrieving file: /vmlinuz-3.11.0-0.rc6.git4.1.fc20.armv7hl 5152408 bytes read in 351 ms (14 MiB/s) append: console=ttymxc0,115200 root=UUID=ac77ed30-9586-4ffe-94c0-7bd5eaebcdfa ro rhgb quiet LANG=en_US.UTF-8 Retrieving file: /dtb/imx6q-wandboard.dtb 23567 bytes read in 153 ms (150.4 KiB/s) (nothing more printed out...)
Ah yes, I've seen that a couple of times, too; I tried until it worked (about 1 of 5/10 tries). A later just worked for me, so I suggest you should try a later version, e.g from http://dl.fedoraproject.org/pub/alt/stage/20-Alpha-RC2/Images/armhfp/Fedora-...
Best regards, Matthias
On 09/12/2013 04:54 AM, Matthias Runge wrote:
On 11/09/13 14:07, Steven Falco wrote:
Hit any key to stop autoboot: 0 => run bootcmd mmc0 is current device Retrieving file: /boot/extlinux/extlinux.conf ** File not found /boot/extlinux/extlinux.conf ** Error reading config file Retrieving file: /extlinux/extlinux.conf 524 bytes read in 194 ms (2 KiB/s) Ignoring malformed menu command: autoboot 1: Fedora (3.11.0-0.rc6.git4.1.fc20.armv7hl) 20 (Null) Enter choice: 1 1: Fedora (3.11.0-0.rc6.git4.1.fc20.armv7hl) 20 (Null) Retrieving file: /initramfs-3.11.0-0.rc6.git4.1.fc20.armv7hl.img 10841835 bytes read in 643 ms (16.1 MiB/s) Retrieving file: /vmlinuz-3.11.0-0.rc6.git4.1.fc20.armv7hl 5152408 bytes read in 351 ms (14 MiB/s) append: console=ttymxc0,115200 root=UUID=ac77ed30-9586-4ffe-94c0-7bd5eaebcdfa ro rhgb quiet LANG=en_US.UTF-8 Retrieving file: /dtb/imx6q-wandboard.dtb 23567 bytes read in 153 ms (150.4 KiB/s) (nothing more printed out...)
Ah yes, I've seen that a couple of times, too; I tried until it worked (about 1 of 5/10 tries). A later just worked for me, so I suggest you should try a later version, e.g from http://dl.fedoraproject.org/pub/alt/stage/20-Alpha-RC2/Images/armhfp/Fedora-...
Thanks - I'm downloading it now.
Steve
On 09/12/2013 07:50 AM, Steven Falco wrote:
On 09/12/2013 04:54 AM, Matthias Runge wrote:
On 11/09/13 14:07, Steven Falco wrote:
Hit any key to stop autoboot: 0 => run bootcmd mmc0 is current device Retrieving file: /boot/extlinux/extlinux.conf ** File not found /boot/extlinux/extlinux.conf ** Error reading config file Retrieving file: /extlinux/extlinux.conf 524 bytes read in 194 ms (2 KiB/s) Ignoring malformed menu command: autoboot 1: Fedora (3.11.0-0.rc6.git4.1.fc20.armv7hl) 20 (Null) Enter choice: 1 1: Fedora (3.11.0-0.rc6.git4.1.fc20.armv7hl) 20 (Null) Retrieving file: /initramfs-3.11.0-0.rc6.git4.1.fc20.armv7hl.img 10841835 bytes read in 643 ms (16.1 MiB/s) Retrieving file: /vmlinuz-3.11.0-0.rc6.git4.1.fc20.armv7hl 5152408 bytes read in 351 ms (14 MiB/s) append: console=ttymxc0,115200 root=UUID=ac77ed30-9586-4ffe-94c0-7bd5eaebcdfa ro rhgb quiet LANG=en_US.UTF-8 Retrieving file: /dtb/imx6q-wandboard.dtb 23567 bytes read in 153 ms (150.4 KiB/s) (nothing more printed out...)
Ah yes, I've seen that a couple of times, too; I tried until it worked (about 1 of 5/10 tries). A later just worked for me, so I suggest you should try a later version, e.g from http://dl.fedoraproject.org/pub/alt/stage/20-Alpha-RC2/Images/armhfp/Fedora-...
Thanks - I'm downloading it now.
When it does crash (which is every so many boots), I briefly (on occasion) see output about illegal/undefined instructions. There's perhaps a multitplatform artifact in here. Some kind of errata or other workaround might be enabled that triggers on some boots and causes this.
Jon.
On 09/13/2013 12:17 PM, Jon Masters wrote:
When it does crash (which is every so many boots), I briefly (on occasion) see output about illegal/undefined instructions. There's perhaps a multitplatform artifact in here. Some kind of errata or other workaround might be enabled that triggers on some boots and causes this.
The sadly, there is no (real) output from the kernel, but "Wrong Image Format for"
Matthias
On 09/14/2013 03:48 AM, Matthias Runge wrote:
On 09/13/2013 12:17 PM, Jon Masters wrote:
When it does crash (which is every so many boots), I briefly (on occasion) see output about illegal/undefined instructions. There's perhaps a multitplatform artifact in here. Some kind of errata or other workaround might be enabled that triggers on some boots and causes this.
The sadly, there is no (real) output from the kernel, but "Wrong Image Format for"
Matthias
I am seeing similar behavior. Sometimes I get a hang:
Enter choice: 1 1: Fedora (3.11.0-300.fc20.armv7hl) 20 (Null) Retrieving file: /initramfs-3.11.0-300.fc20.armv7hl.img 10760171 bytes read in 600 ms (17.1 MiB/s) Retrieving file: /vmlinuz-3.11.0-300.fc20.armv7hl 4748528 bytes read in 304 ms (14.9 MiB/s) append: console=ttymxc0,115200 root=UUID=e72ec2c4-bd9e-4100-85be-df34e7f01e53 ro rhgb quiet LANG=en_US.UTF-8 Retrieving file: /dtb/imx6q-wandboard.dtb 23567 bytes read in 160 ms (143.6 KiB/s)
(no more output after the above)
Another time I got:
Retrieving file: /dtb/imx6q-wandboard.dtb 23567 bytes read in 161 ms (142.6 KiB/s) Wrong Image Format for undefined instruction pc : [<8e1fec44>] lr : [<8ff93518>] sp : 8f579708 ip : 00000000 fp : 00000000 r10: 8ffb9e18 r9 : 8f57978c r8 : 8f579f38 r7 : 00000003 r6 : 00000000 r5 : 0000070f r4 : 8ffb9e18 r3 : 00000000 r2 : 00000001 r1 : 00000020 r0 : 00000000 Flags: nZCv IRQs off FIQs off Mode SVC_32 Resetting CPU ...
I'll try another SD card, in case this one is defective.
BTW, I made a few edits to:
https://fedoraproject.org/wiki/User:Mrunge/Wandboard_quad
I added a wget of the u-boot package, and how to unpack the rpm, and I updated the extlinux.conf script for the correct root UUID for the Alpha-2 build.
One other thing - once I got the system installed and booted, I could not log in. I tried numerous times, and even edited /etc/shadow to paste in the crypted PW from my desktop machine.
Finally, I disabled selinux, booted into single-user mode, did "init 3" and then I could log in. I later tried booting directly into level 3, and I could log in. Has anyone seen anything similar?
Steve
The next RC will have the fix to the initial-setup program that prompts a text mode console to set root password, create user, set the timezone, etc.
Thanks for updating the wiki notes =)
On Sat, Sep 14, 2013 at 1:03 PM, Steven Falco stevenfalco@gmail.com wrote:
On 09/14/2013 03:48 AM, Matthias Runge wrote:
On 09/13/2013 12:17 PM, Jon Masters wrote:
When it does crash (which is every so many boots), I briefly (on occasion) see output about illegal/undefined instructions. There's perhaps a multitplatform artifact in here. Some kind of errata or other workaround might be enabled that triggers on some boots and causes this.
The sadly, there is no (real) output from the kernel, but "Wrong Image Format for"
Matthias
I am seeing similar behavior. Sometimes I get a hang:
Enter choice: 1 1: Fedora (3.11.0-300.fc20.armv7hl) 20 (Null) Retrieving file: /initramfs-3.11.0-300.fc20.armv7hl.img 10760171 bytes read in 600 ms (17.1 MiB/s) Retrieving file: /vmlinuz-3.11.0-300.fc20.armv7hl 4748528 bytes read in 304 ms (14.9 MiB/s) append: console=ttymxc0,115200 root=UUID=e72ec2c4-bd9e-4100-85be-df34e7f01e53 ro rhgb quiet LANG=en_US.UTF-8 Retrieving file: /dtb/imx6q-wandboard.dtb 23567 bytes read in 160 ms (143.6 KiB/s)
(no more output after the above)
Another time I got:
Retrieving file: /dtb/imx6q-wandboard.dtb 23567 bytes read in 161 ms (142.6 KiB/s) Wrong Image Format for undefined instruction pc : [<8e1fec44>] lr : [<8ff93518>] sp : 8f579708 ip : 00000000 fp : 00000000 r10: 8ffb9e18 r9 : 8f57978c r8 : 8f579f38 r7 : 00000003 r6 : 00000000 r5 : 0000070f r4 : 8ffb9e18 r3 : 00000000 r2 : 00000001 r1 : 00000020 r0 : 00000000 Flags: nZCv IRQs off FIQs off Mode SVC_32 Resetting CPU ...
I'll try another SD card, in case this one is defective.
BTW, I made a few edits to:
https://fedoraproject.org/wiki/User:Mrunge/Wandboard_quad
I added a wget of the u-boot package, and how to unpack the rpm, and I updated the extlinux.conf script for the correct root UUID for the Alpha-2 build.
One other thing - once I got the system installed and booted, I could not log in. I tried numerous times, and even edited /etc/shadow to paste in the crypted PW from my desktop machine.
Finally, I disabled selinux, booted into single-user mode, did "init 3" and then I could log in. I later tried booting directly into level 3, and I could log in. Has anyone seen anything similar?
Steve
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
If someone can capture a full backtrace then I will look. I will also aim to reproduce myself a few more times. I am told there is a JTAG option but have not looked further since the weekend yet.
On 09/16/2013 07:55 PM, Jonathan Masters wrote:
If someone can capture a full backtrace then I will look. I will also aim to reproduce myself a few more times. I am told there is a JTAG option but have not looked further since the weekend yet.
I've tried, but I think what I've already posted is all the backtrace I can get.
Here is the strange thing. It looks like this is happening while still in u-boot, but it appears to be dependent on the kernel being loaded.
I realize that that doesn't make much sense, but here are my reasons for that conclusion.
1) One of the failure cases prints "Wrong Image Format for", which comes from u-boot/common/cmd_bootm.c
2) If the boot sequence gets as far as printing:
Starting kernel ...
then it will always boot successfully (for me, anyway). That message comes from u-boot/arch/arm/lib/bootm.c
3) Another failure case prints:
MAYBE you should read doc/README.arm-unaligned-accesses
That comes from u-boot/arch/arm/lib/interrupts.c
I cannot explain why the specific kernel matters, unless the size of the kernel matters. The uImage from Tapani's tree is around 2 MB, while the Fedora one is closer to 5 MB.
I don't know if this makes it any easier to track down, but it is the best data I've got right now.
Steve
On 09/12/2013 04:54 AM, Matthias Runge wrote:
On 11/09/13 14:07, Steven Falco wrote:
Hit any key to stop autoboot: 0 => run bootcmd mmc0 is current device Retrieving file: /boot/extlinux/extlinux.conf ** File not found /boot/extlinux/extlinux.conf ** Error reading config file Retrieving file: /extlinux/extlinux.conf 524 bytes read in 194 ms (2 KiB/s) Ignoring malformed menu command: autoboot 1: Fedora (3.11.0-0.rc6.git4.1.fc20.armv7hl) 20 (Null) Enter choice: 1 1: Fedora (3.11.0-0.rc6.git4.1.fc20.armv7hl) 20 (Null) Retrieving file: /initramfs-3.11.0-0.rc6.git4.1.fc20.armv7hl.img 10841835 bytes read in 643 ms (16.1 MiB/s) Retrieving file: /vmlinuz-3.11.0-0.rc6.git4.1.fc20.armv7hl 5152408 bytes read in 351 ms (14 MiB/s) append: console=ttymxc0,115200 root=UUID=ac77ed30-9586-4ffe-94c0-7bd5eaebcdfa ro rhgb quiet LANG=en_US.UTF-8 Retrieving file: /dtb/imx6q-wandboard.dtb 23567 bytes read in 153 ms (150.4 KiB/s) (nothing more printed out...)
Ah yes, I've seen that a couple of times, too; I tried until it worked (about 1 of 5/10 tries). A later just worked for me, so I suggest you should try a later version, e.g from http://dl.fedoraproject.org/pub/alt/stage/20-Alpha-RC2/Images/armhfp/Fedora-...
Working great on my board here too. I've made a minor fix to your wiki entry to update the kernel paths so that they work with the Alpha RC2.
Jon.
On Wed, Sep 11, 2013 at 08:26:51AM +0200, Matthias Runge wrote:
On 11/09/13 01:58, Steven Falco wrote:
I'm afraid I'm going to need a bit of a pointer here. I downloaded Fedora-Minimal-armhfp-20-Alpha-TC1-1-sda.raw.xz, uncompressed it, and dd'ed it to an SD card. I then dd'ed my U-Boot build for the Wandboard Quad onto the SD card, beginning at offset 1k (where the iMX6 bootrom expects it), and started the board running.
From my experience, you should take a later snapshot. Recently, I started to write the process up a bit.
https://fedoraproject.org/wiki/User:Mrunge/Wandboard_quad
Please note, it's a wiki. If anything is missing or wrong, I encourage you to correct it.
Thanks for posting the link. I've used your description with on my Wandboard DualLite and it works like a charm (using the imx6dl uboot.imx and dtb). Dmesg: http://paste.fedoraproject.org/39690/48270137/
Some issues I have noticed: - no autoboot (bootcmd and bootdelay are set in uboot, whats missing?) - no automatic resize of / on the first boot (is that intentional?) - occasional hang while booting (mentioned elsewhere in this thread)
Does anyone know if bugs have been filed for this already? I do not seem to be able to find any.
What are the plans to go forward with this wiki page? Currently it is named and written for the Wandboard Quad, but obviously other Wandboard(s) work too.
Also, the scripts that Hans de Goede provides in his AllWinner remix take care of configuring the bootloader and things, maybe that can be used as a base for the other image(s)? I think that providing a common way to write/configure images for Fedora ARM where possible is preferred?
Niels
I'm afraid I'm going to need a bit of a pointer here. I downloaded
Fedora-Minimal-armhfp-20-Alpha-TC1-1-sda.raw.xz, uncompressed it, and dd'ed it to an SD card. I then dd'ed my U-Boot build for the Wandboard Quad onto the SD card, beginning at offset 1k (where the iMX6 bootrom expects it), and started the board running.
From my experience, you should take a later snapshot. Recently, I started to write the process up a bit.
https://fedoraproject.org/wiki/User:Mrunge/Wandboard_quad
Please note, it's a wiki. If anything is missing or wrong, I encourage you to correct it.
Thanks for posting the link. I've used your description with on my Wandboard DualLite and it works like a charm (using the imx6dl uboot.imx and dtb). Dmesg: http://paste.fedoraproject.org/39690/48270137/
Some issues I have noticed:
- no autoboot (bootcmd and bootdelay are set in uboot, whats missing?)
Likely an issue with a-b-c so I'd check with Brendan and see if there's anything needed.
- no automatic resize of / on the first boot (is that intentional?)
- occasional hang while booting (mentioned elsewhere in this thread)
Does anyone know if bugs have been filed for this already? I do not seem to be able to find any.
What are the plans to go forward with this wiki page? Currently it is named and written for the Wandboard Quad, but obviously other Wandboard(s) work too.
I would likely rename it, and even make it generic to all i.MX6 devices as I suspect the Wandboard, utilite and new CuBoxes will all be very similar.
Also, the scripts that Hans de Goede provides in his AllWinner remix take care of configuring the bootloader and things, maybe that can be used as a base for the other image(s)? I think that providing a common way to write/configure images for Fedora ARM where possible is preferred?
Yes, it's been randomly discussed that they might be a good start for that sort of thing but no ones actually done it.
Peter
On 09/15/2013 10:55 PM, Peter Robinson wrote:
Likely an issue with a-b-c so I'd check with Brendan and see if there's anything needed.
As I understand it, the wandboard in RC2 works with extlinux, but not abc. The latest version of abc does contain wandboard support, but is sitting in testing waiting for love. Whether you have a wandboard or some other a-b-c using board, please give it a try:
https://admin.fedoraproject.org/updates/FEDORA-2013-16724/arm-boot-config-0....
On Mon, Sep 16, 2013 at 09:34:21AM -0700, Brendan Conoboy wrote:
On 09/15/2013 10:55 PM, Peter Robinson wrote:
Likely an issue with a-b-c so I'd check with Brendan and see if there's anything needed.
As I understand it, the wandboard in RC2 works with extlinux, but not abc. The latest version of abc does contain wandboard support, but is sitting in testing waiting for love. Whether you have a wandboard or some other a-b-c using board, please give it a try:
https://admin.fedoraproject.org/updates/FEDORA-2013-16724/arm-boot-config-0....
I am happy to test, but indeed the Wandboard in RC2 uses extlinux. When booting it shows a uboot menu (with "U-Boot console" as only entry which autoboots).
Manually loading the boot.scr and running it shows a-b-c and starts the kernel successfully. Boot log attached. Unfortunately, there seems to be one issue that the serial output after "Starting kernel..." is messed up. It only seems to be something binary, so maybe the console parameters are wrong. I'll try to have a look at that an other day.
It is not clear to me what the advised/correct way to configure the system should be. Is booting with extlinux the goal, or use a-b-c? Either way, the uboot.imx that is compiled for the Wandboard does not seem to have the correct autoboot options. This is probably a bug in the configuration done by the uboot-tools package, but without knowing what the expected/planned behaviour is, I can not patch/test or file a decent bug.
Thanks, Niels
On 09/18/2013 07:00 AM, Niels de Vos wrote:
I am happy to test, but indeed the Wandboard in RC2 uses extlinux. When booting it shows a uboot menu (with "U-Boot console" as only entry which autoboots).
Thanks!
Manually loading the boot.scr and running it shows a-b-c and starts the kernel successfully. Boot log attached. Unfortunately, there seems to be one issue that the serial output after "Starting kernel..." is messed up. It only seems to be something binary, so maybe the console parameters are wrong. I'll try to have a look at that an other day.
Yes, this is a known issue which requires an update to uboot-tools. Basically, abc uses the uboot environment variable $console. Currently uboot-tools provides that setting, which includes the right tty, but doesn't set the speed (It should be 115200), so the kernel message output is garbled, probably 9600 baud. Systemd seems to figure out the right setting in the end though.
It is not clear to me what the advised/correct way to configure the system should be. Is booting with extlinux the goal, or use a-b-c? Either way, the uboot.imx that is compiled for the Wandboard does not seem to have the correct autoboot options. This is probably a bug in the configuration done by the uboot-tools package, but without knowing what the expected/planned behaviour is, I can not patch/test or file a decent bug.
Long term we'd like to retire abc in favor of extlinux- abc is a stopgap for boards with a uboot which cannot support it. I suggest filing a BZ against uboot-tools for what appears to be missing. Thanks again,
On Wed, Sep 11, 2013 at 12:58 AM, Steven Falco stevenfalco@gmail.comwrote:
On 09/09/2013 05:14 PM, Peter Robinson wrote:
On Sun, Sep 8, 2013 at 10:59 PM, Steven Falco <stevenfalco@gmail.commailto: stevenfalco@gmail.com**> wrote:
I've been able to boot Fedora 19 on my Wandboard quad. It is very rough - I basically cross-compiled uboot and the Freescale 3.0.35 kernel separately, and constructed an SD card image from that, plus the rootfs from Fedora-KDE-armhfp-19-1-sda.__**raw.xz. I naturally had to edit the fstab to match the partitions I created on my SD card. Anyway, a few pictures are here: http://www.sfalco.us/fedora It's a start...We have initial out of the box support for all of the WandBoard devices with F-20 alpha without having to do anything out of the ordinary. Support will only improve with the 3.12 kernel as there's a lot of improvements for i.MX6 landing in there.
Peter
I'm afraid I'm going to need a bit of a pointer here. I downloaded Fedora-Minimal-armhfp-20-**Alpha-TC1-1-sda.raw.xz, uncompressed it, and dd'ed it to an SD card. I then dd'ed my U-Boot build for the Wandboard Quad onto the SD card, beginning at offset 1k (where the iMX6 bootrom expects it), and started the board running.
Why are you using your own custom uboot? We ship one for the wandboards which ensures it has all the needed bits to boot Fedora. The details of what to do with the uboot should be documented generally for F-19 omap devices and you should be able to sub in the WBQ where necessary.
On 09/11/2013 05:12 AM, Peter Robinson wrote:
On Wed, Sep 11, 2013 at 12:58 AM, Steven Falco <stevenfalco@gmail.com mailto:stevenfalco@gmail.com> wrote:
On 09/09/2013 05:14 PM, Peter Robinson wrote: On Sun, Sep 8, 2013 at 10:59 PM, Steven Falco <stevenfalco@gmail.com <mailto:stevenfalco@gmail.com> <mailto:stevenfalco@gmail.com <mailto:stevenfalco@gmail.com>>__> wrote: I've been able to boot Fedora 19 on my Wandboard quad. It is very rough - I basically cross-compiled uboot and the Freescale 3.0.35 kernel separately, and constructed an SD card image from that, plus the rootfs from Fedora-KDE-armhfp-19-1-sda.____raw.xz. I naturally had to edit the fstab to match the partitions I created on my SD card. Anyway, a few pictures are here: http://www.sfalco.us/fedora It's a start... We have initial out of the box support for all of the WandBoard devices with F-20 alpha without having to do anything out of the ordinary. Support will only improve with the 3.12 kernel as there's a lot of improvements for i.MX6 landing in there. Peter I'm afraid I'm going to need a bit of a pointer here. I downloaded Fedora-Minimal-armhfp-20-__Alpha-TC1-1-sda.raw.xz, uncompressed it, and dd'ed it to an SD card. I then dd'ed my U-Boot build for the Wandboard Quad onto the SD card, beginning at offset 1k (where the iMX6 bootrom expects it), and started the board running.Why are you using your own custom uboot? We ship one for the wandboards which ensures it has all the needed bits to boot Fedora. The details of what to do with the uboot should be documented generally for F-19 omap devices and you should be able to sub in the WBQ where necessary.
For the simple reason that I didn't know a Fedora one existed. I perhaps foolishly assumed that since there was no Wandboard xz file yet, that nothing else existed for Wandboard. I know better now. :-)
Steve
-
Brendan Conoboy -
Clive Messer -
Dennis Gilmore -
Jon -
Jon Masters -
Matthias Runge -
Niels de Vos -
Peter Robinson -
Robert Nelson -
Steven Falco