USR 56k 5610 Modem: How to get it to work in FreeBSD 4.4 stable

USR 56k 5610 Modem: How to get it to work in FreeBSD 4.4 stable

Post by Joe Luc » Tue, 21 May 2002 08:53:21



Ok, here goes:

I have a modem in my box. It is a USR 5610 Pci modem. It is not a
winmodem, cause, well, i can use it in linux. This is a reach, but I
think it should work in fbsd as well. Ok, I have a serial port (sio0).

i said that right, i'm typing it from memory). Anywho, I can't get the
modem to initialize in PPP. I know that it is on COM3 (or ttyS4 in
Linux ---> but shouldn't it be ttyS2 cause it is 1 less in *nix
systems? Somebody could answer that for me too :-)) When I try to set
the device to /dev/cuaa2 (where is should be), it doesn't work. When I
try cuaa0 bsd freezes up on me. I know somebody out there can shed
some light on this subject for me :-)

Bonus question:

When I run KDE 2.2 in FBSD, the screen is huge. I've managed to gather
that it is some kind of virtual desktop or I have to edit the
resolution somehow. Could somebody point in the right direction (file
to edit)?

THANK YOU in advance, I am in dire need of help.

Regards,

J. Lucas
St. Clair, MI

 
 
 

USR 56k 5610 Modem: How to get it to work in FreeBSD 4.4 stable

Post by James Gra » Tue, 21 May 2002 15:35:42


"Joe Lucas" wrote...
> I have a modem in my box. It is a USR 5610 Pci modem. It is not a
> winmodem, cause, well, i can use it in linux. This is a reach, but I
> think it should work in fbsd as well. Ok, I have a serial port (sio0).

> i said that right, i'm typing it from memory). Anywho, I can't get the
> modem to initialize in PPP. I know that it is on COM3 (or ttyS4 in
> Linux ---> but shouldn't it be ttyS2 cause it is 1 less in *nix
> systems?

In Linux /dev/ttys4 is "COM5".  ttys0=COM1, s1=COM2 etc....

Quote:> Bonus question:

> When I run KDE 2.2 in FBSD, the screen is huge. I've managed to gather
> that it is some kind of virtual desktop or I have to edit the
> resolution somehow. Could somebody point in the right direction (file
> to edit)?

xf86config or xf86config-4 for XFree86 4.x.  Change the virtual resolution
to match the actual resolution.  man xf86config and man xf86config-4 are
your friends.

--James

 
 
 

USR 56k 5610 Modem: How to get it to work in FreeBSD 4.4 stable

Post by charo » Thu, 23 May 2002 13:52:26



> When I run KDE 2.2 in FBSD, the screen is huge. I've managed to gather
> that it is some kind of virtual desktop or I have to edit the
> resolution somehow. Could somebody point in the right direction (file
> to edit)?

        iff you are running X 3.3.6 you need to be editing /etc/XF86Config

        try this

        around line 378


        Modeline "1024x768a"    75    1024 ... and so on
        <-- change 1024x768 to 1024x768a -->

        <-- around line 544 - between 'Section "Screen"' and 'EndSection'
        just under where it sais 'Depth 32' change the Modes line to read -->
        Modes "1024x768a"

        <-- NB: I assume you are using the SVGA server. The server should choose
        the highest available resolution on the mode line and use that to set the
        virtual desktop size. The starting resolution is the first available
        one on the Mode line. Switch resolutions via 'Ctrl Alt +' and 'Ctrl Alt -'

        to test - try 'startx -- -bpp 32' otherwise iff you are using xdm

        edit /usr/X11R6/lib/X11/xdm/Xservers and change the :0 line to read -->

        :0 local /usr/X11R6/bin/X -bpp 32 -allowMouseOpenFail

        <-- this just means roughly: run the server in 32 bits per pixel mode and
        don't bleat about an unplugged mouse -->

        pps: look at the manual for the monitor - it should have a list of scan
        rates it can cope with. 1024x768 at 70 Hz is pretty safe for most monitors
        these days.

--
If you keep anything long enough, you can throw it away.

 
 
 

1. USR/3COM 56K PCI FaxModem Model 5610 config

Hi-

I bought a VALinux system with a "USR/3COM 56K PCI FaxModem Model 5610"
and found that this was config'd by a script called from
/etc/rc.d/rc.local.  I'm posting this for anyone searching for this
modem config (I dunno, maybe it's common knowledge, but methinks not :)
---
#!/bin/sh

# 01:08.0 Class 0700: 12b9:1008 (rev 01) (prog-if 02)
#        Subsystem: 12b9:00ad
#        Flags: medium devsel, IRQ 11
#        I/O ports at dff0
#        Capabilities: [dc] Power Management version 2

# A nasty hack to make the USR/3COM pci modem work.

#Scan the pci bus exit if no modem.
/sbin/lspci -d 12b9:1008 | /bin/grep -q "US Robotics" || exit

#Figure out what resources we need.
ioport=`/sbin/lspci -nvd 12b9:1008 | /bin/grep "I/O ports" | awk '{
print $4 }'`irq=`/sbin/lspci -nvd 12b9:1008 | /bin/grep " IRQ " | awk '{
print $5 }'`

#Use the ttyS3 device, COM 4 under DOS.
serport=/dev/ttyS3

#Bind modem to
device.                                                          
/bin/setserial $serport irq $irq port 0x$ioport ^fourport ^auto_irq
skip_test autoconfig spd_vhi
/bin/setserial $serport skip_test autoconfig

#check for symlink /dev/modem
if [ -L /dev/modem ]; then
        #if it exists bail out
        exit 0
        else
        #if not set the symlink.
        ln -s $serport /dev/modem
fi
#In the unlikely event /dev/modem is not a symlink this will produce an
error.
----
FWIW. Bob L.
--

2. HELP: Redhat SLIP problems

3. USRobotics PCI 56K Modem (5610-rev1) with COM5 in Windows

4. am53c794-dawicontrol2974

5. Different keymap on FreeBSD 4.4 stable won't work

6. Which Netscape and where

7. USR 5610 Modem

8. Networking 2 PCs via null modem.

9. 3Com USR 5610 PCI Modem Problems

10. USR/3COM 5610 modem

11. Solved: configuration of 3Com/USR 5610 PCI modem

12. 5610 USR modem issues

13. Vmware2 and FreeBSD 4.4-STABLE network trouble