Keresés

Hirdetés

Új hozzászólás Aktív témák

  • zodo

    nagyúr

    válasz Vladi #7360 üzenetére

    Csomag telepítése megtörtént ,meg is találom a Usr/bin mappában,de újraíndítás útán semmi. A cikkben említett két sort ,nem tudtam hova beilleszteni. :U
    Megprobáltam ,amit a cikk végén ír,hogy nyomja le a Ctrl+Alt+backspace kombot,de szintén semmi.
    Megnéztem a Etc/Consol-tool mappában lévő Config fájl tartalmát.
    Ebben ennyit találtam:

    # This files tells the console-tools package:
    #
    # - whether to load a specific font and boot (and maybe a screen-font map,
    # but you should avoid that if possible).
    # - whether to setup an Application-Charset Map other than the default CP437.
    # - whether to start "vcstime" to have time on all text VC'S.
    #
    # You can also specify per-VC settings by suffixing variable names as in
    # the examples below. This only works on framebuffer devices.
    #
    # CAVEATS:
    #
    # - When using the new framebuffer devices, the "global setting" for a font
    # only affects the current console (ie., at boot-time, the first one)
    # - ACM setting involves 2 steps (maybe loading a user ACM, and activating
    # it on a given charset slot - see charset(1) for details), the 1st of which
    # affects the entire system, but the 2nd of which only affects the current
    # VC (ie., at boot-time, the first one). So that if you want to use the same
    # ACM on all VCs, you have to specify "APP_CHARSET_MAP_vc<N>=user" for all
    # relevant values of <N>.
    #
    # Example:
    #
    #SCREEN_FONT=iso01.f16
    #SCREEN_FONT_vc2=LatArCyrHeb-16
    #
    #APP_CHARSET_MAP=iso05
    #APP_CHARSET_MAP_vc2=user
    #
    # Set the following - more euro-friendly default than kernel font.
    # SCREEN_FONT=latarcyrheb-sun16.psf

    #DO_VCSTIME=yes
    #
    # Forget this one unless you _know_ it is necessary for your font:
    #SCREEN_FONT_MAP=iso01

    # **** screen saver/DPMS settings: all VCs ****
    # These settings are commented by default to avoid the chance of damage to
    # very old monitors that don't support DPMS signalling.

    # screen blanking timeout. monitor remains on, but the screen is cleared to
    # range: 0-60 min (0==never) kernels I've looked at default to 10 minutes.
    # (see linux/drivers/char/console.c)
    BLANK_TIME=30

    # blanking method (VESA DPMS mode to use after BLANK_TIME, before powerdown):
    # on: the default, no DPMS signalling. near instant powerup, no power saving
    # vsync: DPMS Standby mode. nearly instant recovery, uses 110/120W (17" screen)
    # hsync: DPMS Suspend mode. typically 3s recovery, uses 15/120W (17" screen)
    # powerdown,off: DPMS Off mode, typ. 10s recovery, uses 5/120W (17" screen)

    # Those values are for my 17" Mag, but some monitors do suspend the same as
    # standby. xset dpms force {off|standby|suspend|on} is useful for this, if X
    # supports DPMS on your video card. Set X's DPMS screensaver with xset dpms
    # or use option power_saver in XF86Config
    #
    # DPMS set by default to on, because hsync can cause problems on certain
    # hardware, such as Armada E500 laptops
    BLANK_DPMS=off

    # Powerdown time. The console will go to DPMS Off mode POWERDOWN_TIME
    # minutes _after_ blanking. (POWERDOWN_TIME + BLANK_TIME after the last input)
    POWERDOWN_TIME=30

    # rate and delay can get only specific values, consult kbdrate(1) for help
    #KEYBOARD_RATE="30"
    #KEYBOARD_DELAY="250"

    # Turn on numlock by default
    #LEDS=+num
    SCREEN_FONT=lat2-sun16
    SCREEN_FONT_vc2=lat2-sun16
    SCREEN_FONT_vc3=lat2-sun16
    SCREEN_FONT_vc4=lat2-sun16
    SCREEN_FONT_vc5=lat2-sun16
    SCREEN_FONT_vc6=lat2-sun16

    [ Szerkesztve ]

Új hozzászólás Aktív témák