On 02/10/11 23:46, Harry Putnam wrote: > Scott Ferguson <prettyfly.producti...@gmail.com> writes: > >> On 02/10/11 01:47, Harry Putnam wrote: >>> Scott Ferguson <prettyfly.producti...@gmail.com> writes: >>>
<snipped> >> It would be appreciated, greatly, if you could use "Reply" to >> continue a thread - saves searching through lots of posts in order >> to patch together all the needed information. > > I'm not sure what problem you are having with threading. This is "wrestling with xrandr", you started with a thread called "virtual resolution of desktop" <snipped> >>> >>> [...] >>> >>>> What Debian release are you running? $ cat /etc/issue ^^^ this is obviously a mistake *I've* made... I assumed that as you didn't initially say what Debian release you were running - that you didn't know. And I should have more clearly separated the question from the fallback query so that your email client wouldn't reformat them onto the same line - as it has. My apologies. What Debian release are you running? Your xlog says Pixman 0.22.2... (Wheezy or Sid) Your /etc/issue said testing/unstable - confusing. In an earlier post I suggested that:- http://wiki.debian.org/XStrikeForce/HowToRandR12 was only relevant to Thinkpads - that is incorrect (I was wrongly referring to another page). The page is useful - those commands, except where superseded, still apply to current version <snipped> > I'm using the standard fonts that are installed with xorg and gnome > desktop. Thanks - GNOME tells me a bit about your system. > I'm not using the gnome desktop. I use fluxbox, but I believe the > same fonts are used. They are - unless you specifically change them. > > I'm not really sure what drivers are being used. T think it is > Nouvea. The proprietary driver has problems with panning. I don't know which version of libxrandr2 you are running (I use 1.3) > I see that mentioned in Xorg.log, and have included Xorg.log at the > end. Thankyou. > I'm not sure how to interpret all that. I see several modules > loaded. That is usual. (multiple modules, difficult to interpret) > There is probably some handier way to get the information but I don't > know it. /var/log/Xorg.0.log (I assume that's what you mean by xorg.log) > > I've fired up gnome desktop and have this information from > Settings/Appearance fonts tab: > > Application font: sans 7 Document font: sans 7 desktop: > sans 7 Window title: Sans Bold 8 Fixed width monospace 9 I assume you mean the DejaVu family. > > Monochrom [], Best contrast [], Best shapes [] and Subpixel smoothing > [x] > > I have Subpixel Smoothing turned on as you see above, but honestly I > see no differnce no matter which of those I select. It makes a slight difference - it also means you have anti-aliasing enabled (I suspect that's default). It doesn't appear that you are running TrueType fonts which make more use of subpixel rendering. I wouldn't worry about it until you stop running the vesa video driver. > > The `details' button shows 96dpi I'm not sure why you have trouble with the fonts - all those settings seem about normal for people with normal vision. > >>> >>>>> TV-1 connected 720x576+1440+0 (normal left inverted right x >>>>> axis y axis) 0mm x 0mm 720x576 50.0*+ 1024x768 >>>>> 50.0 >>>> <snipped> Are you happy with only 720x576 resolution on the >>>> TV-out? 1024x768 is possible. >>> <snipped> >>> But I'd still like to know how to get 1024x768. >> >> I'll add it to the xrandr command. > <snipped> >> I'd suggest using the current default resolution (1440x900) and a >> panning resolution of 1680x1050 (saves scaling problems) > > Thanks for the tip. But I'm not sure what the command syntax would > be. I'm guessing: > > xrandr --fb 1440x900 --output DVI-I-1 --panning 1680x1050 what do you get from:- $ xrandr --output default --dryrun --mode 1440x900 --panning 1680x1050 if no errors, try without the dryrun parameter if you get error codes please post - if screen refreshes (without printing errors) but doesn't seem to pan, try Ctrl++ or Ctrl+- (this may also work:- $ xrandr -s 1440x900 --dryrun --panning 1680x1050) NOTE: I haven't done the virtual screen/VRAM math - your card doesn't have a lot of VRAM and you do want big screens.... > > If that is it, then it fails here: xrandr --fb 1440x900 --output > DVI-I-1 --panning 1680x1050 Those parameters are incorrect. > xrandr: specified screen 1440x900 not large enough for output TV-1 > (720x576+1440+0) X Error of failed request: BadMatch (invalid > parameter attributes) Major opcode of failed request: 150 (RANDR) > Minor opcode of failed request: 29 (RRSetPanning) Serial number of > failed request: 32 Current serial number in output stream: 32 > > I'm not sure how to change the TV setting. Or even if it can be > changed to accommodate that command. try:- $ xrandr --output 'TV-1' --dryrun --mode 1024x768 if *no* errors (probably will be due to a output name problem) *then* try without the dryrun parameter. Might have to create a minimal xorg.conf for that... > > > Trying: xrandr --output DVI-I-1 --panning 1680x1050 > > That shakes the screen a bit, and the mouse can now disappear > slightly at the edges, but as reported in the bug...it appears that > panning is being blocked. 2 pixel variation in screen width and height? If so that's the bug in v1.3.2 > > As you've noted there is a bug that might prevent panning in any > case. > > >> Brian has pointed a bug report that might be relevant. I believe >> the scaling problem is still outstanding - but (with new mode >> creation) panning is definitely not a problem with nouveau (I use >> it on my netbooks). I don't know about Testing though (and can't >> test it this weekend). > > I didn't quite follow what you meant by "(with new mode creation)". xrandr can only use existing modes - either those detected by X on boot (shown in /var/log/Xorg.0.log) or those written in /etc/X11/xorg.conf. cvt is used to determine valid modes - to use those that X doesn't know about, xrandr creates them using the newmode or addmode parameters. > > So you are able to do panning then? At least on a netbook. Yes. Squeeze running Trinity v.1.3.0 of libxrandr2 <snipped> > Xorg.log > > [ 5163.573] X.Org X Server 1.11.1 Release Date: 2011-09-24 [ > 5163.574] X Protocol Version 11, Revision 0 [ 5163.574] Build > Operating System: Linux 2.6.32-5-amd64 i686 Debian [ 5163.574] > Current Operating System: Linux reader 3.0.0-1-686-pae #1 SMP Sat Aug > 27 16:41:03 UTC 2011 i686 Is this a custom kernel? > [ 5163.574] Kernel command line: BOOT_IMAGE=/vmlinuz-3.0.0-1-686-pae > root=UUID=83a94f1d-e6e6-432e-86ad-b24754755fff ro quiet splash <snipped> > [ 5163.575] (WW) `fonts.dir' not found (or not valid) in > "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType". [ 5163.575] > Entry deleted from font path. [ 5163.576] (Run 'mkfontdir' on > "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"). ^^^ <snipped> > [ 5163.582] (==) Matched nouveau as autoconfigured driver 0 [ > 5163.582] (==) Matched nv as autoconfigured driver 1 [ 5163.582] > (==) Matched vesa as autoconfigured driver 2 [ 5163.582] (==) > Matched fbdev as autoconfigured driver 3 [ 5163.582] (==) Assigned > the driver to the xf86ConfigLayout [ 5163.582] (II) LoadModule: > "nouveau" [ 5163.582] (II) Loading > /usr/lib/xorg/modules/drivers/nouveau_drv.so [ 5163.583] (II) Module > nouveau: vendor="X.Org Foundation" [ 5163.583] compiled for 1.11.0, > module version = 0.0.16 [ 5163.583] Module class: X.Org Video > Driver [ 5163.583] ABI class: X.Org Video Driver, version 11.0 [ > 5163.583] (II) LoadModule: "nv" [ 5163.584] (WW) Warning, couldn't > open module nv [ 5163.584] (II) UnloadModule: "nv" [ 5163.584] (II) > Unloading nv [ 5163.584] (EE) Failed to load module "nv" (module > does not exist, 0) ^^^^^^^^^^^^^^^^^^^^^^^^ > [ 5163.584] (II) LoadModule: "vesa" Falling back to vesa(?) > [ 5163.584] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so <snipped> > [ 5163.592] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0 [ > 5163.592] (II) [drm] DRM interface version 1.4 [ 5163.592] (II) > [drm] DRM open master succeeded. [ 5163.593] (--) NOUVEAU(0): > Chipset: "NVIDIA NV36" [ 5163.593] (II) NOUVEAU(0): Creating default > Display subsection in Screen section "Default Screen Section" for > depth/fbbpp 24/32 [ 5163.593] (==) NOUVEAU(0): Depth 24, (--) > framebuffer bpp 32 [ 5163.593] (==) NOUVEAU(0): RGB weight 888 [ > 5163.593] (==) NOUVEAU(0): Default visual is TrueColor [ 5163.593] > (==) NOUVEAU(0): Using HW cursor [ 5163.593] (==) NOUVEAU(0): GLX > sync to VBlank disabled. [ 5163.593] (==) NOUVEAU(0): Page flipping > enabled [ 5163.660] (II) NOUVEAU(0): Output VGA-1 has no monitor > section [ 5163.765] (II) NOUVEAU(0): Output DVI-I-1 has no monitor > section [ 5163.820] (II) NOUVEAU(0): Output TV-1 has no monitor > section [ 5163.876] (II) NOUVEAU(0): EDID for output VGA-1 [ > 5163.981] (II) NOUVEAU(0): EDID for output DVI-I-1 [ 5163.981] (II) > NOUVEAU(0): Manufacturer: ACI Model: 26a4 Serial#: 18746 [ > 5163.981] (II) NOUVEAU(0): Year: 2010 Week: 31 [ 5163.981] (II) > NOUVEAU(0): EDID Version: 1.3 [ 5163.981] (II) NOUVEAU(0): Digital > Display Input [ 5163.981] (II) NOUVEAU(0): Max Image Size [cm]: > horiz.: 55 vert.: 34 [ 5163.981] (II) NOUVEAU(0): Gamma: 2.20 [ > 5163.981] (II) NOUVEAU(0): DPMS capabilities: Off [ 5163.982] (II) > NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 [ > 5163.982] (II) NOUVEAU(0): First detailed timing is preferred mode [ > 5163.982] (II) NOUVEAU(0): redX: 0.640 redY: 0.352 greenX: 0.287 > greenY: 0.628 [ 5163.982] (II) NOUVEAU(0): blueX: 0.144 blueY: 0.075 > whiteX: 0.312 whiteY: 0.328 [ 5163.982] (II) NOUVEAU(0): Supported > established timings: ^^^ all that looks fine. <snipped> > [ 5164.044] (==) NOUVEAU(0): Backing store disabled [ 5164.044] > (==) NOUVEAU(0): Silken mouse enabled [ 5164.045] (II) NOUVEAU(0): > [XvMC] Associated with NV30 texture adapter. [ 5164.045] (II) > NOUVEAU(0): [XvMC] Extension initialized. [ 5164.045] (==) > NOUVEAU(0): DPMS enabled [ 5164.045] (II) NOUVEAU(0): RandR 1.2 > enabled, ignore the following RandR disabled message. [ 5164.045] > (--) RandR disabled ??!! > [ 5164.045] (II) Initializing built-in extension Generic Event > Extension [ 5164.045] (II) Initializing built-in extension SHAPE [ > 5164.045] (II) Initializing built-in extension MIT-SHM [ 5164.045] > (II) Initializing built-in extension XInputExtension [ 5164.045] > (II) Initializing built-in extension XTEST [ 5164.045] (II) > Initializing built-in extension BIG-REQUESTS [ 5164.045] (II) > Initializing built-in extension SYNC [ 5164.045] (II) Initializing > built-in extension XKEYBOARD [ 5164.046] (II) Initializing built-in > extension XC-MISC [ 5164.046] (II) Initializing built-in extension > SECURITY [ 5164.046] (II) Initializing built-in extension XINERAMA [ > 5164.046] (II) Initializing built-in extension XFIXES [ 5164.046] > (II) Initializing built-in extension RENDER [ 5164.046] (II) > Initializing built-in extension RANDR [ 5164.046] (II) Initializing > built-in extension COMPOSITE [ 5164.046] (II) Initializing built-in > extension DAMAGE [ 5164.046] (II) SELinux: Disabled on system [ > 5164.059] (EE) AIGLX error: dlopen of > /usr/lib/i386-linux-gnu/dri/nouveau_dri.so failed > (/usr/lib/i386-linux-gnu/dri/nouveau_dri.so: cannot open shared > object file: No such file or directory) 3D hardware disabled... <snipped> That log makes little sense to me - where you modifying settings during this particular session? If so please:- boot up your box login (and startx) $ cat /var/log/Xorg.0.log > ~/xorg.log attach xorg.log to post. I haven't had a chance to test on identical hardware today - perhaps later in the week. I won't be able to test with the same Debian release - so I won't be able to guarantee it'll work :-( Cheers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e8955ac.8070...@gmail.com
