Secondary store

> > I think i could, in theory. ;-)  With three devices connected, the Wifi server proc (hostapd) never get much more than 1% usage.  So, it could support at least 100 devices.  Perhaps someday, i'll try it and see how many can connect to it in public.
> 
> I suspect the wifi from the little patch antenna mounted in the screen might not do so well in terms of signal strength compared to something with an external antenna.

To cover a large area, we would need external USB adapters with antenna anyway.  They are less than $10 ea.  We would also need to use multiple channels.

> 
> > The argument against using PC/laptops vs. COT routers has been price and power consumption.  These old netbooks can beat/match COT routers with around $50 and 5W.
> 
> Bit tricky to nail a netbook to the wall.  And the 'locals' may take an unhealthy interest when they see a 'free' laptop.  Like I said, this was a 'hostile' environment.  Did I mention ambient temperatures of 50degC? That's where power consumption really bites, because cooling just isn't there.

It could be hidden in a box mounted up in wall, tree or post, as long as there is some power (even solar could work).  Or it could be mounted inside a car, with the webcam "seeing" passing-by as well.  With the LCD screen and hard drive off, the netbook and power plug are cool to the touch.  I think it draws less than 5W average.

Hi Andrew,

On 8/28/2014 8:50 PM, Andrew Smallshaw wrote:

>> BTW, do you know if the DVI+HD15 CA10's can run dual headed?  Or,
>> is the DVI connector just a "convenience" for folks with monitors
>> without HD15's?
>
>  From memory that'll be a VIA Chrome chip in which case no.  At
> least that's the way it was with the VIA EPIA boards of that era
> which seem to be a productised reference design, in that there's
> a 1:1 equivalence in support chips between the Neoware mainboards
> and the equivalent EPIA.  It's a little more than mere convenience
> in that it does generate a digital out, but the displays are clones
> of each other right down to signal timing.

Hmmm... dmesg of a kernel I built for the box with the disk drive
(not the T5530 that was the original subject of this thread but a
CA10) -- linewrap unavoidable (blame the driver authors! :> ):

NetBSD 3.1 (BASTION) #1: Wed Aug 27 16:11:02 MST 2014
	toor@Bastion.XXXX.XXX:/usr/src/sys/arch/i386/compile/BASTION
total memory = 1015 MB
avail memory = 989 MB
BIOS32 rev. 0 found at 0xfb3a0
PCI BIOS rev. 2.1 found at 0xfb3f0
pcibios: config mechanism [1][x], special cycles [1][x], last bus 3
PCI IRQ Routing Table rev. 1.0 found at 0xfdf00, size 128 bytes (6 entries)
PCI Interrupt Router at 000:17:0 (VIA Technologies VT82C596A PCI-ISA 
Bridge compatible)
PCI Exclusive IRQs: 5 11 12 15
mainbus0 (root)
cpu0 at mainbus0: (uniprocessor)
cpu0: VIA C3 Nehemiah (686-class), 1000.48 MHz, id 0x698
cpu0: features 381b03f<FPU,VME,DE,PSE,TSC,MSR,MTRR>
cpu0: features 381b03f<PGE,CMOV,PAT,MMX>
cpu0: features 381b03f<FXSR,SSE>
cpu0: "VIA Nehemiah"
cpu0: I-cache 64 KB 32B/line 2-way, D-cache 64 KB 32B/line 2-way
cpu0: L2 cache 64 KB 32B/line 8-way
cpu0: ITLB 128 4 KB entries 8-way
cpu0: DTLB 128 4 KB entries 8-way
cpu0: 8 page colors
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pchb0 at pci0 dev 0 function 0
pchb0: VIA Technologies VT8623 (Apollo CLE266) CPU-PCI Bridge (rev. 0x00)
agp0 at pchb0: aperture at 0xe4000000, size 0x10000000
ppb0 at pci0 dev 1 function 0: VIA Technologies VT8633 (Apollo Pro 266) 
CPU-AGP Bridge (rev. 0x00)
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled
vga0 at pci1 dev 0 function 0: VIA Technologies VT8623 (Apollo CLE266) 
VGA Controller (rev. 0x03)
wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation)
wsmux1: connecting to wsdisplay0
wsdisplay0: screen 1-3 added (80x25, vt100 emulation)
ppb1 at pci0 dev 8 function 0: Intel S21152BB PCI-PCI Bridge (rev. 0x00)
pci2 at ppb1 bus 2
pci2: i/o space, memory space enabled, rd/line, wr/inv ok
fxp0 at pci2 dev 0 function 0: i82550 Ethernet, rev 16
fxp0: interrupting at irq 15
fxp0: May need receiver lock-up workaround
fxp0: Ethernet address 00:00:50:0f:0e:1b
ukphy0 at fxp0 phy 1: Generic IEEE 802.3u media interface
ukphy0: i82555 10/100 media interface (OUI 0x005500, model 0x0015), rev. 4
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1 at pci2 dev 1 function 0: i82550 Ethernet, rev 16
fxp1: interrupting at irq 11
fxp1: May need receiver lock-up workaround
fxp1: Ethernet address 00:00:50:0f:0e:1c
ukphy1 at fxp1 phy 1: Generic IEEE 802.3u media interface
ukphy1: i82555 10/100 media interface (OUI 0x005500, model 0x0015), rev. 4
ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp2 at pci2 dev 2 function 0: i82550 Ethernet, rev 16
fxp2: interrupting at irq 5
fxp2: May need receiver lock-up workaround
fxp2: Ethernet address 00:00:50:0f:0e:1d
ukphy2 at fxp2 phy 1: Generic IEEE 802.3u media interface
ukphy2: i82555 10/100 media interface (OUI 0x005500, model 0x0015), rev. 4
ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp3 at pci2 dev 3 function 0: i82550 Ethernet, rev 16
fxp3: interrupting at irq 12
fxp3: May need receiver lock-up workaround
fxp3: Ethernet address 00:00:50:0f:0e:1e
ukphy3 at fxp3 phy 1: Generic IEEE 802.3u media interface
ukphy3: i82555 10/100 media interface (OUI 0x005500, model 0x0015), rev. 4
ukphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
cbb0 at pci0 dev 9 function 0: Texas Instruments PCI1510 PCI-CardBus 
Bridge (rev. 0x00)
uhci0 at pci0 dev 16 function 0: VIA Technologies VT83C572 USB 
Controller (rev. 0x80)
uhci0: interrupting at irq 15
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: VIA Technologies UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 16 function 1: VIA Technologies VT83C572 USB 
Controller (rev. 0x80)
uhci1: interrupting at irq 11
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: VIA Technologies UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2 at pci0 dev 16 function 2: VIA Technologies VT83C572 USB 
Controller (rev. 0x80)
uhci2: interrupting at irq 5
usb2 at uhci2: USB revision 1.0
uhub2 at usb2
uhub2: VIA Technologies UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
ehci0 at pci0 dev 16 function 3: VIA Technologies VT8237 EHCI USB 
Controller (rev. 0x82)
ehci0: interrupting at irq 12
ehci0: BIOS has given up ownership
ehci0: EHCI version 1.0
ehci0: companion controllers, 2 ports each: uhci0 uhci1 uhci2
usb3 at ehci0: USB revision 2.0
uhub3 at usb3
uhub3: VIA Technologie EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub3: single transaction translator
uhub3: 6 ports with 6 removable, self powered
pcib0 at pci0 dev 17 function 0
pcib0: VIA Technologies VT8235 (Apollo KT400) PCI-ISA Bridge (rev. 0x00)
viaide0 at pci0 dev 17 function 1
viaide0: VIA Technologies VT8235 ATA133 controller
viaide0: bus-master DMA support present
viaide0: primary channel configured to compatibility mode
viaide0: primary channel interrupting at irq 14
atabus0 at viaide0 channel 0
viaide0: secondary channel configured to compatibility mode
viaide0: secondary channel ignored (disabled)
auvia0 at pci0 dev 17 function 5: VIA Technologies VT8235 AC'97 Audio 
(rev 0x50)
auvia0: interrupting at irq 5
auvia0: ac97: VIA Technologies VT1612A codec; headphone, 18 bit DAC, 18 
bit ADC, KS Waves 3D
auvia0: ac97: ext id 201<AMAP,VRA>
audio0 at auvia0: full duplex, mmap, independent
vr0 at pci0 dev 18 function 0: VIA VT6102 (Rhine II) 10/100 Ethernet
vr0: interrupting at irq 15
vr0: Ethernet address: 00:e0:c5:59:27:98
ukphy4 at vr0 phy 1: Generic IEEE 802.3u media interface
ukphy4: OUI 0x0002c6, model 0x0032, rev. 8
ukphy4: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
cbb0: interrupting at irq 15
cardslot0 at cbb0 slot 0 flags 0
cardbus0 at cardslot0: bus 3 device 0
pcmcia0 at cardslot0
isa0 at pcib0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
pckbc0 at isa0 port 0x60-0x64
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
mpu0 at isa0 port 0x330-0x331 irq 9
midi0 at mpu0: Roland MPU-401 MIDI UART
joy0 at isa0 port 0x201
joy0: joystick not connected
pcppi0 at isa0 port 0x61
midi1 at pcppi0: PC speaker
spkr0 at pcppi0
sysbeep0 at pcppi0
isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
npx0 at isa0 port 0xf0-0xff: using exception 16
isapnp0: no ISA Plug 'n Play devices found
apm0 at mainbus0: Power Management spec V1.2
apm0: A/C state: on
apm0: battery charge state: no battery
Kernelized RAIDframe activated
wd0 at atabus0 drive 0: <TOSHIBA MK1031GAS>
wd0: drive supports 16-sector PIO transfers, LBA addressing
wd0: 95396 MB, 193821 cyl, 16 head, 63 sec, 512 bytes/sect x 195371568 
sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
wd0(viaide0:0:0): using PIO mode 4, Ultra-DMA mode 5 (Ultra/100) (using DMA)
boot device: wd0
root on wd0a dumps on wd0b
root file system type: ffs
wsdisplay0: screen 4 added (80x25, vt100 emulation)
Accounting started

[N.B. fxp* are an add-on card; all other devices are native]

Note "VIA Technologies VT8623 (Apollo CLE266)".  From some quick
doc checks, it looks like this supports dual monitors with two
independent contents, refresh rates and resolutions (in practice,
I run identical monitors so rates and resolutions can remain the
same).

I'll have to see if the X server will support Xinerama on this
chipset or if I will have to treat them as two different (logical)
display devices (i.e., :0 and :1).

> I'll reply to your other post tomorrow, it's getting pretty late
> here now.

Gee, pretty *early*, here!  :>

--don