display problems with ubuntu netbook installation

Your graphics card does not, out of the box, support the ubuntu netbook interface, known as "unity".

you can simply use the fallback desktop with no worries; all the software is the same. The main difference is that the unity interface is simplified as compared to the fallback interface.

If you want us to go a bit further,we need your video card information. To get this, can you open a terminal (Ctrl+Alt+T), and cut and paste the following command

lspci

This will generate a listing of devices on your computer, please post that back here.

I can Load ubuntu netbook inside the window os, but not with the stand alone usb flash drive it does not give me the option

for the safe graphics mode so when ubuntu loads up my umpc screen scrambles & flickers if there is away to get the option

for the safe graphics mode to display when loading up. Would u post the solution or send me an email with the solution.

My intergrated graphics card is:- VIA/S3G Unichrome Pro 11 1GP

                                                           Cheers!

The problem is still not solved

The drivers for that video card are described as "terrible".

I tried to follow some of the instructions here, but I do not have your card, and you have not provided the "lspci" instructions I need to help you. At any rate, I *think* you want "VIA proprietary graphics driver for Chrome9"; but without the chipset number as reported by lspci, I am not sure.

https://help.ubuntu.com/community/OpenChrome#VIA%20proprietary%20graphics%20driver%20for%20Chrome9

Note that via's web-page appears to be quite broken; I tried for a bit to find the download page, but it appears to be entirely blank.

This is the information that I got when I followed your instructions:-

00:00.0 Host bridge: VIA Technologies, Inc. CX700/VX700 Host Bridge (rev 03)

00:00.1 Host bridge: VIA Technologies, Inc. CX700/VX700 Host Bridge

00:00.2 Host bridge: VIA Technologies, Inc. CX700/VX700 Host Bridge

00:00.3 Host bridge: VIA Technologies, Inc. CX700/VX700 Host Bridge

00:00.4 Host bridge: VIA Technologies, Inc. CX700/VX700 Host Bridge

00:00.7 Host bridge: VIA Technologies, Inc. CX700/VX700 Host Bridge

00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge

00:0f.0 IDE interface: VIA Technologies, Inc. VX800 Serial ATA and EIDE Controller

00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 90)

00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 90)

00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 90)

00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 90)

00:11.0 ISA bridge: VIA Technologies, Inc. CX700/VX700 PCI to ISA Bridge

00:11.7 Host bridge: VIA Technologies, Inc. CX700/VX700 Internal Module Bus

00:13.0 PCI bridge: VIA Technologies, Inc. CX700/VX700 Host Bridge

00:13.1 PCI bridge: VIA Technologies, Inc. CX700/VX700 PCI to PCI Bridge

01:00.0 VGA compatible controller: VIA Technologies, Inc. CX700/VX700 [S3 UniChrome Pro] (rev 03)

02:01.0 Audio device: VIA Technologies, Inc. VT1708/A [Azalia HDAC] (VIA High Definition Audio Controller) (rev 10)

03:02.0 Mass storage controller: Winbond Electronics Corp Device 8480 (rev 07)

03:02.1 SD Host controller: Winbond Electronics Corp Device 8481 (rev 07)

OK, their web page appears to be feeling a bit better today, but it is still quite broken. I found the source code, but cannot seem to make heads or tails of their build system. I can't even guarantee that their driver is not simply broken.

== Don't read beyond here, its just in case someone can use this info to help you ==

I can find the source code, but I do not know how to build it into anything useful.

You have to download this file, specifying ubuntu 9.04 as the
http://linux.via.com.tw/support/beginDownload.action?eleid=308&fid=603

It will save as
via-xserver-86a-50283_src.tgz

which is wrong -- its a bzipped file, not a gzipped file -- file-roller will say the archive is not a gzip file.

rename it to:
via-xserver-86a-50283_src.tar.bz2

I believe the useful code is in the via-xserver-86a-50283_src/DRM/H5DRM_Independent_2.6.27_28 folder -- not sure.

The instructions are woeful.

" Get the kernel source code which match exactly to our distribution, since some distributions has modify original kernel source."

No link, no description of what the author was doing, just "do it like I have done" -- great -- who are you? What have you done?

I guess you need a pristine kernel-headers & build-essential. The makefile is quite simple, and simply invokes the kernel's make to generate the chrome9 module.

Once built, it says you can make install to install the module, then depmod the module to generate the dependency info.

Its still not clear how this relates to the card though -- the XServer/Misc vinstall_ubuntu does a check over the lspci output to determine the chip ID.

Specifically
 CHIPID=`lspci -nn | awk /VGA/ | sed -n 's/.*1106:\([0-9]\)\([0-9]\)\([0-9]\)\([0-9]\)].*/\1\2\3\4

it then does a lookup with
 case "$CHIPID" in
  3108)
  DRIDRIVERNAME=via_unichrome;;
  3344)
  DRIDRIVERNAME=via_unichrome;;
  3157)
  DRIDRIVERNAME=via_unichrome;;
  3371)
  DRIDRIVERNAME=via_chrome9;;
  1122)
  DRIDRIVERNAME=via_chrome9;;
  3230)
  DRIDRIVERNAME=via_chrome9;;
                5122)
                DRIDRIVERNAME=via_chrome9;;
                *) DRIDRIVERNAME="Invalid";;
        esac

Punching in Clueless' lspci output tells me that the chipset is invalid...

Clueless:

one more question, can you provide the output of these two commands?

cat /etc/lsb-release
uname -a

Hi There,

Thanks for your patience! I have all drivers to make all the functions
on my UMPC T770 work but there are all based on a windows vista platform
they are all separate window based exe.
On Sat, 2011-03-05 at 18:43 +0000, mycae wrote:
> Your question #147420 on xserver-xorg-video-openchrome in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+question/147420
>
> mycae posted a new comment:
> OK, their web page appears to be feeling a bit better today, but it is
> still quite broken. I found the source code, but cannot seem to make
> heads or tails of their build system. I can't even guarantee that their
> driver is not simply broken.
>
>
> == Don't read beyond here, its just in case someone can use this info to help you ==
>
> I can find the source code, but I do not know how to build it into
> anything useful.
>
>
> You have to download this file, specifying ubuntu 9.04 as the
> http://linux.via.com.tw/support/beginDownload.action?eleid=308&fid=603
>
> It will save as
> via-xserver-86a-50283_src.tgz
>
> which is wrong -- its a bzipped file, not a gzipped file -- file-roller
> will say the archive is not a gzip file.
>
> rename it to:
> via-xserver-86a-50283_src.tar.bz2
>
> I believe the useful code is in the via-xserver-86a-
> 50283_src/DRM/H5DRM_Independent_2.6.27_28 folder -- not sure.
>
> The instructions are woeful.
>
> " Get the kernel source code which match exactly to our distribution,
> since some distributions has modify original kernel source."
>
> No link, no description of what the author was doing, just "do it like I
> have done" -- great -- who are you? What have you done?
>
> I guess you need a pristine kernel-headers & build-essential. The
> makefile is quite simple, and simply invokes the kernel's make to
> generate the chrome9 module.
>
> Once built, it says you can make install to install the module, then
> depmod the module to generate the dependency info.
>
> Its still not clear how this relates to the card though -- the
> XServer/Misc vinstall_ubuntu does a check over the lspci output to
> determine the chip ID.
>
> Specifically
> CHIPID=`lspci -nn | awk /VGA/ | sed -n 's/.*1106:\([0-9]\)\([0-9]\)\([0-9]\)\([0-9]\)].*/\1\2\3\4
>
> it then does a lookup with
> case "$CHIPID" in
> 3108)
> DRIDRIVERNAME=via_unichrome;;
> 3344)
> DRIDRIVERNAME=via_unichrome;;
> 3157)
> DRIDRIVERNAME=via_unichrome;;
> 3371)
> DRIDRIVERNAME=via_chrome9;;
> 1122)
> DRIDRIVERNAME=via_chrome9;;
> 3230)
> DRIDRIVERNAME=via_chrome9;;
> 5122)
> DRIDRIVERNAME=via_chrome9;;
> *) DRIDRIVERNAME="Invalid";;
> esac
>
>
> Punching in Clueless' lspci output tells me that the chipset is invalid...
>
> You received this question notification because you are a direct
> subscriber of the question.

Hi There,

Thanks for your patience! I have all drivers to make all the functions
on my UMPC T770 work but there are all based on a windows vista platform
they are all separate window based exe.
On Sat, 2011-03-05 at 18:43 +0000, mycae wrote:
> Your question #147420 on xserver-xorg-video-openchrome in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+question/147420
>
> mycae posted a new comment:
> OK, their web page appears to be feeling a bit better today, but it is
> still quite broken. I found the source code, but cannot seem to make
> heads or tails of their build system. I can't even guarantee that their
> driver is not simply broken.
>
>
> == Don't read beyond here, its just in case someone can use this info to help you ==
>
> I can find the source code, but I do not know how to build it into
> anything useful.
>
>
> You have to download this file, specifying ubuntu 9.04 as the
> http://linux.via.com.tw/support/beginDownload.action?eleid=308&fid=603
>
> It will save as
> via-xserver-86a-50283_src.tgz
>
> which is wrong -- its a bzipped file, not a gzipped file -- file-roller
> will say the archive is not a gzip file.
>
> rename it to:
> via-xserver-86a-50283_src.tar.bz2
>
> I believe the useful code is in the via-xserver-86a-
> 50283_src/DRM/H5DRM_Independent_2.6.27_28 folder -- not sure.
>
> The instructions are woeful.
>
> " Get the kernel source code which match exactly to our distribution,
> since some distributions has modify original kernel source."
>
> No link, no description of what the author was doing, just "do it like I
> have done" -- great -- who are you? What have you done?
>
> I guess you need a pristine kernel-headers & build-essential. The
> makefile is quite simple, and simply invokes the kernel's make to
> generate the chrome9 module.
>
> Once built, it says you can make install to install the module, then
> depmod the module to generate the dependency info.
>
> Its still not clear how this relates to the card though -- the
> XServer/Misc vinstall_ubuntu does a check over the lspci output to
> determine the chip ID.
>
> Specifically
> CHIPID=`lspci -nn | awk /VGA/ | sed -n 's/.*1106:\([0-9]\)\([0-9]\)\([0-9]\)\([0-9]\)].*/\1\2\3\4
>
> it then does a lookup with
> case "$CHIPID" in
> 3108)
> DRIDRIVERNAME=via_unichrome;;
> 3344)
> DRIDRIVERNAME=via_unichrome;;
> 3157)
> DRIDRIVERNAME=via_unichrome;;
> 3371)
> DRIDRIVERNAME=via_chrome9;;
> 1122)
> DRIDRIVERNAME=via_chrome9;;
> 3230)
> DRIDRIVERNAME=via_chrome9;;
> 5122)
> DRIDRIVERNAME=via_chrome9;;
> *) DRIDRIVERNAME="Invalid";;
> esac
>
>
> Punching in Clueless' lspci output tells me that the chipset is invalid...
>
> You received this question notification because you are a direct
> subscriber of the question.

;Hi There,

Thanks for the advice and the help that I have received so far from

the Linux community. The info below does it help in anyway at all to find away to

get the touch screen functions to work on my umpc.

; S3ISCFG.DAT for UniChrome Family (Windows 2K/XP)

; Configuration options for the SETUP program.

; The [S3Setup] section specifies overall setup behavior, and is also

; used if no specific section exists for the detected hardware.

   ; Type: default is "Unattended"

   ; "UserSetup" - standard wizard-style install.

   ; "UserNoSelect" - like UserSetup, but no Min, Full, Custom choice.

[S3Setup]

;Type=UserSetup

;Type=UserNoSelect

Type=Unattended

   ; OS: specify an exact OS requirement. If not found, Setup will work on

   ; Win9x (16-bit setup) or NT/2K/XP (32-bit setup). To require only one OS,

   ; specify "Win95", "Win98", "NT40", "Win2000" or "WinXP". "Win2K or WinXP"

   ; will allow only Win2K or XP, not NT.

OS=WinXP or Vista or Win2000

   ; Large text in upper-left corner of setup window. If "ProductLongName" isn't

   ; found, will use "ProductShortName" instead; defaults to "S3 Driver Setup".

   ; If this is found, it replaces "S3" in the default text. So if

   ; ProductLongName is "Savage4", then the main title is "Savage4 Driver Setup"

   ; NOTE: "Product" should fit within 8 letters if possible, for 16-bit setups.

ProductLongName=VIA/S3G UniChrome Family Win2K/XP/Server2003 Display

ProductShortName=UChromeP

   ; Name displayed in Add/Remove Programs, or for the uninstall icon.

   ; If this isn't specified, the default will be the product name followed

   ; by the name of any *separate* utilities. Utils installed in a driver

   ; INF file don't have names we can extract easily.

UninstName=VIA/S3G Display Driver

    ; This sets up the version, and is used for some uninstalling functions.

    ; By default, this is "1.00.00", but should be filled in with the real

    ; version number of the product.

Version=22.00.01g

   ; Setup/Driver version, used for some uninstall functions. Default is

   ; "1.00.00", but should be filled in with the real driver version.

DrvINF=uc06i.inf

DrvName=vtdisp.dll

WindowsConfirmAutoOk=1

   ; Use BPP/XRes/YRes to specify the desired resolution and color depth when

   ; installing a driver. However, Windows may not use the supplied info if

   ; it can't detect monitor type. These can also be supplied as command line

   ; arguments (e.g. "BPP=32 Xres=800 Yres=600")

XRes=800

YRes=600

BPP=32

Refresh=1

   ; SetOnlyIfVga: default is 0. If 1, Setup only uses BPP/XRes/YRes if system

   ; is in VGA mode. If not in VGA mode, Setup ignores Bpp/XRes/YRes.

SetOnlyIfVga=0

UsePhysPanelSize=0

PanelID_CR=63

PanelCR_mask=15

PanelX_1=800

PanelY_1=600

PanelX_2=1024

PanelY_2=768

PanelX_3=1280

PanelY_3=768

PanelX_5=1400

PanelY_5=1050

   ; Specify Reboot=0 to prevent setup from rebooting. This has the same

   ; effect as adding "NoReboot" to command-line for setup. ConfirmReboot=0/1

   ; is same as cmdline options "ConfirmReboot" or "NoConfirmReboot",

   ; controlling whether user is prompted before rebooting. The default is to

   ; allow reboots. If NoSilentReboot=1, then setup won't reboot if it's run

   ; in Silent mode (with a -s); if 0, setup will use the "Reboot" key value.

   ; ConfirmSilentReboot default is 0. Set to 1 for confirm, even in silent mode.

Reboot=1

ConfirmReboot=1

IgnoreOSReboot=1

;NoSilentReboot=1

   ; Setup.exe Reboots, prompts for reboot

   ; Setup.exe -s Silent, reboots, no reboot prompt

   ; Uninstall: specifies where the user can find the uninstall option.

   ; Set to "Start Menu" to place it in the Start Menu, "AddRemove"

   ; to put it in Control Panel->Add/Remove Programs area, or "Desktop"

   ; to have a shortcut icon on the desktop. Default is none.

Uninstall=AddRemove

UninstallUsing=s3minset

   ; Default is 0. If 1, won't ask user to confirm uninstall.

   ; If 1, user must confirm when uninstalling.

UninstallPrompt=1

   ; Default is 0. If 1, uninstall will not show any progress dialog.

   ; If 0, an uninstall progress dialog will be shown.

SilentUninstall=0

AllowUtilUninstall=1

   ; FindDeviceNum: defines which adapter to find if multiple adapters

   ; exist. Default is 0 = first adapter (i.e. PCI adapters found before

   ; AGP). 1=2nd adapter, 2=3rd, etc. -1=last, no matter what number it is.

FindDeviceNum = -1

   ; Set ShowLicense to 1 to display license agreement in UserSetup mode.

   ; Defaults to not showing license.

ShowLicense=0

   ; Set "EndScreenDetail=1" to have the reboot prompt screen at the end

   ; detail exactly what got installed (driver, names of utilities, etc.)

   ; Default is to show a standard message, no details.

EndScreenDetail=1

   ; Source: either "Uncompressed" (default) or "CAB" (not supported yet).

   ; "Uncompressed" means all necessary files are in uncompressed format

   ; in source directory. "CAB" means files are stored in an Ishield CAB file,

   ; and must be extracted to TEMP directory before they can be installed.

Source=Uncompressed

;Source=CAB

   ; To have the setup program create a log file, specify that file's name here.

   ; The log file will always be created in the Windows directory.

   ; Command line argument is "LogFile=s3setup.log"

LogFile=s3iscfg.log

egxpen.INF

;

;Installation file (.inf) for the Touchkit HID digitizer device.

;

; Copyright (c) 2006 Inc.

[version]

signature="$WINDOWS NT$"

Class=HIDClass

ClassGuid={745a17a0-74d3-11d0-b6fe-00a0c90f57da}

Provider=%eGalax%

;LayoutFile=layout.inf

CatalogFile=egxpen.cat

DriverVer=03/26/2007, 1.0.0.1526

[SourceDisksNames]

1 = %DiskId1%,,

[ControlFlags]

ExcludeFromSelect=*

[DestinationDirs]

DefaultDestDir =11 ;LDID_SYS

egxPenInst.NT.Copy =12 ;LDID_DRIVERS

; Drivers

;----------------------------------------------------------

[Manufacturer]

%eGalax%=eGalax

[eGalax]

%ACPI\egxpen.DeviceDesc% =egxPenInst,ACPI\EGX5801

%ACPI\egxpen.DeviceDesc% =egxPenInst,ACPI\EGX5802

;%ACPI\egxpen.DeviceDesc% =egxPenInstOverride,ACPI\EGX5802

[egxPenInst.NT]

Include=layout.inf

Needs=SourceDisksFiles

CopyFiles =egxPenInst.NT.Copy

;[egxPenInstOverride.NT]

;CopyFiles =egxPenInst.NT.Copy

[egxPenInst.NT.Copy]

egxpen.sys

;serial.sys

[egxPenInst.NT.HW]

AddReg =SerialInst.NT.HW.AddReg,egx.NT.HW.AddReg

;[egxPenInstOverride.NT.HW]

;AddReg =SerialInst.NT.HW.AddReg,egx.NT.HW.AddReg,egxOverride.NT.HW.AddReg

[egxPenInst.NT.Services]

AddService =egxpen,0x00000002,egxPenServiceInst,egxEventLogInst

AddService =Serial,,SerialServiceInst, SerialEventLogInst

;[egxPenInstOverride.NT.Services]

;AddService =egxpen,0x00000002,egxPenServiceInst,egxEventLogInst

;AddService =Serial,,SerialServiceInst, SerialEventLogInst

[egxEventLogInst]

AddReg =egxEventLogAddReg

[egx.NT.HW.AddReg]

HKR,,"NoOutOfRange",0x00010001,1

; The following registry value can be used to specify the characteristics

; of the touch panel and the controller which will override default values

; in the driver. The registry value represents the binary form of the

; following structure:

; struct _DIGI_DATA {

; USHORT wXMax; //Logical X Max (0x3fff for 14-bit resolution)

; USHORT wYMax; //Logical Y Max (0x3fff for 14-bit resolution)

; USHORT wXDim; //Physical dimension of X (in 100th inches)

; USHORT wYDim; //Physical dimension of Y (in 100th inches)

; ULONG dwSamplingRate; //Sampling rate setting

; };

;

; DigiData: wXMax=0x3fff (14-bit)

; wYMax=0x3fff (14-bit)

; wXDim=0x1770 (6.000 in)

; wYDim=0x0e29 (3.625 in)

; dwSamplingRate=3 (120 samples/sec)

;HKR,,"DigiData",0x00000001,ff,3f,ff,3f,70,17,29,0e,03,00,00,00

HKLM,"System\CurrentControlSet\Control\TabletPC\LinearityData","SR12",0x00000001,40,00,00,00,02,00,00,00,00,00,00,00,00,00,00,00,00,80,00,00,00,80,00,00,00,00,00,00,02,00,02,00,f5,04,44,08,34,08,88,14,b8,7a,44,08,e6,7a,b6,14,f5,04,33,77,e6,07,0e,6a,b8,7a,33,77,16,7b,5a,6a

;[egxOverride.NT.HW.AddReg]

;; DeviceFlags: 1 = Transpose XY

;; 2 = Reverse X

;; 4 = Reverse Y

;; Note that if more than one of the above bits are set, the driver will

;; first do the "Transpose XY" then "Reverse X" and lastly "Reverse Y".

;;

;; DeviceFlags = 3 (Transpose XY, Reverse X)

;HKR,,"DeviceFlags",0x00010001,3

[egxEventLogAddReg]

HKR,,EventMessageFile,0x00020000,"%%SystemRoot%%\System32\IoLogMsg.dll;%%SystemRoot%%\System32\drivers\egxpen.sys"

HKR,,TypesSupported,0x00010001,7

; -------------- eGalax Pen Driver install section

[egxPenServiceInst]

DisplayName = %egxPen.SVCDESC%

ServiceType = 1 ; SERVICE_KERNEL_DRIVER

StartType = 3 ;

ErrorControl = 1 ; SERVICE_ERROR_NORMAL

ServiceBinary = %12%\egxpen.sys

LoadOrderGroup = Extended Base

[SerialInst.NT.HW.AddReg]

HKR,,"LowerFilters",0x00010000,"serial"

HKR,,"MultiportDevice",0x00010001,0

HKR,,"SerialRelinquishPowerPolicy",0x00010001,1

[SerialEventLogInst]

AddReg = SerialEventLogAddReg

[SerialEventLogAddReg]

HKR,,EventMessageFile,0x00020000,"%%SystemRoot%%\System32\IoLogMsg.dll;%%SystemRoot%%\System32\drivers\serial.sys"

HKR,,TypesSupported,0x00010001,7

; -------------- Serial Port Driver install sections

[SerialServiceInst]

DisplayName = %Serial.SVCDESC%

ServiceType = 1 ; SERVICE_KERNEL_DRIVER

StartType = 3 ; SERVICE_DEMAND_START

ErrorControl = 0 ; SERVICE_ERROR_IGNORE

ServiceBinary = %12%\serial.sys

LoadOrderGroup = Extended base

;

; Source file information

;

[SourceDisksFiles]

; Files for disk Touchkit Touchscreen Controller. Installation Disk #1 (Mouse)

egxpen.sys = 1,,

;serial.sys = 1,,

[Strings]

eGalax="eGalax, Inc."

DiskId1 = "Touchkit. Driver Installation Disk(TouchScreen)"

ACPI\egxpen.DeviceDesc="eGalax Resistive Touch Digitizer"

egxPen.SVCDESC="eGalax Resistive Touch HID Driver"

Serial.SVCDESC="Serial Port Driver"

                                                                          Thanks a lot for your time & patience!

Unforunately that does not help us. Via's windows and unix drivers are fundamentally different bits of code.

Hi there,

I have been doing some research on the instillation process of ubuntu 10.10 by usb flash drive onto my umpc. I have noticed that

when I go through this process I am not given the option to use safe graphics mode when F4 is pressed. the only options that are

given are "Normal or cd with drivers or OEM! Any feedback on this would be a great help.

                                                                                         Thanks for your time!