boot.iso problem?
by G.Wolfe Woodbury
AMD K6-2
ASUS mobo
Verbatim CD-RW
I burn the development boot.iso to a CDRW, successful burn and verify
Boot using the new CDRW (boots with other CDRWs are fine)
No flash of messages or anything other than clearing the console screen,
but the machine gets a reset and the POST starts all over again. :-(
Is this because the boot.iso is corrupt in some way? Other testers
report using boot.iso to do installs of "rawhide", so that shouldn't be
the problem. Is the AMD K6-2 not supported? Any suggestions?
--
Gregory G. "Wolfe" Woodbury `-_-' Owner/Admin: wolves.durham.nc.us
ggw at wolves.durham.nc.us U RHCT August 2003
"The Line Eater is a boojum snark." Hug your wolf.
20 years, 2 months
rawhide test results
by Neal Becker
OK, I tried it here. (Update from FC1 -> mirror.hiwaay.net
development) These are my results:
1) No mouse. uhci was not loaded. I added
alias usb-controller uhci
to modprobe.conf
2) X starts at boot, but is just a black screen. Later, when runlevel 5
starts, X server keeps dying, because the first X never stopped. I have to
killall X, then set back to runlevel 5, then it's OK.
3) Feb 7 09:17:14 localhost kernel: atkbd.c: Unknown key released
(translated set 2, code 0x7a on isa0060/serio0).
Feb 7 09:17:14 localhost kernel: atkbd.c: This is an XFree86 bug. It
shouldn't access hardware directly.
4) Feb 7 09:13:14 localhost httpd: Syntax error on line 10
of /etc/httpd/conf.d/perl.conf:
Feb 7 09:13:14 localhost httpd: Cannot load /etc/httpd/modules/mod_perl.so
into server: libperl.so: cannot open shared object file: No such file or
directory
5) Feb 7 09:13:13 localhost cpuspeed: Error: Could not open file for
writing: /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Feb 7 09:13:13 localhost cpuspeed: Error: No such file or directory
20 years, 2 months
FC1 -> FC2 upgrade and LVM
by Robert P. J. Day
i hate to keep harping on this, but how will a FC1->FC2 upgrade handle a
system that already uses an LVM1-formatted filesystem structure?
IIRC (and i could be totally off-base here), the 2.6 kernel handles LVM2
*only*. so what happens to all those LVM1 partitions?
a more general question might be, is there at least a list of
*theoretical* upgrade issues we have to deal with if we want to try
it?
rday
20 years, 2 months
mount error 19 mounting ext3 - with errata kernels and RAID.
by Mr. Adam ALLEN
I'm having problems with upgrading with errata kernels with Fedora Core
1. 2.4.22-1.2129 installed and boots without any problems, however all
later errata kernels don't work.
I have an ext3 RAID-1 / partition as /dev/md0.
relevant line of /etc/fstab
/dev/md0 / ext3 defaults 1 1
relevant line of grub
title Fedora Core (2.4.22-1.2129.nptl)
root (hd0,0)
kernel /vmlinuz-2.4.22-1.2129.nptl ro root=/dev/md0 hdd=ide-scsi nogui
initrd /initrd-2.4.22-1.2129.nptl.img
The error message is:
mount : error 19 moutning ext3
pivot_root (/sysroot, /sysroot/initrd) failed 2
umount /initrd/proc failed 2
kernel panic - try passing init=
From what I can see the initrd's for the 2129 and 2149 seem identical
and so is the grub config.
Any pointers on how to fix this (or what the problem is)?
--
Regards,
Adam Allen.
adam(a)dynamicinteraction.co.uk
pgp http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x553349DB
20 years, 2 months
OT: mydoom-a
by shrek-m@gmx.de
----
Received: from iki.fi (ad245.neoplus.adsl.tpnet.pl [80.50.149.245])
by mx2.redhat.com (8.11.6/8.11.6) with SMTP id i18DSen12810
for <fedora-test-list(a)redhat.com>; Sun, 8 Feb 2004 08:28:41 -0500
----
hi,
all mydoom-a i get privat or throgh lists
are coming from xxx.neoplus.adsl.tpnet.pl
can you check if this is the case ?
--
shrek-m
20 years, 2 months
Re: Security updates are too slow or none existant
by Andy Green
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 08 February 2004 16:20, William Hooper wrote:
> Red Hat is part of a number of non-public groups that discus and fix
> security issues. Releasing an update into testing before the issue was
> made public would be irresponsible.
Just to amplify this in case anyone is wondering why giving the patch early
can be considered irresponsible, blackhats can and do compare the binaries
issued by, for example, Microsoft, to find out what was patched. Armed with
this knowledge they can create attacks on the unpatched machines.
Here is a partial quote form a post to Full Disclosure yesterday, for example
(courtesy of deleon(a)hushmail.com, full post at
http://lists.netsys.com/pipermail/full-disclosure/2004-February/016878.html) :
''...I discover it was a heap overflow and I even found how. The problem
is h323asn1.dll which ms004-04 patch, and microsoft tried to make this
hard to find by changing lost of fake things, but we have no problem
seeing the True Patch. Old function is sub_40fa6d, new is sub_40f627,
and patch checks a word to see that it is short enough. This word is
actually length of a string that follows (use ethereal to understand
packet) and it can be any length but a few kb is enough to overflow...''
Sort of like Neo being able to see the ebb and flow of information in the
Matrix, some guys spent so long in IDA that the binary is not so far from the
source for them....
- -Andy
- --
Find your answer without waiting for replies....
Searchable list archives at
http://marc.theaimsgroup.com/?l=fedora-list&r=1&w=2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAJnGijKeDCxMJCTIRAlrbAJ9bm3lmO9pFhvIw5f0HAQx2WAkEcwCggREk
EPPNGtN05sZjMJpoIU+VCrw=
=SkbW
-----END PGP SIGNATURE-----
20 years, 2 months
gdm problem with the new 2.6.1-1.65 kernel
by Paul F. Johnson
Hi,
Anyone know the cause of this problem. Under the 2.4.2-2149 kernel, I
have no problems logging in. When I try with the 2.6.1-1.65 kernel, all
I get are the following errors. Is there a fix and shouldn't we be
playing with the 2.6.2 kernel instead now?
/etc/X11/gdm/PreSession/Default: Registering your session with wtmp and
utmp
/etc/X11/gdm/PreSession/Default: running: /usr/bin/X11/sessreg -a -w /
var/log/wtmp -u /var/run/utmp -x "/var/gdm/:0.Xservers" -h "" -l ":0"
"paul"
SELinux gdm login : unable to obtain default security context for paul.
I'm running test1 (FC 1.90). Everything is up to date.
TTFN
Paul
20 years, 2 months
Soundcard VIA ac97 doesn't work
by Thiago Vinhas de Moraes
Hi all!
When I try to run /usr/bin/system-config-soundcard to configure my
soundcard on Fedora Core 1 with the latest kernel 2.6.1 from rawhide, I
get the following error:
The via82cxxx_audio driver could not be loaded. This soundcard may not
be compatible with Red Hat Linux.
I tried updating the system-config-soundcard package for the latest from
rawhide, but got the same error. How to put my sound working on Fedora 1
with kernel 2.6?
Regards,
Thiago
20 years, 2 months
Firstboot problem
by G.Wolfe Woodbury
When I boot my AMD K6-2 development testbed machine, firstboot fails
with the following:
Module Loader present
OS Kernel: Linux version 2.6.1-1.65custom (root(a)tembo.private) (gcc
version 3.3.2 20040119 (Red Hat Linux 3.3.2-8)) #1 Fri Feb 6 14:32:55
EST 2004
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.1.log", Time: Sat Feb 7 14:54:20 2004
(==) Using config file: "/etc/X11/XF86Config"
.Traceback (most recent call last):
File "/usr/share/firstboot/firstboot.py", line 207, in ?
import firstbootWindow
File "/usr/share/firstboot/firstbootWindow.py", line 28, in ?
import gtk
File
"/usr/src/build/322659-i386/install/usr/lib/python2.3/site-packages/gtk-2.0/gtk/__init__.py",
line 43, in ?
RuntimeError: could not open display
[root@tembo root]# Window manager error: Unable to open X display :1
The system recovers from the bomb and continues on. Running from the
command line yeilds the same results. The X-server doesn't fail, the
root window and X cursor appear briefly and then the firstboot messages
flash by and a boot.log message simply states that firstboot: failed.
I do not know if the X server is coming up as the proper screen or on
the proper virtual terminal.
--
Gregory G. "Wolfe" Woodbury `-_-' Owner/Admin: wolves.durham.nc.us
ggw at wolves.durham.nc.us U RHCT August 2003
"The Line Eater is a boojum snark." Hug your wolf.
20 years, 2 months