Date: Sat, 15 Jan 2011 23:30:35 +0100 From: "Marek Salwerowicz" <marek_sal@wp.pl> To: "Alexander Motin" <mav@FreeBSD.org> Cc: current <current@freebsd.org> Subject: Re: Soekris net5501-70 problem with loading ATA modules onFreeBSD-Current Message-ID: <0A45D61F328244969D19C8A45A03F92D@marekdesktop> References: <mailpost.1295099154.9461759.68423.mailing.freebsd.current@FreeBSD.cs.nctu.edu.tw> <4D31FF65.6010000@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> I think these errors caused by devices created for legacy ISA > compatibility via device hints. Go to device.hints and remove all ATA > stuff from there to force ATA to be detected only via PCI. > > Another problem I see here with module load order. Loading atapci before > ataadm will make generic driver attach to controller, not specific one. > Unluckily loading in different order won't help, I think, because ataamd > depends on atapci and will load it automatically. > Hi, we have commented these lines in device.hints: > #hint.ata.0.at="isa" > #hint.ata.0.port="0x1F0" > #hint.ata.0.irq="14" > #hint.ata.1.at="isa" > #hint.ata.1.port="0x170" > #hint.ata.1.irq="15" and now there are no errors in dmesg, but: 1. ataamd doesn't load automatically atapci.ko, so I kept the order. 2. after loading modules and # atacontrol detach ata0 # atacontrol attach ata0 I can't still see my CF connected to net5501. Is it possible to load dynamically modules or do they have to be compiled in kernel... ? -- Marek Salwerowicz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0A45D61F328244969D19C8A45A03F92D>