Re: Updated isboot 0.2.6 and FreeBSD 9.1-RC1

2012-08-24 Thread John Nielsen
Thank you for the quick response!

On Aug 23, 2012, at 6:25 PM, Daisuke Aoyama aoy...@peach.ne.jp wrote:

 It seems a bug of isboot. Your NIC is link down, but isboot never retry
 on first connection. Because of this, it failed to find the boot device.
 
 I have updated isboot and created 9.1-RC based image.
 Please try it:
 
 http://www.peach.ne.jp/archives/isboot/isboot-0.2.6.tar.gz

Working great with the new version of the module. It retries 3-4 times until 
the link comes up then continues. Performing pretty well, too--this is over a 
1Gbps LAN on somewhat dated consumer hardware, with istgt and a ZFS zvol on the 
other end.

 http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-9.1-RC1-amd64-memstick-isboot-0.2.6.img
 
 I have a few questions for you (or other knowledgeable people on the list):
 1) Does iBFT require hardware support in the NIC?
 2) Does iBFT require NIC driver support?
 
 NO. You can use both iBFT software like gPXE and NIC's rom like Intel iSCSI 
 boot agent.
 The isboot should work with any NIC supported by FreeBSD.

Fantastic.

 3) Is anything required in loader.conf besides isboot_load=YES?
 
 If your NIC driver is within the kernel, you need only isboot_load=YES.
 
 4) Is it likely to work (better) if I find an em(4) card instead?
 
 I have tested with Intel cards/onboard. If you want the maximum performance,
 I recommend you to use Intel card, but other cards should work with isboot.

I'll stick with what I have for this machine since it's working. In case you're 
interested, here is the dmesg output from the machine:

mptable_probe: MP Config Table has bad signature: 4\^C\^_
Copyright (c) 1992-2012 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 10.0-CURRENT #2 r239337M: Fri Aug 24 12:58:51 EDT 2012
r...@stealth.jnielsen.net:/usr/obj/i386.i386/usr/src/sys/BUFF i386
CPU: AMD Athlon(tm) XP 2800+ (2079.60-MHz 686-class CPU)
  Origin = AuthenticAMD  Id = 0x6a0  Family = 6  Model = a  Stepping = 0
  
Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
  AMD Features=0xc0400800SYSCALL,MMX+,3DNow!+,3DNow!
real memory  = 1342177280 (1280 MB)
avail memory = 1300516864 (1240 MB)
Event timer LAPIC quality 400
ACPI APIC Table: Nvidia AWRDACPI
ioapic0 Version 1.1 irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0: Nvidia AWRDACPI on motherboard
acpi0: Power Button (fixed)
acpi0: reservation of 0, a (3) failed
acpi0: reservation of 10, 4fef (3) failed
cpu0: ACPI CPU on acpi0
attimer0: AT timer port 0x40-0x43 irq 0 on acpi0
Timecounter i8254 frequency 1193182 Hz quality 0
Event timer i8254 frequency 1193182 Hz quality 100
atrtc0: AT realtime clock port 0x70-0x73 irq 8 on acpi0
Event timer RTC frequency 32768 Hz quality 0
Timecounter ACPI-fast frequency 3579545 Hz quality 900
acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0
acpi_button0: Power Button on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
Correcting nForce2 C1 CPU disconnect hangs
agp0: NVIDIA nForce2 AGP Controller on hostb0
pci0: memory, RAM at device 0.1 (no driver attached)
pci0: memory, RAM at device 0.2 (no driver attached)
pci0: memory, RAM at device 0.3 (no driver attached)
pci0: memory, RAM at device 0.4 (no driver attached)
pci0: memory, RAM at device 0.5 (no driver attached)
isab0: PCI-ISA bridge at device 1.0 on pci0
isa0: ISA bus on isab0
nfsmb0: nForce2/3/4 MCP SMBus Controller port 0xd800-0xd81f irq 23 at device 
1.1 on pci0
smbus0: System Management Bus on nfsmb0
nfsmb1: nForce2/3/4 MCP SMBus Controller on nfsmb0
smbus1: System Management Bus on nfsmb1
ohci0: OHCI (generic) USB controller mem 0xe5085000-0xe5085fff irq 20 at 
device 2.0 on pci0
usbus0 on ohci0
ohci1: OHCI (generic) USB controller mem 0xe5081000-0xe5081fff irq 21 at 
device 2.1 on pci0
usbus1 on ohci1
ehci0: NVIDIA nForce2 USB 2.0 controller mem 0xe5082000-0xe50820ff irq 22 at 
device 2.2 on pci0
usbus2: EHCI version 1.0
usbus2 on ehci0
pci0: multimedia, audio at device 5.0 (no driver attached)
pcm0: nVidia nForce2 port 0xdc00-0xdcff,0xe000-0xe07f mem 
0xe5086000-0xe5086fff irq 21 at device 6.0 on pci0
pcm0: Avance Logic ALC650 AC97 Codec
pcib1: ACPI PCI-PCI bridge at device 8.0 on pci0
pci1: ACPI PCI bus on pcib1
skc0: Marvell Gigabit Ethernet port 0x9000-0x90ff mem 0xe402-0xe4023fff 
irq 17 at device 4.0 on pci1
skc0: Marvell Yukon Lite Gigabit Ethernet rev. A3(0x7)
sk0: Marvell Semiconductor, Inc. Yukon on skc0
sk0: Ethernet address: 00:11:2f:57:f4:bf
miibus0: MII bus on sk0
e1000phy0: Marvell 88E1011 Gigabit PHY PHY 0 on miibus0
e1000phy0:  none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
pci1: simple comms, UART at device 7.0 (no driver attached)
ath0: Atheros 

Updated isboot 0.2.6 and FreeBSD 9.1-RC1

2012-08-23 Thread Daisuke Aoyama

Hi,

Thank you for reporting.

It seems a bug of isboot. Your NIC is link down, but isboot never retry
on first connection. Because of this, it failed to find the boot device.

I have updated isboot and created 9.1-RC based image.
Please try it:

http://www.peach.ne.jp/archives/isboot/isboot-0.2.6.tar.gz
http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-9.1-RC1-amd64-memstick-isboot-0.2.6.img

I have a few questions for you (or other knowledgeable people on the 
list):

1) Does iBFT require hardware support in the NIC?
2) Does iBFT require NIC driver support?


NO. You can use both iBFT software like gPXE and NIC's rom like Intel iSCSI 
boot agent.

The isboot should work with any NIC supported by FreeBSD.


3) Is anything required in loader.conf besides isboot_load=YES?


If your NIC driver is within the kernel, you need only isboot_load=YES.


4) Is it likely to work (better) if I find an em(4) card instead?


I have tested with Intel cards/onboard. If you want the maximum performance,
I recommend you to use Intel card, but other cards should work with isboot.


This is my log of ASRock E350M1/USB3(re(4) + gPXE):
--
iSCSI boot driver version 0.2.6
IS: Initiator name: iqn.2000-09.org.etherboot:e350m1
NIC0: IP address: 172.18.0.131
NIC0: Prefix: 16
NIC0: Gateway: 172.18.0.1
NIC0: MAC address: 00:25:22:b3:b7:a7
TGT0: Target IP address: 172.18.0.26
TGT0: Target Port: 3260
TGT0: Target LUN: 0
TGT0: Target name: iqn.2007-09.jp.ne.peach:aria:e350m1-boot
Boot NIC: re0
Configure IPv4 by NIC0
(snip)
da1 at isboot0 bus 0 scbus8 target 0 lun 0
da1: FreeBSD iSCSI DISK 0001 Fixed Direct Access SCSI-5 device
da1: 300.000MB/s transfers
da1: 20480MB (41943040 512 byte sectors: 255H 63S/T 2610C)
da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
da0:  USB Reader 0001 Removable Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: 1882MB (3854336 512 byte sectors: 255H 63S/T 239C)
da2 at isboot0 bus 0 scbus8 target 0 lun 1
da2: FreeBSD iSCSI DISK 0001 Fixed Direct Access SCSI-5 device
da2: 300.000MB/s transfers
da2: 681MB (1395264 512 byte sectors: 64H 32S/T 681C)
Boot device: da1
SMP: AP CPU #1 Launched!
Timecounter TSC-low frequency 12500234 Hz quality 800
GEOM: da0: the primary GPT table is corrupt or invalid.
GEOM: da0: using the secondary instead -- recovery strongly advised.
GEOM: da2: geometry does not match label (32h,63s != 64h,32s).
GEOM: ufsid/5029dbce6b8b4567: geometry does not match label (32h,63s != 
64h,32s).
GEOM: ufs/FreeBSD_Install: geometry does not match label (32h,63s != 
64h,32s).

Trying to mount root from ufs:/dev/da1p2 [rw]...
--

Thanks,
Daisuke Aoyama


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org