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

    • AMAZON needs to take total accountability for this.
    • Server Summit had a heap of announcements, ADCS changes are baller.
    • Nice, hope they *finally* fixed the issue with the NTFS driver where the system would completely brick during large file copies using the built in driver. It's been broken for years requiring me to use the older, slower, NTFS-3G FUSE driver.
    • Windows 11 KB5094126 BSODing, freezing, forcing BitLocker lockout, breaks OneDrive, and more by Sayan Sen Microsoft released Windows 11 KB5094126 and KB5093998 last week as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. While Microsoft has so far not acknowledged any major problems with the release, some users online are running into problems. These range from OneDrive and Dropbox access issues, BitLocker recovery lockouts, to blue screens and BSODs. The most common one seems to be happening with HP systems wherein affected users say they hit 0xc0430001 BSOD (blue screen of death) error code after the KB5094126 update. We wonder if this could be related to the recent bug we covered on HP devices wherein the ongoing Secure Boot certificate updates are leading to similar issues. While we are not certain, users affected by this issue likely need to ensure that the boot.stl file is included on the installation media (such as a USB installer or ISO), if the above-mentioned dynamic updates are deployed. If this file is missing, computers may fail to boot from the installation media and could display the error 0xc0430001. This STL file is used by Secure Boot to verify that the boot files are trusted, so it must match the same Windows version and system architecture. To ensure the file is included, Microsoft recommends using the Update WinPE script, which automatically updates the image and handles the required files. Alternatively, you can manually copy the boot.stl file from the Windows\Boot\EFI folder on a Windows device and place it in the matching folder on your installation media before deploying the updated image. Aside from blue screening some users also note their systems have been freezing following the update. This could be happening to Lenovo PCs specifically. In the case of the OneDrive and Dropbox access issues, a user figured out that there could be a conflict with UAC. He explained: "Okay, so I did some digging, and in our environment KB5094126 breaks OneDrive and Dropbox in Explorer. I went through all our GPOs and found out that the combination of disabling UAC and having my user being a local admin breaks OneDrive in Explorer. ... If I enable UAC again, then it works, even with KB5094126 still installed." Hopefully, Microsoft will look into these issues. Source: Microsoft forum (link1, link2, link3, link4), Reddit (link1, link2, link3, link4)
    • It is when it's a desktop in my house though for a PC that's lightly used and not really important when it is. If it was a laptop, it would be a different story. The real solution is varied and begins starting at post #22 in that thread.
  • 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
      508
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      138
    4. 4
      ATLien_0
      90
    5. 5
      Steven P.
      80
  • Tell a friend

    Love Neowin? Tell a friend!