Thanks for this.  I just installed it, and it seems to be working fine.  Didn't time the boot sequence so I can't really tell if there was a difference.

Not sure I really gained anything, though, as everything was pretty much working already.  I thought this might make eee-control work for me, but it's still dying due to a missing /sys/devices/platform/eeepc/brn.

Also, I noticed that on my next update it pulled down an eeepc version of linux-headers for the old kernel version (2.6.27-4).  I doubt it will make any difference, but I didn't know if that was intended.  (I added the intrepid repository only.)

Hi Adam. Great work releasing this kernel. As long as you can hold off till this coming weekend - starting the 10th - I'll worry about updating the rt2860 to 1.8 so you don't have to, and will test with your kernel. Unfortunately I won't have time till then though. I'll let you know when I do!

coolos wrote:

How did you tranfer 8.10 beta ISO on a USB bootable key ?
Does it work with unetbootin, or isotousb.sh without tweaking ?
thanx

I used unetbootin.  Nothing special required at all.

incandenza wrote:

Thanks for this.  I just installed it, and it seems to be working fine.  Didn't time the boot sequence so I can't really tell if there was a difference.

If you install the bootchart package, it should provide some examples of boot times in /var/log/bootchart/
(You may need to rebuild generic and eeepc's initramfs though. Run "sudo dpkg-reconfigure linux-image-2.6.27-4-generic" and again for linux-image-2.6.27-5-eeepc.

Not sure I really gained anything, though, as everything was pretty much working already.  I thought this might make eee-control work for me, but it's still dying due to a missing /sys/devices/platform/eeepc/brn.

Ahh, in 2.6.27 the official upstream eeepc-laptop module has taken ownership of the brightness level and the wlan. The advantage is that everything is supposed to work now (no more nasty ACPI hacks), the disadvantage is that its not quite working yet (at least the wlan for me.) Eee-control need sto be more 2.6.27-aware.

Also, I noticed that on my next update it pulled down an eeepc version of linux-headers for the old kernel version (2.6.27-4).  I doubt it will make any difference, but I didn't know if that was intended.  (I added the intrepid repository only.)

Ah, thanks for notifying me. I've removed those older versions.

What you had received would have been the exact same thing on the official intrepid repo, so nothing should have changed for you.

@elcesar, That would be very useful.
Also, can you send me a bootchart of 2.6.27-4-generic (or the latest generic kernel, I dont know if they released 5-generic yet).

I've noticed a pretty major difference between 2.6.24-19-generic and 2.6.27-4-generic, myself. (+30sec)

It's a known issue to the upstream kernel.

@hermann4711

Re-read the first post in this thread. Specifically what's below the changelog.

adamm wrote:

@hermann4711

Re-read the first post in this thread. Specifically what's below the changelog.

I read the first post in this thread more than once, it gives an answer to the toggle-problem but not to my question if this new kernel can be used in a normal ubuntu installation.
(I also read Adams answer to another newbie on this side. Maybe, Adam has some mulligrubs!?
Tomorrow it will be better!)
;-)

Holy ****... I just got my 900's boot time from 1:35 on Intrepid to 0:47 with a new test intrepid kernel. (And that's with my permanently borked /dev/sda spewing errors on startup! [dont ask!])

I thought I'd take the lead from Arjan @ fastboot (remember that 5 second boottime article a few days ago) and compile in a slew of the drivers in-line with the kernel... Along with that I disabled /etc/init.d/readahead and readahead-desktop:

sudo chmod -x /etc/init.d/readahead
sudo chmod -x /etc/init.d/readahead-desktop

(The same can be accomplished by just uninstalling the readahead package itself.)

... I'm curious to see how much this'll help in speeding up the faster 901s. 20-25 sec boot time?

adamm wrote:

I just got my 900's boot time from 1:35 on Intrepid to 0:47 with a new test intrepid kernel.

That`s what I´m talkin`about! 50% faster boot time is a huge progress. Go on with the work, maybe you could reach the 5 seconds

I'm going to hold off a bit on this experimental intrepid build.

I'm really weary about how this works. I've never actually tried this method before. So far its working well for me on my 900 (30-40s boot time) but it's a bit higher risk, IMHO.

I'll play with it again tomorrow, for now i'm off

Stay tuned!

back with 2.6.27-5.5eeepc0 kernel & restricted drivers
1) wireless connexion seems OK,

[   14.975817] ath5k_pci 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[   14.975841] ath5k_pci 0000:02:00.0: setting latency timer to 64
[   14.975898] ath5k_pci 0000:02:00.0: registered as 'phy0'
[   14.980313] ath5k phy0: Support for RF2425 is under development.
[   15.486980] phy0: Selected rate control algorithm 'pid'
...
[   17.440087] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)

but syslog says:

[ 1844.324981] ath5k phy0: noise floor calibration timeout (2457MHz)
[ 1844.324999] ath5k phy0: ath5k_chan_set: unable to reset channel (2457 Mhz)
[ 1844.325014] wlan0: failed to set freq to 2457 MHz for scan
[ 1844.368746] ath5k phy0: noise floor calibration failed (2462MHz)
[ 1844.368764] ath5k phy0: ath5k_chan_set: unable to reset channel (2462 Mhz)
[ 1844.368773] wlan0: failed to set freq to 2462 MHz for scan

it happens every 120 seconds

2) powertop says :
No detailed statistics available; please enable the CONFIG_TIMER_STATS kernel option
This option is located in the Kernel Debugging section of menuconfig
(which is CONFIG_DEBUG_KERNEL=y in the config file)
Note: this is only available in 2.6.21 and later kernels

3) about boot times
i didn't install bootchartd yet, but i loo at when i915 driver loads (X start)
8.04 with 2.6.24-eeepc & optimisation* : 34sec
8.10 with 2.6.27-generic : 33sec
8.10 with 2.6.27-5eeepc : 32sec
8.10 with 2.6.27-5eeepc & optimisation* : 29sec

* optimisation for me is : "ro quiet clocksource=hpet elevator=deadline x=1024 y=600" (but i'm not a specialist

4) i have a 'compiz.real' crash notification when i log in.

5) INTEL_BATCH=1 doesn't improve fps anymore (experimental : see Bug #195843:)
on 8.04, i used to get 1400+ fps with INTEL_BATCH=1 glxgears.
with 8.10 i only get 500+fps with or without this option

Last edited by coolos (2008-10-06 7:19:53 am)

The bluetooth patch is incorrect, you also need to add:

&dev_attr_bt.attr

to the list of platform_attributes (in the same order as the EEEPC_CREATE_DEVICE_ATTR macros)

and also change the cm_getv and cm_setv to read:

static const char *cm_getv[] = {
        "WLDG", "BTHG", NULL, NULL,
        "CAMG", NULL, NULL, NULL,
        NULL, "PBLG", NULL, NULL,
        "CFVG", NULL, NULL, NULL,
        "USBG", NULL, NULL, "MODG",
        "CRDG", "LIDG"
};

static const char *cm_setv[] = {
        "WLDS", "BTHS", NULL, NULL,
        "CAMS", NULL, NULL, NULL,
        "SDSP", "PBLS", "HDPS", NULL,
        "CFVS", NULL, NULL, NULL,
        "USBG", NULL, NULL, "MODS",
        "CRDS", NULL
};

but without your source I can't do this properly since you applied other patches to the eeepc_laptop module (which I would like to keep)

Could you please take care of this?

Or I could just change eee-control-daemon to look for whether the bluetooth module is loaded...

I also notice the wlan is missing from /sys/devices/platform/eeepc/ -- is this intentional? what should eee-control-daemon use?