# Curseur introuvable sous Debian 8.4.0 Xfce

**URL:** <https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210>\
**Category:** Support Debian\
**Created:** [Avril 16, 2016, 9:10 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210 "2016-04-16T21:10:06Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![juvisien](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/j/3bc359/32.png) [@juvisien](https://www.debian-fr.org/u/juvisien)\
**Post date:** [Avril 16, 2016, 9:10 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/1 "2016-04-16T21:10:07Z")

</div>

Salut,

Je suis novice dans le monde de linux mais je souhaite tenter le coup.

J’ai installé une Debian 8.4.0 avec Xfce sur AMD Athlon 3000+ avec 512 Mb de RAM et une Geforce MX400.

Manque de bol, je me cogne la tête contre les murs à cause de mon curseur de souris.

Celui-ci ne s’affiche pas même si je peux cliquer, il est fonctionnel mais invisible.

Avant d’installer une Debian, j’avais testé une Lubuntu et j’ai eu exactement le même problème:

[https://forum.ubuntu-fr.org/viewtopic.php?id=1987083](https://forum.ubuntu-fr.org/viewtopic.php?id=1987083)

Quelqu’un aurait-il une idée ?

Merci d’avance !

---

<div class="post-metadata">

**Author:** ![grandtoubab](https://www.debian-fr.org/user_avatar/www.debian-fr.org/grandtoubab/32/4505_2.png) [@grandtoubab](https://www.debian-fr.org/u/grandtoubab)\
**Post date:** [Avril 16, 2016, 10:03 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/2 "2016-04-16T22:03:14Z")

</div>

salut,

`sudo tail -f kern.log`

Puis branche la souris, quels sont les messages??

Exemple:

```
Apr 16 23:58:04 debian kernel: [12741.345235] usb 5-1: new full-speed USB device number 4 using ohci-pci
Apr 16 23:58:04 debian kernel: [12741.546435] usb 5-1: New USB device found, idVendor=046d, idProduct=c52f
Apr 16 23:58:04 debian kernel: [12741.546448] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 16 23:58:04 debian kernel: [12741.546455] usb 5-1: Product: USB Receiver
Apr 16 23:58:04 debian kernel: [12741.546461] usb 5-1: Manufacturer: Logitech
Apr 16 23:58:04 debian kernel: [12741.555502] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:13.0/usb5/5-1/5-1:1.0/0003:046D:C52F.0005/input/input20
Apr 16 23:58:04 debian kernel: [12741.555854] hid-generic 0003:046D:C52F.0005: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:13.0-1/input0
Apr 16 23:58:04 debian kernel: [12741.562558] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:13.0/usb5/5-1/5-1:1.1/0003:046D:C52F.0006/input/input21
Apr 16 23:58:04 debian kernel: [12741.618412] hid-generic 0003:046D:C52F.0006: input,hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:13.0-1/input1
```

---

<div class="post-metadata">

**Author:** ![avram](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/b38774/32.png) [@avram](https://www.debian-fr.org/u/avram)\
**Post date:** [Avril 16, 2016, 10:43 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/3 "2016-04-16T22:43:51Z")

</div>

> [@](#):
>
> Geforce MX400

il faudrait connaître le nom exact de la carte,je pense que c’est une nvidia legacy ancienne et que votre problème de curseur peut bien être un problème de pilote pour cette carte.Quel pilote est installé actuellement?

Donnez la sortie de la commande, en simple user:

lspci -v:

---

<div class="post-metadata">

**Author:** ![juvisien](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/j/3bc359/32.png) [@juvisien](https://www.debian-fr.org/u/juvisien)\
**Post date:** [Avril 17, 2016, 2:00 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/4 "2016-04-17T02:00:58Z")

</div>

Voici les données obtenues:

```
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 760/M760 Host (rev 02)

    Subsystem: Hewlett-Packard Company Device 2a04

    Flags: bus master, medium devsel, latency 32

    Memory at e0000000 (32-bit, non-prefetchable) [size=64M]

    Capabilities: <access denied>

    Kernel driver in use: agpgart-amd64

00:01.0 PCI bridge: Silicon Integrated Systems [SiS] AGP Port (virtual PCI-to-PCI bridge) (prog-if 00 [Normal decode])

    Flags: bus master, 66MHz, medium devsel, latency 99

    Bus: primary=00, secondary=01, subordinate=01, sec-latency=32

    Memory behind bridge: e8000000-e9ffffff

    Prefetchable memory behind bridge: e4000000-e7ffffff

00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] LPC Controller (rev 36)

    Flags: bus master, medium devsel, latency 0

00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 IDE Controller (rev 01) (prog-if 80 [Master])

    Subsystem: Hewlett-Packard Company Device 2a04

    Flags: bus master, medium devsel, latency 128

    I/O ports at 01f0 [size=8]

    I/O ports at 03f4

    I/O ports at 0170 [size=8]

    I/O ports at 0374

    I/O ports at 4000 [size=16]

    Kernel driver in use: pata_sis

00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS7012 AC'97 Sound Controller (rev a0)

    Subsystem: Hewlett-Packard Company Device 2a05

    Flags: bus master, medium devsel, latency 32, IRQ 18

    I/O ports at c000 [size=256]

    I/O ports at c400 [size=128]

    Capabilities: <access denied>

    Kernel driver in use: snd_intel8x0

00:03.0 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI])

    Subsystem: Hewlett-Packard Company Device 2a04

    Flags: bus master, medium devsel, latency 64, IRQ 20

    Memory at eb004000 (32-bit, non-prefetchable) [size=4K]

    Kernel driver in use: ohci-pci

00:03.1 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI])

    Subsystem: Hewlett-Packard Company Device 2a04

    Flags: bus master, medium devsel, latency 64, IRQ 21

    Memory at eb000000 (32-bit, non-prefetchable) [size=4K]

    Kernel driver in use: ohci-pci

00:03.2 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI])

    Subsystem: Hewlett-Packard Company Device 2a04

    Flags: bus master, medium devsel, latency 64, IRQ 22

    Memory at eb001000 (32-bit, non-prefetchable) [size=4K]

    Kernel driver in use: ohci-pci

00:03.3 USB controller: Silicon Integrated Systems [SiS] USB 2.0 Controller (prog-if 20 [EHCI])

    Subsystem: Hewlett-Packard Company Device 2a04

    Flags: bus master, medium devsel, latency 32, IRQ 23

    Memory at eb002000 (32-bit, non-prefetchable) [size=4K]

    Capabilities: <access denied>

    Kernel driver in use: ehci-pci

00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90)

    Subsystem: Hewlett-Packard Company Device 2a04

    Flags: bus master, medium devsel, latency 32, IRQ 19

    I/O ports at c800 [size=256]

    Memory at eb003000 (32-bit, non-prefetchable) [size=4K]

    [virtual] Expansion ROM at 20000000 [disabled] [size=128K]

    Capabilities: <access denied>

    Kernel driver in use: sis900

00:05.0 IDE interface: Silicon Integrated Systems [SiS] RAID bus 
controller 180 SATA/PATA [SiS] (rev 01) (prog-if 85 [Master SecO PriO])

    Subsystem: Hewlett-Packard Company Device 2a04

    Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17

    I/O ports at cc00 [size=8]

    I/O ports at d000 [size=4]

    I/O ports at d400 [size=8]

    I/O ports at d800 [size=4]

    I/O ports at dc00 [size=16]

    I/O ports at e000 [size=128]

    Capabilities: <access denied>

    Kernel driver in use: sata_sis

00:08.0 Multimedia controller: Philips Semiconductors SAA7134/SAA7135HL Video Broadcast Decoder (rev 01)

    Subsystem: ASUSTeK Computer Inc. TV-FM 7134

    Flags: bus master, medium devsel, latency 32, IRQ 16

    Memory at eb005000 (32-bit, non-prefetchable) [size=1K]

    Capabilities: <access denied>

    Kernel driver in use: saa7134

00:09.0 Communication controller: LSI Corporation V.92 56K WinModem (rev 03)

    Subsystem: LSI Corporation Device 044c

    Flags: bus master, medium devsel, latency 32, IRQ 255

    Memory at eb006000 (32-bit, non-prefetchable) [size=256]

    I/O ports at e400 [size=8]

    I/O ports at e800 [size=256]

    Capabilities: <access denied>

00:0b.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306/7/8 [Fire 
II(M)] IEEE 1394 OHCI Controller (rev 80) (prog-if 10 [OHCI])

    Subsystem: Hewlett-Packard Company Device 2a04

    Flags: bus master, medium devsel, latency 32, IRQ 16

    Memory at eb007000 (32-bit, non-prefetchable) [size=2K]

    I/O ports at ec00 [size=128]

    Capabilities: <access denied>

    Kernel driver in use: firewire_ohci

00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration

    Flags: fast devsel

    Capabilities: <access denied>

00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Address Map

    Flags: fast devsel

00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] DRAM Controller

    Flags: fast devsel

00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Miscellaneous Control

    Flags: fast devsel

    Kernel driver in use: k8temp

01:00.0 VGA compatible controller: NVIDIA Corporation NV18 [GeForce4 MX 440SE AGP 8x] (rev a2) (prog-if 00 [VGA controller])

    Subsystem: LeadTek Research Inc. Device 2922

    Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 16

    Memory at e8000000 (32-bit, non-prefetchable) [size=16M]

    Memory at e4000000 (32-bit, prefetchable) [size=64M]

    [virtual] Expansion ROM at e9000000 [disabled] [size=128K]

    Capabilities: <access denied>

    Kernel driver in use: nouveau
```

---

<div class="post-metadata">

**Author:** ![juvisien](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/j/3bc359/32.png) [@juvisien](https://www.debian-fr.org/u/juvisien)\
**Post date:** [Avril 17, 2016, 2:02 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/5 "2016-04-17T02:02:14Z")

</div>

> [@](#):
>
> salut,
> 
> `sudo tail -f kern.log`
> 
> Puis branche la souris, quels sont les messages??
> 
> Exemple:
> 
> ```
> Apr 16 23:58:04 debian kernel: [12741.345235] usb 5-1: new full-speed USB device number 4 using ohci-pci
> Apr 16 23:58:04 debian kernel: [12741.546435] usb 5-1: New USB device found, idVendor=046d, idProduct=c52f
> Apr 16 23:58:04 debian kernel: [12741.546448] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> Apr 16 23:58:04 debian kernel: [12741.546455] usb 5-1: Product: USB Receiver
> Apr 16 23:58:04 debian kernel: [12741.546461] usb 5-1: Manufacturer: Logitech
> Apr 16 23:58:04 debian kernel: [12741.555502] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:13.0/usb5/5-1/5-1:1.0/0003:046D:C52F.0005/input/input20
> Apr 16 23:58:04 debian kernel: [12741.555854] hid-generic 0003:046D:C52F.0005: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:13.0-1/input0
> Apr 16 23:58:04 debian kernel: [12741.562558] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:13.0/usb5/5-1/5-1:1.1/0003:046D:C52F.0006/input/input21
> Apr 16 23:58:04 debian kernel: [12741.618412] hid-generic 0003:046D:C52F.0006: input,hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:13.0-1/input1
> 
> ```

J’obtiens: sudo: commande introuvable

---

<div class="post-metadata">

**Author:** ![seb-ksl](https://www.debian-fr.org/user_avatar/www.debian-fr.org/seb-ksl/32/2946_2.png) [@seb-ksl](https://www.debian-fr.org/u/seb-ksl)\
**Post date:** [Avril 17, 2016, 6:56 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/6 "2016-04-17T06:56:47Z")

</div>

L’idée est de lire la fin du contenu du fichier `/var/log/kern.log` en root. Si tu n’as pas `sudo`, tu peux aussi faire :

```auto
su -
tail -f /var/log/kern.log

```

---

<div class="post-metadata">

**Author:** ![juvisien](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/j/3bc359/32.png) [@juvisien](https://www.debian-fr.org/u/juvisien)\
**Post date:** [Avril 17, 2016, 11:13 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/7 "2016-04-17T11:13:46Z")

</div>

> [@](#):
>
> L’idée est de lire la fin du contenu du fichier `/var/log/kern.log` en root. Si tu n’as pas `sudo`, tu peux aussi faire :
> 
> ```auto
> su -
> tail -f /var/log/kern.log
> 
> ```

Je viens de taper ça dans le terminal et j’ai des messages ERROR qui défilent à toute vitesse et sans cesse… Que se passe-t-il ?

---

<div class="post-metadata">

**Author:** ![grandtoubab](https://www.debian-fr.org/user_avatar/www.debian-fr.org/grandtoubab/32/4505_2.png) [@grandtoubab](https://www.debian-fr.org/u/grandtoubab)\
**Post date:** [Avril 17, 2016, 11:28 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/8 "2016-04-17T11:28:45Z")

</div>

fait ctrl + c pour arreter les messages et poste les ici

---

<div class="post-metadata">

**Author:** ![juvisien](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/j/3bc359/32.png) [@juvisien](https://www.debian-fr.org/u/juvisien)\
**Post date:** [Avril 17, 2016, 11:33 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/9 "2016-04-17T11:33:56Z")

</div>

Merci de ta réponse.

```
tail -f /var/log/kern.log

Apr 17 13:29:56 sam kernel: [1206.294806] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:29:56 sam kernel: [1206.301450] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:29:56 sam kernel: [1206.307271] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:04 sam kernel: [1214.302400] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:07 sam kernel: [1216.929158] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:11 sam kernel: [1221.256599] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:14 sam kernel: [1224.636144] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:16 sam kernel: [1226.480528] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:17 sam kernel: [1226.950005] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:17 sam kernel: [1227.418512] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:18 sam kernel: [1228.615253] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:18 sam kernel: [1228.615325] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:18 sam kernel: [1228.615335] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.656957] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.657103] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.687901] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.688456] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.718479] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.718627] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.748665] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.748810] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.779656] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.779800] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.810674] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.810828] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.841650] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.841796] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.872675] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.872821] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.903626] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.903771] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.934621] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.934765] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.965606] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.965750] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.996615] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1228.996761] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.027625] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.027769] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.058620] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.058766] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.089607] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.089751] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.120636] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.120778] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.151616] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.151767] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.182570] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.182716] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.213583] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.213729] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.244582] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.244737] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.275605] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.275748] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.306627] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.306772] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.337581] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.337726] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.368575] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.368719] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.399591] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.399736] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.430589] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.430740] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.461579] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.461723] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.493487] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.493648] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.523606] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.523734] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.554590] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.554734] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.585577] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.585722] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.616609] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.616752] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.647586] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:19 sam kernel: [1229.647730] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.678582] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.678726] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.709571] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.709715] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.740578] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.740722] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.771593] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.771746] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.802741] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.802884] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.833589] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.833734] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.864572] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.864720] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.895582] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.895735] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.926588] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.926732] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.957573] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.957717] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.988573] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1229.988718] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1230.019584] nouveau E[PBUS][0000:01:00.0] BUS ERROR

Apr 17 13:30:20 sam kernel: [1230.019730] nouveau E[PBUS][0000:01:00.0] BUS ERROR
```

---

<div class="post-metadata">

**Author:** ![avram](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/b38774/32.png) [@avram](https://www.debian-fr.org/u/avram)\
**Post date:** [Avril 17, 2016, 12:13 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/10 "2016-04-17T12:13:21Z")

</div>

le pilote pour votre carte est le 96.43.23 —\> [http://www.nvidia.fr/Download/Find.aspx?lang=fr](http://www.nvidia.fr/Download/Find.aspx?lang=fr)

J’essayerais déjà d’installer ce pilote;votre carte est déjà ancienne et le pilote idoine résoudra peut être le problème,l’installation avec sgfxi est la plus rapide.

---

<div class="post-metadata">

**Author:** ![grandtoubab](https://www.debian-fr.org/user_avatar/www.debian-fr.org/grandtoubab/32/4505_2.png) [@grandtoubab](https://www.debian-fr.org/u/grandtoubab)\
**Post date:** [Avril 17, 2016, 12:23 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/11 "2016-04-17T12:23:34Z")

</div>

le firmware “nouveau” ne convient pas en effet  
[https://wiki.debian.org/NvidiaGraphicsDrivers](https://wiki.debian.org/NvidiaGraphicsDrivers)

---

<div class="post-metadata">

**Author:** ![juvisien](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/j/3bc359/32.png) [@juvisien](https://www.debian-fr.org/u/juvisien)\
**Post date:** [Avril 17, 2016, 3:53 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/12 "2016-04-17T15:53:02Z")

</div>

Je vais tenter l’installation et je vous tiens au courant; merci !

---

<div class="post-metadata">

**Author:** ![juvisien](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/j/3bc359/32.png) [@juvisien](https://www.debian-fr.org/u/juvisien)\
**Post date:** [Avril 17, 2016, 7:24 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/13 "2016-04-17T19:24:09Z")

</div>

Donc j’ai installé SGFXI mais j’obtiens un message d’erreur:

```
ERROR: (226) The driver you selected: 96.43.23 does not support your current Xorg version: 1.16.4 
If this is wrong, please let the script maintainer know.
You can override this test with -! 6 option. If install works, let maintainer know.
```

---

<div class="post-metadata">

**Author:** ![avram](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/b38774/32.png) [@avram](https://www.debian-fr.org/u/avram)\
**Post date:** [Avril 17, 2016, 7:37 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/14 "2016-04-17T19:37:21Z")

</div>

quelles sont les commandes que vous avez utilisées pour installer sgfxi et installer le pilote?  
La commande

sgfxi -h

indique que le 96.43.23 fait bien partie des pilotes installables par sgfxi.

---

<div class="post-metadata">

**Author:** ![juvisien](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/j/3bc359/32.png) [@juvisien](https://www.debian-fr.org/u/juvisien)\
**Post date:** [Avril 17, 2016, 7:39 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/15 "2016-04-17T19:39:29Z")

</div>

J’ai fait

`cd /usr/local/bin && wget -Nc smxi.org/smxi.zip && unzip smxi.zip`

Ensuite je suis passé sur le terminal et j’ai tapé sgfxi

---

<div class="post-metadata">

**Author:** ![avram](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/b38774/32.png) [@avram](https://www.debian-fr.org/u/avram)\
**Post date:** [Avril 17, 2016, 7:44 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/16 "2016-04-17T19:44:30Z")

</div>

installation de sgfxi:

#cd /usr/local/bin && wget -O sgfxi [smxi.org/sgfxi](http://smxi.org/sgfxi) && chmod +x sgfxi

ensuite faire:

Ctrl+Alt+F1

ouvrir votre session et ensuite passer root et faire la commande:

#sgfxi -o 96.43.23

si le pilote nouveau est installé vous aurez un message en fin de procédure vous demandant de redémarrer la machine et de relancer la procédure d’installation de sgfxi pour finaliser l’installation de 96.43.23

---

<div class="post-metadata">

**Author:** ![juvisien](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/j/3bc359/32.png) [@juvisien](https://www.debian-fr.org/u/juvisien)\
**Post date:** [Avril 17, 2016, 9:06 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/17 "2016-04-17T21:06:25Z")

</div>

J’obtiens le même message d’erreur que précédemment. Un problème avec xorg.conf ?

---

<div class="post-metadata">

**Author:** ![avram](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/b38774/32.png) [@avram](https://www.debian-fr.org/u/avram)\
**Post date:** [Avril 17, 2016, 9:19 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/18 "2016-04-17T21:19:23Z")

</div>

avez vous un xorg.conf?Si oui donnez en le contenu.  
installez aussi le paquet nvidia-xconfig et lancezla commande root

nvidia-xconfig

je ne souviens plus si cette commande doit être lancée en tty1.

---

<div class="post-metadata">

**Author:** ![grandtoubab](https://www.debian-fr.org/user_avatar/www.debian-fr.org/grandtoubab/32/4505_2.png) [@grandtoubab](https://www.debian-fr.org/u/grandtoubab)\
**Post date:** [Avril 17, 2016, 9:39 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/19 "2016-04-17T21:39:58Z")

</div>

A propos de ce script

> [@Installer SMXI & SGFXI](https://www.debian-fr.org/t/installer-smxi-sgfxi/30250/13):
>
> On réveille les morts sur ce topic mais je voudrai juste dire ceci : cd /usr/local/bin && wget -O sgfxi [smxi.org/sgfxi](http://smxi.org/sgfxi) && chmod +x sgfxi && sgfxi Cela ne fontionne plus en l'état sur une fresh install stable. Et si on ne prend pas la peine de lire et regarder la sortie dans son /var/log pour voir d'ou vient le problème cela engendre énormément de problèmes. ( A voir certains messages, je suis persuadé que certains on tapé la commande comme des robots et se retrouvent à poster dans le suppo…

---

<div class="post-metadata">

**Author:** ![avram](https://www.debian-fr.org/letter_avatar_proxy/v4/letter/a/b38774/32.png) [@avram](https://www.debian-fr.org/u/avram)\
**Post date:** [Avril 17, 2016, 9:44 UTC](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210/20 "2016-04-17T21:44:38Z")

</div>

il me semblait bien que le script s’occupait d’installer les headers et autres utilités,mais même si il ne le fait pas/plus il devrait le dire si il manque des trucs pour compiler le module.

[Page suivante](https://www.debian-fr.org/t/curseur-introuvable-sous-debian-8-4-0-xfce/69210.md?page=2)