A "Webdesign Linux" approach

Hi Arch folks!
I'm pretty new to arch. I did a couple of different installations, tried different desktops, window managers and all the stuff. I think I created a nice, working, all-purpose system now (using GNOME), but relating webdesign on that system I'm not satisfied at all.
It would be useful if the system and desktop were reduced to needs for webdesign.
Since some time I see more often people asking for the best webdesign applications, tools, widgets, gadgets, tools and linux-distributions which are best for webdesign.
But I don't think it's enough to just install the suggested software and use it within your existing system.
Now, the idea: As the most UI-Designers know, unnecessary stuff should be avoided, I think it would be easier and make webdesigners feel more comfortable when doing the work on a clean desktop.
@Webdesigners: Imagine you choose something like "Webdesign Arch" in the bootloader menu. Then you know, a working system will boot up which won't ask questions at all, autostarts needed stuff on bootup, a fast, sophisticated desktop will say hello and launchers can be found at the intuitvly expected, easy accessible place.
The targets:
1) a ready to use linux system
2) fast desktop, reduced to webdesign needs but ...
3) ... looking good, maybe some eye-candy like wallpaper, icons, themes and stuff which helps the webdesigner to get inspired
4) most needed tools ready to use: different browsers, editors, graphics tools, some note taking widgets for collecting ideas, working and configured LAMP, maybe some multimedia apps like xmms for listening to music while thinking, news-reader with some recommended feeds and blogs
5) at all: the webdesigner should feel comfortable on the desktop
The issues/questions at board users:
@ target 1) I do know how to setup up and install the system, but I don't really know about the system internals:
  - Are really all packages from the arch-base installation needed for this approach?
  - Howto get all the stuff on a CD - ready to install with a few clicks?
@target 2) The LnF-Thread (http://bbs.archlinux.org/viewtopic.php?t=18880) could be useful for choosing the packages and software, but I think XFCE is the best choice for this approach. Other suggestions and oppinions?
@target 3) Suggestions? There should not be too much eye-candy-stuff to keep the system small, but most used and community-favourite eye-candy-stuff should be included.
@target 4) Software as mentioned above, should be a selection of some experienced webdesigners in the arch-community
@target 5) Any suggestions to for this task?
So far the description of the idea.
Are there interested people for this approach? What's your oppinion about it? Could it really be useful? In general, what do you think about it?
If there are people who like the idea, then I don't want to make a big project about it. Just give the child a name, discuss the targets and suggestions, create the system and give it to the community.

To get it runnin' ... a list of packages which I think have to be included:
Browsers
There need to be different browsers/engines to test the pages, as you know the look different...
- Firefox representing the Gecko-engine
- Opera
- Internet Explorer: maybe a difficult challenge, and I don't like it cause for IE it's necessary to include wine...
Graphics
- GIMP or GIMP-Shop
- maybe Blender (I really often see it in recommendation-lists for webdesign with linux)
- xsane (scanning software), a must if you wanna use hand-drawn graphics
Other stuff
- XMMS: as I mentioned, an Audio-Player would be nice to help the designer to get inspired (sorry for my bad english, is it "get" inspired or "become" inspired or something different??)
- eye-candy stuff: nice, inspiring wallpapers, themes, mouse icons, icon-themes, gdm or other login manager themes
- PyPad: really easy and light editor for note taking or reading readmes of PHP-Scripts and all the stuff
What's left?
- Vector-Graphics software: Inkscape or, which I would prefer: XaraLX (see http://www.xaralx.org - any other suggestions?
- Source-Code-Editor: Geany (nice but no code-completion), Bluefish (no code-completion, syntax highlighting is buggy, generally slow and you'll come in troubles when dealing with long lines), Quanta (in my oppinnion a bit overloaded, tries to give the developer everything but not comfortable, and: it needs QT...)
- a simple picture viewer like the gnome standard viewer (don't know it's name)
- file browser: pcmanfm, tuxcommander, mucommander, rox ???
- something to manage network profiles, probably the simplest way is wifi-radar
- clipboard manager, i think there is a plugin for xfce (if "we" use xfce for this little project)
- FTP-client: maybe gftp or a filemanager with ftp-capabilities
- login manager: i think GDM would be the best solution if we are "GTK+-ed"
- any presentation software, something like powerpoint
- an organizer
- a note-taking tool
- brainstorming/mindmapping software
- RSS-reader
Configuration and Ressources
- launchers for the tools should be in place and easy accessible
- nice theme should be standard
- maybe include some short tutorials for things like power-managment (powernowd, cpufreq and the stuff) and for extending it with basic things which really should be users choice (IM, email-client)
- Ressource collection with useful links (tutorials, AJAX-libraries and stuff like this, ebooks, links to software like CMS, BulletinBoards, ...)
- RSS-reader configured with some recommended feeds (like A-List-Apart, and some others)
Any other suggestions? Would be nice if you post your choice, especially for the points in "What's left?" and "Configuration and Ressources"!

Similar Messages

  • Xorg crashes when Firefox loads a lot of images; Intel driver bug?

    For some time now I'm seeing a weird error. Basically, when I load a *lot* of images in Firefox, Xorg crashes completely. In Xorg logfile I can see the following error:
    [ 2993.177] (EE) intel(0): Failed to submit batch buffer, expect rendering corruption or even a frozen display: No space left on device.
    [ 2993.180]
    [ 2993.180] Backtrace:
    [ 2993.214] 0: /usr/bin/X (xorg_backtrace+0x49) [0x81b6bb9]
    [ 2993.214] 1: /usr/bin/X (0x8048000+0x172816) [0x81ba816]
    [ 2993.214] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb77b140c]
    [ 2993.214] 3: /lib/libc.so.6 (0xb7412000+0x12dd10) [0xb753fd10]
    [ 2993.214] 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb71dd000+0xe51c) [0xb71eb51c]
    [ 2993.214] 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb71dd000+0x105c4) [0xb71ed5c4]
    [ 2993.214] 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb71dd000+0x3248d) [0xb720f48d]
    [ 2993.214] 7: /usr/bin/X (0x8048000+0xfb844) [0x8143844]
    [ 2993.214] 8: /usr/bin/X (0x8048000+0x2b84f) [0x807384f]
    [ 2993.214] 9: /usr/bin/X (0x8048000+0x2f0ad) [0x80770ad]
    [ 2993.214] 10: /usr/bin/X (0x8048000+0x1ccd5) [0x8064cd5]
    [ 2993.214] 11: /lib/libc.so.6 (__libc_start_main+0xf5) [0xb742b3d5]
    [ 2993.214] 12: /usr/bin/X (0x8048000+0x1d019) [0x8065019]
    [ 2993.214]
    [ 2993.214] Bus error at address 0xb2f8a748
    [ 2993.214]
    Fatal server error:
    [ 2993.214] Caught signal 7 (Bus error). Server aborting
    I have an Intel GMA 945 and I'm using x586-video-intel and intel-dri.
    It is interesting to see that these crashes happen as soon as the total memory used by Linux approaches/reaches my physical memory size of 2 GB. I should note that I have an SSD - so I do not use swap. With total memory used I mean memory that programs use plus cached memory, so my memory isn't actually "full" since the kernel could just free some cached memory to accommodate the memory Firefox needs. But this is not what happens: as soon as all of the memory is used, Xorg crashes in this scenario. I can prolong the time of crash by manually freeing the cached memory before, but again, as soon as the memory that "free -m" reports as used approaches my physical limit of 2 GB, I get a crash.
    Note that this is not an OOM Killer issue. OOM Killer doesn't do anything (and it shouldn't: the cached memory is available to the system, after all).
    I'm willing to test out any suggestions. My guess is that there is a bug in the intel driver but I rather be sure beforehand.
    Last edited by Natanji (2012-04-30 06:38:45)

    I dont know if this is something related but here is my Xorg.0.log.old:
    See at the end the 'Bus error at address' error:
    [ 8.527]
    X.Org X Server 1.12.1
    Release Date: 2012-04-13
    [ 8.527] X Protocol Version 11, Revision 0
    [ 8.527] Build Operating System: Linux 3.3.2-1-ARCH x86_64
    [ 8.527] Current Operating System: Linux echelon 3.3.6-1-ARCH #1 SMP PREEMPT Sun May 13 10:52:32 CEST 2012 x86_64
    [ 8.527] Kernel command line: root=/dev/sda5 ro
    [ 8.527] Build Date: 15 April 2012 09:55:35AM
    [ 8.527]
    [ 8.527] Current version of pixman: 0.24.4
    [ 8.527] Before reporting problems, check [url]http://wiki.x.org[/url]
    to make sure that you have the latest version.
    [ 8.527] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 8.527] (==) Log file: "/var/log/Xorg.0.log", Time: Fri May 18 09:34:54 2012
    [ 8.626] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 8.652] (==) No Layout section. Using the first Screen section.
    [ 8.652] (==) No screen section available. Using defaults.
    [ 8.652] (**) |-->Screen "Default Screen Section" (0)
    [ 8.652] (**) | |-->Monitor "<default monitor>"
    [ 8.652] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 8.652] (==) Automatically adding devices
    [ 8.652] (==) Automatically enabling devices
    [ 8.721] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 8.721] Entry deleted from font path.
    [ 8.773] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 8.773] Entry deleted from font path.
    [ 8.773] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 8.799] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 8.799] Entry deleted from font path.
    [ 8.799] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 8.799] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    [ 8.799] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 8.799] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 8.800] (II) Loader magic: 0x7c5160
    [ 8.800] (II) Module ABI versions:
    [ 8.800] X.Org ANSI C Emulation: 0.4
    [ 8.800] X.Org Video Driver: 12.0
    [ 8.800] X.Org XInput driver : 16.0
    [ 8.800] X.Org Server Extension : 6.0
    [ 8.800] (--) PCI:*(0:1:0:0) 1002:7142:1462:3000 rev 0, Mem @ 0xe0000000/67108864, 0xe5000000/65536, I/O @ 0x00009000/256, BIOS @ 0x????????/131072
    [ 8.800] (--) PCI: (0:1:0:1) 1002:7162:1462:3001 rev 0, Mem @ 0xe5010000/65536
    [ 8.800] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 8.800] (II) LoadModule: "extmod"
    [ 8.868] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    [ 8.891] (II) Module extmod: vendor="X.Org Foundation"
    [ 8.891] compiled for 1.12.1, module version = 1.0.0
    [ 8.891] Module class: X.Org Server Extension
    [ 8.891] ABI class: X.Org Server Extension, version 6.0
    [ 8.891] (II) Loading extension MIT-SCREEN-SAVER
    [ 8.891] (II) Loading extension XFree86-VidModeExtension
    [ 8.891] (II) Loading extension XFree86-DGA
    [ 8.891] (II) Loading extension DPMS
    [ 8.891] (II) Loading extension XVideo
    [ 8.891] (II) Loading extension XVideo-MotionCompensation
    [ 8.891] (II) Loading extension X-Resource
    [ 8.891] (II) LoadModule: "dbe"
    [ 8.892] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    [ 8.913] (II) Module dbe: vendor="X.Org Foundation"
    [ 8.913] compiled for 1.12.1, module version = 1.0.0
    [ 8.913] Module class: X.Org Server Extension
    [ 8.913] ABI class: X.Org Server Extension, version 6.0
    [ 8.913] (II) Loading extension DOUBLE-BUFFER
    [ 8.913] (II) LoadModule: "glx"
    [ 8.913] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 8.940] (II) Module glx: vendor="X.Org Foundation"
    [ 8.942] compiled for 1.12.1, module version = 1.0.0
    [ 8.943] ABI class: X.Org Server Extension, version 6.0
    [ 8.943] (==) AIGLX enabled
    [ 8.943] (II) Loading extension GLX
    [ 8.970] (II) LoadModule: "record"
    [ 8.970] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 9.003] (II) Module record: vendor="X.Org Foundation"
    [ 9.003] compiled for 1.12.1, module version = 1.13.0
    [ 9.003] Module class: X.Org Server Extension
    [ 9.003] ABI class: X.Org Server Extension, version 6.0
    [ 9.003] (II) Loading extension RECORD
    [ 9.003] (II) LoadModule: "dri"
    [ 9.003] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 9.038] (II) Module dri: vendor="X.Org Foundation"
    [ 9.038] compiled for 1.12.1, module version = 1.0.0
    [ 9.038] ABI class: X.Org Server Extension, version 6.0
    [ 9.038] (II) Loading extension XFree86-DRI
    [ 9.038] (II) LoadModule: "dri2"
    [ 9.038] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 9.058] (II) Module dri2: vendor="X.Org Foundation"
    [ 9.058] compiled for 1.12.1, module version = 1.2.0
    [ 9.058] ABI class: X.Org Server Extension, version 6.0
    [ 9.058] (II) Loading extension DRI2
    [ 9.058] (==) Matched ati as autoconfigured driver 0
    [ 9.058] (==) Matched vesa as autoconfigured driver 1
    [ 9.058] (==) Matched fbdev as autoconfigured driver 2
    [ 9.058] (==) Assigned the driver to the xf86ConfigLayout
    [ 9.058] (II) LoadModule: "ati"
    [ 9.087] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
    [ 9.091] (II) Module ati: vendor="X.Org Foundation"
    [ 9.091] compiled for 1.12.1, module version = 6.14.4
    [ 9.091] Module class: X.Org Video Driver
    [ 9.091] ABI class: X.Org Video Driver, version 12.0
    [ 9.091] (II) LoadModule: "radeon"
    [ 9.091] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
    [ 9.197] (II) Module radeon: vendor="X.Org Foundation"
    [ 9.218] compiled for 1.12.1, module version = 6.14.4
    [ 9.218] Module class: X.Org Video Driver
    [ 9.218] ABI class: X.Org Video Driver, version 12.0
    [ 9.231] (II) LoadModule: "vesa"
    [ 9.231] (WW) Warning, couldn't open module vesa
    [ 9.231] (II) UnloadModule: "vesa"
    [ 9.231] (II) Unloading vesa
    [ 9.231] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 9.231] (II) LoadModule: "fbdev"
    [ 9.231] (WW) Warning, couldn't open module fbdev
    [ 9.231] (II) UnloadModule: "fbdev"
    [ 9.231] (II) Unloading fbdev
    [ 9.231] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 9.231] (II) RADEON: Driver for ATI Radeon chipsets:
    ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
    ATI Radeon Mobility X300 (M24) 3152 (PCIE),
    ATI FireGL M24 GL 3154 (PCIE), ATI FireMV 2400 3155 (PCI),
    ATI Radeon X600 (RV380) 3E50 (PCIE),
    ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon IGP320 (A3) 4136,
    ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon 9500 AD (AGP),
    ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP),
    ATI FireGL Z1 AG (AGP), ATI Radeon 9800SE AH (AGP),
    ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP),
    ATI FireGL X2 AK (AGP), ATI Radeon 9600 AP (AGP),
    ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP),
    ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP), ATI Radeon 9650,
    ATI FireGL RV360 AV (AGP), ATI Radeon 7000 IGP (A4+) 4237,
    ATI Radeon 8500 AIW BB (AGP), ATI Radeon IGP320M (U1) 4336,
    ATI Radeon IGP330M/340M/350M (U2) 4337,
    ATI Radeon Mobility 7000 IGP 4437, ATI Radeon 9000/PRO If (AGP/PCI),
    ATI Radeon 9000 Ig (AGP/PCI), ATI Radeon X800 (R420) JH (AGP),
    ATI Radeon X800PRO (R420) JI (AGP),
    ATI Radeon X800SE (R420) JJ (AGP), ATI Radeon X800 (R420) JK (AGP),
    ATI Radeon X800 (R420) JL (AGP), ATI FireGL X3 (R420) JM (AGP),
    ATI Radeon Mobility 9800 (M18) JN (AGP),
    ATI Radeon X800 SE (R420) (AGP), ATI Radeon X800XT (R420) JP (AGP),
    ATI Radeon X800 VE (R420) JT (AGP), ATI Radeon X850 (R480) (AGP),
    ATI Radeon X850 XT (R480) (AGP), ATI Radeon X850 SE (R480) (AGP),
    ATI Radeon X850 PRO (R480) (AGP), ATI Radeon X850 XT PE (R480) (AGP),
    ATI Radeon Mobility M7 LW (AGP),
    ATI Mobility FireGL 7800 M7 LX (AGP),
    ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP),
    ATI FireGL Mobility 9000 (M9) Ld (AGP),
    ATI Radeon Mobility 9000 (M9) Lf (AGP),
    ATI Radeon Mobility 9000 (M9) Lg (AGP), ATI FireMV 2400 PCI,
    ATI Radeon 9700 Pro ND (AGP), ATI Radeon 9700/9500Pro NE (AGP),
    ATI Radeon 9600TX NF (AGP), ATI FireGL X1 NG (AGP),
    ATI Radeon 9800PRO NH (AGP), ATI Radeon 9800 NI (AGP),
    ATI FireGL X2 NK (AGP), ATI Radeon 9800XT NJ (AGP),
    ATI Radeon Mobility 9600/9700 (M10/M11) NP (AGP),
    ATI Radeon Mobility 9600 (M10) NQ (AGP),
    ATI Radeon Mobility 9600 (M11) NR (AGP),
    ATI Radeon Mobility 9600 (M10) NS (AGP),
    ATI FireGL Mobility T2 (M10) NT (AGP),
    ATI FireGL Mobility T2e (M11) NV (AGP), ATI Radeon QD (AGP),
    ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
    ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP),
    ATI Radeon 9100 QM (AGP), ATI Radeon 7500 QW (AGP/PCI),
    ATI Radeon 7500 QX (AGP/PCI), ATI Radeon VE/7000 QY (AGP/PCI),
    ATI Radeon VE/7000 QZ (AGP/PCI), ATI ES1000 515E (PCI),
    ATI Radeon Mobility X300 (M22) 5460 (PCIE),
    ATI Radeon Mobility X600 SE (M24C) 5462 (PCIE),
    ATI FireGL M22 GL 5464 (PCIE), ATI Radeon X800 (R423) UH (PCIE),
    ATI Radeon X800PRO (R423) UI (PCIE),
    ATI Radeon X800LE (R423) UJ (PCIE),
    ATI Radeon X800SE (R423) UK (PCIE),
    ATI Radeon X800 XTP (R430) (PCIE), ATI Radeon X800 XL (R430) (PCIE),
    ATI Radeon X800 SE (R430) (PCIE), ATI Radeon X800 (R430) (PCIE),
    ATI FireGL V7100 (R423) (PCIE), ATI FireGL V5100 (R423) UQ (PCIE),
    ATI FireGL unknown (R423) UR (PCIE),
    ATI FireGL unknown (R423) UT (PCIE),
    ATI Mobility FireGL V5000 (M26) (PCIE),
    ATI Mobility FireGL V5000 (M26) (PCIE),
    ATI Mobility Radeon X700 XL (M26) (PCIE),
    ATI Mobility Radeon X700 (M26) (PCIE),
    ATI Mobility Radeon X700 (M26) (PCIE),
    ATI Radeon X550XTX 5657 (PCIE), ATI Radeon 9100 IGP (A5) 5834,
    ATI Radeon Mobility 9100 IGP (U3) 5835,
    ATI Radeon XPRESS 200 5954 (PCIE),
    ATI Radeon XPRESS 200M 5955 (PCIE), ATI Radeon 9250 5960 (AGP),
    ATI Radeon 9200 5961 (AGP), ATI Radeon 9200 5962 (AGP),
    ATI Radeon 9200SE 5964 (AGP), ATI FireMV 2200 (PCI),
    ATI ES1000 5969 (PCI), ATI Radeon XPRESS 200 5974 (PCIE),
    ATI Radeon XPRESS 200M 5975 (PCIE),
    ATI Radeon XPRESS 200 5A41 (PCIE),
    ATI Radeon XPRESS 200M 5A42 (PCIE),
    ATI Radeon XPRESS 200 5A61 (PCIE),
    ATI Radeon XPRESS 200M 5A62 (PCIE),
    ATI Radeon X300 (RV370) 5B60 (PCIE),
    ATI Radeon X600 (RV370) 5B62 (PCIE),
    ATI Radeon X550 (RV370) 5B63 (PCIE),
    ATI FireGL V3100 (RV370) 5B64 (PCIE),
    ATI FireMV 2200 PCIE (RV370) 5B65 (PCIE),
    ATI Radeon Mobility 9200 (M9+) 5C61 (AGP),
    ATI Radeon Mobility 9200 (M9+) 5C63 (AGP),
    ATI Mobility Radeon X800 XT (M28) (PCIE),
    ATI Mobility FireGL V5100 (M28) (PCIE),
    ATI Mobility Radeon X800 (M28) (PCIE), ATI Radeon X850 5D4C (PCIE),
    ATI Radeon X850 XT PE (R480) (PCIE),
    ATI Radeon X850 SE (R480) (PCIE), ATI Radeon X850 PRO (R480) (PCIE),
    ATI unknown Radeon / FireGL (R480) 5D50 (PCIE),
    ATI Radeon X850 XT (R480) (PCIE),
    ATI Radeon X800XT (R423) 5D57 (PCIE),
    ATI FireGL V5000 (RV410) (PCIE), ATI Radeon X700 XT (RV410) (PCIE),
    ATI Radeon X700 PRO (RV410) (PCIE),
    ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X700 (RV410) (PCIE),
    ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X1800,
    ATI Mobility Radeon X1800 XT, ATI Mobility Radeon X1800,
    ATI Mobility FireGL V7200, ATI FireGL V7200, ATI FireGL V5300,
    ATI Mobility FireGL V7100, ATI Radeon X1800, ATI Radeon X1800,
    ATI Radeon X1800, ATI Radeon X1800, ATI Radeon X1800,
    ATI FireGL V7300, ATI FireGL V7350, ATI Radeon X1600, ATI RV505,
    ATI Radeon X1300/X1550, ATI Radeon X1550, ATI M54-GL,
    ATI Mobility Radeon X1400, ATI Radeon X1300/X1550,
    ATI Radeon X1550 64-bit, ATI Mobility Radeon X1300,
    ATI Mobility Radeon X1300, ATI Mobility Radeon X1300,
    ATI Mobility Radeon X1300, ATI Radeon X1300, ATI Radeon X1300,
    ATI RV505, ATI RV505, ATI FireGL V3300, ATI FireGL V3350,
    ATI Radeon X1300, ATI Radeon X1550 64-bit, ATI Radeon X1300/X1550,
    ATI Radeon X1600, ATI Radeon X1300/X1550, ATI Mobility Radeon X1450,
    ATI Radeon X1300/X1550, ATI Mobility Radeon X2300,
    ATI Mobility Radeon X2300, ATI Mobility Radeon X1350,
    ATI Mobility Radeon X1350, ATI Mobility Radeon X1450,
    ATI Radeon X1300, ATI Radeon X1550, ATI Mobility Radeon X1350,
    ATI FireMV 2250, ATI Radeon X1550 64-bit, ATI Radeon X1600,
    ATI Radeon X1650, ATI Radeon X1600, ATI Radeon X1600,
    ATI Mobility FireGL V5200, ATI Mobility Radeon X1600,
    ATI Radeon X1650, ATI Radeon X1650, ATI Radeon X1600,
    ATI Radeon X1300 XT/X1600 Pro, ATI FireGL V3400,
    ATI Mobility FireGL V5250, ATI Mobility Radeon X1700,
    ATI Mobility Radeon X1700 XT, ATI FireGL V5200,
    ATI Mobility Radeon X1700, ATI Radeon X2300HD,
    ATI Mobility Radeon HD 2300, ATI Mobility Radeon HD 2300,
    ATI Radeon X1950, ATI Radeon X1900, ATI Radeon X1950,
    ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
    ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
    ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
    ATI AMD Stream Processor, ATI Radeon X1900, ATI Radeon X1950,
    ATI RV560, ATI RV560, ATI Mobility Radeon X1900, ATI RV560,
    ATI Radeon X1950 GT, ATI RV570, ATI RV570, ATI FireGL V7400,
    ATI RV560, ATI Radeon X1650, ATI Radeon X1650, ATI RV560,
    ATI Radeon 9100 PRO IGP 7834, ATI Radeon Mobility 9200 IGP 7835,
    ATI Radeon X1200, ATI Radeon X1200, ATI Radeon X1200,
    ATI Radeon X1200, ATI Radeon X1200, ATI RS740, ATI RS740M, ATI RS740,
    ATI RS740M, ATI Radeon HD 2900 XT, ATI Radeon HD 2900 XT,
    ATI Radeon HD 2900 XT, ATI Radeon HD 2900 Pro, ATI Radeon HD 2900 GT,
    ATI FireGL V8650, ATI FireGL V8600, ATI FireGL V7600,
    ATI Radeon 4800 Series, ATI Radeon HD 4870 x2,
    ATI Radeon 4800 Series, ATI Radeon HD 4850 x2,
    ATI FirePro V8750 (FireGL), ATI FirePro V7760 (FireGL),
    ATI Mobility RADEON HD 4850, ATI Mobility RADEON HD 4850 X2,
    ATI Radeon 4800 Series, ATI FirePro RV770, AMD FireStream 9270,
    AMD FireStream 9250, ATI FirePro V8700 (FireGL),
    ATI Mobility RADEON HD 4870, ATI Mobility RADEON M98,
    ATI Mobility RADEON HD 4870, ATI Radeon 4800 Series,
    ATI Radeon 4800 Series, ATI FirePro M7750, ATI M98, ATI M98, ATI M98,
    ATI Mobility Radeon HD 4650, ATI Radeon RV730 (AGP),
    ATI Mobility Radeon HD 4670, ATI FirePro M5750,
    ATI Mobility Radeon HD 4670, ATI Radeon RV730 (AGP),
    ATI RV730XT [Radeon HD 4670], ATI RADEON E4600,
    ATI Radeon HD 4600 Series, ATI RV730 PRO [Radeon HD 4650],
    ATI FirePro V7750 (FireGL), ATI FirePro V5700 (FireGL),
    ATI FirePro V3750 (FireGL), ATI Mobility Radeon HD 4830,
    ATI Mobility Radeon HD 4850, ATI FirePro M7740, ATI RV740,
    ATI Radeon HD 4770, ATI Radeon HD 4700 Series, ATI Radeon HD 4770,
    ATI FirePro M5750, ATI RV610, ATI Radeon HD 2400 XT,
    ATI Radeon HD 2400 Pro, ATI Radeon HD 2400 PRO AGP, ATI FireGL V4000,
    ATI RV610, ATI Radeon HD 2350, ATI Mobility Radeon HD 2400 XT,
    ATI Mobility Radeon HD 2400, ATI RADEON E2400, ATI RV610,
    ATI FireMV 2260, ATI RV670, ATI Radeon HD3870,
    ATI Mobility Radeon HD 3850, ATI Radeon HD3850,
    ATI Mobility Radeon HD 3850 X2, ATI RV670,
    ATI Mobility Radeon HD 3870, ATI Mobility Radeon HD 3870 X2,
    ATI Radeon HD3870 X2, ATI FireGL V7700, ATI Radeon HD3850,
    ATI Radeon HD3690, AMD Firestream 9170, ATI Radeon HD 4550,
    ATI Radeon RV710, ATI Radeon RV710, ATI Radeon RV710,
    ATI Radeon HD 4350, ATI Mobility Radeon 4300 Series,
    ATI Mobility Radeon 4500 Series, ATI Mobility Radeon 4500 Series,
    ATI FirePro RG220, ATI Mobility Radeon 4330, ATI RV630,
    ATI Mobility Radeon HD 2600, ATI Mobility Radeon HD 2600 XT,
    ATI Radeon HD 2600 XT AGP, ATI Radeon HD 2600 Pro AGP,
    ATI Radeon HD 2600 XT, ATI Radeon HD 2600 Pro, ATI Gemini RV630,
    ATI Gemini Mobility Radeon HD 2600 XT, ATI FireGL V5600,
    ATI FireGL V3600, ATI Radeon HD 2600 LE,
    ATI Mobility FireGL Graphics Processor, ATI Radeon HD 3470,
    ATI Mobility Radeon HD 3430, ATI Mobility Radeon HD 3400 Series,
    ATI Radeon HD 3450, ATI Radeon HD 3450, ATI Radeon HD 3430,
    ATI Radeon HD 3450, ATI FirePro V3700, ATI FireMV 2450,
    ATI FireMV 2260, ATI FireMV 2260, ATI Radeon HD 3600 Series,
    ATI Radeon HD 3650 AGP, ATI Radeon HD 3600 PRO,
    ATI Radeon HD 3600 XT, ATI Radeon HD 3600 PRO,
    ATI Mobility Radeon HD 3650, ATI Mobility Radeon HD 3670,
    ATI Mobility FireGL V5700, ATI Mobility FireGL V5725,
    ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
    ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
    ATI Radeon HD 3300 Graphics, ATI Radeon HD 3200 Graphics,
    ATI Radeon 3000 Graphics, SUMO, SUMO, SUMO2, SUMO2, SUMO2, SUMO2,
    SUMO, SUMO, SUMO, SUMO, SUMO, SUMO, SUMO, ATI Radeon HD 4200,
    ATI Radeon 4100, ATI Mobility Radeon HD 4200,
    ATI Mobility Radeon 4100, ATI Radeon HD 4290, ATI Radeon HD 4250,
    AMD Radeon HD 6310 Graphics, AMD Radeon HD 6310 Graphics,
    AMD Radeon HD 6250 Graphics, AMD Radeon HD 6250 Graphics,
    AMD Radeon HD 6300 Series Graphics,
    AMD Radeon HD 6200 Series Graphics, PALM, PALM, CYPRESS,
    ATI FirePro (FireGL) Graphics Adapter,
    ATI FirePro (FireGL) Graphics Adapter,
    ATI FirePro (FireGL) Graphics Adapter, AMD Firestream 9370,
    AMD Firestream 9350, ATI Radeon HD 5800 Series,
    ATI Radeon HD 5800 Series, ATI Radeon HD 5800 Series,
    ATI Radeon HD 5800 Series, ATI Radeon HD 5900 Series,
    ATI Radeon HD 5900 Series, ATI Mobility Radeon HD 5800 Series,
    ATI Mobility Radeon HD 5800 Series,
    ATI FirePro (FireGL) Graphics Adapter,
    ATI FirePro (FireGL) Graphics Adapter,
    ATI Mobility Radeon HD 5800 Series, ATI Radeon HD 5700 Series,
    ATI Radeon HD 5700 Series, ATI Radeon HD 6700 Series,
    ATI Radeon HD 5700 Series, ATI Radeon HD 6700 Series,
    ATI Mobility Radeon HD 5000 Series,
    ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon HD 5570,
    ATI FirePro (FireGL) Graphics Adapter,
    ATI FirePro (FireGL) Graphics Adapter, ATI Radeon HD 5670,
    ATI Radeon HD 5570, ATI Radeon HD 5500 Series, REDWOOD,
    ATI Mobility Radeon HD 5000 Series,
    ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon Graphics,
    ATI Mobility Radeon Graphics, CEDAR,
    ATI FirePro (FireGL) Graphics Adapter,
    ATI FirePro (FireGL) Graphics Adapter, ATI FirePro 2270, CEDAR,
    ATI Radeon HD 5450, CEDAR, CEDAR, CAYMAN, CAYMAN, CAYMAN, CAYMAN,
    CAYMAN, CAYMAN, CAYMAN, CAYMAN, CAYMAN, CAYMAN,
    AMD Radeon HD 6900 Series, AMD Radeon HD 6900 Series, CAYMAN, CAYMAN,
    CAYMAN, AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series,
    BARTS, BARTS, Mobility Radeon HD 6000 Series,
    Mobility Radeon HD 6000 Series, BARTS, BARTS, BARTS, BARTS,
    AMD Radeon HD 6800 Series, AMD Radeon HD 6800 Series,
    AMD Radeon HD 6700 Series, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
    TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
    TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
    CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS,
    CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, ARUBA, ARUBA, ARUBA,
    ARUBA, ARUBA, ARUBA, ARUBA
    [ 9.234] (++) using VT number 7
    [ 9.238] (II) [KMS] Kernel modesetting enabled.
    [ 9.238] (II) RADEON(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 9.238] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
    [ 9.238] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
    [ 9.238] (==) RADEON(0): Default visual is TrueColor
    [ 9.238] (==) RADEON(0): RGB weight 888
    [ 9.238] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
    [ 9.238] (--) RADEON(0): Chipset: "ATI Radeon X1300/X1550" (ChipID = 0x7142)
    [ 9.238] (II) RADEON(0): PCIE card detected
    [ 9.238] drmOpenDevice: node name is /dev/dri/card0
    [ 9.238] drmOpenDevice: open result is 8, (OK)
    [ 9.238] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
    [ 9.238] drmOpenDevice: node name is /dev/dri/card0
    [ 9.238] drmOpenDevice: open result is 8, (OK)
    [ 9.238] drmOpenByBusid: drmOpenMinor returns 8
    [ 9.238] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
    [ 9.238] (II) Loading sub module "exa"
    [ 9.238] (II) LoadModule: "exa"
    [ 9.238] (II) Loading /usr/lib/xorg/modules/libexa.so
    [ 9.256] (II) Module exa: vendor="X.Org Foundation"
    [ 9.256] compiled for 1.12.1, module version = 2.5.0
    [ 9.256] ABI class: X.Org Video Driver, version 12.0
    [ 9.256] (II) RADEON(0): KMS Color Tiling: enabled
    [ 9.256] (II) RADEON(0): KMS Pageflipping: enabled
    [ 9.256] (II) RADEON(0): SwapBuffers wait for vsync: enabled
    [ 9.314] (II) RADEON(0): Output VGA-0 has no monitor section
    [ 9.347] (II) RADEON(0): Output S-video has no monitor section
    [ 9.405] (II) RADEON(0): Output DVI-0 has no monitor section
    [ 9.463] (II) RADEON(0): EDID for output VGA-0
    [ 9.463] (II) RADEON(0): Manufacturer: FUS Model: 7c7 Serial#: 1
    [ 9.463] (II) RADEON(0): Year: 2009 Week: 53
    [ 9.463] (II) RADEON(0): EDID Version: 1.3
    [ 9.463] (II) RADEON(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
    [ 9.463] (II) RADEON(0): Sync: Separate
    [ 9.463] (II) RADEON(0): Max Image Size [cm]: horiz.: 47 vert.: 30
    [ 9.463] (II) RADEON(0): Gamma: 2.30
    [ 9.463] (II) RADEON(0): DPMS capabilities: Off; RGB/Color Display
    [ 9.463] (II) RADEON(0): First detailed timing is preferred mode
    [ 9.463] (II) RADEON(0): redX: 0.644 redY: 0.333 greenX: 0.286 greenY: 0.605
    [ 9.463] (II) RADEON(0): blueX: 0.152 blueY: 0.076 whiteX: 0.313 whiteY: 0.329
    [ 9.463] (II) RADEON(0): Supported established timings:
    [ 9.463] (II) RADEON(0): 720x400@70Hz
    [ 9.463] (II) RADEON(0): 640x480@60Hz
    [ 9.463] (II) RADEON(0): 640x480@75Hz
    [ 9.463] (II) RADEON(0): 800x600@60Hz
    [ 9.463] (II) RADEON(0): 800x600@75Hz
    [ 9.463] (II) RADEON(0): 1024x768@60Hz
    [ 9.463] (II) RADEON(0): 1024x768@75Hz
    [ 9.463] (II) RADEON(0): 1280x1024@75Hz
    [ 9.463] (II) RADEON(0): Manufacturer's mask: 0
    [ 9.463] (II) RADEON(0): Supported standard timings:
    [ 9.463] (II) RADEON(0): #0: hsize: 1440 vsize 900 refresh: 75 vid: 3989
    [ 9.463] (II) RADEON(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 9.463] (II) RADEON(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
    [ 9.463] (II) RADEON(0): #3: hsize: 1152 vsize 864 refresh: 75 vid: 20337
    [ 9.463] (II) RADEON(0): #4: hsize: 1440 vsize 900 refresh: 60 vid: 149
    [ 9.463] (II) RADEON(0): #5: hsize: 1680 vsize 1050 refresh: 60 vid: 179
    [ 9.463] (II) RADEON(0): #6: hsize: 1280 vsize 720 refresh: 60 vid: 49281
    [ 9.463] (II) RADEON(0): Supported detailed timing:
    [ 9.463] (II) RADEON(0): clock: 146.2 MHz Image Size: 474 x 296 mm
    [ 9.463] (II) RADEON(0): h_active: 1680 h_sync: 1784 h_sync_end 1960 h_blank_end 2240 h_border: 0
    [ 9.463] (II) RADEON(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: 1089 v_border: 0
    [ 9.463] (II) RADEON(0): Serial No: YV1U055401
    [ 9.463] (II) RADEON(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 83 kHz, PixClock max 155 MHz
    [ 9.463] (II) RADEON(0): Monitor name: SL3220W
    [ 9.463] (II) RADEON(0): EDID (in hex):
    [ 9.463] (II) RADEON(0): 00ffffffffffff001ab3c70701000000
    [ 9.463] (II) RADEON(0): 35130103682f1e822ad425a455499b27
    [ 9.463] (II) RADEON(0): 135054a54b00950f81808140714f9500
    [ 9.463] (II) RADEON(0): b30081c0010121399030621a274068b0
    [ 9.463] (II) RADEON(0): 3600da281100001c000000ff00595631
    [ 9.463] (II) RADEON(0): 553035353430310a2020000000fd0038
    [ 9.463] (II) RADEON(0): 4b1e530f000a202020202020000000fc
    [ 9.463] (II) RADEON(0): 00534c33323230570a20202020200014
    [ 9.463] (II) RADEON(0): EDID vendor "FUS", prod id 1991
    [ 9.559] (II) RADEON(0): Using EDID range info for horizontal sync
    [ 9.559] (II) RADEON(0): Using EDID range info for vertical refresh
    [ 9.559] (II) RADEON(0): Printing DDC gathered Modelines:
    [ 9.559] (II) RADEON(0): Modeline "1680x1050"x0.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz eP)
    [ 9.560] (II) RADEON(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "1440x900"x0.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "1440x900"x0.0 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "1280x720"x60.0 74.48 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.8 kHz e)
    [ 9.560] (II) RADEON(0): Printing probed modes for output VGA-0
    [ 9.560] (II) RADEON(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz eP)
    [ 9.560] (II) RADEON(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "1440x900"x75.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "1280x720"x60.0 74.44 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.7 kHz)
    [ 9.560] (II) RADEON(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 9.560] (II) RADEON(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 9.593] (II) RADEON(0): EDID for output S-video
    [ 9.651] (II) RADEON(0): EDID for output DVI-0
    [ 9.651] (II) RADEON(0): Manufacturer: NEC Model: 6692 Serial#: 16843009
    [ 9.651] (II) RADEON(0): Year: 2006 Week: 16
    [ 9.651] (II) RADEON(0): EDID Version: 1.3
    [ 9.651] (II) RADEON(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
    [ 9.651] (II) RADEON(0): Sync: Separate Composite SyncOnGreen
    [ 9.651] (II) RADEON(0): Max Image Size [cm]: horiz.: 38 vert.: 30
    [ 9.651] (II) RADEON(0): Gamma: 2.20
    [ 9.651] (II) RADEON(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
    [ 9.651] (II) RADEON(0): First detailed timing is preferred mode
    [ 9.651] (II) RADEON(0): redX: 0.640 redY: 0.329 greenX: 0.300 greenY: 0.600
    [ 9.651] (II) RADEON(0): blueX: 0.150 blueY: 0.060 whiteX: 0.313 whiteY: 0.329
    [ 9.651] (II) RADEON(0): Supported established timings:
    [ 9.651] (II) RADEON(0): 720x400@70Hz
    [ 9.651] (II) RADEON(0): 640x480@60Hz
    [ 9.651] (II) RADEON(0): 640x480@67Hz
    [ 9.651] (II) RADEON(0): 640x480@72Hz
    [ 9.651] (II) RADEON(0): 640x480@75Hz
    [ 9.651] (II) RADEON(0): 800x600@56Hz
    [ 9.651] (II) RADEON(0): 800x600@60Hz
    [ 9.651] (II) RADEON(0): 800x600@72Hz
    [ 9.651] (II) RADEON(0): 800x600@75Hz
    [ 9.651] (II) RADEON(0): 832x624@75Hz
    [ 9.651] (II) RADEON(0): 1024x768@60Hz
    [ 9.651] (II) RADEON(0): 1024x768@70Hz
    [ 9.651] (II) RADEON(0): 1024x768@75Hz
    [ 9.651] (II) RADEON(0): 1280x1024@75Hz
    [ 9.651] (II) RADEON(0): 1152x864@75Hz
    [ 9.651] (II) RADEON(0): Manufacturer's mask: 0
    [ 9.651] (II) RADEON(0): Supported standard timings:
    [ 9.651] (II) RADEON(0): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
    [ 9.651] (II) RADEON(0): #1: hsize: 1280 vsize 960 refresh: 60 vid: 16513
    [ 9.651] (II) RADEON(0): #2: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 9.651] (II) RADEON(0): Supported detailed timing:
    [ 9.651] (II) RADEON(0): clock: 108.0 MHz Image Size: 376 x 301 mm
    [ 9.651] (II) RADEON(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
    [ 9.651] (II) RADEON(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
    [ 9.651] (II) RADEON(0): Ranges: V min: 56 V max: 75 Hz, H min: 31 H max: 81 kHz, PixClock max 145 MHz
    [ 9.651] (II) RADEON(0): Monitor name: 90GX2
    [ 9.651] (II) RADEON(0): Serial No: 64117793GB
    [ 9.652] (II) RADEON(0): EDID (in hex):
    [ 9.652] (II) RADEON(0): 00ffffffffffff0038a3926601010101
    [ 9.652] (II) RADEON(0): 101001030e261e78eade95a3544c9926
    [ 9.652] (II) RADEON(0): 0f5054bfef80714f8140818001010101
    [ 9.652] (II) RADEON(0): 010101010101302a009851002a403070
    [ 9.652] (II) RADEON(0): 1300782d1100001e000000fd00384b1f
    [ 9.652] (II) RADEON(0): 510e000a202020202020000000fc0039
    [ 9.652] (II) RADEON(0): 304758320a20202020202020000000ff
    [ 9.652] (II) RADEON(0): 00363431313737393347420a202000e1
    [ 9.652] (II) RADEON(0): Printing probed modes for output DVI-0
    [ 9.652] (II) RADEON(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 9.652] (II) RADEON(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 9.652] (II) RADEON(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 9.652] (II) RADEON(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 9.652] (II) RADEON(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 9.652] (II) RADEON(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 9.652] (II) RADEON(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 9.652] (II) RADEON(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 9.652] (II) RADEON(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 9.652] (II) RADEON(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 9.652] (II) RADEON(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 9.652] (II) RADEON(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 9.652] (II) RADEON(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
    [ 9.652] (II) RADEON(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 9.652] (II) RADEON(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 9.652] (II) RADEON(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 9.652] (II) RADEON(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 9.652] (II) RADEON(0): Output VGA-0 connected
    [ 9.652] (II) RADEON(0): Output S-video disconnected
    [ 9.652] (II) RADEON(0): Output DVI-0 connected
    [ 9.652] (II) RADEON(0): Using exact sizes for initial modes
    [ 9.652] (II) RADEON(0): Output VGA-0 using initial mode 1280x1024
    [ 9.652] (II) RADEON(0): Output DVI-0 using initial mode 1280x1024
    [ 9.652] (II) RADEON(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 9.652] (II) RADEON(0): mem size init: gart size :1fdff000 vram size: s:10000000 visible:f8d4000
    [ 9.652] (II) RADEON(0): EXA: Driver will allow EXA pixmaps in VRAM
    [ 9.652] (**) RADEON(0): Display dimensions: (470, 300) mm
    [ 9.652] (**) RADEON(0): DPI set to (69, 86)
    [ 9.652] (II) Loading sub module "fb"
    [ 9.652] (II) LoadModule: "fb"
    [ 9.652] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 9.678] (II) Module fb: vendor="X.Org Foundation"
    [ 9.678] compiled for 1.12.1, module version = 1.0.0
    [ 9.678] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 9.678] (II) Loading sub module "ramdac"
    [ 9.678] (II) LoadModule: "ramdac"
    [ 9.678] (II) Module "ramdac" already built-in
    [ 9.678] (--) Depth 24 pixmap format is 32 bpp
    [ 9.687] (II) RADEON(0): [DRI2] Setup complete
    [ 9.687] (II) RADEON(0): [DRI2] DRI driver: r300
    [ 9.687] (II) RADEON(0): [DRI2] VDPAU driver: r300
    [ 9.687] (II) RADEON(0): Front buffer size: 5120K
    [ 9.688] (II) RADEON(0): VRAM usage limit set to 224712K
    [ 9.738] (==) RADEON(0): Backing store disabled
    [ 9.738] (II) RADEON(0): Direct rendering enabled
    [ 9.770] (II) RADEON(0): Render acceleration enabled for R300/R400/R500 type cards.
    [ 9.770] (II) RADEON(0): Setting EXA maxPitchBytes
    [ 9.770] (II) EXA(0): Driver allocated offscreen pixmaps
    [ 9.770] (II) EXA(0): Driver registered support for the following operations:
    [ 9.770] (II) Solid
    [ 9.770] (II) Copy
    [ 9.770] (II) Composite (RENDER acceleration)
    [ 9.770] (II) UploadToScreen
    [ 9.770] (II) DownloadFromScreen
    [ 9.783] (II) RADEON(0): Acceleration enabled
    [ 9.783] (==) RADEON(0): DPMS enabled
    [ 9.783] (==) RADEON(0): Silken mouse enabled
    [ 9.789] (II) RADEON(0): Set up textured video
    [ 9.789] (II) RADEON(0): [XvMC] Associated with Radeon Textured Video.
    [ 9.789] (II) RADEON(0): [XvMC] Extension initialized.
    [ 9.789] (II) RADEON(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 9.795] (--) RandR disabled
    [ 9.795] (II) Initializing built-in extension Generic Event Extension
    [ 9.795] (II) Initializing built-in extension SHAPE
    [ 9.795] (II) Initializing built-in extension MIT-SHM
    [ 9.795] (II) Initializing built-in extension XInputExtension
    [ 9.795] (II) Initializing built-in extension XTEST
    [ 9.795] (II) Initializing built-in extension BIG-REQUESTS
    [ 9.795] (II) Initializing built-in extension SYNC
    [ 9.795] (II) Initializing built-in extension XKEYBOARD
    [ 9.795] (II) Initializing built-in extension XC-MISC
    [ 9.795] (II) Initializing built-in extension SECURITY
    [ 9.795] (II) Initializing built-in extension XINERAMA
    [ 9.795] (II) Initializing built-in extension XFIXES
    [ 9.795] (II) Initializing built-in extension RENDER
    [ 9.795] (II) Initializing built-in extension RANDR
    [ 9.795] (II) Initializing built-in extension COMPOSITE
    [ 9.795] (II) Initializing built-in extension DAMAGE
    [ 10.154] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 10.154] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 10.154] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 10.154] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 10.154] (II) AIGLX: Loaded and initialized r300
    [ 10.154] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 10.195] (II) RADEON(0): Setting screen physical size to 338 x 270
    [ 10.437] (II) config/udev: Adding input device Power Button (/dev/input/event1)
    [ 10.437] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 10.437] (II) LoadModule: "evdev"
    [ 10.437] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 10.453] (II) Module evdev: vendor="X.Org Foundation"
    [ 10.453] compiled for 1.12.0, module version = 2.7.0
    [ 10.453] Module class: X.Org XInput Driver
    [ 10.453] ABI class: X.Org XInput driver, version 16.0
    [ 10.453] (II) Using input driver 'evdev' for 'Power Button'
    [ 10.453] (**) Power Button: always reports core events
    [ 10.453] (**) evdev: Power Button: Device: "/dev/input/event1"
    [ 10.453] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 10.453] (--) evdev: Power Button: Found keys
    [ 10.453] (II) evdev: Power Button: Configuring as keyboard
    [ 10.453] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
    [ 10.453] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 10.453] (**) Option "xkb_rules" "evdev"
    [ 10.453] (**) Option "xkb_model" "evdev"
    [ 10.453] (**) Option "xkb_layout" "us"
    [ 10.476] (II) config/udev: Adding input device Power Button (/dev/input/event0)
    [ 10.476] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 10.476] (II) Using input driver 'evdev' for 'Power Button'
    [ 10.476] (**) Power Button: always reports core events
    [ 10.476] (**) evdev: Power Button: Device: "/dev/input/event0"
    [ 10.476] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 10.476] (--) evdev: Power Button: Found keys
    [ 10.476] (II) evdev: Power Button: Configuring as keyboard
    [ 10.476] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0/event0"
    [ 10.476] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 10.476] (**) Option "xkb_rules" "evdev"
    [ 10.476] (**) Option "xkb_model" "evdev"
    [ 10.476] (**) Option "xkb_layout" "us"
    [ 10.477] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event3)
    [ 10.477] (II) No input driver specified, ignoring this device.
    [ 10.477] (II) This device may have been added with another device file.
    [ 10.477] (II) config/udev: Adding input device HDA Intel Front Mic (/dev/input/event4)
    [ 10.477] (II) No input driver specified, ignoring this device.
    [ 10.477] (II) This device may have been added with another device file.
    [ 10.477] (II) config/udev: Adding input device HDA Intel Rear Mic (/dev/input/event5)
    [ 10.477] (II) No input driver specified, ignoring this device.
    [ 10.477] (II) This device may have been added with another device file.
    [ 10.478] (II) config/udev: Adding input device HDA Intel Front Headphone (/dev/input/event6)
    [ 10.478] (II) No input driver specified, ignoring this device.
    [ 10.478] (II) This device may have been added with another device file.
    [ 10.478] (II) config/udev: Adding input device HDA Intel Line Out (/dev/input/event7)
    [ 10.478] (II) No input driver specified, ignoring this device.
    [ 10.478] (II) This device may have been added with another device file.
    [ 10.478] (II) config/udev: Adding input device zc3xx (/dev/input/event10)
    [ 10.478] (**) zc3xx: Applying InputClass "evdev keyboard catchall"
    [ 10.478] (II) Using input driver 'evdev' for 'zc3xx'
    [ 10.478] (**) zc3xx: always reports core events
    [ 10.478] (**) evdev: zc3xx: Device: "/dev/input/event10"
    [ 10.478] (--) evdev: zc3xx: Vendor 0x41e Product 0x403a
    [ 10.478] (--) evdev: zc3xx: Found keys
    [ 10.478] (II) evdev: zc3xx: Configuring as keyboard
    [ 10.478] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-1/input/input10/event10"
    [ 10.478] (II) XINPUT: Adding extended input device "zc3xx" (type: KEYBOARD, id 8)
    [ 10.478] (**) Option "xkb_rules" "evdev"
    [ 10.478] (**) Option "xkb_model" "evdev"
    [ 10.478] (**) Option "xkb_layout" "us"
    [ 10.479] (II) config/udev: Adding input device LITEON Technology USB Multimedia Keyboard (/dev/input/event8)
    [ 10.479] (**) LITEON Technology USB Multimedia Keyboard: Applying InputClass "evdev keyboard catchall"
    [ 10.479] (II) Using input driver 'evdev' for 'LITEON Technology USB Multimedia Keyboard'
    [ 10.479] (**) LITEON Technology USB Multimedia Keyboard: always reports core events
    [ 10.479] (**) evdev: LITEON Technology USB Multimedia Keyboard: Device: "/dev/input/event8"
    [ 10.479] (--) evdev: LITEON Technology USB Multimedia Keyboard: Vendor 0x46d Product 0xc312
    [ 10.479] (--) evdev: LITEON Technology USB Multimedia Keyboard: Found keys
    [ 10.479] (II) evdev: LITEON Technology USB Multimedia Keyboard: Configuring as keyboard
    [ 10.479] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0/input/input8/event8"
    [ 10.479] (II) XINPUT: Adding extended input device "LITEON Technology USB Multimedia Keyboard" (type: KEYBOARD, id 9)
    [ 10.479] (**) Option "xkb_rules" "evdev"
    [ 10.479] (**) Option "xkb_model" "evdev"
    [ 10.479] (**) Option "xkb_layout" "us"
    [ 10.479] (II) config/udev: Adding input device ImPS/2 Logitech Wheel Mouse (/dev/input/event9)
    [ 10.479] (**) ImPS/2 Logitech Wheel Mouse: Applying InputClass "evdev pointer catchall"
    [ 10.479] (II) Using input driver 'evdev' for 'ImPS/2 Logitech Wheel Mouse'
    [ 10.479] (**) ImPS/2 Logitech Wheel Mouse: always reports core events
    [ 10.479] (**) evdev: ImPS/2 Logitech Wheel Mouse: Device: "/dev/input/event9"
    [ 10.479] (--) evdev: ImPS/2 Logitech Wheel Mouse: Vendor 0x2 Product 0x5
    [ 10.479] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found 3 mouse buttons
    [ 10.479] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found scroll wheel(s)
    [ 10.479] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found relative axes
    [ 10.479] (--) evdev: ImPS/2 Logitech Wheel Mouse: Found x and y relative axes
    [ 10.479] (II) evdev: ImPS/2 Logitech Wheel Mouse: Configuring as mouse
    [ 10.479] (II) evdev: ImPS/2 Logitech Wheel Mouse: Adding scrollwheel support
    [ 10.479] (**) evdev: ImPS/2 Logitech Wheel Mouse: YAxisMapping: buttons 4 and 5
    [ 10.479] (**) evdev: ImPS/2 Logitech Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 10.479] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input9/event9"
    [ 10.479] (II) XINPUT: Adding extended input device "ImPS/2 Logitech Wheel Mouse" (type: MOUSE, id 10)
    [ 10.479] (II) evdev: ImPS/2 Logitech Wheel Mouse: initialized for relative axes.
    [ 10.480] (**) ImPS/2 Logitech Wheel Mouse: (accel) keeping acceleration scheme 1
    [ 10.480] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration profile 0
    [ 10.480] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration factor: 2.000
    [ 10.480] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration threshold: 4
    [ 10.480] (II) config/udev: Adding input device ImPS/2 Logitech Wheel Mouse (/dev/input/mouse0)
    [ 10.480] (II) No input driver specified, ignoring this device.
    [ 10.480] (II) This device may have been added with another device file.
    [ 10.480] (II) config/udev: Adding input device PC Speaker (/dev/input/event2)
    [ 10.480] (II) No input driver specified, ignoring this device.
    [ 10.480] (II) This device may have been added with another device file.
    [ 26.618] (II) RADEON(0): EDID vendor "NEC", prod id 26258
    [ 26.618] (II) RADEON(0): Using hsync ranges from config file
    [ 26.618] (II) RADEON(0): Using vrefresh ranges from config file
    [ 26.618] (II) RADEON(0): Printing DDC gathered Modelines:
    [ 26.618] (II) RADEON(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 26.618] (II) RADEON(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 26.618] (II) RADEON(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 26.618] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 26.618] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 26.618] (II) RADEON(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 26.618] (II) RADEON(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 26.618] (II) RADEON(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 26.618] (II) RADEON(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 26.618] (II) RADEON(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 26.618] (II) RADEON(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 26.618] (II) RADEON(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 26.618] (II) RADEON(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 26.618] (II) RADEON(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 26.618] (II) RADEON(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 26.618] (II) RADEON(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 26.618] (II) RADEON(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 26.622] (II) RADEON(0): Allocate new frame buffer 2960x1056 stride 3008
    [ 26.631] (II) RADEON(0): VRAM usage limit set to 218152K
    [ 36.615] (II) RADEON(0): EDID vendor "NEC", prod id 26258
    [ 36.615] (II) RADEON(0): Using hsync ranges from config file
    [ 36.615] (II) RADEON(0): Using vrefresh ranges from config file
    [ 36.615] (II) RADEON(0): Printing DDC gathered Modelines:
    [ 36.615] (II) RADEON(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz eP)
    [ 36.615] (II) RADEON(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 36.615] (II) RADEON(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 36.615] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 36.615] (II) RADEON(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [ 36.615] (II) RADEON(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
    [ 36.615] (II) RADEON(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 36.615] (II) RADEON(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 36.615] (II) RADEON(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 36.615] (II) RADEON(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 36.615] (II) RADEON(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [ 36.615] (II) RADEON(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 36.615] (II) RADEON(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
    [ 36.615] (II) RADEON(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 36.615] (II) RADEON(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [ 36.615] (II) RADEON(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
    [ 36.615] (II) RADEON(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 16635.501]
    [ 16635.517] Backtrace:
    [ 16635.517] 0: /usr/bin/X (xorg_backtrace+0x36) [0x55d276]
    [ 16635.517] 1: /usr/bin/X (0x400000+0x160ca9) [0x560ca9]
    [ 16635.517] 2: /lib/libpthread.so.0 (0x7fd85ca81000+0xf140) [0x7fd85ca90140]
    [ 16635.517] 3: /lib/libc.so.6 (0x7fd85b915000+0x125731) [0x7fd85ba3a731]
    [ 16635.517] 4: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7fd859878000+0xa5e51) [0x7fd85991de51]
    [ 16635.517] 5: /usr/lib/xorg/modules/libexa.so (0x7fd859458000+0x9346) [0x7fd859461346]
    [ 16635.517] 6: /usr/bin/X (0x400000+0xf3aa2) [0x4f3aa2]
    [ 16635.517] 7: /usr/bin/X (0x400000+0x30bd3) [0x430bd3]
    [ 16635.517] 8: /usr/bin/X (0x400000+0x33f52) [0x433f52]
    [ 16635.517] 9: /usr/bin/X (0x400000+0x23165) [0x423165]
    [ 16635.517] 10: /lib/libc.so.6 (__libc_start_main+0xf5) [0x7fd85b936455]
    [ 16635.517] 11: /usr/bin/X (0x400000+0x2343d) [0x42343d]
    [ 16635.517]
    [ 16635.517] Bus error at address 0x7fd8504bf010
    [ 16635.517]
    Fatal server error:
    [ 16635.517] Caught signal 7 (Bus error). Server aborting
    [ 16635.517]
    [ 16635.517]
    Please consult the The X.Org Foundation support
    at [url]http://wiki.x.org[/url]
    for help.
    [ 16635.517] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 16635.517]
    [ 16635.542] (II) evdev: Power Button: Close
    [ 16635.542] (II) UnloadModule: "evdev"
    [ 16635.555] (II) evdev: Power Button: Close
    [ 16635.555] (II) UnloadModule: "evdev"
    [ 16635.569] (II) evdev: zc3xx: Close
    [ 16635.569] (II) UnloadModule: "evdev"
    [ 16635.582] (II) evdev: LITEON Technology USB Multimedia Keyboard: Close
    [ 16635.582] (II) UnloadModule: "evdev"
    [ 16635.597] (II) evdev: ImPS/2 Logitech Wheel Mouse: Close
    [ 16635.597] (II) UnloadModule: "evdev"
    [ 16635.597] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 16635.650] Server terminated with error (1). Closing log file.
    This happened when I tried to open a large image file in Firefox.
    This is frustrating ...
    Last edited by gigitek (2012-05-18 11:28:31)

  • Cannot get NB305 to boot USB drive to install Ubuntu 9.10 remix

    I've created the Ubuntu 9.10 remix boot USB drive on another linux system.  I've altered the NB305 BIOS to boot from the USB stick first.  But whenever I restart the light on the USB stick flickers then the netbook continues by booting from the hard drive, i.e. Windows 7 starter.   Any suggestions? 

    I've created the USB drive twice.   The first on a MAC using the exact steps defined on the page
    https://help.ubuntu.com/community/Installation/FromUSBStick.  When I tried that one, it wouldn't boot.   I tried again from a linux box using the 
    That one wouldn't boot, so I tried a SUSE Linux approach which I found googling which suggested:
     sudo dd -bx M8 -if=ISOfilename -of=/dev/sdg1
    That command is from memory, but I think it's close. Again, it wouldn't boot so I came to this forum.
    In both the MAC created stick and the Linux stick, the files appear to be the same:
    /media % ls -la Ubuntu-Netbook-Remix\ 9.10\ i386/
    total 3467
    dr-xr-xr-x 10 art  root    2048 2009-10-28 15:32 .
    drwxr-xr-x  6 root root    4096 2010-03-08 16:36 ..
    -r--r--r--  1 art  root     157 2009-10-28 15:32 autorun.inf
    dr-xr-xr-x  2 art  root    2048 2009-10-28 15:32 casper
    dr-xr-xr-x  2 art  root    2048 2009-10-28 15:32 .disk
    dr-xr-xr-x  3 art  root    2048 2009-10-28 15:32 dists
    dr-xr-xr-x  2 art  root    2048 2009-10-28 15:32 install
    dr-xr-xr-x  2 art  root   14336 2009-10-28 15:32 isolinux
    -r--r--r--  1 art  root    5389 2009-10-28 15:32 md5sum.txt
    dr-xr-xr-x  2 art  root    2048 2009-10-28 15:32 pics
    dr-xr-xr-x  4 art  root    2048 2009-10-28 15:32 pool
    dr-xr-xr-x  2 art  root    2048 2009-10-28 15:32 preseed
    -r--r--r--  1 art  root     236 2009-10-28 15:32 README.diskdefines
    lr-xr-xr-x  1 art  root       1 2009-10-28 15:32 ubuntu -> .
    -r--r--r--  2 art  root 2039576 2009-09-17 12:09 usb-creator.exe
    -r--r--r--  1 art  root 1468640 2009-10-26 10:16 wubi.exe
    Perhaps I'm missing something.   Thanks for the help.

  • Can't mount NFS share via GUI

    Mac OS X 10.8.2
    MacBookPro5,3
    Hello,
    I've recently upgraded to OS X 10.8.2 and am having great difficulty in mounting my NFS shares via the OSX GUI. This worked fine at OS X 10.6.
    My aim is to provide an automount type of setup so that less experienced users don't have to worry about the command line.
    Can someone please point me in the right direction here?
    This is what I've tried to date.
    My NFS service is hosted on my Debian server. It supports NFS v4. The service is working and stable and is used routinely with Ubuntu clients. It has also worked with OS X 10.6 clients in the past, but not with OS X 10.7 clients.
    To date I have tried the following options:
    Mount via finder: Connect to server option using syntax: nfs://<user>@<server>/<share>
    setting up autofs using the instructions from pmbuko
    using the command line to mount the share.
    The first option failed repeatedly.  I did find that it would eventually work, though only after I'd manually mounted the share at the command line.
    I have not been able to get the second option to work.
    I initiate autofs using the command 'automount -vc' and see that the connection is recognised
    when I attempt to cd into a directory below the mount point, I eventually get the message 'Connection Refused'. 
    when I check my Debian logs, I find that the NFS service had actually received an authenticated mount request from the Mac.
    when I check my Mac Console logs, I see an error:kernel: nfs_connect: socket error 61 for <server>/<share>
    I was able to get the third option working, but only after using the '-o resvport' option.
    'Something' does appear to be broken with OS X 10.8.2  as an NFS client.
    Any thoughts?

    I have found a work around that meets my imediate needs, though it doesn't allow me to use autofs functionality.
    The work around uses the traditional Unix/Linux approach of automatically mounting a file system or NFS share via fstab at boot time. OS X 10.8 still supports fstab, even though the file is not included in the default installation.
    Once mounted, the NFS share appears as if it is part of the normal file system.
    The following is only intended for people confident in Unix or Linux systems administration and in using a shell environment via the command line. Do not attempt this if you do not have these skills.
    To set up for fstab, do the following within a terminal session:
    create an empty directory in your file system that you can use as your mount point for your NFS share:
    sudo mkdir /data/share
    sudo chown root:wheel /data/share
    using your favourite editor, create the fstab file (in a terminal type 'man fstab' for details)
    sudo vi /etc/fstab
    add similar to the following to /etc/fstab and then save and exit, substituting your own values where appropriate
    # My NFS share
    <your-server>:/<your-share> /data/share nfs  resvport,rw,hard,intr 0 0
    sudo chown root:wheel /etc/fstab
    Please note: you may not need the resvport option in the fstab line above. It will depend on your NFS server's requirements.
    Once you have done this, reboot your Mac and your NFS share should be mounted at the mount point that you defined.
    If not, check your logs to see what went wrong.

  • Anybody using Epson 4490 scanner w/ Arch?

    Hi, folks--
    I need a good but reasonably priced photo scanner that works with Linux. I am finding that the choices are quite limited, but the Epson 4490 looks like a possibility. However, it requires the 3rd-party iscan driver to work with any Linux distro; the company that develops that driver tests a number of Linux distros, but Arch is not on their list. So, I'm wondering, does anybody use this scanner with Arch? Any voodoo required to make it work?
    BTW, let's please not talk about Wine or any other Windows-based solution. I do need to scan, and will do what I have to to make it work, but any non-pure-Linux approach is a last resort. I would be open to suggestions of other scanners, though.
    TIA for your thoughts.

    Read this thread, especially the post by rbmorse:
    http://ubuntuforums.org/archive/index.php/t-124331.html

  • IVPN on non OSX Server, can't mount volumes remotely via VPN

    I recently got iPVN to create a VPN to my home network. My router simply couldn't be used as an end-point.
    I have successfully installed it, and it does allow me to connect to my home network remotely. The problem is, whenever I try to mount a volume from a machine within my home network, I am prompted for a userid/password. My userid/password doesn't work.
    Setup:
    Home network using private Class C (192.168.1.x). 2009 MacMini is VPN server, and address is manually assigned for this machine (other machines within home network use router as DHCP server). I have forwarded ports 1701, 4500 and 500 (per iVPN instructions) for an L2TP VPN. UDP packets only, and all of these ports are forwarded to the MacMini and it's manually assigned address. My router is configured to use DynDNS if it's address changes, and that works successfully as well (using other services directly to the same MacMini, etc. that DO NOT rely on the VPN).
    I can successfully connect to the VPN, and ping machines within the home network successfully. However, I do not see any of the machines via Bonjour (I understand this is an issue with Bonjour and generally all VPNs). So, once connected to the VPN, I try to mount a volume that is shared on the MacMini. I can do this with either form:
    afp://192.168.1.x/<volumename> or afp://<machinename>/<volumename> (after setting machine name up in /etc/hosts).
    I'm fairly certain I'm getting through, and a mount is attempted, and asks for a userid/password. Same as normal. However, entering my username/password won't let me mount the drive. I keep getting errors indicating the username/password is incorrect, which I know is not the case.
    I have tried this with the MacMini firewall on (allowing shared service), and I have tried it with the MacMini firewall off.
    What am I missing here? Some additional port that should be forwarded? Open it up for TCP as well as UDP?

    I have found a work around that meets my imediate needs, though it doesn't allow me to use autofs functionality.
    The work around uses the traditional Unix/Linux approach of automatically mounting a file system or NFS share via fstab at boot time. OS X 10.8 still supports fstab, even though the file is not included in the default installation.
    Once mounted, the NFS share appears as if it is part of the normal file system.
    The following is only intended for people confident in Unix or Linux systems administration and in using a shell environment via the command line. Do not attempt this if you do not have these skills.
    To set up for fstab, do the following within a terminal session:
    create an empty directory in your file system that you can use as your mount point for your NFS share:
    sudo mkdir /data/share
    sudo chown root:wheel /data/share
    using your favourite editor, create the fstab file (in a terminal type 'man fstab' for details)
    sudo vi /etc/fstab
    add similar to the following to /etc/fstab and then save and exit, substituting your own values where appropriate
    # My NFS share
    <your-server>:/<your-share> /data/share nfs  resvport,rw,hard,intr 0 0
    sudo chown root:wheel /etc/fstab
    Please note: you may not need the resvport option in the fstab line above. It will depend on your NFS server's requirements.
    Once you have done this, reboot your Mac and your NFS share should be mounted at the mount point that you defined.
    If not, check your logs to see what went wrong.

  • Linux on my X220T (and why it failed)

    I’m sorry but this is going to be a long post but I have seen so many posts out there from people in my position - making an attempt to migrate from Windows to Linux - that I felt compelled to share my experiences. This is not a Linux bashing post either. Like UFOs, I want to believe. I just haven’t seen the light yet so if there are any Linux evangelists out there who have got Linux working on their X220T then I would *love* to hear from you
    Background and reasons for change:
    I am not your ordinary Windows user. I work in IT and I’ve been working with Windows since the days of v2 (yes I’m that old) running on Dos. I’m comfortable with it. Because of my age I’m also comfortable with the command line. I’ve worked with Xenix (a variant of the original Unix) and have a grasp of the fundamentals. Now I’m all grown up and an IT consultant I wanted to ‘round out’ my understanding of my business by getting to grips with Linux in order to write code. I understand it’s very different to the nice little bubble of Visual Studio where everything happens around you. I’ve yet to find out Sure I can produce a virtual machine and learn in there but wanted to immerse myself in it all so decided to convert my X220T. This little beauty is not my main work computer so I could sacrifice the contents. If your X220T is your only machine and you need it for serious stuff, think carefully before going ahead.
    Starting point:
    My X220T was pretty much out-of-the-box Windows 7. It was working fine, but had the odd glitch. Wouldn’t hibernate properly (although it did before an ‘upgrade’ screwed it up) and the mouse kept losing its settings despite following all the advice, upgrading, hacking etc to fix it. I also had Windows 8 preview on the ‘Q’ drive and was liking that but of course it’s not really ready to go yet.
    My choice was Linux Mint with the KDE desktop. Did a bit of digging. Seemed to do the job. So I took several backups, trashed the drive and installed it.
    My previous experiences with Linux have always been a battle to get the OS to see certain devices. Wireless cards never used to work. Peripherals failing. Not resuming from hibernate. That kind of thing. This time it was flawless. It simply installed. Everything appeared to work! Fantastic!! Of course it wasn’t all there yet. But because my internet access was up and running (had always been an issue before) I was a happy man.
    Then three things happened almost simultaneously.
    I wanted to read an eBook and the screen wouldn’t rotate
    I couldn’t log on using my fingerprint reader
    My fan wouldn’t shut up
    So thought I would tackle the first issue. KDE supports a tool that pops a nice little icon on to your task bar to allow screen rotation. Didn’t work. What it did do was install the Wacom drivers to manage the touch screen and it would re-orientate the mouse ‘as if’ the screen had rotated, but the display itself was in portrait mode. So spent two evenings after work working out how to make this happen. In the end I wrote two shell scripts to rotate the screen AND to set the Wacom drivers to orientate the mouse and stylus properly. Job done! Felt pleased with myself. I was cross that the KDE interface screen button thingy didn’t work properly but that’s life. I had learned something. Two dos-like icons on my task bar flipped my screen (albeit slowly) from landscape to portrait and back again.
    Meanwhile, I’m sitting in my conservatory (no power) and watching my battery disappear in about two hours. Under windows, my usage pattern gave me at least five hours before a re-charge. And that pesky fan didn’t run once! Peace!! But not with Linux. It was annoying so thought I would tackle that next. Everyone uses their machine differently so since power consumption is quite subjective I thought if I fixed this I could move on to other things and then ‘suddenly notice’ that my battery is still powering my baby after four or five hours.
    After research and digging into a cpu frequency daemon (background process) I realised that this was the wrong line of attack. That took another two evenings of work. The Linux Mint kernel doesn’t support this. More research suggested that this was an old/different methodology and the approach was to use cpu ‘governers’ to control cpu frequency switching. The governers have names like ‘ondemand’ and ‘conservative’ and as you might guess, the conservative one holds the processor speed down to reduce power consumption. You may assume dear reader that I had done all the other stuff. Turning off bluetooth only happened in software and I gave up before researching that. It may be possible to turn it off in hardware via the operating system but didn’t get that far. Screen brightness, wireless etc. Typically when I read a book I flick the hardware radio-off switch on the side which of course turns off bluetooth and wireless, so they were taken out of the equation in terms of power consumption.
    After another evening of digging I managed to discover how to instruct the machine to use the ‘conservative’ governor. By now I’m starting to get a bit fed up. My philosophy was partly to learn what it was like to live in the world of Linux, but mostly to get to grips with the C++ compilers, possibly mono (A windows-like development environment) and Apache (system for hosting web sites) but hadn’t got beyond the foibles of the operating system. Finally got the conservative governor in place, rotated my screen (still working!) and settled down to a good read (purely for testing purposes of course
    Within five minutes, on the came the pesky fan. Battery gone in about three hours. This had me seriously pissed off by now. But still wanted to battle on. Thought I would tackle the fingerprint reader next. Found a driver but it didn’t work. I could register a fingerprint but when it came to save the results it died. Even as the godlike super user it failed.
    Then I found another gui based app and that one worked. Well, it worked nicely in-system. Anything that needed elevated privileges it would work for. I just couldn’t use it to log in. When the laptop was in tablet mode I couldn’t authenticate with my fingerprint reader and there was no on-screen keyboard to use as an alternative.
    And it was all these little things that eventually drove me screaming back towards Windows. I’m now running Windows 8 CP as my main desktop. It’s incomplete and has its own set of foibles, but by installing some of the drivers that Lenovo supply for Windows 7 it is perfectly usable.
    The screen rotates out of the box
    The buttons along the bottom of the screen work to rotate the screen (never did get that working in Linux but it was on my list
    Power consumption is back to being pretty good for a laptop rather than just average
    I can turn my bluetooth off at the hardware level but leave my wireless running so that I can browse the internet without hammering my battery too much (using the Lenovo on-screen utility form Windows7)
    I can logon with my fingerprint reader and when it fails (I get it wrong three times) I can revert to an on-screen keyboard to get me out of trouble without having to switch to desktop mode to do it.
    I know they are small things but they are now what I am used to and what I expect from my operating system so why should I do without them?
    My feeling as I sit here writing is that Linux is great. Don’t get me wrong here. I still love it and intend to explore further, but unlike Windows there is a learning curve that you HAVE to climb. You have no choice. When I come home at the end of the day, sure I want to play with my little Lenovo and have some fun. But then I want to relax. Do a bit of surfing, read my ebooks and generally do stuff that the operating system is intended to support. Instead the operating system got in the way of my user experience rather than supporting my user experience. The problem for me is that wihlst I can produce a Linux machine in vmWare or VirtualBox, the driver woes I’ve just described are hidden from you because those virtual worlds either abstract the problem away or don’t port-over the hardware from the host that you want to explore the problems with. The only solution is to buy another X220T to play with and that’s not worth it for me.
    I also think that my relatively large understanding of Windows frustrates my experience of because I am now a novice with the computer which I’m definitely not used to and that of course skews my perception.
    So if there are any Linux superheroes out there who have solved all the above issues and can lead me into the glorious sunshine of developing in the wonderful world of Linux then please talk to me. And for the rest of you guys in my position for whom this has struck a chord, if you want to play, I’m sure the results are worth it but prepare to be frustrated!!

    Hi all. I must be in league with the devil as my lucky number is 13. When I saw Galloping Gerbil or Raring Rhinocerous or whatever the **bleep** thing is called I also saw v13.04 and thought that the time had come to go again!
    So it's about a year on now. Two important things have happened. The first is that my trusty old X220T is now no longer my primary machine so I can afford to lose it to experimentation for a while. The second is that the huge behemoth that is Linux is rolling over the bugs and niggles that sent me screaming back to Windows all those months ago.
    So I've tried again with Raring Ringtail v13.04 and right now I feel as if I've come home! It's still not right but it's pretty close! More importantly, I fee that I'm no longer in the minority in wanting to get this to work right. There is this big push out there towards touch screen so people are spending time on this and wanting their software to be touch screen friendly so it is!
    Before I go on, I was rather shocked when I did my pre-13.040-install research to find this post top of the google list on linux on x220! I'm guessing that my thoughts must parallel a lot of other people thinking about making the jump. So to that end, here's some thinking.
    13.04 is close. Really close to being a very serious competitor to Windows. My view is that Linux is about there now. The X220T is a complex beast to support. it has touch, pen, fingerprint readers, rotating screens etc. And it all works pretty well. I can do a sudo apt-get install to make the fingerprint reader work. And it DOES work. Reliably. I still have issues rotating the screen but I've learned enough now to knock up a simple bash script that will do it for me. AND (this is where the Linux philosophy works) I have written the script to suit me. I like to hold the battery unit in my left hand and hold my laptop in portrait mode to read books/browse the internet. Then switch to normal orientation to type emails etc. The script only toggles between normal and anti-clockwise and back again. Works for me.
    The issue with Linux was more that it was a philosophy than an operating system. You don't just "use" it. You immerse yourself in it. That made it geeky and non mainstream. You can make it sit up and do stuff that suited you exactly if you were prepared to put the time in. The issue was that until now it didn't do the basics reliably enough to suit everyone. I used to read a lot of stories about sons/friends putting Linux on to Mums/Dads/Grans laptop and it working beautifully. Linux is very very good at this. It just works. But getting it there was a right pain unless you were lucky. Now however that out-of-the-box functionality is really really close. To the point at which Tracey from Essex (forgive me Tracey!) can stick the CD in and expect the same functionality from Linux that she could get from Windows without having to sweet talk that geeky bloke that she knows has a crush on her to come in and sort it all out
    Once you get past that bit then you end up in this little wonderful world. Without too much effort courtesy of all those hard-working ordinary people out there, I have a machine that will do most of what I want without tweaks and pokes that take days to research. Now I can browse, read my books, play the odd game and "ignore" the operating system until such times as I choose to tackle the odd tweak. On my relatively small screen for example I want hide the Unity launch bar thingy. However if I do this I can't get it back via the touch interface. Enter Ginn! I have yet to play with tihs but I can configure multi-touch gestures to "do stuff" like making the launcher appear with two finger gestures (!) and that little nugget of configuration pleasure is waiting in the wings for when I get bored reading the news or playing silly games. My operating system has now become a toy, a tool and a learning centre. I can now pursue my long term dream (okay I have modest dreams!) of being able to develop AJAX based web sites using WCF in Mono running under Apache. That means I have all the fun of learning how to use Apache, and working out how to make WCF code in Mono. These things are easy for me under Windows and IIS but how you do it in Linux is a new and exciting challenge! Yes I truly am that boring!
    I wish I could change the title of my original post because Linux is coming of age. Windows had better watch out.

  • Unable to launch application on Linux machine

    Hi,
    We have a Java based product developed as desktop application. This product has a tree structure built-in. and while connecting to few of the nodes, we are getting the following error: "*Cannot write XdndAware property*".
    Note:
    1. We are running the application on a Linux machine.
    2. We are using JNLP to launch the application.
    3. Only few nodes are causing this issue.
    4. Tried putting -DsuppressSwingDropSupport=true in JNLP file, but no progress.
    5. This happens on JDK1.6.0_23 and above
    Can someone help us to resolve this issue.
    Thank you.
    Regards,
    KNP

    Let me explain my current requirement.
    1. All the client jars should be downloaded every time I click a link (as of now its a JNLP link, but this can change).
    2. And this should be platform independent
    3. I stated in the earlier description I should be able to pass arguments (suppressSwingDropSupport, etc) to VM to resolve the actual issue.
    Can someone please suggest any other approach?
    I have one more generic question: Can I write my own JNLP defining XSD & DTD, so that it can accept all the arguments whichever I can pass to the VM? If so, how to do this?
    Please respond

  • OBIEE 10g to 11g Migration on LINUX Machine

    Hi All,
    I want to Migrate OBIEE 10g (Windows Environment with SQL Server DB) to OBIEE 11g on LINUX Environment with Oracle DB.
    If anybody know this can you please help me how to do ?Thnaks in Advance.
    As per my Knowledge i know upto this .... "first we need to deploy RPD and WEBCatalog files in to New(OBIEE11g) system and we have to test RPD and WEBCatalog files,Whether these two are working fine or not? Because in OBIEE 10g we have OC4J Server,But in OBIEE 11g Architecture wise it's entirely Different here we have OBIEE WEBLOGIC Server. We have to Deploy RPD in WEBCatlog files in to WEBLogic server. And If any changes have to do in Securities and Variables we need to make changes in that after Migration".
    Regards,
    Prasad.

    Prasad,
    Refer the tutorial here..http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm#t4s3
    Your approach is correct.

  • REDHAT LINUX 7.3 on nForce based systems - An installation guide.

    INSTALLING REDHAT LINUX 7.3 ON NFORCE BASED SYSTEMS.
    A) Preface
    I'm a Linux newbie, just sharing my experience with installing linux on nforce.
    in my opinion Linux is a powerful but still a nascent operating system (in terms of user friendliness atleast!). many features are extremely 'release' and 'version' dependent.  this means that, what works in redhat might not work in mandrake or what works in redhat 7.3 might not work in redhat 7.1 or likewise...
    the steps i'm listing below just reflects how i went about installing RH 7.3 on my machine (K7N420D). it MAY not work for other versions or releases.
    B) BIOS SETTINGS
    1. I recommend, PnP disabled, ACPI/APIC disabled.
    for Mandrake 8.2 install on some machines (mine included), i suggest disabling audio and network in the bios till you get a stable level 3 (console without X windows) or level 5 install. for some reason, sometimes, on some boards,  Mandrake 8.2 hangs when probing audio and lan during boot.
    C) PREPARING TO INSTALL
    1. i suggest you get the three iso images from the internet and burn them into installation disks. though there are other ways of installing, this is the simplest way of doing it.
    2. if you have windows installed already, make sure you have a windows boot floppy in case of boot problems, you can also make one for linux during installation.
    3. using windows or fdisk strip off a sufficient chunk of hard disk space from an existing partition if you don't have a free partition. you need not create any partitions, just the non-allocated space would do. (as red hat can beautifully split this partition into /boot, / & swap partitions!)
    4. i recommend using GRUB (GRand Unified Boot-loader) instead of LILO for boot management. if you prefer the same way, get good documentation/how-to for grub from the net. this will be handy if you mess up your boot partition and end up in a grub prompt during boot.
    5. goto nvidia's drivers page and get appropriate drivers. i always recommend tar balls or src.rpm files instead of pre-compiled rpms. if you are using EXACT same version of the linux release as mentioned in the drivers page you can use rpms. If you wish to upgrade your kernel or use a different version of linux then make sure you have tar balls or source rpm files. make sure you also print the installation instructions from the same page.
    6. the drivers you need are
    a. NVIDIA_nforce-1.xxxx. - you need this one for audio & lan. (found in nforce link in drivers menu in nvidia site with an instruction manual)
    b. NVIDIA_kernel-xxxx AND NVIDIA_GLX-xxxx- both these for Graphics in Xwindows. these two drivers should be exactly matched. i suggest you download all of them along with a files named NVchooser.sh found on the same page. NVchooser will tell you which pair to install for your linux kernel version and CPU.
    D) LINUX INSTALLATION
    1. boot from 1st installation disk that you made. go through the GUI installer and choose automatic partitioning, it will take you to the Disk Druid and you can select the partition in which you wanna install linux. if the partition you choose is unallocated, most of the times didk druid will make three patrtions on its own, one is /boot (boot partion), /swap (partition for swap, similar to ramdisk) and / (root partition). all the three mount-points may be allocated on the same partition too.
    2. Choose GRUB (if you prefer) as boot loader and set Linux as primary boot OS and this page would've detected windows if you've already (it may appear as DOS). Choose "MBR" to install GrUB. If you get any warning ignore it. IMPORTANT: If you have NTFS partition for windows and you had windows as primary OS, there is a reported problem that says, in some versions of the linux installer, choosing MBR to install GRUB makes it hard to boot into windows. i haven't tried that option yet as i don't have a NTFS partition. If you have an NTFS partition, you may prefer to choose the other option to install GRUB or you may choose to install it later. in either case make sure you have a boot floppy to get you into linux or windows, whichever one you want.
    3. choose automatic install if you don't want to control which packages you want to install. else choose expert installation and proceed with it.
    4. when prompted to check the packages you want to install, choose "development tools" or something similar without fail. This is for installing a C compiler which is a must have for some driver installations. (this also installs perl and other dev tools, if you're an 'expert', there's an option in this page to custom select modules)
    5. somewhere you'll be asked to provide a root password, in the same page there'll be a provision to add users other than root. create atleast one user other than root at this time.
    4. somewhere you'll be shown a list of video adapters with NVIDIA Geforce 2 generic driver already highlighted. Below this screen you'll see a "Skip X install" or something similar. CHECK THIS TAB and this will NOT install the generic driver for your integrated GPU and also will not configure the GUI environment for Linux. This makes your video configuration a little easier.
    5. now linux will install, get configured and will ask if you wanna create a boot floppy. make one just in case you
    6. RH 7.3 will not recognize your APU and integrated LAN. you can install the drivers for this later.
    7. After installation boot into Linux, if you just followed the steps above you'll nicely end up in level 3 console!
    E) INSTALLING DRIVERS
    1. Assuming you got all the drivers in CD/floppy, login as 'user', type command "su" (super user) supply root password, now you are logged in as root. read the installation manual for the NVIDIA drivers and install NVIDIA_nforce-1.xxxx drivers for audio/LAN. do these series of steps from the console prompt,
    #vi /etc/modules.conf
    press INSERT key, add the following lines,
    alias eth0 mcpeth
    alias sound-slot-1 i810_audio
    alias usb-interface usb-ohci
    press ESC, (Shift) colon, wq and Enter.
    This will save the changes you made.
    2. Now install the NVIDIA_kernel-xxxx AND NVIDIA_GLX-xxxx- drivers as per instructions. follow the steps below.
    #XConfigurator
    Choose settings that are relevant to the monitor you use and mode supported. Choose custom configuration wherever possible. If your monitor is not listed, choose 'custom' all the way through and provide hardware details such as horiz/vert freq range, video memory and clock settings (choose 'recommended').
    DO NOT LET THE XCONFIGURATOR PROBE ANYTHING. sometimes this might cause a hang that is not necessary at all.
    select all videomodes and color depths that you think your monitor will support and exit XConfigurator without any probing.
    3.  Now at the prompt do the following,
    #vi /etc/X11/XF86Config-4
    Press INSERT and make following changes.
    replace line
    Driver "nv"  
    with
    Driver "nvidia"
    In the Module section, make sure you have:
            Load   "glx"
    Remove the following lines: (or put a hash before)
            Load  "dri"
            Load  "GLcore"
    and the whole
    Section "DRI" (last three lines usually, DRI may be in lower case usually)
    Press Esc, (Shift) colon, wq, Enter to save and exit.
    4. using vi make sure you have these lines in /etc/modules.conf file
    alias char-major-195 NVdriver
    5. edit /etc/rc.d/rc.local and insert
    /sbin/modprobe nvaudio
    /sbin/modprobe nvnet
    save and exit. ( this is a crude way of loading modules but it works though!)
    6. Type "reboot" at prompt and reboot your system.
    7. get into bios and load original settings. (get back ACPI if you have windows, enable PnP OS etc)
    8. During restart linux may get you into the kudzu installer to install network drivers/audio, ignore this.
    9. login as "user" and type "startx" from console, your GUI should start smooth and you'll have video, sound, USB, LAN working (you need to fiddle a little bit more to get things work perfect) !
    10. There is extensive documentation found in the internet on these topics, have fun exploring them.
    F) TWEAKING YOUR HARD DRIVE
    most of the modern hard drives support UDMA transfers and usually linux is pretty much conservative on this option. so you might want to force linux to use UDMA. the following discussion assumes that your hard drive is /dev/hda, change it to hdb, hdc etc as per your setup.
    CAUTION: The 'hdparm' utility described here is a very powerful and dangerous if used improperly. USING hdparm IMPROPERLY MIGHT CORRUPT YOUR PARTITIONS AND RESULT IN SEVERE DATA LOSS. hdparm works with IDE drives. i'm not sure how it works on SCSI drives.
    @ console,
    1. type "man hdparm" and read through the hdparm manual atleast twice before you understand what it can do. THIS IS A MUST.
    2. login as root or get into super user mode and try the following. all commands are shown after #
    3. Benchmark the hard drive
    # /sbin/hdparm -t -T /dev/hda
    this should spit out the transfer rate both cached and sustained. note this value. if these values are close to what you expect out of your drive, you are OK. you may get out of further adventures! if the transfer rates are horrible like 3.5 Mbps etc (it was on my seagate ata IV drive!), then proceed with the tweaks. the golden rule is, after each tweak, run the benchmark and record your transfer rate. if there is no significant improvement, revert back to the default settings.
    4. # /sbin/hdparm -i /dev/hda
    note down MaxMultSect, MultSect, Modes supported : PIO/DMA, especially the mode with a 'star' in front of it. (prefered mode)
    5. 32 bit I/O : to enable 32 bit I/O over the PCI bus
    # /sbin/hdparm -c1 /dev/hda
    this usually doubles your transfer rate if the drive supports. you may need to use -c3 for some chipsets.
    6. Enable DMA and set DMA mode
    if your drive supports DMA find out the prefered DMA mode using -i option.
    # /sbin/hdparm -d1 -Xab /dev/hda, where
    ab=64 + uDMA mode number (for eg. 66 for UDMA 2)
    ab=32 + DMA mode number (for multi-word DMA mode)
    you might need to prepare the chipset to enable DMA but on most of the modern hard dirves this works. refer to the "man hdparm" for details. beware, the options to 'prepare' the chipset for DMA should be used with EXTREME caution. if you do not know what you are doing, don't try it.
    7. To set multiple sector mode I/O,
    # /sbin/hdparm -m XX /dev/hda
    where XX is the MaxMultSect value obtained using -i option. if the MaxSect is already set to this value, you need not tweak this.
    after all these tweaks run the benchmark atleast three times consecutively and average the transfer rates. make sure you don't hear grinding noises in the hard drive. use these tweaks a couple of times manually and if verything appears to be working fine, add the necessary commands to the rc.local script to execute them automatically during  start up.
    G) FINAL WORDS
    I assumed that you're a total 'newbie' to linux when writing this so i followed a conservative approach. most of the things that i described can be done in many ways, it's up to you to explore them! as usual, there MIGHT be typos and other serious errors in this guide. also the driver files that i might have mentioned here are the ones that were available when i wrote this. so you might wanna try their latest equivalents. i'm open to all healthy criticism and suggestions. when i installed linux on my nforce board, i was badly looking for an article like this on the net. i missed one, if it exists at all. so am i writing this. i hope you'll get benefitted by this in some way.
    -Venk@

    Venkat,
    Thanks for this really really amazingly accurate and exhaustive post that helped me A LOT to install linux on my machine!!! Otherwise, I think I would still be hanging with a mandrake 8.2 trying to load sound...
    My system is now fully functional but, (yes, there is a little but) I was not able to make the LAN function properly. When booting, while linux tries to load the ethernet module, I get something like:
    'mcpeth device does not seem to be present, delaying eth0 initialiation'. Then, I open an X session, I try to use the network configurator, the ethernet device is there but when trying to activate, it fails... I swear I enabled the LAN in my BIOS.
    I also tried to replace 'alias eth0 mcpeth' with 'alias eth0 nvnet' in /etc/modules.conf after reading the installation notes of NVIDIA drivers. I get a slighty different result: my boot error is now 'failed to load module'.
    It is a shame I have to boot back to Windows to use my DSL connection. I think i need some insights. It will be greatly appreciated!
    Thanks,
    Chouch
    >I'm a Linux newbie, just sharing my experience with
    >installing linux on nforce.
    Not bad for a Newbie...  

  • Oracle9i Rel2 installation fails on Redhat linux 7.3

    Hello there.
    My m/c is Pentium III 500MHz m/c with 320MB physical RAM and it has Redhat Linux 7.3 installed.
    I'm trying to install oracle 9i and it fails in DB creation. The "dbca" shows an error message
    "ORA-27123: unable to attach to shared memory segment" when it is at 51% through.
    I have configured 1.9GB of swap space. The "ipcs" command do show some shared memory allocation under "oracle" user id with "0777" permission. I can't really figure where to start in analysing this problem. Your inputs are very much appreciated.
    Thank you.
    Vimala.
    31-Aug-2002

    You need to know that while installing Oracle software itself you must not invoke any wizard like adjusting Oracle network or creating databases , just finish of the Installation , restart machine and start configuring the network and databases , this approach was very successfull with Servers who have less than 1 G Ram.
    I have installed 9i R2 over 256M ram over Redhat 7.3 , no Problem JUST , if this problems happens after installing the Oracle software itself , it is reported by Oracle that it has bug in this version that happens for instance when you open a shell window , startup a database and exit SQL+ , when trying to shut it down from the same window it returns the same stated error before , I managed to solve it by ( from inside SQL+ ) giving :
    !ipcs oracle
    Then
    !ipcrm ****
    **** = the id numbers of Oracle processes for shared memory realm.
    Then exit SQl+ , open another shell window , start SQL+ and we are back on business again.
    This is all instead of resatrting the server.

  • [Guide]Making the Logitech G510 Work On Linux!

    Update April 23, 2015: I've got a new keyboard (Corsair K95) so I personally probably won't touch this code ever again if I can help it, however it should be working just fine in it's current state without my dabbling, I've set the code up so that the macros are recorded to script files in /usr/share/g15daemon/macros/ with a provided example script, it should be easy enough to read or modify, and if desired the scripts can be replaced by custom executables. When the buttons on the keyboard are pressed they execute these scripts with a command line argument corresponding to the current M-Key state (so we have different functions for M1, M2 and M3 keys), but I thought this was the easiest and most versatile approach, I feel I've got a lot more freedom to customize the macro keys than I ever did in windows this way. As for the MR Key, it is functioning in that it will record a macro (through Xev) and output it to a text file: /usr/share/g15daemon/macros/Macros by running the MacroRecord script located at /usr/share/g15daemon/macros/MacroRecord, you need to ensure that these scripts are made executable when you install this (unless you use my custom pkgbuild on arch which does this automatically) to use these recorded Macros you just have to copy them over to one of the other scripts (for the respective key you wish to use). The Macro Recording script works for recording most normal macros, but if you try to break it, you will (You should be able to use up to 4 modifier keys on one button press (for a total of 5 buttons held down) without running into any problems, as a limitation) but this script is not complex so it should be easy for anyone using it to open it up and try to improve it or increase the amount of modifier keys supported per macro.
    I was working on a Qt5 application that would allow these files to be edited through a Qt based GUI, which also shows the macros recorded by MR for easily copying them over and saving the file. Everything is done except the save function, if someone asks me in a message, I will finish this application for them or send them the source code once I get it.
    Latest Source (Comes with Arch PKGBUILDs, install with makepkg -i)
    Older Source (Before I coded in the MR key)
    Source of Qt GUI Front-End (I never finished this program, you need qt-creator to open these source files and finish them yourself. Without this program you can just manually edit the files in /usr/share/g15daemon/macros as described below, the only parts that haven't been coded in yet are the save code, and the test button code. It should be easy to do though, there is example code in the saveFiles function which you can use to finish it (comment this function out if you want to compile it before you finish up coding it, this function breaks the code since it is not written in functional code) if you just adjust it based on the loadFiles function that is above it which does work for loading all the files, it should be pretty easy to finish this program up. If you finish coding it, feel free to send me a message so that I can link to your complete sources instead. These sources I'm releasing in public domain (do whatever you want with them) but Qt5 is LGPL 3.0 licensed.)
    There is now a wiki page for this, but it's content is slightly different from this thread and doesn't offer much support for other distributions.
    I have a logitech G510 keyboard, and 2 years back I spent about a week applying several patches I had scoured from around the net as well as making my own modifications as needed to make this work with the old g15daemon drivers (as in, I forked g15daemon, without actually changing the programs name). An alternative to this method is using the gnome15 project (just as g15daemon it is no longer being developed) but I had severe (and quite unacceptable) input lag when I used gnome 15 as well as other major issues and as such I vastly prefer my own method. (Besides I worked hard to make this work, I was toying with source code in a programming language I am not really familiar with (C) and did so non-stop for a week, it'd be a total waste if it wasn't better than the alternative!)
    And on february 11th 2015 I made yet another update to these drivers that made them significantly easier to use (before this time, the source code had to be manually edited and the drivers had to be then recompiled ino rder to edit the functionality of the G-Keys (not to mention the source code was an ugly mess because of this roundabout approach) this had to be done because the g15macro part of g15daemon never worked well with this keyboard, so I decided to hardcode the keys into the drivers as a temporary solution, now I've found a more permanent solution which is redirecting the keypresses to bash scripts. One script file for each button, I will explain how to do this later on.
    Here is the  original thread I made on this if anyone wants to see the ugly mess I went through to get here, luckily that's far behind me now and the code is getting more and more mature over time as I fix it little by little.
    How to do it:
    What you will need to do is apply these patches for libg15 and g15daemon. (If you want to do it the hard way, use the older Hardcode Patch but I don't recommend it unless you really know that you want it, and know why you want it.)
    This can be done on any distro I would assume, for gentoo refer to this thread. To get the sources Download this (latest source) and extract it with unrar, (on arch use makepkg -i to install) in the following order: "libg15 -> libg15render -> g15daemon -> g15stats" (Note: You can edit the macros in the macros folder before installing g15daemon. If you are not on arch you need to manually copy the macros folder to /usr/share/g15daemon/macros/, otherwise the pkgbuild will do it for you. If you are running in another distro you can delete the PKGBUILD file in the folders. I included the unmodified libg15render and g15stats too for the sake of convenience, and as a safety net if they disappear off the face of the internet, which is what they seem to be about to do. If you do not feel like trusting the sources I provided then fear not! the ones I provided are just the original sources (md5sum should match with those found there) (as development for the project seems to have been dropped and these were the final versions ever made) but I assure you, the sources I provided are the original ones downloaded straight from sourceforge. If you are on arch you can use ABS to get the sources from the official repositories and then replace the PKGBUILDs with the ones in my rar (or change them yourself, see wiki). If you want to download your own sources (remember to get my patches too!) then here is an alternative download for the default macros.
    Note: In the arch package there were other patches(config-write, recv-oob-answer and uinput) in the package in the official repositories, I added these three to my own file to avoid clutter, the first two are the first two entries of my file, the third is at line 40-71 (two entries) as a part of the same file where I coded in the G-Keys. Depending on your distro and how you get your hands on the sources you may have to adjust this as these patches may already have been applied for you (meaning mine will fail to patch because of mismatching sources). I have no idea what these patches are actually for (would be nice to know) but I imagine they're there for a reason and as such stuck with them.
    For other distros figure out how to compile packages from the sources (sorry Arch and Gentoo are the only distros I really use so I can't help with others, but I assure you this can be done on all distros. If it comes down to it ask on their forums for help!)
    In the libg15 patch I disabled support for other keyboard models in the first few lines (you will see which if you read the patch) as I suspect many of the changes made might break support for the other devices, but if you want to take your chances just remove the minus sign in front of the device you want to use and hope for the best. If you have a keyboard that was already supported by these drivers, the biggest benefit of getting my version working would be the smoother G-Key functions (since they aren't run through a third party program like g15macro, it's bound to be a little faster and less prone to bugs.) also if you have a G510s and want to try these drivers on that board, you will have to add your keyboards id into this section (or replace the one I added with the appropriate ID for your board) using lsusb to find the right values.
    I couldn't get g15macro to work properly with my keyboard and noticed several issues with it (it seemed like it was underdeveloped to me) so my solution to that problem was originally to hardcode the G-key functionalities into the base drivers; But later on I realized I could instead redirect the code to script files that I would create outside of the install, to avoid the load of pain that comes with hardcoding something you may frequently want to change. These drivers are run as root and as such you must be careful and use sudo where applicable to run the commands as your user rather than as root. By default all G-Key presses will be read as commands from the user with uid "#1000", which is in most cases the first user account created on the system. The bonus from this approach is that the G-Keys work much faster than they would using the g15macro and they are also much more customizable than they ever were in windows, the minus is that you need to know/learn bash/shell scripting in order to use it this way. That or find a way to edit the script files to be in a programming language you understand, but bash scripting is the most convenient since you get all the versatility of a terminal in your keyboard that way.
    To change the colors of your keyboard you need to edit the libg15.patch file below line 338 (//Set keyboard color based on M led state.) The code there uses the basic RGB format, and each M-Key has it's own line. The default is: Dark-ish Blue(M1/Fallback), Dark-ish Red(M2), Dark-ish Green(M3)
    To change the macros, you can (if you installed with my pkgbuild on arch) go to /usr/share/g15daemon/macros/ and within you will find 19 files, an "Example" file (this is like a backup, it's what can be used to reset files back to their defaults if you get lost.) The files are named after the keys they affect, each file has statements for M1, M2 and M3 and then a few extras for errors that uses libnotify for error messages. The default setup also uses libnotify to tell you which key was pressed, and which key was released. If you are not on arch or gentoo and could not install directly from my sources, you will need to either copy the files from my rar to "/usr/share/g15daemon/macros/" and edit them from there, or create them yourself from scratch on that path (the names of the scripts are G# where # is the number of the key, make sure that the files are executable with chmod +x if you are more advanced, you can edit the g15daemon.patch file if the location of the macros isn't to your liking and change the path to the scripts to something more convenient for you (e.g. ".../.config/g15daemon/")
    By default, the scripts will look something like this:
    #!/bin/sh
    declare -i mkey=$(( $2 + 1 ))
    declare -r key="G1"
    #M1
    if [[ "$1" == "on" && $2 -eq 0 ]]; then
    /usr/bin/notify-send $key: 'M'$mkey', state='$1
    elif [ $2 -eq 0 ]; then
    /usr/bin/notify-send $key: 'M'$mkey', state='$1
    fi
    #M2
    if [[ "$1" == "on" && $2 -eq 1 ]]; then
    /usr/bin/notify-send $key: 'M'$mkey', state='$1
    elif [ $2 -eq 1 ]; then
    /usr/bin/notify-send $key: 'M'$mkey', state='$1
    fi
    #M3
    if [[ "$1" == "on" && $2 -eq 2 ]]; then
    /usr/bin/notify-send $key: 'M'$mkey', state='$1
    elif [ $2 -eq 2 ]; then
    /usr/bin/notify-send $key: 'M'$mkey', state='$1
    fi
    #Else (Errors)
    #If there is no input
    if [[ -z "$@" ]]; then
    /usr/bin/notify-send $key": Error!" 'There was no input'
    fi
    #If M key state is out of range (less than zero or more than 2)
    if [[ $2 -lt 0 || $2 -gt 2 ]]; then
    /usr/bin/notify-send $key": Error!" 'There is no M'$mkey'! (State='$1')'
    fi
    #If the first input variable (on/off) is incorrect. This should never happen.
    if [[ -n "$1" && "$1" != "on" && "$1" != "off" ]]; then
    /usr/bin/notify-send $key": Warning!" '"'$1'" is not a valid state! (M'$mkey'), defaulting to "off".'
    fi
    And here is an example of how the M1-M3 keys could be edited in this file. The "if" statements are events that occur when you press down on the button, and the elif statements are for the key release.
    #M1
    if [[ "$1" == "on" && $2 -eq 0 ]]; then
    thunar /mnt/stash/movies & disown
    fi
    #^elif is not needed and can be erased for this command to avoid the notification of key-release. The & disown part is extremely important, if you forget to add this to the end of every line where you execute a program that will keep running after you release the button, you will not be able to use any G-Keys until you terminate the program. If you remember to add the & disown, everything will be fine.
    #M2
    if [[ "$1" == "on" && $2 -eq 1 ]]; then
    xdotool keydown Ctrl && xdotool keydown Page_Down
    elif [ $2 -eq 1 ]; then
    xdotool keyup Ctrl && xdotool keyup Page_Down
    fi
    #^The above executes the keyboard combo Ctrl+Page Down (Next Tab) and holds these buttons down until your key release is detected.
    #M3
    if [[ "$1" == "on" && $2 -eq 2 ]]; then
    xdotool keydown Super && xdotool keydown F1 && xdotool keyup Super && xdotool keyup F1
    fi
    #^The above is my keyboard shortcut for changing workspaces, (Meta + F1-F6), since I won't ever need to hold these buttons down, I set them up to press and release on keydown, with no need to detect the key release, this is good to do to avoid a bug I mention lower in the guide.
    That's the gist of it, all you need to know. You can test-fire the commands in your terminal before you add them to the files. Recompiling and re-installing the G15Daemon (at least on arch) will overwrite your existing macros in /usr/lib/g15daemon/macros. Last but not least, you should remember the sleep command (for example, to restart g15daemon, do g15daemon -k && sleep 5 && g15daemon this is how you can set up timed commands and macros on your G-Keys as well. I may later on develop a GUI front-end for editing the macros, and program the MR-key to work like it does on Windows, but right now I'm satisfied with what I've got, so that will have to wait.
    You need to know:
    -The g15daemon service should be started after X11/Xorg-Server is started or any commands that require X (like opening a folder, or graphical notifications) will not work. (You can either just wait till you log in and use xinitrc or an autostart script for your desktop environment to start the service, or you can set up a restart script which kills the original instance (g15daemon -k) and starts a new one, this may be good to know if you would like the service to be started on bootup so you wont have to look at white leds until you have logged in. You can use sudo to run these services as a user). You can also try to have the g15daemon initiate after your display manager loads. (For example make the initscript depend on kdm if you're using kde, I have not tried this though)
    Add this to the sudo configuration with visudo so you can run the g15daemon with sudo and no password (this should work on most distros, if not find the executable, could be in sbin (is on gentoo) like so: "/usr/sbin/g15daemon")
    ALL ALL = (root) NOPASSWD: /usr/bin/g15daemon
    (You can replace the first "ALL" with a username or % group if you want to limit the command to just one user)
    -I have not tested the headphone/mic plugs on the keyboard (please do comment your results if you try to use that)
    -This is not completely bug free.
    -There is no support for tracking launched/focused application and changing the M-Key mode depending on what you are doing (this would be useful though)
    -The MR key is not supported, but the LED works.
    Known Issues: (ordered by severity, if you want to contribute fixing these issues is the best thing you can do to help as I seem incapable of it)
    Sometimes the Key Release of G keys is not detected (this means if you have a key bound to the button that is held until the key is released, the release may not be detected properly. This only happens if you press the key quickly, not if you hold it for a short period before releasing it this is solved by either pressing the key again, or not relying on the key-release state, the latter is fairly easy to do as you can use "variables" and "if"s and "do/while" or "for" in C to set keys with toggle functions.
    Keypress detection for the G-Keys isn't 100% reliable, it will work completely fine 95% of the time or so, but sometimes (usually only if a G key has not been pressed in a while) the key needs to be pressed twice (This was much worse when g15macro was used and the keys almost always had to be pressed twice if I recall correctly). This may look like it's a huge bother at first, but really I hardly ever notice this when I'm using the keyboard and it is a very rare occurance.
    The Volume Wheel is erratic, I used patches from the net to make the wheel work but the wheel was unusable, I managed to make it just barely usable but I wouldn't call it "reliable" in it's current state. It does however work "ok". The wheel worked fine with generic keyboard drivers so maybe there is something in there to shed light on how to make them properly work (remember that there was a bit in libg15.c that made the wheel work, the other half of it is in uinput.c)
    The M-Key leds (M1, M2 and M3) will not light up until a G-Key or one of the M keys is pressed (very minor, I tried to fix this but failed, gave up since it's not really important)
    Run "g15daemon -d" for debug mode to see output from the driver when it is running you will repeatedly get the following error, I have no idea what this is but I do not like it
    libg15: Unknown usb error: Keyboard Read !! (err is -75 (Value too large for defined data type))
    look around line 471 of the patched libg15.c to see where the error is being printed from.
    Terminating the g15daemon (g15daemon -k) will render the keyboard unusable and can result in bugs (for example your next keypress may be detected but release will not be detected) so be careful when doing something like that. Unplugging the keyboard and plugging it back in solves this issue.
    Scroll-Lock led does not work (this is not specific to this keyboard, it is a Linux problem and affects all keyboards as far as I am aware)
    I personally prefer using this keyboard in Linux over using it in Windows because of how much more configurable it is (there's nothing I can't do with the press of a button now) and switching workspaces with just one button each for a total of 6 is a joy!
    Feel free to comment below with any questions or thoughts, any suggestions to improve the code or other contributions are greatly appreciated! I am not skilled in C programming and as such some of my code may look hideous to those who would know what they're doing so better ways to achieve the same results will not be ignored either and I will add any significant updates to the OP when I see them.
    Good Luck and Enjoy
    PS: I know the libg15 patch is rather "unclean" (contains a lot of redundant patches, i.e. replacing a line with the same line) but I was too lazy to clean it up. I tried once but it did not work out so well
    If you have a G510s and this did not work for you, I may be able to help you get that working, comment if you want help with that (the first step to try is on the wiki)
    Last edited by rabcor (2015-05-08 14:41:34)

    Major Update: The G-Keys can now be edited without recompiling by editing shell scripts at "/usr/share/g15daemon/macros/"
    Each button has it's own script file named by it's label (e.g. to edit the functionality of G1, open the script named G1.) The button will try to execute the scripts as programs, so make sure they are executable (chmod +x) and as long as the name remains the same, if you want to replace the files with something different, know that the arguments currently given to the files ($1 and $2) are ($1)on/off and ($2)0-2  (where 0 is M1 and 2 is M3)
    To download the updated sources, go here (only the g15daemon source/patch was updated). This thread's OP has been updated.
    Last edited by rabcor (2015-02-12 04:46:48)

  • Running a Java App like a service in linux and not closing with window

    I know its not really a question i should ask you but thought you might have a quick answer for me, I have trying to running a small java application on one of the servers. I want it to run almost like a service, what i mean is i dont want the application to end when the terminal session is ended. So i thought i should put an entry into the /etc/rc.local file as follows (Final Line):
    cd /home/bluepoint/Teamselect_ServerApp_v1.0/bin/
    java Server
    #!/bin/sh
    # This script will be executed *after* all the other init scripts.
    # You can put your own initialization stuff in here if you don't
    # want to do the full Sys V style init stuff.
    touch /var/lock/subsys/local
    /home/bluepoint/kmyfirewall.sh
    su - bluepoint "/usr/local/tomcat/jakarta-tomcat-5.0.28/bin/startup.sh"
    cd /home/bluepoint/startme.sh
    As you will see it call a shell script which contains only the following lines (or see attached):cd /home/bluepoint/Teamselect_ServerApp_v1.0/bin/
    java Server
    but nothing happens when i restart the server. The DB, sendmail, tomcat etc start fine but not my app.
    The application works fine if i start it in a terminal window so i know it can run.
    Any ideas what im doing wrong??
    Kind Regards

    It's probably not happening because you missed the -c from the su command. However this isn't the correct approach to daemon processes on linux (which is what you're after).
    What you need to do is to place a script in the /etc/init.d directory. This script should take a single argument and start the daemon if the argument is "start", and stop it if "stop". Check out the scripts already in there to see how it's done.
    Then go to System Settings/Server settings/Services and enable the new service for the normal run level.

  • How to enable OCR with Scangear MP under Linux for MG8250?

    Under Linux openSUSE 12.3 I use Scangear MP 1.80 for my Canon PIXMA MG8250.
    As a scan target (in my German GUI it's "Ziel") I can choose "OCR". But there is no text output, the scan is just saved as a picture. How can I configure Scangear to open the scan via Tesseract in a text editor.
    By the way, the target "Print" (in German "Drucken") leads to saving just as well, though there is at least one printer at hand, of course.
    It's a pity that the pixma scan drivers that are shipped with openSUSE don't work with xsane (the scanner starts working, but stops after one third of the page). Using xsane with a different scanner I can use OCR successfully.
    Volker

    There are two basic types of core OCR algorithm, which may produce a ranked list of candidate characters.
    Matrix matching involves comparing an image to a stored glyph on a pixel-by-pixel basis; it is also known as "pattern matching" or "pattern recognition". This relies on the input glyph being correctly isolated from the rest of the image, and on the stored glyph being in a similar font and at the same scale. This technique works best with typewritten text and does not work well when new fonts are encountered. This is the technique the early physical photocell-based OCR implemented, rather directly.
    Feature extraction decomposes glyphs into "features" like lines, closed loops, line direction, and line intersections. These are compared with an abstract vector-like representation of a character, which might reduce to one or more glyph prototypes. General techniques of feature detection in computer vision are applicable to this type of OCR, which is commonly seen in "intelligent" handwriting recognition and indeed most modern OCR software. Nearest neighbour classifiers such as the k-nearest neighbors algorithm are used to compare image features with stored glyph features and choose the nearest match.
    Software such as Cuneiform and Tesseract use a two-pass approach to character recognition. The second pass is known as "adaptive recognition" and uses the letter shapes recognized with high confidence on the first pass to better recognize the remaining letters on the second pass. This is advantageous for unusual fonts or low-quality scans where the font is distorted.
    So I wonder which kind of OCR algorithm are you using?

  • Can't mount oracle database on linux system

    This is same as previous posting just added
    e-mail and username info fo forum posting.
    I am not able to mount an Oracle database.
    I am new to Oracle and am working on an Oracle8i installation on an
    Intel Linux Suse 6.3 platform. I am using only one harddrive and am
    not using the 4 mount points as mentioned for efficiecy purposes in
    the Oracle documentation..I am using the installation cd from Oracle8i
    for Linux Starter Kit by Oracle Press. If anyone has this book they
    can refer to pages 41-44 for the examples I followed.
    As sysdba in sqplplus using the STARTUP command I can not Mount the
    database -step 2 of the 3 stage process (Start, Mount and Open the
    database) of opening an Oracle database.
    I show the errors I encountered when I did the first 2 of the 3 steps
    in the step-by-step mode (STARTUP NOMOUNT pfile=, ALTER DATABASE
    MOUNT) in the sqlplus session and alert log respectively with startup
    nomount and alter database mount for this sqlplus session.
    Additionally I show the init.ora file lines referring to control file
    which seem to be referred to by the sqlplus error messages and the
    alert.log file. Perhaps some can give me some advice as what I can try
    to fix this problem.
    At the end of this e-mail I added several questions I had in regard to the control
    files. Any help is appreciated.
    Well, here are the sqlplus session results and its alert.log file:
    Oracle sqlplus session usr/oracle as sysdba
    oracle@CHESTNUT:~ > sqlplus
    SQL*Plus: Release 8.1.6.0.0 - Production on Mon Mar 19 20:47:49 2001
    (c) Copyright 1999 Oracle Corporation. All rights reserved.
    Enter user-name: usr/oracle as sysdba
    Connected to an idle instance.
    SQL> startup nomount pfile=/usr/oracle/dbs/init.ora ;
    ORACLE instance started.
    Total System Global Area 24989680 bytes
    Fixed Size 69616 bytes
    Variable Size 24637440 bytes
    Database Buffers 204800 bytes
    Redo Buffers 77824 bytes
    SQL> alter database mount ;
    alter database mount
    ERROR at line 1:
    ORA-00205: error in identifying controlfile, check alert log for more
    info
    SQL> shutdown immediate ;
    ORA-01507: database not mounted
    ORACLE instance shut down.
    SQL> exit
    Disconnected
    oracle@CHESTNUT:~ >
    alert.log file for above session
    Mon Mar 19 20:48:38 2001
    Starting ORACLE instance (normal)
    LICENSE_MAX_SESSION = 0
    LICENSE_SESSIONS_WARNING = 0
    LICENSE_MAX_USERS = 0
    Starting up ORACLE RDBMS Version: 8.1.6.1.0.
    System parameters with non-default values:
    processes = 50
    shared_pool_size = 3500000
    control_files = ora_control1, ora_control2
    db_block_buffers = 100
    log_buffer = 32768
    log_checkpoint_interval = 10000
    db_files = 80
    db_file_multiblock_read_count= 8
    global_names = TRUE
    db_name = DEFAULT
    parallel_max_servers = 5
    max_dump_file_size = 10240
    PMON started with pid=2
    Load Indicator not supported by OS !
    DBW0 started with pid=3
    LGWR started with pid=4
    CKPT started with pid=5
    SMON started with pid=6
    RECO started with pid=7
    Mon Mar 19 20:48:58 2001
    alter database mount
    Mon Mar 19 20:48:58 2001
    ORA-00202: controlfile: 'ora_control1'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Mon Mar 19 20:49:01 2001
    ORA-205 signalled during: alter database mount
    Mon Mar 19 20:49:12 2001
    Shutting down instance (immediate)
    License high water mark = 1
    Mon Mar 19 20:49:12 2001
    ALTER DATABASE CLOSE NORMAL
    ORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...
    archiving is disabled
    init.ora control files
    # define two control files by default
    control_files = (ora_control1, ora_control2)
    Here are my control file questions:
    I need to know several points:
    1) What are control files susposed to
    contain and how would I recognize them?
    I used the
    unix find /usr/oracle \*ctl* -print
    command to locate files with a ctl extension.
    This resulted in about a dozen such files in
    different directories as shown below:
    ./bin/lsnrctl
    ./bin/extractlib
    ./bin/agtctl
    ./bin/oidctl
    ./bin/lsnrctl0
    ./bin/agtctlO
    ./rdbms/demo/ulcase1.ctl
    ./rdbms/demo/ulcase10.ctl
    ./rdbms/demo/ulcase2.ctl
    ./rdbms/demo/ulcase3.ctl
    ./rdbms/demo/ulcase4.ctl
    ./rdbms/demo/ulcase5.ctl
    ./rdbms/demo/ulcase6.ctl
    ./rdbms/demo/ulcase7.ctl
    ./rdbms/demo/ulcase8.ctl
    ./rdbms/demo/ulcase9.ctl
    ./ldap/load/dn.ctl
    ./ldap/load/attr_store.ctl
    ./ord/ts/demo/tsquick/tsquick.ctl
    ./ord/ts/demo/usageutl/utildat.ctl
    ./ord/ts/demo/usage/stockdat.ctl
    ./ord/ts/demo/usage/stockinc.ctl
    ./ord/ts/demo/retrofit/sales.ctl
    ./ord/ts/demo/retrofit/sales2.ctl
    ./ord/ts/demo/applet/indexdemo.ctl
    ./javavm/admin/libjox8com_sun_jndi_ldap_ctl.so
    ./md/demo/examples/migctl.h
    ./md/demo/examples/migctl.c
    2) On page 100 in the book Oracle 8i A Beginners's
    by Oracle Press mention is made of a
    CREATE CONTROLFILE command that can under
    circumstances be used to re-create a control-file.
    but that is all that is said about it. Perhaps
    you might know something more about it.
    3) Would you recommend any good text for
    Oracle DBA's, especially for the problem of the sort
    that I am encountering?
    [email protected]
    null

    It's probably not supported on RHEL5/Centos5/etc., but...
    You can get the installer to function using the following steps:
    - extract the cal_linux_*.tar.gz, and cd into the OracleCalendar_inst directory
    In there is the actual installer, cal_linux.
    - the cal_linux is shell script wrapped around some binary blobs. The installer's
    problem is that Oracle is setting the LD_ASSUME_KERNEL=2.2.5 environment
    variable, which is a mistake on RHEL5. You need to make it not set that variable,
    but you need to do so in a way that the size of the shell script does not change at all,
    and none of the binary blobs are impacted.
    - the approach I took was
    mv cal_linux cal_linux.BAK
    sed -e 's/LD_ASSUME_KERNEL=2.2.5/LD_ASSUME_KERNEL= /g' < cal_linux.BAK > cal_linux
    chmod a+rx cal_linux
    cal_linux -i gui
    Note: you must have exactly 5 spaces in the substitution part of the sed command, because you're replacing 5 characters (2.2.5), and the size of the shell script must not change.
    If you do that, the installer should run (one warning from awk still) and you should be able to install the product.
    Tim

Maybe you are looking for