gnoboot
-
Posts
278 -
Joined
-
Last visited
Posts posted by gnoboot
-
-
.Too bad, WOL support for your NIC is not good -> check here. Buy another NIC to satify your needs.
The guy you refer to had problem with WOL in Windows. It works just fine with DSM on mine. Enabled WOL in BIOS and MAC address is matching with physical hardware. Options changed in the /etc/synoinfo.conf (not /etc.defaults/synoinfo.conf)
I’m told that these do support WOL on Windows, but not if you’re running anything else.My bad, I read it from a wrong context. So it must be a user problem or I need to get the latest driver. I'll try to backport the latest 3.2.55 driver from kernel.org.
-
Well, it's not easy if you haven't tried to compile your own kernel from Linux distribution. Once you know how to do it, then you can try again. Aside from Andy's original patch, you still need to figure out how to detect/enable drives that are not fully supported by DSM. I spent a week or two before having a working kernel, and it was built from scratch including Andy's patch which I ported from 4.1 to 4.3 kernel. I've even have to learn how to use synology toolkit to make my life easier.
Good luck on your endeavor. -
Network card details, send me the `lspci -vvv` result?
Thanks, gnuboot. I am using HP N40L. According to the wiki page: http://n40l.wikia.com/wiki/Base_Hardware_N40L, it should be "Onboard NC107i PCI Express Gigabit 10/100/1000".
Here is the link to lspci result, it is pretty big so I put it on dropbox: https://www.dropbox.com/s/p5iugc2kguflmg5/lspci.txt
For your reference, my NIC MAC address is: a0-b3-cc-ff-fe-df-04-0f.
I can see WOL option in Hardware and Power tab, but I cannot save the changes after I enabled the WOL option on NIC. After saving, the checkbox will always get uncheck.
I also changed the eth0_wol_options and wol_enabled_options to 'g' in "/etc.defaults/synoinfo.conf", but WOL still cannot work.
Too bad, WOL support for your NIC is not good -> check here. Buy another NIC to satify your needs.
Any chance getting Xen kernel modules into gnoBoot?
I would love to use paravir + xe-guest-utilities.As long as you are willing to test it and doesn't break iSCSI. I will enable that feature.
-
Hello,
i habe a Asrock Z87E-ITX Mainboard.
Could you integrate the driver for the Giga PHY Intel® I217V network card in the next version?
Thanks
Michael
it will be included.
Anyone can confirm if the WOL function can work on not on XP gnoboot version? I tried on my N40L but failed to get WOL work.Network card details, send me the `lspci -vvv` result?
-
@gnoboot
I saw your recent blog posting about cpu power management. Great that you have this still in mind.
As I read in serveral forums linux powersaving with modern (haswell) cpu is quite tricky, but I'm not a linux developer
. Also sata link power management seems to be a big thing for good idle power values.Best power management is only achieved in Windows* and when several drivers are installed (Intel Inf, RST, GPU, Audio, Lan, MEI).
*http://www.heise.de/ct/artikel/c-t-Labs-5-Watt-fuer-eine-Selbstverstaendlichkeit-1948002.html
I agree with you, recent Intel CPU (Haswell) is not yet fully supported from older kernels. But recent developments (3.9+) has initial support for it.
For SATA power management, I think it's not a problem as a full support (hibernation) for specific drivers (Marvell) are working excellent. The vendor even has a patent about it.
I'm not also a kernel programmer, just pretending.
Use my kernel at your own risks. Here' s a preview of my recent work.
[spoiler=][ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
[ 4.351649] intel_idle: does not run on family 6 model 37
[ 14.818689] cpuidle: using governor ladder
[ 14.819101] cpuidle: using governor menu
That intel_idle message doesn't appear w/o the backported driver on virtual machines. This feature has support for recent CPUs (Ivy Bridge and Ivy Bridge Xeon). I will try to get Haswell supported as well.
Edit:
Also sata link power management seems to be a big thing for good idle power values.ALPM is now available in several SATA controllers that use the Advanced Host Controller Interface (AHCI). However, there is some anecdotal evidence that some controllers may go into a low power state incorrectly and this ends up causing data loss. Ubuntu has the ability to use ALPM but it it disabled by default since it can cause data loss on some machines. Read more...
-
Here's the patch for /etc/rc.network. It's kinda funny that function will generate a random mac address if you don't set one from vender or grub.
@@ -961,7 +961,7 @@ continue fi - set_mac_address ${ifn} + #set_mac_address ${ifn} -
Nope, but I saw this feature on DSM 5.0 beta dsgpl source (KVM host and guest). The vendor might be releasing this feature soon.
I've got a working 5.0 kernel, but waiting for a patched synobios.
Ask k3dt, he patch my 3827 synobios
I'll just wait for k3dt to release it.
I tried to it myself (just guessing the assembly code ) and its very different from 4.3-3810. The first error w/ or w/o hexing it will generate a kernel stack trace related to initTTYS1. -
Nope, but I saw this feature on DSM 5.0 beta dsgpl source (KVM host and guest).
The vendor might be releasing this feature soon.I've got a working 5.0 kernel, but waiting for a patched synobios.
-
Did you get synogpl-3776-x64.tbz? Have you also tried using /source/linux-3.x/synoconfigs/x86 or /source/linux-3.x/synoconfigs/x86_64 config?
-
Try to use x64 dsgpl source and not bromolow.
-
or patch /etc/rc.network to ignore mac address changes. My boot image has been working w/out the hassle of editing vender files or manually setting the mac address in grub.conf.
-
Any chance of getting synodisk to report hard drive temps correctly in VM? I know this plagues all the XPenology releases, so I don't really expect much. Just not sure why it doesn't work since smartctl can read temps just fine, but synodisk returns -1 (it actually returns -1 for any /dev/sdX you use, even drives that don't exist).
How are you presenting your disk drives? I've passed through my sata controller to xpenology and it reads the temps just fine.
Well I have 2 systems right now; a test system on a DH61AG w/ i3 2120T, and my main is a DQ77KB w/ i7 3770T.
My main system is setup with esxi 5.5, and configured for RDM with onboard intel controller. My test system is setup with esxi 5.5, and RDM with LSI 9201-8i controller. I haven't tried passing through my LSI controller yet, since my test system doesn't support VTd. I plan to eventually move the LSI to my main system as I'm building a new custom enclosure for everything, and will probably test out passing through the LSI controller then.
In any event, smartctl built into DSM can read the temps on the RDM'd drives, also other OS's can read temps fine. It's just synodisk that doesn't like RDM I guess.
Try using physical RDM?
-
I keep getting a 'Fixing recurive fault but reboot is needed!' message when I try to install this onto laptops. Am I doing something wrong?
I don't recommend installing on laptops. Since synoboot is using 3.2.40 kernel your laptop might need a particular firmware/driver which isn't available, refer to this bug report.
-
Hi Everyone - I think my previous post got lost among the noise. I'm running an HP N40L microserver with a Silicon Image sil3132 eSATA PCI card. When I boot to ubuntu, all of my drives on my eSata port multiplier bay show up and are available for use, but when I boot Xpenology (Trantor) v 4.1, 4.2, or 4.3 (even the betas) only 1 out of 4 of my drives in my eSATA port multiplier box show up. Again - Ubuntu shows all drives fine, Xpenology only shows first of four drives, others aren't shown at all.
Any help or suggestions?
Thanks
Instead of booting from Ubuntu, can you try Debian Wheezy which has same kernel base (3.2.54+)?
-
Hello,
Little question, I had synoboot and changed for gnoboot because I wanted to upgrade to 3827.
It works fine... but... Before changing for gnoboot, I had a transfer rate about 90mb/s to 100mb/s.
Now I'm begin to above 120mb/s (same as earlier) but it drop to 40 mb/s... so I was wondering if it is because of the ethernet driver use by gnoboot, or a bug in the lastest version of DSM.
Did anybody had the same problem ?
Thanks a lot !
It's probably ethernet driver which is older compared to Trantor's synoboot. Could you provide the `lspci -vvv` result?
Yes, you are right... it is alpha software... but the download is really challenging
Anyway, this evening I found the time to test Alpha 8...
I used a HP ML110 G7, 12GB with a SD Card (SD Card reader directly on the mainboard) for booting and 2 SATA HDD for data.
GREAT Job ! Well Done.... it was working out of the box until now without any issues... surprising.
Thank you for you work!
After complete check of the disks... still running... I will copy a few TB to see how it is working, tomorrow...
I have the possibilty to compare directly with a DS1513+
Until now.... no difference...just faster.
Maik
Don't forget to send your feedback and support my effort by clicking the ADs at my blog.
I just notice DSM 5.0 toolchain is available for download. The next release might be delayed for a week or so. I'm currently working on getting max cpu to the maximum but iSCSI keeps on failing and sometimes crashing the system.
-
And some additional info on pata_legacy:
https://ata.wiki.kernel.org/index.php/Pata_legacy
ISA and other devices offering an ST416 style ATA interface.
There is specific controller support for:
HT6560A/B VLB
Opti 82C465MV VLB
Opti 82C611A VLB
Promise 20230C
Promise 20630
QDI 6500/6580/6580DP
Winbond W83759A
So I believe there is no any reason to include it even as a module. For example in openSuse 13.1 it is not included in binary kernel build by default.
I have no idea why it is found on my mobo... But it may be a problem with some class of hardware - for example 1155 mobos from asus, or with Z77 chipset, or with onboard wifi, or with something else. So it's better to remove this module in future versions or to build it as a module.
Since pata_legacy is a generic driver, it maybe have been able to detect your raid controller. All distributions no longer include this kernel by default.
-
I used gnoBoot to boot DSM 4.3-3810, and try to load button.ko by adding button to /etc/rc in KERNEL_MODULES, but after reboot, the button.ko seems not load. I checked by lsmod|grep button and return nothing. I checked boot log of /var/log/dmes, and there is some output like below:
[Thu Feb 20 14:30:08 2014] thermal_sys: exports duplicate symbol generate_netlink_event (owned by kernel)
[Thu Feb 20 14:30:08 2014] button: exports duplicate symbol acpi_lid_notifier_register (owned by kernel)
It seems button.ko has duplicate export symbol (acpi_lid_notifier_register, which is exported by kernel) to prevent load button module. When i use Trantor's synoboot img and it works ok, what's problem and difference between gnoboot and Trantor's synoboot ?
By the way, it seems thermal_sys.ko also did not load because of duplicate export symbol.
Duplicate symbol means these two modules are built-in in the kernel. I can build button.ko as module but it isn't loaded automatically by default. Users have to manually loaded module for it to work.
-
Why so complicated?
Again: why so complicated ???
Please just make simple downloadble files without jdownload etc and it will take much less time to get started...Or is this a test?Yes, I think the same thing too...
It's alpha!
Don't expect a fully working boot image in every release. my only issue is rmmod seems to not be working anymore. So I can't prevent kernel mods from loading.Notice it too, but I don't have time to investigate. Thanks for reporting!
-
Why so complicated?
Again: why so complicated ???
Please just make simple downloadble files without jdownload etc and it will take much less time to get started...Or is this a test?Yes, I think the same thing too...
It's alpha!
Don't expect a fully working boot image in every release. my only issue is rmmod seems to not be working anymore. So I can't prevent kernel mods from loading.Notice it too, but I don't have time to investigate. Thanks for reporting!
-
Is alpha 8 released yet? I haven't seen any emails for download link yet.
I'm working on it, please be patient.
-
Is alpha 8 released yet? I haven't seen any emails for download link yet.
I'm working on it, please be patient.
-
Okay, I think I know how to install it now. What about major differences between the two kernels? <- All my kernel modules aren't built-in which makes it easier for me to track bugs, adding new drivers will not require kernel re-compilation (I can release new drivers w/o updating the rd.gz, except those drivers required for booting your machine), and more driver support (IMHO). Visit my blog to know more about my changes.
Can I still use the same PDF guide to set up esxi and RDM with gnoBoot? <- Yes, it should work.
-
Okay, I think I know how to install it now. What about major differences between the two kernels? <- All my kernel modules aren't built-in which makes it easier for me to track bugs, adding new drivers will not require kernel re-compilation (I can release new drivers w/o updating the rd.gz, except those drivers required for booting your machine), and more driver support (IMHO). Visit my blog to know more about my changes.
Can I still use the same PDF guide to set up esxi and RDM with gnoBoot? <- Yes, it should work.
-
Sweet, thanks !
Will it be possible to do "clean" update in the future? I can make 5 beta update with telnet command but it doesn't work with 4.3 (3810 -> 3827)
No, update feature is DSM's job which isn't opensource. You can update to 3827 using gnoboot-me grub option, but have a backup before doing it.
XPEnology gnoBoot
in DSM 5.2 and earlier (Legacy)
Posted
According to this link, megaraid_sas is the right driver for Perc H310. Can you send me the `lspci -nn` and `dmesg` output?