Eeso

Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Eeso

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Eeso

    DSM 6.2 Loader

    All good now, the 3617 loader was requiring the BIOS to be swtiched from UEFI to legacy mode
  2. So all seems sorted now and the drivers are working here as well, thank you very much for you work and patience
  3. Okey actually you were right, it boots now, seems to have been when I changed from UEFI to legacy also.. Didn't test 3617 until now on that configuration I thought it wasn't the problem when all the others were working, I'm assuming too much, I can see it is a great deal of hacking for it to run Well that is good, I will try to load the drivers now Ah alright
  4. Aha okey, such a shame I guess I have to get 3617 running then, do you know if any grub debug can be enabled as it tries to unpack and load the kernel and initrd? What is it the with the different zImage I changed on my usb then? If it can't be/no point in being changed I mean, it's a bit confusing
  5. Where do I find the source and toolchain of the kernels? CONFIG_X86_X2APIC seems to be valid for 4.4 as well Would you mind help me and try to compile 918+ with that flag set? I was in the BIOS but I couldn't find anything regarding any such thing
  6. Okey so I found some interesting things with 1.04b which made me wounder. This comes up in the dmesg [ 0.208866] ACPI: NR_CPUS/possible_cpus limit of 1 reached. Processor 1/0x0 ignored. [ 0.208867] ACPI: Unable to map lapic to logical cpu number [ 0.208887] ACPI: NR_CPUS/possible_cpus limit of 1 reached. Processor 2/0x2 ignored. [ 0.208888] ACPI: Unable to map lapic to logical cpu number [ 0.208909] ACPI: NR_CPUS/possible_cpus limit of 1 reached. Processor 3/0x4 ignored. [ 0.208910] ACPI: Unable to map lapic to logical cpu number [ 0.208926] ACPI: NR_CPUS/possible_cpus limit of 1 reached. Processor 4/0x6 ignored. [ 0.208927] ACPI: Unable to map lapic to logical cpu number These seems to be a common thing for linux when it doesn't find all the cores, the solution vary for some, seems to be either to switch bios mode from UEFI to legacy or to enable x2apic in the kernel I tried to switch bios to legacy, I changed it to UEFI for another distro a while back. This didn't do the trick however, do you know if the kernel has the x2apic config enabled (CONFIG_X86_X2APIC to be exact)?
  7. Ye I know, but only 1.04b / 918+ doesn't recognize the other 3 cores, I will recheck Still it seems to be some kind of problem, I remember the 6.1 loader for 3615/3617 do this, it also worked good with the other dists I've tried on this server, but I will recheck this as well cpuinfo exactly Yes gonna do that and document it better this time and I'll report back on my findings Ye I thought it was only that, turns out it wasn't, thanks for heading me in the right direction Ye I tried and all looks good (I thought), except that the 1.03b explicitly says it only supports the intel e1000 nic, which I don't have My logical reasoning was that it was only missing the wrong driver.. Since all other things I've tried have worked. I never checked the VSP before this. My bad Unfortunately I need 6.2, running 6.1 works fine for all simulated models, but one virtualization option is missing in VMM prior to 6.2, or rather you need a pro license enable it, which is free in 6.2. Seems to be bad to try to buy such a license for this I gonna check if there is something that can be done with that
  8. Eeso

    DSM 6.2 Loader

    Hi, So the 1.03b loader for 3615/3617 doesn't load the kernel It prints the grub menu, the intro in info.txt and then hangs the 1.02b loader for all models works, and also the 1.04b loader for 918+ possible to enable debug for grub or something to see and understand what goes wrong? Any help appreciated Thanks
  9. Okey so I don't get jun's loader to load, I suppose its the same for you? did you check with him? I'll go and try to get some clarity over at his thread instead
  10. The problem with 918+ is that I don't think it uses all my cores, it's really slow multitasking and would only list one of the cores in /proc, would 0.7 change anything? Ye it has iLO, so via the VSP it seems it doesn't load the kernel actually, all fine on 918+ And I thought I was only lacking the right driver Does it boot 3615/3517 if you only jun's original 1.03b loader? Gonna try and see what happens
  11. Its a HP ProLiant DL20 Gen9, with a Xeon E3-1220 v5 I think, should be close to what this says otherwise https://certification.ubuntu.com/hardware/201605-22006 Ye weird it works on the microserver and not on my or yours, it prints the message that the display will no longer be update, does it mean it has unpack the kernel? Can I just inject the tg3.ko file somehow? I think thats the only thing I need for now Thanks
  12. Hi, Seems like I can't get the tg3 driver to work, not sure what is wrong My current working setup is jun's 1.04b 918+ loader, lspci says 2x 14e4:165f, and lsmod says libphy -> tg3 So it has 2x Broadcom NetExtreme BCM5720 NIC, and they are working on this 918+ configuration I made a new USB with jun's 1.03b loader, tried both 3615xs/3617xs, changed the grub.cfg with vid/pid, sn, mac, netif's Copied over the correct zImage, rd.gz and extra.lzma for each try It boots but never comes up on the network Any help on how to proceed is appreciated Thanks -- Eeso
  13. Can someone else PM me the files for testing this out while we wait for the final version?
  14. Hi, I have a BCM5720 network card, I would like to try your tg3 driver for both 3615xs and 3617xs in the 1.03b loader, want to test DSM 6.2.x Can you PM me the extra.lzma? Thanks!