• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. koenr
    K
    • Profile
    • Following 0
    • Followers 0
    • Topics 0
    • Posts 2
    • Best 0
    • Controversial 0
    • Groups 0

    koenr

    @koenr

    0
    Reputation
    1
    Profile views
    2
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    koenr Unfollow Follow

    Latest posts made by koenr

    • RE: Dell Latitude 3500

      I got it working, using the realtec.efi driver. It took me some time to realise that the short vendor-class versions take over the later set long ones. Commenting out previous Arch:00007 was necessary.
      Now the L3420 doesn’t install anymore, but I know were to look …

      class "Legacy" {
          match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000";
          filename "undionly.kkpxe";
      }
      class "UEFI-32-2" {
          match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002";
          filename "i386-efi/snponly.efi";
      }
      class "UEFI-32-1" {
          match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006";
          filename "i386-efi/snponly.efi";
      }
      #class "UEFI-64-1" {
      #    match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
      #    filename "snponly.efi";
      #}
      class "UEFI-64-2" {
          match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008";
          filename "snponly.efi";
      }
      class "UEFI-64-3" {
          match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009";
          filename "snponly.efi";
      }
      #class "SURFACE-PRO-4" {
      #    match if substring(option vendor-class-identifier, 0, 32) = "PXEClient:Arch:00007:UNDI:003016";
      #    filename "snponly.efi";
      #}
      class "Apple-Intel-Netboot" {
          match if substring(option vendor-class-identifier, 0, 14) = "AAPLBSDPC/i386";
          option dhcp-parameter-request-list 1,3,17,43,60;
          if (option dhcp-message-type = 8) {
              option vendor-class-identifier "AAPLBSDPC";
              if (substring(option vendor-encapsulated-options, 0, 3) = 01:01:01) {
                  # BSDP List
                  option vendor-encapsulated-options 01:01:01:04:02:80:00:07:04:81:00:05:2a:09:0D:81:00:05:2a:>
                  filename "snponly.efi";
              }
          }
      }
      
      class "LATITIDE-3340" {
          match if substring(option vendor-class-identifier, 0, 32) = "PXEClient:Arch:00007:UNDI:003016";
          filename "realtek.efi";
      }
      
      posted in Hardware Compatibility
      K
      koenr
    • RE: Dell Latitude 3500

      Unfortunately I can’t offer any help, just a me too.

      I see the same problem on Latitude 3440 and Latitude 3540, latest Bios, latest FOG, latest Kernel, Bios settings as they should on an installation that installed already 1000ths of devices (e.g. today 80 Latitude 3310 - no problem)

      They boot fine over the network, but it goes wrong after the selection of the image to deploy (not registered host - host registration fails too). The big difference between the working L3310 and the not working devices I noticed, is that at some point all cksums in the tcp stream are incorrect.

      alioth.http > 10.4.50.87.26147: Flags [.], cksum 0x4c2e (incorrect -> 0x7455), seq 2483321:2484769, ack 118, win 509, options [nop,nop,TS val 1727144768 ecr 204544], length 1448: HTTP
      

      using tcpdump -s0 -vvv -i enp2s0 ether host ac:1a:3d:a4:dd:36

      while with a working setup the failed checksums are rare.

      I’m pulling my hair out - I’m out of ideas and 250 devices to deploy 😞

      posted in Hardware Compatibility
      K
      koenr