Help! Kernel woes.

1999-04-15 Thread William R Pentney

I have tried recompiling a 2.2 kernel, and now I have two problems:

1) The new kernel isn't recognizing my network card. I used the PCI
NE2000 option; it worked before on a 2.0.34 kernel I compiled on a
floppy. Might I be missing an important option?

2) I still can't use sound. I have a SoundBlaster 16 PnP, and a look at
/dev/sndstat reveals that the driver is there, but it doesn't recognize
any audio devices.

Any suggestions?

- thanks, Bill


Re: Help! Kernel woes.

1999-04-15 Thread Arcady Genkin
William R Pentney [EMAIL PROTECTED] writes:

 I have tried recompiling a 2.2 kernel, and now I have two problems:
 
 1) The new kernel isn't recognizing my network card. I used the PCI
 NE2000 option; it worked before on a 2.0.34 kernel I compiled on a
 floppy. Might I be missing an important option?

Which card is it?
 
 2) I still can't use sound. I have a SoundBlaster 16 PnP, and a look at
 /dev/sndstat reveals that the driver is there, but it doesn't recognize
 any audio devices.

Did you compile it in kernel or as modules. I also have a SB16, and
found that it was a bit unobvious how to configure it in
menuconfig... Did you get to the step of specifying the DMA, IRQ
etc.etc.? Which driver did you chose? You should have chosen OSS sound 
modules AND 100% Sound Blastaer compatibles, and only then would
you have been revealed the possibility to enter I/O, IRQ etc.

Cheers,
-- 
Arcady Genkin
I opened up my wallet, and it's full of blood... - GsYDE


Re: Help! Kernel woes.

1999-04-15 Thread William R Pentney
On 15 Apr 1999, Arcady Genkin wrote:

 William R Pentney [EMAIL PROTECTED] writes:
 
  I have tried recompiling a 2.2 kernel, and now I have two problems:
  
  1) The new kernel isn't recognizing my network card. I used the PCI
  NE2000 option; it worked before on a 2.0.34 kernel I compiled on a
  floppy. Might I be missing an important option?
 
 Which card is it?
It is a Dayna PCI card, for 10baseT networks. I used the PCI NE2000 option
with success when I installed it. It also worked when I attempted to
install a 2.0.34 kernel (which unfortunately did not accept my
SoundBlaster 16 - it's a PnP, so I wanted to go for the 2.2 kernel that
has the PnP support.)

 Did you compile it in kernel or as modules. I also have a SB16, and
 found that it was a bit unobvious how to configure it in
 menuconfig... Did you get to the step of specifying the DMA, IRQ
 etc.etc.? Which driver did you chose? You should have chosen OSS sound 
 modules AND 100% Sound Blastaer compatibles, and only then would
 you have been revealed the possibility to enter I/O, IRQ etc.
Did all of that, and it was set up with correct IRQ and all, but I still
couldn't use /dev/audio. It is, as mentioned, a PnP. Should I use the
mysterious isapnptools package?

Thanks, Bill


Re: Help! Kernel woes.

1999-04-15 Thread Arcady Genkin
William R Pentney [EMAIL PROTECTED] writes:

 On 15 Apr 1999, Arcady Genkin wrote:

 It is a Dayna PCI card, for 10baseT networks. I used the PCI NE2000 option
 with success when I installed it. It also worked when I attempted to
 install a 2.0.34 kernel (which unfortunately did not accept my
 SoundBlaster 16 - it's a PnP, so I wanted to go for the 2.2 kernel that
 has the PnP support.)

Hmm. I am runnig 2.2.5 with NE2K PCI and Rtl8139 nics w/o
problems. You mention 2.0.34... Which version of Debian do you have?
Could it be that you need to upgrade some of the stuff on your system
in order to use 2.2.x? Have you checked against the compatibility
table?

 Did all of that, and it was set up with correct IRQ and all, but I still
 couldn't use /dev/audio. It is, as mentioned, a PnP. Should I use the
 mysterious isapnptools package?

Don't know. I usually turn off pnp feature on any piece of hardware
that I buy. Sorry, never used the isapnptools.

I had problems with /dev/audio and /dev/dsp untill I changed their
ownership to root.audio and added myself to audio group. Do you hear
the card initialize at the system startup? Does it produce a popping
noise? (mine does :))

Do you see any warning messages at startup saying that there's 
trouble with initializing the sound card? Here's what you should be
getting:

Apr 15 00:51:04 main kernel: Sound initialization started 
Apr 15 00:51:04 main kernel: Sound Blaster 16 (4.13) at 0x220 irq 7 dma 1,5 
Apr 15 00:51:04 main kernel: Sound Blaster 16 at 0x330 irq 7 dma 0 
Apr 15 00:51:04 main kernel: Sound initialization complete 

-- 
Arcady Genkin
I opened up my wallet, and it's full of blood... - GsYDE


Re: Help! Kernel woes.

1999-04-15 Thread Sean
William R Pentney wrote:


   I have tried recompiling a 2.2 kernel, and now I have two problems:
  
   1) The new kernel isn't recognizing my network card. I used the PCI
   NE2000 option; it worked before on a 2.0.34 kernel I compiled on a
   floppy. Might I be missing an important option?


Have you tried ifconfig?  The kernel might be supporting the card just fine, 
but the
card might not be turned on.  I'm running the 2.2.5 kernel on a slightly 
hacked
slink dist, and had to put the following lines into my /etc/init.d/network file:

ifconfig eth0 192.168.1.1
route add -net 192.168.1.0 netmask 255.255.255.0 dev eth0

I did not have to do this until I moved to the 2.2.x kernel, but it seems to 
work
just fine.



  Did you compile it in kernel or as modules. I also have a SB16, and
  found that it was a bit unobvious how to configure it in
  menuconfig... Did you get to the step of specifying the DMA, IRQ
  etc.etc.? Which driver did you chose? You should have chosen OSS sound
  modules AND 100% Sound Blastaer compatibles, and only then would
  you have been revealed the possibility to enter I/O, IRQ etc.
 Did all of that, and it was set up with correct IRQ and all, but I still
 couldn't use /dev/audio. It is, as mentioned, a PnP. Should I use the
 mysterious isapnptools package?

The only way I can ever get sound to work with soundblasters is to say M to 
sound,
but say Y to all the drivers (OSS sound modules, etc).  Please disregard if 
you've
already done this.

Sean

--
Adler's Distinction:
Language is all that separates us from the lower animals,
and from the bureaucrats.




Re: Help! Kernel woes.

1999-04-15 Thread Stephen Pitts
On Thu, Apr 15, 1999 at 01:43:29AM -0400, William R Pentney wrote:
  Did you compile it in kernel or as modules. I also have a SB16, and
  found that it was a bit unobvious how to configure it in
  menuconfig... Did you get to the step of specifying the DMA, IRQ
  etc.etc.? Which driver did you chose? You should have chosen OSS sound 
  modules AND 100% Sound Blastaer compatibles, and only then would
  you have been revealed the possibility to enter I/O, IRQ etc.
 Did all of that, and it was set up with correct IRQ and all, but I still
 couldn't use /dev/audio. It is, as mentioned, a PnP. Should I use the
 mysterious isapnptools package?
 
 Thanks, Bill

Yep, that's how I've had to use it. Get the isapnptools package and
run pnpdump  /etc/isapnp.conf. Then go into isapnp.conf and uncomment
the lines specifying the configuration settings that you want. It is
a little confusing, so I've included the uncommented portion of my file
below. After that run isapnp /etc/isapnp.conf. It should give you some
sort of affirmative message.
-- 
Stephen Pitts
[EMAIL PROTECTED]
webmaster - http://www.mschess.org

(READPORT 0x0203)
(ISOLATE PRESERVE)
(IDENTIFY *)
(VERBOSITY 2)
(CONFLICT (IO FATAL)(IRQ FATAL)(DMA FATAL)(MEM FATAL)) # or WARNING


(CONFIGURE CTL00f0/-1 (LD 0


(INT 0 (IRQ 5 (MODE +E)))
(DMA 0 (CHANNEL 1))
(DMA 1 (CHANNEL 3))
(IO 0 (SIZE 16) (BASE 0x0220))
(IO 1 (SIZE 2) (BASE 0x0330))
(IO 2 (SIZE 4) (BASE 0x0388))





 (NAME CTL00f0/-1[0]{Audio   })

(ACT Y)
))

(CONFIGURE CTL00f0/-1 (LD 1


(IO 0 (SIZE 1) (BASE 0x0201))

 (NAME CTL00f0/-1[1]{Game})

(ACT Y)
))

(WAITFORKEY)


RE: Help! Kernel woes. -- SoundBlaster

1999-04-15 Thread Jonathan J. Lupa
Hello!

I just went through this fight with my AWE32... there are some docs out there 
that will really help.
For reference: zless /usr/doc/HOWTO/Sound-HOWTO.gz
And the big gun: zless /usr/doc/HOWTO/mini/Soundblaster-AWE.gz

All the stuff in there about ISA PnP should apply. ( I'm not sure how kernel 
2.2 resolves the module loading before PnP devices are configured thing, so 
this may not apply if you are on a 2.2.* system)

The only other pointer that I can give is that in /etc/isapnp.conf should be a 
default line of
(ISOLATE PRESERVE).
to get mine to work I had to change that line to
(ISOLATE CLEAR)

From what I can divine from the documentation, that resets the PnP hardware 
settings... I'm sure there is someone more knowledgeable than I for that kind 
of explanation. Of course, YMMV...

~
-Jonathan
[EMAIL PROTECTED]
Senior Programmer -- Creative Solutions Inc.

On Thursday, April 15, 1999 5:24 PM, Stephen Pitts 
[SMTP:[EMAIL PROTECTED] wrote:
 On Thu, Apr 15, 1999 at 01:43:29AM -0400, William R Pentney wrote:
   Did you compile it in kernel or as modules. I also have a SB16, and
   found that it was a bit unobvious how to configure it in
   menuconfig... Did you get to the step of specifying the DMA, IRQ
   etc.etc.? Which driver did you chose? You should have chosen OSS sound
   modules AND 100% Sound Blastaer compatibles, and only then would
   you have been revealed the possibility to enter I/O, IRQ etc.
  Did all of that, and it was set up with correct IRQ and all, but I still
  couldn't use /dev/audio. It is, as mentioned, a PnP. Should I use the
  mysterious isapnptools package?
 
  Thanks, Bill

 Yep, that's how I've had to use it. Get the isapnptools package and
 run pnpdump  /etc/isapnp.conf. Then go into isapnp.conf and uncomment
 the lines specifying the configuration settings that you want. It is
 a little confusing, so I've included the uncommented portion of my file
 below. After that run isapnp /etc/isapnp.conf. It should give you some
 sort of affirmative message.
 --
 Stephen Pitts
 [EMAIL PROTECTED]
 webmaster - http://www.mschess.org
   File: myisapnp.txt 



Re: Help! Kernel woes. -- SoundBlaster

1999-04-15 Thread Richard Harran
This link from Marcus Brinkmann helped me a lot when I did my
soundblaster setup: it's nice and easy to follow:

http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/soundblaster.html

(hope he doesn't mind me posting his ref.)

HTH
Rich

Jonathan J. Lupa wrote:
 
 Hello!
 
 I just went through this fight with my AWE32... there are some docs out there
 that will really help.
 For reference: zless /usr/doc/HOWTO/Sound-HOWTO.gz
 And the big gun: zless /usr/doc/HOWTO/mini/Soundblaster-AWE.gz
 
 All the stuff in there about ISA PnP should apply. ( I'm not sure how kernel
 2.2 resolves the module loading before PnP devices are configured thing, so
 this may not apply if you are on a 2.2.* system)
 
 The only other pointer that I can give is that in /etc/isapnp.conf should be a
 default line of
 (ISOLATE PRESERVE).
 to get mine to work I had to change that line to
 (ISOLATE CLEAR)
 
 From what I can divine from the documentation, that resets the PnP hardware
 settings... I'm sure there is someone more knowledgeable than I for that kind
 of explanation. Of course, YMMV...
 
 ~
 -Jonathan
 [EMAIL PROTECTED]
 Senior Programmer -- Creative Solutions Inc.
 
 On Thursday, April 15, 1999 5:24 PM, Stephen Pitts
 [SMTP:[EMAIL PROTECTED] wrote:
  On Thu, Apr 15, 1999 at 01:43:29AM -0400, William R Pentney wrote:
Did you compile it in kernel or as modules. I also have a SB16, and
found that it was a bit unobvious how to configure it in
menuconfig... Did you get to the step of specifying the DMA, IRQ
etc.etc.? Which driver did you chose? You should have chosen OSS sound
modules AND 100% Sound Blastaer compatibles, and only then would
you have been revealed the possibility to enter I/O, IRQ etc.
   Did all of that, and it was set up with correct IRQ and all, but I still
   couldn't use /dev/audio. It is, as mentioned, a PnP. Should I use the
   mysterious isapnptools package?
  
   Thanks, Bill
 
  Yep, that's how I've had to use it. Get the isapnptools package and
  run pnpdump  /etc/isapnp.conf. Then go into isapnp.conf and uncomment
  the lines specifying the configuration settings that you want. It is
  a little confusing, so I've included the uncommented portion of my file
  below. After that run isapnp /etc/isapnp.conf. It should give you some
  sort of affirmative message.
  --
  Stephen Pitts
  [EMAIL PROTECTED]
  webmaster - http://www.mschess.org
File: myisapnp.txt 
 
 --
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null