Scott Holder dixit: > I went ahead for broke and figured I didn't have anything to lose, so I went > ahead and untarred the m68k-base.tgz on a spare partition and tried it. But, > it > appears the kernel is missing the Mac SCSI drivers (or they aren't working). > It
Yes, the 3.10 kernel does not have *any* disc or filesystem drivers in the kernel image - it relies on Debian initramfs-tools to create an initrd tailored for your specific system. That's the thing I had feared when switching to initrd - making such bootstrapping cases harder. You should be able to use 3.2 or 3.8 to boot then install the kernel package on the system which will let it generate an initrd. Maybe we can cheat. http://zigo.mirbsd.org:8080/t/initrd.img-3.10-2-m68k is the one Debian generated for me on the system running the buildd and *might* be able to get you into console mode at least. (The "mirnitrd" contains only minimal klibc-utils userspace and is not intended for booting into a system on the HDD. It's supposed to drop you into a shell on tty2.) bye, //sleepless mirabilos -- 21:12⎜<Vutral> sogar bei opensolaris haben die von der community so ziemlich jeden mist eingebaut │ man sollte unices nich so machen das desktopuser zuviel intresse kriegen │ das macht die code base kaputt 21:13⎜<Vutral:#MirBSD> linux war früher auch mal besser :D -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pine.bsm.4.64l.1308200654590.2...@herc.mirbsd.org
