Re: Cannot boot any cd/floppy/kernel on OF prep machine
On Thu, Jun 03, 2004 at 04:34:17PM +0900, Jerome Walter wrote:
> Sven Luther wrote:
> >On Thu, Jun 03, 2004 at 03:09:53PM +0900, Jerome Walter wrote:
> >>I am currently trying to install a Woody on an Bull Estrella 300
> >>machine, running a Prep Motorola 604e Utah processor (/proc/cpuinfo) and
> >>OpenFirmware. Having also an Estrella 200 running fine with it (Estrella
> >>200 is Blackhawk with PPCBug firmware).
> >
> >
> >How much memory have those boxes ?
>
> 128MB for the one i am installing, the same for the other 300 series,
> and 160MB for Estrella 200 one.
Ok, debian-installer has a 24/32Mo memory limit, which is why i am
asking, since i had a bug report about a 16Mo PReP system.
> Not a memory problem though. The box was running AIX fine. (Gosh, it
> seams like a post in debian archive dating back to popato, but the guy
> was having linux booting...
Yep, but probably his own built kernel, not sure.
> >>I tried any cd from woody to debian-installer tc1 passing by netboot and
> >>floppies. They all give the same result: nice black screen (except from
> >>d-i that gives "The attempt to load a boot image failed").
>
> >Please, don't use woody, but debian-installer and sarge. I would be glad
> >to help you out making sure sarge will install and work fine on your
> >hardware. debian-installer needs between 24 and 32 Mo of ram though,
> >which may be a problem on PReP boxes, not sure what is your case.
>
> It is funny, on debien-devel ("Lost Trust"), people are saying that one
> should use Stable for prod systems ;) Ok, i am not here to troll, so i
> will test every single solution, even if i have to downgrade afterwards.
Well, sure it would be better. That said, boot-floppies (the woody and
older installer) is antiquated, and it doesn't make sense to work on it
still given the imminent release of sarge.
What is also possible is to simply use debootstrap, and cross install
the system, but it would be usefull to test debian-installer on said
box for the future.
> >>I have already a similar machine running a woody (2.2.12), from a
> >>previous installation i didn't do, so i think there is a way to get it
> >>working.
> >
> >
> >Ok, ... So, the first order of business is to understand what hardware
> >those boxes have. Please provide a lspci -n, lspci and dmesg output.
> >(possibly to me, or better yet to a debian-installer bug report). Also
> >the content of /proc/cpuinfo would be welcome.
>
> Sorry, i won't snip dmesg ...
Huh ? i think you reached the limit of my english knowledge with this
one.
> # lspci -n
> 00:0b.0 Class 0601: 10ad:0565 (rev 04)
> 00:0b.1 Class 0101: 10ad:0105 (rev 05)
> 00:0c.0 Class 0100: 1000:0003 (rev 11)
> 00:0e.0 Class 0200: 1011:0009 (rev 20)
> 00:11.0 Class 0200: 1011:0009 (rev 22)
> 00:12.0 Class 0300: 1013:00b8
>
> # lspci
> 00:0b.0 ISA bridge: Symphony Labs W83C553 (rev 04)
> 00:0b.1 IDE interface: Symphony Labs SL82c105 (rev 05)
> 00:0c.0 SCSI storage controller: LSI Logic / Symbios Logic (formerly
> NCR) 53c825 (rev 11)
> 00:0e.0 Ethernet controller: Digital Equipment Corporation DECchip 21140
> [FasterNet] (rev 20)
> 00:11.0 Ethernet controller: Digital Equipment Corporation DECchip 21140
> [FasterNet] (rev 22)
> 00:12.0 VGA compatible controller: Cirrus Logic GD 5446
pcnet and sym53c8xx drivers are included, not sure about the ide
controller though. I don't know about an fbdev driver for the cirrus
logic, and am not sure we include the vga console. That said, a serial
console (Well, with a null modem and a second box running minicom for
example) should be enough for debugging the kernel. If you have such a
setup, please boot the d-i kernel with the additional console=ttyS00
console=tty0 option, in order to see where it fails. I suspect it
probably is the missing fbdev/vgacon.
Also, make sure you boot install/powerpc/vmlinuz-prep.initrd on the
netinst iso, or use the netboot image.
> # dmesg is funnier : pages of
> Bogus interrupt from PC = c0008fec...
>
> # cat /var/log/dmesg
> PReP architecture
> Total memory = 128MB; using 512kB for hash table (at c0200000)
> Linux version 2.2.12 (root@beef) (gcc version 2.95.1 19990816 (release))
> #1 Thu
> Nov 11 16:02:41 MST 1999
> Boot arguments: linux root=/dev/sda3
> time_init: decrementer frequency = 3692688360/60 (58MHz)
> Console: colour VGA+ 80x25
> Calibrating delay loop... 1474.56 BogoMIPS
> Memory: 127600k available (1052k kernel code, 2320k data, 100k init)
> [c0000000,c
> 8000000]
> POSIX conformance testing by UNIFIX
> PCI: Probing PCI hardware
> Setting PCI interrupts for a "Utah (Powerstack II Pro4000)"
> Linux NET4.0 for Linux 2.2
> Based upon Swansea University Computer Society NET3.039
> NET4: Unix domain sockets 1.0 for Linux NET4.0.
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP, IGMP
> Starting kswapd v 1.5
> initialize_kbd: Keyboard reset failed, no ACK
> Detected PS/2 Mouse Port.
> Serial driver version 4.27 with MANY_PORTS enabled
> ttyS00 at 0x03f8 (irq = 4) is a 16550A
> ttyS01 at 0x02f8 (irq = 3) is a 16550A
> pty: 256 Unix98 ptys configured
> Real Time Clock Driver v1.09
> Macintosh non-volatile memory driver v1.0
> RAM disk driver initialized: 16 RAM disks of 4096K size
> loop: registered device at major 7
> W82C105: IDE controller on PCI bus 00 dev 59
> W82C105: device enabled (Linux)
> W82C105: will probe irqs later
> W82C105: dma_base is invalid (0x0000)
> ide0: W82C105 Bus-Master DMA disabled (BIOS)
> SL82C105 command word: 1
> IDE control/status register: 00ff0091
> Setting hda from 0x909 to PIO2 timing, 0x3e4
> Setting hdb from 0x909 to PIO2 timing, 0x3e4
> W82C105: dma_base is invalid (0x0000)
> ide1: W82C105 Bus-Master DMA disabled (BIOS)
> Setting hdc from 0x909 to PIO2 timing, 0x3e4
> Setting hdd from 0x909 to PIO2 timing, 0x3e4
> keyboard: Too many NACKs -- noisy kbd cable?
> keyboard: Too many NACKs -- noisy kbd cable?
> Floppy drive(s): fd0 is 2.88M
> FDC 0 is a National Semiconductor PC87306
> ncr53c8xx: at PCI bus 0, device 12, function 0
> ncr53c8xx: attempting to force PCI_COMMAND_MASTER...succeeded.
> ncr53c8xx: attempting to force PCI_COMMAND_IO...succeeded.
> ncr53c8xx: attempting to force PCI_COMMAND_MEMORY...succeeded.
> ncr53c8xx: PCI_LATENCY_TIMER=0, bursting should'nt be allowed.
> ncr53c8xx: PCI_CACHE_LINE_SIZE not set, features based on CACHE LINE
> SIZE not us
> ed.
> ncr53c8xx: 53c825a detected
> ncr53c825a-0: rev=0x11, base=0x3008000, io_port=0x1400, irq=15
> ncr53c825a-0: ID 7, Fast-10, Parity Checking
> ncr53c825a-0: on-chip RAM at 0x3009000
> ncr53c825a-0: restart (scsi reset).
> ncr53c825a-0: Downloading SCSI SCRIPTS.
> scsi0 : ncr53c8xx - version 3.2a-2
> scsi : 1 host.
> Vendor: SEAGATE Model: ST34371W Rev: 0558
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sda at scsi0, channel 0, id 1, lun 0
> Vendor: MATSHITA Model: CD-ROM CR-506 Rev: 8S04
> Type: CD-ROM ANSI SCSI revision: 02
> Detected scsi CD-ROM sr0 at scsi0, channel 0, id 5, lun 0
> ncr53c825a-0-<1,0>: tagged command queue depth set to 4
> scsi : detected 1 SCSI cdrom 1 SCSI disk total.
> ncr53c825a-0-<5,*>: FAST-5 SCSI 5.0 MB/s (200 ns, offset 8)
> Uniform CDROM driver Revision: 2.55
> ncr53c825a-0-<1,*>: FAST-5 WIDE SCSI 10.0 MB/s (200 ns, offset 8)
> SCSI device sda: hdwr sector= 512 bytes. Sectors= 8496960 [4148 MB] [4.1 GB]
> pcnet32.c: PCI bios is present, checking for devices...
> eth0: DC21140 at 0x1800 (PCI bus 0, device 14), h/w address
> 08:00:3e:25:c5:70,
> and requires IRQ11 (provided by PCI BIOS).
> de4x5.c:V0.544 1999/5/8 davies@maniac.ultranet.com
> eth1: DC21140 at 0x1000 (PCI bus 0, device 17), h/w address
> 00:c0:95:fa:df:25,
> and requires IRQ11 (provided by PCI BIOS).
> de4x5.c:V0.544 1999/5/8 davies@maniac.ultranet.com
> Partition check:
> sda: sda1 sda2 sda3
> VFS: Mounted root (ext2 filesystem) readonly.
> Freeing unused kernel memory: 100k init 8k pmac 12k open firmware
> Adding Swap: 249232k swap-space (priority -1)
> eth0: media is 100Mb/s full duplex.
>
> >Then, to test debian-installer, you need to boot the prep kernel, which
> >you find in install/powerpc/vmlinuz-prep.initrd. This may work out of
> >the box, but if not, we need to know the kernel config used in the
> >working kernel, and/or see for ourselves what is going wrong.
>
> Still "The attempt to load boot file failed" and jumps to hard drive boot.
Huh, this should not happen. can you install the
kernel-image-2.4.25-powerpc-prep package on the working system (in
sarge/sid though) and try booting /boot/vmlinuz-2.5.25-powerpc ?
> > Do you per
> >chance have a serial console setup or something such, for getting early
> >kernel log info ?
>
> It would have been too easy with a serial console ;) I do have an async
> vt100 or similar console, but no way to plug it. Irritating, isn't it ?
A null modem and a second box would serve as well. OR maybe a serial
printer :)
> >>BTW, this could be also considered as a boot failure for
> >>debian-installer-tc1 image ;)
> >
> >
> >What is tcl ?
>
> TC-one. Test Candidate 1. The one that was advised to be more visible on
> debian-installer pages yesterday or the day before ;)
> http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/powerpc/tc1/sarge-powerpc-netinst.iso
Arg, again hit by the late translation of the french sides, how well.
Friendly,
Sven Luther
Reply to: