thr3ads.net - Nut upsuser - [Nut-upsuser] Eaton 5E 1100i USB UPS - failed to claim USB device error [Aug 2020]

If this information is useful, please help other people find it:
Share via:

Louis van Dyk

2020-Aug-19 07:36 UTC

[Nut-upsuser] Eaton 5E 1100i USB UPS - failed to claim USB device error

Hi
BACKGROUND INFO:I have a new Eaton 5E 1100i USB UPS which their website
claims is supported on Linux.  They don't provide software for it for
Linux, only for Windows.Referring links:
https://www.eaton.com/za/en-gb/catalog/backup-power-ups-surge-it-power-distribution/Eaton_5E_UPS.html
https://www.eaton.com/za/en-gb/skuPage.5E1100IUSB.specifications.html
It was manufactured in May 2020 according to the sticker on the box.
I am running on Fedora 32 with all the latest patches.  I installed nut
and nut-client from the Fedora repository, which provides version nut-
2.7.4-27.fc32.x86_64nut-client-2.7.4-27.fc32.x86_64
On https://networkupstools.org/stable-hcl.html I am told that it is 5*
green "vendor provided protocol and hardware" using usbhis-ups as a
driver.
PROBLEM:1.  The UPS is listed in "lsusb" as Bus 002 Device 101: ID
0463:ffff MGE UPS Systems UPSHowever, I notice that is disappears and
reconnects every 19 seconds.  I've seen some posts noticing this too,
and stating that it stops once it is successfully connected to the
software.  I hope that is true and that I haven't been wasting effort
on a faulty device.  I have tried with my printer's USB cable and seen
the same thing.  I then tried it on my laptop (also on Fedora 32) with
the same result.  To me this eliminates my PC and the cabling.
2.  The device is detected by "nut-scanner -U" as:root at fedora ~]#
nut-
scanner -UScanning USB bus.[nutdev1]	driver = "usbhid-ups"	port
"auto"	vendorid = "0463"	productid = "FFFF"
product = "5E"
bus = "002"I have put that exact info into /etc/ups/ups.conf -
it's the
only info not commented with a # in the file.  I changed the name to
eaton5e though.
When I then run:  [root at fedora ~]# /usr/sbin/usbhid-ups -DDDD -a
eaton5e Network UPS Tools - Generic HID driver 0.41 (2.7.4)USB
communication driver 0.33   0.000000	debug level is '4'   0.002054	
upsdrv_initups...   0.017685	Checking device (0463/FFFF)
(002/120)   2.024057	- VendorID: 0463   2.024080	- ProductID:
ffff   2.024083	- Manufacturer: unknown   2.024087	- Product:
unknown   2.024090	- Serial Number: unknown   2.024093	- Bus:
002   2.024096	- Device release number: 0001   2.024099	Trying
to match device   2.024122	Device matches   2.024134	failed
to claim USB device: Device or resource busy   4.898305	detached kernel
driver from USB device...   4.898344	nut_usb_set_altinterface:
skipped usb_set_altinterface(udev, 0)   9.901010	Unable to get
HID descriptor (Connection timed out)   9.901031	HID descriptor
length (method 1) -1   9.901037	i=0, extra[i]=09,
extra[i+1]=21   9.901044	HID descriptor, method 2: (9 bytes) =>
09 21 10 01 21 01 22 25 02   9.901048	HID descriptor length (method
2) 549   9.901052	HID descriptor length 549   9.901370	Unable
to get Report descriptor: Broken pipe   9.901403	Checking device
(1B1C/0A17) (002/003)   9.901435	Failed to open device,
skipping. (Permission denied)   9.901441	Checking device
(8087/0024) (002/002)   9.901448	Failed to open device,
skipping. (Permission denied)   9.901452	Checking device
(1D6B/0002) (002/001)   9.901462	Failed to open device,
skipping. (Permission denied)   9.901468	Checking device
(1B80/B403) (001/005)   9.901477	Failed to open device,
skipping. (Permission denied)   9.901483	Checking device
(18F8/0F97) (001/004)   9.901491	Failed to open device,
skipping. (Permission denied)   9.901497	Checking device
(048D/1345) (001/003)   9.901506	Failed to open device,
skipping. (Permission denied)   9.901511	Checking device
(8087/0024) (001/002)   9.901520	Failed to open device,
skipping. (Permission denied)   9.901526	Checking device
(1D6B/0002) (001/001)   9.901534	Failed to open device,
skipping. (Permission denied)   9.901540	Checking device
(1D6B/0003) (004/001)   9.901549	Failed to open device,
skipping. (Permission denied)   9.901555	Checking device
(1D6B/0002) (003/001)   9.901563	Failed to open device,
skipping. (Permission denied)   9.901569	No appropriate HID
device found   9.901575	No matching HID UPS found
(If I run it with -u root it tries to read my headphones and other USB
devices, but the UPS still has the same result.)
So my problem is:   2.024099	Trying to match device   2.024122	
Device matches   2.024134	failed to claim USB device: Device or
resource busy   4.898305	detached kernel driver from USB
device...   4.898344	nut_usb_set_altinterface: skipped
usb_set_altinterface(udev, 0)
Please could you assist me in getting the driver to load and
successfully connect?
Many thanks,Louis

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200819/7d44d3ae/attachment.html>

Eyal Lebedinsky

2020-Aug-19 08:23 UTC

head link

[Nut-upsuser] Eaton 5E 1100i USB UPS - failed to claim USB device error

On 2020-08-19 17:36, Louis van Dyk wrote:> Hi
> 
> BACKGROUND INFO:
> I have a new Eaton 5E 1100i USB UPS which their website claims is supported
on Linux.  They don't provide software for it for Linux, only for Windows.
> Referring links:
>
https://www.eaton.com/za/en-gb/catalog/backup-power-ups-surge-it-power-distribution/Eaton_5E_UPS.html
> https://www.eaton.com/za/en-gb/skuPage.5E1100IUSB.specifications.html
> It was manufactured in May 2020 according to the sticker on the box.
> 
> I am running on Fedora 32 with all the latest patches.  I installed nut and
nut-client from the Fedora repository, which provides version
> nut-2.7.4-27.fc32.x86_64
> nut-client-2.7.4-27.fc32.x86_64
> 
> On https://networkupstools.org/stable-hcl.html I am told that it is 5*
green "vendor provided protocol and hardware" using usbhis-ups as a
driver.
> 
> PROBLEM:
> 1.  The UPS is listed in "lsusb" as
> Bus 002 Device 101: ID 0463:ffff MGE UPS Systems UPS
> However, I notice that is disappears and reconnects every 19 seconds.
 I've seen some posts noticing this too, and stating that it stops once it
is successfully connected to the software.  I hope that is true and that I
haven't been wasting effort on a faulty device.  I have tried with my
printer's USB cable and seen the same thing.  I then tried it on my laptop
(also on Fedora 32) with the same result.  To me this eliminates my PC and the
cabling.
> 
> 2.  The device is detected by "nut-scanner -U" as:
> 
> root at fedora  <mailto:root at fedora>  ~]# nut-scanner -U
> 
> Scanning USB bus.
> 
> [nutdev1]
> 
> 	driver = "usbhid-ups"
> 
> 	port = "auto"
> 
> 	vendorid = "0463"
> 
> 	productid = "FFFF"
> 
> 	product = "5E"
> 
> 	bus = "002"
> 
> I have put that exact info into /etc/ups/ups.conf - it's the only info
not commented with a # in the file.  I changed the name to eaton5e though.
> 
> When I then run:
> 
> [root at fedora  <mailto:root at fedora>  ~]# /usr/sbin/usbhid-ups
-DDDD -a eaton5e
> 
> Network UPS Tools - Generic HID driver 0.41 (2.7.4)
> 
> USB communication driver 0.33
> 
>     0.000000	debug level is '4'
> 
>     0.002054	upsdrv_initups...
> 
>     0.017685	Checking device (0463/FFFF) (002/120)
> 
>     2.024057	- VendorID: 0463
> 
>     2.024080	- ProductID: ffff
> 
>     2.024083	- Manufacturer: unknown
> 
>     2.024087	- Product: unknown
> 
>     2.024090	- Serial Number: unknown
> 
>     2.024093	- Bus: 002
> 
>     2.024096	- Device release number: 0001
> 
>     2.024099	Trying to match device
> 
>     2.024122	Device matches
> 
>     2.024134	failed to claim USB device: Device or resource busy
> 
>     4.898305	detached kernel driver from USB device...
> 
>     4.898344	nut_usb_set_altinterface: skipped usb_set_altinterface(udev,
0)
> 
>     9.901010	Unable to get HID descriptor (Connection timed out)
> 
>     9.901031	HID descriptor length (method 1) -1
> 
>     9.901037	i=0, extra[i]=09, extra[i+1]=21
> 
>     9.901044	HID descriptor, method 2: (9 bytes) => 09 21 10 01 21 01 22
25 02
> 
>     9.901048	HID descriptor length (method 2) 549
> 
>     9.901052	HID descriptor length 549
> 
>     9.901370	Unable to get Report descriptor: Broken pipe
> 
>     9.901403	Checking device (1B1C/0A17) (002/003)
> 
>     9.901435	Failed to open device, skipping. (Permission denied)
> 
>     9.901441	Checking device (8087/0024) (002/002)
> 
>     9.901448	Failed to open device, skipping. (Permission denied)
> 
>     9.901452	Checking device (1D6B/0002) (002/001)
> 
>     9.901462	Failed to open device, skipping. (Permission denied)
> 
>     9.901468	Checking device (1B80/B403) (001/005)
> 
>     9.901477	Failed to open device, skipping. (Permission denied)
> 
>     9.901483	Checking device (18F8/0F97) (001/004)
> 
>     9.901491	Failed to open device, skipping. (Permission denied)
> 
>     9.901497	Checking device (048D/1345) (001/003)
> 
>     9.901506	Failed to open device, skipping. (Permission denied)
> 
>     9.901511	Checking device (8087/0024) (001/002)
> 
>     9.901520	Failed to open device, skipping. (Permission denied)
> 
>     9.901526	Checking device (1D6B/0002) (001/001)
> 
>     9.901534	Failed to open device, skipping. (Permission denied)
> 
>     9.901540	Checking device (1D6B/0003) (004/001)
> 
>     9.901549	Failed to open device, skipping. (Permission denied)
> 
>     9.901555	Checking device (1D6B/0002) (003/001)
> 
>     9.901563	Failed to open device, skipping. (Permission denied)
> 
>     9.901569	No appropriate HID device found
> 
>     9.901575	No matching HID UPS found
> 
> 
> (If I run it with -u root it tries to read my headphones and other USB
devices, but the UPS still has the same result.)
> 
> So my problem is:
> 
>     2.024099	Trying to match device
> 
>     2.024122	Device matches
> 
>     2.024134	*failed to claim USB device: Device or resource busy*
> 
>     4.898305	detached kernel driver from USB device...
> 
>     4.898344	nut_usb_set_altinterface: skipped usb_set_altinterface(udev,
0)
> 
> 
> Please could you assist me in getting the driver to load and successfully
connect?
> 
> Many thanks,
> Louis
Had this ups, turns out the special treatment for this UPS was removed at some
point
when it was thought that it is not needed anymore...

I manually enabled the quirk with a kernel boot option
	usbhid.quirks=0x0463:0xffff:0x08
Append this to GRUB_CMDLINE_LINUX_DEFAULT in /boot/grub2/grub.cfg

I do not have a record of the source of this advice, I found it searching the
'net.

HTH

-- 
Eyal Lebedinsky (eyal at eyal.emu.id.au)

Louis van Dyk

2020-Aug-19 09:59 UTC

head link

[Nut-upsuser] Eaton 5E 1100i USB UPS - failed to claim USB device error

Thank you Eyal!!

Adding 
usbhid.quirks=0x0463:0xffff:0x08
to the kernel boot parameters did the trick for me.

FYI to those using Fedora 32, to edit the command line use the tool
"grubby" as follows:

grubby --update-kernel=ALL --args="usbhid.quirks=0x0463:0xffff:0x08"


@DEVS:  Could you please re-add the code for using this UPS?  It's
still being sold fast and furious in our region, and I'm sure more
people are having the same problem.

Yogesh Bhanu

2020-Aug-19 11:54 UTC

head link

[Nut-upsuser] Eaton 5E 1100i USB UPS - failed to claim USB device error

Hi,

An alternate suggestion instead of modifying grub config. You can try
the following

create a file "/etc/modprobe.d/ups-usbhid.conf"
append / add the line below
--8<--
options usbhid quirks=0x0463:0xffff:0x08
-->8--

hth


On Wed, Aug 19, 2020 at 10:40 AM Eyal Lebedinsky <eyal at eyal.emu.id.au>
wrote:>
> On 2020-08-19 17:36, Louis van Dyk wrote:
> > Hi
> >
> > BACKGROUND INFO:
> > I have a new Eaton 5E 1100i USB UPS which their website claims is
supported on Linux.  They don't provide software for it for Linux, only for
Windows.
> > Referring links:
> >
https://www.eaton.com/za/en-gb/catalog/backup-power-ups-surge-it-power-distribution/Eaton_5E_UPS.html
> > https://www.eaton.com/za/en-gb/skuPage.5E1100IUSB.specifications.html
> > It was manufactured in May 2020 according to the sticker on the box.
> >
> > I am running on Fedora 32 with all the latest patches.  I installed
nut and nut-client from the Fedora repository, which provides version
> > nut-2.7.4-27.fc32.x86_64
> > nut-client-2.7.4-27.fc32.x86_64
> >
> > On https://networkupstools.org/stable-hcl.html I am told that it is 5*
green "vendor provided protocol and hardware" using usbhis-ups as a
driver.
> >
> > PROBLEM:
> > 1.  The UPS is listed in "lsusb" as
> > Bus 002 Device 101: ID 0463:ffff MGE UPS Systems UPS
> > However, I notice that is disappears and reconnects every 19 seconds. 
I've seen some posts noticing this too, and stating that it stops once it is
successfully connected to the software.  I hope that is true and that I
haven't been wasting effort on a faulty device.  I have tried with my
printer's USB cable and seen the same thing.  I then tried it on my laptop
(also on Fedora 32) with the same result.  To me this eliminates my PC and the
cabling.
> >
> > 2.  The device is detected by "nut-scanner -U" as:
> >
> > root at fedora  <mailto:root at fedora>  ~]# nut-scanner -U
> >
> > Scanning USB bus.
> >
> > [nutdev1]
> >
> >       driver = "usbhid-ups"
> >
> >       port = "auto"
> >
> >       vendorid = "0463"
> >
> >       productid = "FFFF"
> >
> >       product = "5E"
> >
> >       bus = "002"
> >
> > I have put that exact info into /etc/ups/ups.conf - it's the only
info not commented with a # in the file.  I changed the name to eaton5e though.
> >
> > When I then run:
> >
> > [root at fedora  <mailto:root at fedora>  ~]#
/usr/sbin/usbhid-ups -DDDD -a eaton5e
> >
> > Network UPS Tools - Generic HID driver 0.41 (2.7.4)
> >
> > USB communication driver 0.33
> >
> >     0.000000  debug level is '4'
> >
> >     0.002054  upsdrv_initups...
> >
> >     0.017685  Checking device (0463/FFFF) (002/120)
> >
> >     2.024057  - VendorID: 0463
> >
> >     2.024080  - ProductID: ffff
> >
> >     2.024083  - Manufacturer: unknown
> >
> >     2.024087  - Product: unknown
> >
> >     2.024090  - Serial Number: unknown
> >
> >     2.024093  - Bus: 002
> >
> >     2.024096  - Device release number: 0001
> >
> >     2.024099  Trying to match device
> >
> >     2.024122  Device matches
> >
> >     2.024134  failed to claim USB device: Device or resource busy
> >
> >     4.898305  detached kernel driver from USB device...
> >
> >     4.898344  nut_usb_set_altinterface: skipped
usb_set_altinterface(udev, 0)
> >
> >     9.901010  Unable to get HID descriptor (Connection timed out)
> >
> >     9.901031  HID descriptor length (method 1) -1
> >
> >     9.901037  i=0, extra[i]=09, extra[i+1]=21
> >
> >     9.901044  HID descriptor, method 2: (9 bytes) => 09 21 10 01 21
01 22 25 02
> >
> >     9.901048  HID descriptor length (method 2) 549
> >
> >     9.901052  HID descriptor length 549
> >
> >     9.901370  Unable to get Report descriptor: Broken pipe
> >
> >     9.901403  Checking device (1B1C/0A17) (002/003)
> >
> >     9.901435  Failed to open device, skipping. (Permission denied)
> >
> >     9.901441  Checking device (8087/0024) (002/002)
> >
> >     9.901448  Failed to open device, skipping. (Permission denied)
> >
> >     9.901452  Checking device (1D6B/0002) (002/001)
> >
> >     9.901462  Failed to open device, skipping. (Permission denied)
> >
> >     9.901468  Checking device (1B80/B403) (001/005)
> >
> >     9.901477  Failed to open device, skipping. (Permission denied)
> >
> >     9.901483  Checking device (18F8/0F97) (001/004)
> >
> >     9.901491  Failed to open device, skipping. (Permission denied)
> >
> >     9.901497  Checking device (048D/1345) (001/003)
> >
> >     9.901506  Failed to open device, skipping. (Permission denied)
> >
> >     9.901511  Checking device (8087/0024) (001/002)
> >
> >     9.901520  Failed to open device, skipping. (Permission denied)
> >
> >     9.901526  Checking device (1D6B/0002) (001/001)
> >
> >     9.901534  Failed to open device, skipping. (Permission denied)
> >
> >     9.901540  Checking device (1D6B/0003) (004/001)
> >
> >     9.901549  Failed to open device, skipping. (Permission denied)
> >
> >     9.901555  Checking device (1D6B/0002) (003/001)
> >
> >     9.901563  Failed to open device, skipping. (Permission denied)
> >
> >     9.901569  No appropriate HID device found
> >
> >     9.901575  No matching HID UPS found
> >
> >
> > (If I run it with -u root it tries to read my headphones and other USB
devices, but the UPS still has the same result.)
> >
> > So my problem is:
> >
> >     2.024099  Trying to match device
> >
> >     2.024122  Device matches
> >
> >     2.024134  *failed to claim USB device: Device or resource busy*
> >
> >     4.898305  detached kernel driver from USB device...
> >
> >     4.898344  nut_usb_set_altinterface: skipped
usb_set_altinterface(udev, 0)
> >
> >
> > Please could you assist me in getting the driver to load and
successfully connect?
> >
> > Many thanks,
> > Louis
>
> Had this ups, turns out the special treatment for this UPS was removed at
some point
> when it was thought that it is not needed anymore...
>
> I manually enabled the quirk with a kernel boot option
>         usbhid.quirks=0x0463:0xffff:0x08
> Append this to GRUB_CMDLINE_LINUX_DEFAULT in /boot/grub2/grub.cfg
>
> I do not have a record of the source of this advice, I found it searching
the 'net.
>
> HTH
>
> --
> Eyal Lebedinsky (eyal at eyal.emu.id.au)
>
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Eyal Lebedinsky

2020-Aug-19 13:07 UTC

head link

[Nut-upsuser] Eaton 5E 1100i USB UPS - failed to claim USB device error

On 2020-08-19 18:23, Eyal Lebedinsky wrote:> On 2020-08-19 17:36, Louis van Dyk wrote:
>> Hi
>>
>> BACKGROUND INFO:
>> I have a new Eaton 5E 1100i USB UPS which their website claims is
supported on Linux.  They don't provide software for it for Linux, only for
Windows.
>> Referring links:
>>
https://www.eaton.com/za/en-gb/catalog/backup-power-ups-surge-it-power-distribution/Eaton_5E_UPS.html
>> https://www.eaton.com/za/en-gb/skuPage.5E1100IUSB.specifications.html
>> It was manufactured in May 2020 according to the sticker on the box.
>>
>> I am running on Fedora 32 with all the latest patches.  I installed nut
and nut-client from the Fedora repository, which provides version
>> nut-2.7.4-27.fc32.x86_64
>> nut-client-2.7.4-27.fc32.x86_64
>>
>> On https://networkupstools.org/stable-hcl.html I am told that it is 5*
green "vendor provided protocol and hardware" using usbhis-ups as a
driver.
>>
>> PROBLEM:
>> 1.  The UPS is listed in "lsusb" as
>> Bus 002 Device 101: ID 0463:ffff MGE UPS Systems UPS
>> However, I notice that is disappears and reconnects every 19 seconds.
 I've seen some posts noticing this too, and stating that it stops once it
is successfully connected to the software.  I hope that is true and that I
haven't been wasting effort on a faulty device.  I have tried with my
printer's USB cable and seen the same thing.  I then tried it on my laptop
(also on Fedora 32) with the same result.  To me this eliminates my PC and the
cabling.
>>
>> 2.  The device is detected by "nut-scanner -U" as:
>>
>> root at fedora  <mailto:root at fedora>  ~]# nut-scanner -U
>>
>> Scanning USB bus.
>>
>> [nutdev1]
>>
>>     driver = "usbhid-ups"
>>
>>     port = "auto"
>>
>>     vendorid = "0463"
>>
>>     productid = "FFFF"
>>
>>     product = "5E"
>>
>>     bus = "002"
>>
>> I have put that exact info into /etc/ups/ups.conf - it's the only
info not commented with a # in the file.  I changed the name to eaton5e though.
>>
>> When I then run:
>>
>> [root at fedora  <mailto:root at fedora>  ~]#
/usr/sbin/usbhid-ups -DDDD -a eaton5e
>>
>> Network UPS Tools - Generic HID driver 0.41 (2.7.4)
>>
>> USB communication driver 0.33
>>
>>     0.000000    debug level is '4'
>>
>>     0.002054    upsdrv_initups...
>>
>>     0.017685    Checking device (0463/FFFF) (002/120)
>>
>>     2.024057    - VendorID: 0463
>>
>>     2.024080    - ProductID: ffff
>>
>>     2.024083    - Manufacturer: unknown
>>
>>     2.024087    - Product: unknown
>>
>>     2.024090    - Serial Number: unknown
>>
>>     2.024093    - Bus: 002
>>
>>     2.024096    - Device release number: 0001
>>
>>     2.024099    Trying to match device
>>
>>     2.024122    Device matches
>>
>>     2.024134    failed to claim USB device: Device or resource busy
>>
>>     4.898305    detached kernel driver from USB device...
>>
>>     4.898344    nut_usb_set_altinterface: skipped
usb_set_altinterface(udev, 0)
>>
>>     9.901010    Unable to get HID descriptor (Connection timed out)
>>
>>     9.901031    HID descriptor length (method 1) -1
>>
>>     9.901037    i=0, extra[i]=09, extra[i+1]=21
>>
>>     9.901044    HID descriptor, method 2: (9 bytes) => 09 21 10 01
21 01 22 25 02
>>
>>     9.901048    HID descriptor length (method 2) 549
>>
>>     9.901052    HID descriptor length 549
>>
>>     9.901370    Unable to get Report descriptor: Broken pipe
>>
>>     9.901403    Checking device (1B1C/0A17) (002/003)
>>
>>     9.901435    Failed to open device, skipping. (Permission denied)
>>
>>     9.901441    Checking device (8087/0024) (002/002)
>>
>>     9.901448    Failed to open device, skipping. (Permission denied)
>>
>>     9.901452    Checking device (1D6B/0002) (002/001)
>>
>>     9.901462    Failed to open device, skipping. (Permission denied)
>>
>>     9.901468    Checking device (1B80/B403) (001/005)
>>
>>     9.901477    Failed to open device, skipping. (Permission denied)
>>
>>     9.901483    Checking device (18F8/0F97) (001/004)
>>
>>     9.901491    Failed to open device, skipping. (Permission denied)
>>
>>     9.901497    Checking device (048D/1345) (001/003)
>>
>>     9.901506    Failed to open device, skipping. (Permission denied)
>>
>>     9.901511    Checking device (8087/0024) (001/002)
>>
>>     9.901520    Failed to open device, skipping. (Permission denied)
>>
>>     9.901526    Checking device (1D6B/0002) (001/001)
>>
>>     9.901534    Failed to open device, skipping. (Permission denied)
>>
>>     9.901540    Checking device (1D6B/0003) (004/001)
>>
>>     9.901549    Failed to open device, skipping. (Permission denied)
>>
>>     9.901555    Checking device (1D6B/0002) (003/001)
>>
>>     9.901563    Failed to open device, skipping. (Permission denied)
>>
>>     9.901569    No appropriate HID device found
>>
>>     9.901575    No matching HID UPS found
>>
>>
>> (If I run it with -u root it tries to read my headphones and other USB
devices, but the UPS still has the same result.)
>>
>> So my problem is:
>>
>>     2.024099    Trying to match device
>>
>>     2.024122    Device matches
>>
>>     2.024134    *failed to claim USB device: Device or resource busy*
>>
>>     4.898305    detached kernel driver from USB device...
>>
>>     4.898344    nut_usb_set_altinterface: skipped
usb_set_altinterface(udev, 0)
>>
>>
>> Please could you assist me in getting the driver to load and
successfully connect?
>>
>> Many thanks,
>> Louis
> 
> Had this ups, turns out the special treatment for this UPS was removed at
some point
> when it was thought that it is not needed anymore...
> 
> I manually enabled the quirk with a kernel boot option
>      usbhid.quirks=0x0463:0xffff:0x08
> Append this to GRUB_CMDLINE_LINUX_DEFAULT in /boot/grub2/grub.cfg
The correct file to edit is, of course, /etc/default/grub, and not
/boot/grub2/grub.cfg
where there is no GRUB_CMDLINE_LINUX_DEFAULT.

However, the other suggestion of adding a file in /etc/modprobe.d/ is the better
way
to add a module parameter without bothering with grub.
> I do not have a record of the source of this advice, I found it searching
the 'net.
> 
> HTH
-- 
Eyal Lebedinsky (eyal at eyal.emu.id.au)

Apparently Analagous Threads

Search for more maybe matching threads

Nut upsuser - Aug 2020 - Eaton 5E 1100i USB UPS - failed to claim USB device error

[Nut-upsuser] Eaton 5E 1100i USB UPS - failed to claim USB device error

[Nut-upsuser] Eaton 5E 1100i USB UPS - failed to claim USB device error

[Nut-upsuser] Eaton 5E 1100i USB UPS - failed to claim USB device error

[Nut-upsuser] Eaton 5E 1100i USB UPS - failed to claim USB device error

[Nut-upsuser] Eaton 5E 1100i USB UPS - failed to claim USB device error

Apparently Analagous Threads