8:25 a.m.
I decided to take the plunge and install F10 x86_64 preview on my main
system at home. This was absolutely the WORST and MOST BRUTAL
installation of Fedora I have ever experienced!!! What in wide world of
sports is going on here??? I was up until midnight trying to get my
system working again.
Had I been a newbie, my impression on Fedora and Linux would have been
that it truly sucks big time. Have I gotten anyone's attention yet...?
...Good. Here's what's wrong and (hopefully) what's needed to fix it.
First here's a summary of my system config (output of lshal available):
Motherboard:
eVGA e7100/630i
This MB uses nVidia onboard GeForce 7100 video with the nForce 630i
chipset. It also uses nVidia MCP73 High Definition Audio
CPU: Intel 2.4GHZ Core2 Quad
4GB RAM
320GB Western Digital SATA drive (WDC_WD3200AAKS)
Monitor: Acer P243W (connected via DVI cable)
OK - Here we go...
Installation was a nightmare (as witnessed by a friend who also
frequents this list). The main thing that was wrong was video. Simply
put, it just doesn't work - and to the point that the Live CD is
unusable and the Install DVD will only install in text mode. What I
found (after a lot of troubleshooting) was that F10 in the default
configuration just doesn't recognize the nVidia card correctly. To get
this to even come up, I had to:
1) Build a bootable USB drive from the live CD with a 2GB persistent
overlay
2) Boot the USB drive, and (because you get a BLANK SCREEN for a GDM
login window) use Alt-F2 to switch to a different tty
3) Login as root and then install system-config-display to the pen drive
4) Switch to run level 3
5) Run the command: system-config-display --reconfig and accept the
default configuration (which meant using the VESA driver and NOT the nv
driver)
6) launch launch X via startx and then run the installer
Notes on this (after "fixing" the USB drive):
1) Loading ANY video driver other than the VESA driver fails miserably.
2) Running the autologin loads a session, which immediately goes to a
blanked out white screen after trying to load 2 "untitled" windows (not
sure what these are), but just makes the desktop unusable. You must
switch to runlevel 3, login as root, load X, and then install.
3) Prior to installing, the hard disk MUST BE MANUALLY PARTITIONED with
fdisk such that ALL partitions are removed. If partitions exist on the
drive, the installer fails when trying to re-partition the drive. You
MUST REBOOT before attempting to install after removing all partitions
because the kernel apparently refuses to use the new partition table.
4) Something in the installation process takes a REALLY LONG TIME to
finish (I mean 20 minutes or more). I later found out that it has
something to do with kernel install / updates.
After getting to a successful completion of an install, reboot from the
hard disk and X will again no longer work. You have to do the following
next:
1) Boot the system, and switch to a different tty (as before)
2) Switch to runlevel 3
3) Install system-config-display (again)
4) Run "system-config-display --reconfig" and accept the VESA driver
defaults (again)
5) Reboot the machine so that firstboot can do its thing
Next, you get F10 in all its 800x600, 16 color display resolution glory
(think Monty Python style "...and there was great rejoicing" applause
here)...
First, run all of the rawhide patches. ANOTHER PROBLEM - the kernel
update alone took over 20 minutes to complete. Why??? It only seemed to
move forward after I put selinux into permissive mode - at which point
several hal oriented messages came through. I think this is also why the
last part of the install took 20 minutes (looking like it was dead at
the time). Reboot after the patches are done.
Next, go get the RPMFusion nVidia drivers (after poking around in all of
the /etc/yum.repos.d based repository files to point them to something
that actually works). Apparently, RPMFusion is currently still confused
over if we should be looking at the rawhide or pre-F10 repositories.
Doing this multiple times last night, there was no rhyme or reason to
this I could figure out, but eventually the rawhide repos worked.
Reboot one more time, and F10 came up on my screen in accelerated
1920x1200 resolution with all of the colors intact.
So now I have F10 running and all of my data has been restored from
backups.
* Flash works kind of - there's no sound.
* Speaking of sound, the sound tests work, but I don't actually GET any
sound to play until a few seconds after something tries to play. Thus,
the login sound never gets heard, neither does the logoff sound, etc.
* Evolution Bogofilter can't seem to figure out how to look for junk
mail. Loads of "Error checking for Junk" messages. Spamassasin works,
but is impressively slow (incredibly slow if you do remote tests).
I'm sure I'll find more as I dig into this deeper.
So there you have it. A very BRUTAL installation session for F10 preview
and an upgrade to rawhide.
I really hope we can do a lot better than this. My lshal output is
available upon request.
Cheers,
Chris
--
==================================
By all means marry;
If you get a good wife, you'll be happy.
If you get a bad one, you'll become a philosopher.
--Socrates
9:03 a.m.
On Sun, 16 Nov 2008 07:25:20 -0700
"Christopher A. Williams" <chriswfedora(a)cawllc.com> wrote:
5) Run the command: system-config-display --reconfig
It is possible that one of the exceedingly hard to find and
underdocumented kernel boot options for anaconda can force it
to use the vesa driver without all the trouble of doing a
usb boot and alternate console stuff, but there is no doubt that
video not working is a monumental pain when it happens.
I have sometimes work around video problems by doing a VNC
install and using a display on another system to provide video
(which only works if you have another system on the network :-).
Here's the link to anaconda options:
https://fedoraproject.org/wiki/Anaconda/Options
I don't see anything there about forcing vesa, but at least the
VNC options are documented. Maybe "xdriver=vesa" is the option
that forces use of vesa driver?
Having almost never encountered a video display that vesa didn't
work on, but having frequently encountered various video
systems that the supposed "proper" driver didn't work on, I
really do wonder why anaconda doesn't just always force vesa
for installs.
10:31 a.m.
Tom Horsley wrote:
On Sun, 16 Nov 2008 07:25:20 -0700
"Christopher A. Williams" <chriswfedora(a)cawllc.com> wrote:
> 5) Run the command: system-config-display --reconfig
>
It is possible that one of the exceedingly hard to find and
underdocumented kernel boot options for anaconda can force it
to use the vesa driver without all the trouble of doing a
usb boot and alternate console stuff, but there is no doubt that
video not working is a monumental pain when it happens.
I have sometimes work around video problems by doing a VNC
install and using a display on another system to provide video
(which only works if you have another system on the network :-).
Here's the link to anaconda options:
https://fedoraproject.org/wiki/Anaconda/Options
I don't see anything there about forcing vesa, but at least the
VNC options are documented. Maybe "xdriver=vesa" is the option
that forces use of vesa driver?
Having almost never encountered a video display that vesa didn't
work on, but having frequently encountered various video
systems that the supposed "proper" driver didn't work on, I
really do wonder why anaconda doesn't just always force vesa
for installs.
I did with F9 on a GF 7050 onboard graphics card.
9:30 a.m.
Oh. Please provide constructive feedback and help getting the problem
solved.
Christopher A. Williams wrote, On 11/16/2008 03:25 PM:
Installation was a nightmare (as witnessed by a friend who also
frequents this list). The main thing that was wrong was video. Simply
put, it just doesn't work
Point taken. Looks like
https://bugzilla.redhat.com/show_bug.cgi?id=465634 (which also suggests
boot parameter "xdriver=vesa" as temporary workaround)
Let's hope it gets fixed.
2) Running the autologin loads a session, which immediately goes to
a
blanked out white screen after trying to load 2 "untitled" windows (not
sure what these are), but just makes the desktop unusable. You must
switch to runlevel 3, login as root, load X, and then install.
So this is with vesa? It looks like a separate problem. But I don't
understand exactly how you get it. And what you call "must" is a
workaround that worked for you? I suggest you file this issue in bugzilla.
3) Prior to installing, the hard disk MUST BE MANUALLY PARTITIONED
with
fdisk such that ALL partitions are removed. If partitions exist on the
drive, the installer fails when trying to re-partition the drive.
That is not what other testers see. How did you see the failure? Any
exact messages? How did you reach your conclusion?
4) Something in the installation process takes a REALLY LONG TIME to
finish (I mean 20 minutes or more). I later found out that it has
something to do with kernel install / updates.
...
First, run all of the rawhide patches. ANOTHER PROBLEM - the kernel
update alone took over 20 minutes to complete. Why??? It only seemed to
move forward after I put selinux into permissive mode - at which point
several hal oriented messages came through. I think this is also why the
last part of the install took 20 minutes (looking like it was dead at
the time).
That is not what other testers see.
Could you try to run something like
mkinitrd -v -f /boot/initrd-2.6.27.5-109.fc10.i686.img
2.6.27.5-109.fc10.i686
and see if that takes 20 minutes - and which part of it that takes time?
* Flash works kind of - there's no sound.
64 bit machine or Flash 9?
http://docs.fedoraproject.org/release-notes/f10preview/en_US/What_is_the_...
* Speaking of sound, the sound tests work, but I don't actually
GET any
sound to play until a few seconds after something tries to play. Thus,
the login sound never gets heard, neither does the logoff sound, etc.
File a bug.
/Mads
10:18 a.m.
New subject: Flash support [branched fromRe: F10 on Homebuilt Box - Absolutely Brutal...!!!!]
On Sun, Nov 16, 2008 at 04:30:33PM +0100, Mads Kiilerich wrote:
64 bit machine or Flash 9?
http://docs.fedoraproject.org/release-notes/f10preview/en_US/What_is_the_...
I just looked at the release notes, and it's really quite unclear.
"If you are using Flash 10, you do not need libflashsupport anymore as
the usage of ALSA has been fixed in this version.
"Users of Fedora x86_64 must install the nspluginwrapper.i386 package to
enable the 32-bit Adobe Flash Player plug-in in Firefox, and the
libflashsupport.i386 package to enable sound from the plugin."
^^^^^^^^
So, is it needed or not?
According to a brief test I made yesterday, it may not be.
I removed libflashsupport with yum remove on a 64 bit install and sound
was fine.
--
Scott Robbins
PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6
Xander: So, we Bronzin' it tonight?
Willow: Wednesdays, kinda beat...
Xander: Well, we could grind our enemies into talcum powder with
a sledgehammer, but, gosh, we did that last night.
11:22 a.m.
New subject: Flash support [branched fromRe: F10 on Homebuilt Box - Absolutely Brutal...!!!!]
Scott Robbins wrote, On 11/16/2008 05:18 PM:
On Sun, Nov 16, 2008 at 04:30:33PM +0100, Mads Kiilerich wrote:
> 64 bit machine or Flash 9?
>
http://docs.fedoraproject.org/release-notes/f10preview/en_US/What_is_the_...
>
I just looked at the release notes, and it's really quite unclear.
"If you are using Flash 10, you do not need libflashsupport anymore as
the usage of ALSA has been fixed in this version.
"Users of Fedora x86_64 must install the nspluginwrapper.i386 package to
enable the 32-bit Adobe Flash Player plug-in in Firefox, and the
libflashsupport.i386 package to enable sound from the plugin."
^^^^^^^^
So, is it needed or not?
I thought it was clear but hard to read: That libflashsupport isn't
"generally" (ie on i386) needed, but on 64-bit it is however still needed.
I proposed a better wording on
https://bugzilla.redhat.com/show_bug.cgi?id=471793 .
According to a brief test I made yesterday, it may not be.
I removed libflashsupport with yum remove on a 64 bit install and sound
was fine.
Interesting. Please try to remove your flash-plugin and nspluginwrappers
and make it work again. And then please add a comment to the bug I
mentioned.
Oh, by the way: Was it a i386 or x86_64 libflashsupport you uninstalled?
I think much of the flash confusion comes because nspluginwrapper runs
mozilla-plugin-config on installation. That makes it hard to figure out
what is going on; it is not only a question of which packages has been
installed, but also in which order.
/Mads
11:50 a.m.
New subject: Flash support [branched fromRe: F10 on Homebuilt Box - Absolutely Brutal...!!!!]
On Sun, Nov 16, 2008 at 6:22 PM, Mads Kiilerich <mads(a)kiilerich.com> wrote:
Scott Robbins wrote, On 11/16/2008 05:18 PM:
>
> On Sun, Nov 16, 2008 at 04:30:33PM +0100, Mads Kiilerich wrote:
>
>>
>> 64 bit machine or Flash 9?
>>
http://docs.fedoraproject.org/release-notes/f10preview/en_US/What_is_the_...
>>
>
> I just looked at the release notes, and it's really quite unclear.
> "If you are using Flash 10, you do not need libflashsupport anymore as
> the usage of ALSA has been fixed in this version.
> "Users of Fedora x86_64 must install the nspluginwrapper.i386 package to
> enable the 32-bit Adobe Flash Player plug-in in Firefox, and the
> libflashsupport.i386 package to enable sound from the plugin."
> ^^^^^^^^
>
> So, is it needed or not?
I thought it was clear but hard to read: That libflashsupport isn't
"generally" (ie on i386) needed, but on 64-bit it is however still needed.
NO, its *NOT* needed.
1:09 p.m.
New subject: Flash support [branched fromRe: F10 on Homebuilt Box - Absolutely Brutal...!!!!]
On Sun, Nov 16, 2008 at 06:50:14PM +0100, drago01 wrote:
--
Scott Robbins
PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6
Spike: A slayer with family and friends. That sure as hell wasn't
in the brochure.
On Sun, Nov 16, 2008 at 6:22 PM, Mads Kiilerich
<mads(a)kiilerich.com> wrote:
> Scott Robbins wrote, On 11/16/2008 05:18 PM:
>>
>> On Sun, Nov 16, 2008 at 04:30:33PM +0100, Mads Kiilerich wrote:
>>
> I thought it was clear but hard to read: That libflashsupport isn't
> "generally" (ie on i386) needed, but on 64-bit it is however still
needed.
NO, its *NOT* needed.
Yup you are correct, it is NOT needed. (As per follow-up email, which
should appear before this one, I've added my comments to yours and Mads'
on the bug report.)
2:30 p.m.
New subject: Flash support [branched fromRe: F10 on Homebuilt Box - Absolutely Brutal...!!!!]
On Sun, 2008-11-16 at 14:09 -0500, Scott Robbins wrote:
On Sun, Nov 16, 2008 at 06:50:14PM +0100, drago01 wrote:
> On Sun, Nov 16, 2008 at 6:22 PM, Mads Kiilerich <mads(a)kiilerich.com> wrote:
> > Scott Robbins wrote, On 11/16/2008 05:18 PM:
> >>
> >> On Sun, Nov 16, 2008 at 04:30:33PM +0100, Mads Kiilerich wrote:
> >>
> > I thought it was clear but hard to read: That libflashsupport isn't
> > "generally" (ie on i386) needed, but on 64-bit it is however still
needed.
>
> NO, its *NOT* needed.
Yup you are correct, it is NOT needed. (As per follow-up email, which
should appear before this one, I've added my comments to yours and Mads'
on the bug report.)
>
I'll have to look at this a little closre later tonight. I did remove
and reinstall nspluginwrapper (386 and x64), as well as Flash 10, in the
order specified.
After this, Flash still does not have any sound...
--
==================================
By all means marry;
If you get a good wife, you'll be happy.
If you get a bad one, you'll become a philosopher.
--Socrates
4:53 p.m.
New subject: Flash support [branched fromRe: F10 on Homebuilt Box - Absolutely Brutal...!!!!]
On Sun, 16 Nov 2008, drago01 wrote:
On Sun, Nov 16, 2008 at 6:22 PM, Mads Kiilerich
<mads(a)kiilerich.com> wrote:
> Scott Robbins wrote, On 11/16/2008 05:18 PM:
>>
>> On Sun, Nov 16, 2008 at 04:30:33PM +0100, Mads Kiilerich wrote:
>>
>>>
>>> 64 bit machine or Flash 9?
>>>
http://docs.fedoraproject.org/release-notes/f10preview/en_US/What_is_the_...
>>>
>>
>> I just looked at the release notes, and it's really quite unclear.
>> "If you are using Flash 10, you do not need libflashsupport anymore as
>> the usage of ALSA has been fixed in this version.
>> "Users of Fedora x86_64 must install the nspluginwrapper.i386 package to
>> enable the 32-bit Adobe Flash Player plug-in in Firefox, and the
>> libflashsupport.i386 package to enable sound from the plugin."
>> ^^^^^^^^
>>
>> So, is it needed or not?
>
> I thought it was clear but hard to read: That libflashsupport isn't
> "generally" (ie on i386) needed, but on 64-bit it is however still needed.
NO, its *NOT* needed.
Tell that to my system. :-) On my F10 x86_64 system, audio does not work
without it. I know what the docs say but...
The problem for me is I am not sure what to file a bug against. Suggestions?
Regards,
--
Tom Diehl tdiehl(a)rogueind.com Spamtrap address mtd123(a)rogueind.com
12:45 p.m.
New subject: Flash support [branched fromRe: F10 on Homebuilt Box - Absolutely Brutal...!!!!]
On Sun, 2008-11-16 at 18:22 +0100, Mads Kiilerich wrote:
I thought it was clear but hard to read: That libflashsupport
isn't
"generally" (ie on i386) needed, but on 64-bit it is however still
needed.
Nope. Flash works fine for me on x86_64 (with sound and everything) and
I don't have libflashsupport. This is with the Adobe plugin BTW, in case
it isn't clear.
poc
12:57 p.m.
New subject: Flash support [branched fromRe: F10 on Homebuilt Box - Absolutely Brutal...!!!!]
On Sun, Nov 16, 2008 at 06:22:16PM +0100, Mads Kiilerich wrote:
Scott Robbins wrote, On 11/16/2008 05:18 PM:
> On Sun, Nov 16, 2008 at 04:30:33PM +0100, Mads Kiilerich wrote:
>
I proposed a better wording on
https://bugzilla.redhat.com/show_bug.cgi?id=471793 .
> According to a brief test I made yesterday, it may not be. I removed
> libflashsupport with yum remove on a 64 bit install and sound
> was fine.
Interesting. Please try to remove your flash-plugin and nspluginwrappers
and make it work again. And then please add a comment to the bug I
mentioned.
Ok, I removed both, and also removed firefox and my ~/.mozilla
directory, to do my best to duplicate a clean install of all three.
I also removed opera and renamed my .opera directory. (As it's my usual
browser, I didn't want to lose it, but did start with a fresh one.)
Reinstalled opera. Reinstalled flash.
Flash works, with sound. At this point, there is no nspluginwrapper.
One more reason it's better than Firefox, but that's a bikeshed thread.
:)
Install firefox.
No plugins shown.
yum -y install nspluginwrapper.{i386,x86_64}
Start firefox. Plugin shown and works with sound.
So, apparently libflashsupport is no longer necessary. This is actually
a good thing.
yum search libflashsupport
No Matches found.
So, I sure *hope* it's not needed. :)
I'll add my comments to the bug very shortly, without the color
commentary.
I think much of the flash confusion comes because nspluginwrapper runs
mozilla-plugin-config on installation. That makes it hard to figure out
what is going on; it is not only a question of which packages has been
installed, but also in which order.
Yes, and this also means it shouldn't be necessary to run
mozilla--plugin-config, which should also be added to the documentation.
Thanks for pushing me to test it, I learned something.
--
Scott Robbins
PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6
Xander: I wish dating was like slaying. You know, simple, direct,
stake through the heart, no muss, no fuss.
7:11 p.m.
New subject: Flash support [branched fromRe: F10 on Homebuilt Box - Absolutely Brutal...!!!!]
On Sun, 2008-11-16 at 11:18 -0500, Scott Robbins wrote:
"Users of Fedora x86_64 must install the nspluginwrapper.i386
package to
enable the 32-bit Adobe Flash Player plug-in in Firefox, and the
libflashsupport.i386 package to enable sound from the plugin."
^^^^^^^^
So, is it needed or not?
No. Install alsa-{libs,plugin-pulseaudio}.i386 instead.
--
Ignacio Vazquez-Abrams <ivazqueznet(a)gmail.com>
PLEASE don't CC me; I'm already subscribed
8:49 p.m.
New subject: Flash support [branched fromRe: F10 on Homebuilt Box - Absolutely Brutal...!!!!]
On Sun, Nov 16, 2008 at 08:11:16PM -0500, Ignacio Vazquez-Abrams wrote:
On Sun, 2008-11-16 at 11:18 -0500, Scott Robbins wrote:
> "Users of Fedora x86_64 must install the nspluginwrapper.i386 package to
> enable the 32-bit Adobe Flash Player plug-in in Firefox, and the
> libflashsupport.i386 package to enable sound from the plugin."
> ^^^^^^^^
>
> So, is it needed or not?
No. Install alsa-{libs,plugin-pulseaudio}.i386 instead.
As I said on the bug report, for me, alsa-plugin-pulseaudio breaks,
rather than fixes sound for me. :)
It seems we're going to have a hard time finding a solution that works
for all of us.
Again, as I stated in earlier posts here, I'm not sure that I would have
this problem if I used Gnome, but I use console and fluxbox.
--
Scott Robbins
PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6
Willow: I just talked to Buffy, and yeah, I think she's feeling a
little... insane. No, not bitchy crazy, more like homicidal
maniac crazy. So I told her to come see you, 'kay?
8:53 p.m.
On Sun, 2008-11-16 at 16:30 +0100, Mads Kiilerich wrote:
Oh. Please provide constructive feedback and help getting the problem
solved.
I think I've been doing that. I also was just venting after a really
frustrating experience...
Christopher A. Williams wrote, On 11/16/2008 03:25 PM:
> Installation was a nightmare (as witnessed by a friend who also
> frequents this list). The main thing that was wrong was video. Simply
> put, it just doesn't work
Point taken. Looks like
https://bugzilla.redhat.com/show_bug.cgi?id=465634 (which also suggests
boot parameter "xdriver=vesa" as temporary workaround)
Let's hope it gets fixed.
Indeed. This looks like the one.
> 2) Running the autologin loads a session, which immediately goes to a
> blanked out white screen after trying to load 2 "untitled" windows (not
> sure what these are), but just makes the desktop unusable. You must
> switch to runlevel 3, login as root, load X, and then install.
>
So this is with vesa? It looks like a separate problem. But I don't
understand exactly how you get it. And what you call "must" is a
workaround that worked for you? I suggest you file this issue in bugzilla.
Just to clarify - yes, this is a work around that worked for me. Also,
yes this is with vesa loading as the video driver. My "fixed" USB drive
will boot. Letting it automatically logon loads the desktop, but
something else is also starting that eventually causes the screen to go
white. I think if we fixed the first problem, the second might not be an
issue. Whatever is loading apparently doesn't load when you login as
root.
> 3) Prior to installing, the hard disk MUST BE MANUALLY PARTITIONED with
> fdisk such that ALL partitions are removed. If partitions exist on the
> drive, the installer fails when trying to re-partition the drive.
That is not what other testers see. How did you see the failure? Any
exact messages? How did you reach your conclusion?
I guess I'm unique then. I'm sure I don't see things other testers do.
That said, I can't remember the exact error message, but it happens when
partitioning the drive when clicking the "Write Changes to Disk" button.
The system then responds that there was an error with partitioning, that
it "was serious", and that the install can not continue.
If I delete all partitions, reboot, and then run the install the same
way, clicking "Write Changes to Disk" works normally, and the install
continues without further incident.
> 4) Something in the installation process takes a REALLY LONG TIME to
> finish (I mean 20 minutes or more). I later found out that it has
> something to do with kernel install / updates.
>
...
> First, run all of the rawhide patches. ANOTHER PROBLEM - the kernel
> update alone took over 20 minutes to complete. Why??? It only seemed to
> move forward after I put selinux into permissive mode - at which point
> several hal oriented messages came through. I think this is also why the
> last part of the install took 20 minutes (looking like it was dead at
> the time).
>
That is not what other testers see.
Again, I apparently don't see things they
do, but this is clearly
reproducible.
Could you try to run something like
mkinitrd -v -f /boot/initrd-2.6.27.5-109.fc10.i686.img
2.6.27.5-109.fc10.i686
and see if that takes 20 minutes - and which part of it that takes time?
Good Call!! Indeed, this is what is apparently taking forever and a day
to complete. Here's the key output:
# mkinitrd -v -f /boot/initrd-2.6.27.5-109.fc10.x86_64.img
2.6.27.5-109.fc10.x86_64
Creating initramfs <---------THIS ONE TAKES A REALLY LONG TIME!!!!!!!
get_netlink_msg returned No buffer space available <--IS THIS WHY?
Found root device /sys/block/dm-0 for /dev/VolGroup00/LogVol00
Looking for driver for device /sys/block/dm-0
Looking for driver for device sda2
Looking for deps of module scsi:t-0x00
Looking for deps of module
pci:v000010DEd000007F0sv000010DEsd0000CB73bc01sc01i85: pata_acpi
ata_generic <----------------- THIS ONE TAKES A REALLY LONG TIME TOO!!!
get_netlink_msg returned No buffer space available <--IT HAPPENED AGAIN!
Found swsusp device /sys/block/dm-1 for /dev/VolGroup00/LogVol01
Looking for driver for device /sys/block/dm-1
Using modules: pata_acpi ata_generic
... (everything else runs as fast as you would expect...)
/etc/ld.so.conf.d/mysql-x86_64.conf
-> /tmp/initrd.yFK3b5/etc/ld.so.conf.d/mysql-x86_64.conf
/etc/ld.so.conf.d/atlas-x86_64.conf
-> /tmp/initrd.yFK3b5/etc/ld.so.conf.d/atlas-x86_64.conf
Running ldconfig
...and it finishes!
> * Flash works kind of - there's no sound.
>
64 bit machine or Flash 9?
http://docs.fedoraproject.org/release-notes/f10preview/en_US/What_is_the_...
64-bit, F10, Flash 10. Installation per the famed release notes. No
sound in Flash. Tried other suggestions from the branched thread. Still
no sound in Flash.
> * Speaking of sound, the sound tests work, but I don't
actually GET any
> sound to play until a few seconds after something tries to play. Thus,
> the login sound never gets heard, neither does the logoff sound, etc.
>
File a bug.
OK - I'll happily do that.
--
==================================
By all means marry;
If you get a good wife, you'll be happy.
If you get a bad one, you'll become a philosopher.
--Socrates
9:47 a.m.
I build my own desktop boxes and usually pick a motherboard that Fedora
is known to work on. Some motherboards just don't work, at least with
older versions of Fedora.
For example the motherboard I'm using now is the Asrock 939SLI32-eSATA2
and I'm using an PCI Express nVidia graphics card -- I forgot the name a
long time ago. Point is, I asked on the x86_64 list for board
recommendations and then bought the recommended board. I seem to recall
there was a problem with the onboard network chip but I fixed it quickly
by finding the right driver and compiling it. Then future kernel updates
had it by default.
I have not paid it the slightest attention in the last few years, but I
believe there is a hardware compatibility list you can check.
You may have seen some of my earlier posts asking about the Dell
Latitude E-series notebooks. I was wondering if others have gotten F10
to install on that. There were no responses -- interesting.
My suggestion is, ask around for a motherboard that works with Fedora
10, and buy and install that. It isn't too tough to change a
motherboard. It might cost you something for new memory though -- and
I've noticed the memory prices Dell quotes for 4 Gb chips are really
high...hmmm. I don't know if that's a market trend.
My current Asrock system is sorely in need of replacement, and I'm
thinking of retiring the desktop entirely and replacing it with a notebook.
Bob Cochran
Christopher A. Williams wrote:
I decided to take the plunge and install F10 x86_64 preview on my
main
system at home. This was absolutely the WORST and MOST BRUTAL
installation of Fedora I have ever experienced!!! What in wide world of
sports is going on here??? I was up until midnight trying to get my
system working again.
Had I been a newbie, my impression on Fedora and Linux would have been
that it truly sucks big time. Have I gotten anyone's attention yet...?
...Good. Here's what's wrong and (hopefully) what's needed to fix it.
First here's a summary of my system config (output of lshal available):
Motherboard:
eVGA e7100/630i
This MB uses nVidia onboard GeForce 7100 video with the nForce 630i
chipset. It also uses nVidia MCP73 High Definition Audio
CPU: Intel 2.4GHZ Core2 Quad
4GB RAM
320GB Western Digital SATA drive (WDC_WD3200AAKS)
Monitor: Acer P243W (connected via DVI cable)
OK - Here we go...
Installation was a nightmare (as witnessed by a friend who also
frequents this list). The main thing that was wrong was video. Simply
put, it just doesn't work - and to the point that the Live CD is
unusable and the Install DVD will only install in text mode. What I
found (after a lot of troubleshooting) was that F10 in the default
configuration just doesn't recognize the nVidia card correctly. To get
this to even come up, I had to:
1) Build a bootable USB drive from the live CD with a 2GB persistent
overlay
2) Boot the USB drive, and (because you get a BLANK SCREEN for a GDM
login window) use Alt-F2 to switch to a different tty
3) Login as root and then install system-config-display to the pen drive
4) Switch to run level 3
5) Run the command: system-config-display --reconfig and accept the
default configuration (which meant using the VESA driver and NOT the nv
driver)
6) launch launch X via startx and then run the installer
Notes on this (after "fixing" the USB drive):
1) Loading ANY video driver other than the VESA driver fails miserably.
2) Running the autologin loads a session, which immediately goes to a
blanked out white screen after trying to load 2 "untitled" windows (not
sure what these are), but just makes the desktop unusable. You must
switch to runlevel 3, login as root, load X, and then install.
3) Prior to installing, the hard disk MUST BE MANUALLY PARTITIONED with
fdisk such that ALL partitions are removed. If partitions exist on the
drive, the installer fails when trying to re-partition the drive. You
MUST REBOOT before attempting to install after removing all partitions
because the kernel apparently refuses to use the new partition table.
4) Something in the installation process takes a REALLY LONG TIME to
finish (I mean 20 minutes or more). I later found out that it has
something to do with kernel install / updates.
After getting to a successful completion of an install, reboot from the
hard disk and X will again no longer work. You have to do the following
next:
1) Boot the system, and switch to a different tty (as before)
2) Switch to runlevel 3
3) Install system-config-display (again)
4) Run "system-config-display --reconfig" and accept the VESA driver
defaults (again)
5) Reboot the machine so that firstboot can do its thing
Next, you get F10 in all its 800x600, 16 color display resolution glory
(think Monty Python style "...and there was great rejoicing" applause
here)...
First, run all of the rawhide patches. ANOTHER PROBLEM - the kernel
update alone took over 20 minutes to complete. Why??? It only seemed to
move forward after I put selinux into permissive mode - at which point
several hal oriented messages came through. I think this is also why the
last part of the install took 20 minutes (looking like it was dead at
the time). Reboot after the patches are done.
Next, go get the RPMFusion nVidia drivers (after poking around in all of
the /etc/yum.repos.d based repository files to point them to something
that actually works). Apparently, RPMFusion is currently still confused
over if we should be looking at the rawhide or pre-F10 repositories.
Doing this multiple times last night, there was no rhyme or reason to
this I could figure out, but eventually the rawhide repos worked.
Reboot one more time, and F10 came up on my screen in accelerated
1920x1200 resolution with all of the colors intact.
So now I have F10 running and all of my data has been restored from
backups.
* Flash works kind of - there's no sound.
* Speaking of sound, the sound tests work, but I don't actually GET any
sound to play until a few seconds after something tries to play. Thus,
the login sound never gets heard, neither does the logoff sound, etc.
* Evolution Bogofilter can't seem to figure out how to look for junk
mail. Loads of "Error checking for Junk" messages. Spamassasin works,
but is impressively slow (incredibly slow if you do remote tests).
I'm sure I'll find more as I dig into this deeper.
So there you have it. A very BRUTAL installation session for F10 preview
and an upgrade to rawhide.
I really hope we can do a lot better than this. My lshal output is
available upon request.
Cheers,
Chris
--
==================================
By all means marry;
If you get a good wife, you'll be happy.
If you get a bad one, you'll become a philosopher.
--Socrates
2:21 p.m.
On Sun, 2008-11-16 at 10:47 -0500, Robert L Cochran wrote:
I build my own desktop boxes and usually pick a motherboard that
Fedora
is known to work on. Some motherboards just don't work, at least with
older versions of Fedora.
For example the motherboard I'm using now is the Asrock 939SLI32-eSATA2
and I'm using an PCI Express nVidia graphics card -- I forgot the name a
long time ago. Point is, I asked on the x86_64 list for board
recommendations and then bought the recommended board. I seem to recall
there was a problem with the onboard network chip but I fixed it quickly
by finding the right driver and compiling it. Then future kernel updates
had it by default.
I have not paid it the slightest attention in the last few years, but I
believe there is a hardware compatibility list you can check.
You may have seen some of my earlier posts asking about the Dell
Latitude E-series notebooks. I was wondering if others have gotten F10
to install on that. There were no responses -- interesting.
My suggestion is, ask around for a motherboard that works with Fedora
10, and buy and install that. It isn't too tough to change a
motherboard. It might cost you something for new memory though -- and
I've noticed the memory prices Dell quotes for 4 Gb chips are really
high...hmmm. I don't know if that's a market trend.
My current Asrock system is sorely in need of replacement, and I'm
thinking of retiring the desktop entirely and replacing it with a notebook.
Correcting the top post along with this...
Short answer: No I am not going to buy another motherboard.
This exact system ran just fine on F9, BTW.
--
==================================
By all means marry;
If you get a good wife, you'll be happy.
If you get a bad one, you'll become a philosopher.
--Socrates
11:52 a.m.
On Sun, Nov 16, 2008 at 07:25:20AM -0700, Christopher A. Williams wrote:
Installation was a nightmare (as witnessed by a friend who also
frequents this list). The main thing that was wrong was video. Simply
put, it just doesn't work
Did you try with 'nomodeset' passed as a kernel parameter?
M.
2:31 p.m.
On Sun, 2008-11-16 at 10:52 -0700, Michal Jaegermann wrote:
On Sun, Nov 16, 2008 at 07:25:20AM -0700, Christopher A. Williams
wrote:
> Installation was a nightmare (as witnessed by a friend who also
> frequents this list). The main thing that was wrong was video. Simply
> put, it just doesn't work
Did you try with 'nomodeset' passed as a kernel parameter?
No I did not. I will try to have a closer look later tonight...
--
==================================
By all means marry;
If you get a good wife, you'll be happy.
If you get a bad one, you'll become a philosopher.
--Socrates
9:44 p.m.
On Sun, Nov 16, 2008 at 13:31:24 -0700,
"Christopher A. Williams" <chriswfedora(a)cawllc.com> wrote:
On Sun, 2008-11-16 at 10:52 -0700, Michal Jaegermann wrote:
> On Sun, Nov 16, 2008 at 07:25:20AM -0700, Christopher A. Williams wrote:
> > Installation was a nightmare (as witnessed by a friend who also
> > frequents this list). The main thing that was wrong was video. Simply
> > put, it just doesn't work
>
> Did you try with 'nomodeset' passed as a kernel parameter?
No I did not. I will try to have a closer look later tonight...
That shouldn't help with an nVidia card, as modesetting isn't used with them.
9:47 a.m.
On Sun, 2008-11-16 at 07:25 -0700, Christopher A. Williams wrote:
Motherboard:
eVGA e7100/630i
This MB uses nVidia onboard GeForce 7100 video with the nForce 630i
chipset. It also uses nVidia MCP73 High Definition Audio
Do you have an X log showing what happens when you run the nv driver?
- ajax
10:56 a.m.
On Tue, 2008-11-18 at 10:47 -0500, Adam Jackson wrote:
On Sun, 2008-11-16 at 07:25 -0700, Christopher A. Williams wrote:
> Motherboard:
> eVGA e7100/630i
> This MB uses nVidia onboard GeForce 7100 video with the nForce 630i
> chipset. It also uses nVidia MCP73 High Definition Audio
Do you have an X log showing what happens when you run the nv driver?
This is going to be long (due to the log length), but hopefully this
helps you out. Keep in mind that, by default (ie absent any xorg.conf
file or what system-config-display wants to set up), only the vesa
driver is used. I have to specifically say that I want to use the nv
driver.
I used system-config-display --reconfig to create a default xorg.conf
file using the nv driver and to autoconfigure the display.
Here's the xorg.conf file that was generated:
# Xorg configuration created by system-config-display
Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
# keyboard added by rhpxl
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105+inet"
Option "XkbLayout" "us"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "nv"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
===========================
...And here's the corresponding Xorg.0.log file (fresh) that resulted
from trying to start the X server using that config file:
X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.18-107.el5xen x86_64
Current Operating System: Linux spikehome.spikelan.local
2.6.27.5-109.fc10.x86_64 #1 SMP Thu Nov 13 20:12:05 EST 2008 x86_64
Build Date: 31 October 2008 01:39:18PM
Build ID: xorg-x11-server 1.5.2-12.fc10
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Nov 18 09:37:31 2008
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "single head configuration"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Videocard0"
(==) No monitor specified for screen "Screen0".
Using a default monitor configuration.
(**) |-->Input Device "Keyboard0"
(==) Automatically adding devices
(==) Automatically enabling devices
(==) No FontPath specified. Using compiled-in default.
(==) FontPath set to:
catalogue:/etc/X11/fontpath.d,
built-ins
(==) ModulePath set to "/usr/lib64/xorg/modules"
(II) Cannot locate a core pointer device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable
AllowEmptyInput.
(WW) AllowEmptyInput is on, devices using drivers 'kbd' or 'mouse' will
be disabled.
(WW) Disabling Keyboard0
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or
directory)
(II) No APM support in BIOS or kernel
(II) Loader magic: 0x7ae540
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 4.1
X.Org XInput driver : 2.1
X.Org Server Extension : 1.1
X.Org Font Renderer : 0.6
(II) Loader running on linux
(--) using VT number 7
(--) PCI:*(0@0:16:0) nVidia Corporation GeForce 7100/nForce 630i rev
162, Mem @ 0xed000000/16777216, 0xd0000000/268435456,
0xee000000/16777216, BIOS @ 0x????????/131072
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) LoadModule: "extmod"
(II) Loading /usr/lib64/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension SELinux
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib64/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib64/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(==) AIGLX enabled
(==) Exporting typical set of GLX visuals
(II) Loading extension GLX
(II) LoadModule: "freetype"
(II) Loading /usr/lib64/xorg/modules/fonts//libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 1.5.2, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.6
(II) Loading font FreeType
(II) LoadModule: "dri"
(II) Loading /usr/lib64/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension XFree86-DRI
(II) LoadModule: "nv"
(II) Loading /usr/lib64/xorg/modules/drivers//nv_drv.so
(II) Module nv: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 2.1.12
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 4.1
(II) NV: driver for NVIDIA chipsets: RIVA 128, RIVA TNT, RIVA TNT2,
Unknown TNT2, Vanta, RIVA TNT2 Ultra, RIVA TNT2 Model 64,
Aladdin TNT2, GeForce 256, GeForce DDR, Quadro, GeForce2 MX/MX 400,
GeForce2 MX 100/200, GeForce2 Go, Quadro2 MXR/EX/Go,
GeForce2 Integrated GPU, GeForce2 GTS, GeForce2 Ti, GeForce2 Ultra,
Quadro2 Pro, GeForce4 MX 460, GeForce4 MX 440, GeForce4 MX 420,
GeForce4 MX 440-SE, GeForce4 440 Go, GeForce4 420 Go,
GeForce4 420 Go 32M, GeForce4 460 Go, Quadro4 550 XGL,
GeForce4 440 Go 64M, Quadro NVS, Quadro4 500 GoGL,
GeForce4 410 Go 16M, GeForce4 MX 440 with AGP8X,
GeForce4 MX 440SE with AGP8X, GeForce4 MX 420 with AGP8X,
GeForce4 MX 4000, GeForce4 448 Go, GeForce4 488 Go, Quadro4 580 XGL,
Quadro4 NVS 280 SD, Quadro4 380 XGL, Quadro NVS 50 PCI,
GeForce4 448 Go, GeForce4 MX Integrated GPU, GeForce3,
GeForce3 Ti 200, GeForce3 Ti 500, Quadro DCC, GeForce4 Ti 4600,
GeForce4 Ti 4400, GeForce4 Ti 4200, Quadro4 900 XGL, Quadro4 750 XGL,
Quadro4 700 XGL, GeForce4 Ti 4800, GeForce4 Ti 4200 with AGP8X,
GeForce4 Ti 4800 SE, GeForce4 4200 Go, Quadro4 700 GoGL,
Quadro4 980 XGL, Quadro4 780 XGL, GeForce FX 5800 Ultra,
GeForce FX 5800, Quadro FX 2000, Quadro FX 1000,
GeForce FX 5600 Ultra, GeForce FX 5600, GeForce FX 5600XT,
GeForce FX Go5600, GeForce FX Go5650, Quadro FX Go700,
GeForce FX 5200, GeForce FX 5200 Ultra, GeForce FX 5200,
GeForce FX 5200LE, GeForce FX Go5200, GeForce FX Go5250,
GeForce FX 5500, GeForce FX 5100, GeForce FX Go5200 32M/64M,
Quadro NVS 55/280 PCI, Quadro FX 500/600 PCI,
GeForce FX Go53xx Series, GeForce FX Go5100, GeForce FX 5900 Ultra,
GeForce FX 5900, GeForce FX 5900XT, GeForce FX 5950 Ultra,
GeForce FX 5900ZT, Quadro FX 3000, Quadro FX 700,
GeForce FX 5700 Ultra, GeForce FX 5700, GeForce FX 5700LE,
GeForce FX 5700VE, GeForce FX Go5700, GeForce FX Go5700,
Quadro FX Go1000, Quadro FX 1100, GeForce 6800 Ultra, GeForce 6800,
GeForce 6800 LE, GeForce 6800 XE, GeForce 6800 XT, GeForce 6800 GT,
GeForce 6800 GT, GeForce 6800 GS, GeForce 6800 XT, Quadro FX 4000,
GeForce 6800 GS, GeForce 6800, GeForce 6800 LE, GeForce 6800 XT,
GeForce Go 6800, GeForce Go 6800 Ultra, Quadro FX Go1400,
Quadro FX 3450/4000 SDI, Quadro FX 1400, GeForce 6600 GT,
GeForce 6600, GeForce 6600 LE, GeForce 6600 VE, GeForce Go 6600,
GeForce 6610 XL, GeForce Go 6600 TE/6200 TE, GeForce 6700 XL,
GeForce Go 6600, GeForce Go 6600 GT, Quadro FX 550, Quadro FX 550,
Quadro FX 540, GeForce 6200, GeForce 6500,
GeForce 6200 TurboCache(TM), GeForce 6200SE TurboCache(TM),
GeForce 6200 LE, GeForce Go 6200, Quadro NVS 285, GeForce Go 6400,
GeForce Go 6200, GeForce Go 6400, GeForce 6250, GeForce 6800,
GeForce 6800 LE, GeForce 6800 GT, GeForce 6800 XT, GeForce 6200,
GeForce 6200 A-LE, GeForce 7800 GTX, GeForce 7800 GTX,
GeForce 7800 GT, GeForce 7800 GS, GeForce 7800 SLI, GeForce Go 7800,
GeForce Go 7800 GTX, Quadro FX 4500, GeForce 7300 LE,
GeForce 7300 SE, GeForce Go 7200, GeForce Go 7300, GeForce Go 7400,
GeForce Go 7400 GS, Quadro NVS 110M, Quadro NVS 120M, Quadro FX 350M,
GeForce 7500 LE, Quadro FX 350, GeForce 7300 GS, GeForce 7600 GT,
GeForce 7600 GS, GeForce 7300 GT, GeForce 7600 LE, GeForce 7300 GT,
GeForce Go 7700, GeForce Go 7600, GeForce Go 7600 GT,
Quadro NVS 300M, GeForce Go 7900 SE, Quadro FX 550M, Quadro FX 560,
GeForce 7900 GTX, GeForce 7900 GT, GeForce 7900 GS,
GeForce Go 7900 GS, GeForce Go 7900 GTX, Quadro FX 2500M,
Quadro FX 1500M, Quadro FX 5500, Quadro FX 3500, Quadro FX 1500,
Quadro FX 4500 X2, GeForce 6150, GeForce 6150 LE, GeForce 6100,
GeForce Go 6150, GeForce Go 6100, GeForce 8800 GTX, GeForce 8800 GTS,
GeForce 8800 Ultra, Quadro FX 5600, Quadro FX 4600, GeForce 8600 GTS,
GeForce 8600 GT, GeForce 8600 GT, GeForce 8600 GS, GeForce 8400 GS,
GeForce 9500M GS, GeForce 8600M GT, GeForce 9650M GS,
GeForce 8700M GT, Quadro FX 370, Quadro NVS 320M, Quadro FX 570M,
Quadro FX 1600M, Quadro FX 570, Quadro FX 1700, GeForce 8400 SE,
GeForce 8500 GT, GeForce 8400 GS, GeForce 8300 GS, GeForce 8400 GS,
GeForce 8600M GS, GeForce 8400M GT, GeForce 8400M GS,
GeForce 8400M G, Quadro NVS 140M, Quadro NVS 130M, Quadro NVS 135M,
GeForce 9400 GT, Quadro FX 360M, GeForce 9300M G, Quadro NVS 290,
GeForce GTX 280, GeForce GTX 260, GeForce 8800 GTS 512,
GeForce 8800 GT, GeForce 9800 GX2, GeForce 8800 GS,
GeForce 8800M GTS, GeForce 8800M GTX, GeForce 8800 GS,
GeForce 9600 GSO, GeForce 8800 GT, GeForce 9800 GTX,
GeForce 9800 GTK+, GeForce 9800 GT, Quadro FX 3700, Quadro FX 3600M,
GeForce 9600 GT, GeForce 9600 GS, GeForce 9800M GTS,
GeForce 9700M GTS, GeForce 9800M GTS, GeForce 9500 GT,
GeForce 9600M GT, GeForce 9600M GS, GeForce 9600M GT,
GeForce 9500M G, GeForce 9300 GS, GeForce 8400 GS, GeForce 9300M GS,
GeForce 9200M GS, GeForce 9300M GS, Quadro NVS 150M, Quadro NVS 160M
(II) Primary Device is: PCI 00@00:10:0
(WW) NV: Ignoring unsupported device 0x10de07e1 (GeForce 7100/nForce
630i) at 00@00:10:0
(EE) No devices detected.
Fatal server error:
no screens found
===========================
Hope that helps!
Cheers,
Chris
--
======================
"Never murder a man when he's
busy committing suicide."
-- Woodrow Wilson
11:16 a.m.
On Tue, 2008-11-18 at 09:56 -0700, Christopher A. Williams wrote:
On Tue, 2008-11-18 at 10:47 -0500, Adam Jackson wrote:
> On Sun, 2008-11-16 at 07:25 -0700, Christopher A. Williams wrote:
>
> > Motherboard:
> > eVGA e7100/630i
> > This MB uses nVidia onboard GeForce 7100 video with the nForce 630i
> > chipset. It also uses nVidia MCP73 High Definition Audio
>
> Do you have an X log showing what happens when you run the nv driver?
This is going to be long (due to the log length), but hopefully this
helps you out. Keep in mind that, by default (ie absent any xorg.conf
file or what system-config-display wants to set up), only the vesa
driver is used. I have to specifically say that I want to use the nv
driver.
...Correction to the above about vesa. It seems that, absent any
xorg.conf file, we DO try to load the nv driver. I think perhaps
system-config-display is just falling back to a vesa driver after
failing with nv, and is just having better luck at getting something
going.
With that in mind, here's a version of the Xorg.0.log file that's
generated when there is no xorg.conf file present:
=========================
X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.18-107.el5xen x86_64
Current Operating System: Linux spikehome.spikelan.local
2.6.27.5-109.fc10.x86_64 #1 SMP Thu Nov 13 20:12:05 EST 2008 x86_64
Build Date: 31 October 2008 01:39:18PM
Build ID: xorg-x11-server 1.5.2-12.fc10
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Nov 18 10:04:00 2008
(EE) Unable to locate/open config file
(II) Loader magic: 0x7ae540
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 4.1
X.Org XInput driver : 2.1
X.Org Server Extension : 1.1
X.Org Font Renderer : 0.6
(II) Loader running on linux
(--) using VT number 7
(--) PCI:*(0@0:16:0) nVidia Corporation GeForce 7100/nForce 630i rev
162, Mem @ 0xed000000/16777216, 0xd0000000/268435456,
0xee000000/16777216, BIOS @ 0x????????/131072
(==) Matched nv for the autoconfigured driver
New driver is "nv"
(==) Using default built-in configuration (30 lines)
(==) --- Start of built-in configuration ---
Section "Device"
Identifier "Builtin Default nv Device 0"
Driver "nv"
EndSection
Section "Screen"
Identifier "Builtin Default nv Screen 0"
Device "Builtin Default nv Device 0"
EndSection
Section "Device"
Identifier "Builtin Default fbdev Device 0"
Driver "fbdev"
EndSection
Section "Screen"
Identifier "Builtin Default fbdev Screen 0"
Device "Builtin Default fbdev Device 0"
EndSection
Section "Device"
Identifier "Builtin Default vesa Device 0"
Driver "vesa"
EndSection
Section "Screen"
Identifier "Builtin Default vesa Screen 0"
Device "Builtin Default vesa Device 0"
EndSection
Section "ServerLayout"
Identifier "Builtin Default Layout"
Screen "Builtin Default nv Screen 0"
Screen "Builtin Default fbdev Screen 0"
Screen "Builtin Default vesa Screen 0"
EndSection
(==) --- End of built-in configuration ---
(==) ServerLayout "Builtin Default Layout"
(**) |-->Screen "Builtin Default nv Screen 0" (0)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default nv Device 0"
(==) No monitor specified for screen "Builtin Default nv Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default fbdev Screen 0" (1)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default fbdev Device 0"
(==) No monitor specified for screen "Builtin Default fbdev Screen 0".
Using a default monitor configuration.
(**) |-->Screen "Builtin Default vesa Screen 0" (2)
(**) | |-->Monitor "<default monitor>"
(**) | |-->Device "Builtin Default vesa Device 0"
(==) No monitor specified for screen "Builtin Default vesa Screen 0".
Using a default monitor configuration.
(==) Automatically adding devices
(==) Automatically enabling devices
(==) No FontPath specified. Using compiled-in default.
(==) FontPath set to:
catalogue:/etc/X11/fontpath.d,
built-ins
(==) ModulePath set to "/usr/lib64/xorg/modules"
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable
AllowEmptyInput.
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or
directory)
(II) No APM support in BIOS or kernel
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) LoadModule: "extmod"
(II) Loading /usr/lib64/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension SELinux
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib64/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib64/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(==) AIGLX enabled
(==) Exporting typical set of GLX visuals
(II) Loading extension GLX
(II) LoadModule: "freetype"
(II) Loading /usr/lib64/xorg/modules/fonts//libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 1.5.2, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.6
(II) Loading font FreeType
(II) LoadModule: "dri"
(II) Loading /usr/lib64/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 1.0.0
ABI class: X.Org Server Extension, version 1.1
(II) Loading extension XFree86-DRI
(II) LoadModule: "nv"
(II) Loading /usr/lib64/xorg/modules/drivers//nv_drv.so
(II) Module nv: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 2.1.12
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 4.1
(II) LoadModule: "fbdev"
(II) Loading /usr/lib64/xorg/modules/drivers//fbdev_drv.so
(II) Module fbdev: vendor="X.Org Foundation"
compiled for 1.4.99.2, module version = 0.3.1
ABI class: X.Org Video Driver, version 4.0
(II) LoadModule: "vesa"
(II) Loading /usr/lib64/xorg/modules/drivers//vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
compiled for 1.4.99.905, module version = 1.3.0
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 4.1
(II) NV: driver for NVIDIA chipsets: RIVA 128, RIVA TNT, RIVA TNT2,
Unknown TNT2, Vanta, RIVA TNT2 Ultra, RIVA TNT2 Model 64,
Aladdin TNT2, GeForce 256, GeForce DDR, Quadro, GeForce2 MX/MX 400,
GeForce2 MX 100/200, GeForce2 Go, Quadro2 MXR/EX/Go,
GeForce2 Integrated GPU, GeForce2 GTS, GeForce2 Ti, GeForce2 Ultra,
Quadro2 Pro, GeForce4 MX 460, GeForce4 MX 440, GeForce4 MX 420,
GeForce4 MX 440-SE, GeForce4 440 Go, GeForce4 420 Go,
GeForce4 420 Go 32M, GeForce4 460 Go, Quadro4 550 XGL,
GeForce4 440 Go 64M, Quadro NVS, Quadro4 500 GoGL,
GeForce4 410 Go 16M, GeForce4 MX 440 with AGP8X,
GeForce4 MX 440SE with AGP8X, GeForce4 MX 420 with AGP8X,
GeForce4 MX 4000, GeForce4 448 Go, GeForce4 488 Go, Quadro4 580 XGL,
Quadro4 NVS 280 SD, Quadro4 380 XGL, Quadro NVS 50 PCI,
GeForce4 448 Go, GeForce4 MX Integrated GPU, GeForce3,
GeForce3 Ti 200, GeForce3 Ti 500, Quadro DCC, GeForce4 Ti 4600,
GeForce4 Ti 4400, GeForce4 Ti 4200, Quadro4 900 XGL, Quadro4 750 XGL,
Quadro4 700 XGL, GeForce4 Ti 4800, GeForce4 Ti 4200 with AGP8X,
GeForce4 Ti 4800 SE, GeForce4 4200 Go, Quadro4 700 GoGL,
Quadro4 980 XGL, Quadro4 780 XGL, GeForce FX 5800 Ultra,
GeForce FX 5800, Quadro FX 2000, Quadro FX 1000,
GeForce FX 5600 Ultra, GeForce FX 5600, GeForce FX 5600XT,
GeForce FX Go5600, GeForce FX Go5650, Quadro FX Go700,
GeForce FX 5200, GeForce FX 5200 Ultra, GeForce FX 5200,
GeForce FX 5200LE, GeForce FX Go5200, GeForce FX Go5250,
GeForce FX 5500, GeForce FX 5100, GeForce FX Go5200 32M/64M,
Quadro NVS 55/280 PCI, Quadro FX 500/600 PCI,
GeForce FX Go53xx Series, GeForce FX Go5100, GeForce FX 5900 Ultra,
GeForce FX 5900, GeForce FX 5900XT, GeForce FX 5950 Ultra,
GeForce FX 5900ZT, Quadro FX 3000, Quadro FX 700,
GeForce FX 5700 Ultra, GeForce FX 5700, GeForce FX 5700LE,
GeForce FX 5700VE, GeForce FX Go5700, GeForce FX Go5700,
Quadro FX Go1000, Quadro FX 1100, GeForce 6800 Ultra, GeForce 6800,
GeForce 6800 LE, GeForce 6800 XE, GeForce 6800 XT, GeForce 6800 GT,
GeForce 6800 GT, GeForce 6800 GS, GeForce 6800 XT, Quadro FX 4000,
GeForce 6800 GS, GeForce 6800, GeForce 6800 LE, GeForce 6800 XT,
GeForce Go 6800, GeForce Go 6800 Ultra, Quadro FX Go1400,
Quadro FX 3450/4000 SDI, Quadro FX 1400, GeForce 6600 GT,
GeForce 6600, GeForce 6600 LE, GeForce 6600 VE, GeForce Go 6600,
GeForce 6610 XL, GeForce Go 6600 TE/6200 TE, GeForce 6700 XL,
GeForce Go 6600, GeForce Go 6600 GT, Quadro FX 550, Quadro FX 550,
Quadro FX 540, GeForce 6200, GeForce 6500,
GeForce 6200 TurboCache(TM), GeForce 6200SE TurboCache(TM),
GeForce 6200 LE, GeForce Go 6200, Quadro NVS 285, GeForce Go 6400,
GeForce Go 6200, GeForce Go 6400, GeForce 6250, GeForce 6800,
GeForce 6800 LE, GeForce 6800 GT, GeForce 6800 XT, GeForce 6200,
GeForce 6200 A-LE, GeForce 7800 GTX, GeForce 7800 GTX,
GeForce 7800 GT, GeForce 7800 GS, GeForce 7800 SLI, GeForce Go 7800,
GeForce Go 7800 GTX, Quadro FX 4500, GeForce 7300 LE,
GeForce 7300 SE, GeForce Go 7200, GeForce Go 7300, GeForce Go 7400,
GeForce Go 7400 GS, Quadro NVS 110M, Quadro NVS 120M, Quadro FX 350M,
GeForce 7500 LE, Quadro FX 350, GeForce 7300 GS, GeForce 7600 GT,
GeForce 7600 GS, GeForce 7300 GT, GeForce 7600 LE, GeForce 7300 GT,
GeForce Go 7700, GeForce Go 7600, GeForce Go 7600 GT,
Quadro NVS 300M, GeForce Go 7900 SE, Quadro FX 550M, Quadro FX 560,
GeForce 7900 GTX, GeForce 7900 GT, GeForce 7900 GS,
GeForce Go 7900 GS, GeForce Go 7900 GTX, Quadro FX 2500M,
Quadro FX 1500M, Quadro FX 5500, Quadro FX 3500, Quadro FX 1500,
Quadro FX 4500 X2, GeForce 6150, GeForce 6150 LE, GeForce 6100,
GeForce Go 6150, GeForce Go 6100, GeForce 8800 GTX, GeForce 8800 GTS,
GeForce 8800 Ultra, Quadro FX 5600, Quadro FX 4600, GeForce 8600 GTS,
GeForce 8600 GT, GeForce 8600 GT, GeForce 8600 GS, GeForce 8400 GS,
GeForce 9500M GS, GeForce 8600M GT, GeForce 9650M GS,
GeForce 8700M GT, Quadro FX 370, Quadro NVS 320M, Quadro FX 570M,
Quadro FX 1600M, Quadro FX 570, Quadro FX 1700, GeForce 8400 SE,
GeForce 8500 GT, GeForce 8400 GS, GeForce 8300 GS, GeForce 8400 GS,
GeForce 8600M GS, GeForce 8400M GT, GeForce 8400M GS,
GeForce 8400M G, Quadro NVS 140M, Quadro NVS 130M, Quadro NVS 135M,
GeForce 9400 GT, Quadro FX 360M, GeForce 9300M G, Quadro NVS 290,
GeForce GTX 280, GeForce GTX 260, GeForce 8800 GTS 512,
GeForce 8800 GT, GeForce 9800 GX2, GeForce 8800 GS,
GeForce 8800M GTS, GeForce 8800M GTX, GeForce 8800 GS,
GeForce 9600 GSO, GeForce 8800 GT, GeForce 9800 GTX,
GeForce 9800 GTK+, GeForce 9800 GT, Quadro FX 3700, Quadro FX 3600M,
GeForce 9600 GT, GeForce 9600 GS, GeForce 9800M GTS,
GeForce 9700M GTS, GeForce 9800M GTS, GeForce 9500 GT,
GeForce 9600M GT, GeForce 9600M GS, GeForce 9600M GT,
GeForce 9500M G, GeForce 9300 GS, GeForce 8400 GS, GeForce 9300M GS,
GeForce 9200M GS, GeForce 9300M GS, Quadro NVS 150M, Quadro NVS 160M
(II) FBDEV: driver for framebuffer: fbdev
(II) VESA: driver for VESA chipsets: vesa
(II) Primary Device is: PCI 00@00:10:0
(WW) NV: Ignoring unsupported device 0x10de07e1 (GeForce 7100/nForce
630i) at 00@00:10:0
(WW) Falling back to old probe method for fbdev
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/lib64/xorg/modules/linux//libfbdevhw.so
(II) Module fbdevhw: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 0.0.2
ABI class: X.Org Video Driver, version 4.1
(EE) open /dev/fb0: No such file or directory
(WW) Falling back to old probe method for vesa
(EE) No devices detected.
Fatal server error:
no screens found
=====================
Looks like it tries to load nv, fails because it doesn't like something
about my on-board video, and then tries to fall back to vesa and fails
again.
Hope that helps a little more!
Cheers,
Chris
--
==============================
"If you are calm while all around you is chaos,
then you probably haven't fully understood
the magnitude of the situation."
--Unknown
11:43 a.m.
New subject: The nv driver and GeForce 7100 (Was: F10 on Homebuilt Box - Absolutely Brutal...!!!!)
On Tue, 2008-11-18 at 10:16 -0700, Christopher A. Williams wrote:
> > > Motherboard:
> > > eVGA e7100/630i
> > > This MB uses nVidia onboard GeForce 7100 video with the nForce 630i
> > > chipset. It also uses nVidia MCP73 High Definition Audio
> >
> > Do you have an X log showing what happens when you run the nv driver?
...Correction to the above about vesa. It seems that, absent any
xorg.conf file, we DO try to load the nv driver. I think perhaps
system-config-display is just falling back to a vesa driver after
failing with nv, and is just having better luck at getting something
going.
With that in mind, here's a version of the Xorg.0.log file that's
generated when there is no xorg.conf file present:
=========================
X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.18-107.el5xen x86_64
<snip...>
(II) NV: driver for NVIDIA chipsets: RIVA 128, RIVA TNT, RIVA TNT2,
<snip...>
GeForce 6200 A-LE, GeForce 7800 GTX, GeForce 7800 GTX,
<snip...>
(II) Primary Device is: PCI 00@00:10:0
(WW) NV: Ignoring unsupported device 0x10de07e1 (GeForce 7100/nForce
630i) at 00@00:10:0
(WW) Falling back to old probe method for fbdev
Unsupported??? (Big, Texas
"Hunnnh...?")
After looking at this log in detail (and googling to see others with the
same card plus F9/10 and other distros having the identical problem), I
guess the real question to ask is why the nv driver seems to support
every nVidia card out there _except_ the GeForce 7100 series.
Oversight? If intentional, why, and what can be done to include it?
Happy to bugzilla this one as needed...
Cheers,
Chris
--
=========================================
"In theory there is no difference between theory and practice.
In practice there is."
--Yogi Berra
3:10 p.m.
New subject: The nv driver and GeForce 7100 (Was: F10 on Homebuilt Box - Absolutely Brutal...!!!!)
On Tue, 2008-11-18 at 10:43 -0700, Christopher A. Williams wrote:
> (II) Primary Device is: PCI 00@00:10:0
> (WW) NV: Ignoring unsupported device 0x10de07e1 (GeForce 7100/nForce
> 630i) at 00@00:10:0
> (WW) Falling back to old probe method for fbdev
Unsupported??? (Big, Texas "Hunnnh...?")
After looking at this log in detail (and googling to see others with the
same card plus F9/10 and other distros having the identical problem), I
guess the real question to ask is why the nv driver seems to support
every nVidia card out there _except_ the GeForce 7100 series.
Oversight? If intentional, why, and what can be done to include it?
Not an oversight, utterly intentional. You can thank nvidia for this
one. Apparently it's slightly weirder than your normal geforce 7, and
they haven't written the code to support it in the nv driver yet (nor
told us what needs doing).
We _ought_ to fall straight back to vesa if we can. I've stared at this
code a bit and not figured out why we're not falling back properly, but
I guess I'll stare more.
If you're feeling adventurous you could hack out the bit of the nv
driver that rejects that chip and then bang on things until it works,
but it's not the sort of thing one can be hand-held through, you really
will have to poke blindly until it works...
- ajax
4:47 p.m.
New subject: The nv driver and GeForce 7100 (Was: F10 on Homebuilt Box - Absolutely Brutal...!!!!)
On Tue, 2008-11-18 at 16:10 -0500, Adam Jackson wrote:
On Tue, 2008-11-18 at 10:43 -0700, Christopher A. Williams wrote:
> > (II) Primary Device is: PCI 00@00:10:0
> > (WW) NV: Ignoring unsupported device 0x10de07e1 (GeForce 7100/nForce
> > 630i) at 00@00:10:0
> > (WW) Falling back to old probe method for fbdev
> Unsupported??? (Big, Texas "Hunnnh...?")
>
> After looking at this log in detail (and googling to see others with the
> same card plus F9/10 and other distros having the identical problem), I
> guess the real question to ask is why the nv driver seems to support
> every nVidia card out there _except_ the GeForce 7100 series.
>
> Oversight? If intentional, why, and what can be done to include it?
Not an oversight, utterly intentional. You can thank nvidia for this
one. Apparently it's slightly weirder than your normal geforce 7, and
they haven't written the code to support it in the nv driver yet (nor
told us what needs doing).
We _ought_ to fall straight back to vesa if we can. I've stared at this
code a bit and not figured out why we're not falling back properly, but
I guess I'll stare more.
If you're feeling adventurous you could hack out the bit of the nv
driver that rejects that chip and then bang on things until it works,
but it's not the sort of thing one can be hand-held through, you really
will have to poke blindly until it works...
So nVidia strikes again. Sad... Well, as long as we can successfully
fall back to vesa long enough to install the proprietary "nvidia"
driver, it's at least not a show stopper those who are less determined
than I to make it work.
Now - as to the nv driver, someone using it with this card on F9 says it
works if you:
- Booted without "rhgb" on the grub kernel line
- Configured the system (fedora initial configuration)
- ctrl-alt-f1
- login as root
- init 3
- change xorg.conf, device driver to "nv" (originally detected vesa).
- # su - rodolfo (thats my daily username)
- $ startx -- -ignoreABI (started fine)
- end that gnome session
- init 5
I don't see why this would work, but the two people on this mailing list
say that it does. I haven't tried it (and probably won't since I have
the proprietary driver working just fine now). Perhaps it gives a clue
to the weirdness of the GeForce 7100. Link to where I found this is:
https://www.redhat.com/archives/fedora-list/2008-May/msg01891.html
I have another idea that might help troubleshoot falling back to vesa
though. I'm assuming that since system-config-display launches a session
of X on its own, there must be a log of what happens somewhere. I'll see
what I can come up with...
Cheers,
Chris
--
====================================
"Ninety-nine percent of the failures
come from people who have the habit
of making excuses."
--George Washington Carver
10:18 a.m.
New subject: The nv driver and GeForce 7100 (Was: F10 on Homebuilt Box - Absolutely Brutal...!!!!)
On Tue, 2008-11-18 at 16:10 -0500, Adam Jackson wrote:
On Tue, 2008-11-18 at 10:43 -0700, Christopher A. Williams wrote:
> > (II) Primary Device is: PCI 00@00:10:0
> > (WW) NV: Ignoring unsupported device 0x10de07e1 (GeForce 7100/nForce
> > 630i) at 00@00:10:0
> > (WW) Falling back to old probe method for fbdev
> Unsupported??? (Big, Texas "Hunnnh...?")
>
> After looking at this log in detail (and googling to see others with the
> same card plus F9/10 and other distros having the identical problem), I
> guess the real question to ask is why the nv driver seems to support
> every nVidia card out there _except_ the GeForce 7100 series.
>
> Oversight? If intentional, why, and what can be done to include it?
Not an oversight, utterly intentional. You can thank nvidia for this
one. Apparently it's slightly weirder than your normal geforce 7, and
they haven't written the code to support it in the nv driver yet (nor
told us what needs doing).
We _ought_ to fall straight back to vesa if we can. I've stared at this
code a bit and not figured out why we're not falling back properly, but
I guess I'll stare more.
If you're feeling adventurous you could hack out the bit of the nv
driver that rejects that chip and then bang on things until it works,
but it's not the sort of thing one can be hand-held through, you really
will have to poke blindly until it works...
Alright, I've got a (bad) fix for this. Not the final fix I want to
use, but I'd at least appreciate some testing from people with this kind
of nv driver failure. It's actually an X server fix, and it can be
found here:
http://koji.fedoraproject.org/scratch/ajax/task_940170/
Run X, either with no config file or with nv selected as the driver in
the config, and then verify in the X log that we fell back to vesa. I
don't have one of the affected nv chips so I had to synthesize the
failure by hacking the nv driver, but it should work. Probably.
- ajax
12:05 p.m.
New subject: The nv driver and GeForce 7100 (Was: F10 on Homebuilt Box - Absolutely Brutal...!!!!)
On Wed, 2008-11-19 at 11:18 -0500, Adam Jackson wrote:
<snip...>
Alright, I've got a (bad) fix for this. Not the final fix I want
to
use, but I'd at least appreciate some testing from people with this kind
of nv driver failure. It's actually an X server fix, and it can be
found here:
http://koji.fedoraproject.org/scratch/ajax/task_940170/
Run X, either with no config file or with nv selected as the driver in
the config, and then verify in the X log that we fell back to vesa. I
don't have one of the affected nv chips so I had to synthesize the
failure by hacking the nv driver, but it should work. Probably.
OK - I tested this out as prescribed. Here are my results:
Running with no xorg.conf file:
We try to load the nv driver and fail, then we SUCCESSFULLY fall back to
vesa! Yaaaaaaaayyyyyyyy!!!!!
Running with xorg.conf file that is _specifically_ set to use the nv
driver:
We try to load the nv driver and fail. No fallback to vesa. If we tried
to fall back to vesa, it didn't work.
Overall, I would call this a success.
Keeping in mind that we won't have an xorg.conf file by default, the fix
works as currently implemented (and should therefore work on the Live CD
and Install DVD). Explicitly configuring the nv driver, IMHO, _should_
produce a failure since it isn't supported on this card.
Given that the nv driver is known not to support this specific card, I
would perhaps just consider throwing some sort of error message which
makes it blatantly clear from the start that this is the case (same for
any other non-supported cards). Perhaps adding some professionally
worded verbiage that we should appeal to nVidia to help change that
would also be appropriate. From a usability perspective, we shouldn't
need to go digging through the Xorg error logs to figure all of that
out.
One more thing to consider: If X does fail to load, we need to do
something other than sit at a blank screen doing nothing - especially on
the Live images. It makes us look silly. I think what may be happening
here is that X is failing, but we're going ahead and trying to load gdm
anyway. That doesn't make a lot of sense. If X fails to start properly,
it should exit and gdm should not be allowed to start. We should allow
the X failure error message to fall through and then drop to a text mode
command prompt. This has the added benefit of giving people the
opportunity to fix problems with X and then trying again.
Let me know when you want to test the final fix you do want to use.
Cheers,
Chris
--
=========================================
"In theory there is no difference between theory and practice.
In practice there is."
--Yogi Berra
12:23 p.m.
New subject: The nv driver and GeForce 7100 (Was: F10 on Homebuilt Box - Absolutely Brutal...!!!!)
On Wed, 2008-11-19 at 11:05 -0700, Christopher A. Williams wrote:
OK - I tested this out as prescribed. Here are my results:
Running with no xorg.conf file:
We try to load the nv driver and fail, then we SUCCESSFULLY fall back to
vesa! Yaaaaaaaayyyyyyyy!!!!!
Running with xorg.conf file that is _specifically_ set to use the nv
driver:
We try to load the nv driver and fail. No fallback to vesa. If we tried
to fall back to vesa, it didn't work.
Overall, I would call this a success.
Keeping in mind that we won't have an xorg.conf file by default, the fix
works as currently implemented (and should therefore work on the Live CD
and Install DVD). Explicitly configuring the nv driver, IMHO, _should_
produce a failure since it isn't supported on this card.
Yeah, I meant it to act this way when I wrote the patch, I just
described the test scenario wrong. Sorry about that.
And yes, I agree, explicitly asking for nv should fail, this is really
just about fixing the magic setup heuristic.
Thanks for testing! I should have an updated patch shortly.
- ajax
12:55 p.m.
New subject: The nv driver and GeForce 7100 (Was: F10 on Homebuilt Box - Absolutely Brutal...!!!!)
does system-config-display know about that specific card not being
supported by nv
if this is true then this fix is perfect
1:49 p.m.
New subject: The nv driver and GeForce 7100 (Was: F10 on Homebuilt Box - Absolutely Brutal...!!!!)
On Wed, 2008-11-19 at 20:55 +0200, Muayyad AlSadi wrote:
does system-config-display know about that specific card not being
supported by nv
if this is true then this fix is perfect
In my experience, yes. Executing system-config-display --reconfig will
automatically configure this card using the vesa driver.
Cheers,
Chris
--
===================================
Warning: You are logged into reality as the root user...
--Unknown
6:12 a.m.
On Tue, Nov 18, 2008 at 5:47 PM, Adam Jackson <ajax(a)redhat.com> wrote:
On Sun, 2008-11-16 at 07:25 -0700, Christopher A. Williams wrote:
> Motherboard:
> eVGA e7100/630i
> This MB uses nVidia onboard GeForce 7100 video with the nForce 630i
> chipset. It also uses nVidia MCP73 High Definition Audio
Do you have an X log showing what happens when you run the nv driver?
- ajax
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
The nv driver doesn't support your hardware.
--
Aioanei Rares
schaiba(a)fedoraproject.org
"China is a big country, inhabited by many Chinese." --Charles de Gaulle
7:27 a.m.
On Wed, 2008-11-19 at 14:12 +0200, Aioanei Rares wrote:
On Tue, Nov 18, 2008 at 5:47 PM, Adam Jackson <ajax(a)redhat.com> wrote:
On Sun, 2008-11-16 at 07:25 -0700, Christopher A. Williams
wrote:
> Motherboard:
> eVGA e7100/630i
> This MB uses nVidia onboard GeForce 7100 video with the
nForce 630i
> chipset. It also uses nVidia MCP73 High Definition Audio
Do you have an X log showing what happens when you run the nv
driver?
- ajax
--
The nv driver doesn't support your hardware.
--
Aioanei Rares
schaiba(a)fedoraproject.org
"China is a big country, inhabited by many Chinese." --Charles de
Gaulle
...ummm I think we figured that part out already.
Where we are now is trying to figure out why we don't fall back
correctly to vesa mode without an xorg.conf file so that we can complete
a graphical install. That allows us to then install the proprietary
"nvidia" driver, which is supported and works great.
Care to contribute there? ...Or perhaps you can help nVidia see the
light about providing the documentation needed for the nv driver to
support the GeForce 7100 series?
Speaking of falling back to vesa mode, it would seem to me that, since
system-config-display --reconfig _does_ correctly fall back vesa mode on
this card (and sets up an xorg.conf file that also successfully uses
it), perhaps the solution lies somewhere in that code as an example.
Possible...?
--
====================================
"If you get to thinkin' you're a
person of some influence, try
orderin' someone else's dog around."
--Cowboy Wisdom
10:55 a.m.
Speaking of falling back to vesa mode...
At the risk of seeming radical, why not just always run anaconda with
xdriver=vesa by default? Since anaconda no longer generates any kind
of an xorg.conf file to "pollute" the install, why not just always use
the driver that always seems to work right? (Unless you are planning
some sort of 3D opengl installer enhancements soon :-).
12:17 p.m.
On Wed, 2008-11-19 at 16:55 +0000, Tom Horsley wrote:
> Speaking of falling back to vesa mode...
At the risk of seeming radical, why not just always run anaconda with
xdriver=vesa by default? Since anaconda no longer generates any kind
of an xorg.conf file to "pollute" the install, why not just always use
the driver that always seems to work right? (Unless you are planning
some sort of 3D opengl installer enhancements soon :-).
Three reasons.
vesa doesn't always work. It will work even less often in the future,
since Vista prohibits use of VBE services at runtime (removing some
incentive for vendors to keep it working), and since EFI removes VBE
altogether. And even for machines where it does do something, we're not
really guaranteed that it will do what we're hoping for. I've seen
BIOSes with no 800x600 mode, or with no 24bpp modes.
Second, by Occam's Razor, we're trying to keep the install environment
as similar to the runtime environment as we can. Otherwise you get bugs
like "I have to install in text mode, but then gdm works fine", or
worse, "graphical install worked but then gdm didn't show up".
Depending on the reporter, one or the other might be below their pain
threshold and thus not get reported, but if _both_ break, then we're
sure we'll hear about it. (Or they'll just give up and run Windows, I
suppose.)
Third, and this is more of a petty code reason and a consequence of
reason #2, xdriver= controls both the X driver anaconda uses _and_ the X
driver it writes out to xorg.conf. If you say xdriver=radeon you'll get
a config file that mentions radeon. The logic here is akin to the logic
for kernel updates to preserve your /proc/cmdline when writing the new
grub.conf. If you needed it to boot _this_ kernel, you'll probably need
it to boot the next one; if you need xdriver= to make graphical install
work, you'll probably need it to make runtime X work.
#3 (and to some extend #2) we could change in the code, but I actually
feel pretty strongly about the philosophical bits of #1 and #2.
- ajax
6:26 p.m.
Christopher A. Williams wrote:
I decided to take the plunge and install F10 x86_64 preview on my
main
system at home. This was absolutely the WORST and MOST BRUTAL
installation of Fedora I have ever experienced!!! What in wide world of
sports is going on here??? I was up until midnight trying to get my
system working again.
Had I been a newbie, my impression on Fedora and Linux would have been
that it truly sucks big time. Have I gotten anyone's attention yet...?
...Good. Here's what's wrong and (hopefully) what's needed to fix it.
First here's a summary of my system config (output of lshal available):
Motherboard:
eVGA e7100/630i
This MB uses nVidia onboard GeForce 7100 video with the nForce 630i
chipset. It also uses nVidia MCP73 High Definition Audio
CPU: Intel 2.4GHZ Core2 Quad
4GB RAM
320GB Western Digital SATA drive (WDC_WD3200AAKS)
Monitor: Acer P243W (connected via DVI cable)
OK - Here we go...
Installation was a nightmare (as witnessed by a friend who also
frequents this list). The main thing that was wrong was video. Simply
put, it just doesn't work - and to the point that the Live CD is
unusable and the Install DVD will only install in text mode. What I
found (after a lot of troubleshooting) was that F10 in the default
configuration just doesn't recognize the nVidia card correctly.
That's a good clue you shouldn't install it. The latest hardware is
generally problematic.
I have a brand-new HP SFF at work, I plan to install Debian on it. First
thing I did was boot a Knoppix DVD.
Everything works[1], so Debian's a goer (maybe not Debian Stable, but
Debian Something).
[1] Come to think of it, I don't think sound does. Sound doesn't matter
for this system.
If I was going to run Fedora or Ubuntu (actually, not silly) or openSUSE
then I'd check it out with a corresponding live image.
--
Cheers
John
-- spambait
1aaaaaaa(a)coco.merseine.nu Z1aaaaaaa(a)coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
5630
days inactive
5633
days old
35 comments
15 participants
participants (15)
-
Adam Jackson -
Bruno Wolff III -
Christopher A Williams -
drago01 -
Ignacio Vazquez-Abrams -
John Summerfield -
Mads Kiilerich -
Michal Jaegermann -
Muayyad AlSadi -
Patrick O'Callaghan -
Rares Aioanei -
Robert L Cochran -
Scott Robbins -
Tom Diehl -
Tom Horsley