I don’t think you need the single quotes in the middle. I think at the u-boot
prompt you can just run:
setenv ’netboot=dhcp 0x4000000; setenv bootargs ${bootargs} root=/dev/nfs
rootpath=${rootpath},nfsver=4 ip=dhcp; bootm 0x4000000’
You can run printenv afterwards to see whether it did what we hope it will do.
If it does, I suggest running `run netboot` to test it out. If it works,
you’ll have to reboot, go into netboot, enter the `setenv` command again, then
run `saveenv`. I’m reluctant to change a known-though-non-working config to
something that may or may not work, so that’s why I suggest testing before
running `saveenv`. When in doubt, you can always reboot to “undo” any unsaved
changes.
Good luck,
Dave
> On Aug 23, 2022, at 3:19 PM, Gary, Dale E <[email protected]> wrote:
>
> Hi Dave,
>
> I think you are right that I found the place to do it, but I don't know what
> syntax to use to set the environment variable for
> netboot=dhcp 0x4000000; setenv bootargs ${bootargs} root='/dev/nfs'
> rootpath=${rootpath} ip=dhcp; bootm 0x4000000
> I am not sure what needs escaping, etc. Can I just add single quotes around
> the whole and escape the ticks? I guess I'll play with it.
>
> Regards,
> Dale
>
> On Tue, Aug 23, 2022 at 5:55 PM David Harold Edward MacMahon
> <[email protected] <mailto:[email protected]>> wrote:
> Hi, Dale,
>
> It sounds like you’ve found where to set the `vers=4` option. If that
> doesn’t work, it’s possible that the ROACH2s don’t support NFSv4. If that's
> the case (I’m not sure it is), then you may have to look into exporting the
> root filesystem via NFSv3 instead.
>
> I always have to double check the MTU configuration on the NFS server’s
> network interface. I think setting it to larger than 1500 won’t work for the
> ROACH2s.
>
> I’m curious to know what the solution ends up being!
>
> Cheers,
> Dave
>
>> On Aug 23, 2022, at 12:08 PM, Gary, Dale E <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> Hi All,
>>
>> I upgraded my remote boot server to a new machine running ubuntu 20.04, and
>> although I tried to set everything up the same for remote booting the
>> ROACH2s, the process fails as shown in the attached file because the root
>> file system could not be mounted. I found one suggestion on the web to edit
>> the Linux/PPC load configuration to add vers=4,tcp to the line, i.e. it
>> might look like this:
>> root=/dev/nfs nfsroot=192.100.16.206:/srv/roach2_boot/etch,vers=4,tcp ip=dhcp
>> but I cannot find any file where that configuration is set. There is a file
>> in /srv/roach2_boot called pxelinux.cfg that looks promising, but it is an
>> empty file. Am I on the right track?
>>
>> Any suggestions?
>> Thanks,
>> Dale
>>
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "[email protected] <mailto:[email protected]>" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected]
>> <mailto:[email protected]>.
>> To view this discussion on the web visit
>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAKeNqUiMwt1RWdSmW6qACbPptY_Dfc1TYiddZa6CdTdUDkDGSA%40mail.gmail.com
>>
>> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAKeNqUiMwt1RWdSmW6qACbPptY_Dfc1TYiddZa6CdTdUDkDGSA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
>> <ROACH_uboot_dialog.txt>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "[email protected] <mailto:[email protected]>" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected]
> <mailto:[email protected]>.
> To view this discussion on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/61DC9F78-39C0-4EF9-9F84-1E3704648F0D%40berkeley.edu
>
> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/61DC9F78-39C0-4EF9-9F84-1E3704648F0D%40berkeley.edu?utm_medium=email&utm_source=footer>.
>
> --
> You received this message because you are subscribed to the Google Groups
> "[email protected]" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected]
> <mailto:[email protected]>.
> To view this discussion on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAKeNqUgTWZpPgcYfn0ZjRp-9a%2BMH8RyVTn-94H5dRahTdHcmhA%40mail.gmail.com
>
> <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAKeNqUgTWZpPgcYfn0ZjRp-9a%2BMH8RyVTn-94H5dRahTdHcmhA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"[email protected]" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/C75BE57C-08FA-498D-BA6F-2F19E6CD61FB%40berkeley.edu.
