QUOTE(datathief @ Aug 8 2008, 11:46 AM)

Do you have a copy of the working bluez-utils deb? I could change its version number so it gets installed instead of the broken one, and host it in my repository, while we figure out what's wrong.
Well, this was my first line of thinking. However, maybe it's induced by other factors, like other packages, because:
From a working rootfs backup where I have bluez-utils installed, I tried to manually install them in your clean rootfs - don't have the package, but first installed all the dependencies, then copied all the bluez-utils files in their place, ran the preinst script, then ran the postinst script, and it fails in the same way...
Like I said, can't catch the errors, but right after hcid initialization I think, a slew or rfcomm or what have you associated errors fly by and that's it, the machine is stuck.
So, since another user has the same issues, it's not motherboard failure related I assume.
Do you have an idea what could be behind this SD I/O read/write problems of mine? It's driving me nuts, I can't use Linux on the Universal now...
Thought it was machine hardware generated, since even the Windows Mobile couldn't access the card, which has the first partition as fat32, which they could before, though the card was readable fine on a PC both under GNU/Linux and under XP. I used some tool though under XP that is supposed to format the card exactly to SD guideline specifications and now the Windows Mobile reads the card.
So should I maybe try just to keep it fat32 formatted and put the Debian into a file and run it off of it, instead of creating an ext2 partition? Would this be beneficial? I'm just curious why this now when for a couple of months didn't have these issues at all...