While trying to boot the .37 kernel I ran into an interesting problem.
The .37 kernel seems to detect the read-only switch on the SD card slot
now,
which the old kernel ignored and just assumed it to always be
write-enabled.
This wouldn't be much of a problem, but on my pandora it seems to think
it's
always set to read-only, which causes a kernel panic when booting the
kernel
rw. (works when giving ro as a bootarg though) This would probably mean the sd card itself can't be written to once the kernel boots, which would mean pnd's wouldn't be able to run.
This far my pandora seems to be the only one to have these problems (as usual :) )
So I'd like to find out if it's just a case of me getting another broken
pandora,
or that it's a problem with a small number of pandoras, or even a whole
batch
that's somehow using other hardware.
<snip>
As I mentioned on IRC, I don't see this problem on my devices but assuming it is an issue I'll look into what we can do about disabling the write protect detection in the kernel for the images as it is going to cause all sorts of hard to track issues if this is a problem with more than one or two isolated devices.
If more people can run aTc's test I would appreciate it. It's a lot easier than putting a full image on an SD card just to prove a point ;).
Regards,
John