Fedora Linux Support Community & Resources Center
  #1  
Old 27th October 2009, 07:12 PM
AdamW Offline
Fedora QA Community Monkey
 
Join Date: Dec 2008
Location: Vancouver, BC
Posts: 4,204
linuxfedorafirefox
Warning: be careful using yumex to update F12

Just a general warning - it's come to light in a couple of threads that if you use yumex to update a Fedora 12 Beta installation, it seems to have trouble updating the kernel package, and leaves the updated kernel broken. If you're stuck in this situation, remove the new kernel package and re-install it using yum or PackageKit, that should make it work properly. If you've installed F12 Beta but haven't updated yet, please update with yum or PackageKit, not yumex.

Thanks!
__________________
Adam Williamson | awilliam AT redhat DOT com
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
  #2  
Old 27th October 2009, 08:44 PM
ovadyah Offline
Registered User
 
Join Date: May 2007
Location: 30.5N 90.1W
Age: 63
Posts: 301
linuxfedorafirefox
Thanks for this update. I have done as prescribed and the new kernel is working, it is working as the old one did...no NM and I am getting the same boot error as I posted in the other thread.

""WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d"

Thanks for all the help and the progress I have made.
__________________
Registered Linux User #452472

Homebuilt = athlon II x2 F21
Dell Inspiron = Sempron 140 W8
  #3  
Old 27th October 2009, 09:16 PM
Dan Offline
Administrator
 
Join Date: Jun 2006
Location: Paris, TX
Posts: 23,279
linuxfedorafirefox
Adam, this could nail a lot of folks, so I'm adding this to an announcement.
  #4  
Old 27th October 2009, 09:47 PM
flokip Offline
Registered User
 
Join Date: Aug 2008
Posts: 101
linuxfedorafirefox
I did file bug
Reported: 2009-09-16
https://bugzilla.redhat.com/show_bug.cgi?id=523644
  #5  
Old 28th October 2009, 02:54 AM
ryptyde Offline
Registered User
 
Join Date: May 2005
Location: Tragic City, Michigan USA
Posts: 1,647
linuxfedorafirefox
Had the yumex problem with the kernel update and removed the kernel then done yum update and it fixed the problem.

Before reinstalling the kernel it would boot to a black screen to an unresponsive blinking cursor and then doing Ctrl+Alt+F2 would get me to a text login. Entering startx would error out with no suitable screens.

I would have never guessed that yumex was the culprit and it does appear to boot quicker too!
  #6  
Old 28th October 2009, 04:22 AM
VernDog Offline
Registered User
 
Join Date: Aug 2009
Posts: 313
linuxfedorafirefox
I don't even know what "yumex" is. If fact I get 'Command not found' when trying to find help. I have seen several references about it and figured I don't need it.
  #7  
Old 28th October 2009, 04:23 AM
Demz
Guest
 
Posts: n/a
windows_98_nt_2000firefox
http://www.yum-extender.org/blog/
  #8  
Old 28th October 2009, 12:59 PM
mit Offline
Registered User
 
Join Date: Jun 2004
Posts: 233
linuxfedorafirefox
Check here for details about the issue

http://www.yum-extender.org/blog/200...xtender-2-9-x/
  #9  
Old 28th October 2009, 03:54 PM
robatino Offline
Registered User
 
Join Date: Feb 2004
Posts: 849
linuxfedorafirefox
Quote:
Originally Posted by ovadyah View Post
Thanks for this update. I have done as prescribed and the new kernel is working, it is working as the old one did...no NM and I am getting the same boot error as I posted in the other thread.

""WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d"
The file /etc/modprobe.conf isn't even supposed to exist. Do an ls -l on it to see when it was created and if it's a zero-byte file. Also run "rpm -qf /etc/modprobe.conf" to see if it's owned by any package. If not, you should be able to remove it to get rid of the error message. I've seen the same problem with this file being created at install time (not with F12 Beta, but with F11, I think). No one has figured out why this happens occasionally or what is responsible for creating it.
  #10  
Old 28th October 2009, 04:25 PM
ovadyah Offline
Registered User
 
Join Date: May 2007
Location: 30.5N 90.1W
Age: 63
Posts: 301
linuxfedorafirefox
Quote:
Originally Posted by robatino View Post
The file /etc/modprobe.conf isn't even supposed to exist. Do an ls -l on it to see when it was created and if it's a zero-byte file. Also run "rpm -qf /etc/modprobe.conf" to see if it's owned by any package. If not, you should be able to remove it to get rid of the error message. I've seen the same problem with this file being created at install time (not with F12 Beta, but with F11, I think). No one has figured out why this happens occasionally or what is responsible for creating it.
Thanks, it was as you said. I do see the error in the boot messages, can I get that to clear some way? I tried rebooting twice and it is still there.
__________________
Registered Linux User #452472

Homebuilt = athlon II x2 F21
Dell Inspiron = Sempron 140 W8
  #11  
Old 28th October 2009, 04:27 PM
robatino Offline
Registered User
 
Join Date: Feb 2004
Posts: 849
linuxfedorafirefox
Is it in fact a zero-byte file? Does the modification time tell you whether it was created at install time? Is it owned by any package? Did you delete the file as I suggested, and if so, is it being recreated each time you boot?
  #12  
Old 28th October 2009, 05:52 PM
ovadyah Offline
Registered User
 
Join Date: May 2007
Location: 30.5N 90.1W
Age: 63
Posts: 301
linuxfedorafirefox
It was a zero byte file, I did not really note the time of creation, it was not owned by any package, I deleted it and it has not re-appeared. The error message in the boot log is there each time I boot. Perhaps there is a way to clear that?
thanks again.
__________________
Registered Linux User #452472

Homebuilt = athlon II x2 F21
Dell Inspiron = Sempron 140 W8
  #13  
Old 28th October 2009, 06:04 PM
robatino Offline
Registered User
 
Join Date: Feb 2004
Posts: 849
linuxfedorafirefox
I don't understand why the message would appear if the file it refers to doesn't exist anymore. After I deleted this file on my machine, the error message disappeared.
  #14  
Old 28th October 2009, 06:25 PM
ovadyah Offline
Registered User
 
Join Date: May 2007
Location: 30.5N 90.1W
Age: 63
Posts: 301
linuxfedorafirefox
Quote:
Originally Posted by robatino View Post
I don't understand why the message would appear if the file it refers to doesn't exist anymore. After I deleted this file on my machine, the error message disappeared.
It still appears, however it is before everything else, even before Welcome to Fedora. It is like it is stuck in the header???????? I do not get the error down in the boot log steps, as I did before.
__________________
Registered Linux User #452472

Homebuilt = athlon II x2 F21
Dell Inspiron = Sempron 140 W8
  #15  
Old 28th October 2009, 06:29 PM
robatino Offline
Registered User
 
Join Date: Feb 2004
Posts: 849
linuxfedorafirefox
If you're talking about graphical boot, I disabled that by deleting "rhgb" and "quiet" from the kernel lines in grub.conf, so maybe that's why I don't see the same problem.
 

Tags
careful, f12, update, warning, yumex

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
yumex won't update RedAnarchy Using Fedora 9 20th July 2008 08:57 AM
after update yumex cannot run leorex Alpha - Beta (Fedora 9 Only) 1 17th April 2008 11:23 AM
yumex and livna python warning marko Using Fedora 0 7th November 2006 02:33 AM
Latest update to pango - be careful! mcwall1064 Using Fedora 14 15th October 2006 03:12 PM
yumex update erros fizy Using Fedora 9 10th March 2006 05:52 PM


Current GMT-time: 21:17 (Friday, 24-10-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat
Hawarden Photos - Nanchang Instagram Photos - Antipolo Photos