[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Warning: unable to open an initial console. During install.



Hello,

I'm trying to install debian sarge on HP-9000 A400.
Server info:

 Processor   Speed            State           CoProcessor State  Cache Size
Number State Inst Data --------- -------- --------------------- ----------------- ------------ 0 440 MHz Active Functional 512 KB 1 MB

Central Bus Speed (in MHz) : 111 Available Memory : 655360 KB
 Good Memory Required        :      15364  KB

I'm booting system using external scsi CD-ROM drive:

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] [<path>]           Display or modify a path
    SEArch [DIsplay|IPL] [<path>]     Search for boot devices

    COnfiguration menu                Displays or sets boot values
    INformation menu                  Displays hardware information
    SERvice menu                      Displays service commands

    DIsplay                           Redisplay the current menu
    HElp [<menu>|<command>]           Display help for menu or command
    RESET                             Restart the system
----
Main Menu: Enter command or menu > sea

Searching for potential boot device(s)
This may take several minutes.

To discontinue search, press any key (termination may not be immediate).


  Path#  Device Path (dec)  Device Path (mnem)  Device Type
  -----  -----------------  ------------------  -----------
P0 0/0/1/1.15 intscsia.15 Random access media P1 0/0/2/0.3 extscsib.3 Random access media P2 0/0/2/1.15 intscsib.15 Random access media

Main Menu: Enter command or menu > bo p1
Interact with IPL (Y, N, or Cancel)?> y

Booting...
Boot IO Dependent Code (IODC) revision 1


HARD Booted.
palo ipl 1.5 root@c3k Fri May 14 16:17:38 MDT 2004

Boot image contains:
   0/vmlinux32 4319117 bytes @ 0x189e800
   0/vmlinux64 5820539 bytes @ 0x1311000
   0/ramdisk 6233937 bytes @ 0xd16000

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/vmlinux root=/dev/ram initrd=0/ramdisk init=/linuxrc' console=ttyS0 TERM=vt102
0: '0/vmlinux
1: root=/dev/ram
2: initrd=0/ramdisk
3: init=/linuxrc'
4: console=ttyS0
5: TERM=vt102

<#>    edit the numbered field
'b'    boot with this command line
'r'    restore command line
'l'    list dir
? 5
TERM=vt100
Current command line:
'0/vmlinux root=/dev/ram initrd=0/ramdisk init=/linuxrc' console=ttyS0 TERM=vt100
0: '0/vmlinux
1: root=/dev/ram
2: initrd=0/ramdisk
3: init=/linuxrc'
4: console=ttyS0
5: TERM=vt100

<#>    edit the numbered field
'b'    boot with this command line
'r'    restore command line
'l'    list dir
? b

System selects 64bit kernel and it's ok (I have another A400 running woody, and it is 64bit only machine).
Here is full console ouput after boot.


Command line for kernel: 'root=/dev/ram init=/linuxrc' console=ttyS0 TERM=vt100 palo_kernel=0'0/vmlinux'
Selected kernel: '0/vmlinux from partition 0
Selected ramdisk: /ramdisk from partition 0
Warning: kernel name doesn't end with 32 or 64 -- Guessing... Choosing 64-bit kernelELF64 executable
Entry 00100000 first 00100000 n 3
Segment 0 load 00100000 size 3822080 mediaptr 0x1000
Segment 1 load 004a8000 size 318168 mediaptr 0x3a7000
Segment 2 load 004f8000 size 372869 mediaptr 0x3f5000
Loading ramdisk 6233937 bytes @ 279fd000...
Branching to kernel entry point 0x00100000.  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 parisc-linux.org


********** VIRTUAL FRONT PANEL **********
System Boot detected
*****************************************
LEDs:  RUN      ATTENTION     FAULT     REMOTE     POWER
      FLASH    FLASH         FLASH     OFF        ON
LED State: Unexpected Reboot. Running non-OS code. Non-critical error detected.
Check Chassis and Console Logs for error messages.

processor                 system initialization      1C00

*****************************************

************ EARLY BOOT VFP *************
End of early boot detected
*****************************************
2, 0x0, 0x582, 0x0000b }
3. Elroy PCI Bridge at 0xfffffffffed30000 [0/0] { 13, 0x0, 0x782, 0x0000a }
4. Elroy PCI Bridge at 0xfffffffffed34000 [0/2] { 13, 0x0, 0x782, 0x0000a }
5. Elroy PCI Bridge at 0xfffffffffed38000 [0/4] { 13, 0x0, 0x782, 0x0000a }
6. Elroy PCI Bridge at 0xfffffffffed3c000 [0/6] { 13, 0x0, 0x782, 0x0000a }
7. Memory at 0xfffffffffed08000 [8] { 1, 0x0, 0x09b, 0x00009 }
Enabling PDC_PAT chassis codes support.
CPU(s): 1 x PA8500 (PCX-W) at 440.000000 MHz
SBA found Astro 2.1 at 0xfffffffffed00000
lba version TR4.0 (0x5) found at 0xfffffffffed30000
lba version TR4.0 (0x5) found at 0xfffffffffed34000
lba version TR4.0 (0x5) found at 0xfffffffffed38000
lba version TR4.0 (0x5) found at 0xfffffffffed3c000
SCSI subsystem initialized
TC classifier action (bugs to netdev@oss.sgi.com cc hadi@cyberus.ca)
STI GSC/PCI core graphics driver Version 0.9a
unwind_init: start = 0x103b66e0end = 0x103d8790, entries = 8715
Performance monitoring counters enabled for Crescendo DC- 440
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x0
Initializing Cryptographic API
Soft power switch support not available.
Generic RTC Driver v1.07
Serial: 8250/16550 driver $Revision: 1.90 $ 25 ports, IRQ sharing enabled
ttyS0 at MMIO 0xfffffffff8000000 (irq = 132) is a 16550A
ttyS1 at MMIO 0xfffffffff8000008 (irq = 132) is a 16550A
ttyS2 at MMIO 0xfffffffff8000010 (irq = 132) is a 16550A
ttyS3 at MMIO 0xfffffffff8006000 (irq = 133) is a 16550A
ttyS4 at MMIO 0xfffffffff8006008 (irq = 133) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
mice: PS/2 mouse device common for all mice
HP SDC: No SDC found.
HP SDC MLC: Registering the System Domain Controller's HIL MLC.
HP SDC MLC: Request for raw HIL ISR hook denied
NET: Registered protocol family 2
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
RAMDISK: Compressed image found at block 0
RAMDISK: incomplete write (-28 != 32768) 8388608
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 368k freed
attempt to access beyond end of device
ram0: rw=0, want=26816, limit=16384
attempt to access beyond end of device
ram0: rw=0, want=26816, limit=16384
Warning: unable to open an initial console.

********** VIRTUAL FRONT PANEL **********
System Boot detected
*****************************************
LEDs:  RUN      ATTENTION     FAULT     REMOTE     POWER
      ON       FLASH         OFF       OFF        ON
LED State: There was a system interruption that did not take the system down.
Check Chassis and Console Logs for error messages.

processor                 system initialization      1C00

*****************************************

************ EARLY BOOT VFP *************
End of early boot detected
*****************************************

********** VIRTUAL FRONT PANEL **********
System Boot detected
*****************************************
LEDs:  RUN      ATTENTION     FAULT     REMOTE     POWER
      ON       FLASH         OFF       OFF        ON
LED State: There was a system interruption that did not take the system down.
Check Chassis and Console Logs for error messages.

processor                 system panic               1B00


I've tried to change 'console' and 'TERM' kernel parametrs, temp variable doesn't change anything. When I'm switching 'console' to another port i don't see any output when kernel starts.


PS: Sorry for html formating, but it must be more easy to read.

<mailto:debian-hppa%40lists.debian.org>

--
Alexander Egorushkin <paranoic@stacksoft.ru>



Reply to: