Juha Jäykkä <juhaj@iki.fi> (31/03/2010): > Last I checked vesa cannot even give me a root window. Probably has > something to do with the 1440x900 size of the LCD. Might be, yeah. > > > but mistakenly upgraded later and now I do not have 2.9.0 anywhere > > Sounds like a kernel issue then? I hope you'll be able to get some > > traces at some point. :) > > I would have thought changing intel driver and getting a problem, > then changing back to the original and getting rid of it, would > indicate intel driver problem, not kernel. =) (That is, the > xserver-xorg-video-intel incarnation of the driver, not drm.ko or > i915.ko.) Oops, read too quickly, sorry. You can fetch older versions from http://snapshot-dev.debian.org/ (although not official, and having changed names several times lately, should help you get what you need.) > > > I could give a try to 2:2.10.903-1 from experimental, though... > > Yes please; it'd be trivial to identify the fix, should it run fine > > I will wait for the next freeze: that and the new kernel are > waiting. Should not take long. =( > > > I do not see it mentioned in 2.6.32-9 or 2.6.32-10 changelog entries > > for linux-2.6, so probably not in 2.6.32-4-$arch kernels. > > =( You probably want to open a bug against linux-2.6 in Debian to make sure the bugfix flows in for squeeze at some point. > > X crashing is no data loss. Data loss means you lost data you > > wrote. Crashing X means you didn't save soon enough. (See > > FS-related bugs, those are usually data loss. Or broken DB > > writes.) > > Bash histories will get lost. Bash's fault. > Likewise the OpenDX view angles. The latter could probably be saved > by vigorous finding of "save program settings as" from "file" menu, > selecting a file and clicking "ok", but that would be extremely > annoying and slow: some of the crashes have happened while rotating > an "object", so there is not much choice of saving while "going > around the corners" of something interactively. If you get what I > mean. Again, I know it's annoying, but still, you didn't save anything, it's not supposed to be saved, it's no *data* loss. Anyway, probably I should concentrate on reading you properly (see mistake above). > But in the sense of data written to disc being lost, I did lose my > kmail settings last time. They certainly were on disc, which is > proven by the fact that I restored them from backups successfully. I > cannot tell what caused this, though: Alt-SysRq-U, Alt-SysRq-S and > Alt-SysRq-B is usually quite safe way of rebooting (especially when > nothing else works except that and tearing away the battery). Is it > data loss yet? I doubt the existence of backup and successful > restore disqualifies a data loss. =) Sure. But I'm quite unsure how X is responsible for that. Unless the crash kills some bits from your disk? Anyway, w/o traces, that's going to be hard to figure out. Mraw, KiBi.
Attachment:
signature.asc
Description: Digital signature