Linux Noob Doesn't Want to Compile Kernel


Recommended Posts

Here's the story -

I just bought a brand new MSI Wind U210. I decided to load Ubuntu for my first Linux experience. I discovered quickly that my wireless chipset, the Ralink rt3090, doesn't work with 9.10. So, I did a bit of research and found these drivers in a handy .deb format. Now that these drivers are installed the rt3090 works - sort of. It will not connect to WPA secured networks, only WEP.

I found this thread on ubuntuforums.org trying to solve this problem. One fellow claims to have done so, posting:

My LG x130 has the same wireless chipset. Since the ndiswrapper did not work very well, I tried with the staging driver. I patched the 2.6.31 kernel source with all rt3090 related patches you can get from here:

http://www.kernel.org/pub/linux/kernel/peo...ging/2.6/2.6.31

Compiled the kernel and installed it. You need to provide the configuration file in /etc/Wireless which I just took from the original Ralink driver. Connecting to WPA encrypted networks now works flawlessly.

Daniel

So I looked up patching the kernel. Well, it looks like I would have to build the whole thing from source and swap it out with the existing kernel. I have been using Linux all of 24 hours. I do not want to do this. The instructions I've read barely make any sense to me.

Please, help me find another solution.

http://array.org/ubuntu/

That kernel is what I use on my eeepc. Apparently the Jaunty kernels now support the Wind too? :)

Won't I need to downgrade to Jaunty to use those kernels? I may do that if Karmic isn't substantially better, but I don't personally know.

If it simply is a patch that made it into later versions of the kernel, it couldn't hurt to check the repo's real quick on Ubuntu to see if there is a more up to date version then what you currently have. I'm not a big fan of Ubuntu, but I know 99% of the time, the distro ISO isn't fully up to date.

Should work with NDISWrapper with no recompiling required. I believe only the latest version of the driver, which is fairly new, supports WPA.

See: https://help.ubuntu.com/community/WifiDocs/...ver/Ndiswrapper

Btw, there is hardly ever a need to recompile the kernel. You just need the kernel headers to build a driver as a loadable module. I don't know who suggested rebuilding the kernel to build the driver into the kernel itself.

Dude, seriously. Compiling an OS kernel just to get wireless to work?

I want to see your defense for that. No, really. I'm serious. =/

If compiling the kernel to get a driver working is true, there is no defense. However that may not be necessary.

http://wolfs-ubuntu.blogspot.com/

The info is about middle ways down the page.

[Thread Cleaned]

Off-topic posts have been removed since they were not helpful to the original poster's situation. If somebody wants to start a new thread about whether an OS should allow you to recompile a kernel to get access to non-supported hardware then go ahead.

Have you tried downloading the drivers from:

http://www.ralinktech.com.tw/support.php?s=2

Installing the kernel-devel package; inside the file there is a readme with step by step instructions on how to compile it against your kernel release. One downside you'll need to recompile it each time you update the kernel.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Anyway to download these versions without being on the Experimental builds?
    • Nothing is stopping you from continuing with your testing cadence. If updates are released every 2 weeks instead of 4, and you test once every 4 weeks, the exact same amount of patches will still be available for you in those 4 weeks. For example: Before 4th week - patch 1, 2, 3, 4 After 2nd week - patch 1 and 2 4th week - patch 3 and 4 Still the same amount after 4.
    • Everyone else has said it. I'm gonna say it - you don't know what you're talking about. I do. I have two laptops. One work, one personal. I have access to two more laptops - both personal. At home I manually update my personal laptop when I see on Neowin that there is an update - I carry on and only apply the updates when I am ready. My work one only updates when my workplace decides to send it - I carry on and only apply the updates (when they actually arrive, which is usually days after the release) when I switch off the laptop at the end of the day as usual. The two other personal laptops only get updated when I get to it which is rarely - the people who own them carry on using them until I get to it and update them. All of the browsers on all laptops are configured to restore the tabs when launched. Google and Microsoft have changed from 6 weeks to 4, and it looks like it's going to move to 2. None of these changes affect how any of these browsers on the laptops are used. Not one jot. My advice to you is stop panicking whenever you see an update. Just carry on with what you're doing. This even benefits you in a way - from your comment you sound like you don't like the changes or the frivolous new features - great - then carry on as before!
    • AMAZON needs to take total accountability for this.
    • Server Summit had a heap of announcements, ADCS changes are baller.
  • Recent Achievements

    • Week One Done
      Jeroen Wilms earned a badge
      Week One Done
    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      509
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      138
    4. 4
      ATLien_0
      90
    5. 5
      Steven P.
      81
  • Tell a friend

    Love Neowin? Tell a friend!