[fedora-arm] Re: Fedora on Rock 5B

[arm_ml]

Am 2023-07-30 15:26, schrieb Peter Robinson:

Hi,

It's in my backlog of devices to play with for F-39.

It looks like it's not finding the storage, you don't mention what
sort of storage you're trying to run Fedora from, is it the SD card or
do you have the firmware on SD and Fedora on something else?

Peter


Hello Peter,
UEFI is on SD-Card, Fedora iso is on USB-Stick, another empty USB-Stick 
and NVME disc are available for storage.


On Sun, 30 Jul 2023, 13:18 Andreas Reschke, 
wrote:


Hi there,
I've tried to install Fedora on my Rock 5 without success.

Booting with


https://github.com/edk2-porting/edk2-rk3588/releases/download/v0.7.1/rock-5b_UEFI_Release_v0.7.1.img


on SD-Card and source from


https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/aarch64/iso/Fedora-Everything-netinst-aarch64-Rawhide-20230730.n.0.iso.


Board boots up fine but later starting in loop with
350.456154] dracut-initqueue[1065]: Warning: # Anaconda
installer errors end ###
[  352.156835] dracut-initqueue[1065]: Warning: dracut-initqueue:
timeout, still waiting for following initqueue hooks:
[  352.161387] dracut-initqueue[1065]: Warning:
/lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2froot.sh:
"[ -e
"/dev/root" ]"
[  352.164564] dracut-initqueue[1065]: Warning:
/lib/dracut/hooks/initqueue/finished/wait_for_disks.sh: "[
"$main_loop"
-ge "10" ]"
[  352.167716] dracut-initqueue[1065]: Warning:
/lib/dracut/hooks/initqueue/finished/wait_for_settle.sh: "[ -f
/tmp/settle.done ]"
[  352.171999] dracut-initqueue[1065]: Warning: dracut-initqueue:
starting timeout scripts
[  352.172610] dracut-initqueue[1065]: Warning: #
Anaconda
installer errors begin #
[  352.172852] dracut-initqueue[1065]: Warning: #
#
[  352.173097] dracut-initqueue[1065]: Warning: It seems that the
boot
has failed. Possible causes include
[  352.173296] dracut-initqueue[1065]: Warning: missing inst.stage2
or
inst.repo boot parameters on the
[  352.173537] dracut-initqueue[1065]: Warning: kernel cmdline.
Please
verify that you have specified
[  352.173731] dracut-initqueue[1065]: Warning: inst.stage2 or
inst.repo.
[  352.173918] dracut-initqueue[1065]: Warning: Please also note
that
the 'inst.' prefix is now mandatory.
[  352.174156] dracut-initqueue[1065]: Warning: #
#
[  352.174354] dracut-initqueue[1065]: Warning:  Installer
errors encountered during boot: 
[  352.174543] dracut-initqueue[1065]: Warning: #
#
[  352.174775] dracut-initqueue[1065]: Warning: Reason unknown
[  352.174970] dracut-initqueue[1065]: Warning: #
#

Full log file: see rock.txt

Has anybody more succcess ?

Greetings
Andreas___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:


https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org

Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue

___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[fedora-arm] Rspamd Package for Fedora 30 armhfp

[arm_ml]

Hello together,

I'm in the process to build up a new mailserver.

Old one: Odroid HC1 with CentOS 7; postfix with postscreen, amavis-new, 
spamassassin, clamav, dovecot < runs smoothly nearly 2 years.


New One: Odroid HC1 with Fedora 30; postfix, dovecot, rspamd? < should 
be state-of-the-art.


I can't find any package for rspamd for armhfp, neither Fedora or 
https://rspamd.com/downloads.html. I only found x86_64.


Greetings
Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org

[fedora-arm] Re: Helios 4 with Fedora

[arm_ml]

Am 2019-01-03 15:17, schrieb Dennis Gilmore:

El jue, 03-01-2019 a las 08:57 +0100, arm...@rirasoft.de escribió:

Hello together and and happy and healthfull new year !

Yesterday the parcel with Helios 4 is be well received. Is there any
hint to install Fedora (or maybe CentOS) on it?

Greetings
Andreas


Hi Andreas,

fedora works well on the helios4, it can however only control one of
the two fansright now due to the upstream kernel only supporting one
pwm device on a GPIO bank and both fans are on one bank of GPIO pins.

grab the image you prefer to use, minimal or server, I personally am
using server and install uboot-images-armv7 on your local machine.

install the image onto your sdcard where sdX is the device your sdcard
shows up as

xzcat Fedora-Image.xz| dd of=/dev/sdX bs=4MiB

then install u-boot into the card

dd if=/usr/share/uboot/helios4/u-boot-spl.kwb of=/dev/sdX  bs=512
seek=1

you could use gparted to resize the rootfs or just boot and resize on
the system when running.

Then boot the system, if you use server you can then manage the disks
you put into the nas through cockpit.  I am planning to package up the
config file for fan control and a preset to enable fancontrol so you
can install a hardware enablement package to have things just work. I
am also planning on gettinga  u-boot build for the spi flash and
enabling booting from sata. On mine I have moved / to the internal
drives and only have /boot on the sdcard. there is a kernel bug that
causes the lm75 module to not autoload, it is needed for the fancontrol
to work also.

Dennis
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@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



Hello Dennis,

thank you for the installation hint. Next step is creating RAID with 
hardisk. I also want to have / with /var on disk and only /boot on 
SD-Card.

What is your setup?

My QNAP-NAS is
[~] # cat /proc/mdstat
Personalities : [raid1] [linear] [raid0] [raid10] [raid6] [raid5] 
[raid4]

md0 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1]
 8786092608 blocks super 1.0 level 5, 64k chunk, 
algorithm 2 [4/4] []

md4 : active raid1 sdd2[4](S) sdc2[3](S) sdb2[2] sda2[0]
 530128 blocks super 1.0 [2/2] [UU]
md13 : active raid1 sda4[0] sdc4[3] sdd4[2] sdb4[1]
 458880 blocks [4/4] []
 bitmap: 2/57 pages [8KB], 4KB chunk


md9 : active raid1 sda1[0] sdd1[3] sdc1[2] sdb1[1]
 530048 blocks [4/4] []
 bitmap: 1/65 pages [4KB], 4KB chunk


unused devices: 
[~] #

I think I create
/dev/md0 = RAID 1 for OS /
/dev/md1 = RAID 1 for OS /var
/dev/md2 = RAID 5 big filesystem

First test with 4 disk with 1 TB

I will test if this work.

Greetings
Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@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

[fedora-arm] Helios 4 with Fedora

[arm_ml]

Hello together and and happy and healthfull new year !

Yesterday the parcel with Helios 4 is be well received. Is there any 
hint to install Fedora (or maybe CentOS) on it?


Greetings
Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@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

[fedora-arm] Re: F28 on odroid XU4

[arm_ml]

Am 2018-08-27 10:41, schrieb Vince Geze:
---snip---


Hello Vince,
after newest kernel update and poweroff for 1 minute:

[root@odroidh2 ~]# 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
 |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 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
[root@odroidh2 ~]# uname -a
Linux odroidh2.reschke.lan 4.17.17-200.fc28.armv7hl #1 SMP Mon Aug 20
17:31:32 UTC 2018 armv7l armv7l armv7l GNU/Linux
[root@odroidh2 ~]#

Greetings
Andreas


Hi Andreas,

Thanks for the feedback, looks like both storage and Ethernet are
connected as USB3 now.
Out of curiosity, are you running from SD or eMMC? I'm still using SD
for testing, but once I got everything covered I'd like to switch to
eMMC.

Best regards,

Vince


Hello Vince,
this system is running only with /boot from SD, all other filesystems 
are on SSD.


I will now update my Odroid XU4, this should also work. I hope, I can 
take this in the near future as my working place.


Greetings
Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@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

[fedora-arm] Re: F28 on odroid XU4

[arm_ml]

Am 2018-08-24 14:37, schrieb Vince Geze:

-Original Message-
From: arm...@rirasoft.de [mailto:arm...@rirasoft.de]
Sent: Friday, August 24, 2018 2:27 PM
To: Vince Geze 
Cc: arm@lists.fedoraproject.org
Subject: Re: [fedora-arm] Re: F28 on odroid XU4

Am 2018-08-24 14:17, schrieb Vince Geze:
>> -Original Message-
>> From: arm...@rirasoft.de [mailto:arm...@rirasoft.de]
>> Sent: Friday, August 24, 2018 1:39 PM
>> To: Vince Geze 
>> Cc: arm@lists.fedoraproject.org
>> Subject: Re: [fedora-arm] Re: F28 on odroid XU4
>>
>> Am 2018-08-24 12:09, schrieb Vince Geze:
>> --snip--
>> >
>> > Well, after countless reboots it seems to be even more simple.
>> > - USB3: preloading xhci-plat-hcd, which already is in the
>> > initramfs, is sufficient to get proper USB3 operation and the r8152
>> > at full speed as well
>> > - CPU HMP: this one I already knew was linked to the
>> > CONFIG_BL_SWITCHER. On [1] it is mentioned there are both sysfs and
>> > kernel boot options to control this behavior. The sysfs path exists
>> > and with lscpu you can see all 8 cores being put online. The kernel
>> > boot command however turned out to be incorrect, but after some
>> > digging I found you only need "no_bL_switcher" as boot option.
>> >
>> > Since the board will be used headless, I also enabled the blinking
>> > led by preloading ledtrig-heartbeat, but this needs to be included
>> > in a /etc/dracut.conf.d/ conf file with 'add_drivers+="
>> > ledtrig-heartbeat "'. The blinking frequency also gives an indication

of

the load.
>> >
>> > The final boot line now looks like this:
>> > append ro rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd
>> > root=UUID=your_UUID cpuidle.off=1 no_bL_switcher console=tty1
>> > console=ttySAC2,115200n8
>> >
>> > Result:
>> > - systematically correct detection of USB3
>> > - performance improvement by enabling all cpus
>> > - indication whether the system is alive or not
>> > - no need for recompiling kernels, only boot time options and an
>> > optional dracut inclusion
>> >
>> > Best regards,
>> >
>> > Vince
>> >
>> > [1]
>> > https://wiki.linaro.org/projects/big.LITTLE.MP/Big.Little.Switcher/
>> > Doc
>> > s/porting-guide
>> ___
>> > arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send
>> > an email to arm-le...@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/message/Y7EMT5B5HYSV3SX533YZZHOOEOMRHNFZ/
>>
>> Hello Vince,
>>
>> I must say thank you !
>>
>> With your work I can enable all 8 CPUs on my Odroid HC1.
>>
>> lscpu before:
>> [root@odroidh1 ~]# lscpu
>> Architektur:   armv7l
>> Byte-Reihenfolge:  Little Endian
>> CPU(s):8
>> Liste der Online-CPU(s):   0-3
>> Liste der Offline-CPU(s):  4-7
>> Thread(s) pro Kern:1
>> Kern(e) pro Socket:4
>> Sockel:1
>>
>> lscpu after:
>> Architektur:   armv7l
>> Byte-Reihenfolge:  Little Endian
>> CPU(s):8
>> Liste der Online-CPU(s):   0-7
>> Thread(s) pro Kern:1
>> Kern(e) pro Socket:4
>> Sockel:2
>>
>> Greetings
>> Andreas
>
> Hi Andreas,
>
> Glad to hear it's working on your side as well. Could you also check
> the number at the end of the r8152 line in lsusb -t with the default
> boot line without preloads? Is it 480M or 5000M?
>
> Best regards,
>
> Vince

System without your modifikation:

[root@odroidh1 ~]# 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
 |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 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
[root@odroidh1 ~]#

System with your modifikation:

[root@odroidh2 ~]# 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
 |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 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
[root@odroidh2 ~]#

Systems are identical: Odroid HC1 with 

[fedora-arm] Re: F28 on odroid XU4

[arm_ml]

Am 2018-08-24 14:17, schrieb Vince Geze:

-Original Message-
From: arm...@rirasoft.de [mailto:arm...@rirasoft.de]
Sent: Friday, August 24, 2018 1:39 PM
To: Vince Geze 
Cc: arm@lists.fedoraproject.org
Subject: Re: [fedora-arm] Re: F28 on odroid XU4

Am 2018-08-24 12:09, schrieb Vince Geze:
--snip--
>
> Well, after countless reboots it seems to be even more simple.
> - USB3: preloading xhci-plat-hcd, which already is in the initramfs,
> is sufficient to get proper USB3 operation and the r8152 at full speed
> as well
> - CPU HMP: this one I already knew was linked to the
> CONFIG_BL_SWITCHER. On [1] it is mentioned there are both sysfs and
> kernel boot options to control this behavior. The sysfs path exists
> and with lscpu you can see all 8 cores being put online. The kernel
> boot command however turned out to be incorrect, but after some
> digging I found you only need "no_bL_switcher" as boot option.
>
> Since the board will be used headless, I also enabled the blinking led
> by preloading ledtrig-heartbeat, but this needs to be included in a
> /etc/dracut.conf.d/ conf file with 'add_drivers+=" ledtrig-heartbeat
> "'. The blinking frequency also gives an indication of the load.
>
> The final boot line now looks like this:
> append ro rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd
> root=UUID=your_UUID cpuidle.off=1 no_bL_switcher console=tty1
> console=ttySAC2,115200n8
>
> Result:
> - systematically correct detection of USB3
> - performance improvement by enabling all cpus
> - indication whether the system is alive or not
> - no need for recompiling kernels, only boot time options and an
> optional dracut inclusion
>
> Best regards,
>
> Vince
>
> [1]
> https://wiki.linaro.org/projects/big.LITTLE.MP/Big.Little.Switcher/Doc
> s/porting-guide
___
> arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an
> email to arm-le...@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/message/Y7EMT5B5HYSV3SX533YZZHOOEOMRHNFZ/

Hello Vince,

I must say thank you !

With your work I can enable all 8 CPUs on my Odroid HC1.

lscpu before:
[root@odroidh1 ~]# lscpu
Architektur:   armv7l
Byte-Reihenfolge:  Little Endian
CPU(s):8
Liste der Online-CPU(s):   0-3
Liste der Offline-CPU(s):  4-7
Thread(s) pro Kern:1
Kern(e) pro Socket:4
Sockel:1

lscpu after:
Architektur:   armv7l
Byte-Reihenfolge:  Little Endian
CPU(s):8
Liste der Online-CPU(s):   0-7
Thread(s) pro Kern:1
Kern(e) pro Socket:4
Sockel:2

Greetings
Andreas


Hi Andreas,

Glad to hear it's working on your side as well. Could you also check 
the
number at the end of the r8152 line in lsusb -t with the default boot 
line

without preloads? Is it 480M or 5000M?

Best regards,

Vince


System without your modifikation:

[root@odroidh1 ~]# 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
|__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 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
[root@odroidh1 ~]#

System with your modifikation:

[root@odroidh2 ~]# 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
|__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 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
[root@odroidh2 ~]#

Systems are identical: Odroid HC1 with update Fedora 28

Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@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/message/75FYHT4M7VFAD66JHUIZK5C3QSTV2DXQ/

[fedora-arm] Re: F28 on odroid XU4

[arm_ml]

Am 2018-08-24 12:09, schrieb Vince Geze:
--snip--


Well, after countless reboots it seems to be even more simple.
- USB3: preloading xhci-plat-hcd, which already is in the initramfs,
is sufficient to get proper USB3 operation and the r8152 at full speed
as well
- CPU HMP: this one I already knew was linked to the
CONFIG_BL_SWITCHER. On [1] it is mentioned there are both sysfs and
kernel boot options to control this behavior. The sysfs path exists
and with lscpu you can see all 8 cores being put online. The kernel
boot command however turned out to be incorrect, but after some
digging I found you only need "no_bL_switcher" as boot option.

Since the board will be used headless, I also enabled the blinking led
by preloading ledtrig-heartbeat, but this needs to be included in a
/etc/dracut.conf.d/ conf file with 'add_drivers+=" ledtrig-heartbeat
"'. The blinking frequency also gives an indication of the load.

The final boot line now looks like this:
append ro rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd
root=UUID=your_UUID cpuidle.off=1 no_bL_switcher console=tty1
console=ttySAC2,115200n8

Result:
- systematically correct detection of USB3
- performance improvement by enabling all cpus
- indication whether the system is alive or not
- no need for recompiling kernels, only boot time options and an
optional dracut inclusion

Best regards,

Vince

[1]
https://wiki.linaro.org/projects/big.LITTLE.MP/Big.Little.Switcher/Docs/porting-guide
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@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/message/Y7EMT5B5HYSV3SX533YZZHOOEOMRHNFZ/


Hello Vince,

I must say thank you !

With your work I can enable all 8 CPUs on my Odroid HC1.

lscpu before:
[root@odroidh1 ~]# lscpu
Architektur:   armv7l
Byte-Reihenfolge:  Little Endian
CPU(s):8
Liste der Online-CPU(s):   0-3
Liste der Offline-CPU(s):  4-7
Thread(s) pro Kern:1
Kern(e) pro Socket:4
Sockel:1

lscpu after:
Architektur:   armv7l
Byte-Reihenfolge:  Little Endian
CPU(s):8
Liste der Online-CPU(s):   0-7
Thread(s) pro Kern:1
Kern(e) pro Socket:4
Sockel:2

Greetings
Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@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/message/CWFLIDYED7CYWSTIZ54MU2FYNWCHOS3N/

[fedora-arm] Helios4 with Fedora

[arm_ml]

Hello all,

I've a very beautiful OpenSource and openHardware NAS: Helios4 
https://kobol.io/helios4/


It comes with Marvell ARMADA® 388 Dual-core ARM Cortex A9 CPU. Does 
anybody knows, if it runs with Fedora?



Greetings
Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@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/message/CTVMFR5Q33WHTMCBNGHP22AKWSVX7HRK/

[fedora-arm] Re: [Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting

[arm_ml]

Am 2018-06-20 15:42, schrieb Peter Robinson:

On Wed, Jun 20, 2018 at 2:40 PM,   wrote:

Am 2018-06-17 17:00, schrieb pwha...@redhat.com:


Dear all,

You are kindly invited to the meeting:
   Fedora ARM & AArch64 status meeting on 2018-06-19 from 15:00:00 to
16:00:00 UTC
   At fedora-meetin...@irc.freenode.net

The meeting will be about:
Fedora ARM & AArch64 weekly status meeting.

More information available at:

[https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org/wiki/Architectures/ARM)


Source: https://apps.fedoraproject.org/calendar/meeting/9202/

___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@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/message/OU4B4GVVJONNBYLHR462KOZKVHVKNYJK/




In fever days there was a protocol from the meeting afterwards. I'm 
missing

the protocol.


What does this even mean?
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@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/message/ZHBFDTMSEMPBNBK4TUTEY4WULQQUOPYA/



Just a meeting summary like:

fedora-meeting-2: Fedora ARM and AArch64 Status Meeting



Meeting started by pwhalen at 15:00:14 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-2/2018-03-06/fedora_arm_and_aarch64_status_meeting.2018-03-06-15.00.log.html
.



Meeting summary
---
* roll call  (pwhalen, 15:00:14)

* 1)  Userspace Status    (pwhalen, 15:04:29)
  * No issues reported.  (pwhalen, 15:05:41)

* 2)  Kernel Status   (pwhalen, 15:05:55)
  * kernel-4.16.0-0.rc4.git0.1.fc28  (pwhalen, 15:06:03)
  * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1053469
(pwhalen, 15:06:04)
  * Please test and report any issues to the list or #fedora-arm.
(pwhalen, 15:08:15)

* 3)  Bootloader Status   (pwhalen, 15:08:24)
  * uboot-tools-2018.03-0.8.rc3.fc28  (pwhalen, 15:08:33)
  * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1053334
(pwhalen, 15:08:33)

* 4)  == F28 Testing ==  (pwhalen, 15:15:02)
  * Latest test results -

https://fedoraproject.org/wiki/Test_Results:Fedora_28_Branched_20180301.n.1_Summary

(pwhalen, 15:16:19)

* 5) == Open Floor ==  (pwhalen, 15:18:38)
  * Fedora 28 Schedule -
https://fedoraproject.org/wiki/Releases/28/Schedule  (pwhalen,
15:21:08)

Meeting ended at 15:22:15 UTC.
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@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/message/SMIOIZZTDJKATTNC4HBPYJI43CNBW5PV/

[fedora-arm] Re: [Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting

[arm_ml]

Am 2018-06-17 17:00, schrieb pwha...@redhat.com:

Dear all,

You are kindly invited to the meeting:
   Fedora ARM & AArch64 status meeting on 2018-06-19 from 15:00:00 to
16:00:00 UTC
   At fedora-meetin...@irc.freenode.net

The meeting will be about:
Fedora ARM & AArch64 weekly status meeting.

More information available at:
[https://fedoraproject.org/wiki/Architectures/ARM](https://fedoraproject.org/wiki/Architectures/ARM)


Source: https://apps.fedoraproject.org/calendar/meeting/9202/

___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@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/message/OU4B4GVVJONNBYLHR462KOZKVHVKNYJK/



In fever days there was a protocol from the meeting afterwards. I'm 
missing the protocol.


Greetings
Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@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/message/ROWXFVD42O2WDYTWUVWVNKGT224KBNPT/

[fedora-arm] Comments to kernel-4.16.0-300.fc28.armv7hl

[arm_ml]

Hi there,

with actual kernel-4.16.0-300.fc28.armv7hl from Fedora 28 Beta no Xorg 
is working on my Odroid XU4 and the system load is constant at 4 .


Hints:
with kernel-core-4.16.0-0.rc6.git2.1.fc29.armv7hl everything is working 
fine. I can work on Xorg with mate (slow, but it works) an system load 
is nearly 0.


Greetings
Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] My experience with Fedora Rawhide on Odroid XU4 and Odroid H1

[arm_ml]

Hello,

based on research from Stewart Samuels with 
Fedora-Mate-armhfp-Rawhide-20180301.n.0-sda.raw.xz I installed this on 
my both Odroid.


First:
Odroid XU4Q (without fan) + SSD
/boot on SD-Card
/ on SSD

Today I've update the system to the latest updates. Kernel 
4.16.0-0.rc6.git1.1.fc29.armv7hl works for me with X


[root@odroidxu4 ~]# ps ax | grep X
  953 tty1 Ssl+   0:02 /usr/libexec/Xorg -core -noreset :0 -seat 
seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch 
-background none
 2046 ?R  0:00 /usr/bin/perl -XU 
/usr/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl listsessionsroot 
odroidxu4.reschke.lan

 2048 pts/0S+ 0:00 grep --color=auto X
[root@odroidxu4 ~]#

Second:
Odroid H1
/boot on SD-Card
/ on SSD
/var, /mail, /nextcloud with LVM
I removed all graphical applications

Only Kernel 4.16.0-0.rc4.git3.1.fc29.armv7hl is working fine with LVM. 
With all newer Kernel system stopps at rescue modus after initialize 
LVM. Volumegroup and Logical Volume are present, after typing "systemctl 
default" system boots into multiuser.target correct. System is running 
"normal" but with a continoius load from 4 (without any running 
services). This didn't happens with 4.16.0-0.rc4.git3.1.fc29.armv7hl.


This system should work in the near future as a Nextcloud-Server, so I 
need LVM.


Greetings
Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: High load with kernel 4.15 on OdroidH1

[arm_ml]

Am 2018-02-27 12:16, schrieb arm...@rirasoft.de:

Hi there,

I've done a fresh installation of Fedora 27
(Fedora-Server-armhfp-27-1.6-sda.raw.xz) on my Odroid H1. With Kernel
4.13.9-300.fc27.armv7hl from this Image the load after boot is nearly
0 without any service running. After Update to actual kernel
4.15.4-300.fc27.armv7hl the load reach up to 4,12. Is the behavour
normal? No services are running, no other modifications, boot from
SD-Card.
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org


Additional infos:

After setting up LVM on SSD, Fedora didn't boot correct:

[  OK  ] Created slice system-lvm2\x2dpvscan.slice.
[   22.545969] r8152 5-1:1.0 eth0: v1.09.9
[ TIME ] Timed out waiting for device 
dev-mapper-systemvg\x2dvmail.device.

[DEPEND] Dependency failed for /vmail.
[DEPEND] Dependency failed for Local File Systems.
[DEPEND] Depe[  106.116695] kauditd_printk_skb: 2 callbacks suppressed
ndency failed [  106.116705] audit: type=1130 audit(1499868161.345:69): 
pid=1 uid=0 auid=4294967295 ses=4294967295 
subj=system_u:system_r:init_t:s0 msg='unit=iscsi-shutdown comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

for Mark the need to relabel after reboot.
[ TIME ] Timed out waiting for device 
dev-mapper-systemvg\x2dnextcloud.device.

[DEPEND] Dependency failed for /nextcloud_data.
 Starting Preprocess NFS configuration...
[  OK  ] Reached target Network (Pre).
[  OK  ] Reached target Login Prompts.
[  OK  ] Reached target Network.
[  OK  ] Reached target Network is Online.
[  OK  ] Started Logout off all iSCSI sessions on shutdown.
[  OK  ] Reached target Timers.
 Starting Import network configuration from initramfs...
 Starting Rebuild Dynamic Linker Cache...
 Starting Tell Plymouth To Write Out Runtime Data...
 Starting Rebuild Journal Catalog...
[  OK  ] Reached target Sockets.
[  OK  ] Reached target User and Group Name Lookups.
[ TIME ] Timed out waiting for device dev-mapper-systemvg\x2dvar.device.
[DEPEND] Dependency failed for /var

Login incorrect

Give root password for maintenance
(or press Control-D to continue):
[root@localhost ~]# df -h
Filesystem  Size  Used Avail Use% Mounted on
devtmpfs955M 0  955M   0% /dev
tmpfs   997M 0  997M   0% /dev/shm
tmpfs   997M   17M  981M   2% /run
tmpfs   997M 0  997M   0% /sys/fs/cgroup
/dev/sda119G  1.6G   16G   9% /
/dev/mmcblk0p2  457M   97M  347M  22% /boot
/dev/mapper/systemvg-nextcloud  9.8G   37M  9.3G   1% /nextcloud_data
/dev/mapper/systemvg-var9.8G  401M  8.9G   5% /var
/dev/mapper/systemvg-vmail  9.8G   37M  9.3G   1% /vmail
[root@localhost ~]#

Boot Prozess goes on with "systemctl default"

Thanks
Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] High load with kernel 4.15 on OdroidH1

[arm_ml]

Hi there,

I've done a fresh installation of Fedora 27 
(Fedora-Server-armhfp-27-1.6-sda.raw.xz) on my Odroid H1. With Kernel 
4.13.9-300.fc27.armv7hl from this Image the load after boot is nearly 0 
without any service running. After Update to actual kernel 
4.15.4-300.fc27.armv7hl the load reach up to 4,12. Is the behavour 
normal? No services are running, no other modifications, boot from 
SD-Card.

___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Fedora + Odroid-Xu4 Cluoudshell TFT

[arm_ml]

Hello there,
last step on my Odroid-Xu4 is console output on the small display at the 
Cloudshell (Cloudshell features a 2.2“ TFT LCD with a 320×240 
resolution. The display is controlled by the well-known ILI9340 
controller.)


[root@myodroid ~]# uname -a
Linux myodroid 4.15.0-0.rc4.git3.1.fc28.armv7hl #1 SMP Sat Dec 23 
22:10:52 UTC 2017 armv7l armv7l armv7l GNU/Linux (Running with Fedora 
27)

[root@myodroid ~]# fbset -fb /dev/dri/card0

mode "0x-1225101404"
geometry 0 -1225101404 -1225318544 1 0
timings 0 0 0 0 0 0 0
rgba 0/0,3199112836/0,1/0,0/0
endmode

[root@myodroid ~]# fbi -d /dev /dri/card0 -i
using "DejaVu Sans Mono-16", pixelsize=16,67 
file=/usr/share/fonts/dejavu/DejaVuSansMono.ttf

ioctl VT_GETSTATE: Inappropriate ioctl for device (not a linux console?)
[root@myodroid ~]# lsmod | grep drm
tinydrm24576  0
exynosdrm 163840  0
analogix_dp32768  1 exynosdrm
drm_kms_helper155648  3 tinydrm,exynosdrm,analogix_dp
syscopyarea16384  1 drm_kms_helper
sysfillrect16384  1 drm_kms_helper
sysimgblt  16384  1 drm_kms_helper
fb_sys_fops16384  1 drm_kms_helper
drm   376832  5 
tinydrm,exynosdrm,analogix_dp,drm_kms_helper

cec53248  2 exynosdrm,s5p_cec
[root@myodroid ~]#

Is there any howto to get this display working with tinydrm? I didn't 
find anything beside https://github.com/notro/tinydrm/wiki/Tools



Thanks
Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: Summary of Fedora on Odroid XU4

[arm_ml]

Summary for me:

I have to wait that all missing parts, (USB3, cpuidle, ...) are done 
upstream (Kernel) when I want to use Fedora on Odroid XU4 or Odroid HC1 
(I've tested Fedora 27 beta on it ) or I have to use Ubuntu.



Thanks for the clarification of fact by Peter.


I want to provide help to the cummunity where I can.


Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Summary of Fedora on Odroid XU4

[arm_ml]

Summary of Fedora on Odroid XU4

1. with Kernel 4.6.5-300.fc24 system boots without failure, but update 
to newer kernel fails due dracut didn't build suitable intramfs

   https://bugzilla.redhat.com/show_bug.cgi?id=1482825
2. newer kernel works only with "cpuidle.off=1" inserted into the 
"append" kernel line in the /boot/extlinux/extlinux.conf file, but all 
USB3 Hosts failed, no onboard ethernet

3. To boot the system from the eMMC card:
   A. The initramfs image file must be rebuilt.  The simplest way is to:
   a. Boot up using the MicroSD card;
   b. Partition the eMMC card such that partition 1 begins on sector 
3072
  (Default starting sector from fdisk is 2048).  There should be 
4 partitions created;
   c. Mount the Fedora image desired to be installed on the eMMC 
card;
   d. Copy all partition data from the mounted fedora image 
partitions (there are 4 for Fedora 26 ARM images) to the appropriate 
eMMC partitions;
   e. Update the UUID values on what will be the 
/boot/extlinux/extlinux.conf file and /etc/fstab files of the eMMC card;

   f. Assuming the eMMC partitions are mounted as such --
 mount /dev/mmcblk1p4 /mnt
 mount /dev/mmcblk1p2 /mnt/boot
  then perform the following mounts --
 mount -o bind /proc /mnt/proc
 mount -o bind /dev /mnt/dev
 mount -o bind /sys /mnt/sys
   B.  Rebuild the eMMC card's initramfs by executing the following 
command:
   chroot /mnt dracut --add-drivers='pwrseq_emmc mmc_block' 
/boot/initramfs-4.11.8-300.fc26.armv7hl.img   4.11.8-300.fc26.armv7hl

   C.  Flash the boot information in the header of the eMMC card;
   C.  Shutdown the system, then remove the MicroSD card;
   D.  Boot up using the eMMC card.

4.  If the system is to be updated using "dnf update", a new initramfs 
image must again be generated.  This can be done using steps 1f - B. 
above using the new initramfs and kernel images provided by the "dnf 
update".




Note to the developers/maintainers of dracut:
The kernel modules "pwrseq_emmc" and "mmc_block" should be included in 
dracut for the Odroid-XU3 and Odroid-XU4 such that the user need not 
have to execute this procedure each time and update to the system is 
performed.




Is this correct and complete ?

Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: Fedora with Odroid-XU4 and Cloudshell 2

[arm_ml]

Am , schrieb Stewart Samuels:

Hello Andreas,

I've updated the bug report and also provided the process for
installing the eMMC card.  Have you successfully installed F26 on your
eMMC card?

  Stewart

On 08/29/2017 12:27 AM, arm...@rirasoft.de wrote:

Am , schrieb den...@ausil.us:

You can drop a snippet into a config file that will make sure it's
there. Could you please file a bug against dracut and CC me on it.

Dennis


---cut---

Hello Dennis and Stewart,

I've open a bug against dracut: 
https://bugzilla.redhat.com/show_bug.cgi?id=1482825


No update since 18.08.2017

Andreas

___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org



Hello Stewart,

Odroid 1 with Cloudshell (Version 1)
yes, I've a running system with Fedora 26 and kernel 
4.6.5-300.fc24.armv7hl on emmc . All the newer kernel are not working.


Odroid 2 Cloudshell (Version 2)
kernel 4.6.5-300.fc24.armv7hl on SD-Card is working with the onboard 
RAID and USB3


Now I'm changing the 2 3,5" HD with 2" SSD and try to get the newer 
kernel work with a rebuild initramfs.


Greetings
Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: Fedora with Odroid-XU4 and Cloudshell 2

[arm_ml]

Am , schrieb den...@ausil.us:

You can drop a snippet into a config file that will make sure it's
there. Could you please file a bug against dracut and CC me on it.

Dennis


---cut---

Hello Dennis and Stewart,

I've open a bug against dracut: 
https://bugzilla.redhat.com/show_bug.cgi?id=1482825


No update since 18.08.2017

Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: Fedora with Odroid-XU4 and Cloudshell 2

[arm_ml]

Am , schrieb Peter Robinson:
On Thu, Aug 24, 2017 at 1:34 AM, Stewart Samuels  
wrote:
Okay.  I can confirm I can now boot the USB device to completion.  I 
was

also successfully able to upgrade the system using the "dnf -y update"
command and reboot successfully using the newer kernel.  The key was 
NOT to

create a new initramfs image after changing the UUIDs for the root
partition.  As well, the cpuidle.off=1 kernel boot parameter was 
required in

the extlinux.conf file.

I did NOT concatenate the u-boot.bin and u-boot.dtb files.  I just 
flashed
the u-boot.bin with the other files from Hardkernel that Dennis 
specifies

below.

There are two problems I see right off the bat.  First, as Dennis 
mentions,
the USB3 ports do not work.  Second, only 4 of the 8 cpus seem to be 
working

based on a top command.  Even so, the system actually seems pretty
responsive and usable.


What does lscpu show? I suspect being a big.little platform you'll
find that all the CPUs work but it might only run one cluster at a
time, or only power up the second cluster under load. I'm not sure
what the algorithms the cpu frequency drivers use for the exynos
platforms, I suspect it depends on other factors as well such as
thermal temp (the tmon util in kernel-tools might give you insight
there).

I will now attempt to get the system installed on the eMMC card.  I 
will

report on that progress later.


---cut---

I also have a running F26, thanks to Dennis for his tips.

@ Peter
[root@localhost ~]# lscpu
Architecture:  armv7l
Byte Order:Little Endian
CPU(s):8
On-line CPU(s) list:   0-3
Off-line CPU(s) list:  4-7
Thread(s) per core:1
Core(s) per socket:4
Socket(s): 1
Model: 3
Model name:ARMv7 Processor rev 3 (v7l)
BogoMIPS:  48.00
Flags: half thumb fastmult vfp edsp thumbee neon vfpv3 
tls vfpv4 idiva idivt vfpd32 lpae

[root@localhost ~]#

I've compared this system with a running F24 system and load the same 
kernel modules via "modprobe".

Fedora 26
[root@localhost ~]# lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[root@localhost ~]#

Fedora 24
[root@myodroid ~]# lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 003: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 
Gigabit Ethernet Adapter

Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 05e3:0735 Genesys Logic, Inc.
Bus 004 Device 002: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[root@myodroid ~]#

The module "r8152" was manual loaded, but no Ethernet Adapter was found.

Greetings

Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: Fedora with Odroid-XU4 and Cloudshell 2

[arm_ml]

Am , schrieb Stewart Samuels:

Ok.  The u-boot issue was my mistake.  I was trying to use the
/usr/share/uboot/odroid u-boot files instead of the
/usr/share/uboot/odroid-xu3 files.  Now I am getting output to the
serial console and the system begins the boot process as expected.
However, it hangs in the kernel seemingly trying to do something with
the network.  Anyone have any ideas as to what I can try to get past
this?  Following is my serial console output:



U-Boot 2017.05 (Jun 24 2017 - 16:40:39 +) for ODROID-XU3

CPU:   Exynos5422 @ 800 MHz
Model: Odroid XU3 based on EXYNOS5422
Board: Odroid XU3 based on EXYNOS5422
Type:  xu4
DRAM:  2 GiB
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
*** Warning - bad CRC, using default environment

In:serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Hit any key to stop autoboot:  0
mmc_init: -5, time 4
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:2...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
513 bytes read in 15 ms (33.2 KiB/s)
Ignoring unknown command: ui
Ignoring malformed menu command:  autoboot
Ignoring malformed menu command:  hidden
Ignoring unknown command: totaltimeout
Fedora-Mate-armhfp-26-1.5 Boot Options.
1:  Fedora-Mate-armhfp-26-1.5 (4.11.8-300.fc26.armv7hl)
Enter choice: 1:Fedora-Mate-armhfp-26-1.5 
(4.11.8-300.fc26.armv7hl)

Retrieving file: /initramfs-4.11.8-300.fc26.armv7hl.img
55227208 bytes read in 15615 ms (3.4 MiB/s)
Retrieving file: /vmlinuz-4.11.8-300.fc26.armv7hl
6267616 bytes read in 503 ms (11.9 MiB/s)
append: ro root=UUID=01a7a7b0-fb7b-4b87-a2b4-c330daaab202 cma=192MB
Retrieving file: /dtb-4.11.8-300.fc26.armv7hl/exynos5422-odroidxu4.dtb
54941 bytes read in 277 ms (193.4 KiB/s)
Kernel image @ 0x4200 [ 0x00 - 0x5fa2e0 ]
## Flattened Device Tree blob at 4300
   Booting using the fdt blob at 0x4300
   Loading Ramdisk to 4cb54000, end 4348 ... OK
   Loading Device Tree to 4cb43000, end 4cb5369c ... OK

Starting kernel ...

[0.00] Booting Linux on physical CPU 0x100
[0.00] Linux version 4.11.8-300.fc26.armv7hl
(mockbu...@buildvm-armv7-13.arm.fedoraproject.org) (gcc version 7.1.1
20177
[0.00] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), 
cr=10c5387d

[0.00] CPU: div instructions available: patching division code
[0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
instruction cache
[0.00] OF: fdt: Machine model: Hardkernel Odroid XU4
[0.00] Memory policy: Data cache writealloc
[0.00] efi: Getting EFI parameters from FDT:
[0.00] efi: UEFI not found.
[0.00] Reserved memory: created DMA memory pool at 0xbe20,
size 8 MiB
[0.00] OF: reserved mem: initialized node region_mfc_right,
compatible id shared-dma-pool
[0.00] Reserved memory: created DMA memory pool at 0xbbe0,
size 36 MiB
[0.00] OF: reserved mem: initialized node region_mfc_left,
compatible id shared-dma-pool
[0.00] cma: Reserved 192 MiB at 0xafc0
[0.00] Samsung CPU ID: 0xe5422001
[0.00] Running under secure firmware.
[0.00] percpu: Embedded 15 pages/cpu @eede s31628 r8192
d21620 u61440
[0.00] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 505664
[0.00] Kernel command line: ro
root=UUID=01a7a7b0-fb7b-4b87-a2b4-c330daaab202 cma=192MB
[0.00] PID hash table entries: 4096 (order: 2, 16384 bytes)
[0.00] Dentry cache hash table entries: 131072 (order: 7, 
524288 bytes)
[0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 
bytes)

[0.00] Memory: 1744476K/2029568K available (7440K kernel code,
1301K rwdata, 3528K rodata, 2048K init, 518K bss, 88484K)
[0.00] Virtual kernel memory layout:
[0.00] vector  : 0x - 0x1000   (   4 kB)
[0.00] fixmap  : 0xffc0 - 0xfff0   (3072 kB)
[0.00] vmalloc : 0xf080 - 0xff80   ( 240 MB)
[0.00] lowmem  : 0xc000 - 0xf000   ( 768 MB)
[0.00] pkmap   : 0xbfe0 - 0xc000   (   2 MB)
[0.00] modules : 0xbf00 - 0xbfe0   (  14 MB)
[0.00]   .text : 0xc0208000 - 0xc0a4408c   (8433 kB)
[0.00]   .init : 0xc0e0 - 0xc100   (2048 kB)
[0.00]   .data : 0xc100 - 0xc1145584   (1302 kB)
[0.00].bss : 0xc1145584 - 0xc11c7160   ( 519 kB)
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, 
Nodes=1

[0.00] Hierarchical RCU implementation.
[0.00]  Build-time adjustment of leaf fanout to 32.
[0.00]  RCU restricting CPUs from NR_CPUS=32 to nr_cpu_ids=8.
[0.00] RCU: Adjusting geometry for rcu_fanout_leaf=32, 
nr_cpu_ids=8

[0.00] NR_IRQS:16 nr_irqs:16 16
[0.00] GIC: Using split EOI/Deactivate mode
[0.00] GIC physical location is 0x10481000
[0.00] Switching to timer-based delay loop, resolution 

[fedora-arm] Re: Odrouid XU4 with Fedora

[arm_ml]

Am 2017-07-20 19:12, schrieb Andreas Reschke:

Am 19.07.2017 um 19:02 schrieb Andreas Reschke:

Am 19.07.2017 um 18:11 schrieb Peter Robinson:
--- cut ---

Stop at the same line:

U-Boot 2016.05 (May 30 2016 - 20:03:50 +) for ODROID-XU3

CPU:   Exynos5422 @ 800 MHz
Model: Odroid XU3 based on EXYNOS5422
Board: Odroid XU3 based on EXYNOS5422
Type:  xu4
DRAM:  2 GiB
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
*** Warning - bad CRC, using default environment

In:serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
896 bytes read in 12 ms (72.3 KiB/s)
Ignoring unknown command: ui
Ignoring malformed menu command:  autoboot
Ignoring malformed menu command:  hidden
Ignoring unknown command: totaltimeout
Ignoring unknown command: default=Fedora
Fedora-Mate-armhfp-24-1.2 Boot Options.
1:  Fedora (4.11.10-300.fc26.armv7hl) 26 (Twenty Six)
2:  Fedora (4.6.5-300.fc24.armv7hl) 24 (Twenty Four)
Enter choice: 1:Fedora (4.11.10-300.fc26.armv7hl) 26 (Twenty 
Six)

Retrieving file: /initramfs-4.11.10-300.fc26.armv7hl.img
54912569 bytes read in 5169 ms (10.1 MiB/s)
Retrieving file: /vmlinuz-4.11.10-300.fc26.armv7hl
6267464 bytes read in 592 ms (10.1 MiB/s)
append: ro root=UUID=dfac3a15-7d31-46ed-842f-2f7599871202
LANG=en_US.UTF-8 enforcing=1 console=ttySAC2,115200 console=tty0
Retrieving file: 
/dtb-4.11.10-300.fc26.armv7hl/exynos5422-odroidxu4.dtb

54941 bytes read in 895 ms (59.6 KiB/s)
Kernel image @ 0x4200 [ 0x00 - 0x5fa248 ]
## Flattened Device Tree blob at 4300
   Booting using the fdt blob at 0x4300
   Loading Ramdisk to 4cba1000, end 4639 ... OK
   Loading Device Tree to 4cb9, end 4cba069c ... OK

Starting kernel ...
..

[6.013567] NET: Registered protocol family 10

Fan is running, no more output




Peter

Any tipps and tricks?

Even with kernel 4.11.11-300.fc26.armv7hl isn't working.

Thanks
Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Fedora with Odroid-XU4 and Cloudshell 2

[arm_ml]

Hi there,

I've managed to get Fedora 26 run with kernel 4.6.5-300.fc24.armv7hl on 
Odroid-XU4 with Cloudshell 2. The onbord RAID 1 (USB-Attached SCSI 
(UAS)) is working with kernel 4.6.5-300.fc24.



[root@myodroid ~]# lsusb -d 152d:0561
Bus 004 Device 003: ID 152d:0561 JMicron Technology Corp. / JMicron USA 
Technology Corp.

[root@myodroid ~]#

Next steps to do:

- move OS from SD-Card to more faster eMMC-Card. How to do it?
- Kernel update to actual version. I've update Kernel to 
4.11.11-300.fc26 and system boots with 8 CPU (FC24 = 5 CPU), but only 
the first part of kernel is booting; then it stops.

- compiling modules to activate the color LCD

Is there anybody who can help me with the first 2 steps ?


Thanks
Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: Odrouid XU4 with Fedora

[arm_ml]

Am 2017-07-19 15:01, schrieb Peter Robinson:

On Wed, Jul 19, 2017 at 1:29 PM,   wrote:

Am 2017-07-18 17:11, schrieb Peter Robinson:


On Tue, Jul 18, 2017 at 2:55 PM, Andreas Reschke 
wrote:


Am 17.07.2017 um 14:33 schrieb Peter Robinson:


On Mon, Jul 17, 2017 at 12:18 PM,   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@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org


___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org




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  | 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@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an 

[fedora-arm] Re: Odrouid XU4 with Fedora

[arm_ml]

Am 2017-07-18 17:11, schrieb Peter Robinson:
On Tue, Jul 18, 2017 at 2:55 PM, Andreas Reschke  
wrote:

Am 17.07.2017 um 14:33 schrieb Peter Robinson:

On Mon, Jul 17, 2017 at 12:18 PM,   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@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org



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


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) ?

___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Odrouid XU4 with Fedora

[arm_ml]

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?

Thanks
Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: Fedora-arm-installer

[arm_ml]

Am 2016-12-08 17:37, schrieb Mickey:

Fedora 21
I installed dnf install -y fedora-arm-installer but when i run
arm-image-installer, it can't find the command.
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org


Hello Mickey,
rpm -ql fedora-arm-installer.noarch | grep bin
/usr/bin/arm-image-installer
/usr/bin/create-install-media
/usr/bin/fedora-arm-image-installer
/usr/bin/update-uboot

BTW: Fedora 21 is end of life and unsupported.

Greetings
Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Upgrade Fedora 23 to Fedora 24 on cubietruck

[arm_ml]

Hi there,

I've running a Cubetruck with Fedora 23 as a SOHO-server for a long 
time. Only the U-boot is on a small SD-Card, all filesystens are located 
on a SSD-Disc attached on the SATA.


It is possible to upgrade to Fedora 24 as a "normal" PC with "dnf 
install dnf-plugin-system-upgrade; dnf system-upgrade download 
--releasever=24" ?



Greetings
Andreas
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: The latest upgrade to 4.7.2-201.fc24.armv7hl fails to boot on Odroid XU4.

[arm_ml]

Am 2016-09-08 13:51, schrieb Stewart Samuels:

Dracut fails to build a bootable image for Odroid XU4 for the
4.7.2-201 fc24 initramfs.
it seems that Dracut fails to create the Early CPIO image it needs to
boot the system.



I can confirm this behavior. After the Update and building a new intrd, 
the Odroid didn't boot.


Greetings
Andreas
___
arm mailing list
arm@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org

[fedora-arm] Any updates on Cubietruck Plus?

[arm_ml]

Hi there,

I've tested the newst Rawhide Image 
(Fedora-Minimal-armhfp-Rawhide-20160906.n.0-sda.raw.xz) with 
fedora-arm-image-installer-1.99.11. The rootfilesystem isn't mounted.


U-Boot SPL 2016.09-rc2 (Aug 23 2016 - 14:07:46)
DRAM: 2048 MiB
Trying to boot from MMC1


U-Boot 2016.09-rc2 (Aug 23 2016 - 14:07:46 +) Allwinner Technology

CPU:   Allwinner A83T (SUN8I 1673)
Model: Cubietech Cubietruck Plus
I2C:   ready
DRAM:  2 GiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:serial
Out:   serial
Err:   serial
Net:   No ethernet found.
starting USB...
USB0:   USB EHCI 1.00
USB1:   USB EHCI 1.00
USB2:   A charger is plugged into the OTG: Port not available.
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
608 bytes read in 88 ms (5.9 KiB/s)
Ignoring unknown command: ui
Ignoring malformed menu command:  autoboot
Ignoring malformed menu command:  hidden
Ignoring unknown command: totaltimeout
Fedora-Minimal-armhfp-Rawhide-20160906.n.0 Boot Options.
1:  Fedora-Minimal-armhfp-Rawhide-20160906.n.0 
(4.8.0-0.rc4.git4.1.fc26.armv7hl)
Enter choice: 1:Fedora-Minimal-armhfp-Rawhide-20160906.n.0 
(4.8.0-0.rc4.git4.1.fc26.armv7hl)

Retrieving file: /initramfs-4.8.0-0.rc4.git4.1.fc26.armv7hl.img
43230475 bytes read in 4428 ms (9.3 MiB/s)
Retrieving file: /vmlinuz-4.8.0-0.rc4.git4.1.fc26.armv7hl
6365792 bytes read in 748 ms (8.1 MiB/s)
append: console=ttyS0,115200 ro 
root=UUID=8b9ae3a6-5647-4628-809b-206be7c0a48c
Retrieving file: 
/dtb-4.8.0-0.rc4.git4.1.fc26.armv7hl/sun8i-a83t-cubietruck-plus.dtb

3278 bytes read in 4134 ms (0 Bytes/s)
## Flattened Device Tree blob at 4300
   Booting using the fdt blob at 0x4300
   Loading Ramdisk to 476c5000, end 49fff50b ... OK
   Loading Device Tree to 476c1000, end 476c4ccd ... OK

Starting kernel ...

[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 4.8.0-0.rc4.git4.1.fc26.armv7hl 
(mockbu...@arm04-builder02.arm.fedoraproject.org) (gcc version 6.2.1 
20160901 (Red Hat 6.2.1-1) (GCC) ) #1 SMP Fri Sep 2 21:29:31 UTC 2016
[0.00] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), 
cr=10c5387d

[0.00] CPU: div instructions available: patching division code
[0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
instruction cache

[0.00] OF: fdt:Machine model: Cubietech Cubietruck Plus
[0.00] efi: Getting EFI parameters from FDT:
[0.00] efi: UEFI not found.
[0.00] cma: Reserved 64 MiB at 0xbc00
[0.00] Memory policy: Data cache writealloc
[0.00] percpu: Embedded 15 pages/cpu @eed5e000 s32552 r8192 
d20696 u61440
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  
Total pages: 522560
[0.00] Kernel command line: console=ttyS0,115200 ro 
root=UUID=8b9ae3a6-5647-4628-809b-206be7c0a48c

[0.00] PID hash table entries: 4096 (order: 2, 16384 bytes)
[0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 
bytes)
[0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 
bytes)
[0.00] Memory: 1946276K/2097152K available (7898K kernel code, 
1162K rwdata, 3400K rodata, 1252K init, 9290K bss, 85340K reserved, 
65536K cma-reserved, 1245184K highmem)

[0.00] Virtual kernel memory layout:
[0.00] vector  : 0x - 0x1000   (   4 kB)
[0.00] fixmap  : 0xffc0 - 0xfff0   (3072 kB)
[0.00] vmalloc : 0xf080 - 0xff80   ( 240 MB)
[0.00] lowmem  : 0xc000 - 0xf000   ( 768 MB)
[0.00] pkmap   : 0xbfe0 - 0xc000   (   2 MB)
[0.00] modules : 0xbf00 - 0xbfe0   (  14 MB)
[0.00]   .text : 0xc0208000 - 0xc09bee64   (7900 kB)
[0.00]   .init : 0xc0d4b000 - 0xc0e84000   (1252 kB)
[0.00]   .data : 0xc0e84000 - 0xc0fa6b54   (1163 kB)
[0.00].bss : 0xc0fa6b54 - 0xc18b9538   (9291 kB)
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, 
Nodes=1

[0.00] Running RCU self tests
[0.00] Hierarchical RCU implementation.
[0.00]  RCU lockdep checking is enabled.
[0.00]  Build-time adjustment of leaf fanout to 32.
[0.00]  RCU restricting CPUs from NR_CPUS=32 to nr_cpu_ids=8.
[0.00] RCU: Adjusting geometry for rcu_fanout_leaf=32, 
nr_cpu_ids=8

[0.00] kmemleak: Kernel memory leak detector disabled
[0.00] NR_IRQS:16 nr_irqs:16 16
[0.00] arm_arch_timer: Architected cp15 timer(s) running at 
24.00MHz (virt).
[0.00] clocksource: arch_sys_counter: mask: 0xff 
max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[0.08] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps 
every 

[fedora-arm] Re: Fedora on Odroid XU4 with Cloudshell LCD

[arm_ml]

Am 2016-08-16 13:22, schrieb Josh Boyer:

On Tue, Aug 16, 2016 at 3:59 AM,   wrote:

Hi there,
I've managed (with a lot of help from Stewart Samuels) to get Fedora 
24 on
my Odroid XU4. This board is part of the Cloudshell with USB3-SATA 
(128GB
SSD-Disc) and a 2.2“ TFT LCD with a 320×240 resolution. There is a 
need of

following kernel modules:

spi-s3c64xx -> found
fbtft_device -> not found
gpio-ir-recv -> found
gpioplug-ir-recv -> not found

The driver homepage https://github.com/notro/fbtft "The FBTFT drivers 
are
now in the Linux kernel staging tree". Where can I find the kernel 
staging?

dnf didn't found kernel-staging or kmod-staging


Fedora doesn't build the majority of the staging drivers.  If you need
some of them and can find someone willing to be on the hook for bug
reports against them, then you can open a bug requesting they be
enabled.

josh
___
arm mailing list
arm@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org


At the last few years there were (at least for i386, x86_64) additional 
rpm packages like kernel-staging or kmod-staging from Fedora or 
RPMFusion. Since FC23 or FC24 they're missing.


I've created a bug request.

Greetings
Andreas
___
arm mailing list
arm@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org

[fedora-arm] Fedora on Odroid XU4 with Cloudshell LCD

[arm_ml]

Hi there,
I've managed (with a lot of help from Stewart Samuels) to get Fedora 24 
on my Odroid XU4. This board is part of the Cloudshell with USB3-SATA 
(128GB SSD-Disc) and a 2.2“ TFT LCD with a 320×240 resolution. There is 
a need of following kernel modules:


spi-s3c64xx -> found
fbtft_device -> not found
gpio-ir-recv -> found
gpioplug-ir-recv -> not found

The driver homepage https://github.com/notro/fbtft "The FBTFT drivers 
are now in the Linux kernel staging tree". Where can I find the kernel 
staging? dnf didn't found kernel-staging or kmod-staging



Thanks
Andreas
___
arm mailing list
arm@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org

[fedora-arm] Fedora on Odroid XU4

[arm_ml]

Hi there,

I'm back from vacation. Is there any update to boot Fedora (24, 25 Beta, 
Rawhide) native on Odroid XU4?


Thanks
Andreas
___
arm mailing list
arm@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org

[fedora-arm] Re: Fedora 24-Beta-1.6 seems not working!!

[arm_ml]

Am 2016-06-30 10:19, schrieb arm...@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...@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
___
arm mailing list
arm@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org

[fedora-arm] Re: Fedora 24-Beta-1.6 seems not working!!

[arm_ml]

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...@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

[fedora-arm] Re: Fedora 23 and Odroid-xu4

[arm_ml]

Am 2016-06-22 07:52, schrieb Dennis Gilmore:

On Saturday, June 18, 2016 7:16:27 PM CDT ali hagigat wrote:

Now, uboot starts and reads initramfs and vmlinuz. But the root file
system can not be found and it enters dracut emergency mode(keyboard
is dead):

dracut:/#

Mr.Robinson, I am using Fedora24+lxde image. What is the name of the
root partition?
___
arm mailing list
arm@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org


you will need to rebuild the initramfs at the least to include 
dw_exynos-mmc
driver, additionally I made sure that exynosdrm, ehci-exynos and 
ohci-exynos

were included in the initramfs. I added rd.driver.pre=dw_exynos-
mmc,exynosdrm,ehci-exynos,ohci-exynos to the append line in 
extlinux.conf


Dennis
___
arm mailing list
arm@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org



Any update on this?

@Ali Hagat: 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
___
arm mailing list
arm@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org

[fedora-arm] Re: Fedora 24-Beta-1.6 seems not working!!

[arm_ml]

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 :



=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2016.06.19 10:38:30 
=~=~=~=~=~=~=~=~=~=~=~=




Hello Ali,

have you try it with Fedora Rwahide? I know they have a newer kernel it 
with more or better ARM-Support.


I didn't have success with my installation.

Greetings
Andreas
___
arm mailing list
arm@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org

[fedora-arm] Re: Fedora 23 and Odroid-xu4

[arm_ml]

Am 2016-06-15 16:06, schrieb ali hagigat:

Yes, the standard Fedora 24 images (choose which one you want) have
support for both the XU3 and XU4. They all have the u-boot and kernel
binaries that are needed. They DO NOT have the binaries I mentioned
before (because we can't legally redistribute them)

Flash the image you want with arm-image-installer with the
--target=none option plus any others you need.

You then need to follow the README.odroid to get them binary bits and
flash the Fedora u-boot with it.

http://git.denx.de/?p=u-boot.git;a=blob_plain;f=doc/README.odroid;hb=HEAD



according to your recommend, README.odroid, we need a fat partition
for kernel+fdt while Fedora24 image creates an EXT4 partition for
kernel.
Besides after writing Fedora 24 image,  when i do sd_fusing , _/boot
partition becomes unreadable and there is an error: wrong fs type, bad
option, bad superblock..
Anyway when the board powers on,  I can see uboot messages and the last 
line is:

ODROID-XU3 #
Uboot does not get the keystrokes of the keyboard though the light of
the keyboard is on but no character is echoed and seen!! and it stops
completely

any comment is highly appreciated
___
arm mailing list
arm@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org

Hello,

I've changed the filesystem on the boot-partition from EXT4 to FAT 
without success. The board is booting the U-Boot but not the kernel.


Greetings
Andreas
___
arm mailing list
arm@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org

[fedora-arm] Re: Fedora on Odroid XU4

[arm_ml]

Am 2016-05-19 11:30, schrieb Peter Robinson:

On Thu, May 19, 2016 at 9:32 AM,   wrote:

Am 2016-05-18 21:24, schrieb Peter Robinson:


Hi,

I've found in 
fedora-minimal-armhfp-rawhide-2016-05-08.n.0.sda.raw.xz
support for U-boot for Odroid-XU4. Can I "dd" the Image to a microSD 
?

Or should I use the fedora-arm-image-installer, but which target?

I'm using the XU4 with the Ubuntu?-Kernel and Fedora 23 on top as a
Home/Nas-Server with the Cloudshell.



So there's some extra steps needed for exynos processors as there's a
binary blob, which we can't redistribute, needed for boot. You can 
use
the Fedora u-boot and kernel. There's details of where to get the 
blob

needed (depends on your version) in the README below (we ship this
readme with the new 2016.05 u-boot).

So you should be able to dd out the image or "arm-image-installer
--image=XX --target=none" and then follow the instructions to write
the blob/u-boot.

Peter

[1]
http://git.denx.de/?p=u-boot.git;a=blob_plain;f=doc/README.odroid;hb=HEAD
___
arm mailing list
arm@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org



Hi Peter,

thank you for this information. What I've done:

[root@destnadml00 Arm]# fedora-arm-image-installer
--image=Fedora-Minimal-armhfp-Rawhide-20160518.n.0-sda.raw.xz 
--target=none

--media=/dev/sdc

=
= Selected Image:
= Fedora-Minimal-armhfp-Rawhide-20160518.n.0-sda.raw.xz
= Selected Media : /dev/sdc
= U-Boot Target : none
=

*
*
 WARNING! ALL DATA WILL BE DESTROYED 
*
*

 Type 'YES' to proceed, anything else to exit now

= Proceed? YES
= Writing:
= Fedora-Minimal-armhfp-Rawhide-20160518.n.0-sda.raw.xz
= To: /dev/sdc 
0+216811 Datensätze ein
0+216811 Datensätze aus
2146435072 Bytes (2,1 GB) kopiert, 176,355 s, 12,2 MB/s
= Writing image complete!
= No U-Boot will be installed.

= Installation Complete! Insert into the none and boot.
[root@destnadml00 Arm]# cd Odroid\ XU4/U-Boot/
[root@destnadml00 U-Boot]# ls -l
insgesamt 944
-rw-rw-r--. 1 resch resch  15616 19. Mai 08:42 bl1.bin.hardkernel
-rw-rw-r--. 1 resch resch  14592 19. Mai 08:37 
bl2.bin.hardkernel.1mb_uboot
-rw-r--r--. 1 root  root   47808 19. Mai 09:49 
exynos5422-odroidxu4.dtb

-rw-rw-r--. 1 resch resch  54209 19. Mai 08:26 movi_partition.patch
-rwxr-xr-x. 1 resch resch   1894 19. Mai 08:38 sd_fusing.1M.sh
-rw-rw-r--. 1 resch resch 262144 19. Mai 08:38 tzsw.bin.hardkernel
-rw-r--r--. 1 root  root  544935 19. Mai 09:57 u-boot.bin
-rw-r--r--. 1 root  root   11399 19. Mai 09:57 u-boot.dtb
[root@destnadml00 U-Boot]# ./sd_fusing.1M.sh /dev/sdc
++ '[' -z /dev/sdc ']'
++ '[' -b /dev/sdc ']'
++ echo '/dev/sdc reader is identified.'
/dev/sdc reader is identified.
++ '[' -d /sys/block/sdcboot0 ']'
++ '[' -n '' ']'
++ signed_bl1_position=1
++ bl2_position=31
++ uboot_position=63
++ tzsw_position=2111
++ device=/dev/sdc
++ '[' -f ./u-boot-dtb.bin ']'
++ '[' -f ./u-boot.bin ']'
++ uboot=./u-boot.bin
++ echo 'BL1 fusing'
BL1 fusing
++ sudo dd iflag=dsync oflag=dsync if=./bl1.bin.hardkernel of=/dev/sdc
seek=1
30+1 Datensätze ein
30+1 Datensätze aus
15616 Bytes (16 kB) kopiert, 0,0437169 s, 357 kB/s
++ echo 'BL2 fusing'
BL2 fusing
++ sudo dd iflag=dsync oflag=dsync if=./bl2.bin.hardkernel.1mb_uboot
of=/dev/sdc seek=31
28+1 Datensätze ein
28+1 Datensätze aus
14592 Bytes (15 kB) kopiert, 0,0736991 s, 198 kB/s
++ echo 'u-boot fusing'
u-boot fusing
++ sudo dd iflag=dsync oflag=dsync if=./u-boot.bin of=/dev/sdc seek=63
1064+1 Datensätze ein
1064+1 Datensätze aus
544935 Bytes (545 kB) kopiert, 1,67099 s, 326 kB/s
++ echo 'TrustZone S/W fusing'
TrustZone S/W fusing
++ sudo dd iflag=dsync oflag=dsync if=./tzsw.bin.hardkernel 
of=/dev/sdc

seek=2111
512+0 Datensätze ein
512+0 Datensätze aus.
262144 Bytes (262 kB) kopiert, 0,932371 s, 281 kB/s
++ echo 'U-boot image is fused successfully.'
U-boot image is fused successfully.
++ echo 'Eject /dev/sdc and insert it again.'
Eject /dev/sdc and insert it again.
[root@destnadml00 U-Boot]#


I've insert the SD-card into the XU4, switch to SD-Boot and Power on.
The fan is running, red light is on, but no output on screen. Neither 
the

mini LCD from the cloudshell or the monitor at HDMI.

What's wrong?


No idea. I don't have one of these. Do you have a serial USB-TTL cable
to be able to debug? It's very likely it's outputting errors to the
serial console telling you what the issue is.



OK, I will try at the evening at home. For the Odroid C2 i've a USB-TTL 
cable.


BTW:

What's the best support ARM board with Fedora? What I need:
- min.Quadcore
- 2 GB RAM
- SATA
- or USB3 to SATA
- OS: direct booting with Fedora 

[fedora-arm] Cubieboard 5 (aka CubieTruck Plus)

[arm_ml]

Hi there,
now the board is on my table.

The only image i've found is
linaro-desktop-cubietruck-plus-card-dp-v1.1.img. But I don't think its a
real aarch64 Image:

linaro@cubietruck-plus:~$ uname -a
Linux cubietruck-plus 3.4.39 #7 SMP PREEMPT Tue Mar 1 09:34:33 CST 2016
armv7l armv7l armv7l GNU/Linux
linaro@cubietruck-plus:~$
I think this should be armv8l ?

Is there any howto to create/build a aarch64 Image on a Cubieboard 5 
with Fedora ?


Greetings
Andreas
___
arm mailing list
arm@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org

[fedora-arm] Fedora on Odroid C2

[arm_ml]

Hi there,

I have my Odroid C2 since last Saturday. Ist there any chance to get 
Fedora on this Arm64 device?


Thanks
Andreas
___
arm mailing list
arm@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/arm@lists.fedoraproject.org