From: "Jerry Eastmanhouser" <fuct.it@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Screen settings
Date: Thu, 23 Feb 2006 04:54:59 -0500 [thread overview]
Message-ID: <87f1fb0a0602230154n25e3af25h415baf5bee46e686@mail.gmail.com> (raw)
In-Reply-To: <a95f61fd0602230130w18b61b10t882a1d435a3e83f9@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 10042 bytes --]
Well here is the thing...your getting a lot of errors in there with respect
to the resolution. I took a snipit that I think is important here.
*(II) I810(0): Monitor0: Using default hsync range of 28.00-33.00 kHz*
*(II) I810(0): Monitor0: Using default vrefresh range of 43.00-72.00 Hz*
*(II) I810(0): Not using default mode "1400x1050" (hsync out of range)*
*(II) I810(0): Not using default mode "700x525" (bad mode
clock/interlace/doublescan)*
*(II) I810(0): Not using default mode "1400x1050" (bad mode
clock/interlace/doublescan)*
*(II) I810(0): Not using default mode "700x525" (bad mode
clock/interlace/doublescan)*
*(II) I810(0): Not using default mode "1600x1024" (hsync out of range)*
*(II) I810(0): Not using default mode "800x512" (bad mode
clock/interlace/doublescan)*
*(II) I810(0): Not using default mode "1920x1440" (bad mode
clock/interlace/doublescan)*
*(II) I810(0): Not using default mode "960x720" (bad mode
clock/interlace/doublescan)*
*(II) I810(0): Not using default mode "2048x1536" (insufficient memory for
mode)*
*(II) I810(0): Not using default mode "1024x768" (bad mode
clock/interlace/doublescan)*
*(II) I810(0): Not using default mode "2048x1536" (insufficient memory for
mode)*
*(II) I810(0): Not using default mode "1024x768" (bad mode
clock/interlace/doublescan)*
*(II) I810(0): Not using default mode "2048x1536" (insufficient memory for
mode)*
*(II) I810(0): Not using default mode "1024x768" (bad mode
clock/interlace/doublescan)*
*(--) I810(0): Virtual size is 640x480 (pitch 1024)*
*(**) I810(0): *Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz*
*(II) I810(0): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525
-hsync -vsync*
*(==) I810(0): DPI set to (75, 75)*
See how the the horizontal and veritical ranges aren't so hot. The
auto-detection can only do
so much sometimes. I'm sure your going to have to refer to your monitor
manual and plug
in these settings manually....sometimes you can just google for them as
well. For example
on a spare box that I have an old 14inch VGA hooked up to the settings in
the xorg.conf file
is as follows.
* HorizSync 31,38,46.8,48*
* VertRefresh 50-100*
Now this is an old monitor that I took from my office when they were
throwing the monitor.
It's old...and yellow and when they were throwing it away it was in
1998....my point here is
that the configuration is higher than what you currently have in your config
file...I'm guessing
that you have a monitor that is newer than the one I have configured so I'm
guessing this is
likely a major part of your problem. X works so much better if you have the
exact configuration in there....and by doing it all by hand you'll also have
a much better understanding of how everything works and is setup. Also copy
your /etc folder and store it somewhere. It's only going to be a few meg
uncompressed and will save you loads of time later if you have a
corruption...blowup or just a reinstall.
J
On 2/23/06, Rajat Gujral <nutts4linux@gmail.com> wrote:
>
> hello all,
>
> I was just goin thru Xorg.0.log file and i notice that after doing startx
> some errors are being logged on the system ... I hope if someone know what
> exactly does this error means then please help me resolve it.
>
> Thanx in advance
>
> rgds
>
> rajat
>
> P.S. : Here with attached is the log file generated by startx
>
>
>
> On 2/23/06, Rajat Gujral <nutts4linux@gmail.com> wrote:
> >
> > Hi frino , steve
> >
> > i have added defaultdepth 24 to xorg.conf file but it still takes the
> > resolution as 640 x 480 ... I have checked the control panel
> > >pheripherals > display and there is only 1 resolution availiable
> > nothing else ..
> >
> > Now what shld i do pls help me through it ...
> >
> >
> > Thanx and rgds
> >
> >
> > Rajat
> >
> > On 2/23/06, Steven S. <stupendoussteve@gmail.com > wrote:
> > > On Thu, 23 Feb 2006, Rajat Gujral wrote:
> > >
> > > Have you tried adding the option DefaultDepth? Since you have the
> > Modes
> > > 1024x768 for 24, it should come out looking
> > > like:
> > >
> > > Section "Screen"
> > > Identifier "Screen0"
> > > Device "Card0"
> > > Monitor "Monitor0"
> > > DefaultDepth 24
> > > SubSection "Display"
> > > Viewport 0 0
> > > Depth 1
> > > EndSubSection
> > >
> > > This is the only way I am ever able to get my system to go to
> > 1280x1024,
> > > possibly it'll force yours to the correct setting.
> > >
> > > > Hi richard and jerry
> > > > thanx for ur suggestions but i guess my problem remains the same ...
> > My
> > > > xserver still starts with screen resolution of 640 x 480 ... Before
> > the
> > > > improper shutdown it was working fine in 1024 x 768 resolution , but
> > now
> > > no
> > > > matter what resolution i provide, it starts up with 640 x 480
> > resolution
> > > > which makes the screen appear so big .. Is there anything else that
> > i can
> > > do
> > > >
> > > >
> > > > Thnx & Regds
> > > >
> > > >
> > > > Rajat :)
> > > >
> > > >
> > > > P.S. I have done "X -configure" and has detected the following
> > settings :
> > > >
> > > > Section "ServerLayout"
> > > > Identifier "X.org <http://x.org/> Configured"
> > > > Screen 0 "Screen0" 0 0
> > > > InputDevice "Mouse0" "CorePointer"
> > > > InputDevice "Keyboard0" "CoreKeyboard"
> > > > EndSection
> > > >
> > > > Section "Files"
> > > > RgbPath "/usr/lib/X11/rgb"
> > > > ModulePath "/usr/lib/modules"
> > > > FontPath "/usr/share/fonts/misc/"
> > > > FontPath "/usr/share/fonts/TTF/"
> > > > FontPath "/usr/share/fonts/Type1/"
> > > > FontPath "/usr/share/fonts/CID/"
> > > > FontPath "/usr/share/fonts/75dpi/"
> > > > FontPath "/usr/share/fonts/100dpi/"
> > > > EndSection
> > > >
> > > > Section "Module"
> > > > Load "extmod"
> > > > Load "dbe"
> > > > Load "dri"
> > > > Load "record"
> > > > Load "xtrap"
> > > > Load "glx"
> > > > Load "type1"
> > > > Load "freetype"
> > > > EndSection
> > > >
> > > > Section "InputDevice"
> > > > Identifier "Keyboard0"
> > > > Driver "kbd"
> > > > EndSection
> > > >
> > > > Section "InputDevice"
> > > > Identifier "Mouse0"
> > > > Driver "mouse"
> > > > Option "Protocol" "Microsoft"
> > > > Option "Device" "/dev/ttyS1"
> > > > EndSection
> > > >
> > > > Section "Monitor"
> > > > Identifier "Monitor0"
> > > > VendorName "Monitor Vendor"
> > > > ModelName "Monitor Model"
> > > > EndSection
> > > > Section "Device"
> > > > ### Available Driver options are:-
> > > > ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
> > > > ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
> > > > ### [arg]: arg optional
> > > > #Option "NoAccel" # [<bool>]
> > > > #Option "SWcursor" # [<bool>]
> > > > #Option "ColorKey" # <i>
> > > > #Option "CacheLines" # <i>
> > > > #Option "Dac6Bit" # [<bool>]
> > > > #Option "DRI" # [<bool>]
> > > > #Option "NoDDC" # [<bool>]
> > > > #Option "ShowCache" # [<bool>]
> > > > #Option "XvMCSurfaces" # <i>
> > > > #Option "PageFlip" # [<bool>]
> > > > Identifier "Card0"
> > > > Driver "i810"
> > > > VendorName "Intel Corp."
> > > > BoardName "82810E DC-133 CGC [Chipset Graphics Controller]"
> >
> > > > BusID "PCI:0:1: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
> > > > Modes "1024x768"
> > > > EndSubSection
> > > > SubSection "Display"
> > > > Viewport 0 0
> > > > Depth 24
> > > > Modes "1024x768"
> > > > EndSubSection
> > > > EndSection
> > > >
> > > >
> > > >
> > > >
> > > > On 2/22/06, Richard Fish <bigfish@asmallpond.org > wrote:
> > > >>
> > > >> On 2/22/06, Jerry Eastmanhouser <fuct.it@gmail.com> wrote:
> > > >>> settings. I did mine manually a long long time ago, but I think
> > you can
> > > >> use
> > > >>> xorgconfig to detect most of your settings for you...if
> > so...hopefully
> > > >> that
> > > >>> will fix you up.
> > > >>
> > > >> I would suggest instead "X -configure". That should autodetect
> > most
> > > >> things, unlike xorgconfig which asks you a bunch of questions that
> > > >> most users don't know the answers to.
> > > >>
> > > >> -Richard
> > > >>
> > > >> --
> > > >> gentoo-user@gentoo.org mailing list
> > > >>
> > > >>
> > > >
> > > --
> > > gentoo-user@gentoo.org mailing list
> > >
> > >
> >
>
>
>
[-- Attachment #2: Type: text/html, Size: 19835 bytes --]
next prev parent reply other threads:[~2006-02-23 10:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 8:59 [gentoo-user] Screen settings Rajat Gujral
2006-02-22 9:28 ` Jerry Eastmanhouser
2006-02-22 15:04 ` Richard Fish
2006-02-23 6:14 ` Rajat Gujral
2006-02-23 6:47 ` Steven S.
2006-02-23 8:45 ` [gentoo-user] " Rajat Gujral
2006-02-23 9:30 ` Rajat Gujral
2006-02-23 9:54 ` Jerry Eastmanhouser [this message]
2006-02-23 6:48 ` [gentoo-user] " Frino Klauss
2006-02-25 5:14 ` Linux Blues
2006-02-23 7:06 ` Martins Steinbergs
2006-02-24 22:10 ` Walter Dnes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87f1fb0a0602230154n25e3af25h415baf5bee46e686@mail.gmail.com \
--to=fuct.it@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox