Why is Arch trending up?

I just went to the distrowatch page and I noticed that for the default 6 month listing Arch is in 10th place. That seems awfully high. Then I went to view the last 7 days detail and arch is in 5th place with over 1000 H.P.D. Is there something going on in the Arch community lately that is causing this high traffic? I've been out of the loop since exams started.

ngoonee wrote:
You may want to reconsider that, sand_man. Give Arch half a million members and the forums would be overflowing with "X DOESN'T WORK WTF!!!" type questions, and many questions would be answered immediately with tangential solutions which are at best workarounds or hacks.
Case-in-point the official forums for a certain popular-distro-which-should-not-be-named. I found gems there, but the forum was just a mess.
Maybe there should be a completely separate "newbie" forum where all newcomers have to post until they reach a certain post count. Kind of like a chroot jail, or it could be "chroot probation."  All issues from all newcomers go in there. Once a user has a certain number of posts (25, 50, 100, whatever) they "graduate" to being able to post in the main forum.
Not that post count itself means much -- and I definitely don't mean it in any elitist sense -- but you have to use something. It wouldn't guarantee anything, but it might cut down on the forums getting flooded with a lot of stuff that otherwise would all be contained in a single newcomer forum. It would also automatically "weed out" those who are just distro hopping and trying arch out for a while or out of curiosity, but who soon leave.
Another benefit is that the newbie forum could be easily scanned to provide quick, targeted help to newcomers. Not that that doesn't happen now, but I think a forum dedicated to relatively easy newbie issues would not only make it easier to provide stealth help but also serve as a great info resource for newcomers, kind of like a second wiki, or a cross between a forum and a wiki.
Perhaps most importantly for the long term, I think when the person finally did "graduate" to the main forum, a sense of accomplishment, belonging, etc. would come with that and make the person psychologically more invested in keeping the main forum operating smoothly. Win-win all around.

Similar Messages

  • KMS+init mods+pacman+kdemod+JFS Why is Arch not #1

    I have finished tweaking my default install for Arch:
    quick install:
    http://wiki.archlinux.org/index.php/Qui … ux_Install
    kdemod:
    pacman -S kdemod
    trimmed and boost boot-up:
    http://prasetyams.net/2008/06/27/speedu … t-process/
    tweak post-install/candy:
    http://wiki.archlinux.org/index.php/Pos … ation_Tips
    native framebuffer kernel mode setting and fast virtual terminal switching:
    http://wiki.archlinux.org/index.php/Intel_Graphics
    My arch system boots to KDM login in NINE seconds from hitting ENTER and Grub, to a gorgeous kdemod [and fast] KDE4 install. Default install without the above took 19 seconds (still not bad compared to the 'big distros')
    Satellite Pro A300 laptop:
    Core Duo T5170
    3MB DDR2
    160GB SATA HDD
    Intel 965GM graphics
    Intel Wireless 54g
    WHY IS ARCH LINUX NOT NUMBER 1. With a little thought a 'desktop package' could be created to achieve the above and knock the hell out of SuSE, Ubuntu, Fedora et.al.
    I have used linux since redhat 1.0 (work it out) and I am now FOREVER Arch !

    This's #1 for me!
    Best is not most.

  • Why does Arch suggest /boot for $esp mount point?

    Hi all,
    Something has been bugging me, and I can't figure out online why this is the case. Arch always suggests to mount the $esp on /boot, and by reading the Beginner's Guide/Installation wiki pages (and forums), it looks like the reasons are:
    - gummiboot upstream expects it there
    - pacman can only update kernels in /boot
    Other distributions suggest to mount the $esp on /boot/efi, and this has the good effect, that all files of distributions are located in subfolders ($esp/EFI/opensuse/, for example), and are not littering the root $esp folder. If every distribution did what Arch does, then on a multi-distro the root folder of the $esp would have every single kernel/fallback img.
    I noticed the FHS doesn't have a standard mount point/folder for the $esp, either.
    Is there another reason that Arch suggests this?
    Thanks

    Gummiboot's method only works if distros keep the /boot folder free of files, and use directories to cleanly categorise kernels, etc. I have yet to find a distribution that does this.
    "Works" is relative here. Gummiboot doesn't do things the way you want; that's fine, because a) you don't use it; and b) you can always organize your EFI images as you see fit. Gummiboot will still accomplish its intended task: booting a working Linux kernel from an EFI image. The Gummiboot Arch wiki page states that the ESP must be mounted at /boot for it to work, but that's it. The UEFI wiki page doesn't mention mounting at boot at all---only to /boot/efi. The EFISTUB page mentions that if you don't mount to /boot, you need to mount the ESP somewhere and manually copy the images to the ESP. The GRUB wiki page doesn't make statements on where the ESP should be mounted, but does make it clear that GRUB needs to be told where the ESP is mounted during installation. The Beginner's Guide does recommend mounting the ESP to /boot, and then links to another page with more information.
    Reading the Beginner's Guide without following the links may give the impression that mounting to /boot is something of a requirement, but it depends on the use case.You have four options when booting from UEFI: rEFInd, Gummiboot, GRUB and  EFISTUB. The first requires the ESP to be mount at /boot/efi, like it or not. The second requires it to be mounted at /boot, like it or not. The latter two have no strict requirements of where the ESP be mounted, but mounting anywhere other than /boot requires extra work on the part of the user. Yes, if you mount the ESP to /boot and run multiple distributions then the kernel images are still going to clutter the /boot directory, which is exactly what happens if you share a /boot partition between distributions no matter what (and as I alluded to earlier, there are cases in which this is necessary). UEFI has nothing to do with that, and it's one reason that each distribution has its own naming conventions for its kernel image (a Linux kernel built from source will always be called "bzImage" regardless of the distribution its built on). Arguably, none of that matters unless you're manually moving and deleting kernel images and get confused about which one is which---a case that almost never arises nowadays, and should never arise for the typical desktop user.

  • Why does Arch use .tar.gz as package files?

    As opposed to a tar.gz file with a .pac extension much like a .deb from Debian.  I'm just curious...
    Arch is a great Distro.  It has taken over my desktop... something that hasn't happened since 1999!

    Nevermind... I found the official reason here:
    http://wiki.archlinux.org/index.php/FAQ … _confusing
    If possible, I would like to add my vote to the "confusing/long" portion of the above. 

  • /dev/sda for Arch but /dev/hda for custom kernel. Why?

    My laptop does not have a scsi or sata hard drive. So why does Arch's kernel view the drive as /dev/sda1 while a custom kernel views it as /dev/hda like it should?

    Hmm that does not at all seem like a good explanation.
    Drivers/ide suffers from many ugly and obscure problems, and re-implementing it on top of libata has been much easier than fixing the unfixable drivers/ide mess
    you don't think fixing broken and ugly code is a good thing? Let me guess, you think sdxX is somehow more ugly then hdxX?
    btw, if you use persistent block device naming scheme, you wouldn't need worry about naming conventions. http://wiki.archlinux.org/index.php/Per … ice_naming

  • Why arch is awesome

    For some reason or another i have been neglecting my Arch installation for the past year or so. Becoming a digital DJ caused me to focus on windows and mac, and busy with schoolwork, I didn't have much time anymore to tinker around with linux as I used to love doing.
    Why is arch awesome?
    After booting up my arch installation that probably hasn't ran for about 6 months, I fired up X and instantly ran pacman -Syu (after following the klibc upgrade instructions i saw on the homepage). Everything worked, Nothing broke. A 6 month update executed perfectly.
    Here's to a great package manager!

    One of the less obvious reasons: the Arch team isn't overstaffed. They just can't afford any technology which is apt to cause trouble. Be really good or step aside; the choce is that simple. Big establishments can afford problems, as everybody knows all too well .
    Last edited by Llama (2008-10-21 10:57:36)

  • Why does the default install make a partition for boot?

    The installer, if one lets it prepare one's hard drive, makes a partition for boot, and formats it as a second extended filesystem. I know that people debate the need for/desirability of a partition for boot, and I do not mean to revive that debate. Rather, I am interested in knowing why the Arch developers, like the developers of some other distributions, such as Gentoo, but unlike some, such as Slackware, call for a boot partition, with ext2fs file system, on a default install. Should Arch users interpret this as a recommendation? Also, why is the partition quite a bit larger (although tiny compared to the available space on hard drives these days) than seems necessary?
    Thanks.

    I've looked at a couple of books and a fair number of internet posts on this, and I must say that these responses are a good deal more concise and clear than what I have come across. I did find it interesting that the Slackware on-line manual doesn't make any effort to encourage it. On the other hand, what you guys are saying sounds sensible enough.
    I have both Arch and Gentoo running, sharing a boot partition, which I set at 50MB. I'm using 25% of it, which is why I ask about size - obviously not in terms of overall capacity, but in terms of need.
    Why not a lot less - say, even if one is considering dual boot, 20MB? And where do numbers like 32MB come from (the Arch, and indeed Gentoo, default, also referred to by T-Dawg)? Why not use round numbers?
    Does 32MB have some rational/irrational/astrological/lucky 7 connection to 64MB RAM, sort of like designating 128MB as swap instead of using numbers like 120MB or 125MB or 130MB?
    As you probably know, in Gentoo this stuff is done on the command line in fdisk, and I found it quite odd to be told in their manual to tell fdisk that the boot partition should be 32MB (assuming a single operating system) and swap should be 256MB, especially since fdisk and my hard drive took these numbers with a grain of salt and conspired to adjust them to slightly different numbers complete with decimals. Arch, on default, does the same.
    Then I find out that with two operating systems, I'm using about 13MB out of 50MB (or rather 49.9MB, as fdisk and my hard drive decreed)
    To change the subject a bit, I think that it is a good idea that the current version of Arch .08 would create, on the default track, a /home partition. There are some nice ideas in the install dialogue, including in the section on setting up a hard drive.

  • Is there a way to have AUFS support with latest kernel in Arch repos?

    http://aufs.sourceforge.net/ says that linux kernel 3.9 has support for AUFS but then why does Arch doesn't have it enabled in the kernel present in repos?

    WonderWoofy wrote:
    As Arch provides near vanilla packages, there is nothing to enable.  AUFS is not part of the kernel, it is a patch.  You can find some AUFS patched kernels in the AUR, and I think linux-pf has it as well.
    Otherwise, you can use the unionfs-fuse package in the official repos.  But just be aware that because it is a fuse based filesystem, it might not be as fast as you want/expect.
    Thanks for bringing it to notice. I thought that it was part of official kernel.
    I need to run docker on 3.9 kernel that's why I need it. In 3.8, my laptop has issues with ethernet not being detected after sleep so I don't want to use the package given in AUR.
    A guy named timebomb has provided a diff against 3.9 here https://aur.archlinux.org/packages/aufs3/ . I was just hoping if we could have a PKGBUILD.
    In the meantime, I'll try linux-pf kernel. Thanks

  • Arch Linux 0.7.1 - my feedback

    please read the post before vote
    Well, I've used Arch linux for many months in late 2004 / early 2005 and then I've switched to Ubuntu...
    some days ago I've installed version 0.7.1 and updated it with pacman -Syu
    I've seen a lot of improvement since the last time I used it and I was near to think "ok let's switch back to Arch" until I found I that thing I really hate  :!: is still here..
    You can't install old versions of some packages. For example, kernel.. or.. php (ok there is one in Aur that is maybe "too" old) and mysql..
    in the php/mysql example it's true that version 5 is the latest one but they (at least php) still develope the 4.x version for security and many server still have it and also many scripts supports only php4 and 5.
    also, as I am a php developer, I need to test scripts with old versions.
    but as I said this is just an example. I think that while you can't think to have a big repository of binaries it would be great to be able to install old versions via source.
    and recompiling software by hand using old PKGBUILDS is a problem case you don't have a tool that tells you wich packaged were "aligned" with wich.. I mean.. the new php works only with the mysql5 extension so even if you build mysql by yourself it won't work with php.. and so on for apache..
    anyway.. if a user is able to block a package and prevent the automatic update he should also be able to use the non-latest version of it.
    I know that arch is a bleeding edge distro but this shouldn't mean that you have only the bleeding things. (see gentoo for example)
    Another thing that will help a lot in my opinion is to have in the wiki 2 lists:
    - one very detailed with available daemons and their use.. for example.. ok.. fam is the file alteration monitor.. but why you need it and wich are the main programs that takes advantage from it and what happens if you doesn't run it? and so on for hal, etc. ..
    - one list with all available standard groups that tells user to wich group subscribe in order to be able to performe a specific action
    imho this 2 lists will help the (new) user understand better what is doing and why The arch philosophy of "do it yourself  and learn doing it" is great but have to be encouraged, and in fact there already is a very good documentation.
    Just my 2 cents. And sorry if some one else already said this before; in this case take my post as an underline mark btw.. I'll attach a poll to it.
    bye,
    Giovanni.

    iphitus wrote:To me this thread looks more like "i dont want to make a second package for myself, so let's get the devs to do it".
    hmm.. this sounds a bit offenisve to me. Cause I don't actually need that packages as I'm not using Arch as main distro. This post was meant to give a feedback..
    iphitus wrote:Especially as there isnt a huge demand for such a package, and you are most likely to be one of a very small minority to use that duplicate package.
    ok I agree with this. but from my point of view it is because users that needed it too already switched to another distro..
    and this leads us to this:
    tomk wrote:I voted "No, there is no need", because I think this is simply an indication that Arch is not the right distro for you - it doesn't meet your requirements.
    Imho, the point is that Arch have a lot of great features. The one I'd like to have is a feature that I think will just increase the number of great features Arch already have and will make Arch the right distro for more users. So users that switch to another distro will lose a lot of features that they like to get one or two that they need..
    tomk wrote:This "thing that you really hate" is still there because firstly the Arch devs, and secondly Arch users, have not needed to change it. If you want to work "from within" to change that, with polls like this, feature requests, etc, I wish you the best of luck, but I think your poll result so far should tell you something about the support you can expect.
    the poll was mainly for myself to get an idea of the users opinion not to change the things. And as I said it is not a change from my point of view, but just a new feature. About Arch devs I agree but about users I don't.. how you can say it if you say to me that I should change distro? In this way people that thinks like me will always remain a minority in arch community. And I don't think that having a old version of a "core" package would be against the Arch philosophy.
    tomk wrote:Finally a general point, and this applies to wiki entries as well - you will get a better response if you do something, and then ask "what do you think?" instead of asking "Why doesn't Arch do this?"
    I did it for the software thing with the poll and anyway also for the wiki I didn't wrote it but I thought it was clear.. For the wiki I posted my idea and there was no need for the question "what do you think" cause is a discussion forum Also please keep in mind that I wrote the original post in late night and that I'm italian so my english isn't so good  :oops:
    anyway.. thanks for the tip about subit a feature request and for your answers.
    bye,
    Giovanni.

  • Popularity Trends report always returns zero

    Hello,
    I have a SharePoint installed on “Windows server 2008 -R2”.
    I have a SQL Data base installed on the same machine.
    I create a new web application with port “2020”. Then I create w new site collection “Publishing”.
    I activate the feature “Reporting” in the site collection level.
    I Open central admin “Monitoring >> Configure usage and health data collection”. I checked “Enable usage data collection” Check box. And I Checked All “Events to Log” check boxes.
    I have configures the following services applications :
           -Business Connectivity Service
           -Excel Services Application
          -Search Service Application
         -Security Token Service Application
         -Application Discovery and Load Balancer Service Application
         -WSS_UsageApplication.
    I run the crawl search. And it is completed successfully.
    The search service account is member of “WSS_WPG” group.
    I have checked the following values from SharePoint PowerShell:
             AppEventTypeId          : 00000000-0000-0000-0000-000000000000
             EventTypeId                 : 1
             EventName                   : Views
             LifeTimeManagedPropertyName : ViewsLifeTime
             RecentManagedPropertyName   : ViewsRecent
            ApplicationName             :
            RecommendationWeight        : 1
           RelevanceWeight             : 1
          RecentPopularityTimeframe   : 14
          AggregationType             : Count, UniqueUsers
         Rollups                     : SiteSubscriptionId, SiteId, ScopeId
        TailTrimming                : 2
       Options                     : AllowAnonymousWrite
        IsReadOnly                  : False
    I open the “default.aspx” page on the portal (I have opened it more than 10 times in different browser window).
    Next day I open “popularity Trends” report, I found that it returns zero.
    I open the “Analytics Report” data base. Then I open “AnalyticsItemData” table. There are already items in the table.
        So I need to know why the “popularity Trends” excel sheet report returns zeros all the time.
    ASk

    Hi,
    According to your description, the popularity Trends report always returns no records.
    Please check the status of the 3 timer jobs: Microsoft SharePoint Foundation Usage Data Import, Microsoft SharePoint Foundation Usage Data Processing and Web Analytics
    Trigger Workflows to see if they are configured to run at regular intervals.
    Also you can take a look at the two links about the similar issue for more information:
    http://www.myriadtech.com.au/blog/Ben/Lists/Posts/Post.aspx?ID=7
    http://sharepoint.stackexchange.com/questions/66476/whats-popular-webpart-is-empty
    Feel free to reply if there any progress.
    Best regards,
    Patrick
    Patrick Liang
    TechNet Community Support

  • Has something changed in the Arch Installation?

    I've seem to run across a few things when I install Arch now.  I've installed Arch many times on the exact same computer with the exact same hardware but I'm experiencing some issues. I always use the FTP install. 
    First, I have no colors anymore when I edit anything in nano (after the installation).  Why is that?  All i have is a completely fresh install, but no colors.  That never used to happen.  I haven't changed anything. 
    Second, even though I select during the install which mirror i would like to keep as my 1st mirror, pacman -Syu will not work.  I have to go into into the mirrorlist file and uncomment a mirror.  Now that is not a problem at all, but why has that changed? 
    On top of those things, I have problems now getting GDM to load my xfce4 session, and even without GDM, I can only load xfce4 thru the root login, not my own, and when I install ttf-ms-fonts, i get a error that says the package has different permissions than the /tmp directory, which has never happened before.  I think the GDM thing is also a permissions problem for some reason. 
    But why oh why has Arch changed on me?!  Help!

    Nano syntax highlighting is now stored in /usr/share/nano.
    I added the following lines to /etc/nanorc:
    ## Arch PKGBUILD
    include "/usr/share/nano/pkgbuild.nanorc"
    ## Syntax highlighting in xorg.conf
    include "/usr/share/nano/xorg.nanorc"
    ## Generic conf/rc/sh file syntax highlighting
    include "/usr/share/nano/conf.nanorc"
    Here are the 3 Arch files I created:
    cat /usr/share/nano/conf.nanorc
    # Generic conf/rc/sh file syntax highlighting
    syntax "conf/rc/sh" "conf$|rc$|sh$"
    color white ".+"
    color green "^#.*"
    cat /usr/share/nano/pkgbuild.nanorc
    ## Arch PKGBUILD files
    syntax "pkgbuild" "^.*PKGBUILD$"
    color green start="^" end="$"
    color cyan "^.*(pkgname|pkgver|pkgrel|pkgdesc|force|url|license|install|source|md5sums|groups|backup|depends|makedepends|conflicts|provides|replaces).*=.*$"
    color brightcyan "\<(pkgname|pkgver|pkgrel|pkgdesc|force|url|license|install|source|md5sums|groups|backup|depends|makedepends|conflicts|provides|replaces)\>"
    color cyan "\.install"
    color brightwhite "=" "'" "\(" "\)" "\"" "#.*$" "\," "\{" "\}"
    color brightcyan "(\$|\$\{|\$\()(pkgname|pkgver|pkgrel|pkgdesc|force|url|license|install|source|md5sums|groups|backup|depends|makedepends|conflicts|provides|replaces|startdir)(|\}|\))"
    color brightred "build\(\)"
    color brightred "\<(configure|make)\>"
    color red "\<(DESTDIR|PREFIX|prefix|sysconfdir|datadir|libdir|includedir|mandir)\>"
    cat /usr/share/nano/xorg.nanorc
    ## syntax highlighting in xorg.conf
    syntax "xorg" "xorg\.conf$"
    color brightwhite "(Section|EndSection|Sub[sS]ection|EndSub[sS]ection)"
    # keywords
    color yellow "[^A-Za-z0-9](Identifier|Screen|InputDevice|Option|RightOf|LeftOf|Driver|RgbPath|FontPath|ModulePath|Load|VendorName|ModelName|BoardName|BusID|Device|Monitor|DefaultDepth|View[pP]ort|Depth|Virtual|Modes|Mode|DefaultColorDepth|Modeline|\+vsync|\+hsync|HorizSync|VertRefresh)[^A-Za-z0-9]"
    # numbers
    color magenta "[0-9]"
    # strings
    color green ""(\\.|[^\"])*""
    # comments
    color white "#.*"

  • Performance issues: why is it not as fast as it should /could be?

    hello,
    i am an experienced unix/linux user since '98 looking for a new linux distro to install on my shining new Dell precision M65 notebook (2gb ram, dual core, 7200rpm, etc.) and Dell optiplex gx270 pc and i want it to be as fast as it can be.
    I really WANT it to be Arch, i love the idea of arch, the basic install, the only get what you need, pacman is nearly as good as apt-get, it boots Really fast, kdemod is cool, the rolling system is awesome ......
    ....  BUT why is Arch so relatively slow?
    i installed the following:
    the duke base install
    kdemod
    kdm
    powersaved
    ifplugd
    xorg
    ipw3945d
    firefox/thunderbird
    pidgin
    nvidia-glx
    that is all, really.
    i was expecting a basic setup like that to be really lightweight and fast but the average load is +1 with X, powersaved (14%), hald(8%), dbus(9%),  and i have a lot of lag. windows drag when moving and firefox startup takes seconds. only booting is Really fast (<30seconds). I am using the nvidia driver but no composite.
    I have also tried the full blown bloated sabayon on my latop and even with all the apps, all the bling and compiz enabled by default it is FASTER then my lovable Arch install (a idle load of 0.02 but i just hate emerge/portage/source stuff), I installed Pardus 2007.02 on my desktop for my wife (everything works out of the box and look familiar) and even on the older pc the load is just 0.06 idle and max 0.8 working.
    What is going on here. I want to stick with Arch, but this seems really akward to me, why could my system be using all that memory / cpu while doing nothing, no compiz, just firefox and thunderbird.
    any insight would be very welcome, there are no errors in the /var/log/* files and only sound and hibernation are not working yet.
    thanks,
    stefan

    hi there all,
    i don't know if it is anything to to with X. I did find out that if I leave my pc idle for long enough (+30 mins) that the load will settle down to around 0.06, but as soon as I start using it it flies back up.
    booting and shutting down is really fast though. Another thing I noticed is that with using the nvidia driver that i get occasional (one a minute) random "flickers"  across my screen, where it turns slightly black or trembles the screen for a milisecond.
    with nvidia-glx i just meant the latest official nvidia drivers (not nv) that i got by "pacman -Sy nvidia"
    the xorg.conf:
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig:  version 1.0  (buildmeister@builder3)  Wed Jun 13 18:39:30 PDT 2007
    # Auto-generated by Archie mkxcfg
    # Auto-generated by Archie mkxcfg
    Section "ServerLayout"
    # Serial Mouse not detected
    # USB Mouse not detected
        Identifier     "Xorg Configured"
        Screen      0  "Screen0" 0 0
        InputDevice    "Keyboard0" "CoreKeyboard"
        InputDevice    "PS/2 Mouse" "CorePointer"
    EndSection
    Section "Files"
    # Additional fonts: Locale, Gimp, TTF...
    #       FontPath     "/usr/share/lib/X11/fonts/latin2/75dpi"
    #       FontPath     "/usr/share/lib/X11/fonts/latin2/100dpi"
    # True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
        RgbPath         "/usr/share/X11/rgb"
        ModulePath      "/usr/lib/xorg/modules"
        FontPath        "/usr/share/fonts/misc:unscaled"
        FontPath        "/usr/share/fonts/misc"
        FontPath        "/usr/share/fonts/75dpi:unscaled"
        FontPath        "/usr/share/fonts/75dpi"
        FontPath        "/usr/share/fonts/100dpi:unscaled"
        FontPath        "/usr/share/fonts/100dpi"
        FontPath        "/usr/share/fonts/PEX"
        FontPath        "/usr/share/fonts/cyrillic"
        FontPath        "/usr/share/fonts/Type1"
        FontPath        "/usr/share/fonts/ttf/western"
        FontPath        "/usr/share/fonts/ttf/decoratives"
        FontPath        "/usr/share/fonts/truetype"
        FontPath        "/usr/share/fonts/truetype/openoffice"
        FontPath        "/usr/share/fonts/truetype/ttf-bitstream-vera"
        FontPath        "/usr/share/fonts/latex-ttf-fonts"
        FontPath        "/usr/share/fonts/defoma/CID"
        FontPath        "/usr/share/fonts/defoma/TrueType"
    EndSection
    Section "Module"
        Load           "ddc"  # ddc probing of monitor
        Load           "dbe"
        Load           "extmod"
        Load           "glx"
        Load           "bitmap" # bitmap-fonts
        Load           "type1"
        Load           "freetype"
        Load           "record"
    EndSection
    Section "ServerFlags"
        Option         "AllowMouseOpenFail" "true"
    EndSection
    Section "InputDevice"
        Identifier     "Keyboard0"
        Driver         "keyboard"
        Option         "CoreKeyboard"
        Option         "XkbRules" "xorg"
        Option         "XkbModel" "pc105"
        Option         "XkbLayout" ""
        Option         "XkbVariant" ""
    EndSection
    Section "InputDevice"
        Identifier     "Serial Mouse"
        Driver         "mouse"
        Option         "Protocol" "Microsoft"
        Option         "Device" "/dev/ttyS0"
        Option         "Emulate3Buttons" "true"
        Option         "Emulate3Timeout" "70"
        Option         "SendCoreEvents" "true"
    EndSection
    Section "InputDevice"
        Identifier     "PS/2 Mouse"
        Driver         "mouse"
        Option         "Protocol" "auto"
        Option         "ZAxisMapping" "4 5"
        Option         "Device" "/dev/psaux"
        Option         "Emulate3Buttons" "true"
        Option         "Emulate3Timeout" "70"
        Option         "SendCoreEvents" "true"
    EndSection
    Section "InputDevice"
        Identifier     "USB Mouse"
        Driver         "mouse"
        Option         "Device" "/dev/input/mice"
        Option         "SendCoreEvents" "true"
        Option         "Protocol" "IMPS/2"
        Option         "ZAxisMapping" "4 5"
        Option         "Buttons" "5"
    EndSection
    Section "Monitor"
    # Warning: This may fry old Monitors
    # Very conservative. May flicker.
    #       VertRefresh  50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
            #  Default modes distilled from
            #      "VESA and Industry Standards and Guide for Computer Display Monitor
            #       Timing", version 1.0, revision 0.8, adopted September 17, 1998.
            #  $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
            # 640x350 @ 85Hz (VESA) hsync: 37.9kHz
        Identifier     "Monitor0"
        HorizSync       28.0 - 96.0
        VertRefresh     50.0 - 75.0
        ModeLine       "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
        ModeLine       "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
        ModeLine       "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
        ModeLine       "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
        ModeLine       "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
        ModeLine       "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
        ModeLine       "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
        ModeLine       "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
        ModeLine       "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
        ModeLine       "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
        ModeLine       "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
        ModeLine       "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
        ModeLine       "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync interlace
        ModeLine       "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
        ModeLine       "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
        ModeLine       "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
        ModeLine       "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
        ModeLine       "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
        ModeLine       "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
        ModeLine       "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
        ModeLine       "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
        ModeLine       "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
        ModeLine       "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
        ModeLine       "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
        ModeLine       "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
        ModeLine       "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
        ModeLine       "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
        ModeLine       "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
        ModeLine       "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
        ModeLine       "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
        ModeLine       "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
        ModeLine       "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
        ModeLine       "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
        ModeLine       "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
        ModeLine       "1800x1440" 230.0 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
        ModeLine       "1800x1440" 250.0 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
        ModeLine       "640x480" 43.2 640 680 744 848 480 481 484 509 -hsync +vsync
        ModeLine       "768x576" 35.0 768 792 872 976 576 577 580 597 -hsync +vsync
        ModeLine       "768x576" 42.9 768 800 880 992 576 577 580 601 -hsync +vsync
        ModeLine       "768x576" 45.5 768 808 888 1008 576 577 580 602 -hsync +vsync
        ModeLine       "768x576" 51.8 768 808 888 1008 576 577 580 605 -hsync +vsync
        ModeLine       "768x576" 62.6 768 816 896 1024 576 577 580 611 -hsync +vsync
        ModeLine       "800x600" 68.2 800 848 936 1072 600 601 604 636 -hsync +vsync
        ModeLine       "1024x768" 113.3 1024 1096 1208 1392 768 769 772 814 -hsync +vsync
        ModeLine       "1152x864" 81.6 1152 1216 1336 1520 864 865 868 895 -hsync +vsync
        ModeLine       "1152x864" 119.7 1152 1224 1352 1552 864 865 868 907 -hsync +vsync
        ModeLine       "1152x864" 143.5 1152 1232 1360 1568 864 865 868 915 -hsync +vsync
        ModeLine       "1280x960" 124.5 1280 1368 1504 1728 960 961 964 1001 -hsync +vsync
        ModeLine       "1280x960" 129.9 1280 1368 1504 1728 960 961 964 1002 -hsync +vsync
        ModeLine       "1280x960" 179.0 1280 1376 1520 1760 960 961 964 1017 -hsync +vsync
        ModeLine       "1280x1024" 191.0 1280 1376 1520 1760 1024 1025 1028 1085 -hsync +vsync
        ModeLine       "1400x1050" 122.6 1400 1488 1640 1880 1050 1051 1054 1087 -hsync +vsync
        ModeLine       "1400x1050" 149.3 1400 1496 1648 1896 1050 1051 1054 1094 -hsync +vsync
        ModeLine       "1400x1050" 155.8 1400 1496 1648 1896 1050 1051 1054 1096 -hsync +vsync
        ModeLine       "1400x1050" 179.3 1400 1504 1656 1912 1050 1051 1054 1103 -hsync +vsync
        ModeLine       "1400x1050" 214.4 1400 1512 1664 1928 1050 1051 1054 1112 -hsync +vsync
        ModeLine       "1600x1200" 280.6 1600 1728 1904 2208 1200 1201 1204 1271 -hsync +vsync
        Option         "DPMS" "true"
    #       HorizSync    28.0 - 78.0 # Warning: This may fry very old Monitors
    EndSection
    Section "Device"
        Identifier     "Card0"
        Driver         "nvidia"
        VendorName     "All"
        BoardName      "All"
    EndSection
    Section "Screen"
        Identifier     "Screen0"
        Device         "Card0"
        Monitor        "Monitor0"
        DefaultDepth    24
        Option         "AllowGLXWithComposite" "True"
        Option         "RenderAccel" "True"
        Option         "AddARGBGLXVisuals" "True"
        Option         "NoLogo" "True"
        SubSection     "Display"
            Depth       24
            Modes      "1900x1200"
        EndSubSection
    EndSection
    Section "Extensions"
        Option         "Composite" "Enable"
    EndSection
    and the logfile:
    X Window System Version 7.2.0
    Release Date: 22 January 2007
    X Protocol Version 11, Revision 0, Release 7.2
    Build Operating System: UNKNOWN
    Current Operating System: Linux Icarus 2.6.21-ARCH #1 SMP PREEMPT Sat Jul 7 09:57:11 UTC 2007 i686
    Build Date: 08 April 2007
            Before reporting problems, check http://wiki.x.org
            to make sure that you have the latest version.
    Module Loader present
    Markers: (--) probed, (**) from config file, (==) default setting,
            (++) from command line, (!!) notice, (II) informational,
            (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jul 24 16:21:48 2007
    (==) Using config file: "/etc/X11/xorg.conf"
    (==) ServerLayout "Xorg Configured"
    (**) |-->Screen "Screen0" (0)
    (**) |   |-->Monitor "Monitor0"
    (**) |   |-->Device "Card0"
    (**) |-->Input Device "Keyboard0"
    (**) Option "XkbRules" "xorg"
    (**) XKB: rules: "xorg"
    (**) Option "XkbModel" "pc105"
    (**) XKB: model: "pc105"
    (WW) Option "XkbLayout" requires an string value
    (WW) Option "XkbVariant" requires an string value
    (==) Keyboard: CustomKeycode disabled
    (**) |-->Input Device "PS/2 Mouse"
    (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi".
            Entry deleted from font path.
            (Run 'mkfontdir' on "/usr/share/fonts/75dpi").
    (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi".
            Entry deleted from font path.
            (Run 'mkfontdir' on "/usr/share/fonts/75dpi").
    (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi".
            Entry deleted from font path.
            (Run 'mkfontdir' on "/usr/share/fonts/100dpi").
    (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi".
            Entry deleted from font path.
            (Run 'mkfontdir' on "/usr/share/fonts/100dpi").
    (WW) The directory "/usr/share/fonts/PEX" does not exist.
            Entry deleted from font path.
    (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/cyrillic".
            Entry deleted from font path.
            (Run 'mkfontdir' on "/usr/share/fonts/cyrillic").
    (WW) The directory "/usr/share/fonts/ttf/western" does not exist.
            Entry deleted from font path.
    (WW) The directory "/usr/share/fonts/ttf/decoratives" does not exist.
            Entry deleted from font path.
    (WW) The directory "/usr/share/fonts/truetype" does not exist.
            Entry deleted from font path.
    (WW) The directory "/usr/share/fonts/truetype/openoffice" does not exist.
            Entry deleted from font path.
    (WW) The directory "/usr/share/fonts/truetype/ttf-bitstream-vera" does not exist.
            Entry deleted from font path.
    (WW) The directory "/usr/share/fonts/latex-ttf-fonts" does not exist.
            Entry deleted from font path.
    (WW) The directory "/usr/share/fonts/defoma/CID" does not exist.
            Entry deleted from font path.
    (WW) The directory "/usr/share/fonts/defoma/TrueType" does not exist.
            Entry deleted from font path.
    (**) FontPath set to:
            /usr/share/fonts/misc:unscaled,
            /usr/share/fonts/misc,
            /usr/share/fonts/Type1
    (**) RgbPath set to "/usr/share/X11/rgb"
    (**) ModulePath set to "/usr/lib/xorg/modules"
    (**) Option "AllowMouseOpenFail" "true"
    (**) Extension "Composite" is enabled
    (II) Open ACPI successful (/var/run/acpid.socket)
    (II) Loader magic: 0x81c44a0
    (II) Module ABI versions:
            X.Org ANSI C Emulation: 0.3
            X.Org Video Driver: 1.1
            X.Org XInput driver : 0.7
            X.Org Server Extension : 0.3
            X.Org Font Renderer : 0.5
    (II) Loader running on linux
    (II) LoadModule: "pcidata"
    (II) Loading /usr/lib/xorg/modules//libpcidata.so
    (II) Module pcidata: vendor="X.Org Foundation"
            compiled for 7.2.0, module version = 1.0.0
            ABI class: X.Org Video Driver, version 1.1
    (++) using VT number 7
    (II) PCI: PCI scan (all values are in hex)
    (II) PCI: 00:00:0: chip 8086,27a0 card 1028,01c8 rev 03 class 06,00,00 hdr 00
    (II) PCI: 00:01:0: chip 8086,27a1 card 0000,0000 rev 03 class 06,04,00 hdr 01
    (II) PCI: 00:1b:0: chip 8086,27d8 card 1028,01c8 rev 01 class 04,03,00 hdr 00
    (II) PCI: 00:1c:0: chip 8086,27d0 card 0000,0000 rev 01 class 06,04,00 hdr 81
    (II) PCI: 00:1c:1: chip 8086,27d2 card 0000,0000 rev 01 class 06,04,00 hdr 81
    (II) PCI: 00:1c:2: chip 8086,27d4 card 0000,0000 rev 01 class 06,04,00 hdr 81
    (II) PCI: 00:1c:3: chip 8086,27d6 card 0000,0000 rev 01 class 06,04,00 hdr 81
    (II) PCI: 00:1d:0: chip 8086,27c8 card 1028,01c8 rev 01 class 0c,03,00 hdr 80
    (II) PCI: 00:1d:1: chip 8086,27c9 card 1028,01c8 rev 01 class 0c,03,00 hdr 00
    (II) PCI: 00:1d:2: chip 8086,27ca card 1028,01c8 rev 01 class 0c,03,00 hdr 00
    (II) PCI: 00:1d:3: chip 8086,27cb card 1028,01c8 rev 01 class 0c,03,00 hdr 00
    (II) PCI: 00:1d:7: chip 8086,27cc card 1028,01c8 rev 01 class 0c,03,20 hdr 00
    (II) PCI: 00:1e:0: chip 8086,2448 card 0000,0000 rev e1 class 06,04,01 hdr 01
    (II) PCI: 00:1f:0: chip 8086,27b9 card 1028,01c8 rev 01 class 06,01,00 hdr 80
    (II) PCI: 00:1f:2: chip 8086,27c4 card 1028,01c8 rev 01 class 01,01,80 hdr 00
    (II) PCI: 00:1f:3: chip 8086,27da card 1028,01c8 rev 01 class 0c,05,00 hdr 00
    (II) PCI: 01:00:0: chip 10de,01dc card 1028,01c8 rev a1 class 03,00,00 hdr 00
    (II) PCI: 03:01:0: chip 1217,7135 card 2001,0000 rev 21 class 06,07,00 hdr 82
    (II) PCI: 03:01:4: chip 1217,00f7 card 1028,01c8 rev 02 class 0c,00,10 hdr 00
    (II) PCI: 09:00:0: chip 14e4,1600 card 1028,01c8 rev 02 class 02,00,00 hdr 00
    (II) PCI: 0c:00:0: chip 8086,4222 card 8086,1021 rev 02 class 02,80,00 hdr 00
    (II) PCI: End of PCI scan
    (II) Intel Bridge workaround enabled
    (II) Host-to-PCI bridge:
    (II) Bus 0: bridge is at (0:0:0), (0,0,13), BCTRL: 0x0008 (VGA_EN is set)
    (II) Bus 0 I/O range:
            [0] -1  0       0x00000000 - 0x0000ffff (0x10000) IX[b]
    (II) Bus 0 non-prefetchable memory range:
            [0] -1  0       0x00000000 - 0xffffffff (0x0) MX[b]
    (II) Bus 0 prefetchable memory range:
            [0] -1  0       0x00000000 - 0xffffffff (0x0) MX[b]
    (II) PCI-to-PCI bridge:
    (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x001a (VGA_EN is set)
    (II) Bus 1 non-prefetchable memory range:
            [0] -1  0       0xed000000 - 0xefefffff (0x2f00000) MX[b]
    (II) Bus 1 prefetchable memory range:
            [0] -1  0       0xd0000000 - 0xdfffffff (0x10000000) MX[b]
    (II) PCI-to-PCI bridge:
    (II) Bus 11: bridge is at (0:28:0), (0,11,11), BCTRL: 0x0002 (VGA_EN is cleared)
    (II) PCI-to-PCI bridge:
    (II) Bus 12: bridge is at (0:28:1), (0,12,12), BCTRL: 0x0002 (VGA_EN is cleared)
    (II) Bus 12 non-prefetchable memory range:
            [0] -1  0       0xecf00000 - 0xecffffff (0x100000) MX[b]
    (II) PCI-to-PCI bridge:
    (II) Bus 9: bridge is at (0:28:2), (0,9,9), BCTRL: 0x0002 (VGA_EN is cleared)
    (II) Bus 9 non-prefetchable memory range:
            [0] -1  0       0xece00000 - 0xecefffff (0x100000) MX[b]
    (II) PCI-to-PCI bridge:
    (II) Bus 13: bridge is at (0:28:3), (0,13,14), BCTRL: 0x0002 (VGA_EN is cleared)
    (II) Bus 13 I/O range:
            [0] -1  0       0x0000e000 - 0x0000efff (0x1000) IX[b]
    (II) Bus 13 non-prefetchable memory range:
            [0] -1  0       0xecc00000 - 0xecdfffff (0x200000) MX[b]
    (II) Bus 13 prefetchable memory range:
            [0] -1  0       0xe0000000 - 0xe01fffff (0x200000) MX[b]
    (II) Subtractive PCI-to-PCI bridge:
    (II) Bus 3: bridge is at (0:30:0), (0,3,7), BCTRL: 0x0002 (VGA_EN is cleared)
    (II) Bus 3 I/O range:
            [0] -1  0       0x00002000 - 0x00002fff (0x1000) IX[b]
    (II) Bus 3 non-prefetchable memory range:
            [0] -1  0       0xecb00000 - 0xecbfffff (0x100000) MX[b]
    (II) Bus 3 prefetchable memory range:
            [0] -1  0       0x88000000 - 0x8bffffff (0x4000000) MX[b]
    (II) PCI-to-ISA bridge:
    (II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
    (II) PCI-to-CardBus bridge:
    (II) Bus 4: bridge is at (3:1:0), (3,4,7), BCTRL: 0x05c0 (VGA_EN is cleared)
    (II) Bus 4 I/O range:
            [0] -1  0       0x00002000 - 0x000020ff (0x100) IX[b]
            [1] -1  0       0x00002400 - 0x000024ff (0x100) IX[b]
    (II) Bus 4 prefetchable memory range:
            [0] -1  0       0x88000000 - 0x8bffffff (0x4000000) MX[b]
    (--) PCI:*(1:0:0) nVidia Corporation unknown chipset (0x01dc) rev 161, Mem @ 0xed000000/24, 0xd0000000/28, 0xee000000/24
    (II) Addressable bus resource ranges are
            [0] -1  0       0x00000000 - 0xffffffff (0x0) MX[b]
            [1] -1  0       0x00000000 - 0x0000ffff (0x10000) IX[b]
    (II) OS-reported resource ranges:
            [0] -1  0       0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
            [1] -1  0       0x000f0000 - 0x000fffff (0x10000) MX[b]
            [2] -1  0       0x000c0000 - 0x000effff (0x30000) MX[b]
            [3] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX[b]
            [4] -1  0       0x0000ffff - 0x0000ffff (0x1) IX[b]
            [5] -1  0       0x00000000 - 0x000000ff (0x100) IX[b]
    (II) Active PCI resource ranges:
            [0] -1  0       0xecfff000 - 0xecffffff (0x1000) MX[b]
            [1] -1  0       0xecef0000 - 0xecefffff (0x10000) MX[b]
            [2] -1  0       0xecbfe800 - 0xecbfefff (0x800) MX[b]
            [3] -1  0       0xecbff000 - 0xecbfffff (0x1000) MX[b]
            [4] -1  0       0xffa80000 - 0xffa803ff (0x400) MX[b]
            [5] -1  0       0xefffc000 - 0xefffffff (0x4000) MX[b]
            [6] -1  0       0xee000000 - 0xeeffffff (0x1000000) MX[b](B)
            [7] -1  0       0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
            [8] -1  0       0xed000000 - 0xedffffff (0x1000000) MX[b](B)
            [9] -1  0       0x000010c0 - 0x000010df (0x20) IX[b]
            [10] -1 0       0x0000bfa0 - 0x0000bfaf (0x10) IX[b]
            [11] -1 0       0x00000374 - 0x00000374 (0x1) IX[b]
            [12] -1 0       0x00000170 - 0x00000177 (0x8) IX[b]
            [13] -1 0       0x000003f4 - 0x000003f4 (0x1) IX[b]
            [14] -1 0       0x000001f0 - 0x000001f7 (0x8) IX[b]
            [15] -1 0       0x0000bf20 - 0x0000bf3f (0x20) IX[b]
            [16] -1 0       0x0000bf40 - 0x0000bf5f (0x20) IX[b]
            [17] -1 0       0x0000bf60 - 0x0000bf7f (0x20) IX[b]
            [18] -1 0       0x0000bf80 - 0x0000bf9f (0x20) IX[b]
    (II) Active PCI resource ranges after removing overlaps:
            [0] -1  0       0xecfff000 - 0xecffffff (0x1000) MX[b]
            [1] -1  0       0xecef0000 - 0xecefffff (0x10000) MX[b]
            [2] -1  0       0xecbfe800 - 0xecbfefff (0x800) MX[b]
            [3] -1  0       0xecbff000 - 0xecbfffff (0x1000) MX[b]
            [4] -1  0       0xffa80000 - 0xffa803ff (0x400) MX[b]
            [5] -1  0       0xefffc000 - 0xefffffff (0x4000) MX[b]
            [6] -1  0       0xee000000 - 0xeeffffff (0x1000000) MX[b](B)
            [7] -1  0       0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
            [8] -1  0       0xed000000 - 0xedffffff (0x1000000) MX[b](B)
            [9] -1  0       0x000010c0 - 0x000010df (0x20) IX[b]
            [10] -1 0       0x0000bfa0 - 0x0000bfaf (0x10) IX[b]
            [11] -1 0       0x00000374 - 0x00000374 (0x1) IX[b]
            [12] -1 0       0x00000170 - 0x00000177 (0x8) IX[b]
            [13] -1 0       0x000003f4 - 0x000003f4 (0x1) IX[b]
            [14] -1 0       0x000001f0 - 0x000001f7 (0x8) IX[b]
            [15] -1 0       0x0000bf20 - 0x0000bf3f (0x20) IX[b]
            [16] -1 0       0x0000bf40 - 0x0000bf5f (0x20) IX[b]
            [17] -1 0       0x0000bf60 - 0x0000bf7f (0x20) IX[b]
            [18] -1 0       0x0000bf80 - 0x0000bf9f (0x20) IX[b]
    (II) OS-reported resource ranges after removing overlaps with PCI:
            [0] -1  0       0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
            [1] -1  0       0x000f0000 - 0x000fffff (0x10000) MX[b]
            [2] -1  0       0x000c0000 - 0x000effff (0x30000) MX[b]
            [3] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX[b]
            [4] -1  0       0x0000ffff - 0x0000ffff (0x1) IX[b]
            [5] -1  0       0x00000000 - 0x000000ff (0x100) IX[b]
    (II) All system resource ranges:
            [0] -1  0       0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
            [1] -1  0       0x000f0000 - 0x000fffff (0x10000) MX[b]
            [2] -1  0       0x000c0000 - 0x000effff (0x30000) MX[b]
            [3] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX[b]
            [4] -1  0       0xecfff000 - 0xecffffff (0x1000) MX[b]
            [5] -1  0       0xecef0000 - 0xecefffff (0x10000) MX[b]
            [6] -1  0       0xecbfe800 - 0xecbfefff (0x800) MX[b]
            [7] -1  0       0xecbff000 - 0xecbfffff (0x1000) MX[b]
            [8] -1  0       0xffa80000 - 0xffa803ff (0x400) MX[b]
            [9] -1  0       0xefffc000 - 0xefffffff (0x4000) MX[b]
            [10] -1 0       0xee000000 - 0xeeffffff (0x1000000) MX[b](B)
            [11] -1 0       0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
            [12] -1 0       0xed000000 - 0xedffffff (0x1000000) MX[b](B)
            [13] -1 0       0x0000ffff - 0x0000ffff (0x1) IX[b]
            [14] -1 0       0x00000000 - 0x000000ff (0x100) IX[b]
            [15] -1 0       0x000010c0 - 0x000010df (0x20) IX[b]
            [16] -1 0       0x0000bfa0 - 0x0000bfaf (0x10) IX[b]
            [17] -1 0       0x00000374 - 0x00000374 (0x1) IX[b]
            [18] -1 0       0x00000170 - 0x00000177 (0x8) IX[b]
            [19] -1 0       0x000003f4 - 0x000003f4 (0x1) IX[b]
            [20] -1 0       0x000001f0 - 0x000001f7 (0x8) IX[b]
            [21] -1 0       0x0000bf20 - 0x0000bf3f (0x20) IX[b]
            [22] -1 0       0x0000bf40 - 0x0000bf5f (0x20) IX[b]
            [23] -1 0       0x0000bf60 - 0x0000bf7f (0x20) IX[b]
            [24] -1 0       0x0000bf80 - 0x0000bf9f (0x20) IX[b]
    (II) LoadModule: "ddc"
    (II) Loading /usr/lib/xorg/modules//libddc.so
    (II) Module ddc: vendor="X.Org Foundation"
            compiled for 7.2.0, module version = 1.0.0
            ABI class: X.Org Video Driver, version 1.1
    (II) LoadModule: "dbe"
    (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
    (II) Module dbe: vendor="X.Org Foundation"
            compiled for 7.2.0, module version = 1.0.0
            Module class: X.Org Server Extension
            ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension DOUBLE-BUFFER
    (II) LoadModule: "extmod"
    (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
    (II) Module extmod: vendor="X.Org Foundation"
            compiled for 7.2.0, module version = 1.0.0
            Module class: X.Org Server Extension
            ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension SHAPE
    (II) Loading extension MIT-SUNDRY-NONSTANDARD
    (II) Loading extension BIG-REQUESTS
    (II) Loading extension SYNC
    (II) Loading extension MIT-SCREEN-SAVER
    (II) Loading extension XC-MISC
    (II) Loading extension XFree86-VidModeExtension
    (II) Loading extension XFree86-Misc
    (II) Loading extension XFree86-DGA
    (II) Loading extension DPMS
    (II) Loading extension TOG-CUP
    (II) Loading extension Extended-Visual-Information
    (II) Loading extension XVideo
    (II) Loading extension XVideo-MotionCompensation
    (II) Loading extension X-Resource
    (II) LoadModule: "glx"
    (II) Loading /usr/lib/xorg/modules/extensions//libglx.so
    (II) Module glx: vendor="NVIDIA Corporation"
            compiled for 4.0.2, module version = 1.0.0
            Module class: X.Org Server Extension
            ABI class: X.Org Server Extension, version 0.1
    (II) NVIDIA GLX Module  100.14.11  Wed Jun 13 18:58:58 PDT 2007
    (II) Loading extension GLX
    (II) LoadModule: "type1"
    (II) Loading /usr/lib/xorg/modules/fonts//libtype1.so
    (II) Module type1: vendor="X.Org Foundation"
            compiled for 7.2.0, module version = 1.0.2
            Module class: X.Org Font Renderer
            ABI class: X.Org Font Renderer, version 0.5
    (II) Loading font Type1
    (II) LoadModule: "freetype"
    (II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
    (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
            compiled for 7.2.0, module version = 2.1.0
            Module class: X.Org Font Renderer
            ABI class: X.Org Font Renderer, version 0.5
    (II) Loading font FreeType
    (II) LoadModule: "record"
    (II) Loading /usr/lib/xorg/modules/extensions//librecord.so
    (II) Module record: vendor="X.Org Foundation"
            compiled for 7.2.0, module version = 1.13.0
            Module class: X.Org Server Extension
            ABI class: X.Org Server Extension, version 0.3
    (II) Loading extension RECORD
    (II) LoadModule: "nvidia"
    (II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
    (II) Module nvidia: vendor="NVIDIA Corporation"
            compiled for 4.0.2, module version = 1.0.0
            Module class: X.Org Video Driver
    (II) LoadModule: "keyboard"
    (II) Loading /usr/lib/xorg/modules/input//keyboard_drv.so
    (II) Module keyboard: vendor="X.Org Foundation"
            compiled for 7.2.0, module version = 1.0.0
            Module class: X.Org XInput Driver
            ABI class: X.Org XInput driver, version 0.7
    (II) LoadModule: "mouse"
    (II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
    (II) Module mouse: vendor="X.Org Foundation"
            compiled for 7.2.0, module version = 1.1.1
            Module class: X.Org XInput Driver
            ABI class: X.Org XInput driver, version 0.7
    (II) NVIDIA dlloader X Driver  100.14.11  Wed Jun 13 18:23:34 PDT 2007
    (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    (II) Primary Device is: PCI 01:00:0
    (--) Assigning device section with no busID to primary device
    (--) Chipset NVIDIA GPU found
    (II) Loading sub module "fb"
    (II) LoadModule: "fb"
    (II) Loading /usr/lib/xorg/modules//libfb.so
    (II) Module fb: vendor="X.Org Foundation"
            compiled for 7.2.0, module version = 1.0.0
            ABI class: X.Org ANSI C Emulation, version 0.3
    (II) Loading sub module "wfb"
    (II) LoadModule: "wfb"
    (II) Loading /usr/lib/xorg/modules//libwfb.so
    (II) Module wfb: vendor="NVIDIA Corporation"
            compiled for 7.1.99.2, module version = 1.0.0
    (II) Loading sub module "ramdac"
    (II) LoadModule: "ramdac"
    (II) Loading /usr/lib/xorg/modules//libramdac.so
    (II) Module ramdac: vendor="X.Org Foundation"
            compiled for 7.2.0, module version = 0.1.0
            ABI class: X.Org Video Driver, version 1.1
    (II) resource ranges after xf86ClaimFixedResources() call:
            [0] -1  0       0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
            [1] -1  0       0x000f0000 - 0x000fffff (0x10000) MX[b]
            [2] -1  0       0x000c0000 - 0x000effff (0x30000) MX[b]
            [3] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX[b]
            [4] -1  0       0xecfff000 - 0xecffffff (0x1000) MX[b]
            [5] -1  0       0xecef0000 - 0xecefffff (0x10000) MX[b]
            [6] -1  0       0xecbfe800 - 0xecbfefff (0x800) MX[b]
            [7] -1  0       0xecbff000 - 0xecbfffff (0x1000) MX[b]
            [8] -1  0       0xffa80000 - 0xffa803ff (0x400) MX[b]
            [9] -1  0       0xefffc000 - 0xefffffff (0x4000) MX[b]
            [10] -1 0       0xee000000 - 0xeeffffff (0x1000000) MX[b](B)
            [11] -1 0       0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
            [12] -1 0       0xed000000 - 0xedffffff (0x1000000) MX[b](B)
            [13] -1 0       0x0000ffff - 0x0000ffff (0x1) IX[b]
            [14] -1 0       0x00000000 - 0x000000ff (0x100) IX[b]
            [15] -1 0       0x000010c0 - 0x000010df (0x20) IX[b]
            [16] -1 0       0x0000bfa0 - 0x0000bfaf (0x10) IX[b]
            [17] -1 0       0x00000374 - 0x00000374 (0x1) IX[b]
            [18] -1 0       0x00000170 - 0x00000177 (0x8) IX[b]
            [19] -1 0       0x000003f4 - 0x000003f4 (0x1) IX[b]
            [20] -1 0       0x000001f0 - 0x000001f7 (0x8) IX[b]
            [21] -1 0       0x0000bf20 - 0x0000bf3f (0x20) IX[b]
            [22] -1 0       0x0000bf40 - 0x0000bf5f (0x20) IX[b]
            [23] -1 0       0x0000bf60 - 0x0000bf7f (0x20) IX[b]
            [24] -1 0       0x0000bf80 - 0x0000bf9f (0x20) IX[b]
    (II) resource ranges after probing:
            [0] -1  0       0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
            [1] -1  0       0x000f0000 - 0x000fffff (0x10000) MX[b]
            [2] -1  0       0x000c0000 - 0x000effff (0x30000) MX[b]
            [3] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX[b]
            [4] -1  0       0xecfff000 - 0xecffffff (0x1000) MX[b]
            [5] -1  0       0xecef0000 - 0xecefffff (0x10000) MX[b]
            [6] -1  0       0xecbfe800 - 0xecbfefff (0x800) MX[b]
            [7] -1  0       0xecbff000 - 0xecbfffff (0x1000) MX[b]
            [8] -1  0       0xffa80000 - 0xffa803ff (0x400) MX[b]
            [9] -1  0       0xefffc000 - 0xefffffff (0x4000) MX[b]
            [10] -1 0       0xee000000 - 0xeeffffff (0x1000000) MX[b](B)
            [11] -1 0       0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
            [12] -1 0       0xed000000 - 0xedffffff (0x1000000) MX[b](B)
            [13] 0  0       0x000a0000 - 0x000affff (0x10000) MS[b]
            [14] 0  0       0x000b0000 - 0x000b7fff (0x8000) MS[b]
            [15] 0  0       0x000b8000 - 0x000bffff (0x8000) MS[b]
            [16] -1 0       0x0000ffff - 0x0000ffff (0x1) IX[b]
            [17] -1 0       0x00000000 - 0x000000ff (0x100) IX[b]
            [18] -1 0       0x000010c0 - 0x000010df (0x20) IX[b]
            [19] -1 0       0x0000bfa0 - 0x0000bfaf (0x10) IX[b]
            [20] -1 0       0x00000374 - 0x00000374 (0x1) IX[b]
            [21] -1 0       0x00000170 - 0x00000177 (0x8) IX[b]
            [22] -1 0       0x000003f4 - 0x000003f4 (0x1) IX[b]
            [23] -1 0       0x000001f0 - 0x000001f7 (0x8) IX[b]
            [24] -1 0       0x0000bf20 - 0x0000bf3f (0x20) IX[b]
            [25] -1 0       0x0000bf40 - 0x0000bf5f (0x20) IX[b]
            [26] -1 0       0x0000bf60 - 0x0000bf7f (0x20) IX[b]
            [27] -1 0       0x0000bf80 - 0x0000bf9f (0x20) IX[b]
            [28] 0  0       0x000003b0 - 0x000003bb (0xc) IS[b]
            [29] 0  0       0x000003c0 - 0x000003df (0x20) IS[b]
    (II) Setting vga for screen 0.
    (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
    (==) NVIDIA(0): RGB weight 888
    (==) NVIDIA(0): Default visual is TrueColor
    (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    (**) NVIDIA(0): Option "NoLogo" "True"
    (**) NVIDIA(0): Option "RenderAccel" "True"
    (**) NVIDIA(0): Option "AllowGLXWithComposite" "True"
    (**) NVIDIA(0): Option "AddARGBGLXVisuals" "True"
    (**) NVIDIA(0): Enabling RENDER acceleration
    (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
    (II) NVIDIA(0):     enabled.
    (II) NVIDIA(0): NVIDIA GPU Quadro FX 350M (G72GL) at PCI:1:0:0 (GPU-0)
    (--) NVIDIA(0): Memory: 524288 kBytes
    (--) NVIDIA(0): VideoBIOS: 05.72.23.21.a1
    (II) NVIDIA(0): Detected PCI Express Link width: 16X
    (--) NVIDIA(0): Interlaced video modes are supported on this GPU
    (--) NVIDIA(0): Connected display device(s) on Quadro FX 350M at PCI:1:0:0:
    (--) NVIDIA(0):     Seiko (DFP-0)
    (--) NVIDIA(0): Seiko (DFP-0): 330.0 MHz maximum pixel clock
    (--) NVIDIA(0): Seiko (DFP-0): Internal Dual Link LVDS
    (II) NVIDIA(0): Assigned Display Device: DFP-0
    (WW) NVIDIA(0): No valid modes for "1900x1200"; removing.
    (WW) NVIDIA(0):
    (WW) NVIDIA(0): Unable to validate any modes; falling back to the default mode
    (WW) NVIDIA(0):     "nvidia-auto-select".
    (WW) NVIDIA(0):
    (II) NVIDIA(0): Validated modes:
    (II) NVIDIA(0):     "nvidia-auto-select"
    (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1200
    (--) NVIDIA(0): DPI set to (147, 145); computed from "UseEdidDpi" X config
    (--) NVIDIA(0):     option
    (WW) NVIDIA(0): UBB is incompatible with the Composite extension.  Disabling
    (WW) NVIDIA(0):     UBB.
    (**) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
    (--) Depth 24 pixmap format is 32 bpp
    (II) do I need RAC?  No, I don't.
    (II) resource ranges after preInit:
            [0] 0   0       0xee000000 - 0xeeffffff (0x1000000) MX[b]
            [1] 0   0       0xd0000000 - 0xdfffffff (0x10000000) MX[b]
            [2] 0   0       0xed000000 - 0xedffffff (0x1000000) MX[b]
            [3] -1  0       0x00100000 - 0x3fffffff (0x3ff00000) MX[b]E(B)
            [4] -1  0       0x000f0000 - 0x000fffff (0x10000) MX[b]
            [5] -1  0       0x000c0000 - 0x000effff (0x30000) MX[b]
            [6] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX[b]
            [7] -1  0       0xecfff000 - 0xecffffff (0x1000) MX[b]
            [8] -1  0       0xecef0000 - 0xecefffff (0x10000) MX[b]
            [9] -1  0       0xecbfe800 - 0xecbfefff (0x800) MX[b]
            [10] -1 0       0xecbff000 - 0xecbfffff (0x1000) MX[b]
            [11] -1 0       0xffa80000 - 0xffa803ff (0x400) MX[b]
            [12] -1 0       0xefffc000 - 0xefffffff (0x4000) MX[b]
            [13] -1 0       0xee000000 - 0xeeffffff (0x1000000) MX[b](B)
            [14] -1 0       0xd0000000 - 0xdfffffff (0x10000000) MX[b](B)
            [15] -1 0       0xed000000 - 0xedffffff (0x1000000) MX[b](B)
            [16] 0  0       0x000a0000 - 0x000affff (0x10000) MS[b](OprD)
            [17] 0  0       0x000b0000 - 0x000b7fff (0x8000) MS[b](OprD)
            [18] 0  0       0x000b8000 - 0x000bffff (0x8000) MS[b](OprD)
            [19] -1 0       0x0000ffff - 0x0000ffff (0x1) IX[b]
            [20] -1 0       0x00000000 - 0x000000ff (0x100) IX[b]
            [21] -1 0       0x000010c0 - 0x000010df (0x20) IX[b]
            [22] -1 0       0x0000bfa0 - 0x0000bfaf (0x10) IX[b]
            [23] -1 0       0x00000374 - 0x00000374 (0x1) IX[b]
            [24] -1 0       0x00000170 - 0x00000177 (0x8) IX[b]
            [25] -1 0       0x000003f4 - 0x000003f4 (0x1) IX[b]
            [26] -1 0       0x000001f0 - 0x000001f7 (0x8) IX[b]
            [27] -1 0       0x0000bf20 - 0x0000bf3f (0x20) IX[b]
            [28] -1 0       0x0000bf40 - 0x0000bf5f (0x20) IX[b]
            [29] -1 0       0x0000bf60 - 0x0000bf7f (0x20) IX[b]
            [30] -1 0       0x0000bf80 - 0x0000bf9f (0x20) IX[b]
            [31] 0  0       0x000003b0 - 0x000003bb (0xc) IS[b](OprU)
            [32] 0  0       0x000003c0 - 0x000003df (0x20) IS[b](OprU)
    (II) NVIDIA(0): Setting mode "nvidia-auto-select"
    (II) Loading extension NV-GLX
    (II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
    (II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
    (==) NVIDIA(0): Backing store disabled
    (==) NVIDIA(0): Silken mouse enabled
    (**) Option "dpms" "true"
    (**) NVIDIA(0): DPMS enabled
    (II) Loading extension NV-CONTROL
    (==) RandR enabled
    (II) Initializing built-in extension MIT-SHM
    (II) Initializing built-in extension XInputExtension
    (II) Initializing built-in extension XTEST
    (II) Initializing built-in extension XKEYBOARD
    (II) Initializing built-in extension XC-APPGROUP
    (II) Initializing built-in extension XAccessControlExtension
    (II) Initializing built-in extension SECURITY
    (II) Initializing built-in extension XINERAMA
    (II) Initializing built-in extension XFIXES
    (II) Initializing built-in extension XFree86-Bigfont
    (II) Initializing built-in extension RENDER
    (II) Initializing built-in extension RANDR
    (II) Initializing built-in extension COMPOSITE
    (II) Initializing built-in extension DAMAGE
    (II) Initializing built-in extension XEVIE
    (II) Initializing extension GLX
    (**) Option "CoreKeyboard"
    (**) Keyboard0: Core Keyboard
    (**) Option "Protocol" "standard"
    (**) Keyboard0: Protocol: standard
    (**) Option "AutoRepeat" "500 30"
    (**) Option "XkbRules" "xorg"
    (**) Keyboard0: XkbRules: "xorg"
    (**) Option "XkbModel" "pc105"
    (**) Keyboard0: XkbModel: "pc105"
    (WW) Option "XkbLayout" requires an string value
    (WW) Option "XkbVariant" requires an string value
    (**) Option "CustomKeycodes" "off"
    (**) Keyboard0: CustomKeycodes disabled
    (**) Option "Protocol" "auto"
    (**) PS/2 Mouse: Device: "/dev/psaux"
    (**) PS/2 Mouse: Protocol: "auto"
    (**) Option "SendCoreEvents" "true"
    (**) PS/2 Mouse: always reports core events
    (**) Option "CorePointer"
    (**) PS/2 Mouse: Core Pointer
    (**) Option "Device" "/dev/psaux"
    (**) Option "Emulate3Buttons" "true"
    (**) Option "Emulate3Timeout" "70"
    (**) PS/2 Mouse: Emulate3Buttons, Emulate3Timeout: 70
    (**) Option "ZAxisMapping" "4 5"
    (**) PS/2 Mouse: ZAxisMapping: buttons 4 and 5
    (**) PS/2 Mouse: Buttons: 9
    (II) XINPUT: Adding extended input device "PS/2 Mouse" (type: MOUSE)
    (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
    (--) PS/2 Mouse: PnP-detected protocol: "ExplorerPS/2"
    (II) PS/2 Mouse: ps2EnableDataReporting: succeeded

  • [SOLVED] Windows 8 made all my arch partition unallocated space

    Hi, I've been using arch for the past 8 months without any problem. I used to have win 7 and fedora on my laptop also.I used the bootloader from fedora to boot arch. Yesterday I decided to replace win7 with win8. After playing around with it, it was time to return to my arch, so I grabbed a live cd and booted, chrooted to my fedora and reinstalled grub. Everything fine but when I rebooted and selected Arch to start I got error that the partition doesn't exist. I booted into fedora and really, gparted shows all my 3 arch partitions as unallocated space. Why only arch has been deleted, and is there a way to save it somehow? I don't know the exact size of the previous partitions. Thanks
    Last edited by raxbg (2012-03-15 06:52:33)

    fdisk seems to find the partition table correctly, but I will not try to write it to the disk since it is now working. Im gonna buy a USB Hard drive and move everything important there first, then I will experiment Thank you for your help

  • My USB mouse can not use in kernel2.6.9-ARCH

    my Microsoft wheel Optical  USB mouse works well in arch0.6 (with kernel2.6.3), but after I update kernel to 2.6.9-ARCH, my mouse device can not works. The red LED have no light.
    But when I install kernel2.6.9 which compile by myself, the mouse works well.
    Why?

    arch kernel 2.6.9 got no built in usb support,
    you have to load the modules yourself or use hotplug,
    if you compile your own kernel you can compile it with built in usb and your mouse will work witout doing anything more,

  • Why /opt? and does it matter?

    I'm just wondering why many Arch packages by default are installed in the /opt directory. I'm just not use to it yet, but are there any real reasons as to why?
    Is it to make it easier to know what you've installed? Like making them seperate from the base install?
    I found this quote from a review at linuxquestions.org
    A few issues that could be a negative is that while a benefit, it can also be a problem with installing everything in /opt. This causes the bin directory to be out of the PATH, so you need to constantly edit the path to include the new installed package bin directory. If done carelessly, this can be a security issue.
    I'm coming from a Slackware background and I'm use to everything (most) being installed under /usr...etc.'
    Anyway, just wondering.
    Thanks for reading.

    oops, sorry . I did however try looking and well I didn't really get the answer I was looking for.
    Time to let it die.
    PS:  My bad

Maybe you are looking for

  • How can I get itunes to recognize my 7th gen. ipod nano

    My wife bought me an ipod nano the other day and I am unable to get itunes to recognize it in the device menu. I have spent over 2 hrs attempting differnt suggestions with no results. I down loaded the newest version of itunes and when I plugged in m

  • Payment card not valid for Poland?

    How come is my payment card not valid for Poland? I purchased some application for my iPhone like a few months ago and it was ok and today I wanted to buy some song and that kind of message showed up: "Your payment card is not valid for Poland". What

  • Can i still get the 10.5.8 upgrade from 10.3.9

    Can i still get the 10.5.8 upgrade from 10.3.9 and will this help preformance

  • Credit Card Processing unavailable right now?!

    I keep getting an error message from the App Store, "Credit Card Processing temporarily unavailable right now" or something close. I know I have money on my MC and am simply trying to make in app purchase. Anyone else getting this message??

  • Viewing specific rows only

    hi, is there a way to only view certain rows in a resultset, i wanted to add a 1 out of 10 pages link on a jsp or servlet page along with the data that fits into that page. but i don't want to have to loop through the entire resultset picking out onl