[SOLVED] ALSA problem in kernel 2.6.17.13-3

Sound stopped working for normal users after upgrading to 2.6.17.13-3. Root has sound.
$ aplay test.wav
ALSA lib pcm_dmix.c:831:(snd_pcm_dmix_open) unable to create IPC semaphore
aplay: main:550: audio open error: Permission denied
$ groups
audio users

The modules are loaded, sound works great for root.
$ ls -l snd/
crw-rw---- 1 root audio 116, 0 2006-09-16 11:36 controlC0
crw-rw---- 1 root audio 116, 32 2006-09-16 11:36 controlC1
crw-rw---- 1 root audio 14, 18 2006-09-16 11:36 midi1
crw-rw---- 1 root audio 116, 40 2006-09-16 11:36 midiC1D0
crw-rw---- 1 root audio 116, 24 2006-09-16 11:36 pcmC0D0c
crw-rw---- 1 root audio 116, 16 2006-09-16 11:36 pcmC0D0p
crw-rw---- 1 root audio 116, 25 2006-09-16 11:36 pcmC0D1c
crw-rw---- 1 root audio 116, 18 2006-09-16 11:36 pcmC0D2p
crw-rw---- 1 root audio 116, 1 2006-09-16 11:36 seq
crw-rw---- 1 root audio 116, 33 2006-09-16 11:36 timer
$ ls -l sound/
crw-rw---- 1 root audio 14, 12 2006-09-16 11:36 adsp
crw-rw---- 1 root audio 14, 4 2006-09-16 11:36 audio
crw-rw---- 1 root audio 14, 25 2006-09-16 11:36 dmmidi1
crw-rw---- 1 root audio 14, 3 2006-09-16 11:36 dsp
crw-rw---- 1 root audio 14, 0 2006-09-16 11:36 mixer
crw-rw---- 1 root audio 14, 16 2006-09-16 11:36 mixer1
crw-rw---- 1 root audio 14, 1 2006-09-16 11:36 sequencer
crw-rw---- 1 root audio 14, 8 2006-09-16 11:36 sequencer2
My user is in the audio group.
I am running ALSA version 1.0.12-1. Any ideas?

Similar Messages

[SOLVED] Touchpad problems with Kernel-2.6.28

I just updated my kernel to 2.6.28. Everythink is working fine (including my Atheros AGN wireless ). The only problem I have now is the Touchpad. After update the double click on the touchpad and the scroll function is not working any more.
Anyone knows why or is having the same problem?
Last edited by falke (2009-01-26 16:32:31)

Thanks a lot!!! It works! I cant live without touchpad scrolling.
I also needed to create /etc/hal/fdi/policy/shmconfig.fdi with this content:
<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
<device>
<match key="input.x11_driver" string="synaptics">
<merge key="input.x11_options.SHMConfig" type="string">True</merge>
</match>
</device>
</deviceinfo>

[SOLVED]alsa problem after getting USB sound card

so heres what happened. i got new USB headphones. i got them set up as the default alsa sound device but now my problem is that i can only use one audio source at a time (video OR mp3 but not both at the same time...)
my lsusb is
[josh@my-computer ~]$ lsusb
Bus 008 Device 004: ID 043d:0078 Lexmark International, Inc. InkJet Color Printer
Bus 008 Device 002: ID 0609:031d SMK Manufacturing, Inc. eHome Infrared Receiver
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 004: ID 046d:0840 Logitech, Inc. QuickCam Express
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 005: ID 0b38:0003
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 009: ID 093a:2510 Pixart Imaging, Inc. Hama Optical Mouse
Bus 007 Device 008: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
what do i need to do to be able to use more then 1 sound source? if u need me to post any files let me know which ones and i'll post it. i never had this problem with my on board audio(hda intel)
Last edited by monkeyslayer56 (2010-02-26 13:13:42)

i probbaly didn't have to add ALL of that but that was the only help from google i could get that supposedably used virtual surround sound and didn't steal the sound... and ya i read the dmix was supposed to load by default but i guess it wasn't. hopfully i'll get to learn how to configure alsa on my own so i don't have to copy/paste/system specific edit... btw here is my old .asoundrc that wouldn't let more then one divice use it(first on i found that supposedly enabled virtual surround sound)
pcm.!default {
type hw
card 0
ctl.!default {
type hw
card 0
pcm.!surround51 {
type vdownmix
slave.pcm "hw:1,0"
pcm.!surround40 {
type vdownmix
slave.pcm "hw:1,0"

[SOLVED]iwlagn problem after kernel update

yesterday i updated kernel to 2.6.32.10. after reboot kernel.log started with messages like:
Mar 17 09:59:43 laptop kernel: iwlagn 0000:04:00.0: free more than tfds_in_queue (0:1)
log creates that message when i do something online. looks like every time i reload page/ping/do anything online that message goes to kernel.log.
the thing that
worries me is this:
% cat /var/log/kernel.log | grep tfds_in_que | wc -l
20106
my computer is up for less than an hour.
wlan card is intel 5100
does anyone have any suggestion? go back to kernel 2..6.32.9?
EDIT: everything else works fine. wlan is working without a problem.
Last edited by devil_kc (2010-04-10 17:37:20)

i confirm that have the same problem
Network controller: Intel Corporation Wireless WiFi Link 5100
[root@hermes ~]# cat /var/log/kernel.log|grep tfds_in_queue|wc -l
40871
[root@hermes ~]# uptime
20:52:08 up 1:18, 2 users, load average: 0.00, 0.02, 0.05
this is really nasty
from changelog on kernel.org i find this:
commit 44af042e42f2231579ea8ef7586d3789d198f609
Author: Stanislaw Gruszka <[email protected]>
Date: Fri Feb 19 15:47:33 2010 -0800
iwlwifi: sanity check before counting number of tfds can be free
commit a120e912eb51e347f36c71b60a1d13af74d30e83 upstream.
Check the frame control for ieee80211_is_data_qos() is true before
counting the number of tfds can be free, the tfds_in_queue only
increment when ieee80211_is_data_qos() is true before transmit; so it
should only decrement if the type match.
Remove ieee80211_is_data_qos check for frame_ctrl in tx_resp to avoid
invalid information pass from uCode.
Signed-off-by: Stanislaw Gruszka <[email protected]>
Signed-off-by: Wey-Yi Guy <[email protected]>
Signed-off-by: Reinette Chatre <[email protected]>
Signed-off-by: John W. Linville <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Last edited by icarus-c (2010-03-17 09:56:00)

[SOLVED] module problems after kernel update

after update to linux-3.10.10-1 I cannot load some modules anymore:
modprobe: ERROR: could not insert 'tp_smapi': Exec format error
modprobe: ERROR: could not insert 'hdaps': Exec format error
modprobe: ERROR: could not insert 'vboxdrv': Exec format error
seems to be all thinkpad modules plus virtualbox. Probably these packages need an update to work with new kernel..?
Last edited by miro279 (2013-09-01 10:37:37)

Probably they do, yes. How exactly did you update? Did you do pacman -Su (or -Syu), or did you selectively update just some packages? You aren't supposed to update just parts of your system – if you do, weird things happen – such as your kernel suddenly not loading all your modules.
Last edited by Oxyd (2013-08-31 18:48:48)

Solve* ALSA problem

Hello all!
I'm a new user of this forum, and first of all, i would like to thank thins community for helping me migrating from ubunto to arch linux, which i do like very much because of it's freedom of choice and it's challenging installation.
As a new Arch user, i had and have some issues that i had to overcome.
One of them was to put ALSA to work correctly.
First, i'm going to describe my system:
- hp dv25699ep
- (uname -a) Linux (none) 3.3.2-1-ARCH #1 SMP PREEMPT Sat Apr 14 10:08:43 UTC 2012 i686 Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz GenuineIntel GNU/Linux
- DE -> xfce4
My issue with ALSA was that i had a scale that i was not used to see, i only could get sound from "unamplified" to "100%", and from "100%" to "infinity".
The thing was that the sound did not raised linearly, causing the "boom" effect, it raised from mute to "boom" in a little space of the scale.
After many hours searching, i found this website: https://gist.github.com/1904230
which helped me a lot. For those who can't access the website, here's what is says:
Copy pulseaudio configuration template to home folder.
https://gist.github.com/1904230 wrote:1. cp /etc/pulse/default.pa ~/.pulse/default.pa
2. Append ignore_dB=1 to line with load-module module-udev-detect.
3. Make sure "speaker" volume is at 100% using alsamixer (press F6 and select HDA NVidia to see more volume controls.
4. To make "speaker" volume persist between boots, run alsactl store -f ~/.asoundrc then make alsactl restore -f ~/.asoundrc start when logging into your user. (See Arch Wiki - ALSA)
5. Profit.
I read somewhere that the alsa driver was not sending the right dB's to pulse, and pulse simply improvised, is this strange?
I have now verified (after the upper solution) that at 20-30% i can't almost hear anything(no, i'm not deaf ), have anyone got a solution or this is normal?
Thank you!

> aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: Conexant Digital [Conexant Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0

[Solved] Kernel26-2.6.21-8 alsa problem

Hi all,
with the last kernel update my audio card doesn't work anymore.
I obtain these error messages (dmesg output):
snd_pcm: Unknown symbol snd_dma_reserve_buf
snd_pcm: Unknown symbol snd_dma_free_pages
snd_pcm: Unknown symbol snd_malloc_pages
snd_pcm: Unknown symbol snd_dma_get_reserved_buf
snd_pcm: Unknown symbol snd_dma_alloc_pages
snd_pcm: Unknown symbol snd_free_pages
snd_ac97_codec: Unknown symbol snd_interval_refine
snd_ac97_codec: Unknown symbol snd_pcm_hw_rule_add
snd_intel8x0: Unknown symbol snd_ac97_pcm_close
snd_intel8x0: Unknown symbol snd_ac97_resume
snd_intel8x0: Unknown symbol snd_pcm_new
snd_intel8x0: Unknown symbol snd_pcm_limit_hw_rates
snd_intel8x0: Unknown symbol snd_pcm_lib_preallocate_pages_for_all
snd_intel8x0: Unknown symbol snd_ac97_pcm_open
snd_intel8x0: Unknown symbol snd_ac97_set_rate
snd_intel8x0: Unknown symbol snd_ac97_update_bits
snd_intel8x0: Unknown symbol snd_ac97_mixer
snd_intel8x0: Unknown symbol snd_ac97_bus
snd_intel8x0: Unknown symbol snd_dma_free_pages
snd_intel8x0: Unknown symbol snd_ac97_pcm_double_rate_rules
snd_intel8x0: Unknown symbol snd_ac97_update_power
snd_intel8x0: Unknown symbol snd_ac97_suspend
snd_intel8x0: Unknown symbol snd_pcm_lib_malloc_pages
snd_intel8x0: Unknown symbol snd_pcm_lib_ioctl
snd_intel8x0: Unknown symbol snd_pcm_lib_free_pages
snd_intel8x0: Unknown symbol snd_pcm_set_ops
snd_intel8x0: Unknown symbol snd_pcm_hw_constraint_list
snd_intel8x0: Unknown symbol snd_ac97_get_short_name
snd_intel8x0: Unknown symbol snd_pcm_suspend_all
snd_intel8x0: Unknown symbol snd_ac97_pcm_assign
snd_intel8x0: Unknown symbol snd_pcm_hw_constraint_integer
snd_intel8x0: Unknown symbol snd_pcm_hw_constraint_msbits
snd_intel8x0: Unknown symbol snd_dma_alloc_pages
snd_intel8x0: Unknown symbol snd_pcm_period_elapsed
snd_intel8x0: Unknown symbol snd_ac97_tune_hardware
My audio card is:
Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
With the previous kernel there was not problem at all.
Last edited by luca (2007-05-15 19:05:21)

I don't get those error messages, but don't get any sound as well. I own an HP DC7100SFF with integrated chipset on an Intel motherboard.
# lspci -v | grep -i audio
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
# lsmod | grep snd
snd_seq_oss 29056 0
snd_seq_midi_event 6528 1 snd_seq_oss
snd_seq 46800 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 6796 2 snd_seq_oss,snd_seq
snd_pcm_oss 38816 0
snd_mixer_oss 14336 1 snd_pcm_oss
snd_intel8x0 28700 0
snd_ac97_codec 95396 1 snd_intel8x0
ac97_bus 2432 1 snd_ac97_codec
snd_pcm 68484 4 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer 19076 2 snd_seq,snd_pcm
snd 44388 10 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore 6496 1 snd
snd_page_alloc 7816 3 snd_intel8x0,snd_pcm
# dmesg | grep intel8x0
intel8x0_measure_ac97_clock: measured 54858 usecs
intel8x0: clocking to 48000
As this is the first time I installed Linux on this machine, I cannot say whether the onboard chipset works with an earlier kernel (or alsa) version. I am in the audio group, sound (even 'headphones') is unmuted... Alsamixer says "Chip: Analog Devices AD1981B", is this correct?
The Alsa-site suggests putting some options in modules.conf. Is this method still supported in Arch Linux? Or has this nothing to do with my sound chipset? At least it doesn't solve the problem.
Any help would be appreciated.
Last edited by Marcel- (2007-05-22 23:28:16)

I'm getting kernel panics each day as I shut down, the message of restarting by holding down the power button appears on the screen - it began about a month ago and. Do you have any ideas of how to solve the problem?

I'm getting kernel panics each day as I shut down, the message of restarting by holding down the power button appears on the screen - it began about a month ago and. Do you have any ideas of how to solve the problem? I've copied the logs that I found for each kernel panic that still have the message logged. Please help if you can, I have read some of the other comments and perhaps it has something to do with my anti-virus software being on at start up. I have copied the log here. Any advice will be welcome.
Interval Since Last Panic Report: 665204 sec
Panics Since Last Report:          8
Anonymous UUID: D6DCC90D-A5CA-4BBE-A435-3E64A512A51B
Sat May 26 07:23:05 2012
panic(cpu 3 caller 0xffffff80002b4f36): trying to interlock destroyed mutex (0xffffff801a489be0)
Backtrace (CPU 3), Frame : Return Address
0xffffff8160313b00 : 0xffffff8000220792
0xffffff8160313b80 : 0xffffff80002b4f36
0xffffff8160313b90 : 0xffffff8000227e68
0xffffff8160313bd0 : 0xffffff7f80d14250
0xffffff8160313c20 : 0xffffff7f80d14f73
0xffffff8160313cc0 : 0xffffff800059a237
0xffffff8160313d00 : 0xffffff8000586cbf
0xffffff8160313d20 : 0xffffff800057e6e3
0xffffff8160313df0 : 0xffffff800057ed06
0xffffff8160313e20 : 0xffffff8000583c52
0xffffff8160313e70 : 0xffffff8000583d05
0xffffff8160313e90 : 0xffffff80005358b4
0xffffff8160313ef0 : 0xffffff80005367c3
0xffffff8160313f30 : 0xffffff8000536897
0xffffff8160313f60 : 0xffffff80005ccfe8
0xffffff8160313fb0 : 0xffffff80002da5e9
      Kernel Extensions in backtrace:
com.intego.iokit.VBX6NKE(1.0)[211D5E46-3E43-C5DC-9C6A-8C3FFF0F4493]@0xffffff7f8 0d11000->0xffffff7f80d1bfff
dependency: com.apple.iokit.IONetworkingFamily(2.1)[2FCC16E1-34AB-3908-98BD-CCBFA56FFDCE]@0 xffffff7f809b7000
BSD process name corresponding to current thread: iStatLocalDaemon
Mac OS version:
11E53
Kernel version:
Darwin Kernel Version 11.4.0: Mon Apr 9 19:32:15 PDT 2012; root:xnu-1699.26.8~1/RELEASE_X86_64
Kernel UUID: A8ED611D-FB0F-3729-8392-E7A32C5E7D74
System model name: iMac11,2 (Mac-F2238AC8)
System uptime in nanoseconds: 69777074610
last loaded kext at 58265763561: com.intego.iokit.VBX6NKE            1 (addr 0xffffff7f80d11000, size 45056)
loaded kexts:
com.intego.iokit.VBX6NKE            1
com.intego.iokit.BehavioralKext            1
com.intego.kext.VirusBarrier.AppBarrierKPI            10.6.8
com.intego.kext.VirusBarrierKPI            10.6.8
com.globaldelight.driver.BoomDevice            1.1
com.huawei.driver.HuaweiDataCardACMData            4.2
Model: iMac11,2, BootROM IM112.0057.B01, 2 processors, Intel Core i3, 3.2 GHz, 12 GB, SMC 1.64f5
Graphics: ATI Radeon HD 5670, ATI Radeon HD 5670, PCIe, 512 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1333 MHz, 0x802C, 0x31364A53463531323634485A2D3147344431
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1333 MHz, 0x802C, 0x31364A53463531323634485A2D3147344431
Memory Module: BANK 0/DIMM1, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353637334648302D4348392020
Memory Module: BANK 1/DIMM1, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353637334648302D4348392020
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x8F), Atheros 9280: 4.0.64.8-P2P
Bluetooth: Version 4.0.5f11, 2 service, 18 devices, 1 incoming serial ports
Serial ATA Device: ST31000528AS, 1 TB
Serial ATA Device: OPTIARC DVD RW AD-5680H
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfa100000 / 2
USB Device: USB2.0 Hub, 0x05e3 (Genesys Logic, Inc.), 0x0606, 0xfa140000 / 5
USB Device: USB2.0 Hub, 0x05e3 (Genesys Logic, Inc.), 0x0606, 0xfa141000 / 9
USB Device: Apple Optical USB Mouse, apple_vendor_id, 0x0304, 0xfa141100 / 8
USB Device: CanoScan, 0x04a9 (Canon Inc.), 0x1904, 0xfa141200 / 6
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8215, 0xfa111000 / 7
USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0xfa120000 / 3
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfd100000 / 2
USB Device: HUAWEI Mobile, 0x12d1 (Huawei Technologies Co., Ltd.), 0x1001, 0xfd130000 / 5
USB Device: My Passport 070A, 0x1058 (Western Digital Technologies, Inc.), 0x070a, 0xfd140000 / 6
USB Device: Built-in iSight, apple_vendor_id, 0x8502, 0xfd110000 / 4
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd120000 / 3

Immediate suspects are the additions you added to you rsystem that installed kexts (drivers). From above,
com.intego.iokit.VBX6NKE            1
com.intego.iokit.BehavioralKext            1
com.intego.kext.VirusBarrier.AppBarrierKPI            10.6.8
com.intego.kext.VirusBarrierKPI            10.6.8
com.globaldelight.driver.BoomDevice            1.1
com.huawei.driver.HuaweiDataCardACMData            4.2
Two experiments you can try.
1. Boot in safe mode and see if you can shut down normally. All thise additions won't be running in safe mode so this test would indicate it is one of them causing the problem.
2. Uninstall all the intego VirusBarrier stuff. That's my first guess and the troublemaker.

[SOLVED]ALSA sequencer(/dev/snd/seq) missing = broken midi

I get this error when attempting to start qsynth (frontend for fluidsynth)
fluidsynth: warning: Failed to pin the sample data to RAM; swapping is possible.
fluidsynth: warning: Requested a period size of 1024, got 940 instead
ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory
fluidsynth: error: Error opening ALSA sequencer
It's right, /dev/snd/seq really does not exist on my system. I have the midi driver set to alsa_seq in the qsynth settings, and it's been working just fine up until now. I haven't tinkered with anything related to alsa, so I'm not sure how it disappeared. The only possible cause I can think of is that today I installed kernel26-lts and have been using it for a few hours. However, rebooting and switching to the standard kernel doesn't solve the problem, as /dev/snd/seq is still missing and I get an identical error message. Any ideas/suggestions/wild guesses?
Last edited by splittercode (2010-08-25 15:14:54)

Maybe you have blacklisted some module in rc.conf?
[karol@black ~]$ lsmod | grep -i seq
snd_seq_dummy 1071 0
snd_seq_oss 25016 0
snd_seq_midi_event 4488 1 snd_seq_oss
snd_seq 41656 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 4353 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_timer 15601 2 snd_seq,snd_pcm
snd 42602 11 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
[karol@black ~]$ l /dev/snd/seq
crw-rw---- 1 116, 3 2010-08-25 13:56 /dev/snd/seq

Start Up disk problem following kernel panic-mounts but not as a boot drive

I have a problem that I can't solve.
Dual processor G4 with 3 hard drive, all of which are bootable drives with 10.4.7 installed:
A- my primary boot drive - internal SCSI drive (Adaptec PowerDomain 2930U PCI card);
B - internal hard drive that came with the G4; and
C - external Firewire hard drive
Recently, I booted into my B drive and it locked up after it went into sleep mode. On reboot, I experienced a number of kernel panic messages, prompting me to restart my computer.
PROBLEM: Since that time, I have not been able to get my A drive to once again be the Startup Disk.
Diagnostic steps that I have performed:
i. I have run and re-run Disk Warrior from a bootable CD and the A drive as well as the other 2 hard drives mount and are "repaired" by DiskWarrior.
ii. TechTools Pro shows no hardware problems and whatever glitches it has found were repaired.
iii. Disk Utilities consistently returns "Volume passed verification."
iv. Zapped the PRAM
The A drive does mount and is accessible whenever either the B drive or the C drive is the bootable drive.
System Preferences/Startup Disk lists the A drive as a candidate whenever either the B drive or the C drive is the bootable drive. However, when the A drive is selected in System Preferences, on reboot, it doesn't become the boot drive.
I have tried to restart and hold the "C" key down so that I might possibly be able to select the boot drive from A, B or C. But the C key method doesn't produce the intended result, only reverting back to the boot drive in power prior to the reboot. That occurs whether the boot drive is B or C.
At that stage, rightfully or wrongfully, since the problem persisted whether the B or C drives were the startup disk I concluded that the problem could be hardware related and not software related.
On one of the reboots following the kernel panics, a Crash Report was produced - the verbiage
which is code related and so far above my knowledge and experience that it is incomprehensible to me. I can post it separately if helpful but it won't fit in this email message due to restrictions on length of messages.
I haven't had a kernel panic following any of the last 50+ restarts that have accompanied my attempted diagnostics.
Finally, I ran the Apple Hardware Test, version 1.2.6, that came with my G4. First, I removed all peripherals except the monitor, keyboard and mouse (plugged into the keyboard), the Adaptec SCSI card, and a 3rd party FW/USB2 PCI card (OrangeLink+). I ran the Extended Test and an error code was generated during the logic board test: Error Code fire/5/2
That gave me some hope. I next removed the 3rd party FW/USB2 PCI card (OrangeLink+) and re-ran the Apple Hardware Test and no error were reported. Both the logic board and memory passed. I ran the extended test twice, each time no error.
Ah, did that solve my problem? I rebooted and I still cannot get my A drive to be the Startup Disk.
Next, I ran the Rember software (a GUI app for Memtest) and the RAM checked out as fine.
At this stage I don't have a clue. The white towel is about to be waved.
If the problem is the Adaptec SCSI card, I don't know how to test it since it obviously has to be installed to enable drive A to mount.
Does anyone have any suggestions?

I am the original poster on this thread.
Turns out that the culprit behind all my boot problems was the battery on my 5 year old Quicksilver G4. Replaced the battery and all is back to normal.
FWIW, for any Quicksilver owners with SCSI cards, be aware that you can create boot problems for your SCSI drive by zapping your PRAM. As part of my diagnostics I did zap the PRAM but that turned out not to be a problem.
Adaptec's site does include a workaround should you have problems after zapping the PRAM. This specifically covers the PowerDomain 29160 SCSI card/2930U card, which I have.

I just updated my latest java but the update is causing problems with some externale devices. So i would like to uninstall this latest java update and get back the previous one. That should solve to problems with my external device

i just updated my latest java but the update is causing problems with some external devices. So i would like to uninstall this latest java update and get back the previous one. That should solve to problems with my external device.
Is this possible and how do i do that?
Anyone who responds thanks for that!
Juko
I am running
Hardware Overview:
Model Name:          Mac Pro
Model Identifier:          MacPro1,1
Processor Name:          Dual-Core Intel Xeon
Processor Speed:          2,66 GHz
Number of Processors:          2
Total Number of Cores:          4
L2 Cache (per Processor):          4 MB
Memory:          6 GB
Bus Speed:          1,33 GHz
Boot ROM Version:          MP11.005D.B00
SMC Version (system):          1.7f10
Serial Number (system):          CK7XXXXXXGP
Hardware UUID:          00000000-0000-1000-8000-0017F20F82F0
System Software Overview:
System Version:          Mac OS X 10.7.5 (11G63)
Kernel Version:          Darwin 11.4.2
Boot Volume:          Macintosh HD(2)
Boot Mode:          Normal
Computer Name:          Mac Pro van Juko de Vries
User Name:          Juko de Vries (jukodevries)
Secure Virtual Memory:          Enabled
64-bit Kernel and Extensions:          No
Time since boot:          11 days 20:39
Message was edited by Host

Java 6 you can't as Apple maintains it, and Java 7 you could if you uninstall it and Oracle provides the earlier version which they likely won't his last update fixed 37 remote exploits.
Java broken some software here and there, all you'll have to do is wait for a update from the other parties.

[SOLVED] Black screen after kernel boot after pacman -Syu

Hi, after full system upgrade with pacman -Syu, I get after the kernel boot black screen and everything is freezing. Then need to manually shut down the power button!
Normally when my system starts up after the kernel boot I get straight to the command line terminal login.
Can anybody help me how to fix this? Any clues? Any advice is welcome!
The problem is solved by downgrading to kernel 3.6.11.-1
Many thanks for the help from the people on #archlinux !
Last edited by OpenEye (2013-01-29 05:14:04)

jasonwryan wrote:
Please stop bumping your thread: use the edit button
https://wiki.archlinux.org/index.php/Fo … te#Bumping
What have you done about the errors being printed to your logs? You could start by fixing the network error and the broken udev rule...
Are you still using intiscripts? They are no longer supported: https://www.archlinux.org/news/end-of-i … s-support/
# edit: not a pacman issue, moving to Newbie Corner
I have searched for many hours and days for solutions on the internet and forums, tried some things, but with no results! I don't know how to fix the errors! Do you know how to fix that? I'm a total n00b! I'm doing my best as I can! Need help, thanks!

Use of EtreCheck to solve WiFi problem

I had a problem with my MacBook Air (original) running 10.7.5. Although the icon in the menubar showed a WiFi connection, I couldn't get any data from the network. Also Airport Utility couldn't see any of the four base stations on my network. I'll leave out the blind alleys and just say what I did to solve the problem.
I rebooted in Safe Mode, and found the problem went away. I ran EtreCheck and saved the results. I rebooted normally and found the WiFi problem was still there. I ran EtreCheck again and saved the results. On comparing the results, I found AirParrot kernel extensions were running in normal boot mode. I figured that might interfere with normal WiFi functioning.
I went to the AirParrot website and found a removal tool. I downloaded that and ran it. On rebooting, the problem was gone. EtreCheck confirmed that the AirParrot extensions were no longer present. Case closed.
I hope this will help someone use a similar method to solve her WiFi, or indeed, other problems. All thanks to the experts on this discussion group who have labored to solve people's problems and put EtreCheck together as a useful tool!
Self-help is key!

Hello najlaa1399,
It sounds like you don't have access to your rescue email and would like to reset your security questions. I found an article with information that should help:
If you decide not to provide a rescue email address, you can't reset your security questions and answers yourself later in the event you can't remember the answers to your questions. You'll need to contact iTunes Store support to have your questions and answers reset.
This is also true if you don't have access to the rescue email. You can find the full article here:
Rescue email address and how to reset Apple ID security questions
http://support.apple.com/kb/HT5312
Thank you for using Apple Support Communities.
Best,
Sheila M.

[Solved] ALSA with multiple applications

I know this issue has been dealt with many times before, but I can't figure out how to conform those fixes to my use case.
I rebuilt my computer today (old motherboard died). Sound worked fine out of box on the old onboard -- I didn't even have an /etc/asound.conf or ~/.asoundrc -- but on this motherboard I'm encountering the problem with ALSA only allowing one process to output sound.
lspci -vvv output:
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 01)
Subsystem: Biostar Microtech Int'l Corp Device 8228
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at fef40000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
I have a 5.1 setup on device 1 that works perfectly fine with whatever audio stream has managed to grab the device. I have looked at breb's asoundrc and changed "card 0" to "card 1" but noticed no change at all, and I don't know enough about the structure of the rc to know if there is anything else to change (although I did also replace all "hw:0" with "hw:1" to no avail). In order to get audio working at all I found a post instructing to put the following in my /etc/asound.conf:
pcm.!default {
type hw
card 1
ctl.!default {
type hw
card 1
I went back to the Arch Wiki and reread the notice: "For ALSA 1.0.9rc2 and higher on analog sound outputs you do not need to setup dmix. Dmix is enabled as default for soundcards which do not support hardware mixing." This is probably what made my last install run without hitches, I am guessing. It then says that if you are still having issues with mixing, to manually add dmix to your asoundrc. So I did that, and my .asoundrc simply looks like:
pcm.dsp {
type plug
slave.pcm "dmix"
I don't know what to do at this point. The only thought I have is that maybe the dmix only mixes to card 0 (which is my disabled HDMI output) and not card 1 (which is my analog out).
aplay -l output (like I said, I have HDMI output disabled in BIOS. After I post this I can reboot to re-enable it just in case it makes a difference, but by all means if it does then there has to be some sort of issue there with how either dmix works or with how this sound card deals with its mixing or something).
**** List of PLAYBACK Hardware Devices ****
card 1: Generic [HD-Audio Generic], device 0: ALC892 Analog [ALC892 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 1: Generic [HD-Audio Generic], device 1: ALC892 Digital [ALC892 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
Also, for instance, when I have mpd running, and try to open a video in VLC, I get this error:
Audio output failed:
The audio device "sysdefault:CARD=Generic" could not be used:
Device or resource busy.
and in mpv (I don't know how much of this is relevant. Probably only the bit after "Selected audio codec..." but here's the whole thing:
The round option must be an integer: 16/9
Error parsing option round (option parameter could not be parsed)
Option vf: Error while parsing expand parameter round (16/9)
Error parsing option vf (option parameter could not be parsed)
/etc/mpv/mpv.conf:24: setting option vf='expand=::::1:16/9:16' failed.
Option af-add: pan has only 2 params, so you can't give more than 2 unnamed params.
Error parsing option af-add (parameter is outside values allowed for option)
/etc/mpv/mpv.conf:58: setting option af-add='pan=6:1:0:.4:0:.6:2:0:1:0:.4:.6:2' failed.
Option af-add: pan has only 2 params, so you can't give more than 2 unnamed params.
Error parsing option af-add (parameter is outside values allowed for option)
/etc/mpv/mpv.conf:63: setting option af-add='pan=2:0.7:0:0:0.7:0.5:0:0:0.5:0.6:0.6:0:0' failed.
Playing: /media/Videos/Other/Samsung_Galaxy_Note_3_4K_Video_sample-XgalnuBlSNE.mp4
Detected file format: QuickTime / MOV (libavformat)
Clip info:
major_brand: mp42
minor_version: 0
compatible_brands: isommp42
creation_time: 2013-09-30 13:12:57
[stream] Video (+) --vid=1 (*) (h264)
[stream] Audio (+) --aid=1 --alang=und (*) (aac)
Selected video codec: H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 [lavc:h264]
Selected audio codec: AAC (Advanced Audio Coding) [lavc:aac]
[ao/alsa] Playback open error: Device or resource busy
[ao] Failed to initialize audio driver 'alsa'
[ao/oss] Can't open audio device /dev/dsp: No such file or directory
[ao] Failed to initialize audio driver 'oss'
Could not open/initialize audio device -> no sound.
Audio: no audio
Audio: no audio
VO: [xv] 3840x2160 => 3840x2160 420p
V: 00:00:05 / 00:00:38 (12%)
Last edited by Zopiac (2014-01-28 16:57:49)

Apparently I knew less than I thought I did about the HDMI out and device numbers. Here's the aplay -l output after re-enabling HDMI out:
**** List of PLAYBACK Hardware Devices ****
card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: Generic [HD-Audio Generic], device 0: ALC892 Analog [ALC892 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 2: Generic [HD-Audio Generic], device 1: ALC892 Digital [ALC892 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
I am currently getting nothing out of my speakers (lsof /dev/snd/* shows no processes using the soundcard even though mpd is "playing" (also ncmpcpp shows "Vol: n/a")). Even after I switched my /etc/asound.conf to "card 2" I get nothing. I am wondering if I needed what I already have in there after all. Maybe I added that and then rebooted, switching off the HDMI out as I did so. I'll check...
Edit: Nope. As I understand it, in order to have sound at all I need to have HDMI out disabled in BIOS and asound.conf set with the two clauses with "card 1", and I then encounter the singe process ALSA problem.
Last edited by Zopiac (2014-01-28 02:40:17)

Solved flicker problem with newer fglrx drivers

This has been annoying me since the move from 8.29 to 8.30: I have an integrated Xpress 200 on my laptop, and newer proprietary drivers caused the screen to flicker. This has caused me to stick with the older drivers, which restricted upgrades to X.org and the kernel. I was misled by some posts on the Internet to believe that this was the result of using custom modelines.
I have finally solved the problem yesterday. I am posting my findings in case anyone else has been suffering from the same behaviour.
The newer drivers come with an ACPI script, installed under /etc/acpi. The script is invoked every minute and inspects the current power status (i.e., A/C or battery). It then invokes
aticonfig --set-powermode=[MODE]
to adjust the driver to the new settings. Each time this command is executed, it causes the screen to flicker.
Obviously, there is no need to run the script if the power mode has not changed since the last call. I have therefore modified the script to first check the current driver power mode, and execute the mode command only if a new setting is required.
I hope this helps someone.

I need my hand held a bit here...
this seems to be the problem I'm having, ie the ac/battery event being called too frequently, but have no idea how to edit the script. I'm on an asus w3n, will it help to replace apci with asus-laptop and apcid daemon...or just add those and leave acpi daemon?
apologies for my numbnut newbie-ness.

[SOLVED] ALSA problem in kernel 2.6.17.13-3

Similar Messages

Maybe you are looking for