On Mon, 8 Feb 1999, Ray Olszewski wrote:

> If PnP is assigning the modem to IRQ 10, then what /dev/ttyS* entry are you
> using? Offhand, I don't know one that is set up for IRQ 10 (and what IO
> ports is it assigning, I wonder).

I assigned /dev/ttyS2, but didn't worked

> Basically, you need to add in these steps:
> 
> 1. Find out what IO ports the new modem is using. Look for this in
> /proc/ioports (I think - I may have the name a bit off).

when I do cat /proc/ioports, I get:
0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
0170-0177 : ide1
01f0-01f7 : ide0
0220-022f : soundblaster
02e8-02ef : serial(set)
02f8-02ff : serial(auto)
0376-0376 : ide1
0388-038b : Yamaha OPL3
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(auto)
f000-f007 : ide0
f008-f00f : ide1

> 2. Just in case, make sure IRQ 10 isn't a conflict (some NICs use IRQ 10).
> Check in /proc/interrupts as before.

it doesn't show something releated to IRQ 10, I have:
           CPU0
  0:    1229267          XT-PIC  timer
  1:      48778          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  4:      11089          XT-PIC  serial
  5:    4478403          XT-PIC  soundblaster
 13:          1          XT-PIC  fpu
 14:       9757          XT-PIC  ide0
 15:      67102          XT-PIC  ide1
NMI:          0
ERR:          0


> 3. Use setserial to set some otherwise unused /dev/ttyS* entry to the
> appropriate IRQ and IOport address: e.g., "setserial /dev/ttyS12 irq 10 port
> xxx", replacing "xxx" with the appropriate starting IO port address you
> found in step 1.

when I do cat /proc/pci I get:
  Bus  0, device  10, function  0:
    Communication controller: Unknown vendor Unknown device (rev 1).
      Vendor id=127a. Device id=2015.
      Medium devsel.  Fast back-to-back capable.  IRQ 10.  Master Capable.
Latency=64.
      Non-prefetchable 32 bit memory at 0xe6000000 [0xe6000000].
      I/O at 0xe400 [0xe401].


> 4. Use setserial to probe the dev you set up in step 3 (e.g., "setserial
> /dev/ttyS12") and see if it returns a UART type. If it did, you should be
> set. If it didn't, somethign went wrong, either with these amended
> instructions or the originals.
> 
ok I typed it and got:
[root@megatron /root]# setserial /dev/ttyS12 irq 10 port 0xe400
/dev/ttyS12: Operation not supported by device
[root@megatron /root]#

Previously I typed: mknod --mode=644 ttyS12 c 4 68

> 5. symlink /dev/modem to the S* you configured in step 3.

I couldn't do that because first we have to get the /dev/ttyS* running,
I'm wrong?

> 6. See if it works.

sniff... it doesn't works. :-(

> If you do need to post again, please include the make, model, and FCC ID (s
> sticker on the board somewhere) of your modem.

ok, I have:
Make: Maxsenger (?)
Model: DM-56V14HSF/2
Manufacturer: Aceex Corp.
FCC: I can't find it, but maybe it's: 98100028767, it also has bar codes.

by the way, I have to modify something in my BIOS configuration?

Thanks
David

Reply via email to