26 Dec
2013
26 Dec
'13
6:17 p.m.
On Wed, 25 Dec 2013, Dan Youngquist wrote:
On 12/24/2013 09:48 PM, Felmon Davis wrote:
I say 'fixed' and not 'solved' since I have no idea what happened!
I was booting into recovery mode and trying to get wifi to work,
something to do with the atheros drivers. google yielded a tip about
changing something in the udev-ilish rules as there was this weird
atl1.c driver that kept showing up in dmesg as failing.
all I know is that I got wifi to work and decided to do a normal boot,
that is, cold boot and proceed automatically to X.
no problem. went from start to gui without a hiccup and with normal
use of touchpad and keyboard.
wicd isn't behaving so that's the next front.
if I wanted to set the default window-manager from the commandline,
which script do I alter?
F.
--
Felmon Davis
What excuses stand in your way? How can you eliminate them? -- Roger
von Oech
the trouble is that booting into the gui causes
touchpad and mouse to freeze
at the login screen, requiring a reboot.
If I understand correctly, the display manager is running things at that
point. So the first thing I'd try is a different display manager, like
lightdm or gdm instead of kdm-trinity.