Forum: PS3 Linux Discussion - The PS3 Linux Discussion forum contains all the information you are looking for on using Linux on the PS3.


The above video goes away if you are a member and logged in, so log in now!




 
Would you like to get all the new info from
PSX-Scene in your email each day?




Want to learn more about the team keeping you up to date with the latest scene news?

Read about them now!

Check out our Developer bios, too!

 


User Tag List

Thread: Netbooting bootos latest?
  

Results 1 to 10 of 10
  1. #1 Netbooting bootos latest? 
    xPreatorianx is offline Sleeping for real this time!
    Join Date
    Aug 2010
    Posts
    1,790
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    349
    Likes Received
    338
    Hey guys I was wondering if it's possible to netboot debian or ubuntu with the latest bootos? Or netboot Graf's version of linux? I want to do this because I only have 2 USB ports on my PS3 so I can't have both the mouse and keyboard hooked up, plus I can't edit the files properly because my win 7 machine does not allow ext3 file system. So I was wondering if it's possible either through windows or by using linux through a VM or something?

    Can anyone tell me how to do it?
    Reply With Quote  

  2. #2  
    andyt12 is offline Member
    Join Date
    Sep 2010
    Posts
    152
    Downloads
    4
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    2
    I don't know how possible it would be to do through windows directly.

    You need
    NFS Server, can run on windows but the problem comes with not supporting linking and permissions the way nix file systems do, so count windows out.

    DHCP Server, The one built into your router is likely not going to cut it so it needs to be disabled.

    So having a nix server is really the only way to go. You could probably pull it off in a virtual environment.

    Once you have a Linux virtual server setup, install NFS server, tftp server and DHCP server. I prefer isc dhcp server and tftp-hpa for tftp.

    Set an area for your boot images, mine is /mnt/nfs/diskless
    My rootfs goes into PS3, so /mnt/nfs/diskless/PS3/

    tftp server config is " -u nobody -l -vvv -p -c -s /mnt/nfs/diskless "

    nfs /etc/exports file will need a line like so
    /mnt/nfs/diskless/PS3 192.168.0.0/255.255.255.0(rw,sync,no_root_squash,no_subtree_ch eck)

    DHCP server will a section like below, aswell as your dynamic configuration.

    host PS3 {
    hardware ethernet 00:24:8d:cc:aa:49; # MAC address of PS3
    fixed-address 192.168.0.13; # PS3 IP address, you decide.
    next-server 192.168.0.15; # IP of the tftp server
    filename "/PS3/boot/kboot.conf"; # Only one of these 2 lines
    option configfile "/PS3/boot/kboot.conf"; # needed, both wont hurt.
    }

    Your kboot.conf will go into /mnt/nfs/diskless/Ps3/boot/kboot.conf
    contents will be
    linux='/PS3/boot/vmlinux video=ps3fb:mode:3 root=/dev/nfs rw nfsroot=192.168.0.15:/mnt/nfs/diskless/PS3_32 ip=dhcp'

    vmlinux which is linux kernel will also go into /mnt/nfs/diskless/PS3/boot and will need to be configured for nfs root and ip auto configuration.

    This is the basics, your DHCP server will need to be configured so the rest of your network still works and I just dont see it working well in a virtual environment.

    Bear in mind that im using asbestos loader 1.5 and not the newer bootos 2.x. And this is all described for a gentoo machine.

    You really need a dedicated linux server. I have had one for years for net booting several HTPC machines, running card servers, asterisk, dvb, nas ect... so it was a simple matter to add the PS3's into it.

    You will find it much easier to buy a USB hub for your kb/mouse and hard disk and use a virtual PC for editing the ext3 filesystem.
    Reply With Quote  

  3. #3  
    xPreatorianx is offline Sleeping for real this time!
    Join Date
    Aug 2010
    Posts
    1,790
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    349
    Likes Received
    338
    Thank you so much! I have a windows 2008 R2 server setup, but yea I can setup a virtual server for it as well.

    But again thanks for your help dude I greatly appreciate it. Very thorough explanation of everything I need to do.
    Reply With Quote  

  4. #4  
    xPreatorianx is offline Sleeping for real this time!
    Join Date
    Aug 2010
    Posts
    1,790
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    349
    Likes Received
    338
    Well I may end up just setting up linux on my server machine. Then I'll do this. I've been meaning to move to linux on it anyways so this is the best time to try and get the hang of this.

    If I need anymore help do you mind if I PM you?
    Reply With Quote  

  5. #5  
    andyt12 is offline Member
    Join Date
    Sep 2010
    Posts
    152
    Downloads
    4
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    2
    No problem. Your making the right choice.
    Reply With Quote  

  6. #6  
    xPreatorianx is offline Sleeping for real this time!
    Join Date
    Aug 2010
    Posts
    1,790
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    349
    Likes Received
    338
    I am confused as hell, about netbooting. I can't figure out what I'm missing or if I even have it setup correctly. Can anyone help me on this? I still don't have it setup correctly. Plus I don't know what to do on the PS3 side and what files I need in the folders.

    Can anyone give me a detailed guide on how to netboot with the PS3?
    Reply With Quote  

  7. #7  
    xPreatorianx is offline Sleeping for real this time!
    Join Date
    Aug 2010
    Posts
    1,790
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    349
    Likes Received
    338
    I guess no one is gonna help me. I have basically got it to boot half way. It goes to the penguins but then times out because it can't find the port for the NFS mnt. I'll try and take a picture of the screen to show all the errors. But it seems like that is gonna be a waste of time because no one wants to help. But I'll do it anyways.
    Reply With Quote  

  8. #8  
    xPreatorianx is offline Sleeping for real this time!
    Join Date
    Aug 2010
    Posts
    1,790
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    349
    Likes Received
    338
    Bump again this is what I got during boot. This post is from the ubuntu forum and includes everything I've done so far. I'm still having trouble. If anyone can help me I would appreciate it!

    I'm running Ubuntu 10.10 latest IIRC and I'm trying to setup a network boot using NFS and TFTP for my PS3 so I can boot gentoo. I can't seem to find where the problem is. I believe I have all the ports forwarded correctly but I'm not sure. I have all the files correctly edited from the guide I followed and it does boot into the vmlinux image I guess. But it can't mount the NFS directory.

    I'm a noob when it comes to linux so I'm still learning. But I do learn quickly. Hopefully these are the correct logs you guys need because I had to take a video with my camera to get the logs from my PS3. I know I have my PS3 configured correctly besides maybe a port or two in relation to NFS or TFTP so I don't need any help with that, at least I hope. I just need help server side.

    Here are the logs from my PS3, ubuntu machine, and all my edited files.

    Here's where I have my files stored for tftp, nfs, and my mnt.

    Code:
    /mnt/experimental
    vmlinux
    Code:
    /var/lib/tftpboot
    IP's I'm using :
    Ubuntu machine with nfs server : 192.168.1.2
    /mnt/experimental is on : 192.168.1.2
    PS3 is on : 192.168.1.3

    I also have latent IP's like 192.168.1.4 because I was troubleshooting. Please let me know where I am going wrong. Thank you for your help in advance.



    [37.474692] rpcbind: server 192.168.1.3 not responding. timed out
    [37.476342] Root-NFS: Unable to get nfsd port number from server, using default.
    [37.479697] Looking up port of RPC 100005/1 on 192.168.1.3
    [72.646690] rpcbind : Server 192.168.1.3 not responding, timed out
    [72.548512] Root-NFS: Unable to get mountd port number from server, using default.
    [107.610727] Root-NFS : Server returned error -110 while mounting /mnt/experimental
    [107.622308] VFS : Unable to mount root fs via NFS, trying floppy.
    [107.624762] VFS : Cannot open root device "nfs" or unknown-block (2,0)
    [107.626594] Please append a correct "root=" boot option; here are the available partitions : (there aren't any it just does a stack trace and freezes.

    dhcpd.conf

    Code:
    # Sample configuration file for ISC dhcpd for Debian
    #
    # Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as
    # configuration file instead of this file.
    #
    # $Id: dhcpd.conf,v 1.1.1.1 2002/05/21 00:07:44 peloy Exp $
    #
    
    # The ddns-updates-style parameter controls whether or not the server will
    # attempt to do a DNS update when a lease is confirmed. We default to the
    # behavior of the version 2 packages ('none', since DHCP v2 didn't
    # have support for DDNS.)
    ddns-update-style none;
    
    # option definitions common to all supported networks...
    option domain-name "example.org";
    option domain-name-servers ns1.example.org, ns2.example.org;
    
    #default-lease-time 600;
    #max-lease-time 7200;
    
    # If this DHCP server is the official DHCP server for the local
    # network, the authoritative directive should be uncommented.
    #authoritative;
    
    # Use this to send dhcp log messages to a different log file (you also
    # have to hack syslog.conf to complete the redirection).
    #log-facility local7;
    
    # No service will be given on this subnet, but declaring it helps the
    # DHCP server to understand the network topology.
    
    #subnet 10.152.187.0 netmask 255.255.255.0 {
    #}
    
    # This is a very basic subnet declaration.
    
    #subnet 10.254.239.0 netmask 255.255.255.224 {
    #  range 10.254.239.10 10.254.239.20;
    #  option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
    #}
    
    # This declaration allows BOOTP clients to get dynamic addresses,
    # which we don't really recommend.
    
    #subnet 10.254.239.32 netmask 255.255.255.224 {
    #  range dynamic-bootp 10.254.239.40 10.254.239.60;
    #  option broadcast-address 10.254.239.31;
    #  option routers rtr-239-32-1.example.org;
    #}
    
    # A slightly different configuration for an internal subnet.
    #subnet 10.5.5.0 netmask 255.255.255.224 {
    #  range 10.5.5.26 10.5.5.30;
    #  option domain-name-servers ns1.internal.example.org;
    #  option domain-name "internal.example.org";
    #  option routers 10.5.5.1;
    #  option broadcast-address 10.5.5.31;
    #  default-lease-time 600;
    #  max-lease-time 7200;
    #}
    
    # Hosts which require special configuration options can be listed in
    # host statements.   If no address is specified, the address will be
    # allocated dynamically (if possible), but the host-specific information
    # will still come from the host declaration.
    
    #host passacaglia {
    #  hardware ethernet 0:0:c0:5d:bd:95;
    #  filename "vmunix.passacaglia";
    #  server-name "toccata.fugue.com";
    #}
    
    # Fixed IP addresses can also be specified for hosts.   These addresses
    # should not also be listed as being available for dynamic assignment.
    # Hosts for which fixed IP addresses have been specified can boot using
    # BOOTP or DHCP.   Hosts for which no fixed address is specified can only
    # be booted with DHCP, unless there is an address range on the subnet
    # to which a BOOTP client is connected which has the dynamic-bootp flag
    # set.
    #host fantasia {
    #  hardware ethernet 08:00:07:26:c0:a5;
    #  fixed-address fantasia.fugue.com;
    #}
    
    # You can declare a class of clients and then do address allocation
    # based on that.   The example below shows a case where all clients
    # in a certain class get addresses on the 10.17.224/24 subnet, and all
    # other clients get addresses on the 10.0.29/24 subnet.
    
    #class "foo" {
    #  match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
    #}
    
    #shared-network 224-29 {
    #  subnet 10.17.224.0 netmask 255.255.255.0 {
    #    option routers rtr-224.example.org;
    #  }
    #  subnet 10.0.29.0 netmask 255.255.255.0 {
    #    option routers rtr-29.example.org;
    #  }
    #  pool {
    #    allow members of "foo";
    #    range 10.17.224.10 10.17.224.250;
    #  }
    #  pool {
    #    deny members of "foo";
    #    range 10.0.29.10 10.0.29.230;
    #  }
    #
    #
    #
    #
    
    
    default-lease-time 600;
    max-lease-time 7200;
    ddns-update-style none;
    authoritative;
    log-facility local7;
    subnet 192.168.1.0 netmask 255.255.255.0{
    range 192.168.1.1 192.168.1.254;
    }
    next-server 192.168.1.2;
    filename "kboot.conf";
    option routers 192.168.1.1;
    
    host PS3{
    hardware ethernet 00:1f:a7:81:1d:72; # MAC address of PS3
    fixed-address 192.168.1.3; # PS3 IP address, you decide.
    }
    exports
    Code:
    # /etc/exports: the access control list for filesystems which may be exported
    #        to NFS clients.  See exports(5).
    #
    # Example for NFSv2 and NFSv3:
    # /srv/homes       hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
    #
    # Example for NFSv4:
    # /srv/nfs4        gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
    # /srv/nfs4/homes  gss/krb5i(rw,sync,no_subtree_check)
    #
    /mnt/experimental 192.168.1.2(rw,async,no_root_squash,no_subtree_check,anonuid=0,anongid=0)
    #/mnt/experimental 192.168.1.4/16(rw,async,no_root_squash,no_subtree_check,anonuid=0,anongid=0)
    kboot.conf
    Code:
    linux='vmlinux video=ps3fb:mode:2 root=/dev/nfs rw ip=dhcp nfsroot=192.168.1.3:/mnt/experimental panic=5'
    rpcinfo
    Code:
    prea@prea-dev:~$ rpcinfo -p
       program vers proto   port
        100000    2   tcp    111  portmapper
        100000    2   udp    111  portmapper
        100024    1   udp  59496  status
        100024    1   tcp  58250  status
        100021    1   udp  37426  nlockmgr
        100021    3   udp  37426  nlockmgr
        100021    4   udp  37426  nlockmgr
        100021    1   tcp  33013  nlockmgr
        100021    3   tcp  33013  nlockmgr
        100021    4   tcp  33013  nlockmgr
        100003    2   tcp   2049  nfs
        100003    3   tcp   2049  nfs
        100003    4   tcp   2049  nfs
        100227    2   tcp   2049
        100227    3   tcp   2049
        100003    2   udp   2049  nfs
        100003    3   udp   2049  nfs
        100003    4   udp   2049  nfs
        100227    2   udp   2049
        100227    3   udp   2049
        100005    1   udp  47827  mountd
        100005    1   tcp  50681  mountd
        100005    2   udp  47827  mountd
        100005    2   tcp  50681  mountd
        100005    3   udp  47827  mountd
        100005    3   tcp  50681  mountd
    Reply With Quote  

  9. #9  
    xPreatorianx is offline Sleeping for real this time!
    Join Date
    Aug 2010
    Posts
    1,790
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    349
    Likes Received
    338
    Bump again this is what I got during boot. This post is from the ubuntu forum and includes everything I've done so far. I'm still having trouble. If anyone can help me I would appreciate it!

    I'm running Ubuntu 10.10 latest IIRC and I'm trying to setup a network boot using NFS and TFTP for my PS3 so I can boot gentoo. I can't seem to find where the problem is. I believe I have all the ports forwarded correctly but I'm not sure. I have all the files correctly edited from the guide I followed and it does boot into the vmlinux image I guess. But it can't mount the NFS directory.

    I'm a noob when it comes to linux so I'm still learning. But I do learn quickly. Hopefully these are the correct logs you guys need because I had to take a video with my camera to get the logs from my PS3. I know I have my PS3 configured correctly besides maybe a port or two in relation to NFS or TFTP so I don't need any help with that, at least I hope. I just need help server side.

    Here are the logs from my PS3, ubuntu machine, and all my edited files.

    Here's where I have my files stored for tftp, nfs, and my mnt.

    Code:
    /mnt/experimental
    vmlinux
    Code:
    /var/lib/tftpboot
    IP's I'm using :
    Ubuntu machine with nfs server : 192.168.1.2
    /mnt/experimental is on : 192.168.1.2
    PS3 is on : 192.168.1.3

    I also have latent IP's like 192.168.1.4 because I was troubleshooting. Please let me know where I am going wrong. Thank you for your help in advance.



    [37.474692] rpcbind: server 192.168.1.3 not responding. timed out
    [37.476342] Root-NFS: Unable to get nfsd port number from server, using default.
    [37.479697] Looking up port of RPC 100005/1 on 192.168.1.3
    [72.646690] rpcbind : Server 192.168.1.3 not responding, timed out
    [72.548512] Root-NFS: Unable to get mountd port number from server, using default.
    [107.610727] Root-NFS : Server returned error -110 while mounting /mnt/experimental
    [107.622308] VFS : Unable to mount root fs via NFS, trying floppy.
    [107.624762] VFS : Cannot open root device "nfs" or unknown-block (2,0)
    [107.626594] Please append a correct "root=" boot option; here are the available partitions : (there aren't any it just does a stack trace and freezes.

    dhcpd.conf

    Code:
    # Sample configuration file for ISC dhcpd for Debian
    #
    # Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as
    # configuration file instead of this file.
    #
    # $Id: dhcpd.conf,v 1.1.1.1 2002/05/21 00:07:44 peloy Exp $
    #
    
    # The ddns-updates-style parameter controls whether or not the server will
    # attempt to do a DNS update when a lease is confirmed. We default to the
    # behavior of the version 2 packages ('none', since DHCP v2 didn't
    # have support for DDNS.)
    ddns-update-style none;
    
    # option definitions common to all supported networks...
    option domain-name "example.org";
    option domain-name-servers ns1.example.org, ns2.example.org;
    
    #default-lease-time 600;
    #max-lease-time 7200;
    
    # If this DHCP server is the official DHCP server for the local
    # network, the authoritative directive should be uncommented.
    #authoritative;
    
    # Use this to send dhcp log messages to a different log file (you also
    # have to hack syslog.conf to complete the redirection).
    #log-facility local7;
    
    # No service will be given on this subnet, but declaring it helps the
    # DHCP server to understand the network topology.
    
    #subnet 10.152.187.0 netmask 255.255.255.0 {
    #}
    
    # This is a very basic subnet declaration.
    
    #subnet 10.254.239.0 netmask 255.255.255.224 {
    #  range 10.254.239.10 10.254.239.20;
    #  option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
    #}
    
    # This declaration allows BOOTP clients to get dynamic addresses,
    # which we don't really recommend.
    
    #subnet 10.254.239.32 netmask 255.255.255.224 {
    #  range dynamic-bootp 10.254.239.40 10.254.239.60;
    #  option broadcast-address 10.254.239.31;
    #  option routers rtr-239-32-1.example.org;
    #}
    
    # A slightly different configuration for an internal subnet.
    #subnet 10.5.5.0 netmask 255.255.255.224 {
    #  range 10.5.5.26 10.5.5.30;
    #  option domain-name-servers ns1.internal.example.org;
    #  option domain-name "internal.example.org";
    #  option routers 10.5.5.1;
    #  option broadcast-address 10.5.5.31;
    #  default-lease-time 600;
    #  max-lease-time 7200;
    #}
    
    # Hosts which require special configuration options can be listed in
    # host statements.   If no address is specified, the address will be
    # allocated dynamically (if possible), but the host-specific information
    # will still come from the host declaration.
    
    #host passacaglia {
    #  hardware ethernet 0:0:c0:5d:bd:95;
    #  filename "vmunix.passacaglia";
    #  server-name "toccata.fugue.com";
    #}
    
    # Fixed IP addresses can also be specified for hosts.   These addresses
    # should not also be listed as being available for dynamic assignment.
    # Hosts for which fixed IP addresses have been specified can boot using
    # BOOTP or DHCP.   Hosts for which no fixed address is specified can only
    # be booted with DHCP, unless there is an address range on the subnet
    # to which a BOOTP client is connected which has the dynamic-bootp flag
    # set.
    #host fantasia {
    #  hardware ethernet 08:00:07:26:c0:a5;
    #  fixed-address fantasia.fugue.com;
    #}
    
    # You can declare a class of clients and then do address allocation
    # based on that.   The example below shows a case where all clients
    # in a certain class get addresses on the 10.17.224/24 subnet, and all
    # other clients get addresses on the 10.0.29/24 subnet.
    
    #class "foo" {
    #  match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
    #}
    
    #shared-network 224-29 {
    #  subnet 10.17.224.0 netmask 255.255.255.0 {
    #    option routers rtr-224.example.org;
    #  }
    #  subnet 10.0.29.0 netmask 255.255.255.0 {
    #    option routers rtr-29.example.org;
    #  }
    #  pool {
    #    allow members of "foo";
    #    range 10.17.224.10 10.17.224.250;
    #  }
    #  pool {
    #    deny members of "foo";
    #    range 10.0.29.10 10.0.29.230;
    #  }
    #
    #
    #
    #
    
    
    default-lease-time 600;
    max-lease-time 7200;
    ddns-update-style none;
    authoritative;
    log-facility local7;
    subnet 192.168.1.0 netmask 255.255.255.0{
    range 192.168.1.1 192.168.1.254;
    }
    next-server 192.168.1.2;
    filename "kboot.conf";
    option routers 192.168.1.1;
    
    host PS3{
    hardware ethernet 00:1f:a7:81:1d:72; # MAC address of PS3
    fixed-address 192.168.1.3; # PS3 IP address, you decide.
    }
    exports
    Code:
    # /etc/exports: the access control list for filesystems which may be exported
    #        to NFS clients.  See exports(5).
    #
    # Example for NFSv2 and NFSv3:
    # /srv/homes       hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
    #
    # Example for NFSv4:
    # /srv/nfs4        gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
    # /srv/nfs4/homes  gss/krb5i(rw,sync,no_subtree_check)
    #
    /mnt/experimental 192.168.1.2(rw,async,no_root_squash,no_subtree_check,anonuid=0,anongid=0)
    #/mnt/experimental 192.168.1.4/16(rw,async,no_root_squash,no_subtree_check,anonuid=0,anongid=0)
    kboot.conf
    Code:
    linux='vmlinux video=ps3fb:mode:2 root=/dev/nfs rw ip=dhcp nfsroot=192.168.1.3:/mnt/experimental panic=5'
    rpcinfo
    Code:
    prea@prea-dev:~$ rpcinfo -p
       program vers proto   port
        100000    2   tcp    111  portmapper
        100000    2   udp    111  portmapper
        100024    1   udp  59496  status
        100024    1   tcp  58250  status
        100021    1   udp  37426  nlockmgr
        100021    3   udp  37426  nlockmgr
        100021    4   udp  37426  nlockmgr
        100021    1   tcp  33013  nlockmgr
        100021    3   tcp  33013  nlockmgr
        100021    4   tcp  33013  nlockmgr
        100003    2   tcp   2049  nfs
        100003    3   tcp   2049  nfs
        100003    4   tcp   2049  nfs
        100227    2   tcp   2049
        100227    3   tcp   2049
        100003    2   udp   2049  nfs
        100003    3   udp   2049  nfs
        100003    4   udp   2049  nfs
        100227    2   udp   2049
        100227    3   udp   2049
        100005    1   udp  47827  mountd
        100005    1   tcp  50681  mountd
        100005    2   udp  47827  mountd
        100005    2   tcp  50681  mountd
        100005    3   udp  47827  mountd
        100005    3   tcp  50681  mountd
    Reply With Quote  

  10. #10  
    George234 is offline Member
    Join Date
    Aug 2010
    Posts
    84
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    1
    Likes Received
    15
    i did a quick search on google...as i did set this up myself and i followed this tut at the time

    Marcan Guide to Running Gentoo Linux on PS3

    ubuntu-desktop% sudo apt-get install dhcp3-server tftpd-hpa nfs-kernel-server

    http://marcansoft.com/transf/gentoo-...101020.tar.bz2 = rootfs
    Multiupload.com - upload your files to multiple file hosting sites! = kernel image and modules

    extract rootfs into /mnt/experimental:
    % sudo mkdir -p /mnt/experimental
    % sudo tar -C /mnt/experimental -xvpf /path/to/gentoo-ps3-20101020.tar.bz2

    then copy 2.6.36-rc7-01073-g47a9595-dirty from ps3linux.tar.gz into /mnt/experimental/lib/modules.

    Set up the DHCP server. Put this in /etc/dhcp3/dhcpd.conf:

    option domain-name "example.org";
    option domain-name-servers 8.8.8.8, 8.8.4.4;
    default-lease-time 600;
    max-lease-time 7200;
    ddns-update-style none;
    authoritative;
    log-facility local7;
    subnet 192.168.2.0 netmask 255.255.255.0 {
    range 192.168.2.128 192.168.2.250;
    }
    next-server 192.168.2.1;
    filename "kboot.conf";
    option routers 192.168.2.1;

    Set up your wired network interface (eth0) to have a static IP address "192.168.2.1".

    Copy vmlinux file into /var/lib/tftpboot.

    add this line to /etc/exports (requires root privs):

    /mnt/experimental 192.168.0.0/16(rw,async,no_root_squash,no_subtree_check,anonui d=0,anongid=0)

    Then everything is done. Let's start up the services:

    % sudo service tftpd-hpa restart
    % sudo service dhcp3-server restart
    % sudo service nfs-kernel-server restart

    Create a kboot.conf file in /var/lib/tftpboot with this line inside:

    linux='vmlinux video=ps3fb:mode:2 root=/dev/nfs rw ip=dhcp nfsroot=192.168.2.1:/mnt/experimental panic=5'

    That's all. Run Linux from lv2patcher v9 and see if it boots.

    btw u do know u can just attach a usb hub and all is well...i got 2 hubs attached to both my usb slots atm hehe

    also im sure i was reading somewhere kmeaw took out nfs support in the later revisions of asbestos and bootos
    Reply With Quote  

Posting Permissions
  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •