This is a discussion on Oct 18th update to current kills X11 ?? within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> Hi all, Anybody see this and know the fix? After after upgrading with the Oct 18th batch of stuff ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi all, Anybody see this and know the fix? After after upgrading with the Oct 18th batch of stuff in current, X11 won't start any more. The log file says it couldn't find the "Keyboard" driver. Up until now my xorg.conf has worked fine on 15 machines. Is there some other driver that needs to be specified now instead of "Keyboard"? TIA Neil |
| |||
| Neil Koozer wrote: > Hi all, > Anybody see this and know the fix? > > After after upgrading with the Oct 18th batch of stuff in current, X11 won't > start any more. The log file says it couldn't find the "Keyboard" driver. > Up until now my xorg.conf has worked fine on 15 machines. Is there some > other driver that needs to be specified now instead of "Keyboard"? > > TIA > Neil > Have you changed your Driver to "kbd" in xorg.conf -- We can predict everything, except the future. |
| |||
| On 10-21-2004, in alt.os.linux.slackware, Jeffrey Froman <jeffrey@fro.man> wrote: > Neil Koozer wrote: > >> The log file says it couldn't find the "Keyboard" driver. > > The name of the driver has changed to "kbd". You'll have to edit > your /etc/X11/xorg.conf file to reflect this change. Didn't the .*-current 'changelog' refer to this change? How is it the OP or anyone else missed that? Max -- ____ ____ ____ ||M |||A |||X || ||__|||__|||__|| |/__\|/__\|/__\| |
| |||
| Max wrote: > Didn't the .*-current 'changelog' refer to this change? How is it > the OP or anyone else missed that? I don't know about this case, but I imagine that many people do things like install swaret, and just run blind updates every so often, without even knowing beforehand what changes have been made, or why. Sort of like closing your eyes and eating whatever someone happens to put in your mouth. Too scary for me! Jeffrey |
| |||
| On 10-22-2004, in alt.os.linux.slackware, Jeffrey Froman <jeffrey@fro.man> wrote: > Max wrote: > >> Didn't the .*-current 'changelog' refer to this change? How is it >> the OP or anyone else missed that? > > I don't know about this case, but I imagine that many people do > things like install swaret, and just run blind updates every so > often, without even knowing beforehand what changes have been > made, or why. Sort of like closing your eyes and eating whatever > someone happens to put in your mouth. Too scary for me! Yikes. I forgot about that "auto-pilot" stuff. Scary? You can say that again. No way in hell I'd walk that isle either. Still seems rather odd the OP mentioning 15 machines and not knowing about the Xorg changes... Max -- If Bill Gates had a dime for every time Windows crashed... Oh wait a minute, he already does. |
| ||||
| On Wed, 20 Oct 2004 21:56:55 -0600, Neil Koozer wrote: > Hi all, > Anybody see this and know the fix? > > After after upgrading with the Oct 18th batch of stuff in current, X11 won't > start any more. The log file says it couldn't find the "Keyboard" driver. > Up until now my xorg.conf has worked fine on 15 machines. Is there some > other driver that needs to be specified now instead of "Keyboard"? > > TIA > Neil Just yesterday I found the solution in one of the mail groups. Just edit your Xorg.conf file to remove the capital 'K'eyboard and replace with the lower case. Simple but easily overlooked. |