Arch i686 and RuneScape HD Issues
I know that I'll get yelled at by some people for wanting to play RuneScape, but let's forget about that for now.
I have xorg installed with the xf86-video-ati driver for my Radeon X850XT card, the driver seems to be working just fine with everything else.
My Desktop Environment is LXDE, with Openbox. I don't have any compositor enabled unless one is enabled by default.
The problem is, RuneScape software (standard) detail works fine but is a bit laggy (that is to be expected, with no hardware support), but as soon as I enable hardware (high) definition, I'm not sure what happens exactly, but it seems to be a sort-of crash for the xserver. The mouse moves but "jumps" across the screen as I move it. The desktop environment itself stops responding and freezes.
XORG version:
version number: 11.0
X.Org version: 1.6.3.901
JRE verison:
java version "1.6.0_16"
Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode
Firefox version:
Mozilla Firefox 3.5.3, Copyright (c) 1998 - 2009 mozilla.org
Can anyone provide assistance?
Much thanks!
Last edited by blakeman8192 (2009-09-19 20:50:48)
All I can say is, good luck. I can't even get it to work very stable (best I can do is make it work, but with random crashes every half hour or so), and I have an Nvidia card. With ATI, I don't really thing you'll be able to get it to work very easily...Does your card support fglrx? If so, try that.
Similar Messages
-
Hi!
I've noticed that there is a x86_64 project for arch at www.arch64.org
Why is that project separated from the normal i686?
The ftp hierarchy supports multiple architecture types:
ftp://ftp.archlinux.org/0.8/os/i686
There could be a i586 and a x86_64 as well. I think it has been introduced for that reason a couple of years ago, so why not use it.
Selection of architecture could be at /etc/rc.conf or /etc/pacman.conf
I know that i586 and x86_64 aren't as stable as i686 is. But I think theses projects could get more testers, because it's easier to install them, find packages, more mirrors are available and so on.
Regards,
Moritz
PS: I hope this discussion didn't happen before and I did not found it, but maybe this is the time to discuss it again! :-)Talk to syamajala or c14n. They can be found in IRC. c14n is busy as hell, but he maintains the system, syamajala is the guy that basically started and heads the project. If you can boot the sucker using directions from the wiki, you'll then be able to build and compile packages in much the same way as i686 users.
http://wiki.archlinux.org/index.php/Cur … velopement
http://wiki.archlinux.org/index.php/Arch64_Install_page
http://wiki.archlinux.org/index.php/Arch64_FAQ
Those pages may or may not be up to date. ;-)
HTH,
Dusty -
Share partitions between Arch i686 and Arch 64
As I have a new shiny Turion 64 laptop, I want to setup a dual boot Arch32/Arch64
So, I wonder :
:arrow: can the swap partition be shared between the two ?
:arrow: can the /home partition be shared without problem (I think of config files stored here : same versions of software ? no known binary-only files ?)
:arrow: what about /boot (same filenames ( = two partitions) ?)
:arrow: I have a local mirror : i686 takes ~4GB, how many for Arch64 ? (I plan to use testing, current and extra repos)
:arrow: any other caveat I didn't think of ?
I'm planning something like this :
hda1 ext2 /boot (32) 128M
hda2 ext2 /boot (64) 128M
hda3 swap (32+64) 1G
hda5 ext3 / (32) 12G
hda6 ext3 / (64) 12G
hda7 reiserfs /var (32) 4G
hda8 reiserfs /var (64) 4G
hda9 ext3 /home (32+64) ~sorry for hijacking this thread but i got a new pc & im about to install arch64 on it. what are the differences between em? i read some stuff here mostly conserning some codecs. can anyone sum the differences up?
Have a look here: http://wiki.archlinux.org/index.php/Arch64_FAQ
The forum contains a lot of in-depth info, also. Arch64 (or any other linux64) is not really for the faint-hearted, because there is inevitably techno-stuff involved. What I mean is that you can't just install and expect everything to be easy. The main points of interest for folks is that it is fa--->st and that it utilises the processor capabilities. There are, however, gaps.
================
Returning to running two arch64's, I have found that amarok gets seriously beeped. This is maybe because of its kde-based settings. Anyhow, I deleted ~/.kde/share/apps/amarok; and just let it sort itself out on starting up again.
Firefox crashes sometimes, too. -
[SOLVED]Arch Linux, and Windows 8.1 Dual Boot issue
Hi guys. I recently bought a new laptop, and decided to run Arch Linux and Windows 8.1. I installed Windows 8.1 first as recommended by the beginners guide, and then installed Arch Linux. I made sure UEFI was enabled in my BIOS, and made sure everything was on a GPT partition. The install itself went fine. My laptop loads grub, and Arch Linux shows up and boots, but there is no option to boot into Windows 8.1. The only way I can boot into Windows 8.1 is by accessing my motherboard, and choosing to launch the windows boot manager instead of the grub launcher. How can I get Windows 8.1 to show up in grub? Thanks in advance guys.
Last edited by Painguy (2014-08-20 20:19:37)Painguy wrote:
-----------Edit------------------
Yeah just ran this after installing os prober
grub-mkconfig -o /boot/grub/grub.cfg
and it works now. Sorry for the crazy posts guys. Thanks for the suggestions and help.
Yeah I'm sure I'm doing something wrong lol. I did not install OS-Prober. I think that's where the issue is. I'm missing the menu entry in grub.cfg right? Do I just run os prober or do I have to manually edit grub.cfg.
If that's not the case then here is what I did up until now. What I did was start with a blank SSD drive. I used cgdisk to make the disk use a GPT partitioning scheme. I installed windows 8.1 and checked in windows to make sure it boots into UEFI-GPT mode and it does. I then installed arch linux using the beginners guide. I made sure to use cgdisk to create any extra partitions, and installed GRUB to the efi partition that windows had created ( I did not format this partition ). I then finished the installation and rebooted, and Grub only shows arch linux. I don't think I'm dealing with anything MBR related. I made sure I used the GPT partitioning scheme....i think lol.
All you need to do is run os-prober then run grub-mkconfig. It should pick up Windows at that point. -
GDM and Gnome graphical issues with Nvidia card
Hi !
I want to install archlinux with cinnamon as desktop environment on the computer of a friend, but I have some issue with it, and especially with (I think) the graphic card, it's a Nvidia GeForce FX 5200LE.
I tried installing nvidia-173xx from the aur first. I installed gdm, but it's extremly slow, as a result that I can't log in (nevertheless the mouse is fluid..) the cpu is not so much used yet, and it's the same thing in the cinnamon session or the gnome session (I tried installing lightdm to log in which works fine). Moreover, in the session I've got some strange graphical things, such as some missing white pixels, or a blue window when I launch nautilus, ... (here are some screenshots : http://i49.tinypic.com/2efhm6s.png and a with a window : http://i46.tinypic.com/116m05k.png)
I tried to install the nouveau driver instead, and now gdm don't freeze, I can log in, but there is always these strange graphical issues.
Is the graphic card too old for gnome ? Or did I forget something ?
Thank you in advance for your help !! And sorry for my english ..
Here are some log with the nouveau driver :
- Xorg.log :
[ 9.026]
X.Org X Server 1.12.4
Release Date: 2012-08-27
[ 9.026] X Protocol Version 11, Revision 0
[ 9.026] Build Operating System: Linux 3.4.8-1-ARCH i686
[ 9.026] Current Operating System: Linux famille-workstation 3.5.3-1-ARCH #1 SMP PREEMPT Sun Aug 26 08:15:06 UTC 2012 i686
[ 9.026] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=83840f06-da6c-4558-a8ef-8ed779442ff3 ro quiet pci=nomsi
[ 9.026] Build Date: 27 August 2012 08:08:29AM
[ 9.026]
[ 9.026] Current version of pixman: 0.26.2
[ 9.026] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 9.026] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 9.027] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 5 13:26:01 2012
[ 9.053] (==) Using config file: "/etc/X11/xorg.conf"
[ 9.053] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 9.072] (==) No Layout section. Using the first Screen section.
[ 9.072] (==) No screen section available. Using defaults.
[ 9.072] (**) |-->Screen "Default Screen Section" (0)
[ 9.072] (**) | |-->Monitor "<default monitor>"
[ 9.074] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 9.074] (**) Option "AIGLX" "off"
[ 9.074] (==) Automatically adding devices
[ 9.074] (==) Automatically enabling devices
[ 9.127] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF/".
[ 9.127] Entry deleted from font path.
[ 9.128] (Run 'mkfontdir' on "/usr/share/fonts/OTF/").
[ 9.128] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/Type1/".
[ 9.128] Entry deleted from font path.
[ 9.128] (Run 'mkfontdir' on "/usr/share/fonts/Type1/").
[ 9.128] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 9.128] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 9.128] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 9.128] (II) Loader magic: 0x82225a0
[ 9.128] (II) Module ABI versions:
[ 9.128] X.Org ANSI C Emulation: 0.4
[ 9.128] X.Org Video Driver: 12.1
[ 9.128] X.Org XInput driver : 16.0
[ 9.128] X.Org Server Extension : 6.0
[ 9.129] (--) PCI:*(0:1:0:0) 10de:0323:107d:1334 rev 161, Mem @ 0xe0000000/16777216, 0xd8000000/134217728, BIOS @ 0x????????/131072
[ 9.129] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 9.129] (II) LoadModule: "extmod"
[ 9.145] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 9.156] (II) Module extmod: vendor="X.Org Foundation"
[ 9.156] compiled for 1.12.4, module version = 1.0.0
[ 9.156] Module class: X.Org Server Extension
[ 9.156] ABI class: X.Org Server Extension, version 6.0
[ 9.156] (II) Loading extension MIT-SCREEN-SAVER
[ 9.156] (II) Loading extension XFree86-VidModeExtension
[ 9.156] (II) Loading extension XFree86-DGA
[ 9.156] (II) Loading extension DPMS
[ 9.156] (II) Loading extension XVideo
[ 9.156] (II) Loading extension XVideo-MotionCompensation
[ 9.156] (II) Loading extension X-Resource
[ 9.156] (II) LoadModule: "dbe"
[ 9.157] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 9.157] (II) Module dbe: vendor="X.Org Foundation"
[ 9.157] compiled for 1.12.4, module version = 1.0.0
[ 9.157] Module class: X.Org Server Extension
[ 9.157] ABI class: X.Org Server Extension, version 6.0
[ 9.157] (II) Loading extension DOUBLE-BUFFER
[ 9.157] (II) LoadModule: "glx"
[ 9.157] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 9.164] (II) Module glx: vendor="X.Org Foundation"
[ 9.164] compiled for 1.12.4, module version = 1.0.0
[ 9.164] ABI class: X.Org Server Extension, version 6.0
[ 9.164] (**) AIGLX disabled
[ 9.165] (II) Loading extension GLX
[ 9.165] (II) LoadModule: "record"
[ 9.165] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 9.166] (II) Module record: vendor="X.Org Foundation"
[ 9.166] compiled for 1.12.4, module version = 1.13.0
[ 9.166] Module class: X.Org Server Extension
[ 9.166] ABI class: X.Org Server Extension, version 6.0
[ 9.166] (II) Loading extension RECORD
[ 9.166] (II) LoadModule: "dri"
[ 9.166] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 9.172] (II) Module dri: vendor="X.Org Foundation"
[ 9.172] compiled for 1.12.4, module version = 1.0.0
[ 9.172] ABI class: X.Org Server Extension, version 6.0
[ 9.172] (II) Loading extension XFree86-DRI
[ 9.172] (II) LoadModule: "dri2"
[ 9.172] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 9.173] (II) Module dri2: vendor="X.Org Foundation"
[ 9.173] compiled for 1.12.4, module version = 1.2.0
[ 9.173] ABI class: X.Org Server Extension, version 6.0
[ 9.173] (II) Loading extension DRI2
[ 9.173] (==) Matched nouveau as autoconfigured driver 0
[ 9.173] (==) Matched nvidia as autoconfigured driver 1
[ 9.173] (==) Matched nv as autoconfigured driver 2
[ 9.173] (==) Matched vesa as autoconfigured driver 3
[ 9.173] (==) Matched fbdev as autoconfigured driver 4
[ 9.173] (==) Assigned the driver to the xf86ConfigLayout
[ 9.173] (II) LoadModule: "nouveau"
[ 9.180] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 9.191] (II) Module nouveau: vendor="X.Org Foundation"
[ 9.191] compiled for 1.12.2, module version = 1.0.1
[ 9.191] Module class: X.Org Video Driver
[ 9.191] ABI class: X.Org Video Driver, version 12.0
[ 9.191] (II) LoadModule: "nvidia"
[ 9.191] (WW) Warning, couldn't open module nvidia
[ 9.191] (II) UnloadModule: "nvidia"
[ 9.191] (II) Unloading nvidia
[ 9.192] (EE) Failed to load module "nvidia" (module does not exist, 0)
[ 9.192] (II) LoadModule: "nv"
[ 9.192] (WW) Warning, couldn't open module nv
[ 9.192] (II) UnloadModule: "nv"
[ 9.192] (II) Unloading nv
[ 9.192] (EE) Failed to load module "nv" (module does not exist, 0)
[ 9.192] (II) LoadModule: "vesa"
[ 9.192] (WW) Warning, couldn't open module vesa
[ 9.192] (II) UnloadModule: "vesa"
[ 9.192] (II) Unloading vesa
[ 9.192] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 9.192] (II) LoadModule: "fbdev"
[ 9.193] (WW) Warning, couldn't open module fbdev
[ 9.193] (II) UnloadModule: "fbdev"
[ 9.193] (II) Unloading fbdev
[ 9.193] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 9.193] (II) NOUVEAU driver
[ 9.193] (II) NOUVEAU driver for NVIDIA chipset families :
[ 9.193] RIVA TNT (NV04)
[ 9.193] RIVA TNT2 (NV05)
[ 9.193] GeForce 256 (NV10)
[ 9.193] GeForce 2 (NV11, NV15)
[ 9.193] GeForce 4MX (NV17, NV18)
[ 9.193] GeForce 3 (NV20)
[ 9.193] GeForce 4Ti (NV25, NV28)
[ 9.193] GeForce FX (NV3x)
[ 9.193] GeForce 6 (NV4x)
[ 9.193] GeForce 7 (G7x)
[ 9.193] GeForce 8 (G8x)
[ 9.193] GeForce GTX 200 (NVA0)
[ 9.193] GeForce GTX 400 (NVC0)
[ 9.193] (++) using VT number 7
[ 9.196] drmOpenDevice: node name is /dev/dri/card0
[ 9.196] drmOpenDevice: open result is 7, (OK)
[ 9.196] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
[ 9.196] drmOpenDevice: node name is /dev/dri/card0
[ 9.196] drmOpenDevice: open result is 7, (OK)
[ 9.196] drmOpenByBusid: drmOpenMinor returns 7
[ 9.196] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
[ 9.196] (II) [drm] nouveau interface version: 1.0.0
[ 9.196] (II) Loading sub module "dri"
[ 9.196] (II) LoadModule: "dri"
[ 9.197] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 9.197] (II) Module dri: vendor="X.Org Foundation"
[ 9.197] compiled for 1.12.4, module version = 1.0.0
[ 9.197] ABI class: X.Org Server Extension, version 6.0
[ 9.197] (II) NOUVEAU(0): Loaded DRI module
[ 9.197] drmOpenDevice: node name is /dev/dri/card0
[ 9.197] drmOpenDevice: open result is 8, (OK)
[ 9.197] drmOpenDevice: node name is /dev/dri/card0
[ 9.197] drmOpenDevice: open result is 8, (OK)
[ 9.197] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
[ 9.197] drmOpenDevice: node name is /dev/dri/card0
[ 9.197] drmOpenDevice: open result is 8, (OK)
[ 9.197] drmOpenByBusid: drmOpenMinor returns 8
[ 9.197] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
[ 9.197] (II) [drm] DRM interface version 1.4
[ 9.197] (II) [drm] DRM open master succeeded.
[ 9.197] (--) NOUVEAU(0): Chipset: "NVIDIA NV34"
[ 9.197] (II) NOUVEAU(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 9.197] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
[ 9.197] (==) NOUVEAU(0): RGB weight 888
[ 9.197] (==) NOUVEAU(0): Default visual is TrueColor
[ 9.197] (==) NOUVEAU(0): Using HW cursor
[ 9.197] (==) NOUVEAU(0): GLX sync to VBlank disabled.
[ 9.197] (==) NOUVEAU(0): Page flipping enabled
[ 9.197] (==) NOUVEAU(0): Swap limit set to 2 [Max allowed 2]
[ 9.227] (II) NOUVEAU(0): Output VGA-1 has no monitor section
[ 9.280] (II) NOUVEAU(0): Output TV-1 has no monitor section
[ 9.309] (II) NOUVEAU(0): EDID for output VGA-1
[ 9.309] (II) NOUVEAU(0): Manufacturer: SAM Model: 1b Serial#: 1195913527
[ 9.309] (II) NOUVEAU(0): Year: 2003 Week: 16
[ 9.309] (II) NOUVEAU(0): EDID Version: 1.3
[ 9.309] (II) NOUVEAU(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
[ 9.309] (II) NOUVEAU(0): Sync: Separate Composite SyncOnGreenSerration on. V.Sync Pulse req. if CompSync or SyncOnGreen
[ 9.309] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 34 vert.: 27
[ 9.309] (II) NOUVEAU(0): Gamma: 2.40
[ 9.309] (II) NOUVEAU(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
[ 9.309] (II) NOUVEAU(0): First detailed timing is preferred mode
[ 9.309] (II) NOUVEAU(0): redX: 0.634 redY: 0.354 greenX: 0.304 greenY: 0.581
[ 9.309] (II) NOUVEAU(0): blueX: 0.143 blueY: 0.102 whiteX: 0.318 whiteY: 0.339
[ 9.309] (II) NOUVEAU(0): Supported established timings:
[ 9.309] (II) NOUVEAU(0): 720x400@70Hz
[ 9.309] (II) NOUVEAU(0): 640x480@60Hz
[ 9.309] (II) NOUVEAU(0): 640x480@67Hz
[ 9.309] (II) NOUVEAU(0): 640x480@72Hz
[ 9.310] (II) NOUVEAU(0): 640x480@75Hz
[ 9.310] (II) NOUVEAU(0): 800x600@56Hz
[ 9.310] (II) NOUVEAU(0): 800x600@60Hz
[ 9.310] (II) NOUVEAU(0): 800x600@72Hz
[ 9.310] (II) NOUVEAU(0): 800x600@75Hz
[ 9.310] (II) NOUVEAU(0): 832x624@75Hz
[ 9.310] (II) NOUVEAU(0): 1024x768@60Hz
[ 9.310] (II) NOUVEAU(0): 1024x768@70Hz
[ 9.310] (II) NOUVEAU(0): 1024x768@75Hz
[ 9.310] (II) NOUVEAU(0): 1280x1024@75Hz
[ 9.310] (II) NOUVEAU(0): 1152x864@75Hz
[ 9.310] (II) NOUVEAU(0): Manufacturer's mask: 0
[ 9.310] (II) NOUVEAU(0): Supported standard timings:
[ 9.310] (II) NOUVEAU(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 9.310] (II) NOUVEAU(0): #1: hsize: 1024 vsize 768 refresh: 60 vid: 16481
[ 9.310] (II) NOUVEAU(0): #2: hsize: 800 vsize 600 refresh: 60 vid: 16453
[ 9.310] (II) NOUVEAU(0): #3: hsize: 640 vsize 480 refresh: 60 vid: 16433
[ 9.310] (II) NOUVEAU(0): Supported detailed timing:
[ 9.310] (II) NOUVEAU(0): clock: 108.0 MHz Image Size: 338 x 270 mm
[ 9.310] (II) NOUVEAU(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
[ 9.310] (II) NOUVEAU(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
[ 9.310] (II) NOUVEAU(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 81 kHz, PixClock max 145 MHz
[ 9.310] (II) NOUVEAU(0): Monitor name: SyncMaster
[ 9.310] (II) NOUVEAU(0): Serial No: HJGW403719
[ 9.310] (II) NOUVEAU(0): EDID (in hex):
[ 9.310] (II) NOUVEAU(0): 00ffffffffffff004c2d1b0037314847
[ 9.310] (II) NOUVEAU(0): 100d01030f221b8cea6f8ba25a4d9424
[ 9.310] (II) NOUVEAU(0): 1a5156bfef8081806140454031400101
[ 9.310] (II) NOUVEAU(0): 010101010101302a009851002a403070
[ 9.310] (II) NOUVEAU(0): 1300520e1100001e000000fd00384c1e
[ 9.310] (II) NOUVEAU(0): 510e000a202020202020000000fc0053
[ 9.310] (II) NOUVEAU(0): 796e634d61737465720a2020000000ff
[ 9.310] (II) NOUVEAU(0): 00484a47573430333731390a20200057
[ 9.310] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
[ 9.310] (II) NOUVEAU(0): Using EDID range info for horizontal sync
[ 9.310] (II) NOUVEAU(0): Using EDID range info for vertical refresh
[ 9.310] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 9.310] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
[ 9.310] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 9.310] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 9.310] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 9.310] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
[ 9.310] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 9.310] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 9.311] (II) NOUVEAU(0): Printing probed modes for output VGA-1
[ 9.311] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
[ 9.311] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "1280x800"x74.9 106.50 1280 1360 1488 1696 800 803 809 838 -hsync +vsync (62.8 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "1280x768"x74.9 102.25 1280 1360 1488 1696 768 771 778 805 +hsync -vsync (60.3 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "1024x576"x60.0 46.97 1024 1064 1168 1312 576 577 580 597 -hsync +vsync (35.8 kHz)
[ 9.311] (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
[ 9.311] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 9.363] (II) NOUVEAU(0): EDID for output TV-1
[ 9.363] (II) NOUVEAU(0): Output VGA-1 connected
[ 9.363] (II) NOUVEAU(0): Output TV-1 disconnected
[ 9.363] (II) NOUVEAU(0): Using exact sizes for initial modes
[ 9.363] (II) NOUVEAU(0): Output VGA-1 using initial mode 1280x1024
[ 9.363] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 9.363] (--) NOUVEAU(0): Virtual size is 1280x1024 (pitch 0)
[ 9.363] (**) NOUVEAU(0): Driver mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
[ 9.363] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
[ 9.363] (**) NOUVEAU(0): Driver mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
[ 9.363] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 9.363] (**) NOUVEAU(0): Driver mode "1280x960": 108.0 MHz (scaled from 0.0 MHz), 60.0 kHz, 60.0 Hz
[ 9.363] (II) NOUVEAU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 9.363] (**) NOUVEAU(0): Driver mode "1280x800": 106.5 MHz (scaled from 0.0 MHz), 62.8 kHz, 74.9 Hz
[ 9.363] (II) NOUVEAU(0): Modeline "1280x800"x74.9 106.50 1280 1360 1488 1696 800 803 809 838 -hsync +vsync (62.8 kHz e)
[ 9.363] (**) NOUVEAU(0): Driver mode "1280x800": 83.5 MHz (scaled from 0.0 MHz), 49.7 kHz, 59.8 Hz
[ 9.363] (II) NOUVEAU(0): Modeline "1280x800"x59.8 83.50 1280 1352 1480 1680 800 803 809 831 +hsync -vsync (49.7 kHz e)
[ 9.363] (**) NOUVEAU(0): Driver mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz
[ 9.363] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 9.363] (**) NOUVEAU(0): Driver mode "1280x768": 102.2 MHz (scaled from 0.0 MHz), 60.3 kHz, 74.9 Hz
[ 9.363] (II) NOUVEAU(0): Modeline "1280x768"x74.9 102.25 1280 1360 1488 1696 768 771 778 805 +hsync -vsync (60.3 kHz e)
[ 9.363] (**) NOUVEAU(0): Driver mode "1280x768": 79.5 MHz (scaled from 0.0 MHz), 47.8 kHz, 59.9 Hz
[ 9.363] (II) NOUVEAU(0): Modeline "1280x768"x59.9 79.50 1280 1344 1472 1664 768 771 778 798 -hsync +vsync (47.8 kHz e)
[ 9.363] (**) NOUVEAU(0): Driver mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.1 kHz, 75.1 Hz
[ 9.363] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 9.363] (**) NOUVEAU(0): Driver mode "1024x768": 75.0 MHz (scaled from 0.0 MHz), 56.5 kHz, 70.1 Hz
[ 9.363] (II) NOUVEAU(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 9.363] (**) NOUVEAU(0): Driver mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
[ 9.364] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 9.364] (**) NOUVEAU(0): Mode "1024x576": 47.0 MHz (scaled from 0.0 MHz), 35.8 kHz, 60.0 Hz
[ 9.364] (II) NOUVEAU(0): Modeline "1024x576"x60.0 46.97 1024 1064 1168 1312 576 577 580 597 -hsync +vsync (35.8 kHz)
[ 9.364] (**) NOUVEAU(0): Driver mode "832x624": 57.3 MHz (scaled from 0.0 MHz), 49.7 kHz, 74.6 Hz
[ 9.364] (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 9.364] (**) NOUVEAU(0): Driver mode "800x600": 50.0 MHz (scaled from 0.0 MHz), 48.1 kHz, 72.2 Hz
[ 9.364] (II) NOUVEAU(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 9.364] (**) NOUVEAU(0): Driver mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
[ 9.364] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 9.364] (**) NOUVEAU(0): Driver mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
[ 9.364] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 9.364] (**) NOUVEAU(0): Driver mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz
[ 9.364] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 9.364] (**) NOUVEAU(0): Driver mode "848x480": 33.8 MHz (scaled from 0.0 MHz), 31.0 kHz, 60.0 Hz
[ 9.364] (II) NOUVEAU(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e)
[ 9.364] (**) NOUVEAU(0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 72.8 Hz
[ 9.364] (II) NOUVEAU(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
[ 9.364] (**) NOUVEAU(0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
[ 9.364] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 9.364] (**) NOUVEAU(0): Driver mode "640x480": 30.2 MHz (scaled from 0.0 MHz), 35.0 kHz, 66.7 Hz
[ 9.364] (II) NOUVEAU(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 9.364] (**) NOUVEAU(0): Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
[ 9.364] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 9.364] (**) NOUVEAU(0): Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 59.9 Hz
[ 9.364] (II) NOUVEAU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 489 492 525 -hsync -vsync (31.5 kHz e)
[ 9.364] (**) NOUVEAU(0): Driver mode "720x400": 28.3 MHz (scaled from 0.0 MHz), 31.5 kHz, 70.1 Hz
[ 9.364] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 9.364] (**) NOUVEAU(0): Display dimensions: (340, 270) mm
[ 9.364] (**) NOUVEAU(0): DPI set to (95, 96)
[ 9.364] (II) Loading sub module "fb"
[ 9.364] (II) LoadModule: "fb"
[ 9.364] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 9.375] (II) Module fb: vendor="X.Org Foundation"
[ 9.375] compiled for 1.12.4, module version = 1.0.0
[ 9.375] ABI class: X.Org ANSI C Emulation, version 0.4
[ 9.375] (II) Loading sub module "exa"
[ 9.375] (II) LoadModule: "exa"
[ 9.376] (II) Loading /usr/lib/xorg/modules/libexa.so
[ 9.380] (II) Module exa: vendor="X.Org Foundation"
[ 9.380] compiled for 1.12.4, module version = 2.5.0
[ 9.380] ABI class: X.Org Video Driver, version 12.1
[ 9.380] (II) Loading sub module "shadowfb"
[ 9.380] (II) LoadModule: "shadowfb"
[ 9.380] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
[ 9.382] (II) Module shadowfb: vendor="X.Org Foundation"
[ 9.382] compiled for 1.12.4, module version = 1.0.0
[ 9.382] ABI class: X.Org ANSI C Emulation, version 0.4
[ 9.382] (--) Depth 24 pixmap format is 32 bpp
[ 9.382] (II) NOUVEAU(0): Opened GPU channel 1
[ 9.384] (II) NOUVEAU(0): [DRI2] Setup complete
[ 9.384] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
[ 9.384] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
[ 9.399] (II) EXA(0): Driver allocated offscreen pixmaps
[ 9.399] (II) EXA(0): Driver registered support for the following operations:
[ 9.399] (II) Solid
[ 9.399] (II) Copy
[ 9.399] (II) Composite (RENDER acceleration)
[ 9.399] (II) UploadToScreen
[ 9.399] (II) DownloadFromScreen
[ 9.399] (==) NOUVEAU(0): Backing store disabled
[ 9.399] (==) NOUVEAU(0): Silken mouse enabled
[ 9.399] (II) NOUVEAU(0): [XvMC] Associated with NV30 texture adapter.
[ 9.399] (II) NOUVEAU(0): [XvMC] Extension initialized.
[ 9.399] (==) NOUVEAU(0): DPMS enabled
[ 9.399] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 9.399] (--) RandR disabled
[ 9.399] (II) Initializing built-in extension Generic Event Extension
[ 9.399] (II) Initializing built-in extension SHAPE
[ 9.399] (II) Initializing built-in extension MIT-SHM
[ 9.400] (II) Initializing built-in extension XInputExtension
[ 9.400] (II) Initializing built-in extension XTEST
[ 9.400] (II) Initializing built-in extension BIG-REQUESTS
[ 9.400] (II) Initializing built-in extension SYNC
[ 9.400] (II) Initializing built-in extension XKEYBOARD
[ 9.400] (II) Initializing built-in extension XC-MISC
[ 9.400] (II) Initializing built-in extension SECURITY
[ 9.400] (II) Initializing built-in extension XINERAMA
[ 9.400] (II) Initializing built-in extension XFIXES
[ 9.400] (II) Initializing built-in extension RENDER
[ 9.400] (II) Initializing built-in extension RANDR
[ 9.400] (II) Initializing built-in extension COMPOSITE
[ 9.400] (II) Initializing built-in extension DAMAGE
[ 9.800] (II) AIGLX: Loaded and initialized swrast
[ 9.800] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 9.807] (II) NOUVEAU(0): NVEnterVT is called.
[ 9.807] (II) NOUVEAU(0): Setting screen physical size to 338 x 270
[ 9.807] resize called 1280 1024
[ 10.066] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 10.066] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 10.066] (II) LoadModule: "evdev"
[ 10.066] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 10.075] (II) Module evdev: vendor="X.Org Foundation"
[ 10.075] compiled for 1.12.3.901, module version = 2.7.3
[ 10.075] Module class: X.Org XInput Driver
[ 10.075] ABI class: X.Org XInput driver, version 16.0
[ 10.075] (II) Using input driver 'evdev' for 'Power Button'
[ 10.076] (**) Power Button: always reports core events
[ 10.076] (**) evdev: Power Button: Device: "/dev/input/event2"
[ 10.076] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 10.076] (--) evdev: Power Button: Found keys
[ 10.076] (II) evdev: Power Button: Configuring as keyboard
[ 10.076] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[ 10.076] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 10.076] (**) Option "xkb_rules" "evdev"
[ 10.076] (**) Option "xkb_model" "evdev"
[ 10.076] (**) Option "xkb_layout" "us"
[ 10.117] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 10.117] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 10.117] (II) Using input driver 'evdev' for 'Power Button'
[ 10.117] (**) Power Button: always reports core events
[ 10.117] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 10.118] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 10.118] (--) evdev: Power Button: Found keys
[ 10.118] (II) evdev: Power Button: Configuring as keyboard
[ 10.118] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1/event1"
[ 10.118] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 10.118] (**) Option "xkb_rules" "evdev"
[ 10.118] (**) Option "xkb_model" "evdev"
[ 10.118] (**) Option "xkb_layout" "us"
[ 10.118] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 10.118] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 10.118] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 10.119] (**) AT Translated Set 2 keyboard: always reports core events
[ 10.119] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 10.119] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 10.119] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 10.119] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 10.119] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 10.119] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 8)
[ 10.119] (**) Option "xkb_rules" "evdev"
[ 10.119] (**) Option "xkb_model" "evdev"
[ 10.119] (**) Option "xkb_layout" "us"
[ 10.120] (II) config/udev: Adding input device ImPS/2 Logitech Wheel Mouse (/dev/input/event4)
[ 10.120] (**) ImPS/2 Logitech Wheel Mouse: Applying InputClass "evdev pointer catchall"
[ 10.120] (II) Using input driver 'evdev' for 'ImPS/2 Logitech Wheel Mouse'
[ 10.120] (**) ImPS/2 Logitech Wheel Mouse: always reports core events
[ 10.120] (**) evdev: ImPS/2 Logitech Wheel Mouse: Device: "/dev/input/event4"
[ 10.120] (--) evdev: ImPS/2 Logitech Wheel Mouse: Vendor 0x2 Product 0x5
[ 10.120] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found 3 mouse buttons
[ 10.120] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found scroll wheel(s)
[ 10.120] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found relative axes
[ 10.120] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found x and y relative axes
[ 10.120] (II) evdev: ImPS/2 Logitech Wheel Mouse: Configuring as mouse
[ 10.120] (II) evdev: ImPS/2 Logitech Wheel Mouse: Adding scrollwheel support
[ 10.120] (**) evdev: ImPS/2 Logitech Wheel Mouse: YAxisMapping: buttons 4 and 5
[ 10.120] (**) evdev: ImPS/2 Logitech Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 10.120] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input4/event4"
[ 10.120] (II) XINPUT: Adding extended input device "ImPS/2 Logitech Wheel Mouse" (type: MOUSE, id 9)
[ 10.120] (II) evdev: ImPS/2 Logitech Wheel Mouse: initialized for relative axes.
[ 10.120] (**) ImPS/2 Logitech Wheel Mouse: (accel) keeping acceleration scheme 1
[ 10.120] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration profile 0
[ 10.120] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration factor: 2.000
[ 10.120] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration threshold: 4
[ 10.121] (II) config/udev: Adding input device ImPS/2 Logitech Wheel Mouse (/dev/input/mouse0)
[ 10.121] (II) No input driver specified, ignoring this device.
[ 10.121] (II) This device may have been added with another device file.
[ 10.121] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
[ 10.121] (II) No input driver specified, ignoring this device.
[ 10.121] (II) This device may have been added with another device file.
[ 10.174] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
[ 10.174] (II) NOUVEAU(0): Using hsync ranges from config file
[ 10.174] (II) NOUVEAU(0): Using vrefresh ranges from config file
[ 10.174] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 10.174] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
[ 10.174] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 10.174] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 10.174] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 10.174] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
[ 10.174] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 10.174] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 10.174] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 10.174] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 10.174] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 10.174] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 10.174] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 10.174] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 10.174] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 10.174] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 10.174] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 14.960] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
[ 14.960] (II) NOUVEAU(0): Using hsync ranges from config file
[ 14.960] (II) NOUVEAU(0): Using vrefresh ranges from config file
[ 14.960] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 14.960] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
[ 14.961] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 14.961] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 14.961] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 14.961] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
[ 14.961] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 14.961] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 14.961] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 14.961] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 14.961] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 14.961] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 14.961] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 14.961] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 14.961] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 14.961] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 14.961] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 84.256] (II) NOUVEAU(0): NVLeaveVT is called.
[ 111.559] (II) NOUVEAU(0): NVEnterVT is called.
[ 111.601] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
[ 111.601] (II) NOUVEAU(0): Using hsync ranges from config file
[ 111.601] (II) NOUVEAU(0): Using vrefresh ranges from config file
[ 111.601] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 111.601] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
[ 111.601] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 111.601] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 111.601] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 111.601] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
[ 111.601] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 111.601] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 111.602] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 111.602] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 111.602] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 111.602] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 111.602] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 111.602] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 111.602] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 111.602] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 111.602] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 119.891] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
[ 119.891] (II) NOUVEAU(0): Using hsync ranges from config file
[ 119.891] (II) NOUVEAU(0): Using vrefresh ranges from config file
[ 119.891] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 119.891] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
[ 119.891] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 119.891] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 119.891] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 119.891] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
[ 119.891] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 119.891] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 119.891] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 119.891] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 119.891] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 119.891] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 119.891] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 119.891] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 119.891] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 119.892] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 119.892] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 121.162] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
[ 121.162] (II) NOUVEAU(0): Using hsync ranges from config file
[ 121.162] (II) NOUVEAU(0): Using vrefresh ranges from config file
[ 121.162] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 121.162] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
[ 121.162] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 121.162] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 121.162] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 121.162] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
[ 121.162] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 121.162] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 121.162] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 121.162] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 121.162] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 121.162] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 121.162] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 121.162] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 121.162] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 121.163] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 121.163] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 122.743] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
[ 122.743] (II) NOUVEAU(0): Using hsync ranges from config file
[ 122.743] (II) NOUVEAU(0): Using vrefresh ranges from config file
[ 122.743] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 122.743] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
[ 122.743] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 122.743] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 122.743] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 122.743] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
[ 122.743] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 122.743] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 122.743] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 122.743] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 122.743] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 122.743] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 122.743] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 122.743] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 122.743] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 122.744] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 122.744] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 138.896] (II) NOUVEAU(0): NVLeaveVT is called.
[ 167.669] (II) NOUVEAU(0): NVEnterVT is called.
[ 167.720] (II) NOUVEAU(0): EDID vendor "SAM", prod id 27
[ 167.720] (II) NOUVEAU(0): Using hsync ranges from config file
[ 167.720] (II) NOUVEAU(0): Using vrefresh ranges from config file
[ 167.720] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 167.720] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
[ 167.720] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 167.720] (II) NOUVEAU(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 167.720] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 167.720] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
[ 167.720] (II) NOUVEAU(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 167.720] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 167.720] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 167.720] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 167.720] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 167.720] (II) NOUVEAU(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 167.720] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 167.720] (II) NOUVEAU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 167.720] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 167.720] (II) NOUVEAU(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 167.720] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 186.390] (II) NOUVEAU(0): NVLeaveVT is called.
- .xsession-errors in gnome session :
GNOME_KEYRING_CONTROL=/home/olivier/.cache/keyring-D3uSoF
GNOME_KEYRING_CONTROL=/home/olivier/.cache/keyring-D3uSoF
GPG_AGENT_INFO=/home/olivier/.cache/keyring-D3uSoF/gpg:0:1
GNOME_KEYRING_CONTROL=/home/olivier/.cache/keyring-D3uSoF
GPG_AGENT_INFO=/home/olivier/.cache/keyring-D3uSoF/gpg:0:1
SSH_AUTH_SOCK=/home/olivier/.cache/keyring-D3uSoF/ssh
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 55
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 56
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 59
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 58
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 55
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 56
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 59
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 58
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
Failed to play sound: File or data not found
** Message: applet now removed from the notification area
** Message: applet now embedded in the notification area
Avertissement du gestionnaire de fenêtres : CurrentTime used to choose focus window; focus window may not be correct.
Avertissement du gestionnaire de fenêtres : Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
(gnome-shell:700): folks-WARNING **: Failed to find primary PersonaStore with type ID 'eds' and ID 'system'.
Individuals will not be linked properly and creating new links between Personas will not work.
The configured primary PersonaStore's backend may not be installed. If you are unsure, check with your distribution.
(gnome-shell:700): GLib-GIO-WARNING **: Dropping signal ActiveSessionChanged of type (s) since the type from the expected interface is (o)
(gnome-settings-daemon:657): color-plugin-WARNING **: Done switch to new account, reload devices
(gnome-shell:700): GLib-GIO-WARNING **: Dropping signal ActiveSessionChanged of type (s) since the type from the expected interface is (o)
(gnome-shell:700): GLib-GIO-WARNING **: Dropping signal ActiveSessionChanged of type (s) since the type from the expected interface is (o)
Last edited by Jejel59 (2012-09-06 11:34:53)I'm no expert on reading the xsession errors, but I had all sorts of problems running gnome3 with my machine of the same vintage. Cinamon is based on gnome3. I switched to Mate which is a re-packaging of the old gnome2 along with Compiz for the window manager and all works well.
I strongly suspect that they are using the newer OpenGL 4 API. The Nvidia FX5200 is stuck at OpenGL 2.1. -
Gnome AND KDE won't start (i686 and 64bit)
http://bbs.archlinux.org/viewtopic.php?id=71991
I've had a rough time these past few days and I posted earlier on Arch64 forums thinking it was just architecture thing but as it turns out after my reinstallation of Arch to 64 bit again (First i686, then 64, then i686 and now 64 again) I finally got it to work but this time Gnome is a pain in the ass, it didn't work with KDE either but KDE never gave me an error or gave me an option to failsafe into the OS.
$HOME/.xsession-errors:
/etc/gdm/Xsession: Beginning session setup...
/etc/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session
gnome-session[3898]: WARNING: Could not connect to ConsoleKit: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
gnome-session[3898]: CRITICAL: dbus_g_connection_get_connection: assertion `gconnection' failed
process 3898: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3298.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
gnome-session[3898]: ******************* START ********************************
gnome-session[3898]: Frame 0: gnome-session [0x4192d7]
gnome-session[3898]: Frame 1: gnome-session [0x419426]
gnome-session[3898]: Frame 2: /lib/libc.so.6 [0x7f3cbc493ec0]
gnome-session[3898]: Frame 3: /lib/libc.so.6(gsignal+0x35) [0x7f3cbc493e45]
gnome-session[3898]: Frame 4: /lib/libc.so.6(abort+0x19a) [0x7f3cbc4952aa]
gnome-session[3898]: Frame 5: /usr/lib/libdbus-1.so.3 [0x7f3cbef6ab95]
gnome-session[3898]: Frame 6: /usr/lib/libdbus-1.so.3 [0x7f3cbef66a5d]
gnome-session[3898]: Frame 7: /usr/lib/libdbus-1.so.3(dbus_connection_send_with_reply_and_block+0x198) [0x7f3cbef50a88]
gnome-session[3898]: Frame 8: gnome-session [0x41203c]
gnome-session[3898]: Frame 9: gnome-session [0x412140]
gnome-session[3898]: Frame 10: gnome-session [0x41a5b0]
gnome-session[3898]: Frame 11: gnome-session [0x41aa8f]
gnome-session[3898]: Frame 12: /lib/libc.so.6(__libc_start_main+0xfd) [0x7f3cbc48055d]
gnome-session[3898]: Frame 13: gnome-session [0x40aef9]
gnome-session[3898]: ******************* END **********************************
/var/log/gdm/:0.log.3
X.Org X Server 1.6.1
Release Date: 2009-4-14
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.29-ARCH x86_64
Current Operating System: Linux deuklin 2.6.29-ARCH #1 SMP PREEMPT Sat May 9 14:09:36 CEST 2009 x86_64
Build Date: 15 April 2009 11:01:49AM
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, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue May 12 08:55:10 2009
(==) Using config file: "/etc/X11/xorg.conf"
dlopen: libdrm.so.2: cannot open shared object file: No such file or directory
(EE) Failed to load /usr/lib/xorg/modules/extensions//libdri.so
(EE) Failed to load module "dri" (loader failed, 7)
(EE) Failed to load module "freetype" (module does not exist, 0)
dlopen: libdrm.so.2: cannot open shared object file: No such file or directory
(EE) Failed to load /usr/lib/xorg/modules/extensions//libdri2.so
(EE) Failed to load module "dri2" (loader failed, 7)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
Just a point here is that I've had the exact same software installed the same day that I reinstalled and this error did not occur but after formatting my partition with ext4 and testing Arch64 it did. But it did with 32bit as well, there were tons of errors.
I've read about this ConsoleKit error in a few posts here but nothing seems to indicate a fix or anything and since I'm using Gnome now I didn't find anything on it just about KDE.
I can safely use "Failsafe Gnome" without startup scripts but I want it to work without any problems and I don't know if the "dri" thing is related to the ConsoleKit thing with GDM.
I installed it via FTP and had the latest updates as soon as I've installed, so if this is just something that is happening to me right now or alot of other people, please give us hints or anything that could solve this?
If you read my Arch64 thread you know that stuff stopped working for me, first the network (it turns out I had to boot Windows inbetween installing Arch for my network even to start and that sounds ridicilous if it depends on another operating system starting the device because in Windows the network card was turned on with a green light wherein Arch after installing it didn't. I reformated my partitions and changed it again, installed Windows again and tried it out and then installed Arch. It worked, and then I mixed around with KDE and after five minutes of using "startx" (the only thing working) I decided to reinstall with Gnome, but then the network didn't start again (tried booting about ten times) and then I just thought "Let's start windows first so it turns on" and when I just booted Windows and immiedatiely restarted it and booted with the Arch CD, network was available again. Strange? Or is this a period of instability for Arch?
But when I got my network to start, appearantly Keyboard and mouse wasn't working because Xorg forgot to install the drivers when I installed the full group of Xorg so I had to fix that and now it's giving me this error.Without a dbus socket, dbus probably isn't running. It's supposed to be started automatically when a program needs it. Check to see that it is installed and running:
pacman -Q dbus
pgrep -l dbus
Dbus won't run without hal, so hal should be in:
tail /etc/rc.conf
Are any of your partitions full?
df -h
For the other error, it looks like libdrm isn't installed, but I don't think you need it if you're running the nvidia driver.
Your xorg.conf and Xorg.0.log would also be useful. Also check dmesg for errors.
And see if /etc/rc.d/dbus is marked executable.
Last edited by fphillips (2009-05-12 18:27:41) -
Can Kerberos Server 5 be run on Arch Linux and Windows Clients use it?
Hi There,
I was wondering (before I invested a great deal of time into it) if I could run a kerberos 5 server on my Arch box and get a Windows machine on my network to use it to log into Windows? (eg. like a domain)
I've tried doing the same with Samba 4 (which I bet will be massive when it's eventually released!), but it doesn't really work too great at the moment and wondered if I could achieve what I wanted with Kerberos 5?
I have DNS & DHCP already running and Samba 3 for network shares; but I really want the whole SSO package for all my machines. I know it's possible for my Mac Laptop to use Kerberos, but just not sure about Windows (XP/2003/7)
Thanks,
TomI will post something when I get the last issues ironed out. There is very little information about this anywhere let-alone on Arch wiki! It has been a real struggle, shame Samba 4 isn't more stable/working.
Stuff like M$ just decided to disable DES encryption by default in Windows 7. You know; the usual c**p-ness! -
RFC: Queries about Arch culture and community
Good day everyone,
This is a request for opinions from the Arch community, especially the Arch developers, Trusted Users, and long time users. I am writing a review about Arch Linux which I hope to publish within the next month or so. Unlike most distro reviews, which are actually distro installation reviews, I have devoted a lot of space to The Arch Way, unique technical qualities of Arch, day to day use and maintenance of Arch, and the Arch community. In my view, the community of a distro is much more important than its installation process.
If I may, I would like to pose some questions about the Arch community. FWIW, I have been quietly participating in the Arch community myself for some months now, contributing material to the wiki. Anyway, please take a look at the queries below, and comment on any as you see fit.
Thank you,
Luke Seubert
1. Despite its modest size, Arch has a very enthusiastic community, as evidenced by its internationalization projects, derivative distros, 3rd party repositories, Arch schwag, active forums and wiki, etc. Is this statement true or false, and if Arch does have an especially enthusiastic community, why?
2. Arch is deeply conservative, refusing to deviate from core principles. Still, within these bounds, Arch permits a wide array of innovation. Are these statements true or false, and why? If true, what are the pros and cons of such conservatism? If false, in what way has Arch deviated from its core principles or resisted innovation?
3. The Arch community is fairly harmonious, with little bickering, flamewars, forks or threats to fork, etc. Is this statement true or false, and why? (I have my own theory on the why of this one, and the answer in brief is... dogfood.)
4. How good or bad a job is Arch doing in cultivating new Trusted Users and Arch developers? Does it have a formal mentoring process? It seems the most direct path to TU status is to put together packages in AUR, and eventually have them voted into Community based upon quality and popularity. However, at some point, virtually all of the popular packages will already be in Community or Extra. How does an AUR uploader become a Trusted User then?
5. Hypothetical Scenario:
The Chakra Project successfully completes in alpha, beta, and release candidate Live CD testing, and releases its Live CD - version 1.0 - with the GUI easy Tribe installer, to wide acclaim - DistroWatch even raves about it. Suddenly, there are lots of new Arch users, who never went through the traditional Arch install process, who never "paid their Arch dues", and who are not nearly as clueful because they never RTFW. They are flooding IRC and webforums with really, uh, "basic" questions, and suggesting/demanding new features. How does the Arch community handle this abrupt change in its culture? Has it dealt with such culture shocks before?
6. If only you too could lift cars over your head, would you be more cool, less cool, or as cool as Phrakture, and why? What if you could only lift cars over your head after eating a can of spinach and slamming a six pack of Red Bull? Then how cool/not cool would you be by comparison?
Last edited by lseubert (2009-08-08 13:45:07)Allan wrote:
Here are my opinions on these questions and do not necessarily reflect other Arch devs...
1. True. I believe part of the enthusiastic community comes from the fact that Arch requires you to set up your system for yourself. So people become very proud of their achievement of getting their system setup exactly as they like it.
This is an excellent point. There is a nice sense of pride that comes from tweaking your Arch install to just the way you like it. And it is an involved process requiring some modicum of skill.
Also, people have always been encouraged to contribute fixes or start projects to fulfill areas they see lacking. Seeing your work become used by many others is always a good feeling.
Yeah, I have noted this in my rough draft. Arch has amazingly low barriers to entry. Sign up for an AUR account, which is quick and automatic, and get to work. Your status and authority is derived from a roughly consensual meritocracy, as opposed to a hierarchical, bureaucratic process full of gatekeepers, aka potential gateclosers, like most distros.
This simplicity extends to our package manager, which I believe is a major factor in making the AUR as popular as it is. (Note that while pacman is developed primarily by Arch users, it aims not to be tied to any distro).
Allan, could you clarify this comment? How does pacman make AUR popular? While I use pacman to access binaries from core, extra, and community; I use yaourt to handle PKGBUILDs from AUR. I don't quite follow you on this one.
But as always, the principles guiding Arch do get bent when it is sensible to do so. It was always said we don't split packages like many other distros, but we do some splitting these days (e.g. gcc-libs, KDE). We now include info pages and other docs.
Both of which are good moves. A system should have documentation built in, for those occasions when internet access is down. And I might actually take a look at KDE 4 once again, now that I wouldn't have to download a pile of unwanted packages.
3. There are flame-wars every so often... The last one that was probably quite obvious to many was changing rules governing the community repo (requiring votes or 1% usage as defined by pkgstats) and the move to using the official db-scripts (which may be seen as making the TUs less independent).
That is a flamewar that I missed. How does Arch resolve difficult issues? There is no Constitution that I could find, nor any formal governing structure. Is it as simple as lengthy debate, and then Dred Overlord Phrakture decrees?
I have never heard of a treat to fork the distro or components of it. I guess that is because of the attitude of show us a working implementation of a good idea and it will possibly become official.
Well, there aren't forks, but there are a lot of derivative distros, some of them with very different goals. And there are a lot of 3rd party repositories out there, outside of AUR. I wouldn't call that forking, but it is, I guess, extending. I think such experimentation is a good thing - really good ideas might be developed outside of even AUR, and eventually brought back into the Arch ecosystem. I believe some of Xyne's packages got started that way, yes?
Here is an interesting factoid I came up with in my research:
Packages Per Maintainer Ratio - how many packages on average does a maintainer support?
For Debian, the P/M Ratio is 28
When you add up all the Arch Devs and TUs, and divide out the packages in core, extra, and community, the Arch P/M Ratio is 67.
Arch devs seem quite impressive, until you recall that they mostly maintain one version of each package and for only two architectures, whereas Debian devs support 11 architectures for 5 versions - experimental, unstable, testing, current stable, and old stable. (Ugh - is that brutal or what?)
Seen in that light, one has to admire the very hardworking Debian devs, and wonder a bit about those Arch dev slackers. Yet another T-shirt idea! Change the first idea so it now reads, "I'm a slacker Arch developer, and I eat my own dogfood!" -
Arch 64bit and 32bit games under wine
Hi there,
I am using an x86_64bit version of arch linux and have tried to use Civilization IV and Warcraft III with wine. But i have no usable Framerates. I have tried a lot of issues from Google Searches and from this forum but i cannot handle this problem. My first idea was, that my drivers are not installed correctly. But programs like glxinfo and glxgears says that there is hardware rendering enabled and compiz also works fine. After some researches today i think to have a new idea for my problem.
First i need to say, that i have an Thinkpad T400 with onborad graphics Intel HD4500 or so on. On Ubuntu with wine there were no problems in using Civ IV and Warcraft III, but under Arch Linux i cannot get it to work correctly. The Ubuntu was also an 64bit version.
Is it possible that wine need 32bit libaries for the graphics driver because of the 32bit games? I have only installed the normal pacman packages for my system, which only compile the drivers for 64bit. If this can fix fix the problem. How can I install 32bit and 64 bit drivers on one system?
I am relativly new to Arch Linux, so pls tell me the right commands if you need mor informations. And thank you for your issues.Psikon wrote:Is it possible that wine need 32bit libaries for the graphics driver because of the 32bit games? I have only installed the normal pacman packages for my system, which only compile the drivers for 64bit. If this can fix fix the problem. How can I install 32bit and 64 bit drivers on one system?
This is almost definitely the problem. First, add the new [multilib] repo (see the news page for how to do this). Then run pacman -Syu lib32-intel-dri (assuming you are using the 64-bit intel-dri. otherwise you may have to build something from the AUR). -
[SOLVED] (Arch)Linux and Intel Core 2 Quad Q8200 ??
hey everybody,
i just bought a new pc, a core 2 quad Q8200 and i have problems to get it work - even with other distros. I instert the install discs, i get the first screen where i can select Boot Live CD blabla, then i just see its unpacking the kernel and after that i just get cryptic errors. then it stops.
On arch i tried the ftp-i686 and ftp-x86_64 isos, both with the same result. i even tried other distributions. GRML: the same. Debian Installer: the same again. (just that the screen stays black on the other dirstros and i see nothing else).
could anyboy help me, please ? i think i used the correct isos, didnt i?
greets chris
Last edited by dude83 (2009-04-01 11:56:06)well, it's definitely not the processors fault, i have q8200 running without problems - even overclocked:
$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz
stepping : 7
cpu MHz : 2800.185
cache size : 2048 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm
bogomips : 5602.71
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
what exactly is the error message? -
RMAN BACKUPS AND ARCHIVED LOG ISSUES
제품 : RMAN
작성날짜 : 2004-02-17
RMAN BACKUPS AND ARCHIVED LOG ISSUES
=====================================
Scenario #1:
1)RMAN이 모든 archived log들을 삭제할 때 실패하는 경우.
database는 두 개의 archive destination에 archive file을 생성한다.
다음과 같은 스크립트를 수행하여 백업후에 archived redo logfile을 삭제한다.
run {
allocate channel c1 type 'sbt_tape';
backup database;
backup archivelog all delete input;
Archived redo logfile 삭제 유무를 확인하기 위해 CROSSCHECK 수행시 다음과
같은 메시지가 발생함.
RMAN> change archivelog all crosscheck;
RMAN-03022: compiling command: change
RMAN-06158: validation succeeded for archived log
RMAN-08514: archivelog filename=
/oracle/arch/dest2/arcr_1_964.arc recid=19 stamp=368726072
2) 원인분석
이 문제는 에러가 아니다. RMAN은 여러 개의 arhive directory중 하나의
directoy안에 있는 archived file들만 삭제한다. 그래서 나머지 directory안의
archived log file들은 삭제되지 않고 남게 되는 것이다.
3) 해결책
RMAN이 강제로 모든 directory안의 archived log file들을 삭제하게 하기 위해서는
여러 개의 채널을 할당하여 각 채널이 각 archive destination안의 archived file을
백업하고 삭제하도록 해야 한다.
이것은 아래와 같이 구현될 수 있다.
run {
allocate channel t1 type 'sbt_tape';
allocate channel t2 type 'sbt_tape';
backup
archivelog like '/oracle/arch/dest1/%' channel t1 delete input
archivelog like '/oracle/arch/dest2/%' channel t2 delete input;
Scenario #2:
1)RMAN이 archived log를 찾을 수 없어 백업이 실패하는 경우.
이 시나리오에서 database를 incremental backup한다고 가정한다.
이 경우 RMAN은 recover시 archived redo log대신에 incremental backup을 사용할
수 있기 때문에 백업 후 모든 archived redo log를 삭제하기 위해 OS utility를 사용한다.
그러나 다음 번 backup시 다음과 같은 Error를 만나게 된다.
RMAN-6089: archive log NAME not found or out of sync with catalog
2) 원인분석
이 문제는 OS 명령을 사용하여 archived log를 삭제하였을 경우 발생한다. 이때 RMAN은
archived log가 삭제되었다는 것을 알지 못한다. RMAN-6089는 RMAN이 OS 명령에 의해
삭제된 archived log가 여전히 존재하다고 생각하고 백업하려고 시도하였을 때 발생하게 된다.
3) 해결책
가장 쉬운 해결책은 archived log를 백업할 때 DELETE INPUT option을 사용하는 것이다.
예를 들면
run {
allocate channel c1 type 'sbt_tape';
backup archivelog all delete input;
두 번째로 가장 쉬운 해결책은 OS utility를 사용하여 archived log를 삭제한 후에
다음과 같은 명령어를 RMAN prompt상에서 수행하는 것이다.
RMAN>allocate channel for maintenance type disk;
RMAN>change archivelog all crosscheck;
Oracle 8.0:
RMAN> change archivelog '/disk/path/archivelog_name' validate;
Oracle 8i:
RMAN> change archivelog all crosscheck ;
Oracle 9i:
RMAN> crosscheck archivelog all ;
catalog의 COMPATIBLE 파라미터가 8.1.5이하로 설정되어 있으면 RMAN은 찾을 수 없는
모든 archived log의 status를 "DELETED" 로 셋팅한다. 만약에 COMPATIBLE이 8.1.6이상으로
설정되어 있으면 RMAN은 Repository에서 record를 삭제한다.Very strange, I issue following command in RMAN on both primary and standby machine, but it they don't delete the 1_55_758646076.dbf, I find in v$archived_log, this "/home/oracle/app/oracle/dataguard/1_55_758646076.dbf" had already been applied.
RMAN> connect target /
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
old RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
new RMAN configuration parameters are successfully stored
RMAN>
---------------------------------------------------------------------------------- -
X86 libs on x64 using --arch=i686 installes to /usr/lib
Hi. I have x64, and need some x86 libs.
I thought running "pacman -S --arch=i686 somelib" would just install files in /usr/lib32, but it seems it installs directly to /usr/lib.
Of course, this is creating quite some problems as programs picks up 32-bit libraries.
I'm afraid to restart my computes until I've fixed this.
Any tips on how I can revert this?
And how I can make "--arch=i686" install to /usr/lib32 by default? (or any other way to handle this)slint wrote:The arch flag is useful when you want to install something on a different system (for example a chroot). Normally you would handle this by installing the lib from multilib, but you can also create a dedicated 32 bit arch chroot.
Oh..
slint wrote:If you didn't overwrite any libraries from other packages (shouldn't if you haven't used -f) a simple pacman -R should be engough I guess.
I didn't use "-f", but it seems pacman overwrote symlinks anyway.
With -R, it complains that other packages relies on this, even though those packages relies on the x64 packages.
"pacman -R -v --debug --arch=i686 somelib" doesn't give me confidence that it won't break my system if I drop checking for dependencies - not a single place are i686 referenced even though I specified --arch with -R. -
Gmail/Exchange email and calendar syncing issues
I have wiped my email accounts several times and entered in my data in the various ways as shown through the forums but my email accounts do no sync properly whether it is manual or active synced.
I read my emails in my gmail and my Microsoft exchange account and will delete or file them away but then when I check my accounts on my desktop, they are not synced as I've done so on my phone. I've also noticed that my calendars are not synced correctly either.
Could someone help me understand why and how these issues can be fixed? I'm in meetings for most of the day so I rely on my phone to keep me mobile. Was this a bad purchase?!?!Hi JadeyMU,
How do you have your Microsoft Exchange account configured on your BlackBerry Z10? Are you using ActiveSync, BlackBerry Enterprise Server (BES), IMAP or POP?
Thanks.
-CptS
Come follow your BlackBerry Technical Team on twitter! @BlackBerryHelp
Be sure to click Kudos! for those who have helped you.Click Solution? for posts that have solved your issue(s)! -
My experience with Apple TV and HDMI/HDCP issues
I am convinced that it is the software update to 4.2.2 from 4.2.1 that is causing this issue. All forms of applications only worked once for me and then it reverted back to HDCP issues. I read several postings everywhere including plenty at Apple's forum and AVS where people were very frustrated with this HDCP issues. Anyways, here is what I did before taking it back to Apple store....I bought AUVIO high speed cables from Radio Shack which is rated very high and tried that and I still got HDCP issues when using NetFlix or AirPlay from iPad. Youtube from Apple TV always worked well without HDCP complaints.
I packed everything back and took it to Apple Store (you can return without re-stocking fee up to 14 days from the day of purchase). After 14 days, you cannot even return it and you can ONLY fix it. I waited for a Technician. They heard my complaints but didn't refute any of it (possibly because they have had numerous complaints on this product). It took 5 minutes inside for them to test and see similar issues with the box that I had. So, they have swapped it for a new box. Before I left the store, I checked the settings including software version and Audio/Video settings in the Apple TV that is connected at the store. I found three main differences none of which the Apple customer service staff agreed could be the reason for my problems (surprise!!)
1. The software update from the shelf and the one they were using was NOT updated to 4.2.2 (it was still running 4.2.1)
2. Because of the software update, the Audio/Video setting for HDMI had the options to toggle between Auto, RGBy, RGBhi & RGBlo bandwidth. I believe this was in place to make the HDMI interface output as component with higher or lower bandwidth but the newer update will ONLY give you the Auto option (!!!)
3. They had this directly Ethernet wired and not through Wireless network and were recieving the all the full bar strength signals. On the box that I returned, eventhough I have 18 Mbps speed at the house (any given time of the day), the Network speed test was taking a long time. Moreover, after the Apple TV network test, it doesn't spit out the outcome of the tests (a BIG bummer and useless for testing).
Anyways, I took the new box and hooked it up directly to my SONY BRAVIA XBR3 TV to one of the HDMI ports, disabled the feature to send or recieve data to Apple directly and did NOT update the software. It worked fine and have tested all of the options. From what I have read so far (I have only spent 30 hours of my weekend on this when Apple product hookups are supposed to take 5 minutes ONLY), there is NO guarantee that it will work continuously as people have had things work on them for 6 months and then suddenly have the HDCP issues.
Will wait to see....if it continues to work....I figured it out. Had to go to general settings on the main screen and restart. Synch of audio is much better.
-
i have a serious (and bizarre!) issue with my novation impulse (Although i've tried it with two other keyboards and i still have the same problem) and its compatibility with mainstage 3.
the problem is best explained on the following one - page thread:
https://discussions.apple.com/thread/3951518?start=0&tstart=0
(Clearly i'm not alone in this problem, although i think i figured out what's going wrong a little more than he did...read on!)
his solution, to put mainstage in jump mode, is very unsatisfactory to me, as it bounces all of a sudden to drastically different settings.
basically, my analysis is that my controller is NOT receiving MIDI date from mainstage. in other words, mainstage knows what my controller is doing, but my controller doens't know what mainstage is doing.
let's say i turn the knob all the way to the right ... 127...and the virtual fader goes to the right like it's supposed to.
now...next...let's say i change to a different patch, where that same VIRTUAL fader is not at the max clockwise position..maybe it's only at 1pm. now when i turn the physical knob to the RIGHT, the midi data is still at 127 on the controller! it didn't "reset" to sync up with the new level (say 80 or so) setting on the new patch. so i can't increase that new setting of 80 by continuing to turn the knob to the right. i have to turn it all the way to zero,...and then continue PAST zero until the controller thinks that IT is at 0...at that point the controller and mainstage are in agreement, and things work fine....so bascially, the keyboard thinks the level is at max...but mainstage thinks the level is at 1pm.
i am using Logic 9, and i have a macbook pro 2.9 Ghz I7 with 8 gigs of memory and OS X 10.8.4Hi Josh,
Thanks for taking the time to contact us here a Novation for technical support. Lets continue to correspond via email so we can get your issue resolved.
Thanks.
Mike Towns
Maybe you are looking for
-
New hard drive - dont want to lose my webpage
Recently had to replace hard drive - lost everything - if you're reading this, pause 1 minute and back up all your pics and videos. Anyway, my webpage is still on .mac, but no info on iweb. Is there way to download from .mac back to iweb? I am worrie
-
ICloud accounts (mine and my wife) seem to have merged
I upgraded my phone, and gave my wife the hand-me-down iPhone 5S. But under my iCloud settings, the old phone 5S (and the iPhone 5 prior, even) still show up as being signed in under my iCloud. Now it seems that the two iCloud accounts have become co
-
LUMIA 800 - Clock running slow!
Hi there, I have a bizarre problem with my Lumia 800 running on Optus - the clock runs slow! I have had to set the clock multiple times since I got it, and within about a week of setting it each time the clock is several minutes behind time. **bleep*
-
hi there, here is a question i have but first i want to apologise for my writting im still learning english ok here it is, hoping that some one who can backup his/her answer read this if every time i use png results in small file size WHY do i want t
-
Notification- code group defaulting
I customized a notification and every time I want to assign task code group and task code to that notification. Is it possible to assign/bring only required Task Folder to that notification, so I dont have to select task code one by one every time.