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

Bug#477268: marked as done (submit@bugs.debian.org)



Your message dated Wed, 08 Sep 2010 03:58:44 +0000
with message-id <E1OtBo4-0006EM-FO@ravel.debian.org>
and subject line Closing old installation report #477268
has caused the Debian Bug report #477268,
regarding submit@bugs.debian.org
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.)


-- 
477268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477268
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.
Image version: <Full URL to image you downloaded is best> 4.0.r3 netinst iso.
Date: <Date and time of the install> 17-4-2008 to 22-4-2008.

Machine: Whitebox, Asus P5K Premium Wi-fi motherbaird with Perc 3CDL raid controller, PCI MX200 graphics card.
Processor: dual core celeron 1.6Ghz
Memory: 3.5Gb
Partitions: fails before this.

Output of lspci -nn and lspci -vnn:  fails before this.

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

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

Comments/Problems:

<Description of the install, in prose, and any thoughts, comments
      and ideas you had during the initial install.>

Several problems were encountered...the Asus P5K permium wi-fi motherboard has 6 internal sata ports (ICH9R) and one ide port with two e-sata (J-micron). The cd would only go through the detect CD stage if the sata dvd was on sata port 1, I tried it initially on 4 then 3 and it didnt work.

I next moved to an IDE DVD and got the same problem. I think what was happening was the cd detection was off looking for a cdrom on the raid card or adaptec 3940....at each test it locked up the box at 8% but the scsi hds lights were flashing, each in turn briefly.

When I went back to the sata dvd drive and port 1 on the ICH9R the cd detect went fine. However I then encountered a terminal issue with the Megaraid module so was unable to install etch.

I went back to 3.1 netinst cd and installed without issue on a std 2.4 kernel. I then upgraded to etch via apt-get -y dist-upgrade. This ran fine until I tried to install a 2.6 kernel, then it locked up during boot at the megaraid_mbox point while looking for disks....something about aborting and waiting 300secs....over and over.

So this appears to be a problem with the megaraid module in 2.6? I have also found that any kernel source 2.4.27+ from kernel org fails at the megraid module also....The debianised kernel source 2.4.27-4 can be compiled and boots fine....anything else locks out at the megraid module. The debian stock kernel images 2.4.27-3-386 and 2.4.27-4-686-smp boot fine as stock kernels.

I also tried kernel 2.6.8 as a kernel.org source, locks out at the megraid_mbox module, same issue as a stock debian 2.6.x image.

At the moment I am trying to locate a 2.4.36-3 debianised package source to see if that is compilable and bootable....

regards

Steven



















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