FreeBSD 6.x problems with IDE drives
Greetings, I've a motherboard and disk drive that have been running on older versions of FreeBSD for quite a while, reliably. Recently, I moved to FreeBSD 6.0-RELEASE (and lately to 6.1-RELEASE, but it didn't help), and the system periodically shows: > ad4: FAILURE - device detached This is likely to happen under heavy I/O load (the machine serves a few dozen virtual websites, averaging 15 Mb/s sustained). Then the machine will eventually reboot. The motherboard is an MSI with an AMD 1.3 GHz CPU and 1.25GB of RAM, it has two IDE controllers, a VIA 8235, and a Promise (I can't access the machine right now to get the exact model number). The problem happens the same with either controller. I tried both UDMA100 and PIO4 modes, no difference. SMART reports a healthy drive, and as mentioned before, it didn't have problems with older versions of FreeBSD (5.4-RELEASE to be precise) and under similarly heavy load. The IDE cable was replaced, just in case, but again, no difference. Any ideas? -jav ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: FreeBSD 5.x problems with new dell server
>-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Jason Lieurance >Sent: Friday, June 03, 2005 8:05 AM >To: freebsd-questions@freebsd.org >Subject: FreeBSD 5.x problems with new dell server > > >Hello, > >I bought a new dell poweredge1425sc server. > >It's has dual 2.8 xeon's with HT, 1 Gb ram, Seagate u320 73GB >HD, Adaptec >u320 scsi controller, its all new stuff. > >FreeBSD 5.3 and 5.4 install fine but then its trouble. It'll be >running fine >and I'll be doing whatever and then intermeantly it will kick >out a bunch of >junk(forgive me I didn't write it down) about scsi channel A timing out. >After all that comes up in white, it'll go back to normal. Then a couple >minutes later it repeats it self and so on. > > >I would really like to get FreeBSD 5.x on there somehow cause I >love BSD but >for now I guess I'll settle for debian unless someone can uncover the >mystery. > You have to use send-pr if you want someone to uncover the mystery. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 5.x problems with new dell server
Hello, I bought a new dell poweredge1425sc server. It's has dual 2.8 xeon's with HT, 1 Gb ram, Seagate u320 73GB HD, Adaptec u320 scsi controller, its all new stuff. FreeBSD 5.3 and 5.4 install fine but then its trouble. It'll be running fine and I'll be doing whatever and then intermeantly it will kick out a bunch of junk(forgive me I didn't write it down) about scsi channel A timing out. After all that comes up in white, it'll go back to normal. Then a couple minutes later it repeats it self and so on. Now, I know the hardware is ok because I checked it and it came wired from the factory but most importantly, Debian Linux(sarge) works fine on it and whats installed now(2 weeks, no problems). I tried disabling HT support on both 5.3 and 5.4 but this doesn't help ( I didn't figure it would but I read something about bad things with HT and BSD 5.x). I would really like to get FreeBSD 5.x on there somehow cause I love BSD but for now I guess I'll settle for debian unless someone can uncover the mystery. Thanks. -- Jason ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 5.x problems with new dell server
Hello, I bought a new dell poweredge1425sc server. It's has dual 2.8 xeon's with HT, 1 Gb ram, Seagate u320 73GB HD, Adaptec u320 scsi controller, its all new stuff. FreeBSD 5.3 and 5.4 install fine but then its trouble. It'll be running fine and I'll be doing whatever and then intermeantly it will kick out a bunch of junk(forgive me I didn't write it down) about scsi channel A timing out. After all that comes up in white, it'll go back to normal. Then a couple minutes later it repeats it self and so on. Now, I know the hardware is ok because I checked it and it came wired from the factory but most importantly, Debian Linux(sarge) works fine on it and whats installed now(2 weeks, no problems). I tried disabling HT support on both 5.3 and 5.4 but this doesn't help ( I didn't figure it would but I read something about bad things with HT and BSD 5.x). I would really like to get FreeBSD 5.x on there somehow cause I love BSD but for now I guess I'll settle for debian unless someone can uncover the mystery. Thanks. -- Jason ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X problems with Dell Inspiron 2600s
Make sure you are running 6.8.2 and try the following driver: http://www.fairlite.demon.co.uk/intel.html On Wed, 2005-03-23 at 12:56 -0500, Rob Winters wrote: > Remington wrote: > > Please attach full Xorg.log and xorg.conf. This wouldnt happen to be a > > widescreen would it? > > I sent the full config and log in the first message. > > This is a 1024x768 screen. Cheapest laptop made; too cheap to put a > property sticker on. > > /// Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X problems with Dell Inspiron 2600s
Remington wrote: Please attach full Xorg.log and xorg.conf. This wouldnt happen to be a widescreen would it? I sent the full config and log in the first message. This is a 1024x768 screen. Cheapest laptop made; too cheap to put a property sticker on. /// Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X problems with Dell Inspiron 2600s
Please attach full Xorg.log and xorg.conf. This wouldnt happen to be a widescreen would it? On Tue, 2005-03-22 at 11:21 -0500, Rob Winters wrote: > Remington wrote: > > change the device driver to vesa, see if it still crashes > > Changed "I810" to "vesa": > > old: > > >(EE) I810(0): No Video BIOS modes for chosen depth. > >(==) I810(0): Write-combining range (0x0,0x1000) was already clear > >(II) UnloadModule: "i810" > >(II) UnloadModule: "ddc" > >(II) Unloading /usr/X11R6/lib/modules/libddc.a > >(II) UnloadModule: "int10" > >(II) UnloadModule: "int10" > >(II) UnloadModule: "vgahw" > >(II) Unloading /usr/X11R6/lib/modules/libvgahw.a > >(II) UnloadModule: "vbe" > >(II) Unloading /usr/X11R6/lib/modules/libvbe.a > >(II) UnloadModule: "int10" > >(II) Unloading /usr/X11R6/lib/modules/libint10.a > >(EE) Screen(s) found, but none have a usable configuration. > > > >Fatal server error: > >no screens found > > new: > > > (II) VESA(0): Total Memory: 125 64KB banks (8000kB) > > (EE) VESA(0): No matching modes > > (==) VESA(0): Write-combining range (0x0,0x1000) was already clear > > (II) UnloadModule: "vesa" > > (II) UnloadModule: "ddc" > > (II) Unloading /usr/X11R6/lib/modules/libddc.a > > (II) UnloadModule: "int10" > > (II) Unloading /usr/X11R6/lib/modules/libint10.a > > (II) UnloadModule: "vbe" > > (II) Unloading /usr/X11R6/lib/modules/libvbe.a > > (EE) Screen(s) found, but none have a usable configuration. > > > > Fatal server error: > > no screens found > > /// Rob > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X problems with Dell Inspiron 2600s
Remington wrote: change the device driver to vesa, see if it still crashes Changed "I810" to "vesa": old: (EE) I810(0): No Video BIOS modes for chosen depth. (==) I810(0): Write-combining range (0x0,0x1000) was already clear (II) UnloadModule: "i810" (II) UnloadModule: "ddc" (II) Unloading /usr/X11R6/lib/modules/libddc.a (II) UnloadModule: "int10" (II) UnloadModule: "int10" (II) UnloadModule: "vgahw" (II) Unloading /usr/X11R6/lib/modules/libvgahw.a (II) UnloadModule: "vbe" (II) Unloading /usr/X11R6/lib/modules/libvbe.a (II) UnloadModule: "int10" (II) Unloading /usr/X11R6/lib/modules/libint10.a (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found new: (II) VESA(0): Total Memory: 125 64KB banks (8000kB) (EE) VESA(0): No matching modes (==) VESA(0): Write-combining range (0x0,0x1000) was already clear (II) UnloadModule: "vesa" (II) UnloadModule: "ddc" (II) Unloading /usr/X11R6/lib/modules/libddc.a (II) UnloadModule: "int10" (II) Unloading /usr/X11R6/lib/modules/libint10.a (II) UnloadModule: "vbe" (II) Unloading /usr/X11R6/lib/modules/libvbe.a (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found /// Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X problems with Dell Inspiron 2600s
change the device driver to vesa, see if it still crashes On Mon, 2005-03-21 at 18:32 -0500, Rob Winters wrote: > I have a couple of Dell Inspiron 2600s, and I can't run Xorg or Xfree86 > on either of them from FreeBSD 5.3 Release. A Fedora Core 3 locks up > solid with the same machines. I'd suspect a video hardware problem, > except I have two failing machines, and "that Microsoft thing" works > fine on both. > > The video is Intel 830M, and the display is a 1024x768 LCD. These should > run with the i810 "family" drivers, I thought. I read about problems > with earlier BIOSen, so I upgraded to the latest (A011), but no joy. > I've tried a few things, but I'm probably going in circles at this > point. So, I will keep it simple. Following is the config generated by > the "Xorg -configure", followed by the log generated by "Xorg -config > /root/xorg.conf.new. > > Help appreciated. Thanks! > > /// Rob > > P.S. Option "NoDDC" per TFM did not fix it. > --- > Section "ServerLayout" > Identifier "X.org 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/TTF/" > 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 "dbe" > Load "dri" > Load "extmod" > Load "glx" > Load "record" > Load "xtrap" > Load "freetype" > Load "speedo" > Load "type1" > EndSection > > Section "InputDevice" > Identifier "Keyboard0" > Driver "keyboard" > EndSection > > Section "InputDevice" > Identifier "Mouse0" > Driver "mouse" > Option "Protocol" "auto" > Option "Device" "/dev/sysmouse" > EndSection > > Section "Monitor" > Identifier "Monitor0" > VendorName "Monitor Vendor" > ModelName"Monitor Model" > EndSection > > Section "Device" > ### Available Driver options are:- > ### Values: : integer, : float, : "True"/"False", > ### : "String", : " Hz/kHz/MHz" > ### [arg]: arg optional > #Option "NoAccel"# [] > #Option "SWcursor" # [] > #Option "ColorKey" # > #Option "CacheLines" # > #Option "Dac6Bit"# [] > #Option "DRI"# [] > #Option "NoDDC" # [] > #Option "ShowCache" # [] > #Option "XvMCSurfaces" # > #Option "PageFlip" # [] > Identifier "Card0" > Driver "i810" > VendorName "Intel Corp." > BoardName "82830 CGC [Chipset Graphics Controller]" > BusID "PCI:0:2:0" > EndSection > > Section "Screen" > Identifier "Screen0" > Device "Card0" > Monitor"Monitor0" > SubSection "Display" > Viewport 0 0 > Depth 1 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 4 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 8 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 15 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 16 > EndSubSection > SubSection "Display" > Viewport 0 0 > Depth 24 > EndSubSection > EndSection > --- > Release Date: 18 December 2003 > X Protocol Version 11, Revision 0, Release 6.7 > Build Operating System: FreeBSD 5.3 i386 [ELF] > Current Operating System: FreeBSD trebor 5.3-RELEASE FreeBSD 5.3-RELEASE > #0: Fri Nov 5 04:19:18 UTC 2004 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 > Build Date: 16 October 2004 > Before reporting problems, check http://wiki.X.Org > to make sure that you have the latest version. > Module Loader present > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 21 18:05:52 2005 > (++) Using config file: "/root/xorg.conf.new" > (==) ServerLayout "X.org Configured" > (*
X problems with Dell Inspiron 2600s
I have a couple of Dell Inspiron 2600s, and I can't run Xorg or Xfree86 on either of them from FreeBSD 5.3 Release. A Fedora Core 3 locks up solid with the same machines. I'd suspect a video hardware problem, except I have two failing machines, and "that Microsoft thing" works fine on both. The video is Intel 830M, and the display is a 1024x768 LCD. These should run with the i810 "family" drivers, I thought. I read about problems with earlier BIOSen, so I upgraded to the latest (A011), but no joy. I've tried a few things, but I'm probably going in circles at this point. So, I will keep it simple. Following is the config generated by the "Xorg -configure", followed by the log generated by "Xorg -config /root/xorg.conf.new. Help appreciated. Thanks! /// Rob P.S. Option "NoDDC" per TFM did not fix it. --- Section "ServerLayout" Identifier "X.org 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/TTF/" 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 "dbe" Load "dri" Load "extmod" Load "glx" Load "record" Load "xtrap" Load "freetype" Load "speedo" Load "type1" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName"Monitor Model" EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz" ### [arg]: arg optional #Option "NoAccel" # [] #Option "SWcursor"# [] #Option "ColorKey"# #Option "CacheLines" # #Option "Dac6Bit" # [] #Option "DRI" # [] #Option "NoDDC" # [] #Option "ShowCache" # [] #Option "XvMCSurfaces"# #Option "PageFlip"# [] Identifier "Card0" Driver "i810" VendorName "Intel Corp." BoardName "82830 CGC [Chipset Graphics Controller]" BusID "PCI:0:2:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor"Monitor0" SubSection "Display" Viewport 0 0 Depth 1 EndSubSection SubSection "Display" Viewport 0 0 Depth 4 EndSubSection SubSection "Display" Viewport 0 0 Depth 8 EndSubSection SubSection "Display" Viewport 0 0 Depth 15 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection --- Release Date: 18 December 2003 X Protocol Version 11, Revision 0, Release 6.7 Build Operating System: FreeBSD 5.3 i386 [ELF] Current Operating System: FreeBSD trebor 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Build Date: 16 October 2004 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 21 18:05:52 2005 (++) Using config file: "/root/xorg.conf.new" (==) ServerLayout "X.org Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (==) Keyboard: CustomKeycode disabled (WW) `fonts.dir' not found (or not valid) in "/usr/X11R6/lib/X11/fonts/Speedo/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/X11R6/lib/X11/fonts/Speedo/"). (WW) `fonts.dir' not found (or not valid) in "/usr/X11R6/lib/X11/fonts/CID/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/X11R6/lib/X11/fonts/CID/"). (**) FontPath set to "/usr/X11R6/lib/X11/f
Re: X problems after upgrade to 6.8.1
On Thu, Dec 23, 2004 at 07:11:00PM -0800, Your Name wrote: > Hi, > > i just upgraded a FreeBSD 5.3 box to Xorg 6.8.1 and it > went perfectly smoothly, then i tried to upgrade a > 4.10 box and im having problems. Please re-send to [EMAIL PROTECTED], the port maintainers. Kris pgpbpqnD8XzjD.pgp Description: PGP signature
X problems after upgrade to 6.8.1
Hi, i just upgraded a FreeBSD 5.3 box to Xorg 6.8.1 and it went perfectly smoothly, then i tried to upgrade a 4.10 box and im having problems. i just did the usual portupgrade -rR xorg, and the entire build process worked fine with no errors. But when i restarted gdm, it died with the following in my .xsession-errors: --- /usr/X11R6/etc/gdm/PreSession/Default: Registering your session with wtmp and utmp /usr/X11R6/etc/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w /var/log/wtmp -u /va r/run/utmp -x "/usr/X11R6/share/gnome/gdm/:0.Xservers" -h "" -l ":0" "jen" /usr/X11R6/etc/gdm/Xsession: Beginning session setup... /usr/X11R6/etc/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session GThread-ERROR **: file gthread-posix.c: line 137 (g_thread_impl_init): error 'Invalid argument' d uring 'pthread_getschedparam (pthread_self(), &policy, &sched)' aborting... --- i Googled but couldn't find another report of this, and didnt see anything in freebsd-questions either. i did rebuild gtk but that didnt work either. thanks for help on what to do, Jen __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MySQL and FreeBSD 4.x.. problems, problems with server
dap wrote: This has happened with enough servers at different locations that I have to believe there is a relationship here. I have servers running the latest release of MySQL. I've run the servers on FreeBSD 4.4., 4.7, and 4.8. I am not using the threaded version. MySQL always uses threads. It's just that you have the choice which implementation to use, native or Linux threads. On all three versions, on different servers at different sites, I have seen MySQL just go wacky after a while. Two types of symptoms: 1. mysqld just decides to consume as much of the CPU as possible. 2. new connections to mysql fail It will usually take 1-3 weeks between occurances. [...] Yes, this is a mysql problem probably, and not a FreeBSD problem. However, I'm hoping to get some help or hope here as well as with the mysql people. :) There have been some fixes lately to 'libc_r', the threads lib MySQL uses by default on FreeBSD 4.x. They deal with EOF conditions in connection with write(2) which may very well cause process looping. This programming error could be the cause of your problem as well, so it might be worthwhile to take a look at the latest CVS commits to 'uthread_write.c': http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc_r/uthread/uthread_write.c?sortby=date&only_with_tag=RELENG_4 BTW, a potentially serious problem with signals in 'uthread_join.c' has been fixed recently, too. Hope it helps in your case. Uwe -- Uwe Doering | EscapeBox - Managed On-Demand UNIX Servers [EMAIL PROTECTED] | http://www.escapebox.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
MySQL and FreeBSD 4.x.. problems, problems with server
This has happened with enough servers at different locations that I have to believe there is a relationship here. I have servers running the latest release of MySQL. I've run the servers on FreeBSD 4.4., 4.7, and 4.8. I am not using the threaded version. On all three versions, on different servers at different sites, I have seen MySQL just go wacky after a while. Two types of symptoms: 1. mysqld just decides to consume as much of the CPU as possible. 2. new connections to mysql fail It will usually take 1-3 weeks between occurances. I have seen posts relating to this off and on. Is there a known problem with running mysqld on FreeBSD 4.x? What about 5.x? Is it better? I was talking to another FreeBSD admin the other day and he commented on the same thing: "mysqld on our FreeBSD 4.7 boxes just lose it sometimes." Honestly, I am thinking of converting out MySQL db servers from FreeBSD to Linux for this reason, and only this reason. Otherwise, I love FreeBSD, but this is just no good. I would blame myself, but I can't when I get wind that others are having the same problem. Yes, this is a mysql problem probably, and not a FreeBSD problem. However, I'm hoping to get some help or hope here as well as with the mysql people. :) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X problems
On Sun, 11 Jan 2004 09:36:39 -0700 (MST) "Lance Earl" <[EMAIL PROTECTED]> wrote: > The Monitor section of XF86Config includes > Identifier "Monitor0" > VendorName "Monitor Vendor" > Model Name "Monitor Model" > HorizSync31.0 -70.0 > VertRefresh 55.0 - 120.0 If your aim is simply to get a stable display (at the expense of video quality,) you could try more conservative values for these. I have the following in my XF86Config: HorizSync 31.5 - 35.1 VertRefresh 50.0 - 70.0 This lets me get 16-bit colour at 800x600 resolution, which is all I need. If you want higher resolutions, you can start from there and gradually increase the values until you get a range which is large enough to support more colours and/or pixels, but not so large that it lets your display go all woobly. > My Monitor is a NEC FE700+ so these settings seem to be correct. I see > taht the refresh rates are not in quotes like the other items, is this > correct? Correct, they do not need quotes. > I forgot to mention that during install, after running the xconfig > setup and saving the files, it said that the setup appeared to have > failed and gave me a chance to try again. I tried several times but > with the same result. I get this all the time too. I think it might be a bug in the install process, actually... -Chris ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X problems
The Monitor section of XF86Config includes Identifier "Monitor0" VendorName "Monitor Vendor" Model Name "Monitor Model" HorizSync31.0 -70.0 VertRefresh 55.0 - 120.0 My Monitor is a NEC FE700+ so these settings seem to be correct. I see taht the refresh rates are not in quotes like the other items, is this correct? I forgot to mention that during install, after running the xconfig setup and saving the files, it said that the setup appeared to have failed and gave me a chance to try again. I tried several times but with the same result. I am running Version 4.8 but thought that I may try version 5.1 to see if I get a better result. Thanks Eric F Crist said: > On Saturday 10 January 2004 10:17 pm, Lance Earl wrote: >> Hi Eric, >> >> We are 1 for 2. I got it so that it will load gnome with startx. > > Glad to hear it! > >> >> The flicker problems on the screen persist and now appear to be the case >> 100% of the time. Restarting the machine no longer seems to correct the >> problem. Do you have any additional suggestions? >> > > Yes. Check the manual for your monitor's refresh rate and make sure you > setup > XFree86 for the correct numbers. This is usually 60 Hz or 72Hz, depending > on > the resolution you set. > > >> I am considering FreeBSD as the OS for our internet server because >> RedHat >> is no longer a viable solution. I just do not like the direction of the >> company. We run Apache, Sendmail, PHP, MySQL, Squirrel Mail and Image >> Magick. I have also considered Debian as a possible candidate. Do you >> have >> any suggestions regarding these two options? > > Yes. I use FreeBSD on my servers. I'm currently in the process of a > physical > move/ISP change, so they're hosted on another set of servers (linux, of > unknow vendor), so they're not under my control ATM. I've been running > FreeBSD as a web server since 1998. It has been 100% secure for me, even > when I was running a 'questionable' server with a domain name of > ardent-hacker.net. Also, the support here for FreeBSD is great! > > HTH > -- > Eric F Crist > AdTech Integrated Systems, Inc > (612) 998-3588 Lance Earl DallyPost, Inc. 208-548-2721 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X problems
On Saturday 10 January 2004 08:49 pm, Lance Earl wrote: > My first install went pretty good but I have a few problems. > > 1. When I startx, x starts properly the first time. When I shut down x > with ctrl/alt backspace, I get: waiting for X server to shut down xterm: A couple things for you: 1) Ctrl-Alt-Backspace is not really the _correct_ way to shutdown the xwindows system. If you get a black, checkered screen with about three green windows, select the one on the left and type 'exit.' If this doesn't work, do the Ctrl-Alt-Backspace and kill all processes that mention X or xfree. 2) To get Gnome to start create a file in your user's home directory ( ~/ ) called .xinitrc (WITH the 'dot' in front). In this file, add the line: exec gnome-session If you use KDE instead, use the line: exec startkde Hope this helps, and welcome to the club. -- Eric F Crist AdTech Integrated Systems, Inc (612) 998-3588 pgp0.pgp Description: signature
X problems
I am new to FreeBSD. I am giving it a hard look because I do not like the the direction that Red Hat is taking and I must find a replacement for my server, www.dallypost.com. My first install went pretty good but I have a few problems. 1. When I startx, x starts properly the first time. When I shut down x with ctrl/alt backspace, I get: waiting for X server to shut down xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0" xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ":0.0" If I attempt to restart x I get a flickering effect that makes the entire screen kind of sparkle. I installed FreeBSD with gnome, but it does not start when I startx. How can I make startx boot into gnome? Thank you for any help. Lance Earl DallyPost, Inc. 208-548-2721 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X problems on i810 | AddScreen/ScreenInit failed
>24bit isn't supported by the driver so I run in 16bit which >is fine. I think acceleration isn't supported in 24 bit at least for the i815e chipset (on my motherboard). > The default configurator option to XFree86 gives a config which >doesn't work, incidently. That would explain why I couldn't get it working on NetBSD. Grrr, typical. Andrew Lankford To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: X problems on i810 | AddScreen/ScreenInit failed
On Tue, Feb 11, 2003 at 09:09:56AM -0700, Darren Spruell wrote: }Andrew Lankford wrote: }>To my knowledge, DRI extensions have never worked with i810 on FreeBSD. }>Whenever I felt tinkering with the config to see I could enable DRI, it }>wouldn't take, but I don't think it ever mucked up my screen. My video }>monitor did have some trouble with the DDC option (on my stable partition, }>just after I had upgraded the bios), but DDC seems to work ok now. If }>you do get it working, I would stay with a DefaultDepth of 16 instead }>of 24, as a setting of 24 tends to slow demanding apps down without }>noticeably improving picture quality. Notice also that the HorizSync }>and VertRefresh values are a tiny bit different on mine as well. }Aargh. I tried both the changes you suggested, as well as adjusting only }the relevant parts of your config and trying it.. same result in both }cases. I even pulled a Red Hat 7.3 XFree86-4 config off of a working X }station and adjusted paths, etc. Same stupid staticy crap with the white }square ;) I hope you haven't given up yet - I just noticed your post. I run XFree86 4.2.0 on an i810. There is no dri yet (see http://people.freebsd.org/~anholt/dri/), but enabling it in the config is harmless. 24bit isn't supported by the driver so I run in 16bit which is fine. The default configurator option to XFree86 gives a config which doesn't work, incidently. -- Callum Gibson [EMAIL PROTECTED] Global Markets IT, Deutsche Bank, Australia 61 2 9258 1620 ### The opinions in this message are mine and not Deutsche's ### # File generated by xf86config. # # Copyright (c) 1999 by The XFree86 Project, Inc. # # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the "Software"), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Except as contained in this notice, the name of the XFree86 Project shall # not be used in advertising or otherwise to promote the sale, use or other # dealings in this Software without prior written authorization from the # XFree86 Project. # # ** # Refer to the XF86Config(4/5) man page for details about the format of # this file. # ** # ** # Module section -- this section is used to specify # which dynamically loadable modules to load. # ** # Section "Module" # This loads the DBE extension module. # This loads the miscellaneous extensions module, and disables # initialisation of the XFree86-DGA extension within that module. SubSection "extmod" Option"omit xfree86-dga" # don't initialise the DGA extension EndSubSection # This loads the Type1 and FreeType font modules Load"type1" Load"freetype" # This loads the GLX module Load "dbe" Load "glx" Load "dri" EndSection # ** # Files section. This allows default font and rgb paths to be set # ** Section "Files" # The location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. RgbPath "/usr/X11R6/lib/X11/rgb" # Multiple FontPath entries are allowed (which are concatenated together), # as well as specifying multiple comma-separated entries in one FontPath # command (or a combination of both methods) # # If you don't have a floating point coprocessor and emacs, Mosaic or other # programs take long to start up, try moving the Type1 and Speedo directory # to the end of this list (or comment them out). # FontPath "/usr/X11R6/lib/X11/fonts/local/" FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath "/us
Re: X problems on i810 | AddScreen/ScreenInit failed
In Device section, try using Driver "i810" (rt. now u r using "vga") If still it doesn't work, I can send you the working XF86Config offlist. Regards, Shantanu +++ Darren Spruell [11-02-03 08:03 -0700]: | Date: Tue, 11 Feb 2003 08:03:39 -0700 | From: Darren Spruell <[EMAIL PROTECTED]> | User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 | To: Shantanu Mahajan <[EMAIL PROTECTED]> | CC: [EMAIL PROTECTED] | Subject: Re: X problems on i810 | AddScreen/ScreenInit failed | | | | Shantanu Mahajan wrote: | >in which file you have made changes? from the logs, you are using | >./XF86Config.new | >Make changes in that file. | > | >Regards, | >Shantanu | | That is the file I am changing and testing (/root/XF86Config.new). | | > | >+++ Darren Spruell [10-02-03 13:28 -0700]: | >| Date: Mon, 10 Feb 2003 13:28:42 -0700 | >| From: Darren Spruell <[EMAIL PROTECTED]> | >| User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) | >Gecko/20020826 | >| To: Shantanu Mahajan <[EMAIL PROTECTED]> | >| CC: [EMAIL PROTECTED] | >| Subject: Re: X problems on i810 | AddScreen/ScreenInit failed | >| | >| Shantanu Mahajan wrote: | >| >try adding following lines | >| > | >| >in Device section | >| > Option "NoDDC" | >| > | >| >in Monitor section | >| > Option "DPMS" | >| > | >| >Regards, | >| >Shantanu | >| | >| Added as suggested. Relevant sections now read: | >| | >| Section "Monitor" | >| Identifier "Monitor0" | >| Option "DPMS" | >| VendorName "Gateway" | >| ModelName"EV700" | >| HorizSync30 - 69 | >| VertRefresh 50 - 110 | >| EndSection | >| | >| Section "Device" | >| ### Available Driver options are:- | >| ### Values: : integer, : float, : "True"/"False", | >| ### : "String", : " Hz/kHz/MHz" | >| ### [arg]: arg optional | >| #Option "ShadowFB" # [] | >| #Option "VGAClocks" # [] | >| Option "NoDDC" | >| Identifier "Card0" | >| Driver "vga" | >| VendorName "Intel" | >| BoardName "i810-dc100" | >| BusID "PCI:0:1:0" | >| EndSection | >| | >| | >| | >| | >| > | >| >+++ Darren Spruell [freebsd] [10-02-03 11:07 -0700]: | >| >| Date: Mon, 10 Feb 2003 11:07:22 -0700 | >| >| From: Darren Spruell <[EMAIL PROTECTED]> | >| >| Subject: X problems on i810 | AddScreen/ScreenInit failed | >| >| | >| >| Greetz, | >| >| | >| >| I'm trying to configure v4.7 to run X but am having a hard time | >getting | >| the server to start. | >| >| | >| >| I've followed the config instructions at | >| >| | >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html | | >>| by doing the following steps: | >| >| | >| >| Run XFree86 -configure | >| >| to create the default XF86Config.new | >| >| Run XFree86 -xf86config ./XF86Config.new | >| >| to ensure that it works w/my hardware | >| >| Edit it to taste, to change specifics for HorizSync, VertRefresh, and | >| >| the Display subsection under "Screen". | >| >| | >| >| However, running 'XFree86 -xf86config ./XF86Config.new' after | >changing | >| my config does not work. The output error is: | >| >| | >| >| == | >| >| (==) VGA(0): Write-combining range (0xa,0x1) was already clear | >| >| | >| >| Fatal server error: | >| >| AddScreen/ScreenInit failed for driver 0 | >| >| == | >| >| | >| >| I followed through the part in the Advanced Configuration section | >about | >| adding in support for agpgart and created the device node and | >added the | >| following to /boot/loader.conf: | >| >| agp_load="YES" | >| >| | >| >| dmesg now shows: | >| >| Preloaded elf module "agp.ko" at 0xc051a09c. | >| >| agp0: mem | >| >| 0xffa8-0xffaf,0xf800-0xfbff irq 11 at device 1.0 on | >pci0 | >| >| | >| >| Here is the current XF86Config.new (non-working). The Monitor section | >| >| was taken from a specs page on the Monitor (Gateway EV700). Full | >dmesg |
Re: X problems on i810 | AddScreen/ScreenInit failed
I did have an instance where my screen had this annoying green square on it, I tried soo many things until I kicked the box in desperation. [ kick = reboot ] It was gone when I restarted. I don't know if this will help or not, just thought I'd throw what happened to me into the mix. R. On Tue, 11 Feb 2003, Darren Spruell wrote: > Andrew Lankford wrote: > > To my knowledge, DRI extensions have never worked with i810 on FreeBSD. > > Whenever I felt tinkering with the config to see I could enable DRI, it > > wouldn't take, but I don't think it ever mucked up my screen. My video monitor > > did have some trouble with the DDC option (on my stable partition, just after > > I had upgraded the bios), but DDC seems to work ok now. If you do get it > > working, I would stay with a DefaultDepth of 16 instead of 24, as > > a setting of 24 tends to slow demanding apps down without noticeably improving > > picture quality. Notice also that the HorizSync and VertRefresh values are > > a tiny bit different on mine as well. > > > > Anyway, here's my XF86Config: > [...] > > Aargh. I tried both the changes you suggested, as well as adjusting only > the relevant parts of your config and trying it.. same result in both > cases. I even pulled a Red Hat 7.3 XFree86-4 config off of a working X > station and adjusted paths, etc. Same stupid staticy crap with the white > square ;) > > Anyway. I hate getting whooped by something this stupid, but I'm at > wit's end. Any other suggestions? If not, I found another huddy OEM > Gateway box with a different video card. I've got half a mind to try X > out on it. > > -- > Darren Spruell > Sento IS Department > [EMAIL PROTECTED] > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: X problems on i810 | AddScreen/ScreenInit failed
Andrew Lankford wrote: To my knowledge, DRI extensions have never worked with i810 on FreeBSD. Whenever I felt tinkering with the config to see I could enable DRI, it wouldn't take, but I don't think it ever mucked up my screen. My video monitor did have some trouble with the DDC option (on my stable partition, just after I had upgraded the bios), but DDC seems to work ok now. If you do get it working, I would stay with a DefaultDepth of 16 instead of 24, as a setting of 24 tends to slow demanding apps down without noticeably improving picture quality. Notice also that the HorizSync and VertRefresh values are a tiny bit different on mine as well. Anyway, here's my XF86Config: [...] Aargh. I tried both the changes you suggested, as well as adjusting only the relevant parts of your config and trying it.. same result in both cases. I even pulled a Red Hat 7.3 XFree86-4 config off of a working X station and adjusted paths, etc. Same stupid staticy crap with the white square ;) Anyway. I hate getting whooped by something this stupid, but I'm at wit's end. Any other suggestions? If not, I found another huddy OEM Gateway box with a different video card. I've got half a mind to try X out on it. -- Darren Spruell Sento IS Department [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: X problems on i810 | AddScreen/ScreenInit failed
Shantanu Mahajan wrote: in which file you have made changes? from the logs, you are using ./XF86Config.new Make changes in that file. Regards, Shantanu That is the file I am changing and testing (/root/XF86Config.new). +++ Darren Spruell [10-02-03 13:28 -0700]: | Date: Mon, 10 Feb 2003 13:28:42 -0700 | From: Darren Spruell <[EMAIL PROTECTED]> | User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 | To: Shantanu Mahajan <[EMAIL PROTECTED]> | CC: [EMAIL PROTECTED] | Subject: Re: X problems on i810 | AddScreen/ScreenInit failed | | Shantanu Mahajan wrote: | >try adding following lines | > | >in Device section | > Option "NoDDC" | > | >in Monitor section | > Option "DPMS" | > | >Regards, | >Shantanu | | Added as suggested. Relevant sections now read: | | Section "Monitor" | Identifier "Monitor0" | Option "DPMS" | VendorName "Gateway" | ModelName"EV700" | HorizSync30 - 69 | VertRefresh 50 - 110 | EndSection | | Section "Device" | ### Available Driver options are:- | ### Values: : integer, : float, : "True"/"False", | ### : "String", : " Hz/kHz/MHz" | ### [arg]: arg optional | #Option "ShadowFB" # [] | #Option "VGAClocks" # [] | Option "NoDDC" | Identifier "Card0" | Driver "vga" | VendorName "Intel" | BoardName "i810-dc100" | BusID "PCI:0:1:0" | EndSection | | | | Still the same error occurs. Here is the full output of the | /var/log/XFree86.0.log for this attempt: | | | | XFree86 Version 4.2.1 / X Window System | (protocol Version 11, revision 0, vendor release 6600) | Release Date: 3 September 2002 | If the server is older than 6-12 months, or if your card is | newer than the above date, look for a newer version before | reporting problems. (See http://www.XFree86.Org/) | Build Operating System: FreeBSD 5.0-CURRENT i386 [ELF] | Module Loader present | Markers: (--) probed, (**) from config file, (==) default setting, | (++) from command line, (!!) notice, (II) informational, | (WW) warning, (EE) error, (NI) not implemented, (??) unknown. | (==) Log file: "/var/log/XFree86.0.log", Time: Mon Feb 10 14:23:18 2003 | (++) Using config file: "./XF86Config.new" | (==) ServerLayout "XFree86 Configured" | (**) |-->Screen "Screen0" (0) | (**) | |-->Monitor "Monitor0" | (**) | |-->Device "Card0" | (**) |-->Input Device "Mouse0" | (**) |-->Input Device "Keyboard0" | (==) Keyboard: CustomKeycode disabled | (**) FontPath set to | "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts | /75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/" | (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" | (**) ModulePath set to "/usr/X11R6/lib/modules" | (--) Using syscons driver with X support (version 2.0) | (--) using VT number 9 | | (II) Module ABI versions: | XFree86 ANSI C Emulation: 0.1 | XFree86 Video Driver: 0.5 | XFree86 XInput driver : 0.3 | XFree86 Server Extension : 0.1 | XFree86 Font Renderer : 0.3 | (II) Loader running on freebsd | (II) LoadModule: "bitmap" | (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a | (II) Module bitmap: vendor="The XFree86 Project" | compiled for 4.2.1, module version = 1.0.0 | Module class: XFree86 Font Renderer | ABI class: XFree86 Font Renderer, version 0.3 | (II) Loading font Bitmap | (II) LoadModule: "pcidata" | (II) Loading /usr/X11R6/lib/modules/libpcidata.a | (II) Module pcidata: vendor="The XFree86 Project" | compiled for 4.2.1, module version = 0.1.0 | ABI class: XFree86 Video Driver, version 0.5 | (II) PCI: Probing config type using method 1 | (II) PCI: Config type is 1 | (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 | (II) PCI: PCI scan (all values are in hex) | (II) PCI: 00:00:0: chip 8086,7122 card , rev 03 class 06,00,00 | hdr 00 | (II) PCI: 00:01:0: chip 8086,7123 card 8086,5355 rev 03 class 03,00,00 | hdr 00 | (II) PCI: 00:1e:0: chip 8086,2418 card , rev 02 class 06,04,00 | hdr 01 | (II) PCI: 00:1f:0: chip 8086,2410 card , rev 02 class 06,01,00 | hdr 80 | (II) PCI: 00:1f:1: chip 8086,2411 card 8086,2411 rev 02 class 01,01,80 | hdr 00 | (II) PCI: 00:1f:2: chip 8086,2412 card 8086,2412 rev 02 class 0c,03,00 | hdr 00 | (II) PCI: 00:1f:3: chip 8086,2413 card 8086,2413 rev
Re: X problems on i810 | AddScreen/ScreenInit failed
in which file you have made changes? from the logs, you are using ./XF86Config.new Make changes in that file. Regards, Shantanu +++ Darren Spruell [10-02-03 13:28 -0700]: | Date: Mon, 10 Feb 2003 13:28:42 -0700 | From: Darren Spruell <[EMAIL PROTECTED]> | User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 | To: Shantanu Mahajan <[EMAIL PROTECTED]> | CC: [EMAIL PROTECTED] | Subject: Re: X problems on i810 | AddScreen/ScreenInit failed | | Shantanu Mahajan wrote: | >try adding following lines | > | >in Device section | > Option "NoDDC" | > | >in Monitor section | > Option "DPMS" | > | >Regards, | >Shantanu | | Added as suggested. Relevant sections now read: | | Section "Monitor" | Identifier "Monitor0" | Option "DPMS" | VendorName "Gateway" | ModelName"EV700" | HorizSync30 - 69 | VertRefresh 50 - 110 | EndSection | | Section "Device" | ### Available Driver options are:- | ### Values: : integer, : float, : "True"/"False", | ### : "String", : " Hz/kHz/MHz" | ### [arg]: arg optional | #Option "ShadowFB" # [] | #Option "VGAClocks" # [] | Option "NoDDC" | Identifier "Card0" | Driver "vga" | VendorName "Intel" | BoardName "i810-dc100" | BusID "PCI:0:1:0" | EndSection | | | | Still the same error occurs. Here is the full output of the | /var/log/XFree86.0.log for this attempt: | | | | XFree86 Version 4.2.1 / X Window System | (protocol Version 11, revision 0, vendor release 6600) | Release Date: 3 September 2002 | If the server is older than 6-12 months, or if your card is | newer than the above date, look for a newer version before | reporting problems. (See http://www.XFree86.Org/) | Build Operating System: FreeBSD 5.0-CURRENT i386 [ELF] | Module Loader present | Markers: (--) probed, (**) from config file, (==) default setting, | (++) from command line, (!!) notice, (II) informational, | (WW) warning, (EE) error, (NI) not implemented, (??) unknown. | (==) Log file: "/var/log/XFree86.0.log", Time: Mon Feb 10 14:23:18 2003 | (++) Using config file: "./XF86Config.new" | (==) ServerLayout "XFree86 Configured" | (**) |-->Screen "Screen0" (0) | (**) | |-->Monitor "Monitor0" | (**) | |-->Device "Card0" | (**) |-->Input Device "Mouse0" | (**) |-->Input Device "Keyboard0" | (==) Keyboard: CustomKeycode disabled | (**) FontPath set to | |"/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts | /75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/" | (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" | (**) ModulePath set to "/usr/X11R6/lib/modules" | (--) Using syscons driver with X support (version 2.0) | (--) using VT number 9 | | (II) Module ABI versions: | XFree86 ANSI C Emulation: 0.1 | XFree86 Video Driver: 0.5 | XFree86 XInput driver : 0.3 | XFree86 Server Extension : 0.1 | XFree86 Font Renderer : 0.3 | (II) Loader running on freebsd | (II) LoadModule: "bitmap" | (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a | (II) Module bitmap: vendor="The XFree86 Project" | compiled for 4.2.1, module version = 1.0.0 | Module class: XFree86 Font Renderer | ABI class: XFree86 Font Renderer, version 0.3 | (II) Loading font Bitmap | (II) LoadModule: "pcidata" | (II) Loading /usr/X11R6/lib/modules/libpcidata.a | (II) Module pcidata: vendor="The XFree86 Project" | compiled for 4.2.1, module version = 0.1.0 | ABI class: XFree86 Video Driver, version 0.5 | (II) PCI: Probing config type using method 1 | (II) PCI: Config type is 1 | (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 | (II) PCI: PCI scan (all values are in hex) | (II) PCI: 00:00:0: chip 8086,7122 card , rev 03 class 06,00,00 | hdr 00 | (II) PCI: 00:01:0: chip 8086,7123 card 8086,5355 rev 03 class 03,00,00 | hdr 00 | (II) PCI: 00:1e:0: chip 8086,2418 card , rev 02 class 06,04,00 | hdr 01 | (II) PCI: 00:1f:0: chip 8086,2410 card , rev 02 class 06,01,00 | hdr 80 | (II) PCI: 00:1f:1: chip 8086,2411 card 8086,2411 rev 02 class 01,01,80 | hdr 00 | (II) PCI: 00:1f:2: chip 8086,2412 card 8086,2412 rev 02 class 0c,03,00 | hdr 00 | (II) PCI: 00:1f:3: chip 8086,2413 card 8086,2413 rev 02 class 0c,05,00 | hdr 00 | (II) PCI: 00:1f:5: chip 8086,2415 card 8086,5355 rev 02 class
Re: X problems on i810 | AddScreen/ScreenInit failed
To my knowledge, DRI extensions have never worked with i810 on FreeBSD. Whenever I felt tinkering with the config to see I could enable DRI, it wouldn't take, but I don't think it ever mucked up my screen. My video monitor did have some trouble with the DDC option (on my stable partition, just after I had upgraded the bios), but DDC seems to work ok now. If you do get it working, I would stay with a DefaultDepth of 16 instead of 24, as a setting of 24 tends to slow demanding apps down without noticeably improving picture quality. Notice also that the HorizSync and VertRefresh values are a tiny bit different on mine as well. Anyway, here's my 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/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" FontPath "/usr/X11R6/lib/X11/fonts/URW" EndSection Section "Module" Load "extmod" Load "xie" Load "pex5" #Load "dri" Load "ddc" #Load "glx" 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/sysmouse" Option "Resolution" "1200" Option "Buttons" "5" Option "ZAxisMapping" "4 5" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName"Monitor Model" HorizSync31.5 - 57.0 VertRefresh 50.0 - 100.0 EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz" ### [arg]: arg optional #Option "NoAccel" # [] #Option "SWcursor" # [] #Option "ColorKey" # #Option "CacheLines"# #Option "Dac6Bit" # [] #Option "DRI" # [] #Option "NoDDC" # [] #Option "XvMCSurfaces" "8" # Identifier "Card0" Driver "i810" VendorName "Intel" BoardName "i815" #VideoRam 1 #BusID "PCI:0:2:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor"Monitor0" DefaultDepth 16 SubSection "Display" Depth 24 Modes"1024x768" "800x600" "640x480" "320x240" EndSubSection SubSection "Display" Depth 16 Modes"1024x768" "800x600" "640x480" "320x240" EndSubSection SubSection "Display" Depth 8 Modes"1024x768" "800x600" "640x480" "320x240" EndSubSection EndSection To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: X problems on i810 | AddScreen/ScreenInit failed
My i815e wouldn't run until I did the following: NoDDC as an option. Configured horiz & vert according to monitor specs. Added agp into kernel configuration. Compiled new agp enabled kernel and installed it. NOTE: For a test I loaded the agp module and then ran X. NOTE2: I also took the generic XF86Config and edited by hand so I didn't have to use -configure. I don't know if this will help any but that's what I did. You might want to check your /dev/agpgart as well to make sure it exists. R. On Mon, 10 Feb 2003, Darren Spruell wrote: > Continuing on from my previous posting below, I have scoured some docs > to make some changes to the XF86Config: > > * Added Option "DPMS" to Monitor section (by suggestion of list member) > * Added Option "NoDDC" to Device section (by suggestion of list member) > * Changed Device section to now read as follows, from i810 man page... > (in short, was using the vga driver, changed to the i810 driver.) > > > Section "Device" > ### Available Driver options are:- > ### Values: : integer, : float, : "True"/"False", > ### : "String", : " Hz/kHz/MHz" > ### [arg]: arg optional > #Option "ShadowFB" # [] > #Option "VGAClocks" # [] > #VideoRam16 > Option "NoDDC" > Identifier "Intel i810" > Driver "i810" > VendorName "Intel" > BoardName "i810-dc100" > BusID "PCI:0:1:0" > EndSection > > The problem now is that when I run "XFree86 -xf86config > ./XF86Config.new", it looks like the X display is coming up but all it > shows me is a 1 inch by 1 inch white square surrounded by a screen of > staticy purplish, bluish, and greenish lines.. and stays. Desktop never > displays. > > The log file shows lines like this, with the following error: > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: open result is -1, (Unknown error: 999() > drmOpenDevice: Open failed > drmOpenDevice: minor is 1 > drmOpenDevice: node name is /dev/dri/card1 > drmOpenDevice: open result is -1, (Unknown error: 999() > drmOpenDevice: Open failed > [...] > drmOpenDevice: minor is 13 > drmOpenDevice: node name is /dev/dri/card13 > drmOpenDevice: open result is -1, (Unknown error: 999() > drmOpenDevice: Open failed > drmOpenDevice: minor is 14 > drmOpenDevice: node name is /dev/dri/card14 > drmOpenDevice: open result is -1, (Unknown error: 999() > drmOpenDevice: Open failed > drmOpenDevice: Open failed > (II) I810(0): [drm] drmOpen failed > (EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI. > > > Any other suggestions? > > > DS > > > > +++ Darren Spruell [freebsd] [10-02-03 11:07 -0700]: > > | Date: Mon, 10 Feb 2003 11:07:22 -0700 > > | From: Darren Spruell <[EMAIL PROTECTED]> > > | Subject: X problems on i810 | AddScreen/ScreenInit failed > > | > > | Greetz, > > | > > | I'm trying to configure v4.7 to run X but am having a hard time getting > > | the server to start. > > | > > | I've followed the config instructions at > > | http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html > > | by doing the following steps: > > | > > | Run XFree86 -configure > > | to create the default XF86Config.new > > | Run XFree86 -xf86config ./XF86Config.new > > | to ensure that it works w/my hardware > > | Edit it to taste, to change specifics for HorizSync, VertRefresh, and > > | the Display subsection under "Screen". > > | > > | However, running 'XFree86 -xf86config ./XF86Config.new' after changing > > | my config does not work. The output error is: > > | > > | == > > | (==) VGA(0): Write-combining range (0xa,0x1) was already clear > > | > > | Fatal server error: > > | AddScreen/ScreenInit failed for driver 0 > > | == > > | > > | I followed through the part in the Advanced Configuration section about > > | adding in support for agpgart and created the device node and added the > > | following to /boot/loader.conf: > > | agp_load="YES" > > | > > | dmesg now shows: > > | Preloaded elf module "agp.ko" at 0xc051a09c. > > | agp0: mem > > | 0xffa8-0xffaf,0xf800-0xfbff irq 11 at de
Re: X problems on i810 | AddScreen/ScreenInit failed
Continuing on from my previous posting below, I have scoured some docs to make some changes to the XF86Config: * Added Option "DPMS" to Monitor section (by suggestion of list member) * Added Option "NoDDC" to Device section (by suggestion of list member) * Changed Device section to now read as follows, from i810 man page... (in short, was using the vga driver, changed to the i810 driver.) Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz" ### [arg]: arg optional #Option "ShadowFB" # [] #Option "VGAClocks" # [] #VideoRam16 Option "NoDDC" Identifier "Intel i810" Driver "i810" VendorName "Intel" BoardName "i810-dc100" BusID "PCI:0:1:0" EndSection The problem now is that when I run "XFree86 -xf86config ./XF86Config.new", it looks like the X display is coming up but all it shows me is a 1 inch by 1 inch white square surrounded by a screen of staticy purplish, bluish, and greenish lines.. and stays. Desktop never displays. The log file shows lines like this, with the following error: drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (Unknown error: 999() drmOpenDevice: Open failed drmOpenDevice: minor is 1 drmOpenDevice: node name is /dev/dri/card1 drmOpenDevice: open result is -1, (Unknown error: 999() drmOpenDevice: Open failed [...] drmOpenDevice: minor is 13 drmOpenDevice: node name is /dev/dri/card13 drmOpenDevice: open result is -1, (Unknown error: 999() drmOpenDevice: Open failed drmOpenDevice: minor is 14 drmOpenDevice: node name is /dev/dri/card14 drmOpenDevice: open result is -1, (Unknown error: 999() drmOpenDevice: Open failed drmOpenDevice: Open failed (II) I810(0): [drm] drmOpen failed (EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI. Any other suggestions? DS +++ Darren Spruell [freebsd] [10-02-03 11:07 -0700]: | Date: Mon, 10 Feb 2003 11:07:22 -0700 | From: Darren Spruell <[EMAIL PROTECTED]> | Subject: X problems on i810 | AddScreen/ScreenInit failed | | Greetz, | | I'm trying to configure v4.7 to run X but am having a hard time getting | the server to start. | | I've followed the config instructions at | http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html | by doing the following steps: | | Run XFree86 -configure | to create the default XF86Config.new | Run XFree86 -xf86config ./XF86Config.new | to ensure that it works w/my hardware | Edit it to taste, to change specifics for HorizSync, VertRefresh, and | the Display subsection under "Screen". | | However, running 'XFree86 -xf86config ./XF86Config.new' after changing | my config does not work. The output error is: | | == | (==) VGA(0): Write-combining range (0xa,0x1) was already clear | | Fatal server error: | AddScreen/ScreenInit failed for driver 0 | == | | I followed through the part in the Advanced Configuration section about | adding in support for agpgart and created the device node and added the | following to /boot/loader.conf: | agp_load="YES" | | dmesg now shows: | Preloaded elf module "agp.ko" at 0xc051a09c. | agp0: mem | 0xffa8-0xffaf,0xf800-0xfbff irq 11 at device 1.0 on pci0 | | Here is the current XF86Config.new (non-working). The Monitor section | was taken from a specs page on the Monitor (Gateway EV700). Full dmesg | included below this: | | 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/75dpi/" | FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" | EndSection | | Section "Module" | Load "dbe" | Load "dri" | Load "extmod" | Load "glx" | Load "pex5" | Load "record" | Load "xie" |
Re: X problems on i810 | AddScreen/ScreenInit failed
0x8000) MS[B](OprU) [13] 0 0x000b8000 - 0x000b (0x8000) MS[B](OprU) [14] -1 0x - 0x (0x1) IX[B] [15] -1 0x - 0x00ff (0x100) IX[B] [16] -1 0xdf00 - 0xdfff (0x100) IX[B]E [17] -1 0xef00 - 0xef7f (0x80) IX[B]E [18] -1 0xe800 - 0xe8ff (0x100) IX[B]E [19] -1 0xefa0 - 0xefbf (0x20) IX[B]E [20] -1 0xef80 - 0xef9f (0x20) IX[B]E [21] -1 0xffa0 - 0xffbf (0x20) IX[B]E [22] 0 0x03b0 - 0x03bb (0xc) IS[B] [23] 0 0x03c0 - 0x03df (0x20) IS[B] (==) VGA(0): Write-combining range (0xa,0x1) was already clear Fatal server error: AddScreen/ScreenInit failed for driver 0 When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file "/var/log/XFree86.0.log". Please report problems to [EMAIL PROTECTED] +++ Darren Spruell [freebsd] [10-02-03 11:07 -0700]: | Date: Mon, 10 Feb 2003 11:07:22 -0700 | From: Darren Spruell <[EMAIL PROTECTED]> | Subject: X problems on i810 | AddScreen/ScreenInit failed | | Greetz, | | I'm trying to configure v4.7 to run X but am having a hard time getting | the server to start. | | I've followed the config instructions at | http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html | by doing the following steps: | | Run XFree86 -configure | to create the default XF86Config.new | Run XFree86 -xf86config ./XF86Config.new | to ensure that it works w/my hardware | Edit it to taste, to change specifics for HorizSync, VertRefresh, and | the Display subsection under "Screen". | | However, running 'XFree86 -xf86config ./XF86Config.new' after changing | my config does not work. The output error is: | | == | (==) VGA(0): Write-combining range (0xa,0x1) was already clear | | Fatal server error: | AddScreen/ScreenInit failed for driver 0 | == | | I followed through the part in the Advanced Configuration section about | adding in support for agpgart and created the device node and added the | following to /boot/loader.conf: | agp_load="YES" | | dmesg now shows: | Preloaded elf module "agp.ko" at 0xc051a09c. | agp0: mem | 0xffa8-0xffaf,0xf800-0xfbff irq 11 at device 1.0 on pci0 | | Here is the current XF86Config.new (non-working). The Monitor section | was taken from a specs page on the Monitor (Gateway EV700). Full dmesg | included below this: | | 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/75dpi/" | FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" | EndSection | | Section "Module" | Load "dbe" | Load "dri" | Load "extmod" | Load "glx" | Load "pex5" | Load "record" | Load "xie" | Load "xtrap" | Load "speedo" | Load "type1" | EndSection | | Section "InputDevice" | Identifier "Keyboard0" | Driver "keyboard" | EndSection | | Section "InputDevice" | Identifier "Mouse0" | Driver "mouse" | Option "Protocol" "MouseSystems" | Option "Device" "/dev/sysmouse" | EndSection | | Section "Monitor" | Identifier "Monitor0" | VendorName "Gateway" | ModelName"EV700" | HorizSync30 - 69 | VertRefresh 50 - 110 | EndSection | | Section "Device" | ### Available Driver options are:- | ### Values: : integer, : float, : "True"/"False", | ### : "String", : " Hz/kHz/MHz" | ### [arg]: arg optional | #Option "ShadowFB" # [] | #Option "VGAClocks" # [] | Identifier "Card0" |
Re: X problems on i810 | AddScreen/ScreenInit failed
try adding following lines in Device section Option "NoDDC" in Monitor section Option "DPMS" Regards, Shantanu +++ Darren Spruell [freebsd] [10-02-03 11:07 -0700]: | Date: Mon, 10 Feb 2003 11:07:22 -0700 | From: Darren Spruell <[EMAIL PROTECTED]> | Subject: X problems on i810 | AddScreen/ScreenInit failed | | Greetz, | | I'm trying to configure v4.7 to run X but am having a hard time getting | the server to start. | | I've followed the config instructions at | http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html | by doing the following steps: | | Run XFree86 -configure | to create the default XF86Config.new | Run XFree86 -xf86config ./XF86Config.new | to ensure that it works w/my hardware | Edit it to taste, to change specifics for HorizSync, VertRefresh, and | the Display subsection under "Screen". | | However, running 'XFree86 -xf86config ./XF86Config.new' after changing | my config does not work. The output error is: | | == | (==) VGA(0): Write-combining range (0xa,0x1) was already clear | | Fatal server error: | AddScreen/ScreenInit failed for driver 0 | == | | I followed through the part in the Advanced Configuration section about | adding in support for agpgart and created the device node and added the | following to /boot/loader.conf: | agp_load="YES" | | dmesg now shows: | Preloaded elf module "agp.ko" at 0xc051a09c. | agp0: mem | 0xffa8-0xffaf,0xf800-0xfbff irq 11 at device 1.0 on pci0 | | Here is the current XF86Config.new (non-working). The Monitor section | was taken from a specs page on the Monitor (Gateway EV700). Full dmesg | included below this: | | 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/75dpi/" | FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" | EndSection | | Section "Module" | Load "dbe" | Load "dri" | Load "extmod" | Load "glx" | Load "pex5" | Load "record" | Load "xie" | Load "xtrap" | Load "speedo" | Load "type1" | EndSection | | Section "InputDevice" | Identifier "Keyboard0" | Driver "keyboard" | EndSection | | Section "InputDevice" | Identifier "Mouse0" | Driver "mouse" | Option "Protocol" "MouseSystems" | Option "Device" "/dev/sysmouse" | EndSection | | Section "Monitor" | Identifier "Monitor0" | VendorName "Gateway" | ModelName"EV700" | HorizSync30 - 69 | VertRefresh 50 - 110 | EndSection | | Section "Device" | ### Available Driver options are:- | ### Values: : integer, : float, : "True"/"False", | ### : "String", : " Hz/kHz/MHz" | ### [arg]: arg optional | #Option "ShadowFB" # [] | #Option "VGAClocks" # [] | Identifier "Card0" | Driver "vga" | VendorName "Intel" | BoardName "i810-dc100" | BusID "PCI:0:1:0" | EndSection | | Section "Screen" | Identifier "Screen0" | Device "Card0" | Monitor"Monitor0" | DefaultDepth 16 | SubSection "Display" | Depth 16 | Modes "1024x768" | EndSubSection | EndSection | | Copyright (c) 1992-2002 The FreeBSD Project. | Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 | The Regents of the University of California. All rights reserved. | FreeBSD 4.7-RELEASE #0: Wed Oct 9 15:08:34 GMT 2002 | [EMAIL PROTECTED]:/us
X problems on i810 | AddScreen/ScreenInit failed
Greetz, I'm trying to configure v4.7 to run X but am having a hard time getting the server to start. I've followed the config instructions at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html by doing the following steps: Run XFree86 -configure to create the default XF86Config.new Run XFree86 -xf86config ./XF86Config.new to ensure that it works w/my hardware Edit it to taste, to change specifics for HorizSync, VertRefresh, and the Display subsection under "Screen". However, running 'XFree86 -xf86config ./XF86Config.new' after changing my config does not work. The output error is: == (==) VGA(0): Write-combining range (0xa,0x1) was already clear Fatal server error: AddScreen/ScreenInit failed for driver 0 == I followed through the part in the Advanced Configuration section about adding in support for agpgart and created the device node and added the following to /boot/loader.conf: agp_load="YES" dmesg now shows: Preloaded elf module "agp.ko" at 0xc051a09c. agp0: mem 0xffa8-0xffaf,0xf800-0xfbff irq 11 at device 1.0 on pci0 Here is the current XF86Config.new (non-working). The Monitor section was taken from a specs page on the Monitor (Gateway EV700). Full dmesg included below this: 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/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" EndSection Section "Module" Load "dbe" Load "dri" Load "extmod" Load "glx" Load "pex5" Load "record" Load "xie" Load "xtrap" Load "speedo" Load "type1" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "MouseSystems" Option "Device" "/dev/sysmouse" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Gateway" ModelName"EV700" HorizSync30 - 69 VertRefresh 50 - 110 EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz" ### [arg]: arg optional #Option "ShadowFB" # [] #Option "VGAClocks" # [] Identifier "Card0" Driver "vga" VendorName "Intel" BoardName "i810-dc100" BusID "PCI:0:1:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor"Monitor0" DefaultDepth 16 SubSection "Display" Depth 16 Modes "1024x768" EndSubSection EndSection Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.7-RELEASE #0: Wed Oct 9 15:08:34 GMT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (697.88-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383f9ff real memory = 267124736 (260864K bytes) avail memory = 254693376 (248724K bytes) Preloaded elf kernel "kernel" at 0xc051a000. Preloaded elf module "agp.ko" at 0xc051a09c. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 11 entries at 0xc00f35a0 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 agp0: mem 0xffa8-0xffaf,0xf800-0xfbff irq 11 at device 1.0 on pci0 pcib1: at device 30.0 on pci0 pci1: on pcib1 fxp0: port 0xdf00-0xdf3f mem 0xff70-0xff7f,0xff8ff000-0xff8f irq 3 at device 1.0 on pci1 fxp0: Ethernet address 00:03:47:0b:0e:20 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xef80-0xef9f irq 10 at device 31.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: (ven
Remote X Problems
Hi all. I'm having more problems getting this X app to run remotely. Whenever Xmanager tries to run it, it gives me the error "No xauth program; cannot forward with spoofing.wl Failed.", and the only way it seams to work is if I install XFree86-4. Does anyone know if there is a way around this? Thanks, --Brian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: X problems, please advise helpless newbie
Thanos Tsouanas <[EMAIL PROTECTED]> writes: > i have followed the instructions on the HB and they didnt work, thats why i came up >with the > insecure method... startx gives similar errors to the ones mentioned in the original >msg. > any ideas why? You can get better control over what's going on by avoiding "startx". I use something like this (in a script which keeps root from using X): /usr/X11R6/bin/xinit ~/.xinitrc -- /usr/X11R6/bin/Xwrapper-4 You should try omiting the second filename after ensuring that you don't have that file (the default) and X should start up an xterm. That Xwrapper-4 comes from the "x11/wrapper" package/port; it's used to run X with non-root privileges and it expects your XF86Config to say which X server module is to be used, etc. You can probably start a window manager by using it's filename instead of ~/.xinitrc, but most people use a file like that modeled on /usr/X11R6/lib/X11/xinit/xinitrc After you know that X will start, you can just start X after booting to text mode like many people prefer to do, or go back and learn how to configure one of the xdm/gdm/kdm gizmos at your leisure. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: X problems, please advise helpless newbie
At 02:09 PM 10/17/2002, RichardH wrote: Are you root when doing the start commands? If you are not root you need to install the wrapper so other users can use X. /usr/ports/x11/wrapper Richard H AHHH, sorry for top posting. RH To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: X problems, please advise helpless newbie
Are you root when doing the start commands? If you are not root you need to install the wrapper so other users can use X. /usr/ports/x11/wrapper Richard H At 12:55 PM 10/17/2002, Thanos Tsouanas wrote: > > wud it be better to comment out all the ttyv8 lines and start XFree86 as a normal user, and > then > > start windowmaker? > > > > i really cant make xdm to work... > > any suggestions? > > > > There's a thorough HowTo on setting up a display manager (e.g. xdm, kdm, > ...) here: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-xdm.html > > I can't think of any reason why it won't work if you follow the > instructions. Note that X *must* load properly for xdm to work properly. > If you need to test and setup X first, use an xinitrc file, e.g.: > > $ echo "exec wmaker" > /home/user/.xinitrc > > and then try 'startx'. The Handbook page above should get you going with > xdm. > i have followed the instructions on the HB and they didnt work, thats why i came up with the insecure method... startx gives similar errors to the ones mentioned in the original msg. any ideas why? __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: X problems, please advise helpless newbie
> > wud it be better to comment out all the ttyv8 lines and start XFree86 as a normal >user, and > then > > start windowmaker? > > > > i really cant make xdm to work... > > any suggestions? > > > > There's a thorough HowTo on setting up a display manager (e.g. xdm, kdm, > ...) here: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-xdm.html > > I can't think of any reason why it won't work if you follow the > instructions. Note that X *must* load properly for xdm to work properly. > If you need to test and setup X first, use an xinitrc file, e.g.: > > $ echo "exec wmaker" > /home/user/.xinitrc > > and then try 'startx'. The Handbook page above should get you going with > xdm. > i have followed the instructions on the HB and they didnt work, thats why i came up with the insecure method... startx gives similar errors to the ones mentioned in the original msg. any ideas why? __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: X problems, please advise helpless newbie
wud it be better to comment out all the ttyv8 lines and start XFree86 as a normal user, and then start windowmaker? i really cant make xdm to work... any suggestions? __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: X problems, please advise helpless newbie
On Thu, 17 Oct 2002, Thanos Tsouanas wrote: > Date: Thu, 17 Oct 2002 10:33:07 -0700 (PDT) > From: Thanos Tsouanas <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: X problems, please advise helpless newbie > > wud it be better to comment out all the ttyv8 lines and start XFree86 as a normal >user, and then > start windowmaker? > > i really cant make xdm to work... > any suggestions? > There's a thorough HowTo on setting up a display manager (e.g. xdm, kdm, ...) here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-xdm.html I can't think of any reason why it won't work if you follow the instructions. Note that X *must* load properly for xdm to work properly. If you need to test and setup X first, use an xinitrc file, e.g.: $ echo "exec wmaker" > /home/user/.xinitrc and then try 'startx'. The Handbook page above should get you going with xdm. HTH - JB # John Bleichert # http://vonbek.dhs.org/latest.jpg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: X problems, please advise helpless newbie
-Original Message- From: Thanos Tsouanas <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Date: Thu, 17 Oct 2002 10:33:07 -0700 (PDT) Subject: Re: X problems, please advise helpless newbie wud it be better to comment out all the ttyv8 lines and start XFree86 as a normal user, and then start windowmaker? i really cant make xdm to work... any suggestions? * * Yes - it's often easier to go with a .xinitrc file and type "startx" at the login prompt. There's a good article by Dru Lavigne on how to set this up: http://www.onlamp.com/pub/a/bsd/2000/06/21/FreeBSD_Basics.html Jud To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: X problems, please advise helpless newbie
wud it be better to comment out all the ttyv8 lines and start XFree86 as a normal user, and then start windowmaker? i really cant make xdm to work... any suggestions? __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Re: X problems, please advise helpless newbie
# [EMAIL PROTECTED] / 2002-10-17 08:09:27 -0700: > On Thu, Oct 17, 2002 at 03:37:38PM +0200, Roman Neuhauser wrote: > > # [EMAIL PROTECTED] / 2002-10-17 08:38:26 -0400: > > > On Thu, Oct 17, 2002 at 01:24:43AM -0700, J. Foobar wrote: > > > > 'startx' returns the following: > > > > > > > > > > > > (EE) GARTInit: Unable to open /dev/agpgart (Device not > > > > configured) > > > > (EE) I810(0): AGP GART support is not available. Make > > > > sure your kernel has agpgart support or that the > > > > agpgart kernel module is loaded. > > ^^^ > > > > > have you checked for agpgard support in your kernel as mentioned > > > above in the startx output? > > > > > > Add the following to your kernel - > > > > > > device agp > > > > > > Then recompile your kernel. > > > > % su > > # echo agp_load="YES" >> /boot/loader.conf > > # kldload agp > > # exit > > % startx > > > > enjoy > > > > Wait, do you have to both compile AGP support into the kernel AND load > an the kernel module? Shouldn't it be just one or the other? sorry for the confusion. this is what I meant: as opposed to what quite a few people would like you to believe you *don't* have to compile stuff into kernel to have the desired functionality. i've successfully used dynamically loaded usb, agp, and sound (at least two different sound cards) support over the last year. -- If you cc me or take the list(s) out completely I'll most likely ignore your message. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: X problems, please advise helpless newbie
On Thu, Oct 17, 2002 at 08:25:27AM -0700, Thanos Tsouanas wrote: > comment out the line that starts xdm -nodaemon > and add a similar one to start the XFree86 > > sth like > > ttyv8 "/usr/X11R6/bin/XFree86" xterm on secure > > this shud result in X starting every time you start your system with the X-mouse >screen and the > pixel-chessboard background. Whoa! Bad karma. Doing this will result in an X session running as root which anyone can just walk up to your machine and use. You really, really don't want to do that. Honestly, this is exactly why xdm(1) exists. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: X problems, please advise helpless newbie
had similar problems... if you dont mind starting your wmanager manually, without using xdm or similar programs, try adding sth like this to your /etc/ttys files... comment out the line that starts xdm -nodaemon and add a similar one to start the XFree86 sth like ttyv8 "/usr/X11R6/bin/XFree86" xterm on secure this shud result in X starting every time you start your system with the X-mouse screen and the pixel-chessboard background. make a small script to start your wmanager in your home dir #!/bin/sh /usr/X11R6/bin/wmaker -display :0 (thats for me, i use windowmaker, add there what you wud normally add to .xinitrc or .xsession) chmod +x filename_to_start_window_manager shud work... __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Re: X problems, please advise helpless newbie
On Thu, Oct 17, 2002 at 03:37:38PM +0200, Roman Neuhauser wrote: > # [EMAIL PROTECTED] / 2002-10-17 08:38:26 -0400: > > On Thu, Oct 17, 2002 at 01:24:43AM -0700, J. Foobar wrote: > > > 'startx' returns the following: > > > > > > > > > (EE) GARTInit: Unable to open /dev/agpgart (Device not > > > configured) > > > (EE) I810(0): AGP GART support is not available. Make > > > sure your kernel has agpgart support or that the > > > agpgart kernel module is loaded. > ^^^ > > > have you checked for agpgard support in your kernel as mentioned > > above in the startx output? > > > > Add the following to your kernel - > > > > device agp > > > > Then recompile your kernel. > > % su > # echo agp_load="YES" >> /boot/loader.conf > # kldload agp > # exit > % startx > > enjoy > Wait, do you have to both compile AGP support into the kernel AND load an the kernel module? Shouldn't it be just one or the other? Nathan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: X problems, please advise helpless newbie
On Thu, Oct 17, 2002 at 01:24:43AM -0700, J. Foobar wrote: > I have been unable to get X to start successfully. > Hopefully I am overlooking something stupid. > > FreeBSD 4.6.2 on an Intel machine > > My graphics card is an Intel 82845G/GL. I searched > for info on the Intel site and it mentioned that this > card is in the i810 class. > > >From my XF86Config file: > Section "Device" > Identifier "Card0" > Driver "i810" > Chipset "i810" > Card"Intel i810" > End Section > > I have added the agp_load="YES" line to > /boot/loader.conf and /dev/agpgart exists. > > 'startx' returns the following: > > > (EE) GARTInit: Unable to open /dev/agpgart (Device not > configured) > (EE) I810(0): AGP GART support is not available. Make > sure your kernel has agpgart support or that the > agpgart kernel module is loaded. > (EE) Screen(s) found, but none have a usable > configuration. > > Fatal server error: > no screens found > > > > X connection to :0.0 broken (explicit kill or server > shutdown) > xauth: creating new authority file /root/.Xauthority > xauth: (argv:1: bad dusplay name in ":0" in "remove" > command > xauth: (argv:1: bad dusplay name in ":0" in "remove" > command > > > I really have no idea what to do next. Any help would > be appreciated, the more layman the terms, the better. > > Thanks, > Justin Have you run `kldstat' (man kldstat) to make sure that the AGP module is actually loaded? Nathan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Re: X problems, please advise helpless newbie
# [EMAIL PROTECTED] / 2002-10-17 08:38:26 -0400: > On Thu, Oct 17, 2002 at 01:24:43AM -0700, J. Foobar wrote: > > 'startx' returns the following: > > > > > > (EE) GARTInit: Unable to open /dev/agpgart (Device not > > configured) > > (EE) I810(0): AGP GART support is not available. Make > > sure your kernel has agpgart support or that the > > agpgart kernel module is loaded. ^^^ > have you checked for agpgard support in your kernel as mentioned > above in the startx output? > > Add the following to your kernel - > > device agp > > Then recompile your kernel. % su # echo agp_load="YES" >> /boot/loader.conf # kldload agp # exit % startx enjoy -- If you cc me or take the list(s) out completely I'll most likely ignore your message. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: X problems, please advise helpless newbie
On Thu, Oct 17, 2002 at 01:24:43AM -0700, J. Foobar wrote: > I have been unable to get X to start successfully. > Hopefully I am overlooking something stupid. > > FreeBSD 4.6.2 on an Intel machine > > My graphics card is an Intel 82845G/GL. I searched > for info on the Intel site and it mentioned that this > card is in the i810 class. > > >From my XF86Config file: > Section "Device" > Identifier "Card0" > Driver "i810" > Chipset "i810" > Card"Intel i810" > End Section > > I have added the agp_load="YES" line to > /boot/loader.conf and /dev/agpgart exists. > > 'startx' returns the following: > > > (EE) GARTInit: Unable to open /dev/agpgart (Device not > configured) > (EE) I810(0): AGP GART support is not available. Make > sure your kernel has agpgart support or that the > agpgart kernel module is loaded. > (EE) Screen(s) found, but none have a usable > configuration. > > Fatal server error: > no screens found > have you checked for agpgard support in your kernel as mentioned above in the startx output? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: Re: X problems, please advise helpless newbie
-Original Message- From: Thomas Spreng <[EMAIL PROTECTED]> To: "J. Foobar" <[EMAIL PROTECTED]> Date: Thu, 17 Oct 2002 13:27:30 +0200 Subject: Re: X problems, please advise helpless newbie On Thu, Oct 17, 2002 at 01:24:43AM -0700, J. Foobar wrote: > I have been unable to get X to start successfully. > Hopefully I am overlooking something stupid. > > FreeBSD 4.6.2 on an Intel machine > > My graphics card is an Intel 82845G/GL. I searched > for info on the Intel site and it mentioned that this > card is in the i810 class. > > >From my XF86Config file: > Section "Device" > Identifier "Card0" > Driver "i810" > Chipset "i810" > Card"Intel i810" > End Section > > I have added the agp_load="YES" line to > /boot/loader.conf and /dev/agpgart exists. > > 'startx' returns the following: > > > (EE) GARTInit: Unable to open /dev/agpgart (Device not > configured) > (EE) I810(0): AGP GART support is not available. Make > sure your kernel has agpgart support or that the > agpgart kernel module is loaded. > (EE) Screen(s) found, but none have a usable > configuration. > > Fatal server error: > no screens found > have you checked for agpgard support in your kernel as mentioned above in the startx output? ** ** Add the following to your kernel - device agp You can add some comments if you like - # Video device agp #Graphics card Then recompile your kernel. If it still doesn't work, I guess something else is borked. I usually have my best success configuring X using the old-fashioned xf86config command and working through the subsequent question-and-answer. Jud To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
X problems, please advise helpless newbie
I have been unable to get X to start successfully. Hopefully I am overlooking something stupid. FreeBSD 4.6.2 on an Intel machine My graphics card is an Intel 82845G/GL. I searched for info on the Intel site and it mentioned that this card is in the i810 class. >From my XF86Config file: Section "Device" Identifier "Card0" Driver "i810" Chipset "i810" Card"Intel i810" End Section I have added the agp_load="YES" line to /boot/loader.conf and /dev/agpgart exists. 'startx' returns the following: (EE) GARTInit: Unable to open /dev/agpgart (Device not configured) (EE) I810(0): AGP GART support is not available. Make sure your kernel has agpgart support or that the agpgart kernel module is loaded. (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found X connection to :0.0 broken (explicit kill or server shutdown) xauth: creating new authority file /root/.Xauthority xauth: (argv:1: bad dusplay name in ":0" in "remove" command xauth: (argv:1: bad dusplay name in ":0" in "remove" command I really have no idea what to do next. Any help would be appreciated, the more layman the terms, the better. Thanks, Justin __ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
