On Fri, Apr 13, 2001 at 07:38:46PM +0200, Alain Schroeder wrote: > On Fri, Apr 13, 2001 at 12:29:37PM -0500, Branden Robinson wrote: > > 1) The on-board Ethernet is not being detected by the kernel. This would [...] > > that the Linux MACE driver works on that machine). Is there a kernel > > command line option I can give (e.g., "eth0=mace" or something like that?) > > to rectify this, or is the MACE driver even built for the 68k kernel? > > > I can at least compile it in in 2.2.19... Maybe you need to upgrade your > kernel? Perhaps. I'll give the sourceforge 2.2.19-20010410 kernel a shot tonight. > > 2) I am getting *really* hard machine lockups during heavy disk access > > (such as, say, a dpkg --unpack of every package auto-selected by dselect). > > There doesn't seem to be Magic SysRq support in the stock kernel. I have > > to take the machine down with the power switch, and both times this has > > happened, the filesystem has been so f*cked that I had to fsck it manually. > > I do realize that these boxes are slow, however, after the second apparent > > lockup (dpkg --unpack mutt), I let the box sit for several hours just in > > case it was busy thinking about the operation. No go. It really was > > locked. > > > If you mac uses the mac53c9x driver for scsi you want to might want to > add mac53c9x=1,0 (1 scsi bus) or mac53c9x=2,0 (2 scsi busses) to your > boot command. The second does make my machine pretty stable (Quadra > 950). I only have one SCSI bus. What exactly is this argument going to do that isn't the default behavior? -- G. Branden Robinson | Reality is what refuses to go away when Debian GNU/Linux | I stop believing in it. branden@debian.org | -- Philip K. Dick http://www.debian.org/~branden/ |
Attachment:
pgp8wnHJZmBgC.pgp
Description: PGP signature