Отпечатай - Проблем със блутут Ubuntu 9.10

при опита да инсталирам omnibook ми дава следната грешка

/usr/bin/make KSRC=/usr/src/linux-headers-2.6.31-17-generic clean
make[1]: Entering directory `/usr/src/modules/omnibook'
rm -f .*.cmd *.map *.mod.c *.o *.ko *~ "#*#"
rm -f -r .tmp_versions
rm -f -r debian/omnibook-source *-stamp
(cd misc/obtest; rm -f obtest *.o)
make[1]: Leaving directory `/usr/src/modules/omnibook'
dh_clean
/usr/bin/make -f debian/rules kdist_clean kdist_config binary-modules
make[1]: Entering directory `/usr/src/modules/omnibook'
/usr/bin/make KSRC=/usr/src/linux-headers-2.6.31-17-generic clean
make[2]: Entering directory `/usr/src/modules/omnibook'
rm -f .*.cmd *.map *.mod.c *.o *.ko *~ "#*#"
rm -f -r .tmp_versions
rm -f -r debian/omnibook-source *-stamp
(cd misc/obtest; rm -f obtest *.o)
cd: 1: can't cd to misc/obtest
make[2]: Leaving directory `/usr/src/modules/omnibook'
dh_clean
make[1]: dh_clean: Command not found
make[1]: *** [kdist_clean] Error 127
make[1]: Leaving directory `/usr/src/modules/omnibook'
make: *** [kdist_build] Error 2

Здрасти

аз до сега не съм имал проблем с исталацията на omibook. Ето ти инструкциите които аз ползвам.

Packages that you will need in order to download and build the omnibook kernel module:

Code:

subversion
build-essential
linux-source

note that linux source is fairly large (in the region of 40 MB). I am not certain if this is required, but it is listed clearly as a dependency in the original install instructions.

You should probably also install the linux-headers package relating to your kernel, for instance linux-headers-generic

So, simply issue this command to install them:

Code:

$ sudo apt-get install subversion build-essential( linux-source) linux-headers-generic

make a folder in your home directory called “omnibook”, and use svn (subversion) to download the latest omnibook module sources:

Code:

$ cd ~
$ mkdir omnibook
$ cd omnibook
$ svn co https://omnibook.svn.sourceforge.net/svnroot/omnibook/omnibook/trunk

you will get notification of each file downloaded, and when it is done, you need to cd into the trunk folder:

Code:

$ cd trunk

now, you need to build and install the module:
Code:

$ make
$ sudo make install

load the module by performing the following command (which will run depmod and modprobe for you):

Code:

$ sudo make load

now, cd to /proc/omnibook/ (which should now exist)

Code:

$ cd /proc/omnibook
$ ls

There should be, at the very least, two files listed there:
dmi
version

If these are the only two files listed, then your machine is not supported directly. I will get to working around that in a second. If you have other files listed there, like wifi, bluetooth, lcd, temparature, touchpad, or others, then your machine is supported and you can enable bluetooth by using the following command:

Code:

$ sudo su
# echo 1 > bluetooth

(I do the “sudo su” to get a root console because a normal “sudo echo 1 > bluetooth” does not work. More on this later, and how to fix it)

To disable:
Code:

$ sudo su
# echo 0 > bluetooth

The same can be done for wifi.
You can also get information about each item by doing this:

Code:

$ sudo cat bluetooth

To stop having to use a root console to set the paramaters, load the module with this option: “userset=1”

so, instead of running “make load” as we did earlier, do this:

Code:

$ sudo depmod -a
$ sudo modprobe omnibook userset=1

now a normal user will be able to enable/disable bluetooth, or edit any other omnibook paramater:

Code:

$ echo 1 > bluetooth

Once bluetooth is enabled using this method, you will be able to use it as normal. Issue a "hcitool dev" command in the console and you should get this:

Code:

$ hcitool dev
Devices:
hci0 xx:xx:xx:xx:xx:xx
$

Code:

xx:xx:xx:xx:xx:xx

is your bluetooth HW address

where before you had this:

Code:

$ hcitool dev
Device:
$

If you do not have the settings files (such as bluetooth and wifi), but only have the dmi and version files, all is not lost if you feel like taking a risk. If your computer is similar to one of the models listed as supported, I think this is a small risk, but if it is completely different.. well, here is the warning from the website:

Quote:
WARNING: Forced load on an unsupported machine may cause unpredictable result. You have been warned...
I take no responsibility for damaged caused by loading the module on an unsupported machine.

Here is where you need the “ectype” from the supported laptop list described above (the number in the column next to the laptop model – 12 in my case)

when you load the module, you will need to specify the ectype as a module option:

Code:

$ sudo depmod -a
$ sudo modprobe omnibook ectype=12

You should now have a list of files something like this in /proc/omnibook
blank
bluetooth
display
dmi
hotkeys
lcd
temperature
touchpad
version
wifi

You can make the module start on boot:

make a file called omnibook.modprobe in /etc/modprobe.d/ and place the module options in it:

Code:

options omnibook ectype=12 userset=1

append “omnibook” to /etc/modules to load it at boot:

Code:

$ sudo su
# echo “omnibook” > /etc/modules

You can also run this command to get a list of module options:

Code:

$ modinfo omnibook

then you can disable support for various elements completely. For instance, using bluetooth=0 as a module option will prevent the bluetooth file from showing up in /proc/omnibook and thus prevent you from modifying it.

see http://omnibook.sourceforge.net for full documentation to discover what else you can do with this utility.

EDIT: See post #3 below for my issues with omnibook.
EDIT (13-12-2007): Update the URL to the SVN repository (It changed, and the one on the website is also incorrect....).
__________________

Забележка
може да се наложи инсталиране на :
apt-get install bluetooth ;bluez-gnome; bluez-utils; gnome-bluetooth;

Linux за българи: Форуми

Linux секция за начинаещи => Настройка на хардуер => Темата е започната от: chavdary в Jan 13, 2010, 21:48