Krisbee Posted April 19, 2005 Report Share Posted April 19, 2005 (edited) I installed Mandrake 10.1 on to a drive attached to a Sil3112 SATA controller using "Linux noapic nolapic". The drive is seen as /dev/sda and the installer can create partitions on it, and the Mandrake install appears to be successful. But the boot hangs at the stage of scanning the drive on the SATA controller, with these messages: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ata1: SATA max UDMA/100 cmd 0xE09FC080 ctl 0xE09FC08A bmdma 0xE09FC000 irq 11 ata2: SATA max UDMA/100 cmd 0xE09FC0C0 ctl 0xE09FC0CA bmdma 0xE09FC008 irq 11 irq 11: nobody cared! [<c012fbea>] __report_bad_irq+0x2a/0x90 [<c012f5a0>] handle_IRQ_event+0x30/0x70 [<c012fcdc>] note_interrupt+0x6c/0xd0 [<c012f710>] __do_IRQ+0x130/0x160 [<c01042b9>] do_IRQ+0x19/0x30 [<c010289a>] common_interrupt+0x1a/0x20 [<c0117830>] __do_softirq+0x30/0x90 [<c01178b6>] do_softirq+0x26/0x30 [<c012f564>] irq_exit+0x34/0x40 [<c01042be>] do_IRQ+0x1e/0x30 [<c010289a>] common_interrupt+0x1a/0x20 [<c01005f0>] default_idle+0x0/0x30 [<c0100613>] default_idle+0x23/0x30 [<c010068a>] cpu_idle+0x3a/0x60 [<c03ca767>] start_kernel+0x147/0x160 [<c03ca360>] unknown_bootoption+0x0/0x1b0 handlers: [<c0273770>] (usb_hcd_irq+0x0/0x70) [<e0975580>] (snd_ice1712_interrupt+0x0/0x250 [snd_ice1712]) [<e0a65460>] (ata_interrupt+0x0/0x1c0 [libata]) Disabling IRQ #11 ata1: dev 0 cfg 49:2f00 82:346b 83:7f21 84:4003 85:3469 86:3c01 87:4003 88:203f ata1: dev 0 ATA, max UDMA/100, 390721968 sectors: lba48 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ (Actually taken from another news group - someone with an ASUS A7N8X, but my messages are identical) My Linux knowledge is limited, so I don't know if it is a kernel problem, a libata problem or something in the motherboard BIOS I set incorrectly. I tried all possilbe combinations of noapic nolapic and disabled all other onboard devices to prevent the SATA controller sharing an interrupt. None of this made any difference. My hardware is an Abit NF7-S v2 (BIOS 27) with a sil3112 RAID controller. The Hitachi PATA drive is attached to the SATA controler using Abit's serillel2 connector. My hardware is a common combination. It all works under Windows, but seemingly not under Linux. What have I missed? I'm a trying to do the impossible? If you've had this problem and know a workaround don't kept to yourself. Edited May 2, 2005 by Krisbee Quote Link to comment Share on other sites More sharing options...
adamw Posted April 19, 2005 Report Share Posted April 19, 2005 Did you try _not_ using noapic? I have an A7N8X-E Deluxe with silicon image controller and it worked fine with 10.1 with no special kernel boot options. Quote Link to comment Share on other sites More sharing options...
Krisbee Posted April 20, 2005 Author Report Share Posted April 20, 2005 Yes I did, as you can see from the first line of my original post it was installed using "Linux noapic nolapic" and these optiions are carried over into the GRUB botloader. Believe me I fiddled around with every combination I could, but always go the same result, the boot would hang with the same interrupt error. Just to add that on the Abit Nf7-S you have both the SATA controller and SATA boot rom enabled in the BIOS inorder for any drive attached to the SATA controller to be seen. Any other ideas? Is there anyone out there with the same hardware as me who has got this working with Mandrake 10.1? It's wierd, and very frustratiing, that the installer can see the drive (I suppose some kind of minimal Linux is running at this stage), partition it and install Mandrake 10.1 on it. but then just not boot. Quote Link to comment Share on other sites More sharing options...
Krisbee Posted May 2, 2005 Author Report Share Posted May 2, 2005 After playing around with this I have still not been able to boot from a drive connected to the SATA controller. But I have been able to detect, mount, read and write to the SATA drive if I use kernel 2.6.11-6mdk on an otherwise standrad Mdk 10.1 IDE install. But this only works if I add these modules to the "modules.preload" file: # /etc/modprobe.preload: kernel modules to load at boot time. # # This file should contain the names of kernel modules that are # to be loaded at boot time, one per line. Comments begin with # a `#', and everything on the line after them are ignored. # this file is for module-init-tools (kernel 2.5 and above) ONLY # for old kernel use /etc/modules scsi_mod libata sata_sil nvidia-agp This is an extract from the logs which shows the detection of the SATA drive with the system booting from an IDE drive: Apr 29 15:26:19 sparky kernel: VFS: Mounted root (cramfs filesystem) readonly. Apr 29 15:26:19 sparky kernel: kjournald starting. Commit interval 5 seconds Apr 29 15:26:19 sparky kernel: EXT3-fs: mounted filesystem with ordered data mode. Apr 29 15:26:19 sparky kernel: Freeing unused kernel memory: 264k freed Apr 29 15:26:19 sparky kernel: usbcore: registered new driver usbfs Apr 29 15:26:19 sparky kernel: usbcore: registered new driver hub Apr 29 15:26:19 sparky kernel: USB Universal Host Controller Interface driver v2.2 Apr 29 15:26:19 sparky kernel: EXT3 FS on hdc1, internal journal Apr 29 15:26:19 sparky kernel: Adding 257000k swap on /dev/hdc5. Priority:-1 extents:1 Apr 29 15:26:19 sparky kernel: Adding 136512k swap on /dev/hdc9. Priority:-2 extents:1 Apr 29 15:26:19 sparky kernel: SCSI subsystem initialized Apr 29 15:26:19 sparky kernel: ata1: SATA max UDMA/100 cmd 0xE0810080 ctl 0xE081008A bmdma 0xE0810000 irq 11 Apr 29 15:26:19 sparky kernel: ata2: SATA max UDMA/100 cmd 0xE08100C0 ctl 0xE08100CA bmdma 0xE0810008 irq 11 Apr 29 15:26:19 sparky kernel: ata1: dev 0 ATA, max UDMA/100, 80418240 sectors: lba48 Apr 29 15:26:19 sparky kernel: ata1: dev 0 configured for UDMA/100 Apr 29 15:26:19 sparky kernel: scsi0 : sata_sil Apr 29 15:26:19 sparky kernel: ata2: no device found (phy stat 00000000) Apr 29 15:26:19 sparky kernel: scsi1 : sata_sil Apr 29 15:26:19 sparky kernel: Vendor: ATA Model: HDS722540VLAT20 Rev: V31O Apr 29 15:26:19 sparky kernel: Type: Direct-Access ANSI SCSI revision: 05 Apr 29 15:26:19 sparky kernel: Linux agpgart interface v0.100 © Dave Jones Apr 29 15:26:19 sparky kernel: agpgart: Detected NVIDIA nForce2 chipset Apr 29 15:26:19 sparky kernel: agpgart: Maximum main memory to use for agp memory: 439M Apr 29 15:26:19 sparky kernel: agpgart: AGP aperture is 256M @ 0xc0000000 Apr 29 15:26:19 sparky kernel: SCSI device sda: 80418240 512-byte hdwr sectors (41174 MB) Apr 29 15:26:19 sparky kernel: SCSI device sda: drive cache: write back Apr 29 15:26:19 sparky kernel: SCSI device sda: 80418240 512-byte hdwr sectors (41174 MB) Apr 29 15:26:19 sparky kernel: SCSI device sda: drive cache: write back Apr 29 15:26:19 sparky kernel: /dev/scsi/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 p9 > Apr 29 15:26:19 sparky kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 Apr 29 15:26:19 sparky kernel: kjournald starting. Commit interval 5 seconds What is weird is that the messages which show these modules being loaded appear after the drive is detected ! What's going on? In anycase, this is of limited use to me unless I can boot from the SATA drive to free up IDE channels. Trying to boot from the SATA drive produces a kernel panic with an int error. I'd still like to hear from anyone who has got this to work on the same hardware as mine (Abit N7F-S v 2 with serillel apdater) without reverting to 2.4 series kernels. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.