Re: Re: y fails to start but gives no useful error message

The fbdev stuff works now. I wrote a script to autogenerate a vanilla
fb.modes file in case I ever have to do this again... The display
looks great at 1024x768x32. Repaints rather slowly considering there's
no load on the box, but I'm assuming the kernel fbcon driver just
doesn't refresh often enough to look snappy.

I got the mouse and keyboard event stuff to work, as in I can cat
/dev/input/event0 and get keyboard nonsense, and mouse nonsense from
event1. The mouse works in Y, so I can drag windows around and such,
but the keyboard doesn't work. I know it's not the event interface
itself since that's tested. Keymap us or gb makes no difference.

I would have looked to see if my keyboard output was still being
routed to tty1, but attempting to switch tty's after Y has started
causes the screen to turn into white lines and stop repainting.
Doesn't crash the whole box, I can still log in on tty2 or ssh, but
working blind is no fun. This isn't a one time glitch, it happens
every time and only a reboot will clear it.

So, two things. Has anyone else had trouble with the keyboard when
using evdev driver? And is the tty switching thing a problem for
anyone else?

On 1/23/06, Jerrit Erickson <[email protected]> wrote:
> On 1/23/06, Kristian Mueller <[email protected]> wrote:
> > Hi Jerrit
> >
> > On Mo, 2006-01-23 at 18:00 -0500, Jerrit Erickson wrote:
> > > [..] We/I really ought to be a handbook for this stuff.
> > > Something along the lines of life with qmail or the gentoo handbooks
> > > that walks through a setup from scratch, in painstaking detail, just
> > > to get new people running Y without having to go through this sort of
> > > thing.
> >
> > That sounds good. Maybe you can put that article into the new Wiki?
> Sure.
>
> >
> >
> > Kristian
> >
> >
>