[ solved] Geexbox via PXE. Some machines boot, some not… ?

Home Forums Miscellaneous [ solved] Geexbox via PXE. Some machines boot, some not… ?

Tagged: 

This topic contains 96 replies, has 4 voices, and was last updated by  tomlohave 1 year, 6 months ago.

Viewing 15 posts - 31 through 45 (of 97 total)
  • Author
    Posts
  • #11632

    tomlohave
    Keymaster

    hum, I joined the team after 1.0, so, no idea.
    Now, with a flat rootfs, I can boot using nfs but I have still some errors (ro mount right now)
    Once solved , you should be able to modify everything (I hope ! )

    #11633

    antony0509
    Participant

    Thank you very much for the best of all

    #11634

    tomlohave
    Keymaster

    Ok I ‘ve found the problem.
    I have to export my fs with
    /data/geexbox-nfs 192.168.1.0/24(rw,no_root_squash) else root (write) access is not allowed

    I boot geexbox using :

    kernel=vmlinuz root=/dev/nfs nfsroot=192.168.1.2:/data/geexbox-nfs ip=dhcp

    note that if you use a flat roofs, you need to disable connman else the network card is deactivated … (just rename connman.service to connman.service2 in /lib/systemd/system )

    I’m building a new version that you can use

    #11635

    antony0509
    Participant

    Thank you for looking forward to your new version

    #11636

    tomlohave
    Keymaster

    sending the file : 416 MB

    #11637

    tomlohave
    Keymaster

    hum I’ve a problem to send the file : it’s very slow today.

    you can try that instead :

    in your nfs-server : at /tftpboot/GEEXBOX
    you should already have the content of the cd, so the file rootfs should be present
    create a new directory and mount rootfs file inside it

    mkdir /tftpboot/GEEXBOX-rootfs
    mount -o loop /tftpboot/GEEXBOX/rootfs /tftpboot/GEEXBOX-rootfs

    listing the content of /tftpboot/GEEXBOX-rootfs, you should have all files

    copy all files from /tftpboot/GEEXBOX-rootfs to /tftpboot/GEEXBOX

    rename /tftpboot/GEEXBOX/lib/systemd/system/connman.service to /tftpboot/GEEXBOX/lib/systemd/system/connman.service2

    modify /tftpboot/GEEXBOX/boot/pxelinux.cfg/default (last line) to

    APPEND rw root=/dev/nfs nfsroot="ip-of-nfs-server":/tftpboot/GEEXBOX ip=dhcp

    in the nfs server :
    modify /etc/export (first line) to
    /tftpboot/GEEXBOX *(rw,sync,async,no_root_squash)
    exportfs -a

    Try to boot :p

    #11638

    antony0509
    Participant

    I modified the screen after the card will not work this

    pic

    • This reply was modified 1 year, 7 months ago by  antony0509.
    • This reply was modified 1 year, 7 months ago by  antony0509.
    #11641

    tomlohave
    Keymaster

    ??

    #11642

    antony0509
    Participant

    Please click “pic” that the three small characters have a link picture can see

    #11643

    tomlohave
    Keymaster

    and What should I see ?
    does the kernel stop at 2,29 s ?
    you have no more lines ?

    I can re-test from my side, but I used a basic kernel from our distro with the command lines posted previously.

    I don’t think it makes difference but I use vmware now.

    #11644

    antony0509
    Participant

    I have recorded videos
    Trouble you to see where the problem may be

    Video

    #11645

    tomlohave
    Keymaster

    Here is mine using rootfs file from a regular iso unpacked to a directory on my nfs-server

    http://download.geexbox.org/tests/tom/i386/Capture%20vid%c3%a9o%202017-04-26%2021%3a04%3a06.mp4

    Are you sure everything is in place, exported fs ? please show your boot command line (press TAB)

    #11646

    antony0509
    Participant

    :exports
    /tftpboot/GEEXBOX *(rw,sync,async,no_root_squash)

    video

    #11647

    tomlohave
    Keymaster

    hum,
    no info about ip in your video ? like this : http://download.geexbox.org/tests/tom/i386/ip-set.png
    are your sure your dhcp server is ok ?

    what returns on the nfs-server :
    showmount -e localhost

    #11648

    tomlohave
    Keymaster

    Time to sleep, sorry, from my side, everything seems to work, I think something is not well configured on your server or in virtualbox

    As you use virtualbox, double check using an iso that you have a working network interface once booted. And look if the problem does not come with the virtual ethernet interface configured on virtualbox (should be configured on the same lan than the host: shared). And you can change the device too to test.

Viewing 15 posts - 31 through 45 (of 97 total)

You must be logged in to reply to this topic.