Skip to contentSkip to conversation

sysctl interface to bootflags?

DISCUSSION Thomas Hood 2 participants 3 messages Oct 10, 2001

lore
Share & tools
lore
#0 lore raw

Well, it may run, but what it changed was NOT the SBF field. When I restarted my machine the BIOS beeped and told me there was an error in the nonvolatile RAM. I was made to reset the system date, and then the computer rebooted normally.

--
Thomas

Quoted 11 lines

Thanks. I tested the new sbf.c and after hacking it a bit to remove the fail-on-invalid-reg-value, it runs:

root@thanatos:/home/jdthood/src/sbf# ./a.out
BOOT @ 0x07fd0040
CMOS register: 0x33
Read current value := 0x88
Read updated value := 0x89

Here it has set bit 0, the PnP-OS bit. Do you have any plans to enhance the program to allow control of all the flags?

#1 lore raw
Quoted 5 lines · Thomas Hood

Well, it may run, but what it changed was NOT the SBF field. When I restarted my machine the BIOS beeped and told me there was an error in the nonvolatile RAM. I was made to reset the system date, and then the computer rebooted normally.

Ouch. Can you verify that the CMOS register its changing matches with what's listed in the BOOT record ?
add a printk to bootflag.c to check.

regards,

Dave.

Signature · 2 lines
| Dave Jones.        http://www.suse.de/~davej
| SuSE Labs
#2 lore raw
Quoted 3 lines · Dave Jones

Ouch. Can you verify that the CMOS register its changing matches with what's listed in the BOOT record ?
add a printk to bootflag.c to check.

I haven't rebooted since this happened; the error occurred when I resumed from hibernation.

In any case, I suspect that the BIOS reset whatever register it was that was incorrectly set. Here again is the output of the sbf program that cause the problem. I ran the "sbf-0.3" version of the program, modified to ignore the parity error on the value read back from the register.

root@thanatos:/home/jdthood/src/sbf# ./a.out
BOOT @ 0x07fd0040
CMOS register: 0x33
Read current value := 0x88
Read updated value := 0x89

We need to come to a better understanding of what it's doing differently from bootflag.c, which writes to the right place.

Regards
Thomas