Hi,
here's my new config: http://nopaste.info/7c11afee7c.html
and here's the complete kernel build output: http://nopaste.info/34db985f16.html
The error message is this:
cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I.
-I/usr/src/sys/modules/ath/../../dev/ath
Hi,
I maybe should add that whenever I haven't explicitly mentioned the version of
FreeBSD I'm using, it's 9.0-RELEASE, as it is in this case. Is this maybe the
cause of confusion?
If you're still unsure why the build fails, please let me know how I can help
to resolve this issue.
Thank you!
Hello again,
here's the new kernel config: http://nopaste.info/d7929aa100.html
and here's the make output: http://nopaste.info/ae7826ba48.html
The error messages I get when building are these:
cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall
-Wredundant-decls
Hello,
I hope you had a pleasant trip. Sorry for not replying for a while.
Anyway, I tried to do what you asked me to. However, it seems like I
misunderstood the handbook and/or your request, as I failed to compile the
kernel.
I copied my previous, working kernel config to a new file, and
Hello everyone,
I'm afraid I still don't know what exactly BAR is, or how I get its value that
I'm supposed to plug into the line John provided:
dd if=/dev/mem bs=4 iseek=((start of bar + reg offset)/4) count=1 | hd
I assumed that start of bar is 0xfdee in my case, since dmesg reports
ath0:
Hello,
thank you for your answer.
Unfortunately, I'm unexperienced with FreeBSD, and am absolutely unfamiliar
with hardware specifics. During this mail conversion, I have heard abour BAR
for the first time, and therefore, I know neither what exactly I should do
(e.g. how I can find the start
Hello everyone,
since this problem hasn't got any attention in the last 14 days, I decided to
file a bug report, so that this issue doesn't sink into oblivion:
http://www.freebsd.org/cgi/query-pr.cgi?pr=173883
I'm still very glad for any attempt to help, and willing to provide more
Hello again,
the mail I'm replying to (and which is cited below) hasn't caused a reaction
yet. Seeing that this mailing list has quite a lot of traffic, I'm worried that
the mail, and the issue it tries to point out, will be forgotten.
Should I file a bug report in hopes that the issue will
Hello,
thank you for your reply.
I've entered the following
pciconf -r ath0@pci0:2:4:0 0:255
and received this output:
001b168c 02900406 0201 2008
fdee
5001 500111ad
0044 1c0a0110
01c20001 c6004000
Hello everyone,
I'm new to FreeBSD and wanted to install 9.0-RELEASE amd64 on a PC I was given.
At first glance, it seems like everything is working, except the wireless LAN
PCI card.
I started a thread on freebsd-wireless on the 31st of October (see here:
10 matches
Mail list logo
