Reporting a failure in the gnumeric.tcz and open-vm-tools.tcz extensions

[marcelocripe]

Your error probably occurred because you are using Xvesa and gnumeric requires Xorg-7.7 or Xorg-7.7-3d

..please use copy and paste in future rather than obliging users who want to help to download twelve png files...

Hi Juanito,

After a long time I was able to understand what you wrote.

I deleted xvesa.tcz from the startup file (onboot.lst) and included xorg-7.7.tcz at the end of the list, saved the onboot.lst file and backed up the settings before restarting Tiny Core Plus 11.1 32 bits.

After restarting the computer I noticed the Tiny Core Plus 11.1 slow, taking a long time to respond to a simple click on the desktop. Using Apps: Regular Applications I loaded gnumeric.tcz and the icon was displayed in the menu, with a click on the icon the program opened and worked.

It is not feasible to remove xvesa.tcz, it is a controller of the video settings, is it not?

Would there be another option for a spreadsheet processor program similar to gnumeric.tcz available for Tiny Core Plus 11.1 other than libreoffice.tcz?

I would like to take the opportunity to ask:

When I'm using gnumeric.tcz, or abword.tcz, or libreoffice.tcz, or inkscap.tcz on Tiny Core Plus 11.1 and I need to save the file, the options window that appears appears with a resolution that is out of proportion to the size of the configured resolution on the video card, can this be fixed?

It is difficult until you choose the format of the file to be saved and the save button is not visible.

For now, I conclude that gnumeric.tcz is not feasible to be used in Tiny Core Plus 11.1, could it be corrected with a new build of this extension?

Thankful.

marcelocripe

Original text in Portuguese, translated into English by the Google translator.

------------

Olá Juanito,

Depois de muito tempo eu consegui compreender o que você escreveu.

Eu deletei do arquivo inicialização (onboot.lst) o xvesa.tcz e incluí no final da lista o xorg-7.7.tcz, salvei o arquivo onboot.lst e fiz backup das configurações antes de reiniciar o Tiny Core Plus 11.1 32 bits.

Após reiniciar o computador eu percebi o Tiny Core Plus 11.1 lento, demorando para responder um simples clique na área de trabalho. Utilizando o Apps: Regular Applications carreguei o gnumeric.tcz e o ícone foi exibido no menu, com um clique no ícone o programa abriu e funcionou.

Não é viável remover o xvesa.tcz, ele é um controlador das configurações de vídeo, não é verdade?

Teria outra opção de um programa processador de planilhas de cálculos semelhante ao gnumeric.tcz disponível para o Tiny Core Plus 11.1 que não fosse o libreoffice.tcz?

Eu gostaria de aproveitar de perguntar:

Quando estou utilizando o gnumeric.tcz, ou abword.tcz, ou libreoffice.tcz, ou inkscap.tcz no Tiny Core Plus 11.1 e preciso salvar o arquivo, a janela de opções que é exibida surge com uma resolução desproporcional ao tamanho da resolução configurada na placa de vídeo, isso pode ser corrigido?

Fica difícil até escolher o formato do arquivo a ser salvo e o botão para salvar não fica visível.

Por enquanto, chego a conclusão de que o gnumeric.tcz não é viável para ser utilizado no Tiny Core Plus 11.1, será que poderia ser corrigido com uma nova compilação desta extensão?

Grato.

marcelocripe

Texto original em português, traduzido para inglês pelo tradutor do Google.         

[Juanito]

I deleted xvesa.tcz from the startup file (onboot.lst) and included xorg-7.7.tcz at the end of the list, saved the onboot.lst file and backed up the settings before restarting Tiny Core Plus 11.1 32 bits.

After restarting the computer I noticed the Tiny Core Plus 11.1 slow, taking a long time to respond to a simple click on the desktop. Using Apps: Regular Applications I loaded gnumeric.tcz and the icon was displayed in the menu, with a click on the icon the program opened and worked.

It is not feasible to remove xvesa.tcz, it is a controller of the video settings, is it not?

Tinycore has four choices for X servers:

Xvesa - small, lightweight - will not work with all gui applications
Xfbdev - small, lightweight - will not work with all gui applications
Xorg-7.7 - large, full featured - will work with most gui applications
Xorg-7.7-3d - large, full featured with software and hardware acceleration - should work with all gui applications

You can only have one X server set "onboot" and you should not have any X servers set "ondemand".

Unless you have a very old machine, using Xorg-7.7 should not slow your machine down by a large amount as compared to Xvesa or Xfbdev.

When I'm using gnumeric.tcz, or abword.tcz, or libreoffice.tcz, or inkscap.tcz on Tiny Core Plus 11.1 and I need to save the file, the options window that appears appears with a resolution that is out of proportion to the size of the configured resolution on the video card, can this be fixed?

It is difficult until you choose the format of the file to be saved and the save button is not visible.

This has been a fault of gtk3 for a long time - on typical laptop landscape screens the bottom of the file open/save dialogue box disappears off the bottom of the screen. I have an old nearly square monitor and the same thing does not happen.

For now, I conclude that gnumeric.tcz is not feasible to be used in Tiny Core Plus 11.1, could it be corrected with a new build of this extension?

The gtk3 developers have not thought this needs fixing for years, I'm not sure they are going to change their minds...

..but you can do something like this:

Code: [Select]

$ gsettings set org.gtk.Settings.FileChooser window-size '(400,200)'..and then close and re-open gnumeric.

[nick65go]

May I provide my feed-back?Using real laptop, not virtual machines, and only FLWM/FLTK base. All the programs like abiword, gnumeric, libreoffice, work very well. I mean the opens/save dialog windows have adjustable size (length/wide).I had problems in virtual machine (Virtual-box on Win10) because of the improper video driver resolution. But even that resolution can be cheated with some lines in the VM machine configuration.  (Otherwise Virtual-box is limiting to 800x600 for my 1600x900 display.)
FYI: the tricky lines in VM config are NOT possible from menus. But reading the help they can be manually inserted in TXT config of VM machine.

[marcelocripe]

I deleted xvesa.tcz from the startup file (onboot.lst) and included xorg-7.7.tcz at the end of the list, saved the onboot.lst file and backed up the settings before restarting Tiny Core Plus 11.1 32 bits.

After restarting the computer I noticed the Tiny Core Plus 11.1 slow, taking a long time to respond to a simple click on the desktop. Using Apps: Regular Applications I loaded gnumeric.tcz and the icon was displayed in the menu, with a click on the icon the program opened and worked.

It is not feasible to remove xvesa.tcz, it is a controller of the video settings, is it not?

Tinycore has four choices for X servers:

Xvesa - small, lightweight - will not work with all gui applications
Xfbdev - small, lightweight - will not work with all gui applications
Xorg-7.7 - large, full featured - will work with most gui applications
Xorg-7.7-3d - large, full featured with software and hardware acceleration - should work with all gui applications

You can only have one X server set "onboot" and you should not have any X servers set "ondemand".

Unless you have a very old machine, using Xorg-7.7 should not slow your machine down by a large amount as compared to Xvesa or Xfbdev.

When I'm using gnumeric.tcz, or abword.tcz, or libreoffice.tcz, or inkscap.tcz on Tiny Core Plus 11.1 and I need to save the file, the options window that appears appears with a resolution that is out of proportion to the size of the configured resolution on the video card, can this be fixed?

It is difficult until you choose the format of the file to be saved and the save button is not visible.

This has been a fault of gtk3 for a long time - on typical laptop landscape screens the bottom of the file open/save dialogue box disappears off the bottom of the screen. I have an old nearly square monitor and the same thing does not happen.

For now, I conclude that gnumeric.tcz is not feasible to be used in Tiny Core Plus 11.1, could it be corrected with a new build of this extension?

The gtk3 developers have not thought this needs fixing for years, I'm not sure they are going to change their minds...

..but you can do something like this:

Code: [Select]

$ gsettings set org.gtk.Settings.FileChooser window-size '(400,200)'..and then close and re-open gnumeric.

Hi Juanito,

Could you please teach me how to set the video resolution using Xorg-7.7.tcz and Xorg-7.7-3d.tcz.

This will help me to solve another problem about the flowblade.tcz video editor, related to the posting of the link: http://forum.tinycorelinux.net/index.php/topic,22778.msg148756.html#msg148756.

The flowblade.tcz video editor needs 1152x768 video card resolution to open, however on Xvesa.tcz the maximum resolution is 1024x768. I know that the video card and monitor support resolutions greater than 1152x768.

Thankful.
marcelocripe

Original text in Brazilian Portuguese, translation into English by Google Translate.

---------------

Olá Juanito,

Por favor poderia me ensinar a configurar a resolução do vídeo usando Xorg-7.7.tcz e o Xorg-7.7-3d.tcz.

Isso me ajudará a resolver outro problema sobre o editor de vídeo flowblade.tcz, referente a postagem do link: http://forum.tinycorelinux.net/index.php/topic,22778.msg148756.html#msg148756.

O editor de vídeo flowblade.tcz necessita de resolução da placa de vídeo 1152x768 para abrir,  contudo no Xvesa.tcz a resolução máxima é de 1024x768. Eu sei que a placa de vídeo e o monitor suportam resoluções maiores que 1152x768.

Grato.
marcelocripe

Texto original em português do Brasil, tradução para o inglês por Google Tradutor.

[Juanito]

Usually Xorg-7.7 or Xorg-7.7-3d will use the native (default) resolution of your display automatically.

Try using Xorg-7.7 or Xorg-7.7-3d without any configuration to see what happens.

It would be useful to look at the file /var/log/Xorg.0.log and check for text that looks like the following and paste it here:

Code: [Select]

[   121.037] (==) Matched intel as autoconfigured driver 0
[   121.037] (==) Matched modesetting as autoconfigured driver 1
[   121.037] (==) Matched fbdev as autoconfigured driver 2
[   121.037] (==) Matched vesa as autoconfigured driver 3
...
[   121.187] (II) intel(0): switch to mode 1366x768@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
[   121.197] (II) intel(0): Setting screen physical size to 361 x 203

[marcelocripe]

Usually Xorg-7.7 or Xorg-7.7-3d will use the native (default) resolution of your display automatically.

Try using Xorg-7.7 or Xorg-7.7-3d without any configuration to see what happens.

It would be useful to look at the file /var/log/Xorg.0.log and check for text that looks like the following and paste it here:

Code: [Select]

[   121.037] (==) Matched intel as autoconfigured driver 0
[   121.037] (==) Matched modesetting as autoconfigured driver 1
[   121.037] (==) Matched fbdev as autoconfigured driver 2
[   121.037] (==) Matched vesa as autoconfigured driver 3
...
[   121.187] (II) intel(0): switch to mode 1366x768@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
[   121.197] (II) intel(0): Setting screen physical size to 361 x 203

Hello Juanito.
Follow the excerpt from the "Xorg.0.log" file, using Xorg-7.7.tcz

-----------------

Olá Juanito.
Segue o trecho do conteúdo do arquivo "Xorg.0.log", usando o Xorg-7.7.tcz.

Code: [Select]

[    73.447] (II) VESA(0): Total Memory: 127 64KB banks (8128kB)
[    73.447] (II) VESA(0): <default monitor>: Using hsync value of 48.26 kHz
[    73.447] (II) VESA(0): <default monitor>: Using vrefresh value of 60.10 Hz
[    73.447] (WW) VESA(0): Unable to estimate virtual size
[    73.447] (II) VESA(0): Not using built-in mode "1024x768" (no mode of this name)
[    73.447] (II) VESA(0): Not using built-in mode "800x600" (no mode of this name)
[    73.447] (II) VESA(0): Not using built-in mode "640x480" (no mode of this name)
[    73.447] (WW) VESA(0): No valid modes left. Trying less strict filter...
[    73.447] (II) VESA(0): <default monitor>: Using hsync value of 48.26 kHz
[    73.447] (II) VESA(0): <default monitor>: Using vrefresh value of 60.10 Hz
[    73.447] (WW) VESA(0): Unable to estimate virtual size
[    73.447] (II) VESA(0): Not using built-in mode "800x600" (hsync out of range)
[    73.447] (II) VESA(0): Not using built-in mode "640x480" (hsync out of range)
[    73.447] (II) VESA(0): Virtual size is 1024x768 (pitch 1024)
[    73.447] (**) VESA(0): *Built-in mode "1024x768"
[    73.447] (**) VESA(0): Display dimensions: (310, 170) mm
[    73.447] (**) VESA(0): DPI set to (83, 114)
[    73.447] (**) VESA(0): Using "Shadow Framebuffer"
[    73.447] (II) Loading sub module "shadow"
[    73.447] (II) LoadModule: "shadow"
[    73.448] (II) Loading /usr/local/lib/xorg/modules/libshadow.so
[    73.449] (II) Module shadow: vendor="X.Org Foundation"
[    73.449] compiled for 1.20.6, module version = 1.1.0
[    73.449] ABI class: X.Org ANSI C Emulation, version 0.4
[    73.449] (II) Loading sub module "fb"
[    73.449] (II) LoadModule: "fb"
[    73.450] (II) Loading /usr/local/lib/xorg/modules/libfb.so
[    73.454] (II) Module fb: vendor="X.Org Foundation"
[    73.454] compiled for 1.20.6, module version = 1.0.0
[    73.454] ABI class: X.Org ANSI C Emulation, version 0.4
[    73.455] (II) Loading sub module "int10"
[    73.455] (II) LoadModule: "int10"
[    73.455] (II) Loading /usr/local/lib/xorg/modules/libint10.so
[    73.455] (II) Module int10: vendor="X.Org Foundation"
[    73.455] compiled for 1.20.6, module version = 1.0.0
[    73.455] ABI class: X.Org Video Driver, version 24.0
[    73.455] (II) VESA(0): initializing int10
[    73.456] (II) VESA(0): Bad V_BIOS checksum
[    73.456] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[    73.456] (II) VESA(0): VESA BIOS detected
[    73.456] (II) VESA(0): VESA VBE Version 3.0
[    73.456] (II) VESA(0): VESA VBE Total Mem: 8128 kB
[    73.456] (II) VESA(0): VESA VBE OEM: Intel(r)PineView Graphics Chip Accelerated VGA BIOS
[    73.456] (II) VESA(0): VESA VBE OEM Software Rev: 1.0
[    73.456] (II) VESA(0): VESA VBE OEM Vendor: Intel Corporation
[    73.456] (II) VESA(0): VESA VBE OEM Product: Intel(r)PineView Graphics Controller
[    73.457] (II) VESA(0): VESA VBE OEM Product Rev: Hardware Version 0.0
[    73.457] (II) VESA(0): virtual address = 0xb6dca000, VGAbase = 0xb6dba000
physical address = 0xd0000000, size = 8323072
[    73.474] (II) VESA(0): Setting up VESA Mode 0x118 (1024x768)
    [EDIT]: Added code tags.  Rich

[marcelocripe]

Using Xorg-7.7-3d.tcz

---------------

Usando o Xorg-7.7-3d.tcz

Code: [Select]

[    79.105] (II) VESA(0): Total Memory: 127 64KB banks (8128kB)
[    79.105] (II) VESA(0): <default monitor>: Using hsync value of 48.26 kHz
[    79.105] (II) VESA(0): <default monitor>: Using vrefresh value of 60.10 Hz
[    79.106] (WW) VESA(0): Unable to estimate virtual size
[    79.106] (II) VESA(0): Not using built-in mode "1024x768" (no mode of this name)
[    79.106] (II) VESA(0): Not using built-in mode "800x600" (no mode of this name)
[    79.106] (II) VESA(0): Not using built-in mode "640x480" (no mode of this name)
[    79.106] (WW) VESA(0): No valid modes left. Trying less strict filter...
[    79.106] (II) VESA(0): <default monitor>: Using hsync value of 48.26 kHz
[    79.106] (II) VESA(0): <default monitor>: Using vrefresh value of 60.10 Hz
[    79.106] (WW) VESA(0): Unable to estimate virtual size
[    79.106] (II) VESA(0): Not using built-in mode "800x600" (hsync out of range)
[    79.106] (II) VESA(0): Not using built-in mode "640x480" (hsync out of range)
[    79.106] (II) VESA(0): Virtual size is 1024x768 (pitch 1024)
[    79.106] (**) VESA(0): *Built-in mode "1024x768"
[    79.106] (**) VESA(0): Display dimensions: (310, 170) mm
[    79.106] (**) VESA(0): DPI set to (83, 114)
[    79.106] (**) VESA(0): Using "Shadow Framebuffer"
[    79.106] (II) Loading sub module "shadow"
[    79.106] (II) LoadModule: "shadow"
[    79.106] (II) Loading /usr/local/lib/xorg/modules/libshadow.so
[    79.108] (II) Module shadow: vendor="X.Org Foundation"
[    79.108] compiled for 1.20.6, module version = 1.1.0
[    79.108] ABI class: X.Org ANSI C Emulation, version 0.4
[    79.108] (II) Loading sub module "fb"
[    79.108] (II) LoadModule: "fb"
[    79.108] (II) Loading /usr/local/lib/xorg/modules/libfb.so
[    79.113] (II) Module fb: vendor="X.Org Foundation"
[    79.113] compiled for 1.20.6, module version = 1.0.0
[    79.113] ABI class: X.Org ANSI C Emulation, version 0.4
[    79.114] (II) Loading sub module "int10"
[    79.114] (II) LoadModule: "int10"
[    79.114] (II) Loading /usr/local/lib/xorg/modules/libint10.so
[    79.114] (II) Module int10: vendor="X.Org Foundation"
[    79.114] compiled for 1.20.6, module version = 1.0.0
[    79.114] ABI class: X.Org Video Driver, version 24.0
[    79.114] (II) VESA(0): initializing int10
[    79.115] (II) VESA(0): Bad V_BIOS checksum
[    79.115] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[    79.115] (II) VESA(0): VESA BIOS detected
[    79.115] (II) VESA(0): VESA VBE Version 3.0
[    79.115] (II) VESA(0): VESA VBE Total Mem: 8128 kB
[    79.115] (II) VESA(0): VESA VBE OEM: Intel(r)PineView Graphics Chip Accelerated VGA BIOS
[    79.115] (II) VESA(0): VESA VBE OEM Software Rev: 1.0
[    79.115] (II) VESA(0): VESA VBE OEM Vendor: Intel Corporation
[    79.115] (II) VESA(0): VESA VBE OEM Product: Intel(r)PineView Graphics Controller
[    79.115] (II) VESA(0): VESA VBE OEM Product Rev: Hardware Version 0.0
[    79.116] (II) VESA(0): virtual address = 0xb6cf8000, VGAbase = 0xb6ce8000
physical address = 0xd0000000, size = 8323072
[    79.133] (II) VESA(0): Setting up VESA Mode 0x118 (1024x768)
[    79.231] (==) VESA(0): Default visual is TrueColor
[    80.565] (==) VESA(0): Backing store enabled

Will this post solution work for the other link post: http://forum.tinycorelinux.net/index.php/topic,22778.msg148756.html#msg148756, about changing the video card resolution so that the editor can open at 1152 x 768.

Thankful.
marcelocripe

Original text in Brazilian Portuguese, translation into English by Google Translate.

------------

A solução dessa postagem servirá para a outra postagem do link: http://forum.tinycorelinux.net/index.php/topic,22778.msg148756.html#msg148756, sobre como alterar a resolução da placa de vídeo para o editor poder abrir em 1152 x 768.

Grato.
marcelocripe

Texto original em português do Brasil, tradução para o inglês por Google Tradutor.

[Juanito]

You forgot the most important part:

Code: [Select]

[   121.037] (==) Matched intel as autoconfigured driver 0
[   121.037] (==) Matched modesetting as autoconfigured driver 1
[   121.037] (==) Matched fbdev as autoconfigured driver 2
[   121.037] (==) Matched vesa as autoconfigured driver 3
Xorg has not found a driver for your hardware and is using the fall-back vesa driver - we need to know what graphics hardware driver Xorg is looking for.

Please post the section from your Xorg.0.log analogous to the section posted above.

[curaga]

"Intel Pineview" - you need to install xf86-video-intel. And possibly graphics-, not sure if it's a dep.

[Juanito]

Loading xf86-video-intel will load graphics-KERNEL so be sure to exit the gui before loading it.

[marcelocripe]

Hi Juanito,

I hope I copied correct characters.
Espero ter copiado os caracteres corretos.

Code: [Select]

[    74.860] Current version of pixman: 0.38.4
[    74.860] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[    74.860] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    74.860] (==) Log file: "/var/log/Xorg.0.log", Time: Wed May 20 17:25:46 2020
[    74.860] (==) Using system config directory "/usr/local/share/X11/xorg.conf.d"
[    74.861] (==) No Layout section.  Using the first Screen section.
[    74.861] (==) No screen section available. Using defaults.
[    74.861] (**) |-->Screen "Default Screen Section" (0)
[    74.861] (**) |   |-->Monitor "<default monitor>"
[    74.866] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[    74.866] (==) Automatically adding devices
[    74.866] (==) Automatically enabling devices
[    74.866] (==) Automatically adding GPU devices
[    74.866] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    74.866] (WW) The directory "/usr/local/lib/X11/fonts/OTF/" does not exist.
[    74.866] Entry deleted from font path.
[    74.866] (WW) The directory "/usr/local/lib/X11/fonts/100dpi/" does not exist.
[    74.866] Entry deleted from font path.
[    74.866] (==) FontPath set to:
/usr/local/lib/X11/fonts/misc/,
/usr/local/lib/X11/fonts/TTF/,
/usr/local/lib/X11/fonts/Type1/,
/usr/local/lib/X11/fonts/75dpi/
[    74.866] (==) ModulePath set to "/usr/local/lib/xorg/modules"
[    74.866] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[    74.866] (II) Loader magic: 0x81e2b20
[    74.866] (II) Module ABI versions:
[    74.867] X.Org ANSI C Emulation: 0.4
[    74.867] X.Org Video Driver: 24.0
[    74.867] X.Org XInput driver : 24.1
[    74.867] X.Org Server Extension : 10.0
[    74.879] (--) PCI:*(0@0:2:0) 8086:a001:1297:2001 rev 2, Mem @ 0xfe980000/524288, 0xd0000000/268435456, 0xfe800000/1048576, I/O @ 0x0000cc00/8, BIOS @ 0x????????/131072
[    74.879] (--) PCI: (0@0:2:1) 8086:a002:1297:2001 rev 2, Mem @ 0xfe780000/524288
[    74.879] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[    74.879] (II) LoadModule: "glx"
[    74.879] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so
[    74.894] (II) Module glx: vendor="X.Org Foundation"
[    74.894] compiled for 1.20.6, module version = 1.0.0
[    74.894] ABI class: X.Org Server Extension, version 10.0
[    74.894] (==) Matched intel as autoconfigured driver 0
[    74.894] (==) Matched modesetting as autoconfigured driver 1
[    74.894] (==) Matched fbdev as autoconfigured driver 2
[    74.894] (==) Matched vesa as autoconfigured driver 3
[    74.894] (==) Assigned the driver to the xf86ConfigLayout
[    74.894] (II) LoadModule: "intel"
[    74.895] (WW) Warning, couldn't open module intel
[    74.895] (EE) Failed to load module "intel" (module does not exist, 0)
[    74.895] (II) LoadModule: "modesetting"
[    74.895] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so
[    74.900] (II) Module modesetting: vendor="X.Org Foundation"
[    74.900] compiled for 1.20.6, module version = 1.20.6
[    74.900] Module class: X.Org Video Driver
[    74.900] ABI class: X.Org Video Driver, version 24.0
[    74.900] (II) LoadModule: "fbdev"
[    74.901] (WW) Warning, couldn't open module fbdev
[    74.901] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    74.901] (II) LoadModule: "vesa"
[    74.901] (II) Loading /usr/local/lib/xorg/modules/drivers/vesa_drv.so
[    74.902] (II) Module vesa: vendor="X.Org Foundation"
[    74.902] compiled for 1.20.0, module version = 2.4.0
[    74.902] Module class: X.Org Video Driver
[    74.902] ABI class: X.Org Video Driver, version 24.0
[    74.902] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    74.903] (II) VESA: driver for VESA chipsets: vesa
[    74.903] (--) using VT number 2

[    74.907] (EE) open /dev/dri/card0: No such file or directory
[    74.907] (WW) Falling back to old probe method for modesetting
[    74.907] (EE) open /dev/dri/card0: No such file or directory
[    74.908] (EE) Screen 0 deleted because of no matching config section.
[    74.908] (II) UnloadModule: "modesetting"
[    74.908] (II) Loading sub module "vbe"
[    74.908] (II) LoadModule: "vbe"
[    74.908] (II) Loading /usr/local/lib/xorg/modules/libvbe.so
[    74.910] (II) Module vbe: vendor="X.Org Foundation"
[    74.910] compiled for 1.20.6, module version = 1.1.0
[    74.910] ABI class: X.Org Video Driver, version 24.0
[    74.910] (II) Loading sub module "int10"
[    74.910] (II) LoadModule: "int10"
[    74.910] (II) Loading /usr/local/lib/xorg/modules/libint10.so
[    74.924] (II) Module int10: vendor="X.Org Foundation"
[    74.924] compiled for 1.20.6, module version = 1.0.0
[    74.924] ABI class: X.Org Video Driver, version 24.0
[    74.925] (II) VESA(0): initializing int10
[    74.926] (II) VESA(0): Bad V_BIOS checksum
[    74.926] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[    74.927] (II) VESA(0): VESA BIOS detected
[    74.927] (II) VESA(0): VESA VBE Version 3.0
[    74.927] (II) VESA(0): VESA VBE Total Mem: 8128 kB
[    74.927] (II) VESA(0): VESA VBE OEM: Intel(r)PineView Graphics Chip Accelerated VGA BIOS
[    74.927] (II) VESA(0): VESA VBE OEM Software Rev: 1.0
[    74.927] (II) VESA(0): VESA VBE OEM Vendor: Intel Corporation
[    74.927] (II) VESA(0): VESA VBE OEM Product: Intel(r)PineView Graphics Controller
[    74.927] (II) VESA(0): VESA VBE OEM Product Rev: Hardware Version 0.0
[    74.952] (II) VESA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[    74.952] (==) VESA(0): Depth 24, (--) framebuffer bpp 32
[    74.952] (==) VESA(0): RGB weight 888
[    74.952] (==) VESA(0): Default visual is TrueColor
[    74.952] (==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
[    74.952] (II) Loading sub module "ddc"
[    74.952] (II) LoadModule: "ddc"
[    74.952] (II) Module "ddc" already built-in
[    74.952] (II) VESA(0): VESA VBE DDC supported
[    74.952] (II) VESA(0): VESA VBE DDC Level 2
[    74.952] (II) VESA(0): VESA VBE DDC transfer in appr. 1 sec.
[    74.955] (II) VESA(0): VESA VBE DDC read successfully
[    74.955] (II) VESA(0): Manufacturer: AUO  Model: 193c  Serial#: 0
[    74.955] (II) VESA(0): Year: 2009  Week: 1
[    74.955] (II) VESA(0): EDID Version: 1.3
[    74.955] (II) VESA(0): Digital Display Input
[    74.955] (II) VESA(0): Max Image Size [cm]: horiz.: 31  vert.: 17
[    74.955] (II) VESA(0): Gamma: 2.20
[    74.955] (II) VESA(0): No DPMS capabilities specified
[    74.955] (II) VESA(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[    74.955] (II) VESA(0): First detailed timing is preferred mode
[    74.955] (II) VESA(0): redX: 0.620 redY: 0.340   greenX: 0.330 greenY: 0.570
[    74.955] (II) VESA(0): blueX: 0.150 blueY: 0.600   whiteX: 0.313 whiteY: 0.329
[    74.955] (II) VESA(0): Manufacturer's mask: 0
[    74.955] (II) VESA(0): Supported detailed timing:
[    74.956] (II) VESA(0): clock: 69.3 MHz   Image Size:  309 x 173 mm
[    74.956] (II) VESA(0): h_active: 1366  h_sync: 1404  h_sync_end 1426 h_blank_end 1436 h_border: 0
[    74.956] (II) VESA(0): v_active: 768  v_sync: 771  v_sync_end 777 v_blanking: 803 v_border: 0
[    74.956] (II) VESA(0): Unknown vendor-specific block f
[    74.956] (II) VESA(0):  AUO
[    74.956] (II) VESA(0):  B140XW01 V9
[    74.956] (II) VESA(0): EDID (in hex):
[    74.956] (II) VESA(0): 00ffffffffffff0006af3c1900000000
[    74.956] (II) VESA(0): 01130103801f11780ac8a59e57549226
[    74.956] (II) VESA(0): 99505400000001010101010101010101
[    74.956] (II) VESA(0): 010101010101121b5646500023302616
[    74.956] (II) VESA(0): 360035ad100000180000000f00000000
[    74.956] (II) VESA(0): 00000000000000000020000000fe0041
[    74.956] (II) VESA(0): 554f0a202020202020202020000000fe
[    74.956] (II) VESA(0): 004231343058573031205639200a0015
[    74.956] (II) VESA(0): EDID vendor "AUO", prod id 6460
[    74.956] (II) VESA(0): Printing DDC gathered Modelines:
[    74.956] (II) VESA(0): Modeline "1366x768"x0.0   69.30  1366 1404 1426 1436  768 771 777 803 -hsync -vsync (48.3 kHz eP)
[    74.956] (II) VESA(0): Searching for matching VESA mode(s):
[    74.957] Mode: 160 (0x0)

marcelocripe

[Juanito]

That confirms it, you need to load the xf86-video-intel extension - exit the gui, load the extension and then "startx".

[marcelocripe]

That confirms it, you need to load the xf86-video-intel extension - exit the gui, load the extension and then "startx".

Hi Juanito,

And I downloaded the extension xf86-video-intel.tcz, clicked Exit, Exit Prompt and clicked OK, to exit the graphical mode and enter the text or command prompt mode, typed:

Code: [Select]

tc @ box: / $ tce-load -i xf86-video-intel {Enter}
i2c-5.4.3-tinycore.tcz: OK
graphics-5.4.3-tinycore.tcz: OK
[drm: 0xf95f218f] * ERROR * CPU pipe B FIFO underrun
xf86-video-intel: OK

tc @ box: / $ startx

I apologize for my lack of basic knowledge in Linux, before applying the above commands, out of curiosity I loaded the xf86-video-intel in graphical mode with Apps, Apps: Regular Applications, Load App Locally and the screen turned black, requiring a restart of the computer. Why did the black screen happen? Why is it necessary to use the prompt to load xf86-video-intel.tcz?

Do I need to understand what each extension is?

The video card driver is xf86-video-intel.tcz and what is Xorg-7.7.tcz and Xorg-7.7-3d.tcz?

Please, how do I adjust the resolution according to the needs of the monitor after xf86-video-intel.tcz and Xorg-7.7-3d.tcz?

I still haven't been able to apply the command you taught me:

Code: [Select]

$ gsettings set org.gtk.Settings.FileChooser window-size '(400,200)'
After several attempts to apply what Mr. Rich taught me in the link post: http://forum.tinycorelinux.net/index.php/topic,23854.0.html, the br-abnt2.kmap keyboard configuration stopped working and now I no longer have single quotes '' on the Brazilian standard keyboard.

Anyway, thanks to the help I have been having in this forum, I am managing to implement most of the teachings, for which I am always grateful.

Thank you.
marcelocripe

Original text in Portuguese, translated into English by the Google translator.

-----------------

Olá Juanito,

E baixei a extensão xf86-video-intel.tcz, cliquei em Exit, Exit Prompt e cliquei em OK, para sair do modo gráfico e entrar no modo texto ou prompt de comando, digitei:

Code: [Select]

tc@box:/$ tce-load -i xf86-video-intel {Enter}
i2c-5.4.3-tinycore.tcz: OK
graphics-5.4.3-tinycore.tcz: OK
[drm:0xf95f218f] *ERROR* CPU pipe B FIFO underrun
xf86-video-intel: OK

tc@box:/$ startx

Eu peço desculpas pela minha falta de conhecimentos básicos em Linux, antes de aplicar os comandos acima, por curiosidade eu carreguei o xf86-video-intel no modo gráfico com o Apps, Apps: Regular Applications, Load App Locally e a tela fiou preta, sendo necessário reiniciar o computador. Por que aconteceu a tela preta? Por que é necessário usar o prompt para carregar o xf86-video-intel.tcz?

Eu preciso compreender o que é o cada extensão?

O driver da placa de vídeo é o xf86-video-intel.tcz e o que é são Xorg-7.7.tcz e o Xorg-7.7-3d.tcz?

Por favor, como eu faço para ajustar a resolução conforme a necessidade do monitor após a xf86-video-intel.tcz e Xorg-7.7-3d.tcz?

Eu ainda não consegui aplicar o comando que você me ensinou:

Code: [Select]

$ gsettings set org.gtk.Settings.FileChooser window-size '(400,200)' 

Após várias tentativas de aplicar o que o senhor Rich me ensinou na postagem do link: http://forum.tinycorelinux.net/index.php/topic,23854.0.html, a configuração do teclado br-abnt2.kmap parou de funcionar e agora eu não possuo mais as aspas simples ' ' no teclado padrão Brasileiro.

De qualquer, graças as ajudas que venho tendo neste fórum, eu estou conseguindo implementar a maioria dos ensinamentos, dos quais eu sou sempre grato.

Obrigado.
marcelocripe

Texto original em português, traduzido para inglês pelo tradutor do Google.

[Juanito]

You didn't say what happened after "startx" - did the gui start and if so, what resolution was used?

What resolution is your graphics hardware capable of?
What resolution is your display monitor capable of?

Did you look at Xorg.0.log to check for errors?

[marcelocripe]

You didn't say what happened after "startx" - did the gui start and if so, what resolution was used?

What resolution is your graphics hardware capable of?
What resolution is your display monitor capable of?

Did you look at Xorg.0.log to check for errors?

Juanito,

Faltou mesmo eu concluir a explicação.

No primeiro teste apliquei os comandos:

Code: [Select]

tc@box:/$ tce-load -i xf86-video-intel {Enter}
i2c-5.4.3-tinycore.tcz: OK
graphics-5.4.3-tinycore.tcz: OK
[drm:0xf95f218f] *ERROR* CPU pipe B FIFO underrun
xf86-video-intel: OK

tc@box:/$ startx

The video has a much better definition and the text is readable.

I checked the Xorg.0.log in the /var/log/Xorg.0.log directory, in the line switch to mode 1366x768 @ 60.0

I restarted the computer without saving changes, as I expected, when starting Tiny Core Plus I had the aspect of the video without installing the driver xf86-video-intel.tcz.

In the second test I applied the same commands, after the startx command, the video was again with a much better definition and the text is readable.

After restarting the graphics mode, with the Editor I opened the file onboot.lst (/mnt/sda1/tce/onboot.lst), under Xorg-7.7-3d.tcz, typed xf86-video-intel.tcz, save, restarted Tiny Core Plus doing the Backup.

After restarting the computer, the video driver was started together with Tiny Core Plus.

To change the resolution, do I change it on the switch to mode 1366x768 @ 60.0 line?

This post became a beautiful tutorial on installing video driver.

Thankful.
marcelocripe

Original text in Brazilian Portuguese, translation into English by Google Translate.

-------------------

O vídeo ficou com uma definição muito melhor e o texto está legível.

Verifiquei o Xorg.0.log no diretório /var/log/Xorg.0.log, na linha switch to mode 1366x768 @ 60.0

Reiniciei o computador sem salvar as alterações, como eu esperava, ao iniciar o Tiny Core Plus estava com o aspecto do vídeo sem a instalação do driver xf86-video-intel.tcz.

No segundo teste apliquei os mesmos comandos, após o comando startx, o vídeo voltou a ficar com uma definição muito melhor e o texto está legível.

Após reiniciar o modo gráfico, com o Editor abri o arquivo onboot.lst (/mnt/sda1/tce/onboot.lst), embaixo de Xorg-7.7-3d.tcz, digitei xf86-video-intel.tcz, salvar, reiniciei o Tiny Core Plus fazendo o Backup.

Após reiniciar o computador, o driver de vídeo foi iniciado junto com o Tiny Core Plus. 

Para alterar a resolução, eu modifico na linha switch to mode 1366x768 @ 60.0?

Este post virou um belo tutorial sobre a instalação de driver de vídeo.

Muito obrigado.
marcelocripe

Texto original em português do Brasil, tradução para o inglês por Google Tradutor.