setting WiFi txpower with ifconfig
I'm trying to do some antenna work so I want a weak signal from the other side of the basement. So I try stuff like ifconfig athn0 txpower 1 and get "ifconfig: SIOCS80211TXPOWER: Invalid argument". Any number I've tried gives the same thing. If I leave out the number it tells me I need one. Worse, the same thing happens with athn, ath, urtwn, in OpenBSD 5.6, 5.2, 5.0. Looking in ieee80211_ioctl.h the power (dBm) value is an int16_t but there's also an i_mode int which controls whether the value can be set manually or it's in automatic mode. The ifconfig man page says: txpower dBm Set the transmit power. The driver will disable any auto level and transmit power controls in this mode. Implying that setting txpower should work. It seems stuck in auto mode or something. I've Googled this and other people have had similar problems for years but no solution seems to be posted. Using -txpower which should (by the man page) put it back in auto mode gives the same invalid argument error. It seems to be something wrong with ifconfig since it works the same way with 3 different cards, or it's something wrong in the man page so I'm using it wrong. I'm probably the only one who wants to turn the power down. I should probably stick in a printf to see exactly what's being fed to the ioctl. Or something in setiftxpower() in ifconfig.c Alan -- Credit is the root of all evil. - AB1JX
Spanish discussion list
Hello Is there someone interested having a discussion list in Spanish? I have a OBSD server running current (httpd, smtpd, ftp), and i would like having a discussion list in Spanish, it could have blogs, foro, or any other related things. For now i have it at home, but i might pay for a dedicated site on a OBSD housing. The main idea is to make it easier for Spanish speakers, keeping the friendly environment of OpenBSD list. Thanks for your attention.
Re: Variable Length Arrays
>So I've been wondering about variable length arrays from c99 for a while >now. They seem to me like a good way to avoid lots of trivial calls to >malloc/free at least for smaller arrays that aren't going to blow up the >stack. That said I don't see them being used. > >The promise of them seems to be 'easy', dynamic, stack allocated memory and >improved readability. That said, using vla's avoids the work on malloc that >creates a hostile (strict) environment, like junking and whatnot. Also there >is the portability stuff, I'm not sure if all the platforms that openbsd >runs on are using a compiler that supports them yet. > >gcc 4.2 in base seems to support them well enough, though I note that the >gcc website says that some corner cases were fixed in version 4.5 which I >haven't investigated yet. > >So what do you guys think? VLA's, are they good, bad, evil, stupid, all of >the above? alloca() re-invented. >From the alloca(3),man page: BUGS The alloca() function is slightly unsafe because it cannot ensure that the pointer returned points to a valid and usable block of memory. The allocation made may exceed the bounds of the stack, or even go further into other objects in memory, and alloca() cannot determine such an error. Avoid alloca() with large unbounded allocations. alloca(3) was considered slightly unsafe, because use if it was rare. Your mail strikes so widely, feel free to modify a whole system to use this instead of malloc. Then argue your point, and lose...
Re: CardBus Support
>Hi, any idea on how to enable CardBus Support on 5.6 ? i'm getting this >message on boot related to the PCMCIA card that i'm trying to use on my old >toshiba lapto, the card works just fine under pfsense/freebsd > >Dmesg: > >cbb0 at pci1 dev 4 function 0 "ENE CB-1410 CardBus" rev 0x01: apic 1 int >16, CardBus support disabled >cardslot0 at cbb0 slot 0 flags 0 > >Any help please. I am continually baffled by how often we have to explain this point, over and over and over again. Your mail does not contain a dmesg. It only contains a very small subset you chose to expose. You went out of your way to remove the rest, or you didn't want to go through the effort of providing a full and proper report. I just spent a few minutes in the code trying to figure out the problem, and soon found out I need the rest of your dmesg. But then I ran out of attention span, so don't bother. Do not submit a new bug report.
Variable Length Arrays
Hey Folks, So I've been wondering about variable length arrays from c99 for a while now. They seem to me like a good way to avoid lots of trivial calls to malloc/free at least for smaller arrays that aren't going to blow up the stack. That said I don't see them being used. The promise of them seems to be 'easy', dynamic, stack allocated memory and improved readability. That said, using vla's avoids the work on malloc that creates a hostile (strict) environment, like junking and whatnot. Also there is the portability stuff, I'm not sure if all the platforms that openbsd runs on are using a compiler that supports them yet. gcc 4.2 in base seems to support them well enough, though I note that the gcc website says that some corner cases were fixed in version 4.5 which I haven't investigated yet. So what do you guys think? VLA's, are they good, bad, evil, stupid, all of the above? -- Ted Bullock
Re: YP Alternative
Thanks for all the ideas. It's given me avenues for testing. On 1/2/2015 5:32 PM, Craig Skinner wrote: On 2015-01-02 Fri 14:02 PM |, Christopher Barry wrote: I can't speak to ksh being 'better', but it may well be. Aye, not subject to bash's many security problems, such as #ShellShock & #BashBug that brought loonix to it's knees a couple of months ago. Who wants to be patching boxes at work at weekends when there's more important fun to be had;- Edinburgh FolkSoc Ceilidh Band: Military Two-Step http://www.youtube.com/watch?v=DNVLDOwxVx4&feature=related I have 20 years experience with bash, so I default to it. Cool Christopher. The smart men on @tech keep ksh slick, so for scripters there's not much difference. Have a go. If I was going to craft something today to solve this problem, I think I would probably use rsync over shh though, and not scp. Like ksh, rdist is in base, (unlike either bash or rsync), and uses ssh by default. A root cronjob like this might be all that is needed: @hourly rdist -f /root/rdist.yp Then it's off to a castle for more flinging of fit Scottish lassies: http://www.youtube.com/watch?v=gBCayM6aFJQ&feature=related
Re: Upgrading issues (i386 on PPro class) 5.4->5.5 leaving system horked
Damon Getsman wrote: > So, can anybody tell me, is my situation just so hosed that it's helpless? > I mean, should I stop waiting for potential ways to fix this dependency > hosed box and reinstall and try to find a way to re-inject all of my data > into it, or are the gurus just swamped with new years tasks? :) If any of > you could give me some feedback I'd really appreciate it. Like I said with > the issue when I was first mentioning it, this system is really integral to > a lot of the work that I do, and it's my sole external facing server... > It's like a knife in my gut not having it working. > > -Damon At this point, I don't know if anyone can tell what's wrong or how to fix it. You might as well reinstall. How spread out is your data? Save /home, /etc, and pkg_info -qm and off you go. I usually make /etc a git repo so I can diff and roll back changes, etc. And keep a seperate partition for backups so I can wipe the system drive and reinstall if needed (haven't needed it yet). You could also try to make a site.tgz of your data to make reinstallation easier if it's that complex. Tim.
Re: /etc/hosts file not being used - OpenBSD v5.1
Hi Raf, It's all been sorted. Should have used getent to check my tweaks. On Friday, 2 January 2015, Raf wrote: > On Fri, Jan 02, 2015 at 04:53:32PM EST, Richard Brooks wrote: > > > Hi Raf > > Hi Richard, > > > Would rather not gives these files out as they do reveal the layout of my > > network. But the simple hosts file I tried was along the lines of: > > Content of 'resolv.conf' might be crucial here - otherwise you may be > wasting all our time here. I'm not asking for a verbatim copy of either > of the files but knowing which options you have used apart from the > aforementioned 'lookup' and 'nameserver', would be very nice. > > > 127.0.0.1 localhost > > 192.168.1.1 myserver.domain.com TheServer > > You haven't answered my other question - how are you doing the lookup? > > host myserver.domain.com > > or > > host myserver > > or > > host TheServer > > also, please specify which utility you are using (host?). > > Regards, > > Raf > > -- Regards Richard
Re: /etc/hosts file not being used - OpenBSD v5.1
On Fri, Jan 02, 2015 at 04:53:32PM EST, Richard Brooks wrote: > Hi Raf Hi Richard, > Would rather not gives these files out as they do reveal the layout of my > network. But the simple hosts file I tried was along the lines of: Content of 'resolv.conf' might be crucial here - otherwise you may be wasting all our time here. I'm not asking for a verbatim copy of either of the files but knowing which options you have used apart from the aforementioned 'lookup' and 'nameserver', would be very nice. > 127.0.0.1 localhost > 192.168.1.1 myserver.domain.com TheServer You haven't answered my other question - how are you doing the lookup? host myserver.domain.com or host myserver or host TheServer also, please specify which utility you are using (host?). Regards, Raf
Re: YP Alternative
On 2015-01-02 Fri 14:02 PM |, Christopher Barry wrote: > > I can't speak to ksh being 'better', but it may well be. Aye, not subject to bash's many security problems, such as #ShellShock & #BashBug that brought loonix to it's knees a couple of months ago. Who wants to be patching boxes at work at weekends when there's more important fun to be had;- Edinburgh FolkSoc Ceilidh Band: Military Two-Step http://www.youtube.com/watch?v=DNVLDOwxVx4&feature=related > > I have 20 years experience with bash, so I default to it. > Cool Christopher. The smart men on @tech keep ksh slick, so for scripters there's not much difference. Have a go. > If I was going to craft something today to solve this problem, > I think I would probably use rsync over shh though, and not scp. > Like ksh, rdist is in base, (unlike either bash or rsync), and uses ssh by default. A root cronjob like this might be all that is needed: @hourly rdist -f /root/rdist.yp Then it's off to a castle for more flinging of fit Scottish lassies: http://www.youtube.com/watch?v=gBCayM6aFJQ&feature=related
CardBus Support
Hi, any idea on how to enable CardBus Support on 5.6 ? i'm getting this message on boot related to the PCMCIA card that i'm trying to use on my old toshiba lapto, the card works just fine under pfsense/freebsd Dmesg: cbb0 at pci1 dev 4 function 0 "ENE CB-1410 CardBus" rev 0x01: apic 1 int 16, CardBus support disabled cardslot0 at cbb0 slot 0 flags 0 Any help please.
Re: Upgrading issues (i386 on PPro class) 5.4->5.5 leaving system horked
Quoting Damon Getsman : Hello everyone. Regardless, I just wanted to find out... I usually get people willing to give some advice, or at least willing to laugh and tell me the lesson that I needed to know on here. I was really kind of surprised that I haven't heard anything back on this for so long... As I see it would be very difficult to diagnose your problem remotely, but I'm new here. Yesterday I did my first (test) upgrade of 5.5 to 5.6 and was fine, the system was smart enough to not screw up things even when I set the wrong architecture and version on pkg.conf. I did four updates in total and the last one was very straightforward and quick. The process was simple: booted systems with the installation CD, selected upgrade and almost everything was the default selection, after that booted into the upgraded server, ran the sysmerge command, deleted the old files, rebooted, updated packages with pkg_add -u, rebooted, ran again pkg_add -u just in case and everything went fine. I even applied patches since I'm using stable. So, can anybody tell me, is my situation just so hosed that it's helpless? I mean, should I stop waiting for potential ways to fix this dependency hosed box and reinstall and try to find a way to re-inject all of my data into it, or are the gurus just swamped with new years tasks? :) If any of you could give me some feedback I'd really appreciate it. Like I said with the issue when I was first mentioning it, this system is really integral to a lot of the work that I do, and it's my sole external facing server... It's like a knife in my gut not having it working. If I was you I would install a clean system, check differences between the stock and your configuration files, restore your data and check if everything is working again. Anyway, if you have to do more than one upgrade operation on the same system it might take less effort just reinstalling than going through all the upgrades. Upgrading critical systems is an excellent case for virtual machines, if something goes wrong you just have to restore the backed up image that can be as easy as copying a file. I know that virtual machines are heresy here and viewed as a waste of resources, but in situations like this are priceless. -- Best regards, Jorge Lopez. This message was sent using IMP, the Internet Messaging Program.
/etc/hosts file not being used - OpenBSD v5.1
Hi Raf Would rather not gives these files out as they do reveal the layout of my network. But the simple hosts file I tried was along the lines of: 127.0.0.1 localhost 192.168.1.1 myserver.domain.com TheServer Like I say the hosts file should do its work without the resolv.conf file (which I tried), so that can't by itself be the issue. Probably best to keep things simple to start with, then re-introduce the resolv.conf file later once we get the resolver using the hosts file. On Friday, 2 January 2015, Raf > wrote: > On Fri, Jan 02, 2015 at 04:16:47PM EST, Richard Brooks wrote: > > > As you can probably tell from the version number, I've been using OpenBSD > > for a while, but have only recently discovered that name resolution > entries > > in the hosts file are not being used and that the o/s waltz's merrily off > > to the remote DNS server when the info it needs is in the hosts file. > > > > resolv.conf file has the 'lookup file bind' option along with entries for > > domain and search. Also tried deleting the hosts file and just adding a > > couple of entries, but no joy. The hosts file has read access for all > users > > set. Am not running named or dhcp servers. > > > > Just did an o/s and user land update. That didn't help either. Also tried > > renaming resolv.conf to _resolv.conf and rebooted so the o/s didn't have > a > > resolv.conf file, the default behaviour in this scenario being that the > > hosts file is all that gets used, but alas it's not so. > > > > Does anyone have any ideas on what's going on? > > Hi Richard, > > Could you include both the 'hosts' and 'resolv.conf' files, please? > > As already pointed out, how are you doing the lookup? > > Regards, > > Raf > > -- Regards Richard
Re: /etc/hosts file not being used - OpenBSD v5.1
Hi Raf Would rather not gives these files out as they do reveal the layout of my network. But the simple hosts file I tried was along the lines of: 127.0.0.1 localhost 192.168.1.1 myserver.domain.com TheServer Like I say the hosts file should do its work without the resolv.conf file (which I tried), so that can't by itself be the issue. Probably best to keep things simple to start with, then re-introduce the resolv.conf file later once we get the resolver using the hosts file. On Friday, 2 January 2015, Raf wrote: > On Fri, Jan 02, 2015 at 04:16:47PM EST, Richard Brooks wrote: > > > As you can probably tell from the version number, I've been using OpenBSD > > for a while, but have only recently discovered that name resolution > entries > > in the hosts file are not being used and that the o/s waltz's merrily off > > to the remote DNS server when the info it needs is in the hosts file. > > > > resolv.conf file has the 'lookup file bind' option along with entries for > > domain and search. Also tried deleting the hosts file and just adding a > > couple of entries, but no joy. The hosts file has read access for all > users > > set. Am not running named or dhcp servers. > > > > Just did an o/s and user land update. That didn't help either. Also tried > > renaming resolv.conf to _resolv.conf and rebooted so the o/s didn't have > a > > resolv.conf file, the default behaviour in this scenario being that the > > hosts file is all that gets used, but alas it's not so. > > > > Does anyone have any ideas on what's going on? > > Hi Richard, > > Could you include both the 'hosts' and 'resolv.conf' files, please? > > As already pointed out, how are you doing the lookup? > > Regards, > > Raf > > -- Regards Richard
Re: Upgrading issues (i386 on PPro class) 5.4->5.5 leaving system horked
On Fri, Jan 02, 2015 at 04:10:58PM EST, Damon Getsman wrote: > Hello everyone. Hi Damon, > I posted that information regarding the 5.4->5.5 upgrade breaking (and > subsequent break when following someone's advice just to take it up to 5.6 > since it was already horked like that) a few days back here. I was going > to post some google groups and/or openbsd.org links to the previous > threaded posts, but I'm not having luck digging them up on google groups, > and it appears that majordomo on the openbsd.org site won't give summaries > from previous months. marc.info? > Regardless, I just wanted to find out... I usually get people willing to > give some advice, or at least willing to laugh and tell me the lesson that > I needed to know on here. I was really kind of surprised that I haven't > heard anything back on this for so long... You haven't provided answers to some of the questions either. http://marc.info/?l=openbsd-misc&m=141958400922121&w=2 > So, can anybody tell me, is my situation just so hosed that it's helpless? > I mean, should I stop waiting for potential ways to fix this dependency > hosed box and reinstall and try to find a way to re-inject all of my data > into it, or are the gurus just swamped with new years tasks? :) If any of > you could give me some feedback I'd really appreciate it. Like I said with > the issue when I was first mentioning it, this system is really integral to > a lot of the work that I do, and it's my sole external facing server... > It's like a knife in my gut not having it working. > > Anything is very much appreciated. Feel free to hit me up via personal > email, too, if you'd rather avoid public posting for some reason. > > I hope you all have a better year than last. :) Regards, Raf
Re: /etc/hosts file not being used - OpenBSD v5.1
On Fri, Jan 02, 2015 at 04:16:47PM EST, Richard Brooks wrote: > As you can probably tell from the version number, I've been using OpenBSD > for a while, but have only recently discovered that name resolution entries > in the hosts file are not being used and that the o/s waltz's merrily off > to the remote DNS server when the info it needs is in the hosts file. > > resolv.conf file has the 'lookup file bind' option along with entries for > domain and search. Also tried deleting the hosts file and just adding a > couple of entries, but no joy. The hosts file has read access for all users > set. Am not running named or dhcp servers. > > Just did an o/s and user land update. That didn't help either. Also tried > renaming resolv.conf to _resolv.conf and rebooted so the o/s didn't have a > resolv.conf file, the default behaviour in this scenario being that the > hosts file is all that gets used, but alas it's not so. > > Does anyone have any ideas on what's going on? Hi Richard, Could you include both the 'hosts' and 'resolv.conf' files, please? As already pointed out, how are you doing the lookup? Regards, Raf
Re: /etc/hosts file not being used - OpenBSD v5.1
On Fri, Jan 02, 2015 at 09:16:47PM +, Richard Brooks wrote: > As you can probably tell from the version number, I've been using OpenBSD > for a while, but have only recently discovered that name resolution entries > in the hosts file are not being used and that the o/s waltz's merrily off > to the remote DNS server when the info it needs is in the hosts file. > > resolv.conf file has the 'lookup file bind' option along with entries for > domain and search. Also tried deleting the hosts file and just adding a > couple of entries, but no joy. The hosts file has read access for all users > set. Am not running named or dhcp servers. > > Just did an o/s and user land update. That didn't help either. Also tried > renaming resolv.conf to _resolv.conf and rebooted so the o/s didn't have a > resolv.conf file, the default behaviour in this scenario being that the > hosts file is all that gets used, but alas it's not so. > > Does anyone have any ideas on what's going on? How are you checking that /etc/hosts is not used? Some commands (like dig) ignore /etc/hosts always. -Otto
/etc/hosts file not being used - OpenBSD v5.1
As you can probably tell from the version number, I've been using OpenBSD for a while, but have only recently discovered that name resolution entries in the hosts file are not being used and that the o/s waltz's merrily off to the remote DNS server when the info it needs is in the hosts file. resolv.conf file has the 'lookup file bind' option along with entries for domain and search. Also tried deleting the hosts file and just adding a couple of entries, but no joy. The hosts file has read access for all users set. Am not running named or dhcp servers. Just did an o/s and user land update. That didn't help either. Also tried renaming resolv.conf to _resolv.conf and rebooted so the o/s didn't have a resolv.conf file, the default behaviour in this scenario being that the hosts file is all that gets used, but alas it's not so. Does anyone have any ideas on what's going on? -- Regards Richard
Re: Upgrading issues (i386 on PPro class) 5.4->5.5 leaving system horked
Hello everyone. I posted that information regarding the 5.4->5.5 upgrade breaking (and subsequent break when following someone's advice just to take it up to 5.6 since it was already horked like that) a few days back here. I was going to post some google groups and/or openbsd.org links to the previous threaded posts, but I'm not having luck digging them up on google groups, and it appears that majordomo on the openbsd.org site won't give summaries from previous months. Regardless, I just wanted to find out... I usually get people willing to give some advice, or at least willing to laugh and tell me the lesson that I needed to know on here. I was really kind of surprised that I haven't heard anything back on this for so long... So, can anybody tell me, is my situation just so hosed that it's helpless? I mean, should I stop waiting for potential ways to fix this dependency hosed box and reinstall and try to find a way to re-inject all of my data into it, or are the gurus just swamped with new years tasks? :) If any of you could give me some feedback I'd really appreciate it. Like I said with the issue when I was first mentioning it, this system is really integral to a lot of the work that I do, and it's my sole external facing server... It's like a knife in my gut not having it working. Anything is very much appreciated. Feel free to hit me up via personal email, too, if you'd rather avoid public posting for some reason. I hope you all have a better year than last. :) -Damon
Re: bridge + vlan broke after 5.5 > 5.6 upgrade
This was fixed in one of the snapshots and was working so it likely got broken again somehow http://marc.info/?l=openbsd-cvs&m=141770981219927&w=2 - Original Message - | | | On 17/11/2014 04:51, James A. Peltier wrote: | > Was a fix for this applied to current or -STABLE? | > | | Just ran into this problem again on a testing box using -CURRENT, | Seems this has not been fixed :( | | Any idea who I should talk to get this into before 5.7 hits -STABLE? | | Regards | | -- | ~ sjorge | -- James A. Peltier IT Services - Research Computing Group Simon Fraser University - Burnaby Campus Phone : 778-782-6573 Fax : 778-782-3045 E-Mail : jpelt...@sfu.ca Website : http://www.sfu.ca/itservices Twitter : @sfu_rcg Powering Engagement Through Technology "Build upon strengths and weaknesses will generally take care of themselves" - Joyce C. Lock
Re: bridge + vlan broke after 5.5 > 5.6 upgrade
- Original Message - | Interesting, looks fine on cvs web view. | Yet the file on my box does not have the change. | | I will give it another go next week and instead of pulling in changes | start fresh. | | Regards | | Jorge I just had a look and it does seem to be working fine for me. VLAN tagging/untagging is working as expected. -- James A. Peltier IT Services - Research Computing Group Simon Fraser University - Burnaby Campus Phone : 778-782-6573 Fax : 778-782-3045 E-Mail : jpelt...@sfu.ca Website : http://www.sfu.ca/itservices Twitter : @sfu_rcg Powering Engagement Through Technology "Build upon strengths and weaknesses will generally take care of themselves" - Joyce C. Lock
Re: bridge + vlan broke after 5.5 > 5.6 upgrade
Interesting, looks fine on cvs web view. Yet the file on my box does not have the change. I will give it another go next week and instead of pulling in changes start fresh. Regards Jorge On 02/01/2015 20:59, James A. Peltier wrote: This was fixed in one of the snapshots and was working so it likely got broken again somehow http://marc.info/?l=openbsd-cvs&m=141770981219927&w=2 - Original Message - | | | On 17/11/2014 04:51, James A. Peltier wrote: | > Was a fix for this applied to current or -STABLE? | > | | Just ran into this problem again on a testing box using -CURRENT, | Seems this has not been fixed :( | | Any idea who I should talk to get this into before 5.7 hits -STABLE? | | Regards | | -- | ~ sjorge | -- ~ sjorge
Re: YP Alternative
Carson Chittom wrote: > There is ldapd(8) in base, though I've never used it myself. ldapd from the base is fine peace of software for small deployments. I have to OpenBSD LDAP servers with about 50-60 users each. Client machines besides of course OpenBSD machines consist of mixture Red Hat computing nodes and large FreeBSD data storages. I am using ldapd both for authentication and authorization. I use TLS for enhance LDAP traffic confidentiality and security even though everything happens behind multiple OpenBSD firewalls. I am very curious to hear if somebody is using Kerberos for authentication and ldapd for authorization. Predrag P.S. Feel free to contact me off the list if you need more info or quick and dirty feature comparison with full featured OpenLDAP
Re: YP Alternative
On Fri, 2 Jan 2015 18:36:38 + skin...@britvault.co.uk (Craig Skinner) wrote: >On 2015-01-02 Fri 13:06 PM |, Christopher Barry wrote: >> #!/bin/bash >> > >OpenBSD has much better ksh(1) > >A simple rdist(1) cronjob might do it. > >e.g: http://www.benedikt-stockebrand.de/rdist-intro_en.html > Hi Craig, I can't speak to ksh being 'better', but it may well be. I have 20 years experience with bash, so I default to it. If I was going to craft something today to solve this problem, I think I would probably use rsync over shh though, and not scp. My example was simply to show that it can be a not-very-complicated hammer and still work reasonably well. -- -C
Re: typo in calendar.ushistory
On Thu, Jan 01, 2015 at 11:40:11PM +, Jason McIntyre wrote: > On Thu, Jan 01, 2015 at 05:45:11PM -0500, Brian Callahan wrote: > > > > On 01/01/15 17:20, Jason McIntyre wrote: > > > On Thu, Jan 01, 2015 at 06:44:50AM -0600, Carson Chittom wrote: > > >> This is minor, but when I received my "Reminder Service" email from > > >> calendar(1) this morning, I noticed that there were a couple of typos. > > > you say couple, but i take it you mean regarding this one entry? > > > > > >> The entry for 01/02 in src/usr.bin/calendar/calendars/calendar.ushistory > > >> has "brittish american". I would suggest "British-American" instead. > > >> > > > i agree we should capitalise both British and American. i agree also > > > that british is more likely with one "t" than two. less persuaded about > > > that > > > hyphen though: > > > > But in this case the hyphen is correct. In this case, British and > > large sigh. hope you hear it. > ...famous last words. i've been mailing brian in private since this and he has pretty much proven me wrong: there is a section in oxford's style guide which recommends an en dash (or "rule", specifically) to "express the meaning of *to* or *and* between words of equal importance" in the context we're talking about. so carson;s original request, to hyphenate "British-American" seems correct. however i've no intention of changing the instance unless i'm handed a diff for all our calendar files making this type of change. i'd consider that. sorry for the mix up - my fault. jmc
Re: OpenBSD + OptiPlex 320 = frozen clock?
Try changing the value for the sysctl variable "kern.timecounter.hardware"? Its just a guess, but its helped me when I had problems with the clock before. On Fri, Jan 2, 2015 at 7:47 AM, John Merriam wrote: > Hello. I have a strange issue with OpenBSD on my Dell OptiPlex 320. The > clock doesn't move: > > # date; sleep 55; date > Thu Jan 1 02:25:47 EST 2015 > Thu Jan 1 02:25:47 EST 2015 > > I see the same behavior with 5.6-release amd64 and -current amd64. The > clock works fine in Windows and Linux on this machine. I installed the > December 27th snapshot on it so I can mess around with it and try to get it > fixed. Has anyone seen this before? If not, any tips on what to try or > where I should start looking in the code to try to figure out what's going > on? > > Below is the dmesg: > > OpenBSD 5.6-current (GENERIC.MP) #735: Sat Dec 27 13:55:58 MST 2014 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 3437608960 (3278MB) > avail mem = 3342295040 (3187MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xf0450 (68 entries) > bios0: vendor Dell Inc. version "1.1.12" date 06/17/2009 > bios0: Dell Inc. OptiPlex 320 > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S1 S3 S4 S5 > acpi0: tables DSDT FACP SSDT APIC BOOT MCFG HPET SLIC SSDT SSDT SSDT > acpi0: wakeup devices VBTN(S4) PCI0(S5) PCI7(S5) MAC1(S5) MOU_(S3) USB0(S3) > USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Core(TM)2 Duo CPU E4400 @ 2.00GHz, 2000.36 MHz > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF > cpu0: 2MB 64b/line 8-way L2 cache > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 200MHz > cpu0: mwait min=64, max=64, C-substates=0.2.2.0.0, IBE > cpu1 at mainbus0: apid 1 (application processor) > cpu1: Intel(R) Core(TM)2 Duo CPU E4400 @ 2.00GHz, 2000.08 MHz > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF > cpu1: 2MB 64b/line 8-way L2 cache > cpu1: smt 0, core 1, package 0 > ioapic0 at mainbus0: apid 8 pa 0xfec0, version 21, 24 pins > ioapic0: misconfigured as apic 0, remapped to apid 8 > acpimcfg0 at acpi0 addr 0xe000, bus 0-255 > acpihpet0 at acpi0: 14318180 Hz > acpiprt0 at acpi0: bus 1 (PCI1) > acpiprt1 at acpi0: bus -1 (PCI2) > acpiprt2 at acpi0: bus -1 (PCI3) > acpiprt3 at acpi0: bus -1 (PCI4) > acpiprt4 at acpi0: bus -1 (PCI5) > acpiprt5 at acpi0: bus -1 (PCI6) > acpiprt6 at acpi0: bus -1 (PCI8) > acpiprt7 at acpi0: bus 2 (PCI7) > acpiprt8 at acpi0: bus 0 (PCI0) > acpicpu0 at acpi0: PSS > acpicpu1 at acpi0: PSS > acpibtn0 at acpi0: VBTN > cpu0: Enhanced SpeedStep 2000 MHz: speeds: 2000, 1600, 1200 MHz > pci0 at mainbus0 bus 0 > 0:20:0: mem address conflict 0xfed0/0x400 > pchb0 at pci0 dev 0 function 0 "ATI RC410 Host" rev 0x01 > ppb0 at pci0 dev 1 function 0 "ATI RS480 PCIE" rev 0x00 > pci1 at ppb0 bus 1 > radeondrm0 at pci1 dev 5 function 0 "ATI Radeon XPRESS 200" rev 0x00 > drm0 at radeondrm0 > radeondrm0: apic 8 int 17 > ahci0 at pci0 dev 18 function 0 "ATI SB600 SATA" rev 0x00: apic 8 int 23, > AHCI 1.1 > scsibus1 at ahci0: 32 targets > sd0 at scsibus1 targ 0 lun 0: SCSI3 0/direct > fixed naa.50014ee201ce1451 > sd0: 476940MB, 512 bytes/sector, 976773168 sectors > cd0 at scsibus1 targ 1 lun 0: ATAPI 5/cdrom > removable > ohci0 at pci0 dev 19 function 0 "ATI SB600 USB" rev 0x00: apic 8 int 16, > version 1.0, legacy support > ohci1 at pci0 dev 19 function 1 "ATI SB600 USB" rev 0x00: apic 8 int 17, > version 1.0, legacy support > ohci2 at pci0 dev 19 function 2 "ATI SB600 USB" rev 0x00: apic 8 int 18, > version 1.0, legacy support > ohci3 at pci0 dev 19 function 3 "ATI SB600 USB" rev 0x00: apic 8 int 17, > version 1.0, legacy support > ohci4 at pci0 dev 19 function 4 "ATI SB600 USB" rev 0x00: apic 8 int 18, > version 1.0, legacy support > ehci0 at pci0 dev 19 function 5 "ATI SB600 USB2" rev 0x00: apic 8 int 19 > usb0 at ehci0: USB revision 2.0 > uhub0 at usb0 "ATI EHCI root hub" rev 2.00/1.00 addr 1 > piixpm0 at pci0 dev 20 function 0 "ATI SBx00 SMBus" rev 0x13: SMI > iic0 at piixpm0 > spdmem0 at iic0 addr 0x50: 2GB DDR2 SDRAM non-parity PC2-5300CL5 > spdmem1 at iic0 addr 0x51: 2GB DDR2 SDRAM non-parity PC2-5300CL5 > pciide0 at pci0 dev 20 function 1 "ATI SB600 IDE" rev 0x00: DMA, channel 0 > configured to compatibility, channel 1 configured to compatibility > azalia0 at pci0 dev 20 function 2 "ATI SBx00 HD Audio" rev 0x00: apic 8 int > 16 > azalia0: codecs: Analog Devices AD1983 > audio0
Re: YP Alternative
On 2015-01-02 Fri 13:06 PM |, Christopher Barry wrote: > #!/bin/bash > OpenBSD has much better ksh(1) A simple rdist(1) cronjob might do it. e.g: http://www.benedikt-stockebrand.de/rdist-intro_en.html
Re: YP Alternative
On Fri, 2 Jan 2015 13:44:36 +0100
Ingo Schwarze wrote:
>Hi Brian,
>
>Brian Empson wrote on Fri, Jan 02, 2015 at 06:52:40AM -0500:
>
>> I'm looking into a way to sync up group and user information across
>> a network of OpenBSD machines. I like YP, except that I don't need
>> the password hashes transferred across the network. I like that it's
>> built right into the base install, are there better ways to handle
>> synchronizing login details across multiple machines that is built
>> into the base install? Preferably written by the OpenBSD team, too?
>
>http://www.openbsd.org/faq/faq10.html#Dir
>
>Yours,
> Ingo
>
With ssh keys for root setup between the 'master' box and the rest of
your machines, something as simple as this can be fairly effective in a
small environment. All changes to users and passwords will need to
happen on the master though, and this will need to be run afterward to
sync them.
CUT==
#!/bin/bash
list=( /etc/passwd /etc/group /etc/shadow /etc/gshadow )
while read host; do
(
for (( i = 0; i < ${#list[*]}; i++ )); do
scp ${list[$i]} ${host}:${list[$i]} || {
echo "scp ${list[$i]} ${host}:${list[$i]} failed" }
done &
) &
done < list-of-additional-hosts.txt
CUT==
This reads a list of hosts, one host per line (could use /etc/hosts
with some parsing), then for each host spawns a subprocess in parallel,
and scp's all the files to each host in parallel.
disclaimer - I just typed this and didn't actually test it, but I've
done similar in small linux cluster configurations. You'll write
a more complete and robust one of course, but you can see the idea here.
You may want to consider automounting everyone's $HOME from a network
location as well, so everyone's stuff is available everywhere. Doing
that securely is a matter for additional debate though.
--
Regards,
Christopher Barry
Random geeky fortune:
Fourth Law of Thermodynamics:
If the probability of success is not almost one, it is damn
near zero. -- David Ellis
OpenBSD + OptiPlex 320 = frozen clock?
Hello. I have a strange issue with OpenBSD on my Dell OptiPlex 320. The clock doesn't move: # date; sleep 55; date Thu Jan 1 02:25:47 EST 2015 Thu Jan 1 02:25:47 EST 2015 I see the same behavior with 5.6-release amd64 and -current amd64. The clock works fine in Windows and Linux on this machine. I installed the December 27th snapshot on it so I can mess around with it and try to get it fixed. Has anyone seen this before? If not, any tips on what to try or where I should start looking in the code to try to figure out what's going on? Below is the dmesg: OpenBSD 5.6-current (GENERIC.MP) #735: Sat Dec 27 13:55:58 MST 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3437608960 (3278MB) avail mem = 3342295040 (3187MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xf0450 (68 entries) bios0: vendor Dell Inc. version "1.1.12" date 06/17/2009 bios0: Dell Inc. OptiPlex 320 acpi0 at bios0: rev 2 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP SSDT APIC BOOT MCFG HPET SLIC SSDT SSDT SSDT acpi0: wakeup devices VBTN(S4) PCI0(S5) PCI7(S5) MAC1(S5) MOU_(S3) USB0(S3) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 Duo CPU E4400 @ 2.00GHz, 2000.36 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF cpu0: 2MB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 200MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.0.0, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 Duo CPU E4400 @ 2.00GHz, 2000.08 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF cpu1: 2MB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 8 pa 0xfec0, version 21, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 8 acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 1 (PCI1) acpiprt1 at acpi0: bus -1 (PCI2) acpiprt2 at acpi0: bus -1 (PCI3) acpiprt3 at acpi0: bus -1 (PCI4) acpiprt4 at acpi0: bus -1 (PCI5) acpiprt5 at acpi0: bus -1 (PCI6) acpiprt6 at acpi0: bus -1 (PCI8) acpiprt7 at acpi0: bus 2 (PCI7) acpiprt8 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0: PSS acpicpu1 at acpi0: PSS acpibtn0 at acpi0: VBTN cpu0: Enhanced SpeedStep 2000 MHz: speeds: 2000, 1600, 1200 MHz pci0 at mainbus0 bus 0 0:20:0: mem address conflict 0xfed0/0x400 pchb0 at pci0 dev 0 function 0 "ATI RC410 Host" rev 0x01 ppb0 at pci0 dev 1 function 0 "ATI RS480 PCIE" rev 0x00 pci1 at ppb0 bus 1 radeondrm0 at pci1 dev 5 function 0 "ATI Radeon XPRESS 200" rev 0x00 drm0 at radeondrm0 radeondrm0: apic 8 int 17 ahci0 at pci0 dev 18 function 0 "ATI SB600 SATA" rev 0x00: apic 8 int 23, AHCI 1.1 scsibus1 at ahci0: 32 targets sd0 at scsibus1 targ 0 lun 0: SCSI3 0/direct fixed naa.50014ee201ce1451 sd0: 476940MB, 512 bytes/sector, 976773168 sectors cd0 at scsibus1 targ 1 lun 0: ATAPI 5/cdrom removable ohci0 at pci0 dev 19 function 0 "ATI SB600 USB" rev 0x00: apic 8 int 16, version 1.0, legacy support ohci1 at pci0 dev 19 function 1 "ATI SB600 USB" rev 0x00: apic 8 int 17, version 1.0, legacy support ohci2 at pci0 dev 19 function 2 "ATI SB600 USB" rev 0x00: apic 8 int 18, version 1.0, legacy support ohci3 at pci0 dev 19 function 3 "ATI SB600 USB" rev 0x00: apic 8 int 17, version 1.0, legacy support ohci4 at pci0 dev 19 function 4 "ATI SB600 USB" rev 0x00: apic 8 int 18, version 1.0, legacy support ehci0 at pci0 dev 19 function 5 "ATI SB600 USB2" rev 0x00: apic 8 int 19 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "ATI EHCI root hub" rev 2.00/1.00 addr 1 piixpm0 at pci0 dev 20 function 0 "ATI SBx00 SMBus" rev 0x13: SMI iic0 at piixpm0 spdmem0 at iic0 addr 0x50: 2GB DDR2 SDRAM non-parity PC2-5300CL5 spdmem1 at iic0 addr 0x51: 2GB DDR2 SDRAM non-parity PC2-5300CL5 pciide0 at pci0 dev 20 function 1 "ATI SB600 IDE" rev 0x00: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility azalia0 at pci0 dev 20 function 2 "ATI SBx00 HD Audio" rev 0x00: apic 8 int 16 azalia0: codecs: Analog Devices AD1983 audio0 at azalia0 pcib0 at pci0 dev 20 function 3 "ATI SB600 ISA" rev 0x00 ppb1 at pci0 dev 20 function 4 "ATI SB600 PCI" rev 0x00 pci2 at ppb1 bus 2 rl0 at pci2 dev 2 function 0 "Realtek 8139" rev 0x10: apic 8 int 22, address 00:40:f4:6c:99:b2 rlphy0 at rl0 phy 0: RTL internal PHY bce0 at pci2 dev 9 function 0 "Broadcom BCM4401B1" rev 0x02: apic 8 int 21, address 00:1d:09:16:ca:2e bm
interpreting ACPI bat values
Hi all, I want to give batmon.app ACPI support on OpenBSD. This is what I get on my Thinkpad T60: $ sysctl | grep acpibat hw.sensors.acpibat0.volt0=10.80 VDC (voltage) hw.sensors.acpibat0.volt1=12.41 VDC (current voltage) hw.sensors.acpibat0.power0=0.00 W (rate) hw.sensors.acpibat0.watthour0=47.16 Wh (last full capacity) hw.sensors.acpibat0.watthour1=2.36 Wh (warning capacity) hw.sensors.acpibat0.watthour2=0.20 Wh (low capacity) hw.sensors.acpibat0.watthour3=47.16 Wh (remaining capacity), OK hw.sensors.acpibat0.watthour4=47.52 Wh (design capacity) hw.sensors.acpibat0.raw0=0 (battery full), OK Some questions. If I had another battery, would I get exactly the same stuff a second time but e.g. with "acpibat1" ? I suppose yes. I need to interpret always e.g. the "remaining capacity" in such a way that it works across different laptop models. Is it reliable to always read "watthour3" ? Or can I trust the description "remaining capacity"? or neither? To know if the laptop is attached to a power source and to know if it is charging or discharging, what can I use? I "acpiac0" tells me if I am attached o a power outlet or not, I suppose: hw.sensors.acpiac0.indicator0=On (power supply) hw.sensors.acpiac0.indicator0=Off (power supply) however this doesn't tell me yet if it is charging. Should I check this? hw.sensors.acpibat0.raw0=1 (battery discharging), OK hw.sensors.acpibat0.raw0=0 (battery idle), OK hw.sensors.acpibat0.raw0=0 (battery full), OK being "raw0" it seems that I need to check the description of the item instead of the actual value which is only 0 or 1, which is less desirable Riccardo
Re: YP Alternative
Brian Empson writes: > I'm looking into a way to sync up group and user information across a > network of OpenBSD machines. I like YP, except that I don't need the > password hashes transferred across the network. I like that it's built > right into the base install, are there better ways to handle > synchronizing login details across multiple machines that is built > into the base install? Preferably written by the OpenBSD team, too? There is ldapd(8) in base, though I've never used it myself. -- http://www.wistly.net
Re: YP Alternative
Hi Brian, Brian Empson wrote on Fri, Jan 02, 2015 at 06:52:40AM -0500: > I'm looking into a way to sync up group and user information across > a network of OpenBSD machines. I like YP, except that I don't need > the password hashes transferred across the network. I like that it's > built right into the base install, are there better ways to handle > synchronizing login details across multiple machines that is built > into the base install? Preferably written by the OpenBSD team, too? http://www.openbsd.org/faq/faq10.html#Dir Yours, Ingo
Re: MEDION S4222 UMTS stick not recognized
On Fri, 2 Jan 2015 12:26:53 +0100 Ingo Feinerer wrote: > The manual of the stick claims that "Linux 2.6" (or newer) is > supported (if this is of any help). > this need "usb mode switch" under linux, searching on google there no solution yet even compiling from source for openbsd.
YP Alternative
I'm looking into a way to sync up group and user information across a network of OpenBSD machines. I like YP, except that I don't need the password hashes transferred across the network. I like that it's built right into the base install, are there better ways to handle synchronizing login details across multiple machines that is built into the base install? Preferably written by the OpenBSD team, too? Thanks, Brian
MEDION S4222 UMTS stick not recognized
Hello, a MEDION S4222 UMTS (https://www.hot.at/images/medion_usb_stick.png) stick port 2 addr 4: high speed, power 500 mA, config 1, Product(0x0002), MediaTek Inc(0x0e8d), rev 3.00, iSerialNumber 683694200024400 attaches as CDROM umass0 at uhub7 port 2 configuration 1 interface 0 "MediaTek Inc Product" rev 2.00/3.00 addr 4 umass0: using SCSI over Bulk-Only scsibus4 at umass0: 2 targets, initiator 0 cd0 at scsibus4 targ 1 lun 0: SCSI0 5/cdrom removable serial.0e8d0002694200024400 but the logic is missing to switch to modem mode. I tried various combinations via sys/dev/usb/umsm.c but did not manage to get ucom attached. The manual of the stick claims that "Linux 2.6" (or newer) is supported (if this is of any help). Any ideas? Thank you very much. Best regards, Ingo dmesg = OpenBSD 5.6-current (GENERIC.MP) #731: Tue Dec 23 12:12:38 MST 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 80 real mem = 4200173568 (4005MB) avail mem = 4084494336 (3895MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe3400 (39 entries) bios0: vendor Intel Corp. version "MQ96510J.86A.1754.2008.1117.0002" date 11/17/2008 bios0: Intel Corporation DG965WH acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC WDDT MCFG ASF! HPET SSDT SSDT SSDT SSDT SSDT acpi0: wakeup devices SLPB(S4) P32_(S4) UAR1(S4) UAR2(S4) ILAN(S4) PEGP(S4) PEX0(S4) PEX1(S4) PEX2(S4) PEX3(S4) PEX4(S4) PEX5(S4) UHC1(S3) UHC2(S3) UHC3(S3) UHC4(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz, 2397.92 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF cpu0: 4MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 266MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz, 2397.61 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF cpu1: 4MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 2 acpimcfg0 at acpi0 addr 0xf000, bus 0-127 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 6 (P32_) acpiprt2 at acpi0: bus 1 (PEX0) acpiprt3 at acpi0: bus 2 (PEX1) acpiprt4 at acpi0: bus 3 (PEX2) acpiprt5 at acpi0: bus 4 (PEX3) acpiprt6 at acpi0: bus 5 (PEX4) acpiprt7 at acpi0: bus -1 (PEX5) acpicpu0 at acpi0: PSS acpicpu1 at acpi0: PSS acpibtn0 at acpi0: SLPB cpu0: Enhanced SpeedStep 2397 MHz: speeds: 2394, 1596 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 82G965 Host" rev 0x02 vga1 at pci0 dev 2 function 0 "Intel 82G965 Video" rev 0x02 intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1920x1080 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) "Intel 82G965 HECI" rev 0x02 at pci0 dev 3 function 0 not configured uhci0 at pci0 dev 26 function 0 "Intel 82801H USB" rev 0x02: apic 2 int 16 uhci1 at pci0 dev 26 function 1 "Intel 82801H USB" rev 0x02: apic 2 int 21 ehci0 at pci0 dev 26 function 7 "Intel 82801H USB" rev 0x02: apic 2 int 18 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 ppb0 at pci0 dev 28 function 0 "Intel 82801H PCIE" rev 0x02: msi pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 1 "Intel 82801H PCIE" rev 0x02: msi pci2 at ppb1 bus 2 pciide0 at pci2 dev 0 function 0 "Marvell 88SE6101 IDE" rev 0xb1: DMA (unsupported), channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide0: using apic 2 int 17 for native-PCI interrupt pciide0: channel 0 ignored (not responding; disabled or no drives?) pciide0: channel 1 ignored (not responding; disabled or no drives?) ppb2 at pci0 dev 28 function 2 "Intel 82801H PCIE" rev 0x02: msi pci3 at ppb2 bus 3 ppb3 at pci0 dev 28 function 3 "Intel 82801H PCIE" rev 0x02: msi pci4 at ppb3 bus 4 ppb4 at pci0 dev 28 function 4 "Intel 82801H PCIE" rev 0x02: msi pci5 at ppb4 bus 5 uhci2 at pci0 dev 29 function 0 "Intel 82801H USB" rev 0x02: apic 2 int 23 uhci3 at pci0 dev 29 function 1 "Intel 82801H USB" rev 0x02: apic 2 int 19 uhci4 at pci0 dev 29 function 2 "Intel 82801H USB" rev 0x02: apic 2 int 18 ehci1 at pci0 dev 29 function 7 "Intel 82801H USB" rev 0x02: apic 2 int 23 usb1 at ehci1: USB rev
Re: bridge + vlan broke after 5.5 > 5.6 upgrade
On 17/11/2014 04:51, James A. Peltier wrote: > Was a fix for this applied to current or -STABLE? > Just ran into this problem again on a testing box using -CURRENT, Seems this has not been fixed :( Any idea who I should talk to get this into before 5.7 hits -STABLE? Regards -- ~ sjorge
