Configuring Soundblaster 16/AWE 32 ISA Card in v7.1
Thanks to all who helped me configure X 4.0.2 and the login via KDM. I have another problem which doesn't seem to be totally resolved by any of the online sources I've looked at so far. I'm sure it's a FAQ, but I haven't found the solution as of yet. In its prior configurations (as first a Caldera box and then, a Mandrake 7.2 box), I have able to get my Soundblaster 16/AWE 32 compatible ISA sound card to work. Caldera detected it during install, while in Mandrake, I had to run sndconfig (or something like that) from a terminal to set it up. The configuration through YAST2 does not work in my particular situation. However, I think this is due to some other underlying problem. First of all, I installed the system via an FTP installation, so if I'm missing any modules, etc., I could use some instruction as how to go through the system to "grab" the appropriate packages. For example, at login, xconsole launches (don't know if this happens by default or not). Three messages come up: modprobe: modprobe: Can't locate module sound-slot-0 modprobe: modprobe: Can't locate module sound-service-0-0 modprobe: modprobe: Can't locate module snd-card-0 If I run the sound card config through Y AST2, I do the following: Start ALSA and Start sequencer are checked (default) I then click on "Add soundcard" and select Soundblaster 16 I then get the message: "An error occured during installing: The kernal module snd-card-sb16 for sound support could not be loaded." I also get admonished to make sure that ALSA is correctly installed (something of which I am not aware of a way to check). It also suggests potentially trying OS/Free or another module. Any suggestions or links to helpful sites appreciated. Greg Lentz
Greg Lentz wrote:
In its prior configurations (as first a Caldera box and then, a Mandrake 7.2 box), I have able to get my Soundblaster 16/AWE 32 compatible ISA sound card to work. Caldera detected it during install, while in Mandrake, I had to run sndconfig (or something like that) from a terminal to set it up.
The configuration through YAST2 does not work in my particular situation. However, I think this is due to some other underlying problem.
First of all, I installed the system via an FTP installation, so if I'm missing any modules, etc., I could use some instruction as how to go through the system to "grab" the appropriate packages.
For example, at login, xconsole launches (don't know if this happens by default or not). Three messages come up:
modprobe: modprobe: Can't locate module sound-slot-0 modprobe: modprobe: Can't locate module sound-service-0-0 modprobe: modprobe: Can't locate module snd-card-0
If I run the sound card config through Y AST2, I do the following:
Start ALSA and Start sequencer are checked (default) I then click on "Add soundcard" and select Soundblaster 16
I then get the message:
"An error occured during installing: The kernal module snd-card-sb16 for sound support could not be loaded." I also get admonished to make sure that ALSA is correctly installed (something of which I am not aware of a way to check). It also suggests potentially trying OS/Free or another module.
Funnily enough, I just compiled and installed the latest ALSA yesterday. As root, try doing a 'modprobe snd-card-sb16' and see what the output is. My guess is that since this is an ISA sound card, the IO/IRQ are not set up quite correctly. Also try the 'lsmod' command to see if there's already a sound module loaded. Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
Read the kernel howto. Essentially the steps are: 1) If you don't have your kernel source tree then install it. 2) as root, at a console, "make menuconfig" and in the Sound section select Alsa and your SB 16/AWE or use the OSS/free section... 3) make dep 3) make clear 4) make bzImage 5) cp bzImage to /boot/vmlinuz.yourinitials 6) cp System.map to /boot/System.map 7) Edit lilo and add your new kernel 8) lilo 10) reboot On Tuesday 03 April 2001 19:40, Greg Lentz wrote:
Thanks to all who helped me configure X 4.0.2 and the login via KDM.
I have another problem which doesn't seem to be totally resolved by any of the online sources I've looked at so far. I'm sure it's a FAQ, but I haven't found the solution as of yet.
In its prior configurations (as first a Caldera box and then, a Mandrake 7.2 box), I have able to get my Soundblaster 16/AWE 32 compatible ISA sound card to work. Caldera detected it during install, while in Mandrake, I had to run sndconfig (or something like that) from a terminal to set it up.
The configuration through YAST2 does not work in my particular situation. However, I think this is due to some other underlying problem.
First of all, I installed the system via an FTP installation, so if I'm missing any modules, etc., I could use some instruction as how to go through the system to "grab" the appropriate packages.
For example, at login, xconsole launches (don't know if this happens by default or not). Three messages come up:
modprobe: modprobe: Can't locate module sound-slot-0 modprobe: modprobe: Can't locate module sound-service-0-0 modprobe: modprobe: Can't locate module snd-card-0
If I run the sound card config through Y AST2, I do the following:
Start ALSA and Start sequencer are checked (default) I then click on "Add soundcard" and select Soundblaster 16
I then get the message:
"An error occured during installing: The kernal module snd-card-sb16 for sound support could not be loaded." I also get admonished to make sure that ALSA is correctly installed (something of which I am not aware of a way to check). It also suggests potentially trying OS/Free or another module.
Any suggestions or links to helpful sites appreciated.
Greg Lentz
Hi Jerry, whereis System.map? What is its purpouse? what is the purpouse of mkinitrd?? TIA, STefano Jerry Kreps wrote:
Read the kernel howto. Essentially the steps are: 1) If you don't have your kernel source tree then install it. 2) as root, at a console, "make menuconfig" and in the Sound section select Alsa and your SB 16/AWE or use the OSS/free section... 3) make dep 3) make clear 4) make bzImage 5) cp bzImage to /boot/vmlinuz.yourinitials 6) cp System.map to /boot/System.map 7) Edit lilo and add your new kernel 8) lilo 10) reboot
On Tuesday 03 April 2001 19:40, Greg Lentz wrote:
Thanks to all who helped me configure X 4.0.2 and the login via KDM.
I have another problem which doesn't seem to be totally resolved by any of the online sources I've looked at so far. I'm sure it's a FAQ, but I haven't found the solution as of yet.
In its prior configurations (as first a Caldera box and then, a Mandrake 7.2 box), I have able to get my Soundblaster 16/AWE 32 compatible ISA sound card to work. Caldera detected it during install, while in Mandrake, I had to run sndconfig (or something like that) from a terminal to set it up.
The configuration through YAST2 does not work in my particular situation. However, I think this is due to some other underlying problem.
First of all, I installed the system via an FTP installation, so if I'm missing any modules, etc., I could use some instruction as how to go through the system to "grab" the appropriate packages.
For example, at login, xconsole launches (don't know if this happens by default or not). Three messages come up:
modprobe: modprobe: Can't locate module sound-slot-0 modprobe: modprobe: Can't locate module sound-service-0-0 modprobe: modprobe: Can't locate module snd-card-0
If I run the sound card config through Y AST2, I do the following:
Start ALSA and Start sequencer are checked (default) I then click on "Add soundcard" and select Soundblaster 16
I then get the message:
"An error occured during installing: The kernal module snd-card-sb16 for sound support could not be loaded." I also get admonished to make sure that ALSA is correctly installed (something of which I am not aware of a way to check). It also suggests potentially trying OS/Free or another module.
Any suggestions or links to helpful sites appreciated.
Greg Lentz
-- 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
Stefano Papini wrote:
whereis System.map?
It will be located in /usr/src/linux after you've compiled your kernel.
What is its purpouse?
It contains kernel symbols and their corresponding addresses and is used for debugging the kernel, and also by other programs, such as 'ps'.
what is the purpouse of mkinitrd??
initrd stands for 'Initial RAMdisk'. If you have an initrd, the kernel loads this at startup. It allows you to have your SCSI card as a module, even if you root device is hanging off that SCSI card. It holds a number of small programs, including modprobe, as well as any modules which may need to be loaded at boot time (your SCSI card modules, for example). 'mkinitrd' is a little utility to help you in creating this file.
Jerry Kreps wrote:
Read the kernel howto. Essentially the steps are: 1) If you don't have your kernel source tree then install it. 2) as root, at a console, "make menuconfig" and in the Sound section select Alsa and your SB 16/AWE or use the OSS/free section... 3) make dep 3) make clear 4) make bzImage 5) cp bzImage to /boot/vmlinuz.yourinitials 6) cp System.map to /boot/System.map
If you copy the kernel to /boot/vmlinuz.yourinitials, you really should copy System.map to /boot/System.map.yourinitials as well, this way the kernel will read to the correct System.map.
7) Edit lilo and add your new kernel 8) lilo 10) reboot
Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
On Wednesday 04 April 2001 08:07, Chris Reeves wrote:
Stefano Papini wrote:
whereis System.map?
It will be located in /usr/src/linux after you've compiled your kernel.
What is its purpouse?
It contains kernel symbols and their corresponding addresses and is used for debugging the kernel, and also by other programs, such as 'ps'.
what is the purpouse of mkinitrd??
initrd stands for 'Initial RAMdisk'. If you have an initrd, the kernel loads this at startup. It allows you to have your SCSI card as a module, even if you root device is hanging off that SCSI card. It holds a number of small programs, including modprobe, as well as any modules which may need to be loaded at boot time (your SCSI card modules, for example). 'mkinitrd' is a little utility to help you in creating this file.
Jerry Kreps wrote:
Read the kernel howto. Essentially the steps are: 1) If you don't have your kernel source tree then install it. 2) as root, at a console, "make menuconfig" and in the Sound section select Alsa and your SB 16/AWE or use the OSS/free section... 3) make dep 3) make clear 4) make bzImage 5) cp bzImage to /boot/vmlinuz.yourinitials 6) cp System.map to /boot/System.map
If you copy the kernel to /boot/vmlinuz.yourinitials, you really should copy System.map to /boot/System.map.yourinitials as well, this way the kernel will read to the correct System.map.
Your right, of course. That wasn't the only thing this 60 yr old brain forgot. %->
7) Edit lilo and add your new kernel 8) lilo 10) reboot
Bye, Chris
Hi again, thanks a lot Chris, but how to cope with different kernels? If I'm not wrong I can see one only System.map in my /boot. Now, I deeply upgraded from 2.2.15 to 2.2.17, 2.4.0... and so on. Now I've 2.4.1, 2.4.2, 2.4.3. Is System.map to be set in /etc/lilo.conf???? Ciao, Stefano Chris Reeves wrote:
Stefano Papini wrote:
whereis System.map?
It will be located in /usr/src/linux after you've compiled your kernel.
What is its purpouse?
It contains kernel symbols and their corresponding addresses and is used for debugging the kernel, and also by other programs, such as 'ps'.
what is the purpouse of mkinitrd??
initrd stands for 'Initial RAMdisk'. If you have an initrd, the kernel loads this at startup. It allows you to have your SCSI card as a module, even if you root device is hanging off that SCSI card. It holds a number of small programs, including modprobe, as well as any modules which may need to be loaded at boot time (your SCSI card modules, for example). 'mkinitrd' is a little utility to help you in creating this file.
Jerry Kreps wrote:
Read the kernel howto. Essentially the steps are: 1) If you don't have your kernel source tree then install it. 2) as root, at a console, "make menuconfig" and in the Sound section select Alsa and your SB 16/AWE or use the OSS/free section... 3) make dep 3) make clear 4) make bzImage 5) cp bzImage to /boot/vmlinuz.yourinitials 6) cp System.map to /boot/System.map
If you copy the kernel to /boot/vmlinuz.yourinitials, you really should copy System.map to /boot/System.map.yourinitials as well, this way the kernel will read to the correct System.map.
7) Edit lilo and add your new kernel 8) lilo 10) reboot
Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
-- 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
Stefano Papini wrote:
thanks a lot Chris, but how to cope with different kernels? If I'm not wrong I can see one only System.map in my /boot.
Now, I deeply upgraded from 2.2.15 to 2.2.17, 2.4.0... and so on.
Now I've 2.4.1, 2.4.2, 2.4.3.
Is System.map to be set in /etc/lilo.conf????
No, the kernel picks the correct one automatically. If the kernel being loaded is called 'vmlinuz-2.4.3' is will look for a file called 'System.map-2.4.3', similarly, if the kernel is called 'vmlinuz-3sj48d', it will look for 'System.map-3sj48d'. If you copied the kernel over manually, you probably either forgot to copy the System.map file, or you copied it straight to /boot/System.map. I don't know exactly what 'make install' or 'make bzlilo' does, with respect to copying System.map. My /boot looks like this: galaxy:~ # ls /boot . System.map.2.4.3 vmlinuz.2.2.14 .. System.map.devel vmlinuz.2.2.14-2 System.map System.old vmlinuz.2.2.14-3 System.map.2.2.14 boot.0300 vmlinuz.2.2.14-4 System.map.2.2.14-2 boot.b vmlinuz.2.2.5.S System.map.2.2.14-3 chain.b vmlinuz.2.2.5.S-2 System.map.2.2.14-4 lost+found vmlinuz.2.2.5.S-orig System.map.2.2.5.S map vmlinuz.2.4.3 System.map.2.2.5.S-2 os2_d.b vmlinuz.devel System.map.2.2.5.S-orig vmlinuz vmlinuz.old This way, the kernel always gets the correct System.map.
Chris Reeves wrote:
Jerry Kreps wrote:
5) cp bzImage to /boot/vmlinuz.yourinitials 6) cp System.map to /boot/System.map
If you copy the kernel to /boot/vmlinuz.yourinitials, you really should copy System.map to /boot/System.map.yourinitials as well, this way the kernel will read to the correct System.map.
Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
On Wednesday 04 April 2001 07:03, Jerry Kreps wrote:
Read the kernel howto. Essentially the steps are: 1) If you don't have your kernel source tree then install it. 2) as root, at a console, "make menuconfig" and in the Sound section select Alsa and your SB 16/AWE or use the OSS/free section... 3) make dep 3) make clear 4) make bzImage
oops! forgot: make modules make modules_install (A mind is a terrible thing to lose)
5) cp bzImage to /boot/vmlinuz.yourinitials 6) cp System.map to /boot/System.map 7) Edit lilo and add your new kernel 8) lilo 10) reboot
On Tuesday 03 April 2001 19:40, Greg Lentz wrote:
Thanks to all who helped me configure X 4.0.2 and the login via KDM.
I have another problem which doesn't seem to be totally resolved by any of the online sources I've looked at so far. I'm sure it's a FAQ, but I haven't found the solution as of yet.
In its prior configurations (as first a Caldera box and then, a Mandrake 7.2 box), I have able to get my Soundblaster 16/AWE 32 compatible ISA sound card to work. Caldera detected it during install, while in Mandrake, I had to run sndconfig (or something like that) from a terminal to set it up.
The configuration through YAST2 does not work in my particular situation. However, I think this is due to some other underlying problem.
First of all, I installed the system via an FTP installation, so if I'm missing any modules, etc., I could use some instruction as how to go through the system to "grab" the appropriate packages.
For example, at login, xconsole launches (don't know if this happens by default or not). Three messages come up:
modprobe: modprobe: Can't locate module sound-slot-0 modprobe: modprobe: Can't locate module sound-service-0-0 modprobe: modprobe: Can't locate module snd-card-0
If I run the sound card config through Y AST2, I do the following:
Start ALSA and Start sequencer are checked (default) I then click on "Add soundcard" and select Soundblaster 16
I then get the message:
"An error occured during installing: The kernal module snd-card-sb16 for sound support could not be loaded." I also get admonished to make sure that ALSA is correctly installed (something of which I am not aware of a way to check). It also suggests potentially trying OS/Free or another module.
Any suggestions or links to helpful sites appreciated.
Greg Lentz
Thanks for the response. I have several follow-up questions: On Wed, 4 Apr 2001 07:34:35 -0500, you wrote:
On Wednesday 04 April 2001 07:03, Jerry Kreps wrote:
Read the kernel howto. Essentially the steps are: 1) If you don't have your kernel source tree then install it. 2) as root, at a console, "make menuconfig" and in the Sound section select Alsa and your SB 16/AWE or use the OSS/free section...
I did not see ALSA listed as an option anywhere, so I used the OSS/Free section.
3) make dep 3) make clear
When I type "make clear" I get the response "No rule to make target 'clear'. Stop."
4) make bzImage
oops! forgot: make modules make modules_install (A mind is a terrible thing to lose)
5) cp bzImage to /boot/vmlinuz.yourinitials
At this point, I have to stop, since for some reason "make bzImage" doesn't leave a file called bzImage anywhere that I can see. I apologize if I'm asking totally stupid questions, but I am a Windows refugee. I'm trying to change... Greg Lentz
Greg Lentz wrote:
On Wed, 4 Apr 2001 07:34:35 -0500, you wrote:
On Wednesday 04 April 2001 07:03, Jerry Kreps wrote:
Read the kernel howto. Essentially the steps are: 1) If you don't have your kernel source tree then install it. 2) as root, at a console, "make menuconfig" and in the Sound section select Alsa and your SB 16/AWE or use the OSS/free section...
I did not see ALSA listed as an option anywhere, so I used the OSS/Free section.
I can't remember exactly which section it is. I think I just said 'm' for sound support and OSS support, and didn't select any drivers.
3) make dep 3) make clear
When I type "make clear" I get the response "No rule to make target 'clear'. Stop."
Should be 'make clean' - looks like neuron 2's on the way out Jerry ;-) make menuconfig make dep make clean make bzImage make modules make modules_install
4) make bzImage
oops! forgot: make modules make modules_install (A mind is a terrible thing to lose)
5) cp bzImage to /boot/vmlinuz.yourinitials
At this point, I have to stop, since for some reason "make bzImage" doesn't leave a file called bzImage anywhere that I can see.
Assuming sources in /usr/src/linux and you're using an i386-based processor, bzImage is called /usr/src/linux/arch/i386/boot/bzImage Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
participants (4)
-
Chris Reeves -
Greg Lentz -
Jerry Kreps -
Stefano Papini