bluetooth Bluetooth on Pineapple?

[Just_a_User]

Just wondering if its even possible specifically on Pineapples, i saw bluez packages etc and have briefly followed an openwrt guide to add bluetooth but I didn't pull it off yet. Did someone already try and succeed?

[rosem]

I was just trying to do the same - but failed. The issue is that the packages provided from OpenWRT are for kernel version 3.18.20 and the Pineapple seems to use 3.18.84. However I was not able to find any other packages for 3.18.84 and using the ones from OpenWRT for kernel 3.18.23 does not work since when you try to insmod the rfcomm.ko kernel module the Pineapple just crashes and reboots...

It's really annoying since I want to get that dongle I have up and running and I was also not able to find a proper resource on how to just recompile the module myself... maybe someone from Hak5 could just join in and give some details?

[moliata]

@Sebkinne is the lead WiFi Pineapple developer, he may take a look.

[rosem]

I basically tried what was outlined in that blogpost but it failed there (when loading rfcomm.ko the Pineapple just rebooted). So I thought it might be due to a kernel version mismatch...

I then basically got the wifipineapple-openwrt code from GitHub and recompiled it including the bluetooth module and dependencies, scp'ed them over and inserted them (leaving out rfcomm.ko for starters). It all worked out but then when I tried to run hcitool or hciconfig he Pineapple again crashes and reboots. The crashlog for my hcitool run is as follows:

ime: 1534674856.346308
Modules:	bnep@81848000+20bd	hci_uart@81878000+225f	btusb@818f8000+4740	bluetooth@81900000+3be3e	pppoe@82a18000+1fc0	ppp_async@82a1a000+18b0	option@82a10000+78f0	iptable_nat@829e4000+2f0	usb_wwan@82a04000+1127	sierra_net@829f6000+1600	rndis_host@829e8000+1339	qmi_wwan@82a00000+2930	pppox@829ee000+53a	ppp_generic@829f8000+5062	pl2303@829e6000+1a10	nf_nat_ipv4@829e2000+e41	nf_conntrack_ipv4@829b4000+1220	iptable_raw@829dd000+280	iptable_mangle@829d8000+3b0	iptable_filter@829d6000+2a0	ipt_REJECT@829cb000+390	ipt_MASQUERADE@829ba000+270	ipt_ECN@829b8000+560	ip_tables@829d0000+24dd	cdc_ether@829bb000+ebc	ax88179_178a@829cc000+32c0	asix@829c4000+3f67	xt_time@829b9000+660	xt_tcpudp@829b7000+690xt_tcpmss@829b2000+3d0	xt_statistic@829aa000+310	xt_state@829af000+2b0	xt_nat@829ab000+420	xt_multiport@829a6000+490	xt_mark@8299c000+290	xt_mac@829a7000+270	xt_limit@829a5000+3e0	xt_length@829a3000+2a0	xt_id@82999000+1e0	xt_hl@8299f000+310	xt_ecn@8299a000+500	xt_dscp@82998000+3d0	xt_conntrack@82996000+870	xt_comment@8298c000+1e0	xt_TCPMSS@82992000+7c0xt_REDIRECT@82991000+410	xt_NETMAP@82971000+480	xt_LOG@8297e000+2b0	xt_HL@8298b000+500	xt_DSCP@82970000+5d0	xt_CT@82972000+8a0	xt_CLASSIFY@828e7000+230	x_tables@82988000+2de2	usbserial@82978000+46eb	usbnet@828e8000+4296	ums_usbat@828da000+1c90	ums_sddr55@828d8000+12c0	ums_sddr09@828d4000+21f0	ums_karma@828cc000+5f0	ums_jumpshot@828ca000+e00	ums_isd200@82fe6000+13a0	ums_freecom@828c4000+7a0	ums_datafab@828ae000+1230	ums_cypress@82879000+8b0	ums_alauda@8289c000+2030	slhc@82f56000+10bb	nf_reject_ipv4@82837000+713	nf_nat_masquerade_ipv4@82fa2000+56c	nf_nat_ftp@82d7c000+4a0	nf_nat@828c0000+228b	nf_log_ipv4@82fa5000+c30	nf_log_common@82899000+8df	nf_defrag_ipv4@82fa8000+316	nf_conntrack_rtcache@8284d000+8c0	nf_conntrack_ftp@8285e000+1490	nf_conntrack@828a0000+b9fb	crc_itu_t@8287e000+3eb	cdc_wdm@8280c000+1e85	cdc_acm@82838000+36b0	sg@82870000+4e90	nfsv3@8281c000+37e8	nfs@82880000+18779	rtl8192cu@82860000+eb6b	rtl_usb@82fe4000+1f41	rtl8192c_common@82850000+83b9	rtlwifi@82810000+bbe6	rtl8187@82840000+b804	rt2800usb@82f6c000+3cf0	rt2800lib@82820000+16600	rt2x00usb@82fe8000+1da9	rt2x00lib@82f88000+7f29	crc_ccitt@82f58000+3eb	tun@82fbc000+3b6f	vfat@82f84000+1ef0	fat@82fb0000+b93f	lockd@82ff0000+b70f	sunrpc@82fc0000+2314a	grace@82d78000+371	ath9k_htc@82f70000+cf33	ath9k@82ce0000+154f6	ath9k_common@82cd8000+4b5e	ath9k_hw@82e80000+52361	ath@82d18000+4635	mac80211@82e00000+6189a	cfg80211@82d40000+34da3	compat@83bb4000+3163	nls_utf8@82ca6000+350	nls_iso8859_1@82ca7000+b40	nls_cp437@82c96000+1140	eeprom_93cx6@82ca8000+6ff	arc4@82cc9000+510	crypto_blkcipher@83b68000+2907	usb_storage@82c50000+938f	uhci_hcd@83b50000+4740	ohci_platform@83b1b000+ab0	ohci_hcd@83b90000+567f	ehci_platform@83b4a000+d20	ehci_hcd@83b08000+7cfc	sd_mod@82c78000+6360	scsi_mod@82c60000+14e47	gpio_button_hotplug@83aea000+1170	ext4@82c00000+4c5fc	jbd2@83af0000+b9b2	mbcache@83b3e000+11ad	usbcore@83b20000+1cf54	nls_base@83ae4000+1360	usb_common@83add000+478	crc16@83adc000+3e7	mii@83ad9000+db8	aead@83ae6000+10a0	crypto_hash@83ae0000+26a2
<6>[    1.220000] 8021q: 802.1Q VLAN Support v1.8
<6>[    1.230000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
<6>[    1.240000] Freeing unused kernel memory: 240K
<14>[    2.770000] init: Console is alive
<14>[    2.770000] init: - watchdog -
<6>[    5.420000] usbcore: registered new interface driver usbfs
<6>[    5.430000] usbcore: registered new interface driver hub
<6>[    5.430000] usbcore: registered new device driver usb
<5>[    5.490000] SCSI subsystem initialized
<6>[    5.500000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
<6>[    5.510000] ehci-platform: EHCI generic platform driver
<6>[    5.510000] ehci-platform ehci-platform: EHCI Host Controller
<6>[    5.520000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1
<6>[    5.530000] ehci-platform ehci-platform: irq 3, io mem 0x1b000000
<6>[    5.550000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00
<6>[    5.550000] hub 1-0:1.0: USB hub found
<6>[    5.550000] hub 1-0:1.0: 1 port detected
<6>[    5.560000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
<6>[    5.570000] ohci-platform: OHCI generic platform driver
<6>[    5.580000] uhci_hcd: USB Universal Host Controller Interface driver
<6>[    5.590000] usbcore: registered new interface driver usb-storage
<14>[    5.840000] init: - preinit -
<6>[    5.880000] usb 1-1: new high-speed USB device number 2 using ehci-platform
<6>[    6.420000] hub 1-1:1.0: USB hub found
<6>[    6.430000] hub 1-1:1.0: 4 ports detected
<5>[    6.610000] random: procd urandom read with 11 bits of entropy available
<14>[    6.820000] mount_root: loading kmods from internal overlay
<6>[    6.970000] usb 1-1.1: new high-speed USB device number 3 using ehci-platform
<5>[    7.140000] jffs2: notice: (327) jffs2_build_xattr_subsystem: complete building xattr subsystem, 4 of xdatum (0 unchecked, 4 orphan) and 4 of xref (0 dead, 4 orphan) found.
<14>[    7.160000] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab
<14>[    7.170000] block: extroot: not configured
<6>[    7.220000] usb 1-1.2: new high-speed USB device number 4 using ehci-platform
<5>[    7.230000] jffs2: notice: (323) jffs2_build_xattr_subsystem: complete building xattr subsystem, 4 of xdatum (0 unchecked, 4 orphan) and 4 of xref (0 dead, 4 orphan) found.
<14>[    7.350000] block: attempting to load /tmp/jffs_cfg/upper/etc/config/fstab
<14>[    7.360000] block: extroot: not configured
<14>[    7.370000] mount_root: switching to jffs2 overlay
<6>[    7.390000] usb-storage 1-1.2:1.0: USB Mass Storage device detected
<6>[    7.410000] scsi host0: usb-storage 1-1.2:1.0
<14>[    7.440000] procd: - early -
<14>[    7.440000] procd: - watchdog -
<14>[    8.350000] procd: - ubus -
<5>[    8.580000] scsi 0:0:0:0: Direct-Access     Generic  STORAGE DEVICE   0933 PQ: 0 ANSI: 6
<5>[    8.910000] sd 0:0:0:0: [sda] 247808 512-byte logical blocks: (126 MB/121 MiB)
<5>[    8.910000] sd 0:0:0:0: [sda] Write Protect is off
<7>[    8.920000] sd 0:0:0:0: [sda] Mode Sense: 21 00 00 00
<5>[    8.930000] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
<6>[    8.940000]  sda: sda1
<5>[    8.950000] sd 0:0:0:0: [sda] Attached SCSI removable disk
<14>[    9.360000] procd: - init -
<6>[   13.250000] Loading modules backported from Linux version v4.4-rc5-1913-gc8fdf68
<6>[   13.260000] Backport generated by backports.git backports-20151218-0-g2f58d9d
<7>[   13.410000] ath: EEPROM regdomain: 0x0
<7>[   13.410000] ath: EEPROM indicates default country code should be used
<7>[   13.410000] ath: doing EEPROM country->regdmn map search
<7>[   13.410000] ath: country maps to regdmn code: 0x3a
<7>[   13.410000] ath: Country alpha2 being used: US
<7>[   13.410000] ath: Regpair used: 0x3a
<7>[   13.420000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
<6>[   13.430000] ieee80211 phy0: Atheros AR9330 Rev:1 mem=0xb8100000, irq=2
<6>[   13.440000] usb 1-1.1: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested
<6>[   13.450000] usbcore: registered new interface driver ath9k_htc
<6>[   13.590000] RPC: Registered named UNIX socket transport module.
<6>[   13.590000] RPC: Registered udp transport module.
<6>[   13.590000] RPC: Registered tcp transport module.
<6>[   13.600000] RPC: Registered tcp NFSv4.1 backchannel transport module.
<6>[   13.630000] tun: Universal TUN/TAP device driver, 1.6
<6>[   13.630000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
<6>[   13.680000] usbcore: registered new interface driver rt2800usb
<6>[   13.700000] usbcore: registered new interface driver rtl8187
<6>[   13.760000] usbcore: registered new interface driver rtl8192cu
<5>[   13.820000] sd 0:0:0:0: Attached scsi generic sg0 type 0
<6>[   13.840000] usbcore: registered new interface driver cdc_acm
<6>[   13.840000] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
<6>[   13.850000] usbcore: registered new interface driver cdc_wdm
<6>[   13.870000] nf_conntrack version 0.5.0 (955 buckets, 3820 max)
<6>[   13.930000] usbcore: registered new interface driver ums-alauda
<6>[   13.940000] usbcore: registered new interface driver ums-cypress
<6>[   13.950000] usbcore: registered new interface driver ums-datafab
<6>[   13.950000] usbcore: registered new interface driver ums-freecom
<6>[   13.960000] usbcore: registered new interface driver ums-isd200
<6>[   13.970000] usbcore: registered new interface driver ums-jumpshot
<6>[   13.980000] usbcore: registered new interface driver ums-karma
<6>[   13.990000] usbcore: registered new interface driver ums-sddr09
<6>[   13.990000] usbcore: registered new interface driver ums-sddr55
<6>[   14.000000] usbcore: registered new interface driver ums-usbat
<6>[   14.010000] usb 1-1.1: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.4.0.fw, size: 51008
<6>[   14.030000] usbcore: registered new interface driver usbserial
<6>[   14.040000] usbcore: registered new interface driver usbserial_generic
<6>[   14.040000] usbserial: USB Serial support registered for generic
<6>[   14.100000] xt_time: kernel timezone is -0000
<6>[   14.110000] usbcore: registered new interface driver asix
<6>[   14.120000] usbcore: registered new interface driver ax88179_178a
<6>[   14.120000] usbcore: registered new interface driver cdc_ether
<6>[   14.130000] ip_tables: (C) 2000-2006 Netfilter Core Team
<6>[   14.160000] usbcore: registered new interface driver pl2303
<6>[   14.160000] usbserial: USB Serial support registered for pl2303
<6>[   14.170000] PPP generic driver version 2.4.2
<6>[   14.180000] NET: Registered protocol family 24
<6>[   14.190000] usbcore: registered new interface driver qmi_wwan
<6>[   14.200000] usbcore: registered new interface driver rndis_host
<6>[   14.200000] usbcore: registered new interface driver sierra_net
<6>[   14.220000] usbcore: registered new interface driver option
<6>[   14.230000] usbserial: USB Serial support registered for GSM modem (1-port)
<6>[   14.260000] ath9k_htc 1-1.1:1.0: ath9k_htc: HTC initialized with 33 credits
<6>[   14.500000] ath9k_htc 1-1.1:1.0: ath9k_htc: FW Version: 1.4
<6>[   14.500000] ath9k_htc 1-1.1:1.0: FW RMW support: On
<7>[   14.510000] ath: EEPROM regdomain: 0x0
<7>[   14.510000] ath: EEPROM indicates default country code should be used
<7>[   14.510000] ath: doing EEPROM country->regdmn map search
<7>[   14.510000] ath: country maps to regdmn code: 0x3a
<7>[   14.510000] ath: Country alpha2 being used: US
<7>[   14.510000] ath: Regpair used: 0x3a
<6>[   14.520000] ieee80211 phy1: Atheros AR9271 Rev:1
<4>[   19.410000] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
<6>[   24.390000] device eth0 entered promiscuous mode
<5>[   27.210000] random: nonblocking pool is initialized
<6>[   27.300000] eth0: link up (100Mbps/Full duplex)
<6>[   27.530000] br-lan: port 1(eth0) entered forwarding state
<6>[   27.540000] br-lan: port 1(eth0) entered forwarding state
<6>[   29.540000] br-lan: port 1(eth0) entered forwarding state
<6>[   30.130000] device wlan0 entered promiscuous mode
<6>[   30.130000] br-lan: port 2(wlan0) entered forwarding state
<6>[   30.140000] br-lan: port 2(wlan0) entered forwarding state
<6>[   30.370000] device wlan0-1 entered promiscuous mode
<6>[   30.370000] br-lan: port 3(wlan0-1) entered forwarding state
<6>[   30.380000] br-lan: port 3(wlan0-1) entered forwarding state
<6>[   31.360000] br-lan: port 3(wlan0-1) entered disabled state
<6>[   32.140000] br-lan: port 2(wlan0) entered forwarding state
<6>[   33.820000] br-lan: port 3(wlan0-1) entered forwarding state
<6>[   33.820000] br-lan: port 3(wlan0-1) entered forwarding state
<6>[   35.820000] br-lan: port 3(wlan0-1) entered forwarding state
<6>[  151.890000] Bluetooth: Core ver 2.19
<6>[  151.890000] NET: Registered protocol family 31
<6>[  151.890000] Bluetooth: HCI device and connection manager initialized
<6>[  151.900000] Bluetooth: HCI socket layer initialized
<6>[  151.900000] Bluetooth: L2CAP socket layer initialized
<6>[  151.910000] Bluetooth: SCO socket layer initialized
<6>[  151.930000] usbcore: registered new interface driver btusb
<6>[  151.950000] Bluetooth: HCI UART driver ver 2.2
<6>[  151.950000] Bluetooth: HCI H4 protocol initialized
<6>[  151.960000] Bluetooth: HCI BCSP protocol initialized
<6>[  151.980000] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
<6>[  151.980000] Bluetooth: BNEP filters: protocol multicast
<6>[  151.980000] Bluetooth: BNEP socket layer initialized
<1>[  265.430000] CPU 0 Unable to handle kernel paging request at virtual address 00000048, epc == 8022dc50, ra == 81921398
<4>[  265.440000] Oops[#1]:
<4>[  265.440000] CPU: 0 PID: 1936 Comm: hcitool Not tainted 3.18.84 #147
<4>[  265.440000] task: 8185ce88 ti: 81814000 task.ti: 81814000
<4>[  265.440000] $ 0   : 00000000 fffffff8 82ae7a5c 000f0000
<4>[  265.440000] $ 4   : 82ae7a00 00000000 00790008 00790008
<4>[  265.440000] $ 8   : 00000001 84080018 8010c83c 00000b3b
<4>[  265.440000] $12   : 7fa8c758 76ffa3a0 0040cfd0 7fa8c778
<4>[  265.440000] $16   : 82ae7a00 00000000 00790008 80360000
<4>[  265.440000] $20   : 8033d100 00000001 00000000 00000000
<4>[  265.440000] $24   : 76fc1e50 76fda7d0                  
<4>[  265.440000] $28   : 81814000 81815e18 7fe92b60 81921398
<4>[  265.440000] Hi    : 00000003
<4>[  265.440000] Lo    : 00000000
<4>[  265.440000] epc   : 8022dc50 release_sock+0x58/0x15c
<4>[  265.440000]     Not tainted
<4>[  265.440000] ra    : 81921398 mgmt_reenable_advertising+0xc18/0x1420 [bluetooth]
<4>[  265.440000] Status: 1000dc03	KERNEL EXL IE 
<4>[  265.440000] Cause : 00800008
<4>[  265.440000] BadVA : 00000048
<4>[  265.440000] PrId  : 00019374 (MIPS 24Kc)
<4>[  265.440000] Modules linked in: bnep hci_uart btusb bluetooth pppoe ppp_async option iptable_nat usb_wwan sierra_net rndis_host qmi_wwan pppox ppp_generic pl2303 nf_nat_ipv4 nf_conntrack_ipv4 iptable_raw iptable_mangle iptable_filter ipt_REJECT ipt_MASQUERADE ipt_ECN ip_tables cdc_ether ax88179_178a asix xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_id xt_hl xt_ecn xt_dscp xt_conntrack xt_comment xt_TCPMSS xt_REDIRECT xt_NETMAP xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY x_tables usbserial usbnet ums_usbat ums_sddr55 ums_sddr09 ums_karma ums_jumpshot ums_isd200 ums_freecom ums_datafab ums_cypress ums_alauda slhc nf_reject_ipv4 nf_nat_masquerade_ipv4 nf_nat_ftp nf_nat nf_log_ipv4 nf_log_common nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack_ftp nf_conntrack crc_itu_t cdc_wdm cdc_acm sg nfsv3 nfs rtl8192cu rtl_usb rtl8192c_common rtlwifi rtl8187 rt2800usb rt2800lib rt2x00usb rt2x00lib crc_ccitt tun vfat fat lockd sunrpc grace ath9k_htc ath9k ath9k_common ath9k_hw ath mac80211 cfg80211 compat nls_utf8 nls_iso8859_1 nls_cp437 eeprom_93cx6 arc4 crypto_blkcipher usb_storage uhci_hcd ohci_platform ohci_hcd ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache usbcore nls_base usb_common crc16 mii aead crypto_hash
<4>[  265.440000] Process hcitool (pid: 1936, threadinfo=81814000, task=8185ce88, tls=7705e440)
<4>[  265.440000] Stack : c0796264 801cb5d4 000000a8 00000000 00000e40 00790008 400448d2 00790008
<4>[  265.440000] 	  82ae7a00 00000003 00000000 81921398 82b0e898 839fa634 839fa600 00000001
<4>[  265.440000] 	  00790004 80075764 839fa600 400448d2 00790008 00790008 400448d2 8022b1c0
<4>[  265.440000] 	  80373df8 800e9fc0 839fa600 00030002 00000001 8183c820 00790008 835ea2e0
<4>[  265.440000] 	  400448d2 8010c730 00100077 800ec1f8 835ea2c0 8010f510 76ff2114 80360000
<4>[  265.440000] 	  ...
<4>[  265.440000] Call Trace:
<4>[  265.440000] [<8022dc50>] release_sock+0x58/0x15c
<4>[  265.440000] [<81921398>] mgmt_reenable_advertising+0xc18/0x1420 [bluetooth]
<4>[  265.440000] [<8022b1c0>] sock_ioctl+0x2b0/0x30c
<4>[  265.440000] [<8010c730>] do_vfs_ioctl+0x4ec/0x5f8
<4>[  265.440000] [<8010c88c>] SyS_ioctl+0x50/0x94
<4>[  265.440000] [<80062b9c>] handle_sys+0x11c/0x140
<4>[  265.440000] 
<4>[  265.440000] 
<4>[  265.440000] Code: 24150001  ae00005c  ae000058 <8e220048> 8e320000  30430001  1060000a  ce400000  2403fffe 
<4>[  265.730000] ---[ end trace 6dfcc692ba99f866 ]---

===================================

That's as far as I could get, I have no idea how to analyze that issue further... would really appreciate some help ?

[Foxtrot]

The crash you're experiencing (seems) related to memory error/corruption. 

<1>[  265.430000] CPU 0 Unable to handle kernel paging request at virtual address 00000048, epc == 8022dc50, ra == 81921398

Did you compile with all the required kernel modules? 

The openWRT wiki page offers some good advice on bluetooth: https://wiki.openwrt.org/doc/howto/usb.bluetooth

[rosem]

I will check as soon as I can get back to working on it - I check the KMODs I loaded for dependencies and whether they were contained in lsmod already so there were no differences there. Basically to compile I ran make menuconfig and then enabled the bluetooth support in "Other modules" (by setting it to an "M"). Afterwards I moved the kernel modules over via scp and tried to load them.

"Naively" I would expect insmod to fail if I'm missing dependencies...?

[Zylla]

On 8/20/2018 at 7:52 AM, rosem said:

I will check as soon as I can get back to working on it - I check the KMODs I loaded for dependencies and whether they were contained in lsmod already so there were no differences there. Basically to compile I ran make menuconfig and then enabled the bluetooth support in "Other modules" (by setting it to an "M"). Afterwards I moved the kernel modules over via scp and tried to load them.

"Naively" I would expect insmod to fail if I'm missing dependencies...?

Did you also install the compiled kernel? Or simply the module?
If not, that can explain why you're kernel is crashing.

[Just_a_User]

31 minutes ago, Zylla said:

Did you also install the compiled kernel? Or simply the module?
If not, that can explain why you're kernel is crashing.

I was kinda under the impression that insmod a kmod package would load it into the kernel, is that not the case? sorry for noob assumption ?

[Zylla]

13 minutes ago, Just_a_User said:

I was kinda under the impression that insmod a kmod package would load it into the kernel, is that not the case? sorry for noob assumption ?

You are totally correct! ?
BUT, that kernel-module should also match the kernel itself. Not JUST the version number.
For example: Le'ts say i compile a version of kernel 3.18.20 (with modules), and you do the same thing. Then i try to install a module that you compiled.
A crash can still occur as the kernels (+modules) aren't necessarily 100% identical.
I'm certain that the MD5 checksum of our kernels would not match. Same with the modules. Due to alot of compile-time reasons. ?

Edited August 22, 2018 by Zylla

[Just_a_User]

Thank you for that, its still a bit of a gray area for me so I'm not confident about these things still.

35 minutes ago, Zylla said:

BUT, that kernel-module should also match the kernel itself. Not JUST the version number.

Could it be that the kmod packages in chaos calmer opkg repo may not have matching kernel versions?

Edited August 22, 2018 by Just_a_User

[Zylla]

43 minutes ago, Just_a_User said:

Thank you for that, its still a bit of a gray area for me so I'm not confident about these things still.

Could it be that the kmod packages in chaos calmer opkg repo may not have matching kernel versions?

The Pineapple is built with a customized version of OpenWRT.
The final firmware uses openwrt's repository, and Hak5's repo. to download packages with opkg, as well as kernel-packages.

The kernel-packages needed for the Pineapple doesn't exist on OpenWRT's repos, as the Pineapple is built with a higher kernel version than the ones on OpenWRT.
But imo. Hak5 should compile them and host them on their repos. But i'm not sure why they don't do that with every package.

[Just_a_User]

Great that's the part i didn't understand. thank you for that @Zylla

[rosem]

16 hours ago, Zylla said:

Did you also install the compiled kernel? Or simply the module?
If not, that can explain why you're kernel is crashing.

You are absolutely right - nope, I didn't install my recompiled kernel ? I thought I can't (because then I would lose the Pineapple stuff) - but it's just the kernel itself so yeah... Will do that on the weekend, have to recompile it again since I tried different compilation configurations for the module...

[rosem]

@Zylla Maybe it's a stupid question but: How to install my own kernel? ? If I understood it correctly, to get my own kernel installed I would have to flash my own firmware onto the Pineapple and thus loosing the default Pineapple stuff (like WebInterface, configuration, etc.) - since the firmware upgrade process would clean out everything. Is that correct or did I just miss something...?

Maybe also @Foxtrot could lend a word here... especially if the provide bluetooth modules for their compiled kernel somewhere else.

[Colincolin343]

On 8/26/2018 at 3:41 AM, rosem said:

@Zylla Maybe it's a stupid question but: How to install my own kernel? ? If I understood it correctly, to get my own kernel installed I would have to flash my own firmware onto the Pineapple and thus loosing the default Pineapple stuff (like WebInterface, configuration, etc.) - since the firmware upgrade process would clean out everything. Is that correct or did I just miss something...?

Maybe also @Foxtrot could lend a word here... especially if the provide bluetooth modules for their compiled kernel somewhere else.

You got it figured out yet?