Re: nvidia.ko freezes system in -current
Andrew Atrens wrote:
The nvidia probe code gets invoked for every pci device discovered on
the bus. The can't-attach-memory-resource thing essentially means that
the driver is trying to attach to a device that isn't a graphics card.
Ok. That seems to be the cause for the death of fsck on boot, too.
Because I use the x11/nvidia-driver port I created a patch. It is
lacking a lot of IDs, because it is the reverse approach to Andrew's.
Hendrik
--- src/nvidia_pci.c.orig Wed May 28 18:51:52 2003
+++ src/nvidia_pci.cSun Aug 31 17:34:19 2003
@@ -29,17 +29,26 @@
vendor = pci_get_vendor(dev);
device = pci_get_device(dev);
-
+
if (vendor != NVIDIA_VENDORID || device 0x0020)
return ENXIO;
-if (rm_get_device_name(device, NV_DEVICE_NAME_LENGTH, name)
-!= RM_OK) {
-strcpy(name, Unknown);
-}
+switch ( device ) {
+case 0x0281:
+if (rm_get_device_name(device, NV_DEVICE_NAME_LENGTH, name)
+!= RM_OK) {
+strcpy(name, Unknown);
+}
-device_set_desc_copy(dev, name);
-return 0;
+device_set_desc_copy(dev, name);
+return 0;
+break;
+default:
+if (pci_get_class(dev) == PCIC_DISPLAY)
+device_printf(dev, Unknown ID\nIf you are sure your device works
with this driver\nplease post the ID);
+return ENXIO;
+break;
+}
}
int nvidia_pci_attach(device_t dev)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia.ko freezes system in -current
Does somebody use the nvidia driver together with a nforce2 chipset? The driver won't enable the agp port: nvidia0: Unknown at device 0.1 on pci0 nvidia0: Unable to enable PCI busmastering. device_probe_and_attach: nvidia0 attach returned 6 Any ideas? Hendrik -- Ahhh there's only 10 types of people in the world, those who understand binary and those who don't... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia.ko freezes system in -current
Hendrik Hasenbein [EMAIL PROTECTED] wrote: Does somebody use the nvidia driver together with a nforce2 chipset? The driver won't enable the agp port: nvidia0: Unknown at device 0.1 on pci0 nvidia0: Unable to enable PCI busmastering. device_probe_and_attach: nvidia0 attach returned 6 Any ideas? Hendrik Yes I have an nforce2 motherboard and use it. I get the same messages but mine does detect it and work fine after all the messages as you can see below. These messages never used to be printed on the older nvidia port but since it was updated I see this every time I kldload it. Though as it eventually attaches and works I have never really cared much about it. Aug 25 09:54:01 neo kernel: nvidia0: Unknown at device 0.1 on pci0 Aug 25 09:54:01 neo kernel: nvidia0: Unable to enable PCI busmastering. Aug 25 09:54:01 neo kernel: device_probe_and_attach: nvidia0 attach returned 6 Aug 25 09:54:01 neo kernel: nvidia0: Unknown at device 0.2 on pci0 Aug 25 09:54:01 neo kernel: nvidia0: Unable to enable PCI busmastering. Aug 25 09:54:01 neo kernel: device_probe_and_attach: nvidia0 attach returned 6 Aug 25 09:54:01 neo kernel: nvidia0: Unknown at device 0.3 on pci0 Aug 25 09:54:01 neo kernel: nvidia0: Unable to enable PCI busmastering. Aug 25 09:54:01 neo kernel: device_probe_and_attach: nvidia0 attach returned 6 Aug 25 09:54:01 neo kernel: nvidia0: Unknown port 0x2480-0x249f,0x24b0-0x24bf,0x24a0-0x24af irq 11 at device 1.1 on pci0 Aug 25 09:54:01 neo kernel: nvidia0: Unable to enable PCI busmastering. Aug 25 09:54:01 neo kernel: device_probe_and_attach: nvidia0 attach returned 6 Aug 25 09:54:01 neo kernel: nvidia0: GeForce4 MX 420 mem 0xfc20-0xfc27,0xf800-0xfbff,0xfd00-0xfdff irq 5 at device 0.0 on pci1 -- email: [EMAIL PROTECTED] - web: http://xtaz.co.uk/ Hardware, n.: The parts of a computer system that can be kicked. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia.ko freezes system in -current
Hendrik Hasenbein wrote:
Does somebody use the nvidia driver together with a nforce2 chipset?
The driver won't enable the agp port:
nvidia0: Unknown at device 0.1 on pci0
nvidia0: Unable to enable PCI busmastering.
device_probe_and_attach: nvidia0 attach returned 6
These messages are actually bogus.
The problem is that the driver tries to attach any devices whose
vendorid is nVIDIA.
In the port, there's a file called nvidia_pci.c. I've modified the
probe to ignore the mb devices -
Try this version -
int nvidia_pci_probe(device_t dev)
{
U016 vendor;
U016 device;
char name[NV_DEVICE_NAME_LENGTH];
vendor = pci_get_vendor(dev);
device = pci_get_device(dev);
if (vendor != NVIDIA_VENDORID || device 0x0020)
return ENXIO;
switch ( device ) {
/* exclude these nForce and nForce2 devices from the probe */
case 0x01e0: /* nForce2 AGP Controller */
case 0x01e8: /* nForce2 AGP Host to PCI Bridge */
case 0x01eb: /* nForce2 Memory Controller 1 */
case 0x01ee: /* nForce2 Memory Controller 4 */
case 0x01ed: /* nForce2 Memory Controller 3 */
case 0x01ec: /* nForce2 Memory Controller 2 */
case 0x01ef: /* nForce2 Memory Controller 5 */
case 0x0060: /* nForce MCP2 ISA Bridge */
case 0x0064: /* nForce MCP-T? SMBus Controller */
case 0x0067: /* nForce MCP2 OpenHCI USB Controller */
case 0x006b: /* nForce MCP-T? Audio Processing Unit (Dolby
Digital) */
case 0x006a: /* nForce MCP2 Audio Codec Interface */
case 0x006c: /* nForce PCI to PCI Bridge */
case 0x0065: /* nForce MCP2 EIDE Controller */
case 0x006d: /* Nvidia (unknown) PCI to PCI Bridge */
case 0x006e: /* nForce MCP2 OHCI Compliant IEEE 1394
Controller */
return ENXIO;
break;
default:
break;
}
if (rm_get_device_name(device, NV_DEVICE_NAME_LENGTH, name)
!= RM_OK) {
strcpy(name, Unknown);
}
device_set_desc_copy(dev, name);
return 0;
}
Note that I don't have the usb2.0 controller (ehci) enabled, because
it's not supported yet in -STABLE. Because it's not support I've
disabled it in the bios and didn't add the device id to the switch
statement for it (actually I don't know what it is :) )... If you have
USB2.0 support enabled in your bios you can do a 'pciconf -l -v' to
extract the device id, and then add that device to the 'ignore list' aka
switch statement :)
Here's an example snippet of pciconf output -
[EMAIL PROTECTED]:9:0: class=0x01018a card=0x0c111043 chip=0x006510de
rev=0xa2 hdr=0x00
^^
0x10de is the vendorid, and the top part 0x0065 is your device id.
The combination that works for me (in -STABLE) is nvidia gart and no
hacks. I spent some time trying to get Matt Dodd's os agp to work,
again in -STABLE, and while it does probe and attach the agp correctly -
and from what I could tell seems to follow the linux code very closely -
I can't get the nvidia driver to work with it.
Good luck,
Andrew.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia.ko freezes system in -current
Andrew Atrens wrote: The combination that works for me (in -STABLE) is nvidia gart and no hacks. I spent some time trying to get Matt Dodd's os agp to work, again in -STABLE, and while it does probe and attach the agp correctly - and from what I could tell seems to follow the linux code very closely - I can't get the nvidia driver to work with it. Good luck, Andrew. Thx. Ok, I thought that was the problem behind the attach problem. If it is bogus why can't the driver attach to the memory resource? '/boot/loader.conf' already contains 'hw.pci.allow_unsupported_io_range=1' In which order do you load the modules? Hendrik Board: Asus a7n8x-deluxe / Epox 8rda GraCa: MSI Geforce 4 TI4200 -- Ahhh there's only 10 types of people in the world, those who understand binary and those who don't... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia.ko freezes system in -current
Hendrik Hasenbein wrote: Andrew Atrens wrote: The combination that works for me (in -STABLE) is nvidia gart and no hacks. I spent some time trying to get Matt Dodd's os agp to work, again in -STABLE, and while it does probe and attach the agp correctly - and from what I could tell seems to follow the linux code very closely - I can't get the nvidia driver to work with it. Good luck, Andrew. Thx. Ok, I thought that was the problem behind the attach problem. If it is bogus why can't the driver attach to the memory resource? The nvidia probe code gets invoked for every pci device discovered on the bus. The can't-attach-memory-resource thing essentially means that the driver is trying to attach to a device that isn't a graphics card. '/boot/loader.conf' already contains 'hw.pci.allow_unsupported_io_range=1' I don't run -current, so I'm not exactly sure what this does :( ... In which order do you load the modules? I just load - kernel linux.ko nvidia.ko and that's it. It's important to note that I do not have 'device agp' in my kernel. Andrew. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
nvidia.ko freezes system in -current
I cvsuped world and kernel today, built world, installed world, did a reinstall (with compilation) of the nvidia module 1.0-4365 and the kernel module loads fine but when I startx I get a few screen flashes and the reboot. I have agp_load=YES in loader.conf (as I had before). I did not choose WITH_FREBSD_AGP as the port makefile gives as option. Need urgent help since I did this (boo boo) on a production server Well the server runs (httpd) but I have no X at the moment and I cannot afford frequent compiles and reboots at the moment. -- Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia.ko freezes system in -current
On Thu, 2003-08-28 at 15:40, Christoph Kukulies wrote: I cvsuped world and kernel today, built world, installed world, did a reinstall (with compilation) of the nvidia module 1.0-4365 and the kernel module loads fine but when I startx I get a few screen flashes and the reboot. I have agp_load=YES in loader.conf (as I had before). I did not choose WITH_FREBSD_AGP as the port makefile gives as option. I had this effect earlier. XFree was trying to change to graphics mode a few times and then fell back to text-mode. I could only see some weird characters on my display. Then the PC was in an unusable state, but if I holded down Ctrl+Alt+Del long enough it rebooted, so it was not frozen. I wanted to confirm your problem today, because I recognized the symptoms, but I failed :) I have: FreeBSD xxx.local 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Wed Jul 30 20:38:47 CEST XFree-ports: XFree86-4.3.0,1 XFree86-FontServer-4.3.0_1 XFree86-Server-4.3.0_8 XFree86-clients-4.3.0_2 XFree86-documents-4.3.0 XFree86-font100dpi-4.3.0 XFree86-font75dpi-4.3.0 XFree86-fontCyrillic-4.3.0 XFree86-fontDefaultBitmaps-4.3.0 XFree86-fontEncodings-4.3.0 XFree86-fontScalable-4.3.0 XFree86-libraries-4.3.0_5 nvidia-driver-1.0.4365 was compiled today with: make install WITH_FREEBSD_AGP=yes My /boot/loader.conf is: agp_load=YES nvidia_load=YES linux_load=YES linprocfs_load=YES It works again! :) Perhaps I could help. Martin PS.: Don't set option RenderAccel in the device section it has weird effects on rendering smaller images. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia.ko freezes system in -current
On Thu, 28 Aug 2003, Christoph Kukulies wrote: I cvsuped world and kernel today, built world, installed world, did a reinstall (with compilation) of the nvidia module 1.0-4365 and the kernel module loads fine but when I startx I get a few screen flashes and the reboot. I have agp_load=YES in loader.conf (as I had before). I did not choose WITH_FREBSD_AGP as the port makefile gives as option. Need urgent help since I did this (boo boo) on a production server Well the server runs (httpd) but I have no X at the moment and I cannot afford frequent compiles and reboots at the moment. You should try either: A) comment out agp_load=YES compile nvidia-driver without WITH_FREEBSD_AGP or B) leave agp_loadYES compile nvidia-driver with WITH_FREEBSD_AGP I used to run WITH_FREEBSD_AGP / agp_load=YES (because it was unstable otherwise), but recently cvsuped to -CURRENT, and discovered that the opposite was now more stable (WITH_FREEBSD_AGP/agp_load=YES now causes my computer to lockup regularly when in X). I suggest you try the opposite setting and see if that helps. Also keep WITH_FREEBSD_AGP and agp_load in 'sync'. -- David Taylor [EMAIL PROTECTED] The future just ain't what it used to be ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
