¿cosa rara?

Hola a todos , acabo de poner un switch en el monitor para enchufar al monitor al mismo tiempo el pc y la xbox360 , y lo curioso es que mi ubuntu solo se puede ver a una resolucion de 640 x 480 y no me deja cambiarla , sin embargo si entro en la particion de win , aqui se puede poner la resolucion que quieras , se supone que es por el switch , pero si acepta una resolucion alta en win tambien deberia aceptarla en linux ¿no?.
A ver si me podeis orientar un poco , o si hay alguna forma de forzar el cambio que no sea en Preferencias - Resolucion.

Muchas gracias.
Te pasa eso posiblemente porque no te reconoce el monitor. Especifica uno manualmente. Salu2
capisergio escribió:Te pasa eso posiblemente porque no te reconoce el monitor. Especifica uno manualmente. Salu2


Gracias por contestar , ¿podrias explicarme (linux para torpes) como se hace? , he estado mirando los menus de preferencias y administracion y no veo como hacerlo.

Muchas gracias
Verás, la distro que uso no tiene asistentes, hay que editar los ficheros a pelo. En cualquier caso la idea es localizar el administrador de Hardware y sustituir el monitor que detecte por uno SVGA con la resolución y el refresco del tuyo en concreto. Salu2
Procura usar siempre el driver "vesa" en lugar del "radeon" o del "ati" y agregale muchas resoluciones asi luego te deja escoger entre varias.
Gracias de nuevo por contestar , pero creo que no habeis leido la parte que ponia que tenia que ser tipo "linux para torpes" [risita] .

Pero bueno , he intentado mirar un poco los archivos dentro de ubuntu , pero tengo que deciros que mi idea de linux fuera del entorno grafico es muy pero que muy pobre.

aun asi , he encontrado dos archivos que creo que pueden tener que ver con lo que me comentais , estan dentro de /etc/vga , uno se llama libvga config , es este:
______________________________________________________________
# Configuration file for svgalib. Default location is /etc/vga.
# Other config file locations: ~/.svgalibrc
# where SVGALIB_CONFIG_FILE points
# Lines starting with '#' are ignored.

# If you have two vga cards with the same pci vendor id, svgalib will try
# to use the first one, even if the second one is active. In that case,
# use PCIStart to force starting the search for a vga card only at a
# specific bus and device numbers. For example, an AGP card is usually on
# bus 1, while pci is on bus 0, so to use the AGP card, uncomment:

# PCIStart 1 0

# Have a deep look at README.config to see what can do here (especially
# for mach32).

# Mouse type:

# mouse Microsoft # Microsoft
# mouse MouseSystems # Mouse Systems
# mouse MMSeries # Logitech MM Series
# mouse Logitech # Logitech protocol (old, newer mice use Microsoft protocol)
# mouse Busmouse # Bus mouse
# mouse PS2 # PS/2 mouse
# mouse MouseMan # Logitech MouseMan
# mouse Spaceball # Spacetec Spaceball
# mouse IntelliMouse # Microsoft IntelliMouse or Logitech MouseMan+ on serial port
# mouse IMPS2 # Microsoft IntelliMouse or Logitech MouseMan+ on PS/2 port
# mouse pnp # plug'n'pray
# mouse WacomGraphire # Wacom Graphire tablet/mouse
# mouse DRMOUSE4DS # Digital Research double-wheeled mouse
# mouse none # None

mouse unconfigured

# (DEBIAN NOTE: the mouse used to default to microsoft, but this was changed
# to fix bug #13458. If your mouse used to work fine, you can simply change
# it back to read "microsoft" again. If you are careful to change *only that
# one word*, and not to add or remove extra whitespace, the package
# installation will continue to update this file without requiring user
# intervention because of a modified config file.
# This applies to all mouse types, not just microsoft.)

# Mouse/keyboard customisation by 101 (Attila Lendvai). If you have any good
# ideas you can reach me at 101@kempelen.inf.bme.hu

# mouse_accel_type normal # No acceleration while delta is less then
# threshold but delta is multiplied by
# mouse_accel_mult if more. Originally done by
# Mike Chapman mike@paranoia.com

mouse_accel_type power # The acceleration factor is a power function
# of delta until it reaches m_accel_mult. It
# starts from the coordinate
# [1, 1 + m_accel_offset] and goes to
# [m_accel_thresh, m_accel_mult]. If delta
# is bigger then m_accel_thresh it is a plain
# constant (m_accel_mult). It is the f(delta)
# function with which the delta itself will be
# multiplied. m_accel_offset is 1 by default,
# so for delta = 1 the accelerated delta will
# remain 1 (You don't lose resolution). The
# starting point of the f(delta) function
# might be moved along the Y axis up/down with
# m_accel_offset thus defining the initial
# minimum acceleration (for delta = 1).
# Basically it's like the normal mode but the
# acceleration factor grows as you move your
# mouse faster and faster, not just turns in
# and out. Threshold is the point from where
# the f(delta) function gets linear.
# This is the one I use for *uaking... =)

# mouse_accel_type off # No comment...


mouse_accel_mult 60 # This is the number with which delta will
# be multiplied. Basically it's the number
# that defines how big the acceleration will
# be

mouse_accel_thresh 4 # This is the threshold. See description by
# power

mouse_accel_power 0.8 # This is the second parameter of the power
# function used in power mode. Used only by
# the power mode

mouse_accel_offset 30 # This is the offset of the starting point
# on the Y axis. With this you can define the
# number that will multiply delta = 1 so it's
# the initial acceleration.

# mouse_accel_maxdelta 600 # This is an upper limit for delta after
# the acceleration was applied

# mouse_maxdelta 30 # This is an upper limit for the delta
# before the acceleration. With this one you
# can limit the biggest valid delta that
# comes from the mouse.

# mouse_force # Force parameters even if they seem strange
# By default svgalib prints an error if any
# of the numbers are somhow out of the
# reasonable limit, (Like a negative mult :)
# and uses the default that's in vgamouse.h

# Usually /dev/mouse will be a link to the mouse device.
# However, esp. with the Spacetec Spaceball you may
# want to specify a different device for svgalib to use

# mdev /dev/ttyS0 # mouse is at /dev/ttyS0

# Some multiprotocol mice will need one of the following:

# setRTS # set the RTS wire.
# clearRTS # clear the RTS wire.
# leaveRTS # leave the RTS wire alone (default) (Wire is usually set)
# setDTR # set the DTR wire.
# clearDTR # clear the DTR wire.
# leaveDTR # leave the DTR wire alone (default) (Wire is usually set)

# On mice such as the Microsoft IntelliMouse and Logitech MouseMan+, turning
# the wheel rotates the mouse around the X axis. mouse_wheel_steps controls
# how many steps make up a full 360-degree turn and thus how much rotation
# occurs with each step. The default is 18 steps (20 degrees per step), the
# real-world value for the IntelliMouse. Adjust it to match your mouse or to
# suit your preferences; a negative number reverses the direction and zero
# disables rotation.

mouse_wheel_steps 18 # For MS IntelliMouse (default)
# mouse_wheel_steps 24 # For Logitech FirstMouse+
# mouse_wheel_steps -18 # Reverses direction
# mouse_wheel_steps 0 # Disables rotation

# mouse_fake_kbd_event sends a fake keyboard event to the program when the
# wheel on a Microsoft IntelliMouse, Logitech MouseMan+, or similar wheel
# mouse is turned. This can be useful for programs that do not recognize the
# Z axis, but only works with some programs that use raw keyboard.
# The format is:
#
# mouse_fake_kbd_event upscancode downscancode
#
# The up and down scancodes are the scancodes of the keys to simulate when
# the wheel is turned up and down, respectively.
#
# Scancodes can be specified numerically or symbolically; the symbolic names
# are determined by the keymap (see below), if no keymap is loaded the default
# is the standard US QWERTY keyboard with the following names available:
# letters (a-z), numbers (zero-nine), function keys (F1-F12), the keypad
# numbers (KP_0-KP_9) and other keys (KP_Multiply, KP_Subtract, KP_Add,
# KP_Period, KP_Enter, and KP_Divide), and the following - minus, equal,
# Delete, Tab, bracketleft, bracketright, Return, Control, semicolon,
# apostrophe, grave, Shift, backslash, comma, period, slash, Shift, Alt, space,
# Caps_Lock, Num_Lock, Scroll_Lock, Last_Console, less, Control_backslash,
# AltGr, Break, Find, Up, Prior, Left, Right, Select, Down, Next, Insert,
# and Remove.
#
# Note that this option has no effect unless the IntelliMouse or IMPS2 mouse
# type is used (see above). Also note that the simulated keypresses are
# instantaneous, so they cannot be used for functions that require a key to
# be held down for a certain length of time.

# This example simulates a press of the left bracket ([) when the wheel is
# turned up and a press of the right bracket (]) when the wheel is turned
# down (good for selecting items in Quake II):
# mouse_fake_kbd_event bracketleft bracketright

# Keyboard config:

# kbd_keymap allows you to use an alternate keyboard layout with programs that
# use raw keyboard support by translating scancodes from the desired layout to
# their equivalents in the layout expected by the program. This option has no
# affect on programs that do not use raw keyboard.
#
# Keymap files to convert between any two arbitrary keyboard layouts can be
# generated with the svgakeymap utility, but there are limitations to the
# translations that can be performed. Read the file README.keymap in the
# svgalib documentation directory for more in-depth information.
#
# You must specify the full path to the keymap file; it is recommended that
# keymaps be kept in the same directory as libvga.config, normally /etc/vga.
# The keymap specified in the configuration file can be overriden by setting
# the environment variable SVGALIB_KEYMAP to point to another keymap file;
# this can be useful for setting keymaps on a per-program basis.
#
# This example will use the provided US-Dvorak to US-QWERTY map to allow a
# Dvorak keyboard layout to be used with a program that expects a standard US
# QWERTY keyboard, for instance Quake:
# kbd_keymap /etc/vga/dvorak-us.keymap

# There is a potential security risk in allowing users to remap keyboard
# scancodes at will; with this option enabled only keymap files owned by
# root can be used. Normally you should leave this on, but if you have a
# single-user box or you really trust your users you may find it convenient
# to run without it and allow users to load arbitrary keymaps.

kbd_only_root_keymaps

# kbd_fake_mouse_event, as it says, sends a fake mouse event to the program.
# The format is: kbd_fake_mouse_event scancode [flag(s)] command [argument]
# Scancode is a raw scancode or a descriptive name, the same as with fake
# keyboard events (see above). If you use keymap conversion, specify
# scancodes for the keyboard layout the program will receive.
# Flags: down - trigger event when the key is pressed (default)
# up - the opposite
# both - trigger in both case, if pressed/released
# repeat - repeat events if the key is kept pressed (off by default)
# commands: delta[xyz] - send a fake delta event as if you have moved your
# mouse. If the parameter is 'off' / 'on' it will turn
# off/on the respective mouse axis (requires a
# parameter, of course)
# button[123] - send a fake event that the mouse button is pressed
# or released that's given by the parameter.
# ('pressed' or 'released')
# Here are some examples:

# This is one I use in *uake: it turns around, looks down a bit and when the
# key is released it does the opposite, so it gets back to the starting state.
# With this one and the help of a rocket you can fly though the whole map :)
# (Scancode 28 is enter)
# kbd_fake_mouse_event 28 both deltax 8182 down deltay -1500 up deltay 1500

# This one will switch off the y axis of the mouse while the key (right ctrl)
# is kept pressed.
# kbd_fake_mouse_event 97 down deltay off up deltay on

# This one is the same as if you were pressing the left mouse button. (But
# if you move your mouse then the button state will reset even if you keep
# right ctrl down...)
# kbd_fake_mouse_event 97 down button1 pressed up button1 released

# Monitor type:

# Only one range can be specified for the moment. Format:
# HorizSync min_kHz max_kHz
# VertRefresh min_Hz max_Hz

# Typical Horizontal sync ranges
# (Consult your monitor manual for Vertical sync ranges)
#
# 31.5 - 31.5 kHz (Standard VGA monitor, 640x480 @ 60 Hz)
# 31.5 - 35.1 kHz (Old SVGA monitor, 800x600 @ 56 Hz)
# 31.5 - 35.5 kHz (Low-end SVGA, 8514, 1024x768 @ 43 Hz interlaced)
# 31.5 - 37.9 kHz (SVGA monitor, 800x600 @ 60 Hz, 640x480 @ 72 Hz)
# 31.5 - 48.3 kHz (SVGA non-interlaced, 800x600 @ 72 Hz, 1024x768 @ 60 Hz)
# 31.5 - 56.0 kHz (high frequency, 1024x768 @ 70 Hz)
# 31.5 - ???? kHz (1024x768 @ 72 Hz)
# 31.5 - 64.3 kHz (1280x1024 @ 60 Hz)

HorizSync 31.5 35.5
VertRefresh 50 90

# If you have a NeoMagic card on a Toshiba Libretto 100, 110 use that instead

# HorizSync 31.5 70
# VertRefresh 50 100
# Modeline "800x480" 50 800 856 976 1024 480 483 490 504 +hsync +vsync
# newmode 800 480 256 800 1
# newmode 800 480 32768 1600 2
# newmode 800 480 65536 1600 2
# newmode 800 480 16777216 2400 3

# Monitor timings
#
# These are prefered over the default timings (if monitor and chipset
# can handle them). Not all drivers use them at the moment, and Mach32
# has its own syntax (see below).
# The format is identical to the one used by XFree86, but the label
# following the modeline keyword is ignored by svgalib.
#
# Here some examples:

# modeline "640x480@100" 43 640 664 780 848 480 483 490 504
# modeline "800x600@73" 50 800 856 976 1024 600 637 643 666
# modeline "1024x768@75" 85 1024 1048 1376 1400 768 771 780 806

# It seems there is a need for a 512x384 mode, this timing was donated
# by Simon Hosie : (it is 39kHz horz by 79Hz vert)

# Modeline "512x384@79" 25.175 512 522 598 646 384 428 436 494

# Here's a 400x300 Modeline (created by svidtune). Note that for
# doublescan modes, the Vertical values are half the real one (so XFree86
# modelines can be used).

# Modeline "400x300@72" 25.000 400 440 504 520 300 319 322 333 doublescan

# Here is a mode for a ZX Spectrum emulator:
# Modeline "256x192@73" 12.588 256 269 312 360 192 208 212 240 doublescan
# newmode 256 192 256 256 1

# the width must be divisible by 8. Some cards require even divisiblity by
# 16, so that's preferable, since there are no standard modes where the
# width is not divisible by 16.

# The following modes are defined in svgalib, but have no timings in
# timing.c, so you'll have to add a modeline in order to use them:
# 1280x720, 1360x768, 1800x1012, 1920x1080, 1920x1440, 2048x1152
# and 2048x1536

# Mach32 timings:

# e.g. Setup a 320x200 mode for the mach32:

#define 320x200x32K 320x200x64K 320x200x16M 320x200x16M32
# 16 320 392 464 552 200 245 265 310

# These are REQUIRED for above mode, please edit to suit your monitor.
# (No, I won't pay for a new one)
# HorizSync 29 65
# VertRefresh 42 93.5

# Chipset type:
#
# Use one of the following force chipset type.
# Autodetects if no chipset is specified.
#
# If you have a PCI or AGP card, don't use chipset type forcing.
# If the card is not autodetected, its a bug, and it will probably
# not work even with forcing. Try running vgatest (with no chipset
# line), and send to me (matan@svgalib.org) the output, a copy of
# /proc/pci (or lspci -n -vv) and whatever info you have on the card.
#
# If a chipset driver gives trouble, try forcing VGA.

# chipset VGA # Standard VGA
# chipset EGA # EGA
# chipset ET3000 # Tseng ET3000
# chipset ET4000 # Tseng ET4000
# chipset Cirrus # Cirrus Logic GD542x
# chipset TVGA # Trident TVGA8900/9000
# chipset Oak # Oak Technologies 037/067/077
# chipset S3 # S3 chipsets
# chipset GVGA6400 # Genoa 6400
# chipset ARK # ARK Logic
# chipset ATI # old ATI VGA
# chipset Mach32 # ATI Mach32
# chipset ALI # ALI2301
# chipset Mach64 # ATI Mach64 - deprecated
# chipset ET6000 # Tseng ET6000
# chipset APM # Alliance Technology AT 24/25/3D
# chipset NV3 # nVidia Riva 128 / TNT / GeForce
# chipset VESA # nicely behaved Vesa Bioses
# chipset MX # MX86251 (some Voodoo Rush boards)
# chipset PARADISE # WD90C31
# chipset RAGE # RagePro (and might work with some older mach64)
# chipset BANSHEE # Banshee/V3.
# chipset SIS # SiS 5597/6326/620/530 cards / integrated vga.
# chipset I740 # Intel i740 based cards.
# chipset NEOMAGIC
# chipset LAGUNA # Cirrus Logic Laguna series (546X)
# chipset FBDEV # Use kernel fbdev, instead of direct hardware.
# chipset G400 # Matrox Mystique/G100/G200/G400/G450
# chipset R128 # Ati Rage128
# chipset SAVAGE # S3 chipsets Savage
# chipset C&T # Chips and Technologies

# EGA Color/mono mode:
# Required if chipset is EGA.
#
# Use one of the following digits to force color/mono:

# monotext # Card is in monochrome emulation mode
# colortext # Card is in color emulation mode
colortext

# RAMDAC support:
# Some chipsets (e.g. S3 and ARK) allows specifying a RAMDAC type.
# If your RAMDAC is not autodetected, you can try specifying it.
# Do NOT specify a RAMDAC if you card uses the S3 Trio chipset
# (the RAMDAC is built in).

# Ramdac Sierra32K
# Ramdac SC15025
# Ramdac SDAC # S3 SDAC
# Ramdac GenDAC # S3 GenDAC
# Ramdac ATT20C490 # AT&T 20C490, 491, 492 (and compatibles)
# Ramdac ATT20C498 # AT&T 20C498
# Ramdac IBMRGB52x # IBM RGB524, 526, 528 (and compatibles)

# Dotclocks:
# Some chipsets needs a list of dot clocks for optimum operation. Some
# includes or supports a programmable clock chip. You'll need to specify
# them here.

# Fixed clocks example:
# (The following is just an example, get the values for your card from
# you XF86Config)

# Clocks 25.175 28.3 40 70 50 75 36 44.9 0 118 77 31.5 110 65 72 93.5

# Programmable clockchip example:

# Clockchip ICD2061A # The only one supported right now



# Here are miscellaneous options to help with specific problems.

# VesaText # Helps the VESA driver with text mode restoration
# problems.

# VesaSave 14 # changing value might help text mode restoring
# problems with VESA driver. Legal values: 0-15

# NoVCControl # Disables svgalib's finding a new VC if run
# from X. Good fo using dumpreg under X, but
# probably bad for standard usage.


# RageDoubleClock # If your card is based on ATI's rage card, and
# the pixel clock is double what it should be
# (main symptom is some modes are out of sync),
# try enabling this. If it helps, please report to
# me (matan@svgalib.org)

# NeoMagicLibretto100
# Enable if you have a NeoMagic card on a Toshiba
# Libretto 100, 110, etc

_______________________________________________________________










jo*** la leche ...

El otro se llama libvga.et4000 y el contenido es este:







_______________________________________________________________


/* ET4000 registers from SVGALIB 0.81 */

/* Define DAC_TYPE to force the DAC type used in the ET4000 driver. If it */
/* is not defined, the driver tries to autodetect the DAC type which may go */
/* wrong. */

/* Use the following values:
0: Ordinary DAC
1: Sierra SC11486 (32k)
3: Sierra 32k/64k
5: SS2410 15/24bit DAC
9: AT&T 20c491/2 (32k/64k/24bit)
17: Acumos ADAC (Cirrus Logic DAC)
33: Sierra 15025/6 24-bit DAC
*/

#define DAC_TYPE 0

/* unsupported modes */
#define g320x200x64K_regs DISABLE_MODE
#define g320x200x16M_regs DISABLE_MODE
#define g800x600x16_regs DISABLE_MODE
#define g1024x768x16_regs DISABLE_MODE
#define g1280x1024x16_regs DISABLE_MODE


/* Got this mode from someone's tseng3.exe dump. */
/* ET4000 HiColor BIOS mode 0x13 -- 320x200x32k */
/* Video timing: Vertical frequency : 70.3Hz
Horizontal frequency : 31.6KHz */
static unsigned char g320x200x32K_regs[73] =
{
0x5F, 0x4F, 0x50, 0x82, 0x54, 0x80, 0xBF, 0x1F, 0x00, 0x41, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x9C, 0x8E, 0x8F, 0x50, 0x60, 0x96, 0xB9, 0xAB,
0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B,
0x0C, 0x0D, 0x0E, 0x0F, 0x01, 0x00, 0x0F, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x40, 0x05, 0x0F, 0xFF,
0x03, 0x01, 0x0F, 0x00, 0x0E,
0x63,
0x00, 0x00, 0x28, 0x00, 0x08, 0x00, 0x43, 0x0F, 0x00, 0xFC, 0x00, 0x00,
0x00
};

/* ET4000 BIOS mode 2Eh - 640x480x256 */
static unsigned char g640x480x256_regs[73] =
{
0x5F, 0x4F, 0x50, 0x82, 0x54, 0x80, 0x0B, 0x3E, 0x00, 0x40, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0xEA, 0x8C, 0xDF, 0x50, 0x60, 0xE7, 0x04, 0xAB,
0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B,
0x0C, 0x0D, 0x0E, 0x0F, 0x01, 0x00, 0x0F, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x40, 0x05, 0x0F, 0xFF,
0x03, 0x01, 0x0F, 0x00, 0x0E,
0xE3,
0x00, 0x00, 0x28, 0x00, 0x08, 0x00, 0x03, 0x0F, 0x00, 0xFC, 0x00, 0x00,
0x00
};

/* ET4000 BIOS mode 30h - 800x600x256 */
static unsigned char g800x600x256_regs[73] =
{
0x7F, 0x63, 0x64, 0x02, 0x6A, 0x1D, 0x77, 0xF0, 0x00, 0x60, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x5D, 0x8F, 0x57, 0x64, 0x60, 0x5B, 0x74, 0xAB,
0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B,
0x0C, 0x0D, 0x0E, 0x0F, 0x01, 0x00, 0x0F, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x40, 0x05, 0x0F, 0xFF,
0x03, 0x01, 0x0F, 0x00, 0x0E,
0xE3,
0x00, 0x00, 0x28, 0x00, 0x0A, 0x00, 0x03, 0x0F, 0x00, 0xFC, 0x00, 0x00,
0x00
};

/* ET4000 BIOS mode 38h - 1024x768x256 */
static unsigned char g1024x768x256_regs[73] =
{
0xA1, 0x7F, 0x80, 0x04, 0x89, 0x99, 0x26, 0xFD, 0x00, 0x60, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x08, 0x8A, 0xFF, 0x80, 0x60, 0x04, 0x22, 0xAB,
0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B,
0x0C, 0x0D, 0x0E, 0x0F, 0x01, 0x00, 0x0F, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x40, 0x05, 0x0F, 0xFF,
0x03, 0x01, 0x0F, 0x00, 0x0E,
0xEB,
0x00, 0x00, 0x28, 0x00, 0x08, 0x00, 0x03, 0x0F, 0x00, 0xBC, 0x00, 0x00,
0x00
};

static unsigned char g800x600x32K_regs[73] =
{
0xF9, 0xC7, 0xC9, 0x9B, 0xCF, 0x8F, 0x78, 0xF0, 0x00, 0x60, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x5C, 0x8E, 0x57, 0xC8, 0x60, 0x5B, 0x75, 0xAB,
0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B,
0x0C, 0x0D, 0x0E, 0x0F, 0x01, 0x00, 0x0F, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x40, 0x05, 0x0F, 0xFF,
0x03, 0x01, 0x0F, 0x00, 0x0E,
0xEF,
0x00, 0x00, 0x28, 0x00, 0x08, 0x00, 0x03, 0x0F, 0x00, 0xBC, 0x00, 0x00,
0x06
};
#define g800x600x64K_regs g800x600x32K_regs

static unsigned char g640x480x16M_regs[73] =
{
0x27, 0xEF, 0xF2, 0x88, 0xF8, 0x98, 0x0B, 0x3E, 0x00, 0x40, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0xEA, 0x0C, 0xDF, 0xF0, 0x60, 0xE7, 0x04, 0xAB,
0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B,
0x0C, 0x0D, 0x0E, 0x0F, 0x01, 0x00, 0x0F, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x40, 0x05, 0x0F, 0xFF,
0x03, 0x01, 0x0F, 0x00, 0x0E,
0xEF,
0x00, 0x00, 0x28, 0x00, 0x0A, 0x00, 0x03, 0x0F, 0x01, 0xBC, 0x00, 0x00,
0x00
};

static unsigned char g640x480x32K_regs[73] =
{
0xC3, 0x9F, 0xA1, 0x85, 0xA7, 0x1F, 0x0B, 0x3E, 0x00, 0x40, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0xEA, 0x8C, 0xDF, 0xA0, 0x60, 0xE7, 0x04, 0xAB,
0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B,
0x0C, 0x0D, 0x0E, 0x0F, 0x01, 0x00, 0x0F, 0x00, 0x00,
0x00, 0x00, 0x00, 0x00, 0x00, 0x40, 0x05, 0x0F, 0xFF,
0x03, 0x01, 0x0F, 0x00, 0x0E,
0xE3,
0x00, 0x00, 0x28, 0x00, 0x08, 0x00, 0x03, 0x0F, 0x00, 0xBC, 0x00, 0x00,
0x00
};
#define g640x480x64K_regs g640x480x32K_regs
_______________________________________________________________

Si veis algo que creais que modificandolo solucionaria el problema . os lo agradeceria mucho.

Se aceptan todo tipo de sugerencias

Gracias de nuevo :-?
En esos archivos no tienes que tocar nada.
Si no tienes un asistente gráfico en ubuntu para configurar eso (que digo yo que tendrá, pero sin usarla no puedo saber seguro) lo que tendrías que tocar es /etc/X11/xorg.conf

En Section "Monitor" puedes especificar las características de tu monitor (mayormente el refresco vertical y horizontal) y en Section "Screen" vienen las resoluciones disponibles para cada nivel de profundidad de color. Si quieres usar una resolución que no venga ahí, pues la añades.


Si sigues sin verlo nada claro, pega aquí tu xorg.conf
kornshell escribió:En esos archivos no tienes que tocar nada.
Si no tienes un asistente gráfico en ubuntu para configurar eso (que digo yo que tendrá, pero sin usarla no puedo saber seguro) lo que tendrías que tocar es /etc/X11/xorg.conf

En Section "Monitor" puedes especificar las características de tu monitor (mayormente el refresco vertical y horizontal) y en Section "Screen" vienen las resoluciones disponibles para cada nivel de profundidad de color. Si quieres usar una resolución que no venga ahí, pues la añades.


Si sigues sin verlo nada claro, pega aquí tu xorg.conf


Muchas gracias por tu interes.

he estado mirando el fichero xorg.conf y he ido donde me dices que mire en la seccion screen , y la verdad es que ahi me aparecen bastantes modos , echale un vistazo tu mismo a ver si me puedes ayudar

gracias de nuevo.


# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
FontPath "/usr/share/X11/fonts/misc"
FontPath "/usr/share/X11/fonts/cyrillic"
FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/X11/fonts/Type1"
FontPath "/usr/share/X11/fonts/CID"
FontPath "/usr/share/X11/fonts/100dpi"
FontPath "/usr/share/X11/fonts/75dpi"
# paths to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"
EndSection

Section "Module"
Load "GLcore"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "type1"
Load "vbe"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "es"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection

Section "Device"
Identifier "NVIDIA Corporation NV15DDR [GeForce2 Ti]"
Driver "nv"
BusID "PCI:1:0:0"
EndSection

Section "Monitor"
Identifier "L1915S"
Option "DPMS"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "NVIDIA Corporation NV15DDR [GeForce2 Ti]"
Monitor "L1915S"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1280x1024" "1024x768" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1280x1024" "1024x768" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1280x1024" "1024x768" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "720x400" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "720x400" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section "DRI"
Mode 0666
EndSection
Pues 2 cosas que puedes probar:

1- Instalar el driver de nvidia en vez de usar el nv que viene con la distro. Abre synaptic, busca el driver de nvidia y dile que te lo instale.
Luego en el xorg.conf donde pone Driver "nv" lo cambias por Driver "nvidia" y reinicias las X (o reinicias el ordenador directamente, como quieras).

2- Mira en el manual de tu monitor qué frecuencias de refresco admite, y especifícalas en la sección "Monitor". Si por ejemplo tu monitor soportase refresco vertical entre 60 y 120, y horizontal entre 40 y 100, te quedaría tal que así:

Section "Monitor"
Identifier "L1915S"
VertRefresh 60.0 - 120.0
HorizSync 40.0 - 100.0
Option "DPMS"
EndSection
kornshell escribió:Pues 2 cosas que puedes probar:

1- Instalar el driver de nvidia en vez de usar el nv que viene con la distro. Abre synaptic, busca el driver de nvidia y dile que te lo instale.
Luego en el xorg.conf donde pone Driver "nv" lo cambias por Driver "nvidia" y reinicias las X (o reinicias el ordenador directamente, como quieras).

2- Mira en el manual de tu monitor qué frecuencias de refresco admite, y especifícalas en la sección "Monitor". Si por ejemplo tu monitor soportase refresco vertical entre 60 y 120, y horizontal entre 40 y 100, te quedaría tal que así:

Section "Monitor"
Identifier "L1915S"
VertRefresh 60.0 - 120.0
HorizSync 40.0 - 100.0
Option "DPMS"
EndSection


Te cuento , despues de varias horas de trasteo , te resumo lo que he hecho , he instalado desde synaptic todo lo que he visto que tenia que ver con nvidia (exepto algunas cosas para procesadores pentiun , ya que yo tengo amd) pero al cambiar en xorg.conf lo de nv por nvidia , me dice que no encuentra los drivers y no me carga el entorno grafico.

he intentado instalar los drivers , bajandolos de la pagina de nvidia , pero me dice (en ingles) que tiene que descargar de envidia el entorno para x , o algo asi pero cuando va a descargar da un error porque dice que no puede descargar y luego dice que no encuentra no se que de gcc.

En fin que sigo igual :(
Si no encuentra gcc, usa synaptic para instalarlo, y luego vuelve a probar con lo del driver. Lo de que de ese error al descargar cuando instalas el driver da igual, lo que pasa es que no encuentra un módulo precompilado apto para tu kernel y lo que hace entonces es compilar uno.
kornshell escribió:Si no encuentra gcc, usa synaptic para instalarlo, y luego vuelve a probar con lo del driver. Lo de que de ese error al descargar cuando instalas el driver da igual, lo que pasa es que no encuentra un módulo precompilado apto para tu kernel y lo que hace entonces es compilar uno.


A ver creo que lo del gcc ya lo he solucionado , solo que en un momento de la instalacion del driver me dice que anteriormente se usó la version 3.4 y ahora está la 4.0 (hablo del gcc) , pero me dice que si quiero que continue , continuo y me da un error que me dice algo asi como que no encuentra el "kernel source tree " ; te pego el informe de errores que me mete en un archivo:

nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Tue Feb 21 20:24:41 2006

option status:
license pre-accepted : false
update : false
force update : false
expert : false
uninstall : false
driver info : false
no precompiled interface: false
no ncurses color : false
query latest driver ver : false
OpenGL header files : true
no questions : false
silent : false
no backup : false
kernel module only : false
sanity : false
add this kernel : false
no runlevel check : false
no network : false
no ABI note : false
no RPMs : false
force tls : (not specified)
force compat32 tls : (not specified)
X install prefix : /usr/X11R6
OpenGL install prefix : /usr
compat32 install prefix : (not specified)
installer install prefix: /usr
utility install prefix : /usr
kernel name : (not specified)
kernel include path : (not specified)
kernel source path : (not specified)
kernel output path : (not specified)
kernel install path : (not specified)
proc mount point : /proc
ui : (not specified)
tmpdir : /tmp
ftp mirror : ftp://download.nvidia.com
RPM file list : (not specified)

Using: nvidia-installer ncurses user interface
-> License accepted.
-> No precompiled kernel interface was found to match your kernel; would you li
ke the installer to attempt to download a kernel interface for your kernel f
rom the NVIDIA ftp site (ftp://download.nvidia.com)? (Answer: Yes)
-> No matching precompiled kernel interface was found on the NVIDIA ftp site;
this means that the installer will need to compile a kernel interface for
your kernel.
-> Performing CC test with CC="cc".
-> gcc-version-check failed:


You appear to be comiling the NVIDIA kernel module with a different compiler
than the one that was used to compile the running kernel. The Linux 2.6 ker
nel module loader rejects kernel modules built with a version of gcc that do
es not exactly match that of the compiler used to build the running kernel.
The compiler used to compile the kernel was gcc 3.4; the current compiler is
gcc 4.0.

If you know what you are doing and want to ignore the gcc version check, sel
ect "No" to continue installation. Otherwise, select "Yes" to abort install
ation, set the CC environment variable to the name of the compiler used to c
ompile your kernel, and restart installation. Abort now? (Answer: No)
ERROR: Unable to find the kernel source tree for the currently running kernel.
Please make sure you have installed the kernel source files for your
kernel and that they are properly configured; on Red Hat Linux systems,
for example, be sure you have the 'kernel-source' RPM installed. If you
know the correct kernel source files are installed, you may specify the
kernel source path with the '--kernel-source-path' command line option.
ERROR: Installation has failed. Please see the file
'/var/log/nvidia-installer.log' for details. You may find suggestions
on fixing installation problems in the README available on the Linux
driver download page at http://www.nvidia.com.


No se , hasta ahora estaba bastante contento con ubuntu , pero quizas debia haber elegido otra distro mas para principiantes , con mas asistentes , ¿cual crees tu que en caso de cambiar a otra sería la más interesante? , porque no se al final si voy a poder solucionar esto , a pesar de tu inestimable ayuda.


muchas gracias
:-|
Lo que necesitarías para poder instalar el driver es por una parte, como te está diciendo, el gcc 3.4, que tiene que estar en synaptic supongo, y por otra parte las sources del kernel.
Para saber qué sources necesitas haz un uname -r, y luego busca en synaptic las sources de esa misma versión del kernel.
Siempre que quieras compilar un módulo para el kernel (que van a ser pocas veces aparte de para esto del driver de nvidia) necesitarás las fuentes del kernel que estés usando, así que si algún día te apetece actualizar el kernel acuérdate de instalar también las sources correspondientes y así ya te quitas de problemas.

Una vez tengas esas dos cosas debería ir sin problemas.

Lo de la distro no se, he oido por ahí alguna vez sobre alguna distribución que trae ya de serie los drivers de nvidia pero ahora mismo no sabría decirte cual es.
kornshell escribió:Lo que necesitarías para poder instalar el driver es por una parte, como te está diciendo, el gcc 3.4, que tiene que estar en synaptic supongo, y por otra parte las sources del kernel.
Para saber qué sources necesitas haz un uname -r, y luego busca en synaptic las sources de esa misma versión del kernel.
Siempre que quieras compilar un módulo para el kernel (que van a ser pocas veces aparte de para esto del driver de nvidia) necesitarás las fuentes del kernel que estés usando, así que si algún día te apetece actualizar el kernel acuérdate de instalar también las sources correspondientes y así ya te quitas de problemas.

Una vez tengas esas dos cosas debería ir sin problemas.

Lo de la distro no se, he oido por ahí alguna vez sobre alguna distribución que trae ya de serie los drivers de nvidia pero ahora mismo no sabría decirte cual es.


Bueno , al final despues de intentarlo todo sin exito he decidido darme por vencido , pero no he dicho irme de linux , me he instalado suse 9.3 a ver que tal me va , de momento me ha dejado elegir la resolución que ya es algo :) , per o claro ahora me encuentro con una distro nueva y nuevos problemas , te voy a comentar una primera cosa que me pasa , el tema de los videos de win , que ya sabes que de primeras no se ven , al intentar abrir el primero me ha enviado a un enlace para bajarme unos ficheros para poder verlos (codecs de win) que vienen dentro de un .zip y no consigo añadir estos codecs a cafeine , que veo que es un reproductor que viene , supongo que el sistema será un poco distinto a ubuntu ; si te apetece y tienes tiempo me contestas y si no ya lo iré averiguando.
En cualquier caso gracias de nuevo por la ayuda de todos estos días [ok]
Para los codecs, y para todo en general, lo más fácil es que uses el administrador de paquetes que traiga la distro, que en Suse creo que es YUM. Busca e instala un paquete llamado win32codecs y ya podrás ver prácticamente todo tipo de vídeos.
14 respuestas