02-24-2012
@Corona688: Thanks for the input.
I find a temporary solution on my problem which is to reinstalled the driver which i downloaded from the AMD source site every time a new kernel is released or the kernel you want to used permanently/current.
I understand the problem by installing the driver one by one on my kernel. If i installed the driver to the current kernel and boot to the old one the problem occurs but not the new one, In comparison if i installed driver in the old kernel the new one will suffer the problem not the old one..
6 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi everyone,
I am trying to have a second kernel in my Red hat 2.4.18.
I downloaded the 2.4.9 version and did all the extract and stuff. when I run the command make bzImage I get the following error:
devlist.h:6931: __devices_b1b3 causes a section type conflict
> devlist.h:6934:... (1 Reply)
Discussion started by: bashirpopal
1 Replies
2. Red Hat
Hello,
How to upgrade kernel from 2.4 to 2.6. Currently i am using rhel3 i want to upgrade it to 2.6
Please provide me the steps.
Prashant (1 Reply)
Discussion started by: prashant_ohol
1 Replies
3. Red Hat
Hello, everyone.
I am using Fedora 15, and want to upgrade to version 16. I follow the official link Upgrading Fedora using yum - FedoraProject to upgrade my OS by the following command:
yum update kernel* --releasever=16
yum groupupdate Base --releasever=16
reboot
After reboot, OS... (2 Replies)
Discussion started by: 915086731
2 Replies
4. OS X (Apple)
Howdy
I am trying to install links2 with graphics support on snow leopard 10.6.8 (xcode installed). I have had the program running last year, also installed from source - but then I had installed some image libraries with mac ports and fink - cannot reproduce that setup. Plus I would like to not... (6 Replies)
Discussion started by: butterbaerchen
6 Replies
5. Solaris
Hi Guys,
I am getting into patching activity now a days.
I had already done kernel upgrade through LU.
My doubt is if i had to install 3 patches to get my system to current available patch level, can i directly patch one by one on an inactive LU and once done i can activate it later on
or... (3 Replies)
Discussion started by: Rockyc3400
3 Replies
6. Red Hat
Dear All ,
I want upgrade my kernel version from kernel-2.6.18-164.el5 to kernel-2.6.18-199.el5.
We have RED HAT Linux Server Red Hat Enterprise Linux Server release 5.4 (Tikanga).
Kindly let me know where we can download this particular RPM.
if we want to download from RHN , pl let... (0 Replies)
Discussion started by: jegaraman
0 Replies
LEARN ABOUT HPUX
gvid_no_claim_dev
gvid_no_claim_dev(5) File Formats Manual gvid_no_claim_dev(5)
NAME
gvid_no_claim_dev - PCI Vendor/Device ID that the gvid graphics driver will not claim
VALUES
Failsafe
Default
Allowed values
Recommended values
Specific to the device you wish to prevent from claiming.
DESCRIPTION
This tunable specifies the PCI Vendor ID and/or Device ID of a graphics device that the HP graphics driver should not claim.
The graphics driver was designed to be a general purpose driver for all PCI graphics cards. As a result, the driver will attempt to claim
any PCI graphics display device found on the system. This can be a problem for graphics device developers who need their own graphics
driver to claim their own graphics device.
The value of will specify a PCI Vendor ID and/or Device ID of a graphics card that the gvid graphics driver should not claim. It is a 32
bit number, with the upper 16 bits containing the PCI Vendor ID and the lower 16 bits containing the PCI Device ID. Either the Vendor ID
or Device ID can use a wildcard value of
For example, if is set to the value the driver will ignore graphics devices with a PCI Vendor ID of and a Device ID of If is set to the
driver will not claim any graphics cards with a Vendor ID of regardless of the Device ID.
Who Is Expected to Change This Tunable?
Anyone who wishes the graphics driver to ignore a specific graphics device. This will typically be someone writing their own graphics
driver for their own hardware.
Restrictions on Changing
Changes to this tunable take effect at the next reboot.
What Other Tunables Should Be Changed at the Same Time?
None.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by HP.
Tunable Kernel Parameters gvid_no_claim_dev(5)