SliTaz SliTaz Forum

You are not logged in.

#1 2012-02-09 15:24:07

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

cooking nomodeset does not work

On one machine with a Nvidia GE Force 7100 GS graphic card the option ,,nomodeset" or even ,,i915.modeset=0 nomodeset" does not work. Whatever I try I cannot bring the screen up.

Detail from the /var/log/Xorg.0.lock-file:

[1655501.488] (II) VESA(0): Total Memory: 2048 64KB banks (131072kB)

[1655501.488] (II) VESA(0): Monitor0: Using hsync range of 31.50-0.00 kHz

[1655501.488] (II) VESA(0): Monitor0: Using vrefresh range of 56.00-0.00 Hz

[1655501.488] (WW) VESA(0): Unable to estimate virtual size

[1655501.488] (II) VESA(0): Not using built-in mode "1280x1024" (no mode of this name)

[1655501.488] (II) VESA(0): Not using built-in mode "1024x768" (no mode of this name)

[1655501.488] (II) VESA(0): Not using built-in mode "800x600" (no mode of this name)

[1655501.488] (II) VESA(0): Not using built-in mode "640x480" (no mode of this name)

[1655501.488] (II) VESA(0): Not using built-in mode "640x400" (no mode of this name)

[1655501.488] (II) VESA(0): Not using built-in mode "320x400" (no mode of this name)

[1655501.488] (II) VESA(0): Not using built-in mode "320x240" (no mode of this name)

[1655501.489] (II) VESA(0): Not using built-in mode "320x200" (no mode of this name)

[1655501.489] (WW) VESA(0): No valid modes left. Trying less strict filter...

[1655501.489] (II) VESA(0): Monitor0: Using hsync range of 31.50-0.00 kHz

[1655501.489] (II) VESA(0): Monitor0: Using vrefresh range of 56.00-0.00 Hz

[1655501.489] (WW) VESA(0): Unable to estimate virtual size

[1655501.489] (II) VESA(0): Not using built-in mode "1280x1024" (unknown reason)

[1655501.489] (II) VESA(0): Not using built-in mode "1024x768" (unknown reason)

[1655501.489] (II) VESA(0): Not using built-in mode "800x600" (unknown reason)

[1655501.489] (II) VESA(0): Not using built-in mode "640x480" (unknown reason)

[1655501.489] (II) VESA(0): Not using built-in mode "640x400" (unknown reason)

[1655501.489] (II) VESA(0): Not using built-in mode "320x400" (unknown reason)

[1655501.489] (II) VESA(0): Not using built-in mode "320x240" (unknown reason)

[1655501.489] (II) VESA(0): Not using built-in mode "320x200" (unknown reason)

[1655501.489] (WW) VESA(0): No valid modes left. Trying aggressive sync range...

[1655501.489] (II) VESA(0): Monitor0: Using hsync range of 31.50-0.00 kHz

[1655501.489] (II) VESA(0): Monitor0: Using vrefresh range of 50.00-0.00 Hz

[1655501.489] (WW) VESA(0): Unable to estimate virtual size

[1655501.489] (II) VESA(0): Not using built-in mode "1280x1024" (unknown reason)

[1655501.489] (II) VESA(0): Not using built-in mode "1024x768" (unknown reason)

[1655501.489] (II) VESA(0): Not using built-in mode "800x600" (unknown reason)

[1655501.489] (II) VESA(0): Not using built-in mode "640x480" (unknown reason)

[1655501.489] (II) VESA(0): Not using built-in mode "640x400" (unknown reason)

[1655501.489] (II) VESA(0): Not using built-in mode "320x400" (unknown reason)

[1655501.489] (II) VESA(0): Not using built-in mode "320x240" (unknown reason)

[1655501.489] (II) VESA(0): Not using built-in mode "320x200" (unknown reason)

[1655501.489] (EE) VESA(0): No valid modes

[1655501.489] (II) UnloadModule: "vesa"

[1655501.489] (II) UnloadModule: "int10"

[1655501.489] (II) Unloading /usr/lib/X11/modules/libint10.so

[1655501.489] (II) UnloadModule: "vbe"

[1655501.489] (II) Unloading /usr/lib/X11/modules/libvbe.so

[1655501.489] (EE) Screen(s) found, but none have a usable configuration.

[1655501.489]

Fatal server error:

[1655501.489] no screens found

[1655501.489]

Please consult the The X.Org Foundation support

     at http://wiki.x.org

for help.

[1655501.489] Please also check the log file at "/var/log/Xorg.0.log" for additional information.

[1655501.489]

Trying ,,tazpkg get-install nvidia" does not help either. Is it possible to use cooking with another kernel? May be naive, I am not a technician.

Offline

#2 2012-02-09 16:41:57

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: cooking nomodeset does not work

On an older machine with a Nvidia NV 43 GeForce 6600 it works usind the modules nvidia (and noveau is also installed) - the boot command line contains ,,nomodeset".

The kernel is 2.6.37-slitaz

Offline

#3 2012-02-09 17:32:52

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: cooking nomodeset does not work

You boot to console login prompt and have no blackscreen ?

Yes then modeset is NOT the problem at this stage.

Your log indicates that xorg was unable to autoconfigure your hardware to provide a screen.

#tazx

Choose nv

#tazhw detect-pci

#/etc/init.d/slim start

If monitor goes totally black it is the modeset problem

Hard shutdown reboot to console login as root

Boot with nomodeset

Offline

#4 2012-02-09 18:12:43

michaelbischof
Member
Registered: 2012-01-20
Posts: 536

Re: cooking nomodeset does not work

Wow, great, Mojo

it works now. And after I realized it and the screen appeared I used a ,,tazlito writeiso", copied then the new rootfs.gz to the harddrive and booted again from it with the command line

   ../bzImage root=/dev/sdb5 rw nomodeset

and immediately got the screen.

Damned, such a hard work I never had before for starting an Xscreen. How will that be done in the future. Do you have any idea?

Slitaz cooking is no stuff for Linux newbies anyway. But so difficult is no good thing on the long run.

;-) @Trixar_z, I do not blame that on Linux, you see!

In this particular case it is Nvidia who mixes this porridge. Incredible! My axiom is the following:

http://www.heise.de/open/artikel/Die-Woche-Freie-Software-gegen-die-Entmuendigung-der-Anwender-1417513.html

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]