Re: [gentoo-user] radeon and radeonfb both loaded

2009-07-22 Thread Mick
On Wednesday 22 July 2009, Mark Knecht wrote:

Did you get your results with them logged in?

(I am surprised by the localhost:10.0 result)

 Subsection Display
 Depth   24
 Modes   1280x1024 1024x768 800x600 640x480
 ViewPort0 0
 EndSubsection

If you have mode 1280x1024 in your mothers xorg.conf, then it will try to 
render this resolution as long as the monitor supports it.

It may be easier to if you ask them to login, fireup a terminal, run xdpyinfo 
for you and read off the screen the result.
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] radeon and radeonfb both loaded

2009-07-21 Thread Mick
On Monday 20 July 2009, Jacob Todd wrote:
 On Mon, Jul 20, 2009 at 08:15:41PM +0100, John wrote:
  Please can you recommend a email virus scanner.
 
  I am a little unsure about all the combinations available. I wish to
  scan incoming email on my home desktop. I currently use Claws Mail and
  was looking for the simplest option.
 
  Many Thanks
  --
  John D Maunder
  j...@articwolf.myzen.co.uk

 Maybe app-antivirus/clamav?

Or may be John shouldn't be hijacking threads (search for netiquette if you 
don't understand what I'm talking about) and Jacob shouldn't respond?

Back to the OP's questions: 

1) radeonfb is the framebuffer used when in console to render fonts in smaller 
sizes.  radeon is the xorg video card driver.  Therefore, you could have them 
both (either built in kernel or as modules).

2)The  (II) RADEON(0): Setting screen physical size to 320 x 240 message is 
expressing the screen resolution in millimeters .  This roughly is equivalent 
to 1210x907 pixels.  Run 'xdpyinfo -display :0.0' to see the dimensions in 
rounded numbers.
-- 
Regards,
Mick


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] radeon and radeonfb both loaded

2009-07-21 Thread Mark Knecht
On Tue, Jul 21, 2009 at 10:56 AM, Mickmichaelkintz...@gmail.com wrote:
SNIP

 Or may be John shouldn't be hijacking threads (search for netiquette if you
 don't understand what I'm talking about) and Jacob shouldn't respond?

 Back to the OP's questions:

 1) radeonfb is the framebuffer used when in console to render fonts in smaller
 sizes.  radeon is the xorg video card driver.  Therefore, you could have them
 both (either built in kernel or as modules).

 2)The  (II) RADEON(0): Setting screen physical size to 320 x 240 message is
 expressing the screen resolution in millimeters .  This roughly is equivalent
 to 1210x907 pixels.  Run 'xdpyinfo -display :0.0' to see the dimensions in
 rounded numbers.
 --
 Regards,
 Mick


I wasn't aware they had done that. GMail separated them into different
threads here. Thanks for catching up with my question.

Thanks for the info on the screen resolution.

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.

Thanks,
Mark



Re: [gentoo-user] radeon and radeonfb both loaded

2009-07-21 Thread Mick
On Tuesday 21 July 2009, Mark Knecht wrote:
 On Tue, Jul 21, 2009 at 10:56 AM, Mickmichaelkintz...@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


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] radeon and radeonfb both loaded

2009-07-21 Thread Mark Knecht
On Tue, Jul 21, 2009 at 4:00 PM, Mickmichaelkintz...@gmail.com wrote:
 On Tuesday 21 July 2009, Mark Knecht wrote:
 On Tue, Jul 21, 2009 at 10:56 AM, Mickmichaelkintz...@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:

m...@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

m...@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
ViewPort0 0
EndSubsection
Subsection Display
Depth   16
Modes   1024x768 800x600
ViewPort0 0
EndSubsection
Subsection Display
Depth   24
Modes   1280x1024 1024x768 800x600 640x480
ViewPort0 0
EndSubsection
EndSection

- Mark



[gentoo-user] radeon and radeonfb both loaded

2009-07-20 Thread Mark Knecht
I'm working on my 80 year old mother's machine remotely and cannot see
the screen. I have a few question about this new Open Source Radeon
driver.

1) I'm seeing both radeon and radeonfb in memory. Is this OK, or does
it imply a problem of some sort? Can xorg-server use radeon while the
console is possibly using radeonfb or is the system misconfigured?

[8.571434] Adding 2048276k swap on /dev/hda6.  Priority:-1
extents:1 across:2048276k
[   20.010361] eth0:  setting full-duplex.
[   26.961162] [drm] Initialized radeon 1.29.0 20080528 on minor 0
[   27.327626] agpgart-ati :00:00.0: AGP 3.0 bridge
[   27.327652] agpgart-ati :00:00.0: putting AGP V3 device into 8x mode
[   27.327680] radeonfb :01:05.0: putting AGP V3 device into 8x mode
[   27.470855] [drm] Setting GART location based on new memory map
[   27.470867] [drm] Loading R200 Microcode
[   27.470914] [drm] writeback test succeeded in 1 usecs
[   30.344023] eth0: no IPv6 routers present
DesertFlower ~ # lsmod
Module  Size  Used by
radeon115840  2
snd_atiixp 14096  0
snd_ac97_codec 89412  1 snd_atiixp
ac97_bus1316  1 snd_ac97_codec
radeonfb   55956  0
fb_ddc  1668  1 radeonfb
DesertFlower ~ #

2) From a distance I'm wondering what these last few lines of
Xorg.0.log are telling me about the state the screen is likely in?
This machine has both a VGA connector (in use) and an S-Video
connector. (not in use) Is the 'Setting screen physical size to 320 x
240' an indication that if she was to look at the screen right now
it's not running in the normal 1024x768 sort of mode? How can I tell
at a distance what the screen resolution might be?

(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenByBusid: Searching for BusID pci::01:05.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 10, (OK)
drmOpenByBusid: drmOpenMinor returns 10
drmOpenByBusid: drmGetBusid reports pci::01:05.0
(II) AIGLX: enabled GLX_MESA_copy_sub_buffer
(II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
(II) AIGLX: enabled GLX_texture_from_pixmap with driver support
(II) AIGLX: Loaded and initialized /usr/lib/dri/r200_dri.so
(II) GLX: Initialized DRI GL provider for screen 0
(II) RADEON(0): Setting screen physical size to 320 x 240
(EE) config/hal: couldn't initialise context: (null) ((null))
disable TVDAC


I do see this implying (to me) that maybe it's in a 1024 type mode:

(==) RADEON(0): Using 16 bit depth buffer
(II) RADEON(0): RADEONInitMemoryMap() :
(II) RADEON(0):   mem_size : 0x0400
(II) RADEON(0):   MC_FB_LOCATION   : 0x0fff0c00
(II) RADEON(0):   MC_AGP_LOCATION  : 0xffc0
(II) RADEON(0): Depth moves disabled by default
(II) RADEON(0): Using 8 MB GART aperture
(II) RADEON(0): Using 1 MB for the ring buffer
(II) RADEON(0): Using 2 MB for vertex/indirect buffers
(II) RADEON(0): Using 5 MB for GART textures
(II) RADEON(0): Memory manager initialized to (0,0) (1024,8191)
(II) RADEON(0): Reserved area from (0,1024) to (1024,1026)
(II) RADEON(0): Largest offscreen area available: 1024 x 7165
(II) RADEON(0): Will use front buffer at offset 0x0
(II) RADEON(0): Will use back buffer at offset 0x80
(II) RADEON(0): Will use depth buffer at offset 0xa0
(II) RADEON(0): Will use 53248 kb for textures at offset 0xc0


Thanks,
Mark