Emigrated from Debian, Arch (where systemd drove me nuts for its opacity) most recently and installed a @funtoo base system. It seems that I don't understand USE / profiles.
Really enjoying @funtoo so far: compilation isn't too long-winded on my old Core2 quad, quite pleased. Learning a little more than I did with the binary distros so far; which was the aim.
I imagined that when I selected Gnome from the profile mix-ins it would emerge Gnome when I hit "world". Am I doing/not-doing something silly or is this by design?
I headed over to the Gentoo gnome install http://www.gentoo.org/doc/en/gnome-config.xml
and emerged that and it asks me to do various USE changes before I can proceed:
1. do I really put the use changes straight into make.conf or is there a set of files in a '.d' directory about to separate them? (I confess to being a bit of a clean freak!)
2. what does the Gnome mix-in actually do if it doesn't set the system up for gnome?
3. what do I actually need to do before I can install gnome (a webpage signpost would be fine but I have looked and confused myself!).
Thanks everyone in advance.
Last edited by alexpj (2013-03-02 16:33:13)
First off if you read the wiki and the walkthrough it would tell you the same, and no I'm not intending to be rude -) Basically yes you do need to alter your /etc/portage/make.conf file with your chosen editor. What the gnome desktop "flavor" or mix in does is adds some general use flags for your system, and to my knowledge they are pretty basic. What you want to do is take a look at what flavors you have selected as this is probably the easiest way for you. I would suggest setting multiple addons to the desktop/gnome flavor. Such as: media, X, audio, console extras, and whatever else there is (I'm not on my laptop atm, which is what I run funtoo on). What these will do is add some extra built in use flags you will not have to worry about. Although you still need to modify your files such as the make.conf file. I would say if you haven't, make sure to do so, and check out gentoo's documentation on it if you like. There are several options you can set in this file alone, its VERY powerful. For instance you can set your compiling to ram, making things much faster, if you have a good amount of ram that is. Also i will say you should, as i learned, set the use flags for all the picture formats you'll like to use, as well as your IMPUT_DEVICES="sinaptics keyboard" and VIDEO_CARDS="nvidia" < -- thats what i use for my gtx 660m you'll have to look if you have something other then nvidia, and if your using the noveau drivers.. well im not going into that but i run the binary drivers and they work wonderfully with noveau blacklisted on the kernel. (and doing this needs to be done at compile of kernel i believe) Anyhow yes in short you do need to add USE flags they are your entire systems bread and butter. You can add or remove support for tons of things. For example, once you set all your flavor, and addons do an emerge --info and see what it spits out, those will be your built in use flags. To build any kind of GUI desktop you'll need to add the input devices and video cards (as far as i know) and install xorg before you can grab gnome. youll also I imagine want a login and i would say go with slim or some such, even gdm i guess since its gnome. I personally hate gnome but anyhow theres a lot to installing a graphical desktop, I believe there is a guide on the site. A quick rundown would be something like this:
set up your addons
set up your use flags in /etc/portage/make.conf
add your INPUT_DEVICES=" and VIDEO_CARD=" in said file above
do an emerge -avt xorg-x11 (the -avt should show you all the use flags your going to use or not use, i have this set automatically in my make.conf file)
emerge your desktop manager, emerge -avt x11-base/gnome-shell (something like that im not entirely sure)
then off to fun land modifying all of your login manager files, setting up xorg (Xorg -configure , then cp ~/xorg.conf.new /etc/X11/xorg.conf) and please check on all this its coming off the top of my head. There is a ton of stuff you'll need to setup the first time you do this its a bit much, so I highly suggest looking for a guide, and remember gentoo/funtoo = about the same thing. gentoo has a lot of documentation, a loooot.
Anyhow like i said, if u cant find it here, look to gentoo documentation, if im wrong in any of this i do apologize its off the top of my head and im not on my linux box atm. good luck hopefully you get some better imput.
EDIT: Check out this guide, its not exactly what you need but its pretty good, and should give you a general idea, as you can just substitute gnome for xfce:
http://techg3ek.wordpress.com/2012/03/1 … oo-part-2/
Last edited by Xo3ymnI (2013-02-26 09:22:26)
Thanks Xo3ymnI, you've put a lot of effort into your post. Didn't take it as rude; I have read the (Gentoo and Funtoo) wiki and plenty of other places like the one you suggested. That's why I'm confused!
When I look at http://www.funtoo.org/wiki/Xfce it says: "Check that you have enabled the USE flags necessary for a desktop environment. You can either set your profile to "desktop" or you can edit your make.conf:
# nano -w /etc/make.conf
USE="-minimal dbus consolekit jpeg libnotify lock session startup-notification svg thunar udev X"
So it isn't clear whether you do have to play with the USE flags if you've correctly set the profile.
It's clear that you can treat Funtoo as Gentoo and it will work, but I might as well use Gentoo in that case!
ugh.. this is a hard topic for someone new, i went through it so no worries, let me break it down a bit, i tend to go over peoples heads.
Now, yes when you set your profile use "eselect profile list" and see what that throws out. You should get a bit of options, the bottom, the addons, are as i said, you can use more then one. NOW.. these DO NOT replace manually editing your /etc/portage/make.conf file. Bottom line. Sorry . What they do is add common USE flags assoaciated with that particular addon or flavor. As i said, its not enough. First of all have you set your MAKEOPTS="-j*" <-- the * being your processor cores plus one, so if your dual core, it would be 3, dual core w/ hyperthreading = 5, my laptop is an i7 quad core w/ hyperthreading so i use 9. this is parallel processes your computer will compile at once, using those cores to the best of their ability. Funtoo/ Gentoo is a distro for Customization, period. You have the make.conf file for a LOT of this. So in other words yes those flavor's and addons will give you some basic USE flags, you're going to want to add some of your own, there is a list i believe, and as i said, when you emerge, use -avt XXXXX what this does it it shows you what USE flags will be used on each dependency, verbosely (so you can see it, some dont like this) and then it lists the dependencies in a tree so when you run into dependency circles or USE conflicts, it will show you what you need to add / remove for that particular item, example: you emerge something it says x11-extra/gnome-themes requires the USE flag "gtk+ gnome" to be able to emerge it. (this is totally made up) SO.. what you would do is simple, you [echo "x11-extras/gnome-themes gtk+ gnome" >> /etc/portage/package.use] without the brackets. then when you emerge said gnome-themes it will use those extra use flags for that specific emerge. You could also do something like [USE="gtk+ gnome" emerge -avt x11-extras/gnome-themes] this will essesently do the same thing. Now This is really hard for me to explain being as i trial and error everything and learn but your USE flags in /etc/portage/make.conf are what make this distro unique. Say you want a gnome system, that doesnt have to compile kde, ruby, etc.. support into your system? well you simply add those in your USE="-kde -ruby" with the minus in front, and it will compile without support for that and be more custom to your specific needs. Also USE flags are but a fraction of what this file is capable of, like i said you can set your compiling to ram to make it much faster and all sorts of neat stuff. ACCEPT_LICENSE="*" will accept all licenses (opensource or not). These things i type in all caps with an = sign and quotes are called variables. They are very usefull and only time will help you truly understand all of this. Anyhow a little off track but yes, you 100% DO want to tinker with your make.conf file even with your profiles set, and there are more, just type eselect profile list to see them all. Now setting these is going to give you some basic flags that you will most likely need, but as I've said, you want to look up the list of those flags and decide what you want your system to be compatible with, NOTE: using a shit ton of flags will result in tremendeous pain in the ass when emerging things because of dependencies. Too little and you will no doubt run into problems. Are you modifying your other files as well? like /etc/fstab? this can be used to mount tmp directories to ram as well, also very usefull. type "df" to see what is mounted on your system anytime you like as well. Now, depending on what you would like to do, and the hardware, internet settings your using, you want to look through the use flags list and find which ones you def want. Such as jpeg,png,mp3,mp4,wmv,dhcpcd? or networkmanager(more likely with gnome) wicd even? ***(oh and have you made sure to set your default internet using rc-update add dhcpcd/networkmanager/wicd default? [only default one of these!]*** So do you see my point? It's not what everyone else is using for their settings, funtoo is made as is gentoo to be extremely customizable on a PER SYSTEM basis. So just setting the profile is not enough. Also if you [emerge --info] it will list all your current flags. Now you can update system / world if you decide you want to ADD compatibility via more use flags, or take away as well. So a basically small amount of flags is normally used in my case, im unsure of others. As i said though, once you have some of that set, oh and make sure you are using march=native/core2 or some such with the -O pipe as well. That will help and should be in the install doc (i believe). Now that you have a basic idea of what you want, like i said, you will need to first emerge xorg-x11. You must do this before emerging gnome as you'll need a working X window enviornment. once its installed run Xorg -configure and if all goes well it will give you a xorg.conf file and tell you where it is, you'll then move it to the /etc/X11/ folder and procede to emerge your gnome base system, as well as any other programs you might require. Some ways are pretty cut and dry others are not so much so. You should (in my opinion) get a document, or even a book reference for bash commands, this will come in hand, and vim is also a VERY GOOD editor to use, once you learn it that is. Meanwhile i will see if i can find and or put something together as a guide for you, but can you do me a favor and paste your emerge --info, uname -a, this will help me see what your working with. As well as what you have emerged so far, if anything? are you still in the command interface? and is your internet working without chroot etc?
First of all, Welcome to funtoo
Use flags are what sets *ntoo systems apart from others. And funtoo has a unique profile that is far advanced then what gentoo offers at this time. The gentoo documentation is very good to look at, as you see with "eselect profile list" on funtoo is very different then gentoo. Just something to keep in mind when looking at gentoo docs.
Setting gnome in profile will enable the use flags wanted for gnome, when you run "emerge -uavND world" after adding gnome profile, this will build all your installed packages with the gnome use flags.
It will not actually install gnome, allthough you may see several gnome packages being installed because of the flags set.
You need to install gnome still.
emerge gnome-light <<<< will give you a minimal working gnome
emerge @gnome <<<< will give you a full gnome desktop
nano -w /etc/make.conf this is old, and now you want to use nano -w /etc/portage/make.conf
was just a few months ago the file was moved, although you still have /etc/make.conf, when you emerge something portage finds /etc/portage/make.conf first, then ignores /etc/make.conf
So your USE=" is being ignored right now. I normally put very little in USE=" what is put in there means all packages will be built with those flags.
I normally just add flags when a package ask for them, then I put them in /etc/portage/package.use Here is a example
When you emerge a package, or sometimes just a update, and portage tells you the following use changes are required, it will show you a line like above but for your package.
This is telling me that qt-sql wants the mysql use flag. I could put put mysql in /etc/portage/make.conf and all packages that might be affected with that flag would be rebuilt with the new flag. Sometimes you want that, I do set some global.
In this case, I just added that line to package.use and only the package complaining will be built with the flag. This is how you manage your system and keep it lean and clean.
"It's clear that you can treat Funtoo as Gentoo and it will work, but I might as well use Gentoo in that case!"
What is not clear, and certainly you as a new user can not know without using both. funtoo forks many system level packages and keeps them at a sane level for stability.
I will just pick one, sys-fs/udev-197-r9 this is where gentoo is currently at with this package, they update it every week and is often broken and causes issues.
funtoo is at sys-fs/udev-171-r8 This is stable and works well, is silly to update core system packages just because some dev pushed out another broken version. There are many examples where funtoo differs from gentoo. I used gentoo for 5 years before trying funtoo, now all my boxen are funtoo.
Thank you very very much funfool and Xo3ymnI.
Thank you again for the long post.
I'm coming from ArchLinux and multiple Debootstrap builds (script to build a very minimal Debian system) elsewhere so I'm used to and *prefer* customisation, but I've never used gentoo/funtoo before.
My GNU/Linux standard isn't noob, mostly learned through Google and the odd book, but I don't know enough about the start-up internals as I would like as I've been cushioned too much by Debian and Arch.
Word from the wise: Arch wasn't a good experience overall; IMHO young distro trying to be too many things at once. Forum's quite aggressive.
I am most grateful for your post. Easy to read and digest.
I have a booting install and have a running X session AFAICT. I haven't configured syslog-ng properly, Debian uses rsyslog by default, so all the logs look like a hex editor display!
I've emerged gnome but stuck at getting gdm to run.
I've created a new user, alex, which logs in OK. The /messages log file says that I haven't set up pam correctly just after the message for gdm ("could not start the display manager") eg. "pam_get_uid: no such user"
I'm a little lost, I have to say. I'm also starting to panic a little as I have an incomplete desktop with work deadlines approaching!
Can someone please point me in the right direction?
You will certainly learn a lot about linux when you build your own
Sounds like a couple of issues going on here, with the pam error I wonder if you are getting messagaes that you have conf files that need to be updated?
To check, as root run the command. etc-update
If there are any files to update, you can choose -5 and will automajically update them for you. If you had made some custom configs you would not want -5, but I am assuming you do not.
message for gdm ("could not start the display manager")
nano /etc/conf.d/xdm edit "xdm" to "gdm", and then rc-update add xdm default,
Not sure why I wrote that, if you have not done this, would not get the message failed to start.
This really smells like a video driver issue or x is not configured correctly, need to know what video card you are using and what driver you have installed. Since I do not know, going to give a quick walk through to setup a generic vesa driver. I always have vesa around in case my nvidia driver blows up.
VIDEO_CARDS="nv vesa nvidia" <<< this is for my nvidia, you just need to add vesa to your line with whatever you already have.
emerge xorg-server <<<< this will now pull in the vesa driver
eselect opengl list
Available OpenGL implementations:
 nvidia *
you see the * indicates I have nvidia set. If I wanted to use vesa, I would run the command
eselect opengl set 2
Then the * would be on xorg-x11 indicating it was set. eselect is a awesome tool, you use it to switch video drivers, kernels, python, text editors, fonts ... coming from debian you will love eselect.
Now in theory, if you reboot your system will find vesa driver and load it and gdm should start. I am never that lucky. Assuming I set everything up correctly x will still fail to start for me without a xorg.conf.
I know with a modern linux system that xorg.conf is not needed, but without one I always have a problem with x starting and this may be your issue also. let me show you mine.
localhost funfool # cat /etc/X11/xorg.conf
VendorName "NVIDIA Corporation"
BoardName "GeForce 9400 GT"
Without that simple device section in xorg.conf, I will have problems, and the only thing that is correct is nvidia in the example above. That is a old p-4 I am ssh into and it has a fx quadro agp nvidia card in it, using legacy 173.xx drivers. I just copy and paste that section over from this desktop that does have the 9400. Point is, a very simple and not even accurate xorg.conf will work.
So eselect opengl set 2
nano /etc/X11/xorg.conf <<< edit Driver "nvidia" to "vesa"
reboot and that box would boot using vesa drivers, is really that simple to change drivers on gentoo.
Switch to vesa is just a work around, to fix your real problem we need some more info.
emerge --info |wgetpaste
cat /var/log/Xorg.0.log |wgetpaste
cat /etc/portage/make.conf |wgetpaste
lspci -k |wgetpaste
eselect profile list |wgetpaste
Also which kernel did you install?
wgetpaste is another awesome tool, will create a url and you post the url here and we can see these files. Just some ideas for you to try.
Funfool, I thank you, truly lol. I am not very good at explaining things in such simple terms. When I said check out the gentoo documentation, I was more refering to the making of the /etc/portage/make.conf file and setting that up correctly. Also if your screen is not being recognized I have had this problem where xorg will try and use several displays, I would since therefore remove all but the one needed. Again I do apologize if this is over your head, and as I said, coming from arch is a VERY good learning curve for jumping into gentoo/funtoo as I did. Reguardless, Vi/Vim are very very complicated and whereas you can use nano, I personally prefer Vim and Vi but I still find myself using my Vi/Vim reference book sometimes, as well as bash scripting/programing book as well. I didn't intend you to take it as you need it, but I personally find it very useful at times is all. Now as Funfool has said, and myself as well, we use a minimal amount of USE flags for the most part. Yet when you need to I personally prefer to just echo into the /etc/portage/profile.use instead of adding it manually since I'm lazy. If your using a laptop I would highly suggest using pcmcia as a use flag. If its a desktop you shouldn't need it i don't believe. You might want to go through the steps of manually editing all your files again, I like to enable hotpluging, As i wouldn't recommend this, I have yet to see problems from it. Also using emerge --ask --verbose --pretend is a nice tool to use, it will show you what use flags are depending on what when you use say, emerge -avtp xorg-x11. Now say you see a use flag that you may want, but is not being used? you can either stick that in your package.use or add it to your main system, its totally up to you. Once you build one or two (took me a few) you will understand the workings of your system ten fold from what arch will teach you. Personally, I'm using xfce as my "base" yet i have gtk+ , gnome, and other pieces all thrown together for my desktop enviornment, with slim as my login manager and once i had everything as i liked it, its very stable, very smooth and very customizable and I absolutely love funtoo. I have also worked with gentoo a lot as well. What he is saying above is very good advice, I'm not very good with explaining things that simply come naturally to me after so much trial and error, I daresay I might look at a handbook once or twice for a specific code. So just to give you a general idea, This isnt a distro that says here you go, pick what you want and click a button done deal. As im sure you could do something similar, thats not the point at all. You will learn a LOT about how your system works, what makes it work, what you can alter in what files to make said changes to said component. If you are using nvidia, I would highly suggest that if you had not blacklisted nouveau before compiling your kernel, do so now, vim (or nano -w) /etc/modprobe.d/blacklist.conf , then go down to the bottom and add the line without a # before it as so:
(I'm not sure on that spelling and I use the capital and non just to be sure)
and now you can recompile your kernel with the VIDEO_CARDS="nvidia vesa(if u want)" and INPUT_DEVICES="(usually a keyboard and mouse is enough, synaptics for laptops udev(maybe)"
Then procede to recompile your kernel, now emerge your nvidia-drivers and nvidia-settings
you can then emerge your xorg-x11
now u can either use Xorg -configure as I've said, and then nvidia-xconfig, although nvidia-xconfig may work by itself.
YOU DONT HAVE TO DO THIS! Its just what i did and i personally like the newest binarys from nvidia as they work miracles for my system.
Also yes when u type eselect profile list, there will be a lot there, including as stated above glx settings etc you can set to nvidia
Oh and dont forget to etc-profile && source /etc/profile when making large changes. If you have any further questions, specific ones, i would be happy to assist, alas im not very good with specific information but I do hope you dont give up its a lot to master but once you have done so its 100% worth it trust me. I understand more of my computers inner systems than i have in 15 years of using windows. In fact I only use it for school and games. Hard work pays off, and when you start to understand you will be able to tweak your system to run faster than you would have immagined possible. Funfool has some great information for you, wheras im not great with explaining things, i run headfirst and figure them out myself and its like speaking alien to others! Anyway as i said, any questions, or one you have everything up and running just ask and i can give you at least some nice tweaks
Dear funfool et al,
I've just realised that I'm making life difficult for you to help me! Sorry.
So whilst I work through your last message I thought I'd better post the interesting bit of my messages log:
Feb 27 20:06:01 sydney sshd: Server listening on 0.0.0.0 port 22. Feb 27 20:06:01 sydney sshd: Server listening on :: port 22. Feb 27 20:06:01 sydney gdm: CRITICAL: error getting system bus: Could not connect: No such file or directory .. Feb 27 20:06:22 sydney /etc/init.d/xdm: start-stop-daemon: failed to start `/usr/bin/gdm' Feb 27 20:06:22 sydney /etc/init.d/xdm: ERROR: could not start the Display Manager Feb 27 20:06:39 sydney login: pam_unix(login:session): session opened for user root by LOGIN(uid=0) Feb 27 20:06:39 sydney gnome-keyring-daemon: couldn't create socket directory: No such file or directory Feb 27 20:06:39 sydney gnome-keyring-daemon: couldn't bind to control socket: /root/.cache/keyring-r2zWx3/control: No such file or directory Feb 27 20:06:39 sydney login: ROOT LOGIN on '/dev/tty1'
I have this feeling that this is going to get embarrassing fairly soon for me!
[I'm going to edit this message multiple times as I work through your list.]
etc-update gave nothing interesting; with -5 (--automode) or not.
/etc/conf.d/xdm had already been edited to make it gdm, but I couldn't remember whether I added "xdm default" or "gdm default" or both on washdays! "rc-update list" just now gave "xdm" in the service list.
I have an Intel integrated graphics board with a standard 965 chip. It's not new and had Arch on it.
(make.conf) VIDEO_CARDS="intel vesa fbdev" INPUT_DEVICES="evdev keyboard mouse" there isn't anything else in make besides the compiler stuff.
I used http://www.funtoo.org/wiki/Funtoo_Linux … teps#X.Org to make sure I could get into X; I had ball (not) getting the intel drivers compiled, didn't come in of their own accord. Lots of messages in the xorg logs but got there eventually!
Curiously "eselect opengl list" only gives xorg-x11 not the intel driver I was now expecting .. I haven't encountered this eselect before you posted.
I've haven't needed a full xorg.conf since my early days of Debian, but when the Intel drivers started to include the special sandybridge modes I created a partial section. Gimme a few minutes and I'll put it back in:
I've stuffed it in /etc like you; there's no /xorg.conf.d ?
Didn't do anything helpful, same timeout.
I installed the kernel.org kernel after a brief dalliance with the gentoo-sources. I am running system root in a subvolume of a btrfs file system with big nodes so need a 3.4+ kernel; /boot is on ext4 btw. Can't do Debian-sources until the freeze is off as it is stuck at 3.2. I usually install extlinux in preference to grub2 but I have a happy boot. The only thing it is upset about is that ntpd starts before the network is open and I think I've seen how to add a dependency in somewhere. Not a big deal at present.
Tasks complete, sir.
Last edited by alexpj (2013-02-27 21:25:26)
It's very hard to read your text in one great lump; but what you're writing is helpful. I hope you're not offended, perhaps you were an old-time lawyer in a past life!
I am just starting to use Vim: my log/messages file was seen as binary and so it went into hex editor mode, and confused the hell out of me. Nano was a more sane option.
It's not true that you're not good at explaining yourself at all; I've been assisted by your posts no end.
I'm very stuck now. So tempted to dump the frigging thing and start again!.
ok is fine, we are still missing some logs and want you to paste them
lspci -k |wgetpaste <<< is important because shows your hardware and what drivers are in use.
cat /var/log/Xorg.0.log |wgetpaste <<<< will show us the errors why x did not start
For intel drivers, eselect opengl list will only show xorg-x11, will only see other options if you have nvidia or ati, so that is fine.
You will not need to add anything or make a xorg.conf file for intel, just something I visually understand with external kernel drivers where udev does not see them nvidia ati, while intel is built into the kernel. and you may need to add intel to your kernel along with kms this will help http://wiki.gentoo.org/wiki/Intel
Sometimes it helps to run the command as root, /etc/init.d/xdm restart is sometimes if you do not have all processes in rc-update set correct, some things will fail to load because something else is not started yet.
Not a big secret, and do not want to discourage you in any way. I started on a gentoo system and learned it's ways. I have since tried a few debian installs and just makes me want to pull my hair out how they make things so difficult.
rc-update is also a *ntoo specific application, and is how you set up specific applications to start on boot. for example xdm, samba, sshd, and you have different choices to start one before another by which run level you put them in.
rc-update add xdm default would be standard and where it goes.
So while you are gathering the other logs above, another log to add would be.
rc-update show -v |wgetpaste
Perhaps I wasn't clear:
http://bpaste.net/show/80303 emerge --info |wgetpaste
http://bpaste.net/show/80304 cat /var/log/Xorg.0.log |wgetpaste
http://bpaste.net/show/80305 cat /etc/portage/make.conf |wgetpaste
http://bpaste.net/show/80306 lspci -k |wgetpaste
http://bpaste.net/show/80307 eselect profile list |wgetpaste
I'm starting to think it is really something quite simple; install order or something.
I've had a look at the logs nd I must be missing something; even the xorg log errors occur after the system has found the mouse. Perhaps the udev is unhappy though.
There might be a clue with the aspid fail perhaps in the initial log I posted? Don't know what it does really.
Sorry - clutching at straws. Debian is a dream to debug compared to this! I didn't usually have a problems with a merged Unstable/experimental system, and switched to Arch to avoid the long freezes debian has and play wih btrfs.
[Off topic: don't mkfs.btrfs with the default leaf size of 4k, use 32k; fragments too quickly for the autorefrag system to cope. But it's bomb proof, worst I've had to do is clear the log after multiple power failures and all the data/checksum was still there.]
Kind regards and thank you for your continued patience.
Last edited by alexpj (2013-02-28 01:22:59)
OK.. so lets go over a few things that will help you immensly i have no doubt.
1st. Have you (or have you not) emerged gnome, gdm, xorg?
2nd. What, as i see your using an integrated graphics device from your motherboard, is your video card? is there anything OTHER then the intel integrated graphics? like a radeon or nvidia card it lists on your (im assuming) laptop?
3rd. You clearly (even when its listed in your emerge --info) should manually set in your /etc/portage/make.conf file your:
VIDEO_CARDS="intel (and if its say, some nvidia card integrated, or radeon) nvidia or radeon and vesa to be safe i would think"
INPUT_DEVICES="synaptics(if your using a toutchpad via laptop) mouse keyboard evdev"
4th. What kernel are you using? did you use genkernel? did you build your own? did you use the binary debian-sources?(by far the best option for you i would assume, and its pretty stable until your comfurtable enough to build your own)
5th. As for vim your getting weird characters because you didn't build compatibility into it im thinking, mine has color coded coding and works wonders.. nano is fine tho its your choice.
6th. I would suggest you do the following, since you have a basic idea of what you want, I would personally just boot up your sysrecoverycd and fire up fdisk and delete everything, re-partition and reinstall using the guide step by step. Make sure to edit EVERY file by hand, check documentation for said files while you do so. Once you have a respectable base system, go to the next section of "what to do now" and continue to emerge more tools / utilities you will need / want. This should also get you a xorg-x11 install. Once xorg is installed you can run Xorg -configure as I've said before, move the file to /etc/X11/xorg.conf and let it be for a moment. You now want to emerge your gnome-base, your login manager (slim,gdm,etc..) following the documentation for each said part. Just follow the documentation as you go, once you get to installing your desktop GUI, google the specific things you want and it will help you echo your startx so that works, as well as setup your login manager to load in your default runlevel instead of command.
:: If you dont want to start over thats understandable but i think at this point it would be best (just my oppinion) I installed Gentoo more then a few times before i finally had a working GUI, and now i find i like and use Funtoo but I still refer to things i learned from those installs. I also use the debian sources on a fresh install to help speed things along, then build a kernel when i have the time. I love funtoo for this its very effecient. Choice is yours but thats my two cents. Of course you dont have to do this, and some would say you dont need to, but personally I like hands on practice and I learn more by doing things so installing once or twice or even three times before i had an install i was happy with, and understood the mechanics and system much much better by this point was good for me. Also you may want to change the following if your not going to reinstall , or even if u do:
ACCEPT_KEYWORDS="amd64 ~amd64" <-- using the unstable branch(~amd4) may not be such a great idea. using simply "amd64" might work better. Again, im not a leading authority on these things!
ACCEPT_LICENSE="* -@EULA" <-- changing this to "*" will let you emerge anything such as flash and adobe reader etc.. personal opinion
CFLAGS="-march=native -O2 -pipe" <-- you could i believe use core2 instead of native, native isnt the best march IMO.
Just my thoughts, I hope they help and yeah I do tend to type faster then I think sometimes sorry they are long posts. EDIT: Personally i would just use ext4 for all but your boot partition and use ext2 for that, thats what i do anyhow.
Last edited by Xo3ymnI (2013-02-28 02:03:19)
Nice post and we now have some logs to work with
First thing I see is lspci -k, we see your video card
00:02.0 VGA compatible controller: Intel Corporation 82G965 Integrated Graphics Controller (rev 02)
Subsystem: Intel Corporation Device 514d
But take a look at the complete file yourself, you will see your other hardware and the kernel driver loaded for that hardware. your vga has no driver.
Just an example look at your sound card
Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
Subsystem: Intel Corporation Device 2504
Kernel driver in use: snd_hda_intel
It shows kernel driver in use, your vga does not show a driver in use. So we now know is a driver issue. But something is weird here and trying to put my finger on it.
I see no reason to consider a fresh install at this time, we just need to get x working, and no disrespect to you. Is very simple to set up intel, at same time is very easy to screw it up.
My only point here is, would take pages to post how many times and different ways I have screwed up x. I just see no reason to consider a new install.
rc-update add dbus default
rc-update add consolekit default
these 2 things may be all you need, I hear consolekit is not needed, my system always complains if not added to a run level. Also
If you ever want to join freenode #funtoo, you will find me there and a large assortment of helpful people, we could probably fix this issue in a few minutes. bbut we can also fix this over a forum, just takes longer.
Deeply sorry both. I didn't see the email's notifying me of the new posts, and as I write I haven't looked though them properly.
I have a feeling that I consulted too many posts and web pages whilst progressing my system install and ended up messing the whole thing up in some quite obscure way.
I'm going to head off to bed now, it's 02:20, and have a proper look though your posts tomorrow, if that's ok: I'm still wondering how I missed the email advice!
Thank you both so much for your patience and good kind words.
I will see you on #freenode, if only just to say "thank you".
On the plus side I think I understand USE flags, but not quite how funtoo manipulates/presents them to the system through the profiles quite yet. It's explained fairly clearly in the wiki so I'll have to follow the code sometime.
Meanwhile my packages.use got boosted by an emerge "--autounmask-write" flag which after taking the "._" filename prefix out was prettier and more accurate than me trying to retype the ">=<package name> .." bollox. I'm used to .pacnew so understand what it's indicating; but not quite fluent enough with diff yet!
I'm loving the completeness (?word?) of funtoo; it's not quite there in Arch. Hell of a leaning curve, but I'm a glutton for that anyway!
Last edited by alexpj (2013-03-01 02:37:11)
Hi Xo3ymnI fella,
Yes, all three. Gnome included gdm though.
Standard fare Intel 965 as indicated. No, no other card on my desktop.
as indicated vanilla-sources; compiled using the Funtoo wiki on kernels with genkernel. As I said I can't use the debian-sources, whcih is at 3.2, as I run btrfs with large leaves: it was most of the reason for going to Arch in the first place . vanilla-sources wasn't hard but that's a testiment to Funtoo/Gentoo not me! I made the minimum config changes I could (clock, btrfs, KMS and NFS i think.)
vim incorrectly saw the log files as binary as I said, and went to hex mode. I can't use either nano or vim properly! Learning to use vim. Nano/less saw my log file as text and so I used that.
Good call; so I did. I agree with funfool that is was a driver issue but I couldn't work out where. I am pretty sure that I messed it up going through the Xorg tutorial on the Funtoo wiki and combining it with other posts/pages on the gnome subject.
As funfool said, he gets X recognising two cards when running through the X config; so did I. I did the X -configure but didn't actully put it in the right place/rename it as X has always recently been able to self config on the fly with Debian and Arch and it's the same X!
I emerged X and then gnome. And it worked. I am really sorry for messing you two about.
Thank you for this helpful post; well observed. After I saw that I went through the system looking at what is stopping the machine recognising the driver cos it is/was there. Didn't find anything particularly, but have the thing in a btrfs snapshot for when I understand what I'm doing a little better.
I had tried to emerge the whole set of drivers (how do you emerge a category btw?) but eventually just did the basic driver. After wipeing and starting again I emerged the VLA driver too. I was so pleased when I rebooted and the KMS kicked it into a decent console text mode, I knew I was on my way.
After that I just emerged Gnome and set up openrc with (your) dbus and consolekit (hint, thank you) and away it went. I have never been so happy to see a spinning cursor the first time!
So I have a very basic Gnome setup, a big smile, and a pending VAT return for a week yesterday. Thank you.
Silly thing is that I dabble in the law and spend most of my time looking for the missing element, but not skilled enough to 'see' it as you did. <tips hat>
I now have a million and one questions other about emerge e.g. does /etc/portage/bashrc hook script work with zsh? I guess it should as it's just a name and not particulaly linked to bash per se. I've used etckeeper for a while and Arch was annoying as there are no hooks yet in pacman to hook it to; guess what hooks in emerge!
I'm off to get LibreOffice and VirtualBox running before the weekend's over.
I hope I'm not too annoying on the IRC ...