Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Jakob Haufe]

On Fri, 11 Nov 2022 16:12:32 +0100
Salvatore Bonaccorso  wrote:

> Jakob, were you able to forward the patch upstream? I'm including
> Johan and linux-usb list in this reply now.

No, I originally wanted to understand the differences of the firmware
loading mechanism as I assumed a patch migrating away from the unified
firmware interface would not be accepted anyway.

Unfortunately, I never found time to do this.

Thanks for bringing this up again.

Given I have two different affected devices, I am more than happy to
test any new versions of this patch.

Cheers,
sur5r

-- 
ceterum censeo microsoftem esse delendam.


pgpOEgbiNr81k.pgp
Description: OpenPGP digital signature

Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Salvatore Bonaccorso]

Hi Jakob,

On Tue, Feb 08, 2022 at 08:03:19AM +0100, Salvatore Bonaccorso wrote:
> Hi Jakob,
> 
> On Mon, Feb 07, 2022 at 03:33:49PM +0100, Jakob Haufe wrote:
> > This still affects 5.15.0-3-amd64:
> > 
> > [624300.704569] usb 5-1: new full-speed USB device number 2 using ohci-pci
> > [624300.901723] usb 5-1: New USB device found, idVendor=06cd, 
> > idProduct=011a, bcdDevice=80.01
> > [624300.901746] usb 5-1: New USB device strings: Mfr=0, Product=0, 
> > SerialNumber=0
> > [624300.903869] keyspan 5-1:1.0: Keyspan - (without firmware) converter 
> > detected
> > [624300.904014] usb 5-1: firmware: direct-loading firmware 
> > keyspan/usa49wlc.fw
> > [624304.121517] usb 5-1: ezusb_ihex_firmware_download - ezusb_writememory 
> > failed writing internal memory (-110 7F92 b8cbdc0a 1)
> > [624304.121545] usb 5-1: failed to load firmware "keyspan/usa49wlc.fw"
> > [624304.121559] keyspan: probe of 5-1:1.0 failed with error -2
> > 
> > The patch applies with some fuzz but still solves the issue.
> > Refreshed patch is attached.
> > 
> > Has anyone already contacted upstream about this? I couldn't find
> > anything related on the linux-usb ML.
> 
> Not that I'm aware of. Given you have a tested patch, would it be
> possible that you contact upstream about it, keeping us in the loop or
> at least notify when it is applied in mainline?

Jakob, were you able to forward the patch upstream? I'm including
Johan and linux-usb list in this reply now.

Johan, fo context, it is about an older bug reported in Debian as
https://bugs.debian.org/833035 with users of the Keyspan USB serial
adapter USA-49WLC faling to load firmware.

There was a patch used, in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833035#68 tough
which hs no commit message or Signed-off-by's . Original patch is from
Ben in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833035#24 .

Regards,
Salvatore

Processed: Re: Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Debian Bug Tracking System]

Processing control commands:

> found -1 linux-5.15.15-1
Bug #833035 [src:linux] linux-image-3.16.0-4-amd64: Keyspan USB serial adapter 
USA-49WLC failed to load firmware
The source 'linux' and version 'linux-5.15.15-1' do not appear to match any 
binary packages
Marked as found in versions linux/linux-5.15.15-1.
> retitle -1 linux: Keyspan USB serial adapter USA-49WLC failed to load 
> firmware since 3.16.0-4-amd64
Bug #833035 [src:linux] linux-image-3.16.0-4-amd64: Keyspan USB serial adapter 
USA-49WLC failed to load firmware
Changed Bug title to 'linux: Keyspan USB serial adapter USA-49WLC failed to 
load firmware since 3.16.0-4-amd64' from 'linux-image-3.16.0-4-amd64: Keyspan 
USB serial adapter USA-49WLC failed to load firmware'.

-- 
833035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Diederik de Haas]

Control: found -1 linux-5.15.15-1
Control: retitle -1 linux: Keyspan USB serial adapter USA-49WLC failed to load 
firmware since 3.16.0-4-amd64

On Monday, 7 February 2022 15:33:49 CEST Jakob Haufe wrote:
> This still affects 5.15.0-3-amd64:

Updating bug metadata accordingly

> The patch applies with some fuzz but still solves the issue.
> Refreshed patch is attached.
> 
> Has anyone already contacted upstream about this? I couldn't find
> anything related on the linux-usb ML.

On Tuesday, 8 February 2022 08:03:19 CEST Salvatore Bonaccorso wrote:
> Not that I'm aware of. Given you have a tested patch, would it be
> possible that you contact upstream about it, keeping us in the loop or
> at least notify when it is applied in mainline?

I just checked current upstream master code and see the patch is not applied.

Any progress with sending the patch upstream?

signature.asc
Description: This is a digitally signed message part.

Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Salvatore Bonaccorso]

Hi Jakob,

On Mon, Feb 07, 2022 at 03:33:49PM +0100, Jakob Haufe wrote:
> This still affects 5.15.0-3-amd64:
> 
> [624300.704569] usb 5-1: new full-speed USB device number 2 using ohci-pci
> [624300.901723] usb 5-1: New USB device found, idVendor=06cd, idProduct=011a, 
> bcdDevice=80.01
> [624300.901746] usb 5-1: New USB device strings: Mfr=0, Product=0, 
> SerialNumber=0
> [624300.903869] keyspan 5-1:1.0: Keyspan - (without firmware) converter 
> detected
> [624300.904014] usb 5-1: firmware: direct-loading firmware keyspan/usa49wlc.fw
> [624304.121517] usb 5-1: ezusb_ihex_firmware_download - ezusb_writememory 
> failed writing internal memory (-110 7F92 b8cbdc0a 1)
> [624304.121545] usb 5-1: failed to load firmware "keyspan/usa49wlc.fw"
> [624304.121559] keyspan: probe of 5-1:1.0 failed with error -2
> 
> The patch applies with some fuzz but still solves the issue.
> Refreshed patch is attached.
> 
> Has anyone already contacted upstream about this? I couldn't find
> anything related on the linux-usb ML.

Not that I'm aware of. Given you have a tested patch, would it be
possible that you contact upstream about it, keeping us in the loop or
at least notify when it is applied in mainline?

Regards,
Salvatore

Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Jakob Haufe]

This still affects 5.15.0-3-amd64:

[624300.704569] usb 5-1: new full-speed USB device number 2 using ohci-pci
[624300.901723] usb 5-1: New USB device found, idVendor=06cd, idProduct=011a, 
bcdDevice=80.01
[624300.901746] usb 5-1: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
[624300.903869] keyspan 5-1:1.0: Keyspan - (without firmware) converter detected
[624300.904014] usb 5-1: firmware: direct-loading firmware keyspan/usa49wlc.fw
[624304.121517] usb 5-1: ezusb_ihex_firmware_download - ezusb_writememory 
failed writing internal memory (-110 7F92 b8cbdc0a 1)
[624304.121545] usb 5-1: failed to load firmware "keyspan/usa49wlc.fw"
[624304.121559] keyspan: probe of 5-1:1.0 failed with error -2

The patch applies with some fuzz but still solves the issue.
Refreshed patch is attached.

Has anyone already contacted upstream about this? I couldn't find
anything related on the linux-usb ML.

Cheers,
sur5r

-- 
ceterum censeo microsoftem esse delendam.
--- keyspan.c.orig	2022-02-01 15:27:35.472432892 +0100
+++ keyspan.c	2022-02-03 16:03:27.166653874 +0100
@@ -33,6 +33,8 @@
 #include 
 #include 
 #include 
+#include 
+#include 
 #include 
 #include 
 #include 
@@ -599,6 +601,19 @@
 #include "keyspan_usa67msg.h"
 
 
+static int ezusb_writememory(struct usb_device *dev, int address,
+unsigned char *data, int length, __u8 request)
+{
+if (!dev)
+return -ENODEV;
+
+return usb_control_msg_send(dev, 0, request,
+ USB_DIR_OUT | USB_TYPE_VENDOR | USB_RECIP_DEVICE,
+ address, 0, data, length, 3000, GFP_KERNEL);
+}
+
+
+
 static void keyspan_break_ctl(struct tty_struct *tty, int break_state)
 {
 	struct usb_serial_port *port = tty->driver_data;
@@ -1599,7 +1614,10 @@
 /* download the firmware to a pre-renumeration device */
 static int keyspan_fake_startup(struct usb_serial *serial)
 {
-	char	*fw_name;
+	int response;
+	const struct ihex_binrec 	*record;
+	char*fw_name;
+	const struct firmware		*fw;
 
 	dev_dbg(>dev->dev, "Keyspan startup version %04x product %04x\n",
 		le16_to_cpu(serial->dev->descriptor.bcdDevice),
@@ -1667,16 +1685,34 @@
 		return 1;
 	}
 
+	if (request_ihex_firmware(, fw_name, >dev->dev)) {
+		dev_err(>dev->dev, "Required keyspan firmware image (%s) unavailable.\n", fw_name);
+		return 1;
+	}
+
 	dev_dbg(>dev->dev, "Uploading Keyspan %s firmware.\n", fw_name);
 
-	if (ezusb_fx1_ihex_firmware_download(serial->dev, fw_name) < 0) {
-		dev_err(>dev->dev, "failed to load firmware \"%s\"\n",
-			fw_name);
-		return -ENOENT;
-	}
+		/* download the firmware image */
+	response = ezusb_fx1_set_reset(serial->dev, 1);
+
+	record = (const struct ihex_binrec *)fw->data;
 
-	/* after downloading firmware Renumeration will occur in a
-	  moment and the new device will bind to the real driver */
+	while (record) {
+		response = ezusb_writememory(serial->dev, be32_to_cpu(record->addr),
+	 (unsigned char *)record->data,
+	 be16_to_cpu(record->len), 0xa0);
+		if (response < 0) {
+			dev_err(>dev->dev, "ezusb_writememory failed for Keyspan firmware (%d %04X %p %d)\n",
+response, be32_to_cpu(record->addr),
+record->data, be16_to_cpu(record->len));
+			break;
+		}
+		record = ihex_next_binrec(record);
+	}
+	release_firmware(fw);
+		/* bring device out of reset. Renumeration will occur in a
+		   moment and the new device will bind to the real driver */
+	response = ezusb_fx1_set_reset(serial->dev, 0);
 
 	/* we don't want this device to have a driver assigned to it. */
 	return 1;


pgpMeVe1Xgrz4.pgp
Description: OpenPGP digital signature

Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Paul Fox]

salvatore wrote:
 > Control: tags -1 + moreinfo
 > 
 > Hi,
 > 
 > On Thu, Oct 19, 2017 at 05:29:41PM -0400, Paul Fox wrote:
 > > chris wrote:
 > >  > On 10/16/2017 11:32 AM, Paul Fox wrote:
 > >  > > ben, chris -- regarding this bug:
 > >  > >   Bug#833035:  linux-image-3.16.0-4-amd64:  Keyspan USB serial adapter
 > >  > >   USA-49WLC failed to load firmware
 > >  > >
 > >  > > whatever became of the proposed patch.  i'm running ubuntu 16.04.3,
 > >  > > kernel 4.4.0-97-generic, and the failure is still present there.
 > >  > >
 > >  > > paul
 > >  > > .
 > >  > >
 > >  > The patch provided fixed the bug.   I think I responded with the news.
 > > 
 > > yes -- sorry for not being clear.  i was wondering whether the fix had
 > > gone upstream, and if not, why not.
 > 
 > Has the fix been upstreamed or the issue fixed in meanwhile with a
 > recent kernel?
 > 
 > Regards,
 > Salvatore
 > 

I just dug out the device and tried it.  The bug persists in:
Linux grass 5.4.0-72-generic #80-Ubuntu SMP Mon Apr 12 17:35:00 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux

dmesg log looks much the same as those originally posted, though somewhat
different, and the returned error number (-2) is different than the -5 reported
by Chris Rhodin:
 [860822.854435] usb 2-1.8: new full-speed USB device number 5 using ehci-pci
 [860822.963452] usb 2-1.8: New USB device found, idVendor=06cd, 
idProduct=011a, bcdDevice=c0.01
 [860822.963455] usb 2-1.8: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
 [860822.963986] keyspan 2-1.8:1.0: Keyspan - (without firmware) converter 
detected
 [860822.964036] usb 2-1.8: Direct firmware load for keyspan/usa49wlc.fw failed 
with error -2
 [860822.964041] usb 2-1.8: ezusb_ihex_firmware_download - request 
"keyspan/usa49wlc.fw" failed
 [860822.965538] usb 2-1.8: failed to load firmware "keyspan/usa49wlc.fw"
 [860822.967366] keyspan: probe of 2-1.8:1.0 failed with error -2
 [860848.230938] usb 2-1.8: USB disconnect, device number 5

paul
=--
paul fox, p...@foxharp.boston.ma.us (arlington, ma, where it's 50.4 degrees)

Processed: Re: Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #833035 [src:linux] linux-image-3.16.0-4-amd64: Keyspan USB serial adapter 
USA-49WLC failed to load firmware
Added tag(s) moreinfo.

-- 
833035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

Hi,

On Thu, Oct 19, 2017 at 05:29:41PM -0400, Paul Fox wrote:
> chris wrote:
>  > On 10/16/2017 11:32 AM, Paul Fox wrote:
>  > > ben, chris -- regarding this bug:
>  > >   Bug#833035:  linux-image-3.16.0-4-amd64:  Keyspan USB serial adapter
>  > >   USA-49WLC failed to load firmware
>  > >
>  > > whatever became of the proposed patch.  i'm running ubuntu 16.04.3,
>  > > kernel 4.4.0-97-generic, and the failure is still present there.
>  > >
>  > > paul
>  > > =--
>  > >   paul fox, p...@foxharp.boston.ma.us (arlington, ma, where it's 50.2 
> degrees)
>  > >
>  > >
>  > > .
>  > >
>  > The patch provided fixed the bug.   I think I responded with the news.
> 
> yes -- sorry for not being clear.  i was wondering whether the fix had
> gone upstream, and if not, why not.

Has the fix been upstreamed or the issue fixed in meanwhile with a
recent kernel?

Regards,
Salvatore

Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Pete Kavanagh]

I take it that this never got properly sorted?

The instructions URL (
https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official)
doesn't work anymore; could someone please suggest an alternative?
I have downloaded the .patch file, but need a steer on what to do with it
please.

Thanks

Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Paul Fox]

chris wrote:
 > On 10/16/2017 11:32 AM, Paul Fox wrote:
 > > ben, chris -- regarding this bug:
 > >   Bug#833035:  linux-image-3.16.0-4-amd64:  Keyspan USB serial adapter
 > >   USA-49WLC failed to load firmware
 > >
 > > whatever became of the proposed patch.  i'm running ubuntu 16.04.3,
 > > kernel 4.4.0-97-generic, and the failure is still present there.
 > >
 > > paul
 > > =--
 > >   paul fox, p...@foxharp.boston.ma.us (arlington, ma, where it's 50.2 
 > > degrees)
 > >
 > >
 > > .
 > >
 > The patch provided fixed the bug.   I think I responded with the news.

yes -- sorry for not being clear.  i was wondering whether the fix had
gone upstream, and if not, why not.

paul
=--
paul fox, p...@foxharp.boston.ma.us (arlington, ma, where it's 61.9 degrees)

Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Chris Rhodin]

On 10/16/2017 11:32 AM, Paul Fox wrote:

ben, chris -- regarding this bug:
  Bug#833035:  linux-image-3.16.0-4-amd64:  Keyspan USB serial adapter
  USA-49WLC failed to load firmware

whatever became of the proposed patch.  i'm running ubuntu 16.04.3,
kernel 4.4.0-97-generic, and the failure is still present there.

paul
=--
  paul fox, p...@foxharp.boston.ma.us (arlington, ma, where it's 50.2 degrees)


.


The patch provided fixed the bug.  I think I responded with the news.

Chris

Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Paul Fox]

ben, chris -- regarding this bug:
 Bug#833035:  linux-image-3.16.0-4-amd64:  Keyspan USB serial adapter
 USA-49WLC failed to load firmware

whatever became of the proposed patch.  i'm running ubuntu 16.04.3,
kernel 4.4.0-97-generic, and the failure is still present there.

paul
=--
 paul fox, p...@foxharp.boston.ma.us (arlington, ma, where it's 50.2 degrees)

Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Chris Rhodin]

On 08/02/2016 16:56, Ben Hutchings wrote:

On Mon, 2016-08-01 at 22:51 -0700, Chris Rhodin wrote:
[...]

I get this from dmesg.  I'm assuming the new error -2 indicates the file
was not found.

[...]

Yes.  And the other error code (-110) indicates a time-out.

Can you test whether the attached patch fixes this?  You can do this by
following the instructions at
.

Ben.


Hi Ben,

That worked.  All four ports can now connect and communicate.  I haven't 
tested handshaking, hardware or software.


I did have to export "ezusb_writememory" from ezusb.c.


Chris

Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Ben Hutchings]

On Mon, 2016-08-01 at 22:51 -0700, Chris Rhodin wrote:
[...]
> I get this from dmesg.  I'm assuming the new error -2 indicates the file 
> was not found.
[...]

Yes.  And the other error code (-110) indicates a time-out.

Can you test whether the attached patch fixes this?  You can do this by
following the instructions at
.

Ben.

-- 

Ben Hutchings
73.46% of all statistics are made up.
--- a/drivers/usb/serial/keyspan.c
+++ b/drivers/usb/serial/keyspan.c
@@ -38,6 +38,8 @@
 #include 
 #include 
 #include 
+#include 
+#include 
 #include 
 #include 
 #include 
@@ -1165,7 +1167,10 @@
 /* download the firmware to a pre-renumeration device */
 static int keyspan_fake_startup(struct usb_serial *serial)
 {
+	int response;
+	const struct ihex_binrec 	*record;
+	char*fw_name;
+	const struct firmware		*fw;
-	char	*fw_name;
 
 	dev_dbg(>dev->dev, "Keyspan startup version %04x product %04x\n",
 		le16_to_cpu(serial->dev->descriptor.bcdDevice),
@@ -1233,16 +1238,34 @@
 		return 1;
 	}
 
+	if (request_ihex_firmware(, fw_name, >dev->dev)) {
+		dev_err(>dev->dev, "Required keyspan firmware image (%s) unavailable.\n", fw_name);
+		return 1;
+	}
+
 	dev_dbg(>dev->dev, "Uploading Keyspan %s firmware.\n", fw_name);
 
+		/* download the firmware image */
+	response = ezusb_fx1_set_reset(serial->dev, 1);
+
+	record = (const struct ihex_binrec *)fw->data;
+
+	while (record) {
+		response = ezusb_writememory(serial->dev, be32_to_cpu(record->addr),
+	 (unsigned char *)record->data,
+	 be16_to_cpu(record->len), 0xa0);
+		if (response < 0) {
+			dev_err(>dev->dev, "ezusb_writememory failed for Keyspan firmware (%d %04X %p %d)\n",
+response, be32_to_cpu(record->addr),
+record->data, be16_to_cpu(record->len));
+			break;
+		}
+		record = ihex_next_binrec(record);
-	if (ezusb_fx1_ihex_firmware_download(serial->dev, fw_name) < 0) {
-		dev_err(>dev->dev, "failed to load firmware \"%s\"\n",
-			fw_name);
-		return -ENOENT;
 	}
+	release_firmware(fw);
+		/* bring device out of reset. Renumeration will occur in a
+		   moment and the new device will bind to the real driver */
+	response = ezusb_fx1_set_reset(serial->dev, 0);
-
-	/* after downloading firmware Renumeration will occur in a
-	  moment and the new device will bind to the real driver */
 
 	/* we don't want this device to have a driver assigned to it. */
 	return 1;


signature.asc
Description: This is a digitally signed message part

Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Chris Rhodin]

On 07/31/2016 17:31, Ben Hutchings wrote:

Control: retitle -1 linux-image-3.16.0-4-amd64: Keyspan USB serial adapter 
USA-49WLC failed to load firmware
Control: tag -1 moreinfo

On Sun, 2016-07-31 at 00:16 -0700, Chris Rhodin wrote:

Subject: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-
49WLC failed to load firmware
Package: src:linux
Version: 3.16.7-ckt25-2+deb8u3
Severity: normal
Tags: upstream

Dear Maintainer,

The Keyspan USB serial adapter USA-49WLC fails to load firmware and
will not work.  This device is based on an older generation
Cypress EZ-USB FX (CY7C64613-80NC).  The firmware fails to load when
the device is attached.  While searching for an answer I found
the problem may stem from a non-standard implementation of the
firmware loading commands.  Earlier versions of the kernel
(pre-Wheezy) did work with this device.  I have tried but have been
unable to locate the change in the USB code taht causes this
failure.

[...]

Is the firmware actually installed?  (It should be
/lib/firmware/keyspan/usa49wlc.fw, I think.)  We don't distribute
firmware for this device as it's not clear that we have permission to
do so.

Ben.


The firmware is installed at:

/lib/firmware/keyspan/usa49wlc.fw

If I do the following:

1) Attach the device.

2) Use dmesg to confirm the load failure

3) Detach the device

4) Rename usa49wlc.fw to usa49wlc.fw.sav

5) Attache the device

I get this from dmesg.  I'm assuming the new error -2 indicates the file 
was not found.


[  871.336021] usb 1-4.1: new full-speed USB device number 8 using ehci-pci
[  871.428765] usb 1-4.1: New USB device found, idVendor=06cd, 
idProduct=011a
[  871.428769] usb 1-4.1: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0

[  872.496494] usbcore: registered new interface driver usbserial
[  872.496520] usbcore: registered new interface driver usbserial_generic
[  872.496539] usbserial: USB Serial support registered for generic
[  872.511885] usbcore: registered new interface driver keyspan
[  872.511909] usbserial: USB Serial support registered for Keyspan - 
(without firmware)
[  872.511931] usbserial: USB Serial support registered for Keyspan 1 
port adapter
[  872.511952] usbserial: USB Serial support registered for Keyspan 2 
port adapter
[  872.511986] usbserial: USB Serial support registered for Keyspan 4 
port adapter
[  872.512065] keyspan 1-4.1:1.0: Keyspan - (without firmware) converter 
detected
[  872.516266] usb 1-4.1: firmware: direct-loading firmware 
keyspan/usa49wlc.fw
[  875.516265] usb 1-4.1: ezusb_ihex_firmware_download - 
ezusb_writememory failed writing internal memory (-110 7F92 
c9001359d006 1)

[  875.516285] usb 1-4.1: failed to load firmware "keyspan/usa49wlc.fw"
[  875.516307] keyspan: probe of 1-4.1:1.0 failed with error -5
[  920.778513] usb 1-4.1: USB disconnect, device number 8
[  933.176024] usb 1-4.1: new full-speed USB device number 9 using ehci-pci
[  933.268765] usb 1-4.1: New USB device found, idVendor=06cd, 
idProduct=011a
[  933.268769] usb 1-4.1: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
[  933.269184] keyspan 1-4.1:1.0: Keyspan - (without firmware) converter 
detected

[  933.269247] usb 1-4.1: firmware: failed to load keyspan/usa49wlc.fw (-2)
[  933.269250] usb 1-4.1: Direct firmware load failed with error -2
[  933.269252] usb 1-4.1: Falling back to user helper
[  933.270457] usb 1-4.1: failed to load firmware "keyspan/usa49wlc.fw"
[  933.270465] keyspan: probe of 1-4.1:1.0 failed with error -5


Chris

Processed: Re: Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC 
> failed to load firmware
Bug #833035 [src:linux] (no subject)
Changed Bug title to 'linux-image-3.16.0-4-amd64: Keyspan USB serial adapter 
USA-49WLC failed to load firmware' from '(no subject)'.
> tag -1 moreinfo
Bug #833035 [src:linux] linux-image-3.16.0-4-amd64: Keyspan USB serial adapter 
USA-49WLC failed to load firmware
Added tag(s) moreinfo.

-- 
833035: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

[Ben Hutchings]

Control: retitle -1 linux-image-3.16.0-4-amd64: Keyspan USB serial adapter 
USA-49WLC failed to load firmware
Control: tag -1 moreinfo

On Sun, 2016-07-31 at 00:16 -0700, Chris Rhodin wrote:
> Subject: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-
> 49WLC failed to load firmware
> Package: src:linux
> Version: 3.16.7-ckt25-2+deb8u3
> Severity: normal
> Tags: upstream
> 
> Dear Maintainer,
> 
> The Keyspan USB serial adapter USA-49WLC fails to load firmware and
> will not work.  This device is based on an older generation
> Cypress EZ-USB FX (CY7C64613-80NC).  The firmware fails to load when
> the device is attached.  While searching for an answer I found
> the problem may stem from a non-standard implementation of the
> firmware loading commands.  Earlier versions of the kernel 
> (pre-Wheezy) did work with this device.  I have tried but have been
> unable to locate the change in the USB code taht causes this
> failure.
[...]

Is the firmware actually installed?  (It should be
/lib/firmware/keyspan/usa49wlc.fw, I think.)  We don't distribute
firmware for this device as it's not clear that we have permission to
do so.

Ben.

-- 

Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.


signature.asc
Description: This is a digitally signed message part