Sorry, I assumed since you were posting to a kernel-related email list
that you had a dev phone, or a rooted one which allows access to
things such as insmod. You aren't going to be able to do any of this
without root access.
On Aug 12, 10:51 pm, perumal316 wrote:
> Hi Andrew,
>
> My main doubt i
Hi Andrew,
My main doubt is after changing how do I update the phone with the new
config? The only way is to recompile the kernel and using a developer
phone flash the new kernel image in. But how do update kernel of
locked phones (those bought from telcos)?
Thanks and Regards,
Perumal
On Aug 12
gunzip config.gz, and edit it with a text editor. If you have a kernel
source tree, put it in there named ".config", and do "make menuconfig"
to use the menu system to edit it. The latter method is probably the
easiest, but requires a kernel source tree.
On Aug 10, 5:06 am, perumal316 wrote:
> Hi
Hi Sven,
If I adb pull /proc/config.gz, I gets the config file. But how is it
possible for me to modify the configurations from the config file.
Just use wordpad to chnage the settings and adb push the new config?
Regards,
Perumal
On Aug 10, 5:33 pm, "Sven Killig" wrote:
> > -Original Messa
I mean kernel version can be known from the phone and it can then be
used to compile the module accordingly. But now how to load it in.
Does it mean that in all phone sold from telcos, kernel modules cannot
be loaded?
Thanks In Advance,
Perumal
On Aug 10, 3:26 pm, Chong Yang wrote:
> that's impo
Hi,
If I am not mistaken, you have to rebuilt the kernel enabling module
loading/unloading settings. You may want to google on how to rebuilt
Linux kernel.
Regards,
Perumal
On May 28, 4:21 am, rohan raizada wrote:
> Yes I did insmod <.ko> but it gave me Permission denied. I am trying to load
>
On Thu, May 27, 2010 at 1:21 PM, rohan raizada wrote:
> Yes I did insmod <.ko> but it gave me Permission denied.
Why do you think this happened?
Hint, look at the error it gave you, and ponder why that might be...
> I am trying to load
> the module into the kernel and see the output of it using
Yes I did insmod <.ko> but it gave me Permission denied. I am trying to load
the module into the kernel and see the output of it using dmesg.
Thanks,
Rohan.
On Thu, May 27, 2010 at 4:04 PM, Greg KH wrote:
> On Thu, May 27, 2010 at 11:34 AM, rohan raizada
> wrote:
> > Hi,
> >
> > I am unable to
On Thu, May 27, 2010 at 11:34 AM, rohan raizada
wrote:
> Hi,
>
> I am unable to run my LKM on the Google Dev Phone2. The thing that i tried
> was that I sent the .ko file to the phone using
>
> adb push <.ko file> /sdcard/module
>
> and when i tried executing it it simply said: Permission denied.
Hi,
I am unable to run my LKM on the Google Dev Phone2. The thing that i tried
was that I sent the .ko file to the phone using
adb push <.ko file> /sdcard/module
and when i tried executing it it simply said: Permission denied. How do i
get my module to work on the phone that I have.
Thanks,
Roh
Thanks Greg, Perumal and Pavan for your inputs .. finally i got it working
:-)
Thanks,
Rohan.
On Wed, May 26, 2010 at 12:46 PM, Pavan Savoy wrote:
> M=`pwd` should work from your present working directory ..
>
> On Wed, May 26, 2010 at 10:07 PM, rohan raizada
> wrote:
> > Hi,
> >
> > I created
M=`pwd` should work from your present working directory ..
On Wed, May 26, 2010 at 10:07 PM, rohan raizada
wrote:
> Hi,
>
> I created a Makefile as Greg suggested but even then it doesnt seem to work
> and now it seems to be giving me this error.
> The Makefile that I have is as follows:
>
> /***
Hi,
I created a Makefile as Greg suggested but even then it doesnt seem to work
and now it seems to be giving me this error.
The Makefile that I have is as follows:
/**/
myhome=/hom
Hi Rohan,
You can try using the below code in the Makefile:
ifeq ($(KERNELRELEASE),)
KERNELDIR ?= /home/
PWD := $(shell pwd)
.PHONY: build clean
build:
$(MAKE) -C $(KERNELDIR) M=$(PWD) modules
clean:
rm -rf *.o *~ core .depend .*.cmd *.ko *.mod.c
else
$(info Building with KER
Hi,
I currently working on a monitoring tool in a form of LKM, which I
want to use to monitor the system calls made and aruguments passed
during the calls.
I can access into the system call table and replace system calls
(using the LKM) but this is only for one system call.
Any idea how to captu
Thanks Mr Chew,
I managed to solve it. I didn't enable module unloading and forced
module unloading previously. After enabling and making the kernel
again, I can unload the modules.
Regards,
Perumal
On Nov 6, 10:22 am, Chew Esmero wrote:
> Haven't encountered that error. Try checking your kerne
Haven't encountered that error. Try checking your kernel .config and
include "Module unloading" & "Forced module
unloading" under the "Enable loadable module support" menu.
On Nov 6, 9:58 am, perumal316 wrote:
> Hi Mr Chew,
>
> When I rmmod my modules. i keep on getting "rmmod: delete_module
> f
Hi Mr Chew,
When I rmmod my modules. i keep on getting "rmmod: delete_module
failed (errno 38)" error message. Any idea what is causing this? My
exit portion of the code is similar to those I tried in Linux. It
works fine in Linux.
Regards,
Perumal
On Oct 30, 12:59 pm, Chew Esmero wrote:
> No p
No problem. Happy coding. =)
On Oct 30, 12:45 pm, Chew Esmero wrote:
> Oh, sorry. Didn't get it right.
>
> Terminal emulator in Android has no root privileges unfortunately. May
> I ask why would you do it in terminal emulator when you can do it in
> adb (already root)?
>
> On Oct 30, 12:30 pm,
Oh, sorry. Didn't get it right.
Terminal emulator in Android has no root privileges unfortunately. May
I ask why would you do it in terminal emulator when you can do it in
adb (already root)?
On Oct 30, 12:30 pm, perumal316 wrote:
> Hi Mr Chew,
>
> I have built the module against the goldfish k
Hi Mr Chew,
I have built the module against the goldfish kernel. Then I start the
emulator then in a terminal (adb shell) then insmod it and it is
working. But within the emulator there is a terminal emulator. If I
insmod there the module is not loaded ("Operation Not Permitted").
Since it is wor
Hi Perumal,
I'm confused when you say that it's already working in shell but not
in emulator. Working in shell meaning you insmod the hello.ko to your
host? If so, then the module was not properly built. If module is
properly built against the goldfish kernel, output module would be for
ARM archi
Hi,
I also faced similar problem, your MakeFile may need changes, below is
the makefile i used:
ifeq ($(KERNELRELEASE),)
KERNELDIR ?= /goldfish/kernel
PWD := $(shell pwd)
.PHONY: build clean
build:
$(MAKE) -C $(KERNELDIR) M=$(PWD) modules
clean:
rm -rf *.o *~ core .depend .*.
Hi Chew,
I'm a newbie in linux/android and Im having some problems to compile the my
module.
i dowloaded the android-goldfish-2.6.29 snapshot and the android plataform.
Compiled the kernel with your instructions to ARCH and CROSS_COMPILE and
have no problem, but when i try to compile the module it
By the way, I'm using SDK 1.5 and android-goldfish-2.6.27. I also
tested android-goldfish-2.6.29 and still ok. Haven't tried the with
1.6 but I think it's still applicable.
On Oct 29, 4:16 pm, Chew Esmero wrote:
> Only "Enable loadable module support". I think you really need to
> build your dri
Only "Enable loadable module support". I think you really need to
build your driver with KERNEL_DIR pointing to your goldfish kernel
directory and using the cross-compiler provided with Android source.
If not, your driver will be built using your host's kernel headers.
The output module is not rec
Hi,
I tried enabling the module support and boot the emulator using that
kernel but still getting the same error when insmod a module from the
terminal in emulator.
I also changing the Make file as specified and make the program but
get a long list of errors like "undeclared identifier" and cann
Yes, it is possible. Exec Format Error: it seems that your module is
not built using the headers of your goldfish kernel. Try this simple
makefile when building your new driver (assuming hello.c as source):
obj-m := hello.o
CROSS_COMPILE=arm-eabi-
KERNEL_DIR ?= ~/goldfish/kernel/
all:
$
Thanks,Yes, now it can be loaded when the emulator is booted with the
new kernel.
But must I always build the module against my new kernel and boot with
the new kernel to load a new module?
Is it possible to insmod , similar like in Linux to load a
module?
I have tried in emulator's terminal and
Did you build the module against your new kernel? (i.e. ARCH=arm
KERNEL_DIR=/kernel make). I've encountered that
error message before and it seems that the booted kernel still do not
allow "Enable Loadable Module" .config support. Are you sure emulator
is booted with the new kernel? (i.e. emulator
Emulator do not support modules. You will have to get that running on
a real hardware.
- Basil
On Oct 1, 1:09 am, perumal316 wrote:
> Hi,
>
> I want to load my own kernel modules into the Android. I downloaded
> the Android kernel source and change the config file to enable modules
> loading (C
31 matches
Mail list logo
