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

Bug#277365: marked as done ((Mostly) successful installation report)



Your message dated Thu, 21 Oct 2004 09:55:35 +0200
with message-id <20041021075535.GA19007@gpm.stappers.nl>
and subject line Bug#277365: (Mostly) successful 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)

--------------------------------------
Received: (at submit) by bugs.debian.org; 19 Oct 2004 18:53:14 +0000
>From prefect_@gmx.net Tue Oct 19 11:53:14 2004
Return-path: <prefect_@gmx.net>
Received: from pop.gmx.net (mail.gmx.net) [213.165.64.20] 
	by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
	id 1CJz6f-00040a-00; Tue, 19 Oct 2004 11:53:13 -0700
Received: (qmail 28060 invoked by uid 65534); 19 Oct 2004 18:52:41 -0000
Received: from dsl-084-057-046-254.arcor-ip.net (EHLO localhost) (84.57.46.254)
  by mail.gmx.net (mp023) with SMTP; 19 Oct 2004 20:52:41 +0200
X-Authenticated: #5817363
From: Nicolai Haehnle <prefect_@gmx.net>
To: submit@bugs.debian.org
Subject: (Mostly) successful installation report
Date: Tue, 19 Oct 2004 20:57:20 +0200
User-Agent: KMail/1.7
MIME-Version: 1.0
Content-Type: multipart/signed;
  boundary="nextPart7576651.o5rT9SvUW8";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <[🔎] 200410192057.21801.prefect_@gmx.net>
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

--nextPart7576651.o5rT9SvUW8
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Package: installation-reports

Debian-installer-version: Daily netinst-cd, 18.10.04
uname -a: Linux sundown 2.6.8-1-386 #1 Thu Oct 7 02:21:16 EDT 2004 i686=20
GNU/Linux
Date: 19.10.2004
Method:=20
Boot from CD, bootloader command "linux26"
Networked using 100Mbit ethernet with a hardware router acting as DSL modem=
,=20
gateway, DHCP server etc.; no proxies or other unusual setup involved

Machine: Fujitsu Siemens Amilo M1425 M725 (i.e. a laptop)
Processor: Intel Pentium M 1.6 GHz
Memory: 512MB
Root Device: IDE /dev/hda
Root Size/partition table:=20
Disk /dev/hda: 80.0 GB, 80026361856 bytes
16 heads, 63 sectors/track, 155061 cylinders
Units =3D cylinders of 1008 * 512 =3D 516096 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1       46729    23551258+   7  HPFS/NTFS
/dev/hda2           46729       47956      618502+  82  Linux swap
/dev/hda3           47956       68277    10241437+  83  Linux  /
/dev/hda4           68277      155056    43736931+   f  W95 Ext'd (LBA)
/dev/hda5           68277       88597    10241406   83  Linux
/dev/hda6           88597       98765     5124703+   b  W95 FAT32 /mnt/banga
/dev/hda7           98765      119085    10241406   83  Linux  /mnt/sabar
/dev/hda8          119086      155056    18129321   83 =20
Linux  /mnt/mornfindel

Output of lspci and lspci -n:
0000:00:00.0 Host bridge: Intel Corp. 82855PM Processor to I/O Controller=20
(rev 21)
0000:00:01.0 PCI bridge: Intel Corp. 82855PM Processor to AGP Controller=20
(rev 21)
0000:00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM=20
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03)
0000:00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM=20
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 03)
0000:00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM=20
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 03)
0000:00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0=
=20
EHCI Controller (rev 03)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 83)
0000:00:1f.0 ISA bridge: Intel Corp. 82801DBM LPC Interface Controller (rev=
=20
03)
0000:00:1f.1 IDE interface: Intel Corp. 82801DBM (ICH4) Ultra ATA Storage=20
Controller (rev 03)
0000:00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus=
=20
Controller (rev 03)
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM=20
(ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)
0000:00:1f.6 Modem: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97=
=20
Modem Controller (rev 03)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobilit=
y=20
Radeon 9600 M10]
0000:02:09.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A=20
IEEE-1394a-2000 Controller (PHY/Link)
0000:02:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd.=20
RTL-8139/8139C/8139C+ (rev 10)
0000:02:0b.0 CardBus bridge: O2 Micro, Inc. OZ711M1 SmartCardBus=20
MultiMediaBay Controller (rev 20)
0000:02:0b.1 CardBus bridge: O2 Micro, Inc. OZ711M1 SmartCardBus=20
MultiMediaBay Controller (rev 20)
0000:02:0b.2 System peripheral: O2 Micro, Inc. OZ711Mx MultiMediaBay=20
Accelerator
0000:02:0d.0 Network controller: Intel Corp. PRO/Wireless 2200BG (rev 05)

0000:00:00.0 0600: 8086:3340 (rev 21)
0000:00:01.0 0604: 8086:3341 (rev 21)
0000:00:1d.0 0c03: 8086:24c2 (rev 03)
0000:00:1d.1 0c03: 8086:24c4 (rev 03)
0000:00:1d.2 0c03: 8086:24c7 (rev 03)
0000:00:1d.7 0c03: 8086:24cd (rev 03)
0000:00:1e.0 0604: 8086:2448 (rev 83)
0000:00:1f.0 0601: 8086:24cc (rev 03)
0000:00:1f.1 0101: 8086:24ca (rev 03)
0000:00:1f.3 0c05: 8086:24c3 (rev 03)
0000:00:1f.5 0401: 8086:24c5 (rev 03)
0000:00:1f.6 0703: 8086:24c6 (rev 03)
0000:01:00.0 0300: 1002:4e50
0000:02:09.0 0c00: 104c:8023
0000:02:0a.0 0200: 10ec:8139 (rev 10)
0000:02:0b.0 0607: 1217:7114 (rev 20)
0000:02:0b.1 0607: 1217:7114 (rev 20)
0000:02:0b.2 0880: 1217:7110
0000:02:0d.0 0280: 8086:4220 (rev 05)


Base System Installation Checklist:
[O] =3D OK, [E] =3D Error (please elaborate below), [ ] =3D 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:
=46irst of all, I am pleasantly surprised about the overall smoothness of t=
he=20
installation. This might even be my first Linux installation where sound
worked out of the box (keep in mind that, thanks mostly to Debian, I don't
install Linux that often ;))

The biggest problems are - not surprisingly - lack of WLAN and power=20
management support. To be honest I haven't tried power management yet
because there is no visible support for it in the UI. I'm using the default
GDM/Gnome setup that results from the "Desktop Environment" task selection,
by the way.
Apart from the lack of WLAN however, network configuration worked fully=20
automatically and perfectly.

Now moving on... I'm not sure if the rest are strictly speaking=20
debian-installer issues, but they are certainly part of the "installation
experience", so here goes:

1. Configuring the X display
=2D The configuration step suggested using the "vesa" driver instead of "at=
i",=20
  even though it should be easy to deduce the correct driver from the PCI ID
=2D The display's native resolution was not detected. I used auto-detection
  whenever possible. The configuration tool set up 800x600 without asking
  for confirmation, so I had to go back and manually fix it later (to
  1280x800, in case you're interested)


2. Keyboard layout woes (X again)
=46YI: I selected language English, country Germany and keyboard layout Ger=
man
I suspect many Germans use a setup like this because a consistently English
system is often better than an inconsistent half-German half-English one.
This choice might have an effect on the problems described below, I just
don't know.
=2D Textmode console had the correct keyboard layout from the start
=2D I had to change the keyboard model from "pc104" to "pc105" in XF86Confi=
g-4
=2D After this change, the keyboard layout was correct in gdm but wrong in =
the
  Gnome session itself. Curiously enough, simply starting the Gnome Keyboard
  configuration and hitting "Reset to Defaults" in the "Layouts" tab fixed
  the problem.

=46or reference, here's the relevant section from my XF86Config-4:
Section "InputDevice"
        Identifier      "Generic Keyboard"
        Driver          "keyboard"
        Option          "CoreKeyboard"
        Option          "XkbRules"      "xfree86"
        Option          "XkbModel"      "pc105"
        Option          "XkbLayout"     "de"
EndSection


3. Mouse (i.e. touchpad) problems
This laptop has a Synaptics touchpad. The relevant section from=20
/proc/bus/input/devices is:
I: Bus=3D0011 Vendor=3D0002 Product=3D0007 Version=3D0000
N: Name=3D"SynPS/2 Synaptics TouchPad"
P: Phys=3Disa0060/serio2/input0
H: Handlers=3Devent1 ts0 mouse0
B: EV=3Db
B: KEY=3D6420 0 70000 0 0 0 0 0 0 0 0
B: ABS=3D11000003

The mouse did work out of the box, but the integrated "touch scrolling" area
and the "tap to click" features did not work. What I did to get it running
after a little research:
=2D Install xfree86-drivers-synaptics and tpconfig packages; I'm not sure=20
  whether installing tpconfig was actually necessary, I certainly didn't use
  the tpconfig tool
=2D Add Load "synaptics" to the Modules section of XF86Config-4
=2D Change the mouse section to the following:
Section "InputDevice"
        Identifier      "Configured Mouse"
        Driver          "synaptics"
        Option          "CorePointer"
        Option          "Device"                "/dev/psaux"
        Option          "Protocol"              "auto-dev"
EndSection

The touchpad works perfectly now.

Of course there's more hardware-related stuff to try (e.g. the built-in=20
burner), but apart from the issues mentioned above everything has been set
up just right for a usable environment.

--nextPart7576651.o5rT9SvUW8
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBdWORsxPozBga0lwRAh0RAKCeVolyPljS1/my70OOLsuVE/UWPQCgvmae
MpdvD+ZCMhGcEWE3Oai/BxE=
=oISl
-----END PGP SIGNATURE-----

--nextPart7576651.o5rT9SvUW8--

---------------------------------------
Received: (at 277365-done) by bugs.debian.org; 21 Oct 2004 07:54:18 +0000
>From stappers@stappers.nl Thu Oct 21 00:54:18 2004
Return-path: <stappers@stappers.nl>
Received: from gpm.stappers.nl [213.84.119.166] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1CKXm6-0002yB-00; Thu, 21 Oct 2004 00:54:18 -0700
Received: by gpm.stappers.nl (Postfix, from userid 1000)
	id E002D79498; Thu, 21 Oct 2004 09:55:35 +0200 (CEST)
Date: Thu, 21 Oct 2004 09:55:35 +0200
To: Nicolai Haehnle <prefect_@gmx.net>, 277365-done@bugs.debian.org
Subject: Re: Bug#277365: (Mostly) successful installation report
Message-ID: <20041021075535.GA19007@gpm.stappers.nl>
References: <[🔎] 200410192057.21801.prefect_@gmx.net> <[🔎] 20041019192538.GC6455@kitenet.net> <[🔎] 200410202052.10853.prefect_@gmx.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l"
Content-Disposition: inline
In-Reply-To: <[🔎] 200410202052.10853.prefect_@gmx.net>
User-Agent: Mutt/1.5.6+20040722i
From: stappers@stappers.nl (Geert Stappers)
Delivered-To: 277365-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 


--XsQoSWH+UP9D9v3l
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Oct 20, 2004 at 08:52:09PM +0200, Nicolai Haehnle wrote:
> On Tuesday 19 October 2004 21:25, Joey Hess wrote:
> > I assume that the above is the wlan device you're speaking of. Do you
> > know what the right kernel module to load is for this device?
>=20
> It turns out that the correct module is the one from http://ipw2200.sf.ne=
t/=20
> which is not in the mainline kernel yet. Also, some of the power manageme=
nt=20
> issues (esp. lack of speedstep support) are fixed in kernel 2.6.9, so thi=
s=20
> isn't an installer issue.

As it is not a installer issue, closing this bugreport.

Thank you for your test report.


Geert Stappers

--XsQoSWH+UP9D9v3l
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBd2t3OSINbgwa/7sRAo0UAJ9ngiXWTlKAiMvVMiud8aciy5DBNQCfR83D
w/nMhAoLCng8tLRnAr5PoiA=
=OAP7
-----END PGP SIGNATURE-----

--XsQoSWH+UP9D9v3l--



Reply to: