Broadcom & limewire
 

Well i found the broadcomxxx crap in the add/remove software... i was hopping that after i unpackaged them it would magically work... wifi button still does not light up and still cant get wireless working... i dont know where to go from here or what to do... would someone please help?

During The Un-Packaging of limewire it says cannot resolve dependencies, it does this alot with software i am install, why could this be....

also, after each time i unpackage software and reboot there is a new boot menu item in the grub older versions along with windows xp home which i still use... how do i remove the old versions of fedora core that i am no longer using...

So your wireless card is a Broadcom one? I don't have much experience with those, but maybe you'll need to make sure you have appropriate kernel module loaded etc. after you've installed the driver package. Did you use Google to find out if there are other people who have solved that problem?

It means that (for example) if you want to install Limewire you'll need to install some other packages (which Limewire needs), but those packages cannot be found in the reposities you have configured. My first try to solve this was add more reposities/mirrors to your configuration. If you're using Fedora Core, you can use yum to install software, so add more Yum reposities. Instructions for this can be found by searching here at LQ, I'm pretty sure, so I'm not going into that (it's a matter of adding files to yum's repo directory). When the needed packages (dependencies) are found on some reposity, the problem disappears.

You'll need to become root to do this. cd into /boot and see what files you've got there - you should have multiple files like vmlinuz-version, System.map-version etc..now you must know the number of the kernel you're using (the latest = the greatest, usually). Leave those files where they are (every file that has the version number), and remove the files that have older version numbers. Files without version number must be left where they are. After this cd into /boot/grub and open the file menu.lst with some text editor; there are the sections for each kernel (items in the boot list). Read the comments to get to know how the file is maintained (probably automatically), and after that remove the sections that define the older kernels, leaving the newest entry (that you have tested so it works) at it's place.

Actually the safest way is to first edit /boot/grub/menu.lst by commenting the older kernel entries out, then reboot and see if the list is fine - boot the kernel entry that is there and see that it works. If you're unable to boot or made some mistake, you can still boot (each one of) the kernels since you haven't deleted anything. After this you can safely remove the out-commented older kernel entries from the file or leave them there (doesn't matter, just makes the file bigger/smaller), and only then remove the older kernel files from /boot.

EDIT: note that the kernel files don't take much space on the harddisk, especially if you have a modern big disk, so it's safe to leave the files there, just in case. So you don't actually have to do anything else but comment out the older kernels' lines from the grub's config file, thus keeping your system surely in a working state.

That was possibly the most clear response I have had. Thank you very much. I really appriciate you taking the time to respond with the quality of respons you wrote. Excellent, and very helpful...