Problems with Fedora-Server-armhfp-27-20170914.n.0-sda
by Robert Moskowitz
I think this one is even worst than 0913. At least with what little I
tested.
Still no ethernet, but the link is up. Further, I forgot to mention
last time, the config network option on the console is only offering the
hostname to change. No ethernet, not surprisingly. But I set the
hostname and it does not 'take'. On continue it does not display an X
in front of the networking option and once I do log in as root, the
hostname is still localhost. I can change the hostname with the normal
commands.
I plugged in the TP-link USB wifi dongle, and the console went crazy
scrolling messages. I had to unplug the dongle. The last few messages are:
[ 6040.253103] [<bf8a46ac>] (ath9k_cmn_init_crypto [ath9k_common]) from
[<bf8ba0c8>] (ath9k_htc_probe_device+0x3c4/0x7fc [ath9k_htc])
[ 6040.264883] [<bf8ba0c8>] (ath9k_htc_probe_device [ath9k_htc]) from
[<bf8b27b8>] (ath9k_htc_hw_init+0x18/0x38 [ath9k_htc])
[ 6040.275879] [<bf8b27b8>] (ath9k_htc_hw_init [ath9k_htc]) from
[<bf8b3cc8>] (ath9k_hif_usb_firmware_cb+0x124/0x184 [ath9k_htc])
[ 6040.287329] [<bf8b3cc8>] (ath9k_hif_usb_firmware_cb [ath9k_htc]) from
[<c07b0a78>] (request_firmware_work_func+0x40/0x68)
[ 6040.298319] [<c07b0a78>] (request_firmware_work_func) from
[<c0364a10>] (process_one_work+0x254/0x42c)
[ 6040.307632] [<c0364a10>] (process_one_work) from [<c0365b34>]
(worker_thread+0x2b8/0x434)
[ 6040.315815] [<c0365b34>] (worker_thread) from [<c036a67c>]
(kthread+0x13c/0x154)
[ 6040.323217] [<c036a67c>] (kthread) from [<c0307e78>]
(ret_from_fork+0x14/0x3c)
[ 6040.330596] ---[ end trace ead9f81706ad04d6 ]---
[ 6040.336440] ath9k_htc: Failed to initialize the device
[ 6040.341864] usb 4-1: ath9k_htc: USB layer deinitialized
I saved the complete console session if you want it or any other file.
Bob
6 years, 7 months
Re: Problems with Fedora-Server-armhfp-27-20170914.n.0-sda
by searider74
Ok. Thanks Peter. Any idea when this will be fixed on the odroid xu4?
Stewart
Sent from my T-Mobile 4G LTE Device
-------- Original message --------
From: Peter Robinson <pbrobinson(a)gmail.com>
Date: 9/16/17 4:54 AM (GMT-08:00)
To: searider74 <searider74(a)gmail.com>
Cc: Robert Moskowitz <rgm(a)htt-consult.com>, arm <arm(a)lists.fedoraproject.org>
Subject: Re: [fedora-arm] Re: Problems with Fedora-Server-armhfp-27-20170914.n.0-sda
On Fri, Sep 15, 2017 at 9:59 PM, searider74 <searider74(a)gmail.com> wrote:
> Interesting! The onboard ethernet for the odroid xu4 is not recognized
> either in f26. Wireless is however. Don't know if there is any relation
> between these systems.
Unrelated, the XU4 ethernet is attached to a USB-3 interface and
there's apparently some issue/regression with that.
> Stewart
>
>
> Sent from my T-Mobile 4G LTE Device
>
>
> -------- Original message --------
> From: Robert Moskowitz <rgm(a)htt-consult.com>
> Date: 9/15/17 11:19 AM (GMT-08:00)
> To: arm <arm(a)lists.fedoraproject.org>
> Subject: [fedora-arm] Problems with Fedora-Server-armhfp-27-20170914.n.0-sda
>
> I think this one is even worst than 0913. At least with what little I
> tested.
>
> Still no ethernet, but the link is up. Further, I forgot to mention
> last time, the config network option on the console is only offering the
> hostname to change. No ethernet, not surprisingly. But I set the
> hostname and it does not 'take'. On continue it does not display an X
> in front of the networking option and once I do log in as root, the
> hostname is still localhost. I can change the hostname with the normal
> commands.
>
> I plugged in the TP-link USB wifi dongle, and the console went crazy
> scrolling messages. I had to unplug the dongle. The last few messages are:
>
> [ 6040.253103] [<bf8a46ac>] (ath9k_cmn_init_crypto [ath9k_common]) from
> [<bf8ba0c8>] (ath9k_htc_probe_device+0x3c4/0x7fc [ath9k_htc])
> [ 6040.264883] [<bf8ba0c8>] (ath9k_htc_probe_device [ath9k_htc]) from
> [<bf8b27b8>] (ath9k_htc_hw_init+0x18/0x38 [ath9k_htc])
> [ 6040.275879] [<bf8b27b8>] (ath9k_htc_hw_init [ath9k_htc]) from
> [<bf8b3cc8>] (ath9k_hif_usb_firmware_cb+0x124/0x184 [ath9k_htc])
> [ 6040.287329] [<bf8b3cc8>] (ath9k_hif_usb_firmware_cb [ath9k_htc]) from
> [<c07b0a78>] (request_firmware_work_func+0x40/0x68)
> [ 6040.298319] [<c07b0a78>] (request_firmware_work_func) from
> [<c0364a10>] (process_one_work+0x254/0x42c)
> [ 6040.307632] [<c0364a10>] (process_one_work) from [<c0365b34>]
> (worker_thread+0x2b8/0x434)
> [ 6040.315815] [<c0365b34>] (worker_thread) from [<c036a67c>]
> (kthread+0x13c/0x154)
> [ 6040.323217] [<c036a67c>] (kthread) from [<c0307e78>]
> (ret_from_fork+0x14/0x3c)
> [ 6040.330596] ---[ end trace ead9f81706ad04d6 ]---
> [ 6040.336440] ath9k_htc: Failed to initialize the device
> [ 6040.341864] usb 4-1: ath9k_htc: USB layer deinitialized
>
>
> I saved the complete console session if you want it or any other file.
>
> Bob
> _______________________________________________
> arm mailing list -- arm(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>
> _______________________________________________
> arm mailing list -- arm(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>
6 years, 7 months
Re: Problems with Fedora-Server-armhfp-27-20170914.n.0-sda
by searider74
Interesting! The onboard ethernet for the odroid xu4 is not recognized either in f26. Wireless is however. Don't know if there is any relation between these systems.
Stewart
Sent from my T-Mobile 4G LTE Device
-------- Original message --------
From: Robert Moskowitz <rgm(a)htt-consult.com>
Date: 9/15/17 11:19 AM (GMT-08:00)
To: arm <arm(a)lists.fedoraproject.org>
Subject: [fedora-arm] Problems with Fedora-Server-armhfp-27-20170914.n.0-sda
I think this one is even worst than 0913. At least with what little I
tested.
Still no ethernet, but the link is up. Further, I forgot to mention
last time, the config network option on the console is only offering the
hostname to change. No ethernet, not surprisingly. But I set the
hostname and it does not 'take'. On continue it does not display an X
in front of the networking option and once I do log in as root, the
hostname is still localhost. I can change the hostname with the normal
commands.
I plugged in the TP-link USB wifi dongle, and the console went crazy
scrolling messages. I had to unplug the dongle. The last few messages are:
[ 6040.253103] [<bf8a46ac>] (ath9k_cmn_init_crypto [ath9k_common]) from
[<bf8ba0c8>] (ath9k_htc_probe_device+0x3c4/0x7fc [ath9k_htc])
[ 6040.264883] [<bf8ba0c8>] (ath9k_htc_probe_device [ath9k_htc]) from
[<bf8b27b8>] (ath9k_htc_hw_init+0x18/0x38 [ath9k_htc])
[ 6040.275879] [<bf8b27b8>] (ath9k_htc_hw_init [ath9k_htc]) from
[<bf8b3cc8>] (ath9k_hif_usb_firmware_cb+0x124/0x184 [ath9k_htc])
[ 6040.287329] [<bf8b3cc8>] (ath9k_hif_usb_firmware_cb [ath9k_htc]) from
[<c07b0a78>] (request_firmware_work_func+0x40/0x68)
[ 6040.298319] [<c07b0a78>] (request_firmware_work_func) from
[<c0364a10>] (process_one_work+0x254/0x42c)
[ 6040.307632] [<c0364a10>] (process_one_work) from [<c0365b34>]
(worker_thread+0x2b8/0x434)
[ 6040.315815] [<c0365b34>] (worker_thread) from [<c036a67c>]
(kthread+0x13c/0x154)
[ 6040.323217] [<c036a67c>] (kthread) from [<c0307e78>]
(ret_from_fork+0x14/0x3c)
[ 6040.330596] ---[ end trace ead9f81706ad04d6 ]---
[ 6040.336440] ath9k_htc: Failed to initialize the device
[ 6040.341864] usb 4-1: ath9k_htc: USB layer deinitialized
I saved the complete console session if you want it or any other file.
Bob
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org
To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
6 years, 7 months
armhfp bootstrap needed for fpc
by Florian Weimer
We never switched fpc (the Free Pascal Compiler) to the armhfp (hard
float) ABI. Would anyone who is familiar with the procedure like to
help with this?
The bug tracking this is:
https://bugzilla.redhat.com/show_bug.cgi?id=1491788
As far as I can tell, Debian has an fpc package which is relatively
close in version to Fedora's, and it does no longer need any upstream
patches for armhfp.
Thanks,
Florian
6 years, 7 months
Problems on Fedora-Server-armhfp-27-20170913.n.0-sda on Cubieboard2
by Robert Moskowitz
I just pulled down the most recent build and wrote it to mSD with:
fedora-arm-image-installer
--image=/home/rgm/arm/Fedora-Server-armhfp-27-20170913.n.0-sda.raw.xz
--target=Cubieboard2 --media=/dev/sdb --norootpass --addconsole
Put it into my C2 and booted. Took a LONG time. Lots of stuff to the
logs if you want them or anything else.
Once booted and logged in as root, 'ip a' does not show eth0. I AM
seeing the link light on the switch.
I added the TP-link wifi usb dongle. It was recognized but I get the
same failures with it as I am getting with F26 server minimal.
I powered down, saved the console log, reboot. and still not eth0 but
link is up.
Is this build known to be a problem? This is the first F27 build I have
tried.
Thanks
Bob
6 years, 7 months
Re: more on - Re: Fedora-Server-armhfp-26-1.5-sda nmcli wili problems
by Robert Moskowitz
Oh, here is what I found in /var/log/messages for the TP-Link:
Sep 12 17:09:22 localhost kernel: usb 1-1: new high-speed USB device
number 4 using ehci-platform
Sep 12 17:09:22 localhost kernel: usb 1-1: New USB device found,
idVendor=0cf3, idProduct=9271
Sep 12 17:09:22 localhost kernel: usb 1-1: New USB device strings:
Mfr=16, Product=32, SerialNumber=48
Sep 12 17:09:22 localhost kernel: usb 1-1: Product: USB2.0 WLAN
Sep 12 17:09:22 localhost kernel: usb 1-1: Manufacturer: ATHEROS
Sep 12 17:09:22 localhost kernel: usb 1-1: SerialNumber: 12345
Sep 12 17:09:22 localhost kernel: usb 1-1: ath9k_htc: Firmware
ath9k_htc/htc_9271-1.4.0.fw requested
Sep 12 17:09:22 localhost kernel: usbcore: registered new interface
driver ath9k_htc
Sep 12 17:09:23 localhost kernel: usb 1-1: ath9k_htc: Transferred FW:
ath9k_htc/htc_9271-1.4.0.fw, size: 51008
Sep 12 17:09:23 localhost kernel: ath9k_htc 1-1:1.0: ath9k_htc: HTC
initialized with 33 credits
Sep 12 17:09:23 localhost kernel: ath9k_htc 1-1:1.0: ath9k_htc: FW
Version: 1.4
Sep 12 17:09:23 localhost kernel: ath9k_htc 1-1:1.0: FW RMW support: On
Sep 12 17:09:23 localhost kernel: ieee80211 phy1: Atheros AR9271 Rev:1
Sep 12 17:09:23 localhost NetworkManager[765]: <info> [1505250563.8303]
manager: (wlan0): 'wifi' plugin not available; creating generic device
Sep 12 17:09:23 localhost systemd: Starting Load/Save RF Kill Switch
Status...
Sep 12 17:09:23 localhost NetworkManager[765]: <info> [1505250563.8859]
manager: (wlan0): new Generic device
(/org/freedesktop/NetworkManager/Devices/4)
Sep 12 17:09:24 localhost systemd-udevd: link_config: autonegotiation is
unset or enabled, the speed and duplex are not writable.
Sep 12 17:09:24 localhost crda: setting regulatory domain to US based on
timezone (America/New_York)
Sep 12 17:09:24 localhost NetworkManager[765]: <info> [1505250564.2765]
rfkill1: found WiFi radio killswitch (at
/sys/devices/platform/soc@01c00000/1c14000.usb/usb1/1-1/1-1:1.0/ieee80211/phy1/rfkill1)
(driver ath9k_htc)
Sep 12 17:09:24 localhost audit: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
Sep 12 17:09:24 localhost systemd: Started Load/Save RF Kill Switch Status.
Sep 12 17:09:29 localhost audit: SERVICE_STOP pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
[root@localhost ~]#
On 09/12/2017 05:02 PM, Peter Robinson wrote:
> On Tue, Sep 12, 2017 at 9:57 PM, Robert Moskowitz <rgm(a)htt-consult.com> wrote:
>> Peter,
>>
>> I just put down a fresh image:
>>
>> fedora-arm-image-installer
>> --image=/home/rgm/arm/Fedora-Server-armhfp-26-1.5-sda.raw.xz
>> --target=Cubieboard2 --media=/dev/sdb --norootpass --selinux=ON --addconsole
>>
>> booted up via a USBTTY dongle, set the timezone, hostname, and root
>> password. Continued and logged in.
>>
>> No dnf update. This is the software levels shipped.
>>
>> After logging in, inserted the wifi USB dongle and and same bad results. So
> What make/model/chipset/driver? You need to provide more information
> that "usb dongle"
>
>> I believe there is some key component missing for wifi support via nmcli in
> There isn't, I use it literally on dozens of different ARM devices
> exactly as you define above, there might well be with your specific
> version USB dongle but it's not generally got an issue.
>
>> the minimal server. It works just fine with the F26-Xfce image and the
>> Centos7-arm image.
>>
>> So please give me some idea of what may be missing. I am happy to test
>> installing and getting this working. In fact I really NEED to get this
>> working by Nov 5 when I leave for pre-IETF travel...
> I don't see what the travel has to do with this bug report
>
>> thanks
>>
>> Bob
>>
>> On 09/08/2017 10:33 AM, Peter Robinson wrote:
>>> On Thu, Sep 7, 2017 at 6:26 PM, Robert Moskowitz <rgm(a)htt-consult.com>
>>> wrote:
>>>> I took my F26 cubieboard to a hackathon where all they have here is
>>>> wireless.
>>>>
>>>> So I put in a wifi usb dongle and see wlan0 available:
>>>>
>>>> # nmcli device status
>>>>
>>>> DEVICE TYPE STATE CONNECTION
>>>>
>>>> eth0 ethernet unavailable --
>>>>
>>>> lo loopback unmanaged --
>>>>
>>>> wlan0 wifi unmanaged --
>>>>
>>>>
>>>> I create a connection:
>>>>
>>>> nmcli con add con-name cobo ifname wlan0 type wifi ssid CoboFree
>>> I use "nmcli device wifi connect SSID-Name password wireless-password"
>>> regularly on F-26 without issue to connect to wireless networks
>>>
6 years, 7 months
Fedora-Server-armhfp-26-1.5-sda nmcli wili problems
by Robert Moskowitz
I took my F26 cubieboard to a hackathon where all they have here is
wireless.
So I put in a wifi usb dongle and see wlan0 available:
# nmcli device status
DEVICE TYPE STATE CONNECTION
eth0 ethernet unavailable --
lo loopback unmanaged --
wlan0 wifi unmanaged --
I create a connection:
nmcli con add con-name cobo ifname wlan0 type wifi ssid CoboFree
(CoboFree is the SSID I am using here on my notebook)
# nmcli connection show
NAME UUID TYPE DEVICE
cobo d9e7a648-0d48-4353-856f-7c3a3dd3db3b 802-11-wireless --
eth0 9699134e-a93c-32fb-b518-a0dc17cc78a3 802-3-ethernet --
I then try to bring the connection up:
# nmcli con up cobo
Error: Connection activation failed: No suitable device found for this
connection.
nmcli device wifi list
is an empty list
What am I missing here. I have used mncli on other builds in the past.
This is my first try with this image.
thanks
Bob
6 years, 7 months
