Your message dated Wed, 17 Jul 2013 01:36:44 +0200 with message-id <201307170137.05268.holger@layer-acht.org> and subject line dealing with old boot related bugs has caused the Debian Bug report #618929, regarding Debian bootup/install bug report 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 immediately.) -- 618929: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618929 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: "Mike Tremblay" <mat715@comcast.net>, <submit@bugs.debian.org>
- Subject: Re: Debian bootup/install bug report
- From: "Mike Tremblay" <mat715@comcast.net>
- Date: Sat, 19 Mar 2011 11:07:24 -0600
- Message-id: <1891E407196A4989A2CA857AA86696B2@yourze8cxvr8tt>
Package: InstallerProblem: Will not boot after installation
System: ~2000 vintage HP Vecta XU, 6/200, system D4365N, dual Pentium II processors, 64 MB RAM, three hard drives - 200G IDE, two 1.3 G SCSI (Quantum Fireball), network card, no USB
The most common outcome of an installation session is that the bootup step at the end of the session results in the letters "GRUB" appearing in the upper left corner of the screen with the blinking cursor to the right of the "B", and nothing else. The system does not respond to any keystrokes, or combination of CTRL-<key>, ALT-<key>, etc. It seems like the system is waiting for keyboard input, but the keyboard is not enabled. If I had a responsive keyboard AND I knew what to type, this could be an acceptable outcome, since it does occur most times.
What I've tried: All combinations of discs (all three drives plugged in, each one separately, all combinations of two drives). The drives all appear to be accessed but the boot ultimately fails as described above.
I've tried most combinations of answering the partitioning questions and placement of the boot sector.
The failures are not all as stated above; it's just the most common outcome. Other results are "GRUB" being continuously written to the screen, until I power off.
I was able to get the boot to succeed once, but that particular system build led to other problems causing me to attempt a second install. This one time the result was that the system would, after powering on and all the verbiage of the boot up process, presents me with a login prompt, accepts my login and allows me to use the system. I was able to run with this system for a couple of weeks, loading packages, etc. until I filled the discs and had to start over. The disc full issue occurred because the IDE drive (most of the system's capacity) was not mounted. I did not realize this until the disc full failure.
The version of Debian is 2.4. I have a 15 CD set, purchased in roughly 2004. Last week I downloaded disc image 1 of Debian 6.0 in hopes that the boot problem has been fixed, but the results are the same.
Thanks,
Mike Tremblay
--- End Message ---
--- Begin Message ---
- To: 695961-done@bugs.debian.org, 657431-done@bugs.debian.org, 657430-done@bugs.debian.org, 618929-done@bugs.debian.org, 612135-done@bugs.debian.org, 583735-done@bugs.debian.org, 572446-done@bugs.debian.org
- Subject: dealing with old boot related bugs
- From: Holger Levsen <holger@layer-acht.org>
- Date: Wed, 17 Jul 2013 01:36:44 +0200
- Message-id: <201307170137.05268.holger@layer-acht.org>
Hi, thank you for submitting installation reports, much appreciated. I read through all the ("boot" related) bugs mentioned here and am closing them now as - 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 were (very) old. If I've closed a bug incorrectly please do reply or just file a new one - thats often better, as the bug log will be more clear. cheers, HolgerAttachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---