Python tkinter packages not being installed
by Sarah Fish
I have had a problem getting a game to run since I put up FC-T2 about a
month ago. It needs Tkinter and it couldn't find it. Had the same
problem with FC1, but installing the Python-tools option via the
add-packages screen took care of it. I tried that with FC-T2 with no
success early on, but didn't have time to dig into it further.
Last night I downloaded T3 and spent today setting up my system to dual
boot Win98 & FC-T3. After all that Windows nonsense, I needed my game -
bad! So after I loaded T3, I started digging into just where Tkinter was
hiding. The T3 setup ran smoothly except that the partitioning section
wasn't happy about the dual boot status. It did it, but it didn't like it.
The tcl8.4 part was installed at setup. I finally located Tkinter on
the 4th T3 disc and tried installing it. It needed two other packages,
also on disk 4, tix-8.1.4-96.1.i386.rpm and tk-8.4.5-8.i386.rpm.
Just in case anybody else needs a Pysol fix :).....
Sarah Fish
Saratoga Springs, NY
16 years, 10 months
dell latitude d600 feedback - FC2 Test3
by Mike Lee
I am having the same problem on my Dell Inspiron 8000. Exact
problem.
When I go to log out, the screen keeps getting brighter and
brigher. Total system lockage.
Anyone have any tips?
Thanks.
Mike
--
Director Services - The NewMedia Group
Montana Tech Blackboard Administrator
16 years, 10 months
FC2 T2 -> T3 upgrade hoses your modprobe.conf - Alan
by RaXeT
Found the reason for my network suddenly getting hosed after using the
iso upgrade install from FC2 T2 to FC2 T3:
The upgrade process deletes original entries and recreates the following
single entry in modprobe.conf:
options tg3 irq=9
So I found a copy of my original FC2 T2 and replaced it and now I'm a
happy guy!
Here is what my modprobe.conf has been all along:
include /etc/modprobe.conf.dist
alias eth0 tg3
alias usb-controller ehci-hcd
alias usb-controller1 uhci_hcd
alias scsi_hostadapter sata_promise
alias scsi_hostadapter1 sbp2
alias scsi_hostadapter2 sata_promise
alias sound-slot-0 snd-emu10k1
alias sound-slot-1 snd-intel8x0
# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-emu10k1
alias snd-card-1 snd-intel8x0
# OSS/Free portion
alias char-major-14* soundcore
alias sound-slot-0 snd-card-0
alias sound-slot-1 snd-card-1
# card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
install fglrx /sbin/modprobe --ignore-install fglrx
install snd-card-0 /sbin/modprobe --ignore-install snd-card-0 && {
/usr/sbin/alsactl restore >/dev/null 2>&1 || :; }
remove snd-card-0 { /usr/sbin/alsactl store >/dev/null 2>&1 || :; };
/sbin/modprobe -r --ignore-remove
install sound-slot-0 /sbin/modprobe --ignore-install sound-slot-0 && {
/bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :; }
remove sound-slot-0 { /bin/aumix-minimal -f /etc/.aumixrc -S >>/dev/null
2>&1 || :; }; /sbin/modprobe -r --ignore-remove
install snd-card-1 /sbin/modprobe --ignore-install snd-card-1 && {
/usr/sbin/alsactl restore >/dev/null 2>&1 || :; }
remove snd-card-1 { /usr/sbin/alsactl store >/dev/null 2>&1 || :; };
/sbin/modprobe -r --ignore-remove
install sound-slot-1 /sbin/modprobe --ignore-install sound-slot-1 && {
/bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :; }
remove sound-slot-1 { /bin/aumix-minimal -f /etc/.aumixrc -S >>/dev/null
2>&1 || :; }; /sbin/modprobe -r --ignore-remove
#FIX for borked Alsa
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 &&
/usr/sbin/alsactl restore
remove snd-emu10k1 /usr/sbin/alsactl store && /sbin/modprobe -r
--ignore-remove snd-emu10k1
install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0 &&
/usr/sbin/alsactl restore
remove snd-intel8x0 /usr/sbin/alsactl store && /sbin/modprobe -r
--ignore-remove snd-intel8x0
16 years, 10 months
unknown video and graphic boot
by Jason Dravet
I have a system that has a Matrox P650 video card in it. FC does not
recognize this card and there is no reason is should. The drivers are closed
source and poorly maintained by matrox. I can install FC2T3 on the system
using text mode (linux text nofb) and everything works. There are a few
screen problems, but nothing cannot live with.
I would like to float the idea that if the video card is not recognized by
FC2 then the default init run level should be 3. Currently the default is 5
which makes the system unusable until I boot into single user mode and
change the inittab to boot to run level 3. What do you think of this idea?
_________________________________________________________________
Stop worrying about overloading your inbox - get MSN Hotmail Extra Storage!
http://join.msn.com/?pgmarket=en-us&page=hotmail/es2&ST=1/go/onm00200362a...
16 years, 10 months
Install Boot Tip for people without CDs and USB keys
by Phil Anderson
This only applies to you if:
- You have an existing linux installation
- You don't have (or don't want to use) a CD Drive
- You don't have (or don't want to use) a USB key
- You don't want to keep anything on your primary hard disk
This is the easiest (only????) way to install fedora 2 tests:
- Copy diskboot.img onto your existing hard disk
- Boot into single user mode
- run sync
- run dd if=diskboot.img of=/dev/hda
- Reset your computer (i.e. press the button on the case)
- Start installation!
If installation freezes looking for existing partitions (#121934):
ALT-F2
killall -9 lvm
ALT-F1
Phil
16 years, 10 months
Fresh install of T3 (observations)
by Fulko.Hew@sita.aero
I decided I'd do the fresh install of T3, I've had so
many symptoms during this experience, that I'm going to
put them all into one email, rather than to break them
out in the hope that someone can make sense of them.
Also I apologize in advance for not writting down all
the error messages along the way.
My environment: A Centrino based 'white box' laptop.
1/ Tried installing Core 2 test 3 from CDs... during install
I selected 'custom' install, and you get the python
core dump (discussed during yesterdays email exchange).
2/ Changed install choices to 'Workstation', and then later
said 'install everything'. That seemed to work.
3/ I use KDE so I tried using the desktop switcher tool
from the menu. It never came up. I then run 'switchdesk'
from the command line, and find a traceback:
File "/usr/share/switchdesk/switchdesk-gui.py", line 36, in ?
from backend import *
File "/usr/share/switchdesk/backend.py", line 18
PROGNAME = @NAME@
^
SyntaxError: invalid syntax
So I found 'switchdesk-helper' and ran it as
'switchdesk-helper KDE' and that worked.
4/ The task bar RHN applet indicated that new RPMs existed.
Clicking on it, running up2date I fetched the new version
of up2date and installed it.
5/ Running up2date again, I installed the remainder of the RPMs
NOTE: Each RPM had a GPG error!
6/ I tried running TuxRacer. it wouldn't start, and complained
about "SDL..." (sorry, I didn't write it down).
6/ I like to use xine, so I fetched apt-get from freshrpms
and installed it. Then I ran apt-get install xine.
It complained about two different versions of a 'policy'
file on the system and suggested a command to execute.
Doing that it complained about something else, and suggested
something else. After 3 rounds of that, I was able to install
xine, and it worked.
7/ I tried TuxRacer again. This time it worked fine. I'm puzzled.
8/ I'd sware that after I ran Kmix (under test2) that it left a
volume control applet on the task bar. Now I can't figure out
how to get the volume control applet _onto_ the task bar!
9/ This morning, the update icon indicated that 22 updates exist.
The alert box lists them all. But after running up2date,
it says my system 'was already up to date', ... but there are
still 22 new RPMs.
10/ Running 'yum update' basically worked, but it complained about
perl-XML-Twig, so doing 'yum --exclude perl-XML-Twig update'
gets past that error, and installed the rest.
11/ The update icon still says there are two RPMs outstanding:
perl-XML-Twig, and perl-Net-DNS, but up2date still insists
that my system is up to date.
12/ What happened to kernel 322? I was running that on test 2,
but test 3 didn't ask for it to be downloaded.
13/ My system still doesn't detect hot-plugged USB devices.
(Cold plugging is still OK).
Overall, the experience is poor, and discouraging (for a final
beta test).
16 years, 10 months
Install great but confused by errors
by BC
Install went great AWESOME distro !!!! Well done guys.
But after I used up2date I rebooted and was filled with a console full of security error messages like tried to
write file "denied" I am sure this is the SELinux stuff and I just don't get it yet. Is there a link for an
SELinux newbie to read ?
I couldn't get to a console because the messages were filling the console so I re-installed. I don't have a
screenshot of the errors but they all seemed to be something with selinux and the secure filesystem. Now I am
on a fresh install doing an up2date gain -- Maybe try 2 will be better. I do see this in the messages file
tough any ideas ? Is this something I should be putting in a diffetrent group If so I am sorry and please stear
me in the right direction.
tail -f messages
Apr 28 20:37:43 Penguin1 kernel: security_context_to_sid: called before initial load_policy on unknown context
root:object_r:staff_home_irc_t
Apr 28 20:37:43 Penguin1 kernel: security_context_to_sid: called before initial load_policy on unknown context
root:object_r:staff_mozilla_rw_t
Apr 28 20:37:43 Penguin1 last message repeated 2 times
Apr 28 20:37:43 Penguin1 kernel: security_context_to_sid: called before initial load_policy on unknown context
root:object_r:staff_home_screen_t
Apr 28 20:37:43 Penguin1 kernel: security_context_to_sid: called before initial load_policy on unknown context
root:object_r:staff_screensaver_rw_t
Apr 28 20:37:43 Penguin1 kernel: security_context_to_sid: called before initial load_policy on unknown context
root:object_r:staff_home_ssh_t
Apr 28 20:37:43 Penguin1 kernel: security_context_to_sid: called before initial load_policy on unknown context
root:object_r:staff_home_xauth_t
Apr 28 20:37:43 Penguin1 kernel: security_context_to_sid: called before initial load_policy on unknown context
system_u:object_r:default_context_t
Apr 28 20:37:43 Penguin1 kernel: security_context_to_sid: called before initial load_policy on unknown context
system_u:object_r:amanda_recover_dir_t
Apr 28 20:37:43 Penguin1 kernel: security_context_to_sid: called before initial load_policy on unknown context
system_u:object_r:staff_home_spamassassin_t
16 years, 10 months
autofs - automount - yp maps
by Robert Cavey
Trying to get started on Migrating from RedHat 9.0 to FC2 when it
releases. We use NIS for auth and mounting homedirs and shares in a
mixed Solaris, SGI and Linux environment.
VERS and ARCH because of the different platforms.
# ypcat auto.tools
-rw,intr,vers=$VERS <host_server>:/automnt/tools/share
-rw,intr,vers=$VERS <host_server>:/automnt/tools/lib/$ARCH
-rw,intr,vers=$VERS <host_server>:/automnt/tools/bin/$ARCH
# ypcat auto.home
<<<<SNIP>>>>
-rw,intr,vers=$VERS <host_server>:/homedir:<username>
<<<<SNIP>>>>
In RH9 we modified the line for localoptions in /etc/init.d/autofs
#
# NOTE Just for giggles to to pass "nfsvers and vers" to server
localoptions=' -D ARCH=linux8.0 rsize=32768,wsize=32768,nfsvers=3,vers3'
This DOES not work in FC2 .... It fails to mount any of the YP map
related mounts.
I even tried: localoptions=' -D ARCH=linux8.0 rsize=32768,wsize=32768'
and still does not mount.
automount complains about vers option now and not before, even removing
that options still fails to mount homedir.
I've had to create file maps local to the test machine. Has that much
changed in the new automount versions??
RH9.0# automount --version
Linux automount version 3.1.7
RH9.0# mount --version
mount: mount-2.11y
----
FC2t2# automount --version
Linux automount version 4.1.1
FC2t2# mount --version
mount: mount-2.12
Anyone seeing strange behavior in automount with yp ?
TIA
16 years, 10 months
hdd: status error
by Hannes Mayer
Hi all!
I just plugged a spare harddisk in my production machine, installed
test3 and all went very well :-D
ATI Radeon 7000, Flattron 995F detected; DDC worked, so I got the full
range of screen-resolutions from the beginning (despite the failing
DDC on my test machine)
Just one possibly minor issue - from dmesg:
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdd: status error: error=0x20LastFailedSense 0x02
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
This appears multiple times!
After all the CD-writer is at least reading CD's (didn't try burning so far)
Anyone else seeing this ?
Cheers,
Hannes.
16 years, 10 months