SliTaz Forum

5.0 - unsufficient resolution

(7 posts) (3 voices)

• Started 9 years ago by michaelbischof
• Latest reply from michaelbischof
• This topic is resolved

Tags:

No tags yet.

1. 

   michaelbischof
   

   offline

   Member

   I just installed from a 5.0 Live-CD to the harddrive. Using the Live-CD I had the correct monitor resolution of 1280 x 1024, but after booting from the harddrive it is only 1024x768.
   I use an old Nvidia card
   [blockquote]05:00.0 VGA compatible controller: NVIDIA Corporation NV44 [GeForce 7100 GS] (rev a1)[/blockquote]
   lsmod shows that for video nouveau is used. The Xorg Vesa video driver is installed. But how to make use of it?
   [blockquote]
   root@slitaz:~$ ls /etc/X11/xorg.conf.d/
   35-synaptics.conf 40-Keyboard.conf 40-evdev.conf 45-synaptics.conf
   [/blockquote]
   Any ideas available here?

   Posted 9 years ago #
2. 

   mojo
   

   offline

   Key Master

   5.0 live cd includes 2 video drivers xorg-xf86-video-fbdev and xorg-xf86-video-vesa
   Check /var/log/Xorg.0.log when booted live with 1280x1024 compared to booted in the install at 1024x768 to see which video driver is in use.

   Posted 9 years ago #
3. 

   az_ua
   

   offline

   Moderator

   http://root:root@tazpanel:82/pkgs.cgi?search=nvidia&repo=Any
   I think "xorg-xf86-video-nouveau" driver is best choice:
   http://root:root@tazpanel:82/pkgs.cgi?do=Install&xorg-xf86-video-nouveau
   Also with default xorg-xf86-video-fbdev you can try video=1280x1024 kernel option.

   Posted 9 years ago #
4. 

   michaelbischof
   

   offline

   Member

   Ok, when I boot from the Live-CD I see in Xorg.0.log that it seems to work with fbdev:
   22.197] (**) FBDEV(1): using shadow framebuffer
   [ 22.197] (II) Loading sub module "shadow"
   [ 22.197] (II) LoadModule: "shadow"
   [ 22.197] (II) Loading /usr/lib/X11/modules/libshadow.so
   [ 22.197] (II) Module shadow: vendor="X.Org Foundation"
   [ 22.197] compiled for 1.12.4, module version = 1.1.0
   [ 22.197] ABI class: X.Org ANSI C Emulation, version 0.4
   [ 22.197] (II) UnloadModule: "vesa"
   [ 22.197] (==) Depth 24 pixmap format is 32 bpp
   [ 22.209] (==) FBDEV(0): Backing store disabled
   [ 22.217] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument
   many error messages, then
   22.230] (II) AIGLX: Screen 0 is not DRI2 capable
   [ 22.230] (II) AIGLX: Screen 0 is not DRI capable
   [ 22.230] (EE) AIGLX error: dlopen of /usr/lib/dri/swrast_dri.so failed (/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
   [ 22.230] (EE) GLX: could not load software renderer
   [ 22.230] (II) GLX: no usable GL providers found for screen 0

   But lsmod shows me that nouveau is loaded:

   root@slitaz:~$ lsmod | grep nouveau
   nouveau 559755 2
   mxm_wmi 1019 1 nouveau
   video 9495 1 nouveau
   i2c_algo_bit 3627 1 nouveau
   ttm 36584 1 nouveau
   drm_kms_helper 17504 1 nouveau
   drm 118562 3 nouveau,ttm,drm_kms_helper
   hwmon 865 1 nouveau
   i2c_core 12294 4 nouveau,i2c_algo_bit,drm_kms_helper,drm
   button 3286 1 nouveau

   root@slitaz:~$ tazhw detected-modules

   Detected PCI and USB modules
   ================================================================================
   ohci_hcd
   ehci_hcd
   pata_amd
   sata_nv
   sata_nv
   forcedeth
   pcieport
   pcieport
   pcieport
   pcieport

   But:

   root@slitaz:~$ tazhw detect-pci

   Detected PCI devices Kernel modules
   ================================================================================
   * Builtin module : ohci_hcd
   * Builtin module : ehci_hcd
   * Builtin module : pata_amd
   * Builtin module : sata_nv
   * Builtin module : forcedeth
   * Builtin module : pcieport
   > Module in use : snd_ca0106
   > Module in use : sky2
   > Module in use : nouveau

   When I blacklist nouveau in the hard-drive install I do not get an X-screen.

   Hopefully this information is sufficient?

   Posted 9 years ago #
5. 

   michaelbischof
   

   offline

   Member

   Ok, the mistake is clear: the problem sits as usual in front of the machine! ;-)
   From Slitaz 4 I was used that I have to run the kernel command line including „nomodeset" to get a sufficient good result. If I stop this when booting the harddrive installatio I get immediately the desired resolution!
   The driver in use is nouveau!

   Thanks a lot for you help!

   Posted 9 years ago #
6. 

   mojo
   

   offline

   Key Master

   What video driver is being used when you boot the install to 1024x768?
   OK, glad you figured it out.

   Posted 9 years ago #
7. 

   michaelbischof
   

   offline

   Member

   @mojo
   Sorry, this I could not figure out. The driver nouveau had been loaded, but when the boot was done with the line including „nomodeset“ it went wrong. I was not able to interprete the contradictory results. Now it is perfect! ;-)

   Posted 9 years ago #

RSS feed for this topic

Reply

You must log in to post.