irq 19: nobody cared
by JD
Kernel-3.7.0-rc6.git local build, belched out
[90658.498609] irq 19: nobody cared (try booting with the "irqpoll" option)
irq19 belongs to my Atheros AR-5008 mini-pci card.
This problem does not occur on kernels prior to 3.7.
Every time it happens, the card gets stuck in a mode
that renders it unusable, so that even restarting wpa_supplicant
does not restore association with AP. Only a reboot
fixes the problem until it happens again.
Is there a user util to force a soft reset of a mini-pci wifi card?
11 years, 5 months
VDPAU works, finally. (VDPAU, Nvidia proprietary drivers, XBMC, MythTV, RPi, Asus, rambling)
by linux guy
Short version.
VDPAU works, finally. libvdpau.i686 was recently updated to 0.5-1 in
Fedora 17. There have also been recent updates to the proprietary
nvidia drivers. The result of this is that vdpau works well, at least
with XBMC running on Fedora 17 on Asus 1012P EeeBox PCs.
Long version.
Asus (and others) made compact form factor PCs based on the Atom series
of processors. Asus called their line the EeeBox PC.
http://en.wikipedia.org/wiki/Asus_EeeBox_PC
One of these devices, the EB1012P was particularly suited for use as a
stand alone media center box (like Apple TV, only with Linux and on
steroids) because it had the right combination of size, cost, quiet
operation, just enough processing power and HDMI output.
The later was provided by an nVidia ION2 graphics controller
(http://en.wikipedia.org/wiki/Nvidia_ION), which was supposedly capable
of 4th generation pure video.
(http://en.wikipedia.org/wiki/Nvidia_PureVideo) The advantage of which
is supposedly the near total processing of various video streams by the
video card directly into HDMI video, aka VDPAU.
About 16 months ago I began working on a whole house video solution
using EB1012P devices as the media player component specifically because
of their VDPAU capability.
What I quickly learned was that VDPAU functionality was all but broken
on this device for the at least the 2 applications I was interested in,
namely XBMC and MythTV. The symptoms ranged from high CPU utilization
playing 1080P streamed mkv files, to screen stuttering to outright
freezing that only a reboot could cure.
Without VDPAU functionality, the EB1012Ps were just about useless as
media center devices. I put my devices to work in other capacities, but
kept one set up as a test device for XBMC and MythTV.
Fast forward to last week when I noticed that libvdpau had received an
update, the first I had seen in a while. Earlier this evening I ran an
update on Fedora 17 that included the libvdpau update. Thereafter I
started XBMC and ran the same 1080p mkv file that I have been fighting
to get displayed properly for the last 16 months.
I am happy to report that a stock F17 XBMC 11 (Eden) install on Fedora
17 running on my EB1012P now renders my test mkv stream perfectly.
I always thought that the EB1012P should be able to do this, but this is
the first time I have ever actually seen it done.
The sad part of all this is that the world has moved on from the
EB1012Ps. They are no longer in production, though one can probably
pick up used devices. At one point I was able to buy them for $120
new, without OS, RAM or a hard drive. Those items were inexpensive
additions, allowing me to equip the 1012Ps exactly how I needed them.
Times have changed and we now have Raspberry Pis capable of rendering
1080P HDMI output, for a lot less money. But the RPis don't have as
much RAM (512 MB versus 2GB), nor USB 3.0, nor an eSATA port, nor a hard
drive interface, nor built in WIFI nor a sleek case and power supply.
The EB1012P is fully capable of running KDE sessions on F17, browsing
with Firefox and displaying Youtube videos, making it a decently high
end media center, mostly thanks to the power of Linux and the 1012Ps
high end graphics capability. The 1012P running XBMC, KDE and Firefox
makes the applications and network integration built into 2012 high end
TVs look like a toy.
I think its a shame that the world essentially missed out on such a
wonderful device for lack of a working driver. Its amazing what one can
do with an EB1012P. Part of that spirit has been captured with RPi,
but the EB1012P did it first and does it with quite a bit more power and
finesse than the RPi does.
If anyone from Asus reads this, I highly recommend you bring these
devices back, with an improved processor, an infared receiver and a
slightly lower price point. RPi is just catching on as a media
center. An upgraded 1012P, unlocked, loaded with the right Linux
software and priced right could literally revolutionize how we use our TVs.
11 years, 5 months
F18: Fedora icon on gdm replaced by a fuzzy rectangle
by Nick Urbanik
Dear Folks,
I have installed Fedora 18 on seven machines using yum distro-sync,
and am happy with the result.
On my son's machine, however, gdm presents a fuzzy rectangular patch
instead of the Fedora logo. This is also the case with the icons at
the top right of the gdm screen, until you move the mouse over them.
Can anyone suggest what I might be able to do here?
--
Nick Urbanik http://nicku.org 808-71011 nick.urbanik(a)optusnet.com.au
GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24
I disclaim, therefore I am.
11 years, 5 months
finding out what wireless card -- asus ee701
by Robert Moskowitz
How do I find out what wireless card is in a system, and thus which
driver to install?
This is for my asus ee701 with the whole minimal business. I am not
seeing any wireless in NM, and I know it is there, as it was their once
ago in an earlier install (f14). When I did the install, I unclicked a
lot of drivers, thinking I knew what I had, but no wireless is showing.
Thus I really need to figure this out.
thank you.
11 years, 5 months
Brother HL5250 vs. Cups (Again)
by Jonathan Ryshpan
When I try to print double sided to this printer I get a single page
reading:
ERROR NAME;
stackunderflow
COMMAND;
pop
OPERAND STACK;
I almost always see this when printing anything double sided from
Firefox or from Acroread, but not when printing from Okular or
LibreOffice. There are other weird problems, but too erratic to
report.
System is Fedora-17 fully up to date, running on x86_64 hardware. The
ppd file appears to come from:
foomatic-db-ppds-4.0-31.20120103.fc17.noarch
Has anyone else seen this? What's the problem? How can it be fixed?
Any ideas on how to debug?
Thanks in advance - jon
11 years, 5 months
strange warnings in yum.log
by Reindl Harald
what the hell does this mean?
Nov 28 14:47:38 perl-HTTP-Tiny-0.012-217.fc17.noarch: ts_done name in te is grub2 should be
perl-HTTP-Tiny-0.012-217.fc17.noarch
Nov 28 14:47:38 perl-Test-Simple-0.98-217.fc17.noarch: ts_done name in te is perl-HTTP-Tiny should be
perl-Test-Simple-0.98-217.fc17.noarch
Nov 28 14:47:38 3:perl-version-0.88-217.fc17.noarch: ts_done name in te is perl-Test-Simple should be
3:perl-version-0.88-217.fc17.noarch
Nov 28 14:47:39 1:perl-parent-0.225-217.fc17.noarch: ts_done name in te is perl-version should be
1:perl-parent-0.225-217.fc17.noarch
Nov 28 14:47:39 hplip-3.12.10-4.a.fc17.x86_64: ts_done name in te is perl-parent should be
hplip-3.12.10-4.a.fc17.x86_64
Nov 28 14:47:39 1:hpijs-3.12.10-4.a.fc17.x86_64: ts_done name in te is hplip should be 1:hpijs-3.12.10-4.a.fc17.x86_64
Nov 28 14:47:39 openssh-server-5.9p1-27.fc17.x86_64: ts_done name in te is hpijs should be
openssh-server-5.9p1-27.fc17.x86_64
Nov 28 14:47:40 openssh-clients-5.9p1-27.fc17.x86_64: ts_done name in te is openssh-server should be
openssh-clients-5.9p1-27.fc17.x86_64
Nov 28 14:47:41 hplip-libs-3.12.10-4.a.fc17.x86_64: ts_done name in te is openssh-clients should be
hplip-libs-3.12.10-4.a.fc17.x86_64
Nov 28 14:47:41 1:perl-Digest-SHA-5.61-217.fc17.x86_64: ts_done name in te is hplip-libs should be
1:perl-Digest-SHA-5.61-217.fc17.x86_64
Nov 28 14:47:42 libreport-2.0.19-1.fc17.x86_64: ts_done name in te is grub2-tools should be
libreport-2.0.19-1.fc17.x86_64
Nov 28 14:47:42 libreport-python-2.0.19-1.fc17.x86_64: ts_done name in te is perl-Digest-SHA should be
libreport-python-2.0.19-1.fc17.x86_64
Nov 28 14:47:42 perl-Digest-MD5-2.51-217.fc17.x86_64: ts_done name in te is libreport should be
perl-Digest-MD5-2.51-217.fc17.x86_64
Nov 28 14:47:42 1:perl-Module-Pluggable-3.90-217.fc17.noarch: ts_done name in te is libreport-python should be
1:perl-Module-Pluggable-3.90-217.fc17.noarch
Nov 28 14:47:43 perl-PathTools-3.33-217.fc17.x86_64: ts_done name in te is perl-Digest-MD5 should be
perl-PathTools-3.33-217.fc17.x86_64
Nov 28 14:47:43 1:perl-Pod-Escapes-1.04-217.fc17.noarch: ts_done name in te is perl-Module-Pluggable should be
1:perl-Pod-Escapes-1.04-217.fc17.noarch
Nov 28 14:47:43 1:perl-Pod-Simple-3.16-217.fc17.noarch: ts_done name in te is perl-PathTools should be
1:perl-Pod-Simple-3.16-217.fc17.noarch
Nov 28 14:47:44 4:perl-libs-5.14.3-217.fc17.x86_64: ts_done name in te is perl-Pod-Escapes should be
4:perl-libs-5.14.3-217.fc17.x86_64
Nov 28 14:47:44 4:perl-macros-5.14.3-217.fc17.x86_64: ts_done name in te is perl-Pod-Simple should be
4:perl-macros-5.14.3-217.fc17.x86_64
Nov 28 14:47:44 4:perl-5.14.3-217.fc17.x86_64: ts_done name in te is perl-libs should be 4:perl-5.14.3-217.fc17.x86_64
Nov 28 14:47:44 openssh-askpass-5.9p1-27.fc17.x86_64: ts_done name in te is perl-macros should be
openssh-askpass-5.9p1-27.fc17.x86_64
Nov 28 14:47:45 libreport-filesystem-2.0.19-1.fc17.x86_64: ts_done name in te is perl should be
libreport-filesystem-2.0.19-1.fc17.x86_64
Nov 28 14:47:45 hplip-common-3.12.10-4.a.fc17.x86_64: ts_done name in te is openssh-askpass should be
hplip-common-3.12.10-4.a.fc17.x86_64
Nov 28 14:47:45 openssh-5.9p1-27.fc17.x86_64: ts_done name in te is libreport-filesystem should be
openssh-5.9p1-27.fc17.x86_64
Nov 28 14:47:45 bash-4.2.39-1.fc17.x86_64: ts_done name in te is hplip-common should be bash-4.2.39-1.fc17.x86_64
Nov 28 14:47:46 fftw-libs-single-3.3.1-3.fc17.x86_64: ts_done name in te is openssh should be
fftw-libs-single-3.3.1-3.fc17.x86_64
Nov 28 14:47:46 fftw-libs-double-3.3.1-3.fc17.x86_64: ts_done name in te is bash should be
fftw-libs-double-3.3.1-3.fc17.x86_64
Nov 28 14:47:46 fftw-libs-long-3.3.1-3.fc17.x86_64: ts_done name in te is fftw-libs-single should be
fftw-libs-long-3.3.1-3.fc17.x86_64
Nov 28 14:47:47 fftw-libs-quad-3.3.1-3.fc17.x86_64: ts_done name in te is fftw-libs-double should be
fftw-libs-quad-3.3.1-3.fc17.x86_64
11 years, 5 months
F17 - yum does not update!
by Cristian Sava
Hi all,
I installed F17 x64 in a virtual box and resulted F17 fully updated and
works well.
But when trying to install any new package ...
>yum install iptraf
....
iptraf-ng-1.1.1-1.fc17.x86_64. FAILED curl#7 - "Couldn't connect"
....
Trying other mirror.
and so on!
Same as
http://lists.fedoraproject.org/pipermail/users/2012-November/427243.html
Modifying in yum.repos.d does not help.
Same install with Centos 6.3 x64 with same result!
Why this, what's wrong now? Any sugestion?
Thanks
C. Sava
11 years, 5 months
usb ethernet adapter
by Gary Hodder
trying to get a Davicom DM9601 USB Ethernet adapter to work with Fedora
17. The driver keeps turning the carrier off on the device.
Anyone know a fix for this or am I better off getting a better one.
If I need to get a better one what cheapies on Ebay are known to work?
This is for a dell laptop to connect to a adsl modem and the on board
network card will connect to the local network switch.
The laptop will be the local server and run off solar power.
Below is a cut from the messages file.
Thanks
Gary.
Nov 28 21:33:58 groucho kernel: [ 3387.653275] usb 6-1: New USB device
found, idVendor=0fe6, idProduct=9700
Nov 28 21:33:58 groucho kernel: [ 3387.653282] usb 6-1: New USB device
strings: Mfr=0, Product=2, SerialNumber=0
Nov 28 21:33:58 groucho kernel: [ 3387.653287] usb 6-1: Product: USB 2.0
10/100M Ethernet Adaptor
Nov 28 21:33:58 groucho kernel: [ 3387.692606] dm9601 6-1:1.0: eth0:
register 'dm9601' at usb-0000:00:1d.0-1, Davicom DM9601 USB Ethernet,
00:e0:4c:53:44:58
Nov 28 21:33:59 groucho NetworkManager[652]: <warn> failed to allocate
link cache: (-10) Operation not supported
Nov 28 21:33:59 groucho NetworkManager[652]: <info> (eth0): carrier is
OFF
Nov 28 21:33:59 groucho NetworkManager[652]: <error> [1354098839.91292]
[nm-device-ethernet.c:456] real_update_permanent_hw_address(): (eth0):
unable to read permanent MAC address (error 0)
Nov 28 21:33:59 groucho NetworkManager[652]: <info> (eth0): new Ethernet
device (driver: 'dm9601' ifindex: 20)
Nov 28 21:33:59 groucho NetworkManager[652]: <info> (eth0): exported
as /org/freedesktop/NetworkManager/Devices/18
Nov 28 21:33:59 groucho NetworkManager[652]: <info> (eth0): now managed
Nov 28 21:33:59 groucho NetworkManager[652]: <info> (eth0): device state
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov 28 21:33:59 groucho NetworkManager[652]: <info> (eth0): bringing up
device.
Nov 28 21:33:59 groucho kernel: [ 3387.958274] dm9601 6-1:1.0: eth0:
link up, 100Mbps, full-duplex, lpa 0xFFFF
Nov 28 21:33:59 groucho NetworkManager[652]: <info> (eth0): carrier now
ON (device state 20)
Nov 28 21:33:59 groucho NetworkManager[652]: <info> (eth0): preparing
device.
Nov 28 21:33:59 groucho NetworkManager[652]: <info> (eth0): deactivating
device (reason 'managed') [2]
Nov 28 21:33:59 groucho NetworkManager[652]: <info> (eth0): carrier now
OFF (device state 20)
Nov 28 21:34:01 groucho avahi-daemon[647]: Registering new address
record for fe80::2e0:4cff:fe53:4458 on eth0.*.
11 years, 5 months
f17 - minimal + gnome :: init 5 does not work
by Robert Moskowitz
I remembered that on a non-graphical system (actually I did a graphical
install, but changed the runlevel to 3) was just to type in:
init 5
So I tried it and things seem to just hang. So I rebooted. Probably
need to install more than just gnome on minimal to get gnome?
11 years, 5 months
