DaemonForums  

Go Back   DaemonForums > FreeBSD > FreeBSD Installation and Upgrading

FreeBSD Installation and Upgrading Installing and upgrading FreeBSD.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 12th May 2008
bjstick bjstick is offline
New User
 
Join Date: May 2008
Posts: 4
Default Strange FreeBSD Issues (USB/Nvidia Drivers)

I have used FreeBSD in the past with no problems. I tried it out around 4.2, and used it as a primary desktop OS after Nvidia released their first GLX drivers. I tried revisiting it recently, and it is giving me nothing but trouble. See below:

1) When booting, if there is a USB hard drive attached I get an instant kernel panic right after it is detected.

2) I can unplug my USB drive and the system will boot. However, during boot my other USB devices (mouse/keyboard) drop connection and I have to unplug them and plug them back in to have them reactivate.

3) NVidia driver does not work for me. I was able to boot into X using "nv" driver, but when I compiled nvidia-driver from ports and ran nvidia-xconfig, I get an error about "/dev/nvidiactl" not being found and X will not boot.

This was with 7.0-RELEASE. The same problems persist with PC-BSD 1.5.1 which is based on 6.3-RELEASE. In fact, when I select the "nvidia" driver during the initial boot, my system hard locks when testing the screen. I have no problems with Linux on this computer, and even Solaris works perfectly with the NVidia drivers and all attached USB devices. Also, I am able to run "special" versions of OS X Leopard with no problems on this machine. Only FreeBSD gives me these problems. OpenBSD boots up normally.

My system specs are:

Gigabyte GA-EX38-DS4 Motherboard
Intel E6850 Core2Duo
XFX NVidia 8800 320MB GTS (G80)
4GB GeiL PC6400 DDR2
150GB WD Raptor

AHCI/SATA Native mode are enabled in BIOS.

Anybody have any ideas?
Reply With Quote
  #2   (View Single Post)  
Old 12th May 2008
J65nko J65nko is offline
Administrator
 
Join Date: May 2008
Location: Budel - the Netherlands
Posts: 4,125
Default

Maybe you can try the suggestions in http://lists.freebsd.org/pipermail/f...il/041893.html
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump
Reply With Quote
  #3   (View Single Post)  
Old 12th May 2008
DrJ DrJ is offline
ISO Quartermaster
 
Join Date: Apr 2008
Location: Gold Country, CA
Posts: 507
Default

Your nvidia issues result from the amount of memory you have. You either have to turn off memory relocation in the BIOS (which Gigabyte usually does not have) or remove a GB of memory.

I too found this out the hard way.

I opened a thread on this topic long ago on nvnews.net, so nVidia knows about it. It has not been fixed.
Reply With Quote
  #4   (View Single Post)  
Old 12th May 2008
bjstick bjstick is offline
New User
 
Join Date: May 2008
Posts: 4
Default

Quote:
Originally Posted by J65nko View Post
Maybe you can try the suggestions in http://lists.freebsd.org/pipermail/f...il/041893.html
I removed atkbd from the kernel when I was compiling it. I'll poke around in BIOS and see if there are any settings I can play around with.
Reply With Quote
  #5   (View Single Post)  
Old 12th May 2008
bjstick bjstick is offline
New User
 
Join Date: May 2008
Posts: 4
Default

Quote:
Originally Posted by DrJ View Post
Your nvidia issues result from the amount of memory you have. You either have to turn off memory relocation in the BIOS (which Gigabyte usually does not have) or remove a GB of memory.

I too found this out the hard way.

I opened a thread on this topic long ago on nvnews.net, so nVidia knows about it. It has not been fixed.
Hmm, I didn't even think of that. I do know that when I am initially booting up I get a "500M over 4GB of RAM ignored" or something similar. I'll have to try that. Thanks for the tip.
Reply With Quote
  #6   (View Single Post)  
Old 12th May 2008
DrJ DrJ is offline
ISO Quartermaster
 
Join Date: Apr 2008
Location: Gold Country, CA
Posts: 507
Default

Just remember that memory on these boards is dual channel. It is fine for debugging purposes, but once you prove to yourself that it works, you will have to consider what you do about reaching 3 - 3.5 GB with standard modules.

Or you might conclude that "nv" is good enough -- that's usually the case unless you need 3D for something like gaming, or you use dual heads.
Reply With Quote
  #7   (View Single Post)  
Old 13th May 2008
tuck's Avatar
tuck tuck is offline
Shell Scout
 
Join Date: May 2008
Posts: 99
Default

Quote:
Originally Posted by bjstick View Post
my system hard locks when testing the screen
After #startx ?
My System did the same thing, removing RAM helped.
Reply With Quote
  #8   (View Single Post)  
Old 13th May 2008
bjstick bjstick is offline
New User
 
Join Date: May 2008
Posts: 4
Default

Quote:
Originally Posted by tuck View Post
After #startx ?
My System did the same thing, removing RAM helped.
In FreeBSD 7.0 I get the "/dev/nvidiactl" not being found error. The module is loaded and I have compat_5x enabled in rc.conf.

PC-BSD is the one that hard locks after startx.
Reply With Quote
  #9   (View Single Post)  
Old 10th April 2017
kusana kusana is offline
New User
 
Join Date: Apr 2017
Posts: 1
Default

Quote:
Originally Posted by DrJ View Post
Just remember that memory on these boards is dual channel. It is fine for debugging purposes, but once you prove to yourself that it works, you will have to consider what you do about reaching 3 - 3.5 GB with standard modules.

Or you might conclude that "nv" is good enough -- that's usually the case unless you need 3D for something like gaming, or you use dual heads.
Hello DrJ,
thank god that i saw your post! i have been trying to nail this issue for months... it had occurred to me that only freebsd has this strange memory size limitation, not windows or linux.
after reading your post, i couldn't find anything talked about on this topic through google. i would like to learn more why memory relocation is a problem in this scenario, and why memory size <3GB would work but not more. could you give me some references to read?
thanks a lot again
Reply With Quote
Old 10th April 2017
Beastie Beastie is offline
Daemonology student
 
Join Date: Jan 2009
Location: /dev/earth0
Posts: 335
Default

I've never used Nvidia products, but perhaps the drivers that were available for FreeBSD at that time were 32-bit only and were subjected to the 3GB barrier.

Note that many things have changed in the past 9 years since this thread was started.
__________________
May the source be with you!
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Strange issues with 7.2 DNAeon FreeBSD General 5 26th September 2009 11:19 AM
HOWTO: Install and configure NVIDIA drivers on FreeBSD tangram Guides 2 29th March 2009 08:23 PM
strange load problem on freebsd 7.0 amd64 skynet_tech FreeBSD General 3 11th September 2008 09:49 PM
NFS and FreeBSD 6.2r strange problem .. bsduser FreeBSD Installation and Upgrading 3 11th July 2008 11:48 AM
PAE and official Nvidia drivers rubenerd FreeBSD General 2 20th May 2008 10:53 PM


All times are GMT. The time now is 08:13 AM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick