public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Semler <cijoml@volny.cz>
To: bluez-users@lists.sourceforge.net
Subject: Re: AW: [Bluez-users] Conflict bluetooth and soundcard
Date: Wed, 22 Dec 2004 12:12:32 +0100	[thread overview]
Message-ID: <200412221212.32080.cijoml@volny.cz> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAosiAEZOtxUiHqgChZUVmh8KAAAAQAAAAejKkYMP2t0iWvwvgIRffgQEAAAAA@t-online.de>

Dne st 22. prosince 2004 11:49 Peter K. Martin napsal(a):
> Hi Michal,
>
> ##>
> ##>Compile and use LATEST vanilla kernel 2.6.10-rc3 and let us
> ##>know about
> ##>success.
> ##>
>
> I'm using SuSE 9.2 with kernel 2.6.8-24.5 and recompiled dmabt but no
> positiv result. Again the message Can't access Toshiba device /dev/toshiba
> occured. Then soundcard is also uncorrectly installed but this is to be
> solved by YaST at Sound --> options --> reset all.
> But the target is to have both available dmabt (bluetooth-function on of
> Toshiba-notebook) and a usable soundcard (in windows it is using PCI-bus 0
> and irq 11). So, do you have an idea to solve this problem?

The most probably it is ACPI problem solved in newer version of kernel - 
upgrade

>
> ##>We NEVER give help to users using vendor kernels.
> ##>
>
> Why? Marcel Holtmann helped me very well to get the whole BT-function with
> AP started. I tried to get help from SuSE, but this is not really good.
> Sometimes they have heard something about bluetooth and BT on
> Toshiba-notebook is a story itself. So, I'm happy about help from
> bluez-users, especially as Bluez is part of the kernel of SuSE 9.2
>
> So, PLEASE be so kind to help me in this case.

We offer help only to vanilla kernels and binaries compiled from source. We 
try help users with vendor kernels, but when it don't work we always 
recommend to upgrade to vanilla.
And most probably this si not BlueZ problem, but ACPI problem and ACPI was 
upgraded in 2.6.9 and 2.6.10


Michal
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-12-22 11:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-22  9:27 Conflict bluetooth and soundcard Peter K. Martin
2004-12-22  9:41 ` [Bluez-users] " Michal Semler
2004-12-22 10:49   ` AW: " Peter K. Martin
2004-12-22 11:12     ` Michal Semler [this message]
2004-12-22 12:57     ` Marcel Holtmann

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=200412221212.32080.cijoml@volny.cz \
    --to=cijoml@volny.cz \
    --cc=bluez-users@lists.sourceforge.net \
    /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