Le vendredi 16 novembre 2012, Francois Andriot a écrit :
Le 16/11/2012 19:19, Patrick Serru a écrit :
Hi all, hello François I must admit that it is not easy to have to re-learn everything. Ido not know Debian :-/ . I want towards Debian or Fedora. Oss 10 + Yast was so easy!
There are some questions I ask in this list: how to take a screenresolution higher IN CONSOLE MODE? My screen seems about 40 lines of 80 columns at startup instead of the usual ~ 150 columns (kernel parameters at boot: vga = 0x31A)!
Graphics mode was achieved by "startx" and not "init 5" ... How doI log in graphic mode (TDM?). While Trinity was started, back on a console (Ctrl + Alt + F3, for example), the keyboard is not "listening" except Ctrl + Alt + Del. Fortunately, because my screen did not like the frequencies used by XOrg in 1280x1024: black-out! (-: See, Calvin). I guess I have to visit XOrg to find out how to do this ...
I can not ask all my questions about Debian on this list. It does not lack, however!
Read you soon!Hello, which OSS version were you running exactly ? 10.x or 11.x ?
About the console video mode, I think the "vga" option and framebuffer stuff are obsoleted by the "KMS" feature. KMS is supposed to switch your console to the best resolution available. If your computer does not support it, I think you can disable it by adding the "nomodeset" kernel parameter in grub.conf . If you do so, the "vga=" parameter should work again.
As you seem to already know, the KDM automatic startup should be enabled if you use the correct runlevel. In Fedora, in order to have Trinity's kdm started automatically in runlevel 5, you must add a variable in a config file.
In file (it does not exist by default): /etc/sysconfig/desktop Add the following line (without spaces): DISPLAYMANAGER=/opt/trinity/bin/kdm Then restart the service with command: service dm restart
There must be a corresponding setting in Debian but I do not know it.
Francois
--------------------------------------------------------------------- Passing by Debian before installing Fedora17: ****************************** Slávek wrote 50 times: REBOOT after the packet modification. ****************************** Thus, the console is correct, and now the login screen is Trinity's. But X is always wrong! ---------------------------------------------------------------------
François: I speak of 10.3 because it is the last distribution I installed "normally". I installed the 11.1 that I currently use in an emergency. I do not know because I have not gone into detail, because its use is only temporary.
Installing Fedora 17 went well. I noticed the similarity of the installer, with that of Debian. I ordered a minimum installation. So, I had to look for wget! Thus, the line indicating how to search with Yum had been helpful.
Once many Trinity packages installed, I rebooted :-) But this went wrong and it ended up with a "Ctrl D to continue". Usually, I get a "Ctrl D to reboot" when I'm wrong when editing /etc/fstab. Look at fstab: Ha horror: UUID while! I wonder how humans can deal with theses UUIDs… I concluded that administrators must identify the disks otherwise. Anyway, I left things such as the installer left it. I try a "startx": X has not started and I do not know why.
I do not know the tool to add software (equivalent to yast). Too bad, because I have installed a small window manager and Firefox. I will search on Internet…
In fact, I came back here to read the mail:
In file (it does not exist by default): /etc/sysconfig/desktop Add the following line (without spaces): DISPLAYMANAGER=/opt/trinity/bin/kdm Then restart the service with command: service dm restart
I'm going to try that. I am not optimistic! If it still does not work, I re-install down from the "Trinity-F17 live CD" on a mini partition, and then copy it all files from this mini partition on the "big" Fedora! It will boot, I hope! And if that does not work: I go back to Windows!
Thank you for all, Patrick