User:Agge/Updating the firmware/rev2/flasher errors
(Created page with "===Linux errors=== # If you get this error while trying to run flasher-3.5 <br /><pre>./flasher-3.5: error while loading shared libraries: libusb-0.1.so.4: cannot open shared ob…") |
m (moved Updating the firmware/rev2 flasher errors to User:Agge/Updating the firmware/rev2/flasher errors) |
Latest revision as of 00:16, 3 November 2013
[edit] Linux errors
- If you get this error while trying to run flasher-3.5
./flasher-3.5: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
you are probably on 64 bit and you need to install a libusb compatibility package. For example, on openSUSE 11.4 you just runzypper in libusb-0_1-4-32bit
On a debian based system you can download and install the 32-bit version in a separate location (don't install it on your system itself -- note: installing libusb0.1-4 from repos on ubuntu 12.10-amd64 worked fine for one user)
First download the libusb-0.1-4_0.1.12-13_i386.deb library (google is your friend) and then:dpkg-deb -c libusb-0.1-4_0.1.12-13_i386.deb
sudo dpkg -x libusb-0.1-4_0.1.12-13_i386.deb libusb-0.1-4_0.1.12-13_i386
sudo mv libusb-0.1-4_0.1.12-13_i386/lib/* /lib32
cd /usr/lib32
sudo ln -s /lib32/libusb-0.1.so.4
Now Set the library path (as su):sudo su
export LD_LIBRARY_PATH=/usr/lib32/:"$LD_LIBRARY_PATH"
Now you can run the flasher application (as su)
- basically all recent linux distros come with kernel module cdc_phonet. The problem is that the kernel module cdc_phonet that is automatically loaded and that disrupts the connection from flasher via USB to device. The solution is to temporarily (or even permanently, since it's a largely useless module) blacklist it, until you are done flashing. On openSUSE this can be done by creating a file like this:
echo "blacklist cdc_phonet" >/etc/modprobe.d/00-blacklist-cdcphonet.conf
When you finish flashing, remove the file 00-blacklist-cdcphonet.conf to revert back to normal - or just keep it this way, you probably won't miss cdc_phonet ever.
There are other, probably timing, reasons causing occasional "unable to enumerate USB". Immediately issue the flasher command again, up-arrow usually helps fetching last command to re-issue it.
- This page was last modified on 3 November 2013, at 00:16.
- This page has been accessed 1,974 times.