Samuel Liddicott wrote: > Neither, its the first phase from a network install after its loaded > loads of udebs I can think of a total of 10 different installation methods that could be characterised as a network install. 4 of these are currently known to be broken: 1. netboot i386 install with 2.4 kernel, using daily built initrd: ok 2. netboot i386 install with 2.6 kernel, using daily built initrd: ok 3. netboot i386 install with 2.4 kernel, using beta4 initrd: probably broken 4. netboot i386 install with 2.6 kernel, using beta4 initrd: probably broken 5. floppy+net-drivers install, using daily built images: ok 6. floppy+net-drivers install, using beta4 images: probably broken 7. businesscard and network install, using daily built images: ok 8. businesscard and network install, using beta4 images: broken 9. netinst CD install (no actual network download), using daily built images: ok 10. netinst CD install (no actual network download), using beta4 images: ok I have heard all of these called a "network install"; this lack of specificity is why we have installation report templates that help users be very specific about exactly what version of the installer they used. Until we know exactly what was used, we generally can't help you, or helping you would end up using much more of both of our time than it would take you to compose a detailed installation report. FWIW, I've verified that the module you want is available using methods 1, 2, 5, 7, and 9. I'm guessing that you're using method 3, which probably won't work. > >or fails to detect your disks, or that there is some other problem. > > > >Send us a full set of logs, please. Preferably in a proper and complete > >installation report filed in the bug tracking system. > > > > > Well, I would, but I can't install till the 3w-xxxx module is loaded. There is a installation report template on the web, and a menu item in the installer to save your logs to a floppy. -- see shy jo
Attachment:
signature.asc
Description: Digital signature