When I go into Skype options to test video, video small screen and full screen works.

When I test sound sometimes it works and sometimes it locks everything up.

I have same setup on IBM a21m Thinkpad and everything works but I have serial mouse there.
There is no serial mouse port on Toshiba to try it there. I have laptop touchpad disabled
in BIOS.

I guess what I'm asking about is why is USB locking up and how to get ALSA to recognize
USB-Audio and USB mixer.

I found other posts that suggest to use pcm.usb to get ALSA to use USB if present and fall back
on default sound hardware if not present but I don't know how to do that with Slackware.

I can post additional information as necessary.

Thanks for reading. System details follow.

Toshiba Satellite M55-S1001 laptop
Logitech C310 USB 2.0 HD WebCam, found a few HCL that say it works fine with linux.

cat /etc/slackware-version:Slackware 13.1.0

uname -r:2.6.33.5

slackbuilds.org: 13.1 > Network > skype (2.1.0.81)

lsusb:Bus 001 Device 003: ID 046d:081b Logitech, Inc.

lsmod | grep video
uvcvideo 54940 0
videodev 32975 1 uvcvideo
v4l1_compat 13004 2 uvcvideo,videodev
i2c_core 15279 2 videodev,i2c_piix4
video 15937 0
thermal_sys 12086 3 thermal,video,processor
output 1444 1 video

lsmod | grep usb
snd_usb_audio 60657 0
snd_hwdep 5046 1 snd_usb_audio
snd_usb_lib 14741 1 snd_usb_audio
snd_rawmidi 15557 1 snd_usb_lib
snd_pcm 57736 4 snd_usb_audio,snd_pcm_oss,snd_atiixp,snd_ac97_codec
snd 43107 13 snd_usb_audio,snd_hwdep,snd_usb_lib,snd_rawmidi,
snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,
snd_mixer_oss,snd_atiixp,snd_ac97_codec,snd_pcm,snd_timer
usbhid 33016 0
hid 61027 1 usbhid

lsmod | grep sound
soundcore 4815 1 snd

system startup messages before log in prompt:
no state is present for card U0x46d0x81b
unknown hardware "USB-Audio" "USB Mixer" "USB046d:081b" "" ""
hardware is initialized using guess method
no state is present for card U0x46d0x81b

/var/log/messages after plugging in webcam:
Apr 7 23:25:46 xxxxxxx kernel: usb 1-1: new high speed USB device using ehci_hcd and address 3
Apr 7 23:25:46 xxxxxxx kernel: usb 1-1: New USB device found, idVendor=046d, idProduct=081b
Apr 7 23:25:46 xxxxxxx kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=2
Apr 7 23:25:46 xxxxxxx kernel: usb 1-1: SerialNumber: 5C17CFE0
Apr 7 23:25:46 xxxxxxx kernel: Linux video capture interface: v2.00
Apr 7 23:25:46 xxxxxxx kernel: uvcvideo: Found UVC 1.00 device <unnamed> (046d:081b)
Apr 7 23:25:46 xxxxxxx kernel: input: UVC Camera (046d:081b) as /devices/pci0000:00/0000:00:13.2/usb1/1-1/1-1:1.0/input/input6
Apr 7 23:25:46 xxxxxxx kernel: usbcore: registered new interface driver uvcvideo
Apr 7 23:25:46 xxxxxxx kernel: USB Video Class driver (v0.1.0)
Apr 7 23:25:50 xxxxxxx kernel: usbcore: registered new interface driver snd-usb-audio

Have you already verified that ALSA does not recognize the USB audio? Try checking the contents of /proc/asound/cards to see if your webcam is listed there as a USB device. If so, you should be able to access the mixer for it using `alsamixer -c X`, x being the number that your card was listed as.

As for why it is locking up, are you able to post any logs from during the crash? It may also help to run skype from the terminal emulator to see what kind of output it is producing before/during the crash.

Hi, forgot to mention system is current with latest updates.

cat /proc/asound/cards

0 [IXP ]: ATIIXP - ATI IXP
ATI IXP rev 80 with ALC250 at 0xc0007400, irq 17
1 [U0x46d0x81b ]: USB-Audio - USB Device 0x46d:0x81b
USB Device 0x46d:0x81b at usb-0000:00:13.2-1, high speed

/var/log/syslog after a crash, not sure what it means, repeats same info a few times, I guess until I rebooted.

Apr 8 11:11:50 xxxxxxx kernel: INFO: task X:2618 blocked for more than 120 seconds.
Apr 8 11:11:50 xxxxxxx kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 8 11:11:50 xxxxxxx kernel: f6673ee8 00003086 0000001b 0000001b e7ecfb80 f5874301 f6673eb0 f6fa5000
Apr 8 11:11:50 xxxxxxx kernel: e46d8366 000022be 00003286 f6673eb8 f66ef000 c2408040 c1a8c040 c1a8c040
Apr 8 11:11:50 xxxxxxx kernel: e4662140 000022be c1a872e4 00000000 e7fb5698 c1a8c040 c1a8c040 e7fb54f0
Apr 8 11:11:50 xxxxxxx kernel: Call Trace:
Apr 8 11:11:50 xxxxxxx kernel: [<c1059328>] ? prepare_to_wait+0x48/0x70
Apr 8 11:11:50 xxxxxxx kernel: [<c15cda1d>] usb_kill_urb+0x6d/0xa0
Apr 8 11:11:50 xxxxxxx kernel: [<c10590d0>] ? autoremove_wake_function+0x0/0x50
Apr 8 11:11:50 xxxxxxx kernel: [<f80362a6>] usbhid_close+0x76/0x80 [usbhid]
Apr 8 11:11:50 xxxxxxx kernel: [<f7c6b24b>] hidinput_close+0x1b/0x20 [hid]
Apr 8 11:11:50 xxxxxxx kernel: [<c1619cc0>] input_close_device+0x50/0x80
Apr 8 11:11:50 xxxxxxx kernel: [<f7fad1a8>] evdev_release+0x88/0xb0 [evdev]
Apr 8 11:11:50 xxxxxxx kernel: [<c10e12d4>] __fput+0xe4/0x1e0
Apr 8 11:11:50 xxxxxxx kernel: [<c10e13ed>] fput+0x1d/0x30
Apr 8 11:11:50 xxxxxxx kernel: [<c10ddc3c>] filp_close+0x4c/0x80
Apr 8 11:11:50 xxxxxxx kernel: [<c10ddccc>] sys_close+0x5c/0xa0
Apr 8 11:11:50 xxxxxxx kernel: [<c174b2d4>] syscall_call+0x7/0xb


I'll check on running skype from a terminal.