Bug 118463

Not really my fault. It's not that I'm doing installation or suchlike.

Steffen, one for you ...

Ok, what driver do you need? 

Sorry, I have no Idea. It does work with Ubuntu 5.04 if that helps....

Olaf, do you have an idea? 

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.

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.

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. 

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). 

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.

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.

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.

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.

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.

So you mean it should work without bluetooth modules? 

Disabling hid2hci should work

what and where is hid2hci?

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} 

probably working meanwhile