On Sat, Jun 16, 2018 at 7:11 PM, Samuel Sieb wrote:
> On 06/16/2018 09:05 AM, Alex wrote:
>>
>> Hi all, this appears to be a problem with the latest kernels and
>> Radeon cards (at least). Adding 'nomodeset' to the kernel command-line
>> fixes it.
>
> What video device do you have? Look in the ou
On 06/16/2018 09:05 AM, Alex wrote:
Hi all, this appears to be a problem with the latest kernels and
Radeon cards (at least). Adding 'nomodeset' to the kernel command-line
fixes it.
What video device do you have? Look in the output of "lspci" for a line
containing "VGA".
Hi all, this appears to be a problem with the latest kernels and
Radeon cards (at least). Adding 'nomodeset' to the kernel command-line
fixes it.
Has anyone else experienced this where the screen goes blank shortly
after booting and is completely unresponsive?
On Tue, Jun 12, 2018 at 11:10 PM, E
On 06/13/18 10:47, Alex wrote:
> Hi,
>
> On Tue, Jun 12, 2018 at 6:16 PM, Ed Greshko wrote:
>> On 06/13/18 04:45, Alex wrote:
>>> Hi,
>>> I have a fedora27 system on an older x86_64 machine and when booting
>>> the latest kernel (I believe it was just released today) as well as
>>> the previous tw
Hi,
On Tue, Jun 12, 2018 at 6:16 PM, Ed Greshko wrote:
> On 06/13/18 04:45, Alex wrote:
>> Hi,
>> I have a fedora27 system on an older x86_64 machine and when booting
>> the latest kernel (I believe it was just released today) as well as
>> the previous two, the display goes dark and becomes unre
No. During boot, on the main session shows what is transpiring,
but one of the other screens shows all the messages.
On 06/12/2018 06:00 PM, Samuel Sieb wrote:
On 06/12/2018 02:44 PM, Robert Moskowitz wrote:
Is it to get the log session or is it F6?
What log session? Are you thinking of
On 06/13/18 04:45, Alex wrote:
> Hi,
> I have a fedora27 system on an older x86_64 machine and when booting
> the latest kernel (I believe it was just released today) as well as
> the previous two, the display goes dark and becomes unresponsive.
>
> I've booted into the rescue kernel (an older 3.14
On 06/12/2018 02:44 PM, Robert Moskowitz wrote:
Is it to get the log session or is it F6?
What log session? Are you thinking of the installer?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.
Is it to get the log session or is it F6?
On 06/12/2018 05:09 PM, Samuel Sieb wrote:
On 06/12/2018 01:58 PM, Alex wrote:
Hi, I should add that I tried to boot into runlevel 3 and it made no
difference. How do I determine at what point it went to a black screen
and just stopped booting?
Can y
On 06/12/2018 01:58 PM, Alex wrote:
Hi, I should add that I tried to boot into runlevel 3 and it made no
difference. How do I determine at what point it went to a black screen
and just stopped booting?
Can you access it remotely using ssh?
You could try adding the "nomodeset" parameter to the k
Hi, I should add that I tried to boot into runlevel 3 and it made no
difference. How do I determine at what point it went to a black screen
and just stopped booting?
I also noticed there's a packagekit core dump, but is that enough to
prevent it from booting?
On Tue, Jun 12, 2018 at 4:45 PM, Alex
Hi,
I have a fedora27 system on an older x86_64 machine and when booting
the latest kernel (I believe it was just released today) as well as
the previous two, the display goes dark and becomes unresponsive.
I've booted into the rescue kernel (an older 3.14 from fc21) to get it
back online.
$ uname
12 matches
Mail list logo
