libc6 2.2-4
Hi, Does anyone know how can I find package libc6 version 2.2-4? Version 2.2-4 of libc6 is no longer available in unstable. Is there a general way to find older packages? I am investigating a possible break-in. Yes, I know, I should have run tripwire, but I didn't :(. Tomasz.
cannot talk with AT modem
Hi, I have just installed slink on my AMD Athlon PC. I have an internal USR 56K modem model 2977. It is not a winmodem, it uses Hayes AT language. Under Windows 98 it is recognized at COM5 and works fine. First problem was that in /dev there were only ttyS0-ttyS3 (COM1-COM4) with major number 4 and minor numbers 64-67. I have created by hand ttyS4-ttyS7 character devices with minor numbers 68-71, and same owner, group and permissions and ttyS0-ttyS3. I hope they correspond to COM5-COM8. However when I run minicom with /dev/ttyS4 I cannot talk to the modem. It does not respond to at, pressing enter, etc., no characters are echoed. wvdialconf scans my serial ports, finds active ports at ttyS0 and ttyS1 (COM1, COM@) with no modem there (it tries to send AT commands), then continues with port scan of ttyS2-ttyS7 without even attempting to send AT commands, i.e. I guess it did not find active serial ports there at all. Does anyone know what I can do? Tomasz.
Re: cannot talk with AT modem
Having the modem recognize the Hayes AT command language is not a reliable indicator. Many winmodem drivers have an AT command interpreter to satisfy older programs. When I bought the modem I was assured it is not a winmodem (software modem) but a hardware modem. I also searched the web and it seems it is not a winmodem. According to the USRobitics web site, this is a PCI modem device; are you able to open the case on your computer to verify that? Yes it is a PCI modem, I am sure of this. The contents of the file /proc/pci will also tell us if this is a PCI modem. I don't really understand output, but typing by hand what seems to be relevant: PCI devices found: Bus 0, device 11, function 0: Serial controller: Unknown vendor Unknown device (rev 1). Vendor id=12b9. Device id=1008. Medium devsel. IRQ 5. I/O at 0xd400 There are 5 more devices: Multimedia audio controller, vendor 1274(Ensoniq) device 5800 IDE interface, vendor 1022(AMD) device 7409 ISA bridge, vendor 1022 device 7408 PCI bridge, vendor 1022 device 7007 Host bridge, vendor 1022 device 7006 Tomasz.
Re: cannot talk with AT modem
Thank you. It worked. I can talk to the modem in minicom now. For the reference: I got IRQ and address number from Windows. The magic command was: setserial -v /dev/ttyS4 uart 16550A port 0xD400 irq 5 session_lockout ^fourport
Re: cannot talk with AT modem
Well, too soon to be happy. cron runs periodically rmmod -a . Then when I want to use the modem again serial driver is re-loaded: Serial driver version 4.13 with no serial options enabled tty00 at 0x03f8 (irq = 4) is a 16550A tty01 at 0x02f8 (irq = 3) is a 16550A And the modem is inaccessible again. setserial shows that /dev/ttyS4 reverted to original parameters. I have to run the setserial command manually again. How can I fix this? BTW I have added proper setserial command to /etc/rc.boot/0setserial as mentioned in the manpage. Tomasz.
