User:Mueller
From KIP Wiki
⧟kip-jumptonavigation⧽⧟kip-jumptosearch⧽
ACL on Ext2/3
- mit Option
acl
mounten:mount -o remount,acl /
- fĂźr dauerhafte Nutzung:
sed 's/\(ext3\s\+\)/\1acl,/' /etc/fstab | diff /etc/fstab -
und das patchen :). apt-get install acl
getfacl
undsetfacl
benutzensetfacl -m u:huffna:r file
gibt Benutzer huffna Leserechte- Achtung: Im Gegensatz zu AFS unterstĂźtzt Ext3-ACL auch fĂźr einzelne Dateien ACLs.
Aufsetzen von Evolver13 (Ubuntu 7.10 Beta i386)
Allgemeine Dienste
- ldap Ăźber auth-client => ganz isi
- autofs mit autofs config von evolver12
Windriver (9.01) fĂźr Darkwing
- in redist/linux_wrappers.c: pci_register_driver() statt pci_module_init()
- Packages: linux-headers-generic linux-source fĂźr "make prepare" Informationen bzw. modpost (=> postprocess module symbol versions :))
- in redist/configure aufrufen (nicht von unten make => versemmelt config)
- in redist/ make install => fertig
- chgrp F9_remote /dev/windrvr6; chmod 664 /dev/windrvr6
- in
/etc/udev/rules.d/40-permissions.rules
anhängen:
# Windriver is very old... wrong register ACTION=="add", DEVPATH=="/bus/pci/drivers/windrvr6_pci", RUN+="/lib/mk_windrvr6.sh" ACTION=="remove", DEVPATH=="/bus/pci/drivers/windrvr6_pci", RUN+="/lib/mk_windrvr6.sh"
- dazu
/lib/mk_windrvr6.sh
:
#! /bin/bash if [ "$ACTION" == "add" ]; then major=`grep -w windrvr6 /proc/devices | cut -f1 -d" "` mknod /dev/windrvr6 c $major 0 chgrp 1009 /dev/windrvr6 chmod 664 /dev/windrvr6 fi if [ "$ACTION" == "remove" ]; then rm /dev/windrvr6 fi
NEST (1.0.13)
export CXX=`which g++`
export CC=`which gcc`
../nest-1.0.13/configure
make
PyNEST 20070419
python setup.py build
PyGSL
python setup.py build
python setup.py install
Hardware
- EPROM falsches Image
- ein Jumper falsche Position => falscher Nathanslot aktiviert
config_darkwing darkwing.bit 40
(oderdarkwing_sctrl3.bit
?)config_nathan nathan_top_spikey_ext_clk2_fastsdram.bit 2
config_darkwing darkwing.bit 60
(oderdarkwing_sctrl3.bit
?)dinit -r
Computerzeug, das auch noch erledigt werden will
- NĂX
Notizen
Erklärungsbedßrftige Meldungen des dwserver
[...]
sctrl.cpp:Exec(): Error at command 0x1, nathan 3, module 0
sctrl.cpp:Exec(): Error at command 0x1, nathan 3, module 0
sctrl.cpp:Exec(): Error at command 0x1, nathan 3, module 0
sctrl.cpp:Exec(): max retries on error reached, giving up
[...]
mutex.cpp:Wait(): Mutex Error: 110 ( = Wait timed out)
hawai.cpp:Wait(): detected FPGA IRQ timeout with pending FPGA IRQ, exiting normally...
mutex.cpp:Wait(): Mutex Error: 110 ( = Wait timed out)
hawai.cpp:Wait(): detected FPGA IRQ timeout with pending FPGA IRQ, exiting normally...
mutex.cpp:Wait(): Mutex Error: 110 ( = Wait timed out)
hawai.cpp:Wait(): detected FPGA IRQ timeout with pending FPGA IRQ, exiting normally...
msgqueue.c: Could not send message: Invalid argument
Performed 48 k read transactions so far.
MerkwĂźrdige Kernel Meldungen
[...]
MMM dd 06:66:00 prozac kernel: [666666.666666] ACPI: PCI interrupt for device 0000:05:00.0 disabled
MMM dd 06:66:00 prozac kernel: [666666.666667] ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 20 (level, low) -> IRQ 23
MMM dd 06:66:00 prozac kernel: [666666.666668] ACPI: PCI interrupt for device 0000:05:00.0 disabled
MMM dd 06:66:00 prozac kernel: [666666.666669] ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 20 (level, low) -> IRQ 23
oder auch:
MMM dd 06:66:00 prozac kernel: [666000.666000] irq 23: nobody cared (try booting with the "irqpoll" option)
MMM dd 06:66:00 prozac kernel: [666000.666000] [__report_bad_irq+36/128] __report_bad_irq+0x24/0x80
MMM dd 06:66:00 prozac kernel: [666000.666000] [note_interrupt+610/672] note_interrupt+0x262/0x2a0
MMM dd 06:66:00 prozac kernel: [666000.666000] [<f8a7dee5>] intr_handler+0xa5/0xc0 [windrvr6]
MMM dd 06:66:00 prozac kernel: [666000.666000] [<f8a79064>] wrapper_handler+0x13/0x20 [windrvr6]
MMM dd 06:66:00 prozac kernel: [666000.666000] [handle_IRQ_event+48/96] handle_IRQ_event+0x30/0x60
MMM dd 06:66:00 prozac kernel: [666000.666000] [handle_fasteoi_irq+187/240] handle_fasteoi_irq+0xbb/0xf0
MMM dd 06:66:00 prozac kernel: [666000.666000] [do_IRQ+59/112] do_IRQ+0x3b/0x70
MMM dd 06:66:00 prozac kernel: [666000.666000] [common_interrupt+35/48] common_interrupt+0x23/0x30
MMM dd 06:66:00 prozac kernel: [666000.666000] [mwait_idle_with_hints+70/96] mwait_idle_with_hints+0x46/0x60
MMM dd 06:66:00 prozac kernel: [666000.666000] [mwait_idle+0/32] mwait_idle+0x0/0x20
MMM dd 06:66:00 prozac kernel: [666000.666000] [cpu_idle+83/224] cpu_idle+0x53/0xe0
MMM dd 06:66:00 prozac kernel: [666000.666000] =======================
MMM dd 06:66:00 prozac kernel: [666000.666000] handlers:
MMM dd 06:66:00 prozac kernel: [666000.666000] [<f8a79051>] (wrapper_handler+0x0/0x20 [windrvr6])
MMM dd 06:66:00 prozac kernel: [666000.666000] Disabling IRQ #23
Hawai Objekt und dergleichen aka zwei DWs in einem Rechner
- Bisher: LockUp des Hostrechners durch unfertigen PCI-Cycle?
- Probieren:
- * PCI Extenderkarte (zum Abschalten des Gerätes) oder PCI Timeout setzen (setpci?)
- * Wird im Hawai-Objekt ein Lock ignoriert, und evtl. doppelt "zugegriffen" auf die gleiche Karte?
Datenformat von read_sram
auf Spikey2
linker Block | rechter Block | ||||
---|---|---|---|---|---|
2 | 1 | 0 | 3 | 4 | 5 |
nb 0 | nb 1 | ||||
23:12 | nb 11:0 | ||||
23:20 | 19:16 | 15:12 | 3:0 | 7:4 | 11:8 |
Empfangene Datenreihenfolge: 2,1,0|5,4,3