[Samsung Galaxy SL i9003] loSconosciuto:
Why would you think ganesh made a different normalboot.img for each firmware? hint: it's not universal.

If you try to load the modules I gave you with it, you'll get the vermagic error hillbeast was talking about. I asked you your dmesg also to check this and they are ok. I don't know why you still got the errors due to the wrong loading order, maybe you still have the app installed, but I checked your dmesg output and it seems that the modules are loaded. You even checked it with lsmod.

Here the analysis:

<4>[ 67.790344] usb_storage: Unknown symbol usb_alloc_urb (err 0)
<4>[ 67.790802] usb_storage: Unknown symbol usb_free_urb (err 0)
<4>[ 67.791320] usb_storage: Unknown symbol usb_alloc_coherent (err 0)
<4>[ 67.791839] usb_storage: Unknown symbol usb_register_driver (err 0)
<4>[ 67.792205] usb_storage: Unknown symbol usb_sg_init (err 0)
<4>[ 67.792785] usb_storage: Unknown symbol usb_sg_cancel (err 0)
<4>[ 67.793121] usb_storage: Unknown symbol usb_reset_device (err 0)
<4>[ 67.793395] usb_storage: Unknown symbol usb_submit_urb (err 0)
<4>[ 67.794006] usb_storage: Unknown symbol usb_free_coherent (err 0)
<4>[ 67.794403] usb_storage: Unknown symbol usb_control_msg (err 0)
<4>[ 67.794860] usb_storage: Unknown symbol usb_deregister (err 0)
<4>[ 67.795104] usb_storage: Unknown symbol usb_lock_device_for_reset (err 0)
<4>[ 67.795471] usb_storage: Unknown symbol usb_unlink_urb (err 0)
<4>[ 67.795898] usb_storage: Unknown symbol usb_kill_urb (err 0)
<4>[ 67.796234] usb_storage: Unknown symbol usb_reset_endpoint (err 0)
<4>[ 67.796813] usb_storage: Unknown symbol usb_sg_wait (err 0)
<6>[ 67.905242] NTFS driver 2.1.29 [Flags: R/O MODULE].

Did you load them as I told you? Do you still have the app installed to autoload the modules? I'm asking because you are trying to load usb-storage.ko too soon, ntfs.ko should be loaded after the other modules and it should be R/W.

<6>[ 69.006347] usbcore: registered new interface driver usbfs
<6>[ 69.026519] usbcore: registered new interface driver hub
<6>[ 69.035064] usbcore: registered new device driver usb
<6>[ 69.300994] usbcore: registered new interface driver usbhid
<6>[ 69.301055] usbhid: USB HID core driver
...
<6>[ 191.482330] usbcore: registered new interface driver usb-storage
<6>[ 191.482360] USB Mass Storage support registered.

That's good.

EDIT:

<2>[ 67.905761] NTFS: Failed to create ntfs_index_ctx_cache!
<2>[ 67.905822] NTFS: Aborting NTFS filesystem driver registration...
<6>[ 68.454254] fuse init (API version 7.14)

NTFS is not working, but fuse works. Make sure your USB drive is not NTFS formatted, but I don't think this is the problem, because it should work with the SD card reader, usually SD cards are not NTFS formatted.

PS: you should ask the owner if his SD card reader is a USB 1.0 or 1.1 or 2.0. But probably this has nothing to do with this, it was just the first thing that came to my mind that could explain this thing.

@hillbeast

That's weird, I downloaded the modules and checked them again:

strings * -f | grep vermagic
btwilink.ko: vermagic=2.6.35.7-CL709629 preempt mod_unload ARMv7
fuse.ko: vermagic=2.6.35.7-CL709629 preempt mod_unload ARMv7
gspca_main.ko: vermagic=2.6.35.7-CL709629 preempt mod_unload ARMv7
ntfs.ko: vermagic=2.6.35.7-CL709629 preempt mod_unload ARMv7
scsi_wait_scan.ko: vermagic=2.6.35.7-CL709629 preempt mod_unload ARMv7
st_drv.ko: vermagic=2.6.35.7-CL709629 preempt mod_unload ARMv7
usbcore.ko: vermagic=2.6.35.7-CL709629 preempt mod_unload ARMv7
usbhid.ko: vermagic=2.6.35.7-CL709629 preempt mod_unload ARMv7
usbmon.ko: vermagic=2.6.35.7-CL709629 preempt mod_unload ARMv7
usb-storage.ko: vermagic=2.6.35.7-CL709629 preempt mod_unload ARMv7

You are using XKPQ, so they should work.