[KERNEL] Kernel (deprimed_test) - Break It If You Can

[jaycemiskel]

Hey prime, I'm using the primed kernel and I can't get link2sd to work. I keep getting a mount script error. It says
Mount script cannot be created.
mount: mounting /dev/block/vold/179:2 on /data/sdext2 failed: No such device

 

[jerroedr]

It's going to be a slow week likely, it's spring break and I have three kids @home.

Just an update on what to expect this week, maybe I can finally work on my overclock app more.. or primed... or.. chameleon.

i say chameleon if that is the deprimed finalized. frees you up for future endeavorers

 

[prime]

Hey prime, I'm using the primed kernel and I can't get link2sd to work. I keep getting a mount script error. It says
Mount script cannot be created.
mount: mounting /dev/block/vold/179:2 on /data/sdext2 failed: No such device

what is the output of 'fdisk -l'

 

[jaycemiskel]

Hey prime, I'm using the primed kernel and I can't get link2sd to work. I keep getting a mount script error. It says
Mount script cannot be created.
mount: mounting /dev/block/vold/179:2 on /data/sdext2 failed: No such device

what is the output of 'fdisk -l'

Do I need to input that into the terminal? I did and nothing happened it just went to another line.

Sent from my Droid using Tapatalk

 

[prime]

Hey prime, I'm using the primed kernel and I can't get link2sd to work. I keep getting a mount script error. It says
Mount script cannot be created.
mount: mounting /dev/block/vold/179:2 on /data/sdext2 failed: No such device

what is the output of 'fdisk -l'

Do I need to input that into the terminal? I did and nothing happened it just went to another line.

Sent from my Droid using Tapatalk

make that

'fdisk -l /dev/block/mmcblk0'

 

[jaycemiskel]

what is the output of 'fdisk -l'

Do I need to input that into the terminal? I did and nothing happened it just went to another line.

Sent from my Droid using Tapatalk

make that

'fdisk -l /dev/block/mmcblk0'

export PATH=/data/local/bin:$PATH
$ export PATH=/data/local/bin:$PATH
$su
# fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1860 14940418+ b Win95 FAT32
/dev/block/mmcblk0p2 1861 1936 610470 83 Linux
#

Sent from my Droid using Tapatalk

 

[sbenson]

I'm pretty much a noob when it comes to kernels and had a couple questions about them.

I'm running the deprimed kernel with the primed script - now is there a way that I can verify that the primed script is indeed working (i.e. ULV). I know when I first ran the primed script in the terminal it displayed some information about the voltages, ect. I've rebooted several times and just want to make sure that the primed script is still intact.

Another question - I created a script base off of primed but with slightly lower voltages and my phone seems to really like it. Now obviously when I reboot my phone reverts back to primed. Is there a way to make my new script stick after a reboot? I read a lot about editing a 20overclock file but I don't fully understand? Can anyone put it in simple terms? Do I need to get Root Explorer - or something else to edit this? Thanks in advance!

One last thing. It's mentioned in the op that the MSOC app is no longer needed to run scripts. Do I need this app for anything else or will I ever? I uninstalled it and just wanted to ask if I should have kept it.

 

[Bear in NM]

Sbenson,

I am a little rusty on each of Prime's new methods, as I just run his test kernel straight up. If you are using the script method, to see what you phone is running at, in terminal:

cat /proc/overclock/freq_table
cat /proc/overclock/mpu_opps

These should return your overclock values if using a init.d script. And the init file should be in /etc/init.d on your phone. You can edit the file with root explorer, or you can do the same on a PC with Notepad++ if using windows (regular notepad will not work), and copy it over and chmod correctly.

And once you are doing the advanced Prime "stuff", msoc is indeed not needed.

Craig

 

[jaycemiskel]

Do I need to input that into the terminal? I did and nothing happened it just went to another line.

Sent from my Droid using Tapatalk

make that

'fdisk -l /dev/block/mmcblk0'

export PATH=/data/local/bin:$PATH
$ export PATH=/data/local/bin:$PATH
$su
# fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 15.9 GB, 15931539456 bytes
255 heads, 63 sectors/track, 1936 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1860 14940418+ b Win95 FAT32
/dev/block/mmcblk0p2 1861 1936 610470 83 Linux
#

Sent from my Droid using Tapatalk

Nevermind, I figured it out. I just input
mount /dev/block/mmcblk0p2 /data/sdext2
What would be the best way to make this run at startup?

 

[dmbfan36_23]

EDIT: nevermind, the bootloop was something else...

 

[sbenson]

Sbenson,

I am a little rusty on each of Prime's new methods, as I just run his test kernel straight up. If you are using the script method, to see what you phone is running at, in terminal:

cat /proc/overclock/freq_table
cat /proc/overclock/mpu_opps

These should return your overclock values if using a init.d script. And the init file should be in /etc/init.d on your phone. You can edit the file with root explorer, or you can do the same on a PC with Notepad++ if using windows (regular notepad will not work), and copy it over and chmod correctly.

And once you are doing the advanced Prime "stuff", msoc is indeed not needed.

Craig

Excellent, those were exactly what I was looking for and they worked like a charm. Is the file you're referring to the 20overclock file? I don't have root explorer yet (thinking I should probably just get it), is there an easy way to do this without? Also, what is chmod?

 

[c4Blimtizle]

why cant i keep my overclock when i reboot when i run the primed script or the overclock script or even run them together i loose my oc every reboot. wtf?

 

[chikimonke]

why cant i keep my overclock when i reboot when i run the primed script or the overclock script or even run them together i loose my oc every reboot. wtf?

Are you giving the terminal super user permission? ie. are you typing in "su" first? And primed is what will keep it persistent, overclock does it just for the current boot of the phone. But I believe in order to keep it persistent, it needs to right the file to a normally RO directory, hence the need for super user permissions.

hope that helps, and someone correct me if this is incorrect.

 

[DMal9782]

why cant i keep my overclock when i reboot when i run the primed script or the overclock script or even run them together i loose my oc every reboot. wtf?

I had this prob yest, reinstall the rom then kernel, no wipe, it goes away

 

[prime]

You must be su to run primed or overclock.