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

Re: Debian on mac68k

On Tue, 23 Feb 2016, Mac User wrote:

> On 2/23/16 8:50 AM, John Paul Adrian Glaubitz wrote:
> > Use the kernel that Finn just created for your machine, see:
> >
> > > https://lists.debian.org/debian-68k/2016/02/msg00047.html
> thanks..  The kernel hung once at the "ABCFGHIJK"-on-a-white-screen,

Please add "earlyprintk" to the kernel parameters in Penguin.

I suspect that this hang happens because the bootloader doesn't disable 
slot interrupts. So you may sometimes see this hang if you first boot into 
MacOS with the ethernet card enabled and then boot into Linux using 

You should not see this problem with Emile. Also, you should not see this 
problem if you boot MacOS without bringing up an ethernet driver (e.g. 
restart holding down shift key).

> but then it booted successfully twice after that. It found the console,
> Farallon Ethermac card and SCSI disk, then it stopped for a few
> minutes after:
> "random: nonblocking pool is initialized"
> There were no further messages after:
> "systemd[1]: Failed to mount tmpfs at /sys/fs/cgroup: No such file
> or directory"

The kernel I sent has CONFIG_CGROUPS disabled, because that's how I like 
it. Obviously Debian configures their kernels differently than I do. I'll 
enable it and build another binary for you.

> I waited a while, but it never showed up on the network.
> I would guess that for some reason it's hanging before running any of 
> the init scripts from the tarball that I downloaded earlier.

Debian uses systemd and doesn't need init scripts, which is why you don't 
see any messages from those scripts.

> Is ADB any less stable with 4.1.18 than in Debian 3.1?  (I never noticed 
> any issues with it there, though I also never used the mouse).

In general, ADB works fine (on m68k and powerpc). Regarding the LC III, 
AFAIK, the Egret driver has always been unstable but YMMV. Having seen the 
code, I no longer take an interest in old v2.x kernels.

> Would it make sense to try using the 4.1.18 kernel with my old Debian 
> 3.1 filesystems?  I'd have to restore them from a backup (taking a few 
> hours at least).

It may work. Whereas, the current Debian distro is known to work.

If you boot the old Debian 3.1 using a recent kernel then you won't be 
able to log in at the console, because the ADB keycodes were changed 
sometime after the v2.2 kernel. (I'm thinking of the IIfx, which does 
not need the Egret driver.)


> thanks
> -Stan

Reply to: