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

Bug#606976: marked as done (Kernel panic with Squeeze (AMD64) d-i beta 2)



Your message dated Sun, 21 Jul 2013 14:32:43 +0200
with message-id <201307211433.01341.holger@layer-acht.org>
and subject line dealing with old debian-installer bugs
has caused the Debian Bug report #606976,
regarding Kernel panic with Squeeze (AMD64) d-i beta 2
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.)


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

Boot method: CD and USB stick
Image version: http://cdimage.debian.org/cdimage/squeeze_di_beta2/amd64/iso-cd/debian-squeeze-di-beta2-amd64-netinst.iso
Date: Dec 13, 2010

Machine: Dell XPS 630i
Processor: Core 2 Quad 2.4 GHz
Memory: 4 GB
Partitions: N/A

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

Initial boot:           [E ]
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:

I've tried d-i beta 2 on Dell XPS 630i.  I first tried creating a USB
memory stick with the installer .iso on it (following a standard
procedure); the install USB stick works on my other computer (Lenovo
T410s).  However, on 630i it always fails at the beginning of the
install process.  The message, when kernel panics, typically goes like
this:

... (no apparent error messages thru this point) ...
[0.597991] List of all partitions:
[0.600310] No filesystem could mount root, tried:
[0.602749] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(8,3)
... (call trace output after this) ...

(This output is from an attempt to use CD install medium.)

I have tried adding rootdelay=10 option for the kernel, without any effect.

I have observed the same symptom with the netinst .iso burned on a
blank CD.  In fact, I have never been able to use d-i successfully on
630i (I've tried the same thing several months ago).  Last time I
installed Debian, I had to install off a Lenny install medium and then
do dist-upgrade.

Is there any way to get Squeeze d-i to work on this machine?  Any help
is appreciated.



--- End Message ---
--- Begin Message ---
reassign 716710 preseed,release-notes
forcemerge 704881 552563
tags 633128 + confirmed
reassign 633128 src:linux,kernel-wedge
affects 633128 debian-installer
reassign 653391 archdetect
forcemerge 653390 653391 
reassign 655579 rootskel-gtk
reassign 690246 partman-lvm
affects 690246 debian-installer
severity 699430 wishlist
reassign 655124 kernel-wedge
affects 655124 debian-installer
thanks

Hi,

thank you for submitting bug reports concering debian-installer, 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 and/or
- they are wishlist but rather special + exotic and not have been acted on for 
years. (See http://blog.liw.fi/posts/wishlist-bugs/ why it's often useful to 
close wishlist bugs.)

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 - and that's 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: