Got the Kubuntu blues... Crashes and drivers and nosound, oh my!
UbuntuThis forum is for the discussion of Ubuntu Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Got the Kubuntu blues... Crashes and drivers and nosound, oh my!
Hi Questioners!
I've recently bought a new PC as I've moved across the country, and have installed Kubuntu Feisty 7.04 on it, via a LiveCD. It's currently dual booting with Vista Ultimate, mainly because my girlfriend wants to use it =/. That aside... I've been having a few issues since I installed Kubuntu a week or so ago.
1) PC will crash randomly. Usually when I'm doing something GPU/CPU intensive (i.e. running WoW under cedega), however sometimes it'll just crash randomly (whilst changing songs on amarok, whilst browsing on firefox...). I'm using a Microsoft keyboard that came with it, and whenever it crashes, the caps lock light starts flashing. Also, the mouse stops responding. I know this isn't much info to go by, but can anyone direct me to some tools that can help me troubleshoot what's causing the problem? And then hopefully I can work out from whatever it tells me what to do, or someone here can point me further the right way with the output :P.
2) NVidia drivers. I have an NVidia GeForce 9600 GT (256MB I think) installed on the PC. As far as I'm aware, I've downloaded the correct drivers for it. I've installed them and they work fine. However, when I reboot the PC X will not start, and when I attempt to use startx, I get an error about incompatibility...
Error: API mismatch: this NVIDIA driver component has version 100.14.19, but the NVIDIA kernel module's version does not match. Please make sure that the kernel module and all NVIDIA driver components have the same version.
(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! Please ensure
(EE) NVIDIA(0): that there is a supported NVIDIA GPU in this system, and
(EE) NVIDIA(0): that the NVIDIA device files have been created properly.
(EE) NVIDIA(0): Please consult the NVIDIA README for details.
(EE) NVIDIA(0): *** Aborting ***
(EE) Screen(s) found, but none have a usable configuration.
Eep... that took a while to type out =/.
Anyhoot, I can rerun the installer for the NVIDIA drivers I have (NVIDIA-Linux-x86-100.14.19-pkg1.run) and it'll reinstall, rebuild everything, rewrite the X config file, and it'll work a treat... Until I reboot. I wouldn't mind, but because of problem 1 I'm regularly rebooting :P.
N.B. Did also notice just now, that in KInfoCenter->OpenGL->Direct Rendering->Driver->Kernel Module it does say "unknown".
3) A more minor one... But I run WoW under cedega 6.x (not sure which), and it will crash randomly. Not the same crashes as in problem one - just cedega crashing. Has anyone got any tips or tricks with that? Config.WTF settings, cedega settings, different ways of running it, versions that work better, etc? . That'd be really helpful!
Bear in mind, I am a bit of a *NIX noob, however I do know how to use a terminal and I'm happy to try out most things that are suggested (for the right amount of money ).
Specs:
AMD Athlon 64 3500+
A8N-SLI Motherboard
NIVDIA 8600GT PCI-E
1GB RAM (4 x 256MB DDR)
200GB Western Digital HDD
400 watt power supply
Creative SB!Live 5.1 Sound Card and 2.1 Speakers
LG DVD-RW Drive
Dual booting (via grub) Kubuntu Feisty Fawn 7.04/Windows Vista Ultimate
Running:
KDE 3.5.6
X server 11.0
Video Drivers NVIDIA 100.14.19
Relevant outputs:
uname -a Linux mongrel 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 i686 GNU/Linux dmesg | grep NVIDIA [ 0.000000] ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000e) @ 0x00000000
[ 54.377099] nvidia: module license 'NVIDIA' taints kernel.
[ 54.380591] NVRM: loading NVIDIA Linux x86 Kernel Module 1.0-7184 Tue Aug 1 18:38:58 PDT 2006
[ 149.476000] NVRM: loading NVIDIA UNIX x86 Kernel Module 100.14.19 Wed Sep 12 14:12:24 PDT 2007
[ 183.364000] NVRM: loading NVIDIA UNIX x86 Kernel Module 100.14.19 Wed Sep 12 14:12:24 PDT 2007
man women Segmentation Fault (core dumped)
Thanks guys!
-nfsnobody
Last edited by WhiteyDude; 09-29-2007 at 04:05 AM.
Well, I'm not sure why things are randomly crashing, but the reason why the nvidia module is getting reset is because Ubuntu is trying to load one from its linux-restricted package, which is linking to the 9755 driver.
So, type this in:
Code:
kdesu kate /etc/default/linux-restricted-modules-common
Well, I'm not sure why things are randomly crashing, but the reason why the nvidia module is getting reset is because Ubuntu is trying to load one from its linux-restricted package, which is linking to the 9755 driver.
So, type this in:
Code:
kdesu kate /etc/default/linux-restricted-modules-common
Change it so it says:
Code:
DISABLED_MODULES="nvidia"
Now see if it keeps your 3D driver.
Thanks for replying angryfirelord .
Tried that, rebooted, same problem
here's my linux-restricted-modules-common file at present:
# This file is sourced from the linux-restricted-modules-common init
# script and is used to disable the link-on-boot feature, one module
# at a time. This can be useful if you want to use hand-compiled
# versions of one or more modules, but keep linux-restricted-modules
# installed on your system, or just to disable modules you don't use
# and speed up your boot process by a second or two.
#
# Use a space-separated list of modules you wish to not have linked
# on boot. The following example shows a (condensed) list of all
# modules shipped in the linux-restricted-modules packages:
#
# DISABLED_MODULES="ath_hal fc fglrx ltm nv"
#
# Note that disabling "fc" disables all fcdsl drivers, "ltm" disables
# ltmodem and ltserial, and "nv" disables both the nvidia drivers.
# You can also name each module individually, if you prefer a subset.
Also, on my Debian system, I had trouble building the module with the latest driver. I used an older one which worked fine. Not sure if it'll make any difference though. http://www.nvidia.com/object/linux_d...100.14.11.html
Nope, tried both of those seperately, that didn't do it .
I did notice however, that whilst running the NVIDIA driver installer, it asks if I want to connect to the NVIDIA site to download a precompiled kernel. As I use knetworkmanager to manage my wireless network, I'm never online before KDE boots, so I never hit "Yes" on this, I always allow it to compile one itself. Would that make a difference?
Kinfocenter->OpenGL->Direct Rendering->Driver->Kernel module is still "unknown" even after I compile one...
Nah, connecting to the internet won't help you. I've never come across this "precompiled" thing anyway.
If you've kept your system up-to-date, you may have more than one kernel installed from the security updates. Open up Synaptic, search for linux-restricted, and completely remove (a.k.a. purging) all but the current one. Then, search for linux-image and do that same thing.
Nah, connecting to the internet won't help you. I've never come across this "precompiled" thing anyway.
If you've kept your system up-to-date, you may have more than one kernel installed from the security updates. Open up Synaptic, search for linux-restricted, and completely remove (a.k.a. purging) all but the current one. Then, search for linux-image and do that same thing.
Nope . New errors though! Hopefully that helps :P.
dlopen: /usr/lb/libGLcore.so.1: undefined symbol: _nv000043g1
(EE) Failed to load /usr/lib/xorg/modules//libglx.so
(EE) Failed to load module "glx" (loader failed, 7)
(WW) NVIDIA: No matching Device section for instance (BusID PCI:1:0:0) found
(EE) No devices detected.
Fatal server error:
no screens found
X10: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.
Any other ideas guys? . Still got the other problems too :P.
Have you tried the Envy installer yet? It might be worth a look. It will download all dependencies, drivers, etc. and compile/install the drivers for you.
Envy will install the latest one for you, make sure the current ones are uninstalled 1st tho, and also sudo apt-get install nvidia-glx-new will install the latest nvidia drivers straight from the repositories. I do no a few people that had problems with that tho, but it solved the problem for me, i had exactly the same one you did on my laptop with a 8400. The random crashing may be down to your psu, dont know your exact card but the newest gpu“s need a pretty huge psu to crank them out, so because your comp is dyeing under intense gpu/cpu action this may be it.
Ask the guys at the cedega forums for help there, i expect they may have the answer you are looking for.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.