Hinweis: Das Forum wird geschlossen! Neue Registrierungen sind nicht mehr möglich!

 Zurück zu Pro-Linux   Foren-Übersicht   FAQ     Suchen    Mitgliederliste
Bluetooth usb adapter unter Linux ?!

 
Neuen Beitrag schreiben   Auf Beitrag antworten    Pro-Linux Foren-Übersicht -> Hardware
Vorheriges Thema anzeigen :: Nächstes Thema anzeigen  
Autor Nachricht
centrino
Gast





BeitragVerfasst am: 09. Dez 2003 11:41   Titel: Bluetooth usb adapter unter Linux ?!

ICh möchte ein Bluetooth USB adapter BT-DG02 von Epox unter Fedora Core einrichten.
Funktioniert das überhaupt, und wenn ja wie kann ich es vorgehen.

gruss
 

centrino
Gast





BeitragVerfasst am: 09. Dez 2003 12:42   Titel: Re: Bluetooth usb adapter unter Linux ?!

Ich wollte nach der Anleitung von Epox homepage den patch für Bluetooth eingespielt, bekomme aber diese Meldung:
wie kann ich meine kernel source rückgängig machen ? und make xconfig wieder funtioniert ?
Was habe ich falsch gemacht ?

[root@localhost linux-2.4]# zcat patch-2.4.20-mh6.gz | patch -p 1
patching file Documentation/Configure.help
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #1 succeeded at 22736 (offset 1458 lines).
Hunk #3 succeeded at 22777 (offset 1458 lines).
Hunk #5 succeeded at 22805 (offset 1458 lines).
Hunk #6 succeeded at 21408 (offset 10 lines).
patching file Makefile
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej
patching file arch/sparc64/kernel/ioctl32.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #1 succeeded at 96 (offset 1 line).
Hunk #2 FAILED at 4287.
Hunk #3 FAILED at 4988.
2 out of 3 hunks FAILED -- saving rejects to file arch/sparc64/kernel/ioctl32.c.rej
patching file drivers/bluetooth/Config.in
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #1 succeeded at 1 with fuzz 1.
Hunk #2 succeeded at 19 (offset 2 lines).
patching file drivers/bluetooth/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #2 FAILED at 9.
1 out of 2 hunks FAILED -- saving rejects to file drivers/bluetooth/Makefile.rej
The next patch would create the file drivers/bluetooth/btuart_cs.c,
which already exists! Assume -R? [n] y
patching file drivers/bluetooth/btuart_cs.c
The next patch would create the file drivers/bluetooth/hci_bcsp.c,
which already exists! Assume -R? [n] y
patching file drivers/bluetooth/hci_bcsp.c
The next patch would create the file drivers/bluetooth/hci_bcsp.h,
which already exists! Assume -R? [n] y
patching file drivers/bluetooth/hci_bcsp.h
patching file drivers/bluetooth/hci_h4.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
patching file drivers/bluetooth/hci_h4.h
Reversed (or previously applied) patch detected! Assume -R? [n] y
patching file drivers/bluetooth/hci_ldisc.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
patching file drivers/bluetooth/hci_uart.h
Reversed (or previously applied) patch detected! Assume -R? [n] y
patching file drivers/bluetooth/hci_usb.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #5 FAILED at 92.
Hunk #6 FAILED at 212.
Hunk #7 succeeded at 230 (offset 1 line).
Hunk #9 succeeded at 278 (offset 1 line).
Hunk #11 succeeded at 390 (offset 1 line).
Hunk #13 succeeded at 663 (offset 1 line).
Hunk #15 succeeded at 687 (offset 1 line).
2 out of 16 hunks FAILED -- saving rejects to file drivers/bluetooth/hci_usb.c.rej
patching file drivers/bluetooth/hci_usb.h
Reversed (or previously applied) patch detected! Assume -R? [n] y
patching file drivers/char/pcmcia/serial_cs.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
patching file drivers/char/serial.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #1 succeeded at 847 (offset 5 lines).
patching file drivers/usb/Config.in
Hunk #1 FAILED at 32.
1 out of 1 hunk FAILED -- saving rejects to file drivers/usb/Config.in.rej
patching file include/net/bluetooth/hci.h
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #3 succeeded at 439 (offset 3 lines).
patching file include/net/bluetooth/hci_core.h
Reversed (or previously applied) patch detected! Assume -R? [n] y
The next patch would create the file include/net/bluetooth/rfcomm.h,
which already exists! Assume -R? [n] y
patching file include/net/bluetooth/rfcomm.h
Hunk #1 FAILED at 1.
File include/net/bluetooth/rfcomm.h is not empty after patch, as expected
1 out of 1 hunk FAILED -- saving rejects to file include/net/bluetooth/rfcomm.h.rej
patching file include/pcmcia/ciscode.h
Reversed (or previously applied) patch detected! Assume -R? [n] y
patching file net/bluetooth/Config.in
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #2 FAILED at 10.
1 out of 2 hunks FAILED -- saving rejects to file net/bluetooth/Config.in.rej
patching file net/bluetooth/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #2 FAILED at 12.
1 out of 2 hunks FAILED -- saving rejects to file net/bluetooth/Makefile.rej
patching file net/bluetooth/af_bluetooth.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
patching file net/bluetooth/bnep/Config.in
Reversed (or previously applied) patch detected! Assume -R? [n] y
patching file net/bluetooth/bnep/Makefile
Reversed (or previously applied) patch detected! Assume -R? [n] y
patching file net/bluetooth/bnep/bnep.h
Reversed (or previously applied) patch detected! Assume -R? [n] y
patching file net/bluetooth/bnep/core.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #16 succeeded at 501 (offset -2 lines).
Hunk #18 succeeded at 544 (offset -2 lines).
Hunk #20 succeeded at 615 (offset -2 lines).
Hunk #22 succeeded at 633 (offset -2 lines).
Hunk #24 FAILED at 676.
Hunk #25 FAILED at 694.
2 out of 25 hunks FAILED -- saving rejects to file net/bluetooth/bnep/core.c.rej
patching file net/bluetooth/bnep/netdev.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
patching file net/bluetooth/bnep/sock.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
patching file net/bluetooth/hci_conn.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
patching file net/bluetooth/hci_core.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #1 succeeded at 720 (offset 3 lines).
Hunk #3 succeeded at 867 (offset 3 lines).
patching file net/bluetooth/hci_sock.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #2 FAILED at 68.
1 out of 3 hunks FAILED -- saving rejects to file net/bluetooth/hci_sock.c.rej
patching file net/bluetooth/l2cap.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #2 succeeded at 430 (offset -2 lines).
Hunk #4 succeeded at 474 (offset -2 lines).
The next patch would create the file net/bluetooth/rfcomm/Config.in,
which already exists! Assume -R? [n] y
patching file net/bluetooth/rfcomm/Config.in
The next patch would create the file net/bluetooth/rfcomm/Makefile,
which already exists! Assume -R? [n] y
patching file net/bluetooth/rfcomm/Makefile
The next patch would create the file net/bluetooth/rfcomm/core.c,
which already exists! Assume -R? [n] y
patching file net/bluetooth/rfcomm/core.c
Hunk #1 FAILED at 1.
File net/bluetooth/rfcomm/core.c is not empty after patch, as expected
1 out of 1 hunk FAILED -- saving rejects to file net/bluetooth/rfcomm/core.c.rej
The next patch would create the file net/bluetooth/rfcomm/crc.c,
which already exists! Assume -R? [n] y
patching file net/bluetooth/rfcomm/crc.c
The next patch would create the file net/bluetooth/rfcomm/sock.c,
which already exists! Assume -R? [n] y
patching file net/bluetooth/rfcomm/sock.c
Hunk #1 FAILED at 1.
File net/bluetooth/rfcomm/sock.c is not empty after patch, as expected
1 out of 1 hunk FAILED -- saving rejects to file net/bluetooth/rfcomm/sock.c.rej
The next patch would create the file net/bluetooth/rfcomm/tty.c,
which already exists! Assume -R? [n] y
patching file net/bluetooth/rfcomm/tty.c
Hunk #1 FAILED at 1.
File net/bluetooth/rfcomm/tty.c is not empty after patch, as expected
1 out of 1 hunk FAILED -- saving rejects to file net/bluetooth/rfcomm/tty.c.rej
patching file net/bluetooth/sco.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #1 succeeded at 679 (offset 1 line).
patching file net/bluetooth/syms.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
[root@localhost linux-2.4]#




[root@localhost linux-2.4]# make xconfig
rm -f include/asm
( cd include ; ln -sf asm-i386 asm)
make -C scripts kconfig.tk
make: Wechsel in das Verzeichnis Verzeichnis »/usr/src/linux-2.4.22-1.2115.nptl/scripts«
gcc32 -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -c -o tkparse.o tkparse.c
gcc32 -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -c -o tkcond.o tkcond.c
gcc32 -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -c -o tkgen.o tkgen.c
gcc32 -o tkparse tkparse.o tkcond.o tkgen.o
cat header.tk >> ./kconfig.tk
./tkparse < ../arch/i386/config.in >> kconfig.tk
net/bluetooth/Config.in: 13: unable to open net/bluetooth/rfcomm/Config.in
make: *** [kconfig.tk] Fehler 1
make: Verlassen des Verzeichnisses Verzeichnis »/usr/src/linux-2.4.22-1.2115.nptl/scripts«
make: *** [xconfig] Fehler 2
 

Jochen
Gast





BeitragVerfasst am: 10. Dez 2003 11:50   Titel: Re: Bluetooth usb adapter unter Linux ?!

Patches beziehen sich immer auf eine bestimmte Kernelversion. Du verwendest die Sourcen des linux-2.4.22-1.2115.nptl-Kernels, wie ihn Redhat bei Fedora Core 1 mitliefert. Der Patch aber scheint sich auf den Kernel 2.4.20-mh6 (also den 2.4.20er mit irgendwelchen Erweiterungen) zu beziehen. Die passen nicht zueinander, so dass der Patch nur teilweise angewendet werden kann. Kein Wunder, dass danach einiges kaputt ist...

Am Besten ist es, wenn Du das Kernelsourcenpaket einfach entfernst und wieder neu installierst; das ist einfach und sicher. Mach einfach ein
code:
rpm -e kernel-source
rm -r /usr/src/linux-2.4.22-1.2115.nptl
rpm -ihv /mnt/cdrom/Fedora/RPMS/kernel-source-*.rpm

Das Verzeichnis solltest Du zwischendurch löschen, da dort noch überreste von Deinen Patchversuchen liegen, von denen das Paketmanagement nichts wissen kann. Das letzte Kommando setzt voraus, dass Du die CD mit dem Kernelsourcen-Paket eingelegt und gemountet hast; ggf. reicht auch ein "yum install kernel-source", wenn der bei Dir eingerichtet ist (und Deine Netzverbindung einigermassen breitbandig ist).

Jochen
 

Beiträge vom vorherigen Thema anzeigen:   
     Pro-Linux Foren-Übersicht -> Hardware Alle Zeiten sind GMT + 1 Stunde
Seite 1 von 1

 
Gehen Sie zu:  

Powered by phpBB © phpBB Group
pro_linux Theme © 2004 by Mandaxy