Still no luck with AHCI!
Installing 2.6.30 Kernel or adding libata.noacpi=1 didn't helped at all...
I'm still wondering what to do...
Still no luck with AHCI!
Installing 2.6.30 Kernel or adding libata.noacpi=1 didn't helped at all...
I'm still wondering what to do...
A common mistake, AHCI is not ACPI.
If you want to turn off AHCI you can do that in the BIOS (set to IDE mode). Running in IDE mode will decrease disk performance a bit, but at least you have a functional laptop till the AHCI issue is sorted.
Oh, you might want to check what version your BIOS is. Acer released a new BIOSes for the timelines that fix some bugs (though I think they had to do with power management, read ACPI )
I was reading a bit to prepare installing ubuntu on my 3810T 944G32N (I hope it arrives tomorrow, but it will probably be monday or tuesday) and I found these 2 pages which link back to the (more) relevant posts in this thread.
https://launchpad.net/~acertimeline
http://linux-macbook-air-killers.blo...-timeline.html
Ok, now we've got a working issue with AHCI problem!!!
The solution is adding to kernel string "libata.force=noncq" (could be done by editing /boot/grub/menu.lst file). This disables NCQ hdd mode but working fine on my 3810T in AHCI mode.
Besides, some guys advised to install 2.6.30 kernel but it didn't worked for me (no matter what: 2.6.28, 2.6.30 or 2.6.31). Also there was a solution by editing initramfs, but it had no results for me too ((
So, just add libata.force=noncq to kernel string!
This solution was tested on Jaunty and Netbook Remix, so enjoy!
I've made a page on the Ubuntu Community Wiki:
Still a WIP, but it might make it easier for people to find out how to setup a Timeline computer. Feel free to contribute
http://help.ubuntu.com/community/AspireTimeline
Here is a report from cyberfish for Ubuntu Karmic Alpha 3:
https://lists.launchpad.net/acertimeline/msg00085.htmlI just installed alpha 3 (since my alpha 2 died when my computer crashed in the middle of a apt-get upgrade), and there are still a few problems.
- with 2.6.31-3-generic, hibernate still works, and suspend still doesn't work. Still haven't found any clue as to why.
- "sudo update-grub2" is needed after installation to find the Vista partition and add it to GRUB. This is a known bug. https://bugs.launchpad.net/ubuntu/+s...b2/+bug/402795
- Intel Wireless doesn't work out of the box anymore. The problem seems to be related to RFKILL framework change in 2.6.31 (http://www.h-online.com/open/Kernel-...--/news/113670). The RFKILL status seems to default to on (wireless disabled) on boot every time (btw, for those that don't know already, to toggle wireless, touch the wireless indication light). I have tried using the RFKILL utility found here - http://wireless.kernel.org/en/users/...ntation/rfkill, to no avail. The wifi device is "hard blocked". It seems like at least HP and Asus people are having problems with their laptops, too, but I didn't investigate into that further. The problem COULD be related to the acer_wmi module.
I didn't and still don't need any special kernel parameter since I have the SSD version, so I can't say if that's "fixed".
Everything else seems to work just like in alpha 2.
Hello All,
I installed Jaunty on my 3810T with dual core CPU and updated the kernel to 2.6.30 and the BIOS to 1.08
Almost all works well, except for the Suspend issue and I also seem to have a problem with the Cpu Frequency Scaling. Some of you reported running their systems at 800 Mhz, But unfortunately I seem to be unable to get below 1.2 Ghz; neither does it show up in the applet (yes I did try on-demand and it did not pop up).
andxxx@yyy:~$ sudo cpufreq-info
cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006
Report errors and bugs to cpufreq@lists.linux.org.uk, please.
analyzing CPU 0:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 0
hardware limits: 1.20 GHz - 1.40 GHz
available frequency steps: 1.40 GHz, 1.40 GHz, 1.20 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1.20 GHz and 1.40 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.20 GHz (asserted by call to hardware).
cpufreq stats: 1.40 GHz:0.00%, 1.40 GHz:0.00%, 1.20 GHz:0.00% (417)
analyzing CPU 1:
driver: acpi-cpufreq
CPUs which need to switch frequency at the same time: 1
hardware limits: 1.20 GHz - 1.40 GHz
available frequency steps: 1.40 GHz, 1.40 GHz, 1.20 GHz
available cpufreq governors: conservative, ondemand, userspace, powersave, performance
current policy: frequency should be within 1.20 GHz and 1.40 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency is 1.20 GHz (asserted by call to hardware).
cpufreq stats: 1.40 GHz:0.00%, 1.40 GHz:0.00%, 1.20 GHz:0.00% (448)
Strange enough I seem to have a 1.401 Ghz CPU state, but no 800 mhz state ???xxx@yyy:~$ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies
1401000 1400000 1200000
1401000 1400000 1200000
Does someone have a similar issue, or even better .... a solution ?
Cheers !
If you're bold enough you could try editing the /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies and /sys/devices/system/cpu/cpu1/cpufreq/scaling_available_frequencies files to
orCode:1400000 1200000 1000000 800000
On the other hand, the trick might be editing /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq and /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq.Code:1400000 1200000 800000
Or, who knows, you might need to edit all 4 files.
At the moment I can't test it yet, my 3810 (with SU9400 also) should arrive tomorrow
That would be great! I'll be adding all I know.Originally Posted by antikristian
Not that I am aware of. I would do it myself... but I'm not familiar with the bug reporting system. We don't even know which package is responsible for this (probably the kernel, though).Has anyone filed a bug about this?
Are you sure that would be a good idea?
Both the SU3500 (which I have) and the SU9400 run on 200mhz FSB (quad-pumped to 800mhz), with a max multiplier of 7 (200x7 = 1.4ghz). As far as I have seen, the lowest multiplier any Intel CPU can do is 6, which makes 1.2ghz (200x6). To achieve anything lower than 1.2ghz, one would have to lower the FSB, which gets problematic (it's not just the CPU anymore, but also the motherboard, memory sub-system, and potentially PCI, PCI-E, since they all run on a ratio to FSB).
Bookmarks