I went to install Gentoo on a friends box and I put a live cd in and booted, didn't work, so I put in a Knoppix CD, didn't work, so I put in a Suse CD and it didn't work, so I put an IDE cdrom in the computer and booted from that. The error comes quicker when using the 2.4 kernel than the 2.6 kernel. The system does not freeze, it just goes to a very basic command line. Reproducible: Always Steps to Reproduce: 1. Incert CD. 2. Boot Computer 3. Wait Actual Results: The minimal command line came up. Expected Results: The software should see the S-ATA cdrom and the CD inside of it. Not many people have S-ATA cdrom drives, but it is a problem for anyone who does.
We didn't have support for SATA on the 2004.3 LiveCD... It has been added for 2005.0, which will be out in a couple weeks...
So... did 2005.0 resolve this issue for you?
The recent 2005.1 installer CD didn't work on my computer. It recognizes the drives, but the installer hangs at the copy to tmpfs part. If I change the BIOS to run as ATA instead of AHCI, the installer has a kernel panic. I see that ahci is being loaded as well as ata_piix. I have a year old Dell 8400 with SATA drives.
Tried installation on an nForce4 board SATA with a SATA plextor PX-716SA. 2005.1 Universal AMD64 LiveCD. It boot, however it could not find the bootable media. No errors on booting the CD, just apparently detection of the optical drive itself. Tried noapic and doscsi with no improved results.
(In reply to comment #0) > I went to install Gentoo on a friends box and I put a live cd in and booted, didn't work, so I put in a Knoppix CD, didn't work, so I put in a Suse CD and it didn't work, so I put an IDE cdrom in the computer and booted from that. The > Not many people have S-ATA cdrom drives, but it is a problem for anyone who does. I have here the same Problems,but with an extern CD/DVD Rom connected per USB on a Dell Latitude D400. I have looking in the dmesg buffer and see something that the cdrom is established as an generic scsi (sr0) so I looked in the
(In reply to comment #0) > I went to install Gentoo on a friends box and I put a live cd in and booted, didn't work, so I put in a Knoppix CD, didn't work, so I put in a Suse CD and it didn't work, so I put an IDE cdrom in the computer and booted from that. The > Not many people have S-ATA cdrom drives, but it is a problem for anyone who does. I have here the same Problems,but with an extern CD/DVD Rom connected per USB on a Dell Latitude D400. I have looking in the dmesg buffer and see something that the cdrom is established as an generic scsi (sr0) so I looked in the ´shell´ environment and se under /dev/ that there is no /dev/sr0 That I generate the dev-entry mknod /dev/sr0 b 11 0 and now I can mount this cdrom:-)) But my problem is here located I dosen´t know what the init (exec /linuxrc) want to do with the live cdrom, cause I´m new here with gentoo, but I like the style.... Maybe some help-info for the right solution?
I'm trying to use Gentoo 2005.1 with a WD 80 mg "Caviar" SATA drive but the installation disk won't recognize it. The MB os KT600 with a VIA 8237 south bridge. The old EIDE 20 mb hd works.
Not recognising a hard drive has nothing to do with the CD detection. Your problem is not related to this bug.
"It took some Google-ing and an email to a guy in Germany (also using an ASUS8N-E mobo w/ Gentoo Linux) who got one around the same time I did to learn I needed to add "libata.atapi_enabled=1" to my grub.conf for Linux to "see" it, plus an upgrade to kernel 2.6.15-gentoo-r1 for burning functionality. Very little documentation from the Linux world (guess I get to write some!) and (worst of all) Plextor's site wasn't helpful in terms of letting me know if my mobo was actually compatible." This is from: http://www.newegg.com/Product/Product.asp?Item=N82E16827131351 Can anyone verify if this is indeed needed? If so, I can be sure it is added on x86/amd64/ppc's release materials.
I'm not sure if this is RESOLVED or not, can anyone verify if it has been solved?
Chris: Hi, I've got some new hardware that's affected with this on the 2006.1 amd64 release. I'll be trying that libata.atapi_enabled=1 in a sec, but I don't think it will help, since according to the kernel sources, atapi_enabled defaults to 1 since 2.6.16 anyway.
Ok, nothing helped. 'libata.atapi_enabled=1' and 'atapi_enabled=1' do nothing. Neither 2006.0 nor 2006.1 work. For reference, this is the hardware: Motherboard: Intel DG965RY CPU: Intel Core Duo 2 E6400 RAM: 2x 1Gb Crucial Rendition I do have a netboot server set up, so if you want specific kernel config testing, I either need a x86->amd64 kernel cross-compiler, or you can send binary kernels+initrd to me.
Strange. My new laptop (Dell D620) has a SATA CDROM and it works perfectly with no additional options. Which SATA driver does that board use? Mine uses the Intel PIIX/ICH SATA driver and it works perfectly.
# lspci -s 00:1f.2 -vvv 00:1f.2 SATA controller: Intel Corporation 82801HR/HO/HH (ICH8R/DO/DH) SATA AHCI Controller (rev 02) (prog-if 01 [AHCI 1.0]) Subsystem: Intel Corporation Unknown device 514d Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0 Interrupt: pin A routed to IRQ 19 Region 0: I/O ports at 4108 [size=8] Region 1: I/O ports at 411c [size=4] Region 2: I/O ports at 4100 [size=8] Region 3: I/O ports at 4118 [size=4] Region 4: I/O ports at 4020 [size=32] Region 5: Memory at 90625000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/4 Enable- Address: 00000000 Data: 0000 Capabilities: [70] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a8] #12 [0010] I'm busy installing this box using a really old 3ware controller and booting via USB memory stick now, and then I'll be able to test out kernels.
Ok, turns out to be a bug in the AHCI driver for certain hardware that follows the specification a little more closely than the driver did (lucky me, I have this hardware) - where certain SATA ports are totally ignored in the kernel (After working fine in the BIOS and during the initial bootloading). There's a fix that's going to the libata tree shortly, and thence into 2.6.19.
The 2007.0 media uses 2.6.19-r5, so this *should* be fixed.
