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

Bug#566310: marked as done (installation report for Squeeze (daily build))

Your message dated Sat, 20 Jul 2013 01:11:55 +0200
with message-id <201307200112.15052.holger@layer-acht.org>
and subject line dealing with old installation-reports
has caused the Debian Bug report #566310,
regarding installation report for Squeeze (daily build)
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.)


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

Boot method: USB stick<How did you boot the installer? CD? floppy? network?>
Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
               (Daily build #5 for Squeeze, "This build finished at
Fri Jan 22 15:47:45 UTC 2010."
               http://d-i.debian.org/daily-images/amd64/daily/hd-media/boot.img.gz
               Both linked from http://www.debian.org/devel/debian-installer/
Date: 22.Jan 2010, approximately 19:45 GMT

Machine: Dell XPS M1330
Processor: Intel Centrino
Memory: 2 GB
Partitions: irrelevant

Output of lspci -knn (or lspci -nn):

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

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

Comments/Problems:

After giving in language and keyboard information, the disks are
detected and the installer searches for an image on the installation
media, then gives a blue screen entitled: "Load installer components
from an installer ISO"
"No kernel modules were found. This probably is due to a mismatch
between the kernel used..."  etc.

The USB stick was prepared according to
http://www.debian.org/releases/squeeze/amd64/ch04s03.html.en using
4.3.1 Copying the files -- the easy way:
"For this installation method you will also need to download a CD
image. The installation image and the CD image must be based on the
same release of debian-installer. If they do not match you are likely
to get errors[4] during the installation."
-------
[4] The error message that is most likely to be displayed is that no
kernel modules can be found. This means that the version of the kernel
module udebs included on the CD image is different from the version of
the running kernel.

If the installation image and the CD image linked from the same page
do not match, I don't know how to make sure they match. This is
perhaps a mis-coordination in the daily builds or in the links
provided on http://www.debian.org/devel/debian-installer/

It failed the same way with the businesscard image:
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-businesscard.iso

Regards,
Mike

--- End Message ---
--- Begin Message --- 
Hi,

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 have been from a development phase where things were not stable and/or
- they are very old, more than 2.5 years.

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.


cheers,
        Holger

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: