GNU Screen and framebuffer (uvesafb)

Hello,
I am using arch linux without X. I have installed a framebuffer (uvesafb) and
am using GNU screen to multitask. I have seen that the screen cannot use a
frame buffer as when a try to use fbi I get this output:
ioctl VT_GETSTATE: Invalid argument (not a linux console?)
But when I use mplayer it seems to work fine. The vidoes play fine (although
there is some flickering and the size is a bit small) and w3m seems to display
the pictures properly inline too. Which means that screen can use a framebuffer.
So my question is how do I use fbi and fbgrab (or fbshot) in screen. Is there a way
for screen to communicate directly with the frame buffer?

Moyamo wrote:Is there any other terminal multiplexer that can support a framebuffer besides screen?
Tmux. I've been using it successfully for quite a while.

Similar Messages

Gnu Screen and 10.5

So, does anyone else have problems with Gnu Screen and OSX 10.5? If I use the box-shipped version, my PATH is completely ignored, and it doesn't understand deflogin or login in my .screenrc file.
If I use the macports version, I get UTMP problems and unless I manually create /var/run/utmp, eventually /etc/sudoers and passwd gets updated, and UID 501 is no longer in the passwd file!

That's actually not screen's fault.
When bash starts, it will read either .profile_bash or .bashrc but not both, depending whether it is a shell process or subprocess.
On X-window based systems, one of these (I can never remember which) gets read when the root window starts, and then the other gets read when every sub-process starts. On OS X this approach breaks down.
There is a slightly different bug I have been seeing, and I think it is due to multi-threading. Basically the screen session starts before the $PATH gets entries like /sw/bin or /opt/local/bin set. I never figured out how, but my hackish workaround is simply to start screen and then invoke the process I want, rather than to do it all in one command. (This gets annoying if you are writing shell scripts that invoke screen).

GNU Screen and 256 color terminal

Okay I've been racking my brain over trying to get 256 colors working while in screen.
If I run the 256colors2.pl script (found in xterm source) while in xterm / roxterm / xfce4-terminal it shows all colours as expected.
$ echo $TERM
xterm
Now I followed the wiki and added the "term screen-256color" line to my .screenrc
but if I run screen and run the 256colors script it doesn't show 256 colours (all messed up)
If I exit screen and manually set my $TERM
$ export TERM=xterm-256color
then run screen again, things seem to work properly.
But why?
I've read elsewhere on this forum that it's not good practice to force your $TERM so what should I do here?
What is the proper way? I just cant wrap my head around why 256 colors work when $TERM=xterm outside of screen, but not when in screen.
Last edited by Zer0 (2009-10-30 05:10:08)

I recommend just using TERM=xterm-256color, as TERM=xterm does not reflect the terminal's capabilities. Replacing the command for your current terminal emulator with something like:
xterm -tn xterm-256color
should be sufficient.
I now use rxvt-unicode-256color from [community], which uses a 256color terminfo by default. Why xterm and friends don't use this when it is supported, I don't understand.
Last edited by chpln (2009-10-30 06:32:44)

Urxvt, xterm, vim, and gnu screen.

To make this simple: all i want is 256 color support in one terminal, that will give 256 color support in vim, gnu screen, and not screw up shells i ssh into. If I could get this working in xterm alone consider this solved.
The more I try to fix my problem it seems the more complicated it gets. What I want, I thought was simple:
Now xterm seems to be the most workable solution, I guess I can give up on having clickable links, so that can go on the back burner. But these are the problems i'm having.
Here's the problem point by point:
Urxvt
$ echo $TERM
xterm-256color
Urxvt will run a perl script I have to display 256 colors. Except is does not show the grayscale ramp shown here:
VIM in urxvt does NOT show any colors. It's all white text.
This is my .vimrc
$ cat .vimrc
syntax on
set ignorecase
set smartcase
set incsearch
set hlsearch
let g:netrw_http_cmd = "wget -q -O"
if &t_Co == 256
colorscheme xoria256
else
colorscheme desert
endif
in urxvt Gnu Screen
echo $TERM
screen-256color-bce
the perl script does not display 256 colors like it should.
vim in urxvt in screen again, does not show any colors. all white text.
Xterm
echo $TERM
xterm
Xterm displays the full 256 colors from the script including the grayscale ramp.
vim in xterm displays the desert theme (i would prefer it default to the xoria256, no idea why the 256 color script works but vim doesn't see xterm as a 256 capable terminal).
in xterm, Gnu Screen
echo $TERM
screen-256color-bce ( I do not see in any file where this option is defined)
Xterm with Gnu Screen displays the full 256 colors from the script including the grayscale ramp.
Vim in Gnu Screen in Xterm displays 256 colors properly.
Here is my .screenrc
#terminfo and termcap for nice 256 color terminal
# allow bold colors - necessary for some reason
attrcolor b ".I"
# tell screen how to set colors. AB = background, AF=foreground
termcapinfo xterm 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'
# erase background with current bg color
defbce "on"
#term xterm-256color
term screen-256color
startup_message off
caption always "%{= KW}%-w%{= gW}%n %t%{-}%+w %-="
hardstatus alwayslastline "%{= kW} %-= %{= kC}Session:%u%{= kW} %5` | %{= kC}Host:%{= kW} %H | %1` |%{= kC} MEM:%{= kW} %2`MB /%{= kC} SW: %{= kW}%3`MB | %4` %{= kR}Unread %{= kW}| %m/%d %c"
vbell off
#Backticks to display information in status bar
backtick 1 60 60 /home/username/bin/get_uptime
backtick 2 60 60 /home/username/bin/get_freemem
backtick 3 60 60 /home/username/bin/get_freeswap
backtick 4 60 60 /home/username/bin/get_gmail
backtick 5 60 60 /home/username/bin/get_sessionname
defscrollback 5000
screen -t root 0 sudo -s
screen -t shell 1 bash
screen -t shell 2 bash
screen -t shell 3 bash
screen -t shell 4 bash
screen -t shell 5 bash
screen -t shell 6 bash
screen -t shell 7 bash
screen -t irc 8 irssi
screen -t home 9 bash
select 1
here is my .Xdefaults
!XTerm*font: -*-terminal-*-*-*-*-14-*-*-*-*-*-*-
XTerm*font: xft:DejaVu Sans Mono:size=8
xterm*faceName: Mono
xterm*faceSize: 8
XTerm*background: #191919
XTerm*foreground: white
XTerm*pointerColor: white
XTerm*pointerColorBackground: black
XTerm*cursorColor: white
!XTerm*internalBorder: 3
XTerm*loginShell: true
XTerm*scrollBar: false
XTerm*scrollKey: true
XTerm*saveLines: 1000
XTerm*multiClickTime: 250
XTerm*boldColors: false
xterm*title: xterm
xterm*geometry: 160x25
! Black
XTerm*color0: #262626
XTerm*color8: #252525
! Red
XTerm*color1: #C12121
XTerm*color9: #E50E0E
! Green
XTerm*color2: #597b20
XTerm*color10: #89b83f
! Yellow
XTerm*color3: #Ded838
XTerm*color11: #efef60
! Blue
XTerm*color4: #265997
XTerm*color12: #3F6FD0
! Magenta
XTerm*color5: #706c9a
XTerm*color13: #826ab1
! Cyan
XTerm*color6: #69a2b0
XTerm*color14: #a1cdcd
! White
XTerm*color7: #BBBBBB
XTerm*color15: #EEEEEF
URxvt*termName: xterm-256color
URxvt*urlLauncher: /usr/bin/firefox
URxvt.matcher.pattern.1: \\bwww\\.[\\w-]\\.[\\w./?&@#-]*[\\w/-]
URxvt.matcher.button: 2
URxvt.perl-ext-common: default,matcher
URxvt*saveLines: 4000
URxvt*background: #191919
URxvt*secondaryScroll: true
URxvt*scrollBar: false
URxvt*geometry: 150x25
URxvt.font: xft:DejaVu Sans Mono:size=8
URxvt.xftAntialias: true
URxvt*foreground: white
URxvt*pointerColor: white
URxvt*pointerColorBackground: black
URxvt*cursorColor: white
!URxvt*inheritPixmap: True
!URxvt*shading: 90
!URxvt*tintColor: #999
URxvt*keysym.Home: \033[1~
URxvt*keysym.End: \033[4~
! Black
URxvt*color0: #262626
URxvt*color8: #252525
! Red
URxvt*color1: #C12121
URxvt*color9: #E50E0E
! Green
URxvt*color2: #597b20
URxvt*color10: #89b83f
! Yellow
URxvt*color3: #Ded838
URxvt*color11: #efef60
! Blue
URxvt*color4: #265997
URxvt*color12: #3F6FD0
! Magenta
URxvt*color5: #706c9a
URxvt*color13: #826ab1
! Cyan
URxvt*color6: #69a2b0
URxvt*color14: #a1cdcd
! White
URxvt*color7: #BBBBBB
URxvt*color15: #EEEEEF
To Fix In Xterm
-Get Vim to display 256 colors without Gnu Screen
To Fix In Urxvt
-Get vim to display any color, but preferably 256 colors in urxvt and urxvt with Gnu Screen. (and yes, it's a 256 capable urxvt)
-Get shells i SSH into to recognize the reported term variable
To Fix In Gnu Screen
-Make it stop reporting the term variable as screen-256color-bce without losing 256 color support as this screws up shells i ssh to.
any help would be greatly appreciated. I feel like a dog chasing its tail b/c when I find a fix to one problem, I end up creating 1-2 more.
Last edited by scv5 (2009-07-31 14:11:31)

I had similar but different issues regarding this. Now, i have 256 color support in whatever terminal/ssh/screen session I'm in.
The relevant config lines:
.Xdefaults:
XTerm*termName: xterm-256color
URxvt*termName: rxvt-256color
.vimrc
" 256 colors only if you can handle it
if $TERM =~ "-256color"
set t_Co=256
colorscheme zenburn
endif
.screenrc
# term
term xterm-256color
# main options
altscreen on
attrcolor b ".I"
defbce "on"
# some termcaps
termcapinfo xterm-256color 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'
termcapinfo rxvt-256color 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'
note: this setup caused an issue where background colors in mutt/htop inside screen did not extend passed the line's text. i had to solve that via this workaround.
Last edited by brisbin33 (2009-07-31 21:28:55)

GNU screen, spawn windows and issue specific command to each

Hello folks.
I want gnu screen to spawn some windows, let's say, so I've put these lines in .screenrc:
screen -t foo
screen -t bar
now I'd like to change the directories for foo and bar. I've tried multiple commands like:
screen -X at foo screen -X stuff 'cd /tmp^M'
screen -X at bar screen -X stuff 'cd ~/projects^M'
and some other variations. At best, it gives the error message: "key: screen: invalid option -X .", at worst it doesn't start at all.
Regards.

problem solved. for others in need, put in .screenrc:
screen -t foo
at foo stuff 'cd /tmp^M'
where "^M" is generated by pressing sequentially ctrl+v,ctrl+m

Xorg and framebuffer issues with high resolutions

So I got a nice shiny new 23" 1080p Asus VH236H monitor. Unfortunately, it's not turning out to be as great I was hoping, possibly due to the Geforce FX5200 bios, but I'm not sure. I think these issues are probably related, so I put them in the same thread.
First, the console: vesafb, uvesafb, and nvidiafb all fail at delivering a useable framebuffer greater than 1280x1024. vesafb flat out denies anything beyond 795 (0x31B). uvesafb and nvidiafb will fall back on 1280x1024@75Hz, which causes text to flash all over the screen and requires a reboot to remedy. It doesn't matter if I feed fbset the exact timings X uses, they'll still fallback on 1280x1024. `hwinfo --vbe` has this to say about hardware support:
02: None 00.0: 11001 VESA Framebuffer
[Created at bios.459]
Unique ID: rdCR.2BE3cN5U3aB
Hardware Class: framebuffer
Model: "NVIDIA NV34 Board - p162-1n"
Vendor: "NVIDIA Corporation"
Device: "NV34 Board - p162-1n"
SubVendor: "NVIDIA"
SubDevice:
Revision: "Chip Rev"
Memory Size: 128 MB
Memory Range: 0xe8000000-0xefffffff (rw)
Mode 0x0300: 640x400 (+640), 8 bits
Mode 0x0301: 640x480 (+640), 8 bits
Mode 0x0303: 800x600 (+800), 8 bits
Mode 0x0305: 1024x768 (+1024), 8 bits
Mode 0x0307: 1280x1024 (+1280), 8 bits
Mode 0x030e: 320x200 (+640), 16 bits
Mode 0x030f: 320x200 (+1280), 24 bits
Mode 0x0311: 640x480 (+1280), 16 bits
Mode 0x0312: 640x480 (+2560), 24 bits
Mode 0x0314: 800x600 (+1600), 16 bits
Mode 0x0315: 800x600 (+3200), 24 bits
Mode 0x0317: 1024x768 (+2048), 16 bits
Mode 0x0318: 1024x768 (+4096), 24 bits
Mode 0x031a: 1280x1024 (+2560), 16 bits
Mode 0x031b: 1280x1024 (+5120), 24 bits
Mode 0x0330: 320x200 (+320), 8 bits
Mode 0x0331: 320x400 (+320), 8 bits
Mode 0x0332: 320x400 (+640), 16 bits
Mode 0x0333: 320x400 (+1280), 24 bits
Mode 0x0334: 320x240 (+320), 8 bits
Mode 0x0335: 320x240 (+640), 16 bits
Mode 0x0336: 320x240 (+1280), 24 bits
Mode 0x033d: 640x400 (+1280), 16 bits
Mode 0x033e: 640x400 (+2560), 24 bits
Mode 0x0347: 1400x1050 (+1400), 8 bits
Mode 0x0348: 1400x1050 (+2800), 16 bits
Config Status: cfg=new, avail=yes, need=no, active=unknown
03: None 00.1: 10002 LCD Monitor
[Created at monitor.95]
Unique ID: jyhG.zs6hrn8sbx2
Hardware Class: monitor
Model: "ASUS VH236H"
Vendor: ACI
Device: eisa 0x23f2 "ASUS VH236H"
Serial ID: "9CLMTF216408"
Resolution: 720x400@70Hz
Resolution: 640x480@60Hz
Resolution: 640x480@67Hz
Resolution: 640x480@72Hz
Resolution: 640x480@75Hz
Resolution: 800x600@56Hz
Resolution: 800x600@60Hz
Resolution: 800x600@72Hz
Resolution: 800x600@75Hz
Resolution: 832x624@75Hz
Resolution: 1024x768@60Hz
Resolution: 1024x768@70Hz
Resolution: 1024x768@75Hz
Resolution: 1280x1024@75Hz
Resolution: 1152x864@75Hz
Resolution: 1280x1024@60Hz
Resolution: 1920x1080@60Hz
Size: 521x293 mm
Detailed Timings #0:
Resolution: 1920x1080
Horizontal: 1920 2008 2052 2200 (+88 +132 +280) +hsync
Vertical: 1080 1084 1089 1125 (+4 +9 +45) +vsync
Frequencies: 148.50 MHz, 67.50 kHz, 60.00 Hz
Driver Info #0:
Max. Resolution: 1920x1080
Vert. Sync Range: 55-75 Hz
Hor. Sync Range: 30-85 kHz
Bandwidth: 148 MHz
Config Status: cfg=new, avail=yes, need=no, active=unknown
Supposedly, the framebuffer should be able to support 1400x1050, but I can't get it, possibly because it's not listed as monitor supported. Does this mean that I'm stuck with a 1280x1024 max res?
This brings me to my next problem... Xorg. On my old monitor, I liked the nvidiafb-fbdev driver combination because I could quickly switch between X and console, and so long as I had the proprietary nvidia gl libraries installed, X ran smoothly. (never got the nv driver fbdev option to function with stability) Obviously, this is impossible now. I can't get nv to run at a resolution greater than 1280x1024. With the proprietary drivers, max resolution is 1440x900; however, if I disable max pixel clock checking, support for 1680x1050 and 1920x1080 is added.
Now, this is where things get serious. If I switch back to console after starting X with NoMaxPClkCheck, I get an out of range message from my monitor. I can freely restart/switch back to X and everything is fine there, but the console is unuseable until reboot.
relevant Xorg.0.log
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "NoLogo" "True"
(**) NVIDIA(0): Option "NvAGP" "1"
(**) NVIDIA(0): Option "ConnectedMonitor" "DFP-0"
(**) NVIDIA(0): Option "RenderAccel" "True"
(**) NVIDIA(0): Option "AllowGLXWithComposite" "True"
(**) NVIDIA(0): Option "Coolbits" "1"
(**) NVIDIA(0): Option "UseEdidDpi" "False"
(**) NVIDIA(0): Option "AddARGBGLXVisuals" "True"
(**) NVIDIA(0): Option "ModeValidation" "DFP-0: NoMaxPClkCheck"
(**) NVIDIA(0): Enabling RENDER acceleration
(**) NVIDIA(0): ConnectedMonitor string: "DFP-0"
(**) NVIDIA(0): Use of NVIDIA internal AGP requested
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.
(II) NVIDIA(0): NVIDIA GPU GeForce FX 5200 (NV34) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 131072 kBytes
(--) NVIDIA(0): VideoBIOS: 04.34.20.87.00
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce FX 5200 at PCI:1:0:0:
(--) NVIDIA(0): ACI ASUS VH236H (DFP-0)
(--) NVIDIA(0): ACI ASUS VH236H (DFP-0): 135.0 MHz maximum pixel clock
(--) NVIDIA(0): ACI ASUS VH236H (DFP-0): Internal Single Link TMDS
(II) NVIDIA(0): Mode Validation Overrides for ACI ASUS VH236H (DFP-0):
(II) NVIDIA(0): NoMaxPClkCheck
(II) NVIDIA(0): Assigned Display Device: DFP-0
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "1920x1080"
(II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
(**) NVIDIA(0): DPI set to (95, 95); computed from "DisplaySize" Monitor
(**) NVIDIA(0): section option
(**) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): Setting mode "1920x1080"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(==) RandR enabled
Xorg.conf
Section "Device"
Identifier "Card0"
VendorName "nVidia Corporation"
BoardName "GeForce FX 5200 [NV34] (rev a1)"
BusID "PCI:1:0:0"
Driver "nvidia"
Option "NvAGP" "1"
Option "Coolbits" "1"
Option "RenderAccel" "True"
Option "NoLogo" "True"
Option "AllowGLXWithComposite" "True"
Option "AddARGBGLXVisuals" "True"
# Option "UseEdid" "False"
Option "UseEdidDpi" "False"
# Option "DPI" "96 x 96"
Option "ConnectedMonitor" "DFP-0"
# Option "ExactModeTimingsDVI" "True"
Option "ModeValidation" "DFP-0: NoMaxPClkCheck"
# Option "ModeValidation" "AllowNon60HzDFPModes,
# NoMaxPClkCheck,
# NoEdidMaxPClkCheck,
# NoMaxSizeCheck,
# NoHorizSyncCheck,
# NoVertRefreshCheck,
# NoDFPNativeResolutionCheck,
# NoVirtualSizeCheck,
# NoVesaModes,
# NoEdidModes,
# NoXServerModes,
# NoTotalSizeCheck"
EndSection
Section "Device"
Identifier "Card1"
VendorName "nVidia Corporation"
BoardName "GeForce FX 5200 [NV34] (rev a1)"
BusID "PCI:1:0:0"
Driver "nv"
Option "NoDDC"
# Option "UseFBDev" "true"
EndSection
Section "Device"
Identifier "Card2"
VendorName "nVidia Corporation"
BoardName "GeForce FX 5200 [NV34] (rev a1)"
BusID "PCI:1:0:0"
Driver "fbdev"
Option "NoDDC"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Asus"
ModelName "VH236H"
DisplaySize 510.72 287.28
# HorizSync 30.0 - 83.0
# VertRefresh 50.0 - 75.0
# ModeLine "1920x1080" 148.5 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Option "DPMS" "true"
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Asus"
ModelName "VH236H"
DisplaySize 510.72 287.28
HorizSync 30.0 - 83.0
VertRefresh 50.0 - 75.0
ModeLine "1920x1080" 148.5 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Option "DPMS" "true"
EndSection
Section "Monitor"
Identifier "Monitor2"
VendorName "LG"
ModelName "566LM"
DisplaySize 305 229
HorizSync 30.0 - 63.0
VertRefresh 50.0 - 75.0
ModeLine "1024x768" 78.75 1024 1056 1152 1312 768 769 772 800 +hsync +vsync
Option "DPMS" "true"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1920x1080"
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Card1"
Monitor "Monitor1"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1920x1080"
EndSubSection
EndSection
Section "Screen"
Identifier "Screen2"
Device "Card2"
Monitor "Monitor1"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1920x1080"
EndSubSection
EndSection
Section "ServerLayout"
Identifier "DefaultLayout"
Screen 0 "Screen0"
EndSection
Section "ServerLayout"
Identifier "nvLayout"
Screen 0 "Screen1"
EndSection
Section "ServerLayout"
Identifier "fbLayout"
Screen 0 "Screen2"
EndSection

Brett,
When working with the file that has many vector points. Try working in Outline mode if you can and if it works for you. Keep in mind with all the complex vectors the screen has to redraw which is taking up application memory when you move or update the object/drawing. If you can try resize the graphic to a smaller size to work with it then enlarge it back to normal size when you are ready for the final version of the file.
It may help.
Thanks
Scott

Xorg / catalyst / kernel upgrade - Frozen screen and input [SOLVED]

I knew it, never upgrade xorg/graphic drivers when using ATI cards, just bless your god when it works and never touch it again. But I got tempted and I did a full system upgrade, and now... my xorg is broken.
I'm using ATI proprietary drivers catalyst 8.12-1 with xorg 1.5.3-3. My card is an ATI x1950 pro.
It used to work perfectly, but since the update, when i startx I just get a terminal (because of my .xinitrc) in fullscreen without my window manager getting launched, and my mouse in the middle of the screen; and nothing responds the mouse won't move, even ctrl+alt+backspace won't work. I have to ssh on my machine and 'killall X'.
I tried starting off with a default config (using aticonfig --initial -f), but still the same problem.
I have a dual screen setup.
I disabled AIGLX and Composite, but no success.
If I fail to repair this, since I made a backup of my pacman database, I could revert it right ?
Please help us, us pwned ATI users !
Here is the /var/log/Xorg.0.log
X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.27-ARCH i686
Current Operating System: Linux fatale 2.6.27-ARCH #1 SMP PREEMPT Mon Dec 8 22:01:01 UTC 2008 i686
Build Date: 05 December 2008 09:10:55PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Dec 13 03:36:24 2008
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Xorg Configured"
(**) |-->Screen "ScreenSamsung" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Card0"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "PS/2 Mouse"
(**) Option "AllowMouseOpenFail" "true"
(**) Option "Xinerama" "true"
(**) Option "AIGLX" "false"
(==) Automatically adding devices
(==) Automatically enabling devices
(**) Xinerama: enabled
(WW) The directory "/usr/share/fonts/PEX" does not exist.
Entry deleted from font path.
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/cyrillic".
Entry deleted from font path.
(Run 'mkfontdir' on "/usr/share/fonts/cyrillic").
(WW) The directory "/usr/share/fonts/ttf/western" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/ttf/decoratives" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/truetype" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/truetype/openoffice" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/truetype/ttf-bitstream-vera" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/latex-ttf-fonts" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/defoma/CID" does not exist.
Entry deleted from font path.
(WW) The directory "/usr/share/fonts/defoma/TrueType" does not exist.
Entry deleted from font path.
(==) Including the default font path /usr/share/fonts/misc,/usr/share/fonts/100dpi:unscaled,/usr/share/fonts/75dpi:unscaled,/usr/share/fonts/TTF,/usr/share/fonts/Type1.
(**) FontPath set to:
/usr/share/fonts/misc:unscaled,
/usr/share/fonts/misc,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/75dpi,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/100dpi,
/usr/share/fonts/Type1,
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1
(**) ModulePath set to "/usr/lib/xorg/modules"
(**) Extension "Composite" is disabled
(WW) AllowEmptyInput is on, devices using drivers 'kbd' or 'mouse' will be disabled.
(WW) Disabling Keyboard0
(WW) Disabling PS/2 Mouse
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) Loader magic: 0x81d5900
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 4.1
X.Org XInput driver : 2.1
X.Org Server Extension : 1.1
X.Org Font Renderer : 0.6
(II) Loader running on linux
(--) using VT number 7
(--) PCI:*(0@1:0:0) ATI Technologies Inc RV570 [Radeon X1950 Pro] rev 0, Mem @ 0xe0000000/0, 0xf5000000/0, I/O @ 0x00008000/0, BIOS @ 0x????????/131072
(--) PCI: (0@1:0:1) ATI Technologies Inc RV570 [Radeon X1950 Pro] (secondary) rev 0, Mem @ 0xf5010000/0
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "freetype" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded. This was enabled by default and also specified in the config file.
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 7.4.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension XFree86-DRI
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 7.4.0, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(--) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "type1"
(WW) Warning, couldn't open module type1
(II) UnloadModule: "type1"
(EE) Failed to load module "type1" (module does not exist, 0)
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 1.5.3, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.6
(II) Loading font FreeType
(II) LoadModule: "record"
(WW) Warning, couldn't open module record
(II) UnloadModule: "record"
(EE) Failed to load module "record" (module does not exist, 0)
(II) LoadModule: "fglrx"
(II) Loading /usr/lib/xorg/modules/drivers//fglrx_drv.so
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
compiled for 1.4.99.906, module version = 8.56.4
Module class: X.Org Video Driver
(II) Primary Device is: PCI 01@00:00:0
(WW) Falling back to old probe method for fglrx
(II) ATI Proprietary Linux Driver Version Identifier:8.56.4
(II) ATI Proprietary Linux Driver Release Identifier: 8.561
(II) ATI Proprietary Linux Driver Build Date: Dec 1 2008 14:55:43
(WW) This ATI Proprietary Linux Driver does not guarantee support of video driver ABI higher than 2.0
(WW) Video driver ABI version of the X server is 4.1
(--) Assigning device section with no busID to primary device
(WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
(--) Chipset Supported AMD Graphics Processor (0x7280) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@1:0:1) found
(II) AMD Video driver is running on a device belonging to a group targeted for this release
(II) AMD Video driver is signed
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) fglrx(0): pEnt->device->identifier=0x9377518
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b]
[5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b]
[6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b]
[7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b]
[10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b]
(II) Setting vga for screen 0.
(II) fglrx(0): === [atiddxPreInit] === begin
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 0.1.0
ABI class: X.Org Video Driver, version 4.1
(II) fglrx(0): PCI bus 1 card 0 func 0
(**) fglrx(0): Depth 24, (--) framebuffer bpp 32
(II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) fglrx(0): Default visual is TrueColor
(**) fglrx(0): Option "dri" "true"
(**) fglrx(0): Option "KernelModuleParm" "agplock=0"
(**) fglrx(0): Option "RingSize" "8"
(**) fglrx(0): Option "EnableDepthMoves" "yes"
(**) fglrx(0): Option "UseInternalAGPGART" "no"
(**) fglrx(0): Option "DPMS" "true"
(II) fglrx(0): Loading PCS database from /etc/ati/amdpcsdb
(II) fglrx(0): 10BitPixelFormat disabled by default
(==) fglrx(0): RGB weight 888
(II) fglrx(0): Using 8 bits per RGB (8 bit DAC)
(==) fglrx(0): Gamma Correction for I is 0x06419064
(==) fglrx(0): Gamma Correction for II is 0x06419064
(==) fglrx(0): Buffer Tiling is ON
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Loading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
compiled for 1.4.99.906, module version = 8.56.4
ABI class: X.Org Server Extension, version 1.1
(--) fglrx(0): Chipset: "Radeon X1950 Series" (Chipset = 0x7280)
(--) fglrx(0): (PciSubVendor = 0x1462, PciSubDevice = 0x0762)
(--) fglrx(0): board vendor info: third party graphics adapter - NOT original ATI
(--) fglrx(0): Linear framebuffer (phys) at 0xe0000000
(--) fglrx(0): MMIO registers at 0xf5000000
(--) fglrx(0): I/O port at 0x00008000
(==) fglrx(0): ROM-BIOS at 0x000c0000
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/lib/xorg/modules//libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org Video Driver, version 4.1
(II) fglrx(0): Primary V_BIOS segment is: 0xc000
(**) fglrx(0): Option "mtrr" "on"
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.1.0
ABI class: X.Org Video Driver, version 4.1
(II) fglrx(0): VESA BIOS detected
(II) fglrx(0): VESA VBE Version 3.0
(II) fglrx(0): VESA VBE Total Mem: 16384 kB
(II) fglrx(0): VESA VBE OEM: ATI ATOMBIOS
(II) fglrx(0): VESA VBE OEM Software Rev: 9.13
(II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc.
(II) fglrx(0): VESA VBE OEM Product: RV570
(II) fglrx(0): VESA VBE OEM Product Rev: 01.00
(II) fglrx(0): ATI Video BIOS revision 9 or later detected
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 12, (OK)
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 12, (OK)
drmOpenByBusid: drmOpenMinor returns 12
drmOpenByBusid: drmGetBusid reports PCI:1:0:0
(II) fglrx(0): Using adapter: 1:0.0.
(II) fglrx(0): [FB] MC range(MCFBBase = 0xc0000000, MCFBSize = 0x10000000)
(--) fglrx(0): Video RAM: 262144 kByte, Type: DDR3
(II) fglrx(0): PCIE card detected
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) fglrx(0): ***Display: ConnectedDisplayTypes=0x00000090, disabled=0x00000000
(II) fglrx(0): Connected Display1: CRT on secondary DAC [crt2]
(II) fglrx(0): Display1 EDID data ---------------------------
(II) fglrx(0): Manufacturer: NUL Model: 1 Serial#: 1
(II) fglrx(0): Year: 2001 Week: 1
(II) fglrx(0): EDID Version: 1.3
(II) fglrx(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
(II) fglrx(0): Sync: Separate
(II) fglrx(0): Max Image Size [cm]: horiz.: 31 vert.: 23
(II) fglrx(0): Gamma: 1.00
(II) fglrx(0): DPMS capabilities: StandBy Suspend; RGB/Color Display
(II) fglrx(0): First detailed timing is preferred mode
(II) fglrx(0): redX: 0.597 redY: 0.343 greenX: 0.316 greenY: 0.566
(II) fglrx(0): blueX: 0.153 blueY: 0.131 whiteX: 0.310 whiteY: 0.328
(II) fglrx(0): Supported VESA Video Modes:
(II) fglrx(0): 720x400@70Hz
(II) fglrx(0): 640x480@60Hz
(II) fglrx(0): 640x480@72Hz
(II) fglrx(0): 640x480@75Hz
(II) fglrx(0): 800x600@56Hz
(II) fglrx(0): 800x600@60Hz
(II) fglrx(0): 800x600@72Hz
(II) fglrx(0): 800x600@75Hz
(II) fglrx(0): 1024x768@60Hz
(II) fglrx(0): 1024x768@70Hz
(II) fglrx(0): 1024x768@75Hz
(II) fglrx(0): Manufacturer's mask: 0
(II) fglrx(0): Supported additional Video Mode:
(II) fglrx(0): clock: 65.0 MHz Image Size: 304 x 228 mm
(II) fglrx(0): h_active: 1024 h_sync: 1048 h_sync_end 1184 h_blank_end 1184 h_border: 0
(II) fglrx(0): v_active: 768 v_sync: 771 v_sync_end 777 v_blanking: 806 v_border: 0
(II) fglrx(0):
(II) fglrx(0):
(II) fglrx(0): Monitor name:
(II) fglrx(0): EDID (in hex):
(II) fglrx(0): 00ffffffffffff003aac010001000000
(II) fglrx(0): 010b0103081f1700caf0649857519127
(II) fglrx(0): 214f54afce0001010101010101010101
(II) fglrx(0): 010101010101641900a0400026301888
(II) fglrx(0): 360030e410000018000000fe000a2020
(II) fglrx(0): 20202020202020202020000000fe000a
(II) fglrx(0): 202020202020202020202020000000fc
(II) fglrx(0): 000a202020202020202020202020000e
(II) fglrx(0): End of Display1 EDID data --------------------
(II) fglrx(0): Connected Display2: DFP on secondary TMDS [tmds2i]
(II) fglrx(0): Display2 EDID data ---------------------------
(II) fglrx(0): Manufacturer: SAM Model: 1e5 Serial#: 1212821817
(II) fglrx(0): Year: 2006 Week: 7
(II) fglrx(0): EDID Version: 1.3
(II) fglrx(0): Digital Display Input
(II) fglrx(0): Max Image Size [cm]: horiz.: 38 vert.: 30
(II) fglrx(0): Gamma: 2.20
(II) fglrx(0): DPMS capabilities: Off
(II) fglrx(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
(II) fglrx(0): First detailed timing is preferred mode
(II) fglrx(0): redX: 0.640 redY: 0.329 greenX: 0.300 greenY: 0.600
(II) fglrx(0): blueX: 0.150 blueY: 0.060 whiteX: 0.313 whiteY: 0.329
(II) fglrx(0): Supported VESA Video Modes:
(II) fglrx(0): 720x400@70Hz
(II) fglrx(0): 640x480@60Hz
(II) fglrx(0): 640x480@67Hz
(II) fglrx(0): 640x480@72Hz
(II) fglrx(0): 640x480@75Hz
(II) fglrx(0): 800x600@56Hz
(II) fglrx(0): 800x600@60Hz
(II) fglrx(0): 800x600@72Hz
(II) fglrx(0): 800x600@75Hz
(II) fglrx(0): 832x624@75Hz
(II) fglrx(0): 1024x768@60Hz
(II) fglrx(0): 1024x768@70Hz
(II) fglrx(0): 1024x768@75Hz
(II) fglrx(0): 1280x1024@75Hz
(II) fglrx(0): 1152x870@75Hz
(II) fglrx(0): Manufacturer's mask: 0
(II) fglrx(0): Supported Future Video Modes:
(II) fglrx(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) fglrx(0): #1: hsize: 1280 vsize 960 refresh: 60 vid: 16513
(II) fglrx(0): #2: hsize: 1152 vsize 864 refresh: 75 vid: 20337
(II) fglrx(0): Supported additional Video Mode:
(II) fglrx(0): clock: 108.0 MHz Image Size: 376 x 301 mm
(II) fglrx(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
(II) fglrx(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
(II) fglrx(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 81 kHz, PixClock max 140 MHz
(II) fglrx(0): Monitor name: SyncMaster
(II) fglrx(0): Serial No: HMEL205539
(II) fglrx(0): EDID (in hex):
(II) fglrx(0): 00ffffffffffff004c2de50139314a48
(II) fglrx(0): 0710010380261e782ade95a3544c9926
(II) fglrx(0): 0f5054bfef8081808140714f01010101
(II) fglrx(0): 010101010101302a009851002a403070
(II) fglrx(0): 1300782d1100001e000000fd00384c1e
(II) fglrx(0): 510e000a202020202020000000fc0053
(II) fglrx(0): 796e634d61737465720a2020000000ff
(II) fglrx(0): 00484d454c3230353533390a20200056
(II) fglrx(0): End of Display2 EDID data --------------------
(WW) fglrx(0): More than one displays are connected,so clone mode is enabled
(II) fglrx(0): Primary Controller - DFP on secondary TMDS
(II) fglrx(0): Secondary Controller - CRT on secondary DAC
(II) fglrx(0): Internal Desktop Setting: 0x00000008
(II) fglrx(0): POWERplay version 3. 1 power state available:
(II) fglrx(0): 1. 574/682MHz @ 0Hz [enable load balancing]
(==) fglrx(0): QBS disabled
(==) fglrx(0): FAST_SWAP disabled
(==) fglrx(0): PseudoColor visuals disabled
(==) fglrx(0): Using gamma correction (1.0, 1.0, 1.0)
(==) fglrx(0): Center Mode is disabled
(==) fglrx(0): TMDS coherent mode is enabled
(II) fglrx(0): Total of 24 modes found for primary display.
(--) fglrx(0): Virtual size is 1280x1024 (pitch 0)
(**) fglrx(0): *Mode "1280x1024_mine": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
(II) fglrx(0): Modeline "1280x1024_mine"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
(**) fglrx(0): Default mode "1280x1024_mine": 109.6 MHz (scaled from 0.0 MHz), 63.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1280x1024_mine"x60.0 109.62 1280 1336 1472 1720 1024 1024 1026 1062 +vsync (63.7 kHz)
(**) fglrx(0): *Mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
(II) fglrx(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
(**) fglrx(0): *Mode "1280x1024": 109.6 MHz (scaled from 0.0 MHz), 63.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1280x1024"x60.0 109.62 1280 1336 1472 1720 1024 1024 1026 1062 +vsync (63.7 kHz)
(**) fglrx(0): Default mode "1280x960": 108.0 MHz (scaled from 0.0 MHz), 60.0 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 (60.0 kHz)
(**) fglrx(0): Default mode "1280x768": 79.5 MHz (scaled from 0.0 MHz), 47.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1280x768"x60.0 79.50 1280 1344 1472 1664 768 771 778 798 +hsync (47.8 kHz)
(**) fglrx(0): Default mode "1280x720": 74.5 MHz (scaled from 0.0 MHz), 44.8 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1280x720"x60.0 74.48 1280 1336 1472 1664 720 721 724 746 +hsync (44.8 kHz)
(**) fglrx(0): Default mode "1280x720": 60.5 MHz (scaled from 0.0 MHz), 37.0 kHz, 50.0 Hz
(II) fglrx(0): Modeline "1280x720"x50.0 60.46 1280 1328 1456 1632 720 721 724 741 +hsync (37.0 kHz)
(**) fglrx(0): Default mode "1152x864": 81.6 MHz (scaled from 0.0 MHz), 53.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1152x864"x60.0 81.62 1152 1216 1336 1520 864 865 868 895 +hsync (53.7 kHz)
[.. Millions of ModeLine's..]
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(==) fglrx(0): NoAccel = NO
(II) Loading sub module "xaa"
(II) LoadModule: "xaa"
(II) Loading /usr/lib/xorg/modules//libxaa.so
(II) Module xaa: vendor="X.Org Foundation"
compiled for 1.5.3, module version = 1.2.0
ABI class: X.Org Video Driver, version 4.1
(**) fglrx(0): NoDRI = NO
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Reloading /usr/lib/xorg/modules/linux//libfglrxdrm.so
(==) fglrx(0): Capabilities: 0x00000000
(==) fglrx(0): CapabilitiesEx: 0x00000000
(==) fglrx(0): cpuFlags: 0x8000001d
(==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
(**) fglrx(0): Ring buffer size: 8 MB
(**) fglrx(0): KernelModuleParm: "agplock=0"
(II) fglrx(0): [pcie] 262144 kB allocated
(II) fglrx(0): [drm] DRM buffer queue setup: nbufs = 100 bufsize = 65536
(==) fglrx(0): UseFastTLS=0
(==) fglrx(0): BlockSignalsOnLock=1
(II) fglrx(0): Direct rendering enabled
(II) fglrx(0): AC Adapter is used
(II) fglrx(0): Interrupt handler installed at IRQ 16.
(II) fglrx(0): Exposed events to the /proc interface
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] 0 0 0x000a0000 - 0x000affff (0x10000) MS[b](OprU)
[5] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[b](OprU)
[6] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[b](OprU)
[7] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[8] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
[9] 0 0 0x000003b0 - 0x000003bb (0xc) IS[b](OprU)
[10] 0 0 0x000003c0 - 0x000003df (0x20) IS[b](OprU)
(II) fglrx(0): driver needs X.org 1.4.x.y with x.y >= 99.906
(II) fglrx(0): detected X.org 7.4.3.0
(II) Loading extension ATIFGLRXDRI
(II) fglrx(0): doing DRIScreenInit
(II) fglrx(0): DRIScreenInit for fglrx driver
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 13, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 13, (OK)
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 13, (OK)
drmOpenByBusid: drmOpenMinor returns 13
drmOpenByBusid: drmGetBusid reports PCI:1:0:0
(II) fglrx(0): [drm] DRM interface version 1.0
(II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:1:0:0"
(II) fglrx(0): [drm] added 8192 byte SAREA at 0x4d000
(II) fglrx(0): [drm] mapped SAREA 0x4d000 to 0xb7af0000
(II) fglrx(0): [drm] framebuffer handle = 0x4e000
(II) fglrx(0): [drm] added 1 reserved context for kernel
(II) fglrx(0): DRIScreenInit done
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0): Name: fglrx
(II) fglrx(0): Version: 8.56.4
(II) fglrx(0): Date: Dec 1 2008
(II) fglrx(0): Desc: ATI FireGL DRM kernel module
(II) fglrx(0): Kernel Module version matches driver.
(II) fglrx(0): Kernel Module Build Time Information:
(II) fglrx(0): Build-Kernel UTS_RELEASE: 2.6.27-ARCH
(II) fglrx(0): Build-Kernel MODVERSIONS: no
(II) fglrx(0): Build-Kernel __SMP__: no
(II) fglrx(0): Build-Kernel PAGE_SIZE: 0x1000
(II) fglrx(0): [drm] register handle = 0x0004f000
(II) fglrx(0): DRI initialization successfull!
(II) fglrx(0): FBADPhys: 0xc0000000 FBMappedSize: 0x01004000
(II) fglrx(0): FBMM initialized for area (0,0)-(1280,3280)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(1280,1024) (front color buffer - assumption)
(II) fglrx(0): Largest offscreen area available: 1280 x 2256
(==) fglrx(0): Backing store disabled
(II) Loading extension FGLRXEXTENSION
(II) Loading extension ATITVOUT
(**) fglrx(0): DPMS enabled
(**) fglrx(0): Textured Video is enabled.
(II) LoadModule: "glesx"
(II) Loading /usr/lib/xorg/modules//glesx.so
(II) Module glesx: vendor="X.Org Foundation"
compiled for 1.4.99.906, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension GLESX
(II) fglrx(0): GLESX enableFlags = 80
(II) fglrx(0): GLESX is enabled
(**) fglrx(0): Option "XaaNoOffscreenPixmaps" "true"
(II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Solid Lines
Dashed Lines
Setting up tile and stipple cache:
32 128x128 slots
14 256x256 slots
5 512x512 slots
(II) fglrx(0): Acceleration enabled
(II) LoadModule: "amdxmm"
(II) Loading /usr/lib/xorg/modules//amdxmm.so
(II) Module amdxmm: vendor="X.Org Foundation"
compiled for 1.4.99.906, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(WW) fglrx(0): Option "AccelMethod" is not used
(WW) fglrx(0): Option "AccelDFS" is not used
(WW) fglrx(0): Option "GARTSize" is not used
(WW) fglrx(0): Option "BufferSize" is not used
(WW) fglrx(0): Option "UseFBDev" is not used
(WW) fglrx(0): Option "ColorTiling" is not used
(WW) fglrx(0): Option "RenderAccel" is not used
(WW) fglrx(0): Option "SubPixelOrder" is not used
(WW) fglrx(0): Option "DynamicClocks" is not used
(WW) fglrx(0): Option "PCI:1:0:0" is not used
(II) fglrx(0): X context handle = 0x1
(II) fglrx(0): [DRI] installation complete
(==) fglrx(0): Silken mouse enabled
(==) fglrx(0): Using hardware cursor
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 14, (OK)
drmOpenByBusid: Searching for BusID PCI:1:0:0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 14, (OK)
drmOpenByBusid: drmOpenMinor returns 14
drmOpenByBusid: drmGetBusid reports PCI:1:0:0
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
(WW) AIGLX: 3D driver claims to not support visual 0x33
(WW) AIGLX: 3D driver claims to not support visual 0x34
(WW) AIGLX: 3D driver claims to not support visual 0x35
(WW) AIGLX: 3D driver claims to not support visual 0x36
(WW) AIGLX: 3D driver claims to not support visual 0x37
(WW) AIGLX: 3D driver claims to not support visual 0x38
(WW) AIGLX: 3D driver claims to not support visual 0x39
(WW) AIGLX: 3D driver claims to not support visual 0x3a
(WW) AIGLX: 3D driver claims to not support visual 0x3b
(WW) AIGLX: 3D driver claims to not support visual 0x3c
(WW) AIGLX: 3D driver claims to not support visual 0x3d
(WW) AIGLX: 3D driver claims to not support visual 0x3e
(WW) AIGLX: 3D driver claims to not support visual 0x3f
(WW) AIGLX: 3D driver claims to not support visual 0x40
(WW) AIGLX: 3D driver claims to not support visual 0x41
(WW) AIGLX: 3D driver claims to not support visual 0x42
(WW) AIGLX: 3D driver claims to not support visual 0x43
(WW) AIGLX: 3D driver claims to not support visual 0x44
(WW) AIGLX: 3D driver claims to not support visual 0x45
(WW) AIGLX: 3D driver claims to not support visual 0x46
(WW) AIGLX: 3D driver claims to not support visual 0x47
(WW) AIGLX: 3D driver claims to not support visual 0x48
(WW) AIGLX: 3D driver claims to not support visual 0x49
(WW) AIGLX: 3D driver claims to not support visual 0x4a
(WW) AIGLX: 3D driver claims to not support visual 0x4b
(WW) AIGLX: 3D driver claims to not support visual 0x4c
(WW) AIGLX: 3D driver claims to not support visual 0x4d
(WW) AIGLX: 3D driver claims to not support visual 0x4e
(WW) AIGLX: 3D driver claims to not support visual 0x4f
(WW) AIGLX: 3D driver claims to not support visual 0x50
(WW) AIGLX: 3D driver claims to not support visual 0x51
(WW) AIGLX: 3D driver claims to not support visual 0x52
(WW) AIGLX: 3D driver claims to not support visual 0x53
(WW) AIGLX: 3D driver claims to not support visual 0x54
(WW) AIGLX: 3D driver claims to not support visual 0x55
(WW) AIGLX: 3D driver claims to not support visual 0x56
(WW) AIGLX: 3D driver claims to not support visual 0x57
(WW) AIGLX: 3D driver claims to not support visual 0x58
(WW) AIGLX: 3D driver claims to not support visual 0x59
(WW) AIGLX: 3D driver claims to not support visual 0x5a
(WW) AIGLX: 3D driver claims to not support visual 0x5b
(WW) AIGLX: 3D driver claims to not support visual 0x5c
(WW) AIGLX: 3D driver claims to not support visual 0x5d
(WW) AIGLX: 3D driver claims to not support visual 0x5e
(WW) AIGLX: 3D driver claims to not support visual 0x5f
(WW) AIGLX: 3D driver claims to not support visual 0x60
(WW) AIGLX: 3D driver claims to not support visual 0x61
(WW) AIGLX: 3D driver claims to not support visual 0x62
(WW) AIGLX: 3D driver claims to not support visual 0x63
(WW) AIGLX: 3D driver claims to not support visual 0x64
(WW) AIGLX: 3D driver claims to not support visual 0x65
(WW) AIGLX: 3D driver claims to not support visual 0x66
(WW) AIGLX: 3D driver claims to not support visual 0x67
(WW) AIGLX: 3D driver claims to not support visual 0x68
(WW) AIGLX: 3D driver claims to not support visual 0x69
(WW) AIGLX: 3D driver claims to not support visual 0x6a
(WW) AIGLX: 3D driver claims to not support visual 0x6b
(WW) AIGLX: 3D driver claims to not support visual 0x6c
(WW) AIGLX: 3D driver claims to not support visual 0x6d
(WW) AIGLX: 3D driver claims to not support visual 0x6e
(WW) AIGLX: 3D driver claims to not support visual 0x6f
(WW) AIGLX: 3D driver claims to not support visual 0x70
(WW) AIGLX: 3D driver claims to not support visual 0x71
(WW) AIGLX: 3D driver claims to not support visual 0x72
(II) AIGLX: Loaded and initialized /usr/lib/dri/fglrx_dri.so
(II) GLX: Initialized DRI GL provider for screen 0
(II) fglrx(0): Shutdown CMMQS
(II) fglrx(0): [drm] removed 1 reserved context for kernel
(II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0x4d000 at 0xb7af0000
Thanks :)
edit: weird thing (or not) but DPMS (or whatever it is, the thing that turns off my monitor after some time) seems to work, altough moving the mouse or pressing the keyboard doesn't wake up the screen. Has this something to do with my mouse and keyboard not being recognized by xorg ?
edit2: omg yes it is ! I added:
urxvtc -e 'screen'
so when I startx an un-window-managered fullscreen terminal launches with a screen session, and if I ssh on it I can type in this terminal from another computer, and the screen actually displays what I'm typing, so that's definitely an input problem !
Final Edit: Well all solved, concerning the "frozen" stuff, it was just that my keyboard and mouse weren't detected because of the new hotpulg thingy (check http://wiki.archlinux.org/index.php/Xor … otplugging for more info, or just add 'hal' to your rc.conf), then restored my original xorg.conf, rebooted and it all went back to normal (: ). Hope this helps.
Last edited by arsenist (2008-12-13 03:28:42)

Has this something to do with my mouse and keyboard not being recognized by xorg
Hmm, I wonder what it would reveal if someone read the news? http://www.archlinux.org/news/424/
Even your Xorg.0.log is telling you the problem.
(WW) AllowEmptyInput is on, devices using drivers 'kbd' or 'mouse' will be disabled.
(WW) Disabling Keyboard0
(WW) Disabling PS/2 Mouse
Last edited by jacko (2008-12-13 03:28:40)

Gnu Screen theme cycle with keybinding

A guy at work did this and shared with me, so i thought I'd continue spreadin the love. If you have multiple gnu screen sessions going at once, wouldn't it be nice to visually tell them apart without spending time to read the session name of each or trying to see what was going on within each?
The best way would be to color code the caption and hardlinestatus lines and be able to easily select a "color" per screen session and that's what he and I did. Using C-g, we/you can easily cycle through various "themes". This could also be useful if you wanted to cycle through mutiple hardstatus lines that displayed different information too if that's the route you'd like to go. Anyways here it goes:
#terminfo and termcap for nice 256 color terminal
# allow bold colors - necessary for some reason
attrcolor b ".I"
# tell screen how to set colors. AB = background, AF=foreground
termcapinfo xterm 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'
# erase background with current bg color
defbce "on"
startup_message off
bindkey ^G screen screen_theme.sh
caption always "%{= KW}%-w%{= gW}%n %t%{-}%+w %-="
hardstatus alwayslastline "%{= kW} %-= %{= kG}Session:%u%{= kW} %5` | %{= kG}Host:%{= kW} %H | %{= kG} MEM:%{= kW} %2`MB |%{= kG} SW: %{= kW}%3`MB | %{= kG}Unread: %{= kW} %4` | %m/%d %C %A"
vbell off
#Backticks to display information in status bar
backtick 1 60 60 $HOME/bin/get_uptime
backtick 2 60 60 $HOME/bin/get_freemem
backtick 3 60 60 $HOME/bin/get_freeswap
backtick 4 60 60 $HOME/bin/get_gmail
backtick 5 60 60 $HOME/bin/get_sessionname
defscrollback 5000
screen -t root 0 sudo -s
screen -t shell 1 bash
screen -t shell 2 bash
screen -t shell 3 bash
screen -t shell 4 bash
screen -t shell 5 bash
screen -t shell 6 bash
screen -t shell 7 bash
screen -M -t irc 8 irssi
screen -t home 9 ssh home
select 1
This script resides in ~/bin which is in my path. screen_theme.sh:
#!/bin/bash
INDEXFILE="$HOME/bin/themes/theme_index"
# if this is the first time then set
# the index to 0
if [[ ! -e $INDEXFILE ]]
then
echo 0 > $INDEXFILE
fi
THEMENO=`cat $INDEXFILE`
THEMEMAX=5
if [[ $THEMENO -eq $THEMEMAX ]]
then
THEMENO=0
else
THEMENO=`expr $THEMENO + 1`
fi
echo $THEMENO > $INDEXFILE
THEMEFILE=$HOME/bin/themes/theme${THEMENO}
if [[ -e $THEMEFILE ]]
then
bash $THEMEFILE $STY
else
# reset the index back to zero if broken
echo 0 > $INDEXFILE
fi
then I created a directory ~/bin/themes. Within that directory I have the following files:
$ ls themes/
theme0 theme1 theme2 theme3 theme4 theme5 theme_index
Each theme file is another color theme, the index just holds a count of the number of themes.
An example of theme0 ( remember when doing yours to escape your backticks, otherwise it'll break).
#!/bin/bash
# yellow
SESSION=$1
screen -S $SESSION -X caption always "%{= KW}%-w%{= yk}%n %t%{-}%+w %-="
screen -S $SESSION -X hardstatus alwayslastline "%{= kW} %-= %{= ky}Session: %u%{= kW}%5\` | %{= ky}Host:%{= kW} %H | %{= ky} MEM:%{= kW} %2\`MB |%{= ky} SW: %{= kW}%3\`MB | %{= ky}Unread: %{= kW}%4\` | %m/%d %c"
Here's how my screen started:
http://tuxtraining.com/images/screen1.png
After C-g
http://tuxtraining.com/images/screen2.png
After C-g again
http://tuxtraining.com/images/screen3.png
and so on.
Last edited by scv5 (2009-10-12 16:38:51)

thayer wrote:
steve___ wrote:
Lich wrote:... useless for most of us as we only use one screen session normally.
How do you know this?
Just a guess, but doesn't that sort of defeat the purpose of a multiplexer? I mean it's like running 20 instances of firefox instead of using a single firefox window with 20 tabs. I'm sure some folks prefer the former, but I think it's safe to say the majority use the latter method.
Sort of, I find screen becomes difficult to manage once we're talking more than the original 0-9 windows and you have to C-a-##, there's also the issue of screenspace. With firefox i can list my tabs vertically giving me a lot more room to manage my tabs, screen doesn't have that option, so they go horizontally. If i name all my tabs after the IP or name of the machine theiy are logged into, approach 15-20 windows really creaps on the screenspace.
So typically what i do is have four shells open (grouped together or done in something like terminotor, or tabbed in flux or pekwm) each with 0-9 shells a piece, each session organized into type of servers. So the upper left may be the email systems i support, the uppser right screen session may hold all the shell of our public facing web environment, bottom left is my local box, bottom right being misc boxes (dns servers, nis/ldap servers, various developement boxes..) you get the hint.
take into consideration i get one of these going per monitor that gives me approximately 80 shells, which is quite unmanagable in one screen session if you ask me.

GNU Screen mouse scrolling shows only empty lines

Hi,
I've got a problem with using my mouse wheel to scroll in GNU Screen.
This is the content of my .screenrc:
defscrollback 10000
hardstatus off
termcapinfo xterm* ti@:te@
altscreen on
With this settings, It kinda works: I can scroll up, but instead of showing the previous output, I just shows blank lines.
I can actually scroll up by entering Screen's copy mode using CTRL-A ESC and then using the Arrow-keys or PageUp.
Furthermore, if I then scroll with my mouse wheel, I can also scroll the lines that were displayed in copy mode, but if I try to scroll further than I scrolled in copy mode, I still see blank lines.
Thanks in advance!

hume's doona wrote:
Are you configuring for the nvidia card?
#sudo nvidia-settings
and set it to twin view in the gui?
No I think the problem is more basic than that...he's trying to use an ATi card and an Nvidia card simultaneously. Something that I don't think will work.
It also dependent on what drivers he is trying to use, as the (new) Nvidia proprietary driver only supports GeForce4 series chips and up...and the OP has an even older card than that. The legacy Nvidia-96.xx driver does support his chipset, but 96.xx does not work with Xorg1.8 last I knew. see: http://www.archlinux.org/news/502/
Twinview does not exist in the Nouveau drivers, so one has to use xrandr: http://wiki.archlinux.org/index.php/Nouveau
Last edited by Skripka (2010-08-14 14:16:25)

GNU Screen prints back garbage?

So. I've noticed an odd thing happening. Eventually, while running GNU Screen, lynx will start spitting out garbage characters at me. It usually starts with lynx, and then spreads to my other programs. http://homepage.mac.com/jamesebailey/screen_garbage.png is a picture of irssi with the garbage. I've only just started using screen, and I don't have the problem when I log in remotely, but only on my local login. I guess I could just SSH into my home computer while sitting in front of it, but that just seems silly, and there's got to be an explanation and solution for this, other than just working around it.
Maybe not.

Yeah, I know a couple of ways of getting it to do that, unfortunately, I've done none. Usually, I just switch back to a screen and see garbage. Moments later, all of my screens have garbage. Usually quitting the program and then quitting terminal gets rid of it, I'm just wondering if anyone knows what causes it and how to prevent it.

Using "Window" (Super_L) key as escape in GNU Screen

I've been trying to map the Windows key (to the left of the space bar) to be the escape key in GNU Screen (as opposed to ^A) with no luck. xev gives me that it generates keycode 133 and its keysym is "Super_L" so its definitely recognized by the system, but I don't know what I can write in my .screenrc to be able to use it as an escape key. I've tried googling how to do it, but the solution another person found didn't work for me (use xmodmap to map keycode 133 to something else - like F13, and then get the literal value in vim by pressing ctrl+v and the key (it generated ^[[3~ or something similar) and then putting that in the .screenrc file).
Has anyone else solved this?

I believe you can use the xmodmap method, although it may cause you some problems. Try this:
$ xmodmap -e "keycode 133 = F19"
then put the following line in your .screenrc:
bindkey -k F9 command
Note the difference between using 'F19' for xmodmap and using 'F9' in the bindkey command. This is due to bindkey using the termcap database for specifing keys. The main problem here, as far as I can tell, is that the termcap database doesn't have any notion of the "Super_L" or "Super_R" keys, thus you have to do this strange xmodmap assignment of keycode 133 to some key that bindkey can recognize. This will work even if your keyboard doesn't have an F19 key as my example shows. Of course, you don't have to use function key F19; you can use any key on your keyboard. The important thing to remember is that the bindkey command in your .screenrc file uses the termcap database (see man termcap) to determine what key to use, and the xmodmap command uses some other mechanism. You have to understand how to specify the keys for each case.
Other possibilities:
xmodmap -e "keycode 133 = F1" <==> bindkey -k k1 command
xmodmap -e "keycode 133 = F2" <==> bindkey -k k2 command
xmodmap -e "keycode 133 = F3" <==> bindkey -k k3 command
xmodmap -e "keycode 133 = F9" <==> bindkey -k k9 command
xmodmap -e "keycode 133 = F10" <==> bindkey -k k; command
xmodmap -e "keycode 133 = F11" <==> bindkey -k F1 command
etc.
This could cause a problem if some other application you use (like your window manager or desktop environment) uses 'Super_L' for something. I really don't understand exactly how all this works so I don't know how you could fix a conflict like that.
Finally, when you remap 'keycode 133' to some other key, then pressing that key will now generate some character. Pressing the windows key when not in screen, at least on my system, caused a '~' to be printed. I don't know how you would get rid of this.

GNU Screen Scroll problem

Hello everyone, I'm a new member in the Arch community and I'm enjoying myself a lot by using this distribution.
the problem I'm having is that I can't seem to get the mouse scrollwheel to scroll upwards in GNU Screen running in a Terminator emulator once the terminal is filled.
I have searched a bit and found that I should put something like this in my ~/.screenrc
terminfo xterm* ti@:te@
I have changed the xterm* to terminator* to match my emulator, my full .screenrc is as follows
bind c screen 1
bind ^c screen 1
bind 0 select 10
screen 1
term screen-256color
hardstatus alwayslastline '%{= g}[ %{G}%H %{g}][%= %{= w}%?%-Lw%?%{= R}%n*%f %t%?%{= R}(%u)%?%{= w}%+Lw%?%= %{= g}][%{B}%Y-%m-%d%{g}]'
startup_message off
terminfo terminator* ti@:te@
vbell off
altscreen on
defscrollback 5000
When I first open screen I can scroll up and down using the mouse wheel, but once the terminal gets filled all the way, the mouse wheel starts to show the command history instead of scrolling, which is a pretty odd behavior in my point of view.
Anyone knows why is that happening?

geekinthesticks wrote:I think I am missing something obvious and simple, but can't see what it is!
They're called code tags
I can't help with the problem directly, but those who can will probably be more inclined to do so if you include file contents of command output in [ code ] ... [ /code ] tags to keep it clean and readable.

Conky inside GNU/Screen session

hi! i was looking around but found nothing similar to what i want...
i was searching for a possibility of use conky INSIDE a terminal instead of the root window (aka "desktop") because i barely see my wallpaper, it's always covered with urxvtc sessions in dwm, so i have a detailed bottom bar inside dwm bottom bar, but i like to trim it to say audio volume + clock and have a conky or another similar program inside a gnu/screen "tab" showing my system activity, i surely want disk I/O usage and free/used space for example
the thing with conky-cli is that it behaves like this: (not cleaning the screen with every refresh)
[aleyscha@aleyscha 39 ~]$ conky
5d 12h/12C | 12%/36.0C/2/140 | 552/415 | /sdb1:12G /sdd1:60G /cdrom:n/a | 90% | 0k/0k | 0/0 | 20:22 07/10/2008
5d 12h/12C | 20%/36.0C/2/140 | 552/415 | /sdb1:12G /sdd1:60G /cdrom:n/a | 90% | 16k/7k | 0/0 | 20:22 07/10/2008
5d 12h/12C | 11%/36.0C/1/140 | 552/415 | /sdb1:12G /sdd1:60G /cdrom:n/a | 90% | 35k/14k | 0/0 | 20:22 07/10/2008
5d 12h/12C | 12%/36.0C/3/140 | 552/415 | /sdb1:12G /sdd1:60G /cdrom:n/a | 90% | 39k/14k | 0/0 | 20:22 07/10/2008
^C5d 12h/12C | 16%/36.0C/1/140 | 552/415 | /sdb1:12G /sdd1:60G /cdrom:n/a | 90% | 39k/14k | 0/0 | 20:22 07/10/2008
Conky: received SIGINT or SIGTERM to terminate. bye!
[aleyscha@aleyscha 40 ~]$

LOL, DONE!!
${execp clear} was the answer
here's my conky(cli) rc file (needs work... i'll stole some from your conky configs and screenshots thread, huaahahahaha)
background no
out_to_console yes
update_interval 2.0
total_run_times 0
uppercase no
TEXT
${execp clear}
${time %l:%M:%p}
Uptime: $uptime
CPU: ${cpu}% ${cpubar 5,85} Disk I/O: ${diskio}
RAM Usage: $mem/$memmax - $memperc%
Swap Usage: $swap/$swapmax - $swapperc%
Net Down: ${downspeed eth0} k/s Net Up: ${upspeed eth0} k/s
File systems:
/ ${fs_used /}/${fs_size /}${alignr}${fs_bar 5,120 /}
/home ${fs_used /home}/${fs_size /home}${alignr}${fs_bar 5,120 /home}
/sda1 ${fs_used /sda1}/${fs_size /sda1}${alignr}${fs_bar 5,120 /sda1}
/sda6 ${fs_used /sda6}/${fs_size /sda6}${alignr}${fs_bar 5,120 /sda6}
/downloads ${fs_used /downloads}/${fs_size /downloads}${alignr}${fs_bar 5,120 /downloads}
/sdb5 ${fs_used /sdb5}/${fs_size /sdb5}${alignr}${fs_bar 5,120 /sdb5}
/sdc1 ${fs_used /sdc1}/${fs_size /sdc1}${alignr}${fs_bar 5,120 /sdc1}
/sdd1 ${fs_used /sdd1}/${fs_size /sdd1}${alignr}${fs_bar 5,120 /sdd1}
Top Processes:
Name PID CPU% MEM%
${top name 1} ${top pid 1} ${top cpu 1} ${top mem 1}
${top name 2} ${top pid 2} ${top cpu 2} ${top mem 2}
${top name 3} ${top pid 3} ${top cpu 3} ${top mem 3}
${top name 4} ${top pid 4} ${top cpu 4} ${top mem 4}
Mem usage
${top_mem name 1} ${top_mem pid 1} ${top_mem cpu 1} ${top_mem mem 1}
${top_mem name 2} ${top_mem pid 2} ${top_mem cpu 2} ${top_mem mem 2}
${top_mem name 3} ${top_mem pid 3} ${top_mem cpu 3} ${top_mem mem 3}
${top_mem name 4} ${top_mem pid 4} ${top_mem cpu 4} ${top_mem mem 4}

[SOLVED] GNU Screen - sessions always dead after restart

I recently started using GNU screen. I'm able to detach and reattach sessions normally, except after a restart. Then any detached sessions are marked as dead and all I can do is run a screen -wipe. My sessions are stored in ~/.screen.
I've searched the web and forums but no one seems to have had this problem.
Any ideas? Screen's a lot less useful if I can't reattach after restarting.
Last edited by noahsark1126 (2009-08-18 05:14:42)

This is sort of related, but sometimes it is possible to use special software to suspend an application as a file, which could possibly be set up with screen to provide a rebootable state. However this software seems to be fairly hard to find and get working well enough to be usable. If you want to investigate more, you can probably google for something like "linux application freezing" or "linux application checkpointing".
Actually I just found the software I was thinking of as I'm typing this, http://cryopid.berlios.de/. The page doesn't seem to be loading for me, but I think I have used this in the past with limited success. Not sure if it up to date with the latest kernels however.

Help! When I select "Phone" it tries to open and gives me a white screen and closes. I cannot view my missed calls or voicemails.

If anyone knows anything about this...
When I select "Phone" on my home screen the iPhone attempts to open it, brings up a white screen and then will shut back down. I have 8 missed calls or voicemails yesterday and I couldn't check any of them. Does this happen to anyone else?
Also, when I receive a call and I answer it does not give me the ability to end call or any of my options (sources, keypad,etc.) during the call.
Basically, I can't do anything with my contacts, favorites, missed calls or voicemails.
Can someone please help?

I have tried that multiple times. I have also made sure that I have the latest updates. Would haveing 27,000+ contacts have anything to do with it?
Sometimes it works and sometimes it doesn't

GNU Screen and framebuffer (uvesafb)

Similar Messages

Maybe you are looking for