j-g-

Lets clear out some misunderstandings, first there's no such thing as USE="~amd64", ~amd64 is an architecture keyword not an use flag. second I don't think it is that simple as USE="multilib" and emerge again, if you want to use multilib you need a compiler that supports multilib, or so far this has been my understanding regarding this topic, and because of "USE=(multilib)" which means multilib use flag is masked, my guess is OP used a pure64 stage3, I don't know if there's an 'easy and just works' way to switch from pure64 to multilib, so it's likely a reinstall would be less work.

Did you used funtoo stable? I checked the vanilla sources ebuilds, and all have KEYWORDS=~arch, so you might have needed to tell portage you wanted vanilla sources from current since there's no 'stable' version, that is adding 'sys-kernel/vanilla-sources ~amd64' or your ~arch, in /etc/portage/package.accept_keywords, create that file if you don't have it, in the portage(5) manual you will find out about all the files in /etc/portage and their use, but a when you are starting with funtoo you mostly will use package.use and package.accept_keywords, so I recommend you to read about those two files first.

Just a note, you don't need to unmerge and reboot your system just for vlc, you can emerge again anything you have installed before, with something like 'emerge -av category/package', and did you set a flavor and mixins? if you select the desktop or workstation flavor or a graphical desktop mixin the 'X' useflag gets enabled by default. Also did you check the 'alsa' use flag was being used for building vlc? I don't think you actually *need* pulseaudio for vlc.

How come you could download gentoo-sources but not vanilla the command is practically the same, was it something with ACCEPT_KEYWORDS? eselect is what you use to change the /usr/src/linux symlink 'eselect kernel [command]'. Anyway have you considered running a funtoo container instead of running a full VM, considering the amount of compiling you'll be doing later, using a VM in your case(just trying a distro) will be slow and overhead, just to share some ideas, I also happen to run a funtoo vm to mess around with a web server and openrc, and for the compiling and initial setup, I used a loopback device on a raw disk image(made with dd), and created a chroot(I actually used systemd-nspawn) where I compiled and configured funtoo, then I configured and compiled a kernel for it, and used qemu to boot it, and run/test what I wanted, and I switch back to the chroot for upgrades.

You should try a newer kernel(debian-sources or gentoo-sources are good), I think your boot failed because maybe older kernels need a more specific command line, try to change the command line, in the grub menu(F2 or 'c') to 'real_root=/dev/sda1 rootfstype=ext4' but you should really try a newer kernel, I wouldn't use anything bellow 3.4 these days.

I don't think xfce4 mixin enables USE=qt4 gloabally, and you need to tell explicitly you want vlc with qt4, try emerge -av vlc again, and check qt4 USE flag is enabled, if not you can add it to package.use just for vlc or make.conf to enable qt4 globally.

You should read the ifconfig manpage and learn a bit more about it, you're missing some basics, run now 'ifconfig -a' the problem is your interface was down, and don't assume the worst first, anyway you cannot really configure a wireless interface with ifconfig, and I have yet to find out if it's possible with iproute2, so use wireless-tools for testing/configuring wireless interfaces. You really seem to have not configured network interfaces with CLI tools before, do some read, or stick to GUI tools before assuming something is wrong with a tool you don't know.

This is really weird, try to see if udev report any error, run as root 'udevadm monitor' and plug the device, and watch the contents of /proc/net/dev and /proc/net/wireless, I don't think the problem is the kernel, but can try using sys-kernel/gentoo-sources, and use iwconfig from wireless-tools, and ip from iproute2, instead of ifconfig, there might be a bug that's causing this, in which case I can only help you find out what is causing it, it's up to you to report it to the proper people.

At least we know now the kernel is detecting it, What's the output of 'rfkill list' is phy0 blocked? PD: If you ever need to troubleshoot a wireless adapter again, go from bottom to top in this thread, we did it all backwards haha, sorry for that. I really thought from the beginning you didn't even had your driver compiled.

What kernel version are you using? You should also search the specific firmware you need and check it is in /lib/firmware, and boot the kernel to test. I found that blog, when I googled a bit about your device, but it's from 2012, and things have changed since, don't try it, you won't even find the file it's said to edit, anyway a couple of "grep -rin" inside drivers/net/wireless/rt2x00/, in the kernel sources, got me to: drivers/net/wireless/rt2x00/rt2800usb.c, see line 1216, your device its already there. As previously said I'm running a 3.15.* gentoo-sources kernel. Since its a usb device, try when running funtoo(not in chroot), run dmesg without the device, imediatly plug it in, run dmesg again, and see what happened, or post it here. EDIT: I enabled the options you need in my kernel config, basically RT2x00, RT2800USB, RT2800USB_RT3573, and build a tarball, then looking at the drivers built here is a list of the relevant files, created: kernel/drivers/net/wireless/rt2x00/rt2x00lib.ko kernel/drivers/net/wireless/rt2x00/rt2x00usb.ko kernel/drivers/net/wireless/rt2x00/rt2800usb.ko kernel/drivers/net/wireless/rt2x00/rt2800lib.ko So what you need to load is rt2800usb, not rt3573 nor rt3573sta as we were thinking.

If you are not able to run X or connect from a machine (ssh) with X, you can use app-misc/tmux in copy-mode and extract relevant info to save a file you can latter attach/copy, also there's app-text/pastebin or wget-paste to paste logs to pastebin sites directly from the CLI.

This is starting to sound like a firmware problem, you should have then the module rt3573 in /lib/modules/${kernel_version}/, search with `find` in that directory for "rt3573*" just to confirm the *.ko file exist, if is there try to load it, if still nothing, this might be a firmware problem, do you have sys-kernel/linux-firmware installed in your system? I had a problem with firmware not being available to load for a Linksys card too some time ago(I just recalled this, though that was in debian).

The problem is caused by the merge script that generates the funtoo tree, spidermonkey is forked in the funtoo-gnome-overlay[1], and the versions in that overlay override any version that comes from gentoo's tree spidermonkey, I tried to 'emerge -1avp gnome-extra/cjs' on my funtoo and gentoo box, and the gentoo tree does have 'dev-lang/spidermonkey-1.8.5:0/mozjs185', this is the output on funtoo: $ sudo emerge -pav1 gnome-extra/cjs These are the packages that would be merged, in order: Calculating dependencies... done! emerge: there are no ebuilds to satisfy ">=dev-lang/spidermonkey-1.8.5:0". (dependency required by "gnome-extra/cjs-2.2.1" [ebuild]) (dependency required by "gnome-extra/cjs" [argument]) A quick fix would be to get that ebuild from gentoo[2](with the files directory too, patches needed are in there) and put it in your local portage, regenerate the manifest and try to emerge cinnamon again, or wait. Btw, post the output of emerge, it helps identifying faster what's going on (better than paragraphs of prose) once you have seen it some times. EDIT: this has been fixed by dantrell and you just need to update your tree to get the fixes, in a few hours at maximum. [1]https://github.com/funtoo/funtoo-gnome-overlay/tree/master/dev-lang/spidermonkey [2]http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-lang/spidermonkey/

I see now, why this doesn't affect gentoo, thanks for the clarification, anyway it feels wrong for me the fact that ebuild has a depend on another package saying it wants a greater-or-equal version, when later it wants to use only one version, but I'm still trying to learn about ebuilds, and what's right and wrong in them, so maybe that's why I don't get this particular one.

Sandro, I think you could mask '>dev-scheme/guile-1.8' and 'emerge --oneshot' it in the meantime this is fixed. You caused it, really? the ebuild seems unmodified from gentoo(I run both funtoo and gentoo, and checked both portage trees), and it would give the same problem I think,ignore me if I'm wrong: COMMON_DEPEND in '>=dev-scheme/guile-1.8.0:12[deprecated,regex]' wich also is valid for '~guile-2.0' and G2CONF with '--with-guile=1.8'wich causes the build to fail, so wouldn't this be also a bug for gentoo? or was this caused by masks/unmasks in the profiles?

I haven't looked, but from what you got, equery directly looks for the Changelogs in the portage tree, so my guess is the same as yours, I'm not aware if equery is also forked for Funtoo. but lets see if someone who knows best can give some feedback.

I think there's no Changelog in the portage tree for funtoo, since git used for development see [1] at line 491: runShell("( cd %s; find -iname ChangeLog -exec rm -f {} \; )" % tree.root ) I'm still in doubt if there's a way to access Changelog for all the ebuilds that come from gentoo. [1] https://github.com/funtoo/funtoo-overlay/blob/master/funtoo/scripts/merge_utils.py

I didn't compile the default funtoo kernel, but I bet it has CONFIG_IKCONFIG enabled, so look for /proc/config.gz and copy it anywhere, as a backup of your current kernel, if you are going to use the same version you can try building a new configuration to use with genkernel, if you already have the source under /usr/src/linux, you might do something as follows: # zcat /proc/config.gz > /usr/src/linux/.config # cd /usr/src/linux # make menuconfig Using '/' you can get a search dialog, and you can search for 'RT2800PCI_RT35XX'. You'll get something like this: Symbol: RT2800PCI_RT35XX [=y] Type : boolean Prompt: rt2800pci - Include support for rt35xx devices (EXPERIMENTAL) Location: -> Device Drivers -> Network device support (NETDEVICES [=y]) -> Wireless LAN (WLAN [=y]) -> Ralink driver support (RT2X00 [=m]) (1) -> Ralink rt27xx/rt28xx/rt30xx (PCI/PCIe/PCMCIA) support (RT2800PCI [=m]) Defined at drivers/net/wireless/rt2x00/Kconfig:87 Depends on: NETDEVICES [=y] && WLAN [=y] && RT2X00 [=m] && RT2800PCI [=m] you can hit '1' (or if you got more options the number you want) and it will take right to the config section, if you have the Dependencies already enabled, Notice: Depends on: NETDEVICES [=y] && WLAN [=y] && RT2X00 [=m] && RT2800PCI [=m] I Had to enable first those, to be able to see 'CONFIG_RT2800PCI_RT35XX', in my case(I build a only-what-i-need kernel) so my desktop had wireless completely disabled, I don't think that is your case, but, make sure the dependecies for the module you are building are enabled , in this case the last three if you notice above are in the location in cascade, so if you navigate through menuconfig when you enable CONFIG_WLAN you get a submenu where CONFIG_RT2X00 is available, as 'Ralink driver support' : ... < > Softmac Prism54 support <M> Ralink driver support ---> < > Realtek rtlwifi family of devices ---- [ ] TI Wireless LAN support ---- ... And in there is what you need, you can also change 'CONFIG_LOCALVERSION' to something you like, so your anything you have now stays untouched(kernel-image and modules), when you finish save your config, you will be asked for a name, defaults to .config. Then recompile I've never used genkernel to build my kernels so I really don't know it but, funtoo wiki says this should do the work: # genkernel --kernel-config=$YOUR_CONFIG_NAME all I hope this helps you, and give it a read at 'make help' in the kernel source directory, all the 'make *config' and building/packaging options are described there, if you are more curious unpack a kernel tarball under any directory you want as an unprivileged user copy your running config file as mentioned above to the as .config, run make menuconfig and start tweaking, you can even build binary tarballs of your kernel image and modules with 'make tarxz-pkg' as an example before installing anything for real in your system.

If you haven't found out yet you need, to enable 'CONFIG_RT2800PCI_RT35XX' to build it, see [1], the easiest way is to run 'make menuconfig' on your kernel source directory, and use '/' and search for 'RT2800PCI_RT35XX', or go: I'm running a 3.15.3 gentoo-sources kernel, and when I searched with menuconfig, this particular config was marked as 'EXPERIMENTAL', so it seems like recently added, make sure it is actually supported if you're planning to run an older kernel. [1] http://cateee.net/lkddb/web-lkddb/RT2800USB.html

You don't need to boot other OS in order to get a new driver, you should already have the kernel source code on your system, first find out which driver supports your device(google might help you with that) and the name of the kernel configuration variable that enables it, should be something like 'CONFIG_YOURMODULE', then verify its compiled and supported for the specific kernel version you are using, if your hardware is new you might need the latests version you can get. modprobe 'module_name' If you don't have it, you can compile it you just need to enable it in your kernel .config, rebuild and reinstall, no need to reboot if you build it as a module and not inside the kernel image. If you need further help post the hardware model and version, and your kernel configuration.

Don't take my comment as an attack, I don't think users are dumb, the fact is I'm just an user of both gentoo and funtoo, but I'm not here to sugarcoat you, I was pointing you to the problem you have, but here's what I mean you didn't do your homework, installing systemd on gentoo, is knowing you are using 'the second' not the most supported init system, so problems are to be expeted, but to be willing to do a little more research if those problems arise, will save you more trouble and time, you seem to have wanted to install sys-fs/udev and sys-apps/systemd at the same time, but you really wanted sys-apps/systemd and virtual/udev, and if after getting the block you would not just have assumed 'this is broken', and take a look at the ebuild of either systemd or udev (I hope you don't think this is too much for users), taking form the ebuild for sys-fs/udev-215, you can notice: Anyway, I hope you do solve your problem in gentoo, but let me point you also, you hope the funtoo users to not have these kind problems if they want to use systemd, but systemd is not supported by the funtoo developers, I'm using it but I have my local portage handling it and don't expect support for it, so don't use funtoo if you want systemd, however if you look around in the forum, you will see the news of Gnome-3.12 being supported without systemd on funtoo, so you may want to give that a try if Gnome is your reason for using systemd. PD: If we're going to brag about experience and all that, I'm a ~1 year old newbie gentoo user and like ~4 months funtoo user, have been using FLOSS for 5 years now, and just starting college, but I'm curious and don't like to ask unless I'm out of resources of my own.

Sounds like you didn't do your homework before emerging sys-apps/systemd, udev IS part of systemd, so when you compile systemd, also compile udev, but also install virtual/udev so other packages which depend on udev know there's one package providing it, sys-apps/systemd or sys-fs/udev if you will use OpenRC, eudev in the case of Funtoo, all this is pretty much old news...

When it fails? before, during compilation?, paste the output of the failure, but before just to make shure your settings are right, since you say it's a new install, did you edited /etc/locale.gen to match your locale and charset and run locale-gen as root? I was reading some tutorial this week about gentoo vms, mostly unrelated, but it mentioned to do this before trying to update glibc, if you didn't want to take all day long(I guess that meaning troubles).

This is not an error, this is portage telling you that php needs the 'sockets' USE flag enabled and this is required by cact. It is asking for your consent to pull dependencies you haven't explicitly requested, I have run in to portage asking me to do this several times. You only need to do: # echo '>=dev-lang/php-5.5.14:5.5 sockets' >> /etc/portage/package.use and emerge -auvDN @world again. PD: do as the output says too, and `man 5 portage` theres more about, package atoms and USE flags you should know, I'm sure you'll find some things nice you might want to use, portage is pretty awesome.

As I understand your problem is what way to go, for buildg arm binaries, right?, Have you considered cross-compiling?, I played around with the gentoo-prefix image of the gentoo for android project for a while, but my phone is too crappy to do real tests so I got bored. Anyway in my search for a solution to the compilation part, cross compiling seemed the best way to go, portage offers many tools to deal with it, and cross-dev lets you build a cross compiling environment easily once you get what kind of cross-compiler you want(I did a chroot with only a stage3 and a armv7a cross-compiler, so I didn't mess up with my main system), I don't remember the details of the tools now but, basically my goal was to build binary packages, it seemed possible with the tools already available, I didn't got to do the full test, only some test programs I compiled and did worked, so I can't assure all would work, Another way could be distcc combined with cross-compiling.