| View previous topic :: View next topic |
| Author |
Message |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54232
Location: 56N 3W
|
 Posted: Fri Nov 10, 2017 8:45 am Post subject: |
 |
|
Thanatos2996,
I think your system is complaining about
| Code: | | CONFIG_VGA_CONSOLE=y |
It might be any of | Code: | CONFIG_FB_VGA16=m
CONFIG_FB_UVESA=m
CONFIG_FB_VESA=y |
UVESA is incomplete. The user space part has been dropped.
I would do these changes in two goes. Rewove the extra frambuffer drivers that you can't use then test.
Lastly, remove CONFIG_VGA_CONSOLE. If this fails, nomodeset will get you a blank screen.
Your kernel has support for | Code: | [ 0.971580] console [netcon0] enabled
[ 0.971722] netconsole: network logging started |
but its probably started after drm.
The network console offers a way to capture at least a part of the boot messages.
To be sure of getting the interesting part you would need to make CONFIG_DRM_AMDGPU=y a module, and the network console built in so you can be sure the console starts before fhe problem.
A serial console is another possibility to capture dmesg but that needs some obsolete hardware.
I've used serial console but never the network console.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
 |
azp
Guru
Joined: 16 Nov 2003
Posts: 456
Location: Sweden
|
| Posted: Wed Jan 17, 2018 9:20 pm Post subject: |
|
|
I'm running the FOSS AMDGPU driver on my AMD R290 card (works great, and has been doing so for more than a year). I noticed that I got errors related to uvesafb during boot and realized I wasn't even using it, although it was compiled into the kernel, which felt very unnecessary, so now I'm trying to "optimize" my framebuffer/KMS experience and I'm quite confused by the previous post. So just to make it completely clear (since I find the wiki a little bit lacking):
(I'm running the 4.14.12 kernel)
1. Should I have any framebuffer driver enabled in the kernel, or does the amdgpu driver handle the KMS for the console as well? From the Arch wiki, I get the impression that the amdgpu driver handles everything now. (https://wiki.archlinux.org/index.php/kernel_mode_setting)
2. If "Yes, you should have vesafb/vga16 enabled", which one is best?
3. What about the radeonfb? Is it completely deprecated or is it for older (pre-KMS?) cards?
I tried disabling all framebuffer devices and the computer boots properly, but I then don't get any console at all. It goes from Grub -> goes black (screen switches of with "No input") for a couple of seconds -> Goes directly into GDM.
_________________
Weeks of coding can save you hours of planning. |
|
| Back to top |
|
|
azp
Guru
Joined: 16 Nov 2003
Posts: 456
Location: Sweden
|
| Posted: Tue Jan 30, 2018 2:02 pm Post subject: |
|
|
I found the guide on the Gentoo wiki, which said I should have the legacy fbdev driver enabled to get the proper support in the AMDGPU driver:
| Code: | | [*] Enable legacy fbdev support for your modesetting driver |
Perhaps it shouldn't be called 'legacy' anymore?
_________________
Weeks of coding can save you hours of planning. |
|
| Back to top |
|
|
azp
Guru
Joined: 16 Nov 2003
Posts: 456
Location: Sweden
|
| Posted: Sun Feb 18, 2018 11:56 am Post subject: |
|
|
When running with ONLY the amdgpu driver, combined with "Enable legacy fbdev support for your modesetting driver" I'm not getting modesetting directly from the start, but a couple of seconds in. Is it supposed to be like that? I have compiled my drivers into the kernel, and not as modules.
_________________
Weeks of coding can save you hours of planning. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
