Yes, this would seem to be my only complaint, but it's the one that really holds me up from testing stuff, since I can't get any further than that to mount anything via NFS.  :-)

8139too will not insmod for me.  The NIC is a DLink DFE-538TX.  The motherboard is an Abit BH6.  network.img from Feb 14 works, every image I have used before and after that day has not.  I guess on the day of love, network.img loved my NIC, and on every other day it doesn't.  (Note: I haven't actually tested the install every day, so there could have been several days there around Valentine's Day that worked, I don't know for sure)

While I'm at it, I can use the Feb 14 disk (since I still have it) to start an install, but once I get to the package selection page, I select all the groups, unselect the option to pick individual packages, and click OK, and watch X (not so) happily disappear from my screen and the system halts.

Entering step 'Choose packages to install'
Entering step 'Install system'
install exited abnormally :-( -- received signal 11
(--) FBDev: Frame buffer device: VESA VGA
(--) FBDev: Video memory: 4096K @ 0xd5000000
(--) FBDev: MMIO regs: OK @ (nil)
(--) FBDev: Type 0 type_aux 0 bits_per_pixel 16
(--) FBDev: Hardware accelerator: none
(--) FBDev: No driver support for hardware acceleration
bits = 16, depth = 16, BitsPerRGB = 6
(--) FBDev: using cfb16 driver
error opening security policy file /usr/X11R6/lib/X11/xserver/SecurityPolicy
sending termination signals...done
etc.

That's using DrakX 1.435, if that helps.  It could just be unhappy at my mixing an older network.img with a newer second stage installer, dunno.  Is that a valid theory?

Eaon

Reply via email to