peter.chiu@stfc.ac.uk said the following on 02/04/2013 02:42 PM:
Many thanks, for your kind comments.
After sending my query to the list, I have made a copy of my installation into another partition, and redid the installation.
As it stands, I have /dev/sda1 with 12.2 without YOU, and /dev/sda2 with YOU. The console is working okay as usual, and I can log on as root, or another user account in kde or gnome.
"Console" meaning what, exactly? To me, being an old UNIX hack from long before GUI, a console is the text mode terminal device hanging of a RS-232 port. What is it to you? Do you mean the text-mode "console" on tt1 that applies whether you are in "runlevel" 1, 3 or 5 or the GUI mode login running under Xorg and XMD/KDM/GDM that only applies if you are running in 'runlevel 5" (or "systemctl default.target" being 'graphical.target' rather than merely 'multi-user.target') Why am I making an issue of this? The term 'console' does have a specific meaning and that meaning is distinct from the GUI. See console(4) pam_console(8) and of course consoletype(1) whic will when run as 'consoletype fg' tell you if you are at the console or not.
I did try to look into dual-booting in the hope of starting up sda2, but have to admit falling behind on Opensuse. Under 12.1 and 11.x, there is a simple script /boot/grub/menu.lst, that I can manually add in a second boot entry.
But this file is no longer present, so cannot reboot the YOU applied version to try out your suggestions, sorry...
The "menu.lst" is from the original grub that was the default with older versions of openSuse. It looks like you took or defaulted to installing grub2. Look under /boot/grub2 for grub.cfg You're not supposed to had edit this :-) See /etc/grub2/ for the files that go to generate it if you want your changes to be persistent. Oh, and google for how-tos on grub2 for that all.
I have however got a copy of the Xorg.0.log, that I have attached here. In comparison from the non-YOU patched version, I can see the patched version is trying to use the module sis
Why it got changed, not sure.
Why it got changed .. probably because your hardware is 'sis'. That's what xorg saw. It would be useful if you gave us the output of "lspci | grep VGA" and "lsmod | grep sis" You might also want to google for an read some of the more recent docco on the X server. I would strongly suggest that while debugging you do not run the system in "runlevel 5" but rather "runlevel 3" and use 'startx'. If all else fails you can use the "-configure" option of X to see what it thinks it should be using - wrong obviously, but it gives you soemting to work with. DO NOT USE A xorg.conf FILE ON A LIVE SYSTEM. The 'sis' system I have had to tweek have a minimalist change in the /etc/X11/xorg.conf.d/ files as needed. What did I do? I set the frequency of my screen in 50-monitor.conf That doesn't seem to be your problem. You can look through the archives for why I needed to do that. I set the characteristics of my touch-pad in 50-synaptics.conf That deons't seem to be your problem either. My *F*E*E*L*I*N*G* is that this is not an xorg problem but a system level problem. Look to see what kernel modules you have loaded.
But it will be useful to know how to reconfigure this.
Go google :-) -- I suspect that, over time, all bureaucratic processes decay into cargo cults unless regularly challenged by a hostile reality. -- Alan Rocker 2001-11-23 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org