Re: ACPI messages in syslog
by vs
----- Original Message ----
> From: Craig White <craigwhite(a)azapple.com>
> To: For users of Fedora <fedora-list(a)redhat.com>
> Sent: Wednesday, August 27, 2008 1:49:11 PM
> Subject: Re: ACPI messages in syslog
>
> On Wed, 2008-08-27 at 16:41 -0400, Mark Haney wrote:
> > Craig White wrote:
> >
> > > ----
> > > I'm not sure that noacpi is an option...perhaps you mean noacpi=1
> > >
> > > you can also boot with the param 'acpi=off' but that is what is known as
> > > the 'big hammer'
> > > http://fedoraproject.org/wiki/KernelCommonProblems
> > >
> > > Craig
> > >
> >
> > Okay, I've asked that question a dozen times on here, what's the option
> > to shut off acpi. I've been told 'noacpi' every time. Not 'noacpi=1'.
> > I've also been told acpi=off doesn't work/isn't used any more.
> >
> > Used to I'd add noacpi,acpi=off to my kernel boot line. Then I was told
> > acpi=off wasn't used (or whatever). So, now I'm really confused.
> ----
> I'm no expert - that's why I provided the link. acpi=off clearly is a
> valid option (they label it the big hammer)
You may need to pass additional options, or better yet disable at the BIOS. More info on this page:
http://www.lesswatts.org/projects/acpi/debug.php
--Victor
> Craig
>
> --
> 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
15 years, 8 months
question on a kernal "uhhuh" message
by Paul Allen Newell
While running a long "yum update", I got the following message in the
middle:
(367/406): cscope-15.6-2.fc9.i386.rpm | 141
kB 00:01
(368/406): gstreamer-p 86% | 20% |== | 57 kB/s | 192
kB 00:12 ETA
Message from syslogd@chowder at Aug 25 11:55:03 ...
kernel: Uhhuh. NMI received for unknown reason a1 on CPU 0.
Message from syslogd@chowder at Aug 25 11:55:03 ...
kernel: You have some hardware problem, likely on the PCI bus.
Message from syslogd@chowder at Aug 25 11:55:03 ...
kernel: Dazed and confused, but trying to continue
(368/406): gstreamer-plugins-base-0.10.19-2.fc9.i386.rpm | 929
kB 00:12
(369/406): exempi-2.0.1-1.fc9.i386.rpm | 297
kB 00:03
I am assuming that the second occurrence of "(368/406):
gstreamer-plugins-base-0.10.19.2.fc9.i386.rpm" indicates that it did
finish that rpm given that the rpm_debug_check and Transaction Test
seemed to have passed.
So, I am figuring this is my computer burping somewhere. Even though it
is trying to point me at my PCI bus, I do not know what test / diags I
should be running to find out if there really is a hardware problem and,
if so, where and then how to deal with it.
Any suggestions appreciated ... if I can provide any more info, please
let me know what would be helpful.
This is related to my prior email "update error on F9 -- round two" if
more context is needed.
Thanks,
Paul
15 years, 8 months
Leopard & Fedora 9 screen sharing?
by MacGuy
Here's what I'd like to do, I brand new to fedora and a user of mac os
x for the last 8 years (since OSX first came out), I've heard that
fedora is not as virus hungry as windows. I've got a windows machine
thats 2 years old and would like to see the desktop of the pc on my
mac as well as filesharing and complete control of the headless PC...
any good, simple instructions out there for doing this? Thank you....
and if fedora isn't suited for this, can someone tell me? Jeff
15 years, 8 months
Virus software? do I need it?
by MacGuy
Is virus software a must have? I'm trying Fedora 9, used Mac OS X for
years without it. What say you? Jeff
15 years, 8 months
Amarok, Songbird, and other similar players...
by Dan Thurman
This is a question that has been bugging me for awhile and
countless of hours trying to fix song tags that seems to be
overwritten, or so it seems.
From what I can tell, it *seems* to me that these players
might be using their own "database" to write over the tags
because no matter what I try via EasyTag, I could never get
these players to incorporate these updates into their database
or song lists.
Am I correctly assuming these players, when started for the
first time collects file tags, adds these tags into their database/list
and from then on "enforces" these tags "downward" and never
checks for updated tags to be incorporated as updates into the
database/list? It seems there is no mechanism to blow away these
player database (at least not from their menu options) other than to
either locate the database and delete them or to completely remove
and re-install the player application?
Many times these player databases/list are completely outdated and
appears in the list or is completely wrong as far as the way I want
them to appear.
It seems that these players are designed to be database/list centric?
Songbird on the other hand appears to keep it's own database/list
updates with "metadata" but does not actually update file tags
because I would edit and update the metadata then check the file's
song-tags and there would be no changes?
What do you do to resolve these issues?
Thanks in kind,
Dan
15 years, 8 months
Konqueror in SU mode
by Jim
FC9, Kde-4.1
How do I run Konqueror as Super User.
It is very different to run konquerorSU in KDE-4.1 than KDE 3.5.
If I open SU in Console and then try to run /usr/bin/konqueror, it won't
run.
15 years, 8 months
truecrypt
by Christopher Lemire
Has anybody been able to compile Truecrypt in F9? It is not very clear
on how to do it. The extracted directory has no make file but some of
the sub-directories do, so which make file should be ran?
--
Christopher Lemire <christopher.lemire(a)gmail.com>
Fedora 64 bit Linux Raid Level 1
15 years, 8 months
kernel update confuses nvidia drivers, where's error message?
by Dave Burns
Laptop is a Dell Latitude D630 with NVIDIA Quadro NVS 135M. X was
working yesterday, until yum update installed new kernels. At boot it
complains:
"checking for module nvidia.ko [failed]
nvidia.ko for kernel ***14-108.PAE was not found
the nvidia driver will not be unabled until" blah blah
* Where could I find the full text of that error message after boot?
Is it just gone? Not in dmesg or /var/log/messages or /var/log/X*.
After some groping I figured out that all's well if I re-executed
nvidia-xconfig and boot from a kernel that matches one of my installed
kmod-nvidia s. Yum updated my kernels, livna is behind on kmod-nvidia,
I think this was discussed here recently. I decided to put some of my
breadcrumbs in this post in case someone else ends up in the same boat
or I ever have to remember what happened.
# grep 'Aug 12 ' /var/log/yum.log|grep -e kernel -e Erase
Aug 12 22:47:13 Updated: kernel-headers-2.6.25.14-108.fc9.i386
Aug 12 22:47:39 Installed: kernel-PAE-2.6.25.14-108.fc9.i686
Aug 12 22:47:54 Installed: kernel-2.6.25.14-108.fc9.i686
Aug 12 22:48:15 Erased: kmod-nvidia-2.6.25.10-86.fc9.i686.PAE
Aug 12 22:48:16 Installed: kernel-PAE-2.6.25.14-108.fc9.i686
Aug 12 22:48:16 Installed: kernel-2.6.25.14-108.fc9.i686
So I reinstalled what got erased.
yum install kmod-nvidia
Now...
# tail -n5 /var/log/yum.log
Aug 12 22:48:15 Erased: kmod-nvidia-2.6.25.10-86.fc9.i686.PAE
Aug 12 22:48:16 Installed: kernel-PAE-2.6.25.14-108.fc9.i686
Aug 12 22:48:16 Installed: kernel-2.6.25.14-108.fc9.i686
Aug 13 09:16:10 Installed: kmod-nvidia-173.14.12-2.lvn9.i686
Aug 13 09:16:15 Installed:
kmod-nvidia-2.6.25.11-97.fc9.i686-173.14.12-2.lvn9.i686
But at boot it still complains.
Well, there is an nvidia.ko there now:
# rpm -q --filesbypkg kmod-nvidia-2.6.25.11-97.fc9.i686.i686
kmod-nvidia-2.6.25.11-97.fc9.i686
/lib/modules/2.6.25.11-97.fc9.i686/extra/nvidia
kmod-nvidia-2.6.25.11-97.fc9.i686
/lib/modules/2.6.25.11-97.fc9.i686/extra/nvidia/nvidia.ko
But it's not a match for the kernel I am currently using, which is:
# uname -a
Linux *** 2.6.25.14-108.fc9.i686.PAE #1 SMP Mon Aug 4 13:57:11 EDT
2008 i686 i686 i386 GNU/Linux
And...
rpm -qa|grep nvidia
xorg-x11-drv-nvidia-173.14.12-1.lvn9.i386
kmod-nvidia-2.6.25.11-97.fc9.i686-173.14.12-2.lvn9.i686
kmod-nvidia-PAE-173.14.12-2.lvn9.i686
kmod-nvidia-2.6.25.11-97.fc9.i686.PAE-173.14.12-2.lvn9.i686
kmod-nvidia-173.14.12-2.lvn9.i686
Is telling me that I have nvidia packages for kernel
2.6.25.11-97.fc9.i686 and 2.6.25.11-97.fc9.i686.PAE. So I should try
booting one of those kernels. Which worked. Don't forget to
nvidia-xconfig. And as always, with nvidia proprietary drivers
(installed from livna), the usual system/administration/display panel
doesn't work, instead use nvidia-settings from the command line.
buena suerte,
Dave
15 years, 8 months
nfs and iptables in FC9, please help!
by Hongwei Li
Hi,
I have just installed fc9 system with the following packages installed:
2.6.25.11-97.fc9.i686
rpcbind-0.1.4-14.fc9.i386
libtirpc-0.1.7-18.fc9.i386
nfs-utils-lib-1.1.1-3.fc9.i386
nfs-utils-1.1.2-2.fc9.i386
quota-3.15-7.fc9.i386
iptables-devel-1.4.1.1-1.fc9.i386
iptables-1.4.1.1-1.fc9.i386
iptables-ipv6-1.4.1.1-1.fc9.i386
...
If the firewall (iptables) is stopped, I can run nfs normally.
# rpcinfo -p
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100000 4 0 111 portmapper
100000 3 0 111 portmapper
100000 2 0 111 portmapper
100011 1 udp 875 rquotad
100011 2 udp 875 rquotad
100011 1 tcp 875 rquotad
100011 2 tcp 875 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 4 udp 2049 nfs
100021 1 udp 32769 nlockmgr
100021 3 udp 32769 nlockmgr
100021 4 udp 32769 nlockmgr
100021 1 tcp 32803 nlockmgr
100021 3 tcp 32803 nlockmgr
100021 4 tcp 32803 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 4 tcp 2049 nfs
100005 1 udp 892 mountd
100005 1 tcp 892 mountd
100005 2 udp 892 mountd
100005 2 tcp 892 mountd
100005 3 udp 892 mountd
However, If iptable is started, then nfs is failed. The followings are
some information:
# /etc/init.d/rpcbind restart
# /etc/init.d/nfs start
Starting NFS services: [ OK ]
Starting NFS quotas: Cannot register service: RPC: Unable to receive;
errno = No route to host
rpc.rquotad: unable to register (RQUOTAPROG, RQUOTAVERS, udp).
[FAILED]
Starting NFS daemon: ^C
(hang there, I have to interrupt it)
# rpcinfo -p
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100000 4 0 111 portmapper
100000 3 0 111 portmapper
100000 2 0 111 portmapper
In my iptable's setting I have enabled the following ports:
# iptables -L -n | more
...
okay tcp -- 128.0.0.0/8 0.0.0.0/0 tcp dpt:32769
ACCEPT udp -- 128.0.0.0/8 0.0.0.0/0 udp dpt:32769
okay tcp -- 128.0.0.0/8 0.0.0.0/0 tcp dpt:32803
ACCEPT udp -- 128.0.0.0/8 0.0.0.0/0 udp dpt:32803
...
okay tcp -- 128.0.0.0/8 0.0.0.0/0 tcp dpt:2049
ACCEPT udp -- 128.0.0.0/8 0.0.0.0/0 udp dpt:2049
...
okay tcp -- 128.0.0.0/8 0.0.0.0/0 tcp dpt:762
ACCEPT udp -- 128.0.0.0/8 0.0.0.0/0 udp dpt:762
okay tcp -- 128.0.0.0/8 0.0.0.0/0 tcp dpt:875
ACCEPT udp -- 128.0.0.0/8 0.0.0.0/0 udp dpt:875
okay tcp -- 128.0.0.0/8 0.0.0.0/0 tcp dpt:892
ACCEPT udp -- 128.0.0.0/8 0.0.0.0/0 udp dpt:892
okay tcp -- 128.0.0.0/8 0.0.0.0/0 tcp dpt:662
ACCEPT udp -- 128.0.0.0/8 0.0.0.0/0 udp dpt:662
okay tcp -- 128.0.0.0/8 0.0.0.0/0 tcp dpt:2020
ACCEPT udp -- 128.0.0.0/8 0.0.0.0/0 udp dpt:2020
...
and I have edited /etc/sysconfig/nfs to set ports:
RQUOTAD="/usr/sbin/rpc.rquotad"
RQUOTAD_PORT=875
LOCKD_TCPPORT=32803
LOCKD_UDPPORT=32769
MOUNTD_PORT=892
STATD_PORT=662
STATD_OUTGOING_PORT=2020
Did I miss anything to make nfs working normally with iptables? I used the
same setting in my FC6 system without any problem, but not lucky in fc9.
Can somebody give me help? Thanks a lot!
Hongwei Li
15 years, 8 months
strange error
by Beartooth
I have a popup saying
failed to get a TID: Incorrect path with ';' returned!
which gets no hits on google advanced linux
Is this part of the latest infrastructure precaution? Or
something wrong on my end??
--
Beartooth Staffwright, PhD, Neo-Redneck Linux Convert
Fedora 7, 8 & 9; Alpine 1.10, Pan 0.132; Privoxy 3.0.6;
Dillo 0.8.6, Galeon 2, Epiphany 2, Opera 9, Firefox 2 & 3
Remember I know precious little of what I am talking about.
15 years, 8 months