A little progress with my modem. It turns out that I had the wrong kernel source. I have now recompiled and installed the modem with the correct kernel source (I believe):
$ /sbin/modprobe -l | grep slamrmo /lib/modules/2.4.22-10mdk/misc/slamrmo.o $ /sbin/lsmod | grep sl slamrmo 282052 0 (autoclean) slmdm 1292480 0 (autoclean) [slamrmo] slhc 6564 0 [ppp_generic] $ ls -l /dev/modem lr-xr-xr-x 1 root root 8 May 12 22:44 /dev/modem -> ./ttySL0 $ ls -l /dev/ttySL0 crw-rw-rw- 1 root root 212, 0 May 12 22:58 /dev/ttySL0 So far so good. 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 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 [Lots of empty lines] CTRL-A Z for help | 38400 8N1 | NOR | Minicom 2.1 | VT102 | Offline What now? What can I do in minicom to see whether the modem is there? Douglas. Douglas Royds wrote: >Here's the output of lsmod: > > [snip - there was no slamrmo] >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". > > [snip] >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? >> >> >> >> >> > > > > >
