Re: recommendations for laptop and desktop
On Jul 12, 2011, at 11:18 AM, Zoran Kolic wrote: > Comes a time to ask again and again the same question. > More I read, less I know. Just as I found that candida- > te for my new laptop, dell latitude 13 comes with anti- > glare screen and all hardware well supported, forums > reveal that it's 320gb hard drive heats a lot. It makes > vostro v13 better runner, but... > How sounds the idea to have a place on freebsd site for > such kind of data/wiki? Laptop recommendations should > include new models only, since older ones are not easy to > find in usable condition. Also, making a go for home > node, cold and quiet box, with parts fine under freebsd > is not so obvious. Especially for newer graphic chips. > It shows that my first idea to get cold phenom II on the > integrated mobo fails on almost all parts. > Yep, some kind of wiki, saying "phenom to use under 8.2 > to be cold and chip to find for amd mobo to take small > amount of power might be..." There is this list for laptops: http://laptop.bsdgroup.de/freebsd/ > At last, sad thing is that only before mentioned dell > comes supported and with matte screen. What is the box > you would recommend, not going deep into past decade? See the recent thread on the freebsd-mobile list with subject "Laptop recommendations?" JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Upgrade from 8.2-STABLE to 9.0-RELEASE wedges on SuperMicro H8DGiF-based system
On Jan 9, 2012, at 12:40 PM, Freddie Cash wrote: > Just wondering if anyone else has run into a similar issue. > > We have a ZFS storage server that was running 8.2-STABLE (from around > beginning of Dec 2011) without any issues, that was upgraded to > 9.0-RELEASE (to consolidate all the ZFS and networking fixes/updates > and bring it up to version parity with our other ZFS storage server > running 9.0) last Thursday. The "svn switch" of the source tree, the > buildworld, the buildkernel, the installkernel, the reboot with the > new kernel, the installworld, the reboot into the new world, the > mergemaster processes all completed successfully. About half-way > through the "make delete-old" process, the box locked up. No messages > on the console, no log entries of any kind, everything just stopped. > Had to do a power-cycle. And then everything went to hell. :( > > On reboot, the loader complained about not being able to determine > which disk it was booting from (even though the new loader had already > booted at least once), and gave strange messages about > panic/free/something or other (didn't write that error down). > > I was able to boot using a 9.0 install CD, drop to a loader prompt, > unload the kernel/modules from CD, load the kernel/modules from the > harddrive, set currdev to the harddrive, and boot. But no matter what > I did (gpart bootcode using pmbr/gptboot from CD or from HD; copy > loader from CD, copy /boot from CD), I could not get the loader on the > HD to load the kernel; always gave the same error message: can't > determine which disk we're booting from. > > After trying for 24 hours to make it work, I just re-installed off the > 9.0-RELEASE CD. > > Now, this box (alphadrive) will freeze after running for between 3 and > 10 hours. Even when left completely idle, it will lock up after about > 3 hours. :( > > I have another system (betadrive) that's almost identical hardware > (chassis, backplane, SATA controllers are different, everything else > is the same) that went from 8.2-STABLE to 9.0-RC2 to 9.0-RC3 to > 9.0-RELEASE without any issues. I've tried copying /boot/loader.conf, > /etc/make.conf, /etc/src.conf, /etc/sysctl.conf, /etc/rc.conf from > betadrive to alphadrive, without any change in the freezing behaviour. > > These are ZFS storage systems, with / (UFS) and swap on SSDs, with 16 > or 24 SATA HDs in the pool (3x 5-disk raidz2 + spare and 4x 6-disk > raidz2 resp). All of the ZFS settings are identical between the two > systems (pool name, pool properties, ZFS filesystems, ZFS properties > per filesystem). Dedupe and compression (LZJB) are enabled on both > systems. > > When alphadrive locks up, there are no entries made in any log files; > there are no log entries on the console; there are no entries in the > BIOS event log; there are no entries in the IPMI event log; the > CPU/case temps are below 40C (emergency shutoff is 75C) as shown via > IPMI; RAM usage is under 20 GB (24 GB per box) with the lowest being > under 2 GB used (I run top on the console so I can see the stats when > it locks up, and the time it locks up). It just ... stops. > > The system will even lock up when running in single-user mode, with > only / mounted (ZFS not loaded, zpool not imported). > > Hardware (alphadrive): > Chenbro 5U rackmount chassis with 24 hot-swap drive bays > SuperMicro H8DGi-F motherboard > AMD Opteron 2218 CPU (8-cores at 2.0 GHz) > 24 GB DDR3-SDRAM > 3x SuperMicro AOC-USAS-L8i SATA controllers (multi-lane break-out cables) > 8x Seagate 7200.12 1.5 TB SATA harddrives > 16x WD RE4 1.0 TB SATA harddrives > 1x Kingston 60 GB SSD (for /, swap, L2ARC) > > Hardware (betadrive): > SuperMicro 4U rackmount chassis with 16 hot-swap drive bays > SuperMicro H8DGi-F motherboard > AMD Opteron 2218 CPU (8-cores at 2.0 GHz) > 24 GB DDR3-SDRAM > 2x SuperMicro AOC-USAS2-L8i SATA controllers (multi-lane cables) > 16x WD RE4 2.0 TB SATA harddrives > 1x Kingston 60 GB SSD (for /, swap, L2ARC) > > betadrive runs perfectly with FreeBSD 9.0-RELEASE. > alphadrive locks up with FreeBSD 9.0-RELEASE. > > We're currently investigating hardware firmware revisions to see if > anything else is different between the two systems. > > Has anyone experience anything similar? Does anyone have any ideas on > what to look for? Any suggestions on what to try next? From what you've said I strongly suspect that you have some kind of hardware issue. Dodgy RAM is my first guess, something cooling-related is my 2nd, and PSU is my 3rd. It is a little suspicious that you only started having problems after your upgrade but it could be coincidence or it could be something about the new software tickling the hardware differently than the old. Open it up, make sure you don't have dust buildup and that all the fans are spinning, re-seat the RAM and then boot into memtest for a few hours. If you have spare similar hardware you can also try swapping components until you isolate the
Re: PCI AP card recommendations
On Jul 25, 2010, at 5:10 PM, Beach Geek wrote: > Looking for feedback from people using FreeBSD v8.x as access points. > We will be using Pentium 3 boxes with 8-STABLE as APs. > Each box will have a unique SSID and use WPA2-PSK. > Each AP will be linked back to 2 gateways. > > I'm looking for AP card suggestions and any helpful hints as far as the > APs. Looking for card models, not chipsets. > > Looking forward to hearing your experiences. I've been using a D-Link DWL-G520 PCI card in my FreeBSD access point since at least 6.x. It sports an Atheros 5212 chip and uses the ath driver. The card supports 802.11b/g as well as the "Turbo" 108Mbps mode. My current setup is FreeBSD 8.1-PRERELEASE with two vap's. The first is bridged with my LAN ethernet device and uses WPA-PSK. The second is for guests and has no security. The latter is firewalled off from the LAN and everything on the host except DNS. It's also bandwidth-controlled using dummynet. This is a small network and rarely has more than 8 or so wireless clients. A couple years ago I added a better external antenna (D-Link ANT24-0700, still available) and saw a noticeable range increase. I've been wanting to upgrade to 802.11n but to my knowledge there is still no rate algorithm so even supported cards will only operate at "g" speeds. Aside from that I've had no complaints whatsoever with my FreeBSD AP. I very much doubt my specific card is still available new. I don't have any experience with the newer card models but it's not unlikely they still make a similar card. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Apparent dnsbl bug in Sendmail or m4
I'm migrating a sendmail server from FreeBSD 4.x to FreeBSD 8.x. After
turning on the new server and feeding it some "live" e-mail, I noticed
that the DNS blacklist lookups weren't actually rejecting e-mail like
they did on the old server. (Actually the presence of blacklist
information in the SpamAssassin report on an unwanted message that was
delivered and a total lack of them in the sendmail logs (versus a
steady stream on the old server).)
I double-checked the syntax of my .mc file, re-ran "cd /etc/mail;
make", and examined the resulting .cf file. While I saw lines
referencing each dnsbl I included in the .mc, all of the error clauses
were missing.
My .mc file includes this line on both servers:
FEATURE(dnsbl, `bl.spamcop.net', `"550 Mail from " $&{client_addr} "
rejected, see http://spamcop.net/bl.shtml?"; $&{client_addr}')
On the FreeBSD 4.x server, this is the corresponding section in the .cf file:
# DNS based IP address spam list bl.spamcop.net
R$* $: $&{client_addr}
R$-.$-.$-.$-$: $(dnsbl $4.$3.$2.$1.bl.spamcop.net. $: OK $)
ROK $: OKSOFAR
R$+ $: TMPOK
R$+ $#error $@ 5.7.1 $: "550 Mail from "
$&{client_addr} " rejected, s
ee http://spamcop.net/bl.shtml?"; $&{client_addr}
On the FreeBSD 8.x server, this is the corresponding section:
# DNS based IP address spam list bl.spamcop.net
R$* $: $&{client_addr}
R$-.$-.$-.$-$: $(dnsbl $4.$3.$2.$1.bl.spamcop.net. $: OK $)
ROK $: OKSOFAR
R$+ $: TMPOK
Note that the last line (containing the "error" clause and custom 550
message) is absent from the new server's file.
I know next to nothing about m4, but I compared the cf/feature/dnsbl.m4
files on the two machines and noticed that the newer version has an
"ifelse" statement to handle 'quarantine' or 'discard' keywords that is
not present in the older version. I counted the arguments and compared
them to the documented behavior of "ifelse" and didn't see any glaring
problems, but the correct output string from the statement simply does
not appear in the .cf file.
Apparently this is the only case that causes the ifelse statement to
not produce any output. Omitting the custom error message, specifying
'discard' or specifying 'quarantine' all produce a suitable action line
in the output (error with default message, discard or quarantine,
respectively). So just specifying e.g. "FEATURE(dnsbl,
`bl.spamcop.net')" is one workaround.
Since I don't use the 'quarantine' or 'discard' keywords I doctored the
dnsbl.m4 file to remove the final "ifelse" statement and always output
the error clause. That allowed me to produce a .cf file which included
the appropriate error clauses and customized 550 error messages.
This is an issue on FreeBSD 7.2 and 8.1 (and probably -CURRENT, but I
don't have a test machine handy), but not on 4.9 (I know, old). For
kicks I tried substituting gm4 from ports for m4 in the base but got
the same results. I also verified that a simple macro containing an
"ifelse" statement with seven arguments works as expected, including
printing the seventh argument if both comparisons (1&2 and 4&5) are
false.
So--I'm stumped. I do have the workarounds I mentioned but now that
I've encountered this mystery I would like to see it solved. Can anyone
help unravel it?
Thanks,
JN
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Apparent dnsbl bug in Sendmail or m4
On Aug 22, 2010, at 6:40 AM, Stefan Bethke wrote:
> Am 22.08.2010 um 10:00 schrieb Stefan Bethke:
>
>> FEATURE(`dnsbl', `bl.spamcop.net', `"550 " $&{client_addr} "foo"
>> $&{client_addr} ""')dnl
>
> The real culprit is the comma. I believe the problem stems from unquoted use
> of the arguments in some of the ifelses, where the comma turns the single
> argument into two.
That makes a lot of sense, especially when combined with the off-list
suggestions I got to double-quote the error message.
> Tracing the ifelses with -d aceq I see this for the last ifelse in
> cf/feature/dnsbl.m4:
>
> m4trace: -1- ifelse(`X"550 Mail from " $&{client_addr} " rejected', `see
> http://spamcop.net/bl.shtml?"; $&{client_addr}', `Xquarantine', `R$+
> $#error $@ quarantine $: _DNSBL_SRV_', `X"550 Mail from " $&{client_addr} "
> rejected', `
> see http://spamcop.net/bl.shtml?"; $&{client_addr}', `Xdiscard', `R$+
>
> $#discard $: _DNSBL_SRV_', `R$+ $#error $@ 5.7.1 $:
> _DNSBL_MSG_'
> ) -> ???
> m4trace: -1- ifelse(...) -> `'
> m4trace: -1- ifelse ...
>
>
> I've never managed to really wrap my head around m4 quoting, but the easy fix
> is to use some other character that has no meaning to m4.
The fact that you knew how to do a trace shows that you're way ahead of me in
grokking m4. :) I can confirm that replacing the comma with a colon makes the
problem go away.
Does someone with some m4-fu want to take a stab at producing a fix? The
problem appears in the 7-arg "ifelse" in the last few lines of
/usr/share/sendmail/cf/feature/dnsbl.m4, though the source could of course be
missing quotes earlier in the file.
I'd be happy to test any proposed patches and submit a bug report to Sendmail
if appropriate. At the very least perhaps the example in the comment of
/etc/mail/freebsd.mc should be modified to not use a comma.
Thanks!
JN
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Apparent dnsbl bug in Sendmail or m4
It was pointed out to me that the example in freebsd.mc has been double-quoted
for some time. That's what I get for carrying old config files around for too
long I suppose. Sorry for the noise and thanks again all for the prompt replies.
On Aug 22, 2010, at 3:48 PM, John Nielsen wrote:
> On Aug 22, 2010, at 6:40 AM, Stefan Bethke wrote:
>
>> Am 22.08.2010 um 10:00 schrieb Stefan Bethke:
>>
>>> FEATURE(`dnsbl', `bl.spamcop.net', `"550 " $&{client_addr} "foo"
>>> $&{client_addr} ""')dnl
>>
>> The real culprit is the comma. I believe the problem stems from unquoted
>> use of the arguments in some of the ifelses, where the comma turns the
>> single argument into two.
>
> That makes a lot of sense, especially when combined with the off-list
> suggestions I got to double-quote the error message.
>
>> Tracing the ifelses with -d aceq I see this for the last ifelse in
>> cf/feature/dnsbl.m4:
>>
>> m4trace: -1- ifelse(`X"550 Mail from " $&{client_addr} " rejected', `see
>> http://spamcop.net/bl.shtml?"; $&{client_addr}', `Xquarantine', `R$+
>> $#error $@ quarantine $: _DNSBL_SRV_', `X"550 Mail from " $&{client_addr}
>> " rejected', `
>> see http://spamcop.net/bl.shtml?"; $&{client_addr}', `Xdiscard', `R$+
>>
>> $#discard $: _DNSBL_SRV_', `R$+ $#error $@ 5.7.1 $:
>> _DNSBL_MSG_'
>> ) -> ???
>> m4trace: -1- ifelse(...) -> `'
>> m4trace: -1- ifelse ...
>>
>>
>> I've never managed to really wrap my head around m4 quoting, but the easy
>> fix is to use some other character that has no meaning to m4.
>
> The fact that you knew how to do a trace shows that you're way ahead of me in
> grokking m4. :) I can confirm that replacing the comma with a colon makes the
> problem go away.
>
> Does someone with some m4-fu want to take a stab at producing a fix? The
> problem appears in the 7-arg "ifelse" in the last few lines of
> /usr/share/sendmail/cf/feature/dnsbl.m4, though the source could of course be
> missing quotes earlier in the file.
>
> I'd be happy to test any proposed patches and submit a bug report to Sendmail
> if appropriate. At the very least perhaps the example in the comment of
> /etc/mail/freebsd.mc should be modified to not use a comma.
>
> Thanks!
>
> JN
>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Build Broken: /usr/src/usr.bin/netstat/inet.c
On Jan 4, 2011, at 3:40 PM, Dan Allen wrote: > I just did a csup of stable, and the build is broken. > > In function protopr various struct members are not defined. The build halts. > > First compile error is at /usr/src/usr.bin/netstat/inet.c line 462 Me too. It seems r216964 is the culprit. See my response on the SVN lists. JN___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: em interface slow down on 8.0R
On Dec 5, 2009, at 4:40 AM, Hiroki Sato wrote: Hiroki Sato wrote in <20091203.182931.129751456@allbsd.org>: hr> And another thing, I noticed a box with 82573E and 82573L sometimes hr> got stuck after upgrading to 8.0-STABLE. It has moderate network hr> load (average 5-10Mbps) on both NICs. It worked for a day or two and hr> then got stuck suddenly. Rebooting the box solved the situation, but hr> it got stuck again after a day or so. After it happens, the hr> interface does not respond. The other functionalities of FreeBSD hr> seemed working. Doing an up/down cycle for the NICs seemed to send hr> some packets, but it did not recover completely; rebooting was needed hr> for recovery. This box does not have the RTT problem. I am still hr> not sure what is the trigger, there seems something wrong. Things turned out for this symptom so far are: - This occurs around once per 1-2 days. - Once it occurs, all of communications including ARP and IPv4 stop. - "ifconfig em0 down/up" can recover the interface. However, on doing "up" after "down" the following message was displayed: # ifconfig em0 up em0: Could not setup receive structures After trying it several times it worked. Then, the interface seemed back to normal for a couple of minutes, but it stopped again. I guess there is a kind of deadlock somewhere but not sure it is really related to the em(4) driver. I will continue to investigate anyway. I'm curious, what speed/duplex is your interface using and is it statically set or using autoselect? JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: newbie question about NFS
Read the exports(5) manpage. Its format is different on FreeBSD than it is on Linux. (rw) isn't valid. Pay particular attention to the section about "maproot". "In the absence of -maproot and -mapall options, remote accesses by root will result in using a credential of -2:-2." So if you mounted the directory as root on the client side then you were given no permissions. Either add a "-maproot=root" flag to your exports line (insecure) or change the ownership on the server to be a different user and mount as that user on the client. JN Quoting geek <[EMAIL PROTECTED]>: I am using FreeBSD 6.2. I am trying to export a directory so that another machine can read and write to it. With an /etc/exports file that says: /Data 192.168.1.20(rw) I get an empty directory on the client machine. I know that there are files in the directory. They show when I list the contents on the FreeBSD machine. If I leave off the (rw), then the contents of the directory are visible. But the documents are read only. What am I doing wrong here? Thanks to all for any help. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: is there any raid5 in software in FreeBSD ?
On Tuesday 19 February 2008 07:51:32 pm Joe Peterson wrote: > Nenhum_de_Nos wrote: > > i've seen RAID 0 through 3 (skip 2 ;) ) > > > > thanks, > > ZFS has RAIDZ - very similar to RAID5 (with added features), if you > don't mind ZFS's current experimental state. gvinum supports RAID5, but is a bit more complicated than g[mirror|stripe| raid3]. There is also an experimental graid5 module but last I heard it was a long way from being ready to commit and it doesn't seem to have much momentum (although FreeNAS uses it). If/when I get around to buying more disks for my home server I'll be using ZFS. YMMV. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ggated vs iscsi
On Thursday 06 March 2008 04:53:55 pm Pete French wrote: > I want to take a disc partition on one box and make it available to > another box to be mounted. Under 7.0 it looks like I have a choice > of using either ggated to do this, or the new iscsis initiator. Does > anyone have any opinions on what is most reliable ? Instyinct says > iscsi as I have used that in the past, but I havent used the new > initiator yet. Any advice ? Keep in mind that with ggate you'll need ggated on the exporting machine and ggatec on the other. Likewise with iSCSI you'll need the a _target_ (such as the one in net/iscsi-target) and an initiator, which you get in the base system starting with FreeBSD 7. Last time I used it the iscsi-target port had some significant bugs, but looking through cvs it looks like those may have been addressed. I can't really speak to performance. Reliability should be all right as long as you don't have frequent network issues. Ggate takes a bit of tweaking and system tuning to get to work right, but works pretty well once you get there. It has the advantage of being very simple to configure and in that regard it might be a good match for your 1:1 exporter/importer setup (although iSCSI isn't that complex, and it sounds like you've used it before). Performance is generally good. Reliability is fair in my experience as long as the network is solid. I don't think ggate does any kind of automatic reconnect (unlike iSCSI), but I've seen simple setups go for months without a hiccup. My best advice would be to try both at least briefly. Do some performance testing, see what happens when you unplug the network (or simulate other interruptions), etc. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ggated vs iscsi
On Friday 07 March 2008 11:25:39 am Pete French wrote: > > Last time I used it the iscsi-target port had some significant bugs, > > but looking through cvs it looks like those may have been addressed. > > I can't really speak to performance. Reliability should be all right > > as long as you don't have frequent network issues. > > Thanks for the warning - do you have any refernces for these bugs ? I > have been using the iscsi-target for a while and never come across > anything problematic, but I havent really hammered it hard as yet. These two (related) PR's are one starting point. Both are closed/fixed. :) http://www.freebsd.org/cgi/query-pr.cgi?pr=117015 http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/117690 There was an e-mail thread about some (possibly the same) issues as well but I can't find it now. In any case it looks like my experience is out of date and the latest version of the port has seen some beneficial updates. > Am currently playing around with using gmirror on a pair of iscsi > drives mounted using iscsi_initiator/iscsi-target and it seems to > work rather nicely actually. Reconnest if I disconnect a drive, > performance is O.K., and it appears to behave itself. I would rather > use ZFS on top, but I am not sure I *quite* trust it yet after some of > the comments on here and my own expeineces, so gmirror it is for now. As long as the rebuild time is okay for you then this is a likely a good way to go. Between iscsi, zfs, and all the geom tools there are a LOT of options for storage in FreeBSD these days. With more people adopting 7 the remaining kinks will hopefully get worked out of the former two in short order. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ggated vs iscsi
On Friday 07 March 2008 10:08:59 am Ivan Voras wrote: > John Nielsen wrote: > > On Thursday 06 March 2008 04:53:55 pm Pete French wrote: > >> I want to take a disc partition on one box and make it available to > >> another box to be mounted. Under 7.0 it looks like I have a choice > >> of using either ggated to do this, or the new iscsis initiator. Does > >> anyone have any opinions on what is most reliable ? Instyinct says > >> iscsi as I have used that in the past, but I havent used the new > >> initiator yet. Any advice ? > > > > Keep in mind that with ggate you'll need ggated on the exporting > > machine and ggatec on the other. Likewise with iSCSI you'll need the > > a _target_ (such as the one in net/iscsi-target) and an initiator, > > which you get in the base system starting with FreeBSD 7. > > According to at least two reports, iSCSI initiator in 7.0-RELEASE is > buggy and has problems that manifest in very low performance. There are > patches for it which should be committed soon. > > See this thread: > http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003383.ht >ml I remember the thread (and the patch). Is there a PR for this or did you or someone else just pick it up directly? JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: BTX on USB pen drive
On Friday 07 March 2008 09:13:12 am John Baldwin wrote: > On Thursday 06 March 2008 07:29:40 pm Daniel O'Connor wrote: > > On Fri, 7 Mar 2008, Vincent Mialon wrote: > > > I tested various options in boot0cfg with no sucess. I also tested > > > the howto from > > > http://typo.submonkey.net/articles/2006/04/13/installing-freebsd-on > > >-u sb-stick-episode-2 with a 6.3 FreeBSD release which boots on my > > > pc but doesn't boot on my supermicro server. > > > > > > Do you have any idea or pointer that may help me find the way to > > > boot this usb drive ? I may file a bug report if you want. > > > > I wanted to make a USB flash drive based installer for FreeBSD but > > unfortunately BTX seems to have issues that make it difficult to do > > reliably :( > > > > Here are 2 patches I tried.. > > http://people.freebsd.org/~kib/realbtx > > http://people.freebsd.org/~jhb/patches/btx_crx.patch > > Try this instead: > > http://people.freebsd.org/~jhb/patches/btx_real.patch > > (btx_crx has been in the base system for a while FWIW). This is > somewhat similar to kib's patch but fixes at least one bug I found in > kib's patch (and uses some slightly different approaches in a few > places). I have a laptop that does the BTX register-spin thing when booting from USB even if I use Grub, so I'll give your patch a try. The first hunk doesn't apply cleanly on today's 7-STABLE sources--the new page tables entry at line 29 throws it off. I applied that hunk manually and am rebuilding now. FWIW the laptop is an Intel-based Gateway M465-E, and it boots from (internal) CD just fine. I don't currently have space or a partition on the internal hard drive for a FreeBSD install, hence the USB stick. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: BTX on USB pen drive
On Friday 07 March 2008 02:18:42 pm John Nielsen wrote: > On Friday 07 March 2008 09:13:12 am John Baldwin wrote: > > On Thursday 06 March 2008 07:29:40 pm Daniel O'Connor wrote: > > > On Fri, 7 Mar 2008, Vincent Mialon wrote: > > > > I tested various options in boot0cfg with no sucess. I also > > > > tested the howto from > > > > http://typo.submonkey.net/articles/2006/04/13/installing-freebsd- > > > >on -u sb-stick-episode-2 with a 6.3 FreeBSD release which boots on > > > > my pc but doesn't boot on my supermicro server. > > > > > > > > Do you have any idea or pointer that may help me find the way to > > > > boot this usb drive ? I may file a bug report if you want. > > > > > > I wanted to make a USB flash drive based installer for FreeBSD but > > > unfortunately BTX seems to have issues that make it difficult to do > > > reliably :( > > > > > > Here are 2 patches I tried.. > > > http://people.freebsd.org/~kib/realbtx > > > http://people.freebsd.org/~jhb/patches/btx_crx.patch > > > > Try this instead: > > > > http://people.freebsd.org/~jhb/patches/btx_real.patch > > > > (btx_crx has been in the base system for a while FWIW). This is > > somewhat similar to kib's patch but fixes at least one bug I found in > > kib's patch (and uses some slightly different approaches in a few > > places). > > I have a laptop that does the BTX register-spin thing when booting from > USB even if I use Grub, so I'll give your patch a try. The first hunk > doesn't apply cleanly on today's 7-STABLE sources--the new page tables > entry at line 29 throws it off. I applied that hunk manually and am > rebuilding now. > > FWIW the laptop is an Intel-based Gateway M465-E, and it boots from > (internal) CD just fine. I don't currently have space or a partition on > the internal hard drive for a FreeBSD install, hence the USB stick. Success! I was able to boot my laptop from my USB stick built with the btx_real patch (after I modified hunk 1 to work with the 7-STABLE sources). Using the same stick on a different (Acer) laptop I was able to get farther in the boot than previously--it won't even boot from a standard CD, but with the stick it got to the menu (and THEN did a btx register dump, but it didn't loop/scroll). In case anyone (like Torfinn) is interested, I'm attaching my modified patch. If you already applied jhb's patch then you should be able to just cut out the first hunk from mine and apply it. JN --- sys/boot/i386/btx/btx/btx.S.orig2006-12-06 12:45:35.0 -0500 +++ sys/boot/i386/btx/btx/btx.S 2008-03-07 17:48:24.0 -0500 @@ -21,10 +21,11 @@ .set MEM_BTX,0x1000 # Start of BTX memory .set MEM_ESP0,0x1800# Supervisor stack .set MEM_BUF,0x1800 # Scratch buffer - .set MEM_ESP1,0x1e00# Link stack - .set MEM_IDT,0x1e00 # IDT - .set MEM_TSS,0x1f98 # TSS - .set MEM_MAP,0x2000 # I/O bit map + .set MEM_ESPR,0x5e00# Real mode stack + .set MEM_IDT,0x5e00 # IDT + .set MEM_TSS,0x5f98 # TSS + .set MEM_MAP,0x6000 # I/O bit map + .set MEM_TSS_END,0x7fff # End of TSS .set MEM_DIR,0x4000 # Page directory .set MEM_TBL,0x5000 # Page tables .set MEM_ORG,0x9000 # BTX code @@ -49,7 +50,6 @@ */ .set TSS_ESP0,0x4 # PL 0 ESP .set TSS_SS0,0x8# PL 0 SS - .set TSS_ESP1,0xc # PL 1 ESP .set TSS_MAP,0x66 # I/O bit map base /* * System calls. @@ -57,10 +57,20 @@ .set SYS_EXIT,0x0 # Exit .set SYS_EXEC,0x1 # Exec /* - * V86 constants. + * Fields in V86 interface structure. */ - .set V86_FLG,0x208eff # V86 flag mask - .set V86_STK,0x400 # V86 stack allowance + .set V86_CTL,0x0# Control flags + .set V86_ADDR,0x4 # Int number/address + .set V86_ES,0x8 # V86 ES + .set V86_DS,0xc # V86 DS + .set V86_FS,0x10# V86 FS + .set V86_GS,0x14# V86 GS +/* + * V86 control flags. + */ + .set V86F_ADDR,0x1 # Segment:offset address + .set V86F_CALLF,0x2 # Emulate far call
Re: BTX on USB pen drive
On Saturday 08 March 2008 04:29:25 pm Torfinn Ingolfsen wrote: > On Sat, 08 Mar 2008 16:11:54 -0500 > > John Nielsen <[EMAIL PROTECTED]> wrote: > > Success! I was able to boot my laptop from my USB stick built with > > the btx_real patch (after I modified hunk 1 to work with the 7-STABLE > > sources). Using the same stick on a different (Acer) laptop I was > > Interesting. Which Acer model is that? > The laptop I have troubles booting from usb is an Acer Aspire 5672. > I boot from an usb hard drive, not a memory stick, but that shouldn't > make a matter, right? I wouldn't think so. The Acer here (an Aspire 5520) won't even boot from the internal CD with a regular ISO install disk. I haven't tried any other approaches except for the USB stick with jhb's patch earlier today. > > able to get farther in the boot than previously--it won't even boot > > from a standard CD, but with the stick it got to the menu (and THEN > > did a btx register dump, but it didn't loop/scroll). > > > > In case anyone (like Torfinn) is interested, I'm attaching my > > modified patch. If you already applied jhb's patch then you should be > > able to just cut out the first hunk from mine and apply it. > > Thanks. > I already used the latest revision (1.45) of btx.S and applied jhb's > patch to that. Unfortunately, it didn't work. See another message in > this thread. Am I correct in thinking that your modified patch wouldn't > help me? Correct. (unless the unpatched version from -HEAD introduced a regression, but I think they're pretty similar). JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: BSD 6 or 7 + Intel 3200 MCH chipset
On Tuesday 25 March 2008 09:19:00 pm Dave Overton wrote: > Just put together a nice 1U box, Tyan Tank GT20, plugged in its 8gb ECC > RAM, its 4 shiney new HDs and fired it up. Bios looks normal, reset > the clock to something resembling today, and throw in the Fbsd7 disk! > > No joy. > > I get just a hint of a "booting" line, then an instant reboot, or with > a 6 disk, I get a scrolling mess that I have no idea what it says. Partly guessing, but this sounds like the real-mode BTX bootloader issue. It's become increasingly common on newer hardware, and it's not limited to USB devices like it used to be. Fortunately, there is a good chance that jhb's recent BTX overhaul will fix it. Unfortunately, it was only committed to -CURRENT two weeks ago and MFC'ed to RELENG_6 and RELENG_7 one week ago so I doubt there's a ready-to-use snapshot CD you can download that includes it. If it were me I'd create a bootable USB stick (on another machine) to verify that you can boot the server with the latest boot blocks, then use it to do a manual install (or at least bootstrap the process). But that's just me--I like that sort of thing. It's also possible to roll your own installation CD but I've never done.it. I do recall someone posting an link to an image to one of the mailing lists, but IIRC that was with a BTX patch older than the one that actually got committed. Probably someone else on this list has a better suggestion. JN > My question, has anyone got fbsd running on one of these chipsets? If > so, how did you do it? Tried 7 release in i386 and amd64 version, and > v6 i386. They all do the same thing. > > (it will run the misc test CDs I have here just fine, even let it do > most of a WinXP install with no issues, so I don't really believe it to > be a hardware issue) > > Tyan Tank GT20 model B5211 > Tyan Toledo i3200R m/b > Intel 3200 MCH chipset. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Adding device to FreeBSD 6.3-STABLE
On Friday 01 August 2008, Jack Raats wrote: > I would like to add the zyd device to FreeBSD. > The zyd driver allready is in FreeBSD 7.0. > Which steps do I have to take to add the zyd device to FreeBSD? Sorry, what are you asking? What version of FreeBSD are you using and what do you need help doing? JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: iSCSI boot driver 0.2.5 (isboot.ko) has been released.
On Aug 21, 2012, at 11:43 PM, Daisuke Aoyama wrote: > You can download the source file from: > http://www.peach.ne.jp/archives/isboot/isboot-0.2.5.tar.gz > ... Daisuke-san- Thank you for this great work! I can see a lot of potential applications for it. I set up a test machine and got as far as booting the FreeBSD 10-CURRENT kernel from an istgt LUN, but it failed to find the root device--the isboot.ko module loaded fine but the iBFT handoff didn't happen so the network was not configured early enough. This machine has an sk(4) NIC, and I am chain-loading gPXE using the "undionly.kpxe" image. I have a few questions for you (or other knowledgeable people on the list): 1) Does iBFT require hardware support in the NIC? 2) Does iBFT require NIC driver support? 3) Is anything required in loader.conf besides isboot_load="YES"? 3) How hard would it be to get this working with sk(4)? 4) Is it likely to work (better) if I find an em(4) card instead? Thanks, JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Updated isboot 0.2.6 and FreeBSD 9.1-RC1
Thank you for the quick response! On Aug 23, 2012, at 6:25 PM, Daisuke Aoyama wrote: > It seems a bug of isboot. Your NIC is link down, but isboot never retry > on first connection. Because of this, it failed to find the boot device. > > I have updated isboot and created 9.1-RC based image. > Please try it: > > http://www.peach.ne.jp/archives/isboot/isboot-0.2.6.tar.gz Working great with the new version of the module. It retries 3-4 times until the link comes up then continues. Performing pretty well, too--this is over a 1Gbps LAN on somewhat dated consumer hardware, with istgt and a ZFS zvol on the other end. > http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-9.1-RC1-amd64-memstick-isboot-0.2.6.img > >> I have a few questions for you (or other knowledgeable people on the list): >> 1) Does iBFT require hardware support in the NIC? >> 2) Does iBFT require NIC driver support? > > NO. You can use both iBFT software like gPXE and NIC's rom like Intel iSCSI > boot agent. > The isboot should work with any NIC supported by FreeBSD. Fantastic. >> 3) Is anything required in loader.conf besides isboot_load="YES"? > > If your NIC driver is within the kernel, you need only isboot_load="YES". > >> 4) Is it likely to work (better) if I find an em(4) card instead? > > I have tested with Intel cards/onboard. If you want the maximum performance, > I recommend you to use Intel card, but other cards should work with isboot. I'll stick with what I have for this machine since it's working. In case you're interested, here is the dmesg output from the machine: mptable_probe: MP Config Table has bad signature: 4\^C\^_ Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #2 r239337M: Fri Aug 24 12:58:51 EDT 2012 r...@stealth.jnielsen.net:/usr/obj/i386.i386/usr/src/sys/BUFF i386 CPU: AMD Athlon(tm) XP 2800+ (2079.60-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x6a0 Family = 6 Model = a Stepping = 0 Features=0x383fbff AMD Features=0xc0400800 real memory = 1342177280 (1280 MB) avail memory = 1300516864 (1240 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 4fef (3) failed cpu0: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x73 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 Correcting nForce2 C1 CPU disconnect hangs agp0: on hostb0 pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 nfsmb0: port 0xd800-0xd81f irq 23 at device 1.1 on pci0 smbus0: on nfsmb0 nfsmb1: on nfsmb0 smbus1: on nfsmb1 ohci0: mem 0xe5085000-0xe5085fff irq 20 at device 2.0 on pci0 usbus0 on ohci0 ohci1: mem 0xe5081000-0xe5081fff irq 21 at device 2.1 on pci0 usbus1 on ohci1 ehci0: mem 0xe5082000-0xe50820ff irq 22 at device 2.2 on pci0 usbus2: EHCI version 1.0 usbus2 on ehci0 pci0: at device 5.0 (no driver attached) pcm0: port 0xdc00-0xdcff,0xe000-0xe07f mem 0xe5086000-0xe5086fff irq 21 at device 6.0 on pci0 pcm0: pcib1: at device 8.0 on pci0 pci1: on pcib1 skc0: port 0x9000-0x90ff mem 0xe402-0xe4023fff irq 17 at device 4.0 on pci1 skc0: Marvell Yukon Lite Gigabit Ethernet rev. A3(0x7) sk0: on skc0 sk0: Ethernet address: 00:11:2f:57:f4:bf miibus0: on sk0 e1000phy0: PHY 0 on miibus0 e1000phy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto pci1: at device 7.0 (no driver attached) ath0: mem 0xe401-0xe401 irq 18 at device 8.0 on pci1 [ath] enabling AN_TOP2_FIXUP ath0: DMA setup: legacy ath0: [HT] enabling HT modes ath0: [HT] 2 RX streams; 2 TX streams ath0: AR9220 mac 128.2 RF5133 phy 13.0 ath0: 2GHz radio: 0x; 5GHz radio: 0x00c0 atapci0: port 0x9400-0x9407,0x9800-0x9803,0x9c00-0x9c07,0xa000-0xa003,0xa400-0xa40f mem 0xe4024000-0xe40241ff irq 18 at device 11.0 on pci1 ata2: at channel 0 on atapci0 ata3: at channel 1 on atapci0 atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 9.0 on pci0 ata0: at channel 0 on atapci1 ata1: at channel 1 on atapci1 fwohci0: <1394 Open Host Controller Interface> mem 0xe5083000-0xe50837ff,0xe5084000-0xe508403f
Re: time issues and ZFS
On Jan 22, 2013, at 2:40 AM, Adrian Chadd wrote: > On Jan 21, 2013, at 4:33 AM, Daniel Braniss wrote: > >> host: DELL PowerEdge R710, 16GB, I administer a Dell PowerEdge R710 and I've been seeing the exact same thing. It's currently running FreeBSD 9.0-STABLE #0 r236355. It has a ZFS pool which sees moderate load most of the time but can be very high at times (when certain scripts run, etc.). I hadn't previously correlated the issue with ZFS load but that is very possible. I set a cron job to restart ntpd when it dies (because the time difference exceeds the sanity check). The cron job runs "every 20 minutes", but that varies greatly when the system stops counting. The time offset from ntpdate (which the script runs before restarting ntpd) varies a lot, but always in increments of 300 seconds. I've seen everything from 1200 to 23100. (Yes, that's 23 thousand seconds aka 6 hours 25 minutes that the system wasn't keeping time for.) Sysctl kern.timecounter.hardware defaults to HPET. I experimented with setting it to ACPI-fast but the issue persisted so I put it back. kern.timecounter.choice: TSC-low(-100) ACPI-fast(900) HPET(950) i8254(0) dummy(-100) I first installed the box with an older 9.0-STABLE and this issue was not present. I have been tracking -STABLE on it (albeit irregularly) so I'm not sure when the issue came up. > Have you run tests with the machdep.idle value changed, and fiddling > kern.eventtimer.periodic / kern.eventtimer.idletick ? I would love to resolve this and am able to do some experimenting. I've _usually_ been seeing the issue 2-3 times every 1-2 days, but I did just make some changes: disabling ZFS compression and deduplication on all pools updated to 9.1-STABLE from yesterday (r245821) If the issue persists I will try changing some of the sysctls above and follow up with the result. If it goes away, I'll try to remember to report that too. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: countdown from 31: helping with the FAQ
Cherry-picking a few: [install-PLIP] Has anyone used PLIP successfully on a currently-supported version of FreeBSD? (or any version since 4.x?) The last I remember hearing about it was Julian Stacey saying it didn't work in 2007. JHB has made http://lists.freebsd.org/pipermail/freebsd-hackers/2007-June/020820.html http://lists.freebsd.org/pipermail/freebsd-current/2007-December/081123.html I think I still have a laplink cable but I don't think I've used it since the 90's. That said, it was a nice feature, especially before CD's, USB and standard (or any) Ethernet interfaces were ubiquitous on laptops. If it works at all the FAQ should be fine; if it doesn't the docs should be updated to either remove the FAQ or include a caveat. [win95-connection] This is a bit dated but fine. The natd Handbook page could maybe reference other ways of doing NAT besides natd--e.g. using pf or ipfw. The IPFW Handbook page could be updated and simplified to include e.g. "firewall_nat_enable" instead of using divert/natd. [nfs-linux] Looks fine. Possibly less of an issue than it used to be but I do remember encountering that issue. [bpf-not-configured] Looks fine. [icmp-response-bw-limit] Looks fine, the sysctls haven't changed. JN On Jan 26, 2013, at 1:00 PM, Eitan Adler wrote: > Hey all, > > I've been working for past several months on improving the FAQ. At > the moment there are 31 unreviewed questions. > > Can you all help out by commenting on the yellow questions here: > https://wiki.freebsd.org/ThwackAFAQ - once the review stage is done > we could continue fixing the red ones! > > -- > Eitan Adler > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Virtio and GEOM labels
On Mar 22, 2013, at 8:14 AM, Paul Mather wrote: > I'm running FreeBSD 9-STABLE as a guest under RHEL 6.4 KVM virtualisation. I > have networking and storage in the FreeBSD guest using the Virtio drivers > (with the virtual disk set to "Virtio" in the definition on the host). > Everything is working nicely: I have a vtnet network adapter and see vtbd > devices for my virtual disks in FreeBSD. Performance is much better compared > with an emulated IDE device. I've had the same experience. > The odd thing is that I don't see GEOM labels reflected in /dev. For > example, I have GPT labels defined in the guest, but I don't see them show up > under /dev/gpt. Similarly, my UFS labels don't show up under /dev/ufs. I > *do* see a /dev/gptid. That appears to be the only label that shows up. I have not encountered this issue. I use virtio block devices and GPT labels exclusively in multiple FreeBSD 9.1 guests and all mount/function without issue. How are you referring to your filesystems in /etc/fstab? IIRC GEOM makes not-in-use labels disappear when a device is in use (e.g. mounted). If you take a new device, put a labeled GPT partition on it and a labeled UFS partition on that but don't mount anything, what happens? > Is there something special I need to do to get GPT and UFS labels to appear > when using Virtio? It seems to me that Virtio block devices appear to be > somewhat unusual. Unlike regular ATA and SCSI devices, my vtbd devices don't > appear in the boot dmesg (although a vtblk device does), and "camcontrol > devlist" does not list them. It's not clear to me how I am supposed to > interact with them other than via basic device I/O through /dev/vtbdX. I > thought that the virtio_scsi module might make them appear as "da" devices > and able to interacted with via camcontrol, but this doesn't seem to be the > case. Virtio block devices and virtio SCSI devices are not the same. If you want to use the virtio_scsi module in FreeBSD you should expose a virtio SCSI device from the host. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS LZ4 Upgrade
On Jun 3, 2013, at 12:52 PM, Kenta Suzumoto wrote: > Hi. I'm planning on doing a ZFS root installation on a remote server very > soon. The company only offers a 9.0 and 9.1 installation and "rescue" > (nfs/pxe boot with ramdisk basically) system. I'd like to use LZ4 with the > ZFS root pool, so I'm going to be upgrading to -STABLE once I have the > initial system installed. Here's what I'll do: > > - install the 9.1 system > - svn source, buildworld/kernel, install, reboot > - upon booting the -STABLE system, begin enabling LZ4 compression on > /usr/ports /usr/src etc. > > Will this work, or do I need to find some way to initially create the zpool > with a -STABLE system? Is it just a matter of running "zfs upgrade" and > "zpool upgrade" before enabling LZ4, or am I missing something? Thanks That should work. Just keep in mind that blocks written before you enable compression won't be compressed. So you may want to create a _new_ ZFS for src (and ports if it already exists as well) after your source upgrade, then copy the contents of /usr/src over to it. (Then update the mountpoints as desired, etc.) JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: request for your comments on release documentation
On Jun 12, 2013, at 11:49 AM, Hiroki Sato wrote: > I would like your comments on release notes for each release. > Although I have been working on editing them for years, the workflow > is still not optimal and sometimes delay of the preparation became an > obstacle for release process. I would like to improve it, but before > that I would like to know what are desired of the contents which > people think. > > Release Notes is just listing the changes between the two releases. > It includes user-visible change (bugfix and/or UI change), new > functionality, and performance improvement. Minor changes such as > one in kernel internal structure are omitted. I always try to keep > these series of relnotes items are correct and reasonably > comprehensive, but this lengthy list may be boring and > technically-correct descriptions can be cryptic for average users. > > So, my questions are: > > 1. What do you think about current granularity of the relnotes items? >Too detailed, good, or too rough? Currently, judgment of what is >included or not is based on user-visible, new functionality, or >performance improvement. Applicable changes are included as >relnotes items even if the changes are small, I think the current granularity is good. > 2. Do you want technical details? For example, just "disk access >performance was improved by 50%" or "Feature A has been added. >This changes the old behavior because ..., and as a result, it >improves disk access performance by 50%". I want technical details. You could compromise here by trying to always have the non-technical end result in the first sentence or so, and then go on with a more technical explanation. I would echo Mark Felder and say that if in doubt, more detail is better. > 3. Is there missing information which should be in the relnotes? >Probably there are some missing items for each release, but this >question is one at some abstraction level. Link to commit log and >diff, detailed description of major incompatible changes, and so >on. I've not ever noticed any. Thanks! I'm on the SVN mailing lists so I tend to know about or be able to find changes I care about independent of the release notes. However if there is a mostly-automated way to link to specific commits in the release notes that could be valuable. > Although the other release documentations---Errata, Installation > Notes, ReadMe, and Hardware Notes---also need some improvements, > please focus on Release Notes only. And you might think quality of > English writing are not good, please leave that alone for now. I've never noticed any language problems in the release notes, and I tend to be a stickler. :) JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Getting going with a new Dell 7810
On Jun 16, 2015, at 12:39 PM, Ronald Klop wrote: > What does 'sysctl kern.vty' say? If it is not 'vt', you need the following > stuff. > > /boot/loader.conf should contain > kern.vty="vt" > > And /etc/rc.conf > kld_list="radeonkms" > > Or something similar. > > FreeBSD is in the transition of old-style syscons- and vt-terminal. The last > one has support for modern KMS graphics, but is not the default on 10 yet. With UEFI boot it will be using vt but with the efifb driver by default. Hopefully loading the radeon KMS driver (as Ronald suggests above) will let it take over. Try it with just a “kldload radeonkms” before adding it to rc.conf, just in case something gets wedged.. > On Tue, 16 Jun 2015 18:55:10 +0200, Richard Kuhns wrote: > >> Greetings all, >> >> I've just received a new Dell Precision 7810. I've installed FreeBSD >> 10.1 (UEFI boot), checked out sources, built world & kernel and am now >> running r284449. So far, so good. >> >> The problem is Xorg. I'm running the latest Xorg in ports; I just did a >> 'make install clean' in /usr/ports/x11/xorg with no errors. >> >> The display card is a FirePro W4100. lspci shows: >> >> 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. >> [AMD/ATI] Cape Verde GL [FirePro W4100] >> >> It has 4 DisplayPorts, and I have 2 monitors plugged in. If I run 'Xorg >> -configure' it says >> >> Number of created screens does not match number of detected devices. >> Configuration failed. >> >> Looking through /var/log/Xorg.0.log it appears that the X server is >> trying to use the RADEON driver, but ends with: >> >> = >> [ 1292.463] (--) Using syscons driver with X support (version 2.0) >> [ 1292.463] (--) using VT number 9 >> >> [ 1292.485] (II) [KMS] Kernel modesetting enabled. >> [ 1292.485] (WW) Falling back to old probe method for vesa >> [ 1292.485] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card >> support >> [ 1292.485] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32 >> [ 1292.485] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 >> bpp pixmaps) >> [ 1292.485] (==) RADEON(0): Default visual is TrueColor >> [ 1292.485] (==) RADEON(0): RGB weight 888 >> [ 1292.485] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC) >> [ 1292.485] (--) RADEON(0): Chipset: "VERDE" (ChipID = 0x682c) >> [ 1292.579] (EE) RADEON(0): [drm] Failed to open DRM device for >> pci::03:00.0: No such file or directory >> [ 1292.579] (EE) RADEON(0): Kernel modesetting setup failed >> [ 1292.579] (II) UnloadModule: "radeon" >> [ 1292.579] (EE) Screen(s) found, but none have a usable configuration. >> [ 1292.579] (EE) >> Fatal server error: >> [ 1292.579] (EE) no screens found(EE) >> [ 1292.580] (EE) >> Please consult the The X.Org Foundation support >> at http://wiki.x.org >> for help. >> [ 1292.580] (EE) Please also check the log file at >> "/var/log/Xorg.0.log" for additional information. >> [ 1292.580] (EE) >> [ 1292.580] (EE) Server terminated with error (1). Closing log file. >> >> >> Should I be able to use this video card? I've done some googling, and >> apparently at least some Linux people are using it. >> >> It's not a huge deal if it doesn't work; I can install a Radeon HD 4670 >> that I know works. If I've mis-configured something, though, I'd like to >> fix it. >> >> Thanks for any comments! > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
/dev/crypto not being used in 12-STABLE
I have upgraded two physical machines from 11-STABLE to 12-STABLE recently (one is 12.0-PRERELEASE r341380 and the other is 12.0-PRERELEASE r341391). I noticed today that neither machine seems to be utilizing /dev/crypto. Typically I see at least ssh/sshd have the device open plus some programs from ports. But 'fuser' doesn't list any processes on either machine: # fuser /dev/crypto /dev/crypto: Both machines are running custom kernels that include "device crypto" and "device cryptodev". One of them additionally has "device aesni". Is anyone else seeing this? Any idea what would cause it? Thanks, JN ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: /dev/crypto not being used in 12-STABLE
> On Dec 6, 2018, at 4:04 PM, Xin LI wrote: > > On Thu, Dec 6, 2018 at 11:37 AM John Nielsen wrote: >> >> I have upgraded two physical machines from 11-STABLE to 12-STABLE recently >> (one is 12.0-PRERELEASE r341380 and the other is 12.0-PRERELEASE r341391). I >> noticed today that neither machine seems to be utilizing /dev/crypto. >> Typically I see at least ssh/sshd have the device open plus some programs >> from ports. But 'fuser' doesn't list any processes on either machine: >> >> # fuser /dev/crypto >> /dev/crypto: >> >> Both machines are running custom kernels that include "device crypto" and >> "device cryptodev". One of them additionally has "device aesni". >> >> Is anyone else seeing this? Any idea what would cause it? > > Your average OpenSSL applications should not use /dev/crypto, if your > goal is to utilize AES-NI (which does not require /dev/crypto). On > capable systems, AES-NI would be used automatically (and it's faster > this way). Thanks for the response. Is there a way to verify that AES-NI is being used for e.g. ssh? I'm also curious why/when/how the change to not use (or support?) /dev/crypto from base openssl was made. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: /dev/crypto not being used in 12-STABLE
> On Dec 6, 2018, at 4:39 PM, John Baldwin wrote: > > On 12/6/18 3:24 PM, John Nielsen wrote: >>> On Dec 6, 2018, at 4:04 PM, Xin LI wrote: >>> >>> On Thu, Dec 6, 2018 at 11:37 AM John Nielsen wrote: >>>> >>>> I have upgraded two physical machines from 11-STABLE to 12-STABLE recently >>>> (one is 12.0-PRERELEASE r341380 and the other is 12.0-PRERELEASE r341391). >>>> I noticed today that neither machine seems to be utilizing /dev/crypto. >>>> Typically I see at least ssh/sshd have the device open plus some programs >>>> from ports. But 'fuser' doesn't list any processes on either machine: >>>> >>>> # fuser /dev/crypto >>>> /dev/crypto: >>>> >>>> Both machines are running custom kernels that include "device crypto" and >>>> "device cryptodev". One of them additionally has "device aesni". >>>> >>>> Is anyone else seeing this? Any idea what would cause it? >>> >>> Your average OpenSSL applications should not use /dev/crypto, if your >>> goal is to utilize AES-NI (which does not require /dev/crypto). On >>> capable systems, AES-NI would be used automatically (and it's faster >>> this way). >> >> Thanks for the response. Is there a way to verify that AES-NI is being used >> for e.g. ssh? I'm also curious why/when/how the change to not use (or >> support?) /dev/crypto from base openssl was made. > > I suspect it was something we just didn't test in the flurry of other work > during the OpenSSL upgrade. I did wonder about that. :) > However, it is much faster to use the AES-NI > instructions in userland than to use a system call that copies the data > into a kernel buffer, uses the sames AES-NI instructions, then copies the > data back out again along with the overhead of a pair of user <--> kernel > transitions. If you have an actual crypto offload device (as in a PCI-e > card or something), then you might be interested in /dev/crypto (and we > should fix that eventually), but AES-NI is just faster software crypto and > is best done directly in userland. That makes sense and explains some other comments I was just reading. Is aesni(4) even required if all you want is userland acceleration? ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: iSCSI initiator tester wanted
Quoting Danny Braniss <[EMAIL PROTECTED]>: I'm in the last mile before crossing the beta->release line, so I'd like to get some input, and update the list of targets it supports. you can obtain the driver from: ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.0.92.tar.gz Looks great! I've done some basic testing against our cluster of three LeftHand Networks NSM 160's running SAN/iQ 6.6SP1. My machine is running -CURRENT as of a couple days ago (with gcc 4.2 and symbol versioning). I've tested previous snapshots of the driver against the same SAN on this and another machine running -STABLE with good results. Is there anything specific you'd like tested? What connection interruption scenarios does the driver try to recover from? I'm running some backups to an iSCSI mount now. When that finishes (and my machine is otherwise unoccupied) I'll play around with temporarily yanking the ethernet cable and other fun tricks. Thanks for the Makefiles. Your blurb text incorrectly directs the reader to run make in sys/dev/iscsi_initiator (which doesn't exist, and there's no Makefile in sys/dev/iscsi). Obviously you meant sys/modules/iscsi_initiator. Also, a line about running make in iscontrol/ would be helpful, as would an install target in that Makefile. Do you have any suggestions on startup integration (rc script, fstab magic, etc)? I know you said once before that that was hopefully coming soon.. Thanks again. I'll post again if I manage to break something. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: iSCSI initiator tester wanted
Quoting Danny Braniss <[EMAIL PROTECTED]>:
Quoting John Nielsen <[EMAIL PROTECTED]>:
Do you have any suggestions on startup integration (rc script, fstab
magic, etc)? I know you said once before that that was hopefully coming
soon..
this is an attempt:
A couple comments just from reading through this, see below.
#!/bin/sh
# PROVIDE: iscsi
# REQUIRE: NETWORKING
# BEFORE: DAEMON
# KEYWORD: nojail shutdown
#
# Add the following lines to /etc/rc.conf to enable iscsi:
#
# iscsi_enable="YES"
# iscsi_fstab="/etc/fstab.iscsi"
The iscsi_exports knob should also be documented here.
. /etc/rc.subr
name=iscsi
rcvar=`set_rcvar`
command=/usr/local/sbin/iscontrol
Assuming this gets commited this will want to be /sbin/iscontrol.
iscsi_enable=${iscsi_enable:-"NO"}
iscsi_fstab=${iscsi_fstab:-"/etc/fstab.iscsi"}
iscsi_exports=${iscsi_exports:-"/etc/exports.iscsi"}
start_cmd="iscsi_start"
faststop_cmp="iscsi_stop"
stop_cmd="iscsi_stop"
iscsi_wait()
{
dev=$1
trap "echo 'wait loop cancelled'; exit 1" 2
count=0
while true; do
if [ -c $dev ]; then
break;
fi
if [ $count -eq 0 ]; then
echo -n Waiting for ${dev}': '
fi
count=$((${count} + 1))
if [ $count -eq 6 ]; then
echo ' Failed'
return 0
break
fi
echo -n '.'
sleep 5;
done
echo '.'
return 1
}
iscsi_start()
{
#
# load needed modules
for m in iscsi_initiator geom_label; do
kldstat -qm $m || kldload $m
done
Good thinking making geom_label a pseudo-requirement. Examples and
documentation for fstab.iscsi should strongly recommend its use, since
device names will vary.
sysctl debug.iscsi=2
Maybe make this another rc variable that could be set in /etc/rc.conf.
You'll probably also want to change the module's default verbosity
level once it becomes more official.
#
# start iscontrol for each target
if [ -n "${iscsi_targets}" ]; then
for target in ${iscsi_targets}; do
${command} ${rc_flags} -n ${target}
done
fi
if [ -f "${iscsi_fstab}" ]; then
while read spec file type opt t1 t2
do
case ${spec} in
\#*|'')
;;
*)
if iscsi_wait ${spec}; then
break;
fi
echo type=$type spec=$spec file=$file
fsck -p ${spec} && mount ${spec} ${file}
;;
esac
done < ${iscsi_fstab}
fi
if [ -f "${iscsi_exports}" ]; then
cat ${iscsi_exports} >> /etc/exports
#/etc/rc.d/mountd reload does not work, why?
kill -1 `cat /var/run/mountd.pid`
fi
}
Look at how Pawel handled this with ZFS (mostly in the zfs and mountd
rc.d scripts), and use the fact that mountd can take multiple exports
files on its command line to your advantage. i.e. appending to the
normal exports file is not really what you want to do.
iscsi_stop()
{
echo 'iscsi stopping'
while read spec file type opt t1 t2
do
case ${spec} in
\#*|'')
;;
*)
echo iscsi: umount $spec
umount -fv $spec
# and remove from the exports ...
See above; this could be a no-op.
;;
esac
done < ${iscsi_fstab}
}
load_rc_config $name
run_rc_command "$1"
--
problems with the above script:
- no background fsck
It would be nice not to re-invent the wheel here, and there are other
reasons it would be nice to just use /etc/fstab instead of adding a new
file -- a number of utilities use /etc/fstab to map between mountpoints
and device names even if the device isn't mounted. Did you try this
approach, and if so what obstacles did you encounter? I will play
around with this if I have time. The "late" fstab/mount option will
probably be useful here.
- restart will mess the exports file
- the wait loop should be replaced by something more deterministic.
JN
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: iSCSI initiator tester wanted
Quoting Ivan Voras <[EMAIL PROTECTED]>: Danny Braniss wrote: I'm in the last mile before crossing the beta->release line, so I'd like to get some input, and update the list of targets it supports. you can obtain the driver from: ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.0.92.tar.gz I think I can test in on our SAN but the only machine attached to it runs 6-STABLE. Will your iSCSI intiator work in -STABLE? This is actually the first snapshot of the initiator that I've tried that works on -CURRENT. Previous ones have always worked on -STABLE and I don't see any reason that this one wouldn't. Also, do you plan to finish it in time to get it included in 7.0? I can't comment on that, but I agree it would be nice.. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gmirror on 7B4
Quoting "Chris H." <[EMAIL PROTECTED]>: Quoting "Chris H." <[EMAIL PROTECTED]>: Hello, I seem to remember a similar question being asked in the past. But never ---8<---snip---8<--- I had originally intended to create a raid mirror on the whole lot of HD's during the install process. But I wasn't presented, nor could I find that option during install. So, due to lack of time, pushed it off till later, and simply installed onto the one HD. Now to my question(s)... Where is the option to create, and install to a gMIRRORED drive-set? ---8<---snip---8<--- 2) In my cases above, I'm interested in RAID-0 (mirroring for /volume/ not redundancy). OK, my mistake... Seems for my application (RAID0), *gstripe* is what I should be using. Q: But RAID0 provides 0 redundancy. How will you cope with data loss? A: Complete backups occur twice daily and I (we) use IP RAID0 - eg; 2 different servers have/provide the same data, and the DNS provides "round-robin". Thereby spreading the requests roughly equal across both servers. So, given my new found knowledge. I felt I should probably ask before potentially clobbering (breaking) the server I'll be attempting this on. Will the following accomplish my goal? Current setup: /dev indicates the following: da0, da0c, da0cs1, da0s1, da0s1c da1, da1c, da1cs1, da1s1, da1s1c da2, da2c, da2cs1, da2s1, da2s1c ...and the following, which FreeBSD is installed on: da3, da3s1, da3s1a, da3s1b, da3s1c, da3s1d All drives are of same size/make/model. Given the above, I intend to issue the following: # gstripe label -v -s 131072 bigstripe \ /dev/da0 /dev/da1 /dev/da2 /dev/da3 # newfs -U /dev/stripe/bigstripe # mount /dev/stripe/bigstripe /bigstripe # echo 'geom_stripe_load="YES"' >> /boot/loader.conf # echo '/dev/stripe/bigstripe /bigstripe ufs rw 2 2' >> /etc/fstab Yes, this should be fine (though you may need to do a "gstripe load" near the beginning). Or do/should I issue: # gconcat label -v extradisks /dev/da0 /dev/da1 /dev/da2 # gstripe label -v bigstripe /dev/da3 /dev/concat/extradisks # bsdlabel -wB /dev/stripe/bigstripe # newfs -U /dev/stripe/bigstripe # mount /dev/stripe/bigstripe /bigstripe No, assuming the disks are (roughly) the same size there's no reason to use gconcat, and in this case doing so will likely hurt performance in addition to adding complexity. gconcat is generally just for JBOD-type scenarios and it sounds like you're after RAID0 which is what gstripe is for. JN Thank you for all your time and consideration. Chris P.S. I know this is a bit noisy. I intend to keep it brief. Thank you for your understanding. :) -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gmirror on 7B4
I'm not sure I remember everything from earlier in this thread so I don't know if it's relevant, BUT you can't boot from a gstripe volume (or from a gconcat one AFAIK). Inferring from your fstab example below it doesn't sound like you intend to but I just wanted to be sure. Quoting John Nielsen <[EMAIL PROTECTED]>: Quoting "Chris H." <[EMAIL PROTECTED]>: Quoting "Chris H." <[EMAIL PROTECTED]>: Hello, I seem to remember a similar question being asked in the past. But never ---8<---snip---8<--- I had originally intended to create a raid mirror on the whole lot of HD's during the install process. But I wasn't presented, nor could I find that option during install. So, due to lack of time, pushed it off till later, and simply installed onto the one HD. Now to my question(s)... Where is the option to create, and install to a gMIRRORED drive-set? ---8<---snip---8<--- 2) In my cases above, I'm interested in RAID-0 (mirroring for /volume/ not redundancy). OK, my mistake... Seems for my application (RAID0), *gstripe* is what I should be using. Q: But RAID0 provides 0 redundancy. How will you cope with data loss? A: Complete backups occur twice daily and I (we) use IP RAID0 - eg; 2 different servers have/provide the same data, and the DNS provides "round-robin". Thereby spreading the requests roughly equal across both servers. So, given my new found knowledge. I felt I should probably ask before potentially clobbering (breaking) the server I'll be attempting this on. Will the following accomplish my goal? Current setup: /dev indicates the following: da0, da0c, da0cs1, da0s1, da0s1c da1, da1c, da1cs1, da1s1, da1s1c da2, da2c, da2cs1, da2s1, da2s1c ...and the following, which FreeBSD is installed on: da3, da3s1, da3s1a, da3s1b, da3s1c, da3s1d All drives are of same size/make/model. Given the above, I intend to issue the following: # gstripe label -v -s 131072 bigstripe \ /dev/da0 /dev/da1 /dev/da2 /dev/da3 # newfs -U /dev/stripe/bigstripe # mount /dev/stripe/bigstripe /bigstripe # echo 'geom_stripe_load="YES"' >> /boot/loader.conf # echo '/dev/stripe/bigstripe /bigstripe ufs rw 2 2' >> /etc/fstab Yes, this should be fine (though you may need to do a "gstripe load" near the beginning). Or do/should I issue: # gconcat label -v extradisks /dev/da0 /dev/da1 /dev/da2 # gstripe label -v bigstripe /dev/da3 /dev/concat/extradisks # bsdlabel -wB /dev/stripe/bigstripe # newfs -U /dev/stripe/bigstripe # mount /dev/stripe/bigstripe /bigstripe No, assuming the disks are (roughly) the same size there's no reason to use gconcat, and in this case doing so will likely hurt performance in addition to adding complexity. gconcat is generally just for JBOD-type scenarios and it sounds like you're after RAID0 which is what gstripe is for. JN Thank you for all your time and consideration. Chris P.S. I know this is a bit noisy. I intend to keep it brief. Thank you for your understanding. :) -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- panic: kernel trap (ignored) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gmirror on 7B4
Quoting "Chris H." <[EMAIL PROTECTED]>: Quoting John Nielsen <[EMAIL PROTECTED]>: I'm not sure I remember everything from earlier in this thread so I don't know if it's relevant, BUT you can't boot from a gstripe volume (or from a gconcat one AFAIK). Inferring from your fstab example below it doesn't sound like you intend to but I just wanted to be sure. Are you sure? I read that using gmirror requires /kernel to be located in the /boot slice and everything else (all other slices) can be mirrored safely. But in all my reading (man pages, FBSD handbook, asstd articles) I haven't seen anything indicating booting wasn't possible from a gstripe volume. Yes, I'm sure. In order to bootstrap the system, the BIOS needs to know how to read the operating system from the disk. FreeBSD's own loader also relies on BIOS calls for disk reads until the kernel is loaded and executed. When using a hardware RAID controller its own BIOS runs before the OS boot so it can handle disk I/O from the RAID volumes it knows about. When using purely software RAID such as gstripe, the computer knows nothing about any volumes, it just knows about the individual disks. If you tell it to boot from disk 1, it will try to boot from disk one and then choke since it will only get at most 1 stripe's worth of contiguous useful data (the next stripe being stored on a different disk). For gmirror this doesn't matter, since an individual disk can be used to load the kernel without any knowledge of RAID volumes. Nothing needs can write to the disk until init mounts the root partition read-write (presumably using gmirror) so the volume integrity is not affected. The simplest (IMO, although knowledge of fdisk, bsdlabel, newfs and what boot blocks go where may be required, along with using dump/restore on occasion) approach is to make / its own small partition on a gmirror volume and then create gstripe (or whatever) volumes from the remainder of the disks for the rest of the mountpoints. That means you'll be handing slices or partitions to gmirror, gstripe and friends rather than whole raw disks, but that's okay. It is possible to have only /boot on the actual boot device/partition (with the rest of / elsewhere) but in this scenario that just adds complexity. Most of the few hundred MB that / typically requires are in /boot anyway. If you want specific advice for a specific scenario you can probably get it, but you'll have to supply some additional details. For instance I'm still not sure if this is a new install or an upgrade (even after re-reading the entire thread), or if da3 is the same size as da0-2. Doing what you describe below will blow away the existing contents of da3 and the other disks, and/or won't be allowed if anything on da3 is currently mounted/running. Also you should stop saying mirror if you mean stripe or JBOD. :) JN For the record, FSTAB (on da3): /dev/da3s1b none (swap) /dev/da3s1a / /dev/da3s1d /var Thanks for your response. Chris Quoting John Nielsen <[EMAIL PROTECTED]>: Quoting "Chris H." <[EMAIL PROTECTED]>: Quoting "Chris H." <[EMAIL PROTECTED]>: Hello, I seem to remember a similar question being asked in the past. But never ---8<---snip---8<--- I had originally intended to create a raid mirror on the whole lot of HD's during the install process. But I wasn't presented, nor could I find that option during install. So, due to lack of time, pushed it off till later, and simply installed onto the one HD. Now to my question(s)... Where is the option to create, and install to a gMIRRORED drive-set? ---8<---snip---8<--- 2) In my cases above, I'm interested in RAID-0 (mirroring for /volume/ not redundancy). OK, my mistake... Seems for my application (RAID0), *gstripe* is what I should be using. Q: But RAID0 provides 0 redundancy. How will you cope with data loss? A: Complete backups occur twice daily and I (we) use IP RAID0 - eg; 2 different servers have/provide the same data, and the DNS provides "round-robin". Thereby spreading the requests roughly equal across both servers. So, given my new found knowledge. I felt I should probably ask before potentially clobbering (breaking) the server I'll be attempting this on. Will the following accomplish my goal? Current setup: /dev indicates the following: da0, da0c, da0cs1, da0s1, da0s1c da1, da1c, da1cs1, da1s1, da1s1c da2, da2c, da2cs1, da2s1, da2s1c ...and the following, which FreeBSD is installed on: da3, da3s1, da3s1a, da3s1b, da3s1c, da3s1d All drives are of same size/make/model. Given the above, I intend to issue the following: # gstripe label -v -s 131072 bigstripe \ /dev/da0 /dev/da1 /dev/da2 /dev/da3 # newfs -U /dev/stripe/bigstripe # mount /dev/stripe/bigstripe /bigstripe # echo 'geom_stripe_load="YES&
Re: gstripe on 7B4 - was: gmirror on 7B4
Quoting "Chris H." <[EMAIL PROTECTED]>: If you want specific advice for a specific scenario you can probably get it, but you'll have to supply some additional details. For instance I'm still not sure if this is a new install or an upgrade Both: I was wondering why gmirror wasn't an option during sysinstall (the creation, and installation to). Which begged the question - now that it's installed... (even after re-reading the entire thread), or if da3 is the same size as da0-2. Doing what you describe below will blow away the existing contents of da3 and the other disks, and/or won't be allowed if anything on da3 is currently mounted/running. Also you should stop saying mirror if you mean stripe or JBOD. :) Quite right. Again, my bad. I'm sorry this became so convoluted. It seemed so clear at first. But as it started a question about gmirror, and my almost immediate discovery that gmirror doesn't do RAID0, as I required. Turned it into gstripe. I thought I had managed to make the transition smoothly. But as you effectively indicated, no dice. Sorry. :( Thank you *very* much for your informative, and thoughtful replies - and patience. :) OK, in the final analysis I've decided (now that it's (7B4) installed...) I'll just keep /boot, /root (and presumably /dev) on the already available and running install disk (da3). Then perform: # gstripe label -v -s 131072 bigstripe \ /dev/da0 /dev/da1 /dev/da2 # newfs -U /dev/stripe/bigstripe # mkdir /bigstripe # mount /dev/stripe/bigstripe /bigstripe # echo 'geom_stripe_load="YES"' >> /boot/loader.conf # echo '/dev/stripe/bigstripe /bigstripe ufs rw 2 2' >> /etc/fstab Good up to here. Now you still have your running system and existing partitions on da3, and a new empty large raid0 volume mounted on /bigstripe. Before continuing, you should ask yourself (and perhaps tell the rest of us) what exactly do you want to use all of that space for? da3 is probably large enough for the OS itself, and while it's not redundant at least you have better odds of not losing your OS if a drive fails with this setup. # cd /var # tar cf - . | (cd /bigstripe; tar xvf - and repeating the above two lines for /bin, /compat, /dist, /entropy, /etc, /lib, /libexec, /media, /mnt, /proc, /rescue, /sbin, /sys, /tmp, and /usr That will get your files moved, but what are you trying to accomplish here? moving and remaking /home. Then deleting and re-creating the above (/bin, /compat, etc...). How do you propose to re-create them if they've been moved to a different filesystem? At best you can create symlinks to them which will usually work, but in this case I don't see a reason to go that route. Then modify /etc/fstab to read /dev/stripe/bigstripe / ufs rw 2 2 And this is the big question mark/red flag. If you get rid of da3 then you won't be able to boot, and if you're keeping it anyway then why not use it? If you really want to do this you should use dump/restore instead of tar above and do the entire root filesystem (by which I mean "/" and not just "/root"), then be careful to always update /boot and /etc on da3 any time you update the system. Or in other words, you're asking for trouble. unmount /bigstripe That should be umount, although you should probably just reboot with the new fstab if that's what you really want. mount / Same as above. Done. Yes? Err.. Maybe I'm overestimating the FreeBSD file system. But this seems plausible. FreeBSD can handle it and you're definitely moving in the direction of a workable setup here, but you may have gotten a bit carried away. A better option might be to just move one mountpoint (such as /var) over to the stripe volume by using dump/restore, then update fstab so it gets mounted from the new location. If you want to move other directories (such as /tmp or /home or even /usr) to the new volume you can do so, you'll just need to create symlinks to their new locations. If this is or was a new install you may want to start over and re-do your partitioning with the end goal in mind (so you don't have unused space or partitions on da3, for instance). Thanks to everyones time, consideration (and patience). Sure. JN For the record, FSTAB (on da3): /dev/da3s1b none (swap) /dev/da3s1a / /dev/da3s1d /var Thanks for your response. Chris A *little* history, perhaps helps context... ---8<---snip---8<--- OK, my mistake... Seems for my application (RAID0), *gstripe* is what I should be using. Q: But RAID0 provides 0 redundancy. How will you cope with data loss? A: Complete backups occur twice daily and I (we) use IP RAID0 - eg; 2 different servers have/provide the same data, and the DNS provides "round-robin". Thereby spreading the requests roughly equal across both servers. So, given my new found knowledge. I felt I should probably ask before potentially clobbering (breaking) the server I'll be attempting this on. Will the following accomplish my goal? Current setup: /dev indic
Re: FreeBSD and iSCSI for disks.
On Thursday 09 April 2009 10:32:05 am Danny Braniss wrote:
> > Danny Braniss wrote:
> > >> This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
> > >> --enig90DADA8437A99D893FB775F8
> > >> Content-Type: text/plain; charset=3DUTF-8
> > >> Content-Transfer-Encoding: quoted-printable
> > >>
> > >> Danny Braniss wrote:
> > Garance A Drosihn wrote:
> > > Some friends of mine are looking at the new "DroboPro", which
> > > makes=
> >
> > a=3D
> >
> > > lot of disk space available via iSCSI (in addition to firewire
> > > 800)=
> >
> > ,
> >
> > > and they were wondering how well iSCSI works with FreeBSD. I
> > > haven=
> >
> > 't=3D
> >
> > > paid attention to iSCSI support. Is there anyone using it
> > > heavily for disk-storage under FreeBSD? Has there been much
> > > changed for iSCSI support in the 8.x branch, or is 7.x support
> > > working fine?
> >
> > I suppose you are interested in the "client" (initiator) side of
> > iSC=
> >
> > SI=3D
> >
> > support. It hasn't changed much between 7.x and 8.x but there
> > are apparently some announcements of a newer version:
> >
> > http://lists.freebsd.org/pipermail/freebsd-scsi/2009-March/00383
> > 4.ht=
> >
> > ml=3D
> >
> > I can't find any more information on it.
> > >>>
> > >>> the latest is in:
> > >>> http://www.cs.huji.ac.il/~danny/ftp/freebsd/iscsi-2.1.1.tar.gz
> > >>
> > >> Thanks!
> > >>
> > >> Is there anything in particular you'd like to get tested in the
> > >> new version, any significant changes or improvements?
> > >
> > > mainly fixed some bugs, and some code cleanup.
> > >=20
> > > give it a spin, and let me know what target you are testing.
> > > btw, the default tag opening is a bit concervative (1), you might
> > > want =
> >
> > to
> >
> > > change it to somewhat larger, say 64 or 128.
> >
> > Hi,
> >
> > "camcontrol tags" hangs:
> >
> > Apr 9 15:36:36 terminator kernel: da3 at iscsi0 bus 0 target 1 lun 0
> > Apr 9 15:36:36 terminator kernel: da3:
> > Fixed Direct Access SCSI-5 device
> > Apr 9 15:36:38 terminator kernel: (da2:iscsi0:0:0:0): lost device
> > Apr 9 15:36:38 terminator kernel: (da2:iscsi0:0:0:0): removing
> > device en= try
> > terminator:~ivoras/temp/sbin/iscontrol# ls /dev/da*
> > /dev/da0 /dev/da0s1 /dev/da0s1a /dev/da0s1b /dev/da0s1c
> > /dev/da1 /dev/da3
> > terminator:~ivoras/temp/sbin/iscontrol# camcontrol tags da3
> >
> >
> > The configuration is:
> >
> > target0 {
> > targetaddress =3D 161.53.72.65
> > targetname =3D iqn.2007-09.jp.ne.peach:disk1
> > tags =3D 16
> > }
>
> Q: what kernel?
From his previous message it looks like 7-STABLE amd64
> Q: what target?
From the targetname it looks like the recently committed net/istgt running
on another FreeBSD machine.
> btw, without the camcontrol tags, is it working?
That one I can't infer. :)
JN
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ZFS MFC heads up
On Thursday 21 May 2009 04:32:56 am Lorenzo Perone wrote: > * dancing around with loud music csupping all over the place... * I'll know I've been hacking too long when my music starts csupping all over the place.. :) Ditto though, huge thanks to Kip! JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
lagg(4) + VLAN + if_bridge(4) vs. ARP
Hi all- I'm trying to troubleshoot a problem on a machine running recent 10-STABLE. The machine has two physical interfaces and hosts a number of services, including a bhyve VM (FreeBSD 10.2-RELEASE) acting as a network appliance. The VM has three interfaces: external, internal-trusted and internal-guest. Each VM interface is plumbed to a TAP device on the host which in turn is a member of a bridge. Here is the current (working) setup: External <> Host <-> Host <-> Host <-> VM portre0 bridge2 tap21vtnet1 Switch <-> Host <-> Host <-> Host <-> Host <-> VM port em0 em0.2bridge0 tap20vtnet0 ^ \-> Host <-> Host <-> Host <-> VM em0.103 bridge1 tap22vtnet2 Since there is not much external traffic, most of the bandwidth potential of re0 is wasted while em0 is sometimes busy. So I'd like to move to a LAGG setup, as below: External Trusted Untrusted VLAN 99 VLAN 2 VLAN 103 | || \ | / /---\ /--> Host <--> Host <-> Host <-> VM | switch| |lagg0.99 bridge2 tap21vtnet1 \---/ | || | /---> Host <--> Host <-> Host <-> VM |v | | lagg0.2 bridge0 tap20vtnet0 | Hostv v \ re0 <-> Host <-> Host <--> Host <-> Host <-> VM \ lagg0lagg0.103 bridge1 tap22vtnet2 \-> Host ^ em0 <--/ So in other words, plugging the external port into the switch, creating a new "external" VLAN, adding both em0 and re0 into a new LAGG and creating VLAN child interfaces off of that. I tried the new setup today and it worked except that the VM no longer received ARP replies from the external network. Using tcpdump on the host's lagg0.99, I saw the ARP request from the VM go out and an ARP reply come back, but that's as far as it went. I did not see the arp reply on the host's bridge2 or tap21 interfaces, and the VM never received it. I didn't make any changes on the VM, and all I changed on the host was the networking via /etc/rc.conf. The host does run ipfw but I verified that none of the rules reference any stale interface names. I have also previously disabled all firewalling of bridged packets: net.link.bridge.pfil_onlyip=0 net.link.bridge.pfil_member=0 net.link.bridge.pfil_bridge=0 I also verified that "ifconfig bridge2 addr" contained the MAC addresses of both the VM and the external device on the correct ports. So in the LAGG setup, why aren't the ARP replies going across bridge2 to the VM? Any ideas on how to narrow down the cause appreciated. Thanks! -John Nielsen ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: lagg(4) + VLAN + if_bridge(4) vs. ARP
> On Jan 8, 2016, at 2:52 PM, John Nielsen wrote: > > I'm trying to troubleshoot a problem on a machine running recent 10-STABLE. > ... So in other words, plugging the external port into the switch, creating a > new "external" VLAN, adding both em0 and re0 into a new LAGG and creating > VLAN child interfaces off of that. > > ... > > So in the LAGG setup, why aren't the ARP replies going across bridge2 to the > VM? For the archives: this turned out to be operator error in the form of a MAC address conflict between the lagg0 interface on the host and the vtnet1 interface in the VM. JN ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Bind-9.10
> On Mar 29, 2016, at 12:57 PM, Peter Fraser wrote:
>
> Hi All
> Honestly, I am not sure if this post belongs over in a Bind Mailing List
> but I will ask just the same to see if anyone has seen this problem. I
> upgraded from Bind 9.9x to bind910-9.10.3P4 on FreeBSD-9.3-RELEASE-p33.
> During the installation from ports, I checked RRL(Response Rate Limiting)
> After the installation I checked and resolves are still working. I
> restarted the service and no errors. My problem now is that when I use the
> option rate-limit { responses-per-second 10; }; and reload bind I get the
> error, unknown option rate-limit. Has anyone ever seen this error?
I haven't run in to that, but something to check is whether your installation
of BIND was built with response rate limiting. The FreeBSD port has it enabled
by default, but it is a selectable option.
Two quick ways to check:
% pkg info bind910|grep RRL
RRL: on
% named -V
...
built by make with [...] '--enable-rrl' [...]
...
HTH,
JN
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Where is 10.2-STABLE?
> On Mar 30, 2016, at 5:04 PM, Ronald F. Guilmette > wrote: > > I was looking to download an ISO for 10.2-STABLE for a new build I'm > doing, however I can't see to locate any such ISO. It isn't where > it seems it should be, according to the info on this page: > > https://www.freebsd.org/snapshots/ > > Where can I get such an ISO? The release process for 10.3 is well underway, with 3 release candidates already shipped and release builds imminent or already started. So the latest ISOs for the equivalent of 10-STABLE are under releases/amd64/amd64/ISO-IMAGES/10.3 of your favorite FTP mirror. E.g.: http://ftp4.us.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/10.3/ Once the release is final and announced I'm sure that -STABLE snapshots will resume from the 10.3-STABLE branch. JN ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
MFC planned for src/sys/dev/wi/if_wi_pccard.c 1.59?
It looks like this one may have slipped through the cracks. I don't think there's any reason not to include support for the SMC 2532W-B in -STABLE's wi driver when all it needs is a reference to an existing definition. See this thread: http://groups.google.com/group/mailing.freebsd.mobile/browse_thread/thread/eca4d606f7165e65/fc59e639e1c4db4f?lnk=st&q=freebsd+wi+smc+2532w&rnum=2#fc59e639e1c4db4f And this commit: == Revision 1.59 / (download) - annotate - [select for diffs], Fri Oct 14 15:06:16 2005 UTC (13 months, 1 week ago) by imp Branch: MAIN CVS Tags: HEAD Changes since 1.58: +2 -0 lines Diff to previous 1.58 (colored) Add ELSA XI330 product. This is rebadged and sold as SMC 2532W-B and I/O Data also resells it. Add an alternative airvast an100 id. == The 1.58 commit seems to touch more than just the one file, but applying the 1.58->1.59 diff to the 1.57 file adds support for the cards above on 6-STABLE. Thanks, JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Any hosting companies offering FreeBSD 5.3 yet?
On Saturday 26 February 2005 06:38 pm, David J. Hughes wrote: > On 26/02/2005, at 7:28 PM, John Pettitt wrote: > > I'm thinking about moving one of my servers to a new home (it's > > currently at servepath.com on a FreeBSD 5.0 box) - does anybody know of > > a reputable hosting company that's offering 5.3 boxes? > > I know www.johncompanies.com will be offering 5.x soon. I've had a 4.x > jail with them for quite some time and am very happy with the service > and support. I second that. Their service is hands-down the best I've ever had for anything technology-related. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 5.3 freezes under heavy hdd load
On Monday 07 March 2005 09:38 am, cyb wrote: > from time to time my FreeBSD freezes under heavy hdd load and only a > hard reset will bring it back to life with fsck complaining about > 'Softupdate Inconsistencies'. I had similar issues on an Athlon machine under 5.3. In my case it turned out that the CPU was running extremely hot. It would frequently freeze while portupgrade was backing up old versions of a port. I initially suspected a disk problem as well, but I haven't yet had any problems since cleaning my CPU and chipset fans. On reflection, my freezes were probably due to the CPU running hotter than usual when running bzip2 (which I believe is how portupgrade stores its backups, and is very CPU-intensive). It is possible that your drive is the culprit, but you would probably get console messages about I/O failures rather than just a hard freeze. Flaky memory or power supply are also possibilities. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: does growfs actually work on -stable?
On Friday 29 December 2006 02:39, John Pettitt wrote: > I tried to grow a 600GB filesystem to 1TB and growfs barfed complaining > about a negative block number - this was a raid array (highpoint) that > looks like one drive (da0) to the system. Does growfs actually work - > google searches were not much help ... I used it successfully a couple months ago (6.1-STABLE most likely). IIRC, you need to resize the slice (fdisk) and the partition (bsdlabel) yourself before calling growfs. I think this was just on a standalone IDE disk. I don't recall the size details. HTH, JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.2 & nvidia x11 driver: weird 16bpp/24bpp colorspace damage
On Monday 15 January 2007 19:42, Daniel O'Connor wrote: > On Tuesday 16 January 2007 09:03, Patrick Reich wrote: > > Wishful thinking: Too bad there isn't an nvidia-driver-legacy port. > > It wouldn't be too much work to split the current port into 3 separate ones > for this purpose. > > Then you could send-pr and someone could commit it :) There's already a PR open (and assigned to danfe@) that recommends this approach (ports/107717) but doesn't include any patches. Actually doing the work would go a long way toward getting it committed. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fetchmail problem
On Tuesday 16 January 2007 23:51, Kris Kennaway wrote: > On Wed, Jan 17, 2007 at 05:13:16AM +0100, Par Leijonhufvud wrote: > > I have a FreeBSD box (running ancient 4.8) that used to collect email > > fine with fetchmail. Then after te latest portupgrade of fetchmail it > > stopped working. When trying to run it manual I see the error shown > > below. > > > > Anyone with suggestions as to (a) just what is going wrong, and (b) how > > to fix it? Another machine running 5.3 have no problems. > > Maybe the configuration options changed. Anyway, this kind of > question should be asked on the fetchmail support mailing lists since > it is not a problem with FreeBSD-stable itself. Or maybe -questions if it's related to a well-known port. Anyway, if it's been over a year since you've updated fetchmail then there are a whole bunch of entries in ports/UPDATING you should read. The problem you're probably running into (along with a possible workaround) is mentioned in the 20051210 entry. There are other more recent entries as well. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gmirror disks vs partitions
On Wednesday 17 January 2007 06:29, Andrew Pantyukhin wrote: > On 1/17/07, Josef Karthauser <[EMAIL PROTECTED]> wrote: > > A poll for opinions if I may? > > > > I've got a few gmirrors running on various machines, all of which > > pair up two drives at the physical level (i.e. mirror /dev/ad0s1 > > with /dev/ad1s1). Of course there are other ways of doing it to, > > like mirroring at the partition level, ie pairing /dev/ad0s1a with > > /dev/ad1s1a, /dev/ad0s1e with /dev/ad0s1e, etc. > > > > Apart from potentially avoiding a whole disk from being copied > > during a resync after a crash, are there any other advantages to > > using partition level mirroring instead of drive level mirroring? > > I can imagine people using partition-level raid to > implement a popular configuration: > > You divide a couple of identical drives proportionally > in two partitions each, place a couple of the first > partitions into gmirror and a couple of the second > ones into gstripe. This way you get both reliable and > fast storage with just two drives. Some strings are > attached. The reduced likelihood of needing to rebuild a given volume is usually enough of an argument for me to mirror at the partition level. Of course, the other side of the coin is that if more than one volume on a given pair of disks needs to be rebuilt, the disks will be twice (or more) as hammered (and less efficient due to the greater number of seeks) during the rebuild(s). If you want to be creative/exotic then it's sometimes useful to use partitions as building blocks for odd (or "advanced") volume configurations. For instance, let's say you're trying to get some disk redundancy for your workstation but you're limited to whatever drives you can scrounge up. (Have _I_ ever been in this position? nah... :) ) You have a 40GB disk, a 60GB disk, and an 80GB disk. If you partition them up right and use gmirror with gstripe, it's possible to use all of the space and still be able to survive the failure of any one disk. Divide everything up into partitions of equal sizes. For an even number of disks you can use the GCD of the sizes as the partition size, but since there's an odd number of disks in this example we'll use GCD/2 or ~10GB. Pair one partition on the 40GB disk with one on the 60GB disk. Then pair all of the partitions on the 80GB disk with the remaining partitions on the 40 and 60 GB disks. Make each pair into a gmirror volume. If you need to boot from the array, pick one pair to be your system volume. The rest of the gmirrors can all be added into a gstripe volume, so you end up with 90GB (or 80+10) of redundant storage with quite good performance (not that I would know, of course). You can use the leftover bits for swap, etc. The two drawbacks to this approach vs a two-disk mirror are increased likelihood of drive failure (due to the greater number of disks) and a more complex recovery procedure if a drive fails (especially if you don't have a spare identical to or slightly larger than the one that failed). Just some thoughts.. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portdowngrade/portupgrade question
On Wednesday 17 January 2007 01:51, Torfinn Ingolfsen wrote: > On Wed, 17 Jan 2007 06:24:23 +0100 > > Par Leijonhufvud <[EMAIL PROTECTED]> wrote: > > How do I tell portupgrade that I *know*, just go ahead anyway? > > Is it 'portupgrade -f ' you want? There's always the traditional cd /usr/ports/sysutils/portdowngrade && make install clean Portupgrade can figure it out later (pkgdb -F). JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Removing unused core components. (Disabled in make.conf)
On Wednesday 17 January 2007 13:52, Victor Snezhko wrote: > Tom Judge <[EMAIL PROTECTED]> writes: > > Hi, > > > > I have the following options in /etc/make.conf: > > > > NO_PROFILE=true > > NO_SENDMAIL=true > > NO_GAMES=true > > NO_I4B=true > > NO_ATM=true > > NO_INET6=true > > NO_BLUETOOTH=true > > NO_IPFILTER=true > > NO_RCMDS=true > > NO_KERBEROS=true > > > > > > However after a "make buildworld installworld" the utilities and libs > > associated with these packages are still installed, is there any easy > > way to remove them from the system? > > make delete-old That will delete obsolete files no longer used by the current version of the operating system, but it won't do what the OP is asking. I don't know of a one-step way to do what you're asking. You could do a find over the base system directories and look for files older than your last installworld. That might not fit the "easy" part of the request since you'd have to go over the list manually to make sure it wasn't killing anything you actually need, but it should be mostly accurate. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Removing unused core components. (Disabled in make.conf)
On Wednesday 17 January 2007 14:29, John Nielsen wrote:
> On Wednesday 17 January 2007 13:52, Victor Snezhko wrote:
> > Tom Judge <[EMAIL PROTECTED]> writes:
> > > Hi,
> > >
> > > I have the following options in /etc/make.conf:
> > >
> > > NO_PROFILE=true
> > > NO_SENDMAIL=true
> > > NO_GAMES=true
> > > NO_I4B=true
> > > NO_ATM=true
> > > NO_INET6=true
> > > NO_BLUETOOTH=true
> > > NO_IPFILTER=true
> > > NO_RCMDS=true
> > > NO_KERBEROS=true
> > >
> > >
> > > However after a "make buildworld installworld" the utilities and libs
> > > associated with these packages are still installed, is there any easy
> > > way to remove them from the system?
> >
> > make delete-old
>
> That will delete obsolete files no longer used by the current version of
> the operating system, but it won't do what the OP is asking.
>
> I don't know of a one-step way to do what you're asking. You could do a
> find over the base system directories and look for files older than your
> last installworld. That might not fit the "easy" part of the request since
> you'd have to go over the list manually to make sure it wasn't killing
> anything you actually need, but it should be mostly accurate.
Here's a script I just put together to get a good first approximation of
outdated files using the approach above. Change the variables to be
appropriate for your situation, review the output file carefully before
deleting anything, and use at your own risk. :)
=== start prune.sh ===
#!/bin/sh
DIRS="/bin /lib /libexec /rescue /sbin /usr/bin /usr/games /usr/lib \
/usr/libdata /usr/libexec /usr/sbin"
OUTFILE=/usr/local/scripts/prune-files.txt
AGE="1 month"
rm -f ${OUTFILE}
for d in ${DIRS} ; do
find ${d} -type f ! -newermt "${AGE} ago" >> ${OUTFILE}.tmp
done
grep -vF "lib/compat" ${OUTFILE}.tmp | grep -vi perl > ${OUTFILE}
rm -f ${OUTFILE}.tmp
=== end prune.sh ===
JN
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
wireless + ndis on Compaq TC1000 revisited
This is a bit of a followup to my post of over a year ago: http://lists.freebsd.org/pipermail/freebsd-stable/2005-November/020289.html I've been playing with FreeBSD on the TC1000 Tablet PC again lately and brought it up to 6-STABLE. Compaq still has the same (Windows) drivers for the built-in wlan device as they did the last time, and it still doesn't work with ndis (ndisgen succeeds but the module causes a panic when it is loaded). However today I was able to locate an alternate driver for the card on one of the "secondhand" Windows driver websites. It's an NDIS 5.1 driver that works with my hardware under Windows XP, but it doesn't seem terribly modern (it comes with its own utility for setting the wireless settings). Under FreeBSD, ndisgen produced a module without any problem, and this one _doesn't_ case a panic when loaded. And it only sometimes causes a panic when trying to configure the interface (possibly just a race condition at boot). I'm now able to configure the interface and see it associate on both ends. When I attempt to get a DHCP lease, the DHCP server sees the request and sends an offer but the tablet never receives it for some reason. So it seems I can send (on Layer 2 at least) but not receive. Layer 3 doesn't work in either direction, presumably because the tablet never gets any ARP replies. I'm wondering if anyone has any experience with similar situations and/or ideas for workarounds or troubleshooting strategies (or even vague theories). The files I'm using are netvnpci.inf and pcifvnet.sys--a "FastVNET PCI 11M Network Adapter driver" from ATMEL. I'm more than happy to provide additional info if needed. Thanks, JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wireless + ndis on Compaq TC1000 revisited
On Saturday 03 February 2007 02:05, John Nielsen wrote: > This is a bit of a followup to my post of over a year ago: > > http://lists.freebsd.org/pipermail/freebsd-stable/2005-November/020289.ht >ml > > I've been playing with FreeBSD on the TC1000 Tablet PC again lately and > brought it up to 6-STABLE. Compaq still has the same (Windows) drivers > for the built-in wlan device as they did the last time, and it still > doesn't work with ndis (ndisgen succeeds but the module causes a panic > when it is loaded). > > However today I was able to locate an alternate driver for the card on > one of the "secondhand" Windows driver websites. It's an NDIS 5.1 driver > that works with my hardware under Windows XP, but it doesn't seem > terribly modern (it comes with its own utility for setting the wireless > settings). > > Under FreeBSD, ndisgen produced a module without any problem, and this > one _doesn't_ case a panic when loaded. And it only sometimes causes a > panic when trying to configure the interface (possibly just a race > condition at boot). > > I'm now able to configure the interface and see it associate on both > ends. When I attempt to get a DHCP lease, the DHCP server sees the > request and sends an offer but the tablet never receives it for some > reason. So it seems I can send (on Layer 2 at least) but not receive. > Layer 3 doesn't work in either direction, presumably because the tablet > never gets any ARP replies. > > I'm wondering if anyone has any experience with similar situations and/or > ideas for workarounds or troubleshooting strategies (or even vague > theories). The files I'm using are netvnpci.inf and > pcifvnet.sys--a "FastVNET PCI 11M Network Adapter driver" from ATMEL. In case anyone's interested (Milan O, are you out there?), I got this working (for basic values of "working"). I didn't actually get anywhere with the NDIS 5.1 (WinXP) driver, but I can send _and_ receive using the NDIS 5.0 (Win2k) driver. The driver is a pseudo-ethernet driver (from the days before Windows had 802.11 support) so it has some warts, but working is better than not, IMO. I actually had the same problem with this one as I did with the other one (could send but not receive) until I disabled usbd. No idea why that matters, but running usbd definitely makes the driver stop receiving packets. This might be related to the issues I was having with the XP driver, but the same workaround (disabling usbd) didn't have any effect with that one. For anyone who might want to do the same thing, here's what I did: Download Atmeldrivers.zip (9.7M) from DriverGuide.com (registration required). Extract and go to the "USB Adapter/Driver and Utility/Drivers/PCI/win982k" directory. Run ndisgen using NETVNpci.INF and pcifvnet.sys. Copy the resultant pcifvnet_sys.ko into /boot/modules. Add 'pcifvnet_sys_load="YES"' to /boot/loader.conf. Add 'ifconfig_ndis0="DHCP"' to /etc/rc.conf. Create an /etc/rc.early file with contents similar to this: #!/bin/sh sysctl dev.ndis.0.ESSID="myssid" ifconfig ndis0 up sleep 5 Apply the attached patch to src/sys/dev/if_ndis/if_ndis.c, then rebuild and reinstall the ndis and if_ndis modules. This might be optional (not 100% sure), but without it you'll get lots of complaints about unknown ethernet speeds. The patch just tells the driver to treat all the wireless speeds as 10baseT. Reboot. I'm not sure if setting the ESSID is necessary or even useful, since the card will associate fine without it. I also don't know if or how well WEP works using the registry-key sysctls. I'm still open to thoughts on why the WinXP driver wouldn't work or why this one only works without usbd, but I'm probably done messing with it for a little while at least. JN --- if_ndis.c.orig Sat Feb 3 15:51:11 2007 +++ if_ndis.c Sat Feb 3 17:23:27 2007 @@ -2007,6 +2007,18 @@ case 10: ifmr->ifm_active |= IFM_10_T; break; + case 1: + ifmr->ifm_active |= IFM_10_T; + break; + case 2: + ifmr->ifm_active |= IFM_10_T; + break; + case 55000: + ifmr->ifm_active |= IFM_10_T; + break; + case 11: + ifmr->ifm_active |= IFM_10_T; + break; case 100: ifmr->ifm_active |= IFM_100_TX; break; ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sysutils/fusefs-ntfs working for anyone?
On Sunday 18 February 2007 12:45, Ulrich Spoerlein wrote: > I've been trying to mount my NTFS partitions with the NTFS-3g project's > FUSE implementation but am unable to mount anything. > > I'm on 6-STABLE and have the latest versions of FUSE installed: [big snip] ... > So, the basic question is: Has _anybody_ used ntfs-3g successfully on > RELENG_6? When I tried it a couple months ago (on -STABLE) all I got were coredumps.. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Stable on Blade server
On Friday 23 February 2007 07:12, Marian Hettwer wrote: > Hi there, > > On Fri, 23 Feb 2007 11:06:54 +0100, Martin <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I work for a little web agency/isp and we are going to buy new hw to > > sustain the growinng demand of our customers. > > > > We're 100% FreeBSD-only and i was looking to buy IBM blade servers: can > > anyone reccomend any of them? models? particular hw/firmware/misc > > we have several blade centers in our datacenters. None of them were able to > boot up 6.1-RELEASE (which was the last one I tried). In general, the IBM > blade center is crap IMO. The management capabilites (some java / vnc > applet speak KVM over IP) is completely borked. Debian Linux runs, but > FreeBSD seems to have problems with the way those IBM blades are handling > the keyboard. Dunno any details, though :) Maybe you'd like to take a look > at HP's blades. I recall that the FreeBSD project got a HP blade donation > and is using a fully equipped HP Bladecenter. Maybe HP is your way to go if > you want to use FReeBSD on blades :) > > HTH, > Marian > > PS.: If I'll find the time to do so, I'll try a pxeboot of 6.2-RELEASE on > some different blades of us. Although this won't happen before end of next > week (to busy right now). I can also recommend HP blades in general. I haven't had a chance to play with FreeBSD on one, but the hardware is solid and the management interface is good. There's a JVM-based remote console that works on most platforms I've tried as well as the IE-only one. The IE-only one has built-in floppy/CD support and a couple other tricks, but there's also a standalone JVM-based media applet. I'm 99% sure that the built-in SAS controller is supported by ciss(4), and 90% sure that the built-in ethernet controller is supported, probably by bge(4). I'm not sure about the fibre controllers. I'm setting up a few of these in the next few days so I may boot to a 6.2 CD on one of them. I'll report what I find if so. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sysutils/fusefs-ntfs working for anyone?
On Sunday 18 February 2007 13:59, John Nielsen wrote: > On Sunday 18 February 2007 12:45, Ulrich Spoerlein wrote: > > I've been trying to mount my NTFS partitions with the NTFS-3g project's > > FUSE implementation but am unable to mount anything. > > > > I'm on 6-STABLE and have the latest versions of FUSE installed: > > [big snip] > ... > > > So, the basic question is: Has _anybody_ used ntfs-3g successfully on > > RELENG_6? > > When I tried it a couple months ago (on -STABLE) all I got were coredumps.. I just tried this again (running -STABLE from a few days ago, reinstalled the port today) and it's working fine for a volume created with mkntfs and for a volume created under Windows XP (over iSCSI no less). JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Changing Console Resolution - Vidcontrol
On Monday 02 April 2007 01:55:45 pm Schiz0 wrote: > I'm wondering how you can increase the resolution of the console in FreeBSD > stable. I have read the man page on vidcontrol and googled around a bit, > but I'm still confused about what to do. I'm currently running FreeBSD in > VMWare on a windows machine (But that'll change as soon as I learn enough > to put it up my server, which currently runs linux). I'd like to have > something like 1024x768 resolution or so. Also, the man pages mention > something about VESA modules. What exactly is this, and do I need it? My > kernel is currently compiled without support for it. Would I need to > recompile my kernel again? Without recompiling your kernel, you should be able to do modes like: # vidcontrol -f 8x8 cp437-8x8.fnt VGA_80x50 # vidcontrol -f 8x8 cp437-8x8.fnt VGA_80x60 If you add "options VGA_WIDTH90" to your kernel you can do things like: # vidcontrol -f 8x8 cp437-8x8.fnt VGA_90x50 # vidcontrol -f 8x8 cp437-8x8.fnt VGA_90x60 (note that not all hardware likes the 90-column modes) And if you add "options VESA" and "options SC_PIXEL_MODE" to your kernel you can use any fontsize (of the three: 8x16, 8x14, 8x8) with any VESA video mode supported by your hardware. You get a list of modes by running "vidcontrol -i mode" from a virtual terminal. On my machine mode 279 is 1024x768x16. If I wanted to use that with an 8x14 font I'd do this: # vidcontrol -f 8x14 cp437-8x14.fnt MODE_279 JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xfce4 broke after pkgdb -Ff
On Thursday 17 May 2007 02:37:15 pm KAYVEN RIESE wrote: > On Thu, 17 May 2007, Lowell Gilbert wrote: > > Please don't top-post. > > > > KAYVEN RIESE <[EMAIL PROTECTED]> writes: > >> so the "-r" option will be the significant difference for the > >> portupgrade comamnd, just verifying > > > > Yes. Otherwise, you may end up with some of the ports that depend on > > pango being unable to use the new version. > > > > Make sure you look through the UPDATING file to see if there are any > > other issues you need to take special action for at the same time. > > this guy seems to disagree > > jnielsendotnet:Try what I asked in my first reply (deleting and > reinstalling pango manually), and see if you can get any error messages > from xfce. > > If portupgrade -f is failing portupgrade -fr isn't likely to succeed > either. Portupgrade with the -r option is very useful, and you will probably want to use it. My point was that _before_ you try that you should figure out why portupgrade is failing to upgrade pango, and/or upgrade it manually. Otherwise it will just keep failing. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Native SATA vs. PATA-emulation - difference?
On Friday 18 May 2007 11:34:52 am Brian A. Seklecki wrote: > On Fri, 2007-05-18 at 16:25 +0100, Tom Evans wrote: > > On Fri, 2007-05-18 at 10:57 -0400, Brian A. Seklecki wrote: > > > On Fri, 2007-05-18 at 11:04 +0200, Patrick M. Hausen wrote: > > > > to UDMA33. I figure, they can safely be ignored? > > > > > > Only if there isn't some massive performance degradation. > > > ports/benchmarks/bonie++ can tell you that. > > > > > > As for the boot loader and your gmirror volumes; it's hard to say. > > > It's possible that there is some "absolute" or "non-relative" data in > > > there related to the device and the bus. > > > > > > Also: Maybe the geometry of the devices changes between modes? > > > > > > Send us the comparable dmesg(8) in both modes? > > > > > > ~BAS > > > > On my Intel ICH7 based laptop, switching from SATA/PATA emulation to > > SATA native mode changes the device of my HD from ad0 to ad4. > > > > YMMV > > right which I never understood absolute device number. you can choose > to do that in obsd/nbsd, but fbsd seems to psuedo magically do it. > reminds me Solaris. ~BAS If you don't want this behavior then remove "options ATA_STATIC_ID" from your kernel config. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ichsmb compile problem
On Saturday 11 February 2006 15:32, Restyánszki Zsolt wrote: > Dear FreeBSD develpers! > > Sorry about my e-mail, but I have a big problem with ichsmb kernel > driver. I try to compile to my kernel, but in FreeBSD 5.4-STABLE version > required smbus_if.h and smbus_if.c files missing, so make depend fails. > > Thats my request: can You send me a compiled version of ichsmb or if you > have a representative of smbus_if sources, can you send me those files? Make sure that your kernel config file includes "device smbus" and "device smb" as well ass "device ichsmb". See also the ichsmb(4) manpage. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mysql50-server not starting correctly on FreeBSD 6.1-PRERELEASE (ldconfig, rcorder)
I installed mysql50-server from an up-to-date ports tree on a new server I'm setting up running FreeBSD 6.1. The port adds the appropriate paths to ldconfig, but the startup script does not require ldconfig. This was causing mysqld not to start up correctly since on my system the mysql-server.sh script was being run before /etc/rc.d/ldconfig. The mysql script failed with errors about libraries being unavailable, etc. Running the mysql-server.sh script again once the system is up works fine. I'm not entirely conversant with the new rc script syntax, but I tried adding "ldconfig" to the REQUIRES line of mysql-server.sh and that seems to have fixed the problem. I now have two questions: 1) Is this a correct fix? 2) If so, should I file a PR with a patch or can someone just get this committed? Thanks, JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mysql50-server not starting correctly on FreeBSD 6.1-PRERELEASE (ldconfig, rcorder)
On Thursday 23 February 2006 03:46, Alex Dupre wrote: > Florent Thoumie wrote: > > Yup, since mysqld is running as root, otherwise REQUIRE: LOGIN. > > mysqld switch to user mysql after startup, so I guess it should require > LOGIN. That works here. I removed the BEFORE line and changed REQUIRE to only include LOGIN: # PROVIDE: mysql # REQUIRE: LOGIN # KEYWORD: shutdown Let me know if there are any other incantations I should test. Thanks, JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: fs check on ext3
On Friday 24 February 2006 04:57, Pol Hallen wrote: > Hi all, > > i want partition a disk on freebsd > > but now the disk is ext3 partition and i need backup a data and later > create a fbsd slide > > i do: > mount_ext2fs /dev/ad5 /disktmp > mount_ext2fs: /dev/ad5: Operation not permitted Are you sure that's the correct device name? Unless the filesystem really is on the beginning of the raw disk, you probably want a "slice" number after ad5. Do an fdisk ad5 To see what slices are on the disk, and then use the appropriate device name (e.g. /dev/ad5s1). JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: New ports on older stable (4.11)
Chiming in a little bit late. I have a hosting server that's running a patched version of FreeBSD 4.9 and regularly update the ports on it from the ports tree with few if any problems. Mail, web, php, etc. The only port I have installed that won't update is rar, and it's marked as broken in the port makefile. (unrar is fine, btw). JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.0 on TC1000 (was: wireless, ndis problems on Compaq TC1000 Tablet running 6-STABLE)
On Tuesday 07 March 2006 08:57, Milan Obuch wrote: > On Wednesday 30 November 2005 15:38, John Nielsen wrote: > > On Tuesday 29 November 2005 06:03 pm, Milan Obuch wrote: > > > On Tuesday 29 November 2005 21:39, John Nielsen wrote: > > > > After successfully installing FreeBSD 6.0 on a Compaq TC1000 Tablet > > > > PC > > > > > > By the way, how did you install 6.0 there? I am working with TC1000 > > > too, but it looks almost impossible to install FreeBSD without > > > keyboard. Just would like to know possibilities - I tried 7.0 but ACPI > > > does not work (does not boot even, only with ACPI disabled). > > > > My only obstacle was getting a keyboard attached to the console - by > > default it would boot up to sysinstall just fine but the keyboard > > wouldn't work. (It was detected, but not attached.. i.e. caps lock, etc > > would work but sysinstall wasn't getting any input.) > > > > Using a 6.0-BETA or RC disk (I don't remember which one), I wasn't able > > to get around this. However, using 6.0-RELEASE I was able to use the > > builtin keyboard by disabling atkbd0 AND atkbdc0 in the loader. > > I did verify this method with 6.1-BETA3. While I did not install it, only > came to sysinstall, it works - even with ACPI loaded, which was my primary > question. So after I build new 5.5-soon-to-be-RELEASE working partition, I > can wipe currently used 5.4-STABLE, couple of months old one and put 6.1 > there to test. Glad to hear it. > > Loading the kbdmux module may or may not be helpful--I didn't end up > > needing it. > > While I consider using loading kbdmux extremely useful, it did not work as > an alternative for your installing method. Neither buttons nor keyboard > worked, so no use... Yeah, I'll have to play around with this some more. > > Once installed (and with sshd running as a backup), I updated to -STABLE > > and built a custom kernel that does not include atkbdc, atkbd, or psm. > > It works fine. (And it's especially nice with a VESA 1024x768 mode in > > syscons.) > > Could you share your setup? Kernel config and similar? Maybe X setup, if > you are using it... I would like to put all information regarding TC1000 to > my web log at www.dino.sk, so others could benefit from my observations as > well. I don't have the tablet with me at the moment, but I do have the kernel config file (attached). The only options in there that I don't typically include on other machines are CPU_ENABLE_LONGRUN and SC_PIXEL_MODE, but I did have the sound and CD-ROM working on this kernel. For the VESA console you'll want to check the output of "vidcontrol -i mode", but IIRC I used this in /etc/rc.conf: allscreens_flags="-f 8x8 cp437-8x8.fnt MODE_280" Obviously you could substitute different font sizes and character pages as appropriate. I did set up X.org, but don't have my config file. "Xorg -configure" was reasonably helpful. I may have only been able to use X's VESA driver, but I don't remember for certain. I do remember that the mouse was flakey. My inability to get the built-in wireless working (even with NDIS) coupled with the mouse not behaving well enough to use in X put a damper on my enthusiasm for running FreeBSD on the device. I didn't explore using the stylus at all. I'd be interested in getting e-mail updates if you make any headway on any of those fronts, and I'll try to keep an eye on your blog. JN # SPARRTAB - Compaq TC1000 tablet machine i386 cpu I586_CPU ident SPARRTAB options CPU_ENABLE_LONGRUN options IPFIREWALL options IPFIREWALL_FORWARD options IPDIVERT options DUMMYNET options LIBMCHAIN options LIBICONV options NETSMB options NETSMBCRYPTO options SMBFS #optionsSCHED_ULE # ULE scheduler options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem fra
Re: pkgdb core dumb
On Thursday 23 March 2006 11:11, Kaveh Ahmadian wrote: > After a recent update, whenever I try to run the pkgdb (or any other > command that in turn calls pkgdb I get an error resulting in a core dump: > > [Updating the pkgdb in /var/db/pkg ... - 24 packages > found (-1 +2) (...).ruby18 in free(): error: chunk is already free > Abort (core dumped) I've seen this a number of times; it usually means a corrupt pkgdb. Rebuild it from scratch (pkgdb -fu). If that fails or if you still get the error afterwards, rebuild and reinstall portupgrade and ruby (without using portupgrade in the process). Run 'pkgdb -fu' again after the reinstall. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ntpdate
On Thursday 30 March 2006 10:31, gareth wrote: > On Thu 2006-03-30 (08:54), Scot Hetzel wrote: > > 2. change to sub directory where FreeBSD builds ntpdate: > > cd /usr/src/usr.sbin/ntp/ntpdate > > make clean Add "make depend" at this point. > > make > > make install > > make clean > > cool, thanx, i found that earlier with a 'locate ntpdate | grep Makefile' > and tried to run make but it gives: > > /usr/src/usr.sbin/ntp/ntpdate/../libntp/libntp.a: No such file or directory > *** Error code 1 > > Stop in /usr/src/usr.sbin/ntp/ntpdate. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ipw2100 vs ndis(4) -- does it work for anybody?
On Tuesday 02 May 2006 13:18, Ulrich Spoerlein wrote: > Good day, > > since the ipw(4) driver can't do WPA, I wanted to give ndis(4) a try. > This *used* to work back on 5.3 (memory is a bit vague) but it ain't > happening on 6.1-RC. > > I'm using the same driver as last time, which is the version 1.2.2.8 > from Intel. I also downloaded the newest one, version 1.2.4.35, but none > of them attach, when loading the if_ndis module. > > /sys/modules/if_ndis# make clean > /sys/modules/if_ndis# ndiscvt -i /compat/ndis/w70n51.inf -s > /compat/ndis/w70n51.sys -o ndis_driver_data.h /sys/modules/if_ndis# make > /sys/modules/if_ndis# make install load > /sbin/kldload -v /vol/obj/usr/src/sys/modules/if_ndis/if_ndis.ko > Loaded /vol/obj/usr/src/sys/modules/if_ndis/if_ndis.ko, id=32 > pci2: at device 3.0 (no driver attached) > > [EMAIL PROTECTED]:3:0: class=0x028000 card=0x25618086 chip=0x10438086 rev=0x04 > hdr=0x00 vendor = 'Intel Corporation' > device = 'Intel(R) PRO/Wireless 2100 LAN Card Driver' > class= network > > I know this did work in the past. What are other peoples experiences? > Besides, does ndis(4) even do WPA? If not then I would have to buy new > hardware anyway and the whole exercise would be in vain. Start by using ndisgen(8) instead of doing things the "old" way. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
MySQL, ntpd, and kern.timecounter
I have a FreeBSD 6.1 machine set up as a web and MySQL database server. Since the application is a bit database-intensive, I followed several of the MySQL tuning recommendations from this page: http://wikitest.freebsd.org/MySQL One of those was to change kern.timecounter.choice from ACPI-fast to TSC. That was fine for MySQL, but the real-world timekeeping on this hardware with TSC is so bad that it broke ntpd and the clock started drifting several seconds every hour. Timekeeping with ACPI-fast was quite reliable. I'm looking for recommendations in general, but I'll pose a few specific questions below as well. Should I change the timecounter back? How big an impact does the choice of timecounter have on performance with MySQL 4.1.19 and FreeBSD 6.1? Is there a conservative way I can answer this question myself for a server that's already in production? Can ntpd be coaxed into working with such bad timekeeping (as long as it's consistently bad)? Would Bad Things happen if I ran ntpdate or ntpd -q once or twice a day? Would this be considered an abuse of the ntp server(s)? Would I run a risk of confusing / breaking cron or sendmail or syslogd or anything else with the time jumps? All input appreciated. Thanks! JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MySQL, ntpd, and kern.timecounter
On Wednesday 07 June 2006 08:15, Lowell Gilbert wrote: > John Nielsen <[EMAIL PROTECTED]> writes: > > I have a FreeBSD 6.1 machine set up as a web and MySQL database server. > > Since the application is a bit database-intensive, I followed several of > > the MySQL tuning recommendations from this page: > > > > http://wikitest.freebsd.org/MySQL > > > > One of those was to change kern.timecounter.choice from ACPI-fast to TSC. > > > > That was fine for MySQL, but the real-world timekeeping on this hardware > > with TSC is so bad that it broke ntpd and the clock started drifting > > several seconds every hour. Timekeeping with ACPI-fast was quite > > reliable. > > > > I'm looking for recommendations in general, but I'll pose a few specific > > questions below as well. > > > > Should I change the timecounter back? How big an impact does the choice > > of timecounter have on performance with MySQL 4.1.19 and FreeBSD 6.1? Is > > there a conservative way I can answer this question myself for a server > > that's already in production? > > Benchmarking on a live system is tough. You can switch the > timecounter back and forth easily enough, but measuring performance > requires a predictable load. > > I don't know anything about mysql in particular, but on a fast > machine, with the database as the primary application, I wouldn't > expect choice of clock tick to affect the performance very much. This seems to be a "feature" of MySQL (on FreeBSD) in particular (see the wiki page above). I was hoping someone would have a general idea of the impact of the clock choice on FreeBSD 6.1 and Mysql 4.1. > > Can ntpd be coaxed into working with such bad timekeeping (as long as > > it's consistently bad)? > > You're not using a driftfile? That should compensate for systematic > drift pretty well. You just specify the file (which ntpd has to be > able to write) in the configuration file for ntpd (/etc/ntp.conf by > default). I always use a driftfile. With the acpi timecounter it behaves fine (it's currently -31.176). With the TSC timecounter ntpd stops working after the second server sync, probably when it realizes how much the clock has drifted in the interval since the first sync. Some things I was reading suggested that ntp's maximum supported drift is +/- 500 PPM, and with TSC this system's drift would be between -800 and -4000 PPM (I'm guessing). I was wondering if the 500 was a hard limit or if there's some kind of workaround. > > Would Bad Things happen if I ran ntpdate or ntpd -q once or twice a day? > > Would this be considered an abuse of the ntp server(s)? Would I run a > > risk of confusing / breaking cron or sendmail or syslogd or anything else > > with the time jumps? > > Nothing horrible would happen, but it could be annoying. I'd > recommend you avoid it. My feeling as well. Thanks for the response! JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
MySQL 4.1, GCC 3.x, FreeBSD 4.x
Should it be possible to compile and run MySQL 4.1 with GCC 3.4 on a FreeBSD 4.11 machine? I have a server which, for the time being at least, cannot be updated to FreeBSD 5. I'm currently running the stock MySQL 4.1.14 compiled from the port with no make flags. I would like to experiment with different build options/flags in the hopes of boosting performance. Specifically, I'd like to build it with linuxthreads and optimized C flags, but I am wary of using -O3 with gcc 2.9. Am I just being paranoid? When I try this from databases/mysql41-server: make WITH_LINUXTHREADS=yes BUILD_OPTIMIZED=yes USE_GCC=3.4 I get this: if gcc34 -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include -I/usr/local/include -DDBUG_OFF -O -pipe -D__USE_UNIX98 -D_REENTRANT -D_THREAD_SAFE -I/usr/local/include/pthread/linuxthreads -O3 -fno-omit-frame-pointer -MT conf_to_src.o -MD -MP -MF ".deps/conf_to_src.Tpo" -c -o conf_to_src.o conf_to_src.c; then mv -f ".deps/conf_to_src.Tpo" ".deps/conf_to_src.Po"; else rm -f ".deps/conf_to_src.Tpo"; exit 1; fi /usr/local/bin/libtool15 --preserve-dup-deps --mode=link gcc34 -DDBUG_OFF -O -pipe -D__USE_UNIX98 -D_REENTRANT -D_THREAD_SAFE -I/usr/local/include/pthread/linuxthreads -O3 -fno-omit-frame-pointer -L/usr/local/lib -o conf_to_src conf_to_src.o xml.o ctype.o bcmp.o -DHAVE_GLIBC2_STYLE_GETHOSTBYNAME_R -D_THREAD_SAFE -I/usr/local/include/pthread/linuxthreads -L/usr/local/lib -llthread -llgcc_r -lcrypt -lm -DHAVE_GLIBC2_STYLE_GETHOSTBYNAME_R -D_THREAD_SAFE -I/usr/local/include/pthread/linuxthreads -L/usr/local/lib -llthread -llgcc_r libtool15: link: unable to infer tagged configuration libtool15: link: specify a tag with `--tag' *** Error code 1 Stop in /usr/ports/databases/mysql41-server/work/mysql-4.1.14/strings. *** Error code 1 Stop in /usr/ports/databases/mysql41-server/work/mysql-4.1.14. *** Error code 1 Stop in /usr/ports/databases/mysql41-server/work/mysql-4.1.14. *** Error code 1 Stop in /usr/ports/databases/mysql41-server. Is this something simple to fix/work around? I'm not at all familiar with libtool. Any input appreciated. Thanks, JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MySQL 4.1, GCC 3.x, FreeBSD 4.x
On Wednesday 21 September 2005 14:41, Alex Dupre wrote: > John Nielsen wrote: > > I would like to experiment with different build options/flags in the > > hopes of boosting performance. Specifically, I'd like to build it with > > linuxthreads and optimized C flags, but I am wary of using -O3 with gcc > > 2.9. Am I just being paranoid? > > Yes, you are. Most MySQL binary packages are compiled with gcc 2.9 and > -O3. Good to know. Thanks! On Wednesday 21 September 2005 14:39, Kris Kennaway wrote: > USE_GCC is wrong, it's not a user-controllable variable. Set CC > instead. > > This might be OK as long as there is no C++ code involved, which > cannot be linked to C++ code from gcc 2.95. > > -O3 can be dangerous, so use with care. I might play around with the CC option. Thanks for straightening me out. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fw: GENERIC and DEFAULTS
On Thursday 03 November 2005 09:03 am, Ruslan Ermilov wrote: > On Thu, Nov 03, 2005 at 12:27:21PM +, Robert Watson wrote: > > On Thu, 3 Nov 2005, dick hoogendijk wrote: > > >Sure, but I think it's the *syntax* that matters here? options -> > > >nooptions / i486_cpu -> no??? It's OK to leave GENERIC alone, but HOW > > >are things switched off? > > > > It appears to be an ommission in the file format. I've e-mailed > > Ruslan, who implemented nodevice and nooption, to suggest that he also > > add nocpu. I wonder if there are other missed syntactic bits of note. > > I've committed a code that implements the "nocpu" directive, FWIW. How about "nomakeoptions"? Or is there already a way to do the equivalent? I just tried to rewrite my custom kernel using GENERIC as a starting point and didn't know how to override/remove the "makeoptions DEBUG=-g" line. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
wireless, ndis problems on Compaq TC1000 Tablet running 6-STABLE
After successfully installing FreeBSD 6.0 on a Compaq TC1000 Tablet PC (and updating it to yesterday's -STABLE), I am trying to get the built-in wireless to work. The wi(4) driver does not attach to it. Under Windows, the card shows up as a "Compaq 802.11b WLAN Mini-PCI" card (although it is not in the user-accessible Mini-PCI slot). Pciconf gives this: [EMAIL PROTECTED]:10:0:class=0x02 card=0x00d30e11 chip=0x05061114 rev=0x11 hdr=0x00 vendor = 'Atmel Corp.' device = 'AT76C506 802.11b Wireless Network Adaptor' class= network subclass = ethernet (Full pciconf -lv output attached). My first question: is there a chance it would be trivial to make this card work with the wi(4) driver? ISTR reading this morning that this was a Prism chip, although now I can't find that again. Undaunted, I moved on to ndis(4). Using wine(1), I was able to extract a driver from SP23100.exe, obtained from hp's website.[1] I fed netcwl200.inf and cwl200.sys to ndisgen(8), and was rewarded with a successfully compiled cwl200_sys.ko. Unfortunately, the machine panics as soon as the module is loaded, with the following output (transcribed by hand, typos possible): tablet# kldload cwl200_sys isab1: at device 7.4 on pci0 device_attach: isab1 attach returned 6 no match for swprintf isab1: at device 7.4 on pci0 device_attach: isab1 attach returned 6 ndis0: port 0x1c00-0x1cff mem 0xe803-0xe803 at device 10.0 on pci0 ndis0: NDIS API version: 5.1 ntoskrnl dummy called... ntoskrnl dummy called... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x20:0xc3bf70d8 stack pointer = 0x28:0xd6cbc62c frame pointer = 0x28:0xd6cbc844 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 = 571 (kldload) trap number = 12 panic: page fault Which leads to my second question: should ndis be expected to work with this device? Assuming the answer is yes, what else can I do to track down the problem? A complete (verbose) dmesg from the system is attached. Any input will be much appreciated. Thanks! JN [1] See http://h18007.www1.hp.com/support/files/Compaqtabletpc/us/download/19836.html Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-STABLE #0: Mon Nov 28 15:23:03 EST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SPARRTAB Preloaded elf kernel "/boot/kernel/kernel" at 0xc0851000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0851188. Calibrating clock(s) ... i8254 clock: 1193167 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 995502588 Hz CPU: Transmeta(tm) Crusoe(tm) Processor TM5800 (995.50-MHz 586-class CPU) Origin = "GenuineTMx86" Id = 0x543 Stepping = 3 Features=0x80893f Processor revision 1.5.0.2 Code Morphing Software revision 4.4.0-10-156 20030501 16:35 official release 62.0.1-4.4.0#1 real memory = 511639552 (487 MB) Physical memory chunk(s): 0x1000 - 0x0009afff, 630784 bytes (154 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x00c25000 - 0x1df23fff, 489680896 bytes (119551 pages) avail memory = 491061248 (468 MB) bios32: Found BIOS32 Service Directory header at 0xc00f7710 bios32: Entry = 0xfd6a0 (c00fd6a0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd6a0+0x16c pnpbios: Found PnP BIOS data at 0xc00f7760 pnpbios: Entry = f:a13e Rev = 1.0 Other BIOS signatures found: Crusoe LongRun support enabled, current mode: 2 <1000MHz 1350mV 100%> wlan: <802.11 Link Layer> netsmb_dev: loaded nfslock: pseudo-device null: io: random: mem: VESA: information block 56 45 53 41 00 03 00 01 00 01 01 00 00 00 22 00 00 01 00 01 11 03 07 01 00 01 1a 01 00 01 25 01 00 01 00 01 01 01 02 01 03 01 04 01 05 01 06 01 07 01 08 01 09 01 0a 01 0b 01 0c 01 0e 01 0f 01 VESA: 33 mode(s) found VESA: v3.0, 16384k memory, flags:0x1, mode table:0xc0761f62 (122) VESA: NVidia VESA: NVidia Corporation NV11 Board Chip Rev B2 npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: [MPSAFE] pci_open(1):mode 1 addr port (0x0cf8) is 0x80003904 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=80] is there (id=03951279) pcibios: BIOS version 2.10 Found $PIR table, 8 entries at 0xc00fdf40 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded07A 0x01 3 4 6 9 10 11 12 14 15 embedded07B 0x02 3 4 6 9 10 11 12 14 15 embedded07C 0x03
Re: FreeBSD 6.0 on TC1000 (was: wireless, ndis problems on Compaq TC1000 Tablet running 6-STABLE)
On Tuesday 29 November 2005 06:03 pm, Milan Obuch wrote: > On Tuesday 29 November 2005 21:39, John Nielsen wrote: > > After successfully installing FreeBSD 6.0 on a Compaq TC1000 Tablet PC > By the way, how did you install 6.0 there? I am working with TC1000 too, > but it looks almost impossible to install FreeBSD without keyboard. Just > would like to know possibilities - I tried 7.0 but ACPI does not work (does > not boot even, only with ACPI disabled). My only obstacle was getting a keyboard attached to the console - by default it would boot up to sysinstall just fine but the keyboard wouldn't work. (It was detected, but not attached.. i.e. caps lock, etc would work but sysinstall wasn't getting any input.) Using a 6.0-BETA or RC disk (I don't remember which one), I wasn't able to get around this. However, using 6.0-RELEASE I was able to use the builtin keyboard by disabling atkbd0 AND atkbdc0 in the loader. Loading the kbdmux module may or may not be helpful--I didn't end up needing it. Once installed (and with sshd running as a backup), I updated to -STABLE and built a custom kernel that does not include atkbdc, atkbd, or psm. It works fine. (And it's especially nice with a VESA 1024x768 mode in syscons.) JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
typo in man ed (4)
This is something that's bitten me on the two occasions I've needed to use it, so I'm hoping it can get fixed. In the CAVEATS section of the ed (4) manpage, it says this: 16bit Compex cards identify themselves as being 8bit. While these cards will work in 8bit mode, much higher performance can be achieved by speci- fying "flags 0x04" (force 16bit mode) in your kernel config file. In addi- tion, you should also specify "iosize 16384" to take advantage of the extra 8k of shared memory that 16bit mode provides. If you put the word "iosize" in a kernel config file it produces a syntax error. It should be "iosiz" (without the 'e'). I'm not familiar with the procedure(s) for fixing typos like this, but if one of you could enlighten me and/or just take care of it I'd be appreciative. Thanks, JN To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Upgrading to Xf864, how do I get wheel moyse to work?
- Original Message - From: "stan" <[EMAIL PROTECTED]> To: "FreeBSD Stable Mailing List" <[EMAIL PROTECTED]> Sent: Monday, March 04, 2002 8:41 AM Subject: Upgrading to Xf864, how do I get wheel moyse to work? > I'm upgrading to Xf6864 from the ports tree. > > I am using mousedd to handle the mouse and pass it on to X. > > What configuration changes do I need to make to moused, and X to take > advantage of my wheel mouse? This post belongs on -questions, if anywhere. The answer is also covered in the FAQ. (http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/x.html#X-AND-WHEEL) Basically, you need to add "-z 4" to "moused_flags" in rc.conf. And your mouse section in XF86Config should look something like this: Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" Option "Buttons" "5" EndSection If the software you want to use the scroll wheel in isn't new enough to recognize it on its own, you may wish to install the imwheel port/package. JN To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: EtherExpress 16 not probed at boot on 4.5R
I had a shutdown issue as well, come to think of it. I didn't have any page faults, but I didn't do much with the system other than some basic tests of the card. Does this driver have a maintainer? Any volunteers? JN - Original Message - From: "Karl Heller" <[EMAIL PROTECTED]> To: "John Nielsen" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; "Karl Heller" <[EMAIL PROTECTED]> Sent: Thursday, April 25, 2002 9:27 PM Subject: Re: EtherExpress 16 not probed at boot on 4.5R > > > Thanks for the patch. It does detect the card now. However, the system is now a bit unstable. It won't shutdown properly.. never gets to the "press any key to reboot" screenk and has a page fault every now and then. Not sure if this is related to the patch or not. But I was surprised to see the dates from 2000. > > Karl > > > - Original Message - > > From: "Karl Heller" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Wednesday, April 24, 2002 10:39 AM > > Subject: EtherExpress 16 not probed at boot on 4.5R > > > Hello, > > > > > > I posted a bug report about this but haven't heard anything back. I'll > > > post here instead. =) > > > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=37240 > > > > > > I have a Intel EtherExpress 16 that will not probe on boot, or with a > > > custom kernel. However, under 3.4R it does find it. I'm just switching > > > boot floppies and notice this. I've since installed 4.5R using CDRom, > > > however, I'd like to get it working. Any thoughts or anyone want to help > > > debug this one. There was a previous bug report for another version with > > > similar problems but the issue was dropped. > > > > > > Please respond via email as I'm having some problems getting on the stable > > > email list. > > > > There was a thread about this a while ago on the newsgroup (the subject was > > "Ether16 NIC" if you want to look it up on google). Martin Birgmeier posted > > a patch which I successfully applied to a -stable machine and got my card > > working. I'm attaching a copy of Martin's patch so you can use it. > > > > To the list: PR kern/16937 is marked as closed even though this is an issue > > with -stable. There may be other PR's on this issue as well, but I don't > > know if any of them have patches included. If one of you wants to > > submit/test/commit this I think that would be great. > > > > JN To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: NTFS (ntfs.ko)
- Original Message - From: "Mike Hogsett" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, June 13, 2002 6:19 PM Subject: NTFS (ntfs.ko) > > We are about to receive some (sensitive) data on possibly an NTFS > filesystem (we are receiving a disk) that we will be performing some > batch processing on. > > I am curious how stable the NTFS support is in FreeBSD 4.5-RELEASE-p6. > > My current plan is to mount the disk read only and copy the data onto the > host's local disk. > > Is ntfs.ko stable enough, or should I but the disk in a Windows box and > tranfer it across the network instead? The NTFS code is quite stable--I've used it on a couple different machines. I seem to recall reading about a case where not all the files on the filesystem were visible when mounted under FreeBSD, but I can't remember where now. Transferring the files across the network is certainly the safest option, and you have the added benefit of being able to write to the filesystem that way as well. Personally (working under the only slightly-untrue notion that FreeBSD can do anything), I'd do it under FreeBSD first and only go to the Windows/network option if you had trouble accessing anything. It should be fast, stable, and a boost for your ego. :) JN To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
