From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net, rene.mayrhofer@gibraltar.at
Subject: Re: [Bluez-devel] snd-bt-sco module prevents ACPI S3
Date: Sun, 30 Oct 2005 16:30:34 -0700 [thread overview]
Message-ID: <4365579A.4080709@xmission.com> (raw)
In-Reply-To: <200510301643.31873.rene.mayrhofer@gibraltar.at>
Rene
> 1. It's name in the lsmod list is different from the module name, i.e.
> modprobe and rmmod must be used with different names.
Do you want to submit a patch (or at least tell us what the different
names are?)
> 2. It breaks ACPI S3 (suspend to RAM), making it pretty much unusable on
> laptops where S3 is used (like mine). Unloading snd-bt-sco does not work (I
> do that with a few other modules); as soon as it has been loaded once (even
> if it has not been used and/or has been unloaded), the kernel (2.6.14-rc5) is
> unable to enter ACPI S3.
This may be the result of something we did but it's much more likely to
be a change in the kernel.
What exactly happens when you try & fail to go to S3?
Brad
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-10-30 23:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-30 16:43 [Bluez-devel] snd-bt-sco module prevents ACPI S3 Rene Mayrhofer
2005-10-30 23:30 ` Brad Midgley [this message]
2005-10-31 12:37 ` Lenz Grimmer
2005-10-31 12:54 ` Luca Capello
2005-10-31 23:23 ` Rene Mayrhofer
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=4365579A.4080709@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=rene.mayrhofer@gibraltar.at \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.