December 2018 - arm - Fedora mailing-lists

Bluetooth on Udoo Neo ?
by Ken Harris 25 Jun '19

25 Jun '19

Is it possible to enable Bluetooth on Udoo Neo ? FYI, it uses the TI WL1831 module. I tried : hciattach -n ttymxc2 texas ... but got "Initialization timed out." I also tried various combinations of bit rates and flow control. Any tips are welcome. -K

2 2

how to make a working f28 sd card for odroid-hc2 ?
by Torbjorn Jansson 14 Mar '19

14 Mar '19

Hello for a while now i have been struggling to create a set of steps to make a successfully bootable fedora 28 image for my odroid hc2 computers. the reason for this is several, but main one is to have all gluster related packaged available like the samba vfs modules and iscsi related packages for gluster that is missing from the ubuntu images. plus i prefer fedora. all i get is a sd card that boots but then hangs on initial setup and if i try to work around that by disabling it then boot takes maybe 5-10 minutes at least with failing services (probably those that depend on network) and when i finally get to a login prompt root doesn't work here is my step by step instructions so far that's not quite working: (this is done from a fedora 28 host) 1: first install needed packages dnf install arm-image-installer-2.5-1.fc28.noarch dnf install uboot-images-armv7-2018.03-6.fc28.noarch 2: get image and install it to sd card fedora-arm-image-installer --target=none --image=Fedora-Minimal-armhfp-28-1.1-sda.raw.xz --resizefs --norootpass --media=/dev/sdf --args "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd cpuidle.off=1 no_bL_switcher console=tty1 console=ttySAC2,115200n8" (sdf in this case is my sd card) 3: fix the missing dtb file mkdir /tmp/sd mount -t auto /dev/sdf2 /tmp/sd cd /tmp/sd/dtb ln -s exynos5422-odroidxu4.dtb exynos5422-odroidunknown.dtb umount /tmp/sd 4: make it boot by running sd_fusing mkdir sd_fusing; cd sd_fusing wget https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_f… \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_f… \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_f… \ https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd_f… chmod a+x sd_fusing.sh cp /usr/share/uboot/odroid-xu3/u-boot.bin . ./sd_fusing.sh /dev/sdf ok so now comes the problems at this stage i have a bootable image but it gets stuck, most likely on initial setup that never shows up. the thing is, it is not locked up because if i plug in an usb device i get a few lines on the serial console so kernel is still working but boot is stuck. last few lines on serial console is something like: Starting firewalld - dynamic firewall daemon... Starting Initial Setup configuration program... then some stuff related to usb & my disk then on first boot a few lines related to OpenSSH key generation rebooting hangs at same place with exception of SSH keys. to get a bit further i can mount the root filesystem manually on my other computer and remove the following two files: rm /etc/systemd/system/graphical.target.wants/initial-setup.service rm /etc/systemd/system/multi-user.target.wants/initial-setup.service this gets rid of the initial setup but then i get a whole bunch of services failing and boot being really really slow, it takes probably 10-15 minutes for everything to time out and get to the logon prompt. when i get it root doesn't work. this is where i kind of gave up. i know i somehow managed to get a bootable image several months ago, but i'm not sure if i then had to manually set root password by editing passwd or shadow before trying to boot. things on my wish list for this board: easier installation and updated packages that work. for example arm-image-installer with a board definition for odroid. may be usefull even if we have to run sd_fusing manualy after anyway, possibly with a text saying so. this also would help to make --addconsole work uboot that recognized hc2 so it loads the right file dtb file for hc2, one that works and is appropriate.

7 19

f29 uboot & odroid hc2 (patch)
by Torbjorn Jansson 27 Jan '19

27 Jan '19

Hello I asked on linux-arm-kernel mail list regarding the "missing" dtb file problem for odroid hc2. The info i got was that the hc1 dtb file is the correct one to use for hc2 too and there is a patch to make uboot detect and use the right dtb file. The patch in question: http://git.denx.de/?p=u-boot.git;a=patch;h=9cd97c5b049a9a282dda0b1782cbb38d… I rebuilt uboot-tools-2018.09-1.fc29.x86_64 with this patch applied and it boots and uses the hc1 dtb file correctly. No need for a manual symlink like: ln -s exynos5422-odroidhc1.dtb exynos5422-odroidunknown.dtb So would be nice if this could be considered for inclusion in the fedora uboot package sometime in the future to make it easier to get the hc2 up and running.

3 3

rock64 and odroid c2 boards
by mark co-dyre 18 Jan '19

18 Jan '19

Hello all, I've been looking for a group like this for a while now to hopefully help with learning how to get get a recent version of u-boot working properly so I can get fedora 29 to boot on my rock64 and odroid c2 boards. I'd also like to contribute this back once I get this working properly. So far I've gotten the odroid c2 to boot fine using the stock hardkernel 3.16 lts kernel and their older version of u-boot. For this I had used a chrooted instance of a Fedora 29 minimum sitting on the Ubuntu distro they provide. From this I built a new initramfs with dracut against a copy of the hosted ubunutu lib/modules. This all worked fine although I'd like to get it working with a recent u-boot, UEFI and load the grub.efi binary to boot the standard fedora kernel. I had got to the point where I had loaded the grub binary and was able to select my kernel (stock fedora 4.18.x kernel); Although things would hang after. I suspect the main reason for the hang was I borrowed the opensuse grub.efi UEFI app because I could not get the fedora one to run. Other than the binary blob stuff from hardkernel u-boot was stock and it was booting into u-boot just fine. I've set that board aside for now to use it as a build host and have moved on to my rock64 board. After putting the stock fedora 29 minimal image on a card and attempting to boot it Im seeing: ... regular u-boot stuff blah blah blah (full u-boot log is below) Hit any key to stop autoboot: 0 Card did not respond to voltage select! switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... ** Unable to read file / ** Found EFI removable media binary efi/boot/bootaa64.efi libfdt fdt_check_header(): FDT_ERR_BADMAGIC Scanning disk rksdmmc(a)ff500000.blk... Card did not respond to voltage select! Scanning disk rksdmmc(a)ff520000.blk... Disk rksdmmc(a)ff520000.blk not ready Found 4 disks 858216 bytes read in 43 ms (19 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC ## Starting EFI application at 02000000 ... System BootOrder not found. Initializing defaults. Creating boot entry "Boot0000" with label "Fedora" for file "\EFI\fedora\shimaa64.efi" ... hangs here I'm using the u-boot binary from another distro (arch linux) configured for a rock64 device; Not the Fedora one. I'm pretty ignorant on how the shim stuff works although I would like to learn all those details to form a better understanding. My current understanding is that this shim is a signed (by UEFI signing service) initial bootloader that handles chaining to a trusted full bootloader (grub in this case). Does grub need to be signed in some way to work with this shim that loads it? Are there any good resources out there that would help me better understand what is happening? My next step is going to be to use the fedora u-boot of course and see where that leads me. Although my gut is telling that may not produce the outcome I desire. I'm very familiar with patching and building so I'm not afraid to dig in and create some patches to bounce back once I have these up and running I'm just hoping to have someone provide some insight as to what I should be focusing on so I can gain some traction. I've noticed there's a #fedora-meeting-2 IRC channel that meets on Tues at 3pm UTC; I'm planning on dropping by next week. Well that's all for now I'm exhausted and need some sleep :) Thanks for reading, DDR version 1.06 20170424 In SRX LPDDR3 786MHz Bus Width=32 Col=11 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=4096MB ddrconfig:7 OUT Boot1 Release Time: 2017-05-18, version: 2.43 ChipType = 0x11, 187 emmc reinit emmc reinit SdmmcInit=2 20 SdmmcInit=0 0 BootCapSize=0 UserCapSize=30436MB FwPartOffset=2000 , 0 StorageInit ok = 60041 Raw SecureMode = 0 SecureInit read PBA: 0x4 SecureInit read PBA: 0x404 SecureInit read PBA: 0x804 SecureInit read PBA: 0xc04 SecureInit read PBA: 0x1004 SecureInit ret = 0, SecureMode = 0 LoadTrustBL No find bl30.bin No find bl32.bin Load uboot, ReadLba = 2000 Load OK, addr=0x200000, size=0x8b0ec RunBL31 0x10000 NOTICE: BL31: v1.3(debug):f947c7e NOTICE: BL31: Built : 09:28:45, May 31 2017 NOTICE: BL31:Rockchip release version: v1.3 INFO: ARM GICv2 driver initialized INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 1 INFO: plat_rockchip_pmu_init: pd status 0xe INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destiK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2018.03-1 (Apr 02 2018 - 19:14:47 -0600) Arch Linux ARM Model: Rockchip RK3328 EVB DRAM: 4 GiB MMC: rksdmmc@ff500000: 1, rksdmmc@ff520000: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment Failed (-5) In: serial@ff130000 Out: serial@ff130000 Err: serial@ff130000 Model: Rockchip RK3328 EVB Net: Warning: ethernet@ff540000 (eth0) using random MAC address - e6:d0:8e:31:57:c3 eth0: ethernet@ff540000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... ** Unable to read file / ** Found EFI removable media binary efi/boot/bootaa64.efi libfdt fdt_check_header(): FDT_ERR_BADMAGIC Scanning disk rksdmmc(a)ff500000.blk... Card did not respond to voltage select! Scanning disk rksdmmc(a)ff520000.blk... Disk rksdmmc(a)ff520000.blk not ready Found 4 disks 858216 bytes read in 43 ms (19 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC ## Starting EFI application at 02000000 ... System BootOrder not found. Initializing defaults. Creating boot entry "Boot0000" with label "Fedora" for file "\EFI\fedora\shimaa64.efi"

5 11

How to enable experimental CPU frequency support
by John Walicki 18 Jan '19

18 Jan '19

In Peter's blog post (1), he mentions that there now experimental CPU frequency support for the Raspberry Pi. I can't get my Raspberry Pi 3 B+ to scale beyond 600MHz. How do I enable the experimental CPU frequency support in /boot/efi/config.txt ? I'm running Fedora 29 4.19.10-300 kernel. Thanks! -- John (1) - https://nullr0ute.com/2018/12/raspberry-pi-improvements-in-fedora-29/

6 10

Request for testing: Raspberry Pi 3 WiFi testing
by Peter Robinson 23 Dec '18

23 Dec '18

Hi All, It looks like we've finally got to the bottom of the issues around disappearing WiFi on the Raspberry Pi 3 series of devices. It should be fixed with kernel 4.19.10 for F-28/F-29. Please test and provide feedback on the bug [1] or karma on the updates for F-29 [2] or F-28 [3]. To test with updates-testing please run: "dnf upgrade --enablerepo=updates-testing kernel\*" [1] https://bugzilla.redhat.com/show_bug.cgi?id=1652093 [2] https://bodhi.fedoraproject.org/updates/FEDORA-2018-95036ea383 [3] https://bodhi.fedoraproject.org/updates/FEDORA-2018-6e8c330d50

4 9

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠redhat.com 23 Dec '18

23 Dec '18

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2018-12-25 from 15:00:00 to 16:00:00 UTC At fedora-meeting-2(a)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… Source: https://apps.fedoraproject.org/calendar/meeting/9432/

2 1

dhcpd6 crashing
by Rafael Leiva-Ochoa 20 Dec '18

20 Dec '18

Hi, I am using a raspberry pi three that’s running Fedora 29. It seems that my DHCPd6 is crashing. I have included a picture of the crash. It was working fine on Fedora 28. Thanks, Rafael

2 2

Re: dhcpd6 crashing
by Rafael Leiva-Ochoa 20 Dec '18

20 Dec '18

Thanks, I will do that. I was not aware of the abrt-cli command. I will give it a try. On Thu, Dec 20, 2018 at 7:22 AM Peter Robinson <pbrobinson(a)gmail.com> wrote: > On Thu, Dec 20, 2018 at 3:08 PM Rafael Leiva-Ochoa <spawn(a)rloteck.net> > wrote: > >> Hi, >> >> I am using a raspberry pi three that’s running Fedora 29. It seems >> that my DHCPd6 is crashing. I have included a picture of the crash. It was >> working fine on Fedora 28. >> > > Generally the rule of thumb for requesting help is to add text to a bug, > not attach photos. > > The output is actually not helpful as it doesn't have the debug symbols. I > suggest using abrt-cli to generate a useful backtrace and report it to the > appropriate component where the maintainer should be able to assist. > > Peter >

1 0

orangepi prime
by ken campbell 20 Dec '18

20 Dec '18

the cat list says it is supported but the target is not fornd

4 14

No wifi on RPi 3B+ after Kernel Update
by John Anthony Frame 18 Dec '18

18 Dec '18

Wifi on RPi 3B+ appears to no longer work after updating kernel to 4.18.17-300.fc29.aarch64. Worked OK with 4.18.16-300.fc29.aarch64 After update: dmesg | grep brcm [ 19.386730] bluetooth hci0: Direct firmware load for brcm/BCM4345C0.hcd failed with error -2 [ 19.396367] Bluetooth: hci0: BCM: Patch brcm/BCM4345C0.hcd not found Before update: dmesg | grep brc [ 30.062387] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 30.075952] usbcore: registered new interface driver brcmfmac [ 30.169952] bluetooth hci0: Direct firmware load for brcm/BCM4345C0.hcd failed with error -2 [ 30.169957] Bluetooth: hci0: BCM: Patch brcm/BCM4345C0.hcd not found [ 32.183096] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 32.220167] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 1 2015 07:29:38 version 7.45.18 (r538002) FWID 01-6a2c8ad4

3 2

Permanently disable wireless and Bluetooth interface at boot
by Rafael Leiva-Ochoa 18 Dec '18

18 Dec '18

Hi, Does anyone know how to disable the wireless and Bluetooth interface on boot or permanently? I’ve been reading a few fedora articles but none of them really have a permanent way to do it on boot. Thanks, Rafael

2 2

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠redhat.com 17 Dec '18

17 Dec '18

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2018-12-18 from 15:00:00 to 16:00:00 UTC At fedora-meeting-2(a)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… Source: https://apps.fedoraproject.org/calendar/meeting/9430/

2 1

Odroid C2
by Dr. Zenzic 16 Dec '18

16 Dec '18

Hello All, Has anyone had any luck getting Fedora 28 to work on the Odroid C2? I've tried downloading the Fedora 28 Server aarch.raw.xz image which i put onto my sd card. I then moved the Archlinux aarch64 boot parition into boot along with the lib/modules and lib/firmware folders from Archlinux. This has been to no avail. I'm working on building the hardkernel kernel myself now but have never actually compiled a kernel myself so I'm not sure what I fully need to get the Fedora rootfs to boot with the kernel. If anyone has some guidance or a nice writeup on getting a bootable kernel recognized by Fedora on the Odroid C2 that would be greatly appreciated.

5 14

Discovering IP address of headless server
by Robert Moskowitz 15 Dec '18

15 Dec '18

I am thinking about how to go about installing Fedora on a headless server without use of a console connection. 1) some in arm-image-installer to provide root password instead of just norootpassword. And then NOT to even stop the install at this initial setup phase. 2) some way (other than tools like fping) to find the IP address of the server. 3) Server management on port 9090 does all that would normally be done in initial setup (I am kind of assuming it already does). What else would be needed for a real headless install? Or maybe it is already there and I just missed the link... thanks

4 3

build of Firefox 64 OOMs in koji
by Dan Horák 14 Dec '18

14 Dec '18

Hi guys, seems we might be at the end of the road with Firefox in Fedora on arm. After the update to FF 64 the builds fail on armv7 with an OOM problem during the linking phase. Martin thinks he has already applied all known workarounds in the spec file to limit the object and library file sizes and it is still not enough. ... 359:49.51 if (!dom::ToJSValue(js, boolBuffer, elemSize, &val)) { 359:49.52 ~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 359:54.71 toolkit/library/symverscript.stub 359:55.08 toolkit/library/libxul.so 362:26.92 /usr/bin/ld.gold: fatal error: libxul.so: mmap: failed to allocate 1784148544 bytes for output file: Cannot allocate memory 362:26.93 collect2: error: ld returned 1 exit status ... see build.log in https://koji.fedoraproject.org/koji/taskinfo?taskID=31439321 https://bugzilla.redhat.com/show_bug.cgi?id=1658940 has been opened to track the issue Any further tips & trick are welcome. Dan

1 0

Raspberry Pi and its 7" display
by Kevin Cummings 13 Dec '18

13 Dec '18

Hi Folks, Longtime Fedora user here. Last winter, I got a Raspberry Pi, and installed F28 on it. Using the HDMI output, it works well. Recently, I picked up the Raspberry Pi 7" display (and case). After hooking up the display to the Pi via the ribbon cable, I booted it up. The 7" display works well as the initial console, and I see all the usual messages go flying by. At some point (when it decides to switch to graphics mode) the display goes blank. Nothing on it. I cannot switch even to a virtual console. The new case blocks using the HDMI port, so I had to remove the Pi from the case (while leaving the ribbon cable attached to the display). After plugging a monitor into the HDMI port, what I discovered was that the Pi boots using the display as console, then switches to the HDMI port for the X11 driver. (not useful) How can I get the X11 display to come up on the 7" display in graphics mode. What do I need? A new xorg-x11-drv driver? A newer kernel? I'd like to turn this into a MythTV server (with a USB capture) and use the display as a system console with the ability to watch videos on it. (Yeah, I'm aware that its only a 800x400 screen.) Failing that, I'd like to use it in a "tablet" mode and get used to the touch screen interface. -- Kevin J. Cummings cummings(a)kjchome.homeip.net cummings(a)kjc386.framingham.ma.us kjchome(a)icloud.com Registered Linux User #1232 (http://www.linuxcounter.net/)

5 11

Support of pitop
by Filip Bartmann 13 Dec '18

13 Dec '18

I wan't to buy for me to christmas https://pi-top.com/products/pi-top, and I want to know if Fedora supports its around rpi 3(eg display or speaker)? Thank's Filip Barmann

1 0

bluetooth on Odroid Xu4
by Stewart Samuels 13 Dec '18

13 Dec '18

Has anyone been able to get bluetooth working on the Odroid Xu4? I've got it working with Fedora 29 on an Intel based PC using two different USB dongles but not on the XU4. So, I am curious if anyone has tried on the XU4 and if successful, what dongles and packages are you using? BTW, on the XU4, I am able to pair and connect to my Yamaha Musiccast speaker. The problem occurs when I try to test the speakers using the bluetooth Mate sound menu. Once I click on either the right or left test button for the speaker, no sound is audible and the bluetooth connection immediately gets dropped. Again, all of this works on the Intel PC and I have verified I have the same bluetooth packages installed on both systems. Stewart

2 5

Fedora ARM & AArch64 Status Meeting Minutes 2018-12-11
by Paul Whalen 11 Dec '18

11 Dec '18

======================================================== #fedora-meeting-2: Fedora ARM and AArch64 Status Meeting ======================================================== Meeting started by pwhalen at 15:00:12 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2018-12-11/fedora_arm_an… . Meeting summary --------------- * roll call (pwhalen, 15:00:12) * 1) ==== Userspace Status ==== (pwhalen, 15:04:15) * unable to log in on arm disk images - no shell: Permission denied (pwhalen, 15:05:55) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1656529 (pwhalen, 15:05:55) * Armv7 guest fails on AArch64 - "cpu.c:906: arm_cpu_realizefn: Assertion no_aa32" (pwhalen, 15:06:36) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1651348 (pwhalen, 15:06:36) * 2) ==== Kernel Status ==== (pwhalen, 15:16:03) * F29: kernel-4.19.8-300.fc29 (pwhalen, 15:16:10) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1171225 (pwhalen, 15:16:11) * F30: kernel-4.20.0-0.rc6.git0.1.fc30 (pwhalen, 15:18:49) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1171248 (pwhalen, 15:18:49) * Please test and report any issues to the list or #fedora-arm. (pwhalen, 15:19:02) * 3) ==== Bootloader Status ==== (pwhalen, 15:22:11) * uboot-tools-2019.01-0.1.rc1.fc30 (pwhalen, 15:22:29) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1168822 (pwhalen, 15:22:38) * Please test and report any issues to the list or #fedora-arm. (pwhalen, 15:24:03) * Support added for RaspberryPi 3A+, better pinebook and a few others in uboot-tools-2019.01-0.1.rc1.fc30. (pwhalen, 15:28:18) * 4) == F30 == (pwhalen, 15:28:37) * Latest nominated nightly - https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test (pwhalen, 15:28:37) * Minimal disk image missing initramfs due to space issue. To be investigated. (pwhalen, 15:29:56) * 5) == Open Floor == (pwhalen, 15:36:02) * Next Fedora ARM meeting - January 8th, 2019 (pwhalen, 15:41:57) Meeting ended at 15:46:15 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * pwhalen (61) * jlinton (16) * mcodyre (12) * zodbot (6) * pbrobinson (6) * stellirin (5) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Introduction/ looking for mentor
by Adrian 10 Dec '18

10 Dec '18

Hey, I'm Adrian Sorge and I would love to contribute to the fedora on arm group, because I've been interested in non x86 architectures since about 5 years. I'm a computer engineering student living in Germany(CET). I have experiences in programming (mostly c(++) and java), automation(ansible and puppet) and monitoring(nagios). I would like to start with some changes to the arm-image-installer (I was thinking about adding some functions, including the automatic download of the image before writing it to the medium). Since I'm new to open source development, it would be great if someone could help me getting started and/or be my mentor/sponsor. Best Regards Adrian

2 1

Raspberry camera module
by Alessio Ciregia 10 Dec '18

10 Dec '18

Hello. I managed to set up the camera module (not the official one) on a Raspberry Pi 3 running Fedora 29. It is pretty simple and it works. [1] In the wiki [2] it is stated that the camera module doesn't work: can I update such paragraph? [1] <https://blog.oless.xyz/post/fedorarpicamera/> [2] <https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Does_the_add-…> Ciao, A

4 7

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠redhat.com 09 Dec '18

09 Dec '18

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2018-12-11 from 15:00:00 to 16:00:00 UTC At fedora-meeting-2(a)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… Source: https://apps.fedoraproject.org/calendar/meeting/9202/

1 0

Hikeyboard (Hikey 620) boots with Fedora 29 on mSD, and need action for install new kernel
by Zamir SUN 08 Dec '18

08 Dec '18

Hi, This meant to be a follow up for my tries on Hikeyboard (Hikey 620). I just tried to install Fedora 29 onto mSD, and it works now. But if I update or install new kernel, it still cannot find the card. By regenerating the initramfs with --add-drivers hi6220_reset.ko, it works. So I've updated the wiki page[1] to make this noted. Hope this can be useful for Hikeyboard users. [1] https://fedoraproject.org/wiki/Architectures/ARM/96Boards -- Zamir SUN Fedora user GPG : 1D86 6D4A 49CE 4BBD 72CF FCF5 D856 6E11 F2A0 525E

1 0

test results on odroid-hc1 on booting from sata
by Robert Moskowitz 06 Dec '18

06 Dec '18

Does not work. Sigh. U-Boot 2018.09 (Sep 11 2018 - 09:51:41 +0000) for ODROID-XU3/XU4/HC1 CPU: Exynos5422 @ 800 MHz Model: Odroid XU3 based on EXYNOS5422 Board: Odroid XU3 based on EXYNOS5422 Type: hc1 DRAM: 2 GiB MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 2 Loading Environment from MMC... Card did not respond to voltage select! *** Warning - No block device, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Hit any key to stop autoboot: 0 MMC Device 1 not found no mmc device at slot 1 Card did not respond to voltage select! switch to partitions #0, OK mmc2 is current device ** Invalid partition 1 ** starting USB... USB0: USB EHCI 1.00 USB1: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.00 USB2: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... cannot reset port 1!? 2 USB Device(s) found scanning bus 2 for devices... 2 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found scanning usb for ethernet devices... 1 Ethernet Device(s) found Waiting for Ethernet connection... done. BOOTP broadcast 1 BOOTP broadcast 2 DHCP client bound to address 192.168.192.15 (5004 ms) *** ERROR: `serverip' not set ================================== Setup was a 4GB uSD that only had the hardkernel bootloader and uboot. No partitions. sata drive (SSD) had the image (all partitions) installed. Including changes to extlinux.conf So now to get what others have working: boot on uSD and / on sata.

3 11

test results on odroid-hc1 on booting from uSD with rootfs on sata
by Robert Moskowitz 05 Dec '18

05 Dec '18

This was 'easy' Install image on uSD and do all the steps to make it bootable. But instead of growing the rootfs partition, delete it. Install image on the sata. Enlarge the rootfs and delete the boot partition. Insert the uSD and sata drive and boot. That is all it takes. It helps that we dd the images so that both devices have partitions with the same UUIDs. There are improvements, like deleting partition 1 from the sata and moving the start of the rootfs to that point, but I did not try this. I will leave it for others. Enjoy! But I really want complete booting from sata...

1 0

Re: Installer failure on SSd drive
by Robert Moskowitz 05 Dec '18

05 Dec '18

On 12/5/18 1:22 PM, Paul Whalen wrote: > > ----- Original Message ----- >> >> On 12/5/18 1:05 PM, Robert Moskowitz wrote: >>> >>> On 12/5/18 1:01 PM, Robert Moskowitz wrote: >>>> ===================================================== >>>> = Selected Image: >>>> = /home/rgm/arm/Fedora-Server-armhfp-29-1.2-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: >>>> = /home/rgm/arm/Fedora-Server-armhfp-29-1.2-sda.raw.xz >>>> = To: /dev/sdc .... >>>> 0+337225 records in >>>> 0+337225 records out >>>> 3242196992 bytes (3.2 GB, 3.0 GiB) copied, 148.012 s, 21.9 MB/s >>>> = Writing image complete! >>>> mount: /tmp/root: wrong fs type, bad option, bad superblock on >>>> /dev/sdc3, missing codepage or helper program, or other error. >>>> Error: mount /dev/sdc3 /tmp/root failed >>>> >>>> what does this mean? The SSD was in a USB/sata adapter that I have >>>> used many times in the past. I unplugged and replugged the USB and >>>> now all 3 partitions are showing and I am using gparted to enlarge >>>> the / partition. But it came up on sdd where before it was on sdc. >>>> >>> gparted failed to grow the partition. >>> >>> mount: /tmp/gparted-n5hfh1: wrong fs type, bad option, bad superblock >>> on /dev/sdd3, missing codepage or helper program, or other error >>> >>> So probably a problem with the SSD? >>> >> same failure with a HD. I am going to try a different adapter. >> >> mount: /tmp/root: wrong fs type, bad option, bad superblock on >> /dev/sdd3, missing codepage or helper program, or other error. >> Error: mount /dev/sdd3 /tmp/root failed > What version of the arm-image-installer is this? I fixed a few things in > the latest (arm-image-installer-2.10-1). > > I have seen that when writing out the server image repeatedly, a reboot > should 'fix' it. ARGH!!!! I have been running fedora-arm-image-installer that has been in my working directory since 11/14!!! version 1.99 :( Just using what I had in my notes instead of noticing the name change to arm-image-installer. Time to delete this old cruft. yes, I did LOTS of writing out images. And a reboot helped.

1 0

Installer failure on SSd drive
by Robert Moskowitz 05 Dec '18

05 Dec '18

===================================================== = Selected Image: = /home/rgm/arm/Fedora-Server-armhfp-29-1.2-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: = /home/rgm/arm/Fedora-Server-armhfp-29-1.2-sda.raw.xz = To: /dev/sdc .... 0+337225 records in 0+337225 records out 3242196992 bytes (3.2 GB, 3.0 GiB) copied, 148.012 s, 21.9 MB/s = Writing image complete! mount: /tmp/root: wrong fs type, bad option, bad superblock on /dev/sdc3, missing codepage or helper program, or other error. Error: mount /dev/sdc3 /tmp/root failed what does this mean? The SSD was in a USB/sata adapter that I have used many times in the past. I unplugged and replugged the USB and now all 3 partitions are showing and I am using gparted to enlarge the / partition. But it came up on sdd where before it was on sdc.

2 4

Finding out which boards are supported
by Robert Moskowitz 05 Dec '18

05 Dec '18

Without doing an install to: cat /usr/share/doc/arm-image-installer/SUPPORTED-BOARDS Kind of a catch-22. You have to do an install to find out if your board is supported? I know there is a uboot for odroid-xu3, but does the F30 installer install for it? Well I will give it a try, but still you have created a catch-22 here. (and who here has read the book or saw the movie? :) ). (book is MUCH better than the movie, you really cannot follow all the flashbacks in the movie)

6 25

Read only sdb - just not my day...
by Robert Moskowitz 04 Dec '18

04 Dec '18

So I am pulling out my hair because even after a reboot I am still getting dd: failed to open '/dev/sdb': Read-only file system = Writing image complete! Warning: Unable to open /dev/sdb read-write (Read-only file system). /dev/sdb has been opened read-only. Warning: Unable to open /dev/sdb read-write (Read-only file system). /dev/sdb has been opened read-only. mount: /tmp/root: WARNING: device write-protected, mounted read-only. = No U-Boot will be installed. Tried a bunch of uSD cards. Then I just happened to look at my uSD card holder and see that the lock switch was locked.... Just one of those days. :)

1 0

Fedora ARM & AArch64 Status Meeting Minutes 2018-12-04
by Paul Whalen 04 Dec '18

04 Dec '18

======================================================== #fedora-meeting-2: Fedora ARM and AArch64 Status Meeting ======================================================== Meeting started by pwhalen at 15:00:38 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2018-12-04/fedora_arm_an… . Meeting summary --------------- * roll call (pwhalen, 15:00:39) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1645853 (stellirin, 15:10:27) * 1) ==== Userspace Status ==== (pwhalen, 15:31:19) * DNF error: Error in POSTTRANS scriptlet in rpm package kernel-core (pwhalen, 15:31:39) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1650707 (pwhalen, 15:31:39) * Should be fixed in rawhide. (pwhalen, 15:32:08) * Armv7 guest fails on AArch64 - "cpu.c:906: arm_cpu_realizefn: Assertion no_aa32" (pwhalen, 15:32:47) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1651348 (pwhalen, 15:32:47) * 32-bit ARM systems upgraded from <F30 to >=F30 will have non-BLS bootloader, but grubby-deprecated will not be installed (pwhalen, 15:34:03) * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1654841 (pwhalen, 15:34:03) * This should be fixed in extlinux-bootloader-1.2-7.fc30 (pwhalen, 15:34:21) * 2) ==== Kernel Status ==== (pwhalen, 15:38:59) * F29: kernel-4.19.6-300.fc29 (pwhalen, 15:40:06) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1168375 (pwhalen, 15:40:06) * Some reports of ext4 file system corruption on 4.19 (pwhalen, 15:41:02) * LINK: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.or… (pwhalen, 15:41:08) * F30: kernel-4.20.0-0.rc5.git0.1.fc30 (pwhalen, 15:43:45) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1168560 (pwhalen, 15:43:45) * Please test and report any issues to the list or #fedora-arm. (pwhalen, 15:45:56) * Very weird and random RPi wifi issue that began around 4.18.17. Wifi shows up on some boots, or not. Some hardware seems unaffected. (pwhalen, 15:52:39) * 3) ==== Bootloader Status ==== (pwhalen, 15:55:12) * uboot-tools-2018.11-1.fc30 available now for testing! (pwhalen, 15:55:37) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1168781 (pwhalen, 15:55:43) * Built with arm-trusted-firmware 2.0. (pwhalen, 15:56:36) * uboot-tools-2019.01-0.1.rc1.fc30 building now (pwhalen, 15:57:24) * LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1168822 (pwhalen, 15:57:38) * Adds support for Pinebook and Raspberry Pi A+. (pwhalen, 15:58:31) * 4) == F30 == (pwhalen, 15:58:41) * Latest nominated nightly - https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test (pwhalen, 15:58:41) * 5) == Open Floor == (pwhalen, 15:59:31) * Fedora ARM on AWS https://fedoramagazine.org/fedora-29-arm-aws/ Meeting ended at 16:00:06 UTC.

1 0

Does the Odroid HC1 support boot from sata
by Robert Moskowitz 03 Dec '18

03 Dec '18

Perhaps I am spoiled with the Cubieboards, I really like the specs of the Odroid HC1, other than its power draw (peaks at 4A) and UART serial (got to get an expensive 1.8V unit). But can I set it up with the partitions on the sata drive and only the uboot on the uSD? thanks

2 2

[Fedocal] Reminder meeting : Fedora ARM & AArch64 status meeting
by pwhalen＠redhat.com 02 Dec '18

02 Dec '18

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2018-12-04 from 15:00:00 to 16:00:00 UTC At fedora-meeting-2(a)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… Source: https://apps.fedoraproject.org/calendar/meeting/9202/

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm December 2018