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

Bug#265793: marked as done (debian-installer report)



Your message dated Wed, 08 Sep 2010 03:57:34 +0000
with message-id <E1OtBmw-0003rP-OS@ravel.debian.org>
and subject line Closing old installation report #265793
has caused the Debian Bug report #265793,
regarding debian-installer 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.)


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

INSTALL REPORT

Debian-installer-version: "sarge-i386-1-20040807.iso" of size 678461440 bytes from www.debian.org, downloaded at 2004-08-14.
uname -a: Linux starfall 2.6.7-1-386 #1 Thu Jul 8 05:08:04 EDT 2004 i686 GNU/Linux
Date: 2004-08-15.
Method: Boot from iso, install basic system from cdrom. Used 'expert26' boot option. (Afterwards, upgraded to unstable via network.)

Machine: Toshiba Satelite P20-103 (laptop)
Processor: P4 2.8ghz with hyper threading
Memory: 512mb
Root Device: IDE. /dev/hda5.
Root Size/partition table:  

Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/hda5              4807056    522756   4040116  12% /
tmpfs                   258464         0    258464   0% /dev/shm
/dev/hda2                37635     13614     22013  39% /boot
/dev/hda6              5739876   1711568   3736732  32% /home
/dev/hda1             47802872  13347416  34455456  28% /media/dos_c
/dev/sda1            292889760 277569120  15320640  95% /media/usb0
/dev/sdb1            292889760  92326176 200563584  32% /media/usb1

Output of lspci and lspci -n:


0000:00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
0000:00:01.0 PCI bridge: Intel Corp. 82865G/PE/P PCI to AGP Controller (rev 02)
0000:00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 (rev 02)
0000:00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 (rev 02)
0000:00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 (rev 02)
0000:00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #4 (rev 02)
0000:00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2)
0000:00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02)
0000:00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra ATA 100 Storage Controller (rev 02)
0000:00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02)
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
0000:00:1f.6 Modem: Intel Corp. 82801EB/ER (ICH5/ICH5R) AC'97 Modem Controller (rev 02)
0000:01:00.0 VGA compatible controller: nVidia Corporation NV34M [GeForce FX Go 5200] (rev a1)
0000:02:00.0 FireWire (IEEE 1394): Texas Instruments TSB43AB21 IEEE-1394a-2000 Controller (PHY/Link)
0000:02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
0000:02:04.0 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to Cardbus Bridge with ZV Support (rev 32)
0000:02:04.1 CardBus bridge: Toshiba America Info Systems ToPIC95 PCI to Cardbus Bridge with ZV Support (rev 32)
0000:02:06.0 System peripheral: Toshiba America Info Systems SD TypA Controller (rev 03)
0000:03:00.0 Network controller: 3Com Corporation 3com 3CRWE154G72 [Office Connect Wireless LAN Adapter] (rev 01)


0000:00:00.0 0600: 8086:2570 (rev 02)
0000:00:01.0 0604: 8086:2571 (rev 02)
0000:00:1d.0 0c03: 8086:24d2 (rev 02)
0000:00:1d.1 0c03: 8086:24d4 (rev 02)
0000:00:1d.2 0c03: 8086:24d7 (rev 02)
0000:00:1d.3 0c03: 8086:24de (rev 02)
0000:00:1d.7 0c03: 8086:24dd (rev 02)
0000:00:1e.0 0604: 8086:244e (rev c2)
0000:00:1f.0 0601: 8086:24d0 (rev 02)
0000:00:1f.1 0101: 8086:24db (rev 02)
0000:00:1f.3 0c05: 8086:24d3 (rev 02)
0000:00:1f.5 0401: 8086:24d5 (rev 02)
0000:00:1f.6 0703: 8086:24d6 (rev 02)
0000:01:00.0 0300: 10de:0324 (rev a1)
0000:02:00.0 0c00: 104c:8026
0000:02:01.0 0200: 10ec:8139 (rev 10)
0000:02:04.0 0607: 1179:0617 (rev 32)
0000:02:04.1 0607: 1179:0617 (rev 32)
0000:02:06.0 0880: 1179:0805 (rev 03)
0000:03:00.0 0280: 10b7:6001 (rev 01)


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

Initial boot worked:    [O]
Configure network HW:   [E]
Config network:         [O]
Detect CD:              [O]
Load installer modules: [ ]
Detect hard drives:     [O]
Partition hard drives:  [O]
Create file systems:    [O]
Mount partitions:       [O]
Install base system:    [O]
Install boot loader:    [O]
Reboot:                 [O]

Comments/Problems:

I put "error" for configure network HW, since the installer
did not detect the prism54 based wireless card. I guess this
is because of the missing firmware binary which is 
required for operation. I put the binary in place from an usb disk
manually after completing the install, but it would be nice
if it was possible for the user to provide this binary at 
install time (via usb keydrive, floppy disk, whatever) to 
be able to do a netinst.

In the partition editor, the character graphics symbols
are not explained anywhere; it took me a while to guess that the 
"lightning symbol" meant "bootable". There should be an
explanation of the symbols.

During install, I also got these error messages in a prompt:

Aug 14 23:54:57 hw-detect: Missing modules 'i810-tco (Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Bridge), 8139too (Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+), ide-mod (Linux IDE driver), ide-probe-mod (Linux IDE probe driver), ide-detect (Linux IDE detection), ide-floppy (Linux IDE floppy), eth1394 (FireWire ethernet)
Aug 14 23:57:05 hw-detect: Missing modules 'i810-tco (Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Bridge), ide-scsi (Linux IDE-SCSI emulation layer), ide-mod (Linux IDE driver), ide-probe-mod (Linux IDE probe driver), ide-detect (Linux IDE detection), ide-floppy (Linux IDE floppy)
Aug 14 23:57:56 hw-detect: Missing modules 'i810-tco (Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Bridge), ide-scsi (Linux IDE-SCSI emulation layer), ide-mod (Linux IDE driver), ide-probe-mod (Linux IDE probe driver), ide-detect (Linux IDE detection), ide-floppy (Linux IDE floppy)

Although they didn't seem to prevent anything from working.


After rebooting from harddisk, startup sequence appeared to hang
at "Starting MTA" (exim4). Probably because the network was unreachable?
(I configured the ethernet card during setup but it is unplugged).
Hitting Ctrl-C caused bootup to continue. It's kind of strange that
the MTA is started at all, considering it has not yet been configured
(the GUI for configuring the MTA was presented at a later stage).


At the prompt to configure keyboard layout, I had to choose between
"regular" and "USB" (can't remember the exact prompt). The USB listing
was missing a lot of layouts (such as "Norwegian"), so I just picked
"regular keyboard" and "Norwegian". I have an USB keyboard attached
to the laptop, which of course also has a built-in keyboard. 
But I thought both keyboards HAD to use the same keymap?

It would be nice if libncurses5-dev is available on the first CD,
so that "make menuconfig" for compiling kernels is possible.


After getting the basic system running, I then proceeded to upgrade
to unstable.




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