From: Dave Givens <dave.givens@phaldor.co.uk>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Bluetooth Printing (Belkin Print Server)
Date: Mon, 22 Nov 2004 17:16:19 +0000 [thread overview]
Message-ID: <41A21EE3.5060408@phaldor.co.uk> (raw)
In-Reply-To: <1101139759.15086.14.camel@pegasus>
[-- Attachment #1: Type: text/plain, Size: 2143 bytes --]
Marcel,
I have tried that via the web page and the KDE Print manager. It
still does not work. The blue light on the print server flashes wildly
for ever, but nothing prints. The same result is obtained by clicking on
the icon under bluetooth devices. Lots of lights but no print. I have
tried other printers, but get the same results.
I have been trying to set-up the printer for several weeks now and I
have read all the bluez postings, I have tried everything that has been
suggested on your site and all others I can find.
The output from hcidump went on forever but seems to repeat what I
have included. I had to kill the job to stop the file before it filled
the hard disk. Is there anything else that might give me a clue as to
what is wrong? I have tried to include the data that I thought you might
need.
Dave Givens
Marcel Holtmann wrote:
>Hi Dave,
>
>
>
>> I have taken Marcels advice and moved to SUSE 9.2 after trying
>>Debian on the way. I could not get Debian to work with SATA and so it
>>was a non starter for this system. SUSE works a treat with SATA,
>>wireless LAN card and everything but my bluetooth print server. I
>>cannot find any services for this device, my phone shows up fine as
>>does a windows bluetooth enabled machine. I have included results from
>>some commands, please let me know if there are any others I should
>>run. Any help would be greatly appreciated as I have very little hair
>>left.
>>
>>
>
>what do you actually wanna do? If you wanna print to your Bluetooth
>printer then setup a new CUPS printer with "bluetooth://0002724080A3/"
>as URI and simply use it.
>
>Regards
>
>Marcel
>
>
>
>
>-------------------------------------------------------
>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
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 2835 bytes --]
next prev parent reply other threads:[~2004-11-22 17:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 15:41 [Bluez-users] Bluetooth Printing (Belkin Print Server) Dave Givens
2004-11-22 16:09 ` Marcel Holtmann
2004-11-22 17:05 ` Dave Givens
2004-11-22 17:16 ` Dave Givens [this message]
2004-11-23 9:16 ` Stefan Behlert
2004-11-23 9:40 ` Marcel Holtmann
2004-11-23 15:49 ` Dave Givens
2004-11-23 16:10 ` Marcel Holtmann
2004-11-23 16:21 ` Dave Givens
2004-11-23 16:36 ` Marcel Holtmann
2004-11-23 17:20 ` Dave Givens
2004-11-23 17:26 ` Marcel Holtmann
2004-11-23 22:28 ` Dave Givens
2004-11-24 6:06 ` Marcel Holtmann
2004-11-23 16:11 ` Stefan Behlert
2004-11-23 18:57 ` Dave Givens
2004-11-24 10:18 ` Stefan Behlert
2004-11-25 1:08 ` Dave Givens
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=41A21EE3.5060408@phaldor.co.uk \
--to=dave.givens@phaldor.co.uk \
--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