execv(clasicladder): No such file or directory

Thanks for finding that!

I will look into the graphics issue.

I had an interesting problem related to graphics in the beginning with Linux thinking there were two monitors so I made an edit to a startup file somewhere to specify the monitors. I hope it isn't related to that, I am so relieved to have that working.
Before I made the edit, the screen only showed the background because it was recognized as the 2nd screen.

schmidtmotorworks wrote:

Yes I just finished that (there were about 100 of them), thanks a lot, that is great progress.



So far I can't find anything useful about the classic ladder message.

according to the error message...you _still_ haven't fixed the spelling of classicladder on line 95

Chris M

cmorley,

Has the correct spelling of classicladder changed?

I didn't change that in the hal file; it is the same way it was in the previous install.

I don't know what to change.

note classicladder in your HAL file line 95 has only one s in it. classicladder has two s in it.
that would be why it cant find the file.
Try spelling it properly and see if it gets past that error.

No the name has never changed.

Chris M

Thanks for noticing that, I hope I can get back to it but I am afraid that I may have made a mistake that I might not be able to recover from.

While trying to follow the instructions to possibly resolve a graphics issue I made a mess of xorg.conf.

I edited it to use the vese driver then restarted the computer.

Next is starts in terminal mode.

So I navigate to xorg.conf and try to edit it with vi.

I did something wrong, now it is named xorg.conf~

Now when I restart it, it never goes to terminal mode at all. just black screen forever.
So I start with F2 recovery mode that gets me to a strange linux background with no usable tools
I try restarting with F2 again, every time seems to get a different result
This time it gets to a menu that gets me to a terminal mode with very big text.

Now I can get to the folder again and try vi.
there is no xorg.conf, but the xorg.conf~ is still there

I have tried to recover it and I can get an option to open a version in vi that looks like what I want to go back to.

The problem now is, I have not been able to write it.

Every combination I try with different combinations of login, owner returns "read only file system"

Every attempt I make to chmod also returns "read only file system" (including using sudo.

I am not expert at LINUX so I am looking up the commands on Google, every time I think I may have found the key I find the same problem "read only file system".

Is there any way I can get past this, or have I bricked the drive?

I found a way to fix the xorg.conf file issue (I think)

I connected the problem drive and a working linux drive to a PC
Booted to the working linux drive
Then edited the the xorg.conf files in the problem linux drive.

I find myself with a strange situation now.

When I start the drive it comes to a login page (it didn't do that before)
When I log in it takes me to a desktop with no icons
It has a sort of menu at the upper left "activities" but it is useless.
There are controls to adjust volume and turn off the computer, I can't seem to do anything else.

It seems that I have made a mess of this.

For now I have decided to postpone going to Mint, and went back to my previous version.

I checked the hal file and found that it does have classic ladder spelled incorrectly.
It is interesting that no problem messages are raised by this.

If I fix the spelling, it causes a second dialog that looks like it is used to develop the ladder code.
This is good to know because i have been wanting to learn classic ladder to get the tool-changer working.

Another interesting thing that I found in regards to the classic ladder spelling; an error message will be raised for it when certain other problems are found. I discovered this when I still had the incorrect spelling and was trying to connect a 4th and 5th axis.

For now, i am going to work on getting the 4th and 5th axis working and take another try at Mint later,

Thanks to everyone that helped on the problem.