What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

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

Prime -- What version of busybox should I be running? Link or site appreciated.

If you're running the supercharger script, definitely not the latest busybox. Check the script thread for more info or the latest versions actually check busybox for you.

- onDroid
 
I tried posting this issue in liquids section: I love Prime's kernel been using it for ages at this point and haven't had any issues with it so far but I flashed liquids 3.0 and 3.1 and I keep getting monster screen wake lag. Is this a scheduler issue or something baked deep in deprimed? or is it a config tweak somewhere I don't know about? I switched to noop as a scheduler with no better result. Any developer type knowledge into this would be much appreciated
 
I tried posting this issue in liquids section: I love Prime's kernel been using it for ages at this point and haven't had any issues with it so far but I flashed liquids 3.0 and 3.1 and I keep getting monster screen wake lag. Is this a scheduler issue or something baked deep in deprimed? or is it a config tweak somewhere I don't know about? I switched to noop as a scheduler with no better result. Any developer type knowledge into this would be much appreciated

You ever run it on liquid before? Liquid rom isn't nearly as stable as other roms. For some phones and some setups it can either run awesomely or be super buggy and lagging.

supercharged modified liquid 3.1 w/turbocharged 3g
Pete's 5 slot lv 1.25GHz w/ kickasskernel tweaks
19.8 linpack score
1856 quadrant score
 
You ever run it on liquid before? Liquid rom isn't nearly as stable as other roms. For some phones and some setups it can either run awesomely or be super buggy and lagging.

supercharged modified liquid 3.1 w/turbocharged 3g
Pete's 5 slot lv 1.25GHz w/ kickasskernel tweaks
19.8 linpack score
1856 quadrant score

Not well that's for sure. I'm thinking that Prime has something built into his kernel that allows for "deep sleep" if you will and that while on any cm7 rom, MIUI, pete's gpa builds it doesn't seem to be an issue but on liquids roms this kernel can't seem to wake up

It's either that or possibly something do with the scheduler. pete and chevy I believe rock deadline as their scheduler and Prime's latest uses cfq/noop I think he abandoned deadline long ago and the BFS scheduler ate battery with some of the later cm7 builds
 
Last edited:
Hey prime I have a quick question about the I/O schedulers. Are there certain times when noop is better than deadline or vice versa?

supercharged modified liquid 3.0 w/turbocharged 3g
Pete's 5 slot lv 1.25GHz w/ kickasskernel tweaks
19.8 linpack score
1856 quadrant score
 
BFQ/S is a CPU scheduler, CFQ|noop|Deadline..etc are IO Schedulers.

What governor are you running?

Try http://bit.ly/deprimed_previous and see if it lags please.


Prime,

I run with Interactive and/or bumblebee typically rarely use ondemand. I've tried both your previous and current kernel revisions I believe the kernel reports them as #19 and #20 both with the same result on liquids rom..

on cm7 builds and winners build your kernel runs like a dream
 
Prime,

I was previously using the following 11link2sd script successfully:

Code:
umount /sd-ext 
modprobe ext4 
mount -t ext4 /dev/block/mmcblk0p2 /data/sdext2

today, after playing with v6 supercharger and changing a couple swap settings,(both things I do frequently) the sdext2 partition is not mounting.

I attempted to run the script and get the outputs, and they are as follows:

Code:
# ./11link2sd
umount: can't umount /sd-ext: Invalid argument
modprobe: chdir(/lib/modules): No such file or directory
mount: mounting /dev/block/mmcblk0p2 on /data/sdext2 failed: No such device

I have reflashed the kernel and CM7 to no avail. I also re-downloaded and copied the 05mountsd script you linked. I'm still unable to mount the partition. I ran the following command which came back clean:

Code:
 e2fsck -fpDC0 /dev/block/mmcblk0p2

The FAT32 partition is still mounting fine - I can see all my pictures, downloads, etc. However, all of my apps including titanium backup and android market are linked to SD, leaving me darn close to dead in the water.

Any Ideas?

Thanks in advance
 
Hey prime I have a quick question about the I/O schedulers. Are there certain times when noop is better than deadline or vice versa?

supercharged modified liquid 3.0 w/turbocharged 3g
Pete's 5 slot lv 1.25GHz w/ kickasskernel tweaks
19.8 linpack score
1856 quadrant score

Not in my experiences with embedded hardware.
 
Prime,

I run with Interactive and/or bumblebee typically rarely use ondemand. I've tried both your previous and current kernel revisions I believe the kernel reports them as #19 and #20 both with the same result on liquids rom..

on cm7 builds and winners build your kernel runs like a dream

Now try reprimed which should use deadline.
 
Prime,

I was previously using the following 11link2sd script successfully:

Code:
umount /sd-ext 
modprobe ext4 
mount -t ext4 /dev/block/mmcblk0p2 /data/sdext2

today, after playing with v6 supercharger and changing a couple swap settings,(both things I do frequently) the sdext2 partition is not mounting.

I attempted to run the script and get the outputs, and they are as follows:

Code:
# ./11link2sd
umount: can't umount /sd-ext: Invalid argument
modprobe: chdir(/lib/modules): No such file or directory
mount: mounting /dev/block/mmcblk0p2 on /data/sdext2 failed: No such device

I have reflashed the kernel and CM7 to no avail. I also re-downloaded and copied the 05mountsd script you linked. I'm still unable to mount the partition. I ran the following command which came back clean:

Code:
 e2fsck -fpDC0 /dev/block/mmcblk0p2

The FAT32 partition is still mounting fine - I can see all my pictures, downloads, etc. However, all of my apps including titanium backup and android market are linked to SD, leaving me darn close to dead in the water.

Any Ideas?

Thanks in advance

It seems as if busybox may be the culprit.

What's the console output of this command?

"which mount" and "busybox" (just revision on busybox)
 
It seems as if busybox may be the culprit.

What's the console output of this command?

"which mount" and "busybox" (just revision on busybox)

WHich mount:

/system/xbin/mount


busybox:

busybox v1.18.2



kevdog said:
What does mount say?

Code:
 # mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
/dev/block/mtdblock4 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock6 on /data type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock5 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock0 on /config type yaffs2 (ro,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
 
Last edited:
Try this instead:

Code:
busybox umount /sd-ext 
busybox insmod /system/lib/modules/ext4 
mount -t ext4 /dev/block/mmcblk0p2 /data/sdext2
 
Back
Top