[debian sid+kernel 2.6.x] eth0 non lancé au boot RESOLU

eth0 non lancé au boot RESOLU [debian sid+kernel 2.6.x] - Hardware - Linux et OS Alternatifs

Marsh Posté le 30-10-2004 à 01:19:28    

Il m'arrive un truc bizarre:
je viens de compiler le noyau 2.6.9 (j'ai essayé avec le 2.6.8 c'est pareil) et au boot suivant voila ce que j'ai:

Code :
  1. eth0: unknown hardware address type 24
  2. Listening on LPF/eth0/
  3. Sending on   LPF/eth0/
  4. Sending on   Socket/fallback
  5. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
  6. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
  7. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
  8. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
  9. ...


bref il a un pb avec la carte reseau et ne peux se faire attribué d'adresse IP.
 
Par contre, une fois booté, je tape en root dhclient et là:

Code :
  1. root@seldon /home/rik# dhclient
  2. Internet Systems Consortium DHCP Client V3.0.1
  3. Copyright 2004 Internet Systems Consortium.
  4. All rights reserved.
  5. For info, please visit http://www.isc.org/products/DHCP
  6. eth0: unknown hardware address type 24
  7. eth0: unknown hardware address type 24
  8. Listening on LPF/eth0/
  9. Sending on   LPF/eth0/
  10. Listening on LPF/lo/
  11. Sending on   LPF/lo/
  12. Listening on LPF/eth1/00:50:fc:24:d9:0d
  13. Sending on   LPF/eth1/00:50:fc:24:d9:0d
  14. Sending on   Socket/fallback
  15. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
  16. DHCPDISCOVER on lo to 255.255.255.255 port 67 interval 7
  17. DHCPREQUEST on eth1 to 255.255.255.255 port 67
  18. DHCPACK from 192.168.0.1
  19. bound to 192.168.0.11 -- renewal in 16833 seconds.


Alors que je n'ai qu'une carte reseau donc il ne devrais pas y avoir de eth1.
 
Et pour finir en beauté voici mon ifconfig :

Code :
  1. root@seldon /home/rik# ifconfig
  2. eth0      Lien encap:UNSPEC  HWaddr 07-00-50-C5-00-01-1A-FB-00-00-00-00-00-00-00-00
  3.           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  4.           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  5.           TX packets:0 errors:20 dropped:20 overruns:0 carrier:0
  6.           collisions:0 lg file transmission:1000
  7.           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
  8. eth1      Lien encap:Ethernet  HWaddr 00:50:FC:24:D9:0D 
  9.           inet adr:192.168.0.11  Bcast:192.168.0.255  Masque:255.255.255.0
  10.           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  11.           RX packets:468 errors:0 dropped:0 overruns:0 frame:0
  12.           TX packets:364 errors:0 dropped:0 overruns:0 carrier:0
  13.           collisions:0 lg file transmission:1000
  14.           RX bytes:437795 (427.5 KiB)  TX bytes:78755 (76.9 KiB)
  15.           Interruption:11 Adresse de base:0xec00
  16. lo        Lien encap:Boucle locale 
  17.           UP LOOPBACK RUNNING  MTU:16436  Metric:1
  18.           RX packets:25 errors:0 dropped:0 overruns:0 frame:0
  19.           TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
  20.           collisions:0 lg file transmission:0
  21.           RX bytes:6136 (5.9 KiB)  TX bytes:6136 (5.9 KiB)


 
Ca c'est de la MAC adresse!
 
Quelqu'un aurrait une idée? parce que là je suis sec...


Message édité par yugo le 31-10-2004 à 11:43:50
Reply

Marsh Posté le 30-10-2004 à 01:19:28   

Reply

Marsh Posté le 30-10-2004 à 09:32:40    

Il n'y a rien dans lspci ou dmesg qui permettrait d'identifier cette carte mystère ?


Message édité par Acontios le 30-10-2004 à 09:33:26

---------------
"not everyone likes metal..... FUCK THEM" Fat Ed.
Reply

Marsh Posté le 30-10-2004 à 15:49:29    

Ben j'ai pas l'impression qu'il y ai un quelconque mystère dans ma machine:

Code :
  1. root@seldon /home/rik# lspci
  2. 0000:00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4)
  3. 0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP]
  4. 0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)
  5. 0000:00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
  6. 0000:00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a)
  7. 0000:00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1a)
  8. 0000:00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
  9. 0000:00:0a.0 FireWire (IEEE 1394): Texas Instruments TSB12LV23 IEEE-1394 Controller
  10. 0000:00:0b.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 08)
  11. 0000:00:0b.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 08)
  12. 0000:00:0c.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 50)
  13. 0000:00:0c.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 50)
  14. 0000:00:0c.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51)
  15. 0000:00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
  16. 0000:01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)


Et le dmesg:

Code :
  1. root@seldon /home/rik# dmesg
  2. Linux version 2.6.8.1 (root@seldon) (version gcc 3.3.5 (Debian 1:3.3.5-2)) #2 Sat Oct 30 14:47:49
  3. BIOS-provided physical RAM map:
  4. BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
  5. BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
  6. BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
  7. BIOS-e820: 0000000000100000 - 000000001fff0000 (usable)
  8. BIOS-e820: 000000001fff0000 - 000000001fff3000 (ACPI NVS)
  9. BIOS-e820: 000000001fff3000 - 0000000020000000 (ACPI data)
  10. BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
  11. 511MB LOWMEM available.
  12. On node 0 totalpages: 131056
  13.   DMA zone: 4096 pages, LIFO batch:1
  14.   Normal zone: 126960 pages, LIFO batch:16
  15.   HighMem zone: 0 pages, LIFO batch:1
  16. DMI 2.2 present.
  17. ACPI: RSDP (v000 VIA694                                    ) @ 0x000f6db0
  18. ACPI: RSDT (v001 VIA694 AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1fff3000
  19. ACPI: FADT (v001 VIA694 AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1fff3040
  20. ACPI: DSDT (v001 VIA694 AWRDACPI 0x00001000 MSFT 0x0100000c) @ 0x00000000
  21. ACPI: PM-Timer IO Port: 0x4008
  22. Built 1 zonelists
  23. Kernel command line: BOOT_IMAGE=Debian_2.6.8.1 ro root=302 devfs=nomount
  24. Local APIC disabled by BIOS -- reenabling.
  25. Found and enabled local APIC!
  26. Initializing CPU#0
  27. PID hash table entries: 2048 (order 11: 16384 bytes)
  28. Detected 1463.461 MHz processor.
  29. Using pmtmr for high-res timesource
  30. Console: colour VGA+ 80x25
  31. Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
  32. Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
  33. Memory: 515988k/524224k available (1510k kernel code, 7472k reserved, 713k data, 144k init, 0k hi
  34. Checking if this processor honours the WP bit even in supervisor mode... Ok.
  35. Calibrating delay loop... 2899.96 BogoMIPS
  36. Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
  37. CPU: After generic identify, caps: 0383fbff 00000000 00000000 00000000
  38. CPU: After vendor identify, caps:  0383fbff 00000000 00000000 00000000
  39. CPU: L1 I cache: 16K, L1 D cache: 16K
  40. CPU: L2 cache: 256K
  41. CPU: After all inits, caps:        0383fbff 00000000 00000000 00000040
  42. Intel machine check architecture supported.
  43. Intel machine check reporting enabled on CPU#0.
  44. CPU: Intel(R) Celeron(TM) CPU                1100MHz stepping 01
  45. Enabling fast FPU save and restore... done.
  46. Enabling unmasked SIMD FPU exception support... done.
  47. Checking 'hlt' instruction... OK.
  48. enabled ExtINT on CPU#0
  49. ESR value before enabling vector: 00000000
  50. ESR value after enabling vector: 00000000
  51. Using local APIC timer interrupts.
  52. calibrating APIC timer ...
  53. ..... CPU clock speed is 1462.0781 MHz.
  54. ..... host bus clock speed is 132.0980 MHz.
  55. NET: Registered protocol family 16
  56. PCI: PCI BIOS revision 2.10 entry at 0xfb390, last bus=1
  57. PCI: Using configuration type 1
  58. mtrr: v2.0 (20020519)
  59. ACPI: Subsystem revision 20040326
  60. ACPI: IRQ11 SCI: Level Trigger.
  61. ACPI: Interpreter enabled
  62. ACPI: Using PIC for interrupt routing
  63. ACPI: PCI Root Bridge [PCI0] (00:00)
  64. PCI: Probing PCI hardware (bus 00)
  65. ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
  66. ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 *11 12 14 15)
  67. ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 *5 6 7 10 11 12 14 15)
  68. ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 *10 11 12 14 15)
  69. ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *9
  70. Linux Plug and Play Support v0.97 (c) Adam Belay
  71. PnPBIOS: Scanning system for PnP BIOS support...
  72. PnPBIOS: Found PnP BIOS installation structure at 0xc00fbe70
  73. PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0xbea0, dseg 0xf0000
  74. PnPBIOS: 15 nodes reported by PnP BIOS; 15 recorded by driver
  75. PCI: Using ACPI for IRQ routing
  76. ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
  77. ACPI: PCI interrupt 0000:00:07.2[D] -> GSI 10 (level, low) -> IRQ 10
  78. ACPI: PCI interrupt 0000:00:07.3[D] -> GSI 10 (level, low) -> IRQ 10
  79. ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5
  80. ACPI: PCI interrupt 0000:00:0a.0[A] -> GSI 5 (level, low) -> IRQ 5
  81. ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
  82. ACPI: PCI interrupt 0000:00:0b.0[A] -> GSI 10 (level, low) -> IRQ 10
  83. ACPI: PCI interrupt 0000:00:0c.0[A] -> GSI 10 (level, low) -> IRQ 10
  84. ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
  85. ACPI: PCI interrupt 0000:00:0c.1[B] -> GSI 11 (level, low) -> IRQ 11
  86. ACPI: PCI interrupt 0000:00:0c.2[C] -> GSI 5 (level, low) -> IRQ 5
  87. ACPI: PCI interrupt 0000:00:0d.0[A] -> GSI 11 (level, low) -> IRQ 11
  88. ACPI: PCI interrupt 0000:01:00.0[A] -> GSI 11 (level, low) -> IRQ 11
  89. vesafb: probe of vesafb0 failed with error -6
  90. Machine check exception polling timer started.
  91. Initializing Cryptographic API
  92. PCI: Disabling Via external APIC routing
  93. PCI: Via IRQ fixup for 0000:00:07.2, from 9 to 10
  94. PCI: Via IRQ fixup for 0000:00:07.3, from 9 to 10
  95. PCI: Via IRQ fixup for 0000:00:0c.0, from 9 to 10
  96. isapnp: Scanning for PnP cards...
  97. isapnp: No Plug & Play device found
  98. Linux agpgart interface v0.100 (c) Dave Jones
  99. RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
  100. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
  101. ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
  102. hda: IC35L090AVV207-0, ATA DISK drive
  103. hdb: ST340014A, ATA DISK drive
  104. hdc: SAMSUNG CD-R/RW DRIVE SW-224B, ATAPI CD/DVD-ROM drive
  105. Using anticipatory io scheduler
  106. ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
  107. ide1 at 0x170-0x177,0x376 on irq 15
  108. hda: max request size: 1024KiB
  109. hda: 160836480 sectors (82348 MB) w/1821KiB Cache, CHS=16383/255/63
  110. hda: hda1 hda2 hda3 hda4
  111. hdb: max request size: 1024KiB
  112. hdb: 78165360 sectors (40020 MB) w/2048KiB Cache, CHS=16383/255/63
  113. hdb: hdb1 hdb2 hdb3
  114. mice: PS/2 mouse device common for all mice
  115. serio: i8042 AUX port at 0x60,0x64 irq 12
  116. input: ImPS/2 Logitech Wheel Mouse on isa0060/serio1
  117. serio: i8042 KBD port at 0x60,0x64 irq 1
  118. input: AT Translated Set 2 keyboard on isa0060/serio0
  119. NET: Registered protocol family 2
  120. IP: routing cache hash table of 4096 buckets, 32Kbytes
  121. TCP: Hash tables configured (established 32768 bind 65536)
  122. NET: Registered protocol family 1
  123. NET: Registered protocol family 17
  124. ACPI: (supports S0 S3 S4 S5)
  125. kjournald starting.  Commit interval 5 seconds
  126. EXT3-fs: mounted filesystem with ordered data mode.
  127. VFS: Mounted root (ext3 filesystem) readonly.
  128. Freeing unused kernel memory: 144k freed
  129. spurious 8259A interrupt: IRQ7.
  130. Adding 1951888k swap on /dev/hdb2.  Priority:-1 extents:1
  131. EXT3 FS on hda2, internal journal
  132. kjournald starting.  Commit interval 5 seconds
  133. EXT3 FS on hda3, internal journal
  134. EXT3-fs: mounted filesystem with ordered data mode.
  135. kjournald starting.  Commit interval 5 seconds
  136. EXT3 FS on hdb3, internal journal
  137. EXT3-fs: mounted filesystem with ordered data mode.
  138. Real Time Clock Driver v1.12
  139. inserting floppy driver for 2.6.8.1
  140. Floppy drive(s): fd0 is 1.44M
  141. FDC 0 is a post-1991 82077
  142. Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
  143. ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
  144. ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
  145. parport0: PC-style at 0x378 [PCSPP(,...)]
  146. parport_pc: Via 686A parallel port: io=0x378
  147. agpgart: Detected VIA Apollo Pro 133 chipset
  148. agpgart: Maximum main memory to use for agp memory: 439M
  149. agpgart: AGP aperture is 128M @ 0xd0000000
  150. usbcore: registered new driver usbfs
  151. usbcore: registered new driver hub
  152. USB Universal Host Controller Interface driver v2.2
  153. ACPI: PCI interrupt 0000:00:07.2[D] -> GSI 10 (level, low) -> IRQ 10
  154. uhci_hcd 0000:00:07.2: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
  155. uhci_hcd 0000:00:07.2: irq 10, io base 0000d400
  156. uhci_hcd 0000:00:07.2: new USB bus registered, assigned bus number 1
  157. hub 1-0:1.0: USB hub found
  158. hub 1-0:1.0: 2 ports detected
  159. ACPI: PCI interrupt 0000:00:07.3[D] -> GSI 10 (level, low) -> IRQ 10
  160. uhci_hcd 0000:00:07.3: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#2)
  161. uhci_hcd 0000:00:07.3: irq 10, io base 0000d800
  162. uhci_hcd 0000:00:07.3: new USB bus registered, assigned bus number 2
  163. hub 2-0:1.0: USB hub found
  164. hub 2-0:1.0: 2 ports detected
  165. ACPI: PCI interrupt 0000:00:0c.0[A] -> GSI 10 (level, low) -> IRQ 10
  166. uhci_hcd 0000:00:0c.0: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#3)
  167. uhci_hcd 0000:00:0c.0: irq 10, io base 0000e400
  168. uhci_hcd 0000:00:0c.0: new USB bus registered, assigned bus number 3
  169. hub 3-0:1.0: USB hub found
  170. hub 3-0:1.0: 2 ports detected
  171. ACPI: PCI interrupt 0000:00:0c.1[B] -> GSI 11 (level, low) -> IRQ 11
  172. uhci_hcd 0000:00:0c.1: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#4)
  173. uhci_hcd 0000:00:0c.1: irq 11, io base 0000e800
  174. uhci_hcd 0000:00:0c.1: new USB bus registered, assigned bus number 4
  175. hub 4-0:1.0: USB hub found
  176. hub 4-0:1.0: 2 ports detected
  177. usb 1-1: new full speed USB device using address 2
  178. hub 1-1:1.0: USB hub found
  179. hub 1-1:1.0: 4 ports detected
  180. ieee1394: Initialized config rom entry `ip1394'
  181. ohci1394: $Rev: 1223 $ Ben Collins <bcollins@debian.org>
  182. ACPI: PCI interrupt 0000:00:0a.0[A] -> GSI 5 (level, low) -> IRQ 5
  183. usb 1-1.2: new full speed USB device using address 3
  184. ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[5]  MMIO=[e3006000-e30067ff]  Max Packet=[2048]
  185. usb 4-1: new full speed USB device using address 2
  186. SCSI subsystem initialized
  187. Initializing USB Mass Storage driver...
  188. scsi0 : SCSI emulation for USB Mass Storage devices
  189.   Vendor:           Model: USB DRIVE         Rev: 2.00
  190.   Type:   Direct-Access                      ANSI SCSI revision: 02
  191. USB Mass Storage device found at 3
  192. usbcore: registered new driver usb-storage
  193. USB Mass Storage support registered.
  194. SCSI device sda: 512000 512-byte hdwr sectors (262 MB)
  195. sda: assuming Write Enabled
  196. sda: assuming drive cache: write through
  197. sda: sda1
  198. Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
  199. ieee1394: Host added: ID:BUS[0-00:1023]  GUID[070050c500011afb]
  200. ip1394: $Rev: 1224 $ Ben Collins <bcollins@debian.org>
  201. ip1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
  202. ACPI: PCI interrupt 0000:00:0b.0[A] -> GSI 10 (level, low) -> IRQ 10
  203. ACPI: PCI interrupt 0000:00:0c.2[C] -> GSI 5 (level, low) -> IRQ 5
  204. ehci_hcd 0000:00:0c.2: VIA Technologies, Inc. USB 2.0
  205. ehci_hcd 0000:00:0c.2: irq 5, pci mem e0a68000
  206. ehci_hcd 0000:00:0c.2: new USB bus registered, assigned bus number 5
  207. ehci_hcd 0000:00:0c.2: USB 2.0 enabled, EHCI 0.95, driver 2004-May-10
  208. hub 5-0:1.0: USB hub found
  209. hub 5-0:1.0: 4 ports detected
  210. usb 4-1: USB disconnect, address 2
  211. 8139too Fast Ethernet driver 0.9.27
  212. ACPI: PCI interrupt 0000:00:0d.0[A] -> GSI 11 (level, low) -> IRQ 11
  213. eth1: RealTek RTL8139 at 0xec00, 00:50:fc:24:d9:0d, IRQ 11
  214. eth1:  Identified 8139 chip type 'RTL-8139C'
  215. usb 4-1: new full speed USB device using address 3


 
J'ai vraiment plus d'idée :(

Reply

Marsh Posté le 30-10-2004 à 20:49:15    

Pas de grands mystères en fait...
 
La réponse se trouve dans ton dmesg :
 
> # ieee1394: Host added: ID:BUS[0-00:1023]  GUID[070050c500011afb]
> # ip1394: $Rev: 1224 $ Ben Collins <bcollins@debian.org>
> # ip1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
 
et
 
> # eth1: RealTek RTL8139 at 0xec00, 00:50:fc:24:D9:0d, IRQ 11
> # eth1:  Identified 8139 chip type 'RTL-8139C'
 
 
C'est simple : en compilant tes noyaux 2.6.x, s'est activé le support pour l'IEEE 1394 over ethernet, qui permet d'utiliser un périph Firewire (IEEE 1394) comme interface réseau.
Comme par hasard il se trouve que tu possède un périph de ce type (cf ton lspci) ; ce périph est en fait utilisé par défaut comme première interface réseau en eth0.
Ta carte Realtek, elle, est configurée en eth1 comme l'atteste le dmesg...
 
Le plus simple dans ce cas, si tu ne souhaite voir que ta carte réseau Realtek comme interface ethernet, c'est donc de lancer une recompil rapide d'un noyau en désactivant le support de l'ieee 1394 over ethernet.


---------------
THRAK (def.) : 1) A sudden and precise impact moving from intention, direction and commitment, in service of an aim. 2) 117 guitars almost striking the same chord simultaneously.
Reply

Marsh Posté le 30-10-2004 à 23:06:43    

alors là, chapeau bas! je suis abasourdi de la simplicité de ton explication ;)
 
Bon, ben ya plus qu'a...
 
Merci parce que là c'est pas une épine que vous m'enlevez du pieds mais un buisson :D
 
Je fais ca et je posterais pour le buisson dans l'autre pied: pb d'install des drivers NVIDIA mais je voudrais chercher encore un peu avant.
 
MERCI!

Reply

Marsh Posté le 31-10-2004 à 11:45:04    

C'était bien ca: j'ai dé-sélectionné le suport du IEEE1394, je le remettrais pas à pas quand j'en aurrais besoin ;)

Reply

Sujets relatifs:

Leave a Replay

Make sure you enter the(*)required information where indicate.HTML code is not allowed