cooledspirit

Hi, I can't properly access my files after I upgraded to nanoboot 5.0.2.4. When I try to create a folder, the error is: There is a problem accessing Z:\ Make sure you are connected to the network and try again. When I try to copy files to the NAS (writing), it freezes up, crashes, (keyboard clicks don't work anymore). Copying files from the NAS (reading) is most of the time a problem too, but the system does not appear to crash. The error there is "an error occured while reconnecting Z: to \\xxx.yyy.zzz\folder . Mirosoft Windows Network: the local device name is already in use. This connection has not been restored". Browsing through folders and files does not seem to be a problem on client side. I'm not sure what is causing it... I have 3 network cards: - onboard Realtek RTL8111E (uses RTL8168 driver) - RTL8169 PCI card - INTEL PCI1000 I have the same problems using each card individually (the other cards not connected at that time). Can anybody help please ?

I just noticed that my HDD do not spindown after the specified time of inactivity, anybody has the same problem ? Or even better ... a solution ? Using GnoBoot 10.4, DSM 5.0 (4458) and IPKG installed (as well as Asterisk 1.8, though currently not running). Many thanks for potential insights !

I installed the regular DSM 5.0 4458. I did upgrade from 4.3 to 5.0 beta (Trantor release) first though. I afterwards switched to GNOboot and besides that one particularity it appears to be working nicely.

Kudos to gnoBoot and Trantor for the excellent work they did !!! I installed gnoBoot alpha 10.4 with DSM 5, and managed to get it work. Thanks to the additional drivers I have a RTL8169 card working, a bluetooth dongle as well as a Huawei 3G dongle for Asterisk. There was one thing weird though, during installation, after reboot, I got a few times that Synology Assistant had a time out and was not able to end the final step in which the configuration files were written. When I logged in on xpenology itself (using gnoBoot's login screen of the NAS itself) and then logged out, for some weird reason, the system was capable of finishing successfully the writing of the configuration files. I don't know why or if I did something wrong, but I'm happy I got it working .

Hi, I installed two standard Synology Python packages ("Python" and "Python 3"). Yet, when I try to install some packages (like Debian Chroot), a very specific Python version appears to be mandatory (I believe it was something like 2.7.30). Aren't Python packages not backwards compatible (e.g. you install a higher version of a Python package that covers the requirements of lower versions) ? What can I do to fix this ? How to retrieve a specific Python version ? Kind regards, David.

Nobody knows or a very dumb question ?

Hello, In order to prepare my system for WOL, I changed the MAC address according the guide (using hexedit) and added the S99ZZZ script to the proper folder. Sorry for the noob question, but I can't seem to find how to put the system into hibernation... what procedure needs to be followed to put the system in hibernation state (S4) ? I assume S3 state is not supported ? My system: ASRock B75 Pro 3-M, 16 Gb RAM Many thanks in advance ! Cooledspirit.