12:10 p.m.
People,
I didn't get a response to my previous Q re an apparent problem with
getting gphoto2 to work with my GoPro Hero 4 Session camera - I hadn't
used the camera for a while and I thought maybe the Fedora upgrades
since then were the cause of the problem - but maybe the problem is
actually with the USB port on the camera? (gphoto2 used to work). The
camera actually charges OK through the port and I can record videos and
then move them to Fedora by moving the SC card to a card reader,
mounting the dir and copying video files to the HD so the camera itself
and device charging seems to be OK.
I am getting nothing recorded in /var/log/messages when I plug in the
GoPro and push its power button (plugging in any other USB device is
working of course) so maybe it is the USB port on the camera that is the
problem? - is there any way to debug that from the Fedora workstation?
Thanks,
Phil.
--
Philip Rhoades
PO Box 896
Cowra NSW 2794
Australia
E-mail: phil(a)pricom.com.au
7:22 p.m.
On 2021-10-26 10:10, Philip Rhoades via users wrote:
I didn't get a response to my previous Q re an apparent problem
with
getting gphoto2 to work with my GoPro Hero 4 Session camera - I hadn't
used the camera for a while and I thought maybe the Fedora upgrades
since then were the cause of the problem - but maybe the problem is
actually with the USB port on the camera? (gphoto2 used to work). The
camera actually charges OK through the port and I can record videos and
then move them to Fedora by moving the SC card to a card reader,
mounting the dir and copying video files to the HD so the camera itself
and device charging seems to be OK.
I am getting nothing recorded in /var/log/messages when I plug in the
GoPro and push its power button (plugging in any other USB device is
working of course) so maybe it is the USB port on the camera that is the
problem? - is there any way to debug that from the Fedora workstation?
If there is no message and another USB device shows up if you plug it
in, then the problem is either with the camera or the cable.
8:13 p.m.
Samuel,
On 2021-10-27 11:22, Samuel Sieb wrote:
On 2021-10-26 10:10, Philip Rhoades via users wrote:
> I didn't get a response to my previous Q re an apparent problem with
> getting gphoto2 to work with my GoPro Hero 4 Session camera - I hadn't
> used the camera for a while and I thought maybe the Fedora upgrades
> since then were the cause of the problem - but maybe the problem is
> actually with the USB port on the camera? (gphoto2 used to work). The
> camera actually charges OK through the port and I can record videos
> and then move them to Fedora by moving the SC card to a card reader,
> mounting the dir and copying video files to the HD so the camera
> itself and device charging seems to be OK.
>
> I am getting nothing recorded in /var/log/messages when I plug in the
> GoPro and push its power button (plugging in any other USB device is
> working of course) so maybe it is the USB port on the camera that is
> the problem? - is there any way to debug that from the Fedora
> workstation?
If there is no message and another USB device shows up if you plug it
in, then the problem is either with the camera or the cable.
And therefore there is no to debug from the computer side . . OK . .
Thanks!
Phil.
--
Philip Rhoades
PO Box 896
Cowra NSW 2794
Australia
E-mail: phil(a)pricom.com.au
3:01 a.m.
On Wed, 2021-10-27 at 04:10 +1100, Philip Rhoades via users wrote:
I am getting nothing recorded in /var/log/messages when I plug in
the GoPro and push its power button (plugging in any other USB device
is working of course) so maybe it is the USB port on the camera that
is the problem? - is there any way to debug that from the Fedora
workstation?
Before you plug it in, open a command line and run: dmesg
Open another command line window, plug it in, and run dmesg in the
second window.
Now you can compare the messages at the end of each dump against each
other.
If it recognised the hardware, you should get some information about
it. If not, a simple first test is to try another USB lead. You can
have broken data lines, and still have functioning power lines, within
the cable, allowing it to charge.
By way of example, when I plug in a webcam, it shows all this gubbins:
[3887829.895943] usb 1-12: new high-speed USB device number 51 using xhci_hcd
[3887830.123901] usb 1-12: New USB device found, idVendor=0c45, idProduct=6366, bcdDevice=
1.00
[3887830.123928] usb 1-12: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[3887830.123936] usb 1-12: Product: CM200
[3887830.123943] usb 1-12: Manufacturer: Sonix Technology Co., Ltd.
[3887830.123949] usb 1-12: SerialNumber: SN0001
[3887830.174819] usb 1-12: 3:1: cannot get freq at ep 0x84
[3887830.395965] Linux video capture interface: v2.00
[3887830.437188] uvcvideo: Found UVC 1.00 device CM200 (0c45:6366)
[3887830.462969] input: CM200 as
/devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.0/input/input51
[3887830.463068] usbcore: registered new interface driver uvcvideo
[3887830.463070] USB Video Class driver (1.1.1)
[3887830.921714] usb 1-12: 3:1: cannot get freq at ep 0x84
[3887830.993514] usb 1-12: 3:1: cannot get freq at ep 0x84
[3892705.253593] snd_hda_intel 0000:00:1f.3: Unstable LPIB (352800 >= 176400);
disabling LPIB delay counting
--
uname -rsvp
Linux 3.10.0-1160.42.2.el7.x86_64 #1 SMP Tue Sep 7 14:49:57 UTC 2021 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
4:47 a.m.
Tim,
On 2021-10-27 19:01, Tim via users wrote:
On Wed, 2021-10-27 at 04:10 +1100, Philip Rhoades via users wrote:
> I am getting nothing recorded in /var/log/messages when I plug in
> the GoPro and push its power button (plugging in any other USB device
> is working of course) so maybe it is the USB port on the camera that
> is the problem? - is there any way to debug that from the Fedora
> workstation?
Before you plug it in, open a command line and run: dmesg
Open another command line window, plug it in, and run dmesg in the
second window.
Now you can compare the messages at the end of each dump against each
other.
It is simpler to just: tail -f /var/log/messages
If it recognised the hardware, you should get some information about
it. If not, a simple first test is to try another USB lead. You can
have broken data lines, and still have functioning power lines, within
the cable, allowing it to charge.
Right - see next reply to Samuel's post . .
Thanks,
Phil.
By way of example, when I plug in a webcam, it shows all this
gubbins:
[3887829.895943] usb 1-12: new high-speed USB device number 51 using
xhci_hcd
[3887830.123901] usb 1-12: New USB device found, idVendor=0c45,
idProduct=6366, bcdDevice= 1.00
[3887830.123928] usb 1-12: New USB device strings: Mfr=2, Product=1,
SerialNumber=3
[3887830.123936] usb 1-12: Product: CM200
[3887830.123943] usb 1-12: Manufacturer: Sonix Technology Co., Ltd.
[3887830.123949] usb 1-12: SerialNumber: SN0001
[3887830.174819] usb 1-12: 3:1: cannot get freq at ep 0x84
[3887830.395965] Linux video capture interface: v2.00
[3887830.437188] uvcvideo: Found UVC 1.00 device CM200 (0c45:6366)
[3887830.462969] input: CM200 as
/devices/pci0000:00/0000:00:14.0/usb1/1-12/1-12:1.0/input/input51
[3887830.463068] usbcore: registered new interface driver uvcvideo
[3887830.463070] USB Video Class driver (1.1.1)
[3887830.921714] usb 1-12: 3:1: cannot get freq at ep 0x84
[3887830.993514] usb 1-12: 3:1: cannot get freq at ep 0x84
[3892705.253593] snd_hda_intel 0000:00:1f.3: Unstable LPIB (352800 >=
176400); disabling LPIB delay counting
--
uname -rsvp
Linux 3.10.0-1160.42.2.el7.x86_64 #1 SMP Tue Sep 7 14:49:57 UTC 2021
x86_64
Boilerplate: All unexpected mail to my mailbox is automatically
deleted.
I will only get to see the messages that are posted to the mailing
list.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
--
Philip Rhoades
PO Box 896
Cowra NSW 2794
Australia
E-mail: phil(a)pricom.com.au
11:08 p.m.
On Wed, 2021-10-27 at 20:47 +1100, Philip Rhoades via users wrote:
It is simpler to just: tail -f /var/log/messages
I've noticed things turn up in dmesg that don't turn up in
/var/log/messages
--
uname -rsvp
Linux 3.10.0-1160.45.1.el7.x86_64 #1 SMP Wed Oct 13 17:20:51 UTC 2021 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
11:44 p.m.
On 10/27/21 21:08, Tim via users wrote:
On Wed, 2021-10-27 at 20:47 +1100, Philip Rhoades via users wrote:
> It is simpler to just: tail -f /var/log/messages
I've noticed things turn up in dmesg that don't turn up in
/var/log/messages
/var/log/messages is legacy, I don't even have that file on my computer.
"journalctl" will show you everything.
2:56 a.m.
Tim:
> I've noticed things turn up in dmesg that don't turn up
in
> /var/log/messages
Samuel Sieb:
/var/log/messages is legacy, I don't even have that file on my
computer.
I know, but I do, on purpose. Because:
"journalctl" will show you everything.
Is a right bastard to deal with. Quite apart from having to remember
new options for a new command, as opposed to just reading a text
file, I find that it's got to trawl through a behemoth of data to come
up with results. To call it sluggish would be an understatement. It's
overkill for most things, and as fun to use as working out regex
parameters.
--
uname -rsvp
Linux 3.10.0-1160.45.1.el7.x86_64 #1 SMP Wed Oct 13 17:20:51 UTC 2021 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
3:06 a.m.
On 2021-10-28 00:56, Tim via users wrote:
Tim:
>> I've noticed things turn up in dmesg that don't turn up in
>> /var/log/messages
Samuel Sieb:
> /var/log/messages is legacy, I don't even have that file on my
> computer.
I know, but I do, on purpose. Because:
> "journalctl" will show you everything.
Is a right bastard to deal with. Quite apart from having to remember
new options for a new command, as opposed to just reading a text
file, I find that it's got to trawl through a behemoth of data to come
up with results. To call it sluggish would be an understatement. It's
overkill for most things, and as fun to use as working out regex
parameters.
Maybe spend a little time figuring it out. It's amazingly useful once
you start to understand it. I don't find it sluggish at all, but maybe
that's because I use SSDs.
11:10 p.m.
Tim:
> Open another command line window, plug it in, and run dmesg in
the
> second window.
Joe Zeff:
Save yourself some typing and use the proper name: terminal.
I could argue that it's not a terminal. Old enough computer guys will
tell you what a terminal really is. :-p
--
uname -rsvp
Linux 3.10.0-1160.45.1.el7.x86_64 #1 SMP Wed Oct 13 17:20:51 UTC 2021 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
12:59 p.m.
On Thu, 28 Oct 2021 at 03:05, Joe Zeff <joe(a)zeff.us> wrote:
On 10/27/21 10:10 PM, Tim via users wrote:
> I could argue that it's not a terminal. Old enough computer guys will
> tell you what a terminal really is. :-p
The first computer I ever programmed was an IBM 1620 Mod 2 back in '68.
Does that make me an old enough computer guy?
In '68 I was using a teletype terminal with paper tape to store programs.
Now I encounter confusion when I ask that posts in scientific forums
copy and paste text from the "terminal" into a post because their screen
snapshot is difficult to read and cuts off critical information at the end
of a long line.
--
George N. White III
2:30 p.m.
New subject: [Off Topic] Re: Debugging USB device issues
On 10/28/21 11:59 AM, George N. White III wrote:
Now I encounter confusion when I ask that posts in scientific
forums
copy and paste text from the "terminal" into a post because their screen
snapshot is difficult to read and cuts off critical information at the end
of a long line.
BTDT. Once, when I was doing tech support for a company selling
security equipment to self-storage facilities I started a tempest in a
teapot because a brain fart made me forget the term multimeter and I
referred to it in my notes as a VOM. Later, I almost caused another one
by calling a power light a pilot light but caught myself in time.
When I was doing support for an ISP, I reluctantly referred to folders
because that's what the callers understood, but if we had to go to a
CLI, I'd call them directories, explaining that it was the proper term
in that environment.
3:31 a.m.
On 2021-10-26 10:10, Philip Rhoades via users wrote:
I am getting nothing recorded in /var/log/messages when I plug in the
GoPro and push its power button (plugging in any other USB device is
working of course) so maybe it is the USB port on the camera that is the
problem? - is there any way to debug that from the Fedora workstation?
After seeing Tim's message, I realized what you wrote. How do you have
/var/log/messages? Run "sudo journalctl -fa" in a terminal before
plugging in the cable and see if anything shows up.
4:54 a.m.
Samuel,
On 2021-10-27 19:31, Samuel Sieb wrote:
On 2021-10-26 10:10, Philip Rhoades via users wrote:
> I am getting nothing recorded in /var/log/messages when I plug in the
> GoPro and push its power button (plugging in any other USB device is
> working of course) so maybe it is the USB port on the camera that is
> the problem? - is there any way to debug that from the Fedora
> workstation?
After seeing Tim's message, I realized what you wrote. How do you
have /var/log/messages? Run "sudo journalctl -fa" in a terminal
before plugging in the cable and see if anything shows up.
Interesting - at first I got no response for a couple of the permuations
I had tried before - so I tried a new permutation of USB port and two
cables - an extension cable connected to a std USB cable with a micro
plug - which worked! Now I am confused about why ALL the other
permutations worked for ALL the other devices - besides the camera . .
weird - maybe it is an intermittent cable or camera problem? - hmm . .
more testing required . . at least I know now that the connection is not
100% failed . .
Thanks for responding - I appreciate it!
Regards,
Phil.
--
Philip Rhoades
PO Box 896
Cowra NSW 2794
Australia
E-mail: phil(a)pricom.com.au
9:41 a.m.
Note, from my experience the micro usb plug was the worst usb plug
ever. (commonly used for charging/data). It seems to wear out and
stop working on the device end (ie the expensive end). I had to get a
wireless charge for my last phone with micro usb because even with a
new cable you physically had to hold the phone and the cable just
write to get it to charge. The mini-usb did not seem to have that
wear issue as fast. My phone stopped working/charging with around 1x
insertion per day for about 3 years (around 1000 insertions) and the
wear issue was on the expensive end (the phone/socket side), not the
cable end as the design intended.
micro-usb was designed to be more reliable than mini-usb, my data, and
many others real world data seems to indicate that design was
massively flawed and the micro-usb is unreliable crap and while
designed to have 2-10x more insertions than mini-usb (in theory) seems
to fail several times faster than mini-usb (in reality). And has to
then be bent/adjusted/held just right for it to work (even with "new"
cables). So be careful with that flawed micro-usb data/charging
connection. And while it could be that it was just some of the
micro-usb sockets the one I had go bad was in a major manufacturer
high-end phone, so not someplace that should have bought the cheapest
socket built by a poor manufacturer.
On Wed, Oct 27, 2021 at 4:54 AM Philip Rhoades via users
<users(a)lists.fedoraproject.org> wrote:
>
> Samuel,
>
>
> On 2021-10-27 19:31, Samuel Sieb wrote:
> > On 2021-10-26 10:10, Philip Rhoades via users wrote:
> >> I am getting nothing recorded in /var/log/messages when I plug in the
> >> GoPro and push its power button (plugging in any other USB device is
> >> working of course) so maybe it is the USB port on the camera that is
> >> the problem? - is there any way to debug that from the Fedora
> >> workstation?
> >
> > After seeing Tim's message, I realized what you wrote. How do you
> > have /var/log/messages? Run "sudo journalctl -fa" in a terminal
> > before plugging in the cable and see if anything shows up.
>
>
> Interesting - at first I got no response for a couple of the permuations
> I had tried before - so I tried a new permutation of USB port and two
> cables - an extension cable connected to a std USB cable with a micro
> plug - which worked! Now I am confused about why ALL the other
> permutations worked for ALL the other devices - besides the camera . .
> weird - maybe it is an intermittent cable or camera problem? - hmm . .
> more testing required . . at least I know now that the connection is not
> 100% failed . .
>
> Thanks for responding - I appreciate it!
>
> Regards,
>
> Phil.
> --
> Philip Rhoades
>
> PO Box 896
> Cowra NSW 2794
> Australia
> E-mail: phil(a)pricom.com.au
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
10:46 a.m.
On Wed, 27 Oct 2021 at 06:54, Philip Rhoades via users <
users(a)lists.fedoraproject.org> wrote:
Samuel,
On 2021-10-27 19:31, Samuel Sieb wrote:
> On 2021-10-26 10:10, Philip Rhoades via users wrote:
>> I am getting nothing recorded in /var/log/messages when I plug in the
>> GoPro and push its power button (plugging in any other USB device is
>> working of course) so maybe it is the USB port on the camera that is
>> the problem? - is there any way to debug that from the Fedora
>> workstation?
>
> After seeing Tim's message, I realized what you wrote. How do you
> have /var/log/messages? Run "sudo journalctl -fa" in a terminal
> before plugging in the cable and see if anything shows up.
Interesting - at first I got no response for a couple of the permuations
I had tried before - so I tried a new permutation of USB port and two
cables - an extension cable connected to a std USB cable with a micro
plug - which worked! Now I am confused about why ALL the other
permutations worked for ALL the other devices - besides the camera . .
weird - maybe it is an intermittent cable or camera problem? - hmm . .
more testing required . . at least I know now that the connection is not
100% failed . .
Thanks for responding - I appreciate it!
Glad your camera is still alive. Cables and connectors should always be a
prime suspect when things stop working. Having worked at an oceanographic
institute, salt air and cables is not a good combination. Cables and
connectors are vulnerable to damage from corrosion and vibration.
Cheap cables are also prone radio-frequency interference (RFI). You
can buy "contact enhancer" fluid such as "Stabilant 22" (used in
aviation
and increasingly used by automakers and auto repair shops -- I'm in
Canada and Stabilant 22 is now sold by auto parts stores here).
USB3 uses signals that can cause RFI with older equipment.
I find that older USB2 devices are often more reliable when used with
an external hub so not connected to a socket on the back of a system
next to one being used by a USB3 device.
--
George N. White III
916
days inactive
918
days old
17 comments
6 participants
participants (6)
-
George N. White III -
Joe Zeff -
Philip Rhoades -
Roger Heflin -
Samuel Sieb -
Tim