Razer Megalodon Headset not recognized on hot plug

Bug #658915 reported by Christian Parent on 2010-10-12
This bug affects 11 people
Affects Status Importance Assigned to Milestone
pulseaudio (Ubuntu)

Bug Description

My Razer Megalodon Headset is only seen has an input device if I hot plug it in the USB port. When connected prior to booting the system, they are seen has input and output device (7.1, 5.1, 4.1, stereo). If after booting with them connected, I disconnect them I can at anytime Hot-Plug them if I did not reboot the system and they will still be properly recognized.

The Device ID is : 1532:000e

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.33
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
 /dev/snd/controlC2: christian 1615 F.... pulseaudio
 /dev/snd/controlC0: christian 1615 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
 Card hw:0 'Intel'/'HDA Intel at 0xf3500000 irq 48'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,1025028e,00100202 HDA:14f12c06,10250093,00100000'
   Controls : 19
   Simple ctrls : 10
 Card hw:2 'Headset'/'Logitech Logitech G35 Headset at usb-0000:00:1d.2-1, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB046d:0a15'
   Controls : 8
   Simple ctrls : 4
Date: Mon Oct 11 22:53:52 2010
HibernationDevice: RESUME=UUID=b093283a-e745-4cd8-a4d6-0935141b46c9
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: Gateway P-79
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=c9a79761-7eac-4094-ac78-4aa7b7ca1a4c ro quiet splash
RelatedPackageVersions: linux-firmware 1.38
SourcePackage: linux
dmi.bios.date: 06/08/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 79.03.00
dmi.board.name: Godzilla-N10
dmi.board.vendor: Gateway
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Gateway
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr79.03.00:bd06/08/2009:svnGateway:pnP-79:pvr0100:rvnGateway:rnGodzilla-N10:rvrRev:cvnGateway:ct10:cvrN/A:
dmi.product.name: P-79
dmi.product.version: 0100
dmi.sys.vendor: Gateway

Christian Parent (mobidoy) wrote :
Changed in linux (Ubuntu):
status: New → Confirmed
importance: Undecided → Low

While headset is plugged after boot and not fully recognized by the Sound preferences panel, ALSA seems happy with the card because it is available in /proc/asound/cards (as card 1) and loaded in /proc/asound/modules.

affects: linux (Ubuntu) → pulseaudio (Ubuntu)
Christian Parent (mobidoy) wrote :

New Laptop (Asus G73JW A1) New Ubuntu installation (10.10) same issue,

Note that Logitech G35 Heaset are seen without any problem and, they are the same kind.

Are you fully updated? We've updated a number of sound-related
packages since the release of Maverick.

Christian Parent (mobidoy) wrote :

Yes I am fully updated, I also had this issue under 10.04. Cant tell if it exist in previous version thought

Christian Parent (mobidoy) wrote :

And just to add, when I hot plug it, for it to work, I simply need to type:

sudo alsa force-reload

and it will be properly detected

Daniel T Chen (crimsun) wrote :

Can you attach dmesg output from differing runs (one from cold boot with device inserted, another hotplugged)?

Christian Parent (mobidoy) wrote :

Here they are.

My knowledge of device driver and initiation in Linux is at 0 at the moment but, I had an idea of what could be the problem. Could it be that there is something not set at the right time in the driver that would make the device not recognize when Hot plugged that is automatically done at boot ?

Like I said, I also own a Logitech G35 which is the same kind of headset (usb with it's own integrated sound card) which is working properly either at boot or hot plug.

Christian Parent (mobidoy) wrote :

Does not take 2 attachment at once so, here is the other.

raphi78 (trance202) wrote :

exactly the same here. On two different machines with the same distribution the same problems. Another thing I noticed was the sound playback crackle from time to time, if I disconnect and reconnect the Megalodon, sometimes after a few times it works with clean sound. The Firmware of the Megalodon is the newest from Razer available. Any Idea for this Problem or has anyone else this issue?

Paul Drain (pd) wrote :

Still occurs on 12.04LTS:

1) Detected as input-only when hot-plugged.
2) Detected as 4.1 Channel Audio when 'sudo alsa force-reload' was run.
3) Detected as 7.1 Channel Audio only when 'sudo alsa force-reload && sudo service pulseaudio reload' was run.

lsusb reports:

Bus 002 Device 004: ID 1532:000e Razer USA, Ltd

Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.

Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
And Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:

Please upgrade to the latest version and re-test.

Changed in pulseaudio (Ubuntu):
status: Confirmed → Incomplete
affects: pulseaudio (Arch Linux) → mir
no longer affects: mir
Launchpad Janitor (janitor) wrote :

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

Changed in pulseaudio (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.