Bluetooth + streaming for tahrpup 6.x

How to do things, solutions, recipes, tutorials
Message
Author
tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#101 Post by tempestuous »

ktat wrote:before entering rfkill list, I clicked on the bluetooth icon to turn the daemon on.
I don't think that's necessary, and may even be counterproductive while you are trying to enable the bluetooth functionality.

This sounds like a case of problematic inbuilt bluetooth devices, as I mentioned in the first post. Comparing the Puppy/Fedora lsmod results, I see one significant one which is absent in Puppy - hp_wireless
Apparently this kernel module supports the hardware wifi switch on HP laptops.
In Tahrpup6 I can see that the hp_wireless module was not enabled in the kernel configuration. So it's feasible you could lobby one of the Tahrpup developers (rcrsn51 springs to mind) to compile this module for you and provide it as a dotpet.
But before you do this, try the fixes mentioned here -
https://forums.gentoo.org/viewtopic-p-7 ... ml#7499484
You will see that one of the suggested fixes is to cycle the wireless switch, which adds additonal weight to my suspicion that the hp_wireless module may be required.

And I still think the "btcoex_enable=1" parameter should be used.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#102 Post by tempestuous »

I have just downloaded the kernel source for Tahrpup 6.0.5 and can compile the hp_wireless driver shortly.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#103 Post by tempestuous »

Here is the hp-wireless driver (kernel module) compatible ONLY with the 3.14.56 PAE kernel in Tahrpup 6.0.5.
This driver is part of the official kernel source, but is not normally enabled in Puppy kernels.
hp-wireless supports the hardware wifi switch on modern HP laptops.

After installing this dotpet, reboot. Puppy should automatically load the new driver at bootup. You can check with the "lsmod" command.
Attachments
hp-wireless-k3.14.56-PAE.pet
for Tahrpup 6.0.5 with 3.14.56 PAE kernel
(1.64 KiB) Downloaded 298 times

ktat
Posts: 20
Joined: Mon 07 Oct 2013, 09:27

#104 Post by ktat »

Thanks, again, for all your help with this problem.

I've installed the dotpet you provided and rebooted. I then ran the following:

Code: Select all

root# lsmod | grep hp
hp_wmi                  4832  0 
sparse_keymap           1532  1 hp_wmi
rfkill                  5402  4 cfg80211,hp_wmi,bluetooth
wmi                     5142  1 hp_wmi
hp_wireless             1064  0 
root# rfkill list
0: phy0: wlan
	Soft blocked: no
	Hard blocked: no
root# hcitool dev
Devices:
I still have the following in my file system:
To make the driver's bluetooth function permanent, create a new text document in Geany, with this text -
Code:
options ath9k btcoex_enable=1

and save the text file as /etc/modprobe.d/bluetooth.conf
From what I can tell, it's not working, is there something that I have missed?

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#105 Post by tempestuous »

ktat wrote:is there something that I have missed?
You didn't mention whether you followed the advice in that gentoo forum link about cycling your hardware wireless switch.
Here's what I suggest you try -

1. boot up to Tahrpup (6.0.5)
2.

Code: Select all

rfkill list
to check that phy0/wlan is displayed, but not hci0.
3. toggle your hardware wireless switch OFF - this should be possible now that you have the hp-wireless driver installed.
4.

Code: Select all

rfkill list
to check that phy0/wlan is absent
5. toggle your hardware wireless switch ON
6.

Code: Select all

rfkill list
to check that phy0/wlan AND hci0 are now displayed.
7.

Code: Select all

hcitool dev
may still display no devices ... so unload/reload the bluetooth driver -
8.

Code: Select all

rmmod btusb
modprobe btusb
9.

Code: Select all

hcitool dev
will now hopefully show "hci0".

ktat
Posts: 20
Joined: Mon 07 Oct 2013, 09:27

#106 Post by ktat »

step 1.

Code: Select all

root# rfkill list
0: phy0: wlan
	Soft blocked: no
	Hard blocked: no
Following this I tried the wifi switch. Pressing 'fn' key and 'f12' (has pic of antenna and light on it) didn't get the desired result. It just caused the Puppy menu to pop up. The wifi light didn't turn off either.

Running rfkill list got the same result as before.

Interestingly, 'f2' and 'f3' have brightness icons and work to adjust brightness without holding down the 'fn' key. this is also true for 'f5', which launches a browser.

Pressing 'f12' on its own seems to do nothing. My experimenting with 'f*' keys hasn't located one that will turn off the wifi.

tempestuous
Posts: 5464
Joined: Fri 10 Jun 2005, 05:12
Location: Australia

#107 Post by tempestuous »

ktat wrote:Pressing 'fn' key and 'f12' (has pic of antenna and light on it) didn't get the desired result. It just caused the Puppy menu to pop up.
Groan. Nothing's easy.
For reference, I was involved with early hotkey support for Puppy in 2008 via the acpid utility, specifically for Asus Eee's at that time. This required different configuration files tailored for different Eee models.
Getting full hotkey support working for your HP g6 would take a lot of effort, but for the task at hand all we need to do is run the Linux commands which are linked to the wifi hotkey ...
and for that I need a little investigation - the (new) hp-wireless driver will probably create its own directory somewhere in /proc
could you please use ROX to look in /proc and report anything which appears to be a candidate. It's likely to be something like
/proc/hp
or
/proc/acpi/hp
or
/proc/hp/wlan
you get the idea.

ktat
Posts: 20
Joined: Mon 07 Oct 2013, 09:27

#108 Post by ktat »

Not sure that I've been able to find what we're looking for. This is what I came up with after searching for "hp" and "wlan" directories in /proc.

Code: Select all

ls /proc/sys/dev/hpet/
max-user-freq

ls /proc/sys/net/ipv4/conf/wlan0/
accept_local
accept_redirects
accept_source_route
arp_accept
arp_announce
arp_filter
arp_ignore
arp_notify
bootp_relay
disable_policy
disable_xfrm
force_igmp_version
forwarding
igmpv2_unsolicited_report_interval
igmpv3_unsolicited_report_interval
log_martians
mc_forwarding
medium_id
promote_secondaries
proxy_arp
proxy_arp_pvlan
route_localnet
rp_filter
secure_redirects
send_redirects
shared_media
src_valid_mark
tag

ls /proc/sys/net/ipv4/neigh/wlan0/
anycast_delay
app_solicit
base_reachable_time
base_reachable_time_ms
delay_first_probe_time
gc_stale_time
locktime
mcast_solicit
proxy_delay
proxy_qlen
retrans_time
retrans_time_ms
ucast_solicit
unres_qlen
unres_qlen_bytes

Walt52
Posts: 123
Joined: Fri 04 Apr 2014, 00:52

#109 Post by Walt52 »

Hope y'all don't mind my butting in, but I've installed three different versions of bluEz on my Dell 1501 Running Tahr, including yours, and I can't get the logo to appear. I was running Precise and got it to come up, but I never did get it to work. Can you offer suggestions?

User avatar
Semme
Posts: 8399
Joined: Sun 07 Aug 2011, 20:07
Location: World_Hub

#110 Post by Semme »

Walt, if your dealing with a 605 cd, boot "puppy pfix=ram" >> dwnld and install from page one. You get an icon? I do.

Fact is remnants from previous Bluez pkgs may be running interference..

==

In addition, use pFind and "system files" search bluez.

After the results surface, you hit "file" and "export the results to text editor" option.

Dump those here..
>>> Living with the immediacy of death helps you sort out your priorities. It helps you live a life less trivial <<<

Walt52
Posts: 123
Joined: Fri 04 Apr 2014, 00:52

#111 Post by Walt52 »

Semme, you are right, it's 605 on a disk, BUT after booting in pfix=ram I downloaded and installed the bluez-4101-streaming from page 1, and STILL get no logo.

"In addition, use pFind and "system files" search bluez.

After the results surface, you hit "file" and "export the results to text editor" option.
Dump those here.."

I'm assuming you want me to get back in the regular boot to do this?

Rebooting. . .

Walt52
Posts: 123
Joined: Fri 04 Apr 2014, 00:52

#112 Post by Walt52 »

gtk-file|bluez|/lib/udev/bluez|169|2016/08/28 - 06:35:58.7165579050|-rwxr-xr-x|root
gtk-file|bluez-simple-agent|/usr/bin/bluez-simple-agent|3933|2016/08/28 - 06:35:58.7115597690|-rwxr-xr-x|root
gtk-file|bluez-simple-service|/usr/bin/bluez-simple-service|2952|2016/08/28 - 06:35:58.7055620060|-rwxr-xr-x|root
gtk-file|bluez-test-adapter|/usr/bin/bluez-test-adapter|3436|2016/08/28 - 06:35:58.6975649900|-rwxr-xr-x|root
gtk-file|bluez-test-audio|/usr/bin/bluez-test-audio|1055|2016/08/28 - 06:35:58.6915672270|-rwxr-xr-x|root
gtk-file|bluez-test-device|/usr/bin/bluez-test-device|5304|2016/08/28 - 06:35:58.7025631250|-rwxr-xr-x|root
gtk-file|bluez-test-discovery|/usr/bin/bluez-test-discovery|1573|2016/08/28 - 06:35:58.6975649900|-rwxr-xr-x|root
gtk-file|bluez-test-input|/usr/bin/bluez-test-input|1055|2016/08/28 - 06:35:58.6985646170|-rwxr-xr-x|root
gtk-file|bluez-test-manager|/usr/bin/bluez-test-manager|913|2016/08/28 - 06:35:58.6985646170|-rwxr-xr-x|root
gtk-file|bluez-test-network|/usr/bin/bluez-test-network|1206|2016/08/28 - 06:35:58.7115597690|-rwxr-xr-x|root
gtk-file|bluez-test-serial|/usr/bin/bluez-test-serial|1197|2016/08/28 - 06:35:58.7025631250|-rwxr-xr-x|root
gtk-file|bluez-test-service|/usr/bin/bluez-test-service|1079|2016/08/28 - 06:35:58.7025631250|-rwxr-xr-x|root
gtk-file|bluez-test-telephony|/usr/bin/bluez-test-telephony|4021|2016/08/28 - 06:35:58.7135590230|-rwxr-xr-x|root
gtk-file|bluez.py|/usr/lib/python2.7/dist-packages/bluetooth/bluez.py|19019|2016/08/29 - 23:13:00.0850595150|-rw-r--r--|root
gtk-file|PyBluez-0.18.egg-info|/usr/lib/python2.7/dist-packages/PyBluez-0.18.egg-info|633|2016/08/29 - 23:13:00.0860596420|-rw-r--r--|root
gtk-file|source_bluez.py|/usr/share/apport/package-hooks/source_bluez.py|1460|2016/08/28 - 06:35:58.6065989220|-rw-r--r--|root
gtk-directory|bluez|/usr/share/doc/bluez|4096|2016/08/28 - 06:35:58.6125966850|drwxr-xr-x|root
gtk-directory|bluez-alsa|/usr/share/doc/bluez-alsa|4096|2016/08/28 - 21:44:45.6165264320|drwxr-xr-x|root
gtk-directory|bluez-audio|/usr/share/doc/bluez-audio|4096|2016/08/28 - 21:44:48.0298331510|drwxr-xr-x|root
gtk-directory|bluez-btsco|/usr/share/doc/bluez-btsco|4096|2016/08/29 - 23:15:37.2050286550|drwxr-xr-x|root
gtk-file|sound-of-bluez.png|/usr/share/doc/bluez-btsco/sound-of-bluez.png|19674|2016/08/29 - 23:15:37.2040285280|-rw-r--r--|root
gtk-directory|bluez-compat|/usr/share/doc/bluez-compat|4096|2016/08/29 - 23:15:27.1487505540|drwxr-xr-x|root
gtk-directory|bluez-cups|/usr/share/doc/bluez-cups|4096|2016/08/29 - 23:15:47.2913105700|drwxr-xr-x|root
gtk-directory|bluez-gstreamer|/usr/share/doc/bluez-gstreamer|4096|2016/08/28 - 06:36:39.7722761890|drwxr-xr-x|root
gtk-directory|bluez-hcidump|/usr/share/doc/bluez-hcidump|4096|2016/08/29 - 23:15:17.4975239330|drwxr-xr-x|root
gtk-directory|bluez-pcmcia-support|/usr/share/doc/bluez-pcmcia-support|4096|2016/08/29 - 23:15:06.9371817670|drwxr-xr-x|root
gtk-directory|bluez-tools|/usr/share/doc/bluez-tools|4096|2016/08/29 - 23:13:11.2974845570|drwxr-xr-x|root
gtk-directory|bluez-utils|/usr/share/doc/bluez-utils|4096|2016/08/29 - 23:14:57.4409748480|drwxr-xr-x|root
gtk-directory|python-bluez|/usr/share/doc/python-bluez|4096|2016/08/29 - 23:13:00.0830592610|drwxr-xr-x|root
gtk-directory|bluezchat|/usr/share/doc/python-bluez/examples/bluezchat|4096|2016/08/29 - 23:13:00.0810590070|drwxr-xr-x|root
gtk-file|bluezchat.py.gz|/usr/share/doc/python-bluez/examples/bluezchat/bluezchat.py.gz|1736|2016/08/29 - 23:13:00.0810590070|-rw-r--r--|root
gtk-file|bluez|/usr/share/lintian/overrides/bluez|1960|2016/08/28 - 06:35:58.6135963120|-rw-r--r--|root
gtk-file|bluez-utils|/usr/share/lintian/overrides/bluez-utils|72|2016/08/29 - 23:14:57.4389745940|-rw-r--r--|root
gtk-file|bluez-simple-agent.1.gz|/usr/share/man/man1/bluez-simple-agent.1.gz|847|2016/08/28 - 06:35:58.6155955660|-rw-r--r--|root

By the way, I tried the version from page one by iteself (with no joy) before going nutso with all the rest. :x

User avatar
Semme
Posts: 8399
Joined: Sun 07 Aug 2011, 20:07
Location: World_Hub

#113 Post by Semme »

Doesn't look right.. @ least, not like mine.

Code: Select all

/lib/udev/bluez
/usr/bin/bluez-simple-agent
/usr/bin/bluez-simple-service
/usr/bin/bluez-test-adapter
/usr/bin/bluez-test-audio
/usr/bin/bluez-test-device
/usr/bin/bluez-test-discovery
/usr/bin/bluez-test-input
/usr/bin/bluez-test-manager
/usr/bin/bluez-test-network
/usr/bin/bluez-test-serial
/usr/bin/bluez-test-service
/usr/bin/bluez-test-telephony
/usr/share/apport/package-hooks/source_bluez.py
/usr/share/doc/bluez
/usr/share/doc/bluez-alsa
/usr/share/lintian/overrides/bluez
/usr/share/man/man1/bluez-simple-agent.1.gz
Yeah, you've got too much baggage.

==

When you booted live, was your dwnld named "bluez_4.101-streaming.pet" or "bluez_4.101-streaming.gz?"

==

Here.. Re-dwnld the pet and do so to /tmp.

Rt-clk >> Hit "UExtract" and do so in/to /tmp.

Rt-clk again >> Window >> "Terminal Here" and issue: ls -lR > ~/bp_list.txt << Lowercase "L"s..

The resulting file, bp_list.txt is in /root.. Copy and paste it's contents..

==

And as soon as you get the chance, use PPM and pFind, remove EVERYTHING Bluez related.

When pFind no longer lists any system files, reboot, then wget the pkg on page one..

Code: Select all

wget http://www.smokey01.com/tempestuous/bluez_4.101-streaming.pet

Walt52
Posts: 123
Joined: Fri 04 Apr 2014, 00:52

#114 Post by Walt52 »

Contents of /root//bp_list.txt

total 1984
lrwxrwxrwx 1 root root 18 Aug 30 17:13 yaf-splash -> /usr/bin/gtkdialog
-rw-r--r-- 1 root root 71 Aug 30 17:13 Xmodes.txt
-rw-r--r-- 1 root root 108 Aug 30 17:55 xml_info.svg
-rw-r--r-- 1 root root 84700 Aug 30 18:09 xerrs.log
-rw-r--r-- 1 root root 381 Aug 30 17:56 wpa_supplicant.log
-rw-r--r-- 1 root root 2228 Aug 30 17:13 udevtrace-modem.log
-rw-r--r-- 1 root root 9226 Aug 30 17:13 udevtrace.log
drwxr-xr-x 4 root root 100 Aug 30 17:13 udev
-rw-r--r-- 1 root root 0 Aug 30 17:44 snapmergepuppyrequest
drwxr-xr-x 2 root root 40 Aug 30 02:13 simple_network_setup
drwxr-xr-x 2 root root 60 Aug 30 02:13 sfs_load
-rw-r--r-- 1 root root 6 Aug 30 17:13 retrovol.pid
drwxr-xr-x 2 root root 40 Aug 30 02:13 rc_sysinit
-rw-r--r-- 1 root root 138 Aug 30 02:13 rc_d_rc_services_log
-rw-r--r-- 1 root root 4 Aug 30 18:06 pup_event_sizefreem
-rw-r--r-- 1 root root 78 Aug 30 17:13 pup_event_probedisk_startup
-rw-r--r-- 1 root root 0 Aug 30 17:13 pup_event_ok_pin
drwxr-xr-x 2 root root 40 Aug 30 02:13 pup_event_ipc
-rw-r--r-- 1 root root 4 Aug 30 18:09 pup_event_frontend_timeout_savecnt
-rw-r--r-- 1 root root 3 Aug 30 17:13 pup_event_frontend_scrn_y
-rw-r--r-- 1 root root 4 Aug 30 17:13 pup_event_frontend_scrn_x
-rw-r--r-- 1 root root 2 Aug 30 18:09 pup_event_frontend_identify2_sr0
-rw-r--r-- 1 root root 2 Aug 30 17:13 pup_event_frontend_identify1_sr0
-rw-r--r-- 1 root root 0 Aug 30 17:13 pup_event_frontend_d_curpos.log
-rw-r--r-- 1 root root 4 Aug 30 17:13 pup_event_drvs_optical
-rw-r--r-- 1 root root 1 Aug 30 17:13 pup_event_drvs_floppy
drwxr-xr-x 2 root root 780 Aug 30 02:13 pup_event_backend
drwx------ 2 root root 40 Jan 1 1970 orbit-root
-rw-r--r-- 1 root root 11117 Aug 30 02:13 networkmodules
-rw-r--r-- 1 root root 301 Aug 30 17:55 network_connection_wizard_5.svg
-rw-r--r-- 1 root root 279 Aug 30 17:55 network_connection_wizard_4.svg
-rw-r--r-- 1 root root 264 Aug 30 17:55 network_connection_wizard_3.svg
-rw-r--r-- 1 root root 271 Aug 30 17:55 network_connection_wizard_2.svg
-rw-r--r-- 1 root root 293 Aug 30 17:55 network_connection_wizard_1.svg
drwxr-xr-x 2 root root 60 Aug 30 02:13 mount
drwxr-xr-x 2 root root 40 Aug 30 02:13 momanager
-rwxr-xr-x 1 root root 10 Aug 30 17:57 linksadded
-rw-r--r-- 1 root root 215 Aug 30 17:55 gtkrc_xml_info
-rw-r--r-- 1 root root 391 Aug 30 17:56 gtkdialog-splash_gtkrc
-rw-r--r-- 1 root root 425 Aug 30 17:56 gtkdialog_splash_border.svg
-rw-r--r-- 1 root root 408 Aug 30 17:56 gtkdialog_splash_bg.svg
-rw-r--r-- 1 root root 0 Aug 30 17:13 delayedrun_firstboot_flag
-rw-r--r-- 1 root root 0 Aug 30 17:57 delayedrun_finished_flag
-rw-r--r-- 1 root root 751 Aug 30 17:13 ddcprobe.txt
-rw-r--r-- 1 root root 2 Aug 30 17:54 CONNECTED
-rw-r--r-- 1 root root 4578 Aug 30 17:13 bootsysinit.log
-rw-r--r-- 1 root root 41229 Aug 30 17:13 bootkernel.log
-rw-r--r-- 1 root root 0 Aug 30 17:13 bootcnt.txt
drwxr-xr-x 3 root root 60 Aug 30 18:04 bluez_4.101-streaming.pet.extracted
-rw-r--r-- 1 root root 1752336 Aug 30 18:02 bluez_4.101-streaming.pet
-rw-r--r-- 1 root root 180 Aug 30 17:13 backg.log

User avatar
Semme
Posts: 8399
Joined: Sun 07 Aug 2011, 20:07
Location: World_Hub

#115 Post by Semme »

Walt, cover the bit below the last ==

It doesn't work because of all that excess baggage..

==

Of course, if you're here for only five minutes a day, don't expect to accomplish much.
>>> Living with the immediacy of death helps you sort out your priorities. It helps you live a life less trivial <<<

Walt52
Posts: 123
Joined: Fri 04 Apr 2014, 00:52

#116 Post by Walt52 »

And as soon as you get the chance, use PPM and pFind, remove EVERYTHING Bluez related.

When pFind no longer lists any system files, reboot, then wget the pkg on page one..
Code:
wget http://www.smokey01.com/tempestuous/blu ... eaming.pet

1. Done. Don't see any difference. Does it need to be in /tmp rather than just in /root?
2.What's the significance of the little printing press logo? Does it have to be extracted? (somehow I thought pets just installed themselves)
3. When I click on the file with the printing press logo, it asks Would you like to create a new archive or add to an existing archive?"

User avatar
Semme
Posts: 8399
Joined: Sun 07 Aug 2011, 20:07
Location: World_Hub

#117 Post by Semme »

BULLY!

"After booting in "puppy pfix=ram" I downloaded and installed the bluez-4101-streaming from page 1, and STILL get no logo."

Did you ever MD5 your 605 image before burning?

Is yours the i386 image?

Live boot for me gets the icon on THREE different boxes.

We could probably MD5 your burned disc if interested..

Walt52
Posts: 123
Joined: Fri 04 Apr 2014, 00:52

#118 Post by Walt52 »

"BULLY" as in TR's exclamation?

MD5 as a verb. OK, I'm willing to MD5 my 605.

How does one know if it's an i386 image?

Also, I remember seeing something about files in /tmp being accessible. . .are they not if they're just in root?

User avatar
Semme
Posts: 8399
Joined: Sun 07 Aug 2011, 20:07
Location: World_Hub

#119 Post by Semme »

Yes -- "BULLY!" :D

As for /root, whatever you place there'll stay. The reason I said save it to /tmp was because we were going to deal with it on a temporary basis. Things saved there don't survive reboots. In other words, it wasn't about to take up any room on your save file because you :roll: forgot to remove it. :wink:

As for your image, open /etc/DISTRO_SPECS >> Forward what it says for "DISTRO_TARGETARCH"

This won't however tell me whether it's PAE or non-PAE.

Not to worry.. There are only TWO possible MD5's.

What I want from you is to tell me there's NO "system files" listing for "bluez" when running pFind..

Walt52
Posts: 123
Joined: Fri 04 Apr 2014, 00:52

#120 Post by Walt52 »

OK, there's NO "system files" listing for "bluez" when running pFind.

Post Reply