boot hangs when udev encounters webcam

justwantin · 07-10-2010, 12:12 AM

I have just installed slack-13.1 on an acer aspire one netbook from a usb stick by booting the install kernel with noudev. I was able to do a complete install including lilo but upon rebooting my boot hangs when encountering my webcam.

I see enough info to note the id as 0c45:62c0. This is a microdia webcam which I may be able to do something about later but in the first instance I'd like to be able to boot my system. The bios is very basic and there is no way to disable devices.

Can anyone suggest another way to bypass loading the webcam modules at boot?

H_TeXMeX_H · 07-10-2010, 03:51 AM

You should blacklist the module in '/etc/modprobe.d/blacklist.conf', but if you're using the huge kernel, the driver may be built-in, in which case it won't work. You'll have to use the generic kernel + initrd.

Is it using the uvc drivers ? I don't think they come with the kernel, so it might be something else.

allend · 07-10-2010, 04:35 AM

Curious.
I have this device in my Acer eMachine 250.
Running '/sbin/lsusb' gives:

Quote:

Bus 001 Device 002: ID 0c45:62c0 Microdia Sonix USB 2.0 Camera

It is supported out of the box by the uvcvideo.ko kernel module.
I am running the 2.6.33.4-smp generic kernel with an initrd.

I do not understand this:

Quote:

..booting the install kernel with noudev.

On my machine, it uses v4l that is setup by /lib/udev/rules.d/60-persistent-v4l.rules, so you will need udev for this.

justwantin · 07-10-2010, 06:03 AM

Quote:

..booting the install kernel with noudev.

It hangs when udev is doing its thing so maybe without udev doing its thing, it won't hang, I don't know.

I do know that a webcam with a microdia chip was very problematic 2 years ago on another machine.

I don't need a webcam but running slack on this machine would be better than a tu .... so I ask.

justwantin · 07-11-2010, 03:02 PM

Quote:

It is supported out of the box by the uvcvideo.ko kernel module.

I had another chance to try booting this box and I can see now that the uvcvideo module is loaded and that the boot hangs after the lines:

Quote:

usbcore: registered new device interface driver uvcvideo
USB Video Class driver (v0.1.0)

The only other things listed after the line "Triggering udev events" and before the webcam are the ethernet and ACPI

After booting with the bootimg and running lspci I can see that my wireless is a BCM4312 802.11b/g. I have found some info on the net indicating that the 2.6.33 drivers may not work with this card although theres an Arch wiki on this chipset here http://wiki.archlinux.org/index.php/Broadcom_BCM4312 which may prove usefull if indeed it is the wireless module.

stormtracknole · 07-11-2010, 03:24 PM

Quote:

Originally Posted by justwantin

I had another chance to try booting this box and I can see now that the uvcvideo module is loaded and that the boot hangs after the lines:

The only other things listed after the line "Triggering udev events" and before the webcam are the ethernet and ACPI

After booting with the bootimg and running lspci I can see that my wireless is a BCM4312 802.11b/g. I have found some info on the net indicating that the 2.6.33 drivers may not work with this card although theres an Arch wiki on this chipset here http://wiki.archlinux.org/index.php/Broadcom_BCM4312 which may prove usefull if indeed it is the wireless module.

I had a similar problem with my HP Mini and that Broadcom chip. Try black listing the following modules to see if that helps:

Code:

blacklist ssb
blacklist b43
blacklist b43-pci-bridge

Give that a try to see if it helps.

justwantin · 07-11-2010, 03:44 PM

Thanks,

I was thinking along those lines. It'll be next on my list when I have the time.

I normally build my own boxes. Haven't purchased a computer off the shelf in a very long time, What a pain in the butt!

stormtracknole · 07-11-2010, 03:50 PM

Quote:

Originally Posted by justwantin

Thanks,

I was thinking along those lines. It'll be next on my list when I have the time.

I normally build my own boxes. Haven't purchased a computer off the shelf in a very long time, What a pain in the butt!

Yes, that was a pain to deal with. I wish I could build my own laptops. :/

H_TeXMeX_H · 07-11-2010, 04:02 PM

Quote:

Originally Posted by stormtracknole

Yes, that was a pain to deal with. I wish I could build my own laptops. :/

That's why I don't buy laptops anymore. I ordered a pandora, maybe it will be enough to fill this gap for me.

Supposedly there may be a way to stop modules from loading by passing boot options, I've never heard of this, and it may be distro-specific.

http://www.debian.org/releases/stabl...h05s02.html.en
http://kerneltrap.org/mailarchive/li...007/1/27/48498

aus9 · 07-11-2010, 07:31 PM

hi justwantin

its not clear to me, if you are using wireless to connect to net or not. Also if its wireless issue maybe you could post your lspci id for that pesky device?

if its now the wireless issue, maybe you could edit your first post to change the subject, when you get a chance please?

You may like to publish your exact make and model of your computer and maybe do a search for it and wireless?

BTW I am not a wireless expert, I came here as I have some webcam experience.

good luck

justwantin · 07-11-2010, 08:50 PM

I haven't connected to the net yet. I haven't been able to boot after install yet due to what I at first thought was udev failing on loding the web cam drivers but now thats not the problem and I'm thinking the next in line for udev would be the wireless and I'm just thinking it might be the driver stock driverfor the broadcom chipset not being quite right for my machine.

Can't do much more as I'm at work on a very thin client

justwantin · 07-12-2010, 03:52 AM

Quote:

blacklist ssb
blacklist b43
blacklist b43-pci-bridge

Yes, blacklisting those modules did the trick and I've got 13.1 up and running To be precise I had booted of the install usb using the huge.s kernel and it hung on b43-pci-bridge which was the first off the rank.

I'll have a look at the Broadcom wireless modules later and will probably set up eth0 for now.

Just for the record, this was an Acer Aspire One 751. It just went to sleep and don't want to wake up LOL!

stormtracknole · 07-12-2010, 01:34 PM

Quote:

Originally Posted by justwantin

Yes, blacklisting those modules did the trick and I've got 13.1 up and running To be precise I had booted of the install usb using the huge.s kernel and it hung on b43-pci-bridge which was the first off the rank.

I'll have a look at the Broadcom wireless modules later and will probably set up eth0 for now.

Just for the record, this was an Acer Aspire One 751. It just went to sleep and don't want to wake up LOL!

Excellent!! Now, in order to get the wireless working, you will need to install the proprietary driver. Here's the slackbuild link. Reboot after installing the driver. It works great with either wicd or NetworkManager.

justwantin · 07-12-2010, 03:13 PM

Thanks again!

did the slackbuilds up but il defer setting up wireless until I read up on it a bit. If I need a heads up I'll do it in a new thread.

How do I marke this thread solved?

stormtracknole · 07-12-2010, 03:21 PM

Quote:

Originally Posted by justwantin

Thanks again!

did the slackbuilds up but il defer setting up wireless until I read up on it a bit. If I need a heads up I'll do it in a new thread.

How do I marke this thread solved?

I don't have much experience setting up wireless through the command line. WICD sets all of that automatically. It's available on Slackware /extra.

There is a setting in the forum software that allows you to change the thread to SOLVED. I can't remember where it is though.