LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 07-10-2010, 12:12 AM   #1
justwantin
Member
 
Registered: Aug 2003
Location: Melbourne, Australia
Distribution: Slackware, Slackware ARM, Salix and Porteus
Posts: 552

Rep: Reputation: 45
boot hangs when udev encounters webcam


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?
 
Old 07-10-2010, 03:51 AM   #2
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
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.
 
Old 07-10-2010, 04:35 AM   #3
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,407

Rep: Reputation: 829Reputation: 829Reputation: 829Reputation: 829Reputation: 829Reputation: 829Reputation: 829
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.
 
Old 07-10-2010, 06:03 AM   #4
justwantin
Member
 
Registered: Aug 2003
Location: Melbourne, Australia
Distribution: Slackware, Slackware ARM, Salix and Porteus
Posts: 552

Original Poster
Rep: Reputation: 45
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.
 
Old 07-11-2010, 03:02 PM   #5
justwantin
Member
 
Registered: Aug 2003
Location: Melbourne, Australia
Distribution: Slackware, Slackware ARM, Salix and Porteus
Posts: 552

Original Poster
Rep: Reputation: 45
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.
 
Old 07-11-2010, 03:24 PM   #6
stormtracknole
Member
 
Registered: Aug 2005
Location: The Big Easy
Distribution: Slackware, RHEL
Posts: 817

Rep: Reputation: 104Reputation: 104
Quote:
Originally Posted by justwantin View Post
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.
 
Old 07-11-2010, 03:44 PM   #7
justwantin
Member
 
Registered: Aug 2003
Location: Melbourne, Australia
Distribution: Slackware, Slackware ARM, Salix and Porteus
Posts: 552

Original Poster
Rep: Reputation: 45
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!
 
Old 07-11-2010, 03:50 PM   #8
stormtracknole
Member
 
Registered: Aug 2005
Location: The Big Easy
Distribution: Slackware, RHEL
Posts: 817

Rep: Reputation: 104Reputation: 104
Quote:
Originally Posted by justwantin View Post
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. :/
 
Old 07-11-2010, 04:02 PM   #9
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
Quote:
Originally Posted by stormtracknole View Post
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

Last edited by H_TeXMeX_H; 07-11-2010 at 04:08 PM.
 
Old 07-11-2010, 07:31 PM   #10
aus9
Guru
 
Registered: Oct 2003
Posts: 5,056

Rep: Reputation: Disabled
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
 
Old 07-11-2010, 08:50 PM   #11
justwantin
Member
 
Registered: Aug 2003
Location: Melbourne, Australia
Distribution: Slackware, Slackware ARM, Salix and Porteus
Posts: 552

Original Poster
Rep: Reputation: 45
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
 
Old 07-12-2010, 03:52 AM   #12
justwantin
Member
 
Registered: Aug 2003
Location: Melbourne, Australia
Distribution: Slackware, Slackware ARM, Salix and Porteus
Posts: 552

Original Poster
Rep: Reputation: 45
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!
 
Old 07-12-2010, 01:34 PM   #13
stormtracknole
Member
 
Registered: Aug 2005
Location: The Big Easy
Distribution: Slackware, RHEL
Posts: 817

Rep: Reputation: 104Reputation: 104
Quote:
Originally Posted by justwantin View Post
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.
 
Old 07-12-2010, 03:13 PM   #14
justwantin
Member
 
Registered: Aug 2003
Location: Melbourne, Australia
Distribution: Slackware, Slackware ARM, Salix and Porteus
Posts: 552

Original Poster
Rep: Reputation: 45
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?
 
Old 07-12-2010, 03:21 PM   #15
stormtracknole
Member
 
Registered: Aug 2005
Location: The Big Easy
Distribution: Slackware, RHEL
Posts: 817

Rep: Reputation: 104Reputation: 104
Quote:
Originally Posted by justwantin View Post
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.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
UDEV - SBLive(emu10k) - Mandriva hangs at UDEV during boot.....still! Grrr. peterlowrie Linux - Hardware 2 05-23-2010 06:37 PM
udev hangs up on boot ghost333 Mandriva 1 12-30-2008 07:42 AM
em2880-dvb hangs after udev on boot Bob Jones Linux - Hardware 2 09-18-2007 01:29 AM
FC6 - UDEV hangs at boot / X won't start wayno Fedora 1 06-02-2007 03:51 AM
udev hangs on bootup oasizfyre Linux - Newbie 2 08-09-2006 06:46 AM


All times are GMT -5. The time now is 03:02 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration