No wifi on RPi 3B+ after Kernel Update
by John Anthony Frame
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
5 years, 4 months
Odroid C2
by Dr. Zenzic
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 years, 4 months
Discovering IP address of headless server
by Robert Moskowitz
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
5 years, 4 months
build of Firefox 64 OOMs in koji
by Dan Horák
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
5 years, 4 months
Raspberry Pi and its 7" display
by Kevin Cummings
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 years, 4 months
bluetooth on Odroid Xu4
by Stewart Samuels
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
5 years, 4 months
Fedora ARM & AArch64 Status Meeting Minutes 2018-12-11
by Paul Whalen
========================================================
#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_...
.
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
5 years, 4 months