Page 24 of 28 FirstFirst ... 1419202122232425262728 LastLast
Results 461 to 480 of 552
Like Tree1Likes
  1. #461  
    lol
    <homerdrool>mmmmm....popcorn </homerdrool>

    Quote Originally Posted by rwhitby View Post
    This'll be good ...

    /me gets out the popcorn.

    -- Rod
  2. #462  
    Quote Originally Posted by rwhitby View Post
    Nope, I already showed in the other thread that the kernel is responding improperly to valid settings from Govnah ...

    -- Rod
    Funny I was teasing anyway.

    -- Sent from my Palm Pre using Forums
    Commodore Pet, Commodore 64&128, Amiga 4000, PC-7, Ubuntu, Treo 650. Treo 755p,Sprint Palm Pre Plus 2.2.4,2 Sprint Pre2 2.2.4, TouchPad 32gig.
  3.    #463  
    Quote Originally Posted by Xanadu73 View Post
    It seems I gooffed with a couple of the command lines more than I thought. I manually went back and added in colons in the output I noticed I missed. Guess I went too fast. The output itself is not typed. Copy & Pasted out of Konsole.


    M.
    download again, same place, and try again.

    Too bad Govnah isnt robust enough to handle my kernels.
    Live free or DIE!
  4. #464  
    Quote Originally Posted by unixpsycho View Post
    download again, same place, and try again.

    Too bad Govnah isnt robust enough to handle my kernels.

    I don't mean to drag this out this long. Custody court dictates when I spend time with my Son and when I don't...


    8aec1f44fe97de6d2032d9e3216104e2 uImage-av8b-05262011-4

    Linux My Pre 2.6.24-palm-joplin-3430 #AV8B-webOS-2.1.0-pre Tue May 24 15:34:25 EDT 2011 armv7l GNU/Linux


    Focusing on the parts that have been blowing up. MemBooted to the above kernel after a battery pull for a super fresh start. Govnah still not installed after the last test.

    Boots fine:

    Code:
    root@My Pre:/# for i in $(find /sys -type f -iname '*vdd*') ; do echo -n $i": " ; cat $i ; done
    /sys/devices/system/cpu/cpu0/cpufreq/vdemand/vdemand_vsel_vdd1: 68 64 60
    /sys/devices/system/cpu/cpu0/cpufreq/vdemand/vdemand_vsel_vdd2: 44 40 36
    /sys/devices/system/cpu/cpu0/cpufreq/vdemand/vdemand_vsel_vdd1_default: 68 64 60
    /sys/devices/system/cpu/cpu0/cpufreq/vdemand/vdemand_vsel_vdd2_default: 44 40 36
    /sys/devices/system/cpu/cpu0/cpufreq/override/vdd1_vsel_min: 25
    /sys/devices/system/cpu/cpu0/cpufreq/override/vdd1_vsel_max: 112
    /sys/devices/system/cpu/cpu0/cpufreq/override/vdd2_vsel_min: 25
    /sys/devices/system/cpu/cpu0/cpufreq/override/vdd2_vsel_max: 55
    /sys/power/sr_vdd1_autocomp: 0
    /sys/power/sr_vdd2_autocomp: 0
    /sys/power/vdd1_opp_value: 5
    /sys/power/vdd2_opp_value: 3
    root@My Pre:/# for i in $(find /sys -type f -iname '*freq*') ; do echo -n $i": " ; cat $i ; done
    /sys/devices/platform/lcd-controller/freq_change:  95133 93744 95133
    OK
    /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq: 500000
    /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq: 1005000
    /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq: 500000
    /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: 1005000
    /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies: 1005000 800000 500000 
    /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq: 1005000
    /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: 1005000
    /sys/class/i2c-adapter/i2c-2/2-0010/min_ext_clk_freq_mhz: 0x5004BFAE(1342488494)
    /sys/class/i2c-adapter/i2c-2/2-0010/max_ext_clk_freq_mhz: 0x8004BFAE(2147794862)
    /sys/class/i2c-adapter/i2c-2/2-0010/min_pll_ip_freq_mhz: 0x1005BFAE(268812206)
    /sys/class/i2c-adapter/i2c-2/2-0010/max_pll_ip_freq_mhz: 0x4005BFAE(1074118574)
    /sys/class/i2c-adapter/i2c-2/2-0010/min_pll_op_freq_mhz: 0xD005BFAE(3490037678)
    /sys/class/i2c-adapter/i2c-2/2-0010/max_pll_op_freq_mhz: 0x0006BFAE(442286)
    /sys/class/i2c-adapter/i2c-2/2-0010/min_vt_sys_clk_freq_mhz: 0x9006BFAE(2416361390)
    /sys/class/i2c-adapter/i2c-2/2-0010/max_vt_sys_clk_freq_mhz: 0xC006BFAE(3221667758)
    /sys/class/i2c-adapter/i2c-2/2-0010/min_vt_pix_clk_freq_mhz: 0xF006BFAE(4026974126)
    /sys/class/i2c-adapter/i2c-2/2-0010/max_vt_pix_clk_freq_mhz: 0x2007BFAE(537378734)
    /sys/class/input/input3/ledon_frequency: 18000
    /sys/class/input/input5/accelerometer_filter_frequency: 224
    /sys/class/rtc/rtc0/max_user_freq: 1
    Install Govnah (Just Type!). Initial load of Govnah looks OK (interesting though, there's no default profile listed in the profile list yet it displays "VDemand 1005" on the main screen):

    Freq: 500M/1G
    VDD1: 68 64 60
    VDD2: 44 40 36
    Poll: 0.3
    etc.

    Set my profile:
    VDD1: 64 62 59
    VDD2: Never touch anymore
    HighTemp: 52
    LowTemp: 49
    Override: True

    Apply.

    Luna restarted itself...

    After Luna restart, Govnah is reporting everything's OK though.

    Code:
    root@My Pre:/# for i in $(find /sys -type f -iname '*vdd*') ; do echo -n $i": " ; cat $i ; done
    /sys/devices/system/cpu/cpu0/cpufreq/vdemand/vdemand_vsel_vdd1: 64 62 59
    /sys/devices/system/cpu/cpu0/cpufreq/vdemand/vdemand_vsel_vdd2: 44 40 36
    /sys/devices/system/cpu/cpu0/cpufreq/vdemand/vdemand_vsel_vdd1_default: 68 64 60
    /sys/devices/system/cpu/cpu0/cpufreq/vdemand/vdemand_vsel_vdd2_default: 44 40 36
    /sys/devices/system/cpu/cpu0/cpufreq/override/vdd1_vsel_min: 25
    /sys/devices/system/cpu/cpu0/cpufreq/override/vdd1_vsel_max: 112
    /sys/devices/system/cpu/cpu0/cpufreq/override/vdd2_vsel_min: 25
    /sys/devices/system/cpu/cpu0/cpufreq/override/vdd2_vsel_max: 55
    /sys/power/sr_vdd1_autocomp: 0
    /sys/power/sr_vdd2_autocomp: 0
    /sys/power/vdd1_opp_value: 5
    /sys/power/vdd2_opp_value: 3
    root@My Pre:/# for i in $(find /sys -type f -iname '*freq*') ; do echo -n $i": " ; cat $i ; done
    /sys/devices/platform/lcd-controller/freq_change:  95133 93744 95133
    OK
    /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq: 500000
    /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq: 1005000
    /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq: 500000
    /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: 1005000
    /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies: 1005000 800000 500000 
    /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq: 1005000
    /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: 1005000
    /sys/class/i2c-adapter/i2c-2/2-0010/min_ext_clk_freq_mhz: 0x5004BFAE(1342488494)
    /sys/class/i2c-adapter/i2c-2/2-0010/max_ext_clk_freq_mhz: 0x8004BFAE(2147794862)
    /sys/class/i2c-adapter/i2c-2/2-0010/min_pll_ip_freq_mhz: 0x1005BFAE(268812206)
    /sys/class/i2c-adapter/i2c-2/2-0010/max_pll_ip_freq_mhz: 0x4005BFAE(1074118574)
    /sys/class/i2c-adapter/i2c-2/2-0010/min_pll_op_freq_mhz: 0xD005BFAE(3490037678)
    /sys/class/i2c-adapter/i2c-2/2-0010/max_pll_op_freq_mhz: 0x0006BFAE(442286)
    /sys/class/i2c-adapter/i2c-2/2-0010/min_vt_sys_clk_freq_mhz: 0x9006BFAE(2416361390)
    /sys/class/i2c-adapter/i2c-2/2-0010/max_vt_sys_clk_freq_mhz: 0xC006BFAE(3221667758)
    /sys/class/i2c-adapter/i2c-2/2-0010/min_vt_pix_clk_freq_mhz: 0xF006BFAE(4026974126)
    /sys/class/i2c-adapter/i2c-2/2-0010/max_vt_pix_clk_freq_mhz: 0x2007BFAE(537378734)
    /sys/class/input/input3/ledon_frequency: 18000
    /sys/class/input/input5/accelerometer_filter_frequency: 224
    /sys/class/rtc/rtc0/max_user_freq: 1
    Named my profile "H-Test3". Govnah displays it.

    /me beats on his desk for drum roll.

    Tapped "H-Test3" in the list. It did NOT blow up. All things look to have proper settings.

    Reboot with Govnah installed and displaying my saved Profile.

    Govnah displays my Profile!

    Code:
    root@My Pre:/# for i in $(find /sys -type f -iname '*vdd*') ; do echo -n $i": " ; cat $i ; done
    /sys/devices/system/cpu/cpu0/cpufreq/vdemand/vdemand_vsel_vdd1: 64 62 59
    /sys/devices/system/cpu/cpu0/cpufreq/vdemand/vdemand_vsel_vdd2: 44 40 36
    /sys/devices/system/cpu/cpu0/cpufreq/vdemand/vdemand_vsel_vdd1_default: 68 64 60
    /sys/devices/system/cpu/cpu0/cpufreq/vdemand/vdemand_vsel_vdd2_default: 44 40 36
    /sys/devices/system/cpu/cpu0/cpufreq/override/vdd1_vsel_min: 25
    /sys/devices/system/cpu/cpu0/cpufreq/override/vdd1_vsel_max: 112
    /sys/devices/system/cpu/cpu0/cpufreq/override/vdd2_vsel_min: 25
    /sys/devices/system/cpu/cpu0/cpufreq/override/vdd2_vsel_max: 55
    /sys/power/sr_vdd1_autocomp: 0
    /sys/power/sr_vdd2_autocomp: 0
    /sys/power/vdd1_opp_value: 5
    /sys/power/vdd2_opp_value: 3
    root@My Pre:/# for i in $(find /sys -type f -iname '*freq*') ; do echo -n $i": " ; cat $i ; done
    /sys/devices/platform/lcd-controller/freq_change:  95133 93744 95133
    OK
    /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq: 500000
    /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq: 1005000
    /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq: 500000
    /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: 1005000
    /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies: 1005000 800000 500000 
    /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq: 1005000
    /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: 1005000
    /sys/class/i2c-adapter/i2c-2/2-0010/min_ext_clk_freq_mhz: 0x5004BFAE(1342488494)
    /sys/class/i2c-adapter/i2c-2/2-0010/max_ext_clk_freq_mhz: 0x8004BFAE(2147794862)
    /sys/class/i2c-adapter/i2c-2/2-0010/min_pll_ip_freq_mhz: 0x1005BFAE(268812206)
    /sys/class/i2c-adapter/i2c-2/2-0010/max_pll_ip_freq_mhz: 0x4005BFAE(1074118574)
    /sys/class/i2c-adapter/i2c-2/2-0010/min_pll_op_freq_mhz: 0xD005BFAE(3490037678)
    /sys/class/i2c-adapter/i2c-2/2-0010/max_pll_op_freq_mhz: 0x0006BFAE(442286)
    /sys/class/i2c-adapter/i2c-2/2-0010/min_vt_sys_clk_freq_mhz: 0x9006BFAE(2416361390)
    /sys/class/i2c-adapter/i2c-2/2-0010/max_vt_sys_clk_freq_mhz: 0xC006BFAE(3221667758)
    /sys/class/i2c-adapter/i2c-2/2-0010/min_vt_pix_clk_freq_mhz: 0xF006BFAE(4026974126)
    /sys/class/i2c-adapter/i2c-2/2-0010/max_vt_pix_clk_freq_mhz: 0x2007BFAE(537378734)
    /sys/class/input/input3/ledon_frequency: 18000
    /sys/class/input/input5/accelerometer_filter_frequency: 224
    /sys/class/rtc/rtc0/max_user_freq: 1

    Is this a winner? Is this enough info/tests?


    M.
  5. #465  
    Sorry, forgot to test streaming audio (even though you already worked on that). I can stream audio just fine.

    I've gotten two Luna Restarts in this time. Dropping VDemand Poll Rate down to 0.2 seems to have gotten rid of it so far.


    M.
  6. #466  
    Quote Originally Posted by Xanadu73 View Post
    Is this enough info/tests?
    Enough to show Govnah was never at fault

    Thanks for being an effective alpha tester.

    -- Rod
    WebOS Internals and Preware Founder and Developer
    You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
    All donations go back into development.
    www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
  7. #467  
    Quote Originally Posted by rwhitby View Post
    Enough to show Govnah was never at fault

    Thanks for being an effective alpha tester.

    -- Rod
    You are quite welcome. Other than the delay in between tests, is there more/different/better info I could've posted to give the two of you what you need faster? I thought of everything I could that you two might need.


    M.
  8. #468  
    Hey!

    I have updated to AV8B-66. I have *none* of these issues. I haven't had a chance to stress test it yet, but, audio is fine, Govnah's happy, etc.

    Thank you, 'Psycho.


    M.
  9.    #469  
    Quote Originally Posted by Xanadu73 View Post
    Hey!

    I have updated to AV8B-66. I have *none* of these issues. I haven't had a chance to stress test it yet, but, audio is fine, Govnah's happy, etc.

    Thank you, 'Psycho.


    M.
    No. thank YOU. You are an effective alpha tester.
    Live free or DIE!
  10. #470  
    Hello. Just FYI... I ran into a compcache crash/incongruance that I believe is noteworthy: From a 'stock' kernel on a pre- 2.1.0 meta'd webos phone, I installed av8b. (power draw was great while active but seriously attacked battery life while on standby) I didn't test too much before freezes prompted a return to uber-ver.18. Went back to 'stock' through preware -- reboot -- installed uber through preware -- reboot.

    Any change made through govnah to compcache resulted in an 'invalid module format' error. I had to pull xvmalloc.ko file from meta-doctor archive to re-enable (winscp upload). I first tried several uninstalls/reinstalls with mutiple versions of both uber and av8b to no avail.

    I'm guessing the av8b preware/ipk install changes the xvmalloc.ko module somehow that doesn't revert during uninstall.
  11. #471  
    Quote Originally Posted by jnever1 View Post
    Hello. Just FYI... I ran into a compcache crash/incongruance that I believe is noteworthy: From a 'stock' kernel on a pre- 2.1.0 meta'd webos phone, I installed av8b. (power draw was great while active but seriously attacked battery life while on standby) I didn't test too much before freezes prompted a return to uber-ver.18. Went back to 'stock' through preware -- reboot -- installed uber through preware -- reboot.

    Any change made through govnah to compcache resulted in an 'invalid module format' error. I had to pull xvmalloc.ko file from meta-doctor archive to re-enable (winscp upload). I first tried several uninstalls/reinstalls with mutiple versions of both uber and av8b to no avail.

    I'm guessing the av8b preware/ipk install changes the xvmalloc.ko module somehow that doesn't revert during uninstall.
    How recent was your av8b installation?

    There was a bug in our packaging of kernels that affected this area for kernels that exist for both 1.4.5 and 2.1.0.

    That bug was fixed earlier this week and all kernels were rebuilt.

    -- Rod
    WebOS Internals and Preware Founder and Developer
    You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
    All donations go back into development.
    www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
  12. #472  
    Quote Originally Posted by rwhitby View Post
    How recent was your av8b installation?
    In alpha life spans... decades ago. I tested av8-64 from feeds Friday~Saturday (western hemi time). A storm came through Saturday night that knocked out my power for 3 days. This is the first opportunity I've had to browse the meta-doc on my home pc and ssh anything over wi-fi. If the fix happened over the weekend or early this week, I didn't experience it.
    Last edited by jnever1; 06/02/2011 at 08:50 PM. Reason: server lag double post
  13. #473  
    Quote Originally Posted by jnever1 View Post
    In alpha life spans... decades ago. I tested av8-64 from feeds Friday~Saturday (western hemi time). A storm came through Saturday night that knocked out my power for 3 days. This is the first opportunity I've had to browse the meta-doc on my home pc and ssh anything over wi-fi. If the fix happened over the weekend or early this week, I didn't experience it.
    Please try the compcache test again with the current kernel release (i.e. reinstall the kernel from the feed). The fix happened early this week.

    -- Rod
    WebOS Internals and Preware Founder and Developer
    You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
    All donations go back into development.
    www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
  14. #474  
    I like what I understand is the theory behind the variable voltage kernel. Perhaps someone can suggest some settings for me that I might make a more substantial go of it? Also, is there a more substantial info resource where I might learn more about how av8b works than the wiki? like what vdd1 and vdd2 mean, what 'system voltage' refers to in govnah etc? I work best when I understand the capabilities of my tools :-)

    I currently use uber-18
    USERSPACE low: 125, high: 1000, set point 600
    compache enabled: 16MB
    I/O: anticipatory
    TCP: westwood
    CPU voltages: 1000: (68) 800: (64) 720: (64) 600: (58) 500: (46) 250: (36) 125: (30)

    also applied Xanadu73's 'sysctl.conf' swap tweaks

    I am happy with performance, battery life, and stability under these stable uber-18 conditions but I'm always looking to squeeze as much power/mV as possible.
    Last edited by jnever1; 06/02/2011 at 08:53 PM.
  15.    #475  
    Quote Originally Posted by jnever1 View Post
    In alpha life spans... decades ago. I tested av8-64 from feeds Friday~Saturday (western hemi time). A storm came through Saturday night that knocked out my power for 3 days. This is the first opportunity I've had to browse the meta-doc on my home pc and ssh anything over wi-fi. If the fix happened over the weekend or early this week, I didn't experience it.

    I suffered with uber with no compcache on a webos2pre- during the power outage over av8b's excessive standby battery draw.

    I like what I understand is the theory behind the variable voltage kernel. Perhaps someone can suggest some settings for me that I might make a more substantial go of it?

    I currently use uber-18
    USERSPACE low: 125, high: 1000, set point 600
    compache enabled: 16MB
    I/O: anticipatory
    TCP: westwood
    CPU voltages: 1000: (68) 800: (64) 720: (64) 600: (58) 500: (46) 250: (36) 125: (30)

    also applied Xanadu73's 'sysctl.conf' swap tweaks

    I am happy with performance, battery life, and stability under these stable uber-18 conditions...
    AV8B-64 is old. As rwhitby mentioned, please test current kernels to see if your problems go away.
    Live free or DIE!
  16. #476  
    ver.66 resolved xvmalloc.ko disagreement across av8b<-->stock<-->uber.18 transitions.

    tested from uber.18 a few hours ago.

    uber.18:uninstall/reboot-->stock-->av8b.66:install/reboot-->(verify compcache enabled/alterable)-->av8b.66:uninstall/reboot-->stock-->uber:install/reboot-->(verify compcache enabled/alterable)-->uber:uninstall/reboot-->stock-->av8b.66:install/reboot

    I'm currently running av8b.66, 0.2 sec poll rate
    CPU: 500/800 (56 50 48)
    SYS: (42 36 34)

    I'm having some thermal issues that are leading to/causing HEAVY battery draw (in the order of 5%/10mins) while on 'stand-by/sleep.' At the extreme, this requires battery pull to free from a locked/frozen state. At the least, 52'C is hot! This is on my best OEM battery, properly/manually calibrated via dr.battery and hex edits to battery chip (1150mAh/100%). I've seen phone temps, while on charger, drop to 30~27'C which confuses the hell out of me compared to 51'C while on unplugged standby.

    I'm trying to narrow down conditions of reproducibility... no luck yet.

    How would I go about logging cpu/sys temp and potentially proximity sensor?

    How would I go about pulling that data from the log in a concise manner? lumberjack?

    I'm not versed in the "for i in $(" code... though I'm sure I could reverse engineer something.
    ------------------------------------------------------
    Aside from the thermal issue, I'm getting about the same battery draw with av8b.66, configured as described above, as with uber.18, configured as described in previous post. This is 800MHz vs 600MHz!

    I see TREMENDOUS improvement while using SuperNES emulator (Tactics Ogre). Battery draw is on the order of roughly 0.5~0.25%/min compared to 1%/min with uber.18. Performance is dramatically improved as well (no frame lag/skip in emulator, uber.18 @ 600MHz frequently frame lagged).
    Last edited by jnever1; 06/03/2011 at 12:45 PM.
  17.    #477  
    Quote Originally Posted by jnever1 View Post
    ver.66 resolved xvmalloc.ko disagreement across av8b<-->stock<-->uber.18 transitions.

    tested from uber.18 a few hours ago.

    uber.18:uninstall/reboot-->stock-->av8b.66:install/reboot-->(verify compcache enabled/alterable)-->av8b.66:uninstall/reboot-->stock-->uber:install/reboot-->(verify compcache enabled/alterable)-->uber:uninstall/reboot-->stock-->av8b.66:install/reboot

    I'm currently running av8b.66, 0.2 sec poll rate
    CPU: 500/800 (56 50 48)
    SYS: (42 36 34)

    I'm having some thermal issues that are leading to/causing HEAVY battery draw (in the order of 5%/10mins) while on 'stand-by/sleep.' At the extreme, this requires battery pull to free from a locked/frozen state. At the least, 52'C is hot! This is on my best OEM battery, properly/manually calibrated via dr.battery and hex edits to battery chip (1150mAh/100%). I've seen phone temps, while on charger, drop to 30~27'C which confuses the hell out of me compared to 51'C while on unplugged standby.

    I'm trying to narrow down conditions of reproducibility... no luck yet.

    How would I go about logging cpu/sys temp and potentially proximity sensor?

    How would I go about pulling that data from the log in a concise manner? lumberjack?

    I'm not versed in the "for i in $(" code... though I'm sure I could reverse engineer something.
    ------------------------------------------------------
    Aside from the thermal issue, I'm getting about the same battery draw with av8b.66, configured as described above, as with uber.18, configured as described in previous post. This is 800MHz vs 600MHz!

    I see TREMENDOUS improvement while using SuperNES emulator (Tactics Ogre). Battery draw is on the order of roughly 0.5~0.25%/min compared to 1%/min with uber.18. Performance is dramatically improved as well (no frame lag/skip in emulator, uber.18 @ 600MHz frequently frame lagged).
    All logs and values needed were described a couple pages back, and some other examples from the SR71-F104-F105 thread.
    Live free or DIE!
  18. #478  
    Hey!

    Is this me, or is this you:

    Code:
    touch build/.unpacked-2.1.0-66
    rm -rf build/arm
    mkdir -p build/arm/usr/palm/applications/org.webosinternals.kernels.psycho-av8b-kernel-pre/additional_files/boot
    if [ -n "psychobuild/AV8B.config" ] ; then \
      cp build/src-2.1.0-66/patches/psychobuild/AV8B.config build/src-2.1.0-66/linux-2.6.24/.config ; \
      yes '' | \
      make -C build/src-2.1.0-66/linux-2.6.24 ARCH=arm CROSS_COMPILE=/srv/build/toolchain/cs09q1armel/build/arm-2009q1/bin/arm-none-linux-gnueabi- \
            oldconfig ; \
    else \
            yes '' | \
            make -C build/src-2.1.0-66/linux-2.6.24 ARCH=arm CROSS_COMPILE=/srv/build/toolchain/cs09q1armel/build/arm-2009q1/bin/arm-none-linux-gnueabi- \
            omap_sirloin_3430_defconfig ; \
    fi
    make[2]: Entering directory `/srv/build/testing-kernels/psycho-av8b-kernel-pre/build/src-2.1.0-66/linux-2.6.24'
    Makefile:439: *** mixed implicit and normal rules.  Stop.
    make[2]: Leaving directory `/srv/build/testing-kernels/psycho-av8b-kernel-pre/build/src-2.1.0-66/linux-2.6.24'
    make[1]: *** [build/arm.built-2.1.0-66] Error 2
    make[1]: Leaving directory `/srv/build/testing-kernels/psycho-av8b-kernel-pre'
    make: *** [package] Error 2

    Thanks!


    M.
  19.    #479  
    Quote Originally Posted by Xanadu73 View Post
    Hey!

    Is this me, or is this you:

    Code:
    touch build/.unpacked-2.1.0-66
    rm -rf build/arm
    mkdir -p build/arm/usr/palm/applications/org.webosinternals.kernels.psycho-av8b-kernel-pre/additional_files/boot
    if [ -n "psychobuild/AV8B.config" ] ; then \
      cp build/src-2.1.0-66/patches/psychobuild/AV8B.config build/src-2.1.0-66/linux-2.6.24/.config ; \
      yes '' | \
      make -C build/src-2.1.0-66/linux-2.6.24 ARCH=arm CROSS_COMPILE=/srv/build/toolchain/cs09q1armel/build/arm-2009q1/bin/arm-none-linux-gnueabi- \
            oldconfig ; \
    else \
            yes '' | \
            make -C build/src-2.1.0-66/linux-2.6.24 ARCH=arm CROSS_COMPILE=/srv/build/toolchain/cs09q1armel/build/arm-2009q1/bin/arm-none-linux-gnueabi- \
            omap_sirloin_3430_defconfig ; \
    fi
    make[2]: Entering directory `/srv/build/testing-kernels/psycho-av8b-kernel-pre/build/src-2.1.0-66/linux-2.6.24'
    Makefile:439: *** mixed implicit and normal rules.  Stop.
    make[2]: Leaving directory `/srv/build/testing-kernels/psycho-av8b-kernel-pre/build/src-2.1.0-66/linux-2.6.24'
    make[1]: *** [build/arm.built-2.1.0-66] Error 2
    make[1]: Leaving directory `/srv/build/testing-kernels/psycho-av8b-kernel-pre'
    make: *** [package] Error 2
    Thanks!


    M.
    Was probably me. do a "git pull" again to get the new tags.

    Although i didnt make any changes to source, only tag changes to get stuff built for Pre2.
    Live free or DIE!
  20. #480  
    Quote Originally Posted by unixpsycho View Post
    Was probably me. do a "git pull" again to get the new tags.

    Although i didnt make any changes to source, only tag changes to get stuff built for Pre2.

    I did a pull about 10 minutes before ending up posting. I just clobbered and pulled (it waas already up-to-date, though) and it falls over in the same place. It's really no big deal. I just wanted to see if a few config options get exposed/hidden with armv7.

    Thanks man!


    M.

Tags for this Thread

Posting Permissions