ArchThis Forum is for the discussion of Arch Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So I installed, and upgraded Arch, set my gpm, wireless and hal modules, so long so good.
Wanted to install the Nvidia proprietary driver, and installed it, but when I startx, keyboard and mouse are no longer available, tried to install stuff that depends on mesa and dri, and this thing pops up...
Quote:
[root@iskandhar ~]# pacman -S gnuplot
resolving dependencies...
looking for inter-conflicts...
Total Download Size: 0.00 MB
Total Installed Size: 55.31 MB
Proceed with installation? [Y/n] y
checking package integrity...
(8/8) checking for file conflicts [#################################################################################################### #] 100%error: failed to commit transaction (conflicting files)
mesa: /usr/include/GL/gl.h exists in filesystem
mesa: /usr/include/GL/glext.h exists in filesystem
mesa: /usr/include/GL/glx.h exists in filesystem
mesa: /usr/include/GL/glxext.h exists in filesystem
Errors occurred, no packages were upgraded.
bash-3.1#
the xorg.conf created by nvidia driver was this one... :
Quote:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder58) Wed Dec 9 16:34:26 PST 2009
yet my /etc/rc.conf clearly states that hal should be loaded at startup, so why the heck are my keyboard and mouse not active when I startx... ? ( I have the default twm as my WM... although I have installed ratpoison, fluxbox, IceWM, wmii and ratpoison, will have to configure startx to load one of these, later, as soon as i can fix this issue... )
Quote:
#
# /etc/rc.conf - Main Configuration for Arch Linux
#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Asia/Japan"
KEYMAP="pt-latin1"
CONSOLEFONT="Agafari-16"
CONSOLEMAP=
USECOLOR="yes"
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=( !pcspkr !snd-pcsp )
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="iskandhar"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
#
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
#Static IP example
eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
#eth0="dhcp"
eth1="dhcp"
INTERFACES=(eth0 eth1)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng gpm network netfs crond)
BRGDS
Alex
EDIT : Found out hal is not there...
I had it there, is it removed when I make an upgrade... ??
That's what I did... Anyway... how do I fix this
mesa: /usr/include/GL/gl.h exists in filesystem
mesa: /usr/include/GL/glext.h exists in filesystem
mesa: /usr/include/GL/glx.h exists in filesystem
mesa: /usr/include/GL/glxext.h exists in filesystem
Errors occurred, no packages were upgraded.
thing...? Probably will have to reinstall Arch....
My HP desktop has a Standard US usb keyboard and a USB optical mouse with a wheel. Notice the comments about the ServerFlags section.
The Xorg server now uses HAL to autodetect devices and configures them on the fly. Until your HAL problem is resolved, I'd recommend the "AutoAddDevices" "off" option, at least temporarily. E.G. make a backup of your old xorg.conf file and fill in the items needed.
Code:
Section "InputDevice"
# Driver "kbd" will be disabled unless 'Option "AutoAddDevices" "off"'
# is set in "ServerFlags" section.
Identifier "Keyboard[0]"
Driver "kbd"
Option "Protocol" "Standard"
Option "XkbLayout" "us"
Option "XkbModel" "microsoftpro"
Option "XkbRules" "xfree86"
EndSection
Code:
Section "InputDevice"
# Driver "mouse" will be disabled unless 'Option "AutoAddDevices" "off"'
# is set in "ServerFlags" section.
Identifier "Mouse[1]"
Driver "mouse"
Option "Buttons" "7"
Option "Device" "/dev/input/mice"
Option "Name" "USB Optical Mouse"
Option "Protocol" "explorerps/2"
Option "Vendor" "Sysp"
Option "ZAxisMapping" "4 5"
EndSection
My desktop has an ATI card. My laptop has an nvidia card. I have gnuplot installed on my laptop, but I don't use the dri module. I do have Mesa installed I see. I don't know if the nvidia install has replaced the gl include files. I believe that it does. At least if you install it from the nvidia installer. (note: I'm using SuSE 11.2) You may need to uninstall GNU plot and rebuild it with different flags eliminating the dri dependency. AFAIK, it is incompatible with the nvidia driver.
I don't know it it will help, and I know we use different distro's. Here is the ./configure --help for my source Mesa package:
Code:
Usage: ./configure [OPTION]... [VAR=VALUE]...
To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE. See below for descriptions of some of the useful variables.
Defaults for the options are specified in brackets.
Configuration:
-h, --help display this help and exit
--help=short display options specific to this package
--help=recursive display the short help of all the included packages
-V, --version display version information and exit
-q, --quiet, --silent do not print `checking...' messages
--cache-file=FILE cache test results in FILE [disabled]
-C, --config-cache alias for `--cache-file=config.cache'
-n, --no-create do not create output files
--srcdir=DIR find the sources in DIR [configure dir or `..']
Installation directories:
--prefix=PREFIX install architecture-independent files in PREFIX
[/usr/local]
--exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
[PREFIX]
By default, `make install' will install all the files in
`/usr/local/bin', `/usr/local/lib' etc. You can specify
an installation prefix other than `/usr/local' using `--prefix',
for instance `--prefix=$HOME'.
For better control, use the options below.
Fine tuning of the installation directories:
--bindir=DIR user executables [EPREFIX/bin]
--sbindir=DIR system admin executables [EPREFIX/sbin]
--libexecdir=DIR program executables [EPREFIX/libexec]
--sysconfdir=DIR read-only single-machine data [PREFIX/etc]
--sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
--localstatedir=DIR modifiable single-machine data [PREFIX/var]
--libdir=DIR object code libraries [EPREFIX/lib]
--includedir=DIR C header files [PREFIX/include]
--oldincludedir=DIR C header files for non-gcc [/usr/include]
--datarootdir=DIR read-only arch.-independent data root [PREFIX/share]
--datadir=DIR read-only architecture-independent data [DATAROOTDIR]
--infodir=DIR info documentation [DATAROOTDIR/info]
--localedir=DIR locale-dependent data [DATAROOTDIR/locale]
--mandir=DIR man documentation [DATAROOTDIR/man]
--docdir=DIR documentation root [DATAROOTDIR/doc/mesa]
--htmldir=DIR html documentation [DOCDIR]
--dvidir=DIR dvi documentation [DOCDIR]
--pdfdir=DIR pdf documentation [DOCDIR]
--psdir=DIR ps documentation [DOCDIR]
X features:
--x-includes=DIR X include files are in DIR
--x-libraries=DIR X library files are in DIR
These options are only used when the X libraries cannot be found by the
pkg-config utility.
System types:
--build=BUILD configure for building on BUILD [guessed]
--host=HOST cross-compile to build programs to run on HOST [BUILD]
Optional Features:
--disable-option-checking ignore unrecognized --enable/--with options
--disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no)
--enable-FEATURE[=ARG] include FEATURE [ARG=yes]
--enable-32-bit build 32-bit libraries [default=auto]
--enable-64-bit build 64-bit libraries [default=auto]
--enable-static build static libraries [default=disabled]
--disable-shared build shared libraries [default=enabled]
--enable-debug use debug compiler flags and macros
[default=disabled]
--disable-asm disable assembly usage [default=enabled on supported
plaforms]
--disable-pic compile PIC objects [default=enabled for shared
builds on supported platforms]
--enable-selinux Build SELinux-aware Mesa [default=disabled]
--enable-xcb use XCB for GLX [default=disabled]
--enable-glx-tls enable TLS support in GLX [default=disabled]
--disable-driglx-direct enable direct rendering in GLX for DRI
[default=enabled]
--enable-gl-osmesa enable OSMesa on libGL [default=enabled for xlib
driver]
--disable-egl disable EGL library [default=enabled]
--disable-glu enable OpenGL Utility library [default=enabled]
--disable-glw enable Xt/Motif widget library [default=enabled]
--enable-motif use Motif widgets in GLw [default=disabled]
--disable-glut enable GLUT library [default=enabled if source
available]
--disable-gallium build gallium [default=enabled]
--disable-gallium-intel build gallium intel [default=enabled]
--enable-gallium-radeon build gallium radeon [default=disabled]
--enable-gallium-nouveau
build gallium nouveau [default=disabled]
Optional Packages:
--with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
--without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
--with-driver=DRIVER driver for Mesa: xlib,dri,osmesa [default=dri when
available, or xlib]
--with-demos[=DIRS...] optional comma delimited demo directories to build
[default=auto if source available]
--with-x use the X Window System
--with-dri-driverdir=DIR
directory for the DRI drivers [${libdir}/dri]
--with-dri-drivers[=DIRS...]
comma delimited DRI drivers list, e.g.
"swrast,i965,radeon" [default=auto]
--with-expat=DIR expat install directory
--with-osmesa-bits=BITS OSMesa channel bits and library name: 8, 16, 32
[default=8]
--with-state-trackers[=DIRS...]
comma delimited state_trackers list, e.g. "egl,glx"
[default=auto]
--with-xorg-driver-dir=DIR
Default xorg driver
directory[[default=${libdir}/xorg/modules/drivers]]
--with-max-width=N Maximum framebuffer width (4096)
--with-max-height=N Maximum framebuffer height (4096)
Some influential environment variables:
CC C compiler command
CFLAGS C compiler flags
LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
nonstandard directory <lib dir>
LIBS libraries to pass to the linker, e.g. -l<library>
CPPFLAGS C/C++/Objective C preprocessor flags, e.g. -I<include dir> if
you have headers in a nonstandard directory <include dir>
CPP C preprocessor
CXX C++ compiler command
CXXFLAGS C++ compiler flags
PKG_CONFIG path to pkg-config utility
EXTRA_LIB_PATH
Extra -L paths for the linker
X11_INCLUDES
Extra -I paths for X11 headers
OPT_FLAGS Additional optimization flags for the compiler. Default is to
use CFLAGS.
ARCH_FLAGS Additional architecture specific flags for the compiler. Default
is to use CFLAGS.
MKLIB_OPTIONS
Options for the Mesa library script, mklib
PIC_FLAGS compiler flags for PIC code
XMKMF Path to xmkmf, Makefile generator for X Window System
XLIBGL_CFLAGS
C compiler flags for XLIBGL, overriding pkg-config
XLIBGL_LIBS linker flags for XLIBGL, overriding pkg-config
LIBDRM_CFLAGS
C compiler flags for LIBDRM, overriding pkg-config
LIBDRM_LIBS linker flags for LIBDRM, overriding pkg-config
DRI2PROTO_CFLAGS
C compiler flags for DRI2PROTO, overriding pkg-config
DRI2PROTO_LIBS
linker flags for DRI2PROTO, overriding pkg-config
LIBDRM_RADEON_CFLAGS
C compiler flags for LIBDRM_RADEON, overriding pkg-config
LIBDRM_RADEON_LIBS
linker flags for LIBDRM_RADEON, overriding pkg-config
DRIGL_CFLAGS
C compiler flags for DRIGL, overriding pkg-config
DRIGL_LIBS linker flags for DRIGL, overriding pkg-config
XCB_CFLAGS C compiler flags for XCB, overriding pkg-config
XCB_LIBS linker flags for XCB, overriding pkg-config
EGL_CFLAGS C compiler flags for EGL, overriding pkg-config
EGL_LIBS linker flags for EGL, overriding pkg-config
GLW_CFLAGS C compiler flags for GLW, overriding pkg-config
GLW_LIBS linker flags for GLW, overriding pkg-config
GLUT_CFLAGS C compiler flags for GLUT, overriding pkg-config
GLUT_LIBS linker flags for GLUT, overriding pkg-config
Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.
See docs/autoconf.html for more details on the options for Mesa.
Report bugs to <https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa>.
Perhaps installing Mesa first and then running the nvidia-installer program to let it replace the headers and openGL files that are compatible would bring you better luck, but I'm just guessing here.
Relax. Archers never "re-install" their system. Never get upset/frustrated with Arch. It may seem intimidating. A difficult beast that can not be tamed easily! However if you try and learn about it,it's easy as pie.
For your first problem regarding keyboard,mouse,I see you have already solved your problem by daemonizing hal. No it shouldn't have been removed due to an upgrade! You may have inserted hal but never saved the rc.conf file after making changes.
As for mesa, when are you getting that error?
I don't visit LQ often these days, but I have subscribed to this topic. You can also email me if you want.
as a "baby Archer" i am, I have several questions:
1.) Why is pacman better than Yum or apt-get...?
I have seen how damn "lightning fast" it is... but... about the underlying philosophy of package management... don't i risk diving into a sort of dependency hell...?
2.) Does pacman dependency handling/update coexist with Arch "Slackbuilds", AUR, without breaking anything...?
I installed Arch w kernel 2.6.30-ARCH, configured wireless, started dhchpd, and ran pacman -Syu...
It upgraded to kernel 2.6.32-ARCH, and i rebooted. Obviously wireless was no longer supported, so i installed kernel headers, and rebuilt kernel object, ran depmod afoer placing the *ko in its place... back to business... .
This is Easy when the only thing you have to do is recompiling a kernel module, now go figure out recompiling a whole DVD of applications from source because glibc/gcc/kernel headers were upgraded... won't take me just one minute to do like with kernel module...
3.) Did all this in console. Ran pacman -U xorg, and Instead of following Archwiki to enable X, I installed the latest nvidia driver from nvidia, downloaded it from Nvidia with links...
...it compiled the kernel support, configured ( created ) xorg.conf... startx and here I land in twm... no probl... I have also installed IceWM, fluxbox, ratpoison, wmii... and I know how to create awesome .twmrc's...
Only, when I wanted to install stuff that depended on dri-mesa... running pacman -U gimp, or pacman -U octave, this thing popped out...
Quote:
mesa: /usr/include/GL/gl.h exists in filesystem
mesa: /usr/include/GL/glext.h exists in filesystem
mesa: /usr/include/GL/glx.h exists in filesystem
mesa: /usr/include/GL/glxext.h exists in filesystem
Errors occurred, no packages were upgraded.
Seems that Nvidia driver did something nasty....
How can I undo this...?
In order to have a frozen snapshot of Arch, I "wgot" [base], [community] and [extra]... for <x86_64> and <any>... this is my personal repo.
In case of a "worst case scenario", me having to reinstall Arch, and upgrading it offline, how can I use this to rebuild my system to the state it was in the day when I made the snapshot ?
Note that, everything I compile/build/install in this system will be coherent with this snapshot, in terms of kernel/glibc/gcc...
I can manage to rebuild a Slackware install fo a working state, all packages installed, in that "worst case scenario" in 20-30 mn... offline...
I have one slackware64-<current> DVD, as well as two other dvds with slackbuilds, slackware packages compiled from slackbuilds, and from source, with makepkg, and src2pkg... with these 3 DVDs I can rebuild everything.
Can I do this with Arch...?
Does it allow for a "post-apocalypse" deployement...?
I have seen how damn "lightning fast" it is... but... about the underlying philosophy of package management... don't i risk diving into a sort of dependency hell...?
I've never seen any crazy dependency issues crop up with pacman. It is certainly no more likely than with yum or apt.
Quote:
mesa: /usr/include/GL/gl.h exists in filesystem
mesa: /usr/include/GL/glext.h exists in filesystem
mesa: /usr/include/GL/glx.h exists in filesystem
mesa: /usr/include/GL/glxext.h exists in filesystem
Errors occurred, no packages were upgraded.
Pacman tends to be conservative about overwriting files. Not entirely sure why this sort of thing occasionally crops up, but if you use the force option it will overwrite these.
Code:
pacman -Sf mesa
Quote:
2.) Does pacman dependency handling/update coexist with Arch "Slackbuilds", AUR, without breaking anything...?
I installed Arch w kernel 2.6.30-ARCH, configured wireless, started dhchpd, and ran pacman -Syu...
Pacman does not handle user built packages or packages from the AUR. You can either do it manually yourself or use 3rd party tools like bauerbill or packer.
What are these customs programs you have so many of? Do they really not exist in the AUR? Probably the easiest method would be to create PKGBUILDS for them and whip up a quick script that will build and install them for you. Or host them on the AUR and use one of the AUR helpers.
What are these customs programs you have so many of? Do they really not exist in the AUR? Probably the easiest method would be to create PKGBUILDS for them and whip up a quick script that will build and install them for you. Or host them on the AUR and use one of the AUR helpers.
Custom built packages by me and other research associates :
OptiStruct ( general genetic algorithm framework for structural optimization )
FSi ( Coupled fluid flow-elastic deformation analysis )
MCpropagate ( coupled Neutronic monte carlo transport radiation hydrodynamic analysis )
Optimized Compilers
Intel C++/Fortran compilers/Math kernel libraries
General simulation codes for DACE ( design and analysis of computer experiments )
General simulation codes for Aircraft stability analysis ( Datcom like application )
3D modeller package
BrlCAD
Finite elements/Volumes meshers :
Tetgen
Netgen
Gmsh
general pre/Post processing environment
Salome Platform
Some of these exist in AUR or Arch Packages,
But for some of them I run "custom" versions compiled with icc/ifort ( optimized compilers of Intel ) like Code-Aster, Code saturne, Syrthes, GetDP, Adventure, Calculix, OptiSruct, MCPropagate...
Just my slackware package of Intel development tools takes 1 Gb ...
These are all big apps, that take a lot to compile... I like to have them pre-built and ready for install in my system ( I have slackbuilds,Slackware packages built with src2pkg or makepkg, source code for everything i sue in Slackware... its about 2 DVDs )
But some of them are pretty sensible to GlibC or kernel version ( Intel compilers for instance )
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.