On Mon, Oct 17, 2022 at 11:07 PM Tim via users
wrote:
> Is the computer powering other things via its USB ports?
>
> Inadequate power is one potential cause for USB disconnects. I'm not
> sure if the USB power negotiation is done entirely in the hardware, or
> if the OS has a say in the matter.
Samuel Sieb:
>> "Unless you keep unplugging it, it appears to be having a problem. Are
>> you using it with windows on this same computer on the same port?"
linux guy:
> Not with this log I'm not. But my laptop dual boots F36 and Windows
> 10. F36 freezes just like on this computer. Windows 1
On 10/17/22 14:57, linux guy wrote:
"Unless you keep unplugging it, it appears to be having a problem. Are
you using it with windows on this same computer on the same port?"
Not with this log I'm not. But my laptop dual boots F36 and Windows
10. F36 freezes just like on this computer. Windo
"Unless you keep unplugging it, it appears to be having a problem. Are
you using it with windows on this same computer on the same port?"
Not with this log I'm not. But my laptop dual boots F36 and Windows
10. F36 freezes just like on this computer. Windows 10 runs it fine.
__
On 10/17/22 13:18, linux guy wrote:
Oct 17 14:13:57 workstation1 kernel: usb 1-3: USB disconnect, device number 10
Oct 17 14:14:24 workstation1 kernel: usb 1-3: new high-speed USB
device number 11 using xhci_hcd
Oct 17 14:14:26 workstation1 kernel: usb 1-3: USB disconnect, device number 11
Oct 17 14:10:29 workstation1 cupsd[1286]: REQUEST localhost - - "POST
/ HTTP/1.1" 200 181 Renew-Subscription successful-ok
Oct 17 14:11:53 workstation1 cups.cups-browsed[1517]: + true
Oct 17 14:11:53 workstation1 cups.cups-browsed[1517]: + sleep 3600
Oct 17 14:13:57 workstation1 kernel: usb 1-3: US
On 10/17/22 12:57, linux guy wrote:
Thanks for the reply.
Here is the output when it fails. The "Unable to dequeue buffer: no
such device" message happens hundreds of times.
...
Oct 17 13:54:05 workstation1 plasmashell[16214]: V4L2_CORE:
(VIDIOC_DQBUF) Unable to dequeue buffer: No such device
Thanks for the reply.
Here is the output when it fails. The "Unable to dequeue buffer: no
such device" message happens hundreds of times.
...
Oct 17 13:54:05 workstation1 plasmashell[16214]: V4L2_CORE:
(VIDIOC_DQBUF) Unable to dequeue buffer: No such device
Oct 17 13:54:05 workstation1 plasmashe
On 10/17/22 08:59, linux guy wrote:
I need to use Mobius 1 Action cameras in a project.
When I connect these cameras to VLC or guvcview they play correctly
for about 10 seconds and then freeze.They work properly in Windows
11.
How do I troubleshoot this issue or get someone from the appropr
I need to use Mobius 1 Action cameras in a project.
When I connect these cameras to VLC or guvcview they play correctly
for about 10 seconds and then freeze.They work properly in Windows
11.
How do I troubleshoot this issue or get someone from the appropriate
community to help me ?
Thanks
__
Short note: I used the camera on a Mac without any problem.
Thanks for all for the tips, I will try them over the week-end.
- Gergely
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelin
Gergely Buday wrote:
> Hi,
>
> fedora did not automount my camera. So I tried lsusb, which has found
> it, but even in verbose mode it did not tell me any data that can be
> fed to mount. How can I mount then my camera?
>
> Bus 001 Device 004: ID 04b0:031d Nikon Corp.
>
> was the relevant line i
On Mon, Jul 9, 2012 at 4:18 AM, Gergely Buday wrote:
> Hi,
>
> fedora did not automount my camera. So I tried lsusb, which has found
> it, but even in verbose mode it did not tell me any data that can be
> fed to mount. How can I mount then my camera?
>
> Bus 001 Device 004: ID 04b0:031d Nikon Co
On 09/07/12 07:18, Gergely Buday types:
Hi,
fedora did not automount my camera. So I tried lsusb, which has found
it, but even in verbose mode it did not tell me any data that can be
fed to mount. How can I mount then my camera?
Bus 001 Device 004: ID 04b0:031d Nikon Corp.
was the relevant lin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/09/2012 12:52 PM, Gergely Buday wrote:
> Bus 001 Device 004: ID 04b0:031d Nikon Corp. [gergoe@oldship
> regio_et_religio]$ lsusb -vs 001:004
>
> Interface Descriptor: bLength 9 bDescriptorType
> 4 bInterfaceNumber0 bAlter
> Does this camera "mount" under other distributions?
I do not know.
> $ lsusb -vs 002:045 | grep bInt
Bus 001 Device 004: ID 04b0:031d Nikon Corp.
[gergoe@oldship regio_et_religio]$ lsusb -vs 001:004
Bus 001 Device 004: ID 04b0:031d Nikon Corp.
Device Descriptor:
bLength18
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/09/2012 12:18 PM, Gergely Buday wrote:
> fedora did not automount my camera. So I tried lsusb, which has
> found it, but even in verbose mode it did not tell me any data that
> can be fed to mount. How can I mount then my camera?
>
> Bus 001 Dev
On Mon, 2012-07-09 at 13:18 +0200, Gergely Buday wrote:
> Hi,
>
> fedora did not automount my camera. So I tried lsusb, which has found
> it, but even in verbose mode it did not tell me any data that can be
> fed to mount. How can I mount then my camera?
Many cameras have an option to connect as
Hi,
fedora did not automount my camera. So I tried lsusb, which has found
it, but even in verbose mode it did not tell me any data that can be
fed to mount. How can I mount then my camera?
Bus 001 Device 004: ID 04b0:031d Nikon Corp.
was the relevant line in lsusb output.
- Gergely
--
users ma
On 04/16/2012 12:05 PM, Patrick Dupre wrote:
> Hello,
>
> When I plug my camera on the usb port it is recognized on bus 006
> but the device is incremented every time. Hence, every time I need to
> make a chmod a+w /dev/bus/usb/006/0xx to let a user read the pictures.
>
> How can I fix this more
Hello,
When I plug my camera on the usb port it is recognized on bus 006
but the device is incremented every time. Hence, every time I need to
make a chmod a+w /dev/bus/usb/006/0xx to let a user read the pictures.
How can I fix this more elegantly?
Thank.
--
---
===
21 matches
Mail list logo
