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.