Re: Call for help: list of machines with working S3
On Fri, Apr 01, 2005 at 11:17:08AM +0200, Romano Giannetti wrote:
> and nothing more. Well, this was done with the double console, so that I
> will try again as soon as I have a bit of time with just the serial console
> on.
Much better now. Configuration, dmesg at boot, etc are at
http://www.dea.icai.upco.es/romano/linux/config-2.6.12-rc1-rg/
I booted the 2.6.12-rc1 kernel above (with the alps resume fix) with the
options: console=ttyS0,115200n8 init=/bin/bash
The full log of the session, if it's interesting to someone, is here:
http://www.dea.icai.upco.es/romano/linux/swsusp/2612rc1-bash.s3.log
The interesting part is here. At suspend I have:
bash-2.05b# echo -n 3 > /proc/acpi/sleep
[4294743.859000] Stopping tasks: ===|
and the laptop goes off with suspend light blinking. Ok. After a 20 sec, I
hit the power button and:
[4294759.817000] evevent-0286: *** Error: No installed handler for fixed
event
[0002]
[4294759.827000] Restarting tasks... done
bash-2.05b#
I have the prompt back! But the HDD light is fixed on... I tried lsmod:
bash-2.05b# lsmod
Dead. After a bit it says:
[4294828.522000] hda: dma_timer_expiry: dma status == 0x21
[4294838.522000] hda: DMA timeout error
[4294838.526000] hda: dma timeout error: status=0x58 { DriveReady
SeekComplete DataRequest }
[4294838.536000]
[4294838.538000] ide: failed opcode was: unknown
[4294838.546000] hda: task_in_intr: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[4294838.556000] hda: task_in_intr: error=0x04 { DriveStatusError }
[4294838.564000] ide: failed opcode was: unknown
this (with error 0x59 and 0x04) is repeated 3 more times, then:
[4294838.699000] ide0: reset: success
but nothing change, and after a bit:
[4294858.708000] hda: dma_timer_expiry: dma status == 0x21
[4294868.708000] hda: DMA timeout error
[4294868.712000] hda: dma timeout error: status=0x58 { DriveReady
SeekComplete DataRequest }
[4294868.722000]
[4294868.724000] ide: failed opcode was: unknown
[4294868.729000] hda: status error: status=0x58 { DriveReady SeekComplete
DataRequest }
[4294868.738000]
[4294868.74] ide: failed opcode was: unknown
[4294868.746000] hda: drive not ready for command
(3 more times)
[4294868.862000] ide0: reset: success
[4294888.879000] hda: dma_timer_expiry: dma status == 0x21
...and continuing forever (with error 0x58 as before). In the full log there
is a sysrq-m and sysrq-t result, but I do not think it's very important
here.
When I decided to stop I hit sysrq-b and:
[4294911.707000] SysRq : Resetting
The bios (with the "sony" splash) restarted but locked hard, and to resume I
had to do the hard poweroff (5 seconds power button down).
Well. I hope this helps someone :-). I will stay with S4 for now.
Romano
--
Romano Giannetti - Univ. Pontificia Comillas (Madrid, Spain)
Electronic Engineer - phone +34 915 422 800 ext 2416 fax +34 915 596 569
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Call for help: list of machines with working S3
On Thu, Mar 31, 2005 at 09:54:33PM +0200, Maximilian Engelhardt wrote:
> On Fri, 2005-03-18 at 15:50 +0100, Romano Giannetti wrote:
> >
> > It happens exactly the same on my laptop, sony vaio whose configuration is
> >
> > http://www.dea.icai.upco.es/romano/linux/vaio-conf/laptop-config.html
>
> I was able to get some logs using CONFIG_LP_CONSOLE (the first time I
> ever saw "Back to C!"):
>
> Back to C!
> PM: Finishing up.
> ACPI: PCI interrupt :00:1f.1[A] -> GSI 10 (level,low) -> IRQ 10
> MCE: The hardware reports a non fatal, correctable incident occurred on
> CPU 0.
> Bank 1: e201
> hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: task_out_intr: error=0x04 { DriveStatusError }
> ide: failed opcode was: unknown
>
> keeps on always repeating last three messages until I reboot
>
> Full log:
> http://home.daemonizer.de/resume.png
>
> kernel version is 2.6.11
> config: http://home.daemonizer.de/config-2.6.11-S3test
> dmesg from booting: http://home.daemonizer.de/dmesg-2.6.11-S3test
> lspci: http://home.daemonizer.de/lspci
> Gentoo Base System version 1.6.10
>
> Hardware:
> Acer Travelmate 661lci (centrino)
> Intel(R) Pentium(R) M processor 1400MHz
I tried with serial console. The only thing I get is:
Stopping tasks:
|
and nothing more. Well, this was done with the double console, so that I
will try again as soon as I have a bit of time with just the serial console
on.
But the "external" behaviour for me is like your: it stops, then at restart
the HDD led stays on and nothing happen.
Romano
--
Romano Giannetti - Univ. Pontificia Comillas (Madrid, Spain)
Electronic Engineer - phone +34 915 422 800 ext 2416 fax +34 915 596 569
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Call for help: list of machines with working S3
On Fri, 2005-03-18 at 15:50 +0100, Romano Giannetti wrote:
>
> It happens exactly the same on my laptop, sony vaio whose configuration is
>
> http://www.dea.icai.upco.es/romano/linux/vaio-conf/laptop-config.html
>
> Next week is Easter holyday here, I will try to connect my Psion casio as
> serial terminal and see if I can catch something.
I was able to get some logs using CONFIG_LP_CONSOLE (the first time I
ever saw "Back to C!"):
Back to C!
PM: Finishing up.
ACPI: PCI interrupt :00:1f.1[A] -> GSI 10 (level,low) -> IRQ 10
MCE: The hardware reports a non fatal, correctable incident occurred on
CPU 0.
Bank 1: e201
hda: task_out_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_out_intr: error=0x04 { DriveStatusError }
ide: failed opcode was: unknown
keeps on always repeating last three messages until I reboot
Full log:
http://home.daemonizer.de/resume.png
kernel version is 2.6.11
config: http://home.daemonizer.de/config-2.6.11-S3test
dmesg from booting: http://home.daemonizer.de/dmesg-2.6.11-S3test
lspci: http://home.daemonizer.de/lspci
Gentoo Base System version 1.6.10
Hardware:
Acer Travelmate 661lci (centrino)
Intel(R) Pentium(R) M processor 1400MHz
please mail me if you need additional data.
Thanks for help,
Maxi
signature.asc
Description: This is a digitally signed message part
Re: Call for help: list of machines with working S3
On Fri, 2005-03-18 at 15:50 +0100, Romano Giannetti wrote: > > It happens exactly the same on my laptop, sony vaio whose configuration is > > http://www.dea.icai.upco.es/romano/linux/vaio-conf/laptop-config.html > > Next week is Easter holyday here, I will try to connect my Psion casio as > serial terminal and see if I can catch something. > >Romano Sorry that I didn't answer earlier , but I didn't have much time the last week. Unfortunately my laptop has a serial port only via docking station that I don't have. So I tried logging via netconsole. This generally worked, but when I try to enter S3 the last thing I get is "PM: Entering state" but the laptop never enters S3, it just hangs there forever. So sadly I couldn't get more information. If anyone has any idea what else I could do to either fix this problem or get more information about it, please tell me and I'll try :) Maxi signature.asc Description: This is a digitally signed message part
Re: Call for help: list of machines with working S3
On Thu, Mar 17, 2005 at 09:05:12PM +0100, Maximilian Engelhardt wrote: > On Mon, 2005-02-14 at 22:20 +0100, Pavel Machek wrote: > > Video issues with S3 resume > > ~~~ > > 2003-2005, Pavel Machek > > > Tried all this on my Laptop but nothing seems to work for me. > I do "echo 3 > /proc/acpi/sleep" and the systems seems to go into S3. > When I press some key to wake it up again it powers up but I get nothing > than a black screen. It's not only the video card that's not working, > because the only thing it reacts to is Sysrq (without screen of course). > One additional thing I found is that in this state the HDD led keeps > lighting all the time untill I reboot my system. After rebooting I > couldn't find anything interesting in my logs. > > Is there any way I could get S3 working on my laptop? > > some data: > Acer Travel Mate 661lci > Gentoo Base System version 1.6.10 > kernel 2.6.11 > > I did all this testing with a minimal kernel that only had the > absolutely necessary drivers. It happens exactly the same on my laptop, sony vaio whose configuration is http://www.dea.icai.upco.es/romano/linux/vaio-conf/laptop-config.html Next week is Easter holyday here, I will try to connect my Psion casio as serial terminal and see if I can catch something. Romano -- Romano Giannetti - Univ. Pontificia Comillas (Madrid, Spain) Electronic Engineer - phone +34 915 422 800 ext 2416 fax +34 915 596 569 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Call for help: list of machines with working S3
On Mon, 2005-02-14 at 22:20 +0100, Pavel Machek wrote: > Hi! > > Stefan provided me initial list of machines where S3 works (including > video). If you have machine that is not on the list, please send me a > diff. If you have eMachines... I'd like you to try playing with > vbetool (it worked for me), and if it works for you supplying right > model numbers. > > Pavel > > > Video issues with S3 resume > ~~~ > 2003-2005, Pavel Machek > > During S3 resume, hardware needs to be reinitialized. For most > devices, this is easy, and kernel driver knows how to do > it. Unfortunately there's one exception: video card. Those are usually > initialized by BIOS, and kernel does not have enough information to > boot video card. (Kernel usually does not even contain video card > driver -- vesafb and vgacon are widely used). > > This is not problem for swsusp, because during swsusp resume, BIOS is > run normally so video card is normally initialized. S3 has absolutely > no change to work with SMP/HT. Be sure it to turn it off before > testing (swsusp should work ok, OTOH). > > There are few types of systems where video works after S3 resume: > > (1) systems where video state is preserved over S3. > > (2) systems where it is possible to call video bios during S3 > resume. Unfortunately, it is not correct to call video BIOS at that > point, but it happens to work on some machines. Use > acpi_sleep=s3_bios. > > (3) systems that initialize video card into vga text mode and where BIOS > works well enough to be able to set video mode. Use > acpi_sleep=s3_mode on these. > > (4) on some systems s3_bios kicks video into text mode, and > acpi_sleep=s3_bios,s3_mode is needed. > > (5) radeon systems, where X can soft-boot your video card. You'll need > patched X, and plain text console (no vesafb or radeonfb), see > http://www.doesi.gmxhome.de/linux/tm800s3/s3.html. > > (6) other radeon systems, where vbetool is enough to bring system back > to life. Do vbetool vbestate save > /tmp/delme; echo 3 > /proc/acpi/sleep; > vbetool post; vbetool vbestate restore < /tmp/delme; setfont > , and your video should work. Tried all this on my Laptop but nothing seems to work for me. I do "echo 3 > /proc/acpi/sleep" and the systems seems to go into S3. When I press some key to wake it up again it powers up but I get nothing than a black screen. It's not only the video card that's not working, because the only thing it reacts to is Sysrq (without screen of course). One additional thing I found is that in this state the HDD led keeps lighting all the time untill I reboot my system. After rebooting I couldn't find anything interesting in my logs. Is there any way I could get S3 working on my laptop? some data: Acer Travel Mate 661lci Gentoo Base System version 1.6.10 kernel 2.6.11 I did all this testing with a minimal kernel that only had the absolutely necessary drivers. Thanks for help, Maxi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Hi! > > > > * MySQL (hinders the actual suspension process and kicks the pc > > > back to > > > > where it was) > > > > > > Try this patch... > > > Pavel > > > > > > --- clean/kernel/signal.c 2005-02-03 22:27:26.0 +0100 > > > +++ linux/kernel/signal.c 2005-02-03 22:28:19.0 +0100 > > > @@ -,6 +,7 @@ > > > ret = -EINTR; > > > } > > > > > > + try_to_freeze(1); > > > return ret; > > > } > > I also encounter a similar issue. syslogd can't be stopped. It's waiting > > for kjournald to flush some works but kjournald is stopped first. Looks > > like the kernel thread should be stopped later than user thread just > > like Nigel's suspend2 patch does. > > Pavel, do you have any kernel/power/process.c changes in? If not, I'll > submit those refrigerator changes. No, process.c was left unchanged for quite a long time. Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Hi. On Tue, 2005-03-15 at 19:10, Li Shaohua wrote: > Hi, > On Mon, 2005-03-14 at 16:00, Pavel Machek wrote: > > Hi! > > > > > * MySQL (hinders the actual suspension process and kicks the pc > > back to > > > where it was) > > > > Try this patch... > > Pavel > > > > --- clean/kernel/signal.c 2005-02-03 22:27:26.0 +0100 > > +++ linux/kernel/signal.c 2005-02-03 22:28:19.0 +0100 > > @@ -,6 +,7 @@ > > ret = -EINTR; > > } > > > > + try_to_freeze(1); > > return ret; > > } > I also encounter a similar issue. syslogd can't be stopped. It's waiting > for kjournald to flush some works but kjournald is stopped first. Looks > like the kernel thread should be stopped later than user thread just > like Nigel's suspend2 patch does. Pavel, do you have any kernel/power/process.c changes in? If not, I'll submit those refrigerator changes. Regards, Nigel -- Nigel Cunningham Software Engineer, Canberra, Australia http://www.cyclades.com Bus: +61 (2) 6291 9554; Hme: +61 (2) 6292 8028; Mob: +61 (417) 100 574 Maintainer of Suspend2 Kernel Patches http://suspend2.net - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Hi, On Mon, 2005-03-14 at 16:00, Pavel Machek wrote: > Hi! > > > * MySQL (hinders the actual suspension process and kicks the pc > back to > > where it was) > > Try this patch... > Pavel > > --- clean/kernel/signal.c 2005-02-03 22:27:26.0 +0100 > +++ linux/kernel/signal.c 2005-02-03 22:28:19.0 +0100 > @@ -,6 +,7 @@ > ret = -EINTR; > } > > + try_to_freeze(1); > return ret; > } I also encounter a similar issue. syslogd can't be stopped. It's waiting for kjournald to flush some works but kjournald is stopped first. Looks like the kernel thread should be stopped later than user thread just like Nigel's suspend2 patch does. Thanks, Shaohua - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Call for help: list of machines with working S3
On Monday 14 March 2005 09:00, Pavel Machek wrote: > Hi! > > > * MySQL (hinders the actual suspension process and kicks the pc back to > > where it was) > > Try this patch... Works nicely. Thanks. Jan -- Most people don't need a great deal of love nearly so much as they need a steady supply. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Call for help: list of machines with working S3
Hi! > * MySQL (hinders the actual suspension process and kicks the pc back to > where it was) Try this patch... Pavel --- clean/kernel/signal.c 2005-02-03 22:27:26.0 +0100 +++ linux/kernel/signal.c 2005-02-03 22:28:19.0 +0100 @@ -,6 +,7 @@ ret = -EINTR; } + try_to_freeze(1); return ret; } -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Call for help: list of machines with working S3
On Monday 14 February 2005 22:11, Pavel Machek wrote: > Hi! > > Stefan provided me initial list of machines where S3 works (including > video). If you have machine that is not on the list, please send me a > diff. If you have eMachines... I'd like you to try playing with > vbetool (it worked for me), and if it works for you supplying right > model numbers. Acer Travelmate 803LCi, working Suspend to ram: - Have to use the soft-boot method for the radeon - Have to shutdown the following parts: * hotplug (actually the USB subsystem, but hotplug does that nicely) * ALSA (modem won't work otherwise without reloading the modules) (snd_intel8x0m module) * MySQL (hinders the actual suspension process and kicks the pc back to where it was) Other than these little things it works like a charm :) Jan -- Bumper sticker: All the parts falling off this car are of the very finest British manufacture. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Call for help: list of machines with working S3
On Mon, 14 Feb 2005 22:11:05 +0100, Pavel Machek <[EMAIL PROTECTED]> wrote: > Table of known working systems: > > Model hack (or "how to do it") > -- > IBM TP R32 / Type 2658-MMG none (1) > Athlon HP Omnibook XE3 none (1) > Compaq Armada E500 - P3-700 none (1) (S1 also works OK) > IBM t41pnone (1) > Athlon64 desktop prototype s3_bios (2) > HP NC6000 s3_bios (2) > Toshiba Satellite 4080XCDT s3_mode (3) > Toshiba Satellite 4030CDT s3_mode (3) > Dell D600, ATI RV250vga=normal (**) > Asus L2400D s3_mode (3)(***) (S1 also works OK) > Toshiba Satellite P10-554 s3_bios,s3_mode (4)() > Acer TM 800 vga=normal, X patches, see webpage (5) > Athlon64 Arima W730avbestate needed (6) > eMachines athlon64 machines vbestate needed (6) (someone please get me > model #s) > > (**) Text console is "strange" after resume. Backlight is switched on again > by the X server. X server is: > | X Window System Version 6.8.1.904 (6.8.2 RC 4) > | Release Date: 2 February 2005 > | X Protocol Version 11, Revision 0, Release 6.8.1.904 > | Build Operating System: SuSE Linux [ELF] SuSE > as present in SUSE 9.3preview3. > > (***) To be tested with a newer kernel. > > () Not with SMP kernel, UP only. Toshiba Libretto L5 works completely with S3, not with S1 when the ali5451 ALSA module is unloaded. -- Anyone who quotes me in their sig is an idiot. -- Rusty Russell. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Call for help: list of machines with working S3
Pavel Machek wrote: > Table of known working systems: > > Model hack (or "how to do it") > -- IBM Thinkpad X40 (Type 2371-7JG) acpi_sleep=s3_bios,s3_mode -- Stefan Seyfried, QA / R&D Team Mobile Devices, SUSE LINUX Nürnberg. "Any ideas, John?" "Well, surrounding them's out." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Call for help: list of machines with working S3
Stefan Seyfried wrote: > Pavel Machek wrote: >> Hi! > >> Table of known working systems: >> >> Model hack (or "how to do it") >> -- > > IBM Thinkpad T20 (S3 Inc. 86C270-294 Savage/IX-MV), model 2647-44G > "Just works" out of the box. S1 works, too but does not switch off the > backlight and looks "interesting", but does not crash. Vesafb is "interesting" also after S3, but X continues to work :-) -- Stefan Seyfried, QA / R&D Team Mobile Devices, SUSE LINUX Nürnberg. "Any ideas, John?" "Well, surrounding them's out." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Call for help: list of machines with working S3
Pavel Machek wrote: > Hi! > Table of known working systems: > > Model hack (or "how to do it") > -- IBM Thinkpad T20 (S3 Inc. 86C270-294 Savage/IX-MV), model 2647-44G "Just works" out of the box. S1 works, too but does not switch off the backlight and looks "interesting", but does not crash. -- Stefan Seyfried, QA / R&D Team Mobile Devices, SUSE LINUX Nürnberg. "Any ideas, John?" "Well, surrounding them's out." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Pavel Machek wrote: >> this server crashes when switching to the console or shutting >> down (crashing is sometimes, not always), very nice screen which >> slowly turns white > > Hmm, it would be nice to be able to trigger "go white" on purpose -- > it looks like screen is burning and could scare quite a lot of people > :-). BTW: turning white does not necessarily mean "screen is dying" but can also mean "LCD is powered off and slowly turning transparent but the backlight is still on" which brings me back to the original subject: Sharp PC-AR10 (ATI rage mobility P/M AGP 2x), which is sort of the crappiest hardware i have ever seen, has working S3 without any tricks. The backlight is not turned off at S3 but in fact it is explicitly turned on (if i do "xset dpms force off" before suspend, it turns back on after or shortly before entering suspend) and the screen slowly goes white (because TFT power is turned off), but if you enter S3 via lidswitch this does not matter since the lidswitch turns off the backlight :-) -- Stefan Seyfried, QA / R&D Team Mobile Devices, SUSE LINUX, Nürnberg. "Any ideas, John?" "Well, surrounding them's out." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Hi! > > > - DRI must be disabled I guess?! Even with newer X server (x.org)? > > > > You still didn't state which X server are you using. In short, XFree86 4.4, > > I have stated it several times, but here a sum up: > > - XFree86 4.3 (debian/sid) > no work > - X.Org 6.8.1.99 (debian -dri-trunk stuff plus kernel modules9 > no work > with 2.6.11-rc4 and 2.6.11-rc3-mm2 > this server crashes when switching to the console or shutting > down (crashing is sometimes, not always), very nice screen which > slowly turns white Hmm, it would be nice to be able to trigger "go white" on purpose -- it looks like screen is burning and could scare quite a lot of people :-). Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
On Thu, Feb 24, 2005 at 01:37:16PM +0100, Norbert Preining wrote: > - X.Org 6.8.1.99 (debian -dri-trunk stuff plus kernel modules9 > no work > with 2.6.11-rc4 and 2.6.11-rc3-mm2 > this server crashes when switching to the console or shutting > down (crashing is sometimes, not always), very nice screen which > slowly turns white > I get a very similar experience on a Sony Vaio PCG-FX401 (Duron 800 / Mach64 based RageM1) All suggestions welcome - no DRI or Framebuffers in use - X is Xorg 6.8.2 and the kernel is a 2.6.10mdk from cooker (yeah - I know not vanilla) P - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Thus wrote Norbert Preining: > - X.Org 6.8.1.99 (debian -dri-trunk stuff plus kernel modules9 > no work > with 2.6.11-rc4 and 2.6.11-rc3-mm2 > this server crashes when switching to the console or shutting > down (crashing is sometimes, not always), very nice screen which > slowly turns white This is either distribution or hardware specific. Try with vanilla 6.8.2 and stock DRM modules, perhaps? Best regards, -- Karol 'sziwan' Kozimor [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
On Die, 22 Feb 2005, Karol Kozimor wrote: > Thus wrote Norbert Preining: > > - DRI must be disabled I guess?! Even with newer X server (x.org)? > > You still didn't state which X server are you using. In short, XFree86 4.4, I have stated it several times, but here a sum up: - XFree86 4.3 (debian/sid) no work - X.Org 6.8.1.99 (debian -dri-trunk stuff plus kernel modules9 no work with 2.6.11-rc4 and 2.6.11-rc3-mm2 this server crashes when switching to the console or shutting down (crashing is sometimes, not always), very nice screen which slowly turns white Best wishes Norbert --- Norbert Preining Università di Siena sip:[EMAIL PROTECTED] +43 (0) 59966-690018 gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- QUEDGELEY (n.) A rabidly left-wing politician who can afford to be that way because he married a millionairess. --- Douglas Adams, The Meaning of Liff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Call for help: list of machines with working S3
On Mon, 14 Feb 2005 22:11:05 +0100, Pavel Machek <[EMAIL PROTECTED]> wrote:
> Hi!
> Table of known working systems:
>
> Model hack (or "how to do it")
> --
> IBM TP R32 / Type 2658-MMG none (1)
> Athlon HP Omnibook XE3 none (1)
> Compaq Armada E500 - P3-700 none (1) (S1 also works OK)
> IBM t41pnone (1)
I am not sure if this is a problem with my machine or the code, but my
T41p does not work "correctly." [1] Pressing the sleep key (Fn-F4),
does sleep the machine, very quickly and nicely. However, on wake-up,
only an external CRT will display video. I see the LCD's backlight
come on, but no video is displayed there. I also noticed that my USB
mouse does not seem to work (this may be a BIOS setting issue, which
I'll check out on next reboot -- soon).
I have noticed that the IBM ACPI extras seems to do some things
incorrectly for me. /proc/acpi/ibm/dock always reports "status:
undocked," even though I'm very much docked right now. Echo'ing
auto_enable/auto_disable into /proc/acpi/ibm/video does change the
auto state, but doing the same for {lcd,crt}_{enable,disable} does
nothing (including not changing the displayed state).
I'm more than happy to try patches, BIOS setting changes, etc.
Thanks,
Nish
[1] Attached dmidecode output (hopefully not screwed up by gmail)
dmidecode.out
Description: Binary data
Re: [ACPI] Call for help: list of machines with working S3
Thus wrote Norbert Preining: > - DRI must be disabled I guess?! Even with newer X server (x.org)? You still didn't state which X server are you using. In short, XFree86 4.4, X.Org 6.7 and 6.8.2 are fine, anything other (including X.Org 6.8.0 and .1) is not. Best regards, -- Karol 'sziwan' Kozimor [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Thus wrote Alistair John Strachan: > I discovered that either the i2c_core.ko or i2c_i801.ko modules cause the > hang > on resume! If you stop the entire i2c subsystem from being loaded by hotplug > (note this is the BUS driver, not the sensors driver!), then resume works > perfectly! Presumably there's a bug in the resuming of this module. Might it be another instance of the LPC chip config space messed up on resume? Best regards, -- Karol 'sziwan' Kozimor [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
fre, 18,.02.2005 kl. 20.49 +, skrev Alistair John Strachan: > On Wednesday 16 Feb 2005 14:25, Kjartan Maraas wrote: > > tir, 15,.02.2005 kl. 17.42 +, skrev Alistair John Strachan: > > > On Tuesday 15 Feb 2005 16:16, Lorenzo Colitti wrote: > > > [snip] > > > > > > > Ok, here is the output from dmidecode (Debian package) and from lspci. > > > > I don't have acpidmp and I don't know where to get it, but if you think > > > > it's necessary I can download it if you tell me where to find it. > > > > > > Find below a diff of my dmidecode output versus Lorenzo's. Nothing much > > > to call home about. > > > > I've attached a diff against Lorenzo's too. Only difference is that my > > laptop is a nc4010, and looking here it's clear that this model doesn't > > support APM at least. I also have non-working S3. It behaves just like > > the entry in the ubuntu wiki for the nc6000 in all three cases with a > > full system running at least. I'll try init=/bin/sh later to see if that > > helps and if it does experiment with removing modules one by one... > > Got it. Sorry for the radio silence, I've been busy for a few days. > > I discovered that either the i2c_core.ko or i2c_i801.ko modules cause the > hang > on resume! If you stop the entire i2c subsystem from being loaded by hotplug > (note this is the BUS driver, not the sensors driver!), then resume works > perfectly! Presumably there's a bug in the resuming of this module. > > In other news, USB devices only work after I remove uhci_hcd and ehci_hcd and > reload them. > > The s3_bios workaround allows video to kind of work, but I can't use anything > other than vga=normal (vesafb results in corruption), and the screen is no > longer artificially resized to fill the LCD, it's native res and centered > (which sure is annoying). > > Kjartan, I hope you isolate the driver causing you problems, as it seems > these > machines can be made, even if it is a bit of a headache. > I tried it again now using init=/bin/sh and acpi_sleep=s3_bios and it still gives a black screen on resume... :-/ Cheers Kjartan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Hello! On Fri 18 Feb 2005 21:49, Alistair John Strachan wrote: > I discovered that either the i2c_core.ko or i2c_i801.ko modules cause the > hang > on resume! If you stop the entire i2c subsystem from being loaded by hotplug > (note this is the BUS driver, not the sensors driver!), then resume works > perfectly! Presumably there's a bug in the resuming of this module. Well, on my IBM ThinkPad T42p (ATI FireGL T2 128MB), I can resume with both I2C modules loaded, so probably the problem is not specific to the I2C subsystem. > In other news, USB devices only work after I remove uhci_hcd and ehci_hcd and > reload them. I just tested two USB devices after S3 resuming without having removed the USB modules (uhci-hcb and ehci-hcd): - Logitech USB Wheel Mouse (046d:c00c, USB 1.x), it works with no problem on console, but not on X (this was caused by the fact that I've two corepointer on my XF86Config-4, in fact after having corrected this error and restarted X, the USB mouse works) - Mitsubishi Chemical 2.5" HD Case (05e3:0702, USB 2.0 [1], with a SAMSUNG MP0804H 80GB), it works with no problem :-D > The s3_bios workaround allows video to kind of work, but I can't use anything > other than vga=normal (vesafb results in corruption), and the screen is no > longer artificially resized to fill the LCD, it's native res and centered > (which sure is annoying). Again, IMHO the problem is specific to your machine: I use the radeonfb (with acpi_sleep=s3_bios) and the resume is ok (both in console and Debian XFree86-4.3.0.dfsg.1-11, radeon driver). Thx, bye, Gismo / Luca [1] http://www.qbik.ch/usb/devices/showdescr.php?id=3039 pgpFAuFgB8Bft.pgp Description: PGP signature
Re: [ACPI] Re: Call for help: list of machines with working S3
On Wednesday 16 Feb 2005 14:25, Kjartan Maraas wrote: > tir, 15,.02.2005 kl. 17.42 +, skrev Alistair John Strachan: > > On Tuesday 15 Feb 2005 16:16, Lorenzo Colitti wrote: > > [snip] > > > > > Ok, here is the output from dmidecode (Debian package) and from lspci. > > > I don't have acpidmp and I don't know where to get it, but if you think > > > it's necessary I can download it if you tell me where to find it. > > > > Find below a diff of my dmidecode output versus Lorenzo's. Nothing much > > to call home about. > > I've attached a diff against Lorenzo's too. Only difference is that my > laptop is a nc4010, and looking here it's clear that this model doesn't > support APM at least. I also have non-working S3. It behaves just like > the entry in the ubuntu wiki for the nc6000 in all three cases with a > full system running at least. I'll try init=/bin/sh later to see if that > helps and if it does experiment with removing modules one by one... Got it. Sorry for the radio silence, I've been busy for a few days. I discovered that either the i2c_core.ko or i2c_i801.ko modules cause the hang on resume! If you stop the entire i2c subsystem from being loaded by hotplug (note this is the BUS driver, not the sensors driver!), then resume works perfectly! Presumably there's a bug in the resuming of this module. In other news, USB devices only work after I remove uhci_hcd and ehci_hcd and reload them. The s3_bios workaround allows video to kind of work, but I can't use anything other than vga=normal (vesafb results in corruption), and the screen is no longer artificially resized to fill the LCD, it's native res and centered (which sure is annoying). Kjartan, I hope you isolate the driver causing you problems, as it seems these machines can be made, even if it is a bit of a headache. Lorenzo, thanks for your kernel config. It made it a lot easier to debug this problem. -- Cheers, Alistair. personal: alistair()devzero!co!uk university: s0348365()sms!ed!ac!uk student:CS/CSim Undergraduate contact:1F2 55 South Clerk Street, Edinburgh. EH8 9PP. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Am Freitag, 18. Februar 2005 14:38 schrieb Norbert Preining: > On Fre, 18 Feb 2005, Norbert Preining wrote: > > I tried: > > 2.6.11-rc3-mm2 + Xorg + DRI disabled > > and this works. > > > > I cannot enable dri/drm with the cvs version of the drm modules, because > > the drm modules do not compile for -mm kernels, since there is the patch > > for multiple agp bridges included (that's the reason why I tried -rc4 > > Final observation: After patching in the changes from mm kernels for > multiple agp bridges to the drm-source code (the patch > drm-add-support-for-new-multiple-agp-bridge-agpgart-api.patch from the > broken out archive) I could compile the drm-trunk-src modules. > > So now I am running with 2.6.11-rc3-mm2 + Xorg + DRI enabled (and > working) with the drm modules from drm-trunk-module-src. > > Outcome: freeze when switching to X. As with the other modules (in fact > I think that most of the changes to the drm stuff are included in the mm > kernel, so this should not change anything, as mm pulls from bk-agpgart, > bk-drm-via) a funny screen, and the CapsLock light is blinking. Kernel panik. Can you ssh into your maschine and get a dmesg? I recommend you to write to the dri devs. Stefan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
On Fre, 18 Feb 2005, Norbert Preining wrote: > I tried: > 2.6.11-rc3-mm2 + Xorg + DRI disabled > and this works. > > I cannot enable dri/drm with the cvs version of the drm modules, because > the drm modules do not compile for -mm kernels, since there is the patch > for multiple agp bridges included (that's the reason why I tried -rc4 Final observation: After patching in the changes from mm kernels for multiple agp bridges to the drm-source code (the patch drm-add-support-for-new-multiple-agp-bridge-agpgart-api.patch from the broken out archive) I could compile the drm-trunk-src modules. So now I am running with 2.6.11-rc3-mm2 + Xorg + DRI enabled (and working) with the drm modules from drm-trunk-module-src. Outcome: freeze when switching to X. As with the other modules (in fact I think that most of the changes to the drm stuff are included in the mm kernel, so this should not change anything, as mm pulls from bk-agpgart, bk-drm-via) a funny screen, and the CapsLock light is blinking. Best wishes Norbert --- Norbert Preining Università di Siena sip:[EMAIL PROTECTED] +43 (0) 59966-690018 gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- `That young girl is one of the least benightedly unintelligent organic life forms it has been my profound lack of pleasure not to be able to avoid meeting.' --- Marvin's first ever compliment about anybody. --- Douglas Adams, The Hitchhikers Guide to the Galaxy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
On Don, 17 Feb 2005, Stefan Dösinger wrote: > > Ok, I installed xlibmesa-gl1-dri-trunk, xserver-xfree86-dri-trunk and > > compiled linux-2.6.11-rc4 and drm modules from drm-trunk-module-src, all > > from http://www.nixnuts.net/files/ > > > > But I had no success whatsoever. With this (Xorg server, current dri/drm > > stuff, ..) the laptop not even wakes up from sleep! > Sorry, no Idea. What about 2.6.11-rc3-mm2 + Xorg 6.8.1.99? Did you test this > combination? I tried: 2.6.11-rc3-mm2 + Xorg + DRI disabled and this works. I cannot enable dri/drm with the cvs version of the drm modules, because the drm modules do not compile for -mm kernels, since there is the patch for multiple agp bridges included (that's the reason why I tried -rc4 without mm) and the drm modules from drm-trunk-module-src are not prepared to the change of the api. I even tried to incorporate the changes to the api but gave up. I *can* active dri but with the builtin kernel drm modules, which makes the kernel freeze while resuming. > Am I right with assuming that resumeworked after the X upgrade if X wasn't > started before suspend? NO!!! Most interestingly: Doing a suspend from single user mode makes the machine freeze (not even sysrq!) I suspect that it has to do with the restoring of graphics state with vbetool from a data set which was taken *while* running X: My suspend2ram script looks like this (as suggested here): statedir=/root/s3/state /usr/bin/chvt 1 cat /dev/vcsa >$statedir/vcsa sync echo 3 > /proc/acpi/sleep sync vbetool post vbetool vbestate restore <$statedir/vbe cat $statedir/vcsa >/dev/vcsa ... but $statedir/vbe was taken once for XFree86 running. Can this be the reason for the freeze? Best wishes Norbert --- Norbert Preining Università di Siena sip:[EMAIL PROTECTED] +43 (0) 59966-690018 gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- MAVIS ENDERBY (n.) The almost-completely-forgotten girlfriend from your distant past for whom your wife has a completely irrational jealousy and hatred. --- Douglas Adams, The Meaning of Liff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3 (fwd)
Pavel Machek schrieb: > >>>I'm not sure if you can push the whole industry at once. >> >>The goal is to know what to tell the system vendors >>interested in supporting Linux what they should do >>with their BIOS on future platforms. >> >>I believe our message should be: >>1. BIOS should save/restore video in S3 > > Actually, that'd expect too much of BIOS writers. I believe right > solution is "POST video as you do during normal boot in S3 resume". Why not leave the choice to the BIOS writers? If some are able to save/restore video state by themselves, we shoudln't stop them. As long as the state after resume accepts setting the mode without lockup, we should be fine. >>2. Use Intel's ACPICA ASL compiler -- if not for production, >>then at least as a static source code checker for validation. > > > 3. Try to boot linux (here's live cd). If it complains about bios bugs > (dmesg | grep ...), try to see if it is not indeed your bug. That could even be automated more. A live cd which boots, performs a few tests, displays the results on screen and offers an option to save these results to usbstick/network/disk/whatever. After saving the boot results, it will perform a S3 suspend and resume and display/save the results of that, too. If Intel have enough money, they could provide the functionality on a hard disk and it would have the benefit that S4 could be tested as well. If the disk has a FAT32 partition, the results can be saved there. Regards, Carl-Daniel -- http://www.hailfinger.org/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3 (fwd)
Hi! Sorry, I was too fast with my mail client. Please cc: Len in your replies. To: Len Brown <[EMAIL PROTECTED]> Subject: Re: [ACPI] Call for help: list of machines with working S3 X-Warning: Reading this can be dangerous to your mental health. Hi! > > I'm not sure if you can push the whole industry at once. > > The goal is to know what to tell the system vendors > interested in supporting Linux what they should do > with their BIOS on future platforms. > > I believe our message should be: > 1. BIOS should save/restore video in S3 Actually, that'd expect too much of BIOS writers. I believe right solution is "POST video as you do during normal boot in S3 resume". > 2. Use Intel's ACPICA ASL compiler -- if not for production, > then at least as a static source code checker for validation. 3. Try to boot linux (here's live cd). If it complains about bios bugs (dmesg | grep ...), try to see if it is not indeed your bug. -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - End forwarded message - -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Hello Pavel! On Mon 14 Feb 2005 22:11, Pavel Machek wrote: > Stefan provided me initial list of machines where S3 works (including > video). If you have machine that is not on the list, please send me a > diff. If you have eMachines... I'd like you to try playing with Sorry, but a diff of what? Of the list? > Table of known working systems: > > Model hack (or "how to do it") > -- IBM ThinkPad T42p (2373-GTG [1]) acpi_sleep=s3_bios (2) More info available upon request, but in general: - Debian unstable - vanilla kernel 2.6.10 - ACPI patch 20050125 - BlueZ patch -mh4 - IBM trackpoint patch [2] - radeonfb - radeon XFree86 4.3.0.dfsg.1-11 - all modules my laptop support installed (and loaded ;-) ) - I used a script that switch to vc1 and stop mysql (this is a known problem [3] [4]), then "echo -n [mem|disk] > /sys/power/state" I've a working S4 with the same configuration, too. But it seems I still suffer a problem about hwclock I already reported with another laptop [5] [6]. In this case, the command proposed seems not working anymore (I should test more deeply, just a question of time ;-) ). Anyway, this laptop works very well! I've also a docking station [7], I'll test with it ASAP. Thx, bye, Gismo / Luca [1] http://www5.pc.ibm.com/ch/products.nsf/$wwwPartNumLookup/_UC2GTSE?OpenDocument [2] http://people.clarkson.edu/~evanchsa/ [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=259745 [4] http://bugs.mysql.com/bug.php?id=4596 [5] http://sourceforge.net/mailarchive/message.php?msg_id=9844751 [6] http://sourceforge.net/mailarchive/message.php?msg_id=9864402 [7] http://www5.pc.ibm.com/ch/products.nsf/$wwwPartNumLookup/_74P6733?OpenDocument pgpkSj2De7ysa.pgp Description: PGP signature
Re: [ACPI] Call for help: list of machines with working S3
On Thu, 2005-02-17 at 05:15, Vojtech Pavlik wrote: > I'm not sure if you can push the whole industry at once. The goal is to know what to tell the system vendors interested in supporting Linux what they should do with their BIOS on future platforms. I believe our message should be: 1. BIOS should save/restore video in S3 2. Use Intel's ACPICA ASL compiler -- if not for production, then at least as a static source code checker for validation. thanks, -Len - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Am Donnerstag, 17. Februar 2005 20:08 schrieb Norbert Preining: > On Die, 15 Feb 2005, Stefan Dösinger wrote: > > > - DRI must be disabled I guess?! Even with newer X server (x.org)? > > > > Do you use the fglrx driver? This doesn't work with any type of suspend > > so far. If you use the radeon driver try a driver update. > > Ok, I installed xlibmesa-gl1-dri-trunk, xserver-xfree86-dri-trunk and > compiled linux-2.6.11-rc4 and drm modules from drm-trunk-module-src, all > from http://www.nixnuts.net/files/ > > But I had no success whatsoever. With this (Xorg server, current dri/drm > stuff, ..) the laptop not even wakes up from sleep! Sorry, no Idea. What about 2.6.11-rc3-mm2 + Xorg 6.8.1.99? Did you test this combination? Am I right with assuming that resumeworked after the X upgrade if X wasn't started before suspend? Stefan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Hi! > >>4. Include a mandantory description of video bringup after resume > > > > That sounds overcomplicated. Simply add this to the specs: > > You have to start to think like a vendor with a long legacy. Then my > spec draft will make more sense. Basically, you can't tell a vendor > that his hardware is broken or he will ignore your efforts from that > point on. "It's a question of honour." If, on the other hand, a > vendor can claim his products are conforming to the spec by issuing > a software update for broken hardware, it is much more likely that > the spec gets accepted. Well, whether you POST video or not is still only software... anyway... Your _WAK idea could work for notebooks (but if you did it in _WAK you'd break windows, so you'd have to call it _VWK (VideoWaK) or something), but for desktop where user can plug in any video card he buys... I do not see how you can get away with something other than normal POST. > > BIOS must do that during normal boot; this should be very little > > additional work. > > Not necessarily. Some BIOSes stay in graphics mode during the whole > bootup (at least it seems so) and would have to include additional > code to enter 80x25 text mode. ??? When grub is launched, you are in 80x25 text mode. Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Pavel Machek schrieb: > >>>to reinitialise the graphics hardware, few are going to care about >>>making life easier for Linux. >> > [...] >>3. Get some shiny certification/label going that can be put on >>fully conforming products as a sticker. Something like the old >>"EPA pollution preventer" logo, but with a more appealing design. >>Perhaps a "InstantOn/PowerSave" sticker, you get the idea. > > Like "This machine actually works" sticker? :-) Yes. >>4. Include a mandantory description of video bringup after resume > > That sounds overcomplicated. Simply add this to the specs: You have to start to think like a vendor with a long legacy. Then my spec draft will make more sense. Basically, you can't tell a vendor that his hardware is broken or he will ignore your efforts from that point on. "It's a question of honour." If, on the other hand, a vendor can claim his products are conforming to the spec by issuing a software update for broken hardware, it is much more likely that the spec gets accepted. > "BIOS must POST video during S3 wakeup. Video must be working > and in 80x25 text mode when it jumps to OS. VESA BIOS calls must be > available to the OS." That would make some products non-conformant which are working perfectly today. If the video state is preserved over S3, it doesn't make sense to declare that behaviour non-conformant. > BIOS must do that during normal boot; this should be very little > additional work. Not necessarily. Some BIOSes stay in graphics mode during the whole bootup (at least it seems so) and would have to include additional code to enter 80x25 text mode. Regards, Carl-Daniel -- http://www.hailfinger.org/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Vernon Mauery schrieb: > Carl-Daniel Hailfinger wrote: > >>1. A first step towards better DSDTs would be to make the ASL compiler >>complain about the same things which are complained about by the >>in-kernel ACPI interpreter. An example would be the following: >> >>acpi_processor-0496 [10] acpi_processor_get_inf: Invalid PBLK length [7] >> >>The ASL compiler will not complain about it, yet the kernel will >>refuse to do any processor throttling with a PBLK length of 7. > > > This is like getting gcc to complain about run-time bugs in a program. Oh, gcc does that to a certain extent. For example, it has warnings like "this comparison is always true" or "value too big for selected type". > The compiler of a language (ASL in this case) compiles the language, > regardless of run-time bugs because it can only detect syntax errors. > And iasl does that pretty well. It is possible to do quite a bit of semantic verification at compile time, but of course there are limits to everything. Regards, Carl-Daniel -- http://www.hailfinger.org/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Hi! > > to reinitialise the graphics hardware, few are going to care about > > making life easier for Linux. > > 1. A first step towards better DSDTs would be to make the ASL compiler > complain about the same things which are complained about by the > in-kernel ACPI interpreter. An example would be the following: > > acpi_processor-0496 [10] acpi_processor_get_inf: Invalid PBLK length [7] > > The ASL compiler will not complain about it, yet the kernel will > refuse to do any processor throttling with a PBLK length of 7. Not sure if you can check all interesting stuff statically. > 2. Urge/force vendors to use the latest ASL compiler available. Heh, good luck. > 3. Get some shiny certification/label going that can be put on > fully conforming products as a sticker. Something like the old > "EPA pollution preventer" logo, but with a more appealing design. > Perhaps a "InstantOn/PowerSave" sticker, you get the idea. Like "This machine actually works" sticker? :-) > 4. Include a mandantory description of video bringup after resume That sounds overcomplicated. Simply add this to the specs: "BIOS must POST video during S3 wakeup. Video mujst be working and in 80x25 text mode when it jumps to OS. VESA BIOS calls must be available to the OS." BIOS must do that during normal boot; this should be very little additional work. Pavel -- 64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
On Die, 15 Feb 2005, Pavel Machek wrote: > > - Sometimes I have to make a Sysrq-s (sync) to get some stuff running > > (eg logging in from the console hangs after input of passwd, calling > > sysrq-s makes it continue). I had a similar effect when logging in > > AFTER resuming (for the resume I had only gdm running but wasn't > > logged in) the GNOME starting screen stayed there indefinitely, no > > change. Even after restarting the X server and retrying. > > Logging in with twm session DID work without any problem. > > Do you have any idea what this could be? > > Does it happen with swsusp? Is it in any way reproducible? Maybe > commenting out refrigerator would help Hmm, don't have swsusp in my kernel (2.6.11-rc3-mm2). reproducible: Not deterministically, i.e. it happened again, but then again not always. Sorry. Best wishes Norbert --- Norbert Preining Università di Siena sip:[EMAIL PROTECTED] +43 (0) 59966-690018 gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- PLYMOUTH (vb.) To relate an amusing story to someone without remembering that it was they who told it to you in the first place. --- Douglas Adams, The Meaning of Liff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
On Die, 15 Feb 2005, Stefan Dösinger wrote: > > - DRI must be disabled I guess?! Even with newer X server (x.org)? > Do you use the fglrx driver? This doesn't work with any type of suspend so > far. If you use the radeon driver try a driver update. Ok, I installed xlibmesa-gl1-dri-trunk, xserver-xfree86-dri-trunk and compiled linux-2.6.11-rc4 and drm modules from drm-trunk-module-src, all from http://www.nixnuts.net/files/ But I had no success whatsoever. With this (Xorg server, current dri/drm stuff, ..) the laptop not even wakes up from sleep! Now I am back at debian XFree 4.3.0.1 and DRI disabled and suspend works again. I don't know wether this is a problem with the kernel or the drm, so to sum up: - kernel 2.6.11-rc3-mm2, XFree 4.3.0.1 (debian/sid), no dri works - kernel 2.6.11-rc4, Xorg 6.8.1.99 (debian sid + nixnuts), drm cvs, drm activated no resume (thus also no test for X) Best wishes Norbert --- Norbert Preining Università di Siena sip:[EMAIL PROTECTED] +43 (0) 59966-690018 gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- SWANIBOST (adj.) Complete shagged out after a hard day having income tax explained to you. --- Douglas Adams, The Meaning of Liff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Carl-Daniel Hailfinger wrote: > 1. A first step towards better DSDTs would be to make the ASL compiler > complain about the same things which are complained about by the > in-kernel ACPI interpreter. An example would be the following: > > acpi_processor-0496 [10] acpi_processor_get_inf: Invalid PBLK length [7] > > The ASL compiler will not complain about it, yet the kernel will > refuse to do any processor throttling with a PBLK length of 7. This is like getting gcc to complain about run-time bugs in a program. The compiler of a language (ASL in this case) compiles the language, regardless of run-time bugs because it can only detect syntax errors. And iasl does that pretty well. --Vernon - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Matthew Garrett schrieb: > On Thu, 2005-02-17 at 01:16 -0500, Len Brown wrote: > >>I think that it is the BIOS' job on S3-suspend >>to save the video mode. On S3-resume the BIOS should >>re-POST and restore the video mode. > > I agree, but in the absence of spec requirement and some form of > certification process, I don't see it happening in the near future. > Given that vendors are still shipping invalid DSDTs, if Windows is able > to reinitialise the graphics hardware, few are going to care about > making life easier for Linux. 1. A first step towards better DSDTs would be to make the ASL compiler complain about the same things which are complained about by the in-kernel ACPI interpreter. An example would be the following: acpi_processor-0496 [10] acpi_processor_get_inf: Invalid PBLK length [7] The ASL compiler will not complain about it, yet the kernel will refuse to do any processor throttling with a PBLK length of 7. 2. Urge/force vendors to use the latest ASL compiler available. In most cases, this will result in a size reduction of the compiled code, which should be in the interest of the vendors. 3. Get some shiny certification/label going that can be put on fully conforming products as a sticker. Something like the old "EPA pollution preventer" logo, but with a more appealing design. Perhaps a "InstantOn/PowerSave" sticker, you get the idea. 4. Include a mandantory description of video bringup after resume into the ACPI spec along the lines of "Conforming products SHOULD make information about handling of the primary video device on resume available to the ACPI interpreter during runtime. If video state will be preserved over a suspend/resume cycle, the _WAK method for said video device MUST be empty. If the video device requires any actions by the operating system after resume to restore the state it had before suspend, the _WAK method for said video device MUST contain ALL the code needed to restore the state before suspend. The _WAK method MAY call OS-supplied ACPI helper functions like ACPI_EXECUTE_CODE_FROM_ROM to keep the _WAK method short. If no _WAK method for a given video device is available, the OS MUST be able to rely on the fact that video state is preserved over suspend/resume. Something like item 4 would be a major step forward and as a bonus, it wouldn't require any hardware changes, only perhaps 3 or 4 additional lines of code in the DSDT. If the _WAK function for my laptop graphics card existed and had the hypothetical commands ACPI_EXECUTE_CODE_FROM_ROM_X86(VGA.ROM) ACPI_RESTORE_VESA_STATE(VGA) we wouldn't have this discussion in the first place. Regards, Carl-Daniel -- http://www.hailfinger.org/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
On Die, 15 Feb 2005, Stefan Dösinger wrote: > > After deactivating DRI in the X config file and saving the states with > > your script (thanks) and turning off various stuff I get X running > > again. > > > > Questions: > > - DRI must be disabled I guess?! Even with newer X server (x.org)? > > Do you use the fglrx driver? This doesn't work with any type of suspend so No > far. If you use the radeon driver try a driver update. >From deb http://www.nixnuts.net/files/ ./ ?? Or direct from dri.freedesktop.org, and updating X to X.org on sid? Best wishes Norbert --- Norbert Preining Università di Siena sip:[EMAIL PROTECTED] +43 (0) 59966-690018 gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- SWANIBOST (adj.) Complete shagged out after a hard day having income tax explained to you. --- Douglas Adams, The Meaning of Liff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Hi! > I think that it is the BIOS' job on S3-suspend > to save the video mode. On S3-resume the BIOS should > re-POST and restore the video mode. Can you find it written down somewhere? It would be certainly easier for me if every BIOS did re-post, but it is not the case on any new BIOS > To completely solve the Linux S3 video restore issue, > we need to push the platform and BIOS vendors. > > What am I missing? I think we are missing few lines in docs somewhere saying "video must be re-POSTed during S3 wakeup". And then we miss someone going around vendors with baseball bat, telling them to fix their BIOSes. Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
On Thu, 2005-02-17 at 01:16 -0500, Len Brown wrote: > Pavel, > I think that it is the BIOS' job on S3-suspend > to save the video mode. On S3-resume the BIOS should > re-POST and restore the video mode. I agree, but in the absence of spec requirement and some form of certification process, I don't see it happening in the near future. Given that vendors are still shipping invalid DSDTs, if Windows is able to reinitialise the graphics hardware, few are going to care about making life easier for Linux. -- Matthew Garrett | [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
On Thu, Feb 17, 2005 at 01:16:45AM -0500, Len Brown wrote: > Pavel, > I think that it is the BIOS' job on S3-suspend > to save the video mode. On S3-resume the BIOS should > re-POST and restore the video mode. Should. But this definitely is not the case on about 80+% of notebooks. You can save the video state through VESA VBE, and restore it on resume, but if the BIOS didn't re-POST the video, this will often fail. > While Linux's X drivers may be able to handle the case > where X is running -- that doesn't help us with the > cases where X is not running (a case that Windows > presumably does not have). > > Besides updated X drivers, which may have complicated > restore routines for complicated modes, all the other > techniques for restoring video from Linux are > hit/miss workarounds for broken platforms. > > To completely solve the Linux S3 video restore issue, > we need to push the platform and BIOS vendors. That's correct. > What am I missing? I'm not sure if you can push the whole industry at once. -- Vojtech Pavlik SuSE Labs, SuSE CR - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Pavel, I think that it is the BIOS' job on S3-suspend to save the video mode. On S3-resume the BIOS should re-POST and restore the video mode. While Linux's X drivers may be able to handle the case where X is running -- that doesn't help us with the cases where X is not running (a case that Windows presumably does not have). Besides updated X drivers, which may have complicated restore routines for complicated modes, all the other techniques for restoring video from Linux are hit/miss workarounds for broken platforms. To completely solve the Linux S3 video restore issue, we need to push the platform and BIOS vendors. What am I missing? thanks, -Len - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Call for help: list of machines with working S3
On Thu, Feb 17, 2005 at 12:22:57AM +0100, Pavel Machek wrote: > > does anyone have some experiences with intel i855 video card and S3? > > > > For me the binary driver from Intel works with S3 but only X server is > > restored > > not the text console. > > > > With open source driver nothing is restored. I try to use s3_bios or > > s3_mode, > > nothing helps. Using vbetool and post causes backlight turn on but display > > is > > full of garbage (vertical lines of different colors). > > Can you do vga=normal and attempt to reload fonts? Did not help. Instead, this seems to be working with X.org and opensource driver: chvt 1 vbetool vbestate save > /tmp/state echo 3 > /proc/acpi/sleep vbetool post vbetool vbestate restore < /tmp/state chvt 7 (if X server is running then chvt to text console is necessary, but it works including DRI and XV overlay running) Can I get the current console so that chvt 7 can switch to the original console? Just re-POST seems to initialize first head connected to external CRT. The second head (connected to LFP) is not initialized. Do not know why :( This is the videocard: Intel Corp. 82852/855GM Integrated Graphics Device. Notebook: Acer TM 242FX -- Lukáš Hejtmánek - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Call for help: list of machines with working S3
Hi! > does anyone have some experiences with intel i855 video card and S3? > > For me the binary driver from Intel works with S3 but only X server is > restored > not the text console. > > With open source driver nothing is restored. I try to use s3_bios or s3_mode, > nothing helps. Using vbetool and post causes backlight turn on but display is > full of garbage (vertical lines of different colors). Can you do vga=normal and attempt to reload fonts? Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Am Mittwoch, 16. Februar 2005 16:06 schrieb Carl-Daniel Hailfinger: > Stefan Dösinger schrieb: > >>The problems with this patch are: > >>- you need to press a key to come back from the "resume-console" after > >>resume. - DRI in X does not work (at least for me with intel-agp, others > >>reportet it works) > >>I just disabloed it by not loading intel-agp (hotplug-blacklist) > > > > You can force the radeon X driver to use pci mode by setting Option > > "ForcePciMode" to "true" or something simmilar in you X config file. This > > way you can get dri without intel-agp. This is much slower, but enought > > to play tuxracer ;-) > > How do I enable DRI with my card to test that crash? I have the > following in my XF86Config: > > Section "DRI" > Group "video" > Mode 0660 > EndSection > > but nothing else about DRI. So do I have to change something in > my configuration? > > Oh, and could you please include run "lspci -vv" and include the > part about VGA compatible controller in your mail? I have some > hypothesis about the settings there having to do with resume. You can set Option "BusType" "PCI" in your cards driver section in xorg.conf / XF86Config. With this setting you should get DRI without having intel-agp loaded(if the rest is set up correctly) My lspci output is: :00:00.0 Host bridge: Intel Corp. 82855PM Processor to I/O Controller (rev 03) Subsystem: Acer Incorporated [ALI]: Unknown device 001f Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Reset- FastB2B- :00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03) (prog-if 00 [UHCI]) Subsystem: Acer Incorporated [ALI]: Unknown device 001f Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Reset- FastB2B- :00:1f.0 ISA bridge: Intel Corp. 82801DBM (ICH4-M) LPC Interface Bridge (rev 03) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Region 1: I/O ports at Region 2: I/O ports at Region 3: I/O ports at Region 4: I/O ports at 1860 [size=16] Region 5: Memory at 2000 (32-bit, non-prefetchable) [size=1K] :00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 03) Subsystem: Acer Incorporated [ALI]: Unknown device 001f Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Reset+ 16bInt+ PostWrite- 16-bit legacy interface ports at 0001 :02:06.1 CardBus bridge: O2 Micro, Inc. OZ711M1 SmartCardBus MultiMediaBay Controller (rev 20) Subsystem: Acer Incorporated [ALI]: Unknown device 001f Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- SERR- Reset- 16bInt- PostWrite- 16-bit legacy interface ports at 0001 :02:06.2 System peripheral: O2 Micro, Inc. OZ711Mx MultiMediaBay Accelerator Subsystem: Acer Incorporated [ALI]: Unknown device 001f Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- SERR- TAbort- SERR- http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
On Wed, 16 Feb 2005 16:06:00 +0100, Carl-Daniel Hailfinger <[EMAIL PROTECTED]> wrote: > Stefan Dösinger schrieb: > >>The problems with this patch are: > >>- you need to press a key to come back from the "resume-console" after > >>resume. - DRI in X does not work (at least for me with intel-agp, others > >>reportet it works) > >>I just disabloed it by not loading intel-agp (hotplug-blacklist) > > > > You can force the radeon X driver to use pci mode by setting Option > > "ForcePciMode" to "true" or something simmilar in you X config file. This > > way > > you can get dri without intel-agp. This is much slower, but enought to play > > tuxracer ;-) > > How do I enable DRI with my card to test that crash? I have the > following in my XF86Config: > > Section "DRI" > Group "video" > Mode 0660 > EndSection > > but nothing else about DRI. So do I have to change something in > my configuration? > you need to compile the right modules and load the agp-bridge's and your gfx module. > Oh, and could you please include run "lspci -vv" and include the > part about VGA compatible controller in your mail? I have some > hypothesis about the settings there having to do with resume. > I attached the full output because there are some more "AGP" there. I just tried it again and it only crashed my X after resume with intel-agp .. I was able to type still and start a new X but when I tried to run a 3d-app it hard crashed and I had to reboot :( I hope you have an idea. Regards, Stefan lspcivv Description: Binary data
Re: [ACPI] Call for help: list of machines with working S3
On Wed, Feb 16, 2005 at 03:54:38PM +0100, Carl-Daniel Hailfinger wrote: > Romano Giannetti schrieb: > > > > I tried with my Sony Vaio FX701. No luck. It goes S3 ok, but it will never > > come back (blank screen, HDD led fixed on). > > > > I am wishing to help, imply tell me what I have to do. > > Please tell us about your graphics chipset, your .config, your > dmesg and the modules loaded. Then we my be able to help. Oops, sorry, I should have added the info before. My apologies. Here will find all the info (if you need more, tell me). Note that I tried with and without ndiswrapper driver loaded, and I have the same hang on resume (blank screen, HDD light fixed on, and no answer to wireless pings). One more note: the ndiswrapper *did* survive OK to a disk suspend cycle. I am running an up-to-date Mandrake 10.0 distribution, with a kernel 2.6.11-rc1 (Linus tree), on a Sony Vaio PGC-FX701 which is almost working perfectly. * Patch applied: - a little patch for ALPS pad detection. http://www.dea.icai.upco.es/romano/linux/alps-detection-2611rc1.txt * .config: http://www.dea.icai.upco.es/romano/linux/config-2.6.11rc1.txt * lsmod after boot: http://www.dea.icai.upco.es/romano/linux/lsmod.txt * lspci -vv http://www.dea.icai.upco.es/romano/linux/lspci.txt * dmesg http://www.dea.icai.upco.es/romano/linux/dmesg.txt * /proc/acpi/dsdt http://www.dea.icai.upco.es/romano/linux/mydsdt.bin More data on http://perso.wanadoo.es/r_mano/vaio/vaio.html Thanks again, Romano -- Romano Giannetti - Univ. Pontificia Comillas (Madrid, Spain) Electronic Engineer - phone +34 915 422 800 ext 2416 fax +34 915 596 569 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Stefan Dösinger schrieb: >>The problems with this patch are: >>- you need to press a key to come back from the "resume-console" after >>resume. - DRI in X does not work (at least for me with intel-agp, others >>reportet it works) >>I just disabloed it by not loading intel-agp (hotplug-blacklist) > > You can force the radeon X driver to use pci mode by setting Option > "ForcePciMode" to "true" or something simmilar in you X config file. This way > you can get dri without intel-agp. This is much slower, but enought to play > tuxracer ;-) How do I enable DRI with my card to test that crash? I have the following in my XF86Config: Section "DRI" Group "video" Mode 0660 EndSection but nothing else about DRI. So do I have to change something in my configuration? Oh, and could you please include run "lspci -vv" and include the part about VGA compatible controller in your mail? I have some hypothesis about the settings there having to do with resume. Regards, Carl-Daniel -- http://www.hailfinger.org/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Romano Giannetti schrieb: > On Tue, Feb 15, 2005 at 06:08:37PM +0100, Norbert Preining wrote: > >>On Die, 15 Feb 2005, Carl-Daniel Hailfinger wrote: >> >>>To suspend and resume properly, call the following script as root: >> >>Success. > > I tried with my Sony Vaio FX701. No luck. It goes S3 ok, but it will never > come back (blank screen, HDD led fixed on). > > I am wishing to help, imply tell me what I have to do. Please tell us about your graphics chipset, your .config, your dmesg and the modules loaded. Then we my be able to help. Regards, Carl-Daniel P.S. If anyone of you is running SUSE 9.2, try their latest kernels from ftp.suse.com/pub/projects/kernel/kotd/i386/HEAD/ Additionally, you may have to upgrade mkinitrd and udev with packages from ftp.suse.com/pub/projects and ftp.suse.com/pub/people (try searching around a bit and you'll surely find them). I'm running a kernel from there right now and can still use S3 without problems on my Samsung P35. -- http://www.hailfinger.org/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
tir, 15,.02.2005 kl. 17.42 +, skrev Alistair John Strachan: > On Tuesday 15 Feb 2005 16:16, Lorenzo Colitti wrote: > [snip] > > > > Ok, here is the output from dmidecode (Debian package) and from lspci. I > > don't have acpidmp and I don't know where to get it, but if you think > > it's necessary I can download it if you tell me where to find it. > > Find below a diff of my dmidecode output versus Lorenzo's. Nothing much > to call home about. > I've attached a diff against Lorenzo's too. Only difference is that my laptop is a nc4010, and looking here it's clear that this model doesn't support APM at least. I also have non-working S3. It behaves just like the entry in the ubuntu wiki for the nc6000 in all three cases with a full system running at least. I'll try init=/bin/sh later to see if that helps and if it does experiment with removing modules one by one... --- dmidecode 2005-02-16 15:17:02.127419209 +0100 +++ dmi.out 2005-02-16 15:16:43.142505944 +0100 @@ -1,21 +1,20 @@ # dmidecode 2.5 SMBIOS 2.3 present. -31 structures occupying 1354 bytes. -Table at 0x000FF2EB. +31 structures occupying 1342 bytes. +Table at 0x000FC06F. Handle 0x DMI type 0, 20 bytes. BIOS Information Vendor: Hewlett-Packard - Version: 68BDD Ver. F.0F - Release Date: 07/23/2004 + Version: 68BAS Ver. F.2F + Release Date: 12/10/2004 Address: 0xE Runtime Size: 128 kB - ROM Size: 1024 kB + ROM Size: 512 kB Characteristics: PCI is supported PC Card (PCMCIA) is supported PNP is supported - APM is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported @@ -37,27 +36,27 @@ Handle 0x0001 DMI type 1, 25 bytes. System Information Manufacturer: Hewlett-Packard - Product Name: HP Compaq nc6000 (DJ254A#ABB) - Version: F.0F - Serial Number: XX - UUID: ---- + Product Name: HP Compaq nc4010 (DY885AA#ABN) + Version: F.2F + Serial Number: XX + UUID: ---- Wake-up Type: Power Switch Handle 0x0002 DMI type 2, 8 bytes. Base Board Information Manufacturer: Hewlett-Packard - Product Name: 0890 - Version: 8051 Version 1A.19 + Product Name: 0834 + Version: KBC Version 20.37 Serial Number: Not Specified Handle 0x0003 DMI type 3, 13 bytes. Chassis Information - Manufacturer: Hewlett-Packard + Manufacturer: Hewlett-Packard Type: Notebook Lock: Not Present Version: Not Specified - Serial Number: XX - Asset Tag: + Serial Number: CNU442FBGX + Asset Tag: CNU442FBGX Boot-up State: Safe Power Supply State: Safe Thermal State: Safe @@ -69,8 +68,8 @@ Handle 0x0004 Type: Central Processor Family: Pentium M Manufacturer: Intel(R) - ID: XX XX XX XX XX XX XX XX - Signature: Type 0, Family 6, Model 9, Stepping 5 + ID: D6 06 00 00 BF F9 E9 AF + Signature: Type 0, Family 6, Model 13, Stepping 6 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) @@ -93,13 +92,14 @@ Handle 0x0004 FXSR (Fast floating-point save and restore) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) + SS (Self-snoop) TM (Thermal monitor supported) SBF (Signal break on FERR) - Version: Intel(R) Pentium(R) M processor 1400MHz - Voltage: 1.8 V + Version: Intel(R) Pentium(R) M processor 1.80GHz + Voltage: 1.1 V External Clock: 100 MHz - Max Speed: 1400 MHz - Current Speed: 1400 MHz + Max Speed: 1800 MHz + Current Speed: 1800 MHz Status: Populated, Enabled Upgrade: None L1 Cache Handle: 0x0005 @@ -121,25 +121,25 @@ Handle 0x0005 Burst Installed SRAM Type: Burst Speed: Unknown - Error Correc
Re: Call for help: list of machines with working S3
Hello, does anyone have some experiences with intel i855 video card and S3? For me the binary driver from Intel works with S3 but only X server is restored not the text console. With open source driver nothing is restored. I try to use s3_bios or s3_mode, nothing helps. Using vbetool and post causes backlight turn on but display is full of garbage (vertical lines of different colors). -- Lukáš Hejtmánek - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Hi Carl-Daniel, hi all, On Die, 15 Feb 2005, Carl-Daniel Hailfinger wrote: > > - DRI must be disabled I guess?! Even with newer X server (x.org)? > > I never disabled it. Here X freezes (Sysrq-b works) with DRI enabled (debian sid, x4.3.0.1, kernel 2.6.11-rc3-mm2, radeon, drm as modules) > I used to unload modules, shutdown network interfaces etc. until I > tried without all that stuff and it still worked. So I concluded YOu are right. I only have to stop the mysql server and everything is working. Thanks. Only one thing (maybe covered somewhere else): After resuming (without having stopped the usb system) my external mouse (USB) stopped working. Is there a way to reactive the external mouse? > I'll prepare a web page with detailed S3/S4 suspend/resume > information for ATI graphics card owners including step-by-step > howtos for smooth suspend/resume cycles. Great idea! I was really searching for something like this. I will check as soon as you have something online wether I have to add something! Best wishes Norbert --- Norbert Preining Università di Siena sip:[EMAIL PROTECTED] +43 (0) 59966-690018 gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- CORRIEVORRIE (n.) Corridor etiquette demands that one a corriedoo (q.v.) has been declared, corrievorrie must be employed. Both protagonists must now embellish their approach with an embarrassing combination of waving, grinning, making idiot faces, doing pirate impressions, and waggling the head from side to side while holding the other person's eyes as the smile drips off their face, until with great relief, they pass each other. --- Douglas Adams, The Meaning of Liff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
On Tue, Feb 15, 2005 at 06:08:37PM +0100, Norbert Preining wrote: > On Die, 15 Feb 2005, Carl-Daniel Hailfinger wrote: > > To suspend and resume properly, call the following script as root: > > Success. > I tried with my Sony Vaio FX701. No luck. It goes S3 ok, but it will never come back (blank screen, HDD led fixed on). I am wishing to help, imply tell me what I have to do. Romano -- Romano Giannetti - Univ. Pontificia Comillas (Madrid, Spain) Electronic Engineer - phone +34 915 422 800 ext 2416 fax +34 915 596 569 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
> The problems with this patch are: > - you need to press a key to come back from the "resume-console" after > resume. - DRI in X does not work (at least for me with intel-agp, others > reportet it works) > I just disabloed it by not loading intel-agp (hotplug-blacklist) You can force the radeon X driver to use pci mode by setting Option "ForcePciMode" to "true" or something simmilar in you X config file. This way you can get dri without intel-agp. This is much slower, but enought to play tuxracer ;-) Stefan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
On Wed, Feb 16, 2005 at 01:47:04PM +1100, Nigel Cunningham wrote: > Hi. > > On Wed, 2005-02-16 at 12:54, Pavel Machek wrote: > > > Also, is USB suspend/resume supposed to work? My brief trials involved > > > modprobing the USB HCD modules, which still allowed me to suspend/resume, > > > but > > > my USB mouse was non-functional on resume. > > > > Yes, it seems to work quite okay. You may need to unplug/replug > > devices after resume, but it should be basically ok. > > We still have plenty of people for whom the best option is to build as > modules, unload prior to suspending and reload afterwards. It seems to > depend on what type your controller is: I do this for uhci_hcd and get > fully functional usb post resume (-rc4). > I have no problem for USB "stateless" devices. The real problem is when you do a suspend/resume cycle with a *mounted* usb stick or disk. Upon resume, the device is found and associated with a diffent block device than before, and the previous mount point is stuck forever (well, almost forever). Sometime umount -f works, sometime no, but it is quite irritating that I need to reboot to have the "good old /dev/sda1" which is in the fstab working. Romano -- Romano Giannetti - Univ. Pontificia Comillas (Madrid, Spain) Electronic Engineer - phone +34 915 422 800 ext 2416 fax +34 915 596 569 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Model hack (or "how to do it") -- Acer Aspire 1406LC ole's radeonfb patch I have to turn off dri, and then it works with the radeonfb patch. I use this method because I like the fancy framebuffersplash on booting .. although I do not reboot often when S3 wors ;) You can find the patch here: http://dev.gentoo.org/~marineam/patch-radeonfb-2.6.11-rc2-mm2 or for older kernels: http://dev.gentoo.org/~genstef/files/radeon-s3-resume-2.6.10.patch The problems with this patch are: - you need to press a key to come back from the "resume-console" after resume. - DRI in X does not work (at least for me with intel-agp, others reportet it works) I just disabloed it by not loading intel-agp (hotplug-blacklist) I have not only issues with video not coming back, but I also need to append acpi=noirq to my command-line that I am able to finish resuming and use my devices correctly afterwards. Regards, Stefan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Hi. On Wed, 2005-02-16 at 12:54, Pavel Machek wrote: > > Also, is USB suspend/resume supposed to work? My brief trials involved > > modprobing the USB HCD modules, which still allowed me to suspend/resume, > > but > > my USB mouse was non-functional on resume. > > Yes, it seems to work quite okay. You may need to unplug/replug > devices after resume, but it should be basically ok. We still have plenty of people for whom the best option is to build as modules, unload prior to suspending and reload afterwards. It seems to depend on what type your controller is: I do this for uhci_hcd and get fully functional usb post resume (-rc4). Regards, Nigel -- Nigel Cunningham Software Engineer, Canberra, Australia http://www.cyclades.com Ph: +61 (2) 6292 8028 Mob: +61 (417) 100 574 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Hi! > > I would advise trying to compile a custom kernel from scratch with my > > .config first. > > > > I got S3 working first with a very basic kernel config, but I couldn't > > get it to work with my usual kernel. Assuming it was some feature that > > caused the problem, I started disabling features in the hope of getting > > it to work, but I ended up with two different kernels with seemingly > > irrelevant differences, of which one would succesfully resume and one > > wouldn't. So I started added features to the other kernel, and I never > > found out what caused the problem. > > I took your advice and built your kernel with a few modifications (XFS > instead > of ext, etc.). If I boot the kernel with init=/bin/sh, I can actually > suspend! Thanks! > > I will exhaustively enable and disable drivers tomorrow to figure out which > one is causing suspend to fail when I do a complete boot. Whatever we find is > clearly a bug that should be fixed. > > It is not the framebuffer driver (I always ran without vesafb or radeonfb), > and it is not my ipw2200 or USB drivers. > > Also, is USB suspend/resume supposed to work? My brief trials involved > modprobing the USB HCD modules, which still allowed me to suspend/resume, but > my USB mouse was non-functional on resume. Yes, it seems to work quite okay. You may need to unplug/replug devices after resume, but it should be basically ok. Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
On Tuesday 15 Feb 2005 21:09, Lorenzo Colitti wrote: [snip] > I would advise trying to compile a custom kernel from scratch with my > .config first. > > I got S3 working first with a very basic kernel config, but I couldn't > get it to work with my usual kernel. Assuming it was some feature that > caused the problem, I started disabling features in the hope of getting > it to work, but I ended up with two different kernels with seemingly > irrelevant differences, of which one would succesfully resume and one > wouldn't. So I started added features to the other kernel, and I never > found out what caused the problem. I took your advice and built your kernel with a few modifications (XFS instead of ext, etc.). If I boot the kernel with init=/bin/sh, I can actually suspend! Thanks! I will exhaustively enable and disable drivers tomorrow to figure out which one is causing suspend to fail when I do a complete boot. Whatever we find is clearly a bug that should be fixed. It is not the framebuffer driver (I always ran without vesafb or radeonfb), and it is not my ipw2200 or USB drivers. Also, is USB suspend/resume supposed to work? My brief trials involved modprobing the USB HCD modules, which still allowed me to suspend/resume, but my USB mouse was non-functional on resume. -- Cheers, Alistair. personal: alistair()devzero!co!uk university: s0348365()sms!ed!ac!uk student:CS/CSim Undergraduate contact:1F2 55 South Clerk Street, Edinburgh. EH8 9PP. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Matthew Garrett schrieb: > On Tue, 2005-02-15 at 19:57 +0100, Carl-Daniel Hailfinger wrote: > > >>Kendall Bennett is working with me to get suspend/resume working >>even with framebuffers. Once we have results, I'll post them here. > > > I've had success using vesafb with vbetool state restoration. vga16fb > ought to work fairly happily. Well, in my testing the machine deadlocked if any framebuffer was active during resume. It even deadlocked *before* I could run vbetool. Regards, Carl-Daniel -- http://www.hailfinger.org/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Hi, On Mon, 2005-02-14 at 22:11 +0100, Pavel Machek wrote: > Stefan provided me initial list of machines where S3 works (including > video). If you have machine that is not on the list, please send me a > diff. If you have eMachines... I'd like you to try playing with > vbetool (it worked for me), and if it works for you supplying right > model numbers. I have S3 working with 2.6.11-rc4 here: Model hack (or "how to do it") -- IBM TP X31 / Type 2672-XXH LCD backlight must be turned off manually using radeontool [1] Sincerely, Brix [1]: http://fdd.com/software/radeon/ -- Henrik Brix Andersen <[EMAIL PROTECTED]> Gentoo Linux signature.asc Description: This is a digitally signed message part
Re: [ACPI] Re: Call for help: list of machines with working S3
Matthew Garrett wrote: Vendor: Hewlett-Packard - Version: 68BDD Ver. F.0F - Release Date: 07/23/2004 + Version: 68BDD Ver. F.11 + Release Date: 11/22/2004 Ok, so you both have different BIOS versions and different CPUs. S3 works for me with both BIOS F.0F, which I was using before, and F.11, which I flashed today after learning it existed. Everything else looks pretty identical. Could you both stick /proc/acpi/dsdt up somewhere so I can check if there are any relevant looking differences? I would advise trying to compile a custom kernel from scratch with my .config first. I got S3 working first with a very basic kernel config, but I couldn't get it to work with my usual kernel. Assuming it was some feature that caused the problem, I started disabling features in the hope of getting it to work, but I ended up with two different kernels with seemingly irrelevant differences, of which one would succesfully resume and one wouldn't. So I started added features to the other kernel, and I never found out what caused the problem. I'm not saying that this is not deterministic, but I am saying that, at least in my case, it's not obvious what it is that stops S3 from working. :-) Cheers, Lorenzo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
On Tue, 2005-02-15 at 17:42 +, Alistair John Strachan wrote: > Vendor: Hewlett-Packard > - Version: 68BDD Ver. F.0F > - Release Date: 07/23/2004 > + Version: 68BDD Ver. F.11 > + Release Date: 11/22/2004 Ok, so you both have different BIOS versions and different CPUs. Everything else looks pretty identical. Could you both stick /proc/acpi/dsdt up somewhere so I can check if there are any relevant looking differences? Thanks, -- Matthew Garrett | [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
On Tue, 2005-02-15 at 19:57 +0100, Carl-Daniel Hailfinger wrote: > Kendall Bennett is working with me to get suspend/resume working > even with framebuffers. Once we have results, I'll post them here. I've had success using vesafb with vbetool state restoration. vga16fb ought to work fairly happily. -- Matthew Garrett | [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Hi! > - Sometimes I have to make a Sysrq-s (sync) to get some stuff running > (eg logging in from the console hangs after input of passwd, calling > sysrq-s makes it continue). I had a similar effect when logging in > AFTER resuming (for the resume I had only gdm running but wasn't > logged in) the GNOME starting screen stayed there indefinitely, no > change. Even after restarting the X server and retrying. > Logging in with twm session DID work without any problem. > Do you have any idea what this could be? Does it happen with swsusp? Is it in any way reproducible? Maybe commenting out refrigerator would help Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Am Dienstag, 15. Februar 2005 18:08 schrieb Norbert Preining: > On Die, 15 Feb 2005, Carl-Daniel Hailfinger wrote: > > To suspend and resume properly, call the following script as root: > > Success. > > After deactivating DRI in the X config file and saving the states with > your script (thanks) and turning off various stuff I get X running > again. > > Questions: > - DRI must be disabled I guess?! Even with newer X server (x.org)? Do you use the fglrx driver? This doesn't work with any type of suspend so far. If you use the radeon driver try a driver update. Stefan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Norbert Preining schrieb: > On Die, 15 Feb 2005, Carl-Daniel Hailfinger wrote: > >>To suspend and resume properly, call the following script as root: > > > Success. Great! > After deactivating DRI in the X config file and saving the states with > your script (thanks) and turning off various stuff I get X running > again. > > Questions: > - DRI must be disabled I guess?! Even with newer X server (x.org)? I never disabled it. > - I dont have to restore the font, it is back without any problem > (I have vga console) Good. I guess that's highly chipset-specific. > - Sometimes I have to make a Sysrq-s (sync) to get some stuff running > (eg logging in from the console hangs after input of passwd, calling > sysrq-s makes it continue). I had a similar effect when logging in > AFTER resuming (for the resume I had only gdm running but wasn't > logged in) the GNOME starting screen stayed there indefinitely, no > change. Even after restarting the X server and retrying. > Logging in with twm session DID work without any problem. > Do you have any idea what this could be? Pavel? > - My script is a bit more complicated: stopping: hotplug, mysql, > ifplugd, waproamd, cpufreqd, acpid, ifdown eth0, eth1, rmmod acerhk > echo "performance" onto governor, then going to sleepand doing > more or less the reverse stuff after waking up. > DO you have any experience with hotplug network etc stuff, working > even without stopping? I used to unload modules, shutdown network interfaces etc. until I tried without all that stuff and it still worked. So I concluded that stopping things before suspend was a thing only needed with older kernels. Granted, mounted volumes on USB or IEEE1394 still have problems because the kernel doesn't expect them to disappear for a few moments, but that's nothing a module unload would fix. Simply umount all external drives and use my script. Drivers which still need to be unloaded and reloaded are buggy and have to be fixed. I'll prepare a web page with detailed S3/S4 suspend/resume information for ATI graphics card owners including step-by-step howtos for smooth suspend/resume cycles. Kendall Bennett is working with me to get suspend/resume working even with framebuffers. Once we have results, I'll post them here. Regards, Carl-Daniel -- http://www.hailfinger.org/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
On Tuesday 15 Feb 2005 16:16, Lorenzo Colitti wrote: [snip] > > Ok, here is the output from dmidecode (Debian package) and from lspci. I > don't have acpidmp and I don't know where to get it, but if you think > it's necessary I can download it if you tell me where to find it. Find below a diff of my dmidecode output versus Lorenzo's. Nothing much to call home about. [alistair] 17:40 [~/dmidecode-2.5] diff -Nudr -U3 lorenzo dmiout --- lorenzo 2005-02-15 17:37:36.091770768 + +++ dmiout 2005-02-15 17:40:08.801555352 + @@ -1,13 +1,13 @@ # dmidecode 2.5 SMBIOS 2.3 present. 31 structures occupying 1354 bytes. -Table at 0x000FF2EB. +Table at 0x000FA1EE. Handle 0x DMI type 0, 20 bytes. BIOS Information Vendor: Hewlett-Packard - Version: 68BDD Ver. F.0F - Release Date: 07/23/2004 + Version: 68BDD Ver. F.11 + Release Date: 11/22/2004 Address: 0xE Runtime Size: 128 kB ROM Size: 1024 kB @@ -37,10 +37,10 @@ DMI type 1, 25 bytes. System Information Manufacturer: Hewlett-Packard - Product Name: HP Compaq nc6000 (DJ254A#ABB) - Version: F.0F - Serial Number: XX - UUID: ---- + Product Name: HP Compaq nc6000 (PK522PS#UUF) + Version: F.11 + Serial Number: + UUID: Wake-up Type: Power Switch Handle 0x0002 DMI type 2, 8 bytes. @@ -52,11 +52,11 @@ Handle 0x0003 DMI type 3, 13 bytes. Chassis Information - Manufacturer: Hewlett-Packard + Manufacturer: Hewlett-Packard Type: Notebook Lock: Not Present Version: Not Specified - Serial Number: XX + Serial Number: Asset Tag: Boot-up State: Safe Power Supply State: Safe @@ -69,8 +69,8 @@ Type: Central Processor Family: Pentium M Manufacturer: Intel(R) - ID: XX XX XX XX XX XX XX XX - Signature: Type 0, Family 6, Model 9, Stepping 5 + ID: D6 06 00 00 BF F9 E9 AF + Signature: Type 0, Family 6, Model 13, Stepping 6 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) @@ -93,13 +93,14 @@ FXSR (Fast floating-point save and restore) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) + SS (Self-snoop) TM (Thermal monitor supported) SBF (Signal break on FERR) - Version: Intel(R) Pentium(R) M processor 1400MHz + Version: Intel(R) Pentium(R) M processor 1.60GHz Voltage: 1.8 V External Clock: 100 MHz - Max Speed: 1400 MHz - Current Speed: 1400 MHz + Max Speed: 1600 MHz + Current Speed: 1600 MHz Status: Populated, Enabled Upgrade: None L1 Cache Handle: 0x0005 @@ -131,8 +132,8 @@ Configuration: Enabled, Not Socketed, Level 2 Operational Mode: Write Back Location: External - Installed Size: 1024 KB - Maximum Size: 1024 KB + Installed Size: 2048 KB + Maximum Size: 2048 KB Supported SRAM Types: Burst Installed SRAM Type: Burst @@ -194,7 +195,7 @@ Form Factor: SODIMM Set: None Locator: DIMM #1 - Bank Locator: 030B2C25 + Bank Locator: 6605F934 Type: DDR Type Detail: Synchronous Speed: 142 MHz (7.0 ns) @@ -213,12 +214,12 @@ Form Factor: SODIMM Set: None Locator: DIMM #2 - Bank Locator: 051FD180 + Bank Locator: 0322BB20 Type: DDR Type Detail: Synchronous Speed: 142 MHz (7.0 ns) Manufacturer: Not Specified - Serial Number: -X + Serial Number: Asset Tag: Not Specified Part Number: Not Specified Handle 0x000E @@ -294,8 +295,8 @@ Portable Battery Location: Primary Manufacturer: Hewlett-Packard - Manufacture Date: 12/12/2003 - Serial Number: 1 + Manufacture Date: 08/20/2004 + Serial Number: 01726 Name: Not Specified Chemistry: Lithium Ion
Re: [ACPI] Call for help: list of machines with working S3
On Die, 15 Feb 2005, Carl-Daniel Hailfinger wrote: > To suspend and resume properly, call the following script as root: Success. After deactivating DRI in the X config file and saving the states with your script (thanks) and turning off various stuff I get X running again. Questions: - DRI must be disabled I guess?! Even with newer X server (x.org)? - I dont have to restore the font, it is back without any problem (I have vga console) - Sometimes I have to make a Sysrq-s (sync) to get some stuff running (eg logging in from the console hangs after input of passwd, calling sysrq-s makes it continue). I had a similar effect when logging in AFTER resuming (for the resume I had only gdm running but wasn't logged in) the GNOME starting screen stayed there indefinitely, no change. Even after restarting the X server and retrying. Logging in with twm session DID work without any problem. Do you have any idea what this could be? - My script is a bit more complicated: stopping: hotplug, mysql, ifplugd, waproamd, cpufreqd, acpid, ifdown eth0, eth1, rmmod acerhk echo "performance" onto governor, then going to sleepand doing more or less the reverse stuff after waking up. DO you have any experience with hotplug network etc stuff, working even without stopping? Thanks a lot. Best wishes Norbert --- Norbert Preining Università di Siena sip:[EMAIL PROTECTED] +43 (0) 59966-690018 gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- CROMARTY (n.) The brittle sludge which clings to the top of ketchup bottles and plastic tomatoes in nasty cafes. --- Douglas Adams, The Meaning of Liff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Pavel Machek wrote: > > Table of known working systems: > > Model hack (or "how to do it") > -- > IBM TP R32 / Type 2658-MMG none (1) IBM TP T40 / Type 2373-MU4 none (1) IBM TP R50p / Type 1832-22U s3_bios (2) > Athlon HP Omnibook XE3none (1) > Compaq Armada E500 - P3-700 none (1) (S1 also works OK) > IBM t41p none (1) --Vernon - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Matthew Garrett wrote: I beg to differ: it works for me on 2.6.11-rc3 (even with the swsusp2 patch). However, I need to use acpi_sleep=s3_bios, and I can't use radeonfb or it will lock up on resume. Could you grab dmidecode from http://www.nongnu.org/dmidecode/ and provide the output? It'd be interesting to compare working with non-working machines. It might also be good to see lspci and acpidmp output. Ok, here is the output from dmidecode (Debian package) and from lspci. I don't have acpidmp and I don't know where to get it, but if you think it's necessary I can download it if you tell me where to find it. Cheers, Lorenzo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Matthew Garrett wrote: I beg to differ: it works for me on 2.6.11-rc3 (even with the swsusp2 patch). However, I need to use acpi_sleep=s3_bios, and I can't use radeonfb or it will lock up on resume. Could you grab dmidecode from http://www.nongnu.org/dmidecode/ and provide the output? It'd be interesting to compare working with non-working machines. It might also be good to see lspci and acpidmp output. Ok, here is the output from dmidecode (Debian package) and from lspci. I don't have acpidmp and I don't know where to get it, but if you think it's necessary I can download it if you tell me where to find it. Cheers, Lorenzo # dmidecode 2.5 SMBIOS 2.3 present. 31 structures occupying 1354 bytes. Table at 0x000FF2EB. Handle 0x DMI type 0, 20 bytes. BIOS Information Vendor: Hewlett-Packard Version: 68BDD Ver. F.0F Release Date: 07/23/2004 Address: 0xE Runtime Size: 128 kB ROM Size: 1024 kB Characteristics: PCI is supported PC Card (PCMCIA) is supported PNP is supported APM is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 3.5"/720 KB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported AGP is supported LS-120 boot is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Handle 0x0001 DMI type 1, 25 bytes. System Information Manufacturer: Hewlett-Packard Product Name: HP Compaq nc6000 (DJ254A#ABB) Version: F.0F Serial Number: XX UUID: ---- Wake-up Type: Power Switch Handle 0x0002 DMI type 2, 8 bytes. Base Board Information Manufacturer: Hewlett-Packard Product Name: 0890 Version: 8051 Version 1A.19 Serial Number: Not Specified Handle 0x0003 DMI type 3, 13 bytes. Chassis Information Manufacturer: Hewlett-Packard Type: Notebook Lock: Not Present Version: Not Specified Serial Number: XX Asset Tag: Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: External Interface Enabled Handle 0x0004 DMI type 4, 35 bytes. Processor Information Socket Designation: U10 Type: Central Processor Family: Pentium M Manufacturer: Intel(R) ID: XX XX XX XX XX XX XX XX Signature: Type 0, Family 6, Model 9, Stepping 5 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (Fast floating-point save and restore) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) TM (Thermal monitor supported) SBF (Signal break on FERR) Version: Intel(R) Pentium(R) M processor 1400MHz
Re: [ACPI] Call for help: list of machines with working S3
Norbert Preining schrieb: > On Mon, 14 Feb 2005, Pavel Machek wrote: > >>(1) systems where video state is preserved over S3. >> >>(2) systems where it is possible to call video bios during S3 >> resume. Unfortunately, it is not correct to call video BIOS at that >> point, but it happens to work on some machines. Use >> acpi_sleep=s3_bios. >> >>(3) systems that initialize video card into vga text mode and where BIOS >> works well enough to be able to set video mode. Use >> acpi_sleep=s3_mode on these. >> >>(4) on some systems s3_bios kicks video into text mode, and >> acpi_sleep=s3_bios,s3_mode is needed. >> >>(5) radeon systems, where X can soft-boot your video card. You'll need >> patched X, and plain text console (no vesafb or radeonfb), see >> http://www.doesi.gmxhome.de/linux/tm800s3/s3.html. >> >>(6) other radeon systems, where vbetool is enough to bring system back >> to life. Do vbetool vbestate save > /tmp/delme; echo 3 > /proc/acpi/sleep; >> vbetool post; vbetool vbestate restore < /tmp/delme; setfont >> , and your video should work. >> >>Acer TM 800 vga=normal, X patches, see webpage (5) > > > > Acer TM 650 (Radeon M7) > > vga=normal plus boot-radeon (webpage(5)) works to get text console > back. But switching to X freezes the computer completely. Please try method (6). It should work perfectly because it is the successor for method (5) and works even without special patches for X. > X from debian sid. > XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-10 20041215174925 [EMAIL > PROTECTED]) > Release Date: 15 August 2003 > X Protocol Version 11, Revision 0, Release 6.6 > Build Operating System: Linux 2.4.26 i686 [ELF] > Build Date: 15 December 2004 > > > I would like to get X running to, but there are no traces in the logfile > whatsoever to be seen. Pity. First, boot into X and run the following script ONCE: #!/bin/bash statedir=/root/s3/state mkdir -p $statedir chvt 2 sleep 1 vbetool vbestate save >$statedir/vbe To suspend and resume properly, call the following script as root: #!/bin/bash statedir=/root/s3/state curcons=`fgconsole` fuser /dev/tty$curcons 2>/dev/null|xargs ps -o comm= -p|grep -q X && chvt 2 cat /dev/vcsa >$statedir/vcsa sync echo 3 >/proc/acpi/sleep sync vbetool post vbetool vbestate restore <$statedir/vbe cat $statedir/vcsa >/dev/vcsa rckbd restart chvt $[curcons%6+1] chvt $curcons Unless you change your grahics card or other hardware configuration, the state once saved will be OK for every resume afterwards. NOTE: The "rckbd restart" command may be different for your distribution. Simply replace it with the command you would use to set the fonts on screen. > So it seems that my laptop does not fall in any of these categories. Please try my scripts and resport back. Regards, Carl-Daniel -- http://www.hailfinger.org/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Alistair John Strachan wrote: .config attached. As recommended elsewhere in this thread, I'm not using any sort of framebuffer driver, but vesafb IS compiled in (but no vga= option is present). Does it need to be compiled out completely? I don't remember, maybe you can deduce it from the .config I sent? I have acpi_sleep=s3_bios on cmdline. I am not using swsusp2 (and I can't see how this is at all related to software suspend). It works with or without swsusp2. Perhaps it is the machine BIOS. Which version do you have? I think it's vF.0F from July 2004. Cheers, Lorenzo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Call for help: list of machines with working S3
Alistair John Strachan wrote: > On Monday 14 Feb 2005 21:11, Pavel Machek wrote: > [snip] >>Table of known working systems: >> >>Model hack (or "how to do it") >>--- >>--- IBM TP R32 / Type 2658-MMG none (1) >>Athlon HP Omnibook XE3none (1) >>Compaq Armada E500 - P3-700 none (1) (S1 also works OK) >>IBM t41p none (1) >>Athlon64 desktop prototypes3_bios (2) >>HP NC6000 s3_bios (2) > > The above report is incorrect. On 2.6.11-rc4, even with the s3_bios option, > the NC6000 (which I own) still does not wake up from S3 sleep. The wiki > linked somewhere else in this thread also identifies these machines as not > working. I just retried it with a nc6000, it worked with "vga=normal acpi_sleep=s3_bios rw init=/bin/bash". It did not work from a full blown system including X etc, but this is probably a driver problem, the machine was sitting in a docking station which connects everything via USB. Sorry, right now i cannot debug this further, but it basically works and should not be too hard to get going. Also, it does not work with vesafb (I have not tried radeonfb) -- Stefan Seyfried, QA / R&D Team Mobile Devices, SUSE LINUX Nürnberg. "Any ideas, John?" "Well, surrounding them's out." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
On Tue, 2005-02-15 at 13:12 +0100, Lorenzo Colitti wrote: > I beg to differ: it works for me on 2.6.11-rc3 (even with the swsusp2 > patch). However, I need to use acpi_sleep=s3_bios, and I can't use > radeonfb or it will lock up on resume. Could you grab dmidecode from http://www.nongnu.org/dmidecode/ and provide the output? It'd be interesting to compare working with non-working machines. It might also be good to see lspci and acpidmp output. -- Matthew Garrett | [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
On Tuesday 15 Feb 2005 12:12, Lorenzo Colitti wrote: > Alistair John Strachan wrote: > > On Monday 14 Feb 2005 21:11, Pavel Machek wrote: > >>Table of known working systems: > >>Model hack (or "how to do it") > >>[...] > >>HP NC6000 s3_bios (2) > > > > The above report is incorrect. On 2.6.11-rc4, even with the s3_bios > > option, the NC6000 (which I own) still does not wake up from S3 sleep. > > The wiki linked somewhere else in this thread also identifies these > > machines as not working. > > I beg to differ: it works for me on 2.6.11-rc3 (even with the swsusp2 > patch). However, I need to use acpi_sleep=s3_bios, and I can't use > radeonfb or it will lock up on resume. > > .config attached. > As recommended elsewhere in this thread, I'm not using any sort of framebuffer driver, but vesafb IS compiled in (but no vga= option is present). Does it need to be compiled out completely? I have acpi_sleep=s3_bios on cmdline. I am not using swsusp2 (and I can't see how this is at all related to software suspend). Perhaps it is the machine BIOS. Which version do you have? -- Cheers, Alistair. personal: alistair()devzero!co!uk university: s0348365()sms!ed!ac!uk student:CS/CSim Undergraduate contact:1F2 55 South Clerk Street, Edinburgh. EH8 9PP. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Thus wrote Norbert Preining: > vga=normal plus boot-radeon (webpage(5)) works to get text console > back. But switching to X freezes the computer completely. > > X from debian sid. > XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-10 20041215174925 [EMAIL > PROTECTED]) > Release Date: 15 August 2003 Get a recent X version, 4.4, 6.7.0 or 6.8.2 will do. Alternatively, disable DRI. Best regards, -- Karol 'sziwan' Kozimor [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
On Mon, 14 Feb 2005, Pavel Machek wrote: > (1) systems where video state is preserved over S3. > > (2) systems where it is possible to call video bios during S3 > resume. Unfortunately, it is not correct to call video BIOS at that > point, but it happens to work on some machines. Use > acpi_sleep=s3_bios. > > (3) systems that initialize video card into vga text mode and where BIOS > works well enough to be able to set video mode. Use > acpi_sleep=s3_mode on these. > > (4) on some systems s3_bios kicks video into text mode, and > acpi_sleep=s3_bios,s3_mode is needed. > > (5) radeon systems, where X can soft-boot your video card. You'll need > patched X, and plain text console (no vesafb or radeonfb), see > http://www.doesi.gmxhome.de/linux/tm800s3/s3.html. > > (6) other radeon systems, where vbetool is enough to bring system back > to life. Do vbetool vbestate save > /tmp/delme; echo 3 > /proc/acpi/sleep; > vbetool post; vbetool vbestate restore < /tmp/delme; setfont > , and your video should work. > > Acer TM 800 vga=normal, X patches, see webpage (5) Acer TM 650 (Radeon M7) vga=normal plus boot-radeon (webpage(5)) works to get text console back. But switching to X freezes the computer completely. X from debian sid. XFree86 Version 4.3.0.1 (Debian 4.3.0.dfsg.1-10 20041215174925 [EMAIL PROTECTED]) Release Date: 15 August 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.26 i686 [ELF] Build Date: 15 December 2004 I would like to get X running to, but there are no traces in the logfile whatsoever to be seen. Pity. So it seems that my laptop does not fall in any of these categories. Best wishes Norbert --- Norbert Preining Università di Siena sip:[EMAIL PROTECTED] +43 (0) 59966-690018 gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- PELUTHO (n.) A South American ball game. The balls are whacked against a brick wall with a stout wooden bat until the prisoner confesses. --- Douglas Adams, The Meaning of Liff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Re: Call for help: list of machines with working S3
Alistair John Strachan wrote: On Monday 14 Feb 2005 21:11, Pavel Machek wrote: Table of known working systems: Model hack (or "how to do it") [...] HP NC6000 s3_bios (2) The above report is incorrect. On 2.6.11-rc4, even with the s3_bios option, the NC6000 (which I own) still does not wake up from S3 sleep. The wiki linked somewhere else in this thread also identifies these machines as not working. I beg to differ: it works for me on 2.6.11-rc3 (even with the swsusp2 patch). However, I need to use acpi_sleep=s3_bios, and I can't use radeonfb or it will lock up on resume. .config attached. Cheers, Lorenzo # # Automatically generated make config: don't edit # Linux kernel version: 2.6.11-rc3-vanilla+swsusp # Thu Feb 10 15:44:07 2005 # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y # # General setup # CONFIG_LOCALVERSION="" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_LOG_BUF_SHIFT=14 CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_FUTEX=y CONFIG_EPOLL=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_OBSOLETE_MODPARM=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set CONFIG_MPENTIUMM=y # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_HPET_TIMER=y # CONFIG_SMP is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y # CONFIG_X86_UP_APIC is not set CONFIG_X86_TSC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_NONFATAL=y # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set CONFIG_MICROCODE=m CONFIG_X86_MSR=m CONFIG_X86_CPUID=m # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_EFI is not set CONFIG_HAVE_DEC_LOCK=y # CONFIG_REGPARM is not set # # NeTraverse Win4Lin Support # # CONFIG_MKI is not set # # Power management options (ACPI, APM) # CONFIG_PM=y CONFIG_PM_DEBUG=y # CONFIG_SOFTWARE_SUSPEND is not set # # Software Suspend 2 # CONFIG_SOFTWARE_SUSPEND2=y CONFIG_SOFTWARE_SUSPEND2_BUILTIN=y # # Image Storage (you need at least one writer) # CONFIG_SOFTWARE_SUSPEND_SWAPWRITER=y # # Page Transformers # CONFIG_SOFTWARE_SUSPEND_LZF_COMPRESSION=y # # User Interface Options # CONFIG_SOFTWARE_SUSPEND_TEXT_MODE=y # # General Options # CONFIG_SOFTWARE_SUSPEND_DEFAULT_RESUME2="/dev/hda7" # CONFIG_SOFTWARE_SUSPEND_KEEP_IMAGE is not set # CONFIG_SOFTWARE_SUSPEND_CHECK_RESUME_SAFE is not set # # Debugging # CONFIG_SOFTWARE_SUSPEND_DEBUG=y # CONFIG_SOFTWARE_SUSPEND_DEVELOPER is not set # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_SLEEP_PROC_FS=y CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m CONFIG_ACPI_BUTTON=m CONFIG_ACPI_VIDEO=m CONFIG_ACPI_FAN=m CONFIG_ACPI_PROCESSOR=m CONFIG_ACPI_THERMAL=m # CONFIG_ACPI_ASUS is not set # CONFIG_ACPI_IBM is not set # CONFIG_ACPI_TOSHIBA is not set CONFIG_ACPI_BLACKLIST_YEAR=0 CONFIG_ACPI_DEBUG=y CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y CONFIG_X86_PM_TIMER=y # CONFIG_ACPI_CONTAINER is not set # # APM (Advanced Power Management) BIO
Re: Call for help: list of machines with working S3
On Monday 14 Feb 2005 21:11, Pavel Machek wrote: [snip] > > Table of known working systems: > > Model hack (or "how to do it") > --- >--- IBM TP R32 / Type 2658-MMG none (1) > Athlon HP Omnibook XE3none (1) > Compaq Armada E500 - P3-700 none (1) (S1 also works OK) > IBM t41p none (1) > Athlon64 desktop prototypes3_bios (2) > HP NC6000 s3_bios (2) The above report is incorrect. On 2.6.11-rc4, even with the s3_bios option, the NC6000 (which I own) still does not wake up from S3 sleep. The wiki linked somewhere else in this thread also identifies these machines as not working. > Toshiba Satellite 4080XCDT s3_mode (3) > Toshiba Satellite 4030CDT s3_mode (3) > Dell D600, ATI RV250vga=normal (**) > Asus L2400D s3_mode (3)(***) (S1 also works OK) > Toshiba Satellite P10-554 s3_bios,s3_mode (4)() > Acer TM 800 vga=normal, X patches, see webpage (5) > Athlon64 Arima W730a vbestate needed (6) > eMachines athlon64 machines vbestate needed (6) (someone please get me > model #s) > > (**) Text console is "strange" after resume. Backlight is switched on again > > by the X server. X server is: > | X Window System Version 6.8.1.904 (6.8.2 RC 4) > | Release Date: 2 February 2005 > | X Protocol Version 11, Revision 0, Release 6.8.1.904 > | Build Operating System: SuSE Linux [ELF] SuSE > > as present in SUSE 9.3preview3. > > (***) To be tested with a newer kernel. > > () Not with SMP kernel, UP only. -- Cheers, Alistair. personal: alistair()devzero!co!uk university: s0348365()sms!ed!ac!uk student:CS/CSim Undergraduate contact:1F2 55 South Clerk Street, Edinburgh. EH8 9PP. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
On Mon, 2005-02-14 at 23:23 +, Matthew Garrett wrote: > On Mon, 2005-02-14 at 22:11 +0100, Pavel Machek wrote: > > Hi! > > > > Stefan provided me initial list of machines where S3 works (including > > video). If you have machine that is not on the list, please send me a > > diff. If you have eMachines... I'd like you to try playing with > > vbetool (it worked for me), and if it works for you supplying right > > model numbers. > > http://www.ubuntulinux.org/wiki/HoaryPMTesting has a list of several > working machines. HP seem to be the worst supported at the moment. Sorry - that should be http://www.ubuntulinux.org/wiki/HoaryPMResults -- Matthew Garrett | [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
On Mon, 2005-02-14 at 22:11 +0100, Pavel Machek wrote: > Hi! > > Stefan provided me initial list of machines where S3 works (including > video). If you have machine that is not on the list, please send me a > diff. If you have eMachines... I'd like you to try playing with > vbetool (it worked for me), and if it works for you supplying right > model numbers. http://www.ubuntulinux.org/wiki/HoaryPMTesting has a list of several working machines. HP seem to be the worst supported at the moment. -- Matthew Garrett | [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [ACPI] Call for help: list of machines with working S3
Pavel Machek schrieb: > Hi! > > Stefan provided me initial list of machines where S3 works (including > video). If you have machine that is not on the list, please send me a > diff. If you have eMachines... I'd like you to try playing with > vbetool (it worked for me), and if it works for you supplying right > model numbers. > > Pavel > > > Video issues with S3 resume > ~~~ > 2003-2005, Pavel Machek > > During S3 resume, hardware needs to be reinitialized. For most > devices, this is easy, and kernel driver knows how to do > it. Unfortunately there's one exception: video card. Those are usually > initialized by BIOS, and kernel does not have enough information to > boot video card. (Kernel usually does not even contain video card > driver -- vesafb and vgacon are widely used). > > This is not problem for swsusp, because during swsusp resume, BIOS is > run normally so video card is normally initialized. S3 has absolutely > no change to work with SMP/HT. Be sure it to turn it off before > testing (swsusp should work ok, OTOH). > > There are few types of systems where video works after S3 resume: > > (1) systems where video state is preserved over S3. > > (2) systems where it is possible to call video bios during S3 > resume. Unfortunately, it is not correct to call video BIOS at that > point, but it happens to work on some machines. Use > acpi_sleep=s3_bios. > > (3) systems that initialize video card into vga text mode and where BIOS > works well enough to be able to set video mode. Use > acpi_sleep=s3_mode on these. > > (4) on some systems s3_bios kicks video into text mode, and > acpi_sleep=s3_bios,s3_mode is needed. > > (5) radeon systems, where X can soft-boot your video card. You'll need > patched X, and plain text console (no vesafb or radeonfb), see > http://www.doesi.gmxhome.de/linux/tm800s3/s3.html. (5) machines should also work with (6), but not the other way round. > > (6) other radeon systems, where vbetool is enough to bring system back > to life. Do vbetool vbestate save > /tmp/delme; echo 3 > /proc/acpi/sleep; > vbetool post; vbetool vbestate restore < /tmp/delme; setfont > , and your video should work. (6) has to be done from a text console! It should work for all radeon systems, btw. > > Now, if you pass acpi_sleep=something, and it does not work with your > bios, you'll get hard crash during resume. Be carefull. Also it is > safest to do your experiments with plain old VGA console. vesafb and > radeonfb (etc) drivers have tendency to crash the machine during resume. > > You may have system where none of above works. At that point you > either invent another ugly hack that works, or write proper driver for > your video card (good luck getting docs :-(). Maybe suspending from X > (proper X, knowing your hardware, not XF68_FBcon) might have better > chance of working. > > Table of known working systems: > > Model hack (or "how to do it") > -- > IBM TP R32 / Type 2658-MMG none (1) > Athlon HP Omnibook XE3none (1) > Compaq Armada E500 - P3-700 none (1) (S1 also works OK) > IBM t41p none (1) > Athlon64 desktop prototypes3_bios (2) > HP NC6000 s3_bios (2) > Toshiba Satellite 4080XCDT s3_mode (3) > Toshiba Satellite 4030CDT s3_mode (3) > Dell D600, ATI RV250vga=normal (**) The Dell system above should also work fine with vbestate. > Asus L2400D s3_mode (3)(***) (S1 also works OK) > Toshiba Satellite P10-554 s3_bios,s3_mode (4)() > Acer TM 800 vga=normal, X patches, see webpage (5) > Athlon64 Arima W730a vbestate needed (6) > eMachines athlon64 machines vbestate needed (6) (someone please get me > model #s) Samsung P35 vbestate needed (6) > > (**) Text console is "strange" after resume. Backlight is switched on again > by the X server. X server is: > | X Window System Version 6.8.1.904 (6.8.2 RC 4) > | Release Date: 2 February 2005 > | X Protocol Version 11, Revision 0, Release 6.8.1.904 > | Build Operating System: SuSE Linux [ELF] SuSE > as present in SUSE 9.3preview3. > > (***) To be tested with a newer kernel. > > () Not with SMP kernel, UP only. Regards, Carl-Daniel -- http://www.hailfinger.org/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Call for help: list of machines with working S3
Hi! Stefan provided me initial list of machines where S3 works (including video). If you have machine that is not on the list, please send me a diff. If you have eMachines... I'd like you to try playing with vbetool (it worked for me), and if it works for you supplying right model numbers. Pavel Video issues with S3 resume ~~~ 2003-2005, Pavel Machek During S3 resume, hardware needs to be reinitialized. For most devices, this is easy, and kernel driver knows how to do it. Unfortunately there's one exception: video card. Those are usually initialized by BIOS, and kernel does not have enough information to boot video card. (Kernel usually does not even contain video card driver -- vesafb and vgacon are widely used). This is not problem for swsusp, because during swsusp resume, BIOS is run normally so video card is normally initialized. S3 has absolutely no change to work with SMP/HT. Be sure it to turn it off before testing (swsusp should work ok, OTOH). There are few types of systems where video works after S3 resume: (1) systems where video state is preserved over S3. (2) systems where it is possible to call video bios during S3 resume. Unfortunately, it is not correct to call video BIOS at that point, but it happens to work on some machines. Use acpi_sleep=s3_bios. (3) systems that initialize video card into vga text mode and where BIOS works well enough to be able to set video mode. Use acpi_sleep=s3_mode on these. (4) on some systems s3_bios kicks video into text mode, and acpi_sleep=s3_bios,s3_mode is needed. (5) radeon systems, where X can soft-boot your video card. You'll need patched X, and plain text console (no vesafb or radeonfb), see http://www.doesi.gmxhome.de/linux/tm800s3/s3.html. (6) other radeon systems, where vbetool is enough to bring system back to life. Do vbetool vbestate save > /tmp/delme; echo 3 > /proc/acpi/sleep; vbetool post; vbetool vbestate restore < /tmp/delme; setfont , and your video should work. Now, if you pass acpi_sleep=something, and it does not work with your bios, you'll get hard crash during resume. Be carefull. Also it is safest to do your experiments with plain old VGA console. vesafb and radeonfb (etc) drivers have tendency to crash the machine during resume. You may have system where none of above works. At that point you either invent another ugly hack that works, or write proper driver for your video card (good luck getting docs :-(). Maybe suspending from X (proper X, knowing your hardware, not XF68_FBcon) might have better chance of working. Table of known working systems: Model hack (or "how to do it") -- IBM TP R32 / Type 2658-MMG none (1) Athlon HP Omnibook XE3 none (1) Compaq Armada E500 - P3-700 none (1) (S1 also works OK) IBM t41pnone (1) Athlon64 desktop prototype s3_bios (2) HP NC6000 s3_bios (2) Toshiba Satellite 4080XCDT s3_mode (3) Toshiba Satellite 4030CDT s3_mode (3) Dell D600, ATI RV250vga=normal (**) Asus L2400D s3_mode (3)(***) (S1 also works OK) Toshiba Satellite P10-554 s3_bios,s3_mode (4)() Acer TM 800 vga=normal, X patches, see webpage (5) Athlon64 Arima W730avbestate needed (6) eMachines athlon64 machines vbestate needed (6) (someone please get me model #s) (**) Text console is "strange" after resume. Backlight is switched on again by the X server. X server is: | X Window System Version 6.8.1.904 (6.8.2 RC 4) | Release Date: 2 February 2005 | X Protocol Version 11, Revision 0, Release 6.8.1.904 | Build Operating System: SuSE Linux [ELF] SuSE as present in SUSE 9.3preview3. (***) To be tested with a newer kernel. () Not with SMP kernel, UP only. -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
