Anton Moiseev wrote:

Hi,

I have almost the same system configuration - opensuse 10.3, ati x1900xt and dual core athlon and I have also recently connected TV as the 2nd monitor.

The solution is not to use SAX to configure dual head mode - you need to run ATI Catalist control center:

...

amdcccle or find it in System/Configuration/Ati catalist...

I agree, that worked just fine. I only played with it briefly, but I had dual-mode upo and running in 5minutes. /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hi, I have tried the clone mode in the ATI Catalist. For me it worked - I saw 2 identical desktops with same windows and two mouse pointers (one per each) moving synchronously. The problem is that it allows to set only the same resolution for both screens. So, as soon as my 1st monitor had 1280x1024, the TV was also set to this resolution, so lower and left part of desktop were cut off. Then I have changed the resolution to something like 1280x768 (wide screen) - in this case the TV showed the whole desktop (with panel at the bottom etc); monitor showed also the whole desktop, but with bad proportions - so in this case I suppose you will have to choose which of this 2 bad options is better for you. As for me, I am using the monitor and TV in the "big desktop" mode - I have the main panel and desktop icons on my usual monitor (TV has nothing of that - it only shows wallpaper), but I can move mouse and windows to the right, so they appear on the TV - and if I maximize the window (video player for example) which is located on the TV, it occupies the whole TV area - so I can play film fullscreen on the TV, and to work on my usual monitor desktop as usual at the same time. On Feb 12, 2008 9:22 PM, Marc Chamberlin wrote:

Per Jessen wrote:

...

Anton Moiseev wrote:

...

Hi,

I have almost the same system configuration - opensuse 10.3, ati x1900xt and dual core athlon and I have also recently connected TV as the 2nd monitor.

The solution is not to use SAX to configure dual head mode - you need to run ATI Catalist control center:

...

amdcccle

or find it in System/Configuration/Ati catalist...

I agree, that worked just fine. I only played with it briefly, but I had dual-mode upo and running in 5minutes.

/Per Jessen, Zürich

Thanks Per and Anton for your suggestions but I am afraid it is still no joy in dual mode. BUT I am getting closer! I did try the ATI Catalysis Control Center for Linux (which appears to be a highly truncated version of the one supplied for Windows) and I specified I wanted two monitors running in clone mode. This resulted in an xorg.conf file with one additional option parameter that I had not set in my hand configured version.

Option "EnableMonitor" "crt1,tmds1"

(It also resulted in the same type of errors that aticonfig causes - decimal truncation in modeline specification lines and a blank line in the mode section which apparently confuses the X server.) But the second monitor, which I have set to run in a basic VESA 800x600 mode, still did not work. It is interesting that during boot up this second monitor does display the same info that is being displayed on the primary monitor. It was when the X windows server becomes active that the second monitor would stop displaying anything and reports that the signal it is receiving is out of specs. I am not configuring any special modelines for this second monitor, as like I said, it does work during bootup so I figure the default VESA modes should work for it even after the X server does become active. (I also tried 640x480 which made no difference either)

Further research (hunting around on the internet) lead me to another clue which was to add the following line to the Server Layout section to activate the second screen in the X server -

Screen 1 "aticonfig-Screen[1]" 0 0

This has lead to partial success!! The second monitor now displays a desktop but it is NOT a clone of the primary desktop. Instead it is some sort of plain vanilla desktop (no icons except for Trash, no background) and seems to be unreachable in that I cannot drag the mouse onto it or interact with it in any way. (My primary desktop to which I log in to has lots of icons and a background so would be easily recognizable had it been properly cloned onto this other monitor.)

I will attach my xorg.conf file just in case someone can see something that I am overlooking...

Marc... with only one functional head...

# /.../ # SaX generated X11 config file # Created on: 2007-11-04T12:31:58-0800. # # Version: 8.1 # Contact: Marcus Schaefer , 2005 # Contact: SaX-User list https://lists.berlios.de/mailman/listinfo/sax-users # # Automatically generated by [ISaX] (8.1) # PLEASE DO NOT EDIT THIS FILE! #

Section "ServerLayout" Identifier "Layout[all]" Screen 0 "aticonfig-Screen[0]" 0 0 Screen 1 "aticonfig-Screen[1]" 0 0 InputDevice "Keyboard[0]" "CoreKeyboard" InputDevice "Mouse[1]" "CorePointer" EndSection

Section "Files" InputDevices "/dev/gpmdata" InputDevices "/dev/input/mice" FontPath "/usr/share/fonts/misc:unscaled" FontPath "/usr/share/fonts/local" FontPath "/usr/share/fonts/75dpi:unscaled" FontPath "/usr/share/fonts/100dpi:unscaled" FontPath "/usr/share/fonts/Type1" FontPath "/usr/share/fonts/URW" FontPath "/usr/share/fonts/Speedo" FontPath "/usr/share/fonts/PEX" FontPath "/usr/share/fonts/cyrillic" FontPath "/usr/share/fonts/latin2/misc:unscaled" FontPath "/usr/share/fonts/latin2/75dpi:unscaled" FontPath "/usr/share/fonts/latin2/100dpi:unscaled" FontPath "/usr/share/fonts/latin2/Type1" FontPath "/usr/share/fonts/latin7/75dpi:unscaled" FontPath "/usr/share/fonts/baekmuk:unscaled" FontPath "/usr/share/fonts/japanese:unscaled" FontPath "/usr/share/fonts/kwintv" FontPath "/usr/share/fonts/truetype" FontPath "/usr/share/fonts/uni:unscaled" FontPath "/usr/share/fonts/CID" FontPath "/usr/share/fonts/ucs/misc:unscaled" FontPath "/usr/share/fonts/ucs/75dpi:unscaled" FontPath "/usr/share/fonts/ucs/100dpi:unscaled" FontPath "/usr/share/fonts/hellas/misc:unscaled" FontPath "/usr/share/fonts/hellas/75dpi:unscaled" FontPath "/usr/share/fonts/hellas/100dpi:unscaled" FontPath "/usr/share/fonts/hellas/Type1" FontPath "/usr/share/fonts/misc/sgi:unscaled" FontPath "/usr/share/fonts/xtest" FontPath "/opt/kde3/share/fonts" EndSection

Section "Module" Load "glx" Load "type1" Load "extmod" Load "dbe" Load "freetype" EndSection

Section "ServerFlags" Option "AllowMouseOpenFail" "on" EndSection

Section "InputDevice" Identifier "Keyboard[0]" Driver "kbd" Option "Protocol" "Standard" Option "XkbLayout" "us" Option "XkbModel" "microsoftpro" Option "XkbRules" "xfree86" EndSection

Section "InputDevice" Identifier "Mouse[1]" Driver "mouse" Option "Buttons" "9" Option "Device" "/dev/input/mice" Option "Name" "Belkin Wireless Keyboard/Mouse(2.4G)" Option "Protocol" "explorerps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection

Section "Modes" # Modeline "1920x1080v" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +vsync # Modeline "1920x1080i" 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace Identifier "Modes[0]" ModeLine "1920x1080ih" 66.33 1920 1960 2152 2384 1080 1081 1084 1113 +hsync interlace # ModeLine "1920x1080" 148.0 1920 2008 2052 2200 1080 1084 1089 1125 -hsync +vsync EndSection

Section "Monitor" Identifier "aticonfig-Monitor[0]" UseModes "Modes[0]" HorizSync 30.0 - 30.0 VertRefresh 43.0 - 60.0 Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" EndSection

Section "Monitor" Identifier "aticonfig-Monitor[1]" Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" EndSection

Section "Device" Identifier "aticonfig-Device[0]" Driver "fglrx" Option "DesktopSetup" "clone" Option "EnableMonitor" "crt1,tmds1" BusID "PCI:1:0:0" EndSection

Section "Device" Identifier "aticonfig-Device[1]" Driver "fglrx" BusID "PCI:1:0:0" Screen 1 EndSection

Section "Screen" Identifier "aticonfig-Screen[0]" Device "aticonfig-Device[0]" Monitor "aticonfig-Monitor[0]" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1920x1080ih" EndSubSection EndSection

Section "Screen" Identifier "aticonfig-Screen[1]" Device "aticonfig-Device[1]" Monitor "aticonfig-Monitor[1]" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "800x600" EndSubSection EndSection

Section "DRI" Group "video" Mode 0660 EndSection

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Sure, this is mine On Feb 13, 2008 12:53 AM, Marc Chamberlin wrote:

Anton, Per - Could I ask you to send me a copy of your xorg.conf file configured for working in clone mode? Perhaps I can spot a difference that I am not getting/overlooking.

Thanks... Marc...

Anton Moiseev wrote:

...

Hi,

I have tried the clone mode in the ATI Catalist. For me it worked - I saw 2 identical desktops with same windows and two mouse pointers (one per each) moving synchronously. The problem is that it allows to set only the same resolution for both screens. So, as soon as my 1st monitor had 1280x1024, the TV was also set to this resolution, so lower and left part of desktop were cut off. Then I have changed the resolution to something like 1280x768 (wide screen) - in this case the TV showed the whole desktop (with panel at the bottom etc); monitor showed also the whole desktop, but with bad proportions - so in this case I suppose you will have to choose which of this 2 bad options is better for you.

As for me, I am using the monitor and TV in the "big desktop" mode - I have the main panel and desktop icons on my usual monitor (TV has nothing of that - it only shows wallpaper), but I can move mouse and windows to the right, so they appear on the TV - and if I maximize the window (video player for example) which is located on the TV, it occupies the whole TV area - so I can play film fullscreen on the TV, and to work on my usual monitor desktop as usual at the same time.

On Feb 12, 2008 9:22 PM, Marc Chamberlin wrote:

...

Per Jessen wrote:

...

Anton Moiseev wrote:

...

Hi,

I have almost the same system configuration - opensuse 10.3, ati x1900xt and dual core athlon and I have also recently connected TV as the 2nd monitor.

The solution is not to use SAX to configure dual head mode - you need to run ATI Catalist control center:

...

amdcccle

or find it in System/Configuration/Ati catalist...

I agree, that worked just fine. I only played with it briefly, but I had dual-mode upo and running in 5minutes.

/Per Jessen, Zürich

Thanks Per and Anton for your suggestions but I am afraid it is still no joy in dual mode. BUT I am getting closer! I did try the ATI Catalysis Control Center for Linux (which appears to be a highly truncated version of the one supplied for Windows) and I specified I wanted two monitors running in clone mode. This resulted in an xorg.conf file with one additional option parameter that I had not set in my hand configured version.

Option "EnableMonitor" "crt1,tmds1"

(It also resulted in the same type of errors that aticonfig causes - decimal truncation in modeline specification lines and a blank line in the mode section which apparently confuses the X server.) But the second monitor, which I have set to run in a basic VESA 800x600 mode, still did not work. It is interesting that during boot up this second monitor does display the same info that is being displayed on the primary monitor. It was when the X windows server becomes active that the second monitor would stop displaying anything and reports that the signal it is receiving is out of specs. I am not configuring any special modelines for this second monitor, as like I said, it does work during bootup so I figure the default VESA modes should work for it even after the X server does become active. (I also tried 640x480 which made no difference either)

Further research (hunting around on the internet) lead me to another clue which was to add the following line to the Server Layout section to activate the second screen in the X server -

Screen 1 "aticonfig-Screen[1]" 0 0

This has lead to partial success!! The second monitor now displays a desktop but it is NOT a clone of the primary desktop. Instead it is some sort of plain vanilla desktop (no icons except for Trash, no background) and seems to be unreachable in that I cannot drag the mouse onto it or interact with it in any way. (My primary desktop to which I log in to has lots of icons and a background so would be easily recognizable had it been properly cloned onto this other monitor.)

I will attach my xorg.conf file just in case someone can see something that I am overlooking...

Marc... with only one functional head...

# /.../ # SaX generated X11 config file # Created on: 2007-11-04T12:31:58-0800. # # Version: 8.1 # Contact: Marcus Schaefer , 2005 # Contact: SaX-User list https://lists.berlios.de/mailman/listinfo/sax-users # # Automatically generated by [ISaX] (8.1) # PLEASE DO NOT EDIT THIS FILE! #

Section "ServerLayout" Identifier "Layout[all]" Screen 0 "aticonfig-Screen[0]" 0 0 Screen 1 "aticonfig-Screen[1]" 0 0 InputDevice "Keyboard[0]" "CoreKeyboard" InputDevice "Mouse[1]" "CorePointer" EndSection

Section "Files" InputDevices "/dev/gpmdata" InputDevices "/dev/input/mice" FontPath "/usr/share/fonts/misc:unscaled" FontPath "/usr/share/fonts/local" FontPath "/usr/share/fonts/75dpi:unscaled" FontPath "/usr/share/fonts/100dpi:unscaled" FontPath "/usr/share/fonts/Type1" FontPath "/usr/share/fonts/URW" FontPath "/usr/share/fonts/Speedo" FontPath "/usr/share/fonts/PEX" FontPath "/usr/share/fonts/cyrillic" FontPath "/usr/share/fonts/latin2/misc:unscaled" FontPath "/usr/share/fonts/latin2/75dpi:unscaled" FontPath "/usr/share/fonts/latin2/100dpi:unscaled" FontPath "/usr/share/fonts/latin2/Type1" FontPath "/usr/share/fonts/latin7/75dpi:unscaled" FontPath "/usr/share/fonts/baekmuk:unscaled" FontPath "/usr/share/fonts/japanese:unscaled" FontPath "/usr/share/fonts/kwintv" FontPath "/usr/share/fonts/truetype" FontPath "/usr/share/fonts/uni:unscaled" FontPath "/usr/share/fonts/CID" FontPath "/usr/share/fonts/ucs/misc:unscaled" FontPath "/usr/share/fonts/ucs/75dpi:unscaled" FontPath "/usr/share/fonts/ucs/100dpi:unscaled" FontPath "/usr/share/fonts/hellas/misc:unscaled" FontPath "/usr/share/fonts/hellas/75dpi:unscaled" FontPath "/usr/share/fonts/hellas/100dpi:unscaled" FontPath "/usr/share/fonts/hellas/Type1" FontPath "/usr/share/fonts/misc/sgi:unscaled" FontPath "/usr/share/fonts/xtest" FontPath "/opt/kde3/share/fonts" EndSection

Section "Module" Load "glx" Load "type1" Load "extmod" Load "dbe" Load "freetype" EndSection

Section "ServerFlags" Option "AllowMouseOpenFail" "on" EndSection

Section "InputDevice" Identifier "Keyboard[0]" Driver "kbd" Option "Protocol" "Standard" Option "XkbLayout" "us" Option "XkbModel" "microsoftpro" Option "XkbRules" "xfree86" EndSection

Section "InputDevice" Identifier "Mouse[1]" Driver "mouse" Option "Buttons" "9" Option "Device" "/dev/input/mice" Option "Name" "Belkin Wireless Keyboard/Mouse(2.4G)" Option "Protocol" "explorerps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection

Section "Modes" # Modeline "1920x1080v" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +vsync # Modeline "1920x1080i" 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace Identifier "Modes[0]" ModeLine "1920x1080ih" 66.33 1920 1960 2152 2384 1080 1081 1084 1113 +hsync interlace # ModeLine "1920x1080" 148.0 1920 2008 2052 2200 1080 1084 1089 1125 -hsync +vsync EndSection

Section "Monitor" Identifier "aticonfig-Monitor[0]" UseModes "Modes[0]" HorizSync 30.0 - 30.0 VertRefresh 43.0 - 60.0 Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" EndSection

Section "Monitor" Identifier "aticonfig-Monitor[1]" Option "VendorName" "ATI Proprietary Driver" Option "ModelName" "Generic Autodetecting Monitor" Option "DPMS" "true" EndSection

Section "Device" Identifier "aticonfig-Device[0]" Driver "fglrx" Option "DesktopSetup" "clone" Option "EnableMonitor" "crt1,tmds1" BusID "PCI:1:0:0" EndSection

Section "Device" Identifier "aticonfig-Device[1]" Driver "fglrx" BusID "PCI:1:0:0" Screen 1 EndSection

Section "Screen" Identifier "aticonfig-Screen[0]" Device "aticonfig-Device[0]" Monitor "aticonfig-Monitor[0]" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1920x1080ih" EndSubSection EndSection

Section "Screen" Identifier "aticonfig-Screen[1]" Device "aticonfig-Device[1]" Monitor "aticonfig-Monitor[1]" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "800x600" EndSubSection EndSection

Section "DRI" Group "video" Mode 0660 EndSection

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hi, I'm glad, that you have achieved some working solution. As for me, I was lucky and desided not to solve the problem in the xorg.conf file manually and searched the issue in the inet and found out that on ATI dual head can be configured only with Catalist - it saved me much time. With closed drivers it seems that the working solution can't be found following the usual logic - it would work only in the way programmers from ATI decided to do it, so I prefer to use only the standard tools they provide - like Catalist - and not to touch xorg.conf by myself. Regarding the system hang - I also have similar problems - they have appeared in latest drivers - there were no such problems, for example, in summer (but there were other problems). For example, I have updated the driver about a week ago, and now I can't log out from kde to gdm - I see the black screen and can only reboot with ctrl+alt+del (it was ok before this update). I also can't do init 3, init 5 to reset X - the system totally hangs. Probably there are more such problems. I only hope for the new open drivers written from opened specs, so probably in the next year my desktop would become stable. On Feb 13, 2008 11:04 PM, Marc Chamberlin wrote:

...

Sure, this is mine

On Feb 13, 2008 12:53 AM, Marc Chamberlin wrote:

...

Anton, Per - Could I ask you to send me a copy of your xorg.conf file configured for working in clone mode? Perhaps I can spot a difference that I am not getting/overlooking.

Thanks... Marc...

Thank you Anton for sending me your xorg.log file. It helped a lot in

Anton Moiseev wrote: the sense that it made me realize that there must be two very separate models on how video displays are being handled, fglrx has one and X11 has another, and the two are NOT well integrated. Apparently fglrx will handle, on its own, clone and big desktop displays and X11 handles dual head with separate desktop displays. When laying out the xorg.conf file this is very confusing and NOT will explained. The trick for me was to get rid of the separate screen, device and monitor sections of the xorg.conf file EVEN THOUGH I think it was aticonfig that had set them up initially for me. That had suggested I needed them for what I was trying to do. Instead, I have found out that what is required is you must set up the Mode2 option for the second monitor. Wow was I ever lead down the primrose path using that tool! The real problem with that tool is that it gives you NO guidance on how to set up a second monitor. Nowhere does it's help text or what little documentation supplied with it say that setting up the Mode2 options for the second monitor is required IF you are trying to use it in a clone mode. IMHO these tools (aticonfig, Sax2, Catalysis Control Center) are failing badly to meet the needs of users. Apparently expert levels of knowledge is a requirement in setting up the displays, they sure didn't GUIDE me to a good workable solution...

Anywise I now have both monitors working in a clone mode so that much is working. I still have the much more serious problem of the screen locking up on me and freezing the entire system. I will keep digging and if anyone has suggestions on how to track this down I sure will appreciate any an all help offered!

Also thanks Per for your help and Patrick for your news etiquette nanny services, writing to news groups is just another layer of rules, models, and non-intuitive practices one must learn in these difficult computer worlds. Not a whole lot different than setting up xorg.conf files...

Marc... now off to the next problem, why my system is freezing up which has strong suggestions of being yet another display related problem (see my earlier posts)....

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

I will start this conversation in a new thread, but this is a continuation of my efforts to get a new media center up an running. I have had a bit of a conversation about this already in the thread I started called "ATI fglrx driver problems"... My issue is that I am experiencing what appears on the surface to be a display problem, either X11 or ATI driver and my system will freeze up on me, usually within a few minutes after startup, and my only recourse is to do a reboot. There is some evidence and a couple of suggestions that this issue is cause by the current fglrx driver from ATI but further research on my part is leading me to question that assumption a bit... I have allowed my system to now go through a number of these lock ups and accumulate messages in the WARN file that is found in /var/logs. I am observing what appears to be a lot of semaphore problems within the fglrx driver but another pattern is also emerging. Just before most of these freezes I am seeing a daemon called audispd report "EOF read". From what I have found out the daemon is handling some sort of system events, I guess recording them and/or passing them on to other interested processes. (I am NOT a Linux guru so please bear with me....) I don't know if this message on reading an end of file ??? is a good thing or a bad thing so thought I would ask.... I will post examples of the more common sets of messages I am seeing when my system locks up and hopefully someone will be able to understand and enlighten me on what is going on... Feb 12 07:39:51 nova kernel: [fglrx:firegl_free_mutex] *ERROR* mutex id 0x00000002 not found in mutex list Feb 12 07:42:05 nova kernel: [fglrx:firegl_free_mutex] *ERROR* mutex id 0x00000004 not found in mutex list Feb 12 07:42:13 nova kernel: [fglrx:firegl_free_mutex] *ERROR* mutex id 0x00000005 not found in mutex list Feb 12 07:44:01 nova nmbd[3377]: [2008/02/12 07:44:01, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396) Feb 12 07:47:10 nova smartd[4225]: Problem creating device name scan list Feb 12 07:47:20 nova kdeinit[4142]: *** WARNING *** The programme 'kdeinit' uses the Apple Bonjour compatiblity layer of Avahi. Feb 12 07:47:20 nova kdeinit[4142]: *** WARNING *** Please fix your application to use the native API of Avahi! Feb 12 07:47:20 nova kdeinit[4142]: *** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=kdeinit Feb 12 07:50:06 nova xinetd[4266]: Exiting... Feb 12 07:50:06 nova audispd[3384]: input read: EOF Feb 12 07:50:11 nova nmbd[3425]: [2008/02/12 07:50:11, 0] nmbd/nmbd.c:terminate(58) Feb 12 07:50:11 nova nmbd[3425]: Got SIGTERM: going down.. Feb 12 08:16:31 nova kernel: [fglrx:firegl_free_mutex] *ERROR* mutex id 0x00000002 not found in mutex list Feb 12 08:16:32 nova powersaved[3916]: WARNING (CpufreqManagement:51) No capability cpufreq_control Feb 12 08:16:32 nova powersaved[3916]: WARNING (CpufreqManagement:51) No capability cpufreq_control Feb 12 08:16:32 nova powersaved[3916]: WARNING (continueEvent:248) Could not execute program /usr/lib/powersave/scripts for event daemon.scheme.change: No such file or directory Feb 12 08:16:38 nova smartd[4162]: Problem creating device name scan list Feb 12 09:00:44 nova kernel: [fglrx:firegl_free_mutex] *ERROR* mutex id 0x0000000e not found in mutex list Feb 12 09:00:50 nova kernel: [fglrx:firegl_free_mutex] *ERROR* mutex id 0x0000000f not found in mutex list Feb 12 09:13:00 nova sudo: pam_unix2(sudo:auth): conversation failed Feb 12 09:20:17 nova xinetd[4259]: Exiting... Feb 12 09:20:17 nova audispd[3399]: input read: EOF Feb 12 09:20:23 nova nmbd[3413]: [2008/02/12 09:20:23, 0] nmbd/nmbd.c:terminate(58) Feb 12 09:20:23 nova nmbd[3413]: Got SIGTERM: going down... (The following pattern happens most of the time without a prior significant/unaccounted for warning message....) Feb 12 09:28:36 nova xinetd[4186]: Exiting... Feb 12 09:28:43 nova audispd[3306]: input read: EOF Feb 12 09:28:43 nova nmbd[3314]: [2008/02/12 09:28:43, 0] nmbd/nmbd.c:terminate(58) Feb 12 09:28:43 nova nmbd[3314]: Got SIGTERM: going down... Feb 12 09:44:41 nova kernel: [fglrx:firegl_lock_free] *ERROR* lock was not held by 2! (*lock=0x00000001) Feb 12 09:44:41 nova kernel: [fglrx:firegl_unlock] *ERROR* firegl_lock_free failed! Feb 12 09:44:44 nova xinetd[4189]: Exiting... Feb 12 09:44:44 nova audispd[3332]: input read: EOF Feb 12 09:44:49 nova nmbd[3291]: [2008/02/12 09:44:49, 0] nmbd/nmbd.c:terminate(58) Feb 12 09:44:49 nova nmbd[3291]: Got SIGTERM: going down... Anyone got an idea on what these warning might be trying to tell me? Marc... still working on a sick puter... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org