エントリー

カテゴリー「Ubuntu」の検索結果は以下のとおりです。

Ubuntu Serverが起動しなくなる

ubuntu serverが昨日まで動いていたのに起動しなくなった

BIOSすら起動しないのでCPUが動作してないと思われる

参ったな・・・最近どれもこれも古いからか故障する

・・・

次の日マザー(K8M800-754)を取り出して見てみるとCPU周辺のコンデンサが怪しい

Albatron K8M800-754

5個ともに既に限界(寿命)を超えているように思える(つ~か、かなり酷い状態)

不良コンデンサ

コンデンサの仕様を見ると3300μF 4Vのようだ(入手が難しそうだな)

3300μF

こんなになるまでほっといたから交換しても動作しないかもしれないなぁ

Ubuntu Serverにlm-sensorsを導入

いまさらながらubuntus serverにlm-sensorsを導入

OS
  • Ubuntu Server 12.04 LTS AMD64
ハードウェア
  • MB: Albatron K8M800-754 (VIA K8M800, VIA VT8237R, RealTek RTL8100C)
  • CPU: AMD Turion 64 MT-30 (CLK:1.6GHz, L2:1MB, TDP:25W)
  • MEM: DDR 266 PC2100 512MB*2
セットアップ
$ sudo aptitude install lm-sensors
以下の新規パッケージがインストールされます:
  libsensors4{a} lm-sensors
0 個のパッケージを更新、 2 個を新たにインストール、 0 個を削除予定、104 個が更新されていない。
133 k バイトのアーカイブを取得する必要があります。 展開後に 554 k バイトのディスク領域が新たに消費されます。
先に進みますか? [Y/n/?] y
取得: 1 http://jp.archive.ubuntu.com/ubuntu/ precise/main libsensors4 amd64 1:3.3.1-2ubuntu1 [31.9 kB]
取得: 2 http://jp.archive.ubuntu.com/ubuntu/ precise/universe lm-sensors amd64 1:3.3.1-2ubuntu1 [101 kB]
Fetched 133 kB in 0秒 (363 kB/s)
Selecting previously unselected package libsensors4.
(データベースを読み込んでいます ... 現在 54989 個のファイルとディレクトリがイン ストールされています。)
(.../libsensors4_1%3a3.3.1-2ubuntu1_amd64.deb から) libsensors4 を展開しています...
Selecting previously unselected package lm-sensors.
(.../lm-sensors_1%3a3.3.1-2ubuntu1_amd64.deb から) lm-sensors を展開しています...
man-db のトリガを処理しています ...
ureadahead のトリガを処理しています ...
ureadahead will be reprofiled on next reboot
libsensors4 (1:3.3.1-2ubuntu1) を設定しています ...
lm-sensors (1:3.3.1-2ubuntu1) を設定しています ...
libc-bin のトリガを処理しています ...
ldconfig deferred processing now taking place

libsensors3が無かったのでどうしようかと思ったが、libsensors4が関連としてインストールされた

$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:         +9.0°C  (crit = +65.0°C)

k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:   +30.0°C
$ cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

loop
lp
rtc
コンフィグ

自動では定義の設定がされないようなので

$ sudo sensors-detect
# sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): y
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   Success!
    (driver `k8temp')
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 15h power sensors...                             No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Fintek F71805F/FG Super IO Sensors'                  Success!
    (address 0x295, driver `f71805f')

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): y
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): y
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): y
Using driver `i2c-viapro' for device 0000:00:11.0: VIA Technologies VT8237 South Bridge
Module i2c-dev loaded successfully.

Next adapter: SMBus Via Pro adapter at 5000 (i2c-0)
Do you want to scan it? (yes/NO/selectively): y
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No
Client found at address 0x51
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `f71805f':
  * ISA bus, address 0x295
    Chip `Fintek F71805F/FG Super IO Sensors' (confidence: 9)

Driver `k8temp' (autoloaded):
  * Chip `AMD K8 thermal sensors' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
f71805f
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

Do you want to add these lines automatically to /etc/modules? (yes/NO)y
Successful!

Monitoring programs won't work until the needed modules are
loaded. You may want to run 'service module-init-tools start'
to load them.

Unloading i2c-dev... OK
Unloading cpuid... OK

$

(再起動)

$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:         +9.0°C  (crit = +65.0°C)

k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp:   +34.0°C

とりあえずこれで良いか

ubuntu用segmenterの作成

参考:

https://github.com/carsonmcdonald/HTTP-Live-Video-Stream-Segmenter-and-Distributor/wiki/Install-on-Ubuntu-10.10

(追加:こちらが最適)
http://blog.kyri0s.org/post/1406637341/free-live-video-streaming-with-http-live-streaming

(追記:2012.10.10)
segmenter(http://svn.assembla.com/svn/legend/segmenter/ から取得、バージョン?)について
・ffmpegのモジュールを利用していて最新のffmpegではインタフェースの相違がある
・旧ffmpeg(2009-12-02)のモジュールを使用することによりmakeは可能
・makeできてもffmpeg以外のライブラリとの整合性もあるのか結果動作不安定

よって最新のffmpegのインタフェースに合わせるよう修正してみる

●OS: Ubuntu 10.04.4 LTS

●ffmpeg: version N-45221-g25f44b0
(以下作成)
参考:https://wiki.ubuntulinux.jp/UbuntuTips/Application/HowToInstallAndUseLatestFFmpegAndX264


ffmpeg version N-45221-g25f44b0 Copyright (c) 2000-2012 the FFmpeg developers
built on Oct 10 2012 17:10:42 with gcc 4.4.3 (Ubuntu 4.4.3-4ubuntu5.1)
configuration: --enable-gpl --enable-version3 --enable-nonfree --enable-postproc --enable-libfaac --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libtheora --enable-libvorbis --enable-libx264 --enable-libxvid --enable-x11grab --enable-libmp3lame --enable-libvpx
libavutil 51. 74.100 / 51. 74.100
libavcodec 54. 65.100 / 54. 65.100
libavformat 54. 31.100 / 54. 31.100
libavdevice 54. 3.100 / 54. 3.100
libavfilter 3. 19.102 / 3. 19.102
libswscale 2. 1.101 / 2. 1.101
libswresample 0. 16.100 / 0. 16.100
libpostproc 52. 1.100 / 52. 1.100
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options] outfile}...

Use -h to get full help or, even better, run 'man ffmpeg'

●segmenter: http://svn.assembla.com/svn/legend/segmenter/
(変更箇所)


28c28
< output_stream = av_new_stream(output_format_context, 0);
---
> output_stream = avformat_new_stream(output_format_context, 0);
53c53
< case CODEC_TYPE_AUDIO:
---
> case AVMEDIA_TYPE_AUDIO:
65c65
< case CODEC_TYPE_VIDEO:
---
> case AVMEDIA_TYPE_VIDEO:
231c231
< ret = av_open_input_file(&ic, input, ifmt, 0, NULL);
---
> ret = avformat_open_input(&ic, input, ifmt, NULL);
237c237
< if (av_find_stream_info(ic) < 0) {
---
> if (avformat_find_stream_info(ic, NULL) < 0) {
242c242
< ofmt = guess_format("mpegts", NULL, NULL);
---
> ofmt = av_guess_format("mpegts", NULL, NULL);
260c260
< case CODEC_TYPE_VIDEO:
---
> case AVMEDIA_TYPE_VIDEO:
265c265
< case CODEC_TYPE_AUDIO:
---
> case AVMEDIA_TYPE_AUDIO:
276,279c276,279
< if (av_set_parameters(oc, NULL) < 0) {
< fprintf(stderr, "Invalid output format parameters ");
< exit(1);
< }
---
> // if (av_set_parameters(oc, NULL) < 0) {
> // fprintf(stderr, "Invalid output format parameters ");
> // exit(1);
> // }
281c281
< dump_format(oc, 0, output_prefix, 1);
---
> av_dump_format(oc, 0, output_prefix, 1);
288c288
< if (avcodec_open(video_st->codec, codec) < 0) {
---
> if (avcodec_open2(video_st->codec, codec, NULL) < 0) {
293c293
< if (url_fopen(&oc->pb, output_filename, URL_WRONLY) < 0) {
---
> if (avio_open(&oc->pb, output_filename, AVIO_FLAG_WRITE) < 0) {
298c298
< if (av_write_header(oc)) {
---
> if (avformat_write_header(oc, NULL)) {
320c320
< if (packet.stream_index == video_index && (packet.flags & PKT_FLAG_KEY)) {
---
> if (packet.stream_index == video_index && (packet.flags & AV_PKT_FLAG_KEY)) {
331,332c331,332
< put_flush_packet(oc->pb);
< url_fclose(oc->pb);
---
> avio_flush(oc->pb);
> avio_close(oc->pb);
352c352
< if (url_fopen(&oc->pb, output_filename, URL_WRONLY) < 0) {
---
> if (avio_open(&oc->pb, output_filename, AVIO_FLAG_WRITE) < 0) {
382c382
< url_fclose(oc->pb);
---
> avio_close(oc->pb);

(makefile:ldは基本的にffmpegに合わせればよい)


all: segmenter
gcc -Wall -g segmenter.c -o segmenter
-I/usr/local/inlcude -L/usr/local/lib
-lavformat -lavcodec -lavutil
-lfaac -lmp3lame -lx264 -lvpx
-lxvidcore -lvorbisenc -ltheoraenc -ltheoradec
-lopencore-amrwb -lopencore-amrnb
-lm -lbz2 -lz

clean:
rm segmenter

install: segmenter
cp segmenter /usr/local/bin/

uninstall:
rm /usr/local/bin/segmenter

●動作確認
・完全な検証が困難なんでx86版での結果とサイズを比べてみたら問題なさそう
・vlcで再生できたし、なんとか動作しているように思える
・tsファイルの分割は一時的な物なので視聴できているので一応OK

(更に追記:2012.10.10)
M3U8 segmenter is an Apple HTTP Live Segmenter というのを発見
http://m3u8-segmenter.inodes.org/

ソースを取ってきて最新ffmpegでmakeしてみた
異常?メッセージが出ているが正常に終了しているようだ

尚、オプションスイッチが変更されているので利用時は注意


Usage: m3u8-sementer [OPTION]...

HTTP Live Streaming - Segments TS file and creates M3U8 index.
-i, --input FILE TS file to segment (Use - for stdin)
-d, --duration SECONDS Duration of each segment (default: 10 seconds)
-p, --output-prefix PREFIX Prefix for the TS segments, will be appended
with -1.ts, -2.ts etc
-m, --m3u8-file FILE M3U8 output filename
-u, --url-prefix PREFIX Prefix for web address of segments, e.g. http://example.org/video/
-n, --num-segment NUMBER Number of segments to keep on disk
-h, --help This help

こちらのほうが安心して使えるかな?

とりあえず、終了

PPC Ubuntu 10.04 LTS (Lucid Lynx)

ページ移動

  • ページ
  • 1
  • 2
  • 3

ユーティリティ

検索

エントリー検索フォーム
キーワード

新着コメント

Re:3.6Vの組充電池用充電器の試作
2022/11/06 from admin
Re:3.6Vの組充電池用充電器の試作
2022/11/03 from 通りすがり
Re:WXtoImgのweather.txtが更新できない件
2022/09/14 from admin
Re:WXtoImgのweather.txtが更新できない件
2022/09/14 from matusita
Re:メロディICと圧電サウンダ
2022/08/29 from 権限がありません

過去ログ

Feed