Potato .deb pkg install of apache/php/mod_perl/postgresql or mysql
I run potato, now about 4 weeks old. I want to install apache with php (3 or 4), mod_perl and either postgresql or mysql. It seems better in the long run to master an apt-get-based method of installing them *if* that is possible--that's what I don't know. I have looked in the debian-user archives and found some relevant posts but nothing that quite answered my question. Is it possible to do so using apt-get & the right debian packages? If so, is there an order to events to make it all work? For instance, should one install postgres/mysql, then apache-perl, then php4-pgsql? Or does it only work to have source for apache and php and perhaps the database, too? Or do folks usually end up compiling their own? In that case, does anyone have a suggestion for which versions of each source to get that match well together? And is it reliable to use debian sources (via apt-get source) to get the programs working together (presuming I follow their directions ;-])? Or should one just head for the 'real' source? Thanks. -- Gordon Pedersen info systems design Saint Paul, Minnesota, USA [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: Potato .deb pkg install of apache/php/mod_perl/postgresql or mysql
Thanks. Your post built confidence so I waded in today. I got apache, php4 and postgresql limping along together, now working on mod_perl. I bear in mind what you said about php4, but it was already installed so I just used it for today's trial. It was easy for the first three: apt-get install apache php4 php4-pgsql postgresql (maybe a few of these) Potato /etc/mime.types comes php-ready: application/x-httpd-php phtml pht php etc. /etc/apache/httpd.conf needed just this: LoadModule php4_module /usr/lib/apache/1.3/libphp4.so /etc//php4/apache/php.ini needed just this: extension=pgsql.so Gordon On Sat, Jul 08, 2000 at 11:29:08AM +0800, Corey Popelier wrote: > I have just completed an install based on MySQL, Apache and PHP3. This was > all done using apt-get install (I'm using woody though, on a 2.2.15 > kernel). > > If you pursue this direction, feel free to email me directly if you need > some hints or tips. Only thing I can think of to say at the moment is get > MySQL and Apache working, then do PHP last. This can all be done using > apt-get install (mysql-server, mysql-client, apache, php3, > php3-mysql) and whatever else it grabs :) > > There should then be an extension=mysql.so line in the php3.ini file, and > a LoadModule line relating to mysql in the apache httpd.conf file. There > isnt much more to this setup - assuming you've set up apache right in the > first place. The config files for apache (httpd.conf, srm.conf) are > pretty well documented. > > You could certainly do Apache first, get that working, then do MySQL and > finally tie the two with PHPx without too much complexity. > > Mod_Perl i cant comment on. Oh, and this above detail should be pretty > right with potato too. And I'd prolly recommend you stay away from PHP4 > for now, from what ive heard its not quite "there" yet. > > Cheers, > Corey Popelier > http://members.dingoblue.net.au/~pancreas > Work Email: [EMAIL PROTECTED] > > On Fri, 7 Jul 2000, Gordon Pedersen wrote: > > > I run potato, now about 4 weeks old. > > > > I want to install apache with php (3 or 4), mod_perl and either > > postgresql or mysql. > > > > It seems better in the long run to master an apt-get-based method of > > installing them *if* that is possible--that's what I don't know. > > > > I have looked in the debian-user archives and found some relevant > > posts but nothing that quite answered my question. > > > > Is it possible to do so using apt-get & the right debian packages? > > If so, is there an order to events to make it all work? For > > instance, should one install postgres/mysql, then apache-perl, then > > php4-pgsql? Or does it only work to have source for apache and php > > and perhaps the database, too? > > > > Or do folks usually end up compiling their own? > > > > In that case, does anyone have a suggestion for which versions of > > each source to get that match well together? > > > > And is it reliable to use debian sources (via apt-get source) to get > > the programs working together (presuming I follow their > > directions ;-])? Or should one just head for the 'real' source? > > > > Thanks. > > > > -- > > Gordon Pedersen > > info systems design Saint Paul, Minnesota, USA > > [EMAIL PROTECTED] > > [EMAIL PROTECTED] > > > > > > -- > > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > > -- Gordon Pedersen info systems design Saint Paul, Minnesota, USA [EMAIL PROTECTED] [EMAIL PROTECTED]
Setting up IP aliasing, cannot find kernel modules
I need to set up IP aliasing and per the (aging but probably still sound) IP-Alias-Mini-HOWTO, I need the .../ipv4/ip_alias.o module. It's not on my system. It doesn't appear to be in kernel-source-2.2.15--I downloaded but did not untar it, just peeked inside with 'tar -t'. I can't find it at the debian site. That probably just means I don't know where to look, since I'm still new to debian. I run potato, installed entirely from packages, so no custom kernel installed on this machine as yet, but I shouldn't need to in order to use a module, AFAIK. Or is aliasing handled differently in 2.2 than earlier kernels? Thanks for any help. Gordon Gordon Pedersen [EMAIL PROTECTED]
Finding and installing lp.o from 2.2.15
(Please reply to [EMAIL PROTECTED] in addition to debian-users. Thanks.) 6 months ago I installed 2.2.15 potato and at the time did not install the lp.o line printer module--big mistake, as it turns out. (I was using a networked printer, had no local printer.) Now I need to install the lp.o module and cannot find it. All I could find on debian site was one from 2.2.18pre21. That doesn't load with modprobe--complains like this: /lib/modules/2.2.15-idepci/misc/lp.o: kernel-module version mismatch /lib/modules/2.2.15-idepci/misc/lp.o was compiled for kernel version 2.2.18pre21 while this kernel is version 2.2.15-idepci. /lib/modules/2.2.15-idepci/misc/lp.o: insmod /lib/modules/2.2.15-idepci/misc/lp.o failed /lib/modules/2.2.15-idepci/misc/lp.o: insmod lp failed I've looked all over debian.org and can't find the actual file that I need in the version that I need. I also could find no helpful instructions for someone in the pickle I'm in. I hope you can help. What are my options? Simply install some package? Must I upgrade first? --- If so, what package gets me a slew of modules, or at least the lp.o module? Steal the module from the rescue or root or driver 'bin' floppies? -- Does anyone know how to do this? It seems to be the easiest approach. My floppies are labelled 2.2r0 which ended up with kernel 2.2.15 in June, 2000. Compile from source? --- I have the file kernel-source-2.2.15.tar. I know that lp.c is in there, but I wonder if all the header files, etc, that I need are there. (I don't often compile c programs, and don't undertand well enough how debian divvies up the various files into packages.) I haven't found a document which describes how to proceed to locate all the pieces and compile a module from source, but could probably follow it if I had one. Thanks in advance. I will no doubt need this again for something else. :-) (Please reply to [EMAIL PROTECTED] in addition to debian-users. Thanks.) -- Gordon Pedersen [EMAIL PROTECTED]
Re: Finding and installing lp.o from 2.2.15
On Sat, Dec 09, 2000 at 03:07:11AM -0600, Nathan E Norman wrote: > On Sat, Dec 09, 2000 at 02:28:39AM -0600, Gordon Pedersen wrote: > > (Please reply to [EMAIL PROTECTED] in addition to debian-users. > > Thanks.) > > > > What are my options? > > If I were you I'd install the kernel 2.2.18 source, the kernel-package > package, and build a kernel. yes. it's a bit daunting the firstr > time, but I figured it out a few years ago and I'm not the brightest > bulb on the tree :) The kernel-package setup makes it all really > easy. > > Here's what you do: > > - Install kernel-source, kernel-package, fakeroot, and libncurses5-dev > - make menuconfig (or make xconfig) make sure you pick the lp and > parport modules! > - run `kernel-package --clean' > - run `fakeroot kernel-package --revision=local.2.2.18-1 kernel_image' > - cd ..; dpkg -i kernel-image-2.2.18_local.2.2.18-1_i386.deb > > That's it! Modules will be installed where they should be, lilo will > run if you want it (and you point it at a generic target like > /vmlinuz). Of course it's a good idea to check your lilo config and > run it again as root before you reboot :) > I like the sound of the first plan, so here goes Thank you for the detailed little cookbook procedure! I don't compile kernels more than once in a blue moon, and my old grey cells are getting greyer by the week. I am trying to master the debian way, which I hope will last me for awhile, and I need a good kernel config/install recipe. gp > > Simply install some package? Must I upgrade first? > > --- > > If so, what package gets me a slew of modules, or at least the lp.o > > module? > > You could punt on the above, and run > > `apt-get install kernel-image-2.2.18pre21' > > > Compile from source? > > --- > > I have the file kernel-source-2.2.15.tar. I know that lp.c is in > > there, but I wonder if all the header files, etc, that I need are > > there. (I don't often compile c programs, and don't undertand well > > enough how debian divvies up the various files into packages.) > > > > I haven't found a document which describes how to proceed to locate > > all the pieces and compile a module from source, but could probably > > follow it if I had one. > > You could follow the directions above with your 2.2.15 source, but > 2.2.15 has enough problems that I'd go with newer code. > > Good luck! > > -- > Nathan Norman - Staff Engineer | A good plan today is better > Micromuse Inc. | than a perfect plan tomorrow. > mailto:[EMAIL PROTECTED] | -- Patton -- Gordon Pedersen [EMAIL PROTECTED] [EMAIL PROTECTED]
X fails to start - Intel i810 (845) - etch + testing
uffers and small DRI memory manager reservation: (II) intel(0): Allocating 7164 scanlines for pixmap cache (WW) intel(0): Failed to allocate texture space. (II) intel(0): Attempting memory allocation with untiled buffers and large DRI memory manager reservation: (II) intel(0): Allocating 7164 scanlines for pixmap cache (II) intel(0): Attempting memory allocation with untiled buffers and small DRI memory manager reservation: (II) intel(0): Allocating 7164 scanlines for pixmap cache (WW) intel(0): Failed to allocate texture space. (WW) intel(0): Not enough video memory. Disabling DRI. (II) intel(0): Allocating 7164 scanlines for pixmap cache (II) intel(0): Memory allocation layout: (II) intel(0): 0x-0x0001: ring buffer (128 kB) (II) intel(0): 0x0002-0x00024fff: HW cursors (20 kB) (II) intel(0): 0x00025000-0x0002cfff: logical 3D context (32 kB) (II) intel(0): 0x0002d000-0x0003cfff: xaa scratch (64 kB) (II) intel(0): 0x007df000:end of stolen memory (II) intel(0): 0x007df000-0x007d: overlay registers (4 kB, 0x034a2000 physic al) (II) intel(0): 0x007e-0x04fd7fff: front buffer (73696 kB) (II) intel(0): 0x0800:end of aperture (II) intel(0): front buffer is not tiled (II) intel(0): Page Flipping disabled (==) intel(0): Write-combining range (0xe000,0x800) (II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x (II) intel(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles 8x8 mono pattern filled rectangles Indirect CPU to Screen color expansion Solid Horizontal and Vertical Lines Offscreen Pixmaps Setting up tile and stipple cache: 32 128x128 slots 32 256x256 slots 16 512x512 slots (==) intel(0): Backing store disabled (==) intel(0): Silken mouse enabled (II) intel(0): Initializing HW Cursor (II) intel(0): xf86BindGARTMemory: bind key 0 at 0x007df000 (pgoffset 2015) (II) intel(0): xf86BindGARTMemory: bind key 1 at 0x007e (pgoffset 2016) (WW) intel(0): ESR is 0x0010, page table error (WW) intel(0): PGTBL_ER is 0x0049 (WW) intel(0): Existing errors found in hardware state. (II) intel(0): Output configuration: (II) intel(0): Pipe A is on (II) intel(0): Display plane A is now enabled and connected to pipe A. (II) intel(0): Output VGA is connected to pipe A (**) Option "dpms" (**) intel(0): DPMS enabled (II) intel(0): Set up overlay video (II) intel(0): direct rendering: Disabled (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message. (--) RandR disabled (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension XAccessControlExtension (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFIXES (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) Initializing built-in extension XEVIE (EE) AIGLX: Screen 0 is not DRI capable (II) Loading local sub module "GLcore" (II) LoadModule: "GLcore" (II) Loading /usr/lib/xorg/modules/extensions//libGLcore.so (II) Module GLcore: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.3 (II) GLX: Initialized MESA-PROXY GL provider for screen 0 (II) intel(0): Setting screen physical size to 375 x 300 (**) Option "CoreKeyboard" (**) Generic Keyboard: Core Keyboard (**) Option "Protocol" "standard" (**) Generic Keyboard: Protocol: standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xorg" (**) Generic Keyboard: XkbRules: "xorg" (**) Option "XkbModel" "pc104" (**) Generic Keyboard: XkbModel: "pc104" (**) Option "XkbLayout" "us" (**) Generic Keyboard: XkbLayout: "us" (**) Option "CustomKeycodes" "off" (**) Generic Keyboard: CustomKeycodes disabled (**) Option "Protocol" "MouseMan" (**) Configured Mouse: Device: "/dev/input/mice" (**) Configured Mouse: Protocol: "MouseMan" (**) Option "CorePointer" (**) Configured Mouse: Core Pointer (**) Option "Device" "/dev/input/mice" (**) Option "Emulate3Buttons" "true" (**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50 (**) Option "ZAxisMapping" "4 5" (**) Configured Mouse: ZAxisMapping: buttons 4 and 5 (**) Configured Mouse: Buttons: 9 (**) Configured Mouse: Sensitivity: 1 (**) Option "BaudRate" "1200" (**) Configured Mouse: BaudRate: 1200 (II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE) (II) XINPUT: Adding extended input device "Generic Keyboard" (type: KEYBOARD) (**) Option "Device" "/dev/input/mice" Could not init font path element /usr/share/fonts/X11/cyrillic, removing from li st! Could not init font path element /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueTyp e, removing from list! (II) intel(0): xf86UnbindGARTMemory: unbind key 0 (II) intel(0): xf86UnbindGARTMemory: unbind key 1 FreeFontPath: FPE "/usr/share/fonts/X11/misc" refcount is 2, should be 1; fixing. -- Gordon Pedersen [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: X fails to start - Intel i810 (845) - etch + testing
On 9/9/07, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: Thanks for the detailed suggestions - too late tonight to experiment, so will do so Monday and report back. > On Sun, Sep 09, 2007 at 10:19:10PM -0500, Gordon Pedersen wrote: > > Hi, > > > > New etch installation on box with builtin video Intel 845. > > > > This is a fresh etch install, i386, 2004 hardware. See DETAILED > > NOTES below for hardware notes, xorg.conf and Xorg.0.log. > > > > Does anyone have X working on one of these builtin Intel 845 chipsets? > > yep. In fact I think I have a 845G Brookdale running in sid right now > and it worked fine in etch, but my monitor wasn't supported, hence the > upgrade to sid. > > > > > I have tried the following changes to xorg.conf: > > > > - no DRI > > - no DRI and no glx > > - no "Modes" lines > > - use "vesa" instead of "i810" > > i810 is being replaced by intel, so fix up your xorg.conf to reflect > intel instead, but that's not your problem here. > > > > > > > Finally, I installed testing versions of xserver-xorg and > > xserver-xorg-video-i810. Still can't get X to start, although now I > > get that special "click" sound when it tries to start. > > the log you included doesn't look like the log of a failed X > session. What exactly happens, other than the magical "click" when the > monitor changes modes? Do you end up back at a VT? do you get a > garbled or black screen? details! > > one note from the logs, it is selecting an initial resolution of > 1920x1200. Does your monitor really support that? it looks like a > hitachi from 1996, and I'd be surprised. I'm guessing that you're > getting a bad mode setting that's not compatible with your monitor. > > try ctrl-alt-keypad'-' or keypad'+' and see if you can toggle your way > into a different mode. > > > > > Any ideas? What can I try? > > the new intel drivers do a fairly decent job of guessing all the > details about your setup. > > I would clean up the xorg.conf by getting rid of all the SubSection > "Display" lines and the VideoRam lines. This would prevent xorg from > trying to second guess what the drivers are telling it. Also, have you > done a good dpkg-reconfigure xserver-xorg? > > A > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFG5LzPaIeIEqwil4YRAm03AJwKXFevE1zSK+LVOyQxWaAzZPtFcQCfeeo4 > UQqzkG+DsLHToYHwFaCp2ms= > =HcIM > -END PGP SIGNATURE- > > -- Gordon Pedersen [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: X fails to start - Intel i810 (845) - etch + testing
On 9/9/07, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: > On Sun, Sep 09, 2007 at 10:19:10PM -0500, Gordon Pedersen wrote: > > Hi, > > > > New etch installation on box with builtin video Intel 845. > > > > i810 is being replaced by intel, so fix up your xorg.conf to reflect > intel instead, but that's not your problem here. Done. I also read on linuxquestions.org about someone who actually downgraded to use the former i810 package (prior to its being subsumed into the intel pkg), FWIW. > the log you included doesn't look like the log of a failed X > session. What exactly happens, other than the magical "click" when the > monitor changes modes? Do you end up back at a VT? do you get a > garbled or black screen? details! The earlier log was certainly from a failed X sessions, appearances to the contrary. - Sorry not to be more precise. When I said that X fails to start I meant that it dropped me back to the terminal from which I had issued "startx -- -logverbose". > > one note from the logs, it is selecting an initial resolution of > 1920x1200. Does your monitor really support that? it looks like a > hitachi from 1996, and I'd be surprised. I'm guessing that you're > getting a bad mode setting that's not compatible with your monitor. See what you interpret from the new Xorg.0.log at bottom. If it is choosing an incorrect mode, how do I prevent that? > I would clean up the xorg.conf by getting rid of all the SubSection > "Display" lines and the VideoRam lines. This would prevent xorg from > trying to second guess what the drivers are telling it. Also, have you > done a good dpkg-reconfigure xserver-xorg? I did a dpkg-reconfigure xserver-xorg. I got rid of all the SubSection "Display" stanzas and VideoRam lines, as well as CRT-specific settings lines. Here are Just the error messages from the complete /var/log/Xorg.0.log listed at bottom of DETAILED NOTES: (EE) intel(0): detecting sil164 (EE) intel(0): Unable to read from DVOI2C_E Slave 112. (EE) intel(0): Unable to read from DVOI2C_E Slave 236. (EE) intel(0): ivch detect failed due to address mismatch (0 vs 2) (EE) intel(0): ivch: Unable to read register 0x01 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x40 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x01 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x01 from DVOI2C_B:04. (EE) intel(0): Unable to write register 0x01 to DVOI2C_B:4. (EE) intel(0): Unable to write register 0x40 to DVOI2C_B:4. (EE) intel(0): ivch: Unable to read register 0x01 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x40 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x01 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x01 from DVOI2C_B:04. (EE) intel(0): Unable to write register 0x01 to DVOI2C_B:4. (EE) intel(0): Unable to write register 0x40 to DVOI2C_B:4. (EE) intel(0): ivch: Unable to read register 0x00 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x01 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x30 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x40 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x80 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x81 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x82 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x83 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x84 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x85 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x86 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x87 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x88 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x8e from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x8f from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x01 from DVOI2C_B:04. (EE) intel(0): ivch: Unable to read register 0x01 from DVOI2C_B:04. (EE) intel(0): I830 Vblank Pipe Setup Failed 0 (EE) intel(0): ivch: Unable to read register 0x01 from DVOI2C_B:04. (EE) intel(0): I830 Vblank Pipe Setup Failed 0 (EE) intel(0): Unable to write register 0x01 to DVOI2C_B:4. (EE) intel(0): Unable to write register 0x40 to DVOI2C_B:4. === DETAILED NOTES - /etc/X11/xorg.conf - # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. # (Type "man /etc/X11/xorg.conf" at the shell prompt.) # # This file is automatically updated
Re: X fails to start - Intel i810 (845) - etch + testing
Andrew: Just a quick feedback to say thanks a bunch for poring over that lengthy post - really appreciate the details about what you tried that worked and your insights into the verbose-yet-cryptic X error log. Quick check verifies that there is just the builtin 82845G chipset video - no extra video card - and certainly no second monitor(!!). I will try to force the driver to use my attached Hitachi CRT and post again. Undocumented is an understatement - on the other hand, hope the X gnomes out there are dreaming up code not docs at this point - aside from maybe having a good spec Gordon On 9/11/07, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: > On Mon, Sep 10, 2007 at 12:41:34PM -0500, Gordon Pedersen wrote: > > On 9/9/07, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: > > ... > > > > > > one note from the logs, it is selecting an initial resolution of > > > 1920x1200. Does your monitor really support that? it looks like a > > > hitachi from 1996, and I'd be surprised. I'm guessing that you're > > > getting a bad mode setting that's not compatible with your monitor. > > > > See what you interpret from the new Xorg.0.log at bottom. > > comments below. > > > > > If it is choosing an incorrect mode, how do I prevent that? > > its tricky with the intel driver as it really likes to do its own > thing. You have to do some mojo to create a mode that appears in the > list before any others. This is what I had to do for my wife's > machine... and it was hard to suss out because of a lack of > documentation. First, it appears to me that the intel driver uses the > highest resolution it can come up with based on its probing of the > devices. It will ignore anything else you tell it, mostly. And the > listing of available resolutions comes out in the same order as you'd > get using xrandr. So, for example, my wife's machine used to display > the following (paraphrased) resolutions for her 1440x900 monitor: > > size Freq. > 1440x900 59.8 60 > 1280x1024 blah blah blah > 1024x768 blah blah blah > ... > > and it would select [EMAIL PROTECTED] which was an invalid spec for the > monitor and would produce a stupidly off-center display. > > I had first tell the driver to use the monitor specifications in the > xorg.conf, otherwise it will just ignore them. Do this in > > Section "Device" >Identifier... >Driver "intel" >... >Option "Monitor-VGA" "monitor_id" > EndSection > > this tells xorg to use the specifications for "monitor_id" instead of > or alongside of the probed ones. > > Then I had to specify a mode in the monitor section > > Section "Monitor" >Identifier "monitor_id" >... >Modeline "1440x900_75" ... >... > EndSection > > this mode appears before the others in the xrandr output and so > becomes the one selected by xorg. Its confusing and undocumented and > ymmv. And this doesn't deal with your real issue, I think, upon > reading the logs below, only with the issue of resolution. > > > ... > > snipped xorg.conf and a bunch of (EE)'s that I don't know diddly > about. > > ... > > > > > - > > /var/log/Xorg.0.log > > - > > > > X Window System Version 1.3.0 > > Release Date: 19 April 2007 > > X Protocol Version 11, Revision 0, Release 1.3 > > Build Operating System: Linux Debian (xorg-server 2:1.3.0.0.dfsg-12) > > Current Operating System: Linux pan 2.6.18-5-686 #1 SMP Fri Jun 1 00:47:00 > > UTC 2 > > 007 i686 > > Build Date: 09 August 2007 > > Before reporting problems, check http://wiki.x.org > > to make sure that you have the latest version. > > Module Loader present > > Markers: (--) probed, (**) from config file, (==) default setting, > > (++) from command line, (!!) notice, (II) informational, > > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > > (==) Log file: "/var/log/Xorg.0.log", Time: Mon Sep 10 11:23:21 2007 > > (==) Using config file: "/etc/X11/xorg.conf" > > (==) ServerLayout "Default Layout" > > (**) |-->Screen "Default Screen" (0) > > (**) | |-->Monitor "Hitachi 203" > > (**) | |-->Device "Intel 845 Brookdale" > > (**) |-->Input Device "Generic Keyboard" > > (**) |-->Input Device "Configured Mouse" > > okay, this all looks good. > ... > > > (II) intel(0): Output VGA using monitor section Hitach
Re: X fails to start - Intel i810 (845) - etch + testing
On 9/11/07, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: > On Tue, Sep 11, 2007 at 02:11:25PM -0500, Gordon Pedersen wrote: > > log. Quick check verifies that there is just the builtin 82845G > > chipset video - no extra video card - and certainly no second > > monitor(!!). > > happy to help, though its effectiveness remains to be seen. I reviewed > the Xorg logs on my wife's machine and confirmed that it does *NOT* > make mention (other than one passing reference, I think) to LVDS. I'm > sure that's your problem. And its surely worth a bug-report if that > ends up being the problem. Now different errors. :-) (Apologies if text gets misformatted here - am forced to cut and paste into a gmail session to get this post out today.) I reinstalled xserver-xorg then followed these suggestions: . Added to xorg.conf: . Section "Device" Option"Monitor-VGA" "Hitachi 803" . Section "Monitor" Modeline "1600x1200" 202.50 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync Good news - no longer trying to connect to LVDS output - but this seems to be more due to choosing an incompatible Modeline than anything else. More good news - X does seem to use the 1600x1200 Modeline specified in xorg.conf Monitor section. But still X does not start. See errors immediately below, followed by xorg.conf and Xorg.0.log. Errors are different, and may prove clue to something else going wrong. But I have no idea what they mean. See what you think. (BTW: have tried disabling glx and dri in xorg.conf, former is still auto-loaded by X and the errors are essentially unchanged.) Googled this: unable to read from dvoi2c_e tfp410 There are bugs open at debian, although doubt we all have same issues. In particular see http://lists.debian.org/debian-x/2007/08/msg00746.html (bug #438650). Bug#424952 might be related, too, although a bit stale. Because this is new system, and prior config values from prior testing exim-4 installation don't seem to be working, I would have a difficult time submitting a bug using "reportbug". Not sure how else to do it. And maybe the above bug report is similar enough - is it good etiquette to chime in "me, too" on a bug report? And do bug reports that are not totally boilerplate standard tend to get ignored? (And as for stable vs testing, that's always a tough question on this server which is my primary file server, but also a workstation that I want to start using again. All in all, if stable xorg worked for me, I'd go back to stable reluctantly. Will try stable again when time permits, but may be awhile.) gordon === Just the error messages from the complete /var/log/Xorg.0.log listed at bottom of DETAILED NOTES: (EE) intel(0): detecting sil164 (EE) intel(0): Unable to read from DVOI2C_E Slave 112. (EE) intel(0): Unable to read from DVOI2C_E Slave 236. (EE) intel(0): ivch: Unable to read register 0x00 from DVOI2C_B:04. (EE) intel(0): Unable to read from DVOI2C_E Slave 112. (EE) intel(0): tfp410 not detected got VID : from DVOI2C_E Slave 112. (EE) intel(0): I830 Vblank Pipe Setup Failed 0 (EE) intel(0): I830 Vblank Pipe Setup Failed 0 === DETAILED NOTES - /etc/X11/xorg.conf - # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. # (Type "man /etc/X11/xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "Files" FontPath"/usr/share/fonts/X11/misc" FontPath"/usr/X11R6/lib/X11/fonts/misc" FontPath"/usr/share/fonts/X11/cyrillic" FontPath"/usr/X11R6/lib/X11/fonts/cyrillic" FontPath"/usr/share/fonts/X11/100dpi/:unscaled" FontPath"/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/share/fonts/X11/75dpi/:unscaled" FontPath"/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/share/fonts/X11/Type1" FontPath"/usr/X11R6/lib/X11/fonts/Type1" FontPath"/usr/share/fonts/X11/100dpi&quo
Re: X fails to start - Intel i810 (845) - etch + testing
Have answered my own questions about bug reporting and joining, and have chimed in on open bugs 424952 and 438650. They both appear to be still open, with no evidence of upstream changes yet. (Perhaps addressed in unstable?? Not that I would dare run that on this box.) On 9/11/07, Gordon Pedersen <[EMAIL PROTECTED]> wrote: > Googled this: unable to read from dvoi2c_e tfp410 > > There are bugs open at debian, although doubt we all have same > issues. In particular see > http://lists.debian.org/debian-x/2007/08/msg00746.html (bug #438650). > Bug#424952 might be related, too, although a bit stale. > > Because this is new system, and prior config values from prior testing > exim-4 installation don't seem to be working, I would have a difficult > time submitting a bug using "reportbug". Not sure how else to do it. > And maybe the above bug report is similar enough - is it good > etiquette to chime in "me, too" on a bug report? And do bug reports > that are not totally boilerplate standard tend to get ignored? > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Surefire Xorg driver/config?
I'm seeking alternative ways to get X up and running on this newly installed lenny box. - Willing to go to stable for all pkgs. - Willing to go to unstable for video (if it does not mean going unstable for core non-X libraries). Is there an xorg driver/configuration that works under almost all circumstances? Hardware: - Intel 82845G Brookdale rev3 chipset - Hitachi 803 21in older CRT w/bandwidth in excess of 200MB. H Freq.V Freq. 31-115KHz 50-160Hz current xorg packages (willing to switch): xserver-xorg/testing uptodate 1:7.2-5 xserver-xorg-video-intel/testing uptodate 2:2.1.0-2 xserver-xorg-core/testing uptodate 2:1.3.0.0.dfsg-12 (It appears to me that the current lenny xorg video driver (xserver-xorg-video-intel) for Intel 845G chipset is flawed. See bugs 438650 and 424952. I also had failure using the stable xorg and i810 driver.) -- Gordon Pedersen [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: X fails to start - Intel i810 (845) - etch + testing
On 9/12/07, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: > On Tue, Sep 11, 2007 at 04:21:31PM -0500, Gordon Pedersen wrote: > > On 9/11/07, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: > > > On Tue, Sep 11, 2007 at 02:11:25PM -0500, Gordon Pedersen wrote: > > > > > > log. Quick check verifies that there is just the builtin 82845G > > > > chipset video - no extra video card - and certainly no second > > > > monitor(!!). > > > > I reinstalled xserver-xorg then followed these suggestions: > > . Added to xorg.conf: > > . Section "Device" Option"Monitor-VGA" > > "Hitachi 803" > > . Section "Monitor" > > Modeline "1600x1200" 202.50 1600 1664 1856 2160 1200 1201 > > 1204 > > 1250 +hsync +vsync > > > > > More good news - X does seem to use the 1600x1200 Modeline specified > > in xorg.conf Monitor section. > > again, does your monitor support that resolution? It probably won't > keep xorg from starting but I'd hate for you to fry the monitor... I was pretty sure but I doublechecked: see http://www.monitorworld.com/Monitors/nsahitachi/superscansupreme803cm803mu.html Max Resolution: 1600 x 1280 > > But still X does not start. See errors immediately below, followed > > by xorg.conf and Xorg.0.log. > > I assume its the same thing as before? back to the cli? Yes, same symptom - back to the cli. > > Googled this: unable to read from dvoi2c_e tfp410 > > yeah, that error crops up in my wife's working config. I think its > just xorg trying different stuff and failing as a means to determine > capabilities as opposed to a fatal error. That's intriguing. > > one think that I'm having trouble with, there is no error message that > indicates a failure. Typically, you'll see something like: > > (EE) intel(0): No valid modes. > (EE) Screen(s) found, but none have a usable configuration. > > Fatal server error: > no screens found > > and either you're snipping that or its not there. When I report those (EE) messages I use grep to gather all of them. I might forget on occasion to look at very bottom of the Xorg.0.log file, I'm getting so bored with it, so it's good that you prompt me to be sure to do so!! > > Lets review plese how you are starting this system. I know you are > using some startx incantation. What config file are you using to > control that xsession, and what are the contents of that file? > > The reason I ask is, lacking those error messages above, I think you > are *may* be successfully starting an x session and then automatically > killing it. If you combine that with a mode that your monitor doesn't > support, and you won't even see the typical X grey screen with "x" cursor". I issue a "startx -- -logverbose" command every time during these trials. xorg.conf and complete Xorg.0.log come after the following comments. Interesting to me that it still starts in 1600x1200 even though I am now issuing a Modeline using 1024x768 in xorg.conf. After repetitive "Vblank Pipe Setup Failed" errors, googled: i830 vblank pipe setup failed I won't try to summarize what I saw from Google, which is to me not meaningful, and maybe inconclusive, maybe not. One bug report on freedesktop.org does point to a "Wang Zhenyu" zhenyu.z.wang at intel.com who was earlier this year fixing bugs in this driver. None that I saw had outright failure to start as a symptom but it wasn't an exhaustive survey of the bugs. ;-) Still sounds to me like a driver with known problems, and possibly unworkable for my hardware right at this moment in time. In separate post to come I will give detail on the failed vesa driver X session. Different errors, and maybe solvable. Did I ever say that this hardware setup works just fine in an earlier testing version I had installed last year? Using an earlier version of all xorg, I believe. Would have to reboot to verify exactly what. === Just the error messages from the complete /var/log/Xorg.0.log listed at bottom of DETAILED NOTES: (EE) intel(0): detecting sil164 (EE) intel(0): Unable to read from DVOI2C_E Slave 112. (EE) intel(0): Unable to read from DVOI2C_E Slave 236. (EE) intel(0): ivch: Unable to read register 0x00 from DVOI2C_B:04. (EE) intel(0): Unable to read from DVOI2C_E Slave 112. (EE) intel(0): tfp410 not detected got VID : from DVOI2C_E Slave 112. (EE) intel(0): I830 Vblank Pipe Setup Failed 0 (EE) intel(0): I830 Vblank Pipe Setup Failed 0 =
Re: Surefire Xorg driver/config?
On 9/12/07, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: > On Wed, Sep 12, 2007 at 11:10:04AM -0500, Gordon Pedersen wrote: > > I'm seeking alternative ways to get X up and running on this newly > > installed lenny box. > > > > see my other post for more discussion of this problem. in the > meantime, try the "vesa" driver. I reinstalled etch 4.0r1 from scratch. So all below refers to stable. Then, it's late so will be terse. Hope the meaning is plain. I don't see what's up yet but we're making progress. Here's what I did post-install. # apt-get install xserver-xorg-video-vesa Made no changes to xorg.conf (see it below). Then did (as errors revealed missing pkgs): # apt-get install xfonts-base xfonts-100dpi xfonts-scalable # apt-get install xterm # apt-show-versions |sort| grep ^xserver xserver-xorg-core/etch uptodate 2:1.1.1-21etch1 xserver-xorg/etch uptodate 1:7.1.0-19 xserver-xorg-input-all/etch uptodate 1:7.1.0-19 xserver-xorg-input-evdev/etch uptodate 1:1.1.2-6 xserver-xorg-input-kbd/etch uptodate 1:1.1.0-4 xserver-xorg-input-mouse/etch uptodate 1:1.1.1-3 xserver-xorg-input-synaptics/etch uptodate 0.14.6-1 xserver-xorg-input-wacom/etch uptodate 0.7.4.1-5 xserver-xorg-video-vesa/etch uptodate 1:1.3.0-1 Now I tried to start X 3 different ways. - SCENARIO 1 - 1. Create ~/.xsession like so (reproduced same with .xinitrc instead, too): #!/bin/sh xsetroot -solid skyblue # tried both with and without the next line #xterm -title "Debian GNU/Linux" -ls -geometry 80x24+99+0 & # Issue this command # startx -- -logverbose SYMPTOMS: The session seems to start, then ends immediately, no particular cause that I can see. - SCENARIO 2 - 2. Have no ~/.xinitrc nor ~/.xsession (thus seemingly reliant on existing stock /etc/X11/Xsession) # Issue this command # startx -- -logverbose SYMPTOMS: Session starts a totally blank screen but it stays open. I have to kill by the usual ctrl-alt-backspace. - SCENARIO 3 - 3. Same setup as 2. above, but different command # Issue this command # startx xterm -- -logverbose SYMPTOMS: The session seems to start, then ends immediately. Afterwards I see this error message on terminal: xterm: bad command line option "xterm" This is followed by the xterm brief help message (ie, list of options). ALL 3 OF THESE HAVE IDENTICAL Xorg.0.log files. (except for the lines for timestamp and VESA virtual address) That includes both variants of scenario 1. Last log file is reproduced below. === DETAILED NOTES - /etc/X11/xorg.conf - # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # Section "Files" FontPath"/usr/share/fonts/X11/misc" FontPath"/usr/X11R6/lib/X11/fonts/misc" FontPath"/usr/share/fonts/X11/cyrillic" FontPath"/usr/X11R6/lib/X11/fonts/cyrillic" FontPath"/usr/share/fonts/X11/100dpi/:unscaled" FontPath"/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/share/fonts/X11/75dpi/:unscaled" FontPath"/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/share/fonts/X11/Type1" FontPath"/usr/X11R6/lib/X11/fonts/Type1" FontPath"/usr/share/fonts/X11/100dpi" FontPath"/usr/X11R6/lib/X11/fonts/100dpi" FontPath"/usr/share/fonts/X11/75dpi" FontPath"/usr/X11R6/lib/X11/fonts/75dpi" # path to defoma fonts FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" EndSection Section "Module" Load"i2c" Load"bitmap" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/input/mice" Option "Protocol" "ImPS/2"
Re: Surefire Xorg driver/config?
On 9/13/07, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: > On Thu, Sep 13, 2007 at 12:39:15AM -0500, Gordon Pedersen wrote: > > On 9/12/07, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: > > > On Wed, Sep 12, 2007 at 11:10:04AM -0500, Gordon Pedersen wrote: > > > > I reinstalled etch 4.0r1 from scratch. So all below refers to stable. > > ... > > Now I tried to start X 3 different ways. > > > > - SCENARIO 1 - > > 1. Create ~/.xsession like so (reproduced same with .xinitrc instead, too): > > # startx -- -logverbose > > see comments on #3 below. the '&' at the end of the xterm line above > is wrong. That will cause the X session to terminate immediately. X > will only stay up as long as the init script (.xsession, .xinitrc) is > still running. Oh, yeah, thanks for reminding me; I was too tuckered last night to remember that. > > > > > - SCENARIO 2 - > > 2. Have no ~/.xinitrc nor ~/.xsession > > (thus seemingly reliant on existing stock /etc/X11/Xsession) > > > > # Issue this command > > # startx -- -logverbose > > > > SYMPTOMS: > > Session starts a totally blank screen but it stays open. I have to kill > > by the usual ctrl-alt-backspace. > > that means X is working. just that there is nothing running in the > session (how that works, I don't know, because without a client X > shoudl die, but we'll take what we get...) I ran ps on that X session. In a nutshell, it looks like there is a default /etc/X11/xinit/xinitrc script being invoked and it starts xterm ultimately. > > > > > - SCENARIO 3 - > > 3. Same setup as 2. above, but different command > > > > # Issue this command > > # startx xterm -- -logverbose > > > > SYMPTOMS: > > The session seems to start, then ends immediately. > > Afterwards I see this error message on terminal: > > xterm: bad command line option "xterm" > > This is followed by the xterm brief help message (ie, list of options). > > > > the X session is dying because it has no client. It has no client > because xterm is bombing because it doesn't like whatever its getting > for a command line. > > So go back to #1 and make your ~/.xinitrc look *just* like this: > > xsetroot -solid skyblue > xterm > > save it and run just > > startx > > without the extra stuff. I did this (and in fact other permutations of .xinitrc) and I see the same blank screen I saw for original scenario #2 above. X is apparently running. But the screen is totally blank, and when I type, nothing shows. I kill the session using ctrl-alt-backspace. I tried also using ~/.xsession with identical contents instead of ~/.xinitrc; identical symptoms. (My keyboard is a trusty old IBM without a separate keypad so although I tried, I can't test cycling through the possible active modes.) I looked using "ps fax" and see the following while that blank screen is up (trimming some output): \_/bin/sh /usr/bin/startx \_ xinit /root/.xinitrc -- /etc/X11/xinit/xserverrc -aut[rest cut off] \_ /usr/bin/X11/X -dpi 100 -nolisten tcp \_ sh /root/.xinitrc \_ xterm \_ bash Looks okay to me, but I don't know what to look for in an obscure case like this. The sync setting happen to be displayed on this CRT when modes change. What is displayed is 48 kHz / 60 Hz These fall within acceptable limits for my monitor: H 31-115, V 50-160. Any thoughts? gp -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
X bombs, calls for /usr/bin/cpp at startup - Why? Was: Surefire Xorg driver/config?
I am top-posting the crucial error message. Context follows below, and in prior posts this thread. > are there any errors in ~/.xsession-errors? maybe there's a clue > there. sh: /usr/bin/cpp: No such file or directory What is cpp (is it same as gcc)? Why would it be referenced while starting X? Must cpp/gcc be installed simply to run X? Are there additional packages beyond what is shown below that need to be installed to support running X? Here is a list of the X-related pkgs currently installed: x11-common/etch uptodate 1:7.1.0-19 xbase-clients/etch uptodate 1:7.1.ds1-2 xbitmaps/etch uptodate 1.0.1-2 xfonts-100dpi/etch uptodate 1:1.0.0-3 xfonts-75dpi/etch uptodate 1:1.0.0-3 xfonts-base/etch uptodate 1:1.0.0-4 xfonts-encodings/etch uptodate 1:1.0.0-6 xfonts-scalable/etch uptodate 1:1.0.0-6 xfonts-utils/etch uptodate 1:1.0.1-1 xkb-data/etch uptodate 0.9-4 xserver-xorg-core/etch uptodate 2:1.1.1-21etch1 xserver-xorg/etch uptodate 1:7.1.0-19 xserver-xorg-input-all/etch uptodate 1:7.1.0-19 xserver-xorg-input-evdev/etch uptodate 1:1.1.2-6 xserver-xorg-input-kbd/etch uptodate 1:1.1.0-4 xserver-xorg-input-mouse/etch uptodate 1:1.1.1-3 xserver-xorg-input-synaptics/etch uptodate 0.14.6-1 xserver-xorg-input-wacom/etch uptodate 0.7.4.1-5 xserver-xorg-video-vesa/etch uptodate 1:1.3.0-1 xterm/etch uptodate 222-1etch2 On 9/14/07, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: > On Thu, Sep 13, 2007 at 06:05:00PM -0500, Gordon Pedersen wrote: > > On 9/13/07, Andrew Sackville-West <[EMAIL PROTECTED]> wrote: > > > On Thu, Sep 13, 2007 at 12:39:15AM -0500, Gordon Pedersen wrote: > > > > > > > > I reinstalled etch 4.0r1 from scratch. So all below refers to stable. > > > > ... > > > > Now I tried to start X 3 different ways. X is verified to be running. > > I looked using "ps fax" and see the following while that blank screen > > is up (trimming some output): > > > > \_/bin/sh /usr/bin/startx > > \_ xinit /root/.xinitrc -- /etc/X11/xinit/xserverrc -aut[rest cut off] > > \_ /usr/bin/X11/X -dpi 100 -nolisten tcp > > \_ sh /root/.xinitrc > >\_ xterm > >\_ bash > > > > Ok, wow, so X is coming up (yay) and its clients are up and > running (yay!!!) but you can't see them (bo). I assume you are > only seeing the usual grey screen, right? xsetroot is doing nothing as > well, right? is there a mouse cursor? I see no grey screen. Screen is TOTALLY blank (and black). No background anything. No mouse cursor. To remind those new to thread: this very same hardware runs X fine in an etch (when it was testing) install from late 2005. > > maybe try coming up with an xterm command line that > specifies the placement of the window someting like --geometry > 300x400+100+100 so that you are confident that the window would be > intersecting the > screen Have already tried this but retried with xterm -geometry 80x24+0+0 Same blank black screen. > > are there any errors in ~/.xsession-errors? maybe there's a clue > there. Yes, there is one error there, I missed reporting it the other night sh: /usr/bin/cpp: No such file or directory What is cpp (is it same as gcc)? Why would it be referenced while starting X? > > Also, is it possible somehow that you are getting more than one X > display running and the xterm is connecting to the wrong one? maybe > specify --display :0.0 Only one shows in ps listing so I assume only one is running. -- Gordon Pedersen [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: X bombs, calls for /usr/bin/cpp at startup - Why? Was: Surefire Xorg driver/config?
On 9/14/07, Andrew Sackville-West <[EMAIL PROTECTED]> wrote:
> On Fri, Sep 14, 2007 at 12:35:20PM -0500, Gordon Pedersen wrote:
> > > are there any errors in ~/.xsession-errors?
> > sh: /usr/bin/cpp: No such file or directory
> apt-cache rdepends cpp
> shows, among other things, xbase-clients as depending on cpp.
>
>
> so long as you used an apt frontend to install the X stuff you should
> already have everything you need. But apparently you don't.
> I don't see just the meta package - xorg, which you might want to
> install, to make sure you bring in all the dependencies.
I did not install xorg package earlier - I began by installing
xserver-xorg-video-vesa, then added font and xterm packages.
Installed the xorg meta-pkg now using apt-get - it caught several
extraneous dependencies.
The /usr/bin/cpp error message is gone. But other symptoms are
completely unchanged: black screen, totally blank, no cursor, etc.
Detail on the library cross-checks you suggested at bottom. It looks
to my untrained eye as if all the library packages needed by
xbase-clients are now installed.
Is it a problem with the dependency checks, in your opinion, that
"xorg" package is not listed as a dependency for xserver-xorg-core or
its dependencies (as far as I can see)?
Do you know the "standard" way to install X if one chooses not to
check the box for "Desktop Environment" during installlation? I
wasn't trying to cause problems, merely to install X (without having
to eliminate an unwanted desktop later on). :-)
gp
=
Library cross-check detail:
>
> also look at:
>
> apt-cache depends xbase-clients | awk '/Depends/ { print $2 }' | xargs dpkg -l
superuser pan:/mnt/hda11/oldpan/home/gp $ apt-cache depends
xbase-clients |awk '/Depends/ {print $2}'|xargs dpkg -l
No packages found matching .
(But: lists libgl1-mesa-gl below - I think it provides libgl1)
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name VersionDescription
+++-==-==-
ii libc6 2.3.6.ds1-13et GNU C Library: Shared libraries
ii libfontconfig1 2.4.2-1.2 generic font configuration library - runtime
ii libfreetype6 2.2.1-5+etch1 FreeType 2 font engine, shared library files
ii libfs6 1.0.0-4X11 Font Services library
ii libgl1-mesa-gl 6.5.1-0.6 A free implementation of the OpenGL API -- G
ii libice61.0.1-2X11 Inter-Client Exchange library
ii libpng12-0 1.2.15~beta5-1 PNG library - runtime
ii libsm6 1.0.1-3X11 Session Management library
ii libx11-6 1.0.3-7X11 client-side library
ii libxau61.0.1-2X11 authorisation library
ii libxaw71.0.2-4X11 Athena Widget library
ii libxcursor11.1.7-4X cursor management library
ii libxext6 1.0.1-2X11 miscellaneous extension library
ii libxft22.1.8.2-8 FreeType-based font drawing library for X
ii libxi6 1.0.1-4X11 Input extension library
ii libxkbfile11.0.3-2X11 keyboard file manipulation library
ii libxmu61.0.2-2X11 miscellaneous utility library
ii libxmuu1 1.0.2-2X11 miscellaneous micro-utility library
ii libxrandr2 1.1.0.2-5 X11 RandR extension library
ii libxrender10.9.1-3X Rendering Extension client library
ii libxss11.1.0-1X11 Screen Saver extension library
ii libxt6 1.0.2-2X11 toolkit intrinsics library
ii libxtrap6 1.0.0-4X11 event trapping extension library
ii libxtst6 1.0.1-5X11 Testing -- Resource extension library
ii libxv1 1.0.2-1X11 Video extension library
ii libxxf86dga1 1.0.1-2X11 Direct Graphics Access extension library
ii libxxf86vm11.0.1-2X11 XFree86 video mode extension library
ii x11-common 7.1.0-19 X Window System (X.Org) infrastructure
ii zlib1g 1.2.3-13 compression library - runtime
>
> and make sure its all 'ii' installed. note this is not a dependable
> one-liner as the depends listing is not properly parsed by this, but
> it helps anyway.
I eliminated "libgl1" from the list produced above by "apt-cache
depends xbase-clients" and checked against the list produced by
apt-show-versions.
It looks as if all those libraries are installed. It looks as if only
"libgl1" was a complex dependency of xbase-clients. I used the other
package names exactly as produced by the awk hack you suggested.
Detail shown below.
superuser pan:/mnt/hda11/sync/newpan $ apt-show-vers
Re: X bombs, calls for /usr/bin/cpp at startup - Why? Was: Surefire Xorg driver/config?
On 9/14/07, Andrew Sackville-West <[EMAIL PROTECTED]> wrote:
> On Fri, Sep 14, 2007 at 05:07:17PM -0500, Gordon Pedersen wrote:
> > On 9/14/07, Andrew Sackville-West <[EMAIL PROTECTED]> wrote:
> > > On Fri, Sep 14, 2007 at 12:35:20PM -0500, Gordon Pedersen wrote:
> > I did not install xorg package earlier - I began by installing
> > xserver-xorg-video-vesa, then added font and xterm packages.
> > Installed the xorg meta-pkg now using apt-get - it caught several
> > extraneous dependencies.
> >
> > The /usr/bin/cpp error message is gone. But other symptoms are
> > completely unchanged: black screen, totally blank, no cursor, etc.
>
> Based on the info below, you should be working. I'm sorry, I don't
> know what else to tell you. Oh, one mor thing -- try a different
> client besides xterm -- anything will do.
>
> sorry. I've exhausted my knowledge on this.
>
> A
Thanks kindly for all the careful attention that you lavished on this
problem, Andrew.
I have learned much about X installs and troubleshooting and tweaking
the current xorg, and that's worth as much to me as simply getting it
to work.
And if I stumble across a fix, I'll report it to the list.
Gordon
>
> >
> > Detail on the library cross-checks you suggested at bottom. It looks
> > to my untrained eye as if all the library packages needed by
> > xbase-clients are now installed.
> >
> > Is it a problem with the dependency checks, in your opinion, that
> > "xorg" package is not listed as a dependency for xserver-xorg-core or
> > its dependencies (as far as I can see)?
> >
> > Do you know the "standard" way to install X if one chooses not to
> > check the box for "Desktop Environment" during installlation? I
> > wasn't trying to cause problems, merely to install X (without having
> > to eliminate an unwanted desktop later on). :-)
> >
> > gp
> >
> > =
> > Library cross-check detail:
> >
> > >
> > > also look at:
> > >
> > > apt-cache depends xbase-clients | awk '/Depends/ { print $2 }' | xargs
> > > dpkg -l
> >
> > superuser pan:/mnt/hda11/oldpan/home/gp $ apt-cache depends
> > xbase-clients |awk '/Depends/ {print $2}'|xargs dpkg -l
> >
> > No packages found matching .
> > (But: lists libgl1-mesa-gl below - I think it provides libgl1)
> >
> > Desired=Unknown/Install/Remove/Purge/Hold
> > | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
> > |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
> > uppercase=bad)
> > ||/ Name VersionDescription
> > +++-==-==-
> > ii libc6 2.3.6.ds1-13et GNU C Library: Shared libraries
> > ii libfontconfig1 2.4.2-1.2 generic font configuration library -
> > runtime
> > ii libfreetype6 2.2.1-5+etch1 FreeType 2 font engine, shared library
> > files
> > ii libfs6 1.0.0-4X11 Font Services library
> > ii libgl1-mesa-gl 6.5.1-0.6 A free implementation of the OpenGL API
> > -- G
> > ii libice61.0.1-2X11 Inter-Client Exchange library
> > ii libpng12-0 1.2.15~beta5-1 PNG library - runtime
> > ii libsm6 1.0.1-3X11 Session Management library
> > ii libx11-6 1.0.3-7X11 client-side library
> > ii libxau61.0.1-2X11 authorisation library
> > ii libxaw71.0.2-4X11 Athena Widget library
> > ii libxcursor11.1.7-4X cursor management library
> > ii libxext6 1.0.1-2X11 miscellaneous extension library
> > ii libxft22.1.8.2-8 FreeType-based font drawing library for X
> > ii libxi6 1.0.1-4X11 Input extension library
> > ii libxkbfile11.0.3-2X11 keyboard file manipulation library
> > ii libxmu61.0.2-2X11 miscellaneous utility library
> > ii libxmuu1 1.0.2-2X11 miscellaneous micro-utility library
> > ii libxrandr2 1.1.0.2-5 X11 RandR extension library
> > ii libxrender10.9.1-3X Rendering Extension client library
> > ii libxss11.1.0-1X11 Screen Saver extension library
> > ii libxt6 1.0.2-2X11 toolkit intrinsics library
> > ii libxtrap6 1.0.0-4X11 event trapping extension library
> > ii libxtst6 1.0.1-5X11 Testing -- Resource extension library
> > ii libxv1 1.0.2-1
Re: trouble installing ruby in etch
On 10/19/07, Mumia W.. <[EMAIL PROTECTED]> wrote: > On 10/18/2007 10:47 PM, Gordon Pedersen wrote: > > [...] > > ...except, why were testing packages favored over stable? > > By default, apt-get wants to install later versions of packages, so if > it sees both libc6 2.6.1 and libc6 2.3.6, apt-get will prefer the later > version, 2.6.1. Thanks. I guess apt doesn't sense that the system is "stable" - I wonder if there is a way to tell it so? Maybe by pinning "*" to stable, somehow? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Best way to install a few testing pkgs on stable system
On 10/19/07, Amit Uttamchandani <[EMAIL PROTECTED]> wrote: > I was in a similar situation as you. I installed the stable Debian etch and I > required a few new packages. The best way to go about this is to compile them > from source. It can get quite a bit tedious at times but here are a few tips: Will do so in a pinch, but more of a mind to learn how to creatively use the Debian packages system. (Have done source installs but like packages, and want to find a smart way to mix testing and/or unstable w/stable.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Best way to install a few testing pkgs on stable system
On 10/19/07, Adrian Levi <[EMAIL PROTECTED]> wrote: > On 19/10/2007, Gordon Pedersen <[EMAIL PROTECTED]> wrote: > > Running an etch system I nonetheless may want to install a testing > > package or two. > Do you know of backports.org? would that provide the packages you require? Yes, just heard about them, they're great. Don't have everything - witness: all of ruby I need but rubygems. -- Gordon Pedersen [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: trouble installing ruby in etch
On 10/18/07, Ron Johnson <[EMAIL PROTECTED]> wrote: > > > > Is it possible to install ruby wholly within debian stable at this > > moment in time? > > > > When I try, it appears that the following dependency chain > > > > ruby -> ruby1.8 -> libruby1.8 -> libc6 (>= 2.3.6-6) [i386] > > > > leads apt-get to want to install packages from the "testing" dist, > > including some major C library-related pkgs (see below). I'm worried > > about allowing that to happen, afraid system will start losing > > integrity, etc. > > > > It decides to remove stable package libc6 (2.3.6.ds1-13etch2), then > > goes to get libc6 (2.6.1-1+b1 Debian:testing) and continues on with > > testing pkgs. > > > > I can't decipher the meaning of the stable libc6 package version > > (2.3.6.ds1-13etch2). > > > > Is it a legitimate dependency for libruby1.8? > > > > If so, where do I look to find out how to install libruby1.8 in the > > face of apt-get thinking it has a missing dependency? > > > > If not, what are my options? > > You seem to be running a mixed system. Not good. I stand humbled. I just took the "testing" lines from /etc/apt/sources.list and now the dependencies are calculated differently. I see now looking more closely that libruby1.8 has different subversions in stable vs testing, and they depend on different versions of libc6. I had thought that a package named "libruby1.8" would point to the same underlying code in both. That explains why so many testing libraries were pulled in ...except, why were testing packages favored over stable? That is interesting but not crucial to answer. For me a more important and useful question is this: if I feel the need to bring in one or a few testing packages, what is a good procedure to follow? I'll start a new thread with appropriate subject for that. Gordon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
trouble installing ruby in etch
I'm running a fairly fresh install of etch (4.0r1). Is it possible to install ruby wholly within debian stable at this moment in time? When I try, it appears that the following dependency chain ruby -> ruby1.8 -> libruby1.8 -> libc6 (>= 2.3.6-6) [i386] leads apt-get to want to install packages from the "testing" dist, including some major C library-related pkgs (see below). I'm worried about allowing that to happen, afraid system will start losing integrity, etc. It decides to remove stable package libc6 (2.3.6.ds1-13etch2), then goes to get libc6 (2.6.1-1+b1 Debian:testing) and continues on with testing pkgs. I can't decipher the meaning of the stable libc6 package version (2.3.6.ds1-13etch2). Is it a legitimate dependency for libruby1.8? If so, where do I look to find out how to install libruby1.8 in the face of apt-get thinking it has a missing dependency? If not, what are my options? Here is what a simulated apt-get install shows: $ apt-get install libruby1.8 -s Reading package lists... Done Building dependency tree... Done The following extra packages will be installed: gcc-4.2-base libc6 libc6-i686 libmudflap0 libncurses5 linux-libc-dev locales tzdata zlib1g Suggested packages: glibc-doc The following packages will be REMOVED: libc6-dev libmudflap0-dev linux-kernel-headers The following NEW packages will be installed: gcc-4.2-base libruby1.8 linux-libc-dev The following packages will be upgraded: libc6 libc6-i686 libmudflap0 libncurses5 locales tzdata zlib1g 7 upgraded, 3 newly installed, 3 to remove and 352 not upgraded. Remv libmudflap0-dev [4.1.1-21] Remv libc6-dev [2.3.6.ds1-13etch2] Remv linux-kernel-headers [2.6.18-7] Inst tzdata [2007b-1] (2007h-1 Debian:testing) Conf tzdata (2007h-1 Debian:testing) Inst locales [2.3.6.ds1-13etch2] (2.6.1-1 Debian:testing) [] Inst libc6 [2.3.6.ds1-13etch2] (2.6.1-1+b1 Debian:testing) [libc6-i686 on libc6] [libc6-i686 ] Conf libc6 (2.6.1-1+b1 Debian:testing) [libc6-i686 ] Inst libc6-i686 [2.3.6.ds1-13etch2] (2.6.1-1+b1 Debian:testing) Inst libncurses5 [5.5-5] (5.6+20070908-1 Debian:testing) Conf libncurses5 (5.6+20070908-1 Debian:testing) Inst zlib1g [1:1.2.3-13] (1:1.2.3.3.dfsg-6 Debian:testing) Conf zlib1g (1:1.2.3.3.dfsg-6 Debian:testing) Inst gcc-4.2-base (4.2.1-4 Debian:testing) Inst libmudflap0 [4.1.1-21] (4.2.1-4 Debian:testing) Inst libruby1.8 (1.8.6.36-3 Debian:testing) Inst linux-libc-dev (2.6.22-4 Debian:testing) Conf locales (2.6.1-1 Debian:testing) Conf libc6-i686 (2.6.1-1+b1 Debian:testing) Conf gcc-4.2-base (4.2.1-4 Debian:testing) Conf libmudflap0 (4.2.1-4 Debian:testing) Conf libruby1.8 (1.8.6.36-3 Debian:testing) Conf linux-libc-dev (2.6.22-4 Debian:testing) -- Gordon Pedersen [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Best way to install a few testing pkgs on stable system
Running an etch system I nonetheless may want to install a testing package or two. If I use pinning, I have a clue about how to go about it, and have seen a debian wiki page about that. But I really could use a more general education on how to safely mix a few testing pkgs into a stable system. If there is a safe way in some cases I'd like to learn more about it. (I doubt it's safe in all cases, based on my recent need to abandon installing rubygems from testing into my etch system). Does anyone have suggested methods or reading? -- Gordon Pedersen [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: trouble installing ruby in etch
On 10/19/07, Mumia W.. <[EMAIL PROTECTED]> wrote: > On 10/19/2007 10:45 AM, Gordon Pedersen wrote: > > On 10/19/07, Mumia W.. <[EMAIL PROTECTED]> wrote: > >> On 10/18/2007 10:47 PM, Gordon Pedersen wrote: > >>> [...] > >>> ...except, why were testing packages favored over stable? > >> By default, apt-get wants to install later versions of packages, so if > >> it sees both libc6 2.6.1 and libc6 2.3.6, apt-get will prefer the later > >> version, 2.6.1. > > > > Thanks. I guess apt doesn't sense that the system is "stable" - I > > wonder if there is a way to tell it so? Maybe by pinning "*" to > > stable, somehow? > > Yes. Read "man apt_preferences" to find out how to pin packages and > distributions. Thank you. It's a lot to digest, but it is exactly focussed on what I'm trying to do. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
error starting java .jar app - classpath issue?
This is likely a very simple issue. I've never tried to run a java .jar library on debian before. I wonder if it may just be a matter of learning how to correctly setting the CLASSPATH before issuing the java command on .jar libraries held in /usr/share/java/. I could not find any clear guidance about the usual CLASSPATH practice on debian. For all commands discussed below, no CLASSPATH variable has been defined. (I run sarge. Java is from blackdown j2re1.4 and j2sdk1.4. Installed without a hitch.) App in question is a timekeeper program. See http://www.taubler.com/timebox/. No errors if I switch to the .jar file directory and issue this command: $ java -jar tt.jar But if if try either of the following commands from an outside directory, the errors shown below commands appear: $ java -jar /usr/share/java/tt.jar $ java -classpath /usr/share/java/tt.jar -jar /usr/share/java/tt.jar Exception in thread "main" java.lang.NullPointerException at javax.swing.ImageIcon.(ImageIcon.java:161) at com.taubler.timebox.submit.SubmitExtensionWidget.(SubmitExtensionWidget.java:16) at com.taubler.timebox.submit.SubmitManager.(SubmitManager.java:52) at com.taubler.timebox.TimeTracker.(TimeTracker.java:54) at com.taubler.timebox.TimeTracker.main(TimeTracker.java:1115) Thanks. Gordon -- Gordon Pedersen St Paul, Minnesota, USA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
