Your message dated Tue, 13 Apr 2004 16:22:21 -0400
with message-id <[EMAIL PROTECTED]>
and subject line fixed
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; 13 Apr 2004 19:00:18 +0000
>From [EMAIL PROTECTED] Tue Apr 13 12:00:18 2004
Return-path: <[EMAIL PROTECTED]>
Received: from webmail-outgoing.us4.outblaze.com [205.158.62.67] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1BDT8s-0001JQ-00; Tue, 13 Apr 2004 12:00:18 -0700
Received: from wfilter.us4.outblaze.com (wfilter.us4.outblaze.com [205.158.62.180])
        by webmail-outgoing.us4.outblaze.com (Postfix) with QMQP id 35D2218021CF
        for <[EMAIL PROTECTED]>; Tue, 13 Apr 2004 18:58:42 +0000 (GMT)
X-OB-Received: from unknown (205.158.62.91)
  by wfilter.us4.outblaze.com; 13 Apr 2004 18:57:14 -0000
Received: by ws3-1.us4.outblaze.com (Postfix, from userid 1001)
        id 5F9EF1536DC; Tue, 13 Apr 2004 18:56:18 +0000 (GMT)
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)
Received: from [160.129.138.230] by ws3-1.us4.outblaze.com with http for
    [EMAIL PROTECTED]; Tue, 13 Apr 2004 13:56:18 -0500
From: "Bob Smith" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date: Tue, 13 Apr 2004 13:56:18 -0500
Subject: =?iso-8859-1?q?installation-reports:_glitch_setting_ESSID_with?=
    =?iso-8859-1?q?out_WEP_(to_do_wireless_net_in=0D stall)?=
X-Originating-Ip: 160.129.138.230
X-Originating-Server: ws3-1.us4.outblaze.com
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
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=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 
X-CrossAssassin-Score: 1

Package: installation-reports

Debian-installer-version: sarge-i386-netinst.iso(beta2) 26Mar04
uname -a: Linux (none) 2.4.25-1-386 #1 Tue Feb 24 08:11:13 EST 2004
Date: 13Apr04 0900
Method: started a network install using 802.11

Machine: IBM Thinkpad 570E (2644-6BU)
Processor: PIII 500MHz
Memory: 192 MB
Root Device:
Root Size/partition table: 
Output of lspci:

Base System Installation Checklist:

Initial boot worked:    [O]
Configure network HW:   [O]
Config network:         [E]
Detect CD:              [O]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [ ]
Create file systems:    [ ]
Mount partitions:       [ ]
Install base system:    [ ]
Install boot loader:    [ ]
Reboot:                 [ ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems:

I tried to do a net-install using 802.11b.
My institution does not use WEP, but does use an SSID.
This causes a problem, because the installer asks for the WEP key,
then 
tries DHCP, but does not ask for the SSID unless you go back to the
main 
menu and choose "configure network" *twice*.

Details:
--------------------
***this fails:
Choose a language: english-us
Select a keyboard layout: american english
Detecting hardware
Loading components of Debian installer
Detecting Hardware
Configure the network
        WEP key for eth0: none (continue)
Configuring the network with DHCP (fails)
        retry? no (continue)
Configure the network
        IP address: (dead end) go back
menu->configure the network
        WEP key for eth0: none (continue)
        Network configuration method: DHCP (continue)
Configuring the network with DHCP (fails)
        retry? no
Configure the network
        IP address: (dead end)

***this works:  
Choose a language: english-us
Select a keyboard layout: american english
Detecting hardware
Loading components of debian installer
Detecting hardware
Configure the network
        WEP key for eth0: go back
menu->choose: configure the network
        WEP key for eth0: go back
menu->choose: configure the network
        Wireless ESSID for eth0: (entered correctly)
Configure the network
        WEP key for eth0: none (continue)
Configure the network
        Network configuration method: DHCP
Configure the network
        DHCP hostname: none (continue)
Configuring the network with DHCP
Configure the network:
        hostname: debian32
successfully connects to network... 
menu->continues with detect hardware

(note that in the first example, if I go back to "Configure the
network"
for a third time, it *will* ask for the Wireless ESSID, and then
succeed)

--------------------

card used:
Netgear 802.11b Wireless PC Card
  16-bit PCMCIA Model MA401
  (known good in this machine per current Knoppix HD installation)

--------------------

I didn't have time to complete the installation.
I don't understand why the installer *does* ask for the SSID before
the WEP key, 
but only on the third try. I suspect a small problem with the
sequencing logic.

--------------------
Hope this helps; keep up the great work!





-- 
__________________________________________________________
Sign-up for your own personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

Search Smarter - get the new eXact Search Bar for free!
http://www.exactsearchbar.com/


---------------------------------------
Received: (at 243563-done) by bugs.debian.org; 13 Apr 2004 20:22:44 +0000
>From [EMAIL PROTECTED] Tue Apr 13 13:22:44 2004
Return-path: <[EMAIL PROTECTED]>
Received: from kitenet.net [64.62.161.42] (postfix)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1BDUQe-0000vU-00; Tue, 13 Apr 2004 13:22:44 -0700
Received: from dragon.kitenet.net (216-98-95-240.access.naxs.com [216.98.95.240])
        (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
        (Client CN "Joey Hess", Issuer "Joey Hess" (verified OK))
        by kitenet.net (Postfix) with ESMTP id 42FB9184E6
        for <[EMAIL PROTECTED]>; Tue, 13 Apr 2004 20:22:43 +0000 (GMT)
Received: by dragon.kitenet.net (Postfix, from userid 1000)
        id E139C6E901; Tue, 13 Apr 2004 16:22:21 -0400 (EDT)
Date: Tue, 13 Apr 2004 16:22:21 -0400
From: Joey Hess <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: fixed
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="G4iJoqBmSsgzjUCe"
Content-Disposition: inline
User-Agent: Mutt/1.5.5.1+cvs20040105i
Delivered-To: [EMAIL PROTECTED]
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=-2.0 required=4.0 tests=BAYES_00 autolearn=no 
        version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 
X-CrossAssassin-Score: 1


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

This is fixed in current daily builds

--=20
see shy jo

--G4iJoqBmSsgzjUCe
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)

iD8DBQFAfEv9d8HHehbQuO8RApN8AJ4rGH7Byex0fbxH8DqBA+41KEoGDwCglFZF
Zvw+S0czaMprnxyOwehq1vM=
=Fv0C
-----END PGP SIGNATURE-----

--G4iJoqBmSsgzjUCe--


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to