UnKn0wnBooof Posted August 31, 2015 Posted August 31, 2015 I was reading http://wiki.wifipineapple.com/#!build_guide.md but it seems that it isn't the full source code to the Pineapple. Why is this? Why are we being restricted like this? All hackers should know by now that restrictions is a No No. Why can't we hack the Pineapple? Why can't we modify parts of the system without losing functionality? The current source code seems to only provide the necessary resources to build a standard, boring openwrt image. I believe that we could take better advantage of the MKV if we actually had the full source, no? Quote
phpsystems Posted August 31, 2015 Posted August 31, 2015 Probably not, no. Most of it is open source, but some of it is covered by NDAs with the chip manufactures. Going totally open source has other draw backs too. Just look at the hackrf and the hackrf blue. Quote
UnKn0wnBooof Posted August 31, 2015 Author Posted August 31, 2015 Probably not, no. Most of it is open source, but some of it is covered by NDAs with the chip manufactures. Going totally open source has other draw backs too. Just look at the hackrf and the hackrf blue. Hm,I haven't looked into the hackrf so I wouldn't know of the drawbacks. That's a bummer ._. Was still hoping on a custom kernel. Quote
phpsystems Posted August 31, 2015 Posted August 31, 2015 Hackrf blue came out shortly after the hackrf. No design change or improvement, just a lower cost. While I bought a hackrf through a reseller to support the developer, many people wouldn't. As for the custom kernel, do you need to customize it, or just build modules for it? Quote
UnKn0wnBooof Posted August 31, 2015 Author Posted August 31, 2015 (edited) Hackrf blue came out shortly after the hackrf. No design change or improvement, just a lower cost. While I bought a hackrf through a reseller to support the developer, many people wouldn't. As for the custom kernel, do you need to customize it, or just build modules for it? Oh, I see. As for the kernel, I was hoping to make changes so it would mount a file system on the SD card, as the root fs. This would eliminate the 3MB limitation that I currently have. Was also hoping to build a WiFi driver into it, so my small edimax wifi adapter would be compatible. Those are literally the only 2 things I want to change: The filesystem that is mounted and add a wifi driver. The Raspberry Pi is capable of loading a kernal from the SD card then mount a USB drive as the root file system, I don't see how it wouldn't be possible to do the same to the Pineapple: Kernal on internal storage and everything else on the SD card. Edited August 31, 2015 by Lavanoid Quote
phpsystems Posted August 31, 2015 Posted August 31, 2015 The edimax can be a module (see the link I sent in your other post. Changing the root fs should be a case of changing fstab (or equivalent). Shouldn't need to customize the kernel for that. Quote
UnKn0wnBooof Posted August 31, 2015 Author Posted August 31, 2015 The edimax can be a module (see the link I sent in your other post. Changing the root fs should be a case of changing fstab (or equivalent). Shouldn't need to customize the kernel for that. Thanks :) I can't find anything in fstab that relates to what mounts the root (/) file system. I checked both /etc/fstab and /etc/config/fstab I always thought that such a config was stored in the kernel itself, correct me if I'm wrong tho. Quote
phpsystems Posted August 31, 2015 Posted August 31, 2015 Actually, the file is /etc/config/fstab. All you have to do is change the mount point to / http://wiki.openwrt.org/doc/uci/fstab Quote
phpsystems Posted August 31, 2015 Posted August 31, 2015 Just one last thing, if this goes wrong you may need to unbrick / reflash it. Make sure you can do that before you replace the config. Quote
UnKn0wnBooof Posted September 1, 2015 Author Posted September 1, 2015 Actually, the file is /etc/config/fstab. All you have to do is change the mount point to / http://wiki.openwrt.org/doc/uci/fstab Thanks, will do that :) I'll reply if something happens. Just one last thing, if this goes wrong you may need to unbrick / reflash it. Make sure you can do that before you replace the config. Yeah, it'll probably brick if I forget to put the filesystem onto my SD card. Will do that first, then edit the config :) Quote
phpsystems Posted September 1, 2015 Posted September 1, 2015 Don't forget to copy over the correct permissions / users and groups! Quote
UnKn0wnBooof Posted September 1, 2015 Author Posted September 1, 2015 Don't forget to copy over the correct permissions / users and groups! Will do. Still compiling OpenWRT so I can get the kernel module ._. Quote
UnKn0wnBooof Posted September 1, 2015 Author Posted September 1, 2015 Okay, OpenWRT is just a pain in the ass ._. It won't compile. cmp: /home/lavanoid/openwrt/build_dir/target-mips_34kc_musl-1.1.10/linux-ar71xx_generic/linux-4.1.6/include/linux/ath9k_platform.h: No such file or directory Makefile:2049: recipe for target '/home/lavanoid/openwrt/build_dir/target-mips_34kc_musl-1.1.10/linux-ar71xx_generic/compat-wireless-2015-07-21/.configured_ynnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnynyynnnynyynnnnnnnnnnnnnyyyyyyyy' failed make[2]: *** [/home/lavanoid/openwrt/build_dir/target-mips_34kc_musl-1.1.10/linux-ar71xx_generic/compat-wireless-2015-07-21/.configured_ynnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnynyynnnynyynnnnnnnnnnnnnyyyyyyyy] Error 2 make[2]: Leaving directory '/home/lavanoid/openwrt/package/kernel/mac80211' package/Makefile:191: recipe for target 'package/kernel/mac80211/compile' failed make[1]: *** [package/kernel/mac80211/compile] Error 2 make[1]: Leaving directory '/home/lavanoid/openwrt' /home/lavanoid/openwrt/include/toplevel.mk:181: recipe for target 'package/compile' failed make: *** [package/compile] Error 2 lavanoid@lavanoid-VirtualBox:~/openwrt$ :( Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.