Re: fedora-list Digest, Fedora Preview 11 ATI Driver install crash IRQ

Send fedora-list mailing list submissions to fedora-list(a)redhat.com To subscribe or unsubscribe via the World Wide Web, visit https://www.redhat.com/mailman/listinfo/fedora-list or, via email, send a message with subject or body 'help' to fedora-list-request(a)redhat.com You can reach the person managing the list at fedora-list-owner(a)redhat.com When replying, please edit your Subject line so it is more specific than "Re: Contents of fedora-list digest..." Today's Topics: 1. yum red letters (Oliver Ruebenacker) 2. Re: yum red letters (Todd Zullinger) 3. kmod-nvidia yum update problem (Steve) 4. Re: Accessing A Fedora 7 Box FROM The Net (Bruno Wolff III) 5. Re: find tux comic picture help (Marc Ferguson) 6. Re: "Blinking lights of death" ? Netgear Switch GS108 (Robin Laing) 7. Re: Where is lsof? (Alan Evans) 8. Re: Where is lsof? (Mikkel L. Ellertson) 9. Re: phoronix-test-suite for Fedora? (Kevin Fenzi) 10. Re: Where is lsof? (Sharpe, Sam J) 11. Re: kmod-nvidia yum update problem (Thorsten Leemhuis) 12. Not getting clean shutdowns for FireFox and Epiphany (William Case) 13. Re: Selinux disallows read-only loop mount of a file, but only at boot [SOLVED] (David) ---------------------------------------------------------------------- Message: 1 Date: Tue, 5 May 2009 09:41:42 -0400 From: Oliver Ruebenacker <curoli(a)gmail.com&gt; Subject: yum red letters To: "Community assistance, encouragement, and advice for using Fedora." <fedora-list(a)redhat.com&gt; Message-ID: <5639badd0905050641j39bf5c91t11463f175db88d1f(a)mail.gmail.com&gt; Content-Type: text/plain; charset=ISO-8859-1 Hello, Any one knows why yum prints the installed Sun Java JRE in red letters when I list packages? Thanks! Take care Oliver -- Oliver Ruebenacker, Computational Cell Biologist BioPAX Integration at Virtual Cell (http://vcell.org/biopax) Center for Cell Analysis and Modeling http://www.oliver.curiousworld.org ------------------------------ Message: 2 Date: Tue, 5 May 2009 09:53:24 -0400 From: Todd Zullinger <tmz(a)pobox.com&gt; Subject: Re: yum red letters To: fedora-list(a)redhat.com Message-ID: <20090505135324.GG4166(a)inocybe.localdomain&gt; Content-Type: text/plain; charset="utf-8" Oliver Ruebenacker wrote: > Any one knows why yum prints the installed Sun Java JRE in red > letters when I list packages? Thanks! The meanings of the colors used are described in the yum.conf(5) man page. For example: color_list_installed_extra The colorization/highlighting for pacakges in list/info installed which has no available package with the same name and arch. Default is ‘bold,red’. See color_list_installed_older for possible values. -- Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ People demand freedom of speech to make up for the freedom of thought which they avoid. -- Soren Aabye Kierkegaard (1813-1855) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 542 bytes Desc: not available Url : https://www.redhat.com/archives/fedora-list/attachments/20090505/49919185... ------------------------------ Message: 3 Date: Tue, 5 May 2009 9:54:35 -0400 From: Steve <zephod(a)cfl.rr.com&gt; Subject: kmod-nvidia yum update problem To: fedora-list(a)redhat.com Message-ID: <20090505135435.4GJHM.430729.root@cdptpa-web06-z02> Content-Type: text/plain; charset=utf-8 I get this error when trying to update kmod-nvidia package: Test Transaction Errors: file /lib/modules/2.6.27.21-78.2.41.fc9.x86_64/extra/nvidia/nvidia.ko from install of kmod-nvidia-2.6.27.21-78.2.41.fc9.x86_64-173.14.15-1.fc9.12.x86_64 conflicts with file from package kmod-nvidia-2.6.27.21-78.2.41.fc9.x86_64-173.14.15-1.fc9.5.x86_64 which appears to be telling me that it cannot upgrade because the package it is trying to replace has a file by the same name. Isn't that the point of an upgrade? I assume I am misinterpreting this. Thanks, Steve $ rpm -qa | grep 'kmod\|nvidia' xorg-x11-drv-nvidia-173.14.15-2.fc9.x86_64 kmod-nvidia-2.6.27.21-78.2.41.fc9.x86_64-173.14.15-1.fc9.5.x86_64 akmod-nvidia-173.14.15-1.fc9.5.x86_64 kmod-ndiswrapper-2.6.27.21-78.2.41.fc9.x86_64-1.53-5.fc9.13.x86_64 kmod-ndiswrapper-2.6.27.15-78.2.23.fc9.x86_64-1.53-5.fc9.11.x86_64 yum-fedorakmod-1.1.19-1.fc9.noarch kmodtool-1-15.fc9.noarch kmod-ndiswrapper-1.53-5.fc9.13.x86_64 xorg-x11-drv-nvidia-libs-173.14.15-2.fc9.x86_64 akmods-0.3.3-2.fc9.noarch kmod-ndiswrapper-2.6.27.19-78.2.30.fc9.x86_64-1.53-5.fc9.12.x86_64 $ uname -r 2.6.27.21-78.2.41.fc9.x86_64 ------------------------------ Message: 4 Date: Tue, 5 May 2009 08:56:31 -0500 From: Bruno Wolff III <bruno(a)wolff.to&gt; Subject: Re: Accessing A Fedora 7 Box FROM The Net To: "Admin@AnythingGoes" <admin(a)anything-goes.us&gt; Cc: fedora-list(a)redhat.com Message-ID: <20090505135631.GB17760(a)wolff.to&gt; Content-Type: text/plain; charset=us-ascii On Tue, May 05, 2009 at 08:07:46 -0400, "Admin@AnythingGoes" <admin(a)anything-goes.us&gt; wrote: > > I can ping the server, but I cannot SSH in, FTP in or WEB BROWSE in.. > All the appropriate servers are running and are easily accessed from > within the 192.168.1.x subnet.. If you are using those addresses it won't work because those aren't routable. And your dsl modem with have to be doing nat. If those aren't the correct addresses, then you are lying to us and that is not a good way to get your problems solved. ------------------------------ Message: 5 Date: Tue, 5 May 2009 10:13:55 -0400 From: Marc Ferguson <marcferguson(a)gmail.com&gt; Subject: Re: find tux comic picture help To: "Community assistance, encouragement, and advice for using Fedora." <fedora-list(a)redhat.com&gt; Message-ID: <e3f73e670905050713p4a6189edre542bfb8070591a2(a)mail.gmail.com&gt; Content-Type: text/plain; charset="utf-8" On Sat, May 2, 2009 at 11:24 AM, Erik Xavior <erikxavior80(a)gmail.com&gt; wrote: > does anyone knows/have that comic picture of "tux" the Linux penguin that: > > - has four pictures in it > - it defines 4 "levels" of the knowledge of tux, who is "symbolizing a > learning person" > - the first one: tux is just a Linux "fanboy"; second: tux is working, and > say's: "...stupid rpm"; three: I can't remember that:D sorry; four: tux has > a beard, and the picture says don't mess with it. > > thank you, and sorry for the question, but I just can't find it on google > :D :S > -- > fedora-list mailing list > fedora-list(a)redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: > http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > Hi Xavior, I don't know about those images your talking about, but I do know of a great resource for TUX. http://tux.crystalxp.net/ Maybe you can do a Google search for "tux gallery cartoon" or something of that nature. Happy hunting! -- Marc F. www.fergytech.com Registered Linux User: #410978 "When life gives me lemons... I make Linuxaide, hmm good stuff!" -------------- next part -------------- An HTML attachment was scrubbed... URL: https://www.redhat.com/archives/fedora-list/attachments/20090505/8b13a7cc... ------------------------------ Message: 6 Date: Tue, 05 May 2009 08:29:27 -0600 From: Robin Laing <Robin.Laing(a)drdc-rddc.gc.ca&gt; Subject: Re: "Blinking lights of death" ? Netgear Switch GS108 To: "Community assistance, encouragement, and advice for using Fedora." <fedora-list(a)redhat.com&gt; Message-ID: <4A004D47.9060004(a)drdc-rddc.gc.ca&gt; Content-Type: text/plain; charset=ISO-8859-1; format=flowed David Liguori wrote: > > > Aldo Foot wrote: >> On Wed, Apr 29, 2009 at 7:23 PM, Robert L Cochran >> <cochranb(a)speakeasy.net&gt; wrote: >> > One of the more common mechanisms for failure of electrolytic capacitors > is too high an ambient temperature over a period of time. Usually the > temperature rating is on the cap. You say the room is well-ventilated > but that doesn't rule out too high an ambient temperature in a room full > of equipment, especially if it was sitting on top of or in a rack full > of other equipment. It's more likely to have open rather than short > circuited. An ESR (effective series resistance) meter will tell. > > If you're pretty sure the capacitor is what's ailing it and it's > through-hole rather than surface mounted, I would consider it well worth > fixing, or even trying if there's greater than a 10% success > probability. Many 8-port switches aren't worth fixing below that. > Another issue is using capacitors that are close to the operating voltage of the system. 12V and use 15V capacitors. This doesn't give any overhead for voltage spikes or surges caused by charging and discharging circuits. Remember that many circuit boards are multi-layer now so be careful if you are working with a thru-hole circuit board. Have fun. -- Robin Laing ------------------------------ Message: 7 Date: Tue, 5 May 2009 07:52:34 -0700 From: Alan Evans <ame.fedora(a)gmail.com&gt; Subject: Re: Where is lsof? To: "Community assistance, encouragement, and advice for using Fedora." <fedora-list(a)redhat.com&gt; Message-ID: <ec0de77f0905050752h6d1a4defr16249a64966b6615(a)mail.gmail.com&gt; Content-Type: text/plain; charset=ISO-8859-1 On Tue, May 5, 2009 at 5:39 AM, Mike Cloaked wrote: > Usually a good way to find where a command is would be to use the "which" > command. In this case: > [mike@gestalt ~]$ which lsof > /usr/sbin/lsof How is that going to work if /usr/sbin isn't already in your path? ------------------------------ Message: 8 Date: Tue, 05 May 2009 10:13:46 -0500 From: "Mikkel L. Ellertson" <mikkel(a)infinity-ltd.com&gt; Subject: Re: Where is lsof? To: "Community assistance, encouragement, and advice for using Fedora." <fedora-list(a)redhat.com&gt; Message-ID: <4A0057AA.2090501(a)infinity-ltd.com&gt; Content-Type: text/plain; charset="iso-8859-1" Alan Evans wrote: > On Tue, May 5, 2009 at 5:39 AM, Mike Cloaked wrote: >> Usually a good way to find where a command is would be to use the "which" >> command. In this case: >> [mike@gestalt ~]$ which lsof >> /usr/sbin/lsof > > How is that going to work if /usr/sbin isn't already in your path? > It does work. Try it yourself. $ which lsof /usr/sbin/lsof $ echo $PATH /usr/lib/qt-3.3/bin:/usr/kerberos/bin:/usr/lib/ccache:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/mikkel/bin Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: OpenPGP digital signature Url : https://www.redhat.com/archives/fedora-list/attachments/20090505/f90f609d... ------------------------------ Message: 9 Date: Tue, 5 May 2009 09:19:46 -0600 From: Kevin Fenzi <kevin(a)scrye.com&gt; Subject: Re: phoronix-test-suite for Fedora? To: fedora-list(a)redhat.com Message-ID: <20090505091946.1621acd4(a)ohm.scrye.com&gt; Content-Type: text/plain; charset="us-ascii" On Mon, 4 May 2009 15:22:07 -0700 Dave Stevens <geek(a)uniserve.com&gt; wrote: ...snip... > [dave@localhost ~]$ uname -a > Linux localhost.davedomain 2.6.23.17-88.fc7 #1 SMP Thu May 15 > 00:02:29 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux > [dave@localhost ~]$ > > > > So maybe I have to wait for F11 when I'm planning to upgrade anyway. Yeah. F7 is end of life and no longer supported. It does not get updates of any kind. ;( I would suggest you look at upgrading asap. > D kevin -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available Url : https://www.redhat.com/archives/fedora-list/attachments/20090505/bfb1b42d... ------------------------------ Message: 10 Date: Tue, 05 May 2009 16:37:18 +0100 From: "Sharpe, Sam J" <sam.sharpe+lists.redhat@gmail.com&lt;sam.sharpe%2Blists.redhat(a)gmail.com&gt; > Subject: Re: Where is lsof? To: "Community assistance, encouragement, and advice for using Fedora." <fedora-list(a)redhat.com&gt; Message-ID: <4A005D2E.8070501(a)gmail.com&gt; Content-Type: text/plain; charset=ISO-8859-1; format=flowed Mikkel L. Ellertson wrote: > Alan Evans wrote: > > On Tue, May 5, 2009 at 5:39 AM, Mike Cloaked wrote: > >> Usually a good way to find where a command is would be to use the > "which" > >> command. In this case: > >> [mike@gestalt ~]$ which lsof > >> /usr/sbin/lsof > > How is that going to work if /usr/sbin isn't already in your path? > > > It does work. Try it yourself. > > $ which lsof > /usr/sbin/lsof > $ echo $PATH > /usr/lib/qt-3.3/bin:/usr/kerberos/bin:/usr/lib/ccache:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/mikkel/bin You'll note that /usr/sbin *is* in your path and the man page for which says: DESCRIPTION Which takes one or more arguments. For each of its arguments it prints to stdout the full path of the executables that would have been exe- cuted when this argument had been entered at the shell prompt. It does this by searching for an executable or script in the directories listed in the environment variable PATH using the same algorithm as bash(1). So if you hadn't had /usr/sbin in your PATH, then "which lsof" would have returned nothing - so it isn't useful for this situation... [sam@sam ~]$ echo $PATH /usr/kerberos/bin:/usr/bin:/bin:/usr/sbin:/sbin [sam@sam ~]$ which lsof /usr/sbin/lsof [sam@sam ~]$ export PATH=/usr/kerberos/bin:/usr/bin:/bin:/sbin [sam@sam ~]$ which lsof /usr/bin/which: no lsof in (/usr/kerberos/bin:/usr/bin:/bin:/sbin) -- Sam ------------------------------ Message: 11 Date: Tue, 05 May 2009 17:49:17 +0200 From: Thorsten Leemhuis <fedora(a)leemhuis.info&gt; Subject: Re: kmod-nvidia yum update problem To: "Community assistance, encouragement, and advice for using Fedora." <fedora-list(a)redhat.com&gt; Message-ID: <4A005FFD.6050701(a)leemhuis.info&gt; Content-Type: text/plain; charset=UTF-8; format=flowed On 05.05.2009 15:54, Steve wrote: > I get this error when trying to update kmod-nvidia package: > > Test Transaction Errors: > file /lib/modules/2.6.27.21-78.2.41.fc9.x86_64/extra/nvidia/nvidia.ko from install of > kmod-nvidia-2.6.27.21-78.2.41.fc9.x86_64-173.14.15-1.fc9.12.x86_64 conflicts with file from package > kmod-nvidia-2.6.27.21-78.2.41.fc9.x86_64-173.14.15-1.fc9.5.x86_64 > > which appears to be telling me that it cannot upgrade because the package it is trying to replace has a file by the same name. Isn't that the point of an upgrade? > I assume I am misinterpreting this. No, you get fooled by yum-fedorakmod; just remove it; see last question on http://rpmfusion.org/FAQ HTH CU knurd ------------------------------ Message: 12 Date: Tue, 05 May 2009 11:49:59 -0400 From: William Case <billlinux(a)rogers.com&gt; Subject: Not getting clean shutdowns for FireFox and Epiphany To: Fedora List <fedora-list(a)redhat.com&gt; Message-ID: <1241538599.3301.17.camel(a)localhost.localdomain&gt; Content-Type: text/plain Hi; How do I set up rc6 or whatever, so that I get a clean shutdown for FireFox and Epiphany? FireFox is started by my session manager and I often use Epiphany -b as a specialized bookmark editor on my panel. Whenever I login to start a new session FireFox and Epiphany gives a standard warning/option of restoring my previous session. I want to eliminate those warnings without having to specifically close those programs before logging out. -- Regards Bill Fedora 10, Gnome 2.24.3 Evo.2.24.5, Emacs 22.3.1 ------------------------------ Message: 13 Date: Wed, 6 May 2009 01:56:42 +1000 From: David <bouncingcats(a)gmail.com&gt; Subject: Re: Selinux disallows read-only loop mount of a file, but only at boot [SOLVED] To: "Community assistance, encouragement, and advice for using Fedora." <fedora-list(a)redhat.com&gt; Cc: dwalsh(a)redhat.com Message-ID: <974cfff50905050856p72fc989frfd062b2ebf94bd18(a)mail.gmail.com&gt; Content-Type: text/plain; charset=ISO-8859-1 I'm attempting to mount a loop device (a ro file) at boot using fstab. My fstab entry works fine from the command line, but it fails at boot time due to a selinux avc error. I assume this is due to incorrect file context. The file is under a nonstandard top level directory, so I need to specifically assign it the correct file context, which I would do if I could figure out what it ought to be. Where do I look on the system to discover what is the correct file context required by mount at boot time? The file and context are: $ ls -lZ /HUGE/get/iso/Fedora-09-i386-DVD/Fedora-09-i386-DVD.iso -r--r----- root share unconfined_u:object_r:default_t:s0 /HUGE/get/iso/Fedora-09-i386-DVD/Fedora-09-i386-DVD.iso The fstab line is: /HUGE/get/iso/Fedora-09-i386-DVD/Fedora-09-i386-DVD.iso /mnt/Fedora-09-i386-DVD iso9660 loop,ro,gid=share 0 0 The command line that works is: # mount /mnt/Fedora-09-i386-DVD The boot-time error messages are: Mounting local filesystems: /HUGE/get/iso/Fedora-09-i386-DVD/Fedora-09-i386-DVD.iso: Permission denied [FAILED] Mounting other filesystems: /HUGE/get/iso/Fedora-09-i386-DVD/Fedora-09-i386-DVD.iso: Permission denied [FAILED] The dmesg error is: type=1400 audit(1241535886.437:4): avc: denied { read } for pid=1335 comm="mount" name="Fedora-09-i386-DVD.iso" dev=sdb2 ino=1922 scontext=system_u:system_r:mount_t:s0 tcontext=unconfined_u:object_r:default_t:s0 tclass=file My selinux policy is: # rpm -qa 'selinux-policy-targeted*' selinux-policy-targeted-3.3.1-132.fc9.noarch My selinux status is: # sestatus SELinux status: enabled SELinuxfs mount: /selinux Current mode: enforcing Mode from config file: enforcing Policy version: 22 Policy from config file: targeted My os is: # uname -r 2.6.25-14.fc9.i686 I have the following boolean unset because I wish to utilise selinux file context to restrict which files can be mounted: # getsebool allow_mount_anyfile allow_mount_anyfile --> off Interestingly, I did discover that the following command allows subsequent boot-time mounts to succeed: # chcon -t mount_exec_t /HUGE/get/iso/Fedora-09-i386-DVD/Fedora-09-i386-DVD.iso But I am unsure whether this is the correct solution. Where do I look on the system to discover what is the correct file context required by mount at boot time? ------------------------------ -- fedora-list mailing list fedora-list(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-list End of fedora-list Digest, Vol 63, Issue 22 *******************************************