ACPI issues with 2.4.17 kernel losing nic

[Abzstrak]

Anyone that can help...

I enabled ACPI inthe 2.4 kernel and now my laptop is happily sleeping (was having issues with apm only), but now when it wakes up the nic is GONE, and I mean gone... I have to completely shut down to get it working again. Anyone have any ideas? This is the first time I've played with the ACPI stuff and I know its experimental, but....

Its a Thinkpad 600E, and the nic is a 3com 374

TIA

 

[Epyon9283]

Same thing happens to my computer in both windows and linux...

 

[LNXman]

I have the same laptop, and that behaviour happens with any O.S. (win98,win2k, or LINUX). After a lot of research, I discovered that I was not the only one having problems waking up my laptop. The problems I encountered were odd power saving behaviour, like going to sleep at random, shutting down devices at random, devices would take ~15mins to wake up, or the LCD going on stand by for no apparent reason. . . . Short lived model from IBM anyways. . .
However, if you mess around with the IBM's bios settings for the laptop with it's software tool, you can diminish the odd power saving behaviour. . . Or, you can use the LINUX version of the tool (tpctl) to see if it can help with some of your issues. . .
In my case, I can watch DVD's with rare uncontrolled interruptions now . . .

Just curious, what do you use to wake up your laptop?

 

[Abzstrak]

Oh, thats quite strange, this is the first power management issue I've had with it, well other than the pure apm kernel not waking up. In win2k and XP it works perfectly, and both are using acpi hals, so I figured maybe compiling acpi in the kernel would help, and it did... except now the nic disappears, even in /proc

 

[Abzstrak]

lnxman,

I use one of two things to wake it up, usually I only put it to sleep/wake up by opening and closing the lid. Sometimes thats annoying though so I disable it and put it in standby with an apm -s and wake it up by hitting the Fn key once.

 

[Abzstrak]

^^^

 

[LNXman]

Heh, I am sorry, I have not paid attention to the forums for a bit. . . I would have thought someone else would have tried to help you by now. . .but here I go.

I noticed that in one of your posts you mention using "apm". That command will work since I am sure you are running ampd, and ampd will be able to tell the kernel through ACPI to suspend the machine (since it is a simple call). However, you are not using the right tools to work with the built-in ACPI in your kernel, and this means some critical information ACPI assumes it will have to wake up the machine, will mostlikely not be exist, because of the wrong tool used. And therefore some peripherals may not wake up because ACPI will not find the information about their status prior to when they were suspended.
You have to install the correct daemon, and use the specific tools to make good use of the current ACPI support for LINUX. Keep in mind that ACPI is NOT well supported yet, and probably wont be for a while due to the complexity used for coding this type of power management.

You can find out about the tools here. Give it a try, and if it works, great! If it does not work, I would default back to APM, cause it currently works for me the best, and problems are almost none existent.


GL

/edit: fixed paragraph, cause it was a bit confusing, since I just woke up. . . hehehehehe

 

[Abzstrak]

cool, thanx... I'll give it a shot.