Building ATI drive for 2.6.x
by Gavin Graham
Why is it that everytime I try to build the ATI driver for kernel 2.6.x
I get the following from the driver build script:
ATI module generator V 2.0
==========================
initializing...
Error:
XFree86 drm includes at
/lib/modules/2.6.1-1.138smp/build/include/../drivers/char/drm do not fit
this driver.
This driver is designed to only work with X4.1.0 or higher.
You can match this by getting Linux kernel 2.4.8 or higher.
..The driver are meant to be 2.6.x ready are they not?
--
➧ Gavin Graham ➧ Arkpandora.com
➧ g.graham(a)bigpond.net.au ➧ Annerley, QLD ❖
20 years, 2 months
Fedora Core 1 Test Update: kudzu-1.1.36.1-1
by Bill Nottingham
---------------------------------------------------------------------
Fedora Test Update Notification
FEDORA-2004-067
2004-02-05
---------------------------------------------------------------------
Name : kudzu
Version : 1.1.36.1
Release : 1
Summary : The Red Hat Linux hardware probing tool.
Description :
Kudzu is a hardware probing tool run at system boot time to determine
what hardware has been added or removed from the system.
---------------------------------------------------------------------
Update Information:
This kudzu package fixes a segfault in the network detection code, and some
bugs when configuring network devices.
---------------------------------------------------------------------
* Wed Feb 04 2004 Bill Nottingham <notting(a)redhat.com> 1.1.36.1-1
- fix segfault on CLASS_NETWORK devices with no device set (#106332)
- fix various network device naming snafus (#114611, #113418)
---------------------------------------------------------------------
This update can be downloaded from:
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/1/
c0f7cfa3762c77f06a13b427eeefdc2c SRPMS/kudzu-1.1.36.1-1.src.rpm
93309c70e9a83a79fa1b7e59e1730f7a i386/kudzu-1.1.36.1-1.i386.rpm
818a1c10331ea10458f8989487d19e7d i386/kudzu-devel-1.1.36.1-1.i386.rpm
11dbfdb1ace24f1b2de255b174f533a4 i386/debug/kudzu-debuginfo-1.1.36.1-1.i386.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, 2 months
[Fwd: Re: x86_64 and Radeon 9600]
by Jason Reicheneker
Oops. I'll check the Xfree86 users' mailing list.
-------- Original Message --------
Subject: Re: x86_64 and Radeon 9600
Date: Sat, 07 Feb 2004 11:33:41 -0700
From: Jason Reicheneker <jreichen(a)computer.org>
To: fedora-test-list(a)redhat.com
References: <40244A99.30601(a)computer.org>
<63543.24.86.105.71.1076138536.squirrel(a)www.harddata.com>
I tried to set it to radeon but it froze on the startup splash screen
before it loaded any of the modules.
I couldn't find redhat-config-display.
I have another Linux box that's hooked up to the same monitor, keyboard
and mouse. It has Fedora Core 1 32 bit and was able to recognize them.
So I used the XF86Config from that machine and changed the video driver
to vesa.
How do I find the PCI ID and what do I put in the XF86Config file?
mark(a)harddata.com wrote:
>>I'm trying to install Fedora Core 1 x86_64 and it says it cannot
>>recognize my monitor or video card, even though it outputs to the
>>display. The install switches to text mode and finishes successfully.
>>After rebooting, Linux starts at the command line. I'm not sure how to
>>get it to recognize my hardware and start X. Is anyone else having this
>> problem, what can I do to fix it?
>>
>>Here's my system setup:
>>ASUS K8V Deluxe
>>AMD 64 3200
>>60GB IDE Hard Drive
>>2x 250GB SATA RAID 0
>>1GB DDR400 RAM
>>ATI Radeon 9600SE
>>KDS Visual Sensations 21" monitor
>>USB Mouse
>>PS/2 Keyboard
>>
>>
>
>Well the radeon driver should support 2D with that card but I don't know
>if the PCI ID for the 9600SE is recognized or not. Try setting the driver
>to radeon in your XF86Config. You may be able to do this
>redhat-config-display. You can also use redhat-config-display to set the
>monitor to your specific model. If your monitor isn't a listed model, you
>can enter the ranges for Horizontal and Vertical Refresh Rates found in
>the Monitor Manual or from that models specs online.
>
>If per chance the video still doesn't work even after tell Xfree86 to use
>the radeon driver, you may need to upgrade the driver or place recognized
>PCI ID in your XF86Config file. Information on how to do this should be
>available in the Xfree86 users' mailing list or the DRI users' list.
>
>
>
>
>
20 years, 2 months
No sound under the 2.6.1 test kernels
by Paul F. Johnson
Hi,
My box has two sound cards - a PCI ES1371 and the onboard Intel_810. Due
to it having far better sound quality, I use the ES1371 card.
Under the 2.4.2 kernels, I have no problems with the sound. Under the
2.6.1 kernels, I have no sound whatsoever.
lspci reveals
0000:00:1f.5 Multimedia audio controller : Intel Corp. 82801BA/BAM AC'97
Audio (rev 05)
0000:02:01.0 Multimedia audio control : Ensoniq ES1371 [AudioPCI-97]
lsmod shows the es1371 driver and ac97 codec are both loaded
Any ideas on how to get sound running under the newer kernel without a
recompile?
TTFN
Paul
20 years, 2 months
Some FC 2 Test / rawhide results
by Mark Heslep
I pulled the latest from yesterdays rawhide FC development tree and
ran an install of FC 2 Test (early?). Created a syslinux USB stick
based on the boot.iso image to use as a boot medium Install method was
NFS from a tree w/ kickstart to JFS partitions.
1. 1/2 dozen gnome(ish) package installs ( gdm, evolution, file-roller,
etc ) report a "...parser error: Input is not proper UTF-8...." to the
anaconda /root/install.log but install ok otherwise.
2. Bus device name attribuition caused headaches with conflicts betwenn
the usb storage device and internal SCSI adapter. When the usb stick
is the boot device it takes /dev/sda away from the internal scsi
adapter / disks. [1] The install can be made to go ok but on reboot from
the internal drive is atrributed sda again causing havoc. Passing
"nousbstorage" to anaconda clears the way of course for the internal
SCSI but makes the usb stick unusable for any further use during the
installation. I thought filesystem LABELs were invented to avoid this
kind of problem but they dont help either: the kernel can't find
'init' on root and panics. Had to fall back to rescue mode and mangle
/etc/fstab back to /dev/sda.
3. Graphical install fails on the attempt to start the X server on this
ATI FireGL X1 card connected to a DVI LCD and a VGA LCD. The failure
locks everything up completely. This appears to be the same radeon
problem reported on FC 1 installs.
4. The often reported Gnome process-hang-after-log-outs continue to
leave several processes running after X goes down, usually nautilus and
bonobo.
5. Unsupported category: jfs based installation crashes Anaconda due
to a bad path to jfs_tune. bug# 115101. Kick start %pre sym link
provies a work around for now.
-Mark
[1] I vaguely recall that a post to lkml on scsi name attribution said
a recent 2.6 patch solves this problem.
20 years, 2 months
Compiling gnome 2.5.3
by Paul F. Johnson
Hi,
I'm 99% certain that there is something rather amiss with the rawhide
rpms of the gnome 2.5.3 branch. I say that as when I used the rawhide
versions, a normally very stable machine became unstable in places. When
I compiled them myself (so I could get Evolution to work), things became
more stable again.
It could just be me though.
I've now downloaded the entire source tree for the 2.5.3 branch (the
Gnome website says 2.5.4 should have been out a few days back). Is there
any particular order in which I need to compile the sources or can I
start at a and go through to z. I imagine it would be a good idea to
compile the lib* directories first.
TTFN
Paul
--
Free your mind to a time where a company does not have control
Free your mind to a choice of applications which you can control
Free your mind from the closed world of those who seek total power
Free your mind to the wonderful world of free software
20 years, 2 months
Fedora core development <W00t>
by Norman Madden
I downloaded the core 2 beta last night.
I burned the boot.iso to a mini cd and did the ftp install off: mirror.
hiwaay.net
from directory:
redhat/fedora/linux/core/development/i386
Success!
My Epson Perfection 1670 USB Scanner now works under Fedora core 1.90
via Xsane 0.92
Hats off to all Xsane and Fedora developers <g>
20 years, 2 months
JVM for amd64 RC1?
by Barry Roberts
I nuked the included SuSE 8.1/United 1.0 that came on my appro box to
try Fedora RC1 because I couldn't get a usable jdk/jvm to run tomcat
on. The only improvement so far with Fedora is that I get better
error messages (I think).
I tried the blackdown rc1 for amd64 and after a few seconds of running
my app, I get the attached error. On SuSE, the jvm process just
silently exits in roughly the same amount of time.
I can't seem to install a 32-bit jdk because I keep getting errors
like the following from the self-extracting executables:
/root/j2sdk-1_4_2_03-linux-i586.bin: ./install.sfx.16985: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
Is there a decent jdk for Fedora RC1 amd64? Or is there a way to make
one of the ones I've already tried actually work?
Thanks,
Barry Roberts
20 years, 3 months
I'm gaim
by Leonard den Ottolander
Hi,
http://gaim.sourceforge.net/gaim-0.75.patch
Everybody being so tide up in testing "security enhanced" linux serious
vulnerabilties lay around unaddressed for weeks. What's up?
I won't repeat my complaints about mc as I know Jakub is away and a
patched version can at least be found in testing, but this gaim issue
has been around for 2 weeks and has not been addressed yet.
I had hoped Fedora would continue the good track record Red Hat has had
for years considering releasing security related patches, but I the last
few weeks I feel somewhat disappointed.
Bye,
Leonard.
--
mount -t life -o ro /dev/dna /genetic/research
20 years, 3 months