After the last update from testing, rpmbuild broke. rpm-4.2.2-0.7.
python-2.3.3-1. I've tried going backwards with a few packages, and nothing
seems to make a difference. Don't know enough about rpm to do much
Through -bi is okay. With -ba, on very rare occasions finishes,
sometimes hangs, usually segfaults. It appears to be having problems with
the debug info. I don't know how to turn off debuginfo processing, which is
where I suspect the problem is.
I suspect this, because the debuginfo isn't always produced in the
installation tree, and one rpmbuild run hangs on:
Processing files: hp2pbm-debuginfo-0.1-3
I don't know where to go from here to deal with this, so I'm reporting
it in the hopes it will make sense to someone who does know.
look at this file from the installation of the linksys EG1032 Gigabit Nic
[root@matrix DriverInstall]# ./install.sh
Installation script for sk98lin driver.
Version 1.03 (20030319)
(C)Copyright 1999-2003 Marvell(R).
Add to your trouble-report the logfile install.log
which is located in the DriverInstall directory.
Choose your favorite installation method: 2
Check user id (0) passed
Check host type (done) passed
Check compiler (/usr/bin/gcc) passed
Check module support (/sbin/insmod) passed
Check make (/usr/bin/make) passed
Check archive file (sk98lin) passed
Check kernel version (2.6.0-1.104) failed
Kernel version unsupported.
This driver was developed for the kernel family 2.4.x
higher then 2.4.13. If you are still using a old version
of the kernel, please uptade to the newest version from
Installation of sk98lin driver module failed.
>From: Karen Spearel <kas11(a)tampabay.rr.com>
>Subject: Re: Instant Gigahertz NIC Linksys EG1032
>Date: Sat, 27 Dec 2003 13:00:25 -0500
>Alton Bailey wrote:
> > I'm currently upgrading my network to Gigabit data transfer, I install
> > linksys EG1032 ) on my Fedora box and use the installation from the cd
> > comes with the Nic Card and i got an error during the setup. I am using
> > Kernel 188.8.131.52.104 and also the original 184.108.40.206.2115 up to 2135
> > when I try to setup the NIC with Kernel 220.127.116.11.104 this NIC is not
> > supported.
> > and for kernel 18.104.22.168.2115 up to 2135 I got an error too and I
> > attachment.
> > could some one look into this problem
>The Linksys vendor ID and a device ID of 0x1032 show up in the
>SysKonnect 98 source...googling elsewhere indicates that the Natsemi
>83821 chip used on at least 1 rev of that card is based on the Marvell
>Yukon design which this driver does support...so it seems probable that
>the sk98lin driver included in FC1 ought to work. Give it a shot and
>let us know.
>fedora-test-list mailing list
Alton Bailey wrote:
> I'm currently upgrading my network to Gigabit data transfer, I install (
> linksys EG1032 ) on my Fedora box and use the installation from the cd that
> comes with the Nic Card and i got an error during the setup. I am using
> Kernel 22.214.171.124.104 and also the original 126.96.36.199.2115 up to 2135
> when I try to setup the NIC with Kernel 188.8.131.52.104 this NIC is not
> and for kernel 184.108.40.206.2115 up to 2135 I got an error too and I include an
> could some one look into this problem
The Linksys vendor ID and a device ID of 0x1032 show up in the
SysKonnect 98 source...googling elsewhere indicates that the Natsemi
83821 chip used on at least 1 rev of that card is based on the Marvell
Yukon design which this driver does support...so it seems probable that
the sk98lin driver included in FC1 ought to work. Give it a shot and
let us know.
I'm currently upgrading my network to Gigabit data transfer, I install (
linksys EG1032 ) on my Fedora box and use the installation from the cd that
comes with the Nic Card and i got an error during the setup. I am using
Kernel 220.127.116.11.104 and also the original 18.104.22.168.2115 up to 2135
when I try to setup the NIC with Kernel 22.214.171.124.104 this NIC is not
and for kernel 126.96.36.199.2115 up to 2135 I got an error too and I include an
could some one look into this problem
I have been trying out the new 2.6 kernel and Alsa as I have a Edirol
SD-20 USB sound module that was a pain under the OSS system. While all
is great, there is this one problem:
I have two sound cards, one is the Edirol USB sound module and the other
is a stock SB-Audigy. During system init, all USB drivers get load
before the standard sound drivers which means that my Edirol sound
module becomes sound-card-0. Then along come the standard sound module
load which make the SB-Audigy become sound-card-1.
The problem with this is that the Edriol module is midi only and has no
PCM/Wave capability. This make play normal audio very difficult. ..Not
to mention just running the volume applet!!!
My fix to date has been to unload both modules and then reload them in
the correct order of SB then Edirol.
It think some re-ordering is involved here but I am unsure how to best
➧ Gavin Graham ➧ Arkpandora.com
➧ g.graham(a)bigpond.net.au ➧ Annerley, QLD ❖
MozcurveBlue & Arkpandora fonts:
On Tue, 2003-12-23 at 05:59, jason pearl wrote:
> On Mon, 2003-12-22 at 22:44, Philip Wyett wrote:
> > On Tue, 2003-12-23 at 02:31, Michal Zeravik wrote:
> > > Hi to all,
> > >
> > > I've tried to install %subj% on FC1 but X server fails on same
> > > either with CC=gcc32 (for old-good 44.96).
> > > Do you have any expoerience how to successfuly install 53.28?
> > >
> > > michalz
> > >
> > Before installing the nvidia drivers 4496 or the latest 5328 you
> > first remove XFree86-Mesa-libGL to avoid conflicts. After this
> > CC=gcc32' then do the nvidia install as normal and all should be
> > Regards
> > Philip Wyett
> I just did the nvidia install 5328 and had no problems so far i did
> init 3.. installed the drivers and edited the x86 config file. then
> 5 and it went ok and shown an nvidia splash screen.. so you think i
> be ok/? i am scared to rebooot my kernel in fear of a crash hehe
re-send as the reply seems to have got stripped and mashed on it's way.
You have the driver installed and thats Ok - Don't worry about reboots
etc.! :) The need for removing the Mesa GL package is due to a file
conflict which leads to GL related issues. The easiest way to see the
problem is to fire up glxgears and then exit and try and fire it up
again and watch the blank viewport. :( Removing the Mesa GL package
prior to installing/re-installing the nvidia drivers removes the chance
of this problem happening.
Public key: http://www.wyett.net/gpg/public_key.txt
OK, I got my amd64 hardware ... actually an Opteron 140 but am having some
After much hassle I got an ASUS SK8V MB. I first ordered a Gigabyte
K8NNXP-940 (looked pretty good and I had good luck with another Gigabyte MB
for dual athlons). This proved to an advertised and not really available
product so I switch the order to an ASUS SK8N. When I went to pick it up, I
was told that the RUMOR (NOTE, this is RUMOR, not FACT) that the SK8N had
been recalled and if I wanted, they had an SK8V I could have. Now, this
seemed better because the VIA chipset does not apparently have the acpi
problem so I got it.
The video adapter is an ATI 9100 and (as expected from other comments) the
onboard NIC did not work so I added a Linksys (tulip) NIC. The system has
1GB ECC Reg ram.
I installed i386 FC1 with no (well, see below) problems so this is hardware
that FC1 should handle.
Problem 1 (I do not really expect help here but who knows):
I have a Dell 2000FP (analog) monitor which is connected to a total of four
systems via a Belkin KVM switch. I have had zero problems with this setup
(runs 1600x1200 just fine) on my other systems (dual P-III, single P-III and
When I poweron the Opteron the screen blinks a couple of times, some text
comes up for some IDE/raid controllers but then I get a blank screen with the
Dell saying it is in power-save mode. I finally dug out an old NEC XV17+ and
connected it directly. OK, it comes up and I was finally able the get into
BIOS Setup via the DEL key. I turned off some fancy ASUS/AMI graphic boot
stuff and otherwise configured the BIOS to be more friendly ... this resulted
in being able to at least bootup on the Dell but still unable to get into
BIOS Setup this way (or at least get it to display). On the Dell this BIOS
Setup image flashes but then the monitor goes into power-save mode. Once I
get to with the FC1 i386 cdrom prompt or (after install) the grub panel, the
display works fine.
OK, the conclusion I have come to is that the ASUS/AMI BIOS is using some
video adapter parameters which drives the Dell monitor nuts and forces it
into "off" mode.
I can't get this system to boot the floppy (it does boot the Maxtor harddrive
and the cdrom (DVD drive) but not the floppy) -- I am not sure the floppy
drive is even seen. This means that I cannot update the BIOS although there
is an update available.
I have not yet tried attaching the Dell monitor directly or to use the DVI
interface (both the 9100 adapter and the Dell monitor have a DVI interface in
addition to an analog interface). However, I do not expect this to work any
better since it seems (to me) to be video parameters that the ASUS/AMI BIOS
As I said, I don't expect help here but any would be appreciated.
Problem 2 (installing FC1 X86_64):
I downloaded all of the files from fedora.linux.duke.edu, burned a cdrom using
images/boot.iso, and made the directory tree available via an NFS share. The
nfs shared fc1 directory tree has both i386 and x86_64 subtrees and I
successfully installed fc1-i386 off the i386 tree.
When I boot the x86_64 boot.iso cdrom it comes up. I enter the appropriate
system name and directory tree but then get "unable to mount" popup and am
unable to get any further. As I said, I used this same process to install
i386 FC1 and have checked the permission and they are OK.
Another strange thing is that I cannot switch to VT2 (ctl-alt-F2) although I
can switch to VT3 and VT4 ... maybe I am not far along enough for VT2 to
Any help appreciated.
Just wondering if anyone has had success installing Fedora on a system
with a motherboard that utilizes a Promise FastTrak100 Lite chip? The
does not seem to recognize it, or any of the disks attached to it. This
is a Soyo Dragon Plus, but I suspect that any mobo with this chip exhibits
the same behavior.
OK, I need to make x86_64 cdroms (I believe that my Linksys (tulip) NIC is not
recognized in 64 bit mode). I read the x86_64 FC1 faq and it says I should
run /usr/lib/anaconda-runtime/splittree ... OK, but how? Can enyone provide
a few more hints as to how to do this? I can see that I need to run pkgorder
but have no clue as to what it expects?
I am not well versed in python and don't want to spend the time to learn it
just so I can get the tree split and cdroms built.
If it comes down to it I suppose I can manually split the tree but I am hoping
there is a quicker way.