I have done that and I am happy to report that, with the new kernel 4.5.5-300
this bug is resolved to my complete satisfaction :-)
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
On Sun, 2016-05-22 at 17:33 -0600, P. Gueckel wrote:
> Adam Williamson wrote:
>
> > In this case it worked out, and in fact was correct
> as the issue turns
> > out to be in some ways Fedora-specific, but
> generally speaking I
> > usually recommend filing graphics issues upstream
> these days
Adam Williamson wrote:
> In this case it worked out, and in fact was correct
as the issue turns
> out to be in some ways Fedora-specific, but
generally speaking I
> usually recommend filing graphics issues upstream
these days, as there
> are a lot more devs following upstream trackers than
RHB
On Sat, 2016-05-21 at 08:11 -0600, Peter G. wrote:
> Adam Williamson wrote:
>
> > That's a kernel crash. If you boot with 'nomodeset' added
> back you
> > should be able to report a bug for it. I can't remember if
> we have abrt
> > collection of kernel traces set up ATM; if not, you can
> jus
Adam Williamson wrote:
> That's a kernel crash. If you boot with 'nomodeset' added
back you
> should be able to report a bug for it. I can't remember if
we have abrt
> collection of kernel traces set up ATM; if not, you can
just file a bug
> at https://bugs.freedesktop.org (against xorg
Driver
If you have anything to add, I have made a bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1338076
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org
On Sat, 2016-05-21 at 07:41 -0600, Peter G. wrote:
> Then, suddenly, after a line appeared about GDM having
> started, or something like that, the screen flashed
> momentarily and new text appeared, all in white on black,
> with the name of my computer, Compaq, at the top. A fifth of
> the way
There's definitely a bug here!
First try, I removed nomodeset and I got the expected fedora
infinity and everything went well, just like in f23 and just
like in the regular anaconda installer on the live CD,
except...
GDM never starts! The computer just hangs. I cannot use ESC
to switch to th
That's lots of information and none of it conflicting. Thanks,
guys! I'll give it a try. It sounds very encouraging. This old
box isn't done yet ;-)
Yep, I realize that i686 is no longer supported, but I just
can't rationalize spending hundreds on a new laptop (or other
portable), considering
On 05/20/2016 05:04 PM, Peter G. wrote:
My suspicion is that, when I installed from the live CD, I
had trouble with the graphical mode, so I had to select the
graphics lite from the troubleshooting screen and somehow
this setting has been made permanent.
Yes, that would cause it. Check in the
On Fri, 2016-05-20 at 18:04 -0600, Peter G. wrote:
>
> When I select KDE, there is a lot of screen flashing (mode-
> setting?) and artifacts covering half of the screen, then the
> starfield background image appears and the KDE logo with the
> progress bar. It is all very jerky, not smooth, lik
On Fri, May 20, 2016 at 6:04 PM, Peter G. wrote:
> Is there a way I can tell the computer to boot in the proper
> mode right at the grub prompt, or even set it permanently?
At the grub menu, press e to edit the first entry, find the linux16
line, on that line there might be a nomodeset parameter
In F23, all went fine, but in F24, some video problems are
showing up.
After the grub menu, the machine is supposed to switch to the
framebuffer and the boot image (fedora infinity goes from
white to filled in) appears and one can switch to the boot
message display with ESC.
Well, not in F24
13 matches
Mail list logo
