Netra X1 boot getting closer
Well, I can *almost* boot my X1 now with the sun4u tftpboot.img on
http://auric.debian.org/~bcollins. (6/21/01) -- Here's my dmesg:
Boot device: /pci@1f,0/ethernet@c File and args: -p
Using Onboard Transceiver - Link Up.
Timeout waiting for ARP/RARP packet
28e200 240600
Server IP address: 165.254.98.30
Client IP address: 165.254.98.31
TILO
Selecting sun4u kernel...
/
PROMLIB: Sun IEEE Boot Prom 4.0.6 2001/02/19 09:56
Linux version 2.4.4 (root@vore) (gcc version 3.0 20010426 (Debian prerelease)) #
1 Thu May 17 11:59:44 EDT 2001
ARCH: SUN4U
Ethernet address: 00:03:ba:04:d6:84
Remapping the kernel... done.
On node 0 totalpages: 15586
zone(0): 16228 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Booting Linux...
Found CPU 0 (node=f0071fb0,mid=0)
Found 1 CPU prom device tree node(s).
Kernel command line: -p
Calibrating delay loop... 799.53 BogoMIPS
Memory: 122632k available (1816k kernel code, 472k data, 200k init) [fffff800000
00000,0000000067ec8000]
Dentry-cache hash table entries: 16384 (order: 5, 262144 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 8192 bytes)
Page-cache hash table entries: 16384 (order: 4, 131072 bytes)
Inode-cache hash table entries: 8192 (order: 4, 131072 bytes)
POSIX conformance testing by UNIFIX
PCI: Probing for controllers.
PCI: Found SABRE, main regs at 000001fe00000000, wsync at 000001fe00001c20
SABRE: Shared PCI config space at 000001fe01000000
SABRE: DVMA at 60000000 [20000000]
PCI: Address space collision on region 0 of device PCI device 1282:9102
PCI: Address space collision on region 0 of device PCI device 1282:9102
PCI: Address space collision on region 0 of device PCI device 10b9:5229
PCI: Address space collision on region 1 of device PCI device 10b9:5229
PCI: Address space collision on region 2 of device PCI device 10b9:5229
PCI: Address space collision on region 3 of device PCI device 10b9:5229
PCI: Address space collision on region 4 of device PCI device 10b9:5229
PCI0(PBMA): Bus running at 33MHz
isa0: [dma] [rtc] [power] [SUNW,lomh] [serial] [serial] [flashprom]
ebus: No EBus's found.
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Starting kswapd v1.8
pty: 256 Unix98 ptys configured
Linux video capture interface: v1.00
block: queued sectors max/low 80901kB/26967kB, 256 slots per queue
RAMDISK driver initialized: 16 RAM disks of 4096K 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
ALI15X3: IDE controller on PCI bus 00 dev 68
ALI15X3: chipset revision 195
ALI15X3: 100% native mode on irq 1,7cc
ide0: BM-DMA at 0x1fe02000620-0x1fe02000627, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0x1fe02000628-0x1fe0200062f, BIOS settings: hdc:pio, hdd:pio
hda: ST320413A, ATA DISK drive
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ide0 at 0x1fe02000600-0x1fe02000607,0x1fe0200060a on irq 1,7cc
hda: 39102336 sectors (20020 MB) w/512KiB Cache, CHS=38792/16/63, UDMA(66)
Partition check:
hda: hda1 hda2 hda3 hda5 hda6 hda7
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 1431k freed
loop: loaded (max 8 devices)
rtc_init: no PC rtc found
SCSI subsystem driver Revision: 1.00
request_module[scsi_hostadapter]: Root fs not mounted
request_module[scsi_hostadapter]: Root fs not mounted
request_module[scsi_hostadapter]: Root fs not mounted
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-ohci.c: USB OHCI at membase 0x1ff01000000, IRQ 14,7e4
usb-ohci.c: usb-00:0a.0, PCI device 10b9:5237
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb.c: registered new driver hid
mice: PS/2 mouse device common for all mice
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP: Hash tables configured (established 16384 bind 16384)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (ext2 filesystem).
Warning: unable to open an initial console.
Has anyone gotten this to successfully boot into the installer on an X1?
Also, it doesn't look as if the Ethernet device was detected. From posts I
read last week, this should be ok in 2.4.6?
Thanks,
--Adam
--
Adam McKenna <adam@debian.org> <adam@flounder.net>
Reply to: