FedoraForum.org - Fedora Support Forums and Community
Page 3 of 4 FirstFirst 1234 LastLast
Results 31 to 45 of 59
  1. #31
    zedstarr Guest
    Quote Originally Posted by Quasar8000
    I chose a custom partitioning scheme as follows:
    Many thanks - I followed that scheme on my second install (my first 901 had an SSD #2 that died after only a week).

    My first yum update after install took me to 99.9% utilisation on / - a few updates complained that they couldn't save config information and I guess that was why.

    After the fact I set cachedir=/home/yum so that can't happen again.

    I also saved some space (about 300M!) on / by manually deleting unwanted language files from /usr/share/locale

  2. #32
    fed_core9 Guest
    Looks good also I had some trouble with my wireless but it has been fixed.

  3. #33
    Join Date
    Jun 2008
    Posts
    111
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I made an updated tutorial for installing Fedora 10 on the Eee PC 901/1000, it can be found here

  4. #34
    Join Date
    Dec 2008
    Posts
    71
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quasar8000, does the xorg.conf file you posted in earlier in this thread also work in Fedora 10? (I don't see it mentioned in your F10 tutorial).

    I've just tried my F10 installation (eeepc 901) on a projector, and once the system detects the projector it switches into 800x480 for both the built-in display AND the projector. But I haven't tried your xorg.conf contents yet.

    Thanks!

  5. #35
    Join Date
    Jun 2008
    Posts
    111
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Actually, I didn't try to modify the xorg.conf since I don't have an external monitor or projector to try it on. I can't see why the configuration should be any different though, so the one that worked for F9 should also work for F10. Just in case, make a backup of your original xorg.conf before making any modifications, and let us know how it goes

  6. #36
    Join Date
    May 2004
    Location
    Sydney, Australia
    Age
    48
    Posts
    254
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I've got a fresh F10 install on my Eee PC 901, and I think an xorg.conf is going to be needed to get external monitors working properly. There are a few problems with the default behaviour you get without one:

    1. The dual head configuration defaults to mirroring the two displays for which both displays have to be in the same mode. For most external displays the only possible common modes with the internal display are going to be very low resolution (i.e. 800x480). You can overide this behaviour later (using xrandr) but it's not ideal and you're still stuck with low-res boot and login screens. In fact this issue made it impossible for me to use an external monitor during installation, Anaconda can't be used at 800x480 resolution because the main buttons end up off the bottom of the screen...

    2. The 'screen' size gets set on X.org startup to be big enough to accommodate all the attached displays, but no bigger. What this means is that if you boot up with the external monitor attached you can configure dual head for an extended desktop just fine, but if you attach the monitor later you'll be severely restricted in the resolutions and display placements you can select. The only way out of this situation would be to log out to restart X.org.

    3. The gnome-display-properties application (System->Preferences->Hardware->Display Resolution) doesn't work properly, at least not for Intel 945GME graphics such as in our Eee's. The only reliable way to reconfigure the displays is with xrandr at the command line.

    A xorg.conf should be able to easily fix the first two problems, however. Following the guide here you can set up a non-mirrored monitor layout for X.org to use by default when it detects an external monitor and you can also specify a default 'screen' size (the Virtual entry in the Screen section) large enough so you can hotplug external monitors without having to restart X.org. As for the third issue, well, I've filed it with Bugzilla...
    Asus Eee PC 901, 2GB RAM, 20GB SSD + 16GB SDHC w/ Fedora 11
    HTC Hero w/ Android 1.5 (MoDaCo Custom ROM 2.2e)

  7. #37
    Join Date
    Dec 2008
    Posts
    71
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Ah, Quasar8000 I was (confused!) thinking of the earlier post by Hotdog in which he showed a revised xorg.conf and a link to the intel page that describes the way to do it.

    My eeepc, running F10, doesn't have an xorg.conf. Must be a new, smarter, X server So I just copied in the one Hotdog gave and rebooted and found no difference whatsoever in the behavior.

    Attaching it to a projector at work (I don't know the max resolution of it, but I've run it at 1024x768 before) I can get 640x480 only. Switching back to the internal monitor resolution returns to 1024x600, but the upper and lower panels remain the sizes and positions they were when the display was at the lower resolution, i.e., they are now not the full width of the screen, and the bottom one is an inch or more up from the bottom. When I get more time I'll have to play with it some more, perhaps trying xrandr would let me set some better resolutions. Time will tell.

  8. #38
    Join Date
    May 2004
    Location
    Sydney, Australia
    Age
    48
    Posts
    254
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Hi fredex, it sounds like you're using the gnome-display-properties tool (System->Preferences->Hardware->Display Resolution) to set up the dual head display with the projector. I've found that it doesn't work properly at all for dual head (panels ending up in strange places, etc.) and so have to use xrandr to do display reconfiguration.

    When you get a chance connect up the projector and just type 'xrandr' in a terminal. That should give details of the virtual screen size, list the usable modes of the currently connected displays, and indicate which modes are active and which are the 'preferred' modes (i.e. native resolution for an LCD). If the virtual screen size is still too small and the native resolution mode of the external monitor isn't listed than it means the xorg.conf hasn't done the trick.

    To enable an external display as an extended desktop I just type the command 'xrandr --output VGA --auto --above LVDS' which enables the external display in its preferred mode and creates an extended desktop with the external display above the laptop display. Before disconnecting the external display I have to disable it using 'xrandr --output VGA --off'. The other options are described in the xrandr man page ('man xrandr'), it's quite simple to use.

    It would be nice if this all happened automatically (especially disabling monitors when you disconnect them) but X.org, RandR, Intel and Gnome aren't quite there yet.
    Asus Eee PC 901, 2GB RAM, 20GB SSD + 16GB SDHC w/ Fedora 11
    HTC Hero w/ Android 1.5 (MoDaCo Custom ROM 2.2e)

  9. #39
    Join Date
    May 2004
    Location
    Sydney, Australia
    Age
    48
    Posts
    254
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    OK, I've now put my money where my mouth is and created a pared down, minimal xorg.conf for my Fedora 10 Eee PC 901. This is intended to let X.org automatically configure as much stuff as possible, I've only included just enough to make it do more sensible things with dual head.

    Code:
    Section "ServerLayout"
    	Identifier     "Default Layout"
    	Screen      0  "Screen0" 0  0
    EndSection
    
    Section "Device"
    	Identifier  "Intel 945GME"
    	Driver      "intel"
            Option      "Monitor-VGA" "vga"
    	Option      "Monitor-LVDS" "lfp"
    EndSection
    
    Section "Monitor"
            Identifier  "vga"
    EndSection
    
    Section "Monitor"
            Identifier  "lfp"
            Option      "Below" "vga"
    EndSection
    
    Section "Screen"
    	Identifier "Screen0"
    	Device     "Intel 945GME"
    	Monitor    "vga"
    	DefaultDepth     24
    	SubSection "Display"
    		Depth     24
    		Virtual  1920 1800
    	EndSubSection
    EndSection
    What this does is tell X to enable both the internal and external monitors on startup (if connected, if not it'll gracefully fall back to just using the internal monitor) and to configure them at their native resolution as an extended desktop with one above the other (instead of the silly mirrored setup which results in horribly low resolution modes when done on an Eee PC). The behaviour when booting up with an external monitor attached is now much more pleasant.

    It also sets the virtual screen to a size that will enable me to 'hotplug' any external monitor after starting X and use it at its native resolution. The highest resolution monitor that the Eee PC can drive from the VGA port is 1920x1200, so to enable me to do that with the internal 1024x600 below it I need a virtual screen size of 1920x1800. Actually enabling and disabling the external monitor will still require me to use xrandr in a terminal, but at least I won't have to restart X.

    Note, you won't be able to set up an extended desktop with the two monitors side by side with these setting as the virtual screen isn't wide enough. With Intel 945GME graphics if you go above 2048 pixels in either direction for the virtual screen direct rendering gets disabled, killing graphics performance, so I just settle for the vertical arrangement. It generally makes sense for me anyway, I usually have the laptop sitting in front of the external monitor so it really is below it.
    Asus Eee PC 901, 2GB RAM, 20GB SSD + 16GB SDHC w/ Fedora 11
    HTC Hero w/ Android 1.5 (MoDaCo Custom ROM 2.2e)

  10. #40
    malath Guest

    my cam and function keys

    Dear guys,

    i need help, i just installed fedora 9 on my eee pc, asus...i followed the tutorial iin the begining of this thread to get my cam to work and function keys, but unfortunately nothing is working. i edited the files but still also cam is not turned on and no hotkeys are working.

    when i had a look for the files requested to be modified it was empty.

  11. #41
    scottro's Avatar
    scottro is offline Retired Community Manager -- Banned from Texas by popular demand.
    Join Date
    Sep 2007
    Location
    NYC
    Posts
    8,120
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Look in the howto section, I believe he's posted an updated guide.

  12. #42
    zedstarr Guest
    Has anyone found a definitive guide on getting all audio working on the eee 901?

    I've never had the built-in front mic working. I have had some limited success at getting my bluetooth headset working with skype, but after the last kernel update I've now even lost the "front mic" as an input device - something's very broken

    Playback is still OK, but audio capture seems chaotic to say the least.

    I've googled and found either conflicting advice, or some debian specific stuff which talks about rebuilding the alsa driver ( see here ) but does that rely on a 2.6.28 series kernel....


    Maybe time to upgrade to F10


    zed.

  13. #43
    Join Date
    May 2004
    Location
    Sydney, Australia
    Age
    48
    Posts
    254
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    The front mics never worked for me with Fedora 9, and don't seem to with Fedora 10 either. I haven't tried very hard to find a solution though as I simply bought a USB headset for use with Skype, etc. instead and that has worked fine.

    I hoping we'll get a 2.6.28 kernel in Fedora 10 soon myself, but for other reasons.

    The touchpads in the Eee PCs (and some of the other netbooks) gets misidentified by Linux as a Logitech ImPS/2 Scrollwheel mouse (plus a few other incorrect bits of hardware, if I recall correctly). The touchpad still mostly works (two finger vertical scrolling and one, two and three finger taps for left, middle and right mouse clicks all OK) but you can't modify the settings.

    The touchpads are actually Elantech pads, however, and there's now a driver which causes the hardware to be identified correctly and adds support for it via the Synaptics touchpad driver. With this you can use all the Synaptics driver settings and tools, the one I'm particularly after is the daemon which automatically disables touchpad taps while you're typing. I keep accidentally brushing the pad and end up with my text inserted in the wrong part of the document I'm writing... It was added to the mainstream kernel for 2.6.28.
    Last edited by hotdog; 11th December 2008 at 01:04 AM.
    Asus Eee PC 901, 2GB RAM, 20GB SSD + 16GB SDHC w/ Fedora 11
    HTC Hero w/ Android 1.5 (MoDaCo Custom ROM 2.2e)

  14. #44
    Join Date
    May 2004
    Location
    Sydney, Australia
    Age
    48
    Posts
    254
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    An update on the built in microphones, with the latest Fedora 10 kernel (2.6.27.7-134) I've been able to record from the front mics using Sound Recorder. Just make sure they're not muted anywhere in Volume Control or the Pulse Audio Volume Control and they should work.

    I haven't tried them with Skype yet though.
    Asus Eee PC 901, 2GB RAM, 20GB SSD + 16GB SDHC w/ Fedora 11
    HTC Hero w/ Android 1.5 (MoDaCo Custom ROM 2.2e)

  15. #45
    Uru Wolf Guest
    Hey, I am a little stuck on the make process.

    make: *** /lib/modules/2.6.27.12-78.2.8.fc9.i686/build: No such file or directory. Stop.
    make: *** [LINUX] Error 2

    and then it stops. I guess I need some extra files but am not sure where to get them. Could anyone help out at all?

Page 3 of 4 FirstFirst 1234 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •