Firewire card reader os x 10.7
Can anyone advise of a firewire compact flash card reader which is compatible with Lion? If not a USB 2 card reader which is fairly quick, Just upgraded my camera and the RAW files are rather large!
Thanks
Thanks Allan
I cannot seem to find that p/n in UK. I can find Lexa Professional UDM but usb 3 which I do not think the iMac has?
I wonder if they have changed them.
Regards
Similar Messages
-
Can anyone help with a troublesome FireWire card reader
I have an Addonics firewire card reader to transfer image files to my Macs. It has never been predictable about mounting on the desktop when I insert a card. I've used it with OS 10.2, 10.3 and now 10.4.8. I have the OS set to open Photo Mechanic when I insert a card, but most times, nothing happens. After trying various daisy-chain connections, I have the reader connected directly to the computer, but this hasn't helped.
Usually, I have to disconnect the cable, then re-connect; I usually do this at the reader end, to save wear and tear on the computer port. Sometimes multiple attempts are necessary, but in the end, this procedure gets results better than anything else. I have tried a different cable, known to be good, with no improvement.
I have a little utility called Spindown HD, which shows what's attached, and in fact, the reader shows up as connected, but sleeping. So, perhaps this is a "wake-from-sleep" problem instead.
By the way, Addonics "support" was useless. Their site states that they offer no support on products over two years old. An email inquiry brought the response that they could do nothing to help. On service quality grounds alone, I have bought my last Addonics product.
Do others have problems with getting FW readers to respond? This is driving me crazy, and wearing out ports or connectors.bad card reader, un-supported by Addonics (mfg)
-
Firewire card reader won't mount since 10.4.9 update
If anybody knows of a resolution to this issue, I'd surely appreciate it if you would share that knowledge!
I have two SanDisk Firewire ImageMate Compact Flash card readers (model #SDDR-80 Rev:B). They've been very reliable (and fast) - have had them for over 3 years now. Never had a problem with them or their interoperability with either of my Macs (I also own a PowerBook G4 17" (1.67Ghz).
The other day (4/17), I installed the 10.4.9 (Combined) update on my PowerMac without a hitch. My card reader was connected at the time, and I quickly found out that the reader would not mount on my desktop after the update, but would appear in the System Profiler as "Unknown Device".
Just for the "fun of it", I installed the same update on my PowerBook, repaired permissions, then attached my other card reader (same model). Same friggin' thing!
A glutton for punishment, I disconnected the card reader, reinstalled Tiger from scratch (Erase and Install), and applied the 10.4.9 (Combined) update as before. To my utter disgust, I got the same behavior.
Now there's no doubt in my mind that the problem here is with Apple's 10.4.9 update, and that I'll likely be downloading 2GB's of images via a very slow USB connection directly from my camera until Apple releases yet another update, but I thought I'd give all the Apple geeks out there a shot at this first - you know, just for the fun of it.
Thanks in advance!Abbott1,
As you pointed out, I've done a little detective work here already - as I do with any problem I've have with my Macs. I find that in virtually every case, I'll resolve the issue myself - which is why this is the first time I've posted to Apple's discussion board.
You see, once upon a time, I provided 2nd tier Mac technical support in addition to acting as a liason to the engineers for a huge printer company whose name begins with an "X". I've been working with OS X since it was beta, and have been honing my Mac "detective skills" ever since. Now, I realize that I sound as though I'm tooting my own horn here, but I wanted to point out that I'm not another Mac newbie who just made the switch.
In my experience, taking this issue to Apple's Genius Bar will have only one of two outcomes - they will either deny the problem is Apple's, or they'll tell me to wait for an update - neither of which resolves the issue itself.
As it happens, I may very well end up showing the problem to one of the guys at the Genius Bar anyway, as I'm having an unrelated problem with the "G" key on my PowerBook - it has decided that it no longer wishes to reside with the other keys on the keyboard, and keeps trying to extricate itself just to prove it.
I knew it was a shot in the dark when I posted the original question, but I was hoping that some genius out there would beat Apple to the punch and have figured out a solution to the problem that didn't require me purchasing new card readers to replace perfectly good ones. I sure hope this problem doesn't exist in Leopard.
The card readers don't require any 3rd party software - there are no drivers, firmware updates, etc. - they define "plug-n-play".
Thanks for posting! -
Faster card reader -- USB 3 rocks
Just a heads-up for those interested. I got a USB 3 card reader yesterday (SanDisk ImageMate All-in-one, from B&H). It seems to be much faster than my old Lexar FireWire card reader. USB 3 has almost completely superceded FireWire in my practice.
The SanDisk reader is petite -- 1 x 4 x 12 cm. That's without the USB 3 cable, which is long enough for desk use but gargantuan for portability. I'll look for a smaller cable.
I selected the ImageMate because I needed a reader that accepts Memory Stick, SDHC, and Compact Flash. It also accepts Micro cards.I could take it to an Apple store. Maybe I will do that.
Good to be sure of simple stuff. Yes. I connected this to a windows PC and it works -- at least as a USB 2 device.
Yes, the blue light does come on.
BUT, you gave me a big clue here ..... This is a USB issue. I just plugged it NOT into the USB 3 port on the mini but a USB 2 port on my monitor -- that is connected to the mini. BINGO. It works.
So, something with USB 3 is not supported here ... -
Where can I get an internal memory card reader?
Is there one that also combines to give usb 3.0, firewire, SATS, etc.?combo cards are terrible but if you look you will see that Highpoint has a USB3 card, yes; or SATA3 (which is probably better).
FW is slower than any drive in existence now.
multi interface chip cards have never performed well but needed back in their day, like OldWorld PowerMacs and those lacking FW800 and USB2.
www.macsales.com/firewire -
Firewire 800 card reader with OS 10.6
Can anyone confirm whether the Lexar Firewire 800 card reader will work with OS 10.6.2 etc? I'm told it won't.
Adobe Reader>Preferences>Internet.
-
I just bought 3 Lexar Professional UDMA FireWire® 800 Card Readers. The problem I am having is that they wont work in the 800 port. It cant be the card reader because they are plug and play and not all 3 would be broken. So, either there is a firmware update or something. Please help.
ThanksHave you tried using the readers individually, using the long fw800 cable, and not the short connecting ones? I have two of them and the short cable(s) caused some transfer problems in which I lost images. Perhaps because they get bent so much, the stress damaged the short cables somehow.
-
I have a G4/APG Sawtooth.
Has anyone installed any kind of card reader or USB/Firewire panel in the ZIP Drive slot?
If so, how did you alter the bezel?
thx
MacMini, TiBook, G4 AGP, iMacs & SE Mac OS X (10.4.6) that SE just won't die..."What about buying a PCI card like the Sonnet Tango (http://www.sonnettech.com/product/tango_2.html) and then getting a generic PC hub to mount in the bay and plug into the Sonnett card?"
That's what I did.
It works fine except for one thing.
I can't use Option-boot. My mouse clicks don't get recognized correctly when I try to select a boot drive.
I'm pretty sure it's the hub. It has an NEC chipset according to ASP. -
Firewire CF Card Reader Compatible Please Lexar is NOT!
Just bought a $50 Lexar Firewire Compact Flash reader only to find out it is not supported by Tiger or Lexar for Tiger. It would be nice to get a patch from Apple or a driver from Lexar but I'm not holding my breath. Right now I just want to know if there is another firewire CF card reader that will for sure work on my G4 tower running 10.4.5 Thanks!
Alex - I have the same card reader...it works FINE with my 1G Sandisk Ultra II - BUT Tiger will NOT mount a 2G Lexar card in the same reader....I've exchanged the reader twice and still no joy....WHAT IS UP WITH THIS? I can find nothing on any of the Mac forums here or elswhere and can't believe others are not having a problem...??? any ideas...anyone?
G4 Mac OS X (10.4.5) -
To capture the Mini-DV file through the 1394 firewire card from t
hii there!
first let mi make you understand what we people are doing ....
We people want to capture the Mini-DV file directly through the 1394 firewire card from the sony camcorder in to the MPEG2
format. Thent on the fly(i.e.during capturing into MPEG2) we also want to capture the metadata i.e (time,date etc. of the
original shooting event) into some text file. Our MPEG2 format requirements are: 8mbps viedeo,freq-48KHz,16 bit sterio,384
audio kbps, Deinterlace... we are using JavaMediaFramework-2.1.1e(Java Media Studio tool)..so we want to explore that tool
much more coz rightnow it's not supporting MPEG2(only supporting MPEG1) and also not supporting 1394 cpture card ...we want
the codec for converting DV-AVI to MPEG2 with date and time exctrated and much more explored details about JMf2.1.1 JavaMedia
Studio to get more familiar.....
for the above mentioned problem I am trying to add the mpeg2 codec inthe plugin of the jmf studio..and i have followed the
steps ..
Download the Codec from IBM
Extracted jmf.jar
Extracted codec.zip
Added files from codec folder to jmf folder
Made a jar out of it and name it jmf.jar
Replaced that with current jmf.jar (kept a backup)
Opened JMFRegistry and in "Plugins","Codec" and now unable to add " "
this becoz i am not knowing the exact way of recopiling that newly created jar file and because of that that mpeg-2 codedc is
not get added .....so i am looking forward for any help for the above mentioned problem!
I would be gratefull on getting ur help coz it's such challenging and techy concept to explore...
thanks..
nilesh hardikar
contact: [email protected]I understand your pain. See BUG ID 4640032: JMF does not support DSVD encoding
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4640032
Add your vote, maye Sun will hear! -
PCMCIA firewire card for G4 laptop (follow-up to excessive timecode breaks)
1.) It was recommended that I get a new firewire bus to resolve excessive timecode breaks when importing from a Canon camcorder to an external hard drive. I've been reading through posts on this topic...and saw getting a new firewire port mentioned a few times... How come when I called Apple to check on the cost of a new firewire card for my laptop Powerbook G4, I was told that nothing could be added without replacing the entire logic board? Am I missing something? I didn't say "PCMCIA firewire drive" - is that something special? Any idea of the cost to purchase and install?
2.) Apple recommended just capturing to my internal hard drive, and transfering the projects. Apart from this being cumbersome... I need a little verification: if I transfer PROJECT X to my external hard drive, then do I also need to transfer my Audio Render, Autosave,Capture Scratch, Render, Thumbnail, and Waveform folders? [I realize this is basic, but I'm wary of losing the information the project needs and getting it all messed up]
Powerbook G4, Mac OS X (10.3.9) FCP 4.5, LaCie external HD
Powerbook G4, Mac OS X (10.3.9) FCP 4.5, LaCie external HDhttp://www.bhphotovideo.com/bnh/controller/home?A=details&kw=BEAFWT2&is=REG&Q=&O =productlist&sku=304014
pcmcia is an card slot. If you have a 12" PB you may not have one.
If you have a pcmcia slot, buy the card. Slide the card into your computer and start up. Put the camcorder on the card and your fw drive on the port built-in to your computer. Even if this does not solve the timecode issues, it will save you other headaches in the future.
Question. Does capturing to your internal drive solve the timecode issues you are having?
I disagree with the advice of capturing to your internal drive and transfering the project after the fact. There are a bunch of reasons why, and all of them are qualified, so I hesitate to go further until I know whether or not capturing to the internal drive is making your timecode headaches go away.
I suspect capturing to the internal drive will not help the timecode issues which will make the whole point moot. But hopefully I'm wrong :>
Tom
ps
When you talk to representatives from Apple, you have to be conscious that if they are not specialists in the area you are focused on their advice may be based on general recommendations from an IT or home user perspective. There is a difference between talking to a sales person on the floor of the Apple Store and someone from the Genius Bar. And the person at the Genius Bar may have a tremendous background in network installations, but never have opened FCP. Or you might get lucky and get a FCP savvy genius, who would be a bit weak when talking about some other area.
This is not a knock, just a reality. It is difficult to be deeply conversant with even one area. It is not realistic for the generalists you usually deal with to know the best answers to very specific questions.
I'm working toward becoming a certified trainer with FCP and it is not easy or cheap to become an expert at this one application, never mind all the possible applications and hardware combinations for wildly different needs and budgets. -
How can I restore my card reader after upgrading to Mavericks?
I have a MacBookPro that is not identifying the SD card reader since installing Mavericks. I have heard that ScanDisk has a patch but I have not been able to download it from their site. I have read that downloading the SandDisk patch on a PC and then transferring it to a Mac will fix the problem. I would sure appreciate some help restoring my Mac after uploading to Mavericks. My firewire drive does not seem to be working either. I cannot use my M-Audio firewire interface for recording and editing in ProTools. This represents a lot of down time and/or a pretty big loss of money for me. Can anybody tell me whether Apple provides support for these types of problems or is it completely up to the user to solve them? I am a relatively new Apple user. I bought the MacBook Pro shortly after they were released, about 2 1/2 years ago. Up to that time I was strictly a Windows user. I am surprised Apple did not seem to go to much, if any trouble to warn me of the difficulty I would have after upgrading to Mavericks. Apple, where are you?
Launch the Image Capture app in your Applications folder.
Conenct the card reader.
Then see if Image Capture recognizes the card unde DEVICES top left side of the Image Capture window.
BEFORE upgrading from one OS X to the next, check the websites for your third party software and hardware for compatibility.
Apple is not responsible for third party software and hardware used with your Mac. -
[SOLVED]Laptop Internal SD card reader no longer working
Two weeks ago I purchased a Raspberry Pi and set up my own SD card with Arch Linux ARM using the directions at http://archlinuxarm.org/platforms/armv6/raspberry-pi with the internal SD card reader on my laptop and had no issues. Today I decided to load up a XBMC distro to a new SD card, but my internal card reader doesn't seem to autodetect or mount my new card. I tried inserting my other card with Arch ARM that I know is a good card, but it no longer works with that card either. Here are all my logs that I could think of to post for any advice:
uname -r
3.9.8-1-ARCH
lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express PCI Express Root Port (rev 03)
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02)
00:1c.2 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 4 (rev 02)
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 02)
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 02)
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode] (rev 02)
00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02)
01:00.0 VGA compatible controller: NVIDIA Corporation G73M [GeForce Go 7600] (rev a1)
02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 01)
06:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller (rev c0)
06:04.0 CardBus bridge: ENE Technology Inc CB-712/4 Cardbus Controller (rev 10)
06:04.1 FLASH memory: ENE Technology Inc ENE PCI Memory Stick Card Reader Controller (rev 01)
06:04.2 SD Host controller: ENE Technology Inc ENE PCI Secure Digital Card Reader Controller (rev 01)
06:04.4 FLASH memory: ENE Technology Inc SD/MMC Card Reader Controller (rev 01)
lsusb
Bus 001 Device 002: ID 0c45:624f Microdia PC Camera (SN9C201 + OV9650)
Bus 004 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 74.5G 0 disk
|-sda1 8:1 0 9.3G 0 part /
|-sda2 8:2 0 63.3G 0 part /home
`-sda3 8:3 0 1.9G 0 part [SWAP]
sr0 11:0 1 1024M 0 rom
fdisk -l
Disk /dev/sda: 80.0 GB, 80026361856 bytes, 156301488 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x000f2f32
Device Boot Start End Blocks Id System
/dev/sda1 * 63 19535039 9767488+ 83 Linux
/dev/sda2 19535040 152296199 66380580 83 Linux
/dev/sda3 152296200 156301487 2002644 83 Linux
dmesg | tail
[17198.557922] mmc0: new SDHC card at address aaaa
[17535.391900] mmc0: card aaaa removed
[17537.984043] mmc1: new SDHC card at address aaaa
[18198.208331] usb 4-1: new full-speed USB device number 3 using uhci_hcd
[18199.855227] mmc1: card aaaa removed
[18221.345032] usb 4-1: USB disconnect, device number 3
[18473.771242] mmc1: new SDHC card at address aaaa
[20787.874847] mmc1: card aaaa removed
[21102.784624] mmc1: new high speed SDHC card at address e624
[21119.691467] mmc1: card e624 removed
It seems I have all the necessary information, but I am not sure where to go from here. It's obvious my laptop is detecting the card being inserted and removed, but the card reader is never listed in /dev so I can't mount it. It's listed under lspci but not under lsusb. I'm assuming that it was two weeks ago and that's why it worked, but I'm not sure how to get lsusb to detect it so it will work again. Thanks for any help you guys have.
Last edited by coolcashews (2013-07-06 00:32:55)Thanks for your quick reply. Here are the logs you asked for:
lsmod | grep mm
mmc_core 94486 2 sdhci,sdhci_pci
usb_common 954 1 usbcore
pacman -Qi linux
Name : linux
Version : 3.9.9-1
Description : The linux kernel and modules
Architecture : x86_64
URL : http://www.kernel.org/
Licenses : GPL2
Groups : base
Provides : kernel26=3.9.9
Depends On : coreutils linux-firmware kmod mkinitcpio>=0.7
Optional Deps : crda: to set the correct wireless channels of your country
Required By : None
Optional For : None
Conflicts With : kernel26
Replaces : kernel26
Installed Size : 65511.00 KiB
Packager : Tobias Powalowski <[email protected]>
Build Date : Wed Jul 3 16:00:01 2013
Install Date : Fri Jul 5 11:31:57 2013
Install Reason : Explicitly installed
Install Script : Yes
Validated By : Signature -
At present, the only way I can load photos from a CF card to my new Macbook Pro Retina is by loading them onto an external hard drive via an old PC that can accept either of my USB card readers, then plugging the external hard drive into my MBP. Neither the USB card reader or the cable that comes with the Canon HDSLR camera will transfer photos directly to my MBP. I find it unbelievable that I have to go to a PC to load photos because I can't do it with my new MBP.
Has anyone found a reliable USB CF card reader, or one that connects via thunderbolt or HDMI, at any price, that will work directly with the new MBP Retina?This is what we need:
Location photoshoot - we use the Canon EOS 5D Mk II still camera & the Canon FX100 pro camcorder.
CF cards are: SanDisk Extreme UDMA & SanDisk Extreme Pro UDMA 6 for video (I think they are both Type II) My Mac recognises them both as FAT 32 format
My MBPRetina is on the latest version of Mountain Lion OSX 10.83
the files from the camcorder will transfer to my MacBook Pro Retina directly via the camera's cable but it is quite slow & it means I cannot continue to film while downloading files but this we can live with.
the files from the still camera Canon EOS 5D Mk II will not transfer directly via the camera's cable - have yet to get the Canon software to download, but via the camera's cable will not help anyway as we need to have the still camera free to keep shooting.
We need to be able to take out the CF card from the first part of the shoot & download the still shots while just on the Macbook's battery power, while we insert a fresh CF card back into the still camera to continue with the next part of the shoot simultaneously (while the first card is downloading.)
The files from the first part of the shoot will be both in RAW (.CR2) & Jpeg format. We just need to quickly transfer the jpegs, then I do a quick sort, batch the best ones as black/white images, & use these in a client slideshow immediately after part 2 of the shoot.
Obviously we need fast data transfer speeds, & rely on the MBP's battery power while on a location shoot.
The card readers I have tried are an older specific CF card reader branded as Palm, & a USB 2 multi card reader branded as Travel Flash. With both readers, the lights on the readers flash on & off, & the MBP recognises the card & the files will even appear both in Finder & in i-Photo, so it starts importing, then aborts with an error message saying:
'The Finder can’t complete the operation because some data in “” can’t be read or written.
(Error code -36)'
& another message saying:
'the disk was not ejected properly'.
So it appears the MBP does read the CF cards but the card readers don't stay connected, no matter what angle I put them on or however many times I re-connect them.
Yes, they are probably cheap & I want to buy a decent one.
So, in summary:
the card reader needs to work when the MBPR is only on battery power (I read in some forums that some USB card readers aren't so reliable on the laptop's battery power)
the card reader needs to be quite fast. I have read the USB 3 readers won't read CF cards at higher than USB 2 speeds. Is this true? Are the firewire connected ones faster, & if so, are they still reliable on the MBP's battery power?
From research, it appears my problem is associated with my specific model of Mac & platform, being MacBook Retina on Mountain Lion OSX Version 10.83. If any of the recommended card readers have been successful with this, plese let me know.
Thanks heaps for the suggestions so far. -
Texas Instruments SD card reader not writing to card
I'm having trouble getting a Texas Instruments 6-in-1 card reader to write to SD cards. It is built into an HP Pavilion DV5215us notebook, lspci:
00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 01)
00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:05.0 PCI bridge: ATI Technologies Inc Unknown device 5a37
00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller
00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 11)
00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI IDE Controller ATI
00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge
00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge
00:14.5 Multimedia audio controller: ATI Technologies Inc IXP SB400 AC'97 Audio Controller (rev 02)
00:14.6 Modem: ATI Technologies Inc ATI SB400 - AC'97 Modem Controller (rev 02)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:05.0 VGA compatible controller: ATI Technologies Inc ATI Radeon XPRESS 200M 5955 (PCIE)
06:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
06:04.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
06:04.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller
06:04.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller
06:04.4 Generic system peripheral [0805]: Texas Instruments PCI6411/6421/6611/6621/7411/7421/7611/7621 Secure Digital Controller
06:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
Using the 2.6.19.2 kernel with the tifm_core, tifm_sd, tifm_7xx1 modules on a fully up to date voodoo install (just pacman -Syu'd this morning). I can read from the SD fine at full speed, but as soon as I try to write a file to it the device disappears from KDE mediamanager and nothing gets written. Here's the dmesg output from when I insert the card and start writing a 101mb tarball:
tifm_7xx1: sd card detected in socket 3
mmcblk0: mmc3:8001 SD02G 1985024KiB
mmcblk0: p1
mmcblk0: error 4 sending stop command
end_request: I/O error, dev mmcblk0, sector 3970040
Buffer I/O error on device mmcblk0, logical block 496255
ending read/write command
end_request: I/O error, dev mmcblk0, sector 227728
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227736
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227744
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227752
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227760
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227768
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227776
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227784
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227792
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227800
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227808
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227816
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227824
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227832
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227840
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227848
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227856
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227864
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227872
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227880
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227888
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227896
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227904
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227912
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227920
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227928
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227936
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227944
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227952
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227960
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227968
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227976
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227984
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 227992
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228000
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228008
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228016
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228024
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228032
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228040
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228048
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228056
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228064
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228072
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228080
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228088
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228096
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228104
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228112
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228120
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228128
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228136
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228144
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228152
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228160
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228168
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228176
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228184
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228192
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228200
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228208
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228216
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228224
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228232
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228240
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228248
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228256
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228264
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228272
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228280
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228288
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228296
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228304
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228312
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228320
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228328
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228336
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228344
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228352
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228360
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228368
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228376
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228384
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228392
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228400
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228408
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228416
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228424
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228432
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228440
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228448
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228456
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228464
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228472
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228480
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228488
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228496
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228504
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228512
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228520
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228528
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228536
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228544
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228552
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228560
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228568
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228576
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228584
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228592
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228600
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228608
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228616
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228624
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228632
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228640
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228648
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228656
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228664
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228672
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228680
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228688
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228696
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228704
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228712
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228720
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228728
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228736
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228744
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228752
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228760
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228768
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228776
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228784
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228792
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228800
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228808
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228816
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228824
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228832
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228840
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228848
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228856
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228864
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228872
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228880
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228888
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228896
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228904
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228912
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228920
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228928
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228936
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228944
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228952
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228960
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228968
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228976
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228984
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 228992
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229000
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229008
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229016
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229024
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229032
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229040
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229048
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229056
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229064
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229072
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229080
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229088
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229096
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229104
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229112
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229120
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229128
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229136
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229144
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229152
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229160
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229168
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229176
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229184
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229192
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229200
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229208
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229216
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229224
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229232
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229240
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229248
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229256
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229264
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229272
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229280
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229288
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229296
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229304
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229312
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229320
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229328
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229336
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229344
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229352
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229360
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229368
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229376
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229384
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229392
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229400
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229408
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229416
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229424
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229432
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229440
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229448
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229456
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229464
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229472
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229480
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229488
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229496
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229504
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229512
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229520
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229528
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229536
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229544
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229552
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229560
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229568
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229576
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229584
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229592
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229600
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229608
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229616
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229624
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229632
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229640
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229648
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229656
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229664
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229672
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229680
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229688
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229696
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229704
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229712
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229720
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229728
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229736
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229744
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229752
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229760
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229768
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229776
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229784
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229792
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229800
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229808
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229816
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229824
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229832
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229840
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229848
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229856
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229864
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229872
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229880
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229888
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229896
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229904
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229912
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229920
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229928
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229936
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229944
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229952
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229960
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229968
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229976
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229984
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 229992
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 230000
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 230008
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 250
Buffer I/O error on device mmcblk0p1, logical block 1
lost page write due to I/O error on mmcblk0p1
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 251
Buffer I/O error on device mmcblk0p1, logical block 2
lost page write due to I/O error on mmcblk0p1
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 252
Buffer I/O error on device mmcblk0p1, logical block 3
lost page write due to I/O error on mmcblk0p1
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 253
Buffer I/O error on device mmcblk0p1, logical block 4
lost page write due to I/O error on mmcblk0p1
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 254
Buffer I/O error on device mmcblk0p1, logical block 5
lost page write due to I/O error on mmcblk0p1
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 255
Buffer I/O error on device mmcblk0p1, logical block 6
lost page write due to I/O error on mmcblk0p1
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 256
Buffer I/O error on device mmcblk0p1, logical block 7
lost page write due to I/O error on mmcblk0p1
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 257
Buffer I/O error on device mmcblk0p1, logical block 8
lost page write due to I/O error on mmcblk0p1
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 258
Buffer I/O error on device mmcblk0p1, logical block 9
lost page write due to I/O error on mmcblk0p1
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 259
Buffer I/O error on device mmcblk0p1, logical block 10
lost page write due to I/O error on mmcblk0p1
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 260
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 261
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 262
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 263
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 493
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 494
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 495
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 496
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 497
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 498
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 499
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 500
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 501
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 502
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 503
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 504
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 505
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 506
mmcblk0: error 1 sending read/write command
end_request: I/O error, dev mmcblk0, sector 736
Tried with a 2gb SD card and a 512mb one, same effect. Couldn't find much on google other then how-to's that don't specifically note inability to write to cards, which makes me think someone has gotten write support working. If anyone has gotten this hardware to write to SD cards I'd like to know how you did it. Thanks for reading.my lspci
00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02)
00:01.0 PCI bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to AGP Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 83)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 03)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 03)
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]
02:02.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01)
02:04.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network Connection (rev 05)
02:06.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller
02:06.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller
02:06.3 Mass storage controller: Texas Instruments PCIxx21 Integrated FlashMedia Controller
my loaded modules
tifm_7xx1
tifm_sd
tifm_core
mmc_core
mmc_block
If I can mount the card writing to it works, but I have a strange problem here.
Sometimes when I insert a SD card udev creates /dev/mmcblk0 and I can't mount it.
And sometimes, with the same card, udev creates /dev/mmcblk0p1 and I CAN mount it.
I read that its handled like a hard-disk, but don't remember where and if my memories are correct. However...
mmcblk0 is the disk
mmcblk0p1 is the first partition
Anybody knows how to solve this udev problem?
Maybe you are looking for
-
New iPod nano chromatic crashes computer
I have an iMac version 10.4.11. My daughter just bought a new iPod nano chromatic and whenever we try to use it on that computer, it crashes and a window pops up demanding a mandatory restart. There was no way to even register the iPod and it never s
-
Hi, Whenvever I try to update apps on my new macbook pro 15" retina, a message appears saying my ID has been disabled and then another appears saying we could not complete your request with error message 18. I can however sign in to other things with
-
Capacity Planning Fields - CM01
Hi guys, I need help on getting some information from SAP. I have a request for a report that need the Availability Capacity for Machines. This information can be found in T-Code CM01. See below the result of the transaction: Week Requirements AvailC
-
SandBox Violation while invoking remoteObject on different war
Hi, I have two wars in my application say abc.war and xyz.war My abc.war contains the swf file and I am trying to invoke a method in xyz.war using RemoteObject. And while doing so I get Security sandbox violation. The context and domain of both are d
-
DYNPRO_ITAB_ERROR
Please assist SDCCN provides the error.