   FIXED!!Help Request(FreeBSD): Trying to get modem to work.
  Aka, Linux RPM with modem drivers, how to?This is regarding a U.S. Robotics V92 Fax PCI modem, a.k.a. 56k Performance Pro Modem a.k.a. mod 5610b on (according to windows device manager) Com 3, Irq 11 (Loc: 5, PCI Bus 0, device 12, function 0)Hello there! I have found the URL for my modem drivers with linux (binary) RPM file (yay!)quote:The instructions at given say:    Install the RPM file by entering the rpm -i 3ComMdm-1.0-1.i386.rpm command at the command prompt.My boggle is what should I do for FreeBSD (5.0-Release)?I have linux compatibility installed, rpm-3.0.6.tar.gz downloaded and rpm2cpio.pl (which should make the rpm into something cpio can deal with, whatever that is.), I also was able to extract rpm-3.0.6.tar.gz into:D:.+---bin|  3ComMdm|+---etc|   \---rc.d|  \---init.d|serial|\---usr    \---man   \---man1 3ComMdm.1  But I'm not sure how to go about using the dern thing, or for that matter if I even can… or perhaps should.I found that dmsg saysquote:sio0: <3COM PCI FaxModem> port 0xe800-0xe807 irq 5 at device 12.0 on pci0sio0: moving to sio4sio4: type 16550AWindows reports the modem on Com3, which should be /dev/cuaa2 … I seem to have only /dev/cuaa0, /dev/cuaa1 and /dev/cuaa4 … I’m guessing that is because the modem is stuck in /dev/cuaa2 and there is no driver for it so it does not show up. (love FreeBSD 5’s devfs I think it is called.)`man sio` mentioned that 3COM PCI FaxModem (of which mine qualifies I believe) was suported/found (something of that nature, I do not recall the exact wording at the moment.)I’ve burnt the day goooooogling, reading and playing with it to no avail. I am very grateful for any advice, Thank you! p.s. I'd also just like to comment on how bloody primitive dos' command line tools are :ThankFeral[edited by - FeralofFireTop on August 16, 2003 11:06:24 AM]
  Have you actully tried connecting to the modem?I don''t know if Linux drivers will work under FreeBSD even with the compatiblity layer running.Anways as root run ppp. and then type "term" at the ppp prompt. If ppp connects to the modem in terminal mode then you can issue modem commands. Try ATZ for reset. If none of this works edit /etc/ppp/ppp.conf. Inside you will find a line "set device /dev/cuaa0" change it to "set device /dev/cuaa1" and try the procdure until something hopefully works. If that dosen''t work try cuaa4.Also when you get into term on ppp typeing "~." will exit the term mode. Typing "quit" will exit ppp.;  I tried similar to that with pppd, the daemon never found the modem, but I''ll give it a shot with ppp might be enlightning to see the term output.Thanks for the input! ;WOOOT!  , WEEEEE!   and last but not least YAYAYAYAY!  yes well anyway...That did the trick! User PPP with modem on /dev/cuaa4 ... wierd, but I''m not complaining! (= (first time I''ve got anything other than windows on the net, I''m pleased as punch!)THANK YOU THANK YOU THANK YOU Clash Rocker! ;  No worries mate :-)I was also very excited when I first FreeBSD or something other Windows connected to the Internet :-)Anyways I found pppd far to hard to setup. In fact I never really setup ppp either. I would just switch to ttyv8 and run ppp term from there and connect.When I eventully ran KDE it came with a program KPPPD which used pppd with out any problems. ;  That is probably explains why kppp wasn''t working for me (as pppd does not seem to find the modem)... Interesting!I think I like your mehtod of going to a diff term to start ppp, I''ve been (since I want a graphical browser) going to kde and ppp -background papchap from a term window.Neat neat (= 