--- Begin Message ---
>From cossa@ulp.u-strasbg.fr Wed Feb 01 08:34:18 2006
Received: (at submit) by bugs.debian.org; 1 Feb 2006 16:34:18 +0000
Return-path: <cossa@ulp.u-strasbg.fr>
Received: from smtp5-g19.free.fr ([212.27.42.35])
by spohr.debian.org with esmtp (Exim 4.50)
id 1F4Kvy-0008OB-2o
for submit@bugs.debian.org; Wed, 01 Feb 2006 08:34:18 -0800
Received: from [192.168.0.1] (bro67-2-82-225-7-246.fbx.proxad.net [82.225.7.246])
by smtp5-g19.free.fr (Postfix) with ESMTP id 214AA17F73
for <submit@bugs.debian.org>; Wed, 1 Feb 2006 17:34:17 +0100 (CET)
Message-ID: <[🔎] 43E0E37F.7060008@ulp.u-strasbg.fr>
Date: Wed, 01 Feb 2006 17:36:15 +0100
From: Adrien <cossa@ulp.u-strasbg.fr>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: submit@bugs.debian.org
Subject: (pas de sujet)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE,
RCVD_IN_SORBS autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: installation-reports
Boot method: netboot
Image version: daily netboot i386 from people.debian.org/~joeyh/
Date: 20060131
Machine: Asus A8N-VM CSM (Nforce 430 / 6500)
Processor: AMD64 3200+
Memory: 2 * 512 DDR
Partitions: on Hitachi T7K250 250 Go (SATA II)
29996.3 MB NTFS
980.5 MB Linux Swap
18128.0 MB Linux Ext3
189367.8 MB Linux Ext3
Output of lspci and lspci -n: i'm not under linux right now... will send
it after if needed
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: [E]
Detect CD: [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives: [ ]
Create file systems: [ ]
Mount partitions: [ ]
Install base system: [ ]
Install boot loader: [ ]
Reboot: [ ]
Comments/Problems:
Two network interfaces were detected where there is only one onboard.
Then the DHCP configuration doesn't detect anything, so it's impossible
to download the Releases file on the next step. I tryed to fill manually
the IP/netmask/gateway/etc and it's the same. I found at least one
person who had the same problem :
http://www.nvnews.net/vbulletin/showpost.php?p=792214&postcount=212
It's strange as I didn't have this problem with the netboot CD for
AMD64. Two interfaces were found too, but the configuration was
successfully detected by DHCP and the rest of the installation was OK.
--- End Message ---
--- Begin Message ---
>From stappers@stappers.nl Sat Feb 04 05:32:11 2006
Received: (at 350912-done) by bugs.debian.org; 4 Feb 2006 13:32:11 +0000
Return-path: <stappers@stappers.nl>
Received: from gpm.stappers.nl ([213.84.119.166])
by spohr.debian.org with esmtp (Exim 4.50)
id 1F5NWN-0003a0-5A
for 350912-done@bugs.debian.org; Sat, 04 Feb 2006 05:32:11 -0800
Received: by gpm.stappers.nl (Postfix, from userid 1000)
id 39D7C794A0; Sat, 4 Feb 2006 14:25:49 +0100 (CET)
Date: Sat, 4 Feb 2006 14:25:49 +0100
To: Adrien <cossa@ulp.u-strasbg.fr>, 350912-done@bugs.debian.org
Subject: Bug#350912: it works being AMD64
Message-ID: <20060204132549.GA25648@gpm.stappers.nl>
References: <[🔎] 43E49D5E.3070408@ulp.u-strasbg.fr>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="h31gzZEtNLTqOjlF"
Content-Disposition: inline
In-Reply-To: <[🔎] 43E49D5E.3070408@ulp.u-strasbg.fr>
User-Agent: Mutt/1.5.6+20040722i
From: stappers@stappers.nl (Geert Stappers)
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-3.1 required=4.0 tests=BAYES_44,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
--h31gzZEtNLTqOjlF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sat, Feb 04, 2006 at 01:26:06PM +0100, Adrien wrote:
> Hi, as I didnt send the output of lspci and lspci -n last time, here is=
=20
> the output of lspci :
> And lspci -n :
Sorted, stripped and blank lines added:
0000:00:14.0 0680: 10de:0269 (rev a1)
0000:00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a1)
0000:00:18.0 0600: 1022:1100
0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron=
] HyperTransport Technology Configuration
0000:00:18.1 0600: 1022:1101
0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron=
] Address Map
0000:00:18.2 0600: 1022:1102
0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron=
] DRAM Controller
0000:00:18.3 0600: 1022:1103
0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron=
] Miscellaneous Control
0000:04:05.0 0c00: 1106:3044 (rev 80)
0000:04:05.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host=20
0000:04:09.0 0280: 1814:0201 (rev 01)
0000:04:09.0 Network controller: RaLink Ralink RT2500 802.11 Cardbus=20
> The problem was :
>=20
> "Two network interfaces were detected where there is only one onboard.=20
> Then the DHCP configuration doesn't detect anything, so it's impossible=
=20
> to download the Releases file on the next step. I tryed to fill manually=
=20
> the IP/netmask/gateway/etc and it's the same. I found at least one=20
> person who had the same problem :
>=20
> http://www.nvnews.net/vbulletin/showpost.php?p=3D792214&postcount=3D212
>=20
> It's strange as I didn't have this problem with the netboot CD for=20
> AMD64. Two interfaces were found too, but the configuration was=20
> successfully detected by DHCP and the rest of the installation was OK."
:-)
> Somebody said me that the second network interface was the firewire, but=
=20
> I still can't use the network. Did I something wrong or is it an=20
> installer bug ?
Nope. Neither an installer bug nor you doing something wrong.
It is a good thing to be curious and play with technology.
You found out that an AMD64 does differ from i386.
> Thanks.
I'm closing this bugreport. You have your AMD64 working as AMD64.
That the AMD64 doesn't work as i386 at (low-level) hardware level ("driver"=
),
is something you have to accept.
Cheers
Geert Stappers
P.S.
As always: feel free to tell more about the topic.
Another point of view, does effect my opinion! (c:
--h31gzZEtNLTqOjlF
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)
iD8DBQFD5KtdOSINbgwa/7sRAgj3AKCZdqItda5flpN0+Vc47OzllkfbgwCfR4eu
GL+YzdMZBWRyXghKlHg8E90=
=9N7y
-----END PGP SIGNATURE-----
--h31gzZEtNLTqOjlF--
--- End Message ---