[Solved] Virtual terminals/agetty overhanging screen.

I've got a strange problem on my Asus A6Jc lappy with nVidia 7300 Go card and 1280x800 screen. X/Gnome/KDE/Openbox/Whatever is fine and acts normally, but the virtual terminals (Ctrl-Alt-F[1-6]) are bigger than my physical screen (vertically). Not a problem to start with, and even if the terminal is used for more than a few commands, a 'clear' gets it usable again, but opening nano/vi/links chops off the last 4 or 5 lines of text.
I don't think I've done anything particularly strange in the config files, and I've not got the problem in other distros. vbeinfo and hwinfo --framebuffer both give the same results (aside from the +-512 to convert between linux and vesa modes) but these only include 320x240, 640x480, 800x600, and 1024x768 at various bit depths, with no mention of 1280x800. I've searched the forum and google, although, to be fair, I'm not sure of the best things to search for. My /etc/inittab looks sane, and agetty takes no size arguments anyway that I can see. The other thing I've noticed is that the grub terminal works correctly - ie, doesn't overhang, its only the linux virtual terminals. I'm not sure if the boot messages fall off the edge, since they go past too quick for me.
Any ideas where to look?
Last edited by mjc506 (2010-04-09 01:06:54)

On several laptops the kernel option vga=864 or vga=865 will select the widescreen resolution for the framebuffer. However 1280x800 is not an official VESA mode so these codes may or may not work depending on your laptop's manufacturer.
If you use grub to boot other distros that work correctly you might want to take a look at the config file and see what they use as kernel options.

Similar Messages

  • Startx works fine... but kills my virtual terminals.

    What I mean by this is when I type in startx all goes well but as soon as I (Alt+F1 - F6) It just displays a black window with a flashing cursor similar to that of a "Pre" boot screen.
    To clear things up Virtual Terminals work just fine before startx in fact you start at TTY1 be default.
    How do I fix this?

    Any errors in the logs? What graphics driver are you using?

  • I solve my problem of black screen when starting up my Mac pro, namely by the button lighting and then i saw the login screen. Hopefully it works for you too.

    I solve my problem of black screen when starting up my Mac pro, namely by using the lighting button and then i saw the login screen. Hopefully it works for you.

    It was the PRAM.

  • Virtual terminals on Solaris 8

    Does anyone know how to get virtual terminals running on Solaris 8? According to the xfree86 VT-switching documentation there is driver named chanmux which is missing. Was it renamed or is there another prodecure?

    I think VT was ripped out of S8.

  • Configuring virtual terminals

    Hi there
    Sorry if this isn't the correct terminology. I've seen someone on Gentoo where when they go to terminal 12 (Ctrl + Alt + F12) it shows them what is currently running in /var/log/messages and I thought that I'd like to try and get this working on my Arch system.
    Any tips?
    Thanks
    eskay

    The virtual terminals will display whatever's sent to them, so just write whatever text you like to /dev/vc/n, where n is the number of the VT you want to use. syslog is handy for this; just add something like this to the end of /etc/syslog-ng.conf:
    destination vt_12 { file("/dev/vc/12"); };
    log { source(src); filter(f_messages); destination(vt_12); };
    Replace f_messages with any of the filters defined in the file to get other information. You can even leave out the filter, if you want to see everything.

  • My iphone  screen has gone white with a few grey lines down the right hand side.. Has anyone any ideas how I can solve this and get my screen back to normal..? Thanks

    my iphone screen has gone white with a few grey lines down the right hand side.. Has anyone any idea how I can solve this and get my screen back to normal..? Thanks

    Hi tag71,
    If you are having issues with the display on your iPhone, you may find the Display portion of the following article helpful:
    iPhone: Hardware troubleshooting
    http://support.apple.com/kb/ts2802
    Regards,
    - Brenden

  • [SOLVED] Virtual screen resolution in xorg.conf being ignored

    I'm trying to configure a dual monitor set up but xrandr is telling me the max screen size is 1600x1600. I have already enterd a virtual resolution in xorg.conf.
    Section "ServerLayout"
    Identifier "aticonfig Layout"
    Screen 0 "aticonfig-Screen[0]-0" 0 0
    EndSection
    Section "Files"
    EndSection
    Section "Module"
    EndSection
    Section "Monitor"
    Identifier "aticonfig-Monitor[0]-0"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    EndSection
    Section "Device"
    Identifier "aticonfig-Device[0]-0"
    Driver "fglrx"
    BusID "PCI:1:0:0"
    EndSection
    Section "Screen"
    Identifier "aticonfig-Screen[0]-0"
    Device "aticonfig-Device[0]-0"
    Monitor "aticonfig-Monitor[0]-0"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 24
    Virtual 2832 1050
    EndSubSection
    EndSection
    When I first installed Arch I was using the radeon drivers. I had no problem configuring my monitors the way I wanted. Now I'm using catalyst and getting errors.
    Am I just doing something wrong?
    Last edited by thetoxikavenger (2010-06-06 15:58:18)

    I didn't really fix the issue with xrandr, but I did manage to get my dual monitors to work with Xinerama.

  • [SOLVED] virtual tty covering only part of screen; 2nd graphics chip?

    Hi there!
    I'm running Arch (KDE 4.6.1) on an intel Essential D510mo mobo. Now I'm seeing some graphics issues, which seem interrelated to me:
    1. on the tty the output extends only over part of the screen: the right (estimated) quarter and the bottom (estimated) quarter stay black
    2. plasma device notifications pop up roughly at the same spot where my tty ends. The rest of KDE 'looks normally', extending to the physical borders of my screen
    3. KDE's splash screen (set to Standard, 'Air and Horos Splash Screen') shows two wallpapers: one covering the whole screen, underneath a smaller copy of itself in the same reduced size as seen in 1 and 2
    4. sometimes (mainly when the screen gets driven by my other PC on its DVI-D input) kdm comes up in a lower *resolution*. This lower resolution *might* correspond to the same size as seen in 1 to 3, but it's hard to tell
    Some details regarding my setup:
    - The board is connected to a 1680x1050 TFT via its VGA input.
    - I *think* I'm running KMS (at least switching between TTY's and X works instantly).
    - krandrtray talks of my mobo having two connectors: one is called LVDS1, allowing a resolution of up to 1280x800, the other is called VGA1 allowing a resolution of up to 1680x1050. The ratio of these resolutions roughly corresponds to the two screen sizes I've spoken about in 1-3 above. When clicking krandrtray's 'identify screens', both 'LVDS1' and 'VGA1' are shown on my one physical TFT, slightly shifted (I assume they both are shown in the 'center' of their respective screens). So my mobo seem to think it can drive two screen simultaneously. I don't think so, but I may be wrong.
    - Some time ago, when kdm almost always came up in the wrong resolution, I created a /etc/X11/xorg.conf.d/15-edid.conf to try to force the graphics driver to run at 1680x1050:
    Section "Screen"
    Identifier "Default Screen"
    Device "Intel Corporation "
    Monitor "Generic Monitor"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    Modes "1680x1050"
    EndSubSection
    EndSection
    I know I'm being terribly vague, sorry for that. If there's any further information you need, I'll be glad to provide it, but at the moment I don't know what to look for. Still, I'd be grateful for any help offered. I'm pretty sure the solution is embarassingly simple.
    Kind regards,
    Rufus
    P.S.: Here go the relevant parts of Xorg.0.log. To my untrained eye, Xorg seems to see two graphics chips:
    [ 8064.638] (II) LoadModule: "glx"
    [ 8064.639] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 8064.680] (II) Module glx: vendor="X.Org Foundation"
    [ 8064.681] compiled for 1.9.4.901, module version = 1.0.0
    [ 8064.681] ABI class: X.Org Server Extension, version 4.0
    [ 8064.681] (==) AIGLX enabled
    [ 8064.681] (II) Loading extension GLX
    [ 8064.681] (II) LoadModule: "record"
    [ 8064.681] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 8064.682] (II) Module record: vendor="X.Org Foundation"
    [ 8064.682] compiled for 1.9.4.901, module version = 1.13.0
    [ 8064.682] Module class: X.Org Server Extension
    [ 8064.682] ABI class: X.Org Server Extension, version 4.0
    [ 8064.682] (II) Loading extension RECORD
    [ 8064.682] (II) LoadModule: "dri"
    [ 8064.682] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 8064.683] (II) Module dri: vendor="X.Org Foundation"
    [ 8064.683] compiled for 1.9.4.901, module version = 1.0.0
    [ 8064.683] ABI class: X.Org Server Extension, version 4.0
    [ 8064.683] (II) Loading extension XFree86-DRI
    [ 8064.683] (II) LoadModule: "dri2"
    [ 8064.683] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 8064.684] (II) Module dri2: vendor="X.Org Foundation"
    [ 8064.684] compiled for 1.9.4.901, module version = 1.2.0
    [ 8064.685] ABI class: X.Org Server Extension, version 4.0
    [ 8064.685] (II) Loading extension DRI2
    [ 8064.685] (==) Matched intel as autoconfigured driver 0
    [ 8064.685] (==) Matched vesa as autoconfigured driver 1
    [ 8064.685] (==) Matched fbdev as autoconfigured driver 2
    [ 8064.685] (==) Assigned the driver to the xf86ConfigLayout
    [ 8064.685] (II) LoadModule: "intel"
    [ 8064.686] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 8064.688] (II) Module intel: vendor="X.Org Foundation"
    [ 8064.688] compiled for 1.9.4, module version = 2.14.0
    [ 8064.688] Module class: X.Org Video Driver
    [ 8064.688] ABI class: X.Org Video Driver, version 8.0
    [ 8064.688] (II) LoadModule: "vesa"
    [ 8064.690] (WW) Warning, couldn't open module vesa
    [ 8064.690] (II) UnloadModule: "vesa"
    [ 8064.690] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 8064.690] (II) LoadModule: "fbdev"
    [ 8064.691] (WW) Warning, couldn't open module fbdev
    [ 8064.691] (II) UnloadModule: "fbdev"
    [ 8064.691] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 8064.691] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
    i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
    E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
    965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
    4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
    Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge,
    Sandybridge, Sandybridge
    [ 8064.693] (++) using VT number 7
    [ 8064.729] drmOpenDevice: node name is /dev/dri/card0
    [ 8064.729] drmOpenDevice: open result is 8, (OK)
    [ 8064.729] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    [ 8064.729] drmOpenDevice: node name is /dev/dri/card0
    [ 8064.729] drmOpenDevice: open result is 8, (OK)
    [ 8064.729] drmOpenByBusid: drmOpenMinor returns 8
    [ 8064.730] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    [ 8064.730] (**) intel(0): Depth 24, (--) framebuffer bpp 32
    [ 8064.730] (==) intel(0): RGB weight 888
    [ 8064.730] (==) intel(0): Default visual is TrueColor
    [ 8064.730] (II) intel(0): Integrated Graphics Chipset: Intel(R) Pineview G
    [ 8064.730] (--) intel(0): Chipset: "Pineview G"
    [ 8064.730] (**) intel(0): Tiling enabled
    [ 8064.730] (**) intel(0): SwapBuffers wait enabled
    [ 8064.730] (==) intel(0): video overlay key set to 0x101fe
    [ 8064.731] (II) intel(0): Output LVDS1 has no monitor section
    [ 8064.811] (II) intel(0): Output VGA1 has no monitor section
    [ 8064.811] (II) intel(0): EDID for output LVDS1
    [ 8064.812] (II) intel(0): Not using default mode "320x240" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "400x300" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "512x384" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "640x480" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "640x512" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "800x600" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "896x672" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "928x696" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "960x720" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "700x525" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Not using default mode "1024x768" (doublescan mode not supported)
    [ 8064.812] (II) intel(0): Printing probed modes for output LVDS1
    [ 8064.812] (II) intel(0): Modeline "1280x800"x58.1 68.90 1280 1292 1340 1440 800 804 807 823 -hsync -vsync (47.8 kHz)
    [ 8064.812] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
    [ 8064.813] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
    [ 8064.813] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
    [ 8064.813] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
    [ 8064.874] (II) intel(0): EDID for output VGA1
    [ 8064.874] (II) intel(0): Manufacturer: MAX Model: 7d5 Serial#: 1
    [ 8064.874] (II) intel(0): Year: 2006 Week: 39
    [ 8064.874] (II) intel(0): EDID Version: 1.3
    [ 8064.874] (II) intel(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
    [ 8064.874] (II) intel(0): Sync: Separate Composite SyncOnGreen
    [ 8064.874] (II) intel(0): Max Image Size [cm]: horiz.: 43 vert.: 27
    [ 8064.874] (II) intel(0): Gamma: 2.20
    [ 8064.874] (II) intel(0): DPMS capabilities: Off; RGB/Color Display
    [ 8064.874] (II) intel(0): Default color space is primary color space
    [ 8064.875] (II) intel(0): First detailed timing is preferred mode
    [ 8064.875] (II) intel(0): redX: 0.640 redY: 0.340 greenX: 0.295 greenY: 0.610
    [ 8064.875] (II) intel(0): blueX: 0.145 blueY: 0.070 whiteX: 0.313 whiteY: 0.329
    [ 8064.875] (II) intel(0): Supported established timings:
    [ 8064.875] (II) intel(0): 720x400@70Hz
    [ 8064.875] (II) intel(0): 640x480@60Hz
    [ 8064.875] (II) intel(0): 640x480@67Hz
    [ 8064.875] (II) intel(0): 640x480@72Hz
    [ 8064.875] (II) intel(0): 640x480@75Hz
    [ 8064.875] (II) intel(0): 800x600@56Hz
    [ 8064.875] (II) intel(0): 800x600@60Hz
    [ 8064.875] (II) intel(0): 800x600@72Hz
    [ 8064.875] (II) intel(0): 800x600@75Hz
    [ 8064.875] (II) intel(0): 832x624@75Hz
    [ 8064.875] (II) intel(0): 1024x768@60Hz
    [ 8064.875] (II) intel(0): 1024x768@70Hz
    [ 8064.875] (II) intel(0): 1024x768@75Hz
    [ 8064.875] (II) intel(0): 1280x1024@75Hz
    [ 8064.876] (II) intel(0): Manufacturer's mask: 0
    [ 8064.876] (II) intel(0): Supported standard timings:
    [ 8064.876] (II) intel(0): #0: hsize: 640 vsize 400 refresh: 70 vid: 2609
    [ 8064.876] (II) intel(0): #1: hsize: 1024 vsize 768 refresh: 72 vid: 19553
    [ 8064.876] (II) intel(0): #2: hsize: 1152 vsize 864 refresh: 75 vid: 20337
    [ 8064.876] (II) intel(0): #3: hsize: 1280 vsize 960 refresh: 60 vid: 16513
    [ 8064.876] (II) intel(0): #4: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 8064.876] (II) intel(0): #5: hsize: 1440 vsize 900 refresh: 75 vid: 3989
    [ 8064.876] (II) intel(0): Supported detailed timing:
    [ 8064.876] (II) intel(0): clock: 146.2 MHz Image Size: 433 x 270 mm
    [ 8064.876] (II) intel(0): h_active: 1680 h_sync: 1784 h_sync_end 1960 h_blank_end 2240 h_border: 0
    [ 8064.876] (II) intel(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: 1089 v_border: 0
    [ 8064.876] (II) intel(0): Ranges: V min: 56 V max: 75 Hz, H min: 31 H max: 83 kHz, PixClock max 155 MHz
    [ 8064.876] (II) intel(0): Monitor name: B102035W
    [ 8064.876] (II) intel(0): EDID (in hex):
    [ 8064.876] (II) intel(0): 00ffffffffffff003438d50701000000
    [ 8064.877] (II) intel(0): 271001030e2b1b782ec905a3574b9c25
    [ 8064.877] (II) intel(0): 125054bfef00310a614c714f81408180
    [ 8064.877] (II) intel(0): 950f0101010121399030621a274068b0
    [ 8064.877] (II) intel(0): 3600b10e1100001e0000000000000000
    [ 8064.877] (II) intel(0): 00000000000000000000000000fd0038
    [ 8064.877] (II) intel(0): 4b1f530f000a202020202020000000fc
    [ 8064.877] (II) intel(0): 0042313032303335570a2020202000f0
    [ 8064.877] (II) intel(0): Printing probed modes for output VGA1
    [ 8064.877] (II) intel(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 +hsync +vsync (65.3 kHz)
    [ 8064.877] (II) intel(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
    [ 8064.877] (II) intel(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
    [ 8064.877] (II) intel(0): Modeline "1440x900"x75.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz)
    [ 8064.877] (II) intel(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz)
    [ 8064.877] (II) intel(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
    [ 8064.878] (II) intel(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz)
    [ 8064.878] (II) intel(0): Modeline "1024x768"x72.0 78.44 1024 1080 1192 1360 768 769 772 801 -hsync +vsync (57.7 kHz)
    [ 8064.878] (II) intel(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
    [ 8064.878] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
    [ 8064.878] (II) intel(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
    [ 8064.878] (II) intel(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
    [ 8064.878] (II) intel(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
    [ 8064.878] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
    [ 8064.878] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
    [ 8064.878] (II) intel(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz)
    [ 8064.878] (II) intel(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
    [ 8064.878] (II) intel(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
    [ 8064.878] (II) intel(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
    [ 8064.879] (II) intel(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
    [ 8064.879] (II) intel(0): Output LVDS1 connected
    [ 8064.879] (II) intel(0): Output VGA1 connected
    [ 8064.879] (II) intel(0): Using user preference for initial modes
    [ 8064.879] (II) intel(0): Output LVDS1 using initial mode 1280x800
    [ 8064.879] (II) intel(0): Output VGA1 using initial mode 1680x1050
    [ 8064.879] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 8064.879] (II) intel(0): Kernel page flipping support detected, enabling
    [ 8064.879] (==) intel(0): DPI set to (96, 96)
    [ 8064.879] (II) Loading sub module "fb"
    [ 8064.879] (II) LoadModule: "fb"
    [ 8064.880] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 8064.882] (II) Module fb: vendor="X.Org Foundation"
    [ 8064.882] compiled for 1.9.4.901, module version = 1.0.0
    [ 8064.882] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 8064.882] (II) Loading sub module "dri2"
    [ 8064.882] (II) LoadModule: "dri2"
    [ 8064.882] (II) Reloading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 8064.882] (==) Depth 24 pixmap format is 32 bpp
    [ 8064.883] (II) intel(0): [DRI2] Setup complete
    [ 8064.883] (II) intel(0): [DRI2] DRI driver: i915
    [ 8064.883] (II) intel(0): Allocated new frame buffer 1728x1050 stride 8192, tiled
    [ 8064.883] (II) UXA(0): Driver registered support for the following operations:
    [ 8064.883] (II) solid
    [ 8064.883] (II) copy
    [ 8064.883] (II) composite (RENDER acceleration)
    [ 8064.883] (II) put_image
    [ 8064.883] (II) get_image
    [ 8064.883] (==) intel(0): Backing store disabled
    [ 8064.884] (==) intel(0): Silken mouse enabled
    [ 8064.884] (II) intel(0): Initializing HW Cursor
    [ 8065.019] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 8065.020] (==) intel(0): DPMS enabled
    [ 8065.020] (==) intel(0): Intel XvMC decoder disabled
    [ 8065.020] (II) intel(0): Set up textured video
    [ 8065.020] (II) intel(0): Set up overlay video
    [ 8065.020] (II) intel(0): direct rendering: DRI2 Enabled
    [ 8065.020] (==) intel(0): hotplug detection: "enabled"
    [ 8065.020] (--) RandR disabled
    Last edited by RufusD (2011-03-24 08:36:40)

    OK, it turned out rather easy, I'll write it down here for the record:
    simply add
    video=LVDS-1:d
    to the line
    GRUB_CMDLINE_LINUX_DEFAULT=
    in /etc/default/burg and run the command specified at the top of this file (IIRC, it's "burg-mkconfig -o /boot/burg/burg.cfg"; cf. http://code.google.com/p/burg/wiki/Manu … #Configure)
    This definitely solves issue 1 and 3. Issue 2 *seems* to be solved, issue 4 will need further testing (since it was erratic to begin with)
    Last edited by RufusD (2011-03-24 08:37:37)

  • Screen remains dim after waking up on virtual terminals

    I am having a strange issue when the display gets dim and won't get bright again, but only when I am no a vt.
    I have an older (~4 yrs) Dell Studio 1737 with a Mobility Radeon inside with the xf86-video-ati driver:
    $ lspci | grep -i vga
    01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650]
    $ pacman -Qq | grep xf86-video
    xf86-video-ati
    $ lsmod | grep radeon
    radeon 754282 2
    ttm 65132 1 radeon
    drm_kms_helper 35086 1 radeon
    drm 229990 4 ttm,drm_kms_helper,radeon
    i2c_algo_bit 5391 1 radeon
    i2c_core 22479 6 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,radeon,videodev
    When I leave my computer on one of the virtual consoles (vt2 - vt6) and it is idle for (I think) 10 minutes, it gets dim (via DPMS, I guess?) . However, I can't make it go bright again - after I move the mouse (which I am not sure makes any sense since I have no mouse in the vts) / press any key, nothing happens.
    Now, the strange thing is, when the light is right, I can just see the text, but it is very, very dark and unreadable. Under normal circumstances I can see nothing and the screen can't be told apart form a blank black display. Actually, I had thought it was blank for a while until only recently, when I had the Sun shining against the display.
    I wrote a simple script whose name is 'b':
    echo 10 | tee /sys/class/backlight/acpi_video0/brightness
    and I left the console as root (!) for 10 minutes (!) and when the screen went dim I called 'b' and nothing happened. I have no other ideas about how deal with this one - I tried reading and looking around, and have pretty much nothing. Does this problem ring any bells? Does anybody know how this can be fixed (apart from "just don't leave it on the vt for longer than 10 mins" or similar ;d - these have occurred to me already). Of course, if you need any more information about my hardware, I will provide it.
    I am running a constantly updated arch.
    wujek
    Last edited by wujek.srujek (2013-06-12 21:53:03)

    From the news page here...
    http://xlr8yourmac.com/
    See if it's related to this...
    It also seems to be related to later OSX versions, like 10.8.x & 10.9.x
    The 2012 macs (and later apparently) (also later OSX versions on earlier Macs can do it also), not waking normally from sleep after hours being in sleep. (noted here ...
    http://www.xlr8yourmac.com/archives/feb13/022813.html#2012macswontwake
    "Why 2012 iMac/2012 Mac Mini won't Wake After Hours of Sleep (Hibernates/Powers Off)")
    The sleepimage file still reappears even if never slept. Delete it (hibernate off, etc) - within minutes its back.
    A note on that here - http://www.xlr8yourmac.com/feedback/Chameleon_SSD_Optimizer.html
    About iMac sleep...
    http://forums.macrumors.com/showthread.php?t=1529750
    Try this: "sudo pmset autopoweroff 0" and "sudo pmset standby 0"
    http://xlr8yourmac.com/archives/sep13/091313.html#10.8.5SleepEjectTip
    Two users reported that the opposite worked...
    Try this: "sudo pmset autopoweroff 1" and "sudo pmset standby 1"

  • [SOLVED]After yesterday's upgrade screen problem

    So, yesterday i have upgraded to the newest kernel and udev. Now, the problem is that (i have XFCE) when laptop goes into "switch off screen" mode (in xfce4-power-manager) i cannot recall the screen back to normal (it remains black). I have to suspend it and wake it up in order the screen is visible/normal again (haven't tried to just kill X).
    /var/log/messages:
    Nov 10 14:42:27 localhost -- MARK --
    Nov 10 15:21:01 localhost -- MARK --
    Nov 10 15:41:01 localhost -- MARK --
    Nov 10 16:12:08 localhost saso: ACPI group/action undefined: hotkey / ATK0100:00
    Nov 10 16:12:08 localhost saso: ACPI group/action undefined: video/switchmode / VMOD
    Nov 10 16:12:10 localhost saso: ACPI group/action undefined: hotkey / ATK0100:00
    Nov 10 16:12:10 localhost saso: ACPI group/action undefined: video/switchmode / VMOD
    Nov 10 16:12:16 localhost acpid: client 1616[0:100] has disconnected
    Nov 10 16:12:23 localhost acpid: client connected from 1616[0:100]
    Nov 10 16:12:23 localhost acpid: 1 client rule loaded
    Nov 10 16:12:27 localhost kernel: [44163.481659] EXT4-fs (sda1): re-mounted. Opts: commit=0
    Nov 10 16:12:27 localhost kernel: [44163.489933] EXT4-fs (sda2): re-mounted. Opts: commit=0
    Nov 10 16:12:27 localhost kernel: [44163.499653] EXT4-fs (sda3): re-mounted. Opts: commit=0
    Nov 10 16:12:28 localhost dhcpcd[5940]: sending signal 1 to pid 5326
    Nov 10 16:12:28 localhost dhcpcd[5940]: waiting for pid 5326 to exit
    Nov 10 16:12:28 localhost dhcpcd[5326]: received SIGHUP, releasing
    Nov 10 16:12:28 localhost dhcpcd[5326]: wlan0: releasing lease of 192.168.1.3
    Nov 10 16:12:28 localhost dhcpcd[5326]: wlan0: removing interface
    Nov 10 16:12:28 localhost kernel: [44164.828910] cfg80211: Calling CRDA to update world regulatory domain
    Nov 10 16:12:28 localhost kernel: [44164.913810] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Nov 10 16:12:28 localhost kernel: [44164.994702] ADDRCONF(NETDEV_UP): eth0: link is not ready
    Nov 10 16:12:28 localhost kernel: [44165.101603] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Nov 10 16:12:28 localhost kernel: [44165.162838] ADDRCONF(NETDEV_UP): eth0: link is not ready
    Nov 10 16:12:41 localhost kernel: [44165.504492] PM: Syncing filesystems ... done.
    Nov 10 16:12:41 localhost kernel: [44165.510675] Freezing user space processes ... (elapsed 0.01 seconds) done.
    Nov 10 16:12:41 localhost kernel: [44165.522325] Freezing remaining freezable tasks ... (elapsed 1.09 seconds) done.
    Nov 10 16:12:41 localhost kernel: [44166.615763] Suspending console(s) (use no_console_suspend to debug)
    Nov 10 16:12:41 localhost kernel: [44166.616477] sd 0:0:0:0: [sda] Synchronizing SCSI cache
    Nov 10 16:12:41 localhost kernel: [44166.629860] sd 0:0:0:0: [sda] Stopping disk
    Nov 10 16:12:41 localhost kernel: [44166.642540] ATL1E 0000:03:00.0: PCI INT A disabled
    Nov 10 16:12:41 localhost kernel: [44166.732640] snd_hda_intel 0000:00:1b.0: PCI INT A disabled
    Nov 10 16:12:41 localhost kernel: [44167.018971] PM: suspend of devices complete after 402.827 msecs
    Nov 10 16:12:41 localhost kernel: [44167.059129] PM: late suspend of devices complete after 40.150 msecs
    Nov 10 16:12:41 localhost kernel: [44167.059309] ACPI: Preparing to enter system sleep state S3
    Nov 10 16:12:41 localhost kernel: [44167.257307] PM: Saving platform NVS memory
    Nov 10 16:12:41 localhost kernel: [44167.257797] Disabling non-boot CPUs ...
    Nov 10 16:12:41 localhost kernel: [44167.259218] CPU 1 is now offline
    Nov 10 16:12:41 localhost kernel: [44167.259707] Extended CMOS year: 2000
    Nov 10 16:12:41 localhost kernel: [44167.259707] ACPI: Low-level resume complete
    Nov 10 16:12:41 localhost kernel: [44167.259707] PM: Restoring platform NVS memory
    Nov 10 16:12:41 localhost kernel: [44167.259707] Extended CMOS year: 2000
    Nov 10 16:12:41 localhost kernel: [44167.259707] Enabling non-boot CPUs ...
    Nov 10 16:12:41 localhost kernel: [44167.266546] Booting Node 0 Processor 1 APIC 0x1
    Nov 10 16:12:41 localhost kernel: [44167.259183] Initializing CPU#1
    Nov 10 16:12:41 localhost kernel: [44167.259183] Calibrating delay loop (skipped) already calibrated this CPU
    Nov 10 16:12:41 localhost kernel: [44167.277996] NMI watchdog enabled, takes one hw-pmu counter.
    Nov 10 16:12:41 localhost kernel: [44167.278933] Switched to NOHz mode on CPU #1
    Nov 10 16:12:41 localhost kernel: [44167.282318] CPU1 is up
    Nov 10 16:12:42 localhost kernel: [44167.283293] ACPI: Waking up from system sleep state S3
    Nov 10 16:12:42 localhost kernel: [44168.297514] PM: early resume of devices complete after 1.403 msecs
    Nov 10 16:12:42 localhost kernel: [44168.297649] usb usb3: root hub lost power or was reset
    Nov 10 16:12:42 localhost kernel: [44168.297719] usb usb4: root hub lost power or was reset
    Nov 10 16:12:42 localhost kernel: [44168.297793] usb usb5: root hub lost power or was reset
    Nov 10 16:12:42 localhost kernel: [44168.299179] snd_hda_intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
    Nov 10 16:12:42 localhost kernel: [44168.299334] usb usb6: root hub lost power or was reset
    Nov 10 16:12:42 localhost kernel: [44168.299374] usb usb7: root hub lost power or was reset
    Nov 10 16:12:42 localhost kernel: [44168.299413] usb usb8: root hub lost power or was reset
    Nov 10 16:12:42 localhost kernel: [44168.305605] ATL1E 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    Nov 10 16:12:42 localhost kernel: [44168.355074] Extended CMOS year: 2000
    Nov 10 16:12:42 localhost kernel: [44168.362432] sd 0:0:0:0: [sda] Starting disk
    Nov 10 16:12:42 localhost kernel: [44168.632301] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Nov 10 16:12:42 localhost kernel: [44168.655037] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
    Nov 10 16:12:42 localhost kernel: [44168.685480] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
    Nov 10 16:12:42 localhost kernel: [44168.698272] ata2.00: configured for UDMA/100
    Nov 10 16:12:42 localhost kernel: [44168.815660] usb 6-2: reset low speed USB device number 3 using uhci_hcd
    Nov 10 16:12:42 localhost kernel: [44170.172346] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Nov 10 16:12:42 localhost kernel: [44170.174103] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
    Nov 10 16:12:42 localhost kernel: [44170.174434] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
    Nov 10 16:12:42 localhost kernel: [44170.178450] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
    Nov 10 16:12:42 localhost kernel: [44170.178782] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
    Nov 10 16:12:42 localhost kernel: [44170.180642] ata1.00: configured for UDMA/133
    Nov 10 16:12:42 localhost kernel: [44170.224518] PM: resume of devices complete after 1926.927 msecs
    Nov 10 16:12:42 localhost kernel: [44170.224850] Restarting tasks ... done.
    Nov 10 16:12:42 localhost kernel: [44170.238561] video LNXVIDEO:00: Restoring backlight state
    Nov 10 16:12:45 localhost kernel: [44173.423488] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Nov 10 16:12:45 localhost laptop-mode: Laptop mode
    Nov 10 16:12:45 localhost laptop-mode: enabled, not active
    Nov 10 16:12:46 localhost kernel: [44174.630668] CE: hpet increased min_delta_ns to 30169 nsec
    Nov 10 16:12:46 localhost kernel: [44174.885331] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Nov 10 16:12:46 localhost kernel: [44174.928328] ADDRCONF(NETDEV_UP): eth0: link is not ready
    Nov 10 16:12:46 localhost kernel: [44175.030767] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Nov 10 16:12:47 localhost kernel: [44175.496506] EXT4-fs (sda1): re-mounted. Opts: commit=0
    Nov 10 16:12:47 localhost kernel: [44175.704900] EXT4-fs (sda2): re-mounted. Opts: commit=0
    Nov 10 16:12:47 localhost kernel: [44175.708047] EXT4-fs (sda3): re-mounted. Opts: commit=0
    Nov 10 16:12:47 localhost acpid: client 1616[0:100] has disconnected
    Nov 10 16:12:47 localhost saso: ACPI group/action undefined: processor / LNXCPU:00
    Nov 10 16:12:47 localhost acpid: client connected from 1616[0:100]
    Nov 10 16:12:47 localhost acpid: 1 client rule loaded
    Nov 10 16:12:47 localhost saso: ACPI group/action undefined: processor / LNXCPU:01
    Nov 10 16:12:47 localhost laptop-mode: Laptop mode
    Nov 10 16:12:47 localhost laptop-mode: enabled,
    Nov 10 16:12:47 localhost laptop-mode: not active [unchanged]
    Nov 10 16:12:47 localhost saso: ACPI action undefined: PNP0C0A:00
    Nov 10 16:12:47 localhost laptop-mode: Laptop mode
    Nov 10 16:12:47 localhost laptop-mode: enabled,
    Nov 10 16:12:47 localhost laptop-mode: not active [unchanged]
    Nov 10 16:12:49 localhost kernel: [44177.453758] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    Nov 10 16:12:49 localhost dhcpcd[6755]: version 5.2.12 starting
    Nov 10 16:12:50 localhost dhcpcd[6755]: wlan0: broadcasting for a lease
    Nov 10 16:12:50 localhost dhcpcd[6755]: wlan0: offered 192.168.1.3 from 192.168.1.1
    Nov 10 16:12:50 localhost dhcpcd[6755]: wlan0: acknowledged 192.168.1.3 from 192.168.1.1
    Nov 10 16:12:50 localhost dhcpcd[6755]: wlan0: checking for 192.168.1.3
    Nov 10 16:12:55 localhost dhcpcd[6755]: wlan0: leased 192.168.1.3 for 86400 seconds
    Nov 10 16:12:55 localhost dhcpcd[6755]: forked to background, child pid 6778
    /var/log/kernel.log:
    Nov 10 13:29:37 localhost kernel: [34393.536524] oosplash.bin[28937]: segfault at 4d0 ip b779fa1b sp bf9ffbe0 error 4 in libX11.so.6.3.0[b776c000+132000]
    Nov 10 16:12:27 localhost kernel: [44163.481659] EXT4-fs (sda1): re-mounted. Opts: commit=0
    Nov 10 16:12:27 localhost kernel: [44163.489933] EXT4-fs (sda2): re-mounted. Opts: commit=0
    Nov 10 16:12:27 localhost kernel: [44163.499653] EXT4-fs (sda3): re-mounted. Opts: commit=0
    Nov 10 16:12:28 localhost kernel: [44164.769066] wlan0: deauthenticating from 00:1d:60:19:9c:51 by local choice (reason=3)
    Nov 10 16:12:28 localhost kernel: [44164.828910] cfg80211: Calling CRDA to update world regulatory domain
    Nov 10 16:12:28 localhost kernel: [44164.913810] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Nov 10 16:12:28 localhost kernel: [44164.994333] ATL1E 0000:03:00.0: irq 46 for MSI/MSI-X
    Nov 10 16:12:28 localhost kernel: [44164.994702] ADDRCONF(NETDEV_UP): eth0: link is not ready
    Nov 10 16:12:28 localhost kernel: [44165.101603] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Nov 10 16:12:28 localhost kernel: [44165.162190] ATL1E 0000:03:00.0: irq 46 for MSI/MSI-X
    Nov 10 16:12:28 localhost kernel: [44165.162838] ADDRCONF(NETDEV_UP): eth0: link is not ready
    Nov 10 16:12:41 localhost kernel: [44165.504492] PM: Syncing filesystems ... done.
    Nov 10 16:12:41 localhost kernel: [44165.510538] PM: Preparing system for mem sleep
    Nov 10 16:12:41 localhost kernel: [44165.510675] Freezing user space processes ... (elapsed 0.01 seconds) done.
    Nov 10 16:12:41 localhost kernel: [44165.522325] Freezing remaining freezable tasks ... (elapsed 1.09 seconds) done.
    Nov 10 16:12:41 localhost kernel: [44166.615714] PM: Entering mem sleep
    Nov 10 16:12:41 localhost kernel: [44166.615763] Suspending console(s) (use no_console_suspend to debug)
    Nov 10 16:12:41 localhost kernel: [44166.616477] sd 0:0:0:0: [sda] Synchronizing SCSI cache
    Nov 10 16:12:41 localhost kernel: [44166.629860] sd 0:0:0:0: [sda] Stopping disk
    Nov 10 16:12:41 localhost kernel: [44166.642540] ATL1E 0000:03:00.0: PCI INT A disabled
    Nov 10 16:12:41 localhost kernel: [44166.732640] snd_hda_intel 0000:00:1b.0: PCI INT A disabled
    Nov 10 16:12:41 localhost kernel: [44167.018971] PM: suspend of devices complete after 402.827 msecs
    Nov 10 16:12:41 localhost kernel: [44167.059129] PM: late suspend of devices complete after 40.150 msecs
    Nov 10 16:12:41 localhost kernel: [44167.059309] ACPI: Preparing to enter system sleep state S3
    Nov 10 16:12:41 localhost kernel: [44167.257307] PM: Saving platform NVS memory
    Nov 10 16:12:41 localhost kernel: [44167.257797] Disabling non-boot CPUs ...
    Nov 10 16:12:41 localhost kernel: [44167.259218] CPU 1 is now offline
    Nov 10 16:12:41 localhost kernel: [44167.259707] Extended CMOS year: 2000
    Nov 10 16:12:41 localhost kernel: [44167.259707] ACPI: Low-level resume complete
    Nov 10 16:12:41 localhost kernel: [44167.259707] PM: Restoring platform NVS memory
    Nov 10 16:12:41 localhost kernel: [44167.259707] CPU0: Thermal monitoring handled by SMI
    Nov 10 16:12:41 localhost kernel: [44167.259707] Extended CMOS year: 2000
    Nov 10 16:12:41 localhost kernel: [44167.259707] Enabling non-boot CPUs ...
    Nov 10 16:12:41 localhost kernel: [44167.266546] Booting Node 0 Processor 1 APIC 0x1
    Nov 10 16:12:41 localhost kernel: [44167.266548] smpboot cpu 1: start_ip = 93000
    Nov 10 16:12:41 localhost kernel: [44167.259183] Initializing CPU#1
    Nov 10 16:12:41 localhost kernel: [44167.259183] Calibrating delay loop (skipped) already calibrated this CPU
    Nov 10 16:12:41 localhost kernel: [44167.259183] CPU1: Thermal monitoring handled by SMI
    Nov 10 16:12:41 localhost kernel: [44167.277996] NMI watchdog enabled, takes one hw-pmu counter.
    Nov 10 16:12:41 localhost kernel: [44167.278933] Switched to NOHz mode on CPU #1
    Nov 10 16:12:41 localhost kernel: [44167.282318] CPU1 is up
    Nov 10 16:12:42 localhost kernel: [44167.283293] ACPI: Waking up from system sleep state S3
    Nov 10 16:12:42 localhost kernel: [44168.296199] i915 0000:00:02.0: restoring config space at offset 0x8 (was 0x1, writing 0xdc01)
    Nov 10 16:12:42 localhost kernel: [44168.296208] i915 0000:00:02.0: restoring config space at offset 0x1 (was 0x900007, writing 0x900407)
    Nov 10 16:12:42 localhost kernel: [44168.296456] snd_hda_intel 0000:00:1b.0: restoring config space at offset 0x3 (was 0x0, writing 0x8)
    Nov 10 16:12:42 localhost kernel: [44168.296464] snd_hda_intel 0000:00:1b.0: restoring config space at offset 0x1 (was 0x100006, writing 0x100002)
    Nov 10 16:12:42 localhost kernel: [44168.296500] pcieport 0000:00:1c.0: restoring config space at offset 0xf (was 0x20100, writing 0x2010a)
    Nov 10 16:12:42 localhost kernel: [44168.296517] pcieport 0000:00:1c.0: restoring config space at offset 0x7 (was 0xf0, writing 0x200000f0)
    Nov 10 16:12:42 localhost kernel: [44168.296528] pcieport 0000:00:1c.0: restoring config space at offset 0x3 (was 0x810000, writing 0x810008)
    Nov 10 16:12:42 localhost kernel: [44168.296536] pcieport 0000:00:1c.0: restoring config space at offset 0x1 (was 0x100104, writing 0x100504)
    Nov 10 16:12:42 localhost kernel: [44168.296592] pcieport 0000:00:1c.1: restoring config space at offset 0xf (was 0x20200, writing 0x20205)
    Nov 10 16:12:42 localhost kernel: [44168.296609] pcieport 0000:00:1c.1: restoring config space at offset 0x7 (was 0xf0, writing 0x200000f0)
    Nov 10 16:12:42 localhost kernel: [44168.296620] pcieport 0000:00:1c.1: restoring config space at offset 0x3 (was 0x810000, writing 0x810008)
    Nov 10 16:12:42 localhost kernel: [44168.296628] pcieport 0000:00:1c.1: restoring config space at offset 0x1 (was 0x100106, writing 0x100506)
    Nov 10 16:12:42 localhost kernel: [44168.296684] pcieport 0000:00:1c.5: restoring config space at offset 0xf (was 0x20200, writing 0x20205)
    Nov 10 16:12:42 localhost kernel: [44168.296698] pcieport 0000:00:1c.5: restoring config space at offset 0x9 (was 0x1fff1, writing 0x7df17de1)
    Nov 10 16:12:42 localhost kernel: [44168.296712] pcieport 0000:00:1c.5: restoring config space at offset 0x3 (was 0x810000, writing 0x810008)
    Nov 10 16:12:42 localhost kernel: [44168.296720] pcieport 0000:00:1c.5: restoring config space at offset 0x1 (was 0x100107, writing 0x100507)
    Nov 10 16:12:42 localhost kernel: [44168.297063] ahci 0000:00:1f.2: restoring config space at offset 0x1 (was 0x2b00007, writing 0x2b00407)
    Nov 10 16:12:42 localhost kernel: [44168.297137] ath9k 0000:02:00.0: restoring config space at offset 0xf (was 0x1ff, writing 0x105)
    Nov 10 16:12:42 localhost kernel: [44168.297165] ath9k 0000:02:00.0: restoring config space at offset 0x4 (was 0x4, writing 0xfeaf0004)
    Nov 10 16:12:42 localhost kernel: [44168.297172] ath9k 0000:02:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x8)
    Nov 10 16:12:42 localhost kernel: [44168.297182] ath9k 0000:02:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100007)
    Nov 10 16:12:42 localhost kernel: [44168.297234] ATL1E 0000:03:00.0: restoring config space at offset 0xf (was 0x100, writing 0x105)
    Nov 10 16:12:42 localhost kernel: [44168.297265] ATL1E 0000:03:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x8)
    Nov 10 16:12:42 localhost kernel: [44168.297274] ATL1E 0000:03:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100407)
    Nov 10 16:12:42 localhost kernel: [44168.297514] PM: early resume of devices complete after 1.403 msecs
    Nov 10 16:12:42 localhost kernel: [44168.297614] i915 0000:00:02.0: setting latency timer to 64
    Nov 10 16:12:42 localhost kernel: [44168.297619] uhci_hcd 0000:00:1a.0: setting latency timer to 64
    Nov 10 16:12:42 localhost kernel: [44168.297649] usb usb3: root hub lost power or was reset
    Nov 10 16:12:42 localhost kernel: [44168.297692] uhci_hcd 0000:00:1a.1: setting latency timer to 64
    Nov 10 16:12:42 localhost kernel: [44168.297719] usb usb4: root hub lost power or was reset
    Nov 10 16:12:42 localhost kernel: [44168.297766] uhci_hcd 0000:00:1a.2: setting latency timer to 64
    Nov 10 16:12:42 localhost kernel: [44168.297793] usb usb5: root hub lost power or was reset
    Nov 10 16:12:42 localhost kernel: [44168.297807] ehci_hcd 0000:00:1a.7: setting latency timer to 64
    Nov 10 16:12:42 localhost kernel: [44168.299179] snd_hda_intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
    Nov 10 16:12:42 localhost kernel: [44168.299187] snd_hda_intel 0000:00:1b.0: setting latency timer to 64
    Nov 10 16:12:42 localhost kernel: [44168.299238] snd_hda_intel 0000:00:1b.0: irq 44 for MSI/MSI-X
    Nov 10 16:12:42 localhost kernel: [44168.299307] uhci_hcd 0000:00:1d.0: setting latency timer to 64
    Nov 10 16:12:42 localhost kernel: [44168.299334] usb usb6: root hub lost power or was reset
    Nov 10 16:12:42 localhost kernel: [44168.299347] uhci_hcd 0000:00:1d.1: setting latency timer to 64
    Nov 10 16:12:42 localhost kernel: [44168.299374] usb usb7: root hub lost power or was reset
    Nov 10 16:12:42 localhost kernel: [44168.299387] uhci_hcd 0000:00:1d.2: setting latency timer to 64
    Nov 10 16:12:42 localhost kernel: [44168.299413] usb usb8: root hub lost power or was reset
    Nov 10 16:12:42 localhost kernel: [44168.299428] ehci_hcd 0000:00:1d.7: setting latency timer to 64
    Nov 10 16:12:42 localhost kernel: [44168.299473] pci 0000:00:1e.0: setting latency timer to 64
    Nov 10 16:12:42 localhost kernel: [44168.299489] ahci 0000:00:1f.2: setting latency timer to 64
    Nov 10 16:12:42 localhost kernel: [44168.305605] ATL1E 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    Nov 10 16:12:42 localhost kernel: [44168.305613] ATL1E 0000:03:00.0: setting latency timer to 64
    Nov 10 16:12:42 localhost kernel: [44168.305680] ATL1E 0000:03:00.0: irq 46 for MSI/MSI-X
    Nov 10 16:12:42 localhost kernel: [44168.355074] Extended CMOS year: 2000
    Nov 10 16:12:42 localhost kernel: [44168.362432] sd 0:0:0:0: [sda] Starting disk
    Nov 10 16:12:42 localhost kernel: [44168.632301] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    Nov 10 16:12:42 localhost kernel: [44168.655032] ata2.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
    Nov 10 16:12:42 localhost kernel: [44168.655037] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
    Nov 10 16:12:42 localhost kernel: [44168.685475] ata2.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
    Nov 10 16:12:42 localhost kernel: [44168.685480] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
    Nov 10 16:12:42 localhost kernel: [44168.698272] ata2.00: configured for UDMA/100
    Nov 10 16:12:42 localhost kernel: [44168.815660] usb 6-2: reset low speed USB device number 3 using uhci_hcd
    Nov 10 16:12:42 localhost kernel: [44170.172346] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    Nov 10 16:12:42 localhost kernel: [44170.174103] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
    Nov 10 16:12:42 localhost kernel: [44170.174430] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
    Nov 10 16:12:42 localhost kernel: [44170.174434] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
    Nov 10 16:12:42 localhost kernel: [44170.178450] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
    Nov 10 16:12:42 localhost kernel: [44170.178777] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
    Nov 10 16:12:42 localhost kernel: [44170.178782] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
    Nov 10 16:12:42 localhost kernel: [44170.180642] ata1.00: configured for UDMA/133
    Nov 10 16:12:42 localhost kernel: [44170.224518] PM: resume of devices complete after 1926.927 msecs
    Nov 10 16:12:42 localhost kernel: [44170.224848] PM: Finishing wakeup.
    Nov 10 16:12:42 localhost kernel: [44170.224850] Restarting tasks ... done.
    Nov 10 16:12:42 localhost kernel: [44170.238561] video LNXVIDEO:00: Restoring backlight state
    Nov 10 16:12:45 localhost kernel: [44173.423488] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Nov 10 16:12:46 localhost kernel: [44174.630668] CE: hpet increased min_delta_ns to 30169 nsec
    Nov 10 16:12:46 localhost kernel: [44174.885331] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Nov 10 16:12:46 localhost kernel: [44174.927923] ATL1E 0000:03:00.0: irq 46 for MSI/MSI-X
    Nov 10 16:12:46 localhost kernel: [44174.928328] ADDRCONF(NETDEV_UP): eth0: link is not ready
    Nov 10 16:12:46 localhost kernel: [44175.030767] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Nov 10 16:12:47 localhost kernel: [44175.496506] EXT4-fs (sda1): re-mounted. Opts: commit=0
    Nov 10 16:12:47 localhost kernel: [44175.704900] EXT4-fs (sda2): re-mounted. Opts: commit=0
    Nov 10 16:12:47 localhost kernel: [44175.708047] EXT4-fs (sda3): re-mounted. Opts: commit=0
    Nov 10 16:12:49 localhost kernel: [44177.448823] wlan0: authenticate with 00:1d:60:19:9c:51 (try 1)
    Nov 10 16:12:49 localhost kernel: [44177.450829] wlan0: authenticated
    Nov 10 16:12:49 localhost kernel: [44177.450861] wlan0: associate with 00:1d:60:19:9c:51 (try 1)
    Nov 10 16:12:49 localhost kernel: [44177.453381] wlan0: RX AssocResp from 00:1d:60:19:9c:51 (capab=0x411 status=0 aid=2)
    Nov 10 16:12:49 localhost kernel: [44177.453385] wlan0: associated
    Nov 10 16:12:49 localhost kernel: [44177.453758] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    Nov 10 16:12:59 localhost kernel: [44188.252291] wlan0: no IPv6 routers present
    Upgraded packages:
    [2011-11-09 12:04] upgraded linux (3.0.7-1 -> 3.1-4)
    [2011-11-09 12:04] upgraded linux-headers (3.0.7-1 -> 3.1-4)
    [2011-11-09 12:04] upgraded lirc-utils (1:0.9.0-6 -> 1:0.9.0-8)
    [2011-11-09 12:04] upgraded mpfr (3.1.0.p1-1 -> 3.1.0.p3-1)
    [2011-11-09 12:04] upgraded net-tools (1.60.20110819cvs-1 -> 1.60.20110819cvs-3)
    [2011-11-09 12:04] upgraded pixman (0.22.2-1 -> 0.24.0-1)
    [2011-11-09 12:04] upgraded udev (174-1 -> 175-1)
    [2011-11-09 12:04] upgraded wine (1.3.32-1 -> 1.3.32-2)
    /var/log/Xorg.0.log:
    http://dl.dropbox.com/u/38176672/Xorg.0.log
    /var/log/dmesg.log:
    http://dl.dropbox.com/u/38176672/dmesg.log
    Last edited by Shark (2011-12-01 12:49:45)

    hi,
    I have the same problem(intel Corporation Mobile 915GM). And I found the following can solve the half of the problem
    Section "Device"
        Identifier    "Device0"
        Driver        "vesa" # <---replacing intel by vesa
    EndSection
    But after "kill X", the screen of the framebuffer becomes quite horrible as showed in the pic.

  • [SOLVED] Gnome 3 == The Green Screen of Death

    Greetings,
    Trying to load GNOME 3 seems to result constantly in nothing but a bright green screen and mouse, despite anything else I've tried. Nothing else loads. I have to change tty to do anything else. Doing so, I executed htop and saw that only 2% of my CPU was being used, and the only thing from GNOME3 that was running was GDM.
    These are the steps I have taken before posting in here....
    1.) I followed the steps in the wiki for upgrading to GNOME3. Testing repo is the first repo.
    ----- That brought me into fallback mode but was missing many things. Upon investigation I saw that I had never fully installed GNOME 2 to begin with, that I only had XFCE and GNOME stuff that were brought in as dependecies to some other programs I had installed. So.....
    2.) pacman -Rcns gnome followed by following the Wiki for installing from scratch.
    ----- Got the correct GDM (takes a while to load it), but only get the green screen with mouse cursor.
    3.) Thinks and searches, "Hey I need pulseaudio... maybe that is why it isn't working." So I follow the wiki on installing pulseaudio.
    ----- Still, green screen
    4.) Maybe, just maybe, it doesn't like the nouvela driver? So I change to nvidia.
    ----- Still, green screen
    5.) Try another pacman -Syu.
    ----- Nothing new related to gnome 3 updates. Still green screen.
    6.) Search frantically on google for anything related to GNOME 3 not loading or showing a green screen. Searched here as well.
    ----- Found nothing. Still has a freaking green screen upon reboot of system (thankfully I have laptop here to use while trying to figure this out but damn, I am getting aggravated by this frustrating issue).
    EDIT: Just in case it is relevant, I am using the inittab method of loading GDM.
    EDIT 2: Forgot to add, I also removed all old instances of gconf and gconfd and such in an attempt to solve the green screen.
    Defeated, I come here. Does anyone have any advise, suggestions, etc or does this spell the end of GNOME 3 on my computer?
    Last edited by mythus (2011-04-08 15:00:17)

    Greetings,
    I have solved this issue. The conflict was with firefox4-beta-opensuse. I replaced it with firefox from the official repositories, and *poof*, I am now in Gnome3 with Gnome shell.
    LOL, yeah I tried those things which is what led me to the answer. Actually, it was the lack of libmozjs.so anywhere on my system combined with a google search indicating that it was supposed to be in xulrunner, yet it wasn't. That is what led me to re-uploading firefox completely so that I could do away with the beta xulrunner.
    Did you still need that pacman -Qm list? I am going to assume no since it is solved, but who knows, you may have seen something else in my pastebin report as well. Anyways thanks!

  • [SOLVED] Login Prompt Vs Blank Screen On Startup

    Hello there,
    Problem:
      - When booting into Arch I am either presented with the Login Prompt (Yay!) or a blank back lit screen (Boo!). The pattern is completely random. I can boot up 2-3 times in a row successfully then go on a streak of blank back lit screens and am forced to constantly reboot until I get it to work (see below):
    Boot Attempt => Result after selecting Arch from Grub
    1) Blank screen
    2) Blank
    3) Blank
    4) Login prompt
    5) Login
    6) Login
    7) Login
    8) Blank
    9) Blank
    10) Login
    11) Login
    12) Blank
    13) Login
    14) Blank
    Its a fresh install up until this point in the procedure, Arch Wiki Beginners Guide, so no graphical elements have been installed yet only thing I have installed is firmware for the wireless Broadcom (which is working fine).
    Display: Intel Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
    Network: Broadcom BCM4311 802.11b/g WLAN (rev 01)
    CPU: Core Duo ~2Ghz x86
    RAM: 1.5GB
    Memory Test: Success
    sda
    |------sda1 (Windows XP)
    |------sda2 (NTFS partition [No OS])
    |------sda3 (Arch i686)
    |------sda4 (Swap)
    Search regarding blank screen turned up this thread, https://bbs.archlinux.org/viewtopic.php?id=151240 , which seemed relevant. It led to KMS though not sure exactly what that does even after reading the Wiki so I decided to post here rather than tinker with it and risk making things 100x worse than they already are.
    Any idea as to what could be causing my irregular boot behavior?
    Last edited by notyourbuddy (2013-01-01 04:07:28)

    cfr wrote:Although that thread seems similar, I'm not sure how this could be the same issue as I thought KMS required a suitable video driver. Still, you could try passing nomodeset on the kernel command line as described in that thread. The worst that will happen is that it won't work. (You can edit the line from the grub menu so if it doesn't work you can just reboot and be back to the same settings you had before.) I guess you'd have to boot a few times to know if it helped.
    Hmm, that seems to have fixed my problem. 9 successful reboots in a row. Figured with my erratic boot behavior as opposed to 100% blank screening that my problem was far worse when in fact the solution seems to have turned out to be quite simple.  Oopsie. My bad guys.
    Followed these steps to make the changes persistent, https://wiki.archlinux.org/index.php/Kernel_parameters , and seems to be holding up well. Will go ahead and marked as Solved and hope no more monitor boot problems arise.
    cfr wrote:So just to clarify: you have not installed any video drivers at this point, correct? And you haven't installed X? You definitely only have one graphics card?
    Nope. Nope. Yep.
    cfr wrote:You can try examining the log files to see what is happening on successful versus unsuccessful boots. journalctl will let you do this and you can filter it with various options.
    Cool, first time I've heard of this and just tested that out. Looks to be a wealth of information. Will have to remember this next time I have boot woes.
    Last edited by notyourbuddy (2013-01-01 04:12:26)

  • [Solved] Amilo XI 2550 - Black screen after fresh install

    Dear archlinux users,
    I have been reading the archlinux wiki and forums since I started using arch several years ago. It was always possible to solve the problems I ran into by consulting these webpages, therefore a big thanks to the community for the provided help.
    Two weeks ago I installed arch on a Fujitsu Siemens Amilo XI 2550. The first problem I ran into was that booting the live-cd resulted in a black screen and I could not even start with installing arch. This problem was solved with the kernel parameter 'nomodeset'.
    The first boot of the freshly installed arch also resulted in a black screen after the GRUB menu which was perfectly displayed. After some searching (here and here and ...) I plugged in an external monitor and it showed the login screen. I then installed KDE because I thaught the problem might not show up with X and KDE running. After the login to KDE I realized that the brightness of the laptop display is nearly black but not totally. It seems as if the brightness is at a very low level, but brightness cannot be controlled with the Fn+F8 or Fn+F9 commands. But I see a OSD that indicates that the controls are used but without effect. So at the moment it is only possible to work on the laptop with another display connected to it.
    Maybe of use:
    ls /sys/class/backlight/
    acpi_video0
    radeon_bl0
    less /sys/class/backlight/acpi_video0/bl_power
    0
    less /sys/class/backlight/acpi_video0/actual_brightness
    7
    less /sys/class/backlight/acpi_video0/brightness
    7
    less /sys/class/backlight/acpi_video0/max_brightness
    7
    less /sys/class/backlight/radeon_bl0/bl_power
    0
    less /sys/class/backlight/radeon_bl0/actual_brightness
    255
    less /sys/class/backlight/radeon_bl0/brightness
    255
    less /sys/class/backlight/radeon_bl0/max_brightness
    255
    dmesg | grep drm
    [ 0.736559] [drm] Initialized drm 1.1.0 20060810
    [ 0.743608] [drm] radeon kernel modesetting enabled.
    [ 0.743678] fb: switching to radeondrmfb from VESA VGA
    [ 0.744054] [drm] initializing kernel modesetting (RV630 0x1002:0x9583 0x1734:0x1107).
    [ 0.744065] [drm] register mmio base: 0xCFEF0000
    [ 0.744067] [drm] register mmio size: 65536
    [ 0.744172] [drm] Detected VRAM RAM=256M, BAR=256M
    [ 0.744174] [drm] RAM width 128bits DDR
    [ 0.744257] [drm] radeon: 256M of VRAM memory ready
    [ 0.744259] [drm] radeon: 512M of GTT memory ready.
    [ 0.744275] [drm] Loading RV630 Microcode
    [ 0.744345] [drm] Internal thermal controller without fan control
    [ 0.744386] [drm] radeon: power management initialized
    [ 0.744389] [drm] GART: num cpu pages 131072, num gpu pages 131072
    [ 0.762830] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
    [ 0.762873] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
    [ 0.762874] [drm] Driver supports precise vblank timestamp query.
    [ 0.762937] [drm] radeon: irq initialized.
    [ 0.794780] [drm] ring test on 0 succeeded in 1 usecs
    [ 0.795253] [drm] ib test on ring 0 succeeded in 0 usecs
    [ 0.795942] [drm] radeon atom DIG backlight initialized
    [ 0.795945] [drm] Radeon Display Connectors
    [ 0.795947] [drm] Connector 0:
    [ 0.795948] [drm] LVDS-1
    [ 0.795950] [drm] DDC: 0xac0 0xac0 0xac4 0xac4 0xac8 0xac8 0xacc 0xacc
    [ 0.795951] [drm] Encoders:
    [ 0.795952] [drm] LCD1: INTERNAL_LVTM1
    [ 0.795953] [drm] Connector 1:
    [ 0.795954] [drm] DIN-1
    [ 0.795955] [drm] Encoders:
    [ 0.795956] [drm] TV1: INTERNAL_KLDSCP_DAC2
    [ 0.795957] [drm] Connector 2:
    [ 0.795958] [drm] HDMI-A-1
    [ 0.795960] [drm] HPD1
    [ 0.795961] [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
    [ 0.795963] [drm] Encoders:
    [ 0.795964] [drm] DFP1: INTERNAL_KLDSCP_TMDS1
    [ 0.795965] [drm] Connector 3:
    [ 0.795966] [drm] VGA-1
    [ 0.795968] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
    [ 0.795969] [drm] Encoders:
    [ 0.795970] [drm] CRT1: INTERNAL_KLDSCP_DAC1
    [ 1.278449] [drm] fb mappable at 0xD0141000
    [ 1.278451] [drm] vram apper at 0xD0000000
    [ 1.278453] [drm] size 9216000
    [ 1.278454] [drm] fb depth is 24
    [ 1.278455] [drm] pitch is 7680
    [ 1.278527] fbcon: radeondrmfb (fb0) is primary device
    [ 1.726069] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
    [ 1.770030] [drm] Initialized radeon 2.39.0 20080528 for 0000:01:00.0 on minor 0
    Until now and amongst others I tried the following things.
    Using kernel parameters
    video.use_native_backlight=1
    video.use_native_backlight=0
    acpi_osi=linux
    acpi_backlight=vendor
    and others I just cannot remember.
    Masking backlight
    systemctl mask systemd-backlight@backlight:acpi_video0.service
    systemctl mask systemd-backlight@backlight:radeon_bl0.service
    Setting bl_power
    echo 1 > /sys/class/backlight/acpi_video0/bl_power
    echo 1 > /sys/class/backlight/radeon_bl0/bl_power
    Nothing of the above was improving the situation.
    Your help on the problem would be highly appreciated.
    Best regards
    mgs
    Last edited by mgs (2014-10-27 10:15:11)

    Hello Trilby,
    thanks for the reply.
    Trilby wrote:If nomodeset worked with the installation medium, why haven't you tried that for the same problem on your installed system?
    The kernel parameter 'nomodeset' results in a working display but without X support, due to the fact that with 'nomodeset' there is no KMS support and therefore no X. But nevertheless I tried it and as expected X did not start.
    Trilby wrote:Could you also post information about your graphics card and what drivers you've installed.
    The graphics card is a Radeon HD 2700 and according to the above dmesg log it is recognized as RV 630. The radeon module is loaded via /etc/mkinitcpio.conf and xf86-video-ati (1:7.5.0-1) is installed.
    I hope the provided information is what you asked for, thanks for your help.
    Best regards
    mgs

  • Virtual Console on Separate Screen

    As in the title, I would like to know how (if at all possible) to run a virtual console on my second screen, and still have X, Openbox, all my graphical stuff on my main screen.

    I had considered this, but if I set it to TwinView, it stretches by desktop background, and my SLiM logon background.
    In the nVidia config utility, I saw an option for a separate X screen, would I be able to set this up to have a terminal full screen on my second screen?

  • Cannot see virtual terminals

    I boot into X and then attempt to switch to a virtual terminal (ctrl+alt+f{1,2,3...}). I just get a black screen (the screen is on) but cannot see anything. The terminal is there because I can type 'root' and the password to log in and type 'restart' to restart the machine. Any idea how to fix this?
    I am running nouveau but the same issue was happening with the proprietary nvidia driver.

    Fixed by installing xf86-video-intel.

Maybe you are looking for