Roadnav required library missing from x86_64 F8
by Gene Heskett
Specifically:
libexpat.so.0()(64bit)
Or at least this is what the attempted install of roadnav-0.19-1.f7.x86_64.rpm
claims. There is no x86_64 download yet for F8 on the roadnav site. Message
left for the author, but it looks like he's gone on to other things according
to his site.
I did a file against the libexpat.so.1.5.2 that was installed and linked to
libexpat.so.1, (this was a clean the disk install folks) and it claims to be
a 32 bit file. WTH?
Am I going to have to blow this install away and put the i386 back in to get a
library compatible with a 32 bit version of roadnav?
Or is it possible that the libexpat src rpm might build on x86_64? I've not
had that great a luck doing those operations over the years, its almost
easier for me to package things with checkinstall.
Thanks for any help on this.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
"We shall reach greater and greater platitudes of achievement."
-- Richard J. Daley
16 years, 4 months
Cannot Change essid using iwconfig
by Rick Bilonick
I know the bcm4318 mini pci wifi card works in my Dell Inspiron 2200
laptop - I had installed a hard drive with Fedora 8 (installed on a
different laptop) and I had no trouble using ndiswrapper and getting the
wireless nic to work perfectly. Now I've put the original hard drive
(that had Fedora 6 working with the same wireless nic) back in,
installed Fedora 8 (destroying all of the original data on the disk).
I've installed the same kernel, ndiswrapper, kernel modules, etc. that
is on the other hard drive with Fedora 8, went through the same process
but cannot get the wireless nic with the new Fedora 8 to work. Surely,
it can't be the hard drive (the laptop connects to the wired eth0
connection). If I put the other hard drive in with Fedora 8, the bcm4318
connects to the wireless network.
I've blacklisted bcm43xx, b43, and ssb (not sure ssb needs to be
blacklisted or even can be blacklisted).
I can get the nic to scan:
[root@localhost ~]# iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: 00:18:E7:0B:50:B0
ESSID:"default"
Protocol:IEEE 802.11g
Mode:Managed
Frequency:2.462 GHz (Channel 11)
Quality:50/100 Signal level:-64 dBm Noise
level:-96 dBm
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:bcn_int=100
Extra:atim=0
[root@localhost ~]#
ndiswrapper reports:
[root@localhost ~]# ndiswrapper -l
bcmwl5 : driver installed
device (14E4:4318) present (alternate driver: ssb)
I'm not sure what ssb is but when the other drive was it, I received the
same message and the nic connected to the wireless network.
dmesg reports:
ndiswrapper version 1.48 loaded (smp=yes, preempt=no)
ndiswrapper: driver bcmwl5 (Broadcom,12/22/2004, 3.100.46.0) loaded
ndiswrapper: using IRQ 1
(see below)
wlan0: ethernet device 00:14:a5:09:f5:28 using NDIS driver: bcmwl5,
version: 0x3642e00, NDIS version: 0x501, vendor: 'NDIS Network Adapter',
14E4:4318.5.conf
wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK;
AES/CCMP with WPA, WPA2, WPA2PSK
usbcore: registered new interface driver ndiswrapper
modprobe reports:
[root@localhost ~]# modprobe -l | grep ndiswrapper
/lib/modules/2.6.23.9-85.fc8/extra/ndiswrapper/ndiswrapper.ko
lspci reports:
[root@localhost ~]# lspci | grep BCM
02:03.0 Network controller: Broadcom Corporation BCM4318 [AirForce One
54g] 802.11g Wireless LAN Controller (rev 02)
If I try to manually configure the nic using iwconfig, I can set the key
but I CANNOT get it to set the essid:
[root@localhost ~]# iwconfig wlan0 essid default
[root@localhost ~]# iwconfig wlan0
wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.462 GHz Access Point:
Not-Associated
Bit Rate:54 Mb/s Tx-Power:25 dBm
RTS thr:2347 B Fragment thr:2346 B
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
(iwconfig will set the key, but I'm not showing the key info.)
When I use dhclient to obtain a lease, it tells me no leases were
offered (even though the other laptop is connected to the wireless
network and I've had them both wirelessly connected at the same time
when using Fedora 6 on the Dell).
I cannot figure out why iwconfig cannot set the essid.
What else can I check? Any ideas on what is wrong or how to fix this?
(I've tried the "native" driver for the bcm4318 but it just will not
work.)
Rick B.
P.S. I do get this message from dmesg but I don't think it has anything
to do with ndiswrapper:
irq 5: nobody cared (try booting with the "irqpoll" option)
[<c045b16a>] __report_bad_irq+0x36/0x75
[<c045b380>] note_interrupt+0x1d7/0x213
[<c057ae99>] usb_hcd_irq+0x21/0x4e
[<c045a807>] handle_IRQ_event+0x23/0x51
[<c045bcaf>] handle_level_irq+0x88/0xb9
[<c045bc27>] handle_level_irq+0x0/0xb9
[<c04074c3>] do_IRQ+0x8c/0xb9
[<c0405b6f>] common_interrupt+0x23/0x28
[<c0431dec>] __do_softirq+0x50/0xd3
[<c04073d5>] do_softirq+0x6c/0xce
[<c0444685>] tick_do_update_jiffies64+0x15/0xa8
[<c04401a1>] ktime_get+0xf/0x2b
[<c045bc27>] handle_level_irq+0x0/0xb9
[<c0431cc5>] irq_exit+0x38/0x6b
[<c04074d6>] do_IRQ+0x9f/0xb9
[<c043ff74>] hrtimer_start+0xfe/0x10a
[<c0403ddf>] default_idle+0x0/0x55
[<c0405b6f>] common_interrupt+0x23/0x28
[<c0403ddf>] default_idle+0x0/0x55
[<c042007b>] save_v86_state+0x19/0x12b
[<c0421f78>] native_safe_halt+0x2/0x3
[<c0403e18>] default_idle+0x39/0x55
[<c040340b>] cpu_idle+0xab/0xcc
[<c073fa6c>] start_kernel+0x32c/0x334
[<c073f177>] unknown_bootoption+0x0/0x195
=======================
handlers:
[<c057ae78>] (usb_hcd_irq+0x0/0x4e)
Disabling IRQ #5
16 years, 4 months
Where to type the SSID. newbie
by Jan Brosius
Hello,
I have a laptop and want to connect wirelessly to the internet. With
System>Administration>Network I have created a wireless network. But
where can I type my SSID?
Thanks for any help
Jan Brosius
16 years, 4 months
hp officejet 6310
by Neal Becker
Just got my hp officejet 6310. Doesn't show up as a choice on F8 (with all
current updates). I picked officejet 6300, seems to work. Is there an
update or does it really matter?
16 years, 4 months
Ralink 2500 chipset based pcmcia wireless card
by Ivan Virgili
I have just got hold of a GIGABYTE WMKG Wireless Notebook PCMCIA
Adapter. I installed the Ralink firmware on F8, restarted my laptop and
the card was recognised and started working immediately.
I now have got the following problems (one is really minor):
- the card is set to 1 Mb/s when the computer starts and I have to
manually run "iwconfig wlan1 rate 54M" to get the full speed.
How can set that permanently? Which file do I need to work on?
I had a look around (Google, my Fedora installation, etc.), but I did
not find a solution.
- the network adapter shows the power led always on (fine), but the link
led does not flash. It does work, because it goes on for one split of a
second when the card is "started". This is not a huge issue, but I would
like to figure out how to make it work.
Thank you,
Ivan
--
Ivan Virgili
GNU/Linux user #292882
16 years, 4 months
fedora 8 unknown process "exe"
by Joshua Andrews
Hi
Just curious about a process that shows up in top as exe--it uses a fair
amount of processor time and killing it does not seem to effect
anything. I am wondering what it is-and where it is.
`ps auxwwf` does not list anything named exe.
Thanks
- Joshua
16 years, 4 months
Re: No way to boot on 2.6.23.12-52.fc7
by Antonio Olivares
> ----- Original Message ----
> From: Dr P Dupre <pd520(a)york.ac.uk>
> To: For users of Fedora <fedora-list(a)redhat.com>
> Sent: Thursday, January 3, 2008 2:21:00 PM
> Subject: Re: No way to boot on 2.6.23.12-52.fc7
>
>
On Thu, 3 Jan 2008, Antonio Olivares wrote:
>
>
> --- Dr P Dupre <pd520(a)york.ac.uk> wrote:
>
>> On Thu, 3 Jan 2008, Antonio Olivares wrote:
>>
>>>
>>> --- pd520(a)york.ac.uk wrote:
>>>
>>>> Hello,
>>>>
>>>> I do not understand, I still cannot boot on the
>> new
>>>> kernel:
>>>> 2.6.23.12-52.fc7
>>>>
>>>> This is my grub.conf:
>>>> boot=/dev/sda
>>>> default=0
>>>> timeout=10
>>>> splashimage=(hd0,7)/boot/grub/splash.xpm.gz
>>>> hiddenmenu
>>>> password --md5 $1$Ey8yydw2$Ia5NHuLvdjduWOKIJM57u0
>>>> title Fedora (2.6.23.12-52.fc7)
>>>> root (hd0,7)
>>>> # kernel /boot/vmlinuz-2.6.23.12-52.fc7 ro
>>>> root=LABEL=/ rhgb quiet
>>>> selinux=0
>>>> kernel /boot/vmlinuz-2.6.23.12-52.fc7 ro
>>>> root=/dev/sda8 rhgb quiet
>>>> selinux=0
>>>> initrd /boot/initrd-2.6.23.12-52.fc7.img
>>>>
>>>>
>>>> title Fedora (2.6.21-1.3194.fc7)
>>>> root (hd0,7)
>>>> kernel /boot/vmlinuz-2.6.21-1.3194.fc7
>> ro
>>>> root=/dev/sda8 rhgb
>>>> quiet selinux=0
>>>> initrd
>> /boot/initrd-2.6.21-1.3194.fc7.img
>>>>
>>>>
>>>> I have not problem to boot on: 2.6.21-1.3194.fc7
>>>> With the new kernel, if I put:
>>>> kernel /boot/vmlinuz-2.6.23.12-52.fc7 ro
>>>> root=LABEL=/ rhgb quiet
>>>> selinux=0
>>>>
>>>> if fails because it try to boot on a /dev/sdb, so
>> I
>>>> force it to boot on
>>>> /dev/sda8, but I get:
>>>> setuproot: moving /dev failed No such file or
>>>> directory
>>>> setuproot: error mounting /proc
>>>> setuproot: error mounting /sys
>>>>
>>>> In what these 2 kernels are so different ?
>>>>
>>>> Regards
*** message truncated ****
> If you do an ls in /boot directory, what do you see?
>
> is the kernel in there,
config-2.6.21-1.3194.fc7 System.map-2.6.21-1.3194.fc7
config-2.6.23.12-52.fc7 System.map-2.6.23.12-52.fc7
grub/ vmlinuz-2.6.21-1.3194.fc7
initrd-2.6.21-1.3194.fc7.img vmlinuz-2.6.23.12-52.fc7
initrd-2.6.23.12-52.fc7.img
>
> What does
> $ rpm -qa kernel
> return?
kernel-2.6.21-1.3194.fc7
kernel-2.6.23.12-52.fc7
kernel-devel-2.6.23.12-52.fc7
kernel-doc-2.6.23.12-52.fc7
kernel-headers-2.6.23.12-52.fc7
--
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Patrick Dupré
pd520(a)york.ac.uk
University of York Department of
Chemistry
Heslington, York YO10 5DD United
Kingdom
Phone: +44-(0)-1904-434384 Fax:
+44-(0)-1904-432516
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Patrick,
Can you remove the line
# kernel /boot/vmlinuz-2.6.23.12-52.fc7 ro
root=LABEL=/ rhgb quiet
selinux=0
so that it matches the
title Fedora (2.6.21-1.3194.fc7)
one. If you have done that, and it did not work, then there might be something wrong with the initrd/or something else.
Regards,
Antonio
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
16 years, 4 months
Email delivery
by Tim Alberts
Question, where is it configured (in FC6) with sendmail/procmail that
mail is delivered to /var/spool/mail/<user>?
I see in the sendmail.cf that the mqueue is configured, but I use the m4
and there's nothing that says where mail is delivered. I figured at
first it was a procmail configuration, but all it does (with my setup)
is send it to spamassassin. I'm thinking the sendmail m4 line:
FEATURE(local_procmail, `', `procmail -t -Y -a $h -d $u')dnl
is setting the delivery location from the parameter $h and the user from $u?
16 years, 4 months
F8-x86_64 dccm problem & confusion
by Gene Heskett
Greetings;
Trying to make synce work on my lappy.
1) the error message when trying to start the synce-trayicon is missleading as
it names a failure to start dccm as a major problem, but parks itself in the
tray anyway.
2) starting synce-software-manager doesn't complain, but doesn't show anything
either. No pulldown config menu's or anything but the add-subtract etc
buttons. Is this the correct behaviour?
3) I finally installed the smart package manager because the updatern appears
to to have been dumbed down until it just barely survives. Using the search
function of SPM, I find that the package is actually named vdccm, and is
supposed to replace the dccm in the synce-kde package. Thats fine, but there
is no 'dccm' in the synce-kde package. And all the vdccm stuff that's
non-devel is installed already.
4) as user, do "strace /usr/bin/vdccm", which begins the failure stanza with a
getuid() returning a 500, then
setresuid(-1, 500, -1) = 0
setresuid(-1, 0, -1) = -1 EPERM (Operation not permitted)
getuid() = 500
geteuid() = 500
write(2, "[int main(int, char**)53:] ",27[int main(int, char**):53] ) = 27
write(2, "Could not start - either because"...,90Could not start - either
because vdccm is not installed suid, or you start directly as root) = 90
So I become root with an su - and repeat, and get essentially that same exact
output but without the setresuid's -EPERM return, it and the following
setresuid's are all = 0 this time:
getuid() = 0
setresuid(-1, 0, -1) = 0
setresuid(-1, 0, -1) = 0
getuid() = 0
geteuid() = 0
write(2, "[int main(int, char**)53:] ",27[int main(int, char**):53] ) = 27
write(2, "Could not start - either because"...,90Could not start - either
because vdccm is not installed suid, or you start directly as root) = 90
This does not appear to be an selinux problem, but a packaging problem, so how
do I fix the already installed /usr/bin/vdccm? Its perms now read -rwsr-xr-x
according to ls -l.
And 5) will this fix the synce-trayicon since its error message says dccm, not
vdccm?
6) what's the relationship to raki, do they clash and fsck things up fighting
over resources?
Thanks.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Veni, Vidi, VISA:
I came, I saw, I did a little shopping.
16 years, 4 months