LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Ubuntu
User Name
Password
Ubuntu This forum is for the discussion of Ubuntu Linux.

Notices

Reply
 
Search this Thread
Old 06-24-2008, 03:37 PM   #1
PTrenholme
Senior Member
 
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,147

Rep: Reputation: 330Reputation: 330Reputation: 330Reputation: 330
Question How can I make Kubuntu (Hardy) keep newer modules compiled from source in the kernel?


I broke the screen on my old laptop (Please, don't ask how.) and thought to upgrade to an inexpensive dual AMD X64 laptop. Bought a HP DV9810US 17" screen laptop with "Vista" installed. Yanked that HD and installed a larger empty drive and Kubuntu X64.

But I have a couple of problems:

1) The older nVidia driver in the "restricted" repositories does not support the GeForce 7100M GUP in the laptop, and
2) The older Atheros WiFi driver in those repositories doesn't support the MCP67 chip package on x64.

So I downloaded the nVidia script to install their current driver and the MadWiFi snapshot of the ATH driver updated for x64. After running the script and "make"ing the snapshot, the display and the WiFi connection are both working well.

But I have one problem: If I reboot, the system points itself to the older, non-working, drivers from the repositories, and I have to log in to a terminal window, reinstall nVidia and MadWiFi, and then do a "startx" to get into KDE.

So, can anyone suggest what I need to do to make my changes "stick?" I did turn off the "w" permission on the libGL.so.1 symbolic link which may fix the nVidia problem. (I say "may" because I've not rebooted since doing that.)

But I haven't a clue about how to make the WiFi driver fix immutable.

Any suggestions?

<edit>
Hum. After that "fix" to the library symlink permissions, both problems seem to have been fixed. For one re-boot so far. Very strange.
</edit>

Last edited by PTrenholme; 06-24-2008 at 05:41 PM. Reason: Additional info.
 
Old 06-25-2008, 04:48 AM   #2
tredegar
Guru
 
Registered: May 2003
Location: London, UK
Distribution: Ubuntu 10.04, mostly
Posts: 6,007

Rep: Reputation: 367Reputation: 367Reputation: 367Reputation: 367
Take a look at /etc/modprobe.d/blacklist
 
Old 06-25-2008, 08:31 AM   #3
PTrenholme
Senior Member
 
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,147

Original Poster
Rep: Reputation: 330Reputation: 330Reputation: 330Reputation: 330
Interesting thought. Can the blacklist be used to blacklist specific versions of a driver? If so, how would it help when the distribution updated the driver to, for example, a more recent - but still incompatible - driver? (The madwifi fix, for one, is unlikely to make it into the trunk for some time and there may be intervening releases.)

In any case, my "fix" seems to have held for two reboots now.
 
Old 06-25-2008, 04:09 PM   #4
tredegar
Guru
 
Registered: May 2003
Location: London, UK
Distribution: Ubuntu 10.04, mostly
Posts: 6,007

Rep: Reputation: 367Reputation: 367Reputation: 367Reputation: 367
Quote:
Can the blacklist be used to blacklist specific versions of a driver?
I do not know

My (personal) notes for the installation of the nvidia driver for kubuntu include this:

Quote:
Make sure the files /etc/init.d/nvidia-glx and /etc/init.d/nvidia-kernel do not exist (so delete them).

Edit /etc/default/linux-restricted-modules-common so it contains this line:

DISABLED_MODULES=”nv nvidia_new”

So nasty stuff doesn't get loaded. You'll need to restore this file if you need to go back to the nv driver.

If the file /lib/linux-restricted-modules/.nvidia_new_installed exists, delete it.
If you (or your distro) needs to install a new kernel, you'll have to reinstall the nvidia driver. Such is life, & it's a small price to pay for freedom.
Hope this helps.
 
Old 06-26-2008, 04:58 PM   #5
PTrenholme
Senior Member
 
Registered: Dec 2004
Location: Olympia, WA, USA
Distribution: Fedora, (K)Ubuntu
Posts: 4,147

Original Poster
Rep: Reputation: 330Reputation: 330Reputation: 330Reputation: 330
O.K., now that was helpful: I was not aware of the /etc/default/linux-restricted-modules file, which seems designed to solve the problem I was having. I added ath_hal nv nvidia-new to the list, and I'll see what happens next time the kernel changes.

Again, thank you.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
kubuntu hardy 8.04 hardy BCN94311 jppranker Linux - Hardware 1 06-02-2008 04:45 PM
custom compiled kernel 2.6.21.1 and rc.modules matters Slackware 14 05-18-2007 08:56 AM
kernel compiled, but modules not found? mikedeatworld Slackware 2 11-29-2006 06:54 PM
Compiled Kernel -- Modules can't be Found... joeyjwc Linux - Newbie 2 08-07-2005 05:27 AM
kernel compiled. starts up. no modules, and etc. RHLinuxGUY Slackware 5 04-14-2005 07:04 PM


All times are GMT -5. The time now is 05:55 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration