You are not logged in.

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

aronasorman
Member
Registered: 2009-11-28
Posts: 11

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

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.

Offline

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

wonder
Developer
From: Bucharest, Romania
Registered: 2006-07-05
Posts: 5,941
Website

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

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

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


Give what you have. To someone, it may be better than you dare to think.

Offline

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

aronasorman
Member
Registered: 2009-11-28
Posts: 11

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

oh my bad. Haha.

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

Offline

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

martusia
Member
Registered: 2009-10-17
Posts: 10

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

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)

Offline

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

ingemar
Member
From: Sweden
Registered: 2010-01-04
Posts: 4

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

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?

Offline

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

pie86
Member
Registered: 2009-09-06
Posts: 78

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

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.

Offline

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

marvn
Member
From: Prague
Registered: 2010-01-05
Posts: 84

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

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


core i5 4590, x86_64, nvidia 970

Offline

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

tavianator
Member
From: Waterloo, ON, Canada
Registered: 2007-08-21
Posts: 858
Website

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

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.

Offline

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

marvn
Member
From: Prague
Registered: 2010-01-05
Posts: 84

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

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)


core i5 4590, x86_64, nvidia 970

Offline

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

tavianator
Member
From: Waterloo, ON, Canada
Registered: 2007-08-21
Posts: 858
Website

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

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.

Offline

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

marvn
Member
From: Prague
Registered: 2010-01-05
Posts: 84

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

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)


core i5 4590, x86_64, nvidia 970

Offline

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

ingemar
Member
From: Sweden
Registered: 2010-01-04
Posts: 4

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

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!

Offline

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

TiborB
Member
Registered: 2008-12-09
Posts: 103

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

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...

Offline

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

loafer
Member
From: the pub
Registered: 2009-04-14
Posts: 1,772

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

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


All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.

Offline

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

TiborB
Member
Registered: 2008-12-09
Posts: 103

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

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

Offline

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

ngoonee
Forum Fellow
From: Between Thailand and Singapore
Registered: 2009-03-17
Posts: 7,354

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

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?


Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.

Offline

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

TiborB
Member
Registered: 2008-12-09
Posts: 103

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

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...

Offline

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

marvn
Member
From: Prague
Registered: 2010-01-05
Posts: 84

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

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?


core i5 4590, x86_64, nvidia 970

Offline

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

Ultraman
Member
Registered: 2009-12-24
Posts: 242

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

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)

Offline

Board footer

Powered by FluxBB