** le kernel 5.8 est dispo ** (page 20)

Le fameux bug:
http://marc.theaimsgroup.com/?l=linux-kernel&m=106423857728133&w=2
“Amazingly idiotic typo” : c’est lui qui le dit… :slight_smile:
@+

Pour revenir à mon petit pb USB… en fait c ptet plus grave que ça.
Voici le dmesg :

[fixed]

e:1 Active:1)
00:00:08[C] -> 2-18 -> IRQ 18
IOAPIC[0]: Set PCI routing entry (2-19 -> 0xc1 -> IRQ 19 Mode:1 Active:1)
00:00:08[D] -> 2-19 -> IRQ 19
Pin 2-17 already programmed
Pin 2-19 already programmed
Pin 2-18 already programmed
Pin 2-16 already programmed
Pin 2-17 already programmed
Pin 2-16 already programmed
Pin 2-19 already programmed
Pin 2-18 already programmed
Pin 2-19 already programmed
Pin 2-16 already programmed
Pin 2-17 already programmed
Pin 2-18 already programmed
Pin 2-18 already programmed
Pin 2-19 already programmed
Pin 2-16 already programmed
Pin 2-17 already programmed
Pin 2-19 already programmed
Pin 2-17 already programmed
Pin 2-18 already programmed
Pin 2-16 already programmed
Pin 2-18 already programmed
Pin 2-19 already programmed
Pin 2-16 already programmed
Pin 2-17 already programmed
pci_link-0263 [22] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKB] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_link-0263 [23] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKB] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_link-0263 [24] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKB] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_link-0263 [25] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKB] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_link-0263 [26] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKA] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_link-0263 [27] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKB] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_link-0263 [28] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKC] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_link-0263 [29] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKD] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
Pin 2-16 already programmed
Pin 2-17 already programmed
Pin 2-18 already programmed
Pin 2-19 already programmed
pci_link-0263 [30] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKD] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_link-0263 [31] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKD] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_link-0263 [32] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKD] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_link-0263 [33] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKD] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_link-0263 [36] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKB] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_irq-0259 [32] acpi_pci_irq_lookup : Invalid IRQ link routing entry
pci_irq-0299 [32] acpi_pci_irq_derive : Unable to derive IRQ for device 0000:00:10.0
ACPI: No IRQ known for interrupt pin A of device 0000:00:10.0
pci_link-0263 [37] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKB] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_irq-0259 [33] acpi_pci_irq_lookup : Invalid IRQ link routing entry
pci_irq-0299 [33] acpi_pci_irq_derive : Unable to derive IRQ for device 0000:00:10.1
ACPI: No IRQ known for interrupt pin B of device 0000:00:10.1
pci_link-0263 [38] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKB] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_irq-0259 [34] acpi_pci_irq_lookup : Invalid IRQ link routing entry
pci_irq-0299 [34] acpi_pci_irq_derive : Unable to derive IRQ for device 0000:00:10.2
ACPI: No IRQ known for interrupt pin C of device 0000:00:10.2
pci_link-0263 [39] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKB] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_irq-0259 [35] acpi_pci_irq_lookup : Invalid IRQ link routing entry
pci_irq-0299 [35] acpi_pci_irq_derive : Unable to derive IRQ for device 0000:00:10.3
ACPI: No IRQ known for interrupt pin D of device 0000:00:10.3
pci_link-0263 [40] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKA] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_irq-0259 [36] acpi_pci_irq_lookup : Invalid IRQ link routing entry
pci_irq-0299 [36] acpi_pci_irq_derive : Unable to derive IRQ for device 0000:00:11.1
ACPI: No IRQ known for interrupt pin A of device 0000:00:11.1 - using IRQ 255
pci_link-0263 [41] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKC] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_irq-0259 [37] acpi_pci_irq_lookup : Invalid IRQ link routing entry
pci_irq-0299 [37] acpi_pci_irq_derive : Unable to derive IRQ for device 0000:00:11.5
ACPI: No IRQ known for interrupt pin C of device 0000:00:11.5
pci_link-0263 [42] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKD] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_irq-0259 [38] acpi_pci_irq_lookup : Invalid IRQ link routing entry
pci_irq-0299 [38] acpi_pci_irq_derive : Unable to derive IRQ for device 0000:00:12.0
ACPI: No IRQ known for interrupt pin A of device 0000:00:12.0
PCI: Using ACPI for IRQ routing
PCI: if you experience problems, try using option ‘pci=noacpi’ or even ‘acpi=off’
pty: 256 Unix98 ptys configured
Machine check exception polling timer started.
ikconfig 0.6 with /proc/ikconfig
NTFS driver 2.1.4 [Flags: R/O].
Initializing Cryptographic API
Real Time Clock Driver v1.12
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:11.1
pci_link-0263 [42] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKA] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_irq-0259 [38] acpi_pci_irq_lookup : Invalid IRQ link routing entry
pci_irq-0299 [38] acpi_pci_irq_derive : Unable to derive IRQ for device 0000:00:11.1
ACPI: No IRQ known for interrupt pin A of device 0000:00:11.1 - using IRQ 255
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci0000:00:11.1
ide0: BM-DMA at 0xdc00-0xdc07, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xdc08-0xdc0f, BIOS settings: hdc:DMA, hdd:DMA
hda: WDC WD600BB-00CAA0, ATA DISK drive
hdb: HITACHI DVD-ROM GD-2500, ATAPI CD/DVD-ROM drive
Using anticipatory scheduling io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: IBM-DTLA-307030, ATA DISK drive
hdd: LITE-ON LTR-48246K, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
hda: hda1 hda2 hda3 hda4
hdc: max request size: 128KiB
hdc: 60036480 sectors (30738 MB) w/1916KiB Cache, CHS=59560/16/63, UDMA(100)
hdc: hdc1 < hdc5 hdc6 hdc7 hdc8 hdc9 > hdc2 hdc3
mice: PS/2 mouse device common for all mice
serio: i8042 AUX port at 0x60,0x64 irq 12
input: AT Set 2 keyboard on isa0060/serio0
serio: i8042 KBD port at 0x60,0x64 irq 1
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
ip_tables: © 2000-2002 Netfilter core team
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 8
NET: Registered protocol family 20
ACPI: (supports S0 S1 S4 S5)
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 152k freed
Adding 248968k swap on /dev/hdc7. Priority:-1 extents:1
EXT3 FS on hdc9, internal journal
via-rhine.c:v1.10-LK1.1.19-2.5 July-12-2003 Written by Donald Becker
http://www.scyld.com/network/via-rhine.html
pci_link-0263 [43] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKD] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_irq-0259 [39] acpi_pci_irq_lookup : Invalid IRQ link routing entry
pci_irq-0299 [39] acpi_pci_irq_derive : Unable to derive IRQ for device 0000:00:12.0
ACPI: No IRQ known for interrupt pin A of device 0000:00:12.0
eth0: VIA VT6102 Rhine-II at 0xe400, 00:50:8d:45:91:c5, IRQ 11.
eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 0081.
SCSI subsystem initialized
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: HITACHI Model: DVD-ROM GD-2500 Rev: 0101
Type: CD-ROM ANSI SCSI revision: 02
scsi1 : SCSI host adapter emulation for IDE ATAPI devices
Vendor: LITE-ON Model: LTR-48246K Rev: SKS7
Type: CD-ROM ANSI SCSI revision: 02
Linux video capture interface: v1.00
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
drivers/usb/core/usb.c: registered new driver ov511
drivers/usb/media/ov511.c: v1.64 for Linux 2.5 : ov511 USB Camera Driver
drivers/usb/core/usb.c: registered new driver usbscanner
drivers/usb/image/scanner.c: 0.4.14:USB Scanner Driver
Initializing USB Mass Storage driver…
drivers/usb/core/usb.c: registered new driver usb-storage
USB Mass Storage support registered.
ip_conntrack version 2.1 (4095 buckets, 32760 max) - 300 bytes per conntrack
kjournald starting. Commit interval 5 seconds
EXT3 FS on hdc5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hdc8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hdc6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
NTFS-fs warning (device hda4): parse_options(): Option iocharset is deprecated. Please use option nls= in the future.
NTFS volume version 3.1.
NTFS-fs warning (device hdc3): parse_options(): Option iocharset is deprecated. Please use option nls= in the future.
NTFS volume version 3.1.
NTFS-fs warning (device hda3): parse_options(): Option iocharset is deprecated. Please use option nls= in the future.
NTFS volume version 3.1.
NTFS-fs warning (device hda1): parse_options(): Option iocharset is deprecated. Please use option nls= in the future.
NTFS volume version 3.1.
pci_link-0263 [44] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKB] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_irq-0259 [40] acpi_pci_irq_lookup : Invalid IRQ link routing entry
pci_irq-0299 [40] acpi_pci_irq_derive : Unable to derive IRQ for device 0000:00:10.3
ACPI: No IRQ known for interrupt pin D of device 0000:00:10.3
ehci_hcd 0000:00:10.3: EHCI Host Controller
ehci_hcd 0000:00:10.3: irq 5, pci mem e088e000
ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:10.3: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-13
hub 1-0:0: USB hub found
hub 1-0:0: 6 ports detected
drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver v2.1
pci_link-0263 [45] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKB] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_irq-0259 [41] acpi_pci_irq_lookup : Invalid IRQ link routing entry
pci_irq-0299 [41] acpi_pci_irq_derive : Unable to derive IRQ for device 0000:00:10.0
ACPI: No IRQ known for interrupt pin A of device 0000:00:10.0
uhci-hcd 0000:00:10.0: UHCI Host Controller
uhci-hcd 0000:00:10.0: irq 11, io base 0000d000
uhci-hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
hub 2-0:0: USB hub found
hub 2-0:0: 2 ports detected
pci_link-0263 [46] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKB] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_irq-0259 [42] acpi_pci_irq_lookup : Invalid IRQ link routing entry
pci_irq-0299 [42] acpi_pci_irq_derive : Unable to derive IRQ for device 0000:00:10.1
ACPI: No IRQ known for interrupt pin B of device 0000:00:10.1
uhci-hcd 0000:00:10.1: UHCI Host Controller
uhci-hcd 0000:00:10.1: irq 10, io base 0000d400
uhci-hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
hub 3-0:0: USB hub found
hub 3-0:0: 2 ports detected
pci_link-0263 [47] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKB] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_irq-0259 [43] acpi_pci_irq_lookup : Invalid IRQ link routing entry
pci_irq-0299 [43] acpi_pci_irq_derive : Unable to derive IRQ for device 0000:00:10.2
ACPI: No IRQ known for interrupt pin C of device 0000:00:10.2
uhci-hcd 0000:00:10.2: UHCI Host Controller
uhci-hcd 0000:00:10.2: irq 12, io base 0000d800
uhci-hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
hub 4-0:0: USB hub found
hub 4-0:0: 2 ports detected
hub 1-0:0: debounce: port 2: delay 100ms stable 4 status 0x501
hub 2-0:0: debounce: port 2: delay 100ms stable 4 status 0x301
hub 2-0:0: new USB device on port 2, assigned address 2
pci_link-0263 [48] acpi_pci_link_get_curr: No IRQ resource found
ACPI: Unable to set IRQ for PCI Interrupt Link [ALKC] (likely buggy ACPI BIOS). Aborting ACPI-based IRQ routing. Try pci=noacpi or acpi=off
pci_irq-0259 [44] acpi_pci_irq_lookup : Invalid IRQ link routing entry
pci_irq-0299 [44] acpi_pci_irq_derive : Unable to derive IRQ for device 0000:00:11.5
ACPI: No IRQ known for interrupt pin C of device 0000:00:11.5
PCI: Setting latency timer of device 0000:00:11.5 to 64
pnp: the driver ‘parport_pc’ has been registered
parport0: PC-style at 0x378 (0x778) [PCSPP(,…)]
parport0: irq 7 detected
lp0: using parport0 (polling).
usb 2-2: control timeout on ep0out
uhci-hcd 0000:00:10.0: Unlink after no-IRQ? Different ACPI or APIC settings may help.
[drm] Initialized radeon 1.9.0 20020828 on minor 0
[drm:radeon_cp_init] ERROR radeon_cp_init called without lock held
[drm:radeon_unlock] ERROR Process 572 using kernel context 0
[/fixed]

c’est assez moche :cry:

Souvent ca aide de lire ce qui est ecrit :slight_smile:

ajoute l’option pci=noacpi a ta ligne de commande pour lancer linux, et tout devrait mieux se passer pour toi…

En ce qui me concerne, pas de chance avec le 2.6.0-test{4,5}{,mm*}… J’ai jamais reussi a en booter un sur une Asus P4P800 Deluxe. Quelqu’un aurait-il reussi ?? J’ai beau enlever le SMP, l’ACPI, l’APIC , le preemptif ou encore toute la gestion d’energie, rien a faire… Si quelqu’un a un .config qui marche, je l’accepte bien volontiers ;o)

En fait j’ai recompilé en enlevant le support ACPI et c’est tout bon :wink:
Etrange qd même…

ce bug est connu : attends un mm5 ou un test6 pour qu’il soit corrigé.
@+

OK autant pour moi :slight_smile:

Bon je vais tenter de compiler le driver radeon pour ma 9200.
on verra si c mieux qu’avec le 2.4 (pb agpgart KT400)

C’est encore une version de test et certaines fois, il faut patienter un peu. TU peux aussi essayer de corriger le bug toi même mais c’est plus dur :wink:

Je reviens un peu sur ma radeon 9200.

Alros après avoir chargé les modules via_agp, agpgart et radeon, qd je lance xfree j’ai le message suivant ds les logs :

fixed RADEON(0): [drm] created “radeon” driver at busid “PCI:1:0:0”
(II) RADEON(0): [drm] added 8192 byte SAREA at 0xe0996000
(II) RADEON(0): [drm] mapped SAREA 0xe0996000 to 0x482ad000
(II) RADEON(0): [drm] framebuffer handle = 0xd0000000
(II) RADEON(0): [drm] added 1 reserved context for kernel
(II) RADEON(0): [agp] Mode 0x1f000a09 [AGP 0x1106/0x3189; Card 0x1002/0x5961]
(II) RADEON(0): [agp] 8192 kB allocated with handle 0x00000001
(II) RADEON(0): [agp] ring handle = 0xe0000000
(II) RADEON(0): [agp] Ring mapped at 0x482af000
(II) RADEON(0): [agp] ring read ptr handle = 0xe0101000
(II) RADEON(0): [agp] Ring read ptr mapped at 0x483b0000
(II) RADEON(0): [agp] vertex/indirect buffers handle = 0xe0102000
(II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0x483b1000
(II) RADEON(0): [agp] AGP texture map handle = 0xe0302000
(II) RADEON(0): [agp] AGP Texture map mapped at 0x485b1000
(II) RADEON(0): [drm] register handle = 0xe5000000
(II) RADEON(0): [dri] Visual configs initialized
(II) RADEON(0): CP in BM mode
(II) RADEON(0): Using 8 MB AGP aperture
(II) RADEON(0): Using 1 MB for the ring buffer
(II) RADEON(0): Using 2 MB for vertex/indirect buffers
(II) RADEON(0): Using 5 MB for AGP textures
(II) RADEON(0): Memory manager initialized to (0,0) (1024,8191)
(II) RADEON(0): Reserved area from (0,768) to (1024,770)
(II) RADEON(0): Largest offscreen area available: 1024 x 7421
(II) RADEON(0): Will use back buffer at offset 0xc00000
(II) RADEON(0): Will use depth buffer at offset 0xf00000
(II) RADEON(0): Will use 112640 kb for textures at offset 0x1200000
(II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Lines
Scanline Image Writes
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
32 256x256 slots
16 512x512 slots
(II) RADEON(0): Acceleration enabled
(==) RADEON(0): Backing store disabled
(==) RADEON(0): Silken mouse enabled
(II) RADEON(0): Using software cursor
(II) RADEON(0): X context handle = 0x00000001
(II) RADEON(0): [drm] installed DRM signal handler
(II) RADEON(0): [DRI] installation complete
(II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers
(II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers
(II) RADEON(0): [drm] dma control initialized, using IRQ 16
(II) RADEON(0): [drm] Initialized kernel agp heap manager, 5111808
(II) RADEON(0): Direct rendering enabled[/fixed]

En voyant ça je me suis dit OK c bon cette fois ci…

Et en fait glxinfo m’indique que le dri ne fonctionne pas.
Et c vrai (j’ai essayé tux).

Donc c toujours pas ça :frowning:

heu…dsl ma je n’y connais rien en ati (j’ai une geforce.)
C’est un driver externe au noyau? Le dri, c’est le dri du noyau ou d’un driver externe? Avec un 2.4, ça marche comment? (ça ne marche pas car le driver n’existe pas c’est ça?)
Qlqn s’y connait en Ati ici?

http://marc.theaimsgroup.com/?l=linux-kernel&m=106471273819562&w=2
Et une version de test de plus! le 2.6.0 approche :wink:

Alors en fait c assez compliqué…
C’est pas la carte graphique qui posait pb en 2.4, c t le chipset KT400 qui n’était aps bien supporté au niveau de l’agp (agpgart plus précisement).
J’ai donc tenté un 2.6 qui lui ne pose apparement pas de pb même xfree m’indique que le dri fonctionne, or glxinfo me dit le contraire.

Le module utilisé est celui du kernel, radeon.ko
Je vais essayer celui d’ati (fglrx.ko si j’arrive à le compiler ;))

ok merci de l’info.
Qlqn d’autre a testé fglrx.ko?
@+

s’il est compatible avec le radeon 7500 mobility je veux bien le tester

Les noms des devices souris ont changé il me semble.
J’ai une souris ps2 et une usb. C’est /dev/psaux et /dev/mouse c’est bien ça? (pour le moment, l’usb ne marche pas : timeout dû à l’apic ou à l’acpi. Je vais essayer sans apic.)

Quelle sont les bonnes options pour que le framebuffer marche avec une geforce? Est ce qu’il faut prendre le framebuffer nvidia/riva (il est incompatible avec les drivers nvidia non?)

Sinon pour le reste, c’est tout bon! et c’est très réactif :wink:

irq 9: nobody cared!
Call Trace:
[] __report_bad_irq+0x2a/0x90
[] note_interrupt+0x70/0xa0
[] do_IRQ+0x120/0x130
[] common_interrupt+0x18/0x20
[] do_softirq+0x40/0xa0
[] do_IRQ+0xfc/0x130
[] common_interrupt+0x18/0x20
[] pci_bus_write_config_word+0x61/0x90
[] uhci_reset+0x3f/0x60
[] usb_hcd_pci_probe+0x195/0x4a0
[] pci_device_probe_static+0x52/0x70
[] __pci_device_probe+0x3b/0x50
[] pci_device_probe+0x2c/0x50
[] bus_match+0x3f/0x70
[] driver_attach+0x59/0x90
[] bus_add_driver+0x8d/0xa0
[] driver_register+0x2f/0x40
[] pci_register_driver+0x5f/0x90
[] uhci_hcd_init+0xc4/0x140
[] do_initcalls+0x2b/0xa0
[] init_workqueues+0xf/0x50
[] init+0x2d/0x160
[] init+0x0/0x160
[] kernel_thread_helper+0x5/0xc

handlers:
[] (acpi_irq+0x0/0x16)
[] (yenta_interrupt+0x0/0x40)
Disabling IRQ #9

toujours le même bug depuis qlqs versions…

L’ACPI me fait foirer l’USB sur le test5… je vais voir avec le test6 si c mieux…

Bonjour à tous!
Pour ceux ayant des difficultés avec l’usb et l’acpi avec le 2.6-test6-*, essayez ce petit patch:
http://marc.theaimsgroup.com/?l=linux-kernel&m=106485647522096&w=2

ok merci. Il y avait un autre patch qui proposait de masquer les interruptions pendant 50ms mais ça ne résolvait pas le pb.
Le temps de compiler un noyo et on va voir si ça marche.
@+

L’usb fonctionne à nouveau avec l’acpi :slight_smile: Merci!
Autre pb (moins grave) : que deviennent les scripts alsa de debian avec un 2.6 : au boot ça semble marche mais quand on arrète le système, on se fait insulter à cause de la syntaxe de rmmod…
Comment utiliser correctement alsa avec un 2.6 sous debian?
Merci.

héhé, Salut les gens :wink:
Je vais bientot avoir mon PC donc je vais pouvoir tester la derniere version, apres avoir installer ma mdk 9.1 :wink: