Originally Posted by tuctboh
uname -a :
FreeBSD himinbjorg.tucs-beachin-obx-house.com 5.5-STABLE FreeBSD 5.5-STABLE #9: Tue Jan 23 23:44:47 EST 2007 firstname.lastname@example.org
pci1: <ACPI PCI bus> on pcib1
nvidia0: <GeForce4 440 Go> mem 0xdff80000-0xdfffffff,0xe0000000-0xe7ffffff,0xfc0
00000-0xfcffffff irq 11 at device 0.0 on pci1
NVRM: detected agp.ko, aborting NVIDIA AGP setup!
Ok. You've got a custom kernel. The NVidia driver is detecting the freebsd agp driver. I removed device agp
from my kernel config and used the one build into the NVidia driver (Option NvAGP "1"
in xorg.conf). You may want to try that too. IIRC it was recommended in the README.
Id Refs Address Size Name
1 33 0xc0400000 5cee14 kernel
2 1 0xc09cf000 587c vesa.ko
3 4 0xc09d5000 1b36c linux.ko
4 1 0xc09f1000 3704 umodem.ko
5 1 0xc09f5000 4deeb4 nvidia.ko
6 1 0xc0ed4000 86c0 ng_ubt.ko
7 6 0xc0edd000 dcac netgraph.ko
8 1 0xc0eeb000 40ac uplcom.ko
9 1 0xc0ef0000 8ba0 aio.ko
10 1 0xc0ef9000 580b0 acpi.ko
11 1 0xc2c8b000 6000 linprocfs.ko
12 4 0xc2db2000 2000 ng_bluetooth.ko
13 1 0xc2dbe000 d000 ng_hci.ko
14 1 0xc2dcb000 f000 ng_l2cap.ko
15 1 0xc2dda000 18000 ng_btsocket.ko
16 1 0xc2df3000 4000 ng_socket.ko
117 1 0xc2e0e000 2000 snake_saver.ko
18 1 0xc2ea3000 4000 if_tap.ko
19 1 0xc2eb6000 2000 rtc.ko
Try removing vesa_load=YES from /boot/loader.conf, that would probably mean removing the snake_saver too. The regular console (with the nvidia driver) can only run kind of plain i.e. no vidcontrol modes, not even a decent text one. Sad but true. Doesn't really matter if most of your time is spend in X anyway
Shows everything normal... Attached for your reading enjoyment.
Yup. Looks fine actually. It detects modes it can use.. One thing I forgot to ask cause I hadn't really picked up on the fact it's a notebook
What resolution is the LCD itself? Can it do 1600x1200? Because that's the mode it selected.
Is there an external monitor connected? Is that possible on that model?
If you get a black screen try that Fn+F3(?) to make it switch from the internal to external screen and vice versa.
So freaking many after upgrading from 6.8 to 7.2 it isn't funny! Also attached for your amusement.
Aye.. Ports count was raised dramatically indeed. 7.2 still installed the old school monolithic way, everything but the kitchen sink. They've made some big improvements with the 7.3 port install. You're now able to select the parts you actually need and skip the rest.
Driver from ports: Yup
portupgrade: Don't leave home w/o it.
Cool. Agree on portupgrade I do
Monitor section : Just as nvidia-xconfig made it :
Monitor section from my "nv" running config :
VendorName "Monitor Vendor"
ModelName "Monitor Model"
# HorizSync 31.5 - 64.3
# VertRefresh 50.0 - 90.0
Don't bother with xconfig
Create a nice clean xorg that runs on the nv driver. Only manually change the driver from nv to nvidia. If it works without the HorizSync/VertRefresh lines you don't need 'm with the nvidia driver either. No need to anyway as the display (lcd) will tell the card (and driver) what it's able to handle.
As it is a laptop you may need to play a little with these options to get it to turn on the correct display:
Option "ConnectedMonitor" "string"
Allows you to override what the NVIDIA kernel module detects is connected to your graphics card. This may be useful, for example, if you use a KVM (keyboard, video, mouse) switch and you are switched away when X is started. In such a situation, the NVIDIA kernel module cannot detect what display devices are connected, and the NVIDIA X driver assumes you have a single CRT.
Valid values for this option are "CRT" (cathode ray tube), "DFP" (digital flat panel), or "TV" (television); if using TwinView, this option may be a comma-separated list of display devices; e.g.: "CRT, CRT" or "CRT, DFP".
It is generally recommended to not use this option, but instead use the "UseDisplayDevice" option.
NOTE: anything attached to a 15 pin VGA connector is regarded by the driver as a CRT. "DFP" should only be used to refer to digital flat panels connected via a DVI port.
Default: string is NULL (the NVIDIA driver will detect the connected display devices).
Option "UseDisplayDevice" "string"
When assigning display devices to X screens, the NVIDIA X driver by default assigns display devices in the order they are found (looking first at CRTs, then at DFPs, and finally at TVs). This option can be used to override this assignment. For example, if both a CRT and a DFP are connected, you could specify:
Option "UseDisplayDevice" "DFP"
to make the X screen use the DFP, even though it would have used a CRT by default.
Note the subtle difference between this option and the "ConnectedMonitor" option: the "ConnectedMonitor" option overrides what display devices are actually detected, while the "UseDisplayDevice" option controls which of the detected display devices will be used on this X screen.
Additionally, the special value "none" can be specified for the "UseDisplayDevice" option. When this value is given, any programming of the display hardware is disabled. The NVIDIA driver will not perform any mode validation or modesetting for this X screen. This is intended for use in conjunction with CUDA or in remote graphics solutions such as VNC or Hewlett Packard's Remote Graphics Software (RGS). This functionality is only available on Quadro and Tesla GPUs.
Note the following restrictions for setting the "UseDisplayDevice" to "none":
* OpenGL SyncToVBlank will have no effect.
* You must also explicitly specify the Virtual screen size for your X screen (see the xorg.conf(5x) or XF86Config(5x) manpages for the 'Virtual' option, or the nvidia-xconfig(1) manpage for the '--virtual' commandline option); the Virtual screen size must be at least 304x200, and the width must be a multiple of 8.
* None of Stereo, Overlay, CIOverlay, or SLI are allowed when "UseDisplayDevice" is set to "none".
Oh and I told about NvAGP:
Option "NvAGP" "integer"
Configure AGP support. Integer argument can be one of:
0 disable AGP
1 use NVIDIA internal AGP support, if possible
2 use AGPGART, if possible
3 use any AGP support (try AGPGART, then NVIDIA AGP)
Note that NVIDIA internal AGP support cannot work if AGPGART is either statically compiled into your kernel or is built as a module and loaded into your kernel. See Chapter 9, Configuring AGP for details. Default: 3.
You can find a lot more options in appendix-f of the README.