Re: install problems
Maybe try adding "earlycon=pdc" to kernel command line. I would of thought it would be
default.
Dave
On 2025-03-23 1:01 p.m., Christian Groessler wrote:
> On 3/16/25 11:40 PM, Helge Deller wrote:
>>> I suggest you install the machine with serial console. Then, after installing
>>> a newer kernel you should be able to boot the installed machine
>>> with text-mode STIcon.
>
>
> I've set the console to SERIAL_1, but it doesn't help.
>
> -----------
> Firmware Version 2.0
>
> Duplex Console IO Dependent Code (IODC) revision 1
>
> ------------------------------------------------------------------------------
> (c) Copyright 1995-2000, Hewlett-Packard Company, All rights reserved
> ------------------------------------------------------------------------------
>
> Processor Speed State Coprocessor State I/D Cache
> --------- -------- --------------------- ----------------- -------------
> 0 875 MHz Active Functional 768 kB/1536 kB
>
> Central Bus Speed: 120 MHz
>
> Available memory: 3221159936 bytes
> Good memory required: 33366016 bytes
>
> Primary boot path: FWSCSI.5.0
> Alternate boot path: SCSI.6.0
> Console path: SERIAL_1.9600.8.none
> Keyboard path: USB
>
> Processor is booting from first available device.
>
> To discontinue, press any key within 10 seconds.
>
> Boot terminated.
>
>
> ----- Main Menu -------------------------------------------------------------
>
> Command Description
> ------- -----------
> BOot [PRI|ALT|<path>] Boot from specified path
> PAth [PRI|ALT|CON|KEY [<path>]] Display or modify a path
> SEArch [DIsplay|[[IPL] [<path>]]] Search for boot devices
>
> COnfiguration [<command>] Access Configuration menu/commands
> INformation [<command>] Access Information menu/commands
> SERvice [<command>] Access Service menu/commands
>
> DIsplay Redisplay the current menu
> HElp [<menu>|<command>] Display help for menu or command
> RESET Restart the system
> -----
> Main Menu: Enter command > bo ide
> Interact with IPL (Y, N, Q)?> y
>
> Booting...
> Boot IO Dependent Code (IODC) revision 0
>
>
> HARD Booted.
> palo ipl 2.25 https://parisc.wiki.kernel.org - Tue, 18 Jun 2024 16:57:10 +0000
> Boot limited to sectors below 2GB: NO
>
> Boot image contains:
> 0/vmlinux32 5102748(0) bytes @ 0x1202800
> 0/vmlinux64 6162944(0) bytes @ 0x16e0800
> 0/ramdisk 17880911 bytes @ 0xe7800
>
> Information: No console specified on kernel command line. This is normal.
> PALO will choose the console currently used by firmware (serial).
> Current command line:
> 0/vmlinuz initrd=0/ramdisk console=ttyS0 TERM=vt102
> 0: 0/vmlinuz
> 1: initrd=0/ramdisk
> 2: console=ttyS0
> 3: TERM=vt102
>
> <#> edit the numbered field
> 'b' boot with this command line
> 'r' restore command line
> 'l <#/path> list dir from numbered partition with path
> 'x' reset and reboot machine
> ? b
>
> Command line for kernel: ' console=ttyS0 TERM=vt102 palo_kernel=0/vmlinuz'
> Selected kernel: /vmlinuz from partition 0
> Selected ramdisk: /ramdisk from partition 0
> Warning: kernel name doesn't end with 32 or 64 -- Guessing...
> This box can boot either 32 or 64-bit kernels...
> Both kernels available, choosing 64-bit kernel
> ELF64 executable
> Segment 0 load 0x000e0000 size 6107176 mediaptr 0x1000
> Segment 1 load 0x01e00000 size 25628 mediaptr 0x5d5000
> Loading ramdisk 17880911 bytes @ 3eee1000...
> Branching to kernel entry point 0x000e0000. If this is the last message you
> see, you may need to switch your console. This is a common symptom -- search
> the FAQ and mailing list at https://parisc.wiki.kernel.org
>
> -----------
>
> And then ... nothing
>
> Strange. Given that the older installation medium worked.
>
> regards,
> chris
>
--
John David Anglin dave.anglin@bell.net
Reply to: