Temporary mail address, use [EMAIL PROTECTED] if you write to me
direct.
> #1) Periodic X locks. These happen maybe once every week or two, and
> generally after a session of quake3 has just ended. Easily remidied by
SSHing
> from another box on the network. I don't believe I've had one since I
upgraded
> my nvidia geforce drivers. I'm not totally sure though.
There were some troubles with some version of those drivers, seen some
downgraded back to 0.9.6 from 0.9.7 versions. Hopefully the 1.0 ones out
now, are gold.
> #2) My box completely crashes during the process of making a bootdisk
> with the command "mkboot" under Debian Unstable [Sid]. The box locks very
hard
> - monitor blanks out totally and claims it's not getting a signal.
Network
> goes down, so no ssh or telnet. After a hard reboot, the monitor still
won't
> get a signal, and I have to physically remove the video card, and other
> peripheral cards, and reinstall them separately. Then all works ok. It's
good
> to assume that I don't make bootdisks anymore unless extremely necessary.
Right now, mkboot is a shell script, you'll find a procedure in there called
makelilo. Simply make a copy of mkboot, and put in some simple debugging
with echo, and then after unmounting as many file systems as you can,
'sh -x mymkboot', to see what is causing this.
Possibly it's when the floppy is being written, maybe there's a lot of
interrupts going on or something. I've had a number of installs on various
systems, where the 'make a boot floppy' bit seemed to cause lock ups, though
ironically for me, it worked perfectly under Debian (woody).
Rob
--
=- To unsubscribe, email [EMAIL PROTECTED] with the -=
=- body of "unsubscribe linux-abit". -=
