Kernel compile problem?
Hi all, Just wondered if anyone could help me out here, Im trying to cvsup from 4.0-RELEASE to 4.1-STABLE and on a make depend on my kernel I get the following: === agp make: don't know how to make agp_if.c. Stop *** Error code 2 Stop in /usr/src/sys/modules. *** Error code 1 Anyone else getting this error on a build? I last cvsupped at 8:50am GMT+2 Thanks Andrew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Kernel compile problem?
Lists Account wrote: Hi all, Just wondered if anyone could help me out here, Im trying to cvsup from 4.0-RELEASE to 4.1-STABLE and on a make depend on my kernel I get the following: It doesn't work this way. When you cvsup, you need to follow the recipe in /usr/src/UPDATING. There is a section on upgrading from 4.x to 4.1-stable. The safe route is to follow the buildworld, build[install]kernel, installworld sequence. Kent === agp make: don't know how to make agp_if.c. Stop *** Error code 2 Stop in /usr/src/sys/modules. *** Error code 1 Anyone else getting this error on a build? I last cvsupped at 8:50am GMT+2 Thanks Andrew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Kernel compile problem?
In message [EMAIL PROTECTED] Lists Account writes: : Just wondered if anyone could help me out here, Im trying to cvsup from : 4.0-RELEASE to 4.1-STABLE and on a make depend on my kernel I get the : following: : : === agp : make: don't know how to make agp_if.c. Stop : *** Error code 2 : : Stop in /usr/src/sys/modules. : *** Error code 1 : : Anyone else getting this error on a build? Just those people that haven't read UPDATING :-) make buildkernel is your friend... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Kernel compile problem?
Just wondered if anyone could help me out here, Im trying to cvsup from 4.0-RELEASE to 4.1-STABLE and on a make depend on my kernel I get the following: === agp make: don't know how to make agp_if.c. Stop *** Error code 2 Anyone else getting this error on a build? Yup. I've spent the last hour or two banging my head on it. There's a variety of answers on freebsd-questions (http://www.freebsd.org/cgi/search.cgi?words=agp+cvsupmax=25sort=scoresou rce=freebsd-questions). These include " 'make buildkernel' works fine ", "RTFM /usr/src/UPDATING" and "get usr-share as well". None of which work for me. I currently have a really minimal install, so I'm currently installing all the 4.0 sources to do a cvsup with src-all then a make buildkernel (or even a world) to see how it goes. Last time I tried cvsup'ing it was 3.3 to 4.0 and a complete disaster. Had to use the CD's in the end (me=lam3r). Dave BTW, Best directed onto -questions, por favor. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Shared Memory Issues
John Toon wrote: Hi, I've scoured through the net and the mailing archives, but was unable to find any satisfactory information on a certain problem I'm suffering at the moment. After getting the dreaded "shmget() failed" error message, I have since tried several recompiles of the kernel to fix the problem. The same with me. I added options SHMMAXPGS=16385 options SHMMAX=(SHMMAXPGS*PAGE_SIZE+1) to my new kernel and recompiled. I tried this without success. However, under XFree86 4.0, I still seem to be getting shared memory issues. I'm using XFree86 3.3.6 with the server of 3.3.5. The problem is not in XFree, but in imlib. Compupic refuses to start under GNOME issuing X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 146 (MIT-SHM) Minor opcode of failed request: 1 (X_ShmAttach) Serial number of failed request: 2961 Current serial number in output stream: 2962 Yet works under VTWM - until I load up a few applications, when it terminates again, with the same problem. More annoyingly, FXTV also dies with the same problem. Next, I tried another kernel, this time with the following options: options SEMMNI=100 options SEMMNS=300 options SEMUME=100 options SEMMNU=150 options SHMMAXPGS=16385 I omitted the SHMMAX option, as I have read that this option is now deprecated. Unfortunately, this kernel was not better. For me, playing with SHM options made things worse than it was in the default SHM kernel configuration. I'm currently running FreeBSD 4.0-RELEASE. Several questions; 1. If I upgrade to 4.1-STABLE (which I will be soon), will the shared memory issue disappear? I doubt so. I'm running 5.0-CURRENT, and still have the problem. -- * *Konstantin Chuguev - Application Engineer * * Francis House, 112 Hills Road * Cambridge CB2 1PQ, United Kingdom D A N T E WWW:http://www.dante.net To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Shared Memory Issues
I think that there is an application that is not releasing memory resources you can check that with ipcs and ipcsrm cheers At 11:35 AM 9/5/2000 +0100, Konstantin Chuguev wrote: John Toon wrote: Hi, I've scoured through the net and the mailing archives, but was unable to find any satisfactory information on a certain problem I'm suffering at the moment. After getting the dreaded "shmget() failed" error message, I have since tried several recompiles of the kernel to fix the problem. The same with me. I added options SHMMAXPGS=16385 options SHMMAX=(SHMMAXPGS*PAGE_SIZE+1) to my new kernel and recompiled. I tried this without success. However, under XFree86 4.0, I still seem to be getting shared memory issues. I'm using XFree86 3.3.6 with the server of 3.3.5. The problem is not in XFree, but in imlib. Compupic refuses to start under GNOME issuing X Error of failed request: BadAccess (attempt to access private resource denied) Major opcode of failed request: 146 (MIT-SHM) Minor opcode of failed request: 1 (X_ShmAttach) Serial number of failed request: 2961 Current serial number in output stream: 2962 Yet works under VTWM - until I load up a few applications, when it terminates again, with the same problem. More annoyingly, FXTV also dies with the same problem. Next, I tried another kernel, this time with the following options: options SEMMNI=100 options SEMMNS=300 options SEMUME=100 options SEMMNU=150 options SHMMAXPGS=16385 I omitted the SHMMAX option, as I have read that this option is now deprecated. Unfortunately, this kernel was not better. For me, playing with SHM options made things worse than it was in the default SHM kernel configuration. I'm currently running FreeBSD 4.0-RELEASE. Several questions; 1. If I upgrade to 4.1-STABLE (which I will be soon), will the shared memory issue disappear? I doubt so. I'm running 5.0-CURRENT, and still have the problem. -- * *Konstantin Chuguev - Application Engineer * * Francis House, 112 Hills Road * Cambridge CB2 1PQ, United Kingdom D A N T E WWW:http://www.dante.net To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dlopen()
On Mon, Sep 04, 2000 at 11:16:17PM -0500, Michael Owens wrote: [...] -Wl,export-dynamic, but still have not seemed to resolve the problem: when the program calls dlopen to load the library, it returns ./libcircle.so: Undefined symbol "__pure_virtual" It seems that this is a libgcc issue. When linking `testdcl', the linker does not add unneeded symbols from libgcc. Symbols from libgcc needed in libcircle.so or libsquare.so, but unneeded in testdcl won't get resolved. Try linking libgcc to libcircle.so and libsquare.so. Look after how g++ invokes the linker (g++ -v), you may have to call the linker by yourself. This is a dirty hack. The proper solution is to convert libgcc into a shared library. This work is already under way. Björn -- -BEGIN GEEK CODE BLOCK- GCS d--(+) s++: a- C+++(-) UBOSI$ P+++(-) L---(++) !E W- N+ o+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+ --END GEEK CODE BLOCK-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Multiple kernels selector...
This is an adaptation from menuconf.4th: \ Simple greeting screen, presenting basic options. \ XXX This is far too trivial - I don't have time now to think \ XXX about something more fancy... :-/ \ $FreeBSD: /c/ncvs/src/share/examples/bootforth/menuconf.4th,v 1.4 1999/09/29 04:46:01 dcs Exp $ : title ." Welcome to BootFORTH!" cr cr ; : menu ." 1. Start FreeBSD with /boot/stable.conf." cr ." 2. Start FreeBSD with /boot/current.conf." cr ." 3. Start FreeBSD with standard configuration. " cr ." 4. Reboot." cr cr ; : tkey ( d -- flag | char ) seconds + begin 1 while dup seconds u if drop -1 exit then key? if drop key exit then repeat ; : prompt ." Enter your option (1,2,3,4): " 10 tkey dup 32 = if drop key then dup 0 if drop 51 then dup emit cr ; : (reboot) 0 reboot ; : main_menu begin 1 while title menu prompt cr cr dup 49 = if drop ." Loading /boot/stable.conf. Please wait..." cr s" /boot/stable.conf" read-conf 0 boot-conf exit then dup 50 = if drop ." Loading /boot/current.conf. Please wait..." cr s" /boot/current.conf" read-conf 0 boot-conf exit then dup 51 = if drop ." Proceeding with standard boot. Please wait..." cr 0 boot-conf exit then dup 52 = if drop ['] (reboot) catch abort" Error rebooting" then ." Key " emit ." is not a valid option!" cr ." Press any key to continue..." key drop cr repeat ; This reads stable.conf or current.conf depending on option 1 or 2 (or standard boot for option 3), and then boots. You can simplify it in the following way. Replace the lines s" /boot/stable.conf" read-conf 0 boot-conf exit (and similar for current.conf) with the line s" kernel.stable" 1 boot-conf exit and you'll just try to boot the standard configuration using the kernel named kernel.stable. If you need to match modules to kernels, keep both kernel and modules in the same directory, under either root or /boot, for each kernel/modules set. Then, if you want to boot the kernel and modules inside the directory /boot/stable or /stable, for example, you replace the two lines with: s" stable" 1 boot-conf exit You can, of course, add more options easily. And you can mix all of the above options: .conf files names, kernel names and directory names, depending on what option you choose. Put this stuff in a file (asciimenu.4th, for example) and then replace the "start" on loader.rc with the following: s" /boot/asciimenu.4th" fopen dup fload fclose initialize drop main_menu -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] OK, so the solar flares are my fault.. I am sorry, ok?!?! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Need quick help.
I tried to change smth in my interfaces and now receive such message in /var/log/messages /kernel: arp: IP_number is on rl2 but got reply from MAC_ADDRESS an ed1 Please need quick help. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Need quick help.
I tried to change smth in my interfaces and now receive such message in /var/log/messages /kernel: arp: IP_number is on rl2 but got reply from MAC_ADDRESS an ed1 presumably you have bridging enabled ? cheers luigi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Promise PDC20265
Hello, I have Asus A7V motherboard that has integrated UDMA100-controller PDC20265 made by Promise and Maxtor 54098H8 hard disk. When plugged to the UDMA66-controller the Maxtor works properly, boots and is fast. But when plugged to the PDC20265 BIOS detects it, kernel boots but don't detect the controller nor the disk so it complains about root not found. I checked the ata driver (I have 4.1-STABLE by yesterday) and it has support for Promise 100 (I presume it's PDC20265) but it doesn't work ? Any suggestions will be appreciated. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Need quick help.
On Tue, 5 Sep 2000, petro wrote: I tried to change smth in my interfaces and now receive such message in /var/log/messages /kernel: arp: IP_number is on rl2 but got reply from MAC_ADDRESS an ed1 Your networks are broken. It appears the two interfaces are plugged into the same physical network. Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Shared Memory Issues
Clive Lin wrote: Hm... long time ago I asked google about those SHM* and I thought SHMSEG may be the key point. Because SHMSEG stands for maximum number of shared segments per process. Fantastic! You're absolutely correct. Everything is now working perfectly. My mistake had been to think that the system was running out of actual shared memory pages, but successive increases of the maximum pages had no effect. The actual problem, as you've rightly pointed out, was that each process was running out of shared memory segments... Incidentally, how many pages does a segment in FreeBSD correspond to? 4? 16? Ask google ? It's really powerful... I know ;^) Google is considerably better than any other search engine... About the SYSV options, I have small notes about them. Though, I couldn't make sure they are 100% correct. It just works, and I have no more interests to dig more :- SHMALL max shared mem system wide (in pages). SHMMAX max shared memory segment size (bytes). SHMMIN min shared memory segment size (bytes). SHMMNI max num of shared segments system wide. SHMSEG maximum number of shared segments per process. Regards, Clive Just as a side note, are there any commands available that will inform me how many shared memory pages are currently being used by the running system? Thanks. -- :s/Windows/UNIX John Toon | [EMAIL PROTECTED] | "Sonnilon" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
GeForce 6600 driver
Nvidia have released source code for a linux kernel driver and an XFree86 module which provides 3D accelleration via OpenGL. Having just acquired one of these boards, I'm intersted in knowing whether anyone has been interested in porting that driver from Linux to FreeBSD. I believe the XFree86 module should work without modification (include file locations notwithstanding). The kernel module might require a bit of work, though. Has anyone already made any progress on this which I could build on? Or any useful contacts inside Nvidia who could help out? Thanks, - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
FW: GeForce 6600 driver
FYI.. -Original Message- From: Nick Triantos Sent: Tuesday, September 05, 2000 6:20 PM To: Dennis Wong Subject: RE: GeForce 6600 driver Hi Dennis, Actually, we haven't done it yet. However, all of our major Linux dependencies should be in the 3 source files which ship as part of our kernel module's tarball. If those files were ported to BSD, in theory everything else "should" work, though I'm sure we'd need a bit of testing before that became fully true. We do plan to start on a FreeBSD port soon, we just haven't had time yet. However, if there's someone interested in trying to help do this port, we'd be happy to talk to them. They can email me at [EMAIL PROTECTED] BTW, we did also speak with the FreeBSD guys at linuxworld, I think we have a possible way we could check our code into the FreeBSD tree, which would be great once we do get it working well. Feel free to post this, btw. I also really like BSD. -Nick -Original Message- From: Dennis Wong Sent: Tuesday, September 05, 2000 5:28 PM To: Nick Triantos Subject: FW: GeForce 6600 driver ...So, can we help these guys out? I love FreeBSD.. -Original Message- From: Mark Newton [SMTP:[EMAIL PROTECTED]] Sent: Tuesday, September 05, 2000 5:12 PM To: [EMAIL PROTECTED] Subject: GeForce 6600 driver Nvidia have released source code for a linux kernel driver and an XFree86 module which provides 3D accelleration via OpenGL. Having just acquired one of these boards, I'm intersted in knowing whether anyone has been interested in porting that driver from Linux to FreeBSD. I believe the XFree86 module should work without modification (include file locations notwithstanding). The kernel module might require a bit of work, though. Has anyone already made any progress on this which I could build on? Or any useful contacts inside Nvidia who could help out? Thanks, - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
