NVidia tainting kernel?
Hi I have installed Suse 10.0 this morning. Everything worked fine. My Graphics card is "NVidia GeForce 2 Ti". Since the "nv" driver that is built into Suse doesn´t support 3D, and the nvidia-driver, which I can download using YAST, does not do anything at all (big *slap* for the Suse developers), I devided to download and install the original NVidia driver. So I got "NVIDIA-Linux-x86-1.0-7174-pkg1.run" (later versions do not support the GeForce2 Ti any more - I don´t know why). "sh NVIDIA-Linux-x86-1.0-7174-pkg1.run -q" installed the driver, a kernel module was built, successfull. Afterward, i executed "sax2 -m 0=nvidia" to configure my screen. 3D Support was available at this point and I was happy. :) But after a reboot, the driver didn´t work anymore. I searched the internet and found out that I have to modify the /etc/udev/static-devices.txt and add these lines: nvidia0 c 195 0 666 nvidia1 c 195 1 666 nvidia2 c 195 2 666 nvidia3 c 195 3 666 nvidia4 c 195 4 666 nvidia5 c 195 5 666 nvidia6 c 195 6 666 nvidia7 c 195 7 666 nvidiactl c 195 255 666 Now everything was working fine, event a reboot could not destroy the diver module. Then, I made an online update using YAST. Since I have done this update, the nvidia driver doesn´t work anymore (I could use "nv" instead, but this does not provide 3D-Support). dmesg told my something about it, and I think the important lines are: nvidia: module not supported by Novell, setting U taint flag. nvidia: module license 'NVIDIA' taints kernel. nvidia: Unknown parameter `NVreg_DeviceFileUID' What is this? How can the module "taint" the kernel? A new installation of the driver doesn´t solve the problem. Thanks, Chris ======================== Full dmesg: Linux version 2.6.13-15-default (geeko@buildhost) (gcc version 4.0.2 20050901 (prerelease) (SUSE Linux)) #1 Tue Sep 13 14:56:15 UTC 2005 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e8000 - 00000000000ea000 (reserved) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000001fff0000 (usable) BIOS-e820: 000000001fff0000 - 000000001fff8000 (ACPI data) BIOS-e820: 000000001fff8000 - 0000000020000000 (ACPI NVS) BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) BIOS-e820: 00000000ffee0000 - 00000000fff00000 (reserved) BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved) 0MB HIGHMEM available. 511MB LOWMEM available. On node 0 totalpages: 131056 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 126960 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 DMI 2.3 present. ACPI: RSDP (v000 AMI ) @ 0x000fa250 ACPI: RSDT (v001 AMIINT SiS740XX 0x00001000 MSFT 0x0100000b) @ 0x1fff0000 ACPI: FADT (v001 AMIINT SiS740XX 0x00000011 MSFT 0x0100000b) @ 0x1fff0030 ACPI: MADT (v001 AMIINT SiS740XX 0x00001000 MSFT 0x0100000b) @ 0x1fff00c0 ACPI: DSDT (v001 SiS 740 0x00000100 MSFT 0x0100000d) @ 0x00000000 ACPI: PM-Timer IO Port: 0x808 ACPI: local apic disabled Allocating PCI resources starting at 20000000 (gap: 20000000:dec00000) Built 1 zonelists Kernel command line: root=/dev/hda3 vga=0x31a selinux=0 resume=/dev/hda2 splash=silent bootsplash: silent mode. Initializing CPU#0 PID hash table entries: 2048 (order: 11, 32768 bytes) Detected 1466.906 MHz processor. Using pmtmr for high-res timesource Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 513616k/524224k available (2028k kernel code, 10016k reserved, 700k data, 204k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 2935.64 BogoMIPS (lpj=5871299) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Mount-cache hash table entries: 512 CPU: After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000 00000000 00000000 00000000 CPU: After vendor identify, caps: 0383fbff c1c3fbff 00000000 00000000 00000000 00000000 00000000 CPU: CLK_CTL MSR was 6003d22f. Reprogramming to 2003d22f CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 256K (64 bytes/line) CPU: After all inits, caps: 0383fbff c1c3fbff 00000000 00000020 00000000 00000000 00000000 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. mtrr: v2.0 (20020519) CPU: AMD Athlon(tm) XP 1700+ stepping 01 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. checking if image is initramfs... it is Freeing initrd memory: 1746k freed ACPI: Looking for DSDT in initrd... not found! not found! ACPI: setting ELCR to 0200 (from 0c20) NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xfdb01, last bus=2 PCI: Using configuration type 1 ACPI: Subsystem revision 20050408 ACPI: Interpreter enabled ACPI: Using PIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) PCI: Probing PCI hardware (bus 00) ACPI: Assume root bridge [\_SB_.PCI0] segment is 0 Uncovering SIS963 that hid as a SIS503 (compatible=0) Enabling SiS 96x SMBus. Boot video device is 0000:01:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: Power Resource [URP1] (off) ACPI: Power Resource [URP2] (off) ACPI: Power Resource [FDDP] (off) ACPI: Power Resource [LPTP] (off) ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 7 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 *5 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 *5 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 7 *10 11 12 14 15) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 10 devices PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report TC classifier action (bugs to netdev@vger.kernel.org cc hadi@cyberus.ca) PCI: Bridge: 0000:00:01.0 IO window: disabled. MEM window: cdd00000-cfefffff PREFETCH window: bda00000-cdbfffff apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac) apm: overridden by ACPI. audit: initializing netlink socket (disabled) audit(1135693469.948:1): initialized Total HugeTLB memory allocated, 0 VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API vesafb: framebuffer at 0xc0000000, mapped to 0xe0880000, using 10240k, total 65536k vesafb: mode is 1280x1024x16, linelength=2560, pages=1 vesafb: protected mode interface info at c000:bdb0 vesafb: scrolling: redraw vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0 bootsplash 3.1.6-2004/03/31: looking for picture...<6> silentjpeg size 112645 bytes,<6>...found (1280x1024, 17839 bytes, v3). Console: switching to colour frame buffer device 158x59 fb0: VESA VGA frame buffer device isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found Real Time Clock Driver v1.12 PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12 serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 RAMDISK driver initialized: 16 RAM disks of 64000K size 1024 blocksize loop: loaded (max 8 devices) mice: PS/2 mouse device common for all mice input: PC Speaker md: md driver 0.90.2 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 3.38 NET: Registered protocol family 2 input: AT Translated Set 2 keyboard on isa0060/serio0 IP route cache hash table entries: 8192 (order: 3, 32768 bytes) TCP established hash table entries: 32768 (order: 6, 262144 bytes) TCP bind hash table entries: 32768 (order: 5, 131072 bytes) TCP: Hash tables configured (established 32768 bind 32768) TCP reno registered NET: Registered protocol family 1 Using IPI Shortcut mode ACPI wakeup devices: PCI0 PS2M PS2K UAR1 USB1 USB2 USB3 USB4 S139 LAN MDM AUD SLPB ACPI: (supports S0 S1 S4 S5) Freeing unused kernel memory: 204k freed Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx SIS5513: IDE controller at PCI slot 0000:00:02.5 SIS5513: chipset revision 0 SIS5513: not 100% native mode: will probe irqs later SIS5513: SiS 962/963 MuTIOL IDE UDMA133 controller ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA Probing IDE interface ide0... input: ImPS/2 Generic Wheel Mouse on isa0060/serio1 hda: WDC WD600AB-00BVA0, ATA DISK drive hdb: ST38641A, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hda: max request size: 128KiB hda: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100) hda: cache flushes not supported hda: hda1 hda2 hda3 hdb: max request size: 128KiB hdb: 16809660 sectors (8606 MB) w/128KiB Cache, CHS=16676/16/63, UDMA(33) hdb: cache flushes not supported hdb: hdb1 Probing IDE interface ide1... hdc: _NEC DV-5700B, ATAPI CD/DVD-ROM drive hdd: SONY CD-RW CRX185E3, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 ACPI: CPU0 (power states: C1[C1]) hdc: ATAPI 40X DVD-ROM drive, 256kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.20 hdd: ATAPI 8X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33) Attempting manual resume swsusp: Suspend partition has wrong signature? ReiserFS: hda3: found reiserfs format "3.6" with standard journal ReiserFS: hda3: using ordered data mode ReiserFS: hda3: journal params: device hda3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: hda3: checking transaction log (hda3) ReiserFS: hda3: Using r5 hash to sort names bootsplash: status on console 0 changed to on md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. Adding 1036184k swap on /dev/hda2. Priority:-1 extents:1 device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com NTFS driver 2.1.23 [Flags: R/W MODULE]. NTFS volume version 3.1. parport: PnPBIOS parport detected. parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA] lp0: using parport0 (interrupt-driven). NET: Registered protocol family 10 Disabled Privacy Extensions on device c036b920(lo) IPv6 over IPv4 tunneling driver ip6_tables: (C) 2000-2002 Netfilter core team pci_hotplug: PCI Hot Plug PCI Core version: 0.5 shpchp: shpc_init : shpc_cap_offset == 0 shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Linux agpgart interface v0.101 (c) Dave Jones agpgart: Detected SiS 746 chipset agpgart: AGP aperture is 128M @ 0xd0000000 ip_tables: (C) 2000-2002 Netfilter core team i2c-sis96x version 1.0.0 sis96x_smbus 0000:00:02.1: SiS96x SMBus base address: 0x0c00 ip_conntrack version 2.1 (4095 buckets, 32760 max) - 248 bytes per conntrack usbcore: registered new driver usbfs usbcore: registered new driver hub ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 5 PCI: setting IRQ 5 as level-triggered ACPI: PCI Interrupt 0000:00:03.0[A] -> Link [LNKE] -> GSI 5 (level, low) -> IRQ 5 ohci_hcd 0000:00:03.0: OHCI Host Controller ohci_hcd 0000:00:03.0: new USB bus registered, assigned bus number 1 ohci_hcd 0000:00:03.0: irq 5, io mem 0xcfffd000 hub 1-0:1.0: USB hub found hub 1-0:1.0: 3 ports detected ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 5 ACPI: PCI Interrupt 0000:00:03.1[B] -> Link [LNKF] -> GSI 5 (level, low) -> IRQ 5 ohci_hcd 0000:00:03.1: OHCI Host Controller ohci_hcd 0000:00:03.1: new USB bus registered, assigned bus number 2 ohci_hcd 0000:00:03.1: irq 5, io mem 0xcfffe000 hub 2-0:1.0: USB hub found hub 2-0:1.0: 3 ports detected ieee1394: Initialized config rom entry `ip1394' ohci1394: $Rev: 1299 $ Ben Collins <bcollins@debian.org> ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11 PCI: setting IRQ 11 as level-triggered ACPI: PCI Interrupt 0000:00:0c.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[11] MMIO=[cfffb800-cfffbfff] Max Packet=[2048] ACPI-0212: *** Warning: Device is not power manageable ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 10 PCI: setting IRQ 10 as level-triggered ACPI: PCI Interrupt 0000:00:03.2[D] -> Link [LNKH] -> GSI 10 (level, low) -> IRQ 10 ehci_hcd 0000:00:03.2: EHCI Host Controller ehci_hcd 0000:00:03.2: new USB bus registered, assigned bus number 3 ehci_hcd 0000:00:03.2: irq 10, io mem 0xcffff000 PCI: cache line size of 64 is not supported by device 0000:00:03.2 ehci_hcd 0000:00:03.2: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004 hub 3-0:1.0: USB hub found hub 3-0:1.0: 6 ports detected sis900.c: v1.08.08 Jan. 22 2005 ACPI-0212: *** Warning: Device is not power manageable ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11 ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 0000:00:04.0: Realtek RTL8201 PHY transceiver found at address 1. 0000:00:04.0: Using transceiver found at address 1 as default eth0: SiS 900 PCI Fast Ethernet at 0xdc00, IRQ 11, 00:0a:e6:98:db:73. 8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004) 8139cp: pci dev 0000:00:0d.0 (id 10ec:8139 rev 10) is not an 8139C+ compatible chip 8139cp: Try the "8139too" driver instead. 8139too Fast Ethernet driver 0.9.27 ACPI: PCI Interrupt 0000:00:0d.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11 eth1: RealTek RTL8139 at 0xe177a700, 00:50:fc:ad:cd:e1, IRQ 11 eth1: Identified 8139 chip type 'RTL-8100B/8139D' ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5 ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKC] -> GSI 5 (level, low) -> IRQ 5 gameport: ES1938 is pci0000:00:0a.0/gameport0, io 0xc800, speed 1065kHz ieee1394: Host added: ID:BUS[0-00:1023] GUID[001106000099d044] bootsplash: status on console 0 changed to on BIOS EDD facility v0.16 2004-Jun-25, 2 devices found NET: Registered protocol family 17 eth1: Media Link On 100mbps full-duplex nvidia: module not supported by Novell, setting U taint flag. nvidia: module license 'NVIDIA' taints kernel. nvidia: Unknown parameter `NVreg_DeviceFileUID' ACPI: Power Button (FF) [PWRF] ACPI: Power Button (CM) [PWRB] ACPI: Sleep Button (CM) [SLPB] IA-32 Microcode Update Driver: v1.14 <tigran@veritas.com> microcode: CPU0 not a capable Intel processor microcode: No new microcode data for CPU0 IA-32 Microcode Update Driver v1.14 unregistered bootsplash: status on console 0 changed to on powernow-k8: Processor cpuid 681 not supported bootsplash: status on console 0 changed to on eth1: no IPv6 routers present bootsplash: status on console 0 changed to on SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.1.4 DST=224.0.0.251 LEN=109 TOS=0x00 PREC=0x00 TTL=255 ID=5 DF PROTO=UDP SPT=5353 DPT=5353 LEN=89 subfs 0.9 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 subfs: unsuccessful attempt to mount media (256) cdrom: This disc doesn't have any tracks I recognize! SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.1.4 DST=224.0.0.251 LEN=109 TOS=0x00 PREC=0x00 TTL=255 ID=6 DF PROTO=UDP SPT=5353 DPT=5353 LEN=89 SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.1.4 DST=224.0.0.251 LEN=109 TOS=0x00 PREC=0x00 TTL=255 ID=7 DF PROTO=UDP SPT=5353 DPT=5353 LEN=89 nvidia: module not supported by Novell, setting U taint flag. nvidia: Unknown parameter `NVreg_DeviceFileUID' SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.1.4 DST=224.0.0.251 LEN=109 TOS=0x00 PREC=0x00 TTL=255 ID=8 DF PROTO=UDP SPT=5353 DPT=5353 LEN=89 nvidia: module not supported by Novell, setting U taint flag. nvidia: Unknown parameter `NVreg_DeviceFileUID' SFW2-INext-DROP-DEFLT IN=eth1 OUT= MAC= SRC=192.168.1.4 DST=224.0.0.251 LEN=109 TOS=0x00 PREC=0x00 TTL=255 ID=9 DF PROTO=UDP SPT=5353 DPT=5353 LEN=89 __________________________________________________________________________ Erweitern Sie FreeMail zu einem noch leistungsstarkeren E-Mail-Postfach! Mehr Infos unter http://freemail.web.de/home/landingpad/?mc=021131
On Tuesday 27 December 2005 9:08 am, Christian Lange wrote:
Then, I made an online update using YAST. Since I have done this update, the nvidia driver doesn´t work anymore (I could use "nv" instead, but this does not provide 3D-Support). dmesg told my something about it, and I think the important lines are: nvidia: module not supported by Novell, setting U taint flag. nvidia: module license 'NVIDIA' taints kernel. nvidia: Unknown parameter `NVreg_DeviceFileUID'
What is this? How can the module "taint" the kernel? A new installation of the driver doesn´t solve the problem.
3D isn't working in the last 12 or so installs I've done.....users are NOT happy, and not all boxen have nVidia, but most do. I don't know what happened in SUSE 10.0, but once again, this is some of the stuff that keeps new users away from Linux!! Fred -- Paid purchaser of ALL SuSE Linux releases since 6.x
On Tue, 2005-12-27 at 09:40 -0500, Fred A. Miller wrote:
On Tuesday 27 December 2005 9:08 am, Christian Lange wrote:
Then, I made an online update using YAST. Since I have done this update, the nvidia driver doesn´t work anymore (I could use "nv" instead, but this does not provide 3D-Support). dmesg told my something about it, and I think the important lines are: nvidia: module not supported by Novell, setting U taint flag. nvidia: module license 'NVIDIA' taints kernel. nvidia: Unknown parameter `NVreg_DeviceFileUID'
What is this? How can the module "taint" the kernel? A new installation of the driver doesn´t solve the problem.
3D isn't working in the last 12 or so installs I've done.....users are NOT happy, and not all boxen have nVidia, but most do. I don't know what happened in SUSE 10.0, but once again, this is some of the stuff that keeps new users away from Linux!!
Fred
Then you are doing something wrong. The Nvidia driver install using YOU does work. It has worked in -every- install/upgrade I have done since I started to use an Nvidia graphics card. As has been stated many times in the SUSE english list the 3D checkbox will -not- be selected when checking with sax2 but 3d -is- turned on. The tell tail sign that 3D is working is the Nvidia splash screen showing when "X" starts up. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Tuesday 27 December 2005 10:01 am, Ken Schneider wrote:
3D isn't working in the last 12 or so installs I've done.....users are NOT happy, and not all boxen have nVidia, but most do. I don't know what happened in SUSE 10.0, but once again, this is some of the stuff that keeps new users away from Linux!!
Fred
Then you are doing something wrong. The Nvidia driver install using YOU does work. It has worked in -every- install/upgrade I have done since I started to use an Nvidia graphics card. As has been stated many times in the SUSE english list the 3D checkbox will -not- be selected when checking with sax2 but 3d -is- turned on. The tell tail sign that 3D is working is the Nvidia splash screen showing when "X" starts up.
Correct, and guess what - it's NOT working in a LOT of boxen! Fred -- Paid purchaser of ALL SuSE Linux releases since 6.x
Then you are doing something wrong. The Nvidia driver install using YOU does work. It has worked in -every- install/upgrade I have done since I started to use an Nvidia graphics card. As has been stated many times in the SUSE english list the 3D checkbox will -not- be selected when checking with sax2 but 3d -is- turned on. The tell tail sign that 3D is working is the Nvidia splash screen showing when "X" starts up.
Correct, and guess what - it's NOT working in a LOT of boxen!
Hmmm I've installed SUSE10 on a LOT of computers too... probably 20 or 30 now, and every single one with nVidia cards has worked perfectly. Teh few that have had ATI have been a nightmare (but eventually did work in the end). So far, the only time I've heard of anyone having problems with nVidia on SUSE10 is from reports from Fred on this list. I don't know what the specific circumstances are for you Fred, but... I've never experienced any problems with nVidia on 10.0 (on an almost random combination of hardware). 3D has always worked on the very first try after installing the nVidia drivers using YAST - this is always done on the initial install. 3D acceleration works, and all customers/friends/acquaintances that I've assisted with 10.0 installs are all very happy. C.
So is it, or is it not necessary to download the Nvidia driver from the Nvidia site? I use a Nvidia Quadro Pro 2 and 3D seems not to work. If I start a game that needs 3D it says that I do not have 3D support. Is there a howto that also applies to SUSE 10 / Nvidia? 2005/12/27, Clayton <smaug42@gmail.com>:
Then you are doing something wrong. The Nvidia driver install using YOU does work. It has worked in -every- install/upgrade I have done since I started to use an Nvidia graphics card. As has been stated many times in the SUSE english list the 3D checkbox will -not- be selected when checking with sax2 but 3d -is- turned on. The tell tail sign that 3D is working is the Nvidia splash screen showing when "X" starts up.
Correct, and guess what - it's NOT working in a LOT of boxen!
Hmmm I've installed SUSE10 on a LOT of computers too... probably 20 or 30 now, and every single one with nVidia cards has worked perfectly. Teh few that have had ATI have been a nightmare (but eventually did work in the end).
So far, the only time I've heard of anyone having problems with nVidia on SUSE10 is from reports from Fred on this list. I don't know what the specific circumstances are for you Fred, but... I've never experienced any problems with nVidia on 10.0 (on an almost random combination of hardware). 3D has always worked on the very first try after installing the nVidia drivers using YAST - this is always done on the initial install. 3D acceleration works, and all customers/friends/acquaintances that I've assisted with 10.0 installs are all very happy.
C.
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
On Tue, 2005-12-27 at 16:30 +0100, Jan van Kollenburg wrote:
So is it, or is it not necessary to download the Nvidia driver from the Nvidia site? I use a Nvidia Quadro Pro 2 and 3D seems not to work. If I start a game that needs 3D it says that I do not have 3D support. Is there a howto that also applies to SUSE 10 / Nvidia?
Use the one that gets installed through the YOU interface, when you would normally install security fixes. This way you will not have problems when a kernel update takes place. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Tue, 2005-12-27 at 11:00 -0500, Ken Schneider wrote:
On Tue, 2005-12-27 at 16:30 +0100, Jan van Kollenburg wrote:
So is it, or is it not necessary to download the Nvidia driver from the Nvidia site? I use a Nvidia Quadro Pro 2 and 3D seems not to work. If I start a game that needs 3D it says that I do not have 3D support. Is there a howto that also applies to SUSE 10 / Nvidia?
Use the one that gets installed through the YOU interface, where you would normally install security fixes. This way you will not have problems when a kernel update takes place.
One further point, if you have installed the driver from the Nvidia site you will have to un-install that one first otherwise it driver download using YOU will not work. I think this is where many people have failures. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
On Tuesday 27 December 2005 10:16 am, Clayton wrote:
So far, the only time I've heard of anyone having problems with nVidia on SUSE10 is from reports from Fred on this list. I don't know what the specific circumstances are for you Fred, but... I've never experienced any problems with nVidia on 10.0 (on an almost random combination of hardware). 3D has always worked on the very first try after installing the nVidia drivers using YAST - this is always done on the initial install. 3D acceleration works, and all customers/friends/acquaintances that I've assisted with 10.0 installs are all very happy.
Check the archives for the suse English list........MANY have had problems. Very happy for you Clayton that it all works. I happen to know that it doesn't on a LOT of systems, and should. Fred -- Paid purchaser of ALL SuSE Linux releases since 6.x
On Tue, 2005-12-27 at 15:08 +0100, Christian Lange wrote:
Hi
I have installed Suse 10.0 this morning. Everything worked fine. My Graphics card is "NVidia GeForce 2 Ti". Since the "nv" driver that is built into Suse doesn´t support 3D, and the nvidia-driver, which I can download using YAST, does not do anything at all (big *slap* for the Suse developers),
And what makes you think it does nothing? Works fine for probably everybody else. Just take a look at the frame rate difference between the two.
I decided to download and install the original NVidia driver. So I got "NVIDIA-Linux-x86-1.0-7174-pkg1.run" (later versions do not support the GeForce2 Ti any more - I don´t know why). "sh NVIDIA-Linux-x86-1.0-7174-pkg1.run -q" installed the driver, a kernel module was built, successful. Afterward, i executed "sax2 -m 0=nvidia" to configure my screen. 3D Support was available at this point and I was happy. :) But after a reboot, the driver didn´t work anymore. I searched the internet and found out that I have to modify the /etc/udev/static-devices.txt and add these lines: nvidia0 c 195 0 666 nvidia1 c 195 1 666 nvidia2 c 195 2 666 nvidia3 c 195 3 666 nvidia4 c 195 4 666 nvidia5 c 195 5 666 nvidia6 c 195 6 666 nvidia7 c 195 7 666 nvidiactl c 195 255 666 Now everything was working fine, event a reboot could not destroy the diver module.
Then, I made an online update using YAST. Since I have done this update, the nvidia driver doesn´t work anymore (I could use "nv" instead, but this does not provide 3D-Support). dmesg told my something about it, and I think the important lines are: nvidia: module not supported by Novell, setting U taint flag. nvidia: module license 'NVIDIA' taints kernel.
This is -not- an unusual occurrence. The VMware modules do the same thing.
nvidia: Unknown parameter `NVreg_DeviceFileUID'
What is this? How can the module "taint" the kernel? A new installation of the driver doesn´t solve the problem.
Thanks, Chris
======================== Full dmesg:
It was -NOT- necessary to send the entire dmesg output to only show that the module "taints" the kernel.
nvidia: module not supported by Novell, setting U taint flag. nvidia: module license 'NVIDIA' taints kernel. nvidia: Unknown parameter `NVreg_DeviceFileUID'
nvidia: module not supported by Novell, setting U taint flag. nvidia: Unknown parameter `NVreg_DeviceFileUID'
nvidia: module not supported by Novell, setting U taint flag. nvidia: Unknown parameter `NVreg_DeviceFileUID'
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
Christian Lange wrote:
What is this? How can the module "taint" the kernel?
A module "taint" the kernel when it's license it's not GPL compatible. read : http://www.tux.org/lkml/#s1-18
participants (6)
-
Christian Lange
-
Clayton
-
Cristian Rodriguez
-
Fred A. Miller
-
Jan van Kollenburg
-
Ken Schneider