View previous topic :: View next topic |
Author |
Message |
PeggySue n00b
Joined: 19 Dec 2009 Posts: 73 Location: Devon, UK
|
Posted: Mon Dec 28, 2009 12:47 pm Post subject: Xorg Install failed - Missing directories? |
|
|
With more than a little help from the forums I have built a Gentoo system from the minimal install disk and stage 3 over the internet on my Dell Vostro 1000 laptop. My next step is to install X.
I followed the handbook and
Device Drivers --->
Input device support --->
<*> Event interface
is enabled in my kernel.
I set
INPUT_DEVICES="evdev synaptics"
VIDEO_CARDS="radeon"
in make.conf and did emerge xorg-server, env-update and source /etc/profile.
Next came a trial startx which flashed the screen a couple of times and then returned to the command line. My Xorg log suggests that my Radeon Xpress 200M graphics was found and the correct driver loaded but the mouse and keboard modules weren't found.
I have pasted the log to http://pastebin.com/m31cc8b12
The instructions to get a basic keyboard/mouse combination say
Code: | # cp /usr/share/hal/fdi/policy/10osvendor/10-input-policy.fdi /etc/hal/fdi/policy
# cp /usr/share/hal/fdi/policy/10osvendor/10-x11-input.fdi /etc/hal/fdi/policy
|
but there is no /usr/share/hal directory. Also no /etc/hal or /etc/X11 directories. The only xorg.conf files are in /usr/... directories. I was expecting a xorg.conf (with default values) in /etc/X11.
There was only one thing to check; one file to update and three commands to give. Any ideas what could I have done wrong here please??
P.S. I am assuming I need X working to be able to use the Firefox browser. I want a decent browser on my laptop so I can debug my wireless connection without having to be at the desktop for the internet. (Links isn't good enough). _________________ My time machine is broken which is odd because it was working tomorrow. |
|
Back to top |
|
|
sera Retired Dev
Joined: 29 Feb 2008 Posts: 1017 Location: CET
|
Posted: Mon Dec 28, 2009 1:07 pm Post subject: |
|
|
Do you have hal and dbus installed?
Code: | emerge -pv hal dbus |
to check if the case. You might want to probably set the hal and dbus useflag globally.
Make sure hald and dbus are in the default runlevel and started successfully. Use and for this.
You do only need a policy file if you want to use a non us keyboard layout.
How does your xorg.conf look like? Ever tried without one? |
|
Back to top |
|
|
PeggySue n00b
Joined: 19 Dec 2009 Posts: 73 Location: Devon, UK
|
Posted: Mon Dec 28, 2009 4:59 pm Post subject: |
|
|
Hi sera,
The pretend emerge said it would install hal and dbus so I did that. I assume I should put hal and dbus in my make.conf USE Flags to set them globally, so I will do this.
"/etc/init.d/hald start" started hald but "/etc/init.d/dbus start" didn't start dbus it so I did a reboot! hald and dbus were not in the default run level so I used rc-update add hald default (and dbus). hald and dbus are now started and in the default run level.
I copied across the fdi policies (I am using a UK keyboard) and did startx but the output was the same. (No mouse, kbd, xterm etc.).
I am running without an xorg.conf. I have been following the instruction manual and one isn't created. I don't even have an X11 directory.
If hal and dbus are required is there an omission in the instructions? and how should I report that?
Thanks. _________________ My time machine is broken which is odd because it was working tomorrow. |
|
Back to top |
|
|
dtjohnst Apprentice
Joined: 23 Apr 2006 Posts: 178
|
Posted: Mon Dec 28, 2009 6:29 pm Post subject: |
|
|
I don't know which walkthrough/howto you're using, but I'd recommend this one:
http://www.gentoo.org/doc/en/xorg-config.xml
It does mention HAL. More importantly is the Xorg -configure section which will create an xorg.conf for you. |
|
Back to top |
|
|
PeggySue n00b
Joined: 19 Dec 2009 Posts: 73 Location: Devon, UK
|
Posted: Mon Dec 28, 2009 6:56 pm Post subject: |
|
|
Yes. That's the instructions I am following. It does mention hal but I should have said it doesn't mention installing Hal or dbus. I am only installing the packages called for by the instructions. I have no knowledge of the dependencies.
I get as far as
Quote: | For example, to get a basic working keyboard/mouse combination, you could copy the following files to /etc/hal/fdi/policy/: |
and I don't get a valid keyboard or mouse.
Later the instructions refer to creating an xorg.conf but the initial system install taught me to take each step at a time and get it right; anything else would colapse in a heap!
Some say xorg.conf shouldn't be required but I will push on and make one to see what happens. _________________ My time machine is broken which is odd because it was working tomorrow. |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
|
Back to top |
|
|
PeggySue n00b
Joined: 19 Dec 2009 Posts: 73 Location: Devon, UK
|
Posted: Mon Dec 28, 2009 7:23 pm Post subject: |
|
|
I moved on. Tried the Xorg -configure (after editing 10-x11-input for ctrl_alt_bksp) and then X -config /root/xorg.conf.new.
I got a blank screen; no mouse or keyboard and no way out. Ctrl-Z, Ctrl-C and Ctrl-Alt-Bksp have no response. As you might expect if you have no keyboard!! _________________ My time machine is broken which is odd because it was working tomorrow. |
|
Back to top |
|
|
PeggySue n00b
Joined: 19 Dec 2009 Posts: 73 Location: Devon, UK
|
Posted: Mon Dec 28, 2009 7:26 pm Post subject: |
|
|
Hi Donahue,
Thanks for the tips. The links look interesting and differ from the basic instructions. I will give it a go tomorrow.
Thanks. _________________ My time machine is broken which is odd because it was working tomorrow. |
|
Back to top |
|
|
Total MAdMaN n00b
Joined: 04 Aug 2009 Posts: 14
|
Posted: Mon Dec 28, 2009 8:01 pm Post subject: |
|
|
PeggySue wrote: | I moved on. Tried the Xorg -configure (after editing 10-x11-input for ctrl_alt_bksp) and then X -config /root/xorg.conf.new.
I got a blank screen; no mouse or keyboard and no way out. Ctrl-Z, Ctrl-C and Ctrl-Alt-Bksp have no response. As you might expect if you have no keyboard!! |
The blank screen is because twm is no longer installed by default when installing X (the documentation is a little out of date). To be able to test whether X is working properly you need to install a window manager and edit XSESSION as DONAHUE mentions. |
|
Back to top |
|
|
dtjohnst Apprentice
Joined: 23 Apr 2006 Posts: 178
|
Posted: Mon Dec 28, 2009 8:14 pm Post subject: |
|
|
PeggySue wrote: | I moved on. Tried the Xorg -configure (after editing 10-x11-input for ctrl_alt_bksp) and then X -config /root/xorg.conf.new.
I got a blank screen; no mouse or keyboard and no way out. Ctrl-Z, Ctrl-C and Ctrl-Alt-Bksp have no response. As you might expect if you have no keyboard!! |
Sometimes you don't need an xorg.conf, but if things aren't working, it might sort them out. I once fixed no kb/mouse problems by adding
Code: | Option "AutoAddDevices" "false"
|
to my xorg.conf ServerFlags section...but I haven't ran an xorg in awhile on that machine to know if what had caused that issue is resolved. Might be worth trying if none of those links pan out.
Also, if Xorg loads again and leaves you with no kb, you could try CRTL-ALT-F1 (or F2, F3, etc) to switch to a console window and either CTRL-C once you're on the console you ran X from or use ps to find the task and kill it... If nothing else, that should save you from being trapped with no way out. As far as my memory serves me, that works even when X is being ornery. |
|
Back to top |
|
|
cach0rr0 Bodhisattva
Joined: 13 Nov 2008 Posts: 4123 Location: Houston, Republic of Texas
|
Posted: Mon Dec 28, 2009 11:21 pm Post subject: |
|
|
IIRC adding
Code: |
Option "AutoAddDevices" "false"
|
disables hal in X
I'd be keen to see output of
Code: |
equery hasuse hal |grep x11
|
if hal and dbus were added to USE flags *after* xorg was emerged, it will make no difference; need to remerge xorg after adding those flags
for reference
Code: |
# equery hasuse hal |grep x11
x11-apps/xinit-1.0.8-r4
x11-base/xorg-server-1.6.3.901-r2 |
_________________ Lost configuring your system?
dump lspci -n here | see Pappy's guide | Link Stash |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Tue Dec 29, 2009 2:23 am Post subject: |
|
|
My kernel config for radeon driver:
Quote: | Bus options (PCI etc.) --->
[*] PCI support
[*] Support mmconfig PCI config space access
[*] Support for DMA Remapping Devices (EXPERIMENTAL)
[ ] Enable DMA Remapping Devices by default
[*] Support for Graphics workaround
[*] Support for Interrupt Remapping (EXPERIMENTAL)
[*] PCI Express support
< > PCI Express Hotplug driver
[*] Root Port Advanced Error Reporting support
[ ] PCI Express ASPM support(Experimental)
-*- Message Signaled Interrupts (MSI and MSI-X)
[*] Enable deprecated pci_find_* API
[ ] PCI Debugging
< > PCI Stub driver
[*] Interrupts on hypertransport devices
[ ] PCI IOV support
<*> PCCard (PCMCIA/CardBus) support --->
<*> Support for PCI Hotplug --->
Graphics support --->
-*- /dev/agpgart (AGP Support) --->
<M> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support
--- Direct Rendering Manager (XFree86 4.1.0 and higher DRI support
< > 3dfx Banshee/Voodoo3+
< > ATI Rage 128
<M> ATI Radeon
< > Matrox g200/g400
< > SiS video cards
< > Via unichrome video cards
< > Savage video cards
< > Lowlevel video output switch controls
<*> Support for frame buffer devices --->
--- Support for frame buffer devices
[*] Enable firmware EDID
[ ] Framebuffer foreign endianness support --
-*- Enable Video Mode Handling Helpers
[*] Enable Tile Blitting Support
*** Frame buffer hardware drivers ***
< > Cirrus Logic
< > Permedia2 support
< > CyberPro 2000/2010/5000 support
< > Arc Monochrome LCD board support
[ ] Asiliant (Chips) 69000 display support
[ ] IMS Twin Turbo display support
< > VGA 16-color graphics support
< > Userspace VESA VGA graphics support
[*] VESA VGA graphics support
< > N411 Apollo/Hecuba devkit support
< > Hercules mono graphics support
< > Epson S1D13XXX framebuffer support
< > nVidia Framebuffer Support
< > nVidia Riva support
< > Intel LE80578 (Vermilion) support
< > Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965GM support (EX
< > Matrox acceleration
< > ATI Radeon display support
< > ATI Rage128 display support
< > ATI Mach64 display support
< > S3 Trio/Virge support
< > S3 Savage support
< > SiS/XGI display support
< > VIA UniChrome (Pro) and Chrome9 display support
< > NeoMagic display support
< > IMG Kyro support
< > 3Dfx Banshee/Voodoo3/Voodoo5 display support
< > 3Dfx Voodoo Graphics (sst1) support
< > VIA VT8623 support
< > Trident support
< > ARK 2000PV support
< > Permedia3 support (EXPERIMENTAL)
< > Fujitsu carmine frame buffer support
[ ] AMD Geode family framebuffer support (EXPERIMENTAL)
< > Virtual Frame Buffer support (ONLY FOR TESTING!)
< > E-Ink Metronome/8track controller support
< > Fujitsu MB862xx GDC support
[*] Backlight & LCD device support --->
--- Backlight & LCD device support
< > Lowlevel LCD controls
<*> Lowlevel Backlight controls
< > Generic (aka Sharp Corgi) Backlight Driver (DEPRECATED)
< > Frontpath ProGear Backlight Driver
< > MacBook Pro Nvidia Backlight Driver
< > Tabletkiosk Sahara Touch-iT Backlight Driver
Display device support --->
Console display driver support --->
-*- VGA text console
[*] Enable Scrollback Buffer in System RAM
(1024) Scrollback Buffer Size (in KB)
<*> Framebuffer Console support
[ ] Map the console to the primary display device
[ ] Framebuffer Console Rotation
[ ] Select compiled-in fonts
[*] Bootup logo --->
--- Bootup logo
[ ] Standard black and white Linux logo
[ ] Standard 16-color Linux logo
[*] Standard 224-color Linux logo |
|
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Tue Dec 29, 2009 4:18 am Post subject: |
|
|
This check list has helped me (and others):
If: Code: | grep -i evdev /usr/src/linux/.config | does not produce Quote: | CONFIG_INPUT_EVDEV=y | you need to add evdev support to the kernel.
If: Code: | grep -i evdev /etc/make.conf | does not produce Quote: | INPUT_DEVICES="evdev" | you need to edit make.conf to add evdev to INPUT_DEVICES="
If: Code: | grep -i DISPLAYMANAGER /etc/conf.d/xdm | does not produce Quote: | DISPLAYMANAGER="xdm" | (or some other display manager of your choice that you know you have emerged), you need to edit /etc/conf.d/xdm to add DISPLAYMANAGER="xdm" (or DISPLAYMANAGER="<some other display manager of your choice that you emerged>")
If: Code: | grep -i hal /etc/make.conf | does not produceyou need to edit make.conf to add hal to USE="
Make any repairs found needed above, then run:
Code: | echo "XSESSION=Gnome" > /etc/env.d/90xsession #replace Gnome with your choice as appropriate
env-update
source /etc/profile
emerge -uND dbus hal xorg-server xf86-input-evdev xf86-video-ati gentoolkit
rc-update add dbus default
rc-update add hald default
cp /etc/X11/xorg.conf /etc/X11/xorg.conf.old
rm /etc/X11/xorg.conf
reboot |
To see if X will start with no xorg.config:
Last edited by DONAHUE on Tue Dec 29, 2009 2:28 pm; edited 1 time in total |
|
Back to top |
|
|
sera Retired Dev
Joined: 29 Feb 2008 Posts: 1017 Location: CET
|
Posted: Tue Dec 29, 2009 8:50 am Post subject: |
|
|
PeggySue,
dbus is not necessarily needed for X itself, but a lot of applications running in X will make use of it. You most likely want it, as I guess otherwise applications won't behave as you expect them to.
Not having hal and dbus in your useflags most likely means you are not using the desktop profile. The desktop profile is meant as a solid base for gentoo being used with X. I recommend using it at least till you get more familiar with gentoo. Code: | eselect profile list
eselect profile set <number of profile seen in previous command> |
About what needs to be done:
After you have added the hal and dbus useflags to /etc/make.conf and or have switched profile, you should run Code: | emerge -avuND world | to make sure all packages are built with new set of useflags.
Then Quote: | emerge -av $(qlist -IC x11-drivers) | to reinstall all drivers, just in case they need to be rebuilt after rebuilding X.
The qlist command is part of app-portage/portage-utils. You might need to install it. Code: | emerge -av portage-utils |
Testing X now is not as simple as you can see and a DM is your goal anyway.
So without testing X for the moment install your desktop and login manager.
As an example Quote: | emerge -av gnome gdm |
Then replace xdm with gdm in /etc/conf.d/xdm.
Now try /etc/init.d/xdm start.
Without doing anything beside the above I installed 3 machines the last halve year and it always worked out of the box.
Setting XSession an such is simply not necessary on a default setup. Gdm will see all your DM on it's own, etc.
Adding an xorg.conf later to set default resolution and such was necessary.
Finally if /etc/init.d/xdm start works, add it to the default runlevel.
Code: | rc-update add xdm default |
Instead of coping the huge policy file over to /etc/ use a minimal one. Incompatible options will brake mouse and or keyboard. This is a bit tricky to debug and seen before.
Code: | <?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
<device>
<match key="info.capabilities" contains="input.keyboard">
<merge key="input.x11_options.XkbLayout" type="string">uk</merge>
</match>
</device>
</deviceinfo> |
Overconfiguration is a bad habit and might become a maintenance horror later. Unless you acerbically document your changes to the defaults you soon will forget what makes this particular machine special. |
|
Back to top |
|
|
PeggySue n00b
Joined: 19 Dec 2009 Posts: 73 Location: Devon, UK
|
Posted: Tue Dec 29, 2009 5:14 pm Post subject: |
|
|
Many thanks for all the responses; I am totally blown away by the level of support. Hopefully I can give something back when I get this going. Clearly the instructions need a bit of a revamp with missing dependencies and updates; I will try to log what really needed to happen in the hope this will help.
cach0rr0:
'equery' was command not found but after Donahue's check list it reports:
x11-drivers/xf86-input-synaptics-1.2.0
x11-base/xorg-server-1.6.5-r1
Donahue:
My system passed your check list but a couple of observations:
INPUT_DEVICES: I included synaptics for my touch-pad
The USE flags also included the default settings and dbus which I added after the main build. So I hadn't run make after adding hal and dbus; I emerged them, started them from the command line and added them to the default run level so dbus and hald were already in the default run level and there was no xorg.conf to hide in /etc/X11.
After a reboot the startx gave a few flashes of the screen and returned me to the command line. Xorg.0.log suggests my keyboard and synaptics touchpad are now found, but no window!
I have yet to go through Donahue's upgrade links for libraries etc. I will do this before loading the desktop environment.
Sera's suggestion to install the desktop is tempting and looks to be the surest way of getting things going and I do need the laptop working soon. Before I do that, does any one want me to record anything from my system to try to track down why X won't stay up? If I do install the desktop we won't know what has happened with X. If that is the way it goes I will do another install on spare space on my desktop to see what goes wrong. The instructions to build from a minimal install, through stage3 and then X should be made to work. _________________ My time machine is broken which is odd because it was working tomorrow. |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Tue Dec 29, 2009 6:05 pm Post subject: |
|
|
Post result of:
Code: | nano /etc/env.d/90xsession |
Code: | emerge --search xdm |
if not installed suggest emerge xdm
Have you emerged a desktop/window manager? Gnome, kde, xfce ...?
if not you need one.
sera technique looks reasonable, I have not used it. I always boot to the black screen CLI you are trapped in now and then login and use startx to go to the GUI/Gnome interface.
It sounds like you have xorg-server running without a window manager.
Code: | nano /etc/conf.d/xdm |
should look like: Quote: | GNU nano 2.1.10 File: /etc/conf.d/xdm
# We always try and start X on a static VT. The various DMs normally default
# to using VT7. If you wish to use the xdm init script, then you should ensure
# that the VT checked is the same VT your DM wants to use. We do this check to
# ensure that you haven't accidentally configured something to run on the VT
# in your /etc/inittab file so that you don't get a dead keyboard.
CHECKVT=7
# What display manager do you use ? [ xdm | gdm | kdm | kdm-4.3 | gpe | entrance ]
# NOTE: If this is set in /etc/rc.conf, that setting will override this one.
#
# KDE-specific note:
# - If you are using kdeprefix go with "kdm-4.Y", e.g. "kdm-4.3".
# You can find possible versions by looking at the directories in /usr/kde/.
# - Else, if you are using KDE 3 enter "kdm-3.5"
# - Else, if you are using KDE 4 enter "kdm" without a version
DISPLAYMANAGER="xdm" # "gdm" for sera way
# Set whether xorg should depend on hald or not. If set to 'auto' then the init
# script tries to determine the dependency on hald automatically, by examining
# xorg.conf files on various locations. If you have built xorg without hal
# use-flag, you should set 'no' here. If xorg has been built with hal then you
# may set 'auto' or 'yes' here.
# Possible values are: [ yes | no | auto ]
NEEDS_HALD="auto" |
|
|
Back to top |
|
|
sera Retired Dev
Joined: 29 Feb 2008 Posts: 1017 Location: CET
|
Posted: Tue Dec 29, 2009 7:15 pm Post subject: |
|
|
Installing a DM now doesn't change anything but making it possible for the startx test to succeed.
You won't loose anything by trying what I suggested. You probably rather not install xdm if you do not intend to use it. As it is the loginmanager which needs the most knowledge to use I think gdm or kdm are better choices for you. Exploring the internals is easier on a mostly functioning system. Knowing the DM you are gonna install influences the choice as well. |
|
Back to top |
|
|
PeggySue n00b
Joined: 19 Dec 2009 Posts: 73 Location: Devon, UK
|
Posted: Thu Dec 31, 2009 11:20 am Post subject: |
|
|
The big revelation is that I have been under the misapprehension that Xorg managed the windows as well as creating them and I thought Gnome etc. just managed the desktop!
Before I installed the desktop:
/etc/env.d/90xsession has Xsession=Gnome and
emerge xdm tells us that xdms, xdm and libXdmcp would be merged.
Following sera's recipe:
I selected profile 2 (Desktop).
The output from emerge -avuND world said 2 config files in /etc had to be updated. So I figured out that a) they were hidden files and b) they weren't in /etc! I found etc-update and this helped me find the files. ssh was auto-merged because it was considered trivial and /etc/pam.d/system-login only had 1 additional line so I merged that as well.
emerge ...drivers and utilities went by without issues.
emerge gnome gdm took a while; over 10 hours, probably 11 hours, (I went to bed!) This was on an AMD 64 X2 Athlon @1.7 GHz laptop but I awoke to a pleasant surprise - a working Gnome desktop! Many thanks for all the support we made it! I now have to get printing and the wireless going, change the keyboard, try the simple profile, figure out why logical volume manager is there etc. but hopefully I can cope with that.
Just two parting questions if I may.
If I wanted a system that booted to the command prompt but would run applications like Firefox in a window would I have stopped the process before "emerge gnome gdm" and emerged xdm or would I still need gdm? I assume I can get to a system like that by setting my DISPLAY_MANAGER to xdm.
Is it worthwhile flagging my problem to the documentation team, and if so how? My problem was that I followed the minimal install which worked OK (on the second pass, but that was probably my fault). At page 53 "Where do we go from here" I then went to the main documentation page http://www.gentoo.org/doc/en/list.xml and selected "X server configuration HowTo" which was first in line after the installation options. http://www.gentoo.org/doc/en/xorg-config.xml But, using "Find" on this page doesn't show a single occurrence of xdm or gdm; also it assumes you have hal installed which the minimal install doesn't do.
There are lots of routes to various Gentoo configurations but some paths are shared. My suggestion would be to head each section with "This section will build you a xxxx feature" and "before you start this you need to have done yyyyy".
Thanks again for the help. I really like the Gentoo philosophy and it has just the right level of challenge! _________________ My time machine is broken which is odd because it was working tomorrow. |
|
Back to top |
|
|
sera Retired Dev
Joined: 29 Feb 2008 Posts: 1017 Location: CET
|
Posted: Thu Dec 31, 2009 12:10 pm Post subject: |
|
|
For firefox you will need a window manager (WM). Desktop manager (DM) is a term for a WM with some extras. Gnome and KDE are the major DMs (both have a bit more than just some extras ).
Twm(default X WM) was bundled wit X until recently and this is what the documentation expects when you issue startx. This is obviously no longer the case. I wasn't aware of that before this thread either.
It's always hard to write documentation for user with a lot less background knowledge than oneself. So tips on what caused misunderstandings from your point of view and how it could have been avoided are likely welcome.
Xdm, gdm, kdm basically do all the same. Xdm is sure the most lightweight of those and certainly something to consider if you use another WM/DM than gnome or kde and still want to comfortably boot into a graphical environment by default. Gdm and kdm are supposed to work out of the box, not so xdm.
All of them do the same job, so have somewhat different features, and therefore you only need one of them. |
|
Back to top |
|
|
DONAHUE Watchman
Joined: 09 Dec 2006 Posts: 7651 Location: Goose Creek SC
|
Posted: Thu Dec 31, 2009 4:45 pm Post subject: |
|
|
Quote: | If I wanted a system that booted to the command prompt but would run applications like Firefox in a window would I have stopped the process before "emerge gnome gdm" and emerged xdm or would I still need gdm? I assume I can get to a system like that by setting my DISPLAY_MANAGER to xdm. |
Running as root:
Code: | rc-update del xdm default
reboot |
should cause your system to boot to the black CLI which became unduly familiar.
Log in as root or a user and then enter startx to go straight to gnome.
Log in as root or a user and then enter gdm to go to the gdm login.
The results of Code: | ls -l /etc/init.d/xdm* | would be of interest if you never emerged xdm specifically. |
|
Back to top |
|
|
PeggySue n00b
Joined: 19 Dec 2009 Posts: 73 Location: Devon, UK
|
Posted: Fri Jan 01, 2010 5:52 pm Post subject: |
|
|
Thanks for the inputs.
I am progressing and have managed to get wireless going. It was painful but educational and I have copies of wpa_supplicant.conf all over the place!! Different people have different ideas where it should be. Again the instructions would have been fine iff I had met the prerequisites of loading the correct kernel module before starting.
Printing to a remote printer is well under way.
I will need to figure out how to stop eth0 waiting for a dhcp address at boot up but apart from that the system is becoming quite tidy.
Donahue: To the best of my recollection: I used emerge -pv xdm to find that xdm xdms etc were not loaded and then followed sera's recipe. The output from ls -l /etc/init.d/xdm* is now
Code: | -rwxr-xr-x 1 root root 6515 Dec 28 10:31 /etc/init.d/xdm
-rwxr-xr-x 1 root root 340 Dec 28 10:31 /etc/init.d/xdm-setup
|
dtjohnst: I did find iwconfig in wireless tools but went with the Gentoo preferred wpa_supplicant.
A happy and healthy New Year to you all. _________________ My time machine is broken which is odd because it was working tomorrow. |
|
Back to top |
|
|
sera Retired Dev
Joined: 29 Feb 2008 Posts: 1017 Location: CET
|
Posted: Fri Jan 01, 2010 6:14 pm Post subject: |
|
|
The default location for wpa_supplicant.conf on Gentoo is /etc/wpa_supplicant/wpa_supplicant.conf
To not wait for the timeout of eth0 there is the package ifplugd.
Wireless-tools only offers WEP encryption. This was ok 10 years ago.
@DONAHUE,
/etc/init.d/xdm comes with x11-apps/xinit which is a dependency of x11-base/xorg-server. No need to install xdm. The name of the init script is misleading in this regard. |
|
Back to top |
|
|
Deathwing00 Bodhisattva
Joined: 13 Jun 2003 Posts: 4087 Location: Dresden, Germany
|
Posted: Fri Apr 02, 2010 12:08 pm Post subject: |
|
|
Moved from Installing Gentoo to Desktop Environments. |
|
Back to top |
|
|
|