public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pongracz Istvan <pongracz.istvan@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: Re[2]: [gentoo-user] iwlwifi & psk auth
Date: Tue, 11 Mar 2008 10:05:58 +0100	[thread overview]
Message-ID: <1205226358.9884.5.camel@localhost> (raw)
In-Reply-To: <525882546.20080311100027@gmail.com>

Hi,

2008. 03. 11, kedd keltezéssel 10.00-kor Sergey Kobzar ezt írta:
> What does
> 'wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf'
> command tell?
> 
> Don't forget stop wpa_supplicant before and reload iwl module.

Thank you for you help.

I already removed the ipw3945d ebuild from my system.

So, here is the output:

fujitsu ~ # wpa_supplicant -Dwext -iwlan0
-c/etc/wpa_supplicant/wpa_supplicant.conf
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not
supported
WEXT auth param 5 value 0x1 - ioctl[SIOCGIWSCAN]: Resource temporarily
unavailable

^CCTRL-EVENT-TERMINATING - signal 2 received
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not
supported
WEXT auth param 4 value 0x0 - fujitsu ~ # 

My relevant dmesg is:

Regarding ieee80211 (grep'ed):

ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation
<jketreno@linux.intel.com>

Regarding iwl (grep'ed)
iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for
Linux, 1.1.17kds
iwl3945: Copyright(c) 2003-2007 Intel Corporation
iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels
phy0: Selected rate control algorithm 'iwl-3945-rs'
iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms.
iwl3945: Error sending REPLY_RXON: time out after 500ms.
iwl3945: Error setting new configuration (-110).
iwl3945: Error sending REPLY_RXON: time out after 500ms.
iwl3945: Error setting new configuration (-110).


Regarding the wlan (grep'ed):

ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready


Anyaway, at this moment I have no wireless access point near to me
(workplace).

Thank you for your help,
István




-- 
BSA. Mert megérdemlitek.
Open Source. Mert megérdemlem.
--
BSA. They value it.
Open Source. The value. It.
--
http://www.osbusiness.hu

-- 
gentoo-user@lists.gentoo.org mailing list



  reply	other threads:[~2008-03-11  9:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10 19:37 [gentoo-user] iwlwifi & psk auth Sergey Kobzar
2008-03-10 20:23 ` Pongracz Istvan
2008-03-10 20:33 ` Jan Seeger
2008-03-10 20:44   ` Re[2]: " Sergey Kobzar
2008-03-10 21:01     ` Jan Seeger
2008-03-10 21:28       ` Pongracz Istvan
2008-03-10 21:39         ` Pongracz Istvan
2008-03-11  8:00           ` Re[2]: " Sergey Kobzar
2008-03-11  9:05             ` Pongracz Istvan [this message]
2008-03-11 10:49               ` Pongracz Istvan
2008-03-11 12:02                 ` Peter Humphrey
2008-03-11 19:39                   ` Pongracz Istvan
2008-03-10 20:56   ` Pongracz Istvan
2008-03-11 11:32   ` Peter Humphrey
2008-03-11 12:36     ` Jan Seeger
2008-03-11 17:22       ` Peter Humphrey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1205226358.9884.5.camel@localhost \
    --to=pongracz.istvan@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox