Subject: Re: Enable osi_enet causes MoL-MacOS crash at end of boot
From: Bill Fink (billfink@capu.net)
Date: Fri Jun 16 2000 - 02:41:01 MDT
> On Thu, 15 Jun 2000, Peter F. Handel wrote:
>
> On Thu, 15 Jun 2000, Jan Sievers wrote:
> > get my ethernet card to work under MOL 0.9.48. If I disable osi_enet it
> > starts up fine, if I enable it crashes at the very end of the Mac OS 8.6
> > boot process.
> [snip]
> > unique_mol_ethernet: yes
>
> Have you tried setting this to "no"?
I second Peter's suggestion (BTW, "no" is the default setting).
I've also seen cases where I've had to reboot Linux to get the
Ethernet hardware into a pristine state for changes to the
unique_mol_ethernet parameter to take affect. I'd be interested
in knowing what manufacturer and model of Ethernet interface you're
using, especially if switching the unique_mol_ethernet parameter
to "no" is sufficient to cure your problem. It appears you're
using an Apple NIC (built-in?). I couldn't get the Apple BMAC
hardware on a friend's PowerBook to work with unique_mol_ethernet
set to "yes", but I never saw any MOL crashes.
I'd be interested in general in receiving any reports from people
trying out the unique_mol_ethernet parameter set to "yes", either
positive or negative. Please specify the manufacturer and model
of the Ethernet interface, type of Ethernet controller chip
(from dmesg | grep eth), driver being used (e.g. tulip or de4x5),
Linux kernel version and boot method (e.g. quik, bootx, miboot, or
yaboot), MOL version and boot method (oldworld or newworld), and
MacOS and MacOS ROM versions. If that's asking too much, a simple
message saying Brand X works or doesn't work would still be useful.
To test it out, I suggest rebooting Linux first so that the Ethernet
hardware is in a clean state when MOL is started up.
-Bill
This archive was generated by hypermail 2a24 : Fri Jun 16 2000 - 02:43:21 MDT