Posted by split on 13:48:00 04-21-2003
I recently installed Slackware 9.0 with the 2.4.20 kernel. Shortly after I login the machine reboots (after 10-15 seconds). I have determined the problem lies with hotplug being enabled, but it is hard to correct anything in the short amount of time I have. I have tried running the following two commands to stop hotplug from causing the machine to reboot:
chmod 644 /etc/rc.d/rc.hotplug
sh /etc/rc.d/rc.hotplug stop
But I had no luck with them. Does anyone have any idea how to take care of this?
Posted by dxprog on 00:36:00 04-22-2003
You don't have a serious CPU overheating problem do you? I know that that could cause something like that (had the same stupid problem myself).
[addsig]
Posted by split on 04:57:00 04-22-2003
dxprog,
I don't think I do. The machine runs fine with all versions of Windows, as well as every other version of Linux I have used. Any other ideas?
Posted by dxprog on 06:50:00 04-22-2003
Okay, just making sure. I have no other ideas for you. SOrry.
[addsig]
Posted by devusb on 12:13:00 04-27-2003
Did you compile this kernel yourself, or what? If you didn't I would suggest getting the kernel sources from kernel.org, building them with just what you need, maybe that will take care of the problem.
Posted by split on 04:50:00 04-30-2003
Nah, but I think I will give that a shot. It will be nice to know which modules I actually have installed and stuff.
Later.
Posted by Yjo on 03:49:00 05-01-2003
heh, i just installed Slack 9 & have a whole different set of problems.
After the 1st install startx ran gnome which hung for a couple of minutes and then complained about some missing modules. I really couldnt be bother to spend days trying to fix it from the console so i reinstalled with kdm instead. That managed to start ok, if with several seconds of screen black-out time, but seemed to completely loose the mouse & kbd: it initialised the display and gave me a typical high res splash screen with some config box, but no way to use it, or even to switch to a VT or reboot the machine...
none of my h/w is particularly nonstandard. it's all about 2 years old meaning its neither uselessly outdated nor scary new technology, and its a shame when a system doesn't work out-of the box when even *windoze* manages it with a 99.95% success rate..
/me hacks around frustratedly
Posted by dxprog on 10:18:00 05-01-2003
That's the one problem with Linux. It doesn't have the backwards compatability that Windows does. If you put a new video card in Windows it'll still run in VGA mode at the least. Not to mention install can be a real pain.
[addsig]
Posted by devusb on 10:32:00 05-01-2003
Well, actually, linux will start with a console, or even a framebuffer console, with any graphics card, no issues, out-of-the-box. And with xfree, all you need is one change in one line of one file and you've got it set for a new card. So, in that way, it is better than windows, because in that you have to download a new driver, install it, and sometimes that doesn't even work.
Posted by dxprog on 12:09:00 05-01-2003
Well, heck. I'm a Linux newbie. But without a flop drive it's easier to get into a recorvery mode with Windows, unless there's some Linux safe mode I don't know about .
[addsig]
Posted by devusb on 11:36:00 05-14-2003
Hehe, it's called runlevel 3 (on redhat-like systems, anyway)
Just run 'linux 3' on a lilo prompt, and there's some funky thing you have to do to grub, or, to an already booted system, just do /sbin/telinit 3
Posted by KaGez on 19:56:00 05-18-2003
As devusb said, there is such a "failsafe" mode
Most Linux distributions have such a entry in their bootloader.
[addsig]