• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Latitude 5290 2-in-1 with Dell USB-C Mobile Adapter - DA300 : fail udhcpc

Scheduled Pinned Locked Moved
Hardware Compatibility
2
2
479
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • F
    FredG
    last edited by Oct 17, 2019, 7:44 AM

    Hello everyone,

    Server:
    Ubuntu 16.04.6 LTS
    Fog 1.5.7

    Client:
    Dell Latitude 5290 2-in-1
    Dell USB-C Mobile Adapter - DA300
    MAC Address pass through (only choice)

    efi files tested :
    intel7156.efi
    intel.efi
    ipxe7156.efi
    ipxe.efi
    realtek7156.efi
    realtek.efi
    snp7156.efi
    snp.efi
    snponly7156.efi
    snponly.efi

    Phase 1 successful for :
    ipxe7156.efi
    ipxe.efi
    snp.efi
    snponly7156.efi
    snponly.efi

    Phase 2 does not work
    fail udhcpc

    Because an image is more explicit than a speech, i have attached Phase 1 and Phase 2.

    I have no problem with a rj45 usb adapter

    Sincerely!

    Phase 1
    Phase1.jpg

    Phase 2
    Phase2.jpg

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by Oct 17, 2019, 10:28 AM

      If you are seeing bzImage being transferred you can remove iPXE out of the problem. The default you should have for uefi is ipxe.efi.

      Now you should focus on the FOS Linux engine (bzImage). What version is the FOS Linux kernel? I know I have a Dell 7400 2 in 1 with a Dell usb c dongle (as well as a WD15/WD19 docks) that boot into FOS Linux and pick up a dhcp address.

      I find it strange that it finds the network adapter, and sees the link come up but can’t communicate over that link. Lets start with what version of kernel are you using? The next part is to schedule a new capture/deploy task but tick the debug check box before you schedule the task. Then pxe boot the target computer that will but the target computer in debug mode so we can key in some additional commands.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

      1 Reply Last reply Reply Quote 0
      • 1 / 1
      1 / 1
      • First post
        2/2
        Last post

      165

      Online

      12.1k

      Users

      17.3k

      Topics

      155.4k

      Posts
      Copyright © 2012-2024 FOG Project