5.3-RELEASE hw.ata.atapi_dma and DRI questions
I've two questions I'm hoping can be answered quickly. After installing 5.3-RELEASE on my Dell Inspiron 8000 I put the following into /boot/loader.conf as per usual (previous) convention: hw.ata.atapi_dma="1" Though the sysctl does get set at boot the dvd drive still attaches as PIO4 instead of WDMA2. I can use atacontrol after boot to get full dma speed out of it but why does this not happen at boot with the sysctl set? The second question has to do with DRI. I upgraded my graphics card to a Radeon Mobility 7500 with 64 MB of RAM a while back (it's an M7) and it has been working quite well. This is the first time I've attempted to run Xorg on any of my installs (I have two others on the same disk) and I'm seeing some rather strange behavior. Namely, /var/log/Xorg.0.log claims that DRI is enabled but glxinfo and the speed of glxgears testify to indirect rendering only. The section from the log is as follows: (II) RADEON(0): Direct rendering enabled I'm using the same config file I've been using for 3 revisions of 5.x and 4.x under XFree but with the BusID line removed and the file renamed to xorg.conf (just to be consistent). Any ideas? Has anyone else seen this? I'm just using the Xorg packages from the install disc with the GENERIC kernel that shipped with the release. Permissions are correct on the dev entry, the console message looks normal, and there are no errors loading the kernel module but I can't use acceleration at all! Sean ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
APM and DRI lockups when suspending
Duane, there have always been issues with this aspect of APM. I have found it sufficient to run two X servers to handle the issue. Most of my software runs in an X session without DRI enabled and then when I want to run accelerated 3D I just start up another X session with DRI enabled. For example, this can be done by running the following command from an xterm in the first (normal, non-DRI session): startx -- :1 -xf86config XF86Config.dri & I've got DRI enabled in the XF86Config.dri file (which just resides under /etc/X11 along side the default config file) and this command starts up an X session on ttyv9 (alt-ctrl-F10). Be sure that you use a different window manager in your .xinitrc if you use either Gnome or KDE!! When I want to suspend, I just shut down the accelerated X session and then when I resume I can start it back up again without ill effects. I hope this helps! Sean > Does anybody know if there is a workaround for the problem with DRI > and > APM within X? > > If I load the DRI module in my XF86Config file, and attempt to > suspend > my laptop, the system freezes on resume, then reboots. > > If I comment out the line "Load dri" out of the Module section in > /etc/X11/XF86Config, all is well. > > But now I don't have direct rendering capability, correct? I don't > think > I have any apps yet that need direct rendering, so it probably isn't > a > huge deal (yet), but I would like to have it enable if possible. > > Does anybody know of a solution or simple workaround for this > problem? > > Thanks, > Duane Winner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: openoffice-1.1.1RC install without jdk
As an additional data point, I noticed that configure is looking for javac so I just add /usr/local/jdk1.4.2/bin/ to root's default PATH environment variable. Everything ran just fine after that. This is under 5.2.1-RELEASE. Sean >> The port is under construction at the moment. I told is explicitly to >> use my installed java: >> make CONFIGURE_ARGS+="--with-jdk-home=/usr/local/jdk1.4.2" >> which solves that problem, but I haven't gotten it all the way built >> yet, so I can't be sure that's all you need to know. >> >> This particular problem seems to be caused by the makefile using >> JDKDIR and JAVAVM before defining them. It looks like the definitions >> should be able to just get moved up, so I'm trying that, but it hasn't >> gotten far yet. > >No, that doesn't do it. I can't remember why I thought it would, >either; it doesn't actually affect the configure script. > >I won't get more time to work on it for a few days, and by then >there may be more changes to the port. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
VMWare licensing file problem.
Version 2 of VmWare is no longer sold so the evaluation license you got is most likely for version 4 (which does not run on FreeBSD yet). The confusion results from the fact that with version 2 you got a license file but starting with version 3 (which DOES run under FreeBSD) you are only supplied with a "key" which is to be entered into a form in the VmWare gui once it has been started (there is a register menu or some such). I'm affraid you are out of luck with vmware2 unless you can manage to locate a license file somewhere. It is still possible to find boxed copies of version 3 online (check ebay and such) and that version will run on either 4-STABLE or 5.1 and higher. I'm currently running it under a patched 4.9-RELEASE and also under 5.2-RELEASE. Sean -- > Hi everybody. > I have a problem with the vmware licensing file > after installing the vmware2 port. > I've received an e-mail with the evaluation key, copied it into > /home/user/.vmware, named it license2.0 but it don't seem to work. > The message I get is that there is no valid license for this version of > VMware workstation. > After checking at vmware's website and reading troubleshooting > instructions, it seems like there should have been an atachment with a > licencefile to the mail I received, but there was none. > Just a 30 days evolution license-key. > Anybody have any clues ? > > TIA > Regards > Geir Svalland ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Unprobed PCI bus on VXPro II chipset
Thanks very much for the suggestion! Unfortunately it didn't make any difference at all to the probe. Any other suggestions? Anyone else? Sean -Original Message- From: fbsd_user <[EMAIL PROTECTED]> Sent: Dec 24, 2003 3:14 PM To: Sean Welch <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Subject: RE: Unprobed PCI bus on VXPro II chipset You did not have to do all that hacking, there is an simple fix for old bio's and PCI cards. Add device puc to your kernel source and recompile. Your next boot review your boot log and you should see all the PCI devices found except sound cards. You have to add device pcm to your kernel and recompile to find PCI sound cards or built on the motherboard sound. I know this works for the 4.x releases including 4.9. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sean Welch Sent: Wednesday, December 24, 2003 5:55 PM To: [EMAIL PROTECTED] Subject: Unprobed PCI bus on VXPro II chipset As I'm not quite sure where I should be asking for help with this I figured I'd try shooting the info over to freebsd-hackers (as it seemed the closest match) and to freebsd-questions (as there seems to be a requirement to join the list for hackers mail). I've got an oldish machine (EDO RAM and such) running a VXPro II chipset. I have successfully configured FreeBSD from 2.2.8 up to 5-CURRENT to run on this thing but I've never managed to get it to probe and attach anything on the PCI bus. Here's what I've found and what I've tried. I believe the motherboard was sold as PCChips kit. Looking up the stats I find that it was a rebrand of Hint Co. hardware. The PCI IDs are actually listed in /usr/share/misc/pci_vendors and look like this: 3388Hint Corp. 0020HB6 UNIVERSAL PCI-PCI BRIDGE 0021HB1-SE33 PCI-to-PCI Bridge 8011VXPro II Chipset CPU to PCI Bridge 8012VXPro II Chipset PCI to ISA Bridge 8013VXPro II Chipset EIDE Controller I found a commit notice online to the linux kernel that contained these same IDs so it looks like the complete string should be "33880020", "33880021", etc. I also managed to find this message from *long* ago: http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm= Pine.BSF.3.96.990120135600.28221A-10_gate1.ilhadamagia.com.br%40 ns.sol.net&rnum=5&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3 DUTF-8%26q%3Dfreebsd%2Bvxpro%26btnG%3DGoogle%2BSearch I'm currently running 4.9-RELEASE. The uname -a output is: FreeBSD 4.9-RELEASE FreeBSD 4.9-RELEASE #5: Tue Oct 14 11:51:28 CDT 2003 root@:/usr/src/sys/compile/WARPPHYS i386 Poking around I discovered that pcibus.c no longer contains the code referenced in the above message (but that didn't stop me). I found it instead in pci_cfgreg.c and tried adding the explicit set of oldval1 to zero but no joy. I ended up adding the PCI IDs to both /usr/src/sys/i386/isa/pcibus.c and also /usr/src/sys/pci/pcisupport.c in the effort to get the chipset recognized. No go. When I boot verbose this is all I can get about the PCI bus: pci_open(1):mode 1 addr port (0x0cf8) is 0xff00 pci_open(1a): mode1res=0x (0x8000) pci_open(1b): mode1res=0x7020 (0xff01) pci_open(2):mode 2 enable port (0x0cf8) is 0xff Infuriatingly, the BIOS sees everything on the bus and labels the devices with reasonable categories. Likewise, scanpci (comes with XFree86) identifies the chipsets and the devices without any trouble at all -- that at least explains why I've never had any trouble using the PCI video card under X. The output of scanpci identifies the last three chipsets from that snipet I put above (from pci_vendors) with the last being labeled as IDE rather than EIDE (which is correct). Based on this digging around I'm convinced that there must be some ugly hack that is posible to get FreeBSD to probe and attach the bus and devices on it. I've only got this desktop and while I've been able to live without the PCI USB card, I need to test out a PCI WinTV card. The whole machine is old enough that isn't feasible to just try swapping out the motherboard (the case isn't even ATX compatible) and I've not got the money to just buy something else. Would anyone be willing to help me get this sorted out? I'm out of my depth here but to my inexperienced eyes this doesn't look to be an insurmountable issue. Sean ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Unprobed PCI bus on VXPro II chipset
As I'm not quite sure where I should be asking for help with this I figured I'd try shooting the info over to freebsd-hackers (as it seemed the closest match) and to freebsd-questions (as there seems to be a requirement to join the list for hackers mail). I've got an oldish machine (EDO RAM and such) running a VXPro II chipset. I have successfully configured FreeBSD from 2.2.8 up to 5-CURRENT to run on this thing but I've never managed to get it to probe and attach anything on the PCI bus. Here's what I've found and what I've tried. I believe the motherboard was sold as PCChips kit. Looking up the stats I find that it was a rebrand of Hint Co. hardware. The PCI IDs are actually listed in /usr/share/misc/pci_vendors and look like this: 3388Hint Corp. 0020HB6 UNIVERSAL PCI-PCI BRIDGE 0021HB1-SE33 PCI-to-PCI Bridge 8011VXPro II Chipset CPU to PCI Bridge 8012VXPro II Chipset PCI to ISA Bridge 8013VXPro II Chipset EIDE Controller I found a commit notice online to the linux kernel that contained these same IDs so it looks like the complete string should be "33880020", "33880021", etc. I also managed to find this message from *long* ago: http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&threadm=Pine.BSF.3.96.990120135600.28221A-10_gate1.ilhadamagia.com.br%40ns.sol.net&rnum=5&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26q%3Dfreebsd%2Bvxpro%26btnG%3DGoogle%2BSearch I'm currently running 4.9-RELEASE. The uname -a output is: FreeBSD 4.9-RELEASE FreeBSD 4.9-RELEASE #5: Tue Oct 14 11:51:28 CDT 2003 root@:/usr/src/sys/compile/WARPPHYS i386 Poking around I discovered that pcibus.c no longer contains the code referenced in the above message (but that didn't stop me). I found it instead in pci_cfgreg.c and tried adding the explicit set of oldval1 to zero but no joy. I ended up adding the PCI IDs to both /usr/src/sys/i386/isa/pcibus.c and also /usr/src/sys/pci/pcisupport.c in the effort to get the chipset recognized. No go. When I boot verbose this is all I can get about the PCI bus: pci_open(1):mode 1 addr port (0x0cf8) is 0xff00 pci_open(1a): mode1res=0x (0x8000) pci_open(1b): mode1res=0x7020 (0xff01) pci_open(2):mode 2 enable port (0x0cf8) is 0xff Infuriatingly, the BIOS sees everything on the bus and labels the devices with reasonable categories. Likewise, scanpci (comes with XFree86) identifies the chipsets and the devices without any trouble at all -- that at least explains why I've never had any trouble using the PCI video card under X. The output of scanpci identifies the last three chipsets from that snipet I put above (from pci_vendors) with the last being labeled as IDE rather than EIDE (which is correct). Based on this digging around I'm convinced that there must be some ugly hack that is posible to get FreeBSD to probe and attach the bus and devices on it. I've only got this desktop and while I've been able to live without the PCI USB card, I need to test out a PCI WinTV card. The whole machine is old enough that isn't feasible to just try swapping out the motherboard (the case isn't even ATX compatible) and I've not got the money to just buy something else. Would anyone be willing to help me get this sorted out? I'm out of my depth here but to my inexperienced eyes this doesn't look to be an insurmountable issue. Sean ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
