Fifi wrote:Bizarre : l'akmod-wl que tu as installé après avoir viré les kmod-wl ne t'a pas reconstruit de kmod-wl ! Comme paquet installé, tu n'as que l'akmod-wl, les kmod-wl sont dans les paquets disponibles mais pas installés !!! Tu es sûr du retour de ta commande yum list *kmod-wl* ?
Oui, désolé. Je me suis rendu compte de mon erreur après coup.
Après avoir déinstallé kmod-wl puis installé akmod-wl, j'ai redémarré mon PC.
Là, j'ai constaté que j'avais de nouveau de kmod-wl.
Je n'avais pas compris que akmod-wl me reconstruisait les kmod-wl.
J'ai donc de nouveau désinstallé les kmod-wl.
D'où le retour ci-dessus de la commande yum list *kmod-wl*.
Pour repartir d'une situation propre, j'ai désinstallé kmod-wl et akmod-wl.
Puis j'ai réinstallé akmod-wl.
[root@DELL15 ~]# yum install akmod-wl
Modules complémentaires chargés : presto, refresh-packagekit
Configuration du processus d'installation
Résolution des dépendances
--> Lancement de la transaction de test
---> Package akmod-wl.i686 0:5.60.48.36-2.fc14 will be installé
--> Traitement de la dépendance : wl-kmod-common >= 5.60.48.36 pour le paquet : akmod-wl-5.60.48.36-2.fc14.i686
--> Lancement de la transaction de test
---> Package broadcom-wl.noarch 0:5.60.48.36-1.fc13 will be installé
--> Résolution des dépendances terminée
Dépendances résolues
=========================================================================
Paquet Architecture
Version Dépôt Taille
=========================================================================
Installation:
akmod-wl i686 5.60.48.36-2.fc14 rpmfusion-nonfree-rawhide 1.7 M
Installation pour dépendance:
broadcom-wl noarch 5.60.48.36-1.fc13 rpmfusion-nonfree-rawhide 13 k
Résumé de la transaction
=========================================================================
Installation de 2 paquet(s)
Taille totale des téléchargements : 1.7 M
Taille d'installation : 1.7 M
Est-ce correct [o/N] : o
Téléchargement des paquets :
Setting up and reading Presto delta metadata
Processing delta metadata
Package(s) data still to download: 1.7 M
(1/2): akmod-wl-5.60.48.36-2.fc14.i686.rpm | 1.7 MB 00:01
(2/2): broadcom-wl-5.60.48.36-1.fc13.noarch.rpm | 13 kB 00:00
-------------------------------------------------------------------------
Total 921 kB/s | 1.7 MB 00:01
Lancement de rpm_check_debug
Lancement de la transaction de test
Transaction de test réussie
Lancement de la transaction
Installation : broadcom-wl-5.60.48.36-1.fc13.noarch 1/2
Installation : akmod-wl-5.60.48.36-2.fc14.i686 2/2
Installé:
akmod-wl.i686 0:5.60.48.36-2.fc14
Dépendance(s) installée(s) :
broadcom-wl.noarch 0:5.60.48.36-1.fc13
Terminé !
Deux surprises : les deux packages installés sont pour fc14 et fc13
1) akmod-wl i686 5.60.48.36-2.fc14
2) broadcom-wl.noarch 0:5.60.48.36-1.fc13
Pourquoi pas pour Fedora 15 ?
J'ai rebooté pour que akmod-wl me génère les kmod-wl.
Toujours pas de kmod-wl.
J'ai de nouveau rebooté en regardant cette fois-ci les informations qui s'affichent lors lors du démarrage.
J'ai donc regardé dans /var/log/boot.log
Welcome to [0;34mFedora release 15 (Lovelock)[0m!
Starting Bootup hack...
Started Load legacy module configuration.
Starting Apply Kernel Variables...
Starting Syslog Kernel Log Buffer Bridge...
Started Syslog Kernel Log Buffer Bridge.
Started Load Kernel Modules.
Started Set Up Additional Binary Formats.
Starting udev Kernel Device Manager...
Started File System Check on Root Device.
Starting Media Directory...
Starting Runtime Directory...
Starting Remount Root FS...
Starting Lock Directory...
Starting Remount API VFS...
Starting Setup Virtual Console...
Started Bootup hack.
Started Apply Kernel Variables.
Started Runtime Directory.
Started Media Directory.
Started Lock Directory.
Starting Stdio Syslog Bridge...
Started Stdio Syslog Bridge.
Started Remount API VFS.
Started Remount Root FS.
Starting Configure read-only root support...
Started Configure read-only root support.
Started Setup Virtual Console.
Started udev Kernel Device Manager.
Starting udev Coldplug all Devices...
Started udev Coldplug all Devices.
Starting udev Wait for Complete Device Initialization...
Started udev Kernel Device Manager.
Starting /dev/mapper/vg_dell15-lv_swap...
%GStarted /dev/mapper/vg_dell15-lv_swap.
Starting File System Check on /dev/disk/by-uuid/70a1c164-6ec2-4e61-bd1b-98d804da9522...
Starting Huge Pages File System...
Started Huge Pages File System.
Starting POSIX Message Queue File System...
Started POSIX Message Queue File System.
systemd-fsck[783]: /dev/sda5 : propre, 57/128016 fichiers, 139732/512000 blocs
Started File System Check on /dev/disk/by-uuid/70a1c164-6ec2-4e61-bd1b-98d804da9522.
Starting /boot...
Started /boot.
Started udev Wait for Complete Device Initialization.
Starting Wait for storage scan...
Started Show Plymouth Boot Screen.
Started Wait for storage scan.
Starting Initialize storage subsystems (RAID, LVM, etc.)...
Starting File System Check on /dev/mapper/vg_dell15-lv_opt...
Starting File System Check on /dev/mapper/vg_dell15-lv_home...
Started Initialize storage subsystems (RAID, LVM, etc.).
Starting Initialize storage subsystems (RAID, LVM, etc.)...
systemd-fsck[832]: /dev/mapper/vg_dell15-lv_opt : propre, 42707/1281120 fichiers, 638611/5120000 blocs
systemd-fsck[834]: /dev/mapper/vg_dell15-lv_home : propre, 428233/11739136 fichiers, 16317852/46940160 blocs
Started File System Check on /dev/mapper/vg_dell15-lv_home.
Starting /home...
Started File System Check on /dev/mapper/vg_dell15-lv_opt.
Starting /opt...
Started /home.
Started /opt.
Started Initialize storage subsystems (RAID, LVM, etc.).
Starting Tell Plymouth To Write Out Runtime Data...
Starting Load Random Seed...
Started Reconfigure the system on administrator request.
Started Mark the need to relabel after reboot.
Started Relabel all filesystems, if necessary.
Starting Enable all detected swap partitions...
Starting Recreate Volatile Files and Directories...
Started Tell Plymouth To Write Out Runtime Data.
Started Load Random Seed.
Started Enable all detected swap partitions.
Started Recreate Volatile Files and Directories.
Starting Bootup unhack...
Starting Console System Startup Logging...
Starting Restore Sound Card State...
Starting ABRT Automated Bug Reporting Tool...
Starting Avahi mDNS/DNS-SD Stack...
Starting LSB: Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Starting LSB: Builds and install new kmods from akmod packages...
Starting Network Manager...
Starting LSB: Port reservation utility...
Starting LSB: start and stop ip6tables firewall...
Starting LSB: start and stop iptables firewall...
Starting Job spooling tools...
Started Job spooling tools.
Starting irqbalance daemon...
Starting Command Scheduler...
Started Command Scheduler.
Starting D-Bus System Message Bus...
Started Bootup unhack.
Started Console System Startup Logging.
Started Restore Sound Card State.
Started D-Bus System Message Bus.
[b]Starting LSB: Builds and install new kmods from akmod packages [1;31mfailed[0m, see 'systemctl status akmods.service' for details.[/b]
Started LSB: Port reservation utility.
Started LSB: start and stop iptables firewall.
Started irqbalance daemon.
Started Avahi mDNS/DNS-SD Stack.
Started ABRT Automated Bug Reporting Tool.
Started LSB: start and stop ip6tables firewall.
Started LSB: Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Starting SYSV: This starts the Linux Auditing System Daemon, which collects security related events in a dedicated audit log. If this daemon is turned off, audit events will be sent to syslog....
Starting Bluetooth Manager...
Started Network Manager.
Started SYSV: This starts the Linux Auditing System Daemon, which collects security related events in a dedicated audit log. If this daemon is turned off, audit events will be sent to syslog..
Starting LSB: processor frequency scaling support...
Starting SYSV: The rpcbind utility is a server that converts RPC program numbers into universal addresses. It must be running on the host to be able to make RPC calls on a server on that machine....
Started Bluetooth Manager.
Started SYSV: The rpcbind utility is a server that converts RPC program numbers into universal addresses. It must be running on the host to be able to make RPC calls on a server on that machine..
Starting LSB: Start and stop the MD software RAID monitor...
Starting LSB: Starts the NFSv4 id mapping daemon...
Starting LSB: Start up the OpenSSH server daemon...
Starting LSB: Installs coredump handler which saves segfault data...
Starting LSB: Start up the NFS file locking sevice...
Starting LSB: start and stop sendmail...
Starting LSB: Starts the RPCSEC GSS client daemon...
Starting LSB: The CUPS scheduler...
Starting LSB: Mount and unmount network filesystems....
Starting /etc/rc.local Compatibility...
Started LSB: processor frequency scaling support.
Started /etc/rc.local Compatibility.
Starting Wait for Plymouth Boot Screen to Quit...
Started LSB: Starts the RPCSEC GSS client daemon.
Started LSB: Start and stop the MD software RAID monitor.
Started LSB: Start up the NFS file locking sevice.
Started LSB: Installs coredump handler which saves segfault data.
Started LSB: Starts the NFSv4 id mapping daemon.
Started LSB: Start up the OpenSSH server daemon.
Started LSB: The CUPS scheduler.
Started LSB: start and stop sendmail.
Started LSB: Mount and unmount network filesystems..
Starting LSB: Daemon to access a smart card using PC/SC...
Starting Permit User Sessions...
Started Permit User Sessions.
Starting Display Manager...
Started Display Manager.
Started LSB: Daemon to access a smart card using PC/SC.
Là je voit que tout se passe correctement à l’exception d'une ligne :
Build and install kmod from akmod package: FAILD
see 'systemctl status akmod.service' for details
Cette dernière commande me donne alors :
[root@DELL15 ~]# systemctl status akmod.service
akmod.service
Loaded: error
Active: inactive (dead)
Il n'y a pas de doute que le problème provient d'ici.