Updated to Gnome 2.12 broke login script
So I went about updating to Gnome 2.12 (which also included a kernel update from 53 to 56.
In the process my login script got broken.
not sure how, or what the problem is. It just tells me there is an invalid entry in the configuration file.
(a side note neither my wireless or built in NIC on the laptop would work after booting. I've since got the NIC back up and running).
Anyone know what this is referring to and how I can fix it? My linux knowledge is so-so, but I'm getting there.
You should try to find your orignal kernal image an use it. If gnome then complains you'll at least be able to see whats changed.
Drunk on my only day off :) If this didnt make any sense reply and I'll do better.
Heres some suggestions for a reply:
What script connects you on the internet? Using ifup? kppp? Send its config file (read all the files in your /etc/chat /etc/ppp /etc/ppp/peers/(ISP specific script or orig dummy script)
Your kernel .config file and a description of your system. If the generic kernel you installed didnt include support for something that your disto's default kernel did it could cause this problem. Dial up or network card?
well so far so good in getting stuff fixed.
All I did was choose a login screen and gnome stopped complaing.
I reinstalled my NIC drivers and all is good
currently fighting with my wireless intel ipw2200BG. it was working, now its being a pain. First it was the firmware, then the firmware was good, (after installing wireless tools) now it decided to crash because I had it working, and tried to connect to an old wireless connection (instead of remaking it) I'm going in again to see if I can convince it to work.
when I dmesg | grep ipw
I get now errors, however when I try to initialize the wireless connection I get:
./ifup-wireless: line 66: 3401 segmentation fault iwconfig $DEVICE key $KEY
 google has lead me to believe this is the WPA key causing a segmentation fault (though I know it supported WPA before). I haven't found a listed fix for my card specifically, that might help someone who knows what they're doing give me a solution ;)
|All times are GMT -5. The time now is 10:37 PM.|