Alpha worked, Beta now does not

[ovadyah]

My machine now is nearly useless. I did all the updates and now the NM is not working (does not even find the hardware!...... sound is not working on boot up......this all seems to be from the update(s) to the latest kernel (2.6.31.5-96.fc12.x86_64) --

I can go back to the first kernel I installed(2.6.31.1-56.fc12.x86_64) and I can get on the internet but still cannot get NM to work. I have to manually set it up each time.

So, now the least of my problems is the ati driver issue. On this machine Alpha worked very well, Beta does not work ... much.....still working on it.:confused:

[Dies]

My machine now is nearly useless.

And that's just fine isn't it?

Right, because you wouldn't be running 'alpha' or even 'beta' releases as your main or only system, right? Nah, that would just be silly, to put it kindly.

At least you can always just boot to your main system and use that for filing bugs, checking the mailing list, getting your work done, etc. Right?

:)

[ovadyah]

Absolutely correct :D
I am having a great time with this one. Learning a lot and still able to use the F12 machine cause of what you fine folks have taught me.

[AdamW]

what exactly do you mean by you 'have to manually set it up each time'?

What's your sound hardware? (output of alsa-info.sh --no-upload)

[ovadyah]

thanks Adam for your replies, here is more of my detective work:

Old kernel = 2.6.31.1-56.fc12.x86_64
New kernel = 2.6.31.5-96.fc12.x86_64

OK, the network will NOT work at all in the new kernel (along with several other things... see bellow), but I can get it to work in the old kernel by manually activating each time:

Menus/System Administration/Network Device Control
Click Configure eth0
Activate.

It always un-activates each time after a reboot. However, in the Network Device Control edit of eth0 it is checked to "Activate Device when Computer Starts"

I believe that the majority of problems I am seeing in the new kernel (sound not woking, CD drive not seen, eth0 not seen) are related to modules not loading

Modprobe Errors in /var/log/messages:
ct 27 09:31:55 ovadyah modprobe: FATAL: Could not load /lib/modules/2.6.31.5-96.fc12.x86_64/modules.dep: No such file or directory
Oct 27 09:31:55 ovadyah modprobe: FATAL: Could not load /lib/modules/2.6.31.5-96.fc12.x86_64/modules.dep: No such file or directory
Oct 27 09:31:55 ovadyah seahorse-daemon[1539]: init gpgme version 1.1.8
Oct 27 09:31:56 ovadyah modprobe: FATAL: Could not load /lib/modules/2.6.31.5-96.fc12.x86_64/modules.dep: No such file or directory
Oct 27 09:31:56 ovadyah restorecond: Unable to watch (/home/ovadyah/public_html/*) No such file or directory
Oct 27 09:31:56 ovadyah modprobe: FATAL: Could not load /lib/modules/2.6.31.5-96

boot.log is attached with similar errors.

Sound IS working in the OLD kernel, but not the new. I bet it has something to do with modules.

Thanks for your help.

[AdamW]

those messages don't look right. Um. Someone in another thread had a problem installing the new kernel with yumex - do you use yumex?

[ovadyah]

Yes, I do use yumex.... had noticed a new version so I believe I may have updated with it.

I just noticed this error in the boot messages for the OLD kernel. I just used yum to update with today's updates.

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

[AdamW]

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

That one's pretty harmless, you can ignore it.

Sounds like you got bit by the yumex bug, then. The procedure that fixed it for the others was to remove the new kernel package and then re-install it using yum or PackageKit rather than yumex. Can you try that and see if it does the trick?

[ovadyah]

Yep, It worked fine. I posted to the yumex warning thread. I am up and working on the NetworkManager problems now. Still have to manually start the eth0 to get network. I cannot get the NM applet to work.
Video drive is fixed per your instruction.

Thanks as all ways.

[AdamW]

no problem. so, you're not seeing the networkmanager applet at all? what happens if you run 'nm-applet' in a console? have you checked that the notification area hasn't been removed from your panel somehow?

[ovadyah]

I have tried to run 'nm-applet and the reply is "-bash: nm-applet: command not found"

All the other info on my network problems are in post #5 of this thread.

I have the notification area in place.

[hceylan]

You seem to be missing the NetworkManager isnatllation.

Restore your internet connection some way (ex: with Network settings) or get the rpms onto a removable media

go to console and install NetworkManager rpms using yum...

[ovadyah]

Thanks - I did look, and it appeared that NM was there, so I went ahead and re-installed it. Still unable to get it going. At least I can get the network going so as to have the internet and updates, etc.

[AdamW]

Check if NetworkManager-gnome is installed, that's the package that nm-applet is a part of.

[ovadyah]

Adam, your last post set off a light bulb in my head :eek:
I remembered that I had installed KDE desktop -(standard package) I believe and I noticed when the transaction was running it (I think I used Yumex) removed a huge number of packages. If I am not mistaken, open office and a lot of other stuff I did not even check out also disappeared.

This may have been about the same time as I got the updates (and the broken kernel install) with yumex.

I shall look for NetworkManager-gnome --- asap. If it is not there would it install with a re-install of gnome desktop???? Or, should I try some other way?

Hope I can help.

[AdamW]

you can reinstall it with just 'yum install NetworkManager-gnome', but if yumex really did wipe a bunch of packages, you may be missing other stuff too. It may be worth doing a reinstall.

[ovadyah]

Thanks for all the help. I re-installed NM-G and all seems back in order. I was wondering about advice on installing first from a KDE live disk and then adding to that installation whether it be more KDE or Gnome?

[AdamW]

I can't really tell you what'd be best, to be honest - I don't use KDE on my main system at all, when I want to test how KDE is looking I boot up a VM. So can't help, I'm afraid.