Differences between revisions 7 and 13 (spanning 6 versions)
Revision 7 as of 2006-05-29 00:41:48
Size: 1594
Comment:
Revision 13 as of 2009-03-16 03:30:18
Size: 1788
Editor: anonymous
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:


== kernel/quik/miboot status ==

||<rowbgcolor="#F0ECE6"> '''machine type'''||'''tester'''||'''boot method'''||'''boot kernel version'''||'''installed kernel'''||'''quik ok'''||'''miboot ok'''||'''remarks'''||
|| oldworld g3 || h01ger || Yoe's miboot floppies from 2006-12-31 || 2.6.18 || || || || ||
Line 37: Line 43:
 * Fix quik-install; it claims boot and root must be on the same partition, however this is not true, the limitation is that they must be on the same disk.
Line 40: Line 44:
 * ? Is BootX distributable. If so, should it be included on Etch distribution media?  * Q: ''? Is BootX distributable. If so, should it be included on Etch distribution media?'' A: ''Not distributable with debian''

Old World Macintosh and Macintosh Clone DebianInstaller Notes

kernel/quik/miboot status

machine type

tester

boot method

boot kernel version

installed kernel

quik ok

miboot ok

remarks

oldworld g3

h01ger

Yoe's miboot floppies from 2006-12-31

2.6.18

TODO

  • Get eject onto miBoot-enabled boot disk so manual ejection of floppies is unnecessary
  • Fix quik-install (currently it doesn't do the right thing in terms of setting the OF variables needed to boot using quik)
  • Proposed solution for quik-install
    • If /proc/device-tree can be included in the miBoot floppies (the hd-media and cd installs already include this support) I think I have the beginnings of a solution: If /proc/dev-tree/alias/screen exists
      • nvsetenv output-device screen
      • else
        • Search /sys for a device of type 'display' If there's more than one, ask which to use Set output-device to the OF firmware name (this information is supplied in same directory as the 'display' device)
      endif if /proc/dev-tree/alias/kbd exists
      • nvsetenv output-device kbd
      else
      • not sure, will have to check if there is a way to do this
      fi The boot-device fix: First you determine what device under /sys is the boot device's controller, then you figure out what that corresponds to under /proc/device-tree. Then you figure out the boot disk's OF name, based on it's /sys name.
  • Create patch for update of manual
  • Q: ? Is BootX distributable. If so, should it be included on Etch distribution media? A: Not distributable with debian