Install fails at 'Mounting local filesystems'

[DarrenG]

Hi. I am essentially completely new to Gentoo. I have searched for this on here, but either my search terms were wrong or it is new. Apologies if not. Also, not sure if this post should be here (install) or in the 'other architecture' forum.

I am trying to install on an AlphaServer 1200. 1GB RAM, 2 EV56 chips, 4 SCSI HDDs, 1 SCSI CD, 1 IDE CD. It boots from SRM console no worries, but when it gets to 'Mounting local filesystems' it just stops. It's not dead -- I can use Ctrl-Alt-Del to reset, for example, so it does take input. (I should say the box boots into Debian 5.0 no worries.)

I think the problem is a lack of firmware/kernel modules for my hardware. Years ago (say 10 years ago), they were in Gentoo (at least, I remember getting to the stage of trying to compile a kernel, so I must have got a lot further, but it wasw a long time ago).

I'm not sure how to dig up dmesg output from the installation kernel, because I cannot seem to get out of the boot sequence without shutting the thing down.

The lights on the HDDs flicker during boot, while activating udev. It finds the root device on /dev/srt0 (the CD) ok. When it says 'populating udev' during the boot, all the HDD lights flicker. But that's it.

During a previous attempt with a Stage 1 from maybe 6 months ago, I could get to /run/initramfs/gksosreport.txt
I
and it said:

could not load sym53c8xx, qla1280, pata_pdc202xx_old.

So I am wondering if there is a way to add more firmware to the initrd on the Stage 1 disc. With a lot of advice, I have tried this with Debian with some success (https://lists.debian.org/debian-alpha/2019/11/msg00033.html). They gave me a method to unpack the ISO, then unpack the initrd, add firmware to it and package it all up again.

I do not want to assume that would work here, so I am asking for advice.

THanks!

Darren
_________________
Some guy playing with old hardware

[Banana]

Hello and welcome to the forums.

How did you do your install? Are you running gentoo already?

The amount of RAM worries me. Gentoo builds required software you want to install and thus needs ressources to do so. 1GB RAM is not enough for this kind of process. I don't know if 1GB RAM is even enough to build the kernel.
One idea could be using another hardware which builds the required software packages and the AlphaServer uses them.
_________________
Forum Guidelines

PFL - Portage file list - find which package a file or command belongs to.
My delta-labs.org snippets do expire

[NeddySeagoon]

DarrenG,

Welcome to Gentoo.
Let's start at the beginning by discovering your hardware.

Boot any linux that works.

Run lspci -nnk and post the output.
Not all versions of lspci support the -k option but it's only a nice to have.

With that information, we can unpick the Alpha liveCD and see what is missing,

Another thought ...
The Gentoo ISO is not required to install Gentoo. It's just a toolkit.
Boot whatever works
Get a root shell
Run mkdir /mnt/gentoo
Follow the handbook.

/mnt/gentoo is about all that the ISO gives you.
Extra points for doing the install over ssh. :)

I can see lack of RAM being a problem further down the road.

== edit ==
It's even possible to put the Gentoo stage 3 on top of a kernel from another distro but let's not go there yet.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[DarrenG]

Dear NeddySeagoon.

Many thanks. I think you are referring to https://wiki.gentoo.org/wiki/Installation_alternatives#Installing_Gentoo_from_an_existing_Linux_distribution, yes?

Now that I have seen it, that's a good idea. The alpha has several HDD, so I can choose one and manipulate it from the working Debian 5 installation. AFAIK Alpha needs you to install aboot to the front of the drive. but I don't think that has to be a problem. IN fact, I suspect I can use the aboot on an existing working drive to boot a distro on another drive. Hmm.

The handbook refers to the CD method as recommended, though. So with that in mind, here is the lspci output. This is a system from last century, so it is possible that some of the needed stuff has been weeded out in recent years as cruft ...

lspci outout:

0000:00:01.0 EISA bridge [0602]: Intel Corporation 82375EB/SB PCI to EISA Bridge [8086:0482] (rev 15)
Kernel driver in use: pci_eisa
0000:00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 [1013:00b8]
Kernel modules: cirrusfb
0000:00:03.0 Mass storage controller [0180]: Promise Technology, Inc. PDC20262 (FastTrak66/Ultra66) [105a:4d38] (rev 01)
Kernel driver in use: Promise_Old_IDE
Kernel modules: pdc202xx_old
0000:00:04.0 PCI bridge [0604]: Digital Equipment Corporation DECchip 21050 [1011:0001] (rev 02)
0000:01:00.0 SCSI storage controller [0100]: QLogic Corp. ISP1020 Fast-wide SCSI [1077:1020] (rev 02)
Kernel driver in use: qla1280
Kernel modules: qla1280
0001:02:01.0 SCSI storage controller [0100]: LSI Logic / Symbios Logic 53c810 [1000:0001] (rev 02)
Kernel driver in use: sym53c8xx
Kernel modules: sym53c8xx
0001:02:02.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 62)
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
0001:02:02.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev 62)
Kernel driver in use: uhci_hcd
Kernel modules: uhci-hcd
0001:02:02.2 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 65)
Kernel driver in use: ehci_hcd
Kernel modules: ehci-hcd
0001:02:03.0 Ethernet controller [0200]: Digital Equipment Corporation DECchip 21140 [FasterNet] [1011:0009] (rev 20)
Kernel driver in use: tulip
Kernel modules: tulip



Cheerio
_________________
Some guy playing with old hardware

[Banana]