[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: My sb16 pnp, isdn avm-fritz! pci card



Hey !
1. My sb card is ISA card as my sb16 manual telling me. I recompiled the sb
support as
    module and I tried the parameters that he wrote (I/O=220, IRQ=5, DMA1=1,
DMA2=3)
    and i couldn't hear the sample.
    how do i fixing it?
2. I d/led the isdn-2.tar.gz (or something like this), and installed it from
avm's ftp.
    when i running the script, he writes me that the connection already
active.
    How do i fixing it?

bye, waiting for your answer.



Lior Okman wrote:

> On Mon, 11 Jan 1999, - wrote:
>
> > First, Thank you for helping me.
> > 1. About the SB16, The device driver isn't loaded (sb16) here is the list
> > of all other devices:
> > slhc               2            0 (autoclean)
> > nls_iso8859_1      1            2 (autoclean)
> > nls_cp437          1            2 (autoclean)
> > vfat               4            2 (autoclean)
> > opl3               3            0
> > uart401            2            0
> > sound             15    [opl3 uart401]  0
> > soundlow           1    [sound] 0
> > soundcore          1    [sound] 3
> >   As you can see, sb16/sb isn't there. And about sndconfig - when i
> > running it on port 240 - "device
> > or resource busy" and when i trying other ports (220 for example)
> > it accept it - but no sound !!!
> > When i compiled the kernel i told him to compile the sound as
> > bulit in driver, with the 220 port.
> > what can I do?
>
> First of all, lets make a few things obvious:
> 1. If your card is an ISA PnP card, it will not work if you compile it
> into the kernel. In other words, you must compile it as a module.
> 2. If it isn't and ISA PnP card, but say a PCI PnP card it will work if
> not compiled as a module.
> 3. SndConfig assumes that you compiled it as a module and will not work
> for you if you compiled it into the kernel (as the parameters it controls
> are all compiled into the kernel). The "work" that sndconfig does is this:
>    a. Get your idea of the cards parameters : port,irq,dma & high dma
>    b. Edit the file /etc/conf.modules and add appropriate lines there.
>    c. modprobe the card for you once.
> therefore:
>  1.If your card is an ISA PnP card, make sure that the parameters that you
>    initialize your card with are the same as the ones you try to use.
>    Typically, if you used isapnptools, the isapnp configuration file is
>    /etc/isapnp.conf , and you should check it out. You can't just try any
>    port you feel like.
>  2.If your card is a PCI PnP card, the bios and kernel take care of
>    initializing the card. You just have to find out which IRQ's have been
>    assigned. I don't think (read "I am not sure") that there are any PCI
>    SB cards (Creative have their Ensonic card series). You can find out
>    which IRQ's are used in one of two methods: Use pciutils (lspci) or
>    just simply `cat /proc/pci` and find the correct card (Should be
>    obvious)
>
> 4. If you compiled the driver as a module, you should modprobe it into the
> kernel before you want to use it (or let the kernel automatically insmod
> it , read the Modules-HOWTO) You don't need to sndconfig it everytime.
> 5. If you compile it into the kernel (IMPOSSIBLE for ISA PnP cards, the
> card isn't initialized when the kernel tries to initialize the driver)
> then the card should work whenever you try to use it, and you don't need
> sndconfig because it won't work anyways.
>
> BTW: All this is explained in the Sound-HOWTO. Next time, try to RTFM.
>
> > 2. About the isdn :
> >     First, i still think that the kernel 2.0.36 support it (its on
> > the configuration menu -
> >     AVM FRITZ! pci/pnp, but i'll download the drivers.
>
> The 2.0.36 kernel supports Fritz! card (AVM A1) as in the not PnP/PCI card
> variaty, and expects you to specify all sorts of parameters that the PCI
> card does not want. When you get the drivers, you'll see the new addition
> in the list. There is specific support for the PCI/PnP card. That's what
> you need.
>
> >     My problem was about the configuration scripts for my pppd, and i'll
> >     try your solve.
> You don't want to use pppd with isdn. You want to use ipppd.
>
> >     I'm downloading now the drivers, but because of my 3 tests tomorrow,
> >     so I won't try it today.
>
> Good luck.
>
> Lior Okman
> lior@hempseed.com