- 1 04/07/13 gcc-config: error: could not run/locate 'gcc'
- 2 03/16/10 URL Change for Entropy Repository
- 3 02/12/10 Mandatory Entropy Update and Wireless KDE4.4
- 4 10/14/09 Slow Speeds with Limbo Repo
- 5 9/8/09 Gnome 5.0 and jpg
- 6 8/3/09 Late Bugs Fixes
- 7 6/20/09 Mibbit WebChat
- 8 4/29/09 Adding Users
- 9 3/29/09 Grub Issue
- 10 3/27/09 Entropy Wiki Addition
- 11 3/25/09 ext4 with kernel .29
- 12 3/21/09 Update Information
04/07/13 gcc-config: error: could not run/locate 'gcc'
Simply reinstall gcc. And run the second line in addition, if you use 64Bit and reinstalling don't solve your issue:
# equo install gcc # gcc-config x86_64-pc-linux-gcc-4.7.2
03/16/10 URL Change for Entropy Repository
Please see this topic http://forum.sabayon.org/viewtopic.php?f=76&t=17144&sid=0223fbd47ed1bc0ccd777fdcdce290f3 it has a working repository config file. This effects all versions pre 5.2
02/12/10 Mandatory Entropy Update and Wireless KDE4.4
Wireless issues after KDE 4.4 update Friday, February 12, 2010 5:37 AM With KDE 4.4, we had to drop the old Plasma-based Network Manager tool, you must install knetworkmanager or nm-applet (GNOME)
Entropy update required Friday, February 12, 2010 5:34 AM If you are having download problems, they may be caused by your Entropy version not up-to-date. You can solve this by updating Entropy this way: equo update && equo install entropy equo --nodeps && equo upgrade
10/14/09 Slow Speeds with Limbo Repo
You may notice a big slow down with entropy and Limbo Repo, please add this mirror under your existing Limbo line
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayonlinux.org/entropy%7Chttp://pkg.sabayonlinux.org
so it should look like
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayonlinux.org/entropy%7Chttp://pkg.sabayonlinux.org repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://na.mirror.garr.it/mirrors/sabayonlinux/entropy/%7Chttp://na.mirror.garr.it/mirrors/sabayonlinux/entropy#bz2
now you should have good speeds again. You may have to put a # in front of the top one to force equo to use garr only. example:
# repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayonlinux.org/entropy%7Chttp://pkg.sabayonlinux.org repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://na.mirror.garr.it/mirrors/sabayonlinux/entropy/%7Chttp://na.mirror.garr.it/mirrors/sabayonlinux/entropy#bz2
Another thing you can do is make it look like:
repository|sabayon-limbo|Sabayon Linux Limbo Repository|http://pkg.sabayonlinux.org/entropy%7Chttp://pkg.sabayonlinux.org repository|sabayon-limbo||http://na.mirror.garr.it/mirrors/sabayonlinux/entropy%7C
You will still get the update db from pkg site, but it should download the packages from garr. I leave the choice up to you.
9/8/09 Gnome 5.0 and jpg
Gnome 5.0 having jpg issues - fix is to reinstall gtk+
#equo install gtk+
also run as user
$ update-mime-database ~/.local/share/mime/
8/3/09 Late Bugs Fixes
Make sure before you install 5.0 that you run the Update Installer. The button is found by launching the Install to Disk. It will download the latest fixes and restart the install process.
6/20/09 Mibbit WebChat
Freenode had banned mibbit, which is the webchat that we had been using for Live Help. Please use an irc client to connect to live help or you can use the Freenode webchat - channel #Sabayon
4/29/09 Adding Users
Please see this thread on kuser and gnome user I find doing the command line method the easiest
# useradd -m -G users,wheel,audio -s /bin/bash john # passwd john Password: (Enter the password for john) Re-enter password: (Re-enter the password to verify)
3/29/09 Grub Issue
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
# grub-install /dev/sda
3/27/09 Entropy Wiki Addition
hopefully this will help people get started with the entire process
3/25/09 ext4 with kernel .29
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
/dev/sdb8 / ext4 extents,user_xattr,noatime 1 1
THIS IS WRONG NOW
You need to change it so it looks like:
/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
3/21/09 Update Information
We are seeing plenty of people having problems with updates as they don't realize what happens when there is a kernel change.
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
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
# 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
wolf64 wolfden # eselect kernel list Available kernel symlink targets:  linux-2.6.27-sabayon  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
# 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
wolf64 wolfden # eselect opengl list Available OpenGL implementations:  nvidia *  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.
and always always always
# 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
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
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
Look for udev and if you don't see it
# 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
Another thing with Networking breaking:
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.