You did a stupid mistake, my friend.
I admit - I made the same stupid mistake myself because documentation on
/dev/nvram described it as "for storing important information persistent
through reboot" and I did read somewhere in MP specs that there may be a
way to store opaque persistent information. So I thought - "great, that
must be it and Linux supports it!" and did echo "Hello world" > /dev/nvram.
The rest you know yourself...
Regards,
Tigran
On 23 Nov 1998 ketil@ii.uib.no wrote:
>
> Hi
>
> /dev/nvram, while no doubt it works, is broken, at least on my Digital
> Celebris P133.
>
> I tried to cat a string into the device (after compiling a new kernel
> with support for it, of course), and I could read it back. Great, I
> though. But when I rebooted, POST failed, the BIOS drive setup were
> horribly messed up, and suddenly I had a BIOS password.
>
> Apparently, /dev/nvram overwrites important BIOS configurations, surely,
> this isn't intended?
>
> I'll try to make a note of what BIOS the machine has, but I can't boot
> it at the moment. Drop me a mail if you really have to know.
>
> -kzm
> --
> If I haven't seen further, it is by standing in the footprints of giants
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/