> > On 12/10/18 10:18 PM, Kevin Cummings wrote: > >> On 12/10/18 9:20 PM, Peter Robinson wrote: > >> Any reason for F-28 instead of F-29? > > > > Lazy? I think you're lucky I upgraded it from the F27 I originally > > installed.... > > OK, I updated to f29 running 4.19.7-300.fc29 > > The first thing I noticed was that I had no wifi device. ifcfg only > showed eth0, lo, & vibr0 as network devices. > > My second boot of the day recognized my wifi and connected. > > The next thing I did was update 28 more packages, including a new kernel > (4.19.8-300.fc29). > > Upon rebooting it, no wifi again. In fact after 6 more reboots, none of > them had wifi. so I rebooted the 4.19.7-300.f29 kernel I still had, > which had a working wifi the last time I ran it. No wifi. > > Rebooted again back to 4.19.7-200.fc28 kernel, and bang! Wifi is up and > running. > > I could have sworn there was a statement in the Fedora ARM wiki that > says that wifi should work out of the box for my Pi 3B after 4.19.2. That fixed an issue for aarch64, there's two distinct and different issues. The issue you're seeing is being followed in the following bug, and as you've noticed with it coming and going depending on boot it's very intermittent and hence proving quite elusive to track down. https://bugzilla.redhat.com/show_bug.cgi?id=1652093 > >>> picked up the Raspberry Pi 7" display (and case). After hooking up the > >>> display to the Pi via the ribbon cable, I booted it up. > >>> > >>> The 7" display works well as the initial console, and I see all the > >>> usual messages go flying by. At some point (when it decides to switch > >>> to graphics mode) the display goes blank. Nothing on it. I cannot > >>> switch even to a virtual console. The new case blocks using the HDMI > >>> port, so I had to remove the Pi from the case (while leaving the ribbon > >>> cable attached to the display). After plugging a monitor into the HDMI > >>> port, what I discovered was that the Pi boots using the display as > >>> console, then switches to the HDMI port for the X11 driver. (not useful) > >> > >> If you block the vc4 driver it will continue to work as a pure non > >> accelerated display, at the moment when the accelerated driver > >> initialises it can't detect the DSI attached display so it goes blank. > > OK, so I added the vc4 module with a "blacklist vc4" in my modprobe stuff. > > > So if I blacklist the vc4 driver, will an X11 session start up on the > > display? If not, can I modify the boot up to bring Linux up in command > > line only mode? Will the virtual consoles work in that mode? > > Yes, the HDMI stuff is now disabled and a non-accelerated X11 server > starts up. Yeah, its a little small @ 800x480. BUT IT WORKS! > > > I don't (yet) understand the uboot stuff. In a PC, I can interrupt grub > > and edit the command line to put kernel options on the boot line. I > > don't know how to do that with uboot. > > I found the /boot/extlinux/extlinux.conf file, and made by hand > modifications there to get where I am. > > Happy that I don't NEED an HDMI screen anymore, and X11 runs on the > display. YEA! > > Peter, thanks for the pointers! > _______________________________________________ > arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
