[MaxW]

I have following device: D-link DWM-157 (HW B1, SW 2.0.1EU) and want/need to make it working on RHEL 6.8.

I have installed following:
USB modeswitch data 20160803, USB modeswitch 2.4.0
I ran the 'Make install' command in terminal in proper folder, and got no error msg - so I suppose all was installed fine.
I have libusb1-1.0.9.7.rc1 installed

It looks like modeswitch works somehow, as 'lsusb' command output shows 'ID 2001:7d02 D-Link Corp.'(switched from '2001:a707').
However when I open Computer from desktop, the device is shown as 'HSPA USB SCSI CD-ROM'.

I see 'segfault' in output of dmesg command (check attached file), can this be the issue?

Any idea how to solve this & make the device shown as USB 3g modem?

Thanks

PS: I am not a Linux guy, plz talk to me in simple way when hinting what to do : )

[Josh]

Hmm, if you are not very familiar with Linux, why did you choose RHEL?
Support for newer hardware is much better in end-user-oriented distributions like Fedora, Ubuntu, Mageia etc.

The mode switch worked but the modem is obviously not known to any driver.

[MaxW]

Well, I did not choose it... just have to use it.

Plz any idea if a driver for this device exist?

Thx

[LOM]

2001:7d02 was added to the usb serial driver named option in the autumn of 2013.

[Josh]

If your kernel is older than autumn 2013, see if you have the "new_id" attribute in the driver. Then you can add the ID of the modem manually. You'd have to do that once after every reboot.

Code: Select all

# modprobe -v option
# echo "2001 7d02" >/sys/bus/usb-serial/drivers/option1/new_id

[MaxW]

Well, still not solved.

If I did not miss something RHEL kernel 6.8 is from May 2015....

I have set logging and here is the output. Looks like some files are missing. Any idea?
(Only removed date, otherwise no modification.)

Thanks...

[Josh]

The answer is unchanged as well ...

There appears to be a crash in libusb instead of a normal error. Other than that, the switching commands went through and it's likely that your modem is in the target (useable) mode afterwards.
Check the USB ID to be sure.

If your driver does not know this USB ID, you have to tell it. This is easily possible if you have the "new_id" feature (depends on your kernel version).

If you are running kernel 2.6.32, then it was released in December 2009. No "new_id" then.

You could try a crude fall-back by loading the "usbserial" module with your USB ID as parameter. Note that kernel developers discourage this.