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

Bug#410211: marked as done (Debian Installation report)

Your message dated Wed, 08 Sep 2010 03:58:23 +0000
with message-id <E1OtBnj-0005VG-ND@ravel.debian.org>
and subject line Closing old installation report #410211
has caused the Debian Bug report #410211,
regarding Debian Installation 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.)


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

Boot method: CD
Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/ arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso 
Date: Feb 7, 2007

Machine: Apple Mac Pro
Processor: (2) 2.66 GHz Duel-Intel Xeon
Memory: 3 GB
Partitions:
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:    [O]
Overall install:        [E]
Comments/Problems: booted with expert irqpoll, installer wants to try install a mess of IDE chipset controllers (does not identify Intel 5000X chipset?), disabled IDE chipset drivers from floppy to bottom of first page on the Feb 7 install (disabled bigger set on second attempt on Feb 8). Installed LILO to MBR.
Seeing "the drive appears to be confused" messages on boot of new system (which uses 2.6.18). /sbin/lilo -v 5 runs on clean system. Installed system boots with minimal desktop install from CD with periodic "the drive appears to be confused" messages.
Installing a standard set of desktop software causes the "the drive appears to be confused" messages to appear continuously, making the system unusable.
Changing append="irqpoll" to append="apic" in /etc/lilo.conf, running /sbin/lilo -v 5, and rebooting, removes the drive confused problem (disables the PATA controller? and thereby the DVD drive).
HOWEVER, then /sbin/lilo hangs preventing any further updates to the system. The problem is specific to the 2.6.18 kernel on this system. The 2.6.17 kernel does not have this problem. Unable to install 2.6.17 kernel because is has been removed from the servers. Rebuilding system again with RC1 to get back to 2.6.17.
The Feb. 7, 2007 daily build is the first daily build that I could get to install on this machine, before this only RC1 worked.
The second attempt using the Feb 7 daily image (on Feb 8) disabled even more IDE chipset controllers (previous attempts along this line have not been successful). I have been unable to find documentation in the install FAQ and the Debian web sites on what chipsets are covered by which drivers, I believe that information might be somewhere in the kernel configuration interfaces; however, nothing there refers the Intel 5000X chipset so it's rather a guess at which IDE chipset drivers to keep. Keeping them all may have prevented my previous attempts installing with the daily builds using the 2.6.18 kernel or a mod to the installer or the Debian 2.6.18 kernel between Feb 1 and Feb 7 daily builds has fixed part of the problem I was seeing.

--- End Message ---
--- Begin Message --- 
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
  Installer.
- indications in the installation report give the feeling that
  the reported problem waslying in another software, unrelated to
  D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
  fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful


The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet. 

In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.

You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.

If some problems are found, please report them with a new bug sent
against installation-reports.

Many thanks for your understanding and your help improving Debian,
past and present.

--- End Message ---
Reply to: