https://wiki.ubuntu.com/MainInclusionReportBluezPcmciaSupport, I did put
it there. Since my knowledge is limited, I entered the questions as far
as I could. Let's see what is going to happen (some help is welcome I
suppose ;)). Thanks for the support!
--
Sitecom CN-504 doesn't work anymore in dap
Oops, i incorrectly assume you have in fact bluez-pcmcia-support
installed on your system, my mistake. About the inclusion of this
package by default in gutsy please take a look at
https://wiki.ubuntu.com/UbuntuMainInclusionRequirements for the
instructions.
Since the problem was you don't have th
The problem is solved! Installing bluez-pcmcia did the trick. Maybe you
could arrange that that package is included by default, it would solve a
lot of problems for all Bluetooth PCMCIA users, since there is no
information available on how to solve the problem. Maybe even for Gutsy?
--
Sitecom CN
I did that, and unfortunately, it didn't solve the problem. I'll try to
install all bluetooth-related packets, maybe that will help.
--
Sitecom CN-504 doesn't work anymore in dapper
https://bugs.launchpad.net/bugs/46186
You received this bug notification because you are a member of Ubuntu
Bugs, w
could you please install setserial and then re-attach the pcmcia card, i
believe this is the problem, but need to be sure.
--
Sitecom CN-504 doesn't work anymore in dapper
https://bugs.launchpad.net/bugs/46186
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
No, setserial is not installed.
I attached files, with information. With the pccardctl command I can see
there is a bluetooth PCMCIA card, but hcitool dev lists no devices.
** Attachment added: "Outputs"
http://launchpadlibrarian.net/9463456/lists.tar.gz
--
Sitecom CN-504 doesn't work anymor
just out of curiosity, do you have the setserial package installed?.
Could you please attach in different files your full dmesg output to check if
there's more relevant information, and the lspci -vvnn output as well.
--
Sitecom CN-504 doesn't work anymore in dapper
https://bugs.launchpad.net/bu
Output of dmesg on Gutsy:
[ 827.52] pccard: card ejected from slot 0
[ 832.208000] pccard: PCMCIA card inserted into slot 0
[ 832.208000] pcmcia: registering new device pcmcia0.0
[ 832.252000] ttyS0: detected caps 0700 should be 0100
[ 832.252000] 0.0: ttyS0 at I/O 0x400 (irq = 3)
The last time I reinstalled Feisty, it still was a problem: the device
was recognized as a serial port, but that was settled after changing
some files (which, blame myself, I can't remember). In the coming days I
will install Gutsy and check if the problem persists, and report on that
here. Is that
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Thanks in advance.
** Changed in: bluez-utils (Ubuntu)
Assignee: (unassign
The error disappeared, but still hciconfig -a shows no devices.
syslog:
Oct 15 22:47:52 danny kernel: [17220934.048000] pccard: PCMCIA card inserted
into slot 0
Oct 15 22:47:52 danny kernel: [17220934.048000] pcmcia: registering new device
pcmcia0.0
Oct 15 22:47:52 danny kernel: [17220934.188000
Hi, thanks for your report,
please try to follow this:
https://launchpad.net/distros/ubuntu/+source/bluez-utils/+bug/8
and report back if succed.
Thaks!!
--
Sitecom CN-504 doesn't work anymore in dapper
https://launchpad.net/bugs/46186
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
12 matches
Mail list logo
