search for: fs0

...anced Features Kernel driver in use: e1000e Kernel modules: e1000e This might be the only wired NIC but there's possibly multiple device handles to it and possibly a device handle to the wrong NIC (wireless). In your EFI shell (hopefully you have such an option): version > fs0:\efi-ver.txt dh -p Net > fs0:\efi-dh-net.txt Feel free to run it without the redirect (">") to see the results yourself. The redirects would help if you can access the files so you don't need to manually transcribe the output. Here's some other UEFI Shell commands that ma...

On Mon, Aug 17, 2015 at 3:34 PM, Derrick M <derrick.martinez at gmail.com> wrote: > Gene > > Thanks for the reply. I didn't have a guid command, and couldn't find the > equivalent. dh > fs0:\efi-dh.txt worked, but dh -p Net did not so I ran dh Nothing of the sort listed with the help command to list the full GUIDs and their aliases? > -d -v -p SimpleNetwork > fs0:\efi-simplenetwork.txt Excellent job on finding the target alias. > Also attaching a screenshot from Oscar'...

...Parameters: failover.node=10.0.0.22@tcp failover.node=10.0.0.23@tcp sys.timeout=5000 2 mdt0: # zpool create -f -o ashift=12 -O canmount=off lustre-mdt0 mirror /dev/disk/by-id/wwn-0x50000c0f01d07a34 /dev/disk/by-id/wwn-0x50000c0f01d110c8 # mkfs.lustre --mdt --fsname=fs0 --servicenode=mds1@tcp0 --servicenode=mds2@tcp0 --param sys.timeout=5000 --backfstype=zfs --mgsnode=mds1@tcp0 --mgsnode=mds2@tcp0  lustre-mdt0/mdt0 warning: lustre-mdt0/mdt0: for Lustre 2.4 and later, the target index must be specified with --index    Permanent disk data:...

...dules: e1000e >> >> This might be the only wired NIC but there's possibly multiple device >> handles to it and possibly a device handle to the wrong NIC >> (wireless). >> >> In your EFI shell (hopefully you have such an option): >> >> version > fs0:\efi-ver.txt >> dh -p Net > fs0:\efi-dh-net.txt >> >> Feel free to run it without the redirect (">") to see the results >> yourself. The redirects would help if you can access the files so you >> don't need to manually transcribe the output. >&g...

...there's possibly multiple device > > > > handles to it and possibly a device handle to the wrong NIC > > > > (wireless). > > > > > > > > In your EFI shell (hopefully you have such an option): > > > > > > > > version > fs0:\efi-ver.txt > > > > dh -p Net > fs0:\efi-dh-net.txt > > > > > > > > Feel free to run it without the redirect (">") to see the results > > > > yourself. The redirects would help if you can access the files so you > > > >...

...t; > handles to it and possibly a device handle to the wrong NIC > > > > > > (wireless). > > > > > > > > > > > > In your EFI shell (hopefully you have such an option): > > > > > > > > > > > > version > fs0:\efi-ver.txt > > > > > > dh -p Net > fs0:\efi-dh-net.txt > > > > > > > > > > > > Feel free to run it without the redirect (">") to see the results > > > > > > yourself. The redirects would help if you can acce...

...3 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Mon, Aug 17, 2015 at 3:34 PM, Derrick M <derrick.martinez at gmail.com> > wrote: > > Gene > > > > Thanks for the reply. I didn't have a guid command, and couldn't find the > > equivalent. dh > fs0:\efi-dh.txt worked, but dh -p Net did not so I ran > dh > > Nothing of the sort listed with the help command to list the full > GUIDs and their aliases? > > > -d -v -p SimpleNetwork > fs0:\efi-simplenetwork.txt > > Excellent job on finding the target alias. > > &...

...3 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Mon, Aug 17, 2015 at 3:34 PM, Derrick M <derrick.martinez at gmail.com> > wrote: > > Gene > > > > Thanks for the reply. I didn't have a guid command, and couldn't find the > > equivalent. dh > fs0:\efi-dh.txt worked, but dh -p Net did not so I ran > dh > > Nothing of the sort listed with the help command to list the full > GUIDs and their aliases? > > > -d -v -p SimpleNetwork > fs0:\efi-simplenetwork.txt > > Excellent job on finding the target alias. > > &...

Hi, I am trying to create a boot cd for ia64 systems which will go into the efi shell, map to fs0 (cdrom) and give a help message on screen. I have tried creating a CD using isolinux but this boots as the Red Hat AW2.1 CD 1 and ignores the message file. After selecting the efi shell and mapping to fs0 then entering - elilo linux ks=nfs:<ip address>:<kickstart file> I get the message...

.../vmlinuz-3.14.33-101.el6.x86_64 -initrd /srv/overlay/kernels/grsec-3.14.33-101/initramfs-3.14.33-101.el6.x86_64.img -append root=virtfs:root rootflags=trans=virtio,version=9p2000.u rw rootfstype=9p -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -fsdev local,security_model=passthrough,id=fsdev-fs0,path=/srv/overlay/run/irc -device virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=root,bus=pci.0,addr=0x5 -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=28 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:00:10:10,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=c...

>>> I'm just debating what's the best algorithm here.? It would seem if the LoadeImage's DeviceHandle provides UDPv4Sb, use it as it's guaranteed to be the same interface.? Otherwise, we need a MNPSb (EFI_MANAGED_NETWORK_SERVICE_BINDING) that provides UDPv4Sb across the same interface.? Presumably it should also provide TCPv4Sb (rather than being on a separate

...uess. Do you have a shell option in your boot selections? Looking to get data like I did for an HP system in http://www.syslinux.org/archives/2015-August/023999.html http://www.syslinux.org/archives/2015-August/024005.html and http://www.syslinux.org/archives/2015-August/024055.html version > fs0:\efi-ver.txt guid > fs0:\efi-guid.txt or alias > fs0:\efi-alias.txt dh > fs0:\efi-dh.txt dh -p Net > fs0:\efi-dh-net.txt I'm guessing a lack of TCPv4Sb (an alias for the EFI_TCP4_SERVICE_BINDING_PROTOCOL ). > Somehow I was under the impression improvements from pxelinux v...

...EFI shell (hopefully you have such an option): I only have BIOS access on this laptop and no UEFI or some such, I am attempting to install the initial UEFI boot on the laptop. Did try to disable all Wireless options in BIOS and tested again but got the same error. Jocke > > version > fs0:\efi-ver.txt > dh -p Net > fs0:\efi-dh-net.txt > > Feel free to run it without the redirect (">") to see the results > yourself. The redirects would help if you can access the files so you > don't need to manually transcribe the output. > > Here's som...

...e1000e > Kernel modules: e1000e > > This might be the only wired NIC but there's possibly multiple device > handles to it and possibly a device handle to the wrong NIC > (wireless). > > In your EFI shell (hopefully you have such an option): > > version > fs0:\efi-ver.txt > dh -p Net > fs0:\efi-dh-net.txt > > Feel free to run it without the redirect (">") to see the results > yourself. The redirects would help if you can access the files so you > don't need to manually transcribe the output. > > Here's som...

...gt;> This might be the only wired NIC but there's possibly multiple device >>> handles to it and possibly a device handle to the wrong NIC >>> (wireless). >>> >>> In your EFI shell (hopefully you have such an option): >>> >>> version > fs0:\efi-ver.txt >>> dh -p Net > fs0:\efi-dh-net.txt >>> >>> Feel free to run it without the redirect (">") to see the results >>> yourself. The redirects would help if you can access the files so you >>> don't need to manually transcrib...

...t; > handles to it and possibly a device handle to the wrong NIC > > > > > > (wireless). > > > > > > > > > > > > In your EFI shell (hopefully you have such an option): > > > > > > > > > > > > version > fs0:\efi-ver.txt > > > > > > dh -p Net > fs0:\efi-dh-net.txt > > > > > > > > > > > > Feel free to run it without the redirect (">") to see the results > > > > > > yourself. The redirects would help if you can acce...

...multiple device >> > > > handles to it and possibly a device handle to the wrong NIC >> > > > (wireless). >> > > > >> > > > In your EFI shell (hopefully you have such an option): >> > > > >> > > > version > fs0:\efi-ver.txt >> > > > dh -p Net > fs0:\efi-dh-net.txt >> > > > >> > > > Feel free to run it without the redirect (">") to see the results >> > > > yourself. The redirects would help if you can access the files so you >&...

...it and possibly a device handle to the wrong NIC >> > > > > > (wireless). >> > > > > > >> > > > > > In your EFI shell (hopefully you have such an option): >> > > > > > >> > > > > > version > fs0:\efi-ver.txt >> > > > > > dh -p Net > fs0:\efi-dh-net.txt >> > > > > > >> > > > > > Feel free to run it without the redirect (">") to see the results >> > > > > > yourself. The redirects would help...

.../vmlinuz-3.14.33-101.el6.x86_64 -initrd /srv/overlay/kernels/grsec-3.14.33-101/initramfs-3.14.33-101.el6.x86_64.img -append root=virtfs:root rootflags=trans=virtio,version=9p2000.u rw rootfstype=9p -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -fsdev local,security_model=passthrough,id=fsdev-fs0,path=/srv/overlay/run/irc -device virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=root,bus=pci.0,addr=0x5 -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=28 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:00:10:10,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=c...

> > Is syslinux.efi supposed to be able to handle HTTP URLs? > > If the underlying firmware can. Try just specifying an HTTP URL in the > config or on the command line instead of the path-prefix option. Doesn't work. Apparently the Dell UEFI PXE firmware doesn't know HTTP. Somehow I was under the impression improvements from pxelinux variants like lpxelinux were