wrong full screen resolution - no sound

Added by buegeleisen over 4 years ago

hello,

let's start with the resolution:

Linux lipwig 2.6.36.1-lipwig.2.0 #1 SMP Wed Dec 1 20:38:50 CET 2010 x86_64 GNU/Linux

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.10
DISTRIB_CODENAME=maverick
DISTRIB_DESCRIPTION="Ubuntu 10.10"

(also tried with default kernel, same thing)

nvidia driver 260.19.21 with a GeForce GTX 460

i'm using two monitors with twinview, 1920x1200 + 1280x1024. when starting full-screen-mode the only resolution i can use is 3200x1200 stretched over both monitors, what isn't exactly what i would expect.

relevant part of xorg.conf:

<!-- snip -->
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "DELL U2410"
HorizSync 30.0 - 81.0
VertRefresh 56.0 - 76.0
Option "DPMS"
EndSection

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX 460"
EndSection

Section "Screen"

  1. Removed Option "metamodes" "DFP-0: nvidia-auto-select +0+0, DFP-2: nvidia-auto-select +1920+0"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "TwinView" "1"
    Option "metamodes" "DFP-0: 1920x1200 +0+0, DFP-2: 1280x1024 +1920+0"
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    <!-- snap -->

the other problem is that i don't get any sound.

03:00.0 Audio device: Creative Labs X-Fi Titanium series [EMU20k2] (rev 03)

the audio controller built into the graphics card is disabled via /etc/modules.

i sometimes have problems playback for example with vlc when set to standard-device because ubuntu sometimes changes the device numbers (sometimes front is 0,0, sometimes it's 0,1, what is the reason why i disabled the nvidia-audio, because then it kept switching between 0,0, 0,1 and 1,1).

so the question here is if there is any way to manually set the audio device for ryzom, too.

cheerio

ps: logfile attached

log.log - logfile (915.7 kB)


Replies (3)

RE: wrong full screen resolution - no sound - Added by kervala over 4 years ago

For your problem about your screens, we need to implement Xinerama, for the moment, you can still play in windowed mode :)

About your soundcard, since it's a Creative card, don't you have hardware accelerated drivers for Linux ?

RE: wrong full screen resolution - no sound - Added by buegeleisen over 4 years ago

For your problem about your screens, we need to implement Xinerama, for the moment, you can still play in windowed mode :)

already found a solution via google, nvidia has an option called metamode. looks for example like that:

Option         "metamodes" "DFP-0: 1920x1200 +0+0, DFP-2: 1280x1024 +1920+0;DFP-0: 1920x1200 +0+0, DFP-2: NULL"

now applications see as an option 1920x1200 and no second monitor, and if it is enabled the second monitor just gets black. and the best thing: applications set to the second monitor (like konsole or amarok) remember their position and do not "crash" into the first screen :).

About your soundcard, since it's a Creative card, don't you have hardware accelerated drivers for Linux ?

with 2.6.33 (or maybe a version earlier or later) snd_ctxfi has been accepted into the linux kernel (which was my original reason to compile my own kernel, because ubuntu 10.4 had 2.6.32 and no driver for emu20k2).

but about the device number switching, looks like blacklisting the driver (snd_hda_codec_nvhdmi) didn't help because the soundcard can also be controlled through snd_hda_intel which just got loaded instead. so i'll blacklist that one too, reboot and look what happens to sound in ryzom :).

RE: wrong full screen resolution - no sound - Added by buegeleisen over 4 years ago

so, fullscreen just works perfect now.

the rogue sound card is away, too, but still no sound with ryzom.

but i see the following lines in log.log:

<!-- snip -->
2010/12/01 23:35:12 INF 4122118496 <Unknown> common.cpp 547 Exception : Exception will be launched: AL: Failed to open device
2010/12/01 23:35:12 WRN 4122118496 <Unknown> audio_mixer_user.cpp 463 initDevice : AL: Failed to open device
<!-- snap -->

any idea?

(1-3/3)