FC4 Gnome Large Mouse Curser only has effect on first login
by Jerone Young
Choosing under Preferences->Mouse:Cursors you can choose to make your
mouse cursor Small , Medium, or Large. Well it seems this only affects
the first person who logs in. Once that person logs out, the next
person to login or the same person who just logged in will nolonger
have a large (or Medium) mouse cursor, it will stay the same small
size untill you move the mouse over a application window (ex.
firefox), but once you have the mouse back on the desktop it becomes
very small. If you use high resolution monitors or have disabilities
this can be a real pain.
18 years, 12 months
Making FC-4 branches in CVS (Core & Extras)
by Elliot Lee
Just a heads-up that the branching of Fedora Core and Fedora Extras
CVS repos is imminent. This means that the devel branch will start to be
used for Fedora Core 5 & Fedora Extras for FC5, while the FC-4 branch will
be the place to make updates targetted at FC4.
This branching should happen sometime today, depending on the builds that
are going on and how the FC4 release shapes up.
-- Elliot
18 years, 12 months
How to debug a hung system?
by Frank Chen
I installed FC3 on a ASUS Terminator C3 PC. It has a
VIA C3 CPU. The system becomes completely unresponsive
from time to time. The only thing I could do was to do
a hard reboot. Any suggestions on how to debug such a
system?
Thanks,
Frank
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
18 years, 12 months
Re: Fedora 3 kernel 2.6.10-1.770_FC3 and nfsroot problem for PXE/diskless (CONFIG_ROOT_NFS=y)
by Nico Bdav
This work with a kernel from kernel.org (linux-2.6.11.10.tar.bz2) and
exactly the same options set!
I think Redhat/Fedora kernel patches corrupt the Network booting options.
-------------------------------------------------------------------
hi all,
im trying to setup a diskless environnement with Fedora.
I use etherboot (as a bootable CDROM) to load linux kernel via PXE.
I have a dhcp, nfs and a tftp server working properly.
I have rebuild a 2.6.10-1.770_FC3 fedora kernel because latest 2.6.11
kernel series can't be build on my FC3.
I have rebuild a kernel (as an rpm, or via make bzImage), with the
NFSROOT option, to allow / mounting via NFS
pxelinux.0 boot normaly, load the kernel and the initrd, but when the
kernel try to moun the / partition, i obtain a kernel panic message:
VFS: Cannont open root device "nfs" or unknow-block(0,255)
Please append a correct "root=" boot option
Kernel Panic - not syncing : VFS: Unable to mount root fs on
unknow-block(0,255)
After that, i have tried many other options in the linux kernel (using
devfs instead udev, yes i know it's obsolete :)), and some other tips i
found but no one worked. Note that on the NFS Server i don't see any
packet using the NFS protocol.
Is there some special configuration with Fedora kernels and nfsroot option ?
Thanks for your suggest
¤ Here is my pxelinux.cfg/default file :
kernel FC3_PXE/vmlinuz
APPEND ramdisk_size=100000 root=/dev/ram0 nfsroot=192.168.1.14:/DOC/PXE/root
or
APPEND initrd=FC3_PXE/initrd.img ramdisk_size=10000 root=/dev/nfs
nfsroot=192.168.1.14:/DOC/PXE/root
¤ Here is the main kernel option needed (if i don't miss one!) and that
i have in my kernel:
grep -i "IP_PNP\|NFS\|RAMFS"
/DOC/PXE/root/boot/config-2.6.10-1.770_FC3nscheibl.20050525
CONFIG_INITRAMFS_SOURCE=""
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_IP_PNP_BOOTP=y
CONFIG_IP_PNP_RARP=y
CONFIG_RAMFS=y
CONFIG_CRAMFS=m
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_V4=y
CONFIG_NFS_DIRECTIO=y
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_ROOT_NFS=y
CONFIG_NCPFS_NFS_NS=y
¤ Here is the config of the diskless client in my dhcp server
(/etc/dhcpd.conf):
group {
next-server 192.168.1.14;
filename "linux-install/pxelinux.0";
option root-path "192.168.1.14:/DOC/PXE/root,v3,tcp,hard";
host PXED {
hardware ethernet 00:48:54:XX:YY:ZZ ;
fixed-address 192.168.1.133;
}
}
¤ And here is my nfsd config (/etc/exports):
/DOC/PXE/root *(ro,no_root_squash,sync)
/DOC/PXE/snapshot *(rw,no_root_squash,sync)
18 years, 12 months
rawhide report: 20050528 changes
by Build System
Updated Packages:
alsa-lib-1.0.9rc4-2
-------------------
* Fri May 27 2005 Martin Stransky <stransky(a)redhat.com> 1.0.9rc4-2
- alsacard utility for s-c-s
gnome-applets-1:2.10.1-9
------------------------
* Fri May 27 2005 Bill Nottingham <notting(a)redhat.com> 1:2.10.1-9
- remove setuid bit from cpufreq-selector, usermode-ify it
gnu-crypto-0:2.0.1-1jpp_5fc
---------------------------
* Thu May 26 2005 Thomas Fitzsimmons <fitzsim(a)redhat.com> - 0:2.0.1-1jpp_5fc
- Separate post and postun lines.
- Require libgcj, not gcc-java.
isdn4k-utils-3.2-28
-------------------
* Fri May 27 2005 Bill Nottingham <notting(a)redhat.com> 3.2-28
- remove setuid bit from vboxbeep
jessie-0:1.0.0-8
----------------
* Thu May 26 2005 Thomas Fitzsimmons <fitzsim(a)redhat.com> - 0:1.0.0-8
- Require libgcj.
- Separate post and postun requirement lines.
- Specify gnu-crypto jar directly.
nfs-utils-1.0.7-8
-----------------
* Thu May 26 2005 Steve Dickson <SteveD(a)RedHat.com> 1.0.7-8
- Fixed subscripting problem in idmapd (bz 158188)
screen-4.0.2-9
--------------
* Fri May 27 2005 Bill Nottingham <notting(a)redhat.com> - 4.0.2-9
- don't use utmp group for socket dir; use a dedicated screen gid
system-config-netboot-0.1.16-1_FC3
----------------------------------
* Thu May 26 2005 Jason Vas Dias <jvdias(a)redhat.com> 0.1.16-1
- fix bugs 144240, 148022, 149000, 153047, 154982
19 years
2.6.11-1.1287_FC4 kernel panic on intel 915
by sean darcy
I've installed kernel-smp-2.6.11-1.1287_FC4 on a Gigabyte
GA-8i915G Pro ( with has ICH6 ) with a pentium 4 2.8g HT
chip. It has a 300g maxtor SATA drive ( only drive ).
It boots, but then kernel panic mounting root.
It looks alright until:
SCSI subsystem initialized
Loading libata.ko module
Loading ata_piix.ko module
Loading dm-mod.ko module
ata_piix: Unknown symbol ata_scsi_ioctl
ata_piix: Unknown symbol ata_std_bios_param
ata_piix: Unknown symbol ata_tf_read
ata_piix: Unknown symbol ata_tf_write
ata_piix: Unknown symbol ata_bmdma_start
ata_piix: Unknown symbol ata_bmdma_setup
ata_piix: Unknown symbol ata_bmdma_stop
[...........]
ata_piix: Unknown symbol ata_port_start
insmod: error inserting '/lib/ata_piix.ko': -1 Unknown
symbol in module
and then all sorts of bad stuff happens.
I did go get 2.6.12-rc4 today. Built it with ata_piix
compiled in ( not as a module ). That worked. Booted.
Mounted root. However, same kernel panic if ahci.ko was
also compiled in. I also got a kernel panic when ata_piix
was a module and I removed ahci.ko from modules.
sean
19 years
alsa 1.0.9 out: epoch issue with FC4 test and rawhide
by Axel Thimm
Hi,
alsa 1.0.9 is out. Any chance this will make it into FC4? Probably
not, but could be one of the earliest updates.
alsa 1.0.9rcX has been packaged in such a way that it will be newer
than 1.0.9 unless an epoch bump is issued.
It has been discussed in the past that rawhide/test release do not
give any upgrade path guarantees for various reasons (among other to
be able to downgrade a bunch of packages like kde w/o having an epoch
inflation).
Should alsa be epochized (poor alsa), or the upgrade paths from
rawhide FC4tX broken? Personally I think epochs are really evil, and
setups with test releases need to be reinstalled anyway.
bugzilla is here: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=158859
--
Axel.Thimm at ATrpms.net
19 years
