Bug#461457: xorg: Doesn't honour DisplaySize

[Kevin Locke]

tags 461457 + upstream
thanks

It appears that this bug has already been reported upstream as bug
12474 https://bugs.freedesktop.org/show_bug.cgi?id=12474.
Apparently the DDC information is incorrectly taking precidence over
the DisplaySize configuration option.  See
http://gitweb.freedesktop.org/?p=xorg/xserver.git;a=commit;h=48ca5961caee62f2980017a6bdc96a1b4c747727
for the patch.

Cheers,
Kevin



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#461457: xorg: Doesn't honour DisplaySize

[Kevin Locke]

reassign 461457 xserver-xorg-core
forwarded 461457 https://bugs.freedesktop.org/show_bug.cgi?id=10582
merge 461457 421772
thanks

After further analysis, this bug is likely a duplicate of 421772.  To
be sure, it would still be nice to get copy of your xorg.conf and
Xorg.0.log.  ;)

Cheers,
Kevin



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#395888: xserver-xephyr: Missing Documentation

[Kevin Locke]

Package: xserver-xephyr
Version: 2:1.1.1-10
Severity: wishlist

It would be great if some documentation for Xephyr could be included
in the xserver-xephyr package; perhaps a manual page, or the Xephyr
README[1], or anything else that could help someone unfamiliar with
Xephyr get started.  Even adding a few common Xephyr invocations to
the Xephyr --help output might be enough, although somewhat terse.

Thanks,
Kevin

1.  http://webcvs.freedesktop.org/xserver/xserver/hw/kdrive/ephyr/README

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18.20061008a
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages xserver-xephyr depends on:
ii  libc62.3.6.ds1-4 GNU C Library: Shared libraries
ii  libfontenc1  1:1.0.2-2   X11 font encoding library
ii  libx11-6 2:1.0.3-2   X11 client-side library
ii  libxau6  1:1.0.1-2   X11 authorisation library
ii  libxdmcp61:1.0.1-2   X11 Display Manager Control Protoc
ii  libxext6 1:1.0.1-2   X11 miscellaneous extension librar
ii  libxfont11:1.2.2-1   X11 font rasterisation library
ii  zlib1g   1:1.2.3-13  compression library - runtime

Versions of packages xserver-xephyr recommends:
ii  xbase-clients 1:7.1.ds-3 miscellaneous X clients

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#338081: xserver-common: Promote xfonts-base from suggests to recommends

[Kevin Locke]

Package: xserver-common
Version: 6.8.2.dfsg.1-7
Severity: wishlist

It would be really great if xfonts-base were promoted from a suggests of
xserver-common to a recommends.  I realize this is certainly a debatable
issue, but I filed this wishlist bug to present my rationale under the
assumption that it could be marked wontfix if there is are compelling
reasons not to do so.

Given that the X server will not start without access to the fonts
provided by xfonts-base (either locally or remotely), it seems to fit
the policy definition of a strong dependency.  I believe it would also
be a benefit to our users, given that they could naively install
xserver-xorg (using a tool that automatically includes recommends) and
have a working X server after the install completes.  Although the
package is not required on setups where the fonts are externally
available, the only detriment to installing this package automatically
would be wasted filesystem space, as opposed to a non-functional X.  I
contend that it is better to err on the side of filesystem cruft than
ease of use.

Thanks for listening,
Kevin

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12.20050905a
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages xserver-common depends on:
ii  debconf [debconf-2.0] 1.4.58 Debian configuration management sy
ii  libc6 2.3.5-6GNU C Library: Shared libraries an
ii  x11-common6.8.2.dfsg.1-7 X Window System (X.Org) infrastruc

xserver-common recommends no packages.

-- debconf information excluded


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#254565: xserver-xfree86: [savage] two cursors display

[Kevin Locke]

I can also confirm this problem on an IBM Thinkpad T21.  The problem is
clearly related to the Hardware Cursor (since adding Option SWCursor
true to the XF86Config-4 solves the problem).  As mentioned in the
Savage(4) Manual Page [1], this option should be enabled by default On
Savage/MX and Savage/IX chips which are connected to LCDs, obviously it
is not being enabled by default, otherwise you would probably not be
seeing all of these messages. ;)

I attached the output of /usr/share/bug/xserver-xfree86  /tmp/output
31 (with the SWCursor option disabled, so you can see it fail to
switch to SWCursor mode).  I have also attached the output from lspci to
assist in specifically identifying the card.

Note:  I am using kernel 2.6.10, with the Debian patches applied, and
have the Enable DDC2 Support (CONFIG_FB_SAVAGE_I2C) suboption of the
S3 Savage Support compiled into the kernel (as well as the Savage
driver).  The description mentions that this option is used to get EDID
information from the attached display...  I do not know if it is
related, just a thought I had.

If there is any other information that I can provide, I would be happy
to do so.  Unfortunately, I am not familiar with the XFree86 drivers, so
I will probably not be much help in patching the code, but feel free to
ask if there is something that you think I can do to help.

Thanks,
Kevin

[1]  http://www.xfree86.org/4.3.0/savage.4.html
:00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(rev 03)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort+ SERR- PERR-
Latency: 64
Region 0: Memory at f800 (32-bit, prefetchable) [size=64M]
Capabilities: [a0] AGP version 1.0
Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 
64bit- FW- AGP3- Rate=x1,x2
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- 
Rate=none

:00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge 
(rev 03) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR-
Latency: 128
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
I/O behind bridge: f000-0fff
Memory behind bridge: f000-f7ff
Prefetchable memory behind bridge: fff0-000f
BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- Reset- FastB2B+

:00:02.0 CardBus bridge: Texas Instruments PCI1450 (rev 03)
Subsystem: IBM: Unknown device 0130
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR-
Latency: 168, Cache Line Size: 0x08 (32 bytes)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at 5000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=00, secondary=02, subordinate=05, sec-latency=176
Memory window 0: 1000-103ff000 (prefetchable)
Memory window 1: 1040-107ff000
I/O window 0: 4000-40ff
I/O window 1: 4400-44ff
BridgeCtl: Parity- SERR- ISA- VGA- MAbort- Reset+ 16bInt+ PostWrite+
16-bit legacy interface ports at 0001

:00:02.1 CardBus bridge: Texas Instruments PCI1450 (rev 03)
Subsystem: IBM: Unknown device 0130
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR-
Latency: 168, Cache Line Size: 0x08 (32 bytes)
Interrupt: pin B routed to IRQ 11
Region 0: Memory at 5010 (32-bit, non-prefetchable) [size=4K]
Bus: primary=00, secondary=06, subordinate=09, sec-latency=176
Memory window 0: 1080-10bff000 (prefetchable)
Memory window 1: 10c0-10fff000
I/O window 0: 4800-48ff
I/O window 1: 4c00-4cff
BridgeCtl: Parity- SERR- ISA- VGA- MAbort- Reset+ 16bInt+ PostWrite+
16-bit legacy interface ports at 0001

:00:03.0 Communication controller: Lucent Microelectronics WinModem 56k 
(rev 01)
Subsystem: CIS Technology Inc Lucent Win Modem
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR-
Interrupt: pin A routed to IRQ 11
Region 0: Memory at e8101000 (32-bit, non-prefetchable) [size=256]
Region 1: I/O ports at 1c00 [size=8]
Region 2: I/O ports at 1800 [size=256]
Capabilities: [f8] Power Management version 2