Re: nat-to private address
On 06/26/2014 04:09 AM, Tuyosi Takesima wrote: hi,all. I tried in various ways, but I can not do 'nat-to private address'. I think that nat-to global address is OK but nat-to private address is NO . Is there another way (for example rdr, rdr-to) ? I myself can't do . sorry for poor english. That depends on what you want to achieve. sometimes you just need a route to the right destination pointing to the right interface. -- With best regards, Gregory Edigarov
Re: nat-to private address
thanks for your advise I write down more detail . IN case of Debian , regardless security internet | router 192:168.0.1 | 192.168.0.x debian firewall :udhcpdiptables 192.168.11.1 |iptables -t nat -P PREROUTING ACCEPT |iptables -t nat -P POSTROUTING ACCEPT | | | 192.168.11.y linux puppy puppy can access intenet by debian's iptables(like pf). I want to do same thing by openbsd . But nat-to is forbidden to private address. It is embarassing .
Re: nat-to private address
On Thu, Jun 26, 2014 at 07:00:22PM +0900, Tuyosi Takesima wrote: thanks for your advise I write down more detail . IN case of Debian , regardless security internet | router 192:168.0.1 | 192.168.0.x debian firewall :udhcpdiptables 192.168.11.1 |iptables -t nat -P PREROUTING ACCEPT |iptables -t nat -P POSTROUTING ACCEPT | | | 192.168.11.y linux puppy puppy can access intenet by debian's iptables(like pf). I want to do same thing by openbsd . But nat-to is forbidden to private address. It is embarassing . Your conlusion is wrong. OpenBSD can do nat to any adress, if it is available on the interface.
Re: nat-to private address
I pick -- # match rules match out on egress inet from !(egress:network) to any nat-to (egress:0) --- from http://www.openbsd.org/faq/pf/example1.html But, this match rules don't work . accordin to man pf.conf 10.0.0.0 - 10.255.255.255 (all of net 10, i.e. 10/8) 172.16.0.0 - 172.31.255.255 (i.e. 172.16/12) 192.168.0.0 - 192.168.255.255 (i.e. 192.168/16) nat-to is usually applied outbound. If applied inbound, nat-to to a local IP address is not supported.
Re: kernel panic from sys/dev/acpi/dsdt.c rev1.210 change
Works now with the latest snapshot (dsdt.c rev. 1.211), thanks!
Re: nat-to private address
On Thu, Jun 26, 2014 at 07:34:05PM +0900, Tuyosi Takesima wrote: I pick -- # match rules match out on egress inet from !(egress:network) to any nat-to (egress:0) --- from http://www.openbsd.org/faq/pf/example1.html But, this match rules don't work . accordin to man pf.conf 10.0.0.0 - 10.255.255.255 (all of net 10, i.e. 10/8) 172.16.0.0 - 172.31.255.255 (i.e. 172.16/12) 192.168.0.0 - 192.168.255.255 (i.e. 192.168/16) nat-to is usually applied outbound. If applied inbound, nat-to to a local IP address is not supported. In general, nat-to is used for outbound, rdr-to for inbound. I don't understand what you are trying to achieve. I suggest you study the FAQ. http://www.openbsd.org/faq/pf/config.html -Otto
Re: nat-to private address
On Thu, Jun 26, 2014 at 07:34:05PM +0900, Tuyosi Takesima wrote: I pick -- # match rules match out on egress inet from !(egress:network) to any nat-to (egress:0) --- from http://www.openbsd.org/faq/pf/example1.html But, this match rules don't work . Is the interface you're NATing to on the egress group? What if you replace 'egress' with the appropriate interface's name? accordin to man pf.conf 10.0.0.0 - 10.255.255.255 (all of net 10, i.e. 10/8) 172.16.0.0 - 172.31.255.255 (i.e. 172.16/12) 192.168.0.0 - 192.168.255.255 (i.e. 192.168/16) nat-to is usually applied outbound. If applied inbound, nat-to to a local IP address is not supported. I think you are misinterpreting things. If I understand correctly, in you case 'outbound' means 'from 192.168.11.x to anywhere', whereas 'inbound' would be 'from anywhere to 192.168.11.y'. So you _do_ want to NAT outbound traffic, and OpenBSD does that just fine. --
Re: nat-to private address
On 2014-06-26, Tuyosi Takesima nakajin.fu...@gmail.com wrote: I pick -- # match rules match out on egress inet from !(egress:network) to any nat-to (egress:0) --- from http://www.openbsd.org/faq/pf/example1.html But, this match rules don't work . accordin to man pf.conf 10.0.0.0 - 10.255.255.255 (all of net 10, i.e. 10/8) 172.16.0.0 - 172.31.255.255 (i.e. 172.16/12) 192.168.0.0 - 192.168.255.255 (i.e. 192.168/16) nat-to is usually applied outbound. If applied inbound, nat-to to a local IP address is not supported. applied outbound means a rule using match out applied inbound means a rule using match in So this does not apply to you anyway because your nat-to rule is applied outbound. local IP address means an IP address on the machine running PF If you show output pfctl -sr and ifconfig -A and sysctl net.inet.ip.forwarding we may be able to help further.
Re: nat-to private address
On Thu, Jun 26, 2014 at 12:14:42PM +0300, Gregory Edigarov wrote: On 06/26/2014 04:09 AM, Tuyosi Takesima wrote: I tried in various ways, but I can not do 'nat-to private address'. I think that nat-to global address is OK but nat-to private address is NO . Did you enable IP forwarding? What's the output of: # sysctl net.inet.ip.forwarding
Re: nat-to private address
Hello Tuyosi, Thursday, June 26, 2014, 5:34:05 AM, you wrote: TT accordin to man pf.conf TT 10.0.0.0 - 10.255.255.255 (all of net 10, i.e. 10/8) TT 172.16.0.0 - 172.31.255.255 (i.e. 172.16/12) TT 192.168.0.0 - 192.168.255.255 (i.e. 192.168/16) TT nat-to is usually applied outbound. If applied inbound, nat-to TT to a local IP address is not supported. It is confusing, but probably means something else. I have a number of nat-to to private IPs, and they work fine. I'm not running the latest version, but hope the nat-to behavior hasn't changed (the man hasn't). The nat-to could be tricky, you need to make sure packets in question are going into the interface you want *before* the NAT. Here comes the routing, which is specially tricky, because in a number of cases running route add isn't enough (or doesn't help at all). -- Best regards, Borismailto:bo...@twopoint.com
ThinkPad T60 screen brightness
Hi, I noticed that since I upgraded to 5.5, the two keys that controls the screen brightness do not work anymore, my LCD is constantly set to a mid-dark. This happens when the new framebuffer console runs, but also when X11 runs. During BIOS post or furing the first boot phase, setting works, but will reset as soon as the framebuffer loads. Posts on the net seem to succest xbacklight, but I get: $ xbacklight No outputs have backlight property Suggestions? Getting the two keys (those activated by the blue Fn) would be the best of course. Riccardo
Re: ThinkPad T60 screen brightness
Fri, Jun 27, 2014 at 00:18:57 +0200, Riccardo Mottola may have written: Hi, I noticed that since I upgraded to 5.5, the two keys that controls the screen brightness do not work anymore, my LCD is constantly set to a mid-dark. This happens when the new framebuffer console runs, but also when X11 runs. During BIOS post or furing the first boot phase, setting works, but will reset as soon as the framebuffer loads. Posts on the net seem to succest xbacklight, but I get: $ xbacklight No outputs have backlight property Suggestions? Getting the two keys (those activated by the blue Fn) would be the best of course. Riccardo Same thing on my T60, but if I suspend and resume, those keys work until the next reboot. Matt. -- Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Kernighan -- quoted by Quentyn Taylor
Re: kernel panic from sys/dev/acpi/dsdt.c rev1.210 change
I have this exact same kernel panic. Unfortunately, it's occurring on a host at a remote co-lo. Does anyone know a way that I can get the on-site tech to suppress the assertion by way of some boot-time configuration? Then at least I can get this machine up and running so I can immediately upgrade to the latest snapshot, which apparently fixes this issue. Thanks. On 6/25/2014 8:05 AM, Jason Crawford wrote: My system panic's from the KASSERT() call at line 2269 after dsdt.c was updated to 1.210. All I have is the basic panic message and the dmesg from the last known working snapshot kernel. I tried to get more information but my USB keyboard does not work in the kernel debugger, and my on-board keyboard no longer works at all (I use the laptop as a desktop now). I typed up everything I could see of that panic message by hand. Any patches that need to be tested I will be glad to try out. Here's the panic message and dmesg output. --- panic --- acpi0 at bios0: rev 2panic: kernel diagnostic assertion rgn-v_opregion.iobase % sz == 0 failed: file ../../../../dev/acpi/dsdt.c, line 2269 Stopped atDebugger+0x9:leave panic() at panic+0xfe __assert() at __assert+0x25 aml_rwgas() at aml_rwgas+0x1fd aml_rwfield() at aml_rwfield+0x205 aml_eval() at aml_eval+0x1ae aml_parse() at aml_parse+0x183d aml_parse() at aml_parse+0x1ff aml_parse() at aml_parse+0x1ff aml_parse() at aml_parse+0x1ff end trace frame: 0x81ef48f0, count: 0 RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! IF RUNNING SMP, USE 'mach ddbcpu #' AND 'trace' ON OTHER PROCESSORS, TOO. DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! --- dmesg --- OpenBSD 5.5-current (GENERIC.MP) #219: Thu Jun 19 22:16:22 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4209770496 (4014MB) avail mem = 4088930304 (3899MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdbeda000 (35 entries) bios0: vendor Phoenix Technologies LTD version V1.04 date 10/22/2009 bios0: Gateway NV53 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC SSDT APIC MCFG HPET acpi0: wakeup devices LID0(S3) SLPB(S3) PB2_(S4) PB3_(S4) PB4_(S4) PB5_(S4) PB6_(S4) PB7_(S4) PB9_(S4) PB10(S4) OHC0(S3) OHC1(S3) OHC2(S3) OHC3(S3) OHC4(S3) EHC0(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) II Dual-Core M300, 2000.97 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,3DNOWP,OSVW,IBS,SKINI T,ITSC cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu0: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu0: AMD erratum 721 detected and fixed cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 200MHz cpu0: mwait min=64, max=64, C-substates=0.0.0.0.0, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Athlon(tm) II Dual-Core M300, 2000.03 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,3DNOWP,OSVW,IBS,SKINI T,ITSC cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu1: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu1: AMD erratum 721 detected and fixed cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-9 acpihpet0 at acpi0: 14318180 Hz acpi0: unable to load \\_SB_.PCI0._INI.EXH2 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PB2_) acpiprt2 at acpi0: bus -1 (PB3_) acpiprt3 at acpi0: bus 3 (PB4_) acpiprt4 at acpi0: bus -1 (PB5_) acpiprt5 at acpi0: bus 9 (PB6_) acpiprt6 at acpi0: bus -1 (PB7_) acpiprt7 at acpi0: bus -1 (PB9_) acpiprt8 at acpi0: bus -1 (PB10) acpiprt9 at acpi0: bus 10 (P2P_) acpiprt10 at acpi0: bus 1 (AGP_) acpiec0 at acpi0 acpicpu0 at acpi0: PSS acpicpu1 at acpi0: PSS acpitz0 at acpi0: critical temperature is 95 degC acpitz1 at acpi0: critical temperature is 95 degC acpibtn0 at acpi0: PWRB acpibtn1 at acpi0: LID0 acpibtn2 at acpi0: SLPB acpibat0 at acpi0: BAT0 model AS09A61 serial 4548 type LION oem 494453 acpiac0 at acpi0: AC unit online acpivideo0 at acpi0: VGA_ acpivideo1 at acpi0: VGA_ acpivout0 at acpivideo1: LCD_ cpu0: 2000 MHz: speeds: 2000 1400 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0
Re: kernel panic from sys/dev/acpi/dsdt.c rev1.210 change
Having done a little man page reading on boot-time configuration, I learned about the existence of ukc. I'm wondering whether something like ukc disable acpi0 might circumvent the kernel panic and allow the boot to successfully complete. I'm hoping that since this is a server, ACPI is non-essential. Just grasping at straws in an effort to get this machine up and running again. Thanks. On 6/26/2014 4:21 PM, Scott Vanderbilt wrote: I have this exact same kernel panic. Unfortunately, it's occurring on a host at a remote co-lo. Does anyone know a way that I can get the on-site tech to suppress the assertion by way of some boot-time configuration? Then at least I can get this machine up and running so I can immediately upgrade to the latest snapshot, which apparently fixes this issue. Thanks. On 6/25/2014 8:05 AM, Jason Crawford wrote: My system panic's from the KASSERT() call at line 2269 after dsdt.c was updated to 1.210. All I have is the basic panic message and the dmesg from the last known working snapshot kernel. I tried to get more information but my USB keyboard does not work in the kernel debugger, and my on-board keyboard no longer works at all (I use the laptop as a desktop now). I typed up everything I could see of that panic message by hand. Any patches that need to be tested I will be glad to try out. Here's the panic message and dmesg output. --- panic --- acpi0 at bios0: rev 2panic: kernel diagnostic assertion rgn-v_opregion.iobase % sz == 0 failed: file ../../../../dev/acpi/dsdt.c, line 2269 Stopped atDebugger+0x9:leave panic() at panic+0xfe __assert() at __assert+0x25 aml_rwgas() at aml_rwgas+0x1fd aml_rwfield() at aml_rwfield+0x205 aml_eval() at aml_eval+0x1ae aml_parse() at aml_parse+0x183d aml_parse() at aml_parse+0x1ff aml_parse() at aml_parse+0x1ff aml_parse() at aml_parse+0x1ff end trace frame: 0x81ef48f0, count: 0 RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! IF RUNNING SMP, USE 'mach ddbcpu #' AND 'trace' ON OTHER PROCESSORS, TOO. DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! --- dmesg --- OpenBSD 5.5-current (GENERIC.MP) #219: Thu Jun 19 22:16:22 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4209770496 (4014MB) avail mem = 4088930304 (3899MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdbeda000 (35 entries) bios0: vendor Phoenix Technologies LTD version V1.04 date 10/22/2009 bios0: Gateway NV53 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC SSDT APIC MCFG HPET acpi0: wakeup devices LID0(S3) SLPB(S3) PB2_(S4) PB3_(S4) PB4_(S4) PB5_(S4) PB6_(S4) PB7_(S4) PB9_(S4) PB10(S4) OHC0(S3) OHC1(S3) OHC2(S3) OHC3(S3) OHC4(S3) EHC0(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Athlon(tm) II Dual-Core M300, 2000.97 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,3DNOWP,OSVW,IBS,SKINI T,ITSC cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu0: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu0: AMD erratum 721 detected and fixed cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 200MHz cpu0: mwait min=64, max=64, C-substates=0.0.0.0.0, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Athlon(tm) II Dual-Core M300, 2000.03 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,3DNOWP,OSVW,IBS,SKINI T,ITSC cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative cpu1: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative cpu1: AMD erratum 721 detected and fixed cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-9 acpihpet0 at acpi0: 14318180 Hz acpi0: unable to load \\_SB_.PCI0._INI.EXH2 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PB2_) acpiprt2 at acpi0: bus -1 (PB3_) acpiprt3 at acpi0: bus 3 (PB4_) acpiprt4 at acpi0: bus -1 (PB5_) acpiprt5 at acpi0: bus 9 (PB6_) acpiprt6 at acpi0: bus -1 (PB7_) acpiprt7 at acpi0: bus -1 (PB9_) acpiprt8 at acpi0: bus -1 (PB10) acpiprt9 at acpi0: bus 10 (P2P_) acpiprt10 at acpi0: bus 1 (AGP_) acpiec0 at acpi0 acpicpu0 at acpi0: PSS acpicpu1 at acpi0: PSS
Re: kernel panic from sys/dev/acpi/dsdt.c rev1.210 change
Scott Vanderbilt [li...@datagenic.com] wrote: Having done a little man page reading on boot-time configuration, I learned about the existence of ukc. I'm wondering whether something like ukc disable acpi0 That or disable acpi might circumvent the kernel panic and allow the boot to successfully complete. I'm hoping that since this is a server, ACPI is non-essential. Just grasping at straws in an effort to get this machine up and running again. Thanks. Yeah, try it. More likely to work without an MP kernel. Maybe disable acpi; boot bsd.sp ?
ssh-add: June 26 snap cannot read an id_rsa file
I just updated from a June 17 to June 26 snapshot. The ssh-add utility now fails immediately: $ ssh-add Cannot parse /home/josh/.ssh/id_rsa: invalid format If I restore the /usr/bin/ssh-add program from the June 17 snap, it works fine. Between these two snapshots there was a major bump for libcrypto from 28.0 to 29.0, but that may not be relevant. OpenBSD 5.5-current (GENERIC.MP) #208: Thu Jun 26 08:55:11 MDT 2014 dera...@i386.openbsd.org:/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,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,LAHF,PERF real mem = 1064464384 (1015MB) avail mem = 1034616832 (986MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 04/18/11, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.5 @ 0xf0720 (30 entries) bios0: vendor American Megatrends Inc. version 1601 date 04/18/2011 bios0: ASUSTeK Computer INC. 1005HA acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG OEMB HPET SSDT acpi0: wakeup devices P0P2(S4) P0P1(S4) HDAC(S4) P0P4(S4) P0P8(S4) P0P5(S4) P0P7(S4) P0P9(S4) P0P6(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 133MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.0.2, IBE 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,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,xTPR,PDCM,MOVBE,LAHF,PERF ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 1, remapped to apid 2 acpimcfg0 at acpi0 addr 0xe000, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (P0P5) acpiprt2 at acpi0: bus 1 (P0P7) acpiprt3 at acpi0: bus -1 (P0P6) acpiec0 at acpi0 acpicpu0 at acpi0: C2, C1, PSS acpicpu1 at acpi0: C2, C1, PSS acpitz0 at acpi0: critical temperature is 88 degC acpibat0 at acpi0: BAT0 model 1005HA serial type LION oem ASUS acpiac0 at acpi0: AC unit online acpiasus0 at acpi0 acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibtn2 at acpi0: PWRB bios0: ROM list: 0xc/0xec00! cpu0: Enhanced SpeedStep 1600 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 intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1024x600 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) 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: msi azalia0: codecs: Realtek ALC269 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: apic 2 int 16 pci1 at ppb0 bus 4 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: apic 2 int 17 pci2 at ppb1 bus 2 athn0 at pci2 dev 0 function 0 Atheros AR9285 rev 0x01: apic 2 int 17 athn0: AR9285 rev 2 (1T1R), ROM rev 13, address 00:25:d3:8a:f6:b4 ppb2 at pci0 dev 28 function 3 Intel 82801GB PCIE rev 0x02: apic 2 int 19 pci3 at ppb2 bus 1 alc0 at pci3 dev 0 function 0 Attansic Technology L2C rev 0xc0: msi, address 90:e6:ba:37:cf:5e atphy0 at alc0 phy 0: F1 10/100/1000 PHY, rev. 11 uhci0 at pci0 dev 29 function 0 Intel 82801GB USB rev 0x02: apic 2 int 23 uhci1 at pci0 dev 29 function 1 Intel 82801GB USB rev 0x02: apic 2 int 19 uhci2 at pci0 dev 29 function 2 Intel 82801GB USB rev 0x02: apic 2 int 18 uhci3 at pci0 dev 29 function 3 Intel 82801GB USB rev 0x02: apic 2 int 16 ehci0 at pci0 dev 29 function 7 Intel 82801GB USB rev 0x02: apic 2 int 23 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 5 ichpcib0 at pci0 dev 31 function 0 Intel 82801GBM LPC rev 0x02: PM disabled ahci0 at pci0 dev 31 function 2 Intel 82801GBM AHCI rev 0x02: msi, AHCI 1.1 scsibus1 at ahci0: 32 targets sd0 at scsibus1 targ 0 lun 0: ATA, ST9160314AS, 0002 SCSI3 0/direct fixed naa.5000c50019076592 sd0: 152627MB, 512 bytes/sector, 312581808 sectors usb1 at uhci0: USB revision 1.0 uhub1 at usb1 Intel UHCI root hub rev 1.00/1.00 addr 1 usb2 at uhci1: USB revision 1.0 uhub2 at usb2 Intel UHCI root hub rev 1.00/1.00 addr 1 usb3 at uhci2: USB revision 1.0 uhub3 at usb3 Intel UHCI root hub rev 1.00/1.00 addr 1 usb4 at uhci3: USB revision 1.0 uhub4 at usb4 Intel
