Re: ACPI on hp tc1100

Joshua Wise
2004-12-05T21:03:42Z

> regarding the nvidia problem, I would recomend you searching the
> november posts to this list for a thread called "Success with
> kernel-swsusp and Nvidia-closed-source" started by me.
Okay, I read through that.

> Just to repeat two things:
> I was not sucessfull with the latest nvidia driver. I needed to use the
> nvidia agpgart with 'Option "NvAGP" "1"', as with my Acer ali-agp it
> would crash on resume.
Hm. First, I tried just setting Option "NvAGP" "1" in my XF86Config
without downgrading, and that seemed to do the trick! I am running the
latest NVidia drivers: 6629. However, when the system 'comes back to
life', the wireless is non-functional, as described below. The
wacom-acpi driver also seems to need to be reloaded: on resume, dmesg
reports that ttyS4 failed the LSR safety check. If I get a chance, I'll
see if I can't write a patch for that to kill off and reload the serial
on suspend and resume, respectively. (This shouldn't go in
suspend/resume scripts because we need to maintain continuity across a
suspend - X doesn't know how to re-open the device when it gets
unexpectedly closed.)

> If you login through the network and run "top" you would see, that X is
> claiming nearly 100% of CPU-cycles..., that happens, when you switch to
> the virtual-console, where the nvidia-binary-only driver is running (or
> if it is resumed to this console...) and the AGP-bus is not initialised.
Ah. In fact, when this system resumes from suspend, the wireless card
refuses to work. Errors in dmesg:
<system power on>
ipw2100: eth0: ipw2100_verify failed: -5
ipw2100: eth0: Failed to power on the adapter.
ipw2100: eth0: Failed to start the firmware.
Restarting tasks... done
<I try to reload the driver>
ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, 1.0.1
ipw2100: Copyright(c) 2003-2004 Intel Corporation
ACPI: PCI interrupt 0000:02:05.0[A] -> GSI 15 (level, low) -> IRQ 15
ipw2100Device not found via register read.

I will see if removing the driver before bringing the system down helps.

> As you may read often on this list, start with suspend to disk, as it is
> the easiest to get running. Then go for S1 and S3 (the S0 you mentioned
> is S1). Just always think of doing a sync before trying to suspend; then
> fsck has a lot better chances to put things together after a crash.
Yup. Sync before suspend has saved me repeatedly. I actually just got S3
mostly working, as described previously. I will try swsusp in a while to
see if that fixes my ipw2100 problems.

> Cheers
> hartwig felger