On 16-Apr-2000 Dirk Traulsen wrote:
Hello to all,
I would need some help to install my modem. I read all I could find, even a lot of mails in the archives of this list. Unfortunately none of these tips could help me. I'm a kind of newby and really at the end of my knowledge. So if you have an idea that possibly could help me....
Thanks a lot in advance Dirk
I'm running Suse Linux 6.1 with kernel 2.2.5 and try to use the modem SupraFaxModem288 from Supra Corporation at the serial port ttyS0. I have Win95 on the HD too and there I have no problems with the same modem at the same com1. It works fine. (Maybe first: it is no winmodem)
When I start minicom and try to initialize <ALT-M> the modem, minicom brings a popup-box telling <Initializing Modem>, but nothing happens.
I tried as root and normal user, both belonging to the groups uucp and dialout.
Then I tried to use wvdial. <wvdialconf /etc/wvdial.conf> as root should build a configuration file, but shows: ################################## Scanning your serial ports for a modem. Port Scan<*1>: S0 ... S7 Port Scan<*1>: S8 ... S15 Port Scan<*1>: S16 .. S23 Sorry, no modem was detected! Is it in use by another program? ##################################
When I understood the help file correctly, then if the modem would be in use by another program there should be a lock file in /var/lock, but there is none.
I checked that /dev/ttyS0 is 660.
After start-up I have a small problem: <setserial -g /dev/ttyS0> shows /dev/ttyS0, uart: unknown, port: 0x03f8, irq: 4 but when I tell him with <setserial -b /dev/ttyS0 uart 16550A> which uart I got, it shows /dev/ttyS0, uart: 16550A, port: 0x03f8, irq: 4 like it should.
I checked that ttyS0 doesn't use two interrupts with <cat /proc/interrupts>. But there wasn't even irq 4 mentioned (???), so blocking two interrupts doesn't seam probable.
The other thing to check if the serial ports are on the motherboard. Use command cat /proc/tty/driver/serial to list the serial devices. Extract from my machine shown below. merlin:/usr/local # cat /proc/tty/driver/serial serinfo:1.0 driver:4.27 0: uart:16550A port:3F8 irq:4 baud:2400 tx:8262180 rx:45660015 RTS|CTS|DTR|CD 1: uart:16550A port:2F8 irq:3 baud:115200 tx:16139617 rx:235581846 brk:11 oe:6 RTS|CTS|DTR|DSR|CD 2: uart:unknown port:3E8 irq:4 3: uart:unknown port:2E8 irq:3
Checking /var/log/messages showed some strange lines:
- I have no SCSI drive
- Module block-major-48/72??
In /etc/modules.conf make sure you have the following set # only used for Mylex or Compaq Raid as module alias block-major-48 off alias block-major-49 off alias block-major-72 off alias block-major-73 off # The serial devices should be set as follows alias char-major-4 serial alias char-major-5 serial
I don't know what this means and whether this has something to do with my modem problem. Maybe somebody can tell me what happens here.
[snip] Apr 12 19:32:16 Prometheus syslogd 1.3-3: restart. Apr 12 19:32:17 Prometheus kernel: klogd 1.3-3, log source = /proc/kmsg started. Apr 12 19:32:17 Prometheus kernel: Inspecting /boot/System.map Apr 12 19:32:18 Prometheus kernel: Loaded 8172 symbols from /boot/System.map. Apr 12 19:32:18 Prometheus kernel: Symbols match kernel version 2.2.5. Apr 12 19:32:18 Prometheus kernel: Loaded 7 symbols from 2 modules. Apr 12 19:32:18 Prometheus kernel: Serial driver version 4.27 with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ enabled Apr 12 19:32:21 Prometheus lpd[109]: restarted Apr 12 19:32:23 Prometheus /usr/sbin/cron[123]: (CRON) STARTUP (fork ok) Apr 12 19:42:43 Prometheus login[127]: ROOT LOGIN on `tty1' Apr 12 19:42:48 Prometheus insmod: /lib/modules/2.2.5/scsi/sd_mod.o: insmod block-major-8 failed Apr 12 19:42:48 Prometheus last message repeated 7 times Apr 12 19:42:48 Prometheus modprobe: modprobe: Can't locate module block-major-48 Apr 12 19:42:49 Prometheus last message repeated 7 times Apr 12 19:42:49 Prometheus modprobe: modprobe: Can't locate module block-major-72 Apr 12 19:42:49 Prometheus last message repeated 7 times Apr 12 19:42:49 Prometheus insmod: /lib/modules/2.2.5/scsi/sd_mod.o: insmod block-major-8 failed Apr 12 19:42:49 Prometheus last message repeated 7 times Apr 12 19:42:49 Prometheus modprobe: modprobe: Can't locate module block-major-48 Apr 12 19:42:49 Prometheus last message repeated 7 times Apr 12 19:42:49 Prometheus modprobe: modprobe: Can't locate module block-major-72 Apr 12 19:42:50 Prometheus last message repeated 7 times [snap]
Is there a possibility to send manually some kind of initstring to the modem to test the serial port? (I did a blind guess, not knowing what this really does: [echo 'ATZ' > /dev/ttyS0], but it didn't work)
If you read until here, thank you again. Bye.
The other thing you don't mention. Have you recompiled the kernel? Regards, Graham Smith ---------------------------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/