On Hand, Patriot PCUSB3EXP (NEC PCIE-XHCI) expresscard usb3 adapter.
All: I got this for my Lenovo S10 to support the USB CD-RW drive I got, as a closer USB Power adapter (Which does not work at this time BTW...) tech@ question: If there is someone looking at XHCI already, Please let me know, I looked in FreeBSD and found some XHCI work beginning (last month) and might take a peek at that, but so far I've been wildly unsuccessful in making any USB type thingies work when I add them... http://www.listware.net/201008/freebsd-arm/23458-beta-testing-usb-30-super-sp eed-support-in-freebsd.html If someone wants one of these for OpenBSD development, I can get one and Mail it to You, please contact me offlist. dmesg and pcidump follows: dmesg: OpenBSD 4.7-stable (GENERIC.MP) #3: Fri Aug 13 15:54:35 EDT 2010 ***...@lenovoju:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (GenuineIntel 686-class) 1.60 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,A CPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,xTPR real mem = 2137419776 (2038MB) avail mem = 2062225408 (1966MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 06/29/09, BIOS32 rev. 0 @ 0xfdc40, SMBIOS rev. 2.5 @ 0xdf010 (24 entries) bios0: vendor LENOVO version 14CN94WW date 06/29/2009 bios0: LENOVO Lenovo acpi0 at bios0: rev 2 acpi0: tables DSDT FACP HPET MCFG TCPA TMOR APIC BOOT ASF! SSDT SSDT SSDT acpi0: wakeup devices HDEF(S4) PXS1(S4) PXS2(S4) PXS3(S4) USB1(S4) USB2(S4) USB3(S4) USB4(S4) USB7(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 132MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (GenuineIntel 686-class) 1.60 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,A CPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,xTPR ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus 3 (RP02) acpiprt3 at acpi0: bus 5 (RP03) acpiprt4 at acpi0: bus 6 (PCIB) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpitz0 at acpi0: critical temperature 86 degC acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: SLPB acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model LE30_S serial type LION oem Sanyo acpibtn2 at acpi0: LID_ acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: DD01 acpivout1 at acpivideo0: DD02 acpivout2 at acpivideo0: DD03 acpivout3 at acpivideo0: DD04 bios0: ROM list: 0xc/0xec00! 0xcf000/0x1e00 0xdf000/0x800! 0xe/0x1800! cpu0: Enhanced SpeedStep 1596 MHz: speeds: 1600, 1333, 1067, 800 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82945GME Host rev 0x03 vga1 at pci0 dev 2 function 0 Intel 82945GME Video rev 0x03 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1: apic 2 int 16 (irq 11) drm0 at inteldrm0 Intel 82945GM Video rev 0x03 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02: apic 2 int 22 (irq 5) azalia0: codecs: Realtek ALC269 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: apic 2 int 17 (irq 3) pci1 at ppb0 bus 2 bge0 at pci1 dev 0 function 0 Broadcom BCM5906M rev 0x02, BCM5906 A2 (0xc002): apic 2 int 16 (irq 11), address **removed** brgphy0 at bge0 phy 1: BCM5906 10/100baseTX PHY, rev. 0 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: apic 2 int 16 (irq 11) pci2 at ppb1 bus 3 NEC PCIE-XHCI rev 0x03 at pci2 dev 0 function 0 not configured ppb2 at pci0 dev 28 function 2 Intel 82801GB PCIE rev 0x02: apic 2 int 18 (irq 3) pci3 at ppb2 bus 5 Broadcom BCM4315 rev 0x01 at pci3 dev 0 function 0 not configured uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x02: apic 2 int 23 (irq 5) uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x02: apic 2 int 19 (irq 10) uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x02: apic 2 int 18 (irq 3) uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x02: apic 2 int 16 (irq 11) ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x02: apic 2 int 23 (irq 5) usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb3 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0xe2 pci4 at ppb3 bus 6 ichpcib0 at pci0 dev 31 function 0 Intel 82801GBM LPC rev 0x02: PM disabled pciide0 at pci0 dev 31 function 1 Intel 82801GB IDE rev 0x02: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility pciide0: channel 0 disabled (no drives) pciide0: channel 1
Re: defining ports LOCKDIR
Marc, Everyone. I say /tmp This; if anything, is what makes OpenBSD - Unix -. The correct usage of /tmp /etc/daily I strongly urge be fixed. -sean Date: Wed, 16 Jun 2010 17:17:40 +0200 From: es...@nerim.net To: tech@openbsd.org Subject: Re: defining ports LOCKDIR I should have been more specific. This is not a vote as to where we should put the default. If you think of the constraints (usually not NFS, user-writable), there are about two locations that make sense: /tmp or /var/tmp. Also remember that it makes no sense for those locks to survive reboot. So /tmp is the only location that makes sense. Remember that it is a default. Stuart's remark wrt /etc/daily is good, but /etc/daily can be fixed. What do you say ? default, or not default ? A computer without COBOL and FORTRAN is like a piece of chocolate cake without ketchup or mustard. unix fortune cookie. _ Look 'em in the eye: FREE Messenger video chat http://go.microsoft.com/?linkid=9734386
Re: PF FAQ example ruleset
pf.conf and typical workstation settings aside, I am wondering about PF FAQ
and 'Some examples.
Really a pf.conf for what I use DD-WRT for running on a linksys. (as compared
to default Linksys Firmware)
(outside world)--[OpenBSD box{PF, dhcpd, services}]--({NAT}wired/wireless
lan)--[PSP, PS3, WinCE, and/or computers]
A good pf.conf example ruleset just to do this, would meet most if not all
basic needs; Need to do more, read the man page...
Wired and Wireless dhcpd config's are straightforward, as are services like
CUPS, SSHd, and FTPd.
Mostly this saves on component count since I use the same OpenBSD box as a
Windows Netbook terminal, and I don't have to lug +5 pieces of gear to get a
network of my own.
For PSP's and PS3's and other devices Like Windows CE, running 802.11bgn
wireless, in my own WLAN space saves me re-running a setup for the wireless
connection every time I goto another hotel...
Further I can run a Branch Office in a Box If I added the requisite VPN
parts, but thats outside the scope of Basic NAT micronetting here.
Note: I did not want to send a DIFF since these are Examples for the PF FAQ,
and not updates for -release.
FWIW, these three examples are what I use for the outside world wired, and
WLAN NAT-Net behind PF.
bge0 is dhclient ext_if, ural0 is dhcpd int_if. This is not the latest
pf.conf from etc47, but updated for the Match Rule.
pf.conf
#$OpenBSD: pf.conf,v 1.44 2009/06/10 15:29:34 sobrado Exp $
#
# See pf.conf(5) for syntax and examples; this sample ruleset uses
# require-order to permit mixing of NAT/RDR and filter rules.
# Remember to set net.inet.ip.forwarding=1 and/or net.inet6.ip6.forwarding=1
# in /etc/sysctl.conf if packets are to be forwarded between interfaces.
#set skip on lo
#ext_if=fxp0 #used on HP SFF Desktop in road-case, Lenovo PinkPad S10
uses bge0 for wired.
#ext_if=ural0#for reversed wireless to wired NAT lan. Change
hostname.ural0 to a dhcp-client version.
ext_if=bge0
#int_if=bge0 #for reversed wireless to wired NAT lan. Change
hostname.bge0 to the dhcpd wired version.
int_if=ural0
# NAT/filter rules and anchors for ftp-proxy(8)
#nat-anchor ftp-proxy/*
#rdr-anchor ftp-proxy/*
#rdr pass on ! egress proto tcp to port ftp - 127.0.0.1 port 8021
#anchor ftp-proxy/*
#pass out proto tcp from $proxy to any port ftp
# NAT/filter rules and anchors for relayd(8)
#rdr-anchor relayd/*
#anchor relayd/*
#nat on $ext_if from !($ext_if) - ($ext_if:0) ### 4.6 old, does not work in
4.7 see below ###
match out on $ext_if from !($ext_if) nat-to ($ext_if:0)
# NAT rules and anchors for spamd(8)
#table spamd-white persist
#table nospamd persist file /etc/mail/nospamd
#no rdr on egress proto tcp from nospamd to any port smtp
#no rdr on egress proto tcp from spamd-white to any port smtp
#rdr pass on egress proto tcp from any to any port smtp - 127.0.0.1 port
spamd
pass out# to establish keep-state
#block in quick from urpf-failed to any# use with care
# By default, do not permit remote connections to X11
block in on ! lo0 proto tcp to port 6000:6010
pass quick on $int_if no state
antispoof quick for { lo $int_if }
pass in on $ext_if proto icmp to ($ext_if)
pass in on $ext_if proto tcp to ($ext_if) port ssh
pf.conf
hostname.ural0 __
!ifconfig ural0 down
!ifconfig ural0 nwkey 0xC0FFEE0DEADBEEF0CAB1BADA55
!ifconfig ural0 mediaopt hostap nwid 1020wlanmyopenbsd3040 chan 6
!ifconfig ural0 10.16.1.1 netmask 255.255.255.0
#!ifconfig ural0 up
hostname.ural0 __
dhcpd.conf
#$OpenBSD: dhcpd.conf,v 1.2 2008/10/03 11:41:21 sthen Exp $
#
# DHCP server options.
# See dhcpd.conf(5) and dhcpd(8) for more information.
#
# Network:192.168.1.0/255.255.255.0
# Domain name:my.domain
# Name servers:192.168.1.3 and 192.168.1.5
# Default router:192.168.1.1
# Addresses:192.168.1.32 - 192.168.1.127
#
option domain-name dfg.org;
# DFG.ORG Office
option domain-name-servers 192.168.125.1;
# Marriot Hotel Internet
#option domain-name-servers 4.2.2.1;
subnet 10.16.1.0 netmask 255.255.255.0 {
option routers 10.16.1.1;
range 10.16.1.32 10.16.1.42;
host static-client {
#hardware ethernet 22:33:44:55:66:77;
#fixed-address 0.1.2.3;
}
host handheld-one {
hardware ethernet 00:a0:35:28:40:0f;
fixed-address 10.16.1.200;
option host-name wince-hh-one;
}
host handheld-two {
hardware ethernet 00:a0:35:28:40:0b;
fixed-address 10.16.1.202;
option host-name wince-hh-two;
}
host pxe-client {
hardware ethernet 02:03:04:05:06:07;
filename pxeboot;
next-server 10.16.1.1;
}
}
dhcpd.conf
These are just examples, but they work for me.
---
Subject: Re: PF FAQ example ruleset
Bump!
The more examples the better, as
Re: disklabel - 'P' option
Meh, nothing like being an Inconsistent mad typist. . . (I did learn on a Manual Typewriter... It was a Green Terminal, it worked even if the power was out...) I'd give a Yay to this variant. ( an Even Bigger Yay now it does 'p m' even... ) -sean Date: Thu, 8 Apr 2010 10:03:27 +0200 Subject: Re: disklabel - 'P' option 'megabyte-able' printing more consistent to my liking. Attached is an amended diff that allows the 'P' option to take an argument just as the 'p' option does. That is the crux of the issue. For those of us who like to type less this diff helps, for you people who like type more... you're weird ;) Anyway, with only one yay, I don't think this will progress much further. I like this too, fwiw. Landry _ Hotmail Messenger are available on your phone. Try now. http://go.microsoft.com/?linkid=9724461
Re: disklabel - 'P' option
When I use Disklabel, I have been in the habit of issuing 'p m enter' rather than just 'p enter' Since I do it for disk / usb thumb setups, and so forth, I find the 'megabyte-able' printing more consistent to my liking. I'd say leave it out, since CHS information may get scrolled off the screen if it was relevant. (Or am I thinking fdisk...?) As it is, both 'p' and 'm' keys have less wear than 'e' 't' and 's' and make for good finger dexterity... -sean Date: Wed, 7 Apr 2010 13:41:25 +0100 Subject: Re: disklabel - 'P' option On 2010/04/07 11:21, Mark Lumsden wrote: I press 'p' then enter after everything I do in disklabel. 'P' automatically prints out the equivalent of 'p' after each command and saves on finger wear and tear. like/dislike? hmm..not sure. I might find it useful if it allowed setting the unit too, but I doubt I'd remember it exists when actually using disklabel. _ Live connected. Get Hotmail Messenger on your phone. http://go.microsoft.com/?linkid=9724462
Read_Write buffers for dd WAS: little cp diff
Moving this to m...@... Would part of this discussion usefully related to such issues like using 'dd' for diskwipes/copies/reformatting and slow data movement speeds? There are times when I am wiping (for reuse) hard disks using 'dd' and I set the BlockSize to 512 (like 1M or so sometimes) and the transfer speeds are quite a lot slower than for using 'dd' on some other Operating systems. (Linux or Windows) Mind you, for a lot of this, I am using oBSD RamDISK, so I am not anticipating a full-fledged OS support for the ATA or SCSI or USB2 platforms. But for those systems where I am using -stable or -current, the speeds are still comparably slow. I concur with Theo's point on portability and making a sysctl for kernel is hazardous, but what am I seeing in the above for 'dd' that would be causing the poor performance? (* BTW, I am using if=/dev/zero for the baseline, other if=/...'es may have lower performance as an input for compare*) Just my 2 cents. -sean Subject: Re: little cp diff 2010/2/8 Theo de Raadt dera...@cvs.openbsd.org: For those of you who asked why cp needs to be portable, come on. You've got it all wrong. If cp isn't written in a portable fashion, then what is the point of doing anything else in a portable fashion. This is good and reasonable answer. So I think we should stop discussion. antonvm _
Re: UBC? And a Mr. Allen
FWIW, Hey, I have been to the RTFM side, as well as asking if YXZ feature is looked into But I see the response to Mr. Allen's RFC (See Initial Posting) appropriate. Including the initial inside humour. In fact, it did spawn a related set of tests where the differences between amd64, and i386 are different (it appeared to me at least) in the mechanisms used for allocations. I benefited from the result of the RFC if in fact I considered the response to the Initial Comment Request - appropriate. Oh, and Mr. Allen. Since it was a bussword RFC you posted, and your lack of comprehension and sensitivity to the response. I (Personally) would prefer if you used a Operating System running on x86 platforms that you decide (if you comprehend it) which licensing solution you can afford. Grow Up, code, hack, and be Free if you want to, but I politely invite you to not Whine on and on about your sensitivities. -- I like my Cheese with a bottle of Merlot, not with a sandwich and Baloney and an ASR38. (grumble) ^G -- DING! Oh Wait, Leave out the ASR38 I need that for the wide listings... -sean Date: Tue, 2 Feb 2010 02:51:52 + From: jake...@sdf.lonestar.org To: tech@openbsd.org Subject: Re: UBC? On Mon, Feb 01, 2010 at 03:28:22PM -0700, Darrin Chandler wrote: On Mon, Feb 01, 2010 at 03:05:37PM -0700, Nick Bender wrote: On Mon, Feb 1, 2010 at 2:46 PM, Bob Beck b...@ualberta.ca wrote: On 1 February 2010 14:09, Donald Allen donaldcal...@gmail.com wrote: I have not responded to this thread because I was angered by it and did not want to respond in anger. That has passed. But this thread is unfortunately all too typical of a pattern of ridicule and downright nastiness that occurs much too often on the OpenBSD lists. Well I certainly didn't get that impression from this thread, Sorry you did.. Happy Trails. Ditto. Thought this thread was fairly productive: - question raised - clarification sought - clarification provided - solution given - bug found - patch proposed and debated You could enforce minimum levels of civility, as many such communities do, without impeding the flow of technical information a it, but you choose not to. Civility is in the eye of the moderator. I prefer my debate unfiltered... There was some belittling of Allen for asking about UBC. I don't think it added anything. Not even humor. Beck's initial response was a good one, clarifying and offering something to try, but at least one person jumped in with unhelpful comments. There were also informative and interesting replies, and in fact these made of the bulk of the thread. While this thread was relatively mild compared to some I think Allen has a point. There's just no need to escalate what should have been a purely technical discussion into an ad hominem attack. are you talking about Bret's reply about buzzwords? imo, that's what that reply was about, buzzwords. there was nothing personal. see, the way buzzwords work, is they get stuck in your (as in most people) head, then they come out when you have a idea but don't know quite how to express it. which is clearly the situation here. I think readers of OpenBSD lists are far too sensitive. there, that's a personal 'attack' on all y'all. -- jake...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org _ Check your Hotmail from your phone. http://go.microsoft.com/?linkid=9708121
Re: Improved Build Process
Hi David. As a person who has worked with the OpenBSD process for easily 12+ years, and longer with a Variety of other platforms; a Wholesale Change such as you are recommending is going to be negatively looked at. Not that what You are typing about is not possible; In fact having a Slice for the /usr/obj folder makes for faster turnaround when doing sysgens. I my case I have to re-read existing documentation once in a while to keep up-to-date on -even- maintaining -stable or -current... And OpenBSD is pretty simple. But the scope of what you are considering / suggesting is a bit much. One of the firstfold reasons that OpenBSD has become a Unix that I appreciate, is due to the diligence of the development principals in using ASAP rules (As Simple As Possible) since this establishes two things: Clarity and Correctness. As for /usr/ports well, thats because we live in an Open Source and Free World. If something needs improvement, sit-down, code, and pay it forward by sending info to the Principals of the Port in Question. Being new to anything is not an excuse, it means you need to sit down and read the manuals, ask some misc@ questions, and when you feel there is something to contribute -- contribute. Its a Shut-Up and Hack thing, not a How We All can make -this- Unix-Based Operating System look like the SuSE build for s390. -sean Subject: Improved Build Process I am somewhat new to OpenBSD but not systems and/or systems programming as a whole. Please excuse any errors Thanks for reading this. I hope it is considered valuable. _ Windows Live: Keep your friends up to date with what you do online. http://go.microsoft.com/?linkid=9691815
Re: too many cpus
Subject: Re: too many cpus 2009/12/9 Theo de Raadt dera...@cvs.openbsd.org: Being different just to be different is also pretty silly. So unless there is a good reason not to choose '1' for this purpose, I'd love to see a new diff from Ted. Being the same is a burden. You should go read the original top source code. making the key the same when we have a chance to is not a burden. Somebody forgot to provide much needed beer for the one (of many) nights that Theo spent reading Al Cahalan's re-write...(and others, but I don't have beer either.) top(1) and ps(1) have a long history. And not to mention Baggage... But having some consistency would be good. It bugs me when I shift from SYSV to oBSD and type 'ps-ef'. _ Eligible CDN College University students can upgrade to Windows 7 before Jan 3 for only $39.99. Upgrade now! http://go.microsoft.com/?linkid=9691819
