A voir également:
- Recupération debian après reboot sauvage
- Reboot pc - Guide
- Reboot system now - Guide
- Convertisseur récupération de texte - Guide
- Recuperation video youtube - Guide
- Comment récupérer son compte facebook apres piratage - Guide
8 réponses
jipicy
Messages postés
40842
Date d'inscription
jeudi 28 août 2003
Statut
Modérateur
Dernière intervention
10 août 2020
4 897
28 mars 2008 à 09:48
28 mars 2008 à 09:48
Salut,
T'as regardé dans les journaux de logs ? (dmesg, /var/log/messages, /var/log/boot.log, etc.)
T'as regardé dans les journaux de logs ? (dmesg, /var/log/messages, /var/log/boot.log, etc.)
Bonjour,
Je pense avoir identifié le problème, mais pas comment le résoudre.
/etc/init.d/rc exited outside the expected code flow
J'ai fait quelques recherches sur le net, mais vu de solution pour régler le problème.
Quels sont les paquets qui correspondent au services rc ?
Ce n'est pas en tout cas rc puisqu'il n'est pas installé.
J'ai tenté une réinstallation à tout hasard de sysv-rc mais sans résultat..
Pour la description des services j'ai installé bum, mais la liste de tous les services n'y est pas, par contre sur le site contrib, y'a une liste plus fournie https://wiki.ubuntu.com/InitScriptHumanDescriptions
Même si c'est en anglais, c'est toujours mieux que rien.
Je pense avoir identifié le problème, mais pas comment le résoudre.
/etc/init.d/rc exited outside the expected code flow
J'ai fait quelques recherches sur le net, mais vu de solution pour régler le problème.
Quels sont les paquets qui correspondent au services rc ?
Ce n'est pas en tout cas rc puisqu'il n'est pas installé.
J'ai tenté une réinstallation à tout hasard de sysv-rc mais sans résultat..
Pour la description des services j'ai installé bum, mais la liste de tous les services n'y est pas, par contre sur le site contrib, y'a une liste plus fournie https://wiki.ubuntu.com/InitScriptHumanDescriptions
Même si c'est en anglais, c'est toujours mieux que rien.
Bon ben j'ai quand même pris le risque d'effectuer cette commande sur mes partitions ext3 non montées, mais maleureusement rien de bien spécial à part sur le hda8.
Je sais pas quoi faire d'autres.
# fsck -v -a /dev/hda8 fsck 1.40-WIP (14-Nov-2006) /dev/hda8 : recupération du journal /dev/hda8: Lors de l'effacement de l'i-noeud orphelin 16 (uid=108, gid=113, mode=0100600, taille=0) /dev/hda8: Lors de l'effacement de l'i-noeud orphelin 15 (uid=108, gid=113, mode=0100600, taille=0) /dev/hda8: Lors de l'effacement de l'i-noeud orphelin 14 (uid=108, gid=113, mode=0100600, taille=0) /dev/hda8: Lors de l'effacement de l'i-noeud orphelin 13 (uid=108, gid=113, mode=0100600, taille=226) /dev/hda8: Lors de l'effacement de l'i-noeud orphelin 12 (uid=108, gid=113, mode=0100600, taille=0) /dev/hda8: clean, 16/122624 files, 8264/244983 blocks
Je sais pas quoi faire d'autres.
Bonjour,
Il s'avère que le problème survient quand je lance l'interface graphique avec gdm.
J'ai fait une réinstallation de celui-ci, mais sans sucès, comment je pourrais détecter ce qui fait planter debian ?
J'ai tenté de désactivé le maximum de services avec sysv-rc-conf mais toujours pareil.
Merci de votre aide.
Il s'avère que le problème survient quand je lance l'interface graphique avec gdm.
J'ai fait une réinstallation de celui-ci, mais sans sucès, comment je pourrais détecter ce qui fait planter debian ?
J'ai tenté de désactivé le maximum de services avec sysv-rc-conf mais toujours pareil.
Merci de votre aide.
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
Je suis désolé de faire un monologue stupide, mais comme ça m'énervait j'ai désactivé tous les services, je pensais pas que debian pourrait démarrer en faisant ça, et beh si, je l'ai enfin récupérer :)
En lançant gdm pas de problème.
Juste une erreur que debian m'a signalé Failed to initialize HAL, j'ai donc relancé dbus.
Maintenant il me reste plus qu'à trouver quel service fait le plantage, et à trouver ceux qui sont nécessaires.
Merci.
En lançant gdm pas de problème.
Juste une erreur que debian m'a signalé Failed to initialize HAL, j'ai donc relancé dbus.
Maintenant il me reste plus qu'à trouver quel service fait le plantage, et à trouver ceux qui sont nécessaires.
Merci.
J'avoue que non, j'ai pas trop eu ce réflexe, je viens de regarder et c'est incompréhensible pour moi.
le log boot ne contient qu'une seule ligne :
(Nothing has been logged yet.)
le dmesg contient pas mal de ligne :
Je ne saurais détecté une erreur dans tout ceci.
Le log message contient énormément de lignes, les dernières sont
Pas facile de trouver la cause du plantage dans tout ça.
le log boot ne contient qu'une seule ligne :
(Nothing has been logged yet.)
le dmesg contient pas mal de ligne :
Linux version 2.6.18-4-486 (Debian 2.6.18.dfsg.1-12etch2) (dannf@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 Wed May 9 22:23:40 UTC 2007
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000003fffb000 (usable)
BIOS-e820: 000000003fffb000 - 000000003ffff000 (ACPI data)
BIOS-e820: 000000003ffff000 - 0000000040000000 (ACPI NVS)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
Warning only 896MB will be used.
Use a HIGHMEM enabled kernel.
896MB LOWMEM available.
On node 0 totalpages: 229376
DMA zone: 4096 pages, LIFO batch:0
Normal zone: 225280 pages, LIFO batch:31
DMI 2.3 present.
ACPI: RSDP (v000 ASUS ) @ 0x000f5e20
ACPI: RSDT (v001 ASUS A7V600-X 0x42302e31 MSFT 0x31313031) @ 0x3fffb000
ACPI: FADT (v001 ASUS A7V600-X 0x42302e31 MSFT 0x31313031) @ 0x3fffb0b2
ACPI: BOOT (v001 ASUS A7V600-X 0x42302e31 MSFT 0x31313031) @ 0x3fffb030
ACPI: MADT (v001 ASUS A7V600-X 0x42302e31 MSFT 0x31313031) @ 0x3fffb058
ACPI: DSDT (v001 ASUS A7V600-X 0x00001000 MSFT 0x0100000b) @ 0x00000000
ACPI: PM-Timer IO Port: 0xe408
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 6:10 APIC version 16
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 3, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode: Flat. Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 50000000 (gap: 40000000:bec00000)
Detected 1999.872 MHz processor.
Built 1 zonelists. Total pages: 229376
Kernel command line: root=/dev/hda5 ro single
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 902096k/917504k available (1502k kernel code, 14852k reserved, 601k data, 256k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 4003.06 BogoMIPS (lpj=8006122)
Security Framework v1.0.0 initialized
SELinux: Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383fbff c1cbfbff 00000000 00000000 00000000 00000000 00000000
CPU: After vendor identify, caps: 0383fbff c1cbfbff 00000000 00000000 00000000 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After all inits, caps: 0383fbff c1cbfbff 00000000 00000420 00000000 00000000 00000000
Compat vDSO mapped to ffffe000.
CPU: AMD Sempron(TM) 2800+ stepping 00
Checking 'hlt' instruction... OK.
ACPI: Core revision 20060707
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
checking if image is initramfs... it is
Freeing initrd memory: 4271k freed
NET: Registered protocol family 16
EISA bus registered
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xf1970, last bus=1
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 11 12) *0, disabled.
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 *10 11 12)
ACPI: PCI Interrupt Link [LNKF] (IRQs *3 4 5 6 7 9 10 11 12)
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 7 9 10 11 12)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 11 12) *15, disabled.
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
PCI: enabled onboard AC97/MC97 devices
Boot video device is 0000:01:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 14 devices
PnPBIOS: Disabled by ACPI PNP
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
pnp: 00:02: ioport range 0xe400-0xe47f could not be reserved
pnp: 00:02: ioport range 0xe800-0xe81f has been reserved
pnp: 00:0d: ioport range 0x290-0x297 has been reserved
pnp: 00:0d: ioport range 0x370-0x375 has been reserved
PCI: Bridge: 0000:00:01.0
IO window: disabled.
MEM window: ee000000-efefffff
PREFETCH window: eff00000-f7ffffff
PCI: Setting latency timer of device 0000:00:01.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
Simple Boot Flag at 0x3a set to 0x1
audit: initializing netlink socket (disabled)
audit(1206696151.784:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
PCI: Bypassing VIA 8237 APIC De-Assert Message
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
PNP: PS/2 controller doesn't have AUX irq; using default 12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
EISA: Probing bus 0 at eisa.0
EISA: Detected 0 cards.
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 8
NET: Registered protocol family 20
Using IPI Shortcut mode
ACPI: (supports S0 S1 S4 S5)
Freeing unused kernel memory: 256k freed
Time: tsc clocksource has been installed.
input: AT Translated Set 2 keyboard as /class/input/input0
SCSI subsystem initialized
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:0f.1
ACPI: PCI Interrupt 0000:00:0f.1[A] -> GSI 20 (level, low) -> IRQ 169
PCI: VIA IRQ fixup for 0000:00:0f.1, from 14 to 9
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci0000:00:0f.1
ide0: BM-DMA at 0xa800-0xa807, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xa808-0xa80f, BIOS settings: hdc:pio, hdd:DMA
Probing IDE interface ide0...
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v3.0
libata version 2.00 loaded.
via-rhine.c:v1.10-LK1.4.1 July-24-2006 Written by Donald Becker
hda: Maxtor 6Y120L0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdd: _NEC DVD_RW ND-3520A, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
ACPI: PCI Interrupt 0000:00:10.0[A] -> GSI 21 (level, low) -> IRQ 177
PCI: VIA IRQ fixup for 0000:00:10.0, from 0 to 1
uhci_hcd 0000:00:10.0: UHCI Host Controller
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:10.0: irq 177, io base 0x0000a400
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
hda: max request size: 128KiB
hda: 240121728 sectors (122942 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(133)
hda: cache flushes supported
hda: hda1 hda2 hda3 < hda5 hda6 hda7 hda8 hda9<6>ACPI: PCI Interrupt 0000:00:10.1[A] -> GSI 21 (level, low) -> IRQ 177
PCI: VIA IRQ fixup for 0000:00:10.1, from 0 to 1
uhci_hcd 0000:00:10.1: UHCI Host Controller
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:10.1: irq 177, io base 0x0000a000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
hda10 hda11 > hda4
hdd: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
ACPI: PCI Interrupt 0000:00:10.2[B] -> GSI 21 (level, low) -> IRQ 177
PCI: VIA IRQ fixup for 0000:00:10.2, from 0 to 1
uhci_hcd 0000:00:10.2: UHCI Host Controller
uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:10.2: irq 177, io base 0x00009800
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:10.3[B] -> GSI 21 (level, low) -> IRQ 177
PCI: VIA IRQ fixup for 0000:00:10.3, from 0 to 1
uhci_hcd 0000:00:10.3: UHCI Host Controller
uhci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:10.3: irq 177, io base 0x00009400
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
sata_via 0000:00:0f.0: version 2.0
ACPI: PCI Interrupt 0000:00:0f.0[B] -> GSI 20 (level, low) -> IRQ 169
sata_via 0000:00:0f.0: routed to hard irq line 0
ata1: SATA max UDMA/133 cmd 0xD800 ctl 0xD402 bmdma 0xB400 irq 169
ata2: SATA max UDMA/133 cmd 0xD000 ctl 0xB802 bmdma 0xB408 irq 169
scsi0 : sata_via
usb 2-1: new low speed USB device using uhci_hcd and address 2
ata1: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
ATA: abnormal status 0x7F on port 0xD807
scsi1 : sata_via
usb 2-1: configuration #1 chosen from 1 choice
ata2: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
ATA: abnormal status 0x7F on port 0xD007
usbcore: registered new driver hiddev
ACPI: PCI Interrupt 0000:00:12.0[A] -> GSI 23 (level, low) -> IRQ 185
eth0: VIA Rhine II at 0x19000, 00:11:2f:3c:e7:f1, IRQ 185.
eth0: MII PHY found at address 1, status 0x786d advertising 01e1 Link 45e1.
ACPI: PCI Interrupt 0000:00:10.4[C] -> GSI 21 (level, low) -> IRQ 177
PCI: VIA IRQ fixup for 0000:00:10.4, from 0 to 1
ehci_hcd 0000:00:10.4: EHCI Host Controller
ehci_hcd 0000:00:10.4: new USB bus registered, assigned bus number 5
ehci_hcd 0000:00:10.4: irq 177, io mem 0xed800000
ehci_hcd 0000:00:10.4: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 8 ports detected
usb 2-1: USB disconnect, address 2
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
Attempting manual resume
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
usb 2-1: new low speed USB device using uhci_hcd and address 3
usb 2-1: configuration #1 chosen from 1 choice
input: Logitech USB-PS/2 Optical Mouse as /class/input/input1
input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:10.1-1
ts: Compaq touchscreen protocol output
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected VIA KT400/KT400A/KT600 chipset
agpgart: AGP aperture is 64M @ 0xf8000000
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
input: PC Speaker as /class/input/input2
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
Real Time Clock Driver v1.12ac
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
PCI: Enabling device 0000:00:11.6 (0000 -> 0001)
ACPI: PCI Interrupt 0000:00:11.6[C] -> GSI 22 (level, low) -> IRQ 193
PCI: Setting latency timer of device 0000:00:11.6 to 64
ACPI: PCI interrupt for device 0000:00:11.6 disabled
VIA 82xx Modem: probe of 0000:00:11.6 failed with error -13
ACPI: PCI Interrupt 0000:00:11.5[C] -> GSI 22 (level, low) -> IRQ 193
PCI: Setting latency timer of device 0000:00:11.5 to 64
codec_read: codec 0 is not valid [0xfe0000]
codec_read: codec 0 is not valid [0xfe0000]
codec_read: codec 0 is not valid [0xfe0000]
codec_read: codec 0 is not valid [0xfe0000]
Adding 1951856k swap on /dev/hda10. Priority:-1 extents:1 across:1951856k
EXT3 FS on hda5, internal journal
loop: loaded (max 8 devices)
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda9, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
NTFS driver 2.1.27 [Flags: R/W MODULE].
NTFS volume version 3.1.
NTFS-fs warning (device hda1): load_system_files(): Unsupported volume flags 0x4000 encountered.
NTFS-fs warning (device hda1): load_system_files(): Volume has unsupported flags set. Will not be able to remount read-write. Run chkdsk and mount in Windows.
NTFS volume version 3.1.
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
eth0: no IPv6 routers present
nvidia: module license 'NVIDIA' taints kernel.
ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 201
NVRM: loading NVIDIA Linux x86 Kernel Module 1.0-8776 Mon Oct 16 21:56:04 PDT 2006
agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
eth0: no IPv6 routers present
Je ne saurais détecté une erreur dans tout ceci.
Le log message contient énormément de lignes, les dernières sont
Mar 27 17:25:38 localhost kernel: ACPI: Power Button (FF) [PWRF] Mar 27 17:25:38 localhost kernel: ACPI: Power Button (CM) [PWRB] Mar 27 17:25:43 localhost dhcdbd: Started up. Mar 27 17:25:44 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason Mar 27 17:25:44 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason Mar 27 17:25:44 localhost kernel: NET: Registered protocol family 5 Mar 27 17:25:44 localhost papd[3332]: restart (2.0.3) Mar 27 17:25:44 localhost papd[3332]: CUPS support enabled (1.1) Mar 27 17:25:46 localhost kernel: vboxdrv: Successfully loaded version 1.5.4 (interface 0x00050002). Mar 27 17:25:49 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name Mar 27 17:25:49 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.domain_name Mar 27 17:25:49 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain Mar 27 17:25:49 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers Mar 27 17:25:50 localhost kernel: nvidia: module license 'NVIDIA' taints kernel. Mar 27 17:25:50 localhost kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 201 Mar 27 17:25:50 localhost kernel: NVRM: loading NVIDIA Linux x86 Kernel Module 1.0-8776 Mon Oct 16 21:56:04 PDT 2006 Mar 27 17:25:50 localhost kernel: agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0. Mar 27 17:25:50 localhost kernel: agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode Mar 27 17:25:50 localhost kernel: agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode Mar 27 17:25:54 localhost kernel: agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0. Mar 27 17:25:54 localhost kernel: agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode Mar 27 17:25:54 localhost kernel: agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode Mar 27 17:25:54 localhost kernel: agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
Pas facile de trouver la cause du plantage dans tout ça.
jipicy
Messages postés
40842
Date d'inscription
jeudi 28 août 2003
Statut
Modérateur
Dernière intervention
10 août 2020
4 897
28 mars 2008 à 10:25
28 mars 2008 à 10:25
Le seul truc que je vois, c'est apparemment un problème avec ta partition Windows (NTFS) !
Il semblerait qu'elle soit montée en lecture/écriture alors que le support adéquat (ntfs-3g) n'est pas installé, mais bon je ne pense pas que c'était la cause de tes soucis...
Il semblerait qu'elle soit montée en lecture/écriture alors que le support adéquat (ntfs-3g) n'est pas installé, mais bon je ne pense pas que c'était la cause de tes soucis...
NTFS driver 2.1.27 [Flags: R/W MODULE]. NTFS volume version 3.1. NTFS-fs warning (device hda1): load_system_files(): Unsupported volume flags 0x4000 encountered. NTFS-fs warning (device hda1): load_system_files(): Volume has unsupported flags set. Will not be able to remount read-write. Run chkdsk and mount in Windows. NTFS volume version 3.1.
