Fab notes
Aus Fedorawiki.de
Auf dieser Seite sind Informations-Fragmente zwischen gelagert, welche viele mal einen Artikel geben.
Inhaltsverzeichnis |
Automatisches Gnome-Login
Damit GDM Autologin unterstüzt muss, folgende Datei angepasst werden
nano -w /etc/gdm/custom.conf
Folgende Zeilen müssen im [daemon] Bereich eingefügt oder geändert werden.
[daemon] AutomaticLoginEnable=true AutomaticLogin=user01 TimedLoginDelay=5
Anlegen der $HOME/.xsession Datei
touch ~/user01/.xsession
Nun können die Eintagungen gemacht werden, respektive bestimmt werden, was gestartet wird.
#!/bin/bash metacity & xterm &
ausführbar machen
chmod +x /home/user01/.xsession
Fedora 7
In Fedora 7 Test 3 funktioniert es mit dem System -> Administration -> Anmeldebildschirm, ohne Änderungen von /etc/gdm/custom.conf.
[root]# gdmsetup
oder
System -> Administration -> Anmeldebildschirm
lm_sensors
lm_sensors dient zum Auslesen von CPU- und Mainboard-Temperatur, Lüfterdrehzahlen und Netzteilspannungen. Diese Werte können dann von Gdesklets, SuperKaramba Gkrellm2 oder Conky auf dem Desktop dargestellt werden.
Installation
Die Installation ist mit yum, pirut oder yumex schnell erledigt.
[root]# yum install lm-sensors
Konfiguration
Nun muss sensors-detect ausgeführt werden. Alle Fragen sind mit Yes zu beantworten, ausser das System besitzt sehr spezielle Hardware.
[root]# sensors-detect
Der Durchlauf auf einem Dell Latitude D610 bringt die Ernüchterung.
# sensors-detect revision 4271 (2006-12-26 03:53:20 -0800) 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. We can start with probing for (PCI) I2C or SMBus adapters. Do you want to probe now? (YES/no): Probing for PCI bus adapters... Sorry, no known PCI bus adapters found. We will now try to load each adapter module in turn. If you have undetectable or unsupported adapters, you can have them scanned by manually loading the modules before running this script. To continue, we need module `i2c-dev' to be loaded. Do you want to load `i2c-dev' now? (YES/no): Module loaded successfully. We are now going to do the I2C/SMBus adapter probings. Some chips may be double detected; we choose the one with the highest confidence value in that case. If you found that the adapter hung after probing a certain address, you can specify that address to remain unprobed. Some chips are also 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): Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM78-J' 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 Probing for `Winbond W83627HF' at 0x290... No Probing for `Silicon Integrated Systems SIS5595'... No Probing for `VIA VT82C686 Integrated Sensors'... No Probing for `VIA VT8231 Integrated Sensors'... No Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some Super I/O chips may also contain 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): Probing for Super-I/O at 0x2e/0x2f Trying family `ITE'... Yes Found unknown chip with ID 0x1d01 Trying family `National Semiconductor'... No Trying family `SMSC'... Yes Found unknown chip with ID 0x1d01 Trying family `VIA/Winbond/Fintek'... No Probing for Super-I/O at 0x4e/0x4f Trying family `ITE'... No Trying family `National Semiconductor'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Fintek'... No Some CPUs or memory controllers may also contain embedded sensors. Do you want to scan for them? (YES/no): AMD K8 thermal sensors... No Intel Core family thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Sorry, no sensors were detected. Either your sensors are not supported, or they are connected to an I2C or SMBus adapter that is not supported. See doc/FAQ, doc/lm_sensors-FAQ.html or http://www.lm-sensors.org/wiki/FAQ (FAQ #4.24.3) for further information. If you find out what chips are on your board, check http://www.lm-sensors.org/wiki/Devices for driver status.
"Sorry, no sensors were detected." ist die lapidare Ausgabe. Auf einem Desktop-System sieht es aber anders aus. Hier nun die Ausgabe eines Dell Optiplex GX110. Die ensprechenden Teile zum Errgänzen in allen Dateien sind speziell markiert.
# sensors-detect revision 4171 (2006-09-24 03:37:01 -0700)
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.
We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-i801' for device 0000:00:1f.3: Intel 82801AA ICH
Use driver `i2c-i810' for device 0000:00:01.0: Intel 82810E GMCH
We will now try to load each adapter module in turn.
Module `i2c-i801' already loaded.
Module `i2c-i810' already loaded.
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.
To continue, we need module `i2c-dev' to be loaded.
Do you want to load `i2c-dev' now? (YES/no):
Module loaded successfully.
We are now going to do the I2C/SMBus adapter probings. Some chips may
be double detected; we choose the one with the highest confidence
value in that case.
If you found that the adapter hung after probing a certain address,
you can specify that address to remain unprobed.
Next adapter: bt878 #0 [sw]
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Handled by driver `tveeprom' (already loaded), chip type `tveeprom'
(note: this is probably NOT a sensor chip!)
Client found at address 0x61
Handled by driver `tuner' (already loaded), chip type `Philips PAL_BG (FI1216 and compatibles)'
(note: this is probably NOT a sensor chip!)
Next adapter: SMBus I801 adapter at dcd0
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Probing for `EDID EEPROM'... No
Probing for `Maxim MAX6900'... No
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Client found at address 0x69
Next adapter: I810/I815 DDC Adapter
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Success!
(confidence 1, driver `eeprom')
Probing for `EDID EEPROM'... Success!
(confidence 8, driver `eeprom'), other addresses: 0x51 0x52 0x53 0x54 0x55 0x56 0x57
Probing for `Maxim MAX6900'... No
Next adapter: I810/I815 I2C Adapter
Do you want to scan it? (YES/no/selectively):
Some chips are also 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):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM78-J' 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
Probing for `Winbond W83627HF' at 0x290... No
Probing for `Silicon Integrated Systems SIS5595'... No
Probing for `VIA VT82C686 Integrated Sensors'... No
Probing for `VIA VT8231 Integrated Sensors'... No
Probing for `AMD K8 thermal sensors'... No
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No
Some Super I/O chips may also contain 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):
Probing for Super-I/O at 0x2e/0x2f
Trying family `ITE'... Yes
Found unknown chip with ID 0xe411
Trying family `National Semiconductor'... Yes
Found `Nat. Semi. PC87364 Super IO Fan Sensors'
(but not activated)
Trying family `SMSC'... Yes
Found unknown chip with ID 0xe411
Trying family `VIA/Winbond/Fintek'... Yes
Found unknown chip with ID 0xe411
Probing for Super-I/O at 0x4e/0x4f
Trying family `ITE'... No
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `eeprom' (should be inserted):
Detects correctly:
* Bus `SMBus I801 adapter at dcd0'
Busdriver `i2c-i801', I2C address 0x50
Chip `SPD EEPROM' (confidence: 8)
* Bus `SMBus I801 adapter at dcd0'
Busdriver `i2c-i801', I2C address 0x51
Chip `SPD EEPROM' (confidence: 8)
* Bus `I810/I815 DDC Adapter'
Busdriver `i2c-i810', I2C address 0x50 (and 0x51 0x52 0x53 0x54 0x55 0x56 0x57)
Chip `EDID EEPROM' (confidence: 8)
EEPROMs are *NOT* sensors! They are data storage chips commonly
found on memory modules (SPD), in monitors (EDID), or in some
laptops, for example.
I will now generate the commands needed to load the required modules.
Just press ENTER to continue:
To make the sensors modules behave correctly, add these lines to
/etc/modprobe.conf:
#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----
To load everything that is needed, add this to some /etc/rc* file:
#----cut here----
# I2C adapter drivers
modprobe i2c-i801
modprobe i2c-i810
# Chip drivers
modprobe eeprom
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones! You really
should try these commands right now to make sure everything is
working properly. Monitoring programs won't work until the needed
modules are loaded.
Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
Diese Liste sollte gespeichert oder ausgedruckt werden.
Die Werte müssen in die Datei /etc/modprobe.conf übergetragen werden, damit sie beim Start geladen werden. Die Reihenfolge ist entscheidend.
# I2C module options alias char-major-89 i2c-dev
Folgende Werte müssen in die Datei /etc/rc.local eingefügt werden.
# I2C adapter drivers modprobe i2c-i801 modprobe i2c-i810 # Chip drivers modprobe eeprom # sleep 2 # optional /usr/bin/sensors -s # recommended
Laden der Module
Nun müssen die Module geladen werden, damit ein Test durchgeführt werden kann. Nach einem Neustart stehen die Modul bereits beim Start zur Verfügung und das manuelle Laden entfällt.
[root]# modprobe i2c-i801
[root]# modprobe i2c-i810
[root]# modprobe eeprom
und zur Sicherheit noch
[root]# depmod -a
Durch das Ausführen von sensors kann die Ausgabe der Werte getestet werden.
[root]# sensors
Die Ausgabe beim Versuchsystem sieht so aus.
Philips PAL_BG (FI1216 and compatibles)-i2c-3-61 Adapter: bt878 #0 [sw]
Fein-Konfiguration
Falls Werte eine unpassende Skala haben, kann dies in der Datei /etc/sensors.conf angepasst werden.
Links
Wipe
Wipe ist das sichere Pendant zu rm. Wird eine Datei mit wipe gelöscht, so überschreibt wipe diese mehrmals mit Zufallsdaten oder auch Bitmustern. So wird sichergestellt, dass die gelöschten Daten nicht mehr wiederhergestellt werden können.
Damit wird die Partition /dev/hda3 aus /dev/random 4 Mal überschieben (Option -q). Die Option -k (keep) gibt an, dass die Datei nach Beendigung des Überschreibens nicht gelöscht wird.
wipe -qk /dev/hda3
Löscht jede Datei und jedes Verzeichnis unter (Option -r) /home/berke/plaintext/ inkl. /home/berke/plaintext/.
wipe -rcf /home/berke/plaintext/
Since wipe never follows symlinks unless explicitly told to do so, if you want to wipe /dev/floppy which happens to be a symlink to /dev/fd0u1440 you will have to specify the -D option. Before starting, it will ask you to type ``yes.
wipe -kqD /dev/floppy
Here, wipe will recursively (option -r) destroy everything under /var/log, excepting /var/log. It will not attempt to chmod() things. It will however be verbose (option -i). It won't ask you to type ``yes because of the -f option.
wipe -rfi >wipe.log /var/log/*
Links
Noname-Webcam
Die Webcam hat eine Bezeichnung VP-Eye und das ist schon alles.
lsusb -v | more
Ausgabe:
Bus 004 Device 003: ID 06a5:d001 Divio ProLink DS3303u WebCam
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x06a5 Divio
idProduct 0xd001 ProLink DS3303u WebCam
bcdDevice 1.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 249
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
MaxPower 300mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 1
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x03c0 1x 960 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 2
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0380 1x 896 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 3
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0300 1x 768 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 4
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0280 1x 640 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 5
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 6
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0180 1x 384 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 7
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0100 1x 256 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 1
Zusammenfassung der interessantesten Informationen
Bus 004 Device 003: ID 06a5:d001 Divio ProLink DS3303u WebCam ... ... idVendor 0x06a5 Divio idProduct 0xd001 ProLink DS3303u WebCam
Treiber
cvs -d:pserver:anonymous@nw802.cvs.sourceforge.net:/cvsroot/nw802 login cvs -z3 -d:pserver:anonymous@nw802.cvs.sourceforge.net:/cvsroot/nw802 co -P nw802-2.4
Verzeichnis wechseln
cd nw802-2.4
Make-File kopieren
cp Makefile.26 Makefile
Patchen der Datei
patch -p0 < patch-2.6
es erscheint folgende Ausgabe
patching file nw802.c
Aufräumen
make clean
[root]# make
Ausgabe
ln -sf /lib/modules/`uname -r`/build/drivers/media/video/usbvideo/usbvideo.h . ln -sf /lib/modules/`uname -r`/build/drivers/media/video/usbvideo/usbvideo.c . make -C /lib/modules/`uname -r`/build SUBDIRS=`pwd` modules make[1]: Entering directory `/usr/src/kernels/2.6.20-1.2933.fc6-i686' CC [M] /home/fab/nw802-2.4/nw8xx_jpgl.o In Datei, eingefügt von /home/fab/nw802-2.4/nw8xx_jpgl.c:38: /home/fab/nw802-2.4/nw8xx_jpgl.h:43:22: Fehler: usbvideo.h: Datei oder Verzeichnis nicht gefunden In file included from /home/fab/nw802-2.4/nw8xx_jpgl.c:38: /home/fab/nw802-2.4/nw8xx_jpgl.h:50: Warnung: »struct RingQueue« innerhalb Parameterliste deklariert /home/fab/nw802-2.4/nw8xx_jpgl.h:50: Warnung: sein Gültigkeitsbereich umfasst nur diese Definition bzw. Deklaration, was Sie wahrscheinlich nicht wollten /home/fab/nw802-2.4/nw8xx_jpgl.h:57: Warnung: »struct RingQueue« innerhalb Parameterliste deklariert /home/fab/nw802-2.4/nw8xx_jpgl.c: In Funktion »rqBR_init«: /home/fab/nw802-2.4/nw8xx_jpgl.c:65: Fehler: Implizite Deklaration der Funktion »RING_QUEUE_PEEK« /home/fab/nw802-2.4/nw8xx_jpgl.c:69: Fehler: Implizite Deklaration der Funktion »RING_QUEUE_DEQUEUE_BYTES« /home/fab/nw802-2.4/nw8xx_jpgl.c: Auf höchster Ebene: /home/fab/nw802-2.4/nw8xx_jpgl.c:435: Fehler: In Konflikt stehende Typen für »jpgl_processFrame« /home/fab/nw802-2.4/nw8xx_jpgl.h:50: Fehler: Vorherige Deklaration von »jpgl_processFrame« war hier /home/fab/nw802-2.4/nw8xx_jpgl.c: In Funktion »jpgl_processFrame«: /home/fab/nw802-2.4/nw8xx_jpgl.c:469: Fehler: Implizite Deklaration der Funktion »printk« /home/fab/nw802-2.4/nw8xx_jpgl.c:469: Fehler: »KERN_NOTICE« nicht deklariert (erste Benutzung in dieser Funktion) /home/fab/nw802-2.4/nw8xx_jpgl.c:469: Fehler: (Jeder nicht deklarierte Bezeichner wird nur einmal aufgeführt /home/fab/nw802-2.4/nw8xx_jpgl.c:469: Fehler: für jede Funktion in der er auftritt.) /home/fab/nw802-2.4/nw8xx_jpgl.c:469: Fehler: expected »)« before string constant /home/fab/nw802-2.4/nw8xx_jpgl.c:479: Fehler: Implizite Deklaration der Funktion »kmalloc« /home/fab/nw802-2.4/nw8xx_jpgl.c:479: Fehler: »GFP_KERNEL« nicht deklariert (erste Benutzung in dieser Funktion) /home/fab/nw802-2.4/nw8xx_jpgl.c:479: Warnung: Zuweisung erzeugt Zeiger von Ganzzahl ohne Typkonvertierung /home/fab/nw802-2.4/nw8xx_jpgl.c:661: Fehler: Implizite Deklaration der Funktion »kfree« /home/fab/nw802-2.4/nw8xx_jpgl.c: Auf höchster Ebene: /home/fab/nw802-2.4/nw8xx_jpgl.c:672: Fehler: In Konflikt stehende Typen für »jpgl_findHeader« /home/fab/nw802-2.4/nw8xx_jpgl.h:57: Fehler: Vorherige Deklaration von »jpgl_findHeader« war hier /home/fab/nw802-2.4/nw8xx_jpgl.c: In Funktion »jpgl_findHeader«: /home/fab/nw802-2.4/nw8xx_jpgl.c:688: Fehler: Implizite Deklaration der Funktion »RingQueue_GetLength« make[2]: *** [/home/fab/nw802-2.4/nw8xx_jpgl.o] Fehler 1 make[1]: *** [_module_/home/fab/nw802-2.4] Fehler 2 make[1]: Leaving directory `/usr/src/kernels/2.6.20-1.2933.fc6-i686' make: *** [default] Fehler 2
Laden der Treiber
insmod usbvideo.o && insmod nw802.o
Links
Geräte identifizieren
mit lspci und lsusb können Geräte genauer identifiziert werden. Unter anderem ähnliche Einträge wie dieser (für eine WLAN-Karte mit Raltek-Chipsatz)
Bus 001 Device 003: ID 0b05:1742 ASUSTek Computer, Inc. 802.11n Network Adapter
Nach der Id 0b05:1742 (bzw. eurer Id) einfach googeln, dann sollte sich das Gerät (bzw. der Chipsatz, der ja oft viel wichtiger ist) schon irgendwo finden lassen. Mit Option -v bekommt man bei beiden noch nähere Infos.
next
...
