On Mon, 2004-11-22 at 13:30 -0500, Greg Folkert wrote: > I have an Alpha 2100 Sable (not 2100A model) Single or Dual (I can use > either processor). I netboot using the boot.img from the Daily builds of > 20041018 for Alpha. I used my on LAN mirror for the packages and > ftp.us.debian.org. Both work well. > > I completely have 100% success, up until the point I try to boot from > the Hard Drive. > [snip] > I booted with this SRM command-line: > > boot dka0 -fi 2/vmlinuz-2.4.27-1-generic -fl ro root=/dev/sda3 > > And that is where it sat the whole weekend. Okay so, I am an idiot. I looked at the aboot.conf. It explained a couple of things to me. Aboot is no longer the problem. aboot uses part3 for storing config. Here is the current SRM boot* etc... settings: boot_dev dka0.0.0.1.0 boot_file 2/vmlinuz-2.4.27-1-generic boot_osflags initrd=initrd.img-2.4.27-1-generic ro root=/dev/sda3 boot_reset OFF bootdef_dev dka0.0.0.1.0 booted* do not matter. the command line looks like this, split for mail readers: P00>>boot dka0 -fi 2/vmlinuz-2.4.27-1-generic -fl \ initrd=initrd.img-2.4.27-1-generic ro root=/dev/sda3 Now, I am getting to the point where I ask. I can't get the sym53c8xx.o module to work (from the above kernel) something is amiss. Le-sigh... Going to try kernel-image-2.6.8-1-generic for alpha as well. [snip] > Looking gleefully for assistance! -- greg, greg@gregfolkert.net The technology that is Stronger, better, faster: Linux
Attachment:
signature.asc
Description: This is a digitally signed message part