Re: Problems with Fedora-Server-armhfp-27-20170914.n.0-sda

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Sep 17, 2017 at 2:45 AM, Robert Moskowitz <rgm@xxxxxxxxxxxxxxx> wrote:
>
>
> On 09/16/2017 07:57 AM, Peter Robinson wrote:
>>
>> On Fri, Sep 15, 2017 at 7:19 PM, Robert Moskowitz <rgm@xxxxxxxxxxxxxxx>
>> wrote:
>>>
>>> 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.
>>
>> What version of u-boot? There was an issue that affected some
>> AllWinner A20 devices, make sure you're running 2017.09 rc4
>
>
> I will check, perhaps tomorrow or Monday for sure.  But it is whatever is
> shipping with the image.  If necessary, I do know how to regress uboot.
>
>>
>>> 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
>>
>> You need to include the full trace (from the point it says begin trace
>> or similar), but that's not really a ARM/cubieboard specific crash
>>
> Let's first look into the uboot issue.  I would be happy to provide the
> whole trace.  Just a little leery of swamping this list.

That is your wireless, the u-boot version won't fix that, the u-boot
issue should fixed the wired ethernet
_______________________________________________
arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux ARM (Vger)]     [Linux ARM]     [ARM Kernel]     [Fedora User Discussion]     [Older Fedora Users Discussion]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Maintainers]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

Powered by Linux