Broadcom 4318 wireless again ...
by Klaus-Peter Schrage
I have been struggling with my wireless since FC 5. Although on a
comparatively rare hardware (Apple ibook - ppc), problems were similar
to those reported by users with a different architecture. I have tried
the old-style driver (bcm43xx) as well as the new-style one
(bcm43xx_mac80211). After a lot of reading, some reports to bugzilla
(which turned out to be quite responsive and helpful, btw), and long and
sometimes frustrating experimentation, I got both drivers to associate
somehow, but eventually I stuck with the old one which seemed to be more
reliable and gave me a stable connection with WPA encryption.
Whenever a new kernel comes up (and when I have some spare time) I give
the new driver another try. Now, today we have 2.6.22.4-65 (Sunday
afternoon), so I fired up the new driver again (won't give you the
details now how I did the change) which is now called b43, but the name
is aliased to bcm43xx_mac8021.
Now to my problem: I can activate the device with the new driver, run
wpa_supplicant to associate to my access point, get an ip address with
dhclient, and iwconfig tells me that there is a connection established
with a speed of 54 Mbits/s, but - I can't get to the Internet. Pings are
extremely slow, when trying to go to a web site the browser tells me
that it is performing a look up but it ends up in an error (can't connect).
So what's going on there? There seems to be nothing wrong in the output
of dmesg, ifconfig, iwconfig ...
16 years, 9 months
puplet doesn't start in Fedora 8 Devel
by Mark
Hey,
First a little history.
When i installed Fedora 7 (kde live cd) for the first time i had the
puplet problem but back than it was with some files that where not
loaded by kde while it should have been. i reported a bug report in
bugzilla for that and it has been fixed in Fedora 7.
But now in Fedora 8 i have the problem again (not the same but with
the same result). This time it's not because of files that aren't
loaded but because of errors in puplet itself (or one of the programs
puplet is using):
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/dbus/connection.py", line
210, in maybe_handle_message
self._handler(*args, **kwargs)
File "/usr/bin/puplet", line 279, in updates_avail_handler
self.trayicon.set_tooltip(num)
TypeError: GtkStatusIcon.set_tooltip() argument 1 must be string or
None, not int
Traceback (most recent call last):
File "/usr/bin/puplet", line 384, in <module>
main()
File "/usr/bin/puplet", line 381, in main
p.run()
File "/usr/bin/puplet", line 371, in run
gtk.main()
KeyboardInterrupt
And i just filled in this as a bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=260681
16 years, 9 months
dev file goes missing after reboot
by Philip Walden
I have just started using jpilot to sync my Palm-top.
Jpilot expects to have /dev/pilot links to the device file connecting
the palmtop. In this case, I do a
ln /dev/ttyS0 /dev/pilot
chmod o+rw /dev/pilot
This work great. However, when I restart the computer the next day, the
link is gone. I have to recreate it.
This is the first I have noticed this behavior. Any idea as to why this
happens?
Phil
16 years, 9 months
ntpd filling log
by Ian Malone
Hi,
My dmesg and /var/log/messages are full of ntpd complaining,
it seems to be trying to get a IPv6 address:
Aug 28 10:20:11 atlas ntpd[3443]: bind() fd 21, family 10, port 123,
scope 4, addr fe80::20e:2eff:fe51:c525, in6_is_addr_multicast=
0 flags=0x11 fails: Cannot assign requested address
Aug 28 10:20:11 atlas ntpd[3443]: unable to create socket on ra0 (22)
for fe80::20e:2eff:fe51:c525#123
Aug 28 10:20:11 atlas ntpd[3443]: failed to initialize interface for
address fe80::20e:2eff:fe51:c525
Can anyone suggest why this might be happening all
of a sudden? (All I can think of is I changed from the
old rt2500 driver for my wireless card to the rt2x00
driver in current kernels.)
It does seem to be talking to IPv4 okay, since
there's one mention of:
Aug 28 10:16:45 atlas ntpd[3443]: synchronized to 198.144.194.12, stratum 2
Aug 28 10:18:50 atlas ntpd[3443]: synchronized to 198.38.16.2, stratum 2
Aug 28 10:18:55 atlas ntpd[3443]: synchronized to 195.179.15.117, stratum 3
System is 2.6.22.2-42.fc6
--
imalone
16 years, 9 months
Linux stops working
by Karl Larsen
I'm back on my old computer because of problems with the new one.
They were these:
1. I had the same 500kb RAM and hard drive from this computer in the new
one.
2. After a couple of problems grub started working just exactly as before.
3. But this F7 would start to load and then go into a kernel panic.
4. I tried FC6 and it was better. It loaded clear up but then I had no
"head" on my mouse. I could not see how to do anything.
5. I made a new F7 and it boots up but just like FC6 the mouse was
invisable :-)
I am just wiped out today. No ideas here except I may have had the
mouse and keyboard plugged in wrong. They are both PS2 connectors.
Any help will be much appreciated!
--
Karl F. Larsen, AKA K5DI
Linux User
#450462 http://counter.li.org.
16 years, 9 months
Today's update conflict
by Zoltan Boszormenyi
Hi,
when updating via yum, I saw this:
Transaction Check Error:
file /usr/lib/rpm/check-rpaths-worker from install of
rpm-build-4.4.2.1-1.fc6 conflicts with file from package
rpmdevtools-5.3-1.fc6
Best regards,
Zoltán Böszörményi
16 years, 9 months
CUPS problem
by Per Anton Rønning
After a long period of smooth sailing I suddenly encountered a CUPS problem.
Why I have got it is uncertain, maybe as a result of a yum upgrade run.
I had to reinstall FC 5 due to some disk trouble (possibly because a
blown fuse cut the electricity supply to my desk)
so I imagined that I would be interested in upgraded programs since I
burned the FC5 distro.
I remove and reinstall the printer (which btw. is online, lights are up
:-) ) and when sending a testpage to the printer i get the following
message:
"There was a problem sending CUPS test page to laser1 queue (my chosen
printer name)
/usr/bin/lpr connection refused
The following daemons are running:
cupsd
cups-config-daemon
I would be grateful to receive some help on this one.
Brgds
PAR
16 years, 9 months
Routing/Iptables/Forwarding = i have no idea
by Roger Grosswiler
Hey togehter,
until the update to Kernel 2.6.22.x i had a well working, forwarding, proxying and
natting infrastructure.
Since this Kernel it is not working no longer, as internal traffice outside squid gets
no longer forwarded.
i have forwarding-rules for a transparent-proxy, that work now again. Internal and
external. This must be because of squid forwarding the requests.
e-mail is no longer working, as the request doesn't get forwarded to the mailserver. it
stops somewhere on the firewall (3 nics, all use SNAT-Rules to mask their IP-Adresses).
Traceroute also stopps on the firewall, nothing goes outside. The forward-bit is set in
ip4_forward.
Did they change something in iptables?
Please help...
Thanks in advance
Roger
16 years, 9 months
memory fragmentation?
by charles f. zeitler
after a few days of moderately heavy use,
( running 2 or 3 gui-based apps simoltaneously,
typically konqueror, thoggen or sound juicer
& mebbe a third ) things tend to get _real_
slow (apps more than system functions) as my
swap usage starts climbing...
logging out/in alleviates this greatly, but
i usually wind up re-booting.
i should think 1 gb of ram was sufficient..
perhaps system tweak somewhere would help?
charles zeitler
: Do What Thou Wilt :
: Shall Be :
: The Whole of The Law :
--Aleister Crowley--
16 years, 9 months