Justin Smith wrote:
After upgrading to STABLE a few days ago, several odd problems developed:
1. cups did not start automatically. It turned out the CUPS script was
being given the parameter 'faststart' rather than 'start'
You have an old version of the cups.sh script in /usr/local/etc/rc.d.
On Wed, Jan 11, 2006 at 11:29:27AM -0500, Justin Smith wrote:
> 2. GDM started but in an odd mode that didn't detect any keyboard input
> (so I couldn't log in). The mouse continued to work.
Any characters? Or you can enter numbers?
___
freebsd-stable@fr
Two of us just went through it, last week. A number of tweaks
gets you going again, but the real answer is to set:
VTAllocation=true
in /usr/X11R6/etc/gdm/gdm.conf
You may want to set the Virtual Terminal you want as well. I turn
off 5-8 to tty, and have mine come on VT5. I never use the four a
After upgrading to STABLE a few days ago, several odd problems developed:
1. cups did not start automatically. It turned out the CUPS script was
being given the parameter 'faststart' rather than 'start'
2. GDM started but in an odd mode that didn't detect any keyboard input
(so I couldn't log
On Thu, Jan 05, 2006 at 04:34:33PM -0500, Richard Kuhns wrote:
> If anyone has suggestions/wants me to try anything, just say so.
Yes, you can solve this problem by changing your
/usr/X11R6/etc/gdm/gdm.conf. You have to change the setting for
VTAllocation:
VTAllocation=true
bye,
Uwe
_
I'm in at work and turned off gdm in my rc.conf and rebooted.
The keyboard works fine! Then manually starting gdm and it
still works. That's great.
I think that something happened in the rc files that makes it
start earlier and that's conflicting with something that freezes
the keyboard.
Richar
I just finished a buildworld/buildkernel/mergemaster on my Dell Inspiron
9300. Upon rebooting, I noticed that gdm seemed to start earlier in the
boot process than it used to. When the login screen appeared, the mouse
seemed to work fine, but nothing I typed appeared. Attempting to use
C-A-F1 to
