Hi Again. Switching to fbdeb made thing even worse, there was no graphics at all.. I had to switch to vesa, and disable KMS. But now I have only 640x480 graphics, which cause me to miss the crashes I had before with the regular intel driver.
After more Googling, I have found this page: https://wiki.ubuntu.com/X/Bugs/Lucidi8xxFreezes What do you think about the work arounds suggested there? I'm a bit afraid of trying those, because I read somewhere in the FAQ that taking solutions from other distros to Debian might be problematic; so I wanted to verify that these are safe to try. Thanks, and good night. On Sun, Feb 20, 2011 at 5:41 PM, katif software <katifs...@gmail.com> wrote: > - Sorry for my ignorance, but what do you mean by "an upstram issue"? > - Regrading the installer: > Well, I think that it's quite an important issue. When the avarage > end-user will encounter a need to reboot his computer 5 times a day, he will > just say that Linux is even worse than Windows, and will get back to > Microsoft ... > I think that we have to think how can we help him. > > If adding this ability to the installer is problematic, there must be some > other creative solution. > Maybe upon activation of his new environment, the driver will recognize > that it's running on un-supported chipset, and will pop-up some window, > suggesting the user to switch to 'fbdev', with explanation that ordinary > people can understand (or maybe even suggest to do it automatically). > > Thanks again for all the help, > Zvika > > > On Sun, Feb 20, 2011 at 4:44 PM, Cyril Brulebois <k...@debian.org> wrote: > >> Hi. >> >> katif software <katifs...@gmail.com> (20/02/2011): >> > 1. What are the disavantages of using a generic driver instead of >> > this one? >> >> You may lack features like acceleration etc. But you gain stability. >> >> > 2. Is this problem related to using Debian, or is it for any Linux >> > distro I will use? >> >> That's an upstream issue. >> >> > 3. Maybe the installer program should be aware of the i8xx compatibility >> > problem, and not install this driver on the first place? >> >> We made several attempts at fixing it. Introducing chipset detection >> late in the release cycle could have lead to more issues. >> >> > > How can I know for sure that I have i8xx card? >> >> From the output of the bug script (included in your report), lspci >> returned: >> | 00:02.0 VGA compatible controller: Intel Corporation >> 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03) >> >> > > If I do have an i8xx card - I understood from the FAQ you linked >> > > that I should change my video driver to vesa or fbdev. Which is >> > > prefered? How can I make this change? >> >> I think the FAQ tells you exactly how to do it? IIRC, vesa only does >> 4/3 resolutions. fbdev uses the framebuffer. I'd say fbdev (spares you >> a reboot to disable KMS), and vesa if it doesn't work well. >> >> KiBi. >> >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.10 (GNU/Linux) >> >> iEYEARECAAYFAk1hKLUACgkQeGfVPHR5Nd1t2wCgjv/G/NPVPjE5X1YA0YzFmIIO >> u/UAoJZ20FvWxjvj+iTRcf2luC41XelY >> =hAfd >> -----END PGP SIGNATURE----- >> >> >
