Re: SolarFlare 10GB card
On Aug 13, 2013, at 8:30 PM, kpn...@pobox.com wrote: > On Tue, Aug 13, 2013 at 07:13:57PM -0700, aurfalien wrote: >> >> On Aug 12, 2013, at 11:12 AM, Roland Smith wrote: >> >>> On Mon, Aug 12, 2013 at 10:47:27AM -0700, aurfalien wrote: Hi all, We've a brand spanking new SolarFlare 10GB nic for use with our beast of a server. However the vendor support page says the driver is in beta. >>> >>> If you look in the download[1], you'll see that the driver is named sfxge. >>> It >>> was released in November 2011. This driver is already present in FreeBSD >>> 9.1, >>> look at the source in /usr/src/sys/dev/sfxge. >>> So it seems like it is as much out of beta as any other driver. :-) >> >> It was actually easier to dl the driver from SolarF;ares site and follow >> there dirs. >> >> But for future, ref, would be cool to now how to do this. > > I haven't been paying that much attention, but ... > > If you are running 9.1 or later, what happens if you run as root these two > commands: > > # kldload if_sfxge > # kldstat Hi, Thanks for the reply. It fails as cannot find module. Eh, no biggy, building it from there actual source is trivial. - aurf ___ 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: SolarFlare 10GB card
On Aug 12, 2013, at 11:12 AM, Roland Smith wrote: > On Mon, Aug 12, 2013 at 10:47:27AM -0700, aurfalien wrote: >> Hi all, >> >> We've a brand spanking new SolarFlare 10GB nic for use with our beast of a >> server. >> >> However the vendor support page says the driver is in beta. > > If you look in the download[1], you'll see that the driver is named sfxge. It > was released in November 2011. This driver is already present in FreeBSD 9.1, > look at the source in /usr/src/sys/dev/sfxge. > So it seems like it is as much out of beta as any other driver. :-) It was actually easier to dl the driver from SolarF;ares site and follow there dirs. But for future, ref, would be cool to now how to do this. - aurf ___ 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: SolarFlare 10GB card
On Aug 12, 2013, at 11:12 AM, Roland Smith wrote: > On Mon, Aug 12, 2013 at 10:47:27AM -0700, aurfalien wrote: >> Hi all, >> >> We've a brand spanking new SolarFlare 10GB nic for use with our beast of a >> server. >> >> However the vendor support page says the driver is in beta. > > If you look in the download[1], you'll see that the driver is named sfxge. It > was released in November 2011. This driver is already present in FreeBSD 9.1, > look at the source in /usr/src/sys/dev/sfxge. > So it seems like it is as much out of beta as any other driver. :-) Well, how would I compile it?:) I can the dir in my 9.2RC1 install. - aurf ___ 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: FreeBSD on ThinkPad W530
Hi! Yay another FreeBSD laptop user! Please do this: * join the freebsd-mobile list; * create PRs for each of your problems with -10 above!; * the power utilisation thing is going to be fun to track down - what kind of CPU is in there? Is it a recent Intel? I'm playing around with their tools at the moment; maybe we can look at the power the CPU is consuming and then add on the power from each of the other parts in your laptop until we figure out what's drawing said power * the brightness thing is known; a bunch of us have this issue and the "fix" is known. Trouble is, there's no (yet) clean fix that's made it into acpi_ibm. I'm glad there's another person who cares; it means we have more chance of getting a real fix that works for multiple people into the tree. As for suspend/resume - I'm glad it at least works for you. Right now I don't even get video output upon resume. But, it's a starting point. Let's get the PRs filed, the brightness thing pushed into -HEAD, and then start down the path of figuring out where the power consumption is coming from. -adrian On 13 August 2013 15:21, vermaden wrote: > Hi, > > I have just tried FreeBSD on ThinkPad W530 and I must say that its very > disapointing experience ... > > The FreeBSD 9.2-RC1 and PC-BSD 9.2-BETA2 does not even boot from the USB > drive - instant kernel panic and reboot. > > The FreeBSD 10.0-CURRENT was able to boot successfully and I could install > FreeBSD onto the drive with 'ZFS Madnss' style. > > After installation with extended battery charged to 100% I have about 3 > hours of work ... while having about 10 hours on Windows (haven't tried > Linux yet). I disabled discrete graphics (Nvidia) in the BIOS and also > added set hw.pci.do_power_nodriver to 3, but that also did not solved the > 'battery' problem. The powerd daemon was of course running and worked ok. > > After compiling new x11/xorg (with WITH_NEW_XORG in /etc/make.conf) along > with x11-wm/openbox I was able to get X11 working, but I can not go back to > console as its not implemented yet. > > The screen is 100% bright all the time because acpi_ibm module probably > does not support this model yet (changing the dev.acpi_ibm.0.lcd_brightness > is pointless, no effects). > > Suspend and resume works very poor, after resume the resolution is 640x640 > with all colors broken, requires restarting X11 in 'blind mode' (not > implemented console switching). > > Of course as all of the above is not possible, using the Nvidia Optimus > technology (graphics card switching) is probably also not possible, which > is possible with Bumblebee on Linux, any plans on merging that > functionality into FreeBSD? > > At least WiFi and LAN worked out of the box ... > > Now ... how can I help, what information can I provide to help resolve > these issues: > 1. disable power for discrete graphics card > 2. have working screen brightness changing and working other Fn + X > shotrcuts > 3. I guess I will have to 'just wait' for the console switching > implementation? > > ... or maybe I am doing it 'wrong' someone have W530 there and uses > FreeBSD with any more degree of success then I? > > Regards, > vermaden > ___ > 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" > ___ 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"
FreeBSD on ThinkPad W530
Hi, I have just tried FreeBSD on ThinkPad W530 and I must say that its very disapointing experience ... The FreeBSD 9.2-RC1 and PC-BSD 9.2-BETA2 does not even boot from the USB drive - instant kernel panic and reboot. The FreeBSD 10.0-CURRENT was able to boot successfully and I could install FreeBSD onto the drive with 'ZFS Madnss' style. After installation with extended battery charged to 100% I have about 3 hours of work ... while having about 10 hours on Windows (haven't tried Linux yet). I disabled discrete graphics (Nvidia) in the BIOS and also added set hw.pci.do_power_nodriver to 3, but that also did not solved the 'battery' problem. The powerd daemon was of course running and worked ok. After compiling new x11/xorg (with WITH_NEW_XORG in /etc/make.conf) along with x11-wm/openbox I was able to get X11 working, but I can not go back to console as its not implemented yet. The screen is 100% bright all the time because acpi_ibm module probably does not support this model yet (changing the dev.acpi_ibm.0.lcd_brightness is pointless, no effects). Suspend and resume works very poor, after resume the resolution is 640x640 with all colors broken, requires restarting X11 in 'blind mode' (not implemented console switching). Of course as all of the above is not possible, using the Nvidia Optimus technology (graphics card switching) is probably also not possible, which is possible with Bumblebee on Linux, any plans on merging that functionality into FreeBSD? At least WiFi and LAN worked out of the box ... Now ... how can I help, what information can I provide to help resolve these issues: 1. disable power for discrete graphics card 2. have working screen brightness changing and working other Fn + X shotrcuts 3. I guess I will have to 'just wait' for the console switching implementation? ... or maybe I am doing it 'wrong' someone have W530 there and uses FreeBSD with any more degree of success then I? Regards, vermaden ___ 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"
Qlogic Fiber Target and ZFS
Okay Ive been down this road before but seem to have lost my notes and cat seem to find the original google doc on the process how does one configure a Qlogic 8Gb fiber card as target and attach the zpool ___ 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: sysvipc only for one jail
On Tue, Aug 13, 2013 at 12:14 AM, Shane Ambler wrote: > On 12/08/2013 21:39, Trond Endrestøl wrote: >> >> On Mon, 12 Aug 2013 13:57+0200, David Demelier wrote: > > >>> And thus, it's not enabled as postgresql tells: >>> >>> creating template1 database in /usr/local/pgsql/data/base/1 ... FATAL: >>> could not create shared memory segment: Function not implemented >> >> >> I'll look into this by creating a new jail for PostgreSQL 9.2 when I >> get home. >> > > While it is currently in beta maybe you could also try 9.3 and verify that > the shared memory update works or eliminates this configuration? > No need for any complication. Pg will work just fine by following this simple recipe. I compute a UID unique to the overall system by concatenating 70 (the natural UID for the pgsql user user in FBSD) and the last 3 digits of the Jails'IP, but you can come up with any numbering scheme as long as it's consistent and easily associated to a specific jail. For example for the Pg running on jail 192.168.101.124, install PostgreSQL and before doing anything else: pw usermod pgsql -u 70124 pw groupmod pgsql -g 70124 pw usermod pgsql -g 70124 chown -R pgsql /usr/local/pgsql/ chgrp -R pgsql /usr/local/pgsql/ Any other application that uses SYSV IPC should follow a similar recipe, and it's compatible with al versions of Jails. And that's it. I have dozens of jails with Pg running this way. Likewise also make sure all of your network daemons listen _specifically_ to that jail's IP, in Pg that would be postgresql.conf: listen_addresses = 'xx' although the default 'localhost' should work most of the time. Always double check all daemons with sockstat (e.g. sockstat -4l) to make sure they only listen on that jail's IP(s). Best, -- Alejandro Imass ___ 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: trouble with PostgreSQL 9.2 on FreeBSD 10.0-CURRENT: superuser can not autheticate anymore with md5 password hash set
On Tue, 13 Aug 2013 18:22:33 +0200 Terje Elde wrote: > On 13. aug. 2013, at 16:30, "O. Hartmann" > wrote: > > What is going wrong? > > Are you unable to connect, or do you get an error message? If you do, > what is it? > > Terje I always get this message: psql postgres pgsql Password for user pgsql: XX psql: FATAL: password authentication failed for user "pgsql" signature.asc Description: PGP signature
Re: trouble with PostgreSQL 9.2 on FreeBSD 10.0-CURRENT: superuser can not autheticate anymore with md5 password hash set
On 13. aug. 2013, at 16:30, "O. Hartmann" wrote: > What is going wrong? Are you unable to connect, or do you get an error message? If you do, what is it? Terje ___ 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: trouble with PostgreSQL 9.2 on FreeBSD 10.0-CURRENT: superuser can not autheticate anymore with md5 password hash set
On Tue, 13 Aug 2013 17:55:06 +0300 Volodymyr Kostyrko wrote: > > 13.08.2013 17:30, O. Hartmann wrote: > >> For the past I ran PostgreSQL 9.2 servers on FreeBSD 10.0-CURRENT > >> successfully. But by now, out of the blue, login as the database's > >> supervisor "pgsql" remotely isn't possible any more. > >> > >> The appropriate lines in pg_hba.conf are: > >> > >> local all pgsql md5 > >> hostssl all pgsql 0.0.0.0/0 md5 > >> > >> The funny thing is: when login locally without providing a password > >> (swap md5 to trust in the "local" line) and setting the password > >> for the role "pgsql" via > >> > >> ALTER ROLE pgsql ENCRYPTED PASSWORD 'FooMe"; > > > > I guess ENCRYPTED means you are substituting FooMe with md5 hashed > > password correctly salted with role name as postgresql requires? > > Silly me, that's wrong. ENCRYPTED only means that password will be > stored encrypted on the disk. There's a side note about using > ENCRYPTED password with postgres in the docs though: > > "Note that older clients might lack support for the MD5 > authentication mechanism that is needed to work with passwords that > are stored encrypted." > Well, even if not ENCRYPTED it doesn't work anymore and prior to this failure, the passwords were stored md5 hashed via pgadmin3 all the time - and it worked. I made now another test. On a FreeBSD 9.2 box which is also running PostgreSQL 9.2 and to which I have access the way that is now rejected by the others, I did a login as the supervisor (pgsql) successfully and then set the password for that supervisor again with alter role pgsql with encrypted password 'FooMe'; (FooMe was the passowrd used before on the same system, it worked definitely) and - booom - I can not login anymore onto that machine! Something is definitely wrong. I have no idea what is wrong here. signature.asc Description: PGP signature
Re: trouble with PostgreSQL 9.2 on FreeBSD 10.0-CURRENT: superuser can not autheticate anymore with md5 password hash set
13.08.2013 17:30, O. Hartmann wrote: For the past I ran PostgreSQL 9.2 servers on FreeBSD 10.0-CURRENT successfully. But by now, out of the blue, login as the database's supervisor "pgsql" remotely isn't possible any more. The appropriate lines in pg_hba.conf are: local all pgsql md5 hostssl all pgsql 0.0.0.0/0 md5 The funny thing is: when login locally without providing a password (swap md5 to trust in the "local" line) and setting the password for the role "pgsql" via ALTER ROLE pgsql ENCRYPTED PASSWORD 'FooMe"; I guess ENCRYPTED means you are substituting FooMe with md5 hashed password correctly salted with role name as postgresql requires? Silly me, that's wrong. ENCRYPTED only means that password will be stored encrypted on the disk. There's a side note about using ENCRYPTED password with postgres in the docs though: "Note that older clients might lack support for the MD5 authentication mechanism that is needed to work with passwords that are stored encrypted." -- Sphinx of black quartz, judge my vow. ___ 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: trouble with PostgreSQL 9.2 on FreeBSD 10.0-CURRENT: superuser can not autheticate anymore with md5 password hash set
13.08.2013 17:30, O. Hartmann wrote: For the past I ran PostgreSQL 9.2 servers on FreeBSD 10.0-CURRENT successfully. But by now, out of the blue, login as the database's supervisor "pgsql" remotely isn't possible any more. The appropriate lines in pg_hba.conf are: local all pgsql md5 hostssl all pgsql 0.0.0.0/0 md5 The funny thing is: when login locally without providing a password (swap md5 to trust in the "local" line) and setting the password for the role "pgsql" via ALTER ROLE pgsql ENCRYPTED PASSWORD 'FooMe"; I guess ENCRYPTED means you are substituting FooMe with md5 hashed password correctly salted with role name as postgresql requires? or doing the same via pgadmin3 from remotely by also swapping md5 to trust in the line "hostssl" for global network, it seems I could alter/change the password for the supervisor pgsql. But restoring the password check by setting back "md5" leaves me locked out! By the way, this strange behaviour occurs on ALL(!) PostgreSQL 9.2 servers running on FreeBSD 10.0-CURRENT boxes. Ports databases/postgresql-XXX as well as FreeBSD is as of the latest sources and up to date. What is going wrong? -- Sphinx of black quartz, judge my vow. ___ 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"
trouble with PostgreSQL 9.2 on FreeBSD 10.0-CURRENT: superuser can not autheticate anymore with md5 password hash set
For the past I ran PostgreSQL 9.2 servers on FreeBSD 10.0-CURRENT successfully. But by now, out of the blue, login as the database's supervisor "pgsql" remotely isn't possible any more. The appropriate lines in pg_hba.conf are: local all pgsql md5 hostssl all pgsql 0.0.0.0/0 md5 The funny thing is: when login locally without providing a password (swap md5 to trust in the "local" line) and setting the password for the role "pgsql" via ALTER ROLE pgsql ENCRYPTED PASSWORD 'FooMe"; or doing the same via pgadmin3 from remotely by also swapping md5 to trust in the line "hostssl" for global network, it seems I could alter/change the password for the supervisor pgsql. But restoring the password check by setting back "md5" leaves me locked out! By the way, this strange behaviour occurs on ALL(!) PostgreSQL 9.2 servers running on FreeBSD 10.0-CURRENT boxes. Ports databases/postgresql-XXX as well as FreeBSD is as of the latest sources and up to date. What is going wrong? Please CC me. Regards, Oliver signature.asc Description: PGP signature
Re: sysvipc only for one jail
On Tue, 13 Aug 2013 07:53-0400, Fbsd8 wrote: > What 9.3 are you talking about > 9.2-RC1 is the newest available. > Is 9.3 a typo and you really mean 9.2?? PostgreSQL 9.3beta2, you'll find it in ports as databases/postgresql93-server, etc. http://wiki.postgresql.org/wiki/What's_new_in_PostgreSQL_9.3 Among other things: o Switch to Posix shared memory and mmap(). (DONE) -- +---++ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +---++___ 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: sysvipc only for one jail
Terje Elde wrote: On 12. aug. 2013, at 19.46, Trond Endrestøl wrote: If you start the jail manually using jail(8), then /etc/jail.conf comes into play, whereas the lines in /etc/rc.conf is used during automatic startup of the jails when the host is rebooted. The whole arrangement seems unnecessary redundant, and I truly wish this can be merged sooner rather than later. It *is* unnecessary redundant. If you're using /etc/rc.conf to define the jails, then start them with: /etc/rc.d/jail start jailname That is, if you're mostly using /etc/rc.conf to define the jails, then start them manually using that as well? Problem solved? Terje Here is a writeup about jails that you may find useful. It includes a boot time jail startup script for jail(8) defined jails. http://www.a1poweruser.com/35.00-Jails_guide_article.php ___ 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: sysvipc only for one jail
Shane Ambler wrote: On 12/08/2013 21:39, Trond Endrestøl wrote: While it is currently in beta maybe you could also try 9.3 and verify that the shared memory update works or eliminates this configuration? If you missed the change, 9.3 is implementing shared memory using mmap. What 9.3 are you talking about 9.2-RC1 is the newest available. Is 9.3 a typo and you really mean 9.2?? ___ 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: WIDE-DHCP
yes, unfortunately it's not well enough for me:(( On Tue, Aug 13, 2013 at 1:32 PM, wrote: > > It seems that the distribution includes a directory called db_sample > > with some tutorials/examples. > > > > But it also seems that the last release of wide-dhcp is 16 years old... > > And I also strongly doubt that he's going to have any better luck > with his /8 net. > > Steinar Haug, Nethelp consulting, sth...@nethelp.no > ___ 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: WIDE-DHCP
> It seems that the distribution includes a directory called db_sample > with some tutorials/examples. > > But it also seems that the last release of wide-dhcp is 16 years old... And I also strongly doubt that he's going to have any better luck with his /8 net. Steinar Haug, Nethelp consulting, sth...@nethelp.no ___ 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: WIDE-DHCP
Sam, It seems that the distribution includes a directory called db_sample with some tutorials/examples. But it also seems that the last release of wide-dhcp is 16 years old... Olivier On Tue, Aug 13, 2013 at 3:42 PM, s m wrote: > hello guys, > > > does any body use WIDE-DHCP? i installed it on my freebsd 8.2 but don't > know how to configure it. i searched a lot but can not find any useful > documentation. > > please let me know if some body configure it or have some application about. > thanks in advance > SAM > ___ > 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" ___ 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: 9.2-RC1: Problem with Kernel
On Tue, 13 Aug 2013 05:14:52 +0200, Polytropon wrote: > On Mon, 12 Aug 2013 21:01:14 + (UTC), Walter Hurry wrote: >> Sorry again. Anyway, I have it nailed down now. For anyone who is >> interested, the missing entry was: >> >> options ATA_CAM > > Correct. Line 84 and 264 have it commented out. This is the "new" method > of talking to disk devices, similarly as the acd interface for optical > media has been trans- formed into "SCSI over ATA" (ex device atapicam). > So the disk drive has not been recognized by the kernel, therefore: No > soup for you (i. e., no boot device). :-) Thanks, Polytropon! I have changed the controller (this is a VM, remember) to which the (same) virtual hard drive is attached, from ISA to SATA and "options ATA_CAM" is no longer needed. So I have learned a few things. Thanks again. ___ 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"
WIDE-DHCP
hello guys, does any body use WIDE-DHCP? i installed it on my freebsd 8.2 but don't know how to configure it. i searched a lot but can not find any useful documentation. please let me know if some body configure it or have some application about. thanks in advance SAM ___ 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: sysvipc only for one jail
On 12. aug. 2013, at 19.46, Trond Endrestøl wrote: > If you start the jail manually using jail(8), then /etc/jail.conf > comes into play, whereas the lines in /etc/rc.conf is used during > automatic startup of the jails when the host is rebooted. The whole > arrangement seems unnecessary redundant, and I truly wish this can be > merged sooner rather than later. It *is* unnecessary redundant. If you're using /etc/rc.conf to define the jails, then start them with: /etc/rc.d/jail start jailname That is, if you're mostly using /etc/rc.conf to define the jails, then start them manually using that as well? Problem solved? Terje ___ 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"
