logout and xorg.conf

[fluxalex]

Hi,

I have a small problem with an elderly Toshiba Satellite 1800-314 laptop and the newly installed Mint-Fluxbox. The laptop has a Trident Cyberblade XP Ai1 graphic accelerator and is originally equipped with Windows XP. It runs quite slow with XP, but it works perfectly, also the DirectX hardware acceleration. Maybe a year ago I decided to install ubuntu jaunty side by side to the XP and that also worked a bit slow but perfectly. Due to the very limited hard disk space and the performance difficulties, I decided to give Mint Fluxbox a try. The installation went well, but on reboot the graphics didn't work at all - just some random patterns on the screen. But that's what I was expecting, since on jaunty the "trident" driver was also not working and I had to use "vesa". So I rebooted into recovery mode and copied a xorg.conf file I used in jaunty and previously saved to the XP partition. It's very simple and looks like this:

----------------------------------------------------------------------------
Section "Device"
Identifier "Configured Video Device"
Driver "vesa"
# Driver "trident"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
HorizSync 31.0 - 48.0
VertRefresh 50.0 - 70.0
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1024x768" "800x600"
EndSubSection
EndSection
----------------------------------------------------------------------------

I managed to copy the file, but soon after the laptop was frozen, so that I had to switch it off by "force" and I had little hope that it would ever work with this installation. It is even in later attempts that strangely in recovery-mode it uses to freeze suddenly. For my surprise in the normal mode it works perfectly (with the above xorg.conf file). The only issue that I have now is that when I logout I can't login any more. In the login screen I can type the user-name and password but later it just hangs, although not completely frozen, since it shuts down normally when pressing the power button. The initial first login works always perfectly. The funny thing is that when I rename/delete the xorg.conf file and logout, I can login again and it works normally. Only after reboot I have again the random patterns. Since there are two users on the laptop, it would of course be nice if I could make it logout and login properly and having the correct resolution.

[fluxalex]

What is definitely clear, is that the Trident driver is crap regarding Cyberblade XP Ai1. From the xorg logfile I found out that strangely also in recovery-mode that driver is being used, although using a lower resolution that makes it work but then suddenly freezing. So I've added "xforcevesa" to the grub command-line options and the recovery mode works safe now. But the logout/login issue is still not solved.

[fluxalex]

Another odd thing. Now that I've added "xforcevesa" to the boot options, I tried again renaming/deleting the xorg.conf file. I logged out an in again. Then I went to see the xorg logfile and there again the "trident" driver was activated. I mean I would expect, if I specified forced use of "vesa", that after a simple logging out and logging in again, the driver wouldn't change. But it does and soon after the laptop was frozen again. As far as I remember "jaunty" was installed with "vesa" by default and it was me trying to make the "trident" driver work, but also having these effects, so that I gave up.

[fluxalex]

I went to synaptic and removed all of the xserver video drivers, except "vesa" (saves me about 10MB). Now basically I don't need the xorg.conf file since the correct available resolution is being recognized automatically by the "vesa" driver. But now with or without xorg.conf I cannot login after logout. So the problem is between the "logout/login" and the "vesa" driver and not the presence of "xorg.conf".

[shane]

Are you able to login after logging out... if you restart slim? e.g.

-log out
-Ctr+Alt+F1 and login
-run 'sudo /etc/init.d/slim restart'
-login from slim.

Also, what is in the xorg log file? /var/log/Xorg.0.log.old or something similar... and also ~/.xsession-errors

[fluxalex]

First here is the ".xsession.errors" of the last two sessions, i.e. first failed login after logout and second successful login after reboot:

--------------------------------------------------------------------------------------------

/usr/share/themes/MurrinaMintFB/gtk-2.0/gtkrc:54: Murrine configuration option "hilight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
/usr/lib/linuxmint/mint-fm2/endsession/endsession.py:47: GtkWarning: Theme directory scalable/stock of theme Minty has no size field

self.wTree = gtk.glade.XML(self.gladefile, domain='Quit')
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"

after 883 requests (882 known processed) with 0 events remaining.

polkit-gnome-authentication-agent-1: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Thunar: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
mintUpdate.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
[Errno socket error] [Errno -2] Name or service not known
Xsession: X session started for alex at Wed Mar 3 15:19:20 WET 2010
Setting IM through im-switch for locale=en_US.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default.
/usr/bin/startmintfluxbox: 9: /usr/lib/linuxmint/mint-fluxbox-default-settings/mintfb-verify.sh: not found
conky: no process found
python: no process found
nm-applet: no process found
system-config-printer-applet: no process found
bluetooth-applet: no process found
xfce4vino: no process found
volwheel: no process found
xscreensaver: no process found
mintUpdate: no process found
/usr/share/themes/MurrinaMintFB/gtk-2.0/gtkrc:54: Murrine configuration option "hilight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
mfmuserdaemon: no process found
Using /home/alex/.wbar config file.
fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option
Using a normal Bar.
Keys: Invalid key/modifier on line 18): OnDesktop Mouse1 :hideMenus
Keys: Invalid key/modifier on line 19): OnDesktop Mouse2 :workspaceMenu
Keys: Invalid key/modifier on line 20): OnDesktop Mouse3 :rootMenu
/usr/share/themes/MurrinaMintFB/gtk-2.0/gtkrc:54: Murrine configuration option "hilight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.

(polkit-gnome-authentication-agent-1:2995): GLib-GObject-WARNING **: cannot register existing type `_PolkitError'

(polkit-gnome-authentication-agent-1:2995): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
/usr/share/themes/MurrinaMintFB/gtk-2.0/gtkrc:54: Murrine configuration option "hilight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
/usr/share/themes/MurrinaMintFB/gtk-2.0/gtkrc:54: Murrine configuration option "hilight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
PolicyKit daemon disconnected from the bus.
We are no longer a registered authentication agent.

** (polkit-gnome-authentication-agent-1:2995): WARNING **: no sender

Xsession: X session started for alex at Wed Mar 3 15:22:09 WET 2010
Setting IM through im-switch for locale=en_US.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default.
/usr/bin/startmintfluxbox: 9: /usr/lib/linuxmint/mint-fluxbox-default-settings/mintfb-verify.sh: not found
conky: no process found
python: no process found
nm-applet: no process found
system-config-printer-applet: no process found
bluetooth-applet: no process found
xfce4vino: no process found
volwheel: no process found
xscreensaver: no process found
mintUpdate: no process found
mfmuserdaemon: no process found
/usr/share/themes/MurrinaMintFB/gtk-2.0/gtkrc:54: Murrine configuration option "hilight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
Using /home/alex/.wbar config file.
Using a normal Bar.
Keys: Invalid key/modifier on line 18): OnDesktop Mouse1 :hideMenus
Keys: Invalid key/modifier on line 19): OnDesktop Mouse2 :workspaceMenu
Keys: Invalid key/modifier on line 20): OnDesktop Mouse3 :rootMenu
/usr/share/themes/MurrinaMintFB/gtk-2.0/gtkrc:54: Murrine configuration option "hilight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.

(polkit-gnome-authentication-agent-1:1736): GLib-GObject-WARNING **: cannot register existing type `_PolkitError'

(polkit-gnome-authentication-agent-1:1736): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
/usr/share/themes/MurrinaMintFB/gtk-2.0/gtkrc:54: Murrine configuration option "hilight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
/usr/share/themes/MurrinaMintFB/gtk-2.0/gtkrc:54: Murrine configuration option "hilight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
/usr/share/themes/MurrinaMintFB/gtk-2.0/gtkrc:54: Murrine configuration option "hilight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
/usr/lib/linuxmint/mintUpdate/mintUpdate.py:1421: GtkWarning: Theme directory scalable/stock of theme Minty has no size field

window_id = repr(socket.get_id())
/usr/share/themes/MurrinaMintFB/gtk-2.0/gtkrc:54: Murrine configuration option "hilight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
ping: unknown host google.com
** (nm-applet:1738): DEBUG: foo_client_state_changed_cb
Keys: Invalid key/modifier on line 18): OnDesktop Mouse1 :hideMenus
Keys: Invalid key/modifier on line 19): OnDesktop Mouse2 :workspaceMenu
Keys: Invalid key/modifier on line 20): OnDesktop Mouse3 :rootMenu
Keys: Invalid key/modifier on line 18): OnDesktop Mouse1 :hideMenus
Keys: Invalid key/modifier on line 19): OnDesktop Mouse2 :workspaceMenu
Keys: Invalid key/modifier on line 20): OnDesktop Mouse3 :rootMenu

(nm-applet:1738): Gtk-WARNING **: Theme directory scalable/stock of theme Minty has no size field

** (nm-applet:1738): DEBUG: foo_client_state_changed_cb
/usr/share/themes/MurrinaMintFB/gtk-2.0/gtkrc:54: Murrine configuration option "hilight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.

(Thunar:1734): Gtk-WARNING **: Theme directory scalable/stock of theme Minty has no size field

/usr/share/themes/MurrinaMintFB/gtk-2.0/gtkrc:54: Murrine configuration option "hilight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.

[shane]

Did you try restarting Slim before trying to log in again?

There are quite a few errors but nothing I see that can prevent the login...

Try restarting Slim before logging in again... Also, just to see if it works, when you fail to log in, try switching to a virtual terminal (Ctrl_Alt+F1) and then back to X (Ctrl+Alt+F7) and see if it shows up... because it seems Fluxbox is starting up normally.

P.S. How confident are you with the command line? What's your level of Linux knowledge? So we settle on some level on complexity

[fluxalex]

(II) Module int10: vendor="X.Org Foundation"
compiled for 1.6.4, module version = 1.0.0
ABI class: X.Org Video Driver, version 5.0
(II) VESA(0): initializing int10
(II) VESA(0): Primary V_BIOS segment is: 0xc000
(II) VESA(0): VESA BIOS detected
(II) VESA(0): VESA VBE Version 2.0
(II) VESA(0): VESA VBE Total Mem: 16384 kB
(II) VESA(0): VESA VBE OEM: Trident CYBER 8820
The files Xorg.0.log and Xorg.0.log.old are identical except the very last line (compared them with "diff").
Both files contain this "ILLEGAL EXTENDED X86 OPCODE" error:

------------------------------------------------------------------------

(II) VESA(0): VESA VBE OEM Software Rev: 2.0
(II) VESA(0): VESA VBE OEM Vendor: TRIDENT MICROSYSTEMS INC.
(II) VESA(0): VESA VBE OEM Product: CYBER 8820
(II) VESA(0): VESA VBE OEM Product Rev: KTT 7.1 (12.17)
(**) VESA(0): Depth 24, (--) framebuffer bpp 32
(==) VESA(0): RGB weight 888
(==) VESA(0): Default visual is TrueColor
(==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
f000:370e: 01 ILLEGAL EXTENDED X86 OPCODE!
(II) VESA(0): VESA VBE DDC not supported
(II) VESA(0): VESA VBE PanelID read successfully
(II) VESA(0): PanelID returned panel resolution 1024x768
------------------------------------------------------------------------

And the very last line is different, i.e. the ".old" file DOESN'T contain the "ILLEGAL EXTENDED X86 OPCODE" error.

------------------------------------------------------------------------

(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
(**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00
(**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
(**) Macintosh mouse button emulation: (accel) set acceleration profile 0
(II) Macintosh mouse button emulation: initialized for relative axes.
f000:370e: 01 ILLEGAL EXTENDED X86 OPCODE!

----------------END OF FILE-------------------------------------

[fluxalex]

I'm not quite sure if I understood well, but what I did was to logout "normally" and at the "normal" login screen I pressed Ctrl-Alt-F1. Then I had random patterns on the screen, but it was mostly black So I pressed the power button and it shut down normally (i.e. it was not frozen). Then started again and the first "normal" login works as usual.

[fluxalex]

Now the next try was to logout "normally" and to login "normally" again. Then while it was hanging I pressed Ctrl-Alt-F1 and there happens nothing, i.e. I still see the Mint background image and only the power button still works....

[shane]

That is weird... Try Ctrl+Alt+F2... upto F6 should give you virtual terminals where you can log in to a command line interface.

I'll ask the other team members if they have any ideas.

[fluxalex]

Tried also Ctrl-Alt-F2 to F6 and it's all the same, only the screen is rather completely black. Then tried the same on the first login attempt that generally works. And even there pressind Ctrl-Alt-F1 to F6 doesn't provide me anything but random patterns or completely black screens. Switching back with Ctrl-Alt-F7 allows me to login, but as it's said only the first time.
I'm going to have a break now. I'll check again in the late evening (GMT)...

[rogue_ronin]

I've noticed that "random patterns on a completely black screen" when I was having problems, too. It's actually text, where only a few pixels of each letter is being displayed. Maybe it's a hint? I can recreate it here by using the power button to shut down. But it does log out.

I find that the login is very, very sensitive. I tried adding a .bash_aliases file, copying code from my regular laptop -- locked out of logging in as myself, although I don't get frozen out and could fix it as root.

m a r

[fluxalex]

I've not added anything and from the very beginning I had these problems. First it is that the "Trident" driver, which is supposed to work with this hardware, doesn't work. But that one didn't work with "ubuntu jaunty" either, that I had installed before on this laptop. So as last resort one is using the "Vesa" driver and that one worked with "jaunty". Basically it works also here, except that I cannot login after I logged out, i.e. the first time I'm logging in, it works perfectly. On the other hand with the "Trident" driver I was able to log out and in again. But there I had sudden freezes and it worked only with 800x600 instead of the full 1024 resolution. I mean I like this installation and there is some performance increase compared to "jaunty". WinXP is extremely slow, maybe due to antivirus or that 512MB RAM is not enough, so I'm mostly using it with "Linux", but for few things I still need XP. If I could get rid of this small "blemish", I would be perfectly happy with it, even having to use the "Vesa" driver. This laptop is of course antiquated, and I understand that there is little impetus in maintaining the "Trident" driver, otherwise I'd turn on that

[fluxalex]

What I tried now was to logout, press Ctrl-Alt-F1 and then blindly type my username and password. I could see some changes happening to the patterns , so there was something going on. Then I typed the sudo /etc/init.d/slim restart and typed the password again (for sudo). Then I switched back Ctrl-Alt-F7 and there was a change - the cursor wasn't there and I couldn't type anything any more. Before I could type the username and password and only afterward it would hang.
But obviously the problem must be that the graphics driver is not being put into the same state in the login window through logout as it is after a fresh (re)boot. So there must be some resets missing in the logout procedure.

[fluxalex]

It is weird. Just for fun I was experimenting with the monitor settings. And with these settings and especially only this VertRefresh it seems to be working. I don't know if there is something more involved and this is just coincidence, it might depend on the CPU-temperature

Section "Monitor"
Identifier "Configured Monitor"
HorizSync 28.0 - 51.0
VertRefresh 60.0 - 60.0
EndSection

[shane]

Glad that you figured out a workaround because I was totally stumped for ideas...

[fluxalex]

Yes, even the Ctrl-Alt-F1 works now that we don't need it any more