Fedora-Fr - Communauté francophone Fedora - Linux

Communauté francophone des utilisateurs de la distribution Linux Fedora.

  

Dernière news : Représenter Fedora au Capitole du Libre 2019

#1 Re : [Anciennes versions] Matériel » Probleme Partition ntfs » 29/05/2007 21:01:18

Pour ce qui est de la sauvegarde de mes données c'est pas possible c'est le plus gros disque dur que j'ai et sa m'aurait pris une 30ene de DVD hmm
Bizardment mon disque dur est toujour detecté comme un ntfs par le "gestionnaire de volumes logiques" et pas ifs (ou un truc dans le genre pour lire les partition linux sous windows )

et voila pour pingou

[root@localhost ~]# fdisk -l

Disk /dev/hda: 10.1 GB, 10110320640 bytes
255 heads, 63 sectors/track, 1229 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1          13      104391   83  Linux
/dev/hda2              14        1229     9767520   8e  Linux LVM

Disk /dev/dm-0: 8891 MB, 8891924480 bytes
255 heads, 63 sectors/track, 1081 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 1073 MB, 1073741824 bytes
255 heads, 63 sectors/track, 130 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-1 doesn't contain a valid partition table

Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1       25332   203479258+   7  HPFS/NTFS
/dev/sda2           25333       30401    40716742+   f  W95 Ext'd (LBA)
/dev/sda5           25333       30401    40716711   83  Linux
[root@localhost ~]#

Edit: Je me demandé aussi si un log de recuperation de partition endommagée pourrait me faire recuperer mes données? (un log sous windob me convien aussi)

#2 [Anciennes versions] Matériel » Probleme Partition ntfs » 29/05/2007 00:23:55

YonX
Réponses : 4

Alors voila je voulais monter ma partition ntfs sur mon dd externe je suis donc allé dans le "gestionnaire de volumes logiques" pour voir son chemin et la je voi un bouton qui dit "Initialiser l'entité" je clique dessus en pensant que c'est pour monter mon volume mais je vois 2 autres boutons apparaitres je clique sur celui pour qui mon disque dur revienne dans le groupe "entité non initialisée" et j'essaie de monter ma partition avec une ligne de commande mais je reçoit un message bizard qui m'empeche de faire fonctionner ma partition et elle n'est plus reconnue sous windows non plus ce que je trouve inquietant surtout qu'il y avait 150go de données environ sur ce dd.
Voila le message :

[root@localhost ~]# mount -t ntfs-3g /dev/sda1 /media/ntfs
NTFS signature is missing.
Failed to startup volume: Argument invalide
Failed to mount '/dev/sda1': Argument invalide
The device '/dev/sda1' doesn't have a valid NTFS.
Maybe you selected the wrong device? Or the whole disk instead of a
partition (e.g. /dev/hda, not /dev/hda1)? Or the other way around?
[root@localhost ~]#

Est-ce qu'il y a une solution pour récupérer cette partition ?

#3 Re : [Anciennes versions] Réseaux » Configuration WIFI (chipset Atheros Communications, Inc.) » 24/04/2007 23:40:28

Voila c'est bon j'ai supprimé les lignes inutiles et désactivé mon ethernet rebooté pour voir et tout va bien ma clef se lance au démarrage de fedora juste aprés grub tout est bon

#4 Re : [Anciennes versions] Réseaux » Configuration WIFI (chipset Atheros Communications, Inc.) » 24/04/2007 23:13:54

Oui oui oui je suis connecté via le wifi j'ai débranché ma prise ethernet même ^^

pour /etc/modprobe.d/ndiswrapper

install usb:v0000p0000d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
install usb:v0CF3p0001d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
install usb:v0CF3p0002d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
install usb:v0CF3p0002d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
install usb:v0CF3p0003d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
install usb:v0CF3p0004d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
install usb:v0CF3p0005d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
install usb:v0CF3p0006d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
install usb:v168Cp0001d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
install usb:v168Cp0002d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
alias wlan0 ndiswrapper

et pour  /etc/modprobe.conf

alias snd-card-0 snd-intel8x0
options snd-intel8x0 index=0  
remove snd-intel8x0 { /usr/sbin/alsactl store 0 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-intel8x0
remove snd-mpu401 { /usr/sbin/alsactl store 1 >/dev/null 2>&1 || : ; }; /sbin/modprobe -r --ignore-remove snd-mpu401
alias eth0 8139too
alias snd-card-1 snd-mpu401
options snd-card-1 index=1

#5 Re : [Anciennes versions] Réseaux » Configuration WIFI (chipset Atheros Communications, Inc.) » 24/04/2007 23:06:58

Voili voilouuuuuuuuuuuuuuu sa m'enlève un poids dit donc depuis le temps que je galère y suffisait de redémarrer ndiswrapper j'ai honte de moi big_smile en tout cas un GRAND merci a toi Pikachu_2014

que d'émotion *snif* ma premiere navigation en wifi sur linux ^^

#6 Re : [Anciennes versions] Réseaux » Configuration WIFI (chipset Atheros Communications, Inc.) » 24/04/2007 22:43:38

Euuuuuuuuuuuuu re question bebete ^^'. sa veut dire quoi sa

[root@localhost Win2000-XP.zip_FILES]# ndiswrapper -m
module configuration contains directive install usb:v0000p0000d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 691, <MODPROBE> line 37.
module configuration contains directive install usb:v0CF3p0001d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 691, <MODPROBE> line 38.
module configuration contains directive install usb:v0CF3p0002d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 691, <MODPROBE> line 39.
module configuration contains directive install usb:v0CF3p0002d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 691, <MODPROBE> line 40.
module configuration contains directive install usb:v0CF3p0003d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 691, <MODPROBE> line 41.
module configuration contains directive install usb:v0CF3p0004d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 691, <MODPROBE> line 42.
module configuration contains directive install usb:v0CF3p0005d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 691, <MODPROBE> line 43.
module configuration contains directive install usb:v0CF3p0006d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 691, <MODPROBE> line 44.
module configuration contains directive install usb:v168Cp0001d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 691, <MODPROBE> line 45.
module configuration contains directive install usb:v168Cp0002d*dc*dsc*dp*ic*isc*ip* /sbin/modprobe ndiswrapper
;you should delete that at /usr/sbin/ndiswrapper line 691, <MODPROBE> line 46.
adding "alias wlan0 ndiswrapper" to /etc/modprobe.d/ndiswrapper ...
couldn't add module alias:  at /usr/sbin/ndiswrapper line 705.
[root@localhost Win2000-XP.zip_FILES]#

#7 Re : [Anciennes versions] Réseaux » Configuration WIFI (chipset Atheros Communications, Inc.) » 24/04/2007 22:35:34

OUAIIIIIIIIIIII BRAVOOOOOOOOOOOOOOOOOOOO
enfin y a toujours un message d'erreur que je doit comprendre ^^'

[root@localhost Win2000-XP.zip_FILES]# rmmod ndiswrapper
[root@localhost Win2000-XP.zip_FILES]# modprobe ndiswrapper
[root@localhost Win2000-XP.zip_FILES]# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

sit0      no wireless extensions.

Warning: Driver for device wlan0 has been compiled with version 20
of Wireless Extension, while this program supports up to version 19.
Some things may be broken...

wlan0     IEEE 802.11g  ESSID:""
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated
          Bit Rate:108 Mb/s
          Encryption key:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

[root@localhost Win2000-XP.zip_FILES]#


EDIT: a ba non en fait elle est allumé mais pas fonctionnelle ^^'

#8 Re : [Anciennes versions] Réseaux » Configuration WIFI (chipset Atheros Communications, Inc.) » 24/04/2007 22:25:50

voila c'est fait mais je l'avait deja fait avant ^^

[root@localhost Win2000-XP.zip_FILES]#  ndiswrapper -r net5523
[root@localhost Win2000-XP.zip_FILES]# ndiswrapper -r athfmwdl
[root@localhost Win2000-XP.zip_FILES]#  ndiswrapper -l
no drivers installed
[root@localhost Win2000-XP.zip_FILES]#  ndiswrapper -i net5523.inf
installing net5523 ...
[root@localhost Win2000-XP.zip_FILES]#  ndiswrapper -i athfmwdl.inf
installing athfmwdl ...
[root@localhost Win2000-XP.zip_FILES]#  ndiswrapper -l
installed drivers:
athfmwdl                driver installed, hardware (168C:0002) present
net5523         driver installed
[root@localhost Win2000-XP.zip_FILES]# modprobe ndiswrapper
[root@localhost Win2000-XP.zip_FILES]# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

sit0      no wireless extensions.

[root@localhost Win2000-XP.zip_FILES]#

et voila ce que me dit ndiswrapper

[root@localhost Win2000-XP.zip_FILES]# ndiswrapper
install/manage Windows drivers for ndiswrapper

usage: ndiswrapper OPTION
-i inffile       install driver described by 'inffile'
-a devid driver  use installed 'driver' for 'devid'
-r driver        remove 'driver'
-l               list installed drivers
-m               write configuration for modprobe
-ma              write module alias configuration for all devices
-mi              write module install configuration for all devices
-v               report version information

where 'devid' is either PCIID or USBID of the form XXXX:XXXX,
as reported by 'lspci -n' or 'lsusb' for the card
[root@localhost Win2000-XP.zip_FILES]#

#9 Re : [Anciennes versions] Réseaux » Configuration WIFI (chipset Atheros Communications, Inc.) » 24/04/2007 22:19:07

voili voilou

[root@localhost Win2000-XP.zip_FILES]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:20:ED:BA:83:57
          inet adr:192.168.1.2  Bcast:192.168.1.255  Masque:255.255.255.0
          adr inet6: fe80::220:edff:feba:8357/64 Scope:Lien
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:757665 errors:0 dropped:0 overruns:0 frame:0
          TX packets:864143 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000
          RX bytes:380944335 (363.2 MiB)  TX bytes:629463194 (600.3 MiB)
          Interruption:169 Adresse de base:0xae00

lo        Link encap:Boucle locale
          inet adr:127.0.0.1  Masque:255.0.0.0
          adr inet6: ::1/128 Scope:Hôte
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:3558 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3558 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          RX bytes:5981044 (5.7 MiB)  TX bytes:5981044 (5.7 MiB)

sit0      Link encap:IPv6-dans-IPv4
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

[root@localhost Win2000-XP.zip_FILES]#

au cas ou ta pas vu

Je vien de voir le tuto et y a un truc bizard..... pour desinstaller un pilote je doit mettre ndiswrapper -r et non -e ...... c'est bizard

#10 Re : [Anciennes versions] Réseaux » Configuration WIFI (chipset Atheros Communications, Inc.) » 24/04/2007 22:10:17

Alors voila

[root@localhost Win2000-XP.zip_FILES]# modprobe ndiswrapper
[root@localhost Win2000-XP.zip_FILES]# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

sit0      no wireless extensions.

[root@localhost Win2000-XP.zip_FILES]#

Absolument rien.

P.S: comme tout bon journaliste que je ne suit pas je ne cite jamais mes sources :P (c'était dans un ancien topic que j'avait fait et qui a disparu ^^ )

Je vien de voir le tuto et y a un truc bizard..... pour desinstaller un pilote je doit mettre ndiswrapper -r et non -e ...... c'est bizard

#11 Re : [Anciennes versions] Réseaux » Configuration WIFI (chipset Atheros Communications, Inc.) » 24/04/2007 22:00:15

a j'avait oublié de la mettre cette commande merdouille
pitite correction

[root@localhost Win2000-XP.zip_FILES]# ndiswrapper -l
installed drivers:
athfmwdl                driver installed, hardware (168C:0002) present
net5523         driver installed
[root@localhost Win2000-XP.zip_FILES]#

pendant que je tenté de faire le truc que tu m'a deconseillé j'avait

[root@localhost Win2000-XP.zip_FILES]# ndiswrapper -l
installed drivers:
athfmwdl                driver installed, hardware (168C:0002) present
net5523         driver installed, hardware (168C:0001) present

je sait pas pourquoi j'ai plus confiance en celui ou je fesait des test roll

#12 Re : [Anciennes versions] Réseaux » Configuration WIFI (chipset Atheros Communications, Inc.) » 24/04/2007 21:53:03

a sa suffit sa? En fait avan on m'avait dit de faire comme sa et pas de juste installer les pilotes ^^' tout est bon alors mais rien ne se passe au niveau de ma clef toujours aucune lumière sad

#13 Re : [Anciennes versions] Réseaux » Configuration WIFI (chipset Atheros Communications, Inc.) » 24/04/2007 21:41:19

voili voilouuuu c'est fait mais encor un problème big_smile

[root@localhost Win2000-XP.zip_FILES]# ndiswrapper -a 0cf3:0002 athfmwdl
couldn't create symlink for "0CF3:0002.F.conf" -
installation may be incomplete
couldn't create symlink for "0CF3:0004.F.conf" -
installation may be incomplete
couldn't create symlink for "0CF3:0006.F.conf" -
installation may be incomplete
couldn't create symlink for "168C:0002.F.conf" -
installation may be incomplete
driver 'athfmwdl' is not installed (properly)!
[root@localhost Win2000-XP.zip_FILES]#

sinon c'est bon pour net5523

#14 Re : [Anciennes versions] Réseaux » Configuration WIFI (chipset Atheros Communications, Inc.) » 24/04/2007 21:01:57

Commen on fait fonctionner ndiswrapper?? j'ai un piti problème la.

[root@localhost Win2000-XP.zip_FILES]# ndiswrapper -i net5523.inf
installing net5523 ...
couldn't open net5523.inf: Aucun fichier ou répertoire de ce type at /usr/sbin/ndiswrapper line 166.
[root@localhost Win2000-XP.zip_FILES]# ndiswrapper -i net5523
installing net5523 ...
couldn't open net5523.inf: Aucun fichier ou répertoire de ce type at /usr/sbin/ndiswrapper line 166.

j'ai essayé sa mais bon ( j'ai desinstaller les pilotes avant de les réinstaller.

#15 Re : [Anciennes versions] Réseaux » Configuration WIFI (chipset Atheros Communications, Inc.) » 24/04/2007 20:41:27

Me disait bien que c'était celui la smile mais c'est pas celui donc y parlaient y a marqué "tl-wn620g.inf" et pas "net5523.inf"

#16 Re : [Anciennes versions] Réseaux » Configuration WIFI (chipset Atheros Communications, Inc.) » 24/04/2007 19:54:44

Alors j'ai bien trouvé le "athfmwdl.inf" mais le "tl-wn620g.inf" n'est pas dans les pilotes fournis par ovislink. ( Il est peu etre sur windobe mais j'ai enlever le disque dur qui le contient donc si il y a un moyen de ne pas aller sur windobe smile )

#17 Re : [Anciennes versions] Réseaux » Configuration WIFI (chipset Atheros Communications, Inc.) » 24/04/2007 19:31:46

Une chtite question.... c'est normal que sa prenne du temps le "rpm --rebuilddb"?
sinon lorsque j'avait utilisé Ndiswrapper j'avait bien utilisé 2 *.inf ( ceux que windobe disait utiliser ) mais rien c'est passé a moins que je n'ait fait un truc de traves.:-|

#18 Re : [Anciennes versions] Réseaux » Configuration WIFI (chipset Atheros Communications, Inc.) » 24/04/2007 19:11:25

Alors pour les drivers linux c'est sur le site d'OVISLINK qu'on les trouve ( http://www.ovislink.fr/administration/p … /Linux.zip )
et pour ndiswrapper je l'avait desinstaller et je vien d'avoir un problème en l'installant via yum

rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->cursor: DB_RUNRECOVERY: Fatal error, run datab ase recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->get: DB_RUNRECOVERY: Fatal error, run database  recovery
error: error(-30977) getting "xorg-x11-drv-nvidia" records from Name index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->cursor: DB_RUNRECOVERY: Fatal error, run datab ase recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->get: DB_RUNRECOVERY: Fatal error, run database  recovery
error: error(-30977) getting "kmod-nvidia" records from Name index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->cursor: DB_RUNRECOVERY: Fatal error, run datab ase recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->get: DB_RUNRECOVERY: Fatal error, run database  recovery
error: error(-30977) getting "kernel" records from Name index
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->sync: DB_RUNRECOVERY: Fatal error, run databas e recovery

Removed: kernel.i686 0:2.6.18-1.2200.fc5
Dependency Removed: kmod-nvidia.i686 0:1.0.8776-1.2.6.18_1.2200.fc5 xorg-x11-drv -nvidia.i386 0:1.0.8776-1.lvn5
Dependency Installed: kernel.i686 0:2.6.20-1.2312.fc5
Updated: ndiswrapper.i386 0:1.38-1.lvn5
Dependency Updated: kmod-ndiswrapper.i686 0:1.38-1.2.6.20_1.2312.fc5
Complete!
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run dat abase recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from db->close: DB_RUNRECOVERY: Fatal error, run databa se recovery
rpmdb: PANIC: fatal region error detected; run recovery
error: db4 error(-30977) from dbenv->close: DB_RUNRECOVERY: Fatal error, run dat abase recovery

et pourtant j'arrive a le lancer via le terminal roll

#19 [Anciennes versions] Réseaux » Configuration WIFI (chipset Atheros Communications, Inc.) » 24/04/2007 18:51:12

YonX
Réponses : 36

Alors voili voilou j'ai déjà posté pour le même problème il y a longtemps mais je n'ai pas arrivé a régler le problème alors je retente.

J'ai une clef wifi de marque OVISLINK et de reference EVO-W108USB. J'ai lu que madwifi ne supporte pas le wifi en usb, j'ai installé les Drivers linux fournis avec ma clef et j'ai déjà essayé avec NDiswrapper mais la loupiote reste désespérément éteinte hmm. Je m'y suis surement mal pris c'est pourquoi je vous demande toutes les étapes pour la faire fonctionné cette clef.
roll

j'allait oublier le LSUSB me donne

Bus 001 Device 002: ID 0ac8:301b Z-Star Microelectronics Corp. ZC0301 WebCam
Bus 001 Device 001: ID 0000:0000
Bus 006 Device 005: ID 0cf3:0002 Atheros Communications, Inc.
Bus 006 Device 003: ID 059b:007e Iomega Corp.
Bus 006 Device 001: ID 0000:0000
Bus 005 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 002 Device 002: ID 0f62:8001 Acrox Technologies Co., Ltd
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000

#20 Re : [Anciennes versions] Support général » Probleme avec le NTFS » 13/03/2007 20:25:00

En fait j'ai toujours un problème moi qui n'est pas vraiment un problème. Je m'explique voila ce que m'affiche le terminal

[root@localhost ~]# mount -t ntfs-3g /dev/sda1 /media/ntfs
WARNING: Deficient FUSE kernel module detected. Some driver features are
         not available (swap file on NTFS, boot from NTFS by LILO), and
         unmount is not safe unless it's made sure the ntfs-3g process
         naturally terminates after calling 'umount'. The safe FUSE kernel
         driver is included in the official Linux kernels since version
         2.6.20-rc1, or in the FUSE 2.6.0 or later software packages,
         except the faulty FUSE version 2.6.2. Please see the next page
         for more help: http://www.ntfs-3g.org/support.html#fuse26

mais après sa tout marche l'écriture et la lecture sur ma partition. Qu'est ce que sa veut dire??

#21 Re : [Anciennes versions] Support général » Probleme avec le NTFS » 09/03/2007 23:46:06

C'est boooooooooooon sa marche enfin ba dit donc il c'est fait attendre pour un truc tout con merci a vous ^^

#22 Re : [Anciennes versions] Support général » Probleme avec le NTFS » 09/03/2007 03:26:30

Alors liho voila ce que sa me marque
|code][root@localhost ~]# yum list installed fuse ntfs-3g
Loading "installonlyn" plugin
Installed Packages
fuse.i386                                2.6.3-1.fc5            installed
ntfs-3g.i386                             2:1.0-1.fc5            installed
[root@localhost ~]# mount -t ntfs-3g /dev/sda1 /media/ntfs
$LogFile indicates unclean shutdown (0, 0)
Failed to mount '/dev/sda1': Opération non supportée
Mount is denied because NTFS logfile is unclean. Choose one action:
   Boot Windows and shutdown it cleanly, or if you have a removable
   device then click the 'Safely Remove Hardware' icon in the Windows
   taskbar notification area before disconnecting it.
Or
   Run 'ntfsfix' on Linux unless you have Vista, then mount NTFS with
   the 'force' option read-write, or with the 'ro' option read-only.
Or
   Mount the NTFS volume with the 'ro' option in read-only mode.
[root@localhost ~]#
{/code]

J'ai pas tout saisie. C'est un problème lié a windows ou a une mauvaise fermeture de mon DD???

#23 Re : [Anciennes versions] Support général » Probleme avec le NTFS » 07/03/2007 21:37:10

quel mises a jour et commen rebooter en selinux=o? en mettant I au démarrage?

MINCE je viens de voire une erreur de ma part j'ai du faire une erreur quand j'ai choisi la categorie je suis sous fedora cor 5 et non 6 comment déplacer le sujet?

#24 Re : [Anciennes versions] Support général » Probleme avec le NTFS » 07/03/2007 21:17:45

Ba justement mon problème c'est que SElinux est déjà en "permissive" ^^'

#25 Re : [Anciennes versions] Support général » Probleme avec le NTFS » 07/03/2007 21:06:45

Voila les dernières lignes de "dmesg"

audit(1173285090.382:29): avc:  denied  { read write } for  pid=7078 comm="modprobe" name="fuse.ko" dev=dm-0 ino=1621425 scontext=system_u:system_r:mount_t:s0 tcontext=system_u:object_r:modules_object_t:s0 tclass=file
audit(1173285090.382:30): avc:  denied  { lock } for  pid=7078 comm="modprobe" name="fuse.ko" dev=dm-0 ino=1621425 scontext=system_u:system_r:mount_t:s0 tcontext=system_u:object_r:modules_object_t:s0 tclass=file
audit(1173285090.384:31): avc:  denied  { getattr } for  pid=7078 comm="modprobe" name="fuse.ko" dev=dm-0 ino=1621425 scontext=system_u:system_r:mount_t:s0 tcontext=system_u:object_r:modules_object_t:s0 tclass=file
audit(1173285090.601:32): avc:  denied  { sys_module } for  pid=7078 comm="modprobe" capability=16 scontext=system_u:system_r:mount_t:s0 tcontext=system_u:system_r:mount_t:s0 tclass=capability
fuse init (API version 7.7)
audit(1173285090.722:33): avc:  denied  { getattr } for  pid=7077 comm="mount.ntfs" name="fuse" dev=tmpfs ino=1221 scontext=system_u:system_r:mount_t:s0 tcontext=system_u:object_r:device_t:s0 tclass=chr_file
audit(1173286055.519:34): avc:  denied  { search } for  pid=7657 comm="mount.ntfs" scontext=system_u:system_r:mount_t:s0 tcontext=system_u:object_r:sysctl_kernel_t:s0 tclass=dir
audit(1173294333.059:35): avc:  denied  { getattr } for  pid=9096 comm="mount.ntfs" name="fuse" dev=tmpfs ino=1221 scontext=system_u:system_r:mount_t:s0 tcontext=system_u:object_r:device_t:s0 tclass=chr_file
[root@localhost ~]#

Pied de page des forums

Propulsé par FluxBB