q-cusb-messenger is a forked driver from qc-usb-0.6.2 to support the Logitech Quickcam Messenger series. All other drivers are removed. Reproducible: Always Steps to Reproduce: 1. 2. 3.
inherit kernel-mod eutils DESCRIPTION="Logitech USB Quickcam Messenger Linux Driver Modules" HOMEPAGE="http://home.mag.cx/messenger/" SRC_URI="http://home.mag.cx/messenger/source/${P}.tar.gz" IUSE="" LICENSE="GPL-2" SLOT="0" KEYWORDS="~x86" DEPEND="virtual/linux-sources" src_compile() { emake KERNEL_DIR=${KERNEL_DIR} all || die } src_install() { insinto /lib/modules/${KV}/drivers/usb if kernel-mod_is_2_6_kernel; then doins quickcam.ko else doins quickcam.o fi dobin /usr/bin/qcset dodoc README* APPLICATIONS COPYING CREDITS TODO FAQ insinto /usr/share/doc/${PF} doins quickcam.sh debug.sh freeshm.sh } pkg_postinst() { if kernel-mod_is_2_4_kernel; then /usr/sbin/update-modules fi einfo "The driver is based on qc-usb-0.6.2, but I have removed the support" einfo "for all cameras except Quickcam Messenger in this source, since I" einfo "don't have any other cameras at home." einfo "The kernel module for quickcam.{o,ko} is installed for the" einfo "kernel linked by /usr/src/linux." }
There's a new version, 0.5. It works perfectly just by changing the ebuild version in the filename, to qc-usb-messenger-0.5.ebuild of course.
The original page seems to be dead, a mirror is here: http://www.ee.oulu.fi/~tuukkat/quickcam/messenger/ Anyway, version bumped to 0.8
Please add ebuilds as attachment, not inline in comments. Also update it as there seems to be a few changes needed (linux-sources is not a virtual anymore).
btw, KERNEL_DIR should be changed to LINUX_DIR, as noted in the newsest version of qc-usb in portage
Created attachment 58895 [details] qc-usb-messenger-0.8 ebuild
Created attachment 58896 [details, diff] memory handling patch for 0.8 ebuild Technically, this patch should not be applied to "older" kernels. But since I have no idea, how old kernel should be --- this patch is applied everytime.
a new ticket has been created which seems to include newer ebuild..... bug #84956 please confirm which one is the newest. thanks
(In reply to comment #8) > a new ticket has been created which seems to include newer ebuild..... bug > #84956 > > please confirm which one is the newest. > > thanks I just uploaded an ebuild for version 1.1 of qc-usb-messenger to the other bug. :)
*** Bug 84956 has been marked as a duplicate of this bug. ***
*** Bug 125629 has been marked as a duplicate of this bug. ***
I could maintain this. Just making it known I'm intrested in becoming a dev. See #125629 :)
Created attachment 82116 [details] qc-usb-messenger-1.1.ebuild - Simon80 Since 84956 has been marked a duplicate of this bug, I'm attaching the ebuild I put on that bug. It's for the latest version of qc-usb-messenger, and I've been using it since it was attached to the other bug, without experiencing problems.
As dumb as i may sound, what exactly do i need to do in order to patch the ebuild file(s) ?
Created attachment 83990 [details] qc-usb-messenger-1.2.ebuild by the way, I've had this reviewed in #gentoo-dev-help on Freenode by some of Gentoo developers. All good. :)
(In reply to comment #14) > As dumb as i may sound, what exactly do i need to do in order to patch the > ebuild file(s) ? > Let's say you have program named "example" and you want to change a file from it, copy "example" to "example.orig" so you've got 2 directories. Make the changes you want to "example" directory, and run: diff -ur example.orig example > my.patch Then you got my.patch that contains your changes. Now, you edit the ebuild and add line: epatch "${FILESDIR}"/my.patch in src_unpack() of your ebuild. Copy "my.patch" to files/ directory of that ebuild. And run: ebuild write_your_ebuild_name_here digest And you are good to go.
great ebuild worked perfectly. I have a Logitech Quickcam Communicate works NUMBER ONE
(In reply to comment #14) > As dumb as i may sound, what exactly do i need to do in order to patch the > ebuild file(s) ? > It's not so hard once you've done it, you just need to define an overlay directory in your make.conf, and then you can start putting ebuilds into subdirectories in that directory. See 'http://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds'. I put my overlay in /etc/portage/overlay so that when I back up /etc it gets included in the backup.
tnx .. the 1.2 works great for me :)
Created attachment 87577 [details] qc-usb-messenger-1.2.ebuild (added missing blocking depend)
Hi guys. I'm having problems getting this to work on my amd64 system. The modules is loaded without error, and I can see the camera using lsmod, but I'm yet to have an application use it properly. For instance, xawtv returns this from -hwscan: ioctl: VIDIOC_QUERYCAP(driver="";card="";bus_info="";version=0.0.0;capabilities=0x0 []): Unknown error 515 /dev/video0: OK [ -device /dev/video0 ] type : v4l name : Logitech QuickCam USB flags: capture And when I try to view it: xawtv -d ot i /dev/video This is xawtv-3.94, running on Linux/x86_64 (2.6.15-gentoo-r5) xinerama 0: 1280x1024+0+0 xinerama 1: 1280x1024+1280+0 X Error of failed request: XF86DGANoDirectVideoMode Major opcode of failed request: 138 (XFree86-DGA) Minor opcode of failed request: 1 (XF86DGAGetVideoLL) Serial number of failed request: 69 Current serial number in output stream: 69 Any suggestions? Cheers, Darren
That might be an issue with your video settings and not with the driver. I'd suggest searching for XF86DGANoDirectVideoMode, etc. There are also other apps you can test the cam with, like ekiga and kopete.
(In reply to comment #20) > Created an attachment (id=87577) [edit] > qc-usb-messenger-1.2.ebuild (added missing blocking depend) > I'd also like to mention that my ebuild works with 1.2, you just have to rename the file to qc-usb-messenger-1.2.ebuild. It's very similar to Samuli's, except that I add a debug USE flag, and I pass on the CFLAGS to the makefile. I'm not sure if compiling a kernel module with the make.conf CFLAGS is desirable or not though, so someone feel free to let me know.
(In reply to comment #21) > Minor opcode of failed request: 1 (XF86DGAGetVideoLL) In your xorg.conf, are you loading "extmod"? Examples, Section "Module" # SubSection "extmod" # This loads extmod without DGA. # Option "omit xfree86-dga" # EndSubSection Load "extmod" # This loads extmod with DGA. EndSection - drac
(In reply to comment #23) > (In reply to comment #20) > > Created an attachment (id=87577) [edit] > > qc-usb-messenger-1.2.ebuild (added missing blocking depend) > I'd also like to mention that my ebuild works with 1.2, you just have to rename > the file to qc-usb-messenger-1.2.ebuild. It's very similar to Samuli's, except > that I add a debug USE flag, and I pass on the CFLAGS to the makefile. I'm not > sure if compiling a kernel module with the make.conf CFLAGS is desirable or not > though, so someone feel free to let me know. > There is no reason to strip out CFLAGS unless you get a real bugreport of it. WORKSFORME with all the optimizing. Anyhow, you are doing it wrong.. you should be using flag-o-matic.eclass with strip_flags and append_flags. I won't comment on the debugging thing, as I haven't looked into it.
Simon - kopete is my target application, but it hangs when I select the 'device' section, and I'm assuming its a problem with the driver being as I'm having trouble elsewhere (ie, xawtv). Just emerges ekiga and it doesnt appear to detect the camera either. Samuli - Yes I'm loading extmod.
(In reply to comment #26) > Simon - kopete is my target application, but it hangs when I select the > 'device' section, and I'm assuming its a problem with the driver being as I'm > having trouble elsewhere (ie, xawtv). See, http://bugs.gentoo.org/show_bug.cgi?id=134556. Also I've seen people complaining Kopete freezes in IRC (Freenode) with normal qc-usb driver. I've used this succesfully with "camorama" and "gqcam".
Thanks for the tip Samuli. gqcam gives me an picture, not the greatest fps mind (5-9fps), but an image none the less. I'll add my feedback to the kopete bug you linked me to, thanks again.
Small update fwiw. After rebooting, kopete still hangs when I got to the device section. If I start gqcam *first*, and the close it, kopete no longer freezes and gives me an image. Bug relating to the driver or application, do you think? Slow fps is evident in both apps.
Hmm, the slow fps seems to kick in when I give it some other input (move mouse/type keys).
(In reply to comment #25) > (In reply to comment #23) > > (In reply to comment #20) > > > Created an attachment (id=87577) [edit] > > > qc-usb-messenger-1.2.ebuild (added missing blocking depend) > > I'd also like to mention that my ebuild works with 1.2, you just have to rename > > the file to qc-usb-messenger-1.2.ebuild. It's very similar to Samuli's, except > > that I add a debug USE flag, and I pass on the CFLAGS to the makefile. I'm not > > sure if compiling a kernel module with the make.conf CFLAGS is desirable or not > > though, so someone feel free to let me know. > > > > There is no reason to strip out CFLAGS unless you get a real bugreport of it. > WORKSFORME with all the optimizing. > > Anyhow, you are doing it wrong.. you should be using flag-o-matic.eclass with > strip_flags and append_flags. > > I won't comment on the debugging thing, as I haven't looked into it. > My ebuild isn't intended to strip out the CFLAGS, it's intended to ensure that the module gets compiled with them rather than without. When I wrote it, which was a while ago, it looked like the makefile looks at USER_OPT instead of CFLAGS, which is why my compile block passes them in USER_OPT to make.
qc-usb-messenger-1.2.tar.gz is no longer available at http://home.mag.cx/messenger/source/ is it safe to just change the vaesion in ebuild name to download 1.3 ?
(In reply to comment #32) > qc-usb-messenger-1.2.tar.gz is no longer available at > http://home.mag.cx/messenger/source/ is it safe to just change the vaesion in > ebuild name to download 1.3 ? > Yes.
Created attachment 88531 [details] new version Version 1.3 Hope that the date will be not a problem... ;-)
drac put this in the sunrise overlay for you. http://gentoo-sunrise.org/cgi-bin/trac.cgi/browser/sunrise/media-video/qc-usb-messenger I am updateing the bug for him, because his permissions do not allow editing the whiteboard and keywords.
Created attachment 89542 [details] new version Version 1.3-r1 added the control for conflicts with media-video/qc-usb tnx to Stephan and Drac
Comment on attachment 89542 [details] new version Version 1.3-r1 Please use reviewed ebuild in, http://gentoo-sunrise.org/cgi-bin/trac.cgi/browser/sunrise/media-video/qc-usb-messenger/qc-usb-messenger-1.3.ebuild
(In reply to comment #37) > (From update of attachment 89542 [details] [edit]) > Please use reviewed ebuild in, > http://gentoo-sunrise.org/cgi-bin/trac.cgi/browser/sunrise/media-video/qc-usb-messenger/qc-usb-messenger-1.3.ebuild > could you explain why you deleted the ebuid I posted... it is the same as on your site... I did it only to avoit the need to loose parts/effort around the net without reason. This site is the place where to keep all the new ebuild!!! if you are to lazy to post it here, don't worry I will do it for you!
Created attachment 89604 [details] new version Version 1.3-r2
> could you explain why you deleted the ebuid I posted... it is the same as on > your site... I did it only to avoit the need to loose parts/effort around the > net without reason. This site is the place where to keep all the new ebuild!!! > if you are to lazy to post it here, don't worry I will do it for you! Sunrise is a project where Gentoo Developers review ebuilds committed by contributors (like myself) and users. Note, Keywords: InOverlay Status-whiteboard: [sunrise-overlay] Also, you posted your ebuild in wrong mimetype, application/octet-stream so it can't be easily viewed with a browser.
(In reply to comment #39) > Created an attachment (id=89604) [edit] > new version Version 1.3-r2 > You may want to read http://gentoo-sunrise.org and see #gentoo-sunrise in irc.freenode.net for more information.
(In reply to comment #41) > (In reply to comment #39) > > Created an attachment (id=89604) [edit] > > new version Version 1.3-r2 > > > > You may want to read http://gentoo-sunrise.org and see #gentoo-sunrise in > irc.freenode.net for more information. > I get this error when ebuild qc-usb-messenger-1.3-r2.ebuild digest: ebuild qc-usb-messenger-1.3-r2.ebuild digest /usr/local/portage/media-video/qc-usb-messenger/qc-usb-messenger-1.3-r2.ebuild: line 4: 5: command not found /usr/local/portage/media-video/qc-usb-messenger/qc-usb-messenger-1.3-r2.ebuild: : command not found /usr/local/portage/media-video/qc-usb-messenger/qc-usb-messenger-1.3-r2.ebuild: : command not found /usr/local/portage/media-video/qc-usb-messenger/qc-usb-messenger-1.3-r2.ebuild: : command not found /usr/local/portage/media-video/qc-usb-messenger/qc-usb-messenger-1.3-r2.ebuild: : command not found /usr/local/portage/media-video/qc-usb-messenger/qc-usb-messenger-1.3-r2.ebuild: : command not found /usr/local/portage/media-video/qc-usb-messenger/qc-usb-messenger-1.3-r2.ebuild: 'ine 22: syntax error near unexpected token `{ /usr/local/portage/media-video/qc-usb-messenger/qc-usb-messenger-1.3-r2.ebuild: 'ine 22: `pkg_setup() { !!! ERROR: media-video/qc-usb-messenger-1.3-r2 failed. Call stack: ebuild.sh, line 1447: Called die !!! error sourcing ebuild !!! If you need support, post the topmost build error, and the call stack if relevant. aux_get(): (0) Error in media-video/qc-usb-messenger-1.3-r2 ebuild. (1) Check for syntax error or corruption in the ebuild. (--debug) The 1.3 version compiles fine but it doesn't support my cam, I have a QuickCam Messenger with ID 046d:08da. I thought that maybe 1.3-r2 supports it emerge --info Portage 2.1-r1 (default-linux/x86/2006.0, gcc-3.4.6, glibc-2.3.6-r4, 2.6.17-beyond2.1 i686) ================================================================= System uname: 2.6.17-beyond2.1 i686 Intel(R) Pentium(R) D CPU 3.00GHz Gentoo Base System version 1.6.15 app-admin/eselect-compiler: [Not Present] dev-lang/python: 2.4.3-r1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r3 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=i686 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/lib/mozilla/defaults/pref /usr/share/X11/xkb /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-O2 -march=i686 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.du.se/pub/os/gentoo http://ftp.du.se/pub/os/gentoo http://ds.thn.htu.se/linux/gentoo " LINGUAS="en_US" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 X alsa apache2 apm avi berkdb bitmap-fonts cli crypt cups dlloader dri eds emboss encode esd foomaticdb fortran gdbm gif gnome gpm gstreamer gtk gtk2 imlib ipv6 isdnlog jpeg libg++ libwww mad mikmod motif mp3 mpeg ncurses nls nptl ogg opengl pam pcre pdflib perl png pppd python quicktime readline reflection sdl session spell spl ssl tcpd truetype truetype-fonts type1-fonts udev vorbis xml xmms xorg xv zlib elibc_glibc input_devices_keyboard input_devices_mouse input_devices_evdev kernel_linux linguas_en_US linguas_sv userland_GNU video_cards_fbdev video_cards_nvidia video_cards_vesa video_cards_vga" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS
(In reply to comment #42) Sorry guys, in my tired state I just saw that I've missed the link posted. Sorry
> The 1.3 version compiles fine but it doesn't support my cam, I have a QuickCam > Messenger with ID 046d:08da. I thought that maybe 1.3-r2 supports it I was having the same problem, but for a different reason. Ubuntu 6.06 ships the original quickcam driver, which supports other cameras, but not the messenger, and it was getting loaded instead of the newly compiled module for me. I was going to suggest that you try typing modinfo quickcam and making sure that it is the module file that you expect, but instead, in your case, you may want to try adding your device ID to the sources in qc-driver.c, and seeing if the driver is capable of supporting your camera. I have no idea if it's safe to do that, but I can tell you that your camera's ID isn't in the source right now, I checked.
Also, I forgot to add: it seems that the latest kernel sources from linus' git tree has some sort of quickcam module source, but it may not be the same codebase, and seems to only have one device ID, mine, instead of three, like qc-usb-messenger.
Created attachment 92875 [details] qc-usb-messenger-1.3.ebuild Seriously people, use this. It's been reviewed by developers, and is in http://gentoo-sunrise.org overlay. It works, and QA is allright. Don't mess with working clean ebuild.
If you really want a job, diff this and original qc-usb-0.6.4. Create a cleaned diff and post it upstream, Otherwise, don't waste your time.
Reporting success here on ~x86. Please add to portage...
Reporting another success with 1.3 and ACCEPT_KEYWORDS="~x86"
Report another success. Work great for me too. Ebuild seems to be fine, should definitely be added to portage.
Can't the ebuild be put into portage? Does it need a maintainer? Cause it seems to work fine and should definitely be in portage
There seems to be a problem with the download URL? Here, emerge can't connect to home.mag.cx where the tarball is supposed to get downloaded from. Inet search only listed this page as a source. So, is this tarball gone? (will try later, but a more reliable source for the file should be found in any case imo)
http://home.mag.cx/messenger/source/ Seems ok to me..
Hi all... does it compile on linux 2.6.18 for you? I'm having some problems :-( at the moment don't ask me all the data... I'm still googoling.... but it is just to see your feedbacks... Leo
I believe there's a quickcam driver in 2.6.18, perhaps you can try that one instead?
(In reply to comment #55) > I believe there's a quickcam driver in 2.6.18, perhaps you can try that one > instead? > THANKS FOR THE GREAT HINT !!! IT WORKS :-) the only thing I cannot understand is ... the code for the webcam is available only is activated the deprecated "Enable Video For Linux API 1 (DEPRECATED)" I find it strange to insert in the kernel in to a deprecated branch?!
Created attachment 100723 [details] qc-usb-messenger-1.4.ebuild New driver version 1.4 I just changed the version number. Seems to work fine with a 2.6.17-r4 kernel.
1.5 is out and download for 1.3 and 1.4 is broken. renaming the 1.4 ebuild to 1.5 works perfectly. quickcam [24.358928]: ----------LOADING QUICKCAM MODULE------------ quickcam [24.358936]: struct quickcam size: 4384 quickcam: QuickCam USB camera found (driver version QuickCam Messenger/Communicate USB 1.5 $Date: 2006/11/05 00:00:00 $) quickcam: Kernel:2.6.18-justbudget bus:2 class:FF subclass:FF vendor:046D product:08F5 quickcam [24.359688]: poisoning qc in qc_usb_init quickcam [24.378103]: E00A contains 08F5 quickcam: Sensor VV6450 detected input: Quickcam snapshot button as /class/input/input2 quickcam [24.383702]: Quickcam snapshot button registered on usb-0000:00:03.0-1/input0 quickcam: Registered device: /dev/video0 usbcore: registered new driver quickcam
Created attachment 101736 [details] qc-usb-messenger-1.5.ebuild Work like a charm for me too. Shouldn't this ebuild be add to the tree?
I was looking for qc-usb and found this bug, the ebuild is already in portage so I believe this should be closed.
(In reply to comment #60) > I was looking for qc-usb and found this bug, the ebuild is already in portage > so I believe this should be closed. > You are wrong. This is not in portage yet. qc-usb and qc-usb-messenger are not for same camera models, -messenger adds support for Communicate and Express Messenger cameras. Do not close this bug.
It is in sunrise, we do not call sunrise ebuilds "inPortage"
I've talked with Flameeyes about proxy maintaining this package and looks like it will be in Portage sooner than you expect.
(In reply to comment #62) > It is in sunrise, we do not call sunrise ebuilds "inPortage" > I'm sorry I didn't saw the sunrise indicator.
(In reply to comment #63) > I've talked with Flameeyes about proxy maintaining this package and looks like > it will be in Portage sooner than you expect. Yeah, only two years. A similar driver to it has gotten into the Linux kernel (2.6.18)and then into portage, and this package still isn't in.
Created attachment 103252 [details, diff] qc-usb-messenger-2.6.19.patch Patch for Linux 2.6.19 support.
Created attachment 103253 [details] qc-usb-messenger-1.5-r1.ebuild Ebuild using previous patch.
And you should use gentoo-sources-2.6.19-r1 to avoid Sandbox Violations with .astest* files. Or you can extract patch from http://dev.gentoo.org/~dsd/genpatches/tarballs/genpatches-2.6.19-2.base.tar.bz2 , filename is called 2900_astest-sandbox.patch and apply it yourself to vanilla-sources if you don't need gentoo-sources (I don't.)
Created attachment 103341 [details] qc-usb-messenger-1.5-r1.ebuild Conditionalize patch applying to avoid breakage on 2.6.18 or lower.
Committed to tree.
