Hello
for a while now i have been struggling to create a set of steps to make a successfully bootable fedora 28 image for my odroid hc2 computers.
the reason for this is several, but main one is to have all gluster related packaged available like the samba vfs modules and iscsi related packages for gluster that is missing from the ubuntu images. plus i prefer fedora.
all i get is a sd card that boots but then hangs on initial setup and if i try to work around that by disabling it then boot takes maybe 5-10 minutes at least with failing services (probably those that depend on network) and when i finally get to a login prompt root doesn't work
here is my step by step instructions so far that's not quite working: (this is done from a fedora 28 host)
1: first install needed packages dnf install arm-image-installer-2.5-1.fc28.noarch dnf install uboot-images-armv7-2018.03-6.fc28.noarch
2: get image and install it to sd card fedora-arm-image-installer --target=none --image=Fedora-Minimal-armhfp-28-1.1-sda.raw.xz --resizefs --norootpass --media=/dev/sdf --args "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd cpuidle.off=1 no_bL_switcher console=tty1 console=ttySAC2,115200n8"
(sdf in this case is my sd card)
3: fix the missing dtb file mkdir /tmp/sd mount -t auto /dev/sdf2 /tmp/sd cd /tmp/sd/dtb ln -s exynos5422-odroidxu4.dtb exynos5422-odroidunknown.dtb umount /tmp/sd
4: make it boot by running sd_fusing mkdir sd_fusing; cd sd_fusing wget https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
chmod a+x sd_fusing.sh cp /usr/share/uboot/odroid-xu3/u-boot.bin .
./sd_fusing.sh /dev/sdf
ok so now comes the problems at this stage i have a bootable image but it gets stuck, most likely on initial setup that never shows up. the thing is, it is not locked up because if i plug in an usb device i get a few lines on the serial console so kernel is still working but boot is stuck.
last few lines on serial console is something like: Starting firewalld - dynamic firewall daemon... Starting Initial Setup configuration program... then some stuff related to usb & my disk then on first boot a few lines related to OpenSSH key generation rebooting hangs at same place with exception of SSH keys.
to get a bit further i can mount the root filesystem manually on my other computer and remove the following two files: rm /etc/systemd/system/graphical.target.wants/initial-setup.service rm /etc/systemd/system/multi-user.target.wants/initial-setup.service
this gets rid of the initial setup but then i get a whole bunch of services failing and boot being really really slow, it takes probably 10-15 minutes for everything to time out and get to the logon prompt. when i get it root doesn't work.
this is where i kind of gave up. i know i somehow managed to get a bootable image several months ago, but i'm not sure if i then had to manually set root password by editing passwd or shadow before trying to boot.
things on my wish list for this board:
easier installation and updated packages that work. for example arm-image-installer with a board definition for odroid. may be usefull even if we have to run sd_fusing manualy after anyway, possibly with a text saying so. this also would help to make --addconsole work
uboot that recognized hc2 so it loads the right file dtb file for hc2, one that works and is appropriate.
Hi,
for a while now i have been struggling to create a set of steps to make a successfully bootable fedora 28 image for my odroid hc2 computers.
We're in final freeze for Fedora 29 so I would suggest trying that and seeing how you get on. You can get the latest nightly here:
https://download.fedoraproject.org/pub/fedora/linux/development/29/Spins/arm...
the reason for this is several, but main one is to have all gluster related packaged available like the samba vfs modules and iscsi related packages for gluster that is missing from the ubuntu images. plus i prefer fedora.
all i get is a sd card that boots but then hangs on initial setup and if i try to work around that by disabling it then boot takes maybe 5-10 minutes at least with failing services (probably those that depend on network) and when i finally get to a login prompt root doesn't work
here is my step by step instructions so far that's not quite working: (this is done from a fedora 28 host)
1: first install needed packages dnf install arm-image-installer-2.5-1.fc28.noarch dnf install uboot-images-armv7-2018.03-6.fc28.noarch
I would install the f29 uboot-images-armv7 version here as we've moved to 2018.09
2: get image and install it to sd card fedora-arm-image-installer --target=none --image=Fedora-Minimal-armhfp-28-1.1-sda.raw.xz --resizefs --norootpass --media=/dev/sdf --args "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd cpuidle.off=1 no_bL_switcher console=tty1 console=ttySAC2,115200n8"
I don't believe you need "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd" bit for F-29 but I don't have a device to test.
(sdf in this case is my sd card)
3: fix the missing dtb file mkdir /tmp/sd mount -t auto /dev/sdf2 /tmp/sd cd /tmp/sd/dtb ln -s exynos5422-odroidxu4.dtb exynos5422-odroidunknown.dtb umount /tmp/sd
F-29 has exynos5422-odroidhc1.dtb so that might be a closer fit.
4: make it boot by running sd_fusing mkdir sd_fusing; cd sd_fusing wget https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
chmod a+x sd_fusing.sh cp /usr/share/uboot/odroid-xu3/u-boot.bin .
./sd_fusing.sh /dev/sdf
ok so now comes the problems at this stage i have a bootable image but it gets stuck, most likely on initial setup that never shows up. the thing is, it is not locked up because if i plug in an usb device i get a few lines on the serial console so kernel is still working but boot is stuck.
Try F-29, that's where all the focus is now.
last few lines on serial console is something like: Starting firewalld - dynamic firewall daemon... Starting Initial Setup configuration program... then some stuff related to usb & my disk then on first boot a few lines related to OpenSSH key generation rebooting hangs at same place with exception of SSH keys.
to get a bit further i can mount the root filesystem manually on my other computer and remove the following two files: rm /etc/systemd/system/graphical.target.wants/initial-setup.service rm /etc/systemd/system/multi-user.target.wants/initial-setup.service
this gets rid of the initial setup but then i get a whole bunch of services failing and boot being really really slow, it takes probably 10-15 minutes for everything to time out and get to the logon prompt. when i get it root doesn't work.
this is where i kind of gave up. i know i somehow managed to get a bootable image several months ago, but i'm not sure if i then had to manually set root password by editing passwd or shadow before trying to boot.
things on my wish list for this board:
easier installation and updated packages that work. for example arm-image-installer with a board definition for odroid. may be usefull even if we have to run sd_fusing manualy after anyway, possibly with a text saying so. this also would help to make --addconsole work
uboot that recognized hc2 so it loads the right file dtb file for hc2, one that works and is appropriate. _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
On 2018-10-14 18:03, Peter Robinson wrote:
Hi,
for a while now i have been struggling to create a set of steps to make a successfully bootable fedora 28 image for my odroid hc2 computers.
We're in final freeze for Fedora 29 so I would suggest trying that and seeing how you get on. You can get the latest nightly here:
https://download.fedoraproject.org/pub/fedora/linux/development/29/Spins/arm...
the reason for this is several, but main one is to have all gluster related packaged available like the samba vfs modules and iscsi related packages for gluster that is missing from the ubuntu images. plus i prefer fedora.
all i get is a sd card that boots but then hangs on initial setup and if i try to work around that by disabling it then boot takes maybe 5-10 minutes at least with failing services (probably those that depend on network) and when i finally get to a login prompt root doesn't work
here is my step by step instructions so far that's not quite working: (this is done from a fedora 28 host)
1: first install needed packages dnf install arm-image-installer-2.5-1.fc28.noarch dnf install uboot-images-armv7-2018.03-6.fc28.noarch
I would install the f29 uboot-images-armv7 version here as we've moved to 2018.09
done and i have copied over the u-boot file from it to sd_fusing so it gets picked up and copied to sd card.
2: get image and install it to sd card fedora-arm-image-installer --target=none --image=Fedora-Minimal-armhfp-28-1.1-sda.raw.xz --resizefs --norootpass --media=/dev/sdf --args "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd cpuidle.off=1 no_bL_switcher console=tty1 console=ttySAC2,115200n8"
I don't believe you need "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd" bit for F-29 but I don't have a device to test.
ok, also done for testing purposes
(sdf in this case is my sd card)
3: fix the missing dtb file mkdir /tmp/sd mount -t auto /dev/sdf2 /tmp/sd cd /tmp/sd/dtb ln -s exynos5422-odroidxu4.dtb exynos5422-odroidunknown.dtb umount /tmp/sd
F-29 has exynos5422-odroidhc1.dtb so that might be a closer fit.
that file also existed on f28 and when i used f28 i tried both hc1 and xu4 dtb file but no difference.
4: make it boot by running sd_fusing mkdir sd_fusing; cd sd_fusing wget https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
chmod a+x sd_fusing.sh cp /usr/share/uboot/odroid-xu3/u-boot.bin .
./sd_fusing.sh /dev/sdf
ok so now comes the problems at this stage i have a bootable image but it gets stuck, most likely on initial setup that never shows up. the thing is, it is not locked up because if i plug in an usb device i get a few lines on the serial console so kernel is still working but boot is stuck.
Try F-29, that's where all the focus is now.
with above changes boot looks a little better but boot still gets stuck at about the same place. so no luck :-(
haven't tried yet to skip initial setup by removing: /etc/systemd/system/graphical.target.wants/initial-setup.service /etc/systemd/system/multi-user.target.wants/initial-setup.service
last few lines on serial console is something like: Starting firewalld - dynamic firewall daemon... Starting Initial Setup configuration program... then some stuff related to usb & my disk then on first boot a few lines related to OpenSSH key generation rebooting hangs at same place with exception of SSH keys.
to get a bit further i can mount the root filesystem manually on my other computer and remove the following two files: rm /etc/systemd/system/graphical.target.wants/initial-setup.service rm /etc/systemd/system/multi-user.target.wants/initial-setup.service
this gets rid of the initial setup but then i get a whole bunch of services failing and boot being really really slow, it takes probably 10-15 minutes for everything to time out and get to the logon prompt. when i get it root doesn't work.
this is where i kind of gave up. i know i somehow managed to get a bootable image several months ago, but i'm not sure if i then had to manually set root password by editing passwd or shadow before trying to boot.
things on my wish list for this board:
easier installation and updated packages that work. for example arm-image-installer with a board definition for odroid. may be usefull even if we have to run sd_fusing manualy after anyway, possibly with a text saying so. this also would help to make --addconsole work
uboot that recognized hc2 so it loads the right file dtb file for hc2, one that works and is appropriate.
On 10/14/18 4:20 PM, Torbjorn Jansson wrote:
On 2018-10-14 18:03, Peter Robinson wrote:
Hi,
for a while now i have been struggling to create a set of steps to make a successfully bootable fedora 28 image for my odroid hc2 computers.
We're in final freeze for Fedora 29 so I would suggest trying that and seeing how you get on. You can get the latest nightly here:
https://download.fedoraproject.org/pub/fedora/linux/development/29/Spins/arm...
the reason for this is several, but main one is to have all gluster related packaged available like the samba vfs modules and iscsi related packages for gluster that is missing from the ubuntu images. plus i prefer fedora.
all i get is a sd card that boots but then hangs on initial setup and if i try to work around that by disabling it then boot takes maybe 5-10 minutes at least with failing services (probably those that depend on network) and when i finally get to a login prompt root doesn't work
here is my step by step instructions so far that's not quite working: (this is done from a fedora 28 host)
1: first install needed packages dnf install arm-image-installer-2.5-1.fc28.noarch dnf install uboot-images-armv7-2018.03-6.fc28.noarch
I would install the f29 uboot-images-armv7 version here as we've moved to 2018.09
done and i have copied over the u-boot file from it to sd_fusing so it gets picked up and copied to sd card.
2: get image and install it to sd card fedora-arm-image-installer --target=none --image=Fedora-Minimal-armhfp-28-1.1-sda.raw.xz --resizefs --norootpass --media=/dev/sdf --args "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd cpuidle.off=1 no_bL_switcher console=tty1 console=ttySAC2,115200n8"
I don't believe you need "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd" bit for F-29 but I don't have a device to test.
ok, also done for testing purposes
(sdf in this case is my sd card)
3: fix the missing dtb file mkdir /tmp/sd mount -t auto /dev/sdf2 /tmp/sd cd /tmp/sd/dtb ln -s exynos5422-odroidxu4.dtb exynos5422-odroidunknown.dtb umount /tmp/sd
F-29 has exynos5422-odroidhc1.dtb so that might be a closer fit.
that file also existed on f28 and when i used f28 i tried both hc1 and xu4 dtb file but no difference.
4: make it boot by running sd_fusing mkdir sd_fusing; cd sd_fusing wget https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
\ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
\ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
\ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
chmod a+x sd_fusing.sh cp /usr/share/uboot/odroid-xu3/u-boot.bin .
./sd_fusing.sh /dev/sdf
ok so now comes the problems at this stage i have a bootable image but it gets stuck, most likely on initial setup that never shows up. the thing is, it is not locked up because if i plug in an usb device i get a few lines on the serial console so kernel is still working but boot is stuck.
Try F-29, that's where all the focus is now.
with above changes boot looks a little better but boot still gets stuck at about the same place. so no luck :-(
haven't tried yet to skip initial setup by removing: /etc/systemd/system/graphical.target.wants/initial-setup.service /etc/systemd/system/multi-user.target.wants/initial-setup.service
try minimal image first. It does all the setup in text on a serial console or text display.
If you get minimal working, you can install your graphical group and see if that works. Then go back to install the graphical image.
last few lines on serial console is something like: Starting firewalld - dynamic firewall daemon... Starting Initial Setup configuration program... then some stuff related to usb & my disk then on first boot a few lines related to OpenSSH key generation rebooting hangs at same place with exception of SSH keys.
to get a bit further i can mount the root filesystem manually on my other computer and remove the following two files: rm /etc/systemd/system/graphical.target.wants/initial-setup.service rm /etc/systemd/system/multi-user.target.wants/initial-setup.service
this gets rid of the initial setup but then i get a whole bunch of services failing and boot being really really slow, it takes probably 10-15 minutes for everything to time out and get to the logon prompt. when i get it root doesn't work.
this is where i kind of gave up. i know i somehow managed to get a bootable image several months ago, but i'm not sure if i then had to manually set root password by editing passwd or shadow before trying to boot.
things on my wish list for this board:
easier installation and updated packages that work. for example arm-image-installer with a board definition for odroid. may be usefull even if we have to run sd_fusing manualy after anyway, possibly with a text saying so. this also would help to make --addconsole work
uboot that recognized hc2 so it loads the right file dtb file for hc2, one that works and is appropriate.
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
On 2018-10-14 22:53, Robert Moskowitz wrote:
On 10/14/18 4:20 PM, Torbjorn Jansson wrote:
On 2018-10-14 18:03, Peter Robinson wrote:
Hi,
for a while now i have been struggling to create a set of steps to make a successfully bootable fedora 28 image for my odroid hc2 computers.
We're in final freeze for Fedora 29 so I would suggest trying that and seeing how you get on. You can get the latest nightly here:
https://download.fedoraproject.org/pub/fedora/linux/development/29/Spins/arm...
the reason for this is several, but main one is to have all gluster related packaged available like the samba vfs modules and iscsi related packages for gluster that is missing from the ubuntu images. plus i prefer fedora.
all i get is a sd card that boots but then hangs on initial setup and if i try to work around that by disabling it then boot takes maybe 5-10 minutes at least with failing services (probably those that depend on network) and when i finally get to a login prompt root doesn't work
here is my step by step instructions so far that's not quite working: (this is done from a fedora 28 host)
1: first install needed packages dnf install arm-image-installer-2.5-1.fc28.noarch dnf install uboot-images-armv7-2018.03-6.fc28.noarch
I would install the f29 uboot-images-armv7 version here as we've moved to 2018.09
done and i have copied over the u-boot file from it to sd_fusing so it gets picked up and copied to sd card.
2: get image and install it to sd card fedora-arm-image-installer --target=none --image=Fedora-Minimal-armhfp-28-1.1-sda.raw.xz --resizefs --norootpass --media=/dev/sdf --args "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd cpuidle.off=1 no_bL_switcher console=tty1 console=ttySAC2,115200n8"
I don't believe you need "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd" bit for F-29 but I don't have a device to test.
ok, also done for testing purposes
(sdf in this case is my sd card)
3: fix the missing dtb file mkdir /tmp/sd mount -t auto /dev/sdf2 /tmp/sd cd /tmp/sd/dtb ln -s exynos5422-odroidxu4.dtb exynos5422-odroidunknown.dtb umount /tmp/sd
F-29 has exynos5422-odroidhc1.dtb so that might be a closer fit.
that file also existed on f28 and when i used f28 i tried both hc1 and xu4 dtb file but no difference.
4: make it boot by running sd_fusing mkdir sd_fusing; cd sd_fusing wget https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
\ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
\ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
\ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
chmod a+x sd_fusing.sh cp /usr/share/uboot/odroid-xu3/u-boot.bin .
./sd_fusing.sh /dev/sdf
ok so now comes the problems at this stage i have a bootable image but it gets stuck, most likely on initial setup that never shows up. the thing is, it is not locked up because if i plug in an usb device i get a few lines on the serial console so kernel is still working but boot is stuck.
Try F-29, that's where all the focus is now.
with above changes boot looks a little better but boot still gets stuck at about the same place. so no luck :-(
haven't tried yet to skip initial setup by removing: /etc/systemd/system/graphical.target.wants/initial-setup.service /etc/systemd/system/multi-user.target.wants/initial-setup.service
try minimal image first. It does all the setup in text on a serial console or text display.
If you get minimal working, you can install your graphical group and see if that works. Then go back to install the graphical image.
odroid hc2 have no graphics at all and i have been using the minimal image all the time during my testing. it is the initial text based setup that gets screwed up and stuck.
this is why i tried removing the two symlinks starting it but then after 10-15 minutes and a few failed services i cant logon as root.
El dom, 14-10-2018 a las 16:24 +0200, Torbjorn Jansson escribió:
Hello
for a while now i have been struggling to create a set of steps to make a successfully bootable fedora 28 image for my odroid hc2 computers.
the reason for this is several, but main one is to have all gluster related packaged available like the samba vfs modules and iscsi related packages for gluster that is missing from the ubuntu images. plus i prefer fedora.
all i get is a sd card that boots but then hangs on initial setup and if i try to work around that by disabling it then boot takes maybe 5-10 minutes at least with failing services (probably those that depend on network) and when i finally get to a login prompt root doesn't work
here is my step by step instructions so far that's not quite working: (this is done from a fedora 28 host)
1: first install needed packages dnf install arm-image-installer-2.5-1.fc28.noarch dnf install uboot-images-armv7-2018.03-6.fc28.noarch
2: get image and install it to sd card fedora-arm-image-installer --target=none --image=Fedora-Minimal-armhfp-28-1.1-sda.raw.xz --resizefs -- norootpass --media=/dev/sdf --args "rd.driver.pre=ledtrig-heartbeat,xhci-plat- hcd cpuidle.off=1 no_bL_switcher console=tty1 console=ttySAC2,115200n8"
given the hardware you will not want a console on tty1 and being first it is likely where initial-setup is being run
Dennis
(sdf in this case is my sd card)
3: fix the missing dtb file mkdir /tmp/sd mount -t auto /dev/sdf2 /tmp/sd cd /tmp/sd/dtb ln -s exynos5422-odroidxu4.dtb exynos5422-odroidunknown.dtb umount /tmp/sd
4: make it boot by running sd_fusing mkdir sd_fusing; cd sd_fusing wget https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
chmod a+x sd_fusing.sh cp /usr/share/uboot/odroid-xu3/u-boot.bin .
./sd_fusing.sh /dev/sdf
ok so now comes the problems at this stage i have a bootable image but it gets stuck, most likely on initial setup that never shows up. the thing is, it is not locked up because if i plug in an usb device i get a few lines on the serial console so kernel is still working but boot is stuck.
last few lines on serial console is something like: Starting firewalld - dynamic firewall daemon... Starting Initial Setup configuration program... then some stuff related to usb & my disk then on first boot a few lines related to OpenSSH key generation rebooting hangs at same place with exception of SSH keys.
to get a bit further i can mount the root filesystem manually on my other computer and remove the following two files: rm /etc/systemd/system/graphical.target.wants/initial-setup.service rm /etc/systemd/system/multi-user.target.wants/initial-setup.service
this gets rid of the initial setup but then i get a whole bunch of services failing and boot being really really slow, it takes probably 10-15 minutes for everything to time out and get to the logon prompt. when i get it root doesn't work.
this is where i kind of gave up. i know i somehow managed to get a bootable image several months ago, but i'm not sure if i then had to manually set root password by editing passwd or shadow before trying to boot.
things on my wish list for this board:
easier installation and updated packages that work. for example arm-image-installer with a board definition for odroid. may be usefull even if we have to run sd_fusing manualy after anyway, possibly with a text saying so. this also would help to make --addconsole work
uboot that recognized hc2 so it loads the right file dtb file for hc2, one that works and is appropriate. _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
On 2018-10-15 07:25, Dennis Gilmore wrote:
El dom, 14-10-2018 a las 16:24 +0200, Torbjorn Jansson escribió:
Hello
for a while now i have been struggling to create a set of steps to make a successfully bootable fedora 28 image for my odroid hc2 computers.
the reason for this is several, but main one is to have all gluster related packaged available like the samba vfs modules and iscsi related packages for gluster that is missing from the ubuntu images. plus i prefer fedora.
all i get is a sd card that boots but then hangs on initial setup and if i try to work around that by disabling it then boot takes maybe 5-10 minutes at least with failing services (probably those that depend on network) and when i finally get to a login prompt root doesn't work
here is my step by step instructions so far that's not quite working: (this is done from a fedora 28 host)
1: first install needed packages dnf install arm-image-installer-2.5-1.fc28.noarch dnf install uboot-images-armv7-2018.03-6.fc28.noarch
2: get image and install it to sd card fedora-arm-image-installer --target=none --image=Fedora-Minimal-armhfp-28-1.1-sda.raw.xz --resizefs -- norootpass --media=/dev/sdf --args "rd.driver.pre=ledtrig-heartbeat,xhci-plat- hcd cpuidle.off=1 no_bL_switcher console=tty1 console=ttySAC2,115200n8"
given the hardware you will not want a console on tty1 and being first it is likely where initial-setup is being run
Dennis
thanks, i was a bit unsure about that part of the console command. i changed it and retested with f28 using hc1 dtb file and it still gets stuck at same place on first boot.
if i wait long enough first service to fail is: [FAILED] Failed to start System Security Services Daemon. See 'systemctl status sssd.service' for details.
and the times i have disabled initial setup at boot and wait even longer then a few more services fail after several minutes like networkmanager and login something (forgot exact names)
and since i can't get in i cant see what it is failing on to continue my troubleshooting.
(sdf in this case is my sd card)
3: fix the missing dtb file mkdir /tmp/sd mount -t auto /dev/sdf2 /tmp/sd cd /tmp/sd/dtb ln -s exynos5422-odroidxu4.dtb exynos5422-odroidunknown.dtb umount /tmp/sd
4: make it boot by running sd_fusing mkdir sd_fusing; cd sd_fusing wget https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
chmod a+x sd_fusing.sh cp /usr/share/uboot/odroid-xu3/u-boot.bin .
./sd_fusing.sh /dev/sdf
ok so now comes the problems at this stage i have a bootable image but it gets stuck, most likely on initial setup that never shows up. the thing is, it is not locked up because if i plug in an usb device i get a few lines on the serial console so kernel is still working but boot is stuck.
last few lines on serial console is something like: Starting firewalld - dynamic firewall daemon... Starting Initial Setup configuration program... then some stuff related to usb & my disk then on first boot a few lines related to OpenSSH key generation rebooting hangs at same place with exception of SSH keys.
to get a bit further i can mount the root filesystem manually on my other computer and remove the following two files: rm /etc/systemd/system/graphical.target.wants/initial-setup.service rm /etc/systemd/system/multi-user.target.wants/initial-setup.service
this gets rid of the initial setup but then i get a whole bunch of services failing and boot being really really slow, it takes probably 10-15 minutes for everything to time out and get to the logon prompt. when i get it root doesn't work.
this is where i kind of gave up. i know i somehow managed to get a bootable image several months ago, but i'm not sure if i then had to manually set root password by editing passwd or shadow before trying to boot.
things on my wish list for this board:
easier installation and updated packages that work. for example arm-image-installer with a board definition for odroid. may be usefull even if we have to run sd_fusing manualy after anyway, possibly with a text saying so. this also would help to make --addconsole work
uboot that recognized hc2 so it loads the right file dtb file for hc2, one that works and is appropriate.
On 2018-10-15 00:05, Torbjorn Jansson wrote:
On 2018-10-14 22:53, Robert Moskowitz wrote:
On 10/14/18 4:20 PM, Torbjorn Jansson wrote:
On 2018-10-14 18:03, Peter Robinson wrote:
Hi,
for a while now i have been struggling to create a set of steps to make a successfully bootable fedora 28 image for my odroid hc2 computers.
We're in final freeze for Fedora 29 so I would suggest trying that and seeing how you get on. You can get the latest nightly here:
https://download.fedoraproject.org/pub/fedora/linux/development/29/Spins/arm...
the reason for this is several, but main one is to have all gluster related packaged available like the samba vfs modules and iscsi related packages for gluster that is missing from the ubuntu images. plus i prefer fedora.
all i get is a sd card that boots but then hangs on initial setup and if i try to work around that by disabling it then boot takes maybe 5-10 minutes at least with failing services (probably those that depend on network) and when i finally get to a login prompt root doesn't work
here is my step by step instructions so far that's not quite working: (this is done from a fedora 28 host)
1: first install needed packages dnf install arm-image-installer-2.5-1.fc28.noarch dnf install uboot-images-armv7-2018.03-6.fc28.noarch
I would install the f29 uboot-images-armv7 version here as we've moved to 2018.09
done and i have copied over the u-boot file from it to sd_fusing so it gets picked up and copied to sd card.
2: get image and install it to sd card fedora-arm-image-installer --target=none --image=Fedora-Minimal-armhfp-28-1.1-sda.raw.xz --resizefs --norootpass --media=/dev/sdf --args "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd cpuidle.off=1 no_bL_switcher console=tty1 console=ttySAC2,115200n8"
I don't believe you need "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd" bit for F-29 but I don't have a device to test.
ok, also done for testing purposes
(sdf in this case is my sd card)
3: fix the missing dtb file mkdir /tmp/sd mount -t auto /dev/sdf2 /tmp/sd cd /tmp/sd/dtb ln -s exynos5422-odroidxu4.dtb exynos5422-odroidunknown.dtb umount /tmp/sd
F-29 has exynos5422-odroidhc1.dtb so that might be a closer fit.
that file also existed on f28 and when i used f28 i tried both hc1 and xu4 dtb file but no difference.
4: make it boot by running sd_fusing mkdir sd_fusing; cd sd_fusing wget https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
\ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
\ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
\ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
chmod a+x sd_fusing.sh cp /usr/share/uboot/odroid-xu3/u-boot.bin .
./sd_fusing.sh /dev/sdf
ok so now comes the problems at this stage i have a bootable image but it gets stuck, most likely on initial setup that never shows up. the thing is, it is not locked up because if i plug in an usb device i get a few lines on the serial console so kernel is still working but boot is stuck.
Try F-29, that's where all the focus is now.
with above changes boot looks a little better but boot still gets stuck at about the same place. so no luck :-(
haven't tried yet to skip initial setup by removing: /etc/systemd/system/graphical.target.wants/initial-setup.service /etc/systemd/system/multi-user.target.wants/initial-setup.service
try minimal image first. It does all the setup in text on a serial console or text display.
If you get minimal working, you can install your graphical group and see if that works. Then go back to install the graphical image.
odroid hc2 have no graphics at all and i have been using the minimal image all the time during my testing. it is the initial text based setup that gets screwed up and stuck.
this is why i tried removing the two symlinks starting it but then after 10-15 minutes and a few failed services i cant logon as root.
Well... Turns out it does boot eventually. BUT the boot or HORRIBLY slow, it takes a full hour to complete the boot and the initial setup is nowhere to be found (this time using fresh install of sd card)
sssd fails during boot: [FAILED] Failed to start System Security Services Daemon. See 'systemctl status sssd.service' for details.
and then trying to logon with root doesn't work (--norootpass was specified during creation of sd card)
On 2018-10-15 14:33, Torbjorn Jansson wrote:
On 2018-10-15 00:05, Torbjorn Jansson wrote:
On 2018-10-14 22:53, Robert Moskowitz wrote:
On 10/14/18 4:20 PM, Torbjorn Jansson wrote:
On 2018-10-14 18:03, Peter Robinson wrote:
Hi,
for a while now i have been struggling to create a set of steps to make a successfully bootable fedora 28 image for my odroid hc2 computers.
We're in final freeze for Fedora 29 so I would suggest trying that and seeing how you get on. You can get the latest nightly here:
https://download.fedoraproject.org/pub/fedora/linux/development/29/Spins/arm...
the reason for this is several, but main one is to have all gluster related packaged available like the samba vfs modules and iscsi related packages for gluster that is missing from the ubuntu images. plus i prefer fedora.
all i get is a sd card that boots but then hangs on initial setup and if i try to work around that by disabling it then boot takes maybe 5-10 minutes at least with failing services (probably those that depend on network) and when i finally get to a login prompt root doesn't work
here is my step by step instructions so far that's not quite working: (this is done from a fedora 28 host)
1: first install needed packages dnf install arm-image-installer-2.5-1.fc28.noarch dnf install uboot-images-armv7-2018.03-6.fc28.noarch
I would install the f29 uboot-images-armv7 version here as we've moved to 2018.09
done and i have copied over the u-boot file from it to sd_fusing so it gets picked up and copied to sd card.
2: get image and install it to sd card fedora-arm-image-installer --target=none --image=Fedora-Minimal-armhfp-28-1.1-sda.raw.xz --resizefs --norootpass --media=/dev/sdf --args "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd cpuidle.off=1 no_bL_switcher console=tty1 console=ttySAC2,115200n8"
I don't believe you need "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd" bit for F-29 but I don't have a device to test.
ok, also done for testing purposes
(sdf in this case is my sd card)
3: fix the missing dtb file mkdir /tmp/sd mount -t auto /dev/sdf2 /tmp/sd cd /tmp/sd/dtb ln -s exynos5422-odroidxu4.dtb exynos5422-odroidunknown.dtb umount /tmp/sd
F-29 has exynos5422-odroidhc1.dtb so that might be a closer fit.
that file also existed on f28 and when i used f28 i tried both hc1 and xu4 dtb file but no difference.
4: make it boot by running sd_fusing mkdir sd_fusing; cd sd_fusing wget https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
\ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
\ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
\ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu...
chmod a+x sd_fusing.sh cp /usr/share/uboot/odroid-xu3/u-boot.bin .
./sd_fusing.sh /dev/sdf
ok so now comes the problems at this stage i have a bootable image but it gets stuck, most likely on initial setup that never shows up. the thing is, it is not locked up because if i plug in an usb device i get a few lines on the serial console so kernel is still working but boot is stuck.
Try F-29, that's where all the focus is now.
with above changes boot looks a little better but boot still gets stuck at about the same place. so no luck :-(
haven't tried yet to skip initial setup by removing: /etc/systemd/system/graphical.target.wants/initial-setup.service /etc/systemd/system/multi-user.target.wants/initial-setup.service
try minimal image first. It does all the setup in text on a serial console or text display.
If you get minimal working, you can install your graphical group and see if that works. Then go back to install the graphical image.
odroid hc2 have no graphics at all and i have been using the minimal image all the time during my testing. it is the initial text based setup that gets screwed up and stuck.
this is why i tried removing the two symlinks starting it but then after 10-15 minutes and a few failed services i cant logon as root.
Well... Turns out it does boot eventually. BUT the boot or HORRIBLY slow, it takes a full hour to complete the boot and the initial setup is nowhere to be found (this time using fresh install of sd card)
sssd fails during boot: [FAILED] Failed to start System Security Services Daemon. See 'systemctl status sssd.service' for details.
and then trying to logon with root doesn't work (--norootpass was specified during creation of sd card)
i have retested this with fedora 29 with host, image and all other packages as fedora 29 and using my initially posted instructions it works much better.
to my surprise it booted without the 50 minute delay and i also got the first time setup on serial console. i was able to for the first time set a root password properly and get in.
also all cores was active so it is now looking really promising.
what did not work was: ledtrig-heartbeat did not load even when rd.driver.pre=ledtrig-heartbeat was specified on kernel boot command line. so no heartbeat led was on. a simple modprobe ledtrig-heartbeat fixed it and led immediately started blinking as expected. i'm guessing dtb sets led up for heatbeat but module is not loaded at boot so doesnt work.
resizing of rootfs did not work even when --resizefs was specified on command line to fedora-arm-image-installer i had to fix it myself once i got in (fdisk /dev/mmcblk0p3 and then resize2fs). ran out of space initially when updating packages
and of course it would have been really nice with a hc2 dtb file so i don't have to manually link exynos5422-odroidhc1.dtb to exynos5422-odroidunknown.dtb
and related to above also would be good if uboot could detect the hc2 properly instead of unknown.
maybe it is time to write some kind of installation instruction for all this. because how to get all the bits and pieces working is not obvious for someone trying fedora on the odroid hc2 for the first time.
On 2018-11-17 16:52, Torbjorn Jansson wrote:
On 2018-10-15 14:33, Torbjorn Jansson wrote:
On 2018-10-15 00:05, Torbjorn Jansson wrote:
On 2018-10-14 22:53, Robert Moskowitz wrote:
On 10/14/18 4:20 PM, Torbjorn Jansson wrote:
On 2018-10-14 18:03, Peter Robinson wrote:
Hi,
> for a while now i have been struggling to create a set of steps to make a > successfully bootable fedora 28 image for my odroid hc2 computers.
We're in final freeze for Fedora 29 so I would suggest trying that and seeing how you get on. You can get the latest nightly here:
https://download.fedoraproject.org/pub/fedora/linux/development/29/Spins/arm...
> the reason for this is several, but main one is to have all gluster related > packaged available like the samba vfs modules and iscsi related packages > for > gluster that is missing from the ubuntu images. > plus i prefer fedora. > > all i get is a sd card that boots but then hangs on initial setup and if > i try > to work around that by disabling it then boot takes maybe 5-10 minutes > at least > with failing services (probably those that depend on network) and when i > finally get to a login prompt root doesn't work > > > here is my step by step instructions so far that's not quite working: > (this is done from a fedora 28 host) > > 1: first install needed packages > dnf install arm-image-installer-2.5-1.fc28.noarch > dnf install uboot-images-armv7-2018.03-6.fc28.noarch
I would install the f29 uboot-images-armv7 version here as we've moved to 2018.09
done and i have copied over the u-boot file from it to sd_fusing so it gets picked up and copied to sd card.
> 2: get image and install it to sd card > fedora-arm-image-installer --target=none > --image=Fedora-Minimal-armhfp-28-1.1-sda.raw.xz --resizefs --norootpass > --media=/dev/sdf --args "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd > cpuidle.off=1 no_bL_switcher console=tty1 console=ttySAC2,115200n8"
I don't believe you need "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd" bit for F-29 but I don't have a device to test.
ok, also done for testing purposes
> (sdf in this case is my sd card) > > 3: fix the missing dtb file > mkdir /tmp/sd > mount -t auto /dev/sdf2 /tmp/sd > cd /tmp/sd/dtb > ln -s exynos5422-odroidxu4.dtb exynos5422-odroidunknown.dtb > umount /tmp/sd
F-29 has exynos5422-odroidhc1.dtb so that might be a closer fit.
that file also existed on f28 and when i used f28 i tried both hc1 and xu4 dtb file but no difference.
> 4: make it boot by running sd_fusing > mkdir sd_fusing; cd sd_fusing > wget > https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... > > \ > https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... > > \ > https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... > > \ > https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... > > > chmod a+x sd_fusing.sh > cp /usr/share/uboot/odroid-xu3/u-boot.bin . > > ./sd_fusing.sh /dev/sdf > > > ok so now comes the problems > at this stage i have a bootable image but it gets stuck, most likely on > initial > setup that never shows up. > the thing is, it is not locked up because if i plug in an usb device i > get a > few lines on the serial console so kernel is still working but boot is > stuck.
Try F-29, that's where all the focus is now.
with above changes boot looks a little better but boot still gets stuck at about the same place. so no luck :-(
haven't tried yet to skip initial setup by removing: /etc/systemd/system/graphical.target.wants/initial-setup.service /etc/systemd/system/multi-user.target.wants/initial-setup.service
try minimal image first. It does all the setup in text on a serial console or text display.
If you get minimal working, you can install your graphical group and see if that works. Then go back to install the graphical image.
odroid hc2 have no graphics at all and i have been using the minimal image all the time during my testing. it is the initial text based setup that gets screwed up and stuck.
this is why i tried removing the two symlinks starting it but then after 10-15 minutes and a few failed services i cant logon as root.
Well... Turns out it does boot eventually. BUT the boot or HORRIBLY slow, it takes a full hour to complete the boot and the initial setup is nowhere to be found (this time using fresh install of sd card)
sssd fails during boot: [FAILED] Failed to start System Security Services Daemon. See 'systemctl status sssd.service' for details.
and then trying to logon with root doesn't work (--norootpass was specified during creation of sd card)
i have retested this with fedora 29 with host, image and all other packages as fedora 29 and using my initially posted instructions it works much better.
to my surprise it booted without the 50 minute delay and i also got the first time setup on serial console. i was able to for the first time set a root password properly and get in.
also all cores was active so it is now looking really promising.
turns out this is not repeatable and i'm not sure why it worked and why i can't make it work again with fresh image.
so i'm back to the 50 minute boot delay, no initial text based setup and broken root account.
back to the drawing board and debugging. but i'm not exactly sure where to begin, only theory i have is that maybe ubuntu image i was running earlier somehow did something to make my first boot with fedora 29 image also work.
once the image is in a working state everything is just fine. so my suspicions still go to initial text based setup.
On 2018-12-01 16:41, Torbjorn Jansson wrote:
On 2018-11-17 16:52, Torbjorn Jansson wrote:
On 2018-10-15 14:33, Torbjorn Jansson wrote:
On 2018-10-15 00:05, Torbjorn Jansson wrote:
On 2018-10-14 22:53, Robert Moskowitz wrote:
On 10/14/18 4:20 PM, Torbjorn Jansson wrote:
On 2018-10-14 18:03, Peter Robinson wrote: > Hi, > >> for a while now i have been struggling to create a set of steps to make a >> successfully bootable fedora 28 image for my odroid hc2 computers. > > We're in final freeze for Fedora 29 so I would suggest trying that and > seeing how you get on. You can get the latest nightly here: > > https://download.fedoraproject.org/pub/fedora/linux/development/29/Spins/arm... > > >> the reason for this is several, but main one is to have all gluster >> related >> packaged available like the samba vfs modules and iscsi related >> packages for >> gluster that is missing from the ubuntu images. >> plus i prefer fedora. >> >> all i get is a sd card that boots but then hangs on initial setup and >> if i try >> to work around that by disabling it then boot takes maybe 5-10 minutes >> at least >> with failing services (probably those that depend on network) and when i >> finally get to a login prompt root doesn't work >> >> >> here is my step by step instructions so far that's not quite working: >> (this is done from a fedora 28 host) >> >> 1: first install needed packages >> dnf install arm-image-installer-2.5-1.fc28.noarch >> dnf install uboot-images-armv7-2018.03-6.fc28.noarch > > I would install the f29 uboot-images-armv7 version here as we've moved > to 2018.09 >
done and i have copied over the u-boot file from it to sd_fusing so it gets picked up and copied to sd card.
>> 2: get image and install it to sd card >> fedora-arm-image-installer --target=none >> --image=Fedora-Minimal-armhfp-28-1.1-sda.raw.xz --resizefs --norootpass >> --media=/dev/sdf --args "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd >> cpuidle.off=1 no_bL_switcher console=tty1 console=ttySAC2,115200n8" > > I don't believe you need > "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd" bit for F-29 but I > don't have a device to test. >
ok, also done for testing purposes
>> (sdf in this case is my sd card) >> >> 3: fix the missing dtb file >> mkdir /tmp/sd >> mount -t auto /dev/sdf2 /tmp/sd >> cd /tmp/sd/dtb >> ln -s exynos5422-odroidxu4.dtb exynos5422-odroidunknown.dtb >> umount /tmp/sd > > F-29 has exynos5422-odroidhc1.dtb so that might be a closer fit. >
that file also existed on f28 and when i used f28 i tried both hc1 and xu4 dtb file but no difference.
>> 4: make it boot by running sd_fusing >> mkdir sd_fusing; cd sd_fusing >> wget >> https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... >> >> \ >> https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... >> >> \ >> https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... >> >> \ >> https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... >> >> >> chmod a+x sd_fusing.sh >> cp /usr/share/uboot/odroid-xu3/u-boot.bin . >> >> ./sd_fusing.sh /dev/sdf >> >> >> ok so now comes the problems >> at this stage i have a bootable image but it gets stuck, most likely on >> initial >> setup that never shows up. >> the thing is, it is not locked up because if i plug in an usb device i >> get a >> few lines on the serial console so kernel is still working but boot is >> stuck. > > Try F-29, that's where all the focus is now. >
with above changes boot looks a little better but boot still gets stuck at about the same place. so no luck :-(
haven't tried yet to skip initial setup by removing: /etc/systemd/system/graphical.target.wants/initial-setup.service /etc/systemd/system/multi-user.target.wants/initial-setup.service
try minimal image first. It does all the setup in text on a serial console or text display.
If you get minimal working, you can install your graphical group and see if that works. Then go back to install the graphical image.
odroid hc2 have no graphics at all and i have been using the minimal image all the time during my testing. it is the initial text based setup that gets screwed up and stuck.
this is why i tried removing the two symlinks starting it but then after 10-15 minutes and a few failed services i cant logon as root.
Well... Turns out it does boot eventually. BUT the boot or HORRIBLY slow, it takes a full hour to complete the boot and the initial setup is nowhere to be found (this time using fresh install of sd card)
sssd fails during boot: [FAILED] Failed to start System Security Services Daemon. See 'systemctl status sssd.service' for details.
and then trying to logon with root doesn't work (--norootpass was specified during creation of sd card)
i have retested this with fedora 29 with host, image and all other packages as fedora 29 and using my initially posted instructions it works much better.
to my surprise it booted without the 50 minute delay and i also got the first time setup on serial console. i was able to for the first time set a root password properly and get in.
also all cores was active so it is now looking really promising.
turns out this is not repeatable and i'm not sure why it worked and why i can't make it work again with fresh image.
so i'm back to the 50 minute boot delay, no initial text based setup and broken root account.
back to the drawing board and debugging. but i'm not exactly sure where to begin, only theory i have is that maybe ubuntu image i was running earlier somehow did something to make my first boot with fedora 29 image also work.
once the image is in a working state everything is just fine. so my suspicions still go to initial text based setup.
changed boot options so journald outputs its log to serial console. when it is stuck the below section keeps repeating at even intervals over and over. any experts out there that know why the services keep failing?
[ 1293.050223] systemd[1]: Failed to get initial list of names: Connection timed out [ 1293.059841] systemd[1]: dbus.service: Main process exited, code=exited, status=1/FAILURE [ 1293.072092] systemd[1]: dbus.service: Failed with result 'exit-code'. [ 1293.082140] systemd[1]: sshd.service: Service RestartSec=42s expired, scheduling restart. [ 1293.092808] systemd[1]: sshd.service: Scheduled restart job, restart counter is at 5. [ 1293.106343] systemd[1]: systemd-logind.service: Start operation timed out. Terminating. [ 1293.123132] dbus-daemon[820]: dbus[820]: Unknown username "systemd-resolve" in message bus configuration file [ 1293.139994] systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. [ 1293.152811] dbus-daemon[820]: dbus[820]: Unknown username "systemd-timesync" in message bus configuration file [ 1293.166311] dbus-daemon[820]: dbus[820]: Unknown username "systemd-network" in message bus configuration file [ 1293.179637] dbus-daemon[820]: dbus[820]: Unknown username "polkitd" in message bus configuration file [ 1293.191577] dbus-daemon[820]: dbus[820]: Unknown username "polkitd" in message bus configuration file [ 1293.206002] dbus-daemon[820]: Failed to start message bus: Could not get UID and GID for username "dbus" [ 1293.221191] systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 4. [ 1293.235797] systemd[1]: Stopped Network Manager. [ 1293.244930] systemd[1]: Started D-Bus System Message Bus. [ 1293.254343] systemd[1]: Starting Network Manager... [ 1293.262796] systemd[1]: Stopped OpenSSH server daemon. [ 1293.272751] systemd[1]: Stopped target sshd-keygen.target. [ 1293.281229] systemd[1]: Stopping sshd-keygen.target. [ 1293.288891] systemd[1]: Reached target sshd-keygen.target. [ 1293.297969] systemd[1]: Starting OpenSSH server daemon... [ 1293.307232] systemd[1]: systemd-logind.service: Failed with result 'timeout'. [ 1293.317644] systemd[1]: Failed to start Login Service. [ 1293.326278] systemd[1]: systemd-logind.service: Service has no hold-off time (RestartSec=0), scheduling restart. [ 1293.340292] systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 11. [ 1293.353654] systemd[1]: Stopped Login Service. [ 1293.361281] systemd[1]: Starting Login Service... [ 1293.371696] NetworkManager[821]: <info> [1529667196.1274] NetworkManager (version 1.12.4-1.fc29) is starting... (after a restart) [ 1293.386568] NetworkManager[821]: <info> [1529667196.1283] Read config: /etc/NetworkManager/NetworkManager.conf [ 1293.405375] systemd-logind[823]: New seat seat0.
On 2018-12-02 14:54, Torbjorn Jansson wrote:
On 2018-12-01 16:41, Torbjorn Jansson wrote:
On 2018-11-17 16:52, Torbjorn Jansson wrote:
On 2018-10-15 14:33, Torbjorn Jansson wrote:
On 2018-10-15 00:05, Torbjorn Jansson wrote:
On 2018-10-14 22:53, Robert Moskowitz wrote:
On 10/14/18 4:20 PM, Torbjorn Jansson wrote: > On 2018-10-14 18:03, Peter Robinson wrote: >> Hi, >> >>> for a while now i have been struggling to create a set of steps to make a >>> successfully bootable fedora 28 image for my odroid hc2 computers. >> >> We're in final freeze for Fedora 29 so I would suggest trying that and >> seeing how you get on. You can get the latest nightly here: >> >> https://download.fedoraproject.org/pub/fedora/linux/development/29/Spins/arm... >> >> >>> the reason for this is several, but main one is to have all gluster >>> related >>> packaged available like the samba vfs modules and iscsi related >>> packages for >>> gluster that is missing from the ubuntu images. >>> plus i prefer fedora. >>> >>> all i get is a sd card that boots but then hangs on initial setup and >>> if i try >>> to work around that by disabling it then boot takes maybe 5-10 minutes >>> at least >>> with failing services (probably those that depend on network) and when i >>> finally get to a login prompt root doesn't work >>> >>> >>> here is my step by step instructions so far that's not quite working: >>> (this is done from a fedora 28 host) >>> >>> 1: first install needed packages >>> dnf install arm-image-installer-2.5-1.fc28.noarch >>> dnf install uboot-images-armv7-2018.03-6.fc28.noarch >> >> I would install the f29 uboot-images-armv7 version here as we've moved >> to 2018.09 >> > > done and i have copied over the u-boot file from it to sd_fusing so it > gets picked up and copied to sd card. > > >>> 2: get image and install it to sd card >>> fedora-arm-image-installer --target=none >>> --image=Fedora-Minimal-armhfp-28-1.1-sda.raw.xz --resizefs --norootpass >>> --media=/dev/sdf --args "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd >>> cpuidle.off=1 no_bL_switcher console=tty1 console=ttySAC2,115200n8" >> >> I don't believe you need >> "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd" bit for F-29 but I >> don't have a device to test. >> > > ok, also done for testing purposes > > >>> (sdf in this case is my sd card) >>> >>> 3: fix the missing dtb file >>> mkdir /tmp/sd >>> mount -t auto /dev/sdf2 /tmp/sd >>> cd /tmp/sd/dtb >>> ln -s exynos5422-odroidxu4.dtb exynos5422-odroidunknown.dtb >>> umount /tmp/sd >> >> F-29 has exynos5422-odroidhc1.dtb so that might be a closer fit. >> > > that file also existed on f28 and when i used f28 i tried both hc1 and > xu4 dtb file but no difference. > >>> 4: make it boot by running sd_fusing >>> mkdir sd_fusing; cd sd_fusing >>> wget >>> https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... >>> >>> \ >>> https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... >>> >>> \ >>> https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... >>> >>> \ >>> https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_fu... >>> >>> >>> chmod a+x sd_fusing.sh >>> cp /usr/share/uboot/odroid-xu3/u-boot.bin . >>> >>> ./sd_fusing.sh /dev/sdf >>> >>> >>> ok so now comes the problems >>> at this stage i have a bootable image but it gets stuck, most likely >>> on initial >>> setup that never shows up. >>> the thing is, it is not locked up because if i plug in an usb device i >>> get a >>> few lines on the serial console so kernel is still working but boot is >>> stuck. >> >> Try F-29, that's where all the focus is now. >> > > with above changes boot looks a little better but boot still gets stuck > at about the same place. > so no luck :-( > > haven't tried yet to skip initial setup by removing: > /etc/systemd/system/graphical.target.wants/initial-setup.service > /etc/systemd/system/multi-user.target.wants/initial-setup.service
try minimal image first. It does all the setup in text on a serial console or text display.
If you get minimal working, you can install your graphical group and see if that works. Then go back to install the graphical image.
odroid hc2 have no graphics at all and i have been using the minimal image all the time during my testing. it is the initial text based setup that gets screwed up and stuck.
this is why i tried removing the two symlinks starting it but then after 10-15 minutes and a few failed services i cant logon as root.
Well... Turns out it does boot eventually. BUT the boot or HORRIBLY slow, it takes a full hour to complete the boot and the initial setup is nowhere to be found (this time using fresh install of sd card)
sssd fails during boot: [FAILED] Failed to start System Security Services Daemon. See 'systemctl status sssd.service' for details.
and then trying to logon with root doesn't work (--norootpass was specified during creation of sd card)
i have retested this with fedora 29 with host, image and all other packages as fedora 29 and using my initially posted instructions it works much better.
to my surprise it booted without the 50 minute delay and i also got the first time setup on serial console. i was able to for the first time set a root password properly and get in.
also all cores was active so it is now looking really promising.
turns out this is not repeatable and i'm not sure why it worked and why i can't make it work again with fresh image.
so i'm back to the 50 minute boot delay, no initial text based setup and broken root account.
back to the drawing board and debugging. but i'm not exactly sure where to begin, only theory i have is that maybe ubuntu image i was running earlier somehow did something to make my first boot with fedora 29 image also work.
once the image is in a working state everything is just fine. so my suspicions still go to initial text based setup.
changed boot options so journald outputs its log to serial console. when it is stuck the below section keeps repeating at even intervals over and over. any experts out there that know why the services keep failing?
<snip> [ 1293.152811] dbus-daemon[820]: dbus[820]: Unknown username "systemd-timesync" <snip, several lines related to unknown username>
i think i have found the cause of my boot problems and also one or two bugs in fedora-arm-image-installer
first one that is not so critical but still different compared to how fedora28 version of fedora-arm-image-installer worked and is related to --resizefs in fedora28 this did the right thing, in fedora29 it doesn't work. it appears to do something but my guess is that it tries to resize wrong partition or similar. end result is no resizing of root partition.
second one is the important one. specifying --norootpass results in an image totally broken with a lot of services errors with "Unknown username" (if you turn on systemd journal logging to serial console) and then boot is stuck in an endless loop. i'm guessing fedora-arm-image-installer incorrectly modifies some files
with above two changes i have now successfully 4 sd cards for my 4 odroid hc2 that all boot properly on first try with no long boot delay. so i think i can say it is repeatable.
<snip> [ 1293.152811] dbus-daemon[820]: dbus[820]: Unknown username "systemd-timesync" <snip, several lines related to unknown username>
i think i have found the cause of my boot problems and also one or two bugs in fedora-arm-image-installer
first one that is not so critical but still different compared to how fedora28 version of fedora-arm-image-installer worked and is related to --resizefs in fedora28 this did the right thing, in fedora29 it doesn't work. it appears to do something but my guess is that it tries to resize wrong partition or similar. end result is no resizing of root partition.
second one is the important one. specifying --norootpass results in an image totally broken with a lot of services errors with "Unknown username" (if you turn on systemd journal logging to serial console) and then boot is stuck in an endless loop. i'm guessing fedora-arm-image-installer incorrectly modifies some files
with above two changes i have now successfully 4 sd cards for my 4 odroid hc2 that all boot properly on first try with no long boot delay. so i think i can say it is repeatable.
And from your bug report, which you don't reference here, you're using 2.5 and I believe this has now all been fixed in a now stable 2.8
Peter
FWIW, I bought an ODROID-HC2 this week and though I'd share my findings with the most current versions from rawhide on my F29 x86_64 which has
I don't believe you need "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd" bit for F-29 but I don't have a device to test.
I tested the LED part with rawhide packages on my F29 x86_64 * arm-image-installer-2.10-1.fc29.noarch * uboot-images-armv7-2019.01-1.fc30.noarch * kernel-4.18.16-300.fc29.armv7hl
The board boots fine, no need to symlink. As long as I have `cpuidle.off=1` (without it the board gets stuck during boot)
I do need both `rd.driver.pre=ledtrig-heartbeat` and preloading with
cat <<EOF >>/etc/dracut.conf.d/ledtrig-heartbeat.conf add_drivers+=" ledtrig-heartbeat " EOF
To get heartbeat LED functionality, after re-doing initramfs LED shows alive from early in boot process on, exactly what I need at the moment.
I still need to check if rd.driver.pre=xhci-plat-hcd is needed. At the moment the board has no disk connected, only µSD card
Exact command used; sudo fedora-arm-image-installer \ --target=none \ --image=Fedora-Minimal-armhfp-29-1.2-sda.raw.xz \ --addkey=/home/pcfe/.ssh/id_USBkey.pub \ --args "console=ttySAC2,115200n8 cpuidle.off=1 rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd no_bL_switcher" \ --media=/dev/sdi
I still need to check if rd.driver.pre=xhci-plat-hcd is needed.
Seems so;
booting with `rd.driver.pre=xhci-plat-hcd` I get Driver=r8152, 5000M
```bash [root@odroid-hc2-00 ~]# cat /proc/cmdline console=ttySAC2,115200n8 cpuidle.off=1 rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd no_bL_switcher ro root=UUID=2161061e-8612-4e18-a4e1-0e95aca6d2ff LANG=en_US.UTF-8 [root@odroid-hc2-00 ~]# lsusb -t /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=exynos-ohci/3p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=exynos-ehci/3p, 480M ```
dropping the option, I get Driver=r8152, 480M
```bash [root@odroid-hc2-00 ~]# cat /proc/cmdline console=ttySAC2,115200n8 cpuidle.off=1 rd.driver.pre=ledtrig-heartbeat no_bL_switcher ro root=UUID=2161061e-8612-4e18-a4e1-0e95aca6d2ff LANG=en_US.UTF-8 [root@odroid-hc2-00 ~]# lsusb -t /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 480M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=exynos-ehci/3p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=exynos-ohci/3p, 12M ```
On Mon, Jan 28, 2019 at 5:18 PM Patrick Charles François Ernzer pcfe@redhat.com wrote:
I still need to check if rd.driver.pre=xhci-plat-hcd is needed.
Seems so;
There's some discussion of this on the upstream USB mailing list: https://www.spinics.net/lists/linux-usb/msg176210.html
I think this is also related: https://www.spinics.net/lists/linux-usb/msg176223.html
booting with `rd.driver.pre=xhci-plat-hcd` I get Driver=r8152, 5000M
[root@odroid-hc2-00 ~]# cat /proc/cmdline console=ttySAC2,115200n8 cpuidle.off=1 rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd no_bL_switcher ro root=UUID=2161061e-8612-4e18-a4e1-0e95aca6d2ff LANG=en_US.UTF-8 [root@odroid-hc2-00 ~]# lsusb -t /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=exynos-ohci/3p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=exynos-ehci/3p, 480Mdropping the option, I get Driver=r8152, 480M
[root@odroid-hc2-00 ~]# cat /proc/cmdline console=ttySAC2,115200n8 cpuidle.off=1 rd.driver.pre=ledtrig-heartbeat no_bL_switcher ro root=UUID=2161061e-8612-4e18-a4e1-0e95aca6d2ff LANG=en_US.UTF-8 [root@odroid-hc2-00 ~]# lsusb -t /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 480M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=exynos-ehci/3p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=exynos-ohci/3p, 12M
arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
On Mon, Jan 28, 2019 at 5:18 PM Patrick Charles François Ernzer <pcfe(a)redhat.com> wrote:
There's some discussion of this on the upstream USB mailing list: https://www.spinics.net/lists/linux-usb/msg176210.html
I think this is also related: https://www.spinics.net/lists/linux-usb/msg176223.html
Yes. While I can live with adding 'xhci-plat-hcd', another annoyance is that on some of the reboots the bard boots fine but fails to initialise the network device: Bus 006 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
dmesg in that state at https://paste.fedoraproject.org/paste/zOqTsC8EiWsRaM2DTQojJA lsusb in that state at https://paste.fedoraproject.org/paste/Iq-ZBtl29GG9xvtVD2~Ijw
I'm happy to provide more logs is needed, I've just wired up 2 serial consoles permanently, that makes life easier.
FWIW: when the ODROID is in this state of not having access to the network, clean reboots issued via serial console end up in the same disconnected state. (I've tried 3 consecutive reboots just now).
Additionally, I have the hardware watchdog set up and when I forcefully crash a system in this state with [root@localhost ~]# echo '1' > /proc/sys/kernel/sysrq [root@localhost ~]# echo 'c' > /proc/sysrq-trigger Network remains unreachable after the reboot triggered by the watchdog (also tested 3 times in a row)
Power cycling the ODOID has, so far, always resolved the issue.
pcfe
Just tested with Kernel 5.0.1-300.fc29.armv7hl, same problem, out of 3 reboots one did not manage to initialise network.
The kernel tried to power cycle the port;
[ 19.429292] xhci-hcd xhci-hcd.1.auto: Timeout while waiting for setup device command [ 19.637128] usb 6-1: device not accepting address 2, error -62 [...] [ 30.901110] usb 6-1: device not accepting address 3, error -62 [ 30.927259] usb usb6-port1: attempt power cycle (full boot logs can be provided if needed, but that did not bring the device up. From that state the only way to fix it was a power cycle of the whole ODROID-HC2.
pcfe
Just tested with Kernel 5.0.1-300.fc29.armv7hl, same problem, out of 3 reboots one did not manage to initialise network.
So one of the patches I referenced above, "usb: dwc3: exynos: Fix error handling of clk_prepare_enable" is in 5.0 and just landed in 4.20.16, the other problem is basically summarised in the following post
https://www.spinics.net/lists/linux-usb/msg177861.html
But should be mitigatable with "rd.driver.pre=xhci-plat-hcd "
The kernel tried to power cycle the port;
[ 19.429292] xhci-hcd xhci-hcd.1.auto: Timeout while waiting for setup device command [ 19.637128] usb 6-1: device not accepting address 2, error -62 [...] [ 30.901110] usb 6-1: device not accepting address 3, error -62 [ 30.927259] usb usb6-port1: attempt power cycle (full boot logs can be provided if needed, but that did not bring the device up. From that state the only way to fix it was a power cycle of the whole ODROID-HC2.
pcfe _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
On Thu, 14 Mar 2019 18:16:32 +0000 Peter Robinson pbrobinson@gmail.com wrote:
Just tested with Kernel 5.0.1-300.fc29.armv7hl, same problem, out of 3 reboots one did not manage to initialise network.
So one of the patches I referenced above, "usb: dwc3: exynos: Fix error handling of clk_prepare_enable" is in 5.0 and just landed in 4.20.16, the other problem is basically summarised in the following post
https://www.spinics.net/lists/linux-usb/msg177861.html
But should be mitigatable with "rd.driver.pre=xhci-plat-hcd "
Sadly not, I boot with rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd (because I want the 5000M mode).
One thing to note, since my initial testing I've switched from the HK power bricks to HK's ODROID power cable wired to a single 12V/20A bench supply. https://blog.pcfe.net/hugo/posts/2019-03-05-odroid-hc2-ceph-cluster/#notes-o...
While I'm confident in the power setup up to the HK power cable itself and have measured voltage under load up to the power distributors, I have not measured yet on the PCB, my current voltmeter leads are a tad too. The HK power cable seems a wee bit too much on the thin side for my taste.
If you want I can re-test 5.0.1-300.fc29.armv7hl with one of HK's power bricks.
In case you want it, I've dumped the console log at https://blog.pcfe.net/tmp/ once as generated by conserver(8), and once after running through strings(1) as I found the control codes annoying when trying to view in a browser ;-)
Until I lost network connectivity, I triggered the reboots by ssh-ing in.
lines 0020 to 0220 is the shutdown of the first systemctl reboot via ssh lines 0221 to 1348 is the system coming up fine and going down after I triggered again a clean reboot lines 1349 to 2462 same again
At line 2464 the boot where I had no network starts. At line 3174 of that boot I get the first Timeout while waiting for setup device command
At line 3459 I trigger a clean reboot via serial
lines 3487 to 4446 the system boots but again the USB network fails to init.
lines 4464 to end is a boot triggerd via watchdog, not helping either.
As before removing power fixed the issue.
Anything else I can test for you?
pcfe
-
Dennis Gilmore -
Patrick C. F. Ernzer -
Patrick Charles François Ernzer
-
Patrick Charles François Ernzer -
Peter Robinson -
Robert Moskowitz -
Torbjorn Jansson