Bonjour,

J'ai un souci avec F15, en démarrant sur le live CD de la beta, j'ai réussi à accéder à gnome 3 sans souci, en revanche lorsque j'installe F15 avec le DVD, au démarrage j'ai le message m'indiquant que je n'ai pas le hardware correspondant pour faire tourner gnome 3.
Voici mes caractéristiques :

J'ai un processeur sandy bridge avec donc une partie graphique intégrée au processeur, c'est elle qui a permis de lancer gnome 3 en live CD je suppose..
J'ai également un Carte graphique dédiée qui est une ATI 6630M et celle-ci n'est visiblement pas supporté.

voici le lspci: 
# lspci
00:00.0 Host bridge: Intel Corporation Sandy Bridge DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Sandy Bridge PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Device 0116 (rev 09)
00:16.0 Communication controller: Intel Corporation Cougar Point HECI Controller #1 (rev 04)
00:1a.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation Cougar Point High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 1 (rev b5)
00:1c.2 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 3 (rev b5)
00:1c.4 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 5 (rev b5)
00:1c.5 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 6 (rev b5)
00:1d.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation Cougar Point LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation Cougar Point 6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation Cougar Point SMBus Controller (rev 05)
01:00.0 VGA compatible controller: ATI Technologies Inc Device 6741
02:00.0 Network controller: Intel Corporation Device 008a (rev 34)
03:00.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)

----------------------- Souci carte Wifi résolu:

J'ai eu un souci avec ma carte wifi qui n'est pas reconnue out of the box, c'est un centrino 1030N, j'ai lu que le driver iwl6000g2b fonctionnait. 
su -
yum install iwl6000g2b-firmware
et un reboot reglent le problème, cela pourra aider ceux qui ont le même souci..

Pour info je suis sur un dell vostro 3450 avec core i5 2410
http://www.x.org/wiki/RadeonFeature

Si j'ai bien lu les Radeon HD 6630M (ou modèle Turks) seront supportés pour le kernel 2.6.38. autant dire que ça ne sera pas immédiat. J'ai lu aussi qu'il peut y avoir un support 3D pour une version MESA 7.11 (on est 7.9) pour radeon.

Sinon attendre le pilote Catalyst 11.3 soit intégré au dépôt RPMFusion, qui est sortie il y a peu de chez AMD.
Faire un essai avec la 11.2 qui devrait somme toute marcher.
Demander à VINDICATORS pour être sûr (c'est comme même la bible du driver sur ce forum).

Source :
1/ http://www.phoronix.com/scan.php?page=news_item&px=OTM2Mg
2/ Mémoire : n'est pas toujours fiable.
Merci pour ces precisions, je suis en 2.6.38, sous F15 😉
je me demandais si je pouvais reussir a installer les pilotes du chipset integre.. j'ai vu que certaines personnes avaient reussies à les installer sur f14 en mettant a jour avec les depots rawhide, du coup sur f15 cela devrait fonctionner non ? Je ne sais pas trop ou chercher..
Je souhaite faire fonctionner le chipset étant donné que cela consomme moins, pour la CG elle m'est inutile sur Fedora
Tu me poses une colle. Je ne suis pas du tout familiarisé avec les chipsets intégrés, mais je suis intéressé si tu trouves des infos car mon prochain PC sera sûrement équipé de la sorte.

Je ne connais pas exactement la marche à suivre pour bien éditer son fichier de config Xorg. Est-ce que le serveur X.org gère automatiquement le chipset intel, ou est-ce qu'un 'X -configure' suffit.
Je me pose beaucoup de questions, j'ai hâte que les problèmes arrivent. :-D

J'ai trouvé ça, qui à l'air intéressant, mais ce n'est ni plus ni moins ce que tu disais (rendre effectif le chipset sur F14 grâce au dépôt Rawhide).
http://phoronix.com/forums/showthread.php?28092-Intel-Sandy-Bridge-Linux-Graphics-It-s-A-Challenge/page6

La démarche à suivre doit être proche.
Je ne sais pas quelle version est la mieux.. j'ai ça moi : 
rpm -qa |grep xorg-x11-drv-intel
xorg-x11-drv-intel-2.14.0-5.fc15.x86_64
J'ai posté sur le forum anglais ici : http://www.fedoraforum.org/forum/showthread.php?t=262184, et j'ai eu une réponse, qui semblait encourageante mais ne fonctionne pas pour moi:
l'ajout de radeon.modeset=0 à la ligne du kernel, en verifiant qu'il n'y ait pas de nomodeset sur la ligne
j'ai plymouth qui se lance (donc cela est mieux que les barres) mais en revanche j'aboutie sur un ligne du style 
mkdir : cannot create directory "/run" file exists
et je ne peux pas aller plus loin.. j'ai bien essayé de faire un backup et de supprimer /run mais impossible car occupé..

Juste après cette ligne s'en suit une serie de warning rouge:
Unable to fix label of /sys/fs/cgroup/systemd: No such file or directory
Unable to fix label of /sys/fs/cgroup/cpuset: No such file or directory
Unable to fix label of /sys/fs/cgroup/ns: No such file or directory
Unable to fix label of /sys/fs/cgroup/cpu: No such file or directory
Unable to fix label of /sys/fs/cgroup/cpuacct: No such file or directory
Unable to fix label of /sys/fs/cgroup/memory: No such file or directory
Unable to fix label of /sys/fs/cgroup/devices: No such file or directory
Unable to fix label of /sys/fs/cgroup/freezer: No such file or directory
Unable to fix label of /sys/fs/cgroup/net_cls: No such file or directory
Unable to fix label of /sys/fs/cgroup/blkio: No such file or directory
c'est un bug qui a été reporté, je ne sais pas si c'est lié..

une idée ?
visiblement ces soucis n'ont rien a voir avec mon problème.. voici mes log :

lorsque j'ai radeon.modeset=0 et qu'il ne boot pas en graphique:
]cat ~/Documents/logboot 
Unable to fix label of /sys/fs/cgroup/systemd: No such file or directory
Unable to fix label of /sys/fs/cgroup/cpuset: No such file or directory
Unable to fix label of /sys/fs/cgroup/ns: No such file or directory
Unable to fix label of /sys/fs/cgroup/cpu: No such file or directory
Unable to fix label of /sys/fs/cgroup/cpuacct: No such file or directory
Unable to fix label of /sys/fs/cgroup/memory: No such file or directory
Unable to fix label of /sys/fs/cgroup/devices: No such file or directory
Unable to fix label of /sys/fs/cgroup/freezer: No such file or directory
Unable to fix label of /sys/fs/cgroup/net_cls: No such file or directory
Unable to fix label of /sys/fs/cgroup/blkio: No such file or directory

Welcome to Fedora release 15 (Lovelock)!

Started Replay Read-Ahead Data.
Starting Collect Read-Ahead Data...
Starting Bootup hack...
Starting Syslog Kernel Log Buffer Bridge...
Started Syslog Kernel Log Buffer Bridge.
Started Lock Directory.
Started Runtime Directory.
Starting Media Directory...
Started Collect Read-Ahead Data.
Starting Load legacy module configuration...
Starting Remount API VFS...
Started File System Check on Root Device.
Starting Remount Root FS...
Starting Apply System Clock UTC Offset...
Started Set Up Additional Binary Formats.
Started Load Kernel Modules.
Starting Apply Kernel Variables...
Starting Setup Virtual Console...
Starting Stdio Syslog Bridge...
Started Stdio Syslog Bridge.
Started Bootup hack.
Started Apply Kernel Variables.
Started Apply System Clock UTC Offset.
Starting udev Kernel Device Manager...
Started Media Directory.
Started Remount API VFS.
Started Remount Root FS.
Starting Configure read-only root support...
Started Load legacy module configuration.
Started Setup Virtual Console.
Started Configure read-only root support.
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/disk/by-uuid/d78213ca-d309-4102-9679-3ca37cf41633...
Starting File System Check on /dev/disk/by-uuid/0ef280d1-1cf4-4953-aefc-0f5d222faef4...
Started /dev/disk/by-uuid/d78213ca-d309-4102-9679-3ca37cf41633.
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.)...
systemd-fsck[653]: /dev/sda5*: propre, 486/3203072 fichiers, 266244/12800000 blocs
Started File System Check on /dev/disk/by-uuid/0ef280d1-1cf4-4953-aefc-0f5d222faef4.
Starting /home...
Started /home.
Started Initialize storage subsystems (RAID, LVM, etc.).
Starting Enable all detected swap partitions...
Started Mark the need to relabel after reboot.
Started Reconfigure the system on administrator request.
Started Relabel all filesystems, if necessary.
Starting Tell Plymouth To Write Out Runtime Data...
Starting Recreate Volatile Files and Directories...
Starting Load Random Seed...
Started Enable all detected swap partitions.
Started Tell Plymouth To Write Out Runtime Data.
Started Load Random Seed.
Started Recreate Volatile Files and Directories.
Starting Restore Sound Card State...
Starting Console System Startup Logging...
Starting Bootup unhack...
Starting ACPI Event Daemon...
Starting SYSV: sandbox, xguest and other apps that want to use pam_namespace require this script be run at boot.  This service script does not actually run any service but sets up: /var/tmp, /tmp and home directories to be used by these tools. If you do not use sandbox, xguest or pam_namespace you can turn this service off....
Starting System Logging Service...
Starting ABRT Automated Bug Reporting Tool...
Starting Command Scheduler...
Started Command Scheduler.
Starting Console Mouse manager...
Starting Network Manager...
Starting Job spooling tools...
Started Job spooling tools.
Starting Self Monitoring and Reporting Technology (SMART) Daemon...
Started Self Monitoring and Reporting Technology (SMART) Daemon.
Starting Machine Check Exception Logging Daemon...
Starting irqbalance daemon...
Starting System Setup Keyboard...
Started System Setup Keyboard.
Starting D-Bus System Message Bus...
Started Restore Sound Card State.
Started Console System Startup Logging.
Started Bootup unhack.
Started ACPI Event Daemon.
Started SYSV: sandbox, xguest and other apps that want to use pam_namespace require this script be run at boot.  This service script does not actually run any service but sets up: /var/tmp, /tmp and home directories to be used by these tools. If you do not use sandbox, xguest or pam_namespace you can turn this service off..
Started Console Mouse manager.
Started Machine Check Exception Logging Daemon.
Started irqbalance daemon.
Starting LSB: start and stop ip6tables firewall...
Starting LSB: start and stop iptables firewall...
Starting LSB: Port reservation utility...
Started D-Bus System Message Bus.
Started LSB: start and stop ip6tables firewall.
Started LSB: start and stop iptables firewall.
Started LSB: Port reservation utility.
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....
Started ABRT Automated Bug Reporting Tool.
Stopping Syslog Kernel Log Buffer Bridge...
Stopped Syslog Kernel Log Buffer Bridge.
Started System Logging Service.
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 LSB: processor frequency scaling support.
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: Installs coredump handler which saves segfault data...
Starting LSB: Mount and unmount network filesystems....
Starting LSB: Start and stop the MD software RAID monitor...
Starting LSB: The CUPS scheduler...
Started LSB: Installs coredump handler which saves segfault data.
Started Network Manager.
Starting LSB: Start up the OpenSSH server daemon...
Starting LSB: Start up the NFS file locking sevice...
Starting LSB: Starts the NFSv4 id mapping daemon...
Starting LSB: Starts the RPCSEC GSS client daemon...
Starting LSB: start and stop sendmail...
Starting Set time via NTP...
Started LSB: Mount and unmount network filesystems..
Starting LSB: Daemon to access a smart card using PC/SC...
Starting Permit User Sessions...
Started LSB: Starts the RPCSEC GSS client daemon.
Started Permit User Sessions.
Started LSB: Daemon to access a smart card using PC/SC.
Started LSB: Start and stop the MD software RAID monitor.
Started LSB: Start up the NFS file locking sevice.
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.
Starting SYSV: Enable monthly update of Smolt...
Started SYSV: Enable monthly update of Smolt
et lorsqu'il boot (avec simplement nomodeset) :
cat /var/log/boot.log
Unable to fix label of /sys/fs/cgroup/systemd: No such file or directory
Unable to fix label of /sys/fs/cgroup/cpuset: No such file or directory
Unable to fix label of /sys/fs/cgroup/ns: No such file or directory
Unable to fix label of /sys/fs/cgroup/cpu: No such file or directory
Unable to fix label of /sys/fs/cgroup/cpuacct: No such file or directory
Unable to fix label of /sys/fs/cgroup/memory: No such file or directory
Unable to fix label of /sys/fs/cgroup/devices: No such file or directory
Unable to fix label of /sys/fs/cgroup/freezer: No such file or directory
Unable to fix label of /sys/fs/cgroup/net_cls: No such file or directory
Unable to fix label of /sys/fs/cgroup/blkio: No such file or directory

Welcome to Fedora release 15 (Lovelock)!

Started Replay Read-Ahead Data.
Starting Collect Read-Ahead Data...
Starting Bootup hack...
Starting Syslog Kernel Log Buffer Bridge...
Started Syslog Kernel Log Buffer Bridge.
Started Lock Directory.
Started Runtime Directory.
Starting Media Directory...
Started Collect Read-Ahead Data.
Starting Load legacy module configuration...
Starting Remount API VFS...
Started File System Check on Root Device.
Starting Remount Root FS...
Starting Apply System Clock UTC Offset...
Started Set Up Additional Binary Formats.
Started Load Kernel Modules.
Starting Apply Kernel Variables...
Starting Setup Virtual Console...
Starting Stdio Syslog Bridge...
Started Stdio Syslog Bridge.
Started Bootup hack.
Started Apply System Clock UTC Offset.
Started Apply Kernel Variables.
Starting udev Kernel Device Manager...
Started Media Directory.
Started Remount API VFS.
Started Load legacy module configuration.
Started Remount Root FS.
Started Setup Virtual Console.
Starting Configure read-only root support...
Started Configure read-only root support.
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 File System Check on /dev/disk/by-uuid/0ef280d1-1cf4-4953-aefc-0f5d222faef4...
Starting /dev/disk/by-uuid/d78213ca-d309-4102-9679-3ca37cf41633...
Started /dev/disk/by-uuid/d78213ca-d309-4102-9679-3ca37cf41633.
Started udev Wait for Complete Device Initialization.
Starting Wait for storage scan...
systemd-fsck[608]: /dev/sda5 : propre, 495/3203072 fichiers, 266263/12800000 blocs
Started Show Plymouth Boot Screen.
Started File System Check on /dev/disk/by-uuid/0ef280d1-1cf4-4953-aefc-0f5d222faef4.
Starting /home...
Started Wait for storage scan.
Starting Initialize storage subsystems (RAID, LVM, etc.)...
Started /home.
Started Initialize storage subsystems (RAID, LVM, etc.).
Starting Enable all detected swap partitions...
Started Mark the need to relabel after reboot.
Started Reconfigure the system on administrator request.
Started Relabel all filesystems, if necessary.
Starting Tell Plymouth To Write Out Runtime Data...
Starting Recreate Volatile Files and Directories...
Starting Load Random Seed...
Started Enable all detected swap partitions.
Started Tell Plymouth To Write Out Runtime Data.
Started Load Random Seed.
Started Recreate Volatile Files and Directories.
Starting Restore Sound Card State...
Starting Console System Startup Logging...
Starting Bootup unhack...
Starting ACPI Event Daemon...
Starting SYSV: sandbox, xguest and other apps that want to use pam_namespace require this script be run at boot. This service script does not actually run any service but sets up: /var/tmp, /tmp and home directories to be used by these tools. If you do not use sandbox, xguest or pam_namespace you can turn this service off....
Starting System Logging Service...
Starting ABRT Automated Bug Reporting Tool...
Starting Command Scheduler...
Started Command Scheduler.
Starting Console Mouse manager...
Starting Network Manager...
Starting Job spooling tools...
Started Job spooling tools.
Starting Self Monitoring and Reporting Technology (SMART) Daemon...
Started Self Monitoring and Reporting Technology (SMART) Daemon.
Starting Machine Check Exception Logging Daemon...
Starting irqbalance daemon...
Starting System Setup Keyboard...
Started System Setup Keyboard.
Starting D-Bus System Message Bus...
Started Restore Sound Card State.
Started Console System Startup Logging.
Started Bootup unhack.
Started ACPI Event Daemon.
Started SYSV: sandbox, xguest and other apps that want to use pam_namespace require this script be run at boot. This service script does not actually run any service but sets up: /var/tmp, /tmp and home directories to be used by these tools. If you do not use sandbox, xguest or pam_namespace you can turn this service off..
Started Console Mouse manager.
Started irqbalance daemon.
Starting LSB: start and stop ip6tables firewall...
Starting LSB: start and stop iptables firewall...
Starting LSB: Port reservation utility...
Started Machine Check Exception Logging Daemon.
Started D-Bus System Message Bus.
Started LSB: start and stop ip6tables firewall.
Started LSB: start and stop iptables firewall.
Started LSB: Port reservation utility.
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....
Stopping Syslog Kernel Log Buffer Bridge...
Started ABRT Automated Bug Reporting Tool.
Stopped Syslog Kernel Log Buffer Bridge.
Started System Logging Service.
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 LSB: processor frequency scaling support.
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: Installs coredump handler which saves segfault data...
Starting LSB: Mount and unmount network filesystems....
Starting LSB: Start and stop the MD software RAID monitor...
Starting LSB: The CUPS scheduler...
Started Network Manager.
Starting LSB: Start up the OpenSSH server daemon...
Starting LSB: Start up the NFS file locking sevice...
Starting LSB: Starts the NFSv4 id mapping daemon...
Starting LSB: Starts the RPCSEC GSS client daemon...
Starting LSB: start and stop sendmail...
Starting Set time via NTP...
Started LSB: Starts the RPCSEC GSS client daemon.
Started LSB: Installs coredump handler which saves segfault data.
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.
Started LSB: Daemon to access a smart card using PC/SC.
Started LSB: Start up the NFS file locking sevice.
Started LSB: Start and stop the MD software RAID monitor.
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.
Starting SYSV: Enable monthly update of Smolt...
Started SYSV: Enable monthly update of Smolt.
Je n'arrive pas à voir ce qui cloche.. ni où je pourrais trouver mon souci..
ta quel version de mesa? parce que normalement ça arrive et commence à être en place avec Fedora 15, mais à voir si cela ne sera pas effectif juste dans quelques temps.

Le support ira quand même plus vite que pour les HD5xxx (R8xx).

Il faudrait le rapport de xorg, car là...
Merci pour la reponse, le rapport de xorg se trouve ou exactement ?
Merci pour la reponse, le rapport de xorg se trouve ou exactement ?
/var/log/Xorg.0.log

Une demande de réponse c'était bon, pas que cela à faire non plus!
Ok merci je posterai ca des mon retour je ne suis plus chez moi. Sorry pour le dual post envoi depuis un portable et beug visiblement..
4 jours plus tard
J'ai trouvé le truc, il faut modifier le /etc/X11/xorg.conf comme cela :
Section "Device"
    Identifier "Videocard0"
    Driver "intel"
    BusId "PCI:0:2:0"
EndSection
ça m'a résolu mon problème, à moi gnome 3 maintenant ! haha