[opensuse-factory] Tumbleweed not booting for Radeon R9 380 card
I just installed a new Radeon R9 380 card today, and tried booting into Tumbleweed. Grub loaded without issue but when it was suppose to show the screen to input my LUKS password, only the following error messages appear: EDAC sbridge: ECC is disabled. Aborting EDAC sbridge: Couldn't find mci handler amdgpu 0000:03:00.0: Invalid ROM contents I have Ubuntu loaded in a separate partition to boot into which also briefly shows something similar, but immediately loads lightdm without issue. I would not the Ubuntu installation is running the proprietary drivers, but not Tumbleweed. What packages am I suppose to install to get the card working properly on Tumbleweed?
On Wednesday 20 Jan 2016 20:50:13 Chan Ju Ping wrote:
I just installed a new Radeon R9 380 card today, and tried booting into Tumbleweed. Grub loaded without issue but when it was suppose to show the screen to input my LUKS password, only the following error messages appear:
EDAC sbridge: ECC is disabled. Aborting EDAC sbridge: Couldn't find mci handler amdgpu 0000:03:00.0: Invalid ROM contents
I have Ubuntu loaded in a separate partition to boot into which also briefly shows something similar, but immediately loads lightdm without issue. I would not the Ubuntu installation is running the proprietary drivers, but not Tumbleweed.
What packages am I suppose to install to get the card working properly on Tumbleweed?
Sorry, I meant Ubuntu is running the fglrx drivers but not Tumbleweed. Sort of garbled my sentence there.
On Wednesday 20 January 2016 20.55:29 Chan Ju Ping wrote:
On Wednesday 20 Jan 2016 20:50:13 Chan Ju Ping wrote:
I just installed a new Radeon R9 380 card today, and tried booting into Tumbleweed. Grub loaded without issue but when it was suppose to show the screen to input my LUKS password, only the following error messages appear:
EDAC sbridge: ECC is disabled. Aborting EDAC sbridge: Couldn't find mci handler amdgpu 0000:03:00.0: Invalid ROM contents
I have Ubuntu loaded in a separate partition to boot into which also briefly shows something similar, but immediately loads lightdm without issue. I would not the Ubuntu installation is running the proprietary drivers, but not Tumbleweed.
What packages am I suppose to install to get the card working properly on Tumbleweed?
Sorry, I meant Ubuntu is running the fglrx drivers but not Tumbleweed. Sort of garbled my sentence there.
I don't know if the last fglrx packaged I have can really help with the newer card repo http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_Tumbleweed/ wiki page https://en.opensuse.org/SDB:AMD_fglrx It's not the latest published by AMD, (end of december), but I didn't get news from our script maintainer Sebastian Siebert, which normall include special patches to make fglrx working with very recent kernel. At least the rpm version can be cleanup easily. For tumbleweed, I really recommends to use the free drivers (but sometimes this one lack good support for latest chips). Perhaps you can edit your boot line (type e on the grub line) use arrow to move to kernel line and add a nomodeset You didn't tell us what was the previous card installed. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot
On Thursday 21 Jan 2016 08:48:42 Bruno Friedmann wrote:
On Wednesday 20 January 2016 20.55:29 Chan Ju Ping wrote:
On Wednesday 20 Jan 2016 20:50:13 Chan Ju Ping wrote:
I just installed a new Radeon R9 380 card today, and tried booting into Tumbleweed. Grub loaded without issue but when it was suppose to show the screen to input my LUKS password, only the following error messages appear:
EDAC sbridge: ECC is disabled. Aborting EDAC sbridge: Couldn't find mci handler amdgpu 0000:03:00.0: Invalid ROM contents
I have Ubuntu loaded in a separate partition to boot into which also briefly shows something similar, but immediately loads lightdm without issue. I would not the Ubuntu installation is running the proprietary drivers, but not Tumbleweed.
What packages am I suppose to install to get the card working properly on Tumbleweed?
Sorry, I meant Ubuntu is running the fglrx drivers but not Tumbleweed. Sort of garbled my sentence there.
I don't know if the last fglrx packaged I have can really help with the newer card repo http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_Tumbleweed/
wiki page https://en.opensuse.org/SDB:AMD_fglrx
It's not the latest published by AMD, (end of december), but I didn't get news from our script maintainer Sebastian Siebert, which normall include special patches to make fglrx working with very recent kernel. At least the rpm version can be cleanup easily.
For tumbleweed, I really recommends to use the free drivers (but sometimes this one lack good support for latest chips).
Quite so. I learnt it the hard way that the proprietary drivers are hard to set up correctly last year for Tumbleweed. Don't really want to repeat the experience.
Perhaps you can edit your boot line (type e on the grub line) use arrow to move to kernel line and add a nomodeset
Thanks. With this I can boot into Tumbleweed, though the video drivers being loaded appear to be the unoptimised ones, as my screen is lagging quite badly. I am running updates now to see if anything is fixed.
You didn't tell us what was the previous card installed.
The previous working card was the Radeon HD 5450. It was a reliable workhorse that gave me no issues. I bought it to replace an R9 270X card that occasionally failed to output anything onto the screen while running.
Quite so. I learnt it the hard way that the proprietary drivers are hard to set up correctly last year for Tumbleweed. Don't really want to repeat the experience.
openSUSE Tumbleweed has newer xorg version 1.18 than is supported by the driver at the moment. AMD drivers supports version up to 1.17. See AMD release note: http://support.amd.com/en-us/kb-articles/Pages/AMDRadeonSoftwareCrimsonEditi... """" Before attempting to install the AMD Radeon Software Crimson Edition 15.12 Proprietary Linux Graphics Driver, the following software must be installed: Xorg/Xserver 7.4 and above (up to 1.17) Linux kernel 2.6 or above (up to 3.19) glibc version 2.2 or 2.3 POSIX Shared Memory (/dev/shm) support is required for 3D applications """ If you want to use TW and AMD proprietary drivers, you can add repos from Leap 42.1, downgrade xorg and related packages. Lock downgraded packages, remove Leap repos, install driver and reboot. You will have unsupported "hybrid" system, but it will work. Here is the list of packages which should downgraded and locked: $ zypper ll # | Name | Type | Repository ---+-----------------------+---------+----------- 1 | xorg-x11-server | package | (any) 2 | xf86-input-evdev | package | (any) 3 | xf86-input-joystick | package | (any) 4 | xf86-input-keyboard | package | (any) 5 | xf86-input-mouse | package | (any) 6 | xf86-input-synaptics | package | (any) 7 | xf86-input-vmmouse | package | (any) 8 | xf86-input-void | package | (any) 9 | xf86-input-wacom | package | (any) 10 | xf86-video-ati | package | (any) 11 | xf86-video-fbdev | package | (any) 12 | xf86-video-vesa | package | (any) 13 | xorg-x11-driver-input | package | (any) 14 | xorg-x11-driver-video | package | (any) See the comment from Sebastian on page: https://www.sebastian-siebert.de/2015/12/05/opensuse-proprietaeren-grafik-tr... I have ASUS 380x and above thing works :) (having crossed fingers each tw update) If you want to use amdgpu driver, check following bug: https://bugzilla.opensuse.org/show_bug.cgi?id=956181 Basically create file /etc/X11/xorg.conf.d/10-amdgpu.conf with: Section "OutputClass" Identifier "AMDgpu" MatchDriver "amdgpu" Driver "amdgpu" EndSection This will help X11 to detect amdgpu card and solve mouse issue etc... (of course 3D performance will be very, very poor) Regards, Petr -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thu, Jan 21, 2016 at 4:37 PM, Petr Červinka <petr@cervinka.net> wrote:
If you want to use amdgpu driver, check following bug: https://bugzilla.opensuse.org/show_bug.cgi?id=956181
Basically create file /etc/X11/xorg.conf.d/10-amdgpu.conf with: Section "OutputClass" Identifier "AMDgpu" MatchDriver "amdgpu" Driver "amdgpu" EndSection
This will help X11 to detect amdgpu card and solve mouse issue etc... (of course 3D performance will be very, very poor)
Just for everyone, who is interested. I tested in tumbleweed kernel 4.5rc1 from HEAD repo and it works nicely. Kernel 4.5 has already powerplay support for amdgpu driver(disabled by default, but can be enabled during boot GRUB_CMDLINE_LINUX="amdgpu.powerplay=1"). There is very positive impact on performance. Still slower (10-15%) than fglrx drivers, but games are playable. So when is kernel 4.5 fully out, we will be able to R9380 cards without dirty workarounds for binary drivers. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday 21 Jan 2016 08:56:23 Chan Ju Ping wrote:
On Thursday 21 Jan 2016 08:48:42 Bruno Friedmann wrote:
On Wednesday 20 January 2016 20.55:29 Chan Ju Ping wrote:
On Wednesday 20 Jan 2016 20:50:13 Chan Ju Ping wrote:
I just installed a new Radeon R9 380 card today, and tried booting into Tumbleweed. Grub loaded without issue but when it was suppose to show the screen to input my LUKS password, only the following error messages appear:
EDAC sbridge: ECC is disabled. Aborting EDAC sbridge: Couldn't find mci handler amdgpu 0000:03:00.0: Invalid ROM contents
I have Ubuntu loaded in a separate partition to boot into which also briefly shows something similar, but immediately loads lightdm without issue. I would not the Ubuntu installation is running the proprietary drivers, but not Tumbleweed.
What packages am I suppose to install to get the card working properly on Tumbleweed?
Sorry, I meant Ubuntu is running the fglrx drivers but not Tumbleweed. Sort of garbled my sentence there.
I don't know if the last fglrx packaged I have can really help with the newer card repo http://geeko.ioda.net/mirror/amd-fglrx/openSUSE_Tumbleweed/
wiki page https://en.opensuse.org/SDB:AMD_fglrx
It's not the latest published by AMD, (end of december), but I didn't get news from our script maintainer Sebastian Siebert, which normall include special patches to make fglrx working with very recent kernel. At least the rpm version can be cleanup easily.
For tumbleweed, I really recommends to use the free drivers (but sometimes this one lack good support for latest chips).
Quite so. I learnt it the hard way that the proprietary drivers are hard to set up correctly last year for Tumbleweed. Don't really want to repeat the experience.
Perhaps you can edit your boot line (type e on the grub line) use arrow to move to kernel line and add a nomodeset
Thanks. With this I can boot into Tumbleweed, though the video drivers being loaded appear to be the unoptimised ones, as my screen is lagging quite badly. I am running updates now to see if anything is fixed.
You didn't tell us what was the previous card installed.
The previous working card was the Radeon HD 5450. It was a reliable workhorse that gave me no issues. I bought it to replace an R9 270X card that occasionally failed to output anything onto the screen while running.
This could be a case of superbly bad timing. At the same time I managed to enter and run the update, the terminal output showed I have run out of diskspace. A quick check showed I had ran out of inode space, probably because all of the old kernels are still installed! I had assumed Tumbleweed would automatically remove old kernels but that appears to not be the case. I cannot get yast2 to run as sudo in tty1, and though the desktop ran briefly it is now a blank screen once more. I want to be careful about not borking my installation, so how should I proceed from here?
On Thu, Jan 21, 2016 at 01:16:47PM -0600, Chan Ju Ping wrote: [ 8< ]
This could be a case of superbly bad timing. At the same time I managed to enter and run the update, the terminal output showed I have run out of diskspace. A quick check showed I had ran out of inode space, probably because all of the old kernels are still installed!
a) Enable and call purge-kernels.service (part of the dracut package) Is the service enabled? systemctl is-enabled purge-kernels.service If not enabled enable it: systemctl enable purge-kernels.service Start purge-kernels service now systemctl start purge-kernels.service This is done if /boot/do_purge_kernels exists. By default the running and most current kernel are kept installed (ConditionPathExists in the purge-kernels.service file). b) check if your / fs isn't full full due to snapshots This might happen if it is on btrfs and snapper is active. btrfs filesystem df / or in more detail btrfs filesystem usage /
I had assumed Tumbleweed would automatically remove old kernels but that appears to not be the case.
Tumbleweed and openSUSE in general do this. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On Thursday 21 Jan 2016 22:07:25 Lars Müller wrote:
On Thu, Jan 21, 2016 at 01:16:47PM -0600, Chan Ju Ping wrote: [ 8< ]
This could be a case of superbly bad timing. At the same time I managed to enter and run the update, the terminal output showed I have run out of diskspace. A quick check showed I had ran out of inode space, probably because all of the old kernels are still installed!
a) Enable and call purge-kernels.service (part of the dracut package)
Is the service enabled?
systemctl is-enabled purge-kernels.service
If not enabled enable it:
systemctl enable purge-kernels.service
Haha. It was disabled. Now re-enabled.
Start purge-kernels service now
systemctl start purge-kernels.service
This is done if /boot/do_purge_kernels exists.
By default the running and most current kernel are kept installed (ConditionPathExists in the purge-kernels.service file).
b) check if your / fs isn't full full due to snapshots
This might happen if it is on btrfs and snapper is active.
btrfs filesystem df /
or in more detail
btrfs filesystem usage /
I have Snapper running, and I removed a few snapshots to free up inode space. Though snapper actually does a good job of keeping snapshot numbers low.
I had assumed Tumbleweed would automatically remove old kernels but that appears to not be the case.
Tumbleweed and openSUSE in general do this.
Cheers,
Lars
Thanks for the assistance. I was able to clear up some space so the GUI could load, then forced a rebuild of the rpm database (because some of the kernels were not removable) with zypper refresh -fdb I will now check my other laptop running Tumbleweed to make sure the purge- kernels.service is also enabled.
On Thursday 21 Jan 2016 16:32:57 Chan Ju Ping wrote:
On Thursday 21 Jan 2016 22:07:25 Lars Müller wrote:
On Thu, Jan 21, 2016 at 01:16:47PM -0600, Chan Ju Ping wrote: [ 8< ]
This could be a case of superbly bad timing. At the same time I managed to enter and run the update, the terminal output showed I have run out of diskspace. A quick check showed I had ran out of inode space, probably because all of the old kernels are still installed!
a) Enable and call purge-kernels.service (part of the dracut package)
Is the service enabled?
systemctl is-enabled purge-kernels.service
If not enabled enable it: systemctl enable purge-kernels.service
Haha. It was disabled. Now re-enabled.
Start purge-kernels service now
systemctl start purge-kernels.service
This is done if /boot/do_purge_kernels exists.
By default the running and most current kernel are kept installed (ConditionPathExists in the purge-kernels.service file).
b) check if your / fs isn't full full due to snapshots
This might happen if it is on btrfs and snapper is active.
btrfs filesystem df /
or in more detail
btrfs filesystem usage /
I have Snapper running, and I removed a few snapshots to free up inode space. Though snapper actually does a good job of keeping snapshot numbers low.
I had assumed Tumbleweed would automatically remove old kernels but that appears to not be the case.
Tumbleweed and openSUSE in general do this.
Cheers,
Lars
Thanks for the assistance. I was able to clear up some space so the GUI could load, then forced a rebuild of the rpm database (because some of the kernels were not removable) with
zypper refresh -fdb
I will now check my other laptop running Tumbleweed to make sure the purge- kernels.service is also enabled.
I have renamed this thread to the more appropriate problem at hand. I just checked my other computer running TW (brand new setup from a couple of months ago), and the purge-kernels service is disabled and inactive in the Yast Services Manager. I don't know how many users may be potentially impacted by this setting, but it may be necessary to check to make sure it is active.
participants (4)
-
Bruno Friedmann -
Chan Ju Ping -
Lars Müller -
Petr Červinka