From: Michel <mi...@da...> - 2002-07-31 19:14:53
|
On Wed, 2002-07-31 at 00:17, Daniel Palmer wrote:=20 >=20 > >The output you posted shows that the kernel panics when it probes for >P= CI=20 > >hardware. Do you have a PCI daughter board or something? I think >these=20 > >have been reported to interfere with the PCI code for the >B/CVision car= ds. >=20 > I've been disscusing this via e-mail with someone else on the list over t= he=20 > past couple days .. I'm CC:'ing the list, hoping that others can benefit. > I think we rounded it down to a PCI problem because i later discovered th= at > i can't boot 2.2.x kernels that have the PCI stuff in so i'm currently us= ing > the latest prebuilt kernel that doesn't do a PCI probe. The strange thing > is i don't have any real pci devices or a bus board, i only have the bliz= zard > vision (which is a pci device , but shouldn't really crash the probe :/) = connected. >=20 > The blizzard is flashed with the last phase5 rom ( i've also tried the DC= E=20 > one with the pci stuff , but that seemed to nock the BV out ) , its left = me=20 > completly puzzled , as i haven't got any pci hardware and i'm booting APU= S=20 > from its own clean harddrive with only a small 0s3.1 install on to get it= =20 > booted. >=20 > Maybe it thinks i've got a busboard or something ( i wish :) ) The problem I suspected would be the other way around, that it would get confused by a bus board when it expects a B/CVision. > >Are you using pm2fb in console? Otherwise try without >Option=20 > >"UseFBDev",you'd be missing out on pm2fb though. >=20 > I'm using the pm2fb console , IIRC 1024x768-60 , i was told to try a nice= =20 > standard mode , but alas that didn't help either The funny thing is that the PCI code is taken from pm2fb. The X problem might be related, my only guess is that it's somehow related to the Firmware upgrade. --=20 Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast |