-
Posts
122 -
Joined
-
Last visited
-
Days Won
9
Content Type
Profiles
Forums
Blogs
Posts posted by sputnik
-
-
I've seen the 1st error before, that's normal (?) and of no consequence. I forget why, but it's well known non-issue.
I can't log into my ati machine at the moment to see anything more.
Glad I could help...
-
You'll find it's quite easy in Funtoo also if you follow the guide that paddymac linked to. I use cross-compiling environments extensively here, works great for a couple of years.
It's interesting what paddymac has to say about the gcc builds, as the guide points out, you cannot use funtoo gcc ebuilds per angry vincent and my own experience. The features may have been added back, but you still won't get them to work with crossdev. But the info about the toolchain overlay is new to me, I may have to try that.
I also find 20140729 to be the latest working crossdev as per that bug report.
I'm exploring Funtoo for both a desktop (x86_64) as well as my Beaglebone Black (armv7). I've got it working great on my desktop but I'm struggling to get a cross compiler set up on my desktop since I obviously don't want to be compiling a bunch of stuff on a small ARM system.I make my own ARM flattened device tree kernels from vanilla-sources on my x86_64, no problem, < 1/2 hour. Heh, my dockstar has just hit hour 25 compiling sys-devel/gcc-4.8.3. It'll do it though. It's the one tough thing, gcc, but not as tough for your beaglebone, the dockstar only has 118M memory so it's swapping alot. Fortunately the toolchain doesn't get updated that often. You can cheat by making a qemu ARM environment, downloading the latest stage3 and repackaging the gcc from it.
-
# equery g skype
* Searching for skype ...
* dependency graph for net-im/skype-4.3.0.37-r3
`-- net-im/skype-4.3.0.37-r3 ~amd64
`-- sys-apps/sed-4.2.2 (>=sys-apps/sed-4) ~amd64
`-- virtual/ttf-fonts-1 (virtual/ttf-fonts) amd64
`-- dev-qt/qtcore-4.8.5-r2 (dev-qt/qtcore) amd64 [abi_x86_32(-)]
`-- dev-qt/qtdbus-4.8.5 (dev-qt/qtdbus) amd64 [abi_x86_32(-)]
`-- dev-qt/qtgui-4.8.5-r3 (dev-qt/qtgui) amd64 [accessibility abi_x86_32(-)]
`-- dev-qt/qtwebkit-4.8.5 (dev-qt/qtwebkit) amd64 [abi_x86_32(-)]
`-- app-emulation/emul-linux-x86-qtlibs-20140508-r1 (>=app-emulation/emul-linux-x86-qtlibs-20120520) amd64 [-abi_x86_32(-)]
`-- media-libs/alsa-lib-1.0.28 (media-libs/alsa-lib) amd64 [abi_x86_32(-)]
`-- app-emulation/emul-linux-x86-soundlibs-20140508 (>=app-emulation/emul-linux-x86-soundlibs-20120520) ~amd64 [-abi_x86_32(-)]
`-- x11-libs/libX11-1.6.2 (x11-libs/libX11) amd64 [abi_x86_32(-)]
`-- x11-libs/libXext-1.3.3 (x11-libs/libXext) ~amd64 [abi_x86_32(-)]
`-- x11-libs/libXScrnSaver-1.2.2-r1 (x11-libs/libXScrnSaver) amd64 [abi_x86_32(-)]
`-- x11-libs/libXv-1.0.10 (x11-libs/libXv) amd64 [abi_x86_32(-)]
`-- app-emulation/emul-linux-x86-xlibs-20140508 (>=app-emulation/emul-linux-x86-xlibs-20120520) ~amd64 [-abi_x86_32(-)]
`-- media-sound/pulseaudio-5.0.20141024 (media-sound/pulseaudio) M[package.mask] [abi_x86_32(-)]
`-- media-sound/apulse-0.1.2-r2 (media-sound/apulse) ~amd64 [abi_x86_32(-)]
`-- sec-policy/selinux-skype-2.20140311-r7 (sec-policy/selinux-skype) ~amd64
[ net-im/skype-4.3.0.37-r3 stats: packages (18), max depth (1) ]
# equery g wine
* Searching for wine ...
dependency graph for app-emulation/wine-1.7.29
`-- app-emulation/wine-1.7.29 ~amd64
`-- media-libs/freetype-2.5.3-r1 (>=media-libs/freetype-2.0.0) amd64
`-- net-dialup/capi4k-utils-20050718-r6 (net-dialup/capi4k-utils) amd64
`-- sys-libs/ncurses-5.9-r3 (>=sys-libs/ncurses-5.2) ~amd64
`-- sys-apps/dbus-1.8.10 (sys-apps/dbus) amd64
`-- media-libs/fontconfig-2.11.1-r1 (media-libs/fontconfig) ~amd64
`-- media-libs/libgphoto2-2.5.5.1-r1 (media-libs/libgphoto2) ~amd64
`-- media-libs/openal-1.15.1-r2 (media-libs/openal) ~amd64
`-- media-libs/gstreamer-0.10.36-r2 (media-libs/gstreamer) unknown
`-- media-libs/gst-plugins-base-0.10.36-r1 (media-libs/gst-plugins-base) amd64
`-- x11-libs/libXcursor-1.1.14 (x11-libs/libXcursor) amd64
`-- x11-libs/libXext-1.3.3 (x11-libs/libXext) ~amd64
`-- x11-libs/libXrandr-1.4.2 (x11-libs/libXrandr) amd64
`-- x11-libs/libXi-1.7.4 (x11-libs/libXi) ~amd64
`-- x11-libs/libXxf86vm-1.1.3 (x11-libs/libXxf86vm) amd64
`-- x11-libs/libXinerama-1.1.3 (x11-libs/libXinerama) amd64
`-- media-libs/alsa-lib-1.0.28 (media-libs/alsa-lib) amd64
`-- net-print/cups-2.0.0-r2 (net-print/cups) unknown
`-- virtual/opencl-0-r4 (virtual/opencl) amd64
`-- virtual/glu-9.0-r1 (virtual/glu) ~amd64
`-- virtual/opengl-7.0-r1 (virtual/opengl) ~amd64
`-- media-sound/gsm-1.0.13-r1 (media-sound/gsm) ~amd64
`-- virtual/jpeg-0-r2 (virtual/jpeg) amd64
`-- net-nds/openldap-2.4.40-r2 (net-nds/openldap) unknown
`-- media-libs/lcms-2.6-r1 (media-libs/lcms) ~amd64
`-- media-sound/mpg123-1.21.0 (>=media-sound/mpg123-1.5.0) ~amd64
`-- net-fs/samba-3.6.24 (net-fs/samba) ~amd64 [netapi(+)]
`-- sys-devel/gettext-0.19.3 (sys-devel/gettext) ~amd64
`-- dev-db/unixODBC-2.3.2-r1 (dev-db/unixODBC) ~amd64
`-- media-libs/mesa-10.3.1 (media-libs/mesa) ~amd64 [osmesa]
`-- sys-apps/attr-2.4.47-r1 (sys-apps/attr) ~amd64
`-- media-sound/pulseaudio-5.0.20141024 (media-sound/pulseaudio) M[package.mask]
`-- dev-libs/libxml2-2.9.2-r1000 (dev-libs/libxml2) unknown
`-- dev-libs/libxslt-1.1.28-r1002 (dev-libs/libxslt) unknown
`-- media-gfx/sane-backends-1.0.24-r5 (media-gfx/sane-backends) ~amd64
`-- net-libs/gnutls-3.3.10 (net-libs/gnutls) unknown
`-- media-libs/libpng-1.6.13 (media-libs/libpng) ~amd64
`-- media-libs/libv4l-1.6.0-r1 (media-libs/libv4l) ~amd64
`-- x11-libs/libXcomposite-0.4.4-r1 (x11-libs/libXcomposite) amd64
`-- app-emulation/emul-linux-x86-xlibs-20140508 (>=app-emulation/emul-linux-x86-xlibs-2.1) ~amd64 [development -abi_x86_32(-)]
`-- app-emulation/emul-linux-x86-baselibs-20140508-r14 (app-emulation/emul-linux-x86-baselibs) ~amd64 [development -abi_x86_32(-)]
`-- app-emulation/emul-linux-x86-medialibs-20140508-r6 (app-emulation/emul-linux-x86-medialibs) amd64 [development -abi_x86_32(-)]
`-- app-emulation/emul-linux-x86-sdl-20140508-r1 (app-emulation/emul-linux-x86-sdl) amd64 [development -abi_x86_32(-)]
`-- app-emulation/emul-linux-x86-soundlibs-20140508 (app-emulation/emul-linux-x86-soundlibs) ~amd64 [alsa development -abi_x86_32(-)]
`-- app-emulation/emul-linux-x86-opengl-20140508 (app-emulation/emul-linux-x86-opengl) ~amd64 [development -abi_x86_32(-)]
`-- app-emulation/emul-linux-x86-db-20140508-r3 (app-emulation/emul-linux-x86-db) ~amd64 [development -abi_x86_32(-)]
`-- x11-proto/inputproto-2.3.1 (x11-proto/inputproto) ~amd64
`-- x11-proto/xextproto-7.3.0 (x11-proto/xextproto) ~amd64
`-- x11-proto/xf86vidmodeproto-2.3.1-r1 (x11-proto/xf86vidmodeproto) amd64
`-- x11-proto/xineramaproto-1.2.1-r1 (x11-proto/xineramaproto) amd64
`-- sys-devel/prelink-20130503 (sys-devel/prelink) ~amd64
`-- sys-kernel/linux-headers-3.17-r1 (>=sys-kernel/linux-headers-2.6) unknown
`-- virtual/pkgconfig-0-r1 (virtual/pkgconfig) unknown
`-- virtual/yacc-0 (virtual/yacc) amd64
`-- sys-devel/flex-2.5.39-r1 (sys-devel/flex) amd64
`-- sys-devel/automake-1.13.4 (>=sys-devel/automake-1.13) amd64
`-- sys-devel/automake-1.14.1 (>=sys-devel/automake-1.14) M[package.mask]
`-- sys-devel/autoconf-2.69 (>=sys-devel/autoconf-2.69) amd64
`-- sys-devel/libtool-2.4.3-r2 (>=sys-devel/libtool-2.4) unknown
`-- sys-apps/sed-4.2.2 (>=sys-apps/sed-4) ~amd64
`-- x11-base/xorg-server-1.16.1-r1 (x11-base/xorg-server) ~amd64 [xvfb]
`-- x11-apps/xhost-1.0.6 (x11-apps/xhost) amd64
`-- games-emulation/dosbox-0.74 (games-emulation/dosbox) amd64
`-- dev-lang/perl-5.20.1-r2 (dev-lang/perl) ~amd64
`-- dev-perl/XML-Simple-2.200.0-r1 (dev-perl/XML-Simple) amd64
`-- sec-policy/selinux-wine-2.20140311-r7 (sec-policy/selinux-wine) ~amd64
`-- sys-fs/udisks-2.1.3 (sys-fs/udisks) amd64
`-- sys-auth/rtkit-0.11 (sys-auth/rtkit) ~amd64
[ app-emulation/wine-1.7.29 stats: packages (68), max depth (1) ]
-
I don't disagree, it _should work with /dev/sdx, but I have seen it not and as evidenced by that post at least one other Funtoo person has as well. Actually, I've seen others saying the same on the web, that's how I came to realize it. Various distros.
I don't claim to know why, but there it is.
But now I read your OP again and see you don't use initramfs and generic kernels do boot, sorry for not paying more attention. So obviously it's in the config, as you've noted.
Sounds like maybe some more hours making the perfect lean kernel ;) I guess you could diff the generic config vs. your new config, probably you've thought of that, but it might be easier to start with the generic, shave off a little at a time, until you are lean.
Seems likely to be something in device drivers>serial ATA and parallel ATA drivers doesn't it? It's all a good learning experience :lol:
-
I've done what you are trying to do before, but I switched to a different method. The issue is you have your .config and .gnome, etc. type of config files and the OS'es can get things mixed up. Better I think to use links for those folders you think you might want to share, then the config folders will be unique to each, sidestepping that problem.
-
It's not an absolute verbatim law, but I find often using /dev/sdx in fstab is a loser. And most distros recommend trying to use uuid or labels. There's another post on the forum where someone had the same issue and that solved it http://forums.funtoo.org/index.php?/topic/176-boot-update-issue/
-
Couple questions since we are on the topic.
Will Grub scale the given image to the current resolution, or do you have to provide a copy of the image in every resolution?
Is there a tutorial on how to change the menu size? I've seen the menus placed in various parts of the screen, changed to use icons, and all sorts of stuff. The last Gentoo live DVD is a good example. Its a big download, but the grub on it is newer than what funtoo has available and the configuration is very well done!
In the loopback mount that you did, have you ever tried to grab the ISO off NFS? I think its possible. And if grub can do that (would need NFS drivers in grub) then you should be able to chainload the ISO image as if it was a CD without having to give it the kernel and initrd lines ... just chainload to whatever secondary bootloader is on the medium. I was thinking that with some careful scripting, you could have an NFS server with a bunch of ISOs and a script that generates a grub config file for all those entries. You would then just need a grub menu item that loads the remote config file.
I guess grub can load files through tftp. Anyone tried to load a whole ISO via tftpboot and loopback it in grub?
I don't think it will scale the image, but frankly I forget. Try it!
Menu size (including font) changes with the resolution changes. AFAIK you need to size the picture to match gfxmode. But not the box, it fills the screen no matter what, I don't know how to change that. Also you can try dinking around with changing the default grub font, too much to go into here, but you can find lots of info on that on the web.
I haven't tried the NFS idea. Sounds like a cool idea, but I think you would have to modify the initrd for sysrescue, that could be hairy because it's a compressed filesystem. I have made custom sysrescue iso's and it's a several step process because of that. And then the same for any other iso's. It would be cool though.
-
Some more thoughts on this.
Do you really need a new case and power supply? That could help. That 500gb PATA, heck, the stuff you're doing, that could do you for a while, you may need a card to run PATA, no big deal. Can upgrade drive later. Can replace power supply when it dies.
Nah, he can do it easily for $500 if he's cautious and the above stuff would help alot.
Might find some good deals with Black Friday coming up ;)
-
You ask a lot of questions paddymac :)
Since I have the second oldest equipment in the Funtoouniverse I feel qualified to answer :D
I think you can pull it off easily for $500.
Emulator for windows (virtualbox works great), or you can dual boot easily enough too, so that's not an issue.
As far as the long term planning, it's a nice concept. After many decades I've never seen it amount to much. Things change too quickly and to try and hold on, it just doesn't work out much. Welcome to the disposable western world. You can make sure you have at least 4 or more ram slots, some m/b's just have two. You can upgrade video cards easily enough, until they come up with the "next new bus". You can upgrade cpu's for a couple of years, then they'll freeze that design too. But perhaps others may have pointers that can help.
Being an Asus fan (except for price) I'll pass on the m/b question. That power off issue can be hairy I know. And can be caused by many things. In worst case scenarios you can often find or make a hacked bios, I run hacked bioses on two machines here, for other issues though.
I have been looking at the new stuff. My impression: Intel won the race, lower power consumption, faster, cooler. AMD higher power consumption, more cores (ergo higher power consumption) to attempt to compete. I'm an AMD fan from way back, but I'd have to buy Intel now. AMD was doomed from the start and now Intel has played the trump card (more bucks). They just can't afford the super cutting edge equipment Intel uses to get those tiny, tiny lines. And cpu optimizations, Intel loses them in the dust. Didn't I see you say in another thread you are on Hughes Net? So probably you'd be interested in power consumption like I am. I'm trying to hang on for Intel to get even lower consumption and higher speed...
I have Nvidia here and remotely maintain a friend's AMD/ATI machine. I'd have to pick Nvidia there too. When AMD acquired ATI the development went into the dumper, although it's said lately they are trying to do something about that. Time will tell. After a long, long wait there was finally an updated video driver and it's said that the next driver will REALLY be an improvement. Meanwhile Nvidia keeps cranking along like a well-oiled machine. Even the manual that comes down the pipe with every Nvidia upgrade is quite detailed. Don't get me wrong, I think they both stink, just Nvidia stinks less. Once upon a time there were 15-20 video card manufacturers, now there's 2 (we won't count Intel)? So it's a seller's market...Here's what Linus Torvalds thinks of Nvidia http://cdn.arstechnica.net/wp-content/uploads/2013/02/linus-eff-you-640x363.png
Really, that was his reaction in a discussion about them :)
All that being said, your uses are pretty light, and if power consumption is not such an issue for you you can save some bucks going AMD/ATI. When you think of a car purchase do you have to have the fastest on the block, or just one to get you back and forth from the store? But even then you'll just be paying just as much or probably more on your electric bill to run the AMD, unless you really are tight for bucks it just doesn't make sense anymore. AMD used to give you 90-95% of the performance for 50% of the price, I thought that was a fair trade. But the performance rift is bigger now and you just end up paying the same or more in monthly installments on your electric bill.
Your old computer? Put it in a big grinding machine, then take the pieces that come out and put them in a pot heated above the melting point of gold. Carefully dump off the plastic & junk and recover the gold. Ship the junk to Africa. Or just take it to a recycler where he'll do all that for you and give you $3 for it. Or give it to the thrift store and feel good about it. Save the whales & all.
Seriously, at an average of about 105 watts it's not really much good re-purposed, unless you can find it a home somewhere where it's better than nothing.
Hey, where's that thrift store located?
-
I only run php on my ARM devices and it is a real pain there, especially because the software needing it has lots of arcane use flags needed. Actually, I've stopped using that software and just haven't bothered uninstalling php, will get back to it someday, got it masked back to what is installed. Anyhow the point is, I found, at least on that platform, it's very sensitive to which use flags are used, and with some enabled it fails install every time. It's especially painful with a slow compiling ARM device. I didn't get very depthful into understanding the problems because I was on the fence about that software anyhow, that was the tipping point.
-
Hmm, not sure what you mean. If you just make another kernel and it gets placed in /boot by make install, then boot-update will find it and happily put it on your grub startup list. If that's what you're looking for. You can make as many kernels as you have room for on disk.
-
Well, no, not fine after all. Get this:
* Package: x11-drivers/ati-drivers-14.9-r1 * Repository: gentoo * USE: amd64 elibc_glibc kernel_linux modules multilib qt4 userland_GNU vaapi * FEATURES: ccache preserve-libs sandbox * Determining the location of the kernel source code * Found kernel source directory: * /usr/src/linux * Found kernel object directory: * /lib/modules/3.10.33/build * Found sources for kernel version: * 3.10.33 * * Please note that this driver only supports graphic cards based on * Evergreen chipset and newer. * This includes the AMD Radeon HD 5400+ series at this moment. * * If your card is older then use x11-drivers/xf86-video-ati * For migration informations please refer to: * http://www.gentoo.org/proj/en/desktop/x/x11/ati-migration-guide.xml * >>> Unpacking source... >>> Unpacking fglrx-installer_14.201.orig.tar.gz to /var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/work ls: cannot access /var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/work/fglrx-*/*.run: No such file or directory >>> Unpacking xvba-sdk-0.74-404001.tar.gz to /var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/work/xvba_sdk >>> Source unpacked in /var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/work >>> Preparing source in /var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/work ... * Applying makefile_compat.patch ... [ ok ] * Applying lano1106_fglrx_intel_iommu.patch ... [ ok ] * Applying lano1106_kcl_agp_13_4.patch ... [ ok ] * Applying lano1106_fglrx-13.8_proc.patch ... [ ok ] * Applying cold-fglrx-3.14-current_euid.patch ... [ ok ] * Applying fglrx_3.17rc6-no_hotplug.patch ... [ ok ] * Applying ati-powermode-opt-path-3.patch ... [ ok ] * Applying ati-drivers-x32_something_something.patch ... [ ok ] * Applying ati-drivers-12.9-KCL_AGP_FindCapsRegisters-stub.patch ... [ ok ] * Applying ati-drivers-13.8-beta-include-seq_file.patch ... [ ok ] * Applying fgl_glxgears-do-not-include-glATI.patch ... [ ok ] * Applying fix-the-linux-3.17-no_hotplug-error.patch ... [ ok ] * Converting 2.6.x/Makefile to use M= instead of SUBDIRS= ... [ ok ] >>> Source prepared. >>> Configuring source in /var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/work ... >>> Source configured. >>> Compiling source in /var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/work ... * Preparing fglrx module make -j3 HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= GCC_VER_MAJ=4 KVER=3.10.33 KDIR=/usr/src/linux 'CFLAGS_MODULE+=-DMODULE -DATI -DFGL' CFLAGS_MODULE+=-DCOMPAT_ALLOC_USER_SPACE=arch_compat_alloc_user_space kmod_build make -C /usr/src/linux M=/var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/work/common/lib/modules/fglrx/build_mod/2.6.x modules make[1]: Entering directory '/usr/src/linux-3.10.33' CC [M] /var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/work/common/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o CC [M] /var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/work/common/lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.o CC [M] /var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/work/common/lib/modules/fglrx/build_mod/2.6.x/kcl_agp.o <command-line>:0:0: warning: "COMPAT_ALLOC_USER_SPACE" redefined [enabled by default] <command-line>:0:0: note: this is the location of the previous definition /var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/work/common/lib/modules/fglrx/build_mod/2.6.x/kcl_agp.c:482:33: error: redefinition of ?KCL_AGP_FindCapsRegisters? int ATI_API_CALL KCL_AGP_FindCapsRegisters(KCL_PCI_DevHandle dev) ^ /var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/work/common/lib/modules/fglrx/build_mod/2.6.x/kcl_agp.c:63:33: note: previous definition of ?KCL_AGP_FindCapsRegisters? was here int ATI_API_CALL KCL_AGP_FindCapsRegisters(KCL_PCI_DevHandle dev) ^ scripts/Makefile.build:308: recipe for target '/var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/work/common/lib/modules/fglrx/build_mod/2.6.x/kcl_agp.o' failed make[2]: *** [/var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/work/common/lib/modules/fglrx/build_mod/2.6.x/kcl_agp.o] Error 1 make[2]: *** Waiting for unfinished jobs.... <command-line>:0:0: warning: "COMPAT_ALLOC_USER_SPACE" redefined [enabled by default] <command-line>:0:0: note: this is the location of the previous definition /var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/work/common/lib/modules/fglrx/build_mod/2.6.x/kcl_acpi.c:832:20: warning: ?KCL_ACPI_Slot_No_Hotplug? defined but not used [-Wunused-function] static acpi_status KCL_ACPI_Slot_No_Hotplug(KCL_ACPI_DevHandle handle, u32 lvl, void *data, void **rv) ^ <command-line>:0:0: warning: "COMPAT_ALLOC_USER_SPACE" redefined [enabled by default] <command-line>:0:0: note: this is the location of the previous definition Makefile:1224: recipe for target '_module_/var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/work/common/lib/modules/fglrx/build_mod/2.6.x' failed make[1]: *** [_module_/var/tmp/portage/x11-drivers/ati-drivers-14.9-r1/work/common/lib/modules/fglrx/build_mod/2.6.x] Error 2 make[1]: Leaving directory '/usr/src/linux-3.10.33' Makefile:89: recipe for target 'kmod_build' failed make: *** [kmod_build] Error 2 * ERROR: x11-drivers/ati-drivers-14.9-r1 failed (compile phase): * emake failed * -
Hmm, not here:
>>> 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/log/portage/x11-drivers:ati-drivers-14.9-r1:20141107-023405.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
# ls /usr/portage/distfiles/fglrx-installer_14.201.orig.tar.gz /usr/portage/distfiles/fglrx-installer_14.201.orig.tar.gz ls /usr/portage/distfiles/xvba-sdk-0.74-404001.tar.gz /usr/portage/distfiles/xvba-sdk-0.74-404001.tar.gz
(manually downloaded, as it says)
Edit: Ah, I see. After resync. All fine now, sorry
-
I had to install sys-power/upower-pm-utils for some reason, I can't remember why now. All works here.
-
I can beat that. I have a pentium3 laptop here with Funtoo, about 1999. It's one of my "backup" computers, I got it for $7.16/free shipping on ebay. Every last thing works perfectly on it, such as it is, even the battery (ni-cad). I never forget what I paid for it because it was listed improperly, like in a black hole, and I had only one competitor that quit at $6.66. I just love predictable people :P. I don't do webkit-gtk on it though.
But even my daily user is a core2 duo laptop, about 2006 vintage. It does help alot that I have an older m/b (laptop) from this computer that can't use a keyboard, making it useless as a laptop, that acts as a distcc slave. No screen. Between the two I nearly match a friend's 4 core AMD (with 1 dead core, 2 crippled at half speed :lol: ).
webkit-gtk: Tue Nov 4 18:22:20 2014: 10459 seconds - 2.9 hours.
libreoffice: Sun Oct 26 02:30:27 2014: 13573 seconds - 3.7 hours
I have quite a complex bash script I've been using for a year or so, backup and update all the computers while I sleep, that is a lifesaver too. Turns them all off at the end, makes kernels, takes care of preserved-rebuild, lots of custom things. I don't share it because it's so very complex and specific to my environment, it would be very difficult to make it one-size fits all. But if you are masochistic let me know, it's not a secret or anything. I wouldn't do it without the backup in case of a sick update, as we get now & then, hah, like today (libtool). But no problems yet.
I have an x86 eee that takes 10 hours for libreoffice, I gave up, the optimization isn't worth it for what little I use libreoffice, had to go for openoffice-bin because libreoffice-bin is always compiled for stable and difficult, sometimes impossible to shoe-horn in to current.
Believe it or not, I hate laptops. Sometimes things just don't work out the way you want...
I ask the OP's forgiveness for contributing to hijacking this thread.
-
I'm using plymouth with vanilla kernel. I've been using it for years and I can tell you, it's always an adventure to set up. And every new upgrade is a toss up, will it work or not? I see the latest upgrade which failed miserably for me months ago is no longer in the tree.
I've seen that 3 squares thing before, but don't recall what it was about. Probably though a framebuffer thing I'm pretty sure. Currently on nvidia here I use VESA vga framebuffer because I'm using an older kernel for other reasons. Prior though I used the newer simplefb framebuffer and that worked also.
I can't comment on the systemd issue except to say it doesn't try to do that here.
Wish I had more to give you.
Well I do have this on my kernel command line: video=uvesafb:1440x900-32,mtrr:3, I forget the details how I came to that and don't know if something like that applies to you
-
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.
- Tassie_Tux and cuchumino
-
2
-
This is the beginning section of my /etc/boot.conf, if it gives any ideas:
boot { generate grub default "And we're gonna have Funtoo!" timeout 3 } display { gfxmode 1440x900x32 background /boot/grub-startup.png } color { normal light-blue/black highlight white/light-blue }The memtest+ could be trickier, some of those things are not yet implemented in boot-update. Although I vaguely recall seeing someone doing it with memtest on the old (now non-existent) funtoo forum.A couple of weeks ago I submitted the following code that adds a loop mounted sysrescuedisk entry to grub. But it's either been trashed or is still in limbo. Probably because the right way to do it would be to submit a patch to boot-update, only I'm not so hot on python, which is what it's coded in. Here it is:#!/bin/bash # boot-fix FILENAME=`ls /opt/sysrcd/systemrescuecd*` sed -i 's/gfxpayload=text/gfxpayload=keep/g' /boot/grub/grub.cfg sed -i 's%set menu_color_highlight=white/light-blue%set menu_color_highlight=white/light-blue\ set color_normal=brown/black%' /boot/grub/grub.cfg sed -i 's%set default%menuentry "SystemRescueCd (isoloop with backstore)" {\ insmod part_gpt\ insmod ext2\ set root=(hostdisk//dev/sda,gpt4)\ loopback loop (hd0,gpt4)'$FILENAME'\ linux (loop)/isolinux/rescue64 setkmap=us backstore=alldev,/opt/sysrcd/sysrcd.bs docache isoloop='$FILENAME'\ initrd (loop)/isolinux/initram.igz\ }\n\ menuentry "SystemRescueCd (isoloop no backstore)" {\ insmod ext2\ insmod part_gpt\ set root=(hostdisk//dev/sda,gpt4)\ loopback loop (hd0,gpt4)'$FILENAME'\ linux (loop)/isolinux/rescue64 setkmap=us backstore=off docache isoloop='$FILENAME'\ initrd (loop)/isolinux/initram.igz\ }\n\ set default%' /boot/grub/grub.cfgIt's a bash bandage with just a bunch of sed statements modifying your grub.cfg after boot-update generates it. If all else fails, you can do something like that. -
Did you check your DNS? That's usually the cause when it hooks up but appears not to go to web pages. If you don't have a terminal app you can get one and do ping www.google.com. Tells whole story. Hmm, guess you'll have to get busybox too if you don't have it for ping, there's probably some app just for pinging, even easier.
-
Drobbins made some improvements to gcc since the 4.6.2 ebuilds, and they are not cross-compile friendly. You have the right idea though, I've been using the Gentoo ebuilds for cross-compiling for over a year now, all works great that way, no fuss once you figure that out. I'm a heavy distcc user with a good assortment of different machines here (including arduino). My 1st mega on the way for this
Um, how much for the hat?
-
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.
-
While the reasoning is sound enough, I must disagree about emerge -1 zlib being the same. This is one of those cases where in theory, theory and practice are the same. In practice they are different...
Not that uncommon, when you see blocks you can get past it with the cheat I mentioned above. This is with NO use changes, just simply pulling it out and letting it reemerge.
That being said, I haven't tried emerge -1 in such a case, perhaps that practice is better than my theory...
-
Hmm, well since it's all centered around zlib, what often works with blocks, etc. is to remove the item and let it reinstall with all else. You can use quickpkg to store the binaries for quick easy reinstall if necessary. A guess, worth a try.
quickpkg zlib emerge --unmerge zlib emerge chromium
-
Perhaps this helps. I have this in /etc/portage/package.use/chromium.use. Some of it's outdated, like I think they dumped aura
>=media-libs/mesa-9.1 gles2 >=sys-libs/zlib-1.2.7 minizip media-video/ffmpeg opus x264 www-client/chromium -tcmalloc aura

ATI Catalyst Black Screen - new install
in Desktop Help
Posted
Well, now not so sure, maybe I was engaging mouth before brain again. Finally got logged into ati machine, thought it used to do that error, but I don't see it.
So instead of helping, just the opposite. Rather than opening mouth again with more nonsense here is the xorg log from that machine, maybe give you a clue.
Did you do aticonfig --initial to set up your xorg.conf?
It does find fglrx anyhow, they say over at the ati bar & grill, but seems it is indicative of something else wrong?