cuchumino

Hello guys! It's been a while. I'm very interested in installing funtoo on my new desktop. I've got skylake goodness in there. I wanted to know, given that there wasn't any subarch for skylake, if I should just go generic, and then once the skylake subarch comes out, switch to whatever skylake will be, and do a: emerge -DuNav world Thanks for the feedback!

---- Wrong post ----

For some reason it was giving me troubles with fglrx. I have been using radeon drivers for the past week. I am switching back to fglrx, just because I REALLY want some games to work correctly. :) If it fails, I think I'm going to do an "emerge -eav world". (Heading out to visit some friends anyway this weekend. so that should be done when I'm back.) If it doesn't work and am going to do just what you're recommending. Mask Gnome 3.14.

I actually liked gnome 3. It was working fantastic on gnome 3.12 for myself. The latest upgrade to 14 made gnome-session not start up. http://forums.funtoo.org/index.php?/topic/267-gnome-314-doesnt-boot-i-suspect-cluttereglfglrx/&do=findComment&comment=1362 I am currently using mate, but I liked the window snapping, and was used to jumping from desktop to desktop from Gnome. Plus I also enjoyed the eyecandy. In the middle of writing this, I started to recompile gnome. Going to give it another stab. see what happens. :)

Will do. Thanks.

Not sure if I should post this here or in the Funtoo bugs page, but, seems Dogecoin is at 1.6, and it should be at 1.8. http://www.reddit.com/r/dogecoin/comments/2egjqg/dogecoin_core_18_released_mandatory_upgrade/ I came across some Dogecoin recently, and wanted to place it in my wallet. I found the solution, and it was an upgrade. Let me know if I should post this in bugs. Thanks!

Unfortunately getting the same error messages. :(

*gbm sure thing. it currently is on there and I believe it was up when it was crashing, but not sure. I'll check if recompiling ati-drivers unchecks it, or if it still fails with the flag up.

Cool! Thanks! Very much appreciated! :) On another note, I've really gotten the swing of Gnome 3, I thnk they've implemented some changes that make it slightly better to use, and I'm quite comfortable using it for my work and day to day purposes. Would suck to have to shop around for another D.E..

No I didn't. There was a time, before funtoo got all the openrc stuff sorted, that I couldn't get into gnome, but that was a distrowide thing. I can't remember which version of gnome that was. I think there was also a moment last year, before the operc issue, where I was having driver issues as well. ATI drivers didn't play nice with gnome. I remember always getting black screen with gdm, or if I used slim to log into gnome, also getting a black screen. A couple of bugs were fixed, and the black screen stopped, but then there were issues with the windows. They wouldn't update, so it would look like everything was working if you just looked at the desktop, but once you tried to click something in a window, the content within the window wouldn't refresh. This time around, I'm getting the "oh no! something has gone wrong" screen, and the startup programs I'd want would load up, but there would be no gnome shell, and the windows wouldn't have a frame, so i wouldn't be able to move them around.

I can confirm, this was definitely a fglrx/clutter issue. switching to radeon open source drivers fixed the solution. Although now 3d rendering sucks with my current card!

I was thinking this was something I did wrong. But I think this is a greater issue. I did some searching and it seems it's a fglrx & clutter issue. Something to the effect that fglrx doesn't play nice with EGL. $ gnome-shell (gnome-shell:23142): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' failed (gnome-shell:23142): Clutter-CRITICAL **: Unable to initialize Clutter: The OpenGL version could not be determined (gnome-shell:23142): mutter-ERROR **: Unable to initialize Clutter. let me know if you'd like any other additional information. I'm going to switch to radeon and unmerge fglrx, at least to get Gnome running. I tried to file a bug earlier but the bug website's user server seemed to be down.

Thanks Oleg! After resync this worked for me!

I've tried to emerge -av ati-drivers but I'm having a problem when doing this. I downloaded the files it expects given at these locations, and plop them in /usr/portage/distfiles Unfortunately it doesn't take. I'd blacklist whatever CONFIG_DRM is, but I don't know what module it is on load, but for some reason, given that there is no checksum being seen, I don't think it's CONFIG_DRM being the issue. Edit: am using debian binary sources if this info is needed Calculating dependencies... done! [ebuild U ] x11-drivers/ati-drivers-14.9-r1:1 [14.4_p1:1] USE="modules (multilib) qt4 vaapi -debug -pax_kernel -static-libs" 0 kB Total: 1 package (1 upgrade), Size of downloads: 0 kB Would you like to merge these packages? [Yes/No] >>> Verifying ebuild manifests >>> Running pre-merge checks for x11-drivers/ati-drivers-14.9-r1 * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /lib/modules/3.16.2-3/build * Found sources for kernel version: * 3.16.2-3 * Checking for suitable kernel configuration options... * CONFIG_DRM must be disabled or compiled as a module and not loaded for direct * rendering to work. * Please check to make sure these options are set correctly. * Failure to do so may cause unexpected problems. * Checking for suitable kernel configuration options... * CONFIG_DRM must be disabled or compiled as a module and not loaded for direct * rendering to work. * Please check to make sure these options are set correctly. * Failure to do so may cause unexpected problems. >>> Emerging (1 of 1) x11-drivers/ati-drivers-14.9-r1 !!! Fetched file: fglrx-installer_14.201.orig.tar.gz VERIFY FAILED! !!! Reason: Insufficient data for checksum verification !!! Got: !!! Expected: MD5 RMD160 SHA1 SHA256 SHA512 WHIRLPOOL * Fetch failed for 'x11-drivers/ati-drivers-14.9-r1', Log file: * '/var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/temp/build.log' * The driver packages * fglrx-installer_14.201.orig.tar.gz xvba-sdk-0.74-404001.tar.gz * need to be downloaded manually from * http://support.amd.com/en-us/download/desktop?os=Linux%20x86_64 * and http://developer.amd.com/wordpress/media/2012/10/xvba-sdk-0.74-404001.tar.gz >>> Failed to emerge x11-drivers/ati-drivers-14.9-r1, Log file: >>> '/var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/temp/build.log' * Messages for package x11-drivers/ati-drivers-14.9-r1: * CONFIG_DRM must be disabled or compiled as a module and not loaded for direct * rendering to work. * Please check to make sure these options are set correctly. * Failure to do so may cause unexpected problems. * CONFIG_DRM must be disabled or compiled as a module and not loaded for direct * rendering to work. * Please check to make sure these options are set correctly. * Failure to do so may cause unexpected problems. * Messages for package x11-drivers/ati-drivers-14.9-r1: * Fetch failed for 'x11-drivers/ati-drivers-14.9-r1', Log file: * '/var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/temp/build.log'

Wow! A bit off topic but... Athon XP.... that's round 2003-ish processor if my mind doesn't fail me? 13 hours!? My old computer recently died, was the one my mom was using. Can't remember which one it was it definitely was an Athlon. The model number does ring a bell.

Thanks Overkill. I hadn't restarted my system in a couple of days, last night, I shut everything down. Once it restarted, regular behavior resumed. Weird though.

Thanks for your help everyone. I ended up re-installing funtoo. I concluded that I must have done something else that first night I deleted portage in an attempt to fix it, and got lost in the depths of my mind when I went to sleep. I'm marking as solved because, as pointed out, had this only been a deleted /usr/portage/* , the following: #tar xpf portage.tbz2 -C / Should have fixed the problem, as it completely populated it again. In any case, thanks for the support!

Hello all! I recently reinstalled funtoo. I am using Gnome, and currently an important short cut key, the "windows" key on a regular keyboard, has stopped functioning correctly. I don't know what happens but when I hit that key, it takes me to terminal mode (not sure if this is what it is called.). I used to only be able to come to this mode if I hit ctrl+alt+F3 , or F1, or F2.... also, now if I want to close a window in Gnome, I might hit F4 on full screen applications or games. It takes me to the same console mode, and I have to ctrl+alt+F7 back in. Anyone know how to undo this annoying behavior?

Thanks for the messages. I did what sputnik suggested. I also downloaded a stage3 tarball image and replaced /usr/lib/portage/{bin,pym} with what was in the tarball. I'm getting this error now. I think it's getting there. :) FuntooBox portage # emerge --sync Unavailable repository 'gentoo' referenced by masters entry in '/var/lib/layman/steam/metadata/layout.conf' Unavailable repository 'gentoo' referenced by masters entry in '/var/lib/layman/pro-audio/metadata/layout.conf' --- Invalid atom in /usr/portage/profiles/package.mask/00-gentoo: Slot deps are not allowed in EAPI 0: 'dev-java/ibm-jdk-bin:1.5' --- Invalid atom in /usr/portage/profiles/package.mask/00-gentoo: Slot deps are not allowed in EAPI 0: 'www-plugins/chrome-binary-plugins:unstable' --- Invalid atom in /usr/portage/profiles/package.mask/00-gentoo: Slot deps are not allowed in EAPI 0: 'www-client/google-chrome:beta' --- Invalid atom in /usr/portage/profiles/package.mask/00-gentoo: Slot deps are not allowed in EAPI 0: 'www-client/google-chrome:stable' --- Invalid atom in /usr/portage/profiles/package.mask/00-gentoo: Slot deps are not allowed in EAPI 0: 'www-client/google-chrome:unstable' --- Invalid atom in /usr/portage/profiles/package.mask/00-gentoo: Slot deps are not allowed in EAPI 0: 'dev-java/itext:5' /usr/lib64/portage/pym/portage/package/ebuild/_config/MaskManager.py:50: UserWarning: Repository 'x-portage' is implicitly using 'portage-1' profile format in its profiles/package.mask, but the repository profiles are not marked as that format. This will break in the future. Please either convert the following paths to files, or add profile-formats = portage-1 to the repositories layout.conf. % dict(repo_name=repo_config.name)) WARNING: One or more repositories have missing repo_name entries: /usr/portage/profiles/repo_name NOTE: Each repo_name entry should be a plain text file containing a unique name for the repository on the first line. >>> Starting git pull... remote: Counting objects: 79, done. remote: Compressing objects: 100% (14/14), done. remote: Total 79 (delta 65), reused 79 (delta 65) Unpacking objects: 100% (79/79), done. From git://github.com/funtoo/ports-2012 1d8b3be..a780479 funtoo.org -> origin/funtoo.org You are not currently on a branch. Please specify which branch you want to merge with. See git-pull(1) for details. git pull <remote> <branch> !!! git pull error in /usr/portage. In any case, thanks for the help so far!

I know... I know... :unsure: I was going for the last action of the day. typed in rm -rf /usr/portage/* instead of: rm -rf /usr/portage/distfiles/* I am currently getting the following output when I try to emerge --sync Traceback (most recent call last): File "/usr/bin/emerge", line 37, in <module> from _emerge.main import emerge_main File "/usr/lib64/python2.7/site-packages/_emerge/main.py", line 36, in <module> from _emerge.actions import action_config, action_sync, action_metadata, \ File "/usr/lib64/python2.7/site-packages/_emerge/actions.py", line 39, in <module> from portage.package.ebuild.doebuild import _check_temp_dir File "/usr/lib64/python2.7/site-packages/portage/package/ebuild/doebuild.py", line 41, in <module> from portage.dbapi.porttree import _parse_uri_map File "/usr/lib64/python2.7/site-packages/portage/dbapi/porttree.py", line 20, in <module> from portage.cache import metadata_overlay, volatile ImportError: cannot import name metadata_overlay I tried python-update but... Traceback (most recent call last): File "/usr/bin/portageq", line 820, in <module> main() File "/usr/bin/portageq", line 800, in main args[0] = portage.settings["ROOT"] File "/usr/lib64/python2.7/site-packages/portage/proxy/objectproxy.py", line 37, in __getitem__ return object.__getattribute__(self, '_get_target')()[key] File "/usr/lib64/python2.7/site-packages/portage/__init__.py", line 608, in _get_target return _get_legacy_global(name) File "/usr/lib64/python2.7/site-packages/portage/_legacy_globals.py", line 34, in _get_legacy_global portage.db = portage.create_trees(**kwargs) File "/usr/lib64/python2.7/site-packages/portage/__init__.py", line 495, in create_trees config_incrementals=portage.const.INCREMENTALS, _eprefix=eprefix) File "/usr/lib64/python2.7/site-packages/portage/proxy/objectproxy.py", line 30, in __call__ result = object.__getattribute__(self, '_get_target')() File "/usr/lib64/python2.7/site-packages/portage/proxy/lazyimport.py", line 129, in _get_target __import__(name) File "/usr/lib64/python2.7/site-packages/portage/package/ebuild/config.py", line 15, in <module> from _emerge.Package import Package File "/usr/lib64/python2.7/site-packages/_emerge/Package.py", line 15, in <module> from _emerge.Task import Task File "/usr/lib64/python2.7/site-packages/_emerge/Task.py", line 4, in <module> from _emerge.SlotObject import SlotObject ImportError: No module named SlotObject Traceback (most recent call last): File "/usr/bin/portageq", line 820, in <module> main() File "/usr/bin/portageq", line 800, in main args[0] = portage.settings["ROOT"] File "/usr/lib64/python2.7/site-packages/portage/proxy/objectproxy.py", line 37, in __getitem__ return object.__getattribute__(self, '_get_target')()[key] File "/usr/lib64/python2.7/site-packages/portage/__init__.py", line 608, in _get_target return _get_legacy_global(name) File "/usr/lib64/python2.7/site-packages/portage/_legacy_globals.py", line 34, in _get_legacy_global portage.db = portage.create_trees(**kwargs) File "/usr/lib64/python2.7/site-packages/portage/__init__.py", line 495, in create_trees config_incrementals=portage.const.INCREMENTALS, _eprefix=eprefix) File "/usr/lib64/python2.7/site-packages/portage/proxy/objectproxy.py", line 30, in __call__ result = object.__getattribute__(self, '_get_target')() File "/usr/lib64/python2.7/site-packages/portage/proxy/lazyimport.py", line 129, in _get_target __import__(name) File "/usr/lib64/python2.7/site-packages/portage/package/ebuild/config.py", line 15, in <module> from _emerge.Package import Package File "/usr/lib64/python2.7/site-packages/_emerge/Package.py", line 15, in <module> from _emerge.Task import Task File "/usr/lib64/python2.7/site-packages/_emerge/Task.py", line 4, in <module> from _emerge.SlotObject import SlotObject ImportError: No module named SlotObject * Python 2 and Python 3 not installed eselect python list : Available Python interpreters: [1] python2.7 * [2] python3.3 Anyone know how to fix? I'd hate to have to wipe. :S

Video card is Radeon 5780. dbus loads on default on rc booting process. correct fglrx is eselected. With regards to dmesg/Xorg.logs, how exactly would I check my information? would dmesg be different from Xorg.logs? Where would these files be located? Thanks!

Hello All. First off, kudos for finding a way around systemd and GNOME. What a pain in the ass that migration would be. second off, I'm having some behavioral issues with GNOME. I think it might be on the video front, but also might be on the power front (power up, power down, log out, restart, etc). I'm putting them in the same topic because I believe that they might be related on some way. But.... I really don't know how to diagnose this to be quite honest. Lets start with the video side. Everything works great, for a while. If I use a program such as VLC, or Totem, there are times when the whole screen freezes, but the mouse is still able to move around. But I cannot drag any of the windows in the gnome environment, and the video's picture stays on the same frame, but the audio continues to play. Another problem I've had, and I believe it might be video related is when GNOME goes into screen shutdown or lock mode. there are times when it shuts the screen down, and when I move the mouse, the mouse works but the screen is black and I am stuck. Everything else on GNOME continues to work, but I can't get to my desktop. Sometimes the default "drag up" gnome lock screen appears, then it works as intended. Sometimes I have to wait for the screen to turn back off, and when it turns back on, the normal drag up screen will appear and work perfectly as well.... Other times I have to ALT+F1, and killall gnome-shell That seems to kill that. I ALT-F7 back on to the desktop, and since I have guake fired up, I can run gnome-shell again, and work with the intended GNOME environment. Other times, I'll get a partial black screen, and a partially loaded GNOME drag-up, lock screen. Almost as if it's in mid load. Then, my system freezes completly. I can move my mouse around, but I can't ALT+F1 out. On the power up/down, restart, logout, I have another set of issues. Sometimes, once the system has been running, say an hour or two, and I want to restart/power down my computer, it takes an awful long time to shut down GNOME and go into the reboot/power down state. I've noticed that it isn't a specific program running on GNOME as I shut down all programs that are currently open and on the system tab, and it still takes its time to shutdown. There are moments when it might take up to 3 - 5 minutes for GNOME to shut off and go into reboot/power down mode. Is there any way to diagnose this? I would appreciate any help on learning how to check what's going on here. Or has anyone had these issues in the past as well? I am really getting used to using GNOME, and would hate to have to switch desktops because of these problems. Thanks!

what duncan.britton said, plus you should blacklist the following. /etc/modprobe.d/blacklist.conf blacklist radeon If you don't do this before reboot, you might run into trouble. the radeon kernel module will load, and block fglrx from loading. This in turn can bring you massive headaches. Hope this helps!

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

I've been playing with some mild success with Funtoo on my new laptop. I sucessfully got Funtoo boot on UEFI by using the gentoo ebuild Grub2 work around stated in a previous post. I have not however been able to start X. long and the short of it is, my video wasn't being detected by X so it seems. i.e.: when I would run aticonfig --initial, I'd get something to the effect of "no adapters detected". simliar would happen with radeon. I believe it could be a kernel issue. I couldn't report or post anything for feedback because I have to travel this weekend, and need to have a working OS on my laptop. So I scrapped it all, but once I'm back, I'm going to give it another stab, hopefully post something to get some feedback and hopefully help out others. I am planning on adding a couple of caveats on using the rtl8723be wifi card, and getting it to work on a system using a kernel >3.15. It's not tough, but a little tricky. I'll post this while I'm re-installing. In the meantime, what info should I post once I attempt another install (most likely on Wednesday/Thursday), to get X troubleshot? Maybe the .config of the kernel? (I did do debian-sources binary though, not sure if that would help at all)