[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: starting X interferes with NFS



On Mon, Apr 17, 2006 at 10:01:34AM -0400, Lennart Sorensen wrote:
> On Thu, Apr 13, 2006 at 11:15:20PM -0400, hendrik@topoi.pooq.com wrote:
> > Yeah.  I've been trying to set up X on my ASUS A8N-VM-UAYGZ system.
> > Its on-board graphics chip is, I believe, an GFORCE4 6300.  This 
> > machine is successfully in production use as an NFS server, serving an 
> > 80G reiser filesystem on LVM on RAID-1 to several other machines on the 
> > LAN.
> > 
> > I'm using AMD64 etch with Len Sorenson's -12 kernel, and csail at MIT is 
> > my package repository.  I've managed to compile and install the 
> > so-called nvidia-kernel, but nvidia is not one of the options I get when 
> > running dpkg-reconfigure xserver-xorg.
> > 
> > Selecting nv gets nowhere; when I boot, X tries to start 
> > up and fails, finding no screens.  But more than that, when it starts 
> > and fails on boot,  the NFS server doesn't seem to work.  
> > remote-mounting the big partition on another machine times out.
> > 
> > Of the options I've tried, only vga works at all.  X still doesn't 
> > start (apparently I've specified 24-bit graphics and VGA doesn't like 
> > it), but at least the NFS server comes up properly, and my remote users 
> > are happy.
> > 
> > Is this a known problem?
> > 
> > Actually, I'm not completely certain whether it was nv or vesa (or 
> > both) I was using when the NFS server failed to operate -- I'd have to 
> > try it again to be sure, but it's getting late and my users are 
> > complaining about yet another shutdown.  I will test it again and give 
> > more complete details, probably tomorrow.
> > 
> > In the meantime, if someone could tell me just what data to gather to 
> > help in diagnosis, I'd appreciate it.
> > 
> > -- hendrik
> > 
> > P.S.  Does anyone know which NFS demon does proper locking *and* handles 
> > files larger than 4G?
> 
> You only get the nvidia choice after you install nvidia-glx as well.

Which, looking it up on packages.debian.org, is in stable and unstable, 
but has somehow skipped by testing.  That's why aptitude didn't find it.

> nvidia-kernel is the kernel module part.
> 
> I suspect for your particular board you require the new driver that just
> entered unstable, although you should be able to grab it and rebuild it
> for amd64 if it hasn't already been built for amd64.  Not sure if the
> x.org 7.0 transition stuff will make it not work on older versions.

Not that I have any particular aversion to xorg 7.0, but if that's 
needed it *might* be simplest to wait for it to stabilize into testing.  
I suspect that bug reports from mixing xorg7.0 into an etch system at 
this point would only confuse things, since it doesn't look as if it 
was quite ready for sid yet.

But picking up the new nvidia-glx package and seeing if it works in etch 
might still be useful as long as I can remember how to boot without X if 
it crashes hopelessly.

And it probably wants a compatibly-numbered nvidia-kernel-source.  I'll 
have to get that too.

nvidia-glx_1.0.8756-4_amd64.deb
nvidia-kernel-source_1.0.8756-4_amd64.deb

-- hendrik

> 
> Len Sorensen
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-amd64-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 



Reply to: