SCIENTIFIC-LINUX-USERS Archives

March 2006

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Dushan Mitrovich <[log in to unmask]>
Reply To:
Dushan Mitrovich <[log in to unmask]>
Date:
Thu, 2 Mar 2006 00:09:26 -0700
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (29 lines)
"Bly, MJ \(Martin\)" <[log in to unmask]> wrote:
> Yes, munge = edit.
> 
> The file is called pcitable and lives in the modules directory of
> initrd.img.  It provides a match list between device ids and driver
> names.  There's another file called pci.ids which associates text with
> the numbers.  You can find recipes for untangling initrd.img files and
> adding drivers etc using google.

Okay, I've found several sets of instructions using google, and as soon
as I've digested them and tried them I'll report back progress.  Again,
thanks.
 
> If the device ids (as reported by lspci -n) don't match what's in
> pcitable, it won't recognise a card as being useable by a driver.  (Some
> drivers are extra picky and do their own checks, particularly graphics
> card drivers - but that's another story).
> 
> I think the only problem is deciding which image (.img file) is the one
> you need to 'edit'.  Connie or Troy can say for definite - it usually
> takes me several goes to get it right, which is why I don't do it unless
> can't think of another way to install.  You may have to create more than
> one - both the boot (installer) image and the kernel image(s) you're
> installing.

I'll puzzle over this when I get to that stage.

- Dushan

ATOM RSS1 RSS2