Re: audio probs yet

On Wednesday 17 March 2010, Jim Beard wrote:
>On 03/17/2010 03:12 PM, Gene Heskett wrote:
>> how have I nuke enough of pulse to give me back the usual alsa and kmix
>> type controls?
>
>In the menu system, Tools to System Tools to Configure your
>computer to Hardware to Sound Configuration.  Uncheck the
>pulse-audio stuff.

Ok, found that, and the pulse stuff is already disabled.

When the sound window opens: (copy paste)
Here you can select an alternative driver (either OSS or ALSA) for your sound 
card (ATI Technologies Inc|RV610 audio device [Radeon HD 2400 PRO]).

Your card currently use the ALSA "snd_emu10k1" driver (default driver for 
your card is "snd_hda_intel")

So the question is how the heck do I get rid of the ATI rv610 and 
'snd_hda_intel'.  I wish there was some way I could blacklist that audio from 
even being scanned by the kernel.  It may be on the card, but its not bonded 
out to any real connections external to the )*&%# chip.

Now, see below

If I could do a 'make xconfig' I know where to kill the building of those 
modules, but I can't find them in a make menuconfig.

I can't do a make xconfig because mdv apparently has no qt-mt package that it 
(xconfig) needs.  Is there a package that does contain the qt-mt stuff?

>> Question #2:  I've been building my own kernels since forever, but on a
>> 32 bit system.  Can I bring the full tree of linux-2.6.33.1 over, do a
>> make clean and using the existing config for this hardware, build it back
>> up as a 64 bit kernel?  That way I can get rid of the intel-hd stuff that
>> confuses pulse, making it choose the audio on my video card, an ati
>> 2400HD Pro, but which is not even bonded out to an output connections on
>> the card, and I can also make it ignore the motherboard audio by not
>> building its modules.  I have an SB Audigy-2 Live 24 bit pci card that
>> works buckets better than the imitation stuff ASUS puts on it
>> motherboards.
>
>If your system is currently running 64-bit, you should be able to
>install or copy over the source for your kernel of choice and do
>a make oldconfig

I did exactly that, and it enabled hundreds of modules I didn't have enabled 
in my old 32 bit .configs.

>to use the config of your currently running OS.  Kernels can be funny
>things, though, for someone as ignorant as I am; I have always
>found it
>a good idea to go through the make config routines for each new
>kernel.

I just copy them over from a previous kernel in my scripts and do a make 
oldconfig, and continuity has always been maintained, until now.

>If your newly compiled kernel breaks your kernel, you get to keep
>the pieces.  Be adventurous!  (Back up everything first, of course.)

I am not nuking the old kernels.  Until the boot partition fills up, I just 
add the new ones to the bottom of menu.lst or grub.conf, set the default and 
go.

However, for this to work, I need to be able to chainload to the grub 
iinstall on /dev/sdd1, and I haven't been able to cobble up a grub stanza to 
do that from the /dev/sda1 partition.

I note that the device.map on /dev/sda1/grub is different than the device.map 
on /dev/sdd1/grub.  Should they not all be identical?

If someone can suggest a working grub stanza that will chainload to the grub 
installed on /dev/sdd1, then I can make use of the grub ability to give me a 
menu of the various mdv supplied, or mine, kernels at boot time, simplicating 
the heck out of this.

Many Thanks Jim, and to anyone else who wants to stick an oar in this murky 
water.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Dungeons and Dragons is just a lot of Saxon Violence.
____________________________________________________
Want to buy your Pack or Services from Mandriva? 
Go to http://store.mandriva.com
Join the Club : http://www.mandrivaclub.com
____________________________________________________