Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: NVIDIA Makes Modest Update With 190.xx Linux Driver

  1. #1
    Join Date
    Jan 2007
    Posts
    14,641

    Default NVIDIA Makes Modest Update With 190.xx Linux Driver

    Phoronix: NVIDIA Makes Modest Update With 190.xx Linux Driver

    Late last month there was a private beta driver from NVIDIA for the 190.xx Linux driver series that was leaked onto the Internet. There was no complete change-log with this leak, but we have a change-log now as NVIDIA this afternoon released its first public beta driver...

    http://www.phoronix.com/vr.php?view=NzM5NQ

  2. #2

    Default

    This would be much better if the driver actually worked.... Just about everybody says that it results in a black screen and kernel oops when starting X.

  3. #3
    Join Date
    May 2007
    Location
    Third Rock from the Sun
    Posts
    6,583

    Default

    Quote Originally Posted by thefirstm View Post
    This would be much better if the driver actually worked.... Just about everybody says that it results in a black screen and kernel oops when starting X.
    Deployed it fine this afternoon to over 60 machine of various distros.




    Meanwhile they are all crunching away at Cuda apps just fine as well.

  4. #4
    Join Date
    Jul 2007
    Posts
    57

    Default

    Please specify kernel and xorg versions... For me it's giving blank screen, 2.6.30.2 + Xorg 1.6.2 (ArchLinux).

  5. #5
    Join Date
    Jan 2009
    Posts
    206

    Default

    Quote Originally Posted by Kirurgs View Post
    Please specify kernel and xorg versions... For me it's giving blank screen, 2.6.30.2 + Xorg 1.6.2 (ArchLinux).
    WorksForMe(TM), Archlinux x86_64 ~ testing repo enabled ~ pacman -Syu'ed ~ tested on 2 machines with GeForce 260 GTX and 9600GT. Hats off to nvidia yet again for quality drivers.

  6. #6
    Join Date
    Jul 2007
    Posts
    57

    Default

    Ok, mine is M one NVS140M (Mobile product) which is equivalent for 8400GS[M] or so... So it might be that mobile users are affected

  7. #7
    Join Date
    Oct 2007
    Posts
    92

    Default

    Well this should be noted in the news:
    OpenGL version string: 3.2.0 NVIDIA 190.16
    The 3.2.0 spec is not even released yet.

  8. #8
    Join Date
    Jan 2009
    Posts
    206

    Default

    Quote Originally Posted by Kirurgs View Post
    Ok, mine is M one NVS140M (Mobile product) which is equivalent for 8400GS[M] or so... So it might be that mobile users are affected
    Yup, my sister has GeForce 7150M and her laptop oops'es:
    Code:
    Oops: 0010 [#1] PREEMPT SMP 
    last sysfs file: /sys/devices/pci0000:00/0000:00:0d.0/0000:04:00.0/resource
    CPU 1 
    Modules linked in: ipv6 snd_hda_codec_conexant b43 rfkill snd_seq_dummy snd_hda_intel mac80211 snd_seq_oss snd_hda_codec uvcvideo snd_seq_midi_event snd_seq snd_seq_device cfg80211 input_polldev videodev v4l1_compat v4l2_compat_ioctl32 sdhci_pci sdhci joydev snd_pcm_oss snd_mixer_oss snd_hwdep snd_pcm mmc_core ohci1394 ssb snd_timer snd soundcore i2c_nforce2 ohci_hcd ricoh_mmc led_class ieee1394 psmouse sg serio_raw pcmcia pcmcia_core snd_page_alloc k8temp pcspkr ehci_hcd nvidia(P) i2c_core forcedeth video usbcore output wmi thermal evdev fan button battery ac cpufreq_conservative powernow_k8 freq_table processor rtc_cmos rtc_core rtc_lib ext4 mbcache jbd2 crc16 sd_mod sr_mod cdrom ata_generic pata_acpi ahci pata_amd libata scsi_mod
    Pid: 2306, comm: X Tainted: P           2.6.30-ARCH #1 HP Pavilion dv2700 Notebook PC
    RIP: 0010:[<0000000000000000>]  [<(null)>] (null)
    RSP: 0018:ffff88007402fb00  EFLAGS: 00010246
    RAX: 000000000000000b RBX: ffff8800784ee000 RCX: ffff8800740e2e5e
    RDX: ffff880074116000 RSI: 0000000000000110 RDI: ffff8800784ee000
    RBP: ffff8800740e2e58 R08: ffff880001036c00 R09: ffff8800740e2dc8
    R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
    R13: ffff88007af060c0 R14: ffff88007a754000 R15: ffff88007ab6c000
    FS:  00007f4d12b716f0(0000) GS:ffff880001029000(0000) knlGS:0000000000000000
    CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    CR2: 0000000000000000 CR3: 000000007406d000 CR4: 00000000000006e0
    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Process X (pid: 2306, threadinfo ffff88007402e000, task ffff88007a734bc0)
    Stack:
     ffffffffa0582704 ffff8800740e2dd0 ffff88007af060c0 ffff88007af06000
     ffff8800784ee000 000000000000000f ffffffffa05828e7 ffff88007af06000
     ffff8800784ee000 0000000000010000 ffffffffa058f0bc 0000000000000000
    Call Trace:
     [<ffffffffa0582704>] ? _nv021736rm+0x63/0x110 [nvidia]
     [<ffffffffa05828e7>] ? _nv021737rm+0x3f/0x45 [nvidia]
     [<ffffffffa058f0bc>] ? _nv016604rm+0x83/0x92 [nvidia]
     [<ffffffffa028c932>] ? _nv001365rm+0x1ea/0x32c [nvidia]
     [<ffffffffa058f301>] ? _nv016603rm+0x236/0x250 [nvidia]
     [<ffffffffa034e452>] ? _nv016175rm+0x13/0x91 [nvidia]
     [<ffffffffa059e0cd>] ? _nv012267rm+0x2a2/0x3dd [nvidia]
     [<ffffffffa059d8d0>] ? _nv011879rm+0x5e/0x9c [nvidia]
     [<ffffffffa0433535>] ? _nv012102rm+0xd/0x12 [nvidia]
     [<ffffffffa05fe05b>] ? _nv003827rm+0x161/0x255 [nvidia]
     [<ffffffffa05fed9b>] ? _nv003833rm+0x3d7/0x594 [nvidia]
     [<ffffffffa05f9798>] ? rm_init_adapter+0x69/0xbd [nvidia]
     [<ffffffffa06db6a3>] ? nv_kern_open+0x393/0x7c0 [nvidia]
     [<ffffffff802ff5a0>] ? exact_match+0x0/0x40
     [<ffffffff802ffc57>] ? chrdev_open+0x157/0x260
     [<ffffffff802ffb00>] ? chrdev_open+0x0/0x260
     [<ffffffff802f91ac>] ? __dentry_open+0x13c/0x390
     [<ffffffff8030baca>] ? do_filp_open+0x2da/0xa50
     [<ffffffff803168f8>] ? notify_change+0x268/0x3a0
     [<ffffffff80317fca>] ? alloc_fd+0x10a/0x160
     [<ffffffff802f8ee1>] ? do_sys_open+0x71/0x130
     [<ffffffff8020c442>] ? system_call_fastpath+0x16/0x1b
    Code:  Bad RIP value.
    RIP  [<(null)>] (null)
     RSP <ffff88007402fb00>
    CR2: 0000000000000000
    ---[ end trace ef2fdd6e372dfe26 ]---
    Lol check out the rip/eip register, it points to null ~ 0th byte (more like, hey cpu, upon next instruction jump to 0x00 address and linux goes like wtf noob...and crashes), nvidia screwed up somewhere big time.

  9. #9

    Default

    One of the most important features of this driver isn't even mentioned. Pay close attention to the OpenGL version it reports which is 3.2! Also various new OpenGL ARB extensions have been added like GL_ARB_draw_elements_base_vertex, GL_ARB_fragment_coord_conventions, GL_ARB_provoking_vertex and GL_ARB_seamless_cube_map.

    I expect that OpenGL 3.2 will be announced at Siggraph soon and that's why the logs don't mention it. So this is actually a big release!

  10. #10
    Join Date
    Oct 2007
    Location
    Under the bridge
    Posts
    2,129

    Default

    Quote Originally Posted by Thunderbird View Post
    One of the most important features of this driver isn't even mentioned. Pay close attention to the OpenGL version it reports which is 3.2! Also various new OpenGL ARB extensions have been added like GL_ARB_draw_elements_base_vertex, GL_ARB_fragment_coord_conventions, GL_ARB_provoking_vertex and GL_ARB_seamless_cube_map.

    I expect that OpenGL 3.2 will be announced at Siggraph soon and that's why the logs don't mention it. So this is actually a big release!
    Check the registry, gl.spec already contains references to 3.2 modifications.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •