From: Glyn Millington on
Mike Spencer <mds(a)bogus.nodomain.nowhere> writes:

> I haven't folowed all the details of this thread so this may be way
> off base, but...
>
> If you used the Logitech cam on Slack 11 or earlier and you have now
> ported the same driver to Slack 12, you may possibly be having
> problems with the libs used to compile the driver. Slack 12 switched
> to new versions of some libs (gnulibc? gnulic++?) and non-open source
> software compiled with the earlier libs may fail.
>
> This has really pissed me off because I have two commercial packages
> for which I'm compelled to stay with Slack 11 even when I've upgraded
> other boxen to Slack 12. Grrrrrrr....

Just wondering - would VirtualBox set you free here?

http://www.virtualbox.org/



ie run Slackware 13 on your machine (with all that juicy KDE4 goodness
:-) but have Slack 11 installed as a virtual machine via VirtualBox and
fire it up when you need your commercial apps?

It may be overkill of course .....

atb




Glyn
--
RTFM http://www.tldp.org/index.html
GAFC http://slackbook.org/ The Official Source :-)
STFW http://groups.google.com/groups?hl=en&group=alt.os.linux.slackware
JFGI http://jfgi.us/
From: Jim Diamond on
On 2010-01-08 at 16:43 AST, Bud <Bud(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
From: Bud on
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.
>
> 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

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. Perhaps I should
have said as a user use /usr/sbin/lsusb and the result will follow.
--
Bud
From: Tuxedo on
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

[..]
From: microsys on
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.