public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Erik DeBill <edebill@swbell.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.2ac12 and ac13 breaks usb-visor
Date: Fri, 9 Mar 2001 13:31:12 -0800	[thread overview]
Message-ID: <20010309133112.A17792@kroah.com> (raw)
In-Reply-To: <E14aQA9-0001br-00@the-village.bc.nu> <20010307172056.A8647@austin.rr.com> <20010307173640.A14818@kroah.com> <20010308140103.A17993@austin.rr.com> <20010308160758.A16296@kroah.com> <20010309141332.A29339@austin.rr.com>
In-Reply-To: <20010309141332.A29339@austin.rr.com>; from edebill@swbell.net on Fri, Mar 09, 2001 at 02:13:32PM -0600

On Fri, Mar 09, 2001 at 02:13:32PM -0600, Erik DeBill wrote:
> Nothing.  I've got the following in /etc/syslog.conf (which I believe
> SHOULD be correct), but I get absolutely nothing.
> 
> *.=debug;\
> 	auth,authpriv.none;\
> 	news.none;mail.none	/var/log/debug

Try adding an entry for kern.* like:
kern.*        -/var/log/kernel

> Until it's documented this is a landmine.  JE is the default USB
> driver, so you can bet that a great many people will be using it (even
> though it's described as "alternate").  Once it's fixed we just pull
> the warning from Config.help.

No, JE is _NOT_ the default USB UHCI driver, it doesn't say so in the
menu or anywhere.  It's just another option.

> This is the first time I've ever run across something like this in
> Linux that wasn't at least labelled "experimental".  Perhaps I've been
> leading a sheltered life.

Good point, I'll add something like your proposed patch for the visor
and other drivers that don't work with the JE driver.

> #
> # USB support
> #
> CONFIG_USB=y
> # CONFIG_USB_DEBUG is not set
> # CONFIG_USB_DEVICEFS is not set
> # CONFIG_USB_BANDWIDTH is not set
> CONFIG_USB_UHCI_ALT=y

This is your problem, DO NOT USE THIS DRIVER WITH THE VISOR!
set CONFIG_USB_UHCI=y and you should be fine.

Try that and let me know if you still have problems.

thanks,

greg k-h

-- 
greg@(kroah|wirex).com

  reply	other threads:[~2001-03-09 21:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-06 22:42 Linux 2.4.2ac13 Alan Cox
2001-03-06 22:56 ` Sergey Kubushin
2001-03-06 23:12 ` Andrzej Krzysztofowicz
2001-03-07  8:22 ` Michael Meissner
2001-03-07 23:20 ` Linux 2.4.2ac12 and ac13 breaks usb-visor Erik DeBill
2001-03-07 23:50   ` Greg KH
2001-03-07 23:52   ` Alan Cox
2001-03-08  1:36   ` Greg KH
2001-03-08 20:01     ` Erik DeBill
2001-03-09  0:07       ` Greg KH
2001-03-09 13:15         ` Reboot fails 2.2.19pre11 SMP Collectively Unconscious
2001-03-09 20:13         ` Linux 2.4.2ac12 and ac13 breaks usb-visor Erik DeBill
2001-03-09 21:31           ` Greg KH [this message]
2001-03-10  2:10             ` David Huggins-Daines
2001-03-11  2:30               ` Greg KH

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=20010309133112.A17792@kroah.com \
    --to=greg@kroah.com \
    --cc=edebill@swbell.net \
    --cc=linux-kernel@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