Additional info: [!] Check the CD-ROM(s) integrity Integrity test failed The ./dists/etch/main/binary-i386/Packages file failed the MD5 checksum verification. Your CD-ROM or this file may have been corrupted.
Burned 2nd CD with same result. > -----Oorspronkelijk bericht----- > Van: Pieter Roodnat [mailto:[EMAIL PROTECTED] > Verzonden: donderdag 8 juni 2006 9:42 > Aan: 'Christian Perrier'; '[EMAIL PROTECTED]' > Onderwerp: RE: Bug#371856: etch beta 2 release netinst CD image no central > european locale + reboot problem > > Hi Christian, > > Thanks for your reply. > As suggested, i downloaded daily build netinst CD image debian-testing- > i386-netinst.iso on June 8th 9:12CET > File properties creation date June 6th 2006, 20:06:08 > > ENTER to boot: <Enter> > Language: English > Location: other->Netherlands > Keymap to use: American English > Detecting hardware for find CD-ROMs... > Scanning CD-ROM... > > [!!!] Load installer components from CD > > No kernel modules were found. This probably is due to a mismatch between > the kernel used by this version of the installer and the kernel version > available in the archive. > > > > -----Oorspronkelijk bericht----- > > Van: Christian Perrier [mailto:[EMAIL PROTECTED] > > Verzonden: donderdag 8 juni 2006 7:02 > > Aan: Pieter Roodnat; [EMAIL PROTECTED] > > Onderwerp: Re: Bug#371856: etch beta 2 release netinst CD image no > central > > european locale + reboot problem > > > > > > > 1. Timezone selection didn't seem to let me choose for central > European > > time > > > like sarge installer did. > > > > Please be more precise here. Which language did you install with? > > > > If you did choose English and whichever country as only one timezone, > > then the installer did choose the timezone of that country without > > asking you. So, for instance, if you choose English then Netherlands, > > you'll end up with a system setup for CET. Same of course, if you did > > choose Dutch then Netherlands, of course. > > > > > > > > 2. Left select and install software which I left on the defaults. > After > > > installation finished there was an error which was gone after the > > installer > > > retried installing everything again. Eventually it finished without > > errors > > > and rebooted resulting in a "boot failure" because the harddisk does > not > > > seem to be bootable. > > > > We need more details here. What "error" and when exactly ? > > > > The boot failure is probably a device naming issue. Something that > > actually has been solved in recent daily builds (please try some of > > them if you can reinstall this machine). > >
