Suspend breaks X

ptmkenny · 2010-08-09 00:55:10

I'm using an Asus T91MT (hardware: http://wiki.archlinux.org/index.php/Asus_Eee_PC_T91MT) and with the vesa driver suspend works fine. However, I can't use the native resolution of the display (1024x600).

So, to fix the resolution I installed the fbdev driver as per the instructions (http://wiki.archlinux.org/index.php/Pou … fer_driver), and this fixed the resolution problem.

However, now I can suspend, but when the machine wakes up X crashes with a message that it cannot find the screen and I have to reboot to get it to work again.

Could anyone point me in the right direction? I'd search for more information on the problem but I'm just not sure where to look.

Best,
Patrick

schen · 2010-08-09 00:59:51

Why are you using vesa? Use the video card driver, vesa is a generic one that only supports the resolution in the bios. Fbdev could work, but you would get better support with the driver for your video card, which seems to be an intel card, so use xf86-video-intel.

Also, how do you suspend?

BTW, nice touchscreen tablet.

ptmkenny · 2010-08-09 03:14:06

Thanks for the reply.

The T91MT uses the Poulsbo chipset, so the generic Intel driver doesn't work. Fbdev allows me to use the native resolution, but it seems to break suspend. When I switch back to vesa I can suspend with no problem.

I suspend with:
sudo pm-suspend

ptmkenny · 2010-08-19 05:01:30

I tried reformatting the system and trying again from scratch (a carryover from growing up on Windows I suppose). Unfortunately, I still have the same problem, so I'm back to the vesa driver for now.

schen · 2010-08-19 17:30:39

There are poulsbo drivers in the aur. Search up psb.

whacath · 2010-08-24 12:06:53

Well, the psb-driver sucks, especially in combination with archlinux because when running archlinux you want to be able to update everything. If you are using the psb-driver you can't becouse you are stuck with an old kernel. That just doesn't add up with the archlinux philosophy. So the best bet is fbdev.

I got an t91mt and the same problem as you. I gues that the only thing we can assume to work is suspend-to-file.

Ps. Have you been able to get the touchscreen working?

schen · 2010-08-24 13:40:52

What do you mean?

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

ptmkenny · 2010-08-26 06:24:53

I will try the Poulsbo-specific drivers instead of fbdev as soon as I get the chance.

I have not been able to get the touchscreen working.

schen · 2010-08-26 21:56:54

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

I don't see what's so hard about searching the wiki.

Last edited by schen (2010-08-26 21:57:30)

whacath · 2010-08-26 22:18:19

Okey, schen. we got it, it is very very VERY easy to search the wiki. Please stop being such an ass and do something creative instead!

Last edited by whacath (2010-08-26 22:40:22)

jasonwryan · 2010-08-26 22:44:16

schen, the OP was responding to a question, if you have nothing to contribute to that part of the conversation, please refrain.

whacath: name calling is not helpful: please desist.

DarksideEE7 · 2010-08-26 23:29:17

ptmkenny wrote:

I'm using an Asus T91MT (hardware: http://wiki.archlinux.org/index.php/Asus_Eee_PC_T91MT) and with the vesa driver suspend works fine. However, I can't use the native resolution of the display (1024x600).
So, to fix the resolution I installed the fbdev driver as per the instructions (http://wiki.archlinux.org/index.php/Pou … fer_driver), and this fixed the resolution problem.
However, now I can suspend, but when the machine wakes up X crashes with a message that it cannot find the screen and I have to reboot to get it to work again.
Could anyone point me in the right direction? I'd search for more information on the problem but I'm just not sure where to look.

Best,
Patrick

Sounds like a bug with a tracker going already. It's actually RANDR causing the problem, not suspend.

https://bugs.kde.org/show_bug.cgi?id=236869

Try this:

Please try to deactivate the RandR kded module ("kcmshell4 kcmkded") as the
attached .xsession-errors note:

That fixed it for me on my ASUS laptop.

EDIT:

What's the deal with people being such hard-asses on the forums lately? Be nice!

Last edited by DarksideEE7 (2010-08-26 23:40:55)

schen · 2010-08-27 00:52:46

schen wrote:

http://wiki.archlinux.org/index.php/Touchscreen
I don't see what's so hard about searching the wiki.

Look, I'm sorry, I just don't get how I'm a hardass all of a sudden. Lots of stress.

Last edited by schen (2010-08-27 01:06:27)

DarksideEE7 · 2010-08-27 22:11:32

schen wrote:

schen wrote:
http://wiki.archlinux.org/index.php/Touchscreen
I don't see what's so hard about searching the wiki.

Look, I'm sorry, I just don't get how I'm a hardass all of a sudden. Lots of stress.

NP, we all have those days

Arch Linux

#1 2010-08-09 00:55:10

Suspend breaks X

#2 2010-08-09 00:59:51

Re: Suspend breaks X

#3 2010-08-09 03:14:06

Re: Suspend breaks X

#4 2010-08-19 05:01:30

Re: Suspend breaks X

#5 2010-08-19 17:30:39

Re: Suspend breaks X

#6 2010-08-24 12:06:53

Re: Suspend breaks X

#7 2010-08-24 13:40:52

Re: Suspend breaks X

#8 2010-08-26 06:24:53

Re: Suspend breaks X

#9 2010-08-26 21:56:54

Re: Suspend breaks X

#10 2010-08-26 22:18:19

Re: Suspend breaks X

#11 2010-08-26 22:44:16

Re: Suspend breaks X

#12 2010-08-26 23:29:17

Re: Suspend breaks X

#13 2010-08-27 00:52:46

Re: Suspend breaks X

#14 2010-08-27 22:11:32

Re: Suspend breaks X

Board footer