Installing Debian on an Imac DV
John Winters
[snip]
> is your machine a `newworld' type, (colored case for desktops, made
> 1999 or later for powerbooks)
>
> if so debian can do this quite easily, you only need to download a
> couple small files and enter OpenFirmware to boot them. the rest of
> the system can be installed directly over the internet. (or a hard
> disk if you wish)
This seems to address my problem exactly. I've got an iMac DV and it
won't boot the Debian CD. Can you point me in the direction of
instructions for what these two files are and how to use them please?
I'm completely new to Macs but well versed in Linux so once I've got the
thing to boot I should be OK.
Am I right in thinking that once I've got something to boot I can
partition the hard disc (even though I've booted from it) and create the
itsy partition at the front, then a MacOS partition then the relevant
Linux partitions?
The machine also has a USB Zip drive - can it boot from that?
TIA,
John
--
John Winters. Wallingford, Oxon, England.
The Linux Emporium - the source for Linux CDs in the UK
See http://www.linuxemporium.co.uk/
--
To UNSUBSCRIBE, email to debian-powe...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Ethan Benson
>
> This seems to address my problem exactly. I've got an iMac DV and it
> won't boot the Debian CD. Can you point me in the direction of
> instructions for what these two files are and how to use them please?
> I'm completely new to Macs but well versed in Linux so once I've got the
> thing to boot I should be OK.
ftp.debian.org:/debian/dists/potato/main/disks-powerpc/current/powermac/linux
ftp.debian.org:/debian/dists/potato/main/disks-powerpc/current/powermac/images-1.44/root.bin
you also need a yaboot binary, you can get that from my web page (see
my .sig)
put all this at the root of your macos partition and create a
yaboot.conf like this:
device=hd:
image=linux
label=debian
initrd=root.bin
initrd-size=8192
then boot into OpenFirmware (command option o f) and run:
boot hd:,yaboot
you might have to specify a partition, im not sure what that is, there
are many useless cruft partitions macos hides from you, try 5, 6, 7
and 8 one will work.
you should then be in yaboot, press enter and you should be in
dbootstrap.
another option if you have another *nix box around is netboot, see my
netboot howto on my page too.
> Am I right in thinking that once I've got something to boot I can
> partition the hard disc (even though I've booted from it) and create the
> itsy partition at the front, then a MacOS partition then the relevant
> Linux partitions?
yes that is how i installed my system for the first time (back when
yaboot was buggy and would not work on scsi disks)
see my partitioning doc on my web page too. if you want to ditch
macos (an excellent idea) then clear the partition table so you don't
have all that sh*t cluttering it up. (my doc tells how to do this)
as usuall, first partition: 800K type Apple_Bootstrap.
> The machine also has a USB Zip drive - can it boot from that?
i don't think so.
let me know if you need any more help.
--
Ethan Benson
http://www.alaska.net/~erbenson/
Hadess
Quoting Ethan Benson <erbe...@alaska.net>:
>
> put all this at the root of your macos partition and create a
> yaboot.conf like this:
>
> device=hd:
>
> image=linux
> label=debian
> initrd=root.bin
> initrd-size=8192
>
> then boot into OpenFirmware (command option o f) and run:
>
> boot hd:,yaboot
Works nifty indeed. I've used this trick to install Debian on my iMac/DV this
week-end. I had a bit more problems with the iBook SE (the new one with DVD),
the kernel doesn't recognize the Rage 128 Mobility so the display *seems* to
hang after the "Booting..." message. Adding "novideo" to yaboot.conf solves the
problem. (I was using the stock kernel from the R0 CDs).
A couple of things, I'll like to see changed.
Daniel, I think you are responsible for the PPC boot-floppies: would you add
"eject" to it ? Otherwise, you have to use a paperclip to get the CD out on
multiple CD installs, with slot-loading iMacs.
Ethan, your mac-fdisk document should really be added to the Debian/PPC install
doc. Invaluable.
I still have to test XF4 on these 2 machines. Does the ati128 driver recognize
the Rage 128 Mobility ?
Cheers
/Hadess
http://hadess.net
Michel Dänzer
> I still have to test XF4 on these 2 machines. Does the ati128 driver
> recognize the Rage 128 Mobility ?
The latest CVS probably does, but it doesn't work nevertheless because it
can't cope with the flat panel :(
In the DRI PPC branch I have added an option "DisableFP" to surpass this
issue, so that might work (only at the full panel resolution though),
including 3d acceleration :)
Michel
--
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project
Hadess
> Hadess wrote:
>
> > I still have to test XF4 on these 2 machines. Does the ati128 driver
> > recognize the Rage 128 Mobility ?
>
> The latest CVS probably does, but it doesn't work nevertheless because
> it
> can't cope with the flat panel :(
>
> In the DRI PPC branch I have added an option "DisableFP" to surpass this
> issue, so that might work (only at the full panel resolution though),
> including 3d acceleration :)
What do the Debian XFree packages include ?
If I understand well, I could get:
X Strike-force deb packages
+ kernel patches from DRI/PPC
+ CVS ati128 driver from DRI/PPC
and it should (would...) work, or not ? I'm a bit confused with all these
different places I can get X from.
Also, could you make a snapshot (sources) available ? I don't have ways to
access CVS (f/w).
Thanks
PS: When done, I ask John Carmack for Quake3 on PPC/Linux ;P
/Hadess
http://hadess.net
Michel Dänzer
>
> Quoting Michel Dänzer <daen...@student.ethz.ch>:
>
> > Hadess wrote:
> >
> > > I still have to test XF4 on these 2 machines. Does the ati128 driver
> > > recognize the Rage 128 Mobility ?
> >
> > The latest CVS probably does, but it doesn't work nevertheless because
> > it can't cope with the flat panel :(
> >
> > In the DRI PPC branch I have added an option "DisableFP" to surpass this
> > issue, so that might work (only at the full panel resolution though),
> > including 3d acceleration :)
>
> What do the Debian XFree packages include ?
XFree86 CVS from sometime after 4.0.1c + PPC patches from Ani Joshi's rsync
tree.
> If I understand well, I could get:
> X Strike-force deb packages
> + kernel patches from DRI/PPC
The kernel stuff (DRM) is only needed for 3D, and it's in Ben's kernels now.
> + CVS ati128 driver from DRI/PPC
> and it should (would...) work, or not ?
Yes, it should. Be sure to use Option "DisableFP". If you forget that, you get
either garbage or a black screen, but you can abort the server with
ctrl-alt-backspace.
> I'm a bit confused with all these different places I can get X from.
It is confusing I guess :( All the stuff should eventually be merged into
standard XFree86 though.
> Also, could you make a snapshot (sources) available ? I don't have ways to
> access CVS (f/w).
No SSH? SourceForge uses an SSH tunnel for CVS. Anyway, I'll probably put up
new test binaries in the not too distant future and will announce them here.
> PS: When done, I ask John Carmack for Quake3 on PPC/Linux ;P
:) Might be better to ask Loki directly though ;)
Michel
--
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and the DRI project
Ethan Benson
> > > Ethan, your mac-fdisk document should really be added to the Debian/PPC install
> > > doc. Invaluable.
> >
>
> I'm currently reworking the mac-fdisk man page (which should be in the
> install section) to cover the 'reorder to place bootstrap partition before
> MacOS' trick. Plus I've fixed the problem with reordering partitions - on
> shifting partitions downward, there was a stupid off-by-one error in the
> code so the new partition index was always one less than intended. Very
> confusing when moving partition 4 to position 5 :-) Right now the correct
> semantics of reordering is 'insert partition <old> _before_ partition <new>
> but that doesn't seem the obvious one.
ah cool, i did notice that the broken man page link seems to have been
fixed since last time i looked. i still think my doc would be useful
to have in the debian install docs since its a more step by step
example of the partitioning process, to some this can be easier to
follow then a man page. i was looking at just adding a second link
next to the man page link.
Michael Schmitz
> > install section) to cover the 'reorder to place bootstrap partition before
>
> fixed since last time i looked. i still think my doc would be useful
:-) The first mac-fdisk version didn't have man pages, that came later.
> to have in the debian install docs since its a more step by step
> example of the partitioning process, to some this can be easier to
> follow then a man page. i was looking at just adding a second link
> next to the man page link.
Fine, the more info the better. We could also incorporate your mac-fdisk
tutorial in the /usr/doc material.
Michael
Hadess
I'm really annoying, sorry...
Quoting Michel Dänzer <dae...@relog.ch>:
> > What do the Debian XFree packages include ?
>
> XFree86 CVS from sometime after 4.0.1c + PPC patches from Ani Joshi's
> rsync
> tree.
Good enough for DRI ?
> > If I understand well, I could get:
> > X Strike-force deb packages
> > + kernel patches from DRI/PPC
>
> The kernel stuff (DRM) is only needed for 3D, and it's in Ben's kernels
> now.
Very good =)
For those like me who don't have access to CVS, rsync and other stuff like that,
you can get your kernels on http://kernel.xorsis.com/
They have just about everything: compiled, sources, patches for every PPC tree.
> > + CVS ati128 driver from DRI/PPC
> > and it should (would...) work, or not ?
>
> Yes, it should. Be sure to use Option "DisableFP". If you forget that,
> you get
> either garbage or a black screen, but you can abort the server with
> ctrl-alt-backspace.
Hmmm, does this also apply to Pismos ? They also use R128 (Mobility ?) AFAIK.
> No SSH? SourceForge uses an SSH tunnel for CVS. Anyway, I'll probably
> put up
> new test binaries in the not too distant future and will announce them
> here.
No SSH... I'm quite lucky we have a Debian mirror on the company intranet.
> > PS: When done, I ask John Carmack for Quake3 on PPC/Linux ;P
>
> :) Might be better to ask Loki directly though ;)
Hmmm, that and Unreal Tournament.
/me drooling
/Hadess
http://hadess.net
Michel Dänzer
> > > What do the Debian XFree packages include ?
> >
> > XFree86 CVS from sometime after 4.0.1c + PPC patches from Ani Joshi's
> > rsync tree.
>
> Good enough for DRI ?
No. To be exact, the 2D driver should be good, but you need the libGL stuff
from DRI. I guess I'll put all that in a seperate tarball for my next test
binaries.
Hint for the X packagers: the DRI stuff should be really easy to integrate
now. Just a few things down xc/lib/GL/mesa and in the r128 2D driver directory
have changed. But I don't know if there's already a plan how to package the
DRI stuff?
> > > + CVS ati128 driver from DRI/PPC
> > > and it should (would...) work, or not ?
> >
> > Yes, it should. Be sure to use Option "DisableFP". If you forget that,
> > you get either garbage or a black screen, but you can abort the server
> > with ctrl-alt-backspace.
This is already old news. It works out of the box on my Pismo, however the
flat panel code can potentially damage the panel, so there's another option to
disable it.
In any case you need to specify the panel dimensions, I'll put an example
XF86Config with my binaries.
> > > PS: When done, I ask John Carmack for Quake3 on PPC/Linux ;P
> >
> > :) Might be better to ask Loki directly though ;)
>
> Hmmm, that and Unreal Tournament.
> /me drooling
/me too...
Michel
--
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and the DRI project
Branden Robinson
> Hadess wrote:
>
> > > > What do the Debian XFree packages include ?
> > >
> > > XFree86 CVS from sometime after 4.0.1c + PPC patches from Ani Joshi's
> > > rsync tree.
> >
> > Good enough for DRI ?
>
> No. To be exact, the 2D driver should be good, but you need the libGL stuff
> from DRI. I guess I'll put all that in a seperate tarball for my next test
> binaries.
>
> Hint for the X packagers: the DRI stuff should be really easy to integrate
> now. Just a few things down xc/lib/GL/mesa and in the r128 2D driver directory
> have changed. But I don't know if there's already a plan how to package the
> DRI stuff?
I'm sorry, I need some more specific instructions than this.
* XFree86 periodically takes snapshots of the Mesa CVS tree for inclusion
in the XFree86 sources (xc/extras/Mesa)
* I periodically generate packages from XFree86 CVS (if they build and work
on my boxen)
Given those facts, what would you like me to do, specifically? It seems
too complicated to me to track Mesa sources in my XFree86 packages
independently of what XFree86 itself is doing.
--
G. Branden Robinson | The only way to get rid of a temptation
Debian GNU/Linux | is to yield to it.
bra...@debian.org | -- Oscar Wilde
http://www.debian.org/~branden/ |
Michel Dänzer
>
> On Wed, Oct 04, 2000 at 03:43:43PM +0200, Michel Dänzer wrote:
> > Hadess wrote:
> >
> > > > > What do the Debian XFree packages include ?
> > > >
> > > > XFree86 CVS from sometime after 4.0.1c + PPC patches from Ani Joshi's
> > > > rsync tree.
> > >
> > > Good enough for DRI ?
> >
> > No. To be exact, the 2D driver should be good, but you need the libGL
> > stuff from DRI. I guess I'll put all that in a seperate tarball for my
> > next test binaries.
> >
> > Hint for the X packagers: the DRI stuff should be really easy to integrate
> > now. Just a few things down xc/lib/GL/mesa and in the r128 2D driver
> > directory have changed. But I don't know if there's already a plan how to
> > package the DRI stuff?
>
> I'm sorry, I need some more specific instructions than this.
>
> * XFree86 periodically takes snapshots of the Mesa CVS tree for inclusion
> in the XFree86 sources (xc/extras/Mesa)
> * I periodically generate packages from XFree86 CVS (if they build and work
> on my boxen)
>
> Given those facts, what would you like me to do, specifically? It seems
> too complicated to me to track Mesa sources in my XFree86 packages
> independently of what XFree86 itself is doing.
Of course. I was just wondering if and how the DRI stuff is currently
integrated in your packages. I see the *_dri.so modules are in the
xserver-xfree86 package - they are useless without libGL though, so wouldn't
they rather belong there?
And I was wondering if it would be appropriate to include the changes from my
PPC DRI branch into your packages so that we have working DRI in the powerpc
packages now. May be better to wait until it finds its way into the XFree86
CVS though...
Michel
--
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project
Hadess
> > > > + CVS ati128 driver from DRI/PPC
> > > > and it should (would...) work, or not ?
> > >
> > > Yes, it should. Be sure to use Option "DisableFP". If you forget
> that,
> > > you get either garbage or a black screen, but you can abort the
> server
> > > with ctrl-alt-backspace.
>
> This is already old news. It works out of the box on my Pismo, however
> the
> flat panel code can potentially damage the panel, so there's another
> option to
> disable it.
>
> In any case you need to specify the panel dimensions, I'll put an
> example
> XF86Config with my binaries.
Hum, another question. I've already got the 4.0.1 PPC debs. Can I still use my
iBook with that ?
Cheers
/Hadess
http://hadess.net
Michel Dänzer
> Hum, another question. I've already got the 4.0.1 PPC debs. Can I still use
> my iBook with that ?
I don't understand your question, especially the 'still'?
It may not work, but you can try without Option "UseFBDev".
Michel
--
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project
Hadess
> Hadess wrote:
>
> > Hum, another question. I've already got the 4.0.1 PPC debs. Can I
> still use
> > my iBook with that ?
>
> I don't understand your question, especially the 'still'?
I mean, I know that DRI-PPC does work with the Rage 128 Mobility (you told me
about the option to disable the automatic detection, etc.), but is the version
packed in the X-Force .debs enough ?
> It may not work, but you can try without Option "UseFBDev".
Hum, that would answer my question.
Thanks =)
/Hadess
http://hadess.net
Daniel Jacobowitz
> > I'm sorry, I need some more specific instructions than this.
> >
> > * XFree86 periodically takes snapshots of the Mesa CVS tree for inclusion
> > in the XFree86 sources (xc/extras/Mesa)
> > * I periodically generate packages from XFree86 CVS (if they build and work
> > on my boxen)
> >
> > Given those facts, what would you like me to do, specifically? It seems
> > too complicated to me to track Mesa sources in my XFree86 packages
> > independently of what XFree86 itself is doing.
>
> Of course. I was just wondering if and how the DRI stuff is currently
> integrated in your packages. I see the *_dri.so modules are in the
> xserver-xfree86 package - they are useless without libGL though, so wouldn't
> they rather belong there?
>
>
> And I was wondering if it would be appropriate to include the changes from my
> PPC DRI branch into your packages so that we have working DRI in the powerpc
> packages now. May be better to wait until it finds its way into the XFree86
> CVS though...
>
That would be best - we don't want to get TOO much further out than we
already are.
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| d...@debian.org | | dm...@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/
Branden Robinson
> Of course. I was just wondering if and how the DRI stuff is currently
> integrated in your packages. I see the *_dri.so modules are in the
> xserver-xfree86 package - they are useless without libGL though, so wouldn't
> they rather belong there?
I've decided to put all XFree86 server modules in the xserver-xfree86
package as a tactic to prevent bug reports about being unable to find a
module package, or "THE X SURVUR SHOULD DEPEND ON THE XYZ SURVUR MODULE
BECAUSE SURVUR IZ BROKEN ON MY BOX W1THOUT THE XYZ MODULE. D00D!!1!1!"
(I get lots of bug reports like this, because of course every single
computer in the world is identical.)
I'm not 100% opposed to breaking some server modules out, but:
1) It needs to be done in a logical, coherent fashion, and me *must* avoid
anything resembling a "one-package-per-module" situation.
2) I want to be presented with a complete plan of action for handling
dependencies and virtual packages dependencies thus required.
> And I was wondering if it would be appropriate to include the changes from my
> PPC DRI branch into your packages so that we have working DRI in the powerpc
> packages now. May be better to wait until it finds its way into the XFree86
> CVS though...
I am more than happy to integrate PowerPC patches (DRI or otherwise) if
they:
1) Apply to my current source package. I know I make this difficult by
updating from CVS almost every day.
2) Don't break other architectures (either at compile or run-time). I
really dislike things like %ifarch in RPM .spec files.
I've been over these issues with Dan Jacobowitz, and unfortunately I think
accomplishing these 2 points is at present just too much work. So we may
end up waiting for Ani to make his fixes portable and push them to XFree86
CVS.
--
G. Branden Robinson | Experience should teach us to be most on
Debian GNU/Linux | our guard to protect liberty when the
bra...@debian.org | government's purposes are beneficent.
http://www.debian.org/~branden/ | -- Louis Brandeis
Michel Dänzer
>
> On Thu, Oct 05, 2000 at 09:59:01AM +0200, Michel Dänzer wrote:
> > Of course. I was just wondering if and how the DRI stuff is currently
> > integrated in your packages. I see the *_dri.so modules are in the
> > xserver-xfree86 package - they are useless without libGL though, so
> > wouldn't they rather belong there?
>
> I've decided to put all XFree86 server modules in the xserver-xfree86
> package as a tactic to prevent bug reports about being unable to find a
> module package, or "THE X SURVUR SHOULD DEPEND ON THE XYZ SURVUR MODULE
> BECAUSE SURVUR IZ BROKEN ON MY BOX W1THOUT THE XYZ MODULE. D00D!!1!1!"
> (I get lots of bug reports like this, because of course every single
> computer in the world is identical.)
*LOL*
However, these aren't server modules. They are loaded by libGL for direct
rendering. So I think the xlibgl1 package is the logical place for them.
> > And I was wondering if it would be appropriate to include the changes from
> > my PPC DRI branch into your packages so that we have working DRI in the
> > powerpc packages now. May be better to wait until it finds its way into
> > the XFree86 CVS though...
>
> I am more than happy to integrate PowerPC patches (DRI or otherwise) if
> they:
> 1) Apply to my current source package. I know I make this difficult by
> updating from CVS almost every day.
> 2) Don't break other architectures (either at compile or run-time). I
> really dislike things like %ifarch in RPM .spec files.
>
> I've been over these issues with Dan Jacobowitz, and unfortunately I think
> accomplishing these 2 points is at present just too much work. So we may
> end up waiting for Ani to make his fixes portable and push them to XFree86
> CVS.
Agreed. That is I'll take care of my stuff myself ;)
Michel
--
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project
Branden Robinson
> Branden Robinson wrote:
> >
> > On Thu, Oct 05, 2000 at 09:59:01AM +0200, Michel Dänzer wrote:
> > > Of course. I was just wondering if and how the DRI stuff is currently
> > > integrated in your packages. I see the *_dri.so modules are in the
> > > xserver-xfree86 package - they are useless without libGL though, so
> > > wouldn't they rather belong there?
> >
> > I've decided to put all XFree86 server modules in the xserver-xfree86
> > package as a tactic to prevent bug reports about being unable to find a
> > module package, or "THE X SURVUR SHOULD DEPEND ON THE XYZ SURVUR MODULE
> > BECAUSE SURVUR IZ BROKEN ON MY BOX W1THOUT THE XYZ MODULE. D00D!!1!1!"
> > (I get lots of bug reports like this, because of course every single
> > computer in the world is identical.)
>
> rendering. So I think the xlibgl1 package is the logical place for them.
Oh; this I didn't know, not yet knowing much about DRI. I'll re-examine
this.
--
G. Branden Robinson | You should try building some of the
Debian GNU/Linux | stuff in main that is modern...turning
bra...@deadbeast.net | on -Wall is like turning on the pain.
http://deadbeast.net/~branden/ | -- James Troup