Related
We are looking for users that is still on STOCK ROM and Kernel. BOTH AT&T and Roger. We are trying to see what errors are in STOCK so we can crush out bugs we might have introduce in modified Kernel or ROM
If you are a user still running STOCK ROM/KERNEL please run this command and post your dump.txt files
adb logcat -d *:E > dump.txt
You must have adb running. USB Drivers installed either by KIES package or Samsung USB Package, ADB should be in your folder if you used Zergberg Root method. Or can be downloaded via the Android SDK package
Your help will only future help the developing
mbze430 said:
We are looking for users that is still on STOCK ROM and Kernel. BOTH AT&T and Roger. We are trying to see what errors are in STOCK so we can crush out bugs we might have introduce in modified Kernel or ROM
If you are a user still running STOCK ROM/KERNEL please run this command and post your dump.txt files
adb logcat -d *:E > dump.txt
You must have adb running. USB Drivers installed either by KIES package or Samsung USB Package, ADB should be in your folder if you used Zergberg Root method. Or can be downloaded via the Android SDK package
Your help will only future help the developing
Click to expand...
Click to collapse
Here ya go
oh ok lol thank u i found it dugh
silver03wrx said:
im trying to do this i keep getting the message the process cannot access the file because it is being used by another process?. i did adb kill-server then adb start server it started then i typed in adb logcat -d *:E > dump.txt. and i can not find the dang text file on my sd card lol sorry have not used adb much
Click to expand...
Click to collapse
the text file will be located in the directory where you ran the command from and not in the sdcard or in the phone
ok thanks bud here ya go
Attached my dump file.
I may need to google some of the crap that was in it.
Alright guys, I was on an irc channel when I considered posting this since it's rather important. There has been a lot of disappointing posts all over the forum with people complaining about bugs, while not providing any kind of information for the developers aside from "X doesn't work" or "I get random reboots".
Well, without the proper knowledge, how are we going to fix it? We don't know what kernel you may be running, what version number you're on, or any information that the system spits out to let you know there's an error. So, I decided to start this thread, to hopefully teach newbies how to give us (developers) proper knowledge when complaining about issues.
This thread will have 3 sections, Logcat (App / system debug log.), Dmesg (active kernel output) and last_ksmg (Typically if you get a random reboot or something of that sort {this is the same as dmesg except it gets the info from the last shutdown [like a kernel panic]})
Section 1: Logcat
This log should almost always be included just because it provides more info than just saying something doesn't work. It will essentially tell you which apps are crashing and why and it also gives output of what they're doing. (Your system is running through apps, the dialer, wireless radio's, etc are all ran through apps.) so, if something is general, like a system force close, please just include a logcat.
How to get a logcat:
Well, this is REALLY simple, all you need to do is just get adb up and running (google how to do that, I don't feel like writing a 'how to use adb' tutorial for everyone's phone.) and then type
Code:
adb logcat
then you just right click, select, and paste to the thread. It's really that simple!
Section 2: Dmesg
This is getting into issues such as wifi not working, sleep of death, etc. Basically, things that make us go "OH F***" when we use our devices. Note: You will need adb access for this to work, same as logcat.
What this will do is get us live kernel output so we can know things like "What driver is the kernel loading {or not loading for that matter}" and similar things. This is linux, so kernel output is important if a hardware aspect isn't working right.
How to get a dmesg:
This is simple as well, no matter what operating system you're on (mac, windows, linux) just type
Code:
adb shell dmesg > dmesg.txt
and then it will have written the output to a .txt file in your current directory. Either paste the contents to the thread, or attach it to your post.
You can also get the dmesg by using terminal emulator. Instead though, you dont type adb shell, you need to also include it to somewhere you will be able to save it. Like /sdcard so, the command goes
Code:
dmesg > /sdcard/dmesg.txt
Just get it off your sdcard and get the contents to the developer!
Section 3: last_kmsg
Ok, the last thing is last_kmsg. When android kernels crash, they right to last_kmsg so then you can find out what's going on. This is usually for issues such as random reboots and other various kernel panic symptoms. A kernel panic happens when the kernel tries to do something it can't. It doesn't mean wrong permissions, it could just have errored out on something and died which can cause a few things. Anyway, developers REALLY need this if debugging a kernel because it gives us a viable way to see WHAT it's trying to do instead of trying to guess what it is trying to do
How to get a last_kmsg:
This is super simple and the same on all phones no matter what, what you need is adb up and running (or terminal emulator) and either in adb shell, or terminal emulator just type
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
or you can do
Code:
adb shell cat /proc/last_kmsg > kmsg.txt
and that will write it to your current working directory from cmd.
Hopefully, this way we developers can have our lives be a little bit easier and you can learn more about android.
I'm glad to have written this and devs, feel free to link to this guide as a "bug reporting FAQ"
HALP! I BRICKD MY FONE!!1!
I JAILBROKED IT LAST NIGHT AND NOW I NO GET SIGNEL!! PLASE HALP!!!1
but on a more serious note, good tut
Thanks dude!!! I was looking for some kind of guide. Only thing I still don't understand is when are we supposed to give dmesg and when do we give the logcat? I understand the last_kmsg is for kernel panics and random reboots, but the rest two are still ambiguous to me... Could you please explain the other two in a simpler way with an easy example for each?... Sorry.. I'm a noob... but am trying to learn these things..
There also is this app called 'Bootlog Uptime' that tries to auto-detect a crash and subsequently exports the log to sdcard.
When I get in to cmd in bootloader mode and type adb shell cat /proc/last_kmsg > kmsg.txt, I get a message Error: Device not found. I checked the ADB drivers, the are loading well. Am I doing something wrong?
If you're in boot loader mode, that's not adb.
Sent from my Full Android on Crespo4G using xda premium
anshumandash said:
When I get in to cmd in bootloader mode and type adb shell cat /proc/last_kmsg > kmsg.txt, I get a message Error: Device not found. I checked the ADB drivers, the are loading well. Am I doing something wrong?
Click to expand...
Click to collapse
You need to boot into the ROM, then grab the logs.
Sent from my GT-I9100 using xda app-developers app
Thank you for this
Sent from my Nexus 4 using Xparent BlueTapatalk 2
Can someone help me please.
I am from the HTC One S (Ville C2) community. I am testing a new kernel by one of the devs who doesnt have the phone. Now after installing the new kernel the phone is on bootloop. I need to extract the last_kmsg. the only way I can get out of the boot loop to do anything is by pressing the power button and simulate battery out. This it seems erases the last_kmsg cuz when I enter recovery to get it. It either says no such file or sometimes ends up showing me the recovery kernels last_kmsg. I am at a total loss as to how I the last_kmsg file.
There is also no way to install a working boot image as the kernel uses a zip to install files on the phone so we must use recovery to restore to previous state. This leads to the original condition. I tried looking for a solution but cant find it anywhere.
I tried the above method (via the Terminal Emulator) for finding the last_kmsg (my phone had just rebooted) and it says "/system/bin/sh: cat: /proc/last_kmsg: No such file or directory"
And Indeed, there is no last_kmsg file in my proc folder. Is there something I have to do to create it in the first place?
Thanks!
piyush_soni said:
I tried the above method (via the Terminal Emulator) for finding the last_kmsg (my phone had just rebooted) and it says "/system/bin/sh: cat: /proc/last_kmsg: No such file or directory"
And Indeed, there is no last_kmsg file in my proc folder. Is there something I have to do to create it in the first place?
Thanks!
Click to expand...
Click to collapse
I have the same problem.
Nexus 7-16 GB, PA 3.00, faux kernel 16 ultimate
Just solved the last kmsg problem. Instead of making the terminal do the job and getting "there is no such directory", just go above one level from sdcard and find proc folder. There will be a file named last_kmsg.
Hope it helps someone
Nexus 7-16 GB, PA 3.00, faux kernel 16 ultimate
---------- Post added at 10:13 AM ---------- Previous post was at 10:08 AM ----------
piyush_soni said:
I tried the above method (via the Terminal Emulator) for finding the last_kmsg (my phone had just rebooted) and it says "/system/bin/sh: cat: /proc/last_kmsg: No such file or directory"
And Indeed, there is no last_kmsg file in my proc folder. Is there something I have to do to create it in the first place?
Thanks!
Click to expand...
Click to collapse
Wait a few minutes it will be there
Nexus 7-16 GB, PA 3.00, faux kernel 16 ultimate
Kaiyes said:
Just solved the last kmsg problem. Instead of making the terminal do the job and getting "there is no such directory", just go above one level from sdcard and find proc folder. There will be a file named last_kmsg.
Click to expand...
Click to collapse
Kaiyes said:
Wait a few minutes it will be there
Click to expand...
Click to collapse
Nope. It's still not there for me ... I have a file called kmsg, but not last_kmsg.
Good stuff!
I'm on JB 4.3, Galaxy Note 2 and I've Flash Davil Kernel.
Two Bugs for me:
1) when the Phone, in switch off, is charging... the LED will not light. No Red Light (when in charging), nor Green one, when it has reached the 100%.
2) When Phone is connect to PC it isn't recognized by the PC in any way. To transfer files I have to use some app via Wi-Fi.
Are Two knows Bugs? Thanks in advance.
Hey glowerita I have this same problem minus the devil kernel. I don't think devil works with the FTW rom
Sent from my SPH-L900 using Tapatalk
Aquarius169 said:
Hey glowerita I have this same problem minus the devil kernel. I don't think devil works with the FTW rom
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
Hi! About PC recognize I've done so and now it's ok.
With Terminal emulator digit;
su
Press Enter.
Now digit; setprop persist.sys.usb.config mtp,adb
Enter, exit and reboot device and PC. [emoji1]
About led light... have you same problem like me?
Inviato dal mio GT-I9100 utilizzando Tapatalk
Take a look at
https://play.google.com/store/apps/details?id=com.bassel.andylog
... [email protected]
dmesg kmsg not permitted
Here's the dmesg.txt file when issuing C:\platform-tools>adb shell dmesg > dmesg.txt
"klogctl: Operation not permitted"
So I tried:
"C:\platform-tools>adb shell
←7←[r←[999;999H←[[email protected]:/ $ su
su
←7←[r←[999;999H←[[email protected]:/ # dmesg > dmesg.txt
dmesg > dmesg.txt
sh: can't create dmesg.txt: Read-only file system"
Results of issuing "C:\platform-tools>cat /proc/last_kmsg > /sdcard/last_kmsg.txt
The system cannot find the path specified.
C:\platform-tools>adb shell cat /proc/last_kmsg > kmsg.txt
/system/bin/sh: cat: /proc/last_kmsg: Operation not permitted"
Same results running terminal on phone also.
-Running PecanCM's CM11 Beta10 on LG L5 e610-
So neat and simple. Thanks for clarifying that.
Hi everyone, I'm trying to Install busybox,SuperUser and SU Binaries on my OUYA ...
I Have:
-ADB set up and working(wired)
-Downloded and unzipped the needed files
-Placed unzipped files in /android-sdk/platform-tools
Then i run the following commands to make sure my console is connected:
-adb kill-server
-echo 0x2836
-adb start-server
-adb devices
After 'adb devices' I see a number(My console #), which signifies my connected console...
Then i run the following commands to put SU in the proper place:
-adb shell
-su
-mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
-exit
-exit
-adb push su /sdcard/su<-----here is where i get an error (cannot stat 'su': No Such Files Or Directory :crying What am i doing wrong here/ i don't get it!...Can anyone please help me?
cronikman84 said:
Hi everyone, I'm trying to Install busybox,SuperUser and SU Binaries on my OUYA ...
I Have:
-ADB set up and working(wired)
-Downloded and unzipped the needed files
-Placed unzipped files in /android-sdk/platform-tools
Then i run the following commands to make sure my console is connected:
-adb kill-server
-echo 0x2836
-adb start-server
-adb devices
After 'adb devices' I see a number(My console #), which signifies my connected console...
Then i run the following commands to put SU in the proper place:
-adb shell
-su
-mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
-exit
-exit
-adb push su /sdcard/su<-----here is where i get an error (cannot stat 'su': No Such Files Or Directory :crying What am i doing wrong here/ i don't get it!...Can anyone please help me?
Click to expand...
Click to collapse
:good:never mind i figured it out...but when i go to Run SuperUser on the OUYA (Make > Software > SuperUser) and allow it to update, it gives me an error saying---->there was an error installing superuser. please send a log of the error to the developer. what now?
cronikman84 said:
:good:never mind i figured it out...but when i go to Run SuperUser on the OUYA (Make > Software > SuperUser) and allow it to update, it gives me an error saying---->there was an error installing superuser. please send a log of the error to the developer. what now?
Click to expand...
Click to collapse
Never mind LMAO...i got it :victory:
cronikman84 said:
Never mind LMAO...i got it :victory:
Click to expand...
Click to collapse
How'd you get it?! I'm stuck here too, thanks!
thanamesjames said:
How'd you get it?! I'm stuck here too, thanks!
Click to expand...
Click to collapse
Are you stuck at the error saying---->"there was an error installing superuser" still? cause if you are i think i can help you..., just on your ouya head over to MANAGE-SYSTEM-ADVANCED and scroll down to apps and delete the BUSYBOX FREE and SUPERUSER APPS...after that's done just repeat the commands again and reboot the system, then go click on MAKE>SOFTWARE>SUPERUSER and allow it to UPDATE but not from recovery and if that doesn't work let me know and ill tell you what to do next...BUT if your stuck at "adb push su /sdcard/su cannot stat 'su': No Such Files Or Directory" error then i can also help you...let me know, it's very simple, less than a minute
cronikman84 said:
Are you stuck at the error saying---->"there was an error installing superuser" still? cause if you are i think i can help you..., just on your ouya head over to MANAGE-SYSTEM-ADVANCED and scroll down to apps and delete the BUSYBOX FREE and SUPERUSER APPS...after that's done just repeat the commands again and reboot the system, then go click on MAKE>SOFTWARE>SUPERUSER and allow it to UPDATE but not from recovery and if that doesn't work let me know and ill tell you what to do next...BUT if your stuck at "adb push su /sdcard/su cannot stat 'su': No Such Files Or Directory" error then i can also help you...let me know, it's very simple, less than a minute
Click to expand...
Click to collapse
Hi,
I'm at the point where I've installed 'superuser' apk via adb. I've rebooted the console, gone to MAKE>SOFTWARE>SUPERUSER but when I click on 'install', I just get the error message: "There was an error installing Superuser. Please send a log to the error to the developer" but there are no logs.
Any ideas?
diazamet said:
Hi,
I'm at the point where I've installed 'superuser' apk via adb. I've rebooted the console, gone to MAKE>SOFTWARE>SUPERUSER but when I click on 'install', I just get the error message: "There was an error installing Superuser. Please send a log to the error to the developer" but there are no logs.
Any ideas?
Click to expand...
Click to collapse
yes, the best way to do it is with this tool OUYA toolbox and you can find it over here-----> http://forum.xda-developers.com/showthread.php?t=2350900 follow the instructions plug in your OUYA to your pc and download the test version of the tool, open it, click on install superuser and install it, then istall busybox and install it...then go to make- software-superuser and Update but not from recovery, then plug you OUYA back on to the pc and run the ouya toolbox program again and root(if you want to), you will be all set with SuperUser apk and busybox apk and root working perfect with no errors...
cronikman84 said:
yes, the best way to do it is with this tool OUYA toolbox and you can find it over here-----> http://forum.xda-developers.com/showthread.php?t=2350900 follow the instructions plug in your OUYA to your pc and download the test version of the tool, open it, click on install superuser and install it, then istall busybox and install it...then go to make- software-superuser and Update but not from recovery, then plug you OUYA back on to the pc and run the ouya toolbox program again and root(if you want to), you will be all set with SuperUser apk and busybox apk and root working perfect with no errors...
Click to expand...
Click to collapse
I think I might have found the issue. I think I forgot to copy the 'su' executable from /sdcard to /system/xbin. I've copied the correct 'su' executable to /system/xbin now. I'll have to test it later, I'm connected remotely at the moment so I can only do the shell stuff, I can't run Superuser.
What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?
diazamet said:
I think I might have found the issue. I think I forgot to copy the 'su' executable from /sdcard to /system/xbin. I've copied the correct 'su' executable to /system/xbin now. I'll have to test it later, I'm connected remotely at the moment so I can only do the shell stuff, I can't run Superuser.
What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?
Click to expand...
Click to collapse
:good: i hope you found the issue...i was having the same issue as you "There was an error installing Superuser. Please send a log to the error to the developer" and no matter what i tried it wouldn't work, so i just downloaded the OUYA toolbox test version and it took me less then 1 minutes to have superuser apk and busybox apk running and rooted, i didn't know you were connected remotely, i had mines connected straight up with the usb cable and it makes it easier for me..."What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?" <----yes, i'm 90% sure that the native SU is crippled in some type of way, and i've heard other people confirm this.
cronikman84 said:
:good: i hope you found the issue...i was having the same issue as you "There was an error installing Superuser. Please send a log to the error to the developer" and no matter what i tried it wouldn't work, so i just downloaded the OUYA toolbox test version and it took me less then 1 minutes to have superuser apk and busybox apk running and rooted, i didn't know you were connected remotely, i had mines connected straight up with the usb cable and it makes it easier for me..."What is the difference between the nativesu and the su copied from the attachment on this thread. There is a significant difference in size. Is the native su crippled in someway?" <----yes, i'm 90% sure that the native SU is crippled in some type of way, and i've heard other people confirm this.
Click to expand...
Click to collapse
Yep. That was the problem. I guess I thought I'd copied the correct version of 'su' across without checking properly.
diazamet said:
Yep. That was the problem. I guess I thought I'd copied the correct version of 'su' across without checking properly.
Click to expand...
Click to collapse
Sweet!!...glad you got it fixed... I knew that the native SU was crippled the first time i tried it...that's why i tried the OUYA toolbox cause i knew people had success with SU on that toolbox, so i gave it a try and SU was workin...tha's how i knew something was wrong with the native SU...
Can someone who has an Essential Phone (PH-1) upload a zip of the system dump. Run the command below in ADB to pull the dump (no root required):
Code:
adb pull /system PH1_system_dump
The dump will be pulled to a folder called "PH1_system_dump". Zip and upload that folder so we can begin development on this device.
I just tried...it stopped at 18% with the following message:
adb: error: failed to copy '/system/vendor/firmware/msadp' to 'PH1_system_dump/system/vendor/firmware/msadp': remote open failed: Permission denied
cabegol said:
I just tried...it stopped at 18% with the following message:
adb: error: failed to copy '/system/vendor/firmware/msadp' to 'PH1_system_dump/system/vendor/firmware/msadp': remote open failed: Permission denied
Click to expand...
Click to collapse
Try to pull like this:
Code:
adb pull /system/app PH1_system_apps
Code:
adb pull /system/priv-app PH1_system_priv_app
Code:
adb pull /system/framework PH1_system_framework
Code:
adb pull /system/media PH1_system_media
Code:
adb pull /system/etc PH1_system_dump_etc
Shawn5162 said:
Try to pull like this:
Code:
adb pull /system/app PH1_system_apps
Code:
adb pull /system/priv-app PH1_system_priv_app
Code:
adb pull /system/framework PH1_system_framework
Code:
adb pull /system/media PH1_system_media
Code:
adb pull /system/etc PH1_system_dump_etc
Click to expand...
Click to collapse
Here you go, this is off of the newest update, NMJ20D. The zip contains only system apps, priv_system apps, framework, and media.
Extracting /system/etc gave me this error, may be an error on my side but I'm not sure:
Code:
adb: error: cannot create 'PH1_system_etc\firmware\TFA9891.cnt': No such file or directory
I tried a workaround (specifying a folder rather than extracting to root), and it ended with this:
Code:
adb: error: failed to copy '/system/etc/firmware/wlan/qca_cld/wlan_mac.bin' to 'C:\Users\bmg10\Documents\dump\etc\firmware\wlan\qca_cld\wlan_mac.bin': open failed: Permission denied
DOWNLOAD
bmg1001 said:
Here you go, this is off of the newest update, NMJ20D. The zip contains only system apps, priv_system apps, framework, and media.
Extracting /system/etc gave me this error, may be an error on my side but I'm not sure:
Code:
adb: error: cannot create 'PH1_system_etc\firmware\TFA9891.cnt': No such file or directory
I tried a workaround (specifying a folder rather than extracting to root), and it ended with this:
Code:
adb: error: failed to copy '/system/etc/firmware/wlan/qca_cld/wlan_mac.bin' to 'C:\Users\bmg10\Documents\dump\etc\firmware\wlan\qca_cld\wlan_mac.bin': open failed: Permission denied
DOWNLOAD
Click to expand...
Click to collapse
Without root and factory images, I think this is the best we'll be able to get via ADB. This should be enough for a starting point though. Thanks for your help
Shawn5162 said:
Here you go, this is off of the newest update, NMJ20D. The zip contains only system apps, priv_system apps, framework, and media.
Extracting /system/etc gave me this error, may be an error on my side but I'm not sure: I tried a workaround (specifying a folder rather than extracting to root), and it ended with this:
Without root and factory images, I think this is the best we'll be able to get via ADB. This should be enough for a starting point though. Thanks for your help
Click to expand...
Click to collapse
Someone in this thread managed to get the boot.img. I downloaded it and tried rooting it with Magisk but it didn't work. He already has TWRP and Lineage but they're still unreleased as its being worked on. I can't try the boot image anymore since I'm on the newest update and the image posted was for the previous update.
https://forum.xda-developers.com/essential-phone/help/bootloader-root-t3695583/page3
You need root to get actual dumps. Our TWRP is still only usable via adb since they're loading touchscreen firmware in userspace via a daemon that doesn't want to run without the rest of android up, otherwise we'd have released something.
We have dumps of the latest OTA (NMJ20D) already. If anyone is interested in contributing or following development of this device (TWRP/Lineage/etc) here's a link to our discord: https://discord.gg/DTtY2nb
Look on the post below the guy already pulled the zip file already. I pushed it to my device via adb.
invisiblek said:
You need root to get actual dumps. Our TWRP is still only usable via adb since they're loading touchscreen firmware in userspace via a daemon that doesn't want to run without the rest of android up, otherwise we'd have released something.
We have dumps of the latest OTA (NMJ20D) already. If anyone is interested in contributing or following development of this device (TWRP/Lineage/etc) here's a link to our discord: https://discord.gg/DTtY2nb
Click to expand...
Click to collapse
is the touchscreen daemon the last piece of the TWRP puzzle? Can it be manipulated with vol + - and power buttons?
Hi all,
I've followed the threads at https://forum.xda-developers.com/showthread.php?t=2003836 and https://forum.xda-developers.com/showthread.php?t=2502559 to the best of my ability but can't seem to get this to work for the life of me! I'm stuck on the part where insmod is used to load the md4.ko and cifs.ko modules. I get "insmod: failed to load /system/lib/modules/<module name>: Permission denied" errors in either case.
I have ensured that I am properly rooted, BusyBox 1.26.2 is installed to /system/bin and /system is mounted as read-write. All relevant files/directories have 777 permissions and I am running these commands as root. So what else could be the problem??
I've tried this from both Terminal Emulator on the phone itself, and also from an adb shell on my PC. Can't use adb localhost on the phone as it doesn't seem to be installed (I get "sush: adb: not found" when trying to run "adb").
Curiously, running the insmod command and having it fail seems to remount /system as read-only again (prompt changes from "zeroflte:/ #" to "1|zeroflte:/ #", which it was before the first remount). Could this have anything to do with the issue?
MTIA as I've been tearing my hair out for the best part of a day trying to figure out what the %$#& I'm doing wrong!
Kernel modules needs to be compiled for the specified kernel that you are currently using on your phone. If the insmod detects that the module is not compiled for the kernel that the device currently running on, it wont allow to load them. But in that case, if I remember correctly, a different error should be shown instead of "Permission denied" error (at least it was like that on kernel 2.6.xx, may it had been changed on 3.xx).
Or with a very low chance, maybe the SELinux prevents the insmodding the modules.
forumber2 said:
Kernel modules needs to be compiled for the specified kernel that you are currently using on your phone.
Click to expand...
Click to collapse
OK, how would I go about rebuilding the kernel myself? I have TWRP installed and know how to flash the resulting image, but have no idea where to even start with kernel modification and haven't been able to find much on the subject for my specific device.
forumber2 said:
But in that case, if I remember correctly, a different error should be shown instead of "Permission denied" error (at least it was like that on kernel 2.6.xx, maybe it has been changed on 3.xx).
Click to expand...
Click to collapse
Does that mean that even if I could bypass the permission denied error, I would be likely to get other errors? If so, should I simply give up on trying to get those modules to work?
forumber2 said:
Or with a very low chance, maybe the SELinux prevents the insmodding the modules.
Click to expand...
Click to collapse
I have tried "setenforce 0" and "setenforce Permissive" just in case those commands might help, but neither one did (getenforce returned "Enforcing" after running either command as root).