I have the mouse working, I reinstalled Linux with the serial port 
enabled, configured the mouse to ttyS0 and it worked. And all my 
packages and everything (well almost everything) is wonderful.

Thanks to all!

Sam.

Sam MacDonald wrote:

> But no IRQ is allocated.
> I'll boot with a DOS disk, (tools I know well)
> ***********
> I didn't have COM1 under msd.exe
> I sort of hate when one setting in a BIOS can effect another and I 
> don't think about it long enough.
> I checked the power settings in BIOS serial was "Disabled" one would 
> think that would mean "don't turn the power off on the COM port"  I 
> "Enabled" it and restarted.
> COM1 is now found by msd.exe
> ***********
> stty -F /dev/ttyS0 raw 1200
> cat /dev/ttyS0 | od
>    now returns
> 9 colums of 6 digits scrolling.  Moving the mouse does nothing.
>
> dmesg | grep tty
>     returns
> ttyS00 at ox03f8 (irq = 4) is at 16450
>
> Sam.
>
>
> Scot Jenkins wrote:
>
>> try Karl's trick on the other com ports as well (/dev/ttyS1, 
>> /dev/ttyS2, etc...) I have an couple Gateway machines that the BIOS 
>> does strange numbering of COM ports.  Instead of COM1 and COM2 
>> they're COM2 and COM3.  Especially with a laptop, who knows what the 
>> manufacturer was thinking that day.
>>
>> see what ports the kernel detects right after bootup:
>>
>>     dmesg | grep tty
>>
>> you should see something like:
>>
>>     ttyS00 at 0x03f8 (irq = 4) is a 16550A
>>     ttyS01 at 0x02f8 (irq = 3) is a 16550A
>>
>> I don't think that your debian install will do evil things like renumber
>> or hide com ports from you.
>>
>> Sam MacDonald wrote:
>>  
>>
>>> Well that's tell me what I need to know.
>>> The serial port is not found anywhere and no resources are allocated 
>>> (goes without saying). So where the f is it!
>>> I'm thinking the way this laptops hardware/BIOS is setup, with the 
>>> setting for the mouse, set to the PS2 port during the install of 
>>> debian, the serial port was not found at install.  Hmmm... 26 
>>> diskettes to install without knowing if it would work.
>>>
>>> Any other ideas folks?
>>>
>>> ***********************************
>>> [From: Karl Bongers ]
>>>
>>> /etc/init.d/gpm stop
>>>    *Result*
>>> Stopping mouse interface server: gpm.
>>>
>>> /etc/init.d/gpm stop
>>>
>>> stty -F /dev/ttyS0 raw 1200
>>> cat /dev/ttyS0 | od
>>>     *Results*
>>> stty: /dev/ttyS0: input/output error
>>> stty: /dev/ttyS1: input/output error
>>>
>>> [From: Karl Bongers ]
>>> cat /proc/interrupts
>>>     *Results*
>>>     CPU0
>>> 0:    4644729    XT-PIC    timer
>>> 1:    789    XT-PIC    keyboard
>>> 2:    0    XT-PIC    cascade
>>> 3:    1929    XT-PIC    xirc2ps_cs
>>> 8:    3    XT-PIC    rtc
>>> 11:    4    XT-PIC    i82365
>>> 13:    0    XT-PIC    fpu
>>> 14:    92546    XT-PIC    ide0
>>> NMI:    0
>>> ***********************************
>>>   
>>
>>
>> _______________________________________________
>> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
>> http://www.mn-linux.org tclug-list at mn-linux.org
>> https://mailman.real-time.com/mailman/listinfo/tclug-list
>>
>>  
>>
>
>
> _______________________________________________
> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
> http://www.mn-linux.org tclug-list at mn-linux.org
> https://mailman.real-time.com/mailman/listinfo/tclug-list
>


_______________________________________________
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
http://www.mn-linux.org tclug-list at mn-linux.org
https://mailman.real-time.com/mailman/listinfo/tclug-list