Linux won't boot up
Hi guys, can anyone help?
Acer Aspire One running Linux has suddendly stopped booting up with the following message: Failed to start message bus: failed to bind socket "/var/run/dbus/system_bus_socket": Address already in use sudo:sudo please use single character optionsplease sudo:sudo no passwd entry for linpus FATAL: Module speedstep_lib not found Starting acpi daemon:acpid:starting up OK acpid: 1 rule loaded setpci: Warning: No devices selected for AE47 /etc/rc.d/rc.last.ctrl:line 17 /sys/bus/usb/devices/5-5/power/level:No such file or directory All of which means nothing to me but the thing ain't working! Any help would be greatly appreciated |
what did you last do?
install some program ? also WHAT operating system is this ? this is an acer netbook so i am guessing "limpus light" that is about 5 years out of date and was loosely based on the very OLD fedora 8 ( from 5 years ago) |
Hi John
Thanks for the quick reply, yes it is a netbook, two years old. Think it is limpus lite. Only ever used for surfing the web. Nothing installed recently, shut down as normal last night, won't boot this morning. Any ideas what's up? |
can you boot into single user mode or text only
( think of it as "safe mode" on Windows) during the 3 sec. count down at the very beginning of booting hit < enter> then < e> for edit use the down arrow to move to the boot line and a the number 1 to the end a space then 1 or a 3 for text boot then hit <b> for boot if so then read the boor log file for the error /var/log the boot.0.log and xorg.log and messages in those 3 files will be the error |
Have tried to boot into single user mode as you suggested but nothing happens just get the blue aspire one screen same as before?
Thanks |
without knowing what the logs say ... i can only guess
things like the ram becoming unseated can cause it to error or some of the ram has gone bad or some of the hardware became disconnected or has gone bad there is no dvd drive so if you "can" boot using a live USB image ? then you can read the logs |
Worth a try but I don't know how to do that, can you advise?
|
ram / harddrive not being seated properly can cause something of the sort... try to boot from a live distro and access your hard drive to ensure that it is seated (or just open the laptop, remove the hard drive/ram, then reseat the hard drive/ram).
|
I think you had a hard poweroff and dbus was not able to delete the file /var/run/dbus/system_bus_socket .
Code:
find /var -name dbus -exec ls -R {} \; /var/lib/dbus: machine-id /var/run/dbus: pid system_bus_socket The existing pid file might be the main problem . You should organize some USB Pendrive bootable linux, boot it, mount the main partition, navigate to the /var directory and delete the dbus files (not the directories) . [Another thing is ownership and permissions of the dbus files/directories.] dbus itself on Puppy Linux for example gets launched by /etc/init.d/01_messagebus script . * Nevertheless your system boots, but refuses to launch the desktop/windowmanager . The "blue screen" must be some sort of "/bin/whiptail" or "/bin/dialog" started by a script. |
Ok thanks,think I understand. Can you suggest a site or program for the USB bootable linux?
|
Quote:
http://unetbootin.sourceforge.net/ What version are you using? http://distrowatch.com/table.php?distribution=linpus |
Quote:
Linux is not for beginners. Especially Puppy Linux because it lacks the manpages, which are accessible via the internet though. I was a beginner once. |
Hey guys I've fixed it!
Followed your advice and booted with linuxliveusb.com Have upgraded to Ubuntu, working perfectly. Thank you, one and all Best regards Gary |
Congrats aspireone!
|
All times are GMT -5. The time now is 10:48 PM. |