On Mon, Dec 17, 2012 at 07:34:22PM +0100, pk wrote
On 2012-12-17 17:23, Walter Dnes wrote:
snipped a whole lot...
1) Despite the TV being native 1366x768, it defaults to 1280x720, which
is the first mode listed in the EDID. Fixed-pixel displays show best at
their native resolution So
Walter's Excellent Adventure Chapter 2
On Tue, Dec 18, 2012 at 03:17:59AM -0500, Walter Dnes wrote
I ran emerge -pv mesa, and discovered that mesa had been merged with
USE=-xorg. This is what I get for starting USE with -*...
Walter's Excellent Adventure Chapter 3
On Tue, Dec 18, 2012 at 05:02:32AM -0500, Walter Dnes wrote
The net change is that...
* the TV displays in native 1366x768 mode, and *ONLY* 1366x768 mode
* X now has hardware acceleration
I ran emerge -pv --deep --newuse world to make sure
On Tue, Dec 18, 2012 at 05:01:59PM -0500, Walter Dnes wrote:
* X now has hardware acceleration
I ran emerge -pv --deep --newuse world to make sure everything was
OK. It wanted to rebuild xorg-server and one other lib after the
changes in VIDEO_CARDS in make.conf. While I was at, I
On Tue, Dec 18, 2012 at 04:59:47PM -0600, Bruce Hill wrote
On Tue, Dec 18, 2012 at 05:01:59PM -0500, Walter Dnes wrote:
With hardware acceleration enable for the onboard Intel GPU, I
can now dump the Nvidia card.
Can you give me some guide, or advice for this ... other than the
I have an Intel i3 hooked up to the HDMI input of my 50-inch plasma
TV. The TV's native resolution is 1366x768. It was bought in the
summer of 2007. I have 2 problems I want to fix as far as displaying
stuff on it is concerned...
1) Despite the TV being native 1366x768, it defaults to
On 2012-12-17 17:23, Walter Dnes wrote:
snipped a whole lot...
1) Despite the TV being native 1366x768, it defaults to 1280x720, which
is the first mode listed in the EDID. Fixed-pixel displays show best at
their native resolution So I ran Xorg -configure and created an
xorg.conf file, and
Hello,
We'll I've got a new samsung monitor 2333HD-1
that is verified 1920x1080.
Finally, I got it working on a dvi-d-2-dvi-d video cable
with no problems...(minimal xorg.conf) and ati-drivers.
OK, so I switch to a DVI-Don video card to HDMI
on the monitor and it comes in, but the bottom and
On Fri, Aug 27, 2010 at 1:31 PM, James wirel...@tampabay.rr.com wrote:
We'll I've got a new samsung monitor 2333HD-1
that is verified 1920x1080.
Finally, I got it working on a dvi-d-2-dvi-d video cable
with no problems...(minimal xorg.conf) and ati-drivers.
OK, so I switch to a DVI-Don
Apparently, though unproven, at 20:31 on Friday 27 August 2010, James did
opine thusly:
Hello,
We'll I've got a new samsung monitor 2333HD-1
that is verified 1920x1080.
Finally, I got it working on a dvi-d-2-dvi-d video cable
with no problems...(minimal xorg.conf) and ati-drivers.
On Fri, Aug 27, 2010 at 15:31, James wirel...@tampabay.rr.com wrote:
Hello,
We'll I've got a new samsung monitor 2333HD-1
that is verified 1920x1080.
Finally, I got it working on a dvi-d-2-dvi-d video cable
with no problems...(minimal xorg.conf) and ati-drivers.
OK, so I switch to a
Hello,
We'll I've got a new samsung monitor 2333HD-1
that is verified 1920x1080.
Finally, I got it working on a dvi-d-2-dvi-d video cable
with no problems...(minimal xorg.conf) and ati-drivers.
OK, so I switch to a DVI-Don video card to HDMI
on the monitor and it comes in, but the
On 21.07.2010 5:46, James wrote:
I can get X(kde 4.4) to start and run without a xorg.conf file
but at the wrong screen resolution. (1600x1200) instead
of 1920x1280, as it was before. Every attempt to
edit the old xorg.conf or roll a new xorg.conf with the new
2.6.34-gentoo-r1 kernel
On 07/21/2010 04:46 AM, James wrote:
hello,
I can get X(kde 4.4) to start and run without a xorg.conf file
but at the wrong screen resolution. (1600x1200) instead
of 1920x1280, as it was before. Every attempt to
edit the old xorg.conf or roll a new xorg.conf with the new
hello,
I can get X(kde 4.4) to start and run without a xorg.conf file
but at the wrong screen resolution. (1600x1200) instead
of 1920x1280, as it was before. Every attempt to
edit the old xorg.conf or roll a new xorg.conf with the new
2.6.34-gentoo-r1 kernel results in X that crashes.
Maybe
On Saturday 15 September 2007, Allan Gottlieb wrote:
At Sat, 15 Sep 2007 20:56:32 +0100 Mick [EMAIL PROTECTED] wrote:
As it happens I noticed that my TV out also stopped working recently.
However, I run ATI not nvidia. I blamed the latest xorg-server for it
and left it at that. When I run
On Tuesday 11 September 2007, Daniel Pielmeier wrote:
Since you are describing a TV out it might be your tertiary screen.
When I type xrandr with no arguments I get
Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 1920 x 1920
VGA connected 1600x1200+0+0 (normal left
As it happens I noticed that my TV out also stopped working recently.
However, I run ATI not nvidia. I blamed the latest xorg-server for it and
left it at that. When I run xrandr, just like you, I only see the laptop's
screen:
==
$ xrandr
Screen 0:
At Sat, 15 Sep 2007 20:56:32 +0100 Mick [EMAIL PROTECTED] wrote:
As it happens I noticed that my TV out also stopped working recently.
However, I run ATI not nvidia. I blamed the latest xorg-server for it and
left it at that. When I run xrandr, just like you, I only see the laptop's
Sounds like the server doesn't implement RandR version 1.2
What does xrandr -v say. For me it is
Server reports RandR version 1.2
If you don't have 1.2 you won't have the --output stuff.
Also --on doesn't exist even in 1.2.
I found man xrandr helpful.
Randr 1.2 was introduced in xorg
Since you are describing a TV out it might be your tertiary screen.
When I type xrandr with no arguments I get
Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 1920 x 1920
VGA connected 1600x1200+0+0 (normal left inverted right) 0mm x 0mm
1920x1440 60.0
Now my ~/bin/Xinitialize begins
#!/bin/sh
sleep 2
if xrandr | grep VGA connected ; then
xrandr --verbose --output VGA --mode 1600x1200 --output LVDS --off
else
xrandr --verbose --output VGA --off --output LVDS --mode 1680x1050
fi
xset s reset# above seems to
I have tested xrandr but it is useless for me! I tried various things
but neither of them seem to have any effect on my secondary screen. I
can only change the configuration of my primary monitor. Disabling randr
in xorg conf has no effect too.
Does anybody know what changes have to be done in
At Mon, 10 Sep 2007 09:24:59 +0200 Daniel Pielmeier [EMAIL PROTECTED] wrote:
Thanks for your answer, i will try if i can get it working like this
but randr doesn't seem to work on the secondary device. I have heard
that nvidia cards doesn't support randr 1.2 so i will give it a try
with randr
Thanks for your answer, i will try if i can get it working like this
but randr doesn't seem to work on the secondary device. I have heard
that nvidia cards doesn't support randr 1.2 so i will give it a try
with randr disabled in my configuration.
I don't have nvidia so can't comment (I810)
Allan Gottlieb schrieb:
At Mon, 10 Sep 2007 09:24:59 +0200 Daniel Pielmeier [EMAIL PROTECTED] wrote:
Thanks for your answer, i will try if i can get it working like this
but randr doesn't seem to work on the secondary device. I have heard
that nvidia cards doesn't support randr 1.2 so i will
I found a bug at archlinux [1] which is describing my problem. There are
two pictures attached. I have exactly the same problem. This bug was
closed as wont fix because it should be a nvidia problem. This is
possible, but i don't think so as the upgrade of xorg-server package
obviously caused
At Mon, 10 Sep 2007 20:05:26 +0200 Daniel Pielmeier [EMAIL PROTECTED] wrote:
I have tested xrandr but it is useless for me! I tried various things
but neither of them seem to have any effect on my secondary screen.
Since you are describing a TV out it might be your tertiary screen.
When I type
Hi,
the update to xorg-server-1.3 broke my dual-screen setup. It creates a
virtual screen size with the same size of the primary monitor for the
second monitor which is my TV. So i can only reach a zone with 800x600
on the second device, even scrolling within the virtual screen is
impossible. I
At Mon, 10 Sep 2007 00:33:35 +0200 Daniel Pielmeier [EMAIL PROTECTED] wrote:
the update to xorg-server-1.3 broke my dual-screen setup. It creates a
virtual screen size with the same size of the primary monitor for the
second monitor which is my TV. So i can only reach a zone with 800x600
on
I have a problem with my screen resolution.
In my xorg.conf file I have this:
# The favoured Depth and/or Bpp may be specified here
DefaultDepth 24
SubSection Display
Depth8
ViewPort0 0
Modes1024x768 800x600 640x480
EndSubsection
Hi Guys,
Well, finally! Thanks, again, to everyone who assisted with this
problem yesterday. As previously stated, I finally got an xorg.conf
file that worked and would allow me to use full screen mode for some of
the games that I play.
However, as of my last post yesterday, I still didn't
Colleen Beamer wrote:
Okay, I give. I'm having a problem with configuring xorg.
I *do* have a basic configuration, but can't run some applications in
full screen mode and I surmise this is because something isn't set
properly in xorg.conf I ran Xorg -configure and it did give me a basic
Hi folks,
I can't find an xorg.conf.example file
I just finished installing X window server.
# X -config /root/xorg.conf.new
created a working xorg.conf for me. I don't need xorg.conf.example.
Then;
# cp /root/xorg.conf.new /etc/X11/xorg.conf
That is all. Some minor adjustment has to be
Stephen Liu wrote:
Hi folks,
I can't find an xorg.conf.example file
I just finished installing X window server.
# X -config /root/xorg.conf.new
created a working xorg.conf for me. I don't need xorg.conf.example.
Then;
# cp /root/xorg.conf.new /etc/X11/xorg.conf
That is
Hi Dale,
I recall having to work a bit to get it to see my mouse too. X will
not
start without the little rat being found.
Mine is:
OptionDevice /dev/input/mouse0
The above line works for me too. OR /dev/input/mice also works here.
On the document mentioned by me
On Saturday 09 September 2006 08:30, Stephen Liu wrote:
Mine is:
OptionDevice /dev/input/mouse0
The above line works for me too. OR /dev/input/mice also works here.
X will *always* fail to correctly detect my mice on most of the boxen that I
have configured so far.
Option
On Fri, 2006-09-08 at 23:53 -0500, Colleen Beamer wrote:
Okay, I give. I'm having a problem with configuring xorg.
I *do* have a basic configuration, but can't run some applications in
full screen mode and I surmise this is because something isn't set
properly in xorg.conf I ran Xorg
On Fri, 2006-09-08 at 23:53 -0500, Colleen Beamer wrote:
Okay, I give. I'm having a problem with configuring xorg.
I *do* have a basic configuration, but can't run some applications in
full screen mode and I surmise this is because something isn't set
properly in xorg.conf I ran Xorg
Thanks to all who have replied, but my problem *is not* with my mouse.
I went through that issue the very first time I installed Gentoo and
know that I have to change it to /dev/psaux.
I can boot into kde. However ...
1) I can't view some things in full screen. For instance, I play the
game
On Saturday 9 September 2006 15:14, Colleen Beamer wrote:
I've tried following the X Server Configuration HOW-TO, but no where
in that is there something that corresponds to this:
SubSection Display
Viewport 0 0
Depth 24
EndSubSection
I understand what the 24 means,
Colleen Beamer wrote:
Thanks to all who have replied, but my problem *is not* with my mouse.
I went through that issue the very first time I installed Gentoo and
know that I have to change it to /dev/psaux.
I can boot into kde. However ...
As root:
$ emerge -av app-admin/eselect-opengl
On Saturday 09 September 2006 13:14, Colleen Beamer wrote:
Thanks to all who have replied, but my problem *is not* with my mouse.
I went through that issue the very first time I installed Gentoo and
know that I have to change it to /dev/psaux.
Sorry, I only mentioned the mouse because it has
Hi,
Mick wrote:
On Saturday 09 September 2006 13:14, Colleen Beamer wrote:
Thanks to all who have replied, but my problem *is not* with my mouse.
I went through that issue the very first time I installed Gentoo and
know that I have to change it to /dev/psaux.
Sorry, I only mentioned the
On my graphic card there are 3 ports : DVI, VGA, TV. I use an LCD
monitor on 1280x1024 resolution with this config :
Section Monitor
Identifier monitor0
HorizSync 30-82
VertRefresh 50-85
EndSection
Section Device
Identifier ATI_VE_7000
Driver radeon
Option
Hi,
On Sat, 09 Sep 2006 11:40:11 -0500
Colleen Beamer [EMAIL PROTECTED] wrote:
Mick wrote:
Viewport refers to your virtual screen which is larger than the physical
monitor screen. Placing the cursor at the edge of the monitors scrolls the
screen in that direction, until the edge of the
On Saturday 09 September 2006 16:40, Colleen Beamer wrote:
This is part of my xorg.conf in case it helps:
===
Section Monitor
DisplaySize 336 269 # 96 DPI @ 1280x1024
Identifier Monitor0
VendorName NEC
ModelName
Hi (again),
On Sat, 09 Sep 2006 08:14:47 -0500
Colleen Beamer [EMAIL PROTECTED] wrote:
1) I can't view some things in full screen. For instance, I play the
game Blobwars and if I try to set it to use full screen mode, the game
shows in the middle of the screen, the same size as it was when
On Sat, 9 Sep 2006 18:38:26 +
Mick [EMAIL PROTECTED] wrote:
On Saturday 09 September 2006 16:40, Colleen Beamer wrote:
This is part of my xorg.conf in case it helps:
===
Section Monitor
DisplaySize 336 269 # 96 DPI @ 1280x1024
On Saturday 09 September 2006 18:16, Jan-Hendrik Zab wrote:
Hey,
just for the record. IMHO it is a lot easier to set the DPI per
~/.Xdefaults with 'Xft.dpi: 96'. Or by starting the X Server with
'-dpi 96'. Especially when you want to try some specific DPI value.
Cool! I didn't know
Hi Guys,
Thank you *so* much for your patience and your help!
Hervé wrote:
On my graphic card there are 3 ports : DVI, VGA, TV. I use an LCD
monitor on 1280x1024 resolution with this config :
Section Monitor
Identifier monitor0
HorizSync 30-82
VertRefresh 50-85
Okay, I give. I'm having a problem with configuring xorg.
I *do* have a basic configuration, but can't run some applications in
full screen mode and I surmise this is because something isn't set
properly in xorg.conf I ran Xorg -configure and it did give me a basic
configuration, but the file
Did you check Linux on Laptops [http://www.linux-on-laptops.com/hp.html]?
http://www.linuxquestions.org/hcl/showproduct.php?product=1563
http://www.unicolet.org/nx9105.html
--
ellotheth rimmwen
* monjoy *
--
gentoo-user@gentoo.org mailing list
Hi!
I have laptop HP nx9105 which has screen 15.4
resolution of 1280x800 and graphics card nVidia GeForce 4 Go 32M and I am
looking for some assistance in configuration of xorg.conf J. So, can
somebody help me?
Bye
Goran
I have laptop HP nx9105 which has screen 15.4 resolution of 1280x800 and
graphics card nVidia GeForce 4 Go 32M and I am looking for some assistance
in configuration of xorg.conf J. So, can somebody help me?
Try Xorg -configure
see http://www.gentoo.org/doc/en/xorg-config.xml
Dave
--
Yes I tried but I am looking if someone has done it already or does know
what should I write in xorg.conf.
Bye
Goran
-Original Message-
From: Dave Moore [mailto:[EMAIL PROTECTED]
Sent: Monday, March 13, 2006 11:00 PM
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] xorg.conf
in xorg.conf.
Bye
Goran
-Original Message-
From: Dave Moore [mailto:[EMAIL PROTECTED]
Sent: Monday, March 13, 2006 11:00 PM
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] xorg.conf
I have laptop HP nx9105 which has screen 15.4 resolution of 1280x800 and
graphics
On Thu, 13 Oct 2005, Holly Bostick wrote:
Jorge Almeida schreef:
It seems it's a known bug. I emerged nvidia-kernel and nvidia-glx
with ACCEPT_KEYWORDS=~x86 and it works now.
Glad that worked for you, but please now remember to add nvidia-kernel
and nvidia-glx to
On Wed, 12 Oct 2005, Brett I. Holcomb wrote:
One thing to check is do you have any /dev/nv* devices? There was a thread in
the forums on this which has a script for recreating them and another thread
on this list in which I posted it.
That was it. I found the thread, that's why I emerged
Jorge Almeida wrote:
Glad that worked for you, but please now remember to add nvidia-kernel
and nvidia-glx to /etc/portage/package.keywords as allowed to be ~x86,
or else Portage will try to downgrade them the next time you do an
emerge world-- ACCEPT_KEYWORDS on an emerge command line is only
Jorge Almeida schreef:
On Thu, 13 Oct 2005, Holly Bostick wrote:
Jorge Almeida schreef:
It seems it's a known bug. I emerged nvidia-kernel and nvidia-glx
with ACCEPT_KEYWORDS=~x86 and it works now.
Glad that worked for you, but please now remember to add
nvidia-kernel and
On Thu, 13 Oct 2005, Holly Bostick wrote:
The solution for your stated preference is to unmask the packages'
keyword in /etc/portage/package.keywords, and mask all versions of the
package above the one you have now, so that they do not appear if an
update occurs and you do not want to
On Thu, 13 Oct 2005 08:48:27 +0100 (WEST), Jorge Almeida wrote:
Glad that worked for you, but please now remember to add nvidia-kernel
and nvidia-glx to /etc/portage/package.keywords as allowed to be ~x86,
or else Portage will try to downgrade them the next time you do an
emerge world--
@lists.gentoo.org
Subject: Re: [gentoo-user] xorg.conf
On Wed, 12 Oct 2005, Brett I. Holcomb wrote:
One thing to check is do you have any /dev/nv* devices? There was a thread
in
the forums on this which has a script for recreating them and another thread
on this list in which I posted
I have never seen a good reason why a package *shoulnt* be in the world
file. Especially dependencies. I am continually getting surprised by
emerge -s showing new versions of packages that emerge -u and sometimes
emerge -uD do not see. Not good.
depclean is unclean = system breaker.
It has
I can't find out what I'm doing wrong. I have a nvidia card (GeForce FX
5200) and I managed to launch the X server with the nv driver. When I
try to use the nvidia driver, the server aborts, complaining about not
finding a usable screen section.
The following file is the one that works (with nv).
It seems it's a known bug. I emerged nvidia-kernel and nvidia-glx with
ACCEPT_KEYWORDS=~x86 and it works now.
--
Jorge Almeida
--
gentoo-user@gentoo.org mailing list
One thing to check is do you have any /dev/nv* devices? There was a
thread in the forums on this which has a script for recreating them and
another thread on this list in which I posted it.
On Wed, 12 Oct 2005,
Jorge Almeida wrote:
I can't find out what I'm doing wrong. I have a nvidia
Jorge Almeida schreef:
It seems it's a known bug. I emerged nvidia-kernel and nvidia-glx
with ACCEPT_KEYWORDS=~x86 and it works now.
Glad that worked for you, but please now remember to add nvidia-kernel
and nvidia-glx to /etc/portage/package.keywords as allowed to be ~x86,
or else Portage
I got the alsa sound set up right (I think) and now I turn my attention
toward support for my Mitsumi Optical wheel mouse. I never had a
problem with it before the past two days' install. I ran X -configure
and got a configuration file:
xorg.conf.new:
baby root # cat xorg.conf.new
Section
It was actually /dev/input/mouse0, but I found it and now the mouse
works right. Thanks for your help! :)
On Fri, 2005-04-15 at 16:59 +0200, Cyrille Damez wrote:
I guess the problem is the last line of this section:
Section InputDevice
Identifier Mouse0
Driver mouse
71 matches
Mail list logo
