nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   General Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=27)
-   -   [ACPI][Wake-on-LAN] System won't boot after Power down from Linux (http://www.nvnews.net/vbulletin/showthread.php?t=21578)

sphere 11-27-03 12:12 PM

[ACPI][Wake-on-LAN] System won't boot after Power down from Linux
 
I've installed Debian unstable on my abit nf7-s v2.0. While I was waiting for the packages for X to trickle in, I tried to fix Wake-on-Lan. And it works... once.

If I shutdown from W2K I can ether-wake the box, but when I shutdown from Linux I cannot. I have to power on/off the box (to reset the BIOS maybe :confused: ) and then it will boot again after a call from ether-wake.

The kernel is a 2.4.22 one with ACPI. Does anyone have any pointers on how to get this going after a Power down. from Linux? The only strange thing I can see is that after the "Power down." message appears, two more usb******* messages flash by, but I don't have a clue what they are, it is almost impossible to see and I don't have a videocamera to tape it.

LBJM 12-03-03 07:08 PM

is it a stock debian kernel? if so custom compile the kernel with all the acpi options.

you can read the boot log in /var/log I'm using debian unstable as well.

though I'm using a 2.6 test 11 custom complied kernel

sphere 12-04-03 01:03 AM

Quote:

Originally posted by LBJM
is it a stock debian kernel? if so custom compile the kernel with all the acpi options.

you can read the boot log in /var/log I'm using debian unstable as well.

though I'm using a 2.6 test 11 custom complied kernel

Yep it is. I have a 2.6.0-test11 branch as well, but the behaviour seems to be the same? Are you trying to tell me that wake-on-lan works for you after power down from linux? Are you in the position to test if Wake-on-LAN works for you?

I have failed a bug against this issue btw:
http://bugzilla.kernel.org/show_bug.cgi?id=1636

[offtopic]I built a 2.6.0-test11 kernel with the forcedeth patch, currently reading if it is possible to use my nvidia gfx card with 2.6
[/offtopic]

LBJM 12-05-03 02:00 PM

no I was just trying totell you that with stock kernels they arent setup upfor wake on lan. I could use it but I dont. heres a mini howto I havent checked it though http://gsd.di.uminho.pt/jpo/software...an/mini-howto/

heres the site for patching the nvidia drivers to work with 2.6 http://www.minion.de/ in case you need it.

sphere 12-06-03 04:19 PM

Quote:

Originally posted by LBJM
no I was just trying totell you that with stock kernels they arent setup upfor wake on lan. I could use it but I dont. heres a mini howto I havent checked it though http://gsd.di.uminho.pt/jpo/software...an/mini-howto/

heres the site for patching the nvidia drivers to work with 2.6 http://www.minion.de/ in case you need it.

You've lost me. Do you know of an instance where Wake-on-LAN works after power down from Linux? I've checked the howto and it contained a useful link, but no solution. I'm milking the link for information as we speak.

Nvidia has replied that their driver does not support, but this may change in a "future release."

LBJM 12-08-03 06:46 PM

not with the built on nforce2 nic
I know wake on lan works searches on google show they work with intel cards and 3com 905c. I own the latter I'll do testing after my finals are up after next week


heres a simple question when you power down under windows 2000 .. the nic light stays on after the system is off right.. well is hte light till on after you shutdown under linux..? yes no? well I have the problem of not being able to power up(not with this machine) with older 2.5 and 2.4 kernels because of the way the kernel was doing acpi and the state the bios was set to use acpi( I dont remember the setting). it got resolved when they re wrote the acpi in the kernel. but when I would shut down under linux the wake on lan would turn off. now some boards either have acpi troubles or Apic troubles.. with my nforce2 system that I'm using I have to disable acpi though it might be a pic related the system locks when acpi is enabled even under linux 2.6 test11 I havent looked into it yet.

I'm trying to say the problem might not just be wake on lan related.

have you tried the forcedeth driver right? so is the nic still active after shutdown under linux?
http://www.hailfinger.org/carldani/l...hes/forcedeth/

sphere 12-08-03 07:00 PM

I have tried 2.4.22, 2.4.23 and 2.6.0-test11 with nvidia and forcedeth drivers. The LEDs do stay on. Through your link to the howto I found pci-config.c on http://www.scyld.com/diag/index.html which can set the power state of devices.

I have added a script in /etc/rc0.d to put the nic to D3, and that enables WOL functionality. Unfortunately, this causes the box to hang sometimes, so it's not full-proof, but it seems to work -most- of the time.

It seems the kernel ACPI maintainer has a mobo with nforce2 chipset, so he will be able to do some testing when he gets around to it. Hopefully he can dig up enough information about this issue so that the forcedeth crew can incorporate it into their driver.

In the mean time I am going to look for a failsafe solution, i.e. a network card that will support wake-on-lan. However, this might prove very difficult because I don't think my mobo has pins to attach a WOL cable to :(

sphere 12-11-03 02:31 AM

Wake-on-LAN:
NOTE: This will not work flawlessly with the nvnet driver, use forcedeth instead if you value WOL.
This works with Debian on an Abit NF7-S, but it's probably easy enough to adapt it for your setup.
http://www.scyld.com/diag/index.html
Download ftp://ftp.scyld.com/pub/diag/pci-config.c

NOTE: You have to figure out yourself what device number your nic has:
Example:
#! /bin/shsphere@barton:~/media$ lspci
[SNIP]
00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller (rev a1)
[SNIP]

sphere@barton:~/media$ ./pci-config
pci-config.c:v2.03 4/15/2002 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
[SNIP]
Device #12 at bus 0 device/function 4/0, 006610de.
[SNIP]

sphere@barton:~/media$ cat /proc/pci
PCI devices found:
[SNIP]
Bus 0, device 4, function 0:
Ethernet controller: nVidia Corporation nForce2 Ethernet Controller (rev 161).
IRQ 20.
Master Capable. No bursts. Min Gnt=1.Max Lat=20.
Non-prefetchable 32 bit memory at 0xe0087000 [0xe0087fff].
[SNIP]

sphere@barton:~/media$ ./pci-config -a -#12
pci-config.c:v2.03 4/15/2002 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Device #12 at bus 0 device/function 4/0.
006610de 00b00007 020000a1 00000000 e0087000 0000b001 00000000 00000000
00000000 00000000 00000000 1c00147b 00000000 00000044 00000000 1401010b
1c00147b fe020001 00000100 00000004 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Base Address 0: Memory at e0087000.
Base Address 1: I/O at 0000b000.
Address 0 memory at e0087000, decoded bits are 00000fff.
Address 1 is I/O at 0000b000, decoded bits are 00000006.
No BIOS extension (boot ROM).
Extended capabilities, first structure at offset 0x44.
Extended PCI capability type 1 at 0x44, next 0.
Power management entry ver. 2: Capabilities fe02, Ctrl 0100, Event 0000.
Power state D0.

Now that you know the device number, you can force it to power state D3 at shutdown. The forcedeth driver will complain about the transceiver. After power down you are able to wake your box up by sending it a magic packet, with ether-wake for Linux for instance.

Add script for init 0:
sphere@barton:/usr/src$ more /etc/rc0.d/S21D3NIC
echo "Putting NIC to D3 state -- FIXME!!!"
/home/sphere/media/pci-config -S -#12 | grep Power
/home/sphere/media/pci-config -a -#12 | grep Power

LBJM 12-11-03 01:24 PM

good job. I knew there had to be a way with the forcedeth driver.

sphere 12-11-03 01:35 PM

Quote:

Originally posted by LBJM
good job. I knew there had to be a way with the forcedeth driver.
Please note that this has next to nothing to do with the forcedeth driver. However, I hope that this can be added to future functionality of the driver, but I'm not sure if I should leave this to the ACPI people or not, bc the driver may have to interface with the ACPI stuff in the kernel.

Also, a Nvidia engineer has confirmed that the nvnet driver, like the MS driver has WOL functionality implemented. Why it doesn't work is unknown to me.

LBJM 12-12-03 12:26 PM

Quote:

Originally posted by sphere
Please note that this has next to nothing to do with the forcedeth driver. However, I hope that this can be added to future functionality of the driver, but I'm not sure if I should leave this to the ACPI people or not, bc the driver may have to interface with the ACPI stuff in the kernel.

Also, a Nvidia engineer has confirmed that the nvnet driver, like the MS driver has WOL functionality implemented. Why it doesn't work is unknown to me.

you did tell him the hack you had to do to get it to work right? chances are the code thats in their driver is for 2.4 ACPI from june which is different then the current 2.6 ACPI(even the 2.4 ACPI is changed from then). they havent updated their drivers for linux in a very long time. theres an Nvnet petition to GPL the driver

http://www.petitiononline.com/nforce2/petition.html

I won't use the nvnet driver because of the fact it taints the kernel. they released the AGP driver GPL and its even it the kernel source now. I can understand making the video card driver closed source, but I dont agree with the motherboard drivers being closed. the big reason is they dont update them, nor are they improved. the forcedeth driver might not be as good as the nvnet driver, but it will be.

sphere 12-12-03 01:36 PM

I told him that it didn't work currently and that I use pci-config to enable the functionality currently. He isn't particularely speedy with replying, but I guess nividia engineers probably have windows drivers on their mind and linux drivers are there to play with when they can squeeze it in a quiet moment.


All times are GMT -5. The time now is 08:01 PM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.