[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: startx : Fatal server error: Can't set keyboard mode - follow-up
XWindows finally work on my Jornada 680. Many thanks to Valeriy who
suggested to recompile the kernel with the following options in the config
options WSDISPLAY_COMPAT_PCVT # emulate some ioctls
options WSDISPLAY_COMPAT_SYSCONS # emulate some ioctls
options WSDISPLAY_COMPAT_USL # VT handling
options WSDISPLAY_COMPAT_RAWKBD # can get raw scancodes
So, after 2 days of compilation (Tools and Kernel) on my old pentium
machine, it finally worked.
I noticed that the config file for the kernel in the current branch contains
reference to :
hpcapm0 at mainbus0
apmdev0 at hpcapm0
Although they generate error in compilation is this the forecast of power
management implemented on the jornada ?
----- Original Message -----
From: "Valeriy E. Ushakov" <uwe%ptc.spbu.ru@localhost>
Sent: Thursday, December 16, 2004 10:35 AM
Subject: Re: startx : Fatal server error: Can't set keyboard mode
On Thu, Dec 16, 2004 at 09:21:39 -0500, Alain Robillard wrote:
> Hmm, I think the problem is that 2.0 GENERIC doesn't have neccessary
> options enabled. Add these options to your kernel config:
> # compatibility to other console drivers
> options WSDISPLAY_COMPAT_PCVT # emulate some ioctls
> options WSDISPLAY_COMPAT_SYSCONS # emulate some ioctls
> options WSDISPLAY_COMPAT_USL # VT handling
> options WSDISPLAY_COMPAT_RAWKBD # can get raw scancodes
I will try this during the weekend and keep the news group informed of
results. Is the config file for the GENERIC kernel set up this way in
order to be more hardware independent or should it have these options
included for future releases ?
If has them in -current, but they were not pulled up to 2.0.
Unfortunately, very few people work on hpcsh code, so release branch
often tends to be "ignored" :(.
uwe%ptc.spbu.ru@localhost | Zu Grunde kommen
http://www.ptc.spbu.ru/~uwe/ | Ist zu Grunde gehen
Main Index |
Thread Index |