The subject line is full and the browser will not accept additional keystrokes. I think I'll need to start prefixing all my requests for X logs with "uninstall xf86-video-vesa". ALL RIGHT! Perhaps I need to change to another console (Alt-F7 or another) in order to actually see the running X? I've never used, or needed, the vesa driver on bare metal. (sorry, l missed this information) The title says 'mesa' but I meant 'vesa'. Package: kernel-image-2.4.6-i386 Version: 2.4.6-1 It would be nice if the i386 kernel images would be compiled with: CONFIG_FB_VESA=y If people are upgrading from a 2.2.x-idepci kernel image and/or have video=vesa set as a boot option, the default 2.4 kernel images will boot with a blank screen unless "vga=normal" is set. This driver was designed and introduced as a generic driver for any video card which has VESA VBE 2.0 compatible BIOS. - is not actually correct. I'm going to back off, and think about this; I want to be asking good questions, and not ones I can deduce myself. I don't seem to have problems with any of the *buntu LiveCDs. And in "System Settings" / "Display & Monitor" (or something like that, this is from memory) I could see the Monitor listed as 1024X768 (75Hz), which is just what the Win XP I'm typing on shows. Note Big Grey is not new behavior; sometimes I've seen text failures, sometimes I've had to exit from Greyness to see same / similar text failures. I'm satisfied in all particulars except mildly mystified as to why this is called "10-monitor.conf" (mine now looks more like a 10-videodriver.conf ). $$$$$ Forum Team --- thank you for doing what you do (this place wouldn't work without you); please reclassify this if you feel it would be better posted in "Installation" than "Newbie Corner". I removed (pacman -R) xf86-video-ati then mesa-demos then mesa, almost, mesa wouldn't remove (nice, this pacman may be the central tool of Arch), finally added xf86-video-mach64. Please consult the The X.Org Foundation support      at http://wiki.x.org for help. But the reference to "mach64" seems to have disappeared, a fate that didn't befall either "vesa" or "fbdev". Join the global Raspberry Pi community. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Nov  2 12:47:20 2011(==) Using config directory: "/etc/X11/xorg.conf.d"(EE) Failed to load module "mach64" (module does not exist, 0)(EE) Failed to load module "vesa" (module does not exist, 0)(EE) Failed to load module "fbdev" (module does not exist, 0)(EE) No drivers available. This post lacks information. And this antique has a Rage XL card (8MB I believe), so I chose the open-source xf86-video-ati driver. $$$$$  Here's wgetpaste access for the two logfiles (I don't know how to make these "inline" scrollable windows - if someone might advise then any future posts will have those): -rw-r--r-- 1 root root 7438 Nov  2 10:41 /var/log/Xorg.0.log ---> (wgetpaste _via_ /dos/ to) http://paste.pocoo.org/show/501834-rw-r--r-- 1 root root 2525 Nov  2 09:34 /var/log/Xorg.0.log.old ---> (wgetpaste _via_ /dos/ to) http://paste.pocoo.org/show/501833. Seems like the only people who need xf86-video-intel these days are people with oddball multi-monitor setups. But alas I don't (yet) know how to evaluate either of these. Any of the other display modes can be selected with xrandr (1). And me? Another advantage of this driver is that it tries to force TV output on. Apparently fbdev is just not necessary, ditto ati. So I don't see it (whatever "it" is), so far. And incidentally, it's not obvious to me (yet) how to mark this as SOLVED (so if someone might advise...). I'll look forward to your careful review (please echo what you consider relevant). VESA BIOS EXTENSION (VBE) Version 3.0 Date: September 16, 1998 (Page 70) says: Which means that part of the configuration is not what contributes to the "fix". Perhaps I'll get time to just roll another netinstall (10_GB disk, I don't need a /home anyway...), and start fresh next Monday. Choose 8. 3310. VESA in summary. Current version of pixman: 0.22.2    Before reporting problems, check http://wiki.x.org    to make sure that you have the latest version.Markers: (--) probed, (**) from config file, (==) default setting,    (++) from command line, (!!) Here are both current and old Xorg.0.log files: I'm typing this from WinXP Pro; Display Properties / Settings tells me Rage XL PCI (correct, and FWIW I believe an 8MB card), 1024 X 768 (native & highest resolution for the formerly rackmounted LCD "Samsung SyncMaster 570S/580S TFT", so also correct), and Color quality "Highest (32 bit)" (I don't know how to tell if this is correct, so I'm merely reporting it). Thanks all for reading. Work is light so far, so I've run the lspci -k as you requested (thank you for the participation), and thrown in a dmesg for good measure: However, thinking away from the screen let me realize that I was overlooking a valuable tool. Sorry, no. I've been using the modesetting default as per someone's suggestion and it works, but should I expect better 2D performance from the Intel driver? I'm going to just enjoy using Arch for a while but also lurk around the forums (perhaps something I know can be useful, payback & payforward both). The actual resolutions and number of colors available using the VESA driver depends on the video adapter. So I went for KDE here (my Gentoo runs Gnome, I like both). For example, to switch to 1280x1024 at 60 Hz: % xrandr --mode 1280x1024 --rate 60. You have no working video driver - vesa won't go near it. So I ran wild, pacman -S xf86-video-ati xf86-video-vesa xf86-video-fbdev (remember that at this point xf64-video-mach64 is still installed), and finally another startx: I wgetpaste'd the latest /var/log/Xorg.0.log and /var/log/Xorg.0.log.old. VESA Updates DisplayHDR Standard with Tighter Specifications and New DisplayHDR 1400 Performance Level. When I compare the (previously posted, fails) (Arch) Xorg.0.log to the (successful) (Lubuntu) Xorg.0.log, I see that they diverge when the latter fails to LoadModule on "fglrx" but then goes on to load "ati" then "mach64" then "vesa" then "fbdev". I have tested more of different settings and I ended up for now with this setting, since I do not need sound it is OK for me. That will allow me to repartition slash anyway, move /home to a spare partition on another drive. "the splashscreen is not installed so cannot be activated" - new install, no splash, help! Per your request, I ran additional testing. As I can't get X running, I have to use a WinXP (the dual-boot portion of same computer) with FAT32 partition for data transfer (& some notepad-to-wordpad ux2dos-style conversions); I don't think that's introduced any artifacts, but can't be sure. Thanks all for your attention. * Icons off the K-button seem to have a cross-hatching and colorless aspect to them. unknown. Last edited by Gusar (2011-11-05 17:25:25). I'm no twm fan, but FWIW it looked OK.... TEST Runlevel 3 / root / startx ---> (with ~/.xinitrc that execs startkde) ---> /var/log/Xorg.0.log. It can drive most VESA-compatible video cards, but only makes use of the basic standard VESA core that is common to these cards. I like a full-feature desktop, but Gnome 3 refused (no doubt balking at my fossil video card), and Gnome 2 seemed kinda rough around the edges. I'll have to carefully look at the logs. This seems harder than it should. X.Org X Server 1.11.1.902 (1.11.2 RC 2)Release Date: 2011-10-28X Protocol Version 11, Revision 0Build Operating System: Linux 3.1.0-2-ARCH i686 Current Operating System: Linux xw4600 3.0-ARCH #1 SMP PREEMPT Wed Oct 19 12:14:48 UTC 2011 i686Kernel command line: root=/dev/disk/by-uuid/dc10849c-493b-4176-a9b9-114bdc7d6416 roBuild Date: 30 October 2011  09:00:20AM. That is, if I put the pointer on the shutdown icon, KDE wouldn't then offer the shutdown / reboot / {others} actions, but would instead show me the results of the recently-used icon. I'll look forward to future updates (yourself or others) on this developing thread. Just edit your first post, there you (and only you) will get access to the title line ("Subject"). Make sure your monitor supports this resolution prior to configuring it. So install xf86-video-mach64 and remove all other x86-video-* packages. unknown. Particularly with gradients. The fourth time was the charm. Does Xorg's built-in driver benefit from GPU-based hardware acceleration as Intel's solution does? Last edited by Gusar (2011-11-14 20:12:10), https://wiki.archlinux.org/index.php/Xinitrc, https://bbs.archlinux.org/viewtopic.php … 3#p1011433. Press question mark to learn the rest of the keyboard shortcuts. To know or not to know ...... the questions remain forever. * Ctrl+Alt+F2 got me to a command prompt, in order to do some wgetpaste-ing. And if that's the case, how come Ubuntu picks up on that automatically and Arch doesn't? We all missed it, that there might be another configuration file, some place to tell the kernel which video driver to use. Default settings managed by the distribution are available as well (partially through the Portage package defaults, partially through the Gentoo profile that is in use). The display was (I believe) both dim and low-contrast. That's it, my friend. Resolved!!! not if you are a AMD type of guy. Thanks for your attention. Does it mean this graphic card is so old it can't handle 24bit? If it won't work, we will have the final fix, and thus gain full enlightenment : ATi Rage cards require explicit driver assignment. No, you shouldn't. Just edit your first post, there you (and only you) will get access to the title line ("Subject"). So I'm going to suspect that my installation has diverged from "normal" (Who's to say what's normal..? Currently CONFIG can not report whether the command succeeded or not. libva-intel-driver is for VA-API video acceleration. I think I'll need to start prefixing all my requests for X logs with "uninstall xf86-video-vesa". Trust me, it's noticeable. This driver is often used as fallback driver if the hardware specific and VESA drivers fail to load or are not present. Whether a TV wall mount is fixed, tilt able, turn able or swiveling, the VESA mounting size is always the same: horizontal x vertical distance in mm. Thanks -- Alex Thanks karol. Perhaps this is a valuable clue.... Last edited by truebuilder (2011-11-05 16:23:12). Please also check the log file at "/var/log/Xorg.0.log" for additional information. Unless someone has a better idea, I'd say we should just let this one go by the wayside. The Lubuntu logfile has this to say about "ati" & "mach64": Here's the Lubuntu LiveCD reading on that directory: And here's a reality check on the startx-fails Arch: The slightly different sizes for all five files are undoubtedly explained as slightly different versions; the only other difference I see is more liberal use of the execute bit, and that can't matter. Add that [SOLVED] to the title (as everyone does). Can you do one final test? The final Portage configuration is not only based on make.conf. When adding 'xdriver=vesa nomodeset' as kernel boot options and then booting anaconda, it seems that VESA driver was not selected, but CIRRUS was selected instead. There may be an "xf86-video-SiS" or something like it package for X. you need that one badly. Thanks for your faith, Gusar. Two days of Googling turned up that ArchLinux's own Xorg Getting Started knows. I see the problem. is a mystery to me, but you'll know. After installation the 'xdriver=vesa' option is not passed to grub.conf, but 'modeset' is (that could be anaconda bug perhaps). $$$$$  _After_ I get X running, I'll probably go on for either Gnome or LXDE, satisfy myself all is well, and then wipe & redo from netinstall (if I can do this twice...). You need xf86-video-mach64. I believe you're onto something. I'm curious about the actual fix though. notice, (II) informational,    (WW) warning, (EE) error, (NI) not implemented, (??) (==) Log file: "/var/log/Xorg.0.log", Time: Wed Nov  2 10:41:37 2011(==) Using config directory: "/etc/X11/xorg.conf.d"(EE) Failed to load module "mach64" (module does not exist, 0)(EE) Failed to load module "vesa" (module does not exist, 0)(EE) Failed to load module "fbdev" (module does not exist, 0)(EE) No drivers available. I'm using an Optimus-enabled laptop & reading through the comments, I thought xf86-video-intel is a package that must be installed alongside bumblebee? Reply Quote 0. That bought me a slightly different output; the only substantive line changed was from. Prepend [SOLVED] there and done. If this driver is not installed, Xorg Server will print a warning on startup, but it can be safely ignored if hardware specific driver works well. Pretty unrelated... New comments cannot be posted and votes cannot be cast, Looks like you're using new Reddit on an old browser. xf86-video-mesa is not a thing, I think you're confusing it with xf86-video-vesa which is a fallback driver for very old machines. Thanks again for the suggestion, Gunar. The Slackware essentials book just talks about XF86 all the time, not x.org. I'm new to Arch Linux, but not to Linux (I've been using the following distros for a decade or so, roughly in this sequence: Slackware, Redhat, SuSE, Debian, *buntu, & just this autumn Gentoo also) or Unix (I've been call-center-style professional support for a major computer vendor for fifteen years), and plan to be "always learning". --- that's what you meant, right? -set "section property=value" CONFIG will attempt to set the property to new value. In order to use the vesa driver, i created a new xorg.conf file following the instructions of this link : SDB:Configuring graphics cards - openSUSE (section 4.5). Prepend [SOLVED] there and done. Hmmm. To sum up, VESA is a standard adopted by all important television manufacturers. But, let me make a query that what is the main difference between Intel's xf86-video-intel driver and generic modosetting driver? Create a user and a light .xinitrc for him with some wm - twm is fine. To download Node.js v10.x, use the Node.js > Downloads > Previous Releases page.. For more information about Node.js's Long Term Support (LTS) schedule, see: Node.js > Releases. $$$$$  I don't have either an ~/.xinitrc (still working as root, will worry about as a user later) or an xorg.conf: ls: cannot access /root/.xinitrc: No such file or directoryls: cannot access /etc/X11/xorg.conf: No such file or directory/var/log/Xorg.0.log/var/log/Xorg.0.log.old. Yo… Either Ubuntu patches X (similar to how Arch does if for Nvidia cards) or they some extra magic before starting X. And I even located ati-dri and tried with that. (Warning: you can only undo this mode by restarting DOSBox.) Despite that, I think I got what I wanted: it seems one needs to explicitly specify mach64 on Arch, whereas this is not needed on Ubuntu. ActiveX not installed for IP Camera I am stuck trying to get a download to be applies to my ipcamera or my IE version 11.2. Could affect which resolutions are available. The only thing I see is setting depth to 16bit. And thank you, Gusar. Last edited by truebuilder (2011-11-02 20:07:15). What does Intel's driver provide us and what does not? I had to take a good look at what the code actually does differently from what is default. When I created (the default is apparently no such) /etc/X11/xorg.conf.d/10-monitor.conf with just its example: I could get twm up on vesa; changing vesa to mach64 got me up on that. Let me be clear; "startx" (root or an unprivileged user) doesn't seem to give me an X graphical session, but instead dumps me back to a shell prompt in a minute or so. Ok, we still won't know why Arch requires this and Ubuntu doesn't... Last edited by Gusar (2011-11-12 15:28:05). This driver for the X.Org X server (see xserver-xorg for a further description) uses the standard VESA interface provided on all video cards, but runs unaccelerated. I'm satisfied in all particulars except mildly mystified as to why this is called "10-monitor.conf" (mine now looks more like a 10-videodriver.conf ). Yep, you're definitely using 16bit in Arch, but 24/32bit in Ubuntu. Processor: Not Available & Installed memory (RAM): Not Available Hello, and I would like to thank you in advance for reviewing my question. At this time, Node.js v12.x is the Active LTS version listed on the Node.js homepage as the default download. It's not possible either to create a new configfile or languagefile in this mode. Windows users can use the *.msi installers for x86 or x64 depending on your Windows installation. It can drive most VESA-compatible video cards, but only makes use of the basic standard VESA core that is common to these cards. Results were identical to the Runlevel 5 that I've outlined below (experimentation and note composition just aren't synchronized - this was chronologically the third of the three tests, "5" was the second). And thank you three and karol; this seems a rich forum, I'm glad I'm here. But your subtle reminder that root is a security risk _is_ an excellent point. No need to actually post the response though (unless you've something you want to convey ), Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael FaradaySometimes it is the people no one can imagine anything of who do the things no one can imagine. Adoption of DisplayHDR continues to grow with more than 125 certified display models introduced to date. Important. The only other difference between the logs is this:Ubuntu: Try this: Reduce 10-monitor.conf to just the Device section, remove the other parts. Loading More Posts. VESA 800 x 600. Help and Support. My first Arch install went well, up on CLI in no time (my compliments to those who labor to create such ease, and such directions). $$$$$  Here's the "startx" (no options) error: This is a pre-release version of the X server from The X.Org Foundation.It is not supported in any way.Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.Select the "xorg" product for bugs you find in this release.Before reporting bugs in pre-release versions please check thelatest version in the X.Org Foundation git repository.See http://wiki.x.org/wiki/GitPage for git access instructions. You also don't need xf86-video-intel if you have a recent (Sandy Bridge+) Intel graphics card, because those are better supported by the generic modesetting driver that's built into Xorg. * System Settings / Display and Monitor showed: With reboot based upon the four-line 10-monitor.conf that would be 75.0 Hz.... * Mousing for a reboot..., the mouse pointer had to be a full icon to the right of where the action seemed to be occurring. Last edited by Gusar (2011-11-10 11:59:39), With a /etc/X11/xorg.conf.d/10-monitor.conf composed only of, I get this /var/log/Xorg.0.log. Here's my complete recipe (that others might benefit from my hardfought knowledge): Here are the copied files:/etc/rc.conf/etc/fstab/etc/inittab/boot/grub/menu.lst/etc/X11/xorg/conf.d/10-evdev.conf/etc/X11/xorg/conf.d/10-monitor.conf. The driver supports depths 8, 15 16 and 24. I'm now doing 24-bit (or perhaps 32-bit) color, whereas I was before doing 16-bit (I'm not sure that I can detect the distinction, but it's nice to get what the system can deliver). Higher bit depth, lower maximum clock. 2. but I get the following error:. Hello, I just installed Opensuse 12.1 on an old laptop (amilo pro v3515). Hi all, I've some trouble with my graphic card (nvidia 9300GE, 256Mo) : It's recognized by sax2 as a "Vesa frame buffer". With the four-line version of /etc/X11/xorg.conf.d/10-monitor.conf absent I received the following results: TEST Runlevel 3 / root / startx ---> twm (oops, no ~/.xinitrc) ---> /var/log/Xorg.0.log. ), and hit the Big Red Button, just do a fresh netinstall. Note that after rebooting with four-line 10-monitor.conf, this works perfectly; I can Ctrl+Alt+F2 then Ctrl+Alt+F7, and the display is as it was before, as it should be. @truebuilder: Could you post an Xorg.0.log from Arch now that it's working? Thank you all for your advice and attention. However, I'm having X11 problems, as in it-won't-start. I needed full HD resolution on my display, so I use this additional setting in config (you just add these lines to config and restart device) by hdmi_drive=2I set it to DMT (Display Monitor Timings; the standard typically used by monitors) by hdmi_mode=82I set resolution to 1920x1080 @60Hz (1080p) If you want to read more about supported resolution, you can find a very useful article here. Thus I'm inclined to consider this an issue within either pacman or the kernel (the loading of modules). And indeed, I don't have a /dev/fb0, Google didn't seem to be enlightening about just rolling-your-own (I don't yet know any of the methods _in Linux_ for creating device files - it's probably not that easy anyway). xf86-video-mesa is not a thing, I think you're confusing it with xf86-video-vesa which is a fallback driver for very old machines. A common task is using the external video output on a notebook computer for a video … I've been searching for an answer on how to fix this for quite some time on the internet, and I'm still lost. I followed various setup directions in several pages below archlinux.org, but the errors I'm getting suggest I'm missing something quite basic, and for life of me.... Google was almost useful, but not quite, thus this query. It was almost impossible to use, I couldn't even perform a reboot (I had to do that from the F2 console instead). To make the installed system use the vesa driver, anaconda should in fact have written a /etc/X11/xorg.conf file which specifies 'vesa' as the driver. I noticed that the normal vesa driver wasn't chosen automaticaly, instead of that i got "software rasterizer". The Raspberry Pi is a tiny and affordable computer that you can use to learn programming through fun, practical projects. The refresh rate is not set by the VESA … Current version of pixman: 0.22.2    Before reporting problems, check http://wiki.x.org    to make sure that you have the latest version.Markers: (--) probed, (**) from config file, (==) default setting,    (++) from command line, (!!) Thank you, Moderator ewaller, I was wondering how some of the formatting was done. Lately I've fallen out of love with Canonical, however; want to have more control of the installation, be more involved with the troubleshooting, and stick with distributions that offer two things [1] text-based configuration (no Unity-style "binary blobs", thank you), and [2] rolling upgrades (always blee..., uhhh, cutting-edge --- and the reason why Gentoo runs my other web-facing box). Then post Xorg.0.log again. since my desktop is working smoothly without these drivers already.ThanksUPDATE: I have Intel i5 4th gen processor, no dedicated graphics card. Nothing seems to get me further than X seeming to start, big grey screen, hung forever, and when I Control+Alt+Backspace out, I see a variation on failures already posted. I have debian installed with KDE as the desktop environment, the following situation happened after I uninstalled nvidia-driver. 2. now updated. Then I'll return to the history here, and see what jells out. There is no xorg.conf file so I run sudo X -configure to regenerate the file for my Intel driver. sudo X -configure output (pasted /var/log/xorg.0.log) mach64 is definitely the right driver to use. I've tried it without the "ati", with only the "mach64", with all four. Please note that this is not related to the "Stacks=" line in the Config.sys file, which is used for 16-bit MS-DOS device drivers. You can name the file grblj.conf if you want. Then 9. Which means the mode you've set up in your 10-monitor.conf does nothing. edit: you used to need xf86-video-vesa inside virtualbox, though I don't know if it's still that way. This parameter is only considered by anaconda / live boot; it is *not* read by anything during boot of a normal installed system. Yup! Getting "memory configuration is not optimal press f1 to continue" After memory is installed [ Edited ] I replaced the entire fleet of 2gb memory sticks in a Dell Poweredge R715 with: Crucial 16GB Kit (2 x 8GB) DDR3-1600 ECC RDIMM (Part#CT5321400). Before I loaded pacman -S xf86-video-mach64 I was failing to load "mach64"; after I added it I was failing to load "ati". pardon me for missing information on processors. Other day someone posted an image of Arch Linux installation guide in this subreddit showing that we should install these two drivers.My question is should I or should I not install these drivers? notice, (II) informational,    (WW) warning, (EE) error, (NI) not implemented, (??) TEST Runlevel 5 / non-root ---> Abbey-normal KDE, here's the /var/log/Xorg.0.log; what I noticed that seemed, well, interesting (note that _all_ of these were eliminated by returning the 10-monitor.conf): * Taskbar stretched from the lower-left corner to about 70% of the way across (yet the peanut thingie was indeed in the upper-right corner). The recommended mode is 1024x768 with 256 colors. … vesa to nvidia It works fine, but I have a GeForce4 420 Go card as my lspci dutifully tells me, and I want to know how to change xorg.conf to specify it properly. See anaconda logs. I think I get it now. Monitors are not attached to the DisplayPort-0 and HDMI-0 connectors. Choose Config / tools. Regarding that maximum clock, (line 233 in the URL). I see (line 111 in the URL). Not processing this CCR SMS_CLIENT_CONFIG_MANAGER 6/14/2017 11:18:32 PM 3328 (0x0D00) ---> Deleting SMS Client Install Lock File '\WINDOWS7X64.testlab.com\admin$\SMSClientInstall.001' SMS_CLIENT_CONFIG_MANAGER 6/14/2017 11:18:32 PM 3328 (0x0D00) Execute query exec [sp_CP_SetLastErrorCode] 2097152003, 120 SMS_CLIENT_CONFIG… That way this is not of much use for others who search the forums. Output of the command glxinfo (if this is not installed, install the package glx-utils) A screenshot, if possible (if the system has crashed but the display on screen is something other than just blank, take a picture with a digital camera and attach that) Information as to whether or not other OpenGL applications are able to run without problems. I actually suspected so. After reading a couple of messages in Reddit, I have decided to give a try to Xorg's built-in generic modosetting driver, and told myself that why I have been using Intel's driver for all those years as I have a newer graphic card already. I'll leave this not-yet-SOLVED in case throwing that switch shuts down further replies (someone might want to comment...). Last edited by truebuilder (2011-11-10 04:12:10). Will followup with X status by Monday hopefully. This driver is not recommended for use unless you have a problem with the normal driver for your card, because it will perform very badly. I hope that this gives you the clues you were hoping for, Gusar. Scroll down to 827 - splashscreen. Done The following packages were automatically installed and are no longer required: accountsservice-ubuntu-schemas acl activity-log-manager aglfn apg appmenu-qt apt-config-icons-large apt-config-icons-large-hidpi apturl-common argyll argyll-ref bamfdaemon blender-data breeze-cursor-theme breeze-gtk-theme calculix-ccx catdoc cheese-common cinnamon-desktop-data cinnamon-l10n colord-data … Closing log file.xinit: giving upxinit: unable to connect to X server: Connection refusedxinit: server error. average user may be frightened at the thought of having to type in commands at a command-line interface (CLI It is easily done. At least that's what ArchWiki told me... And what if your Intel graphics is a little older than Sandy Bridge (I have a Nehalem-era CPU)? splashscreen splash screen install. Server terminated with error (1). Remove the file completely. vesa is an Xorg driver for generic VESA video cards. Please check that it did so. From your Arch log: Compare that with the code snippet I posted above from the Ubuntu log. Despite that, I think I got what I wanted: it seems one needs to explicitly specify mach64 on Arch, whereas this is not needed on Ubuntu. Thanks in advance. It is currently included for optional use in VESA’s Embedded DisplayPort (eDP) Standard v1.4, and MIPI’s DSI Specification v1.2, and is open for use in … But Ctrl+Alt+F7 took me ~back to the twilight zone. The name is irrelevant pretty much, it only matters that it has a .conf extension. -- Alan Turing---How to Ask Questions the Smart Way. vesa is an Xorg driver for generic VESA video cards. Are you sure you clicked 'Edit' on this post: https://bbs.archlinux.org/viewtopic.php … 3#p1011433 ? No, you shouldn't. So here are the same plus Xorg.0.log for a successful boot with Lubuntu Desktop 11.10 Oneiric Ocelot: (Lubuntu) dmesg(Lubuntu) lspci -k(Lubuntu) Xorg.0.log. And I'm about out of "weekend" anyway, on shift tomorrow through Sunday late, I'll be unable to do much experimentation. There's one more puzzle that I don't seem to yet understand. Last edited by Gusar (2011-11-10 01:18:56), To make it easier for others to search the forums (the main reason that I went into such detail was so that others might benefit), I've removed that [SOLVED] from the first message then changed the thread's subject line from, startx ---> (EE) Failed to load module "mach64" ... "vesa" ... "fbdev". I tried to install everything that Lubuntu had attempted LoadModule. $$$$$  Here are my relevant pacman commands: 41  pacman -Syy   42  pacman -Syu   46  pacman -S sudo   51  pacman -Syy   52  pacman -Syu   55  pacman -S alsa-utils   56  pacman -S alsa-plugins   72  pacman -S xorg-server xorg-xinit xorg-utils xorg-server-utils   73  pacman -S mesa   74  pacman -S mesa-demos   75  pacman -S xf86-video-ati   76  pacman -S xorg-twm xorg-xclock xterm   80  pacman -S dbus  126  history | grep pacman > /dos/pacman.txt. xf86-video-ati is too new for that old thing. I would have preferred logs when xf86-video-vesa is not installed. Time for a break; later I'll return to consider firefox, chromium, opera, and stellarium. From the ArchWiki entry for Mach64 I gathered that all I had to do was pacman -S xf86-video-mach64, and that's all I did. DSC is an open standard that was developed in liaison with the MIPI Alliance for general purpose display interface compression.