Can't suspend laptop in slack 13.37 after installing ATI drivers
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Can't suspend laptop in slack 13.37 after installing ATI drivers
Hello gentlemen,
I have run into the following problem, after I installed the proprietary AMD/ATI driver for my videocard I've been unable to wake up my laptop after suspend to RAM, it suspends ok (I guess?) but when I try to wake it up the screen doesn't turn on so I have to manually shut down the laptop.
before installing the proprietary driver, it worked ok
the videocard is a Radeon HD 3200, and the processor is an AMD Turion X2 Mobile
Hello gentlemen,
I have run into the following problem, after I installed the proprietary AMD/ATI driver for my videocard I've been unable to wake up my laptop after suspend to RAM, it suspends ok (I guess?) but when I try to wake it up the screen doesn't turn on so I have to manually shut down the laptop.
before installing the proprietary driver, it worked ok
the videocard is a Radeon HD 3200, and the processor is an AMD Turion X2 Mobile
any ideas?
I had exactly the same problem. What worked for me was to append
Code:
vga=0
to the append line close to the top in /etc/lilo.conf and comment out the framebuffer value used to somewhere in middle of lilo.conf here is mine as an example
Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0" vga=0
boot = /dev/sda
compact
default = Linux
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255
# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt
# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x64k
#vga = 791
# Normal VGA console
#vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# VESA framebuffer console @ 1024x768x64k
#vga=791
# VESA framebuffer console @ 1024x768x32k
#vga=790
# VESA framebuffer console @ 1024x768x256
#vga=773
# VESA framebuffer console @ 800x600x64k
#vga=788
# VESA framebuffer console @ 800x600x32k
#vga=787
# VESA framebuffer console @ 800x600x256
#vga=771
# VESA framebuffer console @ 640x480x64k
#vga=785
# VESA framebuffer console @ 640x480x32k
#vga=784
# VESA framebuffer console @ 640x480x256
#vga=769
# End LILO global section
# Windows bootable partition config begins
other = /dev/sda2
label = Windows
table = /dev/sda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda5
label = Linux
read-only
# Linux bootable partition config ends
Yes, I can't see that the vga mode would affect suspend resume. I have the same hardware as you and use the fglrx driver. I don't use suspend though...i'll have a go tonight and let you know if I work out what is going on. Are you using an initrd?
Yes, I can't see that the vga mode would affect suspend resume. I have the same hardware as you and use the fglrx driver. I don't use suspend though...i'll have a go tonight and let you know if I work out what is going on. Are you using an initrd?
I have an ATI HD5470 and the vga=0 does indeed most definitely work for me.
I qoute: "...ATI's proprietary catalyst driver cannot resume from suspend if the framebuffer is enabled. To disable the framebuffer, add vga=0 to your kernel options in /boot/grub/menu.lst..."
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.