Dell D610 F8 boot message
by Mike C
After needing the workaround in
http://marc.info/?l=fedora-list&m=119462933124885&w=2
I have got the install to complete, including firstboot.
However during the subsequent boot I see on the screen and in
/var/log/messages the entries
Nov 9 17:37:27 localhost kernel: Uhhuh. NMI received for unknown reason a1 on C
PU 0.
Nov 9 17:37:27 localhost kernel: You have some hardware problem, likely on the
PCI bus.
Nov 9 17:37:27 localhost kernel: Dazed and confused, but trying to continue
When I get to the completed f8 running system then I will add to the
smolt entry suggested by Rahul in the above link/thread.
In the meantime does anyone know what the likely cause of the kernel
message above is?
Also whether this is cause for concern, and what workaround is possible?
The workaround needed to get the install to run was not added to the
grub entries by default - should it be?
Also I was not asked during firstboot to check sound - and it seems no
sound is working at present. Has anyone else had this?
--
mike cohler
16 years, 7 months
RE: VMware install on F7 -- Solved
by McGuffey, David C.
>
> > I'm a bit dismayed that VMware is not playing a more active role in
> > making the scripts necessary to get their product to run on Fedora.
> > Afterall Fedora eventually rolls over into a Red Hat server
offering.
> >
> The issue is more the rate at which Fedora changes the kernel, the
> Vmware installation process requires (as you discvered) a build
> against the kernel sources. Vmware make their code work with the
> latest kernels being used in various distributions at the time the
> Vmware release is done.
>
> Some distributions keep the same kernel throughout their life (e.g.
> typically server/commercial distributions) for just this reason,
> things like Vmware are supported only against certain kernel versions.
>
> Other distributions (like Fedora) stay on the 'bleeding edge' and
> update the kernel frequently, Vmware releases don't keep up with these
> changes.
>
> If you want a 'safe' place to be for sensitive software to run you
> want to use a more stable distribution than Fedora.
>
I agree...I was just sniveling a bit.
Dave McGuffey
Principal Information System Security Engineer // NSA-IEM, NSA-IAM SAIC,
IISBU, Columbia, MD
16 years, 7 months
F8 on PS3
by Vassilios Kotoulas
Hi
I'm just curious. Is there a special version for the PS3 or should I
take the PPC version? Is the Cell CPU supported? How much performance
can I expect? Will it constantly swap?
Regards
Vassilios
16 years, 7 months
Fedora 8 x86_64: "You have specified an install method which isn't supported by anaconda"
by Steve Hill
I'm trying to upgrade my 64 bit F7 install on a Core 2 Duo notebook.
>From power-up I put the F8 x86_64 DVD in the drive, the bootloader appears
and I select "Install or upgrade an existing system". The kernel boots,
asks me if I want to verify the installation media. After that, X starts
up and I immediately get a box pop up which says "You have specified an
install method which isn't supported by anaconda".
Pressing the Ok button just results in the system shutting down.
I am now upgrading from text mode, which seems to be working. A quick
scan of the mailing list seems to suggest no one else has seen this
problem, but I can't think why it would just affect me since the error
message appears as soon as anaconda starts, before it asks for the user
to make any choices.
- Steve
xmpp:steve@nexusuk.org sip:steve@nexusuk.org http://www.nexusuk.org/
Servatis a periculum, servatis a maleficum - Whisper, Evanescence
16 years, 7 months
F8 freshrpms
by Antonio M
When I try to install gstreamer-plugins-bad - 0.10.5-1.fc8.i386 I get:
13:47:22 : Errore controllo transazione: file
/usr/lib/gstreamer-0.10/libgstladspa.so from install of
gstreamer-plugins-bad-0.10.5-1.fc8 conflicts with file from package
gstreamer-plugins-good-0.10.6-6.fc8
any help???
--
Antonio Montagnani
Skype : antoniomontag
16 years, 7 months
RE: fedora-list Digest, Vol 45, Issue 77
by McGuffey, David C.
>
> > I'm a bit dismayed that VMware is not playing a more active role in
> > making the scripts necessary to get their product to run on Fedora.
> > Afterall Fedora eventually rolls over into a Red Hat server
offering.
> >
> The issue is more the rate at which Fedora changes the kernel, the
> Vmware installation process requires (as you discvered) a build
> against the kernel sources. Vmware make their code work with the
> latest kernels being used in various distributions at the time the
> Vmware release is done.
>
> Some distributions keep the same kernel throughout their life (e.g.
> typically server/commercial distributions) for just this reason,
> things like Vmware are supported only against certain kernel versions.
>
> Other distributions (like Fedora) stay on the 'bleeding edge' and
> update the kernel frequently, Vmware releases don't keep up with these
> changes.
>
> If you want a 'safe' place to be for sensitive software to run you
> want to use a more stable distribution than Fedora.
>
I agree...I was just sniveling a bit.
Dave McGuffey
Principal Information System Security Engineer // NSA-IEM, NSA-IAM
SAIC, IISBU, Columbia, MD
16 years, 7 months
FC6 .22-9 kernel and qla2xxx driver
by Mark Haney
I just rebooted one of my SAN hosts, running FC6, and had it boot into
the latest FC6 kernel 2.6.22-9. After the boot, the primary SAN
partitions it mounts weren't available. A check through
/var/log/messages revealed this little nugget:
Nov 9 10:01:04 blowingrock kernel: QLogic Fibre Channel HBA Driver
Nov 9 10:01:04 blowingrock kernel: e1000: eth0: e1000_probe: Intel(R)
PRO/1000 Network Connection
Nov 9 10:01:04 blowingrock kernel: ACPI: PCI Interrupt 0000:01:01.0[A]
-> GSI 28 (level, low) -> IRQ 28
Nov 9 10:01:04 blowingrock kernel: qla2xxx 0000:01:01.0: Found an
ISP2300, irq 28, iobase 0xffffc20001438000
Nov 9 10:01:04 blowingrock kernel: qla2xxx 0000:01:01.0: Configuring
PCI space...
Nov 9 10:01:04 blowingrock kernel: qla2xxx 0000:01:01.0: Configure
NVRAM parameters...
Nov 9 10:01:04 blowingrock kernel: qla2xxx 0000:01:01.0: Verifying
loaded RISC code...
Nov 9 10:01:04 blowingrock kernel: ACPI: PCI Interrupt 0000:02:04.1[B]
-> GSI 26 (level, low) -> IRQ 26
Nov 9 10:01:04 blowingrock kernel: e1000: 0000:02:04.1: e1000_probe:
(PCI:33MHz:64-bit) 00:04:23:a8:96:d7
Nov 9 10:01:04 blowingrock kernel: Floppy drive(s): fd0 is 1.44M
Nov 9 10:01:04 blowingrock kernel: FDC 0 is a post-1991 82077
Nov 9 10:01:04 blowingrock kernel: e1000: eth1: e1000_probe: Intel(R)
PRO/1000 Network Connection
Nov 9 10:01:04 blowingrock kernel: qla2xxx 0000:01:01.0: Firmware image
unavailable.
Nov 9 10:01:04 blowingrock kernel: qla2xxx 0000:01:01.0: Firmware
images can be retrieved from: ftp://ftp.qlogic.com/outgoing/linux/firmware/.
Nov 9 10:01:04 blowingrock kernel: qla2xxx 0000:01:01.0: Failed to
initialize adapter
So, in my panic, I reset grub to point back to the existing .20 kernel
and all came up just fine:
Nov 9 10:31:06 blowingrock kernel: qla2xxx 0000:01:01.0: Found an
ISP2300, irq 28, iobase 0xffffc20000022000
Nov 9 10:31:06 blowingrock kernel: qla2xxx 0000:01:01.0: Configuring
PCI space...
Nov 9 10:31:06 blowingrock kernel: qla2xxx 0000:01:01.0: Configure
NVRAM parameters...
Nov 9 10:31:06 blowingrock kernel: qla2xxx 0000:01:01.0: Verifying
loaded RISC code...
Nov 9 10:31:06 blowingrock kernel: Intel(R) PRO/1000 Network Driver -
version 7.3.15-k2-NAPI
Nov 9 10:31:06 blowingrock kernel: Copyright (c) 1999-2006 Intel
Corporation.
Nov 9 10:31:06 blowingrock kernel: input: PC Speaker as /class/input/input3
Nov 9 10:31:06 blowingrock kernel: qla2xxx 0000:01:01.0: Allocated (412
KB) for firmware dump...
Nov 9 10:31:06 blowingrock kernel: scsi2 : qla2xxx
Nov 9 10:31:06 blowingrock kernel: hdc: ATAPI 52X CD-ROM drive, 128kB
Cache, UDMA(33)
Nov 9 10:31:06 blowingrock kernel: Uniform CD-ROM driver Revision: 3.20
Nov 9 10:31:06 blowingrock kernel: Floppy drive(s): fd0 is 1.44M
Nov 9 10:31:06 blowingrock kernel: FDC 0 is a post-1991 82077
Nov 9 10:31:06 blowingrock kernel: qla2xxx 0000:01:01.0: LOOP UP
detected (2 Gbps).
So my question, WTH is going on here? I've obviously missed a memo or
something.
--
Recedite, plebes! Gero rem imperialem!
Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
Call (866) ERC-7110 for after hours support
16 years, 7 months
Yum update problem with %preun
by lluis
I am trying to the yum update command using a spec file with pre,post
and %preun
Yum does not correctly update my package:
It starts with the %pre then %post of the new package version, and after
that do the %preun of the old package version!
At the end the package is not correctly installed because of %preun
commands (unlinks, etc )
Does Somebody experienced this problem ?
What's wrong in my package ?
Thank.
16 years, 7 months
can't subscribe to F8 package announcements
by Andre Robatino
The config page for the fedora-package-announce list doesn't have a F8
choice, though there are choices for FC3 through F7, and FC3, FC4, and
FC5 are no longer supported and presumably not getting any more
announcements. The list archive already has batches of F8 announcements
for Nov. 6 and Nov. 8.
16 years, 7 months
