realplayer and pulseaudio on F8
by Ian Malone
This is mainly a happy story, but things could be better.
Under F7 i686 I ran a nightly build of realplayer (from
<helixcommunity.org>) which understood ALSA. As
such I was able to set up a dmix device for it and it
played happily with the rest of the system.
When I moved to F8 I changed to using the x86_64
system, and the first thing I did was try a 64bit realplayer
build. After changing it to use the hardware device
(as it wont output to a pulse ALSA device), I discovered
that:
a. The sound warbled. The closest effect to it that I've
heard before is where there's a rate mismatch and the
buffer keeps running out.
b. The mozilla plugins wouldn't work, with or without
nspluginwrapper. I'm hypothesising that despite being
included with the 64 bit build they are intended for 32
bit realplayer.
So, I changed to a 32 bit build of RP. I have it outputting
through a dmix device set to 48kHz as otherwise it runs
too fast (i.e. if I load a file on the machine it plays it back
at an incredible speed and a high pitch). It now runs
okay both stand-alone and as a browser plugin.
However, because most things use pulseaudio now
(including flash and rhythmbox), using RP is mutually
exclusive with most other sound apps.
I /think/ the solution to this would be to set up a dmix
or plug device going into the pulseaudio ALSA device,
but I've had a couple of goes and can't work it out.
Any suggestions?
--
imalone
16 years
tar backup on tape doesn't work
by Budiono
Hi all,
I 'm just install a scsi card BusLogic BT-958 and HP DAT 40, on my
fedora core 6 system. I usually backup my system, using tar.
My problem is backup doesn't running well.
And this is my backup script:
#tar -b 1024 -cvf /dev/st0 /usr/local/src/my_home/yahoomail | bzip2 -9 >
/var/log/Backup.log.bz2
Backup only run a while, and archive some files in directory and then stop.
[root@mis-s155 ~]# tar -b 1024 -cvf /dev/st0
/usr/local/src/my_home/yahoomail | bzip2 -9 > /var/tmp/Backup.log.bz2
tar: Removing leading `/' from member names
tar: /dev/st0: Cannot write: Device or resource busy
tar: Error is not recoverable: exiting now
But when I put out -b parameter on tar. It run a while and not backup
directory at all
The backup script I used was running well when I'm using redhat 9.0 system.
I attach some message from my system
scsi: ***** BusLogic SCSI Driver Version 2.1.16 of 18 July 2002 *****
scsi: Copyright 1995-1998 by Leonard N. Zubkoff <lnz(a)dandelion.com>
scsi5: Configuring BusLogic Model BT-958 PCI Wide Ultra SCSI Host Adapter
scsi5: Firmware Version: 5.06I, I/O Address: 0xDC00, IRQ Channel:
225/Level
scsi5: PCI Bus: 2, Device: 3, Address: 0xFEAFF000, Host Adapter SCSI ID: 7
scsi5: Parity Checking: Enabled, Extended Translation: Enabled
scsi5: Synchronous Negotiation: Fast, Wide Negotiation: Enabled
scsi5: Disconnect/Reconnect: Enabled, Tagged Queuing: Enabled
scsi5: Scatter/Gather Limit: 128 of 8192 segments, Mailboxes: 211
scsi5: Driver Queue Depth: 211, Host Adapter Queue Depth: 192
scsi5: Tagged Queue Depth: Automatic, Untagged Queue Depth: 3
scsi5: SCSI Bus Termination: Both Enabled, SCAM: Disabled
scsi5: *** BusLogic BT-958 Initialized Successfully ***
scsi5 : BusLogic BT-958
Vendor: HP Model: C5683A Rev: YP61
Type: Sequential-Access ANSI SCSI revision: 03
scsi 5:0:3:0: Attached scsi generic sg1 type 1
st: Version 20050830, fixed bufsize 32768, s/g segs 256
st 5:0:3:0: Attached scsi tape st0
st0: try direct i/o: yes (alignment 512 B)
[root@mis-s155 ~]# mt -f /dev/st0 status
SCSI 2 tape drive:
File number=-1, block number=-1, partition=0.
Tape block size 0 bytes. Density code 0x26 (DDS-4 or QIC-4GB).
Soft error count since last status=0
General status bits on (1010000):
ONLINE IM_REP_EN
I very appeciate for any solution and comment.
Thank you
Budiono
16 years
Nagios yum install
by Mike Morraye
Dear List,
I just installed nagios on my Fedora 8 trough Yum. (standard repo's)
Now it seems that the rpm installs in different dir's than what you're
expected to do while installing from source.
Now it's quite hard to follow the official nagios manual, and i can't seem
to find modified ones.
What should I do?
16 years
Re: Port forwarding
by Andy
Hi,
Jari Marikainen wrote:
> I would like to forward incoming traffic from internet to
> "<195.198.111.x> port 80" to "<some other ip on the internet> port 80"
> in FC3 on the same interface.
I would try the DNAT/SNAT iptables targets, along the lines of:
iptables -t nat -A PREROUTING -p tcp --dport 80 -d 195.198.111.x \
-j DNAT --to-destination 65.114.4.69
iptables -t nat -A POSTROUTING -p tcp --dport 80 -d 65.114.4.69 \
-j SNAT --to-source <your external IP address on this machine>
The second line makes the real server send it's replies through the same
path (otherwise it will reply directly to the client)
You have to enable/allow forwarding for everything to work.
hth,
/Andy
16 years
Integrated bluetooth on Toshiba laptop wont work
by Zlatko
Hello to everybody, and greetings from Croatia (Europe)...
I need help...
Model of laptop: Toshiba Satellite P200-10C
My integrated bluetooth wont work, unless I do the following:
1. I start laptop with Windows Vista
2. I restart from Vista to Fedora
Each time I do this, bluetooth works fine. But, if I turn off computer,
and start it again directly to Fedora, bluetooth wont work, and system
wont recognize any bluetooth device.
I have described this problem on Fedora forum, also, but nobody answered
my question so far, even I have posted that post month ago.
Here is the link to that post:
http://forums.fedoraforum.org/forum/showthread.php?t=172988
If anybody knows how to handle this problem, I'll be very appreciated...
Also, my combination of pressing Fn + (F1-F9) wont work either...
Thanks
16 years
Fedora 8: X/Nautilus eating CPU
by wwp
Hello all,
now that my Fedora 8 is fully set up, I notice periodical short
hangs of the Desktop, making its use quite uncomfortable. `top` tells me
that the X and Nautilus processes are eating up to 30% of CPU every
15-20sec approximately (I can hear some disk activity as well).
Sensors applets are configured to poll on a longer period basis so it's
probably not them. No cron activity has been set. Anyway, I was running
the same applets with my Fedora Core 5 and GNOME and never encountered
such behaviour before.
For the record, nautilus-action is installed and there are few mounts
(USB disks) visible onto the Desktop. I've tried closing all apps (but
GNOME Desktop) and this still happens.
Anybody has this too? Or any hint?
Regards,
--
wwp
16 years, 1 month
ssh and port 22 problem, cont.
by Gerhard Magnus
Greetings!
I've made some progress on troubleshooting this "ssh & port 22 problem".
Here was my original post:
When I try to connect from a remote machine to my one at home
using ssh I get the error message "ssh: connect to host 64.146.133.1 port
22: Connection refused" -- but using ssh in the outgoing direction (i.e.
from home to the remote location) works fine.
Here's what's happened since:
I have two machines (PuteA and PuteB) sharing an ActionTec DSL modem. The IP
I was using was that of my "Gateway" ISP (64.146.133.1) -- an error. But
when I used the correct, static IP address of the ActionTec
(64.146.133.52) I got this message:
ssh: connect to host 64.146.133.52 port22: Connection refused
I thought I had port forwarding (for port 22) set correctly on the modem. For
troubleshooting, my ISP advised me to run "tcpdump -n host 192.168.0.2" on
PuteA, where 192.168.0.2 is the "internal" IP of PuteA. Then I logged on
to the remote location from PuteB and tried to ssh from there to PuteA
using the static IP address. The ssh from the remote location timed out
with the same "port 22: connection refused" message. The tcpdump on Pute
A gave this message:
> tcpdump: listening on eth0
> 17:27:33.662753 arp who-has 192.168.0.2 tell 192.168.0.1
where 182.168.0.1 is the "internal" IP of the modem. (Sorry if I have
this terminology wrong.)
My ISP says the problem is the firewall on PuteA and that he doesn't do linux
firewalls.
Here are my replies to the people who responded to my first post:
(1) "Do you have the firewall configured to deny incoming packets to port
22?"
How do I check this?
(2) "You need to check that sshd is running on your system."
Yes. I comes up with each boot. Also "service sshd status" gives
"sshd (pid 787) is running".
(3) "sshd uses /etc/hosts.allow and /etc/hosts.deny. Check that they are
configured to allow your remote machine in."
Both files have only commented lines.
(4) "Also, if your /etc/ssh/sshd_config file has VerifyReverseMapping
turned on, you will get kicked out if your remote address does not work
with a reverse dns lookup."
There's a "VerifyReverseMapping no" line in the file but it's been commented
out.
(5) "Just to be sure: when you are at home machine, try 'ssh localhost'.
If this works, you probably need to check your firewall."
It seems to work -- I ssh to the machine itself.
(6) "This is common on every system I have ever loaded with FC2. Your
iptables are blocking the connection. You can do one of the following:
iptables -A INPUT -m tcp -p tcp --dport 22 - j ACCEPT"
I tried this. The ssh to PuteA from the remote location still times out.
(7) "Oh yes I also took out the REDHAT firewall entrie as I dont have a
clue as to how to work with it."
I've fiddled endlessly with this "system tool" at each of the three levels
of security as well as using the "customize" option to set eth0 as a
trusted device and to allow incoming ssh. It doesn't show the settings
that actually exist.
(8) "If your fedora box is connected directly to a DSL modem, you should
be able to find your IP address by running ifconfig from the command
line and looking for 'inet addr:' (probably under 'eth0')."
eth0 Link encap:Ethernet HWaddr 00:40:05:81:60:8E
inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2184 errors:0 dropped:0 overruns:0 frame:0
TX packets:2005 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1122075 (1.0 Mb) TX bytes:190214 (185.7 Kb)
Interrupt:5 Base address:0x3000
Could this be the problem -- the "inet addr" of 192.168.0.4? As far as I
can tell, the modem is 192.168.0.1, PuteA is 192.168.0.2, and PuteB is
192.168.0.3. I haven't set anything as 192.168.0.4.
(9) "nmap 64.146.133.52"
(The 1598 ports scanned but not shown below are in state: closed)
Port State Service
23/tcp open telnet
53/tcp open domain
80/tcp open http
Shouldn't ssh be here? And what's telnet doing open? The books have me
scared to death of this... hackers, crackers, script kiddies, etc.
Thanks for the help!
Jerry Magnus
16 years, 1 month
Kernel 115 Doesn't Like iwl4965
by Christopher A. Williams
Since upgrading to kernel 2.6.23.14-115.fc8, my Intel iwl4965 wireless
card refuses to connect. It seems to think my hardware kill switch is
enabled, which is not true. The hardware radio switch is most certainly
on. Output from dmesg is at the end of this message.
If I roll back to kernel 2.6.23.14-107.fc8 (the previous one),
everything works as it should.
Laptop is an HP/Compaq 8510w with 4GB RAM and running F8 (64-bit).
Has anyone else run into this?
Cheers,
Chris
======================================
Here's the relevant output from dmesg:
ACPI: PCI Interrupt 0000:10:00.0[A] -> GSI 17 (level, low) -> IRQ 17
iwl4965: Radio disabled by HW RF Kill switch
ACPI: PCI interrupt for device 0000:10:00.0 disabled
ACPI: PCI Interrupt 0000:10:00.0[A] -> GSI 17 (level, low) -> IRQ 17
iwl4965: Radio disabled by HW RF Kill switch
ACPI: PCI interrupt for device 0000:10:00.0 disabled
irq 17: nobody cared (try booting with the "irqpoll" option)
Call Trace:
<IRQ> [<ffffffff8106aa87>] __report_bad_irq+0x30/0x72
[<ffffffff8106acd8>] note_interrupt+0x20f/0x253
[<ffffffff8106b5c4>] handle_fasteoi_irq+0xa9/0xd1
[<ffffffff8100e0fc>] do_IRQ+0xf1/0x161
[<ffffffff8100c0e1>] ret_from_intr+0x0/0xa
<EOI> [<ffffffff8125b7f9>] thread_return+0x5c/0xd8
[<ffffffff8101bdf7>] lapic_next_event+0x0/0xa
[<ffffffff8105064c>] tick_nohz_restart_sched_tick+0x12b/0x12f
[<ffffffff811d5a6a>] cpuidle_idle_call+0x0/0xa6
[<ffffffff8100aeb1>] cpu_idle+0xba/0xbc
[<ffffffff81431baa>] start_kernel+0x2cf/0x2db
[<ffffffff81431140>] _sinittext+0x140/0x144
handlers:
[<ffffffff811a69e9>] (yenta_interrupt+0x0/0xb9)
[<ffffffff811abe2f>] (usb_hcd_irq+0x0/0x52)
[<ffffffff88b13de3>] (azx_interrupt+0x0/0xc3 [snd_hda_intel])
Disabling IRQ #17
--
====================================================
In theory there is no difference between theory and practice.
In practice there is.
--Yogi Berra
16 years, 2 months
