[fc2t1] Can't boot 2.6.6X kernels
by Harry Putnam
I've never gotten sound to work in several attempts so thought maybe
updating to latest kernel would help.
After rpm -ivh and boot that kernel it stalls at the line that says
something like:
Freeing memory... blah 152kb or something similar.
There it hangs indefinitely. I see no other output that looks
ominous to that point. Any ideas here what might be going on?
20 years
Fedora Core 1 Test Update: vsftpd-1.2.1-4.fc1
by Bill Nottingham
---------------------------------------------------------------------
Fedora Test Update Notification
FEDORA-2004-141
2004-05-25
---------------------------------------------------------------------
Product : Fedora Core 1
Name : vsftpd
Version : 1.2.1
Release : 4.fc1
Summary : vsftpd - Very Secure Ftp Daemon
Description :
vsftpd is a Very Secure FTP daemon. It was written completely from
scratch.
---------------------------------------------------------------------
Update Information:
This update upgrades vsftpd to the code shipped in Fedora Core 2. Notable is
a fix for the signal handling in the listener code that can cause the
listener to hang. (bug #109933, #113364)
If no new regressions are found, this will be pushed as a final update by
Friday, May 28.
---------------------------------------------------------------------
* Tue May 25 2004 Bill Nottingham <notting(a)redhat.com> 1.2.1-4.FC1
- build for FC1
* Mon May 03 2004 Bill Nottingham <notting(a)redhat.com> 1.2.1-5
- fix all references to vsftpd.conf to be /etc/vsftpd/vsftpd.conf,
including in the binary (#121199, #104075)
* Thu Mar 25 2004 Bill Nottingham <notting(a)redhat.com> 1.2.1-4
- don't call malloc()/free() in signal handlers (#119136,
<olivier.baudron(a)m4x.org>)
* Fri Feb 13 2004 Elliot Lee <sopwith(a)redhat.com>
- rebuilt
* Mon Nov 24 2003 Karsten Hopp <karsten(a)redhat.de> 1.2.1-1
- update to 1.2.1, which fixes #89765 and lot of other issues
- remove manpage patch, it isn't required anymore
- clean up init script
- don't use script to find libs to link with (lib64 issues)
---------------------------------------------------------------------
This update can be downloaded from:
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/1/
420fa4030b0794876ba57277a65f6cd7 SRPMS/vsftpd-1.2.1-4.fc1.src.rpm
504562451ebe59f6dc25db7902325f79 i386/vsftpd-1.2.1-4.fc1.i386.rpm
89fa426bcd80a82bb32547d6f03e054b i386/debug/vsftpd-debuginfo-1.2.1-4.fc1.i386.rpm
8042b35120e06bdf5487c61d03095a9f x86_64/vsftpd-1.2.1-4.fc1.x86_64.rpm
80a242b75160937f26206177be7ada71 x86_64/debug/vsftpd-debuginfo-1.2.1-4.fc1.x86_64.rpm
This update can also be installed with the Update Agent; you can
launch the Update Agent with the 'up2date' command. You may
need to edit your up2date channels configuration. Within
/etc/sysconfig/rhn/sources enable the following line:
yum updates-testing http://fedora.redhat.com/updates/testing/fedora-core-1
---------------------------------------------------------------------
20 years
FC2 and keyboard layouts
by Mohamed Eldesoky
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Any one noticed that you can't change the keyboard layout ??
It is not only me, but other friends has suffered the same too.
I am using KDE.
Regards
Mohamed Eldesoky
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAsbzl2FHsOWMJBKMRAszrAKDQB8EYaYfhSOU1Md0jHvH5+/Y5VQCgxku3
zYQejGx/yb7YFjas5/abqbI=
=E7ZF
-----END PGP SIGNATURE-----
20 years
Error messages on new version of autofs on FC2
by David Pullman
We have a several indirect NIS maps that support Fedora, RedHat 9, SGI
and Sun workstations, including a homedirs map. The homedirs mounts are
failing under FC2, where they work fine with the other OSs listed,
including FC1.
The homedirs maps have a quota option specified, for example one line in
the map is:
mel -quota meles1:/meles1/home_mel
The syslog message is:
May 21 17:08:02 ballyhoo automount[7854]: failed to mount /home/mel
May 21 17:08:02 ballyhoo automount[7856]: >> Unsupported nfs mount
option: quota
May 21 17:08:02 ballyhoo automount[7856]: mount(nfs): nfs: mount failure
meles1:/meles1/home_mel on /home/mel
Anyone see anything like this?
Is this related to the new autofs version? Is it possible to correct
this in the autofs init script, or is it only going to be encountered at
the time it parses the homedirs map?
Thanks for any input.
--David
20 years
Re: fc2 kernel panic
by Listman
On Mon, 2004-05-24 at 11:15 -0400, Robert P. J. Day wrote:
> On Mon, 24 May 2004, Ted Kaczmarek wrote:
>
> > On Mon, 2004-05-24 at 06:52 -0400, Thomas Molina wrote:
> > > > root@inyoureyes boot]# ls -latr initrd-2.*
> > > > -rw-rw-r-- 1 root root 276009 Aug 20 2003 initrd-2.4.20-20.9.img
> > > > This one post yum upgrade.
> > > > -rw-r--r-- 1 root root 195900 May 23 18:28initrd-2.6.5-1.358smp.img.old
> > > > This one I created "mkinitrd 2.6.5-1.358"
> > > > -rw-r--r-- 1 root root 194628 May 23 18:34 initrd-2.6.5-1.358smp.img
> > > > And Arjans latest test kernel.
> > > > -rw-r--r-- 1 root root 195429 May 23 19:13 initrd-2.6.6-1.376smp.img
> > > >
> > > >
> > > > mkrootdev: label / not found
> > > > mount: error 2 mounting ext3
> > > > pivotroot: pivot_root(/sysroot/initrd) failed: 2
> > > > umount /initrd/proc failed: 2
> > > > Freeing unused kernel memory: 188k freed
> > > > Kernel panic: No init found. Try passing init=option to kernel
>
> this is one of the banes of my current existence -- people claiming
> "kernel panic" when it's just a missing/broken init.
>
> i know it sounds pedantic, but i'm working on a project that involves
> messing considerably with the init structure (replacing it with minit,
> actually, so it's not unexpected to mess that up and get a broken init
> and get that kind of error message.)
>
> given that i'm looking after the kernel, i freak out just a little when
> someone comes running up, saying, "i just got a kernel panic!". then i
> see that it's a boot-time init problem, and i calm down.
>
> so, might it be possible to be a bit more precise in the subject lines
> than the generic, catch-all "fc2 kernel panic"?
>
> rday
I apologize for the lack of detail in my subject, but I thought I made
it crystal clear in the body.
Us less experienced users depend on feedback from people just like you,
whether it be good or bad.
I would love to learn more about your minit project, so please do keep
us posted :-)
Sorry for any trouble my poor subject matter might have caused you.
Regards,
Ted
20 years
Back up to square one with sound config
by Harry Putnam
Setup: FC2 test1
Kernel: kernel-2.6.6-1.376
I've been trying to get sound working for several days on and off.
Went back and read the relevant posts or at least what I could find.
Tried several of the suggestions ... still not getting anywhere.
At this point I have so much crap in /etc/modprobe.conf and in
/etc/rc.d/rc.local I'd like to clean the slate and start from square
one.
Has anyone posted a step by step guide to getting this setup? It
seems to be getting unduly complex.
Running lsmod I see a pile of sound related stuff a yard long.
Seems like a lot of junk to make a sound.
dmesg shows this sound related output:
intel8x0_measure_ac97_clock: measured 49486 usecs
intel8x0: clocking to 41161
PCI: Setting latency timer of device 0000:00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 49487 usecs
intel8x0: clocking to 41161
PCI: Setting latency timer of device 0000:00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 49487 usecs
intel8x0: clocking to 41161
Current /etc/modprobe.conf:
alias eth0 3c59x
alias eth1 e100
include /etc/modprobe.conf.dist
alias usb-controller ehci-hcd
alias usb-controller1 ohci-hcd
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
# [HP 05/23/04 09:25 alsa part:]
alias char-major-116 snd
# post-install sound-slot-0 /sbin/modprobe --ignore-install sound-slot-0 && /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :
# pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S /dev/null 2>&1 || :
alias sound-slot-0 snd-intel8x0
install sound-slot-0 /sbin/modprobe --ignore-install sound-slot-0 && /bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :
Current /etc/rc.d/rc.local
touch /var/lock/subsys/local
modprobe snd-seq-oss
modprobe snd-pcm-oss
modprobe snd_intel8x0
Aumix is zeroed out on every boot but even setting it wide open
doesn't give me anything.
`system-config-soundcard' fails but starts with a warning about
invalid utf-8 junk in something to do with desktop:
(system-config-soundcard.py:2767): Gdk-WARNING **:
DESKTOP_STARTUP_ID contains invalid UTF-8
Going through the rest of the proceedure does nothing usefull.
How can I clean this mess up and start one step at a time with some
chance of debugging my problem?
20 years
kernel 2.6.6-1.377 warnings - unknown symbol
by Götz Reinicke
Hi after a "rpm -ivh kernel-2.6.6-1.377.i686.rpm" I get:
WARNING: /lib/modules/2.6.6-1.377smp/kernel/fs/jffs2/jffs2.ko needs
unknown symbol jffs2_add_physical_node_ref
WARNING: /lib/modules/2.6.6-1.377smp/kernel/fs/jffs2/jffs2.ko needs
unknown symbol jffs2_garbage_collect_pass
WARNING: /lib/modules/2.6.6-1.377smp/kernel/fs/jffs2/jffs2.ko needs
unknown symbol jffs2_flash_direct_writev
WARNING: /lib/modules/2.6.6-1.377smp/kernel/fs/jffs2/jffs2.ko needs
unknown symbol jffs2_reserve_space_gc
WARNING: /lib/modules/2.6.6-1.377smp/kernel/fs/jffs2/jffs2.ko needs
unknown symbol jffs2_erase_pending_trigger
WARNING: /lib/modules/2.6.6-1.377smp/kernel/fs/jffs2/jffs2.ko needs
unknown symbol jffs2_alloc_raw_node_ref
regards götz
--
Götz Reinicke
IT Koordinator - IT OfficeNet
Tel. +49 (0) 7141 - 969 420
Fax +49 (0) 7141 - 969 55 420
goetz.reinicke(a)filmakademie.de
Filmakademie Baden-Württemberg
Mathildenstr. 20
71638 Ludwigsburg
www.filmakademie.de
20 years
FC2 Installation via Telnet Bug
by Janina Sajka
I have more news regarding the bug I reported on this list some weeks ago. I'm sorry, I've tried to put it into Bugzilla, but 2,571 hyperlinks and active fields on one web page exceeds even my capacity. Yes, that's the number lynx reports. So, someone, please help.
Here's the story:
Whether setting a static or using dhcp, attempting to set up installation via telnet breaks at the point a telnet connection is made to the machine where the installation is to be done. Now that I have speech running for the installer, I can report the error that is displayed in Console 3.
There's no /dev/ttyp0 to receive the telnet connection.
So, installing via telnet remains broken.
--
Janina Sajka, Director
Technology Research and Development
Governmental Relations Group
American Foundation for the Blind (AFB)
Chair, Accessibility Workgroup
Free Standards Group (FSG)
Email: janina(a)afb.net Phone: (202) 408-8175
20 years
Fedora Project Mailing Lists reminder
by Elliot Lee
This is a reminder of the mailing lists for the Fedora Project, and
the purpose of each list. You can view this information at
http://fedora.redhat.com/participate/communicate/
When you're using these mailing lists, please take the time to choose
the one that is most appropriate to your post. If you don't know the
right mailing list to use for a question or discussion, please contact
me. This will help you get the best possible answer for your question,
and keep other list subscribers happy!
Mailing Lists
Mailing lists are email addresses which send email to all users
subscribed to the mailing list. Sending an email to a mailing list
reaches all users interested in discussing a specific topic and users
available to help other users with the topic.
The following mailing lists are available. To subscribe, send email to <listname>-request(a)redhat.com
(replace <listname> with the desired mailing list name such as
fedora-list) with the word subscribe in the subject.
fedora-announce-list - Announcements of changes and events. To stay
aware of news, subscribe to this list.
fedora-list - For users of releases. If you want help with a problem
installing or using , this is the list for you.
fedora-test-list - For testers of test releases. If you would like to
discuss experiences using TEST releases, this is the list for you.
fedora-devel-list - For developers, developers, developers. If you are
interested in helping create releases, this is the list for you.
fedora-docs-list - For participants of the docs project
fedora-desktop-list - For discussions about desktop issues such as user
interfaces, artwork, and usability
fedora-config-list - For discussions about the development of
configuration tools
fedora-legacy-announce - For announcements about the Fedora Legacy
Project
fedora-legacy-list - For discussions about the Fedora Legacy Project
fedora-selinux-list - For discussions about the Fedora SELinux Project
fedora-de-list - For discussions about Fedora in the German language
fedora-ja-list - For discussions about Fedora in the Japanese language
fedora-i18n-list - For discussions about the internationalization of
Fedora Core
fedora-trans-list - For discussions about translating the software and
documentation associated with the Fedora Project
German: fedora-trans-de
French: fedora-trans-fr
Spanish: fedora-trans-es
Italian: fedora-trans-it
Brazilian Portuguese: fedora-trans-pt_br
Japanese: fedora-trans-ja
Korean: fedora-trans-ko
Simplified Chinese: fedora-trans-zh_cn
Traditional Chinese: fedora-trans-zh_tw
20 years
Burning ISO to CD
by Leon Stringer
Hi,
This is slightly off topic but I'm having severe problems burning the
FC2 ISOs to CD with FC2t3.
A conservative guess is that 1 in 5 CDs are working OK the rest are
landfill and this is obviously frustrating my move to FC2.
I'm burning with Nautilus' "Write to CD" option (i.e. right clicking on
the ISO file) and I've checked the MD5sum of the ISO beforehand.
I've tried 3 different drives (Samsung SM-332B, SM-352B and an MSI 52x
CD-R drive) and tried Maximum Available and 2x speed and both fail. (I'm
checking the md5sum of /dev/cdrom and this comes up with the wrong
number and an error message)
The media are Sony 700MB CD-Rs. The platform is Intel 845GERG2 board
with a P4 CPU.
So: am I doing anything wrong? Should Nautilus be able to write
reliably? Are my drives or media no good? Is this a known problem in
FC2t3? Will I ever be able to install FC2?!
I'm very grateful for any pointers in troubleshooting this,
Leon...
20 years
