Re: F10 -> F11 X server problem with /dev/fb0
On Mon, Jun 29, 2009 at 12:16 PM, Peter J. Stieber wrote: > AF = Aldo Foot > AF>> One way to troubleshoot is to create a > AF>> new Xorg.conf and change the Driver line > AF>> to "vesa". You need to boot into runlevel 3, > > PS = Peter Stieber > PS> I always have inittab setup to boot to run > PS> level 3, then type startx after logging in. > > AF>> log in as root and do "Xorg -configure", > AF>> which will create a new config file at > AF>> /root/xorg.conf.new. To use it you'll > AF>> have to move it to /etc/Xorg.conf. > > PS> I did this and I have attached the resulting > PS> xorg.conf file. > PS> > PS> When I ran startx, it didn't work. I've > PS> attached the xorg log file. > > AF>> In it find the Device block, like: > AF>> > AF>> Section "Device" > AF>> Driver "vesa" > AF>> EndSection > > PS> I'll try this next. > > I finally got my local X server to work, but changing the Driver vesa was > not enough. Here's the xorg.conf file I used to get a display... > > Section "Screen" > Identifier "Screen0" > Device "Card0" > Monitor "Monitor0" > DefaultDepth 24 > SubSection "Display" > Depth 24 > Modes "1280x1024" > EndSubSection > EndSection > > Section "Monitor" > Identifier "Monitor0" > HorizSync 36-52 > VertRefresh 36-60 > EndSection > > Section "Device" > Identifier "Card0" > Driver "vesa" > EndSection > > I had to put the monitor H sync and V refresh rates in the file for this to > work. I did this because I saw 36-0 values in the log and thought it was > strange. Is this worthy of a bug report? > > So I guess the initial problem was, the new xorg nouveau NVIDIA driver > doesn't work with my nVidia Corporation NV44 [GeForce 6200 LE]. Should I > file a bug report with Fedora or xorg? > > Pete I believe I've read threads of people mentioning that they could no use the xorg.conf, but with a bit of effort you got it going. Nicely done. Filing a bug would be informative to the folks who work on the nouveau driver. ~af -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F10 -> F11 X server problem with /dev/fb0
AF = Aldo Foot AF>> One way to troubleshoot is to create a AF>> new Xorg.conf and change the Driver line AF>> to "vesa". You need to boot into runlevel 3, PS = Peter Stieber PS> I always have inittab setup to boot to run PS> level 3, then type startx after logging in. AF>> log in as root and do "Xorg -configure", AF>> which will create a new config file at AF>> /root/xorg.conf.new. To use it you'll AF>> have to move it to /etc/Xorg.conf. PS> I did this and I have attached the resulting PS> xorg.conf file. PS> PS> When I ran startx, it didn't work. I've PS> attached the xorg log file. AF>> In it find the Device block, like: AF>> AF>> Section "Device" AF>> Driver "vesa" AF>> EndSection PS> I'll try this next. I finally got my local X server to work, but changing the Driver vesa was not enough. Here's the xorg.conf file I used to get a display... Section "Screen" Identifier "Screen0" Device "Card0" Monitor"Monitor0" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1280x1024" EndSubSection EndSection Section "Monitor" Identifier "Monitor0" HorizSync36-52 VertRefresh 36-60 EndSection Section "Device" Identifier "Card0" Driver "vesa" EndSection I had to put the monitor H sync and V refresh rates in the file for this to work. I did this because I saw 36-0 values in the log and thought it was strange. Is this worthy of a bug report? So I guess the initial problem was, the new xorg nouveau NVIDIA driver doesn't work with my nVidia Corporation NV44 [GeForce 6200 LE]. Should I file a bug report with Fedora or xorg? Pete -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F10 -> F11 X server problem with /dev/fb0
AF = Aldo Foot AF> One way to troubleshoot is to create a AF> new Xorg.conf and change the Driver line AF> to "vesa". You need to boot into runlevel 3, I always have inittab setup to boot to run level 3, then type startx after logging in. AF> log in as root and do "Xorg -configure", AF> which will create a new config file at AF> /root/xorg.conf.new. To use it you'll AF> have to move it to /etc/Xorg.conf. I did this and I have attached the resulting xorg.conf file. When I ran startx, it didn't work. I've attached the xorg log file. AF> In it find the Device block, like: AF> AF> Section "Device" AF> Driver "vesa" AF> EndSection I'll try this next. AF> Note that there's no longer need for an Xorg.conf AF> since support for video cards is now more AF> extensive[1]. I didn't have one on this box. I administer 16 different Fedora boxes and none of them have an xorg.conf file. 12 of them run x86_64 qne the rest run the appropriate 32-bit version of Fedora. I don't use any non-Fedora repos. I tried preupgrade on one of the x86_64 boxes and it didn't work, but fortunately F10 still worked. For the machine I'm discussing in this thread, I use the F11 x86_64 network install CD to upgrade the system. Obviously the xdriver update is causing me problems. The rest are still running F10. The others have ATI graphics card so I probably will not run into the same problems. AF> I have an nvidia card in my 32bit system and AF> never had issues, but everyone's setup AF> is different. Try the Xorg archives[2] and AF> mine for info there. AF> AF> [1] http://docs.fedoraproject.org/release-notes/f11/en-US/ AF> [2] http://lists.freedesktop.org/archives/xorg/ AF> AF> good luck, Thanks, Pete Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice"Mouse0" "CorePointer" InputDevice"Keyboard0" "CoreKeyboard" EndSection Section "Files" ModulePath "/usr/lib64/xorg/modules" FontPath "catalogue:/etc/X11/fontpath.d" FontPath "built-ins" EndSection Section "Module" Load "dri2" Load "extmod" Load "record" Load "dri" Load "dbe" Load "glx" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName"Monitor Model" EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, : float, : "True"/"False", ### : "String", : " Hz/kHz/MHz" ### [arg]: arg optional #Option "SWcursor" # [] #Option "HWcursor" # [] #Option "NoAccel" # [] #Option "ShadowFB" # [] #Option "VideoKey" # #Option "FlatPanel" # [] #Option "FPDither" # [] #Option "FPScale" # [] #Option "FPTweak" # #Option "CBLocation"# #Option "CBSize"# #Option "Randr12" # [] #Option "ScalingMode" # #Option "EXAPixmaps"# [] Identifier "Card0" Driver "nouveau" VendorName "nVidia Corporation" BoardName "NV44 [GeForce 6200 LE]" BusID "PCI:1:0:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor"Monitor0" SubSection "Display" Viewport 0 0 Depth 1 EndSubSection SubSection "Display" Viewport 0 0 Depth 4 EndSubSection SubSection "Display" Viewport 0 0 Depth 8 EndSubSection SubSection "Display" Viewport 0 0 Depth 15 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection X.Org X Server 1.6.1.901 (1.6.2 RC 1) Release Date: 2009-5-8 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.18-128.1.6.el5 x86_64 Current Operating System: Linux mrburns.toyon.corp 2.6.29.4-167.fc11.x86_64 #1 SMP Wed May 27 17:27:08 EDT 2009 x86_64 Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet Build Date: 18 May 2009 02:47:15PM Build ID: xorg-x11-serv
Re: F10 -> F11 X server problem with /dev/fb0
On Thu, Jun 25, 2009 at 8:45 AM, Peter J. Stieber wrote: > AF = Aldo Foot > AF>>> http://tldp.org/HOWTO/Framebuffer-HOWTO-5.html > AF>>> > AF>>> "You'll need to create the framebuffer device in /dev. > AF>>> You need one per framebuffer device, so all you need > AF>>> to do is to type in mknod /dev/fb0 c 29 0 for the first > AF>>> one. Subsequent ones would be in multiples of 32, so for > AF>>> example to create /dev/fb1, you would need to type in > AF>>> mknod /dev/fb1 c 29 32, and so on up to the eighth > AF>>> framebuffer device (mknod /dev/fb7 c 29 224)" > > PS = Pete Stieber > PS>> I already have a /dev/fb that I didn't create... > PS>> > PS>> crw---. 1 pstieber root 29, 0 2009-06-24 08:15 fb > PS>> > PS>> Should I still create /dev/fb0? > > AF> I would since the error message you get points to > AF> the specific filename /dev/fb0. But note the "29, 0" > AF> for /dev/fb, which means for a second one it would be > AF> "29, 32". If you feel brave delete the /dev/fb and > AF> create a new /dev/fb0. I wonder what would happen if > AF> you rename /dev/fb to /dev/fb0. Just be cautious and > AF> try whatever you're comfortable with. > > I tried > > # mv /dev/fb /dev/fb0 > > It didn't work, so I moved it back to fb and I tried to create fb0... > > # mv /dev/fb0 /dev/fb > # mknod /dev/fb0 c 29 32 > > startx still report > > (EE) open /dev/fb0: No such device > > Xwindows is trying to use the new nouveau NVIDIA driver. > > Maybe there is a problem with the driver? One way to troubleshoot is to create a new Xorg.conf and change the Driver line to "vesa". You need to boot into runlevel 3, log in as root and do "Xorg -configure", which will create a new config file at /root/xorg.conf.new. To use it you'll have to move it to /etc/Xorg.conf. In it find the Device block, like: Section "Device" Driver "vesa" EndSection Note that there's no longer need for an Xorg.conf since support for video cards is now more extensive[1]. I have an nvidia card in my 32bit system and never had issues, but everyone's setup is different. Try the Xorg archives[2] and mine for info there. [1] http://docs.fedoraproject.org/release-notes/f11/en-US/ [2] http://lists.freedesktop.org/archives/xorg/ good luck, ~af -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F10 -> F11 X server problem with /dev/fb0
AF = Aldo Foot AF>>> http://tldp.org/HOWTO/Framebuffer-HOWTO-5.html AF>>> AF>>> "You'll need to create the framebuffer device in /dev. AF>>> You need one per framebuffer device, so all you need AF>>> to do is to type in mknod /dev/fb0 c 29 0 for the first AF>>> one. Subsequent ones would be in multiples of 32, so for AF>>> example to create /dev/fb1, you would need to type in AF>>> mknod /dev/fb1 c 29 32, and so on up to the eighth AF>>> framebuffer device (mknod /dev/fb7 c 29 224)" PS = Pete Stieber PS>> I already have a /dev/fb that I didn't create... PS>> PS>> crw---. 1 pstieber root 29, 0 2009-06-24 08:15 fb PS>> PS>> Should I still create /dev/fb0? AF> I would since the error message you get points to AF> the specific filename /dev/fb0. But note the "29, 0" AF> for /dev/fb, which means for a second one it would be AF> "29, 32". If you feel brave delete the /dev/fb and AF> create a new /dev/fb0. I wonder what would happen if AF> you rename /dev/fb to /dev/fb0. Just be cautious and AF> try whatever you're comfortable with. I tried # mv /dev/fb /dev/fb0 It didn't work, so I moved it back to fb and I tried to create fb0... # mv /dev/fb0 /dev/fb # mknod /dev/fb0 c 29 32 startx still report (EE) open /dev/fb0: No such device Xwindows is trying to use the new nouveau NVIDIA driver. Maybe there is a problem with the driver? Pete -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F10 -> F11 X server problem with /dev/fb0
On Wed, Jun 24, 2009 at 6:02 PM, Peter J. Stieber wrote: <...snip...> > AF> http://tldp.org/HOWTO/Framebuffer-HOWTO-5.html > AF> > AF> "You'll need to create the framebuffer device in /dev. > AF> You need one per framebuffer device, so all you need > AF> to do is to type in mknod /dev/fb0 c 29 0 for the first > AF> one. Subsequent ones would be in multiples of 32, so for > AF> example to create /dev/fb1, you would need to type in > AF> mknod /dev/fb1 c 29 32, and so on up to the eighth > AF> framebuffer device (mknod /dev/fb7 c 29 224)" > > I already have a /dev/fb that I didn't create... > > crw---. 1 pstieber root 29, 0 2009-06-24 08:15 fb > > Should I still create /dev/fb0? I would since the error message you get points to the specific filename /dev/fb0. But note the "29, 0" for /dev/fb, which means for a second one it would be "29, 32". If you feel brave delete the /dev/fb and create a new /dev/fb0. I wonder what would happen if you rename /dev/fb to /dev/fb0. Just be cautious and try whatever you're comfortable with. <...snip...> > I used a F11 network install CD to update. Probably most people do the same. Network installs (in particular NFS) are very efficient. > Thanks for the help Aldo, > Pete you're welcome. ~af -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F10 -> F11 X server problem with /dev/fb0
PS = Pete Stieber PS>> I just upgraded an x86_64 Fedora 10 system to PS>> Fedora 11. Now when I run startx I get the PS>> following complaint. PS>> PS>> (EE) open /dev/fb0: No such file or directory PS>> PS>> Then the screen output says... PS>> PS>> Fatal server error: PS>> Detected GPU lockup PS>> PS>> My Fedora 10 system was using the Fedora Xvfb PS>> package to perform offline processing. I stopped PS>> that server, but I'm still getting the error. PS>> PS>> $ lspci PS>> ... PS>> 01:00.0 VGA compatible controller: nVidia Corporation NV44 PS>> [GeForce 6200 LE] (rev a1) PS>> ... PS>> PS>> I'm wondering how to go about fixing this. I PS>> know this probably isn't enough to "go on", but PS>> just ask, and I'll provide more information. AF = Aldo Foot AF> Hmm... this is just a pointer. At least you'll AF> know what /dev/fb0 is for. AF> AF> http://tldp.org/HOWTO/Framebuffer-HOWTO-3.html AF> AF> "A framebuffer device is an abstraction for the AF> graphic hardware. It represents the frame buffer AF> of some video hardware, and allows application AF> software to access the graphic hardware through a AF> well-defined interface, so that the software doesn't AF> need to know anything about the low-level interface AF> stuff [Taken from Geert Uytterhoeven's AF> framebuffer.txt in the linux kernel sources]" AF> AF> http://tldp.org/HOWTO/Framebuffer-HOWTO-5.html AF> AF> "You'll need to create the framebuffer device in /dev. AF> You need one per framebuffer device, so all you need AF> to do is to type in mknod /dev/fb0 c 29 0 for the first AF> one. Subsequent ones would be in multiples of 32, so for AF> example to create /dev/fb1, you would need to type in AF> mknod /dev/fb1 c 29 32, and so on up to the eighth AF> framebuffer device (mknod /dev/fb7 c 29 224)" I already have a /dev/fb that I didn't create... crw---. 1 pstieber root 29, 0 2009-06-24 08:15 fb Should I still create /dev/fb0? AF> Just to check the MAJOR and MINOR numbers (also do AF> "man mknod") AF> http://lkml.indiana.edu/hypermail/linux/kernel/9807.3/0929.html AF> AF> It looks like the preupgrade process needs some AF> polishing. I used a F11 network install CD to update. Thanks for the help Aldo, Pete -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: F10 -> F11 X server problem with /dev/fb0
On Wed, Jun 24, 2009 at 4:41 PM, Peter J. Stieber wrote: > I just upgraded an x86_64 Fedora 10 system to Fedora 11. Now when I run > startx I get the following complaint. > > (EE) open /dev/fb0: No such file or directory > > Then the screen output says... > > Fatal server error: > Detected GPU lockup > > My Fedora 10 system was using the Fedora Xvfb package to perform offline > processing. I stopped that server, but I'm still getting the error. > > $ lspci > ... > 01:00.0 VGA compatible controller: nVidia Corporation NV44 > [GeForce 6200 LE] (rev a1) > ... > > I'm wondering how to go about fixing this. I know this probably isn't > enough to "go on", but just ask, and I'll provide more information. > > Pete > Hmm... this is just a pointer. At least you'll know what /dev/fb0 is for. http://tldp.org/HOWTO/Framebuffer-HOWTO-3.html "A framebuffer device is an abstraction for the graphic hardware. It represents the frame buffer of some video hardware, and allows application software to access the graphic hardware through a well-defined interface, so that the software doesn't need to know anything about the low-level interface stuff [Taken from Geert Uytterhoeven's framebuffer.txt in the linux kernel sources]" http://tldp.org/HOWTO/Framebuffer-HOWTO-5.html "You'll need to create the framebuffer device in /dev. You need one per framebuffer device, so all you need to do is to type in mknod /dev/fb0 c 29 0 for the first one. Subsequent ones would be in multiples of 32, so for example to create /dev/fb1, you would need to type in mknod /dev/fb1 c 29 32, and so on up to the eighth framebuffer device (mknod /dev/fb7 c 29 224)" Just to check the MAJOR and MINOR numbers (also do "man mknod") http://lkml.indiana.edu/hypermail/linux/kernel/9807.3/0929.html It looks like the preupgrade process needs some polishing. HTH, ~af -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
