Hi,
I am facing a problem getting the Dlink DWA-525 wifi to be detected in 12.1, have already downloaded the specific linux driver (also opensuse based ), compiled it and loaded the rt3562sta module but yast is not able to see the card. lspci shows it as ralink and ifconfig does show any ra0 devices
Any ideas people ?
If more info is needed please do let me know.
On 06/26/2012 05:46 AM, zulfikar wrote:
>
> Hi,
>
> I am facing a problem getting the Dlink DWA-525 wifi to be detected in
> 12.1, have already downloaded the specific linux driver (also opensuse
> based ), compiled it and loaded the rt3562sta module but yast is not
> able to see the card.
>
> Any ideas people ?
>
> If more info is needed please do let me know.
As is stated in the stickies in the wireless forum, and in many other posts, the
make and model are simply not sufficient. You MUST provide the PCI ID using
“/sbin/lspci -nn”, or the USB ID using “lsusb”. Vendors change the chip inside
without making any change in the model, or they may merely change from V1 to V2.
YaST is not a good tool to see if a driver has been loaded as the device will
only appear when the load is completely successful. For instance, if external
firmware is needed and not provided, device wlan0, which is what YaST is
needing, is not created. You need to look at the output of dmesg to get clues.
Do not post the entire output. Most of it is uninteresting for this problem.
Sorry my mistake I will post the pci list and a few kernel output regarding the device.
It should be a ra0 device.
This is the lspci
04:06.0 Network controller [0280]: Ralink corp. Device [1814:5360]
The other thing about dmesg output , I do not see any ralink or anything indicating this card, that would mean the module is not loading during boot up.
lsmod does not show the rt3562sta module, Let me try 2860 drivers.
On 06/27/2012 01:36 AM, zulfikar wrote:
>
> This is the lspci
>
> 04:06.0 Network controller [0280]: Ralink corp. Device [1814:5360]
>
> The other thing about dmesg output , I do not see any ralink or
> anything indicating this card, that would mean the module is not loading
> during boot up.
The official built-in driver for that device is rt2800pci. It is available in
kernel 3.1.10-1.9-desktop. There should be no need for you to mess around with
the driver source from the vendor.
I do recall a configuration problem with earlier kernels. What does ‘uname -r’
report as your kernel version?
You may also check the status of your kernel with the command
zcat /proc/config.gz | grep RT53XX
If the command returns “# CONFIG_RT2800PCI_RT53XX is not set”, then your device
is not configured. The response “CONFIG_RT2800PCI_RT53XX=y” means that the
driver should be available.
One other thing to check is the existence of file /lib/firmware/rt2860.bin. If
it is not on your system, then install the kernel-firmware package.
I am using the default kernel, and zcat /proc/config shows rt2800PCI_RT53XX=y and also have the rt2860.bin under firmware
On 06/27/2012 01:26 PM, zulfikar wrote:
>
> I am using the default kernel, and zcat /proc/config shows
> rt2800PCI_RT53XX=y and also have the rt2860.bin under firmware
The driver should be loading, and /usr/sbin/iwconfig should show an interface,
unless your attempts to use an outside driver resulted in blacklisting
rt2800pci. Run the command
grep rt2800pci /etc/modprobe.d/*
If any files blacklist rt2800pci, then you need to delete that line of that file.
On 06/27/2012 01:48 PM, Larry Finger wrote:
> On 06/27/2012 01:26 PM, zulfikar wrote:
>>
>> I am using the default kernel, and zcat /proc/config shows
>> rt2800PCI_RT53XX=y and also have the rt2860.bin under firmware
>
> The driver should be loading, and /usr/sbin/iwconfig should show an interface,
> unless your attempts to use an outside driver resulted in blacklisting
> rt2800pci. Run the command
>
>
> grep rt2800pci /etc/modprobe.d/*
>
If any files blacklist rt2800pci, then you need to delete that line of that file.
I finally got a chance to reboot and install my RT3090, which also uses
rt2800pci. The lspci line for it is
06:00.0 Network controller [0280]: Ralink corp. RT3090 Wireless 802.11n 1T/1R
PCIe [1814:3090]
The driver is not very chatty. The only mention of it in the dmesg log is
29.208258] Registered led device: rt2800pci-phy1::radio
29.215349] Registered led device: rt2800pci-phy1::assoc
29.216533] Registered led device: rt2800pci-phy1::quality
It does create a wireless device wlan0, not ra0.
Will check all these and post back within a couple of hours. thnx.
Check every thing but no luck, no blacklisting of the module.
The 5360 should be supported by driver compile but not happening.
On 06/28/2012 12:56 PM, zulfikar wrote:
>
> The 5360 should be supported by driver compile but not happening.
OK, but I do not help with out-of-kernel drivers if there is an in-kernel
version. Sorry.
I am comfortable with driver compile no issues there. I will check on the 5360 if its part of the kernel, report back in a couple of hours.thnx.
It is working after compiling the RT5390 drivers , but there is a catch I need to do this
"echo “1814 5360” > /sys/bus/pci/drivers/rt2860/new_id "
But it works.
On 06/29/2012 01:46 AM, zulfikar wrote:
>
> lwfinger;2471794 Wrote:
>> On 06/28/2012 12:56 PM, zulfikar wrote:
>>>
>>> The 5360 should be supported by driver compile but not happening.
>>
>> OK, but I do not help with out-of-kernel drivers if there is an
>> in-kernel
>> version. Sorry.
>
> It is working after compiling the RT5390 drivers , but there is a catch
> I need to do this
>
> “echo “1814 5360” > /sys/bus/pci/drivers/rt2860/new_id”
>
> But it works.
In the source, find the PCI_DEViCE macro calls, and add a new entry with your
PCI_ID. In the in-kernel driver, the line is
{ PCI_DEVICE(0x1814, 0x5360) },
After you do that, rebuild, and reinstall the driver, the device will start
automatically.
Which source ?
On 06/29/2012 01:46 PM, zulfikar wrote:
>
> lwfinger;2471934 Wrote:
>> On 06/29/2012 01:46 AM, zulfikar wrote:
>>>
>>> lwfinger;2471794 Wrote:
>>>> On 06/28/2012 12:56 PM, zulfikar wrote:
>>>>>
>>>>> The 5360 should be supported by driver compile but not happening.
>>>>
>>>> OK, but I do not help with out-of-kernel drivers if there is an
>>>> in-kernel
>>>> version. Sorry.
>>>
>>> It is working after compiling the RT5390 drivers , but there is a
>> catch
>>> I need to do this
>>>
>>> “echo “1814 5360” > /sys/bus/pci/drivers/rt2860/new_id”
>>>
>>> But it works.
>>
>> In the source, find the PCI_DEViCE macro calls, and add a new entry
>> with your
>> PCI_ID. In the in-kernel driver, the line is
>>
>>>
> Code:
> --------------------
> > >
> > { PCI_DEVICE(0x1814, 0x5360) },
> >
> --------------------
>>>
>>
>> After you do that, rebuild, and reinstall the driver, the device will
>> start
>> automatically.
>
> Which source ?
The one that your device is using as a driver, of course. If you needed to
modify the kernel, I would have sent the requisite patch file.
Could you send me the patch
On 06/30/2012 04:06 AM, zulfikar wrote:
>
> Could you send me the patch
Patch what? The last I heard was that you are building an out-of kernel driver.
I do not have that source!