Linux-Setup Digest #378, Volume #19              Fri, 11 Aug 00 17:13:10 EDT

Contents:
  Trouble w/ppp and 2.2.16. (Eric DeFonso)
  Re: Sound card doesn't initialize (Opti 931) (Mr. Mister)
  Re: Trouble w/ppp and 2.2.16. (Naren Devaiah)
  Re: Sendmail (Naren Devaiah)
  Re: Sound card doesn't initialize (Opti 931) (Naren Devaiah)

----------------------------------------------------------------------------

From: [EMAIL PROTECTED] (Eric DeFonso)
Subject: Trouble w/ppp and 2.2.16.
Date: 11 Aug 2000 13:06:48 -0700


Hello all,

        I have problem for which I can't seem to find any helpful
documentation, so I hope someone here can point me in the right direction.
I am attempting to upgrade my kernel from2.0.36 to 2.2.16. I am able to
configure the new kernel just the way I want (for now, anyway), and to get
it and the modules to compile properly. I can boot up fine, but I cannot
seem to establish a proper ppp connection with my ISP under it anymore.
Here's what happens:

0) I operate ppp from a module, so I do insmod slhc, ppp.
1) In X, I launch ifup-ppp. I expect to hear the dialtone, but nothing
happens. I do a ps ax, and see this:

  706   1 S    0:00 sh /etc/sysconfig/network-scripts/ifup-ppp daemon ifcfg-ppp2
  713   1 S    0:00 /usr/sbin/pppd -detach lock modem crtscts defaultroute
  715   1 R    0:01 /sbin/modprobe -s -k ppp0 

pid 715 is usually the chat script. It hangs like this indefinitely. I
don't ever remember seeing modprobe doing anything under my old kernel
(which I obviously kept!). 

2) Anyway, after some experimentation, I found that if I ran 
kill -9 715 at the command line, the chat would actually start. It sounds
normal, and completes. Here is the transcript from
/var/log/messages:

Aug 11 12:12:11 debussy kernel: PPP: version 2.3.7 (demand dialling)
Aug 11 12:12:11 debussy kernel: PPP line discipline registered.
Aug 11 12:15:18 debussy ifup-ppp: pppd started for ppp2 on /dev/modem at 115200
Aug 11 12:15:50 debussy pppd[713]: pppd 2.3.5 started by root, uid 0
Aug 11 12:15:50 debussy kernel: registered device ppp0
Aug 11 12:15:51 debussy chat[717]: abort on (BUSY)
Aug 11 12:15:51 debussy chat[717]: abort on (ERROR)
Aug 11 12:15:51 debussy chat[717]: abort on (NO CARRIER)
Aug 11 12:15:51 debussy chat[717]: abort on (NO DIALTONE)
Aug 11 12:15:51 debussy chat[717]: abort on (Invalid Login)
Aug 11 12:15:51 debussy chat[717]: abort on (Login incorrect)
Aug 11 12:15:51 debussy chat[717]: send (AT&F1M1L1^M)
Aug 11 12:15:52 debussy chat[717]: expect (OK)
Aug 11 12:15:52 debussy chat[717]: AT&F1M1L1^M^M
Aug 11 12:15:52 debussy chat[717]: OK
Aug 11 12:15:52 debussy chat[717]:  -- got it 
Aug 11 12:15:52 debussy chat[717]: send (ATDT<phonenum>^M)
Aug 11 12:15:52 debussy chat[717]: expect (CONNECT)
Aug 11 12:15:52 debussy chat[717]: ^M
Aug 11 12:16:14 debussy chat[717]: ATDT<phonenum>^M^M
Aug 11 12:16:14 debussy chat[717]: CONNECT
Aug 11 12:16:14 debussy chat[717]:  -- got it 
Aug 11 12:16:14 debussy chat[717]: send (^M)
Aug 11 12:16:14 debussy pppd[713]: Serial connection established.
Aug 11 12:16:15 debussy pppd[713]: Using interface ppp0
Aug 11 12:16:15 debussy pppd[713]: Connect: ppp0 <--> /dev/modem
Aug 11 12:16:22 debussy pppd[713]: Remote message: Login Succeeded

Similar thing from ppplog:

Aug 11 12:15:18 debussy ifup-ppp: pppd started for ppp2 on /dev/modem at 115200
Aug 11 12:15:50 debussy pppd[713]: pppd 2.3.5 started by root, uid 0
Aug 11 12:16:14 debussy pppd[713]: Serial connection established.
Aug 11 12:16:15 debussy pppd[713]: Using interface ppp0
Aug 11 12:16:15 debussy pppd[713]: Connect: ppp0 <--> /dev/modem
Aug 11 12:16:15 debussy pppd[713]: sent [LCP ConfReq id=0x1 
  <magic 0x69945247> <pcomp> <accomp>]
Aug 11 12:16:18 debussy pppd[713]: sent [LCP ConfReq id=0x1 
  <magic 0x69945247> <pcomp> <accomp>]
Aug 11 12:16:18 debussy pppd[713]: rcvd [LCP ConfReq id=0x1 <asyncmap 0x0> 
  <magic 0x9a4de94c> <pcomp> <accomp> <auth pap>]
Aug 11 12:16:18 debussy pppd[713]: sent [LCP ConfAck id=0x1 <asyncmap 0x0> 
  <magic 0x9a4de94c> <pcomp> <accomp> <auth pap>]
Aug 11 12:16:21 debussy pppd[713]: sent [LCP ConfReq id=0x1 
  <magic 0x69945247> <pcomp> <accomp>]
Aug 11 12:16:21 debussy pppd[713]: rcvd [LCP ConfAck id=0x1 
  <magic 0x69945247> <pcomp> <accomp>]
Aug 11 12:16:21 debussy pppd[713]: sent [PAP AuthReq id=0x1 user="ericd" 
  password="<passwd>"]
Aug 11 12:16:22 debussy pppd[713]: rcvd [PAP AuthAck id=0x1 "Login Succeeded"]
Aug 11 12:16:22 debussy pppd[713]: Remote message: Login Succeeded
Aug 11 12:16:22 debussy pppd[713]: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> 
  <compress VJ 0f 01>]

However, the actual connection is never completely established. I still
cannot access mail or news or name  servers at this point. 
3) I do another ps aux and I see this:

732  1 R 0:11 /sbin/modprobe -s -k ppp-compress-21 

I have *no* idea what this is all about. There is no such module, or is
there?



4) Anyway, if I do kill -9 732, this is what I get from /var/log/messages.

Aug 11 12:20:15 debussy pppd[713]: write: warning: Input/output error(5)
Aug 11 12:20:15 debussy pppd[713]: Modem hangup
Aug 11 12:20:15 debussy pppd[713]: Connection terminated.
Aug 11 12:20:16 debussy pppd[713]: Exit.

That is, it terminates the "parent" process, 713.


5) Now, after all this, I can simply touch the Usernet ppp button (in X)
to attempt to reestablish the serial connection, which it tries.
Curiously, I don't have to kill any modprobe processes that probe ppp0.
But, it still hangs on a modprobe of ppp-compress-21.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Can anyone shed some light on why this is happening, and what I can do to
correct it? 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Here is the result of setserial, to show you where my modem is, etc.

root: /proc# setserial -a /dev/ttyS2
/dev/ttyS2, Line 2, UART: 16550A, Port: 0x03e8, IRQ: 5
        Baud_base: 115200, close_delay: 50, divisor: 0
        closing_wait: 3000, closing_wait2: infinte
        Flags: spd_vhi skip_test


This is the result of ifconfig, during my attempt to ppp in the bad
kernel.

root: /var/log# ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:18 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 

Here's what it looks like in the good kernel, when pppd is running.

root: /root# ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
          UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
          RX packets:18 errors:0 dropped:0 overruns:0 frame:0
          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 

ppp0      Link encap:Point-to-Point Protocol  
          inet addr:209.157.137.22  P-t-P:140.174.164.8 Mask:255.255.255.0
          UP POINTOPOINT RUNNING  MTU:1500  Metric:1
          RX packets:853 errors:1 dropped:1 overruns:0 frame:0
          TX packets:809 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 
          Memory:56c0038-56c0c04 


Here is the result of /proc/interrupts for the bad kernel. I notice that
IRQ 5, which is where the modem is, is missing.

root: /var/log# cat /proc/interrupts 
           CPU0       
  0:      73313          XT-PIC  timer
  1:       1213          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  8:          1          XT-PIC  rtc
 11:          0          XT-PIC  es1371
 12:      28470          XT-PIC  PS/2 Mouse
 13:          1          XT-PIC  fpu
 14:       5721          XT-PIC  ide0
 15:         10          XT-PIC  ide1
NMI:          0


And here's the good kernel.

root: /root# cat /proc/interrupts 
 0:     208269   timer
 1:      10182   keyboard
 2:          0   cascade
 5:      92962 + serial
 8:          1 + rtc
11:          0 + es1371
12:      19402   PS/2 Mouse
13:          1   math error
14:      63181 + ide0
15:         15 + ide1


If any other information is desired, just let me know. Thanks very much
for your time!


Eric


------------------------------

From: Mr. Mister <[EMAIL PROTECTED]>
Subject: Re: Sound card doesn't initialize (Opti 931)
Date: Fri, 11 Aug 2000 20:16:31 GMT

I've already generated the isapnp.conf file with isapnp. What seems to
be happening is that for whatever reason Linux doesn't init the card.
What would be helpful is if someone knows the steps that linux takes to
setup the pnp cards during system start. Then at least I could verify
each step.
Thanks


In article <[EMAIL PROTECTED]>,
  Naren Devaiah <[EMAIL PROTECTED]> wrote:
> use isapnp-tools to init the card.
>
> Modprobe loads the driver for you...It does not init the device...
> (please correct me if I am mistaken)
>
> -Naren
>
> "Mr. Mister" wrote:
>
> > It is plug and play actually.  I don't follow you regarding setting
the
> > IRQ.  The setup string(s) that modprobe uses in conf.modules has a
parm
> > in there for the IRQ already. Doesn't modprobe do the init?
> >
> > In article <[EMAIL PROTECTED]>,
> >   [EMAIL PROTECTED] wrote:
> > > On Wed, 09 Aug 2000 20:51:02 GMT, Mr. Mister <[EMAIL PROTECTED]>
> > > wrote:
> > >
> > > >My sound card only seems to work under Linux if I start the
computer
> > in
> > > >Windows first. If I do a cold boot directly into Linux the sound
card
> > > >doesn't work, i.e. cat /dev/sndstat gives an error rather than
the
> > nice
> > > >list of devices.  By the behavior is suspect that Windows is
> > > >initializing something on the card that Linux for some reason
isn't.
> > > >
> > > >I'm using Suse 6.2, the sound card is a a Sound Blaster
compatible
> > Bravo
> > > >card with the Opti 931 chip set.
> > >
> > > Maybe the card is P&P, so is waiting to receive the correct "init"
> > > for IRQ and DMA... try set the IRQ manually.
> > > Davide
> > >
> > >
> >
> > Sent via Deja.com http://www.deja.com/
> > Before you buy.
>
>


Sent via Deja.com http://www.deja.com/
Before you buy.

------------------------------

From: Naren Devaiah <[EMAIL PROTECTED]>
Subject: Re: Trouble w/ppp and 2.2.16.
Date: Fri, 11 Aug 2000 13:32:53 -0700

Enable the debug option in pppd and see if you can find what's happening.

If ppp-compress-21 is not present, you might try aliasing the bsd-comp.o module (or
softlinking bsd-comp.o as ppp-compress-21.o).

-Naren

Eric DeFonso wrote:

> Hello all,
>
>         I have problem for which I can't seem to find any helpful
> documentation, so I hope someone here can point me in the right direction.
> I am attempting to upgrade my kernel from2.0.36 to 2.2.16. I am able to
> configure the new kernel just the way I want (for now, anyway), and to get
> it and the modules to compile properly. I can boot up fine, but I cannot
> seem to establish a proper ppp connection with my ISP under it anymore.
> Here's what happens:
>
> 0) I operate ppp from a module, so I do insmod slhc, ppp.
> 1) In X, I launch ifup-ppp. I expect to hear the dialtone, but nothing
> happens. I do a ps ax, and see this:
>
>   706   1 S    0:00 sh /etc/sysconfig/network-scripts/ifup-ppp daemon ifcfg-ppp2
>   713   1 S    0:00 /usr/sbin/pppd -detach lock modem crtscts defaultroute
>   715   1 R    0:01 /sbin/modprobe -s -k ppp0
>
> pid 715 is usually the chat script. It hangs like this indefinitely. I
> don't ever remember seeing modprobe doing anything under my old kernel
> (which I obviously kept!).
>
> 2) Anyway, after some experimentation, I found that if I ran
> kill -9 715 at the command line, the chat would actually start. It sounds
> normal, and completes. Here is the transcript from
> /var/log/messages:
>
> Aug 11 12:12:11 debussy kernel: PPP: version 2.3.7 (demand dialling)
> Aug 11 12:12:11 debussy kernel: PPP line discipline registered.
> Aug 11 12:15:18 debussy ifup-ppp: pppd started for ppp2 on /dev/modem at 115200
> Aug 11 12:15:50 debussy pppd[713]: pppd 2.3.5 started by root, uid 0
> Aug 11 12:15:50 debussy kernel: registered device ppp0
> Aug 11 12:15:51 debussy chat[717]: abort on (BUSY)
> Aug 11 12:15:51 debussy chat[717]: abort on (ERROR)
> Aug 11 12:15:51 debussy chat[717]: abort on (NO CARRIER)
> Aug 11 12:15:51 debussy chat[717]: abort on (NO DIALTONE)
> Aug 11 12:15:51 debussy chat[717]: abort on (Invalid Login)
> Aug 11 12:15:51 debussy chat[717]: abort on (Login incorrect)
> Aug 11 12:15:51 debussy chat[717]: send (AT&F1M1L1^M)
> Aug 11 12:15:52 debussy chat[717]: expect (OK)
> Aug 11 12:15:52 debussy chat[717]: AT&F1M1L1^M^M
> Aug 11 12:15:52 debussy chat[717]: OK
> Aug 11 12:15:52 debussy chat[717]:  -- got it
> Aug 11 12:15:52 debussy chat[717]: send (ATDT<phonenum>^M)
> Aug 11 12:15:52 debussy chat[717]: expect (CONNECT)
> Aug 11 12:15:52 debussy chat[717]: ^M
> Aug 11 12:16:14 debussy chat[717]: ATDT<phonenum>^M^M
> Aug 11 12:16:14 debussy chat[717]: CONNECT
> Aug 11 12:16:14 debussy chat[717]:  -- got it
> Aug 11 12:16:14 debussy chat[717]: send (^M)
> Aug 11 12:16:14 debussy pppd[713]: Serial connection established.
> Aug 11 12:16:15 debussy pppd[713]: Using interface ppp0
> Aug 11 12:16:15 debussy pppd[713]: Connect: ppp0 <--> /dev/modem
> Aug 11 12:16:22 debussy pppd[713]: Remote message: Login Succeeded
>
> Similar thing from ppplog:
>
> Aug 11 12:15:18 debussy ifup-ppp: pppd started for ppp2 on /dev/modem at 115200
> Aug 11 12:15:50 debussy pppd[713]: pppd 2.3.5 started by root, uid 0
> Aug 11 12:16:14 debussy pppd[713]: Serial connection established.
> Aug 11 12:16:15 debussy pppd[713]: Using interface ppp0
> Aug 11 12:16:15 debussy pppd[713]: Connect: ppp0 <--> /dev/modem
> Aug 11 12:16:15 debussy pppd[713]: sent [LCP ConfReq id=0x1
>   <magic 0x69945247> <pcomp> <accomp>]
> Aug 11 12:16:18 debussy pppd[713]: sent [LCP ConfReq id=0x1
>   <magic 0x69945247> <pcomp> <accomp>]
> Aug 11 12:16:18 debussy pppd[713]: rcvd [LCP ConfReq id=0x1 <asyncmap 0x0>
>   <magic 0x9a4de94c> <pcomp> <accomp> <auth pap>]
> Aug 11 12:16:18 debussy pppd[713]: sent [LCP ConfAck id=0x1 <asyncmap 0x0>
>   <magic 0x9a4de94c> <pcomp> <accomp> <auth pap>]
> Aug 11 12:16:21 debussy pppd[713]: sent [LCP ConfReq id=0x1
>   <magic 0x69945247> <pcomp> <accomp>]
> Aug 11 12:16:21 debussy pppd[713]: rcvd [LCP ConfAck id=0x1
>   <magic 0x69945247> <pcomp> <accomp>]
> Aug 11 12:16:21 debussy pppd[713]: sent [PAP AuthReq id=0x1 user="ericd"
>   password="<passwd>"]
> Aug 11 12:16:22 debussy pppd[713]: rcvd [PAP AuthAck id=0x1 "Login Succeeded"]
> Aug 11 12:16:22 debussy pppd[713]: Remote message: Login Succeeded
> Aug 11 12:16:22 debussy pppd[713]: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0>
>   <compress VJ 0f 01>]
>
> However, the actual connection is never completely established. I still
> cannot access mail or news or name  servers at this point.
> 3) I do another ps aux and I see this:
>
> 732  1 R 0:11 /sbin/modprobe -s -k ppp-compress-21
>
> I have *no* idea what this is all about. There is no such module, or is
> there?
>
> 4) Anyway, if I do kill -9 732, this is what I get from /var/log/messages.
>
> Aug 11 12:20:15 debussy pppd[713]: write: warning: Input/output error(5)
> Aug 11 12:20:15 debussy pppd[713]: Modem hangup
> Aug 11 12:20:15 debussy pppd[713]: Connection terminated.
> Aug 11 12:20:16 debussy pppd[713]: Exit.
>
> That is, it terminates the "parent" process, 713.
>
> 5) Now, after all this, I can simply touch the Usernet ppp button (in X)
> to attempt to reestablish the serial connection, which it tries.
> Curiously, I don't have to kill any modprobe processes that probe ppp0.
> But, it still hangs on a modprobe of ppp-compress-21.
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Can anyone shed some light on why this is happening, and what I can do to
> correct it?
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Here is the result of setserial, to show you where my modem is, etc.
>
> root: /proc# setserial -a /dev/ttyS2
> /dev/ttyS2, Line 2, UART: 16550A, Port: 0x03e8, IRQ: 5
>         Baud_base: 115200, close_delay: 50, divisor: 0
>         closing_wait: 3000, closing_wait2: infinte
>         Flags: spd_vhi skip_test
>
> This is the result of ifconfig, during my attempt to ppp in the bad
> kernel.
>
> root: /var/log# ifconfig
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:3924  Metric:1
>           RX packets:18 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0
>
> Here's what it looks like in the good kernel, when pppd is running.
>
> root: /root# ifconfig
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
>           UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
>           RX packets:18 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0
>
> ppp0      Link encap:Point-to-Point Protocol
>           inet addr:209.157.137.22  P-t-P:140.174.164.8 Mask:255.255.255.0
>           UP POINTOPOINT RUNNING  MTU:1500  Metric:1
>           RX packets:853 errors:1 dropped:1 overruns:0 frame:0
>           TX packets:809 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0
>           Memory:56c0038-56c0c04
>
> Here is the result of /proc/interrupts for the bad kernel. I notice that
> IRQ 5, which is where the modem is, is missing.
>
> root: /var/log# cat /proc/interrupts
>            CPU0
>   0:      73313          XT-PIC  timer
>   1:       1213          XT-PIC  keyboard
>   2:          0          XT-PIC  cascade
>   8:          1          XT-PIC  rtc
>  11:          0          XT-PIC  es1371
>  12:      28470          XT-PIC  PS/2 Mouse
>  13:          1          XT-PIC  fpu
>  14:       5721          XT-PIC  ide0
>  15:         10          XT-PIC  ide1
> NMI:          0
>
> And here's the good kernel.
>
> root: /root# cat /proc/interrupts
>  0:     208269   timer
>  1:      10182   keyboard
>  2:          0   cascade
>  5:      92962 + serial
>  8:          1 + rtc
> 11:          0 + es1371
> 12:      19402   PS/2 Mouse
> 13:          1   math error
> 14:      63181 + ide0
> 15:         15 + ide1
>
> If any other information is desired, just let me know. Thanks very much
> for your time!
>
> Eric

--
Opinions expressed are my own an no one else's!



------------------------------

From: Naren Devaiah <[EMAIL PROTECTED]>
Subject: Re: Sendmail
Date: Fri, 11 Aug 2000 13:37:15 -0700

Sendmail uses TCP as it's transport. If your macs and pcs are not able to see
the linux box, install TCP/IP on them and try again. NetBEUI won't show the
linux box.

-Naren

Chris Wagner wrote:

> I am not familiar with Linux and have recently gotten involved with
> networking and administration. I have recently installed Caldera OpenLinux
> 2.4 on a Pentium MMX system and am wanting to setup this box to serve mail
> internally and for internet. I downloaded sendmail config options from
> support.calderasystems.com and followed the FAQ step by step, but it still
> does not work. The machine has its own unique IP set and all sendmail
> options are configured to use POP3(tcp) for the MTA. I created a dummy
> domain as suggested by Caldera for my local machine and pointed all systems
> on the network to this domain, though none of the systems can see the linux
> box. I have a peer-to-peer network with 4 macs and 5 pc's running PCMacLAN
> using NetBEUI. Does this have anything to do with the problem? I guess I was
> assuming that since the protocol being utilized by sendmail was not
> platform-dependent that if I set the protocol as default on the clients that
> it should have worked. I know sendmail is working locally on the box, as I
> can check users mailboxes, access new messages, etc. I just can't see others
> on the network.
>
> I apologize in advance for my lack of knowledge about networks. I am simply
> looking for a better and simpler setup to use pop3 mail internally and have
> gathered from many that sendmail is not easy at all to configure and deploy.
>
> Any suggestions are appreciated.
>
> Chris Wagner

--
Opinions expressed are my own an no one else's!



------------------------------

From: Naren Devaiah <[EMAIL PROTECTED]>
Subject: Re: Sound card doesn't initialize (Opti 931)
Date: Fri, 11 Aug 2000 13:44:22 -0700

FWIK Linux does nothing to initialise PnP devices (2.2.x have PnP code for
parallel ports but that's about it).

Once the isapnp.conf file is generated, you might have to edit it (if
required) and then during the boot process run isapnp with this cfg file to
actually initialize the card(s).

I am not sure about this, but isapnp should have a verbose option to show
what it is doing...
man isapnp should tell you this.

ISAPNP is the workhorse which you need to tame/ride...

-Naren

"Mr. Mister" wrote:

> I've already generated the isapnp.conf file with isapnp. What seems to
> be happening is that for whatever reason Linux doesn't init the card.
> What would be helpful is if someone knows the steps that linux takes to
> setup the pnp cards during system start. Then at least I could verify
> each step.
> Thanks
>
> In article <[EMAIL PROTECTED]>,
>   Naren Devaiah <[EMAIL PROTECTED]> wrote:
> > use isapnp-tools to init the card.
> >
> > Modprobe loads the driver for you...It does not init the device...
> > (please correct me if I am mistaken)
> >
> > -Naren
> >
> > "Mr. Mister" wrote:
> >
> > > It is plug and play actually.  I don't follow you regarding setting
> the
> > > IRQ.  The setup string(s) that modprobe uses in conf.modules has a
> parm
> > > in there for the IRQ already. Doesn't modprobe do the init?
> > >
> > > In article <[EMAIL PROTECTED]>,
> > >   [EMAIL PROTECTED] wrote:
> > > > On Wed, 09 Aug 2000 20:51:02 GMT, Mr. Mister <[EMAIL PROTECTED]>
> > > > wrote:
> > > >
> > > > >My sound card only seems to work under Linux if I start the
> computer
> > > in
> > > > >Windows first. If I do a cold boot directly into Linux the sound
> card
> > > > >doesn't work, i.e. cat /dev/sndstat gives an error rather than
> the
> > > nice
> > > > >list of devices.  By the behavior is suspect that Windows is
> > > > >initializing something on the card that Linux for some reason
> isn't.
> > > > >
> > > > >I'm using Suse 6.2, the sound card is a a Sound Blaster
> compatible
> > > Bravo
> > > > >card with the Opti 931 chip set.
> > > >
> > > > Maybe the card is P&P, so is waiting to receive the correct "init"
> > > > for IRQ and DMA... try set the IRQ manually.
> > > > Davide
> > > >
> > > >
> > >
> > > Sent via Deja.com http://www.deja.com/
> > > Before you buy.
> >
> >
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.

--
Opinions expressed are my own an no one else's!



------------------------------


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [EMAIL PROTECTED]

You can send mail to the entire list (and comp.os.linux.setup) via:

    Internet: [EMAIL PROTECTED]

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Setup Digest
******************************

Reply via email to