The Long awaited Ubuntu Install Guide (based on a Gutsy Gibbon installation)

diJenerate
Senior Member
Posts: 119
Joined: Fri Jul 13, 2007 14:29

The Long awaited Ubuntu Install Guide (based on a Gutsy Gibbon installation)

Postby diJenerate » Thu Oct 11, 2007 22:15

First of... this guide is just that... a guide. You take full responsibility for the results (negative or positive) derived from executing any steps below.

Second... I have not done an x86_64 install on a Core2 based UX so I am only assuming functionality on those is the same. If anyone wants to donate a UX92/S or UX490N/C for me to test the install on, I'll be happy to do said tests and update this guide accordingly.

Third... The best place by far to get your UX is still Dynamism.

Last of all... The guide!

Ok... on with the show:

NB. if you are already running Feisty Fawn (7.04) and want to upgrade, as sev7en pointed out (as I missed it the first pass) you can update your repositories by running in terminal

Code: Select all

sudo apt-get update


followed by

Code: Select all

sudo apt-get dist-upgrade -y -f


If however you are doing a clean installation, after creating your Windows boot disks using the Vaio utility...

1. Install Gutsy on your system via an external bootable optical drive. from the usual sources (or you may try ubuntustudio for its quicker pickup and built-in multimedia support as recommended by sev7en - beware the rt kernel!). This applies to both Ubuntu, (gnome based) and Kubuntu (kde based) variants. As I am a KDE fan, I am running Kubuntu on my UX and as it is not as popular as the gnome based variant and often neglected, I will be providing these steps from the perspective of the KDE user.

2. You don't need more than 2GB for swap as these babies don't yet come with more than 1GB of (shared with video) RAM. After your first boot, you won't have a working touch screen, cameras, fingerprint reader, WWAN (for US models) or possibly WLAN. You will also not have any control over your backlight.

3. If you selected auto-login during installation, logout now. If you are at the login-screen, select CTRL+Fn+Alt+F1 to go to the first Virtual console. Login with your regular username and password then type the command

Code: Select all

sudo su

hit the return key then type your root password (should be the same as your own). Next type

Code: Select all

killall kdm


This ends the Xwindow session. If you end up at a blank screen with a flashing cursor, select CTRL+Fn+Alt+F1 again.

Next type

Code: Select all

startx

and you should see KDE start up and logging in.
If you have gotten this far, congratulations. The hard work now begins.

4. First let's enable the WLAN and get some better display drivers than you currently have. By default you should be running either VESA or i810 display drivers. If you want to play any 3D games you'll need a bit more power than those will give you. You will need to launch the Adept Manager found at:

KMenu->System->Adept Manager - Manage Packages

In Adept Manager you'll need to make sure you have installed all updates available to ensure you have the latest kernel version. After this is complete, you'll need to make sure you have installed:
1. restricted-manager (you can search for this)
2. linux-restricted-modules-VERSION.THAT.MATCHES.YOUR.RUNNING.KERNEL

After installation has completed restart your Vaio and repeat Step 3 above. As root go to:
KMenu->System->Konsole - Terminal Program
and type

Code: Select all

restricted-manager


When the window launches, ensure that the Intel(R) PRO/Wireless 3945 Network Connection Driver for Linux is enabled.

Next let's get some improved video performance.
Launch Adept Manager
KMenu->System->Adept Manager - Manage Packages

Search for xserver-xorg-video-intel and xserver-xorg-input-evtouch make sure these packages are installed
Then search for kate and make sure this package is also installed
Next launch
KMenu->System->Konsole - Terminal Program
and type:

Code: Select all

cp /etc/X11/xorg.conf /etc/X11/xorg.conf.backup

next type

Code: Select all

kate /etc/X11/xorg.conf


In the window that opens, you will need to select/highlight the entire all the text and delete it. Ensure that all text is gone an copy and paste the following into its place:

Code: Select all

# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades [B]only[/B]
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
        FontPath        "/usr/share/fonts/X11/misc"
        FontPath        "/usr/X11R6/lib/X11/fonts/misc"
        FontPath        "/usr/share/fonts/X11/cyrillic"
        FontPath        "/usr/X11R6/lib/X11/fonts/cyrillic"
        FontPath        "/usr/share/fonts/X11/100dpi/:unscaled"
        FontPath        "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
        FontPath        "/usr/share/fonts/X11/75dpi/:unscaled"
        FontPath        "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
        FontPath        "/usr/share/fonts/X11/Type1"
        FontPath        "/usr/X11R6/lib/X11/fonts/Type1"
        FontPath        "/usr/share/fonts/X11/100dpi"
        FontPath        "/usr/X11R6/lib/X11/fonts/100dpi"
        FontPath        "/usr/share/fonts/X11/75dpi"
        FontPath        "/usr/X11R6/lib/X11/fonts/75dpi"
        # path to defoma fonts
        FontPath        "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
        Load    "i2c"
        Load    "bitmap"
        Load    "ddc"
        Load    "dri"
        Load    "extmod"
        Load    "freetype"
        Load    "glx"
        Load    "int10"
        Load    "type1"
        Load    "synaptics"
        Load    "vbe"
EndSection

Section "InputDevice"
        Identifier      "Generic Keyboard"
        Driver          "kbd"
        Option          "CoreKeyboard"
        Option          "XkbRules"      "xorg"
        Option          "XkbModel"      "pc105"
        Option          "XkbLayout"     "us"
EndSection

Section "InputDevice"
        Identifier      "Configured Mouse"
        Driver          "mouse"
        Option          "CorePointer"
        Option          "Device"                "/dev/input/mice"
        Option          "Protocol"              "ImPS/2"
        Option          "Emulate3Buttons"       "true"
EndSection

Section "InputDevice"
        Identifier      "Synaptics Touchpad"
        Driver          "synaptics"
        Option          "SendCoreEvents"        "true"
        Option          "Device"                "/dev/psaux"
        Option          "Protocol"              "auto-dev"
        Option          "LeftEdge"              "120"
        Option          "RightEdge"             "830"
        Option          "TopEdge"               "120"
        Option          "BottomEdge"            "650"
        Option          "FingerLow"             "14"
        Option          "FingerHigh"            "15"
        Option          "MaxTapTime"            "200"
        Option          "MaxTapMove"            "110"
        Option          "EmulateMidButtonTime"  "75"
        Option          "VertScrollDelta"       "20"
        Option          "HorizScrollDelta"      "20"
        Option          "MinSpeed"              "0.3"
        Option          "MaxSpeed"              "0.75"
        Option          "AccelFactor"           "0.015"
        Option          "EdgeMotionMinSpeed"    "200"
        Option          "EdgeMotionMaxSpeed"    "200"
        Option          "UpDownScrolling"       "1"
        Option          "CircularScrolling"     "1"
        Option          "CircScrollDelta"       "0.1"
        Option          "CircScrollTrigger"     "2"
        Option          "SHMConfig"             "on"
EndSection

Section "InputDevice"
        Identifier      "touchscreen"
        Driver  "evtouch"
        Option  "Device"        "/dev/input/gunze"
        Option  "DeviceName"    "touchscreen"
   Option   "MinX" "32"
   Option   "MaxX" "992"
   Option   "MinY" "38"
   Option   "MaxY" "968"
        Option  "SwapY"         "0"
        #Option "SwapXY"        "1"
        Option  "ReportingMode" "Raw"
        Option  "Emulate3Buttons"
        Option  "Emulate3Timeout"       "50"
        Option  "SendCoreEvents"
   #Option   "Calibrate"   "1"
EndSection

# INTERNAL
Section "Device"
        Identifier      "Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller"
        Driver          "intel"
        BusID           "PCI:0:2:0"
#       Option          "MonitorLayout" "TV,LFP"
        Option          "MonitorLayout" "NONE,CRT+LFP"
#       Option          "MonitorLayout" "CRT,LFP"
#       Option          "Clone"         "true"
        Option          "XAANoOffscreenPixmaps" "true"
        Screen          0
EndSection

Section "Monitor"
        Identifier      "Internal Monitor"
        Option          "DPMS"
EndSection

Section "Screen"
        Identifier      "Internal Screen"
        Device          "Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller"
        Monitor         "Internal Monitor"
        DefaultDepth    24
        SubSection "Display"
                Depth           24
                Modes           "1024x600" "800x600"
        EndSubSection
EndSection

# EXTERNAL
Section "Device"
        Identifier      "Intel 945GM/GMS/940GML Express External"
        Driver          "intel"
        BusID           "PCI:0:2:0"
        Option          "MonitorLayout" "CRT,LFP"
#       Option          "Clone"         "true"
        Option          "DevicePresence"        "true"
        Screen          1
EndSection

Section "Monitor"
        Identifier      "External Monitor"
        Option          "DPMS"
EndSection

Section "Screen"
        Identifier      "External Screen"
        Device          "Intel 945GM/GMS/940GML Express External"
        Monitor         "External Monitor"
        DefaultDepth    24
        SubSection "Display"
                Depth           24
                Modes           "1280x1024" "1024x768" "800x600" "640x480"
        EndSubSection
EndSection

# TV
Section "Device"
        Identifier "TV"
        Driver  "intel"
        Option  "MonitorLayout" "TV,NONE"
        Option  "TVStandard"    "PAL-B"
        Option  "TVOutFormat"   "COMPOSITE"
#       Option  "Clone"         "true"
#       Option  "ConnectedMonitor"      "TV"
        Option  "DevicePresence"        "true"
#       Screen  1
        BusID   "PCI:0:2:0"
EndSection

Section "Monitor"
        Identifier      "TV"
        HorizSync       30-50
        VertRefresh     60
EndSection

Section "Screen"
        Identifier      "TV"
        Device          "TV"
        Monitor         "TV"
        DefaultDepth    24
        SubSection "Display"
                Depth   24
                Modes   "1024x768" "800x600" "640x480"
        EndSubSection
EndSection

# SERVER LAYOUT
Section "ServerLayout"
   InputDevice   "touchscreen"   "SendCoreEvents"
        Identifier      "Default Layout"
        Screen          0 "Internal Screen"
#       Screen          1 "External Screen" LeftOf "Internal Screen"
#       Screen          0 "TV"
        InputDevice     "Generic Keyboard"
        InputDevice     "Configured Mouse"
        InputDevice     "Synaptics Touchpad"
EndSection

Section "DRI"
        Mode    0666
EndSection

Section "Extensions"
        Option "Composite" "enable"
EndSection

#Section "ServerFlags"
#       Option  "Xinerama"      "true"
#EndSection


Save this file overwriting the old file and exit kate.

Back at console type

Code: Select all

kate /etc/udev/rules.d/60-symlinks.rules


In the open file add the following lines below the lines about # Compatibility symlinks for /dev/scd* devices:

Code: Select all

#Touch Panel compatibility
SUBSYSTEMS=="input", KERNEL=="event*", ATTRS{name}=="GUNZE USB Touch Panel", SYMLINK+="input/gunze"


Again save and exit and back at console, type

Code: Select all

sudo locate -u && for i in $(locate lcd-???-brightness); do sudo cp $i $i.bak; sudo sed -i '1 s|#!/bin/sh|#!/bin/bash|g' $i; done


lastly type

Code: Select all

kate /etc/modules


and add

Code: Select all

sony_acpi


to the list of modules

now, restart the system.


5. Ok now you have better graphics, and surprise touch screen and backlight support! You may log on as your regular user through the GUI interface this time.

You've probably noticed I haven't mentioned sound as one the things not working, that's because sound is working... it's just turned down. The UX has a mono speaker array on the body of the unit and all you have to do is tap that little speaker in your task bar, launch Kmix and raise the volume for the mono controls.


As far as the cameras go... well first things, it's actually one camera with 2 CCDs. The driver can be found by first adding the Arakhnê.org repo to your sources.list file. Instructions can be found here.

Then you'll need to update your list by launching

KMenu->System->Konsole - Terminal Program

and typing:

Code: Select all

sudo apt-get update


Then launch Adept Manager

KMenu->System->Adept Manager - Manage Packages

Search for ricoh-webcam-r5u870 matching your running kernel

and then install it.

So far noone has been able to figure out how to get the Camera to switch CCDs on demand under linux. Until this is achieved, linux users only get Webcam support. :(


6. Progress has been made with the support for Sony's BIOS and hardware subsystem. To ensure you have support (and of course you must be running kernel 2.6.22+) you'll need to ensure the sony_laptop (thanks Mattia Dongili) module is running, not the deprecated sonypi. For this you'll need to go to console and type

Code: Select all

sudo kate /etc/init.d/hotkey-setup


search for the line:

Code: Select all

modprobe sonypi; # Needed to get hotkey events


and change it (by commenting out the sonypi) to

Code: Select all

modprobe #sonypi; # Needed to get hotkey events


reboot.

We can turn on the WWAN module (USB serial modem) of the US model...

Code: Select all

sudo su


Code: Select all

 echo 1 > /sys/devices/platform/sony-laptop/wwanpower
to power on and

Code: Select all

 echo 0 > /sys/devices/platform/sony-laptop/wwanpower
to power off...

now after powering the modem on, run this command to find its vendor and product IDs:

Code: Select all

lsusb


the line of interest here should read something like:

Code: Select all

Bus 004 Device 007: ID 0fce:d019 Sony Ericsson Mobile Communications AB


it may not be exactly the same on your unit but the characters after ID in the above example

Code: Select all

0fce:d019


are what we want.

Run the following command:

Code: Select all

sudo kate /etc/modules


and add the line

Code: Select all

usbserial vendor=0x[B]XXX[/B] product=0x[B]XXXX[/B]


where if you ID was as above you would replaces the sets of Xs with fce and d019 respectively. creating the line

Code: Select all

usbserial vendor=0xfce product=0xd019


in your file.

Save the file and reboot. So long as long as you don't have any other USB serial devices attached, when you power up the modem, it should be at:

Code: Select all

/dev/ttyUSB0


so you can now create /dev/modem with

Code: Select all

sudo ln -s /dev/ttyUSB0 /dev/modem


and make it occur at each boot by adding this to the end of /etc/rc.local before the line exit0

Code: Select all

ln -s /dev/ttyUSB0 /dev/modem

exit 0


Feel free to use your WWAN with any GPRS/EDGE connection utility such as comgt and GPRS Easy Connect, treating the card like a Sony Ericsson GC75 or GC83.

It seems that the SonyEricsson VDC is quite possibly a GC83 on the USB bus... as it supports the 850MHz/1800MHz/1900MHz bands and behaves like the GC83 does. It also supports most of the AT commands supported by the GC75 making the GC75 AT reference Manual quite useful to us, at least until I can find the VDC/GC83 reference manual.

Mattia Dongili has just pointed me here where there is more information on use of the egprs/WWAN module. This will save you having to run minicom at each restart to enter your pin. Thanks Mattia, thanks Sergio.

Adaptation of Sergio's scripts for this installation would be as follows:

Edit /etc/udev/rules.d/60-symlinks.rules as before using the console

Code: Select all

sudo kate /etc/udev/rules.d/60-symlinks.rules


In the open file add the following lines below the lines we added before for the touchscreen:

Code: Select all

#Sony Ericsson EGPRS Radio initialization
BUS=="usb", SYSFS{idVendor}=="0fce", SYSFS{idProduct}=="d019", RUN+="/etc/udev/scripts/gprs_modem_setup.sh /dev/%k"


save this file then create /etc/udev/scripts/gprs_modem_setup.sh by typing

Code: Select all

sudo kate /etc/udev/scripts/gprs_modem_setup.sh


and in the empty file paste the following where if you have an enabled PIN on your SIM card, you should replace pin_code with it and uncomment that line:

Code: Select all

#!/bin/bash

echo $1;

/bin/echo -en "AT+CFUN=1,1\r\n" > $1

#/bin/echo -en "AT+CPIN=[B]pin_code[/B]\r\n" > $1


save the file then set its execution bit with

Code: Select all

sudo chmod a+x /etc/udev/scripts/gprs_modem_setup.sh




Note I
For those having WLAN issues, like not being able to connect to WPA2 encrypted networks etc, have a look here.

Note II
If you have no memorystick support and inserting a memorystick gives you this when you check dmesg

Code: Select all

tifm_ms: Unknown symbol tifm_has_ms_pif


you will need to update your driver and memorystick subsystem.

at a terminal type

Code: Select all

svn co http://svn.berlios.de/svnroot/repos/tifmxx/trunk/driver/


then

Code: Select all

cd driver


Code: Select all

make


Code: Select all

sudo make install


restart your UX.


Note III
As under windows, you will need to have your WWAN module unlocked if you want to use it on a carrier other than AT&T. You can use minicom to issue the commands under linux and it's installed by typing the following at a shell:

Code: Select all

sudo apt-get install minicom


then simply issue the command

Code: Select all

minicom


at the minicom prompt type

Code: Select all

AT

which should give you the response

Code: Select all

OK

then type

Code: Select all

 AT+CLCK=PN,0,[B]XXXXXXXX[/B]

(where the XXXXXXXXs are the unlock code for your Vaio provided by Sony support) which should produce another

Code: Select all

OK


at which point you can press Ctrl+X followed by Z then X to exit minicom.



Note IV
For those with an irritating super-sensitive pointer, you can disable tap/click by first editing the line in your xorg.conf file under Section "InputDevice":

Code: Select all

Option          "MaxTapTime"            "180"


changing it to:

Code: Select all

Option          "MaxTapTime"            "0"



Then you'll have to download the latest Synaptics TouchPad driver for XOrg/XFree86 and see the included README.alps file for instructions on patching your kernel to support disabling the tap/click functions of the pointer.

For those who still want click-to-drag but just with less sensitivity, MrMuzz has suggested tweaking this value to get your personal optimal performance by trying values of 180 or higher.


Note V

If when using your GPRS/EDGE service you can only stay connected for about a minute or two at a time and your /var/log/messages shows an error which looks something like this:

Code: Select all

No response to 4 echo-requests
Serial link appears to be disconnected.
Connect time 2.0 minutes.
Sent 13102 bytes, received 27004 bytes.
Connection terminated.


You may need to edit your /etc/ppp/options file. Find the line:

Code: Select all

lcp-echo-failure [B]X[/B]

and replace the X with 0.


Now what's left...

1. Biometric Reader which requires that we either flash its controller with standard firmware or find Sony's custom firmware's key.

2. The zoom+/zoom-, Vaio launcher & camera capture buttons which all report the same event on keypress. Sony's windows driver either uses a little help from the BIOS or measures the length of time the event lasts to tell which button was pressed. If someone is willing to write a small piece of code to test this it may be possible to get these mapped as individual buttons, not just one button in several places.

3. Switching between CCDs on the Camera. Again the BIOS helps the windows driver along.


To be continued...

Credits to: benz145, Mattia Dongili, xenoph0be on the ubuntu forums, Alexander Sack, sev7en, Tymoteusz Rogalewski, Sergio, Riyan Mynuddin, MrMuzz... (more to come)

diJenerate

User avatar
Benz145
Senior Member
Posts: 2383
Joined: Thu Sep 14, 2006 04:06
Contact:

Postby Benz145 » Fri Oct 12, 2007 00:42

Nice work, I'll sticky this. You might consider making a list of non-working hardware so people who want to install can see what is/isn't working. Also, can anyone say if Ubuntu gets better battery life than XP? I'd love a super stripped down version of Linux that would be much more energy efficient.

User avatar
sev7en
Senior Member
Posts: 599
Joined: Sun Mar 04, 2007 23:27
Location: Italy
Contact:

Postby sev7en » Mon Oct 29, 2007 07:08

Great works! Just a tips... after the update of repositories, via console, do also an apt-get dist-upgrade -y -f command: as you know the first updates the archive, the second applies the new software packages (-y -f forces the update and do a automatic confirm for any request about the dipendencies).
[color="Red"]Sony VAIO VGN-UX91S - 03.04.07[/color]
[color="Orange"] OS - Windows 7 Build 7000 || iPC OSX Leopard Uni 10.5.6 || Project Fedora 10 [/color]
[color="White"]MacBook Pro 17" C2D 2.33GHz ||
Nokia N93 || HTC TouchHD [/color]
--------
[color="DarkRed"]|||[/color] Full Guide: Sony Vaio UX MacOS X Installation Guide & HowTo
[color="DarkRed"]|||[/color] Repo: Sony Vaio Series,Apple and...Cartoons Wallpapers!
[color="DarkRed"]|||[/color] Repo: "The Essential" For Any Mac User

User avatar
sev7en
Senior Member
Posts: 599
Joined: Sun Mar 04, 2007 23:27
Location: Italy
Contact:

Postby sev7en » Mon Oct 29, 2007 07:21

P.S: Just another suggest... instead to install the Ubuntu, get directly the UbuntuStudio v7.10: this version has been shipped with LowLatency kernel and sports better performance than the original Gutsy Gibbon (atm the repository give you the ability to install other patch, e.g. RT, but not this version of kernel).


Cheers,
[color="Red"]Sony VAIO VGN-UX91S - 03.04.07[/color]

[color="Orange"] OS - Windows 7 Build 7000 || iPC OSX Leopard Uni 10.5.6 || Project Fedora 10 [/color]

[color="White"]MacBook Pro 17" C2D 2.33GHz ||

Nokia N93 || HTC TouchHD [/color]

--------

[color="DarkRed"]|||[/color] Full Guide: Sony Vaio UX MacOS X Installation Guide & HowTo

[color="DarkRed"]|||[/color] Repo: Sony Vaio Series,Apple and...Cartoons Wallpapers!

[color="DarkRed"]|||[/color] Repo: "The Essential" For Any Mac User

diJenerate
Senior Member
Posts: 119
Joined: Fri Jul 13, 2007 14:29

Postby diJenerate » Sun Nov 04, 2007 14:29

sev7en wrote:P.S: Just another suggest... instead to install the Ubuntu, get directly the UbuntuStudio v7.10: this version has been shipped with LowLatency kernel and sports better performance than the original Gutsy Gibbon (atm the repository give you the ability to install other patch, e.g. RT, but not this version of kernel).


Cheers,


Sev7en: with the rt kernel I have no suspend to RAM or disk and without recompiling the driver
no webcam.... I'm running studio with the generic kernel now.

diJenerate

diJenerate
Senior Member
Posts: 119
Joined: Fri Jul 13, 2007 14:29

Postby diJenerate » Mon Nov 05, 2007 13:05

benz145 wrote:Nice work, I'll sticky this. You might consider making a list of non-working hardware so people who want to install can see what is/isn't working. Also, can anyone say if Ubuntu gets better battery life than XP? I'd love a super stripped down version of Linux that would be much more energy efficient.



benz145: so far as non-working hardware goes... I'd prefer to consider it a 'progress-to-date' report.

So as of November 5th 2007,

The not-as-yet-functional-under-Ubuntu list reads:

- Front Panel +/- Zoom and Sony Launcher shortcut buttons
- Rear 1.3MP CCD of camera and camera capture button
- Biometric Reader (work in progress) but the biggest problem is Sony

So far as battery life goes... well under ubuntustudio 7.10 with 2.6.22-14-generic and with gnome, 50% backlight (gnome power management with 'idle auto dim' box checked), WWAN, Wiifi & BT on, compiz-fusion running and a 4GB MS Pro-Duo perpetually mounted, my UX280P gets about 1hr 23 mins before the gnome 'critical battery' warning (10% battery remaining) and warns of imminent hibernation (5%) at 1hr 27min on a standard battery (VGP-BPS6) that's almost a year old.... and yes I used a stop-clock.

Hope that helps.

diJenerate

MrMuzz
Senior Member
Posts: 54
Joined: Thu Dec 07, 2006 03:23

Postby MrMuzz » Tue Nov 20, 2007 21:39

Boredom drives me. I followed the guide, thanks!!! Everything works as described 'cept my ALPS stick tap sensitivity drives me nuts!!!! I've dug around the Ubuntu forums and tried a slew of things, no luck. I have a 280p and would love some help either here or via PM. I went the Gnome route but have also install the KDE desktop. I've tried some touchpanel GUI utils edits to xorg.conf and I'm just feelin' downright sad.

User avatar
Benz145
Senior Member
Posts: 2383
Joined: Thu Sep 14, 2006 04:06
Contact:

Postby Benz145 » Tue Nov 20, 2007 21:47

MrMuzz wrote:Boredom drives me. I followed the guide, thanks!!! Everything works as described 'cept my ALPS stick tap sensitivity drives me nuts!!!! I've dug around the Ubuntu forums and tried a slew of things, no luck. I have a 280p and would love some help either here or via PM. I went the Gnome route but have also install the KDE desktop. I've tried some touchpanel GUI utils edits to xorg.conf and I'm just feelin' downright sad.


Are you talking about the sensitivity of the push down click, or the actual movement speed?
Sony VAIO UX180 | Asus UX31E Ultrabook | iPhone 5S | Google Glass

Virtual Reality Blog
Personal Blog

Editor for:
UltrabookNews.com
Carrypad.com
UMPCPortal.com

MrMuzz
Senior Member
Posts: 54
Joined: Thu Dec 07, 2006 03:23

Postby MrMuzz » Tue Nov 20, 2007 23:28

push down.

User avatar
Benz145
Senior Member
Posts: 2383
Joined: Thu Sep 14, 2006 04:06
Contact:

Postby Benz145 » Wed Nov 21, 2007 01:31

I know someone posted a fix for it under Max OSX, but I'm not sure if that can be applied to Linux, here is the link for that thread -

http://micropctalk.com/forums/showthread.php?t=3152
Sony VAIO UX180 | Asus UX31E Ultrabook | iPhone 5S | Google Glass



Virtual Reality Blog

Personal Blog



Editor for:

UltrabookNews.com

Carrypad.com

UMPCPortal.com


Return to “Linux OS”

Who is online

Users browsing this forum: No registered users and 2 guests