[parisc-linux] Serial support in IPL

[parisc-linux] Serial support in IPL

[Pavel Roskin]

Hello!

I'm completely new to PA/Linux and I'm not subscribed to the list, so
excuse me my dummy questions.

I've got C160L without monitor. I also don't know how to connect the
console. There is a connector "HP-HIL" which is somewhat similar to RJ-45,
but I don't know the wiring, and I'm not sure if it's the PDC console.

If the hard drive is connected, I don't see anything interesting except a
packet on the ethernet interface containing words:

HP LAN loop back test packet. LAN2 driver version 1

If I disconnect the drive, the box sends a bootp request and then a tftp
request. I can feed it with the linux kernel, but I see nothing on the
serial port.

If I use a fake kernel it is requested only once. The real kernel is
requested two or three times. I believe, this means that IPL actually
tries to "rewind" tftp to get the kernel.

I'm affraid that I need a version of IPL with serial console support to
get any further. ipl_c.c contains encouraging words:

 * Revision 1.24 1999/10/15 19:30:30 deller
 *
 * The serial console works now !

But it is just revision 1.3 in the anonymous CVS. There must be historic
versions with serial support using different revision numbering, right?

Can anybody build a kernel with the serial support at least in IPL
(ideally, in the kernel too)? Thank you in advance.

Regards,
Pavel Roskin

Re: [parisc-linux] Serial support in IPL

[Matt Taggart]

Pavel Roskin writes...

> I've got C160L without monitor. I also don't know how to connect the
> console. There is a connector "HP-HIL" which is somewhat similar to RJ-45,
> but I don't know the wiring, and I'm not sure if it's the PDC console.

The console is probably set to graphics, but if you boot without a keyboard 
plugged in it should go to the first serial port(unless the console path is 
set to something weird).

> If the hard drive is connected, I don't see anything interesting except a
> packet on the ethernet interface containing words:
> 
> HP LAN loop back test packet. LAN2 driver version 1

It's booting off the primary path(the disk). The disk probably still has HP-UX 
on it and that packet is the result of the driver loading.

> If I disconnect the drive, the box sends a bootp request and then a tftp
> request.

In this case the primary path failed and it's trying the secondary path which 
is lan.

> I can feed it with the linux kernel, but I see nothing on the
> serial port.

A couple suggestions(obvious but worth checking),

- Make sure all keyboards are unplugged
- Have you tried both serial ports?
- Are you sure your serial console is working?
- If you are connecting computer to computer be sure to use a null modem cable.
- Use 9600,8,N,1

> If I use a fake kernel it is requested only once. The real kernel is
> requested two or three times. I believe, this means that IPL actually
> tries to "rewind" tftp to get the kernel.
> 
> I'm affraid that I need a version of IPL with serial console support to
> get any further. ipl_c.c contains encouraging words:
> 
>  * Revision 1.24 1999/10/15 19:30:30 deller
>  *
>  * The serial console works now !
> 

This only affect after the system starts booting. No matter what you should be 
seeing the firmware interface on the console(whatever it's set to).

If none of the above work it could be that your console path is set to 
something weird. You might be able to fix it by blindly changing it. If you 
can't get it to work let me know and I'll post a keystroke recipe to fix it.

-- 
Matt Taggart
taggart@fc.hp.com

Re: [parisc-linux] Serial support in IPL

[Philipp Rumpf]

On Wed, May 24, 2000 at 05:22:46PM -0400, Pavel Roskin wrote:
> I've got C160L without monitor. I also don't know how to connect the
> console. There is a connector "HP-HIL" which is somewhat similar to RJ-45,
> but I don't know the wiring, and I'm not sure if it's the PDC console.

This is the keyboard connector.  Some older C-class workstations have both
HIL and PS/2; forget it exists.

> If I use a fake kernel it is requested only once. The real kernel is
> requested two or three times. I believe, this means that IPL actually
> tries to "rewind" tftp to get the kernel.

IPL, parts of the kernel and the boot interface all use the console device
selected in nvram.  my guess is this is graphics (since you don't see
anything on your serial port when booting the machine ?), so you should
either connect a monitor or try to remove all keyboards.

> I'm affraid that I need a version of IPL with serial console support to
> get any further. ipl_c.c contains encouraging words:

You should make sure you have a working firmware console first (IPL does
not really care whether it's connected to serial or graphics).

>  * Revision 1.24 1999/10/15 19:30:30 deller
>  *
>  * The serial console works now !

That comment is in ipl_c.c only because the command line was changed and
it was set there back then.

	Philipp Rumpf

Re: [parisc-linux] Serial support in IPL

[Pavel Roskin]

Hello, Matt!

> A couple suggestions(obvious but worth checking),
> 
> - Make sure all keyboards are unplugged
> - Have you tried both serial ports?
> - Are you sure your serial console is working?

The cable was bad. Now it works!!! Thank you for the tip!

Now I can interact with firmware and IPL. I can edit the prompt and load
the kernel. But the kernel doesn't show anything:

Please enter the command-line:
/stand/vmlinux HOME=/ TERM=LINUX console=tty

SOM-Kernel:
aux_header_location: 00000080
som       : 01000080
exec_dfile: 00145000
exec_dsize: 000B9000
exec_dmem : C01F5000
exec_tfile: 00050000
exec_tsize: 000F4008
exec_tmem : C0100000
exec_bsize: 00060FE0
exec_entry: C0100000
Code at 0x00100000, size=0x000F4008
Data at 0x001F5000, size=0x000B9000
BSS  at 0x002AE000.
exec_entry: C0100000

Transferring control to kernel. (At entry point 0x00100000)

That's all I see. I have tried console=serial, console=ttyS0, I have tried
to remove the "console" parameter - no effect. I cannot see where that
"console" parameter is parsed.

I'm using Image-20000218.bin

Anyway, I have yet a lot of things to try (including compiling the latest
version). Thank you for your help.

Regards,
Pavel Roskin