Schlagwort-Archive: *NIX

unter (Arch)Linux ein Intel ICH8R Raid zum laufen bringen [update 1]

Allgemein,

Hardware: 

  • RAID bus controller: Intel Corporation 82801HR/HO/HH (ICH8R/DO/DH) SATA RAID Controller (rev 02)
  • 2x Western Digital 
    WDC WD2500YD

auf ’nem Asus P5B Deluxe.

[root@weltzerstoerung /]# dmraid -s -vvd
NOTICE: skipping removable device /dev/sdd
NOTICE: skipping removable device /dev/hdd
NOTICE: /dev/hda: asr     discovering
NOTICE: /dev/hda: ddf1    discovering
NOTICE: /dev/hda: hpt37x  discovering
NOTICE: /dev/hda: hpt45x  discovering
NOTICE: /dev/hda: isw     discovering
NOTICE: /dev/hda: jmicron discovering
NOTICE: /dev/hda: lsi     discovering
NOTICE: /dev/hda: nvidia  discovering
NOTICE: /dev/hda: pdc     discovering
NOTICE: /dev/hda: sil     discovering
NOTICE: /dev/hda: via     discovering
NOTICE: /dev/hdb: asr     discovering
NOTICE: /dev/hdb: ddf1    discovering
NOTICE: /dev/hdb: hpt37x  discovering
NOTICE: /dev/hdb: hpt45x  discovering
NOTICE: /dev/hdb: isw     discovering
NOTICE: /dev/hdb: jmicron discovering
NOTICE: /dev/hdb: lsi     discovering
NOTICE: /dev/hdb: nvidia  discovering
NOTICE: /dev/hdb: pdc     discovering
NOTICE: /dev/hdb: sil     discovering
NOTICE: /dev/hdb: via     discovering
NOTICE: /dev/sda: asr     discovering
NOTICE: /dev/sda: ddf1    discovering
NOTICE: /dev/sda: hpt37x  discovering
NOTICE: /dev/sda: hpt45x  discovering
NOTICE: /dev/sda: isw     discovering
NOTICE: /dev/sda: isw metadata discovered
NOTICE: /dev/sda: jmicron discovering
NOTICE: /dev/sda: lsi     discovering
NOTICE: /dev/sda: nvidia  discovering
NOTICE: /dev/sda: pdc     discovering
NOTICE: /dev/sda: sil     discovering
NOTICE: /dev/sda: via     discovering
NOTICE: /dev/sdb: asr     discovering
NOTICE: /dev/sdb: ddf1    discovering
NOTICE: /dev/sdb: hpt37x  discovering
NOTICE: /dev/sdb: hpt45x  discovering
NOTICE: /dev/sdb: isw     discovering
NOTICE: /dev/sdb: isw metadata discovered
NOTICE: /dev/sdb: jmicron discovering
NOTICE: /dev/sdb: lsi     discovering
NOTICE: /dev/sdb: nvidia  discovering
NOTICE: /dev/sdb: pdc     discovering
NOTICE: /dev/sdb: sil     discovering
NOTICE: /dev/sdb: via     discovering
NOTICE: /dev/sdc: asr     discovering
NOTICE: /dev/sdc: ddf1    discovering
NOTICE: /dev/sdc: hpt37x  discovering
NOTICE: /dev/sdc: hpt45x  discovering
NOTICE: /dev/sdc: isw     discovering
NOTICE: /dev/sdc: jmicron discovering
NOTICE: /dev/sdc: lsi     discovering
NOTICE: /dev/sdc: nvidia  discovering
NOTICE: /dev/sdc: pdc     discovering
NOTICE: /dev/sdc: sil     discovering
NOTICE: /dev/sdc: via     discovering
DEBUG: _find_set: searching isw_ebdgbigaaf
DEBUG: _find_set: not found isw_ebdgbigaaf
DEBUG: _find_set: searching isw_ebdgbigaaf_raid0.sys
DEBUG: _find_set: searching isw_ebdgbigaaf_raid0.sys
DEBUG: _find_set: not found isw_ebdgbigaaf_raid0.sys
DEBUG: _find_set: not found isw_ebdgbigaaf_raid0.sys
NOTICE: added /dev/sda to RAID set "isw_ebdgbigaaf"
DEBUG: _find_set: searching isw_ebdgbigaaf
DEBUG: _find_set: found isw_ebdgbigaaf
DEBUG: _find_set: searching isw_ebdgbigaaf_raid0.sys
DEBUG: _find_set: searching isw_ebdgbigaaf_raid0.sys
DEBUG: _find_set: found isw_ebdgbigaaf_raid0.sys
DEBUG: _find_set: found isw_ebdgbigaaf_raid0.sys
NOTICE: added /dev/sdb to RAID set "isw_ebdgbigaaf"
DEBUG: checking isw device "/dev/sda"
DEBUG: checking isw device "/dev/sdb"
DEBUG: set status of set "isw_ebdgbigaaf_raid0.sys" to 16
DEBUG: set status of set "isw_ebdgbigaaf" to 16
*** Group superset isw_ebdgbigaaf
--> Subset
name   : isw_ebdgbigaaf_raid0.sys
size   : 980460032
stride : 256
type   : stripe
status : ok
subsets: 0
devs   : 2
spares : 0
DEBUG: freeing devices of RAID set "isw_ebdgbigaaf_raid0.sys"
DEBUG: freeing device "isw_ebdgbigaaf_raid0.sys", path "/dev/sda"
DEBUG: freeing device "isw_ebdgbigaaf_raid0.sys", path "/dev/sdb"
DEBUG: freeing devices of RAID set "isw_ebdgbigaaf"
DEBUG: freeing device "isw_ebdgbigaaf", path "/dev/sda"
DEBUG: freeing device "isw_ebdgbigaaf", path "/dev/sdb"

wir sehen dass 

type   : stripe

ist.

dann via 

[root@weltzerstoerung /]# mdadm --create /dev/md0 -l stripe -n2 /dev/sda /dev/sdb
mdadm: array /dev/md0 started.

ein mdX device erzeugen was aus zwei g’stripe’ten platten besteht.

Rückfragen sind erwünscht.
// i am also speaking english, please use the comments :)

update1:

[root@weltzerstoerung /]# mdadm --detail /dev/md0
/dev/md0:
       Version : 00.90.03
 Creation Time : Sun Feb 25 17:45:24 2007
    Raid Level : raid0
    Array Size : 490234624 (467.52 GiB 502.00 GB)
  Raid Devices : 2
 Total Devices : 2
Preferred Minor : 0
   Persistence : Superblock is persistent

   Update Time : Sun Feb 25 19:55:33 2007
         State : active
Active Devices : 2
Working Devices : 2
Failed Devices : 0
 Spare Devices : 0

    Chunk Size : 64K

          UUID : a7dc0fa0:0681ac11:0fc4577a:d30e7155
        Events : 0.3

   Number   Major   Minor   RaidDevice State
      0       8        0        0      active sync   /dev/sda
      1       8       16        1      active sync   /dev/sdb

das Raid lauft so weit, ich komme allerdings nicht an die Partitionen ‚ran:

[root@weltzerstoerung /]# fdisk /dev/md0 -l

Disk /dev/md0: 502.0 GB, 502000254976 bytes
255 heads, 63 sectors/track, 61031 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

  Device Boot      Start         End      Blocks   Id  System
/dev/md0p1   *           1        5099    40957686    7  HPFS/NTFS
/dev/md0p2            5100       17847   102398310    f  W95 Ext'd (LBA)
/dev/md0p3           17848       37650   159067597+  83  Linux
/dev/md0p4           37651       61029   187791817+   7  HPFS/NTFS
/dev/md0p5            5100       17847   102398278+   7  HPFS/NTFS
[root@weltzerstoerung /]# ls /dev/|grep md
md
md0

canonical evil?

pirastlog, , , , , ,

As CNR ships proprietary software, does it use DRM? Is CNR going to be shipped by default in Ubuntu?

For me, those would be real killer-arguments against Ubuntu and Canonical. I mean, Canonical has the right to make money with Ubuntu but then they should please do so supporting or selling Ubuntu and not integrating third party applications.

The question that I ask myself is: „Is Canonical evil?“

I mean,
* Launchpad is closed source in order to compete with Red Hat and other Linux vendors [1]
* Mark does a lot of FUD against Red Hat, who contribute a lot to the FOSS community (also on the upstream side) which Canonical does not do.
Ubuntu kills Debian by taking it’s packages to universe, modifying them and not contributing back (there would be other ways fixing bugs in Universe, for example, fixing bugs in Debian and then syncing).
* Rosetta destroys upstream translations: Some nice users think “Hey, let’s translate this application / change some string” and translate it using Rosetta. The translations do not have any quality and upstream does not receive the changes. In most cases, Ubuntu gets bad translations. Yes, I already posted that and a possible “fix” to Rosetta-users ML.
* Dapper-commercial: Canonical surely gets money for doing d-c and not few. It fears me that one single company can say “Hey, let’s make a dapper-commercial repository and let’s ask our developers to modify gnome-app-install in a stable release so that it automatically adds a new repository on Canonical server”.

This and some things that I can’t remember are the reasons for not contributing to Ubuntu anymore on the side of fixing bugs. Though, I will still use it as my OS, since it is the best one I ever used. I think that since Canonical is the financier of Ubuntu, they can drive it the way they want. But it does not strength the trust me (maybe the community) if they do such things.

[1] http://charismacode.blogspot.com/2007/01/powers-and-repositories-ubuntu-and.html Over time, it will be open sourced. Right now we compete with Progeny and Red Hat and other companies, so we need to have a unique offering to do so effectively, and that’s Launchpad.

[2] http://www.markshuttleworth.com/archives/77

Some links about that:
http://forums.lugradio.org/viewtopic.php?t=2271&view=previous
http://geekz.co.uk/lovesraymond/archive/cancomical-lynchpad
http://azure.humbug.org.au/~aj/blog/2005/09/04
http://charismacode.blogspot.com/2007/01/powers-and-repositories-ubuntu-and.html

ergänzung zu css unter linux: half life 2 unter linux

pirastlog, ,

half life 2 läuft auch erstaunlich problemlos unter linux mit wine, so lange man wieder mit WINEDEBUG=-all startet und – ganz wichtig – unbedingt bei den startoptionen -dxlevel 70 angibt. sonst hat man im spiel nur ein schwarzes bild.

nicht aufgeben, beim intro beim ersten level ( munter ans werk dr. freeman blablabla ) kommt kein bild. einfach abwarten, wenn es losgeht gibt es auch ein bild.

counter strike source unter linux

pirastlog, , ,

der weihnachtsmann hat zugeschlagen.

vor einiger zeit habe ich mal versucht, source unter linux zum laufen zu bringen.. das ist meißtens an zu lahmer grafik gescheitert.

heute habe ich dann die neue wine version, 0.9.28, installiert.

in der changelog steht nichts besonderes aber irgendwo gibts eine tolle änderung: directx anwendungen laufen wieder im vollbildmodus.

also habe ich mir gedacht, dass ich ja mal wieder counter strike source unter linux ausprobieren könnte.

gesagt, getan:

ich wechselte in das steam verzeichnis und startete steam mit

WINEDEBUG=-all wine steam

warum WINEDEBUG=-all? es gab bei source – jedenfalls bei älteren wine versionen – so viele konsolenausgaben, dass das spiel unerträglich langsam wurde.

dann habe ich bei den startoptionen noch

-dxlevel 70

gesetzt. das macht die grafik zwar schlechter, erhöht dafür aber deren performance aber immens.

anschl. musste ich nur noch counter strike starten und steam schnell per x minimieren – sonst bleibt steam vor counter strike source im vordergrund – und schon konnte der spielspaß beginnen :-)