SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
i didn't try it yet, a little busy, and have some probs with my ISP so internet at home is down,but on weekend i think everything will be ready and i'll try it out, i need it working!!!!!
i think i'll have some questions!!!
root@gnom:~# /etc/rc.d/rc.bluetooth start
which: no hid2hci in (/sbin:/bin:/usr/sbin:/usr/bin)
Starting Bluetooth subsystem: hcid sdpdCan't open HIDP control socket: Protocol not supported
hiddCan't open RFCOMM control socket: Protocol not supported
It depends on your phone. Not all manufacturers release the specs to their devices. For instance, I have a nokia 9300 which does not have native Linux support. Thankfully, Rudolph Koenig developed support for my device (and a few others) with p3nfs. Be warned though, this is pretty hard to set up and only works on the commands line. Search the web to see if there are any gui tools that support your device. A few that come to mind are 'plptools' and 'kandy' (which comes with KDE). If you are unsure, let me know what device you have and maybe I can find something for you.
in other systems kdebluetooth makes it all, is it possible in slackware and how??
Are you saying you got kdebluetooth to work with your phone on other distros? If so, let me know and I'll see if I can figure out why it's not working in Slackware.
I have updated the guide I wrote to give directions for installing kdebluetooth but I ran into a snag with QT. It does not support dynamic instalation directories which prevents you from building it into a package. You can do a regular 'make install', or you can wait until later tonight when I come up with a work around and update the guide again.
I strongly recomend waiting since I havn't had time to test it yet.
kdebluetooth does not support my phone, but I am always willing to spend the time proving that you can do anything on Slackware that you can do on other distros.
I am rebuilding QT right now on my home computer. I'll see how it turns out when I get home from work. Be fare warned though, it takes an ungodly amount of time to compile. The first time I went though it took about an hour on my PIV 2.8 Ghz!
I'll update the guide again once I get kdebluetooth running but I will need your help debugging since I have no way of testing if it works or not. Just make sure you run kdebluetooth from the command line so you can report any errors, if any.
i plug in my device and it works, i pull it off and plugg again and it works!!! with out typing any commands!!!with default kernel!
that is all!!
As you will find out, every kernel is different. What one distro includes in its kernel build is not neccesarily in another distros kernel build.
This is a prime example of this. Bluetooth kernel options are not enabled in the standard kernel configs in Slackware, but obviously are in your previous distro. That is a prime reason why the very first thing I do after a fresh install is to recompile my kernel, enabling what I need, and disabling what I do not. Again, bluetooth support comes to mind. As does my specific video, chipset, ports, filesystems, network, wireless, sound, etc.
ok, i'm ready for help, and ready to compile with my 2000 Mhz laptop all night long!!!
just tell me the commands and a full guide, how and what to do, because i installed linux 6 months before and it takes time to understand how it works and why... but i want to know!!!and i'll try to understand!!!!
As you will find out, every kernel is different. What one distro includes in its kernel build is not neccesarily in another distros kernel build
i've already understood this, and i don't know how many times i've already compiled it, and it's a little copmlicated to make some things in my laptop working such as hibirnate or standby, and fan,wifi and so on, but i'm trying and some day i'll do it with your help i hope!!!!
OK, well as it turns out, building kdebluetooth is a little bit more work then I had thought since it uses newer parts of KDE that were not implemented in Slackware-10.2. I was just about to rebuild my entire KDE from the ground up when I realized it would probably be easier to just upgrade KDE from slackware-current. I am still working out a few kinks in building kdebluetooth but if you want to get started upgrading KDE I'll give you some basic instructions in the mean time.
note: I have been able to upgrade to the current KDE and it seems to be running OK, but I can't grantee it's stability. Upgrading to the current KDE requires you to upgrade some key system dependencies with it. You might want to make sure you have backed up any important data before doing this.