[Fedora-ia64-list] Re: [Bug 205970] text install from cdrom fails, cdrom is not mounted for rpm

[John L. Bass]

Prarit Bhargava <prarit at redhat.com> writes:
> John L. Bass wrote:
> > Thanks ... I don't see an updated schedule, so i guess the Sept 14 date
> > is still a go for FC6T3 release ... I can wait a couple days. Good luck
> > on the panic resolution.
> >
> > What IA64 machines are your QA guys regression testing against? 

> SGI, HP, Fujitsu ...

I understand that HP is using their own I/O chips, that are not clones of the
Intel PCI/ISA bridges. What about the other guys? This Supermicro box is using:

[root at ollie root]# cat /etc/issue
Red Hat Enterprise Linux AS release 3 (Taroon)
Kernel \r on an \m

[root at ollie root]# lspci
00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 02)
00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 02)
00:1d.2 USB Controller: Intel Corp. 82801DB USB (Hub #3) (rev 02)
00:1d.7 USB Controller: Intel Corp. 82801DB USB2 (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB PCI Bridge (rev 82)
00:1f.0 ISA bridge: Intel Corp. 82801DB LPC Interface Controller (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801DB Ultra ATA Storage Controller (rev 02)
00:1f.3 SMBus: Intel Corp. 82801DB/DBM SMBus Controller (rev 02)
01:02.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
02:1c.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04)
02:1d.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04)
02:1e.0 PIC: Intel Corp. 82870P2 P64H2 I/OxAPIC (rev 04)
02:1f.0 PCI bridge: Intel Corp. 82870P2 P64H2 Hub PCI Bridge (rev 04)
03:02.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
03:02.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)

The box didn't have a problem installing or running with the ATA CDROM under RH AS3,
as you might note.

> > I'm
> > a little concerned the NPF reply to this install bug from your QA
> > lab is likely the same regression set used to test FC6T2 last month.
> > I can only assume the problem wasn't seen that cycle either.
> >
> >   

> We haven't seen anything like this.  Could you update the closed BZ with 
> the info in your original reply?

Will do. I suggest that your staff reopen it until formally resolved, as an NPF
just because the QA regression didn't see it for either FC6T2 or FC6T3 isn't
enough data to close the ticket.

John

PS ... this is how far the text install got before failing without a cdrom:

[root at ollie root]# ls -R /fedora
/fedora:
boot  dev  etc  lost+found  proc  rhinstall-stage2.img  root  selinux  sys  tmp  var

/fedora/boot:
efi

/fedora/boot/efi:

/fedora/dev:

/fedora/etc:
fstab  hosts  modprobe.conf  mtab  resolv.conf  rpm  sysconfig  X11

/fedora/etc/rpm:
macros  platform

/fedora/etc/sysconfig:
network  network-scripts

/fedora/etc/sysconfig/network-scripts:
ifcfg-eth0  ifcfg-eth1

/fedora/etc/X11:

/fedora/lost+found:

/fedora/proc:

/fedora/root:
install.log  install.log.syslog

/fedora/selinux:

/fedora/sys:

/fedora/tmp:

/fedora/var:
cache  lib  tmp

/fedora/var/cache:
yum

/fedora/var/cache/yum:

/fedora/var/lib:
rpm

/fedora/var/lib/rpm:
__db.001  __db.002  __db.003  Packages  Providename

/fedora/var/tmp:
[root at ollie root]#