Hi,
I'm trying to make my BB boot as fast as possible. I notice it is
taking some time to start/load bluetooth drivers? I've tried
everything to stop it from starting up (However, I'm new to linux and
don't know a ton about the startup process). Is it possible to disable/
uninstall bluetooth support?
The normal methods I've read about to disable processes on startup
don't seem to work on Angstrom (service, chkconfig, etc).
Any help is greatly appreciated! I'm really stuck trying to reduce
boot time.
Angstrom uses the debian way of configuring services, not the red hat way.
regards,
Koen
Can you expand on that a little? I'm very new. I'm not even sure how
to check what processes/services bluetooth is using so I know what to
disable.
Also, you mentioned in the chat:
update-rc.d
after
init=/bin/busybox.sh
Can you explain what this means a little more?
Thanks again for all the help. I'm very new to linux and I'm trying to
finish up a Senior Design project for my Engineering degree.
Bump. I really need help with this.
Thanks!
Hello Alex,
I'm sorry but there's a sort of arrogance towards begginers on the
list. Some people believe they know it all.
Anyways here are my 2 cents worth of help:
chkconfig is redhat specific. It works differently with debian.
Service are started in /etc/rcX.d where X is the runlevel. The default
runlevel is set in /etc/inittab - most likely 2
Simply remove the link in /etc/rc2.d to the /etc/init.d bluetoth
daemon (most likely hcid - I can't check at the moment) and reboot to
make sure it won't restart
Here's a little chkconfig util I think I wrote ca 6 years ago, when I
switched from redhat to debian. With some minor tweaks on the awk
extraction of the runlevels and positions, tt'll help you get started
before knowing the debian way.
In any case, a faster boot is interesting - I am working on a specific
appliance which should start in 15 seconds max. I'll see where
additional delays can be shaved.
Guylhem
chkconfig (941 Bytes)
Guylhem,
You're great! Thanks so much for the help.
Yeah I'm just a beginner and trying to get some help, but I haven't been able to get many answers and when I do they are pretty vague and I haven't gotten much follow up. Thanks again I will give it a try tomorrow.
Alex Behrens
Next Generation Computer Consulting
Phone: 651.329.4187
E-mail: alex.behrens@ng-cc.com
WWW: www.ng-cc.com
I'm sorry but there's a sort of arrogance towards begginers on the
list. Some people believe they know it all.
And of course people ignoring advice, update-rc.d has been mentioned at least twice. Let me share a gem of wisdom on that: http://tinyurl.com/dj8cjm
Anyways here are my 2 cents worth of help:
chkconfig is redhat specific. It works differently with debian.
Service are started in /etc/rcX.d where X is the runlevel. The default
runlevel is set in /etc/inittab - most likely 2
Simply remove the link in /etc/rc2.d to the /etc/init.d bluetoth
daemon (most likely hcid
Use update-rc.d for that, if you go deleting symlinks manually you can just as well truncate libc.so.6 so you know you get random errors.
I did do a google of update-rc.d and I looked around at the documents.
Sorry I'm very much a newbie.
I ran:
update-rc.d -f bluetooth remove and it said it removed startup links.
However, I still see:
Bluetooth: L2CAP ver
2.11
Bluetooth: L2CAP socket layer
initialized
Bluetooth: SCO (Voice Link) ver
0.6
Bluetooth: SCO socket layer
initialized
Bluetooth: RFCOMM socket layer
initialized
Bluetooth: RFCOMM TTY layer
initialized
Bluetooth: RFCOMM ver
1.10
Bluetooth: BNEP (Ethernet Emulation) ver
1.3
Bluetooth: BNEP filters: protocol
multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
during the startup sequence and the processes:
btconnadd
btconndel
How do I check to see what files a certain process are related too? I
tried doing:
update-rc.d -f btconnadd remove and I don't think it did anything.
Sorry for being so redundant but I'm trying my best to learn. I'm very
new to linux/embedded linux.
<snip>
These messages come from the kernel. Your kernel was build with a
variety of bluetooth features enabled. To get rid of theses messages
you will need to update your kernel config and rebuild.
Steve
Alright sounds good.
I have no idea how to do that, but I'll start googling 
Is there anything I need to keep in mind since it is a embedded linux
kernel?