Bug#271122: sarge netinst 2004-09-09: display manager missing, X resolution&refresh wrong
Package: installation-reports
INSTALL REPORT
Debian-installer-version: http://cdimage.debian.org/pub/cdimage-testing/daily/i386/20040909/sarge-i386-netinst.iso
kernel: 2.4.27
Date: Sep 11 2004 about 01:00-11.00 EEST
Method: sarge-i386-netinst, burned to CDRW and booted off that.
ftp.fi.debian.org, no proxy, 1024/768 ADSL line w/ DHCP
Machine: self-built x86 PC
Processor: 1.3 GHz Athlon
Memory: 1GB
Root Device: /dev/hdc7
Root Size/partition table:
Disk /dev/hdc: 80.0 GB, 80054059008 bytes
16 heads, 63 sectors/track, 155114 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/hdc1 * 1 40635 20480008+ 7 HPFS/NTFS
/dev/hdc2 40636 155114 57697416 f W95 Ext'd (LBA)
/dev/hdc5 40636 81270 20480008+ 83 Linux
/dev/hdc6 81271 121905 20480008+ b W95 FAT32
/dev/hdc7 * 121906 155114 16737304+ 83 Linux
Disk /dev/hdd: 120.0 GB, 120060444672 bytes
16 heads, 63 sectors/track, 232632 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/hdd1 1 232632 117246496+ b W95 FAT32
Output of lspci and lspci -n:
(this was run after booting back to my normal sid install)
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 02)
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
0000:00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22)
0000:00:04.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10)
0000:00:04.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 10)
0000:00:04.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 10)
0000:00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30)
0000:00:09.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
0000:00:09.1 Input device controller: Creative Labs SB Audigy MIDI/Game port (rev 04)
0000:00:09.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04)
0000:00:0b.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
0000:00:11.0 Unknown mass storage controller: Promise Technology, Inc. PDC20265 (FastTrak100 Lite/Ultra100) (rev 02)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R100 QD [Radeon 7200]
0000:00:00.0 0600: 1106:0305 (rev 02)
0000:00:01.0 0604: 1106:8305
0000:00:04.0 0601: 1106:0686 (rev 22)
0000:00:04.1 0101: 1106:0571 (rev 10)
0000:00:04.2 0c03: 1106:3038 (rev 10)
0000:00:04.3 0c03: 1106:3038 (rev 10)
0000:00:04.4 0600: 1106:3057 (rev 30)
0000:00:09.0 0401: 1102:0004 (rev 04)
0000:00:09.1 0980: 1102:7003 (rev 04)
0000:00:09.2 0c00: 1102:4001 (rev 04)
0000:00:0b.0 0200: 8086:1229 (rev 08)
0000:00:11.0 0180: 105a:0d30 (rev 02)
0000:01:00.0 0300: 1002:5144
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: [O]
Install boot loader: [O]
Reboot: [O]
Comments/Problems:
- No display manager installed by default, so GUI didn't start up
after boot automatically. Had to use startx.
- X stuck at 1024x768@60 Hz, so apparently monitor detection didn't
work.
- arts error displayed when starting X: "device /dev/dsp can't be
opened (No such device)" Apparently 2.4.27 doesn't support the
Audigy2. Installing a 2.6 kernel image fixed that. The master
volume was set to zero by default, though.
- Some of the package configuration questions asked are really arcane
and provide little or no explanation on what the question means.
Examples are: libpango1.0-common, kpilot, xserver-xfree86, libsensors3.
For more information see:
http://nostromo.dynalias.org/~jplauril/debianinstall/
Luckily picking the defaults works fine for most packages.
- Minor nitpick/wishlist item: During the install process
language/region/keyboard gets asked at least three times: in the
beginning, during the configuration of X and when starting KDE. I do
understand that making all the various applications do the right
thing by default may be more trouble than it's worth.
I was pleasantly surprised by how easy it was to install the base
system and to get it to boot. Just pick language, keyboard, region,
partition to install to, pound on enter a few times and bam, you have
a working base install.
Reply to: