TonysMacJournal Mar07 - Revision history

Tonyr: redirect

2007-03-24T05:45:53Z

redirect

Show changes

Tonyr: 21mar07 section

2007-03-21T21:15:31Z

21mar07 section

Tonyr: /* 20mar07 */

2007-03-21T00:21:21Z

20mar07

Tonyr: /* 20mar07 */ g3/500 video fix references

2007-03-21T00:20:42Z

20mar07: g3/500 video fix references

Tonyr: /* 20mar07 */ possible g3/500 video fix

2007-03-21T00:07:13Z

20mar07: possible g3/500 video fix

Tonyr: 20mar07 section

2007-03-20T23:51:45Z

20mar07 section

Tonyr: /* 16mar07 */

2007-03-19T00:51:06Z

16mar07

Tonyr at 00:42, 19 March 2007

2007-03-19T00:42:06Z

Tonyr: /* 16mar07 */ oem-config-prepare note

2007-03-19T00:40:49Z

16mar07: oem-config-prepare note

Tonyr: /* 16mar07 */ g3/500 update note

2007-03-18T17:31:18Z

16mar07: g3/500 update note

← Older revision		Revision as of 21:15, 21 March 2007
Line 149:		Line 149:
	* [http://nowonder.com/forums/unix-x11/292334-boot-problems-kernal-panics-2.html http://nowonder.com/forums/unix-x11/292334-boot-problems-kernal-panics-2.html]		* [http://nowonder.com/forums/unix-x11/292334-boot-problems-kernal-panics-2.html http://nowonder.com/forums/unix-x11/292334-boot-problems-kernal-panics-2.html]
	They suggest various '''xorg.conf''' modifications. One suggests using the '''r128''' driver instead of the '''ati''' driver.		They suggest various '''xorg.conf''' modifications. One suggests using the '''r128''' driver instead of the '''ati''' driver.
		+
		+
		+	==21mar07==
		+	''G4/533''<br>
		+	See [[#15mar07]] and [[#16mar07]].
		+
		+	Solution found. I read the referenced articles, decided to play with '''amixer''' to modify the contents of '''/var/lib/alsa/asound.state'''. and discovered the working combination of changes. So here is the deal.
		+	* After installation, add the line '''snd-powermac''' to /etc/modules
		+	* Run two '''amixer''' commands as root to modify mixer controls
		+	sudo amixer sset 'Auto Mute' off
		+	sudo amixer sset 'PC Speaker' on
		+
		+	''G3/500''<br>
		+	The solution described in the first reference mentioned in [[#20mar07]] works, so I stopped experimenting. Basically it says comment out some of the modules, and in the ati device section, turn off the FB option and add SWCursor and ForcePCIMode options.

@@ Line 143: / Line 143: @@
 ==20mar07==
-''Oem installation, G3/500''
+''Oem installation, G3/500''<br>
 There are two of them.  They came in together.  I'm inclined to believe they are both something called iMac DVSE. One of them has a flower pattern on the inside on the plastic case; I believe this one is called '''Flower Power'''. I think the other one is called '''Snow'''.  Neither of them perform very well after installation; graphics seem extremely slow, as reported in [[#15mar05]].  This appears to be a known problem in bugs and forums.  Here are some solutions.
 * [http://ubuntuforums.org/showthread.php?t=191080 http://ubuntuforums.org/showthread.php?t=191080]

@@ Line 144: / Line 144: @@
 ==20mar07==
 ''Oem installation, G3/500''
-There are two of them.  They came in together.  I'm inclined to believe they are both something called iMac DVSE. One of them has a flower pattern on the inside on the plastic case; I believe this one is called '''Flower Power'''. I think the other one is called '''Snow'''.  Neither of them perform very well after installation; graphics seem extremely slow, as reported in [[#15mar05]].  This appears to be a known problem discussed in the forums.  [http://ubuntuforums.org/showthread.php?t=191080 Here] is one such thread that suggests a solution.  Essentially it says to modify the modules list and video device section:
+There are two of them.  They came in together.  I'm inclined to believe they are both something called iMac DVSE. One of them has a flower pattern on the inside on the plastic case; I believe this one is called '''Flower Power'''. I think the other one is called '''Snow'''.  Neither of them perform very well after installation; graphics seem extremely slow, as reported in [[#15mar05]].  This appears to be a known problem in bugs and forums.  Here are some solutions.
+* [http://ubuntuforums.org/showthread.php?t=191080 http://ubuntuforums.org/showthread.php?t=191080]
-  look for the modules section in there insert a # before all but
+* [https://launchpad.net/ubuntu/+source/xorg-server/+bug/22667 https://launchpad.net/ubuntu/+source/xorg-server/+bug/22667]
+* [http://nowonder.com/forums/unix-x11/292334-boot-problems-kernal-panics-2.html http://nowonder.com/forums/unix-x11/292334-boot-problems-kernal-panics-2.html]
- load "dri"
+They suggest various '''xorg.conf''' modifications.  One suggests using the '''r128''' driver instead of the '''ati''' driver.

@@ Line 144: / Line 144: @@
 ==20mar07==
 ''Oem installation, G3/500''
-There are two of them.  They came in together.  I'm inclined to believe they are both something called iMac DVSE. One of them has a flower pattern on the inside on the plastic case; I believe this one is called 'Flower Power'. Neither of them perform very well after installation; graphics seem extremely slow, as reported in [[#15mar05]].
+There are two of them.  They came in together.  I'm inclined to believe they are both something called iMac DVSE. One of them has a flower pattern on the inside on the plastic case; I believe this one is called '''Flower Power'''. I think the other one is called '''Snow'''.  Neither of them perform very well after installation; graphics seem extremely slow, as reported in [[#15mar05]].  This appears to be a known problem discussed in the forums.  [http://ubuntuforums.org/showthread.php?t=191080 Here] is one such thread that suggests a solution.  Essentially it says to modify the modules list and video device section:

← Older revision		Revision as of 23:51, 20 March 2007
Line 140:		Line 140:
	I also wonder of the '''oem-config-prepare''' script is present in the normal install that we do, and if it would have the same effect.		I also wonder of the '''oem-config-prepare''' script is present in the normal install that we do, and if it would have the same effect.
	note 17mar07: no, it's not.		note 17mar07: no, it's not.
		+
		+
		+	==20mar07==
		+	''Oem installation, G3/500''
		+	There are two of them. They came in together. I'm inclined to believe they are both something called iMac DVSE. One of them has a flower pattern on the inside on the plastic case; I believe this one is called 'Flower Power'. Neither of them perform very well after installation; graphics seem extremely slow, as reported in [[#15mar05]].

@@ Line 135: / Line 135: @@
 When I rebooted the machine and tried to log in as '''oem''', the login and X startup process took a really, really long time, several minutes in fact.  The mouse cursor would disappear and reappear and not respond to mouse motion for a long time.  It makes me wonder about the integrity of the installation.  I did manage to get to a virtual console (CTL+ALT+F1), halt '''gdm''', and run the '''oem-config-prepare''' script from there.  It remains to be seen what happens on the next boot of that machine.
-  note 17mar07: It has more to do with the machine itself. The same behavior is present with a regular install.
+  note 17mar07: It has more to do with the machine itself. The same behavior is present with a regular install
-  Virtual console CLI works fine, implying that video/X might be involved.
+ on this particular machine.  Virtual console CLI works fine, implying that video/X might be involved.
 I also wonder of the '''oem-config-prepare''' script is present in the normal install that we do, and if it would have the same effect.
   note 17mar07: no, it's not.

@@ Line 113: / Line 113: @@
-/==16mar07==
+==16mar07==
 ''G4/533 Sound''<br>
 There are three separate audio output issues here.

@@ Line 113: / Line 113: @@
-==16mar07==
+/==16mar07==
 ''G4/533 Sound''<br>
 There are three separate audio output issues here.
@@ Line 120: / Line 120: @@
 # External speakers must be of the '''Apple Pro Speakers''' variety, the same ones that come with the iMac G4/700 Flat Panel machine.  These speakers draw power from the speaker jack with a special mini-jack connector.
-The sound device on this machine is called '''Tumbler'''.    In '''alsamixer''' it will show up as '''Powermac Tumbler'''.  To get it to show up, invoke '''modprobe snd-powermac'''; then '''aplay -l''' will show that the device is detected.  The onboard circuitry is apparently provided by a TI '''tas3004''' chip(?).
+The sound device on this machine is called '''Tumbler'''.    In '''alsamixer''' it will show up as '''Powermac Tumbler'''.  To get it to show up, invoke '''modprobe snd-powermac'''; then '''aplay -l''' will show that the device is detected, as will '''alsamixer'''.  The onboard circuitry is apparently provided by a TI '''tas3004''' chip(?).
 One of the previous references mentioned that plugging in headphones had an effect on the problem.  I plugged in my ipod headphones, an lo and behold the front speaker started working.  Unplug the headphones and the sound goes away.
@@ Line 132: / Line 132: @@
 ''Oem installation''<br>
-I did an '''oem''' installation formn the alternate CD on a 500MHz iMac.  The installation seemed to succeed.  The only noticeable difference in the process is that the username '''oem''' is provided automatically (it still prompted for a password to be created).  The closing message about rebooting says that the '''oem''' account has sudo privileges, that the installer may use that to make necessary post-installation modifications, and that the installer may then run the script '''oem-config-prepare''' to remove the oem account so that on the next boot, a new account with sudo privileges can be created by the owner/user.
+I did an '''oem''' installation from the alternate CD on a 500MHz iMac.  The installation seemed to succeed.  The only noticeable difference in the process is that the username '''oem''' is provided automatically (it still prompted for a password to be created).  The closing message about rebooting says that the '''oem''' account has sudo privileges, that the installer may use that to make necessary post-installation modifications, and that the installer may then run the script '''oem-config-prepare''' to remove the oem account so that on the next boot, a new account with sudo privileges can be created by the owner/user.
-When I rebooted the machine and tried to log in as '''oem''', the login and X startup process took a really, really long time, several minutes in fact.  The mouse cursor would disappear and reappear and not respond to mouse motion for a long time.  It makes me wonder about the integrity of the installation.  I did manage to get to a virtual console (CTL+ALT+F1), halt '''gdm''', and run the '''oem-config-prepare''' script form there.  It remains to be seen what happens on the next boot of that machine.
+When I rebooted the machine and tried to log in as '''oem''', the login and X startup process took a really, really long time, several minutes in fact.  The mouse cursor would disappear and reappear and not respond to mouse motion for a long time.  It makes me wonder about the integrity of the installation.  I did manage to get to a virtual console (CTL+ALT+F1), halt '''gdm''', and run the '''oem-config-prepare''' script from there.  It remains to be seen what happens on the next boot of that machine.
   note 17mar07: It has more to do with the machine itself. The same behavior is present with a regular install.
   Virtual console CLI works fine, implying that video/X might be involved.
 I also wonder of the '''oem-config-prepare''' script is present in the normal install that we do, and if it would have the same effect.