Slack reboot my computer

laurentbon · 08-23-2003, 03:17 AM

My computer has 2 hardrives: one with win2000 and the other on which I have installed Slack 9 from the installation cd.

My problem is as follow:

- Having the linux hd as a slave, I boot from the boot floppy I made and find myself in slack. Everything is fine and I can use my command line and even fire x up. But after about 1 minute the computer turns itself off and back on!

- If I set up lilo and put my linux hd as master, I can boot in slack from lilo but the same problem occurs after the same lapse of time.
Furthermore, from the lilo prompt, I can't boot in windows as nothing happens. Clicking windows at the lilo prompt just put me back to the prompt..

I should add that I have a Gainward video card with an nvidia GeForce 4 Ti.

Has anyone experienced the power off of a computer after about a minute in slack? Is it hardware related? What can I do to debug? Help...

L

linuxJaver · 08-23-2003, 05:17 AM

First of all make clear that the first Harddisk will be referenced as /dev/hda and the second HD as /dev/hdb in linux when ur HDs are IDE/EIDE hardisks, scsi ones will be referenced as /dev/sda, /dev/sdb ..

According to the information u posted above the following lines should be on ur /etc/lilo.conf

image = /boot/vmlinuz
root = /dev/hdb1
append=" hdc=ide-scsi"
label = slackware
read-only

other = /dev/hda1
label = Windows
table = /dev/hda

other=/dev/fd0
label=floppy
unsafe

Especially the windows-entries should look like that if your windows-OS is installed on the first IDE-HD on the first partition.

Just make a comparison, maybe some edit to ur /etc/lilo.conf then execute "lilo -v -v " on the command prompt to actualize the mbr-record, reboot, try to see whether u can boot into windows ..

As for the caused of that self reboot of slack u may post more infos .. Just type : " dmesg > dmesg.txt " on the shell prompt then grab the dmesg.txt into here, maybe some guys in here will be able to find out wuts wrong later ..

brain_bucket · 08-23-2003, 09:22 PM

This is a moderatly common problem. It's usualy a problem with the Watchdog Timer. Try:

Code:

rmmod i810-tco

That will remove the i810-tco module. Now wait awhile and if the system doesn't reboot itself add this to your /etc/modules.conf

Code:

alias i810-tco off
alias i810-rng off

That will stop i810-tco and i810-rng (random number generator) from loading up.
-brain_bucket2000

laurentbon · 08-26-2003, 03:44 AM

Thank you for your replies! I will try to remove the watchdog timer tonight and also play further with lilo.
Will post my progress as soon as I can!
L

laurentbon · 08-29-2003, 04:20 AM

Thanks brain_bucket, your tip worked perfectly!
The only one thing I need now is to find out how to set up lilo to boot either from my primary hd (slack) or my seconday one (win)....
Thanks again!