Today I installed Mandrake 9.1 on my computer and im having problems getting my usb headset working with it (The headset is a Plantronic DSP-500). If I boot my computer with the headset blugged in, it freezes the computer up halfway through the linux boot up (It happens right after the usb drivers are loaded and I here the headset make a click noise then it all freezes). Ive tried a little bit of everything with no avail. Mandrake comes with drivers that support usb headsets (I forgot the name of it) and I tried updating those drivers. I also tried plugging in the headset after I loaded mandrake and it still locks up. Im thinking its not the driver for the headset and it might have more to do with the usb drivers. If I could get any help I would be very thatnkfull, if not then ill probly forget about linux all together and stick with xp pro (I realy want to give linux a good shot, thats why I came here).

My specs:

AMD 1.4 t-bird
768 mb pc2100 ram
onboard sound (Ac'97) - disabled
geforce 3 ti 200

these things sure do find their way down the forums fast :P

bump, I would realy like to get an answer on this. the driver ALSA should work with it and mandrake supports it.

Try this one out:
http://www.alsa-project.org/alsa-doc...dule=usb-audio

Start about halfway down, since you 'already' have the modules, just work on the 'Now insert the modules into the kernel.' part, and
the /etc/modules.conf file, eg
# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-usb-audio
# module options should go here
# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0
# card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss

Then run
modprobe snd-usb-audio;modprobe snd-pcm-oss;modprobe snd-mixer-oss;modprobe snd-seq-oss

Will all this work out of the box, probably not, but try it and see.
One of the abov might not work, but give it a shot.

Don't forget your .asoundrc file in the link above.

So far I have updated the alsa drivers and I did all that was mentioned by faheyd with no luck. I even tried a config file that was recommended under the usb generic setup webpage where you set it so it will load the device before playing it. I was thinking maybe it was freezing because the device was starting prematurely.

Any other ideas?

Ill try to give some more info on my headset which might help.
Here is the plantronics website.
http://www.plantronics.com/north_ame...eId=cat1430032

sooner or later I hope to get this thing working. Till then no americas army on linux . I have been tinkering with linux more and I think ill be dropping windows all together if I ever get help with this thing. Anyway, still looking for someone with an answer.

Oh btw, this headset works with knoppix. Maybe there is something there?

1. Boot without the Headset plugged in
2. Plug the headset in and
a. Post anything that has to usb and audio from your output of 'dmesg' command.
b. Post the relevent parts from your /var/log/messages file, anything having to do with usb and audio
3. Do you see the device in your Mandrake control panel anywhere?

The posts you give will help someone to 'help you'.

NOTE:
http://alsa.opensrc.org/index.php?page=usb-audio
Most important from link,
"One more note on configuring your kernel: there is an option for USB audio support in the USB section of the kernel config. You should _NOT_ enable it. It is intended for use with USB speakers."

ah faeyd I think we might be getting somewhere .
I booted without the headset on then plugged it in. The system froze again and I was forced to hard boot. I got all the info you want from the dmesg and my message logs did capture information regaurding this headset malfunctioning.

Ill tell you message log first since its shorter

--------------------------------------------------------------------------------
message log:
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------Oct 2 04:12:31 localhost kernel: hub.c: new USB --------------------------------------------------------------------------------device 00:07.3-1, assigned address 2
Oct 2 04:12:31 localhost kernel: usb-uhci.c: interrupt, status 2, fra--------------------------------------------------------------------------------me# 1103
Oct 2 04:12:36 localhost kernel: usb_control/bulk_msg: timeout
Oct 2 04:12:36 localhost kernel: usb-uhci.c: interrupt, status 3, frame# 2014
Oct 2 04:12:36 localhost kernel: input1: USB HID v1.00 Pointer [Plantronics Plantronics Headset] on usb2:2.3
Oct 2 04:16:20 localhost syslogd 1.4.1: restart.

--------------------------------------------------------------------------------
dmesg:
--------------------------------------------------------------------------------

usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 15:32:56 Mar 14 2003
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: USB UHCI at I/O 0xc800, IRQ 12
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: USB UHCI at I/O 0xcc00, IRQ 12
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
usbdevfs: remount parameter error
usb.c: registered new driver usblp
printer.c: v0.11: USB Printer Device Class driver
hub.c: new USB device 00:07.2-1, assigned address 2
printer.c: Disabling reads from problem bidirectional printer on usblp0
printer.c: usblp0: USB Unidirectional printer dev 2 if 0 alt 1 proto 2 vid 0x03F
0 pid 0x0304
hub.c: new USB device 00:07.2-2, assigned address 3
hub.c: USB hub found
hub.c: 4 ports detected
hub.c: new USB device 00:07.2-2.4, assigned address 4
usb.c: USB device 4 (vend/prod 0x45e/0x39) is not claimed by any active driver.
usb.c: registered new driver hiddev
usb.c: registered new driver hid
usb-uhci.c: interrupt, status 3, frame# 1106
input0: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb1:
4.0
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice
usb.c: registered new driver usb_mouse
usbmouse.c: v1.6:USB HID Boot Protocol mouse driver
spurious 8259A interrupt: IRQ7.
scsi0 : SCSI host adapter emulation for IDE ATAPI devices

Are you using an external USB hub? If so, please try plugging in the 'most' needed devices directly into your computer and see what happens. Leave off the printer, or any other device you don't need. Maybe you have the ps2 version of a mouse and can connect just the usb keyboard and then the usb headset?

I have a usb hub and until after I installed the alsa update did it seam like removing the hub made a difference. I disconnected everything and plugged my headset in and the system was able to find my headset. I didnt have a mouse and found it extremely difficult to use the gui interface without it so I plugged it back in. I had to reboot for the mouse to work. this time it all booted up with the mouse and headset plugged in.

The problem is now getting sound through my headset. Linux now recognizes my headset as a sound device but dosnt seam to be loading the module for it so im ganna try reinstalling the alsa driver, library, and utilities to see if I might have missed a step.

Ill let you know what I come up with.

Oh and btw, I got an email from plantronic regarding my headset. He said even though its not supported they have tried it with a few destros of linux and found that red hat and mandrake work with it. Red had can find it from the install which I was unable to accomplish so far. If all fails I can probly fall back to red hat 9.

Bump, anyone have more info about this?

bumpish, bah, anyone? this is a very popular headset and alot of people im sure are having the same trouble as me...

Me to. I'm using MDK 10.0 CE (Kernel 2.6.3)
Haven't tried very hard to get it working yet, but I will. Need to use with UT2004. You aren't alone.

Can anyone try this with redhat 9/8 ?

me too experiencing same problems with suse 9.1
i'll post any news...