On 6/29/16, arm_ml@rirasoft.de arm_ml@rirasoft.de wrote:
Am 2016-06-19 08:28, schrieb ali hagigat:
I have the following software and hardware:
- Odroid XU4
- Fedora-LXDE-armhfp-24-Beta-1.6-sda.raw.xz
I used /usr/share/uboot/odroid-xu3/u-boot.bin as u-boot.bin file. When the board boots, it finds vmlinuz and initramfs files and the kernel start running. But it seems that kernel has some problems:
- it can not initialize HDMI interface
- it does not find the EXT4 root file system
The following boot messages are printed and then the system stops with a dracut prompt and no keyboard key stroke is taken :
--- schnip---
Hello Ali,
Any update on this? Did you manage to rebuild the initramfs? I will try to make this week (I must search for a howto to rebuild initramfs)
Greetings Andreas
I used the latest image of Fedora, https://download.fedoraproject.org/pub/fedora/linux/releases/24/Spins/armhfp... The kernel can not initialize HDMI port and monitor like before and it can not read the root file system though the SD card UUID is correct.
I did not change initramfs. I need a howto page like Andreas to do that.
But why initramfs is incorrect? while Fedora has released the final version of arm-Fedora 24 What are the functionalities of these drivers? dw_exynos-mmc exynosdrm ehci-exynos ohci-exynos
uboot is reading the fist partition on the SD card, how the kernel and initramfs can not read the third partion?!! and the root file system I think the Fedora arm image has problems
On Wednesday, June 29, 2016 6:37:48 PM CDT ali hagigat wrote:
On 6/29/16, arm_ml@rirasoft.de arm_ml@rirasoft.de wrote:
Am 2016-06-19 08:28, schrieb ali hagigat:
I have the following software and hardware:
- Odroid XU4
- Fedora-LXDE-armhfp-24-Beta-1.6-sda.raw.xz
I used /usr/share/uboot/odroid-xu3/u-boot.bin as u-boot.bin file. When the board boots, it finds vmlinuz and initramfs files and the kernel start running. But it seems that kernel has some problems:
- it can not initialize HDMI interface
- it does not find the EXT4 root file system
The following boot messages are printed and then the system stops with
a dracut prompt and no keyboard key stroke is taken :
--- schnip---
Hello Ali,
Any update on this? Did you manage to rebuild the initramfs? I will try to make this week (I must search for a howto to rebuild initramfs)
Greetings Andreas
I used the latest image of Fedora, https://download.fedoraproject.org/pub/fedora/linux/releases/24/Spins/armhfp /images/Fedora-LXDE-armhfp-24-1.2-sda.raw.xz The kernel can not initialize HDMI port and monitor like before and it can not read the root file system though the SD card UUID is correct.
I did not change initramfs. I need a howto page like Andreas to do that.
do you have another working arm system? you will need one to make the initramfs
But why initramfs is incorrect? while Fedora has released the final version of arm-Fedora 24 What are the functionalities of these drivers? dw_exynos-mmc
this is the mmc driver for exynos
exynosdrm
video for exynos
ehci-exynos ohci-exynos
use 1.1 and usb 2 drivers for exynos
uboot is reading the fist partition on the SD card, how the kernel and initramfs can not read the third partion?!! and the root file system I think the Fedora arm image has problems
u-boot can read the partitions just fine, but the kernel can not, which is where you are getting stuck.
I used the Xfce image, after editing extlinux.conf and rebuilding the initramfs to include the correct modules it worked fine. there is a bug in dracut or the kernel or both that prevents things from just working. We will need to figure out what exactly and work with the upstreams to fix it
Dennis
Am 2016-06-30 02:46, schrieb Dennis Gilmore:
On Wednesday, June 29, 2016 6:37:48 PM CDT ali hagigat wrote:
On 6/29/16, arm_ml@rirasoft.de arm_ml@rirasoft.de wrote:
Am 2016-06-19 08:28, schrieb ali hagigat:
I have the following software and hardware:
- Odroid XU4
- Fedora-LXDE-armhfp-24-Beta-1.6-sda.raw.xz
I used /usr/share/uboot/odroid-xu3/u-boot.bin as u-boot.bin file. When the board boots, it finds vmlinuz and initramfs files and the kernel start running. But it seems that kernel has some problems:
- it can not initialize HDMI interface
- it does not find the EXT4 root file system
The following boot messages are printed and then the system stops with
a dracut prompt and no keyboard key stroke is taken :
--- schnip---
Hello Ali,
Any update on this? Did you manage to rebuild the initramfs? I will try to make this week (I must search for a howto to rebuild initramfs)
Greetings Andreas
I used the latest image of Fedora, https://download.fedoraproject.org/pub/fedora/linux/releases/24/Spins/armhfp /images/Fedora-LXDE-armhfp-24-1.2-sda.raw.xz The kernel can not initialize HDMI port and monitor like before and it can not read the root file system though the SD card UUID is correct.
I did not change initramfs. I need a howto page like Andreas to do that.
do you have another working arm system? you will need one to make the initramfs
But why initramfs is incorrect? while Fedora has released the final version of arm-Fedora 24 What are the functionalities of these drivers? dw_exynos-mmc
this is the mmc driver for exynos
exynosdrm
video for exynos
ehci-exynos ohci-exynos
use 1.1 and usb 2 drivers for exynos
uboot is reading the fist partition on the SD card, how the kernel and initramfs can not read the third partion?!! and the root file system I think the Fedora arm image has problems
u-boot can read the partitions just fine, but the kernel can not, which is where you are getting stuck.
I used the Xfce image, after editing extlinux.conf and rebuilding the initramfs to include the correct modules it worked fine. there is a bug in dracut or the kernel or both that prevents things from just working. We will need to figure out what exactly and work with the upstreams to fix it
Dennis _______________________________________________ arm mailing list arm@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org
Hello Dennis,
is there any howto to rebuild the initramfs on the ARM-System and bring it back the image? I have a running Fedora 24 with the Ubuntu-Kernel on the XU4. There is no extlinux.conf.
Thank you Andreas
Am 2016-06-30 10:19, schrieb arm_ml@rirasoft.de:
Am 2016-06-30 02:46, schrieb Dennis Gilmore:
On Wednesday, June 29, 2016 6:37:48 PM CDT ali hagigat wrote:
On 6/29/16, arm_ml@rirasoft.de arm_ml@rirasoft.de wrote:
Am 2016-06-19 08:28, schrieb ali hagigat:
I have the following software and hardware:
- Odroid XU4
- Fedora-LXDE-armhfp-24-Beta-1.6-sda.raw.xz
I used /usr/share/uboot/odroid-xu3/u-boot.bin as u-boot.bin file. When the board boots, it finds vmlinuz and initramfs files and the kernel start running. But it seems that kernel has some problems:
- it can not initialize HDMI interface
- it does not find the EXT4 root file system
The following boot messages are printed and then the system stops with
a dracut prompt and no keyboard key stroke is taken :
--- schnip---
Hello Ali,
Any update on this? Did you manage to rebuild the initramfs? I will try to make this week (I must search for a howto to rebuild initramfs)
Greetings Andreas
I used the latest image of Fedora, https://download.fedoraproject.org/pub/fedora/linux/releases/24/Spins/armhfp /images/Fedora-LXDE-armhfp-24-1.2-sda.raw.xz The kernel can not initialize HDMI port and monitor like before and it can not read the root file system though the SD card UUID is correct.
I did not change initramfs. I need a howto page like Andreas to do that.
do you have another working arm system? you will need one to make the initramfs
But why initramfs is incorrect? while Fedora has released the final version of arm-Fedora 24 What are the functionalities of these drivers? dw_exynos-mmc
this is the mmc driver for exynos
exynosdrm
video for exynos
ehci-exynos ohci-exynos
use 1.1 and usb 2 drivers for exynos
uboot is reading the fist partition on the SD card, how the kernel and initramfs can not read the third partion?!! and the root file system I think the Fedora arm image has problems
u-boot can read the partitions just fine, but the kernel can not, which is where you are getting stuck.
I used the Xfce image, after editing extlinux.conf and rebuilding the initramfs to include the correct modules it worked fine. there is a bug in dracut or the kernel or both that prevents things from just working. We will need to figure out what exactly and work with the upstreams to fix it
Dennis _______________________________________________ arm mailing list arm@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org
Hello Dennis,
is there any howto to rebuild the initramfs on the ARM-System and bring it back the image? I have a running Fedora 24 with the Ubuntu-Kernel on the XU4. There is no extlinux.conf.
Thank you Andreas _______________________________________________ arm mailing list arm@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org
Hello all, is there anybody who can help me to rebuild the initramfs (with including the exynos modules) on the ARM-System and bring it back the image?
@Dennis: it is possible to have your working image or a howto for the rebuild?
Thanks Andreas
Hello everyone,
I've recently purchased the Odroid-Xu4 and have been following this thread to install Fedora 24 on it. I now have the system fully booting with the exception that Xorg is not working. I am running the Fedora Mate Spin. I even performed a "dnf update" to get the latest 4.4.6 kernel and package fixes, but no luck with booting into graphical mode via Xorg.
Here's what I did to get there.
1. Downloaded the latest Fedora 24 Mate Spin, Fedora-Mate-armhfp-24-1.2-sda.raw.xz, onto my raspberry pi2. The raspberry pi 2, runs the raspberry pi 2 kernel 4.4.7+ with Fedora-Mate-armhfp-24-1.2-sda.raw.xz layered on top. This is I suspect, similar to what Andreas is doing with the Ubuntu kernel. In any event, a Fedora (or derivative i.e. Centos, Redhat, etc.) install on an ARMv7 based system is required to do the following tasks.
2. I too found the same issues as Ali in that using the u-boot install script to install u-boot.bin makes the the boot partition unreadable if you use either the Fedora install script or install the partitions yourself. However, if you begin the boot partition on starting disk block "3072" instead of the default "2048", you can get around this.
I used fdisk to create my boot partition starting at block "3072". I also found I needed to set the length of this partition to 400M or more (I use 400M). I set this partition as a FAT partition just to see if I could get the system working, based on everyone's comments in this thread. I will, in the near future try to use and EXT4 partition here and see if it works as well. But other things first, like trying to get Xorg working.
**note: I have now rebuilt the boot partition as ext4 and following this procedure, everything except Xorg works.
I then added a swap partition as partition 2 with a length of 200M, and partition 3 as my root partition (EXT4), taking up the rest of my 32GB SD card.
3. I then created the filesystems, vFAT or EXT4 (your choice) for the boot partition, EXT4 for the root partition. Once done, I mounted them on the raspberry pi 2.
4 I copied the root partition of the Fedora Spin image to the mounted root partition on the raspberry pi and similarly for the boot partition. If you require exact commands here, I can provide them to you later. But I suspect you already know how to do this.
5. I downloaded the appropriate u-boot pieces Peter suggested and which Andreas used from the Odroid website specified, along with the SD install script. I also copied into this directory, the u-boot.bin and u-boot.dtb files from /usr/share/uboot/odroid-xu3 of the mounted root partition on the raspberry pi. This is the Fedora supported u-boot.bin. Then I flashed the SD card using the Odroid SD install script.
6. At this point, you have everything on your mounted SD card. The problem now is you run into the issues that Ali ran into if you try to boot the Odroid from it, namely, the kernel (4.5.5-300) cannot find the root partition from which to boot and dracut fails because of it. This is because key drivers (as Dennis eluded) seem to be missing from the kernel AND the initramfs image. Therefore, the following steps are required to get past this.
7. While your SD card is still mounted (both boot and root partitions), perform the following tasks: a) execute the command "blkid -s UUID /dev/xxxx" where "xxxx" is your mounted SD card root partition. This will provide the UUID of that disk partition. Do the same thing for your mounted SD card boot partition. b) execute the chroot command to your mounted SD root partition. c) add any users you need by executing "useradd" and add/set the root passwd so you can login through and alternate counsel if needed. Also, you can set up your network configuration here too if you know your system's ethernet MAC address (if you use static addresses) or you know what IP address will be assigned to your network devices via DHCP. As well, edit the /etc/selinux/config file and change "SELINUX=enforcing" to "SELINUX=disabled". This will allow you to login at an alternate console or remotely via ssh. d) edit the /etc/fstab file and replace the UUIDs for each partition with what you obtained in step "7a". Also, ensure that vFAT is the type of partition being mounted for the boot partition and ext4 is the type for the root partition. If not, then change the fstab file so that they are, respectively. e) edit the /boot/extlinux/extlinux.conf file and on the "Append" line, replace the root=UUID value with that which you obtained from step "7a". You also need to add the need kernel drivers to this line such that your line looks like the following with your root's UUID instead of mine:
Append rd.driver.pre=dw_mmc-exynos,exynosdrm,ehci-exynos,ohci-exynos ro root=UUID=4237819f-e48e-46c8-8b6a-7832e7e351b5 f) Delete the original initramfs and rebuild the new initramfs image by executing the following commands:
rm -f /boot/initramfs-4.5.5-300.fc24.armv7hl.img dracut --add-drivers "dw_mmc-exynos exynosdrm ehci-exynos ohci-exynos" /boot/initramfs-4.5.5-300.fc24.armv7hl.img 4.5.5-300.fc24.armv7hl
g) exit from chroot back to your normal root window.
8. Unmount all of your SD card partitions and try to boot from the SD card in your Odroid.
9. At this point, the system should boot using the 4.5.5-300 kernel but it will fail in XORG to get to graphical mode. It does at this point however, support SSH. So you can connect via SSH if your network is set up correctly.
10. If you login to your Odroid and your network is working, you can then update to the latest kernel (4.6.5-300) and packages using the "dnf update" command. However, if you do this, you will then again have to rebuild the initramfs image because although the updates provide the correct driver parameters on the Append line in the updated /boot/extlinux/extlinux.conf file, the 4.6.5 initramfs image does not contain them. As a result, the system will fail to boot in dracut, once again looking for the root partition. To build the correct initramfs for 4.6.5-300 execute the following commands:
rm -f /boot/initramfs-4.6.5-300.fc24.armv7hl.img dracut --add-drivers "dw_mmc-exynos exynosdrm ehci-exynos ohci-exynos" /boot/initramfs-4.6.5-300.fc24.armv7hl.img 4.6.5-300.fc24.armv7hl
**Note, if you want to boot from the 4.6.5 kernel, then remember to edit the /boot/extlinux/extlinux.conf file and change the "default" line to use the 4.6.5-300 entry.
11. Reboot your Odroid if you ran "dnf update" and made the suggested changes in step 10. At this point, you should be where I am currently ... with a system that boots completely but fails to boot into graphics mode. And yes, executing "systemctl get-default" displays "graphical.target".
Anyway, that's it. Hope this helps.
Stewart Samuels
P.S. @Peter or @Dennis, any help with the XORG problem would be greatly appreciated. What do you need me to do to get you information on this? Post the XORG.0.LOG here? What files/logs do you need, etc.?
Also, on another note. I notice now that when the system boots (either 4.5.5-300 or 4.6.5-300 kernel), it only boots 5 cpus. If fails to start the remaining 3. Is there a limit that is being exceeded somewhere?
A follow-up to my previous post for clarity.
In step 7d, if you built an EXT4 boot partition rather the the vFAT partition, ensure in the fstab file that it is EXT4.
Also, the line that follows the "dracut" lines is in fact part of the "dracut' command. It is not a separate line. Unfortunately, it got wrapped in this message and looks like a separate command.
Regarding the xorg problem, this is what I get when executing "startx" X.Org X Server 1.18.4 Release Date: 2016-07-19 X Protocol Version 11, Revision 0 Build Operating System: 4.6.3-300.fc24.armv7hl Current Operating System: Linux myodroid 4.6.5-300.fc24.armv7hl #1 SMP Thu Jul 28 03:09:19 UTC 2016 armv7l Kernel command line: rd.driver.pre=dw_mmc-exynos,exynosdrm,ehci-exynos,ohci-exynos ro root=UUID=dfac3a15-7d31-46ed-842f-2f7599871202 LANG=en_US.UTF-8 Build Date: 19 July 2016 06:13:15PM Build ID: xorg-x11-server 1.18.4-1.fc24 Current version of pixman: 0.34.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Thu Aug 11 13:06:48 2016 (==) Using system config directory "/usr/share/X11/xorg.conf.d" gbm: failed to open any driver (search paths /usr/lib/dri) gbm: Last dlopen error: /usr/lib/dri/exynos_dri.so: cannot open shared object file: No such file or directory failed to load driver: exynos EGL_MESA_drm_image required. (EE) Fatal server error: (EE) AddScreen/ScreenInit failed for driver 0 (EE) (EE) Please consult the Fedora Project support at http://wiki.x.org for help. (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. (EE) (EE) Server terminated with error (1). Closing log file. xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error
And here is the information from the UART serial port regarding the CPU startup.
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x100 [ 0.000000] Linux version 4.6.5-300.fc24.armv7hl (mockbuild@arm04-builder03.arm.fedoraproject.org) (gcc version 6.1.1 20160621 (Red Hat 6.1.1-3) (GCC) ) #1 SMP Thu Jul 28 03:09:19 UTC 2016 [ 0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=10c5387d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] Machine model: Hardkernel Odroid XU4 [ 0.000000] efi: Getting EFI parameters from FDT: [ 0.000000] efi: UEFI not found. [ 0.000000] cma: Reserved 16 MiB at 0xbd800000 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] Samsung CPU ID: 0xe5422001 [ 0.000000] Running under secure firmware. [ 0.000000] percpu: Embedded 13 pages/cpu @eed8a000 s24332 r8192 d20724 u53248 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 512832 [ 0.000000] Kernel command line: rd.driver.pre=dw_mmc-exynos,exynosdrm,ehci-exynos,ohci-exynos ro root=UUID=dfac3a15-7d31-46ed- 842f-2f7599871202 LANG=en_US.UTF-8 [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Memory: 1991052K/2058240K available (7609K kernel code, 1140K rwdata, 3376K rodata, 1108K init, 854K bss, 50804K re served, 16384K cma-reserved, 1271808K highmem) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB) [ 0.000000] vmalloc : 0xf0800000 - 0xff800000 ( 240 MB) [ 0.000000] lowmem : 0xc0000000 - 0xf0000000 ( 768 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) [ 0.000000] .text : 0xc0208000 - 0xc0cc28f8 (10987 kB) [ 0.000000] .init : 0xc0cc3000 - 0xc0dd8000 (1108 kB) [ 0.000000] .data : 0xc0dd8000 - 0xc0ef52b4 (1141 kB) [ 0.000000] .bss : 0xc0ef52b4 - 0xc0fcabb8 ( 855 kB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] Build-time adjustment of leaf fanout to 32. [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] Switching to timer-based delay loop, resolution 41ns [ 0.000000] clocksource: mct-frc: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns [ 0.000007] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns [ 0.005175] Console: colour dummy device 80x30 [ 0.006059] console [tty0] enabled [ 0.006118] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=120000) [ 0.006178] pid_max: default: 32768 minimum: 301 [ 0.006430] Security Framework initialized [ 0.006465] Yama: becoming mindful. [ 0.006510] SELinux: Initializing. [ 0.006857] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.006900] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.008098] CPU: Testing write buffer coherency: ok [ 0.008174] ftrace: allocating 31745 entries in 63 pages [ 0.071403] CPU0: update cpu_capacity 448 [ 0.071454] CPU0: thread -1, cpu 0, socket 1, mpidr 80000100 [ 0.071691] Setting up static identity map for 0x40208280 - 0x40208318 [ 0.079130] EFI services will not be available. [ 0.081617] CPU1: update cpu_capacity 448 [ 0.081626] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.083550] CPU2: update cpu_capacity 448 [ 0.083557] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 [ 0.085427] CPU3: update cpu_capacity 448 [ 0.085434] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 [ 0.087281] CPU4: update cpu_capacity 1535 [ 0.087288] CPU4: thread -1, cpu 0, socket 0, mpidr 80000000 [ 1.084982] CPU5: failed to boot: -110 [ 2.084996] CPU6: failed to boot: -110 [ 3.085013] CPU7: failed to boot: -110 [ 3.085077] Brought up 5 CPUs [ 3.085105] SMP: Total of 5 processors activated (240.00 BogoMIPS). [ 3.085132] CPU: All CPU(s) started in HYP mode.
Also, the "Append" line step 7e also got wrapped. There is only one line, not 3 lines as appear. It begins with "Append" and ends with your root partition UUID. There is also a space betwen the "ro" and "root=UUID".
***** Update *****
I now have the system booting into graphical mode. Here's what I found out in the process:
I use the process as stated above on the stock Fedora 24 Mate Spin (kernel 4.5.5-300) to build the system. However, on the "append" line of /boot/extlinux/extlinux.conf, you do NOT need all the "dracut" parameters required to build the initramfs. Rather, my append line simply looks like the following:
append ro root=UUID=4d70d307-a61d-4cda-9535-8a8849c262c2 cma=64M
That's it.
-
ali hagigat -
Andreas Reschke -
Dennis Gilmore -
Stewart Samuels