View Full Version : XF86 Config
socomm
January 20th, 2003, 23:04
Let me start off by saying that this is my second time using FreeBSD. Just this evenning I downloaded FreeBSD 5.0RC3. The install went smoothly I installed the X-Developer package this comes with the latest X-server( which works perfectly fine under linux ). My system setup at least the the part pertaining to the graphic interface goes as follows:
Video Card: SiS 630
Video Memory: 8192k
Monitor: LE-500
H-Sync: 30-69
V-Sync: 50-120
I've been through the whole FreeBSD handbook even setting thes values by hand. Also done the whole startx chore and all that results is a long message that displays a long error. I'd be very grateful( greatful? ) if anyone would help me.
Thanks in Advance.
elmore
January 20th, 2003, 23:34
Hey socomm welcome. I'm glad you took the time to sign up for an account. I'm going to ask that you post your XF86Config file and at least summarize the error message that you are receiving. I'm sure if you post that we can get you fixed up in a gif.
Kernel_Killer
January 20th, 2003, 23:35
There could be various errors causing this. What is the error at the end? The one marked with the (EE) at the beginning of the line? It might even be your mouse. :P
You should also be albe to get the error from the file /var/log/XFree86.0.log
socomm
January 21st, 2003, 12:22
BSD is not detecting my floppy so ill have to post back later once I get the net configured. By the way what is the BSD equivalent of eth0 is it net? This is required for the roaring penguin setup. Are there any other ADSL dialers that you guys would recommend? Thanks guys I really appreciate the help :)
bsdjunkie
January 21st, 2003, 12:32
The ethernet interface is dependant on the network card you have. A linksys is often dc0 and intel is fxp0. do an ifconfig -a or look in your dmesg to see what it was detected as.
elmore
January 21st, 2003, 12:40
3coms are xl0
BTW your floppy should be something like fd0a
elmore
January 21st, 2003, 12:52
well if you use pppoe you could configure that. Here's a link that should help with your ADSL setup.
http://docs.freebsd.org/handbook/en/4.5R/ppp-and-slip.html
In general This link is one you'll want to bookmark, you'll be visiting it a lot!
http://docs.freebsd.org/handbook/en/4.5R/
socomm
January 21st, 2003, 12:58
A quick ifconfig cleared that .
elmore
January 21st, 2003, 13:05
oh d00d I had that error a while back on one of my machines at home. When I get home I'll look at it to see what I did to fix it because I forget. I seem to remember it was pretty easy.
socomm
January 21st, 2003, 18:58
EDIT: I'm typing this from links so my network is now up still stuck on the XSERVER issu :(.
Kernel_Killer
January 21st, 2003, 21:57
What I did for this error was to go into 'sysinstall' and go into 'configure' then 'XFree86', then the 'XFree86cfg --text' whatever, and set my monitor, and video card again.
elmore
January 22nd, 2003, 00:09
Here's my XF86 file
[code:1:92e4f612c9]
hackbox# cat XF86Config
Section "ServerLayout"
Identifier "XFree86 Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
ModulePath "/usr/X11R6/lib/modules"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
EndSection
Section "Module"
Load "extmod"
Load "glx"
Load "dri"
Load "dbe"
Load "record"
Load "xtrap"
Load "speedo"
Load "type1"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/mouse"
Option "Emulate3Buttons"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 30-107
VertRefresh 48-120
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "SWcursor" # [<bool>]
#Option "PciRetry" # [<bool>]
#Option "NoAccel" # [<bool>]
#Option "SetMClk" # <freq>
#Option "MUXThreshold" # <i>
#Option "ShadowFB" # [<bool>]
#Option "Rotate" # [<str>]
#Option "VideoKey" # <i>
#Option "NoMMIO" # [<bool>]
#Option "NoPciBurst" # [<bool>]
#Option "MMIOonly" # [<bool>]
#Option "CyberShadow" # [<bool>]
#Option "CyberStretch" # [<bool>]
#Option "XvHsync" # <i>
#Option "XvVsync" # <i>
#Option "XvBskew" # <i>
#Option "XvRskew" # <i>
Identifier "Card0"
Driver "trident"
# Driver "vesa"
VendorName "Trident"
BoardName "Cyber/BladeXP"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 16
SubSection "Display"
Depth 1
EndSubSection
SubSection "Display"
Depth 4
EndSubSection
SubSection "Display"
Depth 8
EndSubSection
SubSection "Display"
Depth 15
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768"
# Modes "1280x1024"
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768"
# Modes "1280x1024"
EndSubSection
EndSection
[/code:1:92e4f612c9]
elmore
January 22nd, 2003, 00:17
Particularly you need topay attention to the server layout area it looks like. You could actually just use the XF86Config file I have and plug in your driver.
Hmmm.....
This is the box I had a problem with very similar to you. Another thing to check is to make sure you're pulling the correct config file. /etc/X11/XF86Config sometime FreeBSD looks in /usr/X11/etc or /usr/X11/etc/X11, depending on weather or not you allowed the FreeBSD install to make a link.
Let us know how it goes.
socomm
January 22nd, 2003, 00:55
Thanks elmore and all the others who helped out. I've got the Xserver and network up. I had bit of a problem with the mouse but everything is up and running( minus sound but ill get that up very shortly ). Thanks again guys enjoy the rest of your week :)
socomm
January 26th, 2003, 02:42
Okay I must admit I chickened out for a few days and installed redhat8.0.92. Now I'm back on FreeBSD the ports system is very cool. I've downloaded KDE from cvs aswell as a the latest xserver. Now for my next stumbling block I cannot get this xserver to run either. Here is the output I get:
(EE) SIS(0): Virtual height (0) is too small for the hardware (min128)
(EE) SIS(0): xf86ValidateModes() error
Symbol VBEInit from module /usr/X11R6/lib/modules/drivers/sis_drv.o is unresolved!
*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.
Fatal server error:
Caught signale 11. Server aborting.
The xserver seems to work just fine under the sysconfig util but when I fire it up it blows up with that error. What can I do?
Kernel_Killer
January 26th, 2003, 02:59
What resoulution are you trying to set it to? I would try lowering your resolution a bit, or even lowering to 16-bit depth. Should help.
socomm
January 26th, 2003, 16:13
Great I just lowered the res and it worked perfect :D . Still cant get latest version of KDE but its fine I just wanted konqueror with tabs and all but I'm compiling mozilla now hope that this works. I hope you guys dont mind if I bother you with the sound later on( I compiled the a new kernel just yesterday which is very easy ). Thanks alot you guys been tons of help.
KrUsTy!
January 26th, 2003, 16:37
I hope you guys dont mind if I bother you with the sound later on( I compiled the a new kernel just yesterday which is very easy ). Thanks alot you guys been tons of help.
Sorry for the siliness with your last post socomm, I hit the wrong button and accidently was editting your last post instead of posting my response! I think I have restored your post to its orginal version. That will teach me to have too many things on my screen at once!
Getting sound support to work should be really easy. All you need to to is compile your kernel with the following line in your Kernel config file,
device pcm
The pcm device supports most all modern sound cards. Reboot with your new kernel and the sound should just work. In older versions of FreeBSD you used to have to add the sound device nodes, but I haven't had to do that in a while.
Hope this helps and sorry for the post silliness. That'll learn me to be more carefull! :oops:
{K}
elmore
January 26th, 2003, 17:40
Hey socomm here's a link to a thread that was posted earlier on keeping your ports up to date. You might be able to get the latest version of KDE that way.
http://screamingelectron.org/phpBB2/viewtopic.php?t=221
Krusty wrote that one up. Also I believe that KDE is producing precompiled binaries nowadays for FreeBSD on their website, so you should be able to download the latest there. Cheers.
socomm
January 27th, 2003, 17:29
Thanks I've got the sound to work now also compiled joystick support which does not seem to work with my playstation to usb converter but that is alright. I downloaded kde_cvs version which did not work( something about x fonts ) however I do have mozilla up and running which is great thanks alot I really appreciate all the help :) .
EDIT: Oh yes krusty dont sweat it hehe most things I post are probably trivial so it would not have been a big loss.
GhostDawg
January 29th, 2003, 04:44
Getting sound support to work should be really easy. All you need to to is compile your kernel with the following line in your Kernel config file,
device pcm
The pcm device supports most all modern sound cards. Reboot with your new kernel and the sound should just work. In older versions of FreeBSD you used to have to add the sound device nodes, but I haven't had to do that in a while.
Hope this helps and sorry for the post silliness. That'll learn me to be more carefull! :oops:
{K}
So does Freebsd support the onboard VIA AC'97 sound card pretty good? That's what I have and haven't tried getting any sound yet.
bsdjunkie
January 29th, 2003, 10:53
So does Freebsd support the onboard VIA AC'97 sound card pretty good? That's what I have and haven't tried getting any sound yet.
My experience with that chipset has been hit and miss, at least with linux. Some boxes it worked great and others would detect it but never play sound. Seems like half the internet had the same problems as well judgig by the search results i had. I ended up picking up a cheap sb card and used that instead on the box in question.
Strog
January 29th, 2003, 12:44
The biggest problem with AC'97 is that it is a standard but not really a chipset. Different manufacturers have implemented it in slightly different ways making is very difficult at times. They seem to be Windows oriented but they are still a pain in the butt on Windows too. The good news is that if it works, it is likely to work well and have good sound quality.
I have a Gateway 3600 motherboard with AC'97 on it but I hadn't gotten around to trying it. I have a Sound Blaster Live that I was going to put in there if it gives me too much trouble. AC'97 uses more CPU time than a decent PCI sound card so putting in a replacement sound card isn't all bad.
GhostDawg
February 3rd, 2003, 00:42
Yes you right about different mfg. using different standards. From reading Linux forums, some users seem to get AC'97 working and some have to get alsa sound drivers, which is what I had to do with Slackware & Debian to get mine working.
The same with windoze, Winxp picked it right up and Win98 I have to use the drivers that came with the mobo. Odd!
I think I will just buy a cheap SB card & a nice hardware modem and install them.
Thnx.
vBulletin® v3.7.1, Copyright ©2000-2012, Jelsoft Enterprises Ltd.