INIT: open(/dev/console): Input/output error
Hi. All of a sudden, after a quick install of Slackware and I did everything like always, this error appears at boot time
Code:
Using /etc/random-seed to initialize /dev/urandom. |
Maybe you need to change the permissions on /dev/console?
|
What would the permissions for /dev/console be ? This is what I've got
Code:
root@nykey:~# ls -al /dev/console |
Quote:
|
that could not be the proper solution...
I've the same permissions as nykey's ... Code:
$ ls -l /dev/console Code:
$ ls -l /dev/urandom /etc/random-seed |
Very interesting - my /dev/console is somehow not owned by root, and has differing permissions. Odd considering I just installed Slack on this machine a few days ago, and have never touched that file. :)
|
Quote:
Can you boot to another system (Live CD?) and try to chroot into your broken install? Might give you an indication of the problem. regards, ...drkstr **edit** Quote:
|
Quote:
Code:
oblique ~/bin $ ls -l /dev/console |
I am also now (suddenly) getting this error as mentioned by nykey with same permissions as in his #3 post in this thread. I don't run current, I run 10.2. The only things I've done lately were to play around with sshd.
Did anybody ever figure out what's causing this? Now I'm missing some messages I used to get during init like the output from dhcpcd and later sshd. |
I changed my vga mode in lilo and I rebooted 5 or six times without getting this error anymore. I have no idea if this is really fixed or not and I hate mysteries. The reason I changed the mode was that a search showed that somebody suggested that the error can be caused by a framebuffer problem. I chose a mode with higher resolution because I have a new screen (although it had worked fine without this error happening for a few weeks already :mad:) and for now it's coming up without the error message and I can see the stuff I used to get before on the console.
|
I've tried many fixes which I got on forums, by googling, etc... and none worked for me so I just reinstalled the system because I had nothing to loose, just some free time.... and I didn't get the error anymore. I was and still am courios about it too... hopefully you'll get it solved.... Good luck.
|
Quote:
|
nykey, if you get it again try checking your video card to see what native modes it supports and choose a LILO vga mode (or use the default by not specifying anything) and see if that fixes it. It worked both ways for me but since I use console sometimes I needed a high resolution mode. I'm using 795 with my new screen.
Gilead, it hasn't happened again since I reinstalled LILO with the new vga mode (maybe 10 boots). Good question though, next time I boot I'll try to look at the messages and answer you. Thanks guys, Rand |
All times are GMT -5. The time now is 08:14 AM. |