Summary: | mkxf86config build bad xorg.conf, mouse doesn't work | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | lxg <mail2lx> |
Component: | [OLD] Development | Assignee: | Gentoo LiveCD Package Maintainers <livecd> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
lxg
2006-01-15 13:14:14 UTC
In the workaround, it should be: [...] put it into /etc/conf.d/local.start [...] If mkxf86config is setting up a serial mouse, it is because it is failing detection of any other mouse types. What kind of mouse do you have and which CD is this happening to you on? The devices were on two machines pretty simple USB mice, on my notebook I additionally have a Synaptics PS/2 touch pad. In the config file, there are several mice: the first is as mentioned the serial one, then a IMPS/2 and a USB. As I said, when deleting the first entry, both other work. Even the Synaptics together with the USB mouse, and the latter even with scroll wheel. The CD is a LiveCD I built myself taking inspirations from http://gentoo-wiki.com/HOWTO_build_a_LiveCD_from_scratch. Could the serial mouse entry be created because I compiled some support for serial devices into the kernel? If there is a theoretical possibility for this, I could try to compile a kernel w/o serial support and see what happens. Which version of mkxf86config are you pulling into your CD? Using official Gentoo CD creation methods (using catalyst) there are no such issues. Unfortunately, I cannot either verify nor endorse the use of the wiki's method for creating a CD, as it is first off completely incorrect on catalyst, and second off, outside of the scope of the Gentoo project. If you have a patch that resolves this problem for you on the latest mkxf86config version, that does not impact official CD building processes, then I'll gladly add it. No response... I've put out a new version of mkxf86config and I still cannot reproduce this. Resolving as WORKSFORME. |