From London Hackspace Wiki
< Equipment‎ | Lovelace(Redirected from Lovelace/Logbook)
Jump to: navigation, search


Attempted to perform an Ebay search in Chrome. Machine stalled. Only mouse movement possible with cursor jammed as text-entry. Otherwise completely locked up. After several minutes, on advise of lobby IRC terminal, went to hard reboot. Holding power button unjammed machine to reboot options. Selected restart.

On restart an automatic disk-check was performed with no apparent errors. However when graphical startup began it gave an error that video hardware could not be properly configured. Selected to continue in basic graphics mode. Machine started with desktop cloned across both monitors, not shared.

Installed KeepassX to allow me to update logbook.

~ Sci


Oh dear that broke mounting root again.

Much fiddling later:

it appears that at some point the disk in lovelace has been part of a 3 disk raid array, the md superblock is still there (possibly left over from a previous life?), the newer kernels that where detecting this and making a partly formed md0 disk which then blocked root from being mounted cos it overlapped with the raid partition.

I did mdadm --zero-superblock /dev/sda (or something like that), and now it boot!

it boooooooooooooooooooooooooots!!!!!

--JasperWallace 01:04, 12 April 2012 (UTC)


lovelace can't update the nvidia kernel modules, looks like it's using a back ported kernel.

remove back ported kernel and went with stock one.

--JasperWallace 01:04, 12 April 2012 (UTC)


Wouldn't turn on


Second monitor wasn't set up, added it to xorg.conf as a second X Screen (this will allow for disconnections w/o affecting Screen0). Noticed that attempting to restart X lead to it hitting 100% and hanging. Killed it, and kdm brought it up okay the next time & for a re-test. Should be okay on reboot (didn't test this). Gnome didn't handle a screen stretched across the two screens well (lacking Xinerama support?), which is why I went with the two-XScreen approach. The nouveau driver supports xrandr properly, so would be a better choice for frequent re-connections (at a cost of worse 3d support).

Note: Why is it using kdm for gnome? Loading gtk and qt for login is expensive. 15:22, 8 March 2012 (UTC)

2011-11-16 Operator: Mark

Created logbook