Bug#853153: It can't start by a segmentation fault
Steven wrote: > I don't have any LynxEM+ hardware to test with until next week, but I've > attached a patch for xserver-xorg-video-siliconmotion, if Jonny would > like to try rebuilding with this perhaps. Thank you! I ran the whole distance. Xorg.0.log Description: Binary data
Bug#853153: It can't start by a segmentation fault
Steven wrote: > Thanks. What exactly is this machine? IBM ThinkPad i 1200? It is a very old machine. > but there is not much detail in the backtrace. > > If you are able to install Xorg 1.19.1 again, please try to also install > xserver-xorg-video-siliconmotion-dbgsym and > xserver-xorg-core-dbgsym, from this APT respository: > > deb http://debug.mirrors.debian.org/debian-debug/ sid-debug main > > then the Xorg.log should give a more detailed backtrace. I am not made to make a core dumped even if I install it. Is there the necessary procedure any place other than "ulimit -c unlimited?"
Bug#853153: It can't start by a segmentation fault
Steven wrote: > Exactly what graphics hardware do you have? Please could you show > relevant output from dmesg/lspci describing what it is? Or even better, > a Xorg.log for the version that works correctly? I attached an output result of "lspci -vv" as "lspci.log." The log of Xorg of the version that can start is "1.18-Xorg.0.log." > Actually your log doesn't seem to describe any issue with graphics, but > rather something to do with dbus, either crashed or not running: > > | (EE) dbus-core: error connecting to system bus: > | org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket > | /var/run/dbus/system_bus_socket: No such file or directory) > > Did you try rebooting the machine before starting Xorg? Perhaps you > could find something relevant in your logs with: > $ cd /var/log && sudo grep dbus dpkg.log syslog The log that is in condition that dbus is installed is "1.19-Xorg.0.log." lspci.log Description: Binary data 1.18-Xorg.0.log Description: Binary data 1.19-Xorg.0.log Description: Binary data
Bug#853153: It can't start by a segmentation fault
Package: xserver-xorg-video-siliconmotion Version: 1:1.7.9-1 Severity: critical Hi, it was not able to start at all after I was rebuilt in xorg-server after 1.19. It can start in xserver-xorg-core 2:1.18.4-2 and xserver-xorg-video-siliconmiton 1:1.7.8-2. Xorg.0.log Description: Binary data xorg.conf Description: Binary data
Bug#526269: An afterimage occurs
Package: xserver-xorg-video-siliconmotion Version: 1:1.7.1-1 A screen becomes full of afterimages. It does not generate in 1:1.7.0-2. It seems that this commitment is the cause: http://cgit.freedesktop.org/xorg/driver/xf86-video-siliconmotion/commit/?id=abf1ba79f2bfe61f24cfa43deb0400d7c5f95bd5 When this patch was removed, the afterimage disappeared. lspci -v: 00:02.0 VGA compatible controller: Silicon Motion, Inc. SM712 LynxEM+ (rev a0) (prog-if 00 [VGA controller]) Subsystem: IBM Device 01a4 Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 10 Memory at 0e00 (32-bit, non-prefetchable) [size=16M] Expansion ROM at unassigned [disabled] Capabilities: [40] Power Management version 1 xorg.conf: Section Device Identifier Card0 Driver siliconmotion Option UseBIOS false Option AccelMethod exa EndSection -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#498359: It cannot use at all by fatal server error
Brice wrote: These patches have been applied upstream and 1.7.0 has been released. I'll try to package 1.7.0 today (for experimental only I think, is that fine for you?) Brice Thank you, I appreciate. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#498359: It cannot use at all by fatal server error
Hi, It solved by applying the following patch: http://lists.freedesktop.org/archives/xorg/2008-December/041044.html http://lists.freedesktop.org/archives/xorg/2008-December/041126.html http://bugs.freedesktop.org/show_bug.cgi?id=18816 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#499018: [Upstream Fixes] 3 possibilities of Blank Screen and performance issue.
François Wendling wrote:
* Debian/Upstream?, not fixed : autodetection fails, the
generated xorg.conf leads to a blank screen while starting X.
Then when it comes back to the vt, the vt turns blank, but i
can
still type commands blindly. It can be considered as
unusable, since i need to reboot to use the vt. I attach my
(ugly but working) xorg.conf that avoids this problem.
How is this patch?
--- a/src/smi_driver.c
+++ b/src/smi_driver.c
@@ -770,8 +770,8 @@
xf86DrvMsg(pScrn-scrnIndex, X_CONFIG, Option: UseBIOS %s.\n,
pSmi-useBIOS ? enabled : disabled);
} else {
- /* Default to UseBIOS enabled. */
- pSmi-useBIOS = TRUE;
+ /* Default to UseBIOS disabled. */
+ pSmi-useBIOS = FALSE;
}
if (xf86GetOptValBool(pSmi-Options, OPTION_ZOOMONLCD, pSmi-zoomOnLCD)) {
@@ -791,6 +791,7 @@
return FALSE;
}
+if (pSmi-useBIOS) {
if (xf86LoadSubModule(pScrn,int10)) {
xf86LoaderReqSymLists(int10Symbols,NULL);
pSmi-pInt10 = xf86InitInt10(pEnt-index);
@@ -800,6 +801,7 @@
xf86LoaderReqSymLists(vbeSymbols, NULL);
pVbe = VBEInit(pSmi-pInt10, pEnt-index);
}
+}
pSmi-PciInfo = xf86GetPciInfoForEntity(pEnt-index);
xf86RegisterResources(pEnt-index, NULL, ResExclusive);
@@ -893,6 +895,7 @@
/* detect the panel size */
SMI_DetectPanelSize(pScrn);
+if (pVbe) {
if (xf86LoadSubModule(pScrn, i2c)) {
xf86LoaderReqSymLists(i2cSymbols, NULL);
SMI_I2CInit(pScrn);
@@ -937,6 +940,7 @@
vbeFree(pVbe);
xf86FreeInt10(pSmi-pInt10);
pSmi-pInt10 = NULL;
+}
/*
* If the driver can do gamma correction, it should call xf86SetGamma()
@@ -1148,6 +1152,7 @@
}
}
+if (pVbe) {
/* Load ramdac if needed */
if (pSmi-hwcursor) {
if (!xf86LoadSubModule(pScrn, ramdac)) {
@@ -1157,6 +1162,7 @@
}
xf86LoaderReqSymLists(ramdacSymbols, NULL);
}
+}
if (pSmi-shadowFB) {
if (!xf86LoadSubModule(pScrn, shadowfb)) {
@@ -2032,7 +2038,7 @@
pEnt = xf86GetEntityInfo(pScrn-entityList[0]);
-if (!pSmi-pInt10) {
+if (!pSmi-pInt10 pSmi-useBIOS) {
pSmi-pInt10 = xf86InitInt10(pEnt-index);
}
fix_vt_blank.diff.gz
Description: Binary data
Bug#498359: It cannot use at all by fatal server error
Package: xserver-xorg-video-siliconmotion Version: 1:1.6.0-2 Severity: important Is xorg-server 1.5.0 supported? /var/log/Xorg.0.log: (II) Loading /usr/lib/xorg/modules//libexa.so (II) Module exa: vendor=X.Org Foundation compiled for 1.5.0, module version = 2.4.0 ABI class: X.Org Video Driver, version 4.1 (II) Loading sub module ramdac (II) LoadModule: ramdac (II) Module ramdac already built-in (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] -1 0 0x - 0x (0x1) MX[B] [1] -1 0 0x000f - 0x000f (0x1) MX[B] [2] -1 0 0x000c - 0x000e (0x3) MX[B] [3] -1 0 0x - 0x0009 (0xa) MX[B] [4] 0 0 0x000a - 0x000a (0x1) MS[B] [5] 0 0 0x000b - 0x000b7fff (0x8000) MS[B] [6] 0 0 0x000b8000 - 0x000b (0x8000) MS[B] [7] -1 0 0x - 0x (0x1) IX[B] [8] -1 0 0x - 0x (0x1) IX[B] [9] 0 0 0x03b0 - 0x03bb (0xc) IS[B] [10] 0 0 0x03c0 - 0x03df (0x20) IS[B] Fatal server error: AddScreen/ScreenInit failed for driver 0 xorg.conf.gz Description: Binary data Xorg.0.log.gz Description: Binary data
Bug#428711: xserver-xorg: xorg suddenly locks up Thinkpad
I have improved by applying this patch. http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-siliconmotion.git;a=commitdiff;h=8feca790a6e92799019237ac69a4ef618cacfaae However, dash shell sends a message called turning off NDELAY mode. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#458415: xserver-xorg-video-ati: Windows maximise beyond right of screen boundary
On Mon, 2007-12-31 at 13:21 +, Jonny Lamb wrote: After some fiddling, I fixed the problem by commenting out the VertRefresh option in the Monitor section of xorg.conf. I'm not sure whether the value was incorrect, or just having any value screwed it up. This doesn't feel like a particularly elegant or permanent solution, but I didn't have the time to investigate. Not sure if this has been noted, but if you czech out /usr/share/doc/xserver-xorg-video-ati/NEWS.Debian.gz then you find: xserver-xorg-video-ati (1:6.7.197-1) unstable; urgency=low * The X.Org ATI driver supports RandR 1.2 which enables dynamic enabling, disabling, resizing, rotating, placing, ... of multiple outputs at runtime. You might want to update your /etc/X11/xorg.conf accordingly. See http://wiki.debian.org/XStrikeForce/HowToRandR12 and http://www.intellinuxgraphics.org/dualhead.html for some help. -- Brice Goglin [EMAIL PROTECTED] Fri, 21 Dec 2007 08:12:13 +0100 Right at the top of the wiki page is my earlier suggestion of commenting/wiping parts of xorg.conf. Should've stuck to my guns! I guess this can be closed then as it's not really a bug..? P.S. Happy new year! -- Jonny Lamb, UK [EMAIL PROTECTED] http://jonnylamb.com GPG: 0x2E039402 signature.asc Description: This is a digitally signed message part
Bug#458415: xserver-xorg-video-ati: Windows maximise beyond right of screen boundary
Hi. On Mon, 2007-12-31 at 12:03 +, Tim Retout wrote: The set of available resolutions is a bit weird. $ xrandr -q Screen 0: minimum 320 x 200, current 1152 x 768, maximum 1280 x 1200 VGA-0 unknown connection 1152x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1280x800 60.0 1152x768 54.8* 800x60056.2 640x48059.9 LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis) 304mm x 228mm 1024x768 60.0*+ 800x60060.3 640x48059.9 S-video disconnected (normal left inverted right x axis y axis) I got exactly this issue a few days ago upon upgrading xorg on my laptop. I got the same weird[0] resolution which made apps mess around, and the same xrandr output. After some fiddling, I fixed the problem by commenting out the VertRefresh option in the Monitor section of xorg.conf. I'm not sure whether the value was incorrect, or just having any value screwed it up. This doesn't feel like a particularly elegant or permanent solution, but I didn't have the time to investigate. Hope this is slightly useful. [0] http://compsoc.dur.ac.uk/~jdl/screwed-resolution.png -- Jonny Lamb, UK [EMAIL PROTECTED] http://jonnylamb.com GPG: 0x2E039402 signature.asc Description: This is a digitally signed message part
Bug#428711: xserver-xorg: xorg suddenly locks up Thinkpad i1300/Silicon Motion
Hi, Is 1.2.99.901-1 or 1.2.99.902-1 generated? It is remembered that it was between 1.2.99.901-1 and 1.2.99.902-1 that the condition from which VT is set to blank screen by my machine began to occur. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
