Fedora 12: Cannot boot with kernel-2.6.32.9-67.fc12.x86_64
by Steven P. Ulrick
Hello Everyone
The good news is that in my 10+ years using Linux, I am almost certain that
I have never had a kernel that would not boot...
Last night I ran "yum update" and it pulled in
kernel-2.6.32.9-67.fc12.x86_64. When I attempted to boot it, the boot
process seemed to complete, but X never started.
Since I have never had this problem before, I don't know precisely what
information that you need.
I am running an NVidia video card, with the proprietary NVidia driver,
installed from RPMFusion. After failing to boot
kernel-2.6.32.9-67.fc12.x86_64, I can reboot and choose another kernel and
it boots just fine.
From /var/log/messages, this is the closest that I can find to anything
relevant:
Mar 8 03:01:56 localhost kernel: DRHD: handling fault status reg 102
Mar 8 03:01:56 localhost kernel: DMAR:[DMA Read] Request device [03:00.0]
fault addr 233038000
Mar 8 03:01:56 localhost kernel: DMAR:[fault reason 01] Present bit in
root entry is clear
Mar 8 03:01:56 localhost kernel: NVRM: Xid (0003:00): 54, CMDre 00000000
00000000 00000000 00000001 00000001
Mar 8 03:01:56 localhost kernel: DRHD: handling fault status reg 202
Mar 8 03:01:56 localhost kernel: DMAR:[DMA Read] Request device [03:00.0]
fault addr 235833000
Mar 8 03:01:56 localhost kernel: DMAR:[fault reason 01] Present bit in
root entry is clear
Mar 8 03:01:56 localhost kernel: NVRM: Xid (0003:00): 6, PE007e
Mar 8 03:01:56 localhost kernel: DRHD: handling fault status reg 302
Mar 8 03:01:56 localhost kernel: NVRM: Xid (0003:00): 6, PE007e
Again, I can boot fine from every other kernel. I just can't boot from
2.6.32.
If all I need to do is try running without the proprietary NVidia driver,
please let me know specifically how to disable that driver the easiest
possible way. Translation: so that I can just boot back into an older
kernel and continue using the proprietary NVidia driver if I decide to do
that.
Also, not only have I never had a problem with being able to boot a
particular kernel, I have never had any problems with the proprietary
NVidia driver.
Let me know any additional information that you may need to help me with
this issue.
Steven P. Ulrick
14 years, 3 months
Yunm /theora problem -
by Bob Goodwin
Today's yum update choked on ffmpeg2theora.
Transaction Check Error:
file /usr/share/man/man1/ffmpeg2theora.1.gz from install of
ffmpeg2theora-0.26-1.fc12.x86_64 conflicts with file from package
ffmpeg2theora-0.25-1.fc12.i686
Error Summary
-------------
I'm not sure why I have the i386 version and not the x86_64 version
but perhaps it came with one of the video applications I downloaded?
I guess I can try removing the i386 stuff and see if it will then
permit me to install the x86_64 version and then see if some other
app. dies. I have been working with some video cameras and may have
inadvertently caused this problem.
I guess what I want to know is if others have a problem with this
update or is it just me?
Bob
--
14 years, 3 months
fc12 create initramfs contaning twofish kernel module
by Jeffrey Kelling
Hello,
I just installed fc12 on an existing Twofish-encrypted LVM containing /home
and / as logical volumes. The installation went well, but the system won't
start because the initramfs misses module 'twofish-common'.
How can I add the missing module to the initramfs? I was not able to find a
working HowTo for dracut. Issuing
> dracut /boot/myinit
from the live-CD in a chroot to the system on disc did produce an initramfs
containing an empty directory tree.
Furthermore, I was not able to find any further options when creating an
encrypted filesystem in anaconda, did I miss something there?
Thanks in advance.
Regards,
Jeffrey
14 years, 3 months
After installation, booting FC-12.
by ZL
Hello
List,
The installation of FC-12 went very smoothly. I removed all external devices and unnecessary seated cards, to do the install. Then, the reboot screen appeared. I clicked on the reboot button, and the computer rebooted. During the reboot procedure, the yaboot (the apple macintosh boot loader) screen appeared. The following options were presented:
l linux
x macosx
o openfirmware
n network
c cdrom
I entered an l, at the boot prompt, and the booting procedure continued to boot linux.
During the boot process, an Oops! machine check 7... occurred. Followed by a trace and other information. The machine check, Oops, appears to revolve around ochi1394, or firewire. Incedently, the computer's 2 external firewire ports, and the internal firewire port are no longer working.
With FC-11, this very same machine check, Oops, occurred. Also, after loading all necessary linux software components, the login screen would appear. After logging into FC-11's gnome or KDE desktop, a kernel report (which was probably related to the Oops!) would be automatically generated and sent to whomever.
In this version of linux, FC-12, the boot procedure stops loading after eth1 (apple wireless base station check), and simply stands still.
What changed in the boot load process? Were additional stringent modules, components, checks, or procedures added?
The boot process does not allow the welcome screen to appear.
What is the possible solution? I would like to know.
Thank you
Linux user
14 years, 3 months
After installation, booting FC-12.
by ZL
Hello
List,
The installation of FC-12 went very smoothly. I removed all external devices and unnecessary seated cards, to do the install. Then, the reboot screen appeared. I clicked on the reboot button, and the computer rebooted. During the reboot procedure, the yaboot (the apple macintosh boot loader) screen appeared. The following options were presented:
l linux
x macosx
o openfirmware
n network
c cdrom
I entered an l, at the boot prompt, and the booting procedure continued to boot linux.
During the boot process, an Oops! machine check 7... occurred. Followed by a trace and other information. The machine check, Oops, appears to revolve around ochi1394, or firewire. Incedently, the computer's 2 external firewire ports, and the internal firewire port are no longer working.
With FC-11, this very same machine check, Oops, occurred. Also, after loading all necessary linux software components, the login screen would appear. After logging into FC-11's gnome or KDE desktop, a kernel report (which was probably related to the Oops!) would be automatically generated and sent to whomever.
In this version of linux, FC-12, the boot procedure stops loading after eth1 (apple wireless base station check), and simply stands still.
What changed in the boot load process? Were additional stringent modules, components, checks, or procedures added?
The boot process does not allow the welcome screen to appear.
What is the possible solution? I would like to know.
Thank you
Linux user
14 years, 3 months
icons vs. messages in gpk-update-viewer??
by Beartooth
The last couple batches of updates have shown lots of apps with
the little round gray power button icon, like the one you click to shut
down, reboot, etc. And the initial box interprets it as meaning restart
(which seems generally to be spreading as a substitute for reboot).
But the message in the box after the update finishes says to log
out and back in.
Has there been a great change? Or has the message somehow gotten
bonkered?
--
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
I have precious (very precious!) little idea where up is.
14 years, 3 months
flash on www.nbc.com
by Michael Hennebry
Is there some trick to getting flash to work through firefox?
When I click on a Chuck episode,
the peacock shows up and wiggles its tail, but that is all that happens.
Zoom in works.
I've running FC 11.
About tells me that I'm running Adobe Flash Player 10,0,45,2 .
I can play flash on some sites.
On others, I can download and use mplayer.
On www.nbc.com, neither.
--
Michael hennebry(a)web.cs.ndsu.NoDak.edu
"Pessimist: The glass is half empty.
Optimist: The glass is half full.
Engineer: The glass is twice as big as it needs to be."
14 years, 3 months
Vanilla kernels and nouveau
by Rares Aioanei
Hi y'all,
I have the habit of compiling kernels from Linus' tree once in a while.
The list of installed kernels on my AA64 Fedora 12 machine looks like so :
[arares@localhost ~]$ ls /boot | grep vmlinuz
vmlinuz
vmlinuz-2.6.31.12-174.2.22.fc12.x86_64
vmlinuz-2.6.31.5-127.fc12.x86_64
vmlinuz-2.6.32.9-67.fc12.x86_64
vmlinuz-2.6.33-00001-gbaac35c
vmlinuz-2.6.33-05070-g64ba992
vmlinuz-2.6.33-05679-g4da0b66
vmlinuz-2.6.34-rc1-00005-g522dba7
Now, the first vanilla kernel (aka the oldest) works OK with nouveau,
and the Fedora-supplied ones do the same. However, the other vanilla
kernels fail to show me a nice gdm screen, and after some flickering,
leave the following in my logs :
195 (II) [drm] DRM interface version 1.3
196 (II) [drm] DRM open master succeeded.
197 (II) NOUVEAU(0): [drm] nouveau interface version: 0.0.16
198 (EE) NOUVEAU(0): [drm] wrong version, expecting 0.0.15
199 (EE) NOUVEAU(0): 879:
200 (II) UnloadModule: "nouveau"
201 (II) UnloadModule: "dri"
202 (II) UnloadModule: "int10"
203 (II) Unloading /usr/lib64/xorg/modules/libint10.so
204 (EE) Screen(s) found, but none have a usable configuration.
205
206 Fatal server error:
207 no screens found
208
209 Please consult the Fedora Project support
(the line numbers are from my vim, sorry). So, the question is : should
I file this as a bug in kernel's bugzilla or in Fedora's? Thank you.
14 years, 3 months
Proftpd config problem in Fedora 11 ( 64Bit )
by Edward S.P. Leong
Dear All,
Mine is Fedora 11 ( without enable firewall and selinux )....
After install proftp as ftp server, there is error message during upload
file/data to the ftp server as the following :
[root@]# rpm -qa | grep "proftpd"
proftpd-1.3.2d-1.fc11.x86_64
for /etc/proftpd.conf :
ServerType inetd
DefaultServer on
UseReverseDNS off
IdentLookups off
Port 21
Umask 022
MaxInstances 30
MaxClients 50
User nobody
Group nobody
TimeoutIdle 1800
TimeoutStalled 1800
TimeoutNoTransfer 1800
TimeoutLogin 1800
TimesGMT off
AllowRetrieveRestart on
AllowOverwrite on
AllowStoreRestart on
ServerIdent On "FTP Server"
for /etc/xinetd.d/proftpd :
service ftp
{
socket_type = stream
wait = no
user = root
server = /usr/sbin/in.proftpd
# log_on_success += DURATION USERID
# log_on_failure += USERID
log_on_success = EXIT DURATION
log_on_failure = ATTEMPT
nice = 10
disable = no
}
error :
STOR MySQL-client-5.1.44-1.glibc23.x86_64.rpm
150 Opening BINARY mode data connection for
MySQL-client-5.1.44-1.glibc23.x86_64.rpm
Transmitted 7359458 bytes in 155.5 secs, (464.13 Kbps), transfer succeeded
! Receive error: Blocking call cancelled
Thanks!
14 years, 3 months