Re: Watchdog timeout with MSI and Realtek 8101E on Dell Inspiron 3521 (amd64)
Francois Ambrosini [francois.ambros...@famb.info] wrote: After upgrading from the July 25 to the August 24 snapshot (amd64), I started getting re0: watchdog timeout messages from the system when sending files via re0. This seems to be caused by MSI being enabled in sys/dev/pci/if_re_pci.c beginning of August. Upgrading the BIOS to the latest version (A09) did not solve the issue. Mark Kettenis just posted a patch to disable (and later re-enable) interrupts at some point in the driver. It's on the openbsd-tech list, dated Aug 21. Try and and see if it fixes your issue, as it appears nobody else has done so yet. -- scio me nihil scire or scio me nescire
Re: OpenBSD 5.3, CARP and IPv6
On 29/08/13 18:37, Todd T. Fries wrote:
Penned by Andy on 20130829 9:57.29, we have:
| Hi everyone,
|
| I'm hoping someone can help me as I'm not having much luck with adding
| IPv6 to the mix of our already working IPv4 setup.
|
| What should /etc/hostname.carpX look like for an IPv6 setup? Is this
| correct;?
|
| inet 10.0.10.1 255.255.255.0 10.0.10.255 vhid 1 pass temppass advbase 3
| advskew 0
| inet6 2a00:7e0:0:a::1 64
Any 'inet6' except the first link local reference in a given hostname.if(4)
file should be followed by 'alias'.
Aka you need:
inet6 alias 2a00:7e0:0:a::1
The 64 is implicitly default, if you choose to explicitly list it thats ok too.
Hi guys,
Adding the inet6 as an alias didn't work for me.
When the first line is an 'inet' entry, adding an inet6 alias results in
errors when running /etc/netstart :(
And trying;
inet 194.199.X.28 255.255.255.240 NONE
inet6 2001:660:abcd:1234::1:1 64
description CARP server
carpdev vlan603 vhid 62 advskew 1 carppeer 194.199.X.29 pass x
Resulted in multi-master (no flip-flopping but permanently multi-master)
even if I removed the carpdev and carppeer attributes :(
I have tested both of these with PF disabled just encase a rule was
messing things up.
With pf enabled, does this rule satisfy CARP and is it sensible?;
pass in quick proto carp from { fe80::/8 } to { ff00::/8 } keep state
(no-sync)
The only way I have managed to get this to work with 5.3 is separate
carp devices, if I have to run two of course I will, but I would really
like to get it working under one for clarity.
PS; Todd,
Thanks you very much for your detailed thoughts on IPv6 regarding
filtering icmp6, ndp. Really appreciate your time to help.
For ndp is this rule sensible?;
pass quick proto icmp6 from { ff00::/8 } to { ff00::/8 }
I have just set-up an he.net tunnel at home ;)
Cheers :)
Andy.
php-5.4.19
HI! Auuu! :) Where is php-5.4.19? #pkg_add -u [12:51] quirks-1.90: ok asterisk-11.5.1-imap:ffmpeg-20130319-20130718: ok asterisk-11.5.0-imap-11.5.1-imap: ok mplayer-20130214p4-20130214p5: ok nfsen-1.3.6pl1p2-1.3.6pl1p2: ok Error from http://ftp.eu.openbsd.org/pub/OpenBSD/snapshots/packages/i386/php-5.4.19.tgz ftp: Error retrieving file: 404 Not Found Error from http://ftp.eu.openbsd.org/pub/OpenBSD/snapshots/packages/i386/php-5.4.19.tgz ftp: Error retrieving file: 404 Not Found Error from http://ftp.eu.openbsd.org/pub/OpenBSD/snapshots/packages/i386/php-5.4.19.tgz ftp: Error retrieving file: 404 Not Found Error from http://ftp.eu.openbsd.org/pub/OpenBSD/snapshots/packages/i386/php-5.4.19.tgz ftp: Error retrieving file: 404 Not Found Error from http://ftp.eu.openbsd.org/pub/OpenBSD/snapshots/packages/i386/php-5.4.19.tgz ftp: Error retrieving file: 404 Not Found Can't find php-5.4.19 Can't install php-pgsql-5.4.17p0-5.4.19: can't resolve php-5.4.19 Alex.
Re: user can not shutdown PC in xfce
-- Original -- From: Tomas Bodzartomas.bod...@gmail.com; On Tue, Aug 27, 2013 at 2:34 PM, Fung fungm...@qq.com wrote: 1. root login xfce can shutdown the pc smoothly using mouse. 2. other user in xfce can not shutdown the pc, why? # visudo ... %wheel ALL=(ALL) SETENV: ALL share ALL=NOPASSWD: /usr/local/lib/xfce4/session/xfsm-shutdown-helper ... # id share uid=1000(share) gid=1000(share) groups=1000(share), 0(wheel) # sysctl kern.version kern.version=OpenBSD 5.4-current (GENERIC.MP) #48: Sat Aug 24 20:31:41 MDT 2013 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP # cat /usr/local/share/doc/pkg-readmes/xfce-4.10p0 said Logging out and shutting down the computer == If your installation supports complete shutdown, clicking on the logout button on panel will permit you to either logout, rebooting or halt the computer, provided you have the needed sudo credentials. If you don't want to have to enter your password, simply add this line to the /etc/sudoers file using visudo: $your_username ALL=NOPASSWD: /usr/local/lib/xfce4/session/xfsm-shutdown-helper == are you in operator group? ;-) $ ls -l /sbin/shutdown -r-sr-x--- 1 root operator 222416 Aug 20 00:46 /sbin/shutdown $ . hi, tomas, Shutdown in xfce not work with operator group . BTW, from terminal , user share can halt -p/ shutdown the system.
Re: Compiling BOINC/Seti at Home for OpenBSD 5.3 Sparc64
On 2013-08-29 Thu 17:02 PM |, Daniel Ouellet wrote: Wonder why keep running something doing nothing ;) Still happily married I see. (: Install a network of multiple machines at home. There'll be lots to do.. -- Craig Skinner | http://twitter.com/Craig_Skinner | http://linkd.in/yGqkv7
Re: user can not shutdown PC in xfce
!-- On Fri 30.Aug'13 at 9:08:05 BST, Fung (fungm...@qq.com), wrote: -- Original -- From: Tomas Bodzartomas.bod...@gmail.com; On Tue, Aug 27, 2013 at 2:34 PM, Fung fungm...@qq.com wrote: 1. root login xfce can shutdown the pc smoothly using mouse. 2. other user in xfce can not shutdown the pc, why? # visudo ... %wheel ALL=(ALL) SETENV: ALL share ALL=NOPASSWD: /usr/local/lib/xfce4/session/xfsm-shutdown-helper ... # id share uid=1000(share) gid=1000(share) groups=1000(share), 0(wheel) # sysctl kern.version kern.version=OpenBSD 5.4-current (GENERIC.MP) #48: Sat Aug 24 20:31:41 MDT 2013 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP # cat /usr/local/share/doc/pkg-readmes/xfce-4.10p0 said Logging out and shutting down the computer == If your installation supports complete shutdown, clicking on the logout button on panel will permit you to either logout, rebooting or halt the computer, provided you have the needed sudo credentials. If you don't want to have to enter your password, simply add this line to the /etc/sudoers file using visudo: $your_username ALL=NOPASSWD: /usr/local/lib/xfce4/session/xfsm-shutdown-helper == are you in operator group? ;-) $ ls -l /sbin/shutdown -r-sr-x--- 1 root operator 222416 Aug 20 00:46 /sbin/shutdown $ . hi, tomas, Shutdown in xfce not work with operator group . BTW, from terminal , user share can halt -p/ shutdown the system. You could use a better Window Manager/Desktop. The cwm in base is excellent. Also, fvwm2 in packages is excellent (I use that one), so are some tiling WM's, like dwm and spectrwm. -- James Griffin: jmz at kontrol.kode5.net A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: user can not shutdown PC in xfce
When I want to shut down, I use on/off switch. No permissions needed. Sent from my BlackBerry 10 smartphone on the Verizon Wireless 4G LTE network. From: James GriffinSent: Friday, August 30, 2013 6:00 AMTo: misc@openbsd.orgSubject: Re: user can not shutdown PC in xfce !-- On Fri 30.Aug'13 at 9:08:05 BST, Fung (fungm...@qq.com), wrote: -- Original -- From: Tomas Bodzartomas.bod...@gmail.com; On Tue, Aug 27, 2013 at 2:34 PM, Fung fungm...@qq.com wrote: 1. root login xfce can shutdown the pc smoothly using mouse. 2. other user in xfce can not shutdown the pc, why? # visudo ... %wheel ALL=(ALL) SETENV: ALL share ALL=NOPASSWD: /usr/local/lib/xfce4/session/xfsm-shutdown-helper ... # id share uid=1000(share) gid=1000(share) groups=1000(share), 0(wheel) # sysctl kern.version kern.version=OpenBSD 5.4-current (GENERIC.MP) #48: Sat Aug 24 20:31:41 MDT 2013 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP # cat /usr/local/share/doc/pkg-readmes/xfce-4.10p0 said Logging out and shutting down the computer == If your installation supports complete shutdown, clicking on the logout button on panel will permit you to either logout, rebooting or halt the computer, provided you have the needed sudo credentials. If you don't want to have to enter your password, simply add this line to the /etc/sudoers file using visudo: $your_username ALL=NOPASSWD: /usr/local/lib/xfce4/session/xfsm-shutdown-helper == are you in operator group? ;-) $ ls -l /sbin/shutdown -r-sr-x--- 1 root operator 222416 Aug 20 00:46 /sbin/shutdown $ . hi, tomas, Shutdown in xfce not work with operator group . BTW, from terminal , user share can halt -p/ shutdown the system. You could use a better Window Manager/Desktop. The cwm in base is excellent. Also, fvwm2 in packages is excellent (I use that one), so are some tiling WM's, like dwm and spectrwm. -- James Griffin: jmz at kontrol.kode5.net A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: OpenBSD 5.3, CARP and IPv6
On Fri, Aug 30, 2013 at 10:08:56AM +0100, Andy wrote:
Hi guys,
Adding the inet6 as an alias didn't work for me.
When the first line is an 'inet' entry, adding an inet6 alias
results in errors when running /etc/netstart :(
I never had a need to use 'alias' for IPv6 addresses, even
when adding multiple addresses to an interface with ifconfig.
And trying;
inet 194.199.X.28 255.255.255.240 NONE
inet6 2001:660:abcd:1234::1:1 64
description CARP server
carpdev vlan603 vhid 62 advskew 1 carppeer 194.199.X.29 pass x
Resulted in multi-master (no flip-flopping but permanently
multi-master) even if I removed the carpdev and carppeer attributes
:(
I believe the carpdev needs an address in the same prefix as the carp
interface for things to work, because carp uses that information
to locate the carpdev for sending IPv6 multicast. Does the vlan603
interface have an IPv6 address in prefix 2001:660:abcd:1234::/64?
The config I use looks somewhat like this, and works fine for
both IPv4 and IPv6. Note that the carp peers' em interfaces
are plugged into a common switch and are not filtered by pf.
# cat hostname.em0
inet 10.2.84.33 255.255.255.0 NONE
inet6 2001:660:abcd:11::1 64
# cat /etc/hostname.carp0
inet 10.2.84.46 255.255.255.0 NONE vhid 1 pass xxx advbase 10
inet6 2001:660:abcd:11::14 64 vhid 1 pass xxx advbase 10
And on the slave:
# cat hostname.em0
inet 10.2.84.43 255.255.255.0 NONE
inet6 2001:660:abcd:11::11 64
# cat /etc/hostname.carp0
inet 10.2.84.46 255.255.255.0 NONE vhid 1 pass xxx advbase 10 advskew 200
inet6 2001:660:abcd:11::14 64 vhid 1 pass xxx advbase 10 advskew 200
Carp multicast traffic is broadcast across the entire LAN.
But it is authenticated so it cannot be spoofed (the password can
be up to 32 chars in length). I see no way around that unless someone
adds 'carppeer' support for IPv6. The carppeer option only works for
IPv4 right now, probably due to lack of time and personal itch.
ip_carp.c:carp_send_ad() would be the place to start hacking.
I have tested both of these with PF disabled just encase a rule was
messing things up.
With pf enabled, does this rule satisfy CARP and is it sensible?;
pass in quick proto carp from { fe80::/8 } to { ff00::/8 } keep
state (no-sync)
Carp sends from fe80::/8 to ff02::/8.
If you can link your firewalls via a trusted network you could
probably just 'skip' the carpdev in pf.conf.
The only way I have managed to get this to work with 5.3 is separate
carp devices, if I have to run two of course I will, but I would
really like to get it working under one for clarity.
Not sure why that worked. Hard to tell without knowing how
your other interfaces are configured.
Re: OpenBSD 5.3, CARP and IPv6
On 2013-08-29, Todd T. Fries t...@fries.net wrote: Any 'inet6' except the first link local reference in a given hostname.if(4) file should be followed by 'alias'. Aka you need: inet6 alias 2a00:7e0:0:a::1 alias shouldn't be needed for v6, addresses added to an interface are always treated as additional addresses..
Re: OpenBSD 5.3, CARP and IPv6
On 2013-08-29, Andy a...@brandwatch.com wrote: PS; I don't have MLD capable switches in all locations if that is a factor here regarding CARP messages being via IPv6 Multicast. Not a problem - this just means the frames get flooded to all ports in the vlan in that case (whereas if your switches could do MLD snooping then frames going to ports not interested in them would be filtered). This can be important for high bandwidth multicast (video, disk images, etc) but shouldn't matter for carp. Or should I have a separate carpX interface for the IPv6? same interface is fine.
Re: user can not shutdown PC in xfce
When I want to shut down, I use on/off switch. No permissions needed. I am evaluating parts for improving my OpenBSD desktops but xfce4-session is not part of it so I haven't chimed in yet as I thought others may do a better job. However on Linux such as my TV's I always have a console user auto logged in as well as a different user logged into X11 and multiple users logged in says shutdown is not authorised even though ctrl-alt-del works. With Linux becoming more annoying with regard to ease or allowance of configuration and providing terrible documentation especially man pages combined with me often disabling the pointless polkit, I found a much preferred option. So on XFCE I use a launcher with sudo shutdown -h now and sudo /usr/sbin/pm-suspendhybrid as two icons with the advanced option arrow button position - inside button so that it is not accidentally pressed. A bonus is you get a nice looking shutdown button that everyone understands rather than their own name preventing them from finding how to shut the system down which is just one step from Gnome3 rediculousness requiring alt to show the power down option. Thankfully mythtv is nice and easily configurable and hasn't gone down the redhat you must use our shitzle route and allows the command changing to sudo shutdown -h now too. The real joke is login managers that now use your possibly non unique real name rather than your guaranteed unique user name. It is annoyingly amusing when all you have is three Kevin Chadwicks to choose from. Do people just do things without thinking or being beaten into a pulp on mailing lists these days? -- ___ 'Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface' (Doug McIlroy) ___
Re: OpenBSD 5.3, CARP and IPv6
Thank you for all your help guys :)
I finally figured out what I was doing wrong (including one of the
problems being that I forgot to turn on one of the lab switches this
morning (not enough coffee!) ;)
For others, here is what I have done to get IPv6 working so far with one
CARP interface per subnet;
sysctl.conf;
net.inet.carp.allow=1
net.inet.carp.preempt=1
net.inet.carp.log=3
net.inet6.ip6.forwarding=1
net.inet6.ip6.redirect=0
net.inet6.ip6.accept_rtadv=0
allow carp;
pass quick proto carp from { fe80::/8 } to { ff00::/8 } keep state (no-sync)
allow ndp;
pass quick proto icmp6 from { ff00::/8 } to { ff00::/8 }
/etc/hostname.*;
cat /etc/hostname.em0
inet 18.2.32.11 255.255.255.0
inet6 a00:7e0::b 64
cat /etc/hostname.em1
inet 10.0.10.2 255.255.255.0
inet6 a00:7e0:0:a::2 64
cat /etc/hostname.carp0
inet 18.2.32.10 255.255.255.0 18.2.32.255
inet6 a00:7e0::a 64
carpdev em0 carppeer 18.2.32.12 vhid 201 pass testpass advbase 3 advskew
0 description WAN
cat /etc/hostname.carp1
inet 10.0.10.1 255.255.255.0 10.0.10.255
inet6 a00:7e0:0:a::1 64
carpdev em1 carppeer 10.0.10.3 vhid 1 pass testpass advbase 3 advskew 0
description LAN
To enable IPv6 on Cisco;
interface GigabitEthernet0/0/1
ip address 18.2.32.1 255.255.255.0
ipv6 address a00:7e0::1/64
ipv6 unicast-routing
Cheers, Andy.
On 30/08/13 11:18, Stefan Sperling wrote:
On Fri, Aug 30, 2013 at 10:08:56AM +0100, Andy wrote:
Hi guys,
Adding the inet6 as an alias didn't work for me.
When the first line is an 'inet' entry, adding an inet6 alias
results in errors when running /etc/netstart :(
I never had a need to use 'alias' for IPv6 addresses, even
when adding multiple addresses to an interface with ifconfig.
And trying;
inet 194.199.X.28 255.255.255.240 NONE
inet6 2001:660:abcd:1234::1:1 64
description CARP server
carpdev vlan603 vhid 62 advskew 1 carppeer 194.199.X.29 pass x
Resulted in multi-master (no flip-flopping but permanently
multi-master) even if I removed the carpdev and carppeer attributes
:(
I believe the carpdev needs an address in the same prefix as the carp
interface for things to work, because carp uses that information
to locate the carpdev for sending IPv6 multicast. Does the vlan603
interface have an IPv6 address in prefix 2001:660:abcd:1234::/64?
The config I use looks somewhat like this, and works fine for
both IPv4 and IPv6. Note that the carp peers' em interfaces
are plugged into a common switch and are not filtered by pf.
# cat hostname.em0
inet 10.2.84.33 255.255.255.0 NONE
inet6 2001:660:abcd:11::1 64
# cat /etc/hostname.carp0
inet 10.2.84.46 255.255.255.0 NONE vhid 1 pass xxx advbase 10
inet6 2001:660:abcd:11::14 64 vhid 1 pass xxx advbase 10
And on the slave:
# cat hostname.em0
inet 10.2.84.43 255.255.255.0 NONE
inet6 2001:660:abcd:11::11 64
# cat /etc/hostname.carp0
inet 10.2.84.46 255.255.255.0 NONE vhid 1 pass xxx advbase 10 advskew 200
inet6 2001:660:abcd:11::14 64 vhid 1 pass xxx advbase 10 advskew 200
Carp multicast traffic is broadcast across the entire LAN.
But it is authenticated so it cannot be spoofed (the password can
be up to 32 chars in length). I see no way around that unless someone
adds 'carppeer' support for IPv6. The carppeer option only works for
IPv4 right now, probably due to lack of time and personal itch.
ip_carp.c:carp_send_ad() would be the place to start hacking.
I have tested both of these with PF disabled just encase a rule was
messing things up.
With pf enabled, does this rule satisfy CARP and is it sensible?;
pass in quick proto carp from { fe80::/8 } to { ff00::/8 } keep
state (no-sync)
Carp sends from fe80::/8 to ff02::/8.
If you can link your firewalls via a trusted network you could
probably just 'skip' the carpdev in pf.conf.
The only way I have managed to get this to work with 5.3 is separate
carp devices, if I have to run two of course I will, but I would
really like to get it working under one for clarity.
Not sure why that worked. Hard to tell without knowing how
your other interfaces are configured.
Re: Compiling BOINC/Seti at Home for OpenBSD 5.3 Sparc64
You are right. I am using a virtual installation right now until I figure it all out. Sent from my BlackBerry 10 smartphone on the Verizon Wireless 4G LTE network. From: Daniel OuelletSent: Thursday, August 29, 2013 6:19 PMTo: misc@openbsd.orgSubject: Re: Compiling BOINC/Seti at Home for OpenBSD 5.3 Sparc64 On 8/29/2013 4:15 PM, Alexey E. Suslikov wrote: Christian Weisgerber naddy at mips.inka.de writes: Richard Thornton thornton.richard at gmail.com wrote: My Sun Blade 100, has a fresh install of 5.3, and its very good, much better than 5.1; XFCE is very stable and R is much better than prior ports. you guys did a great job! Now this computer sits running actively, with nothing to do! Use apm -L or -C and save 10 W. Wonder why keep running something doing nothing ;) Still happily married I see. (:
Re: OpenBSD 5.3, CARP and IPv6
Penned by Andy on 20130830 4:08.56, we have:
| On 29/08/13 18:37, Todd T. Fries wrote:
| Penned by Andy on 20130829 9:57.29, we have:
| | Hi everyone,
| |
| | I'm hoping someone can help me as I'm not having much luck with adding
| | IPv6 to the mix of our already working IPv4 setup.
| |
| | What should /etc/hostname.carpX look like for an IPv6 setup? Is this
| | correct;?
| |
| | inet 10.0.10.1 255.255.255.0 10.0.10.255 vhid 1 pass temppass advbase 3
| | advskew 0
| | inet6 2a00:7e0:0:a::1 64
|
| Any 'inet6' except the first link local reference in a given hostname.if(4)
| file should be followed by 'alias'.
|
| Aka you need:
|
| inet6 alias 2a00:7e0:0:a::1
|
| The 64 is implicitly default, if you choose to explicitly list it thats ok
too.
|
| Hi guys,
|
| Adding the inet6 as an alias didn't work for me.
| When the first line is an 'inet' entry, adding an inet6 alias
| results in errors when running /etc/netstart :(
|
|
| And trying;
| inet 194.199.X.28 255.255.255.240 NONE
| inet6 2001:660:abcd:1234::1:1 64
| description CARP server
| carpdev vlan603 vhid 62 advskew 1 carppeer 194.199.X.29 pass x
|
| Resulted in multi-master (no flip-flopping but permanently
| multi-master) even if I removed the carpdev and carppeer attributes
| :(
Realize you have to do the exact same config on both hosts at the same
time.
I usually either manually type the same ifconfig commands on both hosts
and press enter in two nearby windows rapidly in succession. Editing the
hostname.carpX to match for reboot is also useful. If you're in testing
mode simply 'ifconfig carp0 down destroy; sh /etc/netstart carp0' on both
in rapid succession can also be an option.
Just remember, the key with carp is that all of the addresses on the carp
interface build up into a hash that must match the `other' system or both
systems will think they have a different config and you'll be stuck scratching
your head in permanent multi master mode, as you described above.
| I have tested both of these with PF disabled just encase a rule was
| messing things up.
| With pf enabled, does this rule satisfy CARP and is it sensible?;
| pass in quick proto carp from { fe80::/8 } to { ff00::/8 } keep
| state (no-sync)
|
| The only way I have managed to get this to work with 5.3 is separate
| carp devices, if I have to run two of course I will, but I would
| really like to get it working under one for clarity.
|
|
| PS; Todd,
| Thanks you very much for your detailed thoughts on IPv6 regarding
| filtering icmp6, ndp. Really appreciate your time to help.
| For ndp is this rule sensible?;
| pass quick proto icmp6 from { ff00::/8 } to { ff00::/8 }
| I have just set-up an he.net tunnel at home ;)
Do some tcpdump on pflog0 if you block other icmp6 codes (though I am an
advocate of universally enabling {echo,fqdn}{req,reply} .. if you have
abusers, block them via an overload rule or something, but permit
yourself the time proven luxury of 'ping6 host' to confirm its up from
wherever.
I think you'll find some { global, link local } - { fe80::/16,
ff02::/16 } activity. Yes I just realized /8 is the wrong prefixlen for
the lin local muticast and address space) activi
Thanks,
--
Todd Fries .. t...@fries.net
|\ 1.636.410.0632 (voice)
| Free Daemon Consulting, LLC\ 1.405.227.9094 (voice)
| http://FreeDaemonConsulting.com\ 1.866.792.3418 (FAX)
| PO Box 16169, Oklahoma City, OK 73113-2169 \ sip:freedae...@ekiga.net
| ..in support of free software solutions. \ sip:4052279...@ekiga.net
\
37E7 D3EB 74D0 8D66 A68D B866 0326 204E 3F42 004A
http://todd.fries.net/pgp.txt
Re: user can not shutdown PC in xfce
On Fri, August 30, 2013 13:58, James Griffin wrote: !-- On Fri 30.Aug'13 at 9:08:05 BST, Fung (fungm...@qq.com), wrote: -- Original -- From: Tomas Bodzartomas.bod...@gmail.com; On Tue, Aug 27, 2013 at 2:34 PM, Fung fungm...@qq.com wrote: 1. root login xfce can shutdown the pc smoothly using mouse. 2. other user in xfce can not shutdown the pc, why? # visudo ... %wheel ALL=(ALL) SETENV: ALL share ALL=NOPASSWD: /usr/local/lib/xfce4/session/xfsm-shutdown-helper ... # id share uid=1000(share) gid=1000(share) groups=1000(share), 0(wheel) # sysctl kern.version kern.version=OpenBSD 5.4-current (GENERIC.MP) #48: Sat Aug 24 20:31:41 MDT 2013 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP # cat /usr/local/share/doc/pkg-readmes/xfce-4.10p0 said Logging out and shutting down the computer == If your installation supports complete shutdown, clicking on the logout button on panel will permit you to either logout, rebooting or halt the computer, provided you have the needed sudo credentials. If you don't want to have to enter your password, simply add this line to the /etc/sudoers file using visudo: $your_username ALL=NOPASSWD: /usr/local/lib/xfce4/session/xfsm-shutdown-helper == are you in operator group? ;-) $ ls -l /sbin/shutdown -r-sr-x--- 1 root operator 222416 Aug 20 00:46 /sbin/shutdown $ . hi, tomas, Shutdown in xfce not work with operator group . BTW, from terminal , user share can halt -p/ shutdown the system. You could use a better Window Manager/Desktop. The cwm in base is excellent. Also, fvwm2 in packages is excellent (I use that one), so are some tiling WM's, like dwm and spectrwm. Maybe you can suggest even better OS to use? P.S. I'm using xfce and I'm in wheel group - everything works fine.
Searching dmesg from Z68P-DS3 ...
Hello, I'm looking for a dmesg from a Z68P-DS3 motherboard as seen by OpenBSD/amd64, as well as the result of sysctl hw. Does someone have this kind of information available ? Reason: on my system the ITE chip is not seen by the OS. So... Just checking... and sorry for the noise ! :) Thank-you, Eric.
Hard Freeze with Snapshots After Aug 19 on ThinkPad X1 Carbon
I'm running OpenBSD/amd64 5.4-current with GENERIC.MP from 2013/08/19 downloaded from the mirrors on a Levovo ThinkPad X1 Carbon. Both snapshots I have tried (2013/08/25 and 2013/08/29) after the 19th have resulted in hard system freezes every few hours. I don't have any logs or anything else that indicate a hard freeze but everything just hard freezes. I first noticed because I left the ThinkPad running overnight on my desk and when I came back to the system the next morning it was hard frozen. Several times during the day while I'm working I have also experienced the same thing. Anyone else seeing something similar? Bryan
Re: X reverts to vesa driver with 2013-AUG-24 snapshot
On 8/27/13, Jonathan Gray j...@jsg.id.au wrote: On Tue, Aug 27, 2013 at 01:15:02AM -0700, patrick keshishian wrote: On 8/26/13, Jonathan Gray j...@jsg.id.au wrote: On Mon, Aug 26, 2013 at 10:45:00PM -0700, patrick keshishian wrote: On 8/26/13, Jonathan Gray j...@jsg.id.au wrote: On Mon, Aug 26, 2013 at 12:35:18PM -0700, patrick keshishian wrote: help? should I wait for next snapshot? Some of the integrated graphics parts were previously disabled due to various issues. The radeondrm code we have now is a complete re-port though so try this: Thanks for the reply. I'll give this a go as soon as I get a breather. Curious, the snapshot from Aug 17th worked just fine. I didn't scrutinize it too much then, but the X session seemed fine to me, vs. the VESA one now that looks just wrong. xf86-video-ati was updated to version 7.2.0 which no longer supports userland modedesetting. So if a device doesn't match radeondrm it won't have any way of doing modesetting and will fall back to using vesa. I think I'll just commit the diff to enable the igp devices as it should work. Let us know how it goes, and remember to install the radeon firmware if you haven't already. The patched worked very nicely! :-) I just added fw_update'ed after noticing the drm error message in the dmesg output. Thank you, --patrick You'll have to reboot for the firmware to be found. Then you'll have acceleration in Xorg instead of the basic shadowfb mode. I really like the ominous Bad things might happen note. I think I'll borrow it for my code. after reboot: drm: initializing kernel modesetting (RS690 0x1002:0x791F 0x1025:0x028C). radeondrm0: VRAM: 384M 0x6800 - 0x7FFF (384M used) radeondrm0: GTT: 512M 0x8000 - 0x9FFF ttm_pool_mm_shrink_init stub drm: PCIE GART of 512M enabled (table at 0x04EC4000). error: [drm:pid0:r100_ring_test] *ERROR* radeon: ring test failed (scratch(0x15E4)=0xCAFEDEAD) error: [drm:pid0:r100_cp_init] *ERROR* radeon: cp isn't working (-22). error: [drm:pid0:rs690_startup] *ERROR* failed initializing CP (-22). error: [drm:pid0:rs690_init] *ERROR* Disabling GPU acceleration error: [drm:pid0:r100_cp_fini] *ERROR* Wait for CP idle timeout, shutting down CP. error: [drm:pid0:r100_cp_disable] *ERROR* Failed to wait GUI idle while programming pipes. Bad things might happen. drm: radeon: cp finalized radeondrm0: 1366x768 wsdisplay0 at radeondrm0 mux 1: console (std, vt100 emulation), using wskbd0 wsdisplay0: screen 1-5 added (std, vt100 emulation) [14.383] (--) checkDevMem: using aperture driver /dev/xf86 [14.396] (--) Using wscons driver on /dev/ttyC4 in pcvt compatibility mode (version 3.32) [14.479] X.Org X Server 1.14.1 Release Date: 2013-04-17 [14.479] X Protocol Version 11, Revision 0 [14.479] Build Operating System: OpenBSD 5.4 amd64 [14.479] Current Operating System: OpenBSD mycomputer 5.4 GENERIC#1 amd64 [14.480] Build Date: 18 August 2013 10:32:37PM [14.480] [14.491] Current version of pixman: 0.30.0 [14.491]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [14.491] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [14.492] (==) Log file: /var/log/Xorg.0.log, Time: Fri Aug 30 11:14:02 2013 [14.509] (==) Using config file: /etc/X11/xorg.conf [14.509] (==) Using system config directory /usr/X11R6/share/X11/xorg.conf.d [14.550] (==) No Layout section. Using the first Screen section. [14.550] (==) No screen section available. Using defaults. [14.550] (**) |--Screen Default Screen Section (0) [14.550] (**) | |--Monitor default monitor [14.558] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [14.558] (==) Disabling SIGIO handlers for input devices [14.558] (==) Automatically adding devices [14.558] (==) Automatically enabling devices [14.558] (==) Not automatically adding GPU devices [14.739] (==) FontPath set to: /usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/OTF/, /usr/X11R6/lib/X11/fonts/Type1/, /usr/X11R6/lib/X11/fonts/100dpi/, /usr/X11R6/lib/X11/fonts/75dpi/ [14.739] (==) ModulePath set to /usr/X11R6/lib/modules [14.739] (II) The server relies on wscons to provide the list of input devices. If no devices become available, reconfigure wscons or disable AutoAddDevices. [14.745] (II) Loader magic: 0x63d254e9100 [14.745] (II) Module ABI versions: [14.745]X.Org ANSI C Emulation: 0.4 [14.745]X.Org Video Driver: 14.1 [14.745]X.Org XInput driver : 19.1 [14.745]X.Org Server Extension : 7.0 [
Re: Watchdog timeout with MSI and Realtek 8101E on Dell Inspiron 3521 (amd64)
On 8/30/13, Alexey E. Suslikov alexey.susli...@gmail.com wrote: Chris Cappuccio chris at nmedia.net writes: Mark Kettenis just posted a patch to disable (and later re-enable) interrupts at some point in the driver. It's on the openbsd-tech list, dated Aug 21. Try and and see if it fixes your issue, as it appears nobody else has done so yet. could you drop marc or gmane link for that? http://marc.info/?l=openbsd-techm=137711518130141w=2 http://article.gmane.org/gmane.os.openbsd.tech/33395 I just applied this patch to my now-less-used-netbook, and the re0 timeouts I saw earlier this week during cvs updating, I no longer see. But my uptime is about 34min right now. so status may change :) --patrick
Re: Hard Freeze with Snapshots After Aug 19 on ThinkPad X1 Carbon
Yes, on an IdeaPad Yoga 13 I also experience hard freezes throughout the day. The timing varies from as little as one hour to several. Started happening a few snapshots back (around Aug. 19). On Aug 30, 2013 11:02 AM, Bryan Vyhmeister br...@bsdjournal.net wrote: I'm running OpenBSD/amd64 5.4-current with GENERIC.MP from 2013/08/19 downloaded from the mirrors on a Levovo ThinkPad X1 Carbon. Both snapshots I have tried (2013/08/25 and 2013/08/29) after the 19th have resulted in hard system freezes every few hours. I don't have any logs or anything else that indicate a hard freeze but everything just hard freezes. I first noticed because I left the ThinkPad running overnight on my desk and when I came back to the system the next morning it was hard frozen. Several times during the day while I'm working I have also experienced the same thing. Anyone else seeing something similar? Bryan
Re: Watchdog timeout with MSI and Realtek 8101E on Dell Inspiron 3521 (amd64)
On Fri, 30 Aug 2013 11:48:12 -0700 patrick keshishian pkesh...@gmail.com wrote: On 8/30/13, Alexey E. Suslikov alexey.susli...@gmail.com wrote: Chris Cappuccio chris at nmedia.net writes: Mark Kettenis just posted a patch to disable (and later re-enable) interrupts at some point in the driver. It's on the openbsd-tech list, dated Aug 21. Try and and see if it fixes your issue, as it appears nobody else has done so yet. could you drop marc or gmane link for that? http://marc.info/?l=openbsd-techm=137711518130141w=2 http://article.gmane.org/gmane.os.openbsd.tech/33395 I just applied this patch to my now-less-used-netbook, and the re0 timeouts I saw earlier this week during cvs updating, I no longer see. But my uptime is about 34min right now. so status may change :) --patrick This re0 at pci1 dev 0 function 0 Realtek 8101E rev 0x05: RTL8105E (0x4080), msi, address e0:db:55:d1:d7:f4 rlphy0 at re0 phy 7: RTL8201E 10/100 PHY, rev. 2 now works with the aforementioned patch. I have been running it and testing re0 for the last eight hours, and saw no watchdog timeout. Thanks !
Re: Watchdog timeout with MSI and Realtek 8101E on Dell Inspiron 3521 (amd64)
Chris Cappuccio chris at nmedia.net writes: Mark Kettenis just posted a patch to disable (and later re-enable) interrupts at some point in the driver. It's on the openbsd-tech list, dated Aug 21. Try and and see if it fixes your issue, as it appears nobody else has done so yet. could you drop marc or gmane link for that?
Re: user can not shutdown PC in xfce
!-- On Fri 30.Aug'13 at 15:21:03 BST, Kirill Bychkov (ki...@linklevel.net), wrote: On Fri, August 30, 2013 13:58, James Griffin wrote: !-- On Fri 30.Aug'13 at 9:08:05 BST, Fung (fungm...@qq.com), wrote: -- Original -- From: Tomas Bodzartomas.bod...@gmail.com; On Tue, Aug 27, 2013 at 2:34 PM, Fung fungm...@qq.com wrote: 1. root login xfce can shutdown the pc smoothly using mouse. 2. other user in xfce can not shutdown the pc, why? # visudo ... %wheel ALL=(ALL) SETENV: ALL share ALL=NOPASSWD: /usr/local/lib/xfce4/session/xfsm-shutdown-helper ... # id share uid=1000(share) gid=1000(share) groups=1000(share), 0(wheel) # sysctl kern.version kern.version=OpenBSD 5.4-current (GENERIC.MP) #48: Sat Aug 24 20:31:41 MDT 2013 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP # cat /usr/local/share/doc/pkg-readmes/xfce-4.10p0 said Logging out and shutting down the computer == If your installation supports complete shutdown, clicking on the logout button on panel will permit you to either logout, rebooting or halt the computer, provided you have the needed sudo credentials. If you don't want to have to enter your password, simply add this line to the /etc/sudoers file using visudo: $your_username ALL=NOPASSWD: /usr/local/lib/xfce4/session/xfsm-shutdown-helper == are you in operator group? ;-) $ ls -l /sbin/shutdown -r-sr-x--- 1 root operator 222416 Aug 20 00:46 /sbin/shutdown $ . hi, tomas, Shutdown in xfce not work with operator group . BTW, from terminal , user share can halt -p/ shutdown the system. You could use a better Window Manager/Desktop. The cwm in base is excellent. Also, fvwm2 in packages is excellent (I use that one), so are some tiling WM's, like dwm and spectrwm. Maybe you can suggest even better OS to use? Why would I want to do that? OpenBSD is the best os - xfce isn't that great i'm afraid. Simple as that. P.S. I'm using xfce and I'm in wheel group - everything works fine. -- James Griffin: jmz at kontrol.kode5.net A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Selecting new motherboards in the era of uefi
I'm shopping around for new server hardware. Unless someone has a reason to think of something else, I'm planing on a i7-4770K. The more interesting question is what motherboard to get. I have my eye on the Asus Sabertooth Z87, but I see that it talks of uefi. What I do not yet see, is whether the system can boot in a non- uefi mode or not. Given that the motherboard is at least a little OS agnostic, I have some hope that it will work. But I don't know, and in general I think it might be worth talking of strategies for motherboard selection given the size of the marketplace. I wonder if this might make a new section Thoughts? --STeve Andre'
Re: Hard Freeze with Snapshots After Aug 19 on ThinkPad X1 Carbon
On Aug 30, 2013, at 12:43, Jean Lucas nos...@gmail.com wrote: Yes, on an IdeaPad Yoga 13 I also experience hard freezes throughout the day. The timing varies from as little as one hour to several. Started happening a few snapshots back (around Aug. 19). Maybe ThinkPad ACPI related or something like that? Anyone have any ideas what might be causing the hard freezes? I haven't tried on my ThinkPad X230 but I could test on it as well if needed. Bryan
intel(0): Failed to submit batch buffer, [...]
Hello misc@, since a recent upgrade to a snapshot (the exact date of which I forgot; I hope the kernel build date from the dmesg below suffices), I've been getting the following X error regularly: (EE) intel(0): Failed to submit batch buffer, expect rendering corruption or even a frozen display: Unknown error: -4. I seem to be able to reproduce this quite reliably by starting the xombrero web browser with 'gui_mode = minimal' until I see corruptly rendered text in the status and/or tab bar. Similar errors occur from time to time during the rendering of web pages. dmesg and Xorg.0.log: OpenBSD 5.4-current (GENERIC) #40: Mon Aug 19 17:13:59 MDT 2013 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Pentium(R) M processor 1.10GHz (GenuineIntel 686-class) 1.10 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE,NXE,EST,TM2,PERF real mem = 1333133312 (1271MB) avail mem = 1299533824 (1239MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 07/26/06, BIOS32 rev. 0 @ 0xffe90, SMBIOS rev. 2.3 @ 0xf81a0 (45 entries) bios0: vendor Dell Inc. version A06 date 07/26/2006 bios0: Dell Inc. Latitude X1 acpi0 at bios0: rev 0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC ASF! MCFG SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) PBTN(S4) PCI0(S5) USB0(S0) USB1(S0) USB2(S0) USB4(S0) USB3(S0) MODM(S3) PCIE(S4) NIC_(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 99MHz ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 1 acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (PCIE) acpicpu0 at acpi0: C3, C3, C2, C1, PSS acpitz0 at acpi0: critical temperature is 95 degC acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 model DELL T61376 serial 490 type LION oem Sanyo acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: PBTN acpibtn2 at acpi0: SBTN acpivideo0 at acpi0: VID_ acpivideo1 at acpi0: VID2 bios0: ROM list: 0xc/0xf800! 0xcf800/0x800 cpu0: Enhanced SpeedStep 1098 MHz: speeds: 1100, 800, 600 MHz pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82915GM Host rev 0x03 vga1 at pci0 dev 2 function 0 Intel 82915GM Video rev 0x03 intagp0 at vga1 agp0 at intagp0: aperture at 0xc000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 composite sync not supported composite sync not supported inteldrm0: 1280x768 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) Intel 82915GM Video rev 0x03 at pci0 dev 2 function 1 not configured ppb0 at pci0 dev 28 function 0 Intel 82801FB PCIE rev 0x03: apic 1 int 16 pci1 at ppb0 bus 1 bge0 at pci1 dev 0 function 0 Broadcom BCM5751 rev 0x01, BCM5750 A1 (0x4001): apic 1 int 16, address xxx brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0 uhci0 at pci0 dev 29 function 0 Intel 82801FB USB rev 0x03: apic 1 int 16 uhci1 at pci0 dev 29 function 2 Intel 82801FB USB rev 0x03: apic 1 int 18 uhci2 at pci0 dev 29 function 3 Intel 82801FB USB rev 0x03: apic 1 int 19 ehci0 at pci0 dev 29 function 7 Intel 82801FB USB rev 0x03: apic 1 int 16 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb1 at pci0 dev 30 function 0 Intel 82801BAM Hub-to-PCI rev 0xd3 pci2 at ppb1 bus 2 cbb0 at pci2 dev 1 function 0 Ricoh 5C476 CardBus rev 0xb3: apic 1 int 19 Ricoh 5C552 Firewire rev 0x08 at pci2 dev 1 function 1 not configured sdhc0 at pci2 dev 1 function 2 Ricoh 5C822 SD/MMC rev 0x17: apic 1 int 17 sdmmc0 at sdhc0 iwi0 at pci2 dev 3 function 0 Intel PRO/Wireless 2200BG rev 0x05: apic 1 int 17, address xxx cardslot0 at cbb0 slot 0 flags 0 cardbus0 at cardslot0: bus 3 device 0 cacheline 0x0, lattimer 0x20 pcmcia0 at cardslot0 auich0 at pci0 dev 30 function 2 Intel 82801FB AC97 rev 0x03: apic 1 int 16, ICH6 AC97 ac97: codec id 0x83847652 (SigmaTel STAC9752/53) ac97: codec features headphone, 20 bit DAC, 20 bit ADC, SigmaTel 3D audio0 at auich0 ichpcib0 at pci0 dev 31 function 0 Intel 82801FBM LPC rev 0x03: PM disabled pciide0 at pci0 dev 31 function 1 Intel 82801FB IDE rev 0x03: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility wd0 at pciide0 channel 0 drive 0: KingSpec KSD-CF18.6-032MS wd0: 1-sector PIO, LBA48, 30192MB, 61833216 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 pciide0: channel 1 ignored (disabled) usb1 at uhci0: USB revision 1.0 uhub1 at usb1 Intel UHCI root hub rev 1.00/1.00 addr 1 usb2 at uhci1: USB revision 1.0 uhub2 at usb2 Intel UHCI root hub rev 1.00/1.00 addr 1 usb3 at uhci2: USB revision 1.0 uhub3 at usb3 Intel UHCI root hub rev 1.00/1.00 addr 1 isa0 at ichpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for
Re: Selecting new motherboards in the era of uefi
You are asking about a Sabertooth Z87, but according to a moderator of the FreeBSD forums, the Sabertooth Z77 can boot in legacy, non-UEFI mode. See https://forums.freebsd.org/showpost.php?p=228402postcount=5 On Fri, Aug 30, 2013 at 11:32 PM, STeve Andre' and...@msu.edu wrote: I'm shopping around for new server hardware. Unless someone has a reason to think of something else, I'm planing on a i7-4770K. The more interesting question is what motherboard to get. I have my eye on the Asus Sabertooth Z87, but I see that it talks of uefi. What I do not yet see, is whether the system can boot in a non- uefi mode or not. Given that the motherboard is at least a little OS agnostic, I have some hope that it will work. But I don't know, and in general I think it might be worth talking of strategies for motherboard selection given the size of the marketplace. I wonder if this might make a new section Thoughts? --STeve Andre'
