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.  🙂

Advertisements

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
=======================