[parisc-linux] C180 netbooting

[parisc-linux] C180 netbooting

[nick]

Hi, I'm trying to get a C180 booting entirely off the network.  I can load
a lifimage over bootp, however then I'm stuck.  There is a vmlinux
attached to the lifimage, but I can't figure out how to tell the loader to
boot that and use an NFSroot.  I have found a few suggestions (vmlinux
HOME=/ TERM=linux root=/dev/nfs nfsroot=mynfs:/dir) and that dosen't seem
to work.  Do I need a special lifimage?
	Nick

Re: [parisc-linux] C180 netbooting

[Helge Deller]

On Thursday 23 August 2001 18:58, nick@snowman.net wrote:
> Hi, I'm trying to get a C180 booting entirely off the network.  I can load
> a lifimage over bootp, however then I'm stuck.  There is a vmlinux
> attached to the lifimage, but I can't figure out how to tell the loader to
> boot that and use an NFSroot.  I have found a few suggestions (vmlinux
> HOME=/ TERM=linux root=/dev/nfs nfsroot=mynfs:/dir) and that dosen't seem
> to work.  Do I need a special lifimage?
> 	Nick

Hi Nick,

you forgot to mention which kernel version you booted.
In case you use a newer 2.4 kernel you'll have to add "ip=bootp" and should use 
an ip-address instead of <mynfs> in the nfsroot parameter.

Greetings,
Helge

Re: [parisc-linux] C180 netbooting

[nick]

I'm not even getting that far.  I can't get the linux kernel to start
booting, I always get errors along the lines of 
Current command line:
vmlinux HOME=/ TERM=vt100 root=/dev/nfs nfsroot=172.16.1.1:/mnt
console=ttyS0
 0: vmlinux
 1: HOME=/
 2: TERM=vt100
 3: root=/dev/nfs
 4: nfsroot=172.16.1.1:/mnt
 5: console=ttyS0
Edit which field?
(or 'b' to boot with this command line)? b
Kernel: partition 0 file vmlinux
ERROR: Read from boot device failed (status = -3).
byteio_read: seekread() returned -1 expected 2048

I'm assumeing paramater 0 is set wrong, but I've tried 0/vmlinux and
vmlinux, neither work.  What should I set it to?  Should I use a different
lif image?  Where can I get a lifimage known to work for this?
	Thanks
		Nick

On Thu, 23 Aug 2001, Helge Deller wrote:

> On Thursday 23 August 2001 18:58, nick@snowman.net wrote:
> > Hi, I'm trying to get a C180 booting entirely off the network.  I can load
> > a lifimage over bootp, however then I'm stuck.  There is a vmlinux
> > attached to the lifimage, but I can't figure out how to tell the loader to
> > boot that and use an NFSroot.  I have found a few suggestions (vmlinux
> > HOME=/ TERM=linux root=/dev/nfs nfsroot=mynfs:/dir) and that dosen't seem
> > to work.  Do I need a special lifimage?
> > 	Nick
> 
> Hi Nick,
> 
> you forgot to mention which kernel version you booted.
> In case you use a newer 2.4 kernel you'll have to add "ip=bootp" and should use 
> an ip-address instead of <mynfs> in the nfsroot parameter.
> 
> Greetings,
> Helge
> 
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux
> 

Re: [parisc-linux] C180 netbooting

[Matthew Wilcox]

On Thu, Aug 23, 2001 at 02:21:10PM -0400, nick@snowman.net wrote:
> I'm not even getting that far.  I can't get the linux kernel to start
> booting, I always get errors along the lines of 
> Current command line:
> vmlinux HOME=/ TERM=vt100 root=/dev/nfs nfsroot=172.16.1.1:/mnt
> console=ttyS0
>  0: vmlinux
>  1: HOME=/
>  2: TERM=vt100
>  3: root=/dev/nfs
>  4: nfsroot=172.16.1.1:/mnt
>  5: console=ttyS0
> Edit which field?
> (or 'b' to boot with this command line)? b
> Kernel: partition 0 file vmlinux
> ERROR: Read from boot device failed (status = -3).
> byteio_read: seekread() returned -1 expected 2048

You're running into a known palo bug.  Sometimes when you're editing
entries it does this.  No-one's tracked down the cause yet (and it
is sporadic).

-- 
Revolutions do not require corporate support.

Re: [parisc-linux] C180 netbooting

[nick]

Well thanks to your suggestion I tried not even attempting to change the
params and just see what happened.  what I got was
The 64-bit Kernel has started...
Determining PDC firmware type: Ancient Box (bus_id = 0x0)
Kernel panic: This system will probably never run Linux.

In idle task - not syncing

Is that as bad as it sounds?  Can I update the PDC firmware, or would that
not help?
	Thanks
		Nick

On Thu, 23 Aug 2001, Matthew Wilcox wrote:

> On Thu, Aug 23, 2001 at 02:21:10PM -0400, nick@snowman.net wrote:
> > I'm not even getting that far.  I can't get the linux kernel to start
> > booting, I always get errors along the lines of 
> > Current command line:
> > vmlinux HOME=/ TERM=vt100 root=/dev/nfs nfsroot=172.16.1.1:/mnt
> > console=ttyS0
> >  0: vmlinux
> >  1: HOME=/
> >  2: TERM=vt100
> >  3: root=/dev/nfs
> >  4: nfsroot=172.16.1.1:/mnt
> >  5: console=ttyS0
> > Edit which field?
> > (or 'b' to boot with this command line)? b
> > Kernel: partition 0 file vmlinux
> > ERROR: Read from boot device failed (status = -3).
> > byteio_read: seekread() returned -1 expected 2048
> 
> You're running into a known palo bug.  Sometimes when you're editing
> entries it does this.  No-one's tracked down the cause yet (and it
> is sporadic).
> 
> -- 
> Revolutions do not require corporate support.
> 
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux
> 

Re: [parisc-linux] C180 netbooting

[Matthew Wilcox]

On Thu, Aug 23, 2001 at 02:57:17PM -0400, nick@snowman.net wrote:
> Well thanks to your suggestion I tried not even attempting to change the
> params and just see what happened.  what I got was
> The 64-bit Kernel has started...
> Determining PDC firmware type: Ancient Box (bus_id = 0x0)
> Kernel panic: This system will probably never run Linux.
> 
> In idle task - not syncing
> 
> Is that as bad as it sounds?  Can I update the PDC firmware, or would that
> not help?
> 	Thanks

You should run a 32-bit kernel on the C180 :-)

-- 
Revolutions do not require corporate support.

Re: [parisc-linux] C180 netbooting

[nick]

Ok, only one more question hopefully.  I updated my PDC firmware from v2.7
to v6.1, that went fine.  I tried booting a 32bit lifimage, that worked
untill it got to the SCSI, at which point it spat out lots of errors for
id's 0, 1 and 2, then locked.  Is there something special I need to do to
keep C180's scsi happy?  I am useing the debian iso's lifimages right now.
	Nick

On Thu, 23 Aug 2001, Matthew Wilcox wrote:

> On Thu, Aug 23, 2001 at 02:57:17PM -0400, nick@snowman.net wrote:
> > Well thanks to your suggestion I tried not even attempting to change the
> > params and just see what happened.  what I got was
> > The 64-bit Kernel has started...
> > Determining PDC firmware type: Ancient Box (bus_id = 0x0)
> > Kernel panic: This system will probably never run Linux.
> > 
> > In idle task - not syncing
> > 
> > Is that as bad as it sounds?  Can I update the PDC firmware, or would that
> > not help?
> > 	Thanks
> 
> You should run a 32-bit kernel on the C180 :-)
> 
> -- 
> Revolutions do not require corporate support.
> 
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux
> 

Re: [parisc-linux] C180 netbooting

[Matthew Wilcox]

On Thu, Aug 23, 2001 at 03:33:36PM -0400, nick@snowman.net wrote:
> Ok, only one more question hopefully.  I updated my PDC firmware from v2.7
> to v6.1, that went fine.  I tried booting a 32bit lifimage, that worked
> untill it got to the SCSI, at which point it spat out lots of errors for
> id's 0, 1 and 2, then locked.  Is there something special I need to do to
> keep C180's scsi happy?  I am useing the debian iso's lifimages right now.

I don't recognise this problem, can you post the SCSI messages?

-- 
Revolutions do not require corporate support.

Re: [parisc-linux] C180 netbooting

[nick]

SCSI subsystem driver Revision: 1.00
sim700: Configuring 53c710 (SCSI-ID 7) at ffd06100, IRQ 86, options 0
scsi0: Revision 0x2
Post test1, istat 01, sstat0 00, dstat 84
sim700: WARNING IRQ probe failed, (returned 0)
scsi0: Good, target data areas are dma coherent
scsi0: test 1 completed ok.
scsi0 : LASI/Simple 53c7xx
scsi0: Unable to abort command for target 0
scsi0: Unable to send Bus Device Reset for target 0
scsi0: Unable to do SCSI bus reset
scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
scsi0: istat = 00, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00088018 (script[0x0006]), dsps = 00088448, target = 0
scsi0: Failing command for ID0
scsi0: Unable to abort command for target 0
scsi0: Unable to abort command for target 1
scsi0: Unable to send Bus Device Reset for target 1
scsi0: Unable to do SCSI bus reset
scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
scsi0: istat = 00, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00088018 (script[0x0006]), dsps = 00088448, target = 0
scsi0: Failing command for ID0
scsi0: Unable to abort command for target 1
  Vendor:           Model:                   Rev:     
  Type:   Direct-Access                      ANSI SCSI revision: 00
scsi0: Unable to abort command for target 2
scsi0: Unable to send Bus Device Reset for target 2
scsi0: Unable to do SCSI bus reset
scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
scsi0: istat = 00, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00089018 (script[0x0406]), dsps = 00089448, target = 0
scsi0: Failing command for ID1
scsi0: Unable to abort command for target 2


If you need more of the boot messages I can provide them.
	Nick

On Fri, 24 Aug 2001, Matthew Wilcox wrote:

> On Thu, Aug 23, 2001 at 03:33:36PM -0400, nick@snowman.net wrote:
> > Ok, only one more question hopefully.  I updated my PDC firmware from v2.7
> > to v6.1, that went fine.  I tried booting a 32bit lifimage, that worked
> > untill it got to the SCSI, at which point it spat out lots of errors for
> > id's 0, 1 and 2, then locked.  Is there something special I need to do to
> > keep C180's scsi happy?  I am useing the debian iso's lifimages right now.
> 
> I don't recognise this problem, can you post the SCSI messages?
> 
> -- 
> Revolutions do not require corporate support.
> 
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux
> 

Re: [parisc-linux] C180 netbooting

[Richard Hirst]

I don't recall any reports that C180 works, so it might just not be
supported.  

I can tell from your log that the scsi chip is basically working, it
has executed a few script instructions, but in each case it has hung
on a SELECT instruction.  If there is no device on a given ID the
chip should interrupt and say so; in this case there is no interrupt,
so the higher level code times out and resets.  From the log it appears
that the chip hasn't tried to generate an interrupt, so it is not just
an interrupt routing problem.

Do you have terminators on your scsi bus?

What devices are present, on which scsi IDs?

If you let it run on beyond this point does it continue to generate
errors for scsi IDs up to ID 6?

I guess the C180 has more than one scsi bus, these errors relate to the
narrow scsi bus, probably used for the CDROM.  If your disks are on
another scsi bus, and you can install va the network, you could perhaps
get going that way.

Feel free to send me a complete log of the boot msgs.

Richard


On Thu, Aug 23, 2001 at 10:19:16PM -0400, nick@snowman.net wrote:
> SCSI subsystem driver Revision: 1.00
> sim700: Configuring 53c710 (SCSI-ID 7) at ffd06100, IRQ 86, options 0
> scsi0: Revision 0x2
> Post test1, istat 01, sstat0 00, dstat 84
> sim700: WARNING IRQ probe failed, (returned 0)
> scsi0: Good, target data areas are dma coherent
> scsi0: test 1 completed ok.
> scsi0 : LASI/Simple 53c7xx
> scsi0: Unable to abort command for target 0
> scsi0: Unable to send Bus Device Reset for target 0
> scsi0: Unable to do SCSI bus reset
> scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
> scsi0: istat = 00, sstat0 = 00, sstat1 = 00, dstat = 00
> scsi0: dsp = 00088018 (script[0x0006]), dsps = 00088448, target = 0
> scsi0: Failing command for ID0
> scsi0: Unable to abort command for target 0
> scsi0: Unable to abort command for target 1
> scsi0: Unable to send Bus Device Reset for target 1
> scsi0: Unable to do SCSI bus reset
> scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
> scsi0: istat = 00, sstat0 = 00, sstat1 = 00, dstat = 00
> scsi0: dsp = 00088018 (script[0x0006]), dsps = 00088448, target = 0
> scsi0: Failing command for ID0
> scsi0: Unable to abort command for target 1
>   Vendor:           Model:                   Rev:     
>   Type:   Direct-Access                      ANSI SCSI revision: 00
> scsi0: Unable to abort command for target 2
> scsi0: Unable to send Bus Device Reset for target 2
> scsi0: Unable to do SCSI bus reset
> scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
> scsi0: istat = 00, sstat0 = 00, sstat1 = 00, dstat = 00
> scsi0: dsp = 00089018 (script[0x0406]), dsps = 00089448, target = 0
> scsi0: Failing command for ID1
> scsi0: Unable to abort command for target 2
> 
> 
> If you need more of the boot messages I can provide them.
> 	Nick
> 
> On Fri, 24 Aug 2001, Matthew Wilcox wrote:
> 
> > On Thu, Aug 23, 2001 at 03:33:36PM -0400, nick@snowman.net wrote:
> > > Ok, only one more question hopefully.  I updated my PDC firmware from v2.7
> > > to v6.1, that went fine.  I tried booting a 32bit lifimage, that worked
> > > untill it got to the SCSI, at which point it spat out lots of errors for
> > > id's 0, 1 and 2, then locked.  Is there something special I need to do to
> > > keep C180's scsi happy?  I am useing the debian iso's lifimages right now.
> > 
> > I don't recognise this problem, can you post the SCSI messages?
> > 
> > -- 
> > Revolutions do not require corporate support.
> > 
> > 
> > _______________________________________________
> > parisc-linux mailing list
> > parisc-linux@lists.parisc-linux.org
> > http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux
> > 
> 
> 
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux
> 

Re: [parisc-linux] C180 netbooting

[nick]

ok, what I've finally been able to do is boot to an nfsroot, partition sda
and sdb, then when I try to mke2fs any partition on either drive I get
errors along the lines of
init-2.04# SCSI device sdb: 4194685 512-byte hdwr sectors (2148 MB)
 sdb: sdb1 sdb2
SCSI device sdb: 4194685 512-byte hdwr sectors (2148 MB)
 sdb: sdb1 sdb2
Kernel panic: ccio-dma.c: ccio_alloc_range() I/O MMU is out of mapping
resources.

Kernel panic: ccio-dma.c: ccio_alloc_range() I/O MMU is out of mapping
resources.

In interrupt handler - not syncing
Kernel panic: ccio-dma.c: ccio_alloc_range() I/O MMU is out of mapping
resources.

In interrupt handler - not syncing
Kernel panic: ccio-dma.c: ccio_alloc_range() I/O MMU is out of mapping
resources.

In interrupt handler - not syncing
SysRq: Boot Sync Unmount showPc showTasks showMem loglevel0-8 tErm kIll
killalL
SysRq: Resetting

Is that usefull at all, and if not what would be usefull?
	Thanks
		Nick


On Tue, 28 Aug 2001, Richard Hirst wrote:

> I don't recall any reports that C180 works, so it might just not be
> supported.  
> 
> I can tell from your log that the scsi chip is basically working, it
> has executed a few script instructions, but in each case it has hung
> on a SELECT instruction.  If there is no device on a given ID the
> chip should interrupt and say so; in this case there is no interrupt,
> so the higher level code times out and resets.  From the log it appears
> that the chip hasn't tried to generate an interrupt, so it is not just
> an interrupt routing problem.
> 
> Do you have terminators on your scsi bus?
> 
> What devices are present, on which scsi IDs?
> 
> If you let it run on beyond this point does it continue to generate
> errors for scsi IDs up to ID 6?
> 
> I guess the C180 has more than one scsi bus, these errors relate to the
> narrow scsi bus, probably used for the CDROM.  If your disks are on
> another scsi bus, and you can install va the network, you could perhaps
> get going that way.
> 
> Feel free to send me a complete log of the boot msgs.
> 
> Richard
> 
> 
> On Thu, Aug 23, 2001 at 10:19:16PM -0400, nick@snowman.net wrote:
> > SCSI subsystem driver Revision: 1.00
> > sim700: Configuring 53c710 (SCSI-ID 7) at ffd06100, IRQ 86, options 0
> > scsi0: Revision 0x2
> > Post test1, istat 01, sstat0 00, dstat 84
> > sim700: WARNING IRQ probe failed, (returned 0)
> > scsi0: Good, target data areas are dma coherent
> > scsi0: test 1 completed ok.
> > scsi0 : LASI/Simple 53c7xx
> > scsi0: Unable to abort command for target 0
> > scsi0: Unable to send Bus Device Reset for target 0
> > scsi0: Unable to do SCSI bus reset
> > scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
> > scsi0: istat = 00, sstat0 = 00, sstat1 = 00, dstat = 00
> > scsi0: dsp = 00088018 (script[0x0006]), dsps = 00088448, target = 0
> > scsi0: Failing command for ID0
> > scsi0: Unable to abort command for target 0
> > scsi0: Unable to abort command for target 1
> > scsi0: Unable to send Bus Device Reset for target 1
> > scsi0: Unable to do SCSI bus reset
> > scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
> > scsi0: istat = 00, sstat0 = 00, sstat1 = 00, dstat = 00
> > scsi0: dsp = 00088018 (script[0x0006]), dsps = 00088448, target = 0
> > scsi0: Failing command for ID0
> > scsi0: Unable to abort command for target 1
> >   Vendor:           Model:                   Rev:     
> >   Type:   Direct-Access                      ANSI SCSI revision: 00
> > scsi0: Unable to abort command for target 2
> > scsi0: Unable to send Bus Device Reset for target 2
> > scsi0: Unable to do SCSI bus reset
> > scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
> > scsi0: istat = 00, sstat0 = 00, sstat1 = 00, dstat = 00
> > scsi0: dsp = 00089018 (script[0x0406]), dsps = 00089448, target = 0
> > scsi0: Failing command for ID1
> > scsi0: Unable to abort command for target 2
> > 
> > 
> > If you need more of the boot messages I can provide them.
> > 	Nick
> > 
> > On Fri, 24 Aug 2001, Matthew Wilcox wrote:
> > 
> > > On Thu, Aug 23, 2001 at 03:33:36PM -0400, nick@snowman.net wrote:
> > > > Ok, only one more question hopefully.  I updated my PDC firmware from v2.7
> > > > to v6.1, that went fine.  I tried booting a 32bit lifimage, that worked
> > > > untill it got to the SCSI, at which point it spat out lots of errors for
> > > > id's 0, 1 and 2, then locked.  Is there something special I need to do to
> > > > keep C180's scsi happy?  I am useing the debian iso's lifimages right now.
> > > 
> > > I don't recognise this problem, can you post the SCSI messages?
> > > 
> > > -- 
> > > Revolutions do not require corporate support.
> > > 
> > > 
> > > _______________________________________________
> > > parisc-linux mailing list
> > > parisc-linux@lists.parisc-linux.org
> > > http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux
> > > 
> > 
> > 
> > 
> > _______________________________________________
> > parisc-linux mailing list
> > parisc-linux@lists.parisc-linux.org
> > http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux
> > 
> 
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux
> 

Re: [parisc-linux] C180 netbooting

[Ryan Bradetich]

Arg.... I recongnize this message :(

Nick,

Can you tell me which kernel you are using, and how much
RAM you have in the C180?  This message means that the ccio
driver can not find any available resources in the IO page
directory to allocate for the DMA trasaction.

Thanks,

- Ryan

On Tue, Aug 28, 2001 at 06:12:45PM -0400, nick@snowman.net wrote:
> ok, what I've finally been able to do is boot to an nfsroot, partition sda
> and sdb, then when I try to mke2fs any partition on either drive I get
> errors along the lines of
> init-2.04# SCSI device sdb: 4194685 512-byte hdwr sectors (2148 MB)
>  sdb: sdb1 sdb2
> SCSI device sdb: 4194685 512-byte hdwr sectors (2148 MB)
>  sdb: sdb1 sdb2
> Kernel panic: ccio-dma.c: ccio_alloc_range() I/O MMU is out of mapping
> resources.
> 
> Kernel panic: ccio-dma.c: ccio_alloc_range() I/O MMU is out of mapping
> resources.
> 
> In interrupt handler - not syncing
> Kernel panic: ccio-dma.c: ccio_alloc_range() I/O MMU is out of mapping
> resources.
> 
> In interrupt handler - not syncing
> Kernel panic: ccio-dma.c: ccio_alloc_range() I/O MMU is out of mapping
> resources.
> 
> In interrupt handler - not syncing
> SysRq: Boot Sync Unmount showPc showTasks showMem loglevel0-8 tErm kIll
> killalL
> SysRq: Resetting
> 
> Is that usefull at all, and if not what would be usefull?
> 	Thanks
> 		Nick

Re: [parisc-linux] C180 netbooting

[nick]

I have 128meg of ram and am useing the current CVS source compiled
today.  Should I try another kernel?  I have to boot custom kernels as one
of the SCSI drivers hangs the system.
	Nick

On Tue, 28 Aug 2001, Ryan Bradetich wrote:

> Arg.... I recongnize this message :(
> 
> Nick,
> 
> Can you tell me which kernel you are using, and how much
> RAM you have in the C180?  This message means that the ccio
> driver can not find any available resources in the IO page
> directory to allocate for the DMA trasaction.
> 
> Thanks,
> 
> - Ryan
> 
> On Tue, Aug 28, 2001 at 06:12:45PM -0400, nick@snowman.net wrote:
> > ok, what I've finally been able to do is boot to an nfsroot, partition sda
> > and sdb, then when I try to mke2fs any partition on either drive I get
> > errors along the lines of
> > init-2.04# SCSI device sdb: 4194685 512-byte hdwr sectors (2148 MB)
> >  sdb: sdb1 sdb2
> > SCSI device sdb: 4194685 512-byte hdwr sectors (2148 MB)
> >  sdb: sdb1 sdb2
> > Kernel panic: ccio-dma.c: ccio_alloc_range() I/O MMU is out of mapping
> > resources.
> > 
> > Kernel panic: ccio-dma.c: ccio_alloc_range() I/O MMU is out of mapping
> > resources.
> > 
> > In interrupt handler - not syncing
> > Kernel panic: ccio-dma.c: ccio_alloc_range() I/O MMU is out of mapping
> > resources.
> > 
> > In interrupt handler - not syncing
> > Kernel panic: ccio-dma.c: ccio_alloc_range() I/O MMU is out of mapping
> > resources.
> > 
> > In interrupt handler - not syncing
> > SysRq: Boot Sync Unmount showPc showTasks showMem loglevel0-8 tErm kIll
> > killalL
> > SysRq: Resetting
> > 
> > Is that usefull at all, and if not what would be usefull?
> > 	Thanks
> > 		Nick
> 
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux
> 

Re: [parisc-linux] C180 netbooting

[nick]

Do you need any more boot messages?  I sent you the ones that looked
usefull/important, however I can send you the entire boot log. 
	Nick
> 
> I don't recognise this problem, can you post the SCSI messages?
> 
> -- 
> Revolutions do not require corporate support.
> 
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux
> 

Re: [parisc-linux] C180 netbooting

[Matthew Wilcox]

On Thu, Aug 23, 2001 at 12:58:34PM -0400, nick@snowman.net wrote:
> Hi, I'm trying to get a C180 booting entirely off the network.  I can load
> a lifimage over bootp, however then I'm stuck.  There is a vmlinux
> attached to the lifimage, but I can't figure out how to tell the loader to
> boot that and use an NFSroot.  I have found a few suggestions (vmlinux
> HOME=/ TERM=linux root=/dev/nfs nfsroot=mynfs:/dir) and that dosen't seem
> to work.  Do I need a special lifimage?

Well, I do this all the time, so it does work :-)  All I need to do is
change the NFSROOT in palo's Makefile to my server's IP address.  I'm
still crosscompiling; my string looks like this:
0/vmlinux64 HOME=/ TERM=linux root=/dev/nfs nfsroot=15.1.50.190 ip=bootp

-- 
Revolutions do not require corporate support.

Re: [parisc-linux] C180 netbooting

[nick]

Could you email or point me to the lifimage you use?
	Thanks
		Nick

On Thu, 23 Aug 2001, Matthew Wilcox wrote:

> On Thu, Aug 23, 2001 at 12:58:34PM -0400, nick@snowman.net wrote:
> > Hi, I'm trying to get a C180 booting entirely off the network.  I can load
> > a lifimage over bootp, however then I'm stuck.  There is a vmlinux
> > attached to the lifimage, but I can't figure out how to tell the loader to
> > boot that and use an NFSroot.  I have found a few suggestions (vmlinux
> > HOME=/ TERM=linux root=/dev/nfs nfsroot=mynfs:/dir) and that dosen't seem
> > to work.  Do I need a special lifimage?
> 
> Well, I do this all the time, so it does work :-)  All I need to do is
> change the NFSROOT in palo's Makefile to my server's IP address.  I'm
> still crosscompiling; my string looks like this:
> 0/vmlinux64 HOME=/ TERM=linux root=/dev/nfs nfsroot=15.1.50.190 ip=bootp
> 
> -- 
> Revolutions do not require corporate support.
> 
> 
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux
> 

Re: [parisc-linux] C180 netbooting

[Helge Deller]

On Thursday 23 August 2001 20:38, Matthew Wilcox wrote:
> On Thu, Aug 23, 2001 at 12:58:34PM -0400, nick@snowman.net wrote:
> > Hi, I'm trying to get a C180 booting entirely off the network.  I can
> > load a lifimage over bootp, however then I'm stuck.  There is a vmlinux
> > attached to the lifimage, but I can't figure out how to tell the loader
> > to boot that and use an NFSroot.  I have found a few suggestions (vmlinux
> > HOME=/ TERM=linux root=/dev/nfs nfsroot=mynfs:/dir) and that dosen't seem
> > to work.  Do I need a special lifimage?
>
> Well, I do this all the time, so it does work :-)  All I need to do is
> change the NFSROOT in palo's Makefile to my server's IP address.  I'm
> still crosscompiling; my string looks like this:
> 0/vmlinux64 HOME=/ TERM=linux root=/dev/nfs nfsroot=15.1.50.190 ip=bootp

I think this is the point. If you hardcode it in the Makefile and boot this lifimage
directly without user-interaction (bo lan ipl) it works. If you try to change it at
the prompt it won't boot. (I've just tested that)

Helge

Re: [parisc-linux] C180 netbooting

[Helge Deller]

Hi Mike,

I've just added your machine to the kernel hardware database, which should 
at least eliminate the following two "Unknown device" strings in the kernel log.

> Found devices:
> 1. Unknown device (4) at 0xf200c000, versions 0x3b, 0x0, 0x89, 0x0, 0x80
> 22. Unknown device (0) at 0xfffa0000, versions 0x59c, 0x0, 0x4, 0x0, 0x81


On Tuesday 28 August 2001 11:22, Helge Deller wrote:
> CVSROOT:	/home/cvs/parisc
> Module name:	linux
> Changes by:	deller	01/08/28 03:22:53
>
> Modified files:
> 	arch/parisc/kernel: hardware.c
>
> Log message:
> - add Raven U180 cpu and FW-SCSI entries to hardware-database
> acording to <nick@snowman.net>'s machine

Index: hardware.c
===================================================================
RCS file: /home/cvs/parisc/linux/arch/parisc/kernel/hardware.c,v
retrieving revision 1.22
diff -u -r1.22 hardware.c
--- hardware.c	2001/08/28 08:01:27	1.22
+++ hardware.c	2001/08/28 09:20:59
@@ -174,6 +174,7 @@
 	{HPHW_NPROC,0x59A,0x4,0x81,"Unlisted but reserved"},
 	{HPHW_NPROC,0x59B,0x4,0x81,"Raven U 160 (9000/780/C160)"},
 	{HPHW_NPROC,0x59D,0x4,0x81,"Raven U 200 (9000/780/C200)"},
+	{HPHW_NPROC,0x59C,0x4,0x81,"Raven U 180 (9000/780/C180)"},
 	{HPHW_NPROC,0x59E,0x4,0x91,"ThunderHawk T' 120"},
 	{HPHW_NPROC,0x59F,0x4,0x91,"Raven U 180+ (9000/780)"},
 	{HPHW_NPROC,0x5A0,0x4,0x81,"UL 1w T120 1MB/1MB (841/D260,D360)"},
@@ -340,6 +341,7 @@
 	{HPHW_A_DMA, 0x01F, 0x00089, 0x80, "SkyHawk 100/120 FW-SCSI"}, 
 	{HPHW_A_DMA, 0x027, 0x00089, 0x80, "Piranha 100 FW-SCSI"}, 
 	{HPHW_A_DMA, 0x032, 0x00089, 0x80, "Raven T' Core FW-SCSI"}, 
+	{HPHW_A_DMA, 0x03b, 0x00089, 0x80, "Raven U/L2 Core FW-SCSI"}, 
 	{HPHW_A_DMA, 0x03d, 0x00089, 0x80, "Merlin 160 Core FW-SCSI"},
 	{HPHW_A_DMA, 0x044, 0x00089, 0x80, "Mohawk Core FW-SCSI"}, 
 	{HPHW_A_DMA, 0x051, 0x00089, 0x80, "Firehawk FW-SCSI"},