On Wed, Jul 19, 2017 at 1:29 PM, <arm_ml(a)rirasoft.de> wrote:
Am 2017-07-18 17:11, schrieb Peter Robinson:
> On Tue, Jul 18, 2017 at 2:55 PM, Andreas Reschke <arm_ml(a)rirasoft.de>
>> Am 17.07.2017 um 14:33 schrieb Peter Robinson:
>>> On Mon, Jul 17, 2017 at 12:18 PM, <arm_ml(a)rirasoft.de> wrote:
>>>> Hi there,
>>>> I've two XU4: one with Fedora25 and handmade Kernel 4.2.0+ #1 (based
>>>> 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
>>>> 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.
>> 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 ?
>> arm mailing list -- arm(a)lists.fedoraproject.org
>> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
> arm mailing list -- arm(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
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.
label Fedora (4.11.10-300.fc26.armv7hl) 26 (Twenty Six)
root=UUID=dfac3a15-7d31-46ed-842f-2f7599871202 LANG=de_DE.UTF-8 enforcing=1
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?
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
Then add the initrd line to exiting entry in extlinux.conf
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
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 ;-)