I demand that Rainer Zocholl may or may not have written...

[snip]

One probem is logged in dmesg:

ACPI: Power Button (FF) [PWRF] apm: BIOS not found. apm: BIOS not found. NET: Registered protocol family 17 eth0: no IPv6 routers present lirc_dev: IR Remote Control driver registered, at major 61 lirc_serial: no version for "lirc_unregister_plugin" found: kernel tainted.

That's probably nothing to worry about...

lirc_serial: auto-detected active low receiver lirc_dev: lirc_register_plugin: sample_rate: 0 lp: driver loaded but no devices found Non-volatile memory driver v1.2 lirc_serial: auto-detected active low receiver lirc_dev: lirc_register_plugin: sample_rate: 0 APIC error on CPU0: 00(02) APIC error on CPU0: 02(02) APIC error on CPU0: 02(02)

[snip more APIC errors]

Presumably you've tried booting with noapic and/or nolapic?

linux@youmustbejoking.demon.co.uk(Darren Salt) 28.05.05 01:17

I demand that Rainer Zocholl may or may not have written...

[snip]

...

One probem is logged in dmesg:

...

ACPI: Power Button (FF) [PWRF] apm: BIOS not found. apm: BIOS not found.

That's OK?

...

lirc_dev: IR Remote Control driver registered, at major 61 lirc_serial: no version for "lirc_unregister_plugin" found: kernel tainted.

That's probably nothing to worry about...

Yes, i don't ;-)

...

lirc_serial: auto-detected active low receiver lirc_dev: lirc_register_plugin: sample_rate: 0 lp: driver loaded but no devices found Non-volatile memory driver v1.2 lirc_serial: auto-detected active low receiver lirc_dev: lirc_register_plugin: sample_rate: 0 APIC error on CPU0: 00(02) APIC error on CPU0: 02(02) APIC error on CPU0: 02(02)

[snip more APIC errors]

Presumably you've tried booting with noapic and/or nolapic?

What's that? Where do i say that?

I assumed that those APCI errors corresponds with the "lirc" modules. I have see during mutliple loads and unloads of lirc

lirc start APIC error APIC error APIC error lirc start APIC error APIC error APIC error

but i did not record teh exact lines.

Rainer

UseNet-Posting-Nospam-74308-@zocki.toppoint.de(Rainer Zocholl) 28.05.05 00:07

Using

http://www.vdr-wiki.de/wiki/index.php/Debian_mit_2.6.9er_/_2.6.10er_Ke rnel_f%FCr _VDR_aufsetzen

the upgrade was relatively painless.

The gain of 2.6 is, that USB(DVB and Storage) is much better supported, and the DVB drivers including DVB-T are part of the kernel!

Now let's wait if the box is stable now...

One problem is there:

nvram-wakeup 2.6.11: nvram-wakeup: ioctl RTC_ALM_READ: Invalid argument

Readme says: NOTE for Kernels 2.6.x: You must enable "Enhanced RTC support". the "generic /dev/rtc" is not enough.

I had made the RTC in modules, that was not sufficient. Compiling them inti kernekl solved that problem. Which step do i miss so that "my" modules are never started?

Dis: make make-kpkg kernel_image --revision=dvb.0 --initrd dpkg -i ../kernel-image-2.6.11_dvb.0_i386.deb

What is missing?

I made the same experience with the Sis-900 Ethernet module which was only loaded as module first. OTOH i had to edit a shell script to get the DVB-T drivers loaded...

But the most serious problem:

nvram-wakeup shuts down the box gracefully, but the box does not wake up anymore!

I am using the CSV verion of nvram-wakeup and did not had that problem with 2.4.29 on teh same board and same conf.

msi:~/video/nvram/nvram-wakeup# nvram-wakeup -D ; date Printing debug messages enbled. $Id: nvram-wakeup.h,v 1.38 2005/03/16 22:43:39 bistr-o-math Exp $ $Id: nvram-wakeup.c,v 1.78 2005/03/16 23:41:35 bistr-o-math Exp $ $Id: nvram-wakeup-mb.c,v 1.279 2005/05/11 11:51:17 bistr-o-math Exp $ $Id: bios.c,v 1.6 2004/01/23 12:00:04 bistr-o-math Exp $ $Id: gmt-test.c,v 1.17 2004/07/21 12:19:57 bistr-o-math Exp $ $Id: byteops.c,v 1.6 2003/03/18 13:44:03 bistr-o-math Exp $ $Id: nvramops.c,v 1.3 2004/05/03 22:40:13 bistr-o-math Exp $ $Id: guess.c,v 1.24 2005/03/16 22:43:39 bistr-o-math Exp $ $Id: biosinfo.c,v 1.8 2005/03/16 22:43:39 bistr-o-math Exp $ $Id: tools.c,v 1.3 2004/01/23 12:04:21 bistr-o-math Exp $ $Id: readconf.c,v 1.12 2004/07/20 14:20:36 bistr-o-math Exp $ $Id: cat_nvram.c,v 1.3 2004/05/03 22:40:13 bistr-o-math Exp $ $Id: rtc.c,v 1.6 2003/03/18 13:44:07 bistr-o-math Exp $ $Id: time.c,v 1.5 2004/06/26 07:21:23 bistr-o-math Exp $ Built at: May 28 2005 20:32:39 Opening /dev/mem in O_RDONLY mode... _DMI_ table found: base: 0xF0630, size: 0x2F0, count: 21 data block 1 at offset 0x000: type 0, size 0x014 ( 20) found string "American Megatrends Inc." found string "P1.70" found string "04/27/2004" data block 2 at offset 0x03F: type 1, size 0x019 ( 25) data block 3 at offset 0x080: type 2, size 0x008 ( 8) found string "" found string "K7S8XE+" found string "1.0" data block 4 at offset 0x0B0: type 3, size 0x011 ( 17) data block 5 at offset 0x0FC: type 4, size 0x020 ( 32) data block 6 at offset 0x188: type 7, size 0x013 ( 19) data block 7 at offset 0x1AB: type 7, size 0x013 ( 19) data block 8 at offset 0x1CE: type 5, size 0x016 ( 22) data block 9 at offset 0x1E6: type 6, size 0x00C ( 12) data block 10 at offset 0x1F9: type 6, size 0x00C ( 12) data block 11 at offset 0x20C: type 6, size 0x00C ( 12) data block 12 at offset 0x21F: type 9, size 0x00D ( 13) data block 13 at offset 0x232: type 9, size 0x00D ( 13) data block 14 at offset 0x245: type 9, size 0x00D ( 13) data block 15 at offset 0x258: type 9, size 0x00D ( 13) data block 16 at offset 0x26B: type 9, size 0x00D ( 13) data block 17 at offset 0x27E: type 9, size 0x00D ( 13) data block 18 at offset 0x291: type 8, size 0x009 ( 9) data block 19 at offset 0x2A3: type 12, size 0x005 ( 5) data block 20 at offset 0x2DD: type 64, size 0x00B ( 11) data block 21 at offset 0x2EA: type 127, size 0x004 ( 4) Following DMI entries found: - Mainboard vendor: "" - Mainboard type: "K7S8XE+" - Mainboard revision: "1.0" - BIOS vendor: "American Megatrends Inc." - BIOS version: "P1.70" - BIOS release: "04/27/2004" Using infowriter "asrock_k7s8xep" (automatically detected) Using following bios info: need_reboot = -1 addr_chk_h = 0x30 addr_chk_l = 0x31 addr_chk_h2 = 0x00 addr_chk_l2 = 0x00 addr_stat = 0x51 addr_mon = 0x00 addr_day = 0x53 addr_wdays = 0x00 addr_hour = 0x54 addr_min = 0x55 addr_sec = 0x56 shift_stat = 5 shift_mon = 0 shift_day = 0 shift_wdays = 0 shift_hour = 0 shift_min = 0 shift_sec = 0 rtc_time = 1 rtc_day = 0x70 rtc_mon = 0x00 rtc_day_0_is_c0 = 1 rtc_mon_0_is_c0 = 0 reset_day = 1 reset_mon = 0 nr_stat = 1 nr_mon = 4 nr_day = 5 nr_hour = 5 nr_min = 6 nr_sec = 6 nr_rtc_day = 8 nr_rtc_mon = 5 nr_wdays = 7 bcd = 0 day_hack = 0 upper_method = 0 chk_method = 0 Opening /dev/rtc in O_RDONLY mode... Hardware clock: 2005-05-28 20:37:35 rtc.tm_isdst : 1 rtc.tm_gmtoff: 7200 diff : 0 RTC is running in localtime! Test (this should be the current time of the hardware clock): Sat May 28 20:37:35 2005 Opening /dev/nvram in O_RDONLY mode... The size of NVRAM is 114 bytes. [some dump that maybe contain a password removed] value of the addr_stat byte is: 0x21. value of the addr_day byte is: 0x1C. value of the addr_hour byte is: 0x90. value of the addr_min byte is: 0x19. value of the addr_sec byte is: 0x80. value of the rtc_day byte is: 0x28. value of the addr_chk_h byte is: 0x98. value of the addr_chk_l byte is: 0x26. Opening /dev/rtc in O_RDONLY mode... Checksum is: 0x9826.

All values are displayed as they are stored in the nvram/rtc. (and do not correspond necessarily to the system date/time)

WakeUp : Enabled (0x21) Day : 28 (0x1C) Hour : 16 (0x90) Minute : 25 (0x19) Second : 00 (0x80) rtcDay : 28 (0x28) rtcHour : 16 rtcMin : 25 rtcSec : 00 Checksum: 0x9826

Sat May 28 20:37:35 CEST 2005

Rainer Zocholl schrieb:

[...]

# nvram-wakeup -s $((`date +%s`+ 10 * 60))

Box does not wake up anymore.

With 2.4.2x i had no such problem.

[...]

If you don't find a solution to get NVRAM-wakeup working try my ACPI-wakeup. The setup is pretty simple and with a little bit of luck your motherboard is also able, to start on this way.

You can download it from here:

http://www.zastrow4u.de/download/acpi-wakeup-0.1.tar.bz2

Regards Alfred

BTW. I use a Epox EP-8K5A2 board, which is working so far under Linux 2.6.12-rc1, but only with _daily_ recordings.

Rainer Zocholl wrote:

Or does "acpi-wakeup" only allow daily recordings?

acpi-wakeup, unless it has been fixed in newer kernels, doesn't allow to set the day but only the time. I'm using it with an asrock k7s8x motherboard and I'm piggy-backing on this "feature" to schedule an external epg scan at 7 o'clock in the morning if there's no recording scheduled for that day (and then tune to cbeebies so when my kids wake up they don't "harass" ;-) me to turn on the vdr box).

Bye

vdr@zastrow4u.de(Alfred Zastrow) 29.05.05 12:36

Once upon a time "Alfred Zastrow " shaped the electrons to say...

Luca Olivetti schrieb:

...

acpi-wakeup, unless it has been fixed in newer kernels, doesn't allow to set the day but only the time. I'm using it with an asrock k7s8x motherboard

I wonder why that was no problem with 2.4. Was something changed in the "halt" statement with 2.6.x?

Too i don't understand, why the wakeup works, when i use the botton "short", but not when i pressed it "long". The BIOS is 1.7 is that a BIOS bug?

...

and I'm piggy-backing on this "feature" to schedule an external epg scan at 7 o'clock in the morning if there's no recording scheduled for that day (and then tune to cbeebies so when my kids wake up they don't "harass" ;-) me to turn on the vdr box).

I'm recording the daily-news every day, therefore I can live with this "feature". :-)

ACK. Too there would be no big risc if the VDR-PC is started at the "wrong" day, noticed that today is nothing to and went to sleep again 3 minutes later.

Rainer

luca@ventoso.org(Luca Olivetti) 29.05.05 18:54

Once upon a time "Luca Olivetti " shaped the electrons to say...

Rainer Zocholl wrote:

...

vdr@zastrow4u.de(Alfred Zastrow) 29.05.05 12:36

Once upon a time "Alfred Zastrow " shaped the electrons to say...

...

Luca Olivetti schrieb:

...

...

acpi-wakeup, unless it has been fixed in newer kernels, doesn't allow to set the day but only the time. I'm using it with an asrock k7s8x motherboard

I wonder why that was no problem with 2.4.

We're talking about acpi wakeup, not nvram-wakeup

Neither. I am wondering why the same BIOS(!) can wakeup the box under 2.4 and can't under 2.6.x. See the previous postings under "First try" and "next try". There is no acpi-wakeup nor nvram-wakeup involved.

...

Was something changed in the "halt" statement with 2.6.x?

Too i don't understand, why the wakeup works, when i use the botton "short", but not when i pressed it "long". The BIOS is 1.7 is that a BIOS bug?

Usually a short press is a signal to the operating system to cleanly shut down itself and then turn power off[*], while a long press bypasses the os and cuts power directly.

ACK. But i had been in BIOS in that tests to avoid any problem with the OS!

Maybe a "lilo:" boot prompt could be seen before the power off.

If the short press (or an equivalent "shutdown -h now") doesn't cut power, it's probably because you (or your distribution) didn't setup apm/acpi (whichever works best with your mb) correctly.

[*] actually you can do whatever you want with the power button, I configured it to send an "hitk power" command through svdrp.

Nice idea. I'll steal it ASAP ;-)

Rainer

On Sat, 28 May 2005, Rainer Zocholl (RZ) wrote:

RZ> RZ> nvram-wakeup shuts down the box gracefully, but the box does not RZ> wake up anymore! RZ> RZ> I am using the CSV verion of nvram-wakeup and did not had that problem RZ> with 2.4.29 on teh same board and same conf.

it's the new kernel.

more precisely, it is the particular version of the ACPI or APM driver in the kernel.

when you shutdown your PC, the halt command (ACPI or APM) is called, which switches off the PC.

some boards do not wake up at all if you shutdown them using acpi. some boards do not wake up at all if you shutdown them using apm.

some boards do not wake up at all if you shutdown them using some particulat versions of acpi/apm.

See second reboot problem in README.reboot in the nvram-wakeup package.

c ya Sergei

On Mon, 30 May 2005, Rainer Zocholl (RZ) wrote:

RZ> Sergei.Haller@math.uni-giessen.de(Sergei Haller) 30.05.05 00:45 RZ> RZ> RZ> >On Sat, 28 May 2005, Rainer Zocholl (RZ) wrote: RZ> RZ> RZ>> nvram-wakeup shuts down the box gracefully, but the box does not RZ> RZ>> wake up anymore! RZ> RZ>> RZ> RZ>> I am using the CSV verion of nvram-wakeup and did not had that RZ> RZ>> problem with 2.4.29 on teh same board and same conf. RZ> RZ> >it's the new kernel. RZ> RZ> >more precisely, it is the particular version of the ACPI or APM driver RZ> >in the kernel. RZ> RZ> The APM part of the BIOS is not detected anymore. RZ> So it's only ACPI.

if nothing else works, you can still use the old kernel for shutdown (in a way described in README.reboot)

Sergei