Prev: recent updates broke the nvidia binary driver?! (64-current)
Next: Live CD/DVD for SlackWare?
From: Robby Workman on 9 Mar 2010 00:41
On 2010-03-09, kevin <kellis360(a)gmail.com> wrote:
>
> I had the same issue, the fix for me was to go into my custom kernel
> and turn on the /dev tmpfs and then everything booted fine. It's
> located here:
>
> Device Drivers ->
> Generic Driver Options ->
> Create a kernel maintained /dev tmpfs (EXPERIMENTAL)
> Automount devtmpfs at /dev
>
> That was the only change I made and the system boots fine now. Didn't
> have to downgrade udev at all.


You should make sure you don't have that DEPRECATED_SYSFS config
parameter enabled, because it sounds like you're just papering
over the real problem with the "free lunch" nodes provided by
devtmpfs.

-RW
From: Helmut Hullen on 11 Mar 2010 10:58
Hallo, kevin,

Du meintest am 08.03.10:


> I had the same issue, the fix for me was to go into my custom kernel
> and turn on the /dev tmpfs and then everything booted fine. It's
> located here:

> Device Drivers ->
> Generic Driver Options ->
> Create a kernel maintained /dev tmpfs (EXPERIMENTAL)
> Automount devtmpfs at /dev

> That was the only change I made and the system boots fine now.
> Didn't have to downgrade udev at all.

That option may lead to another problem: if you have compiled your
kernel with this option it *must* use "udev" too.

I don't like "udev", I've tried a kernel with devtmpfs and no "rc.udev":
many devices had gone. p.e. "/dev/sg0" which is needed from and for
"cdrecord".

Viele Gruesse
Helmut

"Ubuntu" - an African word, meaning "Slackware is too hard for me".

First  |  Prev  | 
Pages: 1 2
Prev: recent updates broke the nvidia binary driver?! (64-current)
Next: Live CD/DVD for SlackWare?