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

Bug#468357: marked as done (win32-loader: installer won't load after rebooting)

Your message dated Wed, 10 Nov 2010 13:32:51 +0100
with message-id <201011101332.52833.didier@raboud.com>
and subject line Bug: #468357: win32-loader: installer won't load after rebooting
has caused the Debian Bug report #468357,
regarding win32-loader: installer won't load after rebooting
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

468357: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468357
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: win32-loader
Severity: normal


I was trying to install Debian from the Windows XP Home operating
system of a Dell Dimension DIMC521 desktop.

CPU: AMD Athlon(tm) 64 Processor 3200+ 2.00GHz
Memory: 512MB
Graphic card: on board NVIDIA GeForce 6150 LE
Disk: 80GB with WinXP Home preloaded
Installer loader: http://goodbye-microsoft.com/

Problem: Loader ran well in Windows. After rebooting, the entry
labeled "Debian Installer" was shown in the start up menu, which
should be correct. After I selected that entry, a screen appeared
with the following words:

Welcome to GRUB!
hd0,2 [Linux-bzImage, setup=0x1e00, size=0x16f3cf]

And it hung after a few seconds showing a black screen. I could
reboot back to Windows with no problem.



Wei Chen

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-3-686 (SMP w/2 CPU cores)
Locale: LANG=en_HK.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--- End Message ---
--- Begin Message ---
Version: 0.6.10

Hi Wei Chen, 

As the bugreport mentions, the bug #468357 you reported was not caused by win32-
loader, but by bad hardware and/or by the kernel failing to properly handle it.

I am hereby closing this bug as solved in the Lenny version of win32-loader. 
Please re-open if you think this problem is still alive (and caused by win32-


OdyX, win32-loader co-maintainer.
Didier Raboud, proud Debian Maintainer (DM).
CH-1020 Renens

--- End Message ---

Reply to: