I got it run by skipping the probe of ide0, it works as /dev/sdaX But It is really strange.
On 6/26/05, Johnny Hughes mailing-lists@hughesjr.com wrote:
On Sun, 2005-06-26 at 14:58 +0800, Ceg Ryan wrote:
I installed a 4.1 x86_64 with kernel 2.6.9-11.ELsmp (rpm) initially. My box is tyan 5350 and a SATA harddisk The install was successful and the harddisk was detected as /dev/sdaX
But strangely, when I first reboot my machine. The harddisk change to /dev/hdaX
What is the problem ?
Below are some of dmesg output
hda: WDC WD1200JD-00HBB0, ATA DISK drive Probing IDE interface ide1... Probing IDE interface ide2... Probing IDE interface ide3... Probing IDE interface ide4... Probing IDE interface ide5... Using cfq io scheduler ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hda: max request size: 1024KiB hda: 234441648 sectors (120034 MB) w/8192KiB Cache, CHS=16383/255/63 hda: cache flushes supported hda: hda1 hda2 hda3 hda4 < hda5 > ide-floppy driver 0.99.newide usbcore: registered new driver hiddev usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.0:USB HID core driver mice: PS/2 mouse device common for all mice 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, 112Kbytes TCP: Hash tables configured (established 524288 bind 37449) Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 ACPI: (supports S0 S1 S5) ACPI wakeup devices: PCE0 PCE1 PCIX PCIB USB1 USB2 USBE KBC0 MSE0 Freeing unused kernel memory: 164k freed SCSI subsystem initialized libata version 1.10 loaded. ata_piix version 1.03 ACPI: PCI interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 193 ata: 0x1f0 IDE port busy PCI: Setting latency timer of device 0000:00:1f.2 to 64 ata1: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1478 irq 15 ata1: SATA port has no device. scsi0 : ata_piix _______________________________________________
Are you able to use the machine?
(Seems like it is booted, if you have a dmesg)
I have never seen this specifically, but I don't have that board or even that controller (Intel 6300ESB).
Looks like there is a difference in the way the SMP kernel sees the machine as compared to the non-smp kernel.
BodyID:8823902.2.n.logpart (stored separately)
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos