The lines:
[xdmcp]
Enable=true
ARE in the gdm.conf.
>Do you have your client listed in /etc/hosts?
Yes.
Nothing in the "gray_screen" docs helps this time, to wit:
The display manager is listening and running.
The SERVER in lts.conf is correct.
iptables -L shows no rules with all tables at policy AC
I have begun to play with LTSP 4.1, but have a problem.
I'm getting the dreaded "XDMCP: Manager Unwilling Host Unwilling" deal.
In the past, I've been able to solve this, but not this time.
I have Red Hat 9, and am (trying) to use gdm.
I have no firewall.
I do have a line with an asterisk in
/etc/X
This was due to Tripp-Lite PowerAlert 6.2. It is unhappy on RH9
and will screw with the unprivileged ports needed for the MIT
Magic Cookie stuff needed for remote XDMCP.
XDM will fail, once, then work, with this same machine for this
same reason.
It's actually PowerAlert and RH9 that are fighting.
I had a dead mouse wheel in LTSP. Read the docs at xfree86.org. Logitech
needs a mouse protocol of "MouseManPlusPS/2" (!) to get the wheel working.
Made this change to lts.conf and had glory.
Had a "stuck" video resolution. Read the full installation doc at ltsp.org.
I was using the 2.x X_
I decided to try to get gdm instead of xdm working with LTSP. Not a good
idea. If you have Red Hat 9, that is.
I dropped, into /etc/sysconfig/desktop:
DISPLAYMANAGER=GNOME
and restored the original /etc/X11/prefdm line to /etc/inittab.
Made sure that the Enable=true line is in /etc/X11/gdm/g
"James Newlin" <[EMAIL PROTECTED]> writes:
>Could someone please explain why we are getting
>"fh_verify: ltsroot/dev permission failure, acc=3, error=30".
This is being issued by the X Server. Hit Ctrl-Alt-Backspace to
force the X Server to restart. You'll see this message once every
time you
From the LTSP download page, I have installed:
kernel 2.2.18
lts-core 2.08
Mach64 X server 2.0
onto RedHat 7.1. All standard pieces.
I made changes to lts.conf that should be very standard and sensible.
I have put Etherboot 5.0.3 into a 3com 3c590 card at the workstation.
There's an ATI card
Hmmm.. well, I've been fooling around with my custom kernel config,
thinking that was the most likely irregularity when:
fh_verify: ltsroot/dev permission failure, acc=3, error=30
shows up on the server's tty1 virtual terminal. Well, now I find
this little nugget on
http://www.geocrawler.com/a
I compiled parallel port support into a monolithic kernel- nope.
Next I'll try a modular kernel, but not compile anything as a module.
--
Windows: A 32 bit shell for a 16 bit operating system, originally
written for an 8 bit data bus processor by a 2 bit company that can't
stand 1 bit of competi
I discovered that, using the standard RPMS that ship with RedHat 7.0
and 7.1, that the -s option is not the only difference.
The -s option is added to server-args, but the 7.1 version of in.tftpd
requires being run as root, not nobody, or it will be launched by
the super-server, but will not bind
I've compiled a custom kernel, 2.4.9. I now get, on the server console
tty1:
fh_verify: [permission problem message] ltsroot/dev acc=3 error=30
and X is halted at the root window, xdm never shows up.
I'm using lts-core 2.08.
This looks like a capability of the kernel is needed, which I did no
11 matches
Mail list logo
