On Fri, Feb 16, 2001 at 08:14:28PM -0600, Jonathan Drews wrote:
Hi Tor:
Was it difficult to install the 2.4 kernel with SuSE 7.1. -- Cheers,
Jonathan
Hi, No, it was no problem at all. 2.2.18 was already selected, so I selected 2.4 as well. The installer created a nice lilo config, and the bootscreen has become graphical :-) ( Really nice touch there SuSE :-) Now, I just select which kernel I want to boot, and presto :> -tosi -- ______ /---------------------------------------\ \ | Þór Sigurðsson | Tor Sigurdsson | t | | Netmaður | Network Specialist | o | |-----------------------------------------| s | | tosi@rhi.hi.is | i | \---------------------------------------/_____/
At 02:18 AM 2/17/2001 +0000, you wrote:
On Fri, Feb 16, 2001 at 08:14:28PM -0600, Jonathan Drews wrote:
No, it was no problem at all. 2.2.18 was already selected, so I selected 2.4 as well.
<snip> Now, I just select which kernel I want to boot, and presto :>
-tosi
Eh? You can install both kernels? Doesn't that mess up modutils and the like? How stable is that? ---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com Central Texas IT http://www.centraltexasit.com
It actually works pretty well. I would suggest that you only play with the 2.4.X kernel because it still has some issues. If you want stablity right now .. then stick with 2.2.18 .. * Jonathan Wilson (wilson@claborn.net) [010217 19:21]: => =>Eh? You can install both kernels? Doesn't that mess up modutils and the =>like? How stable is that? => -- Ben Rosenberg mailto:ben@whack.org ----- SuSE Linux 7.1 : Mutt 1.3.12i : KDE 2.1 Beta2 : Peace of Mind ----- If two men agree on everything, you can be sure that only one of them is doing the thinking.
On Saturday 17 February 2001 21:27, you wrote:
It actually works pretty well. I would suggest that you only play with the 2.4.X kernel because it still has some issues. If you want stablity right now .. then stick with 2.2.18 ..
Ben: can you breifly describe what those issues might be? Does 2.4 have a tough time coping with hdparm and DMA? I am primarily interested in SuSE for use as a desktop OS. Do the issues affect this kind of use? -- Cheers, Jonathan
Jonathan, Well, as far as what happened to me...everything just seemed to freeze up when doing simple tasks such as reading my mail in a terminal window. I didn't give it much of a chance...I am not into tweaking as much as I use to be...so I just switched to the 2.2.x kernel and I plan to mess with 2.4 when it reaches the 2.4.5 or so version. Regards, * Jonathan Drews (j.e.drews@worldnet.att.net) [010217 19:33]: => => can you breifly describe what those issues might be? Does 2.4 have a tough =>time coping with hdparm and DMA? I am primarily interested in SuSE for use as =>a desktop OS. Do the issues affect this kind of use? => -- Ben Rosenberg mailto:ben@whack.org ----- SuSE Linux 7.1 : Mutt 1.3.12i : KDE 2.1 Beta2 : Peace of Mind ----- If two men agree on everything, you can be sure that only one of them is doing the thinking.
On Saturday 17 February 2001 22:40, Jonathan Drews wrote:
On Saturday 17 February 2001 21:27, you wrote:
It actually works pretty well. I would suggest that you only play with the 2.4.X kernel because it still has some issues. If you want stablity right now .. then stick with 2.2.18 ..
Ben:
can you breifly describe what those issues might be? Does 2.4 have a tough time coping with hdparm and DMA? I am primarily interested in SuSE for use as a desktop OS. Do the issues affect this kind of use? Yea, Ben,
That's kinda like I fall in love with this girl and tell ya' about her and you just say "oh, I know her. . . She's got some 'issues'" and walk away. {;-)> Steve
At 07:27 PM 2/17/2001 -0800, you wrote:
It actually works pretty well. I would suggest that you only play with the 2.4.X kernel because it still has some issues.
Which brings up another Q I meant to ask: SuSE will surely provide an update to 2.4.x as they become available right? IIRC there's a few things fixed in 2.4.1 that are fairly important... I really hope SuSE will give us an update rpm. Boy, I'm starving for 7.1...won't order it over the net though, I've decided that I should buy it locally so that the local computer stores will know they have customers who really do want it..... ---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com Central Texas IT http://www.centraltexasit.com
On Saturday 17 February 2001 22:44, Jonathan Wilson wrote:
At 07:27 PM 2/17/2001 -0800, you wrote:
It actually works pretty well. I would suggest that you only play with the 2.4.X kernel because it still has some issues.
Which brings up another Q I meant to ask: SuSE will surely provide an update to 2.4.x as they become available right? IIRC there's a few things fixed in 2.4.1 that are fairly important... I really hope SuSE will give us an update rpm. Jonathan,
SuSE has in the past back-ported fixes from the development kernels. You may find the fixes are in the SuSE 2.4 RPMs. Steve
I believe the 2.4.X kernel that is shipping with 7.1 is 2.4.1 pre10 w/ lots of patching. I could be wrong, but I am pretty sure that's it. * Steven T. Hatton (hattons@bellatlantic.net) [010217 19:48]: => =>SuSE has in the past back-ported fixes from the development kernels. You may =>find the fixes are in the SuSE 2.4 RPMs. => -- Ben Rosenberg mailto:ben@whack.org ----- SuSE Linux 7.1 : Mutt 1.3.12i : KDE 2.1 Beta2 : Peace of Mind ----- If two men agree on everything, you can be sure that only one of them is doing the thinking.
Boy, I'm starving for 7.1...won't order it over the net though, I've decided that I should buy it locally so that the local computer stores will know they have customers who really do want it.....
Jonathan, You raise a good point here. If digitalriver's site had been offering the boxes Yesterday, I may have jumped on one, but I think you're right. It's a good idea to reward the Brick-n-Mortars for carrying the boxes. That way we ensure SuSE gets the drive-by exposure. *Drive-by* in the traditional sense mind you. Steve
On Sat, Feb 17, Jonathan Wilson wrote:
At 07:27 PM 2/17/2001 -0800, you wrote:
It actually works pretty well. I would suggest that you only play with the 2.4.X kernel because it still has some issues.
Which brings up another Q I meant to ask: SuSE will surely provide an update to 2.4.x as they become available right? IIRC there's a few things fixed in 2.4.1 that are fairly important... I really hope SuSE will give us an update rpm.
Yes, as soon as we incorporated and tested all required fixes. If you want to toy around with the current status, you can always get the sources from Huberts ftp directory: ftp://ftp.suse.com/pub/people/mantel/next/ Bye, LenZ -- ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH mailto:grimmer@suse.de Schanzaeckerstr. 10 http://www.suse.de/~grimmer/ 90443 Nuernberg, Germany The graveyards are full of indispensable people.
On Saturday 17 February 2001 22:29, Jonathan Wilson wrote:
At 02:18 AM 2/17/2001 +0000, you wrote:
On Fri, Feb 16, 2001 at 08:14:28PM -0600, Jonathan Drews wrote:
No, it was no problem at all. 2.2.18 was already selected, so I selected 2.4 as well.
<snip> Now, I just select which kernel I want to boot, and presto :>
-tosi
Eh? You can install both kernels? Doesn't that mess up modutils and the like? How stable is that?
Jonathan, This may or may not be a problem. If the modules for the different kernels will work off the same parameters in /etc/modules.conf things should be harmonious. Each kernel version has its own /lib/modules/<kernel-id> directory. The only reason I did not stay with the 2.4.2-pre3 I built is because I couldn't figure out how to get the sound working in a SuSE compatable way. This is a large part of the reason I suggested the 'Jugling Knives' book. (My vision is a picture of that krazy Kameleon all bandaged up, knives in hand, getting ready to try it once again.) As for the problems Ben experienced, I can't say too much. I was already trying to fix a problem with my X restarting. So I didn't have a known good system to start with. Steve
The newest version of Alsa should fix sound issues. Did to my SB live!, however that may not mean much to anyone out there with lesser known cards though... Matt On Saturday 17 February 2001 08:26 pm, Steven T. Hatton wrote:
On Saturday 17 February 2001 22:29, Jonathan Wilson wrote:
At 02:18 AM 2/17/2001 +0000, you wrote:
On Fri, Feb 16, 2001 at 08:14:28PM -0600, Jonathan Drews wrote:
No, it was no problem at all. 2.2.18 was already selected, so I selected 2.4 as well.
<snip> Now, I just select which kernel I want to boot, and presto :>
-tosi
Eh? You can install both kernels? Doesn't that mess up modutils and the like? How stable is that?
Jonathan,
This may or may not be a problem. If the modules for the different kernels will work off the same parameters in /etc/modules.conf things should be harmonious. Each kernel version has its own /lib/modules/<kernel-id> directory. The only reason I did not stay with the 2.4.2-pre3 I built is because I couldn't figure out how to get the sound working in a SuSE compatable way. This is a large part of the reason I suggested the 'Jugling Knives' book. (My vision is a picture of that krazy Kameleon all bandaged up, knives in hand, getting ready to try it once again.)
As for the problems Ben experienced, I can't say too much. I was already trying to fix a problem with my X restarting. So I didn't have a known good system to start with.
Steve
On Sunday 18 February 2001 00:58, Matthew wrote:
The newest version of Alsa should fix sound issues. Did to my SB live!, however that may not mean much to anyone out there with lesser known cards though...
Matt
This may or may not be a problem. If the modules for the different kernels will work off the same parameters in /etc/modules.conf things should be harmonious. Each kernel version has its own /lib/modules/<kernel-id> directory. The only reason I did not stay with the 2.4.2-pre3 I built is because I couldn't figure out how to get the sound working in a SuSE compatable way. This is a large part of the reason I suggested the 'Jugling Knives' book. (My vision is a picture of that krazy Kameleon all bandaged up, knives in hand, getting ready to try it once again.)
Steve
Matt, This soundcard has been VERY frustrating for me. I just checked to make sure I had all the latest alsa rpms from SuSE and indeed they are here. I re-ran the configuration in YaST2 and I get the following when I check my system: _________________________________________________________ nariana:~/helpfiles # cat /proc/asound/sndstat Sound Driver:3.8.1a-980706 (ALSA v0.5.9c emulation code) Kernel: Linux nariana 2.2.16 #4 Wed Feb 14 00:05:18 EST 2001 i686 Config options: 0 Installed drivers: Type 10: ALSA emulation Card config: Sound Blaster 16 at 0x220, irq 5, dma 1&5 Audio devices: 0: DSP v4.16 (DUPLEX) Synth devices: NOT ENABLED IN CONFIG Midi devices: 0: MPU-401 (UART) Timers: 7: system timer Mixers: 0: CTL1745 nariana:~/helpfiles # __________________________________________________________ I was able to build all the moduels in the tarball from the creative labs drvawe or whatever they call it. I wasn't sure what to do with the modules. At the same time I was having the X problem I've described earlier (and will return to soon.) I had to get that fixed because I was losing work every time it happened. There is a description of how to set this stuff up by hand in the SuSE book. I am not sure what the initial conditions are though. Here are a few of the questions I have regarding sound: 1) Do they expect for me to have ALSA installed when I follow the instructions starting on page 309 of the SuSE Book? 2) Do I need to remove all the ALSA stuff from the /etc/modules.conf if I do this by hand? - I *believe* so. 3) Does ALSA expect me to have an /etc/isapnp.conf if I do use ALSA? 4) If I have an isapnp.conf, will that break ALSA? 5) If I compile my own kernel should I build the modules? 5.a ) should I skip the sound section all together in the /usr/src/linux/.config? 5.b ) which modules do I need for my card? - I *believe* I finally found the answer to that. 5.c ) If I don't build the modules, are they removed when I make modules_install? 6 ) Does ALSA use different modules than the kernel build creates? 7 ) If I build the kernel modules will they step on ALSA modules of the same name? 8 ) Can I add the correct parameteres to the YaST2 configuraton mask and make ALSA work with my card? 8.a) How do I translate the names of the fields in the YaST2 mask to the names I see in a sndstat cat? 9) Why do I get "no device found" when I do a cat /dev/sndstat with ALSA? 9.a) should I get something else with alsa? 9.b) should I link /proc/asound/sndstat to /dev? 10 ) Why does the information I see in proc differ when using Creative Lab's modules and when using the ALSA RPMs? ########## with Creative Labs' modules bash-2.04# cat /proc/ioports 0220-022f : soundblaster 0330-0333 : MPU-401 UART 0388-038b : Yamaha OPL3 0620-0623 : sound driver (AWE32) 0a20-0a23 : sound driver (AWE32) 0e20-0e23 : sound driver (AWE32) ######## with the ALSA from the RPM bash-2.04# cat /proc/ioports 0220-022f : Sound Blaster 16 0330-0331 : Sound Blaster 16 - MPU-401 0388-038b : Sound Blaster 16 - FM 0620-0623 : Sound Blaster AWE 0a20-0a23 : Sound Blaster AWE 0e20-0e23 : Sound Blaster AWE 10.a) are these equivalent? 11) why does kmidi crash immediately in kde2.1-beta with an error saying it can't find piana+guitar no such file when I launch it from the command line. 11.a) if I launch kmidi through the "karaoke file player" option is doesn't crash, but it doesn't produce sound. Why? 11.a.1) when I do select "karaoke file player" I get this error in the system console: Feb 18 02:13:56 nariana modprobe: modprobe: Can't locate module sound-service-0-6 Why? What does it mean? 12 ) why does timidity only find guitar + piano when Creative Labs' player made the same Bach piece sound like a cathreral organ? 13) Can I use "sound fonts" with this setup? How? 14) How do I test to determine that all the functionality of my sound card is available? 15) What does that "Synth devices: NOT ENABLED IN CONFIG" messge mean in the cat /proc/asound/sndstat output? 16) would I get better results if I took the time to configure my sound card by hand? Any ideas? Steve
On Sunday 18 February 2001 00:58, Matthew wrote:
The newest version of Alsa should fix sound issues. Did to my SB live!, however that may not mean much to anyone out there with lesser known cards though...
Matt
This may or may not be a problem. If the modules for the different kernels will work off the same parameters in /etc/modules.conf things should be harmonious. Each kernel version has its own /lib/modules/<kernel-id> directory. The only reason I did not stay with the 2.4.2-pre3 I built is because I couldn't figure out how to get the sound working in a SuSE compatable way. This is a large part of the reason I suggested the 'Jugling Knives' book. (My vision is a picture
of
that krazy Kameleon all bandaged up, knives in hand, getting ready to
Hello Steve, Wow, a whole load of questions :-). They may all have a common source, I believe you are using an old version of ALSA that does not take 2.4 kernel into any consideration. I was having poblems to, until I went to www.alsa-project.org there site seems to be down at the moment though. From there I got there latest build, which I believe is newer than the SuSE rpm. After that was installed (really was not too bad to install either) everything worked fine! After running yast2, (I also tried alsaconf) it added back in the correct lines to /etc/modules.conf, even kimix worked fine after that. If you still get stuck I find there mailing list pretty good too, as they seem to know more about sound, in fact most of the questions and answers there leave me totally in the dust :-). Really hope that helps! Just wish there website was up... Matt On Sun, 18 Feb 2001 01:25:44 Steven T. Hatton wrote: try
it once again.)
Steve
Matt,
This soundcard has been VERY frustrating for me. I just checked to make sure
I had all the latest alsa rpms from SuSE and indeed they are here. I re-ran
the configuration in YaST2 and I get the following when I check my system: _________________________________________________________ nariana:~/helpfiles # cat /proc/asound/sndstat Sound Driver:3.8.1a-980706 (ALSA v0.5.9c emulation code) Kernel: Linux nariana 2.2.16 #4 Wed Feb 14 00:05:18 EST 2001 i686 Config options: 0
Installed drivers: Type 10: ALSA emulation
Card config: Sound Blaster 16 at 0x220, irq 5, dma 1&5
Audio devices: 0: DSP v4.16 (DUPLEX)
Synth devices: NOT ENABLED IN CONFIG
Midi devices: 0: MPU-401 (UART)
Timers: 7: system timer
Mixers: 0: CTL1745 nariana:~/helpfiles # __________________________________________________________
I was able to build all the moduels in the tarball from the creative labs drvawe or whatever they call it. I wasn't sure what to do with the modules.
At the same time I was having the X problem I've described earlier (and will
return to soon.) I had to get that fixed because I was losing work every time
it happened. There is a description of how to set this stuff up by hand in the SuSE book. I am not sure what the initial conditions are though. Here are a few of the questions I have regarding sound:
1) Do they expect for me to have ALSA installed when I follow the instructions starting on page 309 of the SuSE Book?
2) Do I need to remove all the ALSA stuff from the /etc/modules.conf if I do
this by hand? - I *believe* so.
3) Does ALSA expect me to have an /etc/isapnp.conf if I do use ALSA?
4) If I have an isapnp.conf, will that break ALSA?
5) If I compile my own kernel should I build the modules?
5.a ) should I skip the sound section all together in the /usr/src/linux/.config?
5.b ) which modules do I need for my card? - I *believe* I finally found the
answer to that.
5.c ) If I don't build the modules, are they removed when I make modules_install?
6 ) Does ALSA use different modules than the kernel build creates?
7 ) If I build the kernel modules will they step on ALSA modules of the same
name? 8 ) Can I add the correct parameteres to the YaST2 configuraton mask and make
ALSA work with my card?
8.a) How do I translate the names of the fields in the YaST2 mask to the names I see in a sndstat cat?
9) Why do I get "no device found" when I do a cat /dev/sndstat with ALSA? 9.a) should I get something else with alsa? 9.b) should I link /proc/asound/sndstat to /dev?
10 ) Why does the information I see in proc differ when using Creative Lab's
modules and when using the ALSA RPMs? ########## with Creative Labs' modules bash-2.04# cat /proc/ioports
0220-022f : soundblaster 0330-0333 : MPU-401 UART 0388-038b : Yamaha OPL3 0620-0623 : sound driver (AWE32) 0a20-0a23 : sound driver (AWE32) 0e20-0e23 : sound driver (AWE32)
######## with the ALSA from the RPM bash-2.04# cat /proc/ioports
0220-022f : Sound Blaster 16 0330-0331 : Sound Blaster 16 - MPU-401 0388-038b : Sound Blaster 16 - FM 0620-0623 : Sound Blaster AWE 0a20-0a23 : Sound Blaster AWE 0e20-0e23 : Sound Blaster AWE
10.a) are these equivalent?
11) why does kmidi crash immediately in kde2.1-beta with an error saying it can't find piana+guitar no such file when I launch it from the command line.
11.a) if I launch kmidi through the "karaoke file player" option is doesn't crash, but it doesn't produce sound. Why? 11.a.1) when I do select "karaoke file player" I get this error in the system
console: Feb 18 02:13:56 nariana modprobe: modprobe: Can't locate module sound-service-0-6 Why? What does it mean?
12 ) why does timidity only find guitar + piano when Creative Labs' player made the same Bach piece sound like a cathreral organ?
13) Can I use "sound fonts" with this setup? How?
14) How do I test to determine that all the functionality of my sound card is
available?
15) What does that "Synth devices: NOT ENABLED IN CONFIG" messge mean in the
cat /proc/asound/sndstat output?
16) would I get better results if I took the time to configure my sound card
by hand?
Any ideas?
Steve
-- 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
On Sunday 18 February 2001 04:48, Matthew Johnson wrote:
Hello Steve,
Wow, a whole load of questions :-). They may all have a common source, I believe you are using an old version of ALSA that does not take 2.4 kernel into any consideration. I was having poblems to, until I went to www.alsa-project.org there site seems to be down at the moment though. From there I got there latest build, which I believe is newer than the SuSE rpm.
After that was installed (really was not too bad to install either) everything worked fine! After running yast2, (I also tried alsaconf) it added back in the correct lines to /etc/modules.conf, even kimix worked fine after that.
If you still get stuck I find there mailing list pretty good too, as they seem to know more about sound, in fact most of the questions and answers there leave me totally in the dust :-).
Really hope that helps! Just wish there website was up...
Matt
On Sun, 18 Feb 2001 01:25:44 Steven T. Hatton wrote:
On Sunday 18 February 2001 00:58, Matthew wrote:
The newest version of Alsa should fix sound issues. Did to my SB live!, however that may not mean much to anyone out there with lesser known cards though...
Matt
This may or may not be a problem. If the modules for the different kernels will work off the same parameters in /etc/modules.conf things should be harmonious. Each kernel version has its own /lib/modules/<kernel-id> directory. The only reason I did not stay with the 2.4.2-pre3 I built is because I couldn't figure out how to get the sound working in a SuSE compatable way. This is a large part of the reason I suggested the 'Jugling Knives' book. (My vision is a picture
of
that krazy Kameleon all bandaged up, knives in hand, getting ready to
try
it once again.)
Steve
Matt,
This soundcard has been VERY frustrating for me. I just checked to make sure
I had all the latest alsa rpms from SuSE and indeed they are here. I re-ran
the configuration in YaST2 and I get the following when I check my system: _________________________________________________________ nariana:~/helpfiles # cat /proc/asound/sndstat Sound Driver:3.8.1a-980706 (ALSA v0.5.9c emulation code) Kernel: Linux nariana 2.2.16 #4 Wed Feb 14 00:05:18 EST 2001 i686 Config options: 0
Installed drivers: Type 10: ALSA emulation
Card config: Sound Blaster 16 at 0x220, irq 5, dma 1&5
Audio devices: 0: DSP v4.16 (DUPLEX)
Synth devices: NOT ENABLED IN CONFIG
Midi devices: 0: MPU-401 (UART)
Timers: 7: system timer
Mixers: 0: CTL1745 nariana:~/helpfiles # __________________________________________________________
I was able to build all the moduels in the tarball from the creative labs drvawe or whatever they call it. I wasn't sure what to do with the modules.
At the same time I was having the X problem I've described earlier (and will
return to soon.) I had to get that fixed because I was losing work every time
it happened. There is a description of how to set this stuff up by hand in the SuSE book. I am not sure what the initial conditions are though. Here are a few of the questions I have regarding sound:
1) Do they expect for me to have ALSA installed when I follow the instructions starting on page 309 of the SuSE Book?
2) Do I need to remove all the ALSA stuff from the /etc/modules.conf if I do
this by hand? - I *believe* so.
3) Does ALSA expect me to have an /etc/isapnp.conf if I do use ALSA?
4) If I have an isapnp.conf, will that break ALSA?
5) If I compile my own kernel should I build the modules?
5.a ) should I skip the sound section all together in the /usr/src/linux/.config?
5.b ) which modules do I need for my card? - I *believe* I finally found the
answer to that.
5.c ) If I don't build the modules, are they removed when I make modules_install?
6 ) Does ALSA use different modules than the kernel build creates?
7 ) If I build the kernel modules will they step on ALSA modules of the same
name? 8 ) Can I add the correct parameteres to the YaST2 configuraton mask and make
ALSA work with my card?
8.a) How do I translate the names of the fields in the YaST2 mask to the names I see in a sndstat cat?
9) Why do I get "no device found" when I do a cat /dev/sndstat with ALSA? 9.a) should I get something else with alsa? 9.b) should I link /proc/asound/sndstat to /dev?
10 ) Why does the information I see in proc differ when using Creative Lab's
modules and when using the ALSA RPMs? ########## with Creative Labs' modules bash-2.04# cat /proc/ioports
0220-022f : soundblaster 0330-0333 : MPU-401 UART 0388-038b : Yamaha OPL3 0620-0623 : sound driver (AWE32) 0a20-0a23 : sound driver (AWE32) 0e20-0e23 : sound driver (AWE32)
######## with the ALSA from the RPM bash-2.04# cat /proc/ioports
0220-022f : Sound Blaster 16 0330-0331 : Sound Blaster 16 - MPU-401 0388-038b : Sound Blaster 16 - FM 0620-0623 : Sound Blaster AWE 0a20-0a23 : Sound Blaster AWE 0e20-0e23 : Sound Blaster AWE
10.a) are these equivalent?
11) why does kmidi crash immediately in kde2.1-beta with an error saying it can't find piana+guitar no such file when I launch it from the command line.
11.a) if I launch kmidi through the "karaoke file player" option is doesn't crash, but it doesn't produce sound. Why? 11.a.1) when I do select "karaoke file player" I get this error in the system
console: Feb 18 02:13:56 nariana modprobe: modprobe: Can't locate module sound-service-0-6 Why? What does it mean?
12 ) why does timidity only find guitar + piano when Creative Labs' player made the same Bach piece sound like a cathreral organ?
13) Can I use "sound fonts" with this setup? How?
14) How do I test to determine that all the functionality of my sound card is
available?
15) What does that "Synth devices: NOT ENABLED IN CONFIG" messge mean in the
cat /proc/asound/sndstat output?
16) would I get better results if I took the time to configure my sound card
by hand?
Any ideas?
Steve
-- 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 Matt,
Sorry, I should have been more clear about my current configuration. I'm back on 2.2.16-SuSE compiled to my liking. Also running 7.0 not 7.1. I am not sure whether to thank you for pointing me to the ALSA mailing list or not. {:-)> I was about ready to give up on this thing and move on to glx. Now it looks like I'll have yet another go at it. WRT using the latest ALSA, did you first remove all the SuSE provided RPMs? I seem to remember having a problem with dependencies when doing that. Oh, and I *was* tending to a bit of hyperbole in the length of the list of questions, but they are all questions I wish I had answers for. They are the kinds of questions that are best addressed by having a better core understanding of what is happening "under the hood." I have the type of mind that does not do well with simply remembering the facts. I need a good theoretical framework or I get confused quickly. I may also try to clean up the list and send it to the SuSE protal folks as a topic suggestion. Which reminds me, I think I have an unanswered message from you vis-a-vis glx and XF86-3 and 4 Steve
Hi Guys My experience with 7.1 was similar. When installing using kernel 2.2.18 I was able to configure Xfree to work with my HP laptop. When I got clever and decided to install 2.4 I couldn't get a working X configuration. Reinstalled (fresh Install) 2.2.18 and got my GUI back, no problem. However this could also be my limited knowledge of Linux and if I understood the issues with 2.4 there may have been a simple fix. But, as they say, If it aint broke, don't fix it. Regards Mark A.
Eh? You can install both kernels? Doesn't that mess up modutils and the like? How stable is that?
As for the problems Ben experienced, I can't say too much. I was already trying to fix a problem with my X restarting. So I didn't have a known good system to start with.
On Sunday 18 February 2001 03:57, Mark Annandale wrote:
Hi Guys
My experience with 7.1 was similar. When installing using kernel 2.2.18 I was able to configure Xfree to work with my HP laptop.
When I got clever and decided to install 2.4 I couldn't get a working X configuration. Reinstalled (fresh Install) 2.2.18 and got my GUI back, no problem.
However this could also be my limited knowledge of Linux and if I understood the issues with 2.4 there may have been a simple fix.
But, as they say, If it aint broke, don't fix it.
Regards
Mark A.
Eh? You can install both kernels? Doesn't that mess up modutils and the
like? How stable is that?
As for the problems Ben experienced, I can't say too much. I was already trying to fix a problem with my X restarting. So I didn't have a known
good
system to start with.
Mark, Guess I should've been clearer on this. My X was hosed *before* I went to 2.4.2-pre3. I was hoping the new kernel would fix the problem, but it didn't. I will say my system seemed to boot faster with the new kernel, and I didn't notice any problems other than the aforementioned problem with sound modules. On laptops and Linux all I can say is, 'I saw a picture of it once.' Sorry I can't add too much on that one. Steve
participants (9)
-
Ben Rosenberg -
Jonathan Drews -
Lenz Grimmer -
Mark Annandale -
Matthew -
Matthew Johnson
-
Steven T. Hatton -
Tor Sigurdsson -
wilson＠claborn.net