dvd and eth0 doesnt work on fresh install mdk 10.1
 

Ok. I''ve just installed mdh 10.1 community. But i don't know what's going on with my dvd reader and my eth0 device.

First, the DVD.
I've installed the OS from 3 cds using my dvd reader. Setup runned smoothly and with no problems. I restarted and logged into KDE. Then i see that /mnt/cdrom was shown with the hard disk drive icon. I double clicked it and an error message poped up sayin that device /dev/hdc doesnt exist. Checked /dev and, as reported, the device isn't there. I had NO problems gettin my CD Writer recognized.

Something similar happened when i first installed MDK 10.0 Official. But, i tried booting with an alternative kernel that install putted into the LILO list and like 'magic' the dvd started to work. I see no alternative kernel in this version, so i don't know what to do and my entire backup is in a dvd.

I have a LG DVD reader and CD Writer.

Next, the eth0 thing
Here i have NO Idea what can be happenning. This is the first time i have 2 network interfaces since i want to share internet connection: eth1 is a VIA Rhine II interface, no problem with it, eth0 is a DAVICOM (CNET) card, i've tried to configure using drakconf and manually editing the eth* scripts. Nothing works. When network starts at boot time it just appears [FAILED]

Thanx in advance.
triaydev
:D

Type

dmesg | more

and look to see how the kernel recognizes and configures your DVD drive.

Try dmfe for the Davicom chipset

edit /ect/modprobe.conf

change "alias eth0 tulip" to "alias eth0 dmfe"

reboot

Ok.. eth0 is up... but dvd ...
 

Ok.
Thanx SinSpinr, eth0 is up and running.

opjose, the result of dmesg | grep 'CD' is

hdd: HL-DT-ST GCE-8160B, ATAPI CD/DVD-ROM drive
hdd: ATAPI 32X CD-ROM CD-R/RW drive, 2048kB Cache, DMA
Uniform CD-ROM driver Revision: 3.20

Check out that both devices, the dvd and the cd-rw, are mapped as hdd, and i think this could be the problem. How can i create or force the system to create an hdc device and map it to my dvd? I've just checked the jumper settings of both drives and they're ok, the cdrw is slave and the dvd is master, they're on the same channel IDE1. I have 2 hard drives at IDE0, no problem with them.

Anyway, here's my entire dmesg output. Thanx again
triaydev :D

MHz processor.
Using pmtmr for high-res timesource
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 254180k/262080k available (1964k kernel code, 7164k reserved, 868k data, 216k init, 0k highmem, 0k BadRAM)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 4538.36 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: bfebfbff 00000000 00000000 00000000
CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 128K
CPU: Hyper-Threading is disabled
CPU: After all inits, caps: bfebfbff 00000000 00000000 00000080
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU0: Intel P4/Xeon Extended MCE MSRs (12) available
CPU0: Thermal monitoring enabled
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
CPU0: Intel(R) Celeron(R) CPU 2.30GHz stepping 09
per-CPU timeslice cutoff: 365.86 usecs.
task migration cache decay timeout: 1 msecs.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Total of 1 processors activated (4538.36 BogoMIPS).
ENABLING IO-APIC IRQs
Setting 2 in the phys_id_present_map
...changing IO-APIC physical APIC ID to 2 ... ok.
init IO_APIC IRQs
IO-APIC (apicid-pin) 2-0, 2-5, 2-10, 2-11, 2-17, 2-18, 2-19 not connected.
..TIMER: vector=0x31 pin1=2 pin2=0
number of MP IRQ sources: 23.
number of IO-APIC #2 registers: 24.
testing the IO APIC.......................
IO APIC #2......
.... register #00: 02000000
....... : physical APIC id: 02
....... : Delivery Type: 0
....... : LTS : 0
.... register #01: 00178003
....... : max redirection entries: 0017
....... : PRQ implemented: 1
....... : IO APIC version: 0003
.... IRQ redirection table:
NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
00 000 00 1 0 0 0 0 0 0 00
01 001 01 0 0 0 0 0 1 1 39
02 001 01 0 0 0 0 0 1 1 31
03 001 01 0 0 0 0 0 1 1 41
04 001 01 0 0 0 0 0 1 1 49
05 000 00 1 0 0 0 0 0 0 00
06 001 01 0 0 0 0 0 1 1 51
07 001 01 0 0 0 0 0 1 1 59
08 001 01 0 0 0 0 0 1 1 61
09 001 01 0 0 0 0 0 1 1 69
0a 000 00 1 0 0 0 0 0 0 00
0b 000 00 1 0 0 0 0 0 0 00
0c 001 01 0 0 0 0 0 1 1 71
0d 001 01 0 0 0 0 0 1 1 79
0e 001 01 0 0 0 0 0 1 1 81
0f 001 01 0 0 0 0 0 1 1 89
10 001 01 1 1 0 1 0 1 1 91
11 000 00 1 0 0 0 0 0 0 00
12 000 00 1 0 0 0 0 0 0 00
13 000 00 1 0 0 0 0 0 0 00
14 001 01 1 1 0 1 0 1 1 99
15 001 01 1 1 0 1 0 1 1 A1
16 001 01 1 1 0 1 0 1 1 A9
17 001 01 1 1 0 1 0 1 1 B1
IRQ to pin mappings:
IRQ0 -> 0:2
IRQ1 -> 0:1
IRQ3 -> 0:3
IRQ4 -> 0:4
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ9 -> 0:9
IRQ12 -> 0:12
IRQ13 -> 0:13
IRQ14 -> 0:14
IRQ15 -> 0:15
IRQ16 -> 0:16
IRQ20 -> 0:20
IRQ21 -> 0:21
IRQ22 -> 0:22
IRQ23 -> 0:23
.................................... done.
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 2299.0477 MHz.
..... host bus clock speed is 99.0977 MHz.
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
Brought up 1 CPUs
init init/main.c:716
CPU0: online
domain 0: span 00000001
groups: 00000001
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: 213k 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 0xfb130, 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/3227] at 0000:00:11.0
PCI->APIC IRQ transform: (B0,I8,P0) -> 16
PCI->APIC IRQ transform: (B0,I15,P1) -> 20
PCI->APIC IRQ transform: (B0,I15,P0) -> 20
PCI->APIC IRQ transform: (B0,I16,P0) -> 21
PCI->APIC IRQ transform: (B0,I16,P0) -> 21
PCI->APIC IRQ transform: (B0,I16,P1) -> 21
PCI->APIC IRQ transform: (B0,I16,P1) -> 21
PCI->APIC IRQ transform: (B0,I16,P2) -> 21
PCI->APIC IRQ transform: (B0,I17,P2) -> 22
PCI->APIC IRQ transform: (B0,I18,P0) -> 23
PCI->APIC IRQ transform: (B1,I0,P0) -> 16
vesafb: framebuffer at 0xe0000000, mapped to 0xd0800000, size 1875k
vesafb: mode is 800x600x16, linelength=1600, pages=33
vesafb: protected mode interface info at c000:5470
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 0x07 (Driver version 1.16ac)
audit: initializing netlink socket (disabled)
audit(1100453116.727: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: 0x0
Initializing Cryptographic API
PCI: Via IRQ fixup for 0000:00:10.0, from 10 to 5
PCI: Via IRQ fixup for 0000:00:10.1, from 10 to 5
PCI: Via IRQ fixup for 0000:00:10.2, from 11 to 5
PCI: Via IRQ fixup for 0000:00:10.3, from 11 to 5
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
bootsplash 3.1.6-2004/03/31: looking for picture.... silentjpeg size 14344 bytes, found (800x600, 14296 bytes, v3).
Console: switching to colour frame buffer device 92x32
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) 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:0f.1
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 0xcc00-0xcc07, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xcc08-0xcc0f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: Maxtor 90432D2, ATA DISK drive
hdb: ST340016A, ATA DISK drive
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
ide1: Wait for ready failed before probe !
hdd: HL-DT-ST GCE-8160B, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 8440992 sectors (4321 MB) w/256KiB Cache, CHS=8374/16/63, UDMA(33)
/dev/ide/host0/bus0/target0/lun0: p1
hdb: max request size: 128KiB
hdb: 78165360 sectors (40020 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
/dev/ide/host0/bus0/target1/lun0: p1 p2 < p5 p6 p7 >
mice: PS/2 mouse device common for all mice
serio: i8042 AUX port at 0x60,0x64 irq 12
input: ImExPS/2 Generic Explorer Mouse on isa0060/serio1
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 16384)
NET: Registered protocol family 1
BIOS EDD facility v0.16 2004-Jun-25, 2 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).
ReiserFS: hdb1: found reiserfs format "3.6" with standard journal
ReiserFS: hdb1: using ordered data mode
ReiserFS: hdb1: journal params: device hdb1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
ReiserFS: hdb1: checking transaction log (hdb1)
ReiserFS: hdb1: Using r5 hash to sort names
Freeing unused kernel memory: 216k freed
Generic RTC Driver v1.07
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v2.2
uhci_hcd 0000:00:10.0: UHCI Host Controller
uhci_hcd 0000:00:10.0: irq 21, io base 0000d000
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
uhci_hcd 0000:00:10.1: UHCI Host Controller
uhci_hcd 0000:00:10.1: irq 21, io base 0000d400
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
uhci_hcd 0000:00:10.2: UHCI Host Controller
uhci_hcd 0000:00:10.2: irq 21, io base 0000d800
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
uhci_hcd 0000:00:10.3: UHCI Host Controller
uhci_hcd 0000:00:10.3: irq 21, io base 0000dc00
uhci_hcd 0000:00:10.3: new USB bus registered, assigned bus number 4
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ehci_hcd 0000:00:10.4: EHCI Host Controller
ehci_hcd 0000:00:10.4: irq 21, pci mem d0a05000
ehci_hcd 0000:00:10.4: new USB bus registered, assigned bus number 5
ehci_hcd 0000:00:10.4: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 8 ports detected
usb 3-2: new full speed USB device using address 2
Adding 811240k swap on /dev/hdb5. Priority:-1 extents:1
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected VIA PM800/PN800/PM880/PN880 chipset
agpgart: Maximum main memory to use for agp memory: 203M
agpgart: AGP aperture is 64M @ 0xe8000000
kjournald starting. Commit interval 5 seconds
EXT3 FS on hdb7, 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 volume version 3.0.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hdb6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
loop: loaded (max 8 devices)
hdd: ATAPI 32X CD-ROM CD-R/RW drive, 2048kB Cache, DMA
Uniform CD-ROM driver Revision: 3.20
SCSI subsystem initialized
libata version 1.02 loaded.
sata_via version 0.20
sata_via(0000:00:0f.0): routed to hard irq line 4
ata1: SATA max UDMA/133 cmd 0xB400 ctl 0xB802 bmdma 0xC400 irq 20
ata2: SATA max UDMA/133 cmd 0xBC00 ctl 0xC002 bmdma 0xC408 irq 20
ata1: no device found (phy stat 00000000)
scsi0 : sata_via
ata2: no device found (phy stat 00000000)
scsi1 : sata_via
dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
eth0: Davicom DM9102 at pci0000:00:08.0, 00:80:ad:04:ce:b7, irq 16.
via-rhine.c:v1.10-LK1.2.0-2.6 June-10-2004 Written by Donald Becker
eth1: VIA Rhine II at 0xe400, 00:30:18:04:c2:cf, IRQ 23.
eth1: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1.
inserting floppy driver for 2.6.8.1-10mdksmp
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
NET: Registered protocol family 17
eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: Tx timeout - resetting
via82xx: Assuming DXS channels with 48k fixed sample rate.
Please try dxs_support=1 or dxs_support=4 option
and report if it works on your machine.
PCI: Setting latency timer of device 0000:00:11.5 to 64
NET: Registered protocol family 10
Disabled Privacy Extensions on device c0342740(lo)
IPv6 over IPv4 tunneling driver
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
eth0: Tx timeout - resetting
mtrr: 0xe0000000,0x2000000 overlaps existing 0xe0000000,0x100000
[drm] Initialized radeon 1.11.0 20020828 on minor 0:
mtrr: 0xe0000000,0x2000000 overlaps existing 0xe0000000,0x100000
agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
agpgart: Device is in legacy mode, falling back to 2.x
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode
200.79.248.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 200.79.248.255 on eth1
200.79.248.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 200.79.248.255 on eth1
eth0: Tx timeout - resetting
eth0: no IPv6 routers present
eth1: no IPv6 routers present
eth0: Tx timeout - resetting
bootsplash 3.1.6-2004/03/31: looking for picture.... found (800x600, 10049 bytes, v3).
bootsplash: status on console 0 changed to on
bootsplash 3.1.6-2004/03/31: looking for picture.... found (800x600, 10049 bytes, v3).
bootsplash: status on console 1 changed to on
bootsplash 3.1.6-2004/03/31: looking for picture.... found (800x600, 10049 bytes, v3).
bootsplash: status on console 2 changed to on
bootsplash 3.1.6-2004/03/31: looking for picture.... found (800x600, 10049 bytes, v3).
bootsplash: status on console 3 changed to on
bootsplash 3.1.6-2004/03/31: looking for picture.... found (800x600, 10049 bytes, v3).
bootsplash: status on console 4 changed to on
bootsplash 3.1.6-2004/03/31: looking for picture.... found (800x600, 10049 bytes, v3).
bootsplash: status on console 5 changed to on
eth0: Tx timeout - resetting
cdrom: hdd: mmc-3 profile capable, current profile: Ah
cdrom: hdd: mmc-3 profile capable, current profile: Ah
ISO 9660 Extensions: RRIP_1991A
200.79.248.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 200.79.248.255 on eth1
eth0: Tx timeout - resetting
200.79.248.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 200.79.248.255 on eth1
eth0: Tx timeout - resetting
200.79.248.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 200.79.248.255 on eth1
eth0: Tx timeout - resetting
eth0: Tx timeout - resetting
200.79.248.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 200.79.248.255 on eth1
eth0: Tx timeout - resetting
eth0: Tx timeout - resetting
200.79.248.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 200.79.248.255 on eth1
eth0: Tx timeout - resetting
eth0: Tx timeout - resetting
200.79.248.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 200.79.248.255 on eth1
eth0: Tx timeout - resetting
200.79.248.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 200.79.248.255 on eth1
eth0: Tx timeout - resetting
200.79.248.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 200.79.248.255 on eth1
eth0: Tx timeout - resetting
200.79.248.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 200.79.248.255 on eth1
eth0: Tx timeout - resetting
200.79.248.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 200.79.248.255 on eth1
eth0: Tx timeout - resetting
200.79.248.1 sent an invalid ICMP type 3, code 3 error to a broadcast: 200.79.248.255 on eth1
eth0: Tx timeout - resetting

This is probably why:

Probing IDE interface ide1...
ide1: Wait for ready failed before probe !

The drives are not going ready as far as the kernel is concerned.

This could be due to a noise issue on the cable (change cables and route them away from the CPU and motherboard as much as possible, shield them with metal if possible... e.g. the casing, etc... DO NOT use "round" cables...).

This could also be due to booting the system with a disk in the drive(s), data rates being set to high by the bios, etc.

Start by setting the drives to PIO 3 mode and see if there is any change.

same thing
 

Changed to PIO3
nothing
Changed Cable
did not work... :S
under Windows it all runs fine. and as i said, i booted and installed from the dvd reader, the one with problems
anything else would be appreciated.

triaydev
:S

While Windows is often used as a comparison, remember that the results from Windows don't necessarily apply.

As Linux sees it, your devices are not coming "ready" when the IDE interface is probed and reset.

USUALLY this indicates a problem with the devices themselves or with communication to/from the device.

I say USUALLY because an unusual kernel problem may also be to blame, but this is less likely...

It may be possible to pass a kernel parameter to Linux prior to start to help deal with this and assign the correct mappings.

Quick question here.
Is their a problem with noise and rounded cables ?
I put some on my system to help with the airflow. I haven't heard anything negative about them yet.

I was just wondering..........

Never hurts to keep your ears open and ask questions <grin>

Thanks Charlie

Rounded cables put the wire pairs next to each other in a way that the ribbon cables do not.

This causes signal induction, where in an adjacent wire picks up a signal from another, called cross-talk.

Most rounded cables have had their individual strands cut apart negating some of the RF shielding features of the return ground on the 80 pin versions.

The rounded cables then tend to pick up far more interference from the CPU and other components as well.

If you really want to use round cables they should not be hacked apart ribbon cables or loose stranded, but rather specifically designed for this purpose... e.g. w/twists in the manner of cat-5/6e and with an outer shielded shieth.


I at first thought that the caveat about round cables was all hype, until I noticed problems burning DVD's on a particular 3.4gHz P4 system I had.


I ended up replacing everything in the system trying to eradicate the problem.

New motherboards, software, OS installs, power supply case, everything, but I kept the same type of round cables (though I did swap them for a different set...) EVERYTHING.

The same problem continued even though it was seemingly impossible given the completely revamped machine...

Then one day I put in a set of flat cables and routed them away from the mainboard while bending/folding them up against the new case sides.

The problems went away immediately.

I couldn't believe that the cables could be to blame so I tried a couple of different pairs from other manufacturers. One rounded set gave me decent results, another the same problem as before.


Finally I scoped the signals on a fast Tek scope.

Sure enough on some of the rounded cables noise induction could be seen as well as more than expected "ringing".

So watch out.

Not all rounded cables are bad, but some are much better than others.

See: http://www.dansdata.com/rcables.htm

thanks for the info.

nothing works... with the dvd
 

ok, everything's well connected, i have read faqs ant done everything opjose said before.
I compared to windows to discard device failure., and as i said, everything's works fine there.
so... any other idea to get my IDE1 well identified?
As i said, when i first installed mdk10official, i had the same problem but once i booted with other kernel included with that version (the one labeled as 'linux-smp' on the LiLo boot menu) everything started work fine, even if i booted with the normal 'linux' kernel. That makes me think i have one kernel module missing to handle the IDE the right way. My motherboard is an Shikatronics model SHP4VQF24S and uses a VIA PM800 + VIA 8237 Chipset
thanx again
:)

It's unlikely that it's a missing kernel module, as the ide interface modules are rolled into the initrd image for that kernel....


However it could well be the initrd image itself which is to blame.

After you installed the smp kernel, the process may have created NEW initrd images, cleaning up the problem.

Any time you modify the boot themes and kernel parameters a new initrd image is automatically created for you.

Info on initrd, boot theme, etc.
 

Thanks again opjose...
well... this is kinda new for me. I've never dealed with boot parameters and initrd images... where do i find information (online or printed docs) about this so i can try to fix this problem. Serious, I have no idea where to start.
Thanx again
triaydev
:D

Basically the way it works is like this...

initrd images are stored in /boot

They are used to "preload" any modules along with the kernel, so that once the kernel starts to run, it has sufficient resources available to it, to find the hard drives and continue initialization of the system.

Usually the initial installation merely copies out the contents of an initrd image to the /boot directory which is used during the first stage boot.

When you subsequently load a new kernel via urpmi or rpm, the installation wants to see what you may have manually added to your system (such as a raid array) so it builds a NEW initrd image for the new kernel you are installing.

When it does this it uses the entries in /etc/modprobe.conf and /etc/modules.conf to determine which drivers to add to the initrd image.

Programs such as the bootsplash and lilo gui's will automatically do this for you as well... but you can also do it manually.

For example; if your SMP kernel is working and up and running, but you want to generate a new initrd image for the uniprocessor kernel... and you have kernel-2.6.8.1-12mdk, all you would have to do is type as root


mkinitrd /boot/initrd-2.6.8.1-12mdk.img 2.6.8.1-12mdk

where the /boot/initrd-2.6.8.1-12mdk.img indicates the name of the file it is to create (in this case it should already exist and ask you if you wish to overwrite, to which you answer YES...)...

and 2.6.8.1-12mdk specifies which kernel modules are to be used, in this case namely those from the UNIPROCESSOR 2.6.8.1-12mdk installed kernel.

After it succeeds (you merely get a prompt back after the overwrite message...) you need to run lilo again to get the boot loader to recognize the changes.

The mystery of dvd and ide1
 

Aright. The mystery remains...
Today I turned on my computer and suddenly i found i had access to my dvd.
My motherboard usually doesn't start up if i have any USB device plugged in but this didn't happen today, booted up normally and when i got my deskop loaded i found the dvd correctly configured.
Now, the ONLY thing i did was installing an trying to configure the demo version of vmware up and running. I haven't run any virtual machine yet.
I'm surprised and really curious about what vmware did. Maybe it's because it does something with the rd scripts. That reminds me what opjose told me about the init images.

At the end... this never happened to me with MDK 9.x but 10.0 and 10.1 has got me this problems and, beside, i find the 10.x versions buggy compared with 9.2 so, now i'm near of holydays i'm thinking about give Debian a chance (i'm downloading the latest version) .

Any suggestions? can anybody tell me about that?

thanks!
triaydev
:)

No, it's unlikely to be anything with VMWARE.

Also 10.x is far more stable than 9.x, so you have something amiss.

I've seen the usb problems you mention but these have nothing to do with Mandrake or Linux.

Some motherboards have a tendancy to burn out the supply voltage stages of the on board USB hubs after a few months even with almost no use!

In this case you will get the strange behaviour you've observed.

e.g.

Inserting a usb device will prevent the system from booting or even getting past a post, devices (such as your DVD drive) will "disappear", etc.

It sounds like your motherboard is to blame for all the woes you are putting on Mandrake.