Results 1 to 3 of 3
I'm running debian lenny, 2.6.26.4 kernel.
I get the error "could not open obex://some_long_MAC_address...please do something..." when I try to browse my samsung using bluetooth.
My phone's service list indicates ...
- 01-11-2011 #1Just Joined!
- Join Date
- Sep 2008
- Posts
- 88
Bluetooth Menace + compilation error!
I'm running debian lenny, 2.6.26.4 kernel.
I get the error "could not open obex://some_long_MAC_address...please do something..." when I try to browse my samsung using bluetooth.
My phone's service list indicates all but one service item(modem) are present. I can send stuff to it but not the other way round.
Someone told me that debian distros have bluetooth problems.
Anyone knows how to go round this problem?
Also, when compiling kernel 2.6.36.5 and 2.6.37-etc, I get the undisputed error concerning the 'lguest' feature. How do I turn it off?
Help on these two is highly appreciated.
- 01-13-2011 #2Just Joined!
- Join Date
- Sep 2008
- Posts
- 88
Ok then, I have a more pressing issue than the above:
See, I'm trying to boot from the network and the tutorials I have read aren't bearing fruit. Tried two ways; using a wireless linksys router as my DHCP
server, and installing the OS named above for the same purpose (albeit at different times).
Here's what I've done:
1. boot my linksys router and configured it as a DHCP server with ip-range
190.68.227.200-190.68.227.220(which is more than good enough)
2. between my router and two PCs, there's a switch and connected it to them via the switch.
3. copied the ISO image of Debian 5.0.1 to PC1 with Ip 190.68.227.204 255.255.255.0 172.16.20.1(this is the gateway address and yes, it works fine)
to a directory "/foreign/boot_IMG/img_name.iso"
4. booted pc2 using PXE.
...and it failed...miserably!
1. Installed debian 5.0.1 on pc1 and configured it as the DHCP server, assigned itself a IP address 169.254.something.something (one of those wireless self-assigned IPs).
2. Copied the bootable image file to "/foreign/boot_IMG/img_name.iso"
3. In my simple network described above, I only removed the router but retained all the rest.
4. Tried to boot pc2 using PXE.
While trying PXE-boot, the comp reports no DHCP offers made to it by the server.
...and it failed...dissapointingly.
I found that pc2, which was configured to use DHCP, had the same address prefix as pc1 but the 2 suffixes in the address were different.
What am I doing wrong/forgotten to do?
Please advise promptly (take into mind that I can't give the bootable image's path without the address).Last edited by njuguna; 01-13-2011 at 07:01 AM. Reason: Add details
- 01-19-2011 #3Just Joined!
- Join Date
- Sep 2008
- Posts
- 88


Reply With Quote

