Hallo!
Ich hab heute mal versucht, mein P3B-F mittels nvram-wakeup unter Gentoo zum Starten zu bewegen.
Da der Thread hier doch leicht veraltet ist, bin ich davon ausgegangen, dass in der aktuellen nvram-wakeup Version 0.97 die Einstellungen für's P3B-F bereits drin sind.
Ausgabe von 'biosinfo':
Following DMI entries found:
- Mainboard vendor: "ASUSTeK Computer INC."
- Mainboard type: "<P3B-F>"
- Mainboard revision: "REV 1.xx"
- BIOS vendor: "Award Software, Inc."
- BIOS version: "ASUS P3B-F ACPI BIOS Revision 1008 Beta 004"
- BIOS release: "10/15/2001"
Ausgabe von 'nvram-wakeup --debug':
nvram-wakeup: Printing debug messages enbled.
nvram-wakeup: $Id: nvram-wakeup.h,v 1.35 2004/07/20 14:20:36 bistr-o-math Exp $
nvram-wakeup: $Id: nvram-wakeup.c,v 1.74 2004/07/20 14:30:40 bistr-o-math Exp $
nvram-wakeup: Opening /dev/mem in O_RDONLY mode...
nvram-wakeup: _DMI_ table found: base: 0xF1F50, size: 0x538, count: 45
nvram-wakeup: data block 1 at offset 0x000: type 0, size 0x014 ( 20)
nvram-wakeup: found string "Award Software, Inc."
nvram-wakeup: found string "ASUS P3B-F ACPI BIOS Revision 1008 Beta 004"
nvram-wakeup: found string "10/15/2001"
nvram-wakeup: data block 2 at offset 0x061: type 1, size 0x019 ( 25)
nvram-wakeup: data block 3 at offset 0x0B9: type 2, size 0x008 ( 8)
nvram-wakeup: found string "ASUSTeK Computer INC."
nvram-wakeup: found string "<P3B-F>"
nvram-wakeup: found string "REV 1.xx"
nvram-wakeup: data block 4 at offset 0x0F5: type 3, size 0x011 ( 17)
nvram-wakeup: data block 5 at offset 0x152: type 4, size 0x020 ( 32)
nvram-wakeup: data block 6 at offset 0x1A4: type 5, size 0x018 ( 24)
nvram-wakeup: data block 7 at offset 0x1BE: type 6, size 0x00C ( 12)
nvram-wakeup: data block 8 at offset 0x1D2: type 6, size 0x00C ( 12)
nvram-wakeup: data block 9 at offset 0x1E6: type 6, size 0x00C ( 12)
nvram-wakeup: data block 10 at offset 0x1FA: type 6, size 0x00C ( 12)
nvram-wakeup: data block 11 at offset 0x20E: type 7, size 0x013 ( 19)
nvram-wakeup: data block 12 at offset 0x22B: type 7, size 0x013 ( 19)
nvram-wakeup: data block 13 at offset 0x248: type 8, size 0x009 ( 9)
nvram-wakeup: data block 14 at offset 0x262: type 8, size 0x009 ( 9)
nvram-wakeup: data block 15 at offset 0x27E: type 8, size 0x009 ( 9)
nvram-wakeup: data block 16 at offset 0x28F: type 8, size 0x009 ( 9)
nvram-wakeup: data block 17 at offset 0x29E: type 8, size 0x009 ( 9)
nvram-wakeup: data block 18 at offset 0x2AD: type 8, size 0x009 ( 9)
nvram-wakeup: data block 19 at offset 0x2C5: type 8, size 0x009 ( 9)
nvram-wakeup: data block 20 at offset 0x2DA: type 8, size 0x009 ( 9)
nvram-wakeup: data block 21 at offset 0x2F2: type 8, size 0x009 ( 9)
nvram-wakeup: data block 22 at offset 0x308: type 8, size 0x009 ( 9)
nvram-wakeup: data block 23 at offset 0x31E: type 9, size 0x00D ( 13)
nvram-wakeup: data block 24 at offset 0x332: type 9, size 0x00D ( 13)
nvram-wakeup: data block 25 at offset 0x346: type 9, size 0x00D ( 13)
nvram-wakeup: data block 26 at offset 0x35A: type 9, size 0x00D ( 13)
nvram-wakeup: data block 27 at offset 0x36E: type 9, size 0x00D ( 13)
nvram-wakeup: data block 28 at offset 0x382: type 9, size 0x00D ( 13)
nvram-wakeup: data block 29 at offset 0x396: type 9, size 0x00D ( 13)
nvram-wakeup: data block 30 at offset 0x3A8: type 9, size 0x00D ( 13)
nvram-wakeup: data block 31 at offset 0x3BC: type 13, size 0x016 ( 22)
nvram-wakeup: data block 32 at offset 0x3E3: type 14, size 0x00E ( 14)
nvram-wakeup: data block 33 at offset 0x3FD: type 14, size 0x023 ( 35)
nvram-wakeup: data block 34 at offset 0x433: type 16, size 0x00F ( 15)
nvram-wakeup: data block 35 at offset 0x444: type 17, size 0x017 ( 23)
nvram-wakeup: data block 36 at offset 0x463: type 17, size 0x017 ( 23)
nvram-wakeup: data block 37 at offset 0x482: type 17, size 0x017 ( 23)
nvram-wakeup: data block 38 at offset 0x4A1: type 17, size 0x017 ( 23)
nvram-wakeup: data block 39 at offset 0x4C0: type 19, size 0x00F ( 15)
nvram-wakeup: data block 40 at offset 0x4D1: type 20, size 0x013 ( 19)
nvram-wakeup: data block 41 at offset 0x4E6: type 20, size 0x013 ( 19)
nvram-wakeup: data block 42 at offset 0x4FB: type 20, size 0x013 ( 19)
nvram-wakeup: data block 43 at offset 0x510: type 20, size 0x013 ( 19)
nvram-wakeup: data block 44 at offset 0x525: type 32, size 0x00B ( 11)
nvram-wakeup: data block 45 at offset 0x532: type 127, size 0x004 ( 4)
nvram-wakeup: Following DMI entries found:
nvram-wakeup: - Mainboard vendor: "ASUSTeK Computer INC."
nvram-wakeup: - Mainboard type: "<P3B-F>"
nvram-wakeup: - Mainboard revision: "REV 1.xx"
nvram-wakeup: - BIOS vendor: "Award Software, Inc."
nvram-wakeup: - BIOS version: "ASUS P3B-F ACPI BIOS Revision 1008 Beta 004"
nvram-wakeup: - BIOS release: "10/15/2001"
nvram-wakeup: Using following bios info:
nvram-wakeup: need_reboot = 0
nvram-wakeup: addr_chk_h = 0x6C
nvram-wakeup: addr_chk_l = 0x6D
nvram-wakeup: addr_chk_h2 = 0x00
nvram-wakeup: addr_chk_l2 = 0x00
nvram-wakeup: addr_stat = 0x56
nvram-wakeup: addr_mon = 0x00
nvram-wakeup: addr_day = 0x00
nvram-wakeup: addr_wdays = 0x00
nvram-wakeup: addr_hour = 0x00
nvram-wakeup: addr_min = 0x00
nvram-wakeup: addr_sec = 0x00
nvram-wakeup: shift_stat = 4
nvram-wakeup: shift_mon = 0
nvram-wakeup: shift_day = 0
nvram-wakeup: shift_wdays = 0
nvram-wakeup: shift_hour = 0
nvram-wakeup: shift_min = 0
nvram-wakeup: shift_sec = 0
nvram-wakeup: rtc_time = 1
nvram-wakeup: rtc_day = 0x7F
nvram-wakeup: rtc_mon = 0x00
nvram-wakeup: rtc_day_0_is_c0 = 0
nvram-wakeup: rtc_mon_0_is_c0 = 0
nvram-wakeup: reset_day = 1
nvram-wakeup: reset_mon = 0
nvram-wakeup: nr_stat = 1
nvram-wakeup: nr_mon = 4
nvram-wakeup: nr_day = 5
nvram-wakeup: nr_hour = 5
nvram-wakeup: nr_min = 6
nvram-wakeup: nr_sec = 6
nvram-wakeup: nr_rtc_day = 6
nvram-wakeup: nr_rtc_mon = 5
nvram-wakeup: nr_wdays = 7
nvram-wakeup: bcd = 0
nvram-wakeup: day_hack = 0
nvram-wakeup: upper_method = 0
nvram-wakeup: chk_method = 0
nvram-wakeup: Opening /dev/rtc in O_RDONLY mode...
nvram-wakeup: Hardware clock: 2005-03-29 17:25:32
nvram-wakeup: rtc.tm_isdst : 1
nvram-wakeup: rtc.tm_gmtoff: 7200
nvram-wakeup: diff : 0
nvram-wakeup: RTC is running in localtime!
nvram-wakeup: Test (this should be the current time of the hardware clock): Tue Mar 29 17:25:32 2005
nvram-wakeup: Opening /dev/nvram in O_RDONLY mode...
nvram-wakeup: The size of NVRAM is 114 bytes.
nvram-wakeup: 0000000: 0000 4060 F032 0380 02C0 FF2F 0002 0002
nvram-wakeup: 0000010: 710E 1002 0100 0020 0000 0000 3002 0080
nvram-wakeup: 0000020: 059D C0FF 2001 C688 0300 0000 0100 0006
nvram-wakeup: 0000030: 0000 0004 FF3F 4614 0000 0000 4638 0004
nvram-wakeup: 0000040: FF3F 46FB 0000 0000 4638 1485 0217 0000
nvram-wakeup: 0000050: 0000 8800 20F7 1703 0000 0000 0000 E131
nvram-wakeup: 0000060: 0900 0000 0000 0000 0000 0000 08A1 FFFF
nvram-wakeup: 0000070: FFFF
nvram-wakeup: value of the addr_stat byte is: 0x17.
nvram-wakeup: rtc_day (0x7F) is beyond the end of nvram
nvram-wakeup: You might want to use the --directisa command line option.
Display More
Jetzt habe ich ausgeführt:
nvram-wakeup --directisa -s $((`date +%s` + 601))
Und es wird auch alles korrekt geschrieben. Jedoch bleibt der Rechner aus, auch nach dem Durchgehen der Reboot-Problematik-Punkte in Hubertus Sandmann's Anleitung. Warum? Hab ich noch was vergessen?
Vielen Dank,
Chol.