Bug 15800

Summary: Dell WS63 and ide/pci configuration
Product: [Retired] Red Hat Linux Reporter: Rogelio Noriega <rogelio_noriega>
Component: anacondaAssignee: Michael K. Johnson <johnsonm>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: todd
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-08-17 15:54:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
ANACDUMP.txt
none
PCI.TXT none

Description Rogelio Noriega 2000-08-09 12:56:40 UTC
System description:

WS 630 prototype
Dual 800 MHz CPUs
128 MB ECC RDRAM
40 MB IDE HDD
Matrox G400 AGP

Factory download correctly connects to the network and downloads the RPMS.

The installation fails with an anaconda error (line 426) with manual
install from HDD or CDROM and with kickstart install.  The anaconda dump is

Comment 1 Rogelio Noriega 2000-08-09 12:57:51 UTC
Created attachment 2275 [details]
ANACDUMP.txt

Comment 2 Rogelio Noriega 2000-08-09 12:58:42 UTC
Created attachment 2276 [details]
PCI.TXT

Comment 3 Rogelio Noriega 2000-08-09 13:00:38 UTC
The anaconda dump is attached along with the results of cat /proc/pci.

Comment 4 Glen Foster 2000-08-13 17:46:42 UTC
Is this hardware generally available?  If not, what's the possibilty of sending
it to our Durham site so we can reproduce this prior to release? Time is SHORT
-- RC2 is 21-Aug.  Please reply ASAP.

Comment 5 Rogelio Noriega 2000-08-16 03:53:30 UTC
I sent the system to Doug Ledford I checked the Airborne status and it arrive 
at RedHat on 14 August D. Long signed for the system. Any question please 
contact me directly. Rogelio_Noriega

Comment 6 Michael Fulbright 2000-08-17 15:48:54 UTC
The traceback is because the kernel (via uname) reports the arch is i?86 (yes
?).

RPM tries to match up packages with the architecture, so it finds no matches,
causes the problem you saw.

There are additional issues related to this which are kernel related.

I'm assigning this bug to the kernel team.

Comment 7 Michael K. Johnson 2000-08-17 15:54:51 UTC
There are many potential problems here.  Intel says that our
current kernel, lacking FXSAVE/FXRESTOR, will simply not work
reliably with the P4.

I patched procfs to return 6 instead of ? (UGLY patch) and will
do the same for the uname system call.

Comment 8 Bill Nottingham 2000-08-17 15:57:15 UTC

*** This bug has been marked as a duplicate of 16294 ***