Discussion:
Surface Pro3 Benchmark issue(Only single-core can be used)in x86-r2
'Patrick Wirth' via Android-x86
2018-06-09 23:40:11 UTC
Permalink
I found that entry in the file but what do i have to edit to get 4 cores useable?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2018-06-10 01:51:50 UTC
Permalink
unpack pack ramdisk.imgedit init.rc

# this ensures that the cpusets are present and usable, but the device's
# init.rc must actually set the correct cpus
mkdir /dev/cpuset/foreground
write /dev/cpuset/foreground/cpus 0-3
write /dev/cpuset/foreground/mems 0
mkdir /dev/cpuset/foreground/boost
write /dev/cpuset/foreground/boost/cpus 0-3
write /dev/cpuset/foreground/boost/mems 0
mkdir /dev/cpuset/background
write /dev/cpuset/background/cpus 0-3
write /dev/cpuset/background/mems 0

# system-background is for system tasks that should only run on
# little cores, not on bigs
# to be used only by init, so don't change system-bg permissions
mkdir /dev/cpuset/system-background
write /dev/cpuset/system-background/cpus 0-3
write /dev/cpuset/system-background/mems 0

mkdir /dev/cpuset/top-app
write /dev/cpuset/top-app/cpus 0-3
write /dev/cpuset/top-app/mems 0

圚 2018幎6月10日星期日 UTC+8䞊午7:40:11Patrick Wirth写道
Post by 'Patrick Wirth' via Android-x86
I found that entry in the file but what do i have to edit to get 4 cores useable?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Alfu s
2018-06-10 15:30:12 UTC
Permalink
I have successfully edit new init.rc and unpack pack ramdisk.imgboot
successfully but the issue still havebenchmark only core 0 is being used.
圚 2018幎6月10日星期日 UTC+8䞊午9:51:50youling 257写道
Post by youling 257
unpack pack ramdisk.imgedit init.rc
# this ensures that the cpusets are present and usable, but the device's
# init.rc must actually set the correct cpus
mkdir /dev/cpuset/foreground
write /dev/cpuset/foreground/cpus 0-3
write /dev/cpuset/foreground/mems 0
mkdir /dev/cpuset/foreground/boost
write /dev/cpuset/foreground/boost/cpus 0-3
write /dev/cpuset/foreground/boost/mems 0
mkdir /dev/cpuset/background
write /dev/cpuset/background/cpus 0-3
write /dev/cpuset/background/mems 0
# system-background is for system tasks that should only run on
# little cores, not on bigs
# to be used only by init, so don't change system-bg permissions
mkdir /dev/cpuset/system-background
write /dev/cpuset/system-background/cpus 0-3
write /dev/cpuset/system-background/mems 0
mkdir /dev/cpuset/top-app
write /dev/cpuset/top-app/cpus 0-3
write /dev/cpuset/top-app/mems 0
圚 2018幎6月10日星期日 UTC+8䞊午7:40:11Patrick Wirth写道
Post by 'Patrick Wirth' via Android-x86
I found that entry in the file but what do i have to edit to get 4 cores useable?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Alfu s
2018-06-10 16:11:28 UTC
Permalink
I try delete Android-x86 7.1-r2 init.rc all of cpuset line.

find init.rc cpuset line in Android-x86 7.1-r1.iso and add to r2 init.rc
then unpack pack ramdisk.img to boot system.

lucky it works so good :)

I guess r2‘s cpuset parameter have issues.

圚 2018幎6月10日星期日 UTC+8䞊午9:51:50youling 257写道
Post by youling 257
unpack pack ramdisk.imgedit init.rc
# this ensures that the cpusets are present and usable, but the device's
# init.rc must actually set the correct cpus
mkdir /dev/cpuset/foreground
write /dev/cpuset/foreground/cpus 0-3
write /dev/cpuset/foreground/mems 0
mkdir /dev/cpuset/foreground/boost
write /dev/cpuset/foreground/boost/cpus 0-3
write /dev/cpuset/foreground/boost/mems 0
mkdir /dev/cpuset/background
write /dev/cpuset/background/cpus 0-3
write /dev/cpuset/background/mems 0
# system-background is for system tasks that should only run on
# little cores, not on bigs
# to be used only by init, so don't change system-bg permissions
mkdir /dev/cpuset/system-background
write /dev/cpuset/system-background/cpus 0-3
write /dev/cpuset/system-background/mems 0
mkdir /dev/cpuset/top-app
write /dev/cpuset/top-app/cpus 0-3
write /dev/cpuset/top-app/mems 0
圚 2018幎6月10日星期日 UTC+8䞊午7:40:11Patrick Wirth写道
Post by 'Patrick Wirth' via Android-x86
I found that entry in the file but what do i have to edit to get 4 cores useable?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2018-06-10 20:09:02 UTC
Permalink
圚 2018幎6月10日星期日 UTC+8䞊午9:51:50youling 257写道
Post by youling 257
unpack pack ramdisk.imgedit init.rc
# this ensures that the cpusets are present and usable, but the device's
# init.rc must actually set the correct cpus
mkdir /dev/cpuset/foreground
write /dev/cpuset/foreground/cpus 0-3
write /dev/cpuset/foreground/mems 0
mkdir /dev/cpuset/foreground/boost
write /dev/cpuset/foreground/boost/cpus 0-3
write /dev/cpuset/foreground/boost/mems 0
mkdir /dev/cpuset/background
write /dev/cpuset/background/cpus 0-3
write /dev/cpuset/background/mems 0
# system-background is for system tasks that should only run on
# little cores, not on bigs
# to be used only by init, so don't change system-bg permissions
mkdir /dev/cpuset/system-background
write /dev/cpuset/system-background/cpus 0-3
write /dev/cpuset/system-background/mems 0
mkdir /dev/cpuset/top-app
write /dev/cpuset/top-app/cpus 0-3
write /dev/cpuset/top-app/mems 0
圚 2018幎6月10日星期日 UTC+8䞊午7:40:11Patrick Wirth写道
Post by 'Patrick Wirth' via Android-x86
I found that entry in the file but what do i have to edit to get 4 cores useable?
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
'Patrick Wirth' via Android-x86
2018-06-10 17:10:44 UTC
Permalink
how did you unpack and repack ramdisk.img?
IÂŽm just trying the whole day to get it to work.
I followed this guide to do the job:
https://access.redhat.com/solutions/24029

After replacing the ramdisk.img with my modified version, android x86
doesnÂŽt boot anymore...
Can you upload your image?
Maybe it works
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Alfu s
2018-06-10 18:15:56 UTC
Permalink
i use ubuntu and run gunzip ramdisk.img, edit init.rc and cpio new img

or try this unpack image,it works on i5 4300u ,

i just test in *CM-x86-14.1-r2*. Google Drive New ramdisk.img
<https://drive.google.com/file/d/1yXUDSO1mOhyyxOZ7S6kQRs9S5V2jgivE/view?usp=sharing>

rm -r old ramdisk.img and cp new ramdisk.img or use the CM-x86-14.1-r2.iso replace
ramdisk.img to reinstall android x86

圚 2018幎6月11日星期䞀 UTC+8䞊午1:10:44Patrick Wirth写道
Post by 'Patrick Wirth' via Android-x86
how did you unpack and repack ramdisk.img?
IÂŽm just trying the whole day to get it to work.
https://access.redhat.com/solutions/24029
After replacing the ramdisk.img with my modified version, android x86
doesnÂŽt boot anymore...
Can you upload your image?
Maybe it works
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2018-06-10 19:57:20 UTC
Permalink
I see you remove mount cpuset none /dev/cpusetcpuset won't workyou break
it !

圚 2018幎6月11日星期䞀 UTC+8䞊午2:15:56Alfu s写道
Post by Alfu s
i use ubuntu and run gunzip ramdisk.img, edit init.rc and cpio new img
or try this unpack image,it works on i5 4300u ,
i just test in *CM-x86-14.1-r2*. Google Drive New ramdisk.img
<https://drive.google.com/file/d/1yXUDSO1mOhyyxOZ7S6kQRs9S5V2jgivE/view?usp=sharing>
rm -r old ramdisk.img and cp new ramdisk.img or use the CM-x86-14.1-r2.iso
replace ramdisk.img to reinstall android x86
圚 2018幎6月11日星期䞀 UTC+8䞊午1:10:44Patrick Wirth写道
Post by 'Patrick Wirth' via Android-x86
how did you unpack and repack ramdisk.img?
IÂŽm just trying the whole day to get it to work.
https://access.redhat.com/solutions/24029
After replacing the ramdisk.img with my modified version, android x86
doesnÂŽt boot anymore...
Can you upload your image?
Maybe it works
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
youling 257
2018-06-10 20:05:34 UTC
Permalink
you break it ! cpuset won't work

it should be on init然后换行对霐空栌䞍是换行以后盎接write啥啥啥䜠这根本没甚语法错误

for
examplehttps://github.com/me176c-dev/android_device_asus_me176c/blob/cm-14.1/init/root/init.me176c.rc
on late-init
write /dev/cpuset/foreground/cpus 0-2
write /dev/cpuset/foreground/boost/cpus 0-3
write /dev/cpuset/background/cpus 0
write /dev/cpuset/system-background/cpus 0-1
write /dev/cpuset/top-app/cpus 0-3

圚 2018幎6月11日星期䞀 UTC+8䞊午2:15:56Alfu s写道
Post by Alfu s
i use ubuntu and run gunzip ramdisk.img, edit init.rc and cpio new img
or try this unpack image,it works on i5 4300u ,
i just test in *CM-x86-14.1-r2*. Google Drive New ramdisk.img
<https://drive.google.com/file/d/1yXUDSO1mOhyyxOZ7S6kQRs9S5V2jgivE/view?usp=sharing>
rm -r old ramdisk.img and cp new ramdisk.img or use the CM-x86-14.1-r2.iso
replace ramdisk.img to reinstall android x86
圚 2018幎6月11日星期䞀 UTC+8䞊午1:10:44Patrick Wirth写道
Post by 'Patrick Wirth' via Android-x86
how did you unpack and repack ramdisk.img?
IÂŽm just trying the whole day to get it to work.
https://access.redhat.com/solutions/24029
After replacing the ramdisk.img with my modified version, android x86
doesnÂŽt boot anymore...
Can you upload your image?
Maybe it works
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
'Patrick Wirth' via Android-x86
2018-06-10 18:35:59 UTC
Permalink
Your image works as expected! thank you!
DonÂŽt know what was wrong with my image, maybe wrong compression or
whatever.
My linux skills are very "noob" basics
--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86+***@googlegroups.com.
To post to this group, send email to android-***@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.
Loading...