Re: etch upgrade problem
On Thu, Apr 12, 2007 at 07:38:49PM -0400, Douglas Allan Tutty wrote: On Thu, Apr 12, 2007 at 06:21:34PM -0500, Seth Goodman wrote: Andrei Popescu mailto:[EMAIL PROTECTED] wrote on Tuesday, April 10, 2007 10:35 AM -0500: I am curious whether some debconf action, or dependencies in the deb files, could have warned the user? Prior to a new release, I wonder if there should be a security-update to apt that issues a notice to all debian users who use apt, warning them about a pending release and to prepare such things as sources.list so that they don't accidentally upgrade without reading the release notes. It sounds doable, but you have to do it as a package which only contains the news as debconf messages. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: etch upgrade problem
On Mon, Apr 30, 2007 at 08:23:27PM +0300, Andrei Popescu wrote: On Thu, Apr 12, 2007 at 07:38:49PM -0400, Douglas Allan Tutty wrote: On Thu, Apr 12, 2007 at 06:21:34PM -0500, Seth Goodman wrote: Andrei Popescu mailto:[EMAIL PROTECTED] wrote on Tuesday, April 10, 2007 10:35 AM -0500: I am curious whether some debconf action, or dependencies in the deb files, could have warned the user? Prior to a new release, I wonder if there should be a security-update to apt that issues a notice to all debian users who use apt, warning them about a pending release and to prepare such things as sources.list so that they don't accidentally upgrade without reading the release notes. It sounds doable, but you have to do it as a package which only contains the news as debconf messages. If you want people to actually install it, it should probably be part of a required package or a dependancy of that. For example, the news package could be called critical-news and be required by base-files (since its priority is 'required'). Taking this recent Sarg Etch transition as a template, under Sarge, when Etch freezes it could be updated to provide notice of an upcoming release with pointers e.g. re sources.list. When Etch is released, Sarge's critical-news could be updated (via the security.debian.org repository) to inform users (via debconf with a critical severity so that they get it) that their Sarge installation is now old-stable, and provide the current release notes (in /usr/share/doc/critical-news). Etch's critical-news could be the same as the last Sarge version, until Lenny freezes, when the pattern repeats itself. This would also provide a good mechanism to in effect email all debian users (or at least administrators) should that ever be needed, more reliably than hoping that everyone subscribes to the announce list. The package maintainers for this should probably be the people who write the release notes. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: etch upgrade problem
Andrei Popescu mailto:[EMAIL PROTECTED] wrote on Tuesday, April 10, 2007 10:35 AM -0500: Seth Goodman [EMAIL PROTECTED] wrote: In another thread, someone suggested dpkg-reconfigure udev for other hardware detection problems, so I tried it. That refuses to run because it wants a more recent kernel. Missed this the first time. What kernel are you running and what version of udev? If you are still running the sarge kernel then you should upgrade (but read the release notes first). Installing initrd-tools and then upgrading the kernel to 2.6.18 fixed the mouse and vga detection problems with X, so gnome runs. I may decide to do a clean install of etch when I find the time, but at least I have a desktop. Reading release notes is always an excellent idea, so we could safely label this problem as PEBKAC. OTOH, my setup was within the envelope for Debian stable, so the same will probably happen to other casual users. I also suspect it's avoidable. The setup that led to this upgrade problem was: - Debian stable installed as desktop system plus server - all package management done through Synaptic - repositories pointed to stable, not Sarge - Gnome screen saver active When the Etch release appeared, Synaptic offered to upgrade all the packages just as I expected after seeing the release announcement on the list. What I also expected was that Synaptic would either upgrade/install/remove packages in an appropriate order, or tell me that it couldn't. After all, this was a transition from pure stable to pure stable, nothing out of the ordinary. Instead, it apparently removed some of the Sarge hardware detection packages and installed udev without requiring a kernel upgrade. It also replaced X while X was running, causing the (standard Gnome) screensaver to no longer recognize passwords. I am curious whether some debconf action, or dependencies in the deb files, could have warned the user? -- Seth Goodman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: etch upgrade problem
On Thu, Apr 12, 2007 at 06:21:34PM -0500, Seth Goodman wrote: Andrei Popescu mailto:[EMAIL PROTECTED] wrote on Tuesday, April 10, 2007 10:35 AM -0500: I am curious whether some debconf action, or dependencies in the deb files, could have warned the user? Prior to a new release, I wonder if there should be a security-update to apt that issues a notice to all debian users who use apt, warning them about a pending release and to prepare such things as sources.list so that they don't accidentally upgrade without reading the release notes. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: etch upgrade problem
Seth Goodman [EMAIL PROTECTED] wrote: Fatal server error: failed to initialize core devices ^^^ X cannot find your mouse. Try another device instead of /dev/psaux. I have /dev/input/mice Same result. Have a look for errors in dmesg. I have this: ~# dmesg | grep mice mice: PS/2 mouse device common for all mice Regards, Andrei P.S. I have a feeling this is rather related to udev, modules, ... Did you try using a different mouse? -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: PGP signature
RE: etch upgrade problem
Andrei Popescu mailto:[EMAIL PROTECTED] wrote on Tuesday, April 10, 2007 2:54 AM -0500: Seth Goodman [EMAIL PROTECTED] wrote: Fatal server error: failed to initialize core devices ^^^ X cannot find your mouse. Try another device instead of /dev/psaux. I have /dev/input/mice Same result. Have a look for errors in dmesg. I have this: ~# dmesg | grep mice mice: PS/2 mouse device common for all mice No mouse errors in dmesg. In fact, here is the mouse detection line: input: ImPS/2 Generic Wheel Mouse on isa0060/serio1 The mouse is in fact an intellimouse PS/2. The terminal interface can use the mouse (aptitude, for example) but X doesn't find it, even though xserver-xorg-input-mouse is installed. X is also unable to install the savage module for my vga card, even though the terminal interface can use the card and xserver-xorg-video-savage is installed. My apt sources list points to stable, not etch (which is how I got here through Synaptic). That shouldn't be an issue, right? P.S. I have a feeling this is rather related to udev, modules, ... Did you try using a different mouse? No, I haven't, it's the only non-USB mouse I have left. This is the same PS/2 mouse that Sarge detected properly on this same hardware. In fact, all the hardware is the same as for my last Sarge install. In another thread, someone suggested dpkg-reconfigure udev for other hardware detection problems, so I tried it. That refuses to run because it wants a more recent kernel. -- Seth Goodman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: etch upgrade problem
Seth Goodman [EMAIL PROTECTED] wrote: Andrei Popescu mailto:[EMAIL PROTECTED] wrote on Tuesday, April 10, 2007 2:54 AM -0500: Seth Goodman [EMAIL PROTECTED] wrote: Fatal server error: failed to initialize core devices ^^^ X cannot find your mouse. Try another device instead of /dev/psaux. I have /dev/input/mice Same result. Have a look for errors in dmesg. I have this: ~# dmesg | grep mice mice: PS/2 mouse device common for all mice No mouse errors in dmesg. In fact, here is the mouse detection line: input: ImPS/2 Generic Wheel Mouse on isa0060/serio1 The mouse is in fact an intellimouse PS/2. The terminal interface can use the mouse (aptitude, for example) but X doesn't find it, even though xserver-xorg-input-mouse is installed. Are you using gpm? IIRC the xorg.conf must be setup differently if you use gpm. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: PGP signature
RE: etch upgrade problem
Andrei Popescu wrote on Tuesday, April 10, 2007 9:05 AM -0500: Are you using gpm? IIRC the xorg.conf must be setup differently if you use gpm. gpm package is not installed. -- Seth Goodman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: etch upgrade problem
Seth Goodman [EMAIL PROTECTED] wrote: In another thread, someone suggested dpkg-reconfigure udev for other hardware detection problems, so I tried it. That refuses to run because it wants a more recent kernel. Missed this the first time. What kernel are you running and what version of udev? If you are still running the sarge kernel then you should upgrade (but read the release notes first). Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: PGP signature
RE: etch upgrade problem
Andrei Popescu mailto:[EMAIL PROTECTED] wrote on Tuesday, April 10, 2007 10:35 AM -0500: Seth Goodman [EMAIL PROTECTED] wrote: In another thread, someone suggested dpkg-reconfigure udev for other hardware detection problems, so I tried it. That refuses to run because it wants a more recent kernel. Missed this the first time. What kernel are you running and what version of udev? If you are still running the sarge kernel then you should upgrade (but read the release notes first). It's the Sarge kernel, 2.6.8.3-686, specifically 2.6.8-16sarge6. I can understand that some people may wish to upgrade to etch without replacing their kernel, but I'm surprised that synaptic didn't recommend this as part of the normal upgrade. OTOH, it's possible that it did, but kernel replacement failed as a consequence of my killing the screensaver process that was blocking completion of the upgrade. If so, the primary failure in all of this, in addition to my failing to read the release notes first, may be something in the Xorg transition that resulted in the screensaver no longer accepting the password. Since others have reported successful upgrades to etch with X running, that may be the key. I'm pretty sure that everything on this system was from Sarge repositories. -- Seth Goodman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: etch upgrade problem
Seth Goodman ha scritto: I've started an upgrade from Sarge to Etch through the Synaptic Package all on the terminal display behind the screensaver :) Have you tried to kill xscreensaver after remotely loggin in? gc :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: etch upgrade problem
On Mon, Apr 09, 2007 at 09:41:06 -0500, Seth Goodman wrote: I've started an upgrade from Sarge to Etch through the Synaptic Package manager under Gnome. The package repositories all look for stable. I selected the normal level of questions from the terminal interface. It was going well, but now XScreenSaver activated and it does not accept my password, so I can't get back to the ongoing update. Running Putty from a nearby windows box does let me log in as that user, so PAM still works. Directly logging in as root remotely (to my surprise, SSH allowed this) and running who does show the user running Synaptic, but how do I get back to the running instance of Synaptic? I'm not sure what caused the problem, but I'm thinking of either the change in graphics environment or my choosing to select the keyboard rather than telling it not to touch the previous selection. If I select new login at the screensaver prompt, that also fails trying to load various font packages, so I can't determine if the keyboard map is proper. If I hit the caps lock key, the screensaver does suggest I check for caps lock, so the keyboard works at least a little. Some additional info. Before the screensaver came on, I did notice a long series of warnings concerning what looked like a failure to set the three locale settings for PERL. These same warnings repeated for quite a few packages. I think my settings were both US-English and UK-English for language, locale_all unset and I forget the third variable. It's all on the terminal display behind the screensaver :) You can try to kill the screen saver and/or the screen lock. Log in as your normal user via ssh (or with CTRL-ALT-F1 etc. if that still works) and run ps ux This will list all your user's processes. There should be one with screensaver or lock in its name/command. You can terminate a process with the kill command, specifying its PID (the number in the second column of the ps ux output) as the argument. However, if I kill the screen lock process on my KDE system then the whole X session is terminated; I assume this is a security measure. Therefore you should only try this if you are sure that synaptic has finished whatever it was doing, to avoid bringing your system in an even more inconsistent state. If you cannot kill the screen lock without bringing down the X session then we can tell you how to complete the upgrade and then resurrect your X from the command line. -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: etch upgrade problem (SOLVED)
gianca wrote on Monday, April 09, 2007 10:04 AM -0500: Have you tried to kill xscreensaver after remotely loggin in? Florian Kulzer wrote on Monday, April 09, 2007 10:41 AM -0500: You can try to kill the screen saver and/or the screen lock. However, if I kill the screen lock process on my KDE system then the whole X session is terminated; I assume this is a security measure. Therefore you should only try this if you are sure that synaptic has finished whatever it was doing, to avoid bringing your system in an even more inconsistent state. Leaving things in a partly upgraded and inconsistent state was what I was afraid of, and Synaptic was definitely not done. However, I saw gianca's response before yours so I logged in (as root), killed the screensaver process and fortunately it worked :) I don't know if the difference was due to gnome vs. kde or killing the screensaver process as root, but I'm glad it worked. Thanks for the help to both gianca and Florian. I'll check out the screensaver after rebooting at the end of the upgrade to check see if it works properly. Now on to the PERL locale variable warnings. These warnings are all similar to: perl: warning: Setting locale failed. perl: warning: please check that your locale settings: LANGUAGE = en_US:en_GB:en, LC_ALL = (unset), LANG = en_US are supported and installed on your system. perl: warning: Falling back to the standard locale (C). These appear to be generally harmless, but it might be a good time to fix the locale so this doesn't continue to happen. One solution I read about was dpkg-reconfigure locales, but I wanted to ask here before I go off and break things further :) As I recall, these locale errors also occurred during the Sarge install long ago, so it is more likely a Sarge problem than an Etch problem. -- Seth Goodman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: etch upgrade problem
On Mon, Apr 09, 2007 at 09:41:06AM -0500, Seth Goodman wrote: I've started an upgrade from Sarge to Etch through the Synaptic Package manager under Gnome. The package repositories all look for stable. I selected the normal level of questions from the terminal interface. Please note that the release notes that cover the upgrade say _not_ to try it via X, to use aptitude from the command line. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: etch upgrade problem
On Monday 09 April 2007 19:04, Douglas Allan Tutty wrote: On Mon, Apr 09, 2007 at 09:41:06AM -0500, Seth Goodman wrote: I've started an upgrade from Sarge to Etch through the Synaptic Package manager under Gnome. The package repositories all look for stable. I selected the normal level of questions from the terminal interface. Please note that the release notes that cover the upgrade say _not_ to try it via X, to use aptitude from the command line. Doug. Perhaps it's not a good idea upgrading while X is running, but the only problems I've ever had were when upgrading from Woody to Sarge. I seem to remember X being shutdown, and having to continue the upgrade from the command line. I've recently upgraded a Sarge install to Etch with X running, and including the transition from Xfree 86 to Xorg, and have had no problems, and whenever there have been X updates to Etch, I've just let them go ahead with the Xserver running with no problems. Perhaps I've just got away with it, or maybe the X updates arn't applied until I next reboot the machine. Anyway Debian rocks, especially with version upgrades. I also have Fedora Core versions on my 2 machines, but have never upgraded from one version to the next. I have seen so many problems with this on the Fedora list. Upgrading from FC5 to FC6, and loads of FC5 packages being left on the machine. I've always done fresh installs of the latest Fedora version, but Debian seems to handle the version upgrades a lot better. I'm sending this from Kmail on FC2, but have Etch running on the other machine. Not the Sarge to Etch upgrade I've recently done, but the Woody to Sarge, then kept on testing, which moved up to Etch when Sarge went stable. This recently has had the sources changed to point to Etch rather than testing when I saw that Etch was soon to become stable. Now that Etch is stable I think I will put this Etch install back on testing, and see how Lenny goes. I'm not so close to the edge that I'm going to try Sid though. lol. So currently apart from Fedora FC1,2,3,4,5, and 6, Slackware 10.0, Gentoo (which on dialup I havn't updated for ages, as it takes forever), and not forgetting Kubuntu, I have 1 Sarge install, 1 Etch install, and 1 Etch install which I am about to put back on testing. Hope that doesn't mess up all the music apps I have installed on it!! Nigel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: etch upgrade problem
On Monday, 09.04.2007 at 19:55 +0200, Nigel Henry wrote: Perhaps it's not a good idea upgrading while X is running, but the only problems I've ever had were when upgrading from Woody to Sarge. I seem to remember X being shutdown, and having to continue the upgrade from the command line. I believe the recommended approach is to run the upgrade/dist-upgrade in 'screen', so that any network or X-related problem will not kill the upgrade process. Haven't upgraded my Sarge systems yet, but that's the way *I'm* planning to do it. Dave. -- Please don't CC me on list messages! ... Dave Ewart - [EMAIL PROTECTED] - jabber: [EMAIL PROTECTED] All email from me is now digitally signed, key from http://www.sungate.co.uk/ Fingerprint: AEC5 9360 0A35 7F66 66E9 82E4 9E10 6769 CD28 DA92 signature.asc Description: Digital signature
RE: etch upgrade problem
Well, a bit premature on solved status. The upgrade from Sarge to Etch did complete after killing the screensaver process, but it did not leave the system in a good state. Minor problems include Postgre failing on boot, as well as a mini-DNS server that I don't believe was in Sarge failing to start, but the main problem is that X is inoperable. Looking at the wiki at http://wiki.debian.org/Xorg69To7, some of the common problems are present. xserver-org does appear to be there, so at least that's not a problem. After removing various unused packages, /usr/X11R6/bin contains only a lib directory with a few fonts at the bottom of the tree and the expected symlink from /usr/X11R6/bin to /usr/bin. Running dpkg-reconfigure xserver-xorg, with either autodetection or without, so far has not resulted in a working X configuration. On boot, X doesn't start and the error file makes it sound like it is unable to use ACPI or APM through the BIOS. The hardware detection worked perfectly on Sarge for everything now in this box except for the VGA card, and the problem there was only setting the resolution. I apologize in advance for the long log files included here. I'm not sure how to best do this without abusing the bandwidth of those on dial-up lines. Here's the output of lspci: 00:00.0 Host bridge: Intel Corporation 82820 820 (Camino) Chipset Host Bridge (MCH) (rev 03) 00:01.0 PCI bridge: Intel Corporation 82820 820 (Camino) Chipset AGP Bridge (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801AA PCI Bridge (rev 02) 00:1f.0 ISA bridge: Intel Corporation 82801AA ISA Bridge (LPC) (rev 02) 00:1f.1 IDE interface: Intel Corporation 82801AA IDE (rev 02) 00:1f.2 USB Controller: Intel Corporation 82801AA USB (rev 02) 00:1f.3 SMBus: Intel Corporation 82801AA SMBus (rev 02) 00:1f.5 Multimedia audio controller: Intel Corporation 82801AA AC'97 Audio (rev 02) 01:00.0 VGA compatible controller: S3 Inc. Savage 4 (rev 03) 02:00.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 08) Running dpkg-reconfigure xserver-xorg with autodetection gives the following xorg.conf: cray4:~# cat /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 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 Loadbitmap Loaddbe Loadddc Loaddri Loadextmod Loadfreetype Loadglx Loadint10 Loadrecord Loadvbe 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/psaux Option Protocol PS/2 Option Emulate3Buttons true EndSection Section Device Identifier S3 Inc. Savage 4 Driver savage BusID PCI:1:0:0 Option UseFBDev true EndSection Section Monitor Identifier Generic Monitor Option DPMS HorizSync 28-49 VertRefresh 43-72 EndSection Section Screen Identifier Default Screen Device S3 Inc. Savage 4 Monitor Generic Monitor
Re: etch upgrade problem
On Mon, Apr 09, 2007 at 03:46:21PM -0500, Seth Goodman wrote: Well, a bit premature on solved status. The upgrade from Sarge to Etch did complete after killing the screensaver process, but it did not leave the system in a good state. Minor problems include Postgre failing on boot, as well as a mini-DNS server that I don't believe was in Sarge failing to start, but the main problem is that X is inoperable. This may sound stupid: if you can, purge as much as possible of X Windows. Then apt-get / aptitude install xorg xserver-xorg discover x-window-system That should give you a base of the new packages to go on. If it still doesn't work, dexconf dpkg-reconfigure xserver-xorg -plow should help. plow asks _all_ the questions again, not just those at high priority. HTH, Andy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: etch upgrade problem
Matt Richardson wrote on Monday, April 09, 2007 4:39 PM -0500: I had the same problem when I upgraded sarge to etch some time ago. The solution was to add psmouse to /etc/modules. Check out lsmod and see if it's listed already, but I'd guess not. cray4:~# lsmod Module Size Used by ... psmouse20360 0 ... cray4:~# cat /etc/modules ... ide-cd ide-disk ide-generic psmouse -- Seth Goodman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: etch upgrade problem
Seth Goodman [EMAIL PROTECTED] wrote:
packages, /usr/X11R6/bin contains only a lib directory with a few
^
I guess you mean /usr/X11R6/
Section InputDevice
Identifier Configured Mouse
Driver mouse
Option CorePointer
Option Device/dev/psaux
Option Protocol PS/2
Option Emulate3Buttons true
EndSection
I think your problem is in this section, see below.
(EE) xf86OpenSerial: Cannot open device /dev/psaux
No such device.
(EE) Configured Mouse: cannot open input device
(EE) PreInit failed for input device Configured Mouse
(II) UnloadModule: mouse
(WW) No core pointer registered
(II) XINPUT: Adding extended input device Generic Keyboard (type:
KEYBOARD)
xkb_keycodes { include xfree86+aliases(qwerty) };
xkb_types{ include complete };
xkb_compatibility{ include complete };
xkb_symbols { include pc(pc105)+us };
xkb_geometry { include pc(pc104) };
No core pointer
Fatal server error:
failed to initialize core devices
^^^
X cannot find your mouse. Try another device instead of /dev/psaux. I
have /dev/input/mice
HTH,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
signature.asc
Description: PGP signature
RE: etch upgrade problem
Andrei Popescu wrote on Monday, April 09, 2007 5:28 PM -0500:
Seth Goodman [EMAIL PROTECTED] wrote:
packages, /usr/X11R6/bin contains only a lib directory with a few
^
I guess you mean /usr/X11R6/
Yes, sorry. /usr/X11R6/bin is a symlink to /usr/bin
Section InputDevice
Identifier Configured Mouse
Driver mouse
Option CorePointer
Option Device/dev/psaux
Option Protocol PS/2
Option Emulate3Buttons true
EndSection
I think your problem is in this section, see below.
(EE) xf86OpenSerial: Cannot open device /dev/psaux
No such device.
(EE) Configured Mouse: cannot open input device
(EE) PreInit failed for input device Configured Mouse (II)
UnloadModule: mouse (WW) No core pointer registered
(II) XINPUT: Adding extended input device Generic Keyboard (type:
KEYBOARD) xkb_keycodes { include
xfree86+aliases(qwerty) }; xkb_types{ include
complete }; xkb_compatibility{ include complete };
xkb_symbols { include pc(pc105)+us };
xkb_geometry { include pc(pc104) };
No core pointer
Fatal server error:
failed to initialize core devices
^^^
X cannot find your mouse. Try another device instead of /dev/psaux. I
have /dev/input/mice
Same result.
--
Seth Goodman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: etch upgrade problem
On 4/9/07, Seth Goodman [EMAIL PROTECTED] wrote: Matt Richardson wrote on Monday, April 09, 2007 4:39 PM -0500: I had the same problem when I upgraded sarge to etch some time ago. The solution was to add psmouse to /etc/modules. Check out lsmod and see if it's listed already, but I'd guess not. cray4:~# lsmod Module Size Used by ... psmouse20360 0 ... cray4:~# cat /etc/modules ... ide-cd ide-disk ide-generic psmouse -- Seth Goodman Ok, so that wasn't it. Here's my mouse section from xorg.conf. Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/input/mice Option Protocol ImPS/2 Option Emulate3Buttons true EndSection I remember having a problem with dpkg-reconfigure xserver-xorg when trying to figure out the issue. Something along the lines of an error saying that dpkg wouldn't over-write the existing xorg.conf because it had been manually modified. I think that behavior changed at some point, but I couldn't tell you when. -- Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: etch upgrade problem
Seth Goodman wrote:
I think your problem is in this section, see below.
(EE) xf86OpenSerial: Cannot open device /dev/psaux
No such device.
(EE) Configured Mouse: cannot open input device
(EE) PreInit failed for input device Configured Mouse (II)
UnloadModule: mouse (WW) No core pointer registered
(II) XINPUT: Adding extended input device Generic Keyboard (type:
KEYBOARD) xkb_keycodes { include
xfree86+aliases(qwerty) }; xkb_types{ include
complete }; xkb_compatibility{ include complete };
xkb_symbols { include pc(pc105)+us };
xkb_geometry { include pc(pc104) };
No core pointer
Fatal server error:
failed to initialize core devices
^^^
X cannot find your mouse. Try another device instead of /dev/psaux. I
have /dev/input/mice
Same result.
Well, What kind of mouse do you have? Is it PS/2, USB mouse, wireless mouse
etc.,?
For starters, you can also use AllowMouseOpenFail option in your xorg.conf
and tell the machine to start X despite a failure due to mouse. More
details can be found in 'man xorg.conf'. After that you can configure the
mouse separately knowing that everything else is working.
hth
raju
--
Kamaraju S Kusumanchi
http://www.people.cornell.edu/pages/kk288/
http://malayamaarutham.blogspot.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Etch upgrade problem with font server
On Sat, 2007-04-07 at 10:39 -0700, Terrence Branscombe wrote: Yesterday, I took the leap and upgraded from Sarge to Etch by following the Etch release notes as best I could. The upgrade appeared to work very well, but for some font problems. I'm very new to debian and linux, so may have made some poor decisions during the upgrade. The xfs font server I had running in Sarge now refuses to run and the log file is empty. I made sure my Files list in the /etc/X11/xorg.conf file matched the list in the /etc/X11/fs/config file and my /etc/X11/fs/config file is set to send errors to the /var/log/xfs.log file. Beyond that I'm not sure what else I can do to troubleshoot this. Any help would be appreciated, At this point, the font server is not needed anymore. As long as you have fontconfig and the set of fonts by default. dpkg-reconfigure -phigh xserver-xorg Then restart X, as long you have the files list in the config (which the defaults are very good) it works. -- greg, [EMAIL PROTECTED] Novell's Directory Services is a competitive product to Microsoft's Active Directory in much the same way that the Saturn V is a competitive product to those dinky little model rockets that kids light off down at the playfield. -- Thane Walkup -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Etch upgrade problem with font server
On Sat, 2007-04-07 at 13:03 -0700, [EMAIL PROTECTED] wrote: Greg Folkert wrote:: On Sat, 2007-04-07 at 10:39 -0700, Terrence Branscombe wrote: Yesterday, I took the leap and upgraded from Sarge to Etch by following the Etch release notes as best I could. The upgrade appeared to work very well, but for some font problems. I'm very new to debian and linux, so may have made some poor decisions during the upgrade. The xfs font server I had running in Sarge now refuses to run and the log file is empty. I made sure my Files list in the /etc/X11/xorg.conf file matched the list in the /etc/X11/fs/config file and my /etc/X11/fs/config file is set to send errors to the /var/log/xfs.log file. Beyond that I'm not sure what else I can do to troubleshoot this. Any help would be appreciated, At this point, the font server is not needed anymore. As long as you have fontconfig and the set of fonts by default. dpkg-reconfigure -phigh xserver-xorg Then restart X, as long you have the files list in the config (which the defaults are very good) it works. Since I only connect to my Debian system through remote X sessions, I can configure the X server (Cygwin) to use its own font path; it was simply easier to get the Debian host to supply the fonts and be assured that the fonts would be available. Now that my (remote) X server is no longer crashing because it can't find the xfs server, another problem with the upgrade has cropped up. The XDM login widget fails to appear, but nothing shows up in the /var/log/xdm.log file. To me, that points to the Xstartup script, but I haven't touched it. Sure, you can still run the fontserver if you want. Just the Debian machine doesn't need it and you should not configure it to use it, unless you REALLY want to. First off you will need to purge the old version off apt-get remove --purge xfs or aptitude purge xfs This should clear out some of the older deps on it(if any). Seeing as it was XF86 xfs font server, its no wonder it doesn't run, things are just plain missing and have been moved around drastically. Then, once we get back, the prompt: apt-get install xfs or aptitude install xfs Then you will need to modify the config, commenting out: no-listen = tcp to #no-listen = tcp Then perform a /etc/init.d/xfs restart Once done, netstat -na | grep 7100 will verify it is listening. TO be sure, this does open up your machine to a possible Dos, unless you are behind a proper firewall or are tunneling, etc... Hope this helps. -- greg, [EMAIL PROTECTED] Novell's Directory Services is a competitive product to Microsoft's Active Directory in much the same way that the Saturn V is a competitive product to those dinky little model rockets that kids light off down at the playfield. -- Thane Walkup -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Etch upgrade problem with font server
On Sat, 2007-04-07 at 17:39 -0400, Greg Folkert wrote: On Sat, 2007-04-07 at 13:03 -0700, [EMAIL PROTECTED] wrote: Greg Folkert wrote:: On Sat, 2007-04-07 at 10:39 -0700, Terrence Branscombe wrote: Yesterday, I took the leap and upgraded from Sarge to Etch by following the Etch release notes as best I could. The upgrade appeared to work very well, but for some font problems. I'm very new to debian and linux, so may have made some poor decisions during the upgrade. The xfs font server I had running in Sarge now refuses to run and the log file is empty. I made sure my Files list in the /etc/X11/xorg.conf file matched the list in the /etc/X11/fs/config file and my /etc/X11/fs/config file is set to send errors to the /var/log/xfs.log file. Beyond that I'm not sure what else I can do to troubleshoot this. Any help would be appreciated, At this point, the font server is not needed anymore. As long as you have fontconfig and the set of fonts by default. dpkg-reconfigure -phigh xserver-xorg Then restart X, as long you have the files list in the config (which the defaults are very good) it works. Since I only connect to my Debian system through remote X sessions, I can configure the X server (Cygwin) to use its own font path; it was simply easier to get the Debian host to supply the fonts and be assured that the fonts would be available. Now that my (remote) X server is no longer crashing because it can't find the xfs server, another problem with the upgrade has cropped up. The XDM login widget fails to appear, but nothing shows up in the /var/log/xdm.log file. To me, that points to the Xstartup script, but I haven't touched it. Sure, you can still run the fontserver if you want. Just the Debian machine doesn't need it and you should not configure it to use it, unless you REALLY want to. First off you will need to purge the old version off apt-get remove --purge xfs or aptitude purge xfs This should clear out some of the older deps on it(if any). Seeing as it was XF86 xfs font server, its no wonder it doesn't run, things are just plain missing and have been moved around drastically. Then, once we get back, the prompt: apt-get install xfs or aptitude install xfs Then you will need to modify the config, commenting out: no-listen = tcp to #no-listen = tcp Then perform a /etc/init.d/xfs restart Once done, netstat -na | grep 7100 will verify it is listening. TO be sure, this does open up your machine to a possible Dos, unless you are behind a proper firewall or are tunneling, etc... Hope this helps. Of course, I completely missed the XDM problem. I'll bet the OLD stuff is still hanging around. I don't use XDM, but I do use GDM. Since most pieces of Xorg are modular, so is XDM. I'd do a apt-get install --reinstall xdm Or possibly (if you have another Display Manager) choose to use the other display manager temporarily and then purge xdm and then reinstall it. I am surprised this has happened. -- greg, [EMAIL PROTECTED] Novell's Directory Services is a competitive product to Microsoft's Active Directory in much the same way that the Saturn V is a competitive product to those dinky little model rockets that kids light off down at the playfield. -- Thane Walkup -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
