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

Re: Mac Install Problems



Hi,

>> Right, but you need to install kernel and modules just to get the install
>> process satisfied. Don't ask me why this is, I haven't written dinstall.
>
>O.K. I finally got things installed and working (more or less). I even went
>back and installed the kernel image and modules and that part of the
>installation went fine.

Fine, proves I'm not the only one to succeed installing Debian on a Mac.
In fact, there's a few more Mac installations in the meantime. These people 
hang out on linux-mac68k, mostly.

>> >"Install Operating System Kernel and Modules", but the installation chokes
>> >on "Install the Base System" trying to extract base2_0.tgz from my HFS
>> >partition.  (It gives the message "unexpected end of file".)
>> 
>> That's new - are you sure you entered the right thing at the 'path to archive'
>> prompt? Use 'choose among list of archive files', HFS loves to produce junk
>> files with the same name as the data file, and tar sure chokes on that.
>
>This was my fault (more or less).  HFS support in the kernel image I was
>using (vmlinux-980506.ELF) was broken: the files showed up when you listed
>the directory, but everything had size zero.  I copied the kernel image off
>of the resc1440-mac.bin disk, fed it to Penguin, and I was able to extract
>the tar image during the installation.  

Can't believe that; HFS hasn't changed in ages (at least not in the last month
or so). What probably happened is that you selected one of the 
<path to Debian archive>/.finderinfo/base2_0.tgz 'junk' files (HFS metadata)
and some of these are 0 bytes, some a few k, none make sense. Imagine my 
amusement when installing packages off the HFS partition :-(

>My main task now is to get the ethernet card working . . . The first trouble
>seems to be with modules:  The kernel (which I took from resc1440-mac.bin)
>is 2.0.29, but the modules (which I took from amiga/drv1440.bin) are for a

Forget modules. The Mac kernels are compiled without module support, and with 
all available Mac hardware drivers configured (and hopefully enough of the
other stuff). That's mostly because I had enough Mac quirks to fight with and
couldn't be bothered to install modutils on my cross compile box. James tried
to fix up kernel-source (2.0.33pl1) for Mac and maybe build a kernel image and
modules, but I don't know what was the end of that.

>2.0.33 kernel (and things fail on boot-up with the warning "no modules
>present for this kernel").  And I'm not even sure if the driver I need is a
>module in this disk.  Any recommendations?  Is there a recommended kernel
>with the appropriate ethernet drivers compiled in?  (I have a IIci with the
>Apple ethernet card.)

The 'recommended' kernels (from the Mac port FTP site) all have the Daynaport 
driver compiled in. And that driver should also handle at least some Apple and
clone cards. You might check that the 'don't disable VBL interrupts'
box in the booter options is unchecked; activating that option mysteriously
shuts down Nubus interrupts.

>On a related note, the following shows up during boot-up:
>
>Scanning nubus slots:
>nubus: rewind of 32748
>board resource not found
>
>Does this mean anything important?

Bad news for you. The driver couldn't find the Nubus ROM on the ethernet card
and gave up. You'll have to get the kernel source and start poking around in
the driver to fix this...

	Michael


--
To UNSUBSCRIBE, email to debian-68k-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org




Reply to: