Re: 8.2-PRERELEASE?
On 20/02/2011 03:05, Frank Shute wrote: Just keep following RELENG_8 and once the 8.2-RELEASE is done it will become 8.3-STABLE. Well, yes. But not for something like 4 months until the process for releasing 8.3 has happened. Most of the time between now and then, it will appear as 8.2-STABLE Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
8.2-PRERELEASE?
Hello list, yesterday (Feb, 17th) I performed a cvsup (using csup, infact) of my /usr/src tree using *default release=cvs tag=RELENG_8 in my csup file (based on the csup file /usr/share/examples/cvsup/stable-supfile). According to [1], RELENG_8_2 and RELENG_8_2_0_RELEASE were created before, however, running uname ony machine after building world reports FreeBSD 8.2-PRERELEASE. I expect it not to show 8.2-PRERELEASE but something newer (maybe 8.3-PRERELEASE?) Is uname reporting that I'm stick in some old bits? If so, how can I move to the newer 8.x bits? If not, when does the version change? Thank you! [1] http://wiki.freebsd.org/Releng/8.2TODO -- _ Fry: You can see how I lived before I met you. Bender: You lived before you met me?! Fry: Yeah, lots of people did. Bender: Really?! ___ 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: 8.2-PRERELEASE?
On Sat, Feb 19, 2011 at 04:04:19PM +0100, Harald Servat wrote: Hello list, yesterday (Feb, 17th) I performed a cvsup (using csup, infact) of my /usr/src tree using *default release=cvs tag=RELENG_8 in my csup file (based on the csup file /usr/share/examples/cvsup/stable-supfile). According to [1], RELENG_8_2 and RELENG_8_2_0_RELEASE were created before, however, running uname ony machine after building world reports FreeBSD 8.2-PRERELEASE. I expect it not to show 8.2-PRERELEASE but something newer (maybe 8.3-PRERELEASE?) Is uname reporting that I'm stick in some old bits? If so, how can I move to the newer 8.x bits? If not, when does the version change? Thank you! [1] http://wiki.freebsd.org/Releng/8.2TODO -- Just keep following RELENG_8 and once the 8.2-RELEASE is done it will become 8.3-STABLE. If you want the release (+ fixes) then you should change your tag to RELENG_8_2 and in a few days you will get the release once it's done. You probably want the second option above if you're a fairly normal user. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html pgpno2i1lruwT.pgp Description: PGP signature
Re: 8.2 prerelease, virtualbox, and windows guests that freeze...
On 02/06/2011 21:44, Rob Farmer wrote: On Sun, Feb 6, 2011 at 7:03 PM, Chris Brennan xa...@xaerolimit.net wrote: Net, I've formatted drives as fat32 that were well over 4gb. In fact I have an external 120gb we datavault that's fat32 Max per file, not the whole partition. Virtual machines generally store the whole disk as a single file, though Vmware has an option to split it up for these situations. Correct. not an option here. -- Regards, Eric signature.asc Description: OpenPGP digital signature
Re: 8.2 prerelease, virtualbox, and windows guests that freeze...
On 02/06/2011 22:02, Adam Vande More wrote: On Sun, Feb 6, 2011 at 9:23 PM, Eric Schuele e.schu...@computer.org wrote: Ok... found the logs. :) Looks as if each machine has 4 log files, and that the set of files is from the last run. Anything in there I could post to help diagnose? Let's see what's in the most recent log of an affected VM. If you have any funky options like page fusion enabled disable them. After looking in the logs I found an error. :) AIOMgr: Error happened This led me to an open issues in VirtualBox's bug tracker. The proposed work around is to either *enable* th Use Host I/O cache on your virtualized SATA disks, or just use virtualized IDE disks. I am testing this now. Will let you know how it turns out. What the output of gstat(8) and top(1) look like when you reach this degraded state? -- Regards, Eric signature.asc Description: OpenPGP digital signature
Re: 8.2 prerelease, virtualbox, and windows guests that freeze... [Solved]
On 02/07/2011 05:58, Eric Schuele wrote: On 02/06/2011 22:02, Adam Vande More wrote: On Sun, Feb 6, 2011 at 9:23 PM, Eric Schuele e.schu...@computer.org wrote: Ok... found the logs. :) Looks as if each machine has 4 log files, and that the set of files is from the last run. Anything in there I could post to help diagnose? Let's see what's in the most recent log of an affected VM. If you have any funky options like page fusion enabled disable them. After looking in the logs I found an error. :) AIOMgr: Error happened This led me to an open issues in VirtualBox's bug tracker. The proposed work around is to either *enable* th Use Host I/O cache on your virtualized SATA disks, or just use virtualized IDE disks. I am testing this now. Will let you know how it turns out. Thanks guys! I've had my VMs running longer this evening than before. I'm gonna call this one fixed. For the archives, here is the VirtualBox bug report I was referring to that mentions the host I/O cache. http://www.virtualbox.org/ticket/7363 Thanks. What the output of gstat(8) and top(1) look like when you reach this degraded state? -- Regards, Eric signature.asc Description: OpenPGP digital signature
Re: 8.2 prerelease, virtualbox, and windows guests that freeze...
On Saturday 05 February 2011 22:12:45 Eric Schuele wrote: All, I have a laptop running 8.2-prerelease GENERIC. I have virtualbox ose 3.2.12 from ports (and kmod as well). I've only installed windows guests in vbox. I've installed windows 2008 server 64, windows vista 64bit, and windows 7 32bit. I have the vbox hdd images on an NTFS filesystem mounted using fuse. My box is a dual boot machine between FreeBSD and Windows. My desire is to be able to utilize the same virtual machine in vbox on both my Windows and FreeBSD installations. I can successfully utilize the virtuals in vbox (same version) in Windows. However when I utilize any of the virtual machines in FreeBSD, they run for several minutes and eventually freeze. Freeze may not necessarily be the correct term. All windows processes on the virtual machine begin to die. First one process, then another, then all. Hard to explain, which may not help my cause here. But, most important fact... in Windows they work fine... under FreeBSD they run for a while and then cease to run. When the VM is good and dead, it is always dead with the little vbox virtual hard disk LED lit up (no idea if that is important). Previously, they would run for a *very* short time. seconds? minutes? and then die (sometimes I couldn't login). I disabled sound support and now they run for 10-15 minutes. Had one run for an hour or two the other day, but can't reproduce that. Usually 10-15 minutes max. Network works fine inside the virtual. I'm new to VirtualBox on FreeBSD. I've used it a bit on Windows with good results. I did try a windows guest on a non fuse filesystem just to rule that out, but had same issue. What else could I provide that might allow someone to point me in the right direction here? Thanks. -- Regards, Eric Eric; My advice to you is that you change the file system on drive that holds the VMs files from NTFS to EXT2. NTFS file systems on FreeBSD or even Linux are OK only for doing small r/w stuff. I use the ntfs-3g which is really good but don't trust NTFS for heavy usage under those OSs. Sometimes it's not even trustable under windows itself. EXT on the other hand, is very stable in FreeBSD and has very good drivers for any version of 32/64 windows (Ext2IFS_1_11a) so you can access you vdi files. hope this helps. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE) ___ 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: 8.2 prerelease, virtualbox, and windows guests that freeze...
On 02/06/2011 09:23, Mario Lobo wrote: On Saturday 05 February 2011 22:12:45 Eric Schuele wrote: All, I have a laptop running 8.2-prerelease GENERIC. I have virtualbox ose 3.2.12 from ports (and kmod as well). I've only installed windows guests in vbox. I've installed windows 2008 server 64, windows vista 64bit, and windows 7 32bit. I have the vbox hdd images on an NTFS filesystem mounted using fuse. snip Eric; My advice to you is that you change the file system on drive that holds the VMs files from NTFS to EXT2. Thanks for the suggestion, however, I've already tried this (sorta). From my original post... I did try a windows guest on a non fuse filesystem just to rule that out, but had same issue. I suppose it may have been a little less than clear. By non fuse filesystem I actually meant UFS. The problem still persisted. NTFS file systems on FreeBSD or even Linux are OK only for doing small r/w stuff. I use the ntfs-3g which is really good but don't trust NTFS for heavy usage under those OSs. Sometimes it's not even trustable under windows itself. I realize NTFS on fBSD has been shaky in the past, but had heard it had come a long way these days. It does seem to work well for all my purposes, except these VMs. Had hoped NTFS was not the issue. EXT on the other hand, is very stable in FreeBSD and has very good drivers for any version of 32/64 windows (Ext2IFS_1_11a) so you can access you vdi files. I've not tried the EXT IFS for windows yet, nor had I heard much regarding their success or failure. If your willing to go out on a limb and say very good drivers for any version of 32/64 windows... I'll give it a try, and post my results. :) Thanks. hope this helps. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE) -- Regards, Eric signature.asc Description: OpenPGP digital signature
Re: 8.2 prerelease, virtualbox, and windows guests that freeze...
On Sat, Feb 5, 2011 at 7:12 PM, Eric Schuele e.schu...@computer.org wrote: What else could I provide that might allow someone to point me in the right direction here? You can try recompiling virtualbox with debug options and see if it spits out any pertinent messages. I have no problems with Windows guests on VDI, ZVOL, raw file, or raw partitions. Vbox also logs data per VM, you can check that. Another possibility is that you have mismatched versions of guest additions. If that were the problem, it would show up in the Vbox logs. -- Adam Vande More ___ 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: 8.2 prerelease, virtualbox, and windows guests that freeze...
On Sun, Feb 6, 2011 at 11:09 AM, Eric Schuele e.schu...@computer.orgwrote: I realize NTFS on fBSD has been shaky in the past, but had heard it had come a long way these days. It does seem to work well for all my purposes, except these VMs. Had hoped NTFS was not the issue. ntfs/ntfs-3g is foolhardy at best in linux *and* fbsd ... it's trashed so many drives.partitions on me it's not even funny anymore... and I never did much w/ them except small stuff anyway. If you need to access the volumes in *nix/windows then why not FAT32 then? I use a FAT32 drive for my music so I can access it in any OS reliably and the drive is now 6+ years old. ___ 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: 8.2 prerelease, virtualbox, and windows guests that freeze...
On Sunday 06 February 2011 13:09:47 Eric Schuele wrote: Thanks for the suggestion, however, I've already tried this (sorta). From my original post... I did try a windows guest on a non fuse filesystem just to rule that out, but had same issue. I suppose it may have been a little less than clear. By non fuse filesystem I actually meant UFS. The problem still persisted. NTFS file systems on FreeBSD or even Linux are OK only for doing small r/w stuff. I use the ntfs-3g which is really good but don't trust NTFS for heavy usage under those OSs. Sometimes it's not even trustable under windows itself. My bad!. Sorry!. But it seems that you're right. Looks like the issue is not the FS then. If you're building from the ports, try the svn version from: https://svn.bluelife.at/index.cgi/blueports It's already version 4.0.2 there. I realize NTFS on fBSD has been shaky in the past, but had heard it had come a long way these days. It does seem to work well for all my purposes, except these VMs. Had hoped NTFS was not the issue. I've not tried the EXT IFS for windows yet, nor had I heard much regarding their success or failure. If your willing to go out on a limb and say very good drivers for any version of 32/64 windows... I'll give it a try, and post my results. :) Forgive me if it sounded on a limb. Didn't mean to look like that. The only reason I mentioned it is because it's exactly the way I've been using. I have triple boot system. BSD AMD64, XP32 and Win7 64 and the IFS driver works flawlessly on both windows, and all 3 Vboxes accessing the same VDIs. Because of that, I believe I may have got carried away by saying any win version. regards, -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE) ___ 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: 8.2 prerelease, virtualbox, and windows guests that freeze...
On Sunday 06 February 2011 17:48:45 Chris Brennan wrote: On Sun, Feb 6, 2011 at 11:09 AM, Eric Schuele e.schu...@computer.orgwrote: I realize NTFS on fBSD has been shaky in the past, but had heard it had come a long way these days. It does seem to work well for all my purposes, except these VMs. Had hoped NTFS was not the issue. ntfs/ntfs-3g is foolhardy at best in linux *and* fbsd ... it's trashed so many drives.partitions on me it's not even funny anymore... and I never did much w/ them except small stuff anyway. If you need to access the volumes in *nix/windows then why not FAT32 then? I use a FAT32 drive for my music so I can access it in any OS reliably and the drive is now 6+ years old. FAT32 max file size is 4Gig. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE) ___ 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: 8.2 prerelease, virtualbox, and windows guests that freeze...
Net, I've formatted drives as fat32 that were well over 4gb. In fact I have an external 120gb we datavault that's fat32 -- Sent from my Droid On Feb 6, 2011 5:25 PM, Mario Lobo l...@bsd.com.br wrote: On Sunday 06 February 2011 17:48:45 Chris Brennan wrote: On Sun, Feb 6, 2011 at 11:09 AM, Eric Schuele e.schu...@computer.org wrote: I realize NTFS on fBSD has been shaky in the past, but had heard it had come a long way these days. It does seem to work well for all my purposes, except these VMs. Had hoped NTFS was not the issue. ntfs/ntfs-3g is foolhardy at best in linux *and* fbsd ... it's trashed so many drives.partitions on me it's not even funny anymore... and I never did much w/ them except small stuff anyway. If you need to access the volumes in *nix/windows then why not FAT32 then? I use a FAT32 drive for my music so I can access it in any OS reliably and the drive is now 6+ years old. FAT32 max file size is 4Gig. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE) ___ 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: 8.2 prerelease, virtualbox, and windows guests that freeze...
On 02/06/2011 11:35, Adam Vande More wrote: On Sat, Feb 5, 2011 at 7:12 PM, Eric Schuele e.schu...@computer.org wrote: What else could I provide that might allow someone to point me in the right direction here? You can try recompiling virtualbox with debug options and see if it spits out any pertinent messages. I have no problems with Windows guests on VDI, ZVOL, raw file, or raw partitions. Vbox also logs data per VM, you can check that. Logs might be nice. Where would I find these. Or are they only present with debug builds (which I am building now) Another possibility is that you have mismatched versions of guest additions. If that were the problem, it would show up in the Vbox logs. I thought of that... even though vbox does not complain of a mismatch, I went ahead and removed them from a machine and added them back in from my FreeBSD host. No improvement unfortunately. -- Regards, Eric signature.asc Description: OpenPGP digital signature
Re: 8.2 prerelease, virtualbox, and windows guests that freeze...
On 02/06/2011 21:17, Eric Schuele wrote: On 02/06/2011 11:35, Adam Vande More wrote: On Sat, Feb 5, 2011 at 7:12 PM, Eric Schuele e.schu...@computer.org wrote: What else could I provide that might allow someone to point me in the right direction here? You can try recompiling virtualbox with debug options and see if it spits out any pertinent messages. I have no problems with Windows guests on VDI, ZVOL, raw file, or raw partitions. Vbox also logs data per VM, you can check that. Logs might be nice. Where would I find these. Or are they only present with debug builds (which I am building now) Ok... found the logs. :) Looks as if each machine has 4 log files, and that the set of files is from the last run. Anything in there I could post to help diagnose? Another possibility is that you have mismatched versions of guest additions. If that were the problem, it would show up in the Vbox logs. I thought of that... even though vbox does not complain of a mismatch, I went ahead and removed them from a machine and added them back in from my FreeBSD host. No improvement unfortunately. -- Regards, Eric signature.asc Description: OpenPGP digital signature
Re: 8.2 prerelease, virtualbox, and windows guests that freeze...
On Sun, Feb 6, 2011 at 7:03 PM, Chris Brennan xa...@xaerolimit.net wrote: Net, I've formatted drives as fat32 that were well over 4gb. In fact I have an external 120gb we datavault that's fat32 Max per file, not the whole partition. Virtual machines generally store the whole disk as a single file, though Vmware has an option to split it up for these situations. -- Rob Farmer ___ 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: 8.2 prerelease, virtualbox, and windows guests that freeze...
On Sun, Feb 6, 2011 at 9:23 PM, Eric Schuele e.schu...@computer.org wrote: Ok... found the logs. :) Looks as if each machine has 4 log files, and that the set of files is from the last run. Anything in there I could post to help diagnose? Let's see what's in the most recent log of an affected VM. If you have any funky options like page fusion enabled disable them. What the output of gstat(8) and top(1) look like when you reach this degraded state? -- Adam Vande More ___ 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
8.2 prerelease, virtualbox, and windows guests that freeze...
All, I have a laptop running 8.2-prerelease GENERIC. I have virtualbox ose 3.2.12 from ports (and kmod as well). I've only installed windows guests in vbox. I've installed windows 2008 server 64, windows vista 64bit, and windows 7 32bit. I have the vbox hdd images on an NTFS filesystem mounted using fuse. My box is a dual boot machine between FreeBSD and Windows. My desire is to be able to utilize the same virtual machine in vbox on both my Windows and FreeBSD installations. I can successfully utilize the virtuals in vbox (same version) in Windows. However when I utilize any of the virtual machines in FreeBSD, they run for several minutes and eventually freeze. Freeze may not necessarily be the correct term. All windows processes on the virtual machine begin to die. First one process, then another, then all. Hard to explain, which may not help my cause here. But, most important fact... in Windows they work fine... under FreeBSD they run for a while and then cease to run. When the VM is good and dead, it is always dead with the little vbox virtual hard disk LED lit up (no idea if that is important). Previously, they would run for a *very* short time. seconds? minutes? and then die (sometimes I couldn't login). I disabled sound support and now they run for 10-15 minutes. Had one run for an hour or two the other day, but can't reproduce that. Usually 10-15 minutes max. Network works fine inside the virtual. I'm new to VirtualBox on FreeBSD. I've used it a bit on Windows with good results. I did try a windows guest on a non fuse filesystem just to rule that out, but had same issue. What else could I provide that might allow someone to point me in the right direction here? Thanks. -- Regards, Eric signature.asc Description: OpenPGP digital signature
Re: Problem building GIMP 2.6.11 on 8.2-PRERELEASE
According to Warren Block wbl...@wonkity.com on Thu, 01/27/11 at 16:41: Which is the correct port to install this poppler-cairo file? poppler-0.14.5 Be sure to clean it before rebuilding and installing. Thanks for the reply. I did a make deinstall in /usr/ports/graphics/poppler and it claimed an include directory was not able to be deleted. I deleted this directory by hand - something about the packing list being incorrect or something. Then I did a make clean in the same graphics/poppler directory. I followed this with a make install and when that completed with success, I issued this: # ls -l /usr/local/libdata/pkgconfig/poppler-cairo.pc ls: /usr/local/libdata/pkgconfig/poppler-cairo.pc: No such file or directory This from the Makefile therein: PORTNAME= poppler PORTVERSION=0.14.5 PORTREVISION?= 0 So something is clearly wrong here. The /var/db/ports/poppler/OPTIONS file had: WITHOUT_CAIRO=yes inside, so I changed that to WITH_CAIRO=yes and repeated the above steps. The file /usr/local/libdata/pkgconfig/poppler-cairo.pc is now there! However, I still get this error when I attempt to rebuild the Gimp using make clean and make install inside /usr/ports/graphics/gimp: cc -DHAVE_CONFIG_H -I. -I../.. -I../.. -D_THREAD_SAFE -D_REENTRANT -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/pango-1.0 -I/usr/local/include/gio-unix-2.0/ -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -DGIMP_DISABLE_DEPRECATED -DGDK_MULTIHEAD_SAFE -DGTK_MULTIHEAD_SAFE -D_THREAD_SAFE -D_REENTRANT -I/usr/local/include/poppler/glib -I/usr/local/include/poppler -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/cairo -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/pixman-1 -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/local/include/pango-1.0 -I/usr/local/include/gio-unix-2.0/ -O2 -fno-strict-aliasing -pipe -Wall -Wdeclaration-after-statement -Wmissing-prototypes -Wmissing-declarations -Winit-self -Wpointer-arith -Wold-style-definition -MT file_pdf-file-pdf.o -MD -MP -MF .deps/file_pdf-file-pdf.Tpo -c -o file_pdf-file-pdf.o `test -f 'file-pdf.c' || echo './'`file-pdf.c file-pdf.c:30:21: error: poppler.h: No such file or directory file-pdf.c:70: error: expected ')' before '*' token file-pdf.c:77: error: expected ')' before '*' token file-pdf.c:80: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token file-pdf.c:83: error: expected ')' before '*' token file-pdf.c: In function 'run': file-pdf.c:330: error: 'PopplerDocument' undeclared (first use in this function) file-pdf.c:330: error: (Each undeclared identifier is reported only once file-pdf.c:330: error: for each function it appears in.) file-pdf.c:330: error: 'doc' undeclared (first use in this function) file-pdf.c:331: warning: ISO C90 forbids mixed declarations and code file-pdf.c:356: warning: implicit declaration of function 'open_document' file-pdf.c:364: warning: implicit declaration of function 'load_dialog' file-pdf.c:380: error: 'PopplerPage' undeclared (first use in this function) file-pdf.c:380: error: 'test_page' undeclared (first use in this function) file-pdf.c:380: warning: implicit declaration of function 'poppler_document_get_page' file-pdf.c:405: warning: implicit declaration of function 'load_image' file-pdf.c:449: error: 'page' undeclared (first use in this function) file-pdf.c:453: warning: implicit declaration of function 'poppler_page_get_size' file-pdf.c:458: warning: implicit declaration of function 'get_thumbnail' file-pdf.c:458: warning: assignment makes pointer from integer without a cast file-pdf.c: At top level: file-pdf.c:515: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token file-pdf.c:570: error: expected ')' before '*' token file-pdf.c:680: error: expected ')' before '*' token file-pdf.c:729: error: expected specifier-qualifier-list before 'PopplerDocument' file-pdf.c: In function 'thumbnail_thread': file-pdf.c:762: warning: implicit declaration of function 'poppler_document_get_n_pages' file-pdf.c:762: error: 'ThreadData' has no member named 'document' file-pdf.c:768: error: 'ThreadData' has no member named 'selector' file-pdf.c:772: error: 'ThreadData' has no member named 'document' file-pdf.c:773: warning: assignment makes pointer from integer without a cast file-pdf.c:777: error: 'ThreadData' has no member named 'stop_thumbnailing' file-pdf.c: At top level: file-pdf.c:785: error: expected ')' before '*' token gmake[3]: *** [file_pdf-file-pdf.o] Error 1 gmake[3]: Leaving directory `/usr/ports/graphics/gimp-app/work/gimp-2.6.11/plug-ins/common'
Re: Problem building GIMP 2.6.11 on 8.2-PRERELEASE
On Fri, 28 Jan 2011, William Bulley wrote: So something is clearly wrong here. The /var/db/ports/poppler/OPTIONS file had: WITHOUT_CAIRO=yes inside, so I changed that to WITH_CAIRO=yes and repeated the above steps. The file /usr/local/libdata/pkgconfig/poppler-cairo.pc is now there! The right way to do that is # cd /usr/ports/graphics/poppler # make config You can reset the options with make rmconfig. ___ 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: Problem building GIMP 2.6.11 on 8.2-PRERELEASE
William Bulley w...@umich.edu writes: Everything up to this point builds okay. Then this happens: Making all in common gmake[3]: Entering directory `/usr/ports/graphics/gimp-app/work/gimp-2.6.11/plug-ins/common' cc -DHAVE_CONFIG_H -I. -I../.. -I../.. -D_THREAD_SAFE -D_REENTRANT -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/pango-1.0 -I/usr/local/include/gio-unix-2.0/ -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -DGIMP_DISABLE_DEPRECATED -DGDK_MULTIHEAD_SAFE -DGTK_MULTIHEAD_SAFE -O2 -fno-strict-aliasing -pipe -Wall -Wdeclaration-after-statement -Wmissing-prototypes -Wmissing-declarations -Winit-self -Wpointer-arith -Wold-style-definition -MT file_pdf-file-pdf.o -MD -MP -MF .deps/file_pdf-file-pdf.Tpo -c -o file_pdf-file-pdf.o `test -f 'file-pdf.c' || echo './'`file-pdf.c file-pdf.c:30:21: error: poppler.h: No such file or directory [...] And poppler.h exists here: /usr/local/include/poppler/glib/poppler.h and here: /usr/ports/graphics/poppler/work/poppler-0.14.5/glib/poppler.h and here: /usr/ports/graphics/poppler-gtk/work/poppler-0.14.5/glib/poppler.h and they are all identical. Only the first counts, and it's the one that should be used. You may be doing something strange in the build; you don't mention how you started the build. Definitely make sure you do a make clean before restarting it, and make sure that poppler shows up up in the list of installed ports (pkg_info). ___ 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: Problem building GIMP 2.6.11 on 8.2-PRERELEASE
According to Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org on Thu, 01/27/11 at 11:04: William Bulley w...@umich.edu writes: Everything up to this point builds okay. Then this happens: Making all in common gmake[3]: Entering directory `/usr/ports/graphics/gimp-app/work/gimp-2.6.11/plug-ins/common' cc -DHAVE_CONFIG_H -I. -I../.. -I../.. -D_THREAD_SAFE -D_REENTRANT -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/pango-1.0 -I/usr/local/include/gio-unix-2.0/ -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -DGIMP_DISABLE_DEPRECATED -DGDK_MULTIHEAD_SAFE -DGTK_MULTIHEAD_SAFE -O2 -fno-strict-aliasing -pipe -Wall -Wdeclaration-after-statement -Wmissing-prototypes -Wmissing-declarations -Winit-self -Wpointer-arith -Wold-style-definition -MT file_pdf-file-pdf.o -MD -MP -MF .deps/file_pdf-file-pdf.Tpo -c -o file_pdf-file-pdf.o `test -f 'file-pdf.c' || echo './'`file-pdf.c file-pdf.c:30:21: error: poppler.h: No such file or directory [...] And poppler.h exists here: /usr/local/include/poppler/glib/poppler.h and here: /usr/ports/graphics/poppler/work/poppler-0.14.5/glib/poppler.h and here: /usr/ports/graphics/poppler-gtk/work/poppler-0.14.5/glib/poppler.h and they are all identical. Only the first counts, and it's the one that should be used. Just wanted to show that the include file was present. You may be doing something strange in the build; you don't mention how you started the build. Definitely make sure you do a make clean before restarting it, and make sure that poppler shows up up in the list of installed ports (pkg_info). I start the build in graphics/gimp followed by make install freebsd% pkg_info | grep -i poppler poppler-0.14.5 A PDF rendering library poppler-data-0.4.4 Poppler encoding data poppler-gtk-0.14.5 Gtk bindings to poppler Same results doing a make install after a make clean... :-( Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ 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: Problem building GIMP 2.6.11 on 8.2-PRERELEASE
On 27/01/2011 17:22, William Bulley wrote: According to Lowell Gilbertfreebsd-questions-lo...@be-well.ilk.org on Thu, 01/27/11 at 11:04: William Bulleyw...@umich.edu writes: Everything up to this point builds okay. Then this happens: Making all in common gmake[3]: Entering directory `/usr/ports/graphics/gimp-app/work/gimp-2.6.11/plug-ins/common' cc -DHAVE_CONFIG_H -I. -I../.. -I../.. -D_THREAD_SAFE -D_REENTRANT -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/pango-1.0 -I/usr/local/include/gio-unix-2.0/ -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -DGIMP_DISABLE_DEPRECATED -DGDK_MULTIHEAD_SAFE -DGTK_MULTIHEAD_SAFE -O2 -fno-strict-aliasing -pipe -Wall -Wdeclaration-after-statement -Wmissing-prototypes -Wmissing-declarations -Winit-self -Wpointer-arith -Wold-style-definition -MT file_pdf-file-pdf.o -MD -MP -MF .deps/file_pdf-file-pdf.Tpo -c -o file_pdf-file-pdf.o `test -f 'file-pdf.c' || echo './'`file-pdf.c file-pdf.c:30:21: error: poppler.h: No such file or directory It seems that gmake does not call `pkg-config --libs --cflags poppler`. do you have pkg-config and poppler installed correctly? /usr/local/libdata/pkgconfig/poppler-cairo.pc /usr/local/libdata/pkgconfig/poppler-cpp.pc /usr/local/libdata/pkgconfig/poppler-splash.pc /usr/local/libdata/pkgconfig/poppler.pc These files must be installed by poppler. In your case I will reinstall graphics/poppler by hand and verify that pkg-config finds it. Cheers, -- David Demelier ___ 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: Problem building GIMP 2.6.11 on 8.2-PRERELEASE
According to David Demelier demelier.da...@gmail.com on Thu, 01/27/11 at 11:39: It seems that gmake does not call `pkg-config --libs --cflags poppler`. do you have pkg-config and poppler installed correctly? /usr/local/libdata/pkgconfig/poppler-cairo.pc /usr/local/libdata/pkgconfig/poppler-cpp.pc /usr/local/libdata/pkgconfig/poppler-splash.pc /usr/local/libdata/pkgconfig/poppler.pc These files must be installed by poppler. In your case I will reinstall graphics/poppler by hand and verify that pkg-config finds it. You mention gmake, yet I use # make install all the time. Is this really gmake under the covers? I see both executables and they differ: freebsd% ls -l /usr/local/bin/gmake /usr/bin/make -r-xr-xr-x 1 root wheel 378392 Jan 25 10:12 /usr/bin/make -r-xr-xr-x 1 root wheel 156592 Jan 25 11:29 /usr/local/bin/gmake This is what I found when looking for those four above files: freebsd% ls -l /usr/local/libdata/pkgconfig/poppler-cairo.pc /usr/local/libdata/pkgconfig/poppler-cpp.pc /usr/local/libdata/pkgconfig/poppler-splash.pc /usr/local/libdata/pkgconfig/poppler.pc ls: /usr/local/libdata/pkgconfig/poppler-cairo.pc: No such file or directory -r--r--r-- 1 root wheel 304 Jan 27 11:43 /usr/local/libdata/pkgconfig/poppler-cpp.pc -r--r--r-- 1 root wheel 222 Jan 27 11:43 /usr/local/libdata/pkgconfig/poppler-splash.pc -r--r--r-- 1 root wheel 222 Jan 27 11:43 /usr/local/libdata/pkgconfig/poppler.pc I rebuilt (make deinstall; make clean; make install) graphics/poppler. It made and installed cleanly (as did pkg-config earlier this week). I have these packages: poppler-0.14.5 A PDF rendering library poppler-data-0.4.4 Poppler encoding data poppler-gtk-0.14.5 Gtk bindings to poppler pkg-config-0.25_1 A utility to retrieve information about installed libraries Which is the correct port to install this poppler-cairo file? I see two copies in the ports tree: /usr/ports/graphics/poppler/work/poppler-0.14.5/poppler-cairo.pc and /usr/ports/graphics/poppler-gtk/work/poppler-0.14.5/poppler-cairo.pc When I run this: # pkg-config --libs --cflags poppler I see this: -I/usr/local/include/poppler -L/usr/local/lib -lpoppler Is that to be expected? Note that the file poppler.h exists here: /usr/local/include/poppler/glib/poppler.h so would that not imply that -I/usr/local/include/poppler is wrong and instead should be: -I/usr/local/include/poppler/glib ?? Thanks for all the suggestions, but I am still in a pickle... :-( Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ 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: Problem building GIMP 2.6.11 on 8.2-PRERELEASE
On Thu, Jan 27, 2011 at 11:55 AM, William Bulley w...@umich.edu wrote:
You mention gmake, yet I use # make install all the time. Is this
really gmake under the covers? I see both executables and they differ:
gmake is GNU Make, some applications don't talk nice w/ bsdmake ('make' on
your bsd system). If your installing GIMP from ports then you should be
correctly using something like 'make install clean'. The only time I've
invoked gmake was when building something by hand vs letting a ports
makefile do the footwork for me.
___
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: Problem building GIMP 2.6.11 on 8.2-PRERELEASE
According to Chris Brennan xa...@xaerolimit.net on Thu, 01/27/11 at 12:03:
gmake is GNU Make, some applications don't talk nice w/ bsdmake ('make' on
your bsd system). If your installing GIMP from ports then you should be
correctly using something like 'make install clean'. The only time I've
invoked gmake was when building something by hand vs letting a ports
makefile do the footwork for me.
Okay, thanks. However I still have a broken poppler (somehow) which
means I am unable to build the Gimp from the ports tree. What should I
next look for? I have re-built/installed graphics/poppler and also
graphics/gimp (using make install) but I still get the same error. :-(
Regards,
web...
--
William Bulley Email: w...@umich.edu
72 characters width template -|
___
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: Problem building GIMP 2.6.11 on 8.2-PRERELEASE
On Thu, 27 Jan 2011, William Bulley wrote: According to David Demelier demelier.da...@gmail.com on Thu, 01/27/11 at 11:39: It seems that gmake does not call `pkg-config --libs --cflags poppler`. do you have pkg-config and poppler installed correctly? /usr/local/libdata/pkgconfig/poppler-cairo.pc /usr/local/libdata/pkgconfig/poppler-cpp.pc /usr/local/libdata/pkgconfig/poppler-splash.pc /usr/local/libdata/pkgconfig/poppler.pc These files must be installed by poppler. In your case I will reinstall graphics/poppler by hand and verify that pkg-config finds it. You mention gmake, yet I use # make install all the time. Is this really gmake under the covers? I see both executables and they differ: gmake is used transparently by the ports system when a port needs it, typically marked by USE_GMAKE= yes in the port Makefile (graphics/gimp-app, in this case). poppler-0.14.5 A PDF rendering library poppler-data-0.4.4 Poppler encoding data poppler-gtk-0.14.5 Gtk bindings to poppler pkg-config-0.25_1 A utility to retrieve information about installed libraries Which is the correct port to install this poppler-cairo file? poppler-0.14.5 Be sure to clean it before rebuilding and installing. ___ 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: ndis-based network driver fails to load at boot (8.2-PRERELEASE)
On Tue, Jan 25, 2011 at 7:28 PM, Yuri y...@rawbw.com wrote: Does reverting: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/if_ndis/if_ndis_usb.c.diff?r1=1.19.2.3;r2=1.19.2.4;f=h fixed problem? Hi Paul, So did the find that this particular checkin caused the problem led to some resolution? Is it fixed now in 8.X or 9.X? Should be fixed in 9.0 aka CURRENT and I hope in 8.2 (PRE)RELEASE. ___ 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
Problem building GIMP 2.6.11 on 8.2-PRERELEASE
Everything up to this point builds okay. Then this happens: Making all in common gmake[3]: Entering directory `/usr/ports/graphics/gimp-app/work/gimp-2.6.11/plug-ins/common' cc -DHAVE_CONFIG_H -I. -I../.. -I../.. -D_THREAD_SAFE -D_REENTRANT -I/usr/local/include/gtk-2.0 -I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0 -I/usr/local/include/cairo -I/usr/local/include/gdk-pixbuf-2.0 -I/usr/local/include/pango-1.0 -I/usr/local/include/gio-unix-2.0/ -I/usr/local/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/pixman-1 -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include -DGIMP_DISABLE_DEPRECATED -DGDK_MULTIHEAD_SAFE -DGTK_MULTIHEAD_SAFE -O2 -fno-strict-aliasing -pipe -Wall -Wdeclaration-after-statement -Wmissing-prototypes -Wmissing-declarations -Winit-self -Wpointer-arith -Wold-style-definition -MT file_pdf-file-pdf.o -MD -MP -MF .deps/file_pdf-file-pdf.Tpo -c -o file_pdf-file-pdf.o `test -f 'file-pdf.c' || echo './'`file-pdf.c file-pdf.c:30:21: error: poppler.h: No such file or directory file-pdf.c:70: error: expected ')' before '*' token file-pdf.c:77: error: expected ')' before '*' token file-pdf.c:80: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token file-pdf.c:83: error: expected ')' before '*' token file-pdf.c: In function 'run': file-pdf.c:330: error: 'PopplerDocument' undeclared (first use in this function) file-pdf.c:330: error: (Each undeclared identifier is reported only once file-pdf.c:330: error: for each function it appears in.) file-pdf.c:330: error: 'doc' undeclared (first use in this function) file-pdf.c:331: warning: ISO C90 forbids mixed declarations and code file-pdf.c:356: warning: implicit declaration of function 'open_document' file-pdf.c:364: warning: implicit declaration of function 'load_dialog' file-pdf.c:380: error: 'PopplerPage' undeclared (first use in this function) file-pdf.c:380: error: 'test_page' undeclared (first use in this function) file-pdf.c:380: warning: implicit declaration of function 'poppler_document_get_page' file-pdf.c:405: warning: implicit declaration of function 'load_image' file-pdf.c:449: error: 'page' undeclared (first use in this function) file-pdf.c:453: warning: implicit declaration of function 'poppler_page_get_size' file-pdf.c:458: warning: implicit declaration of function 'get_thumbnail' file-pdf.c:458: warning: assignment makes pointer from integer without a cast file-pdf.c: At top level: file-pdf.c:515: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token file-pdf.c:570: error: expected ')' before '*' token file-pdf.c:680: error: expected ')' before '*' token file-pdf.c:729: error: expected specifier-qualifier-list before 'PopplerDocument' file-pdf.c: In function 'thumbnail_thread': file-pdf.c:762: warning: implicit declaration of function 'poppler_document_get_n_pages' file-pdf.c:762: error: 'ThreadData' has no member named 'document' file-pdf.c:768: error: 'ThreadData' has no member named 'selector' file-pdf.c:772: error: 'ThreadData' has no member named 'document' file-pdf.c:773: warning: assignment makes pointer from integer without a cast file-pdf.c:777: error: 'ThreadData' has no member named 'stop_thumbnailing' file-pdf.c: At top level: file-pdf.c:785: error: expected ')' before '*' token gmake[3]: *** [file_pdf-file-pdf.o] Error 1 gmake[3]: Leaving directory `/usr/ports/graphics/gimp-app/work/gimp-2.6.11/plug-ins/common' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/graphics/gimp-app/work/gimp-2.6.11/plug-ins' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/gimp-app/work/gimp-2.6.11' gmake: *** [all] Error 2 *** Error code 1 Stop in /usr/ports/graphics/gimp-app. *** Error code 1 Stop in /usr/ports/graphics/gimp-app. *** Error code 1 Stop in /usr/ports/graphics/gimp. *** Error code 1 Stop in /usr/ports/graphics/gimp. And poppler.h exists here: /usr/local/include/poppler/glib/poppler.h and here: /usr/ports/graphics/poppler/work/poppler-0.14.5/glib/poppler.h and here: /usr/ports/graphics/poppler-gtk/work/poppler-0.14.5/glib/poppler.h and they are all identical. Regards, web... -- William Bulley Email: w...@umich.edu 72 characters width template -| ___ 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: ndis-based network driver fails to load at boot (8.2-PRERELEASE)
Does reverting: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/if_ndis/if_ndis_usb.c.diff?r1=1.19.2.3;r2=1.19.2.4;f=h fixed problem? Hi Paul, So did the find that this particular checkin caused the problem led to some resolution? Is it fixed now in 8.X or 9.X? Yuri ___ 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: ndis-based network driver fails to load at boot (8.2-PRERELEASE)
On Mon, Jan 17, 2011 at 5:12 PM, Yuri y...@rawbw.com wrote: Do you load ndis and if_ndis via loader.conf too? Yes, presense of if_ndis and ndis in loader.conf doesn't change anything. Does reverting: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/if_ndis/if_ndis_usb.c.diff?r1=1.19.2.3;r2=1.19.2.4;f=h fixed problem? ___ 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: ndis-based network driver fails to load at boot (8.2-PRERELEASE)
On 01/18/2011 06:23, Paul B Mahol wrote: Does reverting: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/if_ndis/if_ndis_usb.c.diff?r1=1.19.2.3;r2=1.19.2.4;f=h fixed problem? Yes it does fix the problem. Yuri ___ 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: ndis-based network driver fails to load at boot (8.2-PRERELEASE)
Do you load ndis and if_ndis via loader.conf too? Yes, presense of if_ndis and ndis in loader.conf doesn't change anything. Yuri ___ 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: ndis-based network driver fails to load at boot (8.2-PRERELEASE)
On Sat, Jan 15, 2011 at 1:19 AM, Yuri y...@rawbw.com wrote: I have the old module that always worked. Begining from some update (~8.1-STABLE), it stopped loading at boot time with the messages: ...skipped... module ndis already present KLD file bcmwl5_sys.ko is missing dependencies ...skipped... /boot/loader.conf has this line that is supposed to, and was loading the module: bcmwl5_sys_load=YES Rebuilding the driver from Windows version with the current ndisgen doesn't change anything. Loading this module by hand (kldload) after system boots succeeds and it runs fine. Although it also says: module ndis already present Why it fails to load at boot? Do you load ndis and if_ndis via loader.conf too? ___ 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
ndis-based network driver fails to load at boot (8.2-PRERELEASE)
I have the old module that always worked. Begining from some update (~8.1-STABLE), it stopped loading at boot time with the messages: ...skipped... module ndis already present KLD file bcmwl5_sys.ko is missing dependencies ...skipped... /boot/loader.conf has this line that is supposed to, and was loading the module: bcmwl5_sys_load=YES Rebuilding the driver from Windows version with the current ndisgen doesn't change anything. Loading this module by hand (kldload) after system boots succeeds and it runs fine. Although it also says: module ndis already present Why it fails to load at boot? Yuri ___ 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
