Linux (Ubuntu 14.04) won't recognize OS

This topic has 5 replies, 3 voices, and was last updated 9 years, 9 months ago by Ray.

Viewing 6 posts - 1 through 6 (of 6 total)

Author

Posts
March 25, 2015 at 8:32 pm #36271

creeble
Participant

Whenever I connect OS to my Linux box in boot mode, I get the following in dmesg:

[ 1158.908082] usb 2-5: new low-speed USB device number 11 using ohci_hcd
[ 1159.088082] usb 2-5: device descriptor read/64, error -62
[ 1159.372034] usb 2-5: device descriptor read/64, error -62
[ 1159.652044] usb 2-5: new low-speed USB device number 12 using ohci_hcd
[ 1160.060035] usb 2-5: device not accepting address 12, error -62
[ 1160.236078] usb 2-5: new low-speed USB device number 13 using ohci_hcd
[ 1160.644040] usb 2-5: device not accepting address 13, error -62
[ 1160.644070] hub 2-0:1.0: unable to enumerate USB device on port 5
and lsusb doesn’t find anything. I’ve tried multiple ports, external hubs, even another Linux machine (Mint 17), and I always get the “unable to enumerate USB device” message.

Is my OS broken?

March 26, 2015 at 11:42 pm #36288

Samer
Keymaster

Hi, If you have a OpenSprinkler 2.1, then you need to be in bootloader mode for the device to be recognized.

Do you know which hardware version you have?

March 26, 2015 at 11:53 pm #36289

creeble
Participant

Hardware 2.1. I am in bootloader mode. Plugging it in (while holding down B2) causes that listing in dmesg.

March 27, 2015 at 2:16 am #36301

Ray
Keymaster

Make sure that you don’t press the button B2 for too long after inserting the USB cable. Release it within a second or two after inserting the USB cable. The LCD screen should remain off — if not, that means the device is not in bootloading mode.

March 27, 2015 at 2:14 pm #36312

creeble
Participant

Okay, I now have the device recognized in Linux — if I hold down B2 for just the right length of time, I get:

[152334.596046] usb 2-5: new low-speed USB device number 16 using ohci_hcd
in dmesg. But when I run osFWUpdater_x64 (after installing some half-gig of Qt and putting all the correct links to libraries in /usr/lib…), it just comes up with a blank window, no controls. I’ve run it both as regular user and as root, no difference.

Moving back to my Win7 laptop and holding the button for just the right length of time, I was able to use the Zadig driver installer to install the libusb driver. But when I run osFWUpdater.exe, I get an “osFWUpdater.exe has stopped working” message, with the following Problem Signature:

Problem signature:
Problem Event Name:    APPCRASH
Application Name:    osFWUpdater.exe
Application Version:    0.0.0.0
Application Timestamp:    00020020
Fault Module Name:    osFWUpdater.exe
Fault Module Version:    0.0.0.0
Fault Module Timestamp:    00020020
Exception Code:    c0000005
Exception Offset:    00002254
OS Version:    6.1.7601.2.1.0.768.3
Locale ID:    1033
Additional Information 1:    0a9e
Additional Information 2:    0a9e372d3b4ad19135b953a78882e789
Additional Information 3:    0a9e
Additional Information 4:    0a9e372d3b4ad19135b953a78882e789

I distinctly remember seeing the Windows version of this program running sometime before installing the libusb driver (but of course it wouldn’t find the OS), so I have no idea why it’s failing to run now.

March 29, 2015 at 11:44 am #36374

Ray
Keymaster

To be sure: you need to unzip the whole package to a local folder, like your Desktop. DO NOT double click on the executable while it’s still in the zip file — Windows makes it look like it’s a folder but it’s still in the zip file. You need to explicitly ‘Extract’ or ‘Unzip’ the zip file first.
Author

Posts

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.