Dear Troy,
Thanks for explaining the situation. Output of lspci is given
below. It is generated while the machine (ASUS M3N78-EM motherboard
with NVIDIA GeForce 8300 chipset) was on openSUSE 11.0. I also want
to intimate you that the SATA hard disks are detected by Fedora 10 as well.
00:00.0 RAM memory: nVidia Corporation Device 0754 (rev a2)
00:01.0 ISA bridge: nVidia Corporation Device 075c (rev a2)
00:01.1 SMBus: nVidia Corporation Device 0752 (rev a1)
00:01.2 RAM memory: nVidia Corporation Device 0751 (rev a1)
00:01.3 Co-processor: nVidia Corporation Device 0753 (rev a2)
00:01.4 RAM memory: nVidia Corporation Device 0568 (rev a1)
00:02.0 USB Controller: nVidia Corporation Device 077b (rev a1)
00:02.1 USB Controller: nVidia Corporation Device 077c (rev a1)
00:04.0 USB Controller: nVidia Corporation Device 077d (rev a1)
00:04.1 USB Controller: nVidia Corporation Device 077e (rev a1)
00:06.0 IDE interface: nVidia Corporation Device 0759 (rev a1)
00:07.0 Audio device: nVidia Corporation Device 0774 (rev a1)
00:08.0 PCI bridge: nVidia Corporation Device 075a (rev a1)
00:09.0 IDE interface: nVidia Corporation Device 0ad0 (rev a2)
00:0a.0 Ethernet controller: nVidia Corporation Device 0760 (rev a2)
00:10.0 PCI bridge: nVidia Corporation Device 0778 (rev a1)
00:12.0 PCI bridge: nVidia Corporation Device 075b (rev a1)
00:13.0 PCI bridge: nVidia Corporation Device 077a (rev a1)
00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron,
Athlon64, Sempron] HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron,
Athlon64, Sempron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron,
Athlon64, Sempron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron,
Athlon64, Sempron] Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h [Opteron,
Athlon64, Sempron] Link Control
02:00.0 VGA compatible controller: nVidia Corporation GeForce 8600 GTS
(rev a1)
04:00.0 FireWire (IEEE 1394): JMicron Technologies, Inc. Device 2380
Jayakumar
Troy Dawson wrote:
> Hi,
> My first word of advice. Don't by Nvidia based chipsets. I've been
> saying that for years, and until NVidia decides to actually start
> working with the open source community ... correctly, I'm going to
> continue to say it. Giving us binary drivers is not "working with the
> community"
>
> Now that I'm off my soapbox (or whatever the equivalent is where you
> live), let's look at the problem.
>
> Please send us the output of
> /sbin/lspci
>
> Also please note that SL is an enterprise OS, meaning that it takes a
> while for newer drivers to make it into the release. OpenSuse, like
> Fedora, is not an enterprise distribution, so it always has the latest
> kernel, and hense, the latest drivers. And Debian 5.0 just barely
> came out.
>
> That being said, if you give us an 'lspci' we can at least look at it.
>
> Troy
>
> J S Jayakumar wrote:
>> Dear Troy,
>>
>> I have tested RC dated 11March. It is not able to recognise
>> hard disks on ASUS M3N78-EM motherboard for AMD processors.
>> Motherboard chipset is NVIDIA GeForce 8300. A Phemon processor and
>> 8GB ECC DDR2 RAM are installed in the motherboard. However, the hard
>> disk is detected on openSUSE 11.0 and Debian 5.0 and installation is
>> successful for these operating systems. Kindly update the SL release
>> candidate accordingly
>>
>> With regards,
>> J S Jayakumar.
>>
>> Troy Dawson wrote:
>>> J S Jayakumar wrote:
>>>> Dear Troy,
>>>>
>>>> As you know SL5.2 does not support many of the new mother
>>>> boards and other hardware. We are eagerly looking for the release
>>>> of SL 5.3 Can you pl. tell the probable date of release?
>>>>
>>>> J S Jayakumar.
>>>>
>>> This is from the RC 2 release notes
>>>
>>> ...
>>>
>>> The second release candidate for Scientific Linux 5.3 i386 has been
>>> released for both i386 and x86_64 on March 02.
>>>
>>> Release Candidate 2 has everything the way it should be, including yum
>>> and updates going to their proper place. We will then let it sit for
>>> almost two weeks as it get's it's final testing and pounding.
>>>
>>> If all goes well, we will incorporate any changes and release Release
>>> Candidate 2.5 somewhere around March 10 or 11. Release Candidate
>>> 2.5 is
>>> essentially the release and will only be changed if something critical
>>> or major happens.
>>>
>>> ...
>>>
>>> I would expect it's final release between March 13 and March 20.
>>>
>>> But you can always test before that. 5.3 Release Candidate 2 is what
>>> is in 5rolling, and any changes between now and the release *should*
>>> be fairly minor.
>>>
>>> Troy
>>
>
>
|
