From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux@cthulhu.engr.sgi.com
Subject: Problems booting Indigo...
Date: Tue, 30 May 2000 03:29:58 +0200 [thread overview]
Message-ID: <20000530032958.D15930@lug-owl.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2801 bytes --]
Hi!
I've now build a kernel which I would like to test on my Indigo;) The
problem is that I can't load it;( I tried bootpd as well as ISC dhcpd.
The result is actually just the same:
>> bootp()parkautomat:/tftpboot/vmlinux.ip12
No server for parkautomat:/tftpboot/vmlinux.ip12
I tried to do with "parkautomat:", with IPs ("192.168.1.4:"), I leaved
the server totally off the string, I used bootpd and dhcps with rfc1048,
with cmu (bootpd), I checked the "SQE dip switch" at the AUI->10baseT
transceiver. setenv/unsetenv netaddr didn't make a difference, too...
I checked dozends of combinations, but there's no server seen by the
Indigo;(
/etc/bootptab:
ip12:\
:ht=ethernet:\
:ha=08006906ba2e:\
:bs=auto:\
:vm=cmu:\
:ip=192.168.1.3:\
:sm=255.255.255.0:\
:sa=192.168.1.4:\
:bf=vmlinux.ip12:\
:to=7200:
tcpdump shows:
[root@parkautomat:/root] #> tcpdump -i eth0 -n
tcpdump: listening on eth0
01:46:03.979150 arp who-has 192.168.1.3 tell 192.168.1.3
01:46:03.979864 192.168.1.3.68 > 255.255.255.255.67: xid:0xa0d5 secs:5 C:192.168.1.3 [|bootp]
01:46:03.982352 192.168.1.4.67 > 255.255.255.255.68: xid:0xa0d5 secs:5 C:192.168.1.3 Y:192.168.1.3 S:192.168.1.4 [|bootp] [tos 0x10]
01:46:08.408974 192.168.1.3.68 > 255.255.255.255.67: xid:0xa0d5 secs:10 C:192.168.1.3 [|bootp]
01:46:08.411526 192.168.1.4.67 > 255.255.255.255.68: xid:0xa0d5 secs:10 C:192.168.1.3 Y:192.168.1.3 S:192.168.1.4 [|bootp] [tos 0x10]
01:46:13.408851 192.168.1.3.68 > 255.255.255.255.67: xid:0xa0d5 secs:15 C:192.168.1.3 [|bootp]
01:46:13.411166 192.168.1.4.67 > 255.255.255.255.68: xid:0xa0d5 secs:15 C:192.168.1.3 Y:192.168.1.3 S:192.168.1.4 [|bootp] [tos 0x10]
01:46:18.408664 192.168.1.3.68 > 255.255.255.255.67: xid:0xa0d5 secs:20 C:192.168.1.3 [|bootp]
01:46:18.411001 192.168.1.4.67 > 255.255.255.255.68: xid:0xa0d5 secs:20 C:192.168.1.3 Y:192.168.1.3 S:192.168.1.4 [|bootp] [tos 0x10]
So there are four requests, four replys, but none of them seems to be
seen;( Can anybody tell me how to boot the kernel? The "Diskless
Workstation Administration Guide" didn't help a lot... Maybe I can
(if nothing else helps...) boot the kernel through the tape? If so,
how di I have to put the kernel onto the tape? How to load it off?
MfG, JBG
PS: Hacking the kernel was done in one evening, trying to boot it costed
dome days...
--
Fehler eingestehen, Größe zeigen: Nehmt die Rechtschreibreform zurück!!!
/* Jan-Benedict Glaw <jbglaw@lug-owl.de> -- +49-177-5601720 */
keyID=0x8399E1BB fingerprint=250D 3BCF 7127 0D8C A444 A961 1DBD 5E75 8399 E1BB
"insmod vi.o and there we go..." (Alexander Viro on linux-kernel)
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next reply other threads:[~2000-05-30 1:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-30 1:29 Jan-Benedict Glaw [this message]
2000-05-30 7:46 ` Problems booting Indigo Richard van den Berg
2000-05-30 14:36 ` J. Scott Kasten
2000-05-30 22:11 ` Jan-Benedict Glaw
2000-05-31 0:12 ` Chris Ruvolo
2000-05-31 4:10 ` William Fisher
2000-05-31 4:10 ` William Fisher
2000-05-31 8:23 ` Chris Ruvolo
2000-05-31 10:25 ` Jan-Benedict Glaw
2000-06-05 14:29 ` Florian Lohoff
2000-06-06 12:30 ` Jan-Benedict Glaw
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20000530032958.D15930@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux@cthulhu.engr.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox