Hi Buck,
On 13.12.2013 00:29, Buck Huppmann wrote:
After failing to install using the latest image, because the md5sum.txt file had
a bad md5sum for one of the installation packages (e2fsprogs*udeb*),
This is usually due to an error while copying to the USB stick.
i downloaded
the image from earlier in the day and it worked just fine, with manual
partition-
ing, creating an LVM, ext4 filesystems, etc., clobbering an NTFS partition and
leaving the rescue partition alone
Great.
Suspend to disk works fine, wireless works fine after installing the appropriate
firmware non-free package. (I installed using the wired Ethernet; wireless
wasn't configured by the installer, and so it didn't go looking for the firmware
tarball i unpacked into a /firmware directory on a VFAT filesystem i appended to
the USB stick)
This is a known problem, see bug #725714 [1].
Comments/Problems:
Reboot failed, as i'd tried to install grub into the /boot partition so i could
boot into the recovery partition, but couldn't figure out how to do that, so i
input
/dev/sda
which seemed to work, but i got
Operating system missing
or some such DOS/Windows MBR boot-failure message, so i rebooted the USB stick
in rescue mode, started up a shell using the newly installed root filesystem
and mounted /usr and /boot, and ran grub-install, which refused to install in
/dev/sda1, so i let it overwrite the /dev/sda
Grub2 should not be installed into a partition, but rather on a hard
disk. If you really need it, you could try the --force option.
I think this bug can be closed, because the remaining problem is
discussed in [1]. Do you agree?
Best regards,
Andreas
1: http://bugs.debian.org/725714
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
