You are not logged in.
solved: post #5. ![]()
As the title states; whenever I mount my digital camera's sd card the pictures look messed up. An example of how a picture is "messed up" is that the image is in blocks of rearranged portions of the original picture (sort of like a jigsaw puzzle in the wrong order). I use xorg18 repo's xorg-server (but I also used to use xorg-server-udev from the AUR and it did the same thing) and have udev 151-3 (I don't use/have HAL). I'm not much on multimedia and imagery so I'm not sure what other information to give. I just insert the sd card from my camera and mount it. It mounts without any errors and I go to the folder I mounted it at and view the pictures which is when I see they're always messed up looking. I can mount the same card on a "out of the box" Linux Mint computer and they show up fine so I'm guessing I'm just missing a udev rule or perhaps I simply need HAL, I don't know.
Any ideas? Thanks for reading
Last edited by milomouse (2010-06-09 19:10:48)
Offline
Are the images messed up (ie., if you copy them to your hard drive are they corrupted) or do they just appear that way in the folder preview?
Offline
It would mess up when I copy them to my hard-drive. When I preview them in an image program (I don't have a file browser) they appear messed up as well. I should rephrase my first statement and instead of saying "always" I should say sometimes, because it will mess up <most> of the time but every now and then they appear properly. An example is that they weren't working this morning before I posted this thread but after I got a reply this evening I tried it again and they appear fine. I'm not sure if it has anything to do with the kernel I'm using because [now that I'm thinking about it] I'm using 2.6.34 right now and it's working whereas most of my previous experiences I booted into 2.6.32. Perhaps it's a filesystem module or other that I didn't select before in the kernel config or a bug fix. Hmm. I'm sorry but I'll wait a little while (perhaps tomorrow morning) and try it again to see if I can replicate the results and show a picture of the messed up image (although I'm hoping I unwittingly fixed it). Thanks for the reply.. got me thinking about the chain of events.
Offline
I wouldn't rule out a corrupted SD card either (it might be worth backing up everything if you do catch it when it is behaving nicely)...
Good luck!
Offline
Well, this is kind of embarrassing but it continuously works now whereas it almost never worked with my pre-2.6.34 kernels. I've had this problem for about 2 years now and viola!; it's automagically fixed as soon as I ask about it. Oh well.
Thanks for your ideas jasonwryan, I'll go ahead and mark this solved as I cannot replicate it anymore.
Offline