Yes, someone is getting your messages... ;o) I believe that anaconda does probe for the mouse, especially if you setup X Windows. Have you tried the skipx option, and set it up afterwards? What version of Redhat are you kickstarting? I've noticed that newer versions seem to contain less support for older (read serial) mice. I believe that X is setup very last, so if you write an RPM it will be installed before X Windows is set up. The post section is, of course, run after everything else, so you could try something there. Running mouseconfig --kickstart will probe for a mouse and run Xconfigurator non-interactively. Perhaps it is not finding anything? Is your mouse really on COM4--when it is setup, what does /dev/mouse point to? Perhaps you could put it on COM1 and see if that probes better (I assume you cannot, or you would have put it there in the first place). Forrest > -----Original Message----- > From: Matt Fahrner [mailto:Matt.Fahrner@xxxxxxxx] > Sent: Friday, June 22, 2001 9:50 AM > To: kickstart-list@xxxxxxxxxx; brian.peront@xxxxxxxx; > joe.funk@xxxxxxxx > Subject: Re: 7.1 Kickstart mouse problem > > > It's my guess that kickstart is still probing the mouse even though we > specified all the information it needs. Then it doesn't find the mouse > it puts it to the default. Can anyone answer "yes" or "no" to > that one? > Looking at the Anaconda source it's really hard to tell (I still can't > locate where it probes the mouse period). > > If so, we either need to patch the mouse in with an installed RPM we > write or put it in the %post. I'm inclined to write an RPM however the > question then is, at the point where the RPMs are installed is the > Anaconda code done manipulating the XF86Config and > /etc/sysconfig/mouse??? I don't want to step on it in an RPM... > > It'll get ugly in the %post (unless we install a script and > then run it > there). > > IS ANYONE ACTUALLY GETTING THESE MESSAGES?!?!?!? > > Thanks, > > - Matt > > Matt Fahrner wrote: > > > > Using kickstart we're trying to configure a serial mouse on COM4, > > however when we put this in our kickstart file: > > > > mouse --device ttyS3 --emulthree generic > > > > it doesn't seem to complain but it also doesn't seem to set > the mouse up > > (it's left as a Generic 2 button with "/dev/mouse" point to > "psaux"). > > Note this port requires a "setserial" in "rc.serial" to work, but I > > don't think it should matter in kickstart? > > > > As a hack we tried doing our own: > > > > /usr/sbin/mouseconfig --kickstart --device ttyS3 > --emulthree generic > > > > in the "%post" section which kind of worked but then it > didn't update > > Kudzu so it ends up asking about the "new" mouse and it also didn't > > update the XF86Config (which seems a little weird since the > interactive > > version sure does). > > > > Anyway, we'd rather have the normal "mouse" parameter work. > What might > > be up? > > > > Thanks, > > > > - Matt > > > > -- > > > --------------------------------------------------------------------- > > Matt Fahrner 2 South Park St. > > Manager of Networking Willis House > > Burlington Coat Factory Warehouse Lebanon, N.H. 03766 > > TEL: (603) 448-4100 xt 5150 USA > > FAX: (603) 443-6190 > Matt.Fahrner@xxxxxxxx > > > --------------------------------------------------------------------- > > -- > --------------------------------------------------------------------- > Matt Fahrner 2 South Park St. > Manager of Networking Willis House > Burlington Coat Factory Warehouse Lebanon, N.H. 03766 > TEL: (603) 448-4100 xt 5150 USA > FAX: (603) 443-6190 Matt.Fahrner@xxxxxxxx > --------------------------------------------------------------------- > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list >
