similar to: RHEL 7 Beta Hidden WIFI issue

I have a file Server CentOS 5.10, its on the internet, so I compress all csv into one file using (tar -czvf compressed_files.tar.gz *.csv) on this server so that I can download them as one compressed file to save bandwidth, Disk space on this server available is 50Gig, so when I copy the files onto Redhat EL 5.9 and decompress them using (tar -zxvf *.gz) It decompresses maybe 80% then get error:

Hi there, I have experienced problems on HP Elitebook 2560p and 8460p latest firmware installed: 2560p 68SSU ver. F50. 08/04/2014 8460p 68SCF ver. F50. 08/04/2014 PXE boot, syslinux.efi gets perfectly TFTP transferred, it nevers asks for ldlinux.e64, and immediately gives up. I have traced the problem to: /syslinux-6.03/efi/udp.c\core_udp_open()

>>> > It does contain a Net but there are 2 issues with SNP: > 1) The interface is different than UDPv4/TCPv4 protocols; this imply lot of code. Not as much as you may think.? We already have lwIP implemented into lpxelinux.0.? It's more a matter of using more glue. > 2) SNP has its non-blocking transmit issues ; see "Flaws in the design" at >

> > Today there are certain PCs i.e Elitebook 2560p, Elitebook 8460p that with > updated FW ""to the last known version"" cannot PXE boot syslinux for the > above mentioned reasons. > > We have already talked about this with Gene an there's an strategy for making > syslinux able to deal with these "weirdo" FWs. > It's just a matter

>>> 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

On Fri, Aug 14, 2015 at 11:42 AM, Patrick Masotta via Syslinux <syslinux at zytor.com> wrote: >>>>> > website (meaning, HP could test their firmware to be compatible with > Syslinux and with non-Windows OSes). If the HP firmware could be made > (more) compliant with UEFI specs, or if it could be improved and still > be compliant with UEFI specs, wouldn't

I have a CentOS6.3 SAMBA file server. All the users are on a Windows Server 2008 Active Directory Domain Controller and authentication is done using Winbind integration on SAMBA . Everything works well except that if someone logs on to the Samba Server, they see all the shared folders there and also a folder with their own name %USER%. This Folder is not accessible, one cannot enter into this

>>> > 1) There's not "any" SB protocol present (Elitebook 8460p/2560p) The only solution for these is to use our own stack (likely full TCP/IP like lwIP) and connect to the Net GUID (EFI_SIMPLE_NETWORK_PROTOCOL).? Does the handle for Pxebc contain a Net?? >>> It does contain a Net but there are 2 issues with SNP: 1) The interface is different than

> Not being able to boot should probably qualify > as good reason for HP to update the > firmware, IMHO. > I agree but considering the problem appears when PXE booting an EFI image requiring the Binding Services of the NIC well I'm not really sure if they would pay any attention. BTW the same failing hardware has not problem booting MS bootmgr.efi but analyzing its code I see

> What about to your HP mail? I'd definitely advise the latest as I merged > some commits this weekend. > > --Gene Hmm... Shamelessly, and off-topic, but not _that_ much... :) For several months we have seen reports (of different matters) here in the Syslinux Mailing List in which some HP model(s) have been having problems network-booting (in UEFI mode; I don't recall

> Hi All, > > My PXE configurations works fine for a bios PXE (the server in legacy > mode) but hangs in an EUFI mode. Look like it can transfer the bootx64.efi > but not the next one ldlinux.e64 > > > Any ideas? > > Thanks > Latest updates (including firmware) for the HP ML350 Gen9 were released on 2014DEC19 (v1.21); I would suggest double-checking

>>> Jeff, Patrick: Could you try my code from my github repo branch efi-multinic?? It's derived from Patrick's code and I finally see good responses with a VMware VM's e1000e NIC (never saw ANYTHING good from it until now). git://github.com/geneC/syslinux.git https://github.com/geneC/syslinux.git -- -Gene <<< Hi there I think in the case of a particular

Hie I lost my CentOS 7 root password, so I tried booting the OS in single user mode but it prompts me for the root password when the system boots, Any ideas? Regards Bonnie

>>> Lovely, the ServiceBindings are on a handle that resembles the NIC while the Pxebc is IP-type specific.? Looks like we should try to do a ServiceBinding based on Pxebc but fall back to MAC-based searching, saving all 3 handles, the image handle, Pxebc handle, and ServiceBinding handle.? Presumably the UDP and TCP handles _should_ be the same... -- -Gene <<< OK now it

1.. Is it even possible? Every example I've seen has bridged eth* rather wlan*. 2.. If it helps here are my scripts: $ more /etc/sysconfig/network-scripts/ifcfg-wlan0 ESSID="snip" MODE=Managed KEY_MGMT=WPA-PSK TYPE=Wireless BOOTPROTO=dhcp DEFROUTE=yes PEERDNS=yes PEERROUTES=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no NAME=wlan0 UUID=2b508481-ec01-4311-8903-af7aaeb9879d ONBOOT=yes

Hie Guys Has anyone managed to run VMware WorkStation 10.0.3 on CentOS 7? Mine ask for some modules to be compiled and loaded into the running Kernel before VMware can run, then an ERROR copy or error below: 2014-07-21T09:01:41.429+02:00| vthread-3| I120: The header path "/lib/modules/3.10.0-123.4.2.el7.x86_64/build/include" for the kernel "3.10.0-123.4.2.el7.x86_64"

Hey everyone, sorry for the delay in replying. First off, thanks for all the help, effort and support so far! == build == I built and used syslinux from https://github.com/ppatpat/syslinux (latest commit 43f5efa2db4a7880c7a2c6485d8fd8a64f0f33c3). On top of that I had to patch main.c. This had to be done to mitigate the following error when trying to 'make all': main.c:(.text+0x3b9):

> > Not being able to boot should probably qualify > > as good reason for HP to update the > > firmware, IMHO. > > > I agree but considering the problem appears when > PXE booting an EFI image requiring the Binding Services > of the NIC well I'm not really sure if they would pay any attention. > BTW the same failing hardware has not problem booting > MS

Hi All, My PXE configurations works fine for a bios PXE (the server in legacy mode) but hangs in an EUFI mode. Look like it can transfer the bootx64.efi but not the next one ldlinux.e64 Any ideas? Thanks Software> syslinux ver 6.3 atftp 7.1 Log server side >> Booting Embedded LOM 1 Port 1 : HP Ethernet 1Gb 4-port 331i Adapter - NIC (PXE IPv4) >> Booting PXE over

Hi, I have an Elitebook but I am unable to even load the kernel or get to a point where user interaction is posible. The bootloader reboots the machine just before or after the amount of memory is shown. Anyone with simliar problems an newer HP notebooks? Gr Matthias