Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
One of my computers uses Debian GNU/Linux 5.0 Lenny. When I went to boot up this morning, this is what I got:
Decompressing Linux ... Parsing ELF ... done.
Booting the kernel.
[ 0.248015] PCI: Not using MMCONFIG
Loading, please wait ...
udevd [381]: error getting socket: Invalid argument
error initializing netlink socket
After 5 minutes of the above data on the screen, this is what came up:
Gave up waiting for root device. Common Problems:
- Boot args (cat/proc/cmdline)
- Check rootdelay=(did the system wait long enough?)
- Check root= (did the system wait tor the right device?)
- Mi8ssibng modules (cat/proc/modules;Is/dev)
ALERT! /dev/sdal does not exist. Dropping to a shell!
BusyBox vl.14.2 (Debian 1:1.14.2-2) built-in shell (ash)
Enter: help for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
(initramfs)
Anybody know what is going on, and what I can do to fix it?
Thank you for the response pentode. Yes, it was working fine the day before and there was no trouble booting up then. I have been doing updates/upgrades pretty much every day - apt-get update and then apt-get upgrade after the update. I will try a few things and see if I can get something happening. Again, thank you for the tips. I will re-post something here if there are any changes.
Yes, I tried booting up in single user mode and it went to a login prompt. I then typed startx at that prompt, and got this:
Failed to start the X server (your graphical interface). It is likely that it is not
set up correctly. Would you like to view the X server output to diagnose the problem?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.