Re: ALSA replacement
Hmm, why didn't you dub this 'pulse audio replacement', i wonder. For most desktop users, ALSA is already doing about anything they need. Most of the rest can be done by just the player (maybe using some pulse lib but would not require the server). Well apparently gnome-media depends on it. Many good players (including vlc) do not. Go figure. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
Re: ALSA replacement
Nate Bargmann : > I have found that on a new installation that I had to go into the > alsamixer application (Ncurses terminal mode app) and unmute various > controls to get sound to work. Also, you likely have Pulse Audio > installed so there is another layer that can mute things. And there's things like "Cinnamon Control Center" on downstreams like mint. I also like Gkrellm's volume plugin. Finally, on my HP Pavilion g4, F9 through F11 control volume and mute. This machine's running Mint 17 Cinnamon. I'm using fluxbox instead. [testing slrn] -- Any technology distinguishable from magic is insufficiently advanced. (*) - - -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
Re: ALSA replacement
I have found that on a new installation that I had to go into the alsamixer application (Ncurses terminal mode app) and unmute various controls to get sound to work. Also, you likely have Pulse Audio installed so there is another layer that can mute things. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Ham radio, Linux, bikes, and more: http://www.n0nb.us -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
Re: ALSA Config
Hello, is there a *alsa-utils entry in /etc/rcS.d available ? I'm not 100% sure but this can be it. j.keßler Dean Chester wrote: > Hi, > Everytime i boot in to debian(sid im running on a vostro 1400) i have > to run alsaconfg. Is there anyway i can get rid of having to do this > as it annoying. > Dean > > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
Re: ALSA mixer values
Hello Haines, There are some other laptops/harwdare which let you activate both the Speakers and the Headphones at the same time, since it's a software configuration. The ones I've seen show the same behaviour you state under Windows, but when under Linux, plugging in the Headphone jack does not mute the laptop speakers. On other hardware, such as my laptop, when the headphone jack is detected, the speaker output is muted automatically (there is no "Front" or similar Alsamixer value to tweak). Best Regards, Jonás Andradas Skype: jontux LinkedIn: http://www.linkedin.com/in/andradas GPG Fingerprint: 5A90 3319 48BC E0DC 17D9 130B B5E2 9AFD 7649 30D5 Keyservers: wwwkeys.eu.pgp.net | pgp.rediris.es On Wed, Aug 27, 2008 at 21:20, Sebastian Günther <[EMAIL PROTECTED] > wrote: > * Haines Brown ([EMAIL PROTECTED]) [27.08.08 20:07]: > > Sorry to follow up on myself, but I discovered that when an external > > device plugged into the headphone jack, it disables the laptop > > internal speaker. > > > > Is there any way to enable both at the same time? Or do I have to rig > > a little external speaker using a "Y" adapter? > > > > No, since this is a hardware feature of any thinkpad. And yes, the Y way > is your solution. > > HTH > Sebastian > > -- > " Religion ist das Opium des Volkes. " Karl Marx > > [EMAIL PROTECTED]@N GÜNTHER mailto:[EMAIL PROTECTED] >
Re: ALSA mixer values
* Haines Brown ([EMAIL PROTECTED]) [27.08.08 20:07]: > Sorry to follow up on myself, but I discovered that when an external > device plugged into the headphone jack, it disables the laptop > internal speaker. > > Is there any way to enable both at the same time? Or do I have to rig > a little external speaker using a "Y" adapter? > No, since this is a hardware feature of any thinkpad. And yes, the Y way is your solution. HTH Sebastian -- " Religion ist das Opium des Volkes. " Karl Marx [EMAIL PROTECTED]@N GÜNTHER mailto:[EMAIL PROTECTED] pgpND2odFOPAL.pgp Description: PGP signature
Re: ALSA mixer values
Sorry to follow up on myself, but I discovered that when an external device plugged into the headphone jack, it disables the laptop internal speaker. Is there any way to enable both at the same time? Or do I have to rig a little external speaker using a "Y" adapter? -- Haines Brown, KB1GRM -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA Problem
On 2/27/06, Peter Frühberger <[EMAIL PROTECTED] > wrote: -BEGIN PGP SIGNED MESSAGE-Hash: RIPEMD160Guilherme Fortunato schrieb:>> This controller should be supported by the snd-atiixp module. Try to>>load the module (as root) with modprobe snd-atiixp Unfortunately, etc/dsp didnt appeared . [..]You use debian, so try: (as root)apt-get install alsa-baseapt-get install alsa-utils now run "alsaconf", it sould detect your card -> then writes your modulsection und modprobes the card automatically with "alsamixer" you can check if volume is mutedHave fun Peter Unloading ALSA sound driver modules: (none loaded).Building card database...Running update-modules...Loading driver...Setting default volumes...Saving the mixer setup used for this in /var/lib/alsa/asound.state. /usr/sbin/alsactl: save_state:1194: No soundcards found...=== Now ALSA is ready to use. For adjustment of volumes, use your favorite mixer. Have a lot of fun!
Re: ALSA Problem
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Guilherme Fortunato schrieb: >> >> >>This controller should be supported by the snd-atiixp module. Try to >>load the module (as root) with >> >>modprobe snd-atiixp > > > > Unfortunately, etc/dsp didnt appeared . [..] You use debian, so try: (as root) apt-get install alsa-base apt-get install alsa-utils now run "alsaconf", it sould detect your card -> then writes your modul section und modprobes the card automatically with "alsamixer" you can check if volume is muted Have fun Peter - -- Key-ID: 0x1A995A9B keyserver: pgp.mit.edu == Fingerprint: 4606 DA19 EC2E 9A0B 0157 C81B DA07 CF63 1A99 5A9B -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEA0E22gfPYxqZWpsRAxcWAJ9C9CrcvhMyqE2QzhwXNqAgS0egigCeJbkj M6l5WTVb0mPnN84j3M+bLkA= =OLN3 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: ALSA Problem
This controller should be supported by the snd-atiixp module. Try toload the module (as root) with modprobe snd-atiixp Unfortunately, etc/dsp didnt appeared . If that works you can check if /dev/dsp was created. If not you can tryudevstart invoke-rc.d alsa reloadinvoke-rc.d alsa-utils restart after typing the last line, the following error message appeared: invoke-rc.d: unknown initscript, /etc/init.d/alsa-utils not found. and see if that helps. If you are not successful you should post theerror messages here; also check for new entries related to sound and udev in /var/log/syslog. No log for udev or sound If you do get /dev/dsp you can restart KDE and see if the error messageis gone. Then you can try your sound at "K-Menu > Control Center > Sound & Multimedia > Sound System" with the "Test Sound" button. This is alsothe place to check if the sound system is enabled and the audio deviceis set to "Advanced Linux Sound Architecture" (in the "Hardware" tab). If everything seems fine (no errors) but you still can't hear anythingit might be due to the volume being set to zero. Open a Konsole windowand use "alsamixer" to check. What else could it be? Thanks, though.
Re: Re: ALSA Problem
OP accidentally sent his reply to my email address instead of the list (probably the old problem of missing "reply-to-list" feature in many email clients). I copy the relevant part below so that everyone can follow the discussion. Guilherme Fortunato wrote: On 2/25/06, Florian Kulzer <[EMAIL PROTECTED]> wrote: [...] It is probably easy to fix this, but we need to know which audio device you have. If you are unsure about this, find the audio-related line in the output of the command "lspci". The following is the output from "lspci": [...] :00:14.5 Multimedia audio controller: ATI Technologies Inc IXP150 AC'97 Audio Controller This controller should be supported by the snd-atiixp module. Try to load the module (as root) with modprobe snd-atiixp If that works you can check if /dev/dsp was created. If not you can try udevstart invoke-rc.d alsa reload invoke-rc.d alsa-utils restart and see if that helps. If you are not successful you should post the error messages here; also check for new entries related to sound and udev in /var/log/syslog. If you do get /dev/dsp you can restart KDE and see if the error message is gone. Then you can try your sound at "K-Menu > Control Center > Sound & Multimedia > Sound System" with the "Test Sound" button. This is also the place to check if the sound system is enabled and the audio device is set to "Advanced Linux Sound Architecture" (in the "Hardware" tab). If everything seems fine (no errors) but you still can't hear anything it might be due to the volume being set to zero. Open a Konsole window and use "alsamixer" to check. Regards, Florian P.S. Please keep the discussion on the list. If your email program does not have a "reply-to-list" function you can use "reply-to-all", manually delete my email address and change the mode for debian-laptop from "Cc:" to "To:". -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA Problem
Guilherme Fortunato wrote:
Dear Fellows,
I'm a newbie in linux, specially in the debian distribution, and I'm having
a problem with the sound system in my Toshiba A70-S249 lap-top. The problem
is that every time I start my system I get this following message:
"starting ALSA (not loaded)"
Then, when I get into the KDE invironment I get the following message:
"Sound Server Informational Message
Error while initializing the sound driver:
device/dev/dsp can't be opened (No such file or directory)
The sound server will continue, using the null output device."
Does anyone could help me saying what is happening?
It seems like your sound card is not recognized properly at boot and
therefore the entry in the /dev directory is not created. KDE can only
access the audio device if this /dev/dsp is present.
It is probably easy to fix this, but we need to know which audio device
you have. If you are unsure about this, find the audio-related line in
the output of the command "lspci".
Another quick thing to check is if your user is a member of the "audio"
group. ("groups username" will list all groups of which "username" is a
member.)
Also tell us which version of Debian ("cat /etc/issue") and which kernel
("uname -a") you are using.
Regards,
Florian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA sound lost in KDE after going to kernel 2.6.15
Try turning off or tuning the KDE sound system. It sounds like it is locking the device. It is being forced to release it when alsaconf unloads the modules. Robert On Wed, 2006-02-15 at 17:48 -0800, Joe Emenaker wrote: Okay... this one is very strange. When I boot my laptop with 2.6.12, it boots right into KDE and I hear the welcome sound during the login splash screen. When I boot with 2.6.15, I don't hear the welcome sound and none of the sound players produce any sound... whether using a GUI player or if I use a console player like mplayer. HOWEVER, if I then run alsaconf in a konsole window, alsaconf unloads all of the drivers and reloads them. THEN, all of the sound players work in KDE (and mplayer works in a konsole window). If I reboot after configuring ALSA, the sound is gone again. Every time, I have to boot to KDE, then run alsaconf, and then I can use sound. But it gets even more strange. If I boot into KDE, then run alsaconf and get sound, and then kill kdm to get back to a text console (where mplayer still makes sound) and then run KDE again, sound is gone *again*. So, it's not something wrong with ALSA at boot time (or else running alsaconf would fix it for the entire uptime... regardless of how many times I killed and restarted kdm). In other words, any time KDE is run, ALSA will be broken (both in KDE and from a console if I kill kdm) until alsaconf is run (either from a Konsole window or from a text console). Has anyone experienced this before? Any ideas? - Joe
Re: Re: ALSA + suspend
try this: /etc/init.d/alsa force-reload this works for me.. -- _ K. Cem Karadeniz Kent State University / Computer Science http://www.cs.kent.edu/~kkaraden/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alsa, strange problems
David Reviejo wrote:
>>* Martin Jenewein <[EMAIL PROTECTED]> [050622
08:57]:>> But how can i change the boot configuration to
unload>> snd_intel8x0m? (it#s not in /etc/modules) >Hi,
Martin>First, the snd_intel8x0m module is not a sound module; it's a
modem>module (because the same chip has sound and modem capabilities). If
you>read the Alsa docs, it say in some place you need to load this
module>AFTER the snd_intel8x0 sound module if you want to have
sound.>I think the module it's been loaded by hotplug on boot; so,
you need to>"blacklist" this module. The better way is to put a file
("alsa-modem">for example), in /etc/hotplug/blacklist.d with the name of
the module>(snd_intel8x0m) in it. The next boot this module will not be
loaded.And/or, if you wish to have the the modem
module available at boot, add both of them in the correct order to /etc/modules.
This solved the problem on my system, anyway.
John
O'Hagan
Re: Alsa, strange problems
* Martin Jenewein <[EMAIL PROTECTED]> [050622 08:57]:
> But how can i change the boot configuration to unload
> snd_intel8x0m? (it#s not in /etc/modules)
Hi, Martin
First, the snd_intel8x0m module is not a sound module; it's a modem
module (because the same chip has sound and modem capabilities). If you
read the Alsa docs, it say in some place you need to load this module
AFTER the snd_intel8x0 sound module if you want to have sound.
I think the module it's been loaded by hotplug on boot; so, you need to
"blacklist" this module. The better way is to put a file ("alsa-modem"
for example), in /etc/hotplug/blacklist.d with the name of the module
(snd_intel8x0m) in it. The next boot this module will not be loaded.
Cheers,
--
David
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA help!
I had the same laptop until recently and had sarge running on it. Configuring the sound gave me a couple more grey hairs as well. Since I was quite the newbie when it comes to configuring that stuff it might be fairly dirty but it worked for me. Some webpage indicated that the chip used on the Omnibook 4150 wasn't actually the neomagic one but the AD1848 ... In the file /etc/modules I added the line ad1848 io=0x530 irq=5 dma=1 dma2=0 -- /etc/modutils/alsa-base : # snd module options options snd device_mode=0660 # autoloader aliases alias char-major-116 snd alias char-major-14 soundcore alias sound-slot-0 ad1848 above sound-slot-0 snd-pcm-oss snd-mixer-oss snd-seq-oss alias sound-service-0-0 snd-mixer-oss #alias sound-service-0-1 snd-seq-oss #alias sound-service-0-3 snd-pcm-oss #alias sound-service-0-8 snd-seq-oss #alias sound-service-0-12 snd-pcm-oss # Load optional modules above their base modules above snd-pcm snd-pcm-oss above snd-mixer snd-mixer-oss above snd-seq snd-seq-oss snd-seq-midi # Cause a script to be run after card driver module initialization post-install snd-ad1848 /lib/alsa/modprobe-post-install snd-ad1848 and I modified /etc/discover.d/alsa-base to skip all other cards (including the nm256_audio !) I guess that should be it. Not sure if I did anything else of consequence to sound since I played around quite a bit. HTH Richard On Tuesday 31 May 2005 09:09, Douglas wrote: > I am runnung debian sarge on a really old HP OmniBook 4150. > soundcard is NeoMagic 256 > > lsmod yields: > snd_seq_dummy 2692 0 > snd_seq48368 1 snd_seq_dummy > snd_seq_device 7116 2 snd_seq_dummy,snd_seq > snd_pcm_oss48288 0 > snd_mixer_oss 17472 1 snd_pcm_oss > snd_nm256 66368 0 > snd_ac97_codec 82716 1 snd_nm256 > snd_pcm80360 3 snd_pcm_oss,snd_nm256,snd_ac97_codec > snd_timer 20644 2 snd_seq,snd_pcm > snd_page_alloc 7652 1 snd_pcm > snd47908 9 > snd_seq_dummy,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_nm256,sn >d_ac97_codec,snd_pcm,snd_timer > > > I just compiled 2.6.11.11. > I compiled in soundcore and nothign else for sound support. > > > I have always had issues gettign sound to work on this machine, but I > decided to attack it in earnest. > > I cannot seem to get it to work. I have tried everything. > > esd says /dev/dsp does not exist (it clearly does) > > XMMS gives me the standard Be sure nothing is blocking your Soundcard. > > arts gives me the basic cannot find device. > > I am part of audio group. > > Anyone have a process (ground up) that gets this workin? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA help!
> I have always had issues gettign sound to work on this machine, but I > decided to attack it in earnest. > > I cannot seem to get it to work. I have tried everything. > > esd says /dev/dsp does not exist (it clearly does) > > XMMS gives me the standard Be sure nothing is blocking your Soundcard. > > arts gives me the basic cannot find device. > > I am part of audio group. > > Anyone have a process (ground up) that gets this workin? debian used to come with a program called sndconfig that always did the trick for me. I know this is not a "ground up" approach, but maybe worth a try. btw - it's only available in woody, though. Also - if you *just* added yourself to the audio group... you need to completely log out , then log in again. HTH. That was a funny post, BTW. -- Regards, dbp
Re: ALSA help!
On Tuesday 31 May 2005 14:42, Douglas wrote: > I have tried that. His problem was that ALSA would not start. My issue > seems to be that it is running but for some reason my system believes > that /dev/dsp is inaccessible and that I have no sound device installed > at all, Alsaconf completes but displays : > /usr/sbin/alsactl: load_state:1236: No soundcards found... If you actually get a message that /dev/dsp is inaccessible, then try NOT loading the OSS drivers. Alsa doesn't need them. -- derek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA help!
Strange. Your ALSA is saying that it cannot find a soundcard. He is saying that you shouldn't use the nm256 driver. So, if you are using the nm256 driver, and he (and others) are saying that you need another driver to get a working setup, I'm not surprised that your ALSA config cannot find a soundcard. Additionally, /dev/dsp is not needed for ALSA, it is only for OSS emulation. I have ALSA running, but I don't have /dev/dsp. So, it's up to you. My best bet would be to follow the advice and let others try to help you (post the output of the commands). If you're sure that you are doing the right thing and the hardware isn't broken, file a bug report. Koen On Tue, 2005-05-31 at 13:42 -0400, Douglas wrote: > I have tried that. His problem was that ALSA would not start. My issue > seems to be that it is running but for some reason my system believes > that /dev/dsp is inaccessible and that I have no sound device installed > at all, Alsaconf completes but displays : > /usr/sbin/alsactl: load_state:1236: No soundcards found... > . > > Koen Vermeer wrote: > > >I'm honestly not trying to be an ass, but this is all the help I can > >give for now: I searched for 'omnibook 4150 alsa' in google. Look at the > >first hit, and try that. Consider reporting the results here. > > > >Koen > > > > > > > > > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA help!
I have tried that. His problem was that ALSA would not start. My issue seems to be that it is running but for some reason my system believes that /dev/dsp is inaccessible and that I have no sound device installed at all, Alsaconf completes but displays : /usr/sbin/alsactl: load_state:1236: No soundcards found... . Koen Vermeer wrote: I'm honestly not trying to be an ass, but this is all the help I can give for now: I searched for 'omnibook 4150 alsa' in google. Look at the first hit, and try that. Consider reporting the results here. Koen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA help!
I'm honestly not trying to be an ass, but this is all the help I can give for now: I searched for 'omnibook 4150 alsa' in google. Look at the first hit, and try that. Consider reporting the results here. Koen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA sound not working after suspend
> Am Donnerstag, 20. Januar 2005 17:05 schrieb Jeremy Brooks: > >> I had the same problem with a Dell X300. I was able to get sound >> working after suspend by using kernel.org 2.6.10 sources, and patching >> them with the software suspend 2 stuff. Now I can suspend to disk, and >> when I resume sound works. The only thing that doesn't work (yet -- >> I'm still playing with the config options) is DRM. After coming back >> from suspend, the GL screensavers no longer animate, and glxgears just >> sits, without spinning. > > Hello Jeremy, > > I am currently reading software suspend 2 HOWTO... did you try the option: > > "UseDummyXServer > > This option may also help if you experience strange things such as 3D not > working upon resume. It launches a fake xserver that should cause proper > initialization of the chipset." Yes, I've tried that option, and combinations of UserDummyXServer and SwitchToTextMode. The only way I can get DRM working again is to log out of X and log back in. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA sound not working after suspend
Am Donnerstag, 20. Januar 2005 17:05 schrieb Jeremy Brooks: > I had the same problem with a Dell X300. I was able to get sound > working after suspend by using kernel.org 2.6.10 sources, and patching > them with the software suspend 2 stuff. Now I can suspend to disk, and > when I resume sound works. The only thing that doesn't work (yet -- > I'm still playing with the config options) is DRM. After coming back > from suspend, the GL screensavers no longer animate, and glxgears just > sits, without spinning. Hello Jeremy, I am currently reading software suspend 2 HOWTO... did you try the option: "UseDummyXServer This option may also help if you experience strange things such as 3D not working upon resume. It launches a fake xserver that should cause proper initialization of the chipset." to get 3D working? http://softwaresuspend.berlios.de/HOWTO-4.html#ss4.1 Regards, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA sound not working after suspend
> > Hello, > > as I told suspend now works with IBM ThinkPad T23 and R51 when using > Debian kernel 2.6.10. > > But I still have one problem: ALSA sound does not work anymore after a > suspend through ARTS. > > On the ThinkPad R51 it is enough to restart the ARTS soundsystem via the > KDE control panel. On the ThinkPad T23 I have to reboot to get ALSA > working. > > Well so next step will be to compile my own kernel out of kernel.org > sources and try it with that. > I had the same problem with a Dell X300. I was able to get sound working after suspend by using kernel.org 2.6.10 sources, and patching them with the software suspend 2 stuff. Now I can suspend to disk, and when I resume sound works. The only thing that doesn't work (yet -- I'm still playing with the config options) is DRM. After coming back from suspend, the GL screensavers no longer animate, and glxgears just sits, without spinning. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA on Compaq Armada 7400
Koen Vermeer wrote: Op vr 07-01-2005, om 15:10 schreef Willie McKemie: If someone has ALSA working on a similair Armada, please tell me how you have it configured. Let's start by giving you my credentials: I recently tried to help someone else on this list and I failed. If you're still interested in my advice: Run alsaconf first, just to see if it works. If not, first make sure all the sound modules are unloaded. Then try modprobe snd-es18xx irq=5 port=0x220 dma1=1 dma2=0 mpu_port=0x330 isapnp=0 (all on one line) Fill in the right values for your card and check with lspci if the card is indeed found. Koen Yes "alsaconf", not "alsaconfig" as per my first post. RRP -- // Randy Potratz, IT Administrator // Quality Paint and Coatings // 2236 Clairville Road // Oshkosh, WI 54904 // Ph. 920 233 3039 FAX 920 233 3362 // [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA on Compaq Armada 7400
Willie McKemie wrote: For years, I have been trying to get sound working on Compaq Armadas: 73xx, 78xx, 7400, & 7800. Thanks to some help I got here months ago, I got it going without ALSA; I guess that's OSS. I've tried to start using ALSA and now I've gotten sound broken again. This is on a 7400 running Ubuntu, kernel 2.6.8. I think it is a problem of just not knowing how to configure ALSA. Before ALSA, "sb irq=5 io=0x220 dma=1" in /etc/modules gave me working sound. With ALSA, snd-es18xx irq=5 io=0x220 dma=1 and snd-sb16 irq=5 io=0x220 dma=1 result in "failure to detect" at boot. If someone has ALSA working on a similair Armada, please tell me how you have it configured. The easiest way I've gotten this to work on a 7400 was to install Mepis and then run "alsaconfig". Zip, bam, boom, it worked! RRP -- // Randy Potratz, IT Administrator // Quality Paint and Coatings // 2236 Clairville Road // Oshkosh, WI 54904 // Ph. 920 233 3039 FAX 920 233 3362 // [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA on Compaq Armada 7400
Op vr 07-01-2005, om 15:10 schreef Willie McKemie: > If someone has ALSA working on a similair Armada, please tell me how > you have it configured. Let's start by giving you my credentials: I recently tried to help someone else on this list and I failed. If you're still interested in my advice: Run alsaconf first, just to see if it works. If not, first make sure all the sound modules are unloaded. Then try modprobe snd-es18xx irq=5 port=0x220 dma1=1 dma2=0 mpu_port=0x330 isapnp=0 (all on one line) Fill in the right values for your card and check with lspci if the card is indeed found. Koen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alsa HP zv5000 ATI IXP150 AC'97
On Monday 29 November 2004 10:27, [EMAIL PROTECTED] wrote: > thx a lot for advice, but I'll need some more help, (Sorry I'm quit fresh > in Debian only 3 weeks expierance) That means I made syslink, but then I > could't run "dpkg-reconfigure alsa-source", couse I got message:" > alsa-source is not installed", I installed alsa from .deb packeges. (I've > try to install from source, which I download from alsa-project.org, but as > I wrote before There was:"error: You have built-in ALSA in your kernel.") > So my question is :Should I install alsa-source? and second: What that > means - "recompile alsa module". I try to find out(google) but I still > don't understand:( regards > Mateusz > > > > -- > Startuj z INTERIA.PL!!! >>> http://link.interia.pl/f1837 I had this problem and found a solution yesterday. I upgraded the machine to the latest 2.6.9 (on unstable) and then as sound had never worked from installation I ran alsaconf which now detects the sound card correctly, and sound works. For some reason (I think it may be due to a problem with writing CDs) the default that is installed currently is 2.6.8, but 2.6.9 is available and does seem to solve this problem. This is not an an HP 5000, but on a Samsung P28, but the sound chip set is the same. David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: Alsa HP zv5000 ATI IXP150 AC'97
thx a lot for advice, but I'll need some more help, (Sorry I'm quit fresh in Debian only 3 weeks expierance) That means I made syslink, but then I could't run "dpkg-reconfigure alsa-source", couse I got message:" alsa-source is not installed", I installed alsa from .deb packeges. (I've try to install from source, which I download from alsa-project.org, but as I wrote before There was:"error: You have built-in ALSA in your kernel.") So my question is :Should I install alsa-source? and second: What that means - "recompile alsa module". I try to find out(google) but I still don't understand:( regards Mateusz -- Startuj z INTERIA.PL!!! >>> http://link.interia.pl/f1837
Re: Alsa HP zv5000 ATI IXP150 AC'97
Ok, I had similar problems for a long time, until something I did suddenly worked. Try this...copy the /etc/modutils/alsa to /etc/alsa/modutils/1.0 then create a symlink to this from /etc/modutils/alsa (thats how it is on my system) [EMAIL PROTECTED]:/etc/alsa/modutils$ ls -l total 12 -rw-r--r-- 1 root root 480 Jul 22 18:36 1.0 [EMAIL PROTECTED]:/etc/modutils$ ls -l total 44 -rw-r--r-- 1 root root 432 Sep 27 2001 0keep -rw-r--r-- 1 root root 198 Sep 27 2001 actions -rw-r--r-- 1 root root 1174 Oct 19 13:28 aliases lrwxrwxrwx 1 root root 22 May 12 2004 alsa -> /etc/alsa/modutils/1.0 -rw-r--r-- 1 root root 82 Oct 19 11:54 alsa-base then run dpkg-reconfigure alsa-source, and recompile alsa module. Hopefully, this will work. keep us posted on your progress -Sudarshan -- diplomacy, n: Lying in state. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alsa HP zv5000 ATI IXP150 AC'97
Hi Mateusz, i am not really sure but there's a bug on bugzilla.kernel.org #3366: [...] Upon upgrading from 2.6.6 to 2.6.8.1, the driver fails to load, with message: kern.log:Sep 8 00:08:37 omicron kernel: ATI IXP AC97 controller: probe of :00:14.5 failed with error -13 A fresh build of 2.6.7 has the same error. [...] That's maybe the problem, still needing a fix (since the bug isn't closed), i think. just my 2 cents, marco Mateusz Milian wrote: ohci_hcd :00:13.1: PCI device 1002:4348 (ATI Technologies Inc) ->ATI IXP AC97 controller: probe of :00:14.5 failed with error -13 <- -- Ho sognato una vita di stagioni sicure ero il padre e la madre di azioni del caso e dell'orgoglio. Ivano Fossati - Labile -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alsa HP zv5000 ATI IXP150 AC'97 (misery loves company)
On Sat, Nov 27, 2004 at 10:46:02AM +0100, Mateusz Milian wrote: > #/etc/init.d/alsa restart > Storing ALSA mixer settings...failed. > Starting ALSA.../etc/init.d/alsa: Error: alsactl restore failed with > message 'alsactl: load_state:1134: No soundcards found...'. > done. > It seems all moduls are corectly loaded. > > #lsmod |grep snd > snd_atiixp 19880 0 > snd_ac97_codec 59268 1 snd_atiixp > snd_pcm85384 1 snd_atiixp > snd_timer 23172 1 snd_pcm > snd50660 4 snd_atiixp,snd_ac97_codec,snd_pcm,snd_timer > soundcore 9824 1 snd > snd_page_alloc 11144 2 snd_atiixp,snd_pcm > > Reely I've got no idea, whtat's wrong:( > > Greets > mateusz > I cannot offer any help, but on my Dell laptop I have exactly the same problems. Alsa was previously working fine, suddenly I went to play a movie and realized I had no sound. I have a this Dell laptop and a desktop, both running sid, both of which I apt-get dist-upgrade at the same time. There was recently an update for alsa that I noticed both machines dutifully installed, this was perhaps a week a go now, not sure. The desktop, also running alsa has no problems whatsoever with sound but now my laptop cannot find any soundcard at all. Did you recently upgrade any alsa packages? -- Angelina Carlton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alsa HP zv5000 ATI IXP150 AC'97
Check to see if your /etc/modutils/alsa looks like this alias char-major-116 snd alias char-major-14 soundcore alias sound-slot-0 snd-slot-0 If not, then put these line in there, and run update-modules, and restart alsa. I too have the same card and it works fine with kernel 2.6.7. I remember that I had some problems initally getting it to work right. Maybe this was what corrected it finally. -- Sudarshan modutils/alsa didn't look like your, and I made according to your tips, but still does't work. I'm wondering, Is in your /etc/modutist file alsa-base? I've got, but when I removed it,nothing has been chenged:(, and still the same error: #/etc/init.d/alsa restart Storing ALSA mixer settings...failed. Starting ALSA.../etc/init.d/alsa: Error: alsactl restore failed with message 'alsactl: load_state:1134: No soundcards found...'. done. It seems all moduls are corectly loaded. #lsmod |grep snd snd_atiixp 19880 0 snd_ac97_codec 59268 1 snd_atiixp snd_pcm85384 1 snd_atiixp snd_timer 23172 1 snd_pcm snd50660 4 snd_atiixp,snd_ac97_codec,snd_pcm,snd_timer soundcore 9824 1 snd snd_page_alloc 11144 2 snd_atiixp,snd_pcm Reely I've got no idea, whtat's wrong:( Greets mateusz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alsa HP zv5000 ATI IXP150 AC'97
Check to see if your /etc/modutils/alsa looks like this alias char-major-116 snd alias char-major-14 soundcore options snd major=116 cards_limit=4 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-12 snd-pcm-oss alias /dev/dsp* snd-pcm-oss alias snd-card-0 snd-atiixp alias snd-slot-0 snd-card-0 alias sound-slot-0 snd-slot-0 If not, then put these line in there, and run update-modules, and restart alsa. I too have the same card and it works fine with kernel 2.6.7. I remember that I had some problems initally getting it to work right. Maybe this was what corrected it finally. -- Sudarshan I have discovered photography. Now I can kill myself. I have nothing else to learn. -- Pablo Picasso -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alsa HP zv5000 ATI IXP150 AC'97
Sudarshana Koushik wrote: Did u apt-get install any of the alsamixers like alsamixer-gui, and try to unmute all the channels? by default they are all muted. If xmms or alsaconf detects the audio card, then most probably this is all that you need to do. -Sudarshan unfortunately It's not so easy, alsaconf detects correctly my soundcard but after there is error: >Running update-modules... >Loading driver... >Starting ALSA.../etc/init.d/alsa: Error: alsactl restore failed with message 'alsactl: load_state:1134: No soundcards found...'. >done. >Setting default volumes... >Saving the mixer setup used for this in /var/lib/alsa/asound.state. >/usr/sbin/alsactl: save_state:1061: No soundcards found... >=== >Now ALSA is ready to use. >For adjustment of volumes, use your favorite mixer. >Have a lot of fun! I found out that It can be problem with kernel https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=125873 http://forums.gentoo.org/viewtopic.php?t=224965 but there is now solution:( I've tried use kernel 2.4.x, but there are a lot of diefrent problems, so I've decided to leave this idea. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alsa HP zv5000 ATI IXP150 AC'97
Did u apt-get install any of the alsamixers like alsamixer-gui, and try to unmute all the channels? by default they are all muted. If xmms or alsaconf detects the audio card, then most probably this is all that you need to do. -Sudarshan -- I have discovered photography. Now I can kill myself. I have nothing else to learn. -- Pablo Picasso -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alsa HP zv5000 ATI IXP150 AC'97
Mateusz Milian wrote: Derek Broughton wrote: On Friday 26 November 2004 14:26, David Goodenough wrote: On Friday 26 November 2004 17:20, Mateusz Milian wrote: Greetz to All! I've got a problem with my sound card. I've just install sarge on hp zv5015ea, but there is no sound. When I try to calls xmms I get: ... and visited www.alsa-project.org, and I found my devince, and install howto. I proceed according to the install howto: You're going about it the hard way. Did you try using alsaconf? This is Debian - you shouldn't have needed to compile anything. Of course, I used alsaconf and: Running update-modules... Loading driver... Starting ALSA.../etc/init.d/alsa: Error: alsactl restore failed with message 'alsactl: load_state:1134: No soundcards found...'. done. Setting default volumes... Saving the mixer setup used for this in /var/lib/alsa/asound.state. /usr/sbin/alsactl: save_state:1061: No soundcards found... === Now ALSA is ready to use. For adjustment of volumes, use your favorite mixer. Have a lot of fun! Very funny, but still no sound, I look for this error and I find a lot information, but I get bogged down in detail That's the problem ! I've forgot to add, that "alsaconf" detects my soundcard, but unfortunately there is above error. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alsa HP zv5000 ATI IXP150 AC'97
Derek Broughton wrote: On Friday 26 November 2004 14:26, David Goodenough wrote: On Friday 26 November 2004 17:20, Mateusz Milian wrote: Greetz to All! I've got a problem with my sound card. I've just install sarge on hp zv5015ea, but there is no sound. When I try to calls xmms I get: ... and visited www.alsa-project.org, and I found my devince, and install howto. I proceed according to the install howto: You're going about it the hard way. Did you try using alsaconf? This is Debian - you shouldn't have needed to compile anything. Of course, I used alsaconf and: Running update-modules... Loading driver... Starting ALSA.../etc/init.d/alsa: Error: alsactl restore failed with message 'alsactl: load_state:1134: No soundcards found...'. done. Setting default volumes... Saving the mixer setup used for this in /var/lib/alsa/asound.state. /usr/sbin/alsactl: save_state:1061: No soundcards found... === Now ALSA is ready to use. For adjustment of volumes, use your favorite mixer. Have a lot of fun! Very funny, but still no sound, I look for this error and I find a lot information, but I get bogged down in detail That's the problem ! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alsa HP zv5000 ATI IXP150 AC'97
On Friday 26 November 2004 14:26, David Goodenough wrote: > On Friday 26 November 2004 17:20, Mateusz Milian wrote: > > Greetz to All! > > > > I've got a problem with my sound card. I've just install sarge on hp > > zv5015ea, but there is no sound. When I try to calls xmms I get: ... > > and visited www.alsa-project.org, and I found my devince, and install > > howto. I proceed according to the install howto: > > You're going about it the hard way. Did you try using alsaconf? This is Debian - you shouldn't have needed to compile anything. -- derek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alsa HP zv5000 ATI IXP150 AC'97
On Friday 26 November 2004 17:20, Mateusz Milian wrote: > Greetz to All! > > I've got a problem with my sound card. I've just install sarge on hp > zv5015ea, but there is no sound. When I try to calls xmms I get: > > melon:~# xmms& > [1] 8941 > melon:~# > ** WARNING **: oss_open(): Failed to open audio device (/dev/dsp): No such > device > > so I've changed plugin to alsa and: > > melon:~# xmms& > [1] 8438 > melon:~# > ** WARNING **: alsa_get_mixer(): Attaching to mixer hw:0 failed: No such > device > > > So I thought maybe I don't have alsa instaled. and I did : > > melon:/usr/src/alsa/alsa-driver-1.0.7# lspci | grep audio > :00:14.5 Multimedia audio controller: ATI Technologies Inc IXP150 AC'97 > Audio Controller > > and visited www.alsa-project.org, and I found my devince, and install > howto. I proceed according to the install howto: > > melon:/# modinfo soundcore > filename: /lib/modules/2.6.8-1-386/kernel/sound/soundcore.ko > description:Core sound module > author: Alan Cox > license:GPL > alias: char-major-14-* > vermagic: 2.6.8-1-386 preempt 386 gcc-3.3 > depends: > > untill this moment: > > /configure --with-cards=atiixp --with-seq > checking for gcc... gcc > .. > checking for directory with kernel source... /usr/src/linux > checking for directory with kernel build... > checking for kernel version... 2.6.8.1 > checking for GCC version... Kernel compiler: gcc 3.3.4 (Debian 1:3.3.4-13) > Used compiler: gcc (GCC) 3.3.4 (Debian 1:3.3.4-13) checking for built-in > ALSA... "yes" > configure: error: You have built-in ALSA in your kernel. > make all-deps > make[1]: Entering directory `/usr/src/alsa/alsa-driver-1.0.7' > make[1]: Nothing to be done for `all-deps'. > make[1]: Leaving directory `/usr/src/alsa/alsa-driver-1.0.7' > > Please, run the configure script as first... > > rm -f /snd*.*o /persist.o /isapnp.o > make[1]: Entering directory `/usr/src/alsa/alsa-driver-1.0.7/acore' > Makefile:6: /usr/src/alsa/alsa-driver-1.0.7/Makefile.conf: No such file or > directory make[1]: *** No rule to make target > `/usr/src/alsa/alsa-driver-1.0.7/Makefile.conf'. Stop. make[1]: Leaving > directory `/usr/src/alsa/alsa-driver-1.0.7/acore' make: *** > [install-modules] Error 1 > > > so It seems I've got alsa built-in (my kernel is 2.6.8-1, so It's for sure) > I checked my moduls: > > melon:~# lsmod > Module Size Used by > snd_pcm_oss48168 0 > nls_cp437 6016 1 > ntfs 88660 1 > snd_mixer_oss 16640 1 snd_pcm_oss > ipv6 229764 8 > ds 17796 4 > thermal12944 0 > fan 4236 0 > button 6680 0 > processor 17584 1 thermal > ac 5132 0 > battery 9740 0 > af_packet 20872 2 > ehci_hcd 27908 0 > eth139419976 0 > yenta_socket 19200 0 > pcmcia_core63028 2 ds,yenta_socket > 8139too23936 0 > 8139cp 19072 0 > mii 4864 2 8139too,8139cp > crc32 4608 2 8139too,8139cp > ohci1394 32004 0 > snd_atiixp 19880 0 > snd_ac97_codec 59268 1 snd_atiixp > snd_pcm85384 2 snd_pcm_oss,snd_atiixp > snd_timer 23172 1 snd_pcm > snd50660 6 > snd_pcm_oss,snd_mixer_oss,snd_atiixp,snd_ac97_codec,snd_pcm,snd_timer > soundcore 9824 1 snd > snd_page_alloc 11144 2 snd_atiixp,snd_pcm > tsdev 7168 0 > mousedev9996 2 > joydev 9536 0 > usbhid 28864 0 > ohci_hcd 19460 0 > usbcore 104164 5 ehci_hcd,usbhid,ohci_hcd > pci_hotplug30640 0 > ati_agp 8332 1 > agpgart31784 1 ati_agp > parport_pc 31936 0 > parport37320 1 parport_pc > evdev 9088 0 > capability 4872 0 > commoncap 7168 1 capability > sr_mod 15780 0 > sbp2 22408 0 > scsi_mod 115148 2 sr_mod,sbp2 > ieee1394 100408 3 eth1394,ohci1394,sbp2 > ide_cd 38176 0 > cdrom 35740 2 sr_mod,ide_cd > genrtc 9332 0 > ext3 109544 1 > jbd54552 1 ext3 > ide_generic 1664 0 > ide_disk 16768 4 > atiixp 8472 1 > ide_core 125156 4 ide_cd,ide_generic,ide_disk,atiixp > unix 25908 47 > font8576 0 > vesafb 6688 0 > cfbcopyarea 3840 1 vesafb > cfbimgblt 3200 1 vesafb > cfbfillrect 3712 1 vesafb > > There is above snb_atiixp, so everything looks good, but still there is no > sound:( I googled that I can
Re: ALSA problem on ASUS M6N
Am Fr, den 01.10.2004 schrieb Ivan Glushkov um 10:35: > Hi list, > I was running happily my ALSA untill this morning... The strangiest > think is that everything looks ok, my sound card is recognized, and running: > > %dmesg | grep intel > intel8x0_measure_ac97_clock: measured 49569 usecs > intel8x0: clocking to 48000 > > the xmms is running happily, the Volume Control applet is claiming to > put up and down the volume, but there is no sound at all! Nothing is > coming out niether from xmms, nor from mplayer. I hear a small squeak > when I rapidly put the volume from min to max on the volume control. Checked Alsamixer? Loaded all your modules? And most importantly, what did you change yesterday *g* > And since I have started asking... Every time when I boot my machine the > esd is started. I have to kill it to be able to use my ALSA. How can I > prevent the esd from starting at boot up? ESD is not started at boot time but by your desktop environment (probably GNOME then). You can turn it off from preferences, audio, Sound Server. It's also possible to remove the whole package (called esound if I recall right -- don't remove libesd though, only the sound server itself). -- Best Regards, | I couldn't afford a cool signature, Sebastian | so I just got this one. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: ALSA problem on ASUS M6N
Am Fr, den 01.10.2004 schrieb Ivan Glushkov um 10:35: > Hi list, > I was running happily my ALSA untill this morning... The strangiest > think is that everything looks ok, my sound card is recognized, and running: > > %dmesg | grep intel > intel8x0_measure_ac97_clock: measured 49569 usecs > intel8x0: clocking to 48000 > > the xmms is running happily, the Volume Control applet is claiming to > put up and down the volume, but there is no sound at all! Nothing is > coming out niether from xmms, nor from mplayer. I hear a small squeak > when I rapidly put the volume from min to max on the volume control. Checked Alsamixer? Loaded all your modules? And most importantly, what did you change yesterday *g* > And since I have started asking... Every time when I boot my machine the > esd is started. I have to kill it to be able to use my ALSA. How can I > prevent the esd from starting at boot up? ESD is not started at boot time but by your desktop environment (probably GNOME then). You can turn it off from preferences, audio, Sound Server. It's also possible to remove the whole package (called esound if I recall right -- don't remove libesd though, only the sound server itself). -- Best Regards, | I couldn't afford a cool signature, Sebastian | so I just got this one. signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: ALSA / DMIX
Hey there,
El Sáb 10 Jul 2004 04:08, B. Douglas Hilton escribió:
> First, why use xmms when Alsaplayer is so cool? Its really good IMHO.
> Alsa is great, especially if you are a musician or work with midi or
> such. Nothing beats it.
I tried, the sound works like a charm...but I'll keep using xmms (some
special features).
> For mplayer, hmm... mine works and is self compiled, make sure you
> have your kernel source compiled and supposedly it will detect alsa
> headers and such. Even if if has to use oss fallback that should
> still work ok.
Mine is working with alsa, my .mplayer/config(I have sarges alsa-headers
installed):
ao=alsa:default
> It took me some tinkering around to get alsa working on my system but
> it is definately superior to anything else around. If it even works
> at all then thats a real good sign.
I'm not saying that alsa doesn't works well. I think that alsa ROCKS!!!,
but DMix support is not working as expected. For example: Depending on
the sound card your /etc/asound.conf YMMV.
> Tip: try killing esd if its running, there's some bug with it that it
> grabs /dev/dsp and locks it so it really screws up alsa apps.
I'm using Arts, no esd arround. Arts works nice through dmixed alsa, but
some apps won't work well, JUK.
> Tip2: compile your kernel with static sound, (no modules), debian
> alsa will grumble a bit about no modules found but it all should
> work. A static kernel sometimes isn't a bad idea for a laptop since
> your hardware is known and immutable. I usually build all static
> support for laptop internal devices and modules for pluggable things
> like USB, serial, parallel, etc.
I now discover is loading the alsa modules, but I'll try it out.
Guess what, I found out what was the problem with xmms, it only happens
with mp3 files, so I installed the mad plugin and it is working like a
charm.
Thanx for your time.
> - Doug
>
> Nicolás Velásquez O. wrote:
> >Hello there,
> >
> >My system:
> >- Dell, Inspiron 5100
> >- Debian sarge
> >- snd_intel8x0
> >- Self compiled kernel 2.6.7
> >
> >I've had not so nice experiences (neither dmix nor asym) with it:
> >- Using xmms, if there is a lot of disk usage, audio will stop
> > playing. - Using (self compiled) mplayer, the audio won't play
> > well.
> >
> >Solutions: (better solutions are welcome!!)
> >- xmms, use xmms through arts (and arts through alsa)
> >- MPlayer, give cache to the default alsa device.
> >
> >Solutions drawbacks:
> >- xmms, arts ain't that good, some audio files will play lossy.
> >- MPlayer, none.
> >
> >Links:
> >http://alsa.opensrc.org/index.php?page=DmixPlugin
> >http://alsa.opensrc.org/index.php?page=asym
> >
> >
> >
> >My /etc/asound.conf:
> >#asym fun start here. we define one pcm device called "dmixed"
> >pcm.dmixed {
> > type dmix
> > ipc_key 1025
> > slave {
> >pcm "hw:0,0" # you cannot use a "plug" device
> > #here,darn.
> >period_time 0
> >period_size 1024 # must be power of 2
> >buffer_size 8192 # dito. It
> >#format "S32_LE"
> >#periods 128 # dito.
> >#rate 8000# with rate 8000 you *will* hear,
> > # if ossmix is used :)
> > }
> > bindings {
> > 0 0
> > 1 1
> > }
> >}
> >
> >#one called "dsnooped" for capturing
> >pcm.dsnooped {
> >ipc_key 1027
> >type dsnoop
> >slave.pcm "hw:0,0"
> >}
> >
> >#and this is the real magic
> >pcm.asymed {
> >type asym
> >playback.pcm "dmixed"
> >capture.pcm "dsnooped"
> >}
> >
> >#a quick plug plugin for above device to do the converting magic
> >pcm.pasymed {
> >type plug
> >slave.pcm "asymed"
> >}
> >
> >#a ctl device to keep xmms happy
> >ctl.pasymed {
> >type hw
> >card 0
> >}
> >
> >#for aoss:
> >pcm.dsp0 {
> >type plug
> >slave.pcm "asymed"
> >}
> >
> >ctl.mixer0 {
> >type hw
> >card 0
> >}
> >
> ># alsa default card
> >pcm.!default {
> > type plug
> > slave.pcm "asymed"
> >}
> >#done
> >
> >El Vie 09 Jul 2004 18:37, Chris Metcalf escribió:
> >>Has anybody had a good experience getting the Dmix plugin working
> >>well with ALSA?
> >>
> >>I'm trying to get my laptop (Thinkpad X31 using the snd_intel8x0
> >> ALSA module) to be able to play more than one wave channel at
> >> once, but I'm not having much success.
> >>
> >>Any helpful direction (howtos, good/bad experiences, alternate
> >>methods) would be appreciated.
> >>
> >>Thanks,
> >>--
> >>Chris Metcalf
> >>[EMAIL PROTECTED]
> >>http://chrismetcalf.net
--
Atentamente,
Nicolás Velásquez
Bogotá, Colombia
(^) ASCII Ribbon Campaign
X NO HTML/RTF in e-mail
/ \ NO Word docs in e-mail
Re: ALSA / DMIX
Hey there,
El Sáb 10 Jul 2004 04:08, B. Douglas Hilton escribió:
> First, why use xmms when Alsaplayer is so cool? Its really good IMHO.
> Alsa is great, especially if you are a musician or work with midi or
> such. Nothing beats it.
I tried, the sound works like a charm...but I'll keep using xmms (some
special features).
> For mplayer, hmm... mine works and is self compiled, make sure you
> have your kernel source compiled and supposedly it will detect alsa
> headers and such. Even if if has to use oss fallback that should
> still work ok.
Mine is working with alsa, my .mplayer/config(I have sarges alsa-headers
installed):
ao=alsa:default
> It took me some tinkering around to get alsa working on my system but
> it is definately superior to anything else around. If it even works
> at all then thats a real good sign.
I'm not saying that alsa doesn't works well. I think that alsa ROCKS!!!,
but DMix support is not working as expected. For example: Depending on
the sound card your /etc/asound.conf YMMV.
> Tip: try killing esd if its running, there's some bug with it that it
> grabs /dev/dsp and locks it so it really screws up alsa apps.
I'm using Arts, no esd arround. Arts works nice through dmixed alsa, but
some apps won't work well, JUK.
> Tip2: compile your kernel with static sound, (no modules), debian
> alsa will grumble a bit about no modules found but it all should
> work. A static kernel sometimes isn't a bad idea for a laptop since
> your hardware is known and immutable. I usually build all static
> support for laptop internal devices and modules for pluggable things
> like USB, serial, parallel, etc.
I now discover is loading the alsa modules, but I'll try it out.
Guess what, I found out what was the problem with xmms, it only happens
with mp3 files, so I installed the mad plugin and it is working like a
charm.
Thanx for your time.
> - Doug
>
> Nicolás Velásquez O. wrote:
> >Hello there,
> >
> >My system:
> >- Dell, Inspiron 5100
> >- Debian sarge
> >- snd_intel8x0
> >- Self compiled kernel 2.6.7
> >
> >I've had not so nice experiences (neither dmix nor asym) with it:
> >- Using xmms, if there is a lot of disk usage, audio will stop
> > playing. - Using (self compiled) mplayer, the audio won't play
> > well.
> >
> >Solutions: (better solutions are welcome!!)
> >- xmms, use xmms through arts (and arts through alsa)
> >- MPlayer, give cache to the default alsa device.
> >
> >Solutions drawbacks:
> >- xmms, arts ain't that good, some audio files will play lossy.
> >- MPlayer, none.
> >
> >Links:
> >http://alsa.opensrc.org/index.php?page=DmixPlugin
> >http://alsa.opensrc.org/index.php?page=asym
> >
> >
> >
> >My /etc/asound.conf:
> >#asym fun start here. we define one pcm device called "dmixed"
> >pcm.dmixed {
> > type dmix
> > ipc_key 1025
> > slave {
> >pcm "hw:0,0" # you cannot use a "plug" device
> > #here,darn.
> >period_time 0
> >period_size 1024 # must be power of 2
> >buffer_size 8192 # dito. It
> >#format "S32_LE"
> >#periods 128 # dito.
> >#rate 8000# with rate 8000 you *will* hear,
> > # if ossmix is used :)
> > }
> > bindings {
> > 0 0
> > 1 1
> > }
> >}
> >
> >#one called "dsnooped" for capturing
> >pcm.dsnooped {
> >ipc_key 1027
> >type dsnoop
> >slave.pcm "hw:0,0"
> >}
> >
> >#and this is the real magic
> >pcm.asymed {
> >type asym
> >playback.pcm "dmixed"
> >capture.pcm "dsnooped"
> >}
> >
> >#a quick plug plugin for above device to do the converting magic
> >pcm.pasymed {
> >type plug
> >slave.pcm "asymed"
> >}
> >
> >#a ctl device to keep xmms happy
> >ctl.pasymed {
> >type hw
> >card 0
> >}
> >
> >#for aoss:
> >pcm.dsp0 {
> >type plug
> >slave.pcm "asymed"
> >}
> >
> >ctl.mixer0 {
> >type hw
> >card 0
> >}
> >
> ># alsa default card
> >pcm.!default {
> > type plug
> > slave.pcm "asymed"
> >}
> >#done
> >
> >El Vie 09 Jul 2004 18:37, Chris Metcalf escribió:
> >>Has anybody had a good experience getting the Dmix plugin working
> >>well with ALSA?
> >>
> >>I'm trying to get my laptop (Thinkpad X31 using the snd_intel8x0
> >> ALSA module) to be able to play more than one wave channel at
> >> once, but I'm not having much success.
> >>
> >>Any helpful direction (howtos, good/bad experiences, alternate
> >>methods) would be appreciated.
> >>
> >>Thanks,
> >>--
> >>Chris Metcalf
> >>[EMAIL PROTECTED]
> >>http://chrismetcalf.net
--
Atentamente,
Nicolás Velásquez
Bogotá, Colombia
(^) ASCII Ribbon Campaign
X NO HTML/RTF in e-mail
/ \ NO Word docs in e-mail
Re: ALSA / DMIX
First, why use xmms when Alsaplayer is so cool? Its really good IMHO.
Alsa is great, especially if you are a musician or work with midi or
such. Nothing beats it.
For mplayer, hmm... mine works and is self compiled, make sure you have
your kernel source compiled and supposedly it will detect alsa headers
and such. Even if if has to use oss fallback that should still work ok.
It took me some tinkering around to get alsa working on my system but it
is definately superior to anything else around. If it even works at all
then thats a real good sign.
Tip: try killing esd if its running, there's some bug with it that it
grabs /dev/dsp and locks it so it really screws up alsa apps.
Tip2: compile your kernel with static sound, (no modules), debian alsa
will grumble a bit about no modules found but it all should work. A
static kernel sometimes isn't a bad idea for a laptop since your
hardware is known and immutable. I usually build all static support for
laptop internal devices and modules for pluggable things like USB,
serial, parallel, etc.
- Doug
Nicolás Velásquez O. wrote:
Hello there,
My system:
- Dell, Inspiron 5100
- Debian sarge
- snd_intel8x0
- Self compiled kernel 2.6.7
I've had not so nice experiences (neither dmix nor asym) with it:
- Using xmms, if there is a lot of disk usage, audio will stop playing.
- Using (self compiled) mplayer, the audio won't play well.
Solutions: (better solutions are welcome!!)
- xmms, use xmms through arts (and arts through alsa)
- MPlayer, give cache to the default alsa device.
Solutions drawbacks:
- xmms, arts ain't that good, some audio files will play lossy.
- MPlayer, none.
Links:
http://alsa.opensrc.org/index.php?page=DmixPlugin
http://alsa.opensrc.org/index.php?page=asym
My /etc/asound.conf:
#asym fun start here. we define one pcm device called "dmixed"
pcm.dmixed {
type dmix
ipc_key 1025
slave {
pcm "hw:0,0" # you cannot use a "plug" device
#here,darn.
period_time 0
period_size 1024 # must be power of 2
buffer_size 8192 # dito. It
#format "S32_LE"
#periods 128 # dito.
#rate 8000# with rate 8000 you *will* hear,
# if ossmix is used :)
}
bindings {
0 0
1 1
}
}
#one called "dsnooped" for capturing
pcm.dsnooped {
ipc_key 1027
type dsnoop
slave.pcm "hw:0,0"
}
#and this is the real magic
pcm.asymed {
type asym
playback.pcm "dmixed"
capture.pcm "dsnooped"
}
#a quick plug plugin for above device to do the converting magic
pcm.pasymed {
type plug
slave.pcm "asymed"
}
#a ctl device to keep xmms happy
ctl.pasymed {
type hw
card 0
}
#for aoss:
pcm.dsp0 {
type plug
slave.pcm "asymed"
}
ctl.mixer0 {
type hw
card 0
}
# alsa default card
pcm.!default {
type plug
slave.pcm "asymed"
}
#done
El Vie 09 Jul 2004 18:37, Chris Metcalf escribió:
Has anybody had a good experience getting the Dmix plugin working
well with ALSA?
I'm trying to get my laptop (Thinkpad X31 using the snd_intel8x0 ALSA
module) to be able to play more than one wave channel at once, but
I'm not having much success.
Any helpful direction (howtos, good/bad experiences, alternate
methods) would be appreciated.
Thanks,
--
Chris Metcalf
[EMAIL PROTECTED]
http://chrismetcalf.net
Re: ALSA / DMIX
On Fri, Jul 09, 2004 at 04:37:26PM -0700, Chris Metcalf wrote:
> Has anybody had a good experience getting the Dmix plugin working well
> with ALSA?
>
> I'm trying to get my laptop (Thinkpad X31 using the snd_intel8x0 ALSA
> module) to be able to play more than one wave channel at once, but I'm
> not having much success.
>
> Any helpful direction (howtos, good/bad experiences, alternate
> methods) would be appreciated.
I use the same module and this is my ~/.asoundrc (same as the howtos on
alsa-project.org[1]):
-8<-
pcm.!default {
type plug
slave.pcm "dmixer"
}
pcm.dsp0 {
type plug
slave.pcm "dmixer"
}
pcm.dmixer {
type dmix
ipc_key 321456
ipc_key_add_uid true
slave {
pcm "hw:0,0"
period_time 0
period_size 1024
buffer_size 4096
rate 48000
}
bindings {
0 0
1 1
}
}
ctl.dmixer {
type hw
card 0
}
-8<-
for mplayer I simply use this ~/.mplayer/config:
-8<-
vo=xv
ao=alsa1x:default
#stop_xscreensaver=1
cat: ~./mplayer/config: No such file or directory
-8<-
while xmms is already configured to use alsa default pcm
the pcm.dsp0 allows using dmix also through oss emulation so mpg123 is
happy too. Note: I have no sound server installed and dmix is working
great :)
[1]:
http://alsa.opensrc.org/index.php?page=DmixPlugin
http://www.alsa-project.org/alsa-doc/alsa-lib/pcm_plugins.html
--
mattia
:wq!
Re: ALSA / DMIX
First, why use xmms when Alsaplayer is so cool? Its really good IMHO.
Alsa is great, especially if you are a musician or work with midi or
such. Nothing beats it.
For mplayer, hmm... mine works and is self compiled, make sure you have
your kernel source compiled and supposedly it will detect alsa headers
and such. Even if if has to use oss fallback that should still work ok.
It took me some tinkering around to get alsa working on my system but it
is definately superior to anything else around. If it even works at all
then thats a real good sign.
Tip: try killing esd if its running, there's some bug with it that it
grabs /dev/dsp and locks it so it really screws up alsa apps.
Tip2: compile your kernel with static sound, (no modules), debian alsa
will grumble a bit about no modules found but it all should work. A
static kernel sometimes isn't a bad idea for a laptop since your
hardware is known and immutable. I usually build all static support for
laptop internal devices and modules for pluggable things like USB,
serial, parallel, etc.
- Doug
Nicolás Velásquez O. wrote:
Hello there,
My system:
- Dell, Inspiron 5100
- Debian sarge
- snd_intel8x0
- Self compiled kernel 2.6.7
I've had not so nice experiences (neither dmix nor asym) with it:
- Using xmms, if there is a lot of disk usage, audio will stop playing.
- Using (self compiled) mplayer, the audio won't play well.
Solutions: (better solutions are welcome!!)
- xmms, use xmms through arts (and arts through alsa)
- MPlayer, give cache to the default alsa device.
Solutions drawbacks:
- xmms, arts ain't that good, some audio files will play lossy.
- MPlayer, none.
Links:
http://alsa.opensrc.org/index.php?page=DmixPlugin
http://alsa.opensrc.org/index.php?page=asym
My /etc/asound.conf:
#asym fun start here. we define one pcm device called "dmixed"
pcm.dmixed {
type dmix
ipc_key 1025
slave {
pcm "hw:0,0" # you cannot use a "plug" device
#here,darn.
period_time 0
period_size 1024 # must be power of 2
buffer_size 8192 # dito. It
#format "S32_LE"
#periods 128 # dito.
#rate 8000# with rate 8000 you *will* hear,
# if ossmix is used :)
}
bindings {
0 0
1 1
}
}
#one called "dsnooped" for capturing
pcm.dsnooped {
ipc_key 1027
type dsnoop
slave.pcm "hw:0,0"
}
#and this is the real magic
pcm.asymed {
type asym
playback.pcm "dmixed"
capture.pcm "dsnooped"
}
#a quick plug plugin for above device to do the converting magic
pcm.pasymed {
type plug
slave.pcm "asymed"
}
#a ctl device to keep xmms happy
ctl.pasymed {
type hw
card 0
}
#for aoss:
pcm.dsp0 {
type plug
slave.pcm "asymed"
}
ctl.mixer0 {
type hw
card 0
}
# alsa default card
pcm.!default {
type plug
slave.pcm "asymed"
}
#done
El Vie 09 Jul 2004 18:37, Chris Metcalf escribió:
Has anybody had a good experience getting the Dmix plugin working
well with ALSA?
I'm trying to get my laptop (Thinkpad X31 using the snd_intel8x0 ALSA
module) to be able to play more than one wave channel at once, but
I'm not having much success.
Any helpful direction (howtos, good/bad experiences, alternate
methods) would be appreciated.
Thanks,
--
Chris Metcalf
[EMAIL PROTECTED]
http://chrismetcalf.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA / DMIX
On Fri, Jul 09, 2004 at 04:37:26PM -0700, Chris Metcalf wrote:
> Has anybody had a good experience getting the Dmix plugin working well
> with ALSA?
>
> I'm trying to get my laptop (Thinkpad X31 using the snd_intel8x0 ALSA
> module) to be able to play more than one wave channel at once, but I'm
> not having much success.
>
> Any helpful direction (howtos, good/bad experiences, alternate
> methods) would be appreciated.
I use the same module and this is my ~/.asoundrc (same as the howtos on
alsa-project.org[1]):
-8<-
pcm.!default {
type plug
slave.pcm "dmixer"
}
pcm.dsp0 {
type plug
slave.pcm "dmixer"
}
pcm.dmixer {
type dmix
ipc_key 321456
ipc_key_add_uid true
slave {
pcm "hw:0,0"
period_time 0
period_size 1024
buffer_size 4096
rate 48000
}
bindings {
0 0
1 1
}
}
ctl.dmixer {
type hw
card 0
}
-8<-
for mplayer I simply use this ~/.mplayer/config:
-8<-
vo=xv
ao=alsa1x:default
#stop_xscreensaver=1
cat: ~./mplayer/config: No such file or directory
-8<-
while xmms is already configured to use alsa default pcm
the pcm.dsp0 allows using dmix also through oss emulation so mpg123 is
happy too. Note: I have no sound server installed and dmix is working
great :)
[1]:
http://alsa.opensrc.org/index.php?page=DmixPlugin
http://www.alsa-project.org/alsa-doc/alsa-lib/pcm_plugins.html
--
mattia
:wq!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA / DMIX
Hello there,
My system:
- Dell, Inspiron 5100
- Debian sarge
- snd_intel8x0
- Self compiled kernel 2.6.7
I've had not so nice experiences (neither dmix nor asym) with it:
- Using xmms, if there is a lot of disk usage, audio will stop playing.
- Using (self compiled) mplayer, the audio won't play well.
Solutions: (better solutions are welcome!!)
- xmms, use xmms through arts (and arts through alsa)
- MPlayer, give cache to the default alsa device.
Solutions drawbacks:
- xmms, arts ain't that good, some audio files will play lossy.
- MPlayer, none.
Links:
http://alsa.opensrc.org/index.php?page=DmixPlugin
http://alsa.opensrc.org/index.php?page=asym
My /etc/asound.conf:
#asym fun start here. we define one pcm device called "dmixed"
pcm.dmixed {
type dmix
ipc_key 1025
slave {
pcm "hw:0,0" # you cannot use a "plug" device
#here,darn.
period_time 0
period_size 1024 # must be power of 2
buffer_size 8192 # dito. It
#format "S32_LE"
#periods 128 # dito.
#rate 8000# with rate 8000 you *will* hear,
# if ossmix is used :)
}
bindings {
0 0
1 1
}
}
#one called "dsnooped" for capturing
pcm.dsnooped {
ipc_key 1027
type dsnoop
slave.pcm "hw:0,0"
}
#and this is the real magic
pcm.asymed {
type asym
playback.pcm "dmixed"
capture.pcm "dsnooped"
}
#a quick plug plugin for above device to do the converting magic
pcm.pasymed {
type plug
slave.pcm "asymed"
}
#a ctl device to keep xmms happy
ctl.pasymed {
type hw
card 0
}
#for aoss:
pcm.dsp0 {
type plug
slave.pcm "asymed"
}
ctl.mixer0 {
type hw
card 0
}
# alsa default card
pcm.!default {
type plug
slave.pcm "asymed"
}
#done
El Vie 09 Jul 2004 18:37, Chris Metcalf escribió:
> Has anybody had a good experience getting the Dmix plugin working
> well with ALSA?
>
> I'm trying to get my laptop (Thinkpad X31 using the snd_intel8x0 ALSA
> module) to be able to play more than one wave channel at once, but
> I'm not having much success.
>
> Any helpful direction (howtos, good/bad experiences, alternate
> methods) would be appreciated.
>
> Thanks,
> --
> Chris Metcalf
> [EMAIL PROTECTED]
> http://chrismetcalf.net
--
Atentamente,
Nicolás Velásquez
Bogotá, Colombia
(^) ASCII Ribbon Campaign
X NO HTML/RTF in e-mail
/ \ NO Word docs in e-mail
Re: ALSA / DMIX
Hello there,
My system:
- Dell, Inspiron 5100
- Debian sarge
- snd_intel8x0
- Self compiled kernel 2.6.7
I've had not so nice experiences (neither dmix nor asym) with it:
- Using xmms, if there is a lot of disk usage, audio will stop playing.
- Using (self compiled) mplayer, the audio won't play well.
Solutions: (better solutions are welcome!!)
- xmms, use xmms through arts (and arts through alsa)
- MPlayer, give cache to the default alsa device.
Solutions drawbacks:
- xmms, arts ain't that good, some audio files will play lossy.
- MPlayer, none.
Links:
http://alsa.opensrc.org/index.php?page=DmixPlugin
http://alsa.opensrc.org/index.php?page=asym
My /etc/asound.conf:
#asym fun start here. we define one pcm device called "dmixed"
pcm.dmixed {
type dmix
ipc_key 1025
slave {
pcm "hw:0,0" # you cannot use a "plug" device
#here,darn.
period_time 0
period_size 1024 # must be power of 2
buffer_size 8192 # dito. It
#format "S32_LE"
#periods 128 # dito.
#rate 8000# with rate 8000 you *will* hear,
# if ossmix is used :)
}
bindings {
0 0
1 1
}
}
#one called "dsnooped" for capturing
pcm.dsnooped {
ipc_key 1027
type dsnoop
slave.pcm "hw:0,0"
}
#and this is the real magic
pcm.asymed {
type asym
playback.pcm "dmixed"
capture.pcm "dsnooped"
}
#a quick plug plugin for above device to do the converting magic
pcm.pasymed {
type plug
slave.pcm "asymed"
}
#a ctl device to keep xmms happy
ctl.pasymed {
type hw
card 0
}
#for aoss:
pcm.dsp0 {
type plug
slave.pcm "asymed"
}
ctl.mixer0 {
type hw
card 0
}
# alsa default card
pcm.!default {
type plug
slave.pcm "asymed"
}
#done
El Vie 09 Jul 2004 18:37, Chris Metcalf escribió:
> Has anybody had a good experience getting the Dmix plugin working
> well with ALSA?
>
> I'm trying to get my laptop (Thinkpad X31 using the snd_intel8x0 ALSA
> module) to be able to play more than one wave channel at once, but
> I'm not having much success.
>
> Any helpful direction (howtos, good/bad experiences, alternate
> methods) would be appreciated.
>
> Thanks,
> --
> Chris Metcalf
> [EMAIL PROTECTED]
> http://chrismetcalf.net
--
Atentamente,
Nicolás Velásquez
Bogotá, Colombia
(^) ASCII Ribbon Campaign
X NO HTML/RTF in e-mail
/ \ NO Word docs in e-mail
Re: alsa prob on sid vaio r505
On Thu, 25 Mar 2004, Christer Stenbrenden wrote: > After a closer look it seems like you configured alsa to be built into > the kernel, and not as modules. Yes, I guess I did... with the problems (solved below, BTW) I guess I wasn't thinking. > if this is so then everything should be up and running. _Should_... and would have been, had I been a member of the audio group (doh!) and the cdrom group (to play the cd in xmms). The speaker at the top of the Gnome desktop said there was no audio device so... > btw. everything is by default muted in alsa, so use alsamixer or > something to raise the volume. Yeah, I forgot to mention that I had done this... but thanks again for the info. Now on to the next issue on the laptop, dvd watching. Thanks for all the help, rdc -- Robert D. Crawford [EMAIL PROTECTED] ...it could be well said that a country, preserved at the sacrifice of all the cardinal principles of liberty, is not worth the cost of preservation. Happily, it is not so. EX PARTE MILLIGAN (1866)
Re: alsa prob on sid vaio r505
On Thu, 25 Mar 2004, Christer Stenbrenden wrote: > After a closer look it seems like you configured alsa to be built into > the kernel, and not as modules. Yes, I guess I did... with the problems (solved below, BTW) I guess I wasn't thinking. > if this is so then everything should be up and running. _Should_... and would have been, had I been a member of the audio group (doh!) and the cdrom group (to play the cd in xmms). The speaker at the top of the Gnome desktop said there was no audio device so... > btw. everything is by default muted in alsa, so use alsamixer or > something to raise the volume. Yeah, I forgot to mention that I had done this... but thanks again for the info. Now on to the next issue on the laptop, dvd watching. Thanks for all the help, rdc -- Robert D. Crawford [EMAIL PROTECTED] ...it could be well said that a country, preserved at the sacrifice of all the cardinal principles of liberty, is not worth the cost of preservation. Happily, it is not so. EX PARTE MILLIGAN (1866) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: alsa prob on sid vaio r505
On Wed, Mar 24, 2004 at 05:09:56 -0600, Robert D. Crawford wrote: Well, I really need to slow down :-) After a closer look it seems like you configured alsa to be built into the kernel, and not as modules. check 'dmesg | more' for anything related to ALSA and intel8x0 if this is so then everything should be up and running. but do not load the i810_audio module if it is present; it will only interfere. btw. everything is by default muted in alsa, so use alsamixer or something to raise the volume. christer.
Re: alsa prob on sid vaio r505
On Wed, Mar 24, 2004 at 05:09:56 -0600, Robert D. Crawford wrote: > On Wed, 24 Mar 2004, Christer Stenbrenden wrote: > > Thanks for the reply. Alas, no joy. > > laptop:/usr/src/kernel-source-2.6.4# modprobe intel8x0 > FATAL: Module intel8x0 not found. > laptop:/usr/src/kernel-source-2.6.4# modprobe snd-intel8x0 > FATAL: Module snd_intel8x0 not found. > laptop:/usr/src/kernel-source-2.6.4# auch. i made a typo in my previous mail... try modprobe snd-intel8x0 christer
Re: alsa prob on sid vaio r505
On Wed, 24 Mar 2004, Christer Stenbrenden wrote: Thanks for the reply. Alas, no joy. laptop:/usr/src/kernel-source-2.6.4# modprobe intel8x0 FATAL: Module intel8x0 not found. laptop:/usr/src/kernel-source-2.6.4# modprobe snd-intel8x0 FATAL: Module snd_intel8x0 not found. laptop:/usr/src/kernel-source-2.6.4# > try this instead: modprobe intel8x0 > > i think i810_audio is the old OSS driver > > regards, > > christer -- Robert D. Crawford [EMAIL PROTECTED] ...it could be well said that a country, preserved at the sacrifice of all the cardinal principles of liberty, is not worth the cost of preservation. Happily, it is not so. EX PARTE MILLIGAN (1866)
Re: alsa prob on sid vaio r505
On Wed, Mar 24, 2004 at 12:25:19 -0600, Robert D. Crawford wrote: > laptop:/usr/src/kernel-source-2.6.4# modprobe i810_audio > FATAL: Module i810_audio not found. > laptop:/usr/src/kernel-source-2.6.4# locate i810_audio > /lib/modules/2.4.18-bf2.4/kernel/drivers/sound/i810_audio.o > /usr/src/kernel-source-2.6.4/sound/oss/i810_audio.c > laptop:/usr/src/kernel-source-2.6.4# > > laptop:/usr/src/kernel-source-2.6.4# grep i810 /var/log/messages > Mar 22 07:45:40 laptop kernel: [drm] AGP 0.99 on Intel i810 @ 0xe800 > 128MB > Mar 22 07:45:40 laptop kernel: [drm] Initialized i810 1.1.0 20010616 on > minor 0 > Mar 22 07:45:40 laptop kernel: i810: Intel ICH3 found at IO 0x18c0 and > 0x1c00, IRQ 9 > Mar 22 07:45:40 laptop kernel: i810_audio: Audio Controller supports 6 > channels.Mar 22 07:45:40 laptop kernel: i810_audio: only 48Khz playback > available. > Mar 22 07:45:40 laptop kernel: i810_audio: AC'97 codec 0 supports AMAP, > total channels = 2 > Mar 22 07:45:40 laptop kernel: i810_audio: timed out waiting for codec 1 > analog ready. > laptop:/usr/src/kernel-source-2.6.4# > > What am I missing here? try this instead: modprobe intel8x0 i think i810_audio is the old OSS driver regards, christer
Re: alsa prob on sid vaio r505
On Wed, Mar 24, 2004 at 05:09:56 -0600, Robert D. Crawford wrote: Well, I really need to slow down :-) After a closer look it seems like you configured alsa to be built into the kernel, and not as modules. check 'dmesg | more' for anything related to ALSA and intel8x0 if this is so then everything should be up and running. but do not load the i810_audio module if it is present; it will only interfere. btw. everything is by default muted in alsa, so use alsamixer or something to raise the volume. christer. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: alsa prob on sid vaio r505
On Wed, Mar 24, 2004 at 05:09:56 -0600, Robert D. Crawford wrote: > On Wed, 24 Mar 2004, Christer Stenbrenden wrote: > > Thanks for the reply. Alas, no joy. > > laptop:/usr/src/kernel-source-2.6.4# modprobe intel8x0 > FATAL: Module intel8x0 not found. > laptop:/usr/src/kernel-source-2.6.4# modprobe snd-intel8x0 > FATAL: Module snd_intel8x0 not found. > laptop:/usr/src/kernel-source-2.6.4# auch. i made a typo in my previous mail... try modprobe snd-intel8x0 christer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: alsa prob on sid vaio r505
On Wed, 24 Mar 2004, Christer Stenbrenden wrote: Thanks for the reply. Alas, no joy. laptop:/usr/src/kernel-source-2.6.4# modprobe intel8x0 FATAL: Module intel8x0 not found. laptop:/usr/src/kernel-source-2.6.4# modprobe snd-intel8x0 FATAL: Module snd_intel8x0 not found. laptop:/usr/src/kernel-source-2.6.4# > try this instead: modprobe intel8x0 > > i think i810_audio is the old OSS driver > > regards, > > christer -- Robert D. Crawford [EMAIL PROTECTED] ...it could be well said that a country, preserved at the sacrifice of all the cardinal principles of liberty, is not worth the cost of preservation. Happily, it is not so. EX PARTE MILLIGAN (1866) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: alsa prob on sid vaio r505
On Wed, Mar 24, 2004 at 12:25:19 -0600, Robert D. Crawford wrote: > laptop:/usr/src/kernel-source-2.6.4# modprobe i810_audio > FATAL: Module i810_audio not found. > laptop:/usr/src/kernel-source-2.6.4# locate i810_audio > /lib/modules/2.4.18-bf2.4/kernel/drivers/sound/i810_audio.o > /usr/src/kernel-source-2.6.4/sound/oss/i810_audio.c > laptop:/usr/src/kernel-source-2.6.4# > > laptop:/usr/src/kernel-source-2.6.4# grep i810 /var/log/messages > Mar 22 07:45:40 laptop kernel: [drm] AGP 0.99 on Intel i810 @ 0xe800 > 128MB > Mar 22 07:45:40 laptop kernel: [drm] Initialized i810 1.1.0 20010616 on > minor 0 > Mar 22 07:45:40 laptop kernel: i810: Intel ICH3 found at IO 0x18c0 and > 0x1c00, IRQ 9 > Mar 22 07:45:40 laptop kernel: i810_audio: Audio Controller supports 6 > channels.Mar 22 07:45:40 laptop kernel: i810_audio: only 48Khz playback > available. > Mar 22 07:45:40 laptop kernel: i810_audio: AC'97 codec 0 supports AMAP, > total channels = 2 > Mar 22 07:45:40 laptop kernel: i810_audio: timed out waiting for codec 1 > analog ready. > laptop:/usr/src/kernel-source-2.6.4# > > What am I missing here? try this instead: modprobe intel8x0 i think i810_audio is the old OSS driver regards, christer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA modules problem
On Thu, 2003-07-31 at 11:43, Abhay Pradhan wrote: > Hi I'm running debian on a Dell inspiron 5100 laptop. > I've a custom kernel v 2.4.20 with the ACPI patch working. > > I wanted to get sound working on my laptop. > My laptop has the Intel 810 and the module is i810 > > this is the relevant dmesg output > > * > Intel 810 + AC97 Audio, version 0.21, 08:36:18 Jul 31 2003 > PCI: Setting latency timer of device 00:1f.5 to 64 > i810: Intel ICH4 found at IO 0x1c80 and 0x1400, IRQ 10 > i810_audio: Audio Controller supports 6 channels. > ac97_codec: AC97 Audio codec, id: v80(Unknown) > i810_audio: AC'97 codec 0 supports AMAP, total channels = 2 > ac97_codec: AC97 Modem codec, id: CXT34(Unknown) > i810_audio: timed out waiting for codec 1 analog ready. > > > I installed alsa-source, alsa-base, alsa-utils and alsa-xmms (all 0.9.4-1) > > then I recompiled my kernel with sound card support and selected my > module, I then did a make-kpkg for both kernel_image and > modules_image. > > the problem I have is when I try and install alsa-modules > > Here is the error I get > *** > herenya:/usr/src# dpkg -i > alsa-modules-2.4.20.07312003.1330_0.9.4-1+10.00.Custom_i386.deb > (Reading database ... 21862 files and directories currently >installed.) > Preparing to replace alsa-modules-2.4.20.07312003.1330 > 0.9.4-1+10.00.Custom (using > > alsa-modules-2.4.20.07312003.1330_0.9.4-1+10.00.Custom_i386.deb) > ... > Unpacking replacement alsa-modules-2.4.20.07312003.1330 ... > Setting up alsa-modules-2.4.20.07312003.1330 (0.9.4-1+10.00.Custom) > ... > Configuration file for ALSA 0.9 exists. > Attempting to start. > > Shutting down ALSA (unknown version): not running > Starting ALSA (unknown version): failed - ALSA modules not installed > invoke-rc.d: initscript alsa, action "restart" failed. > dpkg: error processing alsa-modules-2.4.20.07312003.1330 (--install): > subprocess post-installation script returned error exit status 1 > Errors were encountered while processing: > alsa-modules-2.4.20.07312003.1330 > *** > > > i have no idea what to do next. > Any help would be greatly appreciated! > > abhay > First of all, in the kernel configuration, configure alsa (sound support) as a module and don't select your card or anything else under it. For alsa, iirc there was some problem in the settings file with the module names, but don't remember where and don't know if it was solved. Also, make a link to /etc/alsa/modutils/0.9 under /etc/modutils, and then run update-modules (make sure that the entrees then appear under /etc/modules.conf).
Re: ALSA modules problem
On Thu, 2003-07-31 at 11:43, Abhay Pradhan wrote: > Hi I'm running debian on a Dell inspiron 5100 laptop. > I've a custom kernel v 2.4.20 with the ACPI patch working. > > I wanted to get sound working on my laptop. > My laptop has the Intel 810 and the module is i810 > > this is the relevant dmesg output > > * > Intel 810 + AC97 Audio, version 0.21, 08:36:18 Jul 31 2003 > PCI: Setting latency timer of device 00:1f.5 to 64 > i810: Intel ICH4 found at IO 0x1c80 and 0x1400, IRQ 10 > i810_audio: Audio Controller supports 6 channels. > ac97_codec: AC97 Audio codec, id: v80(Unknown) > i810_audio: AC'97 codec 0 supports AMAP, total channels = 2 > ac97_codec: AC97 Modem codec, id: CXT34(Unknown) > i810_audio: timed out waiting for codec 1 analog ready. > > > I installed alsa-source, alsa-base, alsa-utils and alsa-xmms (all 0.9.4-1) > > then I recompiled my kernel with sound card support and selected my > module, I then did a make-kpkg for both kernel_image and > modules_image. > > the problem I have is when I try and install alsa-modules > > Here is the error I get > *** > herenya:/usr/src# dpkg -i > alsa-modules-2.4.20.07312003.1330_0.9.4-1+10.00.Custom_i386.deb > (Reading database ... 21862 files and directories currently >installed.) > Preparing to replace alsa-modules-2.4.20.07312003.1330 > 0.9.4-1+10.00.Custom (using > > alsa-modules-2.4.20.07312003.1330_0.9.4-1+10.00.Custom_i386.deb) > ... > Unpacking replacement alsa-modules-2.4.20.07312003.1330 ... > Setting up alsa-modules-2.4.20.07312003.1330 (0.9.4-1+10.00.Custom) > ... > Configuration file for ALSA 0.9 exists. > Attempting to start. > > Shutting down ALSA (unknown version): not running > Starting ALSA (unknown version): failed - ALSA modules not installed > invoke-rc.d: initscript alsa, action "restart" failed. > dpkg: error processing alsa-modules-2.4.20.07312003.1330 (--install): > subprocess post-installation script returned error exit status 1 > Errors were encountered while processing: > alsa-modules-2.4.20.07312003.1330 > *** > > > i have no idea what to do next. > Any help would be greatly appreciated! > > abhay > First of all, in the kernel configuration, configure alsa (sound support) as a module and don't select your card or anything else under it. For alsa, iirc there was some problem in the settings file with the module names, but don't remember where and don't know if it was solved. Also, make a link to /etc/alsa/modutils/0.9 under /etc/modutils, and then run update-modules (make sure that the entrees then appear under /etc/modules.conf). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: alsa-source invalid group
Micha Feigin, 2003-Jul-24 23:41 +0300: > If this is the debian alsa-source package look under > /usr/share/doc/alsa-source/README.gz for directions. > > Specificly enter you kernel's top directory and enter > make-kpkg --revision 0.1 --added-modules alsa-driver modules_image > > either as root or using fakeroot. > > This will create the drivers package one directory above. > > This worked for me for 2.4 kernels. > > 2.5 and 2.6 have alsa as part of the kernel. > > good luck Thanks, I didn't realize this was the case. I use kernel-package to compile my kernels too. I'll give it a go this evening. jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User
Re: alsa-source invalid group
On Wed, 2003-07-23 at 23:22, David Z Maze wrote: > Jeff <[EMAIL PROTECTED]> writes: > > > I'm trying to compile the alsa-source in testing and having a > > problem. > > > > I run ./configure and then make without trouble. When I run make > > install, I get this error: > > The Debian kernel module source packages are generally intended to be > built via 'make-kpkg modules-image', from the kernel-package package. > You might look at what debian/rules does for the kdist-image target to > see if anything particularly magical happens. > > > > > if [ -d /sbin/init.d ]; then \ > > install -m 755 -g -o utils/alsasound /sbin/init.d/alsasound; \ > > elif [ -d /etc/rc.d/init.d ]; then \ > > install -m 755 -g -o utils/alsasound /etc/rc.d/init.d/alsasound; \ > > elif [ -d /etc/init.d ]; then \ > > install -m 755 -g -o utils/alsasound /etc/init.d/alsasound; \ > > fi > > ...this is installing userspace stuff, not the kernel drivers, so in > principle you shouldn't be running this code at all. > > (I know that for lm-sensors, which I maintain, the kernel source > package doesn't include a lot of the userspace code, so if you don't > either use kernel-package or read the directions in README.Debian your > build will completely lose. I do this for two reasons: to reduce the > size of the lm-sensors-source package, and so that it won't need to > depend on other development packages that aren't needed for the kernel > modules.) > > -- > David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ > "Theoretical politics is interesting. Politicking should be illegal." > -- Abra Mitchell > If this is the debian alsa-source package look under /usr/share/doc/alsa-source/README.gz for directions. Specificly enter you kernel's top directory and enter make-kpkg --revision 0.1 --added-modules alsa-driver modules_image either as root or using fakeroot. This will create the drivers package one directory above. This worked for me for 2.4 kernels. 2.5 and 2.6 have alsa as part of the kernel. good luck
Re: alsa-source invalid group
Micha Feigin, 2003-Jul-24 23:41 +0300: > If this is the debian alsa-source package look under > /usr/share/doc/alsa-source/README.gz for directions. > > Specificly enter you kernel's top directory and enter > make-kpkg --revision 0.1 --added-modules alsa-driver modules_image > > either as root or using fakeroot. > > This will create the drivers package one directory above. > > This worked for me for 2.4 kernels. > > 2.5 and 2.6 have alsa as part of the kernel. > > good luck Thanks, I didn't realize this was the case. I use kernel-package to compile my kernels too. I'll give it a go this evening. jc -- Jeff CoppockSystems Engineer Diggin' Debian Admin and User -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: alsa-source invalid group
On Wed, 2003-07-23 at 23:22, David Z Maze wrote: > Jeff <[EMAIL PROTECTED]> writes: > > > I'm trying to compile the alsa-source in testing and having a > > problem. > > > > I run ./configure and then make without trouble. When I run make > > install, I get this error: > > The Debian kernel module source packages are generally intended to be > built via 'make-kpkg modules-image', from the kernel-package package. > You might look at what debian/rules does for the kdist-image target to > see if anything particularly magical happens. > > > > > if [ -d /sbin/init.d ]; then \ > > install -m 755 -g -o utils/alsasound /sbin/init.d/alsasound; \ > > elif [ -d /etc/rc.d/init.d ]; then \ > > install -m 755 -g -o utils/alsasound /etc/rc.d/init.d/alsasound; \ > > elif [ -d /etc/init.d ]; then \ > > install -m 755 -g -o utils/alsasound /etc/init.d/alsasound; \ > > fi > > ...this is installing userspace stuff, not the kernel drivers, so in > principle you shouldn't be running this code at all. > > (I know that for lm-sensors, which I maintain, the kernel source > package doesn't include a lot of the userspace code, so if you don't > either use kernel-package or read the directions in README.Debian your > build will completely lose. I do this for two reasons: to reduce the > size of the lm-sensors-source package, and so that it won't need to > depend on other development packages that aren't needed for the kernel > modules.) > > -- > David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ > "Theoretical politics is interesting. Politicking should be illegal." > -- Abra Mitchell > If this is the debian alsa-source package look under /usr/share/doc/alsa-source/README.gz for directions. Specificly enter you kernel's top directory and enter make-kpkg --revision 0.1 --added-modules alsa-driver modules_image either as root or using fakeroot. This will create the drivers package one directory above. This worked for me for 2.4 kernels. 2.5 and 2.6 have alsa as part of the kernel. good luck -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: alsa-source invalid group
On Wed, Jul 23, 2003 at 08:05:49PM +0200, Tommy Dugandzic wrote: > On Wed, 23 Jul 2003, Jeff wrote: > > > I'm trying to compile the alsa-source in testing and having a > > problem. > > > > I run ./configure and then make without trouble. When I run make > > install, I get this error: > > > > > > if [ -d /sbin/init.d ]; then \ > > install -m 755 -g -o utils/alsasound /sbin/init.d/alsasound; \ > > elif [ -d /etc/rc.d/init.d ]; then \ > > install -m 755 -g -o utils/alsasound /etc/rc.d/init.d/alsasound; \ > > elif [ -d /etc/init.d ]; then \ > > install -m 755 -g -o utils/alsasound /etc/init.d/alsasound; \ > > fi > > install: invalid group `-o' > > make: *** [install-scripts] Error 1 > > root # > > > > > > I have a self-compile 2.4.21 kernel running. > > > > I can't figure this out, nor can I find anything googling yet. Anyone > > have an idea on how to get past this? > > I ran a "install --help" which told me this relevant line: > > -g, --group=GROUP set group ownership, instead of process' current > group > he's probably using the debian source packages. They are packaged to be compiled the *debian way* with make-kpkg. I'd suggest to download alsa sources from www.alsa-project.org and try to compile those or to compile kernel and external modules with make-kpkg (very easy). -- mattia :wq!
Re: alsa-source invalid group
Jeff <[EMAIL PROTECTED]> writes: > I'm trying to compile the alsa-source in testing and having a > problem. > > I run ./configure and then make without trouble. When I run make > install, I get this error: The Debian kernel module source packages are generally intended to be built via 'make-kpkg modules-image', from the kernel-package package. You might look at what debian/rules does for the kdist-image target to see if anything particularly magical happens. > > if [ -d /sbin/init.d ]; then \ > install -m 755 -g -o utils/alsasound /sbin/init.d/alsasound; \ > elif [ -d /etc/rc.d/init.d ]; then \ > install -m 755 -g -o utils/alsasound /etc/rc.d/init.d/alsasound; \ > elif [ -d /etc/init.d ]; then \ > install -m 755 -g -o utils/alsasound /etc/init.d/alsasound; \ > fi ...this is installing userspace stuff, not the kernel drivers, so in principle you shouldn't be running this code at all. (I know that for lm-sensors, which I maintain, the kernel source package doesn't include a lot of the userspace code, so if you don't either use kernel-package or read the directions in README.Debian your build will completely lose. I do this for two reasons: to reduce the size of the lm-sensors-source package, and so that it won't need to depend on other development packages that aren't needed for the kernel modules.) -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ "Theoretical politics is interesting. Politicking should be illegal." -- Abra Mitchell
Re: alsa-source invalid group
On Wed, Jul 23, 2003 at 08:05:49PM +0200, Tommy Dugandzic wrote: > On Wed, 23 Jul 2003, Jeff wrote: > > > I'm trying to compile the alsa-source in testing and having a > > problem. > > > > I run ./configure and then make without trouble. When I run make > > install, I get this error: > > > > > > if [ -d /sbin/init.d ]; then \ > > install -m 755 -g -o utils/alsasound /sbin/init.d/alsasound; \ > > elif [ -d /etc/rc.d/init.d ]; then \ > > install -m 755 -g -o utils/alsasound /etc/rc.d/init.d/alsasound; \ > > elif [ -d /etc/init.d ]; then \ > > install -m 755 -g -o utils/alsasound /etc/init.d/alsasound; \ > > fi > > install: invalid group `-o' > > make: *** [install-scripts] Error 1 > > root # > > > > > > I have a self-compile 2.4.21 kernel running. > > > > I can't figure this out, nor can I find anything googling yet. Anyone > > have an idea on how to get past this? > > I ran a "install --help" which told me this relevant line: > > -g, --group=GROUP set group ownership, instead of process' current > group > he's probably using the debian source packages. They are packaged to be compiled the *debian way* with make-kpkg. I'd suggest to download alsa sources from www.alsa-project.org and try to compile those or to compile kernel and external modules with make-kpkg (very easy). -- mattia :wq! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: alsa-source invalid group
Jeff <[EMAIL PROTECTED]> writes: > I'm trying to compile the alsa-source in testing and having a > problem. > > I run ./configure and then make without trouble. When I run make > install, I get this error: The Debian kernel module source packages are generally intended to be built via 'make-kpkg modules-image', from the kernel-package package. You might look at what debian/rules does for the kdist-image target to see if anything particularly magical happens. > > if [ -d /sbin/init.d ]; then \ > install -m 755 -g -o utils/alsasound /sbin/init.d/alsasound; \ > elif [ -d /etc/rc.d/init.d ]; then \ > install -m 755 -g -o utils/alsasound /etc/rc.d/init.d/alsasound; \ > elif [ -d /etc/init.d ]; then \ > install -m 755 -g -o utils/alsasound /etc/init.d/alsasound; \ > fi ...this is installing userspace stuff, not the kernel drivers, so in principle you shouldn't be running this code at all. (I know that for lm-sensors, which I maintain, the kernel source package doesn't include a lot of the userspace code, so if you don't either use kernel-package or read the directions in README.Debian your build will completely lose. I do this for two reasons: to reduce the size of the lm-sensors-source package, and so that it won't need to depend on other development packages that aren't needed for the kernel modules.) -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ "Theoretical politics is interesting. Politicking should be illegal." -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: alsa-source invalid group
On Wed, 23 Jul 2003, Jeff wrote:
> I'm trying to compile the alsa-source in testing and having a
> problem.
>
> I run ./configure and then make without trouble. When I run make
> install, I get this error:
>
>
> if [ -d /sbin/init.d ]; then \
> install -m 755 -g -o utils/alsasound /sbin/init.d/alsasound; \
> elif [ -d /etc/rc.d/init.d ]; then \
> install -m 755 -g -o utils/alsasound /etc/rc.d/init.d/alsasound; \
> elif [ -d /etc/init.d ]; then \
> install -m 755 -g -o utils/alsasound /etc/init.d/alsasound; \
> fi
> install: invalid group `-o'
> make: *** [install-scripts] Error 1
> root #
>
>
> I have a self-compile 2.4.21 kernel running.
>
> I can't figure this out, nor can I find anything googling yet. Anyone
> have an idea on how to get past this?
I ran a "install --help" which told me this relevant line:
-g, --group=GROUP set group ownership, instead of process' current
group
So it would seem that there is an error in your install script. Whoever
made it forgot to add which group the "alsasound" file should be owned by.
Personally I would try to get a more stable package. But if you like
living on the edge you could try to fix it yourself by modifying whichever
file contained the if-command you quoted above.
If you choose to gamble you should change the install script to do this
instead:
if [ -d /sbin/init.d ]; then \
install -m 755 -g root -o utils/alsasound /sbin/init.d/alsasound; \
elif [ -d /etc/rc.d/init.d ]; then \
install -m 755 -g root -o utils/alsasound /etc/rc.d/init.d/alsasound; \
elif [ -d /etc/init.d ]; then \
install -m 755 -g root -o utils/alsasound /etc/init.d/alsasound; \
fi
Ask someone who have a working alsasound package installed, what group
ownes the /sbin/init.d/alsasound, /etc/rc.d/init.d/alsasound, or
/etc/init.d/alsasound file. Also if/when you fix this you should get
another error.
.. oh. Never mind the above ;). It seems as if one doesn't have to specify
a group name after the "-g" parameter. If one had to, you would get two
error messages. If the -g parameter doesn't need a group name after it for
the "install" command to work, perhaps the -o parameter doesn't either. If
that reasoning is correct, we can draw the conclusion that there is
something else wrong. And that might be:
install --help
-o, --owner=OWNER set ownership (super-user only)
..that you maybe need to be logged in as root ("super-user") for this to
work?
Erm.. So what I am rambling about here is that you should try to do what
you did as root instead. If you already where root and it still didn't
work, I don't know what you could do to fix the problem.
..oh. But then again I see .. hehe:
> root #
from your quote.
Which means you ran this as root.
..but then again it said:
> install: invalid group `-o'
It seems to think that "-o" is a name of a group! Therefore one may
conclude that the -g parameter demands a group-name. And possibly the -o
parameter demands a name of an owner.
Soo.. Ask someone with a working alsa installed if they can run these
commands and tell you their output:
ls -la /sbin/init.d/alsasound 2>/dev/null
ls -la /etc/rc.d/init.d/alsasound 2>/dev/null
ls -la /etc/init.d/alsasound 2>/dev/null
The output should be something like this:
-rwxr-xr-x1 tommyroot 148 Jul 23 13:01 alsasound
I dont have alsa installed. So the above line is a made up one. But in the
example above you can see that "tommy" is the owner (-o) and the group
that owns the file is the "root" group (-g).
Then, you can correct your install script. And if you're nice, you can
report the error and fix to the developers of alsasound so other users
wont get the same problem. Or if you're not in any hurry you can just wait
a couple of hours or days until someone else relalizes the package wont
install. Then you can dl the fixed package and it will work.
--
Regards,
Tommy - http://www.geocities.com/todu5811/autosignature?1121
RFC2440 fingerprint: 4445 BB5E AE67 A0C9 7B25 5715 F938 88CB 7A10 2364
Re: alsa-source invalid group
On Wed, 23 Jul 2003, Jeff wrote:
> I'm trying to compile the alsa-source in testing and having a
> problem.
>
> I run ./configure and then make without trouble. When I run make
> install, I get this error:
>
>
> if [ -d /sbin/init.d ]; then \
> install -m 755 -g -o utils/alsasound /sbin/init.d/alsasound; \
> elif [ -d /etc/rc.d/init.d ]; then \
> install -m 755 -g -o utils/alsasound /etc/rc.d/init.d/alsasound; \
> elif [ -d /etc/init.d ]; then \
> install -m 755 -g -o utils/alsasound /etc/init.d/alsasound; \
> fi
> install: invalid group `-o'
> make: *** [install-scripts] Error 1
> root #
>
>
> I have a self-compile 2.4.21 kernel running.
>
> I can't figure this out, nor can I find anything googling yet. Anyone
> have an idea on how to get past this?
I ran a "install --help" which told me this relevant line:
-g, --group=GROUP set group ownership, instead of process' current
group
So it would seem that there is an error in your install script. Whoever
made it forgot to add which group the "alsasound" file should be owned by.
Personally I would try to get a more stable package. But if you like
living on the edge you could try to fix it yourself by modifying whichever
file contained the if-command you quoted above.
If you choose to gamble you should change the install script to do this
instead:
if [ -d /sbin/init.d ]; then \
install -m 755 -g root -o utils/alsasound /sbin/init.d/alsasound; \
elif [ -d /etc/rc.d/init.d ]; then \
install -m 755 -g root -o utils/alsasound /etc/rc.d/init.d/alsasound; \
elif [ -d /etc/init.d ]; then \
install -m 755 -g root -o utils/alsasound /etc/init.d/alsasound; \
fi
Ask someone who have a working alsasound package installed, what group
ownes the /sbin/init.d/alsasound, /etc/rc.d/init.d/alsasound, or
/etc/init.d/alsasound file. Also if/when you fix this you should get
another error.
.. oh. Never mind the above ;). It seems as if one doesn't have to specify
a group name after the "-g" parameter. If one had to, you would get two
error messages. If the -g parameter doesn't need a group name after it for
the "install" command to work, perhaps the -o parameter doesn't either. If
that reasoning is correct, we can draw the conclusion that there is
something else wrong. And that might be:
install --help
-o, --owner=OWNER set ownership (super-user only)
..that you maybe need to be logged in as root ("super-user") for this to
work?
Erm.. So what I am rambling about here is that you should try to do what
you did as root instead. If you already where root and it still didn't
work, I don't know what you could do to fix the problem.
..oh. But then again I see .. hehe:
> root #
from your quote.
Which means you ran this as root.
..but then again it said:
> install: invalid group `-o'
It seems to think that "-o" is a name of a group! Therefore one may
conclude that the -g parameter demands a group-name. And possibly the -o
parameter demands a name of an owner.
Soo.. Ask someone with a working alsa installed if they can run these
commands and tell you their output:
ls -la /sbin/init.d/alsasound 2>/dev/null
ls -la /etc/rc.d/init.d/alsasound 2>/dev/null
ls -la /etc/init.d/alsasound 2>/dev/null
The output should be something like this:
-rwxr-xr-x1 tommyroot 148 Jul 23 13:01 alsasound
I dont have alsa installed. So the above line is a made up one. But in the
example above you can see that "tommy" is the owner (-o) and the group
that owns the file is the "root" group (-g).
Then, you can correct your install script. And if you're nice, you can
report the error and fix to the developers of alsasound so other users
wont get the same problem. Or if you're not in any hurry you can just wait
a couple of hours or days until someone else relalizes the package wont
install. Then you can dl the fixed package and it will work.
--
Regards,
Tommy - http://www.geocities.com/todu5811/autosignature?1121
RFC2440 fingerprint: 4445 BB5E AE67 A0C9 7B25 5715 F938 88CB 7A10 2364
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: alsa please
gustavo wrote: Hello I was configure, make and make install the last versions of ALSA (drives, lib and utils: version 0.9.5). Then I was run `./snddevices' in order to create the devices. Finally when I test the module with: `modprobe snd-ali5451' I receive the next error: /lib/modules/2.4.18-bf2.4/kernel/sound/pci/ali5451/snd-ali5451.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.18-bf2.4/kernel/sound/pci/ali5451/snd-ali5451.o: insmod /lib/modules/2.4.18-bf2.4/kernel/sound/pci/ali5451/snd-ali5451.o failed /lib/modules/2.4.18-bf2.4/kernel/sound/pci/ali5451/snd-ali5451.o: insmod snd-ali5451 failed I really don't know wath is my problem. Please help me. gustavo by the way I have a thinkpad R-30 with sound card: ALI M5229 and I use Woody with kerne 2.4bf2. Have you tried to unload the oss modules before trying to load the alsa ones? K
Re: alsa please
gustavo wrote: Hello I was configure, make and make install the last versions of ALSA (drives, lib and utils: version 0.9.5). Then I was run `./snddevices' in order to create the devices. Finally when I test the module with: `modprobe snd-ali5451' I receive the next error: /lib/modules/2.4.18-bf2.4/kernel/sound/pci/ali5451/snd-ali5451.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.18-bf2.4/kernel/sound/pci/ali5451/snd-ali5451.o: insmod /lib/modules/2.4.18-bf2.4/kernel/sound/pci/ali5451/snd-ali5451.o failed /lib/modules/2.4.18-bf2.4/kernel/sound/pci/ali5451/snd-ali5451.o: insmod snd-ali5451 failed I really don't know wath is my problem. Please help me. gustavo by the way I have a thinkpad R-30 with sound card: ALI M5229 and I use Woody with kerne 2.4bf2. Have you tried to unload the oss modules before trying to load the alsa ones? K -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [ALSA] Toshiba Libretto 110CT
On Tue, Apr 15, 2003 at 09:05:43PM +0200, Sylvain Briole wrote: > Hello all, > > Did someone managed to use/configure ALSA on a Toshiba Libretto 110CT? > > I thank you in advance for any answer, > I configured the toshiba portege 300CT using alsa, it's a yamaha opl3/sa2. Can't remember the data you have to input (DMA, etc etc), but if you search on linuxonlaptops you'll find an artivle about the 300ct where it is. Probably you'll find insytructions for the 110CT too. Aritz Beraza -- Aritz Beraza Garayalde [EMAIL PROTECTED] Linux User 272970 [http://www.upcnet.es/~abg] ************ 110011 TThhiinnggss YYoouu DDoo NNoott WWaanntt YYoouurr SSyysstteemm AAddmmiinniissttrraattoorr TToo SSaayy ************ 69. Ooops. Save your work, everyone. FAST!
Re: ALSA confusion
Kevin McKinley [Dienstag, 15. April 2003 20:35]: >| On Tue, 15 Apr 2003 13:55:23 -0300 >| Derek Broughton <[EMAIL PROTECTED]> wrote: >| > into. So, no, there are no requirements that you use make-kpkg, but it >| > _is_ easier (if you can remember the particular command line - I admit I >| > do it infrequently enough that I have to use man make-kpkg every time) >| Just use the checklist at the end of the newbiedoc tutorial. The command >| lines there show the options most people need. >| Kevin i scratched it with a pencil into one edge of the case ;-) -- micha.
Re: ALSA confusion
On Tue, 15 Apr 2003 13:55:23 -0300 Derek Broughton <[EMAIL PROTECTED]> wrote: > into. So, no, there are no requirements that you use make-kpkg, but it > _is_ easier (if you can remember the particular command line - I admit I > do it infrequently enough that I have to use man make-kpkg every time) Just use the checklist at the end of the newbiedoc tutorial. The command lines there show the options most people need. Kevin
Re: ALSA confusion
From: "Emma Jane Hogbin" <[EMAIL PROTECTED]> > On Mon, Apr 14, 2003 at 08:10:32AM +0200, Emil Pedersen wrote: > > When you built the kernel (your now using), did you build it with > > make-kpkg into a deb package or the "easy" way? I would guess the > > later and that that is the reason apt-get complains. > > Yeah, the easy way. > > > Is it a requirement to do it "the debian way"? I got alsa working not > > using the packed source without too much trouble (at least as I recall > > it). In some cases I find it simpler to "pollute" my system with > > configure/make/install rather than using prepackaged source/packages. > > I ended up doing the ol' configure make make install and it works fine. > One of these I should probably figure out how to do things The Debian Way. > But for now I have (almost) everything I was trying to accomplish. :) Well, I guess "the easy way" means you don't actually have to remember anything - we can all do ./configure, make, make install, in our sleep - but make-kpkg is pretty darn simple, and obviously avoids the problems you've run into. So, no, there are no requirements that you use make-kpkg, but it _is_ easier (if you can remember the particular command line - I admit I do it infrequently enough that I have to use man make-kpkg every time)
Re: ALSA confusion
On Mon, Apr 14, 2003 at 08:10:32AM +0200, Emil Pedersen wrote: > When you built the kernel (your now using), did you build it with > make-kpkg into a deb package or the "easy" way? I would guess the > later and that that is the reason apt-get complains. Yeah, the easy way. > Is it a requirement to do it "the debian way"? I got alsa working not > using the packed source without too much trouble (at least as I recall > it). In some cases I find it simpler to "pollute" my system with > configure/make/install rather than using prepackaged source/packages. I ended up doing the ol' configure make make install and it works fine. One of these I should probably figure out how to do things The Debian Way. But for now I have (almost) everything I was trying to accomplish. :) My laptop is also deliciously quiet this morning and the vibration is gone from the keyboard. :) emma -- Emma Jane Hogbin [[ 416 417 2868 ][ www.xtrinsic.com ]]
Re: ALSA confusion
Emma Jane Hogbin wrote: > > I thought I had everything almost working, but I didn't. My problem is > that most of the instructions need a .deb for the kernel. I do everything > a la main. So I can make and install a .deb for the alsa drivers (at one > point I actually got a sound file to play on xmms -- although there was no > sound that came out of my computer). > > But then whenever I try to use apt-get I get a complaint about the kernel > .deb file missing. > > Does anyone know where I could find instructions on stitching things > together? > > I've been trying to use this one: > http://www.linuxorbit.com/modules.php?op=modload&name=Sections&file=index&req=viewarticle&artid=541&page=1 > but I have to install the alsa modules with dpkg -i... > > thanks! > > emma When you built the kernel (your now using), did you build it with make-kpkg into a deb package or the "easy" way? I would guess the later and that that is the reason apt-get complains. It's not that hard to make a kernel package, but I have no idea if it would help in this case. (Personally I usually skip that step unless I intend to install the same kernel on several computers.) Is it a requirement to do it "the debian way"? I got alsa working not using the packed source without too much trouble (at least as I recall it). In some cases I find it simpler to "pollute" my system with configure/make/install rather than using prepackaged source/packages. Anyway; I'll probably reinstall alsa (new kernel and alsa version) during the day, I'll try to remember what I do (if I get i working again;-) if you want to try the "false" way. Sincerely, Emil
Re: Alsa + 2.4.19 on presario 1245
Sebastian Henschel wrote: hello miguel.. Received at 2002-12-17 / 09:07 by Miguel Griffa: I have an onboard sound at io 0x220, and so, I use alsaconf to configure the card I want, everything seems fine untils alsa runs then, it complains about bad parameters being passed to module, and then says card probably not detected, take a look at http://digilander.libero.it/zeromega/linux_compaq.html, perhaps this helps. then, please take a look at the sound-howto in /usr/share/doc/HOWTO/en-txt/Sound-HOWTO.gz (package doc-linux-text). which card does "lspci" claim to see? which card did you configure with alsa? did you also configure irq (mostly 5 or 7) and dma (mostly 1)? I think I've messed up something, I remember configuring via686 chipset, but the page you sent says ess... I'll try this tonight (I don't have the laptop at this moment) and post updated info. Thanks a lot
Re: Alsa + 2.4.19 on presario 1245
Sebastian Henschel wrote: hello miguel.. Received at 2002-12-17 / 09:07 by Miguel Griffa: I have an onboard sound at io 0x220, and so, I use alsaconf to configure the card I want, everything seems fine untils alsa runs then, it complains about bad parameters being passed to module, and then says card probably not detected, take a look at http://digilander.libero.it/zeromega/linux_compaq.html, perhaps this helps. then, please take a look at the sound-howto in /usr/share/doc/HOWTO/en-txt/Sound-HOWTO.gz (package doc-linux-text). which card does "lspci" claim to see? which card did you configure with alsa? did you also configure irq (mostly 5 or 7) and dma (mostly 1)? I think I've messed up something, I remember configuring via686 chipset, but the page you sent says ess... I'll try this tonight (I don't have the laptop at this moment) and post updated info. Thanks a lot -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alsa + 2.4.19 on presario 1245
hello miguel.. Received at 2002-12-17 / 09:07 by Miguel Griffa: > I have an onboard sound at io 0x220, and so, > I use alsaconf to configure the card I want, everything seems fine > untils alsa runs > then, it complains about bad parameters being passed to module, and then > says card probably not detected, take a look at http://digilander.libero.it/zeromega/linux_compaq.html, perhaps this helps. then, please take a look at the sound-howto in /usr/share/doc/HOWTO/en-txt/Sound-HOWTO.gz (package doc-linux-text). which card does "lspci" claim to see? which card did you configure with alsa? did you also configure irq (mostly 5 or 7) and dma (mostly 1)? hth, sebastian -- ::: sebastian henschel ::: kodeaffe ::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import
Re: Alsa + 2.4.19 on presario 1245
hello miguel.. Received at 2002-12-17 / 09:07 by Miguel Griffa: > I have an onboard sound at io 0x220, and so, > I use alsaconf to configure the card I want, everything seems fine > untils alsa runs > then, it complains about bad parameters being passed to module, and then > says card probably not detected, take a look at http://digilander.libero.it/zeromega/linux_compaq.html, perhaps this helps. then, please take a look at the sound-howto in /usr/share/doc/HOWTO/en-txt/Sound-HOWTO.gz (package doc-linux-text). which card does "lspci" claim to see? which card did you configure with alsa? did you also configure irq (mostly 5 or 7) and dma (mostly 1)? hth, sebastian -- ::: sebastian henschel ::: kodeaffe ::: lynx -source http://www.kodeaffe.de/shensche.pub | gpg --import -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Alsa-devel] Re: [2.4]ALi M5451 sound hangs on init; workaround
At Wed, 11 Dec 2002 08:52:42 -0800,
Fedor Karpelevitch wrote:
>
> > > I have ALi M5451 souncard in my laptop (Compaq Presario 900z for
> > > those searching) and it hangs the machine with any kernel I tried
> > > (currently 2.4.20-ac1 + hirofumi patch). I traced it down to the
> > > line where it hangs - that is drivers/sound/trident.c:3379 which
> > > says: pci_write_config_byte(pci_dev, 0xB8, ~temp);
> >
> > Looking at the docs it looks like the code Matt Wu added may have
> > been meant to do
> >
> > pci_read_config_byte(pci_dev, 0x59, temp)
> > temp &= ~0x80
> > pci_write...
> >
>
> just to make sure I got it right, is the following what you suggest?
> (pseudo-patch):
>
>
> static int ali_close_multi_channels(void)
> {
> char temp = 0;
> struct pci_dev *pci_dev = NULL;
>
> pci_dev =pci_find_device(PCI_VENDOR_ID_AL,PCI_DEVICE_ID_AL_M1533,
> pci_dev);
> if (pci_dev == NULL)
> return -1;
> - temp = 0x80;
> + pci_read_config_byte(pci_dev, 0x59, temp);
> + temp &= ~0x80;
> - pci_write_config_byte(pci_dev, 0x59, ~temp);
> + pci_write_config_byte(pci_dev, 0x59, temp);
>
> pci_dev = pci_find_device(PCI_VENDOR_ID_AL,
> PCI_DEVICE_ID_AL_M7101, pci_dev);
> if (pci_dev == NULL)
> return -1;
>
> - temp = 0x20;
> + pci_read_config_byte(pci_dev, 0xB8, temp);
> + temp &= ~0x20
> - pci_write_config_byte(pci_dev, 0xB8, ~temp); // the line I
> + pci_write_config_byte(pci_dev, 0xB8, temp); //commented out
>
> return 0;
> }
> -
and don't forget to change similary for ali_setup_multi_channels(),
too.
> >
> > (Ditto with fixing setup_multi_cannnels)
> >
Takashi
Re: [Alsa-devel] Re: [2.4]ALi M5451 sound hangs on init; workaround
At Wed, 11 Dec 2002 08:52:42 -0800,
Fedor Karpelevitch wrote:
>
> > > I have ALi M5451 souncard in my laptop (Compaq Presario 900z for
> > > those searching) and it hangs the machine with any kernel I tried
> > > (currently 2.4.20-ac1 + hirofumi patch). I traced it down to the
> > > line where it hangs - that is drivers/sound/trident.c:3379 which
> > > says: pci_write_config_byte(pci_dev, 0xB8, ~temp);
> >
> > Looking at the docs it looks like the code Matt Wu added may have
> > been meant to do
> >
> > pci_read_config_byte(pci_dev, 0x59, temp)
> > temp &= ~0x80
> > pci_write...
> >
>
> just to make sure I got it right, is the following what you suggest?
> (pseudo-patch):
>
>
> static int ali_close_multi_channels(void)
> {
> char temp = 0;
> struct pci_dev *pci_dev = NULL;
>
> pci_dev =pci_find_device(PCI_VENDOR_ID_AL,PCI_DEVICE_ID_AL_M1533,
> pci_dev);
> if (pci_dev == NULL)
> return -1;
> - temp = 0x80;
> + pci_read_config_byte(pci_dev, 0x59, temp);
> + temp &= ~0x80;
> - pci_write_config_byte(pci_dev, 0x59, ~temp);
> + pci_write_config_byte(pci_dev, 0x59, temp);
>
> pci_dev = pci_find_device(PCI_VENDOR_ID_AL,
> PCI_DEVICE_ID_AL_M7101, pci_dev);
> if (pci_dev == NULL)
> return -1;
>
> - temp = 0x20;
> + pci_read_config_byte(pci_dev, 0xB8, temp);
> + temp &= ~0x20
> - pci_write_config_byte(pci_dev, 0xB8, ~temp); // the line I
> + pci_write_config_byte(pci_dev, 0xB8, temp); //commented out
>
> return 0;
> }
> -
and don't forget to change similary for ali_setup_multi_channels(),
too.
> >
> > (Ditto with fixing setup_multi_cannnels)
> >
Takashi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: alsa/kernel-modules - new problems
On Tue, Aug 13, 2002 at 01:30:39PM -0700, Ivan Uemlianin wrote: > > So now uname and I are in agreement, and there is a new set of > > error messages: > > > > > > * During dpkg -i kernel-image-2.4.18_forAlsa.1.0_i386.deb I got this new > > depmod error: > > > > depmod: *** Unresolved symbols in /lib/modules/2.4.18/alsa/snd-intel8x0.o > > There was a problem running depmod. This may be benign, > > (You may have versioned symbol names, for instance). > > Or this could be an error. In any case, since depmod is > > run at install time, we could just defer running depmod > > Would you like to abort now? [Yes] no I hit this as well. Build the mpu401 soundcard module as well as the intel8x0 module... -- --- Paul "TBBle" Hampson, MCSE 5th year CompSci/Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] Of course Pacman didn't influence us as kids. If it did, we'd be running around in darkened rooms, popping pills and listening to repetitive music. This email is licensed to the recipient for non-commercial use, duplication and distribution. --- pgpTOENNGmyQl.pgp Description: PGP signature
Re: alsa/kernel-modules - new problems
> > * During dpkg -i kernel-image-2.4.18_forAlsa.1.0_i386.deb I got this new > > depmod error: > > > > depmod: *** Unresolved symbols in /lib/modules/2.4.18/alsa/snd-intel8x0.o > > There was a problem running depmod. This may be benign, > > (You may have versioned symbol names, for instance). > > Or this could be an error. In any case, since depmod is > > run at install time, we could just defer running depmod > > Would you like to abort now? [Yes] no So, you installed kernel-image-for-alsa. Try to install correspondent alsa modules as well.
Re: alsa not working: step-by-step
I guess you ARE still running the -bf2.4 kernel. uname -a is VERY reliable... So check your lilo or grub setup. Greetings, Erich -- erich@(mucl.de|debian.org)--GPG Key ID: 4B3A135C There are only 10 types of people in the world: Those who understand binary and those who don't Mancher findet sein Herz nicht eher, als bis er seinen Kopf verliert. "Wissen ist Macht" - wenn man das richtige daraus macht.
Re: alsa/sound on thinkpad
According to your log output your system has the AC97 on an Intel 810 chipset. Have you looked at this page: http://www.alsa-project.org/alsa-doc/ and taken a look at the Analog Devices lines? To the right is a button to some specific information on either the Intel or Via chipsets followed by generic installation docs. Keep working at it. You'll figure it out eventually! - Nate >> -- Wireless | Amateur Radio Station N0NB | "We have awakened a Internet | [EMAIL PROTECTED] | sleeping giant and Location | Bremen, Kansas USA EM19ov | have instilled in him Amateur radio exams; ham radio; Linux info @ | a terrible resolve". http://www.qsl.net/n0nb/ | - Admiral Yamomoto
Re: Alsa setup on Toshiba
> At 03:35 PM 07/29/02 -0400, kiss the sun and walk on air wrote: > >use the ymfpci driver, from either the kernel or alsa. > > Why that made it easy. Thanks! Still not sure what or when or why to use > Alsa, but that can now be left for another day. OSS are old drivers, ALSA are new. Use OSS if you want configuration to be simple. Use ALSA if you want to have a modern system or if OSS drivers don't satisfy you. > Any suggestions for a basic mixer for X (I'm running fluxbox). Actually, > aumix is not that bad, really. gmix -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alsa setup on Toshiba
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Off the top, I'd suggest installing package aumix-gtk. Basically aumix, but with a gtk interface, so it runs natively under X HTH, Bill Moseley wrote: | At 03:35 PM 07/29/02 -0400, kiss the sun and walk on air wrote: | |>use the ymfpci driver, from either the kernel or alsa. | | | Why that made it easy. Thanks! Still not sure what or when or why to use | Alsa, but that can now be left for another day. | | Any suggestions for a basic mixer for X (I'm running fluxbox). Actually, | aumix is not that bad, really. | | - -- Mike Alborn <[EMAIL PROTECTED]> http://deandra.homeip.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org iD8DBQE9RaHftZvnYYvO/VIRAksLAKCXuw8KS5U/xQKZ4KbYQdL9BCKXYgCg76xx FIm+7d3YPokjOU09EbRp1sY= =y/C7 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alsa setup on Toshiba
At 03:35 PM 07/29/02 -0400, kiss the sun and walk on air wrote: >use the ymfpci driver, from either the kernel or alsa. Why that made it easy. Thanks! Still not sure what or when or why to use Alsa, but that can now be left for another day. Any suggestions for a basic mixer for X (I'm running fluxbox). Actually, aumix is not that bad, really. -- Bill Moseley mailto:[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alsa setup on Toshiba
On Mon, Jul 29, 2002 at 12:30:50PM -0700, Bill Moseley wrote: > lspci shows: > > 00:0c.0 Multimedia audio controller: Yamaha Corporation YMF-754 > [DS-1E Audio Controller] > > My kernel would seem to support this. I can run modconf and see an entry: > > ac97_codec- Yamaha YMF7xx PCI audio (native mode) use the ymfpci driver, from either the kernel or alsa. -pete -- (peter.royal|osi)@pobox.com - http://fotap.org/~osi jabber/ [EMAIL PROTECTED] - icq/ 153025 - aim/ osifx - yahoo/ osi_fx your brain on life - http://fotap.org - incubating pgpiLO20nHWdl.pgp Description: PGP signature
Re: ALSA + suspend
On Thu, 13 Jun 2002 11:46:19 -0400 Hubert Chan <[EMAIL PROTECTED]> wrote: > > "ugk8" == ugk8 <[EMAIL PROTECTED]> writes: > > ugk8> Laptor:/>>> fuser /dev/dsp > ugk8> Laptor:/>>> rmmod snd-trident-synth > ugk8> snd-trident-synth: Device or resource busy > > That means some device is using sound. > > Try "fuser /dev/snd/*" and "fuser /dev/sound/*". Maybe even i don't have them i tried all, that belong to group audio > "fuser /usr/lib/libasound*". no, nothing. > > -- > Hubert Chan <[EMAIL PROTECTED]> - http://www.uhoreg.ca/ > PGP/GnuPG key: 1024D/124B61FA > Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA > Key available at wwwkeys.pgp.net. Encrypted e-mail preferred. > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA + suspend
hi ugk8. are you sure, no prog is using the devices (ALSA-devs as well). Dunno what they are called. Try the hard one: go to console. su - init S lsmod rmmod all-by-hand init if that doesn't help, it you.ld be a bug in the modules. so far. see you, up5a -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA + suspend
> "ugk8" == ugk8 <[EMAIL PROTECTED]> writes: ugk8> Laptor:/>>> fuser /dev/dsp ugk8> Laptor:/>>> rmmod snd-trident-synth ugk8> snd-trident-synth: Device or resource busy That means some device is using sound. Try "fuser /dev/snd/*" and "fuser /dev/sound/*". Maybe even "fuser /usr/lib/libasound*". -- Hubert Chan <[EMAIL PROTECTED]> - http://www.uhoreg.ca/ PGP/GnuPG key: 1024D/124B61FA Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA Key available at wwwkeys.pgp.net. Encrypted e-mail preferred. pgpaSrwhKCbdr.pgp Description: PGP signature
Re: ALSA + suspend
On Thu, 13 Jun 2002 11:46:19 -0400 Hubert Chan <[EMAIL PROTECTED]> wrote: > > "ugk8" == ugk8 <[EMAIL PROTECTED]> writes: > > ugk8> Laptor:/>>> fuser /dev/dsp > ugk8> Laptor:/>>> rmmod snd-trident-synth > ugk8> snd-trident-synth: Device or resource busy > > That means some device is using sound. > > Try "fuser /dev/snd/*" and "fuser /dev/sound/*". Maybe even i don't have them i tried all, that belong to group audio > "fuser /usr/lib/libasound*". no, nothing. > > -- > Hubert Chan <[EMAIL PROTECTED]> - http://www.uhoreg.ca/ > PGP/GnuPG key: 1024D/124B61FA > Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA > Key available at wwwkeys.pgp.net. Encrypted e-mail preferred. > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ALSA + suspend
On Wed, 12 Jun 2002 14:23:11 -0400 Hubert Chan <[EMAIL PROTECTED]> wrote: > > "ugk8" == ugk8 <[EMAIL PROTECTED]> writes: > > ugk8> Hi, after resuming from standby or suspend ALSA doesn't work > ugk8> anymore. I can't rmmod the modules, neither before suspending, > ugk8> nor after resuming. No processes use the modules. > > What do you mean "can't rmmod the modules"? What message did rmmod give > you? Laptor:/>>> fuser /dev/dsp Laptor:/>>> rmmod snd-trident-synth snd-trident-synth: Device or resource busy Laptor:/>>> /etc/init.d/alsasound stop Shutting down sound driver: ALSA lib seq_hw.c:446:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory can't open sequencer /usr/sbin/alsactl: save_state:963: No soundcards found... snd-mixer-oss: Device or resource busy snd-trident-synth: Device or resource busy snd-seq-instr: Device or resource busy snd-ainstr-simple: Device or resource busy snd-seq-midi-emul: Device or resource busy snd-seq: Device or resource busy snd-trident: Device or resource busy snd-pcm: Device or resource busy snd-timer: Device or resource busy snd-mpu401-uart: Device or resource busy snd-rawmidi: Device or resource busy snd-seq-device: Device or resource busy snd-util-mem: Device or resource busy snd-ac97-codec: Device or resource busy snd: Device or resource busy done Laptor:/>>> /etc/init.d/alsasound start ALSA driver is already running. Laptor:/>>> That's it. > > Did you try "/etc/init.d/alsa restart"? > > -- > Hubert Chan <[EMAIL PROTECTED]> - http://www.uhoreg.ca/ > PGP/GnuPG key: 1024D/124B61FA > Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA > Key available at wwwkeys.pgp.net. Encrypted e-mail preferred. > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
