From: ebrower@usa.net
To: ultralinux@vger.kernel.org
Subject: Re: [Q] ultrapenguin-1.1 on UE4000
Date: Thu, 19 Nov 1998 20:27:36 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-91155331807414@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-91139210917441@msgid-missing>
> Ok thanks, now grab the tftpboot image from:
>
> ftp.cobaltnet.com:/pub/users/davem/for_ebrower/e4000test.img
>
> and tftpboot that and send me the console output, it may be lengthy.
>
> If it works and detects your disks, it will be a step in the right
> direction, but this image is not an install image, just a kernel by
> itself so it will die when it tries to mount root even if the device
> probing works :-)
>
> Let me know how it goes.
Here's the output from the kernel:
E
---
{0} ok boot net
Boot device: /sbus@3,0/SUNW,hme@3,8c00000 File and args:
root child is f002cf50
Found CPU 0 (nodeð06f708,mid=0)
Found CPU 1 (nodeð06fac8,mid=1)
Found CPU 2 (nodeð14f6e4,mid=4)
Found CPU 3 (nodeð14faa4,mid=5)
Found CPU 4 (nodeð22f6e4,mid=8)
Found CPU 5 (nodeð22faa4,mid=9)
Found CPU 6 (nodeð30f6e4,mid\x12)
Found CPU 7 (nodeð30faa4,mid\x13)
PROMLIB: Sun IEEE Boot Prom 3.2.16 1998/06/08 16:58
Linux version 2.1.129 (davem@pizda.cobaltnet.com) (gcc driver version 2.7.2
snapshot 970621 executing gcc version 2.7.2) #4 SMP Thu Nov 19 12:41:20 PST 1998
ARCH: SUN4U
Ethernet address: 08:00:20:9a:71:d5
Found CPU 0 (nodeð06f708,mid=0)
Found CPU 1 (nodeð06fac8,mid=1)
Found CPU 2 (nodeð14f6e4,mid=4)
Found CPU 3 (nodeð14faa4,mid=5)
Found CPU 4 (nodeð22f6e4,mid=8)
Found CPU 5 (nodeð22faa4,mid=9)
Found CPU 6 (nodeð30f6e4,mid\x12)
Found CPU 7 (nodeð30faa4,mid\x13)
Found 8 CPU prom device tree node(s).
CENTRAL: found central PROM node f005df90.
FHC Version[1] PartID[fa0] Manufacturer[3e]
Calibrating delay loop... 494.80 BogoMIPS
Memory: 1022408k available (1616k kernel code, 12000k data, 160k init)
[fffff80000000000,fffff8003fcd8000]
POSIX conformance testing by UNIFIX
Entering UltraSMPenguin Mode...
Calibrating delay loop... 494.80 BogoMIPS
Calibrating delay loop... 494.80 BogoMIPS
Calibrating delay loop... 494.80 BogoMIPS
Calibrating delay loop... 494.80 BogoMIPS
Calibrating delay loop... 494.80 BogoMIPS
Calibrating delay loop... 494.80 BogoMIPS
Calibrating delay loop... 494.80 BogoMIPS
Total of 8 processors activated (3958.37 BogoMIPS).
PCI: Probing for controllers.
PCI: No PCI bus detected
IOMMU(SBUS): IMPL[0] VERS[0] SYSIO mapped at fffff9c600000000
IOMMU: Streaming Buffer IMPL[0] REV[0] FlushFLAG[0000000000d78400] ... ENABLED
sbus0: Clock 25.0 MHz
dma0: HME DVMA gate array
IOMMU(SBUS): IMPL[0] VERS[0] SYSIO mapped at fffff9cc00000000
IOMMU: Streaming Buffer IMPL[0] REV[0] FlushFLAG[0000000000d78520] ... ENABLED
sbus1: Clock 25.0 MHz
IOMMU(SBUS): IMPL[0] VERS[0] SYSIO mapped at fffff9ce00000000
IOMMU: Streaming Buffer IMPL[0] REV[0] FlushFLAG[0000000000d785e0] ... ENABLED
sbus2: Clock 25.0 MHz
dma1: HME DVMA gate array
IOMMU(SBUS): IMPL[0] VERS[0] SYSIO mapped at fffff9d400000000
IOMMU: Streaming Buffer IMPL[0] REV[0] FlushFLAG[0000000000d78700] ... ENABLED
sbus3: Clock 25.0 MHz
IOMMU(SBUS): IMPL[0] VERS[0] SYSIO mapped at fffff9d600000000
IOMMU: Streaming Buffer IMPL[0] REV[0] FlushFLAG[0000000000d787c0] ... ENABLED
sbus4: Clock 25.0 MHz
dma2: HME DVMA gate array
Swansea University Computer Society NET3.039 for Linux 2.1
NET3: Unix domain sockets 0.16 for Linux NET3.038.
Swansea University Computer Society TCP/IP for NET3.037
IP Protocols: ICMP, UDP, TCP
Starting kswapd v 1.5
Sparc Zilog8530 serial driver version 1.32
tty00 at 0xfff66004 (irq = 12,339) is a Zilog8530
tty01 at 0xfff66000 (irq = 12,339) is a Zilog8530
tty02 at 0xffd9e004 (irq = 12,339) is a Zilog8530
tty03 at 0xffd9e000 (irq = 12,339) is a Zilog8530
keyboard: not present
Console: ttyS0 (Zilog8530)
Sun Mouse-Systems mouse driver version 1.00
RAM disk driver initialized: 16 RAM disks of 4096K size
md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
esp0: IRQ 7,db SCSI ID 7 Clock 40 MHz CCF=8 Time-Out 167 NCR53C9XF(espfast)
detected
esp0: FAST chip is fasHME (family\x10, version=5)
esp1: IRQ 7,1db SCSI ID 7 Clock 40 MHz CCF=8 Time-Out 167 NCR53C9XF(espfast)
detected
esp1: FAST chip is fasHME (family\x10, version=5)
esp2: IRQ 7,2db SCSI ID 7 Clock 40 MHz CCF=8 Time-Out 167 NCR53C9XF(espfast)
detected
esp2: FAST chip is fasHME (family\x10, version=5)
ESP: Total of 3 ESP hosts found, 3 actually in use.
scsi0 : Sparc ESP366-HME
scsi1 : Sparc ESP366-HME
scsi2 : Sparc ESP366-HME
scsi : 3 hosts.
scsi : detected total.
sunhme.c:v1.2 10/Oct/96 David S. Miller (davem@caipfs.rutgers.edu)
eth0: HAPPY MEAL (SBUS) 10/100baseT Ethernet 08:00:20:9a:71:d5
eth1: HAPPY MEAL (SBUS) 10/100baseT Ethernet 08:00:20:9a:71:d5
eth2: HAPPY MEAL (SBUS) 10/100baseT Ethernet 08:00:20:9a:71:d5
Partition check:
VFS: Cannot open root device 00:00
Kernel panic: VFS: Unable to mount root fs on 00:00
Press L1-A to return to the boot prom
next prev parent reply other threads:[~1998-11-19 20:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-17 21:16 [Q] ultrapenguin-1.1 on UE4000 ebrower
1998-11-18 12:36 ` David S. Miller
1998-11-18 13:31 ` Jakub Jelinek
1998-11-18 13:39 ` Jakub Jelinek
1998-11-18 19:14 ` ebrower
1998-11-19 16:05 ` Matthew Jacob
1998-11-19 17:15 ` David S. Miller
1998-11-19 18:15 ` ebrower
1998-11-19 19:44 ` David S. Miller
1998-11-19 20:27 ` ebrower [this message]
1998-11-19 20:32 ` David S. Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-ultrasparc-91155331807414@msgid-missing \
--to=ebrower@usa.net \
--cc=ultralinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.