Forum Linux.mandriva Problemes de toutes sortes ...

Posté par  .
Étiquettes :
0
12
oct.
2004
Bonjour, Je viens de mettre à jour de mandrake 9.2 vers mandrake 10.1 communauty. Mais les problemes sont nombreux: Freeze, souris USB qui fonctionne mais sans possibilités de choisir une config dans mousedrake, module mousedev introuvable , IRQ, demarrage très long après la phase de login mdklogin, mise en veille de l'écran inopiné ... Voici le dmesg en son entier (si vous avez des pistes, super) Pour info portable Athlon 1800xp chipset via son VT8233A, Carte graphique geforce4 440 64Mo, Dlink 650+ avec ACX100 sur Cardbus) : bit even in supervisor mode... Ok.
Calibrating delay loop... 3301.37 BogoMIPS
Security Scaffold v1.0.0 initialized
SELinux: Disabled at boot.
Capability LSM initialized
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0383fbff c1cbfbff 00000000 00000000
CPU: After vendor identify, caps: 0383fbff c1cbfbff 00000000 00000000
CPU: CLK_CTL MSR was 60079263. Reprogramming to 20079263
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 00000020
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: AMD Athlon(tm) XP 2000+ stepping 01
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
init init/main.c:689
init init/main.c:702
init init/main.c:707
do_pre_smp_initcalls init/main.c:653
do_pre_smp_initcalls init/main.c:659
init init/main.c:711
init init/main.c:714
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 1666.0139 MHz.
..... host bus clock speed is 266.0582 MHz.
init init/main.c:716
init init/main.c:718
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
ACPI: Looking for DSDT in initrd ... not found!
Freeing initrd memory: 145k freed
init init/main.c:724
do_basic_setup init/main.c:634
do_basic_setup init/main.c:636
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfd94c, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040326
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
PnPBIOS: Disabled
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router VIA [1106/3177] at 0000:00:11.0
PCI: IRQ 0 for device 0000:00:0d.0 doesn't match PIRQ mask - try pci=usepirqmask
PCI: IRQ 0 for device 0000:00:10.0 doesn't match PIRQ mask - try pci=usepirqmask
PCI: IRQ 0 for device 0000:00:11.1 doesn't match PIRQ mask - try pci=usepirqmask
PCI: Found IRQ 11 for device 0000:00:11.1
PCI: Sharing IRQ 11 with 0000:00:10.2
PCI: Cannot allocate resource region 0 of device 0000:00:12.0
PCI: Cannot allocate resource region 0 of device 0000:00:0d.0
vesafb: framebuffer at 0xf0000000, mapped to 0xd0800000, size 1875k
vesafb: mode is 800x600x16, linelength=1600, pages=2
vesafb: protected mode interface info at c000:f890
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
fb0: VESA VGA frame buffer device
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
audit: initializing netlink socket (disabled)
audit(1097592162.133:0): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
Initializing Cryptographic API
PCI: Via IRQ fixup for 0000:00:11.6, from 255 to 0
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
bootsplash 3.1.6-2004/03/31: looking for picture... no good signature found.
spurious 8259A interrupt: IRQ7.
Console: switching to colour frame buffer device 100x37
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 32000K size 1024 blocksize
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: Found IRQ 11 for device 0000:00:11.1
PCI: Sharing IRQ 11 with 0000:00:10.2
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci0000:00:11.1
ide0: BM-DMA at 0x1800-0x1807, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x1808-0x180f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: HITACHI_DK23DA-30, ATA DISK drive
hda: IRQ probe failed (0xfffffffa)
hdb: IRQ probe failed (0xfffffffa)
hdb: IRQ probe failed (0xfffffffa)
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: QSI CD-RW/DVD-ROM SBW-241, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 58605120 sectors (30005 MB) w/2048KiB Cache, CHS=58140/16/63, UDMA(100)
/dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 p9 p10 >
mice: PS/2 mouse device common for all mice
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
input: PS/2 Generic Mouse on isa0060/serio4
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
NET: Registered protocol family 1
BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
init init/main.c:726
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Mounted devfs on /dev
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Mounted devfs on /dev
Freeing unused kernel memory: 200k freed
Real Time Clock Driver v1.12
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v2.2
PCI: IRQ 0 for device 0000:00:10.0 doesn't match PIRQ mask - try pci=usepirqmask
PCI: Assigned IRQ 10 for device 0000:00:10.0
PCI: Sharing IRQ 10 with 0000:00:0c.0
PCI: Sharing IRQ 10 with 0000:00:0d.0
uhci_hcd 0000:00:10.0: UHCI Host Controller
uhci_hcd 0000:00:10.0: irq 10, io base 0000fe00
uhci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
PCI: Found IRQ 10 for device 0000:00:10.1
uhci_hcd 0000:00:10.1: UHCI Host Controller
uhci_hcd 0000:00:10.1: irq 10, io base 00001820
uhci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
PCI: Found IRQ 11 for device 0000:00:10.2
PCI: Sharing IRQ 11 with 0000:00:11.1
uhci_hcd 0000:00:10.2: UHCI Host Controller
uhci_hcd 0000:00:10.2: irq 11, io base 00001840
uhci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
PCI: Found IRQ 11 for device 0000:00:10.3
ehci_hcd 0000:00:10.3: EHCI Host Controller
ehci_hcd 0000:00:10.3: irq 11, pci mem d09e7000
ehci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 4
ehci_hcd 0000:00:10.3: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 6 ports detected
usb 3-1: new low speed USB device using address 2
usbcore: registered new driver hiddev
input: USB HID v1.10 Mouse [Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)] on usb-0000:00:10.2-1
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
usbcore: registered new driver usbmouse
drivers/usb/input/usbmouse.c: v1.6:USB HID Boot Protocol mouse driver
usb 2-1: new full speed USB device using address 2
ts: Compaq touchscreen protocol output
SCSI subsystem initialized
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
Vendor: Generic Model: Traveling Disk Rev: 1.11
Type: Direct-Access ANSI SCSI revision: 02
USB Mass Storage device found at 2
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
SCSI device sda: 129024 512-byte hdwr sectors (66 MB)
sda: Write Protect is off
sda: Mode Sense: 03 00 00 00
sda: assuming drive cache: write through
/dev/scsi/host0/bus0/target0/lun0: p1
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
EXT3 FS on hda10, internal journal
Adding 329260k swap on /dev/hda6. Priority:-1 extents:1
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected VIA KT266/KY266x/KT333 chipset
agpgart: Maximum main memory to use for agp memory: 202M
agpgart: AGP aperture is 64M @ 0xe4000000
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Supermount version 2.0.4 for kernel 2.6
NTFS driver 2.1.15 [Flags: R/O DEBUG MODULE].
NTFS-fs warning (device hda1): parse_options(): Option iocharset is deprecated. Please use option nls= in the future.
NTFS volume version 3.1.
NTFS-fs warning (device hda5): parse_options(): Option iocharset is deprecated. Please use option nls= in the future.
NTFS volume version 3.1.
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 hda9, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
loop: loaded (max 8 devices)
ieee1394: Initialized config rom entry `ip1394'
ohci1394: $Rev: 1223 $ Ben Collins <bcollins@debian.org>
PCI: Enabling device 0000:00:0d.0 (0000 -> 0002)
PCI: Found IRQ 10 for device 0000:00:0d.0
PCI: Sharing IRQ 10 with 0000:00:0c.0
PCI: Sharing IRQ 10 with 0000:00:10.0
ohci1394: fw-host0: Unexpected PCI resource length of 1000!
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[10] MMIO=[10001000-100017ff] Max Packet=[2048]
hdc: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
ieee1394: Host added: ID:BUS[0-00:1023] GUID[0040ca0115200e91]
ip1394: $Rev: 1224 $ Ben Collins <bcollins@debian.org>
ip1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (2039 buckets, 16312 max) - 328 bytes per conntrack
Linux Kernel Card Services
options: [pci] [cardbus] [pm]
PCI: Found IRQ 10 for device 0000:00:0c.0
PCI: Sharing IRQ 10 with 0000:00:0d.0
PCI: Sharing IRQ 10 with 0000:00:10.0
Yenta: CardBus bridge found at 0000:00:0c.0 [1509:2750]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:0c.0, mfunc 0x01021c02, devctl 0x44
Yenta: ISA IRQ mask 0x00a0, PCI irq 10
Socket status: 30000020
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
acx100: It looks like you've been coaxed into buying a wireless network card
acx100: that uses the mysterious ACX100/ACX111 chip from Texas Instruments.
acx100: You should better have bought e.g. a PRISM(R) chipset based card,
acx100: since that would mean REAL vendor Linux support.
acx100: Given this info, it's evident that this driver is quite EXPERIMENTAL,
acx100: thus your mileage may vary. Visit http://acx100.sf.net(...) for support.
acx100: Compiled to use 32bit I/O access (I/O timing issues might occur, such as firmware upload failure!)
acx_init_module: dev_info is: TI acx_pci
acx_init_module: TI acx_pci.o: Ver 0.2.0pre8 Driver initialized, waiting for cards to probe...
PCI: Enabling device 0000:02:00.0 (0000 -> 0003)
PCI: Setting latency timer of device 0000:02:00.0 to 64
Found ACX100-based wireless network card at 0000:02:00.0, irq:10, phymem1:0x10810000, phymem2:0x10800000, mem1:0xd0c23000, mem1_size:4096, mem2:0xd0c5e000, mem2_size:65536
initial debug setting is 0x001b
acx_select_io_register_set: using ACX100 io resource addresses (size: 56)
hw_unavailable = 1
acx_probe_pci: TI acx_pci: Using IRQ 10
reset hw_unavailable++
acx_reset_mac: enable soft reset...
acx_reset_mac: disable soft reset and go to init mode...
Attention: no custom firmware directory specified (via module parameter firmware_dir), thus using our default firmware directory /usr/share/acx
Trying to load firmware: '/usr/share/acx/WLANGEN.BIN'
Allocated 40636 bytes for firmware module loading.
not using auto increment for firmware loading.
acx_write_fw: Firmware written.
acx_write_fw (firmware): 0, acx_validate_fw: 0
acx_reset_dev: boot up eCPU and wait for complete...
acx_reset_dev: Received signal that card is ready to be configured :) (the eCPU has woken up)
reset hw_unavailable--
acx100: allocated net device wlan0, driver compiled against wireless extensions v16 and Linux 2.6.8.1-10mdk
******************************************
************* acx_init_mac_1 *************
******************************************
==> Get the mailbox pointers from the scratch pad registers
CmdMailboxOffset = fdc8
InfoMailboxOffset = ff4c
<== Get the mailbox pointers from the scratch pad registers
CommandParameters = [ 0xd0c6ddcc ]
InfoParameters = [ 0xd0c6df50 ]
Allocated 936 bytes for firmware module loading.
not using auto increment for firmware loading.
acx_write_fw: Firmware written.
acx_write_fw (radio): 0, acx_validate_fw: 0
CodeEnd:A250
acx_init_wep: writing WEP options.
get_mask 0x00004182, set_mask 0x00000000
Got sensitivity value 176
Got antenna value 0x8D
Got regulatory domain 0x30
get_mask 0x00000000, set_mask 0x00000000 - after update
new ratevector: 82 84 8b 96 ac
SSID = STA15B2FF, len = 9
Beacon length:61
SSID = STA15B2FF, len = 9
hw_unavailable--
acx100: form factor 0x01 ((mini-)PCI / CardBus), radio type 0x0d (Maxim), EEPROM version 0x0005. Uploaded firmware 'Rev 1.9.8.b' (0x01020505).
creating /proc entry driver/acx_wlan0
creating /proc entry driver/acx_wlan0_diag
creating /proc entry driver/acx_wlan0_eeprom
creating /proc entry driver/acx_wlan0_phy
acx_probe_pci: TI acx_pci.o: Ver 0.2.0pre8 Loaded Successfully
inserting floppy driver for 2.6.8.1-10mdk
floppy0: no floppy controllers found
inserting floppy driver for 2.6.8.1-10mdk
floppy0: no floppy controllers found
NET: Registered protocol family 17
Via 686a/8233/8235 audio driver 1.9.1-ac4-2.5
PCI: No IRQ known for interrupt pin C of device 0000:00:11.5. Please try using pci=biosirq.
via82cxxx: Six channel audio available
via82cxxx: invalid PCI IRQ 0, aborting
NET: Registered protocol family 10
Disabled Privacy Extensions on device c0323b60(lo)
IPv6 over IPv4 tunneling driver
mtrr: 0xf0000000,0x4000000 overlaps existing 0xf0000000,0x100000
parport0: PC-style at 0x378 [PCSPP,TRISTATE,EPP]
lp0: using parport0 (polling).
lp0: console ready
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
inserting floppy driver for 2.6.8.1-10mdk
floppy0: no floppy controllers found
inserting floppy driver for 2.6.8.1-10mdk
floppy0: no floppy controllers found
inserting floppy driver for 2.6.8.1-10mdk
floppy0: no floppy controllers found
NET: Registered protocol family 23
IrCOMM protocol (Dag Brattli)
inserting floppy driver for 2.6.8.1-10mdk
floppy0: no floppy controllers found
inserting floppy driver for 2.6.8.1-10mdk
floppy0: no floppy controllers found
inserting floppy driver for 2.6.8.1-10mdk
floppy0: no floppy controllers found
inserting floppy driver for 2.6.8.1-10mdk
floppy0: no floppy controllers found
usb 2-1: USB disconnect, address 2
  • # mise à jour ou installation ?

    Posté par  (site web personnel) . Évalué à 3.

    Il est préférable de faire une "installation" plutot qu'une mise à jour quandon passe de la 9.2 à la 10. Le changment de noyau nottament et l'upgrade de certains paquets importants font qu'ils vaut mieux refaire un systeme tout neuf. (et ca te prendra moins de temps qu'une mise à jour)
    • [^] # Re: mise à jour ou installation ?

      Posté par  . Évalué à -3.

      Super le système de paquet sauce Mandrake, vive la Debian
      • [^] # Re: mise à jour ou installation ?

        Posté par  . Évalué à 1.

        Eh eh ! pi t'etre qu'un jour j'y viendrais... Mais "vive Debian" pour les utilisateurs moyen (j'ai meme pas dis débutant), cela peut faire encore plus de temps à bidouiller le zinzouin pour avoir un pingouin qui flotte. Mais tu as raison, ce systeme de gestion n'est pas toujours d'une praticité extreme. En tout cas, je veux bien un coup de main pour une Debian install ;-)
    • [^] # Re: mise à jour ou installation ?

      Posté par  . Évalué à 1.

      J'y pensais justement ... car un nouveau probleme. Je bosse sur le Web. Et j'aai besoin d'un d'Apache / MySQL / PHP. Et la il est maintenant impossible de démarrer httpd (mod_perl manque à l'appel). Donc je prends mes CD d'installation et je m'aperçois que 2 montages /mnt/cdrom et /mnt/cdrom2 sont apparus. (j'en ai qu'un ...) Donc drakerpm cherche dans /mnt/cdrom et le montage est effectif dans /mnt/cdrom2 .
      Franchement cette derniere mouture de Mandrake est pour moi vraiment géniale, comme d'hab., mais tu as raison, la mise à jour est vraiment merdique. Pourtant c'est ce que j'ai fait sur mon desktop (9.0 Comm. -> 9.1 Comm. -> 9.2 Comm. -> 10.0 Official) Et tout c'était très bien passé (ou presque ;-)) . Mais là, la somme du temps passé à resoudre les problemes est de loin supèrieur à celle passée à réinstaller.
      Il n'empêche que j'ai toujours eu sur ce portable des problèmes de souris et de freeze (apparemment du à la carte graphique ou à la gestion de l'ACPI), ce qui m'avait obligé de downgradder de 10.0 Download vers la 9.2 Download puis j'avais réessayer avec la 10.0 Official que j'avais acheté mais j'avais re-downgradder vers la 9.2 Download (freeze et gel intempestifs - du pour moi à la mauvaise gestion de la gforce4 spéciale portable par le drivers nvidia fourni par Mandrake mais bon).
      Allez je réinstalle...

      Merci à toi.

Suivre le flux des commentaires

Note : les commentaires appartiennent à celles et ceux qui les ont postés. Nous n’en sommes pas responsables.