Helping
installed FreeBSD on VirtualPC but I have a problem with configuring Internet dhpc normally gets the ip address and the address of the router but when I introduce portsnap fetch HQ to download files I do not want to download by failed and when I go back to the configuration of the Internet in sysinstall is a ip address 255.255.255.0 and disappears and it is still several times reinstalled FreeBSD Zainstalowałem freeBSD na VirtualPC ale mam problem z skonfigurowaniem internetu dhpc normalnie pobiera adres ip i adres routera ale gdy wprowadzam Komendę portsnap fetch do pobrania plików nie chce mi pobierać pisze failed i gdy wchodzę znów do konfiguracji internetu w sysinstall to adres ip i 255.255.255.0 znika i to ciągle przeinstalowałem freeBSD kilka razy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
helping
installed FreeBSD on VirtualPC but I have a problem with configuring Internet dhpc normally gets the ip address and the address of the router but when I introduce portsnap fetch HQ to download files I do not want to download by failed and when I go back to the configuration of the Internet in sysinstall is a ip address 255.255.255.0 and disappears and it is still several times reinstalled FreeBSD Zainstalowałem freeBSD na VirtualPC ale mam problem z skonfigurowaniem internetu dhpc normalnie pobiera adres ip i adres routera ale gdy wprowadzam Komendę portsnap fetch do pobrania plików nie chce mi pobierać pisze failed i gdy wchodzę znów do konfiguracji internetu w sysinstall to adres ip i 255.255.255.0 znika i to ciągle przeinstalowałem freeBSD kilka razy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: helping
Kamil Nowacki wrote: installed FreeBSD on VirtualPC but I have a problem with configuring Internet dhpc normally gets the ip address and the address of the router but when I introduce portsnap fetch HQ to download files I do not want to download by failed and when I go back to the configuration of the Internet in sysinstall is a ip address 255.255.255.0 and disappears and it is still several times reinstalled FreeBSD [snip] I do not know anything about VirtualPC, but I have used VirtualBox for some time and if the two are similar enough what works with VBox may also apply, with minor variations. The nominal default install of VirtualBox provides a virtual NAT and DHCP services to the guest OS. The virtual network card that it is simulating needs to be known, so the correct network card driver can be selected. In VirtualBox the default is AMD PCNet FAST III, but one may also select a variant of Intel PRo/1000 as well. This is the NIC that the guest OS will be using. Since the driver (em) is included already in the default FreeBSD kernel a good choice would be the Intel PRO/1000 MT which is simulating an 82540. In any event, you will need to discover the virtual network card being presented to the guest OS. The command dmesg may help. An example based on the above Intel adapter would look like this: In your /etc/rc.conf file place the following: ifconfig_em0=DHCP That is all you need to do. Replace the em part with the driver that corresponds to the driver required for whichever network interface VirtualPC is presenting to the guest OS. For example, a very common Realtek 10/100 might look like: ifconfig_rl0=DHCP - rl is the name of the driver needed for the Realtek 8139-based family of adapters. When you boot the guest, it should initialize the adapter via DHCP. What I do not know is if VirtualPC is providing these NAT and DHCP services to the guest OS in a manner similar to VirtualBox. If it does this info will work. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Helping interpreting crash
Hello cw, Monday, April 3, 2006, 2:09:12 PM, you wrote: c My FreeBSD server (6.0-RELEASE #0) crashed out the other night. I have a c custom kernel in place with debugging on so can get the info out the c dump in /var/crash Try upgrade to 6.1 -- 6.0 have some troubles... c current process = 687 (python) Check python scripts.. -- Best regards, Playnetmailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Helping interpreting crash
Hi folks,
My FreeBSD server (6.0-RELEASE #0) crashed out the other night. I have a
custom kernel in place with debugging on so can get the info out the
dump in /var/crash
Thing is, I'm not sure how to interpret it. I can see all the stuff
about ip and the network but I don't know if it means that is the
culprit and the handbook only goes into how to get the data out of the dump.
So could anyone possibly have a look at below (or tell me of somewhere I
can go to get the right info..bearing in mind I don't know all that much
about the kernel) and let me know what's up?
Thanks,
Colin.
cd /usr/obj/usr/src/sys/IVY
kgdb kernel.debug /var/crash/vmcore.1
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x58
fault code = supervisor write, page not present
instruction pointer = 0x20:0xc0551fcb
stack pointer = 0x28:0xde9fbb18
frame pointer = 0x28:0xde9fbb34
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 687 (python)
trap number = 12
panic: page fault
Uptime: 2d12h7m56s
Dumping 510 MB (2 chunks)
chunk 0: 1MB (160 pages) ... ok
chunk 1: 510MB (130416 pages) 494 478 462 446 430 414 398 382 366 350
334 318 302 286 270 254 238 222 206 190 174 158 142 126 110 94 78 62 46
30 14
#0 doadump () at pcpu.h:165
165 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) list *0xc0551fcb
0xc0551fcb is in ip_ctloutput (/usr/src/sys/netinet/ip_output.c:1208).
1203if (error)
1204break;
1205
1206switch (sopt-sopt_name) {
1207case IP_TOS:
1208inp-inp_ip_tos = optval;
1209break;
1210
1211case IP_TTL:
1212inp-inp_ip_ttl = optval;
(kgdb) backtrace
#0 doadump () at pcpu.h:165
#1 0xc04ccb72 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399
#2 0xc04cce08 in panic (fmt=0xc05fc04b %s)
at /usr/src/sys/kern/kern_shutdown.c:555
#3 0xc05dedb8 in trap_fatal (frame=0xde9fbad8, eva=88)
at /usr/src/sys/i386/i386/trap.c:831
#4 0xc05deb23 in trap_pfault (frame=0xde9fbad8, usermode=0, eva=88)
at /usr/src/sys/i386/i386/trap.c:742
#5 0xc05de781 in trap (frame=
{tf_fs = -1067646968, tf_es = -1024393176, tf_ds = 40, tf_edi =
0, tf_esi = 0, tf_ebp = -559957196, tf_isp = -559957244, tf_ebx =
-559956848, tf_edx = -559956592, tf_ecx = 0, tf_eax = 8, tf_trapno = 12,
tf_err = 2, tf_eip = -1068163125, tf_cs = 32, tf_eflags = 66183, tf_esp
= -559957204, tf_ss = 8})
at /usr/src/sys/i386/i386/trap.c:432
#6 0xc05ce86a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0xc0551fcb in ip_ctloutput (so=0x8, sopt=0xde9fbc90)
at /usr/src/sys/netinet/ip_output.c:1208
#8 0xc056016f in tcp_ctloutput (so=0xc2f376f4, sopt=0xde9fbc90)
at /usr/src/sys/netinet/tcp_usrreq.c:1036
#9 0xc05062c8 in sosetopt (so=0xc2f376f4, sopt=0xde9fbc90)
at /usr/src/sys/kern/uipc_socket.c:1553
#10 0xc050b525 in kern_setsockopt (td=0xc2f1dd80, s=14, level=8, name=8,
val=0xde9fbd90, valseg=UIO_USERSPACE, valsize=0)
at /usr/src/sys/kern/uipc_syscalls.c:1331
#11 0xc050b456 in setsockopt (td=0xc2f1dd80, uap=0x8)
at /usr/src/sys/kern/uipc_syscalls.c:1287
#12 0xc05df0cf in syscall (frame=
{tf_fs = 171507771, tf_es = 174850107, tf_ds = -1078001605,
tf_edi = -1077955292, tf_esi = -1077955284, tf_ebp = -1077955268, tf_isp
= -559956636, tf_ebx = 708242808, tf_edx = 154827904, tf_ecx =
-1077955988, tf_eax = 105, tf_trapno = 0, tf_err = 2, tf_eip =
673615827, tf_cs = 51, tf_eflags = 658, tf_esp = -1077955344, tf_ss =
59}) at /usr/src/sys/i386/i386/trap.c:976
#13 0xc05ce8bf in Xint0x80_syscall () at
/usr/src/sys/i386/i386/exception.s:200
#14 0x0033 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb) p *sopt
$1 = {sopt_dir = SOPT_SET, sopt_level = 0, sopt_name = 3,
sopt_val = 0xbfbfb52c, sopt_valsize = 4, sopt_td = 0xc2f1dd80}
As a sidenote, I recently upgraded sendmail to 8.13.6 using the ports
tree with a few commands I picked out of the web. Whilst it appears that
8.13.6 is still on the server, it has somehow lost its ability to use
sasl2 which was compiled into it as follows:
**Added to Makefile
SENDMAIL_CFLAGS=-I/usr/local/include -DSASL=2
SENDMAIL_LDFLAGS=-L/usr/local/lib
SENDMAIL_LDADD=-lsasl2
SENDMAIL_CF_DIR=/usr/local/share/sendmail/cf
FORCE_PKG_REGISTER=yes
**Also uncommented lines about tls, smtps and sasl2
**Make command
make DESTDIR= PREFIX=/usr PIDDIR=/var/run DESTETC=/etc/mail
DESTEXEC=/usr/libexec DESTRUN=/var/run DESTBIN=/usr/sbin install
As a result I have had to recompile sendmail to get support back. (I'm
aware this probably isn't the best way of upgrading
Re: Cd rom device naming - thanks for helping
Craig Lloyd [EMAIL PROTECTED] writes: -Just an info on something I could found nowhere (searched the device namings section of FreeBSD handbook, books, other forums..etc) I know that IDE ATAPI cdrom drive is acd - acd0 = 1st IDE ATAPI cdrom acd1 = 2nd IDE ATAPI cdrom acd2 = 3rd IDE ATAPI cdrom ..etc My question: why is there mention in FreeBSD manuals and technicals of acd0a, acd0b..etc Why that letter at the end (which normaly designates a partition --but there's no partitions on a Cd rom!!!) OS that I have - FreeBSD 5.1 Historical reasons. Those devices are the ones in use on 4.x. -- Lowell Gilbert, embedded/networking software engineer, Boston area: resume/CV at http://be-well.ilk.org:8088/~lowell/resume/ username/password public ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Cd rom device naming - thanks for helping
-Just an info on something I could found nowhere (searched the device namings section of FreeBSD handbook, books, other forums..etc) I know that IDE ATAPI cdrom drive is acd - acd0 = 1st IDE ATAPI cdrom acd1 = 2nd IDE ATAPI cdrom acd2 = 3rd IDE ATAPI cdrom ..etc My question: why is there mention in FreeBSD manuals and technicals of acd0a, acd0b..etc Why that letter at the end (which normaly designates a partition --but there's no partitions on a Cd rom!!!) OS that I have - FreeBSD 5.1 Craig Lloyd Searching for the best free email? Try MetaCrawler Mail, from the #1 metasearch service on the Web, http://www.metacrawler.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [XFree86] helping setting up dvi connections, Please!
On Thu, 13 Feb 2003, KroNiC~BSD wrote: Has anyone been able to get a geforce 4 dvi output working with xfree86? I want to connect my flat panel to my freebsd 4.7 machine via DVI-D. Thanks in advance. I assume you're refering to the nv driver. You'll need a newer server as the nv driver didn't support DVI in any of the official XFree86 versions. Try one of the 4.2.99.x snapshots on ftp.xfree86.org and put Option FlatPanel in the Section Device of the XF86Config file. Mark. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: helping setting up dvi connections, Please!
On Thu, Feb 13, 2003 at 01:44:53PM -0600, KroNiC~BSD wrote: Has anyone been able to get a geforce 4 dvi output working with xfree86? I want to connect my flat panel to my freebsd 4.7 machine via DVI-D. what is exactly your problem? works like a charm for me. i am using an aopen ti4200 card with two ibm t84h screens attached to it. one uses the dvi connecter the other the normal one. find attached my XFree86 config. i am using the commerical nvidia geforce driver. toni -- Terror ist der Krieg der Armen, | [EMAIL PROTECTED] Krieg ist der Terror der Reichen. | Toni Schmidbauer - Sir Peter Ustinov | Section ServerLayout Identifier pinhead Screen Screen0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files RgbPath /usr/X11R6/lib/X11/rgb ModulePath /usr/X11R6/lib/modules FontPath /usr/X11R6/lib/X11/fonts/misc/ FontPath /usr/X11R6/lib/X11/fonts/CID/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/100dpi/ EndSection Section Module Load extmod Load pex5 Load glx Load dbe Load record Load type1 EndSection Section ServerFlags # Option Xinerama Option StandbyTime 10 Option SuspendTime 20 Option OffTime off EndSection Section InputDevice Identifier Keyboard0 Driver keyboard Option XkbModel pc105 Option XkbLayout de EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/mouse Option ZAxisMapping 4 5 Option Buttons 3 Option SampleRate 150 Option Emulate3Buttons EndSection Section Monitor Identifier Monitor0 VendorName ibm ModelNamet84h HorizSync31.0 - 81.0 VertRefresh 55.0 - 85.0 Option DPMS EndSection Section Monitor Identifier Monitor1 VendorName ibm ModelNamet84h HorizSync31.0 - 81.0 VertRefresh 55.0 - 85.0 Option DPMS EndSection Section Device Identifier Card0 Driver nvidia VendorName NVIDIA BoardName GeForce TI4200 Option DigitalScreen yes EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultDepth 16 Option TwinView Option SecondMonitorHorizSync 31.0 - 81.0 Option SecondMonitorVertRefresh 55.0 - 85.0 Option MetaModes 1280x1024,1280x1024 Option TwinViewOrientation RightOf SubSection Display Depth 1 EndSubSection SubSection Display Depth 4 EndSubSection SubSection Display Depth 8 Modes1280x1024 EndSubSection SubSection Display Depth 15 EndSubSection SubSection Display Depth 16 Modes1280x1024 EndSubSection SubSection Display Depth 24 Modes1280x1024 EndSubSection EndSection msg19322/pgp0.pgp Description: PGP signature
helping setting up dvi connections, Please!
Has anyone been able to get a geforce 4 dvi output working with xfree86? I want to connect my flat panel to my freebsd 4.7 machine via DVI-D. Thanks in advance. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Need helping lengthening timeouts for sendmail...
Hi all - Two weeks ago nwlink.com upgraded it's mail servers. Ever since that time I can not email anyone whose email is handled by those servers. What's even more frustrating is that my home server, same setup, same DSL (through nwlink.com even), but on a different subnet cause it's in a different city, has no problems whatsoever. The messages I get back from processing the queue manually with a lot of debugging are: Running /var/spool/mqueue/h0THo5Sc018988 (sequence 2 of 11) dowork(/var/spool/mqueue/h0THo5Sc018988) [EMAIL PROTECTED]... Connecting to mx1.pacifier.net. via esmtp... [EMAIL PROTECTED]... Connecting to mx3.pacifier.net. via esmtp... [EMAIL PROTECTED]... Connecting to mx2.pacifier.net. via esmtp... [EMAIL PROTECTED]... Connecting to mx4.pacifier.net. via esmtp... If I telnet to those IP's above on port 25, it does take about 60-90 seconds to connect, but it does connect. I've fiddled with the various Timeout paramaters in my sendmail.cf and submit.cf, but without any luck. I'm running sendmail 8.12.3 on FreeBSD 4.5-stable. I've gone round and round with them (for two weeks now) and they agree there's something wrong, and are now looking into their network issues, but in the meantime, I need help getting mail to send? So... is there anyway to get sendmail to just wait and wait and wait for that connection to appear? Or is there an easy way to tell it that intead of trying mx#.pacifier.net to use smtp.nwlink.com instead? Thanks folks... this is driving me nuts. -philip To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Need helping lengthening timeouts for sendmail...
I found a temporary hack that solves my most immediate problem of sending mail to @nwlink.com addresses by adding the following to /etc/mail/mailertable nwlink.com smtp:[smtp.nwlink.com] Of course any other domains hosted at nwlink.com still fail, but this will get me by till they fix it. What would be really cool is if I could add: mx:mx1.pacifier.net smtp:[smtp.nwlink.com] and have it redirect all mail that would have gone to mx1.pacifier.net to smtp.nwlink.com :-) -philip On Wed, 29 Jan 2003, Philip Hallstrom wrote: Hi all - Two weeks ago nwlink.com upgraded it's mail servers. Ever since that time I can not email anyone whose email is handled by those servers. What's even more frustrating is that my home server, same setup, same DSL (through nwlink.com even), but on a different subnet cause it's in a different city, has no problems whatsoever. The messages I get back from processing the queue manually with a lot of debugging are: Running /var/spool/mqueue/h0THo5Sc018988 (sequence 2 of 11) dowork(/var/spool/mqueue/h0THo5Sc018988) [EMAIL PROTECTED]... Connecting to mx1.pacifier.net. via esmtp... [EMAIL PROTECTED]... Connecting to mx3.pacifier.net. via esmtp... [EMAIL PROTECTED]... Connecting to mx2.pacifier.net. via esmtp... [EMAIL PROTECTED]... Connecting to mx4.pacifier.net. via esmtp... If I telnet to those IP's above on port 25, it does take about 60-90 seconds to connect, but it does connect. I've fiddled with the various Timeout paramaters in my sendmail.cf and submit.cf, but without any luck. I'm running sendmail 8.12.3 on FreeBSD 4.5-stable. I've gone round and round with them (for two weeks now) and they agree there's something wrong, and are now looking into their network issues, but in the meantime, I need help getting mail to send? So... is there anyway to get sendmail to just wait and wait and wait for that connection to appear? Or is there an easy way to tell it that intead of trying mx#.pacifier.net to use smtp.nwlink.com instead? Thanks folks... this is driving me nuts. -philip To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
