cuchumino

Hello everybody! after six years using Linux distributions like fedora and sabayon , finally i decided to move to a really serious distro. I was researching on what kind of meta-distro must be installed on my computer and i really really liked the funtoo way for linux since the first time i meet the welcome page in funtoo.org, ,,, anyway, i was wondering on how to install the Mate environment over my new stage 3 tarball and brand new compiled kernel already installed on my hard drive. First i take a look to http://www.funtoo.org/MATE_Desktop, but when i needed to do the following step:
cp /usr/portage/sets/mate /etc/portage/sets suddenly the things went very dark... the '/usr/portage/sets/mate' doesn't exist on my installation, i decided to install Mate following the little guide provided by the gentoo wiki (http://wiki.gentoo.org/wiki/MATE), after that, finally i can run the mate desktop by 'startx' , but to be honest, the desktop really sucks balls, it lack a lot of things that usally i need: doesn't mount any kind of media, doesn't have network manager, there are no sound, even i don't know how to set up the time. So, how to correctly install the Mate environment?? or how to complete the installation of the very minimal 'mate-base/mate' desktop. I really appreciate any information or any help . Thanks!
 

Technically, Grub does not require the boot (/boot) partition to be mounted to reference/locate the kernel and boot the machine. Generally, the arguments for having /boot mounted for normal system usage are few. As mentioned, it's been quite some years that 'noauto' has been set as the default for /boot in the template fstab file provided in the stage-3 tarballs from Gentoo and Funtoo. But it's not some type of hard 'law' or anything - if you'd like to always see your boot partition mounted, feel free to go ahead and removed 'noauto' from that line in fstab.
 
In the Gen/Funtoo-verses (and well, in Linux-verse generally), it's really only necessary to mount /boot when performing a kernel upgrade. Otherwise, it's a best practice to leave it as 'noauto' in fstab, imho. It has happened that newer users in years past have accidentally cd'd into /boot and deleted the kernel. Not the end of the world, by any means, but a pita to correct when you have to reboot the box.

this is fixed now.

sould be fixed with next tree update.

Yeah, it's a bit cryptic.  It wants it like this
eselect java-nsplugin set 64bit blah Blah being the name or number of what you want to use.
 

Check your keyboard settings in the gnome control panel.  There are shortcuts there that can be added/changed/removed.  Maybe you have the wrong keyboard input source?  That can be changed there as well.

This never fails:http://www.funtoo.org/Installing_Portage_From_Snapshot
Although guessing, you've still got some hidden files in /usr/portage, just finish what you started and rm /usr/portage, install -d /usr/portage and try emerge --sync, faster.  That is if you don't care about distfiles and packages.

Deleting /usr/portage doesn't cause emerge to fail on --sync, so you have something else going on.
 
It's perfectly fine to rm -rf /usr/portage and emerge --sync to get a new copy. This is something that works.

Have someone do an emerge --quickpkg portage for you and install the resultant tarball by extracting to /:
 
# tar xpf portage.tbz2 -C /

from my experience, when "weird or undefined" issues appears during portage tree updates, it's good to wait until next update :)

There was some kind of funny stuff with the Gentoo afternoon update, I had a weird message about downgrading libreoffice for no good reason.  Happens.  Good to say "oh, well, I'll update tomorrow" when you see stuff like that.  Maybe there's something else to the xfce stuff, I just don't know, but considering the other funnyness I'd wait and see.  I re-synced later and the libreoffice downgrade was gone, although the xfce stuff you mention is still missing.
Also, as a BTW, I used to have a lot of trouble with eix-sync, lunched my Portdir 2 or 3 times, so I quit using it.  In Funtoo, when I was using Gentoo it was no problem.  Just FYI, in case you have trouble.  Could have just been something here locally.  Now I emerge --sync && eix-update, same thing, a little more typing.

It looks like you already have some drivers installed for your graphics card that are pulling in a later version of Xorg than the ati-drivers can support:
x11-drivers/xf86-video-ati-7.4.0::gentoo If you only want to have the ati-drivers, change your /etc/portage/make.conf to contain the following:
VIDEO_CARDS="fglrx" After doing that, you can try unmerging xf86-video-ati, glamor, and xf86-input-evdev. Then, run an "emerge --update --newuse --deep --with-bdeps=y @world". This should pull in the ati-drivers without all of those nasty conflicts that you are getting. Also, check out http://www.funtoo.org/Package:AMD_Catalyst_Video_Drivers . Hope this helped!

Hello benzolius!
 
As j-g- mentioned, you don't have to boot into another system, unless that's the only way to download the driver because of your wireless connection.
 
My question would be, what wireless card do you have. If the wireless card is so new that it's not in the kernel (as happened with my new laptop recently), you'll have to do some research to find and compile the module yourself.
 
could you post the output of :
sudo lspci

Thanks for your reply. nomodeset didn't work for me. Your advice was helpful and I made sure my settings were right, so thank you for that :).
 
Unfortunately, it still didn't work. So I decided to try something different.
 
I ended up finding a fix! I'm now able to boot in correctly. I believe this is a fix for someone that's exhausted all possible kernel trials. I'm assuming this is a funtoo grub packaging problem or something was wrong with my grub.cfg. It's just weird because grub was loading fine, that is why I assumed kernel error.
 
Here is what I did to fix it:
emerge --unmerge grub Added a local overlay, something like /usr/local/portage is good. Added gentoo's version of grub to the overlay. It was also a newer version than funtoo's. emerge -va grub grub-install --target=x86_64-efi --efi-directory=/boot /dev/sda grub2-mkconfig -o /boot/grub/grub.cfg Restarted and was able to get into my system. If anyone has any idea why the funtoo grub didn't work for me, let me know.

Okay. I will be working on resources for new developers. Flora was run as sort of a side-project, and that was probably not the best approach. An effort like that needs to be fully integrated into the main Funtoo Linux project, which I will do. That should solve the problem by ensuring that your work is paid more attention to and you are given the resources you need to be successful and learn.