[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#685308: marked as done (Installation report Wheezy Beta 1)

Your message dated Sun, 25 Aug 2013 12:42:38 +0200
with message-id <201308251243.25305.holger@layer-acht.org>
and subject line dealing with old installation-reports
has caused the Debian Bug report #685308,
regarding Installation report Wheezy Beta 1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

685308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685308
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: <How did you boot the installer? CD? floppy? network?>

Image version: <Full URL to image you downloaded is best>
Wheezy release Beta 1 AMD64 Netinst

Date: <Date and time of the install>
August 18 and August 19, several attempts

Machine: <Description of machine (eg, IBM Thinkpad R32)>
Lenovo IdeaCentre K210

Processor: Intel Dual Core Pentium E5200
Memory: 4G
Partitions: <df -Tl will do; the raw partition table is preferred>
Partition 1: Windows Vista (620 GB)
Partition 2: free space (19 GB)

Output of lspci -knn (or lspci -nn): not available

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [O]
Detect network card:    [O]
Configure network:      [O]
Detect CD:              [O]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [O]
Install base system:    [O]
Clock/timezone setup:   [O]
User/password setup:    [O]
Install tasks:          [O]
Install boot loader:    [E]
Overall install:        [ ]


I tried several attempts, with different partitioning.

In each case, I preserved partition 1, which held a Windows Vista partition.
The free space was either partitioned into a swap and a root partition, or
was used as an encrypted partition with LVM holding a swap and root logical
volume.  I also tried several choices about what partitions were bootable.
I didn't really know what this should have been, which may well have been
part of the problem.  One of the choices I tried was to let the installer
automatically partition the free space.

For all of these choices, when I got to the Grub screen, the installer
did not recognize the Vista installation.  Eventually, I went ahead anyway
and let grub install.  But the installation to the MBR got a fatal error,
and trying to let grub install elsewhere eventually got my system pretty
messed up.  Telling grub to install at /dev/sda2 finally did it in and its
not bootable now.  Next step will be to try a clean install to the entire
drive, overwriting the Vista.

As a second oddity, once when I was at the Popularity Contest screen,
I hit the Go Back button.  This was a mistake, as it locked up the installation
and I eventually had to restart the machine and installation to unfreeze it.

Thanks for all the great work you people do.  I hope this report helps make
Debian a bit better.

--- End Message ---
--- Begin Message ---
reassign 701201 src:linux
retitle 701201 libata.atapi_passthru16=0 is needed by some hardware
forcemerge 690985 686954


thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given.

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


Attachment: signature.asc
Description: This is a digitally signed message part.

--- End Message ---

Reply to: