Linux PARISC architecture development
 help / color / mirror / Atom feed
* [parisc-linux] PALO and ramdisk micro-howto
@ 2000-03-21 17:44 Paul Bame
  2000-03-21 21:40 ` Paul Bame
  2000-03-22 22:33 ` 5116
  0 siblings, 2 replies; 5+ messages in thread
From: Paul Bame @ 2000-03-21 17:44 UTC (permalink / raw)
  To: parisc-linux


Grab recent versions of these from CVS:
	palo sources
	linux-2.3/init/main.c
	linux-2.3/arch/parisc/kernel/setup.c

In palo/Makefile, comment out NFSROOT= and uncomment the RAMDISK= line
which assumes your ramdisk is the file ../linux-2.3/ramdisk.bin which
is the way we used to have things.  Make sure you have a ramdisk in that
file (or change RAMDISK=).

Next time you 'make palo' in your linux tree, palo inserts the ramdisk
inside lifimage and constructs a default kernel command line to use the
ramdisk.

I tried both the old ramdisk, and I turned willy's nfsroot into a
ramdisk, and both booted and loaded but died with that
'Kernel panic: Attempted to kill init!' message.  Looks like sash is
being started with some args it doesn't like and exiting with a usage
message.

	-P

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [parisc-linux] PALO and ramdisk micro-howto
  2000-03-21 17:44 [parisc-linux] PALO and ramdisk micro-howto Paul Bame
@ 2000-03-21 21:40 ` Paul Bame
  2000-03-22 22:33 ` 5116
  1 sibling, 0 replies; 5+ messages in thread
From: Paul Bame @ 2000-03-21 21:40 UTC (permalink / raw)
  Cc: parisc-linux


= I tried both the old ramdisk, and I turned willy's nfsroot into a
                                             ^^^^^ mkp's
= ramdisk, and both booted and loaded but died with that
= 'Kernel panic: Attempted to kill init!' message.  Looks like sash is
= being started with some args it doesn't like and exiting with a usage
= message.

Fixed by new palo/ipl.c

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [parisc-linux] PALO and ramdisk micro-howto
  2000-03-21 17:44 [parisc-linux] PALO and ramdisk micro-howto Paul Bame
  2000-03-21 21:40 ` Paul Bame
@ 2000-03-22 22:33 ` 5116
  2000-03-23  3:02   ` willy
  1 sibling, 1 reply; 5+ messages in thread
From: 5116 @ 2000-03-22 22:33 UTC (permalink / raw)
  To: Paul Bame; +Cc: parisc-linux

On 21 Mar, Paul Bame wrote:
> In palo/Makefile, comment out NFSROOT= and uncomment the RAMDISK= line
> which assumes your ramdisk is the file ../linux-2.3/ramdisk.bin which
> is the way we used to have things.  Make sure you have a ramdisk in that
> file (or change RAMDISK=).
> 
I tried this with my 715/50 and current CVS kernel and palo as of today.

I got the following results:

[...]

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
SCSI clock: 50000000
Lasi Scsi (53c700) found at 0xf0825100
scsi-ncr53c7xx : unsupported SCSI chip 700
scsi : 0 hosts.
scsi : detected total.
IP-Config: No network devices available.
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 600 blocks [1 disk] into ram disk... done. 
kernel BUG at block_dev.c:411! 
kernel BUG at block_dev.c:411!


Any ideas?

/Daniel

-- 
Daniel Engström - Lilla Fabriken AB - Technical Support
daniel@lillfab.se - Work related.  5116@telia.com - Private.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [parisc-linux] PALO and ramdisk micro-howto
  2000-03-22 22:33 ` 5116
@ 2000-03-23  3:02   ` willy
  2000-03-23 19:05     ` [parisc-linux] Eth0 trouble Thierry SIMONNET
  0 siblings, 1 reply; 5+ messages in thread
From: willy @ 2000-03-23  3:02 UTC (permalink / raw)
  To: 5116; +Cc: Paul Bame, parisc-linux

On Wed, Mar 22, 2000 at 11:33:21PM +0100, 5116@telia.com wrote:
> I tried this with my 715/50 and current CVS kernel and palo as of today.

> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> SCSI clock: 50000000
> Lasi Scsi (53c700) found at 0xf0825100
> scsi-ncr53c7xx : unsupported SCSI chip 700

hehehe... someone's going to have to fix that someday...

> scsi : 0 hosts.
> scsi : detected total.
> IP-Config: No network devices available.
> RAMDISK: ext2 filesystem found at block 0
> RAMDISK: Loading 600 blocks [1 disk] into ram disk... done. 
> kernel BUG at block_dev.c:411! 
> kernel BUG at block_dev.c:411!

those two are OK, they should disappear when we go to the latest Linus
tree.  What's happening at this point is that it's switching to serial
console.  You should be able to stay with PDC console for the time being,
though you can't use it as an input device, only output.  In the fullness
of time, we'll have a proper graphics console.  Stay tuned :-)

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [parisc-linux] Eth0 trouble
  2000-03-23  3:02   ` willy
@ 2000-03-23 19:05     ` Thierry SIMONNET
  0 siblings, 0 replies; 5+ messages in thread
From: Thierry SIMONNET @ 2000-03-23 19:05 UTC (permalink / raw)
  To: parisc-linux

I have generated new lifimages with differents methods (ramdisk, nfsroot and
disk) using palo.
I have the following messages :
    eth0: receive unit error
    eth0: Null rbd - oops!
     eth0: receive unit error
    eth0: Null rbd - oops!
    eth0: receive unit error
    eth0: Null rbd - oops!
    eth0: receive unit error
    eth0: Null rbd - oops!
....

Before this messages, everything is OK. sash works fine, and I can execute
some test programs. After that, I lost LAN connectivity.

My config is  : 712/80 Workstation, with latest binutils, gcc, linux-2.3 and
palo.

Have an idea?

THX

Th. SIMONNET

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2000-03-23 20:02 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-03-21 17:44 [parisc-linux] PALO and ramdisk micro-howto Paul Bame
2000-03-21 21:40 ` Paul Bame
2000-03-22 22:33 ` 5116
2000-03-23  3:02   ` willy
2000-03-23 19:05     ` [parisc-linux] Eth0 trouble Thierry SIMONNET

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox