FIXED: initial console warning
root
of my tweaks: good advice, if it were applicable. I
have been tweaking a "virgin" install to get to my
system that has been growing since kernel version 0.9.
The problem of the initial console arose when I tried
to add something to rc.local that tried to write
to the console.
For the record, the warning message comes from
/usr/src/linux/init/main.c where the kernel
cannot open /dev/console RDRW.
The fix: boot into a working system on a different
partition, mount your root partition and copy over
/dev/console to the (empty) /dev directory on the
root partition. In other words, make sure your
/dev directory already has a correct console
entry.
This is almost the same as the poster who suggested
I add the console entry to /lib/udev/devices, but
that suggestion did not work.
Henrik Carlqvist
> The fix: boot into a working system on a different
> partition, mount your root partition and copy over
> /dev/console to the (empty) /dev directory on the
> root partition.
If that was a working fix it would probably also have been possible to
recreate /dev/console either by calling the script /dev/MAKEDEV or by
using the mknod program directly.
regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost
Keith Keller
>
> If that was a working fix it would probably also have been possible to
> recreate /dev/console either by calling the script /dev/MAKEDEV or by
> using the mknod program directly.
There's no MAKEDEV script in my /dev/ directory, a Slackware-current
just before 64bit Slackware 13 was released.
Just for the record, the console is major number 5, minor number 1. So
you would do
mknod console c 5 1
(Of course if you don't have /dev/console you probably still need to
boot off of other media and mount the nonworking / separately.)
--keith
--
kkeller...@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information
Helmut Hullen
Du meintest am 18.11.09:
> There's no MAKEDEV script in my /dev/ directory, a Slackware-current
> just before 64bit Slackware 13 was released.
Surely?
Maybe you can't see it because "udev" overwrites (overmounts) the "/dev"
directory.
Look into the package a/devs-*.txz, you'll see the program "/dev/
MAKEDEV".
Stop "udev" and you'll see the real "/dev" directory.
By the way: I have copied "MAKEDEV" into "/sbin". It's now (with the bad
and ugly "udev") a better place than "/dev".
Viele Gruesse
Helmut
"Ubuntu" - an African word, meaning "Slackware is too hard for me".
root
> root <NoE...@home.org> wrote:
>> The fix: boot into a working system on a different
>> partition, mount your root partition and copy over
>> /dev/console to the (empty) /dev directory on the
>> root partition.
>
> If that was a working fix it would probably also have been possible to
> recreate /dev/console either by calling the script /dev/MAKEDEV or by
> using the mknod program directly.
>
> regards Henrik
For many years I have been running a script to upgrade
my system rather than installing from scratch. That
means I had been carrying around an *old* /dev directory.
Only recently has that changed. I don't know why udev doesn't
work for my initial console, and there may be other
devices that I find missing.
Thanks for the help.
Jerry Peters
Because udev is started well after the kernel initializes and
complains about no initial console.
If you're not using an init{rd,ramfs} you need a minimal /dev to keep
the kernel happy.
Jerry
Keith Keller
> Du meintest am 18.11.09:
>
>> There's no MAKEDEV script in my /dev/ directory, a Slackware-current
>> just before 64bit Slackware 13 was released.
>
> Surely?
> Maybe you can't see it because "udev" overwrites (overmounts) the "/dev"
> directory.
> Look into the package a/devs-*.txz, you'll see the program "/dev/
> MAKEDEV".
> Stop "udev" and you'll see the real "/dev" directory.
Could be. But if the OP can't even get to runlevel 1, it won't make any
difference. He might as well at least know how to do the mknod.
Anyway, I'm not about to stop udevd on a running box just to see if
MAKEDEV is there! :)