Ubuntu – Trying to install iSight webcam; following instructions but “module bcd_pci” not found – Google doesn’t help

19.04macbookwebcam

I'm a recently convert to Linux.

Running Ubuntu 19.04 on an older Macbook 4.1 or 4.4, white model, September 2008.

It has an iSight camera which is the only thing that didn't work out of the box.

I'm following the instructions at:

Everything seems to work fine till the "sudo modprobe -r bcd-pci".

Then I get a "modprobe: FATAL: Module bcd_pci not found".

Google doesn't help and I can't find an explanation on the forums as to why this is happening. I can't get back to using OSX too. This system is limited to 10.7 and things are starting to get outdated/having compatibility issues especially online.

I'm aware my question might be tremendously simple to solve, but I'm really at a loss.

Yeah, I should just buy a new computer and get on with it. Unfortunaly, can't spend that much right now.

I'd be very thankfull if anyone could chime in.

Best Answer

I did this a while ago and I did:

install the firmware tool

sudo apt-get install isight-firmware-tools

firmware file

file

Extract the firmware file somewhere and when the iSight-firmware-tool is done installing and it opens, go through the process and when it asks for a firmware file, give it the location of the file that you extracted before. Then if all goes well, reboot and boom, iSight.

Related Solutions

Laptop Webcam – Fix Laptop Webcam Not Detected in lsusb

Check if you have a switch button and certify that the camera is turned "on".

This switch could be on one of the function keys (accessible by using the Fn key).

Or as a separate button in a row, near the power button.

Ubuntu – Udev webcam rule read, but not respected

It looks like you have two problems.

The first is an ordering problem. Reading the kernel.org manpage on udev, it mentions:

All rules files are ... processed in lexical order

Meaning rules are processed in alphabetical order. The first rule that triggers for a device creates the device file. It looks like you've named your rule file jj-video.rules. Looking at the output you provided of udevadm --debug test, it shows that this file is parsed LAST of all the rule files on your system.

Try renaming your file 00-jj-video.rules. That should put it first in the udev rule list, and make it trigger before the other rules.

The second issue is with the rules themselves. The rules read that you're trying to create /dev/webcam2 when the Logitech QuickCam Pro 3000 is plugged in and when the kernel puts it on /dev/video2. From what you said, you don't want to match on the device name. Another problem is that you aren't always using hexadecimal notation in your ATTRS.

This rule should work for the Logitech QuickCam Pro 3000, based on the information you provided in the question:

SUBSYSTEM=="video4linux", ATTRS{idVendor}=="0x046d", ATTRS{idProduct}=="0x08b0", SYMLINK+="webcam2"

The following may work for the other webcam. I can't be sure, because you didn't provide full information on it:

SUBSYSTEM=="video4linux", SUBSYSTEMS=="usb", ATTRS{idVendor}=="0x1d6b", ATTRS{idProduct}=="0x0001", SYMLINK+="webcam1"

The most useful tutorial I've found on writing udev rules is http://www.reactivated.net/writing_udev_rules.html.