Re: Re (6): xorg-server failing on IBM NetVista with Intel 82815 video
On Wed, 26 May 2010 15:22:31 -0400 (EDT), Peter Easthope wrote:
>
> Correction:
> "# ~/.xinitrc
> exec openbox" lets X stay running with the refresh
> rate warning from the monitor.
Now that you have a scenario that lets X stay running,
change your driver back to intel and see if it stays running.
>
> In Fall 2009 upgraded Lenny to Squeeze using aptitude.
> Squeeze had no serious problems for a few months.
> Then grub-pc failed. A week or two later X failed.
It's getting trickier and trickier to correctly do an
upgrade from one release to the next. You can't just
update your /etc/apt/sources.list file and run
aptitude update
aptitude full-upgrade
I tried that and got an unbootable system. You need to
follow the instructions in the release notes carefully
for an upgrade. And usually, the instructions in the
release notes are not accurate until *after* the release
becomes the stable release. If you have /home as
a separate partition, which I strongly recommend, then
I would suggest reinstalling squeeze from scratch,
formatting the / partition (but not /home). My personal
favorite is the netboot mini.iso image, burned to a CD.
For squeeze I would probably use the latest "daily build"
installer for your architecture (i386, amd64, etc.)
At least as of this moment, the Debian installer lets
you select lilo as an alternate boot loader during
installation.
>> What window manager do you intend to use?
>
> LXDE. It works in Squeeze on a Toshiba 4000CDS laptop
> and in Lenny on a generic pc.
There is a file that controls what applications are launched
when you start X. The last one listed is your window manager.
Years ago it was called .xsession. Maybe now its called
something else, like maybe .xinitrc? Compare these files
between a machine that's working and one that's not. It should
give you some clues.
>> ... identify your monitor by manufacturer and model
>> number. If you have the date of manufacture ...
>
> NEC MultiSync FE700, 2001 January.
That's new enough to support DDC2/EDID. Manual configuration
should not be necessary.
>> I assume that you're using a standard 15-pin
>> analog VGA connector on the back of your computer and a standard
>> analog monitor.
>
> Definitely and the Intel video chip is on the
> mainboard of the NetVista. The hardware couldn't
> be more ordinary, although it's old.
Good.
>> Also, please post the /etc/X11/xorg.conf file
>
> # dalton:/etc/X11/xorg.conf created 2009-10-20.
>
> Section "Device"
> # Option "UseBIOS" "off"
> Identifier "Configured Video Device"
> Driver "vesa"
> EndSection
>
> Section "Monitor"
> Identifier "Configured Monitor"
> EndSection
>
> Section "Screen"
> Identifier "Default Screen"
> Device "Configured Video Device"
> Monitor "Configured Monitor"
> DefaultDepth 16
> Subsection "Display"
>
> Depth 16
> Modes "1024x768" "800x600" "640x480"
> EndSubSection
> EndSection
>
> Section "ServerLayout"
> Identifier "Default Layout"
> Screen "Default Screen"
> EndSection
>
> #Section "ServerFlags"
> # Option "AutoEnableDevices" "true"
> #EndSection
As I said before, change back to intel, now that you have something
that stays running. Based on the output of /var/log/Xorg.0.log,
we may need to change the Modes line. It used to be that the
default modelines were called "1024x768", "800x600", etc. But
based on the /var/log/Xorg.0.log file, the names may have changed
slightly. But I want to wait and see what the output looks like
with the intel driver. But one thing at a time.
Please consider a reinstall first. Who knows how many other hidden
problems are lurking in your system.
--
.''`. Stephen Powell
: :' :
`. `'`
`-
Reply to: