User:Tonyr/Journal/Apr07 - Revision history

Tonyr: /* 17Apr07 */

2007-09-16T20:10:14Z

17Apr07

Tonyr: /* 17Apr07 */

2007-09-16T20:05:57Z

17Apr07

Tonyr: /* 29Apr07 */

2007-05-13T22:36:52Z

29Apr07

Tonyr: /* 29Apr07 */

2007-05-13T22:36:17Z

29Apr07

Tonyr: /* 29Apr07 */ Radeon R200 note

2007-05-13T22:35:16Z

29Apr07: Radeon R200 note

Tonyr at 03:28, 2 May 2007

2007-05-02T03:28:00Z

Tonyr: 30apr07 section: sample dhcpd.conf

2007-05-01T20:18:15Z

30apr07 section: sample dhcpd.conf

Tonyr: /* 29Apr07 */ radeon xorg.conf ref

2007-04-30T23:18:32Z

29Apr07: radeon xorg.conf ref

Tonyr: /* 29Apr07 */

2007-04-30T21:30:42Z

29Apr07

Tonyr: /* 29Apr07 */ powerbook takeapart

2007-04-30T21:27:10Z

29Apr07: powerbook takeapart

@@ Line 82: / Line 82: @@
 * The OpenFirmware version that is on the iMac I am using limits TFTP transfers to <=6MB.  The '''initrd''' files for edgy and feisty are both >6MB, so the boot process fails for those Ubuntu versions at the '''initrd.gz''' TFPT transfer step.  One solution for this that I saw suggested that several drivers can be removed from the '''initrd''' file (a '''cpio''' archive) to get the size down.  I tried that a couple of times, but was never able to get it to work:  the transfer succeeded, but the initrd fs wouldn't mount.  I blame that on my current lack of understanding about '''initrd''' file generation.  It may be that later versions of OpenFirmware, or even updated current versions, allow larger transfers, but I have found no evidence to support that at this point.
-* The '''yaboot.conf''' files in the netboot file sets use absolute path names '''/vmlinux''' and '''initrd.gz'''.  Something there is that does not like that very much, and the first TFT transfer, '''boot.msg''', fails saying that it cannot find the file.  Modifying '''yaboot.conf''' to remove the leading '''/''' from all file names fixes that.
+* The '''yaboot.conf''' files in the netboot file sets use absolute path names '''/vmlinux''' and '''/initrd.gz'''.  Something there is that does not like that very much, and the first TFT transfer, '''boot.msg''', fails saying that it cannot find the file.  Modifying '''yaboot.conf''' to remove the leading '''/''' from all file names fixes that.
 There is a [https://bugs.launchpad.net/ubuntu/+source/yaboot/+bug/26426 bug at Launchpad] about the TFTP transfer size dating back to Hoary, but nothing I could find about the absolute path names. Maybe it only applies to the method I'm using (separate DHCP and TFTP servers).

@@ Line 73: / Line 73: @@
 There is a set of netboot network installation files for Dapper (6.04) at [http://archive.ubuntu.com/ubuntu/dists/dapper/main/installer-powerpc/20051026ubuntu36/images/powerpc/netboot http://archive.ubuntu.com/ubuntu/dists/dapper/main/installer-powerpc/20051026ubuntu36/images/powerpc/netboot]
-Thee are several ways to implement the network boot process.  I did it at home where my Linksys router is the DHCP server and a Desktop Ubuntu system has a TFTP server.  All of the netboot files from the Ubuntu archive site are in a designated tftp directory.  An iMac booted into OpenFirmware an then issue the command
+There are several ways to implement the network boot process.  I did it at home where my Linksys router is the DHCP server and a Desktop Ubuntu system has a TFTP server.  All of the netboot files from the Ubuntu archive site are in a designated tftp directory.  An iMac booted into OpenFirmware an then issue the command
   boot enet:192.168.1.100,yaboot
 and get right into the network installation process, which early on asks for a URL from which to get the installation data.  The IP in that '''boot enet:''' command is the address of the TFTP server.  One recommended arrangement is to have the DHCP server and the TFTP server be on the same machine, in which case the '''boot''' command would be
@@ Line 97: / Line 97: @@
 The point is that PXE is not for PowerPC.
 ==18Apr07==

@@ Line 198: / Line 198: @@
 This process may actually work for Edgy also, but since FG (according to Martin) is headed for '''Feisty''' anyway, I'm not going to pursue that.  I think the way I went about trying to get smp to work in Edgy earlier was flawed, but it's a moot point now.
-'''Radeon R200 video support''<br>
+''Radeon R200 video support''<br>
 The installation problem alluded to earlier involved the video card.  The card in that particular machine was an ATI Radeon QL R200 (AGP). Xorg's '''radeon''' driver didn't recognize it, so '''X''' didn't start up (and so neither did '''gdm''').  Reconfiguring '''xserver-xorg''' didn't do any good, either.  This is all very strange, since the card is recognized successfully in Edgy.  I can only surmise that support for that particular card was dropped in the ATI video driver released with Feisty.
   FWIW, here is a [http://ubuntuforums.org/showthread.php?t=393174 thread] with an '''xorg.conf''' that is reported to work for this particular

@@ Line 198: / Line 198: @@
 This process may actually work for Edgy also, but since FG (according to Martin) is headed for '''Feisty''' anyway, I'm not going to pursue that.  I think the way I went about trying to get smp to work in Edgy earlier was flawed, but it's a moot point now.
+'''Radeon R200 video support''<br>
 The installation problem alluded to earlier involved the video card.  The card in that particular machine was an ATI Radeon QL R200 (AGP). Xorg's '''radeon''' driver didn't recognize it, so '''X''' didn't start up (and so neither did '''gdm''').  Reconfiguring '''xserver-xorg''' didn't do any good, either.  This is all very strange, since the card is recognized successfully in Edgy.  I can only surmise that support for that particular card was dropped in the ATI video driver released with Feisty.
   FWIW, here is a [http://ubuntuforums.org/showthread.php?t=393174 thread] with an '''xorg.conf''' that is reported to work for this particular

@@ Line 198: / Line 198: @@
 This process may actually work for Edgy also, but since FG (according to Martin) is headed for '''Feisty''' anyway, I'm not going to pursue that.  I think the way I went about trying to get smp to work in Edgy earlier was flawed, but it's a moot point now.
 The installation problem alluded to earlier involved the video card.  The card in that particular machine was an ATI Radeon QL R200 (AGP). Xorg's '''radeon''' driver didn't recognize it, so '''X''' didn't start up (and so neither did '''gdm''').  Reconfiguring '''xserver-xorg''' didn't do any good, either.  This is all very strange, since the card is recognized successfully in Edgy.  I can only surmise that support for that particular card was dropped in the ATI video driver released with Feisty.
   FWIW, here is a [http://ubuntuforums.org/showthread.php?t=393174 thread] with an '''xorg.conf''' that is reported to work for this particular
   card in Feisty.
@@ Line 211: / Line 219: @@
 *[http://www.xlr8yourmac.com/systems/PB_G4_15_AL_takeapart/AL_PB_G4_take-apart.html http://www.xlr8yourmac.com/systems/PB_G4_15_AL_takeapart/AL_PB_G4_take-apart.html]
 *[http://www.powerbookmedic.com/xcart1/files/G4aluminum15.pdf http://www.powerbookmedic.com/xcart1/files/G4aluminum15.pdf]
 ==30Apr07==

@@ Line 213: / Line 213: @@
-==30APr07==
+==30Apr07==
 ''Sample dhcpd.conf''
 courtesy of '''cliebow''' in irc channel #ltsp

← Older revision		Revision as of 20:18, 1 May 2007
Line 211:		Line 211:
	*[http://www.xlr8yourmac.com/systems/PB_G4_15_AL_takeapart/AL_PB_G4_take-apart.html http://www.xlr8yourmac.com/systems/PB_G4_15_AL_takeapart/AL_PB_G4_take-apart.html]		*[http://www.xlr8yourmac.com/systems/PB_G4_15_AL_takeapart/AL_PB_G4_take-apart.html http://www.xlr8yourmac.com/systems/PB_G4_15_AL_takeapart/AL_PB_G4_take-apart.html]
	*[http://www.powerbookmedic.com/xcart1/files/G4aluminum15.pdf http://www.powerbookmedic.com/xcart1/files/G4aluminum15.pdf]		*[http://www.powerbookmedic.com/xcart1/files/G4aluminum15.pdf http://www.powerbookmedic.com/xcart1/files/G4aluminum15.pdf]
		+
		+
		+	==30APr07==
		+	''Sample dhcpd.conf''
		+	courtesy of '''cliebow''' in irc channel #ltsp
		+	authoritative;
		+
		+	subnet 10.10.0.0 netmask 255.255.255.0 {
		+	range 10.10.0.20 10.10.0.250;
		+	option domain-name "cliebow.com";
		+	option domain-name-servers 10.10.0.1;
		+	option broadcast-address 10.10.0.255;
		+	option routers 10.10.0.1;
		+	option subnet-mask 255.255.255.0;
		+	if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
		+	filename "/ltsp/i386/pxelinux.0";
		+	}
		+	elsif substring (option vendor-class-identifier, 0, 9) = "AAPLBSDPC" {
		+	filename "/yaboot";
		+	option vendor-class-identifier "AAPLBSDPC";
		+	option vendor-encapsulated-options 01:01:02:08:04:01:00:00:01:82:
		+	05: # length
		+	69:6d:61:63:34; # hostname
		+	option root-path "/opt/ltsp/powerpc";
		+	}
		+
		+
		+	else{
		+	filename "/ltsp/i386/nbi.img";
		+	}
		+	if substring (option vendor-class-identifier, 0, 3) = "d-i" {
		+	option root-path "/opt/ltsp/powerpc";
		+	}
		+	else {
		+	option root-path "/opt/ltsp/i386";
		+	}
		+
		+	# option root-path "/opt/ltsp/powerpc";
		+	}

← Older revision		Revision as of 23:18, 30 April 2007
Line 199:		Line 199:

	The installation problem alluded to earlier involved the video card. The card in that particular machine was an ATI Radeon QL R200 (AGP). Xorg's '''radeon''' driver didn't recognize it, so '''X''' didn't start up (and so neither did '''gdm'''). Reconfiguring '''xserver-xorg''' didn't do any good, either. This is all very strange, since the card is recognized successfully in Edgy. I can only surmise that support for that particular card was dropped in the ATI video driver released with Feisty.		The installation problem alluded to earlier involved the video card. The card in that particular machine was an ATI Radeon QL R200 (AGP). Xorg's '''radeon''' driver didn't recognize it, so '''X''' didn't start up (and so neither did '''gdm'''). Reconfiguring '''xserver-xorg''' didn't do any good, either. This is all very strange, since the card is recognized successfully in Edgy. I can only surmise that support for that particular card was dropped in the ATI video driver released with Feisty.
		+	FWIW, here is a [http://ubuntuforums.org/showthread.php?t=393174 thread] with an '''xorg.conf''' that is reported to work for this particular
		+	card in Feisty.

@@ Line 206: / Line 206: @@
 ''PowerBook repair''<br>
-Some laptops came in last week. A couple of them were PowerBooks of recent vintage. Loren is working on several of them.  THere is one that powers up but won't boot for love nor money: not from HD, not from CD (finnix nor Mac OS 9, didn't have a PowerBook CD to try).  Here are a couple of links for opening/repairing Powerbooks that might be useful:
+Some laptops came in last week. A couple of them were PowerBooks of recent vintage. Loren is working on several of them.  There is one that powers up but won't boot for love nor money: not from HD, not from CD (finnix nor Mac OS 9, didn't have a PowerBook CD to try).  Here are a couple of links for opening/repairing Powerbooks that might be useful:
 *[http://www.xlr8yourmac.com/systems/PB_G4_15_AL_takeapart/AL_PB_G4_take-apart.html http://www.xlr8yourmac.com/systems/PB_G4_15_AL_takeapart/AL_PB_G4_take-apart.html]
 *[http://www.powerbookmedic.com/xcart1/files/G4aluminum15.pdf http://www.powerbookmedic.com/xcart1/files/G4aluminum15.pdf]

← Older revision		Revision as of 21:27, 30 April 2007
Line 203:		Line 203:
	''Netinstall/netboot''<br>		''Netinstall/netboot''<br>
	Matteo installed my modified Feisty powerpc netinstall files in the tftp server directory on machine '''schist''', and then we successfully got a Mac to boot into the net install process by using the OpenFirmware '''boot enet:''' syntax. That was enough for ''proof-of-concept''. The next step appears to be to get '''ltsp''' involved to somehow provide the configured installed image via '''rsync'''. I don't know how to do that, but Matteo said he did. Martin is looking to have both i386 and ppc images provided via '''ltsp'''.		Matteo installed my modified Feisty powerpc netinstall files in the tftp server directory on machine '''schist''', and then we successfully got a Mac to boot into the net install process by using the OpenFirmware '''boot enet:''' syntax. That was enough for ''proof-of-concept''. The next step appears to be to get '''ltsp''' involved to somehow provide the configured installed image via '''rsync'''. I don't know how to do that, but Matteo said he did. Martin is looking to have both i386 and ppc images provided via '''ltsp'''.
		+
		+
		+	''PowerBook repair''<br>
		+	Some laptops came in last week. A couple of them were PowerBooks of recent vintage. Loren is working on several of them. THere is one that powers up but won't boot for love nor money: not from HD, not from CD (finnix nor Mac OS 9, didn't have a PowerBook CD to try). Here are a couple of links for opening/repairing Powerbooks that might be useful:
		+	*[http://www.xlr8yourmac.com/systems/PB_G4_15_AL_takeapart/AL_PB_G4_take-apart.html http://www.xlr8yourmac.com/systems/PB_G4_15_AL_takeapart/AL_PB_G4_take-apart.html]
		+	*[http://www.powerbookmedic.com/xcart1/files/G4aluminum15.pdf http://www.powerbookmedic.com/xcart1/files/G4aluminum15.pdf]