[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1107361: linux-image-6.1.0-37-amd64: Owon VDS1022I usb oscilloscope stops working with this kernel version

Hi Salvatore,
    That is correct. We can close this bug-report. There isn't much that can be done at the kernel level which can be used as an OS default. Hopefully these bug reports would redirect other users of this device to the workaround that they can apply themselves.
    Normally the VID is meant to be unique to a manufacturer (Owon for e.g.) and the PID should be unique to a product. In this case Owon was using the same PID for multiple products causing compatibility issues. 

regards,

Amit

On 07/06/25 12:48, Salvatore Bonaccorso wrote:

Control: tags -1 + moreinfo

Hi,

On Fri, Jun 06, 2025 at 05:35:26PM +0530, amith wrote:

Package: src:linux
Version: 6.1.140-1
Severity: important
Tags: upstream
X-Debbugs-Cc: lestoppe@gmail.com

Dear Maintainer,

         My Owon VDS1022I USB oscilloscope stopped working with it's user
software after upgrading the Debian linux kernel from 6.1.0.34-amd64 to
6.1.0.37-amd64.

         On debug, it was found that this is because upstream had added the VID
and PID for this device to the usb_serial_simple.c device driver. The intent
was to support a different Owon device HDS200 which had the same VID and PID.

         Currently my USB oscilloscope is unusable unless I force unload or
blacklist usb_serial_simple. It would be better if this work around is not
needed because new users of this device may not be aware of this and assume by
default that the device is unusable on Linux. I only debugged it because it
worked without issues in the older kernels.

         I have filed the kernel bugzilla report :
https://bugzilla.kernel.org/show_bug.cgi?id=220193 and also emailed the
maintainers for advice.

         There is also a Debian forums posts on this topic :
https://forums.debian.net/viewtopic.php?t=162942

My understanding of Greg's reply in
https://lore.kernel.org/all/2025060620-twister-starved-3fb8@gregkh/ is
htat this is not a kernel issue but the devices vendors did not follow
the rules on assigning the ids?

If this interpretation is correct then I do not see something on our
end which needs to be changed.

Can you confirm?

Regards,
Salvatore
Reply to: