another problem starting X with sarge-install
I did an install using the sarge install cd last night. Initially I was working on a very small installation because of my plans on setting up LVM. I installed the minimum software necessary. installed lvm10 using 'apt-get install lvm10' set up lvm disks. This went fine. Then I ran TaskSel and selected only the X-Window-Server. An interesting note to make here is that the installation and configuration was extremely fast and simple. However, there was one oddity in the X-Window-Server set-up that I didn't expect. Initially there was an autodetect made of my hardware, including my video card, all of which went fine. It completely recognized my video card and the memory available on my Matrox G400. At what I expect was the completion of the process, it started over again at the beginning asking me about my Geniric Video Card and how much memory it had. I assume this is an installation bug of the sarge-install process. Installed and configured all of those packages and tested X. X worked for both root and regular users. I was able to login using xdm and get to a twm (default) desktop as root and non-root users. I then ran dselect, which selected a number of files by default. I selected no other packages for installation except the package for msft fonts and continued with the install. After this completed, I rebooted (new kernel) and was able to start up xdm (did not start automatically). I could login using XDM to the WindowMaker desktop as root. As a non-root user, my login failed and I was sent back to the XDM login screen. Something was introduced of the MANY packages that has severely broken the X-Windows installation in a way that are a little difficult to debug because there are so many and I'm unable to find any specific errors that really have meaning. In every case there was an error about not being able to find mga_hal driver, but since it worked initially with this error I don't think it really matters and the 'EE' statement in XFree86.0.log is superficial. The only other 'EE' statement found was about a generic mouse configuration. Again, removing that configuration option in XF86Config-4 did nothing to fix the problem. At this point I will retry installation of Debian using only -stable packages to see if this can be set up correctly with those packages. I used this exact hardware for 4 years with Debian on it and only recently removed the installation. But now I'm unable to get back. ugh! I'm not sure where to go next. But I've been running without a workstation for almost two weeks and kind of need something. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: another problem starting X with sarge-install
Tom Allison wrote: I did an install using the sarge install cd last night. I installed the minimum software necessary. This went fine. Then I ran TaskSel and selected only the X-Window-Server. Initially there was an autodetect made of my hardware, including my video card, all of which went fine. It completely recognized my video card and the memory available on my Matrox G400. At what I expect was the completion of the process, it started over again at the beginning asking me about my Geniric Video Card and how much memory it had. Do you perhaps have two video cards in the system? Or is the G400 dual-headed? I assume this is an installation bug of the sarge-install process. Installed and configured all of those packages and tested X. X worked for both root and regular users. I was able to login using xdm and get to a twm (default) desktop as root and non-root users. I then ran dselect, which selected a number of files by default. I selected no other packages for installation except the package for msft fonts and continued with the install. After this completed, I rebooted (new kernel) and was able to start up xdm (did not start automatically). Odd that it did not start automatically. I could login using XDM to the WindowMaker desktop as root. As a non-root user, my login failed and I was sent back to the XDM login screen. Instead of using XDM, can you start X as a normal user with just the startx command? My first suspicion would be /etc/X11/Xwrapper.config having the line allowed_users=root instead of allowed_users=console. If so, you can change it manually or run dpkg-reconfigure xserver-common and properly answer the question about who can run X. At this point I will retry installation of Debian using only -stable packages to see if this can be set up correctly with those packages. Yikes! No need to reinstall. This is just an X issue, not an OS issue. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: another problem starting X with sarge-install
Tom Allison wrote: Do you perhaps have two video cards in the system? Or is the G400 dual-headed? No... Just one G400, single head. After this completed, I rebooted (new kernel) and was able to start up xdm (did not start automatically). Odd that it did not start automatically. Yes... it is. I could login using XDM to the WindowMaker desktop as root. As a non-root user, my login failed and I was sent back to the XDM login screen. Instead of using XDM, can you start X as a normal user with just the startx command? No I cannot run startx as normal user. My first suspicion would be /etc/X11/Xwrapper.config having the line allowed_users=root instead of allowed_users=console. If so, you can change it manually or run dpkg-reconfigure xserver-common and properly answer the question about who can run X. I was never asked, under Medium dialog, who could run this. I will check it when I get in front of my computer. If this does solve the matter, then I will consider filing a bugreport against the installation. Thanks for the suggestion. At this point I will retry installation of Debian using only -stable packages to see if this can be set up correctly with those packages. Yikes! No need to reinstall. This is just an X issue, not an OS issue. Normally true. But when I run into goofy stuff that I can't seem to identify after the experience overall and time on this one... It's faster to reinstall sometimes. This is a very new setup. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
