Re: dist-upgrade (potato-woody): how to get X back up?
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? 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 snip (II) Module mouse: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 1.0.0 (II) MGA: driver for Matrox chipsets: mga2064w, mga1064sg, mga2164w, mga2164w AGP, mgag100, mgag100 PCI, mgag200, mgag200 PCI, mgag400, mgag550 (--) 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 4.1.0.1, 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 4.1.0.1, 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 PROTECTED] X connection to :0.0 broken (explicit kill or server shutdown). aaugh! -- 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 [EMAIL PROTECTED] : Ever wondered WHAT DOCUMENTATION IS ON YOUR SYSTEM? And if there was an easy way to browse it? apt-get install dhelp dhelp or for those running the testing distribution, try doc-central as well. Also see http://newbieDoc.sourceForge.net/ ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 snip (II) Module mouse: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 1.0.0 (II) MGA: driver for Matrox chipsets: mga2064w, mga1064sg, mga2164w, mga2164w AGP, mgag100, mgag100 PCI, mgag200, mgag200 PCI, mgag400, mgag550 (--) 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 4.1.0.1, 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 4.1.0.1, 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 PROTECTED] X connection to :0.0 broken (explicit kill or server shutdown). aaugh! -- 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 [EMAIL PROTECTED] : Ever wondered WHAT DOCUMENTATION IS ON YOUR SYSTEM? And if there was an easy way to browse it? apt-get install dhelp dhelp or for those running the testing distribution, try doc-central as well. Also see http://newbieDoc.sourceForge.net/ ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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? From your log, it looks a bit as if your mouse isn't configured properly, or at all, in XF86Config. X is using Auto to try and work out what it is, and failing. Have a look at /etc/X11/XF86Config itself and see what's in the InputDevice section for mice. I dunno much about the automatic X config tools; I ran xf86config to get a basic setup and then hacked /etc/X11/XF86Config by hand. (Generally I reckon this is easier, and also seems to be the only way to force it to do 100Hz vertical refresh.) A lot of people are referring to XF86Config-4 instead of XF86Config these days. My compiled-from-xfree's-own-source X 4.2 calls it XF86Config, but presumably the Debianised version calls it by the new name. Perhaps someone else could clarify this? Your mouse is indeed a serial mouse. Option Protocol Microsoft should work. (A rare sentence combining should work and Microsoft.) You can funnel gpm data through to X by using gpm with the -R option and setting Option Device /dev/gpmdata in XF86Config. The slink version of gpm apparently only repeats in Mouse Systems protocol. Later versions can repeat the raw data. See man gpm for the options. I can't tell you because my man page is for my old gpm. If you can't figure it out you can always use Option Protocol MouseSystems. If you DON'T set up gpm to repeat the mouse won't work in X anyway unless you kill gpm before you startx. Pigeon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dist-upgrade (potato-woody): how to get X back up?
On Sun, Dec 01, 2002 at 06:31:48AM -0500, [EMAIL PROTECTED] wrote: In linux.debian.user, you wrote: under potato i had X up and running like a champ. now i've dist-upgraded to woody ... Try 'XFree86 -configure' If it detects your hardware, it will produce the proper XF86Config or XF86Config-4 file. Mine gave me such high resolution that I had to include some Mode lines in the Screen section for lower resolution. If it is less than perfect, at least you might be able to modify it. well i got my hopes up for a minute, there. (and thanx for the pointer -- i wouldn't have known to try that!) during XFree86 -configure the screen went blank, and some odd color blots flashed on and off across the middle of the screen real estate; the output looks like this: This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.1.0.1 / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: 21 December 2001 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Build Operating System: Linux 2.4.17 i686 [ELF] Module Loader present (==) Log file: /var/log/XFree86.0.log, Time: Thu Dec 5 11:15:04 2002 (--) using VT number 7 (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 0.1.0 (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 0.1.0 (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (--) PCI:*(0:14:0) Matrox MGA 2064W rev 1, Mem @ 0xe000/14, 0xe100/23 List of video drivers: atimisc r128 radeon mga glint nv tga s3virge sis rendition neomagic i740 tdfx savage cirrus vmware tseng trident chips apm glide fbdev i128 ati i810 imstt ark cyrix siliconmotion vesa vga v4l (II) Loading /usr/X11R6/lib/modules/drivers/atimisc_drv.o (II) Module atimisc: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 6.3.6 (II) Loading /usr/X11R6/lib/modules/drivers/r128_drv.o (II) Module r128: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 4.0.1 (II) Loading /usr/X11R6/lib/modules/drivers/radeon_drv.o (II) Module radeon: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 4.0.1 (II) Loading /usr/X11R6/lib/modules/drivers/mga_drv.o (II) Module mga: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 1.0.1 (II) Loading /usr/X11R6/lib/modules/drivers/glint_drv.o (II) Module glint: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 1.0.1 (II) Loading /usr/X11R6/lib/modules/drivers/nv_drv.o (II) Module nv: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 1.0.1 (II) Loading /usr/X11R6/lib/modules/drivers/tga_drv.o (II) Module tga: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 1.0.1 (II) Loading /usr/X11R6/lib/modules/drivers/s3virge_drv.o (II) Module s3virge: vendor=Kevin Brosius compiled for 4.1.0.1, module version = 1.6.13 (II) Loading /usr/X11R6/lib/modules/drivers/sis_drv.o (II) Module sis: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 0.6.0 (II) Loading /usr/X11R6/lib/modules/drivers/rendition_drv.o (II) Module rendition: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 4.0.0 (II) Loading /usr/X11R6/lib/modules/drivers/neomagic_drv.o (II) Module neomagic: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/drivers/i740_drv.o (II) Module i740: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 1.0.0 (II) Loading /usr/X11R6/lib/modules/drivers/tdfx_drv.o (II) Module tdfx: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 1.0.1 (II) Loading /usr/X11R6/lib/modules/drivers/savage_drv.o (II) Module savage: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 1.1.16 (II) Loading /usr/X11R6/lib/modules/drivers/cirrus_drv.o (II) Module cirrus: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 1.0.0 (II) Loading
Re: dist-upgrade (potato-woody): how to get X back up?
On Thu, Dec 05, 2002 at 11:38:04AM -0600, will trillich wrote: [ snip ] To test the server, run 'XFree86 -xf86config /root/XF86Config.new' and then i do XFree86 -xf86config /root/XF86Config.new just like it says, and the bilge-plate bitmap pattern comes up (the generic X background) with the X pointer in the center of the screen -- but the mouse does nothing and the keyboard appears to do nothing as well. (resolution looks to be about 640x480.) i know about CTL-ALT-BACKSPACE to get out of X in a hurry, which works, and where i then see 193 lines of output (i can send them if it'll help). here are some snippets related to my video card: [ snip ] (II) MGA(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits if there's useful snippets for you x-server sleuths there, please let me know! Snippets aren't too helpful. Instead, attach the file /var/log/XFree86.0.log (I'm not sure that's _exactly_ the correct name, because I'm not sure if that .0 means it was rotated or if .0 means display :0. The file will certainly be /var/log/XFree86something :) what other things can an ignoramus try, to get X working under woody? Which version of X do you have installed? My xserver is xserver-xfree86, version 4.2.1-3. Whenever I am having trouble with X and some video card or monitor, I google for 'name of card/monitor XF86Config'. You should end up with copies of XF86COnfigs that presumably are working for other people. I also use 2.4 kernels on any box running X because I like the DRI support. -- Nathan Norman - Incanus Networking mailto:[EMAIL PROTECTED] Multiculturalism is one society's tolerance of other societies' intolerance. -- Mark Steyn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dist-upgrade (potato-woody): how to get X back up?
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 nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dist-upgrade (potato-woody): how to get X back up?
In linux.debian.user, you wrote: under potato i had X (and kde2 thanks to some unofficial sources.list items) up and running like a champ. occasionally konqueror would die colorfully (hit alt-left to go back a few pages and boom, only one desktop, no window borders...) and X windows worked fine under potato. now i've dist-upgraded to woody and there are a plethora of technical questions i'm supposed to know the answers to, in order to get X going. such as-- select the desired X server driver please enter the video card's bus identifier enter the amount of memory used by your video card use kernel framebuffer interface? select the XKB rule set to use choose your mouse port choose the entry that best describes your mouse write default dri section to config file? ...to name a few... SO: how do i find out what those answers should be? e.g. what makes a mouse a ps/2 mouse and not ImPS/2? what the heck is a DRI device? how can you tell, by looking at the case, whether the mouse port would be called mouse or ttyS0 or psaux? (i finally figured out how to get to the questions again: it's dpkg-reconfigure xserver-xfree86 that does the asking. and i have no clue for the answers... :( ) === Try 'XFree86 -configure' If it detects your hardware, it will produce the proper XF86Config or XF86Config-4 file. Mine gave me such high resolution that I had to include some Mode lines in the Screen section for lower resolution. If it is less than perfect, at least you might be able to modify it. -- Anita GnuPG key: 1024D/9EDAC910 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
dist-upgrade (potato-woody): how to get X back up?
under potato i had X (and kde2 thanks to some unofficial sources.list items) up and running like a champ. occasionally konqueror would die colorfully (hit alt-left to go back a few pages and boom, only one desktop, no window borders...) and X windows worked fine under potato. now i've dist-upgraded to woody and there are a plethora of technical questions i'm supposed to know the answers to, in order to get X going. such as-- select the desired X server driver please enter the video card's bus identifier enter the amount of memory used by your video card use kernel framebuffer interface? select the XKB rule set to use choose your mouse port choose the entry that best describes your mouse write default dri section to config file? ...to name a few... SO: how do i find out what those answers should be? e.g. what makes a mouse a ps/2 mouse and not ImPS/2? what the heck is a DRI device? how can you tell, by looking at the case, whether the mouse port would be called mouse or ttyS0 or psaux? (i finally figured out how to get to the questions again: it's dpkg-reconfigure xserver-xfree86 that does the asking. and i have no clue for the answers... :( ) === i try anyway, to do startx and get bumpkis. here's the log file /var/log/XFree86.0.log after trying plain ol' vga monitor type and generic huh? responses from most of the other questions: snip (==) VGA(0): Virtual size is 320x200 (pitch 320) (**) VGA(0): Built-in mode Generic 320x200 default mode: 12.6 MHz (scaled from 25.2 MHz), 31.5 kHz, 70.2 Hz (VScan) (II) VGA(0): Modeline Generic 320x200 default mode 12.59 320 336 384 400 200 206 207 224 vscan 2 -hsync +vsync (++) VGA(0): DPI set to (100, 100) (II) Loading sub module fb (II) LoadModule: fb (II) Loading /usr/X11R6/lib/modules/libfb.a (II) Module fb: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 1.0.0 ABI class: XFree86 ANSI C Emulation, version 0.1 (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] 0 0 0xe100 - 0xe17f (0x80) MS[B] [1] 0 0 0xe000 - 0xe0003fff (0x4000) MS[B] [2] -1 00xffe0 - 0x (0x20) MX[B](B) [3] -1 00x0010 - 0x3fff (0x3ff0) MX[B]E(B) [4] -1 00x000f - 0x000f (0x1) MX[B] [5] -1 00x000c - 0x000e (0x3) MX[B] [6] -1 00x - 0x0009 (0xa) MX[B] [7] -1 00xe100 - 0xe17f (0x80) MX[B](B) [8] -1 00xe000 - 0xe0003fff (0x4000) MX[B](B) [9] 0 0 0x000a - 0x000a (0x1) MS[B] [10] 0 00x000b - 0x000b7fff (0x8000) MS[B](OprU) [11] 0 00x000b8000 - 0x000b (0x8000) MS[B](OprU) [12] -1 0 0x - 0x (0x1) IX[B] [13] -1 0 0x - 0x00ff (0x100) IX[B] [14] -1 0 0x6400 - 0x64ff (0x100) IX[B]E [15] -1 0 0xf000 - 0xf0ff (0x100) IX[B]E [16] 0 00x03b0 - 0x03bb (0xc) IS[B] [17] 0 00x03c0 - 0x03df (0x20) IS[B] (WW) System lacks support for changing MTRRs Fatal server error: AddScreen/ScreenInit failed for driver 0 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 PROTECTED] end seems odd that i feel more like a newbie now, after three years of debian, unable to get X working -- when on potato it was a snap (or maybe i just got RAL lucky)...? -- 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 #103 from Dave Sherohman [EMAIL PROTECTED] : Trying to CREATE A CRONTAB FOR THE LAST DAY OF THE MONTH? Best to put all the logic within the crontab itself (a Good Thing, since you then only have to look in one place to find it): 1 0 28-31 * * [ $(date +%d -d +1day) -eq 1 ] /path/to/script args Also see http://newbieDoc.sourceForge.net/ ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dist-upgrade (potato-woody): how to get X back up?
This one time, at band camp, will trillich said: and X windows worked fine under potato. now i've dist-upgraded to woody and there are a plethora of technical questions i'm supposed to know the answers to, in order to get X going. such as-- select the desired X server driver please enter the video card's bus identifier enter the amount of memory used by your video card use kernel framebuffer interface? select the XKB rule set to use choose your mouse port choose the entry that best describes your mouse write default dri section to config file? ...to name a few... SO: how do i find out what those answers should be? OK. Try cat /proc/pci to find out what video card is in your box - then you can look through the docs that came with xserver-xfree86 to find out which driver to use with it. For now, ignore the questions about bus identifier and memory - leave them blank. They'll only be needed if X can't detect your card automagically. Framebuffer makes setting up X a little easier, but all the graphics are slw. You'll need to find the refresh settings for your monitor somewhere - owner's manual or manufacturer's website are always good places to start. XKB ruleset is, IIRC, kind of straightforward - regular or USB? What country? Mouse - see below. DRI can't hurt, go ahead. e.g. what makes a mouse a ps/2 mouse and not ImPS/2? what the heck is a DRI device? how can you tell, by looking at the case, whether the mouse port would be called mouse or ttyS0 or psaux? ttyS0 is a serial mouse, and psaux is a PS2 mouse. PS2 mice have the little round connector, and serial mice have the, well, serial connector that's kind of rhombus shaped. As for which protocol, again, read the docs for your mouse. If I can't figure it out, I try one and then another untilit stops jumping around. If you have gpm running, you can use gpmdata instead. (i finally figured out how to get to the questions again: it's dpkg-reconfigure xserver-xfree86 that does the asking. and i have no clue for the answers... :( ) HTH, -- -- | Stephen Gran | It's not really a rule--it's more like | | [EMAIL PROTECTED] | a trend. -- Larry Wall in | | http://www.lobefin.net/~steve | [EMAIL PROTECTED]| -- msg16306/pgp0.pgp Description: PGP signature
