(temp)
>
> Right?
>
> Matt
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 05, 2002 4:12 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: [Ltsp-discuss] DHCPD option-129 again
>
>
On 05-Feb-02 Joseph Kezar wrote:
> What NIC are you using. Some ISAs need messaging before they
> work. I know I gave up on using IRQ 10 for my NE2000 NICs and
> resorted to turning off COM1+COM2 to free up IRQ 3 and 4.
> If the card has jumpers and you can change the IO, I suggest
> changing th
>Technically speaking, you could have Etherboot load Etherboot load
>Etherboot load Etherboot etc. etc. (depending on how many different
[Rest of Jason's wonderfully detailed and correct analysis snipped.]
Sigh, it's so hard to keep a nice hack secret. :-)
Etherboot loading Etherboot was orig
[EMAIL PROTECTED] wrote:
>Jason Pattie figured out how to have the older etherboot
>grab a newer etherboot from the tftp server, which in turn
>would grab the kernel and pass the options properly.
>
>it involved trickery in the dhcpd.conf file, which btw, required
>dhcpd version 3.0.
>
>I'll see
t
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 05, 2002 4:12 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: [Ltsp-discuss] DHCPD option-129 again
>
> Wouter,
>
> There ya go! That ve
Jim,
Regarding fix 1:
Your previous reply made me suspect that. I went to rom-o-matic to
download newer versions (5.0.5) of the Etherboot floppy and ROM images
for NE*000 ISA NICs.
In order to try the floppy boot first, I'll have to re-connect a
floppy drive to the terminal though. That'll be f
But for testing you would be fine just using a boot floppy (temp)
Right?
Matt
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 05, 2002 4:12 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [Ltsp-discuss] DHCPD option-129 again
Wouter,
There ya go! That version of Etherboot is too old to handle
the command line args properly.
One way to fix it is to burn new eproms with the latest
etherboot code.
Another interesting way to fix it came up yesterday
on the #ltsp IRC channel.
Jason Pattie figured out how to have the ol
Wouter,
What version of Etherboot are you using on those workstations ?
Older versions, I think before 5.0 don't handle the kernel
command line options the same way.
once it fails, try hitting Shift-PageUp and scroll backwards
through the kernel startup messages and see if you
can find the plac
Jim,
Thanks for looking into my Etherboot/DHCP problem.
I am using Etherboot/32 version 4.2.9 for [NE*000] burned into an
EEPROM.
The Kernel command line contains:
rw root=/dev/ram0 init=/linuxrc rw
but nothing about the NIC.
Wouter
On 05-Feb-02 [EMAIL PROTECTED] wrote:
> What versi
Okay,
Here comes my dhcpd.conf file.
Wouter
On 05-Feb-02 [EMAIL PROTECTED] wrote:
> Wouter,
>
> How about you send me your dhcpd.conf file, maybe i'll
> be able to see what's wrong.
>
> Jim.
Wouter DeBacker ([EMAIL PROTECTED])
05-Feb-0222:56:
Hi Wouter,
My guess is that you are using a base address and IRQ that is not the
default for the Linux ISA card driver (it searches a few pre-compiled
settings, check the driver code for your type of NIC). I would suggest that
you either supply them as kernel parameters (I'd have to check docs
Wouter,
How about you send me your dhcpd.conf file, maybe i'll
be able to see what's wrong.
Jim.
On Tue, 5 Feb 2002 [EMAIL PROTECTED] wrote:
> Jim,
>
> I've read those instructions carefully and completely even _before_
> installing SuSE. The DHCP, TFTP and NFS are running. I've triple
> che
What NIC are you using. Some ISAs need messaging before they
work. I know I gave up on using IRQ 10 for my NE2000 NICs and
resorted to turning off COM1+COM2 to free up IRQ 3 and 4.
If the card has jumpers and you can change the IO, I suggest
changing the base IO to 0x280 I have found it to have
Jim,
I've read those instructions carefully and completely even _before_
installing SuSE. The DHCP, TFTP and NFS are running. I've triple
checked. The _ddns_ entry, the definitions for option 128/129 and the
options 128/129 for each terminal are there. Instead of restarting
the DHCP manually afte
Wouter,
Sounds like a classic case of forgetting to also include
an option-128 entry.
Take a look at http://www.ltsp.org/instructions-3.0.html
Down near the bottom it explains the entries needed
in dhcpd.conf.
Jim McQuillan
[EMAIL PROTECTED]
On Tue, 5 Feb 2002 [EMAIL PROTECTED] wrote:
> Hi
16 matches
Mail list logo
