Patrzysz na wiadomości znalezione dla zapytania: 3e y activejet

Jestem ciekawy czy Biskup cokolwiek robi w JADE ? Mamy juz polowe roku (juz nie mowie ze TB zapowiadal "much more active 2007 year") a nic ciekawego nie slychac ? Czy Thomas sobie odpuscil ,czy JADE go przeroslo ? Dziwi mnie ten facet jakis czas temu pokazywal screeny i pisal ze juz oprocz itemow i potworkow wszystko ma ? a tu dupa...dodatkow mial wydac ADoM deluxe'a i zgarniac za niego kase - tez dupa ? Tym bardziej (sadzac po miliniowych "wejsciach") dziwi fakt ze facet nie ciagnie tematu jakby umiejetnie sie zakrecil ,to moglby żyć z ADoMa...

Z innej beczki moje pytanie do Was znawcow rogali brzmi tak "Czy istnieje jakis rogal ktory jest na bierzaco (czyt.ostatni upgrade rok 2007) rozwijany i ktory ma jakas porzadna strone i forum ???"

Ł.3E-DA

To jeszcze odp[owiedz mi, co takiego się stało po 15.09 - (podpowiadam że może coś 17.09), że przestało się to "miescić w logice obrony Georgesa"

Już odpowiedziałem. Wcześniej, ale skoro o to prosisz:
Le 15 septembre, le gĂŠnĂŠral Georges prescrit Ă la 3e armĂŠe et au 6e CA d'attaquer la ferme de BĂŠrus qui constitue un magnifique observatoire sur la ville de Saarlouis et la vallĂŠe de la Sarre. Cette attaque, qui nĂŠcessite au moins trois divisions d'active et cinq bataillons de chars R 35, est finalement abandonnĂŠe, l'ennemi se renforĂ§ant de jour en jour dans ce secteur.

To fragment logu (w tym zakresie czasu odcięło mnie od sieci od sieci)

May 2 19:59:07 router thttpd[562]: up 511200 seconds, stats for 3600 seconds:
May 2 19:59:07 router thttpd[562]: thttpd - 4 connections (0.00111111/sec), 1 max simultaneous, 781 bytes (0.216944/sec), 2 httpd_conns allocated
May 2 19:59:07 router thttpd[562]: libhttpd - 31 strings allocated, 16400 bytes (529.032 bytes/str)
May 2 19:59:07 router thttpd[562]: map cache - 8 allocated, 0 active (0 bytes), 8 free; hash size: 1024; expire age: 1800
May 2 19:59:07 router thttpd[562]: fdwatch - 746 polls (0.207222/sec)
May 2 19:59:07 router thttpd[562]: timers - 3 allocated, 3 active, 0 free
May 2 20:32:57 router dhcpd: Wrote 8 leases to leases file.
May 2 20:35:43 router dhcpd: DHCPREQUEST for 192.168.0.5 from 00:0e:2e:60:d5:3e (nowy) via eth0
May 2 20:35:43 router dhcpd: DHCPACK on 192.168.0.5 to 00:0e:2e:60:d5:3e (nowy) via eth0
May 2 20:56:57 router dhcpd: DHCPDISCOVER from 00:0e:2e:60:d5:3e (nowy) via eth0
May 2 20:56:58 router dhcpd: DHCPOFFER on 192.168.0.5 to 00:0e:2e:60:d5:3e (nowy) via eth0
May 2 20:56:58 router dhcpd: DHCPREQUEST for 192.168.0.5 (192.168.0.1) from 00:0e:2e:60:d5:3e (nowy) via eth0
May 2 20:56:58 router dhcpd: DHCPACK on 192.168.0.5 to 00:0e:2e:60:d5:3e (nowy) via eth0
May 2 20:59:07 router thttpd[562]: up 514800 seconds, stats for 3600 seconds:
May 2 20:59:07 router thttpd[562]: thttpd - 4 connections (0.00111111/sec), 1 max simultaneous, 1093 bytes (0.303611/sec), 2 httpd_conns allocated
May 2 20:59:07 router thttpd[562]: libhttpd - 31 strings allocated, 16400 bytes (529.032 bytes/str)
May 2 20:59:07 router thttpd[562]: map cache - 8 allocated, 3 active (1093 bytes), 5 free; hash size: 1024; expire age: 1800
May 2 20:59:07 router thttpd[562]: fdwatch - 747 polls (0.2075/sec)
May 2 20:59:07 router thttpd[562]: timers - 3 allocated, 3 active, 0 free

o 20:56:58 wyłaczyłem i właczyłem sieć i miałem ponownie sieć.

Pakiet: Dish Network
Satelita: EchoStar 3 61.5°W
System kodowania: Nagravision2
CAID: 1801
ProvID: 0101

Kod:
Key 00: 3F 6F 1F FE 1B 52 3E F8 29 D8 21 DA 80 68 0C 86 ->Active
Key 01: 36 C5 BF 32 8E F3 65 E8 B4 62 6D 36 DC 8E 85 51

Bell ExpressVu (0901)

86: CD 7F 03 26 BF 4A FE DD 87 C2 47 7F 10 FE 44 F2
96: 53 D8 68 B2 17 C9 C7 44 3B 24 35 8D 9B 3E B9 A9 <---Active

Keys for Dream TV @ 146°E Agila 2
Ident: 4E 01 / 4F 01
DEC: 079 001
Key 00: 6D 50 19 45 C9 CB 63 3E
DEC: 109 080 025 069 201 203 099 062
Key 01: 98 CF 1C F5 8D CB 6A 5F <--- Active
DEC: 152 207 028 245 141 203 106 095

Dream TV @ 146E Agila 2
Ident: 4E 01 / 4F 01
DEC: 079 001
KEY 00: 4B B7 7A 0A 34 A8 8B 9B <--- Active
DEC: 075 183 122 010 052 168 139 155
KEY 01: 91 36 F5 B5 ED 99 83 3E
DEC: 145 054 245 181 237 153 131 062

02/ C1 CC C4 A6 AF F3 18 94 03/ 8F 79 C8 80 3E 70 90 1A (active)11:35 07.09.2007

02/ C1 CC C4 A6 AF F3 18 94
03/ 8F 79 C8 80 3E 70 90 1A (active)11:35 07.09.2007

Hi!
Jaki kod ma ALT i efy?

readkey 1 2
f1 - $00 $3b;
f2 - $00 $3c;
f3 - $00 $3d;
f4 - $00 $3e;
f5 - $00 $3f;
f6 - $00 $40;
f7 - $00 $41;
f8 - $00 $42;
f9 - $00 $43;
f10 - $00 $44;

Í7-6-5-4-3-2-1-0Ì
¦i¦c¦n¦s¦A¦C¦ ¦ ¦ Perform INT 16H or fetch AL=byte at 0:0417
ËÏ-Ï-Ï-Ï-Ï-Ï-Ï-Ï¯ bit
¦ ¦ ¦ ¦ ¦ ¦ ¦ +- 0: alpha-shift (right shift key) (AL & 01H) 01H=depressed
¦ ¦ ¦ ¦ ¦ ¦ +--- 1: alpha-shift (left shift key) (AL & 02H) 02H=depressed
¦ ¦ ¦ ¦ ¦ +----- 2: Ctrl-shift (AL & 04H) 04H=[Ctrl] is depressed
¦ ¦ ¦ ¦ +------- 3: Alt-shift (AL & 08H) 08H=[Alt] is depressed
¦ ¦ ¦ +--------- 4: ScrollLock state (AL & 10H) 10H=ScrollLock state active
¦ ¦ +----------- 5: NumLock state (AL & 20H) 20H=NumLock state active
¦ +------------- 6: CapsLock state (AL & 40H) 40H=CapsLock state active
+--------------- 7: Insert state (AL & 80H) 80H=Insert state active

Í7-6-5-4-3-2-1-0Ì
¦I¦C¦N¦S¦ ¦ ¦ ¦ ¦ fetch AL=byte at 0:0418
ËÏ-Ï-Ï-Ï-Ï-Ï-Ï-Ï¯ bit
¦ ¦ ¦ ¦ ¦ ¦ ¦ +- 0: Ctrl-shift (left Ctrl key) (AL & 01H) 01H=depressed
¦ ¦ ¦ ¦ ¦ ¦ +--- 1: Alt-shift (left Alt key) (AL & 02H) 02H=depressed
¦ ¦ ¦ ¦ ¦ +----- 2: SysReq (AL & 04H) 40H=SysReq key is depressed
¦ ¦ ¦ ¦ +------- 3: hold state (AL & 08H) 08H Ctrl-NumLock (Pause) is active
¦ ¦ ¦ +--------- 4: ScrollLock (AL & 10H) 10H=[ScrollLock] is depressed
¦ ¦ +----------- 5: NumLock (AL & 20H) 20H=[NumLock] is depressed
¦ +------------- 6: CapsLock (AL & 40H) 40H=[CapsLock] is depressed
+--------------- 7: Insert (AL & 80H) 80H=[Ins] is depressed

Notes: Bits 0-2 of 0:0418 are defined only for the 101-key enhanced keyboard.
Bit 2 is used by the PCjr to indicate "key click" is active.

Some older programs change the values of NumLock and CapsLock state bits
(at 0:0417) to force a known status. This is unwise because modern
keyboards have indicator lights which will get out of sync with the
status. See AT Keyboard for more information on the lock-key LEDs.

Time for yet another update here

The progress of the last two weeks is quite encouraging. We've decided to give the extend approach for scripting a try in a separate branch but it looks like that this branch will replace our current trunk version quite fast. The work on it isn't finished yet but it seems that the performance drawback of the extend approach should be bearable; some initial tests (although with work in progress code and just on tested a Linux system) did show almost no performance drawbacks at all.

For anyone who's interested to know more about it and is not afraid of playing around with some work in progress code, check out our extend branch in SVN:
branches/active/extend

One major advantage of the extend approach in combination with SWIG is that you'll be able to get FIFE running with bindings for your favourite scripting language quite easily. We do currently play around with Python support and that works quite well. Additionally we'll maintain support for Lua bindings as Lua was our language of choice before we decided to try something different than embedding the scripting language into FIFE. It shouldn't be too hard to create Ruby or OCaml bindings for FIFE either and if we find somebody who maintains these bindings, they'll find their way into our Subversion repository so you won't even need to invest time to generate the bindings yourself (although SWIG makes it rather easy in most cases).

Here is a nice screenshot from one of our recent test sessions. It shows the FIFE console that now can execute Python code e.g. for ingame manipulations or debugging your FIFE-based game:

Besides the work on the extend branch we're currently trying to fill our wiki with use cases for some possible FIFE-based games. That's because we intend to tackle the design of our scripting API after the work on the extend branch has finished. There is already a pretty small API in place but as it was written as proof of concept and for doing initial scripting tests it is neither consistent nor feature-complete. So we're trying to collect some real game examples first, analyze them concerning their requirements for a scripting API and plan to come up with a consistent design for our API after that.

If you consider to use FIFE for an own game in the future feel free to lend us a hand by contributing to the use cases. And don't be afraid: there are already a bunch of examples listed there that should make it easy for you to get started. If you would like to contribute but don't understand the concept of the use cases or got other related questions feel free to ask them here or at the talk page of our use case wiki article:
Use cases for the FIFE scripting API

And last but not least we're still searching for interested programmers who would like to collect some experience working on a rather large scale group project And we're usually kind guys and don't bite so if you want to find out more about us before you sign a lifetime contract with us feel free to visit our irc channel
#fife @ quakenet

| hda: dma_timer_expiry: dma status == 0x21
| hda: error waiting for DMA
| hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }
| hda: dma_timer_expiry: dma status == 0x21
| hda: error waiting for DMA
| hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }

Na innym kompie jest tak samo,

Smart:

=== START OF INFORMATION SECTION ===
Device Model: ST340016A
Serial Number: 3HS0TR8K
Firmware Version: 3.05
User Capacity: 40,020,664,320 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 5
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Fri Jun 23 20:26:19 2006 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 422) seconds.
Offline data collection
capabilities: (0x1b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 31) minutes.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 065 061 034 Pre-fail Always - 219337760
3 Spin_Up_Time 0x0003 085 070 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 735
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 085 060 030 Pre-fail Always - 364066955
9 Power_On_Hours 0x0032 081 081 000 Old_age Always - 16744
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 098 098 020 Old_age Always - 2864
194 Temperature_Celsius 0x0022 041 062 000 Old_age Always - 41
195 Hardware_ECC_Recovered 0x001a 065 061 000 Old_age Always - 219337760
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 018 000 Old_age Always - 302
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0
202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0

SMART Error Log Version: 1
ATA Error Count: 926 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 926 occurred at disk power-on lifetime: 15326 hours (638 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 04 8c 02 b8 Error: ICRC, ABRT at LBA = 0x08028c04 = 134384644

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 04 8c 02 b8 00 00:03:25.075 READ DMA
c8 00 08 03 88 01 b7 00 00:03:25.070 READ DMA
c8 00 08 02 84 00 b6 00 00:03:25.056 READ DMA
10 00 3f 00 00 00 b0 00 00:03:25.056 RECALIBRATE [OBS-4]
c8 00 08 02 84 00 b6 00 00:03:24.639 READ DMA

Error 925 occurred at disk power-on lifetime: 15326 hours (638 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 02 84 00 b6 Error: ICRC, ABRT at LBA = 0x06008402 = 100697090

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 02 84 00 b6 00 00:03:24.639 READ DMA
c8 00 08 02 84 00 b6 00 00:03:24.209 READ DMA
c8 00 08 01 80 ff b5 00 00:03:24.199 READ DMA
c8 00 08 3f 7c fe b3 00 00:03:24.191 READ DMA
c8 00 08 3e 78 fd b2 00 00:03:24.171 READ DMA

Error 924 occurred at disk power-on lifetime: 15326 hours (638 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 02 84 00 b6 Error: ICRC, ABRT at LBA = 0x06008402 = 100697090

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 02 84 00 b6 00 00:03:24.209 READ DMA
c8 00 08 01 80 ff b5 00 00:03:24.199 READ DMA
c8 00 08 3f 7c fe b3 00 00:03:24.191 READ DMA
c8 00 08 3e 78 fd b2 00 00:03:24.171 READ DMA
10 00 3f 00 00 00 b0 00 00:03:24.171 RECALIBRATE [OBS-4]

Error 923 occurred at disk power-on lifetime: 15326 hours (638 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 3e 78 fd b2 Error: ICRC, ABRT at LBA = 0x02fd783e = 50165822

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 3e 78 fd b2 00 00:03:23.734 READ DMA
c8 00 08 3e 78 fd b2 00 00:03:23.323 READ DMA
c8 00 08 3d 74 fc b1 00 00:03:23.314 READ DMA
c8 00 08 3c 70 fb b0 00 00:03:23.304 READ DMA
c8 00 08 3b 6b fa bf 00 00:03:23.285 READ DMA

Error 922 occurred at disk power-on lifetime: 15326 hours (638 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 3e 78 fd b2 Error: ICRC, ABRT at LBA = 0x02fd783e = 50165822

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 3e 78 fd b2 00 00:03:23.323 READ DMA
c8 00 08 3d 74 fc b1 00 00:03:23.314 READ DMA
c8 00 08 3c 70 fb b0 00 00:03:23.304 READ DMA
c8 00 08 3b 6b fa bf 00 00:03:23.285 READ DMA
10 00 3f 00 00 00 b0 00 00:03:23.285 RECALIBRATE [OBS-4]

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]

Device does not support Selective Self Tests/Logging

Gwoli ścisłości: Linux 2.0.x radzi sobie z 2 i więcej procesorami, ale
zdecydowanie lepiej to robi na Sparcach niż Intelach. 2.2.x (i nowsze
2.1) ma już całkiem znośne osiągi...

No wlasnie :-)

--- cut here ---
bash# cat /proc/cpuinfo
cpu : TI UltraSparc II (BlackBird)
fpu : UltraSparc II integrated FPU
promlib : Version 3 Revision 2
prom : 3.2.16
type : sun4u
ncpus probed : 14
ncpus active : 14
Cpu0Bogo : 494.79
Cpu1Bogo : 494.79
Cpu4Bogo : 494.79
Cpu5Bogo : 494.79
Cpu6Bogo : 494.79
Cpu7Bogo : 494.79
Cpu8Bogo : 494.79
Cpu9Bogo : 494.79
Cpu10Bogo : 494.79
Cpu11Bogo : 494.79
Cpu12Bogo : 494.79
Cpu13Bogo : 494.79
Cpu14Bogo : 494.79
Cpu15Bogo : 494.79
MMU Type : Spitfire
State:
CPU0: online
CPU1: online
CPU4: online
CPU5: online
CPU6: online
CPU7: online
CPU8: online
CPU9: online
CPU10: online
CPU11: online
CPU12: online
CPU13: online
CPU14: online
CPU15: online
bash# dmesg
PROMLIB: Sun IEEE Boot Prom 3.2.16 1998/06/08 16:58

snapshot 97
0621 executing gcc version 2.7.2) #3 SMP Mon Dec 7 21:58:03 PST 1998
ARCH: SUN4U
Ethernet address: 08:00:20:9a:71:d5
Found CPU 0 (node=f006f708,mid=0)
Found CPU 1 (node=f006fac8,mid=1)
Found CPU 2 (node=f014f6e4,mid=4)
Found CPU 3 (node=f014faa4,mid=5)
Found CPU 4 (node=f01bf6e4,mid=6)
Found CPU 5 (node=f01bfaa4,mid=7)
Found CPU 6 (node=f022f6e4,mid=8)
Found CPU 7 (node=f022faa4,mid=9)
Found CPU 8 (node=f029f6e4,mid=10)
Found CPU 9 (node=f029faa4,mid=11)
Found CPU 10 (node=f030f6e4,mid=12)
Found CPU 11 (node=f030faa4,mid=13)
Found CPU 12 (node=f037f6e4,mid=14)
Found CPU 13 (node=f037faa4,mid=15)
Found 14 CPU prom device tree node(s).
CENTRAL: Detected 8 slot Enterprise system. cfreg[9e]
FHC(board 0): Version[1] PartID[fa0] Manuf[3e] (CENTRAL)
FHC(board 0): Version[1] PartID[fa0] Manuf[3e] (JTAG Master)
FHC(board 2): Version[1] PartID[fa0] Manuf[3e]
FHC(board 3): Version[1] PartID[fa0] Manuf[3e]
FHC(board 4): Version[1] PartID[fa0] Manuf[3e]
FHC(board 5): Version[1] PartID[fa0] Manuf[3e]
FHC(board 6): Version[1] PartID[fa0] Manuf[3e]
FHC(board 7): Version[1] PartID[fa0] Manuf[3e]
FHC(board 1): Version[1] PartID[fa0] Manuf[3e]
Calibrating delay loop... 494.80 BogoMIPS
Memory: 2059720k available (1600k kernel code, 23528k data, 184k init)
[fffff80
000000000,fffff8007fd1c000]
POSIX conformance testing by UNIFIX
Entering UltraSMPenguin Mode...
Calibrating delay loop... 494.80 BogoMIPS
Calibrating delay loop... 494.80 BogoMIPS
Calibrating delay loop... 494.80 BogoMIPS
Calibrating delay loop... 494.80 BogoMIPS
Calibrating delay loop... 494.80 BogoMIPS
Calibrating delay loop... 494.80 BogoMIPS
Calibrating delay loop... 494.80 BogoMIPS
Calibrating delay loop... 494.80 BogoMIPS
Calibrating delay loop... 494.80 BogoMIPS
Calibrating delay loop... 494.80 BogoMIPS
Calibrating delay loop... 494.80 BogoMIPS
Calibrating delay loop... 494.80 BogoMIPS
Calibrating delay loop... 494.80 BogoMIPS
Calibrating delay loop... 494.80 BogoMIPS
Total of 14 processors activated (6927.16 BogoMIPS).
PCI: Probing for controllers.
PCI: No PCI bus detected
IOMMU(SBUS): IMPL[0] VERS[0] SYSIO mapped at fffff9c600000000
IOMMU: Streaming Buffer IMPL[0] REV[0] ... ENABLED
sbus0: Clock 25.0 MHz
dma0: HME DVMA gate array=20
Linux NET4.0 for Linux 2.1
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
Starting kswapd v 1.5=20
Sparc Zilog8530 serial driver version 1.34
tty00 at 0xf0902004 (irq = 12,339) is a Zilog8530
tty01 at 0xf0902000 (irq = 12,339) is a Zilog8530
tty02 at 0xf0904004 (irq = 12,339) is a Zilog8530
tty03 at 0xf0904000 (irq = 12,339) is a Zilog8530
keyboard: not present
Console: ttyS0 (Zilog8530)
Sun Mouse-Systems mouse driver version 1.00
RAM disk driver initialized: 16 RAM disks of 4096K size
esp0: IRQ 7,db SCSI ID 7 Clk 40MHz CCF=8 TOut 167 NCR53C9XF(espfast)
ESP: Total of 1 ESP hosts found, 1 actually in use.
qpti0: IRQ 7,d3 SCSI ID 7 (Firmware 1.25 96/10/15) [Ultra Wide, using
single en
ded interface]
QPTI: Total of 1 PTI Qlogic/ISP hosts found, 1 actually in use.
scsi0 : Sparc ESP366-HME
scsi1 : PTI Qlogic,ISP SBUS SCSI irq 7,d3 regs at fffff9c720010000
scsi : 2 hosts.
Vendor: EXABYTE Model: EXB-8505SMBANSH2 Rev: 0098
Type: Sequential-Access ANSI SCSI revision: 02
Detected scsi tape st0 at scsi0, channel 0, id 5, lun 0
Vendor: TOSHIBA Model: XM5701TASUN12XCD Rev: 2395
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 6, lun 0
Vendor: SEAGATE Model: ST34501WCSUN4.2G Rev: 0558
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi1, channel 0, id 0, lun 0
Vendor: SEAGATE Model: ST34501WCSUN4.2G Rev: 0558
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdb at scsi1, channel 0, id 1, lun 0
Vendor: SEAGATE Model: ST34501WCSUN4.2G Rev: 0558
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdc at scsi1, channel 0, id 2, lun 0
Vendor: SEAGATE Model: ST34501WCSUN4.2G Rev: 0558
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdd at scsi1, channel 0, id 3, lun 0
Vendor: SEAGATE Model: ST34501WCSUN4.2G Rev: 0558
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sde at scsi1, channel 0, id 8, lun 0
Vendor: SEAGATE Model: ST34501WCSUN4.2G Rev: 0558
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdf at scsi1, channel 0, id 9, lun 0
Vendor: SEAGATE Model: ST34501WCSUN4.2G Rev: 0558
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdg at scsi1, channel 0, id 10, lun 0
Vendor: SEAGATE Model: ST34501WCSUN4.2G Rev: 0558
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdh at scsi1, channel 0, id 11, lun 0
scsi : detected 1 SCSI tape 1 SCSI cdrom 8 SCSI disks total.
esp0: target 6 asynchronous
Uniform CDROM driver Revision: 2.50
Uniform CDROM driver Revision: 2.50
SCSI device sda: hdwr sector= 512 bytes. Sectors= 8385121 [4094 MB]
[4.1 GB]
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 8385121 [4094 MB]
[4.1 GB]
SCSI device sdc: hdwr sector= 512 bytes. Sectors= 8385121 [4094 MB]
[4.1 GB]
SCSI device sdd: hdwr sector= 512 bytes. Sectors= 8385121 [4094 MB]
[4.1 GB]
SCSI device sde: hdwr sector= 512 bytes. Sectors= 8385121 [4094 MB]
[4.1 GB]
SCSI device sdf: hdwr sector= 512 bytes. Sectors= 8385121 [4094 MB]
[4.1 GB]
SCSI device sdg: hdwr sector= 512 bytes. Sectors= 8385121 [4094 MB]
[4.1 GB]
SCSI device sdh: hdwr sector= 512 bytes. Sectors= 8385121 [4094 MB]
[4.1 GB]

eth0: HAPPY MEAL (SBUS) 10/100baseT Ethernet 08:00:20:9a:71:d5=20
Partition check:
sda: sda1 sda2 sda3
sdb: sdb1 sdb3 sdb4 sdb5 sdb6 sdb7 sdb8
sdc: sdc1 sdc3 sdc4 sdc5 sdc6 sdc7 sdc8
sdd: sdd1 sdd2 sdd3 sdd7
sde: sde1 sde3 sde4 sde5 sde6 sde7 sde8
sdf: sdf1 sdf3 sdf4 sdf5 sdf6 sdf7 sdf8
sdg: sdg1 sdg3 sdg4 sdg5 sdg6 sdg7 sdg8
sdh: sdh1 sdh2 sdh3 sdh7
VFS: Mounted root (ext2 filesystem) readonly.
--- cut here ---

Przy synchronizacji wyświetla sie błąd załączony poniżej. Czy fma z k600i ma wyłączoną obsługe kalendarza?

Exception class: EConvertError
Exception message: Format '% ' invalid or incompatible with argument
Exception address: 0040A3E2
----------------------------------------------------------------------------------------------------
Stack list, generated 2006-02-07 12:56:53
[0040A3DD] SysUtils.ConvertErrorFmt + $19
[0040C188] SysUtils.FormatError + $4C
[0040CB81] SysUtils.WideFormatError + $4D
[0040CD97] SysUtils.WideFormatBuf + $1BF
[0040CC7E] SysUtils.WideFormatBuf + $A6
[004059BF] System.@WStrArrayClr + $13
[0043EB6F] TntFormatStrUtils.ReplaceFloatingArgumentsInFormatString (Line 314, "TntFormatStrUtils.pas" + 34) + $59
[0043ED0A] TntSysUtils._Tnt_WideFormatBuf (Line 405, "TntSysUtils.pas" + 11) + $14
[0043ED9B] TntSysUtils._Tnt_WideFmtStr (Line 431, "TntSysUtils.pas" + 3) + $23
[0049CFFB] Controls.TWinControl.DefaultHandler + $D7
[00499E64] Controls.TControl.WndProc + $188
[0049CF17] Controls.TWinControl.WndProc + $157
[004E0B89] TntComCtrls.TTntCustomStatusBar.WndProc (Line 3806, "TntComCtrls.pas" + 16) + $26
[00422B60] Classes.TThreadList.UnlockList + $4
[00448AA4] Graphics.FreeMemoryContexts + $98
[0049CB94] Controls.TWinControl.MainWndProc + $2C
[0049CBA9] Controls.TWinControl.MainWndProc + $41
[0042D000] Classes.StdWndProc + $14
[00499E64] Controls.TControl.WndProc + $188
[004CF1AC] TntControls.TWinControlTrap.Win32Proc (Line 553, "TntControls.pas" + 12) + $19
[0049CF17] Controls.TWinControl.WndProc + $157
[0047E711] ComCtrls.TToolBar.WndProc + $241
[0049D04F] Controls.DoControlMsg + $23
[0049D729] Controls.TWinControl.WMNotify + $D
[00499E64] Controls.TControl.WndProc + $188
[00422B60] Classes.TThreadList.UnlockList + $4
[00448AA4] Graphics.FreeMemoryContexts + $98
[00405973] System.@NewWideString + $7
[00405FAA] System.@WStrSetLength + $3E
[0044156E] TntSystem.Custom_System_WStrFromPCharLen (Line 964, "TntSystem.pas" + 24) + $F
[004415BD] TntSystem.Custom_System_WStrFromPCharLen (Line 974, "TntSystem.pas" + 34) + $1D
[0040276A] System.SysGetMem + $196
[00404C4C] System.@TryFinallyExit + $10
[004026E0] System.SysGetMem + $10C
[00402C32] System.@GetMem + $A
[0040530C] System.@NewAnsiString + $C
[004058EF] System.@LStrSetLength + $57
[00441647] TntSystem.Custom_System_LStrFromPWCharLen (Line 1005, "TntSystem.pas" + 14) + $11
[00405973] System.@NewWideString + $7
[00405FAA] System.@WStrSetLength + $3E
[0044156E] TntSystem.Custom_System_WStrFromPCharLen (Line 964, "TntSystem.pas" + 24) + $F
[004415BD] TntSystem.Custom_System_WStrFromPCharLen (Line 974, "TntSystem.pas" + 34) + $1D
[00410033] SysUtils.GetMonthDayNames + $E7
[00450032] ToolWin.TToolDockObject.DrawDragDockImage + $6
[0044003C] TntWindows.Tnt_FindFirstFileW (Line 627, "TntWindows.pas" + 0) + $8
[00450032] ToolWin.TToolDockObject.DrawDragDockImage + $6
[0049CFFB] Controls.TWinControl.DefaultHandler + $D7
[00499E64] Controls.TControl.WndProc + $188
[00650075] uSelectContact.TfrmSelContact.Get_Sel (Line 378, "uSelectContact.pas" + 16) + $B
[0063005A] Chart.DrawLegendItem + $1A2
[00441520] TntSystem.Custom_System_WStrFromPCharLen (Line 954, "TntSystem.pas" + 14) + $3
[004415BD] TntSystem.Custom_System_WStrFromPCharLen (Line 974, "TntSystem.pas" + 34) + $1D
[00730060] uCrash.TExceptionDialog.CreateReport (Line 482, "uCrash.pas" + 46) + $40
[0063006D] Chart.DrawLegendItem + $1B5
[0049CF17] Controls.TWinControl.WndProc + $157
[0040276A] System.SysGetMem + $196
[004E0B89] TntComCtrls.TTntCustomStatusBar.WndProc (Line 3806, "TntComCtrls.pas" + 16) + $26
[00422B60] Classes.TThreadList.UnlockList + $4
[00448AA4] Graphics.FreeMemoryContexts + $98
[0049CF17] Controls.TWinControl.WndProc + $157
[0054551C] UniTntCtrls.TToolBar.CheckBtnMsg (Line 237, "UniTntCtrls.pas" + 6) + $D
[0047E711] ComCtrls.TToolBar.WndProc + $241
[0054576E] UniTntCtrls.TToolBar.WndProc (Line 309, "UniTntCtrls.pas" + 3) + $4
[00499C34] Controls.TControl.Perform + $24
[0047BBC8] ComCtrls.TToolBar.UpdateItem + $1A0
[0047BBED] ComCtrls.TToolBar.UpdateItem + $1C5
[00441520] TntSystem.Custom_System_WStrFromPCharLen (Line 954, "TntSystem.pas" + 14) + $3
[004415BD] TntSystem.Custom_System_WStrFromPCharLen (Line 974, "TntSystem.pas" + 34) + $1D
[004CF1AC] TntControls.TWinControlTrap.Win32Proc (Line 553, "TntControls.pas" + 12) + $19
[00405973] System.@NewWideString + $7
[00405FAA] System.@WStrSetLength + $3E
[0044156E] TntSystem.Custom_System_WStrFromPCharLen (Line 964, "TntSystem.pas" + 24) + $F
[004415BD] TntSystem.Custom_System_WStrFromPCharLen (Line 974, "TntSystem.pas" + 34) + $1D
[0045003A] ToolWin.TToolDockObject.DrawDragDockImage + $E
[0044003C] TntWindows.Tnt_FindFirstFileW (Line 627, "TntWindows.pas" + 0) + $8
[00450032] ToolWin.TToolDockObject.DrawDragDockImage + $6
[0044003C] TntWindows.Tnt_FindFirstFileW (Line 627, "TntWindows.pas" + 0) + $8
[00450032] ToolWin.TToolDockObject.DrawDragDockImage + $6
[004CF3A4] TntControls.TWinControlTrap.DefWin32Proc (Line 604, "TntControls.pas" + 25) + $19
[0042D000] Classes.StdWndProc + $14
[004059A2] System.@WStrClr + $E
[006F50AE] Unit1.TForm1.HandleMessage (Line 4069, "Unit1.pas" + 114) + $30
[00499E64] Controls.TControl.WndProc + $188
[0040276A] System.SysGetMem + $196
[00404C4C] System.@TryFinallyExit + $10
[004026E0] System.SysGetMem + $10C
[00402919] System.SysFreeMem + $199
[00402941] System.SysFreeMem + $1C1
[00402C5D] System.@FreeMem + $5
[00405258] System.@LStrClr + $1C
[006F5927] Unit1.TForm1.ComPortRxChar (Line 4164, "Unit1.pas" + 17) + $2C
[0049CF17] Controls.TWinControl.WndProc + $157
[004B079D] Forms.TCustomForm.WndProc + $421
[0049CBA9] Controls.TWinControl.MainWndProc + $41
[004CF1AC] TntControls.TWinControlTrap.Win32Proc (Line 553, "TntControls.pas" + 12) + $19
[0042D000] Classes.StdWndProc + $14
[0044003C] TntWindows.Tnt_FindFirstFileW (Line 627, "TntWindows.pas" + 0) + $8
[0045003A] ToolWin.TToolDockObject.DrawDragDockImage + $E
[0044003C] TntWindows.Tnt_FindFirstFileW (Line 627, "TntWindows.pas" + 0) + $8
[0040276A] System.SysGetMem + $196
[00404C4C] System.@TryFinallyExit + $10
[004026E0] System.SysGetMem + $10C
[00402919] System.SysFreeMem + $199
[00402C32] System.@GetMem + $A
[0040530C] System.@NewAnsiString + $C
[00402919] System.SysFreeMem + $199
[00402941] System.SysFreeMem + $1C1
[0043EE26] TntSysUtils.Tnt_WideFmtStr (Line 457, "TntSysUtils.pas" + 1) + $6
[0040D42A] SysUtils.WideFormat + $A
[0057BBEB] uLogger.TLog.AddSynchronizationMessageFmt (Line 288, "uLogger.pas" + 1) + $B
[0057B7C9] uLogger. (Line 185, "uLogger.pas" + 0) + $7D
[0071AABC] Unit1.TForm1.DownloadMessages (Line 12343, "Unit1.pas" + 65) + $67
[0071AB57] Unit1.TForm1.DownloadMessages (Line 12356, "Unit1.pas" + 78) + $13
[006F80C0] Unit1.TForm1.ActionConnectionDownloadExecute (Line 4865, "Unit1.pas" + 16) + $E
[0042C96B] Classes.TBasicAction.Execute + $F
[004BADD9] ActnList.TContainedAction.Execute + $31
[004BBA7B] ActnList.TCustomAction.Execute + $4F
[0042C83F] Classes.TBasicActionLink.Execute + $13
[004A8233] Menus.TMenuItem.Click + $8F
[004A956B] Menus.TMenu.DispatchCommand + $13
[004AA322] Menus.TPopupList.WndProc + $82
[0049CD7D] Controls.TWinControl.IsControlMouseMsg + $51
[0049CF17] Controls.TWinControl.WndProc + $157
[004CE1C9] TntMenus.TTntPopupList.WndProc (Line 1079, "TntMenus.pas" + 33) + $5
[004AA271] Menus.TPopupList.MainWndProc + $1D
[0042D000] Classes.StdWndProc + $14
[00558839] VirtualTrees.TVirtualTreeHintWindow.IsHintMsg (Line 6686, "VirtualTrees.pas" + 6) + $13
[004B6CDF] Forms.TApplication.ProcessMessage + $83
[004B6D16] Forms.TApplication.HandleMessage + $A
[004B6F46] Forms.TApplication.Run + $96
[00731F62] MobileAgent.MobileAgent (Line 111, "C:Projectscvsrootfma_2_2MobileAgent.dpr" + 15) + $2
----------------------------------------------------------------------------------------------------
System : Windows XP Professional, Version: 5.1, Build: A28, "Dodatek Service Pack 2"
Processor: AMD, AMD Athlon(tm) 64 Processor 3000+, 1800 MHz MMX
Display : 1024x768 pixels, 32 bpp
----------------------------------------------------------------------------------------------------
List of loaded modules:
[00400000] D:ProgramyMobile Agent 2.1 beta 3MobileAgent.exe
2.1.2.17 - 2.1.2.17
Mobile Agent
[01590000] D:ProgramyMobile Agent 2.1 beta 3UOLPatch.dll
<00400000> 1.5.3.2 - 1.5.3.2
UOL Patch Routines
[022E0000] D:ProgramyTlen.plhook.dll
<10000000> 1.0.0.1 - 1, 0, 0, 1
Simple Hook
----------------------------------------------------------------------------------------------------
Active Controls hiearchy:
TVirtualStringTree "ExplorerNew"
TTntPanel "PanelExplorer"
TForm1 "Form1"
----------------------------------------------------------------------------------------------------

Cześć,

Jakiś czas temu wpadłem na orginalny nieco pomysł żeby zobaczyć "z debianem co i jak", ściągnęłem wersję dvd testową przez jidigo, i chciałem zainstalować na jednym kompie, doszedłem do momentu gdzie jest wybór partycji, i ... instalator nie widział dysku, i był problem z wyjściem "z tego miejsca", ściągnęłem jeszcze małą płytkę netinstall, ta widziała dysk i partycje, uznałem że coś w instalce było "walnięte" i się nie przejełem, jednak przy uruchamianiu slacka okazało się że dysk nie ma dma i coś z wykrywaniem partycji jest nie tak, kombinowałem, usuwałem wszystkie parytcje, i zakładałem od nowa, ale to nic nie dało. Taśmy itd w kompie mam sprawne, z resztą, na innym kompie jest tak samo. Zainstalowałem nawet windows żeby żobaczyc co on na to, ten jednak ładuje się jak nigdy nic, tyle że dysk jest powolny bo nie ma dma.
Linuksy przy uruchamianiu sypią błędami, no i uruchamiają się baaaardzo długo, próba włączenia dma hdparm-em nic nie daje, (wyłączenia też).
Co z tym fantem zrobić? Dysk to baracuda.
Z dmesg:

hda: ST340016A, ATA DISK drive
blk: queue c03af460, I/O limit 4095Mb (mask 0xffffffff)
hdc: HL-DT-ST DVDRAM GSA-4163B, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 78165360 sectors (40021 MB) w/2048KiB Cache, CHS=4865/255/63, UDMA(100)
Partition check:
hda:<4>hda: dma_timer_expiry: dma status == 0x21
hda: error waiting for DMA
hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }

hda1 hda2 <<4>hda: dma_timer_expiry: dma status == 0x21
hda: error waiting for DMA
hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }

hda5 >
.
.
.
.
hda: dma_timer_expiry: dma status == 0x21
hda: error waiting for DMA
hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }

hda: dma_timer_expiry: dma status == 0x21
hda: error waiting for DMA
hda: dma timeout retry: status=0x58 { DriveReady SeekComplete DataRequest }

Smart:

smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model: ST340016A
Serial Number: 3HS0TR8K
Firmware Version: 3.05
User Capacity: 40,020,664,320 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 5
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon Jul 3 20:46:22 2006 GMT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 422) seconds.
Offline data collection
capabilities: (0x1b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
No Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 31) minutes.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 066 061 034 Pre-fail Always - 97696072
3 Spin_Up_Time 0x0003 085 070 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 736
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 085 060 030 Pre-fail Always - 365810667
9 Power_On_Hours 0x0032 081 081 000 Old_age Always - 16777
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 098 098 020 Old_age Always - 2921
194 Temperature_Celsius 0x0022 042 062 000 Old_age Always - 42
195 Hardware_ECC_Recovered 0x001a 066 061 000 Old_age Always - 97696072
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 018 000 Old_age Always - 302
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0
202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 0

SMART Error Log Version: 1
ATA Error Count: 926 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 926 occurred at disk power-on lifetime: 15326 hours (638 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 04 8c 02 b8 Error: ICRC, ABRT at LBA = 0x08028c04 = 134384644

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 04 8c 02 b8 00 00:03:25.075 READ DMA
c8 00 08 03 88 01 b7 00 00:03:25.070 READ DMA
c8 00 08 02 84 00 b6 00 00:03:25.056 READ DMA
10 00 3f 00 00 00 b0 00 00:03:25.056 RECALIBRATE [OBS-4]
c8 00 08 02 84 00 b6 00 00:03:24.639 READ DMA

Error 925 occurred at disk power-on lifetime: 15326 hours (638 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 02 84 00 b6 Error: ICRC, ABRT at LBA = 0x06008402 = 100697090

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 02 84 00 b6 00 00:03:24.639 READ DMA
c8 00 08 02 84 00 b6 00 00:03:24.209 READ DMA
c8 00 08 01 80 ff b5 00 00:03:24.199 READ DMA
c8 00 08 3f 7c fe b3 00 00:03:24.191 READ DMA
c8 00 08 3e 78 fd b2 00 00:03:24.171 READ DMA

Error 924 occurred at disk power-on lifetime: 15326 hours (638 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 02 84 00 b6 Error: ICRC, ABRT at LBA = 0x06008402 = 100697090

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 02 84 00 b6 00 00:03:24.209 READ DMA
c8 00 08 01 80 ff b5 00 00:03:24.199 READ DMA
c8 00 08 3f 7c fe b3 00 00:03:24.191 READ DMA
c8 00 08 3e 78 fd b2 00 00:03:24.171 READ DMA
10 00 3f 00 00 00 b0 00 00:03:24.171 RECALIBRATE [OBS-4]

Error 923 occurred at disk power-on lifetime: 15326 hours (638 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 3e 78 fd b2 Error: ICRC, ABRT at LBA = 0x02fd783e = 50165822

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 3e 78 fd b2 00 00:03:23.734 READ DMA
c8 00 08 3e 78 fd b2 00 00:03:23.323 READ DMA
c8 00 08 3d 74 fc b1 00 00:03:23.314 READ DMA
c8 00 08 3c 70 fb b0 00 00:03:23.304 READ DMA
c8 00 08 3b 6b fa bf 00 00:03:23.285 READ DMA

Error 922 occurred at disk power-on lifetime: 15326 hours (638 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 00 3e 78 fd b2 Error: ICRC, ABRT at LBA = 0x02fd783e = 50165822

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 08 3e 78 fd b2 00 00:03:23.323 READ DMA
c8 00 08 3d 74 fc b1 00 00:03:23.314 READ DMA
c8 00 08 3c 70 fb b0 00 00:03:23.304 READ DMA
c8 00 08 3b 6b fa bf 00 00:03:23.285 READ DMA
10 00 3f 00 00 00 b0 00 00:03:23.285 RECALIBRATE [OBS-4]

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]

Device does not support Selective Self Tests/Logging

Pozdr.

Jeszcze z ciekawostek, różnica w definicji polskiej wikipedii i obcojęzycznych:

Nacięcie krocza (łac. episiotomia, ang. episiotomy) – zabieg ginekologiczno-położniczy stosowany często podczas porodu siłami natury, polegający na nacięciu nożyczkami ściany pochwy, mięśnia kroczowo-łonowego i poprzecznego powierzchownego krocza, a także skóry, w celu ochrony przed samoczynnym pęknięciem krocza.

Opis metody [edytuj]

Najważniejszym celem nacięcia jest ochrona mięśnia zwieracza zewnętrznego odbytu, którego pęknięcie jest często powikłaniem porodu dużego dziecka lub małej podatności tkanek miękkich. Gojenie naciętych tkanek jest znacznie szybsze i wiąże się z mniejszą ilością powikłań, niż gojenie rozerwanych fragmentów. Dodatkowo, wg niektórych położników, zabieg ten chroni główkę płodu przed gwałtownym rozprężeniem podczas opuszczania dróg rodnych, przez co zmniejsza ryzyko pęknięcia sierpa mózgu u dziecka oraz redukuje częstość innych urazów okołoporodowych (np. porażenie splotu barkowego, złamanie obojczyka). Nacięcie wykonuje się w momencie skrajnego rozciągnięcia tkanek, które objawia się ich zbieleniem. Znieczulenie nie jest konieczne, gdyż niedokrwione i rozciągnięte tkanki nie odbierają bodźców bólowych[potrzebne źródło], chociaż przy planowanym nacięciu krocza możliwe jest wykonanie znieczulenia miejscowego. Najczęściej stosowana linia nacięcia przebiega w kierunku boczno-przyśrodkowym (mniej więcej na godzinie piątej lub siódmej). Nacięcie w tej linii względem cięcia w linii pośrodkowej daje mniejsze ryzyko nacięcia zwieracza odbytu i odbytnicy[1]. Po urodzeniu płodu i popłodu krocze zostaje zszyte.

Wskazania [edytuj]

Najistotniejszymi wskazaniami do nacięcia krocza są następujące sytuacje[2]:

* ostry stan zagrożenia płodu w końcowej fazie porodu
* zagrażające pęknięcie krocza (mało podatne mięśnie kanału rodnego)
* ostry kąt podłonowy
* operacja kleszczowa
* pomoc ręczna
* ułożenie odgięciowe główki
* poród drogami natury dużego płodu
* poród pierwiastki[3]

Wpływ na seksualność [edytuj]

Niektóre położne przyrównują rutynowe wykonywanie nacięcia krocza do okaleczenia narządów płciowych kobiety[4]. W jednym z badań wykazano, że nacięcie krocza powoduje zwiększenie bólu w czasie stosunku i zmniejszenie nawilżania w okresie 12–18 miesięcy po porodzie, ale nie powoduje żadnych problemów z pobudzeniem i osiągnięciem orgazmu[5].

Kontrowersje [edytuj]

15 maja 2008 roku Fundacja Rodzić po Ludzku zainaugurowała ogólnopolską kampanię przeciwko rutynowemu wykonywaniu zabiegu nacięcia krocza "Nie daj się naciąć". Kampania ma na celu: zwrócenie uwagi opinii publicznej na problem rutynowego nacięcia krocza, przełamanie tabu i milczenia wokół problemów i komplikacji będących następstwem tego zabiegu, obalanie mitów przedstawiających zalety nacięcia krocza, informowanie i edukowanie kobiet w ciąży - aby wiedziały, jak przygotować się do porodu, aby uniknąć nacięcia, jakich argumentów używać w rozmowach z personelem medycznym, etc., promowanie dobrych praktyk - placówek, w których nie wykonuje się nacięcia krocza w sposób rutynowy, położnych i lekarzy, którzy podchodzą do rodzących w sposób indywidualny, zaapelowanie do środowiska medycznego, aby w Polsce ograniczono wykonywanie nacięcia krocza oraz zwracano większą uwagę na prawa i potrzeby rodzącej[6].

An episiotomy is a surgical incision through the perineum made to enlarge the vagina and assist childbirth. The incision can be midline or at an angle from the posterior end of the vulva, is performed under local anaesthetic (pudendal anesthesia) and is sutured closed after delivery. It is one of the most common medical procedures performed on women, and although its routine use in childbirth has steadily declined in recent decades, it is still widely practiced in Latin America and in Poland and India.

[edit] Uses

The primary rationale behind an episiotomy is related to the nature rather than the size of the tear. Many physicians use episiotomies because they believe that it will lessen perineal trauma, minimize postpartum pelvic floor dysfunction by reducing anal sphincter muscle damage, reduce the loss of blood at delivery, and protect against neonatal trauma. In many cases though, episiotomies cause all of these problems.[1] Research has shown that natural tears typically are less severe (although this is perhaps not surprising since epistiotomy is designed for when natural tearing will cause significant risks/trauma)

Slow delivery of the head, in between contractions will result in the least perineal damage.[2]

Episiotomy is indicated if:

* the baby's shoulders are stuck (Shoulder Dystocia) a bony association, though the episiotomy does not resolve this problem, it allows the operator more room to perform maneuvers to free shoulder from the pelvis.
* There is a serious risk to the mother of second or third degree tearing
* In some cases where a caesearean is not indicated but delivery is adversely affected
* 'Natural' tearing will cause an increased risk of maternal disease being vertically transmitted
* Routine episiotomy is NOT indicated in evidence based practice
* Large baby
* rigid perineal muscles
* When instrumental delivery is indicated
* When a woman has undergone FGM (female genital mutilation) an anterior and or mediolateral episiotomy may be indicated.
* Prolonged late decelerations or fetal bradycardia during active pushing

[edit] Controversy about common usage

In various countries, routine episiotomy has been accepted medical practice for many years. Since about the 1960s, routine episiotomies have been rapidly losing popularity among obstetricians and midwives in Europe, Australia and the United States. A nationwide US population study[3] suggested that 31% of women having babies in U.S. hospitals received episiotomies in 1997, compared with 56% in 1979. In Latin America it remains popular, and is performed in 90% of hospital births,[4] in most cases without the mother's consent. There, routine episiotomy is a major cause of infections, some of them fatal.[5]

Recent studies indicate that routine episiotomies should not be performed, as they increase morbidity. This procedure is not helpful for routine patients[6] Having an episiotomy may increase perineal pain in the postpartum period, resulting in trouble defecating, particularly in midline episiotomies [7]. In addition it may complicate sexual intercourse by making it painful [8] and replacing erectile tissues in the vulva with fibrotic tissue.

In cases where an episiotomy is indicated, a mediolateral incision may be preferable to a median (midline) incision as the latter is associated with a higher risk of injury to the anal sphincter and the rectum[9].

[edit] Impacts on sexual intercourse

Some midwives compare routine episiotomy to female circumcision.[10] One study found that women who underwent episiotomy reported more painful intercourse and insufficient lubrication 12-18 months after birth, but did not find any problems with orgasm or arousal.[11]

[edit] Avoidance

Controlled delivery of the head that allows slow gradual stretching of the perineal tissue can help in minimising damage to the perineum.

Perineal massage beginning around the 34th week has been shown to reduce perineal damage by 6%[12].

A perineal dilator can be used to stretch the perineal tissue gradually and train it in preparation for first births. The "Epi-no Birth Trainer" consists of a small inflatable silicone balloon pumped with the same pump as a sphygmomanometer. The Epi-no device has been shown to reduce perineal damage by 50% at first births[13].

L'épisiotomie est un acte chirurgical consistant à ouvrir le périnée au moment de l'accouchement afin de laisser passer l'enfant. Cette incision a idéalement pour but de sectionner le muscle releveur de l'anus.

La pratique de l'épisiotomie est un geste prophylactique utilisé depuis le XVIIIe siècle et actuellement largement répandu. Les chiffres de 2002-2003 en France indiquent que 47,3% des femmes qui ont accouché par les voies naturelles ont eu une épisiotomie (68 % chez la primipare et 31 % chez la multipare).

Les bénéfices supposés de ce geste sont démentis par la recherche scientifique depuis plusieurs décennies. En France, c'est en 2005 que le Collège national des gynécologues et obstétriciens français (CNGOF) a rendu public le résultat de son travail sur l'analyse des données scientifiques disponibles sur l'épisiotomie[1] [pdf] Lire le résumé des Recommandations de pratique clinique.

Les bénéfices anciennement espérés de l'épisiotomie [modifier]

L'épisiotomie était censée prévenir des déchirures graves du périnée. La recherche montre que non seulement la pratique systématique de l'épisiotomie ne permet pas de réduire les déchirures du 3e ou 4e degré, mais que dans certains cas, le résultat est inverse de celui escompté.

De même, on pratiquait l'épisiotomie en espérant diminuer les incontinences urinaires ou fécales. La recherche a démontré qu'il n'en est rien, et qu'elle est même associée à plus d'incontinence fécale dans les 3 mois après l'accouchement.

La prévention du prolapsus génital par l'épisiotomie n'est pas démontré, car aucune étude médicale ne porte sur une période de temps assez longue pour le vérifier. On sait juste que la force musculaire du périnée est moindre, trois mois après l'accouchement, chez les femmes ayant eu une épisiotomie.

Les grands bénéfices espérés de l'épisiotomie sont donc invalidés par les études médicales.

Les autres indications de l'épisiotomie dans des cas particuliers [modifier]

* Les extractions instrumentales, c'est-à-dire par ventouses ou forceps : la recherche montre qu'il n'y a pas lieu d'effectuer systématiquement une épisiotomie dans ces cas, d'autant plus que taux de lésions périnéales graves est augmenté s'il y a une épisiotomie lors d'une extraction instrumentale. Les professionnels ajoutent néanmoins que les conditions qui ont mené à décider d'une extraction instrumentales peuvent justifier une épisiotomie dans ce cas.

* Les manœuvres obstétricales (extraction d'un second jumeau, dystocie des épaules), la macrosomie (gros bébé), les présentations non classiques du fœtus (en siège, par la face...), la prématurité : il n'y a pas de preuves pour recommander ou non la pratique de l'épisiotomie dans ces cas. Il semble cependant logique que l'obstétricien puisse être amené à pratiquer l'épisiotomie pour faciliter les manœuvres. Certaines études observent des taux d'épisiotomie bien en dessous des 100% pour des présentations non classiques du fœtus (par exemple, 30% d'épisiotomies en cas de siège complet, dans une étude française de 2005).

* Les périnées à risques : le seul type de périnée dit "à risques" qui justifierait, selon la recherche, la pratique de l'épisiotomie est le périnée court, défini comme une distance fourchette-centre de l’anus inférieur ou égal à 3 cm. Pour les périnées cicatriciels (antécédents de lésions périnéales de haut degré), il y a un fort taux de récidive (l'accouchement par voie basse doit donc être discuté) mais l'épisiotomie ne protège pas contre ce risque.

* L'état fœtal non rassurant : la réalisation d'épisiotomies dans ce cas n'améliore pas les résultats néonatals, selon les chercheurs. Cependant, les professionnels peuvent être amenés à réaliser l'épisiotomie s'il faut réduire le temps de l'expulsion.

* La nulliparité : les études arrivent toute à la conclusion que la naissance d'un premier bébé ne justifie pas une épisiotomie systématique.

Techniques de réalisation : types d'épisiotomie, analgésie, suture [modifier]

Types d'épisiotomie [modifier]

* Épisiotomie médiane : incision de la fourchette vulvaire directement vers l'anus sur environ 4 cm. Bien qu'elle soit encore fréquente dans les pays anglo-saxons, on sait qu'elle crée une zone de faiblesse médiane qui peut filer vers le bas et provoquer une rupture du sphincter anal dans près de 20 % des cas.
* Épisiotomie médio-latérale : incision qui est illustrée sur le dessin de l'article. C'est la plus pratiquée en France. L'incision doit partir de la partie médiane de la fourchette et en se diriger latéralement et en dehors vers la région ischiatique (soit un angle de 45° par rapport à la verticale) sur six centimètres en moyenne.
* Autres types d'épisiotomie totalement abandonnés : épisiotomies bilatérales, épisiotomies à multiples incisions radiées, épisiotomies latérales qui augmentaient significativement le risque d'une lésion des glandes de Bartholin au moment de l'incision.

Zauważcie, że "poród pierwiastki" jest wskazaniem do epizjotomii tylko w wersji polskiej.
W innych wersjach językowej pisze się o epizjotomii jako o procedurze, od rutynowego wykonywania której się odchodzi, w polskiej - to jak najbardziej standard. Kiedy wreszcie nadgonimy Europę?