Virus on pdaXrom ?

[sigmaX]

A few minutes ago, I was talking thru phone with a client, and I suddenly noticed that my SL-C860 screen was turning WHITE, from UP to DOWN, like a curtain, but not smooth: It was like someone was pressing "Enter" in a shell, painting with white each line, one text line per second at a time.

This made my matchbox interface gradually dissapear, until even the taskbar went away.

The Wireless network also got stuck ... and I had to unplug the wifi Compact flash, press "HOME" and then I regained my beloved matchbox interface.

Memory issues ? virus ?  anyone had a similar experience ?

I recall now that I found a "white Screen" more than once, after long time inactivity ... So this might have been going on for a while !

Regards,

Enrique.

[iamasmith]

I get something similar using the Cacko ROM from time to time, I get a black screen initially with some large text chopped on interlaced scanlines saying something about a modprobe command then the screen goes white for a couple of minutes and finally it goes back to the Qtopia screen.

I think it may have something to do with when the jffs2 defrag kicks in, normally on stock Qtopia ROMs you get a message about this, I think this may cause a problem with the w100fb (ATI Imageon Frame Buffer) patch that's included in the Cacko ROM, not sure if this patch is in the PDAXROM Kernel though.

So PDAXROM guys, how do you deal with jffs2 defrag, actually I don't even know how it's kicked off, does the file system kick it off in some wierd and wonderful way or is it monitored for by the ROM and then started by Qtopia/PDAXROM

This might be what's causing it, wouldn't know how to fix it though.

[ikm]

A few minutes ago, I was talking thru phone with a client, and I suddenly noticed that my SL-C860 screen was turning WHITE, from UP to DOWN, like a curtain, but not smooth: It was like someone was pressing "Enter" in a shell, painting with white each line, one text line per second at a time.

If that happens once more, be sure to run 'dmesg' right after it happened and check the last lines of the output. It might help understanding the problem.