On Fri, 06 Oct 2006 09:15:53 -0500
Petre Scheie <[EMAIL PROTECTED]> wrote:
>
> I've got Pentium-1 machines, up to about 200mhz, with PCI slots, with
> the old 5-pin DIN AT-style connectors. They're not that rare.
>
> Petre
>
I just want to second that... One of my current clients is a 133mh
Thanks Jim and Jeremy,
The 2.6.16 one worked with the Neoware e140, and still supported the
T42p Thinkpad as well. The 2.6.17.3 and .8 did not work with the
Neoware VIA Rhine II NIC.
- Original Message -
From: Jim McQuillan <[EMAIL PROTECTED]>
Date: Friday, October 6, 2006 1:26 pm
Subj
Thanks Jim,
I was unaware of that process. Pretty slick to have an online update
for LTSP.
My NIC is a VIA Rhine II.
- Original Message -
From: Jim McQuillan <[EMAIL PROTECTED]>
Date: Friday, October 6, 2006 1:26 pm
Subject: Re: [Ltsp-discuss] dhcpcd failed issue
To: ltsp-discuss@list
Fred,
I recommend starting out by updating your LTSP installation.
Using ltspadmin, you can install the latest updates. You just need to
point ltspadmin to the main ltsp repositories.
That would be:
http://ltsp.mirrors.tds.net/pub/ltsp/ltsp-4.2/
It should show several packages that need to
Fred, does your Neoware happen to have a Via Rhine II NIC? Which kernel
version are you using?
I ran into problems with a Neoware e90 and the above NIC. I researched the
kernel bug archives rather thoroughly, and discovered that they've been
tweaking with the settings on these particular types o
Thanks John,
I may have my terms wrong. I set the bios on the Neoware to enable the
bootrom. It starts writing to the black screen just like my other
non-Neoware PCs that work. It sends a dhcp request. THe server gives an
IP, then the server does three tries of DHCPDISCOVER/OFFER with no
succes
Thanks Joe,
I was considering building my own kernel. Have seen others here suffer
with that process. When I downloaded the kernel kit, there was no readme
or doc.
Where is the process of building a LTSP kernel for a NIC card documented
to the point where a person that has never built a kernel ca
Gavin Chester wrote:
> On Thu, 2006-10-05 at 21:54 -0400, Jim McQuillan wrote:
>> Wilson A. Galafassi Jr. wrote:
>>> Hello.
>>>
>>> I have some old machines with motherboard with DIMM (big connector)
>>>
>> That should be 'DIN' connector.
>>
>>> keyboard. What is necessary to change in the con
I may be wrong, but the mention of "PCI" leads me to suspect that the PCI LAN
boot means that it will use a bootrom on the PCI LAN NIC. Is there such a ROM
on your hardware? If not, then that would be consistant with your surmise
that there is no NIC driver, but unfortunately that would mean you
A new kernel will solve the problem if your driver has been built into
it. That is often the case with new hardware, but it depends on how
new. Building it in yourself is the most comprehensive solution.
[EMAIL PROTECTED] wrote:
>Sorry if this is a duplicate, I was haveing "suspicious header
Sorry if this is a duplicate, I was haveing "suspicious header" problems.
Hi, thanks to those who helped me realize my Neoware client was not
really functioning as an LTSP client. I now have it set to do PCI LAN
boot, but I am getting the "dhcpcd failed - kernel panic message at
boot. I have re
I am having a similar experience, i.e. local storage "almost" works. In my
case I am using K12LTSP v5 with LTSP v4.2u4 and all updates. I have two
servers under test: the first one named "ltsp" is a virtual machine running
under VMWare Server, the second machine named "Genesis" is an HP ProLiant
Fredag 06 oktober 2006 15:04 skrev Jim McQuillan:
..see below..
> Verner,
>
> What's in your ~/.lbussd.out file? Might be some clues to the problem.
>
> Also, try modifying your lubs-start.sh script from:
>
> exec /usr/sbin/lbussd > ${HOME}/.lbussd.out &
>
> To:
>
> exec /usr/sbin/lbussd > $
Andrew Ziem wrote:
> Bob Mariotti wrote:
>> Gentlemen;
>>
>> I've new to ltsp. The new shop where I'm now employed uses it to serve
>> approx 50 thin-clients with the server running RHES3.
>>
>> We are currently evaluating VMware ESX 3.x and plan on installing ubuntu
>> 6.06 with ltsp installe
Verner,
What's in your ~/.lbussd.out file? Might be some clues to the problem.
Also, try modifying your lubs-start.sh script from:
exec /usr/sbin/lbussd > ${HOME}/.lbussd.out &
To:
exec /usr/sbin/lbussd > ${HOME}/.lbussd.out 2>&1 &
That might catch more errors, if the script is indeed ha
Fredag 06 oktober 2006 13:41 skrev Jim McQuillan:
A little more info below...
> Verner Kjærsgaard wrote:
> > Hi again,
> >
> > - we've narrowed the problems with no icons popping up when inserting a
> > USB stick down to the wikis troubleshooting section 8...Is lbussd
> > running?
> >
> > It isn'
Fredag 06 oktober 2006 13:41 skrev Jim McQuillan:
> Verner Kjærsgaard wrote:
> > Hi again,
> >
> > - we've narrowed the problems with no icons popping up when inserting a
> > USB stick down to the wikis troubleshooting section 8...Is lbussd
> > running?
> >
> > It isn't.
> >
> > But the startup scr
Verner Kjærsgaard wrote:
> Hi again,
>
> - we've narrowed the problems with no icons popping up when inserting a USB
> stick down to the wikis troubleshooting section 8...Is lbussd running?
>
> It isn't.
>
> But the startup script is being run when the user logs in. We've checked that
> by addi
Hi again,
- we've narrowed the problems with no icons popping up when inserting a USB
stick down to the wikis troubleshooting section 8...Is lbussd running?
It isn't.
But the startup script is being run when the user logs in. We've checked that
by adding a small line that writes to a log file
Hi list,
- We're strugling to get Local Device Access to work on SUSE9.2
- When we insert a USB stick, we get no icon.
- this is the (error ?) output logged in the users home dir..
[EMAIL PROTECTED]:~> cat .lbussd.out
fifo opened, fd: 4
Sending: Register
Sending: EnumerateDevices
Starting the l
On Thu, 2006-10-05 at 21:54 -0400, Jim McQuillan wrote:
>
> Wilson A. Galafassi Jr. wrote:
> > Hello.
> >
> > I have some old machines with motherboard with DIMM (big connector)
> >
>
> That should be 'DIN' connector.
>
> > keyboard. What is necessary to change in the configuration to this ke
Verner Kjærsgaard wrote:
> Torsdag 05 oktober 2006 19:37 skrev Gudmund Areskoug:
>> Verner Kjærsgaard wrote:
>>> As usual, any hint is greatly appreciated!
>> just a shot in the dark: what lib's etc. (versions) are needed for
>> compilation, and which ones do you have in SuSE 9.1? Perhaps going wit
I've got mine to work too, although some of them refuse to work
(compaq' here)
This are my working settings:
lts.conf
[Default]
XRAMPERC = 100
USE_NBD_SWAP = Y
ALLOW_PROCREAD = Y
X_VIDEORAM = 4096
X_COLOR_DEPTH = 24
X_MODE_0 = 1024x768
23 matches
Mail list logo
