Re: nforce2 vs. apic

2004-09-17 Thread Andriy Gapon
on 16.09.2004 23:35 yuri van Overmeeren said the following:
...
 You could check the abit site and update/flash the mainboard with the
 latest bios.
 
 but I'm not sure about the 'official' fixed status of the nf7 and nf7
 V2.0. Btw when flashing the bios make sure you get the correct bios, you
 can check your board to see if you have a normal NF7 or NF7 v2.0.
 flashing it with the wrong bios means bye bye bios.

this is the next thing on my list, thanks

 -I suggest chipmakers make a new standard for something and call it
 'apci', just to keep things clear...-

the more the merrier

-- 
Andriy Gapon
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: nforce2 vs. apic

2004-09-17 Thread Andriy Gapon
on 17.09.2004 00:18 Vulpes Velox said the following:
 I own a Abit NF7
 
 Yeah... I remember this. A bit... I remember having to tweak it a bit
 to get it to play nicely. IIRC 5.2.1 does not have apic in by defualt?
 I may just haved removed it... I forget now, but any ways. Before
 trying apic, make sure your kernel has it. If your kernel does not, go
 into the setup screen and turn it off. I never had any ACPI problems
 with it and that has all ways worked well, minus a warning about a odd
 character or the like in it at startup.

I have also never had any ACPI problems, and everything is fine if APIC
is disabled either in BIOS or in kernel, but when it is enabled in both
the system freezes.

 So far my only complaint with it has been the onboard vr ethernet chip
 appears to suck compared to the dc pci card I have been using. Not
 taken the time to sort that out yet. Appears some what slow under
 heavy load. Think that has to do with a problem with device polling
 for that chipset.

Btw, to be precise I have NF7-S and I use network driver from
ports/net/nvnet, works fine for me, although I never did any performance
benchmarking.

-- 
Andriy Gapon
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


nforce2 vs. apic

2004-09-16 Thread Andriy Gapon

I have nforce2-based motherboard Abit NF7 and run 5.2.1-RELEASE on that
system. I have tried to enable APIC by compiling kernel with 'device
apic' (both with and without SMP option, although this is a UP system),
but system just freezes during boot with it. Everything works pretty
well without APIC, I was just curious about getting it to work.

I found this discussion:

http://lists.freebsd.org/pipermail/freebsd-current/2004-May/027316.html

and I have also found numerous reports on nforce2+APIC lockup problem in
Linux and some patches that were reported to help with it.

So, I want to find out if anything changed with respect to this in
FreeBSD, maybe some patches/workarounds, or success stories about
FreeBSD+nforce2+APIC.

Also some notes about my lockup. It happens at this point (exerpt for
non-verbose non-APIC dmesg):

psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
pmtimer0 on isa0
sc0: System console on isa0
sc0: VGA 16 virtual consoles, flags=0x200
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounter TSC frequency 1830012912 Hz quality 800
Timecounters tick every 10.000 msec
ipfw2 initialized, divert disabled, rule-based forwarding enabled,
default to accept, logging limited to 100 packets/entry by default
 In APIC case system freezes here 
GEOM: create disk ad0 dp=0xc6e15e60
ad0: 76319MB WDC WD800JB-00ETA0 [155061/16/63] at ata0-master UDMA100
acd0: CDRW TEAC CD-W552E at ata1-master UDMA33

Also, when system freezes keyboard LEDs still work properly and cursor
disappears when I press Scroll Lock, but arrow and PgUp/PgDown do not
work; if I try Alt-FN system speacker emits monotonic sound that can
not be turned off (except by reset, of course).

I am ready to provide any additional information. Unfortunately I am not
able to use serial console, so I can't give much info for APIC-enabled case.

-- 
Andriy Gapon
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: nforce2 vs. apic

2004-09-16 Thread yuri van Overmeeren
Andriy Gapon wrote:
I have nforce2-based motherboard Abit NF7 and run 5.2.1-RELEASE on that
system. I have tried to enable APIC by compiling kernel with 'device
apic' (both with and without SMP option, although this is a UP system),
but system just freezes during boot with it. Everything works pretty
well without APIC, I was just curious about getting it to work.
I found this discussion:
http://lists.freebsd.org/pipermail/freebsd-current/2004-May/027316.html
and I have also found numerous reports on nforce2+APIC lockup problem in
Linux and some patches that were reported to help with it.
So, I want to find out if anything changed with respect to this in
FreeBSD, maybe some patches/workarounds, or success stories about
FreeBSD+nforce2+APIC.
Also some notes about my lockup. It happens at this point (exerpt for
non-verbose non-APIC dmesg):
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
pmtimer0 on isa0
sc0: System console on isa0
sc0: VGA 16 virtual consoles, flags=0x200
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounter TSC frequency 1830012912 Hz quality 800
Timecounters tick every 10.000 msec
ipfw2 initialized, divert disabled, rule-based forwarding enabled,
default to accept, logging limited to 100 packets/entry by default
 In APIC case system freezes here 
GEOM: create disk ad0 dp=0xc6e15e60
ad0: 76319MB WDC WD800JB-00ETA0 [155061/16/63] at ata0-master UDMA100
acd0: CDRW TEAC CD-W552E at ata1-master UDMA33
Also, when system freezes keyboard LEDs still work properly and cursor
disappears when I press Scroll Lock, but arrow and PgUp/PgDown do not
work; if I try Alt-FN system speacker emits monotonic sound that can
not be turned off (except by reset, of course).
I am ready to provide any additional information. Unfortunately I am not
able to use serial console, so I can't give much info for APIC-enabled case.
 

5.2.1 freezes on a nforce2 mainboard with apci, I have a nforce2 (same 
abit board) based machine here running freebsd, never got the 
5.2.1-release to work with acpi.
It was fixed a little while after the release, 5-current has been 
running on the nforce2 for a while.
If you can wait untill the 5.3-release,which should be in about 2~3 
weeks, (and run 5.2.1 without acpi for that time) I would do that, 5.3 
no longer has the lock-up issue.

-yuri
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: nforce2 vs. apic

2004-09-16 Thread Andriy Gapon
on 16.09.2004 15:46 yuri van Overmeeren said the following:

 5.2.1 freezes on a nforce2 mainboard with apci, I have a nforce2 (same
 abit board) based machine here running freebsd, never got the
 5.2.1-release to work with acpi.
 It was fixed a little while after the release, 5-current has been
 running on the nforce2 for a while.
 If you can wait untill the 5.3-release,which should be in about 2~3
 weeks, (and run 5.2.1 without acpi for that time) I would do that, 5.3
 no longer has the lock-up issue.

Yuri,

have you really talked about acpi or apic ? Because I was talking about
apic. I have acpi enabled and apic disabled and that works fine. But I
want to try to enable apic.

-- 
Andriy Gapon
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: nforce2 vs. apic

2004-09-16 Thread yuri van Overmeeren

Andriy Gapon wrote:
on 16.09.2004 15:46 yuri van Overmeeren said the following:
 

5.2.1 freezes on a nforce2 mainboard with apci, I have a nforce2 (same
abit board) based machine here running freebsd, never got the
5.2.1-release to work with acpi.
It was fixed a little while after the release, 5-current has been
running on the nforce2 for a while.
If you can wait untill the 5.3-release,which should be in about 2~3
weeks, (and run 5.2.1 without acpi for that time) I would do that, 5.3
no longer has the lock-up issue.
   

Yuri,
have you really talked about acpi or apic ? Because I was talking about
apic. I have acpi enabled and apic disabled and that works fine. But I
want to try to enable apic.
 

:) oopsy I was talking about acpi, since that was also in the url you 
referred too (I should read better -smacks self). From what I've heard 
the apic doesn't work too well on nforce2 boards, appearantly there is 
an updated version of the bios that might fix this problem, I've read 
somewhere (little while ago) of a beta version of the new abit nf7 bios 
that fixes apic problems.

You could check the abit site and update/flash the mainboard with the 
latest bios.

but I'm not sure about the 'official' fixed status of the nf7 and nf7 
V2.0. Btw when flashing the bios make sure you get the correct bios, you 
can check your board to see if you have a normal NF7 or NF7 v2.0. 
flashing it with the wrong bios means bye bye bios.

-I suggest chipmakers make a new standard for something and call it 
'apci', just to keep things clear...-

-yuri
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: nforce2 vs. apic

2004-09-16 Thread Vulpes Velox
On Thu, 16 Sep 2004 14:14:55 +0300
Andriy Gapon [EMAIL PROTECTED] wrote:

 
 I have nforce2-based motherboard Abit NF7 and run 5.2.1-RELEASE on
 that system. I have tried to enable APIC by compiling kernel with
 'device apic' (both with and without SMP option, although this is a
 UP system), but system just freezes during boot with it. Everything
 works pretty well without APIC, I was just curious about getting it
 to work.
 
 I found this discussion:
 
 http://lists.freebsd.org/pipermail/freebsd-current/2004-May/027316.html
 
 and I have also found numerous reports on nforce2+APIC lockup
 problem in Linux and some patches that were reported to help with
 it.
 
 So, I want to find out if anything changed with respect to this in
 FreeBSD, maybe some patches/workarounds, or success stories about
 FreeBSD+nforce2+APIC.
 
 Also some notes about my lockup. It happens at this point (exerpt
 for non-verbose non-APIC dmesg):
 
 psm0: PS/2 Mouse irq 12 on atkbdc0
 psm0: model IntelliMouse, device ID 3
 pmtimer0 on isa0
 sc0: System console on isa0
 sc0: VGA 16 virtual consoles, flags=0x200
 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on
 isa0 Timecounter TSC frequency 1830012912 Hz quality 800
 Timecounters tick every 10.000 msec
 ipfw2 initialized, divert disabled, rule-based forwarding enabled,
 default to accept, logging limited to 100 packets/entry by default
  In APIC case system freezes here 
 GEOM: create disk ad0 dp=0xc6e15e60
 ad0: 76319MB WDC WD800JB-00ETA0 [155061/16/63] at ata0-master
 UDMA100 acd0: CDRW TEAC CD-W552E at ata1-master UDMA33
 
 Also, when system freezes keyboard LEDs still work properly and
 cursor disappears when I press Scroll Lock, but arrow and
 PgUp/PgDown do not work; if I try Alt-FN system speacker emits
 monotonic sound that can not be turned off (except by reset, of
 course).
 
 I am ready to provide any additional information. Unfortunately I am
 not able to use serial console, so I can't give much info for
 APIC-enabled case.

I own a Abit NF7

Yeah... I remember this. A bit... I remember having to tweak it a bit
to get it to play nicely. IIRC 5.2.1 does not have apic in by defualt?
I may just haved removed it... I forget now, but any ways. Before
trying apic, make sure your kernel has it. If your kernel does not, go
into the setup screen and turn it off. I never had any ACPI problems
with it and that has all ways worked well, minus a warning about a odd
character or the like in it at startup.

I also ran into another problem of my board not liking two ram sticks
in dual channel mode... would cause a lock up around booting... iirc
it would nearly finish and then lock up and KB LEDs would work a bit.

So far my only complaint with it has been the onboard vr ethernet chip
appears to suck compared to the dc pci card I have been using. Not
taken the time to sort that out yet. Appears some what slow under
heavy load. Think that has to do with a problem with device polling
for that chipset.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]