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

Bug#412059: marked as done (installation-report)



Your message dated Wed, 28 Feb 2007 15:31:34 +0100
with message-id <200702281531.34937.elendil@planet.nl>
and subject line Bug#412059: installation-report
has caused the attached Bug 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: installation-reports

Boot method: DVD
Image version: http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-dvd/debian-testing-i386-DVD-1.iso
              Debian GNU/Linux testing "Etch" - Official Snapshot
i386 DVD Binary-1 20070221-00:48
Date: 2007-02-23

Machine: Home-brewed
Processor: AMD Athlon XP 2600+
Memory: 631.35MB
Partitions:
Partition    Format  Size         Mountpoint
/dev/hdb1    ext3     41286796    /
/dev/hda1    ntfs     67416740    /media/hda1
/dev/hdb2    ext3     10317860    /home
/dev/hda2    ext3      9068648    /media/hda2
/dev/hda4    ext3      1011960    /media/hda3
/dev/hdb4    vfat    106586240    /media/hdb4

Output of lspci -nn and lspci -vnn:
00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8377 [KT400/KT600
AGP] Host Bridge [1106:3189] (rev 80)
00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8237 PCI Bridge [1106:b198]
00:0a.0 Multimedia audio controller [0401]: Creative Labs SB Audigy
[1102:0004] (rev 03)
00:0a.1 Input device controller [0980]: Creative Labs SB Audigy Game
Port [1102:7003] (rev 03)
00:0a.2 FireWire (IEEE 1394) [0c00]: Creative Labs SB Audigy FireWire
Port [1102:4001]
00:0c.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ [10ec:8139] (rev 10)
00:0f.0 RAID bus controller [0104]: VIA Technologies, Inc. VIA VT6420
SATA RAID Controller [1106:3149] (rev 80)
00:0f.1 IDE interface [0101]: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571]
(rev 06)
00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI
USB 1.1 Controller [1106:3038] (rev 81)
00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI
USB 1.1 Controller [1106:3038] (rev 81)
00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI
USB 1.1 Controller [1106:3038] (rev 81)
00:10.3 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI
USB 1.1 Controller [1106:3038] (rev 81)
00:10.4 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0
[1106:3104] (rev 86)
00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8237 ISA bridge
[KT600/K8T800/K8T890 South] [1106:3227]
01:00.0 VGA compatible controller [0300]: nVidia Corporation Unknown
device [10de:0222] (rev a1)

00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8377 [KT400/KT600
AGP] Host Bridge [1106:3189] (rev 80)
       Subsystem: ASRock Incorporation K7VT6 motherboard [1849:3189]
       Flags: bus master, 66MHz, medium devsel, latency 8
       Memory at e0000000 (32-bit, prefetchable) [size=64M]
       Capabilities: [80] AGP version 3.5
       Capabilities: [c0] Power Management version 2

00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8237 PCI Bridge
[1106:b198] (prog-if 00 [Normal decode])
       Flags: bus master, 66MHz, medium devsel, latency 0
       Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
       Memory behind bridge: dbe00000-dfefffff
       Prefetchable memory behind bridge: bbd00000-dbcfffff
       Capabilities: [80] Power Management version 2

00:0a.0 Multimedia audio controller [0401]: Creative Labs SB Audigy
[1102:0004] (rev 03)
       Subsystem: Creative Labs SB0090 Audigy Player/OEM [1102:0053]
       Flags: bus master, medium devsel, latency 32, IRQ 201
       I/O ports at d000 [size=32]
       Capabilities: [dc] Power Management version 2

00:0a.1 Input device controller [0980]: Creative Labs SB Audigy Game
Port [1102:7003] (rev 03)
       Subsystem: Creative Labs SB Audigy MIDI/Game Port [1102:0040]
       Flags: bus master, medium devsel, latency 32
       I/O ports at ec00 [size=8]
       Capabilities: [dc] Power Management version 2

00:0a.2 FireWire (IEEE 1394) [0c00]: Creative Labs SB Audigy FireWire
Port [1102:4001] (prog-if 10 [OHCI])
       Subsystem: Creative Labs SB Audigy FireWire Port [1102:0010]
       Flags: bus master, medium devsel, latency 32, IRQ 177
       Memory at dfffb800 (32-bit, non-prefetchable) [size=2K]
       Memory at dfff4000 (32-bit, non-prefetchable) [size=16K]
       Capabilities: [44] Power Management version 2

00:0c.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ [10ec:8139] (rev 10)
       Subsystem: Realtek Semiconductor Co., Ltd. RT8139 [10ec:8139]
       Flags: bus master, medium devsel, latency 32, IRQ 193
       I/O ports at cc00 [size=256]
       Memory at dfffb700 (32-bit, non-prefetchable) [size=256]
       Capabilities: [50] Power Management version 2

00:0f.0 RAID bus controller [0104]: VIA Technologies, Inc. VIA VT6420
SATA RAID Controller [1106:3149] (rev 80)
       Subsystem: ASRock Incorporation K7VT6 motherboard [1849:3149]
       Flags: bus master, medium devsel, latency 32, IRQ 169
       I/O ports at e800 [size=8]
       I/O ports at e400 [size=4]
       I/O ports at e000 [size=8]
       I/O ports at dc00 [size=4]
       I/O ports at d800 [size=16]
       I/O ports at d400 [size=256]
       Capabilities: [c0] Power Management version 2

00:0f.1 IDE interface [0101]: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571]
(rev 06) (prog-if 8a [Master SecP PriP])
       Subsystem: ASRock Incorporation K7VT2/K7VT6 motherboard [1849:0571]
       Flags: bus master, medium devsel, latency 32, IRQ 169
       I/O ports at fc00 [size=16]
       Capabilities: [c0] Power Management version 2

00:10.0 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI
USB 1.1 Controller [1106:3038] (rev 81) (prog-if 00 [UHCI])
       Subsystem: ASRock Incorporation K7VT6 [1849:3038]
       Flags: bus master, medium devsel, latency 32, IRQ 185
       I/O ports at bc00 [size=32]
       Capabilities: [80] Power Management version 2

00:10.1 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI
USB 1.1 Controller [1106:3038] (rev 81) (prog-if 00 [UHCI])
       Subsystem: ASRock Incorporation K7VT6 [1849:3038]
       Flags: bus master, medium devsel, latency 32, IRQ 185
       I/O ports at c000 [size=32]
       Capabilities: [80] Power Management version 2

00:10.2 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI
USB 1.1 Controller [1106:3038] (rev 81) (prog-if 00 [UHCI])
       Subsystem: ASRock Incorporation K7VT6 [1849:3038]
       Flags: bus master, medium devsel, latency 32, IRQ 185
       I/O ports at c400 [size=32]
       Capabilities: [80] Power Management version 2

00:10.3 USB Controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI
USB 1.1 Controller [1106:3038] (rev 81) (prog-if 00 [UHCI])
       Subsystem: ASRock Incorporation K7VT6 [1849:3038]
       Flags: bus master, medium devsel, latency 32, IRQ 185
       I/O ports at c800 [size=32]
       Capabilities: [80] Power Management version 2

00:10.4 USB Controller [0c03]: VIA Technologies, Inc. USB 2.0
[1106:3104] (rev 86) (prog-if 20 [EHCI])
       Subsystem: ASRock Incorporation K7VT6 motherboard [1849:3104]
       Flags: bus master, medium devsel, latency 32, IRQ 185
       Memory at dfffb500 (32-bit, non-prefetchable) [size=256]
       Capabilities: [80] Power Management version 2

00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VT8237 ISA bridge
[KT600/K8T800/K8T890 South] [1106:3227]
       Subsystem: ASRock Incorporation K7VT4 motherboard [1849:3227]
       Flags: bus master, stepping, medium devsel, latency 0
       Capabilities: [c0] Power Management version 2

01:00.0 VGA compatible controller [0300]: nVidia Corporation Unknown
device [10de:0222] (rev a1) (prog-if 00 [VGA])
       Subsystem: eVga.com. Corp. Unknown device [3842:a295]
       Flags: bus master, 66MHz, medium devsel, latency 248, IRQ 193
       Memory at de000000 (32-bit, non-prefetchable) [size=16M]
       Memory at c0000000 (32-bit, prefetchable) [size=256M]
       Memory at dd000000 (32-bit, non-prefetchable) [size=16M]
       Expansion ROM at dfee0000 [disabled] [size=128K]
       Capabilities: [60] Power Management version 2
       Capabilities: [44] AGP version 3.0

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

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

Comments/Problems:

There are three main things that could be improved.  They're not
really errors; more like annoyances.

First, several things about your "partitioner" are annoying:
- GUI mode is little different than text-based mode.  You really could
use a graphical
 partitioner, or at least, one that's less clunky.
- Using "expertgui" mode allowed the ntfs driver to be loaded, but the
installer wouldn't let me
 add the pre-existing ntfs partition anyway.  It had to be done by hand.
- The installer gave me no way to grant a regular user read-write
access to the pre-existing FAT32
 parition.  That also had to be done by hand.
- Since your installer was so good at detecting pre-existing
partitions and their various formats,
 why do I have to tell it that a FAT32 partition is a.......FAT32
partition?  What would have
 happened if I'd told the installer to mount the FAT32 partition as
an ext3 partition?  (Shudder.)

Second, while your general package selection is a whole lot better
than being dumped into dselect, it's
still not fine-grained enough.  I know you have a CD 1 for KDE users,
but there was no way to choose KDE
instead of GNOME using the DVD.

Finally, "installgui" should probably be the default, instead of
making the user explicitly choose it.

Don't hate me for saying this, but of all the installers I've seen,
(open)SUSE's is probably the best.

Thanks for producing the Debian Installer!
- Andrew Heil


--- End Message ---
--- Begin Message ---
On Friday 23 February 2007 10:18, Andrew Heil wrote:
> Comments/Problems:
> First, several things about your "partitioner" are annoying:
> - GUI mode is little different than text-based mode.  You really could
> use a graphical
>   partitioner, or at least, one that's less clunky.

We intend to work on this after Etch. Help needed and welcome.

> - Using "expertgui" mode allowed the ntfs driver to be loaded, but the
> installer wouldn't let me add the pre-existing ntfs partition anyway. 
> It had to be done by hand.
> - The installer gave me no way to grant a regular user read-write access
> to the pre-existing FAT32 parition.  That also had to be done by hand. 

This does not make sense. You can select existing partitions, set "keep 
existing data" (don't format) and set a mountpoint.

> - Since your installer was so good at detecting pre-existing
> partitions and their various formats,
>   why do I have to tell it that a FAT32 partition is a.......FAT32
> partition?  What would have
>   happened if I'd told the installer to mount the FAT32 partition as
> an ext3 partition?  (Shudder.)

You'd have to ask the person who originally wrote the partman code. 
Patches to improve this are welcome.

> Second, while your general package selection is a whole lot better
> than being dumped into dselect, it's
> still not fine-grained enough.  I know you have a CD 1 for KDE users,
> but there was no way to choose KDE
> instead of GNOME using the DVD.

Known and often discussed issue and something the tasksel maintainer feels 
fairly strongly about.

> Finally, "installgui" should probably be the default, instead of
> making the user explicitly choose it.

No, there are still too many issues with the graphical installer for it to 
be the default.

As your installation was successful, I'm closing your report. Thank you 
for submitting it and for your comments.

Cheers,
FJP

--- End Message ---

Reply to: