Bug 63222 - old closed bug appears again: no or wrong device in neat
old closed bug appears again: no or wrong device in neat
Status: CLOSED CURRENTRELEASE
Product: Red Hat Public Beta
Classification: Retired
Component: redhat-config-network (Show other bugs)
skipjack-beta2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
:
Depends On:
Blocks: 61901 67218
  Show dependency treegraph
 
Reported: 2002-04-11 07:22 EDT by Need Real Name
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-06-21 16:14:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2002-04-11 07:22:03 EDT
Description of Problem:
On a Dell Inspiron 8100 laptop with Nvidia Geforce 2 GO the following problem
is observed concerning an Intel PRO/100 pcmcia card with driver xirc2ps_cs:
On first configuring networking the correct 'device/driver' was first shown
under Hardware-Description of Network Configuration, namely 'xirc2ps_cs'.
Now, after a couple of days a 'relapse' has occured and "Xircom PMCIA ethernet
driver" is entered under Hardware-Description.
(everything continues to function OK).


Version-Release number of selected component (if applicable):
redhat-config-network-0.9.21-1
kernel-2.4.18-0.13


How Reproducible:


Steps to Reproduce:
1. 
2. 
3. 

Actual Results:


Expected Results:


Additional Information:
A related bug (62256, duplicate of 61722) was reported where no device
appeared at all under Hardware-Devices, Skipjack beta 1.
Comment 1 Trond Eivind Glomsrxd 2002-04-11 17:10:08 EDT
This looks very much like bug #63221?
Comment 2 Trond Eivind Glomsrxd 2002-04-11 20:27:19 EDT
Is this still an issue with 0.9.24-1 at http://people.redhat.com/teg/neat/ ?

Note You need to log in before you can comment on or make changes to this bug.