Bernard, Charles, and Ezra,
Thanks for your suggestions. I've included below the output of the screen during the boot. It picks up after it has started its network boot (it's already gotten the offer from eth1 through DHCP.) Note, the chassis doesn't have the SOL link set up properly on the MM (as the CISCO switches cause some problems with that) so I had to screen capture and then copy all the below information by hand. I tried to be meticulous, but it's possible I fat fingered something. Does any of the output information give a hint as to why the eth1 is not? Is it possible there's a problem with the autonegotiation of interrupts of the eth cards? Would setting them to definite values in the BIOS help?
Charles, I looked into your suggestion, but upon examining the tcpdump through ethereal, I can see that a DHCP discover is bein g sent (with accompanying appropriate MAC address for eth1 in the Ethernet II section of its description.) The only thing that I can think that strikes me as strange in the dump are two things. One is that the packet that sends the DHCP Discovery out is listed (in ethereal) as having a source of 0.0.0.0. This didn't concern me as a similar packet that handles the initial DHCP Discover (to start up the network boot in the first place) has the same source listed but works (this is, of course before the initrd and kernel are loaded.) The second thing that seemed interesting was that right before the DHCP Discovery attempt was made (from the loaded systemimager initrd and kernel) there was a Cisco Discovery Protocol (of CDP protocol), then a Dynamic Trunking Protocol (of DTP protocol), then two replies (of LOOP protocol). Not sure if this would be affecting anything or if its part of normal operation of the two cisco switches we have on the chassis.
Ezra, I had tried to get the grub-installer to work after I had pushed the image in its entirety (with my hacked version of initrd.img, kernel, and boel binaries) but there were some weird messages being displayed, basically it didn't recognize that hd0 was a valid device when I tried to run it (I also tried the grub prompt and it didn't recognize hd0 as a valid drive when I ran the root (hd0,0) or setup (hd0) commands.)
Again, thank you guys for your suggestions, the help is greatly appreciated.
Steve
Thanks for your suggestions. I've included below the output of the screen during the boot. It picks up after it has started its network boot (it's already gotten the offer from eth1 through DHCP.) Note, the chassis doesn't have the SOL link set up properly on the MM (as the CISCO switches cause some problems with that) so I had to screen capture and then copy all the below information by hand. I tried to be meticulous, but it's possible I fat fingered something. Does any of the output information give a hint as to why the eth1 is not? Is it possible there's a problem with the autonegotiation of interrupts of the eth cards? Would setting them to definite values in the BIOS help?
Charles, I looked into your suggestion, but upon examining the tcpdump through ethereal, I can see that a DHCP discover is bein g sent (with accompanying appropriate MAC address for eth1 in the Ethernet II section of its description.) The only thing that I can think that strikes me as strange in the dump are two things. One is that the packet that sends the DHCP Discovery out is listed (in ethereal) as having a source of 0.0.0.0. This didn't concern me as a similar packet that handles the initial DHCP Discover (to start up the network boot in the first place) has the same source listed but works (this is, of course before the initrd and kernel are loaded.) The second thing that seemed interesting was that right before the DHCP Discovery attempt was made (from the loaded systemimager initrd and kernel) there was a Cisco Discovery Protocol (of CDP protocol), then a Dynamic Trunking Protocol (of DTP protocol), then two replies (of LOOP protocol). Not sure if this would be affecting anything or if its part of normal operation of the two cisco switches we have on the chassis.
Ezra, I had tried to get the grub-installer to work after I had pushed the image in its entirety (with my hacked version of initrd.img, kernel, and boel binaries) but there were some weird messages being displayed, basically it didn't recognize that hd0 was a valid device when I tried to run it (I also tried the grub prompt and it didn't recognize hd0 as a valid drive when I ran the root (hd0,0) or setup (hd0) commands.)
Again, thank you guys for your suggestions, the help is greatly appreciated.
Steve
Configuration of PCI Interrupt Routing Section section in BIOS
Planar Usb IRQ Autoconfigure
Current Interrupt Assigned IRQ7
Video IntA IRQ Autoconfigure
Curent Unterrupt Assigned IRQ9
Plana
r
Ethernet IRQ Autoconfigure
Current Interrupt Assigned IRQ10
Planar Ethernet IRQ Autoconfigure
Current Interrupt Assigned IRQ11
Settings under PCI Bus Control section
PCI MLT 40h
Output of screen during booting: after it gets its initial pxelinux.cfg file:
Welcome to SystemImager:
*Systemimager message*
boot:
load kernel
.
load initrd.img
Ready
.
896MB LOWMEM available
Checking if this processor honours the WP bit even in supervisor mode. . . Ok.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 8k
CPU: L2 cache: 512k
CPU: Intel® Xeon CPU 3.06GHZ stepping 09
Enabling fast FPU save and restore. . . done
Enabling unmasked SIMD FPU exception support. . .done.
Checking hlt instruction. . .ok
ACPI: setting ELCR to 0010 (from 0eb8)
Checking if image is initramfs
it isnt (no cpio magic); looks like an initrd
Freeing initrd memory:700k freed
NET: Registrered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfd82c, last bus=4
PCI: Using configuration type 1
ACPI: Subsytem revision 20041105
ACPI: Interpreter enabled
ACPI:
Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDR controller 0000:00:0f.1
ACPI: PCI Root Bridge [PCI1] (00:02)
PCI: Probing PCI hardware (bus 02)
ACPI: PCI Root Bridge [PCI2] (00:01)
PCI: Probing PCI hardware (bus 01)
ACPI: PCI Interrupt Link [LPUS] (IRQs *7)
ACPI: PCI Interrupt Link [LPID] (IRQs *14)
Usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
**PCI interrupts are no longer routed automatically. If this
** cau
ses a
device to stop working, it is probably because the
** driver failed to call pci_enable_device(). As a temporary
**workaround, the pci=routeirq argument restores the old
**behavior. If this argument makes the device work again,
** please email the output of lspci to [EMAIL PROTECTED]
**so I can fix the driver.
devfs: 2004-01-31 Richard Gooch ([EMAIL PROTECTED])
devfs: boot_options: 0x1
Initializing Cryptographic API
ACPI: Power Button (FF) [PWRF]
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
elevator: using anticipatory as default io scheduler
Floppy drive(s): fd0 is 1.44M
RAMDISK driver initialized: 16 RAM disks of 8192k size 4096 blocksize
loop: loaded (max 8 devices)
Intel® PRO/1000 Network Driver version 5.5.4-k2-NAPI
Copyright © 1999-2004 Intel Corporation<
/div>
Then the standard This is the Systemimager autoinstall system, your autoinstall has failed, message
Intel® PRO/10Gbe Network Driver version 1.0.66-k2
Copyright © 2001-2004 Intel Corporation
dgrs: SW=$Id: dgrs.c,v 1.13 2000/06/06 04:07:00 rick Exp $ FW=Build 550 11/16/96
03:45:15
FW Version=$Version$
pcnet32.c:v1.30i 06.28.2005 [EMAIL PROTECTED]
e100: Intel® PRO/100 Network Driver, 3.2.3-k2-NAPI
e100: Copyright© 199-2004 Intel Corporation
nsB3B20.c: National Semiconductor DPB3B20 10/100/1000 driver.
tg3.c:v2.14 (November 15, 2004)
ACPI: PCI interrupt 0000:01:00.0[A]: no GSI using IRQ 10
eth0: Tigon3 [partno BCM95704A41) rev 2002 PHY(serdes)] (PCIX:133MHz:64-bit) 10/
100/1000BaseT Ethernet 00:0d:60:9d:76:36
eth0: RXcsums[1] LinkChgReg[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] TSOcap[0]
ACPI: PCI interrupt 0000:01:00.1[B]: no GSI using IRQ 11
Eth1: Tigon3 [partno BCM95704A41) rev 2002 PHY(serdes)] (PCIX:133MHz:64-bit) 10/
100/1000BaseT Ethernet 00:0d:60:9d:76:37
eth1: RXcsums[1] LinkChgReg[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] TSOcap[1]
dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
winbond-B40.c:v1.01-d (2.4 port) Nov-17-2001 D
onald
Becker [EMAIL PROTECTED]
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
SvrWks CSB6: IDE controller at PCI slot 0000:00:0f.1
SvrWks CSB6: chipset revision 176
SvrWks CSB6: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x0700-0x0707, BIOS settings: hda:DMA, hdb:DMA
ide1: B
M-DMA at
0x070B-0x070F, BIOS settings: hdc:DMA, hdd:DMA
hda: FUJITSU MHT2040AS, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: FUJITSU MHT2040AS, ARA DISK drive
ide1 at 0x170-0x177, 0x376 on irq 15
hda: 78140160 sectors (4006 MB) w/8192KiB Cache, CHS=65535/16/63, UDMA(100)
/dev/ide/host0/bus0/target0/lun0: p1 p2
hdc: max request size: 128KiB
hdc: 78140160 sectors (40007 MB) w/8192KiB Cache, CHS=65535/16/63, UDMA(100)
/dev/ide/host0/bus1/target0/lun0: p1
ide-floppy driver 0.99.newide
ACPI: PCI interrupt 0000:00:0f.2[A]: no GSI using IRQ 7
ohci_hcd 0000:00:0f.2: ServerWorks CSB6 OHCI USB Controller
ohci_hcd 0000:00:0f.2: irq 7, pci mem 0xfebfe000
ohci_hcd 0000:00:0f.2: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
USB Universal Host Controller Interface driver v2.2
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
mice: PS/2 mouse device commn for all mice
I2d Core © Copyright 1999 Red Hat Software.
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: ro
uting
cache has table of 8192 buckets, 64k bytes
TCP: Hash tables configured (established 262144 bind 65536)
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun
md:
autorun DONE.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (cramfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 816K freed
init started: BusyBox v1.00 (2005.07.23-21:30+0000) multi-call binary
[:
missing ]
grep: ] : No such file or directory
Loading tmpfs
[: missing ]
grep: ]: No such file or diretory
Didnt load assuming its built into the kernel.
[: missing ]
grep: ]: No such file or directory
[: missing ]
grep: ]: No such file or directory
mount_proc
[: missing ]
grep: ]: No such file or directory
usb 1-2: new full speed USB device using ohci_hcd and address 2
Internet Software Consortium DHCP Client 2.0p15
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consurtium
All rights reserved
Please contribute if you find this software useful
For info, please visit http://www.isc.org/dhcp-contrib.html
ohci_hcd 0000:00:0f.2: Unlink after no-IRQ? Different ACPI or APIC settings may help
tg3: eth1: Link is up at 1000MBps, full duplex
tg3: eth1: flow control is off for TX and off for RX
tg3: eth0: Link is up at 1000 Mbps, full duplex
tg3: eth0: Flwo control is off for TX and off for RX.
Listening on LPF/lo/<null>
Sending on LPF/lo/<null>
Listening on LPF/eth1/00:0d:60:9d:76:37
Sending on LPF/eth1/00:0d:60:9d:76:37
Listening on LPF/eth0/00:0d:60:9d:76:36
Sending on LPF/eth0/00:0d:60:9d:76:36
Sending on Socket/fallback/fallback-net
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
DHCPDIS
COVER on
eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
No DHCPOFFERS received
No working leases in persistent database sleeping
[: missing ]
grep: ] : No such file or directory
I couldnt configure the network interface using DH
CP
[: missing ]
grep: ]: No such file or diretory
[: missing ]
grep: ]: No such file or directory
Killing off running processes.
[: missing ]
grep: ]: No such file or directory
[: missing ]
grep: ]: No such file or directory
write_variables
[: missing ]
grep: ]: No such file or directory
BusyBox v1.00 (2005.07.23-21:30+0000) Built-in shell (ash)
Enter help for a list of built-in commands.
/my_modules #
Where it sits unresponsive to key strokes through the management module
Configuration Menu of Broadcom NetXtreme Ethernet Boot Agent
Broadcom NetXtreme Ethernet Boot Agent v7.0.3
Boot Protocol
Preboot Execution Environment (PXE)
Boot Strap Type Auto Detect
Hide Setup Prompt Disable
Setup Key Stroke Ctrl-S
Banner Message Timeout 4 seconds
Link Speed Autoneg
Pre-boot Wake On Lan Enable
Yahoo! Photos
Got holiday prints? See all the ways to get quality prints in your hands ASAP.
