Your message dated Wed, 08 Sep 2010 03:58:02 +0000
with message-id <[email protected]>
and subject line Closing old installation report #320480
has caused the Debian Bug report #320480,
regarding Bugreport Package: installation-reports
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 [email protected]
immediately.)
--
320480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=320480
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: installation-reports
Debian-installer-version: Linux-magazine.de
uname -a: Linux barmaglot 2.6.8-2-386 #1 Thu May 19 17:40:50 JST 2005
i686 GNU/Linux
Date: Sun Jul 24 2005
Method: Boot from DVD in the internal drive, install from external ATAPI
DVD drive hooked up with USB enclosure
Machine: Gericom 1st Supersonic M6T
Processor: Pentium III
Memory: 512MB
Root Device: IDE
Root Size/partition table: not relevant
Output of lspci and lspci -n:
lspci:
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo
PRO133x] (rev c4)
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo
MVP3/Pro133x AGP]
0000:00:06.0 Communication controller: Lucent Microelectronics LT WinModem
0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super
South] (rev 40)
0000:00:07.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1 Controller (rev 1a)
0000:00:07.4 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super
ACPI] (rev 40)
0000:00:07.5 Multimedia audio controller: VIA Technologies, Inc.
VT82C686 AC97 Audio Controller (rev 50)
0000:00:09.0 Ethernet controller: Accton Technology Corporation EN-1216
Ethernet Adapter (rev 11)
0000:00:0c.0 CardBus bridge: O2 Micro, Inc. OZ6933 Cardbus Controller
(rev 01)
0000:00:0c.1 CardBus bridge: O2 Micro, Inc. OZ6933 Cardbus Controller
(rev 01)
0000:00:0d.0 FireWire (IEEE 1394): Lucent Microelectronics FW323 (rev 04)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon
Mobility M6 LY
lspci -n:
0000:00:00.0 0600: 1106:0691 (rev c4)
0000:00:01.0 0604: 1106:8598
0000:00:06.0 0780: 11c1:0450
0000:00:07.0 0601: 1106:0686 (rev 40)
0000:00:07.1 0101: 1106:0571 (rev 06)
0000:00: 07.2 0c03: 1106:3038 (rev 1a)
0000:00:07.4 0601: 1106:3057 (rev 40)
0000:00:07.5 0401: 1106:3058 (rev 50)
0000:00:09.0 0200: 1113:1216 (rev 11)
0000:00:0c.0 0607: 1217:6933 (rev 01)
0000:00:0c.1 0607: 1217:6933 (rev 01)
0000:00:0d.0 0c00: 11c1:5811 (rev 04)
0000:01:00.0 0300: 1002:4c59
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked: [O]
Configure network HW: [O]
Config network: [O]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Create file systems: [O]
Mount partitions: [O]
Install base system: [E]
Install boot loader: [O]
Reboot: [E]
Comments/Problems:
Installer failed to access internal CDRW-DVDROM drive from wich it was
started (just after the partitioning) to install packages.
I have bought the 01/2006 issue of the Linux-Magazin.de with Debian
Sarge 3.1 r0a to install it on my Gericom 1st Supersonic M6T laptop.
I can boot fine from the built-in DVD and all my hardware gets
detected, just when the base system should get installed (just after
the partitioning) the installer can not find the installation DVD anymore.
To solve this problem I have connected an external USB DVD Drive but
booted still from the built-in DVD drive. Then I waited until the
installer stumbled, unmounted /cdrom, put the Debian DVD into the
external drive and remounted the external drive under /cdrom. In my case
it was "mount /dev/scsi/host0/bus0/target0/cd /cdrom". To get to the
command line prompt I have used Alt+F2.
Similar problems were seen while using Mandrake Linux up to 10.1 but its
installation allways went fine with this drive.
This is what comes in /var/log/messages
Jul 24 16:17:52 barmaglot kernel: hdc: cdrom_decode_status: status=0x51
{ DriveReady SeekComplete Error }
Jul 24 16:17:52 barmaglot kernel: hdc: cdrom_decode_status:
error=0x40LastFailedSense 0x04
Jul 24 16:17:58 barmaglot kernel: hdc: cdrom_decode_status: status=0x51
{ DriveReady SeekComplete Error }
Jul 24 16:17:58 barmaglot kernel: hdc: cdrom_decode_status:
error=0x40LastFailedSense 0x04
Jul 24 16:18:04 barmaglot kernel: hdc: cdrom_decode_status: status=0x51
{ DriveReady SeekComplete Error }
Jul 24 16:18:04 barmaglot kernel: hdc: cdrom_decode_status:
error=0x40LastFailedSense 0x04
Jul 24 16:18:10 barmaglot kernel: hdc: cdrom_decode_status: status=0x51
{ DriveReady SeekComplete Error }
Jul 24 16:18:10 barmaglot kernel: hdc: cdrom_decode_status:
error=0x40LastFailedSense 0x04
Jul 24 16:18:11 barmaglot kernel: hdc: ATAPI reset complete
Jul 24 16:18:16 barmaglot kernel: hdc: cdrom_decode_status: status=0x51
{ DriveReady SeekComplete Error }
Jul 24 16:18:16 barmaglot kernel: hdc: cdrom_decode_status:
error=0x40LastFailedSense 0x04
Comment: here I have manually ejected the disk to reinsert it.
Jul 24 16:18:21 barmaglot kernel: hdc: tray open
Jul 24 16:18:21 barmaglot kernel: end_request: I/O error, dev hdc,
sector 8532500
Jul 24 16:18:21 barmaglot kernel: hdc: tray open
Jul 24 16:18:21 barmaglot kernel: end_request: I/O error, dev hdc,
sector 8532504
Jul 24 16:18:21 barmaglot kernel: hdc: tray open
Jul 24 16:18:21 barmaglot kernel: end_request: I/O error, dev hdc,
sector 8532508
As for the Reboot error:
I had to boot in the safe mode first time after the installation
finished. Next time everything went OK.
syslog.tar.gz
Description: GNU Zip compressed data
--- 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 ---
