Sun Mouse on Ultra 5 with 2.6 kernel

Mark Clegg

Anybody else having problems with the Keyboard attached Sun Mouse on an Ultra 5?

I've got an Ultra 5 with type 6 UK keyboard and mouse.

On booting the kernel (2.6.3 and 2.6.4 development-sources) the keybaord and mouse are detected correctly

cybrjackle · Apprentice Joined: 09 Jan 2003 Posts: 248 Location: USA

2.6 changed some things, so you might need to edit XF86Config. Here is what mine looks like on a ultra10

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/mouse"
Option "Protocol" "IMPS/2"

Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "type5"
Option "XkbLayout" "us"

Mark Clegg · Posted: Tue Mar 16, 2004 6:42 pm Post subject:

Sorry - it's more subtle than that. - The X config is fine, it's definately the mouse that's the problem.

I'm not even starting X, just doing a 'cat /dev/input/mouse0', or 'hexdump /dev/input/mouse0' gives no output unless I boot 2.4 before booting 2.6. Then it works fine, and I can load X with mouse support without any problems. It's only a cold boot into 2.6 that gives the problem.

I'm thinking I might have to sift through the differences between the 2.4 and 2.6 mouse kernel code to spot the differences, but I don't really fancy the idea.

Maybe I've missed something subtle in my kernel conf?

cybrjackle · Apprentice Joined: 09 Jan 2003 Posts: 248 Location: USA

Don't know if this will help or not, but here is some of my .config searching for [mouse] :

# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768

# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_KEYBOARD_SUNKBD=y
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_SERIAL=y
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y

Weeve · Retired Dev Joined: 30 Oct 2002 Posts: 641

Note you'll want the mouse device to be /dev/input/mice. Also double check you have commented out KEYMAP in /etc/rc.conf or changed it to an x86 keyboard style keymap. I forgot to do this on a u5 and my mouse didn't work at all.

smeets_marc · Posted: Thu Mar 18, 2004 9:55 pm Post subject:

Having the same problem here with 2.6.4. Previously I ran 2.6.3 witch also gave problems now I think of it. I recompiled 2.6.3 about 10 times before the mouse worked. Onze running ok, it ran for over a week great until this morning when I booted my U60 and the mouse was not functioning. I knew a new kernel was there and I wanted to check something with alsa so I tryed 2.6.5-rc1 which exits with errors on alsa CS4231 module. 2.6.4 compiles ok, but has has problems with mouse. I recalled this topic and indeed...when I unplug and plugin the mouse it works.
No dual booting with 2.4 here, just unpluging.

Funny thing here is that 2.6.3 worked for over a week and suddenly it gave problems.

Mark Clegg · Posted: Fri Mar 19, 2004 9:02 am Post subject:

I'm digging around in the sunsu code in the kernel at the moment. From what I gather Sun did different mice that ran at different baud rates (somebody might want to correct me here)

If the kernel code receives a line break from the mouse port it cycles to the next baud rate from a list until it stops getting breaks. That way it can auto detect the speed.

This technique worked ok in 2.4 but I'm wondering if 2.6 has problems with it.

I'll keep digging....

smeets_marc · Posted: Fri Mar 19, 2004 10:07 am Post subject:

When I booted my sparc this morning the mouse was functioning perfect without unplugging....

Just out curiousity, do you also have a Crossbow mouse?

Mark Clegg · Posted: Fri Mar 19, 2004 12:42 pm Post subject:

Yes it is, connected to a type 6 UK keyboard.

Mark Clegg · Posted: Fri Mar 19, 2004 7:12 pm Post subject:

Ok more info....

I've added printk's in drivers/serial/suncore.c to log the return value from suncore_mouse_baud_detection, and the selected baudrate at the end of suncore_mouse_baud_cflag_next.

On boot up all I get in dmesg is..

Mark Clegg · Posted: Sat Mar 20, 2004 7:23 pm Post subject:

It seems that under 2.6 the Serial Line Break isn't getting through, like it does in 2.4 so the mouse driver never changes speed to match the mouse. If I tweak the driver to start the mouse at 1200 baud which is what the crossbow needs, it still doesn't work for some reason.

It occurs to me, that if the UART isn't set to the same speed as the mouse, then we will also receive framing errors, so if we get the mouse driver to detect this as well, we might be in with a chance.

Initial testing of the patch below to linux-2.6.4/drivers/serial/sunsu.c seems to have some degree of success, but I need more test results before I can submit it to the kernel maintainers.

Any takers?

creideiki · Posted: Wed Jun 15, 2005 8:44 am Post subject:

There's a patch at http://marc.theaimsgroup.com/?l=linux-ultrasparc&m=111414697913857 that works much better than the one above on my Ultra10:s running gentoo-sources 2.6.11-r8. It's included in the mainline kernel as of version 2.6.12-rc4.

Emphii · n00b Joined: 08 Oct 2004 Posts: 46

I have installed 2.6.11-gentoo-r4 following the "stage 1 on 3 :oops:

" instruction couple of
months ago.

Well only thing so far which prevents to find out, what else won't work, is mouse.

I've tried to compile kernel several times by adding and removing drivers, with no
luck.

I found Mark Gleggs instructions, and got Gnome up, but mouse did nothing. If
I unplug/plug the mouse, I got major shutdown effect. :wink:

I tried also this patch, which creideiki show up, but now things went more interesting..

When I move the mouse (even accidentally), I get following message to command line