Opened 16 years ago
Closed 14 years ago
#3471 closed bug (fixed)
GeForce4 MX 440 problem
Reported by: | Giuseppe | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Drivers/Graphics/nVidia | Version: | R1/pre-alpha1 |
Keywords: | Cc: | judd@… | |
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
I have a GeForce4 MX 440 it start with the nvidia driver in Haiku but after booting, a few seconds and the cursor creates a permanent trail, the cursor is drawn each time in a new position but the former remains.
This graphic card works fine with the Haiku_Nvidia_V0.80 by Rudolf Cornelissen here: http://www.bebits.com/app/3636 so every time i install Haiku first I boot in vesa and install this driver.
this is the syslog:
KERN: PCI: [dom 0, bus 1] bus 1, device 0, function 0: vendor 10de, device 0171, revision a3 KERN: PCI: class_base 03, class_function 00, class_api 00 KERN: PCI: vendor 10de: nVidia Corporation KERN: PCI: device 0171: NV17 [GeForce4 MX 440] KERN: PCI: info: Display controller (VGA compatible controller, VGA controller) KERN: PCI: line_size 00, latency 20, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00020000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 02d7, subsystem_vendor_id 1043 KERN: PCI: interrupt_line 0a, interrupt_pin 01, min_grant 05, max_latency 01 KERN: PCI: base reg 0: host fb000000, pci fb000000, size 01000000, flags 00 KERN: PCI: base reg 1: host e8000000, pci e8000000, size 08000000, flags 08 KERN: PCI: base reg 2: host f7f80000, pci f7f80000, size 00080000, flags 08 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: PM, AGP
Attachments (1)
Change History (4)
by , 16 years ago
Attachment: | nvidia4mx_driver_bug.jpg added |
---|
comment:1 by , 16 years ago
Cc: | added |
---|
comment:3 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I'm running the same card here and don't have this problem.