Forcer la carte graphique en mode VESA

More
29 Mar 2015 18:37 #57274 by telson
telson created the topic: Forcer la carte graphique en mode VESA
Bonjour,

J'essaie depuis pas mal de temps à passer ma carte graphique en mode vesa.

En essayant de mofifier le fichier grub.cfg pour ajouter : nomodeset xforcevesa dans la ligne : linux /boot/.... ro quiet splash .......

Seulement voilà, lorsque j'ouvre un terminal en administrateur, je tape la commande suivante : sudo vi /boot/grub/grub.cfg

(Le contenu du fichier grub.cfg apparaît mais aucune possibilité de le modifier ?? Message W10: Warning: Changing a readonly file
E325: ATTENTION


Bon.....Quelqu'un pourraît t'il m'aider s'il vous plaît.

Merci par avance.

J'utilise LinuxCNC 2.6 (Debian Wheezy LinuxCNC), source : www.linuxcnc.org/index.php/english/download
More
30 Mar 2015 06:46 #57297 by andypugh
andypugh replied the topic: Forcer la carte graphique en mode VESA
More
30 Mar 2015 15:30 - 30 Mar 2015 15:39 #57308 by ArcEye
ArcEye replied the topic: Forcer la carte graphique en mode VESA
Hi

Regards the specific question,
open a terminal
$ sudo chmod 644 /boot/grub/grub.cfg
$ sudo gedit /boot/grub/grub.cfg
and you should be able to edit the file. It will however be overwritten the next time grub is updated.

If you are using a computer capable of running Wheezy, there should be no need to use Vesa drivers.

They are ancient and have very limited resolution modes
The only use really is with an old CRT monitor, but you can buy a second hand 14" LCD for £10. ( I bought a 19" for £10 locally)

What card or video chipset do you have?

Anything nvidia based can use nouveau and anything Intel based can use i9xx drivers

The important question is probably 'why do you want to use Vesa drivers'?

If is because you have read about improving latency by using them, there are probably much better ways.

regards
Last Edit: 30 Mar 2015 15:39 by ArcEye.
More
07 Apr 2015 13:49 #57598 by telson
telson replied the topic: Forcer la carte graphique en mode VESA
thanks for all your answers.

I'll check this different informations and i come back

Regards
More
16 Apr 2015 15:59 #57832 by telson
telson replied the topic: Forcer la carte graphique en mode VESA
if i follow the link WiKi and i do

CTRL + ALT + F1
i give my login ....
i give my password

I've got :

Last login : ........... CEST 2015 on tty1
Linux debian 3.4-9-rtai-686-pae #1 SMP PREEMPT Debian 3.4.55-4linuxcnc i686

the programs included .......blablabla......, to the extent permitted by apllicable law

so i see on the screen : myuser@debian:~$

and with this : sudo service gdm stop

I've got :

gdm unrecognized service


My card or video : ATI RADEON XPRESS 200 Series inside the motherboard.

Latency max 27000.

with : sudo gedit /boot/grub/grub.cfg

I've got : gedit unrecognized service

.......................HiHaaaaaaaaaaaaaaaaaaaaaaa !!!!

Thanks for help ......
More
16 Apr 2015 17:55 #57833 by ArcEye
ArcEye replied the topic: Forcer la carte graphique en mode VESA

telson wrote: if i follow the link WiKi
................
Linux debian 3.4-9-rtai-686-pae #1 SMP PREEMPT Debian 3.4.55-4linuxcnc i686


The wiki is written for Ubuntu 10.04

and with this : sudo service gdm stop
I've got :
gdm unrecognized service


It doesn't use gdm

with : sudo gedit /boot/grub/grub.cfg
I've got : gedit unrecognized service


gedit is a graphical editor, you were in terminal text mode

My card or video : ATI RADEON XPRESS 200 Series inside the motherboard.


wiki.debian.org/AtiHowTo

regards
More
17 Apr 2015 04:42 #57853 by telson
telson replied the topic: Forcer la carte graphique en mode VESA
I don't understand why the part Download Information of LinuxCNC 2.6 it's for install of LinuxCNC 2.6 is to use the Debian Wheezy LinuxCNC image

But the wiki is written for Ubuntu 10.04 :angry: :huh:

so much informations, so much web site on it, so much version, so much command......We are lost ............

So ....try will read the informations on link wiki.debian.org/AtiHowTo again 2457891 pages to read .................... :S :S
More
17 Apr 2015 14:47 #57856 by ArcEye
ArcEye replied the topic: Forcer la carte graphique en mode VESA

so much informations, so much web site on it, so much version, so much command......We are lost ............


The main problem to assisting you, is that you questions have been about what you have decided the solution is, without ever telling us what the problem is.

The opensource ATI drivers would probably have been used when you did your install.

If your problem is that max jitter on the base thread is 27K, that might be to do with video.

However it might be you are running on an inherently unsuitable computer and will never achieve anything better.
Or it could be something else, we cannot tell.

regards
More
18 Apr 2015 03:17 - 18 Apr 2015 03:29 #57873 by telson
telson replied the topic: Forcer la carte graphique en mode VESA
Yes,

My Max jitter was 50 000

So after changed bios is decrease to 27 000

So for decrease again this value, i would like mod in first the file grub.cfg and after the file Xorg.conf

I do :


CTRL + ALT + F1
I give my login
I give my password

I've got on the screen :

Last login : ........... CEST 2015 on tty1
Linux debian 3.4-9-rtai-686-pae #1 SMP PREEMPT Debian 3.4.55-4linuxcnc i686

the programs included .......blablabla......, to the extent permitted by apllicable law

On sreeen i see : mylogindebian:~$

I try to the command : sudo service gdm stop

But - -> gdm unrecognized service

Apparently with debian wheezy the command gdm : doesn't word

So I try with : sudo service lightdm stop

And it's was a good solution

but when i try : sudo Xorg -configure --> number of created screens does not match number of detected devices. configuration failes. Server terminated with error (2). Closing log file.

Well......................
Last Edit: 18 Apr 2015 03:29 by telson.
More
23 Apr 2015 14:27 #58031 by telson
telson replied the topic: Forcer la carte graphique en mode VESA
Re revoici avec des nouvelles :

Lorsque je crée un fichier : xorg.conf et que je remplace dans la section "Device" : Driver "radeon" par Driver "vesa", au redémarrage j'ai un écran noir avec un petit curseur blanc et c'est tout!!!!

ça marche pas en fait.

voici mon fichier modifié :

Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
Screen 2 "Screen2" RightOf "Screen1"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
FontPath "built-ins"
EndSection

Section "Module"
Load "dri2"
Load "record"
Load "dri"
Load "dbe"
Load "extmod"
Load "glx"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection

Section "Monitor"
Identifier "Monitor1"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection

Section "Monitor"
Identifier "Monitor2"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection

Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "SWcursor" # [<bool>]
#Option "Dac6Bit" # [<bool>]
#Option "Dac8Bit" # [<bool>]
#Option "BusType" # [<str>]
#Option "CPPIOMode" # [<bool>]
#Option "CPusecTimeout" # <i>
#Option "AGPMode" # <i>
#Option "AGPFastWrite" # [<bool>]
#Option "AGPSize" # <i>
#Option "GARTSize" # <i>
#Option "RingSize" # <i>
#Option "BufferSize" # <i>
#Option "EnableDepthMoves" # [<bool>]
#Option "EnablePageFlip" # [<bool>]
#Option "NoBackBuffer" # [<bool>]
#Option "DMAForXv" # [<bool>]
#Option "FBTexPercent" # <i>
#Option "DepthBits" # <i>
#Option "PCIAPERSize" # <i>
#Option "AccelDFS" # [<bool>]
#Option "IgnoreEDID" # [<bool>]
#Option "CustomEDID" # [<str>]
#Option "DisplayPriority" # [<str>]
#Option "PanelSize" # [<str>]
#Option "ForceMinDotClock" # <freq>
#Option "ColorTiling" # [<bool>]
#Option "VideoKey" # <i>
#Option "RageTheatreCrystal" # <i>
#Option "RageTheatreTunerPort" # <i>
#Option "RageTheatreCompositePort" # <i>
#Option "RageTheatreSVideoPort" # <i>
#Option "TunerType" # <i>
#Option "RageTheatreMicrocPath" # <str>
#Option "RageTheatreMicrocType" # <str>
#Option "ScalerWidth" # <i>
#Option "RenderAccel" # [<bool>]
#Option "SubPixelOrder" # [<str>]
#Option "ClockGating" # [<bool>]
#Option "VGAAccess" # [<bool>]
#Option "ReverseDDC" # [<bool>]
#Option "LVDSProbePLL" # [<bool>]
#Option "AccelMethod" # <str>
#Option "DRI" # [<bool>]
#Option "ConnectorTable" # <str>
#Option "DefaultConnectorTable" # [<bool>]
#Option "DefaultTMDSPLL" # [<bool>]
#Option "TVDACLoadDetect" # [<bool>]
#Option "ForceTVOut" # [<bool>]
#Option "TVStandard" # <str>
#Option "IgnoreLidStatus" # [<bool>]
#Option "DefaultTVDACAdj" # [<bool>]
#Option "Int10" # [<bool>]
#Option "EXAVSync" # [<bool>]
#Option "ATOMTVOut" # [<bool>]
#Option "R4xxATOM" # [<bool>]
#Option "ForceLowPowerMode" # [<bool>]
#Option "DynamicPM" # [<bool>]
#Option "NewPLL" # [<bool>]
#Option "ZaphodHeads" # <str>
Identifier "Card0"
Driver "vesa" ici avant il y avait "radeon"
BusID "PCI:1:5:0"
EndSection

Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "Rotate" # <str>
#Option "fbdev" # <str>
#Option "debug" # [<bool>]
Identifier "Card1"
Driver "vesa" ici avant il y avait "fbdev"
BusID "PCI:1:5:0"
EndSection

Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "DefaultRefresh" # [<bool>]
#Option "ModeSetClearScreen" # [<bool>]
Identifier "Card2"
Driver "vesa" # aucun changement effectué ici
BusID "PCI:1:5:0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "Screen"
Identifier "Screen1"
Device "Card1"
Monitor "Monitor1"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "Screen"
Identifier "Screen2"
Device "Card2"
Monitor "Monitor2"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Est ce normal d'avoir 3 Section "Monitor"

Est ce normal d'avoir 3 Section "Device"
Moderators: darty367
Time to create page: 0.092 seconds
Powered by Kunena Forum