Xorg/xfce4 failing on Dual Processor G4 PowerMac's BUT Single Processor G4 PowerMac works (same boot SSD)...
Mark Millard
markmi at dsl-only.net
Sun Sep 7 00:05:51 UTC 2014
I finally asked myself "how many gdb's does FreeBSD have?". This lead me to building and using devel/gdb (/usr/local/bin/gdb). Experiments indicates /usr/local/bin/gdb works on Xorg on the G4's. (Xorg's build installs gcc47 and apparently needs a newer gdb to go with it.)
Thus I managed to get a little more information: /usr/local/bin/gdb reports for Xorg the likes of:
[Inferior 1 (process 1934) exited with code 026]
The process number varies but the exit code does not from test to test.
This happens with partial screen updates showing on screen, showing that I have managed to repeat the context fairly well despite /usr/local/bin/gdb being involved. (I temporarily replaced /usr/local/bin/X with a script that runs gdb on Xorg, feeding gdb some commands via -x file-name.)
Using Option "NoTrapSignals" in the xorg.conf does not change the reports or behavior. (Confirmed no-trap use via Xorg.0.log reporting the likes of: [ 2437.485] (**) Option "NoTrapSignals".)
As for the 1920x1200 "Unknown mode" notice... It is not an issue. Details follow.
I put a 1680x1050 ADC Display on a NVIDIA G5 PowerMac to see what would happen for startxfce4. It both:
(A) generated the xfsettingsd Unkown mode '1920x1200 @ 60.0' message that I reported earlier
and
(B) worked correctly overall, using the 1680x1050 size.
And after shutting down, putting back the 1920x1200 display, and trying again it reported 1680x1050 in the "Unknown mode" message: It is using a record of the prior setting to generate that message.
So it appears that the new "Unknown mode" message is unimportant.
===
Mark Millard
markmi at dsl-only.net
On Sep 6, 2014, at 8:15 AM, Mark Millard <markmi at dsl-only.net> wrote:
Overall not much has changed for the original problem in 10.1-PRERELEASE r270981 with a fresh Xorg/xfce4 build. Details follow. The NVIDIA context does have a new, additional oddity.
Updating to a fresh, from-scratch...
> FreeBSD FBSDG4S1 10.1-PRERELEASE FreeBSD 10.1-PRERELEASE #0 r270981: Wed Sep 3 04:01:09 UTC 2014 root at releng1.nyi.freebsd.org:/usr/obj/powerpc.powerpc/usr/src/sys/GENERIC powerpc
using portsnap fetch extract and building Xorg and xfce4 (and xscreensaver this time) still has the PowerMac G4 X11 UI hangups (well, Xorg and such quitting) after partial screen updates are (usually) visible. (I did not explicitly build anything with debug symbols for this round. I used the MANIFEST file and .txz files and bsdinstall --and did not buildworld nor did I buildkernel.)
The NVIDIA G4 got some interesting information in the script output file for the NVIDIA PowerMac G4 for a startxfce4 -- -logverbose 9:
> failed to set mtrr: File exists
>
> (xfsettingsd:1053): xfsettingsd-WARNING **: Unknown mode '1920x1200 @ 60.0' for output default.
The ADC display in use on one of the G5's has a 1920x1200 native pixel area. But the one on the G4 being used here is smaller: 1680x1050. The SSD had been booted and tested on that G5 first. (So may be that old size is recorded somewhere and is used even when it is not appropriate?) The displayed content actually looks to be not sized to match the display as of when it hangs. (This is new to this build: before as much as displayed seemed to have the right width/height [no wrap around]. So the size issue may be a new, independent issue.)
After the above 1920x1200 reference is the usual sort of indication of the Xorg quit:
> xfce4-session: Fatal IO error 35 (Resource temporarily unavailable) on X server :0.
> xfwm4: Fatal IO error 35 (Resource temporarily unavailable) on X server :0.0.
> Thunar: Fatal IO error 35 (Resource temporarily unavailable) on X server :0.
> xfsettingsd: Fatal IO error 35 (Resource temporarily unavailable) on X server :0.0.
> wrapper: Fatal IO error 35 (Resource temporarily unavailable) on X server :0.0.
> xinit: connection to X server lost
> wrapper: Fatal IO error 35 (Resource temporarily unavailable) on X server :0.0.
> root at FBSDG4S1:~ # Assertion failed: (ret != inval_id), function _XAllocID, file xcb_io.c, line 529.
But the "Assertion failed" notice is new, as may be the "wrapper" references. (ps -aud shows Xorg and the rest are gone while the display still shows the partial update status.) The Xorg.0.log shows for the size question:
> [ 415.724] (--) NV(0): DDC detected a DFP:
> [ 415.724] (II) NV(0): Manufacturer: APP Model: 9219 Serial#: 50201662
> [ 415.724] (II) NV(0): Year: 2004 Week: 13
> [ 415.724] (II) NV(0): EDID Version: 1.3
> [ 415.724] (II) NV(0): Digital Display Input
> [ 415.724] (II) NV(0): Max Image Size [cm]: horiz.: 43 vert.: 27
> [ 415.724] (II) NV(0): Gamma: 2.20
> [ 415.724] (II) NV(0): DPMS capabilities: Off
> [ 415.724] (II) NV(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
> [ 415.724] (II) NV(0): Default color space is primary color space
> [ 415.725] (II) NV(0): First detailed timing is preferred mode
> [ 415.725] (II) NV(0): redX: 0.640 redY: 0.330 greenX: 0.290 greenY: 0.600
> [ 415.725] (II) NV(0): blueX: 0.150 blueY: 0.060 whiteX: 0.312 whiteY: 0.329
> [ 415.725] (II) NV(0): Manufacturer's mask: 0
> [ 415.725] (II) NV(0): Supported detailed timing:
> [ 415.725] (II) NV(0): clock: 117.1 MHz Image Size: 433 x 270 mm
> [ 415.725] (II) NV(0): h_active: 1680 h_sync: 1744 h_sync_end 1776 h_blank_end 1840 h_border: 0
> [ 415.725] (II) NV(0): v_active: 1050 v_sync: 1053 v_sync_end 1056 v_blanking: 1062 v_border: 0
> [ 415.725] (II) NV(0): Monitor name: Apple Cinema
> [ 415.725] (II) NV(0): Monitor name: Display
> ...
> [ 415.729] (--) NV(0): CRTC 0 is currently programmed for DFP
> [ 415.729] (II) NV(0): Using DFP on CRTC 0
> [ 415.729] (--) NV(0): Panel size is 1680 x 1050
> [ 415.729] (II) NV(0): NOTE: This driver cannot reconfigure the BIOS-programmed size.
> [ 415.729] (II) NV(0): These dimensions will be used as the panel size for mode validation.
> [ 415.729] (II) NV(0): EDID vendor "APP", prod id 37401
> [ 415.729] (II) NV(0): Printing DDC gathered Modelines:
> [ 415.729] (II) NV(0): Modeline "1680x1050"x0.0 117.13 1680 1744 1776 1840 1050 1053 1056 1062 +hsync +vsync (63.7 kHz eP)
> [ 415.729] (II) NV(0): Panel is TMDS
> [ 415.729] (--) NV(0): VideoRAM: 131072 kBytes
> [ 415.729] (==) NV(0): Using gamma correction (1.0, 1.0, 1.0)
> [ 415.729] (II) NV(0): Monitor0: Using hsync range of 63.66-64.67 kHz
> [ 415.729] (II) NV(0): Monitor0: Using vrefresh range of 59.88-59.94 Hz
> [ 415.725] (II) NV(0): h_active: 1680 h_sync: 1744 h_sync_end 1776 h_blank_e
> nd 1840 h_border: 0
> [ 415.725] (II) NV(0): v_active: 1050 v_sync: 1053 v_sync_end 1056 v_blankin
> g: 1062 v_border: 0
> [ 415.725] (II) NV(0): Monitor name: Apple Cinema
> [ 415.725] (II) NV(0): Monitor name: Display
> ...
> [ 415.726] (II) NV(0): Probing for EDID on I2C bus B...
> [ 415.729] (II) NV(0): ... none found
> [ 415.729] (--) NV(0): CRTC 0 is currently programmed for DFP
> [ 415.729] (II) NV(0): Using DFP on CRTC 0
> [ 415.729] (--) NV(0): Panel size is 1680 x 1050
> [ 415.729] (II) NV(0): NOTE: This driver cannot reconfigure the BIOS-programme
> d size.
> [ 415.729] (II) NV(0): These dimensions will be used as the panel size for mod
> e validation.
> [ 415.729] (II) NV(0): EDID vendor "APP", prod id 37401
> [ 415.729] (II) NV(0): Printing DDC gathered Modelines:
> [ 415.729] (II) NV(0): Modeline "1680x1050"x0.0 117.13 1680 1744 1776 1840
> 1050 1053 1056 1062 +hsync +vsync (63.7 kHz eP)
> [ 415.729] (II) NV(0): Panel is TMDS
> [ 415.729] (--) NV(0): VideoRAM: 131072 kBytes
> [ 415.729] (==) NV(0): Using gamma correction (1.0, 1.0, 1.0)
> [ 415.729] (II) NV(0): Monitor0: Using hsync range of 63.66-64.67 kHz
> [ 415.729] (II) NV(0): Monitor0: Using vrefresh range of 59.88-59.94 Hz
> [ 415.729] (II) NV(0): Estimated virtual size for aspect ratio 1.5926 is 1680x1050
> [ 415.729] (II) NV(0): Clock range: 12.00 to 350.00 MHz
Then it has the long list of non-working sizes followed by:
> [ 415.732] (--) NV(0): Virtual size is 1680x1050 (pitch 1680)
> [ 415.732] (**) NV(0): *Driver mode "1680x1050": 117.1 MHz, 63.7 kHz, 59.9 Hz
> [ 415.732] (II) NV(0): Modeline "1680x1050"x59.9 117.13 1680 1744 1776 1840 1050 1053 1056 1062 +hsync +vsync (63.7 kHz ezP)
> [ 415.732] (**) NV(0): *Driver mode "1680x1050": 119.0 MHz, 64.7 kHz, 59.9 Hz
> [ 415.732] (II) NV(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz ez)
> [ 415.732] (**) NV(0): *Default mode "1400x1050": 122.0 MHz, 64.9 kHz, 60.0 Hz
> [ 415.732] (II) NV(0): Modeline "1400x1050"x60.0 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync (64.9 kHz zd)
> [ 415.732] (**) NV(0): *Default mode "1280x1024": 108.0 MHz, 64.0 kHz, 60.0 Hz
> [ 415.732] (II) NV(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz zd)
> [ 415.732] (**) NV(0): Display dimensions: (430, 270) mm
> [ 415.732] (**) NV(0): DPI set to (99, 98)
There is no mention of 1920 or of 1200 in the Xorg.0.log file. Nor does the xorg.conf file have size information.
I'd never guess from the Xorg.0.log that there was a problem --either the original one or the size one.
One new thing in the log file is that the tail has:
> [ 419.683] select returned 0
> [ 419.739] select returned 0
> [ 419.747] select returned 0
> [ 419.755] select returned 0
> [ 419.763] select returned 0
> [ 419.771] select returned 0
> [ 419.779] select returned 0
> [ 419.787] select returned 0
> ...
> [ 420.195] select returned 0
> [ 420.203] select returned 0
> [ 420.211] select returned 0
> [ 420.221] select returned 0
> [ 420.227] select returned 0
> [ 420.251] select returned 0
> [ 420.251] select returned 0
The Radeon board based PowerMac G4 that I tested does not report that size notice. It also has a 1680x1050 ADC display. Its Xorg.0.log also shows 1680x1050. Again the Xorg.0.log contents look normal, without an indication of failure. And the script file again shows a sudden, silent quit as the mode of failure (ps -aud showing that Xorg and such are gone while the display is still stuck before any Option-Fn):
> ...
> best_freq: 117132353
> best_feedback_div: 295
> best_frac_feedback_div: 0
> best_ref_div: 34
> best_post_div: 2
> restore memmap
> restore common
> restore crtc1
> restore pll1
> finished PLL1
> set RMX
> set FP1
> enable FP1
> disable TV
> Unhandled monitor type 0
> xfwm4: Fatal IO error 35 (Resource temporarily unavailable) on X server :0.0.
> xfce4-panel: Fatal IO error 35 (Resource temporarily unavailable) on X server :0.0.
> Thunar: Fatal IO error 35 (Resource temporarily unavailable) on X server :0.
> xinit: connection to X server lost
The partial display did not look to be the wrong size.
When I tried a PowerMac G5 booted from that same SSD with a 1680x1050 ADC display and a Radeon board startxfce4 worked fine. This also suggests that the 1920x1200 size issue is a new, separate problem with just the nv driver(?).
===
Mark Millard
markmi at dsl-only.net
On Sep 4, 2014, at 6:46 PM, Mark Millard <markmi at dsl-only.net> wrote:
The radeon G4 contexts do not report "failed to set mtrr: File exists": They seem to be silent about Xorg quitting early as far as error messages or warnings go (booted from that same SSD with xorg.conf for the radeon context). Again Xorg.0.log does not look interesting and stops before the problem. A script logfile shows:
> root at FBSDG4S0:~ # startxfce4 -- -logverbose 9^M
> /usr/local/bin/startxfce4: Starting X server
>
>
> X.Org X Server 1.12.4
> Release Date: 2012-08-27
> X Protocol Version 11, Revision 0
> Build Operating System: FreeBSD 10.0-STABLE powerpc
> Current Operating System: FreeBSD FBSDG4S0 10.0-STABLE FreeBSD 10.0-STABLE #0: T
> hu Sep 4 00:50:31 PDT 2014 root at FBSDG4S0:/usr/obj/usr/src/sys/GENERIC power
> pc
> Build Date: 04 September 2014 06:13:34AM
>
> Current version of pixman: 0.32.4
> Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
> Markers: (--) probed, (**) from config file, (==) default setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/Xorg.0.log", Time: Thu Sep 4 18:20:03 2014
> (==) Using config file: "/etc/X11/xorg.conf"
> XRANDR name: DVI-1
> Connector: DVI-I
> CRT2: INTERNAL_DAC2
> DFP1: INTERNAL_TMDS1
> DDC reg: 0x64
> XRANDR name: DVI-0
> Connector: DVI-I
> CRT1: INTERNAL_DAC1
> DFP2: INTERNAL_DVO1
> DDC reg: 0x60
> XRANDR name: S-video
> Connector: S-video
> TV1: INTERNAL_DAC2
> DDC reg: 0x0
> finished output detect: 0
> Unhandled monitor type 0
> finished output detect: 1
> finished output detect: 2
> finished all detect
> Unhandled monitor type 0
> Entering TV Save
> Save TV timing tables
> saveTimingTables: reading timing tables
> TV Save done
> disable FP1
> disable FP1
> disable TV
> disable FP1
> init memmap
> init common
> init crtc1
> init pll1
> freq: 117130000
> best_freq: 117132353
> best_feedback_div: 295
> best_frac_feedback_div: 0
> best_ref_div: 34
> best_post_div: 2
> restore memmap
> restore common
> restore crtc1
> restore pll1
> finished PLL1
> set RMX
> set FP1
> enable FP1
> disable TV
> xfce4-session: Fatal IO error 35 (Resource temporarily unavailable) on X server :0.
> xfwm4: Fatal IO error 35 (Resource temporarily unavailable) on X server :0.0.
> xinit: connection to X server lost
===
Mark Millard
markmi at dsl-only.net
On Sep 4, 2014, at 6:00 PM, Mark Millard <markmi at dsl-only.net> wrote:
The below includes it reporting getting a "failed to set mtrr: File exists" notice. (A Intel P6+ concept?)
I have since rebuilt (buildworld, kernel, installworld; portmaster -af) from the same /usr/src/... and /usr/ports/... on that same SSD based on /etc/make.conf having:
WITH_DEBUG_FILES=
WITHOUT_CLANG= # because otherwise it leads to buildworld failures with the above enabled
WITH_DEBUG=
Unfortunately uname -a loses the r268571 reference in the process, leaving less of a clue what the build is based on.
In this context the script logfile for running on a PowerMac G4 ends up recording "failed to set mtrr: File exists":
> root at FBSDG4S0:~ # startxfce4 -- -logverbose 9^M
> /usr/local/bin/startxfce4: Starting X server
>
>
> X.Org X Server 1.12.4
> Release Date: 2012-08-27
> X Protocol Version 11, Revision 0
> Build Operating System: FreeBSD 10.0-STABLE powerpc
> Current Operating System: FreeBSD FBSDG4S0 10.0-STABLE FreeBSD 10.0-STABLE #0: Thu Sep 4 00:50:31 PDT 2014 root at FBSDG4S0:/usr/obj/usr/src/sys/GENERIC powerpc
> Build Date: 04 September 2014 06:13:34AM
>
> Current version of pixman: 0.32.4
> Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
> Markers: (--) probed, (**) from config file, (==) default setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/Xorg.0.log", Time: Thu Sep 4 15:14:07 2014
> (==) Using config file: "/etc/X11/xorg.conf"
> failed to set mtrr: File exists
> xfce4-session: Fatal IO error 35 (Resource temporarily unavailable) on X server :0.
> xinit: connection to X server lost
> root at FBSDG4S0:~ # xfwm4: Fatal IO error 35 (Resource temporarily unavailable) on X server :0.0.
> root at FBSDG4S0:~ #
The G5 PowerMac does not display the "failed to set mtrr: File exists" message when booted from the same boot SSD and startxfce4 -- -logverbose 9 is used (but with xorg.conf's BusID changed to match the PowerMac7,11's BusID). The G5 context works fine. (I've not tried the single processor G4 context yet.)
Note: I'm using the G4 NVIDIA PowerMac for most G4 expirements because it allows me to Option-Fn to get to VTn and see thing there and so I can avoid reboots.
The last thing that dmesg -a shows after the G4 startxfce4 -- -logverbose 9 is my logging in as root:
> $ dmesg -a | tail
> Configuring syscons: blanktime.
> Performing sanity check on sshd configuration.
> Starting sshd.
> Starting sendmail_submit.
> Starting sendmail_msp_queue.
> Starting cron.
> Starting background file system checks in 60 seconds.
>
> Thu Sep 4 14:21:42 PDT 2014
> Sep 4 14:21:48 FBSDG4S0 login: ROOT LOGIN (root) ON ttyv0
I do not see anything earlier that looks to be of interest. About the only thing remotely error-like are some examples of "hid_get_item: Number of items truncated to 255".
/var/log/Xorg.0.log's ends in:
> [ 182.354] (II) Module mouse: vendor="X.Org Foundation"
> [ 182.354] compiled for 1.12.4, module version = 1.9.0
> [ 182.354] Module class: X.Org XInput Driver
> [ 182.354] ABI class: X.Org XInput driver, version 16.0
> [ 182.354] (II) Using input driver 'mouse' for 'Apple Optical USB Mouse'
> [ 182.354] (**) Apple Optical USB Mouse: always reports core events
> [ 182.354] (**) Option "Device" "/dev/sysmouse"
> [ 182.354] (==) Apple Optical USB Mouse: Protocol: "Auto"
> [ 182.354] (**) Apple Optical USB Mouse: always reports core events
> [ 182.355] (==) Apple Optical USB Mouse: Emulate3Buttons, Emulate3Timeout: 50
> [ 182.355] (**) Apple Optical USB Mouse: ZAxisMapping: buttons 4 and 5
> [ 182.355] (**) Apple Optical USB Mouse: Buttons: 5
> [ 182.355] (**) Option "config_info" "hal:/org/freedesktop/Hal/devices/usb_device_5ac_304_noserial_if0"
> [ 182.355] (II) XINPUT: Adding extended input device "Apple Optical USB Mouse" (type: MOUSE, id 7)
> [ 182.356] (**) Apple Optical USB Mouse: (accel) keeping acceleration scheme 1
> [ 182.356] (**) Apple Optical USB Mouse: (accel) acceleration profile 0
> [ 182.356] (**) Apple Optical USB Mouse: (accel) acceleration factor: 2.000
> [ 182.356] (**) Apple Optical USB Mouse: (accel) acceleration threshold: 4
> [ 182.356] (II) Apple Optical USB Mouse: SetupAuto: hw.iftype is 4, hw.model is 0
> [ 182.356] (II) Apple Optical USB Mouse: SetupAuto: protocol is SysMouse
I.e., the Xorg quit is silent. Again I do not see anything earlier that looks to be of interest.
Xorg is suddenly, silently quitting. And it is leaving all associated log files with older modification date/times/content from what I can tell. No core file either. "failed to set mtrr: File exists" may explain this. I've not started investigating it yet.
Side notes:
I've not investigated yet if there is a way around gdb Xorg's run :0 under powerpc/GENERIC getting:
> cannot get thread event message: generic error
and gdb's cont then getting:
> suspend error: generic error
I've also seen for other things I've tried with Xorg involved:
> cannot find new threads: generic error
and
> no thread to satisfy query
On the G5 PowerMac's using powerpc64/GENERIC64 boot SSD's I have no such problems with threading for gdb Xorg: only the powerpc/GENERIC boot SSD's have this problem and the gdb thread issues happen on G4's and G5's when booted from powerpc/GENERIC boot SSD's.
===
Mark Millard
markmi at dsl-only.net
On Sep 4, 2014, at 9:46 AM, Nathan Whitehorn <nwhitehorn at freebsd.org> wrote:
Anything in dmesg or in /var/log/Xorg.0.log? What happens if you set logverbose 9?
-Nathan
On 08/31/14 17:27, Mark Millard wrote:
> As an example of how sudden and arbitrary the silent-quit of the X server is:
>
> The partial display update currently on my ADC display has approximating the top 1/2 updated and the bottom half not updated (still black).
>
> But the boundary is somewhat interesting: The last updated raster/pixel line has its left side updated (a uniform grey desktop color) and its right side not updated (still black).
>
> So the silent abort stopped the update mid-raster/pixel line.
>
> ===
> Mark Millard
> markmi at dsl-only.net
>
> On Aug 31, 2014, at 4:49 PM, Mark Millard <markmi at dsl-only.net> wrote:
>
> [E-mail history trimmed this time.]
>
> I used script to log my startxfce4 command and what it produces. With only the ADC connected this results in various "Unhandled monitor type 0" notices as part of normal operation.
>
> The script output shows that the X server quit. There is no core file left in the directory.
>
> Thunar: Fatal IO error 35 (Resource temporarily unavailable) on X server :0.
> xfwm4: Fatal IO error 35 (Resource temporarily unavailable) on X server :0.0.
> xinit: connection to X server lost
> xfdesktop: Fatal IO error 35 (Resource temporarily unavailable) on X server :0.0.
>
> (xfsettingsd:984): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GPhoto2VolumeMonitor: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
> root at FBSDG4S0:~ # xfsettingsd: Fatal IO error 2 (No such file or directory) on X server :0.0.
>
> The full script file contents are:
>
> Script started on Sun Aug 31 16:34:12 2014
> You have mail.
> root at FBSDG4S0:~ # startxfce4^M
> /usr/local/bin/startxfce4: Starting X server
>
>
> X.Org X Server 1.12.4
> Release Date: 2012-08-27
> X Protocol Version 11, Revision 0
> Build Operating System: FreeBSD 10.0-STABLE powerpc
> Current Operating System: FreeBSD FBSDG4S0 10.0-STABLE FreeBSD 10.0-STABLE #0 r268571: Sun Jul 13 05:15:31 UTC 2014 root at grind.freebsd.org:/usr/obj/powerpc.powerpc/usr/src/sys/GENERIC powerpc
> Build Date: 21 July 2014 07:18:49PM
>
> Current version of pixman: 0.32.4
> Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
> Markers: (--) probed, (**) from config file, (==) default setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/Xorg.0.log", Time: Sun Aug 31 16:34:23 2014
> (==) Using config file: "/etc/X11/xorg.conf"
> XRANDR name: DVI-1
> Connector: DVI-I
> CRT2: INTERNAL_DAC2
> DFP1: INTERNAL_TMDS1
> DDC reg: 0x64
> XRANDR name: DVI-0
> Connector: DVI-I
> CRT1: INTERNAL_DAC1
> DFP2: INTERNAL_DVO1
> DDC reg: 0x60
> XRANDR name: S-video
> Connector: S-video
> TV1: INTERNAL_DAC2
> DDC reg: 0x0
> finished output detect: 0
> Unhandled monitor type 0
> finished output detect: 1
> finished output detect: 2
> finished all detect
> Unhandled monitor type 0
> Entering TV Save
> Save TV timing tables
> saveTimingTables: reading timing tables
> TV Save done
> disable FP1
> disable FP1
> disable TV
> disable FP1
> init memmap
> init common
> init crtc1
> init pll1
> freq: 117130000
> best_freq: 117132353
> best_feedback_div: 295
> best_frac_feedback_div: 0
> best_ref_div: 34
> best_post_div: 2
> restore memmap
> restore common
> restore crtc1
> restore pll1
> finished PLL1
> set RMX
> set FP1
> enable FP1
> disable TV
> Unhandled monitor type 0
> Thunar: Fatal IO error 35 (Resource temporarily unavailable) on X server :0.
> xfwm4: Fatal IO error 35 (Resource temporarily unavailable) on X server :0.0.
> xinit: connection to X server lost
> xfdesktop: Fatal IO error 35 (Resource temporarily unavailable) on X server :0.0.
>
> (xfsettingsd:984): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GPhoto2VolumeMonitor: org.freedesktop.DBus.Error.Disconnected: Connection was disconnected before a reply was received
> root at FBSDG4S0:~ # xfsettingsd: Fatal IO error 2 (No such file or directory) on X server :0.0.
>
> ===
> Mark Millard
> markmi at dsl-only.net
>
>
>
More information about the freebsd-ppc
mailing list