Posts tagged Limbo
A user of the limbo repository that is helping test limbo packages that is. Some big updates in limbo lately and we would like to hear from those that are using the limbo repository. Any issues, such as graphical, like the screen isn’t refreshing properly or as Joost says, painted artifacts or x freezing? If so, we would like to know what your hardware is. I’m not noticing any problems with my nvidia card yet on the gnome side. I just finished updating my KDE x86 install, 534 updates for that install. It doesn’t matter which kernel you are using. Joost noticed things with .36 and .37.
Last week I ran into an issue with entropy alpha4 version. I could update, but I couldn’t do anything else without it puking some alien language on my screen. With a broken entropy, I was kinda dead in the water for getting anything installed. So what does a guy do? You always have portage to recover entropy. This is why in our wiki, fresh install what to do section, I put in the suggestion of doing an emerge –sync && layman -S every so often. Entropy is also on our overlay so you can recover it after you do your emerge –sync && layman -S and do emerge entropy equo sulfur to reinstall your entropy packages. In my case it had already been bumped two versions to alpha6. Once installed via portage, I was back in business with entropy. Keep that in mind, portage and our overlay can come in handy.
2.6.37 is available in-case you didn’t know. Remember, a new kernel version should never be pulled with regular updates. If it does, please file a bug with the relevant information. So I will go through steps on how I do a kernel upgrade via equo.
- First I check to see what is available equo search linux-sabayon will show me: sys-kernel/linux-sabayon-2.6.37 is not installed and available of course.
- So to install it, I issue equo install sys-kernel/linux-sabayon-2.6.37 and wait for that to download and install. After install, verify with eselect kernel list and the * should be on linux-2.6.37-sabayon. If not, use eselect kernel set 3 (use the number that corresponds with your kernel).
As always with our kernel changes, you must reinstall your modules/drivers. Repeat to yourself, if I change the kernel, I must reinstall modules/drivers till it sinks in. There is a trick to this, it’s not as easily as installing a new kernel and doing and equo upgrade to pull the new drivers as it won’t do that. You have to tell entropy the specifics of it. So the stuff I need to reinstall are my nvidia drivers and virtualbox stuff. Use equo search to get the package names.
- So for nvidia drivers I do equo search nvidia-drivers and I find x11-drivers/nvidia-drivers-260.19.29#2.6.37-sabayon, which are the ones I need, your mileage may vary, but the key here is to look for the #2.6.37-sabayon as that means it is for .37 kernel. So the trick is to use the full path of name for install, equo install x11-drivers/nvidia-drivers-260.19.29#2.6.37-sabayon and let that download and install. After install, veryify with eselect opengl list and the * should be at nvidia. If it is not, use the eselect opengl set 1 (use the number that corresponds with your driver).
- For each module/driver, repeat that step. For virtualbox I would do the equo search and than find out I need to do equo install app-emulation/virtualbox-modules-3.2.12#2.6.37-sabayon.
You only need to do this once after a kernel change. After you get the proper versions installed, equo upgrade will know which version you are using and keep the software up to date or if you reinstall a package, equo install nvidia-drivers should be all you need. Upon installing the kernel, your grub should be updated and ready to go for the reboot to your new kernel. Just got to keep in mind that driver version has to match kernel version. Use full name to reinstall drivers after a kernel change and after that, you should be set. A bit of PITA and confusing for new people, but easy to do and once you do it once, you will have the confidence to do it again, just take notes, ehehe.
A quick little guide on helping and getting involved with the future releases of Sabayon. I know and see people asking what they can do to be more involved in Sabayon. If you have some experience, time and capabilities, you can help test the weekly iso images or add the entropy limbo repository and test packages. I wouldn’t recommend this for or on your production system. You can and will run into broken stuff, but that is the fun in testing! I like to use rsync as it saves on bandwidth of having to re-download the entire ISO. With rsync you only download the changes. So how does one do this you may ask. It’s pretty easy, find a mirror on our download page that supports rsync.
Let’s for example use Italy – Garr mirror. You will notice rsync://na.mirror.garr.it/sabayonlinux [1000Mbit/sec].
This is what you are looking for. I myself have created in my home directory two directory structures /home/wolfden/isos/x86 and /home/wolfden/isos/64. You have the option to rsync the entire directory which will grab all the iso images from the server. I do not want to do that. I only want the 64 bit ones as that is all I use. So I rsync the Gnome and KDE editions of the x86_64 isos. You will have to decide what you want to do. Either do all or pick the one(s) you want.
Now I just need to run a simple command via terminal:
rsync –progress -av rsync://na.mirror.garr.it/sabayonlinux/iso/daily/Sabayon_Linux_DAILY_x86_G.iso /home/wolfden/isos/x86 (it’s a double dash in front of progress)
That will go out and fetch the iso file and place it into the directory. I always grab the md5 file also and check the iso image. Just like this:
rsync –progress -av rsync://na.mirror.garr.it/sabayonlinux/iso/daily/Sabayon_Linux_DAILY_x86_G.md5 /home/wolfden/isos/x86
than to verify
md5sum -c Sabayon_Linux_DAILY__x86_G.iso
Now that you have the file, in the future when you run the above commands, it will update your iso and md5 by downloading only the changes instead of the entire iso file again. You can of course download your first iso(s) off the ftp side of the server and move it to the correct directory and than run the rsync. As long as the iso and path all point correctly it will update.
If you want to download all the isos, you can simple do something like:
rsync –progress -av rsync://na.mirror.garr.it/sabayonlinux/iso/daily/ /home/wolfden/isos
That will grab everything in the directory. To get a directory listing:
rsync –list-only rsync://na.mirror.garr.it/sabayonlinux/iso/daily/
I like to use unetbootin and a flash drive for testing iso. Save a blank cd/dvd-r and use a flash drive if you can.
Maybe you don’t want to test iso(s) and just want to test packages. We have the entropy limbo repository that is the testing ground for packages before they get moved into the main line repository. One of the entropy team members will give a shout out here and there for specific testing of limbo packages even. You can enable the limbo repository through sulfur or by editing the /etc/entropy/repositories.conf, please see our wiki for that. Also make sure you are on the Sabayon Dev Mailing List to stay in touch with announcements and changes for testing. Getting on the Dev ML should be your first step.
So now you are testing and find an issue or bug and need to report it. You can use the Sabayon Dev ML, Sabayon Bugzilla or discuss testing in the special forum section devoted to just testing. When reporting, try to keep in mind a few important things that are needed:
- Which Sabayon Linux are you running – x86, x86_64, gnome, kde, core ?
- How to reproduce the issue? Give us the steps on what you did to get the issue(s) so we can try and reproduce it.
- Any and All Log files that pertain to the issue.
- Hardware List
The more information you submit, the easier it is for us and there is no cat and mouse chasing to get the required information. Stating that the latest entropy limbo update crashed your desktop isn’t what we want to see. Reports like that are usually deleted as they are useless. So try and remember that the more information you can give, the better. Someone will usually try and recreate the issue to confirm or deny the issue. Feel free to confirm or deny the issue(s) as they are posted.
Being a tester is usually for experienced users and you usually don’t want to run it as your main operating system. Some ask that they don’t have enough hard drive space to test and want to know if they can use Virtual Box. Yes you can. We need all aspects tested. This includes things like virtualization, running it in live mode, and doing actual installs. New users are gonna get their first impression from the Live mode, so we need that working flawlessly. I like to use unetbootin for this. Just let us know how you are running it, again, the more information you can provide, the better. Test anyway you can and help make a stronger Sabayon and be apart of that.
Thanks to all that do already and will be in the future.
If you are using Limbo repository with your sabayon linux, sys-kernel/linux-sabayon-2.6.32 has been added to it. It doesn’t get automatically pulled with equo world, but the other files will. Now for me, my experience was fine. I am world updated with limbo and have the nvidia-drivers unmasked (GeForce 9500 GT). I went ahead and did the equo update && equo world. Once that was done, I did equo install linux-sabayon and than equo install nvidia-drivers. Remember after kernel installs, your drivers/modules need to match up. The install of the kernel doesn’t pull these. Installing the linux-sabayon should set your eselect kernel list properly and also edit your grub.conf file properly, double check to make sure. I had no issues with x11-drivers/xf86-input-xxxxxx drivers without reinstalling them.
If you are an ATI user, apparently the ati-drivers don’t work yet, so you will need to use the xorg-x11 open source drivers. Joost has a 3870 HD ATI and X was unusable with the ati-drivers. He also says you can try appending nomodeset or radeon.modeset=0 to your grub line if having problems with open source drivers. darthlukan reports with his ATI XPRESS 200M Radeon and open source drivers, all good and didn’t have to append anything.
Of course your mileage will vary, you been warned. I would be curious to your finding tho. Click on title to leave comment.
Have you checked for updates lately with entropy? Some are already seeing and questioning 500+ updates hitting their queue. The Limbo repository was released and all the packages got dumped to the main line repository. So when you see the update list, you can be assured that everything is working the way it should be. Now if you have been rolling along with the updates, you of course wouldn’t see such an update. I haven’t updated my package list for threes days now and I only have 35 updates.
So what does this mean? It means we are getting ready to kick out a 5.1 release. In order to do a 5.1, we needed to add the packages from Limbo. Now, main should stay quiet for the most part while the isos are prepared. So how cool is that? You will have 5.1 and didn’t even need to reinstall. Yay!
I wouldn’t expect much changes to artwork. Ian has stepped down from artwork to work on other areas of Sabayon Linux. So we don’t have anyone really doing artwork at the moment. We are talking to a few that maybe interested in joining a team. I encourage anyone that is interested in working with artwork, to get a hold of myself or join irc chat #sabayon and #sabayon-dev on freenode for more information.
We recently posted a message out to the developers mailing list stating that Sabayon Linux is looking for people in all areas. We would like to build up a team for maintaining overlays, artwork, entropy package maintainers, coders/programmers in python and C++, and support/documentation people. It takes a lot of people to keep things rolling smoothly and especially if we want to expand. Are you interested or know of someone that would be interested? Feel free to contact me or join us in #sabayon and #sabayon-dev irc on freenode. Also feel free to use our dev mailing list to contact us also. Please don’t hesitate to ask. We look forward to seeing new blood joining the team.