Usb block special device not writable

This is a system programming / kernel level issue.
I'm doing some hardware development on Mac OS X. When I plug the USB device in question in, I get a message box like this: "Disk Insertion: The disk you inserted was not readable by the computer" with two options, Ignore and Eject. If I choose ignore, the USB device can be accessed via the block special device /dev/disk1. However, /dev/disk1 cannot be opened for writing, even as root: the open(2) call always fails with EACCESS.
A "diskutil info /dev/disk1" reports "Read Only: Yes." Could this be the issue? How does Mac OS decide to set this flag?
FYI, a userspace program that interacts with this device file has so far been ported successfully to Windows, Linux, and FreeBSD. There's no read-only toggle switch on the device itself.
Thanks in advance for any info you may have.

Ok, I've managed to rebuild the IOUSBMassStorage kext from source, with DEBUG_LEVEL cranked way up. What follows is the syslog trace that comes right after plugging in the device. The first error we hit is kIOUSBPipeStalled, and then things finally snowball up to kIOReturnNotResponding. I'm no USB expert, but shouldn't a call to IOUSBPipe::ClearPipeStall(true) have been made pretty soon after the first error?
b400]: kBulkOnlyCommandSent returned 0
USBF: 6926.303 IOUSBMassStorageClass[0x155bb400]: BulkOnlyTransferData returned 0
USBF: 6926.304 IOUSBMassStorageClass[0x155bb400]: GetInterfaceReference
USBF: 6926.304 IOUSBMassStorageClass[0x155bb400]: kBulkOnlyBulkIOComplete returned 0
USBF: 6926.304 IOUSBMassStorageClass[0x155bb400]: BulkOnlyReceiveCSWPacket returned 0
USBF: 6926.305 IOUSBMassStorageClass[0x155bb400]: GetInterfaceReference
USBF: 6926.305 IOUSBMassStorageClass[0x155bb400]: kBulkOnlyStatusReceived returned 0
USBF: 6926.348 IOUSBMassStorageClass[0x155bb400]: SendSCSICommand was called
USBF: 6926.348 IOUSBMassStorageClass[0x155bb400]: SendSCSICommand CDB data:
USBF: 6926.348 IOUSBMassStorageClass[0x155bb400]: 0 : 0 : 0 : 0 : 0 : 0
USBF: 6926.348 IOUSBMassStorageClass[0x155bb400]: SendSCSICommandforBulkOnlyProtocol sent
USBF: 6926.348 IOUSBMassStorageClass[0x155bb400]: SendSCSICommandForBulkOnlyProtocol send CBW
USBF: 6926.348 IOUSBMassStorageClass[0x155bb400]: BulkOnlySendCBWPacket sent
USBF: 6926.348 IOUSBMassStorageClass[0x155bb400]: BulkOnlySendCBWPacket returned 0
USBF: 6926.348 IOUSBMassStorageClass[0x155bb400]: SendSCSICommandForBulkOnlyProtocol send CBW returned 0
USBF: 6926.348 IOUSBMassStorageClass[0x155bb400]: SendSCSICommandforBulkOnlyProtocol returned 0
USBF: 6926.349 IOUSBMassStorageClass[0x155bb400]: GetInterfaceReference
USBF: 6926.349 IOUSBMassStorageClass[0x155bb400]: kBulkOnlyCommandSent returned 0
USBF: 6926.349 IOUSBMassStorageClass[0x155bb400]: BulkOnlyReceiveCSWPacket returned 0
USBF: 6926.350 IOUSBMassStorageClass[0x155bb400]: GetInterfaceReference
USBF: 6926.350 IOUSBMassStorageClass[0x155bb400]: kBulkOnlyStatusReceived returned 0
USBF: 6926.350 IOUSBMassStorageClass[0x155bb400]: SendSCSICommand was called
USBF: 6926.350 IOUSBMassStorageClass[0x155bb400]: SendSCSICommand CDB data:
USBF: 6926.351 IOUSBMassStorageClass[0x155bb400]: 12 : 0 : 0 : 0 : 24 : 0
USBF: 6926.351 IOUSBMassStorageClass[0x155bb400]: SendSCSICommandforBulkOnlyProtocol sent
USBF: 6926.351 IOUSBMassStorageClass[0x155bb400]: SendSCSICommandForBulkOnlyProtocol send CBW
USBF: 6926.351 IOUSBMassStorageClass[0x155bb400]: BulkOnlySendCBWPacket sent
USBF: 6926.351 IOUSBMassStorageClass[0x155bb400]: BulkOnlySendCBWPacket returned 0
USBF: 6926.351 IOUSBMassStorageClass[0x155bb400]: SendSCSICommandForBulkOnlyProtocol send CBW returned 0
USBF: 6926.351 IOUSBMassStorageClass[0x155bb400]: SendSCSICommandforBulkOnlyProtocol returned 0
USBF: 6926.352 IOUSBMassStorageClass[0x155bb400]: GetInterfaceReference
USBF: 6926.352 IOUSBMassStorageClass[0x155bb400]: kBulkOnlyCommandSent returned 0
USBF: 6926.352 IOUSBMassStorageClass[0x155bb400]: BulkOnlyTransferData returned 0
USBF: 6926.353 IOUSBMassStorageClass[0x155bb400]: GetInterfaceReference
USBF: 6926.353 IOUSBMassStorageClass[0x155bb400]: kBulkOnlyBulkIOComplete returned 0
USBF: 6926.353 IOUSBMassStorageClass[0x155bb400]: BulkOnlyReceiveCSWPacket returned 0
USBF: 6926.354 IOUSBMassStorageClass[0x155bb400]: GetInterfaceReference
USBF: 6926.354 IOUSBMassStorageClass[0x155bb400]: kBulkOnlyStatusReceived returned 0
USBF: 6926.355 IOUSBMassStorageClass[0x155bb400]::IsProtocolServiceSupported called
message repeated 3 times ---
USBF: 6926.356 IOUSBMassStorageClass[0x155bb400]::IsProtocolServiceSupported called
message repeated 1 time ---
ForBulkOnlyProtocol send CBW
unable to probe /dev/disk1 (status code 0xFFFFFFFC).
USBF: 6927.381 IOUSBMassStorageClass[0x155bb400]: BulkOnlySendCBWPacket sent
USBF: 6927.381 IOUSBMassStorageClass[0x155bb400]: BulkOnlySendCBWPacket returned 0
USBF: 6927.381 IOUSBMassStorageClass[0x155bb400]: SendSCSICommandForBulkOnlyProtocol send CBW returned 0
USBF: 6927.381 IOUSBMassStorageClass[0x155bb400]: SendSCSICommandforBulkOnlyProtocol returned 0
USBF: 6927.451 IOUSBMassStorageClass[0x155bb400]: GetInterfaceReference
USBF: 6927.451 IOUSBMassStorageClass[0x155bb400]: kBulkOnlyCommandSent returned 0
USBF: 6927.451 IOUSBMassStorageClass[0x155bb400]: BulkOnlyTransferData returned e000404f
USBF: 6927.451 IOUSBMassStorageClass[0x155bb400]: CompleteSCSICommand kSCSITaskStatusCHECKCONDITION
USBF: 6927.451 IOUSBMassStorageClass[0x155bb400]: SendSCSICommand was called
USBF: 6927.451 IOUSBMassStorageClass[0x155bb400]: SendSCSICommand CDB data:
USBF: 6927.451 IOUSBMassStorageClass[0x155bb400]: 12 : 0 : 0 : 0 : 24 : 0
USBF: 6927.451 IOUSBMassStorageClass[0x155bb400]: SendSCSICommandforBulkOnlyProtocol sent
USBF: 6927.451 IOUSBMassStorageClass[0x155bb400]: SendSCSICommandForBulkOnlyProtocol send CBW
USBF: 6927.451 IOUSBMassStorageClass[0x155bb400]: BulkOnlySendCBWPacket sent
USBF: 6927.451 IOUSBMassStorageClass[0x155bb400]: BulkOnlySendCBWPacket returned 0
USBF: 6927.451 IOUSBMassStorageClass[0x155bb400]: SendSCSICommandForBulkOnlyProtocol send CBW returned 0
USBF: 6927.451 IOUSBMassStorageClass[0x155bb400]: SendSCSICommandforBulkOnlyProtocol returned 0
USBF: 6927.452 IOUSBMassStorageClass[0x155bb400]: GetInterfaceReference
USBF: 6927.452 IOUSBMassStorageClass[0x155bb400]: BulkOnlyExecuteCommandCompletion previous command returned e00002ed
unable to probe /dev/disk1 (status code 0xFFFFFFFC).
USBF: 6927.452 IOUSBMassStorageClass[0x155bb400]: + IOUSBMassStorageClass::FinishDeviceRecovery. Status = e00002ed
USBF: 6927.452 IOUSBMassStorageClass[0x155bb400]: FinishDeviceRecovery reseting device on separate thread.
USBF: 6927.452 IOUSBMassStorageClass[0x155bb400]: ResetDeviceNow
USBF: 6927.453 IOUSBMassStorageClass[0x155bb400]: - IOUSBMassStorageClass::FinishDeviceRecovery
USBF: 6927.453 IOUSBMassStorageClass[0x155bb400]: sResetDevice
USBF: 6927.453 IOUSBMassStorageClass[0x155bb400]: GetInterfaceReference
USBF: 6927.455 IOUSBMassStorageClass[0x155bb400]: kIOUSBMessageHubIsDeviceConnected returned = 0
USBF: 6927.455 IOUSBMassStorageClass[0x155bb400]: ResetDevice() returned = e00002e2
USBF: 6927.455 IOUSBMassStorageClass[0x155bb400]: AbortCurrentSCSITask called!
USBF: 6927.455 IOUSBMassStorageClass[0x155bb400]: sAbortCurrentSCSITask
USBF: 6927.455 IOUSBMassStorageClass[0x155bb400]: sAbortCurrentSCSITask Aborting current SCSITask with device not present.
USBF: 6927.455 IOUSBMassStorageClass[0x155bb400]: AbortCurrentSCSITask Exiting
USBF: 6927.455 IOUSBMassStorageClass[0x155bb400]: sResetDevice exiting.
disk1: device/channel is not attached.
message repeated 10 times ---
USBF: 6927.480 IOUSBMassStorageClass[0x155bb400]: ResetDevice() returned = 0
USBF: 6927.480 IOUSBMassStorageClass[0x155bb400]: sResetDevice exiting.
Message was edited by: waitpid
Message was edited by: waitpid

Similar Messages

Can't mount external HDD? "usb 1-1: Device not accepting address"

I just bought a Medion HDDRIVE2GO (Full Speed) from Aldi, and at first when I plugged it in, everything went fine (well, I thought so). Appearently it had some errors with HAL not being able to read the HDD (error name="(unset)").
I gave it a reboot, and now it does not work at all! In dmesg, I have this output (the bottom is the most important I guess)
[dell@linuxnas ~]$ dmesg
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.33-ARCH (thomas@evey) (gcc version 4.5.0 (GCC) ) #1 SMP PREEMPT Thu May 13 12:06:25 CEST 2010
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 0000000000100000 - 000000001ffe2800 (usable)
BIOS-e820: 000000001ffe2800 - 0000000020000000 (reserved)
BIOS-e820: 00000000feda0000 - 00000000fee00000 (reserved)
BIOS-e820: 00000000ffb80000 - 0000000100000000 (reserved)
Notice: NX (Execute Disable) protection missing in CPU or disabled in BIOS!
DMI 2.3 present.
last_pfn = 0x1ffe2 max_arch_pfn = 0x100000
MTRR default type: uncachable
MTRR fixed ranges enabled:
00000-9FFFF write-back
A0000-BFFFF uncachable
C0000-CFFFF write-protect
D0000-EFFFF uncachable
F0000-FFFFF write-protect
MTRR variable ranges enabled:
0 base 000000000 mask FE0000000 write-back
1 base 0FEDA0000 mask FFFFE0000 write-combining
2 disabled
3 disabled
4 disabled
5 disabled
6 disabled
7 disabled
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
e820 update range: 0000000000002000 - 0000000000010000 (usable) ==> (reserved)
Scanning 1 areas for low memory corruption
modified physical RAM map:
modified: 0000000000000000 - 0000000000002000 (usable)
modified: 0000000000002000 - 0000000000010000 (reserved)
modified: 0000000000010000 - 000000000009fc00 (usable)
modified: 000000000009fc00 - 00000000000a0000 (reserved)
modified: 0000000000100000 - 000000001ffe2800 (usable)
modified: 000000001ffe2800 - 0000000020000000 (reserved)
modified: 00000000feda0000 - 00000000fee00000 (reserved)
modified: 00000000ffb80000 - 0000000100000000 (reserved)
initial memory mapped : 0 - 01800000
init_memory_mapping: 0000000000000000-000000001ffe2000
0000000000 - 0000400000 page 4k
0000400000 - 001fc00000 page 2M
001fc00000 - 001ffe2000 page 4k
kernel direct mapping tables up to 1ffe2000 @ 15000-1a000
RAMDISK: 1fe3b000 - 1ffd2770
ACPI: RSDP 000fde50 00014 (v00 DELL )
ACPI: RSDT 000fde64 00028 (v01 DELL CPi R 27D4010C ASL 00000061)
ACPI: FACP 000fde90 00074 (v01 DELL CPi R 27D4010C ASL 00000061)
ACPI: DSDT fffe4000 0319C (v01 INT430 SYSFexxx 00001001 MSFT 0100000E)
ACPI: FACS 1ffff800 00040
0MB HIGHMEM available.
511MB LOWMEM available.
mapped low ram: 0 - 1ffe2000
low ram: 0 - 1ffe2000
node 0 low ram: 00000000 - 1ffe2000
node 0 bootmap 00016000 - 0001a000
(10 early reservations) ==> bootmem [0000000000 - 001ffe2000]
#0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
#1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
#2 [0001000000 - 0001550444] TEXT DATA BSS ==> [0001000000 - 0001550444]
#3 [001fe3b000 - 001ffd2770] RAMDISK ==> [001fe3b000 - 001ffd2770]
#4 [000009fc00 - 0000100000] BIOS reserved ==> [000009fc00 - 0000100000]
#5 [0001551000 - 0001557198] BRK ==> [0001551000 - 0001557198]
#6 [0000010000 - 0000011000] TRAMPOLINE ==> [0000010000 - 0000011000]
#7 [0000011000 - 0000015000] ACPI WAKEUP ==> [0000011000 - 0000015000]
#8 [0000015000 - 0000016000] PGTABLE ==> [0000015000 - 0000016000]
#9 [0000016000 - 000001a000] BOOTMAP ==> [0000016000 - 000001a000]
Zone PFN ranges:
DMA 0x00000000 -> 0x00001000
Normal 0x00001000 -> 0x0001ffe2
HighMem 0x0001ffe2 -> 0x0001ffe2
Movable zone start PFN for each node
early_node_map[3] active PFN ranges
0: 0x00000000 -> 0x00000002
0: 0x00000010 -> 0x0000009f
0: 0x00000100 -> 0x0001ffe2
On node 0 totalpages: 130931
free_area_init_node: node 0, pgdat c13f9880, node_mem_map c1559000
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 3953 pages, LIFO batch:0
Normal zone: 992 pages used for memmap
Normal zone: 125954 pages, LIFO batch:31
Using APIC driver default
ACPI: PM-Timer IO Port: 0x808
SMP: Allowing 1 CPUs, 0 hotplug CPUs
Local APIC disabled by BIOS -- you can enable it with "lapic"
APIC: disable apic facility
APIC: switched to apic NOOP
nr_irqs_gsi: 16
PM: Registered nosave memory: 0000000000002000 - 0000000000010000
PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
PM: Registered nosave memory: 00000000000a0000 - 0000000000100000
Allocating PCI resources starting at 20000000 (gap: 20000000:deda0000)
Booting paravirtualized kernel on bare hardware
setup_percpu: NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1
PERCPU: Embedded 14 pages/cpu @c1c00000 s34776 r0 d22568 u4194304
pcpu-alloc: s34776 r0 d22568 u4194304 alloc=1*4194304
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129907
Kernel command line: root=/dev/disk/by-uuid/5501fa6d-1664-41e3-ac30-9a475cc6843d ro vga=773
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
allocated 2620840 bytes of page_cgroup
please try 'cgroup_disable=memory' option if you don't want memory cgroups
Initializing HighMem for node 0 (00000000:00000000)
Memory: 509220k/524168k available (2895k kernel code, 14260k reserved, 1208k data, 408k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xfff1e000 - 0xfffff000 ( 900 kB)
pkmap : 0xff800000 - 0xffc00000 (4096 kB)
vmalloc : 0xe07e2000 - 0xff7fe000 ( 496 MB)
lowmem : 0xc0000000 - 0xdffe2000 ( 511 MB)
.init : 0xc1403000 - 0xc1469000 ( 408 kB)
.data : 0xc12d3f1e - 0xc14022e0 (1208 kB)
.text : 0xc1000000 - 0xc12d3f1e (2895 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
SLUB: Genslabs=13, HWalign=128, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:512
Console: colour dummy device 80x25
console [tty0] enabled
Fast TSC calibration using PIT
Detected 1993.528 MHz processor.
Calibrating delay loop (skipped), value calculated using timer frequency.. 3988.18 BogoMIPS (lpj=6645093)
Security Framework initialized
Mount-cache hash table entries: 512
Initializing cgroup subsys ns
Initializing cgroup subsys cpuacct
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys net_cls
CPU0: Hyper-Threading is disabled
mce: CPU supports 4 MCE banks
Performance Events: no PMU driver, software events only.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 11k freed
ACPI: Core revision 20091214
ACPI: setting ELCR to 0200 (from 0800)
weird, boot CPU (#0) not listed by the BIOS.
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
SMP disabled
Brought up 1 CPUs
Total of 1 processors activated (3988.18 BogoMIPS).
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfbfee, last bus=2
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using PIC for interrupt routing
ACPI: Power Resource [PADA] (on)
ACPI: ACPI Dock Station Driver: 1 docks/bays found
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci_root PNP0A03:00: ignoring host bridge windows from ACPI; boot with "pci=use_crs" to use them
pci_root PNP0A03:00: host bridge window [io 0x0000-0x0cf7] (ignored)
pci_root PNP0A03:00: host bridge window [io 0x0d00-0xffff] (ignored)
pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
pci_root PNP0A03:00: host bridge window [mem 0x000d0000-0x000dffff] (ignored)
pci_root PNP0A03:00: host bridge window [mem 0x20000000-0xfed9ffff] (ignored)
pci_root PNP0A03:00: host bridge window [mem 0xfee00000-0xffb7ffff] (ignored)
pci_root PNP0A03:00: host bridge window [mem 0xffc00000-0xfff7ffff] (ignored)
pci 0000:00:00.0: reg 10: [mem 0xe8000000-0xebffffff pref]
pci 0000:00:1d.0: reg 20: [io 0xbf80-0xbf9f]
pci 0000:00:1f.0: quirk: [io 0x0800-0x087f] claimed by ICH4 ACPI/GPIO/TCO
pci 0000:00:1f.0: quirk: [io 0x0880-0x08bf] claimed by ICH4 GPIO
pci 0000:00:1f.1: reg 10: [io 0x01f0-0x01f7]
pci 0000:00:1f.1: reg 14: [io 0x03f4-0x03f7]
pci 0000:00:1f.1: reg 18: [io 0x0170-0x0177]
pci 0000:00:1f.1: reg 1c: [io 0x0374-0x0377]
pci 0000:00:1f.1: reg 20: [io 0xbfa0-0xbfaf]
pci 0000:00:1f.1: reg 24: [mem 0x00000000-0x000003ff]
pci 0000:00:1f.5: reg 10: [io 0xd800-0xd8ff]
pci 0000:00:1f.5: reg 14: [io 0xdc80-0xdcbf]
pci 0000:00:1f.6: reg 10: [io 0xd400-0xd4ff]
pci 0000:00:1f.6: reg 14: [io 0xdc00-0xdc7f]
pci 0000:01:00.0: reg 10: [mem 0xe0000000-0xe7ffffff pref]
pci 0000:01:00.0: reg 14: [io 0xc000-0xc0ff]
pci 0000:01:00.0: reg 18: [mem 0xfcff0000-0xfcffffff]
pci 0000:01:00.0: reg 30: [mem 0x00000000-0x0001ffff pref]
pci 0000:01:00.0: supports D1 D2
pci 0000:00:01.0: PCI bridge to [bus 01-01]
pci 0000:00:01.0: bridge window [io 0xc000-0xcfff]
pci 0000:00:01.0: bridge window [mem 0xfc000000-0xfdffffff]
pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe7ffffff pref]
pci 0000:02:00.0: reg 10: [io 0xec80-0xecff]
pci 0000:02:00.0: reg 14: [mem 0xf8fffc00-0xf8fffc7f]
pci 0000:02:00.0: reg 30: [mem 0xf9000000-0xf901ffff pref]
pci 0000:02:00.0: supports D1 D2
pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:02:00.0: PME# disabled
pci 0000:02:01.0: reg 10: [mem 0x00000000-0x00000fff]
pci 0000:02:01.0: supports D1 D2
pci 0000:02:01.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:02:01.0: PME# disabled
pci 0000:02:01.1: reg 10: [mem 0x00000000-0x00000fff]
pci 0000:02:01.1: supports D1 D2
pci 0000:02:01.1: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:02:01.1: PME# disabled
pci 0000:00:1e.0: PCI bridge to [bus 02-10] (subtractive decode)
pci 0000:00:1e.0: bridge window [io 0xe000-0xffff]
pci 0000:00:1e.0: bridge window [mem 0xf4000000-0xfbffffff]
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIE._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 *11)
ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7) *11
ACPI: PCI Interrupt Link [LNKC] (IRQs 9 10 *11)
ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 9 10 *11)
vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
vgaarb: loaded
PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
Switching to clocksource tsc
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp 00:02: disabling [io 0x0800-0x0805] because it overlaps 0000:00:1f.0 BAR 13 [io 0x0800-0x087f]
pnp 00:02: disabling [io 0x0808-0x080f] because it overlaps 0000:00:1f.0 BAR 13 [io 0x0800-0x087f]
pnp 00:03: disabling [io 0x0806-0x0807] because it overlaps 0000:00:1f.0 BAR 13 [io 0x0800-0x087f]
pnp 00:03: disabling [io 0x0810-0x085f] because it overlaps 0000:00:1f.0 BAR 13 [io 0x0800-0x087f]
pnp 00:03: disabling [io 0x0860-0x087f] because it overlaps 0000:00:1f.0 BAR 13 [io 0x0800-0x087f]
pnp 00:04: disabling [io 0xf000-0xf0fe] because it overlaps 0000:00:1e.0 BAR 13 [io 0xe000-0xffff]
pnp 00:04: disabling [io 0xf100-0xf1fe] because it overlaps 0000:00:1e.0 BAR 13 [io 0xe000-0xffff]
pnp 00:04: disabling [io 0xf200-0xf2fe] because it overlaps 0000:00:1e.0 BAR 13 [io 0xe000-0xffff]
pnp 00:04: disabling [io 0xf400-0xf4fe] because it overlaps 0000:00:1e.0 BAR 13 [io 0xe000-0xffff]
pnp 00:04: disabling [io 0xf500-0xf5fe] because it overlaps 0000:00:1e.0 BAR 13 [io 0xe000-0xffff]
pnp 00:04: disabling [io 0xf600-0xf6fe] because it overlaps 0000:00:1e.0 BAR 13 [io 0xe000-0xffff]
pnp 00:04: disabling [io 0xf800-0xf8fe] because it overlaps 0000:00:1e.0 BAR 13 [io 0xe000-0xffff]
pnp 00:04: disabling [io 0xf900-0xf9fe] because it overlaps 0000:00:1e.0 BAR 13 [io 0xe000-0xffff]
pnp 00:04: disabling [io 0xfa00-0xfafe] because it overlaps 0000:00:1e.0 BAR 13 [io 0xe000-0xffff]
pnp 00:04: disabling [io 0xfc00-0xfcfe] because it overlaps 0000:00:1e.0 BAR 13 [io 0xe000-0xffff]
pnp 00:04: disabling [io 0xfd00-0xfdfe] because it overlaps 0000:00:1e.0 BAR 13 [io 0xe000-0xffff]
pnp 00:04: disabling [io 0xfe00-0xfefe] because it overlaps 0000:00:1e.0 BAR 13 [io 0xe000-0xffff]
pnp 00:04: disabling [mem 0xfa000000-0xfbffffff] because it overlaps 0000:00:1e.0 BAR 14 [mem 0xf4000000-0xfbffffff]
pnp: PnP ACPI: found 17 devices
ACPI: ACPI bus type pnp unregistered
system 00:00: [mem 0x00000000-0x0009fbff] could not be reserved
system 00:00: [mem 0x0009fc00-0x0009ffff] could not be reserved
system 00:00: [mem 0x000c0000-0x000cffff] could not be reserved
system 00:00: [mem 0x000e0000-0x000fffff] could not be reserved
system 00:00: [mem 0x00100000-0x1ffeffff] could not be reserved
system 00:00: [mem 0x1fff0000-0x1fffffff] has been reserved
system 00:00: [mem 0xfeda0000-0xfedfffff] has been reserved
system 00:00: [mem 0xfff80000-0xffffffff] has been reserved
system 00:02: [io 0x04d0-0x04d1] has been reserved
system 00:03: [io 0x0880-0x08bf] has been reserved
system 00:03: [io 0x08c0-0x08df] has been reserved
system 00:03: [io 0x08e0-0x08ff] has been reserved
system 00:09: [io 0x0900-0x091f] has been reserved
system 00:09: [io 0x03f0-0x03f1] has been reserved
system 00:0f: [io 0xbf40-0xbf5f] has been reserved
system 00:0f: [io 0xbf20-0xbf3f] has been reserved
system 00:10: [mem 0xfebffc00-0xfebfffff] has been reserved
pci 0000:00:1e.0: BAR 15: assigned [mem 0x20000000-0x27ffffff pref]
pci 0000:00:1f.1: BAR 5: assigned [mem 0x28000000-0x280003ff]
pci 0000:00:1f.1: BAR 5: set to [mem 0x28000000-0x280003ff] (PCI address [0x28000000-0x280003ff]
pci 0000:01:00.0: BAR 6: assigned [mem 0xfc000000-0xfc01ffff pref]
pci 0000:00:01.0: PCI bridge to [bus 01-01]
pci 0000:00:01.0: bridge window [io 0xc000-0xcfff]
pci 0000:00:01.0: bridge window [mem 0xfc000000-0xfdffffff]
pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe7ffffff pref]
pci 0000:02:01.0: BAR 15: assigned [mem 0x20000000-0x23ffffff pref]
pci 0000:02:01.0: BAR 16: assigned [mem 0xf4000000-0xf7ffffff]
pci 0000:02:01.1: BAR 15: assigned [mem 0x24000000-0x27ffffff pref]
pci 0000:02:01.1: BAR 16: assigned [mem 0x2c000000-0x2fffffff]
pci 0000:02:01.0: BAR 0: assigned [mem 0xf8000000-0xf8000fff]
pci 0000:02:01.0: BAR 0: set to [mem 0xf8000000-0xf8000fff] (PCI address [0xf8000000-0xf8000fff]
pci 0000:02:01.1: BAR 0: assigned [mem 0xf8001000-0xf8001fff]
pci 0000:02:01.1: BAR 0: set to [mem 0xf8001000-0xf8001fff] (PCI address [0xf8001000-0xf8001fff]
pci 0000:02:01.0: BAR 13: assigned [io 0xe000-0xe0ff]
pci 0000:02:01.0: BAR 14: assigned [io 0xe400-0xe4ff]
pci 0000:02:01.1: BAR 13: assigned [io 0xe800-0xe8ff]
pci 0000:02:01.1: BAR 14: assigned [io 0xf000-0xf0ff]
pci 0000:02:01.0: CardBus bridge to [bus 03-06]
pci 0000:02:01.0: bridge window [io 0xe000-0xe0ff]
pci 0000:02:01.0: bridge window [io 0xe400-0xe4ff]
pci 0000:02:01.0: bridge window [mem 0x20000000-0x23ffffff pref]
pci 0000:02:01.0: bridge window [mem 0xf4000000-0xf7ffffff]
pci 0000:02:01.1: CardBus bridge to [bus 07-0a]
pci 0000:02:01.1: bridge window [io 0xe800-0xe8ff]
pci 0000:02:01.1: bridge window [io 0xf000-0xf0ff]
pci 0000:02:01.1: bridge window [mem 0x24000000-0x27ffffff pref]
pci 0000:02:01.1: bridge window [mem 0x2c000000-0x2fffffff]
pci 0000:00:1e.0: PCI bridge to [bus 02-10]
pci 0000:00:1e.0: bridge window [io 0xe000-0xffff]
pci 0000:00:1e.0: bridge window [mem 0xf4000000-0xfbffffff]
pci 0000:00:1e.0: bridge window [mem 0x20000000-0x27ffffff pref]
pci 0000:00:1e.0: setting latency timer to 64
pci 0000:02:01.0: enabling device (0000 -> 0003)
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
pci 0000:02:01.0: PCI INT A -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
pci 0000:02:01.1: enabling device (0000 -> 0003)
pci 0000:02:01.1: PCI INT A -> Link[LNKD] -> GSI 11 (level, low) -> IRQ 11
pci_bus 0000:00: resource 0 [io 0x0000-0xffff]
pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffff]
pci_bus 0000:01: resource 0 [io 0xc000-0xcfff]
pci_bus 0000:01: resource 1 [mem 0xfc000000-0xfdffffff]
pci_bus 0000:01: resource 2 [mem 0xe0000000-0xe7ffffff pref]
pci_bus 0000:02: resource 0 [io 0xe000-0xffff]
pci_bus 0000:02: resource 1 [mem 0xf4000000-0xfbffffff]
pci_bus 0000:02: resource 2 [mem 0x20000000-0x27ffffff pref]
pci_bus 0000:02: resource 3 [io 0x0000-0xffff]
pci_bus 0000:02: resource 4 [mem 0x00000000-0xffffffff]
pci_bus 0000:03: resource 0 [io 0xe000-0xe0ff]
pci_bus 0000:03: resource 1 [io 0xe400-0xe4ff]
pci_bus 0000:03: resource 2 [mem 0x20000000-0x23ffffff pref]
pci_bus 0000:03: resource 3 [mem 0xf4000000-0xf7ffffff]
pci_bus 0000:07: resource 0 [io 0xe800-0xe8ff]
pci_bus 0000:07: resource 1 [io 0xf000-0xf0ff]
pci_bus 0000:07: resource 2 [mem 0x24000000-0x27ffffff pref]
pci_bus 0000:07: resource 3 [mem 0x2c000000-0x2fffffff]
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
pci 0000:01:00.0: Boot video device
PCI: CLS 32 bytes, default 64
Unpacking initramfs...
Freeing initrd memory: 1629k freed
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: overridden by ACPI.
Scanning for low memory corruption every 60 seconds
audit: initializing netlink socket (disabled)
type=2000 audit(1274299821.609:1): initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
msgmni has been set to 998
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
vesafb: framebuffer at 0xe0000000, mapped to 0xe0800000, using 1536k, total 32768k
vesafb: mode is 1024x768x8, linelength=1024, pages=41
vesafb: protected mode interface info at c000:549f
vesafb: pmi: set display start = c00c5533, set palette = c00c557f
vesafb: pmi: ports = c010 c016 c054 c038 c03c c05c c000 c004 c0b0 c0b2 c0b4
vesafb: scrolling: redraw
vesafb: Pseudocolor: size=8:8:8:8, shift=0:0:0:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0d: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
serial 0000:00:1f.6: PCI INT B -> Link[LNKB] -> GSI 5 (level, low) -> IRQ 5
serial 0000:00:1f.6: PCI INT B disabled
input: Macintosh mouse button emulation as /devices/virtual/input/input0
PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
cpuidle: using governor menu
TCP cubic registered
NET: Registered protocol family 17
Using IPI No-Shortcut mode
PM: Resume from disk failed.
registered taskstats version 1
Initalizing network drop monitor service
Freeing unused kernel memory: 408k freed
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
Floppy drive(s): fd0 is 1.44M
SCSI subsystem initialized
FDC 0 is a post-1991 82077
libata version 3.00 loaded.
ata_piix 0000:00:1f.1: version 2.13
ata_piix 0000:00:1f.1: enabling device (0005 -> 0007)
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
ata_piix 0000:00:1f.1: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
ata_piix 0000:00:1f.1: setting latency timer to 64
scsi0 : ata_piix
scsi1 : ata_piix
ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xbfa0 irq 14
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xbfa8 irq 15
ata2.01: NODEV after polling detection
ata1.00: ATA-6: HTS548040M9AT00, MG2OA5EA, max UDMA/100
ata1.00: 78140160 sectors, multi 8: LBA48
ata2.00: ATAPI: HL-DT-STDVD-ROM GDR8081N, 0108, max MWDMA2
ata2.00: configured for MWDMA2
ata1.00: configured for UDMA/100
scsi 0:0:0:0: Direct-Access ATA HTS548040M9AT00 MG2O PQ: 0 ANSI: 5
scsi 1:0:0:0: CD-ROM HL-DT-ST DVD-ROM GDR8081N 0108 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 78140160 512-byte logical blocks: (40.0 GB/37.2 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda:sr0: scsi3-mmc drive: 10x/24x cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sda1 sda2 sda3 sda4
sr 1:0:0:0: Attached scsi CD-ROM sr0
sd 0:0:0:0: [sda] Attached SCSI disk
EXT4-fs (sda3): mounted filesystem with ordered data mode
rtc_cmos 00:07: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one day, 114 bytes nvram
udev: starting version 151
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
intel_rng: FWH not detected
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Linux agpgart interface v0.103
Marking TSC unstable due to TSC halts in idle
input: PC Speaker as /devices/platform/pcspkr/input/input2
ACPI: AC Adapter [AC] (on-line)
dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input3
ACPI: Lid Switch [LID]
input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4
ACPI: Power Button [PBTN]
input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input5
ACPI: Sleep Button [SBTN]
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Switching to clocksource acpi_pm
sd 0:0:0:0: Attached scsi generic sg0 type 0
sr 1:0:0:0: Attached scsi generic sg1 type 5
parport_pc 00:0e: reported by Plug and Play ACPI
parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
iTCO_vendor_support: vendor-support=0
agpgart-intel 0000:00:00.0: Intel 845G Chipset
lp: driver loaded but no devices found
lp0: using parport0 (interrupt-driven).
agpgart-intel 0000:00:00.0: AGP aperture is 64M @ 0xe8000000
ppdev: user-space parallel port driver
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
thermal LNXTHERM:01: registered as thermal_zone0
ACPI: Thermal Zone [THM] (57 C)
Synaptics Touchpad, model: 1, fw: 5.9, id: 0x9b4cb1, caps: 0x884793/0x0
serio: Synaptics pass-through port at isa0060/serio1/input0
input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6
ACPI: Battery Slot [BAT0] (battery present)
ACPI: Battery Slot [BAT1] (battery absent)
yenta_cardbus 0000:02:01.0: CardBus bridge found [1028:012a]
yenta_cardbus 0000:02:01.0: Using CSCINT to route CSC interrupts to PCI
yenta_cardbus 0000:02:01.0: Routing CardBus interrupts to PCI
yenta_cardbus 0000:02:01.0: TI: mfunc 0x01261222, devctl 0x64
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.05
iTCO_wdt: Found a ICH3-M TCO device (Version=1, TCOBASE=0x0860)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
uhci_hcd: USB Universal Host Controller Interface driver
uhci_hcd 0000:00:1d.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
uhci_hcd 0000:00:1d.0: setting latency timer to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1d.0: irq 11, io base 0x0000bf80
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:15/LNXVIDEO:00/input/input7
ACPI: Video Device [VID] (multi-head: yes rom: no post: no)
Intel ICH Modem 0000:00:1f.6: PCI INT B -> Link[LNKB] -> GSI 5 (level, low) -> IRQ 5
Intel ICH Modem 0000:00:1f.6: setting latency timer to 64
yenta_cardbus 0000:02:01.0: ISA IRQ mask 0x0418, PCI irq 11
yenta_cardbus 0000:02:01.0: Socket status: 30000006
yenta_cardbus 0000:02:01.0: pcmcia: parent PCI bridge I/O window: 0xe000 - 0xffff
pcmcia_socket pcmcia_socket0: cs: IO port probe 0xe000-0xffff: clean.
yenta_cardbus 0000:02:01.0: pcmcia: parent PCI bridge Memory window: 0xf4000000 - 0xfbffffff
yenta_cardbus 0000:02:01.0: pcmcia: parent PCI bridge Memory window: 0x20000000 - 0x27ffffff
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
3c59x 0000:02:00.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, low) -> IRQ 11
3c59x: Donald Becker and others.
0000:02:00.0: 3Com PCI 3c905C Tornado at e0c6ac00.
Intel ICH 0000:00:1f.5: PCI INT B -> Link[LNKB] -> GSI 5 (level, low) -> IRQ 5
Intel ICH 0000:00:1f.5: setting latency timer to 64
yenta_cardbus 0000:02:01.1: CardBus bridge found [1028:012a]
yenta_cardbus 0000:02:01.1: Using CSCINT to route CSC interrupts to PCI
yenta_cardbus 0000:02:01.1: Routing CardBus interrupts to PCI
yenta_cardbus 0000:02:01.1: TI: mfunc 0x01261222, devctl 0x64
usb 1-1: new full speed USB device using uhci_hcd and address 2
[drm] Initialized drm 1.1.0 20060810
yenta_cardbus 0000:02:01.1: ISA IRQ mask 0x0418, PCI irq 11
yenta_cardbus 0000:02:01.1: Socket status: 30000006
yenta_cardbus 0000:02:01.1: pcmcia: parent PCI bridge I/O window: 0xe000 - 0xffff
pcmcia_socket pcmcia_socket1: cs: IO port probe 0xe000-0xffff: clean.
yenta_cardbus 0000:02:01.1: pcmcia: parent PCI bridge Memory window: 0xf4000000 - 0xfbffffff
yenta_cardbus 0000:02:01.1: pcmcia: parent PCI bridge Memory window: 0x20000000 - 0x27ffffff
usb 1-1: device descriptor read/64, error -71
usb 1-1: device descriptor read/64, error -71
[drm] radeon defaulting to kernel modesetting.
[drm] radeon kernel modesetting enabled.
radeon 0000:01:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
[drm] radeon: Initializing kernel modesetting.
[drm] register mmio base: 0xFCFF0000
[drm] register mmio size: 65536
[drm] GPU reset succeed (RBBM_STATUS=0x00000140)
agpgart-intel 0000:00:00.0: AGP 2.0 bridge
agpgart-intel 0000:00:00.0: putting AGP V2 device into 4x mode
radeon 0000:01:00.0: putting AGP V2 device into 4x mode
[drm] radeon: VRAM 64M
[drm] radeon: VRAM from 0x00000000 to 0x03FFFFFF
[drm] radeon: GTT 64M
[drm] radeon: GTT from 0xE8000000 to 0xEBFFFFFF
[drm] radeon: irq initialized.
[drm] Detected VRAM RAM=64M, BAR=128M
[drm] RAM width 64bits DDR
[TTM] Zone kernel: Available graphics memory: 255756 kiB.
[drm] radeon: 32M of VRAM memory ready
[drm] radeon: 64M of GTT memory ready.
[drm] radeon: cp idle (0x00008383)
[drm] Loading R100 Microcode
platform radeon_cp.0: firmware: requesting radeon/R100_cp.bin
pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: clean.
pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: clean.
pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean.
pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7:
usb 1-1: new full speed USB device using uhci_hcd and address 3
clean.
pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean.
pcmcia_socket pcmcia_socket1: cs: IO port probe 0x100-0x3af: clean.
pcmcia_socket pcmcia_socket1: cs: IO port probe 0x3e0-0x4ff: clean.
pcmcia_socket pcmcia_socket1: cs: IO port probe 0x820-0x8ff: clean.
pcmcia_socket pcmcia_socket1: cs: IO port probe 0xc00-0xcf7: clean.
pcmcia_socket pcmcia_socket1: cs: IO port probe 0xa00-0xaff: clean.
[drm] radeon: ring at 0x00000000E8000000
[drm] ring test succeeded in 1 usecs
intel8x0_measure_ac97_clock: measured 52675 usecs (2532 samples)
intel8x0: clocking to 48000
[drm] radeon: ib pool ready.
[drm] ib test succeeded in 0 usecs
[drm] Panel ID String: QDI141X1LH03
[drm] Panel Size 1024x768
[drm] Default TV standard: NTSC
[drm] 27.000000000 MHz TV ref clk
[drm] No TV DAC info found in BIOS
[drm] Default TV standard: NTSC
[drm] 27.000000000 MHz TV ref clk
[drm] Radeon Display Connectors
[drm] Connector 0:
[drm] VGA
[drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
[drm] Encoders:
[drm] CRT1: INTERNAL_DAC1
[drm] Connector 1:
[drm] LVDS
[drm] Encoders:
[drm] LCD1: INTERNAL_LVDS
[drm] Connector 2:
[drm] S-video
[drm] Encoders:
[drm] TV1: INTERNAL_DAC2
usb 1-1: device descriptor read/64, error -71
[drm] fb mappable at 0xE0040000
[drm] vram apper at 0xE0000000
[drm] size 786432
[drm] fb depth is 8
[drm] pitch is 1024
fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver
Console: switching to colour dummy device 80x25
Console: switching to colour frame buffer device 128x48
fb0: radeondrmfb frame buffer device
registered panic notifier
[drm] Initialized radeon 2.0.0 20080528 for 0000:01:00.0 on minor 0
usb 1-1: device descriptor read/64, error -71
usb 1-1: new full speed USB device using uhci_hcd and address 4
usb 1-1: device not accepting address 4, error -71
EXT4-fs (sda4): mounted filesystem with ordered data mode
usb 1-1: new full speed USB device using uhci_hcd and address 5
Adding 265064k swap on /dev/sda2. Priority:-1 extents:1 across:265064k
psmouse serio2: ID: 10 00 64
usb 1-1: device not accepting address 5, error -71
hub 1-0:1.0: unable to enumerate USB device on port 1
eth0: setting full-duplex.
input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/serio2/input/input8
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
eth0: no IPv6 routers present
lspci (Is this useable info?)
[dell@linuxnas ~]$ lspci
00:00.0 Host bridge: Intel Corporation 82845 845 [Brookdale] Chipset Host Bridge (rev 04)
00:01.0 PCI bridge: Intel Corporation 82845 845 [Brookdale] Chipset AGP Bridge (rev 04)
00:1d.0 USB Controller: Intel Corporation 82801CA/CAM USB Controller #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corporation 82801CAM ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801CAM IDE U100 Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801CA/CAM AC'97 Audio Controller (rev 02)
00:1f.6 Modem: Intel Corporation 82801CA/CAM AC'97 Modem Controller (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]
02:00.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
02:01.0 CardBus bridge: Texas Instruments PCI1420 PC card Cardbus Controller
02:01.1 CardBus bridge: Texas Instruments PCI1420 PC card Cardbus Controller

I found this post on linux forums which say It's a HAL related problem.
"rmmod ehci_hcd" made it work for some of these guys Which one of them explains It's a data speed issue. Cables.., 2.0 1.0, that sort of things. Read it, I bet you'll get more out of it, It's old though.
Try removing the module, plugging the drive, check dmesg, and mount manually.
Last edited by Ekimino (2010-05-20 01:23:54)

BELKIN usb wireless FSD9050 device not recognized by IMAC G4 800

Below is a thread from another group that I was advised to post here. If anyone knows of a solution or work around, it is appreciated.
Thanks
Topic : Belkin Not recognizing
This question is not answered. "Helpful" answers available: 2 . "Solved" answers available: 1 .
Reply to this Topic Subscribe to this Topic Back to Topic List
Replies : 14 - Last Post : Nov 30, 2007 6:32 AM by: real_tt
JakeHebert
Posts: 4
Registered: Sep 19, 2007
Belkin Not recognizing
Posted: Sep 19, 2007 9:04 PM
Reply Email
I bought the Belkin Wireless usb Mimo F5D9050 and it worked amazing with my Ibook G3 800Mhz.. but then it started to occasionally not work until i would eject it and reconnect it a few times.. Now no matter how many time si reconnect it it will not work... ive tried to re-install the belkin but still no luck.. and so i plugge dit into my Windows pc and it worked fine... What could this be! im going nuts
Ibook G3 800 Mhz Mac OS X (10.3.9)
Ronda Wilson
Posts: 13,597
From: The cornfields of Nebraska
Registered: Feb 2, 2003
Re: Belkin Not recognizing
Posted: Sep 19, 2007 9:39 PM in response to: JakeHebert
Reply Email
Hi, Jake. Welcome to Apple Discussions.
It's possible that your AirPort card has fizzled out on you. AirPort card failure doesn't happen very often, but it happened to me once, and it was very frustrating.
We diagnosed what was wrong with mine by my husband swapping his AirPort card with mine. Then my iBook would connect, but his wouldn't, so we knew it was the card.
Will the iBook work on any wireless network? Do you have someone with whom you could swap cards to see if that's the problem?
Possible sources for replacing the original AirPort card (links last checked 8/19/07):
http://www.dvwarehouse.com/Apple-Original-AirPort-Wireless-Card-802.11B-p-31366. html
http://www.synaptech.com/catalog/index.php?mainpage=index&cPath=4953
http://www.powerbookguy.com/xcart/catalog/Airport-Cards-price0-p-1-c-507.html
http://www.expercom.com/productdetail.html?PRODUCTID=305851
http://www.macrecycling.com/ibook-g3-c-18.html
http://techrestore.com/xcart/product.php?productid=16174
eMac800/SuperDrive/512/OS 9.2.2; iBook800G3Combo/640-OS X 10.3.9; Mac OS 9.2.x iBook G4/1.2G/768/OS X 10.4.9
JakeHebert
Posts: 4
Registered: Sep 19, 2007
Re: Belkin Not recognizing
Posted: Sep 20, 2007 1:40 PM in response to: Ronda Wilson
Reply Email
well. no i have no airport card, and never have had one.. this wirless card is a usb plug-in one and .. it is recognized by every compute ri plug it into except the on ei need it for.. yet the one thats not recognizing it now USED to recopgnize it not even 2 weeks ago!... its realllyy frustrating... i mis susing my ibook lol
Ibook G3 800 Mhz Mac OS X (10.3.9)
Ronda Wilson
Posts: 13,597
From: The cornfields of Nebraska
Registered: Feb 2, 2003
Re: Belkin Not recognizing
Posted: Sep 20, 2007 3:12 PM in response to: JakeHebert
Reply Email
Have you tried using the other USB port? If neither port works, try plugging in a USB mouse to see if it works to confirm that your USB ports aren't damaged.
Have you installed any new software? Maybe a Security Update or something similar? Sometimes that will break functionality of third-party drivers.
You may need to go to the website of the manufacturer of the USB wireless device to see if an updated driver is available.
eMac800/SuperDrive/512/OS 9.2.2; iBook800G3Combo/640-OS X 10.3.9; Mac OS 9.2.x iBook G4/1.2G/768/OS X 10.4.9
JakeHebert
Posts: 4
Registered: Sep 19, 2007
Re: Belkin Not recognizing
Posted: Sep 20, 2007 4:11 PM in response to: Ronda Wilson
Reply Email
mmm.. Both usb ports work fine with my wireless mouse... i will have to talk to a tech of Belkin.. but i hate that because i already had to once before... bahh... but i did search for a new updated version of the driver for the ** thing.. but no such luck.. I dont think any new software has been installed though ... i appreciat eyour help though Ronda!
Ibook G3 800 Mhz Mac OS X (10.3.9)
Ronda Wilson
Posts: 13,597
From: The cornfields of Nebraska
Registered: Feb 2, 2003
Re: Belkin Not recognizing
Posted: Sep 20, 2007 5:57 PM in response to: JakeHebert
Reply Email
You're most welcome.
What is the model number of the adapter?
eMac800/SuperDrive/512/OS 9.2.2; iBook800G3Combo/640-OS X 10.3.9; Mac OS 9.2.x iBook G4/1.2G/768/OS X 10.4.9
JakeHebert
Posts: 4
Registered: Sep 19, 2007
Re: Belkin Not recognizing
Posted: Sep 20, 2007 6:24 PM in response to: Ronda Wilson
Reply Email
umm its um f5d9050 the 3001 series... its HUGE lol... but it USED to work like a dream.. baah
Ibook G3 800 Mhz Mac OS X (10.3.9)
Ronda Wilson
Posts: 13,597
From: The cornfields of Nebraska
Registered: Feb 2, 2003
Re: Belkin Not recognizing
Posted: Sep 20, 2007 8:10 PM in response to: JakeHebert
Reply Email
When did you buy it, Jake?
There is a driver that was released on June 19, 2007.
http://www.belkin.com/support/article/?lid=en&pid=F5D9050&aid=5925&scid=0
Even if this is the one you have installed, you may want to reinstall it.
Good luck.
eMac800/SuperDrive/512/OS 9.2.2; iBook800G3Combo/640-OS X 10.3.9; Mac OS 9.2.x iBook G4/1.2G/768/OS X 10.4.9
real_tt
Posts: 4
Registered: Nov 29, 2007
Re: Belkin Not recognizing
Posted: Nov 29, 2007 6:13 PM in response to: JakeHebert
Reply Email
Did this one ever get a real response. Mine is doing the same thing and the machine will not recognise that the usb is even plugged in. Any help is appreciated
Mac OS X (10.5.1)
Ronda Wilson
Posts: 13,597
From: The cornfields of Nebraska
Registered: Feb 2, 2003
Re: Belkin Not recognizing
Posted: Nov 29, 2007 6:21 PM in response to: real_tt
Reply Email
Hi, and welcome to Apple Discussions.
Since Jake hasn't posted in over two months, either that driver worked for him, he found the answer elsewhere, or he gave up. Since he hasn't posted back, we have no way of knowing.
What model computer do you have?
eMac800/SuperDrive/512/OS 9.2.2; iBook800G3Combo/640-OS X 10.3.9; Mac OS 9.2.x iBook G4/1.2G/768/OS X 10.4.9, MacBook 2.0/2 GB/10.4.x
real_tt
Posts: 4
Registered: Nov 29, 2007
Re: Belkin Not recognizing
Posted: Nov 29, 2007 6:35 PM in response to: Ronda Wilson
Reply Email
I MAC G4 and I have tried every driver listed on the forums with no success
it states to go to the network in system pref. to set up device
there appear to be no way I can figure out how to add the usb device
any help is appreciated
Mac OS X (10.5.1)
Ronda Wilson
Posts: 13,597
From: The cornfields of Nebraska
Registered: Feb 2, 2003
Re: Belkin Not recognizing
Posted: Nov 29, 2007 10:29 PM in response to: real_tt
Reply Email
Since you're running Leopard, I surmise that your iMac takes the AirPort Extreme card?
May I ask why you don't just get one of those? As I post this, the Apple Store has a refurbished one for $29.00.
http://store.apple.com/1-800-MY-APPLE/WebObjects/AppleStore.woa/wa/RSLID?find=%2 2extreme+card%22
eMac800/SuperDrive/512/OS 9.2.2; iBook800G3Combo/640-OS X 10.3.9; Mac OS 9.2.x iBook G4/1.2G/768/OS X 10.4.9, MacBook 2.0/2 GB/10.4.x
real_tt
Posts: 4
Registered: Nov 29, 2007
Re: Belkin Not recognizing
Posted: Nov 30, 2007 5:52 AM in response to: Ronda Wilson
Reply Email
I am not running Leopard... using 10.4 and I already own the product. It is suppose to work and there is no reason to purchase another unit. All I need to understand is how to make the IMac recognize the USB device or how to configure the unit. Others have stated in this and other forums that they have used this unit with success.
Thanks for address this specific issue.
Since you're running Leopard, I surmise that your iMac takes the AirPort Extreme card?
May I ask why you don't just get one of those? As I post this, the Apple Store has a refurbished one for $29.00.
http://store.apple.com/1-800-MY-APPLE/WebObjects/AppleStore.woa/wa/RSLID?find=%2 2extreme+card%22
Mac OS X (10.5.1)
Ronda Wilson
Posts: 13,597
From: The cornfields of Nebraska
Registered: Feb 2, 2003
Re: Belkin Not recognizing
Posted: Nov 30, 2007 6:06 AM in response to: real_tt
Reply Email
Your specifications at the bottom of your post state that you're running Mac OS X 10.5.1?
You may want to post in the Internet and Networking your iMac (Flat Panel) Forum. Maybe someone there can help you out. (You've posted in the iBook G3 Forum.)
eMac800/SuperDrive/512/OS 9.2.2; iBook800G3Combo/640-OS X 10.3.9; Mac OS 9.2.x iBook G4/1.2G/768/OS X 10.4.9, MacBook 2.0/2 GB/10.4.x
real_tt
Posts: 4
Registered: Nov 29, 2007
Re: Belkin Not recognizing
Posted: Nov 30, 2007 6:32 AM in response to: Ronda Wilson
Reply Email
I am using a laptop to connect to the internet not the machine that I am writing about. If I could do that I would not need any help. I will check out the other forum but this thread is on topic.
Mac OS X (10.5.1)

The information in your thread references an iBook quite a lot but the title of this post says iMac so I going to assume that you are trying to use this device with an iMac.
It is also unclear what version of the Mac OS you are using.
Let's start by stating the fact that these USB networking networking devices are not inherently supported by the Mac OS. Therefore they need drivers. These drivers are usually fragile and only work with a well defined version (or versions) of the Mac OS. Anytime that you make any upgrade to the Mac you are able to create an incompatibility with the driver and the device.
The Belkin F5D9050 does have some Mac OS drivers available at this link.
You should uninstall/remove the current driver for this device.
Restart your iMac.
Download and install the appropriate driver for the version of Mac OS on your iMac.
Restart your iMac.
If that doesn't work, either get the original AirPort card for the internal wireless slot in the iMac or get an Ethernet wireless adapter. An Ethernet wireless adapter requires no drivers and therefore will work with any Ethernet device.

USB 3.0 devices not being detected on a Thinkpad X1 Carbon

After every reboot or cold boot, no USB 3.0 devices are detected on my
Thinkpad X1 Carbon Touch. (Intel Series 7 chipset)
There is a way to get them to be detected, but it doesn't survive a reboot
and it's ugly.
Go into device manger and uninstall the device "Intel(R) USB 3.0 eXtensible
host Controller - 0100 (Microsoft)"
The do a "Scan for hardware changes"
Then everything is detected correctly.
Bob Comer

>Is it that specific driver?
It's a driver built into Windows 10.
>What if you try the Windows 7 driver available on Intel's website here?
I tried that, Windows 10 wont replace it's own driver. (Windows has
determined that the driver software for your device is up to date.)
>Hope that helps!
I've been fighting it for a long time. It's downright annoying. I can plug
it into my USB 2.0 port and it works all the time, but a lot slower, or
even plugging it into a USB 2.0 hub that's plugged into a USB 3.0 port
always works too, and slightly faster than the USB 2.0 port. (but not as
fast as USB 3.0)
I suspect it's some kind of power management issue to do with the driver,
devices aren't getting the power up signal so they just don't show up at
all. It could be a hardware difference, but the same devices just worked
on Win8.1 and below.
Bob Comer

MacBook Pro Retina USB 2.0 devices not working in right side USB port

4 days ago I bought MacBook Pro Retina 15".
When I plug USB 2.0 device to right side USB port, it does not work. OSX does not recognize it, iPhone does not charge, and so.
When I plug the same USB 2.0 device to left side USB port, it works.
When I plug USB 3.0 device to left or right side USB ports, it works without a problem.
Does anyone have this same issue? How did you resolve it?

I have a similar issue with a 13" Retina. Both my ports work OK for most USB devices but the right one won't work with a USB external HD (Time Machine backup). Very consistant.

Nano 7th gen USB port broken - device not recognized message

Ipod Nano received for Christmas. Worked fine. Plugged into charge. Tried it today and won't power up, when I plug into the PC, I get a message that the device not recognized. The port doesn't appear to be working. What do I do?

This did not work for me. I have a laptop that was running Windows XP, and it had no problems recognizing the iPod. I was having problems with XP, and rather then reinstall XP, I did a clean install of Vista. I did a settings transfer, so the new install of iTunes came already configured--I mention this since I don't know if it was a factor.
When I plugged in the iPod, I got the USB Device Not Recognized. The usbstor.inf file did not fix the problem. However, the solution at http://www.winvistabeta.com/groups/275128/ipod-usb-device-not-recognized/message .aspx did fix the problem. Do this:
Reset the iPod:
1. Unplug the iPod.
2. Turn the hold switch to HOLD and then back to off.
3. Hold the Center and Menu buttons for 6 seconds until you get the Apple logo when you release them.
4. Plug in the iPod. It should now be recognized.
This worked fine for me the first time. Thanks! Jack

Problems with usb / sd removable devices (not/badly copying)

Hi everybody
the problem is when I plug an usb stick or a SD card, all with FAT32 fs, GNOME (I use gnome-shell) asks me if I want to mount and open the device.
so, it loads properly and when it's open I can do all the things you are supposed to do with them.
The issue first appaired when I copied some pics to an SD card. It appaired the progress bar saying it completed the copy process.
So I umounted the device and removed it. Some other people said that actually there weren't any files in the SD card.
Supposing it was bad/corrupted fs I formatted the card and put back the images there. Same issue. I was starting to think the SD card was damaged
until I had the same problem while copying music to my phone (via USB cable).
I noticed it created all the files but didn't store any actual data (e.g. size of files was always 0 byte) or even didn't do anything (neither created the file) sometimes.
Searching the web I found that it wasn't syncing - so they told me to do the sync command on the shell - nothing solved.
So as I read on the wiki [fstab], I mounted the devices with options "sync,flush", which in fact solved the problem.
[Actually I later found that it works even without the flush option, just with the sync option]
Doing so I solved the problem and could copy all the data to the devices.
What I want to know is: how can I say to GNOME (or anyother GNOME uses to mount devices) "well, whenever I put a removable device, mount it with the sync option" ?
thank you in advance,
azzka
PS: [not so important]: I noticed very slow copying bitrate, and I did what the wiki says about but didn't solve anything. Any ideas?

Yep HV,
Verify the discs in the disc utility and see if that works. It'll probably take an hour or so cos the disc utility's performance has been less than favorable.
Try this: Turn off the computer, disconnect the drives, then restart the computer. Now, re-connect the drives while the computer is running, let them mount and see if you can eject them. One would assume it is a permissions issue, however, with the multitude of glitches appearing with ext drives and USB devices in Leopard it's hard to assume anything.
Persevere!

Differences between block special device and character special device

Hi,
I tried to figure out the differences of block and raw devices and try to understand when to use each type of device. To me they are about the same. Can someone enlighten me? For e.g "/dev/dsk/c0t0d0s5" and "/dev/rdsk/c0t0d0s5". I noticed that in "/etc/vfstab", the mounting process always use a block device whereas the fsck process always use a character device, I'm getting confuse about their differeces.
Thank you for your help!

I cannot speak for CS6. Here are thoughts from a new APE11 user's view:
adobe30022 wrote:
Our needs for a video editor are very simple. We need to create simple titles and text overlay to show the name of the speaker and/or topic.
APE11 provides simplicity and good functionality for this stated need.
we would like to sync up the video with this audio. Can this be done in Adobe Premiere Elements 11?
If your video and audio contain a clap, you can manually sync by sliding the audio peak along the video. The audio wave form will be blanked out when sliding, with a frame counter showing how many whole frames you have moved the audio at each moment, so it is a "drag, stop, compare, drag another frame or two, stop, compare" process that works. (Finer adjustment than whole frames is not possible.) Once the sync is achieved, select both audio and video track and link them. (The stability of the sync over time will depend on the accuracy of the recorder, and can pose a problem in long recordings. )
increase the gain/volume for the audio or clean up some hum or background noise. Can this be done in Adobe Premiere Elements 11?
APE11 allows adjusting the volume levels and also provides level normalization if desired, but more involved audio cleanup such as hiss and hum removal, compression, or auto gain are not available.
Please let me know if Adobe Premiere Elements 11 can help us meet our needs. If there is any other software that would be more suitable please advise.
You should download the APE11 trial to judge for yourself how well it will meet all your needs.

Satellite M50D-A : USB 3.0 devices not working in USB 3.0 ports

I can use 2.0 devices in the 3.0 ports fine, but my 3.0 device Flash Voyager USB3 8GB will not work. It connects then disconnects once, not showing up in device manager at all.
I've tried installing the USB driver off this site version 2.0.10.273-130101a for my model. That made no difference.
Install system Windows 8.1
Any ideas? Thanks.

The Voyager USB stick is manufactured by Corsair
I found in Corsair forum some threads and complaints about the troubles connecting the Voyager USB3.0 stick to USB 3.0 ports. Here the link the Corsair threads:
http://forum.corsair.com/v3/showthread.php?t=115891
http://forum.corsair.com/v3/showthread.php?t=111945
It looks like there are some compatibility problems between the USB controller (from AMD but _not_ Intel) and this USB stick.
One of the solutions could be the usage of other USB 3.0 flash memory sticks which are supported by AMD chipset.
You could also try to update the driver manually. You will need to check firstly the chipsets specs and name. To do that, I recommend you to install some kind of hardware diagnostic software (Everest Home Edit or Sandra Sisoft).
Then you could check on AMD page if an update for this chipset is available.

Raw device not seen after reboot the server

hi,
I hv upgrade kernal in linux 7.2 but when reboot system no raw device found
how can find out raw device

From http://www.fors.com/orasupp/unix/37914_1.HTM
Raw Devices and Oracle - 20 Common Questions and Answers
2. How can a raw device be recognised?
In the /dev directory, there are essentially two type of files: block
special and character special. Block special files are used when data is
transferred to or from a device in fixed size amounts (blocks), whereas
character special files are used when data is transferred in varying
size amounts. Raw devices use character special files; a long listing
of the /dev directory shows them with a 'c' at the leftmost position of
the permissions field, e.g.
crw-rw-rw- 1 root system 15, 0 Mar 12 09:45 rfd0
In addition, character special files usually have names beginning with
an 'r', as shown in the above example. Some devices, principally disks,
have both a block special device and a character special device
associated with them; for the floppy diskette shown above, there is also
a device
brw-rw-rw- 1 root system 15, 0 Apr 16 15:42 /dev/fd0
So the presence of a 'c' in a device does NOT necessarily mean this is a
raw device suitable for use by Oracle (or another application).
Generally, a raw device needs to be created and set aside for Oracle (or
whatever application is going to use it) when the UNIX system is set
up - therefore, this needs to be done with close co-operation between
the DBA and UNIX system administrator.
Once a raw device is in use by Oracle, it must be owned by the oracle
account, and may be identified in this way.

USB 2.0 devices get slow after standby / hibernation when docked for Windows 7

Hello,
I am the proud owner of a Lenovo ThinkPad T400. I am having difficulty with my usb 2.0 devices not hooking up to my computer after I resume my computer from hibernation or sleep modes. I tried searching the forum for someone who has had the problem and I seem to have found nothing, but if I missed something I am sorry for the inconvenience. I found this link (http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-73031) but this fix is for XP. Should this still work the same for 7? Is there any other fix that I do not know about?
Thanks in advance for your help.

pjg,
Did you have the same problem with your T500? I did not ever to seem to have this problem until recently. I am trying to figure out if I am missing something inside windows that would detect all of the USB components plugged into it. I don't remember having this problem with Vista. I would not think that there should be much of a difference, with respect to this issue, from Vista to 7.
I bought my machine when Vista was available and I did not notice a long lag time for USB devices, so I upgraded to 7 and I just re-installed all of the software that Lenovo puts on their machines (the preloaded factory stuff) and there was no change. I am running out of ideas to try and fix this.

SOLVED: Mounting IDE ZIP Drives, "Special Device hdb4 Does Not Exist"

I thought I would post a follow-up, since I have finally resolved this long standing issue, which has plagued me since my first days with Linux many years ago.
As outlined in my original post below, every time I would attempt to access a Zip disk for the first time since boot, Linux (pretty much all distros I have ever tried, with the exception of SuSE 9.3) would fail to mount the disk and report back that "Special device hdb4 does not exist". Of course the "hdb4" part varies from distro to distro and machine to machine, depending on how your Zip disk is connected and how the distro names its disks, but the basic error has been constant. I have always worked around it by redoing the mount command specifying just the device, not the partition, and while that would always fail, it would force the creation of the device /dev/hdb4, and I could carry on. Annoying but effective.
FINALLY, a long term answer. I got my inspiration from a really snarky post I read in another online forum where someone had posted this very same question (this is a very common problem with no common answer it seems!). The respondant, who completely failed to provide a helpful answer, basically said "listen, the OS is telling you what is wrong - the device hdb4 doesn't exist - so fix it, and all will be just fine". Of course, the respondant didn't even bother to offer a suggestion about HOW to fix it.
However, therein lies the inspiration for the solution. Indeed they are right, /dev/hdb4 *doesn't* exist, so how to fix that? They had a point. I started researching the mysteries of mknod, a program that can create /dev files, and the even deeper mysteries of Linux device numbers, both major and minor.
In the end, I found a wonderfully informative document that described the current standard for the device numbering scheme used by mknod, and Linux in general. The key things of interest are this:
1/ The major number for IDE based drives is 3.
2/ IDE allows for 64 partitions per device, so the minor numbers are 0-63 for device "a", 64-127 for device "b" and so on. You derive the minor number of interest for your particular device by taking the starting value of the minor number range of interest for your device and adding the partition number to it. So, for example, hdb4 would have a minor number of 64 (the start of the minor number range for device "b") plus 4 (the partition number in "hdb4"), yielding a result of 68.
3/ The major number for SCSI based drives, or those that your OS treats as SCSI, is 8.
4/ SCSI allows for 16 partitions per device, so the minor numbers are 0-15 for device "a", 16-31 for device "b" and so on. You derive the minor number of interest for your particular device by taking the starting value of the minor number range of interest for your device and adding the partition number to it. So, for example, sdb4 would have a minor number of 16 (the start of the minor number range for device "b") plus 4 (the partition number in "hdb4"), yielding a result of 20.
In my case, Arch seems to be treating all of my disk based devices as SCSI, perhaps because I do have a real SCSI interfaced Jaz drive in my machine. So, the Zip disk of interest in my machine is sdc4 (my real SCSI jaz is sda, my Arch root is sdb, and the IDE Zip is sdc). Applying the above, for /dev/sdc4:
- The major number is 8.
- The minor number is 32 (start of range for device "c") plus 4 (the partition number) = 36.
Armed with this knowledge, I su'd to root and entered:
# mknod /dev/sdc4 b 8 36
and like magic, there is was, /dev/sdc4. I popped a disk into the drive and my first attempt to access it was greeted with success, not the usual "device does not exist" error! By the way, the "b" in the above command is just part of the mknod syntax, and indicates that I am creating a block device (vs. a character device, or some other type of device - disk drives all seem to be "block" devices for apparent reasons).
SO, determine your major number by device type (it will usually be 3 or 8), compute your minor number by device letter and partition number, and add a mknod command to your system startup (so you don't have to do it manually every time) and you are done! No more annoying "device does not exist" errors.
Now for the kicker. It turns out that this information has been available under my nose all along. I just didn't recognize the code. If you do the following:
# ls -ald /dev/sd*
Linux obligingly provides you with the major number and the start of the minor number range for your device. Since Linux has always detected the Zip *device* (just not the partition) this is really all you need to know. When I issue the above command, I get an output like:
brw-rw---- 1 root disk 8, 32 date time /dev/sdc
Guess what, there they are! "8" is the major number of interest, "32" is the start of the minor number range of interest. If I had just recognized that, and known that all I had to do was add the partition number to the minor number to get the magic number to feed into mknod, things would have been easier.
Sorry for the long post, but like so many things in Linux, the OS doesn't make this easy on the uninitiated. I sincerely hope that this post may help lots of other people to resolve this vexing and longstanding problem.

Solved!
See the lengthy response in this post:
http://bbs.archlinux.org/viewtopic.php?id=36468
I posted the solution separately, with the most informative title I could come up with, so that others Googling this topic on the web may hopefully easily find it.

Special device does not exist, FSTAB Issue

I set up this arch64 install last night, and till now I've managed all right except for one niggling issue. For some odd reason, when I installed everything I forgot to add my "sandbox" partition in Fstab. I thought I could just generate a UUID then add a line to Fstab later, and I did just that. However, as its not part of my LVM, I'm wondering if thats why I cannot mount my sandbox partition from Fstab. Ideas appreciated.
My fdisk -l output:
[root@acer ~]# fdisk -l
Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x379c7acb
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 6428 51528487+ 5 Extended
/dev/sda3 6429 14593 65585362+ 8e Linux LVM
/dev/sda5 14 6428 51528456 83 Linux
Disk /dev/mmcblk0: 7969 MB, 7969177600 bytes
221 heads, 20 sectors/track, 3521 cylinders
Units = cylinders of 4420 * 512 = 2263040 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 2 3522 7778304 b W95 FAT32
Fstab as it stands now -
/etc/fstab: static file system information
(cut out irrelevant lines about tmpfs & commented out optical devices)
/dev/mapper/vg0-lv_home /home ext3 defaults,noatime 0 1
/dev/mapper/vg0-lv_root / ext3 defaults,noatime 0 1
/dev/mapper/vg0-lv_swap swap swap defaults,noatime 0 0
/dev/mapper/vg0-lv_var /var ext3 defaults,noatime 0 1
UUID=a7d625c6-0fb9-41f5-bdba-6d306c90739a /boot ext2 defaults 0 1
UUID=a802d8f4-f70e-4ed5-ab72-65bb0ebdca9b /media/sandbox ext3 defaults,users,noatime 1 2
## Memory card at /dev/mmcblk0p1 /media/memorycard
UUID=238db34b-8bf3-4510-b8ee-1aa46e04f17d /media/memorycard vfat defaults,users,noauto,noatime 0 0
The error I get when I issue a "mount -a" as root or just let the computer boot up with the "sandbox" in fstab -
mount: special device UUID=a802d8f4-f70e-4ed5-ab72-65bb0ebdca9b does not exist

Having the same problem with flash memory set as /dev/sdb1. It refuses to mount claiming the device doesn't exist.
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/sda2 / reiserfs defaults,noatime 0 1
/dev/sda1 /boot ext2 defaults,noatime 0 1
/dev/sda3 swap swap defaults 0 0
/dev/sdb1 /media/flash auto ro,user,noauto,unhide 0 0
/dev/cdrom /media/cdrom auto ro,user,noauto,unhide 0 0
/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
P.S.
Yuuhuuuuu post #600

USB Storage devices not working with kernel in repositories [Solved]

I am experiencing a quite vexing problem with my USB Mass Storage devices, when I plug one in I get the following error in my dmesg:
[ 1811.976758] usb 2-2: new high speed USB device number 5 using ehci_hcd
[ 1812.101854] scsi7 : usb-storage 2-2:1.0
[ 1813.102576] scsi 7:0:0:0: Direct-Access Verbatim STORE N GO 2.68 PQ: 0 ANSI: 2
[ 1813.103818] sd 7:0:0:0: [sdb] 3913728 512-byte logical blocks: (2.00 GB/1.86 GiB)
[ 1813.104327] sd 7:0:0:0: [sdb] Write Protect is off
[ 1813.104331] sd 7:0:0:0: [sdb] Mode Sense: 0b 00 00 08
[ 1813.105567] sd 7:0:0:0: [sdb] No Caching mode page present
[ 1813.105572] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[ 1813.107560] sd 7:0:0:0: [sdb] No Caching mode page present
[ 1813.107565] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[ 1813.108340] sdb: sdb1
[ 1813.112180] sd 7:0:0:0: [sdb] No Caching mode page present
[ 1813.112186] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[ 1813.112190] sd 7:0:0:0: [sdb] Attached SCSI removable disk
[ 1813.196828] sdb: detected capacity change from 2003828736 to 0
In the /dev/ folder on the device shows up, not the partitions. When I try to open it with cfdisk I get "FATAL ERROR: Cannot open disk drive". I am pretty sure it iss neither a hardware problem with my laptop or my usb devices, as they both work on my dual-booted Ubuntu. My usb ports in general seem to be functioning, I can still charge a phone through them and use my built in USB webcam.
I am not sure where exactly this issue lies, it started after I upgraded to 3.0.7 (among other updates) from the normal repositories, but still persisted after I downgraded to 3.0.6.
My attempts at Googling have so far revealed mainly hardware errors, which don't seem to fit with the devices working on another OS on the same pc.
Thanks.
Last edited by MartianW (2011-11-09 16:30:15)

Same problem. I try to mount different devices. For each device same result.
The file /var/log/error.log is full of this kind of messages:
Nov 4 21:34:18 moria kernel: [ 113.455195] sd 6:0:0:0: [sdb] No Caching mode page present
Nov 4 21:34:18 moria kernel: [ 113.455200] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Nov 4 21:35:29 moria kernel: [ 184.077728] sd 7:0:0:0: [sdb] No Caching mode page present
Nov 4 21:35:29 moria kernel: [ 184.077736] sd 7:0:0:0: [sdb] Assuming drive cache: write through
Nov 4 21:35:29 moria kernel: [ 184.080720] sd 7:0:0:0: [sdb] No Caching mode page present
Nov 4 21:35:29 moria kernel: [ 184.080730] sd 7:0:0:0: [sdb] Assuming drive cache: write through
Nov 4 21:35:30 moria kernel: [ 184.808109] sd 7:0:0:0: [sdb] No Caching mode page present
Nov 4 21:35:30 moria kernel: [ 184.808116] sd 7:0:0:0: [sdb] Assuming drive cache: write through
Nov 4 21:41:10 moria kernel: [ 525.107109] sd 8:0:0:0: [sdb] No Caching mode page present
Nov 4 21:41:10 moria kernel: [ 525.107114] sd 8:0:0:0: [sdb] Assuming drive cache: write through
Nov 4 21:41:10 moria kernel: [ 525.110615] sd 8:0:0:0: [sdb] No Caching mode page present
Nov 4 21:41:10 moria kernel: [ 525.110619] sd 8:0:0:0: [sdb] Assuming drive cache: write through
Nov 4 21:41:11 moria kernel: [ 525.841487] sd 8:0:0:0: [sdb] No Caching mode page present
Nov 4 21:41:11 moria kernel: [ 525.841491] sd 8:0:0:0: [sdb] Assuming drive cache: write through

Lenovo Vibe X2 - USB device not recognized

Dear All, Hope all is fine with you. Friends, I have bought this model (Lenovo Vibe X2) in the month of January 2015 from online purchase in India. THe phone is really nice, except the few things i.e. Picture/Camera Quality specially in low light, the photo quality is too poor, if there is network issue, phone gets heat a lot but overall, I am completely satisfied with the product. Recently, I have came across one issue, that from April onwards, my phone if connected to Laptop/Desktop using USB cable, it charge's but shows the message as "USB Device not recognized". I tried lot of things, even factory resetting but nothing helped me. Download the drivers as well, but no use. Tried with multiple computers but same message. Can anyone tell me how can I fix this issue? Since I have lot of data & need to sync my contact & backup the phone regularly, I face lods of issues doing above activities. Your help is really appreciated. The phone is currently having Android Lolypop (5.0). Below are the details: Model Number: Lenovo X2-AP Android Version: 5.0 Baseband Version (Slot1)-X2-AP-L.V2,2015/05/20 16:26 BASEBAND VERSION (SLOT2) X2-L.MD2-V3, 2015/05/11 10:14 BUILD NUMBER: X2-AP_S224_150709_ROW Regards, Sachin

Lenovo vibe x2-ap sotwer

Usb block special device not writable

Similar Messages

Maybe you are looking for