Re: 43p-140 install issues
Hi, >Would there be any image I can use to install this machine currently? Sure, check http://www.solinno.co.uk/7043-140/, that's Leigh Browns site. There's a detailed step-by-step guide which will take you through the whole process. You can even choose what distro you want to install, but you may have to update your firmware first (I had to do it as well, but it was OK). BTW: great job Leigh! >Here's my situation, If I can get the machine to boot and install by >next week (back to work) my boss will let me keep working on it - >otherwise he'll declare it useless and it'll go back in the closet. If >I can get anything on it I'm ok - It doesn't need to be 2.6. [del] There are 2.4.x kernels on that site which are working very well, I installed Debian Woody on top of it ;-) HTH, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Suicide Drive (The Deep Eynde) 24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)
Re: 43p-140 install issues
Hi, [del] >I would prefer that we fix the debian kernels for them to work correctly >though. More on this on monday. I failed to configure a stock 2.4.28 kernel to detect the SCSI controler. I think some of Leigh patches for this must be applied, but I haven't gone any further. [del] >Do the debian 2.4.27 kernel work on it ? I was unable to boot the 2.4.27 d-i >kernel on my powerstack, but this is a different machine, so the issues may be >a bit different. I've only tried the Woody PREP kernel, which failed in a way which I can't remember, but I'll give it a try. HTH, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Suicide Drive (The Deep Eynde) 24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)
Re: 43p-140 install issues
Hi, [del] >Yes, please, i would greatly appreciate it, preferably the 2.6.8 kernel too. >Let' try to get this fixed before the sarge release, which is not so far off >now. OK, 9 hours later I had a current sarge buisnesscard CD image, with interesting results. I booted the standard kernel from the cdrom with `boot cdrom:`, it came up and failed to load the initrd, so it died on the spot as nothing could be mounted. It was detecting that I was using a serial console. Of course, I forgot to capture that session, so I did it again with logging on in kermit. Then I could not boot anything from the CD, but I can still boot fine from disk, so it's not a hardware problem. The LED displays F05 after reading something from the CDROM in this case and the machine hangs. Strange. I will try to boot via tftp, the firmware seems to be unable to boot a specific file from CDROM, CU, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Suicide Drive (The Deep Eynde) 24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)
Re: 43p-140 install issues
ts complicated, if you ask me. I really don't know why your floppy stops working after booting Leighs kernel. But on the other hand, I don't know why I can't netboot my box either - I can netboot anything else from DECstations to SGIs with the same setup, but my 7043-44 refuses to load the kernel. It contacts the server, figures out the name of the file, but does not request it. For your network trouble, try to disconnect power from the box completely for an hour or so. This was enough for my box to fall back to asking me for the active console, maybe this works for your flaky network as well? HTH, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Suicide Drive (The Deep Eynde) 24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)
Re: 43p-140 install issues
Hi, [del] >> Linux/PPC load: console=ttyS0,9600 console=tty0 > >*** This is the point you get 5 seconds to start editing the parameters. >I guess if you specify root=/dev/ram0 or something then it will boot >from the ramdisk, rather than trying to boot from /dev/sda3. Right, now I can even boot over network: 0 > setenv load-base 100 ok 0 > setenv real-base c0 ok 0 > boot net: LOAD: Waiting 60 seconds for Spanning Tree BOOTP R = 1 BOOTP S = 1 FILE: /tftpboot/wehrle/vmlinuz-prep.initrd Load Addr=0x100 Max Size=0xf00 Packet Count = 100 [snipped the packet count lines] loaded at: 01000400 01554FF4 relocated to: 0080 00D54BF4 zimage at: 0080A94C 0093DC0A initrd at: 0093E000 00D4AB7A avail ram: 0040 0080 Linux/PPC load: console=ttyS0,9600 console=tty0 root=/dev/ram Uncompressing Linux...done. Now booting the kernel Total memory = 256MB; using 512kB for hash table (at c030) Linux version 2.6.8-powerpc ([EMAIL PROTECTED]) (gcc version 3.3.4 (Debian 1:3.3.4-11)) #1 Sun Oct 3 13:22:21 CEST 2004 PReP architecture IBM planar ID: 00d5 MPIC at 0xfddc (0x3ddc), length 0x0004 mapped to 0xeffc Built 1 zonelists Kernel command line: console=ttyS0,9600 console=tty0 root=/dev/ram OpenPIC Version 1.0 (4 CPUs and 16 IRQ sources) at effc PID hash table entries: 2048 (order 11: 16384 bytes) time_init: decrementer frequency = 16.618701 MHz Console: colour dummy device 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 251648k available (1732k kernel code, 1060k data, 164k init, 0k highmem) Calibrating delay loop... 397.31 BogoMIPS Mount-cache hash table entries: 512 (order: 0, 4096 bytes) checking if image is initramfs...it isn't (no cpio magic); looks like an initrd Freeing initrd memory: 4146k freed NET: Registered protocol family 16 PCI: Probing PCI hardware Setting PCI interrupts for a "IBM 43P-140 (Tiger1)" PCI: Cannot allocate resource region 0 of device :00:0b.0 PCI: Cannot allocate resource region 0 of device :00:0c.0 PCI: Cannot allocate resource region 0 of device :00:10.0 PCI: Cannot allocate resource region 0 of device :00:12.0 Thermal assist unit not available audit: initializing netlink socket (disabled) audit(943920304.671:0): initialized devfs: 2004-01-31 Richard Gooch ([EMAIL PROTECTED]) devfs: boot_options: 0x0 Initializing Cryptographic API Generic RTC Driver v1.07 Macintosh non-volatile memory driver v1.1 Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A pmac_zilog: 0.6 (Benjamin Herrenschmidt <[EMAIL PROTECTED]>) RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize input: Macintosh mouse button emulation Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx mice: PS/2 mouse device common for all mice NET: Registered protocol family 2 IP: routing cache hash table of 2048 buckets, 16Kbytes TCP: Hash tables configured (established 16384 bind 32768) RAMDISK: Compressed image found at block 0 VFS: Mounted root (cramfs filesystem) readonly. Freeing unused kernel memory: 164k init 60k pmac 4k chrp 8k openfirmware NET: Registered protocol family 1 And that's it. Seems like the d-i doesn't know that it should use the serial console. BTW, the instructions for booting PREP systems in the debian installation manual aren't quite right, they are missing the "net:" string. If the TFTP-server is setup right, the firmware can figure out the rest, so giving the server IP, the name and the IP should not be necessary and I would try `boot net:` first. [del] >It should never ask the console question again unless you change the >config (plug in a mouse for example), unless your nvram battery is a >bit flat of course! This seems to be the case. But it really simplifies things, as I've never been able to warm-boot anything ;-) Only a cold boot helps. Maybe Daniel should remove the battery to reset things completely? Anyway, without your site, Leigh, I would still have a big doorstop only, thanks again, CU, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Suicide Drive (The Deep Eynde) 24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)
Re: 43p-140 install issues
Hi, >Delete the "console=tty0", so you end up with: > > Linux/PPC load: console=ttyS0,9600 root=/dev/ram > >and try again! [del] Right, then the installer knows what to do. I think this should go into the Debian installation docs, there are a lot of boxes with graphic cards out which are not supported by Linux. But the low level SCSI-driver is missing in this image, or any low level SCSI drivers for that matter. There are only the high level modules there, like sd_mod.ko and sr_mod.ko: Nov 30 00:06:32 hw-detect: Using discover version 1. Nov 30 00:06:35 hw-detect: Detecting hardware... Nov 30 00:06:36 hw-detect: Missing module 'sym53c8xx'. Nov 30 00:06:36 hw-detect: Missing module 'usb-storage'. Nov 30 00:06:36 hw-detect: Missing module 'ide-mod'. Nov 30 00:06:36 hw-detect: Missing module 'ide-probe-mod'. Nov 30 00:06:36 hw-detect: Missing module 'ide-detect'. Nov 30 00:06:36 hw-detect: Missing module 'ide-generic'. Nov 30 00:06:37 hw-detect: Missing module 'ide-floppy'. --More-- (57% of 44385 bytes) Nov 30 00:06:37 hw-detect: Missing module 'ide-disk'. Nov 30 00:06:37 hw-detect: Missing module 'isofs'. Nov 30 00:06:37 hw-detect: Loading modules... Nov 30 00:06:37 hw-detect: Detected module 'pcnet32' for 'Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE]' Nov 30 00:06:37 hw-detect: Trying to load module 'pcnet32' Nov 30 00:06:37 kernel: pcnet32.c:v1.30i 06.28.2004 [EMAIL PROTECTED] Nov 30 00:06:37 kernel: PCI: Enabling device :00:0c.0 ( -> 0003) Nov 30 00:06:37 kernel: pcnet32: PCnet/PCI II 79C970A at 0x1020, 00 06 29 2e 98 9d assigned IRQ 22. Nov 30 00:06:37 kernel: divert: allocating divert_blk for eth0 Nov 30 00:06:37 kernel: eth0: registered as PCnet/PCI II 79C970A Nov 30 00:06:37 kernel: pcnet32: 1 cards_found. Nov 30 00:06:38 hw-detect: Detected module 'floppy' for 'Linux Floppy' Nov 30 00:06:38 hw-detect: Trying to load module 'floppy' Nov 30 00:06:38 kernel: inserting floppy driver for 2.6.8-powerpc Nov 30 00:06:38 kernel: Using anticipatory io scheduler Nov 30 00:06:38 kernel: Floppy drive(s): fd0 is 2.88M Nov 30 00:06:38 kernel: FDC 0 is a National Semiconductor PC87306 Nov 30 00:06:38 hw-detect: Detected module 'ide-cd' for 'Linux ATAPI CD-ROM' Nov 30 00:06:38 hw-detect: Trying to load module 'ide-cd' Nov 30 00:06:39 kernel: Linux Kernel Card Services Nov 30 00:06:39 kernel: options: [pci] [cardbus] [pm] Nov 30 00:06:39 hw-detect: Starting PCMCIA services: using yenta_socket instead of i82365 Nov 30 00:06:39 hw-detect: cardmgr[1070]: no sockets found! Nov 30 00:06:39 cardmgr[1070]: no sockets found! Nov 30 00:06:39 hw-detect: done. Nov 30 00:06:39 hw-detect: Detected discover version 1, installing discover1. Nov 30 00:06:39 hw-detect: Detected hotplug support, installing hotplug. Nov 30 00:06:40 hw-detect: Missing modules 'sym53c8xx (Symbios Logic Inc. / NCR 53c825), usb-storage (USB storage), ide-mod (Linux IDE driver), ide-probe-mod (Linux IDE probe driver), ide-detect (Linux IDE detection), ide-generic (Linux IDE support), ide-floppy (Linux IDE floppy), ide-disk (Linux ATA DISK), isofs (Linux ISO 9660 filesystem) /lib/modules/2.6.8-powerpc/kernel/drivers/scsi # ls scsi_mod.ko sd_mod.kosr_mod.ko So, either this is the wrong image (I've taken the same as Daniel mentioned in one of his mails: http://debian.yorku.ca/debian/dists/testing/main/installer-powerpc/current/images/powerpc/netboot/vmlinuz-prep.initrd), or it's missing some vital modules. HTH, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Suicide Drive (The Deep Eynde) 24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)
Re: 43p-140 install issues
Hi, [del] >Ok... trying again with Leigh Brown's boot image and a woody root >floppy and a woody CD. > >The console capture is below. Leigh's kernel boots up great, asks for >a root floppy and then ... > >VFS: Insert root floppy and press ENTER > >FAT: bogus logical sector size 1981 >FAT: bogus logical sector size 1981 Strange. [del] >Reiserfs? Huh? I tried it twice, two different floppies. Both written >as follows (as suggested in Debian manual): >sudo dd if=root.bin of=/dev/fd0 bs=1024 conv=sync ; sync >\1440+0 records in >1440+0 records out >1474560 bytes transferred in 120.042950 seconds (12284 bytes/sec) How did you format the floppys before? >I can however boot the installation I made earlier using Leigh's >image. I have completed the installation and it runs ... for a short >period of time. After about 5 minutes or so it stops responding to the >console and to pings. Ugh. I would recommend to dd Leighs kernel to your disk then. This has been running reliable for me. The bootup log looks good to me, minus the floppy issue, it's very much like mine. HTH, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Suicide Drive (The Deep Eynde) 24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)
Re: 43p-140 install issues
Hi, [del] > BTW, what about your firmware? Is it the most recent one ? Yes, it is. I have asked this before ;-) CU, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Suicide Drive (The Deep Eynde) 24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)
Re: 43p-140 install issues
Hi, >I gave Leigh's 2.4.22 a try. It gave me the same result with the >debian root disk: > >VFS: Insert root floppy and press ENTER > >FAT: bogus logical sector size 1981 >FAT: bogus logical sector size 1981 >read_super_block: can't find a reiserfs filesystem on (dev 02:00, >block 64, size 1024) >read_super_block: can't find a reiserfs filesystem on (dev 02:00, >block 8, size 1024) >Kernel panic: VFS: Unable to mount root fs on 02:00 Could you try to format them before dd'ing on them, like fdformat /dev/fd0h1440? I am not sure if that will change anything, though. >Tonight I'll grab a different root floppy and see what happens. > >Leigh's 2.4.22 will also boot the system installed on /dev/sdb1, >however it also stopped responding after awhile. I think it lasted >longer than with 2.4.19. I am begining to believe that there is some sort of hardware problem with your box or it is an upgraded version which was a -140 in it's previous life, but my -140 is rock solid with Leigh's 2.4.19 kernel - once it's up, that is. I will leave it running tonight to see what happens, HTH, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Suicide Drive (The Deep Eynde) 24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)
Re: 43p-140 install issues
Hi, [del] >Done - no difference. Same message. Written multiple images, multiple >times on multiple machine. Each one with the same result. At least I'm >not completely alone, I found this: >http://wikihip.cern.ch/twiki/bin/view/RS6000/KernelTestsOn43P240 exact >same error. Perhaps there are two different board revisions of -140's out? I'll check what's written on the system board when I'm home again today. >> > I am begining to believe that there is some sort of hardware problem with >> > your >> > box or it is an upgraded version which was a -140 in it's previous life, >> > but my >> > -140 is rock solid with Leigh's 2.4.19 kernel - once it's up, that is. >> > I will leave it running tonight to see what happens, [del] Still running fine: wehrle:~> uname -a Linux wehrle 2.4.19 #3 Sun Aug 4 08:28:30 BST 2002 ppc unknown wehrle:~> uptime 08:58:25 up 13:08, 1 user, load average: 0.00, 0.00, 0.00 I did a kernel compile with a parallel scp transfer as well to put the box under a bit of load before, no issues. HTH, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Suicide Drive (The Deep Eynde) 24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)
Re: 43p-140 install issues
Hi, the only reference number on my board is the IBM FRU number: FRU 93H7143 I would expect that you will have the same marking on your mainboard. My box ran all day with various loads from high to low or no load at all: wehrle:~> uptime 22:29:24 up 1 day, 2:39, 2 users, load average: 0.15, 0.32, 0.61 with Leigh's 2.4.19 kernel. As I searched for the number, I noticed that the CPU fan was *covered* with dirt. Perhaps you should have a look at yours too, because the front fan will pick up all dust and throw it right on the CPU fan. I still wonder why mine was still spinning HTH, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Suicide Drive (The Deep Eynde) 24539 Neumuenster, Germany|Public Pervert (Interpol) Clé De Contact (Metal Urbain)
