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

RE: Problem installing on HP RP5400



Hi Joel and James,

Hi joel
>> I have downloaded the debian 3 rc2, done the checks etc and get the following
>
>Umm debian-3rc1 was well tested otc 3rc2 less and i read many reports of
>install failure :(
>
>The good thing is that your cd driver is ok and cd was burn correctly :)

If the boot process reached this point it could be not a matter of CD rom,
maybe a problem of kernel, isn't it? 8-))
>
>> output on the console:

>>       0      650  MHz   Active                 Functional         750
KB
>> 1.5 MB

I hadn't work for HP so long to see the 650 MHz CPUs available, you are
a lucky HP systems user!!!;-P
>> Linux version 2.4.17-64 (root@paer) (gcc version 3.0) #1 Sat Mar 16 17:31:44
>
>Well kernel 2.4.17 is a bit outdated now and the only test I did was with
>a 2.4.22-pa10, though

as Joel said afterward with the new d-i the kernel version now is 2.4.26-64-smp
>> 14. Unknown machine (0) at 0xfffffffffed21000 [33], versions 0x5e0, 0x0,
>> 0x0
I can't figure out the meaning of this phrase!

>> CPU(s): 1 x PA8600 (PCX-W+) at 650.000000 MHz
[...]
>> POSIX conformance testing by UNIFIX
>> Linux NET4.0 for Linux 2.4
>> Based upon Swansea University Computer Society NET3.039
>> Initializing RT netlink socket
>> Performance monitoring counters enabled for Unknown machine
>> Starting kswapd
>> Journalled Block Device driver loaded
>> pty: 256 Unix98 ptys configured
>> Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI
>> en
>> abled
>> Redundant entry in serial pci_table.  Please send the output of
>> lspci -vv, this message (103c,1048,103c,104b)
>> and the manufacturer and name of serial board or modem board
>> to serial-pci-info@lists.sourceforge.net.
>> ttyS00 at iomem 0xffffffff80000000 (irq = 132) is a 16550A
>> ttyS01 at iomem 0xffffffff80000008 (irq = 132) is a 16550A
>> ttyS02 at iomem 0xffffffff80000010 (irq = 132) is a 16550A
>> ttyS03 at iomem 0xffffffff80000030 (irq = 132) is a 16550A
>> ttyS04 at iomem 0xffffffff80000038 (irq = 132) is a 16550A
>> request_module[parport_lowlevel]: Root fs not mounted
>> lp: driver loaded but no devices found
>> Generic RTC Driver v1.02 05/27/1999 Sam Creasey (sammy@oh.verio.com)
>> block: 128 slots per queue, batch=32
>> RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
>> Uniform Multi-Platform E-IDE driver Revision: 6.31
>> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
>> loop: loaded (max 8 devices)
>> Linux Tulip driver version 0.9.15-pre9 (Nov 6, 2001)
>> tulip0: no phy info, aborting mtable build
>> tulip0:  MII transceiver #1 config 1000 status 7809 advertising 0061.
>> eth0: Digital DS21143 Tulip rev 65 at 0x80, 00:30:6E:13:C6:42, IRQ 128.
>> SCSI subsystem driver Revision: 1.00
>> sym53c8xx: at PCI bus 0, device 2, function 0
>> sym53c8xx: 53c875 detected
>> sym53c8xx: at PCI bus 0, device 2, function 1
>> sym53c8xx: 53c875 detected
>> sym53c8xx: at PCI bus 80, device 0, function 0
>> sym53c8xx: 53c895 detected
>> sym53c8xx: at PCI bus 96, device 0, function 0
>> sym53c8xx: 53c895 detected
>> sym53c8xx: at PCI bus 0, device 1, function 0
>> sym53c8xx: setting PCI_COMMAND_INVALIDATE (fix-up)
>> sym53c8xx: 53c896 detected
>> sym53c8xx: at PCI bus 0, device 1, function 1
>> sym53c8xx: setting PCI_COMMAND_INVALIDATE (fix-up)
>> sym53c8xx: 53c896 detected
>> sym53c875-0: rev 0x37 on pci bus 0 device 2 function 0 irq 130
>> sym53c875-0: ID 7, Fast-20, Parity Checking

I don't remember the meaning of the led ligthing combination: what I suggest
is to extract all the h/w that you don't really need: leave 1 processor
, the memory, 1 disk; the rest (network cards, fiber channel cards, scsi
cards, extra functionality boards) leave it out.
Fire up the system and see if the msg is repated; you can also try with
the new d-i to boot up the system to see whether it hangs again(with an
earlier kernel version).

>>
>> ************* SYSTEM ALERT **************
>> SYSTEM NAME: fileserver-c
>> DATE: 05/18/2004 TIME: 15:35:24
>> ALERT LEVEL: 7 = reserved
>>
>> REASON FOR ALERT
>> SOURCE: 0 = unknown, no source stated
>> SOURCE DETAIL: 0 = unknown, no source stated   SOURCE ID: FF
>> PROBLEM DETAIL: 0 = no problem detail
>>
>> LEDs:  RUN      ATTENTION     FAULT     REMOTE     POWER
>>        FLASH    FLASH         FLASH     ON         ON
>> LED State: Unexpected Reboot. Running non-OS code. Non-critical error
detected.
>> Check Chassis and Console Logs for error messages.
>>
>
>too bad the system panic :P
>
>> 0x0000007000FF6292 000000FF FF800000 - type  0 = Data Field Unused
>> 0x5800087000FF6292 00006804 120F2318 - type 11 = Timestamp 05/18/2004
15:35:24

>
>I trust you would have better chance with the other mentioned: sarge-netinstall
>cd (it contains the last 2.4.26 :) )
>see <http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/hppa/current/sarge-hppa-netinst.iso>

I agree with Joel

Regards

SteX



Reply to: