Bug #2181
linux-libre missing amdgpu radeon modules
0%
Description
I can boot with linux-libre and get to the login prompt (no display manager here). When I run exec startx, I get no image. It seems that linux-libre 4.20.10-gnu-1 comes without amdgpu and radeon modules:
# mkinitcpio -p linux-libre ==> ERROR: module not found: `amdgpu' ==> ERROR: module not found: `radeon'
Let me know what other information is needed. Kernel 4.9.127-gnu-1-lts-xtreme works fine. I think that the last one that worked well for me was linux-libre 4.20.6-gnu-1.
Thanks!
Files
History
Updated by freemor about 5 years ago
X should start even without accel modules.
What you describe sounds like:
there is nothing in your .xinitrc file
or
You do not have xorg, xorg-drivers, or both installed. You'll probably want to be sure xterm is installed as a lot of things default to that too.
Updated by freemor about 5 years ago
If X tries to start but fails then please attach your Xorg.0.log here
Updated by nona about 5 years ago
I am using a graphical environment with linux-libre-lts-xtreme right now with the same computer, which indicates that my .xinitrc, xorg and xorg-drivers are there. I also have this:
pacman -Qs xorg-drivers
local/xf86-input-libinput 0.28.2-1 (xorg-drivers)
Generic input driver for the X.Org server based on libinput
local/xf86-input-synaptics 1.9.1-1 (xorg-drivers)
Synaptics driver for notebook touchpads
local/xf86-video-amdgpu 18.1.0-1 (xorg-drivers)
X.org amdgpu video driver
local/xf86-video-intel 1:2.99.917+859+g33ee0c3b-1 (xorg-drivers)
X.org Intel i810/i830/i915/945G/G965+ video drivers
local/xf86-video-vesa 2.4.0-2 (xorg-drivers xorg)
X.org vesa video driver
I can also run xterm
Updated by nona about 5 years ago
- File Xorg.0.logbug Xorg.0.logbug added
freemor wrote:
If X tries to start but fails then please attach your Xorg.0.log here
:)
Updated by bill-auger about 5 years ago
- Assignee set to Megver83
- Status changed from unconfirmed to confirmed
causes ISO builds to fail in the mkinitcpio phase
[mkparabolaiso] INFO: Configuration settings [mkparabolaiso] INFO: Command: run [mkparabolaiso] INFO: Architecture: x86_64 [mkparabolaiso] INFO: Working directory: ./work/x86_64 [mkparabolaiso] INFO: Installation directory: parabola [mkparabolaiso] INFO: Run command: mkinitcpio -c /etc/mkinitcpio-parabolaiso.conf -k /boot/vmlinuz-linux-libre -g /boot/parabolaiso.img [mkparabolaiso] INFO: Offline install: false ==> Starting build: 4.20.10-gnu-1 -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [memdisk] -> Running build hook: [parabolaiso_shutdown] -> Running build hook: [parabolaiso] -> Running build hook: [parabolaiso_loop_mnt] -> Running build hook: [parabolaiso_pxe_common] -> Running build hook: [parabolaiso_pxe_nbd] -> Running build hook: [parabolaiso_pxe_http] -> Running build hook: [parabolaiso_pxe_nfs] -> Running build hook: [parabolaiso_kms] ==> ERROR: module not found: `radeon' -> Running build hook: [block] -> Running build hook: [filesystems] -> Running build hook: [keyboard] ==> Generating module dependencies
Updated by freemor about 5 years ago
Nona thanks for posting the Xorg.logs those show that X does indeed start in Vesa mode As I thought it should. Not sure why you aren't seeeing an image. Perhaps it's choosing the wrong sync rate.
That aside for the moment My system has both radeon and amdgpu modules available and I can modprobe both sucessfully.
Can you manually modprobe the modules you need into place and then startx?
I'll try poking at mkinitcpio and see why it can't find modules that modprobe finds no problem.
Updated by freemor about 5 years ago
I was able to add both modules to /etc/mkinitcpio.conf
rebuild the initcpio with mkinitcpio -p linux-libre
and then rebooting the VM pulls them both in fine.
nona, if you are comfortable doing so can you please try these steps. after first ensuring that you can namually modprobe them.
Updated by freemor about 5 years ago
Spoke too soon..
Seems my VM. And main machine are not as up-to-date as I thought
When I tried to bring the VM current (1 kernel behind) it Threw the Radeon/amdgpu errors
This seems to be a very recently introduced glitch
Updated by nona about 5 years ago
freemor wrote:
Spoke too soon..
Seems my VM. And main machine are not as up-to-date as I thought
When I tried to bring the VM current (1 kernel behind) it Threw the Radeon/amdgpu errors
This seems to be a very recently introduced glitch
I tried what you asked, nonetheless. It is not possible to load the modules. If you look at the contents of the package, usr/lib/modules/4.20.10-gnu-1/kernel/drivers/gpu/drm/amd is missing. This exists in the 4.20.6-gnu-1 version.
I am downgrading for the moment (hope that it does not break anything).
Updated by Megver83 about 5 years ago
amdgpu and radeon is enabled in linux-libre-lts and linux-libre-rt.
Anyways, these modules seemed useless
https://lists.gnu.org/archive/html/info-gnu/2015-08/msg00010.html
The greatest new offender is amdgpu that, like radeon, refuses to work
at all without blobs, even though in theory it could offer degraded
functionality.
Now, if you probe them to be useful for something, I can enable amdgpu and radeon for all kernels.
When I run exec startx, I get no image.
hmmm, do you have xf86-video-amdgpu enabled?
freemor wrote:
Spoke too soon..
Seems my VM. And main machine are not as up-to-date as I thought
When I tried to bring the VM current (1 kernel behind) it Threw the Radeon/amdgpu errors
This seems to be a very recently introduced glitch
Could you attach the dmesg log then? and also, please give me more details about how it affected you.
P.S.: linux-libre-lts-xtreme is deprecated, btw
https://git.parabola.nu/abslibre.git/commit/?id=b7655233437453509659e40fcf319dcff8936085
Updated by nona about 5 years ago
Megver83 wrote:
amdgpu and radeon is enabled in linux-libre-lts and linux-libre-rt.
Ok
Anyways, these modules seemed useless
https://lists.gnu.org/archive/html/info-gnu/2015-08/msg00010.htmlThe greatest new offender is amdgpu that, like radeon, refuses to work
at all without blobs, even though in theory it could offer degraded
functionality.
What trickery!
Now, if you probe them to be useful for something, I can enable amdgpu and radeon for all kernels.
Good point. I can't even use the f*king HDMI. I just hope that nothing breaks.
hmmm, do you have xf86-video-amdgpu enabled?
I had it installed, and amdgpu shows up in lsmod. Is that what you mean? I am going to test linux-libre-lts (without MODULES=(amdgpu radeon) in mkinitcpio.conf)
P.S.: linux-libre-lts-xtreme is deprecated, btw
https://git.parabola.nu/abslibre.git/commit/?id=b7655233437453509659e40fcf319dcff8936085
Mmm... ok
Anybody wants to buy a laptop? ;)
Updated by nona about 5 years ago
nona wrote:
Megver83 wrote:
P.S.: linux-libre-lts-xtreme is deprecated, btw
https://git.parabola.nu/abslibre.git/commit/?id=b7655233437453509659e40fcf319dcff8936085
- Remove amdgpu and radeon from MODULES in mkinitcpio.conf
- pacman -S linux-libre-lts
- grub-mkconfig -o /boot/grub/grub.cfg (keep amd_iommu=on in kernel line; within /etc/default/grub)
- Restart
- Grub menu shows up
- Kernel boots
- I get a prompt for the crypt password
- half-way in the booting process it would seem like a hang happens (showing OpenRC start up),
- Wait a bit and I can later input my user and password (without knowing what is going on)
- then I see my graphic session.
The half-way is actually an improvement from linux-libre, which only gives me a blank screen. However, linux-libre-lts-xtreme does not have that glitch. Also, recoll (and whatever is linked to libQt5Core.so.5) works, which did not work in -lts-xtreme.
Thus: I can live without AMDGPU in the kernel. One less blob, I guess. Thank you!
I will now mkinitcpio -p linux-libre to see if I still have issues with that. I'll report later.
Updated by nona about 5 years ago
nona wrote:
nona wrote:
I will now mkinitcpio -p linux-libre to see if I still have issues with that. I'll report later.
You can mark this as solved! Thanks again :)
Updated by bill-auger about 5 years ago
megver -
for parabolaiso, i deleted 'add_module "radeon"' from the KMS modules install hook1 - that allowed the build to complete
is that the proper solution going forward?
Updated by Megver83 about 5 years ago
- Status changed from confirmed to fixed
nona wrote:
nona wrote:
nona wrote:
I will now mkinitcpio -p linux-libre to see if I still have issues with that. I'll report later.You can mark this as solved! Thanks again :)
Right, remember that if you've any other Parabola kernels specific problem you can report it here or in the mailing list, and any linux-libre specific issue will be better to write to linux-libre's mailing list
bill-auger wrote:
megver -
for parabolaiso, i deleted 'add_module "radeon"' from the KMS modules install hook1 - that allowed the build to complete
is that the proper solution going forward?
We've to track this, if no one reports anything, then we should not give it importance. Anyways, as I said before, our lts kernels (linux-libre-lts and linux-libre-rt) have amdgpu and radeon enabled just in case (only for this last 4.19 generation, in the next one I'll remove it if no one reports similar issues to this)
Updated by oaken-source about 5 years ago
Megver, are you sure that removing amdgpu and radeon entirely is a good way forward? from what I quickly skimmed here1, there seems to be at least some cards that are supported.
[1] - https://www.fsfla.org/ikiwiki/selibre/linux-libre/Updated by Megver83 about 5 years ago
oaken-source wrote:
Megver, are you sure that removing amdgpu and radeon entirely is a good way forward? from what I quickly skimmed here1, there seems to be at least some cards that are supported.
As we discussed in IRC, I'll re-enable them for the next releases