public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] USB Mouse on SLES8 Beta1
Date: Thu, 31 Oct 2002 18:01:13 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805318@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805291@msgid-missing>

"Jon R. Doyle" <marsaro@interearth.com> writes:

|> ----- Original Message -----
|> From: "Andreas Schwab" <schwab@suse.de>
|> To: "Jon R. Doyle" <jrd@sendmail.com>
|> Cc: <linux-ia64@linuxia64.org>
|> Sent: Thursday, October 31, 2002 4:31 AM
|> Subject: Re: [Linux-ia64] USB Mouse on SLES8 Beta1
|> 
|> 
|> > "Jon R. Doyle" <marsaro@interearth.com> writes:
|> >
|> > |> This seems to be broke:
|> > |>
|> > |> In Preview 5 & 6 of UL my Intel 4 CPU 900mhz SDV detects the keyboar
|> and
|> > |> mouse fine. SLES 8 beta 1 will not find the USB mouse
|> 
|> root@ia64-2.dev-lab.sendmail.com's password:
|> Last login: Wed Oct 30 13:42:42 2002 from shell.sendmail.com
|> ia64-2:~ # w
|>   9:23am  up 1 day, 20:48,  1 user,  load average: 0.00, 0.00, 0.00
|> USER     TTY      FROM              LOGIN@   IDLE   JCPU   PCPU  WHAT
|> root     pts/0    shell.sendmail.c  9:23am  0.00s  0.04s  0.00s  w
|> ia64-2:~ # hwinfo --usb
|> 03: USB 101.0: 10a00 Hub
|>   [Created at usb.100]
|>   Unique ID: B3Fu.Jt1hg9mdkyE
|>   Hardware Class: hub
|>   Model: "Hub"
|>   Hotplug: USB
|>   USB GUID: 000000000000000000000000
|>   USB Device status: driver active ("hub")
|>   Speed: 1.5 Mbps
|>   Config Status: cfg=new, avail=yes, need=no
|> 
|> 04: USB 102.0: 10800 Keyboard
|>   [Created at usb.100]
|>   Unique ID: B3Fu.PWDW3qm03V3
|>   Hardware Class: keyboard
|>   Model: "SOLIDTEK USB Composite Keyboard"
|>   Hotplug: USB
|>   Vendor: usb 0x060b "Solid Year (?)"
|>   Device: usb 0x2001
|>   SubVendor:  "SOLIDTEK"
|>   SubDevice:  "USB Composite Keyboard"
|>   Revision: "1.00"
|>   USB GUID: 060b20010000000000000000
|>   USB Device status: driver active ("hid")
|>   Speed: 12 Mbps
|>   Driver Info #0:
|>     XkbRules: xfree86
|>   Config Status: cfg=yes, avail=yes, need=yes
|>   Attached to: #3 (Hub)
|> 
|> 05: USB 201.0: 10a00 Hub
|>   [Created at usb.100]
|>   Unique ID: 3Okj.Jt1hg9mdkyE
|>   Hardware Class: hub
|>   Model: "Hub"
|>   Hotplug: USB
|>   USB GUID: 000000000000000000000000
|>   USB Device status: driver active ("hub")
|>   Speed: 1.5 Mbps
|>   Config Status: cfg=new, avail=yes, need=no
|> ia64-2:~ #

Seems like your mouse is broken somehow, as nothing of this kind is
conntected to USB.  What does lsusb give you?

|> I will look at that, better would be "why not have Yast1 like interface for
|> SLES, since it is a server OS. Clearly Yast2 is designed for the desktop
|> users, where you will use KDE.

If you want the textmode interface, you can call it as yast.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


      parent reply	other threads:[~2002-10-31 18:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30  6:07 [Linux-ia64] USB Mouse on SLES8 Beta1 Jon R. Doyle
2002-10-31 12:31 ` Andreas Schwab
2002-10-31 16:22 ` Jon R. Doyle
2002-10-31 18:01 ` Andreas Schwab [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ia64-105590709805318@msgid-missing \
    --to=schwab@suse.de \
    --cc=linux-ia64@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox