This is reported against an old version of Ubuntu and many things has
changed since then. Because of that we won't fix this issue however if
this behavior repeats on a modern version please fill a bug report
against it and we will take it from there.
** Changed in: bluez (Ubuntu)
Status: In
@mcfrei:
Thanks for your help. I now have the M2010 dual booting with Dreamlinux 3.5
and Jaunty. With Dream, the hwC0D0 file was present at installation, but I had
to add hda-verb and the scripts. Dream chose the "vesa" driver for the display
and I installed "fglrx" and changed /etc/X11/xorg.
@CharlesR:
My mouse worked after i installed the bluetooth software that also paired it in
bluetooth mode, i guess.
I was not doing through testing, moreover, i've (sadly) updated it to Jaunty
and now i have ot reinstall it.
I have a dual boot, one hdd is for windows, and another for ubuntu.
As
@mcfrei: Thanks again for the good tip. I put a copy of the Jaunty iso
on a USB stick and booted. The keyboard works; its touchpad works, the
numeric keypad works! I was unable to get the M2010's native mouse to
do anything. But, hey, a USB mouse is not that big a deal -- I've got
several to m
Actually, it works in ubuntu 9.04 for me, but the mouse scroll is not working,
and that's sad.
I'm waiting for it too.
--
internal bluetooth device 413c:8121 in dell m2010 is not recognized
https://bugs.launchpad.net/bugs/452871
You received this bug notification because you are a member of Ubun
mcfrei: Thank you for that fix. "Make" is something I have not done
before, but it seems to work -- that is I got sound out of one of the
Gnome-games. More tests, soon.
If only "we" could get the native keyboard and mouse to work Windows
would be gone!
Thanks again.
CRS
--
internal bluetoot
CharlesR: here's a fix for the speakers to work
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3403
** Bug watch added: ALSA Bug Tracker #3403
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3403
--
internal bluetooth device 413c:8121 in dell m2010 is not recognized
https://bug
I mis-spoke above. Where I said "sleep mode", I should have said
"hibernate mode". The "sleep mode" keeps the working system in memory
and does not allow a choice of boot locations when next turned on. Only
the "hibernate mode" allows the choice of boot location, and then the
choices are only th
Here are some clues I discovered on my M2010: If I boot the Lucid
LiveCD from the Windows "sleep mode" (that is, power off, but not shut
down through the logging off, shutting down sequence), I can coerce the
Bluetooth module into recognizing both the keyboard and the mouse. But
when I installed
Hello, Baptiste Mille-Mathias.
Thank you for your interest.
Yes, i tried that. I tried to load ubuntu immediately after restarting windows
with the bluetooth adapter on, i tried disabling and enabling adapter in
windows and then restarting, i tried disabling and enabling the device in
Device Ma
Hi there,
Usually bluetooth adapters have to be enable in Windows (sigh) to be usable in
Linux.
Could you try that?
Thanks.
** Changed in: bluez (Ubuntu)
Status: New => Incomplete
--
internal bluetooth device 413c:8121 in dell m2010 is not recognized
https://bugs.launchpad.net/bugs/45
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33776613/Dependencies.txt
--
internal bluetooth device 413c:8121 in dell m2010 is not recognized
https://bugs.launchpad.net/bugs/452871
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Attachment added: "lsusb-v"
http://launchpadlibrarian.net/33776671/lsusb-v
--
internal bluetooth device 413c:8121 in dell m2010 is not recognized
https://bugs.launchpad.net/bugs/452871
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
13 matches
Mail list logo