Knarf

Members
  • Content Count

    16
  • Joined

  • Last visited

  • Days Won

    1

Knarf last won the day on October 10

Knarf had the most liked content!

Community Reputation

1 Neutral

About Knarf

  • Rank
    Newbie
  1. Thanks for the encouragement but I just tried again, not found on network. Checked the C1E controller and it is Enabled again, so is there a different Boot Loader I can use that will not keep enabling this or perhaps will a different bios solve the problem? I'm truly stumped. (Stuipid?)
  2. Yes, I checked C1E and it had somehow reverted but I changed it and checked it on next boot. When I ping I receive timed out response. Thanks for the NIC info. If I get a better attitude I will flash the BIOS this weekend and see what happens. Thanks again for all your help. I could have bought a Synology for all the time I've put into this but I'm like a dog with a bone on these projects, I just want to win! OK, so I just checked again and the setting for C1E is Enabled again!!! I wonder why it keeps re-enabling itself?
  3. I know these NIC's are different than for a typical PC (smaller?). Do you know offhand what I should be looking for? No I'm not familiar with hooking up with a serial cable for access, I do have a monitor connected.
  4. I guess this is not going to work for me. I've tried all these things including the unmodified loader and then just changing the ramdisk and no results. One last question, should the original extra.lzma file be deleted and replaced with the extra.lmza or should they both be in the folder? I deleted and replaced in my case. Thanks
  5. Bearcat, Sorry if I've confused you, I rebooted back to 5.2-5644. Since it's never been found on the network I've never loaded the new .pat file. I guess I'll give a new bios a try and see if it will go then. I use a fixed ip address from the router, DSM set to DHCP. I use the "real" MAC in the grub file and a serial number from the generator. Does any of that indicate a problem? Thanks again, Frank
  6. Unfortunately Synology Assistant still can't find NAS on network and ping receives no reply. COmpletely different question, I've never set a virtual machine but can you tell me if this theory is correct? 1: Boot into virtual machine 2: try to update from update window in DSM-this would only be to 5.2-5967 3: If this works in a virtual machine then try it on the bare metal version thru DSM
  7. IG-88, Thank you for the reply. I have a couple of questions about the ramdisk, first of all I see 4 versions listed on the page referenced from the link and I do not know how to determine the proper version for my use. I'm guessing " extra.lzma for ds3615 v4.8 ". Secondly, where do you put this? I assume this is something that needs to be modified in Jun's loader but I do not know what to do. Thanks again, Frank
  8. Well I've created a fresh usb with the modded bootloader and I make it to the Happy hacking screen as shown in the tutorial but my machine still does not show up on the network. My BIOS ID is :041, The version is :07/29/2011. Do you think I have a BIOS issue or do I need a different NIC? This is the result I get from SSH ZenStation> lspci|grep 0200 02:00.0 Class 0200: Device 14e4:165b (rev 10) ZenStation> ethtool -i eth0 driver: tg3 version: 3.137h firmware-version: 5723-v3.35 bus-info: 0000:02:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no ZenStation> lspci -k 00:00.0 Class 0600: Device 1022:9601 Subsystem: Device 103c:1609 00:01.0 Class 0604: Device 103c:9602 00:06.0 Class 0604: Device 1022:9606 Kernel driver in use: pcieport 00:11.0 Class 0106: Device 1002:4391 (rev 40) Subsystem: Device 103c:1609 Kernel driver in use: ahci 00:12.0 Class 0c03: Device 1002:4397 Subsystem: Device 103c:1609 Kernel driver in use: ohci_hcd 00:12.2 Class 0c03: Device 1002:4396 Subsystem: Device 103c:1609 Kernel driver in use: ehci-pci 00:13.0 Class 0c03: Device 1002:4397 Subsystem: Device 103c:1609 Kernel driver in use: ohci_hcd 00:13.2 Class 0c03: Device 1002:4396 Subsystem: Device 103c:1609 Kernel driver in use: ehci-pci 00:14.0 Class 0c05: Device 1002:4385 (rev 42) 00:14.1 Class 0101: Device 1002:439c (rev 40) Subsystem: Device 103c:1609 00:14.3 Class 0601: Device 1002:439d (rev 40) Subsystem: Device 103c:1609 00:14.4 Class 0604: Device 1002:4384 (rev 40) 00:16.0 Class 0c03: Device 1002:4397 Subsystem: Device 103c:1609 Kernel driver in use: ohci_hcd 00:16.2 Class 0c03: Device 1002:4396 Subsystem: Device 103c:1609 Kernel driver in use: ehci-pci 00:18.0 Class 0600: Device 1022:1200 00:18.1 Class 0600: Device 1022:1201 00:18.2 Class 0600: Device 1022:1202 00:18.3 Class 0600: Device 1022:1203 00:18.4 Class 0600: Device 1022:1204 01:05.0 Class 0300: Device 1002:9712 Subsystem: Device 103c:1609 02:00.0 Class 0200: Device 14e4:165b (rev 10) Subsystem: Device 103c:705d Kernel driver in use: tg3 I unfortunately have no idea what any of this means. I'm a slightly accomplished home networker but this is way above my head. I can type in the commands and follow directions (sometimes) but when something goes wrong I'm lost. Once again thanks for the help.
  9. Bearcat, Thanks for the link to the screenshot of the HP Bios screen. I double checked and found the option to disable C1E. It was way down at the bottom of the page and in my late night fog I didn't scroll down far enough. So after disableing C1E I tried to boot from the usb I made from Polanskiman's tutorial and still not showing up in the network. Later today or tonight when I have time I will make a new usb stick from your link and try again. Thanks for your patience and help. Frank
  10. Thank you for the reply. before I did the update I looked in my bios and I do not show any settings for ce1. Does this mean I need a newer bios for my hpn40l before I proceed again? Thanks again.
  11. I'm currently running 5.2-5644.3 and I'd like to update to at least 5.2-5967 which my machine is offering me on the update page. There was a time that with certain installations that worked, but mostly I remember always reading not to update from within the machine offerings. So I followed Polanskiman's tutorial on migrating from 5.2 to 6.1.X (Jun's Loader). I get the same screen shown in the tutorial once I boot but Synology assistant never finds NAS. Will replacing the NIC solve this problem? I've seen a reference to that but I think it's for a later version. One way or another I'd appreciate any direction on either getting 6.1 to work or what bootloader and Pat file I'll need for 5.2-5967. I've searched and worked on this all week and just can't find the answers I'm looking for so I hope someone here has some info. Thanks Frank
  12. That worked just great for the hibernation issue. Thanks for the tip.
  13. I too did the auto update and now am not able to hibernate. I will not make this mistake again. Is there a way to rollback to the prior version? I tried installing a fresh image but when I used the PAT file it asked for a newer version.