Rework carp ipv4 support
Hi all, carp(4) ipv4 users please test following patch: http://leaf.dragonflybsd.org/~sephe/carp_ipv4.diff Configure inet address to carp(4) interface is no longer supported; you need to use "vhinet address" instead. carp(4) now needs explicit bringing up (originally inet address will implicitly bringing up the interface). e.g. ifconfig carp0 create ifconfig carp0 vhid 1 pass your_password vhinet your_virtual_add1 vhinet your_virtual_addr2 ifconfig carp0 up Virtual address support CIDR form. The subnetmask part is not used currently. However, it is recommended to set it according to your needs, in case it is used in the future updating. You will need a quickworld (for ifconfig(8)) and quickkernel Best Regards, sephe -- Live Free or Die
Re: Rework carp ipv4 support
> Configure inet address to carp(4) interface is no longer supported; Hi Sephe, May I ask what is the reason for this change? Petr
Console screen corruption?
I've installed dfly using the kvm/qemu emulator and I'm seeing strange corruption of the console screen at times. Some lines of text will have every other character blacked out, and some lines display perfectly. Does this sound like some sort of confusion between ascii and utf-8, perhaps? That's the only thing I can think of. One notable clue is that dfly and freebsd are the only systems I have this problem with. OpenBSD, NetBSD and linux work correctly, so I'm hoping someone may know what code dfly and fbsd use that would account for the problem. Thanks for any hints.
Re: Console screen corruption?
:I've installed dfly using the kvm/qemu emulator and I'm seeing :strange corruption of the console screen at times. : :Some lines of text will have every other character blacked out, :and some lines display perfectly. Does this sound like some sort :of confusion between ascii and utf-8, perhaps? That's the only :thing I can think of. : :One notable clue is that dfly and freebsd are the only systems I :have this problem with. OpenBSD, NetBSD and linux work correctly, :so I'm hoping someone may know what code dfly and fbsd use that :would account for the problem. : :Thanks for any hints. They are likely trying to emulate VESA modes and getting confused. I'm pretty sure qemu has command line options that allow you to use a 'serial' console, or options to manipulate the console mode to something more compatible. -Matt Matthew Dillon
Re: Console screen corruption?
walt schrieb: I've installed dfly using the kvm/qemu emulator and I'm seeing strange corruption of the console screen at times. Does it happen randomly or when you do some specific thing? Did you change the mode using vidcontrol(8) or does it happen with plain 80x25? Some lines of text will have every other character blacked out, and some lines display perfectly. Does this sound like some sort of confusion between ascii and utf-8, perhaps? That's the only thing I can think of. I don't think that's the cause. One notable clue is that dfly and freebsd are the only systems I have this problem with. OpenBSD, NetBSD and linux work correctly, so I'm hoping someone may know what code dfly and fbsd use that would account for the problem. Yeah, DragonFly and FreeBSD share much of their console code. Sascha -- http://yoyodyne.ath.cx
Re: Console screen corruption?
On Fri, Dec 12, 2008 at 08:59:30PM +0100, Sascha Wildner wrote: > walt schrieb: > >I've installed dfly using the kvm/qemu emulator and I'm seeing > >strange corruption of the console screen at times. > > Does it happen randomly or when you do some specific thing? Did you > change the mode using vidcontrol(8) or does it happen with plain 80x25? > > >Some lines of text will have every other character blacked out, > >and some lines display perfectly. Does this sound like some sort > >of confusion between ascii and utf-8, perhaps? That's the only > >thing I can think of. > > I don't think that's the cause. > > >One notable clue is that dfly and freebsd are the only systems I > >have this problem with. OpenBSD, NetBSD and linux work correctly, > >so I'm hoping someone may know what code dfly and fbsd use that > >would account for the problem. > > Yeah, DragonFly and FreeBSD share much of their console code. I had some console weirdness on FreeBSD once, and it turned out that I had some bad memory. Brett > > Sascha > > -- > http://yoyodyne.ath.cx -- B. Estrade Louisiana Optical Network Initiative +1.225.578.1920 aim: bz743 :wq
Re: Console screen corruption?
On Fri, 12 Dec 2008, Sascha Wildner wrote: > walt schrieb: > > I've installed dfly using the kvm/qemu emulator and I'm seeing > > strange corruption of the console screen at times. > > Does it happen randomly or when you do some specific thing? Did you change the > mode using vidcontrol(8) or does it happen with plain 80x25? Plain 80x25. In fact I wish I could remember how to change to 80x50 :o) I just discovered by accident that if I keep typing (any) characters the characters will disappear randomly as I type, until I get a linewrap. At that point the entire line I just typed suddenly appears normal. If I continue typing on the (wrapped) line, it will again blank out chars randomly until I reach the second linewrap, when *both* lines on the screen suddenly appear normal again. Does that mean anything to you? Pretty mysterious to me.
Re: Console screen corruption?
walt schrieb: On Fri, 12 Dec 2008, Sascha Wildner wrote: walt schrieb: I've installed dfly using the kvm/qemu emulator and I'm seeing strange corruption of the console screen at times. Does it happen randomly or when you do some specific thing? Did you change the mode using vidcontrol(8) or does it happen with plain 80x25? Plain 80x25. In fact I wish I could remember how to change to 80x50 :o) Hm, you can change to 80x50 with 'vidcontrol -f 8x8 iso-8x8.fnt 80x50'. After trying 80x50, switch back to 80x25 with 'vidcontrol 80x25' and check if the problem persists. Also, can you recompile with options VGA_DEBUG=2 options FB_DEBUG=2 in your kernel config and post or mail me a verbose boot message? AFAIK we don't mess with the VGA registers for our initial 80x25 (we just take the BIOS settings). I just discovered by accident that if I keep typing (any) characters the characters will disappear randomly as I type, until I get a linewrap. Weird, I tried DragonFly in plain Windows qemu and the console behaves fine. At that point the entire line I just typed suddenly appears normal. If I continue typing on the (wrapped) line, it will again blank out chars randomly until I reach the second linewrap, when *both* lines on the screen suddenly appear normal again. Does that mean anything to you? Pretty mysterious to me. Yes, seems weird. I hope we can find the cause. Sascha -- http://yoyodyne.ath.cx
Re: Rework carp ipv4 support
On Sat, Dec 13, 2008 at 2:06 AM, Petr Janda wrote: >> Configure inet address to carp(4) interface is no longer supported; > > Hi Sephe, > May I ask what is the reason for this change? Why do you need it? The route added by the inet address will never be used, while the inet address will never be the source address of the outgoing packets (you always need a backing inet address in other "real" iface). The original inet address are just used to do following mapping: target inet address (in arp) -> ether address (generated from vhid) Mixing the carp inet address into the global inet address list and hash table introduce great mess (take a look at how they generated sha1 hash on the inet addresses, and various workaround added to in_control) and actually do you no good. Best Regards, sephe -- Live Free or Die
