Polanskiman
-
Posts
2,735 -
Joined
-
Last visited
-
Days Won
120
Everything posted by Polanskiman
-
Oui normal. Jun a changé la structure et le contenu des partitions. L'image et les modules se trouvent dans la seconde partition maintenant. -
Read the OP.
-
[Tuto] Installer/Migrer DSM 5.2 à 6.0.2 (Loader Jun)
Polanskiman replied to Polanskiman's topic in Archives
Et donc vous avez refait la clef usb comme indiqué plus haut? Si vous lisez la discussion un peu en arrière vous verrez que plusieurs personnes ont eu des problèmes avec l'update 8. Normalement il leur a suffit de faire un reboot forcé ou alors de refaire la clef usb. -
[Tuto] Installer/Migrer DSM 5.2 à 6.0.2 (Loader Jun)
Polanskiman replied to Polanskiman's topic in Archives
Il s'agit d'un vieux XW6400 de chez HP le bios date de 2007 donc boot en Legacy surement, dans tous les cas je ne peux pas switcher entre UEFI ou Legacy. Et toutes les sécurités de modification d'OS son désactivées (prévntion d'exécution de données et technologie de virtualisation intel sur off) Vous ne pouvez pas switcher entre UEFI ou Legacy étant donné que pas de UEFI mais vous pouvez choisir à partir de quel disque booter en principe. Si pas de choix entre 2 disques, regardez aussi si le mode AHCI est activé car le loader ne bootera pas en mode IDE. -
Knee jerk reaction to Syno quickconnect kill
Polanskiman replied to Salah's topic in Packages & DSM Features
It seems to me that you are not understanding the rather primary concept of netiquette. You are not to attack or blame anyone, trolling is also not tolerated. This is the last time I am saying it you. Failure to comply will lead you to be banned. -
3615xs generated serial registration problem
Polanskiman replied to brantje's topic in Packages & DSM Features
QuickConnect use is an abuse of Synology's services. This topic was already closed once and the user recreated it. I am closing this one too. -
Es normal. El modelo del CPU esta codificado de forma fija. Nadie lo puede cambiar cual sea el CPU que tengas. Pero no te preocupes, DSM utiliza todos los recursos de tu CPU instalado.
-
Not defending or blaming anyone. If the devs wanted the source code published they would already have done it. I'm sure they are smart enough to think about that. As mush as I understand the people's wish to see the source code, exposing the source publicly would only serve the community negatively. This project does step on some boundaries and I don't think that it is a good idea to show what is done under the hood. The help that the devs needs in my opinion is the compilation of drivers for a broader compatibility. Right, and it's' my "summer project" but i need to understand because i would like to build my own bootloader with my set of drivers. It was not my intention to blame Jun, i say thanks to him for his works and thanks for scripts Everything you need to make your own bootloader with your drivers is already available. Jun published the scripts. Drivers can be downloaded from the respective publishers and can be compiled against DSM 6.1 source code which is also publicly available, so in fact everything you need is already there although I have to admit I have not tried running those scripts myself yet.
-
[Tuto] Installer/Migrer DSM 5.2 à 6.0.2 (Loader Jun)
Polanskiman replied to Polanskiman's topic in Archives
Vous êtes en 6.0.2 update 9 c'est cela? Essayez par refaire la clef usb voir si cela arrange quelque chose. -
[Tuto] Installer/Migrer DSM 5.2 à 6.0.2 (Loader Jun)
Polanskiman replied to Polanskiman's topic in Archives
Il faudrait pour commencer fournir plus d'information sur votre matériel. Model, année par example. Donc en ayant aussi peu d'info tout ce que me vient à l'esprit c'est que votre Bios n'est pas correctement configuré. Le loader v1.01 est un loader hybride et peut booter soit en uefi soit en legacy. Il faut voir dans votre bios pour faire booter la clef usb en mode legacy (bios). -
6.1. works on AMD, see my signature. That is interesting. Below a quote from Jun himself about AMD support: Yes, AMD loader need some extra work. Did you do a migration or a clean install with v1.02a ?
-
Not defending or blaming anyone. If the devs wanted the source code published they would already have done it. I'm sure they are smart enough to think about that. As mush as I understand the people's wish to see the source code, exposing the source publicly would only serve the community negatively. This project does step on some boundaries and I don't think that it is a good idea to show what is done under the hood. The help that the devs needs in my opinion is the compilation of drivers for a broader compatibility.
-
For the sake of accuracy, Synology is not based in China. It's based in Taiwan.
-
3615xs generated serial registration problem
Polanskiman replied to fatsausage's topic in Packages & DSM Features
What you have contributed to by using QuickConnect is making sure that Synology is blocking generated serials and looking closely at what is happening in this project. Let me repeat what I have already said countless times in the forum. DO NOT use QuickConnect as you are abusing Synology's services. It's basically piracy. QuickConnect is aimed at Synology's customers. If you need to access your Xpenology box from outside your local network simply setup a custom DDNS. The feature is available within DSM. It will do exactly the same as what QuickConnect does without using the servers and resources of Synology. Topic locked. -
The point was to see what difference makes it not boot. So 5.2 works, meaning that kernel config is working. Did the 1.00/1.01 loaders work? None worked. 1.00, 1.01, 1.02a and 1.02a-test
-
No it's not.
-
Yes by loader I meant the kernel since it hangs while the kernel is loading. No ramoops. Only thing I can see is the usb/serial connector LED that stays on continuously instead of blinking when there is data passing in an out. It definitely hangs there. That's a though nut to crack, especially without logs, or access to files. Can you boot 5.2 on it, and see if it works? I could although not sure what the purpose would be. The testing was aimed at v1.02a. Let me try anyway see how that goes. EDIT: Tried with Xpenoboot 5.2 and everything loads properly. I didn't try installing DSM as I don't see the point but it seems to work fine with Xpenoboot 5.2.
-
Yes by loader I meant the kernel since it hangs while the kernel is loading. No ramoops. Only thing I can see is the usb/serial connector LED that stays on continuously instead of blinking when there is data passing in an out. It definitely hangs there.
-
I had a similar bug with my mobo (MSI B250I PRO), but it wasn't about booting. It booted, but network was not accessible. I had already tried a BIOS reset and that didn't change anything. I removed the ODD but still see those two lines and then nothing. I'm guessing the loader is not liking some of the hardware in that machine.
-
Not sure what lead you to create such topic and make such comment. The community is actually active and live. There are currently 2 loaders available. One for 6.0.2 and one for 6.1 currently in testing. What is dead about that? In the future please search the forum prior posting.
-
Since you seem to be more than aware of what Synology, devs, mods and users (basically everyone here) do or know, maybe you could provide your knowledge instead of making obnoxious comments or PMs. Also, please avoid filling topics with single lines posts one after the other and try creating topic titles that describe your question or issue accurately. If your intention is to contribute to the forum I recommend you do so in a manner that does not involve insulting or looking down on people by questioning their ability specially when the great majority of people have been here far longer than you. You might be a system administrator, yet it does not give you any superiority over others. Show your knowledge in a respectful way.
-
I think it's a great idea!
-
[Tuto] Installer/Migrer DSM 5.2 à 6.0.2 (Loader Jun)
Polanskiman replied to Polanskiman's topic in Archives
Vous vouliez surement dire DSM 6.0.2-8451 et non 6.0.2-8541. Les mises à jour sont ici: https://usdl.synology.com/download/DSM/criticalupdate/update_pack/ -
VID/PID not fully required but strongly advisable. The purpose is not for the boot drive not to be seen in DSM. That was true with Xpenoboot though. MAC/SN = Use you NIC's MAC address and for the SN you can simply leave the one on the grub file.
-
Doesn't the ATA port numbering in software begin at 1, while it begins at 0 on the board? Though it is possible that the controller provides 4 ports, and a separate controller is used for eSATA. I doubt that those messages are related to the reason why it won't boot further. Can you provide full logs from start? The ata denomination is really not the issue here. As I have already said, there is nothing else in the consol output, else I would have provided it. Those are the only two lines that appear once the kernel start decompressing. Nothing else shows. I've left it for 10 min see if anything else would show, but nothing there.