Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #199725 > unrolled thread

Buster: "cannot run in framebuffer mode"

Started byLucio <lucio@sulweb.org>
First post2018-09-03 09:00 +0200
Last post2018-09-04 09:50 +0200
Articles 4 — 2 participants

Back to article view | Back to linux.debian.user


Contents

  Buster: "cannot run in framebuffer mode" Lucio <lucio@sulweb.org> - 2018-09-03 09:00 +0200
    Re: Buster: "cannot run in framebuffer mode" Felix Miata <mrmazda@earthlink.net> - 2018-09-03 09:50 +0200
      Re: Buster: "cannot run in framebuffer mode" Lucio <lucio@sulweb.org> - 2018-09-03 10:40 +0200
        Re: Buster: "cannot run in framebuffer mode" Lucio <lucio@sulweb.org> - 2018-09-04 09:50 +0200

#199725 — Buster: "cannot run in framebuffer mode"

FromLucio <lucio@sulweb.org>
Date2018-09-03 09:00 +0200
SubjectBuster: "cannot run in framebuffer mode"
Message-ID<wtR06-3fH-1@gated-at.bofh.it>
I have two different Debian Buster/sid systems. The first is a desktop 
PC with AMD RX 580 graphics. It used to work ok until July, then I 
updated it sometime in August, and Xorg broke.

The second is an Acer Aspire5 notebook I've just bought, with AMD RX 540 
graphics. I've installed Debian using the latest Debian Buster testing 
ISO (August 27th, as today's one wasn't available yet), and Xorg doesn't 
start.

Both Xorg.0.log show the same error:

Fatal server error:
Cannot run in framebuffer mode please supply the busIds for all 
framebuffer devices

Both systems run the 4.17 amd64 kernel, but I've also tried a custom 
4.18 kernel on the desktop system, with the same results.

I could find a number of references to that error out there, but all of 
them point either to a solution that does not work in my cases (e.g. 
adding "amdgpu.cik_support=1 radeon.cik_support=0" to the kernel 
comdline) or to a old and already closed bug report, (e.g. 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508476)

I'd suspect fbdev was somehow guilty, but the fbdev module isn't even 
listed by lsmod.

I've already tried creating a /etc/X11/xorg.conf file, using

# Xorg -configure

but it didn't solve the problem.

Any clues?

[toc] | [next] | [standalone]


#199726

FromFelix Miata <mrmazda@earthlink.net>
Date2018-09-03 09:50 +0200
Message-ID<wtRMt-3JR-7@gated-at.bofh.it>
In reply to#199725
Lucio composed on 2018-09-03 08:52 (UTC+0200):

> I have two different Debian Buster/sid systems. The first is a desktop 
> PC with AMD RX 580 graphics. It used to work ok until July, then I 
> updated it sometime in August, and Xorg broke.

> The second is an Acer Aspire5 notebook I've just bought, with AMD RX 540 
> graphics. I've installed Debian using the latest Debian Buster testing 
> ISO (August 27th, as today's one wasn't available yet), and Xorg doesn't 
> start.

> Both Xorg.0.log show the same error:

> Fatal server error:
> Cannot run in framebuffer mode please supply the busIds for all 
> framebuffer devices

> Both systems run the 4.17 amd64 kernel, but I've also tried a custom 
> 4.18 kernel on the desktop system, with the same results.

> I could find a number of references to that error out there, but all of 
> them point either to a solution that does not work in my cases (e.g. 
> adding "amdgpu.cik_support=1 radeon.cik_support=0" to the kernel 
> comdline) or to a old and already closed bug report, (e.g. 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508476)

> I'd suspect fbdev was somehow guilty, but the fbdev module isn't even 
> listed by lsmod.

fbdev is an xorg driver provided by xserver-xorg-video-fbdev, not to be confused
with the kernel's framebuffer, /dev/fb0.

> I've already tried creating a /etc/X11/xorg.conf file, using

> # Xorg -configure

That's an anachronism rarely useful for any purpose any more.

> but it didn't solve the problem.

Does /dev/fb0 exist? If not, likely you are missing firmware the AMD gfxcards
depend on, most likely firmware-amd-graphics.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]


#199727

FromLucio <lucio@sulweb.org>
Date2018-09-03 10:40 +0200
Message-ID<wtSyR-4eh-9@gated-at.bofh.it>
In reply to#199726
On 03/09/18 09:46, Felix Miata wrote:
> Does /dev/fb0 exist?

I can't check the notebook just now, but in the desktop system yes, it 
exists and the firmware-amd-graphics package was already installed.

[toc] | [prev] | [next] | [standalone]


#199742

FromLucio <lucio@sulweb.org>
Date2018-09-04 09:50 +0200
Message-ID<wueg1-8qa-7@gated-at.bofh.it>
In reply to#199727
On 03/09/18 10:33, Lucio wrote:
> On 03/09/18 09:46, Felix Miata wrote:
>> Does /dev/fb0 exist?
> 
> I can't check the notebook just now, but in the desktop system yes, it 
> exists and the firmware-amd-graphics package was already installed.
> 

The notebook was missing the firmware-amd-graphics package, but please 
note that /dev/fb0 existed even before installing it.

Now that's installed the situation is probably worse: Xorg manages to 
start, lightdm shows up and then the notebook suddendly reboots, so I 
have a boot loop, because now Xorg and lightdm start automatically.

Actually I know how to boot in single user mode and avoid the boot loop, 
but I'm not sure about what to do next. Maybe I'll try with a less 
recent kernel.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web