Linux on the DEC 3000
Home | System Info | Documentation | Log Book
Just got back from Thanksgiving (*burp*) with my folks down in
Ft. Myers. Have tweaked the System
Info page with the memory part numbers. Also, plugged in the
"new" 3000/300LX at home.
Plan, beginning tonight:
|November 22nd||After (another) long hiatus, I'm back. This time for a couple weeks, I hope. I've updated the web pages, and added the System Info page. Now to re-acclimate myself and get coding!|
I've updated the aboot sources on the main page, and provided an SRPM
(my first!). Am trying to find the aboot maintainer now.
Not much work has gone in lately - still reading docs when I can,
trying to understand what the interrupt code is doing. I started
to add some Turbochannel probing code, but it doesn't work yet.
Am past the
Installed NetBSD on the 3000/500 at work. Should be pretty useful, as I can read the code and put lots of printf()s in to learn more about what a working system has to do!
Well, it's been nearly 2 months since I updated this page... Time
to fill in all the listeners out there :)
Not too much happened at the end of June and in July - I was in Ithaca for most of that time, and it was all work and no play (linux-wise, anyway).
Since I've been back, I've gotten a few things done; we are not much farther in the kernel, though. Here's what has gone on:
Kinda funny how that is the same error I was getting way back when with
I added the necessary Flamingo and Pelican hooks to
For now, all members of the Flamingo (DEC 3000/[4-9]00) and Pelican (DEC 3000/300*) families are the same; I'm not sure yet if the kernel needs to know about differences between models within a given family. But the structure is there to easily add that if need be.
The Halt is coming from
Out of sheer curiosity, I tried booting from the new 164SX
running RH6.0, kernel 2.2.9, and aboot 0.5-10. No help - still
death after the first
It turns out...
Aboot was crapping out in
The error above looks like a machine check - not too surprising, as the kernel which I used was for a 164SX :)
I littered printf's all over aboot - we do indeed make it into run_kernel.
I've started adding code to kernel - I added the Makefile stuff
for all the DEC 3000 machines. The netbsd sources were helpful
in getting the family/name/alias stuff worked out for the models
I didn't already know. Here are
the modified entries to
I also hacked up a template for the
Turbochannel ASIC stuff, which I stole from the existing
Linux/Alpha APECS (PCI based) code, and just dummied out a lot
of the functions, etc. I certainly don't expect this to work
out of the box - I've got a lot of consulting with documentaiton
to do. But I did build a "Flamingo" kernel. Here's what
happened when I tried to netboot it.
As an aside, it seems RedHat no longer ships the BOOTP package
with their distribution. I tried DHCP
out, but caradhras kept "RETRYing". Probably 'cuz there was no
entry like BOOTP's
All in all, a good weekend. But now, I think it starts to get hard.
Tried to BOOTP a kernel to see how far I got. Built
aboot-0.5-9 from sources. Funny -
Well, it turns out that I get to aboot's first
I think what I will try to do is make aboot work with the v7.0 firmware. The reasons for this are:
If I can't get past this, I'll find some older firmware and try it out.
Went searching on the net for a solution to the problems
caradhras has netbooting. Bad news and good news. Bad news
first - this is a firmware problem, and people have been having
problems netbooting DEC 3000s for a long, long time. But the
good news is that there is now a solution! Apparently, the
"hn:vm=rfc1048:" entries in the BOOTP server's bootptab are
necessary for the DEC 3000 with most recent firmwares; thanks to
for putting this on his web pages, and to
Dave Johnson for posting
his results to fa.netbsd.ports.alpha (server: i386 Linux,
client: DEC 3000/300). Also note that
Aaron Grier reports
that DHCP also works with these flags (server: DecStation
5000/240 running NetBSD 1.4, client: DEC 3000/400).
Here's my working bootptab:
So it *is* possible to use BOOTP with the most recent firmware.
It turns out that George is working on a Linux port to the DEC 3000/300 - here is his porting diary. I should send him a mail - maybe we can work together on this. His experience, however, was that aboot will not work with version 7.0 of the firmware. I'll try it out.
Well, I've done almost nothing for the last 6 weeks on this.
It is time to start having some fun!
Set up the AlphaStation 250 4/266 as a BOOTP server. Successfully upgraded firmware on the AlphaStation 200 4/233 via BOOTP. So far so good - at least the BOOTP server is functioning correctly.
Had to allow 0.0.0.0 to come in. Originally, I had ALL: ALL in my hosts.deny, and only had machines with IP addresses on my private network permitted in hosts.allow.
However, firmware update for the DEC 3000/600 didn't work...
not sure why. The BOOTP server responds ok, and the DEC 3000
knows it, but the NIC apparently times out. Here's what is on
the console for the client: