hi, i found strange problem with working ssh on server: gr login failures: Jan 4 08:21:57 gr sshd[16218]: Received disconnect from 193.125.78.113: 2: Bad packet length 1626711409. Jan 4 08:35:37 gr sshd[16254]: Received disconnect from 77.123.194.155: 2: Bad packet length 236618258. what is it and what should i fix? FreeBSD gr.holydns.com 7.0-BETA4 FreeBSD 7.0-BETA4 #0: Wed Dec 5 01:12:18 UTC 2007 dexx@gr:/usr/obj/usr/src/sys/GR amd64 -- *#) _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Hello all, I downloaded, burnt and installed 7.0-RC1 (all torrent) on amd64 I downloaded the dell windows drivers for my laptop wireless card (which worked on i3686 6.2-RELEASE) and used ndisgen to create the .ko file (bcmwl5_sys.ko) and loaded it and then realised I had created the 32 bit driver so I re-did it and used the 64 bit file and loaded the 64bit .ko and at that point my laptop (Dell Vostro 1000) hung. I had put bcmwl5_sys_load="YES" in the loader.conf file I rebooted and now I don't get anything. As soon as it starts to boot it stops. There is a screen showing kernel dump info and I can copy it if needed but I have to burn the rescue iso otherwise I cant boot. Is this a known problem ? Does anyone have any advice ? Darran http://www.deejc.net _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
If you have bcmwl5_sys_load in your loader.conf, this is causing the 32bit driver to load at boot, bcmwl563_sys_load needs to be placed in loader.conf for the 64 bit driver. To boot your system without the rescue CD, at the boot menu choose "Escape to loader prompt". Then use "unload" to unload all modules, and "unset bcmwl5_sys" to disable loading of the bcmwl5_sys module. Finally, use "boot" to continue booting. When the system has finished booting, check /boot/loader.conf, does it have bcmwl5_sys_load or bcmwl564_sys_load? Also check that you placed the 64bit driver in your module path, and removed the 32bit driver from the module path. Scot _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Hi Scot, Thanks for your advice, unfortunately it didn't work as I had the 64 bit driver and it appears that it causes major problems and so I rebuilt it. Now I have a completely different problem, I have done make buildworld and it appeared to build ok (this is a fresh install) I edited my /usr/src/sys/amd64/KERNELCONF and called it MYKERNEL and setup a link from my root folder, I did make buildkernel from usr/src and it failed with : MAKE=make sh /usr/src/sys/conf/newvers.sh GENERIC cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=athlon64 -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror vers.c linking kernel.debug uipc_syscalls.o(.text+0x3e1): In function `sctp_generic_recvmsg': /usr/src/sys/kern/uipc_syscalls.c:2600: undefined reference to `sctp_sorecvmsg' uipc_syscalls.o(.text+0x22ad): In function `sctp_generic_sendmsg_iov': /usr/src/sys/kern/uipc_syscalls.c:2478: undefined reference to `sctp_lower_sosend' uipc_syscalls.o(.text+0x2599): In function `sctp_generic_sendmsg': /usr/src/sys/kern/uipc_syscalls.c:2371: undefined reference to `sctp_lower_sosend' uipc_syscalls.o(.text+0x271f): In function `sctp_peeloff': /usr/src/sys/kern/uipc_syscalls.c:2238: undefined reference to `sctp_can_peel_off' uipc_syscalls.o(.text+0x28e4):/usr/src/sys/kern/uipc_syscalls.c:2279: undefined reference to `sctp_do_peeloff' rtsock.o(.text+0xc36): In function `rt_newaddrmsg': /usr/src/sys/net/rtsock.c:897: undefined reference to `sctp_addr_change' in_proto.o(.data+0x150): undefined ...
options INET # InterNETworking #options INET6 # IPv6 communications protocols options SCTP # Stream Control Transmission Protocol Here is the error in your kernel config file. The SCTP option requires both INET and INET6. Scot _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Thanks very much again Scot, i rebuilt it this morning including the INET6 option and it worked. Darran http://www.deejc.net _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
"Scot Hetzel" <swhetzel@gmail.com> wrote: Scot, I forgot to add that i checked the handbook (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html) before i edited my config and i did not see an entry relating to SCTP and its dependants. Is this something missing on purpose (ie: it MUST stay in all configs) or is it a new addition to the config ? thanks again Darran http://www.deejc.net _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Which driver did you down load from Dell? I tried Dell's R151519.EXE XP Driver (http://ftp.us.dell.com/network/R151519.EXE) Created bcmwl564_sys.ko module from this windows driver, disabled the HP bcmwl564_sys.ko driver from loading. Rebooted the system, and when I load the Dell bcmwl564)sys.ko driver the following panic occurs: hp010# kgdb -n 11 kernel.debug [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd". Ready to go. Enter 'tr' to connect to the remote target with /dev/cuad0, 'tr /dev/cuad1' to connect to a different port or 'trf portno' to connect to the remote target with the firewire interface. portno defaults to 5556. Type 'getsyms' after connection to load kld symbols. If you're debugging a local system, you can use 'kldsyms' instead to load the kld symbols. That's a less obnoxious interface. During symbol reading...location expression too complex... During symbol reading, unsupported tag: 'DW_TAG_const_type'. Unread portion of the kernel message buffer: ndis0: <Dell TrueMobile 1300 WLAN Mini-PCI Card> mem 0xc0204000-0xc0205fff irq 21 at device 2.0 on pci6 ndis0: [ITHREAD] ndis0: NDIS API version: 5.1 fpudna in kernel mode! Kernel page fault with the following non-sleepable locks held: exclusive sleep mutex HAL preemption lock (HAL lock) r = 0 (0xffffffffd64bff20) locked @ /usr/src/8x/sys-orig/modules/ndis/../../compat/ndis/subr_hal.c:423 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a witness_warn() at witness_warn+0x248 trap() at trap+0x25e calltrap() at ...
Hi Scott, This is almost exactly the same as i am getting, I will follow your instructions later about the debug but i did use the same driver and it panics with the same sort of message. i think mine might be a dell 1390 card i cant be certain but its almost the same error Darran http://www.deejc.net _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
I also get the same panic when I use the same driver from HP's web site. ftp://ftp.hp.com/pub/softpaq/sp34001-34500/sp34152.exe The version of the failing driver SP34152 (HP) and R151519 (Dell) is 4.100.15.5 (md5 checksum of bcmwl564.sys is the same). I use version 4.40.19.0 available from HP at: ftp://ftp.hp.com/pub/softpaq/sp33001-33500/sp33008.exe This version should also work on your Dell system. Scot _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Thanks Scot I tried this one and I still don't get any connection showing when I look in ifconfig -a I ran ndisgen and bcmwl5.inf and bcmwl564.sys which created bcmwl564_sys.ko, I kldload'ed it and nothing .. even in the message's I don't see the usual Dell entry when the driver loads. Darran http://www.deejc.net -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Scot Hetzel Sent: 10 January 2008 13:59 To: Darran Cc: freebsd-current@freebsd.org Subject: Re: Hung laptop now will not boot 7.0-RC1 I also get the same panic when I use the same driver from HP's web site. ftp://ftp.hp.com/pub/softpaq/sp34001-34500/sp34152.exe The version of the failing driver SP34152 (HP) and R151519 (Dell) is 4.100.15.5 (md5 checksum of bcmwl564.sys is the same). I use version 4.40.19.0 available from HP at: ftp://ftp.hp.com/pub/softpaq/sp33001-33500/sp33008.exe This version should also work on your Dell system. Scot _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Do you have an entry similar to this in your dmesg? ndis0: <Broadcom 802.11b/g WLAN> mem 0xc0204000-0xc0205fff irq 21 at device 2.0 on pci6 Scot _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
hi scot, i do not have this entry, i got it on 6.2 when i used ndis but i dont get it now when i load the driver created from the link you gave me ? Darran http://www.deejc.net
Hey Scott, I rebuilt the laptop (using the same disks)and it worked this time. The only issue I see is that the ifconfig part does not list my router as connected there is just a pair of "" there and not my ssid When it boots the link comes up, dhclient starts then the link goes down and the dhclient runs 3 times then the link comes back up So in effect it is working Darran http://www.deejc.net -----Original Message----- From: Scot Hetzel [mailto:swhetzel@gmail.com] Sent: 10 January 2008 22:08 To: Darran Cc: freebsd-current@freebsd.org Subject: Re: Hung laptop now will not boot 7.0-RC1 Do you have an entry similar to this in your dmesg? ndis0: <Broadcom 802.11b/g WLAN> mem 0xc0204000-0xc0205fff irq 21 at device 2.0 on pci6 Scot
