Re: [arch-general] *** GMX Spamverdacht *** Re: Muting internal speakers
On Fri, Jun 15, 2012 at 11:23 AM, ShichaoGao xgd...@gmail.com wrote: You can try instaling pulseaudio and pavucontrol , in pavucontrol you can set default device. Which is only used for new streams (existing streams are not automatically moved over). I have a small home-brew script which I use to switch the default sink AND move all current streams to that new default, but never figured out (didn't really try too hard) how to automate it to plugging in/out of audio equipment. I think it wasn't possible at that point in time to detect jack in or something like that.
Re: [arch-general] Arch box fine tuning
On Thu, 2012-06-14 at 15:59 +0200, Arno Gaboury wrote: Still looking for a good pointer for building my own Kernel 4.2 wjth comprehensive explanations of each sub menu of menu config. For e.g. make oldconfig you can use the ?. Using this information with a search engine should give the wanted comprehensive explanations. But you even could search the Internet for CONFIG_FOO_BAR ;).
Re: [arch-general] Muting internal speakers
Hello, pulseaudio[1] has that functionality. You should check it out. On KDE , Kmix supports pulseaudio and I am pretty sure it support auto switching too. Regards, --Chris Sakalis [1] - https://wiki.archlinux.org/index.php/Pulseaudio On Fri, Jun 15, 2012 at 12:13 AM, Eric Ryan Jones e...@thetechnojesus.com wrote: Arch always did that automatically for me. I do know that you can set up defaults and fallbacks in KDE just like in Windows. I'm not sure about GNOME, though, as I have used KDE for a while. -Original Message- From: arch-general-boun...@archlinux.org [mailto:arch-general-boun...@archlinux.org] On Behalf Of Nelson Marambio Sent: Thursday, June 14, 2012 4:52 PM To: arch-general@archlinux.org Subject: [arch-general] Muting internal speakers Since the change from Win 7 to Arch there is just one function I really miss up to now. Perhaps someone of you can help me out. Is it possible that Arch deactivates the internal speakers of my laptop when I plug in my USB-headset and turn input / output to this ? In Windows I could define the USB headset as default for in-/output so Win made a fallback to internal speakers only when I plugged out the headset again. It would be really great if Arch was that comfortable too. I know in GNOME there are just two clicks to do for switching to another audio hardware but ... :D Warm regards, Nelson.
Re: [arch-general] Shutdown and reboot not working after last weekend update
On Thu, 2012-06-14 at 11:37 -0300, Victor Silva wrote: Also, is there a procedure I can use to have multiple kernels? Don't name the packages/kernels linux. Name them linux, linux-1, linux-2 etc.?! You also could get different kernels from the repositories, of course not different versions of linux, but e.g. linux + linux-rt. $ ls /mnt/archlinux/boot/vmlinuz* /mnt/archlinux/boot/vmlinuz-linux /mnt/archlinux/boot/vmlinuz-linux-rt
Re: [arch-general] Arch box fine tuning
On Thu, 2012-06-14 at 18:35 +0200, solsTiCe d'Hiver wrote: Anyway, is a kernel configuration and (re)compilation really worth the pain and time ?? Is a custom kernel giving any benefit or speed-up apart from something marginal and more about the feeling than anything else ? I gave up trying to make one just by lazyness on archlinux. I did that many years when I used slackware. But that's a thing to do at least once in a lifetime of course :-) The advantage of having a kernel with more than what is needed is, that it's easier to change hardware if needed. I don't reduce the sizes of my kernels, the drawback is, that it takes around 90 minutes to compile a kernel on an AMD dual-core 2.1GHz, 4GB RAM, 2 jobs. Regarding to the used size or performance IMO it's useless to reduce the kernel's contend, simply don't load unneeded modules. IIRC the OP wishes to learn, IOW he'll do this as an exercise.
Re: [arch-general] Muting internal speakers
Am Fri, 15 Jun 2012 10:17:45 +0300 schrieb Chris Sakalis chrissaka...@gmail.com: Hello, pulseaudio[1] has that functionality. You should check it out. On KDE , Kmix supports pulseaudio and I am pretty sure it support auto switching too. PulseAudio is more or less crap. It still doesn't support (semi-)professional audio cards. If you don't really need it's super-duper extra functions like gaplessly moving a stream from one sound card to another you better don't bother with PA. It rather makes things worse than better. I don't have a solution for the original question, because I don't use two sound cards at the same time, but there are other and better ways to disable the internal notebook speakers. Usually you can choose in every application which sound card to be used (sometimes in it's config files). I guess there are software mixers for every desktop environment which let you choose the sound card, which shall be used. Btw., isn't there a button on the notebook which can mute those speakers? Heiko
Re: [arch-general] Muting internal speakers
On Fri, Jun 15, 2012 at 5:04 PM, Heiko Baums li...@baums-on-web.de wrote: Am Fri, 15 Jun 2012 10:17:45 +0300 schrieb Chris Sakalis chrissaka...@gmail.com: Hello, pulseaudio[1] has that functionality. You should check it out. On KDE , Kmix supports pulseaudio and I am pretty sure it support auto switching too. PulseAudio is more or less crap. It still doesn't support (semi-)professional audio cards. If you don't really need it's super-duper extra functions like gaplessly moving a stream from one sound card to another you better don't bother with PA. It rather makes things worse than better. Yes, why not repeat that opinion in every thread where pulse is brought up? Its not like its repetitive. I don't have a solution for the original question, because I don't use two sound cards at the same time, but there are other and better ways to disable the internal notebook speakers. Usually you can choose in every application which sound card to be used (sometimes in it's config files). I guess there are software mixers for every desktop environment which let you choose the sound card, which shall be used. Which sounds an awful lot like slimmed-down pulseaudio to me. At the OP - pulseaudio may (or may not) help in your situation. The 'default' device is not the same as a Windows default device in the sense that currently playing streams will not be automatically moved. I use a script to do that (change default device and move all streams, I think I may even have posted it up on the pulse wiki), but (AFAIK) there aren't any 'hooks' for activating such scripts within pulseaudio when a new card is detected. Not sure if udev can do that, I just press a shortcut to run the script when I plug in my external headphones/sound card.
Re: [arch-general] Muting internal speakers
On Fri, 15 Jun 2012 11:04:30 +0200 Heiko Baums li...@baums-on-web.de wrote: Am Fri, 15 Jun 2012 10:17:45 +0300 schrieb Chris Sakalis chrissaka...@gmail.com: Hello, pulseaudio[1] has that functionality. You should check it out. On KDE , Kmix supports pulseaudio and I am pretty sure it support auto switching too. PulseAudio is more or less crap. It still doesn't support (semi-)professional audio cards. If you don't really need it's super-duper extra functions like gaplessly moving a stream from one sound card to another you better don't bother with PA. It rather makes things worse than better. I don't have a solution for the original question, because I don't use two sound cards at the same time, but there are other and better ways to disable the internal notebook speakers. Usually you can choose in every application which sound card to be used (sometimes in it's config files). I guess there are software mixers for every desktop environment which let you choose the sound card, which shall be used. Btw., isn't there a button on the notebook which can mute those speakers? Heiko Talk about serious sour grapes .. I have 2 sound cards one internal and a USB one with PA gives me a lot less bother than ALSA did .. Pete -- Linux 7-of-9 3.3.8-1-ARCH #1 SMP PREEMPT Tue Jun 5 15:20:32 CEST 2012 x86_64 GNU/Linux
Re: [arch-general] Arch box fine tuning
... this will build you a kernel with only the bare minimum needed to fulfill your current state; any modules not loaded at this time will not be built. you may still need to configure other features unrelated to modules. I'd be interested to know what size your kernel is when you do that. I know Linux kernels have been built at 16Kb or something silly but then it couldn't actually do anything. When I do this for OpenBSD I get it down to about a quarter of stock at 2 megabytes and there are no modules even on OpenBSD by default. Why not do something good every day and install BOINC.
Re: [arch-general] Muting internal speakers
True! Maybe many people got the bad impression of PA in previous versions. Talk about serious sour grapes .. I have 2 sound cards one internal and a USB one with PA gives me a lot less bother than ALSA did .. Pete
Re: [arch-general] Muting internal speakers
On Fri, 2012-06-15 at 18:06 +0800, Oon-Ee Ng wrote: On Fri, Jun 15, 2012 at 5:04 PM, Heiko Baums li...@baums-on-web.de wrote: Am Fri, 15 Jun 2012 10:17:45 +0300 schrieb Chris Sakalis chrissaka...@gmail.com: Hello, pulseaudio[1] has that functionality. You should check it out. On KDE , Kmix supports pulseaudio and I am pretty sure it support auto switching too. PulseAudio is more or less crap. It still doesn't support (semi-)professional audio cards. If you don't really need it's super-duper extra functions like gaplessly moving a stream from one sound card to another you better don't bother with PA. It rather makes things worse than better. Yes, why not repeat that opinion in every thread where pulse is brought up? Its not like its repetitive. I agree with Heiko Baums and Oon-Ee Ng, this is possible because ... If PA should be able to solve the OP's issue, then it's unimportant what issues PA could cause. If somebody replies with a guess, that PA might solve the issue on GNOME, because KMix is able to solve it, then a hint, that PA could cause serious issues IMO is ok.
Re: [arch-general] Muting internal speakers
PS: On Fri, 2012-06-15 at 12:56 +0200, Ralf Mardorf wrote: I agree with Heiko Baums and Oon-Ee Ng, this is possible because ... If PA should be able to solve the OP's issue, then it's unimportant what issues PA could cause. If somebody replies with a guess, that PA might solve the issue on GNOME, because KMix is able to solve it, then a hint, that PA could cause serious issues IMO is ok. I suspect that PA already is installed, since the OP referred to GNOME. Less people run GNOME without PA. So neither doesn't PA cause an issue for the OP, nor does it satisfy the OP's needs.
Re: [arch-general] Muting internal speakers
Apologize for the Freudian slip ;) So neither doesn't PA cause an issue for the OP, nor does it satisfy the OP's needs. So neither PA does cause an issue for the OP, nor does it satisfy the OP's needs.
Re: [arch-general] Muting internal speakers
Am Fri, 15 Jun 2012 18:06:20 +0800 schrieb Oon-Ee Ng ngoonee.t...@gmail.com: Yes, why not repeat that opinion in every thread where pulse is brought up? Its not like its repetitive. Yes, why not repeat that suggestion installing PulseAudio in every thread where somebody has a simple question about selecting an audio card? It's not like it's repetitive. And the most useless suggestion anyway. Heiko
Re: [arch-general] Muting internal speakers
Am Fri, 15 Jun 2012 18:22:45 +0800 schrieb ShichaoGao xgd...@gmail.com: True! Maybe many people got the bad impression of PA in previous versions. Wrong! Maybe many people got the bad impression of PA, because PA just still doesn't work with their audio cards, and because PA still causes more problems than it solves. There are only a very few SoundBlaster and AC'97 onboard sound cards which are supported by PA. Maybe PA works with those sound cards. But it doesn't work with other ones like the (semi-)professional audio cards. And most of PA's features - well, every useful feature - is available by ALSA and/or the audio applications themselves. Nevertheless installing PA just adds a new additional layer that can cause problems. So finding the reason for a bug is unnecessarily more complicated than without PA. Oh yes, I forgot, PA doesn't and never will have any bugs. Bugs are always only caused by ALSA, which works absolute flawlessly, even with those (semi-)professional audio cards. Heiko
Re: [arch-general] Muting internal speakers
On 15-06-2012 12:42, Heiko Baums wrote: Am Fri, 15 Jun 2012 18:06:20 +0800 schrieb Oon-Ee Ng ngoonee.t...@gmail.com: Yes, why not repeat that opinion in every thread where pulse is brought up? Its not like its repetitive. Yes, why not repeat that suggestion installing PulseAudio in every thread where somebody has a simple question about selecting an audio card? It's not like it's repetitive. And the most useless suggestion anyway. Heiko Have you actually tried using the latest pulseaudio for a couple of weeks? For supported hardware it sure does something somewhat similar to what the OP wants. It sure seems you have some gripe with pulseaudio and/or pulseaudio's upstream and are on a personal crusade to bash it every time you can. Pulseaudio is not perfect but neither is alsa, if alsa only solves the problem then fine, if some user has better luck with pulseaudio+alsa so be it, the user will decide for itself if it sucks or not so just let it rest. -- Mauro Santos
Re: [arch-general] Muting internal speakers
On Fri, 2012-06-15 at 13:00 +0100, Mauro Santos wrote: Have you actually tried using the latest pulseaudio for a couple of weeks? For supported hardware it sure does something somewhat similar to what the OP wants. It sure seems you have some gripe with pulseaudio and/or pulseaudio's upstream and are on a personal crusade to bash it every time you can. Pulseaudio is not perfect but neither is alsa, if alsa only solves the problem then fine, if some user has better luck with pulseaudio+alsa so be it, the user will decide for itself if it sucks or not so just let it rest. Ubuntu Studio Precise chips with a new version of PA and a PA Jack bridge. RME HDSPe AIO started working when PA was removed, it didn't work with PA. Regarding to this thread it's irrelevant. BOT as mentioned before, the OP seem to use GNOME, so it's likely that he already has PA installed. Audio out is ok, so PA doesn't cause trouble, but it also doesn't auto-mute the speakers. So EVERYBODY who brings up to install or not install PA does babble and doesn't help. Are there settings for PA, ALSA some GNOME mixer or what ever, that enables what the OP needs?
[arch-general] Black screen with linux-3.4.2
Hi, I've recently upgraded to linux-3.4.2 only to endeavor that it isn't bootable with my hardware. Basically my screen gets black during boot-up and remains so without anything I can do about it. I've got a Nvidia GPU (310M) driven by nouveau, which worked reasonably fine for the last couple of months. I can remember that there was exactly the same issue with kernels prior to 2.6.38 (or 2.6.39?), so I'm quite unhappy about the regression. I haven't looked much into it yet, just wanted to know whether anyone is also affected by this and/or whether or not this is already known (to the kernel developers)? Otherwise I would probably have to mail to some kernel developing list, wouldn't I? Best regards, Karol Babioch signature.asc Description: OpenPGP digital signature
Re: [arch-general] Black screen with linux-3.4.2
On Fri, 2012-06-15 at 14:21 +0200, Karol Babioch wrote: linux-3.4.2 Nvidia GPU (310M) driven by nouveau 3.4.2-rt10-1-rt x86_64 does work with the nv driver and a GeForce 7200GS, aka 7300 SE. I always run into trouble with nouveau, but for the last months with kernel-rt 3.4.2-rt10-1-rt X couldn't start using the nv driver. For the Arch linux (not linux-rt) kernels there never where issues with X, while using the nvidia driver. Last and current version on Arch here is 3.3.8-1. A script is switching between nv and nvidia at startup, regarding to the kernel I'll boot. This list not only is scrappy regarding to the number of cards, but also doesn't provide for all contingencies: http://nouveau.freedesktop.org/wiki/HardwareStatus I only can portend to audio real-time, while for my gfx card are already issues without audio real-time usage. Dunno if you ask, because you do development for the driver or the kernel. For all people who want a stable desktop, nouveau IMO seldom is a good choice.
Re: [arch-general] Muting internal speakers
On 15/06/12 14:12, Ralf Mardorf wrote: On Fri, 2012-06-15 at 13:00 +0100, Mauro Santos wrote: Have you actually tried using the latest pulseaudio for a couple of weeks? For supported hardware it sure does something somewhat similar to what the OP wants. It sure seems you have some gripe with pulseaudio and/or pulseaudio's upstream and are on a personal crusade to bash it every time you can. Pulseaudio is not perfect but neither is alsa, if alsa only solves the problem then fine, if some user has better luck with pulseaudio+alsa so be it, the user will decide for itself if it sucks or not so just let it rest. Ubuntu Studio Precise chips with a new version of PA and a PA Jack bridge. RME HDSPe AIO started working when PA was removed, it didn't work with PA. Regarding to this thread it's irrelevant. BOT as mentioned before, the OP seem to use GNOME, so it's likely that he already has PA installed. Audio out is ok, so PA doesn't cause trouble, but it also doesn't auto-mute the speakers. So EVERYBODY who brings up to install or not install PA does babble and doesn't help. Are there settings for PA, ALSA some GNOME mixer or what ever, that enables what the OP needs? That could be done with udev and ALSA or with PA. At least a PA solution is/was in the wiki (as far as I remember)
Re: [arch-general] Muting internal speakers
Hi, You have rather new laptop, right? So most probable is that you have soundcard based on HDA chipset, you could check this with this command (type it in your favourite terminal emulator, like xterm or gnome-terminal): $ lsmod | grep hda If you see something like snd_hda_codec it means that you have it :) Now from Kernel documentation: Another related problem is the automatic mute of speaker output by headphone plugging. This feature is implemented in most cases, but not on every preset model or codec-support code. In anyway, try a different model option if you have such a problem. Some other models may match better and give you more matching functionality. If none of the available models works, send a bug report. See the bug report section for details. It basically means that driver for your card is buggy, or is wrongly advertised by BIOS to kernel and bad driver is assign to handle the card. In that situation you could try to manually assign it. At [1] you've got comprehensible thread what to do with it. I hope that help :) [1] http://ubuntuforums.org/showthread.php?t=1043568 Pozdrawiam Łukasz Redynk W dniu 14.06.2012 22:52, Nelson Marambio pisze: Since the change from Win 7 to Arch there is just one function I really miss up to now. Perhaps someone of you can help me out. Is it possible that Arch deactivates the internal speakers of my laptop when I plug in my USB-headset and turn input / output to this ? In Windows I could define the USB headset as default for in-/output so Win made a fallback to internal speakers only when I plugged out the headset again. It would be really great if Arch was that comfortable too. I know in GNOME there are just two clicks to do for switching to another audio hardware but ... :D Warm regards, Nelson.
Re: [arch-general] Muting internal speakers
Am Fri, 15 Jun 2012 13:00:56 +0100 schrieb Mauro Santos registo.maill...@gmail.com: Have you actually tried using the latest pulseaudio for a couple of weeks? For supported hardware it sure does something somewhat similar to what the OP wants. It sure seems you have some gripe with pulseaudio and/or pulseaudio's upstream and are on a personal crusade to bash it every time you can. Pulseaudio is not perfect but neither is alsa, if alsa only solves the problem then fine, if some user has better luck with pulseaudio+alsa so be it, the user will decide for itself if it sucks or not so just let it rest. I haven't tried using the latest PA for a couple of weeks, because I've got an M-Audio Audiophile 24/96. And this is one of those (semi-)professional audio cards which are not supported by PA. So, yes, I have made my experiences. It's not a personal crusade, and it's not bashing. It's just my personal experiences with PA, which totally doesn't work with my audio card. The problems that I have in those discussions, why I bash it (as you call it), are those: 1. PA may work with some certain sound cards (only consumer sound cards), but not with every sound and audio card. Still it always gets hyped as the ultimate sound server by the PA fanboys, which allegedly solves every problem and question. But unfortunately those fanboys are usually only those users who only know their own SoundBlaster or AC'97 onboard sound card and simply ignore the fact that there are some other, more professional audio cards. So they think if PA works for them, it has to work for everybody else, which is totally wrong. 2. Those PA fanboys ignore the fact, that PA indeed is an additional layer which can indeed cause additional issues, which make it harder to find the real reason for those issues. 3. Even the PA developers blame ALSA, which works perfectly with those more professional audio cards out-of-the-box, for the bugs in PA, even if it was clear that it is PA's fault. 4. The PA developers try to having made PA to a new de facto Linux standard - that's at least my impression -, even if it doesn't support every sound and audio card. From a de facto Linux standard it can be expected that it supports every hardware of that kind. Until this is not the case it just has to be called crap, if it's treated as a standard. 5. It's somehow related to 4. At least the GNOME developers and some distribution developers force the users to install PA as a dependency of GNOME or the whole distro. This probably isn't a problem for those PA fanboys with some consumer cards. But it is a very big problem for people who own a better sound or audio card, which doesn't work with PA. Those people not only want but even need a working sound output. 6. The PA fanboys always answer every sound related question by suggesting to install PA, regardless of the question and if the problem can be easily solved in other ways. 7. The PA fanboys seem to be persuaded that PA doesn't have and never will have any bugs. 8. PA is just overrated regarding its features. Maybe there are use cases for PA, maybe it can make some things a bit easier for some people. But it's in most cases not necessary as some PA fanboys are always claiming. And this is not bashing. Those are just facts. If PA would be treated as a normal and optional piece of software which can be installed or not, and if it would not be treated as a de facto Linux standard, and if the users would not be forced to install PA as a dependency, I would have absolutely no problem with PA. But as long as the situation is as I described above, you always will read such comments, if someone mentions PA. Either PA has to support every sound and audio card incl. the (semi-)professional audio cards as they are meant to be used (not crippled down to stereo cards) or PA has to be removed as a dependency from every desktop environment and distro. And the PA fanboys should consider if it's really necessary to install PA to solve a problem or to answer a question, or if there are easier ways (in user friendlyness and in KISS). And they should ask before, if PA would even make sense for the questioner. That's the point. Heiko
Re: [arch-general] Black screen with linux-3.4.2
Hi, to be honest, I didn't want to start a discussion about the nouveau driver vs. the Nvidia one. Am 15.06.2012 14:49, schrieb Ralf Mardorf: Dunno if you ask, because you do development for the driver or the kernel. No, if I would, I probably wouldn't have to ask ;). Am 15.06.2012 14:49, schrieb Ralf Mardorf: For all people who want a stable desktop, nouveau IMO seldom is a good choice. I made the opposing experience within the last couple of years several times. nouveau works out of the box and does integrate with the rest of the system quite well. The proprietary blob made some issues with switching between X and TTY for my setup the last time I tried. From my experience nouveau is just not as good as the Nvidia one when it comes down to 3D performance and/or energy management. Hopefully this will get better in future releases ;). However the problem remains :(. Best regards, Karol Babioch signature.asc Description: OpenPGP digital signature
Re: [arch-general] Muting internal speakers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/15/12 04:52, Heiko Baums wrote: Am Fri, 15 Jun 2012 18:22:45 +0800 schrieb ShichaoGao xgd...@gmail.com: True! Maybe many people got the bad impression of PA in previous versions. Wrong! Maybe many people got the bad impression of PA, because PA just still doesn't work with their audio cards, and because PA still causes more problems than it solves. I think it *might* be possible to configure PulseAudio to work correctly. But in my experience, only LinuxMint has gotten this right out of the box. In *all* other cases (prior to Arch Linux), I have had to make a point of rowing upstream to expunge as much of pulseaudio as I possibly could (I've generally had to leave the libraries) in order to get sound working. And in the majority of these cases over the last few years, removing pulseaudio was the *only* thing I had to do to get sound working. - -- David Benfell benf...@parts-unknown.org -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJP2zhTAAoJELT202JKF+xp7rQP/3RYI29mQYvfbOdbNEsvQtxe B0h65a1IEvh/siTrySXwoUb0t237Wc1KmY1pN2i0TdOlR6wtXVIPDV9aXYjoCU+8 dWgS+Od1YHUWBUEssvTNlF/4QN6EzKzBAtaE17oQrvRAJHcvFYGyPMEkBEqWvZNY GbxItrV3gayOMjne41smc3qflTN3PjAudfJ5oMIEVO776ZGjfZJ5ymZeWQ6fvN/1 Suwkcc/WLZDH4drAqQk88trud3KTvvWXk4su/Qs6lMg9AsTPbR7C5Hp4sBA1GjA2 d2OM9mYYCuSnxp5gXdcRQIeFPYGfk37yZ8ad1be+F0hUA0/oQ5o5Sy0GLHLcPyGL MAZoI+JRZOdB0l04VI+KY0e+84hQUzxde6PVToIV1tC4Lfn3nSFffKgJKccNqKLW 7lGLxDPNFiNXvVRPylaPlhXwL/yP7Ri7ZkdNXU5aCtZkg4R+iiMPJchabRFnBM59 PSVqGRffIsrOdEZ5oDL74qivj5tCEpth+wgELfd3eTW+gCHOGMzJlsMTdV3SokO9 J/365HpnV06UgTwNneON+1bRrhSVq24chj6dI9qTRHfqPTJ0JKgif6PyClhnBIvm 3CIndq8UYmSWe+opduKX9s8RE3vTChO3JYrmJ2l9eGPD96RhH+7VXAdL9H59e/dp HmkJcrjCFGHt4WvCcbny =4KbF -END PGP SIGNATURE-
Re: [arch-general] Shutdown and reboot not working after last weekend update
2012/6/15 Ralf Mardorf ralf.mard...@alice-dsl.net On Thu, 2012-06-14 at 11:37 -0300, Victor Silva wrote: Also, is there a procedure I can use to have multiple kernels? Don't name the packages/kernels linux. Name them linux, linux-1, linux-2 etc.?! You also could get different kernels from the repositories, of course not different versions of linux, but e.g. linux + linux-rt. $ ls /mnt/archlinux/boot/vmlinuz* /mnt/archlinux/boot/vmlinuz-linux /mnt/archlinux/boot/vmlinuz-linux-rt Oki. I will try it on the weekend. There seems to be an official bug now: https://bugs.archlinux.org/task/30136 I will provide them the link of our discussion.
Re: [arch-general] Black screen with linux-3.4.2
On Fri, 2012-06-15 at 15:27 +0200, Karol Babioch wrote: From my experience nouveau is just not as good as the Nvidia one when it comes down to 3D performance and/or energy management. 3D and energy management can be important, but isn't needed by everybody. If you want to run this kernel and don't need 3D, the nv driver might work, it at least does on my machine with the rt patched version of the kernel you wish to use. http://www.archlinux.org/packages/extra/i686/xf86-video-nv/ http://www.archlinux.org/packages/extra/x86_64/xf86-video-nv/ I hope it won't be dropped by Arch. Other distros dropped it. - Ralf
Re: [arch-general] Black screen with linux-3.4.2
Am 15.06.2012 16:22, schrieb Ralf Mardorf: http://www.archlinux.org/packages/extra/i686/xf86-video-nv/ http://www.archlinux.org/packages/extra/x86_64/xf86-video-nv/ I hope it won't be dropped by Arch. Other distros dropped it. It will be dropped, as it isn't developped anymore and will soon be incompatible with xorg-server. signature.asc Description: OpenPGP digital signature
[arch-general] Shutdown issue - after updates yesterday
After updating my systems yesterday I am getting a line with a fail at shutdown at the sigterm/killterm point on the screen after exiting from X. I can't find anything in the logs directly related to this but I do have in /var/log/errors/log: Jun 15 10:58:22 localhost NetworkManager[1441]: nm_supplicant_info_set_call: assertion `call != NULL' failed during the bootup time. I know that NetworkManager has had issues in Fedora 16 for a while - eg https://bugzilla.redhat.com/show_bug.cgi?id=826706 but I don't know if this is related or not. I am running networkmanager 0.9.4.0-5 -- mike c
Re: [arch-general] Shutdown and reboot not working after last weekend update
On 06/14/2012 03:12 PM, Victor Silva wrote: I have no shares. Can I somehow try to umount everything in mtab? I'm not familiar with the internal workings of mtab. I will read a bit. Also the only thing I assume could be hanging is my external HD which I disconnected having no effect on the problem behavior. Still I reported that my /boot partition was being mounted and listed on kde file manager (forgot its name) which was not default behavior. So could be the case that /boot is hanging my shoutdown? I don't get the reason umount -a shutdown -h now did not do the trick. I ask gently again if you could inform me why did the magic reboot did work while shutdown did not. Regards, Victor Victor, I am no expert in the shutdown logic that Arch uses, but it is fairly easy to follow. During shutdown, /etc/rc.shutdown is called and the 'umount_all' command is supposed to take care of unmounting all non-api filesystems. If you have specific commands you need run in _addition to_ what is done by rc.shutdown, then you can put those commands in /etc/rc.local.shutdown. The /etc/rc.local.shutdown must be executable to be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is called close to the beginning of rc.shutdown. Looking at your mtab file and comparing to mine, I do not have any usb drives connected to my system. Somebody more familiar with issues related to usb drives will need to comment. You might want to try Guillermo's shutdown modified as follows: umount -arfl -t usbfs,fuseblk I don't know if that will do it, but you have 5 fuseblk filesystems and 1 usbfs mounted. I don't know how Arch handles their unmounting. Lastly, I do not use the gnome gvfs-fuse-daemon. That is another entry to look at and make sure it isn't the issue. Maybe try your rc.local.shutdown with: umount -arfl -t usbfs,fuseblk killall gvfs-fuse-daemon # or whatever that process actually runs as -- David C. Rankin, J.D.,P.E.
Re: [arch-general] Muting internal speakers
On Jun 15, 2012 9:19 PM, Łukasz Redynk lukas.red...@gmail.com wrote It basically means that driver for your card is buggy, or is wrongly advertised by BIOS to kernel and bad driver is assign to handle the card. In that situation you could try to manually assign it. At [1] you've got comprehensible thread what to do with it. I hope that help :) No it wouldn't because he was talking about a separate USB device.
Re: [arch-general] Muting internal speakers
Having a bit more time to think now, to the OP, if this discussion hasn't scared you off, ask me for my device switching script, am not at my laptop now. And for Heiko On Jun 15, 2012 9:23 PM, Heiko Baums li...@baums-on-web.de wrote: I haven't tried using the latest PA for a couple of weeks, because I've got an M-Audio Audiophile 24/96. And this is one of those (semi-)professional audio cards which are not supported by PA. So, yes, I have made my experiences. It's not a personal crusade, and it's not bashing. It's just my personal experiences with PA, which totally doesn't work with my audio card. That load of drivel below isn't bashing? You refer to fanboys and proceed to list a whole loss of statements not made by anyone in this thread. And then you insist that for pulse to be standard it must conform to your standards, which by the way something like cups also fails. Man, I can't believe my office photocopier can't print out stapled copies using cups, it shouldn't be called a standard until it can do that Not to mention the multiple times you assume that pulse is being forced on everyone just because it's a dependency of some software. May as well complain how X is being forced on everyone. You, sir, are a troll. The problems that I have in those discussions, why I bash it (as you call it), are those: 1. PA may work with some certain sound cards (only consumer sound cards), but not with every sound and audio card. Still it always gets hyped as the ultimate sound server by the PA fanboys, which allegedly solves every problem and question. But unfortunately those fanboys are usually only those users who only know their own SoundBlaster or AC'97 onboard sound card and simply ignore the fact that there are some other, more professional audio cards. So they think if PA works for them, it has to work for everybody else, which is totally wrong. 2. Those PA fanboys ignore the fact, that PA indeed is an additional layer which can indeed cause additional issues, which make it harder to find the real reason for those issues. 3. Even the PA developers blame ALSA, which works perfectly with those more professional audio cards out-of-the-box, for the bugs in PA, even if it was clear that it is PA's fault. 4. The PA developers try to having made PA to a new de facto Linux standard - that's at least my impression -, even if it doesn't support every sound and audio card. From a de facto Linux standard it can be expected that it supports every hardware of that kind. Until this is not the case it just has to be called crap, if it's treated as a standard. 5. It's somehow related to 4. At least the GNOME developers and some distribution developers force the users to install PA as a dependency of GNOME or the whole distro. This probably isn't a problem for those PA fanboys with some consumer cards. But it is a very big problem for people who own a better sound or audio card, which doesn't work with PA. Those people not only want but even need a working sound output. 6. The PA fanboys always answer every sound related question by suggesting to install PA, regardless of the question and if the problem can be easily solved in other ways. 7. The PA fanboys seem to be persuaded that PA doesn't have and never will have any bugs. 8. PA is just overrated regarding its features. Maybe there are use cases for PA, maybe it can make some things a bit easier for some people. But it's in most cases not necessary as some PA fanboys are always claiming. And this is not bashing. Those are just facts. If PA would be treated as a normal and optional piece of software which can be installed or not, and if it would not be treated as a de facto Linux standard, and if the users would not be forced to install PA as a dependency, I would have absolutely no problem with PA. But as long as the situation is as I described above, you always will read such comments, if someone mentions PA. Either PA has to support every sound and audio card incl. the (semi-)professional audio cards as they are meant to be used (not crippled down to stereo cards) or PA has to be removed as a dependency from every desktop environment and distro. And the PA fanboys should consider if it's really necessary to install PA to solve a problem or to answer a question, or if there are easier ways (in user friendlyness and in KISS). And they should ask before, if PA would even make sense for the questioner. That's the point. Heiko
Re: [arch-general] Black screen with linux-3.4.2
Am 15.06.2012 14:21, schrieb Karol Babioch: Hi, I've recently upgraded to linux-3.4.2 only to endeavor that it isn't bootable with my hardware. Basically my screen gets black during boot-up and remains so without anything I can do about it. I've got a Nvidia GPU (310M) driven by nouveau, which worked reasonably fine for the last couple of months. I can remember that there was exactly the same issue with kernels prior to 2.6.38 (or 2.6.39?), so I'm quite unhappy about the regression. I haven't looked much into it yet, just wanted to know whether anyone is also affected by this and/or whether or not this is already known (to the kernel developers)? Otherwise I would probably have to mail to some kernel developing list, wouldn't I? Best regards, Karol Babioch Hi, I have the same problem on my laptop and reported the bug weeks ago: https://bugs.freedesktop.org/show_bug.cgi?id=50175 no reaction from the developers yet, maybe it will get more attention if you comment on the bug report and confirm the issue.
Re: [arch-general] Shutdown issue - after updates yesterday
On Fri, Jun 15, 2012 at 4:04 PM, mike cloaked mike.cloa...@gmail.com wrote: After updating my systems yesterday I am getting a line with a fail at shutdown at the sigterm/killterm point on the screen after exiting from X. I can't find anything in the logs directly related to this but I do have in /var/log/errors/log: Jun 15 10:58:22 localhost NetworkManager[1441]: nm_supplicant_info_set_call: assertion `call != NULL' failed during the bootup time. I know that NetworkManager has had issues in Fedora 16 for a while - eg https://bugzilla.redhat.com/show_bug.cgi?id=826706 but I don't know if this is related or not. I am running networkmanager 0.9.4.0-5 To be more clear during the shutdown at the point where there is Sending SIGTERM signal to processes it gives BUSY at the right side which stays some seconds and turns to FAIL in red before moving on to Sending SIGKILL to processes on the next line and then shuts down quickly after that. Before updates yesterday this did not happen. The pacman log for yesterday's updates is: [2012-06-14 18:11] Running 'pacman -Syu' [2012-06-14 18:11] synchronizing package lists [2012-06-14 18:11] starting full system upgrade [2012-06-14 18:11] upgraded jre7-openjdk-headless (7.u4_2.2-1 - 7.u5_2.2.1-1) [2012-06-14 18:12] upgraded jre7-openjdk (7.u4_2.2-1 - 7.u5_2.2.1-1) [2012-06-14 18:12] upgraded jdk7-openjdk (7.u4_2.2-1 - 7.u5_2.2.1-1) [2012-06-14 18:12] upgraded kdelibs (4.8.4-1 - 4.8.4-2) [2012-06-14 18:12] installed pambase (20120602-1) [2012-06-14 18:12] upgraded pam (1.1.5-3 - 1.1.5-4) [2012-06-14 19:08] Running 'pacman -Syu' [2012-06-14 19:08] synchronizing package lists [2012-06-14 19:08] starting full system upgrade [2012-06-14 19:08] upgraded unrar (4.2.3-1 - 4.2.4-1) Only today was the kernel moved to 3.4 with the same issue. Anyone else seeing this, or suggest how I might get some debug info? Thanks -- mike c
Re: [arch-general] Shutdown issue - after updates yesterday
On Fri, Jun 15, 2012 at 5:33 PM, mike cloaked mike.cloa...@gmail.com wrote: On Fri, Jun 15, 2012 at 4:04 PM, mike cloaked mike.cloa...@gmail.com wrote: After updating my systems yesterday I am getting a line with a fail at shutdown at the sigterm/killterm point on the screen after exiting from X. I can't find anything in the logs directly related to this but I do have in /var/log/errors/log: Jun 15 10:58:22 localhost NetworkManager[1441]: nm_supplicant_info_set_call: assertion `call != NULL' failed during the bootup time. I know that NetworkManager has had issues in Fedora 16 for a while - eg https://bugzilla.redhat.com/show_bug.cgi?id=826706 but I don't know if this is related or not. I am running networkmanager 0.9.4.0-5 To be more clear during the shutdown at the point where there is Sending SIGTERM signal to processes it gives BUSY at the right side which stays some seconds and turns to FAIL in red before moving on to Sending SIGKILL to processes on the next line and then shuts down quickly after that. Before updates yesterday this did not happen. The pacman log for yesterday's updates is: [2012-06-14 18:11] Running 'pacman -Syu' [2012-06-14 18:11] synchronizing package lists [2012-06-14 18:11] starting full system upgrade [2012-06-14 18:11] upgraded jre7-openjdk-headless (7.u4_2.2-1 - 7.u5_2.2.1-1) [2012-06-14 18:12] upgraded jre7-openjdk (7.u4_2.2-1 - 7.u5_2.2.1-1) [2012-06-14 18:12] upgraded jdk7-openjdk (7.u4_2.2-1 - 7.u5_2.2.1-1) [2012-06-14 18:12] upgraded kdelibs (4.8.4-1 - 4.8.4-2) [2012-06-14 18:12] installed pambase (20120602-1) [2012-06-14 18:12] upgraded pam (1.1.5-3 - 1.1.5-4) [2012-06-14 19:08] Running 'pacman -Syu' [2012-06-14 19:08] synchronizing package lists [2012-06-14 19:08] starting full system upgrade [2012-06-14 19:08] upgraded unrar (4.2.3-1 - 4.2.4-1) Only today was the kernel moved to 3.4 with the same issue. Anyone else seeing this, or suggest how I might get some debug info? Thanks Hmm - it seems this may be related to an update today: [2012-06-15 09:42] upgraded networkmanager (0.9.4.0-4 - 0.9.4.0-5) Others are posting the same symptoms at: https://bbs.archlinux.org/viewtopic.php?id=143371 -- mike c
Re: [arch-general] Shutdown issue - after updates yesterday
On Fri, Jun 15, 2012 at 5:39 PM, mike cloaked mike.cloa...@gmail.com wrote: I can't find anything in the logs directly related to this but I do have in /var/log/errors/log: Jun 15 10:58:22 localhost NetworkManager[1441]: nm_supplicant_info_set_call: assertion `call != NULL' failed during the bootup time. snip Hmm - it seems this may be related to an update today: [2012-06-15 09:42] upgraded networkmanager (0.9.4.0-4 - 0.9.4.0-5) Others are posting the same symptoms at: https://bbs.archlinux.org/viewtopic.php?id=143371 -- mike c Reported as FS#30305 at https://bugs.archlinux.org -- mike c
Re: [arch-general] Shutdown and reboot not working after last weekend update
On 06/15/2012 08:29 AM, David C. Rankin wrote: On 06/14/2012 03:12 PM, Victor Silva wrote: I have no shares. Can I somehow try to umount everything in mtab? I'm not familiar with the internal workings of mtab. I will read a bit. Also the only thing I assume could be hanging is my external HD which I disconnected having no effect on the problem behavior. Still I reported that my /boot partition was being mounted and listed on kde file manager (forgot its name) which was not default behavior. So could be the case that /boot is hanging my shoutdown? I don't get the reason umount -a shutdown -h now did not do the trick. I ask gently again if you could inform me why did the magic reboot did work while shutdown did not. Regards, Victor Victor, I am no expert in the shutdown logic that Arch uses, but it is fairly easy to follow. During shutdown, /etc/rc.shutdown is called and the 'umount_all' command is supposed to take care of unmounting all non-api filesystems. If you have specific commands you need run in _addition to_ what is done by rc.shutdown, then you can put those commands in /etc/rc.local.shutdown. The /etc/rc.local.shutdown must be executable to be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is called close to the beginning of rc.shutdown. Looking at your mtab file and comparing to mine, I do not have any usb drives connected to my system. Somebody more familiar with issues related to usb drives will need to comment. You might want to try Guillermo's shutdown modified as follows: umount -arfl -t usbfs,fuseblk I don't know if that will do it, but you have 5 fuseblk filesystems and 1 usbfs mounted. I don't know how Arch handles their unmounting. Lastly, I do not use the gnome gvfs-fuse-daemon. That is another entry to look at and make sure it isn't the issue. Maybe try your rc.local.shutdown with: umount -arfl -t usbfs,fuseblk killall gvfs-fuse-daemon # or whatever that process actually runs as While reading through this to see how much it relates to my shutdown issues, I have noticed this. With gvfs-fuse-daemon install I noticed in top it is being run with what I would think is an incorrect command. /usr/lib/gvfs//gvfs-fuse-daemon -f /home/user/.gvfs The double slash is not a typo on my part that is how it is listed. Do you see the same results when seeing how the gvfs daemon is being run on the system? I am going to try reinstalling it and seeing if it will install properly and not be run with the double slash. Have not noticed this until today.
Re: [arch-general] Black screen with linux-3.4.2
Hi, Am 15.06.2012 18:08, schrieb Mus: no reaction from the developers yet, maybe it will get more attention if you comment on the bug report and confirm the issue Thanks for the link. Have already commented there. However I made the experience in the past that bug trackers are not that popular for kernel development. Seems that most stuff is going on on mailing lists. Interestingly enough I've got a Sony VAIO (VPCS12C5E), just like you. Probably Sony screwed something up here. I've just mailed on the developers list. Hopefully someone will look into it. Best regards, Karol Babioch signature.asc Description: OpenPGP digital signature
Re: [arch-general] Shutdown and reboot not working after last weekend update
On 06/15/2012 08:29 AM, David C. Rankin wrote: On 06/14/2012 03:12 PM, Victor Silva wrote: I have no shares. Can I somehow try to umount everything in mtab? I'm not familiar with the internal workings of mtab. I will read a bit. Also the only thing I assume could be hanging is my external HD which I disconnected having no effect on the problem behavior. Still I reported that my /boot partition was being mounted and listed on kde file manager (forgot its name) which was not default behavior. So could be the case that /boot is hanging my shoutdown? I don't get the reason umount -a shutdown -h now did not do the trick. I ask gently again if you could inform me why did the magic reboot did work while shutdown did not. Regards, Victor Victor, I am no expert in the shutdown logic that Arch uses, but it is fairly easy to follow. During shutdown, /etc/rc.shutdown is called and the 'umount_all' command is supposed to take care of unmounting all non-api filesystems. If you have specific commands you need run in _addition to_ what is done by rc.shutdown, then you can put those commands in /etc/rc.local.shutdown. The /etc/rc.local.shutdown must be executable to be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is called close to the beginning of rc.shutdown. Looking at your mtab file and comparing to mine, I do not have any usb drives connected to my system. Somebody more familiar with issues related to usb drives will need to comment. You might want to try Guillermo's shutdown modified as follows: umount -arfl -t usbfs,fuseblk I don't know if that will do it, but you have 5 fuseblk filesystems and 1 usbfs mounted. I don't know how Arch handles their unmounting. Lastly, I do not use the gnome gvfs-fuse-daemon. That is another entry to look at and make sure it isn't the issue. Maybe try your rc.local.shutdown with: umount -arfl -t usbfs,fuseblk killall gvfs-fuse-daemon # or whatever that process actually runs as Well just tried reinstalling made no difference. So I guess I will be looking it why it is starting that way. It may or may not be related to the shutdown issues. But other than this one thing my symptoms seem to match this minus the screen turning red when freezing. I will post back here if I sort anything out that may help this problem.
Re: [arch-general] *** GMX Spamverdacht *** Re: Muting internal speakers
Am 15.06.2012 18:05, schrieb Oon-Ee Ng: Having a bit more time to think now, to the OP, if this discussion hasn't scared you off, Well, I have to confess that I became a bit meek by following the discussion. Actually I just wanted to get a solution to my problem.:) Oon-Ee, It would be great if you can send me your script or tell me the article in the wiki. Heiko, by installing GNOME, pulseaudio was installed as dependency I guess. So please don't blame for starting with pulse, ok ? ^^ After all I am confused if my installation uses ALSA or pulse now. I installed ALSA but the ALSAmixer shows me the volume level of pulse ??? If you made the experience that pulse failed where ALSA succeeded there is nothing to say against it. But I have to deal with my consumer-card (it's really an HDA-chip by Intel) and thus I can't contribute something relevant. What I learned from this discussion 1) there are several sound-layer (OSS, ALSA, pulse, Jack (?)) 2) several layer can work together but also can result conflicts (nothing but logical) Spoken without any irony: thank you all for this experience. I already have at least two more question and I will use this mailinglist with pleasure ! P.S.: Don't care about the headline from GMX. German Mail-Provider sometimes handle mails writen in English very hysterical. I try to train the server-located Spamfilter with every new mail from this ML but it will take a while.
Re: [arch-general] Muting internal speakers
Hi Nelson :) don't worry. I try to explain in simple words, so it's not a perfect explanation. We are humans, nobody is a fanboy neither a troll. Since you seem to be a human too, you soon will be familiar with this stuff too. On Fri, 2012-06-15 at 20:00 +0200, Nelson Marambio wrote: After all I am confused if my installation uses ALSA or pulse now. I installed ALSA but the ALSAmixer shows me the volume level of pulse ??? Pulse handles audio streams, but does use ALSA. If you made the experience that pulse failed where ALSA succeeded there is nothing to say against it. But I have to deal with my consumer-card (it's really an HDA-chip by Intel) and thus I can't contribute something relevant. You wrote that you're a newbie and that you use GNOME, so the people who suggested to install pulse where mistaken, since it's already installed and Heiko was mistaken, since audio does work on your machine. What I learned from this discussion 1) there are several sound-layer (OSS, ALSA, pulse, Jack (?)) OSS (obsolete) and ALSA are the instances that are needed for audio. Pulse and Jack are layers. 2) several layer can work together but also can result conflicts (nothing but logical) Yes! Spoken without any irony: thank you all for this experience. I already have at least two more question and I will use this mailinglist with pleasure ! P.S.: Don't care about the headline from GMX. German Mail-Provider sometimes handle mails writen in English very hysterical. I try to train the server-located Spamfilter with every new mail from this ML but it will take a while. We know, we don't care. OTOH it's easy to edit the subject. However, you're welcome and I apologize for that idiotic pulse discussion. Again, everybody should have been aware that your card does work with PA and that it didn't automatically satisfies your need to auto-mute the speakers. Regards, Ralf
Re: [arch-general] Muting internal speakers
On Fri, 2012-06-15 at 20:13 +0200, Ralf Mardorf wrote: OSS (obsolete) and ALSA are the instances that are needed for audio. Pulse and Jack are layers. Sorry for my broken English. You need one of both, the obsolete OSS or the current used ALSA. Stuff similar to PA and jackd, there were (are) others too, handle the audio streams in different ways, but usually use ALSA as backend. Firewire audio devices might be something special.
[arch-general] [kernel/update] Found hardware: HDA-Intel: Conexant CX20561 (Hermosa)
Hi, Every day, I run pacman -Syyu on my Arch x86-64 installed on ThinkPad T400. I did it today too and, without a single change in my configuration, I've noticed a new message on boot: Found hardware: HDA-Intel: Conexant CX20561 (Hermosa) ... Hardware is initialized using a generic method It doesn't really bother me, but I wonder where the sudden change from? $ uname -a Linux dog 3.4.2-2-ARCH #1 SMP PREEMPT Mon Jun 11 22:27:17 CEST 2012 x86_64 GNU/Linux Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
Re: [arch-general] Muting internal speakers
You wrote that you're a newbie and that you use GNOME, I am new to Arch but have used Linux for years already before. But there were often problems with release upgrade, lately worse with Mint that is a nice distro though. So I got Arch recommended as of its bleeding-edge-style. I wouldn't be too optimistic that a complete Linux newbie would be able to get Arch started. We know, we don't care. OTOH it's easy to edit the subject. Indeed ! Right now I've whitelisted the ML-address in the GMX portal, However, you're welcome and I apologize for that idiotic pulse discussion. Again, everybody should have been aware that your card does work with PA and that it didn't automatically satisfies your need to auto-mute the speakers. As I said in the OP it was just a question to use Arch even more comfortable, not as a must-have. If this comes to the conclusion that my soundchip has no suitable kernel-support for this aspect yet then this is ok for me. Warm regards, Nelson.
Re: [arch-general] Muting internal speakers
W dniu 15.06.2012 17:53, Oon-Ee Ng pisze: On Jun 15, 2012 9:19 PM, Łukasz Redynk lukas.red...@gmail.com wrote It basically means that driver for your card is buggy, or is wrongly advertised by BIOS to kernel and bad driver is assign to handle the card. In that situation you could try to manually assign it. At [1] you've got comprehensible thread what to do with it. I hope that help :) No it wouldn't because he was talking about a separate USB device. Ok, I've missed the USB part and thought it's about mini jack connection, my bad. -- Pozdrawiam Łukasz Redynk
Re: [arch-general] [kernel/update] Found hardware: HDA-Intel: Conexant CX20561 (Hermosa)
Hi, Am 15.06.2012 20:35, schrieb Mateusz Loskot: It doesn't really bother me, but I wonder where the sudden change from? Noticed this also. In my case two pieces of hardware get found and the status on the right column says failed. Haven't looked into it yet, but probably something else is expected as a return value. But everything works just as usual, even the state of the mixer is being restored, so this is not a major issue for me. Best regards, Karol Babioch signature.asc Description: OpenPGP digital signature
Re: [arch-general] [kernel/update] Found hardware: HDA-Intel: Conexant CX20561 (Hermosa)
On 15 June 2012 19:49, Karol Babioch ka...@babioch.de wrote: Am 15.06.2012 20:35, schrieb Mateusz Loskot: It doesn't really bother me, but I wonder where the sudden change from? Noticed this also. In my case two pieces of hardware get found and the status on the right column says failed. Haven't looked into it yet, but probably something else is expected as a return value. In my case, nothing fails. Here is screenshot: http://www.flickr.com/photos/mloskot/7375548454/ But everything works just as usual, even the state of the mixer is being restored, so this is not a major issue for me. Indeed, same here. I'm just curious. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
Re: [arch-general] [kernel/update] Found hardware: HDA-Intel: Conexant CX20561 (Hermosa)
Hi, Am 15.06.2012 21:12, schrieb Mateusz Loskot: In my case, nothing fails. You've backgrounded alsa. Could you try to start it in the foreground, and see if it still doesn't fail? I would be surprised, to be honest. Best regards, Karol Babioch signature.asc Description: OpenPGP digital signature
Re: [arch-general] [kernel/update] Found hardware: HDA-Intel: Conexant CX20561 (Hermosa)
On Fri, Jun 15, 2012 at 3:12 PM, Mateusz Loskot mate...@loskot.net wrote: On 15 June 2012 19:49, Karol Babioch ka...@babioch.de wrote: Am 15.06.2012 20:35, schrieb Mateusz Loskot: It doesn't really bother me, but I wonder where the sudden change from? Noticed this also. In my case two pieces of hardware get found and the status on the right column says failed. Haven't looked into it yet, but probably something else is expected as a return value. In my case, nothing fails. Here is screenshot: http://www.flickr.com/photos/mloskot/7375548454/ But everything works just as usual, even the state of the mixer is being restored, so this is not a major issue for me. Indeed, same here. I'm just curious. If the driver of your sound hardware changes, then the stored state doesn't apply cleanly, and you will get such a message. I generally see it every time we move to a new kernel series (i.e., 3.3 - 3.4). What I do is to check the mixer settings and fix them if needed, and then run alsactl store by hand so as to update the saved state immediately rather than waiting for it to happen at shutdown time. At that point it matches the new driver and you won't see this message again.
Re: [arch-general] [kernel/update] Found hardware: HDA-Intel: Conexant CX20561 (Hermosa)
On 15 June 2012 20:16, Karol Babioch ka...@babioch.de wrote: Am 15.06.2012 21:12, schrieb Mateusz Loskot: In my case, nothing fails. You've backgrounded alsa. Could you try to start it in the foreground, and see if it still doesn't fail? I would be surprised, to be honest. No difference, doesn't fail: http://www.flickr.com/photos/mloskot/7375588834/ Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
Re: [arch-general] [kernel/update] Found hardware: HDA-Intel: Conexant CX20561 (Hermosa)
On 15 June 2012 20:19, Ray Kohler ataraxia...@gmail.com wrote: On Fri, Jun 15, 2012 at 3:12 PM, Mateusz Loskot mate...@loskot.net wrote: On 15 June 2012 19:49, Karol Babioch ka...@babioch.de wrote: Am 15.06.2012 20:35, schrieb Mateusz Loskot: It doesn't really bother me, but I wonder where the sudden change from? Noticed this also. In my case two pieces of hardware get found and the status on the right column says failed. Haven't looked into it yet, but probably something else is expected as a return value. In my case, nothing fails. Here is screenshot: http://www.flickr.com/photos/mloskot/7375548454/ But everything works just as usual, even the state of the mixer is being restored, so this is not a major issue for me. Indeed, same here. I'm just curious. If the driver of your sound hardware changes, then the stored state doesn't apply cleanly, and you will get such a message. I generally see it every time we move to a new kernel series (i.e., 3.3 - 3.4). I see. What I do is to check the mixer settings and fix them if needed, and then run alsactl store by hand so as to update the saved state immediately rather than waiting for it to happen at shutdown time. At that point it matches the new driver and you won't see this message again. Bingo! It does the trick, thanks Ray! Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
[arch-general] Kernel Update 3.3.8.1 - 3.4.2-2 failed
With the next reboot after today's System Update (which included updates for pkg's linux and nvidia) the kernel was not able the partitions anymore and froze. Having the system restored with a liveCD and chroot I found in pacman.log dozens of lines like this [2012-06-15 17:39] - Running build hook: [fsck] [2012-06-15 17:39] cp: cannot stat '/lib/modules/3.4.2-2-ARCH/kernel/drivers/at$ [2012-06-15 17:39] cp: cannot stat '/lib/modules/3.4.2-2-ARCH/kernel/drivers/hi$ [2012-06-15 17:39] cp: cannot stat '/lib/modules/3.4.2-2-ARCH/kernel/drivers/hi$ [2012-06-15 17:39] cp: cannot stat '/lib/modules/3.4.2-2-ARCH/kernel/drivers/hi$ [2012-06-15 17:39] cp: cannot stat '/lib/modules/3.4.2-2-ARCH/kernel/drivers/hi$ [2012-06-15 17:39] cp: cannot stat '/lib/modules/3.4.2-2-ARCH/kernel/drivers/hi$ [2012-06-15 17:39] cp: cannot stat '/lib/modules/3.4.2-2-ARCH/kernel/drivers/hi$ [2012-06-15 17:39] cp: cannot stat '/lib/modules/3.4.2-2-ARCH/kernel/drivers/hi$ Because no one else reported this here it seems to be specific to my installation. Did the modules move to another directory with 3.4.2-2 oder did I miss a package in the past ? Best regards, Nelson. P.S.: In pacman.conf I have the packages 'linux' and 'nvidia' to the 'IgnorePkgs' line but this shouldn't be the last clue I guess.
Re: [arch-general] Kernel Update 3.3.8.1 - 3.4.2-2 failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/15/12 13:13, Nelson Marambio wrote: With the next reboot after today's System Update (which included updates for pkg's linux and nvidia) the kernel was not able the partitions anymore and froze. Having the system restored with a liveCD and chroot I found in pacman.log dozens of lines like this [2012-06-15 17:39] - Running build hook: [fsck] [2012-06-15 17:39] cp: cannot stat '/lib/modules/3.4.2-2-ARCH/kernel/drivers/at$ [2012-06-15 17:39] cp: cannot stat '/lib/modules/3.4.2-2-ARCH/kernel/drivers/hi$ [2012-06-15 17:39] cp: cannot stat '/lib/modules/3.4.2-2-ARCH/kernel/drivers/hi$ [2012-06-15 17:39] cp: cannot stat '/lib/modules/3.4.2-2-ARCH/kernel/drivers/hi$ [2012-06-15 17:39] cp: cannot stat '/lib/modules/3.4.2-2-ARCH/kernel/drivers/hi$ [2012-06-15 17:39] cp: cannot stat '/lib/modules/3.4.2-2-ARCH/kernel/drivers/hi$ [2012-06-15 17:39] cp: cannot stat '/lib/modules/3.4.2-2-ARCH/kernel/drivers/hi$ [2012-06-15 17:39] cp: cannot stat '/lib/modules/3.4.2-2-ARCH/kernel/drivers/hi$ Because no one else reported this here it seems to be specific to my installation. Did the modules move to another directory with 3.4.2-2 oder did I miss a package in the past ? I also saw this. It seems to have sorted itself out, but I had previously relinked depmod, which had previously effectively been linked to /sbin/usr/bin/kmod, as follows: graton% ls -al $(which depmod) lrwxrwxrwx 1 root root 13 Jun 8 21:53 /sbin/depmod - /usr/bin/kmod Notice that the link is absolute rather than relative. As a precaution, I ran: graton# pacman -S linux warning: linux-3.4.2-2 is up to date -- reinstalling And it was fine. - -- David Benfell benf...@parts-unknown.org -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJP25j3AAoJELT202JKF+xpCfkP/1kC0PD4TZg3yhQnp2UOLsSa s17J/CIQUOPFNiP9huR/FnOO9mWjXXx+y8RD1pC41Jf6v+P9n5cCWs6rHul4JhOS IPS8WHkgoXdmIpzWGJY23TPLKTsT70iRwid0aH3Kj2dUuoCrnU6qYvqM6jCuD/SO ude0sMZUcXCOFK3AJytIZGSr3w5hVPcXl/xONwbCVtozsA9JCgiuXD/MorkySv1h 98zWpAf3tTYa9pZ9ENhaDl35/qW77w2attidlA24VhZUlo4X8Am0e0tWcWzkTumD mWyENFR1aycZObaIgVzsh7jNKscoxqd81Ip4F0CJNHPUQvI+pj8vXYSiBPi9Nb6P uxN2shozqP7ONJycgFS4YtRXkopATJOUTlwy3hLGwglBHdkpUeKSMwnO7xZ6kDng laX4pzHVs/Gy5WZUQxszcTHqJZQxCYPKnaYHUSWLArMHak3DcbltTN5YlilWELhl dI74DjWPmOsBpJaLpKR9QGOS8guYmmXLDpP28sVRFMCtDHgUC3JspcMivD6Odghe h5aMNwpPzwJhsgBz/KwoHPDvdk03vzc6FLkwq8Vbho2hxdfW9U014pVFLNpX+CTT l9+whC8oFk50GVEgJ+viffX+7ZNunSzmOgFpcSaYS4Cos3ai4ze58fWPTIO2OXE8 gfM+iFZ/zVmQ6rg8UMio =yqx/ -END PGP SIGNATURE-
Re: [arch-general] Muting internal speakers
Am Fri, 15 Jun 2012 06:27:47 -0700 schrieb David Benfell benf...@parts-unknown.org: I think it *might* be possible to configure PulseAudio to work correctly. But in my experience, only LinuxMint has gotten this right out of the box. Unfortunately not. The configuration methods you find in the web, in several forums and mailing lists is just a workaround. Well, I wouldn't even call it workaround, because those professional audio cards are crippled down to simple stereo cards by those configurations. PA is not able to handle those audio cards as they are meant to be handled. And in the majority of these cases over the last few years, removing pulseaudio was the *only* thing I had to do to get sound working. I must admit that I'm not a GNOME user, I'm using Xfce, but I don't think that it is the right way to force the users to install PA as a dependency, even if PA can be uninstalled afterwards. On the other hand I read that it's not that easy to just uninstall PA. Heiko
Re: [arch-general] Muting internal speakers
Am Sat, 16 Jun 2012 00:05:11 +0800 schrieb Oon-Ee Ng ngoonee.t...@gmail.com: That load of drivel below isn't bashing? You refer to fanboys and proceed to list a whole loss of statements not made by anyone in this thread. And then you insist that for pulse to be standard it must conform to your standards, which by the way something like cups also fails. Man, I can't believe my office photocopier can't print out stapled copies using cups, it shouldn't be called a standard until it can do that Not to mention the multiple times you assume that pulse is being forced on everyone just because it's a dependency of some software. May as well complain how X is being forced on everyone. You, sir, are a troll. That's funny. A troll is calling someone else, who just wrote facts, a troll. But you may keep comparing apples with oranges, if it makes you happy. If your photocopier can't print out staple copies using cups, this is totally different from not being able to hear any sound, because you only have a professional audio card and the sound server you are forced to use is not able to handle this audio card. And cups is not the only printing server. You see the difference? Heiko
Re: [arch-general] *** GMX Spamverdacht *** Re: Muting internal speakers
Am Fri, 15 Jun 2012 20:00:10 +0200 schrieb Nelson Marambio nelsonmaram...@gmx.de: Heiko, by installing GNOME, pulseaudio was installed as dependency I guess. That's one of the problems I have with PA, indeed. ;-) So please don't blame for starting with pulse, ok ? I don't blame you, but I blame the people who always at once suggest installing and using PA as the ultimate solution and answer for everything. And I blame the developers who force the users to installing PA as a dependency. If PA is working for you, you want to deal with PA and PA solves your problem, it's totally OK for me. ^^ After all I am confused if my installation uses ALSA or pulse now. I installed ALSA but the ALSAmixer shows me the volume level of pulse ??? I guess alsamixer only shows its own volume level. PA can set its own volume level which is, of course, relative to the ALSA level. Just turn up the volume to the highest level in PA and switch the volume level in alsamixer. I guess then you will have a clue. If you made the experience that pulse failed where ALSA succeeded there is nothing to say against it. But I have to deal with my consumer-card (it's really an HDA-chip by Intel) and thus I can't contribute something relevant. What I learned from this discussion 1) there are several sound-layer (OSS, ALSA, pulse, Jack (?)) 2) several layer can work together but also can result conflicts (nothing but logical) That's absolutely right. With one exception, OSS and ALSA are two different sound drivers on the same level. OSS is the older one, and I don't know if there's still an up-to-date version. ALSA has a OSS plugin for compatibility reasons. PulseAudio and Jack are two sound servers which are on the layer on top of ALSA or OSS. Heiko
Re: [arch-general] Shutdown and reboot not working after last weekend update
2012/6/15 Don deJuan donjuans...@gmail.com On 06/15/2012 08:29 AM, David C. Rankin wrote: On 06/14/2012 03:12 PM, Victor Silva wrote: I have no shares. Can I somehow try to umount everything in mtab? I'm not familiar with the internal workings of mtab. I will read a bit. Also the only thing I assume could be hanging is my external HD which I disconnected having no effect on the problem behavior. Still I reported that my /boot partition was being mounted and listed on kde file manager (forgot its name) which was not default behavior. So could be the case that /boot is hanging my shoutdown? I don't get the reason umount -a shutdown -h now did not do the trick. I ask gently again if you could inform me why did the magic reboot did work while shutdown did not. Regards, Victor Victor, I am no expert in the shutdown logic that Arch uses, but it is fairly easy to follow. During shutdown, /etc/rc.shutdown is called and the 'umount_all' command is supposed to take care of unmounting all non-api filesystems. If you have specific commands you need run in _addition to_ what is done by rc.shutdown, then you can put those commands in /etc/rc.local.shutdown. The /etc/rc.local.shutdown must be executable to be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is called close to the beginning of rc.shutdown. Looking at your mtab file and comparing to mine, I do not have any usb drives connected to my system. Somebody more familiar with issues related to usb drives will need to comment. You might want to try Guillermo's shutdown modified as follows: umount -arfl -t usbfs,fuseblk I don't know if that will do it, but you have 5 fuseblk filesystems and 1 usbfs mounted. I don't know how Arch handles their unmounting. Lastly, I do not use the gnome gvfs-fuse-daemon. That is another entry to look at and make sure it isn't the issue. Maybe try your rc.local.shutdown with: umount -arfl -t usbfs,fuseblk killall gvfs-fuse-daemon # or whatever that process actually runs as Well just tried reinstalling made no difference. So I guess I will be looking it why it is starting that way. It may or may not be related to the shutdown issues. But other than this one thing my symptoms seem to match this minus the screen turning red when freezing. I will post back here if I sort anything out that may help this problem. I wil try this at home but I'1m at work atm, https://bugs.archlinux.org/task/30136 ry this kernel paramether reboot=pci More info: http://intosimple.blogspot.com.br/2012/06/reboot-on-dell-latitude-e6520-with-arch.html
Re: [arch-general] Shutdown and reboot not working after last weekend update
On 06/15/2012 02:48 PM, Victor Silva wrote: 2012/6/15 Don deJuan donjuans...@gmail.com On 06/15/2012 08:29 AM, David C. Rankin wrote: On 06/14/2012 03:12 PM, Victor Silva wrote: I have no shares. Can I somehow try to umount everything in mtab? I'm not familiar with the internal workings of mtab. I will read a bit. Also the only thing I assume could be hanging is my external HD which I disconnected having no effect on the problem behavior. Still I reported that my /boot partition was being mounted and listed on kde file manager (forgot its name) which was not default behavior. So could be the case that /boot is hanging my shoutdown? I don't get the reason umount -a shutdown -h now did not do the trick. I ask gently again if you could inform me why did the magic reboot did work while shutdown did not. Regards, Victor Victor, I am no expert in the shutdown logic that Arch uses, but it is fairly easy to follow. During shutdown, /etc/rc.shutdown is called and the 'umount_all' command is supposed to take care of unmounting all non-api filesystems. If you have specific commands you need run in _addition to_ what is done by rc.shutdown, then you can put those commands in /etc/rc.local.shutdown. The /etc/rc.local.shutdown must be executable to be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is called close to the beginning of rc.shutdown. Looking at your mtab file and comparing to mine, I do not have any usb drives connected to my system. Somebody more familiar with issues related to usb drives will need to comment. You might want to try Guillermo's shutdown modified as follows: umount -arfl -t usbfs,fuseblk I don't know if that will do it, but you have 5 fuseblk filesystems and 1 usbfs mounted. I don't know how Arch handles their unmounting. Lastly, I do not use the gnome gvfs-fuse-daemon. That is another entry to look at and make sure it isn't the issue. Maybe try your rc.local.shutdown with: umount -arfl -t usbfs,fuseblk killall gvfs-fuse-daemon # or whatever that process actually runs as Well just tried reinstalling made no difference. So I guess I will be looking it why it is starting that way. It may or may not be related to the shutdown issues. But other than this one thing my symptoms seem to match this minus the screen turning red when freezing. I will post back here if I sort anything out that may help this problem. I wil try this at home but I'1m at work atm, https://bugs.archlinux.org/task/30136 ry this kernel paramether reboot=pci More info: http://intosimple.blogspot.com.br/2012/06/reboot-on-dell-latitude-e6520-with-arch.html After reading more into that parameter I found this http://linux.koolsolutions.com/2009/08/04/howto-fix-linux-hangfreeze-during-reboots-and-restarts/ They show more options. I am going to try the one you suggested shortly and if that does not work do the other suggested option in the link I posted. Thanks for pointing out your findings.
[arch-general] Keyboard and mouse not working in X
Last night, I updated my system with everything from the past week or so. Everything went smoothly. Today, however, I discovered that upon launching X, using, for instance, xinit /usr/bin/xterm my computer stops responding to my USB keyboard and mouse. I can't even switch back to the console using CTRL-ALT-FN. If I SIGTERM the process from ssh, X closes normally and my keyboard resumes function in the console. I've checked, and none of the files in /etc/X11 were modified anytime recently. Any advice? pants.
Re: [arch-general] Muting internal speakers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/15/12 13:29, Heiko Baums wrote: I must admit that I'm not a GNOME user, I'm using Xfce, but I don't think that it is the right way to force the users to install PA as a dependency, even if PA can be uninstalled afterwards. On the other hand I read that it's not that easy to just uninstall PA. I found it more annoying to uninstall pulseaudio than difficult. And it's fair to say I was already annoyed, so there has also been a cathartic element to it. Basically, using whatever package manager was appropriate to the distribution, I searched and removed pulse*, remembering that some packages that list pulseaudio as a dependency are in fact meta-packages that simply exist to bring in all associated packages and which can in fact be removed once you have a functioning installation (though you may find you want to mark other desired packages as manually selected). - -- David Benfell benf...@parts-unknown.org -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJP28B3AAoJELT202JKF+xpeJ8P/2qbU6eYkaae9FoI1n0mtE8q doxyw/mLx3e5hABhFrf5CS90ocJDYQ6EqIBM4bkSHCuBvkfu7nOnJtACicwhyjkK 6JOHsUpUmXhpiFT78jvzRvJMFjIb+NOu5uzycaSDw3CctnztZVGtSb9f5u6Cui0r kVRLFdDiSypN5PKt2zlQaDmXaJZo7qNCDeyDiNly1TRb2pWB1MtEcVzxbHXkyaNo 5UE90DERjvLS2oULNHogVhjilKjJhx5mKD5n/kjlumpbBicNL1u03lMZ5pLKAvkp 8apsXiomDzRJW/cichooQhe3PTe1GFKRf8lDFRzH6DfzRrKYJhWdwBVm5/Cxn4aj P+ANM4Lk6FGAPQvfWDUHsDC+Ts85jd+9alsK+q95oovOSlBUDPCeDgRxS9K7Qh4S E/stwF6sVXaBNRxHZI3dnYge0OHVNQGh0b3aKFoOlc1wKvZQksmagOP5TBUEnO91 BIpINq38mk3IiWwJ5gDhuEQZrWFbyzurkCMD8XK046+s6tTGKkGc64H/3KSloekK hxPjhVM1LehIqQWJxJGs3poCuqva2Q5xFo7oYvVvFYF1/pDGNZNU1F+AaB8Z9/0B xU1vLFidK7WdkLYgZrnVzgSk7OLGEhTTu3F63eLSM3xPX2XOTWxejJz2uNHG6+Jy SFb7w3aiqUeY4ADbUAbK =dxpN -END PGP SIGNATURE-
Re: [arch-general] Keyboard and mouse not working in X
Hi, Am 16.06.2012 00:35, schrieb pants: Any advice? What does the logfile say? Any errors or something like that? Best regards, Karol Babioch signature.asc Description: OpenPGP digital signature
Re: [arch-general] Keyboard and mouse not working in X
On Sat 16 Jun 2012 01:15:07 AM CEST, Karol Babioch wrote: Hi, Am 16.06.2012 00:35, schrieb pants: Any advice? What does the logfile say? Any errors or something like that? Best regards, Karol Babioch Had the same problem one week ago, i was able to switch back to a tty with sysrq r. What i did was reinstall the linux package (compat wireless unistall messed the modules i think) and rebuild the initramfs. Maybe it helps. Cheers, Jonas signature.asc Description: OpenPGP digital signature
Re: [arch-general] Keyboard and mouse not working in X
What does the logfile say? Any errors or something like that? I could find no relevant errors. Have a look for yourself, though: http://pastebin.com/MnCLjL3T pants.
Re: [arch-general] Keyboard and mouse not working in X
What i did was reinstall the linux package (compat wireless unistall messed the modules i think) and rebuild the initramfs. Unfortunately, I do not think this will help. This morning, before discovering this problem, I installed a new version of the linux package (3.4.2-2) and rebuilt the initramfs without installing any other packages, and haven't installed any other packages since. I can't imagine that repeating this would be a solution. pants.
[arch-general] gcc 4.7.1 - any estimate for Arch?
Guys, Just checking to see if anybody has a guestimate on when gcc 4.7.1 might be ready for Arch? I have an infinite loop issue with the Trinity builds in 4.7 that is reportedly corrected on Fedora 17 with the latest gcc. 4.7.1 was release upstream yesterday. Just checking on whether there are any hurdles to get over before we see it in Arch. Thanks. -- David C. Rankin, J.D.,P.E.
Re: [arch-general] gcc 4.7.1 - any estimate for Arch?
On 06/16/2012 02:43 AM, David C. Rankin wrote: Guys, Just checking to see if anybody has a guestimate on when gcc 4.7.1 might be ready for Arch? I have an infinite loop issue with the Trinity builds in 4.7 that is reportedly corrected on Fedora 17 with the latest gcc. 4.7.1 was release upstream yesterday. Just checking on whether there are any hurdles to get over before we see it in Arch. Thanks. OMFG. Arch is not rolling anymore. -- Ionuț signature.asc Description: OpenPGP digital signature
Re: [arch-general] Keyboard and mouse not working in X
Sorry for double posting, but this is just to report that the sysreq trick you recommended does not work in my case. Indeed, not even the capslock light responds; it's like the keyboard is being completely ignored by my system. pants.
Re: [arch-general] Muting internal speakers
On Jun 16, 2012 4:48 AM, Heiko Baums li...@baums-on-web.de wrote: Am Sat, 16 Jun 2012 00:05:11 +0800 schrieb Oon-Ee Ng ngoonee.t...@gmail.com: That load of drivel below isn't bashing? You refer to fanboys and proceed to list a whole loss of statements not made by anyone in this thread. And then you insist that for pulse to be standard it must conform to your standards, which by the way something like cups also fails. Man, I can't believe my office photocopier can't print out stapled copies using cups, it shouldn't be called a standard until it can do that Not to mention the multiple times you assume that pulse is being forced on everyone just because it's a dependency of some software. May as well complain how X is being forced on everyone. You, sir, are a troll. That's funny. A troll is calling someone else, who just wrote facts, a troll. But you may keep comparing apples with oranges, if it makes you happy. Your facts are opinions and assumptions, mostly about putting words in the mythical pulse fanboy's mouth. Not to mention totally unhelpful to the discussion. If your photocopier can't print out staple copies using cups, this is totally different from not being able to hear any sound, because you only have a professional audio card and the sound server you are forced to use is not able to handle this audio card. And cups is not the only printing server. You see the difference? Your previous email indicated sounds could be heard, but only stereo sound. Afaik that's the case for most 5.1 and all 7.1 cards. How is that different from cups not supporting advanced options in my printer? Because pulse is the only existing sound server? You can't and won't use pulse, fine, just don't use it. Jack or pure alsa still work. Just stop pretending that your arbitrary criteria for pulse is in any way an inalienable truth. Just to summarize, it seems your two main gripes are lack of support for semi pro cards and being forced to use it. The former is not likely to change, the latter is patently untrue seeing as how you are already not using it. Heiko
Re: [arch-general] *** GMX Spamverdacht *** Re: Muting internal speakers
On Jun 16, 2012 2:00 AM, Nelson Marambio nelsonmaram...@gmx.de wrote: Am 15.06.2012 18:05, schrieb Oon-Ee Ng: Having a bit more time to think now, to the OP, if this discussion hasn't scared you off, Well, I have to confess that I became a bit meek by following the discussion. Actually I just wanted to get a solution to my problem.:) Oon-Ee, It would be great if you can send me your script or tell me the article in the wiki. Still not on my laptop, but I searched around, posted it a while back on the pulseaudio wiki. Here it is http://www.freedesktop.org/wiki/Software/PulseAudio/FAQ#How_do_I_switch_the_default_sound_card.2C_moving_all_applications.3F Again, not sure if by now there's a way to run this script whenever a card is plugged in and out, if you do find that let me know =). Like I said, I just bind the script to a shortcut key using xbindkeys
Re: [arch-general] Shutdown and reboot not working after last weekend update
2012/6/15 Don deJuan donjuans...@gmail.com On 06/15/2012 02:48 PM, Victor Silva wrote: 2012/6/15 Don deJuan donjuans...@gmail.com On 06/15/2012 08:29 AM, David C. Rankin wrote: On 06/14/2012 03:12 PM, Victor Silva wrote: I have no shares. Can I somehow try to umount everything in mtab? I'm not familiar with the internal workings of mtab. I will read a bit. Also the only thing I assume could be hanging is my external HD which I disconnected having no effect on the problem behavior. Still I reported that my /boot partition was being mounted and listed on kde file manager (forgot its name) which was not default behavior. So could be the case that /boot is hanging my shoutdown? I don't get the reason umount -a shutdown -h now did not do the trick. I ask gently again if you could inform me why did the magic reboot did work while shutdown did not. Regards, Victor Victor, I am no expert in the shutdown logic that Arch uses, but it is fairly easy to follow. During shutdown, /etc/rc.shutdown is called and the 'umount_all' command is supposed to take care of unmounting all non-api filesystems. If you have specific commands you need run in _addition to_ what is done by rc.shutdown, then you can put those commands in /etc/rc.local.shutdown. The /etc/rc.local.shutdown must be executable to be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is called close to the beginning of rc.shutdown. Looking at your mtab file and comparing to mine, I do not have any usb drives connected to my system. Somebody more familiar with issues related to usb drives will need to comment. You might want to try Guillermo's shutdown modified as follows: umount -arfl -t usbfs,fuseblk I don't know if that will do it, but you have 5 fuseblk filesystems and 1 usbfs mounted. I don't know how Arch handles their unmounting. Lastly, I do not use the gnome gvfs-fuse-daemon. That is another entry to look at and make sure it isn't the issue. Maybe try your rc.local.shutdown with: umount -arfl -t usbfs,fuseblk killall gvfs-fuse-daemon # or whatever that process actually runs as Well just tried reinstalling made no difference. So I guess I will be looking it why it is starting that way. It may or may not be related to the shutdown issues. But other than this one thing my symptoms seem to match this minus the screen turning red when freezing. I will post back here if I sort anything out that may help this problem. I wil try this at home but I'1m at work atm, https://bugs.archlinux.org/**task/30136https://bugs.archlinux.org/task/30136 ry this kernel paramether reboot=pci More info: http://intosimple.blogspot.**com.br/2012/06/reboot-on-dell-** latitude-e6520-with-arch.htmlhttp://intosimple.blogspot.com.br/2012/06/reboot-on-dell-latitude-e6520-with-arch.html After reading more into that parameter I found this http://linux.koolsolutions.**com/2009/08/04/howto-fix-** linux-hangfreeze-during-**reboots-and-restarts/http://linux.koolsolutions.com/2009/08/04/howto-fix-linux-hangfreeze-during-reboots-and-restarts/ They show more options. I am going to try the one you suggested shortly and if that does not work do the other suggested option in the link I posted. Thanks for pointing out your findings. A new kernel update was avaliable fo me today. I hoped it could fix some of the issues we were facing. In fact now I have tons of errors, dbus seems screwd and many other things, among the problems I have now is that X fails with no screen found (both nv and nvidia drivers) and I have no network interfaces I fail to get eth0 up. So *DO NOT UPDATE YOUR KERNELS *I'm quite sad as this is a even bigger mistake than the last one. So I think I need to chroot again rever to the old kernel... Anyone else expecting this kind of problem? Btw the reboor parameters for the kernel (which I've tested before the upgrade) also did not work. Regards, Victor
Re: [arch-general] Keyboard and mouse not working in X
More double posting, but there's an update: if I unplug the keyboard and mouse and then reconnect them once X is running, they work fine and they continue to work after closing X and reopening it. This does not, however, continue to be true after rebooting. pants. On Fri, Jun 15, 2012 at 05:14:53PM -0700, pants wrote: Sorry for double posting, but this is just to report that the sysreq trick you recommended does not work in my case. Indeed, not even the capslock light responds; it's like the keyboard is being completely ignored by my system. pants.
Re: [arch-general] Muting internal speakers
Am Fri, 15 Jun 2012 16:08:40 -0700 schrieb David Benfell benf...@parts-unknown.org: I found it more annoying to uninstall pulseaudio than difficult. And it's fair to say I was already annoyed, so there has also been a cathartic element to it. Basically, using whatever package manager was appropriate to the distribution, I searched and removed pulse*, remembering that some packages that list pulseaudio as a dependency are in fact meta-packages that simply exist to bring in all associated packages and which can in fact be removed once you have a functioning installation (though you may find you want to mark other desired packages as manually selected). This sounds like PA isn't a dependency for GNOME any longer? This would mean that it's just a downstream bug, and PA should be handled as an optional dependency or not as a dependency at all by the distros. Heiko
Re: [arch-general] Muting internal speakers
Am Sat, 16 Jun 2012 08:23:54 +0800 schrieb Oon-Ee Ng ngoonee.t...@gmail.com: Your facts are opinions and assumptions, mostly about putting words in the mythical pulse fanboy's mouth. Not to mention totally unhelpful to the discussion. I would say, your nonsense is unhelpful. And my facts are facts. Just read them again, and read all other discussions about questions or problems regarding PA, and you will see it. Those people, who always mention PA as their first and ultimate suggestions without thinking about it - if it really helps, if it really doesn't add additional problems, if it's really useful or necessary for the questioner -, who always say that PA can't have any bugs and can't cause any problems are just fanboys, because this all is just nonsense. If PA works for you, go for it. But if it works for you, doesn't mean, that PA is generally good. And its super-duper features are in most cases just unnecessary. You should really think about that, before you write such a stuff and call other people a troll. Your previous email indicated sounds could be heard, but only stereo sound. Afaik that's the case for most 5.1 and all 7.1 cards. How is that different from cups not supporting advanced options in my printer? Because pulse is the only existing sound server? It's different, because those professional audio cards are not stereo sound cards and are not meant for that. And with the users being forced to install and use PA, professional users just can't use these audio cards and can't do their job in the worst case. That's the difference. And, btw., this crippling down to a stereo sound card didn't work for me either if I recall correctly. Buy such an audio card and try it yourself, and you will see. Or ask all the other pro-audio users who need such audio cards. They all will tell you the same. In fact they already did. You can't and won't use pulse, fine, just don't use it. Jack or pure alsa still work. I don't use PA, and I don't use GNOME. But there are people who like GNOME and want to use it, but they can't use it, at least not always that easily, because PA is installed as a dependency. As David just mentioned, it seems to be possible meanwhile to uninstall PA. Nevertheless it's more than annoying having PA installed as a dependency, if PA is indeed not a real dependency for GNOME anymore. But when I tried PA it was not possible to use pure ALSA anymore. It was just crap. Just stop pretending that your arbitrary criteria for pulse is in any way an inalienable truth. Just to summarize, it seems your two main gripes are lack of support for semi pro cards and being forced to use it. The former is not likely to change, the latter is patently untrue seeing as how you are already not using it. Not untrue, it's true. I have such an audio card and I tested PA myself. I bet you don't have such an audio card, you don't know how they work and you haven't tested PA with them. So who should stop pretending anything? You or me? Heiko
Re: [arch-general] Muting internal speakers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/15/12 18:45, Heiko Baums wrote: This sounds like PA isn't a dependency for GNOME any longer? This would mean that it's just a downstream bug, and PA should be handled as an optional dependency or not as a dependency at all by the distros. More that it is an artifact of how Ubuntu--and I think other distributions, especially those related to Ubuntu--manage their package systems to install all the pieces they choose to install. They create packages--meta-packages--that have no functionality in and of themselves but come with lots and lots of dependencies, those being all the pieces they want to draw in. Then they can, at installation time, essentially list a very short number of meta-packages to install, and let all those dependencies be sorted out by the package manager. So it isn't necessarily really a gnome thing, though that might be how the distributions bring it together. - -- David Benfell benf...@parts-unknown.org -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJP2/P0AAoJELT202JKF+xpeEcP/2E5wNoem9XDO+qSaO2/P7IQ VKFtEOYbNfXhVn9MlkqJK3bbGFAhzZlzg7COOSihhw8kaa2jLA3/G1xjpZoXHoM9 qWIG8f0RTZbUgfMfFG+eeDxZ1ExkkC8fgPgXhfo17qE4f3gZgWU32MkRXGLGlCer wQl/JJ3NlcN3zw/IonPCuHa4SQrQZLBdAyxODZZl1HsYuc+5BkChTqqdP1qZqhzn fzz4NlLI+f/PmQq7AoiTRxJFIQEiHo/E9W9hixMhnzUmZs+42iauFvxdxMQUoUf/ ECPgVYtQAa/7yWxBdH9neVR0gQBLmKo10axLYpSXR7CPvF9UzXpgbHswiaqsoQDK Ag+4LY6QfG8TdZauq55qdm4N161zV8rLEvpzdDOG4fUI3jwBdTRjGmTXztyMGAW7 PwKFF2sA8B6R1n6bY6TB5nrbwQKfEteUvu/oPRY9kPkvrbiDeaPPG0cyU9cwPymt 2b3sH1IAKFNDYXpd1sQ4gRxNcZVZwbZuWUvFyDRvHWFErP4ZQaoRgB/aSfmnY0tP SZIJj/RuSHrYF6xoYmDUhAP4HKPKBBepKbLps+A3uPWV9zt1qpF3XVzS6cuRSMdw XzDmLsTv1Ha7HHfBprfD0+AUdrY2rBJsPYxVhxH+znn4+Ai7qJ2O6eCApJi4YfM6 EkV8Px/4/5Jf7G9cIKvi =hGpd -END PGP SIGNATURE-
Re: [arch-general] Muting internal speakers
On Sat, Jun 16, 2012 at 9:36 AM, Heiko Baums li...@baums-on-web.de wrote: Am Sat, 16 Jun 2012 08:23:54 +0800 schrieb Oon-Ee Ng ngoonee.t...@gmail.com: Your facts are opinions and assumptions, mostly about putting words in the mythical pulse fanboy's mouth. Not to mention totally unhelpful to the discussion. I would say, your nonsense is unhelpful. And my facts are facts. Just read them again, and read all other discussions about questions or problems regarding PA, and you will see it. How is that relevant to this discussion? Or is it now common practice to bring up things posted elsewhere by different people just to prove your point? Straw men are useful that way. Especially when you have an 'either PA is good and awesome or its a useless piece of crap' viewpoint. snip a lot of repeated stuff Just stop pretending that your arbitrary criteria for pulse is in any way an inalienable truth. Just to summarize, it seems your two main gripes are lack of support for semi pro cards and being forced to use it. The former is not likely to change, the latter is patently untrue seeing as how you are already not using it. Not untrue, it's true. I have such an audio card and I tested PA myself. I bet you don't have such an audio card, you don't know how they work and you haven't tested PA with them. So who should stop pretending anything? You or me? Sigh, please read before replying. The LATTER is untrue, I'm not saying that your card works with PA (though you yourself said it does, to a degree, meaning in stereo). You should stop pretending to being forced to use PA (or that anyone in Linux is forced to use PA), because THAT is untrue. In other words, gripe 1 = support for semi-pro cards, gripe 2 = being forced to use PA. Gripe 1 is not likely to change, whether you like it or not. PA is an abstraction which means the application using it doesn't need to care about coding for ALSA. Upstream's decision for now is that supporting non-stereo or 5.1 cards is not yet worth the hassle. Gripe 2 is untrue and just FUD, especially on an Arch Linux list where the developers (wonder in particular) have practically bent over backwards accommodating users who want the choice.
[arch-general] nvidia 295.59-1 dmesg output
Hey guys, after upgrading to 295.59 from 295.53, i am seeing the following in the dmesg output: NVRM: Your system is not currently configured to drive a VGA console NVRM: on the primary VGA device. The NVIDIA Linux graphics driver NVRM: requires the use of a text-mode VGA console. Use of other console NVRM: drivers including, but not limited to, vesafb, may result in NVRM: corruption and stability problems, and is not supported. Any idea what this is about. Seems to be about the framebuffer driver. But earlier no configuration was needed for that. Moreover the virtual console seems to be working fine. Anyone else got a similar message in the log?
Re: [arch-general] nvidia 295.59-1 dmesg output
On 16 June 2012 06:46, gt static.vor...@gmx.com wrote: Hey guys, after upgrading to 295.59 from 295.53, i am seeing the following in the dmesg output: NVRM: Your system is not currently configured to drive a VGA console NVRM: on the primary VGA device. The NVIDIA Linux graphics driver NVRM: requires the use of a text-mode VGA console. Use of other console NVRM: drivers including, but not limited to, vesafb, may result in NVRM: corruption and stability problems, and is not supported. Any idea what this is about. Seems to be about the framebuffer driver. But earlier no configuration was needed for that. Moreover the virtual console seems to be working fine. Anyone else got a similar message in the log? UEFI install by any chance? I ask because the message correlates to http://www.nvnews.net/vbulletin/showpost.php?p=2543252postcount=13 -- Jason Steadman
