Jump to content

sgei

Members
  • Posts

    38
  • Joined

  • Last visited

Posts posted by sgei

  1. Hi,

     

    yesterday I moved my root partition to a 128GB SSD by running "nand-sata-install"

    Everything works fine.

    Now I got a SD-Card in my Banana Pi with one big partition:

     

    fdisk -l

    Disk /dev/sda: 128.0 GB, 128035676160 bytes
    30 heads, 63 sectors/track, 132312 cylinders, total 250069680 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x93d6d043
    
       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1            2048   250069679   125033816   83  Linux
    
    Disk /dev/mmcblk0: 3965 MB, 3965190144 bytes
    46 heads, 9 sectors/track, 18706 cylinders, total 7744512 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00043861
    
            Device Boot      Start         End      Blocks   Id  System
    /dev/mmcblk0p1            2048     7744511     3871232   83  Linux

    df

    Dateisystem    1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf
    rootfs         123071852 1523900 115296264    2% /
    /dev/root      123071852 1523900 115296264    2% /
    devtmpfs          504172       0    504172    0% /dev
    tmpfs             131072     232    130840    1% /run
    tmpfs               5120       0      5120    0% /run/lock
    tmpfs             131072       0    131072    0% /run/shm
    /dev/mmcblk0p1   3810928 1307224   2343624   36% /media/mmc
    /dev/mmcblk0p1   3810928 1307224   2343624   36% /boot
    tmpfs            1048576     128   1048448    1% /tmp
    /dev/root      123071852 1523900 115296264    2% /var/log.hdd
    ramlog-tmpfs      262144   11492    250652    5% /var/log
    

    What do I have to do to prepare a new SD-Card (256MB) and move the Boot-Partition to it?

     

    In /media/mmc is my old /root, isn't it?

     

    Thanks.

     

    Steffen

  2. Hi Igor,

     

    (try bin from normal Banana. Anyway it should work)

     

    script.bin for BananaPi (bananapilcd7.bin) works, even with BananaPro,

     

    but if I use the BIN-file for BananaPro (bananapiprolcd7.bin) I only get a black LCD with backlight on.

    I have tryed the BIN-file from Lemaker. Same problem.

     

    Like I said with Bananian or Raspian there is no problem with BananaPro and Lemaker LCD...

    Any idea?

     

    Now I will try an older version of your image...

     

    Thanks.

     

    Steffen

  3. Hi,

     

    I've tryed to get the 7" Lemaker LCD running with your image v3.2 Kernel 3.4.108 (Wheezy).

     

    What I did is:

    rm -f /boot/script.bin
    ln -s /boot/bin/bananapiprolcd7.bin /boot/script.bin

    After reboot the LCD-Backlight goes on, but there is no output.

     

    I've checked 2 LCDs and 2 BananaPro.

     

    It works with Bananian and Raspian. Can you check it?

     

    Steffen

  4. Hi Igor!

     

    I'm running your Image on BananaPi and BananaPro and I want to use the 7" Lemaker LCD...

     

    Image-Version: 3.2 Kernel 3.4.108 Wheezy

     

    How do I switch the script.bin-file?

     

    Do I have to change the symbolic link like:

    ln -s /boot/bin/bananapipro.bin /boot/script.bin

    In /boot/bin are all script.bin files, but the filesize of the BananaPro BIN-files are identical:

     

    50516 bananapi.bin

    50580 bananapilcd7.bin

    50612 bananapipro.bin

    50612 bananapiprolcd7.bin

     

    The original BIN-files from Lemaker have a different size too:

     

    50972 banana_pi_7lcd.bin

    50564 banana_pro_7lcd.bin

     

    Did you make any changes in the BIN-files?

     

    Can I use the BIN-Files from Lemaker?

     

    Thanks.

     

    Steffen

  5. Hi Igor,

     

    With these two lines in LSB-Tags of ramlog I don't get any Errors:

     

    # X-Stop-After: $syslog
    # X-Interactive: true

     

    Source: https://debianforum.de/forum/viewtopic.php?f=27&t=131540

    ### BEGIN INIT INFO
    # Provides: ramlog
    # Required-Start:
    # Should-Start: $local_fs
    # Required-Stop:
    # Default-Start: 2 3 4 5
    # Default-Stop: 0 1 6
    # Short-Description: moves /var/log into ramdisk
    # Description: ramlog daemon moves /var/log to ramdisk on startup and copies it back to harddrive on shutdown or restart
    #
    # X-Stop-After: $syslog
    # X-Interactive: true
    ### END INIT INFO

    Steffen

  6. Hi Igor,

     

    I've installed a clean version of your image for BananaPi:

     

    Hardware: BananaPi

    Image-Version: 3.2 Kernel 3.4.108 Debian Wheezy

     

    Installed Packages:

     

    zip, unzip

    ftp

    dialog

    xorg

    lxde

    slim

    tightvncserver

     

    I get the following ErrorMessage:

     

    Boot

     

    Jul 12 06:03:11 Enabling ramlog...                                       [ OK ]
    Jul 12 06:03:14 Disabling ramlog...                                      [ OK ]
    Jan 01 01:00:44 Enabling ramlog...                                       [ OK ]
    Jul 24 08:01:08 Stopping ramlog: Error: ramlog is not running            [fail]
    Jul 24 08:02:04 Starting ramlog-tmpfs 2.0.0:                             [ OK ]
    Jul 24 08:23:29 Saving logs to hdd:                                      [ OK ]
    Jul 24 08:23:30 Stopping ramlog:                                         [ OK ]
    Jul 24 08:24:12 Starting ramlog-tmpfs 2.0.0:                             [ OK ]
    Jul 24 08:29:22 Saving logs to hdd:                                      [ OK ]
    Jul 24 08:29:22 Stopping ramlog:                                         [ OK ]
    Jul 24 08:30:04 Starting ramlog-tmpfs 2.0.0:                             [ OK ]
    Jul 24 11:07:43 Saving logs to hdd:                                      [ OK ]
    Jul 24 11:07:45 Stopping ramlog:                                         [ OK ]
    Jul 24 11:08:31 Starting ramlog-tmpfs 2.0.0:                             [ OK ]
    Jul 24 11:39:22 Saving logs to hdd:                                      [ OK ]
    Jul 24 11:39:22 Stopping ramlog:                                         [ OK ]
    Jul 24 11:40:02 Starting ramlog-tmpfs 2.0.0:                             [ OK ]
    Jul 24 11:46:09 Saving logs to hdd:                                      [ OK ]
    Jul 24 11:46:10 Stopping ramlog:                                         [ OK ]
    Jul 24 11:47:05 Starting ramlog-tmpfs 2.0.0:                             [ OK ]
    Jul 24 11:54:24 Saving logs to hdd:                                      [ OK ]
    Jul 24 11:54:24 Stopping ramlog:                                         [ OK ]
    Jan 01 01:00:17 Starting ramlog-tmpfs 2.0.0:                             [ OK ]
    Jul 24 13:23:54 Saving logs to hdd:                                      [ OK ]
    Jul 24 13:23:59 Stopping ramlog:                                         [ OK ]
    Jul 24 13:24:45 Starting ramlog-tmpfs 2.0.0:                             [ OK ]
    Jul 24 13:40:13 Saving logs to hdd:                                      [ OK ]
    Jul 24 13:40:19 Stopping ramlog:                                         [ OK ]
    Jul 24 13:41:09 Starting ramlog-tmpfs 2.0.0: Error: /var/log is in use... [fail]
    Jul 24 13:41:09 The list of open files: (You need to close below daemons if you want to start/stop ramlog manually)

    COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
    slim    1999 root    3w   REG  179,1      334 1598 /var/log/slim.log
    sh      2002 root    3w   REG  179,1      334 1598 /var/log/slim.log
    Jul 24 13:41:09 Test result: ramlog cannot be started or stopped at the moment.
    Jul 24 13:46:19 ramlog: Cannot find shutdown flag file.                  [warning]
    Jul 24 13:46:19 Stopping ramlog: Error: ramlog is not running            [fail]
    Jul 24 13:47:00 Starting ramlog-tmpfs 2.0.0: Error: /var/log is in use... [fail]
    Jul 24 13:47:01 The list of open files: (You need to close below daemons if you want to start/stop ramlog manually)
     

    COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
    slim    1980 root    3w   REG  179,1      677 1598 /var/log/slim.log
    Xorg    1992 root    0w   REG  179,1        0  745 /var/log/Xorg.0.log.old
    Xorg    1992 root    3w   REG  179,1      677 1598 /var/log/slim.log
    Jul 24 13:47:01 Test result: ramlog cannot be started or stopped at the moment.
    Jul 24 14:04:32 ramlog: Cannot find shutdown flag file.                  [warning]
    Jul 24 14:04:33 Stopping ramlog: Error: ramlog is not running            [fail]
    Jul 24 14:05:14 Starting ramlog-tmpfs 2.0.0: Error: /var/log is in use... [fail]
    Jul 24 14:05:15 The list of open files: (You need to close below daemons if you want to start/stop ramlog manually)

    COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
    slim    1981 root    3w   REG  179,1      910 1598 /var/log/slim.log
    Jul 24 14:05:15 Test result: ramlog cannot be started or stopped at the moment.

     

     

    Shutdown/Reboot:

     

    [warn] ramlog: Cannot find shutdown flag file. ... (warning)

    [FAIL] Cannot find shutdown flag file. [.......] Stopping ramlog: Error: ramlog is not running Failed!

     

     

    Can you help me?

     

    Steffen

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines