nfe: can not cvs sources anymore!
Hello. Using these two sources for getting nfe() driver support for my FreeBSD 6.2-BETA/AMD64 box was pretty convenient in the past weeks due to my big interrupt problems using the nve() driver. But with yesterday, I can't get the sources anymore. nfe() isn't yet a part of the 6.2 BETA, that's what I looked first for, so can anybody help me out? Is nfe() a part of 6.2-REL in the near future or are there other reasons stop spreading the sources via that cvs source? Thanks for your help in advance, regards, Oliver ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nfe: can not cvs sources anymore!
On Sun, Nov 19, 2006 at 03:08:58PM +0100, O. Hartmann wrote: > Hello. > Using these two sources for getting nfe() driver support for my FreeBSD > 6.2-BETA/AMD64 box was pretty convenient in the past weeks due to my big > interrupt problems using the nve() driver. > But with yesterday, I can't get the sources anymore. nfe() isn't yet a > part of the 6.2 BETA, that's what I looked first for, so can anybody > help me out? Is nfe() a part of 6.2-REL in the near future or are there > other reasons stop spreading the sources via that cvs source? > > Thanks for your help in advance, > Did you try the version at http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html ? I use it and except for some peer-to-peer gigabit problems I didn't notice any other bad signs. It's far more stable that what we have now in the CVS tree. Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer pgpfeE8IJcsn8.pgp Description: PGP signature
Fatal trap 12 - while installing nvidia-driver for FreeBSD 6.1
Hi, I'm facing kernel panic when try to install nvidia-driver in FreeBSD 6.1. It happen when nvidia kernel module loaded. This is a part of error message: Warning device driver Fatal Trap 12 FYI, I'm still using generic kernel as will compile my own kernel with nvidia kernel module inside. But first I need to make sure that nvidia driver is installed in the system. Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nfe: can not cvs sources anymore!
Ruslan Ermilov wrote: > On Sun, Nov 19, 2006 at 03:08:58PM +0100, O. Hartmann wrote: > >> Hello. >> Using these two sources for getting nfe() driver support for my FreeBSD >> 6.2-BETA/AMD64 box was pretty convenient in the past weeks due to my big >> interrupt problems using the nve() driver. >> But with yesterday, I can't get the sources anymore. nfe() isn't yet a >> part of the 6.2 BETA, that's what I looked first for, so can anybody >> help me out? Is nfe() a part of 6.2-REL in the near future or are there >> other reasons stop spreading the sources via that cvs source? >> >> Thanks for your help in advance, >> >> > Did you try the version at > http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html > ? I use it and except for some peer-to-peer gigabit problems I > didn't notice any other bad signs. It's far more stable that > what we have now in the CVS tree. > > > Cheers, > Thank you for the link. No, I did not try this link since I thought the CVS tree's version was the stabelst version we have. I find it convenient by pushing it via net using cvs just after I upgraded my CVS tree of the sources for the operating system. I will keep this link in mind. Is there a date we can this driver expect in FreeBSD 6.2? Or is the driver more subject to be merged in 6.2-STABLE and for 6.3? nve() isn't suitable, neither with SCHED_ULE (which I use now again) and with SCHED_4BSD, because on my hardware platform the interrupt generation is much higher than that of the nfe() driver - and due to this massive interrupts useless for me. Regards, Oliver -- O. Hartmann Freie Universitaet Berlin Institut fuer Geowissenschaften Fernerkundung der Erde und Planeten Malteser-Str. 74 - 100/Haus D D-12249 Berlin Tel.: +49 (0) 30 838 70 508 FAX: +49 (0) 30 838 70 837 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Status of 3945ABG and others
On Sat, 18 Nov 2006 22:26:08 +0100 Christian Lopez de Castilla Wagner <[EMAIL PROTECTED]> wrote: > Sound is ALC861, Probably HDA, you should test the snd_hdac driver. Look on -multimedia mailinglist for clues. > wireless 3945ABG. As far as I know (and I'm interested, because I have a laptop with this device myself), nothing has happened on this front. It seems that Intel, for reasons of their own, isn't able to (or doesn't want to) release necessary docs to make a good driver. OpenBSD (4.0) have support for this via the wpi driver, but it doesn't support WPA yet, only WEP. Your best bet would be to a) exchange the network card, if possible. Some laptop network cards are miniPCI and can be exchanged, but I do not know if this is the case for the 3945ABG. b) use an external usb network "dongle". Look at the ural driver, you can find some of the supported devices quite cheap. I dont know how good they are, I have just tested one, and have some issues with it (stability) but haven't been able to rule out if it is something with my setup yet. HTH -- Regards, Torfinn Ingolfsen, Norway ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Status of 3945ABG and others
On Sat, 18 Nov 2006 22:26:08 +0100 Christian Lopez de Castilla Wagner <[EMAIL PROTECTED]> wrote: > wireless 3945ABG. I never got around to test the Hmm, I checked this one closer, it seems like the 3945 is a PCIe Mini card, according to http://www.intel.com/network/connectivity/resources/doc_library/tech_brief/310796.htm are there Atheros (ath) based PCIe MMini Cards for sale? -- Regards, Torfinn Ingolfsen, Norway ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Status of 3945ABG and others
On Sun, Nov 19, 2006 at 07:38:58PM +0100, Torfinn Ingolfsen wrote: > are there Atheros (ath) based PCIe MMini Cards for sale? Yes, in my IBM T60 i'm using this one: http://www5.pc.ibm.com/nl/products.nsf/$wwwPartNumLookup/_40Y7026?OpenDocument -- Regards, Richard. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Status of 3945ABG and others
On Sunday 19 November 2006 19:26, Torfinn Ingolfsen wrote: > On Sat, 18 Nov 2006 22:26:08 +0100 > > Christian Lopez de Castilla Wagner <[EMAIL PROTECTED]> wrote: > > Sound is ALC861, > > Probably HDA, you should test the snd_hdac driver. Look on -multimedia > mailinglist for clues. > > > wireless 3945ABG. > > As far as I know (and I'm interested, because I have a laptop with > this device myself), nothing has happened on this front. It seems that > Intel, for reasons of their own, isn't able to (or doesn't want to) > release necessary docs to make a good driver. > OpenBSD (4.0) have support for this via the wpi driver, but it doesn't > support WPA yet, only WEP. There is an experimental FreeBSD version of this driver available via: http://people.freebsd.org/~flz/local/wpi/ ... there are a couple of people interested in getting this working, see Threads on freebsd-net@ from October and November. > Your best bet would be to > a) exchange the network card, if possible. Some laptop network cards > are miniPCI and can be exchanged, but I do not know if this is the case > for the 3945ABG. > b) use an external usb network "dongle". Look at the ural driver, you > can find some of the supported devices quite cheap. I dont know how > good they are, I have just tested one, and have some issues with it > (stability) but haven't been able to rule out if it is something with > my setup yet. -- /"\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News pgpFvO5rBEi3O.pgp Description: PGP signature
Re: nfe: can not cvs sources anymore!
On Sun, Nov 19, 2006 at 07:25:41PM +0100, O. Hartmann wrote: > Ruslan Ermilov wrote: > > On Sun, Nov 19, 2006 at 03:08:58PM +0100, O. Hartmann wrote: > > > >> Hello. > >> Using these two sources for getting nfe() driver support for my FreeBSD > >> 6.2-BETA/AMD64 box was pretty convenient in the past weeks due to my big > >> interrupt problems using the nve() driver. > >> But with yesterday, I can't get the sources anymore. nfe() isn't yet a > >> part of the 6.2 BETA, that's what I looked first for, so can anybody > >> help me out? Is nfe() a part of 6.2-REL in the near future or are there > >> other reasons stop spreading the sources via that cvs source? > >> > >> Thanks for your help in advance, > >> > >> > > Did you try the version at > > http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html > > ? I use it and except for some peer-to-peer gigabit problems I > > didn't notice any other bad signs. It's far more stable that > > what we have now in the CVS tree. > > > > > > Cheers, > > > Thank you for the link. > No, I did not try this link since I thought the CVS tree's version was > the stabelst version we have. I find it convenient by pushing it via net > using cvs just after I upgraded my CVS tree of the sources for the > operating system. I will keep this link in mind. > Is there a date we can this driver expect in FreeBSD 6.2? Or is the > driver more subject to be merged in 6.2-STABLE and for 6.3? nve() isn't > suitable, neither with SCHED_ULE (which I use now again) and with > SCHED_4BSD, because on my hardware platform the interrupt generation is > much higher than that of the nfe() driver - and due to this massive > interrupts useless for me. Please remember to turn off SCHED_ULE before submitting any and all future bug reports, thanks :-) Kris pgpLjDP3DidGv.pgp Description: PGP signature
Re: Fatal trap 12 - while installing nvidia-driver for FreeBSD 6.1
On Mon, Nov 20, 2006 at 12:45:28AM +0800, Nik wrote: > Hi, > > I'm facing kernel panic when try to install nvidia-driver in FreeBSD 6.1. It > happen when nvidia kernel module loaded. This is a part of error message: > > Warning device driver > Fatal Trap 12 FYI, it's rarely a good idea to only include part of an error message. If the rest of the error message wasn't important then it wouldn't be displayed to you. > FYI, I'm still using generic kernel as will compile my own kernel with > nvidia kernel module inside. But first I need to make sure that nvidia > driver is installed in the system. One typically sees panics when using a kernel module that is built against a different set of kernel sources. How did you obtain the module? Kris pgpDlZmGr6laj.pgp Description: PGP signature
Re: nfe: can not cvs sources anymore!
Kris Kennaway wrote: > On Sun, Nov 19, 2006 at 07:25:41PM +0100, O. Hartmann wrote: > >> Ruslan Ermilov wrote: >> >>> On Sun, Nov 19, 2006 at 03:08:58PM +0100, O. Hartmann wrote: >>> >>> Hello. Using these two sources for getting nfe() driver support for my FreeBSD 6.2-BETA/AMD64 box was pretty convenient in the past weeks due to my big interrupt problems using the nve() driver. But with yesterday, I can't get the sources anymore. nfe() isn't yet a part of the 6.2 BETA, that's what I looked first for, so can anybody help me out? Is nfe() a part of 6.2-REL in the near future or are there other reasons stop spreading the sources via that cvs source? Thanks for your help in advance, >>> Did you try the version at >>> http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html >>> ? I use it and except for some peer-to-peer gigabit problems I >>> didn't notice any other bad signs. It's far more stable that >>> what we have now in the CVS tree. >>> >>> >>> Cheers, >>> >>> >> Thank you for the link. >> No, I did not try this link since I thought the CVS tree's version was >> the stabelst version we have. I find it convenient by pushing it via net >> using cvs just after I upgraded my CVS tree of the sources for the >> operating system. I will keep this link in mind. >> Is there a date we can this driver expect in FreeBSD 6.2? Or is the >> driver more subject to be merged in 6.2-STABLE and for 6.3? nve() isn't >> suitable, neither with SCHED_ULE (which I use now again) and with >> SCHED_4BSD, because on my hardware platform the interrupt generation is >> much higher than that of the nfe() driver - and due to this massive >> interrupts useless for me. >> > > Please remember to turn off SCHED_ULE before submitting any and all > future bug reports, thanks :-) > > Kris > Well, yes, I do this, and as I wrote above, the problem ist even worse with SCHED_4BSD. And SCHED_ULE is now my defaukt, beacause FreeBSD 6.2-PRE/AMD64 ADN i386 is as freezing for short periods of times as never seen before ... Regards, Oliver ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Re: hp c class blade
> I've installed FreeBSD 6.2 RC1 onto a BL460c blade. The installation
> itself went fine, but there is no network. The nic is on a broadcom 16
> ports GB switch on the backside of the blade-chassis.
What kind of NIC is it? Type "pcicinf -lv" and look for it.
If you tell us the name, vendor ID and device ID (or even
better, the whole section from pciconf output), someone
might be able to tell you details about the support status
of it in FreeBSD.
After reading
http://www.mail-archive.com/freebsd-stable@freebsd.org/msg83981.html
I added:
{ BRCM_VENDORID, BRCM_DEVICEIDBCM7808S, HP_VENDORID, 0x16AC,
"HP ... ADAPTER" },
to /usr/src/sys/dev/bce/if_bce.c.
After reboot I get SerDes controllers not supported in dmesg,
device_attach: bce0 attach returned 19.
Pciconf -lv says:
[EMAIL PROTECTED]:0:0: class=0x02 card=0x703b103c chip=0x16ac14e4 rev=0x11
hdr=0x00
vendor = Broadcom Corporation'
class = networl
subclass = ethernet
bce1 likewise.
There doesn't seem to be any available drivers atm. I (even :-)) tried
ubuntu 6.10 server (amd64) and it didn't detect any network-cards
either.
The switch is a 16 ports gb passthrough switch.
regards
Claus
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: systat -vm output showing negative total virtual memory
The change to vm_meter.c is ok. Could you please add a comment like that above the location of the patch. Alan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Status of 3945ABG and others
On Sun, 19 Nov 2006 19:48:17 +0100 Richard Arends <[EMAIL PROTECTED]> wrote: > Yes, in my IBM T60 i'm using this one: > http://www5.pc.ibm.com/nl/products.nsf/$wwwPartNumLookup/_40Y7026?OpenDocument > Interesting. This card (partnumber 40Y7026) seems to be the only other choice of mini-PCI express cards available in Norway. The other is - you guessed it - the infamous Intel 3945abg. Now, before I shell out some money for this, does anybody know if it will work in another laptop than the Lenovo / IBM? And, if anybody have experiedce with installing this card in an Acer laptop (AS5672) tha would be even better. -- Regards, Torfinn Ingolfsen, Norway ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nfe: can not cvs sources anymore!
On Sun, Nov 19, 2006 at 10:09:34PM +0100, O. Hartmann wrote: > Kris Kennaway wrote: > > On Sun, Nov 19, 2006 at 07:25:41PM +0100, O. Hartmann wrote: > > > >> Ruslan Ermilov wrote: > >> > >>> On Sun, Nov 19, 2006 at 03:08:58PM +0100, O. Hartmann wrote: > >>> > >>> > Hello. > Using these two sources for getting nfe() driver support for my FreeBSD > 6.2-BETA/AMD64 box was pretty convenient in the past weeks due to my big > interrupt problems using the nve() driver. > But with yesterday, I can't get the sources anymore. nfe() isn't yet a > part of the 6.2 BETA, that's what I looked first for, so can anybody > help me out? Is nfe() a part of 6.2-REL in the near future or are there > other reasons stop spreading the sources via that cvs source? > > Thanks for your help in advance, > > > > >>> Did you try the version at > >>> http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html > >>> ? I use it and except for some peer-to-peer gigabit problems I > >>> didn't notice any other bad signs. It's far more stable that > >>> what we have now in the CVS tree. > >>> > >>> > >>> Cheers, > >>> > >>> > >> Thank you for the link. > >> No, I did not try this link since I thought the CVS tree's version was > >> the stabelst version we have. I find it convenient by pushing it via net > >> using cvs just after I upgraded my CVS tree of the sources for the > >> operating system. I will keep this link in mind. > >> Is there a date we can this driver expect in FreeBSD 6.2? Or is the > >> driver more subject to be merged in 6.2-STABLE and for 6.3? nve() isn't > >> suitable, neither with SCHED_ULE (which I use now again) and with > >> SCHED_4BSD, because on my hardware platform the interrupt generation is > >> much higher than that of the nfe() driver - and due to this massive > >> interrupts useless for me. > >> > > > > Please remember to turn off SCHED_ULE before submitting any and all > > future bug reports, thanks :-) > > > > Kris > > > > > Well, yes, I do this, and as I wrote above, the problem ist even worse with > SCHED_4BSD. And SCHED_ULE is now my defaukt, beacause FreeBSD 6.2-PRE/AMD64 > ADN i386 is as freezing for short periods of times as never seen before ... Even with the above driver? Kris pgpFB92WBTw19.pgp Description: PGP signature
Re: Status of 3945ABG and others
> On Sun, 19 Nov 2006 19:48:17 +0100 > Richard Arends <[EMAIL PROTECTED]> wrote: > > > Yes, in my IBM T60 i'm using this one: > > http://www5.pc.ibm.com/nl/products.nsf/$wwwPartNumLookup/_40Y7026?OpenDocument > > > > Interesting. This card (partnumber 40Y7026) seems to be the only other > choice of mini-PCI express cards available in Norway. The other is - > you guessed it - the infamous Intel 3945abg. > Now, before I shell out some money for this, does anybody know if it > will work in another laptop than the Lenovo / IBM? > And, if anybody have experiedce with installing this card in an Acer > laptop (AS5672) tha would be even better. I don't know about availability in Norway, but the 73P4301 is an Atheros card. It is available in the US. http://shop.lenovo.com/SEUILibrary/controller/catalog.workflow:item.detail?Gro upID=38&Code=73P4301 $65 looks a bit high. You can probably get it cheaper on ebay or elsewhere. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpjw3P93qoeP.pgp Description: PGP signature
Re: Status of 3945ABG and others
On Sun, 19 Nov 2006 19:55:56 +0100 Max Laier <[EMAIL PROTECTED]> wrote: > There is an experimental FreeBSD version of this driver available > via: http://people.freebsd.org/~flz/local/wpi/ ... there are a couple This is indeed great news! I have tested the driver on my laptop, amd it works: [EMAIL PROTECTED] uname -a FreeBSD kg-home.kg4.no 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #3: Fri Nov 10 23:09:04 CET 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AS5672 i386 [EMAIL PROTECTED] ifconfig wpi0 wpi0: flags=8843 mtu 1500 inet 10.1.150.12 netmask 0x broadcast 10.1.255.255 ether 00:13:02:3e:d4:ce media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/6Mbps) status: associated ssid kg4 channel 1 bssid 00:0f:66:51:aa:41 authmode WPA privacy ON deftxkey UNDEF TKIP 2:128-bit txpowmax 100 bmiss 7 protmode CTS roaming MANUAL bintval 100 (I actually SSH'ed into the laptop to get this message) The driver only works with acpi disabled (tha fault of the laptop, not the driver - it is the same with the bge driver), and it spits out soem error messages. I'll update the web page with the information. When updated, you can find dmesg output on http://tingox.googlepages.com/aceraspireas5672andfreebsd Let me know if I can test anything else to help. -- Regards, Torfinn Ingolfsen, Norway ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6.2-RC1 /boot/loader | dhclient
Hi list, i just want to note that after updating to RC1 /boot/loader still refuses to boot with Grub. -> endless rebooting chainloading works though, fortunately. dhclient shows a similar behavior to that Steve Franks reported Nov 13 on -CURRENT. After 20 min of inactivity the route gets flushed on my laptop, calling dhclient wi0 from the command line remedies the problem until it gets flushed again. isc-dhclient does not exhibit this behavior, the route never gets flushed. And btw, isc-dhclient seems to be started so early in the boot-process that its pidfile in /var/run gets deleted later during boot. I have not checked if this happens to dhclient as well. regards, --> auge -- 1:15AM up 105 days, 2:19, 0 users, load averages: 0.00, 0.00, 0.00 In my end is my beginning. -- Mary Stuart, Queen of Scots ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.2-RC1 /boot/loader | dhclient
On Mon, Nov 20, 2006 at 01:49:57AM +0100, Norbert Augenstein wrote: > Hi list, > > i just want to note that after updating to RC1 /boot/loader > still refuses to boot with Grub. -> endless rebooting > chainloading works though, fortunately. > > dhclient shows a similar behavior to that Steve Franks reported > Nov 13 on -CURRENT. > After 20 min of inactivity the route gets flushed on my laptop, > calling dhclient wi0 from the command line remedies the problem > until it gets flushed again. > isc-dhclient does not exhibit this behavior, the route never gets > flushed. Linkstate handling is known to be broken in wi(4) which dhclient relies on, you may just have to use isc-dhclient. Andrew ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
