nv locks - nouveau bails
by Jim Cornette
Is anyone else seeing problems with the nv and nouveau drivers? The
problem started for me yesterday. The computer locks up with the nv. I
then tried the nouveau which would load briefly, then exit.
Currently I am running mga on the primary and vesa on the NVidia card.
Not an ideal situation.
Jim
--
QOTD:
"Of course it's the murder weapon. Who would frame someone with
a fake?"
17 years, 1 month
ATI Radeon support
by Mike Chambers
I just bought a new Radeon X1300 and X fails to run on the radeon
driver, and has to use vesa, although it *seems* to detect what type
card it is. Is this card supported or is using vesa the only way it's
supported?
Matthious, does your freshrpms kmod stuff support fc7t2+rawhide or just
fc6?
--
Mike Chambers
Madisonville, KY
"Sex is like air, it's not important unless your not getting any!"
17 years, 1 month
perl-perlmenu broken
by Kwan Lowe
The perl-perlmenu package as shipped does not work with perl5. The original docs
suggest the following change to /usr/lib/perl5/vendor_perl/5.8.8/perlmenu.pm:
108,113c108,113
< #if ($] >= 5.001) { # Perl5 ONLY!
< #package Perl5::Menu_PL::Compat; # Don't pollute perlmenu.pm namespace
< #require Term::Cap; # Get Tgetent package
< #$term = Tgetent Term::Cap { OSPEED => 9600 }; # Define entry
< #sub perlmenu::getcap { $term->{"_" . shift()} }; # Define local subroutine
< #}
---
> if ($] >= 5.001) { # Perl5 ONLY!
> package Perl5::Menu_PL::Compat; # Don't pollute perlmenu.pm namespace
> require Term::Cap; # Get Tgetent package
> $term = Tgetent Term::Cap { OSPEED => 9600 }; # Define entry
> sub perlmenu::getcap { $term->{"_" . shift()} }; # Define local subroutine
> }
--
* The Digital Hermit http://www.digitalhermit.com
* Unix and Linux Solutions kwan(a)digitalhermit.com
17 years, 1 month
Unable to boot laptop with the 2.6.20-1.3003.fc7 kernel
by Paul F. Johnson
Hi,
When I try to boot using the 2.6.20-1.3003.fc7 kernel on the laptop
(Toshiba SatPro A10), I get the following error
VFS: Cannot open root device "VolGroup00/LogVol00" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
I don't have a problem with the 2990 kernel
The grub lines look like this
title Fedora (2.6.20-1.3003.fc7)
root (hd0,0)
kernel /vmlinuz-2.6.20-1.3003.fc7 ro
root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.20-1.3003.fc7.img
title Fedora (2.6.20-1.2990.fc7)
root (hd0,0)
kernel /vmlinuz-2.6.20-1.2990.fc7 ro
root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.20-1.2990.fc7.img
Has something changed between the 2990 and 3003 kernels (more than the
usual improvements)?
TTFN
Paul
--
Sie können mich aufreizen und wirklich heiß machen!
17 years, 1 month
iwlwifi, NetworkManager, .... ?
by Tom London
I haven't been able to get the 'new and cool' iwlwifi driver included
in the latest kernels working with my ipw3945 NIC.
'iwlist eth0 scan' appears to work properly, but NetworkManager
refuses to associate.
I recall in a previous thread that NM needed some patches to make this
work. Has that happened?
Fails to associate with open (thanks Google!), WEP or WPA networks.
Get these messages during boot:
wmaster0: Error for wireless request "Set Encode" (8B2A) ; SET failed
on device wmaster0 : Operation not supported
SIOCSIFFLAGS: operation not supported
I've killed NM and tried to associate manually, but haven't been successful.
Any hints?
Am I just jumping the gun on NM?
thanks,
tom
--
Tom London
17 years, 1 month
system-config-kickstart errors
by Kwan Lowe
I'm not sure if this is an anaconda or a system-config-kickstart error.
I installed fc7t2 from a kickstart file containing the following:
%packages
@admin-tools
@base
@base-x
@core
@editors
@java
@printing
@text-internet
comps-extras
cracklib-dicts
gnome-mime-data
kernel-headers
nash
rmt
tzdata
xkeyboard-config
After installation, the saved anaconda-ks.cfg contained a bunch of extra packages to
be removed such as:
-iprutils
-yaboot
-ppc64-utils
-elilo
-s390utils
-vixie-cron
-bc
-lsof
-ksh
If I run "system-config-kickstart anaconda-ks.cfg" it fails on each of the unknown
packages (e.g., yaboot is below):
Traceback (most recent call last):
File "/usr/bin/system-config-kickstart", line 81, in <module>
kickstartGui.kickstartGui(file)
File "/usr/share/system-config-kickstart/kickstartGui.py", line 180, in __init__
self.applyKickstart()
File "/usr/share/system-config-kickstart/kickstartGui.py", line 338, in
applyKickstart
self.packages_class.applyKickstart()
File "/usr/share/system-config-kickstart/packages.py", line 255, in applyKickstart
pkgs = self.y.pkgSack.returnNewestByName(pkg)
File "/usr/lib/python2.5/site-packages/yum/packageSack.py", line 318, in
returnNewestByName
return bestofeach.returnNewestByName(name)
File "/usr/lib/python2.5/site-packages/yum/packageSack.py", line 640, in
returnNewestByName
raise PackageSackError, 'No Package Matching %s' % name
PackageSackError: No Package Matching yaboot
If I delete the lines causing errors the utility will start. However, writing back a
new ks.cfg still appends the offending packages.
--
* The Digital Hermit http://www.digitalhermit.com
* Unix and Linux Solutions kwan(a)digitalhermit.com
17 years, 1 month
OpenOffice 2.2.0-12.1 crashes
by Marian Kopala
1).
oowriter
/usr/lib/openoffice.org/program/swriter.bin: symbol lookup
error: /usr/lib/openoffice.org/program/libspell680li.so: undefined
symbol: _ZN8Hunspell5spellEPKc
2).
rpm -qa openoffice.org*
openoffice.org-base-2.2.0-12.1
openoffice.org-writer-2.2.0-12.1
openoffice.org-xsltfilter-2.2.0-12.1
openoffice.org-impress-2.2.0-12.1
openoffice.org-pyuno-2.2.0-12.1
openoffice.org-testtools-2.2.0-12.1
openoffice.org-graphicfilter-2.2.0-12.1
openoffice.org-draw-2.2.0-12.1
openoffice.org-core-2.2.0-12.1
openoffice.org-javafilter-2.2.0-12.1
openoffice.org-langpack-pl_PL-2.2.0-12.1
openoffice.org-emailmerge-2.2.0-12.1
openoffice.org-calc-2.2.0-12.1
openoffice.org-math-2.2.0-12.1
3).
rpm -qa hunspell*
hunspell-pl-0.20070214-1.fc7
hunspell-1.1.5-2.fc7
hunspell-en-0.20040623-1.fc7
Marian
17 years, 1 month
fc7 name
by Adam Pribyl
What will be the official nameing for upcomming Fedora release? Fedora 7
or it will be also Fedora Core 7? Package names still contain .fc7 and
download directories are under core but my understanding was that with
Core and Extras merged there will be no Core anywhere anymore.
Adam Pribyl
17 years, 1 month
rawhide report: 20070322 changes
by Build System
Updated Packages:
fedora-release-6.92-1
---------------------
* Mon Mar 19 2007 Jesse Keating <jkeating(a)redhat.com> - 6.92-1
- Bump for Test 3
- No more eula in fedora-release, moved to firstboot
* Fri Feb 23 2007 Jesse Keating <jkeating(a)redhat.com> - 6.91-1
- Bump for Test 2
* Tue Feb 13 2007 Jesse Keating <jkeating(a)redhat.com> - 6.90-4
- Specfile cleanups
firstboot-1.4.34-1.fc7
----------------------
* Wed Mar 21 2007 Chris Lumens <clumens(a)redhat.com> - 1.4.34-1
- Reword EULA module.
- Fix screenshot code.
* Tue Mar 20 2007 Chris Lumens <clumens(a)redhat.com> - 1.4.33-1
- Don't chop off part of the left side background.
- Added a new EULA module.
kernel-2.6.20-1.3003.fc7
------------------------
* Wed Mar 21 2007 Dave Jones <davej(a)redhat.com>
- New version of the ondemand 'no wakeup whilst idle' patch
* Tue Mar 20 2007 Dave Jones <davej(a)redhat.com>
- 2.6.21-rc4-git5
Broken deps for s390
----------------------------------------------------------
systemtap - 0.5.10-1.fc7.s390 requires kernel >= 0:2.6.9-11
systemtap-runtime - 0.5.10-1.fc7.s390 requires kernel >= 0:2.6.9-11
17 years, 1 month
system-config-kickstart broken dep?
by Kwan Lowe
The package system-config-kickstart seems to require pykickstart, but it doesn't
appear to have been pulled in during the yum install:
[root@xm-fc7-001 tmp]# yum list "*kickstart*"
Installed Packages
system-config-kickstart.noarch 2.7.4-1.fc7 installed
Available Packages
pykickstart.noarch 0.100-1.fc7 development
--
* The Digital Hermit http://www.digitalhermit.com
* Unix and Linux Solutions kwan(a)digitalhermit.com
17 years, 1 month
