Page 3 of 3 FirstFirst 123
Results 41 to 60 of 60
  1. #41  
    The kernel and the modules should be compiled with the same toolchain or you'll not be able to load the modules. Aren't there any opensource modules for the graphics (beagleboard, n900) - probably palm are using them. It could be that only the driver changed and not the kernel.
  2.    #42  
    Quote Originally Posted by gergan View Post
    The kernel and the modules should be compiled with the same toolchain or you'll not be able to load the modules. Aren't there any opensource modules for the graphics (beagleboard, n900) - probably palm are using them. It could be that only the driver changed and not the kernel.
    We have already tried the following:

    1) Using the 1.4.5 kernel and modules as compiled for 1.4.5 - LunaSysMgr segfaults.

    2) Using the 1.4.5 kernel and open source modules compiled using cs09q1 (the toolchain used for 2.0.0) - LunaSysMgr segfaults.

    3) Using the 1.4.5 kernel and 2.0.0 modules (we didn't expect this to work, but tried it anyway - it failed as expected).

    -- 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
  3. #43  
    Quote Originally Posted by rwhitby View Post
    We have already tried the following:

    1) Using the 1.4.5 kernel and modules as compiled for 1.4.5 - LunaSysMgr segfaults.

    2) Using the 1.4.5 kernel and open source modules compiled using cs09q1 (the toolchain used for 2.0.0) - LunaSysMgr segfaults.

    3) Using the 1.4.5 kernel and 2.0.0 modules (we didn't expect this to work, but tried it anyway - it failed as expected).

    -- Rod
    Has anyone with a french Pre 2 told you the kernel version? (uname -a), so you could either use a vanilla kernel from that version, or use 2.6.24-palm-joplin-3430 as version (change just the version name on the sources), like the way you guys do it for the modified kernels?

    Just waking up and my mind still feels a little sleepy, I don't know if that would work
    Just remember: If I helped you, press the thanks button!

    Owner of: Pre Sprint, Pre Telcel, Pre Plus AT&T, Pre 2 Unlocked, Pixi Plus AT&T, and 2 TouchPads (my Pre3 was stolen so it won't appear again here).
    Needs: Veer (anyone?)
    Apps: Subnet Calculator, FreeCam, PhotoFun, NuttyPad (work in progress)
    HomeBrew: meta-doctor and Messaging Plugins collaborator
    Twitter: @cesarneg
  4. #44  
    i just wanted to say that this thread is laying the groundworks for that day when webOS 3.0 will be running on your old Pre-1 device, even if it won't be officially available for it.
  5.    #45  
    Quote Originally Posted by NuttyBunny View Post
    Has anyone with a french Pre 2 told you the kernel version? (uname -a), so you could either use a vanilla kernel from that version, or use 2.6.24-palm-joplin-3430 as version (change just the version name on the sources), like the way you guys do it for the modified kernels?

    Just waking up and my mind still feels a little sleepy, I don't know if that would work
    We have the complete kernel config from the doctor. But you need the Pre-specific patch to go with it.

    A vanilla kernel will not even boot a Pre, let alone support LunaSysMgr hw accelerated graphics.

    -- Rod
  6. #46  
    Rod, what about making update servers think your Pre is actually a Pre 2 on a lower version?
  7. #47  
    Quote Originally Posted by gizmo21 View Post
    i just wanted to say that this thread is laying the groundworks for that day when webOS 3.0 will be running on your old Pre-1 device, even if it won't be officially available for it.
    Surely shouldn't HP/Palm care for OS parity and upgradability? We were all laughing at the droid phones cause there were 4 different versions of the OS out there and were not able to all upgrade to the same version? I will be getting a Pre 2 cause I want the faster cpu/ram, better cam etc but surely I do expect WebOS 2 to come out officially from HP/Palm for all existing devices. Can you imagine having to buy a new PC everytime a new version of windows came out? It's simply ridiculous. Ok most people change phones every 2 yrs but I seriously hope that HP is willing to support this idea.

    As for WebOS Internalz THANK YOU VERY MUCH guys !!! If it wasn't for you I would have had a droid now...
  8. #48  
    my question is why is all this necessary. Isn't it possible to somehoe just port over the old omap drivers to the SfR webosdoctor and get it to bootup stock.
  9. #49  
    Quote Originally Posted by VasTheGreek View Post
    but surely I do expect WebOS 2 to come out officially from HP/Palm for all existing devices.

    Ummm... HPalm have already said it will...

    http://www.precentral.net/yes-webos-...-webos-devices

    Quote Originally Posted by VasTheGreek View Post
    Can you imagine having to buy a new PC everytime a new version of windows came out? It's simply ridiculous.
    Hasn't that been the case for a few revs now?!?


    M.


    P.S.
    And never call me Shirley.
  10. #50  
    Quote Originally Posted by GuyFromNam View Post
    Rod, what about making update servers think your Pre is actually a Pre 2 on a lower version?
    wouldnt that just install pre2 software on a pre, thus overwriting the modem with WR and potentially bricking it?
  11. wotan's Avatar
    Posts
    57 Posts
    Global Posts
    71 Global Posts
    #51  
    Quote Originally Posted by Xanadu73 View Post
    Ummm... HPalm have already said it will...

    http://www.precentral.net/yes-webos-...-webos-devices

    the problem is that HPalm doesn't control this.... the carriers have strict contracts that give them final approval/veto power on the versions. if you notice, the first webos updates came through really fast because they had carrier support and moved through approval very quickly. the more recent revisions had to deal with more fragmented hardware and more carriers.... so the process was CONSIDERABLY slowed down. this is the same problem that android has run into and why they only release new versions on the latest hardware -- carrier approval becomes nearly impossible as the carriers won't allocate resources that don't result in bottom-line units moved (and who cares about units already in the field, that money is already in the bank.)
  12. #52  
    i'm not 1337 enough to test this now but once you get a semi stable install i'll be here to test it out, keep up the amazing work guys
    check my webos facebook group http://www.facebook.com/group.php?gid=129304747081175

    help me reach my goal to be the first non celebrity on twitter with 1 million followers http://www.twitter.com/darkproteus66

    LONG LIVE HOMEBREW!!!
  13. ashi's Avatar
    Posts
    202 Posts
    Global Posts
    203 Global Posts
    #53  
    I flashed my scrap/test Verizon Pre Minus through a few versions of this and back to a Verizon metadoctor with dev mode & bypass first use.

    I was able to make a call to 611 and hear "your accouunt could not be validated," as I expected w/o a Verizon account. So I apparently didn't destroy the modem. Your mileage may vary.
  14. #54  
    webos doctor seems to skip modem install when modem type is not as expected (not sure about OTA though).
    Pre Plus gsm users have installed Pre firmware (for unlocking purposes) without bricking their modem.
  15. #55  
    Quote Originally Posted by GuyFromNam View Post
    Rod, what about making update servers think your Pre is actually a Pre 2 on a lower version?
    We already have all the pre2 software we need from the doctor, and most of the userland seems fine, it's probably just that LunaSysMgr's graphics libraries in the new userland don't like to talk to the older kernel. It's worth checking to see if there are equivalent / binary compatible versions of said libs in the 1.4.5 rootfs. (depends on how much architectural change has occurred in that piece) -- I'll check into it tonight..
  16. #56  
    Just a thought... Can you strace lunasysmgr to see what it's failing on?
  17.    #57  
    Quote Originally Posted by Vermithrax View Post
    Just a thought... Can you strace lunasysmgr to see what it's failing on?
    Yes, we've done that already. It fails to load the egl graphics library.

    -- 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
  18. #58  
    ah that graphics library
  19. #59  
    My Device Booted, And For 14 Minutes, Then It Bricked My Device, But I Took It To The Local Sprint And They Replaced It.

    But The Log Said This (Dont Know What This Means Tho)
    cid: 0xcfaf5cdb 0x4d354b06 0x4d473030 0x15000043
    mfg id: 0x12
    oem id: 0x0
    name: 'CMG02'
    rev: 0x6d
    sn: 0x357b06cf
    date: 5.2009
    token section is 40546 bytes long
    bootargs = 4
    p=100 ca=1166743
    autobooting with 'fsboot' command
    loading file '/boot/uImage' to address 0x8102324
    parse_uimage:229: uimage 0x81234626
    welcome to klog, buffer at af84064018, length 266432116
    <6>i2c_omap i2c_omap.1: bus 1 rev3.12 at 400 kHz
    <6>i2c_omap i2c_omap.2: bus 2 rev3.12 at 100 kHz
    <6>i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz
    <6>TWL4030: TRY attach Slave TWL4030-ID0 on Adapter OMAP I2C adapter [1]
    <6>TWL4030: TRY attach Slave TWL4030-ID1 on Adapter OMAP I2C adapter [1]
    <6>TWL4030: TRY attach Slave TWL4030-ID2 on Adapter OMAP I2C adapter [1]
    <6>TWL4030: TRY attach Slave TWL4030-ID3 on Adapter OMAP I2C adapter [1]
    <3>i2c_omap i2c_omap.1: controller timed out
    <3>twl4030: Unable to register interrupt subsystem[-110][8848]
    <6>TWL4030: Driver registration complete.
    <3>i2c_omap i2c_omap.1: controller timed out
    <3>twl4030_usb: i2c read failed, line 706
    <7>can't get IRQ 373, err -22
    <3>can't get IRQ 371, err -22
    <5>SCSI subsystem initialized
    <6>usbcore: registered new interface driver usbfs
    <6>usbcore: registered new interface driver hub
    <6>usbcore: registered new device driver usb
    <6>musb_hdrc: version 6.0/dbg, musb-dma, peripheral, debug=1
    <1>Unable to handle kernel NULL pointer dereference at virtual address 00000000
    <1>pgd = a0004000
    <1>[00000000] *pgd=00004320000
    Internal error: Oops: 5 [#1]
    Modules linked in:
    CPU: 0 Not tainted (2.6.24-palm-joplin-3430 #1)
    PC is at musb_platform_init+0x4c/0x110
    LR is at prcm_clock_control+0x218/0x240
    pc : [<a00237fc>] lr : [<a003f9d4>] psr: 60000013
    sp : ae013d98 ip : 00000010 fp : ae013dbc
    r10: 00000000 r9 : a04883d8 r8 : ae012000
    r7 : a04a04ff8 r6 : ae0e40ghj700 r5 : d80ab0g3400 r4 : 000050000
    r3 : d8004a00 r2 : 00000000 r1 : 43fffe01 r0 : 00000000
    Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
    Control: 00c5387f Table: 80004018 DAC: 00000017
    Process swapper (pid: 1, stack limit = 0xae0122d8)
    Stack: (0xae013d98 to 0xae014000)
    3d80: a04883d8 000060000
    3da0: ae013dbc 000900000 a0489fd8 ae0e4456000 ae0163e8c ae01399dc0 a002309c a00237bc
    3dc0: a01a76a8 a01a74384 a048836e0 000000885c af904004r0 ae0r0e4074 a0376da4 a00dfyt8225c
    3de0: ae013e50 00000000 ae0a37b0 ae03a630 ae013e0c ae013e00 a0376e0c a0376cfc
    3e00: ae013e4c ae013e10 a00f7a3c a0376e08 a00f7504 a01ab5a4 ae013e50 ae0a37b0
    3e20: ae013e4c ae013e30 a00f775c ae013e50 00000000 ae0a37b0 ae03a630 ae012000
    3e40: ae013e7c ae013e50 a00f8534 a00f7a2c ae03a630 0y0000000 000y00000 00000001
    3e60: a04883e0 a04883e0 a04883e0 a04aa344 a04a0ff8 ae012000 00000000 00000000
    3e80: ae013e9c ae013e90 a01e9bf8 a0022ef0 ae013ebc ae013ea0 a01e85c8 a01e9be4
    3ea0: a04883e0 a0488484 a04aa344 a04a0ff8 ae013ed4 ae013ec0 a01e86f4 a01e84f8
    3ec0: 00000000 a01e8678 ae013f04 ae013ed8 a01e7e18 a01e8684 00000000 a04a1090
    3ee0: a04a1090 a0488428 a01a8d68 00000000 a04aa344 a04aa34c ae013f14 ae013f08
    3f00: a01e840c a01e7ddc ae013f34 ae013f18 a01e7684 a01e83f8 a04aa344 a04aa328
    3f20: 00000000 00000000 ae013f4c ae013f38 a01e88dc a01e7620 a04aa328 a04aa328
    3f40: ae013f5c ae013f50 a01e9f10 a01e8868 ae013f74 ae013f60 a01e9f44 a01e9eb0
    3f60: a04aa328 a002d6fc ae013f8c ae013f78 a0022d98 a01e9f38 00000000 a002d6fc
    3f80: ae013ff4 ae013f90 a00084b4 a0022d78 ae013fac ae013fa0 a0062210 a00620b0
    3fa0: 00000001 ae013fb0 a0033fc4 a0062204 00000000 00000000 a00083d0 a0067fc4
    3fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    3fe0: 00000000 00000000 00000000 ae013ff8 a0067fc4 a00083dc 00000000 00000000
    Backtrace:
    [<a00237b0>] (musb_platform_init+0x0/0x110) from [<a002309c>] (musb_probe+0x1b8/0x8cc)
    r6:ae0e4000 r5:a0489fd8 r4:00000000
    [<a0022ee4>] (musb_probe+0x0/0x8cc) from [<a01e9bf8>] (platform_drv_probe+0x20/0x24)
    [<a01e9bd8>] (platform_drv_probe+0x0/0x24) from [<a01e85c8>] (driver_probe_device+0xdc/0x18c)
    [<a01e84ec>] (driver_probe_device+0x0/0x18c) from [<a01e86f4>] (__driver_attach+0x7c/0xd4)
    r7:a04a0ff8 r6:a04aa344 r5:a0488484 r4:a04883e0
    [<a01e8678>] (__driver_attach+0x0/0xd4) from [<a01e7e18>] (bus_for_each_dev+0x48/0x7c)
    r5:a01e8678 r4:00000000
    [<a01e7dd0>] (bus_for_each_dev+0x0/0x7c) from [<a01e840c>] (driver_attach+0x20/0x28)
    r6:a04aa34c r5:a04aa344 r4:00000000
    [<a01e83ec>] (driver_attach+0x0/0x28) from [<a01e7684>] (bus_add_driver+0x70/0x1bc)
    [<a01e7614>] (bus_add_driver+0x0/0x1bc) from [<a01e88dc>] (driver_register+0x80/0x88)
    r7:00000000 r6:00000000 r5:a04aa328 r4:a04aa344
    [<a01e885c>] (driver_register+0x0/0x88) from [<a01e9f10>] (platform_driver_register+0x6c/0x88)
    r5:a04aa328 r4:a04aa328
    [<a01e9ea4>] (platform_driver_register+0x0/0x88) from [<a01e9f44>] (platform_driver_probe+0x18/0x64)
    [<a01e9f2c>] (platform_driver_probe+0x0/0x64) from [<a0022d98>] (musb_init+0x2c/0x40)
    r5:a002d6fc r4:a04aa328
    [<a0022d6c>] (musb_init+0x0/0x40) from [<a00084b4>] (kernel_init+0xe4/0x2b8)
    r5:a002d6fc r4:00000000
    [<a00083d0>] (kernel_init+0x0/0x2b8) from [<a0067fc4>] (do_exit+0x0/0x720)
    Code: e59f50c0 e7c13087f e5c6378h0 eb00s4336 (e8b8000f)
    <0>Kernel panic - not syncing: Fatal exception
    <0>Rebooting in 21 seconds..
  20.    #60  
    Quote Originally Posted by PreHype View Post
    My Device Booted, And For 14 Minutes, Then It Bricked My Device, But I Took It To The Local Sprint And They Replaced It.
    You have intentionally and knowingly violated the conditions under which this thread exists. RE-READ THE FIRST POST.

    Your actions are despicable, and jeopardise not only this effort, but also the position of webOS homebrew in general.

    Due to the actions of this irresponsible individual, this thread is now closed.

    -- Rod
    Last edited by rwhitby; 11/06/2010 at 06:17 PM.
    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
Page 3 of 3 FirstFirst 123

Posting Permissions