diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-March/012493.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-March/012493.html | 182 |
1 files changed, 182 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-March/012493.html b/zarb-ml/mageia-dev/2012-March/012493.html new file mode 100644 index 000000000..6e9680c2f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-March/012493.html @@ -0,0 +1,182 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20NVidia%20fallback%20to%20Nouveau%20after%20latest%20Kernel%20updates&In-Reply-To=%3C1330677493.3319.4.camel%40foxbase%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="012492.html"> + <LINK REL="Next" HREF="012494.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates</H1> + <B>Robert Fox</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20NVidia%20fallback%20to%20Nouveau%20after%20latest%20Kernel%20updates&In-Reply-To=%3C1330677493.3319.4.camel%40foxbase%3E" + TITLE="[Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates">list at foxconsult.net + </A><BR> + <I>Fri Mar 2 09:38:13 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="012492.html">[Mageia-dev] i586 tainted stalled? +</A></li> + <LI>Next message: <A HREF="012494.html">[Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#12493">[ date ]</a> + <a href="thread.html#12493">[ thread ]</a> + <a href="subject.html#12493">[ subject ]</a> + <a href="author.html#12493">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Since last Cauldron kernel update, I have two nvidia based system which +now fallback to nouveau when starting X - stating nvidia cannot be +loaded. + +checking in dmesg - I see that the nouveau driver grabs the card before +the nvidia driver can - but trying to remove the nouveau driver wants to +remove over 800 packages! + +How can I get the nvidia proprietary driver back?? + +[ 53.253035] [drm] nouveau 0000:04:00.0: Attempting to load BIOS image +from PRAMIN +[ 53.298983] [drm] nouveau 0000:04:00.0: ... appears to be valid +[ 53.298987] [drm] nouveau 0000:04:00.0: BIT BIOS found +[ 53.298990] [drm] nouveau 0000:04:00.0: Bios version 62.94.20.00 +[ 53.298993] [drm] nouveau 0000:04:00.0: TMDS table version 2.0 +[ 53.298996] [drm] nouveau 0000:04:00.0: Found Display Configuration +Block version 4.0 +[ 53.298998] [drm] nouveau 0000:04:00.0: Raw DCB entry 0: 02000300 +00000028 +[ 53.299013] [drm] nouveau 0000:04:00.0: Raw DCB entry 1: 01000302 +00020030 +[ 53.299015] [drm] nouveau 0000:04:00.0: Raw DCB entry 2: 04011310 +00000028 +[ 53.299019] [drm] nouveau 0000:04:00.0: Raw DCB entry 3: 02022332 +00020010 +[ 53.299024] [drm] nouveau 0000:04:00.0: Raw DCB entry 4: 0000000e +00000000 +[ 53.299029] [drm] nouveau 0000:04:00.0: DCB connector table: VHER +0x40 5 16 4 +[ 53.299039] [drm] nouveau 0000:04:00.0: 0: 0x00001030: type 0x30 +idx 0 tag 0x07 +[ 53.299052] [drm] nouveau 0000:04:00.0: 1: 0x00000100: type 0x00 +idx 1 tag 0xff +[ 53.299062] [drm] nouveau 0000:04:00.0: 2: 0x00002261: type 0x61 +idx 2 tag 0x08 +[ 53.299069] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table 0 at +offset 0xD21E +[ 53.324438] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table 1 at +offset 0xD633 +[ 53.327051] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table 2 at +offset 0xE624 +[ 53.327058] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table 3 at +offset 0xE76D +[ 53.328136] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table 4 at +offset 0xE9A9 +[ 53.328140] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table at +offset 0xEA0E +[ 53.348146] [drm] nouveau 0000:04:00.0: 0xEA0E: Condition still not +met after 20ms, skipping following opcodes +[ 53.366853] [drm] nouveau 0000:04:00.0: 1 available performance +level(s) +[ 53.366858] [drm] nouveau 0000:04:00.0: 3: core 500MHz shader 1250MHz +memory 500MHz voltage 1100mV fanspeed 100% +[ 53.366873] [drm] nouveau 0000:04:00.0: c: core 500MHz shader 1250MHz +memory 499MHz voltage 1100mV +[ 53.368881] [TTM] Zone kernel: Available graphics memory: 1543414 +kiB. +[ 53.368884] [TTM] Initializing pool allocator. +[ 53.368894] [drm] nouveau 0000:04:00.0: Detected 768MiB VRAM +[ 53.372117] [drm] nouveau 0000:04:00.0: 512 MiB GART (aperture) +[ 53.397649] [drm] Supports vblank timestamp caching Rev 1 +(10.10.2010). +[ 53.397652] [drm] No driver support for vblank timestamp query. +[ 53.656361] [drm] nouveau 0000:04:00.0: allocated 1680x1050 fb: +0x310000, bo ffff8800b1df9400 +[ 53.656475] fbcon: nouveaufb (fb0) is primary device +[ 53.656688] Console: switching to colour frame buffer device 210x65 +[ 53.656694] fb0: nouveaufb frame buffer device +[ 53.656696] drm: registered panic notifier +[ 53.656703] [drm] Initialized nouveau 0.0.16 20090420 for +0000:04:00.0 on minor 0 +[ 56.018019] eth0: no IPv6 routers present +[ 112.967128] 2:2:1: cannot get freq at ep 0x4 +[ 113.975124] 2:3:1: cannot get freq at ep 0x83 +[ 115.031128] 2:3:1: cannot get freq at ep 0x83 +[ 116.041124] 2:2:1: cannot get freq at ep 0x4 +[ 117.054141] 2:3:1: cannot get freq at ep 0x83 +[ 123.675318] process `skype' is using obsolete setsockopt SO_BSDCOMPAT +[ 243.059920] NVRM: The NVIDIA probe routine was not called for 1 +device(s). +[ 243.059923] NVRM: This can occur when a driver such as nouveau, +rivafb, +[ 243.059924] NVRM: nvidiafb, or rivatv was loaded and obtained +ownership of +[ 243.059925] NVRM: the NVIDIA device(s). +[ 243.059927] NVRM: Try unloading the conflicting kernel module (and/or +[ 243.059928] NVRM: reconfigure your kernel without the conflicting +[ 243.059929] NVRM: driver(s)), then try loading the NVIDIA kernel +module +[ 243.059929] NVRM: again. +[ 243.059931] NVRM: No NVIDIA graphics adapter probed! +[ 566.999504] NVRM: The NVIDIA probe routine was not called for 1 +device(s). +[ 566.999507] NVRM: This can occur when a driver such as nouveau, +rivafb, +[ 566.999508] NVRM: nvidiafb, or rivatv was loaded and obtained +ownership of +[ 566.999509] NVRM: the NVIDIA device(s). +[ 566.999511] NVRM: Try unloading the conflicting kernel module (and/or +[ 566.999512] NVRM: reconfigure your kernel without the conflicting +[ 566.999512] NVRM: driver(s)), then try loading the NVIDIA kernel +module +[ 566.999513] NVRM: again. +[ 566.999515] NVRM: No NVIDIA graphics adapter probed! + +Thx, +R.Fox + + +</PRE> + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="012492.html">[Mageia-dev] i586 tainted stalled? +</A></li> + <LI>Next message: <A HREF="012494.html">[Mageia-dev] NVidia fallback to Nouveau after latest Kernel updates +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#12493">[ date ]</a> + <a href="thread.html#12493">[ thread ]</a> + <a href="subject.html#12493">[ subject ]</a> + <a href="author.html#12493">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |