Re: Boot of 9.1 under qemu-kvm 1.3 hangs at pci probing

2012-12-19 Thread Juergen Lock
In article 50ce5805.7010...@cran.org.uk you write:
I'm trying to install FreeBSD 9.1 in a Proxmox KVM, using qemu-kvm 1.3, 
but the boot process is hanging:

pbib0: matched entry for 0.1 INTA
pbib0: slot 1 INTA hardwired to IRQ 9
ioapic0: Changing polarity for pin 9 to low
found - vendor=0x1013, dev=0x00b8, revid=0x00
domain=0, bus=0, slot=2, func=0
class=03-00-00, hdrtype=0x00, mfdev=0
cmdreg=0x0103, statreg=0x, cachelnsz=0 (dwords)
   lattimer=0x00 (0 ns), mingnt=0x00 (0ns), maxlat=0x00 (0ns)
[hang]

Has anyone come across this before and know of any workarounds?

Just in case you haven't meanwhile found this yourself (and for the
archives), this is caused by an incompatible change in seabios [1]
that qemu uses.  I hope this will be fixed for qemu 1.3.1, a fixed
bios.bin that you can pass to qemu/kvm with -bios has been posted
in this thread:

https://lists.nongnu.org/archive/html/qemu-devel/2012-12/msg01703.html

 HTH, :)
Juergen

[1] 
http://git.qemu.org/?p=seabios.git;a=commit;h=4540409d19a4baeec5006d925cfca19f8038a96e
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: RME audio card user new to FreeBSD

2012-11-24 Thread Juergen Lock
In article 1353768334.2641.21.camel@q you write:
Thank you!
You're welcome!

On Sat, 2012-11-24 at 15:14 +0100, Juergen Lock wrote:
  Don't want to try 9.1RC3?

I thought it would be better to start with something stable as a
newbie and now burning already is in progress.

 Well I don't think there'll be many changes from RC3 to release,
and you can use freebsd-update to get to -release after it's out
anyway.

 (I think you can also back it up, but make sure you don't restore the
 slice table in the mbr too if you add the bsd slice from bsdinstall,
 only the actual bootcode.)

I backup the first 512 bytes:
dd if=/dev/sda of=MBR_sda-$BACKUP_NAME_ADD bs=512 count=1

So I should restore from byte 0 to byte 439 only if a restore should be
needed?

 That does sound correct. (tho I haven't verified the exact number 439.)

I assume that there's also a way to recover a broken partition table
with BSD information if needed and no backup should be available?

 There is sysutils/scan_ffs in ports tho I didn't have to try it yet.

 HTH, :)
Juergen

PS: I have Cc'd the freebsd-questions list as this no longer really
is a multimedia topic...  (Yes I should have done that earlier, sorry.)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: FreeBSD' Webcam and DVB Compatibility List

2011-04-02 Thread Juergen Lock
In article 20110331112119.ga21...@sh4-5.1blu.de you write:
Hello,
Hi!

We have started a small documentation project in the FreeBSD Wiki: The
FreeBSD' Webcam and DVB Compatibility List.

http://wiki.freebsd.org/WebcamCompat

The main goal of this page is to give an exact answer about which
application works with a given cam or DVB. Combinations of the hardware
and software mentioned below in the table are known to work. 
Please add more lines to the table or ask me to do so by just sending a
mail with your Cam/DVB information. Please note: you should only add
information you have seen working and not you may think of or imagine
that they could work. The contact information (name and/or email addr)
is optional. 

If you want me to add your webcam or DVB, please send me a structured
ASCII line of the following format:

Cam or DVB type (USB, build-in);Manufactor;Product Name;VendorID:ProductID 
(hex);Driver or kernel module;V4L/V4L2;min. tested OS version(s);Supported 
application(s);Additional comments;Contact

i.e.
-- use ';' as separator of the fields
-- fill out all fields (if you don't know the value use 'unknown')
-- also use 'unknown' for the field Contact if you don't want your name or 
mail in the row
-- you may send it as one line (as shown above) or wraped lines after any ';'

Please use the above format and no HTML (HTML will be silently ignored).
As well, please send it to me and not to the list.

Any hints, comments or questions are welcomed, of course.

 I have added a few dvb tuners that I tested, and I have also added
a Remote Control section and added my mceusb device that I tested
with lirc, vdr, and xbmc.  Hope that's okay... :)

 Cheers,
Juergen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Tv-card for freebsd

2010-07-24 Thread Juergen Lock
In article aanlktil5_9vmp3zal-4knwx-lblrpwz6dcxq4cora...@mail.gmail.com you 
write:
On 7/14/10, Bernt Hansson be...@bah.homeip.net wrote:
 Hello list!

 I'm in the process of buying a tv-card for dvb-t transmissions.

 Any tips on cards that have a driver for freebsd?

 Thank you.


For a built-in tuner card itself, no recommendations.

For an alternative solution, look at silicondust.com for the HDHomeRun
boxes.  I've had one for a long time and it is a beautiful device.
Simply stated, a dual (or more) digital tuner to ethernet bridge.

[...]

Another option may be an usb tuner with webcamd on FreeBSD 8.1;
webcamd is a pretty cool hack by the author of FreeBSD 8's new
usb stack that essentially runs Linux usb v4l/dvb/atsc drivers on
FreeBSD in userspace and is now in ports:

http://www.freshports.org/multimedia/webcamd

I've put together some (hopefully) useful info here:

http://people.freebsd.org/~nox/dvb/

and there I'm also maintaining experimental ports for vdr which
most Linux users I know prefer over mythtv which is already
committed to ports.  But `simpler' apps like mplayer, kaffeine,
vlc, etc can of course also be used if you build the respective
ports with the V4L knobs enabled in their `make config'.  (and
DVBPSI too in case of vlc.)

 HTH,
Juergen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Why googleearth keeps crashing when photo window is closed?

2010-07-19 Thread Juergen Lock
On Wed, Jul 14, 2010 at 03:44:54AM -0700, Yuri wrote:
 
 For some reason googleearth crashes when the popup with photo is closed.
 Crashes are intermittent, depending on system updates and port updates. 
 After some crashes disappear and after other updates crashes come back 
 again.
 
Hi!

 I didn't answer at first since my ports weren't up to date and I
couldn't reproduce the issue, now after updating to latest ports
and RELENG_8_1 (amd64) googleearth still seems to work just fine
for me, only gl doesn't work since a) our linux versions of the
gl-related libs are too old for my card (radeon r730pro i.e. HD
4650) and b) I'm on amd64 and I've been told the dri interface may
be different between i386 and amd64 so the linuxolator could have
issues emulating gl anyway. (or only with the xorg drivers since
the nvidia blob may already be handling this problem?)

 Crash stack is below.
 
 Yuri
 
 
 Major Version 5
 Minor Version 2
 Build Number 0001
 Build Date Jun 10 2010
 Build Time 16:15:55
 OS Type 3
 OS Major Version 2
 OS Minor Version 6
 OS Build Version 16
 OS Patch Version 0
 Crash Signal 11
 Crash Time 1279103869
 Up Time 31.366
 
 Stacktrace from glibc:
 ./libgoogleearth_free.so[0x33d3c30b]
 [0xbfbfffbb]
 ./libQtWebKit.so.4[0x34bf7f23]
 ./libQtWebKit.so.4[0x34bf7f5f]
 ./libQtWebKit.so.4[0x34bf7f79]
 ./libQtWebKit.so.4[0x34bf7fd3]
 ./libQtWebKit.so.4[0x34cb5da8]
 ./libQtWebKit.so.4[0x34cb5d1c]
 ./libQtWebKit.so.4[0x35057709]
 ./libQtWebKit.so.4[0x350577ad]
 ./libQtWebKit.so.4[0x3516a908]
 ./libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x112)[0x33fdbfca]
 ./libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0xa0)[0x3423ae20]
 ./libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x22e)[0x34244962]
 ./libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x70)[0x33fcdd50]
 ./libQtCore.so.4[0x33ff3743]
 ./libQtCore.so.4(_ZN20QEventDispatcherUNIX14activateTimersEv+0x17)[0x33ff381f]
 ./libQtCore.so.4(_ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0xd9)[0x33ff39ed]
 ./libQtGui.so.4[0x342cfca4]
 ./libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x47)[0x33fccfbf]
 ./libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xff)[0x33fcd223]
 ./libQtCore.so.4(_ZN16QCoreApplication4execEv+0x9d)[0x33fcec05]
 ./libQtGui.so.4(_ZN12QApplication4execEv+0x25)[0x3423a7a1]
 ./libgoogleearth_free.so(_ZN5earth6client11Application3runEv+0x4bc)[0x33d4750c]
 ./libgoogleearth_free.so(earthmain+0x27d)[0x33d3b73d]
 ./googleearth-bin(_init+0x122)[0x80486c2]
 /lib/libc.so.6(__libc_start_main+0xe5)[0x358596e5]
 ./googleearth-bin(_init+0x91)[0x8048631]
 
 I see you also posted this on the googlearth forum, lets hope they know
more...

 Good luck! :)
Juergen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Virtualbox and bridged interface.

2010-01-13 Thread Juergen Lock
On Fri, Jan 08, 2010 at 08:15:58PM +0100, Juergen Lock wrote:
 In article 20100102005808.12d46...@baby-jane.lamaiziere.net you write:
 Le Fri, 1 Jan 2010 17:36:30 -0600,
 Adam Vande More amvandem...@gmail.com a =E9crit :
 
   Is there someone able to make VirtualBox working with a bridged
   interface?
  
   I've got :
   My gateway/access point on 192.168.1.1/24
   The host on 192.168.1.20/24 via wifi (wlan0)
   The guest on 192.168.1.25/24 bridged with wlan0
 ...
 
  Bridged networking doesn't work on wireless interfaces.
 
 Ah ok :(
 
 I would be happy to know why, briefly. Is it a limitation in the
 wireless connection or a limitation in the operating system (FreeBSD)?
 
 The problem is caused by the fact that hosts on wifi can usually only
 use a single mac address, and while the vbox code does contain a
 `shared mac' feature thats supposed to work around this problem this
 feature hasn't been ported for FreeBSD hosts yet.
 
 I've used some bridged guests on Mac OS X and vmware fusion but I don't
 remember if I used the ethernet or the wireless interface.
 
 To J.D.Bronson: no mac authentication here, thanks for the shot in the
 dark anyway.
 
 So I will try to setup a vpn between the host and the guest.
 
  There is another workaround tho that you can try involving a tap
 interface, routing, proxy arp, and a patch to vbox to enable direct
 tap networking,
   http://people.freebsd.org/~nox/vbox/patch-tapdirect.txt
 more details including a config example in this post:
   
 http://lists.freebsd.org/pipermail/freebsd-emulation/2010-January/007260.html
 (I patched vbox 3.1.2 thats not commtted to ports yet, it's possible
 the patch doesn't apply to the older version in ports.  The latest vbox
 3.1.2 Call for testing is here:
   
 http://lists.freebsd.org/pipermail/freebsd-emulation/2010-January/007241.html
 The patch can go in that port's files/ dir.)

All committed to ports now, including the shared mac feature so bridged
mode on wifi should now work in the new emulators/virtualbox-ose* ports:

http://www.freshports.org/commit.php?message_id=201001130803.o0d83hfe012...@repoman.freebsd.org

 Please see http://wiki.freebsd.org/VirtualBox for update instructions.

 Enjoy, :)
Juergen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Virtualbox and bridged interface.

2010-01-08 Thread Juergen Lock
In article 20100102005808.12d46...@baby-jane.lamaiziere.net you write:
Le Fri, 1 Jan 2010 17:36:30 -0600,
Adam Vande More amvandem...@gmail.com a =E9crit :

  Is there someone able to make VirtualBox working with a bridged
  interface?
 
  I've got :
  My gateway/access point on 192.168.1.1/24
  The host on 192.168.1.20/24 via wifi (wlan0)
  The guest on 192.168.1.25/24 bridged with wlan0
...

 Bridged networking doesn't work on wireless interfaces.

Ah ok :(

I would be happy to know why, briefly. Is it a limitation in the
wireless connection or a limitation in the operating system (FreeBSD)?

The problem is caused by the fact that hosts on wifi can usually only
use a single mac address, and while the vbox code does contain a
`shared mac' feature thats supposed to work around this problem this
feature hasn't been ported for FreeBSD hosts yet.

I've used some bridged guests on Mac OS X and vmware fusion but I don't
remember if I used the ethernet or the wireless interface.

To J.D.Bronson: no mac authentication here, thanks for the shot in the
dark anyway.

So I will try to setup a vpn between the host and the guest.

 There is another workaround tho that you can try involving a tap
interface, routing, proxy arp, and a patch to vbox to enable direct
tap networking,
http://people.freebsd.org/~nox/vbox/patch-tapdirect.txt
more details including a config example in this post:

http://lists.freebsd.org/pipermail/freebsd-emulation/2010-January/007260.html
(I patched vbox 3.1.2 thats not commtted to ports yet, it's possible
the patch doesn't apply to the older version in ports.  The latest vbox
3.1.2 Call for testing is here:

http://lists.freebsd.org/pipermail/freebsd-emulation/2010-January/007241.html
The patch can go in that port's files/ dir.)

 HTH,
Juergen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Win4BSD -- any comments or experiences?

2009-04-24 Thread Juergen Lock
In article d356c5630904240925y25a2ec11m429e57001880c...@mail.gmail.com you 
write:
On Fri, Apr 24, 2009 at 10:18 AM, Matthias Apitz g...@unixarea.de wrote:


 Hello,

 Subscribed in a FreeBSD mailing list in Spanish, I've got a pointer to
 this software:

 http://win4bsd.com/wp/win4bsd-free-for-non-commercial-use/

 Any comments about or test results in compare with Qemu?
 Thx

matthias
 --
 Matthias Apitz
 Manager Technical Support - OCLC GmbH
 Gruenwalder Weg 28g - 82041 Oberhaching - Germany
 t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
 e matthias.ap...@oclc.org - w http://www.oclc.org/
 http://www.UnixArea.de/
 People who hate Microsoft Windows use Linux but people who love UNIX use
 FreeBSD.
 ___
  freebsd-questions@freebsd.org


I played with win4bsd for awhile.  It works well for normal desktop usage.
Unfortunately, virtual os setups do not handle complex data analysis of
extremely large data sets well.  I think it has to do with memory
usage/management.  Otherwise, I liked win4bsd a lot.

Well I haven't actually tried win4bsd, only researched about it one the
web a little once and noticed it seems to be based on an old version
of qemu (it still uses kqemu 1.3.* not 1.4.* like current qemu - which
btw is the only reason I haven't removed the old kqemu from ports and
renamed the new one, i.e. emulators/kqemu-kmod still is the old one.)

 Now does that mean current qemu is better/more stable than win4bsd if
all you want is emulate something like xp?  I don't know...  (Maybe the
win4bsd folks have incorporated other fixes that aren't in qemu yet?
At least they certainly seem to have added features...)

 Cheers,
Juergen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: 7.0-STABLE qemu not terminating

2009-04-24 Thread Juergen Lock
On Fri, Apr 24, 2009 at 02:17:51PM +0200, Matthias Apitz wrote:
 El día Thursday, April 23, 2009 a las 10:22:52PM +0200, Juergen Lock escribió:
 
   a new effect is that the qemu proc ends on termination of guest OS; the
   flag -no-shutdown does not help;
  
   Oh, yeah, same here.  I've just reported this on the qemu list, and btw
  kvm seems to be affected too:
  https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/362550/+viewstatus
 
 another issue is, when I'm using:
 
-kernel-kqemu
Enable KQEMU full virtualization (default is user mode only).
 
 the guest system (XP SP3) crashes short after coming up; without
 -kernel-kqemu I'm not sure if Qemu does make use of the kqemu.ko, it is
 so slow, esp. on disk i/o; I have loaded kqemu.ko on boot and if Qemu is
 up I can't kldunload it; but I really don't know if it makes use of it;

Actually it does, just not for guest kernel code, only userland.
(If you want to turn off kqemu completely use -no-kqemu, then it'll
run even slower. :)

 Anyway I've got one report that reinstalling an xp guest (it was
originally installed using an older qemu version) fixed -kernel-kqemu
instabilites at least for one guy (it worked for him with the old qemu)
- it is still true however that kqemu, especially with -kernel-kqemu,
is far from perfect, i.e. it doesn't really work for all types of guests,
and the fact that the linux folks have pretty much deprecated kqemu
in favour of kvm doesn't really help its cause either...  (And yes we
really could use a finished kvm port for the people that do have a
recent cpu with the necessary features, at least on linux kvm is also
much faster than -kernel-kqemu, and it works for more guests.)

 HTH,
Juergen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: 7.0-STABLE qemu not terminating

2009-04-23 Thread Juergen Lock
On Thu, Apr 23, 2009 at 11:43:56AM +0200, Matthias Apitz wrote:
 El día Tuesday, March 24, 2009 a las 07:24:26PM +0100, Juergen Lock escribió:
 
  While I don't remeber seeing reports about this particular issue, it is
  still very well possible that it has been fixed in the meantime, so I'd
  advise you to update.  (the port is at 0.10.1 now, which contains quite
  a few bugfixes and improvements...  Don't forget to read UPDATING and
  the pkg-message of the port tho.)
  ...
 
 I've port updated to:
 kqemu-kmod-devel-1.4.0.p1_2 Kernel Accelerator for QEMU CPU Emulator 
 (development versi
 qemu-0.10.2 QEMU CPU Emulator
 
 and the problem went away;
 
That's good to hear. :)

 a new effect is that the qemu proc ends on termination of guest OS; the
 flag -no-shutdown does not help;

 Oh, yeah, same here.  I've just reported this on the qemu list, and btw
kvm seems to be affected too:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/362550/+viewstatus

 HTH,
Juergen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: 7.0-STABLE qemu not terminating

2009-03-24 Thread Juergen Lock
In article 20090317143537.ga12...@rebelion.sisis.de you write:

Hello,

My VM qemu (qemu-0.9.1_3 / kqemu-kmod-1.3.0.p11_2) does not terminate 
after the system (WinXP) is successfully halted and the qemu window is
closed; it stays forever as:

# ps ax | fgrep qemu
 1687  ??  I  0:00,25 kdesu -u root -c /home/guru/qemu/w2k/qemu.sh 
 1713  ??  Is 0:00,00 sh -c /home/guru/qemu/w2k/qemu.sh 
 1714  ??  I  0:00,00 /bin/sh /home/guru/qemu/w2k/qemu.sh
 1717  ??  DE11:51,11 qemu -localtime -hda disk0 -hdb disk1 -net nic -net 
 tap -m 512

any ides? thx

   matthias

While I don't remeber seeing reports about this particular issue, it is
still very well possible that it has been fixed in the meantime, so I'd
advise you to update.  (the port is at 0.10.1 now, which contains quite
a few bugfixes and improvements...  Don't forget to read UPDATING and
the pkg-message of the port tho.)

 Oh and also, there usually is no reason to run qemu as root if you setup
tap permissions and (possibly) ifup/down scripts accordingly.  (Or,
if you are only using tuntap because you are on amd64 where slirp was
broken, that also is fixed now.)

 HTH,
Juergen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: kqemu runs 2x faster on i386 than amd64!?

2008-11-18 Thread Juergen Lock
In article [EMAIL PROTECTED] you write:
Guess I should've mentioned the target is 32-bit win2k...

On Thu, Oct 30, 2008 at 11:28 AM, Steve Franks [EMAIL PROTECTED] wrote:
 I'm not comparing apples-to-apples exactly, but both my disks are in
 the same system, both are running 7-stable from within the last few
 months, so it's pretty close.  Also, the i386 is a direct replacement
 of the amd64 to fix this and other problems, so the software 
 settings set is pretty identical also...

 kqemu crawls when I boot amd64 (and I notice the processor is always
 over 50%), and it's reasonalbly usable on i386 (also, the processor is
 often in the 30% range, instead of 60%).

 Steve

Hi!

 Are you sure kqemu is even used? (in the monitor do: info kqemu)

 Quoting ports/emulators/qemu/pkg-message:

- also remember that on amd64 you need to run the amd64 (x86_64) system
emulation if you want to use kqemu, i.e. run qemu-system-x86_64 instead of
qemu (the latter only emulates a 32 bit system.) [...]

 Note however that this is no longer true with the qemu-devel port, so
if you are using that also the 32 bit `qemu' can use kqemu.

 And finally, for anyone wanting to test out more recent qemu svn
snapshots, you should check -emulation, I have just prepared another
experimental qemu-devel port update:

http://lists.freebsd.org/pipermail/freebsd-emulation/2008-November/005526.html

 HTH,
Juergen

PS: No I'm still not on -questions, so please Cc me if you want to make
sure I see followups.  (I was just testing out accessing it via gmane and
looked for recent posts about qemu...)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: flash9 checklist

2008-10-30 Thread Juergen Lock
In article [EMAIL PROTECTED] you write:
will this howto work for amd64 ?
[...]

Yes.

Juergen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: flash9 checklist

2008-10-30 Thread Juergen Lock
In article [EMAIL PROTECTED] you write:
Juergen Lock wrote:

 Preliminary checklist for getting flash9 to work in native firefox:
 (flash10 needs more ports work, I shall post about that seperately on
 -emulation...)  If you have additions to this please post a followup to
 this thread, keeping the Cc: (I'm not on -questions...)

 1. You need RELENG_7 from at least Mon Oct 20 11:15:57 2008 UTC
 (the relevant MFC commits are:
  http://svn.freebsd.org/viewvc/base?view=revisionrevision=183819
  http://svn.freebsd.org/viewvc/base?view=revisionrevision=184075
 - a recent HEAD should also work of course.)  There are linprocfs patches
 for RELENG_6 too (merging the former commit), but the latter commit can't
 be merged to 6 (and 7.0) since they lack the cpuset bits, so flash9
 probably won't work on SMP there.  (Although if you have SMP you probably
 should be running 7 anyway. :)  Oh and if you do have SMP you also need to
 use the ULE scheduler, the cpuset syscalls are not supported with 4BSD.
 linprocfs patches for 6:
  http://people.freebsd.org/~nox/linprocfs-6.3.patch
  http://people.freebsd.org/~nox/linprocfs-6.4.patch

 2. Your portstree needs to be from at least Sun Oct 19 17:37:28 2008 UTC
 (the last www/linux-flashplugin9 commit is:
  http://lists.freebsd.org/pipermail/cvs-ports/2008-October/158404.html
 )

 3. Make sure linprocfs is mounted to /compat/linux/proc .

 4. Make sure www/nspluginwrapper, www/linux-flashplugin9 and dependencies
 are installed and up to date(!).  (the default emulators/linux_base-fc4
 should work, if you want to use a later one don't forget to set
 compat.linux.osrelease=2.6.16 in sysctl.conf and OVERRIDE_LINUX_BASE_PORT
 to whichever version you use in make.conf.  Note however that on 6, only
 the default compat.linux.osrelease=2.4.2 really works.)

 5. If the plugin doesnt show up in firefox' about:plugins, run
  nspluginwrapper -i 
 /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so
 and restart firefox.

 6. And remember there's a security advisory for the current version of
 flash9,
  
 http://www.FreeBSD.org/ports/portaudit/78f456fd-9c87-11dd-a55e-00163e16.html
 (if you use portaudit you need to `make -DDISABLE_VULNERABILITIES ...'
 to be able to install the port), and fc4 seems to be eol'd too, so you
 probably want to install something like the noscript firefox extension,
  https://addons.mozilla.org/en-US/firefox/addon/722
 and only allow plugins (and scripts, tho thats a different problem) on
 sites you trust...

  And finally, if you still get crashes after following the above even
 on pages that are reported to work now (like youtube) you probably want
 to run `ktrace -di firefox...' and look at the output using linux_kdump
 (thats the devel/linux_kdump port, you want to use a package), paying
 specific attention to the lines above `PSIG SIGSEGV' (or whichever
 signal you got), maybe there are still shlibs missing that the plugin
 needs (NAMI ...something.so...), and if this is the case tell us about
 it so the appropriate dependencies can be added to the relevant ports.
 If you can't figure it out I guess it doesn't hurt to post the last
 few 100 lines of the dump up to the relevant PSIG on -emulation...

  You may also want to check linked shlibs like this:
  /compat/linux/bin/sh /compat/linux/usr/bin/ldd 
 /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so
 and
  /compat/linux/bin/sh /compat/linux/usr/bin/ldd 
 /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin
 (if you see `not found' in there you know something is wrong) - although
 that doesn't show libs that may be dlopen()d at runtime.

   
Thanks for this.  I was able to get linux-flashplugin9 working in native 
Firefox 3.0.3 on FreeBSD 7-STABLE i386.  The only additional thing I had 
to do was copy 
/usr/X11R6/lib/browser_plugins/npwrapper.libflashplayer.so into 
~/.mozilla/plugins/ for Firefox to recognize the plugin.

Yeah I forgot to note that you want to run nspluginwrapper -i
as the user that will run the native browser, not as root, then the
wrapper will go into ~/.mozilla/plugins/...

  After that 
Youtube, google video, and google maps (incl. street view) work fine, 
but slow.  A friend of mine with a very similar setup was not so lucky 
and still has problems with flash9 locking up FF.

 Hmm, lockups I haven't seen yet here.

 HTH,
Juergen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: flash9 checklist

2008-10-30 Thread Juergen Lock
In article [EMAIL PROTECTED] you write:
On Wed, Oct 29, 2008 at 07:05:51PM +0100, Gary Jennejohn wrote:
 On Wed, 29 Oct 2008 11:50:27 -0400
 Mikhail Teterin [EMAIL PROTECTED] wrote:
 
  Sent by Vladimir Grebenschikov:
   I've seen temporary FF lockups with flashblock FF plugin enabled.
  Same here. Sometimes it works and some times any page containing flash 
  will hang the entire browser. Doing a `killall npviewer.bin' (I use 
  nspluginwrapper) will unfreeze the browser like nothing happened. You'll 
  get the page -- but without the embedded flash, of course.
  I have only gotten Flash-9 to (mostly) work this morning -- thanks to 
  nox' checklist, and have not yet been able to investigate, why it hangs 
  on occasion...
  
 
 I don't have flashblock installed,

btw, noscript  flashblock :)  also it hasn't caused hangs here yet.

  but http://www.mtvmusic.com/ hangs
 firefox 100% of the time.  Strangely enough, under Linux it works just

Hi,
yes, I can confirm. thnx!

 No hangs here on mtvmusic.com with either linux flash9 + linux_base-fc4 +
native ff2 on 6.3/i386/UP or linux flash10 + linux_base-f7 + native ff3
on 7/amd64/SMP.  (my flash10 post is here:

http://lists.freebsd.org/pipermail/freebsd-emulation/2008-October/005438.html
)

 HTH,
Juergen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: flash-9, 10 on FreeBSD

2008-10-28 Thread Juergen Lock
On Tue, Oct 28, 2008 at 01:49:34PM -0400, Mikhail Teterin wrote:
 Sent by matt donovan:
 FreeBSD 7.1 should work with flash9 myself I had no luck so far but nox- 
 does say it should work
 I'm using 7.1-PRERELEASE as of Sep 23 and it does not work (yet?) Juergen, 
 please, confirm, that your fixes

(actually its not _my_ fixes, I only merged one of them for 6...)

  were committed after Sep 23 -- I'll be 
 happy to rebuild/reboot in that case. Thank you very much! Yours,

 Yes, as I said,
http://svn.freebsd.org/viewvc/base?view=revisionrevision=184075
was committed Oct 20 11:15:57 2008.

 HTH,
Juergen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


flash9 checklist (was: flash-9, 10 on FreeBSD)

2008-10-28 Thread Juergen Lock
On Tue, Oct 28, 2008 at 08:59:23AM -0400, Mikhail Teterin wrote:
 Hello!
 
 I'm having serious problems with Adobe's Flash 9 and 10 on my FreeBSD-7/amd64 
 system.
 
 If I try to use it directly with linux-firefox, the entire browser crashes 
 quickly. If I try www/nspluginwrapper with a native browser, the 
 wrapper-launched npviewer.bin seg-faults instead. Either way, the plugin does 
 not work...
 
 It appears, there was some activity recently in trying to fix these problems 
 (is it all in linprocfs/?) What is the current status? Thanks,
 
   -mi

Preliminary checklist for getting flash9 to work in native firefox:
(flash10 needs more ports work, I shall post about that seperately on
-emulation...)  If you have additions to this please post a followup to
this thread, keeping the Cc: (I'm not on -questions...)

1. You need RELENG_7 from at least Mon Oct 20 11:15:57 2008 UTC
(the relevant MFC commits are:
http://svn.freebsd.org/viewvc/base?view=revisionrevision=183819
http://svn.freebsd.org/viewvc/base?view=revisionrevision=184075
- a recent HEAD should also work of course.)  There are linprocfs patches
for RELENG_6 too (merging the former commit), but the latter commit can't
be merged to 6 (and 7.0) since they lack the cpuset bits, so flash9
probably won't work on SMP there.  (Although if you have SMP you probably
should be running 7 anyway. :)  Oh and if you do have SMP you also need to
use the ULE scheduler, the cpuset syscalls are not supported with 4BSD.
linprocfs patches for 6:
http://people.freebsd.org/~nox/linprocfs-6.3.patch
http://people.freebsd.org/~nox/linprocfs-6.4.patch

2. Your portstree needs to be from at least Sun Oct 19 17:37:28 2008 UTC
(the last www/linux-flashplugin9 commit is:
http://lists.freebsd.org/pipermail/cvs-ports/2008-October/158404.html
)

3. Make sure linprocfs is mounted to /compat/linux/proc .

4. Make sure www/nspluginwrapper, www/linux-flashplugin9 and dependencies
are installed and up to date(!).  (the default emulators/linux_base-fc4
should work, if you want to use a later one don't forget to set
compat.linux.osrelease=2.6.16 in sysctl.conf and OVERRIDE_LINUX_BASE_PORT
to whichever version you use in make.conf.  Note however that on 6, only
the default compat.linux.osrelease=2.4.2 really works.)

5. If the plugin doesnt show up in firefox' about:plugins, run
nspluginwrapper -i 
/usr/local/lib/npapi/linux-flashplugin/libflashplayer.so
and restart firefox.

6. And remember there's a security advisory for the current version of
flash9,

http://www.FreeBSD.org/ports/portaudit/78f456fd-9c87-11dd-a55e-00163e16.html
(if you use portaudit you need to `make -DDISABLE_VULNERABILITIES ...'
to be able to install the port), and fc4 seems to be eol'd too, so you
probably want to install something like the noscript firefox extension,
https://addons.mozilla.org/en-US/firefox/addon/722
and only allow plugins (and scripts, tho thats a different problem) on
sites you trust...

 And finally, if you still get crashes after following the above even
on pages that are reported to work now (like youtube) you probably want
to run `ktrace -di firefox...' and look at the output using linux_kdump
(thats the devel/linux_kdump port, you want to use a package), paying
specific attention to the lines above `PSIG SIGSEGV' (or whichever
signal you got), maybe there are still shlibs missing that the plugin
needs (NAMI ...something.so...), and if this is the case tell us about
it so the appropriate dependencies can be added to the relevant ports.
If you can't figure it out I guess it doesn't hurt to post the last
few 100 lines of the dump up to the relevant PSIG on -emulation...

 You may also want to check linked shlibs like this:
/compat/linux/bin/sh /compat/linux/usr/bin/ldd 
/usr/local/lib/npapi/linux-flashplugin/libflashplayer.so
and
/compat/linux/bin/sh /compat/linux/usr/bin/ldd 
/usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin
(if you see `not found' in there you know something is wrong) - although
that doesn't show libs that may be dlopen()d at runtime.

 Good luck,
Juergen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: qemu and usb

2007-08-15 Thread Juergen Lock
On Wed, Aug 15, 2007 at 12:57:36PM +0300, Andriy Gapon wrote:
 
 Is it possible on FreeBSD to provide access to host USB devices for qemu
 guests ?
 
 I tried playing with -usb and -usbdevice and to follow some linux
 how-to's but with no luck.

Does the following snippet from the ports' pkg-message help?

[...]
- if you want to use usb devices connected to the host in the guest
(usb_add host:... monitor command) you need to make sure the host isn't
claiming them, e.g. for umass devices (like memory sticks or external
harddrives) make sure umass isn't in the kernel (you can then still load it
as a kld when needed), also unless you are running qemu as root you then
need to fix permissions for /dev/ugen* device nodes: if you are on 5.x or
later (devfs) put a rule in /etc/devfs.rules, activate it in /etc/rc.conf
and run /etc/rc.d/devfs restart.  example devfs.rules:
[ugen_ruleset=20]
add path 'ugen*' mode 660 group operator
corresponding rc.conf line:
devfs_system_ruleset=ugen_ruleset
- still usb: since the hub is no longer attached to the uchi controller
and the wakeup mechanism, resume interrupt is not implemented yet linux
guests will suspend the bus, i.e. they wont see devices usb_add'ed after
its (linux') uhci module got loaded.  workaround: either add devices
before linux loads the module or rmmod and modprobe it afterwards.
[...]

 With this I was able to mount an usb cardreader from the guest.
(although that is pretty slow...)

Juergen
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Fwd: Re: 6.0-REL ports/emulators/qemu = PANIC

2006-01-20 Thread Juergen Lock
On Fri, Jan 20, 2006 at 05:38:00PM +0100, [EMAIL PROTECTED] wrote:
 El d?a Monday, January 02, 2006 a las 10:57:35PM +0100, Juergen Lock escribi?:
 
  On Mon, Jan 02, 2006 at 12:05:40PM +0100, [EMAIL PROTECTED] wrote:
   
   Hi Juergen,
   
   I've installed 6.0-REL from the CD which brings the qemu/kqemu
   as PORTVERSION=0.7.0s.20050717 but loading the kernel module
   kqemu.so (without even using it) crashes the system;
   
   to what PORTVERSION can I update, even to 0.8 with my 6.0-REL?
  
  Not sure why you get a panic, but you can of course use the latest
  port with 6.0-R.  Should you still get a panic with that then it
  would be nice if you could enable crashdumps and post the backtrace
  on -emulation and Cc me...
 
 When I moved from 5.4-REL to 6.0-REL I took my 4 GByte disk file
 for qemu with me having a W2k in it; the W2k starts fine on 6.0-REL's
 qemu but some Windows apps are crashing, for example OutLook complains
 about a wrong MAPI32.DLL; I went back to the 5.4-REL box, there the
 OutLook runs fine; shutdown W2k, copied over the disk image to 6.0-REL
 again and OutLook crashes; this is with 0.7.0s.20050717 and with 0.8.0;
 
 does W2k has somehow an information about the old host system and notes
 the shift?

Possibly, but I'm no windows expert.

 (Btw, please Cc me with followups that you want me to see, I'm not
subscribed on -questions...)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: foomatic-db-engine port broke?

2004-09-10 Thread Juergen Lock
I just stumbled across this and send-pr'd the fix (it needs to run aclocal).
See:
http://www.freebsd.org/cgi/query-pr.cgi?pr=71573

 You may need to grab the patch out of the raw pr because the ports tree
is still frozen and it may take a while before it gets in...

 (Found this via the archives; I'm not subscribed on -questions
so please Cc me with any followups if you want me to see them.)

 HTH,
Juergen
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]