So, I have been having this same problem (not always, but very frequently),
ever since I upgraded to 2.6.24 kernels (all three released so far).
I put my trusty Thinkpad T61 on pm-hibernate, and it goes down peacefully:
however, within a second after everything shutting down, all lights off, it
revvs up and starts all over again. Regardless of whether the lid is closed or
This does not happen always.
Looking for last minute shopping deals?
Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping
I have an HP 5600 printer that worked just fine with my Fedora box until
I changed the black cartridge with a new HP one. On my windows machine,
I got messages about aligning the print cartridge, and everything worked
fine after that. However, using CUPS on my (much preferred) Fedora box,
the printout is always less than good quality, and the system complains
that the printer is low on ink (which it isn't, since its a new
cartridge and only used a few times so far)
The printout quality is a slightly slight shade of blue / black, rather
than the impressive deep black I get on that (horrible) Windows machine.
It seems to be due to the CUPS printer as my wife gets the same thing
and she has a Ubuntu machine
I first started dabbling with Linux about three years ago. The way I ended up using Fedora was it was the first link I clicked on that worked (I think it was FC3). Since that time, I have around fifteen machines running it. All of them run FC8 except my laptop which, as of yesterday, is running the beta of FC9.
With that said, I have never seen any other version of Linux running except Fedora. What's all the hype around Ubuntu? I realize I could download an install a copy but I never really saw any reason to since FCx seems to work great.
I'm not trying to start a battle of which is better...just trying to get an idea of why its seems so popular.
I'm working at a company that is planning to support customers using
Fedora Core 6. One such customer is using the 2.6.20-1.2925.fc6PAE
kernel. To support this customer we require the corresponding
I've scoured download.fedora.redhat.com for all kernels of all
releases we're interested in, but we've already found two instances
where the specific kernel version the customer is using cannot be
found there. One such kernel (220.127.116.11-32.fc6PAE) has been found at
an academic repository in Taiwan, but the hunt is still on for for
2.6.20-1.2925.fc6PAE. While it would be nice to have access to every
version of the kernel ever produced, it won't be strictly necessary
in the future.
If anyone has any information about and/or a copy of that specific
kernel-devel package (2.6.20-1.2925.fc6PAE), I'd greatly appreciate
Swiss Army Knife
Cell - 408.621.3193
Web - www.hypersphere.org
Home - 404.550.6038
I recently upgraded from fc7 to fc8, about a week ago.
Today, my gdm login is busted. After I enter my user name and password,
gdm just hangs, and never starts up the desktop.
I have to boot the computer into init 3, login to a shell, then run startx.
I do know what I could have done to break this.
I no longer have a "login screen" configuration entry in
system->administration, if that means anything to anyone.
I uninstalled and reinstalled gdm, no luck.
Same issue with any login, including root.
-----BEGIN PGP SIGNED MESSAGE-----
I have just yum installed cinerella and tried to use it:
cinelerra: symbol lookup error: /usr/lib/libavcodec.so.51: undefined
I asked from where this library was installed:
$ rpm -qf /usr/lib/libavcodec.so.51
This package was installed for "dependency" with cinelerra!!!
What can I do.
Thanks for attention.
UFR de mathématiques et informatique
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 44 55 35 61
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
I noticed today in my terminal window I now have a host name of "bogon". I
had never set a hostname for my Fedora8 home system. I can see from my
logwatch and cron system mails that the delivery to this host name started
March 25th but none of my mails shows anything that seems relevant to what
has set this hostname. Oddly on the 26th the system mails were addresses
again to localhost.localdomain but again reverted on the 27th to being
addresses to bogon. I have checked the man pages on the hostname command to
locate where the name is defined. Have checked the files /etc/host,
/etc/hosts.conf, /etc/hostname (does not exist), /etc/nsswitch.conf, ... but
this name does not show in any of the files I have looked at so far. Any
ideas where to look further? I am now wondering whether my system has been
compromised somehow... Googleing the word bogon shows me the meaning of of
bogon which does not seem helpful in this case.
Checking /var/log/messages-20080330 shows the use of this hostname with a
reboot I had done on the 24th. Still cannot see where or how this was set.
my bad. there is an additional step that has to be done tha t i left out. my
apologies. once you've found that you do have the lvms with the:
cmds... the lvm(s) might be in an inactive state. if you do a "ls /dev" and
you see that you have "/dev/VolGroup00" or something to that effect
depending on how you named your lvms... you're ok. if not, then you simply
need to activate the lvms by doing:
lvm vgchange -ay
this will go ahaead and set the lvm(s) to an active state, where it will
then show up under the "/dev" dir...
the rest of the steps i provided should work ok..
Ran into an interesting issue during the past week, and figured I'd post the
issue, and solution here in case it might come in handy for someone else...
The laptop was running, but it was left on with the lid closed for a day or
so.. when powered up, the laptop went into a state saying it couldn't find
the mounts... hmm.. shouldn't have thought this could happen. figured the
drive might screwing up, so i reinstalled FC8.
after a few hours, got everything back.. went and plugged the laptop into a
power strip that had a short..!! ouch, saw the same behavior.. got sort of
nervous, but thought it should be ok (hopefully!) so after another
reinstall, got to really wondering what was really going on... didn't think
about it.. the laptop was working.. things were cool.. for a day! and after
closing the lid, and then reopening.. after another day or so. saw the same
here's what i was seeing:
Filesystemtype is ext2fs, partition type 0x83
"VolGroup00" using etadata type lvm2
2 logical volumes in volume group "VolGroup00" now active
VFS: Can't find ext3 filesystem on dev dm-3
mount: error mounting /dev/root on /sysroot as ext3: Invalid argument
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot: mount failed: No such file or directory
at this point, talked to a few people, and started thinking that somehow the
disk was getting, had gotten corrupted.
started to try to see what the drive had, if anything!
poped in the FC8 rescuedCD, and went to work..
ran the cmds:
since i had installed using the defaults for FC8 LVM, the drive showed that
it was basically ok.
went ahead and ran fdisk /dev/sda and saw that i indeed had my two
partitions /dev/sda1, /dev/sda2
so at this point..
i did a
followed by a
mount /dev/VolGroup00/LogVol00 /mnt/sysimage
this worked, and got me to a point where i could hopefully fix/repair
whatever errs might be on the drive...
i then ran
e2fsck -y /dev/VolGroup00/LogVol00
after a little hope.. and an amount of time as the system did it's thing, it
came back saying how many sectors where corrected, etc...
i then rebooted, and the laptop was back up/running as it should!
feel free to add to this if you have useful information, or additional
insight that you want to share.
What seems to have happened to xinetd in F8 ? I have migrated a server
from FC2 to F8 and most things went over fine, but we have one particular
dedicated socket service that I can't get working. It used to have its
"config" file in /etc/xinetd.d and worked just fine, but I can't find
xinetd on F8 - what is the equivalent ?
Matthew Saltzman said
Pidgin needs something in libnm_glib.so.0, which is
NetworkManager-glib. This doesn't sound like such a
great thing, but
evolution also has that requirement.
If it bothers you, file a Bugzilla entry suggesting
that the relevant
functions be broken out of NetworkManager-glib.
You should be able to remove other NetworkManager
removing NetworkManager-glib. You should also be able
to just shut it
off (/sbin/service NetworkManager stop;
stop; same for NetworkManagerDispatcher--the first
stops it running now,
the second prevents it from starting on boot).
I don't really understand yum's view of dependencies.
The logic of
removing a package and everything it depends on, and
depends on those packages, etc., escapes me. Use
rpm to remove
packages if you don't want yum to run amok deleting
 I could understand removing a package and
everything it depends on
that doesn't, in turn, have something else depending
on it. But this
way, it seems like removing almost anything can end up
ripping most of a
functioning system out by the roots.
Clemson University Math Sciences
mjs AT clemson DOT edu
Thanks I will fool with removing that.
chkconfig NetworkManager off
chkconfig NetworkManagerDispatcher off
chkconfig network on
service NetworkManager stop
service network restart
at this point, system-config-network will work just
like it always has.
NetworkManager is useful when you are using wireless
or just dhcp but
'network' service works fine with dhcp too.
Thanks. I did those commands and it seems to be
working fine. That is the way I ran in fc7. I guess a
"yum upgrade" would have avoided the whole thing. I
still have the fc7 partition so, when I am comfortable
in fc8, I may run the upgrade to compare the