• Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About jollmo

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Because of the Rj45 / SFP+ mismatch, in-between I tried a Asus XG-100F, which I couldn't make recognised under OSX at all. My second try was a Sonnet Solo 10G SFP+, which worked oob, but was very unreliable in connection and had read rates of max 30 MB/s. That was with a 10m Rapidcon Twinax SFP+ cable...
  2. Hi, I added an Asus XG-C100C to my Hackintosh, which worked OOB and a IBM Emulex 49Y7952 2x10GbE card to my converted px12-450 running DSM 6.2.3-25426 Update 3. As the Emulex is FTP+ and the Asus is RJ45 I've put a 6COMGIGA 10GBase-T SFP+ RJ45 copper transceiver Module in the Emulex, turned on jumbo frames and now I've got transfer rates from around 915 MB/s write and 990 MB/s read.
  3. Thats exactly the partition scheme I have on my original NAND with the Lenovo-system on it...
  4. my newly prepared one showed: /dev/disk5 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *16.0 GB disk5 1: EFI NO NAME 15.7 MB disk5s1 2: Linux Filesystem 31.5 MB disk5s2 3: Bios Boot Partition 4.2 MB disk5s3 when attached to my mac using the "diskutil list" command in terminal... And thats the NAND I'm bootin
  5. Thats strange, I've got no idea where to find the chip... Did you try already with swapped PID/VID?
  6. Could you perform lsusb -ciu and post it here?
  7. The USB device can as well be: Product: USB Flash Disk Vendor ID: 0x1307 (Transcend Information, Inc.) Product ID: 0x0165 (2GB/4GB/8GB Flash Drive)... Do you have an idea, where its located? In my machine, it's located here: (this is actually a picture of your board, the px4-300r) here is another foto: the red marked area is the internal USB port. The white pin is there to arrest the USB NAND in its place. The pin layout looks like this: (looking at the back of the NAND) (You can see the hole, whe
  8. @ GodZone: What are the VID/PID of your internal/onboard USB?
  9. At least in my case I had to swap VID and PID to achieve a boot. If you put in your numbers in google, for example 0x1643 0x0951, which is what I find on my Mac, asking System Preferences for my stick, it shows me: Silicon Motion Inc. Taiwan. 4/8/16GB. 0x090C. 0x1000. Kingston Technology Company. 16GB. 0x0951. 0x1665. Kingston Data Traveller. 4GB. 0x0951. 0x1643. And that is exactly my stick I used for the first try booting up my px12... So 0x0951 is the VID (Vendor ID), because it stands for Kingston Technology Company Whereas 0x1643 is the PID (Product ID) But to mak
  10. OMG! I had a closer look at my original bootstick and found out, that I swapped vid and pid numbers accidentally... That was the working one... On the other media I tried, I always put the VID in the vid column and the PID in the pid column as shown in polanskiman's tutorial... As I tried numerous times, I accidently again swapped numbers as well on the compact flash card and suddenly it worked... So now I also swapped VID and PID on the NAND and guess what: I have a clean machine No more stick in the back It boots from the internal Apa
  11. On the partition with the extra.lzma is a file grub_cksum.syno May it be that this prevents altering grub.cfg after the install, because the checksum will be checked? EDIT: No, it's not the case. I was able to clone my stick via dd to a compact flash card in a card reader, changed vid/pid int the grub.cfg and succeeded to boot from that via the USB port at the back of the server. So the NAND problem must be something completely different. On the Mac as well under Windows it behaves exactly like the old NAND, but maybe they changed something I'm not aware of
  12. Ok, but what about my other thoughts? Does the install-process writes anything back on the install media (USB stick) what prevents it from being cloned without altering something on the new media? Has anyone here been successful in cloning his stick and booting from the clone?
  13. So the VID/PID is only for the first install, right? Does the install writes any information back on the stick? So that for every reboot it has to be THE stick you initially installed with? That would could be the reason, why I can't reboot from the NAND. I think so, because I just cloned my stick to another one with dd and have the same problem. Only the original stick is able to boot. So maybe after dd we have to alter some other things on other places?
  14. My Apacer USB NAND arrived today, and this is what I did: I cloned my stick to the NAND using dd (did it on my Mac) dikutil list output after dd: /dev/disk4 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 GB disk4 1: EFI NO NAME 15.7 MB disk4s1 2: Linux Filesystem 31.5 MB disk4s2 3: Bios Boot Partition 4.2 M