Finally I have solved the compile issues of acerhk.
Solution - Makefile changes:
1) turn 'CFLAGS=' to 'EXTRA_CFLAGS='
2) add 'V ?= 0'
3) add the following to the acerhk.ko compile line:
M=$(CURDIR) V=$(V)
That means that for the latest version of fsca16xx.sh, when pressing the wireless button, the Activate/De-Activate notifications work again (been broken for a little less then a year).
I also published it on launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/53953/comments/25
Friday, June 13, 2008
Saturday, May 24, 2008
acer_acpi fork state
The acer_acpi fork I made which has the framework for key pulling through ACPI, have worked on Gutsy but stopped working in Hardy. I am in the midst of my investigation.
Hopefully I will find out why soon.
Hopefully I will find out why soon.
Hardy & ATI
I finally achieved 3D with the open-source radeon driver on my Amilo (which have the Xpress 200M). I've been using it for the last two weeks with full compiz and by now only came upon several minor issues:
1) After resume from hibernation, the window shadows become garbled with green and red lines.
2) When starting Firefox, it will start full screened. Pressing F11 twice while in the address bar return Firefox to it's normal size.
3) Flash is slow. Solved by installing the Flash 10 beta, still consumes a lot of cpu, but works better.
I've used Ubuntu Hardy with the following repositories:
1) 'deb http://ppa.launchpad.net/tormodvolden/ubuntu hardy main' - supplied the git ATI driver.
2) 'deb http://ppa.launchpad.net/xorg-edgers/ubuntu hardy main' - supplied the git libdrm2. don't use the mesa from there as it does not works with compiz (white screen).
3) 'deb http://ppa.launchpad.net/stikonas/ubuntu hardy main' - supplied the git mesa.
Beside the packages I added to the device section in xorg.conf:
1) After resume from hibernation, the window shadows become garbled with green and red lines.
2) When starting Firefox, it will start full screened. Pressing F11 twice while in the address bar return Firefox to it's normal size.
3) Flash is slow. Solved by installing the Flash 10 beta, still consumes a lot of cpu, but works better.
I've used Ubuntu Hardy with the following repositories:
1) 'deb http://ppa.launchpad.net/tormodvolden/ubuntu hardy main' - supplied the git ATI driver.
2) 'deb http://ppa.launchpad.net/xorg-edgers/ubuntu hardy main' - supplied the git libdrm2. don't use the mesa from there as it does not works with compiz (white screen).
3) 'deb http://ppa.launchpad.net/stikonas/ubuntu hardy main' - supplied the git mesa.
Beside the packages I added to the device section in xorg.conf:
Option "EnablePageFlip" "1"
Option "ColorTiling" "1"
Option "AccelMethod" "EXA"
Option "DynamicClocks" "on"
Option "EXANoOffscreenPixmaps" "true"
Wednesday, March 26, 2008
Hardy Beta is now supported - fsca16xx
Last night I've pushed Ubuntu Hardy beta support to the installation script.
For those of you that use hibernation -
Currently, the wireless will not resume correctly, so after resuming, you should run the following lines to make it work:
In the following weeks I'll make the script do that automagically on resume.
For those of you that use hibernation -
Currently, the wireless will not resume correctly, so after resuming, you should run the following lines to make it work:
sudo rmmod ath_pci ath_rate_sample ath_hal
sudo modprobe ath_pci
In the following weeks I'll make the script do that automagically on resume.
Thursday, February 14, 2008
some updates for the fujitsu script
I've just made some updates to the fujitsu auto installation script. Its not "the" update I wanted to do, just some fixes.
Changes:
* use of newest atheros instead of ndiswrapper (should support AR5007).
I did not had time to get into the "add the missing bits to acerhk so that it will properly read the wireless led state".
Changes:
* use of newest atheros instead of ndiswrapper (should support AR5007).
I did not had time to get into the "add the missing bits to acerhk so that it will properly read the wireless led state".
Friday, December 14, 2007
On the tip of a plastic spring
First, let me say BAHHHH!!!!
Now, my Amilo's touchpad left button has stopped working - it even sounds physically broken... Anyway, the technicians at store of which I bought this laptop from said:"This was caused by improper use so warranty is the null and void".
Unhappy, I've decided to take it to my own hands. In order to check it out I had to almost strip the laptop entirely. I mean, the only 2 thing that were left complete were the motherboard to the bottom panel and the screen which was just seperated as is from the rest of the machine.
I was amazed to find out that I had 3 broken plastic springs which are suppose to place both of the buttons in place: 2 broken on the left button an 1 on the right button. More then that, I found out that a plastic spring was completely missing as if it was never there. Some further investigation showed me that it was truly never there and the lack of it was the reason that it broke in the first place! It was designed to take the pressure but in order to lower the manufacturing costs this stabilizer spring has just been left out + reassuring the purchase of a newer model when the old has supposedly become cripple.
BAHHHHH!!!!! When I'll have some free time (probably in 4 months from now), I'll install some real springs below the buttons - that should be suffice to make it last for at least 2 more years.
Now, my Amilo's touchpad left button has stopped working - it even sounds physically broken... Anyway, the technicians at store of which I bought this laptop from said:"This was caused by improper use so warranty is the null and void".
Unhappy, I've decided to take it to my own hands. In order to check it out I had to almost strip the laptop entirely. I mean, the only 2 thing that were left complete were the motherboard to the bottom panel and the screen which was just seperated as is from the rest of the machine.
I was amazed to find out that I had 3 broken plastic springs which are suppose to place both of the buttons in place: 2 broken on the left button an 1 on the right button. More then that, I found out that a plastic spring was completely missing as if it was never there. Some further investigation showed me that it was truly never there and the lack of it was the reason that it broke in the first place! It was designed to take the pressure but in order to lower the manufacturing costs this stabilizer spring has just been left out + reassuring the purchase of a newer model when the old has supposedly become cripple.
BAHHHHH!!!!! When I'll have some free time (probably in 4 months from now), I'll install some real springs below the buttons - that should be suffice to make it last for at least 2 more years.
Tuesday, December 4, 2007
acpi acer hotkey pooler for my amilo
Recently I've started a fork of the acer_acpi kernel module to also pool the 3 hotkeys.
On another note, the patch I've made for acerhk was finally entered the mainstream.
I've moved on to acer_acpi since it supports 64bit distros as well.
I'm up to my ears in homeworks and projects (last year to end my undergraduate degree - yeppieee) so it will probably go gold by May 08.
Work notes:
1) listen for _Q10 (wireless key) event - after it is done, also add the browser and fancy fan buttons.
2) rig the wireless button to run the wireless activation/deactivation method in acer_acpi
3) ask for merge and go mainstream.
some of (1) has already been done.
This will also make the lives of Amilo LI1718 owners much easier...
UPDATE 8/12/07: current work is posted on http://fscamiloa16xx.googlecode.com/svn/trunk/acer_acpi_hkey/
The AML Method PHSR change the values of INF (button id) ,BCMD (0x8B = button pressed) and SMIC (0x00/0xff). When loading this module with debug=4 and press one of the 3 buttons, you'll see (in dmesg) that it sensed the key press. Bad news, SMIC is not updated to 0 as expected and therefore it will act as if the button is being pressed over and over again. Some mutexes are MIA and should be added. acpi-devel list seems to be inactive - so I'll keep searching for a way to acquire an AML mutex...
On another note, the patch I've made for acerhk was finally entered the mainstream.
I've moved on to acer_acpi since it supports 64bit distros as well.
I'm up to my ears in homeworks and projects (last year to end my undergraduate degree - yeppieee) so it will probably go gold by May 08.
Work notes:
1) listen for _Q10 (wireless key) event - after it is done, also add the browser and fancy fan buttons.
2) rig the wireless button to run the wireless activation/deactivation method in acer_acpi
3) ask for merge and go mainstream.
some of (1) has already been done.
This will also make the lives of Amilo LI1718 owners much easier...
UPDATE 8/12/07: current work is posted on http://fscamiloa16xx.googlecode.com/svn/trunk/acer_acpi_hkey/
The AML Method PHSR change the values of INF (button id) ,BCMD (0x8B = button pressed) and SMIC (0x00/0xff). When loading this module with debug=4 and press one of the 3 buttons, you'll see (in dmesg) that it sensed the key press. Bad news, SMIC is not updated to 0 as expected and therefore it will act as if the button is being pressed over and over again. Some mutexes are MIA and should be added. acpi-devel list seems to be inactive - so I'll keep searching for a way to acquire an AML mutex...
Subscribe to:
Posts (Atom)