Re: dist-upgrade (potato->woody): how to get X back up?
On Fri, Dec 06, 2002 at 08:09:31AM -0600, will trillich wrote:
> On Thu, Dec 05, 2002 at 10:31:45PM -0800, nate wrote:
> > will trillich said:
> > > attached is the /var/log/XFree86.0.log file (sorry for the size)... hope
> > > it sheds some light on this. i'd love to get X working
> > > again. (why was it so easy in potato? was i just lucky?)
> > sounds to me like /dev/mouse doesn't point to your mouse device. this
> > is a very common problem when running X -configure
> > if your mouse is PS/2 do:
> > cd /dev
> > ln -s psaux mouse
> > if it's something else..well then you may need another driver(s) for
> > USB or something before starting X, I think the default usb mouse
> > device in debian 3.0 is /dev/input/mice or something
> it's an elder box -- the mouse is a 9-pin, 2-row arrangement
> (db-9 i believe) which apparently indicates a serial device?
> gpm works fine in console mode... is there a way to funnel the
> gpmdata thru to X?
Set the repeater type to "raw" in gpm.conf and set the mouse to
dev/gpmdata for X.
> and when i do the
> XFree86 -xf86config /root/XF86Config.new
> i do get the boilerplate bitmap with a centered (immobile)
> pointer; but when i try startx (using the above config as
> /etc/X11/XF86Config) i get only
> (II) Module mouse: vendor="The XFree86 Project"
> compiled for 184.108.40.206, module version = 1.0.0
> (II) MGA: driver for Matrox chipsets: mga2064w, mga1064sg, mga2164w,
> mga2164w AGP, mgag100, mgag100 PCI, mgag200, mgag200 PCI, mgag400,
> (--) Assigning device section with no busID to primary device
> (--) Chipset mga2064w found
> (II) Loading /usr/X11R6/lib/modules/libvgahw.a
> (II) Module vgahw: vendor="The XFree86 Project"
> compiled for 220.127.116.11, module version = 0.1.0
> (**) MGA(0): Depth 24, (--) framebuffer bpp 32
> (==) MGA(0): RGB weight 888
> (II) MGA(0): Matrox HAL module not found - using builtin mode setup instead
> (--) MGA(0): Chipset: "mga2064w"
> (==) MGA(0): Using AGP 1x mode
> (**) MGA(0): Using framebuffer device
> (II) Loading /usr/X11R6/lib/modules/linux/libfbdevhw.a
> (II) Module fbdevhw: vendor="The XFree86 Project"
> compiled for 18.104.22.168, module version = 0.0.2
> (II) Unloading /usr/X11R6/lib/modules/linux/libfbdevhw.a
> (II) Unloading /usr/X11R6/lib/modules/libvgahw.a
> (EE) Screen(s) found, but none have a usable configuration.
> Fatal server error:
> no screens found
> When reporting a problem related to a server crash, please send
> the full server output, not just the last messages.
> This can be found in the log file "/var/log/XFree86.0.log".
> Please report problems to email@example.com.
> X connection to :0.0 broken (explicit kill or server shutdown).
> I use Debian/GNU Linux version 2.2;
> Linux server 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i586 unknown
> DEBIAN NEWBIE TIP #88 from Jesse Goerz <firstname.lastname@example.org>
> Ever wondered WHAT DOCUMENTATION IS ON YOUR SYSTEM? And if
> there was an easy way to browse it?
> apt-get install dhelp
> or for those running the testing distribution, try
> doc-central as well.
> Also see http://newbieDoc.sourceForge.net/ ...