vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| After installation of Slackware 9.0 with hotplug enabled system reboots in couple of seconds after booting %) Intel 845G chipset(82801DB/DBM USB, Ultra ATA, etc.) with Celeron 2GHz CPU Disabling hotplug enbales systrem to boot and work Is there any fixes or something to do with? It's a cruel BUG - many newbies are giving up seeing system to reboot after just booting without a word saying "See, this buggy Linux is NOT working!!!" In better case they are moving to RedHat |
| |||
| "Anatoliy Okhotnikov" <uhca@ukrsotsbank.com> wrote in message news > After installation of Slackware 9.0 with hotplug enabled > system reboots in couple of seconds after booting %) > > Intel 845G chipset(82801DB/DBM USB, Ultra ATA, etc.) > with Celeron 2GHz CPU > > Disabling hotplug enbales systrem to boot and work > > Is there any fixes or something to do with? > > It's a cruel BUG - many newbies are giving up seeing > system to reboot after just booting without a word > saying "See, this buggy Linux is NOT working!!!" > > In better case they are moving to RedHat > > This has been discussed many times, if can keep the system up long enough, check dmesg output. from a shell type "dmesg" no quotes and see if you see any weird module messages/hotplug message and you've caught whatever is causing your system to booger up. just add that module to /etc/hotplug/blacklist and you're good to go. HTH Drew |
| |||
| In article <peag21-vgj.ln1@proxy.if.ukrsotsbank.com>, Anatoliy Okhotnikov wrote: > Intel 845G chipset(82801DB/DBM USB, Ultra ATA, etc.) > with Celeron 2GHz CPU > > Disabling hotplug enbales systrem to boot and work So which driver was crashing? You'll see it as the last entry in your /var/log/syslog or messages before the no-hotplug reboot. "/sbin/lspci" might give some clues as well. > Is there any fixes or something to do with? echo $BadDriverName >> /etc/hotplug/blacklist > It's a cruel BUG - many newbies are giving up seeing > system to reboot after just booting without a word > saying "See, this buggy Linux is NOT working!!!" It's true that when newbies encounter booting problems, they have a hard time understanding what's happening and why. It happened to me. If I had been content to remain ignorant, I would have given up, saying "See, this buggy Linux is NOT working!" I persisted. As it turns out, my non-standard hardware was causing the crash, and when I swapped it for something less unusual, my Linux booted fine. I later learned that I could have used a different kernel to boot that hardware. > In better case they are moving to RedHat .... where they will encounter the same problem. Please try installing Red Hat 9.0 on the same machine, and report your results back to us. -- /dev/rob0 - preferred_email=i$((28*28+28))@softhome.net or put "not-spam" or "/dev/rob0" in Subject header to reply |
| |||
| On Wed, 03 Sep 2003 08:23:50 +0300, Anatoliy Okhotnikov wrote: > After installation of Slackware 9.0 with hotplug enabled > system reboots in couple of seconds after booting %) > > Intel 845G chipset(82801DB/DBM USB, Ultra ATA, etc.) > with Celeron 2GHz CPU > > Disabling hotplug enbales systrem to boot and work > > Is there any fixes or something to do with? > > It's a cruel BUG - many newbies are giving up seeing > system to reboot after just booting without a word > saying "See, this buggy Linux is NOT working!!!" > > In better case they are moving to RedHat See you should have got an AMD, Intel isn't capatible... j/k roflmao... thinking back to comments made by some people. |
| ||||
| > After installation of Slackware 9.0 with hotplug enabled > system reboots in couple of seconds after booting %) > > Intel 845G chipset(82801DB/DBM USB, Ultra ATA, etc.) > with Celeron 2GHz CPU > > Disabling hotplug enbales systrem to boot and work This has been answered a thousand time in this n.g. Its the i810-tco driver that triggers your motherboard to REBOOT your pc. (i810-tco is a hardware watchdog on your motherboard) Its actually a problem with the motherboards that automatically start the timer, when it shouldn't.. (well maybe its a problem with the i810-tco driver too) > Is there any fixes or something to do with? yes, echo i810-tco >> /etc/hotplug/blacklist I guess this should become te default in Slack, people that need watchdogs will now what to do. -- Дамјан (jabberID:damjan@bagra.net.mk) The difference between theory and practice, is that in theory, there is no difference between theory and practice. |