linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James <bjlockie@lockie.ca>
To: linux-wireless Mailing List <linux-wireless@vger.kernel.org>
Subject: Re: kernel-2.6.36.2 works, later doesn't
Date: Thu, 24 Mar 2011 23:54:05 -0400	[thread overview]
Message-ID: <4D8C11DD.7000003@lockie.ca> (raw)
In-Reply-To: <AANLkTik+AjhMBwRy9ESaidnuW+1YCSZiEzeWdFnmZnqS@mail.gmail.com>

On 03/24/11 12:51, Sedat Dilek wrote:
> On Mon, Mar 21, 2011 at 3:04 AM, James <bjlockie@lockie.ca> wrote:
>> On 03/20/11 17:04, James wrote:
>>> $ dmesg | grep phy
>>> BIOS-provided physical RAM map:
>>> modified physical RAM map:
>>> phy0: Selected rate control algorithm 'ath9k_rate_control'
>>> Registered led device: ath9k-phy0::radio
>>> Registered led device: ath9k-phy0::assoc
>>> Registered led device: ath9k-phy0::tx
>>> Registered led device: ath9k-phy0::rx
>>> phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81
>>> mem=0xffffc90001900000, irq=17
>>>
>>> This is kernel-2.6.36.2.
>>> The wireless doesn't work on any later kernel that I have tried.
>>> It is very interesting the IRQ is 17 on this kernel but 18 on 2.6.37.3.
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>
>> I tried
>> http://www.orbit-lab.org/kernel/compat-wireless-2.6-stable/v2.6.36/compat-wireless-2.6.36-4.tar.bz2
>> but it doesn't work in the 2.6.36.2 kernel or the 2.6.38 kernel.
>>
>> Where can I get the compat-wireless that is the exact code that is in
>> the 2.6.36.2 kernel and then I can try it in the 2.6.38 kernel?
>>
> The idea of compat-wireless is to make new wifi drivers & features
> accessible for older host-kernel, not the other way around.
> It also makes no sense to have same versions of host kernel and c-w
> version (both 2.6.36 for example, it is the same codebase).
If the old c-w works on the new kernel then I know it is a kernel problem.
> Did you try one of the bleeding-edge compat-wireless [1] tarball (it
> is updated daily, but can be broken)?
> Furthermore, [2] has informations about stable releases and detailed
> build instructions.
I last tried 2011-03-19
> Please provide full dmesg and lspci/lsusb output - not truncated one.
> Which user-space do you use? Network-Manager, wpasupplicant, etc.?
No user space utilities are automatically started but I use wicd
manually to get an IP from my wired connection.
The AP is open so I don't use wpasupplicant.

$ dmesg
http://lockie.ca/test/dmesg.txt.bz2

$ sudo lspci
00:00.0 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a1)
00:01.0 ISA bridge: nVidia Corporation MCP65 LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation MCP65 SMBus (rev a1)
00:01.2 RAM memory: nVidia Corporation MCP65 Memory Controller (rev a1)
00:02.0 USB Controller: nVidia Corporation MCP65 USB Controller (rev a1)
00:02.1 USB Controller: nVidia Corporation MCP65 USB Controller (rev a1)
00:07.0 Audio device: nVidia Corporation MCP65 High Definition Audio
(rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP65 PCI bridge (rev a1)
00:09.0 IDE interface: nVidia Corporation MCP65 IDE (rev a1)
00:0a.0 IDE interface: nVidia Corporation MCP65 SATA Controller (rev a1)
00:0b.0 PCI bridge: nVidia Corporation Device 045b (rev a1)
00:0c.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:0d.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:0e.0 PCI bridge: nVidia Corporation MCP65 PCI Express bridge (rev a1)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Miscellaneous Control
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
02:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A
IEEE-1394a-2000 Controller (PHY/Link)
02:08.0 Multimedia video controller: Brooktree Corporation Bt878 Video
Capture (rev 11)
02:08.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture
(rev 11)
02:09.0 Network controller: Atheros Communications Inc. AR5008 Wireless
Network Adapter (rev 01)
04:00.0 VGA compatible controller: nVidia Corporation G92 [GeForce 8800
GT] (rev a2)


      reply	other threads:[~2011-03-25  3:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-20 21:04 kernel-2.6.36.2 works, later doesn't James
2011-03-21  2:04 ` James
2011-03-24 14:27   ` James
2011-03-24 16:51   ` Sedat Dilek
2011-03-25  3:54     ` James [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=4D8C11DD.7000003@lockie.ca \
    --to=bjlockie@lockie.ca \
    --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;
as well as URLs for NNTP newsgroup(s).