We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now

x

Slackware: Unable to open an initial console

umerkhan
umerkhan asked
on
Medium Priority
683 Views
Last Modified: 2013-12-15
Every time, after installing Slackware 3.3 on my system,
when I reboot, after loading the kernel, it gives me
an error saying "unable to open an initial console" and
doesn't even give me a login prompt. Anyone know what I am doing wrong?
Comment
Watch Question

I've got something on the top of my mind for that one, because I had it happen once or twice myself, thinking back I think it had to do something with Lilo, maybe you should try, if you haven't already, running a DOS boot disk, then using the Loadlin program which comes with the Slakware Distrib.
Although you need an image file first for this.  So if you can't work around that, try as soon as you have exited the setup, just running liloconfig again, and then lilo  to make sure it has set up the drive ready for booting.  Sorry I can't "answer" I'm just thinking back to when it happened to me...it might come back to me soon...

Commented:
What's your computer? Where did you install Linux (UMSDOS, partition, whole disk, ...)


Commented:
It happened to me once too... let me see if I can remember...
I'd suggest you boot up from a Linux boot/root disk combination. Mount the root filesystem (be it /dev/hda1, /dev/hdb1, etc.) somewhere using the command:
  mount /dev/whatever /mnt -t ext2

Then check /mnt/dev for the following:

console
tty1

They should look something like (with an ls -l)

crw-------   2 root     root   4, 0 Jan 7 14:58 /dev/console
crw-------   2 root     root   4, 1 Jan 7 14:58 /dev/tty1

(the permissions [crw, etc.], owner [root], and date/time don't matter. What matters is that they exist, and have those mystical number pairs.)

Do you have those? If not, try using mknod:

mknod /mnt/dev/console c 4 0
mknod /mnt/dev/tty1 c 4 1

and see if that fixes the problem. (It's possible that the numbers I've given are incorrect; I'm looking at a system that's running a fairly old version of Linux.)

Commented:
Do Not Install UMSDOS because if you install it, it will detect a directory in your dos partition which is c:\linux and boot it all up. This UMSDOS is used for DOSLinux. Try installing it without UMSDOS support.

regards,

jetx

Author

Commented:
I didn't installed UMSDOS at all.
Commented:
Boot with a bootdisk and when you get to the spot for extra commands type: mount root=/dev/xxxx where xxxx is the linux partition. It sounds like lilo has the wrong partition listed for linux. Once you're in edit /etc/lilo.conf, fix the problem and re-install lilo.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.