On Sun, 1 Oct 2000, Christopher Susi wrote: cs> I am running 6.4 and recently added a SoundBlaster 16 (Actually it is a cs> SB16-SCSI2, but I'm not going to use the SCSI port). It seems that this and cs> my NIC (a 3C509B) share the same IRQ (5). cs> cs> On a Win98 partition this was easy to work around by setting the IRQ for the cs> SB to 7 from autoexec.bat, however it looks like it's not a persistent cs> change (so when I reboot in Linux the IRQ is 5 again, causing a conflict). cs> How can I configure this properly in Linux? I'd prefer to get the SB16 cs> working and change it's IRQ to 7 rather than the NIC (so that it's the same cs> setup as the Win98 boot). YAST2 is puking when I put in these settings cs> (though I may very well be doing something wrong). I'd prefer to modify the cs> configuration files directly though for the sound card (rather than using a cs> setup-program) so I can further my understanding of Linux's guts and cs> settings. Any suggestions or places to look for help? cs> You can change it with menuconfig or xconfig when your compiling the kernel with sound support built into the kernel, or if as a module, you can change the line within the conf.modules file from options sb io=0x220 irq=5 dma=1 dma16=5 mpu_io=0x330 to options sb io=0x220 irq=7 dma=1 dma16=5 mpu_io=0x330 I'd recommend compiling it as a module as well as with the scsi portion as it will allow you to use the scsi if you need to or not, but it's there if you do. Just be sure if you do compile the scsi as a module and you happen to need it at bootup that the aha152x is part of the initrd file. Best of luck to you. cs> cs> -- S.Toms - tomas@primenet.com - www.primenet.com/~tomas SuSE Linux v7.0+ - Kernel 2.2.17 Time flies like an arrow, but fruit flies like a banana. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq