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 3:49 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
>
>
> Dah, I had to do was check the saved console session:
>
> U-Boot SPL 2017.09-rc2 (Aug 25 2017 - 17:20:07)
> DRAM: 1024 MiB
> CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
> Trying to boot from MMC1
>
>
> U-Boot 2017.09-rc2 (Aug 25 2017 - 17:20:07 +0000) Allwinner Technology
>
> CPU:   Allwinner A20 (SUN7I)
> [rgm@lx120e arm]$ head screenlog.6bad -n20
>
> U-Boot SPL 2017.09-rc2 (Aug 25 2017 - 17:20:07)
> DRAM: 1024 MiB
> CPU: 912000000Hz, AXI/AHB/APB: 3/2/2
> Trying to boot from MMC1
>
>
> U-Boot 2017.09-rc2 (Aug 25 2017 - 17:20:07 +0000) Allwinner Technology
>
> CPU:   Allwinner A20 (SUN7I)
> Model: Cubietech Cubieboard2
> I2C:   ready
> DRAM:  1 GiB
> MMC:   SUNXI SD/MMC: 0
>
> So Koji is building the image with RC2.  Please point me to RC4 and I will
> test with that.  Or please roll RC4 into the build process.

https://koji.fedoraproject.org/koji/buildinfo?buildID=966566

It will be added to the build once we're out of freeze post beta,
although that will be a 2017.09 GA build.

>>> 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.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
>>
> Since I am looking at the capture file...
>
> um, the whole capture is 440KB.  How do you want it...

I don't actually want any of it because I don't have much interest in
terrible ath9K wireless dongles but the crash between the star/end
indicators certainly won't be 440K, there's never any reason for a
full dmesg.
_______________________________________________
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