That's probably because this device behaves like a mouse. The solution would be not to attach it during hardware scans, as this port is probably not used very often. I'm not sure what we could do about this. But maby we have such a device somewhere?

Steffen: Can you help us here? If not please assign it back to the screening team.

Please attach the log of 'hwinfo --mouse --log=xxx'.

Created attachment 61486 [details]
hwinfo --mouse --log=hw.log

I don't see any signs of a serial mouse in that log. What makes you think
it is seen as a mouse?

Created attachment 61549 [details]
hwinfo --mouse --log=hw.log

Again, no serial mouse.

On console i have entered runlevel 3. Started sax2 and under "mouse", I can see the 
Microsoft Intelli Explorer and a serial mouse. 
The Router is acessed (under windows xp) with a terminal (RS232C).
How can I acess this unit under Suse, so it can be identified?
I also had some problems with the USB mouse (intelli explorer) after the setup of the operating system (suse). The mouse did not work correctly.

I can't really do anything without a log that shows the serial mouse.
The last log you sent shows some response from your serial line while
looking for a mouse, but nothing that would indicate a mouse. Still,
it is possible that some random response looks like a mouse. I'm afraid
the serial code is not going to change much in the future, so your best
approach might be to turn serial detection off using 'hwprobe=-serial'
at the boot prompt.