[quote=“MattOTop”]Dis moi, tu connais dmesg, pour regarder ce qui se passe au boot ?
[/quote]
ha benh vi tout de suite c’est plus sympa …
enfin voila ce qui me sort , c’est différent du tiens ! Bon, je sais, j’ai un disque qui merdoit, mais c’est pas ça qui provoque cette différence je pense…
[code]Linux version 2.6.12-1-k7 (horms@tabatha.lab.ultramonkey.org) (gcc version 4.0.2 20050917 (prerelease) (Debian 4.0.1-8)) #1 Tue Sep 27 13:22:07 JST 2005
ALI15X3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xb400-0xb407, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xb408-0xb40f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0…
hda: Maxtor 6L160P0, ATA DISK drive
hdb: QUANTUM FIREBALLP LM10.2, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1…
hdc: no response (status = 0xa1), resetting drive
hdc: no response (status = 0xa1)
hdd: no response (status = 0xa1), resetting drive
hdd: no response (status = 0xa1)
Probing IDE interface ide1…
ide1: Wait for ready failed before probe !
hdc: no response (status = 0xa1), resetting drive
hdc: no response (status = 0xa1)
hdd: no response (status = 0xa1), resetting drive
hdd: no response (status = 0xa1)
Probing IDE interface ide2…
Probing IDE interface ide3…
Probing IDE interface ide4…
Probing IDE interface ide5…
hda: max request size: 128KiB
hda: cannot use LBA48 DMA - PIO mode will be used for accessing sectors > 268435456
hda: 320173056 sectors (163928 MB) w/8192KiB Cache, CHS=19929/255/63, UDMA(100)
hda: cache flushes supported
/dev/ide/host0/bus0/target0/lun0: p1
hdb: max request size: 128KiB
hdb: 20066251 sectors (10273 MB) w/1900KiB Cache, CHS=19906/16/63, UDMA(66)
hdb: cache flushes not supported
/dev/ide/host0/bus0/target1/lun0:<4>hdb: dma_timer_expiry: dma status == 0x61
hdb: DMA timeout error
hdb: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
p1 p2
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
EXT3 FS on hda1, internal journal
[/code]
du coup moi je dirai qu’il faut peut etre regarder du coté de ide-probe-mod et ide-mod ?
A+
DeMZed
Participant persistant et envahissant