While trying to solve the “Connection Refused” error I crashed my Ubuntu system. Suggestions invited.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

While trying to solve the “Connection Refused” error I crashed my Ubuntu system. Suggestions invited.

686 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by GBTech on Wed May 21 12:58:54 MST 2014
I  installed  LPCXpresso 7.1.1 and was able to get it running on Ubuntu 12.04 (32 bit system) but could never connect to the LPC Link2 debug probe correctly. I kept getting "Connection Refused".  I spent days searching the lpcware.com website and trying the different suggestions offered.

At some point I tried: "sudo ln -sf linudev.so.1 libudev.so.0"  The instructions on the website were unclear as to whether that was to be used only on 64 bit systems, or on all Ubuntu systems. The way the text was structured, it looked like it applied only to 64 bit computers, but LXPXpresso-support directed people with 32bit systems to that page, so, having spent many hours trying everything else I could find, I tried that.

Ever since then, I have been unable to boot into my primary Ubuntu partition which I have been using for the last two years. I keep getting the error: "libudev.so.0: cannot open shared object file: No such file or directory."

(Fortunately, a few weeks ago I installed Kubuntu on a different partition to see what it is like. I am using that now.)

I am currently unable to resolve this problem. I would be PROFOUNDLY GRATEFUL if someone offered a suggestion that helped me solve this problem. ;-)

Thank you.
0 Kudos
Reply
1 Reply

676 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by starblue on Thu May 22 01:04:34 MST 2014
1. Mount the Ubuntu file system under your Kubuntu and remove the link. (If you really used linudev.so.1 instead of libudev.so.1 the problem may be that it points nowhere.) If you hadn't the Kubuntu you could use any Linux Live system from a disk or stick.

2. If that fails to resolve the problem then try to reinstall udev from your Ubuntu installation disk, there should be some rescue mode.

Note that I'm just guessing from my Linux experience with other systems (mostly Debian), so your mileage may vary.
0 Kudos
Reply