On Sun, Sep 22, 2002 at 03:15:35PM -0400, Felix Miata wrote: > You want to know why loud? You have to be. I've reported a number of > bugs over several Mandrake beta programs, and only one has produced a > response from anyone with a mandrake.com email address. That one was > Guillaume Cottenceau, who explicitly thanked me on the list for my > persistence.
I understand that but your issue does not warrant a delay in the release. And BTW it's @mandrakesoft.com not @mandrake.com. > The problem with my disappearing psaux is that no one with a > mandrake.com email address has suggested what log files or further > procedures on my part would help them either to understand what is > happening or to reproduce. Totally zip. So, I've been logging my > activity on the subject on the mailing list on the hope that sometime > someone else will notice and either allow me to help myself, or actually > produce a fix. > > There used to be Kudzu to handle hardware changes upon bootup. Kudzu was > easy: configure new, remove old, ignore. Most importantly, it gave you > time to become aware what it proposed to do, with a nice long default > pause to allow user input. > > Whatever is happening now instead of Kuduz is buried. A brief message > flashes on the screen, with no chance to pause startup to digest the > problem, or know what utility is actually doing its deed, much less what > config or /dev files it is screwing up. If you were in interactive > startup, you could do something, except you have to know in advance you > need to select interactive, since once the reconfiguration has happened, > you don't get a second chance the next time around. Have to reinstall > all over again to get another chance. So far, I've been unable to locate > what log file, if any, that this bad startup behavior generated. > Preliminary indication is that it happens before / is mounted rw, and so > logging is lost. > > A mouse is no less essential to a desktop environment than a keyboard. > These are basic stuff that has been around almost since the beginning of > time. There is no excuse for basic stuff to be allowed to get screwed > up. It worked before, and always should. Your issue has very little to do with your actually mouse than with the kernel/devfs not thinking that you have a psaux device. There isn't much to tell you to look for because you either have a psaux device or you don't. There isn't really a log file to look in to see why it isn't showing up. Your problem is much deeper than something that Kudzu would have had anything to do with. When it comes to mice all Kudzu did was detect the mouse that was connected and configure X and gpm to know what type of mouse it was. However as your system stands there is no /dev/psaux so there is no way to detect a mouse. IOW your problem is a much lower level. It has nothing to do with the particular mouse you're using. I'd doubt it has much to do with anything Mandrake is doing at all. It might be interesting to see if a totally unpatched clean 2.4.19 kernel from kernel.org behaves the same way. If it does then your specific motherboard has a problem with the 2.4.19 kernel. Without access to the hardware it'll be very difficult to figure out why. It also might be interesting to see if your your mouse works when booting with devfs=nomount If it does then it's a problem with devfs... but I highly doubt this. devfs finds out about what hardware is present from the kernel and it would seem that your kernel doesn't think you have a /dev/psaux device on your system. -- Ben Reser <[EMAIL PROTECTED]> http://ben.reser.org Never take no as an answer from someone who isn't authorized to say yes.
