jun

DSM 6.2 Loader

Recommended Posts

Ok ... Thanks for Info and direct Link :)

 

But how can I update to the newest version?

No Problem to create a USB-Loader-Stick with 918+ and migrate my System from 3615xs to 918+

But without a Serialnumber for the 918+ I can't install this :(

 

Share this post


Link to post
Share on other sites

Back to the Asrock boards:

 

J3455B-ITX: works

J3455-M: works

J3455-ITX: i915 driver fails which explains why /dev/dri is missing:

===== trigger device plug event =====
[  219.079271] BUG: unable to handle kernel NULL pointer dereference at           (null)
[  219.087187] IP: [<          (null)>]           (null)
[  219.092288] PGD 1783da067 PUD 1783db067 PMD 0
[  219.096825] Oops: 0010 [#1] PREEMPT SMP
[  219.100846] Modules linked in: i915(E+) drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) cfbfillrect(E) cfbcopyarea(E) cfbimgblt(E) drm(E) fb(E) fbdev intel_agp(E) intel_gtt(E) agpgart(E) video backlight button synoacl_vfs(PO) hfsplus md4 hmac r8168(OE) ixgbe(E) igb(E) i2c_algo_bit e1000e(E) vxlan ip6_udp_tunnel udp_tunnel fuse vfat fat crc32c_intel aesni_intel glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance acpi_cpufreq processor cpufreq_stats dm_snapshot dm_bufio crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram sg etxhci_hcd rtc_cmos(E) mdio(E) mpt3sas(E) raid_class(E) scsi_transport_sas(E) megaraid_sas(E) megaraid(E) mptctl(E) mptspi(E) mptscsih(E) mptbase(E) scsi_transport_spi(E) megaraid_mbox(E) megaraid_mm(E) vmw_pvscsi(E) BusLogic(E) usb_storage xhci_pci xhci_hcd usbcore usb_common imwz(OE) [last unloaded: apollolake_synobios]
[  219.193595] CPU: 3 PID: 6837 Comm: insmod Tainted: P           OE   4.4.59+ #23824
[  219.201196] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./J3455-ITX, BIOS P1.80 05/21/2018
[  219.210792] task: ffff880178b0e240 ti: ffff880072450000 task.ti: ffff880072450000
[  219.218296] RIP: 0010:[<0000000000000000>]  [<          (null)>]           (null)
[  219.225833] RSP: 0018:ffff880072453950  EFLAGS: 00010202
[  219.231162] RAX: 0000000000000246 RBX: ffff8800727341c0 RCX: 0000000000000010
[  219.238322] RDX: 0000000000000002 RSI: 0000000000000002 RDI: ffff8800727341c0
[  219.245482] RBP: ffff880072453970 R08: 0000000000000000 R09: 0000000000000000
[  219.252641] R10: 0000000000bc5624 R11: 0000000000000001 R12: ffff880072453990
[  219.259803] R13: 0000000000000002 R14: 0000000000000002 R15: ffff880072734ba0
[  219.266962] FS:  00007fb83f4f3700(0000) GS:ffff88017fd80000(0000) knlGS:0000000000000000
[  219.275077] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  219.280847] CR2: 0000000000000000 CR3: 0000000174ffd000 CR4: 00000000003406f0
[  219.288006] Stack:
[  219.290031]  ffffffff8140c409 ffff8800727341c0 ffff880072734000 ffff8800727341c0
[  219.297556]  ffff8800724539b8 ffffffffa059da68 ffff8800724539e7 0000000000000000
[  219.305082]  0000000100000040 ffff88007245398c ffff001000010040 ffff8800724539d0
[  219.312605] Call Trace:
[  219.315076]  [<ffffffff8140c409>] ? i2c_transfer+0x79/0x90
[  219.320594]  [<ffffffffa059da68>] drm_dp_dual_mode_read+0x58/0x80 [drm_kms_helper]
[  219.328194]  [<ffffffffa059dcb2>] drm_dp_dual_mode_detect+0x32/0x150 [drm_kms_helper]
[  219.336121]  [<ffffffffa0683adc>] lspcon_init+0x6c/0x1a0 [i915]
[  219.342121]  [<ffffffffa066b480>] intel_ddi_init+0x2d0/0x4f0 [i915]
[  219.348474]  [<ffffffffa0649537>] intel_modeset_init+0x15e7/0x1a70 [i915]
[  219.355342]  [<ffffffffa0683507>] ? intel_setup_gmbus+0x2e7/0x310 [i915]
[  219.362118]  [<ffffffffa05beccf>] i915_driver_load+0xa0f/0xe00 [i915]
[  219.368637]  [<ffffffffa05c9797>] i915_pci_probe+0x27/0x40 [i915]
[  219.374761]  [<ffffffff812fc85c>] pci_device_probe+0x8c/0x100
[  219.380537]  [<ffffffff813842d1>] driver_probe_device+0x1f1/0x310
[  219.386654]  [<ffffffff81384472>] __driver_attach+0x82/0x90
[  219.392254]  [<ffffffff813843f0>] ? driver_probe_device+0x310/0x310
[  219.398544]  [<ffffffff81382361>] bus_for_each_dev+0x61/0xa0
[  219.404226]  [<ffffffff81383d69>] driver_attach+0x19/0x20
[  219.409643]  [<ffffffff81383993>] bus_add_driver+0x1b3/0x230
[  219.415324]  [<ffffffffa06fa000>] ? 0xffffffffa06fa000
[  219.420483]  [<ffffffff81384c7b>] driver_register+0x5b/0xe0
[  219.426079]  [<ffffffff812fb337>] __pci_register_driver+0x47/0x50
[  219.432243]  [<ffffffffa06fa03e>] i915_init+0x3e/0x45 [i915]
[  219.437926]  [<ffffffff810003b6>] do_one_initcall+0x86/0x1b0
[  219.443608]  [<ffffffff810dfdd8>] do_init_module+0x56/0x1be
[  219.449204]  [<ffffffff810b61ad>] load_module+0x1ded/0x2070
[  219.454798]  [<ffffffff810b3510>] ? __symbol_put+0x50/0x50
[  219.460307]  [<ffffffff810b65b9>] SYSC_finit_module+0x79/0x80
[  219.466082]  [<ffffffff810b65d9>] SyS_finit_module+0x9/0x10
[  219.471679]  [<ffffffff81567444>] entry_SYSCALL_64_fastpath+0x18/0x8c
[  219.478146] Code:  Bad RIP value.
[  219.481540] RIP  [<          (null)>]           (null)
[  219.486723]  RSP <ffff880072453950>
[  219.490238] CR2: 0000000000000000
[  219.493572] ---[ end trace 21ef5019a03d0eeb ]---
[  219.498323] ------------[ cut here ]------------

I've tried:

  • all official versions of the J3455-ITX BIOS including the newly released 1.80
  • flashing the J3455B-ITX and J3455-M BIOSs to the board using an external flashing device
    • the J3455B-ITX BIOS booted but for whatever reason said it was a J3355B-ITX and wouldn't get past post saying the CPU didn't match the BIOS.
    • the J3455-M BIOS also booted but the model string was incorrect
  • all combinations of BIOS settings
  • installing 6.2 using 3615 bootloader, then upgrading to 6.2.1 and the 918+ bootloader
  • changing the GPU priority to PCIe and sticking in a PCIe video card


All of the above failed :(

 

It looks like the original release of the 918+ boot loader works on this board so maybe something to do with the newer i915 driver @jun put in?

 

Edited by ideasman69
  • Like 1

Share this post


Link to post
Share on other sites
3 hours ago, CrazyCreator said:

Ok ... Thanks for Info and direct Link :)

 

But how can I update to the newest version?

No Problem to create a USB-Loader-Stick with 918+ and migrate my System from 3615xs to 918+

But without a Serialnumber for the 918+ I can't install this :(

 

Not going to work. The hardware on the Gen8 is not compatible with the 918+. (CPU Architecture) We are currently topped out at DS3617xs on DSM 6.2-23739 Update 2.

Share this post


Link to post
Share on other sites
Il y a 5 heures, ideasman69 a dit :

Back to the Asrock boards:

 

J3455B-ITX: works

J3455-M: works

J3455-ITX: i915 driver fails which explains why /dev/dri is missing:


===== trigger device plug event =====
[  219.079271] BUG: unable to handle kernel NULL pointer dereference at           (null)
[  219.087187] IP: [<          (null)>]           (null)
[  219.092288] PGD 1783da067 PUD 1783db067 PMD 0
[  219.096825] Oops: 0010 [#1] PREEMPT SMP
[  219.100846] Modules linked in: i915(E+) drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) cfbfillrect(E) cfbcopyarea(E) cfbimgblt(E) drm(E) fb(E) fbdev intel_agp(E) intel_gtt(E) agpgart(E) video backlight button synoacl_vfs(PO) hfsplus md4 hmac r8168(OE) ixgbe(E) igb(E) i2c_algo_bit e1000e(E) vxlan ip6_udp_tunnel udp_tunnel fuse vfat fat crc32c_intel aesni_intel glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance acpi_cpufreq processor cpufreq_stats dm_snapshot dm_bufio crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram sg etxhci_hcd rtc_cmos(E) mdio(E) mpt3sas(E) raid_class(E) scsi_transport_sas(E) megaraid_sas(E) megaraid(E) mptctl(E) mptspi(E) mptscsih(E) mptbase(E) scsi_transport_spi(E) megaraid_mbox(E) megaraid_mm(E) vmw_pvscsi(E) BusLogic(E) usb_storage xhci_pci xhci_hcd usbcore usb_common imwz(OE) [last unloaded: apollolake_synobios]
[  219.193595] CPU: 3 PID: 6837 Comm: insmod Tainted: P           OE   4.4.59+ #23824
[  219.201196] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./J3455-ITX, BIOS P1.80 05/21/2018
[  219.210792] task: ffff880178b0e240 ti: ffff880072450000 task.ti: ffff880072450000
[  219.218296] RIP: 0010:[<0000000000000000>]  [<          (null)>]           (null)
[  219.225833] RSP: 0018:ffff880072453950  EFLAGS: 00010202
[  219.231162] RAX: 0000000000000246 RBX: ffff8800727341c0 RCX: 0000000000000010
[  219.238322] RDX: 0000000000000002 RSI: 0000000000000002 RDI: ffff8800727341c0
[  219.245482] RBP: ffff880072453970 R08: 0000000000000000 R09: 0000000000000000
[  219.252641] R10: 0000000000bc5624 R11: 0000000000000001 R12: ffff880072453990
[  219.259803] R13: 0000000000000002 R14: 0000000000000002 R15: ffff880072734ba0
[  219.266962] FS:  00007fb83f4f3700(0000) GS:ffff88017fd80000(0000) knlGS:0000000000000000
[  219.275077] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  219.280847] CR2: 0000000000000000 CR3: 0000000174ffd000 CR4: 00000000003406f0
[  219.288006] Stack:
[  219.290031]  ffffffff8140c409 ffff8800727341c0 ffff880072734000 ffff8800727341c0
[  219.297556]  ffff8800724539b8 ffffffffa059da68 ffff8800724539e7 0000000000000000
[  219.305082]  0000000100000040 ffff88007245398c ffff001000010040 ffff8800724539d0
[  219.312605] Call Trace:
[  219.315076]  [<ffffffff8140c409>] ? i2c_transfer+0x79/0x90
[  219.320594]  [<ffffffffa059da68>] drm_dp_dual_mode_read+0x58/0x80 [drm_kms_helper]
[  219.328194]  [<ffffffffa059dcb2>] drm_dp_dual_mode_detect+0x32/0x150 [drm_kms_helper]
[  219.336121]  [<ffffffffa0683adc>] lspcon_init+0x6c/0x1a0 [i915]
[  219.342121]  [<ffffffffa066b480>] intel_ddi_init+0x2d0/0x4f0 [i915]
[  219.348474]  [<ffffffffa0649537>] intel_modeset_init+0x15e7/0x1a70 [i915]
[  219.355342]  [<ffffffffa0683507>] ? intel_setup_gmbus+0x2e7/0x310 [i915]
[  219.362118]  [<ffffffffa05beccf>] i915_driver_load+0xa0f/0xe00 [i915]
[  219.368637]  [<ffffffffa05c9797>] i915_pci_probe+0x27/0x40 [i915]
[  219.374761]  [<ffffffff812fc85c>] pci_device_probe+0x8c/0x100
[  219.380537]  [<ffffffff813842d1>] driver_probe_device+0x1f1/0x310
[  219.386654]  [<ffffffff81384472>] __driver_attach+0x82/0x90
[  219.392254]  [<ffffffff813843f0>] ? driver_probe_device+0x310/0x310
[  219.398544]  [<ffffffff81382361>] bus_for_each_dev+0x61/0xa0
[  219.404226]  [<ffffffff81383d69>] driver_attach+0x19/0x20
[  219.409643]  [<ffffffff81383993>] bus_add_driver+0x1b3/0x230
[  219.415324]  [<ffffffffa06fa000>] ? 0xffffffffa06fa000
[  219.420483]  [<ffffffff81384c7b>] driver_register+0x5b/0xe0
[  219.426079]  [<ffffffff812fb337>] __pci_register_driver+0x47/0x50
[  219.432243]  [<ffffffffa06fa03e>] i915_init+0x3e/0x45 [i915]
[  219.437926]  [<ffffffff810003b6>] do_one_initcall+0x86/0x1b0
[  219.443608]  [<ffffffff810dfdd8>] do_init_module+0x56/0x1be
[  219.449204]  [<ffffffff810b61ad>] load_module+0x1ded/0x2070
[  219.454798]  [<ffffffff810b3510>] ? __symbol_put+0x50/0x50
[  219.460307]  [<ffffffff810b65b9>] SYSC_finit_module+0x79/0x80
[  219.466082]  [<ffffffff810b65d9>] SyS_finit_module+0x9/0x10
[  219.471679]  [<ffffffff81567444>] entry_SYSCALL_64_fastpath+0x18/0x8c
[  219.478146] Code:  Bad RIP value.
[  219.481540] RIP  [<          (null)>]           (null)
[  219.486723]  RSP <ffff880072453950>
[  219.490238] CR2: 0000000000000000
[  219.493572] ---[ end trace 21ef5019a03d0eeb ]---
[  219.498323] ------------[ cut here ]------------

I've tried:

  • all official versions of the J3455-ITX BIOS including the newly released 1.80
  • flashing the J3455B-ITX and J3455-M BIOSs to the board using an external flashing device
    • the J3455B-ITX BIOS booted but for whatever reason said it was a J3355B-ITX and wouldn't get past post saying the CPU didn't match the BIOS.
    • the J3455-M BIOS also booted but the model string was incorrect
  • all combinations of BIOS settings
  • installing 6.2 using 3615 bootloader, then upgrading to 6.2.1 and the 918+ bootloader
  • changing the GPU priority to PCIe and sticking in a PCIe video card


All of the above failed :(

 

It looks like the original release of the 918+ boot loader works on this board so maybe something to do with the newer i915 driver @jun put in?

 

 

Hi,

 

same problem on ASRock J4205-ITX.

Seems the new i915 driver that doesn't work for this motherboard.

/dev/dri is created successfully on my ASRock J4205-ITX if boot from fedora.

So it's not a BIOS problem but a kernel module problem.

 

Share this post


Link to post
Share on other sites
8 hours ago, jadehawk said:

Not going to work. The hardware on the Gen8 is not compatible with the 918+. (CPU Architecture) We are currently topped out at DS3617xs on DSM 6.2-23739 Update 2.

 

I have not the Standard CPU. I have a:

 

Intel Xeon E3-1220L V2 17W GEN8 SR0R6 LGA 1155 2.3GHZ Processor CPU

 

make this a difference or ist not compatible too?

Share this post


Link to post
Share on other sites
11 hours ago, ideasman69 said:

Back to the Asrock boards:

 

J3455B-ITX: works

J3455-M: works

J3455-ITX: i915 driver fails which explains why /dev/dri is missing:


===== trigger device plug event =====
[  219.079271] BUG: unable to handle kernel NULL pointer dereference at           (null)
[  219.087187] IP: [<          (null)>]           (null)
[  219.092288] PGD 1783da067 PUD 1783db067 PMD 0
[  219.096825] Oops: 0010 [#1] PREEMPT SMP
[  219.100846] Modules linked in: i915(E+) drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) cfbfillrect(E) cfbcopyarea(E) cfbimgblt(E) drm(E) fb(E) fbdev intel_agp(E) intel_gtt(E) agpgart(E) video backlight button synoacl_vfs(PO) hfsplus md4 hmac r8168(OE) ixgbe(E) igb(E) i2c_algo_bit e1000e(E) vxlan ip6_udp_tunnel udp_tunnel fuse vfat fat crc32c_intel aesni_intel glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha256_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance acpi_cpufreq processor cpufreq_stats dm_snapshot dm_bufio crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram sg etxhci_hcd rtc_cmos(E) mdio(E) mpt3sas(E) raid_class(E) scsi_transport_sas(E) megaraid_sas(E) megaraid(E) mptctl(E) mptspi(E) mptscsih(E) mptbase(E) scsi_transport_spi(E) megaraid_mbox(E) megaraid_mm(E) vmw_pvscsi(E) BusLogic(E) usb_storage xhci_pci xhci_hcd usbcore usb_common imwz(OE) [last unloaded: apollolake_synobios]
[  219.193595] CPU: 3 PID: 6837 Comm: insmod Tainted: P           OE   4.4.59+ #23824
[  219.201196] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./J3455-ITX, BIOS P1.80 05/21/2018
[  219.210792] task: ffff880178b0e240 ti: ffff880072450000 task.ti: ffff880072450000
[  219.218296] RIP: 0010:[<0000000000000000>]  [<          (null)>]           (null)
[  219.225833] RSP: 0018:ffff880072453950  EFLAGS: 00010202
[  219.231162] RAX: 0000000000000246 RBX: ffff8800727341c0 RCX: 0000000000000010
[  219.238322] RDX: 0000000000000002 RSI: 0000000000000002 RDI: ffff8800727341c0
[  219.245482] RBP: ffff880072453970 R08: 0000000000000000 R09: 0000000000000000
[  219.252641] R10: 0000000000bc5624 R11: 0000000000000001 R12: ffff880072453990
[  219.259803] R13: 0000000000000002 R14: 0000000000000002 R15: ffff880072734ba0
[  219.266962] FS:  00007fb83f4f3700(0000) GS:ffff88017fd80000(0000) knlGS:0000000000000000
[  219.275077] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  219.280847] CR2: 0000000000000000 CR3: 0000000174ffd000 CR4: 00000000003406f0
[  219.288006] Stack:
[  219.290031]  ffffffff8140c409 ffff8800727341c0 ffff880072734000 ffff8800727341c0
[  219.297556]  ffff8800724539b8 ffffffffa059da68 ffff8800724539e7 0000000000000000
[  219.305082]  0000000100000040 ffff88007245398c ffff001000010040 ffff8800724539d0
[  219.312605] Call Trace:
[  219.315076]  [<ffffffff8140c409>] ? i2c_transfer+0x79/0x90
[  219.320594]  [<ffffffffa059da68>] drm_dp_dual_mode_read+0x58/0x80 [drm_kms_helper]
[  219.328194]  [<ffffffffa059dcb2>] drm_dp_dual_mode_detect+0x32/0x150 [drm_kms_helper]
[  219.336121]  [<ffffffffa0683adc>] lspcon_init+0x6c/0x1a0 [i915]
[  219.342121]  [<ffffffffa066b480>] intel_ddi_init+0x2d0/0x4f0 [i915]
[  219.348474]  [<ffffffffa0649537>] intel_modeset_init+0x15e7/0x1a70 [i915]
[  219.355342]  [<ffffffffa0683507>] ? intel_setup_gmbus+0x2e7/0x310 [i915]
[  219.362118]  [<ffffffffa05beccf>] i915_driver_load+0xa0f/0xe00 [i915]
[  219.368637]  [<ffffffffa05c9797>] i915_pci_probe+0x27/0x40 [i915]
[  219.374761]  [<ffffffff812fc85c>] pci_device_probe+0x8c/0x100
[  219.380537]  [<ffffffff813842d1>] driver_probe_device+0x1f1/0x310
[  219.386654]  [<ffffffff81384472>] __driver_attach+0x82/0x90
[  219.392254]  [<ffffffff813843f0>] ? driver_probe_device+0x310/0x310
[  219.398544]  [<ffffffff81382361>] bus_for_each_dev+0x61/0xa0
[  219.404226]  [<ffffffff81383d69>] driver_attach+0x19/0x20
[  219.409643]  [<ffffffff81383993>] bus_add_driver+0x1b3/0x230
[  219.415324]  [<ffffffffa06fa000>] ? 0xffffffffa06fa000
[  219.420483]  [<ffffffff81384c7b>] driver_register+0x5b/0xe0
[  219.426079]  [<ffffffff812fb337>] __pci_register_driver+0x47/0x50
[  219.432243]  [<ffffffffa06fa03e>] i915_init+0x3e/0x45 [i915]
[  219.437926]  [<ffffffff810003b6>] do_one_initcall+0x86/0x1b0
[  219.443608]  [<ffffffff810dfdd8>] do_init_module+0x56/0x1be
[  219.449204]  [<ffffffff810b61ad>] load_module+0x1ded/0x2070
[  219.454798]  [<ffffffff810b3510>] ? __symbol_put+0x50/0x50
[  219.460307]  [<ffffffff810b65b9>] SYSC_finit_module+0x79/0x80
[  219.466082]  [<ffffffff810b65d9>] SyS_finit_module+0x9/0x10
[  219.471679]  [<ffffffff81567444>] entry_SYSCALL_64_fastpath+0x18/0x8c
[  219.478146] Code:  Bad RIP value.
[  219.481540] RIP  [<          (null)>]           (null)
[  219.486723]  RSP <ffff880072453950>
[  219.490238] CR2: 0000000000000000
[  219.493572] ---[ end trace 21ef5019a03d0eeb ]---
[  219.498323] ------------[ cut here ]------------

I've tried:

  • all official versions of the J3455-ITX BIOS including the newly released 1.80
  • flashing the J3455B-ITX and J3455-M BIOSs to the board using an external flashing device
    • the J3455B-ITX BIOS booted but for whatever reason said it was a J3355B-ITX and wouldn't get past post saying the CPU didn't match the BIOS.
    • the J3455-M BIOS also booted but the model string was incorrect
  • all combinations of BIOS settings
  • installing 6.2 using 3615 bootloader, then upgrading to 6.2.1 and the 918+ bootloader
  • changing the GPU priority to PCIe and sticking in a PCIe video card


All of the above failed :(

 

It looks like the original release of the 918+ boot loader works on this board so maybe something to do with the newer i915 driver @jun put in?

 

Thanks for all the work. I still hope that somebody can solve the problem.

Share this post


Link to post
Share on other sites

Can somebody please tell me how to make virtio working with Jun Loader 1.04b?

I compiled virtio modules from Synology sources for ApolloLake (DS 918+): https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/22259branch/apollolake-source/linux-4.4.x.txz/download

 

Placed them in /lib/modules inside rd.gz

Edited /etc/rc inside rd.gz to load virtio_net with dependencies and repackaged rd.gz with cpio and lzma

 

I then ran vm inside Bhyve (FreeBSD 11.2), vm config on the host:

uefi="yes"
cpu=2
memory=1G
network0_type="virtio-net"
network0_device="tap1"
disk0_type="ahci-hd"
disk0_name="synoboot-1.04b-virtio-jun.img"

grub_run_dir="/grub"

network0_mac="58:9c:fc:0b:e8:aa"
uuid="b75f312f-e2d8-11e8-9f90-90e2ba471364"

They do insert correctly on the guest (it seems):

DiskStation> lsmod | grep virtio
virtio_net             20035  0 
virtio_ring             6787  1 virtio_net
virtio                  5273  1 virtio_net

but the eth0 interface does not come up, i get lo only

DiskStation> ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

tap1 host interface seems to have no problem bringing up eth0 on the guest with e1000 driver.

 

Here is the modified loader: https://mega.nz/#!nGYXCQDC!heCIsfbHpFP1FBnKSO2uJtMHDygMLoFqJa7_67Lrrqs

Root password: jun

 

Hope somebody gives me a hand, I would like to make virtio_net working as a priority - looking at virtio_blk for the disk next (already in the updated loader).

 

Share this post


Link to post
Share on other sites
On 11/9/2018 at 8:26 AM, ideasman69 said:

Back to the Asrock boards:

 

J3455B-ITX: works

J3455-M: works

J3455-ITX: i915 driver fails which explains why /dev/dri is missing:

I've tried:

  • all official versions of the J3455-ITX BIOS including the newly released 1.80
  • flashing the J3455B-ITX and J3455-M BIOSs to the board using an external flashing device
    • the J3455B-ITX BIOS booted but for whatever reason said it was a J3355B-ITX and wouldn't get past post saying the CPU didn't match the BIOS.
    • the J3455-M BIOS also booted but the model string was incorrect
  • all combinations of BIOS settings
  • installing 6.2 using 3615 bootloader, then upgrading to 6.2.1 and the 918+ bootloader
  • changing the GPU priority to PCIe and sticking in a PCIe video card


All of the above failed :(

 

It looks like the original release of the 918+ boot loader works on this board so maybe something to do with the newer i915 driver @jun put in?

 

 

Whats the problem with this board? I have same came from 916+ 

Did first a test if bootloader (1.04b) was working with test disk. After it worked upgraded 916+ to latest DSM 6.2.123824 update 1 removed old USB loader and placed 1.04b loader. Migrated from 916+ to 918+. The only thing I found is shutdown which is not working anymore. But do I have to verify something else? It looks hardware transcoding is working perfectly now on the J3455 mobo.

Share this post


Link to post
Share on other sites
25 minutes ago, hannibal1969 said:

It looks hardware transcoding is working perfectly now on the J3455 mobo.

 

which board do you have? Your signature says j3455m-itx but that board doesn't exist. Is it the j3455m or the j3455-ITX?

Share this post


Link to post
Share on other sites
2 hours ago, ideasman69 said:

 

which board do you have? Your signature says j3455m-itx but that board doesn't exist. Is it the j3455m or the j3455-ITX?

I'm Sorry I have J3455-ITX ... also transcoding seems not to work ... im missing /dev/dri too ...

 

Edited by hannibal1969

Share this post


Link to post
Share on other sites
On 10/21/2018 at 10:00 PM, FiberInternetUser said:

After upgrading to jun's lastest 918+ boot loader 1.04b, ASRock J3455-ITX motherboard does not perform a graceful shutdown.  Can't perform a reboot from the DSM GUI as It hangs on shutdown. 

I have same board same problem. Also reboot doesnt work.

Share this post


Link to post
Share on other sites
7 hours ago, hannibal1969 said:

I'm Sorry I have J3455-ITX ... also transcoding seems not to work ... im missing /dev/dri too ...

 

Oh ok. Your other post said transcoding worked perfectly. 

 

I think we just need to accept that this particular model doesn't work. 

Share this post


Link to post
Share on other sites
3 hours ago, ideasman69 said:

Oh ok. Your other post said transcoding worked perfectly. 

 

I think we just need to accept that this particular model doesn't work. 

 

No I was wrong. I forgot how to test it sorry for that. Well your conclusion is a little dissapointing but reasonable to conclude when I see what you have done already. Thanks a lot for all your work!  But what to do next? What would you advise to me?

 

Which board with 4 sata ports is working OOTB? and if you had the same situation I'm facing now, bootloader 1.04b with 918+ active on my nas would it be wise to switch over to the Jun's Loader v1.03b DS3617xs ? I have now a no reboot / shutdown issue.  

Edited by hannibal1969

Share this post


Link to post
Share on other sites

I think it has to do something with the way of the intel GPU driver needs to be loaded by the kernel. If I do a google on i915 with J3455 i found plenty issues but also solutions.

 

http://openbsd-archive.7691.n7.nabble.com/Problems-with-inteldrm-on-ASRock-J3455-ITX-Apollo-Lake-td334941.html

https://www.newegg.com/Product/Product.aspx?Item=N82E16813157729 / review Jason S / 

Once the GPU driver is up and running, that is not the end of it. After a GPU hang which lead to a kernel Oops, I upped the shared memory in the BIOS to the max, 512 MB. Also for grub to try to clear up video issues as much as possible I have set:
1. Commented out GRUB_HIDDEN_TIMEOUT*
2. GRUB_CMDLINE_LINUX_DEFAULT="i915.semaphores=1"

https://forums.unraid.net/topic/62525-solved-igpu-transcoding-i915-driver-present-but-devdri-not-available/

I was able to get this working by adding the the kernel parameter i915.alpha_support=1. You can get this to work as well by editing syslinux.cfg as explained here: https://lime-technology.com/wiki/Boot_Codes

 

Share this post


Link to post
Share on other sites
10 hours ago, hannibal1969 said:

I think it has to do something with the way of the intel GPU driver needs to be loaded by the kernel. If I do a google on i915 with J3455 i found plenty issues but also solutions.

 

http://openbsd-archive.7691.n7.nabble.com/Problems-with-inteldrm-on-ASRock-J3455-ITX-Apollo-Lake-td334941.html

https://www.newegg.com/Product/Product.aspx?Item=N82E16813157729 / review Jason S / 

Once the GPU driver is up and running, that is not the end of it. After a GPU hang which lead to a kernel Oops, I upped the shared memory in the BIOS to the max, 512 MB. Also for grub to try to clear up video issues as much as possible I have set:
1. Commented out GRUB_HIDDEN_TIMEOUT*
2. GRUB_CMDLINE_LINUX_DEFAULT="i915.semaphores=1"

https://forums.unraid.net/topic/62525-solved-igpu-transcoding-i915-driver-present-but-devdri-not-available/

I was able to get this working by adding the the kernel parameter i915.alpha_support=1. You can get this to work as well by editing syslinux.cfg as explained here: https://lime-technology.com/wiki/Boot_Codes

 

tried each of those suggestions tonight.. still no go :(

Share this post


Link to post
Share on other sites
2 hours ago, ideasman69 said:

tried each of those suggestions tonight.. still no go :(

 

Ideasman69, Thanks for All your effort! What should I do? Revert to 3617 bootloader or stay with the 918 and hope for better times?

 

what About j5005? Mobo is About 120 and A 8gb stick About 60 ... I Can reuse the j3455 as an untangle firewall at home.

Share this post


Link to post
Share on other sites
16 hours ago, hannibal1969 said:

I think it has to do something with the way of the intel GPU driver needs to be loaded by the kernel. If I do a google on i915 with J3455 i found plenty issues but also solutions.

 

http://openbsd-archive.7691.n7.nabble.com/Problems-with-inteldrm-on-ASRock-J3455-ITX-Apollo-Lake-td334941.html

https://www.newegg.com/Product/Product.aspx?Item=N82E16813157729 / review Jason S / 

Once the GPU driver is up and running, that is not the end of it. After a GPU hang which lead to a kernel Oops, I upped the shared memory in the BIOS to the max, 512 MB. Also for grub to try to clear up video issues as much as possible I have set:
1. Commented out GRUB_HIDDEN_TIMEOUT*
2. GRUB_CMDLINE_LINUX_DEFAULT="i915.semaphores=1"

https://forums.unraid.net/topic/62525-solved-igpu-transcoding-i915-driver-present-but-devdri-not-available/

I was able to get this working by adding the the kernel parameter i915.alpha_support=1. You can get this to work as well by editing syslinux.cfg as explained here: https://lime-technology.com/wiki/Boot_Codes

 

Did this worked for somebody? I dont know how to add this. 

Edited by Profiler64

Share this post


Link to post
Share on other sites
6 hours ago, hannibal1969 said:

 

Ideasman69, Thanks for All your effort! What should I do? Revert to 3617 bootloader or stay with the 918 and hope for better times?

 

what About j5005? Mobo is About 120 and A 8gb stick About 60 ... I Can reuse the j3455 as an untangle firewall at home.

dunno man. but my j3455B-ITX was running ok but noticed this morning that network reads from it went from ~100MB/s down to 25MB/s so im gonna drop back to the 3517 loader. 

 

i'm not really using the hardware transcoding and the unreliability is too worrying enough to stick with it

Share this post


Link to post
Share on other sites

Yes indeed. IT would be Nice if we could make the xp nas as close as the 918+ but with our compatibility issues I will migrate to 3517 too. Thanks for your help and efforts because you did a lot of work.

Share this post


Link to post
Share on other sites
3 hours ago, ideasman69 said:

dunno man. but my j3455B-ITX was running ok but noticed this morning that network reads from it went from ~100MB/s down to 25MB/s so im gonna drop back to the 3517 loader. 

 

i'm not really using the hardware transcoding and the unreliability is too worrying enough to stick with it

I'm back on 3617 with Jun's Loader v1.03b DS3617xs. Keep in mind that it wont work with the realtec nic. I had to add my old intel NIC again to get it working. The strange thing is that it was found by the migration wizard but due some strange reason after the migration i couldn't find the new 3617 nas so i added intel and it was revealed. ... Strange isn't it?

 

Share this post


Link to post
Share on other sites
10 minutes ago, hannibal1969 said:

I'm back on 3617 with Jun's Loader v1.03b DS3617xs. Keep in mind that it wont work with the realtec nic. I had to add my old intel NIC again to get it working. The strange thing is that it was found by the migration wizard but due some strange reason after the migration i couldn't find the new 3617 nas so i added intel and it was revealed. ... Strange isn't it?

 

yeah if you're still using DSM 6.2.1 on bootloader 1.03b the realtek shouldn't work at all. definitively strange that it appeared at all!

Share this post


Link to post
Share on other sites

Trying to migrate from 6.1 to 6.2. It seemed to go ok but like others after 5 min or so the network craps out. Most have been able to fix this by deleting the 

.xpenoboot folder in the root drive, however when I ssh in I don't see that folder? Is it hidden or something or am I doing something wrong that i can't see it when using putty and logging in as admin?

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.