Fedora 10 beta on eee pc 901 – take 2

* before i forget – there’s an odd bug where if you press ctrl– to shrink the text in gnome-terminal it crashes.  i should track that down at some point but it’s certainly there in the f10beta livecd. … seems to be fixed after an update. – ah! actually i think it’s just that with compiz enabled the window resizes itself off the screen.

this time i set up /boot on RAID1, the rest of the 4G disk and a matching chunk of the 16G as a RAID0 physical volume  with /home on it and the rest as another physical volume with / followed by a 1G swap partition.

the 480 updates took 11.5 hours to complete.  no errors so far as i can see.  no new updates to apply.

so, let’s try rebooting from kernel-2.6.27-0.352.rc7.git1.fc10.i686 to kernel-2.6.27.4-47.rc3.fc10.i686

i’ll edit the grub boot line so it’s not quiet or graphical and i’ll press escape if the blue bars appear at the bottom of the boot screen so i can see what happens.  also, i’ll do a shutdown and power on rather than just a restart.

——-

it’s absolutely fine.  no problems at all.  *sigh*

new things:

  • the add/remove software window doesn’t have a maximise button and appears maximised by default.  if you unmaximise it (by dragging) you can’t re-maximise or resize it.  with desktop effects enabled it appears small by default – so you can’t use it.
  • the first attempt to add more software produced an odd error.  just clicking apply again has worked with a message that “An untrusted package was installed”.
  • i installed google gadgets.  clicking Run when it finished either didn’t work or it crashed.  running it again from the menus worked.
    • another software install – another ‘run not working’ – so i don’t think it crashed.
  • i’ve discovered the neon theme for cairo-dock – it’s pretty!

    eee desktop screenshot

    eee desktop screenshot

  • installed the wireless drivers from the development part of the fusion repo.  success!  (you don’t need to reboot – just modprobe rt2860sta and wait a few seconds for NetworkManager to pick up some networks.)  of course, the moment it starts working a new kernel becomes available in rawhide.
  • also discovered that the black variant of the most excellent comix cursors have a super-nice little featurette – the ‘bar’ cursor that appears over text has a red bar.  super-nice.
  • i had intended to do lots of carefully controlled restarts to pin down the problem if it reoccurred .. but i wasn’t concentrating and accidentally did a default reboot.  i’ve done a couple more since then – no problems.

happy now.  🙂

fedora death on eee

i installed those 460 updates and (about 8 hours later) rebooted.  this time we got another filesystem error but fsck reported a lot more problems and now when i boot i just get:

VFS: Can't find ext3 filesystem on dev dm-0.

now i think i got that before when i tried to install F9 and i just re-installed and it was okay the second time round.  so i’m going to try re-installing F10 and we’ll see what we get.

———-

booting to f10 beta livecd was painless again but the system reported many disk errors on the system disks (presumably because of whatever stopped it booting before) and throttled them back to their slowest settings (PIO0) so when the ‘install to system’ got to the ‘copying image to disk’ stage it went very slowly and the system got very slow too.  so i gave up and rebooted.  i guess the re-format and reboot cheered it up because those errors went away and i’m now typing this from f10 beta proper again.

i’ve tried rebooting with this default kernel but haven’t been able to reproduce the disk corruption yet so i’ve kicked off the system update again.  480 updates this time.

oh, i’ve taken a copy of the dmesg errors i mentioned earlier:

=================================
[ INFO: inconsistent lock state ]
2.6.27-0.352.rc7.git1.fc10.i686 #1
———————————
inconsistent {hardirq-on-W} -> {in-hardirq-W} usage.
NetworkManager/2490 [HC1[1]:SC0[1]:HE0:SE0] takes:
(&adapter->mdio_lock){+-..}, at: [<f88ee54e>] atl1e_intr+0x22d/0x3f7 [atl1e]
{hardirq-on-W} state was registered at:
[<c044ca1a>] __lock_acquire+0x2ad/0xae6
[<c044d2ae>] lock_acquire+0x5b/0x81
[<c06e5150>] _spin_lock+0x23/0x50
[<f88f1fdc>] atl1e_probe+0x50b/0x6bc [atl1e]
[<c054164e>] pci_device_probe+0x3e/0x5e
[<c05aeb0e>] driver_probe_device+0xa5/0x141
[<c05aebec>] __driver_attach+0x42/0x64
[<c05ae4c1>] bus_for_each_dev+0x43/0x6d
[<c05ae996>] driver_attach+0x19/0x1b
[<c05aded6>] bus_add_driver+0xa8/0x1c8
[<c05aeda1>] driver_register+0x89/0xe9
[<c0541840>] __pci_register_driver+0x58/0x84
[<f881601c>] 0xf881601c
[<c0401139>] do_one_initcall+0x42/0x133
[<c045500e>] sys_init_module+0x8e/0x183
[<c0404d0a>] syscall_call+0x7/0xb
[<ffffffff>] 0xffffffff
irq event stamp: 8897
hardirqs last  enabled at (8895): [<c044c160>] trace_hardirqs_on+0xb/0xd
hardirqs last disabled at (8897): [<c0535c24>] trace_hardirqs_off_thunk+0xc/0x10
softirqs last  enabled at (8818): [<c0432781>] __do_softirq+0x104/0x10f
softirqs last disabled at (8896): [<c06e518e>] _spin_lock_bh+0x11/0x55

other info that might help us debug this:
2 locks held by NetworkManager/2490:
#0:  (rtnl_mutex){–..}, at: [<c065955d>] rtnetlink_rcv+0x17/0x2b
#1:  (_xmit_ETHER){-…}, at: [<c06504ea>] dev_set_rx_mode+0x19/0x2b

stack backtrace:
Pid: 2490, comm: NetworkManager Not tainted 2.6.27-0.352.rc7.git1.fc10.i686 #1
[<c06e2d1a>] ? printk+0x14/0x1a
[<c044b8fa>] valid_state+0x12a/0x13d
[<c044bcf7>] mark_lock+0xde/0x331
[<c044c99d>] __lock_acquire+0x230/0xae6
[<c044b392>] ? trace_hardirqs_off_caller+0x15/0x91
[<c044b419>] ? trace_hardirqs_off+0xb/0xd
[<c04097a2>] ? native_sched_clock+0xb3/0xd3
[<c044bc37>] ? mark_lock+0x1e/0x331
[<c044d2ae>] lock_acquire+0x5b/0x81
[<f88ee54e>] ? atl1e_intr+0x22d/0x3f7 [atl1e]
[<c06e5150>] _spin_lock+0x23/0x50
[<f88ee54e>] ? atl1e_intr+0x22d/0x3f7 [atl1e]
[<f88ee54e>] atl1e_intr+0x22d/0x3f7 [atl1e]
[<c044a9b0>] ? lock_release_holdtime+0x30/0x125
[<c046d192>] handle_IRQ_event+0x1f/0x54
[<c046e290>] handle_fasteoi_irq+0x82/0xbb
[<c046e20e>] ? handle_fasteoi_irq+0x0/0xbb
[<c0406fad>] do_IRQ+0x9f/0xc9
[<c0405700>] common_interrupt+0x28/0x30
[<c06502a5>] ? __dev_set_rx_mode+0x2b/0x8c
[<c06504f1>] dev_set_rx_mode+0x20/0x2b
[<c06520c0>] dev_open+0x96/0xb9
[<c0651ae0>] dev_change_flags+0xa1/0x154
[<c0658883>] ? rtnl_setlink+0x0/0xdb
[<c06587d1>] do_setlink+0x26d/0x31f
[<c06e4f3c>] ? _read_unlock+0x22/0x25
[<c0658883>] ? rtnl_setlink+0x0/0xdb
[<c065895a>] rtnl_setlink+0xd7/0xdb
[<c065970e>] rtnetlink_rcv_msg+0x19d/0x1b7
[<c0659571>] ? rtnetlink_rcv_msg+0x0/0x1b7
[<c066730b>] netlink_rcv_skb+0x35/0x7a
[<c0659569>] rtnetlink_rcv+0x23/0x2b
[<c0666f05>] netlink_unicast+0xf6/0x14c
[<c0667192>] netlink_sendmsg+0x237/0x244
[<c0645b4f>] __sock_sendmsg+0x4a/0x53
[<c0646379>] sock_sendmsg+0xbd/0xd3
[<c043f922>] ? autoremove_wake_function+0x0/0x38
[<c043f922>] ? autoremove_wake_function+0x0/0x38
[<c041f2ae>] ? need_resched+0x18/0x22
[<c05360db>] ? copy_from_user+0x3e/0x125
[<c064cbae>] ? verify_iovec+0x45/0x73
[<c06464d3>] sys_sendmsg+0x144/0x197
[<c0646fb5>] ? sys_recvmsg+0x11b/0x180
[<c044b392>] ? trace_hardirqs_off_caller+0x15/0x91
[<c044b419>] ? trace_hardirqs_off+0xb/0xd
[<c04097a2>] ? native_sched_clock+0xb3/0xd3
[<c040961f>] ? sched_clock+0x8/0xb
[<c044a9b0>] ? lock_release_holdtime+0x30/0x125
[<c044c160>] ? trace_hardirqs_on+0xb/0xd
[<c044c134>] ? trace_hardirqs_on_caller+0xf9/0x11a
[<c044c160>] ? trace_hardirqs_on+0xb/0xd
[<c042abf1>] ? finish_task_switch+0x49/0xc5
[<c042aba8>] ? finish_task_switch+0x0/0xc5
[<c06e3549>] ? schedule+0x6d9/0x6f8
[<c0647530>] sys_socketcall+0x16d/0x1a3
[<c040b403>] ? syscall_trace_enter+0xba/0xce
[<c0404d0a>] syscall_call+0x7/0xb
=======================

eee 901 wireless on fedora 10

along with the 1.8.0 driver there’s an intriguing WebUI file.  not sure what it is but the install script builds some stuff (possibly including the driver) and then starts firefox pointing at a local server running on another port.

don’t forget to install make, gcc and kernel-devel before running the script!

Error unpacking rpm package glibc-common-2.8.90-14.i386
エラー: アーカイブの伸長に失敗: ファイル /usr/share/i18n/charmaps/ISO_6937-2-25.gz;490266ab: cpio: open

for the WebUI you also need openssl-devel

of course, the kernel-devel package it’s picked up isn’t the right one for the original kernel – that’s not available through yum.  so we’ll have to update the kernel and reboot…..

oooh, while i’m waiting for the kernel to install – watching videos with compiz enabled works fine now!  😀

although that reminds me – with a 5.1ch ogg movie playing in totem all i’m hearing is the rear channels no matter what sound options i select – at least that’s what happened  on F9.

had filesystem problems when i rebooted and it wouldn’t accept my root password.  booted with the old kernel and it still had the fs probs but accepted my password and fsck’d the problems.  now i’m back with the latest kernel.

looks like the driver compiled okay – and it’s done its mad “and copy the file to /tftpboot” thing as before.  let’s try that WebUI thing again…

the script uses zenity to pop up prompts – extremely slow if you’ve got input methods enabled.  lots and lots of compiling but it still doesn’t work.  whatever, back to the actual driver…

hmm.  it looks like it’s loaded okay.  there’s a ra0 device but networkmanager hasn’t spotted it and i can’t ifup it or rmmod the module.  time for another reboot i think….

didn’t help much.  i can rmmod and modprobe now but nothing happens.

tried adding “alias ra0 rt2860sta” to /etc/modprobe.conf …. no change.

running the webui thingy adds the ra0 interface and locks up the module.  doesn’t appear to have any other effect though. … oh, apart from allocating it an IP6 address.  hmm.

guess i’d better install these 460 updates!  good old rawhide.

on the plus side, fiddling around with this has revealed that there is a monitor mode.  iwconfig ra0 mode monitor works!

welcome to fedora 10 Beta

so, almost first impressions:

  • had to install from livecd again – no problems except that, as with f9, the window doesn’t fit until you reduce the font size from 10 to 6pt.  (the font properties window is too big too!)
  • i’ve accepted the default layout this time – no RAID weirdness.
  • like the funny little coloured  bars (white, light blue and blue) during the initial boot.
  • near the end of startup something crashes just before X starts.  i think it happened with the liveCD too.
  • starting X for firstboot takes forever but i think it did that for fedora 9 too.
  • enabling desktop effects for the first time leave a lot of the screen black – needs a redraw.  changing workspaces fixes that.
  • the adobe repo works as does flash (from that repo)
  • the wireless drivers still haven’t arrived in the kernel
  • SELinux is preventing alsactl (alsa_t) “getattr” to /usr/share/alsa/alsa.conf (usr_t).

now to try out the suspend stuff…

on AC:

selecting suspend from the battery status icon suspends (even though it looked like it was about to hibernate because it took ages and went into text mode and displayed some messages)

screen brightness Fn keys still work – there’s no OSD but ‘dim on idle’ seems to work.

suspend on idle works too just the same.

suspend on lid works fine too.  a lot faster but i think that’s just because some system stuff was busy thrashing the disk earlier.  opening the lid doesn’t wake it up – you have to press a key (same as in F9 – presumably it’s a eee thing).

on battery… (screen dims and OSD shows)

suspend from the icon works.

suspend on idle… hibernates!  (that’s probaby what was happening on F9 too) hmm.  seems to be a bit smarter than before – removes cache and “shrinks memory” before writing memory to disk – but it took a looooong time to start up again.

suspend on lid works.

so that’s still annoying – if you’re running on batteries you have to remember to shut the lid otherwise it’ll hibernate.  boo.

but they’ve fixed the screen brightness on resume – hooray!

fedora 9 on the eee pc 901

i need to make a note of all the behaviours of fedora 9 on my eee pc 901 before installing fedora 10 beta on it.

main points are:

  • have to build wireless drivers from source from here – currently version 1.8.0 – which is, hopefully, the same as the 1.7.0 i used plus the patches i had to apply!
  • the wireless driver doesn’t appear to have a monitor mode
  • without a usb dvd drive you have to boot from the SD slot or an external usb hard drive. this works with livecd (if you’ve got the livecd creator tools) but not with the DVD image.
  • after a suspend/resume the brightness control doesn’t work
  • suspend by closing the lid works fine but suspend on idle does a hibernate instead
  • there’s noise from the speakers if they’re not muted – which is a shame on an utterly silent system
  • occasionally the back-light switches off (possibly only after screensaver and screen blank when on AC) and it doesn’t come back on until you use a Fn brightness key. it’s still possible it’s actually any key and it’s just gone to sleep
  • 3D works pretty well for compiz but it goes a bit wrong when you try running a 3D or Xv (video) app at the same time – particularly troublesome when that app defaults to fullscreen mode – e.g. blender or miro. watching DVDs or using stellarium or blender is fine with compiz disabled
  • no middle mouse button (big problem in blender) and we’ve moved to xinput driver so it’s a bit of a pain enabling support again – i created /etc/hal/fdi/policy/3button.fdi with
    <match key="info.product" string="ImPS/2 Logitech Wheel Mouse">
     <merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
    </match>

    in it.  can’t remember where i read that – i think it’s the sum of several hints and previous hal experience.

  • sometimes if you type too fast keystrokes (especially shift keys) are missed
  • when compiz is enabled you get a brief flash of the desktop before the password prompt is displayed when the system has been locked or suspended
  • sometimes networkmanager disables networking entirely – not sure why.  i think it only happens after a suspend/resume – but only occasionally.
  • 3D does have its limits – flightgear manages only a couple of frames per second (might not have anything to do with the 3D and might be fixable in the settings) – celestia doesn’t work at all and google-earth runs a several seconds per frame.  also i’ve switched off the compiz cube as there’s a little bit of tearing when it spins.  the left/right slide is much more understated anyway.
  • many bad apps assume you’ll have 600 vertical pixels to play with.  i think there might be a compiz plugin to run the entire screen like a virtual display scaled down – i’ll see if i can find that.
  • everything looks sooo pretty on it that  a) i’ve forgotten how hideous the ‘pearl white’ plastic is and b) i really don’t want to do a clean re-install.

on the plus side:

  • the screen is very nice
  • it plays DVDs – we’ll see how it copes with HD content soon
  • desktop effects, google gadgets and cairo-dock look great
  • it’s completely silent
  • battery life is good – 4-6 hours
  • i’ve installed all the good office, internet and graphics apps without problems
  • it fits in a small bag
  • i can afford it
  • it certainly runs F10 to some extent
  • you can jam a custom touch screen and 3G slot inside it!

happy days.

well, that’s as much as i can remember for now.  on with the show – let’s trash it and stick F10 beta on instead.

oh yes, the 901 actually has two SSDs – 4G + 16G for linux, 4G + 8G for windows.  nice.  so i tried partitioning them with some RAID stuff.  here’s some hdparm numbers for F9:

cached reads (memory speed) are around 550MB/s

the 4G disk goes at around 26-28MB/s

the 16G at around 24-27MB/s

RAID1 at around 24-26MB/s

RAID0 at around 30MB/s

with O_DIRECT (unbuffered):

4G 31MB/s

16G 28.5MB/s

RAID1 31MB/s

RAID0 30MB/s

STYG