From: jr4412 on 10 Jan 2010 05:21 On 9 Jan, 18:54, Jim Diamond <Jim.Diam...(a)nospam.AcadiaU.ca> wrote: > On 2010-01-08 at 16:43 AST, Bud <B...(a)bud.invalid> wrote: > > > On 2010-01-08, Tuxedo wrote: > >> My system doesn't have the command 'lsusb' but my USB cam device appears to > >> have the ID "USB Camera (046d:08d8)" as reported by the CamStream > >> application. The hardware works fine in Windows on the same machine. > > >> Will test another cam. > > >> Tuxedo > > You have to be root to use the command i.e. username]$lsusb > > Of course, this is not true. You should really try out such simple > things before spreading misinformation to the rest of the world. > > To use lsusb as a non-root user, you can > (1) put /sbin in your PATH, or > (2) call it with the explicit pathname > /sbin/lsusb > or > (3) cd to /sbin > cd /sbin > and then call it as ./lsusb > ./sbin > or > (4...) any number of other ways. > > Cheers. > Jim Jim, are you sure? on Slackware 12.0 executing '/sbin/lsusb' (or by what other method you fancy yields no output and an error return of 1 (ie. echo $?).
From: Tuxedo on 10 Jan 2010 08:50 microsys wrote: > Tuxedo wrote: > > microsys wrote: > > > > [...] > > > >> For Slack-12.2 these packages are available at SBO.. > >> > >> CImg-1.2.9 > >> mjpegtools-1.9.0 > >> wxGTK-2.8.9 > >> wxcam-1.0.3 > >> xvidcore-1.2.1 > > > > I just installed all above packages and the USB camera still does not > > work with camstream but the wxcam application does work! Thanks for > > listing these suggestions. > > > > For a package, eg. camstream or any other package where there are many > > prerequisites, what is a good way of finding out what already exist on a > > system? For example, camstream has a long list of requirements but I > > have no idea what packages or versions of packages are on the system > > already: > > http://repository.slacky.eu/slackware-12.2/multimedia/camstream/0.27/src/slack-required > > > > Is there a command to check and report versions of installed packages > > and libraries, defined by exact package name or wildcard? > > > > Thanks for any tips, > > Tuxedo > > > > [..] > There are a couple of ways of doing this.. Probably the best and easiest > is to use pkgtool. this will list everything installed as a slackpackage > and show you everything contained in the package and where it is > installed. Another method is to look in /var/log/packages where you will > find a listing of all slackware packages installed on the system. > > Keep in mind, you must either su to root or log in as root to use pkgtool. > If you attempt to use it as a user the command will not be found. > > > > Just a note here for informational purposes. > > >>My system doesn't have the command 'lsusb' but my USB cam device > >>appears to have the ID "USB Camera (046d:08d8)" as reported by the > >>CamStream application. The hardware works fine in Windows on the same > >>machine. > > In the previous response in this thread you posted the above information. > Notice the ID "USB Camera (064d:08d8)" shown in your posting corresponds > to the idVendor=046d in my dmesg listing. The idProduct I show is > different than yours most likely because, while the vendor is the same, > the model is different. Yours being the QuickCam notebook model where mine > is the Quickcam Zoom model. Thanks for the various tips and tricks - I'm sure my old Logitech cam will soon be fully Slackware enabled! Tuxedo
From: Tuxedo on 10 Jan 2010 17:12 jr4412 wrote: > Jim, are you sure? on Slackware 12.0 executing '/sbin/lsusb' (or by > what other method you fancy yields no output and an error return of 1 > (ie. echo $?). I have a fresh 12.2 install and executing /sbin/lsusb as a non-root user yields: tuxedo(a)q25:~$ /sbin/lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 046d:08d8 Logitech, Inc. QuickCam for Notebook Deluxe Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Tuxedo
From: Jim Diamond on 10 Jan 2010 19:56 On 2010-01-10 at 06:21 AST, jr4412 <jr4412(a)googlemail.com> wrote: > On 9 Jan, 18:54, Jim Diamond <Jim.Diam...(a)nospam.AcadiaU.ca> wrote: >> On 2010-01-08 at 16:43 AST, Bud <B...(a)bud.invalid> wrote: >> >>> You have to be root to use the command i.e. username]$lsusb >> >> Of course, this is not true. �You should really try out such simple >> things before spreading misinformation to the rest of the world. >> >> To use lsusb as a non-root user, you can >> (1) put /sbin in your PATH, or >> (2) call it with the explicit pathname >> � � � � /sbin/lsusb >> � � or >> (3) cd to /sbin >> � � � � cd /sbin >> � � and then call it as ./lsusb >> � � � � ./sbin >> � � or >> (4...) any number of other ways. >> >> Cheers. >> � � � � � � � � � � � � � � � � Jim > Jim, are you sure? on Slackware 12.0 executing '/sbin/lsusb' (or by > what other method you fancy yields no output and an error return of 1 > (ie. echo $?). Well, I don't have a Slackware 12.0 system lying around any more, but according to slackware.mirrors.tds.net:/pub/slackware/slackware-12.0/slackware/MANIFEST.bz2 package a/usbutils-0.72-i486-2.tgz contains /sbin/lsusb So if you don't have that package installed, Bad Things would happen. Mind you, if you are getting a status return of -1, as opposed to the shell whining "Command not found", then I'd look in the man page and see what it says. The Slack64 13.0 man page says If the specified device is not found, a non-zero exit code is returned. If you are calling /sbin/lsusb with no command-line args, that man page line is a bit vague. Hmmm... do you have something like none /proc/bus/usb usbfs devgid=83,devmode=664 0 0 in your /etc/fstab? If not, while the lsusb man page talks about /dev/bus/usb, perhaps without that line in /etc/fstab you don't get any files in /dev/bus/usb as well as not getting any entries in /proc/bus/usb. Hmmm... maybe not, I tried unmounting that and lsusb still worked. (If you don't have that mounted and want to try it without editing fstab and rebooting, run the command mount /proc/bus/usb /proc/bus/usb -t usbfs -o rw,devgid=83,devmode=664 as root.) Ummm... by any chance are you using really, really old hardware with no USB hubs? What output do you get if you say ls -l /dev/bus/sub (This works for me as an ordinary user, but you might want to try it as root on your system.) I'd be interested in knowing what happens on your system. Cheers. Jim
From: Jim Diamond on 10 Jan 2010 20:06
On 2010-01-10 at 03:32 AST, Bud <Bud(a)bud.invalid> wrote: > On 2010-01-09, Jim Diamond wrote: > I writ: >>> You have to be root to use the command i.e. username]$lsusb >> Of course, this is not true. You should really try out such simple >> things before spreading misinformation to the rest of the world. > Certainly, other ways but if you are new to Linux, you will have to > explain that it can't get a result from just a user and using only > lsusb. Simple to just change to root and back again. Is that simpler than preceding "lsusb" with "/sbin/" ? Hmmmm. > Perhaps I should have said as a user use /usr/sbin/lsusb and the > result will follow. **sigh** /usr/sbin/lsusb will work on some Linux distributions, but not on Slackware 12.2 or 13.0. Jim |