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

Bug#681673: marked as done (amd64 installer fails)

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 #681673,
regarding amd64 installer fails
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

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

The amd64 installer worked fine for lenny.

Not so for squeeze.

I have tried to use the net install disk, and the CD isos.  No go.

The CD images will not boot. I get the "... et al" line at the top and that's it. Nothing more.

I got partway through the net install but that only succeeded in crippling the lenny to squeeze transition. Now I'm not sure where I am. The shift over from GRUB to GRUB 2 also got buggered, despite chain loading properly... I now have no access to any of the linux system. I need to be able to boot from a disk, and that is no longer possible.

Can't load debian from the net, can't load debian from the CDs. Can't load debian...



Bronson Crothers
17 Charles St.
Orono ME 04473

Phone: 207 866 0405

de AA1ZB

--... ...--

Email: bcrothers@roadrunner.com


--- 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: