With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

aronasorman · 2009-12-30 07:13:17

First of all, I would like to say a Happy New Year to all Archers out there. ^^

Recently, the 2.6.32 was moved from testing to core. Now i'm fine by this, because finally I can get the full resolution to my terminals. Unfortunately, It also causes my screen to lock up and not display anything after I wake up from a suspend. (which sucks, because I never turn off my lenovo s10 anymore, just do a suspend)

Is there a fix for this? Or if none, is there a way to revert back to 2.6.31?

Anyways, thanks.

wonder · 2009-12-30 07:56:43

ati, intel or nouveau? is useful to post what video card do you have.

Last edited by wonder (2009-12-30 07:57:40)

aronasorman · 2009-12-30 08:03:41

oh my bad. Haha.

Intel 945GME Express Integrated Graphics Controller aka the intel graphics card that comes with atom netbooks.

martusia · 2009-12-30 13:48:23

Hi,
I've got the same problem as aronasorman with my Dell Latitude D420 with Intel Grahpics Media Accelerator 950, when I close and open laptop screen, without any hibernation or sth.

Last edited by martusia (2009-12-30 15:22:02)

ingemar · 2010-01-04 18:45:06

Same here as well! I'm using an Asus Eee 901 (with a Mobile 945GME Express Integrated Graphics Controller), and waking up from suspend only results in a black screen. If xorg is started there's some flickering as well... Have anyone found a solution?

pie86 · 2010-01-04 19:35:14

On my xps m1330 (Intel Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)) suspend is ok, but when I close and open the lid sometime the screen appears black.

Stupid workaround:
1) ctrl+alt+F1
2) alt+F7

This restore Gnome as I left it.

marvn · 2010-01-05 15:16:08

same here, amilo pro v3545, nvidia 190.53, i686

that trick with switching to tty1 and back doesn't work for me so i've downgraded back to 2.6.31

tavianator · 2010-01-05 15:35:58

Probably a KMS bug; try with kernel parameter "nomodeset". You'll lose your nice full-resolution console unfortunately, but that should make suspend work if it did before. You may want to try with a newer kernel too, to see if the bug has been fixed, and report one if not.

marvn · 2010-01-05 16:52:19

tavianator wrote:

Probably a KMS bug; try with kernel parameter "nomodeset". You'll lose your nice full-resolution console unfortunately, but that should make suspend work if it did before. You may want to try with a newer kernel too, to see if the bug has been fixed, and report one if not.

proprietary nvidia driver AFAIK doesn't use KMS, so this won't help me. but i catch that pm-utils now have vbetool as dep, so this may help...

Edit> nope, vbetool and nomodeset didn't help me...any idea how to debug this?

Last edited by marvn (2010-01-05 17:44:54)

tavianator · 2010-01-05 17:46:16

You're right, but I think yours is a different bug than the OP's. You should try the newer (195.30?) nVidia blob, and also try suspending without X running to see if it's a kernel or graphics driver issue.

marvn · 2010-01-05 18:15:19

ok, i'll try tomorrow

btw. is there some easy way to suspend from tty console?

Edit> i've just tried 'echo -n mem > /sys/power/state' on 2.6.31 kernel from console and i'm really confused, 'cause after waking up, screen won't turn on. so i've tried 'on blind' type /etc/rc.d/kdm restart and then screen has turned on and kdm has started...
edit2> the same with pm-suspend form console, pm-suspend form X works

Last edited by marvn (2010-01-05 18:56:28)

ingemar · 2010-01-05 22:09:37

tavianator wrote:

Probably a KMS bug; try with kernel parameter "nomodeset". You'll lose your nice full-resolution console unfortunately, but that should make suspend work if it did before. You may want to try with a newer kernel too, to see if the bug has been fixed, and report one if not.

This works for me, so yeah, I guess it's a KMS related bug... Hope this get's fixed with the next release of the kernel. Thanks!

TiborB · 2010-01-05 23:21:41

If you are still interested in coming back to 2.6.31...

This is exactly what I did a while ago...

* You need a not synced repository: I used: Server = ftp://gd.tuwien.ac.at/opsys/linux/archl … po/os/i686, make sure this is the only one you have not commented out in /etc/pacman.d/mirrorlist,
* then
pacman -Syy
pacman -Suu # to revert all system
or - what I did:
pacman -S kernel-headers kernel26-firmware kernel26 oss glibc binutils # You might be forced to downgrade other packages
* edit /etc/pacman.conf to add
IgnorePkg=kernel26
IgnorePkg=kernel-headers
IgnorePkg=kernel26-firmware # or whatever seem needed to you
* revert mirrorlist to initial status...

loafer · 2010-01-06 08:58:58

There is also a Wiki article to downgrade packages, with a list of URLs with older packages;

http://wiki.archlinux.org/index.php/Downgrade_packages

TiborB · 2010-01-06 14:30:24

my suggestion is based on section 4.1 Out-Of-Sync Mirrors from this wiki...

ngoonee · 2010-01-07 02:41:01

TiborB wrote:

my suggestion is based on section 4.1 Out-Of-Sync Mirrors from this wiki...

Which is also the most unreliable, since as time goes by there'll be less and less (eventually no) out-of-sync mirrors?

TiborB · 2010-01-07 08:10:46

ngoonee wrote:

TiborB wrote:
my suggestion is based on section 4.1 Out-Of-Sync Mirrors from this wiki...
Which is also the most unreliable, since as time goes by there'll be less and less (eventually no) out-of-sync mirrors?

List of out-of-sync mirrors is quite long, so I would say, that allways there will be some such mirrors.
But for this situation, it just doesnt matter. He needs such mirror only once (now) and from now he will be using normal (up-to-date) mirrors.

He wants to revert to few one-month-old packages. If he wanted older packages (few months/years old), then out-of-sync mirrors would not be a solution. There are not mirrors not synced for such long period of time...

marvn · 2010-01-08 21:07:38

ok, so my issue remains with 2.6.32.3, system won't wake neither form X or console

btw. any way to debug this? or some log i should look at?

Ultraman · 2010-01-08 21:50:50

TiborB wrote:

If you are still interested in coming back to 2.6.31...
This is exactly what I did a while ago...
* You need a not synced repository: I used: Server = ftp://gd.tuwien.ac.at/opsys/linux/archl … po/os/i686, make sure this is the only one you have not commented out in /etc/pacman.d/mirrorlist,
* then
pacman -Syy
pacman -Suu # to revert all system
or - what I did:
pacman -S kernel-headers kernel26-firmware kernel26 oss glibc binutils # You might be forced to downgrade other packages
* edit /etc/pacman.conf to add
IgnorePkg=kernel26
IgnorePkg=kernel-headers
IgnorePkg=kernel26-firmware # or whatever seem needed to you
* revert mirrorlist to initial status...

If you had kernel 2.6.31 installed before, and did not clean your package cache with pacman, you still have the original kernel26 2.6.31 package in /var/cache/pacman/pkg/
You could simply reinstall that one, and perhaps the headers (and/or firmware) as well to be sure it's back to the old ways again.

# cd /var/cache/pacman/pkg/
# pacman -U kernel26-2.6.31.6-1-x86_64.pkg.tar.gz

Rinse and repeat for the headers and firmware.

Last edited by Ultraman (2010-01-08 21:53:49)

Arch Linux

#1 2009-12-30 07:13:17

With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

#2 2009-12-30 07:56:43

Re: With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

#3 2009-12-30 08:03:41

Re: With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

#4 2009-12-30 13:48:23

Re: With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

#5 2010-01-04 18:45:06

Re: With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

#6 2010-01-04 19:35:14

Re: With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

#7 2010-01-05 15:16:08

Re: With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

#8 2010-01-05 15:35:58

Re: With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

#9 2010-01-05 16:52:19

Re: With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

#10 2010-01-05 17:46:16

Re: With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

#11 2010-01-05 18:15:19

Re: With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

#12 2010-01-05 22:09:37

Re: With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

#13 2010-01-05 23:21:41

Re: With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

#14 2010-01-06 08:58:58

Re: With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

#15 2010-01-06 14:30:24

Re: With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

#16 2010-01-07 02:41:01

Re: With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

#17 2010-01-07 08:10:46

Re: With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

#18 2010-01-08 21:07:38

Re: With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

#19 2010-01-08 21:50:50

Re: With regards to the 2.6.32 kernel. (Or how to revert back to 2.6.31)

Board footer