![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
altivoOn the Alpha, Gentoo is only slightly less frustrating than OpenBSD. While it's clear that the system is (or can be) much more functional and usable than OpenBSD, the documentation is about equally poor.
I have a whole page listing downright errors and misinformation in the installation instructions for Alpha systems now. The worst of these is a section on preparing disk drives that turns out to be just plain wrong. The "fdisk" utility supplied in their CD image cannot do what they say it can. Worse, it will corrupt your disk labels if you already have them. Booting from a hard disk using the Alpha SRM console firmware and aboot loader requires BSD style disk labels. MSDOS type partition tables will not work. Linux fdisk a few years ago was capable of generating or updating either one, but apparently the BSD capability has been removed or somehow disabled. In the end, I had to initialize a SCSI drive using OpenBSD (ironic, I know) in order to get it in a format that the Alpha could boot from.
Then there's the kernel build. The distribution CD image does boot, and has a kernel capable of doing most things necessary. The installation procedure strongly recommends building a custom kernel suited to your particular hardware. This is not bad advice, as I well know. It produces a leaner, much more efficient kernel that uses a lot less memory and boots more quickly.
Unfortunately, the information on configuring said kernel is sadly vague. I tried four times, then went the alternate route of letting their utility "genkernel" configure a kernel for me. That was a waste of time. The configuration produced that way wouldn't even compile.
I finally extracted the configuration from the kernel provided on the installation to use as a model for my own. In the process I discovered that the distribution kernel was last compiled on Gentoo version 3.17.7, while the actual software I'm installing is version 4.0.5. Sure enough, when I tried using that configuration file as is to produce a kernel on the current system, it also failed. The errors seem to indicate that the resulting code is too large for the linkage editor to handle. This is understandable, since it includes drivers for every disk controller and NIC known to man or woman, and a few unknown even to the geekiest of users. A NIC made by "Happymeal"? Surely this didn't need to be included. I deselected all of the drivers except for the normal DEC devices that are actually included in my hardware. Now the kernel does compile, and in half the time. It even almost boots, but locks up near the end of the I/O device initialization and I'm still trying to figure out why.
As with OpenBSD, there seem to be no supporting people available who actually have Alpha hardware or know anything about the Alpha branch. I wonder if I'm the first one to actually attempt a new Alpha install since the release came out in January of this year... In fact, I wonder if it was tested at all, given what I've discovered about the instructions and the fdisk program.
Not giving up yet, because I really do want this to work. But: I've been managing UNIX and Linux systems since 1989 or so. I used Slackware, which is almost as geeky a distro as Gentoo, on my own desktop for many years. If I'm having this much trouble getting Gentoo running, there's definitely something wrong and it isn't just with me.
I have a whole page listing downright errors and misinformation in the installation instructions for Alpha systems now. The worst of these is a section on preparing disk drives that turns out to be just plain wrong. The "fdisk" utility supplied in their CD image cannot do what they say it can. Worse, it will corrupt your disk labels if you already have them. Booting from a hard disk using the Alpha SRM console firmware and aboot loader requires BSD style disk labels. MSDOS type partition tables will not work. Linux fdisk a few years ago was capable of generating or updating either one, but apparently the BSD capability has been removed or somehow disabled. In the end, I had to initialize a SCSI drive using OpenBSD (ironic, I know) in order to get it in a format that the Alpha could boot from.
Then there's the kernel build. The distribution CD image does boot, and has a kernel capable of doing most things necessary. The installation procedure strongly recommends building a custom kernel suited to your particular hardware. This is not bad advice, as I well know. It produces a leaner, much more efficient kernel that uses a lot less memory and boots more quickly.
Unfortunately, the information on configuring said kernel is sadly vague. I tried four times, then went the alternate route of letting their utility "genkernel" configure a kernel for me. That was a waste of time. The configuration produced that way wouldn't even compile.
I finally extracted the configuration from the kernel provided on the installation to use as a model for my own. In the process I discovered that the distribution kernel was last compiled on Gentoo version 3.17.7, while the actual software I'm installing is version 4.0.5. Sure enough, when I tried using that configuration file as is to produce a kernel on the current system, it also failed. The errors seem to indicate that the resulting code is too large for the linkage editor to handle. This is understandable, since it includes drivers for every disk controller and NIC known to man or woman, and a few unknown even to the geekiest of users. A NIC made by "Happymeal"? Surely this didn't need to be included. I deselected all of the drivers except for the normal DEC devices that are actually included in my hardware. Now the kernel does compile, and in half the time. It even almost boots, but locks up near the end of the I/O device initialization and I'm still trying to figure out why.
As with OpenBSD, there seem to be no supporting people available who actually have Alpha hardware or know anything about the Alpha branch. I wonder if I'm the first one to actually attempt a new Alpha install since the release came out in January of this year... In fact, I wonder if it was tested at all, given what I've discovered about the instructions and the fdisk program.
Not giving up yet, because I really do want this to work. But: I've been managing UNIX and Linux systems since 1989 or so. I used Slackware, which is almost as geeky a distro as Gentoo, on my own desktop for many years. If I'm having this much trouble getting Gentoo running, there's definitely something wrong and it isn't just with me.
