[ltp] T60, Gutsy, woes!

[Robin Randhawa]

Hi Phil.

I'm a T61p Gutsy user so what I have to say doesn't strictly apply to
you but it sounds like I had similar "woes".

I had basically performed an upgrade from Feisty and was facing problems
with wireless, arbitrary gnome session failures etc. On a tip from a
friend, I bent over backwards and did a proper install of Gutsy this
time around.

On the whole, the overall Gutsy experience, especially with respect to
Network Manager was way better.It appears that something broke along the
upgrade path which an fresh install seems to have fixed.

At the moment, I have 2.6.23.9 working well - no wireless issues at all
- had to compile iwl4965 and associated subsystems by hand. So far as I
stick to vesa, I have hibernate working well too. The latest
thinkpad-acpi patches seem to work fine.

Cheers,
Robin

On Sun, 2007-12-02 at 11:31 +0000, Phil wrote:
> OK, against my better judgement I upgraded my T60 to Gutsy. Main
> reasons were the wireless was getting flaky (used to work like a charm
> but recently been really difficult to get it to connect) and the
> repeated failure to launch update manager because the password entry
> box would not appear.
> 
> Upgrade went very smoothly (I'm impressed with the slickness of this)
> but after upgrade I've got the following major issues:
>      1. wireless is screwed
>      2. gnome won't run (but gnome safe session is fine)
>      3. brightness on battery keeps going dim
> Details below. If anyone can help I'd be grateful.
> 
> Cheers
> Phil
> 
> # uname -a
> Linux phil-t60-linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT
> 2007 i686 GNU/Linux
> 
> 1) Wireless is much worse than before. I've got an Intel Corporation
> PRO/Wireless 3945ABG, and browsing on the net there's lots of people
> having problems and not a lot of good solutoins. In the end I got it
> working by removing network manager, and running the following
> (several times, first time didn't work):
>     modprobe -r ipw3945
>     modprobe ipw3945
>     iwlist scan
>     iwconfig eth1 essid <my network essid>
>     dhclient eth1
> 
> I'd love to get network manager running again, but most stuff I've
> read seems to imply it's the cause of the problem.
> 
> 2) Gnome fails on startup - I can only run in safe session mode.
> Looking in .xsession-errors I see the following:
>         (process:6198): Gtk-WARNING **: This process is currently
>         running setuid or setgid.
>         This is not a supported use of GTK+. You must create a helper
>         program instead. For further details, see:
>         
>             http://www.gtk.org/setuid.html
>         
>         Refusing to initialize GTK+.
>         
>         (process:6202): Gtk-WARNING **: This process is currently
>         running setuid or setgid.
>         This is not a supported use of GTK+. You must create a helper
>         program instead. For further details, see:
>         
>             http://www.gtk.org/setuid.html
>         
>         Refusing to initialize GTK+.
>         gdm[6195]: DEBUG: Attempting to parse key string:
>         daemon/DefaultPath=/bin:/usr/bin
>         
>         gdm[6195]: DEBUG: Attempting to parse key string:
>         daemon/DefaultPath=/bin:/usr/bin
>         gdm[6195]: DEBUG: Attempting to parse key string:
>         daemon/BaseXsession=/etc/gdm/Xsession
>         gdm[6195]: DEBUG:
>         Running /etc/gdm/Xsession /usr/bin/gnome-session for pshotton
>         on :0
>         /etc/gdm/Xsession: Beginning session setup...
>         Checking for nVidia: not present.
>         Starting Xgl with options:  -accel xv:pbuffer -accel
>         glx:pbuffer -nolisten tcp -fullscreen -br +xinerama
>         
>         Fatal server error:
>         no screens found
>         XIO:  fatal IO error 104 (Connection reset by peer) on X
>         server ":1.0"^M
>               after 0 requests (0 known processed) with 0 events
>         remaining.^M
>         rm: cannot remove `/tmp/.X1-lock': No such file or directory
>         can't lock memory: Cannot allocate memoryWARNING: not using
>         secure memory for passwords
>         cannot open display:
>         Run '/usr/bin/seahorse-agent --help' to see a full list of
>         available command line options.
> 
> safe session works fine, but I'm not sure what's blowing me up. XGL?
> What should I do about this?
> I'm using the ATI fglrx driver (latest version pulled of AMD's site) -
> I've got an  ATI Technologies Inc Radeon Mobility X1400
> 
> 3) On battery, the display brightness drops very low (ignoring the
> gnome power manager setting). If I up the brightness using the
> keyboard Fn-Home key it gets brighter, but after a few minutes
> something kicks it back down again.
> 
> -- The linux-thinkpad mailing list home page is at:
> http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad