On Sun, Sep 17, 2017 at 12:47 AM, searider74 <searider74@xxxxxxxxx> wrote: > Ok. Thanks Peter. Any idea when this will be fixed on the odroid xu4? No idea, it's an issue with upstream, no idea if anyone's reported it to the appropriate maintainer, I don't have the hardware or the time so someone who cares about this HW combo will need to drive this, I'm happy to pull in a patch for the kernel once there's something headed upstream. Peter > Stewart > > Sent from my T-Mobile 4G LTE Device > > > -------- Original message -------- > From: Peter Robinson <pbrobinson@xxxxxxxxx> > Date: 9/16/17 4:54 AM (GMT-08:00) > To: searider74 <searider74@xxxxxxxxx> > Cc: Robert Moskowitz <rgm@xxxxxxxxxxxxxxx>, arm > <arm@xxxxxxxxxxxxxxxxxxxxxxx> > 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@xxxxxxxxx> 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@xxxxxxxxxxxxxxx> >> Date: 9/15/17 11:19 AM (GMT-08:00) >> To: arm <arm@xxxxxxxxxxxxxxxxxxxxxxx> >> 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@xxxxxxxxxxxxxxxxxxxxxxx >> To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx >> >> _______________________________________________ >> arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx >> To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx >> _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx
