ThinkPad/A30/SUSE - Revision history

Woozle: removing obsolete navigation links after moving

2014-12-22T14:41:10Z

removing obsolete navigation links after moving

← Older revision		Revision as of 14:41, 22 December 2014
Line 1:		Line 1:
	~~[[Computing]]: [[Linux]]: [[{{PAGENAME}}\|Thinkpad A30]]{{seedling}}~~
	This article is about running [[SUSE]] [[Linux]] on an IBM Thinkpad A30.		This article is about running [[SUSE]] [[Linux]] on an IBM Thinkpad A30.
	==From The Hypertwins==		==From The Hypertwins==
	===~~Overview~~===		===Overall===
	We basically had no troubles installing or running the system, aside from two minor incidents:		We basically had no troubles installing or running the system, aside from two minor incidents:
	* The mouse-wheel somehow got deactivated; to reactivate it, we ran (after a bit of hunting) SaX2 (K -> System -> Configuration -> Configure X11 system) which has a mouse configuration page.		* The mouse-wheel somehow got deactivated; to reactivate it, we ran (after a bit of hunting) SaX2 (K -> System -> Configuration -> Configure X11 system) which has a mouse configuration page.

Woozle: Woozle moved page SUSE on a Thinkpad A30 to ThinkPad/A30/SUSE: reorganizing using subpages

2014-12-22T14:38:36Z

Woozle moved page SUSE on a Thinkpad A30 to ThinkPad/A30/SUSE: reorganizing using subpages

← Older revision	Revision as of 14:38, 22 December 2014
(No difference)

Woozle: /* Installing Packages */ moved to new SUSE page

2006-04-02T22:41:25Z

Installing Packages: moved to new SUSE page

← Older revision		Revision as of 22:41, 2 April 2006
Line 25:		Line 25:

	We were not able to get the thinkpad CLI applet to work.		We were not able to get the thinkpad CLI applet to work.
	~~===Installing Packages===~~
	~~''(This should eventually be moved to a general [[SUSE]] article, as it doesn't pertain to the Thinkpad in particular.)''~~

	Having installed a package (in this case, "xpuzzles"), how do you figure out how to run the application(s)? In debian-based distros, [[synaptic]] will at least tell you what files it installed, from which you can figure out what command(s) will invoke it (and whether or not it created any menu entries). But [[yum]] (a Red Hat package manager) and [[YaST]] (the SUSE package manager) seem to lack this feature. (As does Aptitude, though I think the [[CLI]] [[apt (command)\|apt]] can still get the info if you know how to use it.)

	~~Or, [[Htwiki:YaST Today\|in other words]]...~~

Woozle: /* Thinkpad Configuration */ installing packages

2006-02-09T02:03:07Z

Thinkpad Configuration: installing packages

← Older revision		Revision as of 02:03, 9 February 2006
Line 25:		Line 25:

	We were not able to get the thinkpad CLI applet to work.		We were not able to get the thinkpad CLI applet to work.
			===Installing Packages===
			''(This should eventually be moved to a general [[SUSE]] article, as it doesn't pertain to the Thinkpad in particular.)''

			Having installed a package (in this case, "xpuzzles"), how do you figure out how to run the application(s)? In debian-based distros, [[synaptic]] will at least tell you what files it installed, from which you can figure out what command(s) will invoke it (and whether or not it created any menu entries). But [[yum]] (a Red Hat package manager) and [[YaST]] (the SUSE package manager) seem to lack this feature. (As does Aptitude, though I think the [[CLI]] [[apt (command)\|apt]] can still get the info if you know how to use it.)

			Or, [[Htwiki:YaST Today\|in other words]]...

Woozle at 19:46, 8 February 2006

2006-02-08T19:46:46Z

New page

[[Computing]]: [[Linux]]: [[{{PAGENAME}}|Thinkpad A30]]{{seedling}}
This article is about running [[SUSE]] [[Linux]] on an IBM Thinkpad A30.
==From The Hypertwins==
===Overview===
We basically had no troubles installing or running the system, aside from two minor incidents:
* The mouse-wheel somehow got deactivated; to reactivate it, we ran (after a bit of hunting) SaX2 (K -> System -> Configuration -> Configure X11 system) which has a mouse configuration page.
* The system began running rather slowly at one point, and [[KTorrent]] kept locking up; a reboot displayed error messages accessing sectors on the hard drive, so we ran [[SpinRite]], which found and fixed a bad sector. After that, things were much happier.

We did experience a bit of trouble trying to use the Thinkpad-specific configuration utilities, so here's a bit more on that.
===Thinkpad Configuration===
We noticed that if we booted up ''without'' the (PS/2-connector) mouse plugged in and then connected it after booting up, we could use both the mouse and the eraserhead/keyboard-buttons as mouse controls – whereas if we booted up with the PS/2 mouse plugged in, the eraserhead/keyboad-buttons were disabled. We wanted to see if any of the Thinkpad-specific configuration applets could change this.

There appear to be two places which contain such configuration applets:
* K -> Control Center -> System Administration -> IBM Thinkpad Laptop (which I'll call "thinkpad control module")
* console: configure-thinkpad (which I'll call "thinkpad CLI applet")

On first attempt to run the thinkpad control module, the right panel gave an error message which turned out to be slightly erroneous. Here are the commands which actually work, for enabling the module (run as [[root]]):
modprobe nvram
mknod /dev/nvram c 10 144
chmod 666 /dev/nvram

("chmod 664" apparently works under most circumstances; only certain models need global-write permission)

After running these commands, click away from the thinkpad control module and then back on it again; it should now work properly.

We were not able to get the thinkpad CLI applet to work.