date:20160605

Re: First hint as to why kaffeine won't rx tv

2016-06-05 Thread Alexandre GRIVEAUX

Hi,

Maybe a firmware you need ?
Maybe found inside firmware-linux-nonfree.

Le 05/06/2016 05:16, Gene Heskett a écrit :
> Greetings all;
>
> Running it from the cli, I fand a channel scan is 100% errors because it 
> cannot tune a tuner it knows nothing about, in this case the "Oren 
> OR51132 VSB/QAM Frontend", and there apparently is nothing of that 
> package even installed.  Nor is it findable in the repo's.
>
> This is the support stuff for the pcHDTV3000 tv card.
>
> This is not in the package supplied with the card, and never was, but its 
> been part of the kernel since Hectors grandpa was a puppy!
>
> Is there some reason it is not part of the kernel install on debian?  It 
> has been present and usable in every distro I had installed for at least 
> a decade.
>
> Why not debian?
>
> Cheers, Gene Heskett

aarch64 qemu workaround

2016-06-05 Thread Mike

Folks,

I've been having a terrible time attempting to get debian to install into a
qemu aarch64 environment. It appears that this is an issue that has been
around for some time, though the only information I can find on it seems
dated.

https://gmplib.org/~tege/qemu.html

Scrolling down to the aarch64 section describes the situation. Has this
gotten any better? Is there a better workaround? I was hoping to be able to
automate this, but that's a pretty nasty hack just to get Debian up and
running.

Best,

Mike

Re: aarch64 qemu workaround

2016-06-05 Thread Christian Seiler

On 06/05/2016 09:43 AM, Mike wrote:
> https://gmplib.org/~tege/qemu.html
> 
> Scrolling down to the aarch64 section describes the situation.

Is what is describe there for aarch64 actually that bad? Having to
modify /etc/initramfs-tools/modules seems to be not too bad of a
thing to me... You could probably even preseed the installer with
a custom command, see [1] for details.

On the other hand - what do you want to use emulated aarch64 for?
Do you really need to have a full emulated system, to test the
kernel etc.? Or would a chroot be sufficient?

Because what works _really_ well with aarch64 is qemu-user, i.e.
running aarch64 binaries directly on your local system. There's a
nice tool called qemu-debootstrap with which you can automatically
create a chroot with a different architecture. Some are supported
better than others [2], but for aarch64 I've only had good
experiences with it. For example,

qemu-debootstrap --arch=arm64 sid aarch64-chroot

works out of the box. (jessie as well as sid.)

You can the just chroot into that,

chroot aarch64-chroot /bin/bash

and install stuff you like (just like any other regular chroot).
(Probably want to edit /etc/apt/sources.list first and copy
/etc/resolv.conf from your host system though.) The same caveats
that apply for normal chroots also apply here - and as with
regular chroots, I'd recommend using schroot to manage them once
they're set up. (Or use them as basis for pbuilder, if you want
to build Debian packages. Or both.)

Obviously anything that is related to hardware access won't work
in there (because no full system is emulated), but it's great
for e.g. compiling software - and it's a bit faster than using
the system emulator, because it just emulates the program's CPU
instructions and translates syscalls, it still uses your host's
kernel.

Regards,
Christian

[1] https://www.debian.org/releases/stable/arm64/apbs05.html.en#preseed-hooks
[2] Regarding only official ports: for ppc64el, you need to
export QEMU_CPU=POWER8; on powerpc (32bit) some floating
point instructions aren't properly emulated (it causes
trouble with software compiled with -mpowerpc-gpopt); and
the posix_fadvise() syscall is not mapped correctly on
some 32bit platforms (armel, armhf, powerpc and mips; on
mipsel it works though, funnily enough), but the aarch64
qemu-user port is in very good shape, from my experience.

Re: libreCAD, can't find help docs

2016-06-05 Thread Curt

On 2016-06-03, Gene Heskett  wrote:
> Greetings all;
>
> Wheezy, i386.
>
> libreCAD looks like a simple enough cad I could learn how to use but it 
> cannot find its help docs.

Did you give the built-in help system a try?

> I do not see a separate docs package in the repo's.
>
> Does anyone have a clue where they might be found?
>
> Thanks all.
>
> Cheers, Gene Heskett


-- 
Hypertext--or should I say the ideology of hypertext?--is ultrademocratic and
so entirely in harmony with the demagogic appeals to cultural democracy that
accompany (and distract one’s attention from) the ever-tightening grip of 
plutocratic capitalism. - Susan Sontag

Re: First hint as to why kaffeine won't rx tv

2016-06-05 Thread Gene Heskett

On Sunday 05 June 2016 03:02:10 Alexandre GRIVEAUX wrote:

> Hi,
>
> Maybe a firmware you need ?
> Maybe found inside firmware-linux-nonfree.
>
That entry seems to be empty.

However, I did find it. 3 files from the tarball from pchdtv.com, were,
when it was last built in Feb 2005, that are supposed to be put
in /lib/hotplug/firmware, are now, like all their ilk, in /lib/firmware
as
-rw-r--r-- 1 root root 12772 Feb 25 22:46 dvb-fe-or51132-qam.fw
-rw-r--r-- 1 root root 17532 Feb 25 22:47 dvb-fe-or51132-vsb.fw

I now believe I have all the modules showing in an lsmod:
gene@coyote:/lib/firmware$ lsmod |grep tuner -
tuner_simple 21273 2
tuner_types16409 1 tuner_simple
tuner 25658 2
v4l2_common12995 3 tuner,cx8800,cx88xx
videodev 130540 4 tuner,cx8800,cx88xx,v4l2_common
i2c_core 50108 17
drm,cx88_dvb,tuner,drm_kms_helper,tda8290,tda9887,i2c_algo_bit,cx88_vp3054_i2c,cx8800,cx88xx,v4l2_common,tveeprom,nouveau,tuner_simple,or51132,i2c_nforce2,videodev

And I was able to modprobe the or51132.ko from the kernel tree, but that
made no difference in the reported error. Which is:

Using DVB device 0:0 "Oren OR51132 VSB/QAM Frontend"
tuning ATSC to 57028000
inv:2 mod:7
ERROR tuning
: Inappropriate ioctl for device
Frontend closed
dvbsi: Cant tune DVB

For each channel in the Atsc us table, in this case shown, channel 2,
wash, rinse, repeat for all other channels. This is running a channel
scan from kaffeine. The channel scan, if kaffeine was launched from a
bash shell, also runs at a higher rate such that even if the
command "ioctl" was correct, the error comes back and cancels the 5
second timeout in approximately .75 seconds, no where near enough time
for this card to achieve a signal lock and show a picture.

I know this worked in the previous ubu 10-04 LTS's version of kaffeine,
8.6 IIRC, and this is 8.7 and doesn't work.

pcHDTV's own dtvscan does work, finding all the local on air channels and
reporting their signal strength ok. All the rest of the test utils that
came on the cd, dtvsnr and dtvsignal also work as expected. But even if
I feed kaffeine with the data that should at least tune it, no signal is
detected because the console has logged that same error as above, but
for channel 5.
xawtv's scanner, wscan also failed but for other reasons I don't have in
the bash history now, and since it was junk I had it removed.

Based on that, I am pointing my finger at the newer kaffeine now. But
its been years since I've filed a bug. No clue how to do it on wheezy at
what could be considered this late date. Or has someone else done that,
and found a fix?

[...]

Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page

52 matches

Mail list logo