A discrepancy between the live cd and the installed version of 13.1:
Settings menu > Mouse and touchpad: In installed 13.1, there are two sections, General & Mouse. In the live cd 13.1, there are three: General, Mouse, and Touchpad. The touchpad section allows the disabling of the touchpad, something that I greatly desire, seeing that I am apparently a ‘heavy thumbed’ typer.
Thanks for your help …
Jon
On 2014-03-05 02:26, reddawg315 wrote:
>
> A discrepancy between the live cd and the installed version of 13.1:
Which live cd? There are at least two installable cds.
In other words: are you using gnome or kde?
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
in Gnome I have no idea but in KDE you would use synaptiks to disable the touchpad.
You have a choice of disabling if a mouse is plugged in or disabling for a period of time on keyboard activity.
Sorry, the live cd is the Gnome version, as I use Gnome as my installed desktop
Jon
I have not tried the Gnome live, so I am not aware of the discrepancy. You can perhaps boot the live media, go into
Yast → Software Manager
and search for “touchpad”. Maybe there’s some software there that isn’t present on your installed system. Did you install from that live media? Or did you install from the DVD image?
I’m normally a KDE user. However, when I try Gnome on my laptop, there is an Fn key combination that I can use to disable the touchpad (the same keys as work in Windows). And Gnome remembers that it is disabled for the next login. Hmm, I might be remembering from opensuse 12.3 or earlier. You might want to give that a try.
On KDE, I use “synaptiks” to turn off the touchpad.
On 2014-03-05 15:56, reddawg315 wrote:
>
> Sorry, the live cd is the Gnome version, as I use Gnome as my installed
> desktop
I have tried “gnome-control-center”. There is an item named “Mouse &
touchpad”. In my lapto is has a bottom section for touch pad
configuration, whereas on the desktop that section is missing. It is
automatic, I don’t see where to tell it that there is a touchpad available.
However, if instead of gnome you use xfce, which is also gtk based, the
dialog for the mouse (same laptop) has many more options; but the
touchpad section is only present when it somewhow thinks there is a
touchpad available.
So, why does not your installed system think there is a touchpad?
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Ahh - you have put your finger on the problem. The gnome-control-center is the same applet as is displayed in ‘settings>mouse and touchpad’. Your laptop and the gnome live cd have three sections - my 13.1 shows only two - the bottom section dealing with the touchpad is missing. But it’s not that the system/laptop don’t know there is a touchpad installed - the touchpad cursor control and buttons work as intended, so the driver must be installed & functioning.
I just noticed that there is a ‘touchpad’ icon in the applications screen. But when I try to invoke it, I get the following error:
GSynaptics couldn’t initialize. You have to set ‘SHMConfig’ ‘true’ in xorg.conf or XF86Config to use GSynaptics
I haven’t been able to find either the xorg.conf, or XF86Config files.
Help?
Thanks much
Jon
On 2014-03-06 15:46, reddawg315 wrote:
> I just noticed that there is a ‘touchpad’ icon in the applications
> screen. But when I try to invoke it, I get the following error:
>
> GSynaptics couldn’t initialize. You have to set ‘SHMConfig’ ‘true’ in
> xorg.conf or XF86Config to use GSynaptics
Interesting.
>
> I haven’t been able to find either the xorg.conf, or XF86Config files.
They don’t exist because the configuration is automatic.
> Help?
You should have a file named “/etc/X11/xorg.conf.d/50-synaptics.conf”.
It is installed from “xf86-input-synaptics-…rpm”.
If you have it, please upload your “/var/log/Xorg.0.log” file to
susepaste.org, and post a link here, so that we can see if it mentions
anything about the touchpad.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
That does not actually follow. If the touchpad driver does not recognize it, then it might be recognized as a generic PS/2 mouse, and still work. But you cannot disable it. That happened to me when my laptop was new.
Here is the link to my /var/log/Xorg.0.log file. I do have a Logitech usb mouse attached to the laptop.
Thanks again for your help
Jon
On 2014-03-09 22:26, reddawg315 wrote:
>
> Here is the link to my /var/log/Xorg.0.log file. I do have a Logitech
> usb mouse attached to the laptop.
>
> Thanks again for your help
>
> http://susepaste.org/701288
> 71.320] Kernel command line: root=/dev/sda6 apm=off acpi=off mce=off barrier=off ide=nodma idewait=50 i8042.nomux psmouse.proto=bare irqpoll pci=nommconf resume=/dev/disk/by-id/ata-WDC_WD3200BPVT-75ZEST0_WD-WX41AA0F7602-part5 splash=silent quiet vga=0x317
You are booting in safemode. Things may not work in this mode.acpi is
disabled, apm, mouse is set to a special mode…
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Well, dang! How did safe mode get specified? No intentional effort on my part. Perhaps that would also have an effect on the power / temp probs the laptop is experiencing.
How would one change the boot process back to ‘normal’?
Thanks …
Jon
On 03/10/2014 09:56 AM, reddawg315 pecked at the keyboard and wrote:
> Well, dang! How did safe mode get specified? No intentional effort on
> my part. Perhaps that would also have an effect on the power / temp
> probs the laptop is experiencing.
>
> How would one change the boot process back to ‘normal’?
>
> Thanks …
>
> Jon
>
>
Isn’t this normally triggered by a boot problem? If so check your
/var/log/boot.log file for any errors that may have triggered safemode boot.
Ken
Here is the link to my boot.log file. There’s nothing obviously wrong that I can see - let me know if you see the reason for booting into safe mode.
Thanks …
Jon
On 03/10/2014 05:26 PM, reddawg315 pecked at the keyboard and wrote:
> ’
>
>
> http://susepaste.org/49621562’ (http://susepaste.org/49621562)
>
> Here is the link to my boot.log file. There’s nothing obviously wrong
> that I can see - let me know if you see the reason for booting into safe
> mode.
>
> Thanks …
>
> Jon
>
>
If you run
systemctl set-default graphical.target
and reboot what happens?
Ken
I ran the systemctl command, and the system returned:
rm ‘/etc/systemd/default.target’ ‘etc/systemd/system/default.target’
then I rebooted. I’m not sure how to tell if the system is running in safe mode. Here is the new kernal command line from /var/Xorg.0.log. It looks much like the previous kernal command -
Kernel command line: root=/dev/disk/by-id/ata-WDC_WD3200BPVT-75ZEST0_WD-WX41AA0F7602-part6 apm=off acpi=off mce=off barrier=off ide=nodma idewait=50 i8042.nomux psmouse.proto=bare irqpoll pci=nommconf resume=/dev/disk/by-id/ata-WDC_WD3200BPVT-75ZEST0_WD-WX41AA0F7602-part5 splash=silent quiet vga=0x317
ready for the next step …
Jon
On 2014-03-10 14:56, reddawg315 wrote:
>
> Well, dang! How did safe mode get specified? No intentional effort on
> my part.
Well, it is always an intentional change. It can happen, for instance,
if you had problems during installation, and used safemode for install.
The install system sets the installed kernel for safe defaults always as
a consequence.
I suggest you run:
grep -i "Kernel command line" /var/log/messages
zgrep -i "Kernel command line" /var/log/messages*xz
to find out when it started.
Perhaps that would also have an effect on the power / temp
probs the laptop is experiencing.
Yes. Certainly. No acpi/apm, means no control at all. And many things…
How would one change the boot process back to ‘normal’?
Mmm… tomorrow. I have to go to bed! 
Just a hint. You have to edit “/etc/default/grub”. Find out the lines
GRUB_CMDLINE_LINUX_DEFAULT=...
GRUB_CMDLINE_LINUX_RECOVERY=...
change something, then run something (see the comments on the file). I
can’t give you the details right now. Bed is calling!
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
reddawg315 wrote:
>
> I ran the systemctl command, and the system returned:
>
> rm ‘/etc/systemd/default.target’ ‘etc/systemd/system/default.target’
>
> then I rebooted. I’m not sure how to tell if the system is running
in
> safe mode. Here is the new kernal command line from
/var/Xorg.0.log.
> It looks much like the previous kernal command -
>
> Kernel command line:
> root=/dev/disk/by-id/ata-WDC_WD3200BPVT-75ZEST0_WD-WX41AA0F7602-
part6
> apm=off acpi=off mce=off barrier=off ide=nodma idewait=50
i8042.nomux
> psmouse.proto=bare irqpoll pci=nommconf
> resume=/dev/disk/by-id/ata-WDC_WD3200BPVT-75ZEST0_WD-WX41AA0F7602-
part5
> splash=silent quiet vga=0x317
>
> ready for the next step …
>
> Jon
John you can check with following commands. In safe mode (old run
level three) with the following commands:
systemctl status multi-user.target
</CODE>
Graphical Mode;
<CODE>
systemctl status multi-user.target
</CODE>
If both are Active. You should be able to do (as Root):
<CODE>
systemctl isolate multi-user.target
</CODE>
Once done what you want to do, the systemctl isolate graphical should
take you back to runlevel 5.
man systemctl has a lot more info.
Hope this helps.
openSUSE 13.1(Linux 3.11.10-7-desktop x86_64|
Intel(R) Quad Core™ i5-4440 CPU @ 3.10GHz|8GB DDR3|
GeForce 8400GS (NVIDIA-Linux-x86_64-331.49)|KDE 4.12.3
On 2014-03-11 17:02, upscope wrote:
> <CODE>
You have to use square brackets.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Carlos E. R. wrote:
> On 2014-03-11 17:02, upscope wrote:
>> <CODE>
>
> You have to use square brackets.
>
Sorry about that yesterday was a very confused day.
–
openSUSE 13.1(Linux 3.11.10-7-desktop x86_64|
Intel(R) Quad Core™ i5-4440 CPU @ 3.10GHz|8GB DDR3|
GeForce 8400GS (NVIDIA-Linux-x86_64-331.49)|KDE 4.12.3