Re: MESH not found with 2.4.1 on 7500

2 messages, 2 authors, 2001-02-07 · open the first message on its own page

Re: MESH not found with 2.4.1 on 7500

From: Olaf Hering <hidden>
Date: 2001-02-07 06:54:04

On Tue, Feb 06, Takashi Oe wrote:
On Tue, 6 Feb 2001 17:37:09 +0100, Olaf Hering [off-list ref] wrote:
quoted
Hi,

the current 2.4.1 can not found the mesh scsi controller on my 7500/100.
It doesnt work with bootx and boot fd:vmlinux.coff.

Any ideas how to fix it?
As far as I can tell, your kernel is not getting that far.  Before MESH
message output, you should have something like:

SCSI subsystem driver Revision: 1.00

which is missing.  On my system, there is IDE related messages immediately
following the loop device message, and it's followed by (old) adb mouse
driver and PPP device message.  SCSI is after all of those.
Yeah, 2.4 changed the detection order.
And that loop device ... I guess I have to change the subject.


Gruss Olaf

--
 $ man clone

BUGS
       Main feature not yet implemented...

Re: MESH not found with 2.4.1 on 7500

From: Takashi Oe <hidden>
Date: 2001-02-07 07:19:11

On Wed, 7 Feb 2001 07:54:04 +0100, Olaf Hering [off-list ref] wrote:
On Tue, Feb 06, Takashi Oe wrote:
quoted
message output, you should have something like:

SCSI subsystem driver Revision: 1.00
The SCSI message is missing once again from your dmesg.  If you are
absolutely sure your kernel is built with SCSI support, do "make
distclean" and try again.  If the SCSI subsystem message is still missing,
attach your .config file along with dmesg.  You are working with bk tree,
right?  In any case, can't you at least find out where the machine check
is happening?


Takashi Oe

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help