arm October 2018

arm@lists.fedoraproject.org

13 participants
18 discussions

Bug 1628209
by Steven A. Falco 15 Oct '18

15 Oct '18

Roughly a month ago I upgraded the kernel on my wandboard quad. The quad had been running kernel 4.17.19-200.fc28.armv7hl and was working properly. However, when I upgraded to kernel 4.18.5-200.fc28.armv7hl I found that ethernet no longer worked. I reverted to kernel 4.17.19-200.fc28.armv7hl and ethernet was fine again. I've tried several kernels since then, including the latest (4.18.13-200.fc28.armv7hl), with the same negative result. When running kernel 4.18.13-200.fc28.armv7hl the console messages say that the link is up, however I am not able to ping anything on the local subnet. I filed a bug here: https://bugzilla.redhat.com/show_bug.cgi?id=1628209 Does anyone know of any driver changes that might account for this bug? Steve

2 1

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

14 Oct '18

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2018-10-16 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

Miserable performance F29-beta-Xfce vs F28-Xfce
by Robert Moskowitz 11 Oct '18

11 Oct '18

I am using a Cubieboard2 with the current image: Fedora-Xfce-armhfp-29-20181002.n.0-sda I connect ethernet, serial TTY/USB console, HDMI monitor, kybd/mouse. The OS is on a HD and only uboot is on the uSD card. The firstboot proceeds normally and then I have to really wait for the Initial Setup GUI to fully appear. The mouse is VERY jumpy. I manage to click on root password and the Initial screen slowly goes up as a window shade, revealing the root password dialog. Very jumpy and slow, I manage to set the root password and click done. The screen comes down back to Initial and I manage to click on setting up the user. Very slow raising of the window shade and very slow response in the dialog boxes for setting up the user. Click done then finish on the Initial setup screen. Slowly get to the login screen and then very slow giving me the default workstation question then getting into the session. dnfdragora-updater seems to run forever. I go into session startup settings and turn this off. I wish this was the default for arm... Everything in the DE is very slow. I finally get vncserver working, and switch to a vnc client console and that is peppy. So I wondered... I grabbed another drive and build the F28-Xfce released image and put its uboot on another uSD card. This time Initial Setup had decent performance. The window screen went up much smoother. Mouse was not jumpy. Dialog entry was decent. Got into the DE smoothly. dnfdragora did not take forever to do its initial run. So something really wrong, performance-wise with the F29-beta-Xfce. That SELinux patch we got a couple weeks ago helped a little. One difference I note is F28 has a swap partition, F29 does not. Now during the initial stuff, no swap was used. Now I see 29KB of swap used with 86KB memory free. This is a real problem.

2 11

Re: Putting f28 into galaxy s7
by Peter Robinson 10 Oct '18

10 Oct '18

Hi, Please leave the mailing list on the cc: > Thanks for a quick response. > First, there is no sim card installed so I am using it like a small tablet. > The chipset is EXYNOS8890. > I ALSO HAVE A BLUETOOTH KEYBOARD, if that helps. > I can have constant wifi by using my s9+ phone. None of the above matters until you can get it booting it to Linux, all wireless options (bluetooth, wifi, sim/data) are irrelevant until you get it booting to a userspace wher you can bring any of that up. I'm not sure any of the exynos8 kernel stuff is even upstream yet, unfortunately unless you know quite a bit about low level kernel and boot debug I don't think you're going to have a lot of luck. > On Wed, Oct 10, 2018, 2:53 PM Peter Robinson <pbrobinson(a)gmail.com> wrote: >> >> > I have read a lot of posts about this but still get nowhere. I reset phone to its base android 8.0 and have it rooted etc. >> > It has a 4 GB sd card that was just formatted on the phone. >> > What happens next (and how)? >> >> We don't actively support Fedora on phones, there's a lot of >> complexity involved. That being said there are some people that have >> put Fedora on various phones. >> >> In Fedora we only support booting aarch64, which the S7 is, with UEFI >> so some of the process will be getting a kernel booting like that, >> you'll likely need a custom kernel because the requirements between >> Fedora and Android for kernels are a little different. >> >> Also which version of the S7 because there's at least one with some >> Samsung EXYNOS processor and one that has a Qualcomm processor, I >> suspect you'll have better luck with the later >> >> Basically the Fedora ARM people aren't focused on Phones as they're >> problematic and a constant moving target and we really just don't have >> than many resources so we're focused on more Fedora things like >> servers/laptops/desktops/dev boards/IoT etc. >> >> Peter

1 0

Putting f28 into galaxy s7
by Martyn Griffin 10 Oct '18

10 Oct '18

I have read a lot of posts about this but still get nowhere. I reset phone to its base android 8.0 and have it rooted etc. It has a 4 GB sd card that was just formatted on the phone. What happens next (and how)?

2 1

802.1q vlan support
by solarflow99 07 Oct '18

07 Oct '18

Hi, I used to be able to do with back around the F25 days and previous. Now I can't do vlans at all anymore. As you can see from the commands below the vlan id gets set to id 3068862004, and seems to keep auto incrementing itself, and the kernel module gets loaded but not used. Does anyone have any ideas? $ ip link add link eth0 name eth0.1 type vlan id 1 $ ip -d addr show eth0.1 3: eth0.1@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether b8:27:eb:20:25:16 brd ff:ff:ff:ff:ff:ff promiscuity 3068862004 vlan protocol 802.1Q id 3068862004 <REORDER_HDR> numtxqueues 3068862004 numrxqueues 3068862004 gso_max_size 3068862004 gso_max_segs 3068862004 $ lsmod | grep q Module Size Used by 8021q 28672 0 garp 16384 1 8021q mrp 16384 1 8021q $ lsusb Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter

2 11

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

07 Oct '18

Dear all, You are kindly invited to the meeting: Fedora ARM & AArch64 status meeting on 2018-10-09 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

Testing required for WiFi on the Raspberry Pi 3/3B+
by Peter Robinson 05 Oct '18

05 Oct '18

So a bit of a mike drop moment... WiFi on the Raspberry Pi 3 and 3B+ should now work out of the box on Fedora 29 and rawhide! As of kernel-4.18.11-301.fc29 and linux-firmware-20180913-87.git44d4fca9.fc29 which are now stable in Fedora 29 the wifi interface should just work right away with no extra steps required. Please test and report any problems here. Fedora 28 will come in time, I want to We're still working to get this upstream, ultimately this will improve the entire linux ecosystem around not just the Raspberry Pi but the majority of ARM devices that ship with broadcom wifi and previously needed the same hack to get wifi to work. The focus has been on the Raspberry Pi here because of popularity. Happy weekend! Peter

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

arm October 2018