Here's the output of lsmod: Module Size Used by Not tainted scsimon 9312 0 (unused) usb-storage 91616 1 sg 35068 0 (autoclean) (unused) st 30680 0 (autoclean) (unused) sr_mod 19384 0 (autoclean) (unused) sd_mod 13804 2 (autoclean) scsi_mod 106176 6 (autoclean) [scsimon usb-storage sg st sr_mod sd_mod] snd-seq-midi 5056 0 (autoclean) (unused) snd-trident-synth 9356 1 (autoclean) snd-seq-instr 7204 0 (autoclean) [snd-trident-synth] snd-ainstr-simple 3384 0 (autoclean) [snd-trident-synth] snd-seq-midi-emul 6924 0 (autoclean) [snd-trident-synth] snd-seq-oss 32000 0 (unused) snd-seq-midi-event 6080 0 [snd-seq-midi snd-seq-oss] snd-seq 42544 3 [snd-seq-midi snd-trident-synth snd-seq-instr snd-seq-midi-emul snd-seq-oss snd-seq-midi-event] snd-pcm-oss 43652 1 snd-mixer-oss 14200 0 [snd-pcm-oss] snd-trident 32900 1 [snd-trident-synth] snd-util-mem 3040 0 [snd-trident] snd-pcm 79588 0 [snd-pcm-oss snd-trident] snd-timer 18436 0 [snd-seq snd-pcm] gameport 3268 0 [snd-trident] snd-mpu401-uart 4704 0 [snd-trident] snd-rawmidi 17760 0 [snd-seq-midi snd-mpu401-uart] snd-seq-device 5832 0 [snd-seq-midi snd-trident-synth snd-seq-oss snd-seq snd-trident snd-rawmidi] snd-page-alloc 9044 0 [snd-trident-synth snd-trident snd-pcm] snd-ac97-codec 45720 0 [snd-trident] snd 41380 0 [snd-seq-midi snd-seq-instr snd-seq-oss snd-seq-midi-event snd-seq snd-pcm-oss snd-mixer-oss snd-trident snd-util-mem snd-pcm snd-timer snd-mpu401-uart snd-rawmidi snd-seq-device snd-ac97-codec] soundcore 6340 0 [snd] ds 8500 2 yenta_socket 13088 2 pcmcia_core 57696 0 [ds yenta_socket] ppp_async 9312 0 (unused) ppp_generic 24292 0 [ppp_async] slhc 6564 0 [ppp_generic] af_packet 14856 0 (autoclean) ide-floppy 16128 0 (autoclean) ide-tape 48816 0 (autoclean) ide-cd 33956 0 (autoclean) cdrom 32608 0 (autoclean) [sr_mod ide-cd] floppy 55932 0 ntfs 77292 1 (autoclean) nls_iso8859-15 4060 3 (autoclean) nls_cp850 4284 2 (autoclean) vfat 11820 2 (autoclean) fat 38040 0 (autoclean) [vfat] supermount 84032 3 (autoclean) usb-ohci 21080 0 (unused) usbcore 74988 1 [usb-storage usb-ohci] rtc 9004 0 (autoclean) ext3 60048 2 jbd 39264 2 [ext3]
Does anything there look like a modem? Here's the output of lspci -vv, abridged: 00:01.6 Modem: Silicon Integrated Systems [SiS] Intel 537 [56k Winmodem] (rev a0) (prog-if 00 [Generic]) Subsystem: Unknown device 1631:3005 Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Interrupt: pin C routed to IRQ 11 Region 0: I/O ports at 1400 [size=256] Region 1: I/O ports at 1800 [size=128] Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0-,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- The driver that I have compiled is 2.7.14, the "latest stable". The readme file for the modem says that: After successful installation and configuration modules will be loaded on demand if you are using 'kmod' in linux kernel. Also you can load modules by hand: # modprobe slamrmo How do I know whether I'm using "kmod" in the linux kernel? The modprobe command complained that it couldn't find the module "slamrmo". I ran minicom -s as root. After asking me (again) for a whole lot of info that I couldn't really provide, it declared that it was "initialising modem", then popped up a screen that said: Welcome to minicom 2.1 OPTIONS: History Buffer, F-key Macros, Search History Buffer, I18n Compiled on Jun 15 2003, 14:35:38. Press CTRL-A Z for help on special keys and along the bottom of the screen: CTRL-A Z for help | 38400 8N1 | NOR | Minicom 2.1 | VT102 | Offline What now? Thanks, Douglas. Christopher Sawtell wrote: >On Thursday 22 April 2004 16:58, Douglas Royds wrote: > > >>The winmodem driver is by Smart Link, www.smlink.com. The readme file >>said that the installation would: >> >> - create character tty device entry '/dev/ttySL0' with major >> number 212 and symbolic link 'dev/modem'. >> - config you '/etc/modules.conf' file in order to provide >> possibility for loading the modem modules into kernel on demand >> automatically by kmod, when you are going to use them. >> >>I tried lsmod, but got: "bash: lsmod: command not found". Surprising, >>seeing there is a man page for it. I guess it isn't in my path, so where >>is it? Here's my path: >> >> >/sbin/lsmod > > > >>PATH=/bin:/usr/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/local/bin:/opt/X11R6/bi >>n:/usr/bin:/usr/games:/home/douglas/bin >> >> > > > >>Here're the /dev/modem symbolic link, and the ttySL0 device: >> >>lr-xr-xr-x 1 root root 8 Apr 21 2004 /dev/modem -> >>./ttySL0 >>crw-rw---- 1 douglas tty 212, 0 Apr 21 2004 /dev/ttySL0 >> >>Does my name in the /dev/ttySL0 entry mean that I'm the owner? >> >> >yes, > > > >>00:00.0 Host bridge: Silicon Integrated Systems [SiS] 630 Host (rev 31) >>00:00.1 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) >>00:01.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 >>00:01.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 >>Controller (rev 07) >>00:01.4 Multimedia audio controller: Silicon Integrated Systems [SiS] >>SiS PCI Audio Accelerator (rev 02) >>00:01.6 Modem: Silicon Integrated Systems [SiS] Intel 537 [56k Winmodem] >>(rev a0) >>00:02.0 PCI bridge: Silicon Integrated Systems [SiS] SiS 530 Virtual >>PCI-to-PCI bridge (AGP) >>00:08.0 CardBus bridge: Texas Instruments PCI1225 (rev 01) >>00:08.1 CardBus bridge: Texas Instruments PCI1225 (rev 01) >>01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] >>SiS630 GUI Accelerator+3D (rev 31) >>How do you find out who the group is? >> >> >the group owner is the word to the immediate right of your name, >i.e. the tty group. > > > > >>Here's what lspci had to say: >> >> >I wonder if you could do it with the -vv flag as root so we have all the >details. > >$ su >Password: > ># lspci -vv > >and post the bit about the modem. > > > > >>And more specifically, from /proc/pci: >> >>00:01.6 Modem: Silicon Integrated Systems [SiS] Intel 537 [56k Winmodem] >>(rev a0) (prog-if 00 [Generic]) >> Subsystem: Unknown device 1631:3005 >> Flags: medium devsel, IRQ 11 >> I/O ports at 1400 [size=256] >> I/O ports at 1800 [size=128] >> Capabilities: <available only to root> >> >> >It might well be interesting to do this as root. > > > >>rpm -q ppp: >> ppp-2.4.1-12mdk >> >>kppp is not installed, though I could probably do so off the M9.2 disks. >>Should I do this? I'm guessing the "k" refers to KDE, which I don't have >>installed. >> >> >In that case don't install kppp just yet. Doing so will load up all sorts of >KDE libraries as well. That may or may now be what you want. > > > >>Just installed minicom. I seem to have to run this as root. It said >>"Initialising modem", then popped up its terminal screen, and I made no >>further progress. What next? Typing atz had no visible effect. >> >> >You have to configure minicom to 'talk' to your modem. Do this as the 'root' >user with the -s option flag:- > >minicom -s > > >It would appear that this is the latest stable driver:- > >ftp://ftp.smlink.com/linux/unsupported/slmdm-2.7.14.tar.gz >Which is mirrored locally at:- >ftp://ftp2.jetstreamgames.co.nz/pub/dist/gentoo/distfiles/slmdm-2.7.14.tar.gz > >And this is the beta one:- > >ftp://ftp.smlink.com/linux/unsupported/slmodem-2.9.6.tar.gz > >Have you got the correct and latest driver? > >Geographically, where is this recalcitrant modem situated? > > >
