Yitzchak, Your modem should be easy to set up and supported by the serial drivers > The modem symbolic link is /dev/modem -> ttyS1 Fire up wvdial as root user # wvdialconf /etc/wvdial.conf should find /dev/ttyS1 and then configure your username, password and get up and running. Regards, Antonio --- Yitzchak Schaffer <yitzchas@xxxxxxxxx> wrote: > Hello all -- > > I'm setting up my system, and was hoping someone > could help me interpret the > following. Where can I find instrux on how to > config this thing? > > Thank you very much, > Y > > Only plain text email is forwarded by the > DISCUSS@xxxxxxxxxxxxx List > Server. > Do use the following as the email Subject Line: > SomeName, YourCountry > Welcome to kernel 2.4.33.3 > This will alert cogent experts, and distinguish > cases in the Archives. > YourCountry will enable Country Code guidance. > Occassionally responses are blocked by an Internet > Provider mail filters. > So in a day, also check the Archived responses at > http://www.linmodems.org > . > Local Linux experts can be found through: > http://www.linux.org/groups/index.html > -------------------------- System information > ---------------------------- > CPU=i686, > Welcome to > Linux version 2.4.33.3 (root@tree) (gcc version > 3.4.6) #1 Fri Sep 1 01:48:52 > CDT 2006 > scanModem update of: 2007_June_06 > The modem symbolic link is /dev/modem -> ttyS1 > > ALSAversion 1.0.11 > USB modem not detected by lsusb > > Modem or host audio card candidates have firmware > information: > > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 00:10.0 12b9:1008 12b9:00aa Serial controller: 3Com > Corp, Modem Division > 56K FaxModem Model 5610 > > Modem interrupt assignment and sharing: > 9: 0 XT-PIC usb-uhci > > --- Bootup diagnositcs for card in PCI slot 00:10.0 > ---- > PCI: Found IRQ 9 for device 00:10.0 > PCI: Sharing IRQ 9 with 00:10.0 > > === Finished modem firmware and bootup diagnostics > section. === > === Next deducing cogent software === > > For candidate modem in PCI bus: 00:10.0 > Class 0700: 12b9:1008 Serial controller: 3Com > Corp, Modem Division 56K > FaxModem Model 5610 > Primary PCI_id 12b9:1008 > Support type needed or chipset: USrobotics.serial > > > Vendor 10b7 3COM Inc. purchased the vendor 12b9 US > Robotics modem > technology. > Their winmodems have no Linux support. Their > controller chipset modems > are supported by the Linux serial drivers. > The PCI id 12b9:1008 modem is Supported. > > PCI ID Name > Support status > ---------------------------------------------------------------------------- > --- > 10b7:1006 3COM 0038TA AC101 - TF Mini-PCI winmodem, > not supported > 10b7:1007 3COM 3C556 V.90 Mini-PCI winmodem, not > supported > 12b9:1006 US Robotics 3cp803598 Voice winmodem, > not supported > 12b9:1007 US Robotics ERL3263A-0 DF GWPCI PC99 > winmodem, not supported > > 12b9:0062 US Robotics erk41926a-0.6 usr 56k serial > driver supported > 12b9:1008 US Robotics 3cp803598 > serial driver supported > wvdialconf wvtest , should detect the > modem. Read Testing.txt > ====== end 3COM section ======= > > Completed candidate modem analyses. > > A UDEV device file system is not active. > > Versions adequately match for the compiler > installed: 3.4.6 > and the compiler used in kernel > assembly: 3.4.6 > > > > Compiling resources appear complete: > make utility - /usr/bin/make > Compiler version 3.4 > kernel_headers base folder > /lib/modules/2.4.33.3/build > > > Checking pppd properties: > -rwxr-xr-x 1 root root 366440 2006-06-29 02:50 > /usr/sbin/pppd > > In case of an "error 17" "serial loopback" problem, > see: > > http://phep2.technion.ac.il/linmodems/archive-sixth/msg02637.html > > To enable dialout without Root permission do: > $ su - root (not for Ubuntu) > chmod a+x /usr/sbin/pppd > or under Ubuntu related Linuxes > chmod a+x /usr/sbin/pppd > > Checking settings of: /etc/ppp/options > asyncmap 0 > crtscts > lock > modem > proxyarp > lcp-echo-interval 30 > lcp-echo-failure 4 > > In case of a message like: > Warning: Could not modify /etc/ppp/pap-secrets: > Permission denied > see > http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html > > Read Modem/YourSystem.txt concerning other COMM > channels: eth0 > Which can interfere with Browser naviagation. > > Don't worry about the following, it is for the > experts > should trouble shooting be necessary. > ========================================================== > > Checking for modem support lines: > -------------------------------------- > /device/modem symbolic link: lrwxrwxrwx 1 > root root 5 2007-06-08 > 08:22 /dev/modem -> ttyS1 > slmodemd created symbolic link /dev/ttySL0: > Within /etc/udev/ files: > > Within /etc/modprobe.conf files: > /etc/modprobe.d/blacklist:# ALSA modules to support > sound modems. These > should be loaded manually > /etc/modprobe.d/blacklist:blacklist snd-atiixp-modem > /etc/modprobe.d/blacklist:blacklist > snd-via82xx-modem > Within any ancient /etc/devfs files: > > Within ancient kernel 2.4.n /etc/module.conf > files: > > --------- end modem support lines -------- > > > > ____________________________________________________________________________________ Get the free Yahoo! toolbar and rest assured with the added security of spyware protection. http://new.toolbar.yahoo.com/toolbar/features/norton/index.php
