Re: Missing fileset devices.pci.1410f101

From: Vadim Getmanshchuk (someonet_at_somewhere.com)
Date: 08/28/03


Date: Thu, 28 Aug 2003 00:03:00 GMT


"The Threatener" <nealskywalker@aol.comm> wrote in message
news:20030819020227.08076.00000728@mb-m06.aol.com...
> >> I'm installing AIX 5.2 on a LPAR. After installation I get this
> >> message:
> >>
> >> devices.pci.1410f101
> >> devices.pci.86802912
> >> devices.pci.ethernet
> >> devices.pci.pciclass.0200
> >>
> >> Not found on installation media.
> >>
> >> I can't find anything about a device file for 1410f101. Do you know
> >> anything about this device file?
> >
> >From an old post of mine:
> >
> >
> >AFAIK you can ignore the warning. I have had a simliar problem during a
nim
> >installation.
> >Answer from IBM: ( Just from memory )- Do not worry about the message.
> >cfgmgr tried to load/install some extra software for similar devices.
After
> >reruning cfgmgr -v does not give a error message like: could not
configure
> >device . everthing should be Ok.
>
> As long as everything is seen and working as it should of course. Did a
quick
> surf and:
>
> http://dbforums.com/arch/127/2002/3/333527

Ok, he sayes " I got the driver from a CD "AIX 4.3.3 Additional Device
Software", that was included in the shipment." Have anybody tried? I do not
have the CD. If somebody wants to share those files with me - I'll be
happiest man on the planet. :)

Thanks,
Vadim,



Relevant Pages

  • Re: AT&T strikes again
    ... access to USENET. ... No warning, AFAIK. ... Hello, Astrasweb. ...
    (rec.outdoors.rv-travel)
  • Re: AT&T strikes again
    ... No warning, AFAIK. ... Hello, Astrasweb. ... and I intend on changing over to what ever else is available. ...
    (rec.outdoors.rv-travel)
  • Re: AT&T strikes again
    ... No warning, AFAIK. ... Hello, Astrasweb. ... and I intend on changing over to what ever else is available. ...
    (rec.outdoors.rv-travel)
  • Re: Look what the crappy update does to the compiler
    ... > Dunno if it's related, but did you also mention the incorrect ... > warning issue? ... AFAIK, ...
    (borland.public.delphi.language.basm)