Am 2017-07-19 15:01, schrieb Peter Robinson:
On Wed, Jul 19, 2017 at 1:29 PM, <arm_ml@xxxxxxxxxxx> wrote:
Am 2017-07-18 17:11, schrieb Peter Robinson:
On Tue, Jul 18, 2017 at 2:55 PM, Andreas Reschke <arm_ml@xxxxxxxxxxx>
wrote:
Am 17.07.2017 um 14:33 schrieb Peter Robinson:
On Mon, Jul 17, 2017 at 12:18 PM, <arm_ml@xxxxxxxxxxx> wrote:
Hi there,
I've two XU4: one with Fedora25 and handmade Kernel 4.2.0+ #1
(based on
Odroid image) and one with native Fedora 24 with kernel 4.7.2-201.
Update to newer kernel didn't work because it doesn't build a
suitable
initramfs.
Has anybody tried this?
That should be fixed in F-26, might be easiest to deploy a new
image,
else you could do the upgrade process and that *should* work, but
the
upgrade on those devices is untested.
Peter
Hello Peter,
steps I've done:
1. dnf upgrade --refresh
some Packages are installed, no kernel, System is on 4.6.5-300.fc24
2. dnf system-upgrade download --releasever=26
961 Packages are downloaded, no kernel Package
Have you explcitly excluded the kernel in some dnf/yum config?
3. dnf system-upgrade reboot
Error: system is not ready for upgrade
Whats next ?
Andreas
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
Hello Peter,
you're right: I've exluded the kernel in dnf.conf. Knocking my head on
table
...
Now the board is running FC26 but still with the old
4.6.5-300.fc24.armv7hl
kernel. The 4.11.10-300.fc26 kernel was installed, but no initramfs
was
created in /boot. That means a boot with this kernel is not working.
extlinux.conf:
label Fedora (4.11.10-300.fc26.armv7hl) 26 (Twenty Six)
kernel /vmlinuz-4.11.10-300.fc26.armv7hl
append
rd.driver.pre=dw_mmc-exynos,exynosdrm,ehci-exynos,ohci-exynos ro
root=UUID=dfac3a15-7d31-46ed-842f-2f7599871202 LANG=de_DE.UTF-8
enforcing=1
fdtdir /dtb-4.11.10-300.fc26.armv7hl/
initrd -> is missing
Remove all the rd.driver crap, you also shouldn't need any enforcing=
line
It creates the initrd line from previous ones, did your 4.6.5 kernel
not have that line?
[root@myodroid ~]# cat /boot/extlinux/extlinux.conf
# extlinux.conf generated by appliance-creator
ui menu.c32
menu autoboot Welcome to Fedora-Mate-armhfp-24-1.2. Automatic boot in #
second{,s}. Press a key for options.
menu title Fedora-Mate-armhfp-24-1.2 Boot Options.
menu hidden
timeout 20
totaltimeout 600
default=Fedora (4.6.5-300.fc24.armv7hl) 24 (Twenty Four)
#label Fedora (4.11.10-300.fc26.armv7hl) 26 (Twenty Six)
# kernel /vmlinuz-4.11.10-300.fc26.armv7hl
# append
rd.driver.pre=dw_mmc-exynos,exynosdrm,ehci-exynos,ohci-exynos ro
root=UUID=dfac3a15-7d31-46ed-842f-2f7599871202 LANG=de_DE.UTF-8
enforcing=1
# fdtdir /dtb-4.11.10-300.fc26.armv7hl/
label Fedora (4.6.5-300.fc24.armv7hl) 24 (Twenty Four)
kernel /vmlinuz-4.6.5-300.fc24.armv7hl
append
rd.driver.pre=dw_mmc-exynos,exynosdrm,ehci-exynos,ohci-exynos ro
root=UUID=dfac3a15-7d31-46ed-842f-2f7599871202 LANG=de_DE.UTF-8
enforcing=1
fdtdir /dtb-4.6.5-300.fc24.armv7hl/
initrd /initramfs-4.6.5-300.fc24.armv7hl.img
[root@myodroid ~]#
Check /boot/ for an appropriate initrd, check to see if the mmc
drivers are in there using "lsinitrd <initrd> | grep mmc", if you
don't see them there (sometimes transitioning from weird hacked
kernels dracut gets the module list wrong) you can regenerate a
generic initrd with the following command:
"dracut -N -f /boot/initramfs-4.11.10-300.fc26.armv7hl.img
4.11.10-300.fc26.armv7hl"
While creating the initrd system crashed with a reboot. Maybe I need a
power supply with more power then USB3.
Then add the initrd line to exiting entry in extlinux.conf
initrd /initramfs-4.11.10-300.fc26.armv7hl.img
From then on dracut should get the host specific initrd correct after a
reboot.
I want to build with this board (Odroid xu4) with the new Cloudshell 2
(http://www.hardkernel.com/main/products/prdt_info.php?g_code=G149142327280)
a Nextcloud Storage.
Does Fedora with kernel 4.11 support USB Attached SCSI (UAS or UASP)
and USB
3.0 to SATA bridge (JMicron JMS561) ?
It should as UAS is a usb standard that is supported in the kernel, as
for specific controller details no idea, sorry I don't track that
stuff as I don't particularly care, but why don't you try it and see
for yourself ;-)
Okay, after I get FC26 running with actual kernel I by this case and
write a report.
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
