2002-11-06 22:42:24

by Frank Wang

Subject: devfs, input event system, and kernel configuration.

Hi,

I am trying to attach a special serial input device to an X application.
Looking at the kernel document, it seems to me the input core system (the
/dev/input/event#) fits the my needs nicely. I also realize that the input
system uses the devfs rather than the traditional major/minor number for its
device driver.

So I configured a 2.4.18-5 kernel with the following flags turned on,

- devfs turned on,
- the input core module,
- the input core's keyboard and mouse modules
- the input core's event modules

The kernel compiles fine. However, during boot process, everything under
the /var/* and several device mounts were marked as read-only and thus the
kernel fails to boot. I tried to set the devfs=nomount as its boot
parameter. It didn't help either.

Thanks in advance!

Frank Wang @ Advanced Technology Video Inc.

2002-11-07 10:37:21

by Denis Vlasenko

Subject: Re: devfs, input event system, and kernel configuration.

On 6 November 2002 20:50, Frank Wang wrote:
> Hi,
>
> I am trying to attach a special serial input device to an X
> application. Looking at the kernel document, it seems to me the input
> core system (the /dev/input/event#) fits the my needs nicely. I also
> realize that the input system uses the devfs rather than the
> traditional major/minor number for its device driver.
>
> So I configured a 2.4.18-5 kernel with the following flags turned on,
>
> - devfs turned on,
> - the input core module,
> - the input core's keyboard and mouse modules
> - the input core's event modules
>
> The kernel compiles fine. However, during boot process, everything
> under the /var/* and several device mounts were marked as read-only
> and thus the kernel fails to boot. I tried to set the devfs=nomount
> as its boot parameter. It didn't help either.

Sounds like filesystem corruption. Can you boot singleuser
and run fsck?
--
vda