pavement

Desktop, troubleshooting

From FreeBSDwiki
(Difference between revisions)
Jump to: navigation, search
m (Xorg)
(See also: add Hardware Configuration, Audio/Video)
 
(7 intermediate revisions by one user not shown)
Line 6: Line 6:
 
SLiM will let you log in to the console line, by entering "{{code|console}}", depending on it's configuration file, as the login user name and the root password.
 
SLiM will let you log in to the console line, by entering "{{code|console}}", depending on it's configuration file, as the login user name and the root password.
  
{{yhl|<ctrl><alt><f-key>}} will pull up a virtual console, where you can log in to fix configuration errors. This uses either the {{man|sc|4}} or {{man|vt|4}} driver. The sc driver doesn't work with all video cards.
+
{{yhl|<ctrl><alt><f-key>}} will pull up a virtual console, where you can log in to fix configuration errors.
 +
 
 +
If there are still problems, replace {{file|/etc/ttys}} with {{file|ttys}} from the FreeBSD install cd, then edit it from there.
  
 
==Login manager==
 
==Login manager==
If problems occur with logging in through XDM, check {{file|/var/log/xdm.log}}
+
If problems occur with logging in through XDM, check {{file|/var/log/xdm.log}} or {{file|~/.xsession-errors}}
 
  % less /var/log/xdm.log
 
  % less /var/log/xdm.log
 +
% less ~/.xsession-errors
  
 
==Firewall interference==
 
==Firewall interference==
Line 17: Line 20:
 
==Xorg==
 
==Xorg==
 
If problems occur with Xorg check {{file|/var/log/xorg.0.log}}. Use the commands {{cmd|less}} or {{cmd|grep}} to help you find potential problems.
 
If problems occur with Xorg check {{file|/var/log/xorg.0.log}}. Use the commands {{cmd|less}} or {{cmd|grep}} to help you find potential problems.
 
===Obsolete Xorg configuration reference===
 
This is for those who are familiar with older versions of FreeBSD.
 
 
Manually setting the option in {{file|xorg.conf}} to the next line enabled the mouse and keyboard:
 
Option "AllowEmptyInput" "False"
 
 
{{file|/etc/rc.conf}}:
 
 
hald_enable="YES" #this option can be replaced with FreeBSD's native program devd, if set in xorg-server.
 
 
For a custom xorg configuration file:
 
% Xorg -configure
 
After testing this configuration, {{file|xorg.conf.new}} can be copied to {{file|/etc/X11/xorg.conf}}:
 
% cp /root/xorg.conf.new /etc/X11/xorg.conf
 
  
 
==See also==
 
==See also==
 
* [[Desktop, light setup]]
 
* [[Desktop, light setup]]
* [[Desktop, BSD style]]
+
* [[Hardware Configuration, Audio/Video]]
  
 
[[Category:FreeBSD for Workstations]]
 
[[Category:FreeBSD for Workstations]]
 
[[Category:FreeBSD Multimedia]]
 
[[Category:FreeBSD Multimedia]]
[[Category:Installation]]
 
 
[[Category:Configuring FreeBSD]]
 
[[Category:Configuring FreeBSD]]
[[Category:Important Config Files]]
 
 
[[Category:New_User_Tips_and_FAQs]]
 
[[Category:New_User_Tips_and_FAQs]]

Latest revision as of 11:18, 10 February 2018

Contents

[edit] Rescue configuration

If an error is made, there are convenient options to fix the problem from the console, without requiring the install disc. The availability of some options depend on the situation.

One solution is to reboot into single user mode, then remount the drive using mount -u /. Other partitions required for start-up may have to manually be mounted. To make it easier, you can use the mountpoints in /etc/fstab.

SLiM will let you log in to the console line, by entering "console", depending on it's configuration file, as the login user name and the root password.

<ctrl><alt><f-key> will pull up a virtual console, where you can log in to fix configuration errors.

If there are still problems, replace /etc/ttys with ttys from the FreeBSD install cd, then edit it from there.

[edit] Login manager

If problems occur with logging in through XDM, check /var/log/xdm.log or ~/.xsession-errors

% less /var/log/xdm.log
% less ~/.xsession-errors

[edit] Firewall interference

A firewall's settings such as PF's may delay a windowmanager starting up from the login manager, possibly through the Xserver. Test a permissive firewall setting, to see if this is the problem.

[edit] Xorg

If problems occur with Xorg check /var/log/xorg.0.log. Use the commands less or grep to help you find potential problems.

[edit] See also

Personal tools