Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
Attached is a new ebuild for r5u870; a driver for various Ricoh webcams, commonly found on HP laptops. I've only tested it under amd64, and have marked it as such. Since this is a reasonably common webcam, maybe set it as ~x86 as well? Note, 'make install' for the package puts the module into /lib/modules/.../extra by default, I changed this to /usb for consistency (since thats what the qc-usb ebuild does...)
Created an attachment (id=117963) [details] media-video/r5u870-0.10.0 ebuild
Created an attachment (id=121527) [details] Updated r5u870 ebuild Removed a few redundant things
with this ebuild r5u870-0.10.0.tgz don't downloading from http://lsb.blogdns.net/
Created an attachment (id=138335) [details] New r5u870-0.10.0 ebuild Hi there! Try this new r5u870-0.10.0 ebuild. I've updated the source URL for the tgz file. It worked for me. Bye.
Created an attachment (id=138336) [details] New r5u870-0.10.0 ebuild Hi there! Try this new r5u870-0.10.0 ebuild. I've updated the source URL for the tgz file. It worked for me. Bye.
Unfortunately this did not work for my Vaio TZ11MN, but I have found a patched version of the driver at http://wiki.mediati.org/R5u870 which includes support for the webcam model (VGP-VCC7) shipped in the TZ11 series. Sources can be downloaded using subversion. I am attaching a r5u879-9999.ebuild which fetches sources using subversion.eclass, it works great for me.
Created an attachment (id=140841) [details] Ebuild which fetches from subversion repo, adds support for VGP-VCC7
Created an attachment (id=141094) [details] Ebuild which fetches from subversion repo, adds support for VGP-VCC7 Removes the CONFIG_VIDEO_BUF check to make the ebuild work with zen-sources. The check is not really needed because the component is selected automatically when CONFIG_VIDEO_VIVI is enabled.
Created an attachment (id=141096) [details] Updated ebuild for 0.10.2 Builds from the version of the driver available from http://wiki.mediati.org/R5u870 using the 0.10.2 tarball instead of fetching sources with Subversion. Maybe someone finds this one cleaner ;-)
Created an attachment (id=141716) [details] Ebuild for new 0.11.0 release I have updated my ebuild to version 0.11.0 of the driver. Enjoy!
Created an attachment (id=141719) [details] Patch for config in new (post 2.6.24) kernels, use with the 0.11.0 and 9999 ebuilds
Created an attachment (id=141721) [details] Updated svn-based ebuild
Why does this happen: make[1]: Entering directory `/usr/src/linux-2.6.24-rc1' Makefile:500: /usr/src/linux-2.6.24-rc1/arch/x86/Makefile: No such file or directory make[1]: *** No rule to make target `/usr/src/linux-2.6.24-rc1/arch/x86/Makefile'. Stop. make[1]: Leaving directory `/usr/src/linux-2.6.24-rc1' make: *** [all] Error 2 Thanks, Gene (In reply to comment #12) > Created an attachment (id=141721) [edit] [details] > Updated svn-based ebuild > (In reply to comment #9) > Created an attachment (id=141096) [edit] [details] > Updated ebuild for 0.10.2 > > Builds from the version of the driver available from > http://wiki.mediati.org/R5u870 using the 0.10.2 tarball instead of fetching > sources with Subversion. Maybe someone finds this one cleaner ;-) >
(In reply to comment #13) > Why does this happen: > > make[1]: Entering directory `/usr/src/linux-2.6.24-rc1' > Makefile:500: /usr/src/linux-2.6.24-rc1/arch/x86/Makefile: No such file or > directory > make[1]: *** No rule to make target > `/usr/src/linux-2.6.24-rc1/arch/x86/Makefile'. Stop. > make[1]: Leaving directory `/usr/src/linux-2.6.24-rc1' > make: *** [all] Error 2 I would bet that your kernel source tree is not configured. You will need to do at least "make modules_prepare" in the kernel source tree.
(In reply to comment #14) > (In reply to comment #13) > > Why does this happen: > > > > make[1]: Entering directory `/usr/src/linux-2.6.24-rc1' > > Makefile:500: /usr/src/linux-2.6.24-rc1/arch/x86/Makefile: No such file or > > directory > > make[1]: *** No rule to make target > > `/usr/src/linux-2.6.24-rc1/arch/x86/Makefile'. Stop. > > make[1]: Leaving directory `/usr/src/linux-2.6.24-rc1' > > make: *** [all] Error 2 > > I would bet that your kernel source tree is not configured. You will need to do > at least "make modules_prepare" in the kernel source tree. > > Did that. No change. Any other ideas? Thanks, Gene
(In reply to comment #15) > (In reply to comment #14) > > (In reply to comment #13) > > > Why does this happen: > > > > > > make[1]: Entering directory `/usr/src/linux-2.6.24-rc1' > > > Makefile:500: /usr/src/linux-2.6.24-rc1/arch/x86/Makefile: No such file or > > > directory > > > make[1]: *** No rule to make target > > > `/usr/src/linux-2.6.24-rc1/arch/x86/Makefile'. Stop. > > > make[1]: Leaving directory `/usr/src/linux-2.6.24-rc1' > > > make: *** [all] Error 2 > > > > I would bet that your kernel source tree is not configured. You will need to do > > at least "make modules_prepare" in the kernel source tree. > > > > Did that. No change. Any other ideas? As far as I can tell, the missing file is installed as a part of the kernel sources: # qfile /usr/src/linux-2.6.24-gentoo/arch/x86/Makefile sys-kernel/gentoo-sources (/usr/src/linux-2.6.24-gentoo/arch/x86/Makefile) I would re-emerge sys-kernel/gentoo-sources in order to get the file installed again. I hope that would help ;-)
Created an attachment (id=159454) [details] r5u870-0.11.1.ebuild Ebuild for 0.11.1 release
Hello, I use the r5u870-9999.ebuild since its publication and it works perfectly (in my opinion). What do you suggest me? Flavio
(In reply to comment #18) > Hello, > I use the r5u870-9999.ebuild since its publication and it works perfectly (in > my opinion). > What do you suggest me? It is okay to use it if you want to stay always up-to-date (and living on the edge, hehe). It is also working nice for me, and I will fix the -9999 ebuild if something changes upstream, but I cannot guarantee that it will always work. As a reminder, please remember not to reinstall repository-based packages too much frequently in order to avoid stressing upstream servers (e.g. once a week usually is okay).
(In reply to comment #19) > (In reply to comment #18) > > Hello, > > I use the r5u870-9999.ebuild since its publication and it works perfectly (in > > my opinion). > > What do you suggest me? > > It is okay to use it if you want to stay always up-to-date (and living on the > edge, hehe). It is also working nice for me, and I will fix the -9999 ebuild if > something changes upstream, but I cannot guarantee that it will always work. > > As a reminder, please remember not to reinstall repository-based packages too > much frequently in order to avoid stressing upstream servers (e.g. once a week > usually is okay). > Ok, thank you. So, I'll tell you that I never updated my driver. I left my 9999 driver at the first version I emerged. Anyway, thank you. Flavio
Is there any overlay for this ebuild ?
(In reply to comment #21) > Is there any overlay for this ebuild ? > I don't know. Have you got some problem installing the r5u870 package?
No no everything is ok i was just wandering if there was any overlay.Thank you
(In reply to comment #23) > No no everything is ok i was just wandering if there was any overlay.Thank you > I don't know if this ebuild is contained into an overlay, because I always used my local overlay. Regards Flavio
(In reply to comment #24) > I don't know if this ebuild is contained into an overlay, because I always used my local overlay. I maintain an overlay which contains updated ebuilds for this package, take a look at http://connectical.org/overlay Hope you find it useful :=
I used to use the connectical-contrib overlay but now i just cant get to sync at all... I saw that the urls were changed and i tried the new ones but it fails all the time. I also use my local overlays at the moment Ps. Thank you for the effort you put to maintain the ebuilds in the overlay.There should be a way to be able to contact you but i could not find to any in order inform you about problems ...
As i just compiled the r5u870 i remembered that with the 2.6.25 kernel the 0.11.1 fails while the svn-based compiles without a problem. I dont remember if i had a problem with the 2.6.24. Sorry for the double post
My webcam works very well with the r5u870-9999.ebuild driver. My webcam is: a 05ca:1830 Ricoh Co., Ltd . I am trying to use r5u870 for a similar webcam, but it doesn't work. The webcam is recognized by lsusb as: 05ca:183a Ricoh Co., Ltd Does anyone have his webcam working? It should be like the last one I mentioned. Thank you.
(In reply to comment #28) > My webcam works very well with the r5u870-9999.ebuild driver. My webcam is: a > 05ca:1830 Ricoh Co., Ltd . > > I am trying to use r5u870 for a similar webcam, but it doesn't work. The webcam > is recognized by lsusb as: > 05ca:183a Ricoh Co., Ltd > > Does anyone have his webcam working? It should be like the last one I > mentioned. It works now, with the last svn ebuild. By the way. I am trying to do such a module-rebuild rebuild but emerging r5u870-9999 I'm not able to download the sources. This is what I get: * The specific snippet of code: * ${ESVN_SWITCH_CMD} ${options} ${repo_uri} || die "${ESV N}: can't update ${wc_path} from ${repo_uri}"; * The die message: * subversion: can't update /usr/portage/distfiles/svn-src/r5u870/trunk from h ttp://svn.mediati.org/svn/r5u870/trunk How can I do now? Thanks, Flavio > > Thank you. >
(In reply to comment #29) > By the way. I am trying to do such a module-rebuild rebuild but emerging > r5u870-9999 I'm not able to download the sources. This is what I get: > > * The specific snippet of code: > * ${ESVN_SWITCH_CMD} ${options} ${repo_uri} || die > "${ESV N}: can't update ${wc_path} from ${repo_uri}"; > * The die message: > * subversion: can't update /usr/portage/distfiles/svn-src/r5u870/trunk from > h ttp://svn.mediati.org/svn/r5u870/trunk > > How can I do now? > > Thanks, > > Flavio It seems to work now. Maybe it was a temporary problem with the overlay.
Same problem with the 2.6.27 kernel: * ERROR: media-video/r5u870-9999 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 3205: Called subversion_src_unpack * environment, line 3454: Called subversion_fetch * environment, line 3421: Called die * The specific snippet of code: * ${ESVN_UPDATE_CMD} ${options} || die "${ESVN}: can't up date ${wc_path} from ${repo_uri}."; * The die message: * subversion: can't update /usr/portage/distfiles/svn-src/r5u870/trunk from h ttp://svn.mediati.org/svn/r5u870/trunk. * * If you need support, post the topmost build error, and the call stack if rele vant. * A complete build log is located at '/var/log/portage/media-video:r5u870-9999: 20081019-171645.log'. * The ebuild environment file is located at '/var/tmp/portage/media-video/r5u87 0-9999/temp/environment'. Somebody could emerge r5u870 also on the latest kernel version? Flavio
I know it's currently broken on 2.6.26 and higher kernel versions... I hope they will fix it as soon as possible. :(
I have this problem with 2.6.28 kernel * * ERROR: media-video/r5u870-0.11.1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3194: Called linux-mod_src_compile * environment, line 2457: Called die * The specific snippet of code: * eval "emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}"; * The die message: * Unable to emake HOSTCC=i686-pc-linux-gnu-gcc CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS= all * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/media-video/r5u870-0.11.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/media-video/r5u870-0.11.1/temp/environment'. * This ebuild is from an overlay: '/usr/local/portage/' * belendax
(In reply to comment #33) > I have this problem with 2.6.28 kernel > > * > * ERROR: media-video/r5u870-0.11.1 failed. > * Call stack: > * ebuild.sh, line 49: Called src_compile > * environment, line 3194: Called linux-mod_src_compile > * environment, line 2457: Called die > * The specific snippet of code: > * eval "emake HOSTCC="$(tc-getBUILD_CC)" > CROSS_COMPILE=${CHOST}- > LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} > ${BUILD_PARAMS} > ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" > CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} > ${BUILD_PARAMS} ${BUILD_TARGETS}"; > * The die message: > * Unable to emake HOSTCC=i686-pc-linux-gnu-gcc > CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS= all > * > * If you need support, post the topmost build error, and the call stack if > relevant. > * A complete build log is located at > '/var/tmp/portage/media-video/r5u870-0.11.1/temp/build.log'. > * The ebuild environment file is located at > '/var/tmp/portage/media-video/r5u870-0.11.1/temp/environment'. > * This ebuild is from an overlay: '/usr/local/portage/' > * > > belendax > r5u870 is currently broken on kernels >=2.6.26 !!! The driver development has be abandoned.
(In reply to comment #34) > r5u870 is currently broken on kernels >=2.6.26 !!! > The driver development has be abandoned. You are right. With kernels >=2.6.26 you can use the "uvcvideo" module instead, but the firmware still needs to be loaded to the webcam's volatile memory. You can use a tool called r5u870x (also by Alex Hixon) for that. I have an ebuild which installs a snapshot taken from the mercurial repository here: https://mine.connectical.com/repositories/entry/contrib/media-video/r5u87x/r5u87x-0_p20081121.ebuild Just in case someone wants to keep up with this, you can find the code here: http://bitbucket.org/ahixon/r5u87x/overview/ -- I do not have as much free spare time as I used to have :-(
(In reply to comment #35) Yes! That's right actually! :-) I tried to use uvcvideo driver, uploading the firmware each time, but it doesn't work to me. I don't know why. I should try to with a newer kernel.
(this is an automated message based on filtering criteria that matched this bug) 'EBUILD' is in the KEYWORDS which should mean that there is a ebuild attached to this bug. This bug is assigned to maintainer-wanted which means that it is not in the main tree. Heuristics show that no Gentoo developer has commented on your ebuild. Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accommodate you in a timely manner. There are simply too many new packages. Allow me to use this opportunity to introduce you to Gentoo Sunrise. The sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay. So, the sunrise team is suggesting that you look into this and submit your ebuild to the overlay where even *you* can commit to. =) Because this is a mass message, we are also asking you to be patient with us. We anticipate a large number of requests in a short time. Thanks, On behalf of the Gentoo Sunrise Team, Jeremy. [1]: http://www.gentoo.org/proj/en/sunrise/ [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq
Created an attachment (id=197463) [details] Ebuild that fetches r5u87x from mercurial repository After successfully installing r5u87x with the ebuild from Adrian Perez (thanks!), I felt that there should be an ebuild that fetches the sources from the project repository, here it is. As I'm not very familiar with hacking ebuilds, you are invited to review and improve this one. To get the webcam working you have to do the following after installing the package (and after every reboot): # cd /usr/lib/r5u87x # ./loader # modprobe -r uvcvideo # modprobe uvcvideo
Did anyone try to get the following webcam working? 05ca:1830 Ricoh Co., Ltd .
Created an attachment (id=197570) [details] Ebuild for 2.6.30 kernel http://www.palmix.org/r5u870-en.html Over here they have an updated driver for the 2.6.30 kernel. I created an ebuild with what has already been uploaded here that supports x86 and amd64. I already tested the drivers and they were working fine in skype. Feel free to check and correct the ebuild. Cheers, Christos
Great work, but I'm unable to get it compiled. This is the error which is reported: >>> Unpacking source... >>> Unpacking r5u870_k2.6.30_i386.tar.bz2 to /var/tmp/portage/media-video/r5u870-2.6.30/work /var/tmp/portage/media-video/r5u870-2.6.30/temp/environment: line 3282: cd: /var/tmp/portage/media-video/r5u870-2.6.30/work/r5u870-2.6.30: No such file or directory >>> Source unpacked in /var/tmp/portage/media-video/r5u870-2.6.30/work >>> Compiling source in /var/tmp/portage/media-video/r5u870-2.6.30/work ... /var/tmp/portage/media-video/r5u870-2.6.30/temp/environment: line 2520: cd: /var/tmp/portage/media-video/r5u870-2.6.30/work/r5u870-2.6.30: No such file or directory /var/tmp/portage/media-video/r5u870-2.6.30/temp/environment: line 2533: cd: /var/tmp/portage/media-video/r5u870-2.6.30/work/r5u870-2.6.30: No such file or directory ln: creating symbolic link `Module.symvers': File exists * Preparing r5u870 module make -j3 HOSTCC=i686-pc-linux-gnu-gcc CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS= all make: *** No rule to make target `all'. Stop. * * ERROR: media-video/r5u870-2.6.30 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3277: Called linux-mod_src_compile * environment, line 2539: Called die * The specific snippet of code: * eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" CROSS_COMPILE=${CHOST}- LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}"; * The die message: * Unable to emake HOSTCC=i686-pc-linux-gnu-gcc CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS= all * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/log/portage/media-video:r5u870-2.6.30:20090712-081710.log'. * The ebuild environment file is located at '/var/tmp/portage/media-video/r5u870-2.6.30/temp/environment'. * This ebuild is from an overlay named 'local-repo': '/usr/local/portage/' *
It has to do with the unpacking of the tar.bz2 which is not done properly for the realease they have for 2.6.30 kernel. I see 2 ways of sorting it out one is to provide a package file so you can get it compiled but i am sure that if I ask the guy he will be more than happy to help and provide a proper package so we dont have to do with option 1.
(In reply to comment #42) > It has to do with the unpacking of the tar.bz2 which is not done properly for > the realease they have for 2.6.30 kernel. I see 2 ways of sorting it out one is > to provide a package file so you can get it compiled but i am sure that if I > ask the guy he will be more than happy to help and provide a proper package so > we dont have to do with option 1. > So you mean we have only to wait for a new package?
Created an attachment (id=198270) [details] Updated Ebuild for 2.6.30 kernel I mean that i got to sort it out. It was my fault cause i repackaged the thing when i installed it here and then i totally forgot that i've done that. It should be working properly now. Let me know if you have any problems.
Thanks a lot! This is what I get now: * Checking for suitable kernel configuration options... [ ok ] >>> Unpacking source... >>> Unpacking r5u870_k2.6.30_i386.tar.bz2 to /var/tmp/portage/media-video/r5u870-2.6.30/work /var/tmp/portage/media-video/r5u870-2.6.30/temp/environment: line 3270: cd: /var/tmp/portage/media-video/r5u870-2.6.30/work/r5u870-2.6.30: No such file or directory >>> Source unpacked in /var/tmp/portage/media-video/r5u870-2.6.30/work >>> Compiling source in /var/tmp/portage/media-video/r5u870-2.6.30/work ... /var/tmp/portage/media-video/r5u870-2.6.30/temp/environment: line 2508: cd: /var/tmp/portage/media-video/r5u870-2.6.30/work/r5u870-2.6.30: No such file or directory /var/tmp/portage/media-video/r5u870-2.6.30/temp/environment: line 2521: cd: /var/tmp/portage/media-video/r5u870-2.6.30/work/r5u870-2.6.30: No such file or directory ln: creating symbolic link `Module.symvers': File exists * Preparing r5u870 module make -j3 HOSTCC=i686-pc-linux-gnu-gcc CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS= all make: *** No rule to make target `all'. Stop. * * ERROR: media-video/r5u870-2.6.30 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3265: Called linux-mod_src_compile * environment, line 2527: Called die * The specific snippet of code: * eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" CROSS_COMPILE=${CHOST}- LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}"; * The die message: * Unable to emake HOSTCC=i686-pc-linux-gnu-gcc CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS= all
I'm sorry!!! Ignore my last message.. I forgot to update the ebuild. Sorry for my inattention. (In reply to comment #45) > Thanks a lot! > > This is what I get now: > * Checking for suitable kernel configuration options... > [ ok ] > >>> Unpacking source... > >>> Unpacking r5u870_k2.6.30_i386.tar.bz2 to /var/tmp/portage/media-video/r5u870-2.6.30/work > /var/tmp/portage/media-video/r5u870-2.6.30/temp/environment: line 3270: cd: > /var/tmp/portage/media-video/r5u870-2.6.30/work/r5u870-2.6.30: No such file or > directory > >>> Source unpacked in /var/tmp/portage/media-video/r5u870-2.6.30/work > >>> Compiling source in /var/tmp/portage/media-video/r5u870-2.6.30/work ... > /var/tmp/portage/media-video/r5u870-2.6.30/temp/environment: line 2508: cd: > /var/tmp/portage/media-video/r5u870-2.6.30/work/r5u870-2.6.30: No such file or > directory > /var/tmp/portage/media-video/r5u870-2.6.30/temp/environment: line 2521: cd: > /var/tmp/portage/media-video/r5u870-2.6.30/work/r5u870-2.6.30: No such file or > directory > ln: creating symbolic link `Module.symvers': File exists > * Preparing r5u870 module > make -j3 HOSTCC=i686-pc-linux-gnu-gcc CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS= > all > make: *** No rule to make target `all'. Stop. > * > * ERROR: media-video/r5u870-2.6.30 failed. > * Call stack: > * ebuild.sh, line 49: Called src_compile > * environment, line 3265: Called linux-mod_src_compile > * environment, line 2527: Called die > * The specific snippet of code: > * eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" > CROSS_COMPILE=${CHOST}- > LDFLAGS=\"$(get_abi_LDFLAGS)\" > ${BUILD_FIXES} ${BUILD_PARAMS} > ${BUILD_TARGETS} " || die "Unable to > emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- > LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}"; > * The die message: > * Unable to emake HOSTCC=i686-pc-linux-gnu-gcc > CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS= all >
Yes!!! It perfectly works now! I could compile this package without any problem. Thanks a lot, Flavio
Created an attachment (id=198277) [details] Updated Ebuild for 2.6.30 kernel Awesome, Just a small update so the readme file is also installed properly.
Now I would like to use this driver. If I do modprobe r5u870 I get the following: FATAL: Error inserting r5u870 (/lib/modules/2.6.30-gentoo-r1/media/video/r5u870.ko): Unknown symbol in module, or unknown parameter (see dmesg) dmesg: usbcam: Unknown symbol videobuf_dma_free usbcam: Unknown symbol videobuf_queue_sg_init usbcam: Unknown symbol videobuf_dma_unmap usbcam: Unknown symbol videobuf_to_dma r5u870: Unknown symbol usbcam_ctrl_add r5u870: Unknown symbol usbcam_curframe_get r5u870: Unknown symbol usbcam_claim_interface r5u870: Unknown symbol usbcam_curframe_testpattern r5u870: Unknown symbol usbcam_urbstream_stop r5u870: Unknown symbol usbcam_urbstream_start r5u870: Unknown symbol usbcam_ctrl_add_tmpl r5u870: Unknown symbol usbcam_urbstream_cleanup r5u870: Unknown symbol usbcam_register_mod r5u870: Unknown symbol usbcam_curframe_abortall r5u870: Unknown symbol usbcam_curframe_complete_detail r5u870: Unknown symbol usbcam_unregister r5u870: Unknown symbol usbcam_urbstream_init r5u870: Unknown symbol usbcam_choose_altsetting r5u870: Unknown symbol usbcam_ctrl_alloc r5u870: Unknown symbol usbcam_urbstream_config_iso Do I need some other module built in in the kernel configuration?
Created an attachment (id=198297) [details] install-media-video_r5u870-2.6.30:0::local.out I can't install the r5u870-2.6.30.ebuild any idea what I'm missing?
(In reply to comment #50) > Created an attachment (id=198297) [edit] [details] > install-media-video_r5u870-2.6.30:0::local.out > > I can't install the r5u870-2.6.30.ebuild > > any idea what I'm missing? > What are the steps you did?
Created an attachment (id=198316) [details] Updated Ebuild for 2.6.30 kernel Flavio you have missing symbols you have not configured your kernel properly. You have to either apply this patch vivi-dmasg-config.patch(see attachements of the bug) to the kernel or edit the .config of your kernel and put VIDEOBUF_DMA_SG, VIDEOBUF_GEN and VIDEOBUF_VMALLOC I will re-enable the ewarn messages for the rest of the users that will meet this problem and also updated the ebuild again. The ebuild now has information about applying the patch as it should to have before.
(In reply to comment #50) > Created an attachment (id=198297) [edit] [details] > install-media-video_r5u870-2.6.30:0::local.out > > I can't install the r5u870-2.6.30.ebuild > > any idea what I'm missing? > I think that you dont have V4L enabled in your kernel configuration. Do what i said for Flavio and let us know
Wooow! God Bless you! Thank you so much. My webcam works again finally! It's incredible. Greetings.
Wow, this is the first time I got my webcam(05ca:183a Ricoh Co., Ltd Visual Communication Camera VGP-VCC7 [R5U870] ) working, thank you very much :) Instead of rebooting, I was doing a ususpend2disk, which was actually why my new kernel wasn't used or something like that... Here is a one-liner you may find usefull here: for opt in VIDEO_V4L1 VIDEO_V4L2 VIDEO_V4L1_COMPAT FW_LOADER VIDEO_VIVI V4L_USB_DRIVERS VIDEOBUF_DMA_SG VIDEOBUF_GEN VIDEOBUF_VMALLOC ; do zgrep $opt /proc/config.gz || echo "$opt not found" done Thanks again!
I tried without the deprecated V4L1: <*> Video For Linux [ ] Enable Video For Linux API 1 (DEPRECATED) [*] Enable Video For Linux API 1 compatible Layer (unloaded uvcvideo, r5u870 and usbcam modules, uninstalled r5u870, rebuilt and rebooted on the new kernel and the reinstalled r5u870(*) ) And it's working perfectly! * -> I had to edit the ebuild a bit: --- r5u870-2.6.30.ebuild.old 2009-07-17 21:50:43.585947785 +0200 +++ r5u870-2.6.30.ebuild 2009-07-17 21:51:29.304948296 +0200 @@ -16,7 +16,7 @@ IUSE="" S="${WORKDIR}/${PN}" MODULE_NAMES="r5u870(media/video:) usbcam/usbcam(media/video:)" -CONFIG_CHECK="VIDEO_V4L1 VIDEO_V4L2 VIDEO_V4L1_COMPAT FW_LOADER +CONFIG_CHECK="VIDEO_V4L2 VIDEO_V4L1_COMPAT FW_LOADER VIDEO_VIVI V4L_USB_DRIVERS" MODULESD_R5U870_DOCS="readme" BUILD_TARGETS="all" @@ -40,7 +40,7 @@ pkg_setup () { # ewarn "the supplied patch and rebuild your kernel, as follows:" # ewarn # ewarn " # cd /usr/src/linux" -# ewarn " # cat /usr/share/doc/${P}/vivi-dmasg-config.patch \| patch -p1" +# ewarn " # < /usr/share/doc/${P}/vivi-dmasg-config.patch \| patch -p1" # ewarn # ewarn "Alternatively, you can edit the .config file and make sure that" # ewarn "VIDEOBUF_DMA_SG, VIDEOBUF_GEN and VIDEOBUF_VMALLOC are set" will post, an updated ebuild in a second. | for opt in VIDEO_V4L1 VIDEO_V4L2 VIDEO_V4L1_COMPAT FW_LOADER VIDEO_VIVI V4L_USB_DRIVERS VIDEOBUF_DMA_SG VIDEOBUF_GEN VIDEOBUF_VMALLOC CONFIG_VIDEO_ALLOW_V4L1 ; do | zgrep "$opt=" /proc/config.gz || echo "$opt not found" | done | VIDEO_V4L1 not found | CONFIG_VIDEO_V4L2=y | CONFIG_VIDEO_V4L1_COMPAT=y | CONFIG_FW_LOADER=y | CONFIG_VIDEO_VIVI=y | CONFIG_V4L_USB_DRIVERS=y | CONFIG_VIDEOBUF_DMA_SG=y | CONFIG_VIDEOBUF_GEN=y | CONFIG_VIDEOBUF_VMALLOC=y | CONFIG_VIDEO_ALLOW_V4L1 not found
Created an attachment (id=198357) [details] r5u870-2.6.30.ebuild
I cant find CONFIG_VIDEOBUF_DMA_SG. CONFIG_VIDEO_V4L2=m CONFIG_VIDEO_V4L1_COMPAT=y CONFIG_FW_LOADER=y CONFIG_VIDEO_VIVI=m CONFIG_V4L_USB_DRIVERS=y CONFIG_VIDEOBUF_GEN=m CONFIG_VIDEOBUF_VMALLOC=m $ cat /usr/src/linux/.config | grep CONFIG_VIDEOBUF_DMA_SG # lsmod | grep video videobuf_vmalloc 7372 1 vivi videobuf_core 18188 2 vivi,videobuf_vmalloc videodev 38720 1 vivi v4l1_compat 16396 1 videodev v4l2_compat_ioctl32 11912 1 videodev # modprobe r5u870 FATAL: Error inserting r5u870 (/lib/modules/2.6.30-gentoo-r4/media/video/r5u870.ko): Unknown symbol in module, or unknown parameter (see dmesg) vivi-000: V4L2 device registered as /dev/video0 Video Technology Magazine Virtual Video Capture Board ver 0.6.0 successfully loaded. usbcam: Unknown symbol videobuf_dma_free usbcam: Unknown symbol videobuf_queue_sg_init usbcam: Unknown symbol videobuf_dma_unmap usbcam: Unknown symbol videobuf_to_dma r5u870: Unknown symbol usbcam_ctrl_add r5u870: Unknown symbol usbcam_curframe_get r5u870: Unknown symbol usbcam_claim_interface r5u870: Unknown symbol usbcam_curframe_testpattern r5u870: Unknown symbol usbcam_urbstream_stop r5u870: Unknown symbol usbcam_urbstream_start r5u870: Unknown symbol usbcam_ctrl_add_tmpl r5u870: Unknown symbol usbcam_urbstream_cleanup r5u870: Unknown symbol usbcam_register_mod r5u870: Unknown symbol usbcam_curframe_abortall r5u870: Unknown symbol usbcam_curframe_complete_detail r5u870: Unknown symbol usbcam_unregister r5u870: Unknown symbol usbcam_urbstream_init r5u870: Unknown symbol usbcam_choose_altsetting r5u870: Unknown symbol usbcam_ctrl_alloc r5u870: Unknown symbol usbcam_urbstream_config_iso I'm using linux-2.6.30-gentoo-r4, out of r5u870 compilation: >>> Installing (1 of 1) media-video/r5u870-2.6.30 * Removing media-video/r5u870-2.6.30 from moduledb. * Updating module dependencies for 2.6.30-gentoo-r4 ... WARNING: //lib/modules/2.6.30-gentoo-r4/media/video/usbcam.ko needs unknown symbol videobuf_dma_free WARNING: //lib/modules/2.6.30-gentoo-r4/media/video/usbcam.ko needs unknown symbol videobuf_queue_sg_init WARNING: //lib/modules/2.6.30-gentoo-r4/media/video/usbcam.ko needs unknown symbol videobuf_dma_unmap WARNING: //lib/modules/2.6.30-gentoo-r4/media/video/usbcam.ko needs unknown symbol videobuf_to_dma [ ok ] * Adding module to moduledb. >>> Auto-cleaning packages... What am i doing bad? Thanks.
Related with Comment #58 I do: # cd /usr/src/linux # make # make CONFIG_VIDEOBUF_DMA_SG=m # make install modules_install and now r5u870 compile without warnings and dmesg is error clear after load vivi and r5u870: # modprobe vivi # modprobe r5u870 # dmesg ... vivi-000: V4L2 device registered as /dev/video0 Video Technology Magazine Virtual Video Capture Board ver 0.6.0 successfully loaded. usbcam: registering driver r5u870 0.11.3 r5u870-0: Detected Sony VGP-VCC8 r5u870-0: registered as video1 usbcore: registered new interface driver r5u870 but camera do not work with kopete ¿? What continued doing I wrong? Thanks
(In reply to comment #59) > Related with Comment #58 > > I do: > # cd /usr/src/linux > # make > # make CONFIG_VIDEOBUF_DMA_SG=m > # make install modules_install > > and now r5u870 compile without warnings and dmesg is error clear after load > vivi and r5u870: > # modprobe vivi > # modprobe r5u870 > # dmesg > ... > vivi-000: V4L2 device registered as /dev/video0 > Video Technology Magazine Virtual Video Capture Board ver 0.6.0 successfully > loaded. > usbcam: registering driver r5u870 0.11.3 > r5u870-0: Detected Sony VGP-VCC8 > r5u870-0: registered as video1 > usbcore: registered new interface driver r5u870 > > but camera do not work with kopete ¿? What continued doing I wrong? Thanks > I'm having the same problem but im using genkernel.. I edited /etc/kernels/kernel-config-x86-2.6.30-gentoo-r5 added CONFIG_VIDEOBUF_DMA_SG=y genkernel all reboted and still get the usbcam symbol problem in my dmesg for videobuf_dma_unmap, videobuf_to_dma, videobuf_queue_sg_init whats the issue?
The problems that some of you guys have with kopete are not actually related to this ebuild so it should not be brought up here. If you check it, your webcam should work with other software as skype, amsn or just mplayer. Now regarding kopete since lot people have this problem, the way that kopete works is that it asks solid for available webcams and then solid asks the same thing to HAL. If hal does not recognise any webcam ithere will not be any available to kopete. I am providing an fdi policy for HAL that will allow proper recognition it so it can be used in kopete.Please dont turn this ebuild bug into a support thread. Remember that you should change the name of your webcam to yours by checking the lshal output (the name should be changed in the part after the string=" of the above line of the fdi file <match key="info.udi" string="/org/freedesktop/Hal/devices/usb_device_5ca_1834_noserial">).Make sure to choose the correct name of the r5u870 video cause there are two similar with one being for imaging. Place it over at /etc/hal/fdi/information/ and then restart HAL. This should get it going and i hope you find it helpful
Created an attachment (id=204422) [details] fdi policy for HAL to recognise r5u870 as webcam I forgot to mention that you will probably need the compatible video for linux layer and i am saying probably cause i have not tested what is going on with the deprecated
