public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] radeon and radeonfb both loaded
Date: Tue, 21 Jul 2009 17:43:42 -0700	[thread overview]
Message-ID: <5bdc1c8b0907211743q5e70054cne3be3a419fe68f67@mail.gmail.com> (raw)
In-Reply-To: <200907220000.36430.michaelkintzios@gmail.com>

On Tue, Jul 21, 2009 at 4:00 PM, Mick<michaelkintzios@gmail.com> wrote:
> On Tuesday 21 July 2009, Mark Knecht wrote:
>> On Tue, Jul 21, 2009 at 10:56 AM, Mick<michaelkintzios@gmail.com> wrote:
>
>> > roughly is equivalent to 1210x907 pixels.  Run 'xdpyinfo -display :0.0'
>> > to see the dimensions in rounded numbers.
>
>> OK, there is possibly a little extra difficulty to get this run, but
>> it's likely just ssh stuff or possibly not enabling something in X11.
>>
>> 1) I first ssh into my dad's Gentoo machine. When I try to run the
>> command through the ssh tunnel I get this:
>>
>> gandalf ~ # xdpyinfo -display :0.0
>> Xlib: connection to ":0.0" refused by server
>> Xlib: Protocol not supported by server
>>
>> xdpyinfo:  unable to open display ":0.0".
>> gandalf ~ #
>>
>> I then ssh into my mom's Gentoo machine
>>
>> gandalf ~ # !ssh
>> ssh DesertFlower
>> Password:
>> Last login: Mon Jul 20 19:29:10 PDT 2009 from gandalf on pts/0
>> DesertFlower ~ # xdpyinfo -display :0.0
>> Xlib: connection to ":0.0" refused by server
>> Xlib: No protocol specified
>>
>> xdpyinfo:  unable to open display ":0.0".
>> DesertFlower ~ #
>>
>> Right now no one is logged into either machine. Both are presumably
>> sitting with gdm login screens.
>
> Hmm, it could be an ssh thing, not sure, probably an xauth thing (have a look
> at man xauth).  See if setting your IP address allows to access your parents
> machine:
>
> xdpyinfo -display XXX.XXX.XX.XX:0.0  <--where XXX.XXX.XX.XX is your IP address
>
> of try to set the relevant env variable: setenv DISPLAY XXX.XXX.XXX.XXX:0 at
> your client machine first.
>
> Alternatively, ask them to login and then use the same login credentials.
>
> HTH.
> --
> Regards,
> Mick
>
No luck with -display and any IP address I can think of - my address
from the net, my local address.

However, there is xdpyinfo -queryExtensions and in that data I see this:

mark@gandalf ~ $ xdpyinfo -queryExtensions
name of display:    localhost:10.0
version number:    11.0
vendor string:    The X.Org Foundation
vendor release number:    10503000
X.Org version: 1.5.3
maximum request size:  16777212 bytes
motion buffer size:  256
<SNIP>

screen #0:
  print screen:    no
  dimensions:    1280x1024 pixels (338x270 millimeters)
  resolution:    96x96 dots per inch
  depths (7):    16, 1, 4, 8, 15, 24, 32
  root window id:    0x80
  depth of root window:    16 planes
  number of colormaps:    minimum 1, maximum 1


So on my dad's machine, which I know I set up as 1280x1024, I get the
right answer.

On my mom's machine however, which I have to

mark@DesertFlower ~ $ xdpyinfo -queryExtensions
name of display:    localhost:10.0
version number:    11.0
vendor string:    The X.Org Foundation
vendor release number:    10503000
X.Org version: 1.5.3
maximum request size:  16777212 bytes
<SNIP>
screen #0:
  print screen:    no
  dimensions:    1280x1024 pixels (338x270 millimeters)
  resolution:    96x96 dots per inch
  depths (7):    16, 1, 4, 8, 15, 24, 32
  root window id:    0x80
  depth of root window:    16 planes


and locally on my machine here I get the same info:

screen #0:
  print screen:    no
  dimensions:    1280x1024 pixels (338x270 millimeters)
  resolution:    96x96 dots per inch
  depths (7):    16, 1, 4, 8, 15, 24, 32
  root window id:    0x80
  depth of root window:    16 planes

so I'm not sure if I'm looking at their machines or just my own?

Actually, on my mom's machine it seems it's not really screen #0, it's
screen #1 according to the config file, but maybe Xorg actually calls
it screen #0 when it's tunning. None the less her default resolution
is supposed to be 1024x768 - she has an old small monitor:

Section "Screen"
    Identifier  "Screen 1"
    Device      "** ATI Radeon (generic)               [radeon]"
    Monitor     "My Monitor"
    DefaultDepth 16

    Subsection "Display"
        Depth       8
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1024x768" "800x600"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
EndSection

- Mark



  reply	other threads:[~2009-07-22  0:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20 18:22 [gentoo-user] radeon and radeonfb both loaded Mark Knecht
2009-07-20 19:15 ` [gentoo-user] Email Virus Scanner John
2009-07-20 20:10   ` Jacob Todd
2009-07-21 17:56     ` [gentoo-user] radeon and radeonfb both loaded Mick
2009-07-21 19:38       ` Mark Knecht
2009-07-21 23:00         ` Mick
2009-07-22  0:43           ` Mark Knecht [this message]
2009-07-22  7:49             ` Mick

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=5bdc1c8b0907211743q5e70054cne3be3a419fe68f67@mail.gmail.com \
    --to=markknecht@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