Hi to everyone,
I've a macbook santarosa (13'' 2.4 GHz white) with Kubuntu Linux installed on as a single operating system. I've no refit installed.
In order to boot from usb and cdrom (this last one doesn't work) I tried to use plop with Grub 2. It works well (the boot works) but the keyboard doesn't work until the distribution on the USB card is entirely loaded (example: until the login prompt). I can't choose, for example, the several boot options from the Grub menu of the live USB distribution and looking for any errors in verbose mode.
How to fix it?
$ lsusb
Bus 007 Device 003: ID 05ac:022a Apple, Inc. Internal Keyboard/Trackpad (MacBook Pro) (ISO)
Bus 007 Device 002: ID 05ac:8242 Apple, Inc.
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 004: ID 05ac:8205 Apple, Inc. Bluetooth HCI
Bus 003 Device 003: ID 045e:0084 Microsoft Corp. Basic Optical Mouse
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 006: ID 05ac:8501 Apple, Inc. Built-in iSight [Micron]
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
$ lsusb -t
3-1:1.2: No such file or directory
/: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=HID, Driver=usbhid, 1.5M
|__ Port 2: Dev 3, If 0, Class=HID, Driver=usbhid, 12M
|__ Port 2: Dev 3, If 1, Class=HID, Driver=appletouch, 12M
|__ Port 2: Dev 3, If 2, Class=HID, Driver=usbhid, 12M
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 4, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
|__ Port 1: Dev 4, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
|__ Port 1: Dev 4, If 2, Class=app., Driver=, 12M
|__ Port 2: Dev 3, If 0, Class=HID, Driver=usbhid, 1.5M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M
|__ Port 4: Dev 6, If 0, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
|__ Port 4: Dev 6, If 1, Class='bInterfaceClass 0x0e not yet handled', Driver=uvcvideo, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/4p, 480M
Thanks
number 4 http://www.plop.at/en/bootmanager.html#faq
Thanks for the reply but isn't there a workaround? Because it is not useful if I can't choose the boot options
a workaround is, you have to set the option that you use mostly as default option and use a timeout.
and how to if the distribution is not my own or if it's closed source?
the second and last workaround is to use a connected ps/2 keyboard
then plop is not useful for laptop computers.. right?
I hope that in the next release you will fix this annoying problem
Quote from: drosophila on July 11, 2011, 12:07:21 PM
then plop is not useful for laptop computers.. right?
no, not right
Quote from: drosophila on July 11, 2011, 12:07:21 PM
I hope that in the next release you will fix this annoying problem
there is nothing to fix, its simply not implemented. 5.0.x will never support usb keyboards. why? it's posted in the forum somewhere.
Ok, before I start the searching for the reason, is there a method to customize plop in order to implement the my keyboard's driver?
Quote from: drosophila on July 11, 2011, 12:18:30 PM
Ok, before I start the searching for the reason, is there a method to customize plop in order to implement the my keyboard's driver?
no
Ok,
thank you for the answers. If I'll found a notebook without implemented USB keyboards, I could use this boot manager.
Regards
or you set the default boot with a timeout on the usb drive
I can't edit each distribution that I want to use.. I can't for several reasons:
1. I some cases, I don't know wich boot option I have to use
2. I can't edit the bootloader's configuration file if the distribution's source code is closed
3. It's not flexible operation (I would lose too much time)