World Updating 101 Pre 4.2 -- Read before World Updating --

[PennyRoyal]

Still no luck. This is sooooo frustrating. I can boot the Live DVD (SL4) with "xdriver=nv" and all is fine. If I let the DVD boot default to the nvidia driver, I get a black screen w/blinking curser and all is still. SL3.5 boots perfect... SL3.5.1 & SL4 will not. What am I missing?

New question: Is there a way to install SL3.5 (w/nvidia) THEN update all the programs (ie: OOo 3.0, KDE...) without updating the kernel? Do I really need to change the kernel if I'm not changing any hardware? (PS: the CLI terrifies me... but I'm not going to let it win!) Thanks for any help given...

[wolfden]

Please start a new topic for support

Use the entropy section of the forum

[wolfden]

What about when doing an update destroys your entire system? I started revdep-rebuild 4 hours ago and it's still listing the thousands of files that are not owned by any package and are broken. I've had this happen over and over and I'm growing tired of having to restore the file system and start over - especially since every incident fails to provide any clues to me about why this is happening.

revdep rebuild is not for entropy

if you run into disaster - start a support topic and provide as much info as possible - hardware and log files

[wolfden]

I added a part to entropy wiki called: Fresh Install - What to do?
http://wiki.sabayonlinux.org/index.php? ... t_to_do.3F
hopefully this will help people get started with the entire process

[wolfden]

Updated it again:

Getting reports that Grub issues are hitting a lot of people also, luckily you have some options.
1. The livedvd that you used to install with has in the installer an option to just reinstall grub, so boot up the livedvd, run the installer till you get to reinstall boot loader.
2. I highly recommend Super Grub Disk, it's a wonderful tool to restore Grub, saves a lot of headaches http://www.supergrubdisk.org/ Download the iso, burn it, boot it up, fix, reboot. Keep it safe as you will probably use it again.
3. Advanced users can chroot in and reinstall grub - dave_64, one of the IRC helpers says the archlinux wiki is good guide for this http://wiki.archlinux.org/index.php/Reinstalling_GRUB << he said he never chrooted before and was able to by following that guide.

I'm not sure what the prevention for this is, common sense tells me to reinstall grub before rebooting. I have a different grub so I can't test this out. I'm guessing the grub-install command

Code: Select all

grub-install /dev/sda

If someone cares to enlighten the subject, please do

[speckles]

If you upgrade to kernel 2.6.29 and have ext4, you have to edit you /etc/fstab file and remove the extents option as it is now default

I ran into this bug too. So if extents is turned on by default for ext4 on 2.6.29, then why in the world would it matter if it were also specified in fstab? Explicity telling the kernel I want something when the kernel is already doing what I want logically should not seem to result in any problems.

[wolfden]

that is something you would have to ask the kernel devs about - we have no control over that but to adjust accordingly to what they do

[eshum]

"1. The livedvd that you used to install with has in the installer an option to just reinstall grub, so boot up the livedvd, run the installer till you get to reinstall boot loader." I did not see this help notice . However this exactly how I fixed the grub problem after updating and everything is operating just fine.

ed

[juancholo50]

I upgraded without problem, but as in all the distros that come out each time a new. version is always recommended to perform a clean installation from scratch

[dagurasu]

Gentoo has had module-rebuild for awhile. It rebuilds all kernel modules not provided by the kernel package. There can be several. Virtualbox-modules is another example. You can still emerge this tool and just use it to see what needs to be reinstalled. It gives you a 5 second countdown before actually doing anything.