Bug 118463 - Bluetooth Keyboard and Mouse not found
Summary: Bluetooth Keyboard and Mouse not found
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Installation (show other bugs)
Version: RC 1
Hardware: All All
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Steffen Winterfeldt
QA Contact: Klaus Kämpf
URL:
Whiteboard: bugday_todo
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-22 18:44 UTC by Dirk Becker
Modified: 2008-12-10 14:31 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Becker 2005-09-22 18:44:50 UTC
While installing SL 10.0 RC1, the system doesn't recognize my bluetooth keyboard
or mouse while the initial os-selector does. Installation of the system can not
proceed as I can not select a language or anything.
I use a Mac Mini with Apple Bluetooth keyboard and mouse. It does work with
Ubuntu 5.04.
Comment 1 Hannes Reinecke 2005-09-23 07:26:57 UTC
Not really my fault. It's not that I'm doing installation or suchlike.

Steffen, one for you ...
Comment 2 Steffen Winterfeldt 2005-09-23 08:49:48 UTC
Ok, what driver do you need? 
Comment 3 Dirk Becker 2005-09-23 08:58:19 UTC
Sorry, I have no Idea. It does work with Ubuntu 5.04 if that helps....
Comment 4 Steffen Winterfeldt 2005-09-23 09:02:48 UTC
Olaf, do you have an idea? 
Comment 5 Olaf Hering 2005-09-23 09:08:45 UTC
I guess the bluetooth drivers are not there.
what drivers are needed?

If you have a local network, boot the install CD1 with

install usessh=1 sshpassword=foobar nosshkey start_shell

this is supposed to load the network driver, send out a dhcp request to get an
IP and run a sshd.
Now you can login as root with password foobar and poke around.

We need the 'hwinfo > hwinfo.log' output from this system.
Comment 6 Dirk Becker 2005-09-23 10:27:45 UTC
You see the problem is, that I don't have any access to the system. I can't type
'install....' because I don't have a usable keyboard.
And I don't want to buy a keyboard just for this purpose.

Is there anything else I can do?

(In reply to comment #5)
> I guess the bluetooth drivers are not there.
> what drivers are needed?
> 
> If you have a local network, boot the install CD1 with
> 
> install usessh=1 sshpassword=foobar nosshkey start_shell
> 
> this is supposed to load the network driver, send out a dhcp request to get an
> IP and run a sshd.
> Now you can login as root with password foobar and poke around.
> 
> We need the 'hwinfo > hwinfo.log' output from this system.

Comment 7 Steffen Winterfeldt 2005-09-23 10:46:45 UTC
Hm, if you have ubuntu running, a copy of the /sys & /proc/device-tree 
date would be interesting. Something like 
 
tar -zcf /tmp/xxx.tar.gz /sys /proc/device-tree 
 
Please attach xxx.tar.gz, then. 
Comment 8 Steffen Winterfeldt 2005-09-23 10:50:23 UTC
Ah, wait a second. tar is bad. Do something like  
  
mkdir /tmp/xxx  
cp -a --parents /sys /proc/device-tree /tmp/xxx 
tar -zcf /tmp/xxx.tar.gz /tmp/xxx 
 
(that is, copy the trees, then tar them). 
Comment 9 Dirk Becker 2005-09-23 10:53:12 UTC
Yeah, that would be great if UBUNTU wouldn't forget to start the driver once I
reach the LogIn-Screen. I have a bug open there as well.
And I tried to connect you with the person in charge for that bug.
Comment 10 Olaf Hering 2005-09-23 10:59:52 UTC
you mean you are unable to type in the firmware already?
Thats impossible, because you have to type at least 'return' to load the kernel
off the CD.
Comment 11 Dirk Becker 2005-09-23 11:13:07 UTC
Ok I get it now. I'll provide you with the information as soon as posible. That
would be later this (friday, 23.09, MEST) evening.
Comment 12 Olaf Hering 2005-09-23 11:29:35 UTC
the i386 initrd lacks bluetooth as well, they probably get away with the legacy
emulation.

kernel/drivers/bluetooth/bcm203x.ko
kernel/drivers/bluetooth/bfusb.ko
kernel/drivers/bluetooth/bluecard_cs.ko
kernel/drivers/bluetooth/bpa10x.ko
kernel/drivers/bluetooth/bt3c_cs.ko
kernel/drivers/bluetooth/btuart_cs.ko
kernel/drivers/bluetooth/dtl1_cs.ko
kernel/drivers/bluetooth/hci_uart.ko
kernel/drivers/bluetooth/hci_usb.ko
kernel/drivers/bluetooth/hci_vhci.ko
kernel/net/bluetooth/bluetooth.ko
kernel/net/bluetooth/bnep/bnep.ko
kernel/net/bluetooth/cmtp/cmtp.ko
kernel/net/bluetooth/hidp/hidp.ko
kernel/net/bluetooth/l2cap.ko
kernel/net/bluetooth/rfcomm/rfcomm.ko
kernel/net/bluetooth/sco.ko

the ppc kernel has only kernel/drivers/usb/class/bluetty.ko enabled.

Comment 13 Marcel Holtmann 2005-09-23 15:01:42 UTC
The bluetty.ko should not be activated for any kernel. Use the Bluetooth support
from net/bluetooth/ and all its drivers.

The Apple machines use CSR chips and something that is called HID proxy and so
there is no need to have any Bluetooth modules in initrd. However when the
system is up and hid2hci has been executed you need the full BlueZ stack and the
hidd running. A full installation with a Bluetooth keyboard and mouse that have
never been paired is not that easy.
Comment 14 Steffen Winterfeldt 2005-09-26 08:51:24 UTC
So you mean it should work without bluetooth modules? 
Comment 15 Charles Majola 2005-09-30 07:24:25 UTC
Disabling hid2hci should work
Comment 16 Olaf Hering 2005-10-04 11:30:07 UTC
what and where is hid2hci?
Comment 17 Charles Majola 2005-10-04 11:36:38 UTC
hid2hci is used to set up switch HID proxy Bluetooth dongle into the HCI mode
and back. It comes with bluez-utils, check if its not enables in
/etc/init.d/{bluez-utils, bluetooth} 
Comment 19 Steffen Winterfeldt 2008-12-10 14:31:57 UTC
probably working meanwhile