Jump to content
XPEnology Community

holybabel

Member
  • Posts

    171
  • Joined

  • Last visited

Posts posted by holybabel

  1. - Outcome of the update: SUCCESSFUL

    - DSM version prior update: DSM 6.1.7-15284 Update 2

    - Loader version and model: JUN'S LOADER v1.03b - DS3615xs

    - Using custom extra.lzma: NO

    - Installation type: BAREMETAL - Intel SS4200 

    - Additional comments: Updated my USB-Stick and then migrated my system. Worked without any problems.

  2. Hallo Tiggr,

     

    das Problem mit dem BadChecksum hatte ich mit dem alten Loader immer wenn ich den Rechner mit dem "Advanced Power Manager" gestartet bzw. heruntergefahren habe. Da gab es im Englischen Bereich auch einen ziemlich langen Thread zu. Das Problem habe ich mit dem aktuellen Loader von Jun nicht mehr. Meine Empfehlung ist daher auf den neuen Loader und DSM 6.1 upzudaten.

     

    Bist du nach der Anleitung von Polanskiman vorgegangen? Die Anleitung ist zwar für den 6.02 Loader, du kannst sie aber auch für den aktuellen Loader nutzen:

     

     

  3. Ok, with original extra.lzma it works. DSM 6.1.3-15152 is being installed right now.

     

    EDIT: Had to make a hardreset, but now everything works. DSM 6.1.3-15152 U1

     

    Thanks at all :-)

  4. Hi everyone,

     

    i wanted to update my baremetal diskstation from DSM 6.0.2-8451 Update 11 to latest version using 1.02b loader from jun.

    I followed polanskiman's tutorial and changed the extra.lzma ramdisk with the one polanskiman provided in his tutorial. But now when i boot with the flashdrive it reboots everytime. I hook up a monitor and i can see that it shows the "normal" screen with the "happy hacking...go to find.synology.com...extracting kernel" and so on and then it reboots.

     

    Can someone point me to the right direction?

  5. This is a know problem with many drivers.

     

    ############## Know Issues #####################

    - When running on a slow single core machine, there is a race condition that causes the patcher to load too late. The most obvious sign is that console is not working properly.

    - Some ethernet drivers crash when set MTU above about 4096 (Jumbo frame).

  6. Naja, JBOD heißt ja null Redundanz. Wenn da eine Platte kaputt ist, dann sind auch alle Daten dadrauf weg. Dann kannst du die Platte einfach rausnehmen und gegen eine neue tauschen.

     

    Bist du dir sicher das du nur ein JBOD hast?

     

    Gruß holybabel

  7. Hi everyone,

     

    i already asked this in the "old" XPEnoboot thread but nobody answered. Is it possible to use a usb bluetooth stick that is not listed in the official compatibility list?

     

    I attached a Belkin usb bt stick and it seems to be recognized by the system:

     

        [  566.689037] usb 3-1: new full-speed USB device number 2 using uhci_hcd
       [  566.871019] Got empty serial number. Generate serial number from product.
       [  567.047955] Bluetooth: Core ver 2.16
       [  567.047992] NET: Registered protocol family 31
       [  567.047994] Bluetooth: HCI device and connection manager initialized
       [  567.048023] Bluetooth: HCI socket layer initialized
       [  567.048026] Bluetooth: L2CAP socket layer initialized
       [  567.048035] Bluetooth: SCO socket layer initialized
       [  567.054833] Bluetooth: RFCOMM TTY layer initialized
       [  567.054864] Bluetooth: RFCOMM socket layer initialized
       [  567.054866] Bluetooth: RFCOMM ver 1.11
       [  567.057591] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
       [  567.057617] Bluetooth: HIDP socket layer initialized
       [  567.064134] usbcore: registered new interface driver btusb

     

    lsusb | grep Blue
    Bus 003 Device 002: ID 050d:0013  Broadcom Corp Belkin Bluetooth Device

     

    But the stick doesn't show up in control panel. hcitool says that the device is down and when i want to start it it shows:

     

    can't init device hci0 operation not supported (95) synology

     

    Is there any chance to get the stick up and working?

  8. Hi Trantor,

     

    i tried to connect my Belkin F8T013 Bluetooth Stick to xpenology.

     

    It seems that the stick is recognized by xpenology:

     

    [  566.689037] usb 3-1: new full-speed USB device number 2 using uhci_hcd
    [  566.871019] Got empty serial number. Generate serial number from product.
    [  567.047955] Bluetooth: Core ver 2.16
    [  567.047992] NET: Registered protocol family 31
    [  567.047994] Bluetooth: HCI device and connection manager initialized
    [  567.048023] Bluetooth: HCI socket layer initialized
    [  567.048026] Bluetooth: L2CAP socket layer initialized
    [  567.048035] Bluetooth: SCO socket layer initialized
    [  567.054833] Bluetooth: RFCOMM TTY layer initialized
    [  567.054864] Bluetooth: RFCOMM socket layer initialized
    [  567.054866] Bluetooth: RFCOMM ver 1.11
    [  567.057591] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
    [  567.057617] Bluetooth: HIDP socket layer initialized
    [  567.064134] usbcore: registered new interface driver btusb
    

     

    lsusb also shows it the device:

     

    DiskStation> lsusb | grep Blue
    Bus 003 Device 002: ID 050d:0013  Broadcom Corp Belkin Bluetooth Device
    

     

    But in control panel it doesn't show up. Is there a possibility to use this stick under xpenology or do i have to buy one from compatibility list?

     

    Greetings holybabel

×
×
  • Create New...