Hi,
Where to get vmlinuz-2.4.9-ltsp-5 kernel config file?
Anyone got bpbatch and LTSP working together?
Thanx in advance,
Andres
_
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourc
> I've been completely unable to get the screen to turn off... I've loaded up
> your version of rc.setupx and made changes to the lts.conf and still
> nothing it'll blank the screen just fine, but it won't turn off the
> light...
>
Richard,
Have you tried playing with the settings in th
Hi everyone,
We've got an LCD Monitor 17" I would like to connect to
a terminal. The terminal currently uses 1024x768 mode-line.
I can't find the settings to set this at 1280x1024 60Hz. I also
don't know what the rest of the numbers should be. The tech
at the manufacturer said they did not suppor
Having done some translations for my Palm App, I can
thoroughly recommend using
http://babelfish.altavista.com/
to do the initial heavy lifting, and then touch it
up by hand.
Cheers, Andy!
http://www.wizzy.com/owari/
On Tue, 26 Feb 2002, kwame amedodji wrote:
> Ok, i speak french a
On Tue, 26 Feb 2002, Lachlan Dunlop wrote:
> The root path for the thin client is /opt/ltsp/i386.
>
> If I run ldconfig it will update the ld.so.cache in the /etc
> directory. correct?
Do it on a convenient host, get it working there, and then
figure out how to get it to the thin client.
> >Fr
Jo,
The docs are incorrect. The proper place to put the
XF86Config.ws001 file is the /opt/ltsp/i386/etc directory.
I'm updating the docs now, and I'll post the update soon.
Thanks,
Jim McQuillan
[EMAIL PROTECTED]
On Wed, 27 Feb 2002, Jo wrote:
> On page:
> http://www.ltsp.org/documentatio
in theory, the parent of it all (the w/x/g/kdm session) should kill off all
remaining child processes when it detects the broken pipe. My server's been
pretty successful at doing so for the various incidences that have occured.
think of it as getting disconnected from a telnet session, or ssh se
One more question...
What happens on the server if one just turns off the terminal? Does the
session get cleaned up immediately or after a while. Or does it keep existing
and hogging resources?
Jo
_
Ltsp-discuss mailing list.
Hi,
I hope I'm not bothering you too much. It seems like I'm so near, so I can't
give up now. In the /etc/X11 directory of the Mandrake 8.1 installation I
performed on the box I want to turn into a terminal I found two files:
XF86Config-4 and plain XF86Config
I tried to copy both of them to /
Contact IBM and see if you can update your PXE code. It is likely that the PXE code
is BIOS-integrated so you will need the get the latest BIOS update.
Martin Herweg <[EMAIL PROTECTED]> wrote:
>
>Hi!
>
>I can successfully boot via PXE with an 3c905C-TX-M NIC
>in the Client and K12-LTSP on th
It is definitely in the opt/... tree, /tftpboot/lts/ltsroot is now
defunct ;-)
/Patrick
On Tue, 2002-02-26 at 23:59, Jo wrote:
> On page:
> http://www.ltsp.org/documentation/ltsp-3.0.0/ltsp-3.0.html#AEN672
>
> I read the following:
>
> XF86CONFIG_FILE
>
> If you want to create your own compl
On page:
http://www.ltsp.org/documentation/ltsp-3.0.0/ltsp-3.0.html#AEN672
I read the following:
XF86CONFIG_FILE
If you want to create your own complete XF86Config file you can do so and
place it in the /tftpboot/lts/ltsroot/etc directory. Then, whatever you
decide to call it needs to be ente
It connects, loads kernel,uncompresses kernel.
Installs 8390 module
installs wd driver
assigns the card
Runs dhclient..
This is where it has a problem
"NETDEV WATCHDOG: eth0: transmit timed out
NETDEV WATCHDOG: eth0: transmit timed out
NETDEV WATCHDOG: eth0: transmit timed
I'm not sure what is going on, but i386.1 is supposed
to be a backup directory. When the LTSP core package
is installed, it will look to see if there is already
an existing i386 directory. If there is, it will rename
it to i386.1, then install a new i386 directory.
if you have an empty i386 dire
Also, I've managed to hear something it's just incredibly LOUD.
So, i need to figure out the problem with the mixer...
Any ideas? :)
- Original Message -
From: "D. Clarke" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 26, 2002 11:48 AM
Subject: [Ltsp-discuss] Soun
Daniel Bodanske wrote:
> David Johnston wrote:
> > Daniel, I think Jim did it this way because at the point that you're
> > installing ltsp_core, the ltsp kernels haven't been installed yet. This
> > means that when /etc/dhcpd.tmpl is created, there's no way to know what
> > the kernel entry need
Ok, i speak french and i'll happy to help you!
Do you mind explain me how may i process...
Kwame
--- David Johnston <[EMAIL PROTECTED]> a écrit : >
The translations group needs volunteers to help with
> the French version
> of the documentation. We had a couple of volunteers
> that had to bow
I've got swarms of those cards too!!
I know I have them working with Version 2.08 of LTSP and I'm pretty sure I
had them working with 3 a month or so ago when I was testing.
What have you got so far?
Were do they stop?
Errors?
Dhcpd.conf samples
Matt
-Original Message-
From: Dave Th
Ok, I'm dealing with some old hardware here so be nice ;)
the main problem is aumix-minimal -v65 (or any value) returns:
aumix: no device found
I've tried specifying /dev/sound/mixer and /dev/mixer with the -d option,
but neither of them make a difference.
The drivers are loaded, it's an old so
Hello Andy.
The below steps you show are the steps I followed.
The root path for the thin client is /opt/ltsp/i386.
If I run ldconfig it will update the ld.so.cache in the /etc directory. correct?
>From what I gather the ld.so.cache the thin client uses is the
/opt/ltsp/i386/etc/ld.so.cache.
Hi all,
We are preparing a demo of LTSP for the local school district to utilize the
masses of 486 machines they have kicking around. All these machines seem to
have Smc 8000 nic cards which use the wd driver, which I cannot get to work.
I have changed the card to 3com's and have no problems
A useful tool :- ldd
[root@armada lib]# ldd /bin/sh
libtermcap.so.2 => /lib/libtermcap.so.2 (0x40021000)
libdl.so.2 => /lib/libdl.so.2 (0x40025000)
libc.so.6 => /lib/i686/libc.so.6 (0x40029000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000)
It lists the lib
Hello again,
I have got a little further into my problem.
I have a small text based application that uses a library I don't have the
source for. This application relys on the libc5 shared libraries.
I have tried linking the application against libc6. THe application
starts up and then segfaul
Hi!
I can successfully boot via PXE with an 3c905C-TX-M NIC
in the Client and K12-LTSP on the Server.
Then I tried an IBM PC300PL with on-board NIC.
In the BIOS Menu I had the choice between
DHCP and RPL
with RPL nothing happens, the Client tries to boot from Floppy
with DHCP I get the messa
Hi,
we use LTSP with our own kernel+initrd, compiled with the initrd-kit.
For two types of clients this works fine, but with two other types we
have the following problem:
The kernel boots and loads the ramdisk. Linuxrc is running ok until
doing the pivot_root. After this all commands stop with:
> Daniel, I think Jim did it this way because at the point that you're
> installing ltsp_core, the ltsp kernels haven't been installed yet. This
> means that when /etc/dhcpd.tmpl is created, there's no way to know what
> the kernel entry needs to be.
>
> -David
David,
You're right, of course, and
Darryl Bond wrote:
>
> I use the IGEL terminals as LTSP terminals. The LTSP3 kernel will not boot on
> some of the models but I haven't got to the bottom of why yet (I haven't
> actually spent any time finding out why). I must say that I have spent more time
> getting IGELs to work properly than
27 matches
Mail list logo
