PDA

View Full Version : [ubuntu] hp2133 and 8.10 low resolution



tlindvall
December 18th, 2008, 12:47 PM
Hello,

I have installed 8.10 to 2133 netbook using usb stick. Installation went fine using safe graphics mode (xforcevesa). During the boot progress bar gets messed up, then there is some garbled screen. At the end system is running ok at low resolution mode 640x320. When I open change resolution menu option it says unknown display and if I try to change resolution option box gets orange and don't let me do any change.

I took a look at grub's menu.lst, but there is no xforcevesa option in kernel parameters. I also tried xorg.conf from ubuntu 2133 wiki page, but it didn't help. System is still running in low resolution vga mode. I'm stuck with this display stuff. Any ideas?

hardware:
P/N: FU337EA
screen: 1024x600
bios: F.03

Regs Tarmo

tlindvall
December 18th, 2008, 07:40 PM
I assume the problem could be in the automatic recognition of the display.
xrandr gives the following output:

Screen 0: minimum 640 x 480, current 640 x 480, maximum 640 x 480
default connected 640x480+0+0 0mm x 0mm
640x480 60.0*

Does anyone know if there is possibility to disable automatic recognition and force the system to use xorg.conf display settings?

Regs Tarmo

Roliat
December 19th, 2008, 01:40 PM
Same config here, and same bug as well... If I use the driver provided by VIA and then reference to "via" instead of "vesa" in xorg.conf, the screen will slowly fade - so this doesn't exactly help with FU337EA.

tlindvall
December 19th, 2008, 02:06 PM
I also tried via drivers, no joy. Rolled back to vesa.
I tried to change panel id to 17 and res to 1024x600, no joy.

This is the xorg.log. I assume what is happening here that it uses the right xorg.conf, loads vesa driver, then it tries to automatically recognize display modes, finds only 640x480 modes, compares those to asked 1024x600 mode, decides asked mode is not available and finally takes one of those low resolution modes recognized ie 640x480. Looks like there is a bug in automatic display recognition?

Regs Tarmo

************************************************** ***************

(II) Loading /usr/lib/xorg/modules/drivers//vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
compiled for 1.5.0, module version = 1.3.0
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 4.1
(II) VESA: driver for VESA chipsets: vesa
(II) Primary Device is: PCI 01@00:00:0
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[16] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[20] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[21] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[22] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[23] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[24] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[25] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[26] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[27] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[28] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[29] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[30] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[31] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[32] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[33] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[34] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[35] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[36] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[37] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[38] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[39] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[40] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[41] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[42] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[43] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[44] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[45] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[46] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[47] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[48] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[49] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[50] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[51] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[52] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[53] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) Loading sub module "vbe"
(II) LoadModule: "vbe"

(II) Loading /usr/lib/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 1.1.0
ABI class: X.Org Video Driver, version 4.1
(II) Loading sub module "int10"
(II) LoadModule: "int10"

(II) Loading /usr/lib/xorg/modules//libint10.so
(II) Module int10: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 1.0.0
ABI class: X.Org Video Driver, version 4.1
(II) VESA(0): initializing int10
(II) VESA(0): Primary V_BIOS segment is: 0xc000
(II) VESA(0): VESA BIOS detected
(II) VESA(0): VESA VBE Version 3.0
(II) VESA(0): VESA VBE Total Mem: 32768 kB
(II) VESA(0): VESA VBE OEM: VIA N3364


(II) VESA(0): VESA VBE OEM Software Rev: 1.0
(II) VESA(0): VESA VBE OEM Vendor:
(II) VESA(0): VESA VBE OEM Product:
(II) VESA(0): VESA VBE OEM Product Rev:
(==) VESA(0): Depth 24, (--) framebuffer bpp 32
(==) VESA(0): RGB weight 888
(==) VESA(0): Default visual is TrueColor
(==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) VESA(0): VESA VBE DDC supported
(II) VESA(0): VESA VBE DDC Level 2
(II) VESA(0): VESA VBE DDC transfer in appr. 1 sec.
(II) VESA(0): VESA VBE DDC read failed
(II) VESA(0): Searching for matching VESA mode(s):
Mode: 101 (640x480)
ModeAttributes: 0x9f
WinAAttributes: 0x7
WinBAttributes: 0x0
WinGranularity: 64
WinSize: 64
WinASegment: 0xa000
WinBSegment: 0xa000
WinFuncPtr: 0xc00080c7
BytesPerScanline: 640
XResolution: 640
YResolution: 480
XCharSize: 8
YCharSize: 16
NumberOfPlanes: 1
BitsPerPixel: 8
NumberOfBanks: 1
MemoryModel: 4
BankSize: 0
NumberOfImages: 101
RedMaskSize: 0
RedFieldPosition: 0
GreenMaskSize: 0
GreenFieldPosition: 0
BlueMaskSize: 0
BlueFieldPosition: 0
RsvdMaskSize: 0
RsvdFieldPosition: 0
DirectColorModeInfo: 2
PhysBasePtr: 0xd8000000
LinBytesPerScanLine: 640
BnkNumberOfImagePages: 101
LinNumberOfImagePages: 101
LinRedMaskSize: 0
LinRedFieldPosition: 0
LinGreenMaskSize: 0
LinGreenFieldPosition: 0
LinBlueMaskSize: 0
LinBlueFieldPosition: 0
LinRsvdMaskSize: 0
LinRsvdFieldPosition: 0
MaxPixelClock: 0
Mode: 111 (640x480)
ModeAttributes: 0x9b
WinAAttributes: 0x7
WinBAttributes: 0x0
WinGranularity: 64
WinSize: 64
WinASegment: 0xa000
WinBSegment: 0xa000
WinFuncPtr: 0xc00080c7
BytesPerScanline: 1280
XResolution: 640
YResolution: 480
XCharSize: 8
YCharSize: 16
NumberOfPlanes: 1
BitsPerPixel: 16
NumberOfBanks: 1
MemoryModel: 6
BankSize: 0
NumberOfImages: 50
RedMaskSize: 5
RedFieldPosition: 11
GreenMaskSize: 6
GreenFieldPosition: 5
BlueMaskSize: 5
BlueFieldPosition: 0
RsvdMaskSize: 0
RsvdFieldPosition: 0
DirectColorModeInfo: 2
PhysBasePtr: 0xd8000000
LinBytesPerScanLine: 1280
BnkNumberOfImagePages: 50
LinNumberOfImagePages: 50
LinRedMaskSize: 5
LinRedFieldPosition: 11
LinGreenMaskSize: 6
LinGreenFieldPosition: 5
LinBlueMaskSize: 5
LinBlueFieldPosition: 0
LinRsvdMaskSize: 0
LinRsvdFieldPosition: 0
MaxPixelClock: 0
*Mode: 112 (640x480)
ModeAttributes: 0x9b
WinAAttributes: 0x7
WinBAttributes: 0x0
WinGranularity: 64
WinSize: 64
WinASegment: 0xa000
WinBSegment: 0xa000
WinFuncPtr: 0xc00080c7
BytesPerScanline: 2560
XResolution: 640
YResolution: 480
XCharSize: 8
YCharSize: 16
NumberOfPlanes: 1
BitsPerPixel: 32
NumberOfBanks: 1
MemoryModel: 6
BankSize: 0
NumberOfImages: 25
RedMaskSize: 8
RedFieldPosition: 16
GreenMaskSize: 8
GreenFieldPosition: 8
BlueMaskSize: 8
BlueFieldPosition: 0
RsvdMaskSize: 0
RsvdFieldPosition: 0
DirectColorModeInfo: 2
PhysBasePtr: 0xd8000000
LinBytesPerScanLine: 2560
BnkNumberOfImagePages: 25
LinNumberOfImagePages: 25
LinRedMaskSize: 8
LinRedFieldPosition: 16
LinGreenMaskSize: 8
LinGreenFieldPosition: 8
LinBlueMaskSize: 8
LinBlueFieldPosition: 0
LinRsvdMaskSize: 0
LinRsvdFieldPosition: 0
MaxPixelClock: 0

(II) VESA(0): Total Memory: 512 64KB banks (32768kB)
(II) VESA(0): Monitor[0]: Using hsync range of 28.00-500.00 kHz
(II) VESA(0): Monitor[0]: Using vrefresh range of 43.00-60.00 Hz
(II) VESA(0): Not using mode "1024x600" (no mode of this name)
(II) VESA(0): Not using built-in mode "640x480" (no mode of this name)
(WW) VESA(0): No valid modes left. Trying less strict filter...
(II) VESA(0): Monitor[0]: Using hsync range of 28.00-500.00 kHz
(II) VESA(0): Monitor[0]: Using vrefresh range of 43.00-60.00 Hz
(II) VESA(0): Not using mode "1024x600" (no mode of this name)
(--) VESA(0): Virtual size is 640x480 (pitch 640)
(**) VESA(0): Built-in mode "640x480"
(**) VESA(0): Display dimensions: (250, 150) mm
(**) VESA(0): DPI set to (65, 81)
(**) VESA(0): Using "Shadow Framebuffer"

tlindvall
December 19th, 2008, 04:06 PM
Bug #309734 filed regarding automatic display detection.

tlindvall
December 23rd, 2008, 10:22 PM
Got via drivers working. :) I took minbuntu conf as basis, did a lot of testing and some small changes. The last key issue was probably disabling RandR.

I couldn't solve the strange behaviour of vesa drivers auto detection:confused:, which is in the bug report. At the end looks like Ubuntu is very well suited to HP2133 mininote. This is my first experience with ubuntu. It looks very promising especially for desktop/laptop use.
:guitar:

JupaDuu
January 4th, 2009, 05:49 PM
Could you tlindvall put more exact instructions for newbies like me ?

tlindvall
January 5th, 2009, 10:22 PM
Here is how I did it:
1. load via drivers to your desktop, unpack and run ./vinstall
2. load my modified xorg.conf from the link below to your desktop
3. change the keyboard code to one used in your country
4. backup your current xorg.conf to xorg.bak
5. copy xorg.conf to /etc/X11


http://www.lindvallit.com/tarmo/xorg.conf

johnkew
January 18th, 2009, 12:13 AM
Your xorg.conf worked great for me. This particular issue must be unique to 2133's built recently, as most of the existing advice I found did not quite work, or resulted in the low vesa resolutions.

tlindvall
January 18th, 2009, 11:33 AM
I've also been wondering where do these differences originate

As you said one possibility it depends on the build (most recent having some canges) another possibility is it depends on bios version. Someone mailed to me he got the same xorg working without disabling randr. He was using bios version F.03. For me this was mandatory to get it working. I have updated the latest bios F.05. What's the bios version you are using and does this xorg work for you if you comment randr lines out?

Regs Tarmo