Kernel 2.6.27-3 conflicts with "Logitech Audio Hub"

Still exists in Alpha 6

Still exists in Intrepid Alpha 6

Still exists in Intrepid Beta

I'm experiencing the exact same problem in Ubuntu 8.04 on my EEE with the following kernel:

[ oxyph: ~ ]$ uname -a
Linux eee 2.6.24-21-eeepc #1 SMP Thu Aug 7 22:18:05 MDT 2008 i686 GNU/Linux

---

Is a kernel recompile or distribution upgrade really the only way to solve this problem?

Bug report #252291 seems to indicate the bug still exists in newer kernels.

Distribution upgrade does not solve this problem, you need to recompile the kernel manually. And you seem to have commented on the wrong bug, Bug#252291 is the bug for the older kernel, this is the bug for the newer version.

Thanks for the update. I did post in the wrong report but I've subscribed to both this and the older one in hopes for updates on a fix. I am using a custom kernel for the EEE but it was not compiled by me. However it appears to have been compiled with the following flags enabled:

USB_EHCI_ROOT_HUB_TT
USB_EHCI_TT_NEWSCHED

I will attempt to compile without those flags and report back.

This is still a problem with current kernel of 2.6.27-9-generic.

Can I suggest/request that the title of this bug be updated to reflect it is not just affecting 2.6.27-3, but the whole 2.6.27-x branch.

http://ubuntuforums.org/showpost.php?p=6097365&postcount=12 has details also on this specific problem, showing the recommended fix of kernel compile with USB_EHCI_TT_NEWSCHED not set.

Can the standard ubuntu released kernel have this option unset?

Still a problem in Jaunty (Alpha 3). I'm sure I've heard this exact noise - much like an electronic machine gun - before, perhaps a much as 25 years ago, likely when I was putting together a sound system and the polarities were mismatched or speaker wires were crossed.

There seems to have been a recent update in Jaunty that self-corrects the frequency after a minute or so and the speakers then behave well. This from the log file:

user kernel: [ 33.853118] ADDRCONF(NETDEV_UP): wlan0: link is not ready
user pulseaudio[4072]: alsa-util.c: Device front:1 doesn't support 44100 Hz, changed to 48000 Hz.
user kernel: [ 78.341278] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
user pulseaudio[4072]: module-alsa-sink.c: Increasing wakeup watermark to 6.00 ms
user pulseaudio[4072]: module-alsa-sink.c: Increasing wakeup watermark to 12.00 ms

where 'user' is the machine name. I don't know what the fix was, but it ain't broke...

Thanks Christopher, that offers some great news for Jaunty.

It also means that for Intrepid we should be able to edit /etc/pulse/default.pa and comment out the line for module-hal-detect, and insert a line for setting the Hz rate. Thus ...

### Load audio drivers statically (it's probably better to not load
### these drivers manually, but instead use module-hal-detect --
### see below -- for doing this automatically)
#load-module module-alsa-sink
load-module module-alsa-sink device=front:1 rate=48000
#load-module module-alsa-source device=hw:1,0
#load-module module-oss device="/dev/dsp" sink_name=output source_name=input
#load-module module-oss-mmap device="/dev/dsp" sink_name=output source_name=input
#load-module module-null-sink
#load-module module-pipe-sink

### Automatically load driver modules depending on the hardware available
#.ifexists module-hal-detect.so
#load-module module-hal-detect
#.else
### Alternatively use the static hardware detection module (for systems that
### lack HAL support)
load-module module-detect
#.endif

Refer the bottom of http://en.wikibooks.org/wiki/Configuring_Sound_on_Linux/Pulse_Audio/Troubleshooting for the details/hint on setting the rate for front:1 (audiohub).

I tried it in Intrepid for me, as per the above config but still get the 'machine gun popping'. Perhaps others with Intrepid would like to try?

Or how is Jaunty Alpha-4 for you ... stable?

still broken. not fixed for me with alpha 4. I see the frequency change messages, but it does not take care of the problem. I still need to recompile kernel without those options to make it work.

This from my user.log, also in my syslog repeated over 100 times:

(computer name) pulseaudio[4069]: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the ALSA developers. We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail_update() returned 0.

I guess I should 'report this issue to the ALSA developers as it says.

Still an issue in Jaunty with kernel 2.6.28-11

http://www.alsa-project.org/db/?f=79461ba5be6c55970354ad34e99149a9c59efdab has my audio details for diagnosis, if helpful.

Confirmed.

Xorg thinks it's a keyboard:

(II) config/hal: Adding input device HOLTEK AudioHub Speaker
[ 5.526068] (**) HOLTEK AudioHub Speaker: always reports core events
[ 5.526081] (**) HOLTEK AudioHub Speaker: Device: "/dev/input/event5"
[ 5.526156] (II) HOLTEK AudioHub Speaker: Found keys
[ 5.526167] (II) HOLTEK AudioHub Speaker: Configuring as keyboard
[ 5.526191] (II) XINPUT: Adding extended input device "HOLTEK AudioHub Speaker" (type: KEYBOARD)
[ 5.526213] (**) Option "xkb_rules" "evdev"
[ 5.526229] (**) HOLTEK AudioHub Speaker: xkb_rules: "evdev"
[ 5.526238] (**) Option "xkb_model" "pc105"
[ 5.526252] (**) HOLTEK AudioHub Speaker: xkb_model: "pc105"
[ 5.526261] (**) Option "xkb_layout" "us"
[ 5.526274] (**) HOLTEK AudioHub Speaker: xkb_layout: "us"

Oddly enough, attaching the speakers into a powered USB hub, makes them work fine.

This is true for many different kernels versions that I've tested: 2.6.27-x and 2.6.28-x.

Hope this information helps in determining why this is an issue.

What powered USB hub do you use oxyph?
I have a Laser powered 7 port USB 2.0 hub[1], and still get the fast paced popping sound regardless of whether I plug the audio device into the hub, or directly into the laptop. Up to date kernel 2.6.28-11 on 9.04 beta x86_64

[1] = http://www.laserco.com.au/pc_acc/pc_acc/AO-USBMHV2P.htm

i'm a kubuntu user, using pulse audio to fix this is completely moot.

I am using the current build of 9.04. Same problem - when I boot up after signing in, I get the constant popping for about 10 seconds or so. MP3 files seem to play fine.

anish, thank you for reporting this and helping make Ubuntu better. Intrepid reached EOL on April 30, 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue on a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

Running smoothly in Precise and a few versions before. I'm about to upgrade my testing partition to 12.10, but I don't anticipate any further issues.

As far as I'm concerned, it's fixed.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]