Remember when you change kernels - your modules/drivers must match new kernel.
For example - I upgrade and before I reboot I want to make sure of a few things
- Code: Select all
wolf64 wolfden # uname -r
2.6.28-sabayon
oh look, I has a new kernel now
Did my nvidia-driver update? Probably not, but I can use- Code: Select all
equo search nvidia-driver
to see what I do have installed - x11-drivers/nvidia-drivers-96.43.09-r10#2.6.27-sabayon << DO NOT WANT
let's make sure my kernel is eselected first - if it isn't than it is pointless to rebuild modules as you would be building on the wrong kernel
- Code: Select all
wolf64 wolfden # eselect kernel list
Available kernel symlink targets:
[1] linux-2.6.27-sabayon
[2] linux-2.6.28-sabayon *
sweet, it is eselected to the right kernel, if it wasn't I would have had to eselect kernel set 2
so I better
- Code: Select all
equo install nvidia-driver
to get x11-drivers/nvidia-drivers-180.41-r1#2.6.28-sabayon << DO WANT
now lets make sure eselect is point to right opengl
- Code: Select all
wolf64 wolfden # eselect opengl list
Available OpenGL implementations:
[1] nvidia *
[2] xorg-x11
woot! and it is set to my nvidia, if it wasn't, I would of had to eselect opengl set 1
2.6.28-sabayon and x11-drivers/nvidia-drivers-180.41-r1#2.6.28-sabayon
Notice my Kernel matches my driver to same kernel version. This is critical, otherwise you are gonna boot up to a blinking cursor and run around screaming I Need Support!!!
This is not just an entropy or Sabayon Linux thing. Every time you change kernel in a distro you must rebuild the drivers/modules to work with your new kernel. This includes all hardware like cams, video, any thing that is a module.
We are seeing some weird thing with udev being removed from startup and this is bad bad bad, so before rebooting, make sure udev is in your startup by doing
- Code: Select all
wolf64 wolfden # rc-update show
system-tools-backends | default
mount-ro | shutdown
sshd | default
dmesg | sysinit
hotplug | boot
serial | boot
x-setup | boot
keymaps | boot
syslog-ng | default
mdadm | default
local | nonetwork default
portmap | default
udev | sysinit
hwclock | boot
termencoding | boot
fbcondecor | default
savecache | shutdown
sabayon-mce | boot
fsck | boot
consolefont | boot
swap | default
root | boot
dbus | boot
NetworkManager | default
modules | boot
devfs | sysinit
xdm | boot
vixie-cron | default
mtab | boot
samba | default
sysctl | boot
device-mapper | boot
alsasound | default
avahi-daemon | default
killprocs | shutdown
procfs | boot
hald | boot
localmount | boot
netmount | default
cupsd | default
hostname | boot
nfs | default
net.lo | boot
dhcdbd | default
urandom | default
lvm | boot
bootmisc | boot
wolf64 wolfden #
Look for udev and if you don't see it
- Code: Select all
rc-update add udev sysinit
if you reboot without udev starting, you won't get far as everything is going to fail and you will than be reading chrooting 101 to save your install
and always always always
- Code: Select all
equo conf update
and deal with the config files, you should look over this list and pay attention, most of time -5 is going to work fine, but if you suddenly boot to a different login manager, than you know you overwrote a config file you shouldn't of like /etc/conf.d/xdm, some others I do not over write are /etc/conf.d/hostname and /etc/conf.d/hwclock, there is a couple others but I'm not going to list em all, you should get to know our config files.
Another thing with Networking breaking:
viewtopic.php?f=52&t=16007
viewtopic.php?f=52&t=16086
Hopefully in the future as entropy develops, some of these concerns will be address and make things even smoother for ya. Fabio is always making it better and easier for you, but in the meantime, keep these things in mind when you see a kernel change. Knowledge is power and the more you know what is changing in your system the better.
3/25/09 Update
We have a new issue now with 2.6.29
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
so you will have a line like
- Code: Select all
/dev/sdb8 / ext4 extents,user_xattr,noatime 1 1
THIS IS WRONG NOW
You need to change it so it looks like:
- Code: Select all
/dev/sdb8 / ext4 user_xattr,noatime 1 1
THIS IS CORRECT
if you don't remove the extents option, your system will be stuck in Read Only mode and nothing will start up, you will have to reboot to the previous kernel to edit the /etc/fstab file than reboot back to .29
Edit 3/27/09
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
Edit 3/29/09
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
