-   Linux - Software (
-   -   Ubuntu/Fluxbox Hang at boot (

generallimptoes 09-27-2005 02:22 PM

Ubuntu/Fluxbox Hang at you know anything about linux booting?
ok, I just installed Ubuntu server mode on a Pentium II 400, with 256 ram. It worked fine. I then apt-'got' a lot of software like fluxbox xwindows core, etc...i followed the intructions at an ubuntu forum for what to download for a low ram installation. I left my computer alone for a while, came home from work, and it was off.

I turned it on, the graphical ubuntu boot screen came up, it came out of that back to regular boot screen and read:

Entering run level 2
Starting periodic command scheduler

and there she hangs and deosnt move.

I can boot recovery mode...

Anyone know what to do?

where by default is the .xsession file?

generallimptoes 09-27-2005 06:53 PM

Does anyone know where I can at least start to look? What is going on in the boot process at this time? What is the periodic command schedular? What does it coincide with or associate with at this time in the boot process? What is the boot process checking for to give it an 'ok,'? What directories or files are associated with this time in the boot process, or with the periodic command scheduler?

Could it be another problem?

A few of the previous procesies had failed.

What causes boot to hang? What causes boot to hang without giving any feedback?

What is run level 2?

dmellem 09-27-2005 07:25 PM

I believe runlevel 2 is "multiuser, no network" by default, but of couse it depends on how it's configured. You can run "chkconfig --list" to see what's set to run at runlevel 2.

There's a /usr/share/xsessions/ folder and the dot file is probably in your home directory (guess).


generallimptoes 09-27-2005 11:51 PM

So what do I check? Would a deinstall reinstall of anything help? What should I read?

generallimptoes 09-27-2005 11:52 PM

p.s. what is difference between recovery mode and regular mode?

dmellem 09-28-2005 10:35 AM

How "production" is your computer? If you have an extra hard disk or can install on an unused portion of the disk that may be worth while for testing. I'm sure there's some boot floppys or CDs that can check out your equipment as well. I'm unfamiliar with specific utilities for checking your hardware, though.

I haven't looked at Debian in a long time so I'm not familiar with it's boot options. I've used recovery CDs that have a minimal OS with several utilities on it. I'd guess that recovery mode bypasses most services and startup files, or perhaps disables most kernel modules. If you really want to know, you could look at your bootloader config file (e.g., grub.conf) and see what it's loading and what flags it's using.


generallimptoes 09-28-2005 09:17 PM

Im sorry i dont know what you mean by production. Could you explain? Are you saying that this could be a hardware issue/?

dmellem 09-28-2005 09:29 PM

I mean, is it just a test computer, or would you be upset if you killed your install? I think it's probably a hardware problem if it happens with all OSs, or at least a common driver that's causing it.


generallimptoes 09-28-2005 09:41 PM

No i wouldnt be upset. What small sized distros use apt-get?

dmellem 09-29-2005 12:50 AM

Sorry, I was confusing this with another post. :) I'm not sure what you've done for troubleshooting, so please forgive me if you're past all of this.

First, check your logs:
less /var/log/messages

You might see the cause there.

If there's nothing obvious, you could try using an interactive boot if your distro has it, or start in runlevel 1 (you can always use telinit to change levels after boot). The default runlevel is set in /etc/inittab or you can temporarily change it in grub or lilo. You can then try starting things individually and see what happens.

It just may be short of memory or swap space if you're running X and a bunch of services in a low-memory situation.


All times are GMT -5. The time now is 01:35 PM.