On Thu, 2006-06-29 at 13:38 +0300, Pasi Kärkkäinen wrote: > On Tue, Jun 20, 2006 at 11:41:07AM +0300, Pasi Kärkkäinen wrote: > > On Mon, Jun 19, 2006 at 12:16:28PM +0100, Paul Howarth wrote: > > > Pasi Kärkkäinen wrote: > > > >>Are you sure your actual hardware matches one of the PCI IDs listed? > > > >>What's the output of "lspci -n"? > > > >> > > > > > > > >Yep, it does match. Verified with lspci -n. > > > > > > > >And I'm able to install centos 4.3 with similar selfmade dd image to the > > > >same box.. > > > > > > > >I'm currently reading the anaconda installer sources to find out what's > > > >happening.. anaconda/loader2/driverdisk.c > > > > > > > >Good ideas very welcome.. :) > > > > > > Given that your driver disk building process seems OK judging by the > > > success on Centos 4.3, this may be worth a bugzilla ticket on FC5 > > > anaconda; you might get some help from the "other side of the fence" > > > that way. > > > > > > > I submitted bugzilla entry about this.. > > > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=195899 > > > > Not much comments/help.. :( > > Any ideas how I could debug this? > > The driver modules itself are OK.. I can successfully load them by using > insmod during the installer.. so how can I figure out the problem with the > other files on dd? All the files look OK to me. You'll probably have to try debugging it yourself. You could try the anaconda devel list but I didn't get any help there when I was having driver disk issues... I suppose there's always fedora-devel-list too. Paul.
