From: Chris <dchris@gmail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: bugme-daemon@bugzilla.kernel.org, linux-wireless@vger.kernel.org,
"Johannes Berg" <johannes@sipsolutions.net>
Subject: Re: [Bugme-new] [Bug 11596] New: iwlagn driver in latest linux-2.6 git is not working for intel 4965agn card
Date: Sat, 20 Sep 2008 10:14:38 +0200 [thread overview]
Message-ID: <99175ee40809200114r66d9cceeqa7e59ea8002f24f1@mail.gmail.com> (raw)
In-Reply-To: <99175ee40809200107v17dbcfc7hee08d20417c409b4@mail.gmail.com>
I don't think it was broken that recently though. I experienced the
same problem with ubuntu kernel :
2.6.27-2.3
Which apparently was based on git and was released on :
Wed, 27 Aug 2008 14:03:05 -0400
Best regards,
Chris.
On Sat, Sep 20, 2008 at 10:07 AM, Chris <dchris@gmail.com> wrote:
> I'm not exactly sure when it was broken. I switched directly from
> kernel 2.6.26 (which was working fine) to kernel 2.6 git
> (~2.6.27~rc6).
>
> On Sat, Sep 20, 2008 at 9:59 AM, Andrew Morton
> <akpm@linux-foundation.org> wrote:
>>
>> (switched to email. Please respond via emailed reply-to-all, not via the
>> bugzilla web interface).
>>
>> On Sat, 20 Sep 2008 00:51:50 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
>>
>>> http://bugzilla.kernel.org/show_bug.cgi?id=11596
>>>
>>> Summary: iwlagn driver in latest linux-2.6 git is not working for
>>> intel 4965agn card
>>> Product: Drivers
>>> Version: 2.5
>>> KernelVersion: linux-2.6 git
>>> Platform: All
>>> OS/Version: Linux
>>> Tree: Mainline
>>> Status: NEW
>>> Severity: normal
>>> Priority: P1
>>> Component: network-wireless
>>> AssignedTo: drivers_network-wireless@kernel-bugs.osdl.org
>>> ReportedBy: dchris@gmail.com
>>>
>>>
>>> Latest working kernel version: Linux-2.6git (~linux-2.6.27-rc6)
>>> Earliest failing kernel version: unknown
>>> Distribution: Vanilla
>>> Hardware Environment: Intel 4965agn card
>>> Software Environment:
>>> Problem Description: Although my wifi card is detected, and although it is able
>>> to scan for access points, it is not able to connect to access points. I tried
>>> two access points (one with WPA2 encryption and another without encryption).
>>> Authentication is successful but then it seems like it is not able to get an IP
>>> from DHCP... DHCP server is working fine and forcing an IP does not work (I'm
>>> not able to ping other machines on the wlan).
>>>
>>> I first noticed this problem on Ubuntu intrepid, which is using 2.6.27-rc6.
>>> Then, I decided to compile linux-2.6 git and enable iwlagn debug.
>>>
>>> I'm joining my logs. I'll be happy to provide more information if necessary.
>>>
>>> Steps to reproduce: Connect to any access point, authentication is successful
>>> but you can't get any IP.
>>>
>>
>> hm, so we broke it in the past few days?
>>
>
prev parent reply other threads:[~2008-09-20 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11596-10286@http.bugzilla.kernel.org/>
2008-09-20 7:59 ` [Bugme-new] [Bug 11596] New: iwlagn driver in latest linux-2.6 git is not working for intel 4965agn card Andrew Morton
2008-09-20 8:07 ` Chris
2008-09-20 8:14 ` Chris [this message]
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=99175ee40809200114r66d9cceeqa7e59ea8002f24f1@mail.gmail.com \
--to=dchris@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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