NFS support for Amazon Fire 5th gen ? - Fire Q&A, Help & Troubleshooting

I'm using the unofficial CM-12.1 rom by ggow, which works very well indeed. I note, however, that the kernel lacks support for NFS (no nfs modules are supplied). Since I am running a Linux based file server which already uses NFS, I'd prefer to use that rather than set up something for CIFS, which the kernel seems to support. Any ideas would be most appreciated.

Related

[Q] cifs.ko for the Captivate

Hello all,
Forgive me if this has been asked/requested before. Is there a version of the cifs.ko module that is compiled for any of the current custom ROMs? I am looking for this file or would like to know how to compile it for a custom ROM. It is used to mount Windows SMB fie shares to our Captivate. I am currently using Cog's 2.2 Beta 9 ROM but it does not have the cifs.ko file.
Programs such as File Expert or Cifsmanager can handle the mounting once the cifs.ko file is present.
Any help would be appreciated,
Thanks in advance for any advice or direction to solving this issue.
I think not only cifs.ko. For double bytes characters support, nls_utf8.ko is also a must. If anyone can compile based on froyo source, it'll be awesome.
agreed on the double byte char
agreed that second file is required but as a start the cifs.ko is required. Fingers crossed someone can assist us,
Wow! Dead subject I guess
I thought this would be provide some great functionality to our Captivates but I guess it's just the two of us who are interested in such features. The adventure was fun while it lasted.
Juxtyce
http://forum.xda-developers.com/showthread.php?t=774321
peep this guys
I'm using Serendipity 5.12 with the Speedmod K13C kernel, and it definitely includes CIFS. There's an option in CWM to enable/disable it. I've been using it quite a bit with CIFSManager and Mount Manager.
juxtyce said:
Hello all,
Forgive me if this has been asked/requested before. Is there a version of the cifs.ko module that is compiled for any of the current custom ROMs? I am looking for this file or would like to know how to compile it for a custom ROM. It is used to mount Windows SMB fie shares to our Captivate. I am currently using Cog's 2.2 Beta 9 ROM but it does not have the cifs.ko file.
Programs such as File Expert or Cifsmanager can handle the mounting once the cifs.ko file is present.
Any help would be appreciated,
Thanks in advance for any advice or direction to solving this issue.
Click to expand...
Click to collapse
Most newer Speedmod and Voodoo based kernels include support for CIFS natively. In fact, with Speedmod it's simply a tweak enabled via recovery. I don't use Voodoo, so I won't say for certain, but I think it's enabled by default in most of the newer builds.
Also, it's worth mentioning, that cifs.ko, and associated helpers tend to only work correctly on a specific build of Android. So taking the cifs.ko from an older 2.1 version of Android will probably NOT work on any of the newer JPX-range or JSX-range of ROMs.
Shammyh said:
Also, it's worth mentioning, that cifs.ko, and associated helpers tend to only work correctly on a specific build of Android. So taking the cifs.ko from an older 2.1 version of Android will probably NOT work on any of the newer JPX-range or JSX-range of ROMs.
Click to expand...
Click to collapse
Exactly. The kernel module (.ko file) needs to be compiled against the source of the rest of the kernel or it will not load. I highly doubt that you will find a CIFS or TUN (for OpenVPN) module that is compiled against a generic source (JPX, KB1, etc) just floating around here. All of the CIFS and TUN support that I've seen are built in to the kernels themselves. If you want these features it's as simple as flashing SuckerPunch, SpeedMod, Firebird 2, or any other kernel for the Captivate that has that support built in. I use Firebird 2 v0.8.
If you don't want to flash a kernel, you have another route. You need to figure out what kernel source you are running (the version, such as 2.6.32.9, will likely not be good enough - you'll need to know if it's JPX or KB1 or something else), find a Captivate kernel that is based on that version, and either download the kernel and extract the zImage file to get the modules or PM the author and they might be kind enough to give you just the modules that you are looking for. This route is way more work and not guaranteed to work, but Linux is all about choices and that is what makes it fu*king awesome.
Good luck!

[WIP] [SCRIPT]chroot for omap 4460 GNU/Linux compliant

Hi there!
I'm doing a script for chroot for an easy ongoing GNU/Linux Distro where all can fork it on github and make your own attempts.
A script chrooted like openembedded but it is not.
twitter.com/vicetechno
github.com/vic3t3chn0/zazyl_chroot
The github is where it lies the script.
This is an attempt of an ongoing GNU/Linux where everyone choose which software to package it.
I'll update the script every week.
Thank you so much.
Hi There
Obviously this is still in the early stages and I'm sure you have a plans but 1 question instantly spring to mind
1. How does this relates to Archos Tablets? ( other than the obvious that some G9's have an Omap4460 ) because there are a number of changes that Archos have made to the standard omap kernel. I'd be extremely but pleasantly surprised if you could boot a device using the pandaboard kernel.
This is the the repo for the official archos g9 kernel - git://gitorious.org/archos/archos-gpl-gen9-kernel-ics.git the linux-ics-3.0.21 is the current one in use by the stock firmware.
Myself and @Quallenauge made some further modifications which added a the ability the either boot off the internal or external ramdisk depending on the value of the androidboot.mode which can be passed via the kernel command line and essential turns sde mode into a dual boot mode while leaving standard archos recovery untouched as a safe guard.
@Quallenauge has also ported 3.0.31 and 3.0.58 and is in the process of creating a 3.4 version. All these kernel are located @ https://github.com/Quallenauge/kernel-archos
We are currently using 3.0.58 in the CM-10.1 Rom in this section but all of these should be considered unstable as they haven't been thoroughly
tested.
It's a good idea but not a small task. Also in it's Current state it is far too generic to be relevant to Archos Tablets.
Thanks
Trevd
Hi there!
To answer you.
Yes it is an early stage. To be related to gen9 archos tablets i want to build a own distro to get wiork on pandaboard also gen9 tablets.
I think i've answered you.
Don't hesitate to contact me.

Question about Nook HD hummingbird's CM kernel

I have been use Nook HD hummingbird for a while. There's no official CM rom for CM11 and later, I have tried CM11 which is buggy on HW video decode and it turns out that the last official CM (CM10.1) is so stable and it has the APPOPS!
As time pass by, I feel the performance of the rom is not good enough and I'm thinking about improving it. What I'm planning to do right now is compile a kernel only with CM10.1 source with Linaro toolchain and having -O3 and some other flags. However, it seems Nook HD and Nook HD+ has the same github for the kernel: http://www.github.com/cyanogenmod/android_kernel_bn_omap
Now I'm lost. Could anyone tell me why they share the same source?
Also, I heard that I need to extract some modules from the rom in order to have a recovery flashale zip. I haven't use any programming stuff in the last 12 years and I just find some tutorial about how to compile a kernel. If anyone can provide more information about how to use that source and make a flashable zip to apply the kernel to the CM rom will be greatly appreciated.
It will also be helpful if anyone can compile the kernel and apply some patches to it.
@amaces
@pinguy1982

help with gamepad support and loading xpad.ko

Hi all,
I have a rooted sm-t810 running stock marshmallow kernel 3.10.9.8374498 and I have been trying for a long time to add support for my xbox 360 wireless dongle and controllers.
I read a lot online about it and it seems that I need to load a specific module (xpad.ko) that is not available by default in my kernel.
However I have no idea where to find one that is compiled and compatible with my kernel and I have absolutely zero experience with compiling the kernel and/or the module from source, I wouldn't know where to begin or what to do about it.
From what I understand I should download the source of my kernel in a linux desktop, compile the module in it, copy the compiled module to my decide and run insmod it, but again, I have zero experience in all this.
Could somebody help me by giving me the compiled xpad.ko for my kernel?
If not, could you tell me step by step what should I do it to do it myself assuming im a total ignorant in kernels,modules, their compilation, the specifics about android, and everything around it ?(before yesterday I didn'teven ever rooted my tablet )
Thank you in advance if anybody is willing to help!
Cheers,
Mastro

Mainline Kernels

Hello all! Hope all is well by you.
Based on what I've seen on this forum, the latest available kernel for the Touchpad is version 3.4.x - an older, unmaintained LTS branch, forked from Qualcomm's repos.
It seems that the mainline kernel source has code for the MSM8660 platform (what the Touchpad is based on) which leads me to wonder if it's possible to get a mainline kernel running on the device.
If my optimism serves me right, this could open the doors to running more non-Android systems on the device!
So far my attempts at booting my compilations have yielded nothing more than a hang at the HP splash logo. I've tried different GCC versions from Linaro (targeting arm-eabi) to no avail.
I'm unsure if I'd need to tweak any DTBs, though the 3.4 kernels don't seem to make use of those.
Of course a splash logo isn't too verbose... might anyone know if there's a serial console I can access over USB or some hidden port internally? Has anyone else made a similar attempt with any progress?
Cheers!
PieGuy128 said:
Hello all! Hope all is well by you.
Based on what I've seen on this forum, the latest available kernel for the Touchpad is version 3.4.x - an older, unmaintained LTS branch, forked from Qualcomm's repos.
It seems that the mainline kernel source has code for the MSM8660 platform (what the Touchpad is based on) which leads me to wonder if it's possible to get a mainline kernel running on the device.
If my optimism serves me right, this could open the doors to running more non-Android systems on the device!
So far my attempts at booting my compilations have yielded nothing more than a hang at the HP splash logo. I've tried different GCC versions from Linaro (targeting arm-eabi) to no avail.
I'm unsure if I'd need to tweak any DTBs, though the 3.4 kernels don't seem to make use of those.
Of course a splash logo isn't too verbose... might anyone know if there's a serial console I can access over USB or some hidden port internally? Has anyone else made a similar attempt with any progress?
Cheers!
Click to expand...
Click to collapse
I am not an expert, but have learned a lot by tweaking the kernel for the Hp Touchpad. To my basic understating none of the native driver codes were release as they are not "open source". How the developers got it working is by tweaking the hardware from what is "based on". If the drivers where open source, it could possible be more helpful on getting a lot more done. All I can do is provide some links from others that had tried:
The LuneOS is using the same kernel branch as Android, but there is no development for the kernel:
https://www.webos-ports.org/wiki/Main_Page
https://www.webos-ports.org/wiki/Main_Page
It will be great to have a kernel to run Linux natively.
Here are some work around that others had used:
https://github.com/mikestaszel/ArchLinuxARM-TouchPad
https://github.com/CalcProgrammer1/kernel_tenderloin_debian
https://forum.xda-developers.com/showthread.php?t=2761381
I did the following videos running Ubuntu (arm) as Chroot and is very fast !
https://www.youtube.com/channel/UCKoir6bzzPU-Uq9UjcRR3hw
Good luck learning!
@PieGuy128
Take a look at this post from @elginsk8r about a possible 5.0 Kernel:
There is a 5.0 kernel floating around that looks promising (uses mesa rather than proprietary blobs for display) albeit missing some key hardware support in it's current state. If anyone would like to take a look at the kernel sources and see what can be done it can be found here https://github.com/flto/linux/tree/msm8660. Building and booting instructions are here https://github.com/flto/linux/wiki
original post:
https://forum.xda-developers.com/showpost.php?p=83040029&postcount=273

Categories

Resources