Equipment/Lovelace/Logbook: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=== 2012-04-12 === | |||
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. | |||
=== 2012-03-26 === | === 2012-03-26 === | ||
[https://groups.google.com/d/topic/london-hack-space/95r0YrB2058/discussion Wouldn't turn on] | [https://groups.google.com/d/topic/london-hack-space/95r0YrB2058/discussion Wouldn't turn on] | ||
Revision as of 23:51, 11 April 2012
2012-04-12
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.
2012-03-26
2012-03-08
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
