Cannot use "line in" of USB CM106 Like Sound Device on 32 bit debian testing.
Dear list, I have a problem that does NOT occur on 2 of my machines (a new 64 bit laptop with Debian testing, and a 64 bit desktop with Ubuntu 14.04) but DOES occur on my 32 bit laptop that also runs Debian testing. All machines are fairly clean, the 32 bit laptop is freshly installed yesterday. The problem occurs with an external USB audio device from Sweex, with a CM106 chip. (Bus 001 Device 003: ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like Sound Device) Outputting sound via headphones or speaker plugs work OK. Also, inputting via the microphone input works OK. BUT, inputting sound via "line in" does NOT work (on the 32 bit machine). The Sweex device has a "mic mute" switch and a blue led the which indicates the mic-mute-state. Now if I select "line in" (via pavucontrol or alsamixer) , then the blue "mic mute" LIGHT is turned on, and CANNOT be turned off with the "mic mute" SWITCH on the device. And there is no signal from the device. This does not occur on the other PC's. It is not very likely that it is a hardware problem, but what else could it be? Is there any test that I can perform? I really am at a loss. Hopefully someone can give me a pointer. Thanks in advance, Sietse PS. Although I hear from several sides that it is suppose to work I cannot find the CM106 device on this side. http://www.alsa-project.org/main/index.php/Matrix:Vendor-C-Media But that could easily be out of date or unmaintained -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54061f03.2010...@rug.nl
Re: firewire_ohci does not create devices in testing/jessie
On 03/23/2014 11:49 AM, Brian wrote: On Sun 23 Mar 2014 at 10:35:46 +0100, Sietse Achterop wrote: I am having trouble using my Sony camcorder with dvgrab. It is connected using a PCMCIA Firewire Notebook Adapter from Belkin. This is when using Testing/Jessie installed using the installer from March 16-th, so just a few days before the alfa release of the installer. The problem is that the /dev/fw? devices are not created. Why does that not happen, while the hardware seems to be recognised as shown by the logs, see below. Also, the Sony camcorder recognizes the DV-interface when firewire cable is connected. It all worked perfectly under debian wheezy. Is there a better way to debug this? I would install Wheezy, check the operation of the of the device, upgrade to Jessie and check again. Good advice. It worked on this notebook under wheezy a few months ago. But now using a live-cd of wheezy (7.4) it does not work anymore. Also, using the dualboot windows XP no device is recognized. So I assume a hardware failure. Thanks for the reply, Sietse -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/532edc1e.2070...@rug.nl
firewire_ohci does not create devices in testing/jessie
Hello list, I am having trouble using my Sony camcorder with dvgrab. It is connected using a PCMCIA Firewire Notebook Adapter from Belkin. This is when using Testing/Jessie installed using the installer from March 16-th, so just a few days before the alfa release of the installer. The problem is that the /dev/fw? devices are not created. Why does that not happen, while the hardware seems to be recognised as shown by the logs, see below. Also, the Sony camcorder recognizes the DV-interface when firewire cable is connected. It all worked perfectly under debian wheezy. Is there a better way to debug this? Thanks in advance, Sietse == uname -a: Linux Sietse-1 3.13-1-686-pae #1 SMP Debian 3.13.5-1 (2014-03-04) i686 GNU/Linux from lspci: 02:06.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller 02:06.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller 02:06.4 SD Host controller: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller 02:06.5 Communication controller: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Smart Card Controller 03:00.0 FireWire (IEEE 1394): Texas Instruments Device 0024 from lsmod: firewire_ohci 34856 0 firewire_core 51080 1 firewire_ohci crc_itu_t 12331 1 firewire_core from /var/log/kern Mar 23 07:54:58 Sietse-1 kernel: [ 10.741303] firewire_ohci :03:00.0: enabling device ( -> 0002) (but nothing about creating a device) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/532eaaf2.5060...@rug.nl
Re: Line-in of CM106 like sound device does not work
On 12/25/2013 03:20 PM, Robin wrote: As a start from a terminal run alsamixer, hit F6 to select device and check the line-in level. Thanks Ralf and Robin for the replies. I now somehow got it working properly, but I don't know what has changed. I first removed pulseaudio, but although I could control everything using the alsa mixer, there was no signal on line-in (an now also not on the mic-input). Then I reinstalled pulseaudio again, fiddled a bit with the controls and presto, everything works perfectly. I am perfectly sure that I tried the current control earlier. But never mind, it is working. Thanks again for the replies, Sietse -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52bc0a11.9010...@rug.nl
Re: Line-in of CM106 like sound device does not work
On 12/25/2013 12:30 PM, Sietse Achterop wrote: lsusb says: Bus 003 Device 004: ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like Sound Device This hardware seems OK, because under Windows it is working properly. The problem is that no signal is seen from the line-in input. In addition below some output of "pactl list". This all seems OK too. Sietse = Source #1 State: SUSPENDED Name: alsa_input.usb-0d8c_USB_Sound_Device-00-Device.analog-stereo Description: CM106 Like Sound Device Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 4 Mute: no Volume: 0: 83% 1: 83% 0: -4.99 dB 1: -4.99 dB balance 0.00 Base Volume: 65% -11.06 dB Monitor of Sink: n/a Latency: 0 usec, configured 0 usec Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY Properties: alsa.resolution_bits = "16" device.api = "alsa" device.class = "sound" alsa.class = "generic" alsa.subclass = "generic-mix" alsa.name = "USB Audio" alsa.id = "USB Audio" alsa.subdevice = "0" alsa.subdevice_name = "subdevice #0" alsa.device = "0" alsa.card = "1" alsa.card_name = "USB Sound Device" alsa.long_card_name = "USB Sound Device at usb-:00:14.0-3, full speed" alsa.driver_name = "snd_usb_audio" device.bus_path = "pci-:00:14.0-usb-0:3:1.0" sysfs.path = "/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/sound/card1" udev.id = "usb-0d8c_USB_Sound_Device-00-Device" device.bus = "usb" device.vendor.id = "0d8c" device.vendor.name = "C-Media Electronics, Inc." device.product.id = "0102" device.product.name = "CM106 Like Sound Device" device.serial = "0d8c_USB_Sound_Device" device.string = "front:1" device.buffering.buffer_size = "352800" device.buffering.fragment_size = "176400" device.access_mode = "mmap+timer" device.profile.name = "analog-stereo" device.profile.description = "Analog Stereo" device.description = "CM106 Like Sound Device Analog Stereo" alsa.mixer_name = "USB Mixer" alsa.components = "USB0d8c:0102" module-udev-detect.discovered = "1" device.icon_name = "audio-card-usb" Ports: analog-input-microphone: Microphone (priority: 8700) analog-input-linein: Line In (priority: 8100) Active Port: analog-input-linein Formats: pcm -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52bad54b.7040...@rug.nl
Line-in of CM106 like sound device does not work
Dear List, Using Wheezy, version 7.3, with the 3.11 kernel from wheezy-backports, I have an exteral USB sound device from Sweex, see http://www.sweex.com/nl/assortiment/sound-vision/sound-cards/sc016/ lsusb says: Bus 003 Device 004: ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like Sound Device This hardware seems OK, because under Windows it is working properly. The problem is that no signal is seen from the line-in input. The microphone input (and output) work ok. I can set the settings from System Settings->Sound. The microphone-led on the device shows that the setting is changed on the device. (I am using pulseaudio, so it can also use pavucontrol) The question of course is, why are signals on line-in not seen? What could wrong? Thanks in advance, Sietse -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52bac1f0.5040...@rug.nl
An initial automounting by kde very slow after each X/kde-session start.
Hello List, This problem occurs since a few months, and I'm struggling to solve it. The system is debian/lenny (kde/kdm) on a dual core Intel PC. Inserting a usbstick for the FIRST TIME after logging in via kdm results in a delay of about 10 minutes before the kde-mount-screen appears! Then everything works OK. All next inserts work normal. (I regrettably have to restart the X-server on each logout, so with each login the X-server is also reset. So maybe the 10 minute delay is triggered by the X-server reset. But how?) The devices are always directly created upon insertion (here /dev/sdb1), and pmount can be used directly. There never is any warning or error to be found. Here some debugging info from hald OUTPUT from hald from /var/log/daemon.log: == . Aug 19 13:13:44 wingtip84 hald[5386]: 13:13:44.224 [I] blockdev.c:1622: hald-probe-storage --only-check-for-media returned 0 (exit_type=0) Aug 19 13:22:39 wingtip84 hald[5386]: 13:22:39.186 [I] hald_dbus.c:5127: OK for method 'Mount' with signature 'ssas' on interface 'org.freedesktop.Hal.Device.Volume' for UDI '/org/freedesktop/Hal/devices/volume_uuid_76DE_0888' and execpath 'hal-storage-mount' . == Note the 10 minute delay between the hald-probe-storage and the "OK for method 'Mount'. OUTPUT from hald in nodeamon and verbose mode (different attempt): = ! full path is '/usr/lib/hal/hald-probe-volume', program_dir is '/usr/lib/hal' pid 5476: rc=0 signaled=0: /usr/lib/hal/hald-probe-volume Run started hald-probe-storage (1) (0) ! full path is '/usr/lib/hal/hald-probe-storage', program_dir is '/usr/lib/hal' woohoo pid 5485: rc=0 signaled=0: /usr/lib/hal/hald-probe-storage +++ +++ Run started hal-storage-mount (0) (1) ! full path is '/usr/lib/hal/hal-storage-mount', program_dir is '/usr/lib/hal' 5657: XYA attempting to get lock on /media/.hal-mtab-lock 5657: XYA got lock on /media/.hal-mtab-lock device = /dev/sdb1 invoked by uid = 502 invoked by system bus connection = :1.36 label '' uuid '76DE-0888' Looking at /etc/fstab entry '/dev/sda7' /etc/fstab: device /dev/sda7 -> /dev/sda7 === The ++' stands for the 10 minutes of silence And after that silence the screen appears. Can anyone point me in the right direction? Again note that there never is any warning or error to be found. How could the 10 minute delay be triggered? Is it an udev-rule problem? (at some point I had package dmsetup (devicemapper setup) installed and after fiddling with its udev-rules it seemed to work (once). Now dmsetup is not installed anymore) Thanks in advance. Sietse Achterop -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
