Tach,
tscha, neuer Kernel, neues Glück, heisst es ja. Also auch mal ne neue Version von nvram. Da die alte eh auf einmal nicht mehr ging, hier halte ich mal die geflushte Bios-Version 1013 für den Übeltäter, konnte ich auch das aktuelle nvram draufklatschen.
Natürlich, wie bei meinem Glück stets üblich, stand mein ASUS-Board zwar drinne, aber die Bios-Version natürlich nicht.
Mit der alten 1006 ging das Board ohne Mucken und ohne Reboot, ergo ist es nvram-tauglich.
Liegst nu am Kernel, der neuen Bios-Version, ich weiss es net.
dev/nvram, dev/rtc sindt fest im Kernel drin und die Verzeichnisse existieren auch alle, aber die da von der guess-helper erzeugten Dateien bringen mich dann doch ans Grübeln...
Zunächst ma die aus /root/guess-directisa...
ZitatAlles anzeigen################################################
## Mainboard autodetection information:
##
## - Mainboard vendor: "ASUSTeK Computer INC."
## - Mainboard type: "A7V8X-X"
## - Mainboard revision: "REV 1.xx"
## - BIOS vendor: "Award Software, Inc."
## - BIOS version: "ASUS A7V8X-X ACPI BIOS Revision 1013"
## - BIOS release: "09/02/2004"
addr_stat = 0x4D # but differs somewhere else
shift_stat = 5
addr_stat = 0x6C # but differs somewhere else
shift_stat = 5
rtc_sec = 0x73
rtc_min = 0x75
rtc_hour = 0x77
addr_chk_h = 0x4E
addr_chk_l = 0x6B
upper_method = VT8235_37
alternativ dann die aus guess-nvram-module...
<schnipp>
ZitatAlles anzeigen## - BIOS release: "09/02/2004"
addr_stat = 0x4D # but differs somewhere else
shift_stat = 5
addr_stat = 0x6C # but differs somewhere else
shift_stat = 5
addr_chk_h = 0x4E
addr_chk_l = 0x6B
Keiner der beiden Dateien funktioniert so wirklich...
Was passiert bei Eingabe von guess in nvram-module-Verzeichnis ?
Das hier...
ZitatAlles anzeigenvdrclient01 guess-nvram-module # guess
$Id: guess.c,v 1.22 2004/03/04 08:38:14 bistr-o-math Exp $
Opened file 31.23.59.59+ readonly...
Opened file 11.12.13.14+ readonly...
Opened file 01.00.00.00+ readonly...
Opened file 01.00.00.00- readonly...
Couldn't read byte 0x72 from 31.23.59.59+
Assuming size of files 114 bytes
################################################
## Mainboard autodetection information:
##
guess: Opening /dev/mem in O_RDONLY mode...
guess: _DMI_ table found: base: 0xF38C0, size: 0x570, count: 50
guess: data block 1 at offset 0x000: type 0, size 0x014 ( 20)
guess: found string "Award Software, Inc."
guess: found string "ASUS A7V8X-X ACPI BIOS Revision 1013"
guess: found string "09/02/2004"
guess: data block 2 at offset 0x05A: type 1, size 0x019 ( 25)
guess: data block 3 at offset 0x0B2: type 2, size 0x008 (
guess: found string "ASUSTeK Computer INC."
guess: found string "A7V8X-X"
guess: found string "REV 1.xx"
guess: data block 4 at offset 0x0EE: type 3, size 0x011 ( 17)
guess: data block 5 at offset 0x14B: type 4, size 0x020 ( 32)
guess: data block 6 at offset 0x19A: type 5, size 0x016 ( 22)
guess: data block 7 at offset 0x1B2: type 6, size 0x00C ( 12)
guess: data block 8 at offset 0x1C6: type 6, size 0x00C ( 12)
guess: data block 9 at offset 0x1DA: type 6, size 0x00C ( 12)
guess: data block 10 at offset 0x1EE: type 7, size 0x013 ( 19)
guess: data block 11 at offset 0x20B: type 7, size 0x013 ( 19)
guess: data block 12 at offset 0x228: type 8, size 0x009 ( 9)
guess: data block 13 at offset 0x242: type 8, size 0x009 ( 9)
guess: data block 14 at offset 0x25E: type 8, size 0x009 ( 9)
guess: data block 15 at offset 0x26F: type 8, size 0x009 ( 9)
guess: data block 16 at offset 0x27E: type 8, size 0x009 ( 9)
guess: data block 17 at offset 0x28D: type 8, size 0x009 ( 9)
guess: data block 18 at offset 0x29C: type 8, size 0x009 ( 9)
guess: data block 19 at offset 0x2AB: type 8, size 0x009 ( 9)
guess: data block 20 at offset 0x2BA: type 8, size 0x009 ( 9)
guess: data block 21 at offset 0x2C9: type 8, size 0x009 ( 9)
guess: data block 22 at offset 0x2E1: type 8, size 0x009 ( 9)
guess: data block 23 at offset 0x2F6: type 8, size 0x009 ( 9)
guess: data block 24 at offset 0x30E: type 8, size 0x009 ( 9)
guess: data block 25 at offset 0x326: type 8, size 0x009 ( 9)
guess: data block 26 at offset 0x33E: type 8, size 0x009 ( 9)
guess: data block 27 at offset 0x356: type 8, size 0x009 ( 9)
guess: data block 28 at offset 0x36A: type 8, size 0x009 ( 9)
guess: data block 29 at offset 0x381: type 8, size 0x009 ( 9)
guess: data block 30 at offset 0x39D: type 9, size 0x00D ( 13)
guess: data block 31 at offset 0x3B1: type 9, size 0x00D ( 13)
guess: data block 32 at offset 0x3C5: type 9, size 0x00D ( 13)
guess: data block 33 at offset 0x3D9: type 9, size 0x00D ( 13)
guess: data block 34 at offset 0x3ED: type 9, size 0x00D ( 13)
guess: data block 35 at offset 0x401: type 9, size 0x00D ( 13)
guess: data block 36 at offset 0x415: type 9, size 0x00D ( 13)
guess: data block 37 at offset 0x427: type 11, size 0x005 ( 5)
guess: data block 38 at offset 0x431: type 13, size 0x016 ( 22)
guess: data block 39 at offset 0x458: type 14, size 0x00E ( 14)
guess: data block 40 at offset 0x472: type 14, size 0x01D ( 29)
guess: data block 41 at offset 0x4A2: type 16, size 0x00F ( 15)
guess: data block 42 at offset 0x4B3: type 17, size 0x017 ( 23)
guess: data block 43 at offset 0x4D1: type 17, size 0x017 ( 23)
guess: data block 44 at offset 0x4EF: type 17, size 0x017 ( 23)
guess: data block 45 at offset 0x50D: type 19, size 0x00F ( 15)
guess: data block 46 at offset 0x51E: type 20, size 0x013 ( 19)
guess: data block 47 at offset 0x533: type 20, size 0x013 ( 19)
guess: data block 48 at offset 0x548: type 126, size 0x013 ( 19)
guess: data block 49 at offset 0x55D: type 32, size 0x00B ( 11)
guess: data block 50 at offset 0x56A: type 127, size 0x004 ( 4)
guess: Following DMI entries found:
guess: - Mainboard vendor: "ASUSTeK Computer INC."
guess: - Mainboard type: "A7V8X-X"
guess: - Mainboard revision: "REV 1.xx"
guess: - BIOS vendor: "Award Software, Inc."
guess: - BIOS version: "ASUS A7V8X-X ACPI BIOS Revision 1013"
guess: - BIOS release: "09/02/2004"
## - Mainboard vendor: "ASUSTeK Computer INC."
## - Mainboard type: "A7V8X-X"
## - Mainboard revision: "REV 1.xx"
## - BIOS vendor: "Award Software, Inc."
## - BIOS version: "ASUS A7V8X-X ACPI BIOS Revision 1013"
## - BIOS release: "09/02/2004"
checking 0x4D: 0xE0 0xE0 0x60 0x40
addr_stat = 0x4D # but differs somewhere else
shift_stat = 5
checking 0x4E: 0xDF 0xDA 0xD8 0xD8
checking 0x6B: 0x0A 0x0A 0x09 0x09
checking 0x6C: 0x2E 0x29 0xA7 0x87
addr_stat = 0x6C # but differs somewhere else
shift_stat = 5
addr_chk_h = 0x4E
addr_chk_l = 0x6B
vdrclient01 guess-nvram-module # nvram-wakeup -C /root/guess-nvram-module/mymb.conf
nvram-wakeup: /root/guess-nvram-module/mymb.conf: 14: Previous definition of variable `addr_stat': first definition in line 12
nvram-wakeup: Reading configuration file returned with errors.
Da ist doch wieder was gründlich schiefgegangen...seufz... Wenn ich mich recht erinnere, funktionierte guess bei diesem ASUS-Board nicht so richtig.
Wo kann ich bei der Fehlersuche diesmal ansetzen ???
Ich nehm mal an, die Problematik ist annähernd noch die gleiche wie damals in diesem Thread hier. Da wars ähnlich...
http://www.vdr-portal.de/board/thread.php?threadid=19566&sid=&hilight=nvram&hilightuser=794
Damals bekam man nach Eingabe von nvram-wakeup -s $((`date +%s` + 601)) die entsprechenden Werte angezeigt, da ich ja wohl bei meinem Brett (immer) noch ohne Konfigurationsdatei auskomme ???
Allerdings isses diesmal anders...
ZitatAlles anzeigenvdrclient01 / # nvram-wakeup -s $((`date +%s` + 601))
nvram-wakeup: Your mainboard is currently not supported.
nvram-wakeup: Please try determining the addresses and sending the following
nvram-wakeup: information back to the maintainers:
nvram-wakeup: - The addresses you found out (read README.mb)
nvram-wakeup: - Mainboard vendor: ASUSTeK Computer INC.
nvram-wakeup: - Mainboard type: A7V8X-X
nvram-wakeup: - Mainboard revision: REV 1.xx
nvram-wakeup: - BIOS vendor: Award Software, Inc.
nvram-wakeup: - BIOS version: ASUS A7V8X-X ACPI BIOS Revision 1013
nvram-wakeup: - BIOS release: 09/02/2004
Es reicht doch jetzt wohl net wirklich, einfach einen neuen Eintrag in der nvram-wakeup-mb.c anzulegen, für die andere Bios-Version ???
ZitatAlles anzeigenvdrclient01 nvram-wakeup-0.97 # cat nvram-wakeup-mb.c |grep a7v8
void asus_a7v8x(struct biosinfo *b)
{ asus_a7v8x, "asus_a7v8x", "ASUSTeK Computer INC.", "A7V8X", "REV 1.xx", "Award Software, Inc.", "ASUS A7V8X ACPI BIOS Revision 1007", "10/04/2002" },
{ asus_a7v8x, "asus_a7v8x", "ASUSTeK Computer INC.", "A7V8X", "REV 1.xx", "Award Software, Inc.", "ASUS A7V8X ACPI BIOS Revision 1010", "11/15/2002" },
{ asus_a7v8x, "asus_a7v8x", "ASUSTeK Computer INC.", "A7V8X", "REV 1.xx", "Award Software, Inc.", "ASUS A7V8X ACPI BIOS Revision 1012", "05/08/2003" },
{ asus_a7v8x, "asus_a7v8x", "ASUSTeK Computer INC.", "A7V8X-X", "REV 1.xx", "Award Software, Inc.", "ASUS A7V8X-X ACPI BIOS Revision 1005", "05/08/2003" },
{ asus_a7v8x, "asus_a7v8x", "ASUSTeK Computer INC.", "A7V8X-X", "REV 1.xx", "Award Software, Inc.", "ASUS A7V8X-X ACPI BIOS Revision 1006", "08/06/2003" },
{ asus_a7v8x, "asus_a7v8x", "ASUSTeK Computer INC.", "A7V8X-X", "REV 1.xx", "Award Software, Inc.", "ASUS A7V8X-X ACPI BIOS Revision 1007", "11/13/2003" },
1013 fehlt natürlich...aber nimmer lange, denke ich mal.
Greets Olaf