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

Bug#302402: Debian Installer RC 3 on PARISC - Netboot



Package: installation-reports

Debian-installer-version: RC3
uname -a: Linux palinux 2.6.8-2-32-smp #1 SMP Mon Feb 7 22:19:10 EST 2005 
parisc GNU/Linux
Date: Thu Mar 31 18:29:15 CEST 2005
Method: Booted boot.img from bootp-server

Machine: Hewlett Packard 9000-712/60
Processor: PA-Risc 1.1d - PA7100 LC (PCX-L)
Memory: 64 MB
Root Device: SCSI, /dev/sda
Root Size/partition table:

Disk /dev/sda: 1050 MB, 1050347520 bytes
255 heads, 63 sectors/track, 127 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1           4       32098+  f0  Linux/PA-RISC boot
/dev/sda2               5          14       80325   83  Linux
/dev/sda3              15         127      907672+   5  Extended
/dev/sda5   *          15         118      835348+  83  Linux
/dev/sda6             119         127       72261   82  Linux swap

sda2 = /boot
sda5 = /

Output of lspci: N/A

Base System Installation Checklist:

Initial boot worked:    [E] OK after changing ramdisk_size
Configure network HW:   [O]
Config network:         [O]
Detect CD:              [O]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [0]
Create file systems:    [O]
Mount partitions:       [O]
Install base system:    [O]
Install boot loader:    [O]
Reboot:                 [O]

[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems:

When booting without changing any boot-parameters, the system would hang with 
as last message 'Kernel panic: no init found'. Previous messages already had 
scrolled off the screen (because the scrolling takes place on the first 
line).
However, I already had some experience with booting from CD (see bug report 
301504), so I changed the parameter ramdisk_size to different values. I tried 
this numbers:
4096 --> same problem
8192 --> same problem
16384 --> OK, installer started fine
32768 --> OK, installer started fine

I only tried these values, if you want me to search further (some values in 
between), please let me know.

After that initial problem was solved, the installation went fine.

Just one remark: after every 'apt-get update' I get the following message:
connecting to <mirror I chose> module ipv6 relocation of symbol capable is out 
of range (0x3ffeffdc in 17 bits).




Reply to: