Date: Mon, 10 Feb 1997 22:00:30 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: Tony Overfield <tony@dell.com> Cc: "Jordan K. Hubbard" <jkh@time.cdrom.com>, bugs@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Stuck! 2.2 Gamma won't go. Message-ID: <199702101300.WAA04407@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Mon, 10 Feb 1997 02:28:48 CST." <3.0.1.32.19970210022848.00691d20@bugs.us.dell.com> References: <3.0.1.32.19970210022848.00691d20@bugs.us.dell.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry for not replying promptly. I have been away from my console for a whole day today. I am mostly responsible for the psm driver and the keyboard controller I/O routines in 2.2-BETA/GAMMA and 3.0-CURRENT. >Ok, I did it again. I'm certain that I answered all the >questions correctly. I does ask me for the type of mouse >I have. After answering the question correctly, "PS/2 >mouse", it puts me in the graphical setup program. > >I read the opening graphics screen more carefully and it >says I shouldn't touch the mouse until after selecting >the mouse protocol. > >If I follow those directions, :-), it indeed works ok. > >But, when I instinctively reached for the mouse and >moved it, it totally hosed me down. I consider this >broken. After all, hadn't I just finished telling it >what kind of mouse I have? Not only that, but it puts >a shiny new mouse pointer right in the middle of a >screen surrounded by mouse driven user interface >controls saying, "Move me! Click me!" > >Regardless, even if the mouse protocol is wrong, there >doesn't seem to be any good reason for the keyboard to >go ugly on me. On the screen-o-death, "/dev/psm0" is >shown as the one selected in the mouse device selection >box, this was probably selected as a result of the >text-mode dialog before the X server launched. But the >mouse protocol button that is "pushed down" is the one >labelled "Microsoft" instead of the one labelled "PS/2." You need to specify both the protocol and the port MANUALLY. Push down "PS/2" button by pressing 'p' several times. After selecting a port AND a protocol, press 'a'. And your mouse pointer will be fine. >Shouldn't the text-mode dialog a few screens back have >set the default mouse protocol to match the mouse type >I selected from it's menu? I agree that this is annoying. If only there is a mechanism to tell XF86Setup initial values we want to show to the user... As for the dead keyboard, I haven't figured out why this is happening in XF86Setup. The keyboard and PS/2 mouse I/O routines distinguish keyboard and mouse data and tries hard not to stumble upon each other feet. Whichever mouse protocol XF86Setup thinks it is dealing with, it won't affect the psm driver; the driver just passes read data to XF86Setup, which will, BTW, certainly be confused if a wrong protocol is specified. Besides, if Ctl-Alt-F? and Ctl-Alt-BS are working, I have to say that at least these key codes are received and processed correctly by syscons internally (Ctl-Alt-F?) or properly fed to XF86Setup (Ctl-Alt-BS). This, I think, indicates that the keyboard interrupt is working as it should and key codes are read from the keyboard controller without problems, but somewhere, someone is unable to interpret normal keys... >So, if this happens, what should I do? Do I need to >re-install, or can I finish the install some other way? >- >Tony Kazu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702101300.WAA04407>