lsmod would list the loaded drivers, it would confirm the driver is loaded properly.

Here is dmesg from good unit from the summit

http://pastebin.ca/1610167

do we know the name of the driver?

Anyone have any clues to this MAJOR problem yet.

The problem is that even if the hardware was faulty - the driver could still load. It really would help to see if the serials on the units were part of a batch.

Nope, sorry, I can't seem to figure out the audio driver name.

.....


Well, if you would see that the driver doesn't load then you would be able to draw a conclusion... if the driver loads then I agree, no conclusion can be drawn.

Thanks for starting this thread - it's something that DDP orderers will have to remember checking quickly (due to the one-week return policy).

Yes.
It's highly unlikely that charging like described above will have anything to do with the failed mic. But as you won't know the state of the battery when you receive the N900 you should start with charging it. If you're impatient you could power it up after half an hour and continue charging, but you should avoid powering it on first thing. If you're unlucky you may suddenly have a completely empty battery and then you will not be able to charge the device - it needs to be able to boot to its "charge mode" because the charging is managed by software. And it's always powered through the battery, even when plugged in. A dead battery is a catch-22.

And to the other poster: It's very bad for the battery to do a deep discharge. If it needs to be charged often, charge it often. Every accidental discharge-till-it-turns-off will reduce the capacity and lifetime of the battery. This is how it is with lithium-ion and lithium-polymer batteries.

To see the audio driver, couldn't you just do:

lsmod | grep snd

and

cat /proc/asound/cards

?

nuknuk there are two tracks here

1. it would be useful to see your serial numbers
2. we trying to see if your sound driver is loading to isolate if its a hardware or software problem. Would you know how to get into the terminal ? and run some of the proposed commands :-

Cat /proc/asound/devices

I seriously don't think this is software. We'll need someone from nokia to confirm, but i think the headset mic and the embedded one use the same hardware from some point on, which implies the same software too. Are there separate controls for headset and embedded mic ?
If they do use the same path, it becomes obvious that it's just faulty hardware
EDIT: could people please start posting serial numbers?