Usually the "internal" mice on laptops are connected via PS/2 bus internally, so they're actually considered PS/2, and use a PS/2 driver, etc.
I never thought I would need a rescue floopy when I could just boot from CD, but I was wrong. ;-) lol Of course, you're laptop may not even have a floppy drive. 8-o I never thought to check the BIOS settings, as were suggested - that's always a good place for laptops otherwise inclined to run Linux to fail. One little setting could make all the difference. Thanks for the compliment, but I'm not sure how helpful I've been! :-) lol Good luck with the laptop, I'm sure you're wife will love SuSE in the end. :-) Curtis. -----Original Message----- From: Jarrod Major [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 11, 2003 4:33 PM To: [EMAIL PROTECTED] Subject: Re: (clug-talk) (help) Laptop Issue -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sorry should have clarified, this is the internal mouse toggle thingy. No PS/2 mouse connected. I agree with you, SuSE's hardware detection should have caught this. I'm a little more than surprised. We were never prompted to create a rescue floppy... I believe there is a tool to do so from the CD. However, is that necessary if I can just boot of the CD? There has to be a way to get to something usefull from there... Thanks Curtis. You have my vote for one of the "most helpful guys" award today. J/K, overall there have been lots of helpful people today. Jarrod On Tuesday 11 February 2003 4:24 pm, you wrote: > Perhaps you can (temporarily) disable loading of the PCMCIA module so you > can work with your system live instead of from a CD or boot floppy? > > It would be a step in the right direction, although certainly not a > solution. Even at that... drat BSD-style Slackware init -- I would tell > you to edit rc.d/rc.modules. :-P Not sure what it would be on a SysV box. > > Of course, that step would have to be from a rescue disk (you did make a > rescue disk, right?). ;-) > > Maybe the wrong PCMCIA chipset is being loaded? That seems unlikely since > SuSE's been around the block and I think their hardware detection routines > must be pretty darn good by now. Maybe there's a conflict? If there is, > you could always disable PS/2 loading and tack on a USB mouse or something. > That may not necessarily circumvent a hardware conflict so much as a driver > conflict. I dunno. > > Sorry for not knowing anything about SuSE. Just some brainstorming that > may or may not be of assistance. Hope it helps, though. > > Curtis. > > -----Original Message----- > From: Jarrod Major [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 11, 2003 4:16 PM > To: [EMAIL PROTECTED] > Subject: (clug-talk) (help) Laptop Issue > > > Hey All, > > <knew I should have had my wife do her install at InstallFest> > > My wife has a Toshiba Satellite 2515CDS laptop. The specs are that it is a > Pentium II 233MHz machine with 96Mb RAM and a 4.1Gb HD. The machine has USB > and she's using my old 3Com CardBus NIC for Ethernet. She decided to take > the > plunge and blow away Windows on this machine in favour of SuSE (another > convert for Marcel). > > As I've already done several SuSE installs I figured this one would be > okay. I > looked up this model of laptop and as with most Toshiba's I found it was > supported. So we went through the install, nothing out of the ordinary, it > seemed to go in as we expected. > > Upon final reboot it hung at "Starting kernel PCMCIA". I know that the NIC > card worked with Mandrake and I believe it worked just fine under an > earlier > > version of SuSE. Just to be sure however, we removed the card and tried a > reboot. Same result. FYI, the NIC works perfectly fine under Windows. > > I did a more in-depth Google search this time and found that on some > Toshibas > the PCMCIA conflicts with the mouse. I'm not sure why this didn't come up > during the install (or my previous search). At any rate, I don't know how > to > > get past this and check any logs. The help I found was for a Red Hat > install > > and when I looked on my laptop for the files to edit I couldn't find them. > SuSE must have them somewhere else. > > Anyone encountered anything like this? There are about 17 or so more things > that occur after PCMCIA module is supposed to load. S�bastien recommended > throwing the install CD-ROM and escaping the install somehow and then > checking the logs. I was not overly sure how to do that. > > Thanks, - -- Jarrod Major GPG Fingerprint: FA4A 1EA3 A0EE A842 07BB 804C 0090 14F6 BE6E DE3D CLUG Treasurer Registered Linux User: #224211 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iQCVAwUBPkmIEACQFPa+bt49AQLxHwP/TojpKrNkTNd8CkF7AotJ8MYmqffTqrYE nNHPryVMp9xOaYpB7+SrpujvugNbwPmAjYboe21LszrywsH+vuHePWJEK87slQtH +h38tcryncCfkOTkp3hlPoElBgKFTAA+SD6jwTnZjgVqTSNLumQ9/qIltqSDXyqs EH7Hwa53aMY= =tKTy -----END PGP SIGNATURE-----
