first of all, thanks for to r4idei for his post it helped me a great deal!
I would like to add some details and experiences of my own
Originally Posted by
r4idei
Ok here i am... Im going to be short beacuse i dont have much time, but im not going on the moon so i will follow this thread
I will describe my experience with intrepid and samsung nc20
-Xorg live doesnt start, alternate doesnt boot. Solution: downloading compiling and installing latest openchrome to boot xorg and start installation.
-Afeter installing xorg doesnt start again (obviously). SOlution: same of above (if you are smart put drivers in a persisten partition)
a nice howto for the openchrome drivers can be found here:
https://help.ubuntu.com/community/Op...20Installation
However with openchrome, I could not get an external monitor to work
If anyone has a solution for this, please post it here!
if you don't need an external monitor or 3d accelration, you are probably better off with the openchrome driver. but if you plan to install the via drivers anyway, you might as well do that now: here is a quick step by step guide:
you first need some packages in order to be able to compile a kernel package (I am not sure if this list of packages is complete, since I had installed quite some packages before installing the via drivers please correct me, if anything is missing):
Code:
sudo apt-get install build-essential subversion autoconf automake1.9 libtool linux-headers-generic
get the drivers and the kernel module from http://linux.via.com.tw/support/downloadFiles.action. select OS: ubuntu 8.10 and Platform: VX800.
download the "unified gfx driver" and the "chrome DRM source for kernel 2.6.27"
now install the gfx driver:
Code:
tar zxvf ./5.74.33.85a-44597.tar.gz
cd ./5.74.33.85a-44597
sudo ./vinstall
sudo reboot
after this step, I had a running x system, but resolution and drm were not working.
to get drm working, I had to compile and install the DRM driver (this is from the readme):
Code:
2. For VIA CN896/VN896/VX800 chipset
(1) Copy drm-via_chrome9-2.6.27-85a-44411-src.tar.gz to your working directory
(2) Extract the package
# tar -zxf drm-via_chrome9-2.6.27-85a-44411-src.tar.gz
(3) Enter the directory and build the source
# cd drm-via_chrome9-2.6.27-85a-44411-src
# make
# sudo su -
(4) Backup the VIA chrome9 DRM module
# cd /lib/modules/'uname -r'/kernel/ubuntu/via_chrome9
# mv via_chrome9.ko via_chrome9.ko.bak
(5) Replace VIA DRM module by the new one
# cp ~/drm-via_chrome9-2.6.27-85a-44411-src/via_chrome9.ko /lib/modules/'uname -r'/kernel/ubuntu/via_chrome9/
# depmod -a
(6) Restart (not necessary just load the module)
# modprobe via_chrome9
(7) Check whether VIA chrome9 DRM module is loaded
# lsmod |grep via_chrome9
If you get the output as:
drm 86056 1 via_chrome9
that means the VIA chrome9 DRM module is successfully loaded.
Make sure the path of VIA DRM module is right.
# modinfo via_chrome9
The output should be like:
filename: /lib/modules/'uname -r'/kernel/ubuntu/via_chrome9/via_chrome9.ko
now I had to make some adjustments to my xorg.conf:
Code:
Section "Monitor"
Identifier "Monitor"
EndSection
Section "Screen"
Monitor "Monitor"
DefaultDepth 16
SubSection "Display"
Modes "1280x800"
Virtual 1280 1824
Depth 16
EndSubSection
Identifier "Default Screen"
Device "Configured Video Device"
EndSection
Section "Module"
Load "glx"
Load "dri"
Load "extmod"
EndSection
Section "DRI"
Group 0
Mode 0666
EndSection
Section "Device"
Driver "via"
VendorName "VIA Tech"
BoardName "via"
#Option "PanelID" "0" #640x480, Single, Dithering
Identifier "Configured Video Device"
Option "SWCursor" "TRUE"
Option "PanelID" "7"
EndSection
for some reason I needed to turn off the hardware cursor in order to be able to see the mouse cursor therefore the Option "SWCursor" "TRUE".
-NO CPU FREQUENCY SCALING! PANIC!! Solution: build module e_powersaver from kernel source
Strange things: loading module gives scaling from 850 to 1700.
loading, unloading, reloading gives from 800 to 1600 (same as windows)
BAD THINGS: compiling e_powersaver with 64bit kernel gave me a bunch of errors, im using 32 bit. I'it a shame but im optimistic for future kernels (maybe i was unlucky or/and not capable)
Edit: this is how I got it working:
You could reconfigure and compile a whole new kernel version. However there is a way to compile and install just the module:
first we need the kernel sources
Code:
sudo apt-get build-dep linux-image-$(uname -r)
apt-get source linux-image-$(uname -r)
now switch to the new source directory and configure the kernel:
Code:
cd ~/linux-2.6.27
make oldconfig
gedit .config
change "# CONFIG_X86_E_POWERSAVER is not configured" to "CONFIG_X86_E_POWERSAVER=m"
now we need the Module.symvers file from the linux-headers and then we can compile and install the modules (note: I'm not sure if fakeroot is really necessary but that's how I did it and how it worked):
Code:
cp /usr/src/linux-headers-2.6.27-11-generic/Module.symvers ~/linux-2.6.27/
make clean
fakeroot make prepare
fakeroot make M=arch/x86/kernel/cpu/cpufreq/
sudo cp arch/x86/kernel/cpu/cpufreq/*.ko /lib/modules/2.6.27-11-generic/kernel/arch/x86/kernel/cpu/cpufreq/
sudo depmod -a
sudo modprobe e_pwersaver
now, after a reboot, your frequency switching should be working just fine
Update: I also experienced the weird frequencies, which get fixed upon reloading the module e_powersaver.
I suspect that the frequencies that really get set are correct and just the reported frequencies are wrong.
The evidence for this is that the reported frequencies were 1.6 to 3.2 GHz and the system was running fine and did not even run as hot as before I installed e_powersaver.
This probably has something to do with when the module gets loaded during boot. So the proper fix would be to delay loading e_powersaver. However, I went for a workaround:
add the following lines to /etc/rc.local :
Code:
modprobe -r e_powersaver
modprobe e_powersaver
now the frequencies should be displayed correctly.
I deactivated the default drivers in System -> Administration -> Hardware
then I installed linux-backports-modules-intrepid.
Code:
sudo apt-get install linux-backports-modules-intrepid
activated the atheros 5xxxx drivers in System -> Administration -> Hardware
works like a charm!
-sound seems to work UPDATE: sound works without doing anything. Speakers mute when you plug earphones
One caveat: I could not get the internal microphone to work! Connecting a mic to the microphone jack works, but not the internal one. However, I haven't ever tried under windows, if there is an inernal mic behind this little hole in the screen, or if it is just a mock-up.
If anyone has gotten this to work, please let me know how (or if there is no mic built-in).
-suspend to ram works perfectly. I activated it via menu, the screen shuts down, the power led blinks, everything ok
in principle works for me, too but occasionally, the computer won't wake up any more with the openchrome drivers. don't know if this occurs with the via drivers, since I just installed those.
edit: I have been using the via drivers for quite some time now and never had problems. Also, the video playback acceleration works.
Concerning the webcam: It works out of the box. luvcview shows a nice image albeit just with 3
skype 2.0.0.79, seems to only use the top-right quarter of the image which is o.k. since my head fits in there, but it forces me to look at the screen from an angle. If anyone else has heard of this or knows a solution, please tell.
edit: for some reason, skype works fine now, not sure why (maybe just a reboot?)
Bluetooth works out of the box.
-Special keyboard keys seems to work. Volume up and down works. I didnt try sleep button :\. Brightness buttons dont work (**** i hate this thing, it should be hardware embebbed like my old notebook) but luckily you can use applets in gnome and in kde4 (FIUU!)
Thats all, forgive my shortness (uh?) and my english.
If anybody wants to open a wiki, it would be wonderful and ill partecipate
BTW: the machine is WONDERFUL. Everything runs REALLY smooth, i can live with poor 2d-3d drawing having wifi and sound perfectly workin
same here, I the only thing I am missing is the microphone, but that can be worked around using a bluetooth headset
Bookmarks