From: "Jakub Kiciński" <moorray3@wp.pl>
To: Mohit <mt1037ag11@pdm.ac.in>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Ralink RT3290 proprietary drivers causing kernel panic
Date: Wed, 22 May 2013 22:22:10 +0200 [thread overview]
Message-ID: <20130522222210.4e005cec@north> (raw)
In-Reply-To: <519D0D44.1040901@pdm.ac.in>
On Wed, 22 May 2013 23:54:04 +0530, Mohit wrote:
> Hello,
>
> I am on openSUSE 12.3 with kernel 3.7.10-1.4-desktop, i
> wanted to try out the proprietary drivers for Ralink RT3290 so i
> downloaded the drivers from
> http://www.mediatek.com/_en/07_downloads/01_windows.php?sn=501 and
> compiled the drivers as mentioned on my thread here :
> https://forums.opensuse.org/english/get-technical-help-here/wireless/486975-rt3290-wireless-proprietary-drivers-not-working.html#post2557514.
> Everything compiled fine, openSUSE was able to scan and connect to
> access points after installation, but when i access the internet a
> kernel panic occurs after ~5sec (time varies based on the data usage).
> So i humbly request you to please provide the solution for the same, you
> can reach me through email or reply to my thread (probably faster as i
> don't check my email everyday).
I think vendor drivers crash on 64bit kernel because they
have faulty skb offsets handling. It's usually enough to fix
GCC warnings to make them work.
Having said that - I agree with Gertjan, you should really try
rt2800 from your kernel (or preferably from compat-wireless)
and if that doesn't work ask the vendor for help.
-- Kuba
prev parent reply other threads:[~2013-05-22 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 18:24 Ralink RT3290 proprietary drivers causing kernel panic Mohit
2013-05-22 19:55 ` Gertjan van Wingerde
2013-05-23 12:21 ` Mohit
2013-05-23 16:18 ` Andreas Hartmann
2013-05-22 20:22 ` Jakub Kiciński [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=20130522222210.4e005cec@north \
--to=moorray3@wp.pl \
--cc=linux-wireless@vger.kernel.org \
--cc=mt1037ag11@pdm.ac.in \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.