> ----- Original Message ----- > From: Richard Melville > Sent: 05/09/14 08:54 PM > To: BLFS Support List > Subject: Re: [blfs-support] Bluez-5.18 causing loss of prompt > > On 9 May 2014 19:42, Cliff McDiarmid <[email protected]> wrote: > > Hi > > > > I've installed BlueZ-5.18 into LFS7.5/BLFS7.5. When booting the daemon > > loads, but then I get no command prompt to work from, just a blank screen. > > If I take the bluez script out everything is okay. Any ides what's causing > > this? > > > > Extract from daemon log: > > May 9 19:19:30 cliffhanger acpid: starting up with netlink and the input > > layer > > May 9 19:19:30 cliffhanger acpid: 1 rule loaded > > May 9 19:19:30 cliffhanger acpid: waiting for events: event logging is off > > May 9 19:19:35 cliffhanger bluetoothd[2036]: Bluetooth daemon 5.18 > > May 9 19:19:35 cliffhanger bluetoothd[2036]: Starting SDP server > > May 9 19:19:35 cliffhanger bluetoothd[2036]: Bluetooth management interface > > 1.4 initialized > > > > thanks > > > > Cliff > > > I was getting the same error, Cliff, but I assumed that it was because > I hadn't yet installed the wifi/bluetooth card. After I installed the > card (an Intel 7260ac) and tried again the daemon went into an endless > termination/restart phase before I killed it. Wifi was working just > fine, so I assumed that the Intel bluetooth firmware hadn't loaded > properly. I use a static kernel and all the required bluetooth > components had been built into the kernel, and it's a .config I've > used before with bluetooth working OK.
Thanks Richard. Yeah, I wasn't that bothered by bluetooth until recently, but then I thought I would get it working. If I start the daemon manually in KDE, it still doesn't 'complete' i.e. give OK, but bluetoothctl does work. Try to boot with it and I get no prompt after boot up. thanks Cliff -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
