📄 install.html
字号:
<html><head><title>Installation notes</title><LINK REL="STYLESHEET" HREF="webcam.css" TYPE="text/css"></head><body><h1>Installation notes 8.*</h1><p>Since the PWC driver 8.0 and higher are in the main Linux kernel tree,you probably don't have to install anything on your system; just load thekernel module pwc.o and optionally pwcx.o and you should be up and running.Here's an extremely small HOWTO for upgrading your PWC in your currentkernel; it's not very specific for the very simple reason that there are waytoo many different Linux distributions and I cannot describe them all. So Iassume you know at least how to copy files, build a kernel, etc.</p><p><ul> <li>Locate your kernel sources; they are usually installed in <code>/usr/src/linux</code> or something like <code>/usr/src/linux-2.4.20</code>.</li> <li>Check if the full source is available; if there are only include files present, install the full source from CD or DVD. Better yet, download a vanilla kernel from kernel.org and built from that.</li> <li>Start up the kernel configurator, with 'make menuconfig', 'make xconfig' or any (graphical) tool that's available on your system.</li> <li>Make sure the "Philips Webcam driver" is enabled under the USB section; you may have to turn on "Video 4 Linux" first. Compile as module. Exit the configurator.</li> <li>Go to <code>drivers/usb/</code> (<code>drivers/usb/media/</code> for kernel 2.5/2.6). There you will find the existing PWC driver. Check the version number in pwc.h</li> <li>Copy the *.c and *.h files from the pwc-X.Y.tar.gz packaged over the existing ones.</li> <li>Go back to the root of the kernel sources, and do a 'make modules', followed by 'make modules_install' as root.</li></ul>If this all went well, you should now have a new PWC module available foryour system!</p> I will write a small HOWTO soon if you want/need to upgrade the PWC in yourkernel.</p><p>For module parameters, etc., see <ahref="philips.txt">>Documentation/usb/philips.txt</a> in the kernel sourcefor the latest information.</p><h2>RedHat 7.3/7.2</h2><p>For those who are less familiair with building kernels and loading modulesor are afraid to login as 'root', Curt Noll put up elaborate instrunctionson his site on how configure your RedHat system, including<b>fully automated hotplug</b> support. Please direct all questions regardingthese instructions to Curt Noll, and no, it's no use asking me or Curt forinstructions on other Linux distributions.</p><ul> <li><a href="http://www.isthe.com/chongo/tech/comp/pwc/rh7.3.html">RedHat 7.3</a></li> <li><a href="http://www.isthe.com/chongo/tech/comp/pwc/rh7.2.html">RedHat 7.2</a></li></ul></p><p><a href="install7">Installation notes for older versions of PWC</a></p><hr/><h3><a name="common">Common installation problems</a></h3><p>First, if you get these errors while loading the module:</p><p><pre>/lib/modules/2.4.3/kernel/drivers/usb/pwc.o: unresolved symbol kmalloc/lib/modules/2.4.3/kernel/drivers/usb/pwc.o: unresolved symbol kfree/lib/modules/2.4.3/kernel/drivers/usb/pwc.o: unresolved symbol printk</pre></p><p>you forgot to turn module versioning off in your current kernel (or yourLinux distribution has such a kernel installed for you). Recompile andinstall your kernel without this.</p><p>Second, I've received a number of error reports that unfortunately havenothing to do with my driver. The error messages look like this:</p><p><pre> usb.c: USB device not accepting new address=10 (error=-110) hub.c: USB new device connect on bus1/1, assigned device number 12 usb_control/bulk_msg: timeout usb.c: USB device not accepting new address=12 (error=-110) </pre></p><p>The key phrase in here is "device not accepting new address".When a USB device is plugged in, it gets assigned a unique bus number (theaddress) by the USB core; only after this succeeds the device is probed forits Vendor and Device ID and a driver is sought. But appearantly this fails,and the USB device does not accept the new address. There can be a number ofcauses:<ul> <li>obnoxious USB controllers (the most common problem) <li>power overcurrent condition (= too many devices attached) <li>poor cabling <li>faulty HUBs <li>etc. etc.</ul> </p><p>The long and short of it is: it has nothing to do with my driver, soplease don't send me bug reports when this happens. However, there are a fewthings you can try out:<ul> <li>Make sure all USB connectors are inserted properly; it should be seated firmly, and not wiggly.</li> <li>Plug the cam directly into the PC.</li> <li>Use powered USB hub.</li> <li>In case of a laptop, use the power supply with it. When using the battery, the voltage may drop.</li> <li>Try the latest kernel that is available, even the 2.4.0-test* and 2.5, when available.</li></ul></p><p>If this doesn't help, try the linux-usb-user mailinglist at <ahref="http://sourceforge.net/mail/?group_id=3581">SourceForge</a>. Try tosearch the archives first. When you must mail, make sure to include adescription of your hardware (motherboard, USB controller, kernel, etc).</p><h3><a name="order">Module load order</a></h3><p>This isn't strictly related to the Philips Webcam modules, but it'suseful information anyway. The best order in which to load your USB modulesis to load all 'device' drivers first (audio, pwc, acm, scanners, etc),and finally your USB controller (usb-uhci, usb-ohci).</p><p>If you do it the other way around, you'll get spammed crazy by theUSB-core with descriptor dumps because it couldn't find a driver for aparticular device. The order in which you load the device drivers doesn'tmatter.</p></body></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -