Tiny Core Linux

General TC => Tiny Core Netbooks => Topic started by: Zendrael on July 27, 2010, 02:33:09 PM

Title: [SOLVED] Screen Resolution 1024x600
Post by: Zendrael on July 27, 2010, 02:33:09 PM
Hi!

Tinycore is great! I really like the system! BUT... i am now working only with my netbook and can not get the default 1024x600 resolution... I heard about 915resolution.tce but i can only connect in internet via wireless (that does not work after tinycore boots up...) So, here is the question(s):

- How to setup the correct resolution?

- It will play videos via mplayer or even flash videos from youtube direct in the browser?

- The Xvesa with tinycore has composite support?

- If i can not find some applications under tinycore package management, is there any specific package from another distro that i have/can use?

Ok, that's a lot of questions... I hope someone can help me.

Thanks!
Title: Re: Screen Resolution 1024x600
Post by: roberts on July 27, 2010, 03:08:53 PM
Couldn't you place the needed extensions on to a pendrive?
Title: Re: Screen Resolution 1024x600
Post by: tinypoodle on July 27, 2010, 03:13:18 PM
Your questions might get answered to a big part by searching the forum.
Title: Re: Screen Resolution 1024x600
Post by: h-munster on July 27, 2010, 03:32:44 PM
I have 915resolution.tcz as one of my "onboot" extensions, and I think that it is supposed to work automatically in most cases.  At first, the 1024x600 resolution on my Dell Mini 9 didn't work, but it finally kicked-in for some reason.

By the way, what is the brand-model of your netbook?

I use Mplayer-nodeps.tcz, as it has no dependencies and plays movies within the frame buffer, but there are gtk versions in the TC repository.  You can install mainstream browsers with the proper plug-ins/extensions that will allow you to play video within the browser.

Don't know about composite support in Xvesa.

Don't know about using packages from other distros.

Title: Re: Screen Resolution 1024x600
Post by: curaga on July 27, 2010, 03:53:12 PM
No composite in Xvesa.
Title: Re: Screen Resolution 1024x600
Post by: tinypoodle on July 27, 2010, 04:02:53 PM
I use Mplayer-nodeps.tcz, as it has no dependencies and plays movies within the frame buffer, but there are gtk versions in the TC repository.
Also smplayer.tcz (qt based) works fine as frontend for Mplayer-nodeps.tcz
Title: Re: Screen Resolution 1024x600
Post by: h-munster on July 28, 2010, 01:32:54 AM
The first line of my "/home/tc/.xsession" reads:
Code: [Select]
/usr/bin/Xvesa -br -screen 1024x600x24 -shadow -2button -mouse /dev/input/mice -nolisten tcp -I >/dev/null 2>&1 &
What does yours say?
Title: Re: Screen Resolution 1024x600
Post by: saa_1973 on July 31, 2010, 07:37:34 AM
Hello,

sudo Xvesa -listmodes

gives the following information. I have the 915resolution.tcz extension loaded, but do not get the 1024x600 resolution. Help in this regard will be appreciated.

VBE version 3.0 (Intel(r)PineView Graphics Chip Accelerated VGA BIOS)
DAC is fixed, controller is VGA compatible, RAMDAC causes snow
Total memory: 8128 kilobytes
0x0006: 640x200x1 (monochrome) Planar (1 planes)
0x000D: 320x200x4 Planar (4 planes) (no linear framebuffer)
0x000E: 640x200x4 Planar (4 planes) (no linear framebuffer)
0x0010: 640x350x4 Planar (4 planes) (no linear framebuffer)
0x0011: 640x480x1 (monochrome) Planar (1 planes)
0x0012: 640x480x4 Planar (4 planes) (no linear framebuffer)
0x0013: 320x200x8 PseudoColor
0x0112: 640x480x24 TrueColor [8:8:8:8]
0x0114: 800x600x16 TrueColor [5:6:5:0]
0x0115: 800x600x24 TrueColor [8:8:8:8]
0x0101: 640x480x8 PseudoColor
0x0103: 800x600x8 PseudoColor
0x0111: 640x480x16 TrueColor [5:6:5:0]
Title: Re: Screen Resolution 1024x600
Post by: tinypoodle on July 31, 2010, 08:18:24 AM
What is output of:
Code: [Select]
sudo 915resolution -l |grep 1024x600
?
Title: Re: Screen Resolution 1024x600
Post by: saa_1973 on July 31, 2010, 09:27:54 AM
The output is as below:

Intel chipset detected.  However, 915resolution was unable to determine the chipset type.
Chipset Id: a0108086
Please report this problem to stomljen@yahoo.com
Title: Re: Screen Resolution 1024x600
Post by: tinypoodle on July 31, 2010, 09:35:15 AM
Is it easy for you to try Xorg?
Which version of TC do you refer to?

EDIT: Found 915resolution patched including your chipset here:
http://www.murga-linux.com/puppy/viewtopic.php?t=32462 (http://www.murga-linux.com/puppy/viewtopic.php?t=32462)

HTH
Title: Re: Screen Resolution 1024x600
Post by: Zendrael on July 31, 2010, 04:58:24 PM
Thanks by the answers! I will try "playing" more with tinycore in a vrtualmachine before installing.
Title: Re: Screen Resolution 1024x600
Post by: saa_1973 on August 01, 2010, 01:43:48 AM
Is it easy for you to try Xorg?
Which version of TC do you refer to?

EDIT: Found 915resolution patched including your chipset here:
http://www.murga-linux.com/puppy/viewtopic.php?t=32462 (http://www.murga-linux.com/puppy/viewtopic.php?t=32462)

HTH

Thanks for your help. I could use the patched version available from puppy and get the 1024x600 resolution.
However Xorg-7.5.tcz does not work and gives the following error in Xorg.0.log. I would appreciate your suggestion.


X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.33.3-tinycore i686
Current Operating System: Linux box 2.6.33.3-tinycore #2012 SMP Wed May 12 17:05:42 EEST 2010 i686
Kernel command line: initrd=tinycore.gz quiet waitusb=5:UUID="59C2-C8CE" tce=UUID="59C2-C8CE" BOOT_IMAGE=bzImage
Build Date: 28 May 2010  06:50:29PM
 
Current version of pixman: 0.18.2
   Before reporting problems, check www.tinycorelinux.com
   to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Aug  1 10:08:47 2010
(II) Loader magic: 0x819471c
(II) Module ABI versions:
   X.Org ANSI C Emulation: 0.4
   X.Org Video Driver: 6.0
   X.Org XInput driver : 7.0
   X.Org Server Extension : 2.0
(--) using VT number 2

(--) PCI:*(0:0:2:0) 8086:a011:104d:9075 rev 0, Mem @ 0xfea80000/524288, 0xe0000000/268435456, 0xfe700000/1048576, I/O @ 0x0000f0f0/8
(--) PCI: (0:0:2:1) 8086:a012:104d:9075 rev 0, Mem @ 0xfea00000/524288
(==) Using default built-in configuration (30 lines)
(==) --- Start of built-in configuration ---
   Section "Device"
      Identifier   "Builtin Default intel Device 0"
      Driver   "intel"
   EndSection
   Section "Screen"
      Identifier   "Builtin Default intel Screen 0"
      Device   "Builtin Default intel Device 0"
   EndSection
   Section "Device"
      Identifier   "Builtin Default vesa Device 0"
      Driver   "vesa"
   EndSection
   Section "Screen"
      Identifier   "Builtin Default vesa Screen 0"
      Device   "Builtin Default vesa Device 0"
   EndSection
   Section "Device"
      Identifier   "Builtin Default fbdev Device 0"
      Driver   "fbdev"
   EndSection
   Section "Screen"
      Identifier   "Builtin Default fbdev Screen 0"
      Device   "Builtin Default fbdev Device 0"
   EndSection
   Section "ServerLayout"
      Identifier   "Builtin Default Layout"
      Screen   "Builtin Default intel Screen 0"
      Screen   "Builtin Default vesa Screen 0"
      Screen   "Builtin Default fbdev Screen 0"
   EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default intel Screen 0" (0)
(**) |   |-->Monitor "<default monitor>"
(**) |   |-->Device "Builtin Default intel Device 0"
(==) No monitor specified for screen "Builtin Default intel Screen 0".
   Using a default monitor configuration.
(**) |-->Screen "Builtin Default vesa Screen 0" (1)
(**) |   |-->Monitor "<default monitor>"
(**) |   |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified for screen "Builtin Default vesa Screen 0".
   Using a default monitor configuration.
(**) |-->Screen "Builtin Default fbdev Screen 0" (2)
(**) |   |-->Monitor "<default monitor>"
(**) |   |-->Device "Builtin Default fbdev Device 0"
(==) No monitor specified for screen "Builtin Default fbdev Screen 0".
   Using a default monitor configuration.
(==) Not automatically adding devices
(==) Not automatically enabling devices
(WW) The directory "/usr/local/lib/X11/fonts/OTF" does not exist.
   Entry deleted from font path.
(WW) The directory "/usr/local/lib/X11/fonts/100dpi/" does not exist.
   Entry deleted from font path.
(==) 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/
(==) ModulePath set to "/usr/local/lib/X11/modules"
(==) |-->Input Device "<default pointer>"
(==) |-->Input Device "<default keyboard>"
(==) The core pointer device wasn't specified explicitly in the layout.
   Using the default mouse configuration.
(==) The core keyboard device wasn't specified explicitly in the layout.
   Using the default keyboard configuration.
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) LoadModule: "extmod"
(II) Loading /usr/local/lib/X11/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
   compiled for 1.7.7, module version = 1.0.0
   Module class: X.Org Server Extension
   ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/local/lib/X11/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
   compiled for 1.7.7, module version = 1.0.0
   Module class: X.Org Server Extension
   ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/local/lib/X11/modules/extensions/libglx.so
(II) Module glx: vendor="X.Org Foundation"
   compiled for 1.7.7, module version = 1.0.0
   ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/local/lib/X11/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
   compiled for 1.7.7, module version = 1.0.0
   ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/local/lib/X11/modules/extensions/libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
   compiled for 1.7.7, module version = 1.1.0
   ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "intel"
(II) Loading /usr/local/lib/X11/modules/drivers/intel_drv.so
(II) Module intel: vendor="X.Org Foundation"
   compiled for 1.7.7, module version = 2.11.0
   Module class: X.Org Video Driver
   ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "vesa"
(II) Loading /usr/local/lib/X11/modules/drivers/vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
   compiled for 1.7.7, module version = 2.3.0
   Module class: X.Org Video Driver
   ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "fbdev"
(II) Loading /usr/local/lib/X11/modules/drivers/fbdev_drv.so
(II) Module fbdev: vendor="X.Org Foundation"
   compiled for 1.7.7, module version = 0.4.2
   ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "mouse"
(II) Loading /usr/local/lib/X11/modules/input/mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
   compiled for 1.7.7, module version = 1.5.0
   Module class: X.Org XInput Driver
   ABI class: X.Org XInput driver, version 7.0
(II) LoadModule: "kbd"
(II) Loading /usr/local/lib/X11/modules/input/kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
   compiled for 1.7.7, module version = 1.4.0
   Module class: X.Org XInput Driver
   ABI class: X.Org XInput driver, version 7.0
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
   i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
   E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
   965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
   4 Series, G45/G43, Q45/Q43, G41, B43, Clarkdale, Arrandale
(II) VESA: driver for VESA chipsets: vesa
(II) FBDEV: driver for framebuffer: fbdev
(II) Primary Device is: PCI 00@00:02:0
(WW) Falling back to old probe method for vesa
(WW) Falling back to old probe method for fbdev
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/local/lib/X11/modules/linux/libfbdevhw.so
(II) Module fbdevhw: vendor="X.Org Foundation"
   compiled for 1.7.7, module version = 0.0.2
   ABI class: X.Org Video Driver, version 6.0
(EE) open /dev/fb0: No such device
(EE) intel(0): No kernel modesetting driver detected.
(II) UnloadModule: "intel"
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

Please consult the TinyCore Linux support
    at www.tinycorelinux.com
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
Title: Re: Screen Resolution 1024x600
Post by: curaga on August 01, 2010, 01:55:05 AM
@saa_1973

Quote
(EE) intel(0): No kernel modesetting driver detected.

Do you have graphics-2.6.33.3-tinycore.tcz loaded? Intel needs it for 2d too.
Title: Re: Screen Resolution 1024x600
Post by: tinypoodle on August 01, 2010, 03:08:15 AM
Xorg could do native resolution without 915resolution, but in case 915resolution works for your chipset, Xvesa should work with native resolution.  ;)

That's why i prefixed the part about patched 915resolution with "EDIT", I found that after already having posted suggestion to try Xorg (meant without 915resolution working).
Title: Re: Screen Resolution 1024x600
Post by: 3rail on August 06, 2010, 06:31:22 AM
what about this part of the xorg error:

Code: [Select]
(EE) open /dev/fb0: No such device
shouldn't he enable the framebuffer by using a vga boot code?
Title: Re: Screen Resolution 1024x600
Post by: curaga on August 06, 2010, 12:14:01 PM
what about this part of the xorg error:

Code: [Select]
(EE) open /dev/fb0: No such device
shouldn't he enable the framebuffer by using a vga boot code?

Only if he wants to use fbdev instead of vesa or the native driver. (or have a pretty console)
Title: Re: Screen Resolution 1024x600
Post by: Marco Trapanese on August 26, 2010, 02:09:52 AM
EDIT: Found 915resolution patched including your chipset here:
http://www.murga-linux.com/puppy/viewtopic.php?t=32462 (http://www.murga-linux.com/puppy/viewtopic.php?t=32462)


I have the same problem trying to setup the resolution of 1024x600.
I downloaded the pet file from the link an copied to /usr/sbin

But the output of 915resolution -l is the same.

Another question: I have to manually backup the two files in /opt/.filetool.lst or there is a better way?

Thanks
Marco
Title: Re: Screen Resolution 1024x600
Post by: tinypoodle on August 26, 2010, 02:40:04 AM
Try
Code: [Select]
/usr/sbin/915resolution 50 1024 600
Title: Re: Screen Resolution 1024x600
Post by: Marco Trapanese on August 26, 2010, 02:59:50 AM
Thanks! It works.
And works also

Code: [Select]
/usr/sbin/915resolution -l
but even if I boot with vga=577 (1024x600x16 mode $41+$200 -> 577 dec) I get a 800x600 resolution (I guess).
Title: Re: Screen Resolution 1024x600
Post by: tinypoodle on August 26, 2010, 03:03:24 AM
In framebuffer or Xvesa?
Title: Re: Screen Resolution 1024x600
Post by: Marco Trapanese on August 26, 2010, 03:11:29 AM
framebuffer

this is my boot command:

Code: [Select]
kernel /boot/bzImage quiet tinycore tce=sda3 text vga=577

and this the entry in /home/tc/.xsession

Code: [Select]
/usr/local/bin/Xfbdev -mouse /dev/input/mice,5 -nolisten tcp -I >/dev/null 2>&1&
Title: Re: Screen Resolution 1024x600
Post by: tinypoodle on August 26, 2010, 03:21:40 AM
http://forum.tinycorelinux.net/index.php?topic=6887.msg36786#msg36786

Are you using TC 3.0 with KMS?

Xfbdev will use whatever resolution the framebuffer has, I think, but 915 resolution can set native resolution for Xvesa regardless of framebuffer.
Title: Re: Screen Resolution 1024x600
Post by: Marco Trapanese on August 26, 2010, 03:29:43 AM
I'm running TC 3.0, but what's KMS?

Quote
Xfbdev will use whatever resolution the framebuffer has, I think, but 915 resolution can set native resolution for Xvesa regardless of framebuffer.


I'm not sure to correctly understand your sentence and the thread you linked.
Are you saying I can't get my netbook work at 1024x600 in framebuffer?
Title: Re: Screen Resolution 1024x600
Post by: tinypoodle on August 26, 2010, 06:14:57 AM
Kernel Mode Setting

I am not sure what you do not understand.
Xfbdev will use whatever resolution of framebuffer as is before starting X.
Xvesa could be "tricked" into native resolution by using 915resolution.

The thread I linked discusses native resolution in framebuffer.
No, I am not saying you can't your netbook work at 1024x600 in framebuffer.
See the link to approaches of solutions in the linked thread.
Personally I have never used uvesafb (neither patched bootloader)

Best resolution I get with vga=ask is 800x600 (which makes images look distorted on framebuffer console)
Title: Re: Screen Resolution 1024x600
Post by: solleon on August 31, 2010, 09:46:20 AM
Hey guys,

My steps to work with 1024 x 600:


My xorg.conf from ubunt community

Code: [Select]
Section "Files"
ModulePath   "/usr/local/lib/X11/modules"
FontPath     "/usr/local/lib/X11/fonts/misc/"
FontPath     "/usr/local/lib/X11/fonts/TTF/"
FontPath     "/usr/local/lib/X11/fonts/OTF"
FontPath     "/usr/local/lib/X11/fonts/Type1/"
FontPath     "/usr/local/lib/X11/fonts/100dpi/"
FontPath     "/usr/local/lib/X11/fonts/75dpi/"
EndSection

Section "InputDevice"
Identifier  "Generic Keyboard"
Driver      "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "abnt2"
Option "XkbLayout" "pt"
Option "XkbOptions" "lv3Ç:ralt_switch"
EndSection

Section "InputDevice"
Identifier  "Configured Mouse"
Driver      "mouse"
EndSection

Section "Monitor"
Identifier   "Configured Monitor"
VendorName   "Generic LCD Display"
ModelName    "LCD Panel 1024x600"
HorizSync 31.5 - 37.9
VertRefresh 50.0 - 70.0
DisplaySize 195 113
modeline "1024x600@60" 48.96 1024 1064 1168 1312 600 601 604 622 -HSync -VSync
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
        ### [arg]: arg optional
Identifier  "Configured Video Device"
Driver      "geode"
VendorName  "Unknown Vendor"
BoardName   "vesa"
BusID       "PCI:0:1:1"
Option "AccelMethod" "EXA"
Option "MigrationHeuristic" "greedy"
Option "PanelMode" "48960 1024 1064 1168 1312 600 601 604 622"
Screen 0
EndSection

Section "Screen"
Identifier "Default Screen"
Device     "Configured Video Device"
Monitor    "Configured Monitor"
Defaultdepth 24
SubSection "Display"
Depth 24
Virtual 1024 600
Modes "1024x600@60"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
screen 0 "Default Screen" 0 0
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section "Module"
Load "glx"
Load "GLcore"
### Load "v41"
EndSection

Section "ServerFlags"
EndSection
Title: Re: Screen Resolution 1024x600
Post by: Zendrael on October 06, 2010, 07:12:10 AM
OK, so... let's put a finishing point here:

Wich is more faster and less power and cpu consuption: Xvesa or Xorg (with appropriate drivers) on a netbook with Intel 945GME ?

I usually use my netbook to browse the web, programming for the web, watch some videos and image editing with gimp and inkscape. The hardware is:

video intel 945GME
2GB RAM
250GB HD (not SSD)
All intel chipsets and RTL8101E/RTL8102E for wireless card.

What will be better (like i said in the beginning) Xvesa or Xorg? (or Xfbdev?)

Thanks!
Title: Re: Screen Resolution 1024x600
Post by: Juanito on October 06, 2010, 07:25:08 AM
I use tc on a laptop with Intel 945 graphics and cannot see the difference between Xvesa and Xorg-7.5 in normal use, so I use Xvesa most of the time.
Title: Re: Screen Resolution 1024x600
Post by: tinypoodle on October 06, 2010, 08:44:39 AM
OK, so... let's put a finishing point here:

Wich is more faster and less power and cpu consuption: Xvesa or Xorg (with appropriate drivers) on a netbook with Intel 945GME ?

http://forum.tinycorelinux.net/index.php?topic=6990.0
Title: Re: [SOLVED] Screen Resolution 1024x600
Post by: makoto on April 10, 2012, 04:33:46 PM
Hey, I found a better way than loading 915resolution! I use thinkpad e420 which has a resolution of 1366*768 but Xvesa couldn't display that way,and 915resolution said it couldn't determine my chipset type. So I installed xf86-video-all.tcz, graphics-3.0.3-tinycore.tcz and Xorg-7.6-3d.tcz. Note that you have to download only them instead of Onboot because system may halt during loading. Then modify your onboot.lst, put xf86-video-all.tcz on top and put the others after all the default items. Then it works!
Title: Re: [SOLVED] Screen Resolution 1024x600
Post by: Scampada on April 05, 2015, 02:56:58 AM
Hi,
I've read the thread and tried to use some advices in my own TC. I want to get a framebuffer console with no distortion; so I tried to set vga=577 and it caused only that I booted into 80x25 CLI.
Standard 788 and 789 work fine. I'll read also the thread mentioned somewhere above concerning native resolutions, but, maybe if someone knows that I definitely can not do this, maybe he'd say it earlier than I read that thread and do some more unnecessary quiestion.))

I have tried 915resolution, changed on of the modes to mine, then edited fb.modes and did fbset, but nothing happened...

...That's because fbset doesn't change the mode from file... when I feed it with /etc/fb.modes (which I have to create) and then type fbset it showes me my old 800x600 resolution.
Title: Re: [SOLVED] Screen Resolution 1024x600
Post by: Scampada on April 05, 2015, 03:34:45 AM
When I look at fbset it shows me
mode "800x600-75"
    geometry ...
    timings...
    accel ...
    rgba ...
endmode

when I look for /etc/fb.modes there is no such file. I touch and edit it.
Then I do fbset 1024x600-60 and nothing happens though it doesn't say there is no such mode.
Then I do fbset again and it shows me 800x600-75 etc...
Title: Re: [SOLVED] Screen Resolution 1024x600
Post by: Scampada on April 05, 2015, 07:25:45 AM
SOLVED too; no need to use such magic; my vbios supports native 1024x600 and my grub can do things like set gfxpayload=keep while working in 1024x600 mode from the very beginning.
Now avatars won't distort in the links and fonts look sharper. Fine.