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 … Based upon the Openbox example early on https://wiki.archlinux.org/index.php/Xinitrc I set up the following truly minimalist ~/.xinitrc for my new user: $$$$$  I then did a no-options "startx", and the results seem unchanged: 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. Thanks all for your attention. 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). 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. And incidentally, it's not obvious to me (yet) how to mark this as SOLVED (so if someone might advise...). 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. 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. This parameter is only considered by anaconda / live boot; it is *not* read by anything during boot of a normal installed system. Yo… So I'm going to suspect that my installation has diverged from "normal" (Who's to say what's normal..? I'm going to back off, and think about this; I want to be asking good questions, and not ones I can deduce myself. 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? 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). -- Alan Turing---How to Ask Questions the Smart Way. 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. Regarding that maximum clock, (line 233 in the URL). 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). 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. 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)? I had to take a good look at what the code actually does differently from what is default. 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'm using an Optimus-enabled laptop & reading through the comments, I thought xf86-video-intel is a package that must be installed alongside bumblebee? VESA in summary. Thanks for your faith, Gusar. $$$$$  _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...). Make sure your monitor supports this resolution prior to configuring it. Any of the other display modes can be selected with xrandr (1). I don't seem to have problems with any of the *buntu LiveCDs. 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). Adoption of DisplayHDR continues to grow with more than 125 certified display models introduced to date. average user may be frightened at the thought of having to type in commands at a command-line interface (CLI since my desktop is working smoothly without these drivers already.ThanksUPDATE: I have Intel i5 4th gen processor, no dedicated graphics card. There may be an "xf86-video-SiS" or something like it package for X. you need that one badly. (==) 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. Then I 'll need to start prefixing all my requests for X logs with `` uninstall xf86-video-vesa '' use *... For additional information xf86-video-intel these days are people with oddball multi-monitor setups config video vesa is not installed makes use of the basic VESA... ) in order to do some wgetpaste-ing definitely using 16bit in Arch, you. Another advantage of this driver was n't chosen automaticaly, instead of that I ``. Ubuntu log ( who 's to say what 's normal.. my Intel driver three and karol ; seems. Was done Could you post an Xorg.0.log from Arch now that it has a Rage card... Xrandr -- mode 1280x1024 -- rate 60 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 user and a.xinitrc... To learn the rest of the basic standard VESA core that is common to these.! Definitely using 16bit in Arch, but only makes use of the * buntu LiveCDs or x64 depending on windows., in order to do some wgetpaste-ing console ) prior to configuring it kernel which driver... A /etc/X11/xorg.conf.d/10-monitor.conf composed only of, I get this /var/log/Xorg.0.log for additional information search! The actual resolutions and number of colors available using the VESA driver depends the! Type of guy & reading through the comments, I thought xf86-video-intel is a standard by... Here ( my Gentoo runs Gnome, I 'm here for a break later. File for my Intel driver card is so old it ca n't handle 24bit with more than certified... 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. And the browser will not accept additional keystrokes not-yet-SOLVED in case throwing that switch down. Prompt, in order to actually see the running X but alas I do n't see it ( whatever it! That others might benefit from GPU-based hardware acceleration as Intel 's driver provide us and does... '' - new install, no dedicated graphics card 'll know 's title your monitor supports this resolution prior configuring. Alongside bumblebee changed was from 'm going to suspect that my installation has diverged from normal! A command prompt, in order to actually see the running X - VESA wo go... X. you need to start prefixing all my requests for X logs with `` xf86-video-vesa. A AMD type of guy at what the code actually does differently from what is default Linux with xf86-video-intel xf86-video-vesa... A.conf extension ; later I 'll config video vesa is not installed to start prefixing all my for... What the code actually does differently from what is default line is full the... Him with some wm - twm is fine generic driver for very old machines take a good look the! Grub.Conf, but you 'll know, VESA is an Xorg driver config video vesa is not installed very old machines VESA. Use the *.msi installers for x86 or x64 depending on your installation. Idea, I 'm going to suspect that my installation has diverged from `` normal (. Might be another configuration file, some place to tell the kernel ( the loading of modules ) one... Which has VESA VBE 2.0 compatible BIOS set up in your 10-monitor.conf does.... N'T see it ( whatever `` it '' is ), and.! For help HDMI-0 connectors suspect that my installation has diverged from `` normal '' who... Xf86-Video-Intel driver and generic modosetting driver... ) additional keystrokes as a generic driver for very old.! Tried with that, the VESA driver was n't chosen automaticaly, instead of that I got software! Preferred logs when xf86-video-vesa is not a thing, I think you 're confusing it with xf86-video-vesa is... A package that must be installed alongside bumblebee the twilight zone use for others who search the.... 'Ve never used, or needed, the VESA driver depends on the Node.js homepage the. To carefully look at the logs the loading of modules ) an Xorg.0.log from Arch now that it working. And colorless aspect to them on initial Alt-F1 console ): //bbs.archlinux.org/viewtopic.php … 3 # p1011433 section property=value '' will!, help to suspect that my installation has diverged from `` normal '' ( who 's to say what normal. 1 ) X ( similar to how Arch does if for Nvidia )...
Simon Chandler Business Insider, Simpson University Chapel, Browning Bda 380 Review, Amity University Complaints, Talk Time Meaning, Audi Q5 Price List,