Udev and rebuilding kernal

hi, i just installed arch for the fouth time. I am trying out different ways to run the kernal. I have ide, but no raid or sata, so I removed the ones that i do not need, but now when i boot it does not mount the drive and i cant get to root. i need to rebuild the kernal but i dont know how.
also there is a big lag starting udev uevents. i tried puting pci=conf1 and then pci=nobios at the kernal line but they do not stop the lag. i cant find a solve at this board.

You know, if you don't know what you're doing with this, you should probably either NOT be messing with it, or at least know how to debug things.
For starters, your mkinitcpio image has "base udev ide". This is fine, but if you're trying to minimize modules, you did just the opposite:
$ mkinitcpio -H autodetect
Help for hook 'autodetect':
This hook shrinks your initramdisk to a smaller size
by autodetecting your needed modules. Be sure to verify
included modules are correct and none are missing.
This hook must be run before other subsystem hooks in
order to take advantage of auto-detection. Any hooks
placed before 'autodetect' will be installed in full.
In addition, you removed the filesystems hook, so there are no filesystems there, and thus they can't be mounted
$ mkinitcpio -H filesystems
Help for hook 'filesystems':
This hook is responsible for loading filesystems for the root device.
Detection will be done at runtime. If you would like to minimize the
modules installed in the image, add the autodetect hook too.
Further more, if you REALLY want to minimize the set of modules and the hooks in mkinitcpio, the config file /etc/mkinicpio.conf actually explains what to do:
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
Now, after all this is said and done, I'm still going to recommend you do not edit this image and use the default. This is boot you're messing with and if you don't know what's going on under the hood, you have the potential to make your machine unbootable.

Similar Messages

  • Filesystem Error (UDev and mounting)

    I'm having trouble with my filesystem(s) on startup. These problems began after I cleaned my case using compressed air / vacuum, though I don't think I jostled any hardware. My original filesystem was set up like this:
    /dev/sda1 NTFS WinXP partition
    /dev/sda2 XFS /var
    /dev/sda3 EXT3 root
    /dev/sda4 extended
    /dev/sda5 EXT3 /home
    /dev/sda6 swap
    /dev/sdb1 XFS /digitalmedia
    On startup, UDev starts and Modules are loaded, then I make it to:
    :: Checking Filesystems [BUSY]
    /dev/sda3: clean, 87750/977280 files, 668803/3905803 blocks
    /dev/sda5 is mounted. e2fsck: Cannot continue, aborting.
    /sbin/fsck.xfs: XFS file system. [FAIL]
    *** FILESYSTEM CHECK FAILED ***
    * Please repair manually and reboot *
    <snip>
    If I log in as root, /proc/mounts contains this:
    rootfs / rootfs rw 0 0
    proc /proc prox rw,relatime 0 0
    sys /sys sysfs rw,relatime 0 0
    udev /dev devtmpfs rw,nosuid,relatime,size=10240k,nr_inodes=256615,mode=755 0 0
    /dev/disk/by-uuid/dc4661ec-06bf-46a7-ac7d-ba183f39f402 / ext3 ro,noatime,errors=continue,barrier=0,data=writeback 0 0
    /dev/sdb1 /media/usbhd-sdb1 xfs rw,relatime,attr2,noquota 0 0
    /dev/sda5 /media/usbhd-sda5 ext3 rw,relatime,errors=continue,barrier=0,data=writeback 0 0
    /dev/sda1 /media/usbhd-sda1 ntfs ro,relatime,uid=0,gid=100,umask=02,nls=utf8,errors=continue,mft_zone_multiplier=1 0 0
    /dev/sda2 /media/usbhd-sda2 xfs rw,relatime,attr2,noquota 0 0
    As you can see, 4 partitions are mounted under /media/* instead of their appropriate locations. At this point, I rebooted to SystemRescue LiveCD and issued e2fsck -f commands for the (unmounted) EXT3 partitions:
    root@sysresccd /proc % e2fsck -f /dev/sda3
    e2fsck 1.41.12 (17-May-2010)
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    /dev/sda3: 87750/977280 files (1.0% non-contiguous), 668803/3905803 blocks
    root@sysresccd /proc % e2fsck -f /dev/sda5
    e2fsck 1.41.12 (17-May-2010)
    Superblock last mount time is in the future.
    (by less than a day, probably due to the hardware clock being
    incorrectly set) Fix<y>? yes
    Superblock last write time is in the future.
    (by less than a day, probably due to the hardware clock being
    incorrectly set). Fix<y>? yes
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    /dev/sda5: ***** FILE SYSTEM WAS MODIFIED *****
    /dev/sda5: 7092/2564096 files (7.1% non-contiguous), 3262832/10253478 blocks
    as well as xfs_check and xfs_repair commands for the (unmounted) XFS partitions:
    root@sysresccd /proc % xfs_check /dev/sda2
    root@sysresccd /proc % xfs_check /dev/sdb1
    root@sysresccd /proc % xfs_repair /dev/sda2
    Phase 1 - find and verify superblock...
    Phase 2 - using internal log
    - zero log...
    - scan filesystem freespace and inode maps...
    - found root inode chunk
    Phase 3 - for each AG...
    - scan and clear agi unlinked lists...
    - process known inodes and perform inode discovery...
    - agno = 0
    - agno = 1
    - agno = 2
    - agno = 3
    - process newly discovered inodes...
    Phase 4 - check for duplicate blocks...
    - setting up duplicate extent list...
    - check for inodes claiming duplicate blocks...
    - agno = 0
    - agno = 2
    - agno = 1
    - agno = 3
    Phase 5 - rebuild AG headers and trees...
    - reset superblock...
    Phase 6 - check inode connectivity...
    - resetting contents of realtime bitmap and summary inodes
    - traversing filesystem ...
    - traversal finished ...
    - moving disconnected inodes to lost+found ...
    Phase 7 - verify and correct link counts...
    done
    root@sysresccd /proc % xfs_repair /dev/sdb1
    Phase 1 - find and verify superblock...
    Phase 2 - using internal log
    - zero log...
    - scan filesystem freespace and inode maps...
    - found root inode chunk
    Phase 3 - for each AG...
    - scan and clear agi unlinked lists...
    - process known inodes and perform inode discovery...
    - agno = 0
    - agno = 1
    - agno = 2
    - agno = 3
    - process newly discovered inodes...
    Phase 4 - check for duplicate blocks...
    - setting up duplicate extent list...
    - check for inodes claiming duplicate blocks...
    - agno = 1
    - agno = 0
    - agno = 2
    - agno = 3
    Phase 5 - rebuild AG headers and trees...
    - reset superblock...
    Phase 6 - check inode connectivity...
    - resetting contents of realtime bitmap and summary inodes
    - traversing filesystem ...
    - traversal finished ...
    - moving disconnected inodes to lost+found ...
    Phase 7 - verify and correct link counts...
    done
    root@sysresccd /proc %
    but that doesn't seem to help. I went back to check if the UUIDs in fstab were correct, and they appear to be. Here's fstab:
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    devpts /dev/pts devpts defaults 0 0
    shm /dev/shm tmpfs nodev,nosuid 0 0
    #/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
    #/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
    #/dev/fd0 /media/fl auto user,noauto 0 0
    UUID=216defa9-66be-4a21-940a-2899111b6f9a swap swap defaults 0 0
    UUID=8c0d304b-8c4d-4d8d-a60b-0a2e08dbfd2c /home ext3 defaults,noatime 0 1
    UUID=dc4661ec-06bf-46a7-ac7d-ba183f39f402 / ext3 defaults,noatime 0 1
    UUID=e09984c8-9f9f-46f9-a1c7-e4b5ed6ea1c0 /var xfs defaults 0 1
    #UUID=130a944d-1094-4cde-9af3-90a840290698 /digitalmedia xfs defaults,noatime 000 1
    #UUID=F0D8093AD8090098 /winxp NTFS defaults,noatime 0 0
    And here's the output for fdisk-l, mount, and dmesg:
    Disk /dev/sda: 320.1 GB, 320072933376 bytes
    255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x3f353f35
    Device Boot Start End Blocks Id System
    /dev/sda1 * 63 152151614 76075776 7 HPFS/NTFS
    /dev/sda2 152151615 503718074 175783230 83 Linux
    /dev/sda3 503718075 534964499 15623212+ 83 Linux
    /dev/sda4 534964500 625137344 45086422+ 5 Extended
    /dev/sda5 534964563 616992389 41013913+ 83 Linux
    /dev/sda6 616992453 625137344 4072446 82 Linux swap / Solaris
    Disk /dev/sdb: 640.1 GB, 640135028736 bytes
    255 heads, 63 sectors/track, 77825 cylinders, total 1250263728 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x0005007d
    Device Boot Start End Blocks Id System
    /dev/sdb1 63 1250258624 625129281 83 Linux
    mount
    proc on /proc type proc (rw,relatime)
    sys on /sys type sysfs (rw,relatime)
    udev on /dev type devtmpfs (rw,nosuid,relatime,size=10240k,nr_inodes=256615,mode=755)
    /dev/disk/by-uuid/dc4661ec-06bf-46a7-ac7d-ba183f39f402 on / type ext3 (rw,noatime,errors=continue,barrier=0,data=writeback)
    shm on /dev/shm type tmpfs (rw,nosuid,nodev)
    fusectl on /sys/fs/fuse/connections type fusectl (rw)
    /dev/sda3 on /media/usbhd-sda3 type ext3 (rw,relatime)
    /dev/sdb1 on /media/usbhd-sdb1 type xfs (rw,relatime)
    /dev/sda1 on /media/usbhd-sda1 type ntfs (ro,relatime,utf8,gid=100,umask=002)
    /dev/sda5 on /media/usbhd-sda5 type ext3 (rw,relatime)
    /dev/sda2 on /media/usbhd-sda2 type xfs (rw,relatime)
    mount: warning: /etc/mtab is not writable (e.g. read-only filesystem).
    It's possible that information reported by mount(8) is not
    up to date. For actual information about system mount points
    check the /proc/mounts file
    dmesg
    Initializing cgroup subsys cpuset
    Initializing cgroup subsys cpu
    Linux version 2.6.36-ARCH (tobias@T-POWA-LX) (gcc version 4.5.1 20101125 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Dec 10 20:32:37 CET 2010
    Command line: root=/dev/disk/by-uuid/dc4661ec-06bf-46a7-ac7d-ba183f39f402 ro vga=773
    BIOS-provided physical RAM map:
    BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
    BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
    BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
    BIOS-e820: 0000000000100000 - 000000007fee0000 (usable)
    BIOS-e820: 000000007fee0000 - 000000007fee3000 (ACPI NVS)
    BIOS-e820: 000000007fee3000 - 000000007fef0000 (ACPI data)
    BIOS-e820: 000000007fef0000 - 000000007ff00000 (reserved)
    BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
    BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
    NX (Execute Disable) protection: active
    DMI 2.5 present.
    Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
    e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
    e820 update range: 0000000000000000 - 0000000000001000 (usable) ==> (reserved)
    e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
    No AGP bridge found
    last_pfn = 0x7fee0 max_arch_pfn = 0x400000000
    MTRR default type: uncachable
    MTRR fixed ranges enabled:
    00000-9FFFF write-back
    A0000-BFFFF uncachable
    C0000-CCFFF write-protect
    CD000-EFFFF uncachable
    F0000-FFFFF write-through
    MTRR variable ranges enabled:
    0 base 000000000 mask F80000000 write-back
    1 base 07FF00000 mask FFFF00000 uncachable
    2 disabled
    3 disabled
    4 disabled
    5 disabled
    6 disabled
    7 disabled
    x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Scanning 0 areas for low memory corruption
    modified physical RAM map:
    modified: 0000000000000000 - 0000000000010000 (reserved)
    modified: 0000000000010000 - 000000000009f400 (usable)
    modified: 000000000009f400 - 00000000000a0000 (reserved)
    modified: 00000000000f0000 - 0000000000100000 (reserved)
    modified: 0000000000100000 - 000000007fee0000 (usable)
    modified: 000000007fee0000 - 000000007fee3000 (ACPI NVS)
    modified: 000000007fee3000 - 000000007fef0000 (ACPI data)
    modified: 000000007fef0000 - 000000007ff00000 (reserved)
    modified: 00000000e0000000 - 00000000f0000000 (reserved)
    modified: 00000000fec00000 - 0000000100000000 (reserved)
    initial memory mapped : 0 - 20000000
    found SMP MP-table at [ffff8800000f39f0] f39f0
    init_memory_mapping: 0000000000000000-000000007fee0000
    0000000000 - 007fe00000 page 2M
    007fe00000 - 007fee0000 page 4k
    kernel direct mapping tables up to 7fee0000 @ 16000-1a000
    RAMDISK: 37e02000 - 37ff0000
    ACPI: RSDP 00000000000f7970 00014 (v00 IntelR)
    ACPI: RSDT 000000007fee3000 00034 (v01 IntelR AWRDACPI 42302E31 AWRD 00000000)
    ACPI: FACP 000000007fee3080 00074 (v01 IntelR AWRDACPI 42302E31 AWRD 00000000)
    ACPI: DSDT 000000007fee3100 04EC3 (v01 INTELR AWRDACPI 00001000 MSFT 0100000E)
    ACPI: FACS 000000007fee0000 00040
    ACPI: MCFG 000000007fee80c0 0003C (v01 IntelR AWRDACPI 42302E31 AWRD 00000000)
    ACPI: APIC 000000007fee8000 00084 (v01 IntelR AWRDACPI 42302E31 AWRD 00000000)
    ACPI: SSDT 000000007fee8a20 00380 (v01 PmRef CpuPm 00003000 INTL 20041203)
    ACPI: Local APIC address 0xfee00000
    [ffffea0000000000-ffffea0001bfffff] PMD -> [ffff880002000000-ffff880003bfffff] on node 0
    Zone PFN ranges:
    DMA 0x00000010 -> 0x00001000
    DMA32 0x00001000 -> 0x00100000
    Normal empty
    Movable zone start PFN for each node
    early_node_map[2] active PFN ranges
    0: 0x00000010 -> 0x0000009f
    0: 0x00000100 -> 0x0007fee0
    On node 0 totalpages: 523887
    DMA zone: 56 pages used for memmap
    DMA zone: 0 pages reserved
    DMA zone: 3927 pages, LIFO batch:0
    DMA32 zone: 7109 pages used for memmap
    DMA32 zone: 512795 pages, LIFO batch:31
    ACPI: PM-Timer IO Port: 0x408
    ACPI: Local APIC address 0xfee00000
    ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
    ACPI: LAPIC (acpi_id[0x01] lapic_id[0x03] enabled)
    ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
    ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
    ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
    ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
    ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
    ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
    ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
    IOAPIC[0]: apic_id 4, version 32, address 0xfec00000, GSI 0-23
    ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    ACPI: IRQ0 used by override.
    ACPI: IRQ2 used by override.
    ACPI: IRQ9 used by override.
    Using ACPI (MADT) for SMP configuration information
    SMP: Allowing 4 CPUs, 0 hotplug CPUs
    nr_irqs_gsi: 40
    early_res array is doubled to 64 at [18180 - 1897f]
    PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
    PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
    Allocating PCI resources starting at 7ff00000 (gap: 7ff00000:60100000)
    Booting paravirtualized kernel on bare hardware
    setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1
    PERCPU: Embedded 28 pages/cpu @ffff880001a00000 s86016 r8192 d20480 u524288
    pcpu-alloc: s86016 r8192 d20480 u524288 alloc=1*2097152
    pcpu-alloc: [0] 0 1 2 3
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 516722
    Kernel command line: root=/dev/disk/by-uuid/dc4661ec-06bf-46a7-ac7d-ba183f39f402 ro vga=773
    PID hash table entries: 4096 (order: 3, 32768 bytes)
    Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
    Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
    Checking aperture...
    No AGP bridge found
    Calgary: detecting Calgary via BIOS EBDA area
    Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    Subtract (48 early reservations)
    #1 [0001000000 - 00017fb9a8] TEXT DATA BSS
    #2 [0037e02000 - 0037ff0000] RAMDISK
    #3 [00017fc000 - 00017fc0ee] BRK
    #4 [00000f3a00 - 0000100000] BIOS reserved
    #5 [00000f39f0 - 00000f3a00] MP-table mpf
    #6 [000009ec00 - 00000f20d4] BIOS reserved
    #7 [00000f22a8 - 00000f39f0] BIOS reserved
    #8 [00000f20d4 - 00000f22a8] MP-table mpc
    #9 [0000010000 - 0000012000] TRAMPOLINE
    #10 [0000012000 - 0000016000] ACPI WAKEUP
    #11 [0000016000 - 0000018000] PGTABLE
    #12 [00017fc100 - 00017fd100] BOOTMEM
    #13 [0000018000 - 0000018180] BOOTMEM
    #14 [0001ffe000 - 0001fff000] BOOTMEM
    #15 [0001fff000 - 0002000000] BOOTMEM
    #16 [0002000000 - 0003c00000] MEMMAP 0
    #17 [00017fd100 - 0001815100] BOOTMEM
    #18 [0001815100 - 000182d100] BOOTMEM
    #19 [000182e000 - 000182f000] BOOTMEM
    #20 [00017fb9c0 - 00017fba03] BOOTMEM
    #21 [00017fba40 - 00017fbc70] BOOTMEM
    #22 [00017fbc80 - 00017fbce8] BOOTMEM
    #23 [00017fbd00 - 00017fbd68] BOOTMEM
    #24 [00017fbd80 - 00017fbde8] BOOTMEM
    #25 [00017fbe00 - 00017fbe68] BOOTMEM
    #26 [00017fbe80 - 00017fbee8] BOOTMEM
    #27 [00017fbf00 - 00017fbf68] BOOTMEM
    #28 [00017fbf80 - 00017fbfe8] BOOTMEM
    #29 [000182d100 - 000182d168] BOOTMEM
    #30 [000182d180 - 000182d1e8] BOOTMEM
    #31 [000182d200 - 000182d220] BOOTMEM
    #32 [000182d240 - 000182d287] BOOTMEM
    #33 [000182d2c0 - 000182d307] BOOTMEM
    #34 [0001a00000 - 0001a1c000] BOOTMEM
    #35 [0001a80000 - 0001a9c000] BOOTMEM
    #36 [0001b00000 - 0001b1c000] BOOTMEM
    #37 [0001b80000 - 0001b9c000] BOOTMEM
    #38 [000182d340 - 000182d348] BOOTMEM
    #39 [000182d380 - 000182d388] BOOTMEM
    #40 [000182d3c0 - 000182d3d0] BOOTMEM
    #41 [000182d400 - 000182d420] BOOTMEM
    #42 [000182d440 - 000182d570] BOOTMEM
    #43 [000182d580 - 000182d5d0] BOOTMEM
    #44 [000182d600 - 000182d650] BOOTMEM
    #45 [000182f000 - 0001837000] BOOTMEM
    #46 [0001b9c000 - 0001d9c000] BOOTMEM
    #47 [0001837000 - 0001937000] BOOTMEM
    Memory: 2052920k/2096000k available (3685k kernel code, 452k absent, 42628k reserved, 2089k data, 504k init)
    SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
    Hierarchical RCU implementation.
    RCU-based detection of stalled CPUs is disabled.
    Verbose stalled-CPUs detection is disabled.
    NR_IRQS:2304
    Console: colour dummy device 80x25
    console [tty0] enabled
    allocated 20971520 bytes of page_cgroup
    please try 'cgroup_disable=memory' option if you don't want memory cgroups
    Fast TSC calibration using PIT
    Detected 2550.007 MHz processor.
    Calibrating delay loop (skipped), value calculated using timer frequency.. 5102.51 BogoMIPS (lpj=8500023)
    pid_max: default: 32768 minimum: 301
    Security Framework initialized
    TOMOYO Linux initialized
    AppArmor: AppArmor disabled by boot time parameter
    Mount-cache hash table entries: 256
    Initializing cgroup subsys ns
    Initializing cgroup subsys cpuacct
    Initializing cgroup subsys memory
    Initializing cgroup subsys devices
    Initializing cgroup subsys freezer
    Initializing cgroup subsys net_cls
    Initializing cgroup subsys blkio
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 0
    mce: CPU supports 6 MCE banks
    CPU0: Thermal monitoring enabled (TM2)
    using mwait in idle threads.
    Performance Events: PEBS fmt0+, Core2 events, Intel PMU driver.
    ... version: 2
    ... bit width: 40
    ... generic registers: 2
    ... value mask: 000000ffffffffff
    ... max period: 000000007fffffff
    ... fixed-purpose events: 3
    ... event mask: 0000000700000003
    ACPI: Core revision 20100702
    Setting APIC routing to flat
    ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    CPU0: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz stepping 07
    NMI watchdog enabled, takes one hw-pmu counter.
    Booting Node 0, Processors #1
    NMI watchdog enabled, takes one hw-pmu counter.
    #2
    NMI watchdog enabled, takes one hw-pmu counter.
    #3 Ok.
    NMI watchdog enabled, takes one hw-pmu counter.
    Brought up 4 CPUs
    Total of 4 processors activated (20407.98 BogoMIPS).
    devtmpfs: initialized
    NET: Registered protocol family 16
    ACPI: bus type pci registered
    PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
    PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
    PCI: Using configuration type 1 for base access
    bio: create slab <bio-0> at 0
    ACPI: EC: Look up EC in DSDT
    ACPI: SSDT 000000007fee8140 0022A (v01 PmRef Cpu0Ist 00003000 INTL 20041203)
    ACPI: Dynamic OEM Table Load:
    ACPI: SSDT (null) 0022A (v01 PmRef Cpu0Ist 00003000 INTL 20041203)
    ACPI: SSDT 000000007fee8600 00152 (v01 PmRef Cpu1Ist 00003000 INTL 20041203)
    ACPI: Dynamic OEM Table Load:
    ACPI: SSDT (null) 00152 (v01 PmRef Cpu1Ist 00003000 INTL 20041203)
    ACPI: SSDT 000000007fee8760 00152 (v01 PmRef Cpu2Ist 00003000 INTL 20041203)
    ACPI: Dynamic OEM Table Load:
    ACPI: SSDT (null) 00152 (v01 PmRef Cpu2Ist 00003000 INTL 20041203)
    ACPI: SSDT 000000007fee88c0 00152 (v01 PmRef Cpu3Ist 00003000 INTL 20041203)
    ACPI: Dynamic OEM Table Load:
    ACPI: SSDT (null) 00152 (v01 PmRef Cpu3Ist 00003000 INTL 20041203)
    ACPI: Interpreter enabled
    ACPI: (supports S0 S3 S4 S5)
    ACPI: Using IOAPIC for interrupt routing
    ACPI: No dock devices found.
    PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
    pci_root PNP0A08:00: host bridge window [io 0x0000-0x0cf7]
    pci_root PNP0A08:00: host bridge window [io 0x0d00-0xffff]
    pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff]
    pci_root PNP0A08:00: host bridge window [mem 0x000c0000-0x000dffff]
    pci_root PNP0A08:00: host bridge window [mem 0x7ff00000-0xfebfffff]
    pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:01.0: PME# disabled
    pci 0000:00:1a.0: reg 20: [io 0xff00-0xff1f]
    pci 0000:00:1a.1: reg 20: [io 0xfe00-0xfe1f]
    pci 0000:00:1a.2: reg 20: [io 0xfd00-0xfd1f]
    pci 0000:00:1a.7: reg 10: [mem 0xfdfff000-0xfdfff3ff]
    pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
    pci 0000:00:1a.7: PME# disabled
    pci 0000:00:1b.0: reg 10: [mem 0xfdff8000-0xfdffbfff 64bit]
    pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:1b.0: PME# disabled
    pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:1c.0: PME# disabled
    pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    pci 0000:00:1c.1: PME# disabled
    pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
    pci 0000:00:1c.2: PME# disabled
    pci 0000:00:1d.0: reg 20: [io 0xfc00-0xfc1f]
    pci 0000:00:1d.1: reg 20: [io 0xfb00-0xfb1f]
    pci 0000:00:1d.2: reg 20: [io 0xfa00-0xfa1f]
    pci 0000:00:1d.7: reg 10: [mem 0xfdffe000-0xfdffe3ff]
    pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
    pci 0000:00:1d.7: PME# disabled
    pci 0000:00:1f.0: quirk: [io 0x0400-0x047f] claimed by ICH6 ACPI/GPIO/TCO
    pci 0000:00:1f.0: quirk: [io 0x0480-0x04bf] claimed by ICH6 GPIO
    pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0290 (mask 0007)
    pci 0000:00:1f.2: reg 10: [io 0xf900-0xf907]
    pci 0000:00:1f.2: reg 14: [io 0xf800-0xf803]
    pci 0000:00:1f.2: reg 18: [io 0xf700-0xf707]
    pci 0000:00:1f.2: reg 1c: [io 0xf600-0xf603]
    pci 0000:00:1f.2: reg 20: [io 0xf500-0xf50f]
    pci 0000:00:1f.2: reg 24: [io 0xf400-0xf40f]
    pci 0000:00:1f.3: reg 10: [mem 0xfdffd000-0xfdffd0ff 64bit]
    pci 0000:00:1f.3: reg 20: [io 0x0500-0x051f]
    pci 0000:00:1f.5: reg 10: [io 0xf200-0xf207]
    pci 0000:00:1f.5: reg 14: [io 0xf100-0xf103]
    pci 0000:00:1f.5: reg 18: [io 0xf000-0xf007]
    pci 0000:00:1f.5: reg 1c: [io 0xef00-0xef03]
    pci 0000:00:1f.5: reg 20: [io 0xee00-0xee0f]
    pci 0000:00:1f.5: reg 24: [io 0xed00-0xed0f]
    pci 0000:01:00.0: reg 10: [mem 0xfa000000-0xfaffffff]
    pci 0000:01:00.0: reg 14: [mem 0xd0000000-0xdfffffff 64bit pref]
    pci 0000:01:00.0: reg 1c: [mem 0xf8000000-0xf9ffffff 64bit]
    pci 0000:01:00.0: reg 24: [io 0xaf00-0xaf7f]
    pci 0000:01:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
    pci 0000:00:01.0: PCI bridge to [bus 01-01]
    pci 0000:00:01.0: bridge window [io 0xa000-0xafff]
    pci 0000:00:01.0: bridge window [mem 0xf8000000-0xfbffffff]
    pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
    pci 0000:00:1c.0: PCI bridge to [bus 02-02]
    pci 0000:00:1c.0: bridge window [io 0x9000-0x9fff]
    pci 0000:00:1c.0: bridge window [mem 0xfdb00000-0xfdbfffff]
    pci 0000:00:1c.0: bridge window [mem 0xfd900000-0xfd9fffff 64bit pref]
    pci 0000:03:00.0: reg 10: [io 0xdf00-0xdf07]
    pci 0000:03:00.0: reg 14: [io 0xde00-0xde03]
    pci 0000:03:00.0: reg 18: [io 0xdd00-0xdd07]
    pci 0000:03:00.0: reg 1c: [io 0xdc00-0xdc03]
    pci 0000:03:00.0: reg 20: [io 0xdb00-0xdb0f]
    pci 0000:03:00.0: reg 30: [mem 0x00000000-0x0000ffff pref]
    pci 0000:03:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
    pci 0000:00:1c.1: PCI bridge to [bus 03-03]
    pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
    pci 0000:00:1c.1: bridge window [mem 0xfd800000-0xfd8fffff]
    pci 0000:00:1c.1: bridge window [mem 0xfde00000-0xfdefffff 64bit pref]
    pci 0000:04:00.0: reg 10: [mem 0xfddfc000-0xfddfffff 64bit]
    pci 0000:04:00.0: reg 18: [io 0xbe00-0xbeff]
    pci 0000:04:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
    pci 0000:04:00.0: supports D1 D2
    pci 0000:04:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:04:00.0: PME# disabled
    pci 0000:00:1c.2: PCI bridge to [bus 04-04]
    pci 0000:00:1c.2: bridge window [io 0xb000-0xbfff]
    pci 0000:00:1c.2: bridge window [mem 0xfdd00000-0xfddfffff]
    pci 0000:00:1c.2: bridge window [mem 0xfdc00000-0xfdcfffff 64bit pref]
    pci 0000:05:03.0: reg 10: [mem 0xfdae0000-0xfdaeffff]
    pci 0000:05:03.0: reg 14: [io 0xcf00-0xcf1f]
    pci 0000:05:04.0: reg 10: [mem 0xf4000000-0xf7ffffff pref]
    pci 0000:05:05.0: reg 10: [mem 0xfdaff000-0xfdafffff]
    pci 0000:05:05.0: supports D1 D2
    pci 0000:05:05.0: PME# supported from D0 D1 D2 D3hot
    pci 0000:05:05.0: PME# disabled
    pci 0000:00:1e.0: PCI bridge to [bus 05-05] (subtractive decode)
    pci 0000:00:1e.0: bridge window [io 0xc000-0xcfff]
    pci 0000:00:1e.0: bridge window [mem 0xfda00000-0xfdafffff]
    pci 0000:00:1e.0: bridge window [mem 0xf4000000-0xf7ffffff 64bit pref]
    pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
    pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
    pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
    pci 0000:00:1e.0: bridge window [mem 0x000c0000-0x000dffff] (subtractive decode)
    pci 0000:00:1e.0: bridge window [mem 0x7ff00000-0xfebfffff] (subtractive decode)
    pci_bus 0000:00: on NUMA node 0
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX2._PRT]
    ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
    ACPI: PCI Interrupt Link [LNKA] (IRQs *3 4 5 7 9 10 11 12)
    ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 7 9 *10 11 12)
    ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 7 9 10 11 12)
    ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 7 9 10 *11 12)
    ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 10 11 12) *0, disabled.
    ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 *7 9 10 11 12)
    ACPI: PCI Interrupt Link [LNK0] (IRQs 3 *4 5 7 9 10 11 12)
    ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 7 9 10 *11 12)
    HEST: Table is not found!
    vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
    vgaarb: loaded
    PCI: Using ACPI for IRQ routing
    PCI: pci_cache_line_size set to 64 bytes
    reserve RAM buffer: 000000000009f400 - 000000000009ffff
    reserve RAM buffer: 000000007fee0000 - 000000007fffffff
    NetLabel: Initializing
    NetLabel: domain hash size = 128
    NetLabel: protocols = UNLABELED CIPSOv4
    NetLabel: unlabeled traffic allowed by default
    Switching to clocksource tsc
    pnp: PnP ACPI init
    ACPI: bus type pnp registered
    pnp: PnP ACPI: found 11 devices
    ACPI: ACPI bus type pnp unregistered
    system 00:01: [io 0x04d0-0x04d1] has been reserved
    system 00:01: [io 0x0290-0x030f] has been reserved
    system 00:01: [io 0x0880-0x088f] has been reserved
    system 00:07: [io 0x0400-0x04bf] could not be reserved
    system 00:09: [mem 0xe0000000-0xefffffff] has been reserved
    system 00:0a: [mem 0x000f0000-0x000fffff] could not be reserved
    system 00:0a: [mem 0x7ff00000-0x7fffffff] has been reserved
    system 00:0a: [mem 0x7fee0000-0x7fefffff] could not be reserved
    system 00:0a: [mem 0x00000000-0x0009ffff] could not be reserved
    system 00:0a: [mem 0x00100000-0x7fedffff] could not be reserved
    system 00:0a: [mem 0xfec00000-0xfec00fff] could not be reserved
    system 00:0a: [mem 0xfed14000-0xfed1dfff] has been reserved
    system 00:0a: [mem 0xfed20000-0xfed9ffff] has been reserved
    system 00:0a: [mem 0xfee00000-0xfee00fff] has been reserved
    system 00:0a: [mem 0xffb00000-0xffb7ffff] has been reserved
    system 00:0a: [mem 0xfff00000-0xffffffff] has been reserved
    system 00:0a: [mem 0x000e0000-0x000effff] has been reserved
    pci 0000:01:00.0: BAR 6: assigned [mem 0xfb000000-0xfb01ffff pref]
    pci 0000:00:01.0: PCI bridge to [bus 01-01]
    pci 0000:00:01.0: bridge window [io 0xa000-0xafff]
    pci 0000:00:01.0: bridge window [mem 0xf8000000-0xfbffffff]
    pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
    pci 0000:00:1c.0: PCI bridge to [bus 02-02]
    pci 0000:00:1c.0: bridge window [io 0x9000-0x9fff]
    pci 0000:00:1c.0: bridge window [mem 0xfdb00000-0xfdbfffff]
    pci 0000:00:1c.0: bridge window [mem 0xfd900000-0xfd9fffff 64bit pref]
    pci 0000:03:00.0: BAR 6: assigned [mem 0xfde00000-0xfde0ffff pref]
    pci 0000:00:1c.1: PCI bridge to [bus 03-03]
    pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
    pci 0000:00:1c.1: bridge window [mem 0xfd800000-0xfd8fffff]
    pci 0000:00:1c.1: bridge window [mem 0xfde00000-0xfdefffff 64bit pref]
    pci 0000:04:00.0: BAR 6: assigned [mem 0xfdc00000-0xfdc1ffff pref]
    pci 0000:00:1c.2: PCI bridge to [bus 04-04]
    pci 0000:00:1c.2: bridge window [io 0xb000-0xbfff]
    pci 0000:00:1c.2: bridge window [mem 0xfdd00000-0xfddfffff]
    pci 0000:00:1c.2: bridge window [mem 0xfdc00000-0xfdcfffff 64bit pref]
    pci 0000:00:1e.0: PCI bridge to [bus 05-05]
    pci 0000:00:1e.0: bridge window [io 0xc000-0xcfff]
    pci 0000:00:1e.0: bridge window [mem 0xfda00000-0xfdafffff]
    pci 0000:00:1e.0: bridge window [mem 0xf4000000-0xf7ffffff 64bit pref]
    pci 0000:00:01.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    pci 0000:00:01.0: setting latency timer to 64
    pci 0000:00:1c.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    pci 0000:00:1c.0: setting latency timer to 64
    pci 0000:00:1c.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    pci 0000:00:1c.1: setting latency timer to 64
    pci 0000:00:1c.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
    pci 0000:00:1c.2: setting latency timer to 64
    pci 0000:00:1e.0: setting latency timer to 64
    pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000dffff]
    pci_bus 0000:00: resource 8 [mem 0x7ff00000-0xfebfffff]
    pci_bus 0000:01: resource 0 [io 0xa000-0xafff]
    pci_bus 0000:01: resource 1 [mem 0xf8000000-0xfbffffff]
    pci_bus 0000:01: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
    pci_bus 0000:02: resource 0 [io 0x9000-0x9fff]
    pci_bus 0000:02: resource 1 [mem 0xfdb00000-0xfdbfffff]
    pci_bus 0000:02: resource 2 [mem 0xfd900000-0xfd9fffff 64bit pref]
    pci_bus 0000:03: resource 0 [io 0xd000-0xdfff]
    pci_bus 0000:03: resource 1 [mem 0xfd800000-0xfd8fffff]
    pci_bus 0000:03: resource 2 [mem 0xfde00000-0xfdefffff 64bit pref]
    pci_bus 0000:04: resource 0 [io 0xb000-0xbfff]
    pci_bus 0000:04: resource 1 [mem 0xfdd00000-0xfddfffff]
    pci_bus 0000:04: resource 2 [mem 0xfdc00000-0xfdcfffff 64bit pref]
    pci_bus 0000:05: resource 0 [io 0xc000-0xcfff]
    pci_bus 0000:05: resource 1 [mem 0xfda00000-0xfdafffff]
    pci_bus 0000:05: resource 2 [mem 0xf4000000-0xf7ffffff 64bit pref]
    pci_bus 0000:05: resource 4 [io 0x0000-0x0cf7]
    pci_bus 0000:05: resource 5 [io 0x0d00-0xffff]
    pci_bus 0000:05: resource 6 [mem 0x000a0000-0x000bffff]
    pci_bus 0000:05: resource 7 [mem 0x000c0000-0x000dffff]
    pci_bus 0000:05: resource 8 [mem 0x7ff00000-0xfebfffff]
    NET: Registered protocol family 2
    IP route cache hash table entries: 65536 (order: 7, 524288 bytes)
    TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
    TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    TCP: Hash tables configured (established 262144 bind 65536)
    TCP reno registered
    UDP hash table entries: 1024 (order: 3, 32768 bytes)
    UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
    NET: Registered protocol family 1
    pci 0000:01:00.0: Boot video device
    PCI: CLS 64 bytes, default 64
    Unpacking initramfs...
    Freeing initrd memory: 1976k freed
    Scanning for low memory corruption every 60 seconds
    audit: initializing netlink socket (disabled)
    type=2000 audit(1294574252.469:1): initialized
    HugeTLB registered 2 MB page size, pre-allocated 0 pages
    VFS: Disk quotas dquot_6.5.2
    Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    msgmni has been set to 4013
    Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
    io scheduler noop registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    vesafb: framebuffer at 0xf9000000, mapped to 0xffffc90010100000, using 1536k, total 14336k
    vesafb: mode is 1024x768x8, linelength=1024, pages=3
    vesafb: scrolling: redraw
    vesafb: Pseudocolor: size=8:8:8:8, shift=0:0:0:0
    Console: switching to colour frame buffer device 128x48
    fb0: VESA VGA frame buffer device
    intel_idle: MWAIT substates: 0x20
    intel_idle: does not run on family 6 model 23
    ERST: Table is not found!
    Linux agpgart interface v0.103
    Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    PNP: No PS/2 controller found. Probing ports directly.
    serio: i8042 KBD port at 0x60,0x64 irq 1
    serio: i8042 AUX port at 0x60,0x64 irq 12
    mice: PS/2 mouse device common for all mice
    rtc_cmos 00:03: RTC can wake from S4
    rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
    rtc0: alarms up to one month, 242 bytes nvram
    cpuidle: using governor ladder
    cpuidle: using governor menu
    TCP cubic registered
    NET: Registered protocol family 17
    Registering the dns_resolver key type
    PM: Resume from disk failed.
    registered taskstats version 1
    rtc_cmos 00:03: setting system clock to 2011-01-09 11:57:33 UTC (1294574253)
    Initalizing network drop monitor service
    Freeing unused kernel memory: 504k freed
    udev[45]: starting version 164
    SCSI subsystem initialized
    libata version 3.00 loaded.
    pata_acpi 0000:00:1f.2: PCI INT A -> GSI 19 (level, low) -> IRQ 19
    pata_acpi 0000:00:1f.2: setting latency timer to 64
    pata_acpi 0000:00:1f.2: PCI INT A disabled
    ata_piix 0000:00:1f.2: version 2.13
    ata_piix 0000:00:1f.2: PCI INT A -> GSI 19 (level, low) -> IRQ 19
    Floppy drive(s): fd0 is 1.44M
    ata_piix 0000:00:1f.2: MAP [ P0 -- P1 -- ]
    ata_piix 0000:00:1f.2: setting latency timer to 64
    scsi0 : ata_piix
    scsi1 : ata_piix
    ata1: SATA max UDMA/133 cmd 0xf900 ctl 0xf800 bmdma 0xf500 irq 19
    ata2: SATA max UDMA/133 cmd 0xf700 ctl 0xf600 bmdma 0xf508 irq 19
    ata_piix 0000:00:1f.5: PCI INT A -> GSI 19 (level, low) -> IRQ 19
    ata_piix 0000:00:1f.5: MAP [ P0 -- P1 -- ]
    ata_piix 0000:00:1f.5: setting latency timer to 64
    scsi2 : ata_piix
    scsi3 : ata_piix
    ata3: SATA max UDMA/133 cmd 0xf200 ctl 0xf100 bmdma 0xee00 irq 19
    ata4: SATA max UDMA/133 cmd 0xf000 ctl 0xef00 bmdma 0xee08 irq 19
    FDC 0 is a post-1991 82077
    pata_acpi 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    pata_acpi 0000:03:00.0: setting latency timer to 64
    pata_acpi 0000:03:00.0: PCI INT A disabled
    ata3: SATA link down (SStatus 0 SControl 300)
    ata4: SATA link down (SStatus 0 SControl 300)
    ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata2.00: ATA-8: WDC WD6400AAKS-65A7B2, 01.03B01, max UDMA/133
    ata2.00: 1250263728 sectors, multi 16: LBA48 NCQ (depth 0/32)
    ata2.00: configured for UDMA/133
    ata1.00: ATA-7: MAXTOR STM3320620AS, 3.AAE, max UDMA/133
    ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 0/32)
    ata1.00: configured for UDMA/133
    scsi 0:0:0:0: Direct-Access ATA MAXTOR STM332062 3.AA PQ: 0 ANSI: 5
    scsi 1:0:0:0: Direct-Access ATA WDC WD6400AAKS-6 01.0 PQ: 0 ANSI: 5
    pata_jmicron 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    pata_jmicron 0000:03:00.0: setting latency timer to 64
    scsi4 : pata_jmicron
    scsi5 : pata_jmicron
    ata5: PATA max UDMA/100 cmd 0xdf00 ctl 0xde00 bmdma 0xdb00 irq 17
    ata6: PATA max UDMA/100 cmd 0xdd00 ctl 0xdc00 bmdma 0xdb08 irq 17
    sd 0:0:0:0: [sda] 625142448 512-byte logical blocks: (320 GB/298 GiB)
    sd 1:0:0:0: [sdb] 1250263728 512-byte logical blocks: (640 GB/596 GiB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 1:0:0:0: [sdb] Write Protect is off
    sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
    sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sdb: sdb1
    sd 1:0:0:0: [sdb] Attached SCSI disk
    sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
    sd 0:0:0:0: [sda] Attached SCSI disk
    ata5.00: ATAPI: _NEC DVD_RW ND-3550A, 1.05, max UDMA/33
    ata5.00: configured for UDMA/33
    scsi 4:0:0:0: CD-ROM _NEC DVD_RW ND-3550A 1.05 PQ: 0 ANSI: 5
    sr0: scsi3-mmc drive: 48x/48x writer cd/rw xa/form2 cdda tray
    cdrom: Uniform CD-ROM driver Revision: 3.20
    sr 4:0:0:0: Attached scsi CD-ROM sr0
    EXT3-fs: barriers not enabled
    kjournald starting. Commit interval 5 seconds
    EXT3-fs (sda3): mounted filesystem with writeback data mode
    Not activating Mandatory Access Control now since /sbin/tomoyo-init doesn't exist.
    udev[761]: starting version 164
    pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    i801_smbus 0000:00:1f.3: PCI INT B -> GSI 18 (level, low) -> IRQ 18
    iTCO_vendor_support: vendor-support=0
    iTCO_wdt: Intel TCO WatchDog Timer Driver v1.06
    iTCO_wdt: Found a ICH9 TCO device (Version=2, TCOBASE=0x0460)
    iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
    sky2: driver version 1.28
    sky2 0000:04:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
    sky2 0000:04:00.0: setting latency timer to 64
    sky2 0000:04:00.0: Yukon-2 EC Ultra chip revision 3
    sky2 0000:04:00.0: irq 40 for MSI/MSI-X
    sky2 0000:04:00.0: eth0: addr 00:50:8d:b3:2b:d6
    input: PC Speaker as /devices/platform/pcspkr/input/input0
    sd 0:0:0:0: Attached scsi generic sg0 type 0
    sd 1:0:0:0: Attached scsi generic sg1 type 0
    sr 4:0:0:0: Attached scsi generic sg2 type 5
    HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
    HDA Intel 0000:00:1b.0: irq 41 for MSI/MSI-X
    HDA Intel 0000:00:1b.0: setting latency timer to 64
    hda_codec: ALC888: BIOS auto-probing.
    input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/input/input1
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    ACPI: acpi_idle registered with cpuidle
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
    ehci_hcd 0000:00:1a.7: setting latency timer to 64
    ehci_hcd 0000:00:1a.7: EHCI Host Controller
    ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:1a.7: cache line size of 64 is not supported
    ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfdfff000
    uhci_hcd: USB Universal Host Controller Interface driver
    ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 6 ports detected
    ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
    ehci_hcd 0000:00:1d.7: setting latency timer to 64
    ehci_hcd 0000:00:1d.7: EHCI Host Controller
    ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
    ehci_hcd 0000:00:1d.7: cache line size of 64 is not supported
    ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfdffe000
    ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 6 ports detected
    uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    uhci_hcd 0000:00:1a.0: setting latency timer to 64
    uhci_hcd 0000:00:1a.0: UHCI Host Controller
    uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
    uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000ff00
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 2 ports detected
    uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
    uhci_hcd 0000:00:1a.1: setting latency timer to 64
    uhci_hcd 0000:00:1a.1: UHCI Host Controller
    uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
    uhci_hcd 0000:00:1a.1: irq 21, io base 0x0000fe00
    hub 4-0:1.0: USB hub found
    hub 4-0:1.0: 2 ports detected
    uhci_hcd 0000:00:1a.2: PCI INT D -> GSI 19 (level, low) -> IRQ 19
    uhci_hcd 0000:00:1a.2: setting latency timer to 64
    uhci_hcd 0000:00:1a.2: UHCI Host Controller
    uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5
    uhci_hcd 0000:00:1a.2: irq 19, io base 0x0000fd00
    hub 5-0:1.0: USB hub found
    hub 5-0:1.0: 2 ports detected
    uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
    uhci_hcd 0000:00:1d.0: setting latency timer to 64
    uhci_hcd 0000:00:1d.0: UHCI Host Controller
    uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6
    uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000fc00
    hub 6-0:1.0: USB hub found
    hub 6-0:1.0: 2 ports detected
    uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
    uhci_hcd 0000:00:1d.1: setting latency timer to 64
    uhci_hcd 0000:00:1d.1: UHCI Host Controller
    uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7
    uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000fb00
    hub 7-0:1.0: USB hub found
    hub 7-0:1.0: 2 ports detected
    uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
    uhci_hcd 0000:00:1d.2: setting latency timer to 64
    uhci_hcd 0000:00:1d.2: UHCI Host Controller
    uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8
    uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000fa00
    hub 8-0:1.0: USB hub found
    hub 8-0:1.0: 2 ports detected
    input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
    ACPI: Power Button [PWRB]
    input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
    ACPI: Power Button [PWRF]
    Linux video capture interface: v2.00
    ivtv: Start initialization, version 1.4.2
    ivtv0: Initializing card 0
    ivtv0: Autodetected Hauppauge card (cx23416 based)
    ivtv 0000:05:04.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
    thermal LNXTHERM:01: registered as thermal_zone0
    ACPI: Thermal Zone [THRM] (45 C)
    b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully
    tveeprom 1-0050: Hauppauge model 26582, rev F0B2, serial# 9304267
    tveeprom 1-0050: tuner model is TCL M2523_5N_E (idx 112, type 50)
    tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
    tveeprom 1-0050: audio processor is CX25843 (idx 37)
    tveeprom 1-0050: decoder processor is CX25843 (idx 30)
    tveeprom 1-0050: has no radio
    ivtv0: Autodetected Hauppauge WinTV PVR-150
    cx25840 1-0044: cx25843-24 found @ 0x88 (ivtv i2c driver #0)
    ACPI: Fan [FAN] (on)
    nvidia: module license 'NVIDIA' taints kernel.
    Disabling lock debugging due to kernel taint
    tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
    usb 3-2: new full speed USB device using uhci_hcd and address 2
    wm8775 1-001b: chip found @ 0x36 (ivtv i2c driver #0)
    tuner-simple 1-0061: creating new instance
    tuner-simple 1-0061: type set to 50 (TCL 2002N)
    ivtv0: Registered device video0 for encoder MPG (4096 kB)
    ivtv0: Registered device video32 for encoder YUV (2048 kB)
    ivtv0: Registered device vbi0 for encoder VBI (1024 kB)
    ivtv0: Registered device video24 for encoder PCM (320 kB)
    ivtv0: Initialized card: Hauppauge WinTV PVR-150
    flexcop-pci: will use the HW PID filter.
    flexcop-pci: card revision 2
    ivtv: End initialization
    b2c2_flexcop_pci 0000:05:03.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
    b2c2_flexcop_pci 0000:05:03.0: setting latency timer to 64
    ------------[ cut here ]------------
    WARNING: at fs/proc/generic.c:323 __xlate_proc_name+0xbd/0xe0()
    Hardware name: .
    name 'Technisat/B2C2 FlexCop II/IIb/III Digital TV PCI Driver'
    Modules linked in: tuner_simple tuner_types wm8775 tuner fan cx25840 snd_seq_dummy firewire_ohci(+) firewire_core crc_itu_t snd_seq_oss b2c2_flexcop_pci(+) b2c2_flexcop dvb_core cx24123 cx24113 s5h1420 ivtv cx2341x v4l2_common videodev v4l1_compat v4l2_compat_ioctl32 i2c_algo_bit tveeprom snd_seq_midi_event snd_seq snd_seq_device thermal button uhci_hcd processor ehci_hcd usbcore snd_hda_codec_realtek snd_pcm_oss snd_mixer_oss snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore snd_page_alloc psmouse evdev sg pcspkr sky2 iTCO_wdt iTCO_vendor_support i2c_i801 i2c_core shpchp serio_raw pci_hotplug intel_agp ext3 jbd mbcache sr_mod cdrom sd_mod pata_jmicron floppy ata_piix pata_acpi libata scsi_mod
    Pid: 2310, comm: modprobe Tainted: P 2.6.36-ARCH #1
    Call Trace:
    [<ffffffff81054f7a>] warn_slowpath_common+0x7a/0xb0
    [<ffffffff81055051>] warn_slowpath_fmt+0x41/0x50
    [<ffffffff81189c9d>] __xlate_proc_name+0xbd/0xe0
    [<ffffffff81189d30>] __proc_create+0x70/0x140
    [<ffffffff8118a769>] proc_mkdir_mode+0x29/0x60
    [<ffffffff8118a7b1>] proc_mkdir+0x11/0x20
    [<ffffffff810b7dcb>] register_handler_proc+0x11b/0x140
    [<ffffffff810b5ae9>] __setup_irq+0x1e9/0x340
    [<ffffffffa0636180>] ? flexcop_pci_isr+0x0/0x190 [b2c2_flexcop_pci]
    [<ffffffff810b5d4a>] request_threaded_irq+0x10a/0x210
    [<ffffffffa06364c0>] flexcop_pci_probe+0x1b0/0x350 [b2c2_flexcop_pci]
    [<ffffffff8120976a>] local_pci_probe+0x5a/0xd0
    [<ffffffff81209f50>] pci_device_probe+0x80/0xb0
    [<ffffffff812a4f6a>] ? driver_sysfs_add+0x7a/0xb0
    [<ffffffff812a5246>] driver_probe_device+0x96/0x1c0
    [<ffffffff812a540b>] __driver_attach+0x9b/0xa0
    [<ffffffff812a5370>] ? __driver_attach+0x0/0xa0
    [<ffffffff812a41ae>] bus_for_each_dev+0x5e/0x90
    [<ffffffff812a4ee9>] driver_attach+0x19/0x20
    [<ffffffff812a4a07>] bus_add_driver+0xc7/0x2e0
    [<ffffffffa063a000>] ? flexcop_pci_module_init+0x0/0x20 [b2c2_flexcop_pci]
    [<ffffffff812a5681>] driver_register+0x71/0x140
    [<ffffffff8107b29d>] ? notifier_call_chain+0x4d/0x70
    [<ffffffffa063a000>] ? flexcop_pci_module_init+0x0/0x20 [b2c2_flexcop_pci]
    [<ffffffff8120a1e1>] __pci_register_driver+0x51/0xd0
    [<ffffffff8107b5fe>] ? __blocking_notifier_call_chain+0x5e/0x80
    [<ffffffffa063a01e>] flexcop_pci_module_init+0x1e/0x20 [b2c2_flexcop_pci]
    [<ffffffff8100212f>] do_one_initcall+0x3f/0x180
    [<ffffffff8109113b>] sys_init_module+0xbb/0x200
    [<ffffffff8100af42>] system_call_fastpath+0x16/0x1b
    ---[ end trace cea0e78273359df7 ]---
    DVB: registering new adapter (FlexCop Digital TV device)
    b2c2-flexcop: MAC address = 00:d0:d7:30:15:0f
    CX24123: cx24123_i2c_readreg: reg=0x0 (error=-121)
    CX24123: wrong demod revision: 87
    usb 3-2: not running at top speed; connect to a high speed hub
    hub 3-2:1.0: USB hub found
    hub 3-2:1.0: 4 ports detected
    usb 3-2.2: new low speed USB device using uhci_hcd and address 3
    nvidia 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    nvidia 0000:01:00.0: setting latency timer to 64
    vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
    NVRM: loading NVIDIA UNIX x86_64 Kernel Module 260.19.29 Wed Dec 8 12:08:56 PST 2010
    usb 3-2.3: new low speed USB device using uhci_hcd and address 4
    usbcore: registered new interface driver hiddev
    input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2.2/3-2.2:1.0/input/input4
    generic-usb 0003:046D:C01D.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1a.0-2.2/input0
    attempt to access beyond end of device
    sda4: rw=0, want=4, limit=2
    EXT3-fs (sda4): error: unable to read superblock
    input: Generic USB K/B as /devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2.3/3-2.3:1.0/input/input5
    generic-usb 0003:13BA:0017.0002: input,hidraw1: USB HID v1.10 Keyboard [Generic USB K/B] on usb-0000:00:1a.0-2.3/input0
    input: Generic USB K/B as /devices/pci0000:00/0000:00:1a.0/usb3/3-2/3-2.3/3-2.3:1.1/input/input6
    generic-usb 0003:13BA:0017.0003: input,hidraw2: USB HID v1.10 Mouse [Generic USB K/B] on usb-0000:00:1a.0-2.3/input1
    usbcore: registered new interface driver usbhid
    usbhid: USB HID core driver
    SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
    SGI XFS Quota Management subsystem
    XFS mounting filesystem sdb1
    Ending clean XFS mount for filesystem: sdb1
    ivtv0: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
    nxt200x: nxt200x_readbytes: i2c read error (addr 0x0a, err == -121)
    Unknown/Unsupported NXT chip: 00 00 00 00 00
    lgdt330x: i2c_read_demod_bytes: addr 0x59 select 0x02 error (ret == -121)
    ivtv0: Encoder revision: 0x02060039
    bcm3510: Revision: 0x1, Layer: 0xb.
    b2c2-flexcop: found 'Broadcom BCM3510 VSB/QAM frontend' .
    DVB: registering adapter 0 frontend 0 (Broadcom BCM3510 VSB/QAM frontend)...
    b2c2-flexcop: initialization of 'Air2PC/AirStar 2 ATSC 1st generation' at the 'PCI' bus controlled by a 'FlexCopIIb' complete
    firewire_ohci 0000:05:05.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
    firewire_ohci 0000:05:05.0: setting latency timer to 64
    firewire_ohci: Added fw-ohci device 0000:05:05.0, OHCI v1.0, 8 IR + 8 IT contexts, quirks 0x0
    NTFS driver 2.1.29 [Flags: R/W MODULE].
    NTFS-fs warning (device sda1): parse_options(): Option utf8 is no longer supported, using option nls=utf8. Please use option nls=utf8 in the future and make sure utf8 is compiled either as a module or into the kernel.
    EXT3-fs: barriers not enabled
    kjournald starting. Commit interval 5 seconds
    EXT3-fs (sda5): using internal journal
    EXT3-fs (sda5): mounted filesystem with writeback data mode
    NTFS volume version 3.1.
    NTFS-fs error (device sda1): load_system_files(): Volume is dirty. Mounting read-only. Run chkdsk and mount in Windows.
    XFS mounting filesystem sda2
    Ending clean XFS mount for filesystem: sda2
    firewire_core: created device fw0: GUID 0000010000013236, S400
    cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
    At this point, I'm not exactly sure where the problem is. I suspect that the filesystems themselves are ok (based on the liveCD tests), so perhaps the problem is the filesystems are inappropriately mounted under /media/* when they are not supposed to (ie before fsck during startup). Also, UDev (which I assume does this mounting) thinks these partitions are USB HD type directories instead of internal SATA partitions. Finally, the errors in dmesg referring to the flexcop module might be a red herring? Please help - I'm not sure what next step to take.

    Thanks for your reply. I did not disconnect any SATA leads. I mainly cleaned the CPU heatsink and fan.
    I am able to boot through UDev and get to filesystems checks without the LiveCD. More specifically, on boot without the live CD, both drives are recognized by the bios and Grub 1.5 is loaded, presenting options to boot into Arch Linux, Arch Linux Fallback, or Windows. If I select Arch Linux, boot messages scroll by, then I see:
    > Arch Linux
    > http://www.archlinux.org
    > Copyright 2002-2007 Judd Vinet
    > Copyright 2007-2010 Aaron Griffin
    > Distributed under the GNU General Public License (GPL)
    :: Starting UDev Daemon [DONE]
    :: Triggering UDev uevents [DONE]
    :: Loading Modules [DONE]
    :: Waiting for UDev uevents to be processed [DONE]
    :: Bringing up loopback interface [DONE]
    :: Mounting Root Read-only [DONE]
    :: Checking Filesystems [BUSY]
    /dev/sda3: clean, 87750/977280 files, 668803/3905803 blocks
    /dev/sda5 is mounted. e2fsck: Cannot continue, aborting.
    /sbin/fsck.xfs: XFS file system [FAIL]
    ***************** FILESYSTEM CHECK FAILED ****************
    * Please repair manually and reboot. Note that the root *
    * file system is currently mounted read-only. To remount *
    * it read-write type: mount -n -o remount,rw / *
    * When you exit the maintenance shell the system will *
    * reboot automatically. *
    Give root password for maintenance
    (or type Control-D to continue):
    At this prompt, if I press Control-D, the system reboots. If I log in using the root password, I see a root prompt. At this point, /proc/mounts already has partitions in it under /media (again this is without any LiveCD). Each directories' contents under media seem normal.
    Interestingly, as I posted above, mount reports that both /dev/disk/by-uuid/dc4661 and /dev/sda3 are mounted (to / and /media/usbhd-sda3, respectively), although this is actually the same partition.
    I should mention I have also run the bootable disk utilities provided by Seagate and WD for each drive and have run their diagnostic studies, which were unrevealing (each ran for ~1.5 hours).
    After seeing the sda1 error messages in dmesg, I booted to WinXP from GRUB. CHKDSK ran and the system booted normally. I ran CHKDSK again from within WinXP as well which revealed no errors. Then, booting into Arch produces a few new errors in dmesg (which are probably irrelevant to the main problem):
    NTFS volume version 3.1.
    NTFS-fs warning (device sda1): load_system_files(): Unsupported volume flags 0x4000 encountered.
    NTFS error (device sda1): load_system_files(): Volume has unsupported flags set. Mounting read-only. Run chkdsk and mount in Windows.
    I don't know if the problem is at the BIOS/hw, partition table, GRUB, UDev, etc.

  • Mail won't open.  It then says quit and rebuild and won't do that.  How to fix?

    So I try to open mail but it hangs.  Then gives the option to quit or quit and rebuild.  It will quit but when I quit and rebuild it hangs and then just shuts off without doing anything.  Not quite sure what to do.
    Any help would be great.
    Steve

    You would have to reinstall the OS using the Recovery Volume.
    Try running the combo update.
    10.8.5 Combo Update
    If that doesn't work,try setting up another admin user account to see if the same problem continues. If Back-to-My Mac is selected in System Preferences, the Guest account will not work. The intent is to see if it is specific to one account or a system wide problem. This account can be deleted later.
    Isolating an issue by using another user account
    If the problem is still there, try booting into the Safe Mode using your normal account.  Disconnect all peripherals except those needed for the test. Shut down the computer and then power it back up after waiting 10 seconds. Immediately after hearing the startup chime, hold down the shift key and continue to hold it until the gray Apple icon and a progress bar appear. The boot up is significantly slower than normal. This will reset some caches, forces a directory check, and disables all startup and login items, among other things. When you reboot normally, the initial reboot may be slower than normal. If the system operates normally, there may be 3rd party applications which are causing a problem. Try deleting/disabling the third party applications after a restart by using the application un-installer. For each disable/delete, you will need to restart if you don't do them all at once.
    Safe Mode
    Safe Mode - Abou

  • How does one strip out all Live Cycle data from a PDF and rebuild the form fields in Acrobat?

    Someone in a different department built a bunch of forms in Live Cycle. We now need to make minor edits to these forms but we all have Macs and can't use Live Cycle. Currently our only option to change a date and a name on each form  is to buy a new Windows workstation, buy a copy of Live Cycle and train someone for it.
    I understand the Live Cycle technology and Acrobat technology for forms are somehow different but there must be a way to just strip out all the Live Cycle form programming so that I just have the bare PDF with the text and layout.  Then make the text edits and rebuild the form fields in Acrobat.

    It depends on your PDF. Is the PDF a static XFA or a dynamic XFA?
    You can check to see if the PDF is static/dynamic by clicking File=>Save As, and it should say static or dynamic PDF as file type.
    iText will work with Static XFA forms created in LiveCycle. Dynamic XFA forms are not supported.
    You can also submit XML data to a server side script and parse the XML data using C# system.xml.xmlreader.
    Another tool that may speed the development of the project is:
    http://www.fdftoolkit.net/
    Note: FDFToolkit.net utilizes iText Technologies.

  • Raid Performance and Rebuild Issues

    Rebuilding a Raid array
    What happens when you have a Raid array and one (or more) disk(s) fail?
    First let's consider the work-flow impact of using a Raid array or not. You may want to refresh your memory about Raids, by reading Adobe Forums: To RAID or not to RAID, that is the... again.
    Sustained transfer rates are a major factor in determining how 'snappy' your editing experience will be when editing multiple tracks. For single track editing most modern disks are fast enough, but when editing complex codecs  like AVCHD, DSLR, RED or EPIC, when using uncompressed or AVC-Intra 100 Mbps codecs, or using multi-cam or multiple tracks  the sustained transfer speed can quickly become a bottleneck and limit the 'snappy' feeling during editing.
    For that reason many use raid arrays to remove that bottleneck from their systems, but this also raises the question:
    What happens when one of more of my disks fail?
    Actually, it is simple. Single disks or single level striped arrays will lose all data. And that means that you have to replace the failed disk and then restore the lost data from a backup before you can continue your editing. This situation can become extremely bothersome if you consider the following scenario:
    At 09:00 you start editing and you finish editing by 17:00 and have a planned backup scheduled at 21:00, like you do every day. At 18:30 one of your disks fails, before your backup has been made. All your work from that day is lost, including your auto-save files, so a complete day of editing is irretrievably lost. You only have the backup from the previous day to restore your data, but that can not be done before you have installed a new disk.
    This kind of scenario is not unheard of and even worse, this usually happens at the most inconvenient time, like on Saturday afternoon before a long weekend and you can only buy a new disk on Tuesday...(sigh).
    That is the reason many opt for a mirrored or parity array, despite the much higher cost (dedicated raid controller, extra disks and lower performance than a striped array). They buy safety, peace-of-mind and a more efficient work-flow.
    Consider the same scenario as above and again one disk fails.  No worry, be happy!! No data lost at all and you could continue editing, making the last changes of the day. Your planned backup will proceed as scheduled and the next morning you can continue editing, after having the failed disk replaced. All your auto-save files are intact as well.
    The chances of two disks failing simultaneously are extremely slim, but if cost is no object and safety is everything, some consider using a raid6 array to cover that eventuality. See the article quoted at the top.
    Rebuilding data after a disk failure
    In the case of a single disk or striped arrays, you have to use your backup to rebuild your data. If the backup is not current, you lose everything you did after your last backup.
    In the case of a mirrored array, the raid controller will write all data on the mirror to the newly installed disk. Consider it a disk copy from the mirror to the new disk. This is a fast way to get back to full speed. No need to get out your (possibly older) backup and restore the data. Since the controller does this in the background, you can continue working on your time-line.
    In the case of parity raids (3/5/6) one has to make a distinction between distributed parity raids (5/6) and dedicated parity raid (3).
    Dedicated parity, raid3
    If a disk fails, the data can be rebuild by reading all remaining disks (all but the failed one) and writing the rebuilt data only to the newly replaced disk. So writing to a single disk is enough to rebuild the array. There are actually two possibilities that can impact the rebuild of a degraded array. If the dedicated parity drive failed, the rebuilding process is a matter of recalculating the parity info (relatively easy) by reading all remaining data and writing the parity to the new dedicated disk. If a data disk failed, then the data need to be rebuild, based on the remaining data and the parity and this is the most time-consuming part of rebuilding a degraded array.
    Distributed parity, raid5 or raid6
    If a disk fails, the data can be rebuild by reading all remaining disks (all but the failed one), rebuilding the data and recalculating the parity information and writing the data and parity information to the failed disk. This is always time-consuming.
    The impact of 'hot-spares' and other considerations
    When an array is protected by a hot spare, if a disk drive in that array fails the hot spare is automatically incorporated into the array and takes over for the failed drive. When an array is not protected by a hot spare, if a disk drive in that array fails, remove and replace the failed disk drive. The controller detects the new disk drive and begins to rebuild the array.
    If you have hot-swappable drive bays, you do not need to shut down the PC, you can simply slide out the failed drive and replace it with a new disk. Remember, when a drive has failed and the raid is running in 'degraded' mode, there is no further protection against data loss, so it is imperative that you replace the failed disk at the earliest moment and rebuild the array to a 'healthy' state.
    Rebuilding a 'degraded' array can be done automatically or manually, depending on the controller in use and often you can set the priority of the rebuilding process higher or lower, depending on the need to continue regular work versus the speed required to repair the array to its 'healthy' status.
    What are the performance gains to be expected from a raid and how long will a rebuild take?
    The  most important column in the table below is the sustained transfer  rate. It is indicative and no guarantee that your raid will achieve  exactly the same results. That depends on the controller, the on-board  cache and the disks in use. The more tracks you use in your editing, the higher the resolution you use, the more complex your codec, the more  you will need a high sustained transfer rate and that means more disks in the array.
    Sidebar: While testing a  new time-line for the PPBM6 benchmark, using a large variety of source  material, including RED and EPIC 4K, 4:2:2 MXF, XDCAM HD and the like,  the required sustained transfer rate for simple playback of a  pre-rendered time-line was already over 300 MB/s, even with 1/4  resolution playback, because of the 4 4 4 4 full quality deBayering of  the 4K material.
    Final thoughts
    With the increasing popularity of file based formats, the importance of backups of your media can not be stressed enough. In the past one always had the original tape if disaster stroke, but no longer. You need regular backups of your media and projects.  With single disks and (R)aid0 you take risks of complete data loss, because of the lack of redundancy.  Backups cost extra disks and extra time to create and restore in case of disk failure.
    The need for backups in case of mirrored raids is far less, since there is complete redundancy. Sure, mirrored raids require double the number of disks but you save on the number of backup disks and you save time to create and restore backups.
    In the case of parity raids, the need for backups is more than with mirrored arrays, but less than with single disks or striped arrays and in the case of 'hot-spares' the need for backups is further reduced. Initially, a parity array may look like a costly endeavor. The raid controller and the number of disks make it expensive, but if you consider what you get, more speed, more storage space, easier administration, less backups required, less time for those backups, continued working in case of a drive failure, even though somewhat sluggish, the cost is often worth more with the peace-of-mind it brings, than continuing with single disks or striped arrays.

    Raid3 is better suited for video editing work, because it is more efficient when using large files, as clips usually are. Raid5 is better suited in high I/O environments, where lots of small files need to be accessed all the time, like news sites, webshops and the like. Raid3 will usually have a better rebuild time than raid5.
    But, and there is always a but, raid3 requires an Areca controller. LSI and other controller brands do not support raid3. And Areca is not exactly cheap...
    Keep in mind that a single disk shows declining performance when the fill rate increases. See the example below:
    A Raid3 or Raid30 will not show that behavior. The performance remains nearly constant even if fill rates go up:
    Note that both charts were created with Samsung Spinpoint F1 disks, an older and slower generation of disks and with an older generation Areca ARC-1680iX-12.

  • Exclamation mark appears instead of photo. Recently upgraded from i mac to Macbook air and all was transferred over. I have run all the repair and rebuild functions in iphoto. Any other solution?

    Exclamation mark appears instead of photo. Recently upgraded from i mac to Macbook air and all was transferred over. I have run all the repair and rebuild functions in iphoto. Any other solution?

    Since iPLM failed to help try the following:
    Starting over from scratch with new library
    Start over with a new library and import the Originals (iPhoto 09 and earlier) or the Masters (iPhoto 11) folder from your original library as follows:
    1. Open the library package like this.
    2. Launch iPhoto with the Option key held down and, when asked, select the option to create a new library.
    3. Drag the subfolders of the Originals (iPhoto 09 and earlier) or the Masters (iPhoto 11) folder from the open iPhoto Library package into the open iPhoto window a few at a time.
    This will create a new library with the same Events (but not necessarily the same Event names) as the original library but will not keep the metadata, albums, books slideshows and other projects.
    Note:  your current library will be left untouched for further attempts at a fix if so desired.
    OT

  • I backed up my movies and rebuild my computer, and after making sure i'm using the latest version of itunes and quicktime and and making sure i still had spare computer authorizations, i still get error 23132.  Please help.

    I backed up my movies and rebuild my computer, and after making sure i'm using the latest version of itunes and quicktime and and making sure i still had spare computer authorizations, i still get error 23132.  Please help.

    I had this exact issue.  Spent over an hour on the phone with apple support, they couldn't resolve.  Here is what I ended up doing, that worked.
    1.  Turned iTunes match off on all my iOS devices
    2.  Deleted the offending playlists from the iOS device they originated on
    3.  Started iTunes, let it run (literally) for an hour before it became responsive.  First thing I did, before clicking anywere else was disable iTunes match.  If I clicked anywhere, it would clock for another hour.
    4.  Let iTunes run overnight, by morning it had cleaned out the repeating play lists.  This got my Mac/iTunes back to an operable state.
    5.  Restore iPhones from backup in iTunes.
    What was causing my issue was a single playlist that was created on an iPhone, then suddenly showed up with several thousand duplicates on my other iPhone.  The culprit playlist did not, for some reason, duplicate itself on my two iPads.  Apple support seemed to think it was because the problem iPhone tried to sync the playlist to iCloud over and over again unsuccessfully, then it finally went through and populated the thousands of blank/failed playlists which then tried to propigate to iTunes and my other iOS devices.  Seems like a reasonable theory.
    I have not yet re-enabled iTunes match.  So, no idea what will happen if I decide to go back down that rabbit hole.

  • Selective deletion for particler cube and rebuild of aggrigates in Psystem

    Hi Friends,
    1.In my manage data target screen i have 8 cubes but i want do selective deletion from 1st cube ..how i can do ..?
    Im thinking like...IN DETILS column i will select.one data target and then i will go to contents tap and then selective deletion for paricler requst ID...is correct to do selective deletion for particler data target out of 8 cubes..plz tell me
    2.in production ...while doing selective deletion ...aggregates are failed...means status is in red color...
    now,how can i create or build or rebuild those aggrgates again...please and my qns...
    Thanks in advance

    Hi
    1. technically Yes its ok to do selective deletion of only 1 cube, incase of delta load you will have to do selective reload to only that cube otherwise data for that perticular selection will get doubled in rest of 7 cubes.
    Actually depends on situation in which you plan to do so.
    2. its possible to aggreegates get affected due t selective deletion.
    Just go to manage->rollup tab of cube and rebuild agreegates.
    Hope this helps.
    Regards
    Sudeep

  • AutoMounting / Udev and HAL

    Hey fellow Archers,
    Sorry if this is a bit of a Noob Question.
    But I am having issues with automounting usb drives that etc. 
    I am running eeepc 1000 and everything works fine out of the box.  But I have shown Arch to a friend of mine and we can't gain access to the usb drive with free.desktop permission error.  I have read the wiki and forum posts.  However I have found the are for much older versions of HAL and Udev, and they are contradictory. 
    Please if you could help me clarfiy a solutions.  Should Udev handle to mounting and permission rule or should I add HAL policy ?.
    If HAL if the best solution could be so kind as to provide a example of Hal policy as my previous attempt to edited HAL has failed.
    Kind Regards
    Mac Tzu

    Mac Tzu wrote:
    Great thanks SpeedVin
    Could you Show me w copy of your Hal polcy?
    No problem
    1 <!DOCTYPE busconfig PUBLIC
    2 "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
    3 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
    4 <busconfig>
    5
    6 <!-- This configuration file specifies the required security policies
    7 for the HAL to work. -->
    8
    9 <!-- Only root or user hal can own the HAL service -->
    10 <policy user="hal">
    11 <allow own="org.freedesktop.Hal"/>
    12 </policy>
    13 <policy user="root">
    14 <allow own="org.freedesktop.Hal"/>
    15 </policy>
    16
    17 <!-- Allow anyone to invoke methods on the Manager and Device interfaces -->
    18 <policy context="default">
    19 <allow send_destination="org.freedesktop.Hal"
    20 send_interface="org.freedesktop.DBus.Introspectable"/>
    21 <allow send_destination="org.freedesktop.Hal"
    22 send_interface="org.freedesktop.DBus.Properties" />
    23
    24 <allow send_destination="org.freedesktop.Hal"
    25 send_interface="org.freedesktop.Hal.Device"/>
    26 <allow send_destination="org.freedesktop.Hal"
    27 send_interface="org.freedesktop.Hal.Manager"/>
    28
    29 <allow send_destination="org.freedesktop.Hal"
    30 send_interface="org.freedesktop.Hal.Device.CPUFreq"/>
    31 <allow send_destination="org.freedesktop.Hal"
    32 send_interface="org.freedesktop.Hal.Device.DockStation"/>
    33 <allow send_destination="org.freedesktop.Hal"
    34 send_interface="org.freedesktop.Hal.Device.KillSwitch"/>
    35 <allow send_destination="org.freedesktop.Hal"
    36 send_interface="org.freedesktop.Hal.Device.KeyboardBacklight"/>
    37 <allow send_destination="org.freedesktop.Hal"
    38 send_interface="org.freedesktop.Hal.Device.LaptopPanel"/>
    39 <allow send_destination="org.freedesktop.Hal"
    40 send_interface="org.freedesktop.Hal.Device.Leds"/>
    41 <allow send_destination="org.freedesktop.Hal"
    42 send_interface="org.freedesktop.Hal.Device.LightSensor"/>
    43 <allow send_destination="org.freedesktop.Hal"
    44 send_interface="org.freedesktop.Hal.Device.Storage"/>
    45 <allow send_destination="org.freedesktop.Hal"
    46 send_interface="org.freedesktop.Hal.Device.Storage.Removable"/>
    47 <allow send_destination="org.freedesktop.Hal"
    48 send_interface="org.freedesktop.Hal.Device.SystemPowerManagement"/>
    49 <allow send_destination="org.freedesktop.Hal"
    50 send_interface="org.freedesktop.Hal.Device.Volume"/>
    51 <allow send_destination="org.freedesktop.Hal"
    52 send_interface="org.freedesktop.Hal.Device.Volume.Crypto"/>
    53 <allow send_destination="org.freedesktop.Hal"
    54 send_interface="org.freedesktop.Hal.Device.WakeOnLan"/>
    55
    56 </policy>
    57
    58 </busconfig>
    59
    Nuber's are from Vim

  • I have Macbook Air. One day i am using email-Entrouage, sudden it stuck up. I stopped it and start entourage again but it start verify and and rebuild but not rebuilt. email are 41.5 GB and free 5 GB, plesae guide how to resovle.

    i have Macbook Air. One day i am using email-Entrouage, sudden it stuck up. I stopped it and start entourage again but it start verify and and rebuild but not rebuilt. email are 41.5 GB and free 5 GB. When problem not resolved i also copied that email db file in other Mac book with 200 GB free space but same process first verify then rebuild then message it cannot rebuild. Please guide.

    I've been rebuilding Entourage Identities for years for clients. Most fail because they do not have enough free space. See this article
    http://www.officeformachelp.com/2007/09/rebuilding_a_damaged_database_that_excee ded_size_limit/
    (Fair disclosure: OfficeforMacHelp is my site. I may receive some form of compensation, financial or otherwise, from my recommendation or link.)

  • Dockingstation with udev and systemd

    Hello,
    first: sorry for my bad english... the last time i have practise my english was in school :-)
    now my problem:
    i try to setup a udev-rule for my thinkpad T61 when the latptop is (un)docked from the station.
    i try a lot of thinks... RUN+=" and such stuff -- but my script takes very long time (Setup Interface, WakeOnLAN, multiple cryptet mounts from my homeserver etc.) and killed by systemd after a while.
    related to this (jasonwryan.com -- Scripting with udev) and this (bbs.archlinux.org -- Automating a script for a usb device on systemd?) i create a udev-rule like this:
    /etc/udev/rules.d/10-thinkpad-dock.rules:
    TAG+="systemd", SUBSYSTEM=="platform", KERNEL=="dock.3", ACTION=="change", ENV{SYSTEMD_READY}="1", ENV{SYSTEMD_USER_WANTS}="dock.service"
    and a service-file like this:
    /etc/systemd/user/dock.service
    [Unit]
    Description=User docking actions
    After=graphical.target sys-devices-platform-dock.3.device
    [Service]
    Type=simple
    Restart=always
    Environment=DISPLAY=:0.0
    Environment=XAUTHORITY=/home/emilia/.Xauthority
    ExecStart=-/usr/local/sbin/tp-dock
    [Install]
    WantedBy=graphical.target sys-devices-platform-dock.3.device
    the problem is, the script runs only once at the first docking-action after a reboot. the other times nothing happens and also the logs are empty.
    Any suggestions and/or help please?

    Hello,
    first: sorry for my bad english... the last time i have practise my english was in school :-)
    now my problem:
    i try to setup a udev-rule for my thinkpad T61 when the latptop is (un)docked from the station.
    i try a lot of thinks... RUN+=" and such stuff -- but my script takes very long time (Setup Interface, WakeOnLAN, multiple cryptet mounts from my homeserver etc.) and killed by systemd after a while.
    related to this (jasonwryan.com -- Scripting with udev) and this (bbs.archlinux.org -- Automating a script for a usb device on systemd?) i create a udev-rule like this:
    /etc/udev/rules.d/10-thinkpad-dock.rules:
    TAG+="systemd", SUBSYSTEM=="platform", KERNEL=="dock.3", ACTION=="change", ENV{SYSTEMD_READY}="1", ENV{SYSTEMD_USER_WANTS}="dock.service"
    and a service-file like this:
    /etc/systemd/user/dock.service
    [Unit]
    Description=User docking actions
    After=graphical.target sys-devices-platform-dock.3.device
    [Service]
    Type=simple
    Restart=always
    Environment=DISPLAY=:0.0
    Environment=XAUTHORITY=/home/emilia/.Xauthority
    ExecStart=-/usr/local/sbin/tp-dock
    [Install]
    WantedBy=graphical.target sys-devices-platform-dock.3.device
    the problem is, the script runs only once at the first docking-action after a reboot. the other times nothing happens and also the logs are empty.
    Any suggestions and/or help please?

  • Automated Delete and Rebuild of BIA Indexes

    We have several cubes that we will be loading into BIA that use non-cumulative key figures.  We have heard that it is necessary to periodically rebuild these indexes to keep the BIA performance high.  My question is how do we automate this process?  I don't see a process chain step or program for deleting an index. 
    There is program RSDDTREX_AGGREGATES_FILL, but will this rebuild an index if it already exists?

    Hi
    Deleting and rebuilding the Cube indexes will improve the the loading performance.
    It is very much required for for Full loads and Big loads.
    When it comes to Delta loads or Small loads, then it depends upon the volume of data you are going to get.
    Say like you are getting below 10000 records in daily delta's, then i think no need to delete and rebuild indexes.
    If you know that you will get more than1 lack records, then it's good to go for deletion and rebuild of indexes.
    Example : I load an Infocube once by week in full upload (3 millions of records) after deleting all the content of the previous week. Is it a good idea to add steps of deleting/rebuilding indexes in this case ?
    In this case, it is required.
    Note: 1) If you want you can test in your development system, run the same load first time by deleting indexes and second time without deleting the indexes. you will come to know the time difference.
    2) Anyhow deletion and rebuilding of indexes step will take less than 2 or 3 mins time unless if you have huge volume of uncomressed data in your cube.
    Regards,
    Venkatesh.

  • Incompatible PDB format in 'filename'; delete and rebuild

    Hi !
    I have installed VS 2012 , but i have VS 2010 also. After I open  VS 2010 projects with VS 2012 and  click "update", but while i debug it ,there is a error message:
    LINK : fatal error LNK1207: incompatible PDB format in 'C:\Users\Admir\Documents\Visual Studio 2010\Projects\nr.fjaleve.while\Debug\nr.fjaleve.while.pdb'; delete and rebuild.
    What can I do to solve this?
    verify

    Hi verify,
    It seems that it is not the VS debug issue.
    LINK : fatal error LNK1207: incompatible PDB format in 'C:\Users\Admir\Documents\Visual Studio 2010\Projects\nr.fjaleve.while\Debug\nr.fjaleve.while.pdb'; delete and rebuild.
    Please Clean and Rebuild your app under “Build” menu, check it again. If still no help, maybe you could delete it manually, and then rebuild it again. Hope it could help.
    Reference:
    Linker Tools Error LNK1207
    Best Regards,
    Jack Zhai [MSFT]
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Thank you Jack!
     I cleaned my app, ang rebuild it again, and it works.
    verify

  • Mail spins and rebuild mailbox is grayed

    mail spins and rebuild mailbox option is grayed?

    One way to test is to Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, Test for problem in Safe Mode...
    PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive
    Reboot, test again.

  • After Chapter 7 Car Loan and Rebuilding

    This board has a weath of knowledge and has been a big help for me during the process of BK Chap 7 and rebuilding so I thought I would share some hope with everyone. Filed Chap 7 in April 2015 due to a divorce and job loss and health issues. My lawyer asked me why I waited so long? Tried to fix it all myself but was about 125K in debt. Discharged all but 1k and was finished by late June. Now starting the rebuilding process. Got a 400.00 Fingerhut card....but who can afford to buy this stuff? Oh well I will use it once just to have something on my report. Also got a Credit One bank card with a 300.00 limit. Easy to get. Use it for gas and pay it off every month. My scores after BK have climbed from the low 440's to as high as 695 on Experian in July 15. Now in early August Im at 683 Experian and 674 Transunion. So reading all the recommendations and now looking at my 28+ year credit history that is gone, now it shows about 1 yr, I knew I needed to have good payment history moving forward to rebuild. Car loans are supposed to help, so even though I wasn't planning to get a car until next spring, I couldn't stand the curiosity of whether or not anyone will finance me. So I went online and of course RoadLoans gave me 23K with no down car loan at 17%. Off I go to Carmax. They rerun my credit and it takes forever for all the banks to run me thru.....I wait, I wait. I'm looking at a 2014 Hyundai Santa Fe that's about 25K and over my approval amount. Still wait. All the banks decline but Wells Fargo is still in a holding pattern. After what seemed like an eternity, they blow RoadLoans out of the water and give me the 25K with 0 down and 10% interest! So I'm moving along in the process of rebuilding. Figure I will refi in about a year for lower interest thru my credit union.

    NCSCNative wrote:
    This board has a weath of knowledge and has been a big help for me during the process of BK Chap 7 and rebuilding so I thought I would share some hope with everyone. Filed Chap 7 in April 2015 due to a divorce and job loss and health issues. My lawyer asked me why I waited so long? Tried to fix it all myself but was about 125K in debt. Discharged all but 1k and was finished by late June. Now starting the rebuilding process. Got a 400.00 Fingerhut card....but who can afford to buy this stuff? Oh well I will use it once just to have something on my report. Also got a Credit One bank card with a 300.00 limit. Easy to get. Use it for gas and pay it off every month. My scores after BK have climbed from the low 440's to as high as 695 on Experian in July 15. Now in early August Im at 683 Experian and 674 Transunion. So reading all the recommendations and now looking at my 28+ year credit history that is gone, now it shows about 1 yr, I knew I needed to have good payment history moving forward to rebuild. Car loans are supposed to help, so even though I wasn't planning to get a car until next spring, I couldn't stand the curiosity of whether or not anyone will finance me. So I went online and of course RoadLoans gave me 23K with no down car loan at 17%. Off I go to Carmax. They rerun my credit and it takes forever for all the banks to run me thru.....I wait, I wait. I'm looking at a 2014 Hyundai Santa Fe that's about 25K and over my approval amount. Still wait. All the banks decline but Wells Fargo is still in a holding pattern. After what seemed like an eternity, they blow RoadLoans out of the water and give me the 25K with 0 down and 10% interest! So I'm moving along in the process of rebuilding. Figure I will refi in about a year for lower interest thru my credit union.Welcome to MyFico Congrats on the new vehicle and thanks for sharing your story

Maybe you are looking for

  • Problem in making air application in full screen on load

    Hi all   I am new in flex developing. The problem I m facing in making a air application is that I want to make the application window in full screen view without the top toolbar. The code i got is like: <mx:Button label="fullscreen" click="stage.dis

  • Exporting: How to include all metadata but keywords?

    When exporting to JPEG, is there any way to export all of the metadata that is currently exported, but exclude just the keywords? I know there is an option to minimize metadata on export, but that seems to remove everything but the copyright informat

  • Dynamic URLs for the mx:HTTPService component

    I am looking to make the url property of an mx:HTTPService component dynamic. <mx:HTTPService id="srvDivision" url=" http://prodserver/prod/get_division.jsp" useProxy="false" method="POST"> </mx:HTTPService> I would just like to have an environment p

  • Do you have to buy the nike plus app for nike plus to work

    Do have to buy the nike plus app

  • ODI 11g

    Hi, I found a link which talks about how to use external database to store data in ODI 10g: http://docs.oracle.com/cd/E15985_01/doc.10136/user/e16274/xml/doc/driver_configuration.htm In order to encyrpt the password we are supposed to use java -cp sn