Anyone running VectorLinux?

[xilman]

Originally Posted by EdH

Thanks Paul,

Yep, that's how my inittab looked (well, similar enough, anyway - the "id:5:initdefault:" was there). I had checked that and several other things, but no joy. I just tried an install on a different 64-bit machine and all went as it was supposed to. I guess it's a hardware issue. VL isn't treating me any better on this machine. x11vnc can't find a display. So, that's two distros with some form of video trouble. I'm going to give up for now and try a different video card later.

Thanks again for the note.

Ed

Ah. I have had something similar on my CUDA machines. To get CUDA working the nouvelle driver has to be disabled. Until very recently, upgrading a kernel meant that the nvidia driver had to be reinstalled and until that had been done the X11 server would not start. Reinstalling the driver was enough for the machine to be able to go straight to the GUI. The latest nvidia driver preserves itself over kernel upgrades and that particular misfeature is no more.

It's possible that you are seeing something analogous to this behaviour.

Paul

[EdH]

The thick plottens! I pulled the video card to replace it with another and found it isn't an AGP. Apparently, it's a PCI-E. And, of course, I have no others. Oddly, though, all the PCI video cards I had, have all converted to AGP cards while lounging around in their pile.

Apparently working within the same master plan, devised by my personal tormentor, VectorLinux provides the following scenario:

All comes up correctly through an autologin of the chosen user.
All, except the auto starting of x11vnc.
At the machine, within a terminal, x11vnc runs correctly.
In a terminal, via ssh from a remote location, x11vnc can't find a display.

The end result is that I can't reboot from my remote location and expect to gain vnc access, which is not acceptable. My earlier install of VL on a different machine worked flawlessly. I only abandoned VL last time because I couldn't find a way to get zlib1g-dev into the system, which meant I couldn't compile ggnfs locally. This is still an issue, so I guess VL is out again, anyway.

Of course, it's not like there is a real limited supply of linux distros to play with, although I am looking for something that will run on "older" machinery...

Anyway, thanks for the assistance.

Ed

[paulunderwood]

Are you using the -X switch with ssh?

ssh -X your-target-host-here

[EdH]

Originally Posted by paulunderwood

Are you using the -X switch with ssh?

ssh -X your-target-host-here

That didn't do it either:

Frequently used programs:
Configuration  : vasm
File manager   : mc (press F2 for useful menu)
Editor         : mcedit, nano, vi
Multimedia     : alsamixer, play
Cannot open display "default display"

I'm not using that switch with any of my other OSs, either, because they load x11vnc at boot. But, for some reason, VL refuses to.

Thanks for the idea, though. I do appreciate any help. I will probably go back to antiX and troubleshoot the video there, since VL will still have the library issue, even if I do get vnc working correctly.

I'm going to be quite tied up for the rest of the week and probably won't even be able to put anything more into it for a day or two.

Thanks everyone.

[paulunderwood]

To get the vnc server running at boot you could try calling it from "/etc/rc.local" or whatever VL uses. If you are ambitious you can write an init.d script and start that in run level 5.

[EdH]

Originally Posted by paulunderwood

To get the vnc server running at boot you could try calling it from "/etc/rc.local" or whatever VL uses. If you are ambitious you can write an init.d script and start that in run level 5.

I can at least invoke it remotely via ssh now by using the "-auth guess" switch. The script still won't load from the user startup list. I'll have to play with it more later, but at least I have a remote solution I can work with for now. I'll look into it further when I have some more time...

Thanks to all.