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

From: Denis Vlasenko (vda@port.imtp.ilyichevsk.odessa.ua)
Date: Thu Nov 07 2002 - 10:17:57 EST

Next message: Matti Aarnio: "Re: Majordomo results"
Previous message: bert hubert: "Re: Silly advise in bridge Configure help"
In reply to: Frank Wang: "devfs, input event system, and kernel configuration."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Next message: Matti Aarnio: "Re: Majordomo results"
Previous message: bert hubert: "Re: Silly advise in bridge Configure help"
In reply to: Frank Wang: "devfs, input event system, and kernel configuration."
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Nov 07 2002 - 22:00:48 EST