Created attachment 3383 [details] report.bug Installing Mga3beta2 fails on two desktops, one of them doesn't even reach stage2 (if the DVD is started at all). The same traditional installer DVD installs fine on a laptop. The system where the problems are worst, has no problem installing Mageia 1. Attaching report.bug for the system where it was in stage2 install failed. Both systems have similar hardware, only "the worst" system has more RAM
CC: (none) => thierry.vignaudWhiteboard: (none) => 3beta2
* insmod: ERROR: could not insert module /tmp/floppy.ko: No such device * mounting /dev/sdb1 on /fd as type ntfs-3g, options this reminds me bug 4696 (ie try to disable the floppy drive)
(In reply to comment #1) > * insmod: ERROR: could not insert module /tmp/floppy.ko: No such device > * mounting /dev/sdb1 on /fd as type ntfs-3g, options > > this reminds me bug 4696 (ie try to disable the floppy drive) In the Bios, I already had Floppy 3 Mode Support [Disabled] and Boot Up Floppy Seek [Disabled] Because I don't have a floppy drive. I don't see anything else related to Floppy drives.
With today's traditional i586 installer DVD (from around noon, so not of last night) I get: "Error reading config file" at the same time the boot screen appears. Trying to boot just lets this message repeat itself.
(In reply to comment #3) > With today's traditional i586 installer DVD (from around noon, so not of last > night) I get: > > "Error reading config file" at the same time the boot screen appears. Trying to > boot just lets this message repeat itself. I'll file a separate bug for it, it also happens on a laptop that did not have the problem this report was filed for.
(In reply to comment #4) > > (In reply to comment #3) > > With today's traditional i586 installer DVD (from around noon, so not of last > > night) I get: > > > > "Error reading config file" at the same time the boot screen appears. Trying to > > boot just lets this message repeat itself. > > I'll file a separate bug for it, it also happens on a laptop that did not have > the problem this report was filed for. #8817
Forget comment 5, I had missed that there was yet another new iso, 4 hours later. This bug is fixed in the really last 3beta2 iso
Status: NEW => RESOLVEDResolution: (none) => FIXED