Watchguard Firebox XTM 8 Series
-
pfSense will use com1 but that will just be whatever the first detected com port is. If there's only one enabled it will use that.
Did you use my FreeDOS image? That is configured to use com1 but also to use 9600bps so if you are seeing that then it should be working. If you used a standard FreeDOS image then what you are seeing is being redirected by the BIOS code which remains resident after boot if enabled. This could be interfering perhaps?Try starting your serial terminal at 9600 after the machine has booted. Sometimes putty (if you're using that) has a problem when the baud rate changes.
Steve
-
I saw you had a post of a FreeDos .vhd file but I don't use any virtualisation software on my main pc - I just went to their website and used some images off there and they worked.
I did close down PuTTY between baud changes - I just get garbage and then the garbage stops!
In Advanced>Remote Config screen it has Redirection After BIOS POST [Always]
But I've no way of changing it due to the 'View Only Item' message on everything :(Eamon
-
The .vhd file was my first effort though I think it can be written by anything. Try this image instead:
https://sites.google.com/site/pfsensefirebox/home/FreeDOSBios2.img.gzThat is set to use com1 at 9600 and it will beep three times just before it switches to the serial console.
If pfSense is booting in the background you will see the HD activity LED flashing after the console garbage has stopped. If that isn't happening then I suggest that the image is not writing correctly to the card. What are you extracting it with?
I always use phydiskwriteGUI which does the decompression on the fly. I know some people have had trouble with Windows 7 getting in the way.
Steve
-
You could also try this image which is mostly the same as the other one:
https://sites.google.com/site/pfsensefirebox/home/FreeDOSBios.imgSince that's not gzip'd you won't have to extract it. If that runs but the others didn't you know it's an extraction problem.
Steve
-
Ok, wrote the FreeDosBios2 image to the card - boots up to the DOS menu ok, but after the 3 beeps - nothing (on 115200).
Changed the baud rate to 9600 got the garbage, beeps then nothing again.Did FreeDosBios2 image through WinDiskImager.
Wrote nanobsd.full.img with physdiskwrite - wrote ok - (after using DiskPart to clean the partitions) - got nothing on XTM 8 both at 115200 and 9600.
The HD led does light up during POST but nothing when loading pfSense, however it does flicker up to the beeps on FreeDosBios2 image.
I have read something about UDMA/S.M.A.R.T. having an effect on other Fireboxes - the message shows when pfSense is on the cf card, but doesn't when FreeDos is on it ???
I think my options are:
1. Get a 12pin IDC to 15pin VGA cable and connect up a monitor.
2. Install pfSense on a VM, configure it for COM2 and transfer that to the cf card.
3. Solder a header on to the COM1 space on the board.
4. Flash the BIOS to change COM2 address to the COM1 address.Of which:
1. Do-able but would have to wait a few days for it to arrive.
2. Do-able although I have no knowledge of FreeBSD/pfSense.
3. No chance, I can solder but I'm not willing to risk it on this board.
4. No BIOS update to flash so no go.I'm gonna have a go at changing the FreeDosBios2 image to use COM2 - Dos I can do ;)
Eamon
-
You could also try this image which is mostly the same as the other one:
https://sites.google.com/site/pfsensefirebox/home/FreeDOSBios.imgSince that's not gzip'd you won't have to extract it. If that runs but the others didn't you know it's an extraction problem.
Steve
Tried that one with physdiskwrite - worked the same as the gz one, booted up but that after the beeps nothing :(
Eamon
-
Yes that's the first thing I'd try. Edit the autoexec.bat file to put the console to com2 instead. Relatively easy test and it would confirm the problem.
If you boot with putty at 115200 does it show anything after the bios post that might indicate the card is booting? You should have an opportunity to interrupt the process and give the bootloader some parameters. You could potentially tell it to use com2 at that point.
You could try using one of the nanobsd_vga images. That will attempt to use the keyboard/monitor as the console. The resident bios code may redirect that to the com port. No idea if that would work.
It's possible to modify the bios like I did with the XTM5 but it's risky stuff. I managed to 'brick' the box a number of times but it did give me the opportunity to learn how to recover it! ;D
Steve
-
Ok so I've got a decent version of FreeDOS loaded. I used the image that worked and copied over the other files from the image you posted.
I got a Nanobsd_vga booted to the pfSense menu but then stopped outputting once it carried on, however the HDD light did flicker every so often, nothing came over COM2 :(
I didn't think it would redirect and convert vga to ansi but it was worth a go!
So at the mo I've my own version of the FreeDOSBios image loaded, is there anything I need to run that could be of interest?
Eamon
-
Hmm, OK.
So your hybrid FreeDOS image doesn't switch the console to the com port I take it? Or is it using com2?Interesting the the nanobsd_vga image booted to the menu. I would not expect to see anything on the com port normally from that image. Its console output is all text mode so I would have thought there was a good chance of it being redirected. Can you escape from the boot process at the menu to get a prompt?
So booting the normal nanobsd image do you see anything after the POST?
Steve
-
Yeah with the FreeDOS image I just left everything as it was, no redirection to COM ports done and it works fine - I guess the bios is handling all of the redirection to COM2.
With nanobsd_vga it was just the first pfSense text menu that showed up, then nothing - I guess bios handling the redirection then the switch to vga ends the output.
Booting nanobsg_vga I can escape to a command prompt. I didn't get much out of it as I am not familiar with FreeBSD - managed ls but that was it!
A normal nanobsd image - nothing - however UDMA/SMART message shows in POST - it didn't show with any of the above where I can boot and at least see something.
I've a 12pin IDC to 15pin Vga lead on order from ebay, might make things simplier!
Eamon
-
Ah some progress. :)
Probably the vga cable will make things a lot easier as long as it fits. The boxes I have here have a 2mm pitch connector instead of the more common 2.54mm (0.1"). You have a link to that cable?Here are some things you can do at the boot loader prompt:
http://doc.pfsense.org/index.php/Booting_Options
Though I've never had to try any of them.It appears there is no way (no practical way) use any serial port other than com1 for the console:
@http://www.freebsd.org/doc/en/books/handbook/serialconsole-setup.html:27.6.5.2 Using a Serial Port Other Than sio0 for the Console
Using a port other than sio0 as the console requires the boot blocks, the boot loader, and the kernel to be recompiled as follows.
That's for standard FreeBSD though not NanoBSD. :-\
I take it you tried editing the autoexec.bat file in my FreeDOS image to com2?
Steve
Edit: I see fro your BIOS shots that although there is only one serial port enabled it is still set to com2 and still uses 0x2F8 for its I/O address. Thus if this is hardcoded for com1 it won't work. But FreeDOS should be able to do it.
-
Some other thoughts while I think of it.
There is another difference between the nanobsd and nanobsd_vga images. The straight nano images have dma disabled for the CF card interface. That's because many CF card readers do have required connections for DMA but the cards still report that they are DMA capable causing all sorts of trouble. However the nanobsd_vga image does not do this because it was developed for a specific device that will not boot if DMA is disabled. Could this be an issue here? I think it's probably just that it's trying to use com1 but that doesn't explain why it doesn't continue to boot in the background (flashing the HD LED).One possibility would be to pre-install a config file on the CF card with some interfaces setup and then use the web interface to configure from there.
Steve
-
Ah some progress. :)
Probably the vga cable will make things a lot easier as long as it fits. The boxes I have here have a 2mm pitch connector instead of the more common 2.54mm (0.1"). You have a link to that cable?You're right it's 2mm pitch and not 2.54mm which is what arrived :( The Keyboard/Mouse header is 2.54mm pitch though.
Here are some things you can do at the boot loader prompt:
http://doc.pfsense.org/index.php/Booting_Options
Though I've never had to try any of them.I tried the set console command but got nowhere.
It appears there is no way (no practical way) use any serial port other than com1 for the console:
@http://www.freebsd.org/doc/en/books/handbook/serialconsole-setup.html:27.6.5.2 Using a Serial Port Other Than sio0 for the Console
Using a port other than sio0 as the console requires the boot blocks, the boot loader, and the kernel to be recompiled as follows.
That's for standard FreeBSD though not NanoBSD. :-\
I'm deffo not compiling my own, I don't know anything/enough about FreeBSD to be doing that.
I take it you tried editing the autoexec.bat file in my FreeDOS image to com2?
Steve
Edit: I see fro your BIOS shots that although there is only one serial port enabled it is still set to com2 and still uses 0x2F8 for its I/O address. Thus if this is hardcoded for com1 it won't work. But FreeDOS should be able to do it.
I didn't edit the autoexec.bat file, and I didn't put anything in about COM - just left it as a standard DOS boot up - the BIOS does a good job of redirecting it all to COM2 :)
Eamon
-
Some other thoughts while I think of it.
There is another difference between the nanobsd and nanobsd_vga images. The straight nano images have dma disabled for the CF card interface. That's because many CF card readers do have required connections for DMA but the cards still report that they are DMA capable causing all sorts of trouble. However the nanobsd_vga image does not do this because it was developed for a specific device that will not boot if DMA is disabled. Could this be an issue here? I think it's probably just that it's trying to use com1 but that doesn't explain why it doesn't continue to boot in the background (flashing the HD LED).One possibility would be to pre-install a config file on the CF card with some interfaces setup and then use the web interface to configure from there.
Steve
All the successful boots I've had with pfSense (to the menu) or FreeDos (to the command prompt) is when the UDMA/SMART message hasn't appreared in the POST screen. When it does appear it just blank screens and hangs.
The config file thing is a problem, I can't edit anything on the cf card when pfSense is on it, no go in windows or linux, so kinda stumped on that front.
The VM way might be worth a go. Convert img to vdi, edit, convert back..
Eamon
Eamon
-
You may be able to do this but I don't know if nanobsd checks or not:
http://doc.pfsense.org/index.php/Automatically_Restore_During_InstallI would definitely try one of my images with autoexec edited for com2 instread of com1. That would at least indicate what the issue is.
All the successful boots I've had with pfSense (to the menu) or FreeDos (to the command prompt) is when the UDMA/SMART message hasn't appreared in the POST screen. When it does appear it just blank screens and hangs.
This is interesting. Where exactly does this message appear? The fact that dma is disabled in the image should not affect the POST, how could it.
Steve
-
I was actually looking at this on the FreeBSD website, it seems to be built into FreeBSD's nanobsd build - as it's documented on pfSense I would say it's safe to assume it's in pfSense nanobsd build too.
I'll try out a autoexec with com2 in it and see how that goes. I've another cf card on order so that'll make it easier to deal with mulitple images.
Yeah the UDMA/SMART thing is puzzling, I'll get a log from PuTTY later to show where it is.
Eamon
-
Something else while I think of it. You could potentially change the hardware resource settings for com2 in the BIOS so they use the com1 defaults. Of course you'd need to first mod the bios to open the settings. ;)
Steve
-
Not been on here as much as I expected recently however… I have made some progress!
Forgive me for the lack of PuTTY log for the UDMA/SMART message :(
I've managed to connect a monitor to the onboard VGA connector and I can now see whats happening!
Having gotten nowhere with the nanobsd serial builds due to it being complied for COM1 and this machine having no COM1, I've been trying with the vga builds as they output to text. However they were still no good - it didn't redirect the text screen to COM2 :(
While trying the above on build of pfSense-memstick-2.1-BETA1-i386-20130510-1628.img.gz I had the monitor attached but it's giving me errors about partitioning!
Eamon
![2013-05-13 18.21.30-small.jpg](/public/imported_attachments/1/2013-05-13 18.21.30-small.jpg)
![2013-05-13 18.21.30-small.jpg_thumb](/public/imported_attachments/1/2013-05-13 18.21.30-small.jpg_thumb)
![2013-05-13 18.21.53-small.jpg](/public/imported_attachments/1/2013-05-13 18.21.53-small.jpg)
![2013-05-13 18.21.53-small.jpg_thumb](/public/imported_attachments/1/2013-05-13 18.21.53-small.jpg_thumb) -
Oh forgot to add, I connected a keyboard via usb and it works :)
Eamon
-
Loving your VGA hook up! ;)
The memstick image expects to be connected via USB so if you put it on a CF card it will probably complain.
So with the monitor connected you still can't boot the nano_vga image?
Hmm, I wonder if it set to use dual consoles. I suspect that anything hard coded to talk to the com1 resources will have a problem when they are not available. You'd hope it would fail gracefully but I no idea.Steve
-
Haha, the vga hookup was one of two ways and this was easiest that didn't involve cutting any wires or anything.
Only connected green as I figured it'd let me see everything - apart from bold white!
I'm just writing a nano_vga image as I type on the sandisk 4gig cf card - this one will take the 4gig image!
Eamon
-
Getting some weird READ_DMA error.
Obligatory dmesg:
$ dmesg
Copyright 1992-2010 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 8.1-RELEASE-p13 #0: Fri Apr 12 11:55:06 EDT 2013
root@snapshots-8_1-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap_vga.8.amd64 amd64
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz (2660.01-MHz K8-class CPU)
Origin = "GenuineIntel" Id = 0x1067a Family = 6 Model = 17 Stepping = 10
Features=0xbfebfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Features2=0x408e3fd <sse3,dtes64,mon,ds_cpl,vmx,smx,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,xsave>AMD Features=0x20100800 <syscall,nx,lm>AMD Features2=0x1 <lahf>TSC: P-state invariant
real memory = 2147483648 (2048 MB)
avail memory = 2043940864 (1949 MB)
ACPI APIC Table: <120208 APIC1015>
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
cpu2 (AP): APIC ID: 2
cpu3 (AP): APIC ID: 3
ioapic0 <version 2.0="">irqs 0-23 on motherboard
ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff8040b400, 0) error 1
wlan: mac acl policy registered
ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff8040b4a0, 0) error 1
ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff8040b540, 0) error 1
wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (wpi_fw, 0xffffffff8058a010, 0) error 1
kbd1 at kbdmux0
cryptosoft0: <software crypto="">on motherboard
padlock0: No ACE support.
acpi0: <120208 XSDT1015> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
acpi0: reservation of 0, a0000 (3) failed
acpi0: reservation of 100000, 7f600000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
cpu0: <acpi cpu="">on acpi0
cpu1: <acpi cpu="">on acpi0
cpu2: <acpi cpu="">on acpi0
cpu3: <acpi cpu="">on acpi0
pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
pci0: <acpi pci="" bus="">on pcib0
pcib1: <acpi pci-pci="" bridge="">irq 16 at device 1.0 on pci0
pci7: <acpi pci="" bus="">on pcib1
pcib2: <pci-pci bridge="">mem 0xfe7e0000-0xfe7fffff irq 16 at device 0.0 on pci7
pci8: <pci bus="">on pcib2
pcib3: <pci-pci bridge="">irq 16 at device 0.0 on pci8
pci14: <pci bus="">on pcib3
pci14: <encrypt decrypt,="" network="" computer="" crypto="">at device 0.0 (no driver attached)
pcib4: <pci-pci bridge="">irq 17 at device 1.0 on pci8
pci13: <pci bus="">on pcib4
em0: <intel(r) 1000="" pro="" network="" connection="" 7.3.2="">port 0xec00-0xec1f mem 0xfebe0000-0xfebfffff,0xfebdc000-0xfebdffff irq 17 at device 0.0 on pci13
em0: Using MSIX interrupts with 3 vectors
em0: [ITHREAD]
em0: [ITHREAD]
em0: [ITHREAD]
pcib5: <pci-pci bridge="">irq 16 at device 4.0 on pci8
pci12: <pci bus="">on pcib5
pcib6: <pci-pci bridge="">irq 18 at device 6.0 on pci8
pci11: <pci bus="">on pcib6
em1: <intel(r) 1000="" pro="" network="" connection="" 7.3.2="">port 0xdc00-0xdc1f mem 0xfeae0000-0xfeafffff,0xfeadc000-0xfeadffff irq 18 at device 0.0 on pci11
em1: Using MSIX interrupts with 3 vectors
em1: [ITHREAD]
em1: [ITHREAD]
em1: [ITHREAD]
pcib7: <pci-pci bridge="">irq 16 at device 8.0 on pci8
pci10: <pci bus="">on pcib7
em2: <intel(r) 1000="" pro="" network="" connection="" 7.3.2="">port 0xcc00-0xcc1f mem 0xfe9e0000-0xfe9fffff,0xfe9dc000-0xfe9dffff irq 16 at device 0.0 on pci10
em2: Using MSIX interrupts with 3 vectors
em2: [ITHREAD]
em2: [ITHREAD]
em2: [ITHREAD]
pcib8: <pci-pci bridge="">irq 17 at device 9.0 on pci8
pci9: <pci bus="">on pcib8
em3: <intel(r) 1000="" pro="" network="" connection="" 7.3.2="">port 0xbc00-0xbc1f mem 0xfe8e0000-0xfe8fffff,0xfe8dc000-0xfe8dffff irq 17 at device 0.0 on pci9
em3: Using MSIX interrupts with 3 vectors
em3: [ITHREAD]
em3: [ITHREAD]
em3: [ITHREAD]
vgapci0: <vga-compatible display="">port 0x3800-0x3807 mem 0xfe100000-0xfe17ffff,0xd0000000-0xdfffffff,0xfe000000-0xfe0fffff irq 16 at device 2.0 on pci0
em4: <intel(r) 1000="" pro="" network="" connection="" 7.3.2="">port 0x3880-0x389f mem 0xfe1c0000-0xfe1dffff,0xfe1fe000-0xfe1fefff irq 20 at device 25.0 on pci0
em4: Using an MSI interrupt
em4: [FILTER]
pcib9: <acpi pci-pci="" bridge="">irq 17 at device 28.0 on pci0
pci6: <acpi pci="" bus="">on pcib9
em5: <intel(r) 1000="" pro="" network="" connection="" 7.3.2="">port 0xac00-0xac1f mem 0xfe6e0000-0xfe6fffff irq 16 at device 0.0 on pci6
em5: Using an MSI interrupt
em5: [FILTER]
pcib10: <acpi pci-pci="" bridge="">irq 16 at device 28.1 on pci0
pci5: <acpi pci="" bus="">on pcib10
em6: <intel(r) 1000="" pro="" network="" connection="" 7.3.2="">port 0x9c00-0x9c1f mem 0xfe5e0000-0xfe5fffff irq 17 at device 0.0 on pci5
em6: Using an MSI interrupt
em6: [FILTER]
pcib11: <acpi pci-pci="" bridge="">irq 18 at device 28.2 on pci0
pci4: <acpi pci="" bus="">on pcib11
em7: <intel(r) 1000="" pro="" network="" connection="" 7.3.2="">port 0x8c00-0x8c1f mem 0xfe4e0000-0xfe4fffff irq 18 at device 0.0 on pci4
em7: Using an MSI interrupt
em7: [FILTER]
pcib12: <acpi pci-pci="" bridge="">irq 19 at device 28.3 on pci0
pci3: <acpi pci="" bus="">on pcib12
em8: <intel(r) 1000="" pro="" network="" connection="" 7.3.2="">port 0x7c00-0x7c1f mem 0xfe3e0000-0xfe3fffff irq 19 at device 0.0 on pci3
em8: Using an MSI interrupt
em8: [FILTER]
pcib13: <acpi pci-pci="" bridge="">irq 17 at device 28.4 on pci0
pci2: <acpi pci="" bus="">on pcib13
em9: <intel(r) 1000="" pro="" network="" connection="" 7.3.2="">port 0x6c00-0x6c1f mem 0xfe2e0000-0xfe2fffff irq 16 at device 0.0 on pci2
em9: Using an MSI interrupt
em9: [FILTER]
uhci0: <intel 82801i="" (ich9)="" usb="" controller="">port 0x3c00-0x3c1f irq 23 at device 29.0 on pci0
uhci0: [ITHREAD]
usbus0: <intel 82801i="" (ich9)="" usb="" controller="">on uhci0
uhci1: <intel 82801i="" (ich9)="" usb="" controller="">port 0x4000-0x401f irq 19 at device 29.1 on pci0
uhci1: [ITHREAD]
usbus1: <intel 82801i="" (ich9)="" usb="" controller="">on uhci1
ehci0: <intel 82801i="" (ich9)="" usb="" 2.0="" controller="">mem 0xfe1ff800-0xfe1ffbff irq 23 at device 29.7 on pci0
ehci0: [ITHREAD]
usbus2: EHCI version 1.0
usbus2: <intel 82801i="" (ich9)="" usb="" 2.0="" controller="">on ehci0
pcib14: <acpi pci-pci="" bridge="">at device 30.0 on pci0
pci1: <acpi pci="" bus="">on pcib14
isab0: <pci-isa bridge="">at device 31.0 on pci0
isa0: <isa bus="">on isab0
atapci0: <intel ich9="" sata300="" controller="">port 0x4c00-0x4c07,0x4880-0x4883,0x4800-0x4807,0x4480-0x4483,0x4400-0x440f,0x4080-0x408f irq 19 at device 31.2 on pci0
atapci0: [ITHREAD]
ata2: <ata 0="" channel="">on atapci0
ata2: [ITHREAD]
ata3: <ata 1="" channel="">on atapci0
ata3: [ITHREAD]
pci0: <serial bus,="" smbus="">at device 31.3 (no driver attached)
atapci1: <intel ich9="" sata300="" controller="">port 0x5c00-0x5c07,0x5880-0x5883,0x5800-0x5807,0x5480-0x5483,0x5400-0x540f,0x5080-0x508f irq 19 at device 31.5 on pci0
atapci1: [ITHREAD]
ata4: <ata 0="" channel="">on atapci1
ata4: [ITHREAD]
ata5: <ata 1="" channel="">on atapci1
ata5: [ITHREAD]
acpi_button0: <power button="">on acpi0
atrtc0: <at realtime="" clock="">port 0x70-0x71 irq 8 on acpi0
uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
uart1: [FILTER]
ppc0: <parallel port="">port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppc0: [ITHREAD]
ppbus0: <parallel port="" bus="">on ppc0
ppi0: <parallel i="" o="">on ppbus0
sc0: <system console="">at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
atkbdc0: <keyboard controller="" (i8042)="">at port 0x60,0x64 on isa0
atkbd0: <at keyboard="">irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
Timecounters tick every 10.000 msec
IPsec: Initialized Security Association Processing.
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
usbus2: 480Mbps High Speed USB v2.0
ad7: 3815MB <sandisk sdcfh-004g="" hdx="" 7.07="">at ata3-slave UDMA33 SATA 1.5Gb/s
ugen0.1: <intel>at usbus0
uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
ugen1.1: <intel>at usbus1
uhub1: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus1
ugen2.1: <intel>at usbus2
uhub2: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus2
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
uhub2: 4 ports with 4 removable, self powered
ugen0.2: <chicony>at usbus0
ukbd0: <chicony 0="" 2="" usb="" keyboard,="" class="" 0,="" rev="" 2.00="" 1.57,="" addr="">on usbus0
kbd2 at ukbd0
ad7: FAILURE - READ_DMA timed out LBA=7813117
ad7: TIMEOUT - READ_DMA retrying (1 retry left) LBA=7813119
ad7: FAILURE - READ_DMA timed out LBA=7813103
ad7: TIMEOUT - READ_DMA retrying (0 retries left) LBA=7813119
ad7: FAILURE - READ_DMA timed out LBA=7813116
ad7: FAILURE - READ_DMA timed out LBA=7813119
ad7: FAILURE - READ_DMA timed out LBA=7813119
ad7: FAILURE - READ_DMA timed out LBA=7813119
SMP: AP CPU #1 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #3 Launched!
ad7: TIMEOUT - READ_DMA retrying (1 retry left) LBA=7813119
ad7: TIMEOUT - READ_DMA retrying (0 retries left) LBA=7813119
ad7: FAILURE - READ_DMA timed out LBA=7813119
Trying to mount root from ufs:/dev/ufs/pfsense0
ad7: FAILURE - SETFEATURES 0x85 status=51 <ready,dsc,error>error=4 <aborted>pflog0: promiscuous mode enabled
ad7: TIMEOUT - READ_DMA retrying (1 retry left) LBA=7813119
ad7: TIMEOUT - READ_DMA retrying (0 retries left) LBA=7813119
ad7: FAILURE - READ_DMA timed out LBA=7813119
ad7: TIMEOUT - READ_DMA retrying (1 retry left) LBA=7813119
ad7: TIMEOUT - READ_DMA retrying (0 retries left) LBA=7813119Eamon</aborted></ready,dsc,error></chicony></chicony></intel></intel></intel></intel></intel></intel></sandisk></at></keyboard></generic></system></parallel></parallel></parallel></at></power></ata></ata></intel></serial></ata></ata></intel></isa></pci-isa></acpi></acpi></intel></intel></intel></intel></intel></intel></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel(r)></acpi></acpi></intel(r)></vga-compatible></intel(r)></pci></pci-pci></intel(r)></pci></pci-pci></intel(r)></pci></pci-pci></pci></pci-pci></intel(r)></pci></pci-pci></encrypt></pci></pci-pci></pci></pci-pci></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></software></version></lahf></syscall,nx,lm></sse3,dtes64,mon,ds_cpl,vmx,smx,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,xsave></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>
-
Right, that's what I mentioned earlier. The nanobsd_vga images have DMA enabled because of a specific device but many CF card slots do not have enough pins. Probably that's what's happening here.
Interrupt the boot process at the loader menu and do this:
http://doc.pfsense.org/index.php/Booting_Options#Disable_DMA_for_IDE_drivesSteve
-
My suspicion, based on the high LBA reported, is that your 4GB card is a bit short of providing 4GiB (1024 x 1024 x 1024) and the 4G image didn't quite fit. Some people have had to put a 2GB image on a "4GB" card/stick. Note the card is reported having 3815MB which would allow a LBA of up to around 7630000 which is a bit short of the reported LBAs.
If I recall correctly, the FreeBSD GEOM component goes looking for a GEOM signature on the apparent last sector or two of the disk.
-
I put a 2g nano_vga 64bit image on the same card and got the same LBA error.
Did the set hw.ata.atapi_dma=0 thing too which stopped the LBA errors, however got a different LBA error!
ad7: 3815MB <sandisk sdcfh-004g="" hdx="" 7.07="">at ata3-slave PIO4 SATA 1.5Gb/s
ad7: FAILURE - READ status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=7813117
ad7: FAILURE - READ status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=7813119
ad7: FAILURE - READ status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=7813103
ad7: FAILURE - READ status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=7813116
ad7: FAILURE - READ status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=7813119
ad7: FAILURE - READ status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=7813119
SMP: AP CPU #2 Launched!
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
ugen0.u1g:ue gn <e2i.nn11t.:e 1l:<="">I <naittne ltue="">s lb>au ts a0tus
ubsubsu2s
u1h
ub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
uhub1: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus2
uhub2: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus1
ad7: FAILURE - READ status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=7813119
Root mount waiting for: usbus2 usbus1 usbus0
uhub2: 2 ports with 2 removable, self powered
uhub0: 2 ports with 2 removable, self powered
Root mount waiting for: usbus2
uhub1: 4 ports with 4 removable, self powered
Trying to mount root from ufs:/dev/ufs/pfsense0
ad7: FAILURE - SETFEATURES 0x85 status=51 <ready,dsc,error>error=4 <aborted>ugen0.2: <chicony>at usbus0
ukbd0: <chicony 0="" 2="" usb="" keyboard,="" class="" 0,="" rev="" 2.00="" 1.57,="" addr="">on usbus0
kbd2 at ukbd0
pflog0: promiscuous mode enabled
ad7: FAILURE - READ status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=7813119
ad7: FAILURE - READ status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=7813119
ad7: FAILURE - READ status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=7813119
ad7: FAILURE - READ status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=7813119
ad7: FAILURE - READ status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=7813119
ad7: FAILURE - READ status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=7813119
ad7: FAILURE - READ status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=7813119
ad7: FAILURE - READ status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=7813119
ad7: FAILURE - READ status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=7813119
ad7: FAILURE - READ status=51 <ready,dsc,error>error=10 <nid_not_found>LBA=7813119Burning 2g nano_vga 32bit gives the same error on the same card (4gig SanDisk Ultra)
Booting up on the no name cf card with the same 32bit 2g nano_vga image gives no errors - no ser hw.ata.ata_dma=0 performed - wierd;
ad7: 3639MB <cf card="" ver5.04="">at ata3-slave UDMA33 SATA 1.5Gb/s
SMP: AP CPU #2 Launched!
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
ugen0u.1g:e n<2I.n1t:e l<>I natte l>u saubtu guss0beuns1
2.1
: <intel>at usbus1
uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
uhub1: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus1
uhub2: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus2
Root mount waiting for: usbus2 usbus1 usbus0
uhub1: 2 ports with 2 removable, self powered
uhub0: 2 ports with 2 removable, self powered
Root mount waiting for: usbus2
uhub2: 4 ports with 4 removable, self powered
Trying to mount root from ufs:/dev/ufs/pfsense0
ugen0.2: <chicony>at usbus0
ukbd0: <chicony 0="" 2="" usb="" keyboard,="" class="" 0,="" rev="" 2.00="" 1.57,="" addr="">on usbus0
kbd2 at ukbd0
pflog0: promiscuous mode enabledHow very bizarre.
Eamon</chicony></chicony></intel></intel></intel></intel></cf></nid_not_found></ready,dsc,error></nid_not_found></ready,dsc,error></nid_not_found></ready,dsc,error></nid_not_found></ready,dsc,error></nid_not_found></ready,dsc,error></nid_not_found></ready,dsc,error></nid_not_found></ready,dsc,error></nid_not_found></ready,dsc,error></nid_not_found></ready,dsc,error></nid_not_found></ready,dsc,error></chicony></chicony></aborted></ready,dsc,error></nid_not_found></ready,dsc,error></intel></intel></intel></naittne></e2i.nn11t.:e></nid_not_found></ready,dsc,error></nid_not_found></ready,dsc,error></nid_not_found></ready,dsc,error></nid_not_found></ready,dsc,error></nid_not_found></ready,dsc,error></nid_not_found></ready,dsc,error></sandisk>
-
The 'nid not found' error is common and nothing to worry about:
http://doc.pfsense.org/index.php/DMA_and_LBA_ErrorsI would guess that your no-name card is not DMA capable so didn't cause the problem.
Did it boot successfully then?
Steve
-
Damn I bought the exact same cf card that's in that link! I guess that's that error sorted then.
Yes it did boot, even with the LBA errors, looks like it was a combination of both errors mentioned by yourself and wallabybob.
Its pretty nippy to say the least ;)
I gotta figure out how to set it up now. At least 10x GbE ports gives me plenty to play with haha!I've contacted Lanner to see if I can get the BIOS for the 8750 this is based on, that would help even further.
Eamon
-
The LCD seems to be the same as previous models as you say so should be ok.
There is an arm/disarm led on the front, it hasn't lit up yet.
There is some useful info there about the FW-8750 of which this board seems to be from:
Platform
Chipset: Intel Q35 + ICH9D0Eamon
The LCD code assumes parallel port, so, at a minimum, the sdeclcd driver part of the lcdproc package should run. Might even work, too.
For the LEDs, the driver code supports the various models based on standard PCI detection of the ICH. We definitely need to add an entry for this ICH9 in the driver code. Once you guys get around to it, can you confirm this is, in fact, an ICH9D0, identified by Vendor x8086, device x2914 (the numbers are listed on page 12 of the "Intel I/O Controller Hub 9 (ICH9) Family Specification Update")?
Generally, the LEDs can be wired off of the GPIO device part of this ICH (like in the older models), but, more likely, they are wired off of the SuperIO chip (like the XTM 5). A further screen shot seems to list an ITE8718. This is where the research comes in to identify which line these LEDs are wired off of. I'll be happy to code this in when it is discovered.
-
Commence experimental probing! ;D
Since you don't have the Watchguard OS we can't look for clues in it's boot messages.
Not using a Winbond sio chip, interesting.
You could extract the bios code with flashrom and look at it for hidden menus.
Steve
Edit: Looks to be supported by superiotool as well.
-
fmertz:
Ok, fired up lcdproc, but nothing seems to happen :(The boot up screen shows 'Starting package LCDproc…done.'
Under Status: Services it shows as Stopped. Clicking to start it doesn't change it's status.
ICH9 Chipset - think you were right, experimental probe..:
$ pciconf -lc
hostb0@pci0:0:0:0: class=0x060000 card=0x29b08086 chip=0x29b08086 rev=0x02 hdr=0x00
cap 09[e0] = vendor (length 11) Intel cap 11 version 1
pcib1@pci0:0:1:0: class=0x060400 card=0x29b18086 chip=0x29b18086 rev=0x02 hdr=0x01
cap 0d[88] = PCI Bridge card=0x29b18086
cap 01[80] = powerspec 3 supports D0 D3 current D0
cap 05[90] = MSI supports 1 message
cap 10[a0] = PCI-Express 1 root port max data 128(128) link x4(x16)
vgapci0@pci0:0:2:0: class=0x030000 card=0x29b28086 chip=0x29b28086 rev=0x02 hdr=0x00
cap 05[90] = MSI supports 1 message
cap 01[d0] = powerspec 2 supports D0 D3 current D0
em4@pci0:0:25:0: class=0x020000 card=0x00008086 chip=0x10bd8086 rev=0x02 hdr=0x00
cap 01[c8] = powerspec 2 supports D0 D3 current D0
cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
cap 13[e0] = PCI Advanced Features: FLR TP
pcib9@pci0:0:28:0: class=0x060400 card=0x29408086 chip=0x29408086 rev=0x02 hdr=0x01
cap 10[40] = PCI-Express 1 root port max data 128(128) link x1(x1)
cap 05[80] = MSI supports 1 message
cap 0d[90] = PCI Bridge card=0x29408086
cap 01[a0] = powerspec 2 supports D0 D3 current D0
pcib10@pci0:0:28:1: class=0x060400 card=0x29428086 chip=0x29428086 rev=0x02 hdr=0x01
cap 10[40] = PCI-Express 1 root port max data 128(128) link x1(x1)
cap 05[80] = MSI supports 1 message
cap 0d[90] = PCI Bridge card=0x29428086
cap 01[a0] = powerspec 2 supports D0 D3 current D0
pcib11@pci0:0:28:2: class=0x060400 card=0x29448086 chip=0x29448086 rev=0x02 hdr=0x01
cap 10[40] = PCI-Express 1 root port max data 128(128) link x1(x1)
cap 05[80] = MSI supports 1 message
cap 0d[90] = PCI Bridge card=0x29448086
cap 01[a0] = powerspec 2 supports D0 D3 current D0
pcib12@pci0:0:28:3: class=0x060400 card=0x29468086 chip=0x29468086 rev=0x02 hdr=0x01
cap 10[40] = PCI-Express 1 root port max data 128(128) link x1(x1)
cap 05[80] = MSI supports 1 message
cap 0d[90] = PCI Bridge card=0x29468086
cap 01[a0] = powerspec 2 supports D0 D3 current D0
pcib13@pci0:0:28:4: class=0x060400 card=0x29488086 chip=0x29488086 rev=0x02 hdr=0x01
cap 10[40] = PCI-Express 1 root port max data 128(128) link x1(x1)
cap 05[80] = MSI supports 1 message
cap 0d[90] = PCI Bridge card=0x29488086
cap 01[a0] = powerspec 2 supports D0 D3 current D0
uhci0@pci0:0:29:0: class=0x0c0300 card=0x29348086 chip=0x29348086 rev=0x02 hdr=0x00
cap 13[50] = PCI Advanced Features: FLR TP
uhci1@pci0:0:29:1: class=0x0c0300 card=0x29358086 chip=0x29358086 rev=0x02 hdr=0x00
cap 13[50] = PCI Advanced Features: FLR TP
ehci0@pci0:0:29:7: class=0x0c0320 card=0x293a8086 chip=0x293a8086 rev=0x02 hdr=0x00
cap 01[50] = powerspec 2 supports D0 D3 current D0
cap 0a[58] = EHCI Debug Port at offset 0xa0 in map 0x14
cap 13[98] = PCI Advanced Features: FLR TP
pcib14@pci0:0:30:0: class=0x060401 card=0x244e8086 chip=0x244e8086 rev=0x92 hdr=0x01
cap 0d[50] = PCI Bridge card=0x244e8086
isab0@pci0:0:31:0: class=0x060100 card=0x29148086 chip=0x29148086 rev=0x02 hdr=0x00
cap 09[e0] = vendor (length 12) Intel cap 1 version 0
features: SATA RAID-5, 4 PCI-e x1 slots
atapci0@pci0:0:31:2: class=0x01018f card=0x29208086 chip=0x29208086 rev=0x02 hdr=0x00
cap 01[70] = powerspec 3 supports D0 D3 current D0
cap 13[b0] = PCI Advanced Features: FLR TP
none0@pci0:0:31:3: class=0x0c0500 card=0x29308086 chip=0x29308086 rev=0x02 hdr=0x00
atapci1@pci0:0:31:5: class=0x010185 card=0x29268086 chip=0x29268086 rev=0x02 hdr=0x00
cap 01[70] = powerspec 3 supports D0 D3 current D0
cap 13[b0] = PCI Advanced Features: FLR TP
pcib2@pci0:7:0:0: class=0x060400 card=0x862410b5 chip=0x862410b5 rev=0xbb hdr=0x01
cap 01[40] = powerspec 3 supports D0 D3 current D0
cap 05[48] = MSI supports 4 messages, 64 bit, vector masks
cap 10[68] = PCI-Express 2 upstream port max data 128(2048) link x4(x4)
cap 0d[a4] = PCI Bridge card=0x862410b5
pcib3@pci0:8:0:0: class=0x060400 card=0x862410b5 chip=0x862410b5 rev=0xbb hdr=0x01
cap 01[40] = powerspec 3 supports D0 D3 current D0
cap 05[48] = MSI supports 4 messages, 64 bit, vector masks
cap 10[68] = PCI-Express 2 downstream port max data 128(2048) link x4(x4)
cap 0d[a4] = PCI Bridge card=0x862410b5
pcib4@pci0:8:1:0: class=0x060400 card=0x862410b5 chip=0x862410b5 rev=0xbb hdr=0x01
cap 01[40] = powerspec 3 supports D0 D3 current D0
cap 05[48] = MSI supports 4 messages, 64 bit, vector masks
cap 10[68] = PCI-Express 2 downstream port max data 128(2048) link x1(x4)
cap 0d[a4] = PCI Bridge card=0x862410b5
pcib5@pci0:8:4:0: class=0x060400 card=0x862410b5 chip=0x862410b5 rev=0xbb hdr=0x01
cap 01[40] = powerspec 3 supports D0 D3 current D0
cap 05[48] = MSI supports 4 messages, 64 bit, vector masks
cap 10[68] = PCI-Express 2 downstream port max data 128(2048) link x0(x8)
cap 0d[a4] = PCI Bridge card=0x862410b5
pcib6@pci0:8:6:0: class=0x060400 card=0x862410b5 chip=0x862410b5 rev=0xbb hdr=0x01
cap 01[40] = powerspec 3 supports D0 D3 current D0
cap 05[48] = MSI supports 4 messages, 64 bit, vector masks
cap 10[68] = PCI-Express 2 downstream port max data 128(2048) link x1(x4)
cap 0d[a4] = PCI Bridge card=0x862410b5
pcib7@pci0:8:8:0: class=0x060400 card=0x862410b5 chip=0x862410b5 rev=0xbb hdr=0x01
cap 01[40] = powerspec 3 supports D0 D3 current D0
cap 05[48] = MSI supports 4 messages, 64 bit, vector masks
cap 10[68] = PCI-Express 2 downstream port max data 128(2048) link x1(x4)
cap 0d[a4] = PCI Bridge card=0x862410b5
pcib8@pci0:8:9:0: class=0x060400 card=0x862410b5 chip=0x862410b5 rev=0xbb hdr=0x01
cap 01[40] = powerspec 3 supports D0 D3 current D0
cap 05[48] = MSI supports 4 messages, 64 bit, vector masks
cap 10[68] = PCI-Express 2 downstream port max data 128(2048) link x1(x4)
cap 0d[a4] = PCI Bridge card=0x862410b5
none1@pci0:14:0:0: class=0x100000 card=0x0001177d chip=0x0010177d rev=0x01 hdr=0x00
cap 01[40] = powerspec 3 supports D0 D3 current D0
cap 05[50] = MSI supports 1 message, 64 bit
cap 10[70] = PCI-Express 1 endpoint max data 128(256) link x4(x4)
em0@pci0:13:0:0: class=0x020000 card=0x00008086 chip=0x10d38086 rev=0x00 hdr=0x00
cap 01[c8] = powerspec 2 supports D0 D3 current D0
cap 05[d0] = MSI supports 1 message, 64 bit
cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
cap 11[a0] = MSI-X supports 3 messages in map 0x1c enabled
em1@pci0:11:0:0: class=0x020000 card=0x00008086 chip=0x10d38086 rev=0x00 hdr=0x00
cap 01[c8] = powerspec 2 supports D0 D3 current D0
cap 05[d0] = MSI supports 1 message, 64 bit
cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
cap 11[a0] = MSI-X supports 3 messages in map 0x1c enabled
em2@pci0:10:0:0: class=0x020000 card=0x00008086 chip=0x10d38086 rev=0x00 hdr=0x00
cap 01[c8] = powerspec 2 supports D0 D3 current D0
cap 05[d0] = MSI supports 1 message, 64 bit
cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
cap 11[a0] = MSI-X supports 3 messages in map 0x1c enabled
em3@pci0:9:0:0: class=0x020000 card=0x00008086 chip=0x10d38086 rev=0x00 hdr=0x00
cap 01[c8] = powerspec 2 supports D0 D3 current D0
cap 05[d0] = MSI supports 1 message, 64 bit
cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
cap 11[a0] = MSI-X supports 3 messages in map 0x1c enabled
em5@pci0:6:0:0: class=0x020000 card=0x00008086 chip=0x109a8086 rev=0x00 hdr=0x00
cap 01[c8] = powerspec 2 supports D0 D3 current D0
cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
em6@pci0:5:0:0: class=0x020000 card=0x00008086 chip=0x109a8086 rev=0x00 hdr=0x00
cap 01[c8] = powerspec 2 supports D0 D3 current D0
cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
em7@pci0:4:0:0: class=0x020000 card=0x00008086 chip=0x109a8086 rev=0x00 hdr=0x00
cap 01[c8] = powerspec 2 supports D0 D3 current D0
cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
em8@pci0:3:0:0: class=0x020000 card=0x00008086 chip=0x109a8086 rev=0x00 hdr=0x00
cap 01[c8] = powerspec 2 supports D0 D3 current D0
cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)
em9@pci0:2:0:0: class=0x020000 card=0x00008086 chip=0x109a8086 rev=0x00 hdr=0x00
cap 01[c8] = powerspec 2 supports D0 D3 current D0
cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message
cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1)Stephen:
I managed to upload superiotool to /tmp/ but don't know how to run it :(Ditto flashrom!
Eamon
-
Another experimental probe..
$ sysctl hw
hw.machine: i386
hw.model: Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
hw.ncpu: 4
hw.byteorder: 1234
hw.physmem: 2120441856
hw.usermem: 2066382848
hw.pagesize: 4096
hw.floatingpoint: 1
hw.machine_arch: i386
hw.realmem: 2137784320
hw.amr.force_sg32: 0
hw.an.an_cache_iponly: 1
hw.an.an_cache_mcastonly: 0
hw.an.an_cache_mode: dbm
hw.an.an_dump: off
hw.ata.setmax: 0
hw.ata.wc: 1
hw.ata.atapi_dma: 1
hw.ata.ata_dma_check_80pin: 1
hw.ata.ata_dma: 1
hw.ath.bstuck: 4
hw.ath.txbuf: 200
hw.ath.rxbuf: 40
hw.ath.resetcal: 1200
hw.ath.shortcal: 100
hw.ath.longcal: 30
hw.ath.hal.swba_backoff: 0
hw.ath.hal.sw_brt: 10
hw.ath.hal.dma_brt: 2
hw.bce.msi_enable: 1
hw.bce.tso_enable: 1
hw.bge.allow_asf: 0
hw.bt848.slow_msp_audio: -1
hw.bt848.format: -1
hw.bt848.reverse_mute: -1
hw.bt848.tuner: -1
hw.bt848.card: -1
hw.bwn.wme: 1
hw.bwn.usedma: 1
hw.bwn.hwpctl: 0
hw.bwn.bluetooth: 1
hw.bwn.bfp: 0
hw.cardbus.cis_debug: 0
hw.cardbus.debug: 0
hw.cxgb.snd_queue_len: 128
hw.cxgb.use_16k_clusters: -1
hw.cxgb.force_fw_update: 0
hw.cxgb.multiq: 1
hw.cxgb.ofld_disable: 0
hw.cxgb.msi_allowed: 2
hw.cxgb.tx_reclaim_threshold: 32
hw.cxgb.tx_coalesce_enable_stop: 256
hw.cxgb.tx_coalesce_enable_start: 512
hw.cxgb.tx_coalesce_force: 0
hw.cxgb.txq_mr_size: 1024
hw.em.eee_setting: 0
hw.em.rx_process_limit: 100
hw.em.enable_msix: 1
hw.em.sbp: 0
hw.em.smart_pwr_down: 0
hw.em.txd: 1024
hw.em.rxd: 1024
hw.em.rx_abs_int_delay: 66
hw.em.tx_abs_int_delay: 66
hw.em.rx_int_delay: 0
hw.em.tx_int_delay: 66
hw.igb.rx_process_limit: 100
hw.igb.num_queues: 0
hw.igb.header_split: 0
hw.igb.max_interrupt_rate: 8000
hw.igb.enable_msix: 1
hw.igb.enable_aim: 1
hw.igb.txd: 1024
hw.igb.rxd: 1024
hw.firewire.hold_count: 0
hw.firewire.try_bmr: 1
hw.firewire.fwmem.speed: 2
hw.firewire.fwmem.eui64_lo: 0
hw.firewire.fwmem.eui64_hi: 0
hw.firewire.phydma_enable: 1
hw.firewire.nocyclemaster: 0
hw.firewire.fwe.rx_queue_len: 128
hw.firewire.fwe.tx_speed: 2
hw.firewire.fwe.stream_ch: 1
hw.firewire.sbp.tags: 0
hw.firewire.sbp.use_doorbell: 0
hw.firewire.sbp.scan_delay: 500
hw.firewire.sbp.login_delay: 1000
hw.firewire.sbp.exclusive_login: 1
hw.firewire.sbp.max_speed: -1
hw.firewire.sbp.auto_login: 1
hw.hifn.maxbatch: 1
hw.hifn.debug: 0
hw.malo.txbuf: 256
hw.malo.rxquota: 256
hw.malo.rxbuf: 256
hw.malo.txcoalesce: 8
hw.malo.pci.msi_disable: 0
hw.mfi.max_cmds: 128
hw.mfi.event_class: 0
hw.mfi.event_locale: 65535
hw.mwl.rxdmalow: 3
hw.mwl.rxquota: 640
hw.mwl.txcoalesce: 8
hw.mwl.txbuf: 256
hw.mwl.rxbuf: 640
hw.mwl.rxdesc: 256
hw.pccard.cis_debug: 0
hw.pccard.debug: 0
hw.cbb.debug: 0
hw.cbb.start_32_io: 4096
hw.cbb.start_16_io: 256
hw.cbb.start_memory: 2281701376
hw.pcic.pd6722_vsense: 1
hw.pcic.intr_mask: 57016
hw.pci.usb_early_takeover: 1
hw.pci.honor_msi_blacklist: 1
hw.pci.enable_msix: 1
hw.pci.enable_msi: 1
hw.pci.do_power_resume: 1
hw.pci.do_power_nodriver: 0
hw.pci.enable_io_modes: 1
hw.pci.default_vgapci_unit: -1
hw.pci.host_mem_start: 2147483648
hw.pci.mcfg: 1
hw.pci.irq_override_mask: 57080
hw.safe.rngmaxalarm: 8
hw.safe.rngbufsize: 16
hw.safe.rnginterval: 1
hw.syscons.kbd_debug: 1
hw.syscons.kbd_reboot: 0
hw.syscons.bell: 1
hw.syscons.saver.keybonly: 1
hw.syscons.sc_no_suspend_vtswitch: 0
hw.usb.no_boot_wait: 0
hw.usb.debug: 0
hw.usb.usb_lang_mask: 255
hw.usb.usb_lang_id: 9
hw.usb.template: 0
hw.usb.power_timeout: 30
hw.usb.uath.regdomain: 0
hw.usb.uath.countrycode: 0
hw.usb.urtw.preamble_mode: 2
hw.usb.urtw.debug: 0
hw.usb.ucom.cons_baud: 9600
hw.usb.ucom.cons_unit: -1
hw.wi.debug: 0
hw.wi.txerate: 0
hw.intr_storm_threshold: 1000
hw.pagesizes: 4096 0
hw.availpages: 517686
hw.bus.devctl_queue: 1000
hw.bus.devctl_disable: 0
hw.kbd.keymap_restrict_change: 0
hw.nve_pollinterval: 0
hw.busdma.total_bpages: 128
hw.busdma.zone0.total_bpages: 128
hw.busdma.zone0.free_bpages: 128
hw.busdma.zone0.reserved_bpages: 0
hw.busdma.zone0.active_bpages: 0
hw.busdma.zone0.total_bounced: 0
hw.busdma.zone0.total_deferred: 0
hw.busdma.zone0.lowaddr: 0xffffffff
hw.busdma.zone0.alignment: 4096
hw.clockrate: 2660
hw.via_feature_xcrypt: 0
hw.via_feature_rng: 0
hw.instruction_sse: 1
hw.apic.enable_extint: 0
hw.mca.erratum383: 0
hw.mca.amd10h_L1TP: 1
hw.mca.enabled: 1
hw.mca.count: 0
hw.mca.interval: 3600
hw.mca.force_scan: 0
hw.acpi.supported_sleep_state: S1 S4 S5
hw.acpi.power_button_state: S5
hw.acpi.sleep_button_state: S1
hw.acpi.lid_switch_state: NONE
hw.acpi.standby_state: S1
hw.acpi.suspend_state: NONE
hw.acpi.sleep_delay: 1
hw.acpi.s4bios: 0
hw.acpi.verbose: 0
hw.acpi.disable_on_reboot: 0
hw.acpi.handle_reboot: 0
hw.acpi.reset_video: 0
hw.acpi.cpu.cx_lowest: C1Eamon
-
Another..
$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=_PR_.P001
dev.cpu.0.%pnpinfo: _HID=none UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.cx_supported: C1/0
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% last 5000us
dev.cpu.0.freq: 330
dev.cpu.0.freq_levels: 2646/-1 2315/-1 1984/-1 1653/-1 1323/-1 992/-1 661/-1 330/-1
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=_PR.P002
dev.cpu.1.%pnpinfo: _HID=none UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/0
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% last 5000us
dev.cpu.2.%desc: ACPI CPU
dev.cpu.2.%driver: cpu
dev.cpu.2.%location: handle=_PR.P003
dev.cpu.2.%pnpinfo: _HID=none UID=0
dev.cpu.2.%parent: acpi0
dev.cpu.2.cx_supported: C1/0
dev.cpu.2.cx_lowest: C1
dev.cpu.2.cx_usage: 100.00% last 5000us
dev.cpu.3.%desc: ACPI CPU
dev.cpu.3.%driver: cpu
dev.cpu.3.%location: handle=_PR.P004
dev.cpu.3.%pnpinfo: _HID=none _UID=0
dev.cpu.3.%parent: acpi0
dev.cpu.3.cx_supported: C1/0
dev.cpu.3.cx_lowest: C1
dev.cpu.3.cx_usage: 100.00% last 5000usEamon
-
To use either of those tools you have to install the FreeBSD package properly, so:
As you are running NanoBD first remount the filesystem read-write
[2.0.3-RELEASE][root@pfsense.fire.box]/root(1): /etc/rc.conf_mount_rw
Then add the package. You have to specify the complete path beacsue FreeBSD 8.1 is now quite old
[2.0.3-RELEASE][root@pfsense.fire.box]/root(2): pkg_add -r ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-8.1-release/Latest/superiotool.tbz Fetching ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-8.1-release/Latest/superiotool.tbz... Done.
same for flashrom
[2.0.3-RELEASE][root@pfsense.fire.box]/root(3): pkg_add -r ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-8.1-release/Latest/flashrom.tbz Fetching ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-8.1-release/Latest/flashrom.tbz... Done. Fetching ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-8.1-release/All/libpci-3.1.7_1.tbz... Done.
Then remount the filesystem read-only again
[2.0.3-RELEASE][root@pfsense.fire.box]/root(4): /etc/rc.conf_mount_ro
Finally issue a rehash to re-index the new files so FreeBSD knows where to find them
[2.0.3-RELEASE][root@pfsense.fire.box]/root(5): rehash
Now you run the tools. :)
After you install the lcdproc-dev package via the pfSense GUI you have to configure the various parameters before it will run and then start the service manually the first time in Status: Services:
Steve
-
isab0@pci0:0:31:0: class=0x060100 card=0x29148086 chip=0x29148086 rev=0x02 hdr=0x00
Yep, confirmed ICH9D0. Dom 0, bus 0, device 31, function 0 is the L(ow)P(in)C(ount) device. We can use it to identify the exact ICH model number.
-
I had lcdproc loaded - removed and installed lcdproc-dev - selected WatchGuard Firebox with SDEC (x86only) - see attached pics.
Looks like powerd is doing it's job running the cpu at 330Mhz - fans however haven't slowed down any though :(
Superiotool probe..:
$ superiotool -d
superiotool r
Found ITE IT8718F (id=0x8718, rev=0x4) at 0x2e
Register dump:
idx 20 21 22 23 24 2b
val 87 18 04 10 00 00
def 87 18 01 00 00 00
LDN 0x00 (Floppy)
idx 30 60 61 70 74 f0 f1
val 00 00 00 00 04 00 00
def 00 03 f0 06 02 00 00
LDN 0x01 (COM1)
idx 30 60 61 70 f0 f1 f2 f3
val 00 03 f8 04 00 50 00 7f
def 00 03 f8 04 00 50 00 7f
LDN 0x02 (COM2)
idx 30 60 61 70 f0 f1 f2 f3
val 01 02 f8 03 00 50 00 7f
def 00 02 f8 03 00 50 00 7f
LDN 0x03 (Parallel port)
idx 30 60 61 62 63 70 74 f0
val 01 03 78 00 00 07 04 08
def 00 03 78 07 78 07 03 03
LDN 0x04 (Environment controller)
idx 30 60 61 62 63 70 f0 f1 f2 f3 f4 f5 f6
val 01 0a 10 0a 00 00 80 00 00 00 a0 00 ff
def 00 02 90 02 30 09 00 00 00 00 00 NA NA
LDN 0x05 (Keyboard)
idx 30 60 61 62 63 70 71 f0
val 01 00 60 00 64 01 02 00
def 01 00 60 00 64 01 02 00
LDN 0x06 (Mouse)
idx 30 70 71 f0
val 01 0c 02 00
def 00 0c 02 00
LDN 0x07 (GPIO)
idx 25 26 27 28 29 2a 2c 60 61 62 63 64 65 70 71 72 73 74 b0 b1 b2 b3 b4 b5 b8 b9 ba bb bc bd c0 c1 c2 c3 c4 c5 c8 c9 ca cb cc e0 e1 e2 e3 e4 e5 e6 e7 f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb fc fd fe ff
val 41 d3 00 00 00 20 1f 00 00 0a 20 0a 30 00 00 00 00 00 00 00 00 00 00 00 40 00 00 00 00 00 40 d3 00 40 00 00 40 d0 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 bc 00 00 00
def 01 00 00 40 00 00 00 00 00 00 00 00 00 00 00 20 38 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00 40 00 00 01 00 00 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 NA 00 00 00
LDN 0x0a (Consumer IR)
idx 30 60 61 70 f0
val 00 00 00 00 06
def 00 03 10 0b 00Hope that is of some use ;D
Haven't managed to get flashrom to run ???
Eamon
-
Selected WatchGuard Firebox with SDEC (x86only) - see attached pics.
That was an easy win. Good to see, though. Have you tried the buttons? Best guess, they sort of work, but are not mapped correctly…
-
What happens when you try to run flashrom?
Steve
-
fmertz:
I've tried the buttons, but with the display being so faint, it's hard to see properly. I'll try and have a further play tonight.Steve:
With flashrom I'm getting the error:
/usr/local/bin/flashrom: Exec format error. Binary file not executable.Eamon
-
Ah, that's interesting. Looking back through the boot logs you posted earlier it looks like you were running 64bit, is that still the case?
That explains the wrong binary error.If that is the case:
Remount the filesystem and remove flashrom withpkg_delete flashrom
Then add the correct version
pkg_add -r ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/amd64/packages-8.1-release/Latest/flashrom.tbz
See how that goes, I'm not entirely sure what will happen. You may need to manually remove libpci-3.1.7_1 it may just be overwritten. :-\
Interesting that superiotool worked fine and that the sdeclcd driver worked.
Steve
-
Removed flashrom and libpci-3.1.7_1 but still got the same /usr/local/bin/flashrom: Exec format error. Binary file not executable error.
Just checked and I'm running the nano_vga i386 build ::)
Removed both mentioned above and applied the i386 packages - flashrom now works :)
$ flashrom -V flashrom v0.9.2-r1001 on FreeBSD 8.1-RELEASE-p13 (i386), built with libpci 3.1.7, GCC 4.2.1 20070719 [FreeBSD] flashrom is free software, get the source code at http://www.flashrom.org Initializing internal programmer No coreboot table found. dmidecode execution unsucessfull - continuing without DMI info Found ITE Super I/O, id 8718 Found chipset "Intel ICH9DO", enabling flash write... 0xfff80000/0xffb80000 FWH IDSEL: 0x0 0xfff00000/0xffb00000 FWH IDSEL: 0x0 0xffe80000/0xffa80000 FWH IDSEL: 0x1 0xffe00000/0xffa00000 FWH IDSEL: 0x1 0xffd80000/0xff980000 FWH IDSEL: 0x2 0xffd00000/0xff900000 FWH IDSEL: 0x2 0xffc80000/0xff880000 FWH IDSEL: 0x3 0xffc00000/0xff800000 FWH IDSEL: 0x3 0xff700000/0xff300000 FWH IDSEL: 0x4 0xff600000/0xff200000 FWH IDSEL: 0x5 0xff500000/0xff100000 FWH IDSEL: 0x6 0xff400000/0xff000000 FWH IDSEL: 0x7 0xfff80000/0xffb80000 FWH decode enabled 0xfff00000/0xffb00000 FWH decode enabled 0xffe80000/0xffa80000 FWH decode disabled 0xffe00000/0xffa00000 FWH decode disabled 0xffd80000/0xff980000 FWH decode disabled 0xffd00000/0xff900000 FWH decode disabled 0xffc80000/0xff880000 FWH decode disabled 0xffc00000/0xff800000 FWH decode disabled 0xff700000/0xff300000 FWH decode disabled 0xff600000/0xff200000 FWH decode disabled 0xff500000/0xff100000 FWH decode disabled 0xff400000/0xff000000 FWH decode disabled Maximum FWH chip size: 0x100000 bytes BIOS Lock Enable: disabled, BIOS Write Enable: enabled, BIOS_CNTL is 0x1 Root Complex Register Block address = 0xfed1c000 GCS = 0x464: BIOS Interface Lock-Down: disabled, BOOT BIOS Straps: 0x1 (SPI) Top Swap : not enabled SPIBAR = 0xfed1c000 + 0x3800 0x04: 0x6008 (HSFS) FLOCKDN 0, FDV 1, FDOPSS 1, SCIP 0, BERASE 1, AEL 0, FCERR 0, FDONE 0 0x50: 0x0000ffff (FRAP) BMWAG 0, BMRAG 0, BRWA 255, BRRA 255 0x54: 0x00000000 (FREG0) 0x58: 0x01020003 (FREG1) 0x5C: 0x00000fff (FREG2) 0x60: 0x00020001 (FREG3) 0x64: 0x00000fff (FREG4) 0x74: 0x00000000 (PR0) 0x78: 0x00000000 (PR1) 0x7C: 0x00000000 (PR2) 0x80: 0x00000000 (PR3) 0x84: 0x00000000 (PR4) 0x90: 0x00414004 (SSFS, SSFC) 0x94: 0x5006 (PREOP) 0x96: 0x463b (OPTYPE) 0x98: 0x05d80302 (OPMENU) 0x9C: 0xc79f0190 (OPMENU+4) 0xA0: 0x00000000 (BBAR) 0xB0: 0x00004000 (FDOC) Programming OPCODES... program_opcodes: preop=5006 optype=463b opmenu=05d80302c79f0190 done SPI Read Configuration: prefetching disabled, caching enabled, OK. This chipset supports the following protocols: FWH,SPI. No IT87* serial flash segment enabled. Calibrating delay loop... 1995M loops per second, 10 myus = 11 us, 100 myus = 102 us, 1000 myus = 1002 us, 10000 myus = 10006 us, OK. Probing for AMD Am29F010A/B, 128 KB: skipped. Probing for AMD Am29F002(N)BB, 256 KB: skipped. Probing for AMD Am29F002(N)BT, 256 KB: skipped. Probing for AMD Am29F016D, 2048 KB: skipped. Probing for AMD Am29F040B, 512 KB: skipped. Probing for AMD Am29F080B, 1024 KB: skipped. Probing for AMD Am29LV040B, 512 KB: skipped. Probing for AMD Am29LV081B, 1024 KB: skipped. Probing for ASD AE49F2008, 256 KB: skipped. Probing for Atmel AT25DF021, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT25DF041A, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT25DF081, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT25DF161, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT25DF321, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT25DF321A, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT25DF641, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT25F512B, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT25FS010, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT25FS040, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT26DF041, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT26DF081A, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT26DF161, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT26DF161A, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT26F004, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT29C512, 64 KB: skipped. Probing for Atmel AT29C010A, 128 KB: skipped. Probing for Atmel AT29C020, 256 KB: skipped. Probing for Atmel AT29C040A, 512 KB: skipped. Probing for Atmel AT45CS1282, 16896 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT45DB011D, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT45DB021D, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT45DB041D, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT45DB081D, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT45DB161D, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT45DB321C, 4224 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT45DB321D, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT45DB642D, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Atmel AT49BV512, 64 KB: skipped. Probing for Atmel AT49F002(N), 256 KB: skipped. Probing for Atmel AT49F002(N)T, 256 KB: skipped. Probing for AMIC A25L40PT, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for AMIC A25L40PU, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for AMIC A29002B, 256 KB: skipped. Probing for AMIC A29002T, 256 KB: skipped. Probing for AMIC A29040B, 512 KB: skipped. Probing for AMIC A49LF040A, 512 KB: skipped. Probing for EMST F49B002UA, 256 KB: skipped. Probing for Eon EN25B05, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25B05T, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25B10, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25B10T, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25B20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25B20T, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25B40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25B40T, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25B80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25B80T, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25B16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25B16T, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25B32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25B32T, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25B64, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25B64T, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25D16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25F05, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25F10, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25F20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25F40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25F80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25F16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN25F32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Eon EN29F010, 128 KB: skipped. Probing for EON EN29F002(A)(N)B, 256 KB: skipped. Probing for EON EN29F002(A)(N)T, 256 KB: skipped. Probing for Fujitsu MBM29F004BC, 512 KB: skipped. Probing for Fujitsu MBM29F004TC, 512 KB: skipped. Probing for Fujitsu MBM29F400BC, 512 KB: skipped. Probing for Fujitsu MBM29F400TC, 512 KB: skipped. Probing for Intel 28F001BX-B, 128 KB: skipped. Probing for Intel 28F001BX-T, 128 KB: skipped. Probing for Intel 28F004S5, 512 KB: skipped. Probing for Intel 28F004BV/BE-B, 512 KB: skipped. Probing for Intel 28F004BV/BE-T, 512 KB: skipped. Probing for Intel 28F400BV/CV/CE-B, 512 KB: skipped. Probing for Intel 28F400BV/CV/CE-T, 512 KB: skipped. Probing for Intel 82802AB, 512 KB: probe_82802ab: id1 0x20, id2 0x59, id1 is normal flash content, id2 is normal flash content Probing for Intel 82802AC, 1024 KB: probe_82802ab: id1 0x38, id2 0x30, id1 is normal flash content, id2 is normal flash content Probing for Macronix MX25L512, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Macronix MX25L1005, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Macronix MX25L2005, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Macronix MX25L4005, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Macronix MX25L8005, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Macronix MX25L1605, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Macronix MX25L1635D, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Macronix MX25L3205, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Macronix MX25L3235D, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Macronix MX25L6405, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Macronix MX25L12805, 16384 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Macronix MX29F001B, 128 KB: skipped. Probing for Macronix MX29F001T, 128 KB: skipped. Probing for Macronix MX29F002B, 256 KB: skipped. Probing for Macronix MX29F002T, 256 KB: skipped. Probing for Macronix MX29LV040, 512 KB: skipped. Probing for Numonyx M25PE10, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Numonyx M25PE20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Numonyx M25PE40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Numonyx M25PE80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Numonyx M25PE16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for PMC Pm25LV010, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for PMC Pm25LV016B, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for PMC Pm25LV020, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for PMC Pm25LV040, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for PMC Pm25LV080B, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for PMC Pm25LV512, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for PMC Pm29F002T, 256 KB: skipped. Probing for PMC Pm29F002B, 256 KB: skipped. Probing for PMC Pm39LV010, 128 KB: skipped. Probing for PMC Pm39LV020, 256 KB: skipped. Probing for PMC Pm39LV040, 512 KB: skipped. Probing for PMC Pm49FL002, 256 KB: probe_jedec_common: id1 0x2e, id2 0xc7, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for PMC Pm49FL004, 512 KB: probe_jedec_common: id1 0x20, id2 0x59, id1 is normal flash content, id2 is normal flash content Probing for Sanyo LF25FW203A, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Sharp LHF00L04, 1024 KB: probe_82802ab: id1 0x38, id2 0x30, id1 is normal flash content, id2 is normal flash content Probing for Spansion S25FL008A, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Spansion S25FL016A, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for SST SST25VF016B, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Chip status register is 00 Chip status register: Block Protect Write Disable (BPL) is not set Chip status register: Auto Address Increment Programming (AAI) is not set Chip status register: Bit 5 / Block Protect 3 (BP3) is not set Chip status register: Bit 4 / Block Protect 2 (BP2) is not set Chip status register: Bit 3 / Block Protect 1 (BP1) is not set Chip status register: Bit 2 / Block Protect 0 (BP0) is not set Chip status register: Write Enable Latch (WEL) is not set Chip status register: Write In Progress (WIP/BUSY) is not set Resulting block protection : none Found chip "SST SST25VF016B" (2048 KB, SPI) at physical address 0xffe00000. Probing for SST SST25VF032B, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for SST SST25VF040.REMS, 512 KB: probe_spi_rems: id1 0xbf, id2 0x41 Probing for SST SST25VF040B, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for SST SST25VF040B.REMS, 512 KB: probe_spi_rems: id1 0xbf, id2 0x41 Probing for SST SST25VF080B, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for SST SST28SF040A, 512 KB: skipped. Probing for SST SST29EE010, 128 KB: skipped. Probing for SST SST29LE010, 128 KB: skipped. Probing for SST SST29EE020A, 256 KB: skipped. Probing for SST SST29LE020, 256 KB: skipped. Probing for SST SST39SF512, 64 KB: skipped. Probing for SST SST39SF010A, 128 KB: skipped. Probing for SST SST39SF020A, 256 KB: skipped. Probing for SST SST39SF040, 512 KB: skipped. Probing for SST SST39VF512, 64 KB: skipped. Probing for SST SST39VF010, 128 KB: skipped. Probing for SST SST39VF020, 256 KB: skipped. Probing for SST SST39VF040, 512 KB: skipped. Probing for SST SST39VF080, 1024 KB: skipped. Probing for SST SST49LF002A/B, 256 KB: probe_jedec_common: id1 0x2e, id2 0xc7, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF003A/B, 384 KB: probe_jedec_common: id1 0xbb, id2 0x5d, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004A/B, 512 KB: probe_jedec_common: id1 0x20, id2 0x59, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF004C, 512 KB: probe_82802ab: id1 0x20, id2 0x59, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008A, 1024 KB: probe_jedec_common: id1 0x38, id2 0x30, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF008C, 1024 KB: probe_82802ab: id1 0x38, id2 0x30, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF016C, 2048 KB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for SST SST49LF020, 256 KB: skipped. Probing for SST SST49LF020A, 256 KB: skipped. Probing for SST SST49LF040, 512 KB: skipped. Probing for SST SST49LF040B, 512 KB: skipped. Probing for SST SST49LF080A, 1024 KB: skipped. Probing for SST SST49LF160C, 2048 KB: skipped. Probing for ST M25P05-A, 64 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for ST M25P05.RES, 64 KB: Ignoring RES in favour of RDID. Probing for ST M25P10-A, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for ST M25P10.RES, 128 KB: Ignoring RES in favour of RDID. Probing for ST M25P20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for ST M25P40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for ST M25P40-old, 512 KB: Ignoring RES in favour of RDID. Probing for ST M25P80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for ST M25P16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for ST M25P32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for ST M25P64, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for ST M25P128, 16384 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for ST M29F002B, 256 KB: skipped. Probing for ST M29F002T/NT, 256 KB: skipped. Probing for ST M29F040B, 512 KB: skipped. Probing for ST M29F400BT, 512 KB: skipped. Probing for ST M29W010B, 128 KB: skipped. Probing for ST M29W040B, 512 KB: skipped. Probing for ST M29W512B, 64 KB: skipped. Probing for ST M50FLW040A, 512 KB: probe_82802ab: id1 0x20, id2 0x59, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW040B, 512 KB: probe_82802ab: id1 0x20, id2 0x59, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080A, 1024 KB: probe_82802ab: id1 0x38, id2 0x30, id1 is normal flash content, id2 is normal flash content Probing for ST M50FLW080B, 1024 KB: probe_82802ab: id1 0x38, id2 0x30, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW002, 256 KB: probe_82802ab: id1 0x2e, id2 0xc7, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW016, 2048 KB: Chip size 2048 kB is bigger than supported size 1024 kB of chipset/board/programmer for FWH interface, probe/read/erase/write may fail. probe_82802ab: id1 0xff, id2 0xff, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW040, 512 KB: probe_82802ab: id1 0x20, id2 0x59, id1 is normal flash content, id2 is normal flash content Probing for ST M50FW080, 1024 KB: probe_82802ab: id1 0x38, id2 0x30, id1 is normal flash content, id2 is normal flash content Probing for ST M50LPW116, 2048 KB: skipped. Probing for SyncMOS S29C31004T, 512 KB: skipped. Probing for SyncMOS S29C51001T, 128 KB: skipped. Probing for SyncMOS S29C51002T, 256 KB: skipped. Probing for SyncMOS S29C51004T, 512 KB: skipped. Probing for TI TMS29F002RB, 256 KB: skipped. Probing for TI TMS29F002RT, 256 KB: skipped. Probing for Winbond W25Q80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Winbond W25Q16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Winbond W25Q32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Winbond W25x10, 128 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Winbond W25x20, 256 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Winbond W25x40, 512 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Winbond W25x80, 1024 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Winbond W25x16, 2048 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Winbond W25x32, 4096 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Winbond W25x64, 8192 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Winbond W29C011, 128 KB: skipped. Probing for Winbond W29C020C, 256 KB: skipped. Probing for Winbond W29C040P, 512 KB: skipped. Probing for Winbond W29EE011, 128 KB: skipped. Probing for Winbond W39V040A, 512 KB: skipped. Probing for Winbond W39V040B, 512 KB: skipped. Probing for Winbond W39V040C, 512 KB: skipped. Probing for Winbond W39V040FA, 512 KB: probe_jedec_common: id1 0x20, id2 0x59, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080A, 1024 KB: skipped. Probing for Winbond W49F002U, 256 KB: skipped. Probing for Winbond W49V002A, 256 KB: skipped. Probing for Winbond W49V002FA, 256 KB: probe_jedec_common: id1 0x2e, id2 0xc7, id1 parity violation, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA, 1024 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0x38, id2 0x30, id1 is normal flash content, id2 is normal flash content Probing for Winbond W39V080FA (dual mode), 512 KB: Chip lacks correct probe timing information, using default 10mS/40uS. probe_jedec_common: id1 0x20, id2 0x59, id1 is normal flash content, id2 is normal flash content Probing for Atmel unknown Atmel SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for EON unknown EON SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Macronix unknown Macronix SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for PMC unknown PMC SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for SST unknown SST SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for ST unknown ST SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Sanyo unknown Sanyo SPI chip, 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Generic unknown SPI chip (RDID), 0 KB: probe_spi_rdid_generic: id1 0xbf, id2 0x2541 Probing for Generic unknown SPI chip (REMS), 0 KB: probe_spi_rems: id1 0xbf, id2 0x41 ===
Eamon