Difficulty with netbooting - le0: lost carrier when bringing down the netbsd kernel
Mike Begley <[email protected]> Mon, 22 Dec 2025 00:48:05 +0000
| Newsgroups | gmane.os.netbsd.ports.hp300 |
|---|---|
| Message-ID | <CO1PR18MB4826A4D76FB35436D148789DACB4A@CO1PR18MB4826.namprd18.prod.outlook.com> |
--_000_CO1PR18MB4826A4D76FB35436D148789DACB4ACO1PR18MB4826namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi folks!
For literally the first time in at least a couple decades, I'm trying to po=
wer up and play with my 9000/362 (I think that would be the designation bas=
ed on what I have). Because I don't have an existing system to bootstrap a=
n OS onto a disk with, I'm trying the netboot route. Plus, it seemed like =
an interesting exercise I haven't done since the early 2000s.
I tried following the instructions here: https://www.netbsd.org/docs/networ=
k/netboot/intro.hp300.html - specifically the steps listed at the bottom (r=
bootd, rarpd, etc). I successfully followed those instructions many years =
ago but I think that SYS_UBOOT has changed enough that they are well out of=
date.
TL;DR: I'm getting an le0: lot carrier when it's trying to bring down the k=
ernel.
---
A bit of hardware background. My machine has the thinnet NIC on the System=
Interface board, and an AUI interface in the expansion chassis. Because i=
mmediate access to AUI networking was a little easier (just grab a tranceiv=
er and I'm ready to go), I decided to use the AUI. I switched the select c=
odes on both ethernet devices so that the AUI had the lowest number (not su=
re if this is necessary). Time to start the netboot setup.
rbootd installation went smoothly enough. After the hp was turned on, a l=
ittle while later both the rbootd debug output & the behavior on the hp con=
sole indicated success.
rarpd was where the success stopped. I never got a rarp request. At this =
point I turned to my favorite overeager coding buddy, chatGPT for assistanc=
e, and surprisingly, it had some good info.
Main useful observation: the console message was saying that the SYS_UBOOT =
bootstrapper was using bootp, and that rarpd was no longer in use. Interes=
ting (if true). Time to switch to a bootp process. Rather than suggesting=
traditional bootp, my little coding buddy suggested I try something calle=
d dnsmasq as a more modern alternative. Sure, let's try that out.
I download and configure dnsmasq. This took a bit of poking, but I eventua=
lly got it set up in a way that seemed sane. On the 300, the bootstrap wou=
ld start up, and then start asking for a variety of kernels (netbsd, netbsd=
.gz, etc) but never actually got any data. It just loops over and over thr=
ough the series of kernel names. Using tcpdump on the tftp port, I see no =
requests from the hp. Coding buddy suggests that the SYS_UBOOT might insis=
t on using the thinnet NIC, regardless of Select Code or how it brought dow=
n the bootstrap. At that point I break for the night.
This morning, I dug up some thinnet hardware & cabling, and switched everyt=
hing over to use that NIC. Now, I actually see requests for a kernel showi=
ng up in the dnsmasq logs:
dnsmasq-dhcp: 326617420 bootfile name: netbsd
dnsmasq-dhcp: 326617420 next server: 192.168.2.227
dnsmasq-dhcp: 326617420 sent size: 1 option: 53 message-type 5
dnsmasq-dhcp: 326617420 sent size: 4 option: 54 server-identifier 192.168.2=
.227
dnsmasq-dhcp: 326617420 sent size: 4 option: 1 netmask 255.255.0.0
dnsmasq-dhcp: 326617420 sent size: 4 option: 28 broadcast 192.168.255.255
dnsmasq-dhcp: 326617420 sent size: 4 option: 3 router 192.168.1.1
and on the HP console I just see a sequence of errors:
le0: lost carrier
le0: lost carrier
le0: lost carrier
le0: lost carrier
bootp: no reply
boot: client IP address: 0.0.0.0
root: addr=3D0.0.0.0 path=3D
le0: lost carrier
le0: lost carrier
le0: lost carrier
le0: lost carrier
arpwhohas: no response for 0.0.0.0
And that's where I'm stuck. I suspect those messages indicate physical lev=
el errors; e.g. the onboard bnc wiring, 10baseT hub I'm using that has a 10=
base2 connector on it is faulty, or more likely, the rg58 cabling/tees/term=
inators have decayed or oxidized over the decades and are no longer reliabl=
e. I'm perhaps a little surprised that it's so reliably unreliable, but ma=
ybe that's the difference between bootp and a protocol that requires a sust=
ained carrier running on marginal cabling.
Any insight or ideas would be appreciated! I feel like I'm really close an=
d I'd like to push past this. In particular:
- Ideas on what I might be doing wrong? I know I'm straying from the stand=
ard path, but out of what seems like necessity. I could try to go back to =
traditional bootp, but that doesn't seem like it would make a difference. =
It's the tftp part that's failing.
- Ideas on how to do this all over the AUI, which seems like it might be a =
more reliable connection.
- Have you used the hp300 netboot instructions lately as published on the N=
etBSD site, and been successful, or found another path?
Thanks for any assistance - it would be nice to get this machine up and run=
ning.
-mike
--_000_CO1PR18MB4826A4D76FB35436D148789DACB4ACO1PR18MB4826namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of=
fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Aptos;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-compose;
font-family:"Times New Roman",serif;
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1973094300;
mso-list-type:hybrid;
mso-list-template-ids:281943728 -1774307640 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Aptos",sans-serif;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:Aptos;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style>
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap:brea=
k-word">
<div class=3D"WordSection1">
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">Hi folks!<o:p></o:p></sp=
an></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p> </o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">For literally the first =
time in at least a couple decades, I'm trying to power up and play with my =
9000/362 (I think that would be the designation based on what I have). =
; Because I don't have an existing system
to bootstrap an OS onto a disk with, I'm trying the netboot route. P=
lus, it seemed like an interesting exercise I haven't done since the early =
2000s.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p> </o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">I tried following the in=
structions here:
<a href=3D"https://www.netbsd.org/docs/network/netboot/intro.hp300.html">ht=
tps://www.netbsd.org/docs/network/netboot/intro.hp300.html</a> - speci=
fically the steps listed at the bottom (rbootd, rarpd, etc). I succes=
sfully followed those instructions many years
ago but I think that SYS_UBOOT has changed enough that they are well out o=
f date.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p> </o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">TL;DR: I'm getting an le=
0: lot carrier when it's trying to bring down the kernel.<o:p></o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p> </o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">---<o:p></o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p> </o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">A bit of hardware backgr=
ound. My machine has the thinnet NIC on the System Interface board, a=
nd an AUI interface in the expansion chassis. Because immediate acces=
s to AUI networking was a little easier (just
grab a tranceiver and I'm ready to go), I decided to use the AUI. I =
switched the select codes on both ethernet devices so that the AUI had the =
lowest number (not sure if this is necessary). Time to start the netb=
oot setup.<br>
<br>
rbootd installation went smoothly enough. After the hp was turn=
ed on, a little while later both the rbootd debug output & the behavior=
on the hp console indicated success.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p> </o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">rarpd was where the succ=
ess stopped. I never got a rarp request. At this point I turned=
to my favorite overeager coding buddy, chatGPT for assistance, and surpris=
ingly, it had some good info.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p> </o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">Main useful observation:=
the console message was saying that the SYS_UBOOT bootstrapper was us=
ing bootp, and that rarpd was no longer in use. Interesting (if true)=
. Time to switch to a bootp process. Rather
than suggesting traditional bootp, my little coding buddy suggested =
I try something called dnsmasq as a more modern alternative. Sure, le=
t's try that out.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p> </o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">I download and configure=
dnsmasq. This took a bit of poking, but I eventually got it set up i=
n a way that seemed sane. On the 300, the bootstrap would start up, a=
nd then start asking for a variety of kernels
(netbsd, netbsd.gz, etc) but never actually got any data. It just lo=
ops over and over through the series of kernel names. Using tcpdump o=
n the tftp port, I see no requests from the hp. Coding buddy suggests=
that the SYS_UBOOT might insist on using the thinnet
NIC, regardless of Select Code or how it brought down the bootstrap. =
At that point I break for the night.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p> </o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:black">This morning, I dug up s=
ome thinnet hardware & cabling, and switched everything over to use tha=
t NIC. Now, I actually see requests for a kernel showing up in the dn=
smasq logs:<br>
<br>
dnsmasq-dhcp: 326617420 bootfile name: netbsd<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">dnsmasq-dhcp: 326617420 =
next server: 192.168.2.227<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">dnsmasq-dhcp: 326617420 =
sent size: 1 option: 53 message-type 5<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">dnsmasq-dhcp: 326617420 =
sent size: 4 option: 54 server-identifier 192.168.2.227<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"color:black">dnsmasq-dhcp: 326617420 =
sent size: 4 option: 1 netmask 255.255.0.0<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">dnsmasq-dhcp: 326617420 =
sent size: 4 option: 28 broadcast 192.168.255.255<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">dnsmasq-dhcp: 326617420 =
sent size: 4 option: 3 router 192.168.1.1<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p> </o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">and on the HP console I =
just see a sequence of errors:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">le0: lost carrier<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">le0: lost carrier<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">le0: lost carrier<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">le0: lost carrier<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">bootp: no reply<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">boot: client IP address:=
0.0.0.0<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">root: addr=3D0.0.0.0 pat=
h=3D<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">le0: lost carrier<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">le0: lost carrier<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">le0: lost carrier<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">le0: lost carrier<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">arpwhohas: no response f=
or 0.0.0.0<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p> </o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">And that’s where I=
’m stuck. I suspect those messages indicate physical level erro=
rs; e.g. the onboard bnc wiring, 10baseT hub I’m using that has a 10b=
ase2 connector on it is faulty, or more likely, the rg58 cabling/tees/termi=
nators
have decayed or oxidized over the decades and are no longer reliable. =
; I’m perhaps a little surprised that it’s so reliably unreliab=
le, but maybe that’s the difference between bootp and a protocol that=
requires a sustained carrier running on marginal cabling.<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p> </o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Any insight or ideas wou=
ld be appreciated! I feel like I’m really close and I’d l=
ike to push past this. In particular:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p> </o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">- Ideas on what I might =
be doing wrong? I know I’m straying from the standard path, but=
out of what seems like necessity. I could try to go back to traditio=
nal bootp, but that doesn’t seem like it would make
a difference. It’s the tftp part that’s failing.<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">- Ideas on how to do thi=
s all over the AUI, which seems like it might be a more reliable connection=
.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">- Have you used the hp30=
0 netboot instructions lately as published on the NetBSD site, and been suc=
cessful, or found another path?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p> </o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Thanks for any assistanc=
e – it would be nice to get this machine up and running.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p> </o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">-mike<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p> </o:p></span>=
</p>
</div>
</div>
</body>
</html>
--_000_CO1PR18MB4826A4D76FB35436D148789DACB4ACO1PR18MB4826namp_--