Wednesday, June 5, 2013

fedora 19 installer for nexus4

As promised in my previous post, now there is an f19 installer for nexus4:

https://github.com/freedreno/nexus4-fedora

So if you have an n4 and a bit of free space, you can play around with accelerated open-source gpu goodness :-)

15 comments:

  1. Hi! How you get rw /system and /data? i have root but all what i see is
    ** Creating chroot filesystem
    mkdir failed for -p, Read-only file system
    and then other commands of course says something like
    cannot stat 'system/xbin/busybox': No such file or directory
    Unable to chmod /data/fedora/busybox: No such file or directory

    ReplyDelete
    Replies
    1. hmm, maybe it was r/w for me because I had already rooted the n4?

      Delete
    2. btw, try running 'adb root' first, that might be all you need

      Delete
  2. i used twrp recovery, after i flash cwm i get all permissions, and it loaded, with many errors but i start, how we can get gui? and maybe you can, in next build, try to create .zip for recovery and easy start? ;) .zip will be great!

    ReplyDelete
    Replies
    1. on first start, make sure you have enabled USB tethering, so that it has network access and can install gnome-shell, gdm, etc

      Delete
  3. If i try to connect over ssh after i wrote pass it says permissions denied... why so hard...

    ReplyDelete
  4. hmm, I don't remember any particular ssh issue (I use ssh all the time). Note that I'm enabling USB tethering.. thought I should mention that in case it changes the behavior.

    ReplyDelete
    Replies
    1. of course i enable tethering, how would I get ssh connect :) maybe you can create zip for recovery with fedora with gui? or packed installed fedora, if i can unpack and boot it? or maybe you can add gui pack in root fs and add autorun script who installed gui? sorry for my english and boring, i realy don't know how it do :(

      Delete
    2. full zip of filesystem with gui would be quite a bit large. Are you using my kernel (mako-boot.img)?

      On the first time you enter the chroot, was it able to install the GUI? maybe you could pastebin the the output from when you run /data/fedora/start-chroot.sh?

      Delete
  5. Please share some screenshots.

    ReplyDelete
  6. hello,rob

    My name is Jessica ,i am a developer who comes from China.
    I have read your posts in google forum.Now i am facing the same problem that you have descriped in your posts.I have try my best to solve this problem,but it doesn't work on.
    According to the website you have metioned in the forum https://github.com/robclark/ libdri2
    The Compilation results is :
    [ 9.350] (II) LoadModule: "dri2"
    [ 9.351] (II) Loading /usr/shdb/xorg/modules/extensions/shdbdri2.so
    [ 9.353] (EE) LoadModule: Module dri2 does not have a dri2ModuleData data object.
    [ 9.353] (II) UnloadModule: "dri2"
    [ 9.353] (II) Unloading dri2
    [ 9.353] (EE) OMAP: Failed to load module "dri2" (invalid module, 0)
    [ 9.353] (II) UnloadModule: "omap

    Could you tell me why does the compilation can’t pass?
    I am so confused and worry,because if can’t solve this problem,I can’t complete my emission. I will be grateful to you If you can share me something about this problem.
    my email:1416966044@qq.com
    Looking forward to your reply.

    ReplyDelete
    Replies
    1. what exactly are you trying to build/run?

      The libdri2 git tree is for client side, and you should not need it for anything freedreno related or for xserver. The module that xorg is trying to is something different, which should be coming from your xorg/xserver build.

      Delete
  7. the 0x0@24 pixmap msg is normal at startup (the root pixmap is initially created as width/height of 0x0. It gets fixed up later in startup..

    and there are still a few corruption bugs w/ XA ddx.

    ReplyDelete
  8. Hi,

    Thanks for your great work ! Any chance to have an updated fedora 19 installer for touchpad ? It would make me very happy :) And make my touchpad a lot more usefull !

    ReplyDelete
    Replies
    1. I had started trying to update the installer for f19 in the background (while I was working on something else), but somehow it was hanging half way through untar'ing the rootfs. In f18 I did have to rebuild systemd because of some issues. At least one of my two systemd patches was merged upstream and should already be in f19. The other was supposedly unnecessary. (I'm not a systemd expert, so I'll trust the systemd maintainers on that one.)

      In theory, the pre-build mesa/ddx/libdrm from nexus4/f19 filesys should "just work" on touchpad. All the a220 support is still there (and I even test periodically on touchpad when I make changes in the common code :-P).

      Delete