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

Dell Optiplex 330 PXE Graphics corruption

Scheduled Pinned Locked Moved
Hardware Compatibility
2
5
1.8k
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.
  • T
    twowaynet
    last edited by Mar 19, 2014, 4:07 PM

    Hi guys,

    I’ve got a Dell Optiplex 330’s that I am trying to upload an image from. The PXE process takes place, I get some kernel warnings that I always get on just about machine, stuff like, “[SIZE=2][FONT=arial][COLOR=#545454]Could not find Carillo Ranch MCH device[/COLOR][/FONT][/SIZE]”, it waits for several seconds then my screen goes wonky. I’m guessing there is some sort of error message here but I can’t read it because the screen is pixelated static. I’ts not a moving static like a 90’s TV without a signal, it’s non-changing, a static static. After about a minute the computer resets, and the process repeats itself.

    I know several Optiplex machines have issues with fog as seen here: [url]http://www.fogproject.org/wiki/index.php/ProblematicDevices[/url] But I’m hopeful that I can find a workaround as I have several Optiplex machines I need to deploy images to. Anyone know how I can figure out what’s wrong? Are there any logs I can take a look at on the fog server?

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by Mar 19, 2014, 4:14 PM

      Try my kernel.

      [url]https://mastacontrola.com/fogboot/kernel/bzImage32[/url]

      Save it on your fog server as /tftpboot/fog/kernel/bzImage

      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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

      1 Reply Last reply Reply Quote 0
      • T
        twowaynet
        last edited by Mar 19, 2014, 9:39 PM

        Cool beans. Using your kernel, the screen didn’t go all wonky and now I’m able to read the errors!

        Could you tell me about your kernel? I’m wondering what the differences are that makes it work with the optiplex 330.

        1 Reply Last reply Reply Quote 0
        • T
          Tom Elliott
          last edited by Mar 19, 2014, 9:41 PM

          When the screen goes all wonky, it’s not really at the kernel layer, its one of the video drivers. It tries to perform modesetting which screws up somewhere in the process. The kernel is usually still operating perfectly fine, just you can’t see it. My kernels have removed all of the video drivers so this doesn’t happen.

          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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

          Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

          Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

          1 Reply Last reply Reply Quote 0
          • T
            twowaynet
            last edited by Mar 20, 2014, 12:49 AM

            Excellent! Haha that’s a great solution. Thank you very much.

            The error was because I had the image set to single partition, when there were two partitions on disk. The first partition was a Dell recovery partition.

            For the interested, I recorded a video of the original graphics problem: [media=youtube]KQtLIqUWeQk[/media]

            1 Reply Last reply Reply Quote 0
            • 1 / 1
            1 / 1
            • First post
              3/5
              Last post

            249

            Online

            12.1k

            Users

            17.3k

            Topics

            155.4k

            Posts
            Copyright © 2012-2024 FOG Project