On Wed, Jan 21, 2004 at 04:13:01PM -0600, John Lightsey wrote: > > > The only other > > > trouble I noticed is that the aboot.conf that is generated doesn't point > > > to the proper location of my root filesystem. The installer kept going > > > back to the "configure network" option even though I couldn't bring the > > > network up, so it may be a case where I did something out of order. I > > > did not repartition. I did reformat my old partitions with the root as > > > the A partition. > > Can you provide more details regarding what your aboot.conf looks like > > after installing, what you believe it should look like, and the contents > > of your partition tables? > > I was proud of that bit of code in aboot-installer, so if it has bugs, > > I'd like to get them fixed. ;) > > The "configure network" glitch you're seeing has to do with this being a > > *net*inst image: it really, really, really wants you to have a network, > > because it knows you're not booting from a full CD. :) > My harddrives are already partitioned like this: > /dev/hda1 ext2 > /dev/hda2 swap > /dev/hdb1 ext2 > HDA is partitioned in BSD disklabel format (hda1 is A:) > HDB is partitioned in the standard way. > Configure and mount partitions > (switching to tty2 shows ext3, reiserfs, jfs and xfs modules failing to load.) > IDE1 master, part. 1 -> ext2 -> / > IDE1 master, part. 2 -> swap ->swap > IDE2 master, part. 1 -> ext2 -> /home > I tell it to format all of them, hit finish and yes at the warning screen. > tty2 shows them being formatted and mounted > Again "module needed by your ethernet card:" > and again "none of the above" > Install the kernel. > I select 2.4-generic. > This spends a lot of time at 60% then goes back to the "Module needed by your > ethernet card:" I again pick "none of the above". > Finish the installation and reboot. > cd pops out. > hit continue to reboot. > I have to cycle the power to keep SRM from loading off the cdrom again. Ah, so at no point did you pick "Install aboot on a hard disk" as an option from the main menu? Do you see this as an option? Is it listed in the wrong place in the menu (i.e., below "finish the installation and reboot")? > alpha:~# cat /etc/aboot.conf > # > # aboot default configurations > # > 0:3/vmlinux.gz ro root=/dev/sda2 > 1:3/vmlinux.old.gz ro root=/dev/sda2 > 2:3/vmlinux.new.gz ro root=/dev/sda2 > 3:3/vmlinux ro root=/dev/sda2 > 8:- ro root=/dev/sda2 # fs less boot of raw kernel > 9:0/- ro root=/dev/sda2 # fs less boot of (compressed) ECOFF kernel > - > alpha:~# > what it needs to be is: > 0:1/vmlinuz root=/dev/hda1 initrd=/initrd.img Yep, the aboot.conf cited above is the default shipped with the aboot package. While this could mean aboot-installer failed miserably without telling you, from above it sounds like aboot-installer simply was never run on your system. > > Does this mean you have one of the P1SE/P2SE integrated cards, or > > something similar that results in the use of a PCI bridge on your > > system? > The integrated network card is definitely taking across a PCI bridge. > Anything I plug into the PCI slots also seems to be taking across the PCI > bridge. That thread describes exactly the sort of trouble I've been having > with 2.4 kernels. It's not limited to network cards. They are just the most > visibly broken. Yep, this problem makes both my SCSI controller and my ethernet unusable under 2.4.24. > The 2.2.22 kernel in Woody works flawlessly. If there was a 2.2 > kernel in Unstable I'd have no problems at all. Not likely to happen, I'm afraid... but maybe we can get a 2.6.1 that works instead. -- Steve Langasek postmodern programmer
Attachment:
pgp5M8RlU1V8f.pgp
Description: PGP signature