• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. abos_systemax
    3. Posts
    A
    • Profile
    • Following 0
    • Followers 0
    • Topics 19
    • Posts 132
    • Best 4
    • Controversial 0
    • Groups 0

    Posts made by abos_systemax

    • RE: FOG - boot to FOS - rcu_sched self-detected stall on CPU

      @Tom-Elliott both 4.6.4 and 4.5.0 give the same error as the 4.8.1 bzImage32s

      e1: i even went as far as downgrading to 3.0.1, but that one results in a blinking cursor on the top left
      e2: as does 4.1.0

      e3: 4.2.0 is the first kernel to display the rcu_sched error apparently

      posted in FOG Problems
      A
      abos_systemax
    • RE: FOG - boot to FOS - rcu_sched self-detected stall on CPU

      @Tom-Elliott it does appear to be model related because the other device also isn’t able to boot (with the same rcu_sched messages)

      posted in FOG Problems
      A
      abos_systemax
    • RE: FOG - boot to FOS - rcu_sched self-detected stall on CPU

      @Tom-Elliott
      I was trying to understand that document when I found it on google, but am unfamilair with all the abbreviations used, I am also a ‘transitioner’ from Windows to Linux, so it isn’t my forté yet.

      I have more devices of the kind, will test as soon as I receive the other from our warehouse

      posted in FOG Problems
      A
      abos_systemax
    • RE: FOG - boot to FOS - rcu_sched self-detected stall on CPU

      @Tom-Elliott
      It does indeed stall in the Full registration as well.
      Enableling VT/VTd doesnt resolve the issue

      posted in FOG Problems
      A
      abos_systemax
    • RE: FOG - boot to FOS - rcu_sched self-detected stall on CPU

      It’s the fact that it doesn’t do anything but displaying the message over and over again, so it does prevent functionality.

      I have found references online to a BIOS setting named AMD C1E, but this is an Intel board, so that might not be the solution; maybe there is an equivalent to it…

      However, this message should not stall the device I’d assume based on your reply?

      posted in FOG Problems
      A
      abos_systemax
    • FOG - boot to FOS - rcu_sched self-detected stall on CPU
      Server
      • FOG Version: 3 RC21
      • OS: Debian Jessy
      Client
      • Lenovo E560
      • BIOS: Legacy
      Description

      Hello,

      When I try to boot to the Quick Host Registration on FOG, I see a screen with the following info:

      INFO: rcu_sched self-detected stall on CPU
      o0-…: (337893 ticks this GP) idle=439/14000000000001/0 softirq=119/146 fqs=83192
      o (t=336015 jiffies g=-274 c=-275 q=168)

      This info displays every so often with different numbers every time.

      bzImage Version: 4.8.1
      bzImage32 Version: 4.8.1

      it boots using the bzImage32

      edit: just updated to RC21, problem still exists
      edit2: changed the title, the issue is not only for the Quick reg, it’s the entire FOG OS that doesn’t boot

      posted in FOG Problems
      A
      abos_systemax
    • RE: IPXE error 0x7f048283 on Lenovo m700

      The issues is not yet resolved, however putting the device in Legacy Mode did provide a workaround.
      it has the 2nd latest firmware, that might be an issue but we are not allowed to update the firmware because it is not our own hardware.

      posted in FOG Problems
      A
      abos_systemax
    • IPXE error 0x7f048283 on Lenovo m700
      Server
      • FOG Version: RC19
      • OS: Debian Jessy
      Client
      • OS: Windows 7
      Description

      I receive error iPXE 0x7f048283 (twice) when booting a Lenovo M700.
      This machine uses UEFI to boot which wás working at RC11 (last confirmed working RC)

      The boot process works on other devices, so it must be device related.

      posted in FOG Problems
      A
      abos_systemax
    • RE: Is it possible to image a client from USB, without the FOG server?

      @utopia Thanks for your ‘essay’ (reply). I tried the other way around not very long ago (a ConeZilla image to FOG) but that did not work out very well and I ended up restoring the CZ image to a device and capturing in with FOG so I don’t think that FOG and CZ are interoparable yet.

      I will likely use your method to provision our engineer at the location, thank you.

      posted in General Problems
      A
      abos_systemax
    • RE: Is it possible to image a client from USB, without the FOG server?

      @george1421 Thanks!

      posted in General Problems
      A
      abos_systemax
    • RE: Is it possible to image a client from USB, without the FOG server?

      No, I meant a device with no access to a FOG server; so it has a local image on the USB from where it ‘fogs’

      Can I ‘just use’ the PartClone command to initiate that?

      posted in General Problems
      A
      abos_systemax
    • Is it possible to image a client from USB, without the FOG server?

      Well, the title kinda states it already. We want to service a remote site with just a few machines. We’d like to use USB for this, is that possibile?

      posted in General Problems
      A
      abos_systemax
    • RE: Lenovo Yoga 11e

      @george1421
      I cannot remember seeing anything different than now; you are right that it doesn’t get to FOS; if I load the bzImage by hand, it’ll crash with the same error. This means that it doesn’t even reach the imgfetch init.xz at all

      posted in Hardware Compatibility
      A
      abos_systemax
    • RE: Lenovo Yoga 11e

      @Tom-Elliott

      If I remove the preceding slash before Image Path, the //Images gets changed to /Images; however: It would seem that the WebRoom, FTP Path, SnapinPath and SSL Path are all wrong as well?

      alt text

      posted in Hardware Compatibility
      A
      abos_systemax
    • RE: Lenovo Yoga 11e

      @Tom-Elliott

      http://192.168.68.13/fog/service/ipxe/boot.php?mac=54🆎3a:eb:15:37

      #!ipxe
      set fog-ip 192.168.68.13
      set fog-webroot fog
      set boot-url http://${fog-ip}/${fog-webroot}
      kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.68.13/fog/ consoleblank=0 rootfstype=ext4 mac=54:ab:3a:eb:15:37 ftp=192.168.68.13 storage=192.168.68.13://images/dev/ storageip=192.168.68.13 osid=9 irqpoll hostname=54ab3aeb1537 chkdsk=0 img=KansKleur_PaschalisSchool imgType=mps imgPartitionType=all imgid=18 imgFormat= PIGZ_COMP=-6 shutdown=1 hostearly=1 pct=5 ignorepg=1 type=up
      imgfetch init_32.xz
      boot
      

      And with &arch=x86_x64
      http://192.168.68.13/fog/service/ipxe/boot.php?mac=54🆎3a:eb:15:37&arch=x86_64

      #!ipxe
      set fog-ip 192.168.68.13
      set fog-webroot fog
      set boot-url http://${fog-ip}/${fog-webroot}
      kernel bzImage loglevel=4 initrd=init.xz root=/dev/ram0 rw ramdisk_size=127000 web=192.168.68.13/fog/ consoleblank=0 rootfstype=ext4 mac=54:ab:3a:eb:15:37 ftp=192.168.68.13 storage=192.168.68.13://images/dev/ storageip=192.168.68.13 osid=9 irqpoll hostname=54ab3aeb1537 chkdsk=0 img=KansKleur_PaschalisSchool imgType=mps imgPartitionType=all imgid=18 imgFormat= PIGZ_COMP=-6 shutdown=1 hostearly=1 pct=5 ignorepg=1 type=up
      imgfetch init.xz
      boot
      
      posted in Hardware Compatibility
      A
      abos_systemax
    • RE: Lenovo Yoga 11e

      @Tom-Elliott as Requested
      bzImage Fail

      posted in Hardware Compatibility
      A
      abos_systemax
    • RE: Quick Registration --> Return to iPXE boot menu instead of reboot

      @Tom-Elliott Thanks for that reply.
      I am only (really) interested in the Serial/MAC address combination of the devices that I boot, so I’ll develop a bootmenu.php that posts these values to my own database and waits for the user to create a multicast task then.

      Is it possible to remove the auto reboot feature however? (replace it with a … press any key to continue), that way the engineer can still quick register, but doesnt need to be present (and thus can move on to start/register different machines)

      posted in Feature Request
      A
      abos_systemax
    • RE: Quick Registration --> Return to iPXE boot menu instead of reboot

      @Wayne-Workman
      but requires user input…

      I need all the basic information from the device to be available as soon as the device is booted to PXE (well, after the said quick registration).

      This way, the engineer only needs to boot the device to PXE once, the device will QuickReg itself and return to the IPXE menu, from this point the menu will just stay put until the engineer starts a multicast task selecting all the online hosts

      However, since it is possible in the Full Registration, I’ll take a look in that process to see if I can create it / edit it into the Quick Registration

      posted in Feature Request
      A
      abos_systemax
    • RE: Quick Registration --> Return to iPXE boot menu instead of reboot

      @Wayne-Workman
      Yes. I always want a device to be registered, but do not wish to reboot in between. This causes too much work for our engineers. (because they have to be (and stay) present at the device in case it reboots and press F12 as soon as it does this, else it will reboot to Windows (and that’s quite the fuss to shutdown since windows 😎

      posted in Feature Request
      A
      abos_systemax
    • Quick Registration --> Return to iPXE boot menu instead of reboot

      Howdy,

      Is it possible for the Quick registration option to return to the iPXE boot menu instead of rebooting the system?

      posted in Feature Request
      A
      abos_systemax
    • 1
    • 2
    • 3
    • 4
    • 5
    • 6
    • 7
    • 4 / 7