Prev: OpenSuses 11.0 & cpuset
Next: Servers down
From: JT on 14 Jul 2010 07:30 On 14/07/10 13:05, houghi wrote: > Darklight wrote: > >> I understood that, but i thought you were looking for a replacement because you >> thought sax2 was not going to be available any more . >> > It won't be in the future. SO better start looking for an alternative > now. > > houghi > Maybe missing the point here (English being my 2nd lingo ;-) ), but I myself haven't used sax2 for the better part of 5 years now. As it seems sax2 is phased out, might it be an idea to file an enhancement request for the features you need (multiscreening again?) to be incorporated in the replacing tools? -- Kind regards, JT
From: JT on 14 Jul 2010 08:27 On 14/07/10 14:03, houghi wrote: > JT wrote: > >> As it seems sax2 is phased out, might it be an idea to file an >> enhancement request for the features you need (multiscreening again?) to >> be incorporated in the replacing tools? >> > Sure. Good idea. And what are the replacing tools? > > houghi > In my case Suse handles all screen issues flawlessly (with nvidia drivers) since 10.3 or 11.0 (not sure exactly which one). No more need for sax2-ing before being able to use X. So whatever handles it under the hood might've missed some features. My guess is it's X itself, since I also read that xorg86.conf (or whatever) is obsolete nowadays or will be soon. -- Kind regards, JT
From: JT on 14 Jul 2010 10:24 On 14/07/10 14:59, houghi wrote: > JT wrote: > >>>> As it seems sax2 is phased out, might it be an idea to file an >>>> enhancement request for the features you need (multiscreening again?) to >>>> be incorporated in the replacing tools? >>>> >>>> >>> Sure. Good idea. And what are the replacing tools? >>> >>> >> In my case Suse handles all screen issues flawlessly (with nvidia >> drivers) since 10.3 or 11.0 (not sure exactly which one). No more need >> for sax2-ing before being able to use X. So whatever handles it under >> the hood might've missed some features. My guess is it's X itself, since >> I also read that xorg86.conf (or whatever) is obsolete nowadays or will >> be soon. >> > Yes, it is. However it does NOT do well with multple screens. Guessed that right.... ;-) > So there > is where sax used to come in. In not all cases does it do the things > right. In those cases you must edit xorg.conf. > I get the point - even before ;-). Correct me if I'm wrong, but isn't sax2 in it's essence not 'just' (albeit a very clever) an 'xorg.conf' editor? If that's so, that your real issue won't be solved by finding a replacement - hence my remark about the xorg86.conf becoming obsolete (in my config, there is no such file anymore). > And multiple screens are not that uncommon anymore as more and more > people have notebooks and netbooks. > They should become even more uncommon IMHO, and that's exactly why I suggested doing the enhancement request(s) ;-) > I am using dual screens for a pretty long time and only lately did I > start getting problems with them. There are many ways around it, but not > one like sax (used to be) as X seems to think it does not need xorg.conf > anymore. > > Well, I might be asking something stoopid as I want to use multiple > desktops AND use multiple screens at the same tim AND be able to select > different disktops on each different screens so I can still watch my > movie and/or tv. > Nothing _stupid_ about wanting your currently working setup to work in new versions as well, is there? > So that is why I wanted to start looking for a replacement. Unfortunatly > only one person cam with alternatives (thanks again) where all the rest > did not seem to understand the issue, which is completely my fault. > Not all the rest - I got it for one ;-). So no fault whatsoever, not even yours ;-) > Otherwise more people would have understood. > > So as far as I now understand: there is no replacement for sax2, because > everybody seems to be happy working with either NVidea or with one > screen, or KDE or GNOME. > > <cynical>If what is imporatnd is the number of people, then perhaps I > cab better start using Windows. All these lemmings can't be > wrong.</cynical> > One person can make a diff in the linux community in my experience. So again a good reason to enter the enhancement request(s) ;-) > houghi > I understand your frustration by the way. When running linux on the (b)le(a)eding edge, one tends to run into these kind of issues. Have got a list myself as well. What I try and do is find a workaround and after each install of a new version, I work through the list and see if the workaround's still needed. And sometimes you get lucky, but not in the sax2 case I guess. Hence my suggestion ....well you get my drift.... ;-) Good luck! -- Kind regards, JT
From: J G Miller on 14 Jul 2010 11:30 On Wed, 14 Jul 2010 17:25:26 +0200, houghi wrote: > Then perhaps what I am looking for is a replacement for X. :-D Have you not yet tried doing xorg -configure to generate an xorg.conf file? -configure When this option is specified, the Xorg server loads all video driver modules, probes for available hardware, and writes out an initial xorg.conf(5) file based on what was detected. This option currently has some problems on some platforms, but in most cases it is a good way to bootstrap the configuration process. This option is only available when the server is run as root (i.e, with real-uid 0).
From: JT on 15 Jul 2010 02:52
On 14/07/10 17:25, houghi wrote: > JT wrote: > >> I get the point - even before ;-). Correct me if I'm wrong, but isn't >> sax2 in it's essence not 'just' (albeit a very clever) an 'xorg.conf' >> editor? If that's so, that your real issue won't be solved by finding a >> replacement - hence my remark about the xorg86.conf becoming obsolete >> (in my config, there is no such file anymore). >> > Ah, ok. Misunderstood that. Then perhaps what I am looking for is a > replacement for X. :-D > > >>> And multiple screens are not that uncommon anymore as more and more >>> people have notebooks and netbooks. >>> >>> >> They should become even more uncommon IMHO, and that's exactly why I >> suggested doing the enhancement request(s) ;-) >> > Where? At X? Yes, at X. At least IMHO. Reason: sax2 generates xorg.conf and is being made obsolete, without replacement. Making something obsolete obliges one to take care of all functionality, or? Besides that: the xinerama stuff is typical X-stuff. Agreed: nvid_i_a does come into play as an underlying driver for hardware, but as long as sax2 is now used that is IMHO not a reason for 'them' to point to others than X development. As for window managers: they 'just' pick up on the X notion of screens and use that to position windows. Screens itself should not be handled by window managers - otherwise they should be renamed to screenmanagers? > They will most likely point to the desktop managers. > I have tried these kinds of things before. I can not get what I want in > KDE, GNOME, Windowmaker. Works in Enlightenment and XFCE. One points at > X the next saus it is the desktop, the next that the issue is an NVidea > problem. > > >> I understand your frustration by the way. When running linux on the >> (b)le(a)eding edge, one tends to run into these kind of issues. Have got >> a list myself as well. What I try and do is find a workaround and after >> each install of a new version, I work through the list and see if the >> workaround's still needed. And sometimes you get lucky, but not in the >> sax2 case I guess. Hence my suggestion ....well you get my drift.... ;-) >> > The problem is that not enough people seem to care. The 3D Compiz stuff > needs xinerama, so that gets all the attention. I spoke to some KDE and > GNOME developers and all I got was a blank stare. But erhaps that was > because they were still in shock because I told them I used Windowmaker. > > houghi > -- Kind regards, JT |