Jump to content
funtoo forums

cuchumino

Members
  • Content Count

    28
  • Joined

  • Last visited

  1. 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!
  2. 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.
  3. 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. :)
  4. 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!
  5. Unfortunately getting the same error messages. :(
  6. *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.
  7. 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..
  8. 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.
  9. 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!
  10. 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.
  11. Thanks Oleg! After resync this worked for me!
  12. 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'
  13. 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.
×
×
  • Create New...