From eric at snowmoon.com Wed Mar 2 15:08:07 2005 From: eric at snowmoon.com (Eric Warnke) Date: Wed, 02 Mar 2005 10:08:07 -0500 Subject: Make consolehelper more liske sudo? Message-ID: <4225D6D7.9010103@snowmoon.com> Hello all, I have unsucessfully been attempting to find out through both documentation, testing, and internet sources if I can get consolehelper to act more like sudo rather than su. Right now my problem is that there is NO WAY to roll this out to more users as a desktop alternative without giving them some power user ability ( printers, date and time, removable storage managment, ... ). Right now in order to give them access to these applications AFAICT I must either give the users the root password ( not gonna happen ) or create a pam.d file so that there is no password prompt ( pam_wheel with trust option ). Neither of these is a truly acceptable option at this point. Any change should try to keep the system as close to baseline as possible, I would prefer not to rip out the consolehelper system, but I will if I have to. The featureset I want is identical to sudo, but I will make accomidations as long as I can allow users to run a specific command after prompting for the users password. If anyone can point me in the right direction or just tell me that it's impossible with the current system that would be a great help. Cheers, Eric Warnke Systems Administer, Research ITS SUNY at Albany -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature URL: From hp at redhat.com Thu Mar 3 19:34:51 2005 From: hp at redhat.com (Havoc Pennington) Date: Thu, 03 Mar 2005 14:34:51 -0500 Subject: Make consolehelper more liske sudo? In-Reply-To: <4225D6D7.9010103@snowmoon.com> References: <4225D6D7.9010103@snowmoon.com> Message-ID: <1109878491.21167.15.camel@localhost.localdomain> On Wed, 2005-03-02 at 10:08 -0500, Eric Warnke wrote: > Hello all, > > I have unsucessfully been attempting to find out through both > documentation, testing, and internet sources if I can get consolehelper > to act more like sudo rather than su. Right now my problem is that > there is NO WAY to roll this out to more users as a desktop alternative > without giving them some power user ability ( printers, date and time, > removable storage managment, ... ). Right now in order to give them > access to these applications AFAICT I must either give the users the > root password ( not gonna happen ) or create a pam.d file so that there > is no password prompt ( pam_wheel with trust option ). Neither of these > is a truly acceptable option at this point. > > Any change should try to keep the system as close to baseline as > possible, I would prefer not to rip out the consolehelper system, but I > will if I have to. The featureset I want is identical to sudo, but I > will make accomidations as long as I can allow users to run a specific > command after prompting for the users password. You can probably just set things up with sudo... I'm not sure how involved that is. I do think consolehelper knows how to require user password instead of root password though. You may have more luck finding help with this on fedora-list or IRC than on this list. I'm not sure of the syntax myself but I'm pretty sure you want to edit the /etc/pam.d files. All this "end user desktop" stuff that requires root I consider a bug btw, if you want to file a bugzilla for the individual items that would be helpful. If you get NOTABUG/WONTFIX from someone at Red Hat let me know and I'll tell them they are wrong. Havoc From mattdm at mattdm.org Thu Mar 3 19:56:20 2005 From: mattdm at mattdm.org (Matthew Miller) Date: Thu, 3 Mar 2005 14:56:20 -0500 Subject: Make consolehelper more liske sudo? In-Reply-To: <4225D6D7.9010103@snowmoon.com> References: <4225D6D7.9010103@snowmoon.com> Message-ID: <20050303195620.GA15219@jadzia.bu.edu> On Wed, Mar 02, 2005 at 10:08:07AM -0500, Eric Warnke wrote: > I have unsucessfully been attempting to find out through both > documentation, testing, and internet sources if I can get consolehelper > to act more like sudo rather than su. Right now my problem is that > there is NO WAY to roll this out to more users as a desktop alternative > without giving them some power user ability ( printers, date and time, This may help. As of Fedora Core 3, the "UGROUPS" patch is in usermode. From the userhelper man page: UGROUPS A comma-separated list of groups whose members will be authen- ticated as if USER were set to the special value . If the invoking user is not a member of one of these groups, the name defined in USER will be used as normal. For example, setting UGROUPS to wheel and USER to root allows members of wheel (tra- ditionally used for administrative privileges) to authenticate with their own credentials and requires other users to provide the root password. So, for example, if /etc/security/console.apps/system-config-users looks like this: USER=root PROGRAM=/usr/share/system-config-users/system-config-users SESSION=true UGROUPS=wheel members of the wheel group will be able to authenticate with their own passwords, and others will need the root password. We've made this the default for all of the system-config-* apps here at BU for several years with good results; it might be nice to also make it the default in future versions of Fedora. (Although this is a pretty big default security policy change, it *is* basically the traditional meaning of the "wheel" group.) Caveat: I just noticed that the little "keys" gnome-panel icon doesn't work with this, and I'm trying to figure out what should be done about that. -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From mattdm at mattdm.org Thu Mar 3 20:02:35 2005 From: mattdm at mattdm.org (Matthew Miller) Date: Thu, 3 Mar 2005 15:02:35 -0500 Subject: Make consolehelper more liske sudo? In-Reply-To: <1109878491.21167.15.camel@localhost.localdomain> References: <4225D6D7.9010103@snowmoon.com> <1109878491.21167.15.camel@localhost.localdomain> Message-ID: <20050303200235.GB15060@jadzia.bu.edu> On Thu, Mar 03, 2005 at 02:34:51PM -0500, Havoc Pennington wrote: > All this "end user desktop" stuff that requires root I consider a bug > btw, if you want to file a bugzilla for the individual items that would > be helpful. If you get NOTABUG/WONTFIX from someone at Red Hat let me > know and I'll tell them they are wrong. I wouldn't want just anyone to have the ability to run many of the system-config apps just because they're sitting at the console, though. What do you think about making the UGROUPS=wheel thing the default? (Or some other group like "admin"....) We also patch system-config-users to have an easy checkbox for wheel group membership and to display that in a column on the Users tab (right after Primary Group). -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From davidz at redhat.com Thu Mar 3 20:31:13 2005 From: davidz at redhat.com (David Zeuthen) Date: Thu, 03 Mar 2005 15:31:13 -0500 Subject: Make consolehelper more liske sudo? In-Reply-To: <20050303200235.GB15060@jadzia.bu.edu> References: <4225D6D7.9010103@snowmoon.com> <1109878491.21167.15.camel@localhost.localdomain> <20050303200235.GB15060@jadzia.bu.edu> Message-ID: <1109881873.4422.49.camel@daxter.boston.redhat.com> On Thu, 2005-03-03 at 15:02 -0500, Matthew Miller wrote: >On Thu, Mar 03, 2005 at 02:34:51PM -0500, Havoc Pennington wrote: >> All this "end user desktop" stuff that requires root I consider a bug >> btw, if you want to file a bugzilla for the individual items that would >> be helpful. If you get NOTABUG/WONTFIX from someone at Red Hat let me >> know and I'll tell them they are wrong. > >I wouldn't want just anyone to have the ability to run many of the >system-config apps just because they're sitting at the console, though. What >do you think about making the UGROUPS=wheel thing the default? (Or some >other group like "admin"....) I don't think many of the system-config apps are "end user desktop" stuff at all. What needs to be fixed [1] though is at least printing, sound, display, software installation, date/time and network. Right now, in the default install, this requires the root password. I think that was the bug Havoc talked about. David [1] : here fixed can also mean replaced with something that more, uhm, suitable for desktop use - look at NetworkManager for an example From mattdm at mattdm.org Thu Mar 3 21:01:17 2005 From: mattdm at mattdm.org (Matthew Miller) Date: Thu, 3 Mar 2005 16:01:17 -0500 Subject: Make consolehelper more liske sudo? In-Reply-To: <1109881873.4422.49.camel@daxter.boston.redhat.com> References: <4225D6D7.9010103@snowmoon.com> <1109878491.21167.15.camel@localhost.localdomain> <20050303200235.GB15060@jadzia.bu.edu> <1109881873.4422.49.camel@daxter.boston.redhat.com> Message-ID: <20050303210117.GA17833@jadzia.bu.edu> On Thu, Mar 03, 2005 at 03:31:13PM -0500, David Zeuthen wrote: > I don't think many of the system-config apps are "end user desktop" > stuff at all. What needs to be fixed [1] though is at least printing, > sound, display, software installation, date/time and network. Right now, > in the default install, this requires the root password. I think that > was the bug Havoc talked about. I don't consider date/time to be "end user". That should be managed through ntp, which shouldn't be just tweaked at the whim of whoever sits down at the box. (Setting the *user's* timezone is a different issue.) Display, sound, and local printing should Just Work, and network where possible. I'll not touch the details of printer configuration right now. :) Software installation *definitely* needs some sort of authentication and special privilege. Sure, this needs to be made so it's not intimidating, but we also shouldn't shoot ourselves in the head. -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From hp at redhat.com Thu Mar 3 21:02:57 2005 From: hp at redhat.com (Havoc Pennington) Date: Thu, 03 Mar 2005 16:02:57 -0500 Subject: Make consolehelper more liske sudo? In-Reply-To: <20050303200235.GB15060@jadzia.bu.edu> References: <4225D6D7.9010103@snowmoon.com> <1109878491.21167.15.camel@localhost.localdomain> <20050303200235.GB15060@jadzia.bu.edu> Message-ID: <1109883778.21167.27.camel@localhost.localdomain> On Thu, 2005-03-03 at 15:02 -0500, Matthew Miller wrote: > On Thu, Mar 03, 2005 at 02:34:51PM -0500, Havoc Pennington wrote: > > All this "end user desktop" stuff that requires root I consider a bug > > btw, if you want to file a bugzilla for the individual items that would > > be helpful. If you get NOTABUG/WONTFIX from someone at Red Hat let me > > know and I'll tell them they are wrong. > > I wouldn't want just anyone to have the ability to run many of the > system-config apps just because they're sitting at the console, though. What > do you think about making the UGROUPS=wheel thing the default? (Or some > other group like "admin"....) > > We also patch system-config-users to have an easy checkbox for wheel group > membership and to display that in a column on the Users tab (right after > Primary Group). As David says, sometimes this is sort of complicated. e.g. for NetworkManager we changed the architecture to be asking for certain things from the user session, vs. writing out an arbitrary config file. He's also right that some of the system-config-* aren't desktop oriented at all (or they at least include a bunch of non-desktop stuff in addition) So the fix may not be as simple as changing the pam setup, but it's still broken right now. One problem is that if you can run a GTK app as root (anything equivalent to setgid) then you can probably hack that app and do bad stuff, http://gtk.org/setuid.html So it's probably a requirement in all cases that we split out a backend that runs as root and have the UI separate. Havoc From hp at redhat.com Thu Mar 3 21:10:18 2005 From: hp at redhat.com (Havoc Pennington) Date: Thu, 03 Mar 2005 16:10:18 -0500 Subject: Make consolehelper more liske sudo? In-Reply-To: <20050303210117.GA17833@jadzia.bu.edu> References: <4225D6D7.9010103@snowmoon.com> <1109878491.21167.15.camel@localhost.localdomain> <20050303200235.GB15060@jadzia.bu.edu> <1109881873.4422.49.camel@daxter.boston.redhat.com> <20050303210117.GA17833@jadzia.bu.edu> Message-ID: <1109884218.21167.35.camel@localhost.localdomain> On Thu, 2005-03-03 at 16:01 -0500, Matthew Miller wrote: > On Thu, Mar 03, 2005 at 03:31:13PM -0500, David Zeuthen wrote: > > I don't think many of the system-config apps are "end user desktop" > > stuff at all. What needs to be fixed [1] though is at least printing, > > sound, display, software installation, date/time and network. Right now, > > in the default install, this requires the root password. I think that > > was the bug Havoc talked about. > > I don't consider date/time to be "end user". That should be managed through > ntp, which shouldn't be just tweaked at the whim of whoever sits down at the > box. (Setting the *user's* timezone is a different issue.) Probably depends on the deployment or situation. The additional point about all this "be sure end users can do desktop stuff without root" is that we should have some kind of easy way to enable/disable their ability to do particular things. > Display, sound, and local printing should Just Work, and network where > possible. I'll not touch the details of printer configuration right now. :) > > Software installation *definitely* needs some sort of authentication and > special privilege. Sure, this needs to be made so it's not intimidating, but > we also shouldn't shoot ourselves in the head. For a managed client (with IT staff) then normally the IT dept will own all software installation, but for a home desktop the end user should be able to do it. The trick is to enable that without allowing an app running as the user to do it, in order to preserve safety vs. viruses etc. There was a thread about this a while back. One approach is that if you aren't root, you can only install signed packages; and you have to be root to add new trusted keys. The "setuid" process would be simple and just check the signature, then invoke the full installer. I think software installation without root is less important than the other stuff for now, since we have a ton of other problems in a "home nontechnical user" environment anyhow. And software installation by users isn't useful in an organization with IT staff. Though I guess I *can* imagine a setup where users can install any software that is signed by the particular IT department, that could be useful. Probably not "best practice" but conceivably useful. Havoc From eric at snowmoon.com Thu Mar 3 21:08:45 2005 From: eric at snowmoon.com (Eric Warnke) Date: Thu, 03 Mar 2005 16:08:45 -0500 Subject: Make consolehelper more liske sudo? In-Reply-To: <1109883778.21167.27.camel@localhost.localdomain> References: <4225D6D7.9010103@snowmoon.com> <1109878491.21167.15.camel@localhost.localdomain> <20050303200235.GB15060@jadzia.bu.edu> <1109883778.21167.27.camel@localhost.localdomain> Message-ID: <42277CDD.5070500@snowmoon.com> Thanks everyone, the UGROUPS worked, not the way I would like, but it worked. Is there any more documentation for these config files? I would suggest that the lack of ANY decent installed documentation ( man pages /usr/share/doc/ ) on either consolehelper or usermode be consitered a bug. Cheers, Eric Havoc Pennington wrote: >As David says, sometimes this is sort of complicated. e.g. for >NetworkManager we changed the architecture to be asking for certain >things from the user session, vs. writing out an arbitrary config file. > >He's also right that some of the system-config-* aren't desktop oriented >at all (or they at least include a bunch of non-desktop stuff in >addition) > >So the fix may not be as simple as changing the pam setup, but it's >still broken right now. > >One problem is that if you can run a GTK app as root (anything >equivalent to setgid) then you can probably hack that app and do bad >stuff, http://gtk.org/setuid.html > >So it's probably a requirement in all cases that we split out a backend >that runs as root and have the UI separate. > >Havoc > > > > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 252 bytes Desc: OpenPGP digital signature URL: From mattdm at mattdm.org Thu Mar 3 21:12:34 2005 From: mattdm at mattdm.org (Matthew Miller) Date: Thu, 3 Mar 2005 16:12:34 -0500 Subject: Make consolehelper more liske sudo? In-Reply-To: <1109883778.21167.27.camel@localhost.localdomain> References: <4225D6D7.9010103@snowmoon.com> <1109878491.21167.15.camel@localhost.localdomain> <20050303200235.GB15060@jadzia.bu.edu> <1109883778.21167.27.camel@localhost.localdomain> Message-ID: <20050303211234.GA18871@jadzia.bu.edu> On Thu, Mar 03, 2005 at 04:02:57PM -0500, Havoc Pennington wrote: > One problem is that if you can run a GTK app as root (anything > equivalent to setgid) then you can probably hack that app and do bad > stuff, http://gtk.org/setuid.html > So it's probably a requirement in all cases that we split out a backend > that runs as root and have the UI separate. Yes, sounds very sane. Plus, as long as we're using SELinux, that could definitely help here. -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From davidz at redhat.com Thu Mar 3 21:19:52 2005 From: davidz at redhat.com (David Zeuthen) Date: Thu, 03 Mar 2005 16:19:52 -0500 Subject: Make consolehelper more liske sudo? In-Reply-To: <20050303210117.GA17833@jadzia.bu.edu> References: <4225D6D7.9010103@snowmoon.com> <1109878491.21167.15.camel@localhost.localdomain> <20050303200235.GB15060@jadzia.bu.edu> <1109881873.4422.49.camel@daxter.boston.redhat.com> <20050303210117.GA17833@jadzia.bu.edu> Message-ID: <1109884793.4422.60.camel@daxter.boston.redhat.com> On Thu, 2005-03-03 at 16:01 -0500, Matthew Miller wrote: >I don't consider date/time to be "end user". That should be managed through >ntp, which shouldn't be just tweaked at the whim of whoever sits down at the >box. (Setting the *user's* timezone is a different issue.) You need to be able to change timezone when traveling. User may also not be on a network so you cannot rely on a NTP server. >Display, sound, and local printing should Just Work, and network where >possible. I'll not touch the details of printer configuration right now. :) > Heh :-) >Software installation *definitely* needs some sort of authentication and >special privilege. Sure, this needs to be made so it's not intimidating, but >we also shouldn't shoot ourselves in the head. I knew this would come up :-) o Why should installing updates and software that is *signed* by a key that the admin chooses to trust require root? o IIRC you can already install "software" as a non-privileged user for e.g. Firefox - my point is that there is more to installing software than just RPM In all cases we of course need to guard against viruses and malware so only certain trusted programs are allowed to do these actions. SELinux and D-BUS can help here, e.g. we might use a SE-Linux label for system-config-packages (and make sure LD_PRELOAD exploits are not possible) that allows interaction with a root process via D-BUS that performs the installation. David From mattdm at mattdm.org Thu Mar 3 21:41:33 2005 From: mattdm at mattdm.org (Matthew Miller) Date: Thu, 3 Mar 2005 16:41:33 -0500 Subject: Make consolehelper more liske sudo? In-Reply-To: <1109884793.4422.60.camel@daxter.boston.redhat.com> References: <4225D6D7.9010103@snowmoon.com> <1109878491.21167.15.camel@localhost.localdomain> <20050303200235.GB15060@jadzia.bu.edu> <1109881873.4422.49.camel@daxter.boston.redhat.com> <20050303210117.GA17833@jadzia.bu.edu> <1109884793.4422.60.camel@daxter.boston.redhat.com> Message-ID: <20050303214133.GA19736@jadzia.bu.edu> On Thu, Mar 03, 2005 at 04:19:52PM -0500, David Zeuthen wrote: > >I don't consider date/time to be "end user". That should be managed through > >ntp, which shouldn't be just tweaked at the whim of whoever sits down at the > >box. (Setting the *user's* timezone is a different issue.) > You need to be able to change timezone when traveling. User may also not > be on a network so you cannot rely on a NTP server. You shouldn't have to change the *system* timezone, though. $ echo $TZ America/New_York $ date Thu Mar 3 16:34:40 EST 2005 $ export TZ=Japan $ date Fri Mar 4 06:35:17 JST 2005 Personally, I think the system timezone should *always* be GMT, and local time always set per-user. (There could be a system default TZ, of course.) But that's a different discussion. :) > o Why should installing updates and software that is *signed* > by a key that the admin chooses to trust require root? Because it could affect other users in unpredictable ways. > o IIRC you can already install "software" as a non-privileged user > for e.g. Firefox - my point is that there is more to installing > software than just RPM Right -- that's okay, because privilege separation reduces the possible impact on others. -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From hp at redhat.com Thu Mar 3 23:10:09 2005 From: hp at redhat.com (Havoc Pennington) Date: Thu, 03 Mar 2005 18:10:09 -0500 Subject: Make consolehelper more liske sudo? In-Reply-To: <20050303214133.GA19736@jadzia.bu.edu> References: <4225D6D7.9010103@snowmoon.com> <1109878491.21167.15.camel@localhost.localdomain> <20050303200235.GB15060@jadzia.bu.edu> <1109881873.4422.49.camel@daxter.boston.redhat.com> <20050303210117.GA17833@jadzia.bu.edu> <1109884793.4422.60.camel@daxter.boston.redhat.com> <20050303214133.GA19736@jadzia.bu.edu> Message-ID: <1109891409.21167.49.camel@localhost.localdomain> On Thu, 2005-03-03 at 16:41 -0500, Matthew Miller wrote: > > > o Why should installing updates and software that is *signed* > > by a key that the admin chooses to trust require root? > > Because it could affect other users in unpredictable ways. > Not on a single-user laptop. There has to be local site policy at some point to get things right. Havoc From pbhat at ongc.net Sat Mar 5 13:52:52 2005 From: pbhat at ongc.net (Parameshwara Bhat) Date: Sat, 05 Mar 2005 19:22:52 +0530 Subject: An ordinary user's perspective of Linux (was Re: Make consolehelper more liske sudo?) In-Reply-To: <20050304170018.C6E9773A2C@hormel.redhat.com> References: <20050304170018.C6E9773A2C@hormel.redhat.com> Message-ID: Dear List, I am a curious member of this list and an ordinary user of Linux ; so excuse me for breaking into a learned debate.I want to give a perspective of my end,following the threads between Havoc, Matthew and David. I use Fedora at home and office. Nowhere I can have the support of learned linux experts at my beck and call; Also, I have installed the OS and created root and other users. All passwords are available with me.Working as a user,by the number of times I have to invoke 'root',I wonder why I should not be working as root itself ?. By the discussions I have seen here and elsewhere, it appears most linux experts and creators are basically contemptous of such a user as me. I am sane, responsible and intelligent, but just not a linux expert. I have my job and I want computer to be an unhindering aid and a provider of entertainment.Why should I be required to know the intricacies of the OS ? When the CD is locked and unmountable, unejectable; profound sermons on the security aspects of linux hardly makes sense. While completely respecting the concerns of security and stability; borderlines of zones and the security matrix can always be redefined and redesigned if you know exactly what you want to give the end user.OS and programs like shirts and pants need to be tailored to users. I am a devoted user of Linux and Fedora. But what a stupid it makes of me! Without the root password I just cannot imagine keeping this box running and making any use of it.In a regulated office environment(unlike mine)where I wouldn't be having the root password, I do not think I will be able to use it with any amount of ease.In contrast, much maligned Windows pampers me!So nice and considerate of my needs with all it's flaws and weaknesses.Without the root password and a great deal of 'googli'ng and 'maillist'ng, I couldnot have sustained Linux on this box. Again,compare this with Windows. When will Linux and Fedora learn to respect me and users like me or will it at all? Answer to that will be the key to whether it can really compete with MS Parameshwara Bhat On Fri, 4 Mar 2005 12:00:18 -0500 (EST), wrote: > Send Fedora-desktop-list mailing list submissions to > fedora-desktop-list at redhat.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://www.redhat.com/mailman/listinfo/fedora-desktop-list > or, via email, send a message with subject or body 'help' to > fedora-desktop-list-request at redhat.com > > You can reach the person managing the list at > fedora-desktop-list-owner at redhat.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Fedora-desktop-list digest..." > > > Today's Topics: > > 1. Re: Make consolehelper more liske sudo? (Havoc Pennington) > 2. Re: Make consolehelper more liske sudo? (Matthew Miller) > 3. Re: Make consolehelper more liske sudo? (Matthew Miller) > 4. Re: Make consolehelper more liske sudo? (David Zeuthen) > 5. Re: Make consolehelper more liske sudo? (Matthew Miller) > 6. Re: Make consolehelper more liske sudo? (Havoc Pennington) > 7. Re: Make consolehelper more liske sudo? (Havoc Pennington) > 8. Re: Make consolehelper more liske sudo? (Eric Warnke) > 9. Re: Make consolehelper more liske sudo? (Matthew Miller) > 10. Re: Make consolehelper more liske sudo? (David Zeuthen) > 11. Re: Make consolehelper more liske sudo? (Matthew Miller) > 12. Re: Make consolehelper more liske sudo? (Havoc Pennington) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 03 Mar 2005 14:34:51 -0500 > From: Havoc Pennington > Subject: Re: Make consolehelper more liske sudo? > To: Discussions about development for the Fedora desktop > > Message-ID: <1109878491.21167.15.camel at localhost.localdomain> > Content-Type: text/plain > > On Wed, 2005-03-02 at 10:08 -0500, Eric Warnke wrote: >> Hello all, >> >> I have unsucessfully been attempting to find out through both >> documentation, testing, and internet sources if I can get consolehelper >> to act more like sudo rather than su. Right now my problem is that >> there is NO WAY to roll this out to more users as a desktop alternative >> without giving them some power user ability ( printers, date and time, >> removable storage managment, ... ). Right now in order to give them >> access to these applications AFAICT I must either give the users the >> root password ( not gonna happen ) or create a pam.d file so that there >> is no password prompt ( pam_wheel with trust option ). Neither of these >> is a truly acceptable option at this point. >> >> Any change should try to keep the system as close to baseline as >> possible, I would prefer not to rip out the consolehelper system, but I >> will if I have to. The featureset I want is identical to sudo, but I >> will make accomidations as long as I can allow users to run a specific >> command after prompting for the users password. > > You can probably just set things up with sudo... I'm not sure how > involved that is. > > I do think consolehelper knows how to require user password instead of > root password though. You may have more luck finding help with this on > fedora-list or IRC than on this list. I'm not sure of the syntax myself > but I'm pretty sure you want to edit the /etc/pam.d files. > > All this "end user desktop" stuff that requires root I consider a bug > btw, if you want to file a bugzilla for the individual items that would > be helpful. If you get NOTABUG/WONTFIX from someone at Red Hat let me > know and I'll tell them they are wrong. > > Havoc > > > > > ------------------------------ > > Message: 2 > Date: Thu, 3 Mar 2005 14:56:20 -0500 > From: Matthew Miller > Subject: Re: Make consolehelper more liske sudo? > To: Discussions about development for the Fedora desktop > > Message-ID: <20050303195620.GA15219 at jadzia.bu.edu> > Content-Type: text/plain; charset=us-ascii > > On Wed, Mar 02, 2005 at 10:08:07AM -0500, Eric Warnke wrote: >> I have unsucessfully been attempting to find out through both >> documentation, testing, and internet sources if I can get consolehelper >> to act more like sudo rather than su. Right now my problem is that >> there is NO WAY to roll this out to more users as a desktop alternative >> without giving them some power user ability ( printers, date and time, > > This may help. As of Fedora Core 3, the "UGROUPS" patch is in usermode. > From > the userhelper man page: > > UGROUPS > A comma-separated list of groups whose members will be authen- > ticated as if USER were set to the special value . If the > invoking user is not a member of one of these groups, the name > defined in USER will be used as normal. For example, setting > UGROUPS to wheel and USER to root allows members of wheel (tra- > ditionally used for administrative privileges) to authenticate > with their own credentials and requires other users to provide > the root password. > > So, for example, if /etc/security/console.apps/system-config-users looks > like this: > > USER=root > PROGRAM=/usr/share/system-config-users/system-config-users > SESSION=true > UGROUPS=wheel > > members of the wheel group will be able to authenticate with their own > passwords, and others will need the root password. > > We've made this the default for all of the system-config-* apps here at > BU > for several years with good results; it might be nice to also make it the > default in future versions of Fedora. (Although this is a pretty big > default > security policy change, it *is* basically the traditional meaning of the > "wheel" group.) > > > > > Caveat: I just noticed that the little "keys" gnome-panel icon doesn't > work > with this, and I'm trying to figure out what should be done about that. > -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/ From kyrre at solution-forge.net Sat Mar 5 14:54:28 2005 From: kyrre at solution-forge.net (Kyrre Ness Sjobak) Date: Sat, 05 Mar 2005 15:54:28 +0100 Subject: An ordinary user's perspective of Linux (was Re: Make consolehelper more liske sudo?) In-Reply-To: References: <20050304170018.C6E9773A2C@hormel.redhat.com> Message-ID: <1110034467.6541.16.camel@localhost.localdomain> l?r, 05.03.2005 kl. 14.52 skrev Parameshwara Bhat: > Dear List, > > I am a curious member of this list and an ordinary user of Linux ; so > excuse me for breaking into a learned debate.I want to give a perspective > of my end,following the threads between Havoc, Matthew and David. > > I use Fedora at home and office. Nowhere I can have the support of learned > linux experts at my beck and call; Also, I have installed the OS and > created root and other users. All passwords are available with me.Working > as a user,by the number of times I have to invoke 'root',I wonder why I > should not be working as root itself ?. > Because of security - a flaw in a "user" app could then affect the whole machine. What situations do you have to invoke root? > By the discussions I have seen here and elsewhere, it appears most linux > experts and creators are basically contemptous of such a user as me. I am > sane, responsible and intelligent, but just not a linux expert. I have my > job and I want computer to be an unhindering aid and a provider of > entertainment.Why should I be required to know the intricacies of the OS ? > When the CD is locked and unmountable, unejectable; profound sermons on > the security aspects of linux hardly makes sense. > That is a bug - an annoying one as well. gnome-vfs mount should *really* give some hint about what locks the removable media > While completely respecting the concerns of security and stability; > borderlines of zones and the security matrix can always be redefined and > redesigned if you know exactly what you want to give the end user.OS and > programs like shirts and pants need to be tailored to users. > > I am a devoted user of Linux and Fedora. But what a stupid it makes of me! > Without the root password I just cannot imagine keeping this box running > and making any use of it.In a regulated office environment(unlike > mine)where I wouldn't be having the root password, I do not think I will > be able to use it with any amount of ease.In contrast, much maligned > Windows pampers me!So nice and considerate of my needs with all it's flaws > and weaknesses.Without the root password and a great deal of 'googli'ng > and 'maillist'ng, I couldnot have sustained Linux on this box. > Again,compare this with Windows. > As an administrator of a small network of Linux(fedora) machines, the users very seldom ask me to help them with something involving root. They use the machines for internet, text processing etc., image editing, some do programming, printing stuff, video/sound etc. I have all the workstations identically configured (stock fc3 with some extra apps) - and nobody ever complains. But i do sometimes get the nice "thanks for running that Linux net! those machines are so much less trouble to use, and everything is so much more logically laid out than in windows!" comments. Administration is done through the net using a small self-written utility called "admin-script". Basically i make sure the users have what they need, and the users are happy. When the users are happy, i am happy. So the situation of having a knowing administrator that just takes care of "stuff" and the situation where every users have to be their own admin, are vastly different. In the first situation Linux/fedora is doing really great - using a Linux machine is a no-brainer, administrating one takes some knowledge and isn't (yet) as intuitive as Windows administration (but having experienced both OS's, and having the needed knowledge, ill take Linux over Windows any day). But i do agree that more intuitive (grapical poin't click + wizards to do "inital setup") configuration tools are needed for Linux to do get really wide market acceptance. SuSE has Yast - which do provide such functions in an intuitive way. Redhat/Fedora has system-config-*, which also gives a mostly intuitive way to configure "stuff" - but it doesn't cover a wide enough area. Some system-config tools are great (such as the network one), some are no so great (such as the apache one - covering only a few of apaches functions), and some are still non-existant (such as the yum one). > When will Linux and Fedora learn to respect me and users like me or will > it at all? Answer to that will be the key to whether it can really compete > with MS > I think it does respect you kind of users as well - there are a hugely growing number of them. Keep in mind that Linux has traditionally been used by people with great knowledge of computers, and not by "consumers". Much is therefore yet tuned for that user group, and it is a hard task to cater regular consumers as well as the first group. But things are improving at a fast pace! > Parameshwara Bhat > > On Fri, 4 Mar 2005 12:00:18 -0500 (EST), > wrote: > > > Send Fedora-desktop-list mailing list submissions to > > fedora-desktop-list at redhat.com > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://www.redhat.com/mailman/listinfo/fedora-desktop-list > > or, via email, send a message with subject or body 'help' to > > fedora-desktop-list-request at redhat.com > > > > You can reach the person managing the list at > > fedora-desktop-list-owner at redhat.com > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of Fedora-desktop-list digest..." > > > > > > Today's Topics: > > > > 1. Re: Make consolehelper more liske sudo? (Havoc Pennington) > > 2. Re: Make consolehelper more liske sudo? (Matthew Miller) > > 3. Re: Make consolehelper more liske sudo? (Matthew Miller) > > 4. Re: Make consolehelper more liske sudo? (David Zeuthen) > > 5. Re: Make consolehelper more liske sudo? (Matthew Miller) > > 6. Re: Make consolehelper more liske sudo? (Havoc Pennington) > > 7. Re: Make consolehelper more liske sudo? (Havoc Pennington) > > 8. Re: Make consolehelper more liske sudo? (Eric Warnke) > > 9. Re: Make consolehelper more liske sudo? (Matthew Miller) > > 10. Re: Make consolehelper more liske sudo? (David Zeuthen) > > 11. Re: Make consolehelper more liske sudo? (Matthew Miller) > > 12. Re: Make consolehelper more liske sudo? (Havoc Pennington) > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Thu, 03 Mar 2005 14:34:51 -0500 > > From: Havoc Pennington > > Subject: Re: Make consolehelper more liske sudo? > > To: Discussions about development for the Fedora desktop > > > > Message-ID: <1109878491.21167.15.camel at localhost.localdomain> > > Content-Type: text/plain > > > > On Wed, 2005-03-02 at 10:08 -0500, Eric Warnke wrote: > >> Hello all, > >> > >> I have unsucessfully been attempting to find out through both > >> documentation, testing, and internet sources if I can get consolehelper > >> to act more like sudo rather than su. Right now my problem is that > >> there is NO WAY to roll this out to more users as a desktop alternative > >> without giving them some power user ability ( printers, date and time, > >> removable storage managment, ... ). Right now in order to give them > >> access to these applications AFAICT I must either give the users the > >> root password ( not gonna happen ) or create a pam.d file so that there > >> is no password prompt ( pam_wheel with trust option ). Neither of these > >> is a truly acceptable option at this point. > >> > >> Any change should try to keep the system as close to baseline as > >> possible, I would prefer not to rip out the consolehelper system, but I > >> will if I have to. The featureset I want is identical to sudo, but I > >> will make accomidations as long as I can allow users to run a specific > >> command after prompting for the users password. > > > > You can probably just set things up with sudo... I'm not sure how > > involved that is. > > > > I do think consolehelper knows how to require user password instead of > > root password though. You may have more luck finding help with this on > > fedora-list or IRC than on this list. I'm not sure of the syntax myself > > but I'm pretty sure you want to edit the /etc/pam.d files. > > > > All this "end user desktop" stuff that requires root I consider a bug > > btw, if you want to file a bugzilla for the individual items that would > > be helpful. If you get NOTABUG/WONTFIX from someone at Red Hat let me > > know and I'll tell them they are wrong. > > > > Havoc > > > > > > > > > > ------------------------------ > > > > Message: 2 > > Date: Thu, 3 Mar 2005 14:56:20 -0500 > > From: Matthew Miller > > Subject: Re: Make consolehelper more liske sudo? > > To: Discussions about development for the Fedora desktop > > > > Message-ID: <20050303195620.GA15219 at jadzia.bu.edu> > > Content-Type: text/plain; charset=us-ascii > > > > On Wed, Mar 02, 2005 at 10:08:07AM -0500, Eric Warnke wrote: > >> I have unsucessfully been attempting to find out through both > >> documentation, testing, and internet sources if I can get consolehelper > >> to act more like sudo rather than su. Right now my problem is that > >> there is NO WAY to roll this out to more users as a desktop alternative > >> without giving them some power user ability ( printers, date and time, > > > > This may help. As of Fedora Core 3, the "UGROUPS" patch is in usermode. > > From > > the userhelper man page: > > > > UGROUPS > > A comma-separated list of groups whose members will be authen- > > ticated as if USER were set to the special value . If the > > invoking user is not a member of one of these groups, the name > > defined in USER will be used as normal. For example, setting > > UGROUPS to wheel and USER to root allows members of wheel (tra- > > ditionally used for administrative privileges) to authenticate > > with their own credentials and requires other users to provide > > the root password. > > > > So, for example, if /etc/security/console.apps/system-config-users looks > > like this: > > > > USER=root > > PROGRAM=/usr/share/system-config-users/system-config-users > > SESSION=true > > UGROUPS=wheel > > > > members of the wheel group will be able to authenticate with their own > > passwords, and others will need the root password. > > > > We've made this the default for all of the system-config-* apps here at > > BU > > for several years with good results; it might be nice to also make it the > > default in future versions of Fedora. (Although this is a pretty big > > default > > security policy change, it *is* basically the traditional meaning of the > > "wheel" group.) > > > > > > > > > > Caveat: I just noticed that the little "keys" gnome-panel icon doesn't > > work > > with this, and I'm trying to figure out what should be done about that. > > > > > > -- > Using Opera's revolutionary e-mail client: http://www.opera.com/m2/ From webmanagement at gmail.com Sat Mar 5 15:03:40 2005 From: webmanagement at gmail.com (Andy Hudson) Date: Sat, 05 Mar 2005 15:03:40 +0000 Subject: An ordinary user's perspective of Linux (was Re: Make consolehelper more liske sudo?) In-Reply-To: References: <20050304170018.C6E9773A2C@hormel.redhat.com> Message-ID: <4229CA4C.4000800@nospam.gmail.com> Parameshwara Bhat wrote: > Dear List, > > I am a curious member of this list and an ordinary user of Linux ; so > excuse me for breaking into a learned debate.I want to give a > perspective of my end,following the threads between Havoc, Matthew > and David. > > I use Fedora at home and office. Nowhere I can have the support of > learned linux experts at my beck and call; Also, I have installed the > OS and created root and other users. All passwords are available with > me.Working as a user,by the number of times I have to invoke 'root',I > wonder why I should not be working as root itself ?. > > By the discussions I have seen here and elsewhere, it appears most > linux experts and creators are basically contemptous of such a user > as me. I am sane, responsible and intelligent, but just not a linux > expert. I have my job and I want computer to be an unhindering aid > and a provider of entertainment.Why should I be required to know the > intricacies of the OS ? When the CD is locked and unmountable, > unejectable; profound sermons on the security aspects of linux hardly > makes sense. > > While completely respecting the concerns of security and stability; > borderlines of zones and the security matrix can always be redefined > and redesigned if you know exactly what you want to give the end > user.OS and programs like shirts and pants need to be tailored to users. > > I am a devoted user of Linux and Fedora. But what a stupid it makes of > me! Without the root password I just cannot imagine keeping this box > running and making any use of it.In a regulated office > environment(unlike mine)where I wouldn't be having the root password, > I do not think I will be able to use it with any amount of ease.In > contrast, much maligned Windows pampers me!So nice and considerate of > my needs with all it's flaws and weaknesses.Without the root password > and a great deal of 'googli'ng and 'maillist'ng, I couldnot have > sustained Linux on this box. Again,compare this with Windows. > > When will Linux and Fedora learn to respect me and users like me or > will it at all? Answer to that will be the key to whether it can > really compete with MS > > Parameshwara Bhat > Parameshwara, The reason why root access is necessary is that it prevents any accidental damage to your system. Of course it is ok for you to have root access to your own Fedora Core installation - after all, you are administering it. Your point about the regulated office environment pretty much answers your question. For instance, at my place of work we all use Windows 2000 or Mac OS X. I'm one of the people on Windows 2000. Our IT Services department have an acceptable use policy that is supposed to restrict me from installing third party software or anything malicious. However, with Windows 2000 they have all the users set up with administration rights over their own machine, so in theory I could download iTunes and any other piece of software, install it and let it play havoc with my system. Work computers are for work - it is as simple as that. I have seen many laptops and desktops having to be fixed or having to have spyware removed because some user has downloaded and installed software that they shouldn't have done. However, I have FC3 on my home computer which I trash most weeks just because I can. New software is downloaded and used all the time... sometimes it breaks, sometimes it works, sometimes it makes no difference at all. The point is that I am responsible for my home machine. I am also responsible for my work machine - I have to use it day by day in order to carry out my duties. If it breaks I am not productive... Fedora does respect users - the System Administrators can grant differing levels of access to the system to particular users. I don't think it is as much about system security as it is about system integrity. But that is just my two pence worth, Andy From jason at cassiopaea.com Sat Mar 5 23:33:52 2005 From: jason at cassiopaea.com (Jason Knight) Date: Sun, 06 Mar 2005 00:33:52 +0100 Subject: An ordinary user's perspective of Linux (was Re: Make consolehelper more liske sudo?) In-Reply-To: <4229CA4C.4000800@nospam.gmail.com> References: <20050304170018.C6E9773A2C@hormel.redhat.com> <4229CA4C.4000800@nospam.gmail.com> Message-ID: <422A41E0.5060801@cassiopaea.com> Andy Hudson wrote: > Parameshwara Bhat wrote: > >> Dear List, >> >> I am a curious member of this list and an ordinary user of Linux ; >> so excuse me for breaking into a learned debate.I want to give a >> perspective of my end,following the threads between Havoc, Matthew >> and David. >> >> [...Snippedified by Jason Knight...] >> >> When will Linux and Fedora learn to respect me and users like me or >> will it at all? Answer to that will be the key to whether it can >> really compete with MS >> >> Parameshwara Bhat > > Parameshwara, Linux Distributions are multi-user systems, Microsoft Windows is a single user system, that has attempted to add multi-user features. root is necessary because it is the administrator's account, a multiuser system, to remain secure, must have it implemented in this way. Most if not all, this includes myself, will enccourage you to only use the administrator account to perform administrator functions, and to use a basic user account for day to day activities. I do this, and simply have no problems with it. The separation of Root and User adds an excellent layer of security, if you as a user cannot install any software, that means good software, and bad software. Then there is less risk to the system, that way, everyone will not pay for your mistake. There is little that will stop you from running in root all of the time. But this is grossly insecure. Although most avid linux users that have used windows for more than 5-10 minutes would describe Windows as Grossly Insecure. If you decide to run as root all the time, you will have to make sure that you have a good firewall, a good anti-virus, you will need to keep up to date on all the security issues, you will have to maintain and keep a very close eye on all logs etc... Why not just use windows? No one is stopping you from doing this? I think linux should always and forever put security before useability. Linux is not the lazy man's OS. If you wish to be lazy, by all means use windows, or run as root all the time. You may expect that the world, and all the people in it should spend their time making your life easier, but I do not think that is a good way to look at it, and I do not think that you will get very far with such an idea. This is the application of the windows mentality, i.e. Yeah Oz is really a great place to live, but pay no attention to that man behind the curtain! You can please half the people all the time or all of the people half of the time. I think Linux shouldn't try to please anyone, I think it should simply work well/good/better than last time, allow distributions to decide the level of useability they plan to provide. I don't believe that Distrobutions should sacrifice security to obscure Linux from the user in an effort to make their computer experience uber-pointy-clicky. Thats not interaction, thats not abstraction, and it will never lead to satisfaction. Just my .02 on the subject Jason Knight -------------- next part -------------- A non-text attachment was scrubbed... Name: jason.vcf Type: text/x-vcard Size: 131 bytes Desc: not available URL: From bjiang_ee at yahoo.ca Mon Mar 7 14:38:11 2005 From: bjiang_ee at yahoo.ca (Benjamin Jiang) Date: Mon, 07 Mar 2005 09:38:11 -0500 Subject: X crashes when using a new monitor Message-ID: <422C6753.2090300@yahoo.ca> Hi, all, I installed a fresh copy of FC3 into my Dad's machine and everything worked fine. However, when I brought the machine to my Dad's place and plugged in his monitor (Acer 7154e), X crashes no matter what. I tried config xorg.conf with the correct HorizSync and VertRefresh, but it didn't even make any difference. Then I tried the extreme solution: I replaced the HDD with a new HDD and installed a fresh copy FC3 with my Dad's monitor plugged in while installation. Everything worked fine again and I got graphics interface. I then grabbed the working xorg.conf and swapped the HDDs. After I booted into the previous installed FC3, I replaced the xorg.conf with the working xorg.conf. It still didn't make any difference! I am a little confused. Is there some other file I need to change except for /etc/X11/xorg.conf? Is there any special module I need to load? I know I could just re-install FC3 into my Dad's HDD. I am just curious to see what's wrong here. Here's the setup: AMD K6 350Mhz; 196MB RAM Trident Blade3D 8MB video card Thanks in advance! Ben. Here comes the log file: /var/log/Xorg.0.log: --------------------------------------------------------------------------------- X Window System Version 6.8.1 Release Date: 17 September 2004 X Protocol Version 11, Revision 0, Release 6.8.1 Build Operating System: Linux 2.4.21-14.ELsmp i686 [ELF] Current Operating System: Linux fallsview 2.6.9-1.667 #1 Tue Nov 2 14:41:31 EST 2004 i586 Build Date: 20 October 2004 Build Host: tweety.build.redhat.com Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.6.9-1.667 (bhcompile at tweety.build.redhat.com) (gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)) #1 Tue Nov 2 14:41:31 EST 2004 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: Sat Jan 1 02:56:07 2000 (++) Using config file: "xorg.conf.new" (==) ServerLayout "Default Layout" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Videocard0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (**) FontPath set to "unix/:7100" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (==) ModulePath set to "/usr/X11R6/lib/modules" (WW) Open APM failed (/dev/apm_bios) (No such file or directory) (II) Module ABI versions: X.Org ANSI C Emulation: 0.2 X.Org Video Driver: 0.7 X.Org XInput driver : 0.4 X.Org Server Extension : 0.2 X.Org Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.7 (--) using VT number 7 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x00000000, mode1Res1 = 0x80000000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,0598 card 0000,0000 rev 04 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,8598 card 0000,0000 rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1106,0686 card 1106,0000 rev 22 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1106,0571 card 0000,0000 rev 10 class 01,01,8a hdr 00 (II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 10 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 1106,3038 card 0925,1234 rev 10 class 0c,03,00 hdr 00 (II) PCI: 00:07:4: chip 1106,3057 card 0000,0000 rev 30 class 06,00,00 hdr 00 (II) PCI: 00:08:0: chip 122d,50dc card 122d,8000 rev 10 class 04,01,00 hdr 00 (II) PCI: 00:0b:0: chip 10d9,0531 card 15e8,8110 rev 25 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 1023,9880 card 1023,9880 rev 3a class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set) (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xd4000000 - 0xd7ffffff (0x4000000) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (II) Host-to-PCI bridge: (II) Bus -1: bridge is at (0:7:4), (-1,-1,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus -1 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus -1 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus -1 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (--) PCI:*(1:0:0) Trident Microsystems Blade 3D PCI/AGP rev 58, Mem @ 0xd5800000/23, 0xd6000000/17, 0xd5000000/23 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) PCI Memory resource overlap reduced 0xd0000000 from 0xd3ffffff to 0xcfffffff (II) Active PCI resource ranges: [0] -1 0 0xd9000000 - 0xd90000ff (0x100) MX[B] [1] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O [2] -1 0 0xd5000000 - 0xd57fffff (0x800000) MX[B](B) [3] -1 0 0xd6000000 - 0xd601ffff (0x20000) MX[B](B) [4] -1 0 0xd5800000 - 0xd5ffffff (0x800000) MX[B](B) [5] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B] [6] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] [7] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B] [8] -1 0 0x0000d400 - 0x0000d403 (0x4) IX[B] [9] -1 0 0x0000d000 - 0x0000d007 (0x8) IX[B] [10] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B] [11] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] [12] -1 0 0x0000c400 - 0x0000c41f (0x20) IX[B] [13] -1 0 0x0000c000 - 0x0000c00f (0x10) IX[B] (II) Active PCI resource ranges after removing overlaps: [0] -1 0 0xd9000000 - 0xd90000ff (0x100) MX[B] [1] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O [2] -1 0 0xd5000000 - 0xd57fffff (0x800000) MX[B](B) [3] -1 0 0xd6000000 - 0xd601ffff (0x20000) MX[B](B) [4] -1 0 0xd5800000 - 0xd5ffffff (0x800000) MX[B](B) [5] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B] [6] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] [7] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B] [8] -1 0 0x0000d400 - 0x0000d403 (0x4) IX[B] [9] -1 0 0x0000d000 - 0x0000d007 (0x8) IX[B] [10] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B] [11] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] [12] -1 0 0x0000c400 - 0x0000c41f (0x20) IX[B] [13] -1 0 0x0000c000 - 0x0000c00f (0x10) IX[B] (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) All system resource ranges: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xd9000000 - 0xd90000ff (0x100) MX[B] [6] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O [7] -1 0 0xd5000000 - 0xd57fffff (0x800000) MX[B](B) [8] -1 0 0xd6000000 - 0xd601ffff (0x20000) MX[B](B) [9] -1 0 0xd5800000 - 0xd5ffffff (0x800000) MX[B](B) [10] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [11] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [12] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B] [13] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] [14] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B] [15] -1 0 0x0000d400 - 0x0000d403 (0x4) IX[B] [16] -1 0 0x0000d000 - 0x0000d007 (0x8) IX[B] [17] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B] [18] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] [19] -1 0 0x0000c400 - 0x0000c41f (0x20) IX[B] [20] -1 0 0x0000c000 - 0x0000c00f (0x10) IX[B] (II) LoadModule: "dbe" (II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a (II) Module dbe: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.2 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "extmod" (II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a (II) Module extmod: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.2 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "fbdevhw" (II) Loading /usr/X11R6/lib/modules/linux/libfbdevhw.a (II) Module fbdevhw: vendor="X.Org Foundation" compiled for 6.8.1, module version = 0.0.2 ABI class: X.Org Video Driver, version 0.7 (II) LoadModule: "glx" (II) Loading /usr/X11R6/lib/modules/extensions/libglx.a (II) Module glx: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading sub module "GLcore" (II) LoadModule: "GLcore" (II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a (II) Module GLcore: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading extension GLX (II) LoadModule: "record" (II) Loading /usr/X11R6/lib/modules/extensions/librecord.a (II) Module record: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.13.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.2 (II) Loading extension RECORD (II) LoadModule: "freetype" (II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.so (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project" compiled for 6.8.1, module version = 2.1.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font FreeType (II) LoadModule: "type1" (II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a (II) Module type1: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.2 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Type1 (II) Loading font CID (II) LoadModule: "dri" (II) Loading /usr/X11R6/lib/modules/extensions/libdri.a (II) Module dri: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading sub module "drm" (II) LoadModule: "drm" (II) Loading /usr/X11R6/lib/modules/linux/libdrm.a (II) Module drm: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading extension XFree86-DRI (II) LoadModule: "trident" (II) Loading /usr/X11R6/lib/modules/drivers/trident_drv.o (II) Module trident: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 0.7 (II) LoadModule: "mouse" (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o (II) Module mouse: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.4 (II) LoadModule: "kbd" (II) Loading /usr/X11R6/lib/modules/input/kbd_drv.o (II) Module kbd: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.4 (II) TRIDENT: driver for Trident chipsets: tvga9000, tvga9000i, tvga8900c, tvga8900d, tvga9200cxr, tgui9400cxi, cyber9320, cyber9388, cyber9397, cyber9397dvd, cyber9520, cyber9525dvd, cyberblade/e4, tgui9420dgi, tgui9440agi, tgui9660, tgui9680, providia9682, providia9685, cyber9382, cyber9385, 3dimage975, 3dimage985, blade3d, cyberbladei7, cyberbladei7d, cyberbladei1, cyberbladei1d, cyberbladeAi1, cyberbladeAi1d, bladeXP, cyberbladeXPAi1, cyberbladeXP4 (II) Primary Device is: PCI 01:00:0 (--) Assigning device section with no busID to primary device (--) Chipset blade3d found (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xd9000000 - 0xd90000ff (0x100) MX[B] [6] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O [7] -1 0 0xd5000000 - 0xd57fffff (0x800000) MX[B](B) [8] -1 0 0xd6000000 - 0xd601ffff (0x20000) MX[B](B) [9] -1 0 0xd5800000 - 0xd5ffffff (0x800000) MX[B](B) [10] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [11] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [12] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B] [13] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] [14] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B] [15] -1 0 0x0000d400 - 0x0000d403 (0x4) IX[B] [16] -1 0 0x0000d000 - 0x0000d007 (0x8) IX[B] [17] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B] [18] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] [19] -1 0 0x0000c400 - 0x0000c41f (0x20) IX[B] [20] -1 0 0x0000c000 - 0x0000c00f (0x10) IX[B] (II) resource ranges after probing: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xd9000000 - 0xd90000ff (0x100) MX[B] [6] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O [7] -1 0 0xd5000000 - 0xd57fffff (0x800000) MX[B](B) [8] -1 0 0xd6000000 - 0xd601ffff (0x20000) MX[B](B) [9] -1 0 0xd5800000 - 0xd5ffffff (0x800000) MX[B](B) [10] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [11] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [12] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [13] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [14] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [15] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B] [16] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] [17] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B] [18] -1 0 0x0000d400 - 0x0000d403 (0x4) IX[B] [19] -1 0 0x0000d000 - 0x0000d007 (0x8) IX[B] [20] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B] [21] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] [22] -1 0 0x0000c400 - 0x0000c41f (0x20) IX[B] [23] -1 0 0x0000c000 - 0x0000c00f (0x10) IX[B] [24] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [25] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (**) TRIDENT(0): Depth 16, (--) framebuffer bpp 16 (II) Loading sub module "vgahw" (II) LoadModule: "vgahw" (II) Loading /usr/X11R6/lib/modules/libvgahw.a (II) Module vgahw: vendor="X.Org Foundation" compiled for 6.8.1, module version = 0.1.0 ABI class: X.Org Video Driver, version 0.7 (II) TRIDENT(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (II) Loading sub module "ramdac" (II) LoadModule: "ramdac" (II) Loading /usr/X11R6/lib/modules/libramdac.a (II) Module ramdac: vendor="X.Org Foundation" compiled for 6.8.1, module version = 0.1.0 ABI class: X.Org Video Driver, version 0.7 (==) TRIDENT(0): RGB weight 565 (==) TRIDENT(0): Default visual is TrueColor (==) TRIDENT(0): Using gamma correction (1.0, 1.0, 1.0) (==) TRIDENT(0): Linear framebuffer at 0xD5800000 (--) TRIDENT(0): IO registers at 0xD6000000 (II) Loading sub module "vbe" (II) LoadModule: "vbe" (II) Loading /usr/X11R6/lib/modules/libvbe.a (II) Module vbe: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.1.0 ABI class: X.Org Video Driver, version 0.7 (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/X11R6/lib/modules/linux/libint10.a (II) Module int10: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.7 (II) TRIDENT(0): initializing int10 (II) TRIDENT(0): Primary V_BIOS segment is: 0xc000 (II) TRIDENT(0): VESA BIOS detected (II) TRIDENT(0): VESA VBE Version 2.0 (II) TRIDENT(0): VESA VBE Total Mem: 8192 kB (II) TRIDENT(0): VESA VBE OEM: Trident Blade 3D (II) TRIDENT(0): VESA VBE OEM Software Rev: 2.0 (II) TRIDENT(0): VESA VBE OEM Vendor: TRIDENT MICROSYSTEMS INC. (II) TRIDENT(0): VESA VBE OEM Product: Blade 3D (II) TRIDENT(0): VESA VBE OEM Product Rev: J 6.4 (38) (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Loading /usr/X11R6/lib/modules/libddc.a (II) Module ddc: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.7 (II) TRIDENT(0): VESA VBE DDC supported (II) TRIDENT(0): VESA VBE DDC Level 2 (II) TRIDENT(0): VESA VBE DDC transfer in appr. 1 sec. (II) TRIDENT(0): VESA VBE DDC read successfully (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Reloading /usr/X11R6/lib/modules/libddc.a (II) TRIDENT(0): Manufacturer: API Model: 4536 Serial#: 924 (II) TRIDENT(0): Year: 1997 Week: 26 (II) TRIDENT(0): EDID Version: 1.2 (II) TRIDENT(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V (II) TRIDENT(0): Sync: Separate (II) TRIDENT(0): Max H-Image Size [cm]: horiz.: 27 vert.: 20 (II) TRIDENT(0): Gamma: 2.66 (II) TRIDENT(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display (II) TRIDENT(0): redX: 0.625 redY: 0.340 greenX: 0.284 greenY: 0.600 (II) TRIDENT(0): blueX: 0.149 blueY: 0.064 whiteX: 0.280 whiteY: 0.311 (II) TRIDENT(0): Supported VESA Video Modes: (II) TRIDENT(0): 720x400 at 70Hz (II) TRIDENT(0): 640x480 at 60Hz (II) TRIDENT(0): 640x480 at 72Hz (II) TRIDENT(0): 640x480 at 75Hz (II) TRIDENT(0): 800x600 at 60Hz (II) TRIDENT(0): 800x600 at 72Hz (II) TRIDENT(0): 800x600 at 75Hz (II) TRIDENT(0): 1024x768 at 60Hz (II) TRIDENT(0): Manufacturer's mask: 21 (--) TRIDENT(0): Revision is 58 (--) TRIDENT(0): Found Blade3D chip (--) TRIDENT(0): RAM type is SDRAM (--) TRIDENT(0): Using HW cursor (--) TRIDENT(0): VideoRAM: 8192 kByte (--) TRIDENT(0): Memory Clock is 109.77 MHz (==) TRIDENT(0): Min pixel clock is 12 MHz (--) TRIDENT(0): Max pixel clock is 230 MHz (II) TRIDENT(0): Monitor0: Using hsync range of 31.00-60.00 kHz (II) TRIDENT(0): Monitor0: Using vrefresh range of 55.00-90.00 Hz (II) TRIDENT(0): Clock range: 12.00 to 230.00 MHz (II) TRIDENT(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "360x200" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1024x768" (hsync out of range) (II) TRIDENT(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1152x864" (hsync out of range) (II) TRIDENT(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1280x960" (hsync out of range) (II) TRIDENT(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1280x1024" (hsync out of range) (II) TRIDENT(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1280x1024" (hsync out of range) (II) TRIDENT(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1280x1024" (hsync out of range) (II) TRIDENT(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1600x1200" (hsync out of range) (II) TRIDENT(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1600x1200" (hsync out of range) (II) TRIDENT(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1600x1200" (hsync out of range) (II) TRIDENT(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1600x1200" (hsync out of range) (II) TRIDENT(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1600x1200" (hsync out of range) (II) TRIDENT(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1792x1344" (hsync out of range) (II) TRIDENT(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1792x1344" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1856x1392" (hsync out of range) (II) TRIDENT(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1856x1392" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "416x312" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "576x384" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1152x864" (hsync out of range) (II) TRIDENT(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1400x1050" (hsync out of range) (II) TRIDENT(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1400x1050" (hsync out of range) (II) TRIDENT(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1400x1050" (hsync out of range) (II) TRIDENT(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1400x1050" (hsync out of range) (II) TRIDENT(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1600x1024" (hsync out of range) (II) TRIDENT(0): Not using default mode "800x512" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1920x1200" (hsync out of range) (II) TRIDENT(0): Not using default mode "960x600" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1280x960" (width too large for virtual size) (II) TRIDENT(0): Not using default mode "1152x768" (width too large for virtual size) (II) TRIDENT(0): Not using default mode "1024x768" (width too large for virtual size) (II) TRIDENT(0): Not using default mode "1024x768" (width too large for virtual size) (II) TRIDENT(0): Not using default mode "1024x768" (width too large for virtual size) (II) TRIDENT(0): Not using default mode "1024x768" (width too large for virtual size) (II) TRIDENT(0): Not using default mode "832x624" (width too large for virtual size) (--) TRIDENT(0): Virtual size is 800x600 (pitch 800) (**) TRIDENT(0): *Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz (II) TRIDENT(0): Modeline "800x600" 56.30 800 832 896 1048 600 601 604 631 +hsync +vsync (**) TRIDENT(0): *Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz (II) TRIDENT(0): Modeline "640x480" 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (**) TRIDENT(0): Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz (II) TRIDENT(0): Modeline "800x600" 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (**) TRIDENT(0): Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz (II) TRIDENT(0): Modeline "800x600" 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (**) TRIDENT(0): Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz (II) TRIDENT(0): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (**) TRIDENT(0): Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz (II) TRIDENT(0): Modeline "800x600" 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (**) TRIDENT(0): Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz (II) TRIDENT(0): Modeline "640x480" 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (**) TRIDENT(0): Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz (II) TRIDENT(0): Modeline "640x480" 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (**) TRIDENT(0): Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz (II) TRIDENT(0): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (**) TRIDENT(0): Default mode "720x400": 35.5 MHz, 37.9 kHz, 85.0 Hz (II) TRIDENT(0): Modeline "720x400" 35.50 720 756 828 936 400 401 404 446 -hsync +vsync (**) TRIDENT(0): Default mode "640x400": 31.5 MHz, 37.9 kHz, 85.1 Hz (II) TRIDENT(0): Modeline "640x400" 31.50 640 672 736 832 400 401 404 445 -hsync +vsync (**) TRIDENT(0): Default mode "640x350": 31.5 MHz, 37.9 kHz, 85.1 Hz (II) TRIDENT(0): Modeline "640x350" 31.50 640 672 736 832 350 382 385 445 +hsync -vsync (**) TRIDENT(0): Display dimensions: (270, 200) mm (**) TRIDENT(0): DPI set to (75, 76) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/X11R6/lib/modules/libfb.a (II) Module fb: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.2 (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Loading /usr/X11R6/lib/modules/libi2c.a (II) Module i2c: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.2.0 ABI class: X.Org Video Driver, version 0.7 (II) Loading sub module "xaa" (II) LoadModule: "xaa" (II) Loading /usr/X11R6/lib/modules/libxaa.a (II) Module xaa: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.2.0 ABI class: X.Org Video Driver, version 0.7 *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Fatal server error: Caught signal 11. Server aborting Please consult the The X.Org Foundation support at http://wiki.X.Org for help. Please also check the log file at "/var/log/Xorg.0.log" for additional information. From jonathansavage at gmail.com Mon Mar 7 14:46:23 2005 From: jonathansavage at gmail.com (Jon Savage) Date: Mon, 7 Mar 2005 06:46:23 -0800 Subject: X crashes when using a new monitor In-Reply-To: <422C6753.2090300@yahoo.ca> References: <422C6753.2090300@yahoo.ca> Message-ID: <2ad7cea105030706461e1e280@mail.gmail.com> On Mon, 07 Mar 2005 09:38:11 -0500, Benjamin Jiang wrote: > Hi, all, > > I installed a fresh copy of FC3 into my Dad's machine and everything > worked fine. However, when I brought the machine to my Dad's place and > plugged in his monitor (Acer 7154e), X crashes no matter what. I tried > config xorg.conf with the correct HorizSync and VertRefresh, but it > didn't even make any difference. Try booting into runlevel 3 and then login as root and do system-config-display --reconfig. Bests JS From bjiang_ee at yahoo.ca Mon Mar 7 14:53:59 2005 From: bjiang_ee at yahoo.ca (Benjamin Jiang) Date: Mon, 07 Mar 2005 09:53:59 -0500 Subject: X crashes when using a new monitor In-Reply-To: <2ad7cea105030706461e1e280@mail.gmail.com> References: <422C6753.2090300@yahoo.ca> <2ad7cea105030706461e1e280@mail.gmail.com> Message-ID: <422C6B07.4010501@yahoo.ca> Jon Savage wrote: >On Mon, 07 Mar 2005 09:38:11 -0500, Benjamin Jiang wrote: > > >>Hi, all, >> >>I installed a fresh copy of FC3 into my Dad's machine and everything >>worked fine. However, when I brought the machine to my Dad's place and >>plugged in his monitor (Acer 7154e), X crashes no matter what. I tried >>config xorg.conf with the correct HorizSync and VertRefresh, but it >>didn't even make any difference. >> >> > >Try booting into runlevel 3 and then >login as root and do system-config-display --reconfig. > >Bests > >JS > > > Thanks, Jon. I did that yesterday already and no difference made. Ben. From fedora-lists at dark-hill.co.uk Mon Mar 7 15:30:54 2005 From: fedora-lists at dark-hill.co.uk (Douglas Furlong) Date: Mon, 7 Mar 2005 15:30:54 +0000 Subject: X crashes when using a new monitor In-Reply-To: <422C6B07.4010501@yahoo.ca> References: <422C6753.2090300@yahoo.ca> <2ad7cea105030706461e1e280@mail.gmail.com> <422C6B07.4010501@yahoo.ca> Message-ID: <20050307153054.c2f3mb7npl8oog4o@corrig.dark-hill.co.uk> ----- Message from bjiang_ee at yahoo.ca --------- Date: Mon, 07 Mar 2005 09:53:59 -0500 From: Benjamin Jiang Reply-To: Discussions about development for the Fedora desktop Subject: Re: X crashes when using a new monitor To: Jon Savage , Discussions about development for the Fedora desktop > Jon Savage wrote: > >> On Mon, 07 Mar 2005 09:38:11 -0500, Benjamin Jiang >> wrote: >> >>> Hi, all, >>> >>> I installed a fresh copy of FC3 into my Dad's machine and everything >>> worked fine. However, when I brought the machine to my Dad's place and >>> plugged in his monitor (Acer 7154e), X crashes no matter what. I tried >>> config xorg.conf with the correct HorizSync and VertRefresh, but it >>> didn't even make any difference. >>> >> >> Try booting into runlevel 3 and then >> login as root and do system-config-display --reconfig. >> >> Bests >> >> JS >> >> > Thanks, Jon. > > I did that yesterday already and no difference made. When booting in to run level 3, log in as either a non privaliged user, or as root and running "startx", if X still crashes you should get some output in the terminal. Also look through the file /var/log/Xorg.0.log, as that will have some more information that may help us to help you. Doug -- Douglas Furlong ICQ: 7574077 "There are 10 kinds of people, those that understand binary, and those that do not" From bjiang_ee at yahoo.ca Mon Mar 7 15:40:02 2005 From: bjiang_ee at yahoo.ca (Benjamin Jiang) Date: Mon, 07 Mar 2005 10:40:02 -0500 Subject: X crashes when using a new monitor In-Reply-To: <20050307153054.c2f3mb7npl8oog4o@corrig.dark-hill.co.uk> References: <422C6753.2090300@yahoo.ca> <2ad7cea105030706461e1e280@mail.gmail.com> <422C6B07.4010501@yahoo.ca> <20050307153054.c2f3mb7npl8oog4o@corrig.dark-hill.co.uk> Message-ID: <422C75D2.7060604@yahoo.ca> Douglas Furlong wrote: > ----- Message from bjiang_ee at yahoo.ca --------- Date: Mon, 07 Mar 2005 > 09:53:59 -0500 From: Benjamin Jiang Reply-To: > Discussions about development for the Fedora desktop > Subject: Re: X crashes when using a new > monitor To: Jon Savage , Discussions about > development for the Fedora desktop > >> Jon Savage wrote: >> >>> On Mon, 07 Mar 2005 09:38:11 -0500, Benjamin Jiang >>> wrote: >>> >>>> Hi, all, >>>> >>>> I installed a fresh copy of FC3 into my Dad's machine and everything >>>> worked fine. However, when I brought the machine to my Dad's place and >>>> plugged in his monitor (Acer 7154e), X crashes no matter what. I tried >>>> config xorg.conf with the correct HorizSync and VertRefresh, but it >>>> didn't even make any difference. >>>> >>> >>> Try booting into runlevel 3 and then >>> login as root and do system-config-display --reconfig. >>> >>> Bests >>> >>> JS >>> >>> >> Thanks, Jon. >> >> I did that yesterday already and no difference made. > > > When booting in to run level 3, log in as either a non privaliged > user, or as > root and running "startx", if X still crashes you should get some > output in the > terminal. > > Also look through the file /var/log/Xorg.0.log, as that will have some > more > information that may help us to help you. > > Doug > Doug, I pasted Xorg.0.log at the end of the first email I sent out. But, here is it again anyway: Xorg.0.log: X Window System Version 6.8.1 Release Date: 17 September 2004 X Protocol Version 11, Revision 0, Release 6.8.1 Build Operating System: Linux 2.4.21-14.ELsmp i686 [ELF] Current Operating System: Linux fallsview 2.6.9-1.667 #1 Tue Nov 2 14:41:31 EST 2004 i586 Build Date: 20 October 2004 Build Host: tweety.build.redhat.com Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.6.9-1.667 (bhcompile at tweety.build.redhat.com) (gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)) #1 Tue Nov 2 14:41:31 EST 2004 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: Sat Jan 1 02:56:07 2000 (++) Using config file: "xorg.conf.new" (==) ServerLayout "Default Layout" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Videocard0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (**) FontPath set to "unix/:7100" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (==) ModulePath set to "/usr/X11R6/lib/modules" (WW) Open APM failed (/dev/apm_bios) (No such file or directory) (II) Module ABI versions: X.Org ANSI C Emulation: 0.2 X.Org Video Driver: 0.7 X.Org XInput driver : 0.4 X.Org Server Extension : 0.2 X.Org Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.7 (--) using VT number 7 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x00000000, mode1Res1 = 0x80000000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,0598 card 0000,0000 rev 04 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,8598 card 0000,0000 rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1106,0686 card 1106,0000 rev 22 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1106,0571 card 0000,0000 rev 10 class 01,01,8a hdr 00 (II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 10 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 1106,3038 card 0925,1234 rev 10 class 0c,03,00 hdr 00 (II) PCI: 00:07:4: chip 1106,3057 card 0000,0000 rev 30 class 06,00,00 hdr 00 (II) PCI: 00:08:0: chip 122d,50dc card 122d,8000 rev 10 class 04,01,00 hdr 00 (II) PCI: 00:0b:0: chip 10d9,0531 card 15e8,8110 rev 25 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 1023,9880 card 1023,9880 rev 3a class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set) (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xd4000000 - 0xd7ffffff (0x4000000) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (II) Host-to-PCI bridge: (II) Bus -1: bridge is at (0:7:4), (-1,-1,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus -1 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus -1 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus -1 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (--) PCI:*(1:0:0) Trident Microsystems Blade 3D PCI/AGP rev 58, Mem @ 0xd5800000/23, 0xd6000000/17, 0xd5000000/23 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) PCI Memory resource overlap reduced 0xd0000000 from 0xd3ffffff to 0xcfffffff (II) Active PCI resource ranges: [0] -1 0 0xd9000000 - 0xd90000ff (0x100) MX[B] [1] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O [2] -1 0 0xd5000000 - 0xd57fffff (0x800000) MX[B](B) [3] -1 0 0xd6000000 - 0xd601ffff (0x20000) MX[B](B) [4] -1 0 0xd5800000 - 0xd5ffffff (0x800000) MX[B](B) [5] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B] [6] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] [7] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B] [8] -1 0 0x0000d400 - 0x0000d403 (0x4) IX[B] [9] -1 0 0x0000d000 - 0x0000d007 (0x8) IX[B] [10] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B] [11] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] [12] -1 0 0x0000c400 - 0x0000c41f (0x20) IX[B] [13] -1 0 0x0000c000 - 0x0000c00f (0x10) IX[B] (II) Active PCI resource ranges after removing overlaps: [0] -1 0 0xd9000000 - 0xd90000ff (0x100) MX[B] [1] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O [2] -1 0 0xd5000000 - 0xd57fffff (0x800000) MX[B](B) [3] -1 0 0xd6000000 - 0xd601ffff (0x20000) MX[B](B) [4] -1 0 0xd5800000 - 0xd5ffffff (0x800000) MX[B](B) [5] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B] [6] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] [7] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B] [8] -1 0 0x0000d400 - 0x0000d403 (0x4) IX[B] [9] -1 0 0x0000d000 - 0x0000d007 (0x8) IX[B] [10] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B] [11] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] [12] -1 0 0x0000c400 - 0x0000c41f (0x20) IX[B] [13] -1 0 0x0000c000 - 0x0000c00f (0x10) IX[B] (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) All system resource ranges: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xd9000000 - 0xd90000ff (0x100) MX[B] [6] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O [7] -1 0 0xd5000000 - 0xd57fffff (0x800000) MX[B](B) [8] -1 0 0xd6000000 - 0xd601ffff (0x20000) MX[B](B) [9] -1 0 0xd5800000 - 0xd5ffffff (0x800000) MX[B](B) [10] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [11] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [12] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B] [13] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] [14] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B] [15] -1 0 0x0000d400 - 0x0000d403 (0x4) IX[B] [16] -1 0 0x0000d000 - 0x0000d007 (0x8) IX[B] [17] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B] [18] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] [19] -1 0 0x0000c400 - 0x0000c41f (0x20) IX[B] [20] -1 0 0x0000c000 - 0x0000c00f (0x10) IX[B] (II) LoadModule: "dbe" (II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a (II) Module dbe: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.2 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "extmod" (II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a (II) Module extmod: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.2 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "fbdevhw" (II) Loading /usr/X11R6/lib/modules/linux/libfbdevhw.a (II) Module fbdevhw: vendor="X.Org Foundation" compiled for 6.8.1, module version = 0.0.2 ABI class: X.Org Video Driver, version 0.7 (II) LoadModule: "glx" (II) Loading /usr/X11R6/lib/modules/extensions/libglx.a (II) Module glx: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading sub module "GLcore" (II) LoadModule: "GLcore" (II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a (II) Module GLcore: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading extension GLX (II) LoadModule: "record" (II) Loading /usr/X11R6/lib/modules/extensions/librecord.a (II) Module record: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.13.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.2 (II) Loading extension RECORD (II) LoadModule: "freetype" (II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.so (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project" compiled for 6.8.1, module version = 2.1.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font FreeType (II) LoadModule: "type1" (II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a (II) Module type1: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.2 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Type1 (II) Loading font CID (II) LoadModule: "dri" (II) Loading /usr/X11R6/lib/modules/extensions/libdri.a (II) Module dri: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading sub module "drm" (II) LoadModule: "drm" (II) Loading /usr/X11R6/lib/modules/linux/libdrm.a (II) Module drm: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading extension XFree86-DRI (II) LoadModule: "trident" (II) Loading /usr/X11R6/lib/modules/drivers/trident_drv.o (II) Module trident: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 0.7 (II) LoadModule: "mouse" (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o (II) Module mouse: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.4 (II) LoadModule: "kbd" (II) Loading /usr/X11R6/lib/modules/input/kbd_drv.o (II) Module kbd: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.4 (II) TRIDENT: driver for Trident chipsets: tvga9000, tvga9000i, tvga8900c, tvga8900d, tvga9200cxr, tgui9400cxi, cyber9320, cyber9388, cyber9397, cyber9397dvd, cyber9520, cyber9525dvd, cyberblade/e4, tgui9420dgi, tgui9440agi, tgui9660, tgui9680, providia9682, providia9685, cyber9382, cyber9385, 3dimage975, 3dimage985, blade3d, cyberbladei7, cyberbladei7d, cyberbladei1, cyberbladei1d, cyberbladeAi1, cyberbladeAi1d, bladeXP, cyberbladeXPAi1, cyberbladeXP4 (II) Primary Device is: PCI 01:00:0 (--) Assigning device section with no busID to primary device (--) Chipset blade3d found (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xd9000000 - 0xd90000ff (0x100) MX[B] [6] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O [7] -1 0 0xd5000000 - 0xd57fffff (0x800000) MX[B](B) [8] -1 0 0xd6000000 - 0xd601ffff (0x20000) MX[B](B) [9] -1 0 0xd5800000 - 0xd5ffffff (0x800000) MX[B](B) [10] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [11] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [12] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B] [13] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] [14] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B] [15] -1 0 0x0000d400 - 0x0000d403 (0x4) IX[B] [16] -1 0 0x0000d000 - 0x0000d007 (0x8) IX[B] [17] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B] [18] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] [19] -1 0 0x0000c400 - 0x0000c41f (0x20) IX[B] [20] -1 0 0x0000c000 - 0x0000c00f (0x10) IX[B] (II) resource ranges after probing: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xd9000000 - 0xd90000ff (0x100) MX[B] [6] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O [7] -1 0 0xd5000000 - 0xd57fffff (0x800000) MX[B](B) [8] -1 0 0xd6000000 - 0xd601ffff (0x20000) MX[B](B) [9] -1 0 0xd5800000 - 0xd5ffffff (0x800000) MX[B](B) [10] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [11] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [12] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [13] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [14] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [15] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B] [16] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] [17] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B] [18] -1 0 0x0000d400 - 0x0000d403 (0x4) IX[B] [19] -1 0 0x0000d000 - 0x0000d007 (0x8) IX[B] [20] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B] [21] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] [22] -1 0 0x0000c400 - 0x0000c41f (0x20) IX[B] [23] -1 0 0x0000c000 - 0x0000c00f (0x10) IX[B] [24] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [25] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (**) TRIDENT(0): Depth 16, (--) framebuffer bpp 16 (II) Loading sub module "vgahw" (II) LoadModule: "vgahw" (II) Loading /usr/X11R6/lib/modules/libvgahw.a (II) Module vgahw: vendor="X.Org Foundation" compiled for 6.8.1, module version = 0.1.0 ABI class: X.Org Video Driver, version 0.7 (II) TRIDENT(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (II) Loading sub module "ramdac" (II) LoadModule: "ramdac" (II) Loading /usr/X11R6/lib/modules/libramdac.a (II) Module ramdac: vendor="X.Org Foundation" compiled for 6.8.1, module version = 0.1.0 ABI class: X.Org Video Driver, version 0.7 (==) TRIDENT(0): RGB weight 565 (==) TRIDENT(0): Default visual is TrueColor (==) TRIDENT(0): Using gamma correction (1.0, 1.0, 1.0) (==) TRIDENT(0): Linear framebuffer at 0xD5800000 (--) TRIDENT(0): IO registers at 0xD6000000 (II) Loading sub module "vbe" (II) LoadModule: "vbe" (II) Loading /usr/X11R6/lib/modules/libvbe.a (II) Module vbe: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.1.0 ABI class: X.Org Video Driver, version 0.7 (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/X11R6/lib/modules/linux/libint10.a (II) Module int10: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.7 (II) TRIDENT(0): initializing int10 (II) TRIDENT(0): Primary V_BIOS segment is: 0xc000 (II) TRIDENT(0): VESA BIOS detected (II) TRIDENT(0): VESA VBE Version 2.0 (II) TRIDENT(0): VESA VBE Total Mem: 8192 kB (II) TRIDENT(0): VESA VBE OEM: Trident Blade 3D (II) TRIDENT(0): VESA VBE OEM Software Rev: 2.0 (II) TRIDENT(0): VESA VBE OEM Vendor: TRIDENT MICROSYSTEMS INC. (II) TRIDENT(0): VESA VBE OEM Product: Blade 3D (II) TRIDENT(0): VESA VBE OEM Product Rev: J 6.4 (38) (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Loading /usr/X11R6/lib/modules/libddc.a (II) Module ddc: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.7 (II) TRIDENT(0): VESA VBE DDC supported (II) TRIDENT(0): VESA VBE DDC Level 2 (II) TRIDENT(0): VESA VBE DDC transfer in appr. 1 sec. (II) TRIDENT(0): VESA VBE DDC read successfully (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Reloading /usr/X11R6/lib/modules/libddc.a (II) TRIDENT(0): Manufacturer: API Model: 4536 Serial#: 924 (II) TRIDENT(0): Year: 1997 Week: 26 (II) TRIDENT(0): EDID Version: 1.2 (II) TRIDENT(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V (II) TRIDENT(0): Sync: Separate (II) TRIDENT(0): Max H-Image Size [cm]: horiz.: 27 vert.: 20 (II) TRIDENT(0): Gamma: 2.66 (II) TRIDENT(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display (II) TRIDENT(0): redX: 0.625 redY: 0.340 greenX: 0.284 greenY: 0.600 (II) TRIDENT(0): blueX: 0.149 blueY: 0.064 whiteX: 0.280 whiteY: 0.311 (II) TRIDENT(0): Supported VESA Video Modes: (II) TRIDENT(0): 720x400 at 70Hz (II) TRIDENT(0): 640x480 at 60Hz (II) TRIDENT(0): 640x480 at 72Hz (II) TRIDENT(0): 640x480 at 75Hz (II) TRIDENT(0): 800x600 at 60Hz (II) TRIDENT(0): 800x600 at 72Hz (II) TRIDENT(0): 800x600 at 75Hz (II) TRIDENT(0): 1024x768 at 60Hz (II) TRIDENT(0): Manufacturer's mask: 21 (--) TRIDENT(0): Revision is 58 (--) TRIDENT(0): Found Blade3D chip (--) TRIDENT(0): RAM type is SDRAM (--) TRIDENT(0): Using HW cursor (--) TRIDENT(0): VideoRAM: 8192 kByte (--) TRIDENT(0): Memory Clock is 109.77 MHz (==) TRIDENT(0): Min pixel clock is 12 MHz (--) TRIDENT(0): Max pixel clock is 230 MHz (II) TRIDENT(0): Monitor0: Using hsync range of 31.00-60.00 kHz (II) TRIDENT(0): Monitor0: Using vrefresh range of 55.00-90.00 Hz (II) TRIDENT(0): Clock range: 12.00 to 230.00 MHz (II) TRIDENT(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "360x200" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1024x768" (hsync out of range) (II) TRIDENT(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1152x864" (hsync out of range) (II) TRIDENT(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1280x960" (hsync out of range) (II) TRIDENT(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1280x1024" (hsync out of range) (II) TRIDENT(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1280x1024" (hsync out of range) (II) TRIDENT(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1280x1024" (hsync out of range) (II) TRIDENT(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1600x1200" (hsync out of range) (II) TRIDENT(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1600x1200" (hsync out of range) (II) TRIDENT(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1600x1200" (hsync out of range) (II) TRIDENT(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1600x1200" (hsync out of range) (II) TRIDENT(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1600x1200" (hsync out of range) (II) TRIDENT(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1792x1344" (hsync out of range) (II) TRIDENT(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1792x1344" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1856x1392" (hsync out of range) (II) TRIDENT(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1856x1392" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "416x312" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "576x384" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1152x864" (hsync out of range) (II) TRIDENT(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1400x1050" (hsync out of range) (II) TRIDENT(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1400x1050" (hsync out of range) (II) TRIDENT(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1400x1050" (hsync out of range) (II) TRIDENT(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1400x1050" (hsync out of range) (II) TRIDENT(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1600x1024" (hsync out of range) (II) TRIDENT(0): Not using default mode "800x512" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1920x1200" (hsync out of range) (II) TRIDENT(0): Not using default mode "960x600" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1920x1440" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) TRIDENT(0): Not using default mode "1280x960" (width too large for virtual size) (II) TRIDENT(0): Not using default mode "1152x768" (width too large for virtual size) (II) TRIDENT(0): Not using default mode "1024x768" (width too large for virtual size) (II) TRIDENT(0): Not using default mode "1024x768" (width too large for virtual size) (II) TRIDENT(0): Not using default mode "1024x768" (width too large for virtual size) (II) TRIDENT(0): Not using default mode "1024x768" (width too large for virtual size) (II) TRIDENT(0): Not using default mode "832x624" (width too large for virtual size) (--) TRIDENT(0): Virtual size is 800x600 (pitch 800) (**) TRIDENT(0): *Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz (II) TRIDENT(0): Modeline "800x600" 56.30 800 832 896 1048 600 601 604 631 +hsync +vsync (**) TRIDENT(0): *Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz (II) TRIDENT(0): Modeline "640x480" 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (**) TRIDENT(0): Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz (II) TRIDENT(0): Modeline "800x600" 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (**) TRIDENT(0): Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz (II) TRIDENT(0): Modeline "800x600" 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (**) TRIDENT(0): Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz (II) TRIDENT(0): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (**) TRIDENT(0): Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz (II) TRIDENT(0): Modeline "800x600" 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (**) TRIDENT(0): Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz (II) TRIDENT(0): Modeline "640x480" 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (**) TRIDENT(0): Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz (II) TRIDENT(0): Modeline "640x480" 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (**) TRIDENT(0): Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz (II) TRIDENT(0): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (**) TRIDENT(0): Default mode "720x400": 35.5 MHz, 37.9 kHz, 85.0 Hz (II) TRIDENT(0): Modeline "720x400" 35.50 720 756 828 936 400 401 404 446 -hsync +vsync (**) TRIDENT(0): Default mode "640x400": 31.5 MHz, 37.9 kHz, 85.1 Hz (II) TRIDENT(0): Modeline "640x400" 31.50 640 672 736 832 400 401 404 445 -hsync +vsync (**) TRIDENT(0): Default mode "640x350": 31.5 MHz, 37.9 kHz, 85.1 Hz (II) TRIDENT(0): Modeline "640x350" 31.50 640 672 736 832 350 382 385 445 +hsync -vsync (**) TRIDENT(0): Display dimensions: (270, 200) mm (**) TRIDENT(0): DPI set to (75, 76) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/X11R6/lib/modules/libfb.a (II) Module fb: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.2 (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Loading /usr/X11R6/lib/modules/libi2c.a (II) Module i2c: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.2.0 ABI class: X.Org Video Driver, version 0.7 (II) Loading sub module "xaa" (II) LoadModule: "xaa" (II) Loading /usr/X11R6/lib/modules/libxaa.a (II) Module xaa: vendor="X.Org Foundation" compiled for 6.8.1, module version = 1.2.0 ABI class: X.Org Video Driver, version 0.7 *** If unresolved symbols were reported above, they might not *** be the reason for the server aborting. Fatal server error: Caught signal 11. Server aborting Please consult the The X.Org Foundation support at http://wiki.X.Org for help. Please also check the log file at "/var/log/Xorg.0.log" for additional information. Ben. From kyrre at solution-forge.net Mon Mar 7 17:51:56 2005 From: kyrre at solution-forge.net (Kyrre Ness Sjobak) Date: Mon, 07 Mar 2005 18:51:56 +0100 Subject: X crashes when using a new monitor In-Reply-To: <422C75D2.7060604@yahoo.ca> References: <422C6753.2090300@yahoo.ca> <2ad7cea105030706461e1e280@mail.gmail.com> <422C6B07.4010501@yahoo.ca> <20050307153054.c2f3mb7npl8oog4o@corrig.dark-hill.co.uk> <422C75D2.7060604@yahoo.ca> Message-ID: <1110217916.3439.11.camel@localhost.localdomain> man, 07.03.2005 kl. 16.40 skrev Benjamin Jiang: > Douglas Furlong wrote: > > > ----- Message from bjiang_ee at yahoo.ca --------- Date: Mon, 07 Mar 2005 > > 09:53:59 -0500 From: Benjamin Jiang Reply-To: > > Discussions about development for the Fedora desktop > > Subject: Re: X crashes when using a new > > monitor To: Jon Savage , Discussions about > > development for the Fedora desktop > > > >> Jon Savage wrote: > >> > >>> On Mon, 07 Mar 2005 09:38:11 -0500, Benjamin Jiang > >>> wrote: > >>> > >>>> Hi, all, > >>>> > >>>> I installed a fresh copy of FC3 into my Dad's machine and everything > >>>> worked fine. However, when I brought the machine to my Dad's place and > >>>> plugged in his monitor (Acer 7154e), X crashes no matter what. I tried > >>>> config xorg.conf with the correct HorizSync and VertRefresh, but it > >>>> didn't even make any difference. > >>>> > >>> > >>> Try booting into runlevel 3 and then > >>> login as root and do system-config-display --reconfig. > >>> > >>> Bests > >>> > >>> JS > >>> > >>> > >> Thanks, Jon. > >> > >> I did that yesterday already and no difference made. > > > > > > When booting in to run level 3, log in as either a non privaliged > > user, or as > > root and running "startx", if X still crashes you should get some > > output in the > > terminal. > > > > Also look through the file /var/log/Xorg.0.log, as that will have some > > more > > information that may help us to help you. > > > > Doug > > > Doug, I pasted Xorg.0.log at the end of the first email I sent out. > > But, here is it again anyway: > Xorg.0.log: > > X Window System Version 6.8.1 > Release Date: 17 September 2004 > X Protocol Version 11, Revision 0, Release 6.8.1 > Build Operating System: Linux 2.4.21-14.ELsmp i686 [ELF] > Current Operating System: Linux fallsview 2.6.9-1.667 #1 Tue Nov 2 > 14:41:31 EST 2004 i586 > Build Date: 20 October 2004 > Build Host: tweety.build.redhat.com > > Before reporting problems, check http://wiki.X.Org > to make sure that you have the latest version. > Module Loader present > OS Kernel: Linux version 2.6.9-1.667 (bhcompile at tweety.build.redhat.com) > (gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)) #1 Tue Nov 2 14:41:31 > EST 2004 > 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: Sat Jan 1 02:56:07 2000 > (++) Using config file: "xorg.conf.new" > (==) ServerLayout "Default Layout" > (**) |-->Screen "Screen0" (0) > (**) | |-->Monitor "Monitor0" > (**) | |-->Device "Videocard0" > (**) |-->Input Device "Mouse0" > (**) |-->Input Device "Keyboard0" > (**) FontPath set to "unix/:7100" > (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" > (==) ModulePath set to "/usr/X11R6/lib/modules" > (WW) Open APM failed (/dev/apm_bios) (No such file or directory) > (II) Module ABI versions: > X.Org ANSI C Emulation: 0.2 > X.Org Video Driver: 0.7 > X.Org XInput driver : 0.4 > X.Org Server Extension : 0.2 > X.Org Font Renderer : 0.4 > (II) Loader running on linux > (II) LoadModule: "bitmap" > (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a > (II) Module bitmap: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 1.0.0 > Module class: X.Org Font Renderer > ABI class: X.Org Font Renderer, version 0.4 > (II) Loading font Bitmap > (II) LoadModule: "pcidata" > (II) Loading /usr/X11R6/lib/modules/libpcidata.a > (II) Module pcidata: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 1.0.0 > ABI class: X.Org Video Driver, version 0.7 > (--) using VT number 7 > > (II) PCI: Probing config type using method 1 > (II) PCI: Config type is 1 > (II) PCI: stages = 0x03, oldVal1 = 0x00000000, mode1Res1 = 0x80000000 > (II) PCI: PCI scan (all values are in hex) > (II) PCI: 00:00:0: chip 1106,0598 card 0000,0000 rev 04 class 06,00,00 > hdr 00 > (II) PCI: 00:01:0: chip 1106,8598 card 0000,0000 rev 00 class 06,04,00 > hdr 01 > (II) PCI: 00:07:0: chip 1106,0686 card 1106,0000 rev 22 class 06,01,00 > hdr 80 > (II) PCI: 00:07:1: chip 1106,0571 card 0000,0000 rev 10 class 01,01,8a > hdr 00 > (II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 10 class 0c,03,00 > hdr 00 > (II) PCI: 00:07:3: chip 1106,3038 card 0925,1234 rev 10 class 0c,03,00 > hdr 00 > (II) PCI: 00:07:4: chip 1106,3057 card 0000,0000 rev 30 class 06,00,00 > hdr 00 > (II) PCI: 00:08:0: chip 122d,50dc card 122d,8000 rev 10 class 04,01,00 > hdr 00 > (II) PCI: 00:0b:0: chip 10d9,0531 card 15e8,8110 rev 25 class 02,00,00 > hdr 00 > (II) PCI: 01:00:0: chip 1023,9880 card 1023,9880 rev 3a class 03,00,00 > hdr 00 > (II) PCI: End of PCI scan > (II) Host-to-PCI bridge: > (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) > (II) Bus 0 I/O range: > [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] > (II) Bus 0 non-prefetchable memory range: > [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] > (II) Bus 0 prefetchable memory range: > [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] > (II) PCI-to-PCI bridge: > (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set) > (II) Bus 1 non-prefetchable memory range: > [0] -1 0 0xd4000000 - 0xd7ffffff (0x4000000) MX[B] > (II) PCI-to-ISA bridge: > (II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) > (II) Host-to-PCI bridge: > (II) Bus -1: bridge is at (0:7:4), (-1,-1,1), BCTRL: 0x0008 (VGA_EN is set) > (II) Bus -1 I/O range: > [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] > (II) Bus -1 non-prefetchable memory range: > [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] > (II) Bus -1 prefetchable memory range: > [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] > (--) PCI:*(1:0:0) Trident Microsystems Blade 3D PCI/AGP rev 58, Mem @ > 0xd5800000/23, 0xd6000000/17, 0xd5000000/23 > (II) Addressable bus resource ranges are > [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] > [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] > (II) OS-reported resource ranges: > [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) > [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) > [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] > [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] > [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] > [5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] > [6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] > (II) PCI Memory resource overlap reduced 0xd0000000 from 0xd3ffffff to > 0xcfffffff > (II) Active PCI resource ranges: > [0] -1 0 0xd9000000 - 0xd90000ff (0x100) MX[B] > [1] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O > [2] -1 0 0xd5000000 - 0xd57fffff (0x800000) MX[B](B) > [3] -1 0 0xd6000000 - 0xd601ffff (0x20000) MX[B](B) > [4] -1 0 0xd5800000 - 0xd5ffffff (0x800000) MX[B](B) > [5] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B] > [6] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] > [7] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B] > [8] -1 0 0x0000d400 - 0x0000d403 (0x4) IX[B] > [9] -1 0 0x0000d000 - 0x0000d007 (0x8) IX[B] > [10] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B] > [11] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] > [12] -1 0 0x0000c400 - 0x0000c41f (0x20) IX[B] > [13] -1 0 0x0000c000 - 0x0000c00f (0x10) IX[B] > (II) Active PCI resource ranges after removing overlaps: > [0] -1 0 0xd9000000 - 0xd90000ff (0x100) MX[B] > [1] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O > [2] -1 0 0xd5000000 - 0xd57fffff (0x800000) MX[B](B) > [3] -1 0 0xd6000000 - 0xd601ffff (0x20000) MX[B](B) > [4] -1 0 0xd5800000 - 0xd5ffffff (0x800000) MX[B](B) > [5] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B] > [6] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] > [7] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B] > [8] -1 0 0x0000d400 - 0x0000d403 (0x4) IX[B] > [9] -1 0 0x0000d000 - 0x0000d007 (0x8) IX[B] > [10] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B] > [11] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] > [12] -1 0 0x0000c400 - 0x0000c41f (0x20) IX[B] > [13] -1 0 0x0000c000 - 0x0000c00f (0x10) IX[B] > (II) OS-reported resource ranges after removing overlaps with PCI: > [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) > [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) > [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] > [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] > [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] > [5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] > [6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] > (II) All system resource ranges: > [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) > [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) > [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] > [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] > [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] > [5] -1 0 0xd9000000 - 0xd90000ff (0x100) MX[B] > [6] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O > [7] -1 0 0xd5000000 - 0xd57fffff (0x800000) MX[B](B) > [8] -1 0 0xd6000000 - 0xd601ffff (0x20000) MX[B](B) > [9] -1 0 0xd5800000 - 0xd5ffffff (0x800000) MX[B](B) > [10] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] > [11] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] > [12] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B] > [13] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] > [14] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B] > [15] -1 0 0x0000d400 - 0x0000d403 (0x4) IX[B] > [16] -1 0 0x0000d000 - 0x0000d007 (0x8) IX[B] > [17] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B] > [18] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] > [19] -1 0 0x0000c400 - 0x0000c41f (0x20) IX[B] > [20] -1 0 0x0000c000 - 0x0000c00f (0x10) IX[B] > (II) LoadModule: "dbe" > (II) Loading /usr/X11R6/lib/modules/extensions/libdbe.a > (II) Module dbe: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 1.0.0 > Module class: X.Org Server Extension > ABI class: X.Org Server Extension, version 0.2 > (II) Loading extension DOUBLE-BUFFER > (II) LoadModule: "extmod" > (II) Loading /usr/X11R6/lib/modules/extensions/libextmod.a > (II) Module extmod: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 1.0.0 > Module class: X.Org Server Extension > ABI class: X.Org Server Extension, version 0.2 > (II) Loading extension SHAPE > (II) Loading extension MIT-SUNDRY-NONSTANDARD > (II) Loading extension BIG-REQUESTS > (II) Loading extension SYNC > (II) Loading extension MIT-SCREEN-SAVER > (II) Loading extension XC-MISC > (II) Loading extension XFree86-VidModeExtension > (II) Loading extension XFree86-Misc > (II) Loading extension XFree86-DGA > (II) Loading extension DPMS > (II) Loading extension TOG-CUP > (II) Loading extension Extended-Visual-Information > (II) Loading extension XVideo > (II) Loading extension XVideo-MotionCompensation > (II) Loading extension X-Resource > (II) LoadModule: "fbdevhw" > (II) Loading /usr/X11R6/lib/modules/linux/libfbdevhw.a > (II) Module fbdevhw: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 0.0.2 > ABI class: X.Org Video Driver, version 0.7 > (II) LoadModule: "glx" > (II) Loading /usr/X11R6/lib/modules/extensions/libglx.a > (II) Module glx: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 1.0.0 > ABI class: X.Org Server Extension, version 0.2 > (II) Loading sub module "GLcore" > (II) LoadModule: "GLcore" > (II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.a > (II) Module GLcore: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 1.0.0 > ABI class: X.Org Server Extension, version 0.2 > (II) Loading extension GLX > (II) LoadModule: "record" > (II) Loading /usr/X11R6/lib/modules/extensions/librecord.a > (II) Module record: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 1.13.0 > Module class: X.Org Server Extension > ABI class: X.Org Server Extension, version 0.2 > (II) Loading extension RECORD > (II) LoadModule: "freetype" > (II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.so > (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project" > compiled for 6.8.1, module version = 2.1.0 > Module class: X.Org Font Renderer > ABI class: X.Org Font Renderer, version 0.4 > (II) Loading font FreeType > (II) LoadModule: "type1" > (II) Loading /usr/X11R6/lib/modules/fonts/libtype1.a > (II) Module type1: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 1.0.2 > Module class: X.Org Font Renderer > ABI class: X.Org Font Renderer, version 0.4 > (II) Loading font Type1 > (II) Loading font CID > (II) LoadModule: "dri" > (II) Loading /usr/X11R6/lib/modules/extensions/libdri.a > (II) Module dri: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 1.0.0 > ABI class: X.Org Server Extension, version 0.2 > (II) Loading sub module "drm" > (II) LoadModule: "drm" > (II) Loading /usr/X11R6/lib/modules/linux/libdrm.a > (II) Module drm: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 1.0.0 > ABI class: X.Org Server Extension, version 0.2 > (II) Loading extension XFree86-DRI > (II) LoadModule: "trident" > (II) Loading /usr/X11R6/lib/modules/drivers/trident_drv.o > (II) Module trident: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 1.0.0 > Module class: X.Org Video Driver > ABI class: X.Org Video Driver, version 0.7 > (II) LoadModule: "mouse" > (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.o > (II) Module mouse: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 1.0.0 > Module class: X.Org XInput Driver > ABI class: X.Org XInput driver, version 0.4 > (II) LoadModule: "kbd" > (II) Loading /usr/X11R6/lib/modules/input/kbd_drv.o > (II) Module kbd: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 1.0.0 > Module class: X.Org XInput Driver > ABI class: X.Org XInput driver, version 0.4 > (II) TRIDENT: driver for Trident chipsets: tvga9000, tvga9000i, tvga8900c, > tvga8900d, tvga9200cxr, tgui9400cxi, cyber9320, cyber9388, cyber9397, > cyber9397dvd, cyber9520, cyber9525dvd, cyberblade/e4, tgui9420dgi, > tgui9440agi, tgui9660, tgui9680, providia9682, providia9685, > cyber9382, cyber9385, 3dimage975, 3dimage985, blade3d, cyberbladei7, > cyberbladei7d, cyberbladei1, cyberbladei1d, cyberbladeAi1, > cyberbladeAi1d, bladeXP, cyberbladeXPAi1, cyberbladeXP4 > (II) Primary Device is: PCI 01:00:0 > (--) Assigning device section with no busID to primary device > (--) Chipset blade3d found > (II) resource ranges after xf86ClaimFixedResources() call: > [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) > [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) > [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] > [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] > [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] > [5] -1 0 0xd9000000 - 0xd90000ff (0x100) MX[B] > [6] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O > [7] -1 0 0xd5000000 - 0xd57fffff (0x800000) MX[B](B) > [8] -1 0 0xd6000000 - 0xd601ffff (0x20000) MX[B](B) > [9] -1 0 0xd5800000 - 0xd5ffffff (0x800000) MX[B](B) > [10] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] > [11] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] > [12] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B] > [13] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] > [14] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B] > [15] -1 0 0x0000d400 - 0x0000d403 (0x4) IX[B] > [16] -1 0 0x0000d000 - 0x0000d007 (0x8) IX[B] > [17] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B] > [18] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] > [19] -1 0 0x0000c400 - 0x0000c41f (0x20) IX[B] > [20] -1 0 0x0000c000 - 0x0000c00f (0x10) IX[B] > (II) resource ranges after probing: > [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) > [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) > [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] > [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] > [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] > [5] -1 0 0xd9000000 - 0xd90000ff (0x100) MX[B] > [6] -1 0 0xd0000000 - 0xcfffffff (0x0) MX[B]O > [7] -1 0 0xd5000000 - 0xd57fffff (0x800000) MX[B](B) > [8] -1 0 0xd6000000 - 0xd601ffff (0x20000) MX[B](B) > [9] -1 0 0xd5800000 - 0xd5ffffff (0x800000) MX[B](B) > [10] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] > [11] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] > [12] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] > [13] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] > [14] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] > [15] -1 0 0x0000e000 - 0x0000e0ff (0x100) IX[B] > [16] -1 0 0x0000dc00 - 0x0000dc3f (0x40) IX[B] > [17] -1 0 0x0000d800 - 0x0000d807 (0x8) IX[B] > [18] -1 0 0x0000d400 - 0x0000d403 (0x4) IX[B] > [19] -1 0 0x0000d000 - 0x0000d007 (0x8) IX[B] > [20] -1 0 0x0000cc00 - 0x0000cc7f (0x80) IX[B] > [21] -1 0 0x0000c800 - 0x0000c81f (0x20) IX[B] > [22] -1 0 0x0000c400 - 0x0000c41f (0x20) IX[B] > [23] -1 0 0x0000c000 - 0x0000c00f (0x10) IX[B] > [24] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] > [25] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] > (II) Setting vga for screen 0. > (**) TRIDENT(0): Depth 16, (--) framebuffer bpp 16 > (II) Loading sub module "vgahw" > (II) LoadModule: "vgahw" > (II) Loading /usr/X11R6/lib/modules/libvgahw.a > (II) Module vgahw: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 0.1.0 > ABI class: X.Org Video Driver, version 0.7 > (II) TRIDENT(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset > is 0x0000 > (II) Loading sub module "ramdac" > (II) LoadModule: "ramdac" > (II) Loading /usr/X11R6/lib/modules/libramdac.a > (II) Module ramdac: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 0.1.0 > ABI class: X.Org Video Driver, version 0.7 > (==) TRIDENT(0): RGB weight 565 > (==) TRIDENT(0): Default visual is TrueColor > (==) TRIDENT(0): Using gamma correction (1.0, 1.0, 1.0) > (==) TRIDENT(0): Linear framebuffer at 0xD5800000 > (--) TRIDENT(0): IO registers at 0xD6000000 > (II) Loading sub module "vbe" > (II) LoadModule: "vbe" > (II) Loading /usr/X11R6/lib/modules/libvbe.a > (II) Module vbe: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 1.1.0 > ABI class: X.Org Video Driver, version 0.7 > (II) Loading sub module "int10" > (II) LoadModule: "int10" > (II) Loading /usr/X11R6/lib/modules/linux/libint10.a > (II) Module int10: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 1.0.0 > ABI class: X.Org Video Driver, version 0.7 > (II) TRIDENT(0): initializing int10 > (II) TRIDENT(0): Primary V_BIOS segment is: 0xc000 > (II) TRIDENT(0): VESA BIOS detected > (II) TRIDENT(0): VESA VBE Version 2.0 > (II) TRIDENT(0): VESA VBE Total Mem: 8192 kB > (II) TRIDENT(0): VESA VBE OEM: Trident Blade 3D > (II) TRIDENT(0): VESA VBE OEM Software Rev: 2.0 > (II) TRIDENT(0): VESA VBE OEM Vendor: TRIDENT MICROSYSTEMS INC. > (II) TRIDENT(0): VESA VBE OEM Product: Blade 3D > (II) TRIDENT(0): VESA VBE OEM Product Rev: J 6.4 (38) > (II) Loading sub module "ddc" > (II) LoadModule: "ddc" > (II) Loading /usr/X11R6/lib/modules/libddc.a > (II) Module ddc: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 1.0.0 > ABI class: X.Org Video Driver, version 0.7 > (II) TRIDENT(0): VESA VBE DDC supported > (II) TRIDENT(0): VESA VBE DDC Level 2 > (II) TRIDENT(0): VESA VBE DDC transfer in appr. 1 sec. > (II) TRIDENT(0): VESA VBE DDC read successfully > (II) Loading sub module "ddc" > (II) LoadModule: "ddc" > (II) Reloading /usr/X11R6/lib/modules/libddc.a > (II) TRIDENT(0): Manufacturer: API Model: 4536 Serial#: 924 > (II) TRIDENT(0): Year: 1997 Week: 26 > (II) TRIDENT(0): EDID Version: 1.2 > (II) TRIDENT(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V > (II) TRIDENT(0): Sync: Separate > (II) TRIDENT(0): Max H-Image Size [cm]: horiz.: 27 vert.: 20 > (II) TRIDENT(0): Gamma: 2.66 > (II) TRIDENT(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display > (II) TRIDENT(0): redX: 0.625 redY: 0.340 greenX: 0.284 greenY: 0.600 > (II) TRIDENT(0): blueX: 0.149 blueY: 0.064 whiteX: 0.280 whiteY: 0.311 > (II) TRIDENT(0): Supported VESA Video Modes: > (II) TRIDENT(0): 720x400 at 70Hz > (II) TRIDENT(0): 640x480 at 60Hz > (II) TRIDENT(0): 640x480 at 72Hz > (II) TRIDENT(0): 640x480 at 75Hz > (II) TRIDENT(0): 800x600 at 60Hz > (II) TRIDENT(0): 800x600 at 72Hz > (II) TRIDENT(0): 800x600 at 75Hz > (II) TRIDENT(0): 1024x768 at 60Hz > (II) TRIDENT(0): Manufacturer's mask: 21 > (--) TRIDENT(0): Revision is 58 > (--) TRIDENT(0): Found Blade3D chip > (--) TRIDENT(0): RAM type is SDRAM > (--) TRIDENT(0): Using HW cursor > (--) TRIDENT(0): VideoRAM: 8192 kByte > (--) TRIDENT(0): Memory Clock is 109.77 MHz > (==) TRIDENT(0): Min pixel clock is 12 MHz > (--) TRIDENT(0): Max pixel clock is 230 MHz > (II) TRIDENT(0): Monitor0: Using hsync range of 31.00-60.00 kHz > (II) TRIDENT(0): Monitor0: Using vrefresh range of 55.00-90.00 Hz > (II) TRIDENT(0): Clock range: 12.00 to 230.00 MHz > (II) TRIDENT(0): Not using default mode "320x175" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "320x200" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "360x200" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "320x240" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "320x240" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "320x240" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "320x240" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "400x300" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "400x300" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "400x300" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "400x300" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "400x300" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "512x384" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "512x384" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "512x384" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "512x384" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1024x768" (hsync out of range) > (II) TRIDENT(0): Not using default mode "512x384" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1152x864" (hsync out of range) > (II) TRIDENT(0): Not using default mode "576x432" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "640x480" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1280x960" (hsync out of range) > (II) TRIDENT(0): Not using default mode "640x480" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1280x1024" (hsync out of range) > (II) TRIDENT(0): Not using default mode "640x512" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1280x1024" (hsync out of range) > (II) TRIDENT(0): Not using default mode "640x512" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1280x1024" (hsync out of range) > (II) TRIDENT(0): Not using default mode "640x512" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1600x1200" (hsync out of range) > (II) TRIDENT(0): Not using default mode "800x600" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1600x1200" (hsync out of range) > (II) TRIDENT(0): Not using default mode "800x600" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1600x1200" (hsync out of range) > (II) TRIDENT(0): Not using default mode "800x600" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1600x1200" (hsync out of range) > (II) TRIDENT(0): Not using default mode "800x600" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1600x1200" (hsync out of range) > (II) TRIDENT(0): Not using default mode "800x600" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1792x1344" (hsync out of range) > (II) TRIDENT(0): Not using default mode "896x672" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1792x1344" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "896x672" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1856x1392" (hsync out of range) > (II) TRIDENT(0): Not using default mode "928x696" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1856x1392" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "928x696" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1920x1440" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "960x720" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1920x1440" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "960x720" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "416x312" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "576x384" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1152x864" (hsync out of range) > (II) TRIDENT(0): Not using default mode "576x432" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1400x1050" (hsync out of range) > (II) TRIDENT(0): Not using default mode "700x525" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1400x1050" (hsync out of range) > (II) TRIDENT(0): Not using default mode "700x525" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1400x1050" (hsync out of range) > (II) TRIDENT(0): Not using default mode "700x525" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1400x1050" (hsync out of range) > (II) TRIDENT(0): Not using default mode "700x525" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1600x1024" (hsync out of range) > (II) TRIDENT(0): Not using default mode "800x512" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1920x1200" (hsync out of range) > (II) TRIDENT(0): Not using default mode "960x600" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1920x1440" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "960x720" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "2048x1536" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1024x768" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "2048x1536" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1024x768" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "2048x1536" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1024x768" (bad mode > clock/interlace/doublescan) > (II) TRIDENT(0): Not using default mode "1280x960" (width too large for > virtual size) > (II) TRIDENT(0): Not using default mode "1152x768" (width too large for > virtual size) > (II) TRIDENT(0): Not using default mode "1024x768" (width too large for > virtual size) > (II) TRIDENT(0): Not using default mode "1024x768" (width too large for > virtual size) > (II) TRIDENT(0): Not using default mode "1024x768" (width too large for > virtual size) > (II) TRIDENT(0): Not using default mode "1024x768" (width too large for > virtual size) > (II) TRIDENT(0): Not using default mode "832x624" (width too large for > virtual size) > (--) TRIDENT(0): Virtual size is 800x600 (pitch 800) > (**) TRIDENT(0): *Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz > (II) TRIDENT(0): Modeline "800x600" 56.30 800 832 896 1048 600 601 > 604 631 +hsync +vsync > (**) TRIDENT(0): *Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz > (II) TRIDENT(0): Modeline "640x480" 36.00 640 696 752 832 480 481 > 484 509 -hsync -vsync > (**) TRIDENT(0): Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz > (II) TRIDENT(0): Modeline "800x600" 49.50 800 816 896 1056 600 601 > 604 625 +hsync +vsync > (**) TRIDENT(0): Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz > (II) TRIDENT(0): Modeline "800x600" 50.00 800 856 976 1040 600 637 > 643 666 +hsync +vsync > (**) TRIDENT(0): Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz > (II) TRIDENT(0): Modeline "800x600" 40.00 800 840 968 1056 600 601 > 605 628 +hsync +vsync > (**) TRIDENT(0): Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz > (II) TRIDENT(0): Modeline "800x600" 36.00 800 824 896 1024 600 601 > 603 625 +hsync +vsync > (**) TRIDENT(0): Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz > (II) TRIDENT(0): Modeline "640x480" 31.50 640 656 720 840 480 481 > 484 500 -hsync -vsync > (**) TRIDENT(0): Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz > (II) TRIDENT(0): Modeline "640x480" 31.50 640 664 704 832 480 489 > 491 520 -hsync -vsync > (**) TRIDENT(0): Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz > (II) TRIDENT(0): Modeline "640x480" 25.20 640 656 752 800 480 490 > 492 525 -hsync -vsync > (**) TRIDENT(0): Default mode "720x400": 35.5 MHz, 37.9 kHz, 85.0 Hz > (II) TRIDENT(0): Modeline "720x400" 35.50 720 756 828 936 400 401 > 404 446 -hsync +vsync > (**) TRIDENT(0): Default mode "640x400": 31.5 MHz, 37.9 kHz, 85.1 Hz > (II) TRIDENT(0): Modeline "640x400" 31.50 640 672 736 832 400 401 > 404 445 -hsync +vsync > (**) TRIDENT(0): Default mode "640x350": 31.5 MHz, 37.9 kHz, 85.1 Hz > (II) TRIDENT(0): Modeline "640x350" 31.50 640 672 736 832 350 382 > 385 445 +hsync -vsync > (**) TRIDENT(0): Display dimensions: (270, 200) mm > (**) TRIDENT(0): DPI set to (75, 76) > (II) Loading sub module "fb" > (II) LoadModule: "fb" > (II) Loading /usr/X11R6/lib/modules/libfb.a > (II) Module fb: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 1.0.0 > ABI class: X.Org ANSI C Emulation, version 0.2 > (II) Loading sub module "i2c" > (II) LoadModule: "i2c" > (II) Loading /usr/X11R6/lib/modules/libi2c.a > (II) Module i2c: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 1.2.0 > ABI class: X.Org Video Driver, version 0.7 > (II) Loading sub module "xaa" > (II) LoadModule: "xaa" > (II) Loading /usr/X11R6/lib/modules/libxaa.a > (II) Module xaa: vendor="X.Org Foundation" > compiled for 6.8.1, module version = 1.2.0 > ABI class: X.Org Video Driver, version 0.7 > > *** If unresolved symbols were reported above, they might not > *** be the reason for the server aborting. > > Fatal server error: > Caught signal 11. Server aborting > > > Please consult the The X.Org Foundation support > at http://wiki.X.Org > for help. > Please also check the log file at "/var/log/Xorg.0.log" for additional > information. > > > > Ben. My experience is that if X sends the wrong sync to a monitor, all that happens is that the monitor shows a borked picture, or nothing at all exept an error message. X doesn't crash... From fedora-lists at dark-hill.co.uk Mon Mar 7 18:15:10 2005 From: fedora-lists at dark-hill.co.uk (Douglas Furlong) Date: Mon, 7 Mar 2005 18:15:10 +0000 Subject: X crashes when using a new monitor In-Reply-To: <1110217916.3439.11.camel@localhost.localdomain> References: <422C6753.2090300@yahoo.ca> <2ad7cea105030706461e1e280@mail.gmail.com> <422C6B07.4010501@yahoo.ca> <20050307153054.c2f3mb7npl8oog4o@corrig.dark-hill.co.uk> <422C75D2.7060604@yahoo.ca> <1110217916.3439.11.camel@localhost.localdomain> Message-ID: <20050307181510.v693q9w10di8c0kc@corrig.dark-hill.co.uk> ----- Message from kyrre at solution-forge.net --------- Date: Mon, 07 Mar 2005 18:51:56 +0100 From: Kyrre Ness Sjobak Reply-To: Discussions about development for the Fedora desktop Subject: Re: X crashes when using a new monitor To: Discussions about development for the Fedora desktop > man, 07.03.2005 kl. 16.40 skrev Benjamin Jiang: >> Douglas Furlong wrote: >> >> > ----- Message from bjiang_ee at yahoo.ca --------- Date: Mon, 07 Mar 2005 >> > 09:53:59 -0500 From: Benjamin Jiang Reply-To: >> > Discussions about development for the Fedora desktop >> > Subject: Re: X crashes when using a new >> > monitor To: Jon Savage , Discussions about >> > development for the Fedora desktop >> > >> >> Jon Savage wrote: >> >> >> >>> On Mon, 07 Mar 2005 09:38:11 -0500, Benjamin Jiang >> >>> wrote: >> >>> >> >>>> Hi, all, >> >>>> >> >>>> I installed a fresh copy of FC3 into my Dad's machine and everything >> >>>> worked fine. However, when I brought the machine to my Dad's place and >> >>>> plugged in his monitor (Acer 7154e), X crashes no matter what. I tried >> >>>> config xorg.conf with the correct HorizSync and VertRefresh, but it >> >>>> didn't even make any difference. >> >>>> >> >>> >> >>> Try booting into runlevel 3 and then >> >>> login as root and do system-config-display --reconfig. >> >>> >> >>> Bests >> >>> >> >>> JS >> >>> >> >>> >> >> Thanks, Jon. >> >> >> >> I did that yesterday already and no difference made. >> > >> > >> > When booting in to run level 3, log in as either a non privaliged >> > user, or as >> > root and running "startx", if X still crashes you should get some >> > output in the >> > terminal. >> > >> > Also look through the file /var/log/Xorg.0.log, as that will have some >> > more >> > information that may help us to help you. >> > >> > Doug >> > >> Doug, I pasted Xorg.0.log at the end of the first email I sent out. >> >> But, here is it again anyway: >> Xorg.0.log: >> > > My experience is that if X sends the wrong sync to a monitor, all that > happens is that the monitor shows a borked picture, or nothing at all > exept an error message. X doesn't crash... My expearience is slightly different. If X fails to start due to refresh rate issues, then it will fail to start, not "crash" just will stop trying to load. However this error seems to suggest that it did "crash". It could be due to a damaged hard disk in transit? Causing a problem with some of the libraries? -- Douglas Furlong ICQ: 7574077 "There are 10 kinds of people, those that understand binary, and those that do not" From dotancohen at gmail.com Mon Mar 7 18:17:28 2005 From: dotancohen at gmail.com (Dotan Cohen) Date: Mon, 7 Mar 2005 20:17:28 +0200 Subject: Leave it on or turn it off (Was: Is Linux really faster) In-Reply-To: <6.1.2.0.2.20050306140246.028b9918@mail1.wss.vip.scd.yahoo.com> References: <20050305184913.2B2B822800A@srv01.jemconsult.biz> <880dece005030511585eb713f6@mail.gmail.com> <422A1446.6050205@photo-miracles.com> <880dece005030515186fe6bd05@mail.gmail.com> <422A5264.3060403@photo-miracles.com> <880dece005030610477205fa7c@mail.gmail.com> <6.1.2.0.2.20050306140246.028b9918@mail1.wss.vip.scd.yahoo.com> Message-ID: <880dece005030710177b781d14@mail.gmail.com> > Now the hard part is getting Ety to like Linux. Proving to be not so hard- Now that IE is once again fubar in windows but winetools fires it up just fine! Dotan Cohen http://English-Lyrics.com http://Song-Lyriks.com http://LyricsList.com From bjiang_ee at yahoo.ca Mon Mar 7 19:39:45 2005 From: bjiang_ee at yahoo.ca (Benjamin Jiang) Date: Mon, 07 Mar 2005 14:39:45 -0500 Subject: X crashes when using a new monitor In-Reply-To: <20050307181510.v693q9w10di8c0kc@corrig.dark-hill.co.uk> References: <422C6753.2090300@yahoo.ca> <2ad7cea105030706461e1e280@mail.gmail.com> <422C6B07.4010501@yahoo.ca> <20050307153054.c2f3mb7npl8oog4o@corrig.dark-hill.co.uk> <422C75D2.7060604@yahoo.ca> <1110217916.3439.11.camel@localhost.localdomain> <20050307181510.v693q9w10di8c0kc@corrig.dark-hill.co.uk> Message-ID: <422CAE01.7050309@yahoo.ca> Douglas Furlong wrote: > ----- Message from kyrre at solution-forge.net --------- Date: Mon, 07 > Mar 2005 > 18:51:56 +0100 From: Kyrre Ness Sjobak > Reply-To: > Discussions about development for the Fedora desktop > Subject: Re: X crashes when using a new > monitor To: Discussions about development for the Fedora desktop > > >> man, 07.03.2005 kl. 16.40 skrev Benjamin Jiang: >> >>> Douglas Furlong wrote: >>> >>> > ----- Message from bjiang_ee at yahoo.ca --------- Date: Mon, 07 >>> Mar 2005 >>> > 09:53:59 -0500 From: Benjamin Jiang Reply-To: >>> > Discussions about development for the Fedora desktop >>> > Subject: Re: X crashes when using >>> a new >>> > monitor To: Jon Savage , >>> Discussions about >>> > development for the Fedora desktop >>> > >>> >> Jon Savage wrote: >>> >> >>> >>> On Mon, 07 Mar 2005 09:38:11 -0500, Benjamin Jiang >>> >>> wrote: >>> >>> >>> >>>> Hi, all, >>> >>>> >>> >>>> I installed a fresh copy of FC3 into my Dad's machine and >>> everything >>> >>>> worked fine. However, when I brought the machine to my Dad's >>> place and >>> >>>> plugged in his monitor (Acer 7154e), X crashes no matter what. >>> I tried >>> >>>> config xorg.conf with the correct HorizSync and VertRefresh, >>> but it >>> >>>> didn't even make any difference. >>> >>>> >>> >>> >>> >>> Try booting into runlevel 3 and then >>> >>> login as root and do system-config-display --reconfig. >>> >>> >>> >>> Bests >>> >>> >>> >>> JS >>> >>> >>> >>> >>> >> Thanks, Jon. >>> >> >>> >> I did that yesterday already and no difference made. >>> > >>> > >>> > When booting in to run level 3, log in as either a non privaliged >>> > user, or as >>> > root and running "startx", if X still crashes you should get some >>> > output in the >>> > terminal. >>> > >>> > Also look through the file /var/log/Xorg.0.log, as that will have >>> some >>> > more >>> > information that may help us to help you. >>> > >>> > Doug >>> > >>> Doug, I pasted Xorg.0.log at the end of the first email I sent out. >>> >>> But, here is it again anyway: >>> Xorg.0.log: >>> >> >> My experience is that if X sends the wrong sync to a monitor, all that >> happens is that the monitor shows a borked picture, or nothing at all >> exept an error message. X doesn't crash... > > > My expearience is slightly different. > > If X fails to start due to refresh rate issues, then it will fail to > start, not > "crash" just will stop trying to load. > > However this error seems to suggest that it did "crash". > > It could be due to a damaged hard disk in transit? Causing a problem > with some > of the libraries? > > Let me try to copy the whole /usr/X11R6 directory from a working FC3 machne then. Is that the only directory? Maybe /usr/lib/X11 as weel? Ben. From kyrre at solution-forge.net Mon Mar 7 19:51:06 2005 From: kyrre at solution-forge.net (Kyrre Ness Sjobak) Date: Mon, 07 Mar 2005 20:51:06 +0100 Subject: X crashes when using a new monitor In-Reply-To: <422CAE01.7050309@yahoo.ca> References: <422C6753.2090300@yahoo.ca> <2ad7cea105030706461e1e280@mail.gmail.com> <422C6B07.4010501@yahoo.ca> <20050307153054.c2f3mb7npl8oog4o@corrig.dark-hill.co.uk> <422C75D2.7060604@yahoo.ca> <1110217916.3439.11.camel@localhost.localdomain> <20050307181510.v693q9w10di8c0kc@corrig.dark-hill.co.uk> <422CAE01.7050309@yahoo.ca> Message-ID: <1110225065.3439.14.camel@localhost.localdomain> man, 07.03.2005 kl. 20.39 skrev Benjamin Jiang: > Douglas Furlong wrote: > > > ----- Message from kyrre at solution-forge.net --------- Date: Mon, 07 > > Mar 2005 > > 18:51:56 +0100 From: Kyrre Ness Sjobak > > Reply-To: > > Discussions about development for the Fedora desktop > > Subject: Re: X crashes when using a new > > monitor To: Discussions about development for the Fedora desktop > > > > > >> man, 07.03.2005 kl. 16.40 skrev Benjamin Jiang: > >> > >>> Douglas Furlong wrote: > >>> > >>> > ----- Message from bjiang_ee at yahoo.ca --------- Date: Mon, 07 > >>> Mar 2005 > >>> > 09:53:59 -0500 From: Benjamin Jiang Reply-To: > >>> > Discussions about development for the Fedora desktop > >>> > Subject: Re: X crashes when using > >>> a new > >>> > monitor To: Jon Savage , > >>> Discussions about > >>> > development for the Fedora desktop > >>> > > >>> >> Jon Savage wrote: > >>> >> > >>> >>> On Mon, 07 Mar 2005 09:38:11 -0500, Benjamin Jiang > >>> >>> wrote: > >>> >>> > >>> >>>> Hi, all, > >>> >>>> > >>> >>>> I installed a fresh copy of FC3 into my Dad's machine and > >>> everything > >>> >>>> worked fine. However, when I brought the machine to my Dad's > >>> place and > >>> >>>> plugged in his monitor (Acer 7154e), X crashes no matter what. > >>> I tried > >>> >>>> config xorg.conf with the correct HorizSync and VertRefresh, > >>> but it > >>> >>>> didn't even make any difference. > >>> >>>> > >>> >>> > >>> >>> Try booting into runlevel 3 and then > >>> >>> login as root and do system-config-display --reconfig. > >>> >>> > >>> >>> Bests > >>> >>> > >>> >>> JS > >>> >>> > >>> >>> > >>> >> Thanks, Jon. > >>> >> > >>> >> I did that yesterday already and no difference made. > >>> > > >>> > > >>> > When booting in to run level 3, log in as either a non privaliged > >>> > user, or as > >>> > root and running "startx", if X still crashes you should get some > >>> > output in the > >>> > terminal. > >>> > > >>> > Also look through the file /var/log/Xorg.0.log, as that will have > >>> some > >>> > more > >>> > information that may help us to help you. > >>> > > >>> > Doug > >>> > > >>> Doug, I pasted Xorg.0.log at the end of the first email I sent out. > >>> > >>> But, here is it again anyway: > >>> Xorg.0.log: > >>> > >> > >> My experience is that if X sends the wrong sync to a monitor, all that > >> happens is that the monitor shows a borked picture, or nothing at all > >> exept an error message. X doesn't crash... > > > > > > My expearience is slightly different. > > > > If X fails to start due to refresh rate issues, then it will fail to > > start, not > > "crash" just will stop trying to load. > > > > However this error seems to suggest that it did "crash". > > > > It could be due to a damaged hard disk in transit? Causing a problem > > with some > > of the libraries? > > > > > Let me try to copy the whole /usr/X11R6 directory from a working FC3 > machne then. Is that the only directory? Maybe /usr/lib/X11 as weel? > > Ben. Urk?!? If you are running slackware, go ahead. Since you are running fedora, i would probably more suggest to remove xorg by rpm and then reinstall it (maybe just use --nodeps when removing it, as you are going to plug it right back in again) from known good media From bjiang_ee at yahoo.ca Mon Mar 7 20:06:25 2005 From: bjiang_ee at yahoo.ca (Benjamin Jiang) Date: Mon, 07 Mar 2005 15:06:25 -0500 Subject: X crashes when using a new monitor In-Reply-To: <422CAE01.7050309@yahoo.ca> References: <422C6753.2090300@yahoo.ca> <2ad7cea105030706461e1e280@mail.gmail.com> <422C6B07.4010501@yahoo.ca> <20050307153054.c2f3mb7npl8oog4o@corrig.dark-hill.co.uk> <422C75D2.7060604@yahoo.ca> <1110217916.3439.11.camel@localhost.localdomain> <20050307181510.v693q9w10di8c0kc@corrig.dark-hill.co.uk> <422CAE01.7050309@yahoo.ca> Message-ID: <422CB441.9040901@yahoo.ca> Benjamin Jiang wrote: > Douglas Furlong wrote: > >> ----- Message from kyrre at solution-forge.net --------- Date: Mon, >> 07 Mar 2005 >> 18:51:56 +0100 From: Kyrre Ness Sjobak >> Reply-To: >> Discussions about development for the Fedora desktop >> Subject: Re: X crashes when using a new >> monitor To: Discussions about development for the Fedora desktop >> >> >>> man, 07.03.2005 kl. 16.40 skrev Benjamin Jiang: >>> >>>> Douglas Furlong wrote: >>>> >>>> > ----- Message from bjiang_ee at yahoo.ca --------- Date: Mon, 07 >>>> Mar 2005 >>>> > 09:53:59 -0500 From: Benjamin Jiang Reply-To: >>>> > Discussions about development for the Fedora desktop >>>> > Subject: Re: X crashes when >>>> using a new >>>> > monitor To: Jon Savage , >>>> Discussions about >>>> > development for the Fedora desktop >>>> > >>>> >> Jon Savage wrote: >>>> >> >>>> >>> On Mon, 07 Mar 2005 09:38:11 -0500, Benjamin Jiang >>>> >>> wrote: >>>> >>> >>>> >>>> Hi, all, >>>> >>>> >>>> >>>> I installed a fresh copy of FC3 into my Dad's machine and >>>> everything >>>> >>>> worked fine. However, when I brought the machine to my Dad's >>>> place and >>>> >>>> plugged in his monitor (Acer 7154e), X crashes no matter what. >>>> I tried >>>> >>>> config xorg.conf with the correct HorizSync and VertRefresh, >>>> but it >>>> >>>> didn't even make any difference. >>>> >>>> >>>> >>> >>>> >>> Try booting into runlevel 3 and then >>>> >>> login as root and do system-config-display --reconfig. >>>> >>> >>>> >>> Bests >>>> >>> >>>> >>> JS >>>> >>> >>>> >>> >>>> >> Thanks, Jon. >>>> >> >>>> >> I did that yesterday already and no difference made. >>>> > >>>> > >>>> > When booting in to run level 3, log in as either a non privaliged >>>> > user, or as >>>> > root and running "startx", if X still crashes you should get some >>>> > output in the >>>> > terminal. >>>> > >>>> > Also look through the file /var/log/Xorg.0.log, as that will have >>>> some >>>> > more >>>> > information that may help us to help you. >>>> > >>>> > Doug >>>> > >>>> Doug, I pasted Xorg.0.log at the end of the first email I sent out. >>>> >>>> But, here is it again anyway: >>>> Xorg.0.log: >>>> >>> >>> My experience is that if X sends the wrong sync to a monitor, all that >>> happens is that the monitor shows a borked picture, or nothing at all >>> exept an error message. X doesn't crash... >> >> >> >> My expearience is slightly different. >> >> If X fails to start due to refresh rate issues, then it will fail to >> start, not >> "crash" just will stop trying to load. >> >> However this error seems to suggest that it did "crash". >> >> It could be due to a damaged hard disk in transit? Causing a problem >> with some >> of the libraries? >> >> > Let me try to copy the whole /usr/X11R6 directory from a working FC3 > machne then. Is that the only directory? Maybe /usr/lib/X11 as weel? > > Ben. > It worked! I coped /usr/X11R6 directory from a working FC3 and it works now. Thanks Douglas! God, I feel stupid :-o. Ben. From kyrre at solution-forge.net Mon Mar 7 20:12:29 2005 From: kyrre at solution-forge.net (Kyrre Ness Sjobak) Date: Mon, 07 Mar 2005 21:12:29 +0100 Subject: X crashes when using a new monitor In-Reply-To: <422CB441.9040901@yahoo.ca> References: <422C6753.2090300@yahoo.ca> <2ad7cea105030706461e1e280@mail.gmail.com> <422C6B07.4010501@yahoo.ca> <20050307153054.c2f3mb7npl8oog4o@corrig.dark-hill.co.uk> <422C75D2.7060604@yahoo.ca> <1110217916.3439.11.camel@localhost.localdomain> <20050307181510.v693q9w10di8c0kc@corrig.dark-hill.co.uk> <422CAE01.7050309@yahoo.ca> <422CB441.9040901@yahoo.ca> Message-ID: <1110226349.3439.16.camel@localhost.localdomain> > It worked! I coped /usr/X11R6 directory from a working FC3 and it works > now. Thanks Douglas! 8-| I can't wait to se what happens when an xorg update is pushed... From beartooth at adelphia.net Tue Mar 8 16:19:31 2005 From: beartooth at adelphia.net (beartooth) Date: Tue, 08 Mar 2005 11:19:31 -0500 Subject: FC2 grub defaults to oldest kernel Message-ID: My past experience has been that grub automatically makes each new kernel the default boot; but on my FC2 machine the default is the oldest one. Is there a reason for this? Or should I fix it? And if so, how? -- Beartooth Implacable, Linux Evangelist & Gadfly neo-redneck, curmudgeonly codger with FC1&2, YDL4 Pine 4.62, Pan 0.14.2; Privoxy 3.0.1; Opera 7.54, Firefox 1.0 Bear in mind that I have little idea what I am talking about. From mattdm at mattdm.org Tue Mar 8 17:07:52 2005 From: mattdm at mattdm.org (Matthew Miller) Date: Tue, 8 Mar 2005 12:07:52 -0500 Subject: FC2 grub defaults to oldest kernel In-Reply-To: References: Message-ID: <20050308170752.GA5446@jadzia.bu.edu> On Tue, Mar 08, 2005 at 11:19:31AM -0500, beartooth wrote: > My past experience has been that grub automatically makes each new kernel > the default boot; but on my FC2 machine the default is the oldest one. Is > there a reason for this? Or should I fix it? And if so, how? This is addressed in FC3 -- look at /etc/sysconfig/kernel. -- Matthew Miller mattdm at mattdm.org Boston University Linux ------> From beartooth at adelphia.net Tue Mar 8 20:13:45 2005 From: beartooth at adelphia.net (beartooth) Date: Tue, 08 Mar 2005 15:13:45 -0500 Subject: FC2 grub defaults to oldest kernel References: <20050308170752.GA5446@jadzia.bu.edu> Message-ID: On Tue, 08 Mar 2005 12:07:52 -0500, Matthew Miller wrote: > On Tue, Mar 08, 2005 at 11:19:31AM -0500, beartooth wrote: >> My past experience has been that grub automatically makes each new kernel >> the default boot; but on my FC2 machine the default is the oldest one. Is >> there a reason for this? Or should I fix it? And if so, how? > > This is addressed in FC3 -- look at /etc/sysconfig/kernel. I tried FC3, weeks ago -- and didn't like it. Iirc that tale of woe was here; anyway, I'm not about to try again for another year or two. And during that time I'll stick to FC2 -- if not go back to FC1. So what should I do with FC2?? -- Beartooth Implacable, Linux Evangelist & Gadfly neo-redneck, curmudgeonly codger with FC1 & YDL 4.0 Pine 4.61, Pan 0.14.2; Privoxy 3.0.1; Opera 7.54, Firefox 1.0 Bear in mind that I have little idea what I am talking about. From MPage at ciri.com Tue Mar 8 20:53:39 2005 From: MPage at ciri.com (Matthew Page) Date: Tue, 8 Mar 2005 11:53:39 -0900 Subject: FC2 grub defaults to oldest kernel Message-ID: If you don't mind a little file editing, you can change the default in your /etc/grub.conf > -----Original Message----- > From: fedora-desktop-list-bounces at redhat.com [mailto:fedora-desktop-list- > bounces at redhat.com] On Behalf Of beartooth > Sent: Tuesday, March 08, 2005 11:14 AM > To: fedora-desktop-list at redhat.com > Subject: Re: FC2 grub defaults to oldest kernel > > On Tue, 08 Mar 2005 12:07:52 -0500, Matthew Miller wrote: > > > On Tue, Mar 08, 2005 at 11:19:31AM -0500, beartooth wrote: > >> My past experience has been that grub automatically makes each new > kernel > >> the default boot; but on my FC2 machine the default is the oldest one. > Is > >> there a reason for this? Or should I fix it? And if so, how? > > > > This is addressed in FC3 -- look at /etc/sysconfig/kernel. > > I tried FC3, weeks ago -- and didn't like it. Iirc that tale of woe was > here; anyway, I'm not about to try again for another year or two. And > during that time I'll stick to FC2 -- if not go back to FC1. So what > should I do with FC2?? > > -- > Beartooth Implacable, Linux Evangelist & Gadfly > neo-redneck, curmudgeonly codger with FC1 & YDL 4.0 > Pine 4.61, Pan 0.14.2; Privoxy 3.0.1; Opera 7.54, Firefox 1.0 > Bear in mind that I have little idea what I am talking about. > > > -- > Fedora-desktop-list mailing list > Fedora-desktop-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-desktop-list > > > BEGIN-ANTISPAM-VOTING-LINKS > ------------------------------------------------------ > Teach CanIt if this mail (ID 1934675) is spam: > Spam: > http://canit.ciri.com/canit/b.php?c=s&i=1934675&m=172ba00e46ce > Not spam: > http://canit.ciri.com/canit/b.php?c=n&i=1934675&m=172ba00e46ce > Forget vote: > http://canit.ciri.com/canit/b.php?c=f&i=1934675&m=172ba00e46ce > ------------------------------------------------------ > END-ANTISPAM-VOTING-LINKS From notting at redhat.com Wed Mar 9 03:29:51 2005 From: notting at redhat.com (Bill Nottingham) Date: Tue, 8 Mar 2005 22:29:51 -0500 Subject: locales in OpenOffice.org 2.0pre Message-ID: <20050309032951.GA19963@nostromo.devel.redhat.com> Currently we ship the following localizations in OOo 2.0pre that don't correspond to any glibc supported locale: - eo - kn-IN - ns - tn - zu Any reason to keep them? Bill From dcbw at redhat.com Wed Mar 9 04:54:37 2005 From: dcbw at redhat.com (Dan Williams) Date: Tue, 8 Mar 2005 23:54:37 -0500 (EST) Subject: locales in OpenOffice.org 2.0pre In-Reply-To: <20050309032951.GA19963@nostromo.devel.redhat.com> References: <20050309032951.GA19963@nostromo.devel.redhat.com> Message-ID: On Tue, 8 Mar 2005, Bill Nottingham wrote: > Currently we ship the following localizations in OOo 2.0pre that > don't correspond to any glibc supported locale: > > - eo > - kn-IN > - ns > - tn > - zu > > Any reason to keep them? Well, what's the equivalent locale in glibc? And if its not supported in glibc, why isn't it supported there? In any case, yes, we should probably drop them. Dan From notting at redhat.com Wed Mar 9 06:37:42 2005 From: notting at redhat.com (Bill Nottingham) Date: Wed, 9 Mar 2005 01:37:42 -0500 Subject: locales in OpenOffice.org 2.0pre In-Reply-To: References: <20050309032951.GA19963@nostromo.devel.redhat.com> Message-ID: <20050309063742.GA12187@nostromo.devel.redhat.com> Dan Williams (dcbw at redhat.com) said: > > Currently we ship the following localizations in OOo 2.0pre that > > don't correspond to any glibc supported locale: > > > > - eo > > - kn-IN > > - ns > > - tn > > - zu > > > > Any reason to keep them? > > Well, what's the equivalent locale in glibc? Not sure; I'd presume they'd map to the same locale name, if they existed in glibc. Note that the package description is generic enough to not really tell you what the locale *is* that they support. :) Bill From caolanm at redhat.com Wed Mar 9 08:53:53 2005 From: caolanm at redhat.com (Caolan McNamara) Date: Wed, 09 Mar 2005 08:53:53 +0000 Subject: locales in OpenOffice.org 2.0pre In-Reply-To: <20050309063742.GA12187@nostromo.devel.redhat.com> References: <20050309032951.GA19963@nostromo.devel.redhat.com> <20050309063742.GA12187@nostromo.devel.redhat.com> Message-ID: <1110358433.10051.9.camel@sheol.homelinux.org> On Wed, 2005-03-09 at 01:37 -0500, Bill Nottingham wrote: > Dan Williams (dcbw at redhat.com) said: > > > Currently we ship the following localizations in OOo 2.0pre that > > > don't correspond to any glibc supported locale: > > > > > > - eo esperanto, ok I guess I can drop this one :-) > > > - ns > > > - tn sepedi and tswana, south african languages, if the rest of fedora doesn't support them I guess it makes sense to drop them. > > > - zu > > > - kn-IN zu -> glibc zu_ZA south african zulu, and kn_IN -> glibc kn_IN indian kannada, locale -a shows these two so we'll hold onto them I reckon. > > > > > > Any reason to keep them? > > > > Well, what's the equivalent locale in glibc? > > Not sure; I'd presume they'd map to the same locale name, if they > existed in glibc. Note that the package description is generic enough > to not really tell you what the locale *is* that they support. :) The fact the langpacks worked at all overwhelmed me :-), I'll look into changing the langpack names to match the glibc locale and adding descriptions for what languages they provide. list of language names from OOo's perspective http://go-ooo.org/lxr/source/util/tools/source/intntl/isolang.cxx#248 C. From caolanm at redhat.com Wed Mar 9 09:31:42 2005 From: caolanm at redhat.com (Caolan McNamara) Date: Wed, 09 Mar 2005 09:31:42 +0000 Subject: locales in OpenOffice.org 2.0pre In-Reply-To: <1110358433.10051.9.camel@sheol.homelinux.org> References: <20050309032951.GA19963@nostromo.devel.redhat.com> <20050309063742.GA12187@nostromo.devel.redhat.com> <1110358433.10051.9.camel@sheol.homelinux.org> Message-ID: <1110360702.10071.24.camel@sheol.homelinux.org> On Wed, 2005-03-09 at 08:53 +0000, Caolan McNamara wrote: > On Wed, 2005-03-09 at 01:37 -0500, Bill Nottingham wrote: > > Dan Williams (dcbw at redhat.com) said: > > > > Currently we ship the following localizations in OOo 2.0pre that > > > > don't correspond to any glibc supported locale: > > > > > > > > - eo > > esperanto, ok I guess I can drop this one :-) hmm, there is no langpack-eo, perhaps typo for langpack-eu, which is basque -> e.g. glibc eu_ES C. From otaylor at redhat.com Wed Mar 9 13:23:58 2005 From: otaylor at redhat.com (Owen Taylor) Date: Wed, 09 Mar 2005 08:23:58 -0500 Subject: locales in OpenOffice.org 2.0pre In-Reply-To: <1110358433.10051.9.camel@sheol.homelinux.org> References: <20050309032951.GA19963@nostromo.devel.redhat.com> <20050309063742.GA12187@nostromo.devel.redhat.com> <1110358433.10051.9.camel@sheol.homelinux.org> Message-ID: <422EF8EE.2060300@redhat.com> Caolan McNamara wrote: >>>>- ns >>>>- tn > > > sepedi and tswana, south african languages, if the rest of fedora > doesn't support them I guess it makes sense to drop them. 'ns' isn't a registered iso 639-1 language code to my knowledge. Looks like Sepedi is another name for Northern Sotho - http://www.ethnologue.com/show_language.asp?code=SRT, which is iso 639-2 "nso". (There is a GTK+ translation for nso) Regards, Owen From dcbw at redhat.com Wed Mar 9 15:32:08 2005 From: dcbw at redhat.com (Dan Williams) Date: Wed, 09 Mar 2005 10:32:08 -0500 Subject: locales in OpenOffice.org 2.0pre In-Reply-To: <422EF8EE.2060300@redhat.com> References: <20050309032951.GA19963@nostromo.devel.redhat.com> <20050309063742.GA12187@nostromo.devel.redhat.com> <1110358433.10051.9.camel@sheol.homelinux.org> <422EF8EE.2060300@redhat.com> Message-ID: <1110382328.1589.6.camel@dcbw.boston.redhat.com> On Wed, 2005-03-09 at 08:23 -0500, Owen Taylor wrote: > Caolan McNamara wrote: > > >>>>- ns > >>>>- tn > > > > > > sepedi and tswana, south african languages, if the rest of fedora > > doesn't support them I guess it makes sense to drop them. > > 'ns' isn't a registered iso 639-1 language code to my knowledge. > > Looks like Sepedi is another name for Northern Sotho - > http://www.ethnologue.com/show_language.asp?code=SRT, which is > iso 639-2 "nso". (There is a GTK+ translation for nso) AFAIK, OOo does not use 3-letter language codes... Dan From notting at redhat.com Wed Mar 9 15:57:48 2005 From: notting at redhat.com (Bill Nottingham) Date: Wed, 9 Mar 2005 10:57:48 -0500 Subject: locales in OpenOffice.org 2.0pre In-Reply-To: <1110360702.10071.24.camel@sheol.homelinux.org> References: <20050309032951.GA19963@nostromo.devel.redhat.com> <20050309063742.GA12187@nostromo.devel.redhat.com> <1110358433.10051.9.camel@sheol.homelinux.org> <1110360702.10071.24.camel@sheol.homelinux.org> Message-ID: <20050309155748.GA19846@nostromo.devel.redhat.com> Caolan McNamara (caolanm at redhat.com) said: > On Wed, 2005-03-09 at 08:53 +0000, Caolan McNamara wrote: > > On Wed, 2005-03-09 at 01:37 -0500, Bill Nottingham wrote: > > > Dan Williams (dcbw at redhat.com) said: > > > > > Currently we ship the following localizations in OOo 2.0pre that > > > > > don't correspond to any glibc supported locale: > > > > > > > > > > - eo > > > > esperanto, ok I guess I can drop this one :-) > > hmm, there is no langpack-eo, openoffice.org-langpack-eo-1.9.82-1.i386.rpm eu is already covered, and is in the comps file now. Bill From beartooth at adelphia.net Wed Mar 9 16:55:38 2005 From: beartooth at adelphia.net (beartooth) Date: Wed, 09 Mar 2005 11:55:38 -0500 Subject: FC2 grub defaults to oldest kernel References: Message-ID: On Tue, 08 Mar 2005 11:53:39 -0900, Matthew Page wrote: > If you don't mind a little file editing, you can change the default in > your /etc/grub.conf >> Is there a reason for this? Or should I fix it? And if so, how? OK, the first line not commented out says "default=2" Does that mean it will always be the second one down the list of however many, or something else? Can I simply change the 2 to a 1? -- Beartooth Implacable, Linux Evangelist & Gadfly neo-redneck, curmudgeonly codger with FC1 & YDL 4.0 Pine 4.61, Pan 0.14.2; Privoxy 3.0.1; Opera 7.54, Firefox 1.0 Bear in mind that I have little idea what I am talking about. From breun at xs4all.nl Wed Mar 9 17:07:26 2005 From: breun at xs4all.nl (Nils Breunese) Date: Wed, 09 Mar 2005 18:07:26 +0100 Subject: FC2 grub defaults to oldest kernel In-Reply-To: References: Message-ID: <1110388046.7054.7.camel@breuniac> > > If you don't mind a little file editing, you can change the default in > > your /etc/grub.conf > > >> Is there a reason for this? Or should I fix it? And if so, how? > > OK, the first line not commented out says "default=2" Does that mean it > will always be the second one down the list of however many, or something > else? Can I simply change the 2 to a 1? It means it will always be the third down the list of however many. The count starts at 0. Nils. From kyrre at solution-forge.net Wed Mar 9 17:50:05 2005 From: kyrre at solution-forge.net (Kyrre Ness Sjobak) Date: Wed, 09 Mar 2005 18:50:05 +0100 Subject: locales in OpenOffice.org 2.0pre In-Reply-To: <20050309155748.GA19846@nostromo.devel.redhat.com> References: <20050309032951.GA19963@nostromo.devel.redhat.com> <20050309063742.GA12187@nostromo.devel.redhat.com> <1110358433.10051.9.camel@sheol.homelinux.org> <1110360702.10071.24.camel@sheol.homelinux.org> <20050309155748.GA19846@nostromo.devel.redhat.com> Message-ID: <1110390604.3448.10.camel@localhost.localdomain> ons, 09.03.2005 kl. 16.57 skrev Bill Nottingham: > Caolan McNamara (caolanm at redhat.com) said: > > On Wed, 2005-03-09 at 08:53 +0000, Caolan McNamara wrote: > > > On Wed, 2005-03-09 at 01:37 -0500, Bill Nottingham wrote: > > > > Dan Williams (dcbw at redhat.com) said: > > > > > > Currently we ship the following localizations in OOo 2.0pre that > > > > > > don't correspond to any glibc supported locale: > > > > > > > > > > > > - eo > > > > > > esperanto, ok I guess I can drop this one :-) > > > > hmm, there is no langpack-eo, > > openoffice.org-langpack-eo-1.9.82-1.i386.rpm Whoho! Langpack's are actually *comming*! Great! From fsmith at web-links.net Wed Mar 9 21:08:43 2005 From: fsmith at web-links.net (Frank smith) Date: Wed, 09 Mar 2005 21:08:43 +0000 Subject: locales in OpenOffice.org 2.0pre In-Reply-To: <1110390604.3448.10.camel@localhost.localdomain> References: <20050309032951.GA19963@nostromo.devel.redhat.com> <20050309063742.GA12187@nostromo.devel.redhat.com> <1110358433.10051.9.camel@sheol.homelinux.org> <1110360702.10071.24.camel@sheol.homelinux.org> <20050309155748.GA19846@nostromo.devel.redhat.com> <1110390604.3448.10.camel@localhost.localdomain> Message-ID: <1110402524.7979.3.camel@bear.rokpa> HI Just downloaded OO2 beta and its looking good on my FC 3 Gnome box at the moment, and it's running fine on this. Well done to all Bob On Wed, 2005-03-09 at 18:50 +0100, Kyrre Ness Sjobak wrote: > ons, 09.03.2005 kl. 16.57 skrev Bill Nottingham: > > Caolan McNamara (caolanm at redhat.com) said: > > > On Wed, 2005-03-09 at 08:53 +0000, Caolan McNamara wrote: > > > > On Wed, 2005-03-09 at 01:37 -0500, Bill Nottingham wrote: > > > > > Dan Williams (dcbw at redhat.com) said: > > > > > > > Currently we ship the following localizations in OOo 2.0pre that > > > > > > > don't correspond to any glibc supported locale: > > > > > > > > > > > > > > - eo > > > > > > > > esperanto, ok I guess I can drop this one :-) > > > > > > hmm, there is no langpack-eo, > > > > openoffice.org-langpack-eo-1.9.82-1.i386.rpm > > Whoho! Langpack's are actually *comming*! Great! > From gmureddu at prodigy.net.mx Thu Mar 10 22:06:27 2005 From: gmureddu at prodigy.net.mx (Gain Paolo Mureddu) Date: Thu, 10 Mar 2005 16:06:27 -0600 Subject: Some more OOo 2 questions. Message-ID: <4230C4E3.4040409@prodigy.net.mx> I was following the OOo 2's locale and language packs discussion, however I may lack some background here... And hence I have some questions: 1.- Are the Fedora folks involved in any way on OOo 2 development? 2.- Is there a test build for Fedora or something? Or the only way to get OOo 2 Beta is from the project's official site only? 2bis.- In the event you get the packages from openoffice.org's site, will installing them remove/overwrite OOo 1.1.3? 3.- Once OOo 2 is released, most probably Core 4 will include it, but will be also made available for previous versions of Fedora by means of the Extras repository? (this would actually be cool!) Thanks y'all! From dcbw at redhat.com Wed Mar 9 22:36:31 2005 From: dcbw at redhat.com (Dan Williams) Date: Wed, 09 Mar 2005 17:36:31 -0500 Subject: Some more OOo 2 questions. In-Reply-To: <4230C4E3.4040409@prodigy.net.mx> References: <4230C4E3.4040409@prodigy.net.mx> Message-ID: <1110407791.1589.20.camel@dcbw.boston.redhat.com> On Thu, 2005-03-10 at 16:06 -0600, Gain Paolo Mureddu wrote: > I was following the OOo 2's locale and language packs discussion, > however I may lack some background here... And hence I have some questions: > > 1.- Are the Fedora folks involved in any way on OOo 2 development? Caolan and I work on OOo for Red Hat. We both have a fairly long history with the OOo project, Caolan longer than I. We've both contributed code to the project. > 2.- Is there a test build for Fedora or something? Or the only way to > get OOo 2 Beta is from the project's official site only? Test RPMs are in Rawhide. > 2bis.- In the event you get the packages from openoffice.org's site, > will installing them remove/overwrite OOo 1.1.3? They should not. > 3.- Once OOo 2 is released, most probably Core 4 will include it, but > will be also made available for previous versions of Fedora by means of > the Extras repository? (this would actually be cool!) Most likely not, since the build process uses a lot of the gcj/gij stuff, which only got up to speed with GCC 4.0, which will not be released for FC3. Dan From dchipman at ican.net Thu Mar 10 05:34:36 2005 From: dchipman at ican.net (David C. Chipman) Date: Thu, 10 Mar 2005 00:34:36 -0500 Subject: Fedora Core 4 ETA Message-ID: <1110432876.21187.15.camel@david.chipman> Hi all, Any idea on when FC4 will be available for download? The mention of OOo 2 being provided in it (among the other additions that were related OOo 2) make it sound great. What version of GNOME will be included. (URL can be considered a suitable answer to these questions...) Thanks! -David Chipman -- David C. Chipman From skvidal at phy.duke.edu Thu Mar 10 05:46:41 2005 From: skvidal at phy.duke.edu (seth vidal) Date: Thu, 10 Mar 2005 00:46:41 -0500 Subject: Fedora Core 4 ETA In-Reply-To: <1110432876.21187.15.camel@david.chipman> References: <1110432876.21187.15.camel@david.chipman> Message-ID: <1110433601.31871.97.camel@cutter> On Thu, 2005-03-10 at 00:34 -0500, David C. Chipman wrote: > Hi all, > > Any idea on when FC4 will be available for download? The mention of > OOo 2 being provided in it (among the other additions that were related > OOo 2) make it sound great. What version of GNOME will be included. > (URL can be considered a suitable answer to these questions...) Thanks! http://fedora.redhat.com/participate/schedule/ -sv From dchipman at ican.net Thu Mar 10 05:49:06 2005 From: dchipman at ican.net (David C. Chipman) Date: Thu, 10 Mar 2005 00:49:06 -0500 Subject: Fedora Core 4 ETA In-Reply-To: <1110433601.31871.97.camel@cutter> References: <1110432876.21187.15.camel@david.chipman> <1110433601.31871.97.camel@cutter> Message-ID: <1110433746.21187.18.camel@david.chipman> Hi Seth, I want to thank you for the quick response (kicks self, "BASH HEAD HERE", etc.) -David Chipman On Thu, 2005-10-03 at 00:46 -0500, seth vidal wrote: > On Thu, 2005-03-10 at 00:34 -0500, David C. Chipman wrote: > > Hi all, > > > > Any idea on when FC4 will be available for download? The mention of > > OOo 2 being provided in it (among the other additions that were related > > OOo 2) make it sound great. What version of GNOME will be included. > > (URL can be considered a suitable answer to these questions...) Thanks! > > http://fedora.redhat.com/participate/schedule/ > > -sv > > -- David C. Chipman From gmureddu at prodigy.net.mx Fri Mar 11 07:26:22 2005 From: gmureddu at prodigy.net.mx (Gain Paolo Mureddu) Date: Fri, 11 Mar 2005 01:26:22 -0600 Subject: Fedora Core 4 ETA In-Reply-To: <1110432876.21187.15.camel@david.chipman> References: <1110432876.21187.15.camel@david.chipman> Message-ID: <4231481E.5020109@prodigy.net.mx> David C. Chipman wrote: > Hi all, > > Any idea on when FC4 will be available for download? The mention of >OOo 2 being provided in it (among the other additions that were related >OOo 2) make it sound great. What version of GNOME will be included. >(URL can be considered a suitable answer to these questions...) Thanks! > > -David Chipman > > I think some other interesting questions would be in order: 1) From the desktop stand point, what advancements have there been made in regards to things like udev. We all know udev in FC3 works, but sometimes fails silently and wthout any warning whatsoever to the user on what's going on. I'm sure this has been worked on for Core 4, but how has it been addressed? 2) Though I'm pretty sure it is safe to assume the latest and greatest of environments will ship with it (Xorg 6.8.2, GNOME 2.10, KDE 3.4.x), from a desktop experience stand point, what can we expect? What about eyecandy by means of extensions like Composite, RENDER, Fixes, damages, et al, will Core 4 feature a way to enable/disable these, or is this dependent on the environment used? What about multimedia capabilities? (I can alsmost forsee it will include ALSA at the very least 1.0.9, if not 1.1.0 [or 1.0.10] is made available by then) 3) As it has been hinted, we can expect OOo 2.0 to be boundled with it, does this means Core 2 will feature a JVM with it? If so, which? From richardl at redhat.com Thu Mar 10 13:55:46 2005 From: richardl at redhat.com (Richard Li) Date: Thu, 10 Mar 2005 08:55:46 -0500 Subject: Fedora Core 4 ETA In-Reply-To: <4231481E.5020109@prodigy.net.mx> References: <1110432876.21187.15.camel@david.chipman> <4231481E.5020109@prodigy.net.mx> Message-ID: <423051E2.2060607@redhat.com> > 3) As it has been hinted, we can expect OOo 2.0 to be boundled with > it, does this means Core 2 will feature a JVM with it? If so, which? OOo 2.0 will be built by gcj, which is FOSS. For more information, search the archives. (I'm also assuming you mean Core 4, not Core 2.) From beartooth at adelphia.net Thu Mar 10 20:14:39 2005 From: beartooth at adelphia.net (beartooth) Date: Thu, 10 Mar 2005 15:14:39 -0500 Subject: FC2 grub defaults to oldest kernel References: <1110388046.7054.7.camel@breuniac> Message-ID: On Wed, 09 Mar 2005 18:07:26 +0100, Nils Breunese wrote: >> > If you don't mind a little file editing, you can change the default in >> > your /etc/grub.conf >> >> OK, the first line not commented out says "default=2" Does that mean it >> will always be the second one down the list of however many, or something >> else? Can I simply change the 2 to a 1? > > It means it will always be the third down the list of however many. The > count starts at 0. Aha. I couldn't tell whether it was a sneakin' hunch or a faint memory, but I had a distinct intimation of some sort of lurking gotcha there somewhere. So if I want FC2 to behave as I'm accustomed to things redhat doing, I should just change the 2 to a zero -- right? That's it? -- Beartooth Implacable, Linux Evangelist & Gadfly neo-redneck, curmudgeonly codger with FC1&2, YDL4 Pine 4.62, Pan 0.14.2; Privoxy 3.0.1; Opera 7.54, Firefox 1.0 Bear in mind that I have little idea what I am talking about. From MPage at ciri.com Thu Mar 10 20:27:54 2005 From: MPage at ciri.com (Matthew Page) Date: Thu, 10 Mar 2005 11:27:54 -0900 Subject: FC2 grub defaults to oldest kernel Message-ID: That all depends... If the kernel you want to run is listed first, then the answer to your question is yes. > -----Original Message----- > From: fedora-desktop-list-bounces at redhat.com [mailto:fedora-desktop-list- > bounces at redhat.com] On Behalf Of beartooth > Sent: Thursday, March 10, 2005 11:15 AM > To: fedora-desktop-list at redhat.com > Subject: Re: FC2 grub defaults to oldest kernel > > On Wed, 09 Mar 2005 18:07:26 +0100, Nils Breunese wrote: > > >> > If you don't mind a little file editing, you can change the default > in > >> > your /etc/grub.conf > >> > >> OK, the first line not commented out says "default=2" Does that mean it > >> will always be the second one down the list of however many, or > something > >> else? Can I simply change the 2 to a 1? > > > > It means it will always be the third down the list of however many. The > > count starts at 0. > > Aha. I couldn't tell whether it was a sneakin' hunch or a faint memory, > but I had a distinct intimation of some sort of lurking gotcha there > somewhere. So if I want FC2 to behave as I'm accustomed to things redhat > doing, I should just change the 2 to a zero -- right? That's it? > > -- > Beartooth Implacable, Linux Evangelist & Gadfly > neo-redneck, curmudgeonly codger with FC1&2, YDL4 > Pine 4.62, Pan 0.14.2; Privoxy 3.0.1; Opera 7.54, Firefox 1.0 > Bear in mind that I have little idea what I am talking about. > > > -- > Fedora-desktop-list mailing list > Fedora-desktop-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-desktop-list > > > BEGIN-ANTISPAM-VOTING-LINKS > ------------------------------------------------------ > Teach CanIt if this mail (ID 1945175) is spam: > Spam: > http://canit.ciri.com/canit/b.php?c=s&i=1945175&m=f59a2571da95 > Not spam: > http://canit.ciri.com/canit/b.php?c=n&i=1945175&m=f59a2571da95 > Forget vote: > http://canit.ciri.com/canit/b.php?c=f&i=1945175&m=f59a2571da95 > ------------------------------------------------------ > END-ANTISPAM-VOTING-LINKS From dotancohen at gmail.com Thu Mar 10 22:35:22 2005 From: dotancohen at gmail.com (Dotan Cohen) Date: Fri, 11 Mar 2005 00:35:22 +0200 Subject: startup screen with keyboard. Message-ID: <880dece0050310143575bee7dc@mail.gmail.com> Hi all, I sometimes have problems when I switch computers on my KVM: the mouse stops working in Fedora when I switch back to Fedora. A reset fixes it- so I know that the KVM and the cables are ok. How can I 'restart' the mouse without rebooting? Thanks! Dotan Cohen http://English-Lyrics.com http://Song-Lyriks.com From jdennis at redhat.com Thu Mar 10 23:03:01 2005 From: jdennis at redhat.com (John Dennis) Date: Thu, 10 Mar 2005 18:03:01 -0500 Subject: startup screen with keyboard. In-Reply-To: <880dece0050310143575bee7dc@mail.gmail.com> References: <880dece0050310143575bee7dc@mail.gmail.com> Message-ID: <1110495781.25869.79.camel@finch.boston.redhat.com> On Fri, 2005-03-11 at 00:35 +0200, Dotan Cohen wrote: > Hi all, > > I sometimes have problems when I switch computers on my KVM: the mouse > stops working in Fedora when I switch back to Fedora. A reset fixes > it- so I know that the KVM and the cables are ok. How can I 'restart' > the mouse without rebooting? Thanks! Sadly there have been many reports of mouse problems with recent Fedora releases when connected via a KVM (I know, I have the problem too :-) Some of the bug reports are: 132471, 150746, 139188, 111161 and numerous duplicates. I would encourage you to file another bug report, the more heat, the more attention. BTW, the problem usually manifests itself when switching between hosts, it can usually be corrected (as I think you observed) by resetting X (e.g. switch to a console, switch back to X, but not always, sometimes you have reboot or start X without switching away), and it seems to be especially prevalent with Belkin KVM's (just my observation from listening to the reports) -- John Dennis From wralphie at comcast.net Thu Mar 10 23:19:10 2005 From: wralphie at comcast.net (jludwig) Date: Thu, 10 Mar 2005 18:19:10 -0500 Subject: startup screen with keyboard. In-Reply-To: <880dece0050310143575bee7dc@mail.gmail.com> References: <880dece0050310143575bee7dc@mail.gmail.com> Message-ID: <200503101819.10740.wralphie@comcast.net> On Thursday 10 March 2005 05:35 pm, Dotan Cohen wrote: > Hi all, > > I sometimes have problems when I switch computers on my KVM: the mouse > stops working in Fedora when I switch back to Fedora. A reset fixes > it- so I know that the KVM and the cables are ok. How can I 'restart' > the mouse without rebooting? Thanks! > > Dotan Cohen > http://English-Lyrics.com > http://Song-Lyriks.com The error I have seen on many machines regardless of the operating system that is being used. I suspect it has to do with the hardware/firmware associated with certian motherboards. You should be able to reinitialize the mouse port by reinitializing the mouse driver/module. (Its gpm for terminals and ??? for X. -- John H Ludwig From dotancohen at gmail.com Fri Mar 11 01:09:09 2005 From: dotancohen at gmail.com (Dotan Cohen) Date: Fri, 11 Mar 2005 03:09:09 +0200 Subject: Being denied my own files! Message-ID: <880dece0050310170924a20694@mail.gmail.com> When trying to delete a file in my /home/dotancohen directory (and logged in as dotancohen) I get: Access denied to /home/dotancohen/ankush.jpg. In rightClick-> Properties-> Permissions I saw that Owner can read and write, Group can read, and Others can read. So I changed the permissions so that all the groups say read & write, but still I cannot delete the file. No other application is accessing the file. I'm using Konqueror in KDE on FC3. Thanks in advance. Dotan Cohen http://English-Lyrics.com http://Song-Lyriks.com From marc.miller at amd.com Fri Mar 11 01:12:51 2005 From: marc.miller at amd.com (Miller, Marc) Date: Thu, 10 Mar 2005 17:12:51 -0800 Subject: Being denied my own files! Message-ID: In order to delete the file, you must: * have write access to the file * have write access to the directory * the sTicky bit (chmod +t) must not be set on the directory (sTicky is rare) -----Original Message----- From: fedora-desktop-list-bounces at redhat.com [mailto:fedora-desktop-list-bounces at redhat.com] On Behalf Of Dotan Cohen Sent: Thursday, March 10, 2005 5:09 PM To: fedora-desktop-list at redhat.com Subject: Being denied my own files! When trying to delete a file in my /home/dotancohen directory (and logged in as dotancohen) I get: Access denied to /home/dotancohen/ankush.jpg. In rightClick-> Properties-> Permissions I saw that Owner can read and write, Group can read, and Others can read. So I changed the permissions so that all the groups say read & write, but still I cannot delete the file. No other application is accessing the file. I'm using Konqueror in KDE on FC3. Thanks in advance. Dotan Cohen http://English-Lyrics.com http://Song-Lyriks.com -- Fedora-desktop-list mailing list Fedora-desktop-list at redhat.com http://www.redhat.com/mailman/listinfo/fedora-desktop-list From gmureddu at prodigy.net.mx Sat Mar 12 04:35:56 2005 From: gmureddu at prodigy.net.mx (Gain Paolo Mureddu) Date: Fri, 11 Mar 2005 22:35:56 -0600 Subject: Fedora Core 4 ETA In-Reply-To: <423051E2.2060607@redhat.com> References: <1110432876.21187.15.camel@david.chipman> Message-ID: <423271AC.3020507@prodigy.net.mx> Richard Li wrote: > >> 3) As it has been hinted, we can expect OOo 2.0 to be boundled with >> it, does this means Core 2 will feature a JVM with it? If so, which? > > > OOo 2.0 will be built by gcj, which is FOSS. For more information, > search the archives. > > (I'm also assuming you mean Core 4, not Core 2.) > Yeah, sorry... My mistake. I meant Core 4... From nphilipp at redhat.com Fri Mar 11 10:20:44 2005 From: nphilipp at redhat.com (Nils Philippsen) Date: Fri, 11 Mar 2005 11:20:44 +0100 Subject: [OT] RE: Being denied my own files! In-Reply-To: References: Message-ID: <1110536444.32403.4.camel@wombat.tiptoe.de> Besides being off-topic (fedora-list would be on-topic for this question), ... On Thu, 2005-03-10 at 17:12 -0800, Miller, Marc wrote: > In order to delete the file, you must: > * have write access to the file no. I can delete root-owned files in my directories even if I don't have any rights on the files themselves. > * have write access to the directory > * the sTicky bit (chmod +t) must not be set on the directory (sTicky is > rare) No. The sticky bit on a directory specifies that contrary to the above only file owners can delete their files, handy for world-writable directories like /tmp and /dev/shm. Nils -- Nils Philippsen / Red Hat / nphilipp at redhat.com "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- B. Franklin, 1759 PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011 From mgoodhew at gmail.com Fri Mar 11 13:23:23 2005 From: mgoodhew at gmail.com (Miles Goodhew) Date: Sat, 12 Mar 2005 00:23:23 +1100 Subject: [OT] RE: Being denied my own files! In-Reply-To: <1110536444.32403.4.camel@wombat.tiptoe.de> References: <1110536444.32403.4.camel@wombat.tiptoe.de> Message-ID: <3514a21050311052310af86e1@mail.gmail.com> Hi, The magic of Unix inodes: No user can _actually_ delete a file (Not even root)! However, If a user can write to a directory (and root can write to any local directory not on a read-only filesystem), then that user can delete the link to the file (i.e. delete the file's name from the directory). If a file's link count (= number of directories the file has a name in) and the number of references (= number of open file descriptors for the file) both go to zero, then the system deallocates the files data blocks and makes the file's inode (which is the unique head of a file) reusable for new files. Exercise: % echo "This is the first file" >file1 % ln file1 file2 # Do _not_ put a "-s" here! % ls -li file? The inode number is the first column - file1 and file2 have the same inode -> they're the same file (just two different names for it - the inode and all data blocks on disk ate the same thing). The link count is the column after the mode bits - it's has the value 2 indicating that the file has two names. % rm file1 % cat file2 Hmm, look familiar? Bonus brainteasers: * How many links does "/" have? Why? What are ".." and "."? * What's a symbolic link. * What do "chmod g+s" and "chmod u+s" do to files/directories (This can be fun on Sunos!) Moles. -- Miles Goodhew, Senior Hacker TransACT communications From nman64 at n-man.com Fri Mar 11 17:08:10 2005 From: nman64 at n-man.com (Patrick Barnes) Date: Fri, 11 Mar 2005 11:08:10 -0600 Subject: Being denied my own files! In-Reply-To: <880dece0050310170924a20694@mail.gmail.com> References: <880dece0050310170924a20694@mail.gmail.com> Message-ID: <4231D07A.7030504@n-man.com> If you still haven't been able to delete the file, there are a few other things you should check for. First, make sure the filesystem is writable. Use the mount command with no arguments and look for (rw) at the end of the listing for whatever partition contains the file. Second, check the extended attributes of the file. Run lsattr on the file and make sure it is not immutable (the 'i' flag) and use chattr to correct it if it is. Third, make sure that SELinux is not blocking the access. Try to erase the file, then (as root) run tail /var/log/messages and look for errors. Finally, double check both the permissions and the ownership of both the file and containing directory. You don't want to spend all day bashing your head over something simple. If you are having access problems in your home directory, you'd better double check everything in it for broken permissions and attributes. Faulty permissions can result in some nasty surprises. From kyrre at solution-forge.net Fri Mar 11 20:09:28 2005 From: kyrre at solution-forge.net (Kyrre Ness Sjobak) Date: Fri, 11 Mar 2005 21:09:28 +0100 Subject: [OT] RE: Being denied my own files! In-Reply-To: <1110536444.32403.4.camel@wombat.tiptoe.de> References: <1110536444.32403.4.camel@wombat.tiptoe.de> Message-ID: <1110571768.5618.2.camel@localhost.localdomain> > no. I can delete root-owned files in my directories even if I don't have > any rights on the files themselves. Strange. I have experienced several times to delete something root-owned (in my home folder) from nautilus -> get thrown to ~/.Trash. (or media/trash, but removable media is usually vfat so permissions isn't an issue) When i then try to empty trash, all i get is "acess denied". From beartooth at adelphia.net Fri Mar 11 21:19:31 2005 From: beartooth at adelphia.net (beartooth) Date: Fri, 11 Mar 2005 16:19:31 -0500 Subject: FC2 grub defaults to oldest kernel References: Message-ID: On Thu, 10 Mar 2005 11:27:54 -0900, Matthew Page wrote: > > > The count starts at 0. >> > > Aha. I couldn't tell whether it was a sneakin' hunch or a faint > > memory, but I had a distinct intimation of some sort of lurking gotcha > > there somewhere. So if I want FC2 to behave as I'm accustomed to > > things redhat doing, I should just change the 2 to a zero -- right? > > That's it? > That all depends... If the kernel you want to run is listed first, then > the answer to your question is yes. It sure looks like it: they're in decreasing numerical order. I'll try it. Many thanks! -- Beartooth Implacable, Linux Evangelist & Gadfly neo-redneck, curmudgeonly codger with FC1&2, YDL4 Pine 4.62, Pan 0.14.2; Privoxy 3.0.1; Opera 7.54, Firefox 1.0 Bear in mind that I have little idea what I am talking about. From onave at shopzilla.com Sat Mar 12 07:07:16 2005 From: onave at shopzilla.com (Ofer Nave) Date: Fri, 11 Mar 2005 23:07:16 -0800 Subject: FC3 annoyances (blanking and blanking) Message-ID: <42329524.6060101@shopzilla.com> Hello! I'm new to Fedora... just installed FC3. There are two annoyances that I haven't found a way around, and I was hoping to get help here. 1) I can't find a way to stop the screen from blanking after a while. I tried the screensaver settings, the power settings, and xset s off... nothing has worked so far. 2) I used to use SecureCRT to ssh into linux boxes for development, and when I used man or less, the last screen would remain visible after pressing 'q' to return to the prompt. Now that I'm using X, it disappears when I quit. I've tried xterm, konsole, and gnome term - all have the same behavior. Thanks! -ofer From kms at passback.co.uk Sat Mar 12 09:46:01 2005 From: kms at passback.co.uk (Keith Sharp) Date: Sat, 12 Mar 2005 09:46:01 +0000 Subject: FC3 annoyances (blanking and blanking) In-Reply-To: <42329524.6060101@shopzilla.com> References: <42329524.6060101@shopzilla.com> Message-ID: <1110620761.22897.26.camel@animal.passback.co.uk> On Fri, 2005-03-11 at 23:07 -0800, Ofer Nave wrote: > Hello! I'm new to Fedora... just installed FC3. There are two > annoyances that I haven't found a way around, and I was hoping to get > help here. > > 1) I can't find a way to stop the screen from blanking after a while. I > tried the screensaver settings, the power settings, and xset s off... > nothing has worked so far. This is a pain for me to, in particular when giving presentations on my laptop using ooimpress in full screen mode. It would be cool if running applications in full screen mode (ooimpress, totem, etc) could automagically turn off all forms of screen blanking. Keith. From kyrre at solution-forge.net Sat Mar 12 11:28:46 2005 From: kyrre at solution-forge.net (Kyrre Ness Sjobak) Date: Sat, 12 Mar 2005 12:28:46 +0100 Subject: FC3 annoyances (blanking and blanking) In-Reply-To: <1110620761.22897.26.camel@animal.passback.co.uk> References: <42329524.6060101@shopzilla.com> <1110620761.22897.26.camel@animal.passback.co.uk> Message-ID: <1110626925.3470.0.camel@localhost.localdomain> l?r, 12.03.2005 kl. 10.46 skrev Keith Sharp: > On Fri, 2005-03-11 at 23:07 -0800, Ofer Nave wrote: > > Hello! I'm new to Fedora... just installed FC3. There are two > > annoyances that I haven't found a way around, and I was hoping to get > > help here. > > > > 1) I can't find a way to stop the screen from blanking after a while. I > > tried the screensaver settings, the power settings, and xset s off... > > nothing has worked so far. > > This is a pain for me to, in particular when giving presentations on my > laptop using ooimpress in full screen mode. It would be cool if running > applications in full screen mode (ooimpress, totem, etc) could > automagically turn off all forms of screen blanking. > > Keith. There is a bug# in bugzilla about this - check under fc3->xscreensaver From g.hollestelle at gmail.com Sat Mar 12 12:32:02 2005 From: g.hollestelle at gmail.com (Gijs Hollestelle) Date: Sat, 12 Mar 2005 13:32:02 +0100 Subject: FC3 annoyances (blanking and blanking) In-Reply-To: <42329524.6060101@shopzilla.com> References: <42329524.6060101@shopzilla.com> Message-ID: <95da2d2905031204322ced8310@mail.gmail.com> On Fri, 11 Mar 2005 23:07:16 -0800, Ofer Nave wrote: > Hello! I'm new to Fedora... just installed FC3. There are two > annoyances that I haven't found a way around, and I was hoping to get > help here. > 2) I used to use SecureCRT to ssh into linux boxes for development, and > when I used man or less, the last screen would remain visible after > pressing 'q' to return to the prompt. Now that I'm using X, it > disappears when I quit. I've tried xterm, konsole, and gnome term - all > have the same behavior. This is caused by ncurses that restores the screen after you quit less, if you pass -X to less it doesn't do this. To make less use -X automaticly put something like: export LESS="-X" Into your startup script (this will also work for manual pages as these are displayed using less by default) Greets, Gijs From mgoodhew at gmail.com Sun Mar 13 12:17:34 2005 From: mgoodhew at gmail.com (Miles Goodhew) Date: Sun, 13 Mar 2005 23:17:34 +1100 Subject: [OT] RE: Being denied my own files! In-Reply-To: <1110571768.5618.2.camel@localhost.localdomain> References: <1110536444.32403.4.camel@wombat.tiptoe.de> <1110571768.5618.2.camel@localhost.localdomain> Message-ID: <3514a210503130417449a87ca@mail.gmail.com> Kyrre, On Fri, 11 Mar 2005 21:09:28 +0100, Kyrre Ness Sjobak wrote: > Strange. I have experienced several times to delete something root-owned > (in my home folder) from nautilus -> get thrown to ~/.Trash. (or > media/trash, but removable media is usually vfat so permissions isn't an > issue) > > When i then try to empty trash, all i get is "acess denied". If you own a directory, or if you have write permission to it, you can modify all links (file names) within it. If root owns any "normal" file in the dir, you can delete them immediately (rather, "unlink" them - only the system can delete). However, you can't unlink a directory file (yes, at the inode level, everything's a file with a specific type) unless the directory only contains the two links/names "." and ".." ("self inode" and "parent inode"). So it follows from the preceding two paragraphs that if root owns a directory in your home directory (and you can't write to that directory), then you can move it to some other directory (say "~/.trashcan" or something similar), but you can never actually crowbar it out of the filesystem. In that final case (and if you don't actually have root access to the box you're using), I usually move the directory as far up the filesystem as I can (put it in "/tmp" if it's the same filesystem), rename it to something like "FOR_CLIFFS_SAKE_DELETE_ME" and then possibly send the owner an email requesting it be expunged). Moles. -- Miles Goodhew, Senior Hacker TransACT communications From kyrre at solution-forge.net Sun Mar 13 15:25:54 2005 From: kyrre at solution-forge.net (Kyrre Ness Sjobak) Date: Sun, 13 Mar 2005 16:25:54 +0100 Subject: [OT] RE: Being denied my own files! In-Reply-To: <3514a210503130417449a87ca@mail.gmail.com> References: <1110536444.32403.4.camel@wombat.tiptoe.de> <1110571768.5618.2.camel@localhost.localdomain> <3514a210503130417449a87ca@mail.gmail.com> Message-ID: <1110727554.3447.0.camel@localhost.localdomain> s?n, 13.03.2005 kl. 13.17 skrev Miles Goodhew: > Kyrre, > > > On Fri, 11 Mar 2005 21:09:28 +0100, Kyrre Ness Sjobak > wrote: > > Strange. I have experienced several times to delete something root-owned > > (in my home folder) from nautilus -> get thrown to ~/.Trash. (or > > media/trash, but removable media is usually vfat so permissions isn't an > > issue) > > > > When i then try to empty trash, all i get is "acess denied". > > If you own a directory, or if you have write permission to it, you > can modify all links (file names) within it. If root owns any "normal" > file in the dir, you can delete them immediately (rather, "unlink" > them - only the system can delete). > However, you can't unlink a directory file (yes, at the inode level, > everything's a file with a specific type) unless the directory only > contains the two links/names "." and ".." ("self inode" and "parent > inode"). > So it follows from the preceding two paragraphs that if root owns a > directory in your home directory (and you can't write to that > directory), then you can move it to some other directory (say > "~/.trashcan" or something similar), but you can never actually > crowbar it out of the filesystem. > > In that final case (and if you don't actually have root access to > the box you're using), I usually move the directory as far up the > filesystem as I can (put it in "/tmp" if it's the same filesystem), > rename it to something like "FOR_CLIFFS_SAKE_DELETE_ME" and then > possibly send the owner an email requesting it be expunged). Okay, i understand :) Isn't /tmp often flushed by a reboot etc, also? From onave at shopzilla.com Sun Mar 13 22:22:29 2005 From: onave at shopzilla.com (Ofer Nave) Date: Sun, 13 Mar 2005 14:22:29 -0800 Subject: FC3 annoyances (blanking and blanking) In-Reply-To: <95da2d2905031204322ced8310@mail.gmail.com> References: <42329524.6060101@shopzilla.com> <95da2d2905031204322ced8310@mail.gmail.com> Message-ID: <4234BD25.90604@shopzilla.com> Gijs Hollestelle wrote: >On Fri, 11 Mar 2005 23:07:16 -0800, Ofer Nave wrote: > > >>Hello! I'm new to Fedora... just installed FC3. There are two >>annoyances that I haven't found a way around, and I was hoping to get >>help here. >>2) I used to use SecureCRT to ssh into linux boxes for development, and >>when I used man or less, the last screen would remain visible after >>pressing 'q' to return to the prompt. Now that I'm using X, it >>disappears when I quit. I've tried xterm, konsole, and gnome term - all >>have the same behavior. >> >> >This is caused by ncurses that restores the screen after you quit >less, if you pass -X to less it doesn't do this. To make less use -X >automaticly put something like: > >export LESS="-X" > >Into your startup script (this will also work for manual pages as >these are displayed using less by default) > >Greets, > Gijs > > > It works! Thanks. Problem #2 solved. Anyone have any ideas for problem 1? (screen blanking) -ofer From dchipman at ican.net Mon Mar 14 07:03:28 2005 From: dchipman at ican.net (David C. Chipman) Date: Mon, 14 Mar 2005 02:03:28 -0500 Subject: FC3 annoyances (blanking and blanking) In-Reply-To: <4234BD25.90604@shopzilla.com> References: <42329524.6060101@shopzilla.com> <95da2d2905031204322ced8310@mail.gmail.com> <4234BD25.90604@shopzilla.com> Message-ID: <1110783808.19638.37.camel@david.chipman> Hi Ofer, To fix your screensaver problem, got to Screensaver, on the Preferences sub menu of the Red Hat menu (click on the red hat in the lower left corner of your screen). In the screen saver preferences, select the Mode drop-down list. The option you want is Disable Screensaver. Good luck, -David -- David C. Chipman From onave at shopzilla.com Mon Mar 14 07:11:02 2005 From: onave at shopzilla.com (Ofer Nave) Date: Sun, 13 Mar 2005 23:11:02 -0800 Subject: FC3 annoyances (blanking and blanking) In-Reply-To: <1110783808.19638.37.camel@david.chipman> References: <42329524.6060101@shopzilla.com> <95da2d2905031204322ced8310@mail.gmail.com> <4234BD25.90604@shopzilla.com> <1110783808.19638.37.camel@david.chipman> Message-ID: <42353906.3030206@shopzilla.com> David C. Chipman wrote: > Hi Ofer, > > To fix your screensaver problem, got to Screensaver, on the >Preferences sub menu of the Red Hat menu (click on the red hat in the >lower left corner of your screen). In the screen saver preferences, >select the Mode drop-down list. The option you want is Disable >Screensaver. Good luck, > > -David > > This was the first thing I did when I began trying to solve this problem. :) Doesn't work. -ofer From nicu_fedora at nicubunu.ro Mon Mar 14 08:16:52 2005 From: nicu_fedora at nicubunu.ro (Nicu Buculei) Date: Mon, 14 Mar 2005 10:16:52 +0200 Subject: OpenOffice.org extras - again Message-ID: <42354874.7070600@nicubunu.ro> there was some recent talk about including additional templates in OpenOffice.org as distributed by Fedora: https://www.redhat.com/archives/fedora-devel-list/2005-March/msg00478.html the discuss was expanded later to other extras, like clipart. it appears other distributors are doing exactly this: add a lot of extras to their version of OOo, for example Novell is planning to include images from the Open Clip Art Library: http://lists.freedesktop.org/pipermail/clipart/2005-March/002539.html someone has created a rpm which probably will go in Fedora Extras https://www.redhat.com/archives/fedora-devel-list/2005-March/msg00566.html but IMO, something better is needed: integration - either include the clip art images in an OOo gallery using the patch from Novell or modify the OOo menu, adding a new item Insert->Pictures->Clipart which will point to the location of the installed images. also i think is worth judging the usefulness of including a *selection* of clipart in Core (i know in FC5 will not matter much if a package is in Core or Extras, this is about the next release, FC4). my take is: including clipart in the default install can benefit the overall value of the desktop, but also the size constraints should be considered. -- nicu From fsmith at web-links.net Mon Mar 14 10:16:07 2005 From: fsmith at web-links.net (Frank smith) Date: Mon, 14 Mar 2005 10:16:07 +0000 Subject: OpenOffice.org extras - again In-Reply-To: <42354874.7070600@nicubunu.ro> References: <42354874.7070600@nicubunu.ro> Message-ID: <1110795367.4679.3.camel@bear.rokpa> Hi If we need clipart we should be able to download it. It shouldn't be a part of the package. Cheers Bob On Mon, 2005-03-14 at 10:16 +0200, Nicu Buculei wrote: > there was some recent talk about including additional templates in > OpenOffice.org as distributed by Fedora: > https://www.redhat.com/archives/fedora-devel-list/2005-March/msg00478.html > the discuss was expanded later to other extras, like clipart. > > it appears other distributors are doing exactly this: add a lot of > extras to their version of OOo, for example Novell is planning to > include images from the Open Clip Art Library: > http://lists.freedesktop.org/pipermail/clipart/2005-March/002539.html > > someone has created a rpm which probably will go in Fedora Extras > https://www.redhat.com/archives/fedora-devel-list/2005-March/msg00566.html > but IMO, something better is needed: integration - either include the > clip art images in an OOo gallery using the patch from Novell or modify > the OOo menu, adding a new item Insert->Pictures->Clipart which will > point to the location of the installed images. > > also i think is worth judging the usefulness of including a *selection* > of clipart in Core (i know in FC5 will not matter much if a package is > in Core or Extras, this is about the next release, FC4). > my take is: including clipart in the default install can benefit the > overall value of the desktop, but also the size constraints should be > considered. > > -- > nicu > From beartooth at adelphia.net Mon Mar 14 14:41:05 2005 From: beartooth at adelphia.net (beartooth) Date: Mon, 14 Mar 2005 09:41:05 -0500 Subject: Do yum and up2date play nice? Message-ID: Being a belt-&-suspenders kind of guy, especially about security, I've been running both yum nightly updates and up2date (on three FC1 PCs and an FC2 PC). Someone recommended synaptic, and I installed that. Now when I invoke it, it gives me an error message about duplicate packages ; and when I look, sure enough, there are two -- with slightly different indicia. Will keeping both really make trouble? It looks like synaptic will let me find them and choose -- but not tell me how to choose. (My impulse would just be to take the later a/o higher numbered.) When I invoke synaptic, I get this : ===== [btth at localhost btth]$ synaptic & [1] 10128 [btth at localhost btth]$ (synaptic:10132): Gtk-CRITICAL **: file gtkwidget.c: line 2041 (gtk_widget_hide): assertion `GTK_IS_WIDGET (widget)' failed ===== and once it opens, it shows me : ===== There are multiple versions of "gd-devel" in your system. This package won't be cleanly updated, unless you leave only one version. To leave multiple versions installed, you may remove that warning by setting the following option in your configuration file: RPM::Allow-Duplicated { "^gd-devel$"; }; To disable these warnings completely set: RPM::Allow-Duplicated-Warning "false"; ===== similarly for gstreamer-plugins, gnome-session, man, libpng, syatem-config-display, slang, GConf2-devel, libbonobo, krb5-libs, rsync, squid, gnome-applets, rpm-build, shadow-utils, nfs-utils, mod_ssl, libpcap, and mkisofs. -- Beartooth Implacable, Linux Evangelist & Gadfly neo-redneck, curmudgeonly codger with FC1&2, YDL4 Pine 4.62, Pan 0.14.2; Privoxy 3.0.1; Opera 7.54, Firefox 1.0 Bear in mind that I have little idea what I am talking about. From kyrre at solution-forge.net Mon Mar 14 14:53:48 2005 From: kyrre at solution-forge.net (Kyrre Ness Sjobak) Date: Mon, 14 Mar 2005 15:53:48 +0100 Subject: OpenOffice.org extras - again In-Reply-To: <1110795367.4679.3.camel@bear.rokpa> References: <42354874.7070600@nicubunu.ro> <1110795367.4679.3.camel@bear.rokpa> Message-ID: <1110812027.5775.2.camel@localhost.localdomain> Some minimal stuff should be there - a few templates, a few cliparts etc. When you need them, you do often not have the time needed to go searching for them... man, 14.03.2005 kl. 11.16 skrev Frank smith: > Hi > If we need clipart we should be able to download it. > It shouldn't be a part of the package. > > > Cheers > Bob > > > > > > > > On Mon, 2005-03-14 at 10:16 +0200, Nicu Buculei wrote: > > there was some recent talk about including additional templates in > > OpenOffice.org as distributed by Fedora: > > https://www.redhat.com/archives/fedora-devel-list/2005-March/msg00478.html > > the discuss was expanded later to other extras, like clipart. > > > > it appears other distributors are doing exactly this: add a lot of > > extras to their version of OOo, for example Novell is planning to > > include images from the Open Clip Art Library: > > http://lists.freedesktop.org/pipermail/clipart/2005-March/002539.html > > > > someone has created a rpm which probably will go in Fedora Extras > > https://www.redhat.com/archives/fedora-devel-list/2005-March/msg00566.html > > but IMO, something better is needed: integration - either include the > > clip art images in an OOo gallery using the patch from Novell or modify > > the OOo menu, adding a new item Insert->Pictures->Clipart which will > > point to the location of the installed images. > > > > also i think is worth judging the usefulness of including a *selection* > > of clipart in Core (i know in FC5 will not matter much if a package is > > in Core or Extras, this is about the next release, FC4). > > my take is: including clipart in the default install can benefit the > > overall value of the desktop, but also the size constraints should be > > considered. > > > > -- > > nicu > > > From harald at redhat.com Mon Mar 14 15:09:55 2005 From: harald at redhat.com (Harald Hoyer) Date: Mon, 14 Mar 2005 16:09:55 +0100 Subject: X crashes when using a new monitor In-Reply-To: <1110226349.3439.16.camel@localhost.localdomain> References: <422C6753.2090300@yahoo.ca> <2ad7cea105030706461e1e280@mail.gmail.com> <422C6B07.4010501@yahoo.ca> <20050307153054.c2f3mb7npl8oog4o@corrig.dark-hill.co.uk> <422C75D2.7060604@yahoo.ca> <1110217916.3439.11.camel@localhost.localdomain> <20050307181510.v693q9w10di8c0kc@corrig.dark-hill.co.uk> <422CAE01.7050309@yahoo.ca> <422CB441.9040901@yahoo.ca> <1110226349.3439.16.camel@localhost.localdomain> Message-ID: <4235A943.6040400@redhat.com> Kyrre Ness Sjobak wrote: >>It worked! I coped /usr/X11R6 directory from a working FC3 and it works >>now. Thanks Douglas! > > > 8-| > > I can't wait to se what happens when an xorg update is pushed... > Or, if prelink was the cuplrit :) From nicu_fedora at nicubunu.ro Mon Mar 14 15:43:20 2005 From: nicu_fedora at nicubunu.ro (Nicu Buculei) Date: Mon, 14 Mar 2005 17:43:20 +0200 Subject: OpenOffice.org extras - again In-Reply-To: <1110812027.5775.2.camel@localhost.localdomain> References: <42354874.7070600@nicubunu.ro> <1110795367.4679.3.camel@bear.rokpa> <1110812027.5775.2.camel@localhost.localdomain> Message-ID: <4235B118.9080405@nicubunu.ro> Kyrre Ness Sjobak wrote: > Some minimal stuff should be there - a few templates, a few cliparts > etc. When you need them, you do often not have the time needed to go > searching for them... this is why i started this discuss, we should define this "minimal" stuff. i see two possible approaches: - size based: we define a desired maximum size and collect extras until this size is reached (more the other way around: from a huge pool of extras we eliminate until the size in reached) - functionality based: we define a set of goals (as user needs) and collect extras to fulfill those goals - for example, say we consider our users will want to draw network charts with OOo, then we should include a complete set of computer equipment images. i would prefer the second approach > man, 14.03.2005 kl. 11.16 skrev Frank smith: > >>Hi >>If we need clipart we should be able to download it. >>It shouldn't be a part of the package. we can have two packages containing extras: a small but useful one in Core and a big one in Extras -- nicu From kyrre at solution-forge.net Mon Mar 14 15:46:40 2005 From: kyrre at solution-forge.net (Kyrre Ness Sjobak) Date: Mon, 14 Mar 2005 16:46:40 +0100 Subject: OpenOffice.org extras - again In-Reply-To: <4235B118.9080405@nicubunu.ro> References: <42354874.7070600@nicubunu.ro> <1110795367.4679.3.camel@bear.rokpa> <1110812027.5775.2.camel@localhost.localdomain> <4235B118.9080405@nicubunu.ro> Message-ID: <1110815200.5775.20.camel@localhost.localdomain> man, 14.03.2005 kl. 16.43 skrev Nicu Buculei: > Kyrre Ness Sjobak wrote: > > Some minimal stuff should be there - a few templates, a few cliparts > > etc. When you need them, you do often not have the time needed to go > > searching for them... > > this is why i started this discuss, we should define this "minimal" stuff. > i see two possible approaches: > - size based: we define a desired maximum size and collect extras until > this size is reached (more the other way around: from a huge pool of > extras we eliminate until the size in reached) > - functionality based: we define a set of goals (as user needs) and > collect extras to fulfill those goals - for example, say we consider our > users will want to draw network charts with OOo, then we should include > a complete set of computer equipment images. > > i would prefer the second approach > Me to. Exept that dia is already pretty nice for making charts :) > > man, 14.03.2005 kl. 11.16 skrev Frank smith: > > > >>Hi > >>If we need clipart we should be able to download it. > >>It shouldn't be a part of the package. > > we can have two packages containing extras: a small but useful one in > Core and a big one in Extras > Agreed. From beartooth at adelphia.net Mon Mar 14 16:55:33 2005 From: beartooth at adelphia.net (beartooth) Date: Mon, 14 Mar 2005 11:55:33 -0500 Subject: Do yum and up2date play nice? -- detail References: Message-ID: On Mon, 14 Mar 2005 09:41:05 -0500, beartooth wrote: > Being a belt-&-suspenders kind of guy, especially about security, I've > been running both yum nightly updates and up2date (on three FC1 PCs and an > FC2 PC). Someone recommended synaptic, and I installed that. [....] I forgot to mention: synaptic is on the FC2; it was recommended specifically for that, and I don't know whether it exists for FC1, nor whether to try it if it does. -- Beartooth Implacable, Linux Evangelist & Gadfly neo-redneck, curmudgeonly codger with FC1&2, YDL4 Pine 4.62, Pan 0.14.2; Privoxy 3.0.1; Opera 7.54, Firefox 1.0 Bear in mind that I have little idea what I am talking about. From skvidal at phy.duke.edu Mon Mar 14 18:44:39 2005 From: skvidal at phy.duke.edu (seth vidal) Date: Mon, 14 Mar 2005 13:44:39 -0500 Subject: Do yum and up2date play nice? -- detail In-Reply-To: References: Message-ID: <1110825879.23972.25.camel@opus.phy.duke.edu> On Mon, 2005-03-14 at 11:55 -0500, beartooth wrote: > On Mon, 14 Mar 2005 09:41:05 -0500, beartooth wrote: > > > Being a belt-&-suspenders kind of guy, especially about security, I've > > been running both yum nightly updates and up2date (on three FC1 PCs and an > > FC2 PC). Someone recommended synaptic, and I installed that. [....] > > I forgot to mention: synaptic is on the FC2; it was recommended > specifically for that, and I don't know whether it exists for FC1, nor > whether to try it if it does. > choose one of: yum up2date apt/synaptic and go with it. do not use all of them at once. -sv From beartooth at adelphia.net Mon Mar 14 19:31:07 2005 From: beartooth at adelphia.net (beartooth) Date: Mon, 14 Mar 2005 14:31:07 -0500 Subject: Do yum and up2date play nice? -- detail References: <1110825879.23972.25.camel@opus.phy.duke.edu> Message-ID: On Mon, 14 Mar 2005 13:44:39 -0500, seth vidal wrote: > choose one of: > > yum > up2date > apt/synaptic > > > and go with it. > > do not use all of them at once. Well, as long as yum is working -- which seems to take a lot more and more frequent tweaking -- I prefer it to up2date. (I haven't really tried synaptic yet; haven't even run it.) So at least on the FC1 machines, I should remove the launchers on the panel for up2date. Any advice as between synaptic and yum? I presume each has pros and cons. -- Beartooth Implacable, Linux Evangelist & Gadfly neo-redneck, curmudgeonly codger with FC1&2, YDL4 Pine 4.62, Pan 0.14.2; Privoxy 3.0.1; Opera 7.54, Firefox 1.0 Bear in mind that I have little idea what I am talking about. From skvidal at phy.duke.edu Mon Mar 14 20:12:05 2005 From: skvidal at phy.duke.edu (seth vidal) Date: Mon, 14 Mar 2005 15:12:05 -0500 Subject: Do yum and up2date play nice? -- detail In-Reply-To: References: <1110825879.23972.25.camel@opus.phy.duke.edu> Message-ID: <1110831126.23972.45.camel@opus.phy.duke.edu> > Well, as long as yum is working -- which seems to take a lot more and more > frequent tweaking -- what tweaking does yum take? > Any advice as between synaptic and yum? I presume each has pros and cons. well from the web pages and mailing lists it looks like apt-rpm is abandoned. -sv From kyrre at solution-forge.net Mon Mar 14 20:16:21 2005 From: kyrre at solution-forge.net (Kyrre Ness Sjobak) Date: Mon, 14 Mar 2005 21:16:21 +0100 Subject: Do yum and up2date play nice? -- detail In-Reply-To: References: <1110825879.23972.25.camel@opus.phy.duke.edu> Message-ID: <1110831381.5775.36.camel@localhost.localdomain> a quick sumup: synaptic is a nice GUI for apt. up2date is only usefull to show pending updates yum is only usefull after fc2 (IMO), unless you are dealing with multilib. So for fc<3, use apt. For fc>3, use yum. If x86_64, use yum. That is the simple explanation. man, 14.03.2005 kl. 20.31 skrev beartooth: > On Mon, 14 Mar 2005 13:44:39 -0500, seth vidal wrote: > > > choose one of: > > > > yum > > up2date > > apt/synaptic > > > > > > and go with it. > > > > do not use all of them at once. > > Well, as long as yum is working -- which seems to take a lot more and more > frequent tweaking -- I prefer it to up2date. (I haven't really tried > synaptic yet; haven't even run it.) So at least on the FC1 machines, I > should remove the launchers on the panel for up2date. > > Any advice as between synaptic and yum? I presume each has pros and cons. > > -- > Beartooth Implacable, Linux Evangelist & Gadfly > neo-redneck, curmudgeonly codger with FC1&2, YDL4 > Pine 4.62, Pan 0.14.2; Privoxy 3.0.1; Opera 7.54, Firefox 1.0 > Bear in mind that I have little idea what I am talking about. > From skvidal at phy.duke.edu Mon Mar 14 20:37:49 2005 From: skvidal at phy.duke.edu (seth vidal) Date: Mon, 14 Mar 2005 15:37:49 -0500 Subject: Do yum and up2date play nice? -- detail In-Reply-To: <1110831381.5775.36.camel@localhost.localdomain> References: <1110825879.23972.25.camel@opus.phy.duke.edu> <1110831381.5775.36.camel@localhost.localdomain> Message-ID: <1110832669.23972.54.camel@opus.phy.duke.edu> On Mon, 2005-03-14 at 21:16 +0100, Kyrre Ness Sjobak wrote: > a quick sumup: > > synaptic is a nice GUI for apt. > > up2date is only usefull to show pending updates > > yum is only usefull after fc2 (IMO), unless you are dealing with > multilib. > > So for fc<3, use apt. For fc>3, use yum. If x86_64, use yum. > > That is the simple explanation. I disagree, of course, if you're looking for repositories you're going to have more luck finding yum repositories for FC-2. -sv From dotancohen at gmail.com Mon Mar 14 21:18:06 2005 From: dotancohen at gmail.com (Dotan Cohen) Date: Mon, 14 Mar 2005 23:18:06 +0200 Subject: Do yum and up2date play nice? -- detail In-Reply-To: <1110832669.23972.54.camel@opus.phy.duke.edu> References: <1110825879.23972.25.camel@opus.phy.duke.edu> <1110831381.5775.36.camel@localhost.localdomain> <1110832669.23972.54.camel@opus.phy.duke.edu> Message-ID: <880dece005031413189f0f2c3@mail.gmail.com> On Mon, 14 Mar 2005 15:37:49 -0500, seth vidal wrote: > On Mon, 2005-03-14 at 21:16 +0100, Kyrre Ness Sjobak wrote: > > a quick sumup: > > > > synaptic is a nice GUI for apt. > > > > up2date is only usefull to show pending updates > > > > yum is only usefull after fc2 (IMO), unless you are dealing with > > multilib. > > > > So for fc<3, use apt. For fc>3, use yum. If x86_64, use yum. > > > > That is the simple explanation. > > I disagree, of course, if you're looking for repositories you're going > to have more luck finding yum repositories for FC-2. > > -sv > > > -- > Fedora-desktop-list mailing list > Fedora-desktop-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-desktop-list > Another difference: in synaptic you can browse for packages. AFAIK you can't do that with yum. Dotan Cohen http://English-Lyrics.com http://Song-Lyriks.com From skvidal at phy.duke.edu Mon Mar 14 21:19:38 2005 From: skvidal at phy.duke.edu (seth vidal) Date: Mon, 14 Mar 2005 16:19:38 -0500 Subject: Do yum and up2date play nice? -- detail In-Reply-To: <880dece005031413189f0f2c3@mail.gmail.com> References: <1110825879.23972.25.camel@opus.phy.duke.edu> <1110831381.5775.36.camel@localhost.localdomain> <1110832669.23972.54.camel@opus.phy.duke.edu> <880dece005031413189f0f2c3@mail.gmail.com> Message-ID: <1110835178.23972.60.camel@opus.phy.duke.edu> > Another difference: in synaptic you can browse for packages. AFAIK you > can't do that with yum. > well considering yum isn't a graphic interface, you're right. if you want to search and look through things in yum, you can: yum list available yum search yum provides -sv From kyrre at solution-forge.net Mon Mar 14 21:52:55 2005 From: kyrre at solution-forge.net (Kyrre Ness Sjobak) Date: Mon, 14 Mar 2005 22:52:55 +0100 Subject: Do yum and up2date play nice? -- detail In-Reply-To: <1110835178.23972.60.camel@opus.phy.duke.edu> References: <1110825879.23972.25.camel@opus.phy.duke.edu> <1110831381.5775.36.camel@localhost.localdomain> <1110832669.23972.54.camel@opus.phy.duke.edu> <880dece005031413189f0f2c3@mail.gmail.com> <1110835178.23972.60.camel@opus.phy.duke.edu> Message-ID: <1110837175.5775.132.camel@localhost.localdomain> man, 14.03.2005 kl. 22.19 skrev seth vidal: > > Another difference: in synaptic you can browse for packages. AFAIK you > > can't do that with yum. > > > > well considering yum isn't a graphic interface, you're right. > > if you want to search and look through things in yum, you can: > > yum list available > yum search > yum provides > > -sv > Yes you can. And it works in fc3 (- even if a gui would be nice). But in fc2 and earlier its deadly slow (it migth be me remembering the performance of yum over a dialup...). But today, yum is a nice tool. Really. I am really glad it exists - it provides the "package management piece" to fc, and both me, and many more use it every day with joy. From james.f.powell at navy.mil Mon Mar 14 22:32:01 2005 From: james.f.powell at navy.mil (Powell, James F CONT) Date: Mon, 14 Mar 2005 14:32:01 -0800 Subject: Do yum and up2date play nice? -- detail Message-ID: <0CC8704F9601FA47961256F555270F2F01DC343B@NAWECHLKEX03VA.nadsuswe.nads.navy.mil> > On Mon, 14 Mar 2005 15:37:49 -0500, seth vidal > wrote: > > On Mon, 2005-03-14 at 21:16 +0100, Kyrre Ness Sjobak wrote: > > > a quick sumup: > > > > > > synaptic is a nice GUI for apt. > > > > > > up2date is only usefull to show pending updates > > > > > > yum is only usefull after fc2 (IMO), unless you are dealing with > > > multilib. > > > > > > So for fc<3, use apt. For fc>3, use yum. If x86_64, use yum. > > > > > > That is the simple explanation. > > > > I disagree, of course, if you're looking for repositories > you're going > > to have more luck finding yum repositories for FC-2. > > > > -sv > > > > > > -- > > Fedora-desktop-list mailing list > > Fedora-desktop-list at redhat.com > > http://www.redhat.com/mailman/listinfo/fedora-desktop-list > > > > Another difference: in synaptic you can browse for packages. AFAIK you > can't do that with yum. But with 3rd party apps, like yumi, you can browse, etc with yum. It's not as advanced a GUI as some, but it is functional and works nicely. Jim Powell Senior Scientist/Engineer L3 Communications GSI AV-8B Harrier Support From breun at xs4all.nl Mon Mar 14 22:54:13 2005 From: breun at xs4all.nl (Nils Breunese) Date: Mon, 14 Mar 2005 23:54:13 +0100 Subject: Do yum and up2date play nice? -- detail In-Reply-To: <880dece005031413189f0f2c3@mail.gmail.com> References: <1110825879.23972.25.camel@opus.phy.duke.edu> <1110831381.5775.36.camel@localhost.localdomain> <1110832669.23972.54.camel@opus.phy.duke.edu> <880dece005031413189f0f2c3@mail.gmail.com> Message-ID: <1110840853.21335.18.camel@breuniac> Dotan Cohen: > Another difference: in synaptic you can browse for packages. AFAIK you > can't do that with yum. That's like comparing apples to oranges. Synaptic is a GUI for apt; yum is not a GUI, it's a CLI app like apt. You can browse for packages with yum as a backend using one of the many yum GUI frontends (gyum, yum extender, yummi, etc.). Maybe synaptic is more mature at te moment than the various yum frontends, but I believe a lot of work is being put into them, so I guess it's getting better (disclaimer: I have not used any yum frontends). I used apt and synaptic on FC1 and FC2, but switched to yum with FC3. Not really sure why, but it works just fine. One thing though: every yum command you issue does a full refresh of the header files from the enabled repositories, which takes some time. I liked apt's separation with apt-get update (to update header files from repo's), apt-get upgrade (to upgrade packages) and other commands (like searching), although I do think with apt at first there might be some confusion as to what the difference between update and upgrade is. At least with yum your header files are always up to date. :) Nils Breunese. From jonathansavage at gmail.com Tue Mar 15 00:52:18 2005 From: jonathansavage at gmail.com (Jon Savage) Date: Mon, 14 Mar 2005 16:52:18 -0800 Subject: Do yum and up2date play nice? In-Reply-To: References: Message-ID: <2ad7cea105031416526602e400@mail.gmail.com> > been running both yum nightly updates and up2date (on three FC1 PCs and an > FC2 PC). Someone recommended synaptic, and I installed that. Now when I > invoke it, it gives me an error message about duplicate packages ; and > when I look, sure enough, there are two -- with slightly different indicia. > > Will keeping both really make trouble? It looks like synaptic will let me.. FWIW you are taken care of adaquately by just running yum, it will gracefully update anything that needs updating from Core, Extras and any "other" repos assuming you have properly configured it to do so. There is a possiblity that some of the other repos packages may conflice with Core/Extras (YMMV). As far as the duplicate rpms go keeping the newest version of each and doing rpm -e foo on the older of each pair should suffice. Bests, JS From harald at redhat.com Tue Mar 15 10:18:18 2005 From: harald at redhat.com (Harald Hoyer) Date: Tue, 15 Mar 2005 11:18:18 +0100 Subject: Fedora Core 4 ETA In-Reply-To: <4231481E.5020109@prodigy.net.mx> References: <1110432876.21187.15.camel@david.chipman> <4231481E.5020109@prodigy.net.mx> Message-ID: <4236B66A.5010300@redhat.com> Gain Paolo Mureddu wrote: > 1) From the desktop stand point, what advancements have there been > made in regards to things like udev. We all know udev in FC3 works, but > sometimes fails silently and wthout any warning whatsoever to the user > on what's going on. I'm sure this has been worked on for Core 4, but how > has it been addressed? What exactly do you mean? From gmureddu at prodigy.net.mx Tue Mar 15 10:57:00 2005 From: gmureddu at prodigy.net.mx (Gain Paolo Mureddu) Date: Tue, 15 Mar 2005 04:57:00 -0600 Subject: Fedora Core 4 ETA In-Reply-To: <4236B66A.5010300@redhat.com> References: <1110432876.21187.15.camel@david.chipman> Message-ID: <4236BF7C.1020407@prodigy.net.mx> Harald Hoyer wrote: > Gain Paolo Mureddu wrote: > >> 1) From the desktop stand point, what advancements have there been >> made in regards to things like udev. We all know udev in FC3 works, >> but sometimes fails silently and wthout any warning whatsoever to the >> user on what's going on. I'm sure this has been worked on for Core 4, >> but how has it been addressed? > > > What exactly do you mean? > For instance when your USB mouse suddenly stops working, and if you search for your any kind of explanation in the system log, you'll most likely will find a series of erros regarding timeouts and that the device is not accepting x or y address... From harald at redhat.com Tue Mar 15 15:13:01 2005 From: harald at redhat.com (Harald Hoyer) Date: Tue, 15 Mar 2005 16:13:01 +0100 Subject: Fedora Core 4 ETA In-Reply-To: <4236BF7C.1020407@prodigy.net.mx> References: <1110432876.21187.15.camel@david.chipman> <4236BF7C.1020407@prodigy.net.mx> Message-ID: <4236FB7D.7040707@redhat.com> Gain Paolo Mureddu wrote: > Harald Hoyer wrote: > >> Gain Paolo Mureddu wrote: >> >>> 1) From the desktop stand point, what advancements have there been >>> made in regards to things like udev. We all know udev in FC3 works, >>> but sometimes fails silently and wthout any warning whatsoever to the >>> user on what's going on. I'm sure this has been worked on for Core 4, >>> but how has it been addressed? >> >> >> >> What exactly do you mean? >> > For instance when your USB mouse suddenly stops working, and if you > search for your any kind of explanation in the system log, you'll most > likely will find a series of erros regarding timeouts and that the > device is not accepting x or y address... > udev has nothing to do with that... that is the kernel... I also experience those mouse hangups... search bugzilla for this kernel bug. From sopwith at redhat.com Wed Mar 16 17:28:00 2005 From: sopwith at redhat.com (Elliot Lee) Date: Wed, 16 Mar 2005 12:28:00 -0500 Subject: Fedora Project Mailing Lists reminder Message-ID: This is a reminder of the mailing lists for the Fedora Project, and the purpose of each list. You can view this information at http://fedora.redhat.com/participate/communicate/ When you're using these mailing lists, please take the time to choose the one that is most appropriate to your post. If you don't know the right mailing list to use for a question or discussion, please contact me. This will help you get the best possible answer for your question, and keep other list subscribers happy! Mailing Lists Mailing lists are email addresses which send email to all users subscribed to the mailing list. Sending an email to a mailing list reaches all users interested in discussing a specific topic and users available to help other users with the topic. The following mailing lists are available. To subscribe, send email to -request at redhat.com (replace with the desired mailing list name such as fedora-list) with the word subscribe in the subject. fedora-announce-list - Announcements of changes and events. To stay aware of news, subscribe to this list. fedora-list - For users of releases. If you want help with a problem installing or using , this is the list for you. fedora-test-list - For testers of test releases. If you would like to discuss experiences using TEST releases, this is the list for you. fedora-devel-list - For developers, developers, developers. If you are interested in helping create releases, this is the list for you. fedora-extras-list - For users and developers of Fedora Extras fedora-docs-list - For participants of the docs project fedora-desktop-list - For discussions about desktop issues such as user interfaces, artwork, and usability fedora-config-list - For discussions about the development of configuration tools fedora-tools-list - For discussions about the toolchain (gcc, gdb, etc...) within Fedora fedora-devel-java-list - For discussions about Java-related Fedora development fedora-patches-list - For submitting patches to Fedora maintainers, and used in line with BugWeek fedora-legacy-announce - For announcements about the Fedora Legacy Project fedora-legacy-list - For discussions about the Fedora Legacy Project fedora-selinux-list - For discussions about the Fedora SELinux Project fedora-marketing-list - For discussions about marketing and expanding the Fedora user base fedora-de-list - For discussions about Fedora in the German language fedora-es-list - For discussions about Fedora in the Spanish language fedora-ja-list - For discussions about Fedora in the Japanese language fedora-i18n-list - For discussions about the internationalization of Fedora Core fedora-trans-list - For discussions about translating the software and documentation associated with the Fedora Project German: fedora-trans-de French: fedora-trans-fr Spanish: fedora-trans-es Italian: fedora-trans-it Brazilian Portuguese: fedora-trans-pt_br Japanese: fedora-trans-ja Korean: fedora-trans-ko Simplified Chinese: fedora-trans-zh_cn Traditional Chinese: fedora-trans-zh_tw From mike at navi.cx Mon Mar 21 15:29:31 2005 From: mike at navi.cx (Mike Hearn) Date: Mon, 21 Mar 2005 15:29:31 +0000 Subject: Make consolehelper more liske sudo? References: <4225D6D7.9010103@snowmoon.com> <1109878491.21167.15.camel@localhost.localdomain> <20050303200235.GB15060@jadzia.bu.edu> <1109881873.4422.49.camel@daxter.boston.redhat.com> <20050303210117.GA17833@jadzia.bu.edu> Message-ID: On Thu, 03 Mar 2005 16:01:17 -0500, Matthew Miller wrote: > Software installation *definitely* needs some sort of authentication and > special privilege. Sure, this needs to be made so it's not intimidating, but > we also shouldn't shoot ourselves in the head. You're thinking like an admin - yes for managed networks users probably should not be able to install whatever they like but bear in mind anybody can stick software in $HOME if they really want to, even if it's mounted no-exec. So I think what you really want to avoid is unpredictable system reconfiguration/change rather than software installation per-se. And yes for home/personal systems clearly any root/sudo prompts at all are silly, the user should never be prompted for a password once they have logged in - not even for software installation. thanks -mike From kyrre at solution-forge.net Mon Mar 21 16:36:40 2005 From: kyrre at solution-forge.net (Kyrre Ness Sjobak) Date: Mon, 21 Mar 2005 17:36:40 +0100 Subject: Make consolehelper more liske sudo? In-Reply-To: References: <4225D6D7.9010103@snowmoon.com> <1109878491.21167.15.camel@localhost.localdomain> <20050303200235.GB15060@jadzia.bu.edu> <1109881873.4422.49.camel@daxter.boston.redhat.com> <20050303210117.GA17833@jadzia.bu.edu> Message-ID: <1111423000.3331.231.camel@localhost.localdomain> man, 21.03.2005 kl. 16.29 skrev Mike Hearn: > On Thu, 03 Mar 2005 16:01:17 -0500, Matthew Miller wrote: > > Software installation *definitely* needs some sort of authentication and > > special privilege. Sure, this needs to be made so it's not intimidating, but > > we also shouldn't shoot ourselves in the head. > > You're thinking like an admin - yes for managed networks users probably > should not be able to install whatever they like but bear in mind anybody > can stick software in $HOME if they really want to, even if it's mounted > no-exec. So I think what you really want to avoid is unpredictable system > reconfiguration/change rather than software installation per-se. > > And yes for home/personal systems clearly any root/sudo prompts at all are > silly, the user should never be prompted for a password once they have > logged in - not even for software installation. I disagree - the pasword promt is a good indication of "you are now doing something that will (permanently) change your system configuration". And the gtk pasword dialog (gtksu?) also tells which program asked for root acess. From peter.backlund at home.se Tue Mar 22 20:45:54 2005 From: peter.backlund at home.se (Peter Backlund) Date: Tue, 22 Mar 2005 21:45:54 +0100 Subject: Desktop integration Message-ID: <1111524354.2872.52.camel@localhost.localdomain> Hello. I'd like to give my point of view of the current state of Bluecurve and desktop integration in Fedora, focusing on the artwork. -- The icon set -- The BC icon set is of course comprehensive and generally of very high quality, but there are areas where it is lacking: very small icons, 16x16 or 20x20, are often badly hinted. It looks like the 48x48 version has been scaled down, and a very sharp black edge has been added along the perimeter. Sometimes hinting is missing entirely, leaving a very blurry icon. Also, too much detail is crammed into the small icons. Compare these two screenshots of the Gnome file selector: http://petrix.se/fedora/fileselector_bluecurve.png http://petrix.se/fedora/fileselector_gnome.png The Gnome icons on the left are not only scaled-down versions of the larger ones, but completely redesigned. The Bluecurve Home and Desktop icons are good examples of down-scaled, black-outlined icons with too much detail, and the filesystem icons are missing hinting. I think focus should shift from providing half-done icons for every single menu entry (Sound Juicer, XChat, etc) to improving the icons that make sense for cross-DE (desktop environment) integration, such as basic operations (open, close, home), navigation, RH/Fedora specific applications (system-config-*) and maybe a few main applications (web browser, email program). Build on top of the existing Gnome and KDE/Crystal icon sets, adding a unique "feel", instead of replacing 100%. Ximian Desktop only changed the folder icons and a handful of others, but along with the Gtk theme it made a huge difference. The KDE Crystal icons go very well with the BC icons, and KDE would benefit enormously from better 16x16 icons. -- KDE/Qt -- KDE and Qt are obviously not the main focus of the Fedora desktop team, but the Bluecurve Qt theme was a pioneering effort. However, the version shipped with FC3 has a long list of rendering differences from the Gtk theme. I have personally done some hacking on the Qt theme, trying to bring it closer to the Gtk one: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=141125 None of it has yet shown up in Rawhide, despite being well received. A lot of 3:rd party commercial/scientific applications are written in Qt, and having a near-perfect Qt theme will add to the professional feel of a Red Hat/Fedora desktop. Maybe Qt could be modified to use the Gtk file selector, when an environment variable is set? -- OpenOffice.org/NWF -- The state of of NWF in OOo in 1.1.x, and also in 2.0, is promising at best. If it were up to me, I wouldn't ship it for a few more months. The widget coverage has increased in 2.0, but the quality of individual widgets is still very low. http://petrix.se/fedora/OOo.png Sizes, alignment, shapes, highlighting etc etc. Since the Open Office suite is such a prominent application, I believe more manpower should be thrown at the problem. I know this comes off very negative, and I do not mean to diminish the efforts of the NWF hackers (Dan W for example). It will look tremendous once it's done. It's just that 100% of the widgets are 50% finished, and it would look a lot better if 50% of the widgets were 100% done, and the rest were #ifdef-ed out until they are done. A guide to hacking NWF would be great to attract outsiders, and a list of tricks to build the beast for limited (NWF-only) testing. Stuff that can be ./configure-ed out, ccache etc. -- Firefox/Thunderbird (XUL) -- FF/TB look fairly good already, but have a number of annoying rendering bugs. Submenu arrows, icons alignment on buttons and so on. Better icon coverage in the menus would also be nice -look at the Industrial theme, it has icons for nearly every menu entry: http://linuxart.com/log/archives/2004/09/20/industrial-for-firefox/ -- Conclusion -- So let me sum up: * Fewer, but better Bluecurve icons. Focus on the small ones. * Fix the Qt theme. Patch and bug list in Bugzilla. Not complete, but a good start. * More manpower to OOo/NWF, it's farther behind but very important. * Better icon coverage in menus/preference dialog in FF/TB. /Peter Backlund From nicu_fedora at nicubunu.ro Wed Mar 23 08:16:25 2005 From: nicu_fedora at nicubunu.ro (Nicu Buculei) Date: Wed, 23 Mar 2005 10:16:25 +0200 Subject: Desktop integration In-Reply-To: <1111524354.2872.52.camel@localhost.localdomain> References: <1111524354.2872.52.camel@localhost.localdomain> Message-ID: <424125D9.7050705@nicubunu.ro> Peter Backlund wrote: > I'd like to give my point of view of the current state of Bluecurve and > desktop integration in Fedora, focusing on the artwork. > > -- The icon set -- > > The BC icon set is of course comprehensive and generally of very high > quality, but there are areas where it is lacking: very small icons, > 16x16 or 20x20, are often badly hinted. It looks like the 48x48 version > has been scaled down, and a very sharp black edge has been added along > the perimeter. Sometimes hinting is missing entirely, leaving a very > blurry icon. Also, too much detail is crammed into the small icons. > > Compare these two screenshots of the Gnome file selector: > > http://petrix.se/fedora/fileselector_bluecurve.png > > http://petrix.se/fedora/fileselector_gnome.png > > The Gnome icons on the left are not only scaled-down versions of the > larger ones, but completely redesigned. The Bluecurve Home and Desktop > icons are good examples of down-scaled, black-outlined icons with too > much detail, and the filesystem icons are missing hinting. comparing the two icon sets, you will see two different approaches: the Gnome ones are made at bitmaps, requiring a complete redesign for various sizes; the Bluecurve icons are made in vectorial format (Adobe Illustrator), which means at resize only minor adjustments are needed. unfortunately, as you observe, this adjustment was not made or is not good enough. i would like something else: the icon set made in a *free* scalable format, permitting contributors to work with affordable free tools (ideally with tools included in Fedora Core). back when Bluecurve was created, this was not possible, but, IMO, now a tool like Inkscape was matured enough, is good enough to be used to create a complete icon set, and as part of Fedora Extras is accessible to potential contributors. note: in a future fully Cairo accelerated desktop make sense to have a SVG icon set. > -- OpenOffice.org/NWF -- > > The state of of NWF in OOo in 1.1.x, and also in 2.0, is promising at > best. If it were up to me, I wouldn't ship it for a few more months. The > widget coverage has increased in 2.0, but the quality of individual > widgets is still very low. OOo 2.0 is still under heavy development, both at Red Hat and upstream and NWF is part of this ongoing development. as the OOo release is still at least two months away, there is time for visible improvements. > Sizes, alignment, shapes, highlighting etc etc. Since the Open Office > suite is such a prominent application, I believe more manpower should be > thrown at the problem. I know this comes off very negative, and I do not > mean to diminish the efforts of the NWF hackers (Dan W for example). It > will look tremendous once it's done. It's just that 100% of the widgets > are 50% finished, and it would look a lot better if 50% of the widgets > were 100% done, and the rest were #ifdef-ed out until they are done. here i don't agree: 50% of widgets done and the rest untouched look very inconsistent. take as an example the OOo iconset as included in FC3: half Bluecurve and half Industrial: http://fedora.nicubunu.ro/ooo-bluecurve.png IMO, this floppy icon example is very good: having access to the icons source (which as i said before, is AI) any contributor can produce a Bluecurve version of the second icon in less than one minute (just add a black triangle to the save one) > -- Firefox/Thunderbird (XUL) -- > > FF/TB look fairly good already, but have a number of annoying rendering > bugs. Submenu arrows, icons alignment on buttons and so on. Better icon > coverage in the menus would also be nice -look at the Industrial theme, > it has icons for nearly every menu entry: > > http://linuxart.com/log/archives/2004/09/20/industrial-for-firefox/ i agree: the default browser should make full use of the icon set used on the desktop (and not introduce a new style of icons) > -- Conclusion -- > > So let me sum up: well, as you may know, the look of FC3 was seriously lacking partly because the author of the original Bluecurve has left Red Hat around FC2 release time and it was a few months until they found a replacement. i believe the best solution is to increase the community involvement in maintaining and creating the icon theme -- nicu From gmureddu at prodigy.net.mx Wed Mar 23 23:09:07 2005 From: gmureddu at prodigy.net.mx (Gain Paolo Mureddu) Date: Wed, 23 Mar 2005 17:09:07 -0600 Subject: Strange messages in syslog Message-ID: <4241F713.8060908@prodigy.net.mx> Hi all... Maybe I'm being too paranoid, but I just wanted to know what may be going on if I have a lot of messages in /var/log/messages about root sessions being opened and closed very quickly, for instance: Mar 23 16:55:01 Blackhawk crond(pam_unix)[6028]: session opened for user root by (uid=0) Mar 23 16:55:01 Blackhawk crond(pam_unix)[6028]: session closed for user root As you can see the session lasts less than a second. What does this mean? Are these processes that require root access that open the session and as soon as these services are done, close it?? Thanks! PS: I know this may not be the best place to post this, if so, what would be the best place to post this? From davej at redhat.com Thu Mar 24 00:24:00 2005 From: davej at redhat.com (Dave Jones) Date: Wed, 23 Mar 2005 19:24:00 -0500 Subject: Strange messages in syslog In-Reply-To: <4241F713.8060908@prodigy.net.mx> References: <4241F713.8060908@prodigy.net.mx> Message-ID: <20050324002400.GQ15879@redhat.com> On Wed, Mar 23, 2005 at 05:09:07PM -0600, Gain Paolo Mureddu wrote: > Mar 23 16:55:01 Blackhawk crond(pam_unix)[6028]: session opened for user root by (uid=0) > Mar 23 16:55:01 Blackhawk crond(pam_unix)[6028]: session closed for user root ^^^^^ > As you can see the session lasts less than a second. What does this > mean? Are these processes that require root access that open the session > and as soon as these services are done, close it?? It's cron. > PS: I know this may not be the best place to post this, if so, what > would be the best place to post this? fedora-list at redhat.com Dave From gmureddu at prodigy.net.mx Thu Mar 24 03:11:43 2005 From: gmureddu at prodigy.net.mx (Gain Paolo Mureddu) Date: Wed, 23 Mar 2005 21:11:43 -0600 Subject: Strange messages in syslog In-Reply-To: <20050324002400.GQ15879@redhat.com> References: <4241F713.8060908@prodigy.net.mx> <20050324002400.GQ15879@redhat.com> Message-ID: <42422FEF.2070909@prodigy.net.mx> Dave Jones wrote: >On Wed, Mar 23, 2005 at 05:09:07PM -0600, Gain Paolo Mureddu wrote: > > > Mar 23 16:55:01 Blackhawk crond(pam_unix)[6028]: session opened for user root by (uid=0) > > Mar 23 16:55:01 Blackhawk crond(pam_unix)[6028]: session closed for user root > ^^^^^ > > > As you can see the session lasts less than a second. What does this > > mean? Are these processes that require root access that open the session > > and as soon as these services are done, close it?? > >It's cron. > > > PS: I know this may not be the best place to post this, if so, what > > would be the best place to post this? > >fedora-list at redhat.com > > Dave > > > Thaks Dave... I know I should have paid more attention to the messages ;) From gmureddu at prodigy.net.mx Fri Mar 25 20:01:52 2005 From: gmureddu at prodigy.net.mx (Gain Paolo Mureddu) Date: Fri, 25 Mar 2005 14:01:52 -0600 Subject: Changing default WM for GNOME2 Message-ID: <42446E30.90909@prodigy.net.mx> Although I like Metacity, it is not as low-weight as others, like xfwm4. I'd like to change the default window manager for GNOME in FC3, but whenever I do gconf --> desktop --> gnome --> applications --> window_manager --> default and change there /usr/bin/xfwm4, upon session restart metacity kicks in and I can't stop it from running, cause it immediately loads up again! How can I change this behavior? Is it even remotely possible to do this, or FC3's GNOME WM is hardcoded into some GNOME parts? From kaspars at os.lv Tue Mar 29 10:16:26 2005 From: kaspars at os.lv (Kaspars) Date: Tue, 29 Mar 2005 13:16:26 +0300 Subject: Gnome slowing down again... Message-ID: <42492AFA.1060502@os.lv> Hi, I recently start to have problem with fresh installed FC3 with updates. CPU get load and my fan is getting noisy on laptop... top shows: load average: 5.42, 4.99, 3.27 R 24.6 2.4 3:32.55 gnome-settings- R 24.0 5.2 3:43.49 gnome-panel R 23.6 5.5 3:30.77 nautilus R 23.3 1.4 3:27.30 gnome-vfs-daemo S 3.0 4.8 0:00.44 gnome-terminal S 2.0 8.0 0:39.84 X I close all what is opened, but still load is big and then only reboot helps... I`m not hacker, but how I understand it is Gnome problem, anybody have experienced the some? Casper