You are not logged in.
The following source has detailed info on a method to utilize grub2 in arch raid bootable installs:
http://travishegner.com/2012/02/boot-ar … 42AA7OVv3T
My utilization involves Compact Flash devices in raid0 and was successfully used to install the latest linux kernel yesterday.
The key seems to be to skip grub steps in the archiso and install grub2-bios in a subsequent chroot, utilizing the mdadm.conf steps and mkinitcpio -p linux. Grub2 is installed in the mbr of the boot device.
I setup the raid0 array in gparted and provided 100mb of free space before the primary boot partition which is also 100mb. The rest of the 16GB device is partitioned as ext3 .
The second device is similarly partitoned with 100mb of free space followed by a primary partition of 100mb swap and the rest partitioned the same size as boot device and is ext3.
During the archiso install, the manual partitioning is skipped with "done", preserving the parttioning and the mountpoints are then established. All grub steps are skipped after configuring the system.
I used remote install from mirror to install the latest linux kernel.
The linux kernel and its associated udev,mdadm and init results in mdadm devices with names such as md126, md127 or the like. Mine came out as md127.
The resulting raid0 array using maxell 16GB udma devices boots in about 20 seconds and in hdparm read speed is 90mb/s.
The speed reading is not as expected, it should be 180mb/s. I believe this is due to a failed dma step in the install of linux.
I am hopeful that can be corrected in the near future.
I am using xfce4 and have installed xorg, xfce4,vlc,mirage,kdenlive,smplayer,gparted, hdparm,firefox and jumanji-git subsequent to initial booting.
Happy camper again!
EDIT: Prior installs of raid0 utilized UDMA protocol but this linux kernel does not provide ioctl dma for these devices altho the maxell CF card is labeled UDMA.
Perhaps a guru can explain how to correct this limitation?
Edit: The hdparm reads are weird as shown below:
sh-4.2# hdparm -tT /dev/md1
/dev/md1:
Timing cached reads: 1982 MB in 2.00 seconds = 990.90 MB/sec
Timing buffered disk reads: 272 MB in 3.01 seconds = 90.41 MB/sec
sh-4.2# hdparm -tT /dev/sda2
/dev/sda2:
Timing cached reads: 1988 MB in 2.00 seconds = 994.16 MB/sec
Timing buffered disk reads: 258 MB in 3.02 seconds = 85.33 MB/sec
sh-4.2# hdparm -tT /dev/sdb2a2
/dev/sdb2a2: No such file or directory
sh-4.2# hdparm -tT /dev/sdb2
/dev/sdb2:
Timing cached reads: 1990 MB in 2.00 seconds = 994.97 MB/sec
Timing buffered disk reads: 258 MB in 3.02 seconds = 85.51 MB/sec
sh-4.2# Thus the speed of the array is not twice the speed of the devices.
Why?
EDIT: Further data on the problem:
sh-4.2# dmesg
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.3.2-1-ARCH (tobias@T-POWA-LX) (gcc version 4.7.0 20120407 (prerelease) (GCC) ) #1 SMP PREEMPT Sat Apr 14 09:48:37 CEST 2012
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=525bf29b-6c96-4f58-bb2a-931052c7697f ro quiet add_efi_memmap
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 00000000cf7f0000 (usable)
[ 0.000000] BIOS-e820: 00000000cf7f0000 - 00000000cf7f3000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000cf7f3000 - 00000000cf800000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] DMI 2.4 present.
[ 0.000000] DMI: Gigabyte Technology Co., Ltd. 945GCM-S2C/945GCM-S2C, BIOS F4 11/08/2007
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
[ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
[ 0.000000] No AGP bridge found
[ 0.000000] last_pfn = 0xcf7f0 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-C9FFF write-protect
[ 0.000000] CA000-EFFFF uncachable
[ 0.000000] F0000-FFFFF write-through
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask F80000000 write-back
[ 0.000000] 1 base 080000000 mask FC0000000 write-back
[ 0.000000] 2 base 0C0000000 mask FF0000000 write-back
[ 0.000000] 3 base 0CF800000 mask FFF800000 uncachable
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] found SMP MP-table at [ffff8800000f4c00] f4c00
[ 0.000000] initial memory mapped : 0 - 20000000
[ 0.000000] Base memory trampoline at [ffff88000009a000] 9a000 size 20480
[ 0.000000] init_memory_mapping: 0000000000000000-00000000cf7f0000
[ 0.000000] 0000000000 - 00cf600000 page 2M
[ 0.000000] 00cf600000 - 00cf7f0000 page 4k
[ 0.000000] kernel direct mapping tables up to cf7f0000 @ 1fffa000-20000000
[ 0.000000] RAMDISK: 37a1a000 - 37d05000
[ 0.000000] ACPI: RSDP 00000000000f6540 00014 (v00 GBT )
[ 0.000000] ACPI: RSDT 00000000cf7f3040 0003C (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
[ 0.000000] ACPI: FACP 00000000cf7f30c0 00074 (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
[ 0.000000] ACPI: DSDT 00000000cf7f3180 03844 (v01 GBT GBTUACPI 00001000 MSFT 0100000C)
[ 0.000000] ACPI: FACS 00000000cf7f0000 00040
[ 0.000000] ACPI: HPET 00000000cf7f6b00 00038 (v01 GBT GBTUACPI 42302E31 GBTU 00000098)
[ 0.000000] ACPI: MCFG 00000000cf7f6b80 0003C (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
[ 0.000000] ACPI: APIC 00000000cf7f6a40 00068 (v01 GBT GBTUACPI 42302E31 GBTU 01010101)
[ 0.000000] ACPI: SSDT 00000000cf7f6c00 0015C (v01 PmRef Cpu0Ist 00003000 INTL 20040311)
[ 0.000000] ACPI: SSDT 00000000cf7f7090 00167 (v01 PmRef CpuPm 00003000 INTL 20040311)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at 0000000000000000-00000000cf7f0000
[ 0.000000] Initmem setup node 0 0000000000000000-00000000cf7f0000
[ 0.000000] NODE_DATA [00000000cf7eb000 - 00000000cf7effff]
[ 0.000000] [ffffea0000000000-ffffea00033fffff] PMD -> [ffff8800cba00000-ffff8800cedfffff] on node 0
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000010 -> 0x00001000
[ 0.000000] DMA32 0x00001000 -> 0x00100000
[ 0.000000] Normal empty
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] Early memory PFN ranges
[ 0.000000] 0: 0x00000010 -> 0x0000009f
[ 0.000000] 0: 0x00000100 -> 0x000cf7f0
[ 0.000000] On node 0 totalpages: 849791
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 5 pages reserved
[ 0.000000] DMA zone: 3914 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 13216 pages used for memmap
[ 0.000000] DMA32 zone: 832592 pages, LIFO batch:31
[ 0.000000] ACPI: PM-Timer IO Port: 0x408
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[ 0.000000] SMP: Allowing 2 CPUs, 0 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 40
[ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000
[ 0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000
[ 0.000000] Allocating PCI resources starting at cf800000 (gap: cf800000:20800000)
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:2 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff8800cf400000 s82176 r8192 d24320 u1048576
[ 0.000000] pcpu-alloc: s82176 r8192 d24320 u1048576 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 0 1
[ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 836506
[ 0.000000] Policy zone: DMA32
[ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=525bf29b-6c96-4f58-bb2a-931052c7697f ro quiet add_efi_memmap
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Checking aperture...
[ 0.000000] No AGP bridge found
[ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
[ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[ 0.000000] Memory: 3331536k/3399616k available (4495k kernel code, 452k absent, 67628k reserved, 4327k data, 732k init)
[ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
[ 0.000000] Verbose stalled-CPUs detection is disabled.
[ 0.000000] NR_IRQS:4352 nr_irqs:512 16
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] allocated 13631488 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] hpet clockevent registered
[ 0.000000] Fast TSC calibration using PIT
[ 0.000000] Detected 2800.194 MHz processor.
[ 0.003339] Calibrating delay loop (skipped), value calculated using timer frequency.. 5602.73 BogoMIPS (lpj=9333980)
[ 0.003347] pid_max: default: 32768 minimum: 301
[ 0.003388] Security Framework initialized
[ 0.003396] AppArmor: AppArmor disabled by boot time parameter
[ 0.004365] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
[ 0.007269] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 0.008386] Mount-cache hash table entries: 256
[ 0.008630] Initializing cgroup subsys cpuacct
[ 0.008636] Initializing cgroup subsys memory
[ 0.008650] Initializing cgroup subsys devices
[ 0.008654] Initializing cgroup subsys freezer
[ 0.008657] Initializing cgroup subsys net_cls
[ 0.008661] Initializing cgroup subsys blkio
[ 0.008721] CPU: Physical Processor ID: 0
[ 0.008724] CPU: Processor Core ID: 0
[ 0.008728] mce: CPU supports 4 MCE banks
[ 0.008743] CPU0: Thermal monitoring enabled (TM1)
[ 0.008751] using mwait in idle threads.
[ 0.010140] ACPI: Core revision 20120111
[ 0.013347] ftrace: allocating 17486 entries in 69 pages
[ 0.023811] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.057795] CPU0: Intel(R) Pentium(R) D CPU 2.80GHz stepping 04
[ 0.059996] Performance Events: Netburst events, Netburst P4/Xeon PMU driver.
[ 0.059996] ... version: 0
[ 0.059996] ... bit width: 40
[ 0.059996] ... generic registers: 18
[ 0.059996] ... value mask: 000000ffffffffff
[ 0.059996] ... max period: 0000007fffffffff
[ 0.059996] ... fixed-purpose events: 0
[ 0.059996] ... event mask: 000000000003ffff
[ 0.076759] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.103352] Booting Node 0, Processors #1 Ok.
[ 0.103357] smpboot cpu 1: start_ip = 9a000
[ 0.116693] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.123335] Brought up 2 CPUs
[ 0.123339] Total of 2 processors activated (11205.47 BogoMIPS).
[ 0.125088] devtmpfs: initialized
[ 0.127567] PM: Registering ACPI NVS region at cf7f0000 (12288 bytes)
[ 0.127909] NET: Registered protocol family 16
[ 0.128107] ACPI: bus type pci registered
[ 0.128210] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf0000000-0xf3ffffff] (base 0xf0000000)
[ 0.128216] PCI: MMCONFIG at [mem 0xf0000000-0xf3ffffff] reserved in E820
[ 0.141075] PCI: Using configuration type 1 for base access
[ 0.141255] mtrr: your CPUs had inconsistent variable MTRR settings
[ 0.141259] mtrr: probably your BIOS does not setup all CPUs.
[ 0.141261] mtrr: corrected configuration.
[ 0.141925] bio: create slab <bio-0> at 0
[ 0.141925] ACPI: Added _OSI(Module Device)
[ 0.141925] ACPI: Added _OSI(Processor Device)
[ 0.141925] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.141925] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.141925] ACPI: EC: Look up EC in DSDT
[ 0.146902] ACPI: SSDT 00000000cf7f7000 00087 (v01 PmRef Cpu1Ist 00003000 INTL 20040311)
[ 0.147150] ACPI: Dynamic OEM Table Load:
[ 0.147155] ACPI: SSDT (null) 00087 (v01 PmRef Cpu1Ist 00003000 INTL 20040311)
[ 0.147342] ACPI: Interpreter enabled
[ 0.147350] ACPI: (supports S0 S1 S4 S5)
[ 0.147377] ACPI: Using IOAPIC for interrupt routing
[ 0.153543] ACPI: No dock devices found.
[ 0.153551] PCI: Ignoring host bridge windows from ACPI; if necessary, use "pci=use_crs" and report a bug
[ 0.153634] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3f])
[ 0.153747] pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored)
[ 0.153751] pci_root PNP0A03:00: host bridge window [io 0x0d00-0xffff] (ignored)
[ 0.153755] pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
[ 0.153759] pci_root PNP0A03:00: host bridge window [mem 0x000c0000-0x000dffff] (ignored)
[ 0.153763] pci_root PNP0A03:00: host bridge window [mem 0xcf800000-0xfebfffff] (ignored)
[ 0.153766] PCI: root bus 00: using default resources
[ 0.153839] PCI host bridge to bus 0000:00
[ 0.153844] pci_bus 0000:00: root bus resource [io 0x0000-0xffff]
[ 0.153847] pci_bus 0000:00: root bus resource [mem 0x00000000-0xfffffffff]
[ 0.153861] pci 0000:00:00.0: [8086:2770] type 0 class 0x000600
[ 0.153926] pci 0000:00:02.0: [8086:2772] type 0 class 0x000300
[ 0.153942] pci 0000:00:02.0: reg 10: [mem 0xe2000000-0xe207ffff]
[ 0.153950] pci 0000:00:02.0: reg 14: [io 0xb000-0xb007]
[ 0.153959] pci 0000:00:02.0: reg 18: [mem 0xd0000000-0xdfffffff pref]
[ 0.153967] pci 0000:00:02.0: reg 1c: [mem 0xe2080000-0xe20bffff]
[ 0.154057] pci 0000:00:1b.0: [8086:27d8] type 0 class 0x000403
[ 0.154076] pci 0000:00:1b.0: reg 10: [mem 0xe20c0000-0xe20c3fff 64bit]
[ 0.154159] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.154188] pci 0000:00:1c.0: [8086:27d0] type 1 class 0x000604
[ 0.154272] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 0.154303] pci 0000:00:1c.1: [8086:27d2] type 1 class 0x000604
[ 0.154387] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
[ 0.154420] pci 0000:00:1d.0: [8086:27c8] type 0 class 0x000c03
[ 0.154468] pci 0000:00:1d.0: reg 20: [io 0xb400-0xb41f]
[ 0.154507] pci 0000:00:1d.1: [8086:27c9] type 0 class 0x000c03
[ 0.154555] pci 0000:00:1d.1: reg 20: [io 0xb800-0xb81f]
[ 0.154593] pci 0000:00:1d.2: [8086:27ca] type 0 class 0x000c03
[ 0.154642] pci 0000:00:1d.2: reg 20: [io 0xbc00-0xbc1f]
[ 0.154682] pci 0000:00:1d.3: [8086:27cb] type 0 class 0x000c03
[ 0.154731] pci 0000:00:1d.3: reg 20: [io 0xc000-0xc01f]
[ 0.154782] pci 0000:00:1d.7: [8086:27cc] type 0 class 0x000c03
[ 0.154804] pci 0000:00:1d.7: reg 10: [mem 0xe20c4000-0xe20c43ff]
[ 0.154906] pci 0000:00:1e.0: [8086:244e] type 1 class 0x000604
[ 0.154986] pci 0000:00:1f.0: [8086:27b8] type 0 class 0x000601
[ 0.155081] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0800 (mask 000f)
[ 0.155087] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 0290 (mask 000f)
[ 0.155138] pci 0000:00:1f.1: [8086:27df] type 0 class 0x000101
[ 0.155155] pci 0000:00:1f.1: reg 10: [io 0x0000-0x0007]
[ 0.155167] pci 0000:00:1f.1: reg 14: [io 0x0000-0x0003]
[ 0.155178] pci 0000:00:1f.1: reg 18: [io 0x0000-0x0007]
[ 0.155189] pci 0000:00:1f.1: reg 1c: [io 0x0000-0x0003]
[ 0.155201] pci 0000:00:1f.1: reg 20: [io 0xf000-0xf00f]
[ 0.155245] pci 0000:00:1f.2: [8086:27c0] type 0 class 0x000101
[ 0.155263] pci 0000:00:1f.2: reg 10: [io 0xd400-0xd407]
[ 0.155274] pci 0000:00:1f.2: reg 14: [io 0xd800-0xd803]
[ 0.155284] pci 0000:00:1f.2: reg 18: [io 0xdc00-0xdc07]
[ 0.155294] pci 0000:00:1f.2: reg 1c: [io 0xe000-0xe003]
[ 0.155304] pci 0000:00:1f.2: reg 20: [io 0xe400-0xe40f]
[ 0.155348] pci 0000:00:1f.2: PME# supported from D3hot
[ 0.155368] pci 0000:00:1f.3: [8086:27da] type 0 class 0x000c05
[ 0.155427] pci 0000:00:1f.3: reg 20: [io 0x0500-0x051f]
[ 0.155517] pci 0000:00:1c.0: PCI bridge to [bus 01-01]
[ 0.155522] pci 0000:00:1c.0: bridge window [io 0x9000-0x9fff]
[ 0.155604] pci 0000:02:00.0: [10ec:8136] type 0 class 0x000200
[ 0.155626] pci 0000:02:00.0: reg 10: [io 0xa000-0xa0ff]
[ 0.155661] pci 0000:02:00.0: reg 18: [mem 0xe1000000-0xe1000fff 64bit]
[ 0.155703] pci 0000:02:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
[ 0.155794] pci 0000:02:00.0: supports D1 D2
[ 0.155796] pci 0000:02:00.0: PME# supported from D1 D2 D3hot D3cold
[ 0.155827] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
[ 0.155840] pci 0000:00:1c.1: PCI bridge to [bus 02-02]
[ 0.155846] pci 0000:00:1c.1: bridge window [io 0xa000-0xafff]
[ 0.155851] pci 0000:00:1c.1: bridge window [mem 0xe0000000-0xe1ffffff]
[ 0.155928] pci 0000:00:1e.0: PCI bridge to [bus 03-03] (subtractive decode)
[ 0.155934] pci 0000:00:1e.0: bridge window [io 0x8000-0x8fff]
[ 0.155944] pci 0000:00:1e.0: bridge window [io 0x0000-0xffff] (subtractive decode)
[ 0.155947] pci 0000:00:1e.0: bridge window [mem 0x00000000-0xfffffffff] (subtractive decode)
[ 0.155969] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 0.156112] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX0._PRT]
[ 0.156164] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEX1._PRT]
[ 0.156226] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
[ 0.156341] pci0000:00: Requesting ACPI _OSC control (0x1d)
[ 0.156346] pci0000:00: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d
[ 0.156349] ACPI _OSC control for PCIe not granted, disabling ASPM
[ 0.166267] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
[ 0.166357] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
[ 0.166444] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
[ 0.166529] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
[ 0.166614] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
[ 0.166711] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
[ 0.166797] ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
[ 0.166884] ACPI: PCI Interrupt Link [LNK1] (IRQs *3 4 5 6 7 9 10 11 12 14 15)
[ 0.167018] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.167018] vgaarb: loaded
[ 0.167018] vgaarb: bridge control possible 0000:00:02.0
[ 0.167018] PCI: Using ACPI for IRQ routing
[ 0.168569] PCI: pci_cache_line_size set to 64 bytes
[ 0.168650] reserve RAM buffer: 000000000009f800 - 000000000009ffff
[ 0.168654] reserve RAM buffer: 00000000cf7f0000 - 00000000cfffffff
[ 0.168821] NetLabel: Initializing
[ 0.168824] NetLabel: domain hash size = 128
[ 0.168826] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.168852] NetLabel: unlabeled traffic allowed by default
[ 0.168860] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
[ 0.168866] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 0.168873] hpet0: 3 comparators, 64-bit 14.318180 MHz counter
[ 0.181124] Switching to clocksource hpet
[ 0.191359] pnp: PnP ACPI init
[ 0.191394] ACPI: bus type pnp registered
[ 0.191545] pnp 00:00: [bus 00-3f]
[ 0.191550] pnp 00:00: [io 0x0cf8-0x0cff]
[ 0.191553] pnp 00:00: [io 0x0000-0x0cf7 window]
[ 0.191557] pnp 00:00: [io 0x0d00-0xffff window]
[ 0.191560] pnp 00:00: [mem 0x000a0000-0x000bffff window]
[ 0.191563] pnp 00:00: [mem 0x000c0000-0x000dffff window]
[ 0.191566] pnp 00:00: [mem 0xcf800000-0xfebfffff window]
[ 0.191641] pnp 00:00: Plug and Play ACPI device, IDs PNP0a03 (active)
[ 0.191734] pnp 00:01: [io 0x0010-0x001f]
[ 0.191738] pnp 00:01: [io 0x0022-0x003f]
[ 0.191740] pnp 00:01: [io 0x0044-0x005f]
[ 0.191743] pnp 00:01: [io 0x0062-0x0063]
[ 0.191746] pnp 00:01: [io 0x0065-0x006f]
[ 0.191748] pnp 00:01: [io 0x0074-0x007f]
[ 0.191751] pnp 00:01: [io 0x0091-0x0093]
[ 0.191753] pnp 00:01: [io 0x00a2-0x00bf]
[ 0.191756] pnp 00:01: [io 0x00e0-0x00ef]
[ 0.191758] pnp 00:01: [io 0x04d0-0x04d1]
[ 0.191761] pnp 00:01: [io 0x0290-0x029f]
[ 0.191763] pnp 00:01: [io 0x0800-0x087f]
[ 0.191766] pnp 00:01: [io 0x0290-0x0294]
[ 0.191769] pnp 00:01: [io 0x0880-0x088f]
[ 0.191858] system 00:01: [io 0x04d0-0x04d1] has been reserved
[ 0.191863] system 00:01: [io 0x0290-0x029f] has been reserved
[ 0.191866] system 00:01: [io 0x0800-0x087f] has been reserved
[ 0.191870] system 00:01: [io 0x0290-0x0294] has been reserved
[ 0.191873] system 00:01: [io 0x0880-0x088f] has been reserved
[ 0.191879] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.191900] pnp 00:02: [dma 4]
[ 0.191903] pnp 00:02: [io 0x0000-0x000f]
[ 0.191906] pnp 00:02: [io 0x0080-0x0090]
[ 0.191909] pnp 00:02: [io 0x0094-0x009f]
[ 0.191911] pnp 00:02: [io 0x00c0-0x00df]
[ 0.191969] pnp 00:02: Plug and Play ACPI device, IDs PNP0200 (active)
[ 0.192037] pnp 00:03: [io 0x0070-0x0073]
[ 0.192054] pnp 00:03: [irq 8]
[ 0.192102] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 0.192119] pnp 00:04: [io 0x0061]
[ 0.192163] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
[ 0.192180] pnp 00:05: [io 0x00f0-0x00ff]
[ 0.192188] pnp 00:05: [irq 13]
[ 0.192237] pnp 00:05: Plug and Play ACPI device, IDs PNP0c04 (active)
[ 0.192570] pnp 00:06: [io 0x03f8-0x03ff]
[ 0.192579] pnp 00:06: [irq 4]
[ 0.192673] pnp 00:06: Plug and Play ACPI device, IDs PNP0501 (active)
[ 0.192928] pnp 00:07: [io 0x0378-0x037f]
[ 0.192936] pnp 00:07: [irq 7]
[ 0.193013] pnp 00:07: Plug and Play ACPI device, IDs PNP0400 (active)
[ 0.193189] pnp 00:08: [io 0x0400-0x04bf]
[ 0.193258] system 00:08: [io 0x0400-0x04bf] has been reserved
[ 0.193264] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.193583] pnp 00:09: [mem 0xf0000000-0xf3ffffff]
[ 0.193671] system 00:09: [mem 0xf0000000-0xf3ffffff] has been reserved
[ 0.193677] system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.193888] pnp 00:0a: [mem 0x000cc000-0x000d3fff]
[ 0.193892] pnp 00:0a: [mem 0x000f0000-0x000f7fff]
[ 0.193895] pnp 00:0a: [mem 0x000f8000-0x000fbfff]
[ 0.193898] pnp 00:0a: [mem 0x000fc000-0x000fffff]
[ 0.193900] pnp 00:0a: [mem 0xcf7f0000-0xcf7fffff]
[ 0.193903] pnp 00:0a: [mem 0x00000000-0x0009ffff]
[ 0.193906] pnp 00:0a: [mem 0x00100000-0xcf7effff]
[ 0.193909] pnp 00:0a: [mem 0xfec00000-0xfec00fff]
[ 0.193912] pnp 00:0a: [mem 0xfed13000-0xfed1dfff]
[ 0.193915] pnp 00:0a: [mem 0xfed20000-0xfed8ffff]
[ 0.193918] pnp 00:0a: [mem 0xfee00000-0xfee00fff]
[ 0.193920] pnp 00:0a: [mem 0xffb00000-0xffb7ffff]
[ 0.193923] pnp 00:0a: [mem 0xfff00000-0xffffffff]
[ 0.193926] pnp 00:0a: [mem 0x000e0000-0x000effff]
[ 0.194017] system 00:0a: [mem 0x000cc000-0x000d3fff] has been reserved
[ 0.194022] system 00:0a: [mem 0x000f0000-0x000f7fff] could not be reserved
[ 0.194026] system 00:0a: [mem 0x000f8000-0x000fbfff] could not be reserved
[ 0.194030] system 00:0a: [mem 0x000fc000-0x000fffff] could not be reserved
[ 0.194034] system 00:0a: [mem 0xcf7f0000-0xcf7fffff] could not be reserved
[ 0.194038] system 00:0a: [mem 0x00000000-0x0009ffff] could not be reserved
[ 0.194042] system 00:0a: [mem 0x00100000-0xcf7effff] could not be reserved
[ 0.194046] system 00:0a: [mem 0xfec00000-0xfec00fff] could not be reserved
[ 0.194049] system 00:0a: [mem 0xfed13000-0xfed1dfff] has been reserved
[ 0.194053] system 00:0a: [mem 0xfed20000-0xfed8ffff] has been reserved
[ 0.194057] system 00:0a: [mem 0xfee00000-0xfee00fff] has been reserved
[ 0.194060] system 00:0a: [mem 0xffb00000-0xffb7ffff] has been reserved
[ 0.194064] system 00:0a: [mem 0xfff00000-0xffffffff] has been reserved
[ 0.194071] system 00:0a: [mem 0x000e0000-0x000effff] has been reserved
[ 0.194077] system 00:0a: Plug and Play ACPI device, IDs PNP0c01 (active)
[ 0.194109] pnp 00:0b: [mem 0xffb80000-0xffbfffff]
[ 0.194171] pnp 00:0b: Plug and Play ACPI device, IDs INT0800 (active)
[ 0.194180] pnp: PnP ACPI: found 12 devices
[ 0.194182] ACPI: ACPI bus type pnp unregistered
[ 0.203774] PCI: max bus depth: 1 pci_try_num: 2
[ 0.203813] pci 0000:00:1c.1: BAR 15: assigned [mem 0xe2100000-0xe21fffff pref]
[ 0.203820] pci 0000:00:1c.1: BAR 15: assigned [mem 0xe2100000-0xe23fffff pref]
[ 0.203825] pci 0000:00:1c.0: BAR 14: assigned [mem 0xe2400000-0xe25fffff]
[ 0.203830] pci 0000:00:1c.0: BAR 15: assigned [mem 0xe2600000-0xe27fffff 64bit pref]
[ 0.203834] pci 0000:00:1c.0: PCI bridge to [bus 01-01]
[ 0.203839] pci 0000:00:1c.0: bridge window [io 0x9000-0x9fff]
[ 0.203845] pci 0000:00:1c.0: bridge window [mem 0xe2400000-0xe25fffff]
[ 0.203851] pci 0000:00:1c.0: bridge window [mem 0xe2600000-0xe27fffff 64bit pref]
[ 0.203860] pci 0000:02:00.0: BAR 6: assigned [mem 0xe2100000-0xe211ffff pref]
[ 0.203864] pci 0000:00:1c.1: PCI bridge to [bus 02-02]
[ 0.203868] pci 0000:00:1c.1: bridge window [io 0xa000-0xafff]
[ 0.203874] pci 0000:00:1c.1: bridge window [mem 0xe0000000-0xe1ffffff]
[ 0.203880] pci 0000:00:1c.1: bridge window [mem 0xe2100000-0xe23fffff pref]
[ 0.203887] pci 0000:00:1e.0: PCI bridge to [bus 03-03]
[ 0.203891] pci 0000:00:1e.0: bridge window [io 0x8000-0x8fff]
[ 0.203939] pci 0000:00:1e.0: setting latency timer to 64
[ 0.203945] pci_bus 0000:00: resource 4 [io 0x0000-0xffff]
[ 0.203948] pci_bus 0000:00: resource 5 [mem 0x00000000-0xfffffffff]
[ 0.203952] pci_bus 0000:01: resource 0 [io 0x9000-0x9fff]
[ 0.203955] pci_bus 0000:01: resource 1 [mem 0xe2400000-0xe25fffff]
[ 0.203958] pci_bus 0000:01: resource 2 [mem 0xe2600000-0xe27fffff 64bit pref]
[ 0.203962] pci_bus 0000:02: resource 0 [io 0xa000-0xafff]
[ 0.203965] pci_bus 0000:02: resource 1 [mem 0xe0000000-0xe1ffffff]
[ 0.203968] pci_bus 0000:02: resource 2 [mem 0xe2100000-0xe23fffff pref]
[ 0.203972] pci_bus 0000:03: resource 0 [io 0x8000-0x8fff]
[ 0.203975] pci_bus 0000:03: resource 4 [io 0x0000-0xffff]
[ 0.203978] pci_bus 0000:03: resource 5 [mem 0x00000000-0xfffffffff]
[ 0.204032] NET: Registered protocol family 2
[ 0.204338] IP route cache hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.206849] TCP established hash table entries: 524288 (order: 11, 8388608 bytes)
[ 0.211394] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[ 0.211962] TCP: Hash tables configured (established 524288 bind 65536)
[ 0.211965] TCP reno registered
[ 0.211987] UDP hash table entries: 2048 (order: 4, 65536 bytes)
[ 0.212049] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
[ 0.212209] NET: Registered protocol family 1
[ 0.212240] pci 0000:00:02.0: Boot video device
[ 0.212425] PCI: CLS 32 bytes, default 64
[ 0.212520] Unpacking initramfs...
[ 0.304914] Freeing initrd memory: 2988k freed
[ 0.307162] audit: initializing netlink socket (disabled)
[ 0.307182] type=2000 audit(1334738548.306:1): initialized
[ 0.307834] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.311581] VFS: Disk quotas dquot_6.5.2
[ 0.311675] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.311824] msgmni has been set to 6512
[ 0.312151] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[ 0.312203] io scheduler noop registered
[ 0.312207] io scheduler deadline registered
[ 0.312333] io scheduler cfq registered (default)
[ 0.312521] pcieport 0000:00:1c.0: irq 40 for MSI/MSI-X
[ 0.312650] pcieport 0000:00:1c.1: irq 41 for MSI/MSI-X
[ 0.312856] vesafb: mode is 1024x768x32, linelength=4096, pages=0
[ 0.312859] vesafb: scrolling: redraw
[ 0.312863] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 0.313479] vesafb: framebuffer at 0xd0000000, mapped to 0xffffc90005100000, using 3072k, total 3072k
[ 0.345759] Console: switching to colour frame buffer device 128x48
[ 0.377873] fb0: VESA VGA frame buffer device
[ 0.377932] GHES: HEST is not enabled!
[ 0.378043] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 0.398611] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.419664] 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.419939] Linux agpgart interface v0.103
[ 0.420083] i8042: PNP: No PS/2 controller found. Probing ports directly.
[ 0.420471] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.420523] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 0.420725] mousedev: PS/2 mouse device common for all mice
[ 0.420858] rtc_cmos 00:03: RTC can wake from S4
[ 0.421016] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[ 0.421045] rtc0: alarms up to one month, 242 bytes nvram, hpet irqs
[ 0.421060] cpuidle: using governor ladder
[ 0.421063] cpuidle: using governor menu
[ 0.421369] TCP cubic registered
[ 0.421636] NET: Registered protocol family 10
[ 0.422361] NET: Registered protocol family 17
[ 0.422369] Registering the dns_resolver key type
[ 0.422613] PM: Hibernation image not present or could not be loaded.
[ 0.422626] registered taskstats version 1
[ 0.423248] rtc_cmos 00:03: setting system clock to 2012-04-18 08:42:29 UTC (1334738549)
[ 0.423302] Initializing network drop monitor service
[ 0.424697] Freeing unused kernel memory: 732k freed
[ 0.425077] Write protecting the kernel read-only data: 8192k
[ 0.432038] Freeing unused kernel memory: 1632k freed
[ 0.435658] Freeing unused kernel memory: 656k freed
[ 0.448943] udevd[37]: starting version 182
[ 0.497512] usbcore: registered new interface driver usbfs
[ 0.497555] usbcore: registered new interface driver hub
[ 0.497642] usbcore: registered new device driver usb
[ 0.498708] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.498793] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[ 0.498798] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[ 0.498837] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
[ 0.498865] ehci_hcd 0000:00:1d.7: using broken periodic workaround
[ 0.502771] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
[ 0.502799] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xe20c4000
[ 0.510593] uhci_hcd: USB Universal Host Controller Interface driver
[ 0.512088] SCSI subsystem initialized
[ 0.512269] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 0.513131] hub 1-0:1.0: USB hub found
[ 0.513140] hub 1-0:1.0: 8 ports detected
[ 0.513313] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[ 0.513319] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 0.513410] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
[ 0.513449] uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000b400
[ 0.513901] hub 2-0:1.0: USB hub found
[ 0.513910] hub 2-0:1.0: 2 ports detected
[ 0.514034] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 0.514039] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 0.514052] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
[ 0.514121] uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000b800
[ 0.514684] hub 3-0:1.0: USB hub found
[ 0.514691] hub 3-0:1.0: 2 ports detected
[ 0.514840] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[ 0.514846] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[ 0.514861] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
[ 0.514904] uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000bc00
[ 0.515122] hub 4-0:1.0: USB hub found
[ 0.515129] hub 4-0:1.0: 2 ports detected
[ 0.515245] uhci_hcd 0000:00:1d.3: setting latency timer to 64
[ 0.515250] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[ 0.515262] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
[ 0.515325] uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000c000
[ 0.516908] hub 5-0:1.0: USB hub found
[ 0.516919] hub 5-0:1.0: 2 ports detected
[ 0.518287] libata version 3.00 loaded.
[ 0.519240] ata_piix 0000:00:1f.1: version 2.13
[ 0.519301] ata_piix 0000:00:1f.1: setting latency timer to 64
[ 0.521189] scsi0 : ata_piix
[ 0.521850] scsi1 : ata_piix
[ 0.522635] ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xf000 irq 14
[ 0.522641] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xf008 irq 15
[ 0.522741] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
[ 0.522797] ata_piix 0000:00:1f.2: setting latency timer to 64
[ 0.522921] ata2: port disabled--ignoring
[ 0.523388] scsi2 : ata_piix
[ 0.526732] scsi3 : ata_piix
[ 0.527628] ata3: SATA max UDMA/133 cmd 0xd400 ctl 0xd800 bmdma 0xe400 irq 19
[ 0.527633] ata4: SATA max UDMA/133 cmd 0xdc00 ctl 0xe000 bmdma 0xe408 irq 19
[ 0.703487] ata4.00: CFA: CF Card, Ver6.04, max UDMA/133
[ 0.703493] ata4.00: 31227840 sectors, multi 1: LBA48
[ 0.703500] ata4.01: CFA: CF Card, Ver6.04, max UDMA/133
[ 0.703503] ata4.01: 31227840 sectors, multi 1: LBA48
[ 0.710158] ata4.00: configured for UDMA/133
[ 0.716816] ata4.01: configured for UDMA/133
[ 0.716974] scsi 3:0:0:0: Direct-Access ATA CF Card Ver6 PQ: 0 ANSI: 5
[ 0.717369] scsi 3:0:1:0: Direct-Access ATA CF Card Ver6 PQ: 0 ANSI: 5
[ 0.724905] sd 3:0:0:0: [sda] 31227840 512-byte logical blocks: (15.9 GB/14.8 GiB)
[ 0.725016] sd 3:0:1:0: [sdb] 31227840 512-byte logical blocks: (15.9 GB/14.8 GiB)
[ 0.725077] sd 3:0:0:0: [sda] Write Protect is off
[ 0.725082] sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 0.725155] sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 0.725162] sd 3:0:1:0: [sdb] Write Protect is off
[ 0.725167] sd 3:0:1:0: [sdb] Mode Sense: 00 3a 00 00
[ 0.725205] sd 3:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 0.729476] sda: sda1 sda2
[ 0.730031] sdb: sdb1 sdb2
[ 0.730174] sd 3:0:0:0: [sda] Attached SCSI disk
[ 0.730514] sd 3:0:1:0: [sdb] Attached SCSI disk
[ 0.817477] usb 1-6: new high-speed USB device number 2 using ehci_hcd
[ 0.879397] mdassemble: sending ioctl 800c0910 to a partition!
[ 0.879403] mdassemble: sending ioctl 800c0910 to a partition!
[ 0.879413] mdassemble: sending ioctl 1261 to a partition!
[ 0.879416] mdassemble: sending ioctl 1261 to a partition!
[ 0.879764] mdassemble: sending ioctl 800c0910 to a partition!
[ 0.879768] mdassemble: sending ioctl 800c0910 to a partition!
[ 0.879773] mdassemble: sending ioctl 1261 to a partition!
[ 0.879776] mdassemble: sending ioctl 1261 to a partition!
[ 0.881551] mdassemble: sending ioctl 800c0910 to a partition!
[ 0.881555] mdassemble: sending ioctl 800c0910 to a partition!
[ 0.884599] md: md1 stopped.
[ 0.888847] md: bind<sdb2>
[ 0.889106] md: bind<sda2>
[ 0.890802] md: raid0 personality registered for level 0
[ 0.891196] bio: create slab <bio-1> at 1
[ 0.891208] md/raid0:md1: md_size is 61628416 sectors.
[ 0.891212] md: RAID0 configuration for md1 - 1 zone
[ 0.891214] md: zone0=[sda2/sdb2]
[ 0.891222] zone-offset= 0KB, device-offset= 0KB, size= 30814208KB
[ 0.891225]
[ 0.891237] md1: detected capacity change from 0 to 31553748992
[ 0.941428] hub 1-6:1.0: USB hub found
[ 0.941473] hub 1-6:1.0: 4 ports detected
[ 0.954302] md1: unknown partition table
[ 1.131212] EXT4-fs (md1): mounting ext3 file system using the ext4 subsystem
[ 1.135334] EXT4-fs (md1): mounted filesystem with ordered data mode. Opts: (null)
[ 1.220124] usb 1-6.1: new low-speed USB device number 3 using ehci_hcd
[ 1.306694] Refined TSC clocksource calibration: 2800.001 MHz.
[ 1.306703] Switching to clocksource tsc
[ 1.403502] usb 1-6.2: new low-speed USB device number 4 using ehci_hcd
[ 1.518102] udevd[147]: starting version 182
[ 1.649651] input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6.1/1-6.1:1.0/input/input0
[ 1.649790] generic-usb 0003:046D:C00E.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:1d.7-6.1/input0
[ 1.652254] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
[ 1.652264] ACPI: Power Button [PWRB]
[ 1.652742] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[ 1.652749] ACPI: Power Button [PWRF]
[ 1.660429] input: Chicony Saitek Eclipse II Keyboard as /devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6.2/1-6.2:1.0/input/input3
[ 1.660673] generic-usb 0003:06A3:8021.0002: input,hidraw1: USB HID v1.11 Keyboard [Chicony Saitek Eclipse II Keyboard] on usb-0000:00:1d.7-6.2/input0
[ 1.670411] IT8718 SuperIO detected.
[ 1.670725] parport_pc 00:07: reported by Plug and Play ACPI
[ 1.670774] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[ 1.684890] input: Chicony Saitek Eclipse II Keyboard as /devices/pci0000:00/0000:00:1d.7/usb1/1-6/1-6.2/1-6.2:1.1/input/input4
[ 1.685402] generic-usb 0003:06A3:8021.0003: input,hiddev0,hidraw2: USB HID v1.11 Device [Chicony Saitek Eclipse II Keyboard] on usb-0000:00:1d.7-6.2/input1
[ 1.685434] usbcore: registered new interface driver usbhid
[ 1.685437] usbhid: USB HID core driver
[ 1.706305] intel_rng: FWH not detected
[ 1.712611] leds_ss4200: no LED devices found
[ 1.720342] iTCO_vendor_support: vendor-support=0
[ 1.722921] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07
[ 1.723090] iTCO_wdt: Found a ICH7 or ICH7R TCO device (Version=2, TCOBASE=0x0460)
[ 1.723619] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 1.729909] input: PC Speaker as /devices/platform/pcspkr/input/input5
[ 1.733254] [drm] Initialized drm 1.1.0 20060810
[ 1.744963] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 1.745106] r8169 0000:02:00.0: irq 42 for MSI/MSI-X
[ 1.745933] r8169 0000:02:00.0: eth0: RTL8101e at 0xffffc900058d2000, 00:1d:7d:c1:af:ac, XID 14000000 IRQ 42
[ 1.765162] agpgart-intel 0000:00:00.0: Intel 945G Chipset
[ 1.765303] agpgart-intel 0000:00:00.0: detected gtt size: 262144K total, 262144K mappable
[ 1.766152] agpgart-intel 0000:00:00.0: detected 8192K stolen memory
[ 1.766499] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
[ 1.770284] snd_hda_intel 0000:00:1b.0: irq 43 for MSI/MSI-X
[ 1.841921] ppdev: user-space parallel port driver
[ 1.925606] input: HDA Intel Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input6
[ 1.925802] input: HDA Intel Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
[ 1.927348] input: HDA Intel Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[ 1.927572] input: HDA Intel Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[ 1.927906] input: HDA Intel Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[ 1.929058] i915 0000:00:02.0: setting latency timer to 64
[ 2.007384] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 2.007389] [drm] Driver supports precise vblank timestamp query.
[ 2.033489] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 2.052399] [drm] initialized overlay support
[ 2.130899] checking generic (d0000000 300000) vs hw (d0000000 10000000)
[ 2.130905] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
[ 2.130988] Console: switching to colour dummy device 80x25
[ 2.131832] fbcon: inteldrmfb (fb0) is primary device
[ 2.170693] Console: switching to colour frame buffer device 200x56
[ 2.177031] fb0: inteldrmfb frame buffer device
[ 2.177034] drm: registered panic notifier
[ 2.177093] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[ 2.306851] EXT4-fs (md1): re-mounted. Opts: (null)
[ 2.369941] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem
[ 2.375033] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
[ 2.413220] Adding 102396k swap on /dev/sdb1. Priority:-1 extents:1 across:102396k
[ 2.994535] r8169 0000:02:00.0: eth0: link down
[ 2.994545] r8169 0000:02:00.0: eth0: link down
[ 2.995025] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 5.138610] r8169 0000:02:00.0: eth0: link up
[ 5.139067] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 15.736686] eth0: no IPv6 routers present
sh-4.2# EDIT:sh-4.2# cat /proc/mdstat
Personalities : [raid0]
md0 : active raid0 sdb2[0] sdc2[1]
30717952 blocks super 1.2 512k chunks
unused devices: <none>
sh-4.2#
Further data:
sh-4.2# cat /proc/mdstat
Personalities : [raid0]
md0 : active raid0 sdb2[0] sdc2[1]
30717952 blocks super 1.2 512k chunks
unused devices: <none>
sh-4.2#
Thus, it seems that raid0 is established and therefore must be running at twice the device read speed even though hdparm does not recognize it.
One observation regarding dmesg is that the pio and udma data does no longer appear. This would suggest a kernel change eleiminating the udma factor. Perhaps that limits the raid array as well.
Any insight into this matter is appreciated.
EDIT: 10/1/15 As referenced in the last edit for post#59, I am starting a new thread of EDITS to make it perform more easily. After upgrade to linux-4.2.2-1-x86...I discovered an anomaly in the use of compact flash devices.
This occurred after creating a clone of my /dev/sda, a compact flash device installed with btrfs filesystem. The clone was made to a compact flash device connected via an adapter to a sata port.. The device is a 32gb MONSTER 500x udma 6 and produced a very intriuging result in hdparm read speed. The read speed is presented below:
/dev/sdd:
Timing buffered disk reads: 1394 MB in 3.00 seconds = 464.58 MB/sec
sh-4.3#
I repeated this procedure several times and received the same result...awesome speed...actually faster than the speed limit for SATAII.
This may mean an error in the hdparm system for this device. Nevertheless, I will study this phenom some at length.
EDIT: 10/2/15....Further info on the anomaly indicates a dependence on Journal log being present. With journal log in /var removed, the speed is 34MB/s.
Reinvoking journal log permits the following results:
sh-4.3# systemd-analyze
Startup finished in 315ms (kernel) + 3.283s (initrd) + 553ms (userspace) = 4.152s
sh-4.3# hdparm -t /dev/sdd
/dev/sdd:
Timing buffered disk reads: 1342 MB in 3.00 seconds = 447.07 MB/sec
sh-4.3# hdparm -tT /dev/sdd
/dev/sdd:
Timing cached reads: 2298 MB in 2.00 seconds = 1149.05 MB/sec
Timing buffered disk reads: 1394 MB in 3.00 seconds = 464.32 MB/sec
sh-4.3#
This arrangement permitted the cp of a 1.1G file from root to /var/local at a spped of 130MB/s. Thus it would seem to be a valid speed indication. The systemd-analyze time is indicative as well. I may try another compact flash of this type under the same conditions.This setup of archlinux is full-size device btrfs filesystem and is 32GB in size and operates root only...connected via adapter to SATAII port.
EDIT: 10/2/15.....Repeated the test with hdparm with the clone device /dev/sda removed. The result was hdparm reported 34MB/s. Reinstalling the clone device /dev/sda and rerunning hdparm resulted in the 467MB/s result in hdparm. Thus, both devices performed together to produce the result..
EDIT 10/2/15 ....The arrangement of the clones is one is mounted via adapter to an IDE cable while the other(MONSTER) is connected via adapter to SATAII port. Thus, the clones work together for the hdparm test. Indications are that the speed of file transfers is greater than normal IDE transfer speed. A second clone device installed in the IDE slot produces similar results.
Whether the operations necessary for proper execution of programs occurs with this collusion is not apparent at this time,. I expect some difficulties altho because it is SATA based, the possibilities are improbabale.
The hdparm read speed is greater than that shown by ssd's in my system. They are in the 180 to 220 area.
EDIT: 10/2/15....Performed a boot using a USB connection of the clone instead of the IDE setup. This permitted the high read speed in hdparm. Removed the USB compact flash device and retained the read speed in hdparm at 467MB/s.
Performed a file transfer from /root file to /tmp with the following result:
sh-4.3# time cp /ray90thFINAL2.wmv /tmp
real 0m3.033s
user 0m0.007s
sys 0m2.143
Calculated transfer speed is 362MB/s.....
EDIT: Performed the following on device /sdc......
sh-4.3# hdparm -I /dev/sdc
/dev/sdc:
CompactFlash ATA device
Model Number: CF Card
Serial Number: CB510728040100004572
Firmware Revision: Ver6.05
Standards:
Supported: 5 4
Likely used: 6
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 62455680
LBA user addressable sectors: 62455680
LBA48 user addressable sectors: 62455680
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 30495 MBytes
device size with M = 1000*1000: 31977 MBytes (31 GB)
cache/buffer size = 1 KBytes (type=DualPort)
Nominal Media Rotation Rate: Solid State Device
Capabilities:
LBA, IORDY(cannot be disabled)
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 1 Current = 1
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
Power Management feature set
Write cache
* WRITE_BUFFER command
* READ_BUFFER command
* NOP cmd
* CFA feature set
* 48-bit Address feature set
* Mandatory FLUSH_CACHE
CFA max advanced io_udma cycle time: 80ns
CFA max advanced mem_udma cycle time: 80ns
* CFA advanced modes: pio5 pio6 mdma3 mdma4 io_udma4 io_udma5 io_udma6 io_udma7 io_udma8 io_udma9 *io_udma10 mem_udma4 mem_udma5 mem_udma6 mem_udma7 mem_udma8 mem_udma9 *mem_udma10
* CFA Power Level 1 (max 750mA)
Checksum: correct
sh-4.3# hdparm -I /dev/sdc
/dev/sdc:
CompactFlash ATA device
Model Number: CF Card
Serial Number: CB510728040100004572
Firmware Revision: Ver6.05
Standards:
Supported: 5 4
Likely used: 6
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 62455680
LBA user addressable sectors: 62455680
LBA48 user addressable sectors: 62455680
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 30495 MBytes
device size with M = 1000*1000: 31977 MBytes (31 GB)
cache/buffer size = 1 KBytes (type=DualPort)
Nominal Media Rotation Rate: Solid State Device
Capabilities:
LBA, IORDY(cannot be disabled)
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 1 Current = 1
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
Power Management feature set
Write cache
* WRITE_BUFFER command
* READ_BUFFER command
* NOP cmd
* CFA feature set
* 48-bit Address feature set
* Mandatory FLUSH_CACHE
CFA max advanced io_udma cycle time: 80ns
CFA max advanced mem_udma cycle time: 80ns
* CFA advanced modes: pio5 pio6 mdma3 mdma4 io_udma4 io_udma5 io_udma6 io_udma7 io_udma8 io_udma9 *io_udma10 mem_udma4 mem_udma5 mem_udma6 mem_udma7 mem_udma8 mem_udma9 *mem_udma10
* CFA Power Level 1 (max 750mA)
Checksum: correct
sh-4.3# hdparm -tT /dev/sdc
/dev/sdc:
Timing cached reads: 2358 MB in 2.00 seconds = 1179.07 MB/sec
Timing buffered disk reads: 1408 MB in 3.00 seconds = 468.92 MB/sec
sh-4.3#
This info gives insight to the parameters available for device MONSTER compact flash.
EDIT: 10/7/115....Installed powerpill via AUR and enjoy the speedy upgradeson all my systems. Xyne has produced a really fine helper for pacman downloads. Not more than 2o seconds download of kernel upgrade. Still haven't had any word on when the quantom-dot/nanocrystal monitors will be on retail shelves. Not all MONSTER devices respond as does the one I have installed. It is probably a manufacturing error that allows udma 10 performance as indicated by the hdparm data.
EDIT: 10/13/15...Upgraded to linux-4.2.3-1-x86.... in all systems with no problems. Still not seeing any new monitors in local retail. Powerpill is working very well to increase download in pacman. Very fine package by xyne. Enjoying the new twcable speeds for the same price as adsl.
EDIT: 10/28/15...Upgraded to linux-4.2.4-1-x86.....with no problems. Trying out phoronix-test-suite package...fascinating....
EDIT: 10/29/15.......Upgraded to linux-4.2.5-1-x86...No problems in upgrade. Still no quantom-dot monitors in USA. Hype..Hype.....Learning how to phoronix.....
EDIT: 12/10/15 Installed bauerbill from aur and am learning the ropes in that package. It seems to run a bit faster than powerpill alone. As to the philips 27" monitor with quantom-dot display, I give up waiting for it. The hype has waned and no displays in USA so far. So for now, its learning how to utilize the details in bauerbill. No recent upgrades have surfaced.
EDIT: 12/31/15 Last day of the year ....upgraded to linux-4.3.3-2-x86.. into all systems using bauerbill. All working well in new upgrade. Still await the quantom-dot display which hasn't materialized. I don't expect it to show in 2016 due to conditions in the far east.
Wish everyone a prosperous New Year filled with joy and gladness.
EDIT....1/20/16....Upgraded to linux-4.3.3-3-x86 ....in all systems with no problems. Do not see any trace of quantom-dot monitors so guess it won/t happen in my lifetime! Bauerbill performs well using powerpill...linux downloads in 5-10secs.
EDIT: 2/8./16.....Upgrade to linux-4.4.12-2-x86 succrssful. Still no monitor with quantom dots!!!!
EDIT: 2/29/16 Decided to make an entry on this unusual day in history... Have utilized a running system in archlinux to generate a new install to another device. This is done by utilizing arch-install-scripts which provide the pacstrap and arch-chroot scripts necessary to permit the install to complete. Utilizing these scripts eliminates any need to use the archiso's download. Attention is needed to the internet arrangement since dhcpcd service may have to be restarted. Assuming the operating system has higher download speed than the device used with archiso dd'ed devices, the install proceeds much faster.
The procedure utilizes the same arrangement as the archiso including mkfs, mount device in /mnt pacstrap , genfstab, arch-chroot, and the remaining steps thru the bootloader and mkinitcpio -p linux.
My system with SSD and powerpill permitted full install in 20 minutes or so. A positive improvement in install time.
One must install .....arch-install-scripts i......n the running system. No need to use the archiso download. This insures faster performance when installing to a new device.
Still no quantom-dot display!!!!!
Edit: 3/2/16....Decided to try running all packages with pacstrap /mnt by mounting the device being installed in /mnt (that puts the whole device in /mnt as root) and using pacstrap /mnt followed by the list of packages to be installed. This was done along with base and base-devel. Pacstrap performs this function speedily downloading and installing all packages listed. This step is then followed by the genfstab command which leads to arch-chroot. Enabling pacstrap and chroot with the running system is permitted through install of arch-install-scripts as described in the previous edit.
My list of packages was ....xorg-xinit xorg-server xorg-server-utils xf86-video-intel gvfs leafpad xfce4 alsa-utils mpv feh gparted hdparm kdenlive .....
I utilize aur packages which must be installed after the new system is up.
Upon completing the required arch-chroot steps and grub install with grub-mkconfig, the system was booted to log-in wherein xfce4 was started and the desktop followed. All packages were available and the aur packages were then built and installed.
The systemd-analyze statement revealed 6.5 secs with journal log active. Removing journal reduced the time by 2 secs to 4.45 secs.
The time from initial start of the install to the first desktop was 20 minutes. Many steps left to finish the aur packages bauerbill xpdf phototonic otter-browser and bauerbill but the system is up and running.
The performance of the procedures was faster than the use of archiso methods and I appreciate that factor. Pacstrap is most helpful in downloading and installing without serious interactivity(some selections have to be made during the procedure with this methodology).
Pleased that I could utilize the install scripts to good advantage.
EDIT: 3/3/16 Upgraded all systems to linux-4.4.3-1 with the same install arrangement with no problems. Very speedy with SSD running system using /mnt directory for all system device mounts.
EDIT: 3/12/16...Upgraded to linux-4.4.5-1x64with no problems. Installed several systems to new devices with arch-install-scripts from a running ssd system. Very speedy.
EDIT: 3/30/16.....Finally ordered the philips 27 inch quantom-dot monitor and received same in four days. It has intense color performance but is too bright on text displays. Suggest using dark glasses for viewing same. I use full VGA mode. The unit worked out of the box. Haven't tried any adjustments. Tom's hardware reports thst bright display cannot be controlled. One can wear dark glasses!
EDIT: 4/15/116....Purchased a gigabyte ud3h mobo and installed cpu and 16GB memory. Installed into case and was able to utilize my archlinux ssd's and USB 3.0 devices to boot archlinux. With the ssd it boots in just under 2 secs and just under 5 secs with 3.0 USB boot. The hdparm read speed for the 3.0 ssd is 459 MB/s. The cpu has four core at 1333mhz and the memory is ddr3 1600. Shut down occurs in one second. My devices all boot in the new computer. So now have a major backup! x64 arch.
EDIT: 5/8/16 Happy mother's day! Upgrade tp linux-4.5.2-1-x86 was successful on all systems with no problems. Enjoying my new gigabyte platform which boots in under 4 secs and powers off in 1.5 secs. The mobo runs 100 watts with a 40 watt display included. Using a 3watt desk lamp as well. Installed audacious and android packages to enable photo transfer from smartphones. So I am eco friendly using suspend at every opportunity to save emergy.
EDIT: 5/12/16 Upgraded to linux-4.5.3-1-x64 with no problems.
EDIT: 5/13/16 Installed archlinux with f2fs filesystem using fullsized 60GB SSD sataII. The boot time in grub is 1.447 secs. System is root-only. Learning how to utilize f2fs for a time now. Initrd time is small--kernel over 500ms in systemd-analyze.
EDIT: 5/15/16 Upgraded to linux-4.5.4-1 in all systems. Now have SSDIII 60 GB drive with f2fs filesystem that boots in 1.667 secs. Sure enjoy the suspend feature. This f2fs is obtained with grub via a /boot partition and a /root partition for the remainder of the drive. Installed with arch-install-scripts ....installed all packages with pacstrap ...approx 7GB of packages installed in root.
EDIT: 6/4/16 Have installed qemu in one ssd drive and created .img files. Installed several guest .iso files. Learning qemu system behavior. Utilizing two cores for speed-up. Cpu is vt-x so many things are not provided for AFAICT.
EDIT: 6/8/16 Upgraded to linux-4.6.1-2-x64 with no problems. Have enabled qemu with 8 OS'es the largest is b;uestar.linux being 4.2GB in size. There are a great number of packages therein and it performs well as a guest os. I have much to learn as yet about the qemu options and expect it will be a while before I have reached the top of my learning curve. Qemu has so many options!!! Syntax therein is also a bit difficult to establish for a newcomer. Not able to use win8.1 from another computer because the HDD is 1TB!
EDIT: 6/9/16 Upgraded to linux-4.6.2-1-x86_64 with no problems. Also, using qemu with bluestar linux have been able to add a usb from the host archlinux and also learned how to add alsa sound in the qemu script I generated.
I also find it advantageous to use qwmu to increase my access to many,many packages that enhance the versatility of my computer. Although having such a lot of possible programs does not increase my boot time which is 2.3 secs. Quick response with the normal functions in the host archlinux install is paramount. I find it convenient to use suspend in the host. I was surprised to find that it also works in the guest but doesn't shut down the system...just the guest. Was able to set up a usb file in /tmp which allowed music files to be utilized in the guest from the /tmp/disk.usb file I created in the host. I am able to use firefox to play vimeo videos with sound and play the videos in google news. All in all, a learning experience I won't forget! My cpu is supportive for vtx and does not support virtio so some activities are not possible. Perhaps a different mobo and cpu would be fun to play with....at some expense! I use two cores in the guest which provides adequate boot speeds of ~20 secs for the guest system of 4.2GB with bluestar linux as guest. I do not have a passwd for the bluestar linux so cannot comment on what might ensue if a terminal could be accessed.
EDIT: 6/10/16 My system is still operating btrfs full-capacity SSD's. The cpu is intel 4590 haswell running at 3+ghz, 16GB ddr3 memory (soon to be 32GB), desktop (silver case I call it my "Silver Bullet). Cpu supports vt-x for guest virtualizations. My SSD's are mode III 120GB Patriot,Pny, and samsung 850 evo. I have a cd/dvd included running on usb adapter. There are no IDE ports on the gigabyte z97 ud3h mobo. It has an M2 port of up to size 80 that I may get a disk for on Father's day(dreamer!).
Mobo has six sataIII ports. System boots in 2.3 secs as reported by systemd-analyze and utilizes suspend to eliminate the need to boot. LGA 1150 cpu socket. Qemu script as follows: qemu-system-x86_64 -soundhw hda -enable-kvm -cpu host -smp 2 -m 4G /root/mydisk.img -usb...... I utilize usb device using /tmp file as follows.....in host-----......dd if=/dev/sdx of=/tmp/disk.usb...wherein the usb device is 2GB with 1.2G of music files. This /tmp file is accessed in the host OS Desktop using the following: ctl+alt+2 in the guest Desktop. This initiates qemu in a terminal...enter the following:...... usb-add disk:/tmp/disk.usb..... Then enter keybd....ctl+alt+1..... This returns to Desktop with the usb listed and can be selected and opened for playback in guest apps.
The guest system is snappy with the 2 cores provided and sound is alsa based on my intel z97 built in audio on the host system. No distortion occurs and no clicks nor buzzes.
There may be other ways to enable usb connect but this one works fine. It is of course lost if rebooting, but probably with suspend the connect is not lost.
EDIT: 6/28/16 Upgraded to linux-4.6.3-1-X86_64 with no problems. Have installed qemu, virtualbox and performed a panorama with hugin package. All systems are root-only. One system is contained in an m2 SSD which runs at 516MB/s read speed. All systems are btrfs with full-capacity SSD devices..no partitions.
EDIT: 7/15/16 Upgraded to linux-4.6.4-1-x64 with no problems. Use on four ssd's.
Running qemu often with success on several linux kernels. Used xfburn successfully and also virtualbox. Enjoying the suspend capability of this mobo, keeps the light bill down! One month to my b'day.
EDIT: 8/12/16 Upgraded to linux-4.7-1-x86_64 in all systems with no problems. Now have a photosmart printer running in one system. Surprised to find the following in one system........
208853 items, totalling 40.8 GB........
This is 30% of capacity, 80GB free in a 120GB SSD. This device boots in archlinux in 2.6 seconds.
EDIT: ....9/15/16 Upgraded to linux-4.7.3-2-x86_64 with no problems...other than the ongoing libdbus/dbus bug which attacks x and xfce4 to prevent boot. Boot time in this ssd is 3.174 secs with 38GB of data ...30% of capacity ....root only OS. Ignore applied to libdbus/dbus until bug day solves the problem.
EDIT: 9/17/16...Upgraded to linux-4.7.4-1-X86_64 with no problems. Still ignore libdbus and dbus until bug day arrives.
EDIT: 10/3/16 Upgraded to linux-4.7.5-1-x86_64 with libdbus/dbus problem ignored until bug day
EDIT: 10/4/16 Upgraded to linux-4.7.6-1-x86_64 again with libdbus/dbus ignored
EDIT: 10/7/16 Booted evo ssd m2 in 1.805 seconds to btrfs root only xfce4 Desktop(time displayed in systemd-analyze) Actual time to display is about 4 seconds from suspend to resume with systemd-analyze indicating 1.805 seconds (this being the time to boot as recorded previous to suspend/resume). System is upgraded to linux-4.7.6-1-x86_64.
EDIT: 10/20/16 Upgraded to linux-4.8.2-1 with no problems. Still ignoring libdbus/dbus upgrade.
EDIT: 10/22/16 Upgraded to linux-4.8.3-1-x86_64 with no problems. Still use the ignorelibdbus/dbus. Note the DDOS occuring on the net which may become more intense.
EDIT: 10/24/16 Upgrade to linux-4.8.4-1-x86_64 was successful but still ignore libdbus and dbus.
EDIT: 11/1/16 Upgrade to linux-4.8.6-1-x86_64 was successful but still ignore libdbus and dbus. Used --force to install ttf-dejavu as outlined in news post.
EDIT: 11/12/16 Upgraded to linux-4.8.7-1-x86_64 with no problems. Still using ignore libdbus/dbus.
EDIT: 11/16/16 Upgraded to linux-4.8.8-1-x86_64 in 4 ssd systems with no problem. Still using ignore libdbus/dbus.
EDIT: 11/17/16 Upgraded 4 ssd systems to linux-4.8.8-2-x86_64 with no problems. Still ignoring lidbus/dbus. A reminder that my archlinux systems are full capacity BTRFS ssd's and operate as root only .
They vary a bit in boot speed but typically under 5 seconds...one is 1.885 secs at this time. My "Silver Bullet" has been described previously.
EDIT: 11/23/16 Day before thanksgiving and upgraded to linux-4.8.10-1-x86_64 with no problems. All four ssd's performing normally. No swap partition nor swap file(not allowed in btrfs). Haven't run any support programs in btrfs since putting the mobo in service with ssd's which show no deterioration at this time. One has 40+GB installed.
EDIT: 11/29/16 Upgraded to linux-4.8.11-1-x86_64 on four ssd systems with no problems. Performing btrfs scrub on all systems for first time.
EDIT: 12/6/16 Upgraded all systems to linux-4.8.12-2-x86_64 with no problems. Still await a definitive method of correcting the xfce4 libdbus/dbus problem. Scrub performed rapidly with no problems encountered.
EDIT: 12/9/16 Upgraded to linux-4.8.12-3-x86_64 with no problems. Still ignore libdbus/dbus.
EDIT: 12/11/16 Upgraded to linux-4.8.13-1-x86_64 with no problems. Still ignore as before.
EDIT: 1/27/17 Upgraded to linux-4.9.6-1-x86_64 with no problems . Still ignore as before.
EDIT: 2/13/17 Upgrade to linux-4.9.8-1-x86_64 with no problems. Still ignore as before.
EDIT: 2/19/17 Upgrade to linux-4.9.9-1-x86_64 with one problem. Mpv has upgraded but dropped a service in the upgrade that I was unaware was going to be dropped. This was stream-capture which I really used a lot and had good luck in using. I also rebuilt one SSD with the arch iso which solved the libdbus/dbus problem for that device. The remaining devices still ignore those packages in upgrades. This proves the axiom "you don't always win".
EDIT: 2/21/17 Upgrade to linux-4.9.11-1-x86_64 successful on all four ssd's. Still having problem with mpv --record-file option which doesn't record but does play the url video selected.
EDIT: 3/11/17 Upgraded to linux-4.10.1-1x86_64 with no problems. Using mpv --record-file with two extensions, mkv for some, m4a for others. Acquainting myself with vr packages and viewing some spherical videos.
EDIT: 3/14/17 Upgraded to linux-4.10.2-1-x86_64 in all systems with no problems. Installed getty drop-in-file to establish autologin to root. Discovered that xfce4 could be initiated with up arrow and enter after autologin so that eliminated the many keyboard entries for root enter startxfce4 enter. Very nice! Still operating as root only as I have done for 14 years in archlinux and more before that.
EDIT: 3/18/17 Upgraded to linux-4.10.3-1 with no problems. I now have all four ssd's booting directly to xfce4 Desktop , after finding posts with procedures which I was able to adopt while running as root only. The M2 ssd boots in system analyze timed 1.915 seconds. All systems can utilize suspend which gives 6 seconds total time from keybd stroke to Desktop. I off-load any large files via usb3 storage devices to eliminate loading time for the main system. These usb3 devices are usable on all ssd systems. Running out of projects to pursue!
EDIT: 3/20/17 Upgraded to linux-4.10.4-1x86_64 with no problems. Have a nice first day of spring!
EDIT: 3/24/17 Upgraded all systems to linux-4.10.5-1-x86_64 with no problems. This post thread is now approaching 16000 views.
Using this style of computer shennanigans keeps my mind busy as I approach 92 years of life.
EDIT: 4/5/17 Upgrade to linux-4.10.8-1-x86_64 with no problems. Enjoying my "silver bullet" very much. Having dinner date with Eric Waller tmw at the Outback. Now have 5 systems available with 120GB ssds. Am wondering whether red wine will enhance the computer performance like it has aided performance of superconducting materials! Lol ! I hear Mexico has requested the science gurus to try Tequila instead of red wine!
EDIT: 4/12/17 Upgraded to linux-4.10.9-1-x86_64 with no problems on five ssd systems. Enjoyed a dinner meeting with Eric Waller recently. Still get 2 second boot and suspend produces a similar number. The philips 27 lnch display seems a bit slow in responding, model 276E.
EDIT: 4/17/17 Upgrade to linux-4.10.10-1-X86_64 with no problems. Had a fine visit with great grandchildren on Easter sunday.
EDIT: 3/21/17 Upgrade to linux-4.10.11-1-x86_64 on five ssd systems with no problems. All systems boot in 2 secs with a variable connection time (maybe 3 secs) to the internet. Desktop is xfce4 with only two panels displayed at the bottom of display area with the main display gray background, reduces glare. Browsers are firefox,opera and jumanji.
EDIT: 5/1/17 Upgraded to linux-4.10.13-1-x86_64 with no problems. View count now at 16194+ for this thread.
EDIT: 5/23/17 Upgraded to linux-4.11.2-1-x86_64 with no problems in any of the five sdd's . Noted the available aaa batteries made with ni/zn having 1.65 Volt output, 900mwh capacity. Best features are recharge and a steady state voltage during discharge until drop-off. Some are advertised at 1100mwh. I use them in my hearing aid, self-designed.
EDIT: 5/30/17 Upgrade to linux-4.11.3-1-x86_64 successful. Making a dual mono hearing aid for both ears using type ni/zn aaa batteries.
EDIT: 6/14/17 Upgraded to linux-4.11.4-1-x86_64 with no problems.
EDIT: 6/15/17 Upgraded to linux-4.11.5-1-x86_64 with no problems. Today is my 70th wedding anniversary.
EDIT: 6/20/17 Upgraded to linux-4.11.6-1-x85_64 with no problem. Enjoyed my 69th Father's day with three adult children present.To extend battery life, may include a momentary switch to permit intermittent use in my hearing aid. Could use a magnetic reed type. Good for muting ads on TV!
EDIT: 6/23/17 Upgrade to linux-4.11.6-3-x86_64 with no problems. Installed a pushbutton switch to allow short listening time to save battery power. Nixed the mag switch. A second switch (slide) turns on the hearing aid for long periods. Testing the performance of ni/zn batteries in a three cell hearing aid.
EDIT: 6/30/17 Upgraded to linux-4.11.7-1-x86_64 with no problems. Systemd-analyze for this ssd system.......Startup finished in 861ms (kernel) + 860ms (initrd) + 428ms (userspace) = 2.150s
EDIT: 7/14/17 AFAICT I cannot utilize pulseaudio packages in my root-only btrfs system. It seems that no one can provide aid in trying to modify the package to enable use of pulse in a root-only system....probably because they have no such system in which to test any changes. I expect that it can be done with such a system by generating a new PKGBUILD .
EDIT: 7/31/17 Upgraded to linux-4.12.3-1-x86_64 in five ssd systems with no problems.
My wife, Elaine, passed away from Alzheimer's disease on July, 21, 2017 . A poem by Owen Darnell, "Do not ask me to remember" , is indicative of the torment in her battle with memory loss.
EDIT: 8/6/17 Upgraded all ssd's to Linux-4.12.4-1 with no problems.
EDIT: 8/18/17 Upgraded to linux-4.12.6-1-x86_64 with no problems. Solar eclipse not appearing in this area on Monday 8/21/17. Experienced one in the 1900's.
EDIT: 8/20/17 Upgraded to linux-4.12.8-2-x86_64 with no problems. Tmw is burn your eyeballs day for millions in USA.
EDIT: 9/5/17 Upgraded to Linux-4.12.10-1-x86_64 with no problems. Time to boot now is 2.054secs in ssd120MB single device btrfs full size capacity. I have not tried to optimize the boot time since this figure is quite adequate.
EDIT: 9/10/17 Upgraded to Linux-4.12.12-1-x86_64 in all 5 ssd systems with no problems.
EDIT: 9/15/17 Upgraded to Linux-4.12.13-1-x86_64 with no problems.
EDIT: 9/28/17 Upgraded all systems to linux-4.13.3-1-x86_64 with no problems.
Note that font size was affected but is a minor thing. Soon fall colors will cover the earth with breathtaking panoramas. I live too far away from them in California. Note that Version1delete ...V1del is doing a great service on the boards.
EDIT: 10/8/17 Upgraded to Linux-4.13.4-1-x86_64 with no problems. Gparted failed after losing locate.conf, possibly from glibc upgrade corruption. The wiki enabled to correct the error but searching the boards and googling gave erroneous solutions derived from the same wiki! All is well that ends well.....
EDIT: 10/11/17 Upgrade to Linux-4.13.5-1-x86_64 applied to all ssd devices. Systems performing nicely as usual. The M2 ssd boots in 1.893 secs. View count on my edits is now 18043 and rising, hope some are getting something out of my efforts.
EDIT: 10/16/17 Upgraded to linux-4.13.6-1-x86_64 with no problems. Note a large increase in views to 18103 from 18085 yesterday. Planning to make an fmtv oscillator at 10ghz as a hobby activity.
EDIT: 10/17/17 Upgraded to Linux-4.13.7-1-x86_64 with no problems. Now the count is 18131 as shown on page 113 for this thread. I guess its a product of Trumpism!
EDIT: 10/24/27 Upgrade to Linux-4.13.8-1-x86_64 with no problems. Discovered that jumanji-git does not build probably due to webkitgtk being an orphan. View count jumped to 18236 today. Maybe Trump discovered it as a terrorist site!
EDIT: 10/28/17 Upgrade to Linux-4.13.9-1-x86_64 with no problems. Using reflector and pkgbrowser often. I use aura for aur installs. Still want Jumanji but not yet able to build it.
EDIT: 10/30/17 Upgrade to Linux-4.13.9-1-x86_64 with no problems. Was able to makepkg Jumanji-git after a second attempt. View count on my post on Installation (this one) jumped to 18335. Guess its because the Dodgers lost a terrific game.
EDIT: 11/03/17 Upgraded to Linux-4.13.10-1-x86_64 with no problemsin . Dodgers lost----blame trump? View count is now 18413.
EDIT: 11/13/17 Upgraded all ssd's to Linux-4.13.12-1-x86_64 with no problems. View count on this thread is now 18617. Hear that Bill Gates is now interested in research on alzheimers. I congratulate his decision and hope that his efforts therein are helpful.
EDIT: 12/03/17 Upgraded to Linux-4.14.3-1-x86_64 with no problems. View count is now over 18840. I hope my info is helpful. I am still root only as has been true for 16 years. One boot time is 1.892 secs and I use suspend for fast opening the system and saves energy.
EDIT: 12/10/17 Upgraded to Linux4.14.4-1-x86_64 with no problems. Having a difficult time finding a buildable version of jumanji-git. Get a failed girara/tabs.h file fail in performing build from aur. Download of PKGBUILD includes git with PKGBUILD.
Package view on this thread is now almost 19000.
EDIT: 12/13/17 UpGraded to Linux4.14.5-1-x86_64 with no problems. View count on this thread is now 19041. Designed an audio modulated oscillator providing harmonics in the fm band for use in hearing TV from across the room. Listen on a sony walkman. The circuit used was a modified pierce oscillator with an electret replacing the crystal. It is battery operated with a lithium cell for power. Need it with my hearing problems.
EDIT: 12/17/17 Upgraded to Linux-4.14.6-1-x86_64 with no problems. Soon it will be winter with all its weather. Merry Christmas to all who view this thread.
EDIT: 12/24/17 Upgraded to Linux-4.14.8-1-x86_64 with no problems. Weather is indeed wintry. Thread view count now 19181.
EDIT: 1/3/18 Upgraded to Linux-4.14.10-1-x86_64 with no problems. Thread count is now 19323.
EDIT: 1/4/18 Upgraded to Linux-4.14.11-1-x86_64 with no problems. Thread count is now 19371.
EDIT: 1/8/18 Upgraded to Linux-4.14.12-1-x86_64 with no problems. in Thread count is now 19441. Designed a ring oscillator using 74ac04 smd chip. Utilized two capacitors one on the input and the other on the output of a single inverter. The other two inverters are connected in tandem and the second inverter output returned to the first inverter input. It oscillates at ~10mhz.
I utilize a mosfet smd to enable an electret to modulate the capacitor's return to ground plane. The system utilizes an odd harmonic in the fm band to enable a very sensitive hearing aid due to the multiplication factor in fm deviation and the sensitive mosfet input gate.
EDIT: 1/11/18
Upgraded to Linux-4.14.13-1 with no problems.
EDIT: Upgraded to Linux-4.14.14-1-x86_64 with no problems. Making test of the hearing aid circuit performance to establish the stability and battery performance. Listened all afternoon and evening to football games and had some drift of the fm channel but very minor. Am going to try crystal stabilization of the digital square wave circuit using either sub-harmonic or harmonic stabilization. This does not mean control of the oscillating frequency(no fm) but a preferred harmonic impedance causing the digital square wave to prefer that harmonic. May require some additional component(s) as well as the xtal. Gives me something to do other than facebook, you-tube or netflix.
EDIT: 1/24/18 Upgrade to Linux-4.14.15-1-x86_64 with no problems. View count is now 19964 on this thread.
EDIT: 1/26/18 Decided that the xtal idea isn't viable so installed a parallel open wire 300 ohm line to establish both a resonance and a radiator for the fm band receiver to detect. This reduces the range of the device to room dimensions. View count is now 19716.
EDIT: 2/6/18 Upgrade to Linux-4.15.1-2-x86_64 with no problems. View count is now 19915 on this thread.
EDIT: 2/10/18.....Thread count is now 20017!
EDIT: 2/14/18 Upgraded to Linux -4.15.3-1-x86_64 with no problems. View count is now 20097!
EDIT: 2/17/18 Upgraded to Linux-4.15.3-2-ARCH with no problems. View count is now 20133. My hearing aid device is now running on two aaa batteries....two versions...one with npn transistor modulator and the other with mosfet modulator. Slow drift in frequency but only need to press the walkman once to shift to lower channel. Two 30 inch wires serve as a radiating antenna at 100mhz and the source signal is running at a dc level of 0.89 v. The ring oscillator runs at frequencies near 10mhz , square wave.
EDIT: 2/23/18 Upgraded to Linux-4.15.4-1 with no problems. View count over 20160. Trying new IC 74lvx04 which operates at lower current level with success in my wireless hearing aid.
EDIT: 2/15/18 Upgraded to Linux-4.15.5-1-ARCH with no problems. View count is now 20193. Simplified my hearing aid device to eliminate one transistor. Now have two caps, the IC, one resistor, and the electret and run on two 1.5V cells. The circuit draws ~2ma. It radiates across the room to a Walkman fm receiver.
EDIT: 3/1/18 Upgrade to Linux-4.15.6-1 with no problems. The count is near 20228. Making a six inverter ring oscillator hearing aid. All six inverters in the oscillator loop. Runs on ~2 ma at 1.25 V. There are no modulator transistors included.
EDIT: 3/6/18 Upgraded all 5 systems to Linux-4.15.7-1-x86_64 with no problems. Boot time in this ssd is 1.892 secs. Thread count has reached 20290. Even number of inverters in hearing aid experiment was intermittent so I quit the experiment. I now have a modified three inverter device using an electret in the loop and a resistor in the 3Volt supply running at 2ma load current giving a three part count oscillator which provides very sensitive sound performance used with a walkman fm receiver.
EDIT: 3/12/18 Upgraded to Linux-4.15.8-1-x86_64 with no problems.
EDIT: 3/15/18 Upgraded to Linux-4.15.9-1-x86_64 with no problems. View count is now over 20370.
EDIT: 3/19/18 Upgraded to Linux-4.15.10-1-x86_64 with no problems. View count is now over 20400.
EDIT: 3/22/18 Upgraded to Linux-4.15.11-1-x86_64 with no problems. View count is now over 20457.
EDIT: 3/25/18 Upgraded to Linux-4.15.12-1-x86_64 in five ssd's with no problems. View count is now over 20480.
EDIT: 3/28/18 Upgraded all fivs ssd's to Linux-4.15.13-1-x86_64 with no problems. Thread count is now 20509.
EDIT: 4/6/18 Upgrade to Linux -4/15.15-1-x86_64 with no problems. Thread count is now 20602.
EDIT: 4/12/18 Thread count is now 20650. My hearing aid for TV audio is now made from the 74lvx04 IC and consists of three inverters connected in tandem with a 10K ohm feedback resistor and a second resistor 600ohms connect from output of third inverter (10Kalso connected there) and the input of the third inverter. This setup is run from a 3volt source through a 600 ohm resistor. The electret connects to the Vcc point and negative terminal. The fm channel frequency is 104.9mhz with other channels also tuneable. The remaining three inverters are tied in tendem with the first inverter input tied to the Vcc terminal.
EDIT: 4/13/18 Now have a three part hearing aid using the 74lvx04 IC , a 600 ohm resistor and an electret. It generates an fm signal at ~102mhz which an fm channel receiver can detect and provide two channel sound. It runs from two AAA cells in a switch provided container which mounts the parts. When provided with two thirty -inch lengths of wire it provides a strong enough signal to provide TV sound across the room.
EDIT: 4/19/18 Upgraded in all 5 systems to Linux-4.16.2-2 with no problems. Thread count is now 20753. Watched the TESS satellite launch, an ambitious endeavor requiring orbit control around the moon and transfer of data on each orbit. Not ready for research tasks for 60 days.
EDIT: 4/20/18 Upgraded to Linux-4.16.3-1 in all five systems with no problems. I have watched the archlinux kernel rise steadily for 15 years as it now has nearly reached 70MB in size. My thread view count is over 20750 and climbing. Eric Waller sent me pix of the TESS research satellite launch for which I am grateful. He, his wife and daughter were VIP's because his daughter produced a part of the TESS data handling system while a Junior in college. They viewed the launch from a point five miles away and a delayed thunderous blast occured about 15 seconds later.
EDIT: 5/1/18 Upgraded to Linux-4.16.5-1 in all five systems with no problems.
Thread count is now 20880. Studying the ipfs system hopefully to see some progress in utilizing it with pacman. The hash required needs to be generated for all packages and such is a large undertaking.
EDIT: 5/3/18 Upgraded to Linux-4.16.6-1-x86 with no problems. Pacman was also upgraded. Thread count is 20918.
EDIT: 5/7/18 Upgraded to Linux-4.16.7-1-x86 with no problems. Thread count is now 20938
EDIT: 511/18 Upgraded tp Linux-4.16.8-1-x86 with no problems. Thread count is now 20948. Been experimenting with ipfs and learning the ropes. Looks promising in this era where the internet is threatened with ddos and net neutrality repeal. Am aware that pacman presents a stumbling block for its use in ipfs. Hope exists that it can be implemented in the near future.
EDIT: 5/18/18 Upgraded to Linux-4.16.9-1 in all systems with no problems. Note the very fine pix from TESS satellite sent from the satellite as it passed the moon on its first encounter. Eric Waller's Daughter had a hand in its design, and the family became VIP's at the launch. There's more pix in the near future from the four cameras searching the skies from an elliptical orbit never before utilized.
EDIT: 5/23/18 Upgraded to Linux-4.16.10-1-x86 with no problems. Coming closer to 21000 views in this thread. Sorry there's not much to report.
EDIT: 5/25/18 Upgraded to Linux-4.16.11-1-x86 with no problems. Thread count is now 20988. Having difficulty with go-ipfs...probably my ignorance.
This year is my 15th in archlinux.
EDIT: 6/4/18 Upgraded to Linux-4.16.13-1 with no problems. Thread count is now 21013.
EDIT: 6/6/18 Upgraded to Linux-4.13.16.-2 with no problems. Thread count is now 21028.
EDIT: 6/17/18 Upgraded to Linux-4.17.2-1-x86 with no problems. Happy Fathers's Day to all the Dad's. Thread count is now 21186.
EDIT: 6/30/18 Upgraded to Linux-4.17.3.-1 with no problems. Thread count is now 21217.
EDIT: 7/8/18 Upgraded to Linux-4.17.4-1-arch with no problems. Thread count is now 21228.
EDIT: 7/11/18 Upgraded to Linux-4.17.5-1-x86 with no problems.
EDIT: 7/22/18 Upgraded to Linux-4.17.8-1-x86 with no problems. Thread count is now 21277.
EDIT: 7/27/18 Upgraded to Linux-4.17.10-1-x86 with no problems.
Thread count is now 21306. Had a memorial service for my son Patrick Jon Clancy, 59 on Thursday, July 26,2018, who died May 27, 2018 in Los Alamitos , Ca.
EDIT: 7/30/18 Upgraded to Linux-4.17.11-1-x86 with no problems. Thread count is now 21320.
EDIT: Upgraded to Linux-4.17.13.arch-1 with no problems. Pleased to upgrade printer with testing hplip-3.18.7-3. That fixed the failed filter problem. Five days to my birthday!
EDIT: 8/12/18 Upgraded to Linux-4.17.14-arch-1 with no problems. Had a filter fail in HPLIP upgrade that could be fixed using previous version of hplip but testing provided a new version which provided the needed fix.
Further, the next upgrade of hplip included the new version and all is well.
EDIT: 8/18/18 Upgraded to linux-4.18.arch1-1 with no problems. So I am 93 for a year yet!
EDIT: 8/20/18 Upgraded to Linux-4.18.arch1-1-ARCH with no problems.
EDIT: 8/26/18 Upgraded to Linux-4.18.5-arch1-1-ARCH with no problems. Thread count is now 21461. Interest seems to be falling off.....
EDIT: 9/10/18 Upgraded to Linux-4.18.6.arch1-1ARCH with no problems.
Thread count is now 21486 and counting
EDIT: 9/16/18 Upgraded to Linux-4.18.7.arch1-1ARCHwith no problems. Completed a hearing aid using walkman fm receiver with attached ring oscillator using shunt connected electret sensor powered by aaa battery and 74lvx04 hex inverter. Draws 0.6 ma and is very sensitive. Ring oscillator harmonics capture the full quieting of the walkman receiver.....As the battery drops in voltage, adjustment of the walkman is easily accomplished with the up and down buttons provided. Nizn batteries provide up to 1.9 vdc to operate the attached circuitry. Unit utilizes the harmonic multiplier effect of bandwidth to enable wide-band audio response.
EDIT: 9/20/18 Upgraded to Linux-4.18.8.arch1-ARCH with no problems. Thread count is now 21505.
EDIT: 10/5/18 Upgraded to Linux-4.18.11.arch1-Arch and Linux-4.18.12.arch1-ARCH with no problems. Thread count is now 21541.
EDIT: 10/16/18 Upgraded to Linux-4.18.14.arch1-1-ARCH. Thread is now 21588 views. Just returned from visit to great grandchildren in Arkansas, so I am now a true "Arkansas traveler". Great grandchildren are three girls 8, 11, and 14. Went to Petit Jean state park and overlooked the state of Arkansas, and the Arkansas river. Amazed by the forestation in that State. Now back in "the golden west" of California.
EDIT: 10/22/18 Upgraded to Linux-4.18.14.arch1-1-ARCH with no problems.
EDIT: 11/17/18 Upgraded to Linux-4.19.2.arch1-1-ARCH with no problems. I expect to upgrade my M2 drive to a terrabyte capacity soon which should give me much longer life of that operating system and place the root partition capacity outa sight!
EDIT: 11/23/18 Happy Thanksgiving to all! I have upgraded my m2 device to 1 TB with a samsung 860 EVO and it runs at 536MB/s in hdparm. There is 946GB of free space on the machine, root only , BTRFS, grub bios boot, and latest Linux-4.19.2-1. I expect a long-time service out of this device because of its free-space. I have a spare M2 device of 120Gb as well with Linux-4.19.2-1 installed. This may be the largest root partition in archlinux.
EDIT: 11/26/18 Upgraded to Linux-4.19.4-1.arch1-1ARCH with no problems. Thread count is now 21728. ITB M2 drive is performing well. Building up package count daily. Corrected my last post to show correct free space in the 1TB M2 device, 946GB.
EDIT: 12/10/18 Upgraded to Linux -4.19.8.arch1-1ARCH with no problems. Post count is now 21760.
EDIT: Upgraded to Linux 4.19.1-arch1-1-Arch with no problems. Thread count is now 21808.
Merry Christmas to all!
EDIT: 12/24/18 Upgraded to Linux -4.19.12.arch1-1-ARCH with no problems. Thread count is now 21819. Merry Christmas to all!
EDIT: 1/14/19 Upgraded to Linux-4.20.1.arch1-1-ARCH with no problems. Thread count is now 21888.
EDIT:1/17.19 Upgraded to Linux 4.20.3.arch1-1-ARCH with no problems. Thread count is now 21898.
EDIT: 1/26/19 Upgraded to Linux-4.20.4.arch1-1-ARCH in all 5 systems with no problems. Thread count is now 21926 and counting.
EDIT: 1/30/19 Upgraded to Linux-4.20.5.arch1-1-Arch in five systems with no problems.
Thread count is 21938.
EDIT: 2/1/19 Upgraded to 4.20.6.arch1-1ARCH with no problems. Thread count is now 21944. Linux is changing rapidly lately. I skipped .5 'cause I was ill.
EDIT: 2/7/19 Thread count is now 21967
EDIT: 2/8/19 Upgraded to Linux-4.20.7.arch1-1-ARCH with no problems. Thread is now 21970.
EDIT: 2/14/19 Upgraded to Linux-4.20.8.arch1-1ARCH with no problems. Thread count is now 21992. Happy Valentine's day!
EDIT: 2/20/19 Upgraded to Linux-4.20.arCH1-1-ARCH with no problems. Thread count is no 22041.
EDIT: 2/22/19 Upgraded to Linux-4.20.11.arch1-1-ARCH with no problems. Note in passing that the kernel loads as Linux -4.20.11-arch1-1-ARCH . This seems strange to me since accurate typing is paramount to good computer performance. Thread count has risen to 22060.
EDIT: 2/23/19 Upgraded to Linux-4.20.11.arch2-2-ARCH with no problems. Perhaps the need for a patch is why the new .arch(x) is utilized. Anyhow, it works just fine.
EDIT: 2/2/25 Upgraded to Linux-4.20.12.arch2-1-ARCH with no problems. Thread count is now 22074.
EDIT: 3/1/19 Upgraded to Linux-4.20.13.arch1-1-ARCH with no problems. Thread count is now 22086. Tonight is spacex biggest test to date. Wish them success in the entire venture.
EDIT: 3/14/19 Upgraded to Linux-5.0.arch1-1ARCH with no problems. Thread count is now 22120
EDIT: 3/21/19 Upgraded to Linux-5.0.3.arch1-1-ARCH with no problems. Thread count is now 22137.
EDIT: 3/30/19 Upgraded to Linux-5.0.5.arch1-1-ARCH with no problems. Thread count is now 22169.
EDIT: 4/6/19 Upgraded to Linux-5.06.arch1-1-ARCH with no problems. Thread count is now 22186. Tuesday is big launch day for the Spacex heavy rocket including a triple play recovery. A first ever if successful !
EDIT: 4/7/19 Upgraded to Linux-5.0.7.arch1-1-ARCH with no problems. Thread count is now 22198. Launch is now set for Wednesday. Boeing may cause meltdown globally since transportation is prime need. Certainly not prepared to try for three with MAX anything.
EDIT: 4/20/19 Upgrade to Linux-5.0.8.arch1-1-ARCH with no problems. Thread count is now 22250.
EDIT:4/22/19 Upgraded to Linux-5.0.9.arch1-1-ARCH with no problems. Thread count is now 22264.
EDIT: 5/1/19 Upgraded to Linux-5.0.10.arch1-1-Arch with no problems. Thread count is now 22292. Attempting to connect hdmi to 49" Samsung TV but find it unstable with the present Philips monitor and GAz97x-ud3h mobo. It worked for a short time but then went to a state where the display oscillates between the two display modes. The color on the philips monitor is much brighter than the Samsung 49" display.
EDIT: 5/5/19 Upgraded to Linux-5.0.12.arch2-1-ARCH with no problems.
Thread count is now 22306.
EDIT: 5/6/19 Upgraded to Linux-5.0.13.arch1-1-ARCH with no problems. Thread is now 22308.
EDIT: 5/15/19 Upgraded to Linux-5.1.2.arch1-1-ARCH with no problems.
Thread count is now 22334.
EDIT: 5/17/19 Managed to get started with snapper and grub-btrfs on one of my 128GB ssd's.
Installed the snapper gui to monitor snapshots. Have 24 installed so far and am learning how to utilize them. Eventually want to install new OSes in a subvol and boot into them. Learning curve is slow as usual. Need to search the subvol data to ensure booting. I think there is a method to avoid that procedure. Have to go back and set it up for a go at being ready for the big step into new OSes.
First trial to boot on a subvol ended up failing to load the xfce4 Desktop.
EDIT: 5/22/19 Upgraded to Linux-5.1.3.arch2-1-ARCH with no problems. Thread count is now 22359.
EDIT: 5/23/19 Upgraded to Linux-5.1.4.arch1-1-ARCH with no problems. Thread count is now 22365.
EDIT 5/28/19 Upgraded to Linux-5.1.5.arch1-2-ARCH with no problems. Thread count is now 22381.
EDIT: 6/2/19 Upgraded to Linux 5.1.6.arch1-1-ARCH with no problems. Thread count is now 22392.
EDIT: 6/8/19 Upgrade to Linux-5.1.7.arch1-1-ARCH with no problems. Returned yesterday from trip to Virginia to visit the gravesite of my Sister who died 61 years ago and is buried in Arlington Cemetery very near the entrance gate. This was the first time I was able to see her resting place. Thread count is now 22408.
EDIT: 6/12/19 Upgraded to Linux-5.1.8.arch1-1-ARCH with no problems. Thread count is now 22421.
EDIT: 6/14/19 Upgraded to Linux 5.1.9.arch1-1-ARCH with no problems. Thread is 22430. Note the new Linux trial system located at Distrotest.net but it is overloaded with activity. Try again tmw. Happy Father's Day as is appropriate.note
EDIT: 6/18/19 Upgraded to Linux-5.1.11.arch1-1-ARCH with no problems. Thread count is now 22437.
EDIT: 6/20/19 Upgraded to Linux-5.1.12.arch1-1-ARCH with no problems. Thread count is now 22449. Used Distrotest.net to observe Gentoo with success.
EDIT: 6/24/19 Upgraded to Linux-5.1.14.arch1-1-ARCH with no problems Thread count is now 22485.
EDIT: 6/26/19 Upgraded to Linux-5.1.15.arch1-1-ARCH with no problems. Linux downloads in 7 to 10 seconds. Thread count is now 22500.
EDIT: 7/7/19 Upgraded to Linux-5.1.16.arch1-1-ARCH with no problems. Earthquake(s) in this area caused no damage from rolling activity felt as far as Mexico. August 14 is my 94th b'day. Hallelujah !
EDIT: 7/11/19 Upgraded to Linux-5.2.0.arch2-1-ARCH with no problems. Thread count is now 22539. Note that earthquake crack is seen from space, everyone wondering what's next.
EDIT: 7/16/19 Upgraded to Linux-5.2.1.arch1-1-ARCH with no problems. Thread count is now 22554.
EDIT: 7/23/19 Upgraded to Linux-5.2.2.arch1-1-ARCH with no problems. Thread count is now 22561.
EDIT: 7/27/19 Upgraded to Linux-5.2.3.arch1-1-ARCH with no problems. Thread count is now 22582. Installed Darktable to handle my new camera transfers to computer. Also have Gimp and trying out Dropbox in my BTRFS OS, root only.
EDIT: 7/30/19 Upgraded to Linux-5.2.4.arch1-1-ARCH with no problems. Thread count is now 22594.
EDIT: 7/31/19 Upgraded to Linux5.2.5/arch1-1-ARCH with no problems. Thread count is now 22600. Dropbox worked fine with my new camera .png at 36MB. Hafta study Blender to achieve 3D file to send via dropbox !
EDIT: 8/7/19 Upgraded to Linux-5.2.6.arch1-1-ARCH with no problems. Thread count is now 22619. Blender is a monstrous program and hard to decipher. Something to keep me busy
EDIT: 8/9/19 Upgraded to Linux-5.2.6.arch1-1-ARCH with no problems. Thread count is now 22631. Managed to get a video included with Blender but finding the next steps in the myriad options is a big sweat. Learning curve is hard to rise with older versions shown in tutorial texts.
EDIT: 8/10/19 Upgraded to Linux-5.2.7.arch1-1-ARCH with no problems. Thread count is now 22633.
EDIT: 8/11/19 Upgraded to Linux-5.2.8.arch1-1-ARCH with no problems. Thread count is now 22639. Three more days and I start my 95th year day one.
EDIT: 8/17/19 Upgraded to Linux-5.2.9.arch1-1-ARCH with no problems. Thread count is now 22663. Birthday on Aug 14 made me 94 years young so I am three days into my 95th year. Learning how to use my camera with darktable and blender since the camera generates raw output. Very fine PNG images are produced with CTL-e from Darktable files. Associated with this is the need for a method to send such large files. So Dropbox can do it.
EDIT: 8/29/19 Upgraded to Linux-5.2.10.arch1-1-ARCH with no problems. Continuing to learn Darktable for processing my fujifilm dslr camera images. The gui is hard to read for a 94 year old WWII vet. All 5 systems are running nicely, none have failed in the several years of service. Four of them are 128GB and the fifth is 1 TB. All use BTRFS in full size root only.
EDIT: 8/30/19 Upgraded to Linux-5.2.11.arch1-1-Arch with no problems. Thread count is now 22700. New model of hearing aid uses hex inverter square wave operating at 2 milliamps and modulated by an electret to produce FM harmonics detected by Walkman FM receiver on the 17th odd harmonic. Two batteries supply power, one a Ni-Zinc in the Walkman and the other a 4 volt lithium to operate the hex inverter oscillator. Full quieting is obtained and the drift rate is about 0.2mhz in an hour and a half. This is heard as a noise input and corrected with a down button push to restore tuning to the harmonic again. Both batteries can be restored to full capacity overnight. Retuning after recharge is straight forward to the initial channel. Walkman holds all components and fits into shirt pocket. Unit is not a $4000 item but does well for hearing loss. Walkman allows for hearing the news and listening to music and can be turned off at will to save battery juice. The controls are accessible thru the shirt material with push button controls. No data on how long the walkman can run on its battery.
EDIT: 9/9/19 Upgraded to Linux-5.2.13.arch1-1-ARCH with no problems. I may try charging the Walkman battery at night with current from the lithium battery to replace some of the charge used during the day rather than removing the battery for full charge elsewhere.
Thread count is now 22721.
EDIT: 9/13/19 Upgraded to Linux-5.2.14.arch2-1-ARCH with no problems. Thread count is now 22730. Bought a new FM receiver and will outfit it for my circuit addition to add hearing aid circuit.
EDIT: 9/19/19 Upgraded to Linux-5.3.0.arch1-1-Arch with no problems. Thread count is now 22750. Testing continues on my hearing aid attachment.
EDIT: 9/23/19 Upgraded to Linux-5.3.1.arch1-1-ARCH with no problems. Thread count is now 22761.
EDIT: 10/6/19 Upgraded to Linux-5.3.4.arch1-1-ARCH with no problems. Thread count is now 22803.
EDIT: 10/11/19 Upgraded to Linux-5.3.5.arch1-1-ARCH with no problems. Thread count is now 22814. Completed my hearing design requiring only one resistor, square wave device , electret, mounting board, and eflte lithium battery. These generate an fm signal tuneable in the fm broadcast band. Many harmonics are generated in the square wave device even to the 27th harmonic which enhances the deviation to cover two or three channels of the fm band. Can use the am or fm band of the Walkman to receive news and music. The drift of the signal is rather slow and can be followed by the up/down buttons on the Walkman.
EDIT: 10/14/19 Upgraded to Linux-5.3.6.arch1-1-ARCH with no problems. Thread count is now 22819. Note that Jason has taken the taco route to paradise !!
EDIT: 10/19/19 Upgraded to Linux-5.3.7.arch1-1-ARCH with no problems. Thread is now 22840. Walkman use reveals very useful time to correct for channel shift of an hour or more for the well charged battery. Somewhat faster as the charge falls below 3.700 volts. Surprising stability for such a high harmonic signal.
EDIT: 11/13/19 Upgraded to Linux-5.3.11.arch1-1-ARCH with no problems. Thread count is now 22932. Lost many edits in this entry post for what cause I do not realize.
EDIT: 11/22/19 Upgraded to Linux-5.3.12.1-1-Arch with no problems. Thread count is now 22963.
EDIT: 11/28/19 Upgraded to Linux-5.3.13.1-1ARCH with no problems. Thread count is now 22988.
EDIT: 12/2/19 Upgraded to Linux-5.4.1.arch1-1-ARCH with no problems. Thread count is now 22998. Still having Turkeybone soup and pumpkin pie !!!
EDIT: 12/6/19 Upgraded to Linux-5.4.2.arch1-1 with no problems. Trying a new design of the hearing aid using just one aaa battery. It seems to have merit when using ni-zn aaa batteries. Thread count is now over 23000: 23009. About a hundred views per month.
EDIT: 12/14/19 Upgraded to Linux-5.4.3.arch1-1 with no problems. Thread ct is now 23026.
EDIT: 12/19/19 Upgraded to Linux-5.4.5.arch1-1 with no problems. Thread is now 23034.
EDIT: Upgraded to Linux-5.4.6.arch1-1 with no problems. Thread ct is now 23047.
EDIT: 12/25/19 Upgraded to Linux-5.4.6.arch3-1 with no problems. Thread Ct is now 23060.
Edit:1/2/20 Upgraded to Linux-5.4.7.arch1-1 with no problems. Thread count is now 23076.
EDIT; 1/27/20 Upgraded to Linux-5.4.14.arch1-1 with no problems. Thread count is now 23257. My health has become a major problem. I am in Hospice care at my home with a weak heart.
EDIT: 2/11/2020 Upgraded to Linux-5.5.2--arch2-2 with no problems. Thread count is now 23367. Forever grateful for the archlinux team and the very fine support in the forums.
EDIT: 2/16/2020 Upgraded to Linux-5,5.4.arch1-1 with no problems. Thread count is now 23413. May soon move to Arkansas.
Last edited by lilsirecho (2020-02-17 02:58:10)
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Ran another method of testing write and read speeds:
results:
sh-4.2# dd if=/dev/zero of=test bs=1048576 count=2048
2048+0 records in
2048+0 records out
2147483648 bytes (2.1 GB) copied, 87.708 s, 24.5 MB/s (write)
sh-4.2# dd if=test of=/dev/null bs=1048576
2048+0 records in
2048+0 records out
2147483648 bytes (2.1 GB) copied, 1.46163 s, 1.5 GB/s (read)
sh-4.2# More confusion!
EDIT: Problem solved. Moved the drives to MASTER slots and now the read speed for the raid is 180mb/s.
Last edited by lilsirecho (2012-04-20 04:05:18)
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
The raid0 combo boots to xfce4 Desktop in seven seconds with CF devices by Adata.
Read speed is 123MB/s in hdparm for the 16GB Adata 266x devices.
Have boot partition, swap partition and root partition......none other.
System has vlc,mirage,kdenlive,smplayer,gparted,firefox,thunderbird,jumanji,and qtfm.
Snappy system.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Latest install of the raid0 with lesser items in Desktop boots in ~5 seconds to Desktop xfce4.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Axiom states "don't put all your eggs in one basket".
So I have created three pairs of raid0 grub2 bootable to allow for backup and versatility.
Thus, video could be the theme for one raid, along with the normal needs.
Graphics specials on another raid along with the normal needs.
Specialized internet access for the third theme along with the normal needs.
Only a few themes I can conjure up at the moment but each would have 27GB of compact flash within its array.
Effective storage for apps thusly is 27 x 3= 81GB.
My system is limited to two master sata ports such that I cannot create a larger raid0 array because the flash devices require master interface.
Guess I need to upgrade the mobo in order to study a larger raid0 array.
Note that ivy bridge is being released but reviews indicate it isn't a big improve over sandy bridge(except in the lowered power needs,,,a plus).
Still on a learning curve, sticking my neck out where most fear to tread and testing the results.
One question remains for the raid0 with linux kernels. It may not upgrade the kernel and still boot without intervention. The array is mdadm generated and usually gets clobbered in upgrades.
When linux-3.3.1-1 is released in x86_64 I will find out.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Just finished installing the linux-3.3.3-1 kernel and all is well with the raid system.
Now have two more arrays to upgrade. Pleased as punch!
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Finished install of linux-3.34.3-1 kernel in all three raid0 array devices and rebooted all successfully.
So the kernel upgrades OK so far!
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
It seems I have commited a cardinal sin in Linux: (from dmesg)
879397] mdassemble: sending ioctl 800c0910 to a partition!
[ 0.879403] mdassemble: sending ioctl 800c0910 to a partition!
[ 0.879413] mdassemble: sending ioctl 1261 to a partition!
[ 0.879416] mdassemble: sending ioctl 1261 to a partition!
[ 0.879764] mdassemble: sending ioctl 800c0910 to a partition!
Mea culpa, meaculpa, meamaximaculpa!
[
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Some notes regarding the procedures I utilized in generating this raid system.
When finished with the install via arch setup, skipping the bootloading steps, I installed arch via USB HDD. I placed the two CF devices in Master slots ti insure that the MBR to be installed would be placed in a bootable portion of the boot CF device.
(The partitioning of the two CF devices provided 100mb of free space at the beginning of the device to allow for the grub2 and MBR data.
After booting into arch from the usb hdd, i ran the following:
cat /proc/mdstatThis produced a response indicating the presence of raid0 /dev/md127.
I then ran:
mdadm --stop /dev/md127Now I have to assemble my /dev/md0, thusly:
mdadm --assemble /dev/md0 /dev/sda2 /dev/sdb2 This produces the start of /dev/md0.
Following that, I mounted /dev/md0:
mount /dev/md0 /mnt/md
cd /mnt/mdThen prepared the chroot:
mount -t proc proc proc/
mount -t sysfs sys sys/
mount -o bind /dev dev/
mount /dev/sda1 boot/
chroot . /bin/bashWhile in chroot, the following was entered, each command executed in turn without errors:
pacman -S grub2-bios
grub-mkconfig -o /boot/grub/grub.cfg
grub-install /dev/sda
mdadm -D --scan >> /etc/mdadm.conf
mkinitcpio -p linux(This completes the install to MBR in /dev/sda and enables mdadm to be utilized in the boot sequence to boot from /dev/sda1 boot partition.)
I have generated four Raid0 partitioned boot CF device pairs with this arrangement. One with maxell 400x udma, and three with adata266x devices.
Use of different methods of chroot may introduce other necessary steps of which I am not aware.
I provide this post to make the details more prominent regarding the chroot parameters. I credit the source given in my intial post for the complete solution of raid0 mdadm bootable arrays with devices other than CF, since my application is unique to Compact Flash(although it may be appropo for other flash devices as well, maybe even SSD?
It is important that the CF devices be partitioned with free space at the beginning of the device to allow for the grub2 data and mbr. Thus, to make the raid function, all raid devices need the same free space at the beginning to insure equal sizing of the device partitions in the raid.
My approach partitioned for boot,swap and root. Other combos are permitted. Mine seems to be minimal and includes swap for insurance, probably not needed since my system has 3 GB of ram.
Five second boot time is the best I have achieved with my 945GCM-S2 mobo in x86_64 arch.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Performed pacman upgrade to linux-3.3.4-1 successfully in raid0 this date.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
The system installed has 4.33GB of system packages and a capacity of some 27GB.
The latest linux upgrade has affected the read speed readings to more normal numbers altho no effort has been made to alter the chunk size.
The system appears as follows in /proc:
sh-4.2# cat /proc/mdstat
Personalities : [raid0]
md0 : active raid0 sda2[0] sdb2[1]
29299712 blocks super 1.2 512k chunks
unused devices: <none>
sh-4.2# I plan to use this as it stands until the next kernel upgrade.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
The following data indicates the states provided by the devices in the raid0:
sh-4.2# hdparm -I /dev/sda2
/dev/sda2:
CompactFlash ATA device
Model Number:
Serial Number: CF CARD A0202F59
Firmware Revision: 20090728
Standards:
Likely used: 6
Configuration:
Logical max current
cylinders 31045 31045
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 31293360
LBA user addressable sectors: 31293360
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 15279 MBytes
device size with M = 1000*1000: 16022 MBytes (16 GB)
cache/buffer size = 1 KBytes (type=DualPort)
Capabilities:
LBA, IORDY(can be disabled)
bytes avail on r/w long: 4
Standby timer values: spec'd by Vendor
R/W multiple sector transfer: Max = 1 Current = 0
Advanced power management level: disabled
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
Power Management feature set
* Write cache
WRITE_BUFFER command
READ_BUFFER command
NOP cmd
CFA feature set
Advanced Power Management feature set
* Mandatory FLUSH_CACHE
* CFA advanced modes: pio5 pio6 mdma3 mdma4
* CFA Power Level 1 (max 500mA)
HW reset results:
CBLID- above Vih
Device num = 0
Integrity word not set (found 0x0000, expected 0xb2a5)
sh-4.2# The following for the second device:
sh-4.2# hdparm -I /dev/sdb2
/dev/sdb2:
CompactFlash ATA device
Model Number:
Serial Number: CF CARD A01007DF
Firmware Revision: 20090728
Standards:
Likely used: 6
Configuration:
Logical max current
cylinders 31045 31045
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 31293360
LBA user addressable sectors: 31293360
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 15279 MBytes
device size with M = 1000*1000: 16022 MBytes (16 GB)
cache/buffer size = 1 KBytes (type=DualPort)
Capabilities:
LBA, IORDY(can be disabled)
bytes avail on r/w long: 4
Standby timer values: spec'd by Vendor
R/W multiple sector transfer: Max = 1 Current = 0
Advanced power management level: disabled
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5 udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
Power Management feature set
* Write cache
WRITE_BUFFER command
READ_BUFFER command
NOP cmd
CFA feature set
Advanced Power Management feature set
* Mandatory FLUSH_CACHE
* CFA advanced modes: pio5 pio6 mdma3 mdma4
* CFA Power Level 1 (max 500mA)
HW reset results:
CBLID- above Vih
Device num = 0
Integrity word not set (found 0x0000, expected 0xa8a5)
sh-4.2# This indicates UDMA5 is applicable for the devices in the raid array.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Upgraded to linux-3.3.4-2 successfully with no problem. Still running grub2 raid0 with boot partition.
Making backup now.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
There is a strange result in the works. When I run the latest hdparm on the devices I get the following:
sh-4.2# hdparm -t /dev/sda2 /dev/sdb2 /dev/md0
/dev/sda2:
Timing buffered disk reads: 188 MB in 3.02 seconds = 62.30 MB/sec
/dev/sdb2:
Timing buffered disk reads: 194 MB in 3.01 seconds = 64.48 MB/sec
/dev/md0:
Timing buffered disk reads: 244 MB in 3.02 seconds = 80.78 MB/sec
sh-4.2# This result indicates that the raid array is not responding to twice the speed of the component devices. Its not apparent why this occurs.
Perhaps it is caused by the raid being utilized to report on itself.
Since the array is extent and is identified as md0 in raid0 in proc/mdstat, it must be running at twice device speed according to raid programming.
Some advice is needed for this one!
The devices in sda and sdb are CF cards adata 266x. Thus they are specified to run at 40mb/s. The readings given in hdparm indicates a fifty percent increase in read speed.
Then the read speed of md0 should be 120 mb/s. This figure was obtained in previous setups of raid0 using grub rather than grub2.
This discrepancy exists on all of my raid0 devices generated with this booting method.
Perhaps there is a grub.cfg requirement for raid devices in grub2.
Then again, the read speed of the sda and sdb devices could be erroneous and the md0 read speed correct. Thus twice the specified read speed of the component devices in this case is 80mb/s. Confusing for sure!
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
The mystery is no longer mysterious.........
Booted the system in a usb HDD and assembled the raid devices as /dev/md0.
One device is situated in a primary slot and the other is in a slave position associated with a different Master port.
Running hdparm on this setup produces:
sh-4.2# mdadm --stop /dev/md127
mdadm: stopped /dev/md127
sh-4.2# mdadm --assemble /dev/md0 /dev/sda2 /dev/sdb2
mdadm: /dev/md0 has been started with 2 drives.
sh-4.2# hdparm -t /dev/sda2 /dev/sdb2 /dev/md0
/dev/sda2:
Timing buffered disk reads: 194 MB in 3.01 seconds = 64.46 MB/sec
/dev/sdb2:
Timing buffered disk reads: 188 MB in 3.02 seconds = 62.22 MB/sec
/dev/md0:
Timing buffered disk reads: 374 MB in 3.01 seconds = 124.11 MB/sec
sh-4.2# The results indicate that the raid array is running at twice the speed of each of the component devices.
This is indicative of raid0 operation.
The reason for the discrepancy when running in the raid0 system is that the raid0 cannot run the system and have hdparm interfere. In other words, hdparm cannot produce accurate speed readings on a raid array while the raid is active in use.
This solves the apparent , confusing , dilemma by reinforcing the need to be separate from the raid system in order to run speed tests. Even then, raid speed tests with hdparm can still be a problem according to googling.
I am satisfied that the results look like raid0 is operating correctly.
My raid0 perks along with 5 second boot to Desktop xfce4. I use jumanji for the internet calling most used url's when opening jumanji.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Upgraded all four raid0 pairs today.
According to the system log, my raid0 /dev/md0 has 4.53GB in use and a capacity of 27.4GB for a 16% usage percentage.
My use of the booting system from grub2 partition mode is not the only application. Raid 5 and 6 are possible according to the author of the method.
Perhaps other forms are also possible.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Successfully installed linux-3.3.5-1 and rebooted ok.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Placed four CF cards in the system with two raid0 systems.
Booting from Master or Slave pairs or master-slave.
Raid0 read speed for a data pair 16GB 266x is 129mb/sec.
Raid0 read speed for maxell 16GB UDMA CF cards is 178mb/sec.
Hdparm is suspect for these readings since the devices are connected in stripe mode.
Will check the speed with another methiod.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Haven't found a good way to run tests on the raid0.
Perhaps there is a better method than hdparm but I can't locate one.
As a side note, I find in Fry's specials a Silicon Power 32GB 600x CF card. This is the first 600x device I have seen advertised(high priced Lexar excluded). It is supposed to be fully UDMA capable. I don't know what that means in actual performance terms. I find no pertinent and complete specs for the devices as is general practice for such devices. It may not boot in my system.
They claim both high read and high write speeds but these figures are for camera uses.
Perhaps a user has made something go in Linux with these CF cards?
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Performed hdparm on an 8GB SLC raid0 pair and obtained 80MB/s in the raid0 combo. This is consistent with the rated speed for the individual devices @266x of 40mb/s.
With 16GB devices, the hdparm read speed is fifty percent higher than the rated speed thus an mlc 16GB device pair at 400x produces a read speed in raid0 of 176mb/s.
The 16GB devices are assumed to be mlc devices.
Thus mlc devices report speeds that may be erroneous in hdparm tests. If not erroneous, the mlc devices perform better in raid0.
Perhaps a user can explain the difference?
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Reading the data on maxell 400x 16GB cf device shows an UDMA setting of udma6 is its capability.
A pair of these devices read speed in raid0 is 178mb/s.
Another device pair has an udma capability of udma5 and its read speed pair in raid0 is 143mb/s.
Udma setting may be the key to better performance even though the speed rating is less than the resulting performance.
Strange things!
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Mounted maxell raid0 pair and ran a file transfer from Desktop to /tmp.
The file is ~630MB and it transferred in ~2.4 seconds. This is ~262mb/s.
sh-4.2# time cp /root/Desktop/noname_0.avi /tmp
real 0m1.192s
user 0m0.007s
sys 0m1.177s
sh-4.2# Edit:I now realize it was running from cache. More reasonable numbers obtained in a clean test indicate 88 mb/s with one raid pair and 100mb/s with a second raid pair.
Last edited by lilsirecho (2012-05-17 15:57:55)
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Perhaps it is best to select all repo sources or at least core and extra if installing from remote sources. This establishes the sync files necessary.
This ensures that the grub2-bios in extra repo can be installed via pacman during the chroot.
The entries in /etc/mdadm.conf are critical for the partitioned boot. Blkid will aid in determining the correct entries . Mdadm -D /dev/md(x) will provide the uuid for the /md block device.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
I now have five pairs of raid0 bootable partition grub2 devices.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Upgraded all 5 pairs of raid0 CF cards to linux-3.3.7-1 64bit in 45 minutes.
The download size was ~61MB and my internet speed is not blazing-fast adsl.
Raid pairs comprise one 16GB pair, 4 thirty-twoGB pairs and one 64GB pair.
I have attempted to combine 4 16Gb devices in raid0 but suspect I don't have enough operating space in my system to allow chroot to function with 64GB of system mounted.
Probably will attempt a three level raid0 at 48GB.
With a 16GB pair I have 25.4 GB of free space so I haven't loaded much into the system. Each pair can perform different functions as I previously stated.
Total size of the five pairs is 128GB. Each pair boots at different speeds, best is five seconds and most is 12 seconds.
System power use is low and the system has fan noise but no HDD noise. The CF cards are fast performers and the use of only one partition is part of the story. System has enough ram to obviate swap need....3.2GB.
CF marches on!
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline