구차니의 잡동사니 모음

$ blender

Color management: using fallback mode for management

connect failed: No such file or directory

libGL error: MESA-LOADER: malformed or no PCI ID

libGL error: dlopen /usr/lib/arm-linux-gnueabihf/dri/exynos_dri.so failed (/usr/lib/arm-linux-gnueabihf/dri/exynos_dri.so: cannot open shared object file: No such file or directory)

libGL error: dlopen ${ORIGIN}/dri/exynos_dri.so failed (${ORIGIN}/dri/exynos_dri.so: cannot open shared object file: No such file or directory)

libGL error: dlopen /usr/lib/dri/exynos_dri.so failed (/usr/lib/dri/exynos_dri.so: cannot open shared object file: No such file or directory)

libGL error: unable to load driver: exynos_dri.so

libGL error: driver pointer missing

libGL error: failed to load driver: exynos

Writing: /tmp/blender.crash.txt

Segmentation fault 

/usr/lib/arm-linux-gnueabihf$ ll libdrm_exynos.*

-rw-r--r-- 1 root root 12118 may 12 03:41 libdrm_exynos.a

lrwxrwxrwx 1 root root    22 may 12 03:40 libdrm_exynos.so -> libdrm_exynos.so.1.0.0

lrwxrwxrwx 1 root root    22 may 12 03:40 libdrm_exynos.so.1 -> libdrm_exynos.so.1.0.0

-rw-r--r-- 1 root root 13732 may 12 03:41 libdrm_exynos.so.1.0.0 

/usr/lib/arm-linux-gnueabihf/dri$ ll

total 21116

drwxr-xr-x  2 root root    4096 oct  8 21:28 ./

drwxr-xr-x 94 root root   94208 oct 23 21:11 ../

-rw-r--r--  1 root root   13884 abr 16  2014 dummy_drv_video.so

-rw-r--r--  1 root root 2632560 ene 13  2016 nouveau_dri.so

-rw-r--r--  4 root root 2482560 ene 13  2016 nouveau_vieux_dri.so

-rw-r--r--  4 root root 2482560 ene 13  2016 r200_dri.so

-rw-r--r--  1 root root 2186172 ene 13  2016 r300_dri.so

-rw-r--r--  1 root root 2550644 ene 13  2016 r600_dri.so

-rw-r--r--  4 root root 2482560 ene 13  2016 radeon_dri.so

-rw-r--r--  1 root root 2086952 ene 13  2016 radeonsi_dri.so

-rw-r--r--  4 root root 2482560 ene 13  2016 swrast_dri.so

-rw-r--r--  1 root root 2096024 ene 13  2016 vmwgfx_dri.so 

$ armsoc.sh

bash: /usr/local/bin/armsoc.sh: Permission denied 

$ cat /usr/local/bin/armsoc.sh

#!/bin/bash

rebuild_armsoc() { 

get_board 

if [ "$BOARD" = "odroidxu" ]; then

armsoc_err_not_supported

return

fi

if [ "$BOARD" = "odroidc" ]; then

apt-get -y update

apt-get -y dist-upgrade

msgbox "All updates performed. You don't need to run any other updates."

return

fi

do_5422_1504_apt_update

if [ "$DISTRO" = "ubuntu" ]; then

armsoc_rebuild_ubuntu

elif [ "$DISTRO" = "debian" ]; then

armsoc_rebuild_debian

else

armsoc_err_not_supported

fi

}

armsoc_rebuild_ubuntu() { 

if [ "$BOARD" = "odroidxu3" ]; then

msgbox "ODROID-XU3 isn't supported yet"

return

fi

root=/tmp/armsoc-update

buildlog=/root/armsoc-update-$DATE.txt

mkdir -p $root

cd $root

# Install dependencies.

apt-get -y build-dep xserver-xorg-video-armsoc

# Download the blobs

dlf builder.mdrjr.net/tools/u3/4412_r5p0_x11.tar.xz "Downloading Mali Binaries" $root/mali.tar.xz

# Download armsoc DDX from github

dlf https://github.com/mdrjr/xf86-video-armsoc/archive/r4p0.zip "Downloading ARMSOC DDX Sources from Github" $root/ddx.zip

echo "Building Mali DDX and Installing Binaries. Please wait"

echo "Saving build logs to $buildlog"

# Unpack

xz -d mali.tar.xz &>> $buildlog

tar xf mali.tar &>> $buildlog

unzip -qq ddx.zip &>> $buildlog

# Build DDX

cd xf86-video-armsoc-r4p0

./autogen.sh --with-drmmode=exynos --prefix=/usr &>> $buildlog

make -j4 &>> $buildlog

make install &>> $buildlog

cd ..

# Install new Binaries

cd mali

cp -aRP lib* /usr/lib

cp -aRP lib* /usr/lib/arm-linux-gnueabihf/mali-egl

ldconfig

cp config/xorg.conf /etc/X11/xorg.conf

sync

msgbox "Mali is now updated. If something fails or isn't working report on the forums with the following file: $buildlog"

}

armsoc_rebuild_debian() { 

if [ "$BOARD" = "odroidxu3" ]; then

msgbox "ODROID-XU3 isn't supported yet"

return

fi

root=/tmp/armsoc-update

buildlog=/root/armsoc-update-$DATE.txt

mkdir -p $root

cd $root

echo "Debian requires some extra packages to build. We are installing it.. Please wait."

# debian requires some extra packages to build the DDX. So.. lets install it

apt-get -y build-dep xserver-xorg-video-modesetting xserver-xorg-video-nouveau &>> $buildlog

apt-get -y install build-essential git xz-utils xserver-xorg-dev libudev-dev &>> $buildlog

# Download the blobs

dlf builder.mdrjr.net/tools/u3/4412_r5p0_x11.tar.xz "Downloading Mali Binaries" $root/mali.tar.xz

# Download armsoc DDX from github

dlf https://github.com/mdrjr/xf86-video-armsoc/archive/r4p0.zip "Downloading ARMSOC DDX Sources from Github" $root/ddx.zip

echo "Building Mali DDX and Installing Binaries. Please wait"

echo "Saving build logs to $buildlog"

# Unpack

xz -d mali.tar.xz &>> $buildlog

tar xf mali.tar &>> $buildlog

unzip -qq ddx.zip &>> $buildlog

# Build DDX

cd xf86-video-armsoc-r4p0

./autogen.sh --with-drmmode=exynos --prefix=/usr &>> $buildlog

make -j4 &>> $buildlog

make install &>> $buildlog

cd ..

# Install new Binaries

cd mali

cp -aRP lib* /usr/lib

ldconfig

cp config/xorg.conf /etc/X11/xorg.conf

cd /tmp && rm -fr $root

sync

msgbox "Mali is now updated. If something fails or isn't working report on the forums with the following file: $buildlog"

}

armsoc_err_not_supported() {

msgbox "ARMSOC: Your distro isn't supported. Report this on the forums -> Distro $DISTRO and board $BOARD"

}

/usr/lib/arm-linux-gnueabihf/mali-egl$ ll

total 1172

drwxr-xr-x  2 root root    4096 oct 23 22:19 ./

drwxr-xr-x 94 root root   94208 oct 23 21:11 ../

-rw-r--r--  1 root root      38 may  8  2014 ld.so.conf

lrwxrwxrwx  1 root root      11 feb 18  2015 libEGL.so -> libEGL.so.1*

lrwxrwxrwx  1 root root      13 feb 18  2015 libEGL.so.1 -> libEGL.so.1.4*

lrwxrwxrwx  1 root root      10 feb 18  2015 libEGL.so.1.4 -> libMali.so*

lrwxrwxrwx  1 root root      17 feb 18  2015 libGLESv1_CM.so -> libGLESv1_CM.so.1*

lrwxrwxrwx  1 root root      19 feb 18  2015 libGLESv1_CM.so.1 -> libGLESv1_CM.so.1.1*

lrwxrwxrwx  1 root root      10 feb 18  2015 libGLESv1_CM.so.1.1 -> libMali.so*

lrwxrwxrwx  1 root root      14 feb 18  2015 libGLESv2.so -> libGLESv2.so.2*

lrwxrwxrwx  1 root root      16 feb 18  2015 libGLESv2.so.2 -> libGLESv2.so.2.0*

lrwxrwxrwx  1 root root      10 feb 18  2015 libGLESv2.so.2.0 -> libMali.so*

-rwxr-xr-x  1 root root 1066735 feb 18  2015 libMali.so*

-rw-r--r--  1 root root   22232 feb 22  2013 libUMP.so

log$ grep "EE" Xorg.0.log

[   593.576] (EE) AIGLX error: dlopen of /usr/lib/arm-linux-gnueabihf/dri/armsoc_dri.so failed (/usr/lib/arm-linux-gnueabihf/dri/armsoc_dri.so: cannot open shared object file: No such file or directory)

[   593.576] (EE) AIGLX: reverting to software rendering 

static void

_HibernateWriteComplete(void)

{

    //

    // Spin until the write complete bit is set.

    //

    while(!(HWREG(HIB_CTL) & HIB_CTL_WRC))

    {

    }

}

void

HibernateEnableExpClk(uint32_t ui32HibClk)

{

    //

    // Turn on the clock enable bit.

    //

    HWREG(HIB_CTL) |= HIB_CTL_CLK32EN;

    //

    // Wait for write complete following register load (above).

    //

    _HibernateWriteComplete();

} 

void

HibernateClockConfig(uint32_t ui32Config)

{

    uint32_t ui32HIBCtl;

    ASSERT((ui32Config & ~(HIBERNATE_OSC_HIGHDRIVE | HIBERNATE_OSC_LOWDRIVE |

                           HIBERNATE_OSC_DISABLE)) == 0);

    ui32HIBCtl = HWREG(HIB_CTL);

    //

    // Clear the current configuration bits.

    //

    ui32HIBCtl &= ~(HIBERNATE_OSC_HIGHDRIVE | HIBERNATE_OSC_LOWDRIVE |

                    HIBERNATE_OSC_LFIOSC | HIBERNATE_OSC_DISABLE);

    //

    // Set the new configuration bits.

    //

    ui32HIBCtl |= ui32Config & (HIBERNATE_OSC_HIGHDRIVE |

                                HIBERNATE_OSC_LOWDRIVE |

                                HIBERNATE_OSC_LFIOSC |

                                HIBERNATE_OSC_DISABLE);

    //

    // Must be sure that the 32KHz clock is enabled if the hibernate is about

    // to switch to it.

    //

    if(ui32Config & HIBERNATE_OSC_LFIOSC)

    {

        ui32HIBCtl |= HIB_CTL_CLK32EN;

    }

    //

    // Set the hibernation clocking configuration.

    //

    HWREG(HIB_CTL) = ui32HIBCtl;

    //

    // Wait for write completion

    //

    _HibernateWriteComplete();

    //

    // Write the output clock configuration for devices that support

    // controlling the output clocks from the hibernate module.

    //

    if(HIBERNATE_CLOCK_OUTPUT)

    {

        HWREG(HIB_CC) = ui32Config & (HIBERNATE_OUT_SYSCLK |

                                      HIBERNATE_OUT_ALT1CLK);

    }

} 

void

HibernateEnableExpClk(unsigned long ulHibClk)

{

    //

    // Turn on the clock enable bit.

    //

    HWREG(HIB_CTL) |= HIB_CTL_CLK32EN;

    //

    // For Fury-class devices, compute the number of delay loops that must be

    // used to achieve the desired delay for writes to the hibernation

    // registers.  This value will be used in calls to SysCtlDelay().

    //

    if(CLASS_IS_FURY)

    {

        g_ulWriteDelay = (((ulHibClk / 1000) * DELAY_USECS) /

                          (1000L * LOOP_CYCLES));

        g_ulWriteDelay++;

    }

}

Because your old disc was partitioned with a old utility, such as the Linux fdisk, that uselessly implemented track-alignment using the entirely fake disc geometry that you see reported, and your new disc has been or is being partitioned by a newer utility that (by default) aligns to 1MiB boundaries instead. 

In other words, the LBA sector number 63 corresponds to cylinder 0, head 1, sector 1 in the CHS format, which is the first sector you can use in the MBR format. However, the number 63 is not divisible by 8, which causes a problem with 4K drives, so some modern tools starts the first partition at 2048 which also provides future GPT compatibility. – billc.cn Oct 31 '11 at 23:48 

$ tty

/dev/pts/1

$ screen

$ tty

/dev/pts/6

ctrl-a,c

$ tty

/dev/pts/7

ctrl-a,n

window change

ctrl-a,d detach

[detached from 4014.pts-1.odroid_1]

// detach 시에는 다른 창을 만들어 두었더라도 전부 같이 떨어진다.

$ ps -ef | grep -i screen

odroid    4014     1  0 11:49 ?        00:00:00 SCREEN

$ screen -r

reattach

                       Screen key bindings, page 1 of 2.

                       Command key:  ^A   Literal ^A:  a

  break       ^B b         license     ,            removebuf   =

  clear       C            lockscreen  ^X x         reset       Z

  colon       :            log         H            screen      ^C c

  copy        ^[ [         login       L            select      '

  detach      ^D d         meta        a            silence     _

  digraph     ^V           monitor     M            split       S

  displays    *            next        ^@ ^N sp n   suspend     ^Z z

  dumptermcap .            number      N            time        ^T t

  fit         F            only        Q            title       A

  flow        ^F f         other       ^A           vbell       ^G

  focus       ^I           pow_break   B            version     v

  hardcopy    h            pow_detach  D            width       W

  help        ?            prev        ^H ^P p ^?   windows     ^W w

  history     { }          quit        \            wrap        ^R r

  info        i            readbuf     <            writebuf    >

  kill        K k          redisplay   ^L l         xoff        ^S s

  lastmsg     ^M m         remove      X            xon         ^Q q

                  [Press Space for next page; Return to end.]

                       Screen key bindings, page 2 of 2.

^]   paste .

"    windowlist -b

-    select -

0    select 0

1    select 1

2    select 2

3    select 3

4    select 4

5    select 5

6    select 6

7    select 7

8    select 8

9    select 9

I    login on

O    login off

]    paste .

|    split -v

:kB: focus prev

                        [Press Space or Return to end.]  

$ ps -ef | grep -i screen

odroid    4014     1  0 11:49 ?        00:00:00 SCREEN

odroid   17153  1554  0 11:57 pts/1    00:00:00 screen -r 

$ screen -r

There is a screen on:

        4014.pts-1.odroid_1     (22/10/16 11:49:14)     (Attached)

There is no screen to be resumed. 

$ screen -r

There are several suitable screens on:

        24631.pts-12.odroid_1   (22/10/16 12:02:24)     (Detached)

        4014.pts-1.odroid_1     (22/10/16 11:49:13)     (Detached)

Type "screen [-d] -r [pid.]tty.host" to resume one of them. 

$ ps -ef | grep -i screen

odroid    4014     1  0 11:49 ?        00:00:00 SCREEN

odroid   24631     1  0 12:02 ?        00:00:00 SCREEN

GPU acceleration on the Chromium Web browser

/etc/chromium-browser/default

CHROMIUM_FLAGS=" --use-gl=egl --ignore-gpu-blacklist --disable-accelerated-2d-canvas --num-raster-threads=2"

Slow window moving

menu/settings/Default applications for LXSession –> Core applications –> Windows manager –> metacity

Note that, the metacity doesn't support the short-cut keys well. 

The SAMA5D3 provides up to 24 bits of ECC code per sector of 512 or 1024 bytes. Table 1-1 provides the number of ECC bytes required depending on the number of errors to correct. 

Hamming

A 512B data block consists of 4096 (2^12) bits, thus a Hamming code requires 24 parity bits.

Reed-Solomon

An RS over a 512B data block consisting of 9-bit symbols capable of supporting 8 symbol correction would require 2*9*8, or 144 bits of parity.

BCH

Blocksize ECC Level ECC Bits ECC Bytes

512B ECC 8 13*8=104 13

512B ECC 16 13*16=208 26

1024B ECC 24 14*24=336 42

1024B ECC 40 14*40=560 70 

NOTE:

• Windows 8/8.1/10 are NOT supported in PL-2303HXA and PL-2303X EOL chip versions.
• Run PL2303 CheckChipVersion tool program in Windows XP/Vista/7 to check chip version.
• Windows XP, 2000, 98 and Windows ME driver technical support is discontinued.
• Prolific recommends to use PL-2303HXD (HX Rev D) or PL2303TA chip.

Device using PL-2303 H/HXA/HX/X version chips

Driver Version: 3.3.2.102

Driver Date: 09/29/08

Supported device ID and product strings: . VID_067B&PID_2303 for "Prolific USB-to-Serial Comm Port" 

Please be warned that counterfeit (fake) PL-2303HX (Chip Rev A) USB to Serial Controller ICs using Prolific's trademark logo, brandname, and device drivers, were being sold in the China market. Counterfeit IC products show exactly the same outside chip markings but generally are of poor quality and causes Windows driver compatibility issues (Yellow Mark Error Code 10 in Device Manager). We issue this warning to all our customers and consumers to avoid confusion and false purchase.