Wireless headset for Xbox 360

[MCP]

My daughter gave me a wireless headset that she acquired. I found that it is labeled for the xbox 360. She said it worked for her on her PC with XP.  I was wondering if it would work for me.  My install of PCLOS KDE is fully updated.

Any idea's?

MCP

[Just17]

yeah ......  plug it in and see

[MCP]

yeah ......  plug it in and see

I did just that. While the unit powered up, I got no response from PCLOS.

MCP

[Just17]

yeah ......  plug it in and see

I did just that. While the unit powered up, I got no response from PCLOS.

MCP

check the last few lines of this command after plugging it in

dmesg

for any info about it.

Also check the output of this command for mention of the device

lsusb


Copy and paste the relevant output of the two commands into your next post.

[MCP]

The base unit which plugs into usb is labeled "Microsoft Xbox 360 Wireless Receiver for Windows"  The headset has this on it's side:  FCC ID: C3KWH01 IC: 3048A-WH01

MCP

[MCP]

yeah ......  plug it in and see

I did just that. While the unit powered up, I got no response from PCLOS.

MCP

I got this:

usb 4-2: new full speed USB device using ohci_hcd and address 2
usb 4-2: New USB device found, idVendor=045e, idProduct=0719
usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 4-2: Product: Xbox 360 Wireless Receiver for Windows
usb 4-2: Manufacturer: ©Microsoft
usb 4-2: SerialNumber: FD58DF80
input: Xbox 360 Wireless Receiver as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.0/input/input7
input: Xbox 360 Wireless Receiver as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.2/input/input8
input: Xbox 360 Wireless Receiver as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.4/input/input9
input: Xbox 360 Wireless Receiver as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.6/input/input10
usbcore: registered new interface driver xpad
usb 4-2: USB disconnect, address 2
xpad: xpad_irq_in - usb_submit_urb failed with result -19
xpad: xpad_irq_in - usb_submit_urb failed with result -19
xpad: xpad_irq_in - usb_submit_urb failed with result -19
usb 4-2: new full speed USB device using ohci_hcd and address 3
usb 4-2: New USB device found, idVendor=045e, idProduct=0719
usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 4-2: Product: Xbox 360 Wireless Receiver for Windows
usb 4-2: Manufacturer: ©Microsoft
usb 4-2: SerialNumber: FD58DF80
input: Xbox 360 Wireless Receiver as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.0/input/input11
input: Xbox 360 Wireless Receiver as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.2/input/input12
input: Xbox 360 Wireless Receiver as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.4/input/input13
input: Xbox 360 Wireless Receiver as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.6/input/input14

and this:


check the last few lines of this command after plugging it in

dmesg

for any info about it.

Also check the output of this command for mention of the device

lsusb


Copy and paste the relevant output of the two commands into your next post.

I got this:

usb 4-2: new full speed USB device using ohci_hcd and address 2
usb 4-2: New USB device found, idVendor=045e, idProduct=0719
usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 4-2: Product: Xbox 360 Wireless Receiver for Windows
usb 4-2: Manufacturer: ©Microsoft
usb 4-2: SerialNumber: FD58DF80
input: Xbox 360 Wireless Receiver as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.0/input/input7
input: Xbox 360 Wireless Receiver as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.2/input/input8
input: Xbox 360 Wireless Receiver as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.4/input/input9
input: Xbox 360 Wireless Receiver as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.6/input/input10
usbcore: registered new interface driver xpad
usb 4-2: USB disconnect, address 2
xpad: xpad_irq_in - usb_submit_urb failed with result -19
xpad: xpad_irq_in - usb_submit_urb failed with result -19
xpad: xpad_irq_in - usb_submit_urb failed with result -19
usb 4-2: new full speed USB device using ohci_hcd and address 3
usb 4-2: New USB device found, idVendor=045e, idProduct=0719
usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 4-2: Product: Xbox 360 Wireless Receiver for Windows
usb 4-2: Manufacturer: ©Microsoft
usb 4-2: SerialNumber: FD58DF80
input: Xbox 360 Wireless Receiver as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.0/input/input11
input: Xbox 360 Wireless Receiver as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.2/input/input12
input: Xbox 360 Wireless Receiver as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.4/input/input13
input: Xbox 360 Wireless Receiver as /devices/pci0000:00/0000:00:12.1/usb4/4-2/4-2:1.6/input/input14

and this:

Bus 004 Device 003: ID 045e:0719 Microsoft Corp. Xbox 360 Wireless Adapter


MCP

[Just17]

The results from the above appear promising


Have you tried to get the earpiece to connect properly with the USB wireless unit?


Do you have PulseAudio installed on that PC?

[MCP]

The results from the above appear promising


Have you tried to get the earpiece to connect properly with the USB wireless unit?


Do you have PulseAudio installed on that PC?

When I installed my new ssd I opted not to install PulseAudio when I reinstalled PCLOS.  I turned on the earpiece but got no sound through it.  Do you think PulseAudio is needed?

MCP

[Just17]

The results from the above appear promising


Have you tried to get the earpiece to connect properly with the USB wireless unit?


Do you have PulseAudio installed on that PC?

When I installed my new ssd I opted not to install PulseAudio when I reinstalled PCLOS.  I turned on the earpiece but got no sound through it.  Do you think PulseAudio is needed?

MCP

Not so much needed, as it might be a help ....  if you decide to install and enable it, please be sure to install pavucontrol also.

[MCP]

The results from the above appear promising


Have you tried to get the earpiece to connect properly with the USB wireless unit?


Do you have PulseAudio installed on that PC?

When I installed my new ssd I opted not to install PulseAudio when I reinstalled PCLOS.  I turned on the earpiece but got no sound through it.  Do you think PulseAudio is needed?

MCP

Not so much needed, as it might be a help ....  if you decide to install and enable it, please be sure to install pavucontrol also.

I'm not sure I want to go that route for this device.  I had some problems the last time I installed PulseAudio.  Of course I didn't have an install guide either. Has one been compiled that would make the transition easier.  And what are the advantages outside of using this one device?

MCP

[Just17]

The results from the above appear promising


Have you tried to get the earpiece to connect properly with the USB wireless unit?


Do you have PulseAudio installed on that PC?

When I installed my new ssd I opted not to install PulseAudio when I reinstalled PCLOS.  I turned on the earpiece but got no sound through it.  Do you think PulseAudio is needed?

MCP

Not so much needed, as it might be a help ....  if you decide to install and enable it, please be sure to install pavucontrol also.

I'm not sure I want to go that route for this device.  I had some problems the last time I installed PulseAudio.  Of course I didn't have an install guide either. Has one been compiled that would make the transition easier.  And what are the advantages outside of using this one device?

MCP

PulseAudio is not for everyone, but it is extremely useful when the user has more than one audio output device .....  such as in your situation where you have speakers, USB headset and possibly even HDMI on a graphis card. It allows the user - through a GUI - to determine to which device the sound goes.
That is probably its most useful function for most people who use it.

As for installing it ....

install

task-pulseaudio
pavucontrol

there are some extra pulseaudio modules if you want to use Bluetooth and other things ...  easily found using the search in Synaptic.

When installed, go to PCC - Hardware - Sound and enable PulseAudio.
Immediately reboot, and launch PulseAudio Volume Control from the Sound menu.

If your new device is recognised you can try playing some audio file in an application and directing it to the new device to see if it works.

Hope that helps a little.

If PulseAudio is not required, you can simply disable it in PCC again and reboot.

[MCP]

The results from the above appear promising


Have you tried to get the earpiece to connect properly with the USB wireless unit?


Do you have PulseAudio installed on that PC?

When I installed my new ssd I opted not to install PulseAudio when I reinstalled PCLOS.  I turned on the earpiece but got no sound through it.  Do you think PulseAudio is needed?

MCP

Not so much needed, as it might be a help ....  if you decide to install and enable it, please be sure to install pavucontrol also.

I'm not sure I want to go that route for this device.  I had some problems the last time I installed PulseAudio.  Of course I didn't have an install guide either. Has one been compiled that would make the transition easier.  And what are the advantages outside of using this one device?

MCP

PulseAudio is not for everyone, but it is extremely useful when the user has more than one audio output device .....  such as in your situation where you have speakers, USB headset and possibly even HDMI on a graphis card. It allows the user - through a GUI - to determine to which device the sound goes.
That is probably its most useful function for most people who use it.

As for installing it ....

install

task-pulseaudio
pavucontrol

there are some extra pulseaudio modules if you want to use Bluetooth and other things ...  easily found using the search in Synaptic.

When installed, go to PCC - Hardware - Sound and enable PulseAudio.
Immediately reboot, and launch PulseAudio Volume Control from the Sound menu.

If your new device is recognised you can try playing some audio file in an application and directing it to the new device to see if it works.

Hope that helps a little.

If PulseAudio is not required, you can simply disable it in PCC again and reboot.

You make it sound sooooooooooooo! simple!!!!!!!!!!  I may give it another shot.  Just beware I may be back with more questions.

Thanks,
MCP

[Just17]

No problem 

Once you do the install and reboot as described you should be ok.

[MCP]

No problem 

Once you do the install and reboot as described you should be ok.

O.K. you asked for it.  I installed the packages you suggested.  I enabled pulseaudio in pcc and rebooted. Each time I try to open "Pulse Audio Volume Control", I get "Connection failed: Cpnnection refused"

What now?

MCP

[Just17]

The first thing to try is to disable PulseAudio in PCC and reboot ......  and then when the desktop has settled, enable it again and reboot. Go through this without launching any other apps.
Then try PA Vol Control again.