yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
It's just a matter of taking wlan.ko, wpa_supplicant.conf, etc. as Addisu, Newbie16, Vilord (and the list goes on) said. The build is really meant for a Dream phone which is why the build.prop came from JACxROM. Things got really bad until I swapped it out-- something wifi related I believe. Everything else about the build though, let Zenulator know. I'm not making re-releases of builds anymore. Please refer to the actual developers for their releases now. Thanks everyone that tested the builds.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] xxbabiboi228xx:
Just a quick question for anybody that know is the wifi file in the system.img file?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
Zenulator's latest build has wifi and Exchange support. It's the featured test. I lost my microSD adapter so I'm slowly FTP'ing it now. Has new features too. Just went up minutes ago.

http://code.google.com/p/vogue-hero/downloads/list
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] siulmagic:
will that build work on the kaiser or do we have to wait till they port it?

because i tried it and it just kept rebooting at the htc logo screen
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
Check his thread http://xdaforums.com/showthread.php?t=544906 for updates on that.

Anyone got any info on DMA so far? I'm not sure where to start so if it's in progress, please let me know how to help.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] addisu:
Wifi with dma for Kaiser

Hello,

I have posted a rootfs_wifi_dmatest.img file at http://drop.io/wifikaiser that has dma partially working. This should improve download speeds significantly ( > 10x) . Upload speeds are still around 80kbps for me on a 10Mbps ISP. The rootfs should be compatible with the newer builds (Don't forget to rename it to rootfs.img). I am using an Ion build from 08-08-2009.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] soulbandaid:
The link is dead. Something about not allowing direct linking on non converted files. I'd love to try it!

Edit: first link works, but direct does not. Thanks!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
I see.. I'm about to test the rootfs.img but it seems like you're implying I won't need the wlan.ko DMA test right? This is being hard coded on builds so if you're saying it can be symlinked to where "you people" are working and not system.img that would make things really easy for us. Right now, /system will override I believe for that so please let me know how to ensure it's being used correctly. And I thought the thread was getting updated...

soulbandaid he posted the link. He's talking about rootfs.img but I want to know about how it would work with /system/lib/modules/wlan.ko
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] addisu:
With the build I have, /system/lib/modules/wlan.ko is a symlink to /etc/wifi/wlan.ko in rootfs (/initetc/wifi/wlan.ko). I updated the rootfs wlan.ko so if you have an old system.img it might not work since the wlan.ko wouldn't be a symlink. The rootfs file has everything you need to test the wifi+dma.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
That's perfect. Can you then tell me how to do a hanging symlink for system.img? Do I "ln -s /etc/wifi/wlan.ko /system/bin/su" so it will line up at boot time or what? I've been waiting for that so thanks again for getting it done. Also, because I suck, can you tell me if it includes compcache or how I'd add it? I will honestly try to figure it out but if you had the info already it would help me out.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] addisu:
I don't quite understand the question. The system.img in the ion build of 08-08-09(and on onward I assume) has the symlink in it already. i.e. /system/lib/modules/wlan.ko -> /etc/wifi/wlan.ko. So to update the wlan.ko I updated the file /etc/wifi/wlan.ko. This is /initetc/wifi/wlan.ko in the rootfs.img file when you mount it. To modify stuff in rootfs.img on linux:

$ mkdir rootfs_mnt
$ sudo mount -o loop rootfs.img rootfs_mnt
$ cd rootfs_mnt
// edit stuff and when you are done
$ sudo umount rootfs_mnt
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
With Zen's builds either /lib/modules/wlan.ko already exists or the folder is missing. To get his to symlink properly, I just need to know if I can ln -s to the path that will exists at boot up even if it doesn't on my laptop when I affix the symlink. I saw that a lot of scripts link to busybox but those were within the same image whereas this crosses images so I just want a guarantee that it will use what you've done so we can update Hero users with DMA.

Also if you can tell me if the rootfs has compache in it. I missed the memo on adding it so I want to make sure an updated build will be correct for others.

Sorry if those are dumb questions, I just haven't done it the obligatory first time to get the steps down.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] addisu:
I understand now. Yes, you can symlink from system.img /lib/modules/wlan.ko to /etc/wifi/wlan.ko. It will be available by the time the wifi needs to load.

There is no compcache in the rootfs I put up, sorry.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
Great, will now need to find out how to add compcache but not on this thread. Thanks again, I was happy with wifi as it is but I said that about my 28k modem once upon a time too.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ibanezbass:
enatefox, why dont u jsut take the current compcache rootfs.img and add in the modified wlan.ko?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
I will probably do that but I'd like to know how the two work. Like if it really just is the wlan.ko file responsible or if there's other dependencies. I don't know how compcache was added so I don't want to put something out that I claim is both when I didn't take the time to understand it. Tomorrow sounds good to look it over, just thought I'd ask the questions now.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] ibanezbass:
I would also like to take a look at it, i'm just getting into programming and stuff but i like to fiddle, what program do u use to extract the .img files, bc i cant seem to find one.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Newbie16:
The img files contain data partitions and can be mounted on a linux system. You can then edit the contents of rootfs.img by simply mounting since its formatted with ext2, system.img uses cramfs which is readonly so you'll need to copy it to a new system.ext2 image which can be written to, after making changes you can pack it again as system.img or if you have the space on your sdcard you can use system.ext2
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
Yea, if you get to the point of wanting to mod images, I've posted the exact steps a dozen times and can send you links for each. Just checked and Vilord's got compcache and DMA for rootfs. Seems the newest broke wifi so it will be fixed soon.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] toasty_:
Is the source available or maybe a patch??? (or is the ti-kaiserwifi.zip updated?)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
It's up now. Try it out.

EDIT: whoops. The latest is on Vogue-Android:

http://code.google.com/p/vogue-android/downloads/list?can=2&q=&sort=-uploaded&colspec=Type%20Filename%20Summary%20Uploaded%20Size%20DownloadCount

Top post with rootfs.img (direct link)

Might be the same file, but stick with the updated ones on Google Code
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] toasty_:
Thx!!! I'll try...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] addisu:
Here is the file that needs to be modified. Its also up on drop.io.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
Addisu, can you confirm if that's the latest zImage on Vogue-Android? I need the newest rootfs.img with that right? Or is this a hack in addition to using it? Sorry if it sounds dumb but just wanted to be sure I got it right. Thanks
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] addisu:
The latest zImage works. No change in the kernel is needed. Any of the previously zImages with working wifi should work with the new wifi+dma.

Can anyone who has tested the wifi confirm if it works at all, and is stable, fast?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
cd ~/android/build/

sudo rm system/lib/modules/wlan.ko

sudo ln -s /lib/modules/wlan.ko system/lib/modules/wlan.ko

sudo mkfs.cramfs system test-system.img

....

Unable to start wifi.. Using rootfs-2009-08-16.zip with DMA and zImage-14-08-09a. No go.

Can I just hardlink wlan.ko from rootfs.img into system.img without softlinking?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] natalic:
Just tried using all latest files from Vogue Android and had issues...Just won't start Wifi. Any ideas?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] natalic:
For some reason, I'm unable to pick up any WiFi APs...It enables but nothing is found. Is this a known issue? I'm using the 08-08 build (using the new rootfs)
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
I see that people with newer zImages can't scan for APs. I'm using an older one and it's worked perfectly. Even prompts at setup to connect.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pmos69:
try this combination:

http://xdaforums.com/showthread.php?p=4347295#post4347295

will give you working wifi on kaiser.

you can also try one of the newer rootfs images with compcache+swapfile, but they're pretty new and I'm having issues with them. You'll probably be better of mounting the swapfile after boot at this time... or wait a little bit.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] natalic:
I actually would like your help. I need help getting Hero running...It doesn't load @ all. Perhaps you can msg me on IM for my AIm/Yahoo?

Thanks. I will lower my zimage. I figured it was the kernel.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pmos69:
sure. just sent you a pm.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] addisu:
sudo rm system/lib/modules/wlan.ko
sudo ln -s /etc/wifi/wlan.ko system/lib/modules/wlan.ko
sudo mkfs.cramfs system test-system.img

/etc/wifi/wlan.ko is the updated file.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
I see... well I'll just go ahead and test that now then. Thanks addisu
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] natalic:
I understand everything but the latest line

Remove Wlan.ko

Symlink ...

....?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
it's:

1.) remove wlan.ko

2.) symlink

3.) ???

4.) profit!!!!

addisu, can you tell me how to confirm it's utilizing DMA? I took an existing setup and swapped for the symlink. I reboot and it's connected automatically. I don't want to just "feel like" it's faster so I'm hoping dmesg or similar can tell me. Thanks. If I'm using it and don't realize then it's spot on.

I had issues with HTC's mail widget sending mail (receiving was okay) then after switching to your DMA, it went from my outbox immediately.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] chrisman567:
get natural bootloader...**** haret

we got wifi working for the kaiser by offering people money to do it...so lets do it for a natural bootloader

lol i want to use android as my primary thing hahah
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
If you want a natural bootloader then go for it. I will still be in god-tier because I'll be able to dual-boot my phone. You'd be stuck with the build you are running. If that has a flaw that prevents a requirement to reflash you are screwed. Don't think it's too unlikely.. With a naked ROM like I've got and Haret in the Startup folder it's fast enough. I rarely reboot anyways.

Addisu, I'm assuming DMA is working unless I hear from you on how to confirm it. HTC mail is now working-- you rock.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pmos69:
what image did you modify?

can you make it available?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] addisu:
To check if dma is working, compare your download speed in winmo to android. You can use sites like dslreports.com or download an app from the market. When using dma, it should be 10x or more faster than what we had before.

There is actually another update posted a few hours ago. Thanks to dzo the original ti driver without any of my modifications works even better now.

Here is the original wlan.ko
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pmcnano:
I still dont have wifi after this new updates, it connects but..no data xfered. I mean I open a page and it just doesnt open. Should I be using calibration file yet? Or I should delete it now??? I dont know whats the problem now XD before it worked, slow but it worked...:P
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
The new DMA driver is making my battery extremely hot. Connected instantly (I kept my data.img so it had the AP saved) and is working very well. In Hero at least, I can't turn off wifi-- the process will crash and the toggle widget, it does nothing. I'm reverting back for now.

what can I look at to try to diagnose the suspend issue and troubleshoot the wifi settings?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] toasty_:
I can confirm that, wifi is working fast and stable and seems to be fully useable.

But I have recognized, if I connect to my router with WEP wifi stops after a few seconds. If I use WPA it works fine(but my repeater didn't work with this). But this also happens if I use driver without DMA... So the problem is maybe my router

Btw. nice progress
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] mcfarlan:
pmos, noob question. In the link it says to include Zen-Superhero with wifi and Superhero. Aren't they both system images and one will overwrite the other?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
The one with wifi is just the system.img file.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pmos69:
Yes, that's the point. Overwrite everything in Superhero with the other files.

or check this: http://xdaforums.com/showpost.php?p=4353121&postcount=7457

has some updates
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] natalic:
http://scarlet-arrow.com/builds/Hero/Natalic_Hero_08_18_09_DMAWIFI.rar

This is a Hero build with all the correct settings. Works out of the box, simply copy to your SD card.

Has Compcache and DMA wifi!
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
To which I'd ask you about the power collapse issue and battery temperature with DMA enabled. The "get it while it's hot" part is no joke
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] natalic:
Yeah, the battery does feel a bit hot...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
At least on Hero I can't turn off wifi. It's on at boot and there it remains. The settings for it crashes the process if I try to touch it and toggle widgets do nothing. In fact, I have a fast action replay of my face at that realization: http://www.youtube.com/watch?v=-5eA1jlQMrI. Classic
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] MiZi666:
i think the panel.type "2" makes the problem.. try to set it to 0 or 1.. maybe it helps..

my battery doesn't get warm... running natalic's rar pack and i have wifi running.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] natalic:
Happy to hear my package worked for you:).
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] magicozero:
natalik tanks for your pack is pefect for me i have change only system.img whith jackxrom.img because i need dialer move with dpad.

(wifi ok - gps ok - speedly change menu - call ok - sms ok ) if possible change dialer in your system?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] momo254:
can u link to the jackxrom img file? I tried nataliks bundle but the sms bug in it :(
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] pmos69:
actually, it's JACxROM , not jack...

http://xdaforums.com/showthread.php?t=543621

http://www.youtube.com/watch?v=Q0yqpjGClTU
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] enatefox:
yeah, JACxROM is nice but since we got compcache and swap together, I'm a Hero guy lately.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] magicozero:
http://code.google.com/p/vogue-hero/downloads/detail?name=xROM-zen-build-080709.zip
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] momo254:
my bad lol
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] natalic:
As far as the new rootfs and my package, simply copy the new rootfs to the sd card. It will work right away. I simply turn the wifi off using a widget. I will post the update on my site soon.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] toasty_:
Ok something happened, 'wlan_loader' is now hanging while loading firmware... Maybe a step in the right direction or just a step back.

it also hangs with the eeprom file from G1... so I don't think that the file format is wrong (wlan_loader isn't in a loop waiting for an end-char or sth.)

the last line from logcat is:

logcat:
D/wlan_loader( 448): Configuring adapter

tiwlan_loader.c:
do { /* Need to wait till driver will be created in sdio_probe() */
print_debug("Configuring adapter\n");
[B]rc = IPC_DeviceIoControl(adapter_name, TIWLN_SET_INIT_INFO, init_info, req_size, NULL, 0, NULL);[/B]
...

it depends on 'init_info' or 'req_size', because in eeprom-less mode this funktion was succsesful, and only these two vars are changed... I'll put some extra "print_debug" in wlan_loader, maybe I can find sth...
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Newbie16:
Mine is doing the exact same thing, mine is hanging too, the whole thing locks up and has to be reset with the stylus, this only started happening recently. I am using the rom i cut out

drop by #vogue-android on freenode, it might be faster
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Newbie16:
What code did you use? i used this:

do { /* Need to wait till driver will be created in sdio_probe() */
print_debug("Configuring adapter\n");
rc = IPC_DeviceIoControl(adapter_name, TIWLN_SET_INIT_INFO, init_info, req_size, NULL, 0, NULL);
[B]
print_debug("Adapter Name = %d\n", adapter_name);
print_debug("Init info = %d\n", init_info);
print_debug("Req Size = %d\n", req_size);
[/B]
print_debug("Adapter configuration rc = %d\n", rc);
if( rc != 0 ) {
if( count > 4 ) {
break;
}
count++;
sleep(1);
}
} while( rc != 0 );

/* Send configMge start command as the cli is started */
if( rc == 0 ) {
tiUINT32 tmpData = 1
print_debug("Starting configMge\n");

[B] print_debug("Adapter Name = %d\n", adapter_name);
print_debug("TmpData = %d\n", &tmpData);
print_debug("Sizeof TIUINT32 = %d\n", sizeof(tiUINT32));[/B]

rc = IPC_DeviceIoControl(adapter_name, TIWLN_DRIVER_STATUS_SET, &tmpData, sizeof(tiUINT32), NULL, 0, NULL);
print_debug("ConfigMge start rc = %d\n", rc);
}

This is what i got out:

I'll add more stuff to see how the components of req_size are calculated
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Newbie16:
Latest:

Ignore the TmpData value, now i'll investigate IPC_DeviceIoControl.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] toasty_:
yes, 'tmpData' is set in the next block on starting and configuring adapter, and I think the first 'IPC_DeviceIoControl(...)' for configuring adapter fails... My phone hangs at this point.

Btw. how did you manage to get this function running with EEPROM i still stuck in the first IPC instruction.

(and tmpData isn't wrong, its unsigned so the negation is because you took '%d' in printf. Instead of %d you can use %u)

My extracted an cuted eeprom has 752 byte (begining from the signature we found) - the same size as the G1 eeprom but maybe the kaiser wlan-eeprom has more or less bytes...?

And I'm also wondering how the data get into /proc/calibration on G1 - I think this file is built by the kernle on booting (as the complete procfs).

No I havn't built 'wlan_laoder' yet because it takes so much time to build the complete android source - or is there an easy way to do this (sth. like make 'wlan_laoder')

it would maybe interesting how the files are stored in init_info:

maybe this code can be placed somewhere in tiwlan_loader.c
print_debug("eeprom length = %d\n", init_info->eeprom_image_length);
print_debug("fw lenght = %d\n", init_info->firmware_image_length);
print_debug("init file length = %d\n", init_info->init_file_length);

and than we could maybe output "init_info->data" in this file should be following bytes in this order:

data[...] = eeprom + fw + init-file

I made an output to /sdcard/outhext.txt

FILE *fout = NULL;
if((fout = fopen("/sdcard/outhex.txt", "w")) != NULL)
{
do {
fprintf(fout, "%02x", init_info->data[j]);
j++;
} while (j<k1);
}
if( fout )
fclose(fout);

I have nearly the same outputs as you:

without eeprom:
D/wlan_loader( 526): opening eeprom: /proc/calibration
D/wlan_loader( 526): opening eeprom succsesful, length= 0
D/wlan_loader( 526): loading firmware file /sdcard/wlan/Fw1251r1c.bin
D/wlan_loader( 526): opening init file /sdcard/wlan/tiwlan.ini
D/wlan_loader( 526): firmware length = 185388
D/wlan_loader( 526): eeprom length = 0
D/wlan_loader( 526): init-file length = 8139
D/wlan_loader( 526): Data-Offset = 12
D/wlan_loader( 526): init_info->data[0...193527]
D/wlan_loader( 526):
D/wlan_loader( 526): Configuring adapter
D/wlan_loader( 526): Adapter configuration rc = 0
D/wlan_loader( 526): Starting configMge
D/wlan_loader( 526): ConfigMge start rc = 0
D/wlan_loader( 526): Driver configured
D/wlan_loader( 526): Firmware loaded and running OK
D/wlan_loader( 526): Set property wlan.driver.status = ok - Fail

with eeprom:
D/wlan_loader( 526): opening eeprom: /sdcard/wlan/calibration
D/wlan_loader( 526): opening eeprom succsesful, length= 752
D/wlan_loader( 526): loading firmware file /sdcard/wlan/Fw1251r1c.bin
D/wlan_loader( 526): opening init file /sdcard/wlan/tiwlan.ini
D/wlan_loader( 526): firmware length = 185388
D/wlan_loader( 526): eeprom length = 752
D/wlan_loader( 526): init-file length = 8139
D/wlan_loader( 526): Data-Offset = 12
D/wlan_loader( 526): init_info->data[0...194279]
D/wlan_loader( 526):
D/wlan_loader( 526): Configuring adapter
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Newbie16:
The first time you build the source it does take time, but after the first build it builds just the modified components, but i do a make clean in sta_dk_4_0_4_32 so everything gets rebuilt including the kernel module
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Newbie16:
Very interesting addisu, btw how did you set to get the extra output and are you using the same firmware?, i managed to get my driver to go nuts in yet another new way.

I also found that within my romdump i have two identical copies of the rom, anyone else find two coppies? one at 0x2500040 and one at 0x2500840.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] toasty_:
yes I've also 2 - thought i've posted it yesterday...

@addisu:

am I right, these outputs are from 'wlan.ko' when the first 'IPC_DeviceIoControl' function is called?

Does anybody know, what function is the reason for freezing?
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] addisu:
The outputs I posted before are indeed from the first IPC_DeviceIoControl call. The freezing is due to a call to sdio_memcpy_fromio in tnetw_sdio.c file in SDIO_SyncRead function.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Newbie16:
Well if this code is commented out it shows the ok - OK, so the error is probably in here:

if (configMgr_start(drv->adapter.CoreHalCtx) != OK)
{
print_err("TIWLAN: Failed to start config manager\n");
return -EINVAL;
}
drv->started = 1;

I think this is where the error occurs
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] Newbie16:
Ok so this is what is happening:

status = smeSm_start(pConfigManager->hSmeSm);

So does this mean that this isn't working?