Re: question about my new Dell 3010
On 10/12/2012 00:31, Gary Kline wrote: > On Sun, Dec 09, 2012 at 08:38:06AM +, Matthew Seaman wrote: >> > On 09/12/2012 00:23, Gary Kline wrote: >>> > > one of the remaining problems --hopefuully the Last-- with my >>> > > Dell 3010 quad i5 is that the resolution stops at 5:4. it's >>> > > something like 1280x1014 whereas my widescreen Dell needs >>> > > 1920x1280 or close to that. do I need to go out and find a >>> > > videocard? or is there a way of taking my 6GB of RAM and >>> > > giving >>> > > it to the video? >> > Do you have a DVI connector on your current graphics card, or just the >> > old style VGA connector? Pretty much all modern widescreen monitors >> > will have a DVI connector as well as the legacy VGA. > actually, I have both. the KVM dates from 2010 and came with > four cables and eight plugs. Ahah! You're using a KVM switch. That can block the monitor from sending its configuration information to the X server. It's easy to tell: just try connecting directly to the monitor temporarily. If that works, you can use xrandr to extract the monitor details, write a mode line for your xorg.conf and put the KVM back in the loop, while keeping the optimum configuration. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: question about my new Dell 3010
On Sun, 9 Dec 2012 17:00:17 -0800, Gary Kline wrote: > On Mon, Dec 10, 2012 at 12:08:38AM +, james wrote: > > Are you sure you mean 1920x1280??? > > > > I mean: 1280*800, or 1920*1200, those are more normal. (My older > > portables have the former, my Dell 24" has the latter) > > > > I can believe 1920x1280 might cause problems. > > > > > > I sent a screen shot, snapshot7.png. > > ill resend with this mail. Both the content and the dimensions of the screenshot say it's 1920x1080. If the phsyical display has a different size (measured in pixels), it should communicate that fact to X, and as long as X loads the proper driver (maybe the Intel GPU driver? - has to match what's installed on your mainboard or in your machine!) the correct screen size should be initialized, at least _for_ X. Note that problems might occur _prior_ to X due to KMS (kernel mode switching) which can happen to have less good support. Also from the content of the screenshot, it's visible that the display is connected via VGA. That's sub-optimum. If possible, connect per DVI cable, so it stays "all digital all the time". Even though both VGA and DVI have a "data channel" to transmit data (like monitor pixel size) to the GPU, DVI seems to be the preferred solution for flatpanels, especially wide ones. 1920x1080 is already widescreen. Does it match the size description of the physical monitor, or should it be something different? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: question about my new Dell 3010
On Sun, Dec 09, 2012 at 08:38:06AM +, Matthew Seaman wrote: > On 09/12/2012 00:23, Gary Kline wrote: > > > one of the remaining problems --hopefuully the Last-- with my > > Dell 3010 quad i5 is that the resolution stops at 5:4. it's > > something like 1280x1014 whereas my widescreen Dell needs > > 1920x1280 or close to that. do I need to go out and find a > > videocard? or is there a way of taking my 6GB of RAM and giving > > it to the video? > > Do you have a DVI connector on your current graphics card, or just the > old style VGA connector? Pretty much all modern widescreen monitors > will have a DVI connector as well as the legacy VGA. actually, I have both. the KVM dates from 2010 and came with four cables and eight plugs. > If you don't know what those are, see this page: > > https://en.wikipedia.org/wiki/File:DVI_Connector_Types.svg > > Most DVI monitor cables have a DVI-D dual link plug on them, but > anything matching those patterns is proof positive of DVI. > > VGA connectors looks like this: > > https://en.wikipedia.org/wiki/File:Vga-cable.jpg > > Anyhow, the point is if you're using a DVI connector, X will be able to > query the monitor and find out its preferred resolution etc. > automatically. Whereas with a VGA connector, it will default to using > one of the standard VGA series of resolutions. All monitors will > support some sort of VGA resolution for backwards compatibility -- > typically 1024x768@60Hz -- and many will support higher, but all of the > VGA series resolutions are 4:3 aspect ratio which doesn't look very nice > on a widescreen monitor. > > There's two ways to fix the problem. > > 1) Get a video card with a DVI connector, or at least a DVI-to-DVI > monitor cable if your card already has that. Apart from the > hassle of getting a new video card that will work happily with X, > this should be pretty painfree. > > 2) Edit your Xorg.conf to add a custom mode that matches what your > monitor expects. Back in the days of CRTs this was a potentially > risky thing to do, as configuring the video mode wrongly could > phsically damage your monitor. Modern flatscreens however will > just put up a message saying the input is incompatible. > > Working out what the right parameters are to put in the mode definition > is the tricky bit. You may be able to use xrandr to pull them out (but > if xrandr could do it, then X would do it automatically too...) There > should be documentation that comes with the monitor, or you may find a > kind soul online with the same make and model of monitor who will send > you some xrandr output. here's the Whole story. last summer I dedided to switch to all linux`in order to make upgrades simple[r]. since my brother engineer [a retired ME] was too ill to help i hired a technician. my "old-tao" (a homebrew AMD quad-CPU) had a broken USB. this was how I realized that the USB was broken. with a new KVM the home-brew still failed. I could ssh to<-> from, but not watch it boot. So I finally decided it was time to buys another Dell, new. somebody gave me a used Dell dual. my server is a new dual from '09. used and refurb'd and home-brew is not the optimal way. so my tech said he would look for the best Dell quad he could find, and after 6 weeeks he brought over the 3010. [fact: this chap is self-taught. but he got me a new kvm and blindly pluged things together.]] whether the 3010 has ye-olden VGA jack =plus= the DVI, I dont know. my guess is that the technician knows the diff. nutshell, looks like whatever ghaphic chipset the computer had maxes out a 5:4 screen-size ratio. I =will= try adding the mode line info. thanks, gary > Cheers, > > Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. > PGP: http://www.infracaninophile.co.uk/pgpkey > > -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Twenty-six years of service to the Unix community. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: question about my new Dell 3010
On Sat, Dec 08, 2012 at 07:21:17PM -0800, per...@pluto.rain.com wrote: > Gary Kline wrote: > > > one of the remaining problems --hopefuully the Last-- with my > > Dell 3010 quad i5 is that the resolution stops at 5:4. it's > > something like 1280x1014 ... > > Probably 1280x1024 -- a common size before widescreen. > The largest commonly seen back then was 1600x1200. > > > ... whereas my widescreen Dell needs 1920x1280 or close to that. > > Probably 1920x1200. see enclose snapshot. I was right. nonetheless, howi get that here on my old deall dual and do not on my dell quad is the mystery. > > > do I need to go out and find a videocard? or is there a way of > > taking my 6GB of RAM and giving it to the video? > > Dunno about currently-supported versions, nor your particular > display hardware, but 1920x1200 works for me on an ancient Dell > Optiplex GX1 with ATI Mach64 under 6.1. Maybe something in the > (attached) conf and/or log will help. I'll check, thanks. I had linux as my "desktop" --and the worst of the bunch, IMO, fedora. have to use locate to find the Xorg stuff. /* I wonder if the 1900 line isn't there and commented ... hmm. */ > 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/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 "type1" > EndSection > > Section "InputDevice" > Identifier "Keyboard0" > Driver "kbd" > EndSection > > Section "InputDevice" > Identifier "Mouse0" > Driver "mouse" > Option "Protocol" "auto" > Option "Device" "/dev/psm0" > Option "ZAxisMapping" "4 5 6 7" > EndSection > > Section "Monitor" > #DisplaySize 520 320 # mm > Identifier "Monitor0" > VendorName "IQT" > ModelName"HDIT24W DSUB" > ### Comment all HorizSync and VertSync values to use DDC: > HorizSync31.0 - 83.0 > VertRefresh 59.0 - 76.0 > # Modelines that actually worked on the BTC LM-1702, for reference. The > first is known > # to also work on the IQT (Hyundai) HDIT24W, but it is stretched in the X > dimension. > # Modeline "1280x1024" 108.00 1280 1328 1440 1688 1024 1025 1028 1066 > +hsync +vsync > # Modeline "1024x768"65.00 1024 1048 1184 1344 768 771 777 806 > -hsync -vsync > # Modeline "800x600"40.00 800 840 968 1056 600 601 605 628 > +hsync +vsync > # Modeline "640x480"25.20 640 656 752 800 480 490 492 525 > -hsync -vsync > > # Modeline reported as working (via DVI) on a 24" Eizo FlexScan: > # Modeline "1920x1200" 162.00 1920 1968 2000 2080 1200 1203 1209 1235 > +HSync -Vsync > > # Modelines implied by Xorg.0.log, but not reported by autoconf, for > # the HDIT24W (aka IQT 9001, IQT => ImageQuest, www.imagequest.co.kr) > #+W => wider aspect ratio than (HDIT24W native) 1920x1200 > > Modeline "1920x1200" 154.128 1920 1968 2000 2080 1200 1203 1209 1235 > +hsync +vsync > #+W Modeline "1920x1080" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 > > # Widescreen resolutions claimed as supported in Xorg.0.log, but no details > given: > # Modeline "1680x1050" > # Modeline "1440x900" > #+W Modeline "720x400" > > # Other widescreen resolutions of the same aspect ratio as 1920x1200: > # Modeline "1600x1000" > # Modeline "1280x800" > # Modeline "1229x768" > # Modeline "960x600" > # Modeline "720x450" > # Modeline "640x400" > > # Modelines reported by autoconf for the HDIT24W -- these are not widescreen: > # Modeline "1792x1344" 204.80 1792 1920 2120 2448 1344 1345 1348 1394 > -hsync +vsync > # Modeline "1600x1200" 175.50 1600 1664 1856 2160 1200 1201 1204 1250 > +hsync +vsync > # Modeline "1600x1200" 162.00 1600 1664 1856 2160 1200 1201 1204 1250 > +hsync +vsync > # Modeline "1400x1050" 155.80 1400 1464 1784 1912 1050 1052 1064 1090 > +hsync +vsync > # Modeline "1400x1050" 122.00 1400 1488 1640 1880 1050 1052 1064 1082 > +hsync +vsync > # Modeline "1280x1024" 135.00 1280 1296 1440 1688 1024 1025 1028 1066 > +hsync +vsync > # Modeline "1280x1024" 108.00 1280 1328 1440
Re: Stickers
"CONNOR KELLY (RIT Student)" wrote: > I am a student at Rochester Institute of Technology. I was wondering if > you could send any stickers or swag with the freebsd logo or something > similar to me. I would probably keep some for myself and pass the rest out > to my friends at my university. This is in no way an official > communication from my school. If need be I'll be able to pay for postage. questions@ is wrong list, ask on advocacy@ questions@ & advocacy@ are not some company who pay for labels to be printed & posted Ask your nearest BSD users group who may have some, _wherever in the world you are_. ( BTW real Rochester is on river Medway in Kent, England, Europe. ) Free stickers are included from some vendors of FreeBSD CDs & DVDs explore http://freebsd.org/ You could arrange a print production run & sell surplus. To explore that, post a proposal to advocacy@. (Others have done productions of [Free]BSD lapel pins & stuffed animals & CDs etc & they are pointed to from http://freebsd.org/ try contacting vendors either to purchase, or to arrange a print run where you could sell surplus to them to sell on. Cheers, Julian - -- Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com Reply below not above, like a play script. Indent old text with "> ". Send plain text. Not: HTML, multipart/alternative, base64, quoted-printable. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: question about my new Dell 3010
Are you sure you mean 1920x1280??? I mean: 1280*800, or 1920*1200, those are more normal. (My older portables have the former, my Dell 24" has the latter) I can believe 1920x1280 might cause problems. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: question about my new Dell 3010
> Rats:: xvidtune gave me "Video modes are not settable on this chip." how cheap can you get? no, the question is: what chip/video card do I need that will get me [at least] 1920x1280? -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Twenty-six years of service to the Unix community. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: question about my new Dell 3010
On Sun, Dec 09, 2012 at 05:24:27AM +0100, Polytropon wrote: > On Sat, 8 Dec 2012 16:23:31 -0800, Gary Kline wrote: > > > > > > > > one of the remaining problems --hopefuully the Last-- with my > > Dell 3010 quad i5 is that the resolution stops at 5:4. it's > > something like 1280x1014 whereas my widescreen Dell needs > > 1920x1280 or close to that. do I need to go out and find a > > videocard? or is there a way of taking my 6GB of RAM and giving > > it to the video? > > There are two factors involved: > > The question of video memory is usually selectable in the > CMOS setup of the BIOS. Defaults will allocate several (and > sufficient) MB for common resolutions. However, this is a > usually automated process that does not involve user action. > It should "just work"(TM)(R)(C). :-) Holy Crud =no=. the 3010 has that screwy bootloader UEIF [?] that took me 79 years to get past that. the box just-boot. but not into widescreen. actually, I have two optiplix models; the older is a "Dell dual" and works at widescreen. I dont know why or how. > The question of the support for the current display is handled > by the GPU driver (usually brought by X itself or an additional > package, like for nVidia drivers). You can easily obtain what > resolution your display _natively_ has (in case it's a LCD, > which I assume), and the driver should automatically initialize > the display for _that_ display size (because physically, there > is only that one, in contrast to CRTs that can support different > display characteristics). you lost me. how can I easily obtain the resolution? FWIW:: im using my KDE switch ... ssh works going out; I get "no route to host" going back from this dell dual to "tao" my new quad. I have been trying for around three hours to get ssh working bidirectionally. nutshell, there is no way I can get Perry's or your xorg.con file onto tao wwithout a shit*oad of typing. << censored>> > In case it does _not_ work automatically, you can always setup > things using xorg.conf (which you normally do _not_ need). For > example, > > Section "Screen" > Identifier "Screen0" > Device "Card0" > Monitor "Monitor0" > DefaultDepth24 > SubSection "Display" > Viewport0 0 > Depth 24 > Visual "TrueColor" > Modes "1920x1280" > EndSubSection > EndSection > > would require 1920x1280 to be initialized regardless of what > the integrated magician might think. > > > > For dynamic testing, you can use the xrandr command. Issue those > commands from an X terminal: > > xrandr --fb 1920x1280 > xrandr --size 1920x1280 HMMM. I Just buttoned over: the --size says that the 1920x1280 isnt found in the modes. I'll use locate and see where the heck that configuration file is. ...WEll, the xorg.conf is only three lines long. it's in the usual place, /etc/X11 . and there are a bunch of related files in /usr/share/X11/* without a "Mode" line anywhere. > You can use xvidtune (usually _not_ used for LCDs, only for CRTs > and tuning) to verify. > > In worst case, put those two commands in your X initialization > file (usually ~/.xinitrc, sometimes ~/.xsession, if not cascaded). > It's a dirty hack, but it should work. :-) > everything in my to-be desktop is standard. so is KDE and Gnome. I'll see in xvidtune is there. thanks for the help. gary > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Twenty-six years of service to the Unix community. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Kernel panic after excessive access to NFSv4 as client (FreeBSD-9.1)
Hi, My system has been encountering kernel panic every time it accesses large number of files over NFSv4. The backtrace left after reboot (I haven't saved the core dump): Dec 4 17:35:56 freebsd syslogd: kernel boot file is /boot/kernel/kernel Dec 4 17:35:56 freebsd kernel: panic: stack overflow detected; backtrace may be corrupted Dec 4 17:35:56 freebsd kernel: cpuid = 1 Dec 4 17:35:56 freebsd kernel: KDB: stack backtrace: Dec 4 17:35:56 freebsd kernel: #0 0x809274a6 at kdb_backtrace+0x66 Dec 4 17:35:56 freebsd kernel: #1 0x808f13fe at panic+0x1ce Dec 4 17:35:56 freebsd kernel: #2 0x8091a452 at __stack_chk_fail+0x12 Dec 4 17:35:56 freebsd kernel: #3 0x81613ee7 at krb5_unwrap_old+0x407 Dec 4 17:35:56 freebsd kernel: #4 0x8161413c at krb5_unwrap+0x12c Dec 4 17:35:56 freebsd kernel: #5 0x816446e4 at xdr_rpc_gss_unwrap_data+0x164 Dec 4 17:35:56 freebsd kernel: #6 0x81642a9d at rpc_gss_validate+0x1bd Dec 4 17:35:56 freebsd kernel: #7 0x80ad09be at clnt_vc_call+0x8de Dec 4 17:35:56 freebsd kernel: #8 0x80acec0b at clnt_reconnect_call+0xfb Dec 4 17:35:56 freebsd kernel: #9 0x807f07e5 at newnfs_request+0x595 Dec 4 17:35:56 freebsd kernel: #10 0x80826c42 at nfscl_request+0x72 Dec 4 17:35:56 freebsd kernel: #11 0x808117dd at nfsrpc_lookup+0x1bd Dec 4 17:35:56 freebsd kernel: #12 0x80821982 at nfs_lookup+0x292 Dec 4 17:35:56 freebsd kernel: #13 0x80c6ee60 at VOP_LOOKUP_APV+0x40 Dec 4 17:35:56 freebsd kernel: #14 0x8097abaf at lookup+0x41f Dec 4 17:35:56 freebsd kernel: #15 0x8097bcab at namei+0x4db Dec 4 17:35:56 freebsd kernel: #16 0x8098d203 at kern_statat_vnhook+0xb3 Dec 4 17:35:56 freebsd kernel: #17 0x8098d3c5 at kern_statat+0x15 Dec 4 17:35:56 freebsd kernel: Uptime: 21h22m34s Dec 4 17:35:56 freebsd kernel: Automatic reboot in 15 seconds - press a key on the console to abort Dec 4 17:35:56 freebsd kernel: Rebooting... Here's another backtrace: Dec 2 00:15:33 freebsd syslogd: kernel boot file is /boot/kernel/kernel Dec 2 00:15:33 freebsd kernel: panic: stack overflow detected; backtrace may be corrupted Dec 2 00:15:33 freebsd kernel: cpuid = 3 Dec 2 00:15:33 freebsd kernel: KDB: stack backtrace: Dec 2 00:15:33 freebsd kernel: #0 0x809274a6 at kdb_backtrace+0x66 Dec 2 00:15:33 freebsd kernel: #1 0x808f13fe at panic+0x1ce Dec 2 00:15:33 freebsd kernel: #2 0x8091a452 at __stack_chk_fail+0x12 Dec 2 00:15:33 freebsd kernel: #3 0x81613ee7 at krb5_unwrap_old+0x407 Dec 2 00:15:33 freebsd kernel: #4 0x8161413c at krb5_unwrap+0x12c Dec 2 00:15:33 freebsd kernel: #5 0x816446e4 at xdr_rpc_gss_unwrap_data+0x164 Dec 2 00:15:33 freebsd kernel: #6 0x81642a9d at rpc_gss_validate+0x1bd Dec 2 00:15:33 freebsd kernel: #7 0x80ad09be at clnt_vc_call+0x8de Dec 2 00:15:33 freebsd kernel: #8 0x80acec0b at clnt_reconnect_call+0xfb Dec 2 00:15:33 freebsd kernel: #9 0x807f07e5 at newnfs_request+0x595 Dec 2 00:15:33 freebsd kernel: #10 0x80826c42 at nfscl_request+0x72 Dec 2 00:15:33 freebsd kernel: #11 0x8080fcd4 at nfsrpc_write+0x4e4 Dec 2 00:15:33 freebsd kernel: #12 0x8081ea72 at ncl_writerpc+0x62 Dec 2 00:15:33 freebsd kernel: #13 0x80829f26 at ncl_doio+0x196 Dec 2 00:15:33 freebsd kernel: #14 0x8082e002 at nfssvc_iod+0xc2 Dec 2 00:15:33 freebsd kernel: #15 0x808c1f0f at fork_exit+0x11f Dec 2 00:15:33 freebsd kernel: #16 0x80bc8c3e at fork_trampoline+0xe Dec 2 00:15:33 freebsd kernel: Uptime: 2h6m33s Dec 2 00:15:33 freebsd kernel: Automatic reboot in 15 seconds - press a key on the console to abort Dec 2 00:15:33 freebsd kernel: Rebooting... # uname -a FreeBSD freebsd.nj-k.org 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #5 r243328: Sat Nov 24 03:01:20 JST 2012 root@:/usr/obj/usr/src/sys/GENERIC amd64 Disabling rpcbind stopped the kernel panic for a while. # cat /etc/rc.conf (truncated lines for apache and etc.) hostname="freebsd.nj-k.org" keymap="us.iso.kbd" ifconfig_re0="DHCP" ntpd_enable="YES" ntpd_sync_on_start="YES" nscd_enable="YES" ##rpcbind_enable="YES" gssd_enable="YES" nfsuserd_enable="YES" nfsuserd_flags="-domain nj-k.org" nfscbd_enable="YES" nfs_client_enable="YES" sendmail_enable="YES" # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable dumpdev="NO" # cat /etc/fstab # DeviceMountpoint FStype Options DumpPass# /dev/vtbd0p2/ ufs rw 1 1 /dev/vtbd0p3noneswapsw 0 0 nfs.nj-k.org:/ /mnt/nfsnfs rw,nfsv4,sec=krb5p,rsize=32768,wsize=32768,intr 0 0 # klist Credentials cache: FILE:/tmp/krb5cc_0 Principal: host/freebsd.nj-k@nj-k.org Issued Expires Principal Dec 10 00:45:00 Dec 10 10:45:00 krbtgt/nj-k@nj-k.org
Re: question about my new Dell 3010
On Sun, 9 Dec 2012, Matthew Seaman wrote: https://en.wikipedia.org/wiki/File:DVI_Connector_Types.svg Most DVI monitor cables have a DVI-D dual link plug on them, but anything matching those patterns is proof positive of DVI. VGA connectors looks like this: https://en.wikipedia.org/wiki/File:Vga-cable.jpg Anyhow, the point is if you're using a DVI connector, X will be able to query the monitor and find out its preferred resolution etc. automatically. Whereas with a VGA connector, it will default to using one of the standard VGA series of resolutions. Actually, DDC works on VGA connectors also: http://en.wikipedia.org/wiki/Display_Data_Channel These limited resolutions are almost certainly due to the KMS Intel driver being needed but the system not being built to support it. So the vesa driver is loaded instead, offering only a few legacy resolutions. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: question about my new Dell 3010
On 09/12/2012 00:23, Gary Kline wrote: > one of the remaining problems --hopefuully the Last-- with my > Dell 3010 quad i5 is that the resolution stops at 5:4. it's > something like 1280x1014 whereas my widescreen Dell needs > 1920x1280 or close to that. do I need to go out and find a > videocard? or is there a way of taking my 6GB of RAM and giving > it to the video? Do you have a DVI connector on your current graphics card, or just the old style VGA connector? Pretty much all modern widescreen monitors will have a DVI connector as well as the legacy VGA. If you don't know what those are, see this page: https://en.wikipedia.org/wiki/File:DVI_Connector_Types.svg Most DVI monitor cables have a DVI-D dual link plug on them, but anything matching those patterns is proof positive of DVI. VGA connectors looks like this: https://en.wikipedia.org/wiki/File:Vga-cable.jpg Anyhow, the point is if you're using a DVI connector, X will be able to query the monitor and find out its preferred resolution etc. automatically. Whereas with a VGA connector, it will default to using one of the standard VGA series of resolutions. All monitors will support some sort of VGA resolution for backwards compatibility -- typically 1024x768@60Hz -- and many will support higher, but all of the VGA series resolutions are 4:3 aspect ratio which doesn't look very nice on a widescreen monitor. There's two ways to fix the problem. 1) Get a video card with a DVI connector, or at least a DVI-to-DVI monitor cable if your card already has that. Apart from the hassle of getting a new video card that will work happily with X, this should be pretty painfree. 2) Edit your Xorg.conf to add a custom mode that matches what your monitor expects. Back in the days of CRTs this was a potentially risky thing to do, as configuring the video mode wrongly could phsically damage your monitor. Modern flatscreens however will just put up a message saying the input is incompatible. Working out what the right parameters are to put in the mode definition is the tricky bit. You may be able to use xrandr to pull them out (but if xrandr could do it, then X would do it automatically too...) There should be documentation that comes with the monitor, or you may find a kind soul online with the same make and model of monitor who will send you some xrandr output. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
