[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Kernel+Installer for hardisk boot on pb5300c



To whom it may concern,

I'm experimenting with running linux on a powerbook 5300c. While I know that debian doesn't officially support this platform, i've found experimental support at:

http://nubus-pmac.sourceforge.net/


My machine currently has 56megs of ram and the factory 750mb hard drive. What is the status of support for nubus powermacs? I plan on using a pcmcia 10/100 ethernet adapter (The card is a 3com 3CCFE574BT which is listed as supported by the pcmcia-cs project) and possibly a prism 802.11b card. I followed the first part of the instructions for installing on the pb1400c:

(http://www.icedtrip.net/guides/woody_1400.txt )

I achived early success in booting the woody installer kernel with the MkLinux booter and managed to partition the drive. However, i've hit a snag. The author used a scsi drive to hold iso images from which to install. That worked because that kernel supported scsi on the 1400. But it doesn't support scsi on the 5300. The 2.4.27 nubus kernel, however, does have scsi support, but this kernel doesn't have an installer image. I'm wondering if someone could either:

   a) make a 2.4.27 nubus kernel+{sarge | woody}-installer image
   b) point me in the right direction for doing the above myself
c) offer some suggestion as to how i might otherwise install woody or sarge Powerbooks can operate in scsi-disk mode so I could potentially force-feed packages onto the drive. I have a working debian PC with a scsi controller
       but i'm not sure how to proceed.

I also have a working 9600 (running OS 8.6 -- and it has to stay that way for reasons i don't wish to go into) One thing I haven't tried is booting the sarge installer from that machine and installing onto the laptop. Is this likely to work?

As related question if the kernel drivers for the ethernet card I plan to use will work on a powermac? (experimental PCMCIA support has been added)

Thanks in advance,
Brandon Lewis



Reply to: