Re: Logitech Webcam(USB) New Errors PostedFrom: Murali Parth (muralinux48_at_yahoo.com)Date: 07/05/04# Next message: Wolfgang Gill: "Re: Logitech Webcam(USB) New Errors Posted" * Previous message: Jeff Allison: "Re: Correct driver for VIA KM400 onboard graphics with FC2." * Next in thread: Wolfgang Gill: "Re: Logitech Webcam(USB) New Errors Posted" * Reply: Wolfgang Gill: "Re: Logitech Webcam(USB) New Errors Posted" * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Date: Sun, 4 Jul 2004 20:32:24 -0700 (PDT)To: Redhat FedoraFedora: Re: Logitech Webcam(USB) New Errors PostedHello List !Sorry to bother you again, but with fresher errors.Idownloaded the driver for Logitech QUICKCAM EXPRESSfrom the site : http://qce-ga.sourceforge.net.Thenafter extracting I ran the script "quickcam.sh" andthe following are the messages I got.It seems that theproblem lies with detection of the device.When I doan ls -l /dev/video0 and it displays the major,minornos. as 81 & 0 and /dev/video as 81 & 1.I removed thefile hwconf and ran "kudzu".It detects the USBcontroller as "desc: "VIA Technologies|VT82xxxxx UHCIUSB 1.1 Controller" .Now the result of quickcam.shfollows :'Now everything should be well and the drivercompiled.Let's then try actually loading the fresh driver andtestingif it works.Press Ctrl+C to quit, Enter to continue --->To load the driver, I need to know the root password.=== Entering root mode === I will now try to enable the SysRq key.If your computer crashes, you can try pressing: Alt + SysRq + S: Emergency Sync (writeeverything on hard disk) Alt + SysRq + U: Unmount all harddisks Alt + SysRq + B: Reboot system immediatelyPress Ctrl+C to quit, Enter to continue --->Now I finally will try to load the module.If you're unlucky, your computer might crash rightnow!!!!Consider long if you really want to continue.Press Ctrl+C to quit, Enter to continue --->You decided to do it, here we go...=== Leaving root mode ===The driver detected the following supported cameras:[!] No cameras detected.Try unloading and reloading the driver manually with rmmod quickcam; insmod ./quickcam.ko debug=-1and then checking whether there are any messagesindicatingproblems with command dmesgWARNING: I'll try to continue anyway, but thisprobably will fail.Press Ctrl+C to quit, Enter to continue --->I will be using , if there are more cameras I'll nottest them.Press Ctrl+C to quit, Enter to continue --->Testing if is correct.ls: : No such file or directoryls: : No such file or directory./quickcam.sh: line 547: [: too many argumentsls: : No such file or directoryls: : No such file or directory[!] major number is .Usually it should be 81, so there are problems ahead.WARNING: I'll try to continue anyway, but thisprobably will fail.Press Ctrl+C to quit, Enter to continue ---> Right now driver is loaded and ready to run.If you like, you can quit now and start using thecamera -you have good chances that it works, if no problemswere detected.If you have X Window System running and xawtvinstalled,I can now run it automatically for you.You will then also have opportunity to install thedriver permanently.Press Ctrl+C to quit, Enter to continue --->Launching xawtv (press q on xawtv window to quitit)... xawtv -noscale -noxv -c ""This is xawtv-3.92, running on Linux/i686(2.6.5-1.358)v4l-conf: option requires an argument -- cusage: v4l-conf [ options ] options: -q quiet -d X11 Display [:0.0] -c video device [/dev/video0] -b displays color depth is bpp -s shift display by bytes -f query frame buffer device for info -a set framebuffer address to (in hex, root only, successfulautodetect will overwrite this address) -1 force v4l API -2 force v4l2 APIv4l-conf had some trouble, trying to continue anywayv4l2: open : No such file or directoryv4l2: open : No such file or directoryv4l: open : No such file or directoryno video grabber device available Well, did it work, did you get a picture?If you did, you might now want to install the driverpermanently. Just proceed to do that...Press Ctrl+C to quit, Enter to continue --->Just an extra warning: the driver (quickcam.ko) andthe utility (qcset) will be now copied into systemdirectories. If you have already other versions,they will be overwritten. Verify by giving rootpassword.=== Entering root mode ===/usr/bin/install -c -D -m 644 quickcam.ko/lib/modules/2.6.5-1.358/misc/quickcam.ko/usr/bin/install -c -D -m 755 qcset/usr/local/bin/qcset/sbin/depmod -a=== Leaving root mode ===Hopefully the driver is now installed and can beloadedwith command modprobe quickcamas root. You can put this command into some startupscript to do it always automatically at boot.The exact location depends on distribution, and thisscript is yet too dumb to do this automatically.Press Ctrl+C to quit, Enter to continue --->Goodbye... 'Then I did the following :[root@muralinux qc-usb-0.6.0]# modprobe quickcam[root@muralinux qc-usb-0.6.0]# lsmodModule Size Used byquickcam 59060 0ohci_hcd 14748 0uhci_hcd 23708 0tuner 15380 0bttv 129292 0video_buf 14468 1 bttvi2c_algo_bit 7304 1 bttvv4l2_common 4864 1 bttvbtcx_risc 3592 1 bttvi2c_core 16388 3tuner,bttv,i2c_algo_bitvideodev 6656 2 quickcam,bttv---------------------------------------------Could anyone help me to provide clue to unravellingthis problem ? Thanks.Murali__________________________________________________Do You Yahoo!?Tired of spam? Yahoo! Mail has the best spam protection aroundhttp://mail.yahoo.com-- fedora-list mailing listfedora-list@redhat.comTo unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list# Next message: Wolfgang Gill: "Re: Logitech Webcam(USB) New Errors Posted" * Previous message: Jeff Allison: "Re: Correct driver for VIA KM400 onboard graphics with FC2." * Next in thread: Wolfgang Gill: "Re: Logitech Webcam(USB) New Errors Posted" * Reply: Wolfgang Gill: "Re: Logitech Webcam(USB) New Errors Posted" * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Relevant Pages * Re: [SLE] Missing 3D (was Compiz issues.) ... This is driver file location in above package ... post-uninstall script that will call tiny-nvidia-installer. ... Strange that it didn't offered to prepare existing kernel sources first. ... It can be that Smart did just what is programmed to do, install rpm, run ... (SuSE) * Re: vbs to configure printer to remote machine ... Description The printer driver is unknown. ... Win32 error code 1797 ... copy the files you want to install into this directory. ... Microsoft Windows Script Host Version 5.6 ... (microsoft.public.windowsxp.print_fax) * Re: Adding IP printer and install driver via script ... The driver has to be installed using the setup program from HP. ... an inf file in \Windows\inf you might be able to install it with the "Add ... I figured out how to creat the standard TCP/IP port but I'm ... > This is the error that I get when I run the script I created... ... (microsoft.public.windows.server.scripting) * Re: a script to add a new printer ... You install first the port and the driver, ... >> with the MS Windows 2003 Server Resource Kit from a script. ... (microsoft.public.scripting.wsh) * Re: apsfilter question/problem ... I don't have a fix to your apsfilter issue, but if you you are interested in another possible printing solution... ... that mentioned that driver, 10) PPA printer, so I chose that. ... the apsfilter setup script found it & didn't complain. ... Do I need to install another more complete version? ... (freebsd-questions) We are proud to have Web Hosting and Rack Housing from 9 Net Avenue Deutschland.(09)derkeiler.com * Security * UNIX * Linux * Coding * Usenet * Mailing-Lists * Newsgroups * About * Privacy * Search * ImprintPath: linux.derkeiler.com > Mailing-Lists > Fedora > 2004-07 Print as PDF RSS Feed
Blogged with the Flock Browser
No comments:
Post a Comment