DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi. I am trying out some linux-distros on a Dell dimension 9100 with two harddisks: the first with windows xp, the second so far with Fedora and Slackware. I want to add Debian (40r0, Debian GNU/Linux, kernel 2.6.18-4-686) to the second hd.
Installation from the netinstall CD went ok but after reboot I type startx and get "Fatal server error: no screens found".
I also had a startx-problem in Slackware which (i think) had to do with a missing driver for my Ati Radeon X300 video card. After a lot of googling i solved that with:
as root:
I usually see "radeon" as the driver instead of "ati" here, for Radeon cards. Dunno, though, I don't use ATI card myself.
You can fiddle with the values in xorg.conf but if you don't want to do it manually, there are usually one or more scripts that try to automate the process of creating a working xorg.conf. First it's a good idea to make a backup of your current config, so you don't at least make things worse:
Code:
cp /etc/X11/xorg.conf /etc/X11/xorg.conf.backup
then try to find out what kind of X configuration scripts there is on your system: if you're using BASH you have TAB completion, which means you can type a few of the first letters of a command and press TAB once or twice to make BASH guess the rest and show you what there is available. Try to complete 'X', 'x', 'xorg', 'Xconf' and so on. If you find one, run it and see if it helps.
What you did with the other OS was to install fglrx drivers, the ATI proprietary display drivers for cards newer than Radeon8500. Debian tries not to include any non-free/opensource/otherfancy software, so there might not be fglrx drivers available for you. I wonder why you ran 'rpm' with Slackware, I know it's available, but you shouldn't be using it anyway (Slackware uses .tar.gz packages, not .rpm). Well glad it worked. If the Debian reposities don't have fglrx, you can get it directly from ATI. First Debian way (assuming you have internet connection): as root
Code:
apt-get install fglrx
and if it can't find 'fglrx', try guessing some other good names for it. If you simply can't find it, surf to ATI site -> Download and get the proper installation package for your distribution, along with the directions (README or HOWTO or something). Read carefully what you need before installing using that installer, and then go ahead.
Thanks for your reply. I changed "ati" to "radeon" in /etc/X11/xorg.conf like you said and after reboot, first I got a black screen with 'Cannot Display This Video Mode' but it auto-adjusted and gave me a nice blue GUI-login screen! So i guess the video driver is working!!
The problem now is that I can't get passed the login screen. When I login as normal user the screen turns black and then goes back to the login screen without any warnings or errors. Logging in as root is not allowed.
I tried login with Failsafe and that gave me:
Code:
There was an error setting up interprocess communications for KDE.
The message returned by the system was:
Could not read network connection list.
/home/hans/.DCOPserver_dhcppc1_0
Please check that the "dcopserver" program is running!
After that I get a console-window on a blue background. How do i complete the installation of debian from here? (I also downloaded and burned the 21 installation CD's in case there is no internet connection). I tried apt-get install kde-desktop, but this package was not found.
mmmm.... just messed up a few things i'm afraid. I figured out that there had to be an ownership-problem of the shared /home directory. i had chosen the same username in fedora, slackware and debian. After the debian-installation-attempt I got an error when logging in in fedora:
Code:
User's $HOME/.dmc file is being ignored.
This Prevents the default session and language from being saved.
File should be owned by user and have 644 permissions.
User's $HOME directory must be owned by user and not writeable by other users
and after that:
Code:
the GNOME session manager was unable to lock the file '/home/hans/.ICE authority'. (...)
Sometimes this error may occur if the file's directory is unwritable,
you could try logging in via the failsafe session and ensuring that it is.
So in an attempt to solve the problem i logged in as root in fedora and added a new user and deleted the old. this worked for fedora but resulted in a kernel panic in slackware (hopefully i can find my installation notes!):
Code:
Kernel panic - not syncing: VFS: Unable to mount root fs on unkown-block (8,18)
in fedora i tried to repair it by re-adding the old username but that did not change anything. And i still have the same problem in debian...
Any suggestions to put things back to normal very welcome!
i gave every distro a different username and did a fresh install of debian. After changing ati to radeon again (thanks b0uncer!) i tried startx and after the login screen a beautiful desktop appeared! I also managed to get into slackware again (there are 4 of them in the grubmenu, two of them still give kernel panic, have to do some grub/lilo adjustments).
mmmm.... just messed up a few things i'm afraid. I figured out that there had to be an ownership-problem of the shared /home directory. i had chosen the same username in fedora, slackware and debian. After the debian-installation-attempt I got an error when logging in in fedora:
Code:
User's $HOME/.dmc file is being ignored.
This Prevents the default session and language from being saved.
File should be owned by user and have 644 permissions.
User's $HOME directory must be owned by user and not writeable by other users
and after that:
Code:
the GNOME session manager was unable to lock the file '/home/hans/.ICE authority'. (...)
Sometimes this error may occur if the file's directory is unwritable,
you could try logging in via the failsafe session and ensuring that it is.
So in an attempt to solve the problem i logged in as root in fedora and added a new user and deleted the old. this worked for fedora but resulted in a kernel panic in slackware (hopefully i can find my installation notes!):
Code:
Kernel panic - not syncing: VFS: Unable to mount root fs on unkown-block (8,18)
in fedora i tried to repair it by re-adding the old username but that did not change anything. And i still have the same problem in debian...
Any suggestions to put things back to normal very welcome!
Depending on your level of experience, it may be faster to simply reinstall and keep good track of what you do, in case you have to backtrack again.
If you want to learn and invest time, then it may be worth backing up and figuring out what went wrong, with the understanding that could take considerably longer to succeed.
As far as file and directory permissions, make sure that all the files and directories are owned by the account of the current setup. That is, if you are using /home/johnd as your home directory and johnd as the owner of all files in that directory and beneath it, that is correct.
The command ls -laR ~ will give a long listing of the home directory and all directories beneath it. I assume you will find some files and/or directories with 500, 1000, or some other numerical value as the owner of files and directories. If that is the case, then as root change this:
sudo chown -R johnd:johnd /home/johnd
as an example.
Does did mean that if I run "su -c chown -R <username>:<username> /home/<username>" in each of the three distros i can use the same username in all of them?
The same username should be fine, but I believe the username is mapped to an unique User ID number, so user John should have the same user ID number in all three distributions.. if that number is different then I think you will run into permissions issues..
cat /etc/passwd to see the username and associate User ID numbers..
so in this example, even though the usernames are the same, I don't think they would have access to the same Home directory because of the disparity in the User ID numbers. Easy to fix of course
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.