Mobility Radeon HD 5730 driver now won't boot after reboot, can't get to console. Kubuntu 16.10

seedsca · 03-13-2017, 01:26 AM

All was working well until I rebooted. Nothing happened, only a black screen after leaving the grub screen.

Been trying for two days to get it back to working order. Tried the amdgpu drivers only to realize that my card is not compatible. Not really sure where to go from here...

Using the radeon from xserver-xorg-video-radeon version 7.7.1-1

Code:

uname -r
4.8.0-41-generic

Code:

sudo lspci -v -s 01:00.0
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5730 / 6570M] (prog-if 00 [VGA controller])
        Subsystem: Lenovo Mobility Radeon HD 5730
        Flags: bus master, fast devsel, latency 0, IRQ 10
        Memory at d0000000 (64-bit, prefetchable) [size=256M]
        Memory at e8400000 (64-bit, non-prefetchable) [size=128K]
        I/O ports at 2000 [size=256]
        [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Legacy Endpoint, MSI 00
        Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
        Kernel modules: radeon

Code:

dmesg | egrep 'drm|radeon'
[   47.900816] [drm] Initialized drm 1.1.0 20060810
[   48.349718] [drm] VGACON disable radeon kernel modesetting.
[   48.349756] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!

Code:

xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
   1024x768       0.00*

Code:

sudo lshw -c video
  *-display UNCLAIMED       
       description: VGA compatible controller
       product: Madison [Mobility Radeon HD 5730 / 6570M]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:01:00.0
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list
       configuration: latency=0
       resources: memory:d0000000-dfffffff memory:e8400000-e841ffff ioport:2000(size=256) memory:c0000-dffff

seedsca · 03-13-2017, 04:21 PM

This pastebin shows when this might have started. It's from the kern.log
In line 178 there is a segfault, followed by another. After that reboot, it all began.

I am also noticing that I can't boot to any OS. Not live CDs, not Windows installation (was going to try to re-install the BIOS)
Only way I can get boot "normally" is by using the nomodeset option under GRUB or "recovery mode". This allows me boot to either a live CD or my current Kubuntu 16.10.

ondoho · 03-14-2017, 12:59 AM

Quote:

Originally Posted by seedsca

Only way I can get boot "normally" is by using the nomodeset option under GRUB

ok, that's an important hint.

try a different driver? maybe the proprietary?

https://duckduckgo.com/?q=linux+Mobility+Radeon+HD+5730
doesn't look too good, 7 years ago there were problems, has linux support improved since then?

jsbjsb001 · 03-14-2017, 01:57 AM

You have disabled KMS (Kernel Mode Setting), re-enable it.

As I've been doing some googling (not duckduckgo) and have found some interesting results, have you seen any of them?

Google results: https://www.google.com.au/search?q=N...JKHr8Ae4wYmIDg

Look at this one: https://bbs.archlinux.org/viewtopic.php?id=182244

seedsca · 03-14-2017, 02:08 PM

ondoho: I can't seem to find drivers for my Kubuntu version, 16.10
The proprietary driver only supports up to 15.04 and the amdgpu only seems to support newer cards...

jsbjsb001: I've been looking for 3 days now and it has all become a swamp of possible answers

The ArchLinux link points to a TV out problem, not mine. I looked into enabling KMS but don't have a /etc/modprobe.d/radeon-kms file... Not sure where to go from there. I found a Debian page on Kernel ModeSetting but still no idea how to "enable it" I'll try the GRUB approach again. Though I did and all it seemed to do was give me a different resolution, but not a loaded driver and no dual monitors.

A concern of mine is that I can't boot to a Windows Install CD (As a test, been windows less for years now). The CD spins up but nothing ever comes up. Same with any other graphical interface, such as linux live cds, unless I set "nomodeset" in grub before booting...

Could the BIOS have been corrupted by the segfaults?

Thanks for your help! I'm swimming without a paddle here

jsbjsb001 · 03-14-2017, 09:21 PM

Quote:

Originally Posted by seedsca

ondoho: I can't seem to find drivers for my Kubuntu version, 16.10
The proprietary driver only supports up to 15.04 and the amdgpu only seems to support newer cards...

jsbjsb001: I've been looking for 3 days now and it has all become a swamp of possible answers

The ArchLinux link points to a TV out problem, not mine. I looked into enabling KMS but don't have a /etc/modprobe.d/radeon-kms file... Not sure where to go from there. I found a Debian page on Kernel ModeSetting but still no idea how to "enable it" I'll try the GRUB approach again. Though I did and all it seemed to do was give me a different resolution, but not a loaded driver and no dual monitors.

A concern of mine is that I can't boot to a Windows Install CD (As a test, been windows less for years now). The CD spins up but nothing ever comes up. Same with any other graphical interface, such as linux live cds, unless I set "nomodeset" in grub before booting...

Could the BIOS have been corrupted by the segfaults?

Thanks for your help! I'm swimming without a paddle here

No, I don't see how the BIOS could be corrupted by segfaults. You need to re-enable KMS, if you want your video card to work. As this is NOT optional from my reading (I have NVIDIA myself).

seedsca · 03-14-2017, 11:51 PM

The plot thickens!
So as I'm looking at the kern.log and syslog, i noticed something strange.
I can't troubleshoot this because when I try to use the normal boot process, meaning not using the GRUB "recovery mode" option. Nothing gets logged.

syslog: between 21:15:44 and 21:29:59 I did a normal boot and left the black screen on for 5 minutes.

Code:

Mar 14 21:15:44 OpenTop sddm[1526]: Socket server stopped.
Mar 14 21:15:44 OpenTop sddm[1526]: Display server stopping...
Mar 14 21:15:44 OpenTop systemd[1]: Stopping Session 3 of user sergio.
Mar 14 21:15:44 OpenTop rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1372" x-info="http://www.rsyslog.com"] exiting on signal 15.
Mar 14 21:29:59 OpenTop rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1211" x-info="http://www.rsyslog.com"] start
Mar 14 21:29:59 OpenTop rsyslogd: rsyslogd's groupid changed to 108
Mar 14 21:29:59 OpenTop rsyslogd: rsyslogd's userid changed to 104
Mar 14 21:29:59 OpenTop systemd[1]: Started Create Static Device Nodes in /dev.
Mar 14 21:29:59 OpenTop systemd[1]: Starting udev Kernel Device Manager...

kern.log:

Code:

Mar 14 21:15:44 OpenTop sddm[1526]: Socket server stopping...
Mar 14 21:15:44 OpenTop sddm[1526]: Socket server stopped.
Mar 14 21:15:44 OpenTop sddm[1526]: Display server stopping...
Mar 14 21:29:59 OpenTop kernel: [    0.000000] microcode: microcode updated early to revision 0x7, date = 2013-08-20
Mar 14 21:29:59 OpenTop kernel: [    0.000000] Linux version 4.8.0-41-generic (buildd@lgw01-18) (gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) ) #44-Ubuntu SMP Fri Mar 3 15:27:17 UTC 2017 (Ubuntu 4.8.0-41.44-generic 4.8.17)
Mar 14 21:29:59 OpenTop kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=c2315734-698e-4b0a-a7a0-7f206d79558c ro recovery nomodeset
Mar 14 21:29:59 OpenTop kernel: [    0.000000] KERNEL supported cpus:
Mar 14 21:29:59 OpenTop kernel: [    0.000000]   Intel GenuineIntel
Mar 14 21:29:59 OpenTop kernel: [    0.000000]   AMD AuthenticAMD
Mar 14 21:29:59 OpenTop kernel: [    0.000000]   Centaur CentaurHauls

same with the Xorg.0.logs

So what I have been posting is only the logs from GRUB's "recovery mode" and that would not load KMS, right?

Shouldn't something get logged when I try to boot normally?

Thanks again for your input!

jsbjsb001 · 03-15-2017, 03:12 AM

Quote:

Originally Posted by seedsca

The plot thickens!
So as I'm looking at the kern.log and syslog, i noticed something strange.
I can't troubleshoot this because when I try to use the normal boot process, meaning not using the GRUB "recovery mode" option. Nothing gets logged.

syslog: between 21:15:44 and 21:29:59 I did a normal boot and left the black screen on for 5 minutes.

Code:

Mar 14 21:15:44 OpenTop sddm[1526]: Socket server stopped.
Mar 14 21:15:44 OpenTop sddm[1526]: Display server stopping...
Mar 14 21:15:44 OpenTop systemd[1]: Stopping Session 3 of user sergio.
Mar 14 21:15:44 OpenTop rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1372" x-info="http://www.rsyslog.com"] exiting on signal 15.
Mar 14 21:29:59 OpenTop rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1211" x-info="http://www.rsyslog.com"] start
Mar 14 21:29:59 OpenTop rsyslogd: rsyslogd's groupid changed to 108
Mar 14 21:29:59 OpenTop rsyslogd: rsyslogd's userid changed to 104
Mar 14 21:29:59 OpenTop systemd[1]: Started Create Static Device Nodes in /dev.
Mar 14 21:29:59 OpenTop systemd[1]: Starting udev Kernel Device Manager...

kern.log:

Code:

Mar 14 21:15:44 OpenTop sddm[1526]: Socket server stopping...
Mar 14 21:15:44 OpenTop sddm[1526]: Socket server stopped.
Mar 14 21:15:44 OpenTop sddm[1526]: Display server stopping...
Mar 14 21:29:59 OpenTop kernel: [    0.000000] microcode: microcode updated early to revision 0x7, date = 2013-08-20
Mar 14 21:29:59 OpenTop kernel: [    0.000000] Linux version 4.8.0-41-generic (buildd@lgw01-18) (gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) ) #44-Ubuntu SMP Fri Mar 3 15:27:17 UTC 2017 (Ubuntu 4.8.0-41.44-generic 4.8.17)
Mar 14 21:29:59 OpenTop kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=c2315734-698e-4b0a-a7a0-7f206d79558c ro recovery nomodeset
Mar 14 21:29:59 OpenTop kernel: [    0.000000] KERNEL supported cpus:
Mar 14 21:29:59 OpenTop kernel: [    0.000000]   Intel GenuineIntel
Mar 14 21:29:59 OpenTop kernel: [    0.000000]   AMD AuthenticAMD
Mar 14 21:29:59 OpenTop kernel: [    0.000000]   Centaur CentaurHauls

same with the Xorg.0.logs

So what I have been posting is only the logs from GRUB's "recovery mode" and that would not load KMS, right?

Shouldn't something get logged when I try to boot normally?

Thanks again for your input!

No, the plot is not thickening ... "recovery mode" means exactly what it say's, to restore your system back to a working state. Below is a quote from the link I gave you in post # 4

Quote:

The open-source radeon drivers don't work without KMS and you disabled it. You didn't specify your exact gpu model, but I doubt the closed-source/fglrx/catalyst drivers still support anything that has AGP, so that's probably not an options for you.

Did you try removing the nomodeset/radeon.modeset=0 options after the install and directly booting into X? Not being able to see boot messages isn't optimal, but it might work.

Once again, RE-ENABLE KMS. Your making it a LOT harder than what it need's to be.

seasons · 03-15-2017, 09:52 AM

Quote:

Tried the amdgpu drivers

Be more specific. What did you do exactly? Did you try this before or after your problem started?

Quote:

I can't seem to find drivers for my Kubuntu version, 16.10

The correct and only driver for your GPU (open-source radeon driver) is already loaded out of the box. Trying to use anything else is a recipe to break your install, as you've discovered the hard way.

Quote:

So what I have been posting is only the logs from GRUB's "recovery mode" and that would not load KMS, right?

Booting with nomodeset automatically disables KMS. Can you get to a terminal by pressing Ctrl+Alt+F1 when you boot without nomodeset and end up with blank screen?

Quote:

I am also noticing that I can't boot to any OS. Not live CDs, not Windows installation (was going to try to re-install the BIOS)
Only way I can get boot "normally" is by using the nomodeset option under GRUB or "recovery mode". This allows me boot to either a live CD or my current Kubuntu 16.10.

You do have your CD set to boot first, correct? If so, it kind of sounds like a hardware issue to me, assuming the Windows CD used to work. I would try to reset the BIOS, and look into whether the system (which I guess is a Lenovo laptop) has some sort of hard reset mechanism, like holding the power button in for 30 seconds.

seasons · 03-15-2017, 10:01 AM

Quote:

Originally Posted by jsbjsb001

Once again, RE-ENABLE KMS. Your making it a LOT harder than what it need's to be.

1. The user has already stated that s/he cannot boot without nomodeset and ends up with blank screen. Your advice will not solve that.
2. Beating the user over the head with Caps Lock is not going to magically make an unhelpful statement helpful.

jsbjsb001 · 03-15-2017, 10:23 AM

Quote:

Originally Posted by seasons

1. The user has already stated that s/he cannot boot without nomodeset and ends up with blank screen. Your advice will not solve that.
2. Beating the user over the head with Caps Lock is not going to magically make an unhelpful statement helpful.

From what I'm reading (and you yourself have indicated) KMS is required, so I'm not sure what you think is "unhelpful" there. Unless your saying that KMS is not required for the radeon driver?? Or is there is some other issue you have??

And, exactly what do you mean by "unhelpful"?

BTW. I said from the outset to re-enable KMS, which the OP was indicating was NOT the problem (which differs from any other info I've seen). But if you would like to help the OP instead, well best of luck mate!

seasons · 03-15-2017, 11:52 AM

^You just keep telling the user to (re)enable KMS. You don't tell the user how to do that (although they have figured out KMS doesn't work with 'nomodeset'). Furthermore, user has already noted that system won't boot without 'nomodeset' parameter. So, just telling user to enable KMS and acting like the solution is as simple as that is unhelpful. I can't make it any clearer...

seedsca · 03-15-2017, 12:58 PM

jsbjsb001:

I'm sorry, I just don't see how to enable KMS.
https://wiki.debian.org/KernelModesetting Mentions how KMS is enabled by default on /etc/modprobe.d/radeon-kms.conf However, I don't have that file... When I look at the xserver-xorg-video-radeon package, it tells me only these files were installed:

Code:

/usr
/usr/lib
/usr/lib/xorg
/usr/lib/xorg/modules
/usr/lib/xorg/modules/drivers
/usr/lib/xorg/modules/drivers/radeon_drv.so
/usr/share
/usr/share/bug
/usr/share/bug/xserver-xorg-video-radeon
/usr/share/bug/xserver-xorg-video-radeon/script
/usr/share/doc
/usr/share/doc/xserver-xorg-video-radeon
/usr/share/doc/xserver-xorg-video-radeon/NEWS.Debian.gz
/usr/share/doc/xserver-xorg-video-radeon/changelog.Debian.gz
/usr/share/doc/xserver-xorg-video-radeon/copyright
/usr/share/man
/usr/share/man/man4
/usr/share/man/man4/radeon.4.gz

I've since re-installed it to no avail. Looking into getting the file where it should be now.

On the same link it mentions how to disable KMS which I have made sure is not done. So it would seem that only this radeon-kms.conf file is the missing piece. Not sure why it's missing...

Thanks for your continued help.

seasons:

I tried the amdgpu drivers after seeing this bug on launchpad. It seemed to load, but still things were not right. As this driver does not seem to support my card. I might go back and try it if nothing else works... This all started after rebooting:

Quote:

This pastebin shows when this might have started. It's from the kern.log
In line 178 there is a segfault, followed by another. After that reboot, it all began.

Don't think ctrl-alt-f1 or any other combination worked. I use that often for other things. Though I'll try again. Remember, nothing gets logged when I boot "normally". So not likely.

The CD is an original one and worked fine in the past. The BIOS is set up to boot to it. That's why it seems of concern to me or at least maybe related... I'll look into a BIOS hard reset. Already tried the regular default values. I was trying to reinstall the BIOS firmware, but windows is not installed and the CD won't boot.

Thanks!

seasons · 03-15-2017, 01:53 PM

If you're struggling with different OS's, it really seems like a hardware/BIOS issue.

Quote:

Originally Posted by seedsca

https://wiki.debian.org/KernelModesetting

The document is outdated. You don't need to explicitly enable KMS nowadays; it should work automatically.

Quote:

Mentions how KMS is enabled by default on /etc/modprobe.d/radeon-kms.conf However, I don't have that file.

You don't need it. You can use it (or any .conf file in /etc/modprobe.d) to customize options for kernel modules, but you don't need it.

Quote:

On the same link it mentions how to disable KMS which I have made sure is not done.

You're still booting with nomodeset according to your logs, so you're still disabling KMS. Apparently, when you don't use nomodeset, it hangs without being able to get to a terminal, which is really difficult to troubleshoot. About the only other thing I can think of is trying to ssh into it when you get a blank screen.

Quote:

As (amdgpu) does not seem to support my card. I might go back and try it if nothing else works.

That's completely illogical. Why would you try a driver that you know doesn't support your hardware?

seedsca · 03-15-2017, 02:40 PM

I found a link to /etc/modprobe.d/radeon-kms.conf but when I rebooted nothing changed. Even worse, I also got the black screen on "recovery mode" so I had to boot to a console only and erase the file... Still no logs on any of this.

The computer becomes unresponsive after the black screen. Only thing that works is holding the power button down to shut down.

About the amdgpu... I know, not a good idea.

Looking into ssh and hard reset of BIOS...