[nForce] changing from nforce sata built in to PCI sata controller
Well... I think this board is crap:) hehe....
but hell... I will not change it but I will change the way it recoginzes my hdd
so...
if I insert a PCI sata controller will my XP boot normaly or will I have to reinstall xp?
Is there an easy way to do this?
Check the package containing the PCI controller. It should say it if supports XP or not. I suspect most do. Then do as the manual for the card recommends. It should be very straightforward.
Similar Messages
-
Suggestions for: external SATA array with a PCIe SATA card??
Seems like this would be a good idea but have no idea what hardware to be considering.
external SATA array with a PCIe SATA card
Thanks
JohnSeems like this would be a good idea but have no idea
what hardware to be considering.
external SATA array with a PCIe SATA card
Thanks
John
I purchased and internal raid kit, Rocket Raid 2320 card and Maxupgrades kit. This guy will help you get your equipment running with over the phone with personal customer service. He has external configs also.
http://www.maxupgrades.com/istore/index.cfm?fuseaction=category.display&category _id=313&CFID=3649947&CFTOKEN=58951206
Good Luck
Z1&V1user -
[nForce] PCI SATA Card...Will it work?
I'm planning on installing a PCI Sata card to run 2 WD 80Gb drives...My question is, will I run into any problems when trying to install Xp??? I know that the card came with a CD, but will windows recognize the card and load the drivers automatically? Thanks in advance and sorry if this a noob question!
if you look on the CD that comes with the card, there maybe some drivers that you have to copy to a floppy disk, for windows xp
as you startup windows setup, it prompts "Press F6 to install third-party SCSI/RAID controller" (or something like that). then insert this floppy when prompted
maybe if you tell us what SATA card you have / intend to buy, someone can offer better advice... -
Wireless adapter name is changing from wlp0s26u1u1 to wlan0
If I reboot my computer from an on state the name changes from wlp0s26u1u1 to wlan0 which makes me unable to connect to wifi, even if I make a netctl profile for wlan0, it fails.
If I start my computer from an off state, the adapter takes the name wlp0s26u1u1 and everything works smoothly.
Why does this happen? Is it a bug? How can I fix it?
Thanks.Cold
-- Logs begin at Fri 2013-09-20 15:59:51 PDT, end at Sun 2014-03-09 06:40:40 PDT. --
Mar 09 06:33:04 ---- systemd-journal[136]: Runtime journal is using 8.0M (max allowed 598.7M, trying to leave 898.1M free of 5.8G available → current limit 598.7M).
Mar 09 06:33:04 ---- systemd-journal[136]: Runtime journal is using 8.0M (max allowed 598.7M, trying to leave 898.1M free of 5.8G available → current limit 598.7M).
Mar 09 06:33:04 ---- kernel: Initializing cgroup subsys cpuset
Mar 09 06:33:04 ---- kernel: Initializing cgroup subsys cpu
Mar 09 06:33:04 ---- kernel: Initializing cgroup subsys cpuacct
Mar 09 06:33:04 ---- kernel: Linux version 3.13.6-1-ARCH (nobody@var-lib-archbuild-extra-x86_64-thomas) (gcc version 4.8.2 20140206 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Mar 7 22:47:48 CET 2014
Mar 09 06:33:04 ---- kernel: Command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda1 rw nomodeset initrd=../initramfs-linux.img
Mar 09 06:33:04 ---- kernel: e820: BIOS-provided physical RAM map:
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000dd74efff] usable
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000dd74f000-0x00000000de052fff] reserved
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000de053000-0x00000000de0dffff] usable
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000de0e0000-0x00000000de17dfff] ACPI NVS
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000de17e000-0x00000000de979fff] reserved
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000de97a000-0x00000000de97afff] usable
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000de97b000-0x00000000de9bdfff] ACPI NVS
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000de9be000-0x00000000df3f6fff] usable
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000df3f7000-0x00000000df7f1fff] reserved
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000df7f2000-0x00000000df7fffff] usable
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Mar 09 06:33:04 ---- kernel: BIOS-e820: [mem 0x0000000100000000-0x000000031effffff] usable
Mar 09 06:33:04 ---- kernel: NX (Execute Disable) protection: active
Mar 09 06:33:04 ---- kernel: SMBIOS 2.7 present.
Mar 09 06:33:04 ---- kernel: DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./Z77 Extreme4, BIOS P2.70 11/28/2012
Mar 09 06:33:04 ---- kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Mar 09 06:33:04 ---- kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Mar 09 06:33:04 ---- kernel: No AGP bridge found
Mar 09 06:33:04 ---- kernel: e820: last_pfn = 0x31f000 max_arch_pfn = 0x400000000
Mar 09 06:33:04 ---- kernel: MTRR default type: uncachable
Mar 09 06:33:04 ---- kernel: MTRR fixed ranges enabled:
Mar 09 06:33:04 ---- kernel: 00000-9FFFF write-back
Mar 09 06:33:04 ---- kernel: A0000-BFFFF uncachable
Mar 09 06:33:04 ---- kernel: C0000-CFFFF write-protect
Mar 09 06:33:04 ---- kernel: D0000-E7FFF uncachable
Mar 09 06:33:04 ---- kernel: E8000-FFFFF write-protect
Mar 09 06:33:04 ---- kernel: MTRR variable ranges enabled:
Mar 09 06:33:04 ---- kernel: 0 base 000000000 mask E00000000 write-back
Mar 09 06:33:04 ---- kernel: 1 base 200000000 mask F00000000 write-back
Mar 09 06:33:04 ---- kernel: 2 base 300000000 mask FF0000000 write-back
Mar 09 06:33:04 ---- kernel: 3 base 310000000 mask FF8000000 write-back
Mar 09 06:33:04 ---- kernel: 4 base 318000000 mask FFC000000 write-back
Mar 09 06:33:04 ---- kernel: 5 base 31C000000 mask FFE000000 write-back
Mar 09 06:33:04 ---- kernel: 6 base 31E000000 mask FFF000000 write-back
Mar 09 06:33:04 ---- kernel: 7 base 0E0000000 mask FE0000000 uncachable
Mar 09 06:33:04 ---- kernel: 8 disabled
Mar 09 06:33:04 ---- kernel: 9 disabled
Mar 09 06:33:04 ---- kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Mar 09 06:33:04 ---- kernel: e820: update [mem 0xe0000000-0xffffffff] usable ==> reserved
Mar 09 06:33:04 ---- kernel: e820: last_pfn = 0xdf800 max_arch_pfn = 0x400000000
Mar 09 06:33:04 ---- kernel: found SMP MP-table at [mem 0x000fd8d0-0x000fd8df] mapped at [ffff8800000fd8d0]
Mar 09 06:33:04 ---- kernel: Scanning 1 areas for low memory corruption
Mar 09 06:33:04 ---- kernel: Base memory trampoline at [ffff880000097000] 97000 size 24576
Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
Mar 09 06:33:04 ---- kernel: [mem 0x00000000-0x000fffff] page 4k
Mar 09 06:33:04 ---- kernel: BRK [0x01b3f000, 0x01b3ffff] PGTABLE
Mar 09 06:33:04 ---- kernel: BRK [0x01b40000, 0x01b40fff] PGTABLE
Mar 09 06:33:04 ---- kernel: BRK [0x01b41000, 0x01b41fff] PGTABLE
Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0x31ee00000-0x31effffff]
Mar 09 06:33:04 ---- kernel: [mem 0x31ee00000-0x31effffff] page 2M
Mar 09 06:33:04 ---- kernel: BRK [0x01b42000, 0x01b42fff] PGTABLE
Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0x31c000000-0x31edfffff]
Mar 09 06:33:04 ---- kernel: [mem 0x31c000000-0x31edfffff] page 2M
Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0x300000000-0x31bffffff]
Mar 09 06:33:04 ---- kernel: [mem 0x300000000-0x31bffffff] page 2M
Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0x00100000-0xdd74efff]
Mar 09 06:33:04 ---- kernel: [mem 0x00100000-0x001fffff] page 4k
Mar 09 06:33:04 ---- kernel: [mem 0x00200000-0xdd5fffff] page 2M
Mar 09 06:33:04 ---- kernel: [mem 0xdd600000-0xdd74efff] page 4k
Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0xde053000-0xde0dffff]
Mar 09 06:33:04 ---- kernel: [mem 0xde053000-0xde0dffff] page 4k
Mar 09 06:33:04 ---- kernel: BRK [0x01b43000, 0x01b43fff] PGTABLE
Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0xde97a000-0xde97afff]
Mar 09 06:33:04 ---- kernel: [mem 0xde97a000-0xde97afff] page 4k
Mar 09 06:33:04 ---- kernel: BRK [0x01b44000, 0x01b44fff] PGTABLE
Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0xde9be000-0xdf3f6fff]
Mar 09 06:33:04 ---- kernel: [mem 0xde9be000-0xde9fffff] page 4k
Mar 09 06:33:04 ---- kernel: [mem 0xdea00000-0xdf1fffff] page 2M
Mar 09 06:33:04 ---- kernel: [mem 0xdf200000-0xdf3f6fff] page 4k
Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0xdf7f2000-0xdf7fffff]
Mar 09 06:33:04 ---- kernel: [mem 0xdf7f2000-0xdf7fffff] page 4k
Mar 09 06:33:04 ---- kernel: init_memory_mapping: [mem 0x100000000-0x2ffffffff]
Mar 09 06:33:04 ---- kernel: [mem 0x100000000-0x2ffffffff] page 2M
Mar 09 06:33:04 ---- kernel: RAMDISK: [mem 0x7fcfd000-0x7fffffff]
Mar 09 06:33:04 ---- kernel: ACPI: RSDP 00000000000f0490 000024 (v02 ALASKA)
Mar 09 06:33:04 ---- kernel: ACPI: XSDT 00000000de16f078 00006C (v01 ALASKA A M I 01072009 AMI 00010013)
Mar 09 06:33:04 ---- kernel: ACPI: FACP 00000000de178f58 00010C (v05 ALASKA A M I 01072009 AMI 00010013)
Mar 09 06:33:04 ---- kernel: ACPI: DSDT 00000000de16f178 009DDD (v02 ALASKA A M I 00000022 INTL 20051117)
Mar 09 06:33:04 ---- kernel: ACPI: FACS 00000000de17c080 000040
Mar 09 06:33:04 ---- kernel: ACPI: APIC 00000000de179068 000072 (v03 ALASKA A M I 01072009 AMI 00010013)
Mar 09 06:33:04 ---- kernel: ACPI: FPDT 00000000de1790e0 000044 (v01 ALASKA A M I 01072009 AMI 00010013)
Mar 09 06:33:04 ---- kernel: ACPI: MCFG 00000000de179128 00003C (v01 ALASKA A M I 01072009 MSFT 00000097)
Mar 09 06:33:04 ---- kernel: ACPI: AAFT 00000000de179168 000112 (v01 ALASKA OEMAAFT 01072009 MSFT 00000097)
Mar 09 06:33:04 ---- kernel: ACPI: HPET 00000000de179280 000038 (v01 ALASKA A M I 01072009 AMI. 00000005)
Mar 09 06:33:04 ---- kernel: ACPI: SSDT 00000000de1792b8 00036D (v01 SataRe SataTabl 00001000 INTL 20091112)
Mar 09 06:33:04 ---- kernel: ACPI: SSDT 00000000de179628 000A92 (v01 PmRef CpuPm 00003000 INTL 20051117)
Mar 09 06:33:04 ---- kernel: ACPI: BGRT 00000000de17a0c0 000038 (v00 ALASKA A M I 01072009 AMI 00010013)
Mar 09 06:33:04 ---- kernel: ACPI: Local APIC address 0xfee00000
Mar 09 06:33:04 ---- kernel: No NUMA configuration found
Mar 09 06:33:04 ---- kernel: Faking a node at [mem 0x0000000000000000-0x000000031effffff]
Mar 09 06:33:04 ---- kernel: Initmem setup node 0 [mem 0x00000000-0x31effffff]
Mar 09 06:33:04 ---- kernel: NODE_DATA [mem 0x31efed000-0x31eff1fff]
Mar 09 06:33:04 ---- kernel: [ffffea0000000000-ffffea000c7fffff] PMD -> [ffff880312600000-ffff88031e5fffff] on node 0
Mar 09 06:33:04 ---- kernel: Zone ranges:
Mar 09 06:33:04 ---- kernel: DMA [mem 0x00001000-0x00ffffff]
Mar 09 06:33:04 ---- kernel: DMA32 [mem 0x01000000-0xffffffff]
Mar 09 06:33:04 ---- kernel: Normal [mem 0x100000000-0x31effffff]
Mar 09 06:33:04 ---- kernel: Movable zone start for each node
Mar 09 06:33:04 ---- kernel: Early memory node ranges
Mar 09 06:33:04 ---- kernel: node 0: [mem 0x00001000-0x0009cfff]
Mar 09 06:33:04 ---- kernel: node 0: [mem 0x00100000-0xdd74efff]
Mar 09 06:33:04 ---- kernel: node 0: [mem 0xde053000-0xde0dffff]
Mar 09 06:33:04 ---- kernel: node 0: [mem 0xde97a000-0xde97afff]
Mar 09 06:33:04 ---- kernel: node 0: [mem 0xde9be000-0xdf3f6fff]
Mar 09 06:33:04 ---- kernel: node 0: [mem 0xdf7f2000-0xdf7fffff]
Mar 09 06:33:04 ---- kernel: node 0: [mem 0x100000000-0x31effffff]
Mar 09 06:33:04 ---- kernel: On node 0 totalpages: 3133888
Mar 09 06:33:04 ---- kernel: DMA zone: 64 pages used for memmap
Mar 09 06:33:04 ---- kernel: DMA zone: 21 pages reserved
Mar 09 06:33:04 ---- kernel: DMA zone: 3996 pages, LIFO batch:0
Mar 09 06:33:04 ---- kernel: DMA32 zone: 14153 pages used for memmap
Mar 09 06:33:04 ---- kernel: DMA32 zone: 905764 pages, LIFO batch:31
Mar 09 06:33:04 ---- kernel: Normal zone: 34752 pages used for memmap
Mar 09 06:33:04 ---- kernel: Normal zone: 2224128 pages, LIFO batch:31
Mar 09 06:33:04 ---- kernel: ACPI: PM-Timer IO Port: 0x408
Mar 09 06:33:04 ---- kernel: ACPI: Local APIC address 0xfee00000
Mar 09 06:33:04 ---- kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Mar 09 06:33:04 ---- kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Mar 09 06:33:04 ---- kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
Mar 09 06:33:04 ---- kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
Mar 09 06:33:04 ---- kernel: ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Mar 09 06:33:04 ---- kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
Mar 09 06:33:04 ---- kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
Mar 09 06:33:04 ---- kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Mar 09 06:33:04 ---- kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Mar 09 06:33:04 ---- kernel: ACPI: IRQ0 used by override.
Mar 09 06:33:04 ---- kernel: ACPI: IRQ2 used by override.
Mar 09 06:33:04 ---- kernel: ACPI: IRQ9 used by override.
Mar 09 06:33:04 ---- kernel: Using ACPI (MADT) for SMP configuration information
Mar 09 06:33:04 ---- kernel: ACPI: HPET id: 0x8086a701 base: 0xfed00000
Mar 09 06:33:04 ---- kernel: smpboot: Allowing 4 CPUs, 0 hotplug CPUs
Mar 09 06:33:04 ---- kernel: nr_irqs_gsi: 40
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0x0009d000-0x0009dfff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0x0009e000-0x0009ffff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xdd74f000-0xde052fff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xde0e0000-0xde17dfff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xde17e000-0xde979fff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xde97b000-0xde9bdfff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xdf3f7000-0xdf7f1fff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xdf800000-0xf7ffffff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xf8000000-0xfbffffff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xfc000000-0xfebfffff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xfed00000-0xfed03fff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xfed04000-0xfed1bfff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xfed20000-0xfedfffff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xfee01000-0xfeffffff]
Mar 09 06:33:04 ---- kernel: PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Mar 09 06:33:04 ---- kernel: e820: [mem 0xdf800000-0xf7ffffff] available for PCI devices
Mar 09 06:33:04 ---- kernel: Booting paravirtualized kernel on bare hardware
Mar 09 06:33:04 ---- kernel: setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:4 nr_node_ids:1
Mar 09 06:33:04 ---- kernel: PERCPU: Embedded 29 pages/cpu @ffff88031ec00000 s86336 r8192 d24256 u524288
Mar 09 06:33:04 ---- kernel: pcpu-alloc: s86336 r8192 d24256 u524288 alloc=1*2097152
Mar 09 06:33:04 ---- kernel: pcpu-alloc: [0] 0 1 2 3
Mar 09 06:33:04 ---- kernel: Built 1 zonelists in Zone order, mobility grouping on. Total pages: 3084898
Mar 09 06:33:04 ---- kernel: Policy zone: Normal
Mar 09 06:33:04 ---- kernel: Kernel command line: BOOT_IMAGE=../vmlinuz-linux root=/dev/sda1 rw nomodeset initrd=../initramfs-linux.img
Mar 09 06:33:04 ---- kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
Mar 09 06:33:04 ---- kernel: xsave: enabled xstate_bv 0x7, cntxt size 0x340
Mar 09 06:33:04 ---- kernel: Checking aperture...
Mar 09 06:33:04 ---- kernel: No AGP bridge found
Mar 09 06:33:04 ---- kernel: Calgary: detecting Calgary via BIOS EBDA area
Mar 09 06:33:04 ---- kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Mar 09 06:33:04 ---- kernel: Memory: 12257392K/12535552K available (5270K kernel code, 836K rwdata, 1672K rodata, 1128K init, 1324K bss, 278160K reserved)
Mar 09 06:33:04 ---- kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Mar 09 06:33:04 ---- kernel: Preemptible hierarchical RCU implementation.
Mar 09 06:33:04 ---- kernel: RCU dyntick-idle grace-period acceleration is enabled.
Mar 09 06:33:04 ---- kernel: Dump stacks of tasks blocking RCU-preempt GP.
Mar 09 06:33:04 ---- kernel: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=4.
Mar 09 06:33:04 ---- kernel: NR_IRQS:8448 nr_irqs:712 16
Mar 09 06:33:04 ---- kernel: Console: colour VGA+ 80x25
Mar 09 06:33:04 ---- kernel: console [tty0] enabled
Mar 09 06:33:04 ---- kernel: allocated 50331648 bytes of page_cgroup
Mar 09 06:33:04 ---- kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
Mar 09 06:33:04 ---- kernel: hpet clockevent registered
Mar 09 06:33:04 ---- kernel: tsc: Fast TSC calibration using PIT
Mar 09 06:33:04 ---- kernel: tsc: Detected 3399.681 MHz processor
Mar 09 06:33:04 ---- kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6802.66 BogoMIPS (lpj=11332270)
Mar 09 06:33:04 ---- kernel: pid_max: default: 32768 minimum: 301
Mar 09 06:33:04 ---- kernel: Security Framework initialized
Mar 09 06:33:04 ---- kernel: AppArmor: AppArmor disabled by boot time parameter
Mar 09 06:33:04 ---- kernel: Yama: becoming mindful.
Mar 09 06:33:04 ---- kernel: Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Mar 09 06:33:04 ---- kernel: Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Mar 09 06:33:04 ---- kernel: Mount-cache hash table entries: 256
Mar 09 06:33:04 ---- kernel: Initializing cgroup subsys memory
Mar 09 06:33:04 ---- kernel: Initializing cgroup subsys devices
Mar 09 06:33:04 ---- kernel: Initializing cgroup subsys freezer
Mar 09 06:33:04 ---- kernel: Initializing cgroup subsys net_cls
Mar 09 06:33:04 ---- kernel: Initializing cgroup subsys blkio
Mar 09 06:33:04 ---- kernel: CPU: Physical Processor ID: 0
Mar 09 06:33:04 ---- kernel: CPU: Processor Core ID: 0
Mar 09 06:33:04 ---- kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Mar 09 06:33:04 ---- kernel: mce: CPU supports 9 MCE banks
Mar 09 06:33:04 ---- kernel: CPU0: Thermal monitoring enabled (TM1)
Mar 09 06:33:04 ---- kernel: Last level iTLB entries: 4KB 512, 2MB 0, 4MB 0
Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32
tlb_flushall_shift: 2
Mar 09 06:33:04 ---- kernel: Freeing SMP alternatives memory: 20K (ffffffff819ed000 - ffffffff819f2000)
Mar 09 06:33:04 ---- kernel: ACPI: Core revision 20131115
Mar 09 06:33:04 ---- kernel: ACPI: All ACPI Tables successfully acquired
Mar 09 06:33:04 ---- kernel: ftrace: allocating 21060 entries in 83 pages
Mar 09 06:33:04 ---- kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Mar 09 06:33:04 ---- kernel: smpboot: CPU0: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz (fam: 06, model: 3a, stepping: 09)
Mar 09 06:33:04 ---- kernel: TSC deadline timer enabled
Mar 09 06:33:04 ---- kernel: Performance Events: PEBS fmt1+, 16-deep LBR, IvyBridge events, full-width counters, Intel PMU driver.
Mar 09 06:33:04 ---- kernel: ... version: 3
Mar 09 06:33:04 ---- kernel: ... bit width: 48
Mar 09 06:33:04 ---- kernel: ... generic registers: 8
Mar 09 06:33:04 ---- kernel: ... value mask: 0000ffffffffffff
Mar 09 06:33:04 ---- kernel: ... max period: 0000ffffffffffff
Mar 09 06:33:04 ---- kernel: ... fixed-purpose events: 3
Mar 09 06:33:04 ---- kernel: ... event mask: 00000007000000ff
Mar 09 06:33:04 ---- kernel: x86: Booting SMP configuration:
Mar 09 06:33:04 ---- kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Mar 09 06:33:04 ---- kernel: .... node #0, CPUs: #1 #2 #3
Mar 09 06:33:04 ---- kernel: x86: Booted up 1 node, 4 CPUs
Mar 09 06:33:04 ---- kernel: smpboot: Total of 4 processors activated (27208.67 BogoMIPS)
Mar 09 06:33:04 ---- kernel: devtmpfs: initialized
Mar 09 06:33:04 ---- kernel: PM: Registering ACPI NVS region [mem 0xde0e0000-0xde17dfff] (647168 bytes)
Mar 09 06:33:04 ---- kernel: PM: Registering ACPI NVS region [mem 0xde97b000-0xde9bdfff] (274432 bytes)
Mar 09 06:33:04 ---- kernel: RTC time: 13:33:02, date: 03/09/14
Mar 09 06:33:04 ---- kernel: NET: Registered protocol family 16
Mar 09 06:33:04 ---- kernel: cpuidle: using governor ladder
Mar 09 06:33:04 ---- kernel: cpuidle: using governor menu
Mar 09 06:33:04 ---- kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Mar 09 06:33:04 ---- kernel: ACPI: bus type PCI registered
Mar 09 06:33:04 ---- kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Mar 09 06:33:04 ---- kernel: PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
Mar 09 06:33:04 ---- kernel: PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
Mar 09 06:33:04 ---- kernel: PCI: Using configuration type 1 for base access
Mar 09 06:33:04 ---- kernel: bio: create slab <bio-0> at 0
Mar 09 06:33:04 ---- kernel: ACPI: Added _OSI(Module Device)
Mar 09 06:33:04 ---- kernel: ACPI: Added _OSI(Processor Device)
Mar 09 06:33:04 ---- kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Mar 09 06:33:04 ---- kernel: ACPI: Added _OSI(Processor Aggregator Device)
Mar 09 06:33:04 ---- kernel: ACPI: Executed 1 blocks of module-level executable AML code
Mar 09 06:33:04 ---- kernel: ACPI Error: [\_PR_.CPU0._PPC] Namespace lookup failure, AE_NOT_FOUND (20131115/psargs-359)
Mar 09 06:33:04 ---- kernel: ACPI Error: Method parse/execution failed [\_PR_.CPU0._PDC] (Node ffff88030d496280), AE_NOT_FOUND (20131115/psparse-536)
Mar 09 06:33:04 ---- kernel: ACPI: SSDT 00000000de002c18 000119 (v01 PmRef ApCst 00003000 INTL 20051117)
Mar 09 06:33:04 ---- kernel: ACPI: Dynamic OEM Table Load:
Mar 09 06:33:04 ---- kernel: ACPI: SSDT (null) 000119 (v01 PmRef ApCst 00003000 INTL 20051117)
Mar 09 06:33:04 ---- kernel: ACPI: Interpreter enabled
Mar 09 06:33:04 ---- kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Mar 09 06:33:04 ---- kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Mar 09 06:33:04 ---- kernel: ACPI: (supports S0 S3 S4 S5)
Mar 09 06:33:04 ---- kernel: ACPI: Using IOAPIC for interrupt routing
Mar 09 06:33:04 ---- kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Mar 09 06:33:04 ---- kernel: ACPI: No dock devices found.
Mar 09 06:33:04 ---- kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
Mar 09 06:33:04 ---- kernel: acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Mar 09 06:33:04 ---- kernel: acpi PNP0A08:00: _OSC: platform does not support [PCIeHotplug PME]
Mar 09 06:33:04 ---- kernel: acpi PNP0A08:00: _OSC: OS now controls [AER PCIeCapability]
Mar 09 06:33:04 ---- kernel: PCI host bridge to bus 0000:00
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [bus 00-3e]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: root bus resource [mem 0xe0000000-0xfeafffff]
Mar 09 06:33:04 ---- kernel: pci 0000:00:00.0: [8086:0150] type 00 class 0x060000
Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: [8086:0151] type 01 class 0x060400
Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
Mar 09 06:33:04 ---- kernel: pci 0000:00:14.0: [8086:1e31] type 00 class 0x0c0330
Mar 09 06:33:04 ---- kernel: pci 0000:00:14.0: reg 0x10: [mem 0xf7f00000-0xf7f0ffff 64bit]
Mar 09 06:33:04 ---- kernel: pci 0000:00:14.0: PME# supported from D3hot D3cold
Mar 09 06:33:04 ---- kernel: pci 0000:00:14.0: System wakeup disabled by ACPI
Mar 09 06:33:04 ---- kernel: pci 0000:00:16.0: [8086:1e3a] type 00 class 0x078000
Mar 09 06:33:04 ---- kernel: pci 0000:00:16.0: reg 0x10: [mem 0xf7f1a000-0xf7f1a00f 64bit]
Mar 09 06:33:04 ---- kernel: pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
Mar 09 06:33:04 ---- kernel: pci 0000:00:1a.0: [8086:1e2d] type 00 class 0x0c0320
Mar 09 06:33:04 ---- kernel: pci 0000:00:1a.0: reg 0x10: [mem 0xf7f18000-0xf7f183ff]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Mar 09 06:33:04 ---- kernel: pci 0000:00:1a.0: System wakeup disabled by ACPI
Mar 09 06:33:04 ---- kernel: pci 0000:00:1b.0: [8086:1e20] type 00 class 0x040300
Mar 09 06:33:04 ---- kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf7f10000-0xf7f13fff 64bit]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
Mar 09 06:33:04 ---- kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.0: [8086:1e10] type 01 class 0x060400
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.3: [8086:1e16] type 01 class 0x060400
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.3: System wakeup disabled by ACPI
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.4: [8086:1e18] type 01 class 0x060400
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.4: System wakeup disabled by ACPI
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.5: [8086:1e1a] type 01 class 0x060400
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.5: System wakeup disabled by ACPI
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.7: [8086:1e1e] type 01 class 0x060400
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.7: System wakeup disabled by ACPI
Mar 09 06:33:04 ---- kernel: pci 0000:00:1d.0: [8086:1e26] type 00 class 0x0c0320
Mar 09 06:33:04 ---- kernel: pci 0000:00:1d.0: reg 0x10: [mem 0xf7f17000-0xf7f173ff]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Mar 09 06:33:04 ---- kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.0: [8086:1e44] type 00 class 0x060100
Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.2: [8086:1e02] type 00 class 0x010601
Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.2: reg 0x10: [io 0xf070-0xf077]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.2: reg 0x14: [io 0xf060-0xf063]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.2: reg 0x18: [io 0xf050-0xf057]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.2: reg 0x1c: [io 0xf040-0xf043]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.2: reg 0x20: [io 0xf020-0xf03f]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.2: reg 0x24: [mem 0xf7f16000-0xf7f167ff]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.2: PME# supported from D3hot
Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.3: [8086:1e22] type 00 class 0x0c0500
Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.3: reg 0x10: [mem 0xf7f15000-0xf7f150ff 64bit]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1f.3: reg 0x20: [io 0xf000-0xf01f]
Mar 09 06:33:04 ---- kernel: pci 0000:01:00.0: [1002:6738] type 00 class 0x030000
Mar 09 06:33:04 ---- kernel: pci 0000:01:00.0: reg 0x10: [mem 0xe0000000-0xefffffff 64bit pref]
Mar 09 06:33:04 ---- kernel: pci 0000:01:00.0: reg 0x18: [mem 0xf7e20000-0xf7e3ffff 64bit]
Mar 09 06:33:04 ---- kernel: pci 0000:01:00.0: reg 0x20: [io 0xe000-0xe0ff]
Mar 09 06:33:04 ---- kernel: pci 0000:01:00.0: reg 0x30: [mem 0xf7e00000-0xf7e1ffff pref]
Mar 09 06:33:04 ---- kernel: pci 0000:01:00.0: supports D1 D2
Mar 09 06:33:04 ---- kernel: pci 0000:01:00.1: [1002:aa88] type 00 class 0x040300
Mar 09 06:33:04 ---- kernel: pci 0000:01:00.1: reg 0x10: [mem 0xf7e40000-0xf7e43fff 64bit]
Mar 09 06:33:04 ---- kernel: pci 0000:01:00.1: supports D1 D2
Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: bridge window [mem 0xf7e00000-0xf7efffff]
Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: bridge window [mem 0xe0000000-0xefffffff 64bit pref]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
Mar 09 06:33:04 ---- kernel: pci 0000:03:00.0: [1b21:0612] type 00 class 0x010601
Mar 09 06:33:04 ---- kernel: pci 0000:03:00.0: reg 0x10: [io 0xd050-0xd057]
Mar 09 06:33:04 ---- kernel: pci 0000:03:00.0: reg 0x14: [io 0xd040-0xd043]
Mar 09 06:33:04 ---- kernel: pci 0000:03:00.0: reg 0x18: [io 0xd030-0xd037]
Mar 09 06:33:04 ---- kernel: pci 0000:03:00.0: reg 0x1c: [io 0xd020-0xd023]
Mar 09 06:33:04 ---- kernel: pci 0000:03:00.0: reg 0x20: [io 0xd000-0xd01f]
Mar 09 06:33:04 ---- kernel: pci 0000:03:00.0: reg 0x24: [mem 0xf7d00000-0xf7d001ff]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.3: PCI bridge to [bus 03]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.3: bridge window [io 0xd000-0xdfff]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.3: bridge window [mem 0xf7d00000-0xf7dfffff]
Mar 09 06:33:04 ---- kernel: pci 0000:04:00.0: [14e4:16b1] type 00 class 0x020000
Mar 09 06:33:04 ---- kernel: pci 0000:04:00.0: reg 0x10: [mem 0xf0010000-0xf001ffff 64bit pref]
Mar 09 06:33:04 ---- kernel: pci 0000:04:00.0: reg 0x18: [mem 0xf0000000-0xf000ffff 64bit pref]
Mar 09 06:33:04 ---- kernel: pci 0000:04:00.0: reg 0x30: [mem 0xf7c00000-0xf7c007ff pref]
Mar 09 06:33:04 ---- kernel: pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.4: bridge window [mem 0xf7c00000-0xf7cfffff]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.4: bridge window [mem 0xf0000000-0xf00fffff 64bit pref]
Mar 09 06:33:04 ---- kernel: pci 0000:05:00.0: [1b21:1080] type 01 class 0x060401
Mar 09 06:33:04 ---- kernel: pci 0000:05:00.0: System wakeup disabled by ACPI
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.5: PCI bridge to [bus 05-06]
Mar 09 06:33:04 ---- kernel: pci 0000:05:00.0: PCI bridge to [bus 06] (subtractive decode)
Mar 09 06:33:04 ---- kernel: pci 0000:05:00.0: bridge window [??? 0x00000000 flags 0x0] (subtractive decode)
Mar 09 06:33:04 ---- kernel: pci 0000:05:00.0: bridge window [??? 0x00000000 flags 0x0] (subtractive decode)
Mar 09 06:33:04 ---- kernel: pci 0000:05:00.0: bridge window [??? 0x00000000 flags 0x0] (subtractive decode)
Mar 09 06:33:04 ---- kernel: pci 0000:05:00.0: bridge window [??? 0x00000000 flags 0x0] (subtractive decode)
Mar 09 06:33:04 ---- kernel: pci 0000:07:00.0: [1b21:1042] type 00 class 0x0c0330
Mar 09 06:33:04 ---- kernel: pci 0000:07:00.0: reg 0x10: [mem 0xf7b00000-0xf7b07fff 64bit]
Mar 09 06:33:04 ---- kernel: pci 0000:07:00.0: PME# supported from D3hot D3cold
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.7: PCI bridge to [bus 07]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.7: bridge window [mem 0xf7b00000-0xf7bfffff]
Mar 09 06:33:04 ---- kernel: acpi PNP0A08:00: Disabling ASPM (FADT indicates it is unsupported)
Mar 09 06:33:04 ---- kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
Mar 09 06:33:04 ---- kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
Mar 09 06:33:04 ---- kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 *11 12 14 15)
Mar 09 06:33:04 ---- kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 10 11 12 14 15)
Mar 09 06:33:04 ---- kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
Mar 09 06:33:04 ---- kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
Mar 09 06:33:04 ---- kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs *3 4 5 6 10 11 12 14 15)
Mar 09 06:33:04 ---- kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 *4 5 6 10 11 12 14 15)
Mar 09 06:33:04 ---- kernel: ACPI: Enabled 4 GPEs in block 00 to 3F
Mar 09 06:33:04 ---- kernel: ACPI: \_SB_.PCI0: notify handler is installed
Mar 09 06:33:04 ---- kernel: Found 1 acpi root devices
Mar 09 06:33:04 ---- kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
Mar 09 06:33:04 ---- kernel: vgaarb: loaded
Mar 09 06:33:04 ---- kernel: vgaarb: bridge control possible 0000:01:00.0
Mar 09 06:33:04 ---- kernel: PCI: Using ACPI for IRQ routing
Mar 09 06:33:04 ---- kernel: PCI: pci_cache_line_size set to 64 bytes
Mar 09 06:33:04 ---- kernel: e820: reserve RAM buffer [mem 0x0009d800-0x0009ffff]
Mar 09 06:33:04 ---- kernel: e820: reserve RAM buffer [mem 0xdd74f000-0xdfffffff]
Mar 09 06:33:04 ---- kernel: e820: reserve RAM buffer [mem 0xde0e0000-0xdfffffff]
Mar 09 06:33:04 ---- kernel: e820: reserve RAM buffer [mem 0xde97b000-0xdfffffff]
Mar 09 06:33:04 ---- kernel: e820: reserve RAM buffer [mem 0xdf3f7000-0xdfffffff]
Mar 09 06:33:04 ---- kernel: e820: reserve RAM buffer [mem 0xdf800000-0xdfffffff]
Mar 09 06:33:04 ---- kernel: e820: reserve RAM buffer [mem 0x31f000000-0x31fffffff]
Mar 09 06:33:04 ---- kernel: NetLabel: Initializing
Mar 09 06:33:04 ---- kernel: NetLabel: domain hash size = 128
Mar 09 06:33:04 ---- kernel: NetLabel: protocols = UNLABELED CIPSOv4
Mar 09 06:33:04 ---- kernel: NetLabel: unlabeled traffic allowed by default
Mar 09 06:33:04 ---- kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Mar 09 06:33:04 ---- kernel: hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Mar 09 06:33:04 ---- kernel: Switched to clocksource hpet
Mar 09 06:33:04 ---- kernel: pnp: PnP ACPI init
Mar 09 06:33:04 ---- kernel: ACPI: bus type PNP registered
Mar 09 06:33:04 ---- kernel: system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
Mar 09 06:33:04 ---- kernel: pnp 00:01: [dma 4]
Mar 09 06:33:04 ---- kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Mar 09 06:33:04 ---- kernel: pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
Mar 09 06:33:04 ---- kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
Mar 09 06:33:04 ---- kernel: system 00:04: [io 0x0680-0x069f] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:04: [io 0x1000-0x100f] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:04: [io 0xffff] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:04: [io 0xffff] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:04: [io 0x0400-0x0453] could not be reserved
Mar 09 06:33:04 ---- kernel: system 00:04: [io 0x0458-0x047f] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:04: [io 0x0500-0x057f] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:04: [io 0x164e-0x164f] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
Mar 09 06:33:04 ---- kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
Mar 09 06:33:04 ---- kernel: system 00:06: [io 0x0454-0x0457] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
Mar 09 06:33:04 ---- kernel: system 00:07: [io 0x0290-0x029f] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
Mar 09 06:33:04 ---- kernel: system 00:08: [io 0x04d0-0x04d1] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
Mar 09 06:33:04 ---- kernel: pnp 00:09: Plug and Play ACPI device, IDs PNP0c04 (active)
Mar 09 06:33:04 ---- kernel: pnp 00:0a: Plug and Play ACPI device, IDs PNP0303 PNP030b (active)
Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xfed1c000-0xfed1ffff] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xfed10000-0xfed17fff] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xfed18000-0xfed18fff] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xfed19000-0xfed19fff] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xf8000000-0xfbffffff] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xfed20000-0xfed3ffff] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xfed90000-0xfed93fff] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xfed45000-0xfed8ffff] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xff000000-0xffffffff] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xfee00000-0xfeefffff] could not be reserved
Mar 09 06:33:04 ---- kernel: system 00:0b: [mem 0xf0100000-0xf0100fff] has been reserved
Mar 09 06:33:04 ---- kernel: system 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active)
Mar 09 06:33:04 ---- kernel: pnp: PnP ACPI: found 12 devices
Mar 09 06:33:04 ---- kernel: ACPI: bus type PNP unregistered
Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: PCI bridge to [bus 01]
Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: bridge window [mem 0xf7e00000-0xf7efffff]
Mar 09 06:33:04 ---- kernel: pci 0000:00:01.0: bridge window [mem 0xe0000000-0xefffffff 64bit pref]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.3: PCI bridge to [bus 03]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.3: bridge window [io 0xd000-0xdfff]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.3: bridge window [mem 0xf7d00000-0xf7dfffff]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.4: PCI bridge to [bus 04]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.4: bridge window [mem 0xf7c00000-0xf7cfffff]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.4: bridge window [mem 0xf0000000-0xf00fffff 64bit pref]
Mar 09 06:33:04 ---- kernel: pci 0000:05:00.0: PCI bridge to [bus 06]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.5: PCI bridge to [bus 05-06]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.7: PCI bridge to [bus 07]
Mar 09 06:33:04 ---- kernel: pci 0000:00:1c.7: bridge window [mem 0xf7b00000-0xf7bfffff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000d3fff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 8 [mem 0x000d4000-0x000d7fff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 9 [mem 0x000d8000-0x000dbfff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 10 [mem 0x000dc000-0x000dffff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 11 [mem 0x000e0000-0x000e3fff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 12 [mem 0x000e4000-0x000e7fff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:00: resource 13 [mem 0xe0000000-0xfeafffff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:01: resource 0 [io 0xe000-0xefff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:01: resource 1 [mem 0xf7e00000-0xf7efffff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:01: resource 2 [mem 0xe0000000-0xefffffff 64bit pref]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:03: resource 0 [io 0xd000-0xdfff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:03: resource 1 [mem 0xf7d00000-0xf7dfffff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:04: resource 1 [mem 0xf7c00000-0xf7cfffff]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:04: resource 2 [mem 0xf0000000-0xf00fffff 64bit pref]
Mar 09 06:33:04 ---- kernel: pci_bus 0000:07: resource 1 [mem 0xf7b00000-0xf7bfffff]
Mar 09 06:33:04 ---- kernel: NET: Registered protocol family 2
Mar 09 06:33:04 ---- kernel: TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
Mar 09 06:33:04 ---- kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Mar 09 06:33:04 ---- kernel: TCP: Hash tables configured (established 131072 bind 65536)
Mar 09 06:33:04 ---- kernel: TCP: reno registered
Mar 09 06:33:04 ---- kernel: UDP hash table entries: 8192 (order: 6, 262144 bytes)
Mar 09 06:33:04 ---- kernel: UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes)
Mar 09 06:33:04 ---- kernel: NET: Registered protocol family 1
Mar 09 06:33:04 ---- kernel: pci 0000:01:00.0: Boot video device
Mar 09 06:33:04 ---- kernel: PCI: CLS 64 bytes, default 64
Mar 09 06:33:04 ---- kernel: Unpacking initramfs...
Mar 09 06:33:04 ---- kernel: Freeing initrd memory: 3084K (ffff88007fcfd000 - ffff880080000000)
Mar 09 06:33:04 ---- kernel: PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Mar 09 06:33:04 ---- kernel: software IO TLB [mem 0xd974f000-0xdd74f000] (64MB) mapped at [ffff8800d974f000-ffff8800dd74efff]
Mar 09 06:33:04 ---- kernel: Scanning for low memory corruption every 60 seconds
Mar 09 06:33:04 ---- kernel: audit: initializing netlink socket (disabled)
Mar 09 06:33:04 ---- kernel: type=2000 audit(1394371982.283:1): initialized
Mar 09 06:33:04 ---- kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
Mar 09 06:33:04 ---- kernel: zbud: loaded
Mar 09 06:33:04 ---- kernel: VFS: Disk quotas dquot_6.5.2
Mar 09 06:33:04 ---- kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Mar 09 06:33:04 ---- kernel: msgmni has been set to 23946
Mar 09 06:33:04 ---- kernel: Key type big_key registered
Mar 09 06:33:04 ---- kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Mar 09 06:33:04 ---- kernel: io scheduler noop registered
Mar 09 06:33:04 ---- kernel: io scheduler deadline registered
Mar 09 06:33:04 ---- kernel: io scheduler cfq registered (default)
Mar 09 06:33:04 ---- kernel: pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
Mar 09 06:33:04 ---- kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Mar 09 06:33:04 ---- kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Mar 09 06:33:04 ---- kernel: intel_idle: MWAIT substates: 0x1120
Mar 09 06:33:04 ---- kernel: intel_idle: v0.4 model 0x3A
Mar 09 06:33:04 ---- kernel: intel_idle: lapic_timer_reliable_states 0xffffffff
Mar 09 06:33:04 ---- kernel: GHES: HEST is not enabled!
Mar 09 06:33:04 ---- kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
Mar 09 06:33:04 ---- kernel: Linux agpgart interface v0.103
Mar 09 06:33:04 ---- kernel: rtc_cmos 00:05: RTC can wake from S4
Mar 09 06:33:04 ---- kernel: rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
Mar 09 06:33:04 ---- kernel: rtc_cmos 00:05: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
Mar 09 06:33:04 ---- kernel: Intel P-state driver initializing.
Mar 09 06:33:04 ---- kernel: Intel pstate controlling: cpu 0
Mar 09 06:33:04 ---- kernel: Intel pstate controlling: cpu 1
Mar 09 06:33:04 ---- kernel: Intel pstate controlling: cpu 2
Mar 09 06:33:04 ---- kernel: Intel pstate controlling: cpu 3
Mar 09 06:33:04 ---- kernel: drop_monitor: Initializing network drop monitor service
Mar 09 06:33:04 ---- kernel: TCP: cubic registered
Mar 09 06:33:04 ---- kernel: NET: Registered protocol family 10
Mar 09 06:33:04 ---- kernel: NET: Registered protocol family 17
Mar 09 06:33:04 ---- kernel: Key type dns_resolver registered
Mar 09 06:33:04 ---- kernel: registered taskstats version 1
Mar 09 06:33:04 ---- kernel: Magic number: 6:65:584
Mar 09 06:33:04 ---- kernel: pci_bus 0000:05: hash matches
Mar 09 06:33:04 ---- kernel: rtc_cmos 00:05: setting system clock to 2014-03-09 13:33:02 UTC (1394371982)
Mar 09 06:33:04 ---- kernel: PM: Hibernation image not present or could not be loaded.
Mar 09 06:33:04 ---- kernel: Freeing unused kernel memory: 1128K (ffffffff818d3000 - ffffffff819ed000)
Mar 09 06:33:04 ---- kernel: Write protecting the kernel read-only data: 8192k
Mar 09 06:33:04 ---- kernel: Freeing unused kernel memory: 864K (ffff880001528000 - ffff880001600000)
Mar 09 06:33:04 ---- kernel: Freeing unused kernel memory: 376K (ffff8800017a2000 - ffff880001800000)
Mar 09 06:33:04 ---- kernel: random: systemd-tmpfile urandom read with 1 bits of entropy available
Mar 09 06:33:04 ---- systemd-udevd[56]: starting version 210
Mar 09 06:33:04 ---- kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
Mar 09 06:33:04 ---- kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Mar 09 06:33:04 ---- kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Mar 09 06:33:04 ---- kernel: ACPI: bus type USB registered
Mar 09 06:33:04 ---- kernel: usbcore: registered new interface driver usbfs
Mar 09 06:33:04 ---- kernel: usbcore: registered new interface driver hub
Mar 09 06:33:04 ---- kernel: usbcore: registered new device driver usb
Mar 09 06:33:04 ---- kernel: SCSI subsystem initialized
Mar 09 06:33:04 ---- kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Mar 09 06:33:04 ---- kernel: ehci-pci: EHCI PCI platform driver
Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller
Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1a.0: debug port 2
Mar 09 06:33:04 ---- kernel: libata version 3.00 loaded.
Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7f18000
Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Mar 09 06:33:04 ---- kernel: hub 1-0:1.0: USB hub found
Mar 09 06:33:04 ---- kernel: hub 1-0:1.0: 2 ports detected
Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller
Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1d.0: debug port 2
Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7f17000
Mar 09 06:33:04 ---- kernel: ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Mar 09 06:33:04 ---- kernel: hub 2-0:1.0: USB hub found
Mar 09 06:33:04 ---- kernel: hub 2-0:1.0: 2 ports detected
Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:00:14.0: irq 41 for MSI/MSI-X
Mar 09 06:33:04 ---- kernel: hub 3-0:1.0: USB hub found
Mar 09 06:33:04 ---- kernel: hub 3-0:1.0: 4 ports detected
Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller
Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
Mar 09 06:33:04 ---- kernel: hub 4-0:1.0: USB hub found
Mar 09 06:33:04 ---- kernel: hub 4-0:1.0: 4 ports detected
Mar 09 06:33:04 ---- kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
Mar 09 06:33:04 ---- kernel: ahci 0000:00:1f.2: version 3.0
Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:07:00.0: xHCI Host Controller
Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:07:00.0: new USB bus registered, assigned bus number 5
Mar 09 06:33:04 ---- kernel: ahci 0000:00:1f.2: irq 42 for MSI/MSI-X
Mar 09 06:33:04 ---- kernel: ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x3f impl SATA mode
Mar 09 06:33:04 ---- kernel: ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part ems apst
Mar 09 06:33:04 ---- kernel: scsi0 : ahci
Mar 09 06:33:04 ---- kernel: scsi1 : ahci
Mar 09 06:33:04 ---- kernel: scsi2 : ahci
Mar 09 06:33:04 ---- kernel: scsi3 : ahci
Mar 09 06:33:04 ---- kernel: scsi4 : ahci
Mar 09 06:33:04 ---- kernel: scsi5 : ahci
Mar 09 06:33:04 ---- kernel: ata1: SATA max UDMA/133 abar m2048@0xf7f16000 port 0xf7f16100 irq 42
Mar 09 06:33:04 ---- kernel: ata2: SATA max UDMA/133 abar m2048@0xf7f16000 port 0xf7f16180 irq 42
Mar 09 06:33:04 ---- kernel: ata3: SATA max UDMA/133 abar m2048@0xf7f16000 port 0xf7f16200 irq 42
Mar 09 06:33:04 ---- kernel: ata4: SATA max UDMA/133 abar m2048@0xf7f16000 port 0xf7f16280 irq 42
Mar 09 06:33:04 ---- kernel: ata5: SATA max UDMA/133 abar m2048@0xf7f16000 port 0xf7f16300 irq 42
Mar 09 06:33:04 ---- kernel: ata6: SATA max UDMA/133 abar m2048@0xf7f16000 port 0xf7f16380 irq 42
Mar 09 06:33:04 ---- kernel: ahci 0000:03:00.0: irq 43 for MSI/MSI-X
Mar 09 06:33:04 ---- kernel: ahci 0000:03:00.0: SSS flag set, parallel bus scan disabled
Mar 09 06:33:04 ---- kernel: ahci 0000:03:00.0: AHCI 0001.0200 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
Mar 09 06:33:04 ---- kernel: ahci 0000:03:00.0: flags: 64bit ncq sntf stag led clo pmp pio slum part ccc sxs
Mar 09 06:33:04 ---- kernel: scsi6 : ahci
Mar 09 06:33:04 ---- kernel: scsi7 : ahci
Mar 09 06:33:04 ---- kernel: ata7: SATA max UDMA/133 abar m512@0xf7d00000 port 0xf7d00100 irq 43
Mar 09 06:33:04 ---- kernel: ata8: SATA max UDMA/133 abar m512@0xf7d00000 port 0xf7d00180 irq 43
Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:07:00.0: irq 44 for MSI/MSI-X
Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:07:00.0: irq 45 for MSI/MSI-X
Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:07:00.0: irq 46 for MSI/MSI-X
Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:07:00.0: irq 47 for MSI/MSI-X
Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:07:00.0: irq 48 for MSI/MSI-X
Mar 09 06:33:04 ---- kernel: hub 5-0:1.0: USB hub found
Mar 09 06:33:04 ---- kernel: hub 5-0:1.0: 2 ports detected
Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:07:00.0: xHCI Host Controller
Mar 09 06:33:04 ---- kernel: xhci_hcd 0000:07:00.0: new USB bus registered, assigned bus number 6
Mar 09 06:33:04 ---- kernel: hub 6-0:1.0: USB hub found
Mar 09 06:33:04 ---- kernel: hub 6-0:1.0: 2 ports detected
Mar 09 06:33:04 ---- kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
Mar 09 06:33:04 ---- kernel: ata1: SATA link down (SStatus 0 SControl 300)
Mar 09 06:33:04 ---- kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 09 06:33:04 ---- kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 09 06:33:04 ---- kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 09 06:33:04 ---- kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 09 06:33:04 ---- kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 09 06:33:04 ---- kernel: ata2.00: ATA-8: Corsair CSSD-V64GB2, 2.2, max UDMA/133
Mar 09 06:33:04 ---- kernel: ata2.00: 125045424 sectors, multi 1: LBA48 NCQ (depth 31/32), AA
Mar 09 06:33:04 ---- kernel: ata7: SATA link down (SStatus 0 SControl 300)
Mar 09 06:33:04 ---- kernel: ata5: SATA link down (SStatus 0 SControl 300)
Mar 09 06:33:04 ---- kernel: ata6: SATA link down (SStatus 0 SControl 300)
Mar 09 06:33:04 ---- kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Mar 09 06:33:04 ---- kernel: ata2.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 09 06:33:04 ---- kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 09 06:33:04 ---- kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 09 06:33:04 ---- kernel: ata2.00: configured for UDMA/133
Mar 09 06:33:04 ---- kernel: scsi 1:0:0:0: Direct-Access ATA Corsair CSSD-V64 2.2 PQ: 0 ANSI: 5
Mar 09 06:33:04 ---- kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 09 06:33:04 ---- kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 09 06:33:04 ---- kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 09 06:33:04 ---- kernel: sd 1:0:0:0: [sda] 125045424 512-byte logical blocks: (64.0 GB/59.6 GiB)
Mar 09 06:33:04 ---- kernel: sd 1:0:0:0: [sda] Write Protect is off
Mar 09 06:33:04 ---- kernel: sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
Mar 09 06:33:04 ---- kernel: sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar 09 06:33:04 ---- kernel: ata4.00: ATA-8: WDC WD6400AACS-00G8B1, 05.04C05, max UDMA/133
Mar 09 06:33:04 ---- kernel: ata4.00: 1250263728 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Mar 09 06:33:04 ---- kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 09 06:33:04 ---- kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 09 06:33:04 ---- kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 09 06:33:04 ---- kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 09 06:33:04 ---- kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 09 06:33:04 ---- kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 09 06:33:04 ---- kernel: sda: sda1
Mar 09 06:33:04 ---- kernel: ata4.00: configured for UDMA/133
Mar 09 06:33:04 ---- kernel: sd 1:0:0:0: [sda] Attached SCSI disk
Mar 09 06:33:04 ---- kernel: hub 1-1:1.0: USB hub found
Mar 09 06:33:04 ---- kernel: hub 1-1:1.0: 6 ports detected
Mar 09 06:33:04 ---- kernel: ata3.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133
Mar 09 06:33:04 ---- kernel: ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Mar 09 06:33:04 ---- kernel: ata3.00: ACPI cmd ef/10:06:00:00:00:00 (SET FEATURES) succeeded
Mar 09 06:33:04 ---- kernel: ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
Mar 09 06:33:04 ---- kernel: ata3.00: ACPI cmd b1/c1:00:00:00:00:00 (DEVICE CONFIGURATION OVERLAY) filtered out
Mar 09 06:33:04 ---- kernel: ata3.00: configured for UDMA/133
Mar 09 06:33:04 ---- kernel: scsi 2:0:0:0: Direct-Access ATA SAMSUNG HD103SJ 1AJ1 PQ: 0 ANSI: 5
Mar 09 06:33:04 ---- kernel: sd 2:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Mar 09 06:33:04 ---- kernel: sd 2:0:0:0: [sdb] Write Protect is off
Mar 09 06:33:04 ---- kernel: sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Mar 09 06:33:04 ---- kernel: scsi 3:0:0:0: Direct-Access ATA WDC WD6400AACS-0 05.0 PQ: 0 ANSI: 5
Mar 09 06:33:04 ---- kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar 09 06:33:04 ---- kernel: sd 3:0:0:0: [sdc] 1250263728 512-byte logical blocks: (640 GB/596 GiB)
Mar 09 06:33:04 ---- kernel: sd 3:0:0:0: [sdc] Write Protect is off
Mar 09 06:33:04 ---- kernel: sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Mar 09 06:33:04 ---- kernel: sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar 09 06:33:04 ---- kernel: sdc: sdc1 sdc2
Mar 09 06:33:04 ---- kernel: sd 3:0:0:0: [sdc] Attached SCSI disk
Mar 09 06:33:04 ---- kernel: usb 2-1: new high-speed USB device number 2 using ehci-pci
Mar 09 06:33:04 ---- kernel: sdb: sdb1 sdb2
Mar 09 06:33:04 ---- kernel: sd 2:0:0:0: [sdb] Attached SCSI disk
Mar 09 06:33:04 ---- kernel: hub 2-1:1.0: USB hub found
Mar 09 06:33:04 ---- kernel: hub 2-1:1.0: 8 ports detected
Mar 09 06:33:04 ---- kernel: usb 1-1.1: new high-speed USB device number 3 using ehci-pci
Mar 09 06:33:04 ---- kernel: ata8: SATA link down (SStatus 0 SControl 300)
Mar 09 06:33:04 ---- kernel: usb 2-1.5: new low-speed USB device number 3 using ehci-pci
Mar 09 06:33:04 ---- kernel: tsc: Refined TSC clocksource calibration: 3400.023 MHz
Mar 09 06:33:04 ---- kernel: hidraw: raw HID events driver (C) Jiri Kosina
Mar 09 06:33:04 ---- kernel: usbcore: registered new interface driver usbhid
Mar 09 06:33:04 ---- kernel: usbhid: USB HID core driver
Mar 09 06:33:04 ---- kernel: input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input1
Mar 09 06:33:04 ---- kernel: hid-generic 0003:046D:C051.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.0-1.5/input0
Mar 09 06:33:04 ---- kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Mar 09 06:33:04 ---- kernel: random: nonblocking pool is initialized
Mar 09 06:33:04 ---- systemd[1]: systemd 210 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ +SECCOMP -APPARMOR)
Mar 09 06:33:04 ---- systemd[1]: Detected architecture 'x86-64'.
Mar 09 06:33:04 ---- systemd[1]: Set hostname to <---->.
Mar 09 06:33:04 ---- systemd[1]: Configuration file /etc/systemd/system/netctl@wlp0s26u1u1\x2dXXXXX.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Mar 09 06:33:04 ---- systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
Mar 09 06:33:04 ---- systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
Mar 09 06:33:04 ---- systemd[1]: Started Forward Password Requests to Wall Directory Watch.
Mar 09 06:33:04 ---- systemd[1]: Expecting device sys-subsystem-net-devices-wlp0s26u1u1.device...
Mar 09 06:33:04 ---- systemd[1]: Starting Remote File Systems.
Mar 09 06:33:04 ---- systemd[1]: Reached target Remote File Systems.
Mar 09 06:33:04 ---- systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
Mar 09 06:33:04 ---- systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
Mar 09 06:33:04 ---- systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
Mar 09 06:33:04 ---- systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
Mar 09 06:33:04 ---- systemd[1]: Starting Paths.
Mar 09 06:33:04 ---- systemd[1]: Reached target Paths.
Mar 09 06:33:04 ---- systemd[1]: Starting Encrypted Volumes.
Mar 09 06:33:04 ---- systemd[1]: Reached target Encrypted Volumes.
Mar 09 06:33:04 ---- systemd[1]: Starting Swap.
Mar 09 06:33:04 ---- systemd[1]: Reached target Swap.
Mar 09 06:33:04 ---- systemd[1]: Expecting device dev-disk-by\x2duuid-174c1e56\x2de13d\x2d4806\x2db77b\x2dfd36effe9148.device...
Mar 09 06:33:04 ---- systemd[1]: Expecting device dev-disk-by\x2duuid-7553f5d7\x2deb2c\x2d4f49\x2db9a1\x2d3e1c2850bf5f.device...
Mar 09 06:33:04 ---- systemd[1]: Starting Root Slice.
Mar 09 06:33:04 ---- systemd[1]: Created slice Root Slice.
Mar 09 06:33:04 ---- systemd[1]: Starting User and Session Slice.
Mar 09 06:33:04 ---- systemd[1]: Created slice User and Session Slice.
Mar 09 06:33:04 ---- systemd[1]: Starting Device-mapper event daemon FIFOs.
Mar 09 06:33:04 ---- systemd[1]: Listening on Device-mapper event daemon FIFOs.
Mar 09 06:33:04 ---- systemd[1]: Starting Delayed Shutdown Socket.
Mar 09 06:33:04 ---- systemd[1]: Listening on Delayed Shutdown Socket.
Mar 09 06:33:04 ---- systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
Mar 09 06:33:04 ---- systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
Mar 09 06:33:04 ---- systemd[1]: Starting LVM2 metadata daemon socket.
Mar 09 06:33:04 ---- systemd[1]: Listening on LVM2 metadata daemon socket.
Mar 09 06:33:04 ---- systemd[1]: Starting udev Kernel Socket.
Mar 09 06:33:04 ---- systemd[1]: Listening on udev Kernel Socket.
Mar 09 06:33:04 ---- systemd[1]: Starting udev Control Socket.
Mar 09 06:33:04 ---- systemd[1]: Listening on udev Control Socket.
Mar 09 06:33:04 ---- systemd[1]: Starting Journal Socket.
Mar 09 06:33:04 ---- systemd[1]: Listening on Journal Socket.
Mar 09 06:33:04 ---- systemd[1]: Starting System Slice.
Mar 09 06:33:04 ---- systemd[1]: Created slice System Slice.
Mar 09 06:33:04 ---- systemd[1]: Started File System Check on Root Device.
Mar 09 06:33:04 ---- systemd[1]: Starting system-systemd\x2dfsck.slice.
Mar 09 06:33:04 ---- systemd[1]: Created slice system-systemd\x2dfsck.slice.
Mar 09 06:33:04 ---- systemd[1]: Mounting Temporary Directory...
Mar 09 06:33:04 ---- systemd[1]: Starting system-netctl.slice.
Mar 09 06:33:04 ---- systemd[1]: Created slice system-netctl.slice.
Mar 09 06:33:04 ---- systemd[1]: Starting system-getty.slice.
Mar 09 06:33:04 ---- systemd[1]: Created slice system-getty.slice.
Mar 09 06:33:04 ---- systemd[1]: Started Set Up Additional Binary Formats.
Mar 09 06:33:04 ---- systemd[1]: Starting Load Kernel Modules...
Mar 09 06:33:04 ---- systemd[1]: Mounting Huge Pages File System...
Mar 09 06:33:04 ---- systemd[1]: Mounting Debug File System...
Mar 09 06:33:04 ---- systemd[1]: Starting Apply Kernel Variables...
Mar 09 06:33:04 ---- systemd[1]: Mounting POSIX Message Queue File System...
Mar 09 06:33:04 ---- systemd[1]: Starting udev Coldplug all Devices...
Mar 09 06:33:04 ---- systemd[1]: Starting Create list of required static device nodes for the current kernel...
Mar 09 06:33:04 ---- systemd[1]: Starting Setup Virtual Console...
Mar 09 06:33:04 ---- systemd[1]: Starting Journal Service...
Mar 09 06:33:04 ---- systemd[1]: Started Journal Service.
Mar 09 06:33:04 ---- kernel: EXT4-fs (sda1): re-mounted. Opts: data=ordered
Mar 09 06:33:04 ---- kernel: input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2
Mar 09 06:33:04 ---- kernel: ACPI: Power Button [PWRB]
Mar 09 06:33:04 ---- kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
Mar 09 06:33:04 ---- kernel: ACPI: Power Button [PWRF]
Mar 09 06:33:04 ---- kernel: AMD IOMMUv2 driver by Joerg Roedel <[email protected]>
Mar 09 06:33:04 ---- kernel: AMD IOMMUv2 functionality not available on this system
Mar 09 06:33:04 ---- systemd-journal[136]: Journal started
Mar 09 06:33:04 ---- systemd[1]: Starting Slices.
Mar 09 06:33:04 ---- systemd[1]: Reached target Slices.
Mar 09 06:33:04 ---- systemd[1]: Starting Remount Root and Kernel File Systems...
Mar 09 06:33:04 ---- systemd[1]: Started Apply Kernel Variables.
Mar 09 06:33:04 ---- systemd[1]: Started Setup Virtual Console.
Mar 09 06:33:04 ---- systemd[1]: Mounted Debug File System.
Mar 09 06:33:04 ---- systemd[1]: Mounted Huge Pages File System.
Mar 09 06:33:04 ---- systemd[1]: Started udev Coldplug all Devices.
Mar 09 06:33:04 ---- systemd[1]: Mounted POSIX Message Queue File System.
Mar 09 06:33:04 ---- systemd[1]: Mounted Temporary Directory.
Mar 09 06:33:04 ---- systemd[1]: Started Remount Root and Kernel File Systems.
Mar 09 06:33:04 ---- systemd[1]: Starting Create static device nodes in /dev...
Mar 09 06:33:04 ---- systemd[1]: Started Create static device nodes in /dev.
Mar 09 06:33:04 ---- systemd[1]: Starting udev Kernel Device Manager...
Mar 09 06:33:04 ---- systemd[1]: Starting Local File Systems (Pre).
Mar 09 06:33:04 ---- systemd[1]: Reached target Local File Systems (Pre).
Mar 09 06:33:04 ---- systemd[1]: Started udev Kernel Device Manager.
Mar 09 06:33:04 ---- systemd-udevd[150]: starting version 210
Mar 09 06:33:04 ---- kernel: fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
Mar 09 06:33:04 ---- kernel: Disabling lock debugging due to kernel taint
Mar 09 06:33:04 ---- systemd-modules-load[126]: Inserted module 'fglrx'
Mar 09 06:33:04 ---- kernel: <6>[fglrx] Maximum main memory to use for locked dma buffers: 11672 MBytes.
Mar 09 06:33:04 ---- kernel: <6>[fglrx] vendor: 1002 device: 6738 count: 1
Mar 09 06:33:04 ---- kernel: <6>[fglrx] ioport: bar 4, base 0xe000, size: 0x100
Mar 09 06:33:04 ---- kernel: <6>[fglrx] Kernel PAT support is enabled
Mar 09 06:33:04 ---- kernel: <6>[fglrx] module loaded - fglrx 13.25.5 [Dec 6 2013] with 1 minors
Mar 09 06:33:04 ---- systemd-modules-load[126]: Inserted module 'vboxdrv'
Mar 09 06:33:04 ---- systemd-modules-load[126]: Inserted module 'vboxnetadp'
Mar 09 06:33:04 ---- kernel: vboxdrv: Found 4 processor cores.
Mar 09 06:33:04 ---- kernel: vboxdrv: fAsync=0 offMin=0x179 offMax=0x32f1
Mar 09 06:33:04 ---- kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
Mar 09 06:33:04 ---- kernel: vboxdrv: Successfully loaded version 4.3.8_OSE (interface 0x001a0007).
Mar 09 06:33:04 ---- systemd-modules-load[126]: Inserted module 'vboxnetflt'
Mar 09 06:33:04 ---- systemd-modules-load[126]: Inserted module 'vboxpci'
Mar 09 06:33:04 ---- systemd[1]: Started Load Kernel Modules.
Mar 09 06:33:04 ---- systemd[1]: Mounted FUSE Control File System.
Mar 09 06:33:04 ---- systemd[1]: Mounting Configuration File System...
Mar 09 06:33:04 ---- kernel: vboxpci: IOMMU not found (not registered)
Mar 09 06:33:04 ---- systemd[1]: Mounted Configuration File System.
Mar 09 06:33:04 ---- kernel: ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20131115/utaddress-251)
Mar 09 06:33:04 ---- kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Mar 09 06:33:04 ---- kernel: ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPR2 1 (20131115/utaddress-251)
Mar 09 06:33:04 ---- kernel: ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 2 (20131115/utaddress-251)
Mar 09 06:33:04 ---- kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Mar 09 06:33:04 ---- kernel: ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPR2 1 (20131115/utaddress-251)
Mar 09 06:33:04 ---- kernel: ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 2 (20131115/utaddress-251)
Mar 09 06:33:04 ---- kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Mar 09 06:33:04 ---- kernel: lpc_ich: Resource confl -
Need Help Streaming Video From Web Server Built Into Application - Linksys WRT54g Router
Very much appreciate any help getting streaming video feed from web server built into video application to work properly using port forwarding on my Linksys WRT54g wireless router.
Here is the situation:
My PC is connected to the internet via a Linksys WRT54g wireless router.
The Windows XP Pro SP2 firewall is enabled, with a firewall exception established for the video camera application.
On the router, forwarding of port 80 is enabled for the LAN IP address of the PC running the video application with an embedded web server, and the web server in the video camera application is also set to use port 80.
I have a free DYNDNS account and also run the DYNDNS updater program on the PC running the video application with embedded web server. According to the DYNDNS web site and the DYNDNS updater program, the IP address assigned to the machine running the video application with embedded web server is set correctly in my dyndns account.
When I open a browser (Explorer or Firefox) on the PC running the video camera application with embedded web server, I am able to connect to the video application's web server by going to the dyndns address linked to the machine running the video application. The video application's web server is set to use the dyndns address. That's the good news. The bad news is that I can't connect to the video application's web server from any machine that connects to the internet that uses a router other than the router used by the PC running the video application. I am only able to connect to the streaming video from the application's web server only on machines that connect to the internet using the same (home) router used by the PC that is running the video application.
Since I am able to connect to the video app's embedded web server successfully on the machine running the video application, it seems that at least something about the current port forwarding settings is correct. For example, if I uncheck 'enable' for forwarding of port 80 on the router settings page, I am no longer able to connect to the video app's web server when I try to do so in a browser running on the machine running the video app. When I re-enable port 80 forwarding on the router, I am again able to connect to the web server of the video application on the machine running the video app. I thought that by enabling forwarding of port 80 on the router and associating that port with the LAN IP of the machine running the video application, it would be possible to connect to the streaming video of the video app's embedded web server from ANY machine connected to the internet, but that is not the case. There must be some other router settings to update/change in order to get the port forwarding working to enable a successful connection to the video web server, but I am stumped. Very grateful for any suggestions as to how to get this working properly.
Thanks in advance...The firewall log can be configured on the third tab in the window for the firewall settings, where you can turn the firewall on and off completely.
From your tests, though, it does not seem to be the firewall. However, to be sure, it would be good to check the log. It will help to eliminate the firewall as the culprit and you may find it handy in the future, too. ;-) Just don't forget to turn the log off again after you are done because it may cause some performance penalty on your system while on.
From what you write, it seems as if I should give a little networking background on the ip addresses you'll see. Your setup is (or should be) a modem connected to the WAN/Internet port of the WRT. The computer is connected into a LAN port of the WRT.
Your router has two IP addresses (that's what makes it a router): a WAN address and a LAN address. The WAN address is the address assigned by the ISP. It is a normal internet IP address. Everyone is able to send packets to this IP address. The WAN address is the one reported by whatismyipaddress.com, it should be listed in the dyndns record and it is the address that your router shows on the Status page. It's the public IP address of your router. Dyndns maps your dyndns.org name to that IP address.
Your router also has an IP address on the LAN side. You can configure it to be whatever you want. The default is 192.168.1.1 with netmask 255.255.255.0 and it is better to leave it like that or at least inside the network 192.168.*.*. 192.168 is a special, reserved IP address range for private networks. Basically, routers in the internet are not supposed to forward addresses in this range. That makes them suitable for private LANs as the packets never can get anywhere. Most people using Linksys routers have there LAN in 192.168.1.*.
The router acts as gateway, which means it forwards packets from PCs in the LAN to the internet and back. As all your PCs in your LAN share a single WAN IP address, the gateway does address translation (NAT). This works only in one direction: from the inside to the outside. The router remembers when a PC in your LAN sends something out and accepts the responses in and sending them back to the PC. If something comes in from the internet which cannot be associated with a ongoing communication the packet is dropped unless you use port forwarding.
All computers in your LAN either have a static IP address assigned or use DHCP to get it automatically. The router has a DHCP server as well which gives out IP address from 192.168.1.100-149 if not changed. With a router with default settings static IP addresses can be in the range of 192.168.1.2-99 and 150-254.
ipconfig /all reports your IP address in your LAN, i.e. an address 192.168.1.*. The gateway in this output should be 192.168.1.1 which is your router. And packet no in the LAN address range 192.168.1.* is send to the router which forwards the packets into the internet.
An address 192.168.1.* should not appear as internet address in the Status page of the router nor should it appear at dyndns.
Port forwarding is used to operate a server in the LAN. By default, a server in the LAN cannot be reached from the internet. You have to configure port forwarding for this. You configure that traffic bound for a specific port (e.g. TCP port 80 for http) on your WAN IP address is forwarded to the same port on a specific LAN IP address. If your server runs on 192.168.1.50 than traffic to your WAN IP address port 80 is forwarded to 192.168.1.50 port 80. That way your HTTP server can be reached from the internet. As you can only configure a fixed IP address in port forwarding it is recommended that the server uses a static IP address and not DHCP as in the latter case the IP address may change over time...
O.K. so much for networking. I hope that makes things a little clearer and you can verify that your setup is how it is intended to be.
I suggest the following: on the router's security page there is an option to block WAN requests. Remove the check if it is set (meaning: do not block). After you did that change you should be able to ping your WAN address (e.g. ping xxxx.dyndns.org) from the internet. That way we know that it is on the correct address.
Also on the Administration page make sure that remote management is disabled (should be like that per default) or that the management port is NOT 80 but for example 8080. What is your your UPnP settings on the same page?
O.K. that should be enough for the moment... -
On the iMac G4 can the processor be changed from 1000mhz to a 1024mhz?
On the iMac G4 can the processor be changed from 1000mhz to a 1024mhz?
It's an old iMac that my parents have and want to install a high seep (speed) Internet modem and it's requiring a 1024mhz
Ignore the requirement. 1000 is close enough to 1024 not to make a difference. They cannot be checking the speed anyway.
You may find youtub videos slow.
What version of mac os?
Here is how to find out what version of Mac OS you are running:
Click on the blue apple in the upper left hand of the screen.
click on this icon
Click on the first line, "About This Mac"
Most of these are numbers & that's what we want.
What version & Processor do you have?
You need 10.4 to get a relatively current web browser.
Opera
http://www.opera.com/browser/download/requirements/
http://www.opera.com/download/
OmniWeb 5.11, which, I believe is built on the same framework as Safari 5,
Safari 4.1.3 for Tiger
http://support.apple.com/kb/DL1069
iCab - The Taxi for the Internet
http://www.icab.de/
for PPC
tenfourfox
"World's most advanced web browser. Finely tuned for the Power PC."
http://www.floodgap.com/software/tenfourfox/
alternative download site:
http://www.macupdate.com/app/mac/37761/tenfourfox
What is my user agent?
http://whatsmyuseragent.com/
A larger list:
http://www.macmaps.com/browser.html -
Merging OSB changes from two projects
Good day,
We have two (or possibly more) projects working on OSB. There are some assets that will be modified by more than one project but due to scope and timelines, this work cannot happen on one version.
Is there a recommended way to merge changes from one branch of OSB assets to another branch of OSB assets? I know that under the hood it is just XML but treating the XML files as mergable assets without a tool like the Eclipse VCS support to help guide it seems like a recipe for problems.
How do others handle this issue?
Thanks,
SeanHi Sean,
There is really no tool to guide us to merge two versions of the osb code. As you mentioned, given that osb code is represented as an xml file, you can try to do a comparison between them and merge them manually, but if the changes done in the different branches are significantly different I would refrain from doing so.
#1 The best way is to let one team take the pain of redoing their changes on top of the other team's version.
#2 One stop-gap solution is to build the logic in two different local proxies (by each team) and then have a wrapper proxy that can invoke appropriate proxy based on some logic. But if the functionality built by both the teams is similar, then the above option #1 will be the best way to maintain the code.
Let us know in case of further issues/clarifications.
Thanks,
Patrick -
Any user complaints re: OS X Mavericks. Why change from OS X 10.8.5?
See many user complaints re: OS X Mavericks. Why change from OS X 10.8.5?
Reasons to upgrade:
Mavericks is flawless on my mac.
Mavericks seems faster than 10.8.
iBooks
iCloud keychain (big plus: my passwords now sync between OSX and iOS).
There are a few things to be aware of before you install it, though:
Any new OS has some bugs and incompatibilities with old software and hardware. If you are uncomfortable with basic Mac troubleshooting, then perhaps waiting would be a better strategy. However, I didn't have any software issues with installation or after.
If you have any mission-critical software or peripherals, make sure they are compatible first.
Mavericks does not play well with some old/bad software:
Crapware: anything that purports to "clean", "monitor", "protect", or "accelerate" your mac. Unnecessary on Macs and often harmful. Examples: CleanMyMac and MacKeeper (the King of Crapware).
antivirus software. Of dubious benefit on Macs.
"haxies": apps that change the appearance of the GUI.
The vast majority of disgruntled Mavericks-haters that post on this forum have crapware and antivirus software and other dreck on their macs that they are very reluctant to part with.
Mavericks does not play well with WD hard drives: this is because the software that comes on the drives, and the software that comes with the drives that WD wants you to install on your mac, and in some cases the firmware that is built into the enclosure of the external drive, are all incompatible with Mavericks. None of the software is necessary. If you have a WD drive, you should:
reformat (erase) it before you use it with a Mac
if you have installed WD software on your Mac, uninstall it. It's unnecessary anyway.
research it on line to see if it has the incompatible firmware on it. If it does, and you just bought it, I'd return it.
Before you install Mavericks, it's a good idea to:
have a good backup, like with Time Machine
make sure you have enough RAM. The specs say 2GB, but 4 is probably a more realistic minimum. If you do memory intensive work, you'll want more.
uninstall Crapware. This can be a problem because one of the hallmarks of crapware is that there is usually no uninstaller. It can also damage your OS and be difficult to uninstall completely. You may have to reformat (erase) your HD and do a clean install to completely get rid of it.
uninstall antivirus software and haxies.
repair your hard drive and permissions with Disk Utility
boot into safe mode, and then run the installer Mac OS X: What is Safe Boot, Safe Mode? -
Error when uploading "The bundle identifier cannot be changed from the previous version"
I have an app on the App Store created with DPS, Single Edition a long time ago, shortly after DPS SE became available. Now I've updated the app, built a new version with DPS App Builder, created a new version of the app in iTunes Connect, and tried to upload the Distribution zip file using application loader. I'm getting 2 error messages:
"This bundle is invalid. The bundle identifier cannot be changed from the previous version. If you want to change your bundle identifier, you will need to create a new application in iTunes Connect..."
and
"This app contains an embedded provisioning profile that is not associated with your account. Please use a provisioning profile associated with Team ID ..."
I've done this several times before with other apps, and never got these errors before. Any ideas of what is going on?
I'm able to view the developer ipa file just fine on my iPad.Nevermind. I left for lunch, returned, took a fresh look at it, and discovered that it was a stupid human error on my part.
-
[svn:osmf:] 11996: Updates and changes from the spec review for FMMLoader.
Revision: 11996
Revision: 11996
Author: [email protected]
Date: 2009-11-19 11:12:19 -0800 (Thu, 19 Nov 2009)
Log Message:
Updates and changes from the spec review for FMMLoader.
Modified Paths:
osmf/trunk/framework/MediaFramework/org/osmf/proxies/LoadableProxyElement.as
Added Paths:
osmf/trunk/framework/MediaFramework/org/osmf/net/FMMLoader.as
Removed Paths:
osmf/trunk/framework/MediaFramework/org/osmf/net/ManifestLoader.asHi
I've Updated App Builder, gone back to the DPS App Builder portal, regenerated new zip and ipa files and downloaded them.
I clicked the Application Loader 3.0 link, downloaded the latest Appication Version, clicked on the "Deliver your App" button, and submitted the newly built App that was built using 32.4.2 version. (All the app icons were listed as "stored on server" so I presume they are all ok). The .zip file appeared to 'deliver' to Apple successfully. I've tried to resubmit it but get ta "Redundant Binary Upload. There already exists a binary upload with build version..." error message, so presume the orginal binary upload was successful. I have no idea how I can get this app from the "prepare for submission", to "in review". The last time I thought I'd submitted this app I got as far as the "waiting for review" status, and no further.
At the moment I don't have a"+" button in the Build section - as mentioned on page 66 of Adobe's Step_by_step_guide_to_dps_se.pdf.
So I can't add the new .zip file to the iTunes Connect > My Apps portal in the Build section of the Versions tab.
I have put a support email into Apple, but don't expect a reply any day soon.
The problem with starting all the way back through the App wizard is that I really want to use all the same App Name, Bundle ID, and details etc.
Do you mean, going back to the Folio Producer Panel, and building a whole new App?
This process certainly isn't for the faint-hearted!
HELP! -
I bought a new lenovo B450 with window vista and it makes my set too slow and hangs always when I open few windows,kindly help me because I want to change from vista to window XP,tried but cannot
Coolsaint,
I assume you are talking about the B450 notebook...?
I think Herick offers good advice to first try to tune / optimize the Vista preload to see if you can get the performance you want out of it before reverting to XP.
If you do go the XP route, please note the SATA mode setting in BIOS Herick references.
After loading your XP version, you can go to this page on the support site to download all the XP drivers for the system and install all of them.
I recommend that you DO NOT change your partition sizes. If you just format and install to C: you can always start up with the One Key Recovery and recovery to the factory preload if XP turns out not to work well for you. If you remove the hidden system partition, OKR will no longer work and you won't be able to recover.
Best regards,
Mark
ThinkPads: S30, T43, X60t, X1, W700ds, IdeaPad Y710, IdeaCentre: A300, IdeaPad K1
Mark Hopkins
Program Manager, Lenovo Social Media (Services)
twitter @lenovoforums
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество -
Why did my sign in screen change from black to red?
For no obvious reason (which frustrates me the most out of any computer issue...) my computer sign in screen has changed from back to a pale red color. Though the computer still seems to be working properly *(except a bug change in iPhoto), I want to know if something bad is coming. People usually want to know why something they paid for is changing. Do I need to worry?
* iPhoto has decided to not import my new photos from my card and reader. It got started, and somewhere on the way sat there with nothing to show something was working.... the whirling thing or anything at all. When checking on it, by clicking on "eject" or trying to leave iPhoto, or even turn the computer off, it popped up a message saying to was still importing photos. It stayed like that for a day. I had to force quit but that's not an answer .What's going on? Can I trust importing photos again?Reset PRAM. http://support.apple.com/kb/PH18761
Start up in Safe Mode. http://support.apple.com/en-us/HT1564 -
Issue on payroll area which is changing from biweekly to monthly in Mid of
Dear Experts,
I have an issue on payroll area which is changing from biweekly to monthly in Mid of the Month.
One employee was retired on 29th of March, so his payroll area was changed from biweekly to monthly on 29th. For retire we are running the payroll on 8th of every month. When we are running payroll for April he has received only 29th and 30th retire salary, by the time he is not yet retired also.
In this case the main problem is monthly payroll time is early then biweekly. so the employee is getting retire salary then his regular pay.
Can you guide me where we can control that monthly payroll area should not be triggered at this movement.
Thanks
ChandraYou can do that but it is not that easy as it sounds if you have to do that over a period of say 10-20 years...lot of operational work!!
Also say if you load the retiree action one month ahead say on 03/01/2011. And the employee is retiring on 03/29.
Retire payroll is on 04/08
Biweekly is on 04/15
Now you decide to lock the employees after the 1st biweekly check of March...say which was process 14 days before 04/15 would be 04/01. The employee number is locked between 04/01 to 04/15. For 14 days you have locked these employees!!
What happens if there is adjustment pay...you have to manually go and unlock the employee and lock him after the adjustment check.
I will let you decide based on the comfort, SAP effort, Operational effort and system maintenance. -
When I share a pages document as a PDF (via e-mail) all the pictures change from the original document, most are missing with just a few of them repeated in the spots where others had been. How do I do this without the document changing?
I need to be able to send it to a PC in order to print it.Hard to say what is happening without examining the file.
If you like click on my blue name and email me both the .pages file and the the .pdf you have made from it.
Peter
ps It would help to say what version of Pages you are using and on what you are running it. iOS or Mac and what version. -
TS3899 I changed from an Iphone to a Android. I can't get my email from other Iphones
I changed from an Iphone to a Android. Now I can't recieve emails from other Iphones.
Email should not be a problem, text messages can be but not email if it is set up correctly on your new phone.
Maybe you are looking for
-
10.9.4 broke this xattr command. Can someone help?
I've used the following automator command for a while now. I keep all my files on my main system with tags. I wanted a command to save a copy of any folder/file to my OneDrive folder and overwrite existing files but this resulted in duplicate tags
-
Regarding downlaod the output from ALV grid format
Hi i want to download the output ALV grid format into excel sheet . but condition is when ever user press the button (&ZDL) the should be downloaded. and also how to convert the output into CSV format.
-
Login(user ID and Password) to my VI
Hello, Iam creating a vi with some parameters...........My VI consists of Tabs, now in home page user should enter user name and password...........and if it is success then the VI should give acess to all tabs......otherwise it should display that w
-
Creating a photo slide shome with music and text and export to dvd
Hello I am a newbie on this so I would need a lot of help I would like to create a presentetion DVD for my town. The idea is a slide show of photos with some music and after a set of photos a screen with text displaying infos about the city or the si
-
Drill down problem when using union all combination
Hi All, I have a simple report with a drill down. The report has three columns Region, Sales, Flag... which will drill down to detail level of sales. The Flag column has Y, N values and we added 'All' Value in flag so that the user can select Y, N an