clone 541823 -1 -2 reassign -1 installation-report reassign -2 console-setup reassign -3 iso-scan retitle -1 README.Debian wrongly suggests reporting bugs to installation-report retitle -2 settings chosen from console-setup-udeb not preserved on installed system retitle -3 Consistently fails to find ISO image on first try thanks Quoting Celejar (celejar@gmail.com): Thanks for your very detailed installation report. It contains much valuable information and I'll try a first attempt to use at least part of it > Initial boot: [O ] > Detect network card: [E ] > Configure network: [ ] > Detect CD: [E ] > Load installer modules: [E ] > Detect hard drives: [O ] > Partition hard drives: [E ] > Install base system: [O ] > Clock/timezone setup: [O ] > User/password setup: [O ] > Install tasks: [ ] > Install boot loader: [O ] > Overall install: [E ] > > Comments/Problems: > > 1) The installer allowed me to set a keymap and layout (us / dvorak), but this > was not preserved in the actual install, which reverted to standard us. That's the secodn time we get such report. I'm definitely not in position to test this, but there's something broken somewhere in console-setup > > 2) The installer consistently failed to find the installer ISO on the first > try (I wound up running it quite a few times, due to various problems), > although it always found it on the second. Assigned to iso-scan. It would be very interesting if you could try reproducing this and check what's displayed on 4th console after the first failure. > > 3) AFAICT, the installer kernel doesn't include b43. Why? I understand that > we can't ship non-free firmware, but why not include the driver for those of us > who are able and willing to provide firmware? This one I leave to other maintainers.... > > 4) I was unable to delete a LUKS encrypted disk that I had created on a > partition. The installer refused to delete the partition since it was used by > the encrypted disk, but it also apparently offered no way to delete the > encrypted disk. That one also. Hopefully Max will look at it in details. > > 5) The showstopper: I installed the entire system (except for /boot) onto LVM > volumes in a vg on top of a LUKS volume created out of a primary partition. > When I rebooted, the system wouldn't bring up the LUKS volume. The eventual > fix that worked is to add this line to /boot/grub/menu.lst: > > # kopt=cryptopts=target=hda4_crypt,source=/dev/hda4,lvm=lizzie-root root=/dev/mapper/lizzie-root ro > > This is: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492790 > > and > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522041 > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507721 > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503062 > > 6) Should installation reports be filed against 'installation-report' or > 'installation-reports'? The README from the installation-report package says > 'report', but most reports seem to be filed against 'reports'. Apparently this error is there for ages..:-). Reported against i-r
Attachment:
signature.asc
Description: Digital signature