I have both wxcam and guvcview on my Slackware-Current system, kernel 15.12.14. Neither can see the Logitech webcam even though lsusb identifies it:
Running wxcam gives the error: "Error opening /dev/video0. Please check if your system has the correct driver for your webcam, ..."

Running guvcview gives the error: "no video device found. You seem to have video devices installed. Do you want to try one?" Selecting the shown device from the drop-down "UVC Camera (046d:0825)" gives the same error, although this is obviously the same device as listed by lsusb.

This same webcam worked "out of the box" with Slackware 14.2.

Please advise. Thanks

You are kind to stop comparing the Slackware 15.0 RC1 with the Slackware 14.2 ?

Yeah, you have some hardware which worked with a kernel released 6 (six) year ago, but not with today's kernels. We got it!

BUT, does not helps this comparation for something to fix on -current.

Yea sure ..when you say that , im doubt of rest of your message

Slackware-Current system, kernel 15.12.14

wellcome year 2050

LuckyC. pointless comment. Yes, it can be important to let people know that this same hardware did work on a previous OS version which, by the way, is still the official "supported" release.

Sorry, typeo. That should have been 5.12.14. I've just now upgraded to kernel 5.13.12. Same problem.

1 members found this post helpful.

Pointless? How meaningful is to compare two kernels at 6 years distance, like you do?

Because is obviously that's a kernel driver issue and something happened between the 4.4.x and 5.13.x releases, which "something" means losing proper support for your webcam.

BUT, several hundreds of kernel releases happened meantime.

Who can say you on which one happened this thing and which patch is the cause?

If you want a sincere opinion: feel free to rollback the kernels one by one, until you find the newest one still supporting properly your webcam.

https://slackware.uk/cumulative/

Then, probably you should fill a bug report to kernel.org in my humble opinion - your thirdly party applications reads directly from kernel's devices their video data, so nothing else than the kernel could be at the fault.

Ho_o_old on thar Baba Looey. The kernel mfoley is using obviously DOES see the logitech webcam. What DOESN'T is wxcam and guvcview, both of which are not part of Current by default and only available as SBO addons for 14.2.... so hardly "out of the box".

Now many if not most 14.2 SBOs also work on Current but it and all of the dependencies need to be built in many if not most SBOs when expected to work properly in Current.

My Logitech C310 works great in 14.2 and Current with https://github.com/webcamoid/webcamoid. You might try it or rebuild your current packages but you have no basis to blame Current or your kernel. IIRC there are other ways to at least check video and audio basics with apps that are in default install but I don't recall them since they are just basic and I really like Webcamoid, no installation required.

FWIW I love KDE but Kamoso hasn't ever worked for me due to some QT errors with XDG but I'll maybe figure that out when Official is released.

Don't you have to be a member of the video or wheel group to access it?

1 members found this post helpful.

when thinks like this happen its not a bad idea to search in other distros too
https://forums.gentoo.org/viewtopic-...3db3b25550798c

check the changes to
drivers/media/usb/uvc/uvc_video.c
in the kernel you are using.

why dont you update your kernel?
you mention kernel 15.12.14. latest version of kernel in current is 5.13.12.

i dont thinks its really a good idea to use 14.2 SBOs with current when you have updated slackbuilds available.
with this you ll have new slackbuilds to rebuild your packages https://sbopkg.org/test/sbopkg-0.38.2-noarch-1_wsr.tgz

All: First off, Slackware 14.2 is still the current/supported version of Slackware and that kernel is still being updated and is currently at 4.4.261 on one of my 14.2 systems, updated April, 2021 -- so it's not 6 years old. But, that's not the issue. My point was that this worked under Slackware before will identical hardware, so there is something different with kernel, drivers or libraries.

I do not recall specifically installing guvcview on 14.2. I thought it was already there and accessible from KDE, but perhaps I am mistaken and did install it from SlackBuilds. I'd have to boot back to my 14.2 system to check, but not really important.

adcdam: in my post #4 I did say I upgraded to 15.13.12 and the problem didn't go away.

enine: I am a member of the video group.

enorbet/adcdam: I am not using the 14.2 SlackBuilds repository. I am using the Current sbopkg repo. How to use Current and not the 14.2 repo was a subject of an earlier thread of mine https://www.linuxquestions.org/quest...ent-4175699596, which is what enabled me to build guvcview 2.0.7, today, for Slackware-Current.

LuckyCyBorg: "your thirdly party applications reads directly from kernel's devices their video data, so nothing else than the kernel could be at the fault." That's what I'm trying to determine. If neither guvcview nor wxcam work for anyone else on Slackware-Current, then perhaps a bug-report is in order to the Slackware developers ... or just wait until 15.0 comes out.

I will try enorbet's recommended webcamoid, although, sorry to sound like an idiot, but I rarely use gitHub and I have to spend time researching how to actually download the files. There's no simple "download" button.

I will also try logging in with KDE in case that makes a difference versus XFCE.

If anyone has any additional thoughts on why I'm getting "Error opening /dev/video0" and "no video device found", I'm all ears!

Later ...

Just tried booting with KDE and running programs. Same errors. I'll try webcamiod and post back.

1 members found this post helpful.

Yeah that is a bit of a PITA at github. I just click the green "Code" button and select "download zip". It extracts to it's own directory tree and the top tier has webcamoid.sh. I just symlink it to /usrbin/webcamoid. It's kinda cool that it's a blob but only because it offers a lot of detailed options and control.

FWIW webcamoid works great on 14.2 w/ 5.11.11 and on Current w/ 5.12.12

2 members found this post helpful.

Figured out how to download webcamoid from gitHub (green "Code" button). The README.md file says, "Visit the [wiki](https://github.com/webcamoid/webcamoid/wiki) for a comprehensive compile and install instructions." Went there. Instructions were:
I didn't see anything in the BUILD_FLAGS_GOES_HERE that was required. running 'qmake Webcamoid.pro' gives:
running 'make' gives:
Again, sorry to be an idiot. Not use to gitHub builds. What am I doing wrong?

I have yet to have a problem in years. Basically they either build and run or they don't. If an app is exceptionally important, I make my own poackage. Being Slackware, failure to build is usually pretty easy to fix and if it builds but doesn't run a slight alteration for building newer src usually fixes that and both negatives are exceedingly rare. The main reason I switched to Slackware 20+ years ago was to at least have the option to not be locked into repos.

2 members found this post helpful.

I rarely have an issue with old Slackbuilds on -current but have tried to make it a habit to go ahead and get the updated from the ponce repo on the first page of https://www.linuxquestions.org/quest...ls-4175561999/ for a couple reasons:

1. some of the 14.2 Slackbuilds build older versions of the software you want either because they just haven't been updated or the newer version needs something else newer than whats in 14.2. What I used to do when I found I wanted a newer version of something than what was in the 14.2 Slackbuild was just download the newer source and edit the Slackbuild to specify that version and often then built fine. But since ponce already consolidated all these new versions for testing I find that the version I wanted to use has already been updated in those Slackbuilds and well, could I really call myself a Slacker if I did work that someone else had already done?

2. Now I'm finally able to give back a little bit, I'll run that ponce Slackbuild and if it errors see if I can find a fix myself and then check the thread to see if anyone else already reported the problem and/or provided a fix. If not then I can report it and show the fix if I found it and then Ponce can push the changes.

3. Is say for about the last 6 months or so a lot of 14.2 Slackbuilds have started throwing errors in current due to new defaults in gcc that typically just need a compiler flag to work around or the qt4/5 issues so I've say issues have gone from exceedingly rare to rare

So anyway I think the point I wanted to make when I started typing this was that I'd suggest using the -current ponce Slackbuilds not because you need to but to help others.

works fine here Seems you need to read slackware documentation.
or not be so rude to people in here.
All v4l2 work fine in 14.2 and current
then Digi cam works fine.
Since you are so smart and rude read the docs and fix it your self.
Better yet ask what have I changed that may cause this.

FWIW I have the same device and it works just fine in -current. For testing, I just run 'qv4l2'.although 'mplayer -tv device=/dev/video0 tv://' also works.
My user has

1 members found this post helpful.