public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik DeBill <edebill@swbell.net>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.2ac12 and ac13 breaks usb-visor
Date: Thu, 08 Mar 2001 14:01:03 -0600	[thread overview]
Message-ID: <20010308140103.A17993@austin.rr.com> (raw)
In-Reply-To: <20010307173640.A14818@kroah.com>; from greg@kroah.com on Wed, Mar 07, 2001 at 05:36:40PM -0800
In-Reply-To: <E14aQA9-0001br-00@the-village.bc.nu> <20010307172056.A8647@austin.rr.com> <20010307173640.A14818@kroah.com>

On Wed, Mar 07, 2001 at 05:36:40PM -0800, Greg KH wrote:
> I'll try to run with everything compiled into the kernel later tonight.
> Does -ac14 with all of USB as modules, using usb-uhci work for you?

Hmm... I was compiling usb-uhci and uhci directly into the kernel,
then visor.o as a module.

In any case, I can't load any modules under ac14.  None.  I get
complaints about unmatched symbols.  Really fun when /home is on a fs
compiled as a module...

ac13 + crypto works with usb-uhci, usb-serial, and visor as modules.
No problems.

I've gone back and (re)tested with kernels 2.4.1, 2.4.2, ac[36],
ac1[01234].  I can only get a crash on ac12 and ac13.  2.4.2 is broken
after all, and everything after it.  2.4.2 and the ac kernels seem to
fail on 'pilot-xfer /dev/usb/tts/1 -m scsi.pdb' (to install a zTXT
into gutenpalm, doesn't matter what I'm sending), and things seem to
go slower and have more problems as the versions increase.  Then I can
crash the system under ac12 and 13.  This is using uhci compiled
directly into kernel, with usb-serial and visor as modules.

If uhci + visor is unsupported, might I suggest the following change
to Configure.help to warn people?

Erik


(agains 2.4.2-ac14)

--- Configure.help.orig	Thu Mar  8 13:24:31 2001
+++ Configure.help	Thu Mar  8 13:28:50 2001
@@ -10750,6 +10750,11 @@
   its USB docking station. See http://usbvisor.sourceforge.net for
   more information on using this driver.
 
+  If you say Y here, you MUST NOT use the UHCI Alternate Driver (JE).
+  Use the usb-uhci driver instead ("UHCI (Intel PIIX4, VIA, ...) support").
+  This driver is not stable in combination with the JE driver, and 
+  can cause system crashes.
+
   This code is also available as a module ( = code which can be
   inserted in and removed from the running kernel whenever you want).
   The module will be called visor.o. If you want to compile it as a


  reply	other threads:[~2001-03-08 20:20 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 [this message]
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
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=20010308140103.A17993@austin.rr.com \
    --to=edebill@swbell.net \
    --cc=greg@kroah.com \
    --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