Re: X breaks in CD-based installer environment
On Sat, Apr 27, 2002 at 06:09:50PM -0500, Branden Robinson wrote: > The part that is frustrating is this: > > (**) R128(0): Using framebuffer device > (II) Loading sub module "fbdevhw" > (II) LoadModule: "fbdevhw" > (II) Loading /live/lib/modules/linux/libfbdevhw.a > (II) Module fbdevhw: vendor="The XFree86 Project" > compiled for 4.1.0.1, module version = 0.0.2 > ABI class: XFree86 Video Driver, version 0.4 > (II) UnloadModule: "ati" > (II) UnloadModule: "fbdevhw" > (II) Unloading /live/lib/modules/linux/libfbdevhw.a > (II) UnloadModule: "vgahw" > (II) Unloading /live/lib/modules/libvgahw.a > (II) UnloadModule: "r128" > (II) Unloading /live/lib/modules/drivers/r128_drv.o > (EE) Screen(s) found, but none have a usable configuration. > > All of a sudden, *something* is deciding it's time to bail out. It looks like > the fbdevhw module. But no level of verbosity is explaining. On a normal > startup, right after the fbdevhw module talks about itself, R128(0) speaks up > and claims the ATI Rage 128 LF device. > > I don't understand the internals of > xc/programs/Xserver/hw/xfree86/fbdevhw/fbdevhw.c to speculate on what's > going on. Is there a place where some xf86DrvMsg()s could be added to > help diagnose this apparent decision by the module to bail out?? Problem solved. It was caused by a missing /dev/fb0 file. This, of course, exists in a normal installation but was missing from the instalelr environment. Maybe something (fbdevhw.c or r128_driver.c, I'm not sure which) should complain if /dev/fb0 cannot be opened? -- G. Branden Robinson|If a man ate a pound of pasta and a Debian GNU/Linux |pound of antipasto, would they [EMAIL PROTECTED] |cancel out, leaving him still http://people.debian.org/~branden/ |hungry? -- Scott Adams msg03562/pgp0.pgp Description: PGP signature
Re: Splitting packages of video drivers in XF4.2 ?
On Sun, 2002-04-28 at 01:46, Hendrik Sattler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Am Samstag, 27. April 2002 23:19 schrieben Sie: > > On Sat, 2002-04-27 at 11:39, Hendrik Sattler wrote: > > > I have some kind of wish to discuss which would makes life much less hard > > > for users of non-Debian-files: > > > > > > It is fact that not all graphics hardware runs with the drivers supplied > > > with XF4.x, some examples are: > > > some NVidia cards (if you want any acceleration at all) > > > Matrox cards (if you need the mga_hal, e.g. for DRI) > > > 3Dfx-V3 on earlier XFree version (the YUV support) > > > maybe others, too > > > > > > The problem is: most of those drivers (best example is Matrox) simply > > > replace some original files in /usr/X11R6/lib/modules. As those are not > > > marked and config files (and they are no config files and this is no_ > > > request to make them), they silently get overwritten. > > > The surprise is then on a non-funtional X on restart :( > > > > > > I think the probably best solution would be to split off the video cards > > > drivers into one extra package, only keeping generic drivers in > > > xserver-xfree86. > > > > You don't have to overwrite package-controlled files in this case; the X > > server supports several module paths, just put them in /usr/local/X11R6 > > or wherever. > > To the above: Where are those paths defined? There is nothing in /etc/X11 > that specifies something in /usr/local. Maybe they are compiled in (or even > hard-coded)? The default path is hardcoded, but you can override it with any number of paths in the files section, man XF86Config-4. > Anyway, this would not work anyway because the module names are equal and I > guess that XFree will prefer /usr/X11R6 to anything else. It will traverse the paths in the order you specify them (or maybe in the reverse order? :). -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Splitting packages of video drivers in XF4.2 ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Samstag, 27. April 2002 23:19 schrieben Sie: > On Sat, 2002-04-27 at 11:39, Hendrik Sattler wrote: > > I have some kind of wish to discuss which would makes life much less hard > > for users of non-Debian-files: > > > > It is fact that not all graphics hardware runs with the drivers supplied > > with XF4.x, some examples are: > > some NVidia cards (if you want any acceleration at all) > > Matrox cards (if you need the mga_hal, e.g. for DRI) > > 3Dfx-V3 on earlier XFree version (the YUV support) > > maybe others, too > > > > The problem is: most of those drivers (best example is Matrox) simply > > replace some original files in /usr/X11R6/lib/modules. As those are not > > marked and config files (and they are no config files and this is no_ > > request to make them), they silently get overwritten. > > The surprise is then on a non-funtional X on restart :( > > > > I think the probably best solution would be to split off the video cards > > drivers into one extra package, only keeping generic drivers in > > xserver-xfree86. > > You don't have to overwrite package-controlled files in this case; the X > server supports several module paths, just put them in /usr/local/X11R6 > or wherever. To the above: Where are those paths defined? There is nothing in /etc/X11 that specifies something in /usr/local. Maybe they are compiled in (or even hard-coded)? Anyway, this would not work anyway because the module names are equal and I guess that XFree will prefer /usr/X11R6 to anything else. Well, dpkg-divert works alright, I just did not know about that feature of dpkg (and how to search for a feature you do not even know the word for?). Hendrik Sattler -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8yzg8zvr6q9zCwcERAiUQAJ42DIB7dfKjYXR/5sqcEVfpsYY0uwCgh10e NG6L9XfjwqUyInqKbsOxDCo= =1xUU -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: X breaks in CD-based installer environment
On Sun, Apr 28, 2002 at 12:44:08AM +0200, Michel Dänzer wrote: > On Sun, 2002-04-28 at 00:41, Jimmy Kaplowitz wrote: > > On Sun, Apr 28, 2002 at 12:15:01AM +0200, Michel Dänzer wrote: > > > Option "UseFBDev" only works with a 'real' framebuffer device. Does the > > > working system use aty128fb but the installation system OFfb? > > > > They are the exact same machine. > > I got that. :) > > Maybe the installation system boots with video=ofonly, or its kernel > doesn't have aty128fb, ... FYI, I'm the "other guy" who tried this. Jimmy and I are both working on 600 MHz iBook Dual USBs. I checked the point you're describing with Jimmy. The aty128fb is compiled and available, and video=ofonly is not set in the default boot configuration. The part that is frustrating is this: (**) R128(0): Using framebuffer device (II) Loading sub module "fbdevhw" (II) LoadModule: "fbdevhw" (II) Loading /live/lib/modules/linux/libfbdevhw.a (II) Module fbdevhw: vendor="The XFree86 Project" compiled for 4.1.0.1, module version = 0.0.2 ABI class: XFree86 Video Driver, version 0.4 (II) UnloadModule: "ati" (II) UnloadModule: "fbdevhw" (II) Unloading /live/lib/modules/linux/libfbdevhw.a (II) UnloadModule: "vgahw" (II) Unloading /live/lib/modules/libvgahw.a (II) UnloadModule: "r128" (II) Unloading /live/lib/modules/drivers/r128_drv.o (EE) Screen(s) found, but none have a usable configuration. All of a sudden, *something* is deciding it's time to bail out. It looks like the fbdevhw module. But no level of verbosity is explaining. On a normal startup, right after the fbdevhw module talks about itself, R128(0) speaks up and claims the ATI Rage 128 LF device. I don't understand the internals of xc/programs/Xserver/hw/xfree86/fbdevhw/fbdevhw.c to speculate on what's going on. Is there a place where some xf86DrvMsg()s could be added to help diagnose this apparent decision by the module to bail out?? -- G. Branden Robinson|It was a typical net.exercise -- a Debian GNU/Linux |screaming mob pounding on a greasy [EMAIL PROTECTED] |spot on the pavement, where used to http://people.debian.org/~branden/ |lie the carcass of a dead horse. msg03559/pgp0.pgp Description: PGP signature
Re: X breaks in CD-based installer environment
On Sun, 2002-04-28 at 00:41, Jimmy Kaplowitz wrote: > On Sun, Apr 28, 2002 at 12:15:01AM +0200, Michel Dänzer wrote: > > Option "UseFBDev" only works with a 'real' framebuffer device. Does the > > working system use aty128fb but the installation system OFfb? > > They are the exact same machine. I got that. :) Maybe the installation system boots with video=ofonly, or its kernel doesn't have aty128fb, ... -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: X breaks in CD-based installer environment
On Sun, Apr 28, 2002 at 12:15:01AM +0200, Michel Dänzer wrote: > Option "UseFBDev" only works with a 'real' framebuffer device. Does the > working system use aty128fb but the installation system OFfb? They are the exact same machine. That is why this is so annoying! :-) - Jimmy Kaplowitz [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: X breaks in CD-based installer environment
On Sun, 2002-04-28 at 00:04, Jimmy Kaplowitz wrote: > Hi XFree86 (and Debian X) people. I am in the process of porting PGI, > Progeny Linux Systems' X-based installer program for Debian, to PowerPC. > I have overcome several hurdles, except that on my iBook2, X refuses to do > any modeline processing or find a usable configuration in the installer > (running off of a CD with everything in /live also-known-as /usr > read-only but everything else in a read/write initrd). I have tested my > working config from my existing iBook2 Debian install in the installer, > and it failed the same way as the PGI config did. The reverse has also been > tested. > > I am attaching a working config and the corresponding X log, with -verbose > 3, as well as the equivalent with a PGI config. Again, as I said before, I > have tried the working config in the CD-based installer, and it has failed, > and another person who has the same hardware has tried the broken config on > his regular Debian setup, and it has worked. Option "UseFBDev" only works with a 'real' framebuffer device. Does the working system use aty128fb but the installation system OFfb? -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
X breaks in CD-based installer environment
Hi XFree86 (and Debian X) people. I am in the process of porting PGI, Progeny Linux Systems' X-based installer program for Debian, to PowerPC. I have overcome several hurdles, except that on my iBook2, X refuses to do any modeline processing or find a usable configuration in the installer (running off of a CD with everything in /live also-known-as /usr read-only but everything else in a read/write initrd). I have tested my working config from my existing iBook2 Debian install in the installer, and it failed the same way as the PGI config did. The reverse has also been tested. I am attaching a working config and the corresponding X log, with -verbose 3, as well as the equivalent with a PGI config. Again, as I said before, I have tried the working config in the CD-based installer, and it has failed, and another person who has the same hardware has tried the broken config on his regular Debian setup, and it has worked. Any advice would be very helpful. Thank you. - Jimmy Kaplowitz [EMAIL PROTECTED] # $Progeny: XF86Config.template,v 1.18 2002/04/22 21:34:36 branden Exp $ # This config file is for the 4.x XFree86 X server. Section "Files" RGBPath "/live/lib/X11/rgb" FontPath"/live/lib/X11/fonts/misc" FontPath"/live/lib/X11/fonts/100dpi" ModulePath "/live/lib/modules" EndSection Section "Module" Load"ddc" Load"dbe" Load"extmod" Load"bitmap" Load"type1" Load"speedo" Load"vbe" Load"int10" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc101" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Generic Mouse" Driver "mouse" Option "CorePointer" Option "Device" "/dev/input/mouse0" Option "Protocol" "ImPS/2" EndSection Section "Monitor" Identifier "Primary Monitor" HorizSync 30-55 VertRefresh 50-90 EndSection Section "Device" Identifier "Configured Video Device" Driver "ati" VideoRam2048 Option "UseFBDev" "true" EndSection Section "Screen" Identifier "Low Screen" Device "Configured Video Device" Monitor "Primary Monitor" DefaultDepth4 SubSection "Display" Depth 4 Modes "640x480" EndSubSection EndSection Section "Screen" Identifier "Medium Screen" Device "Configured Video Device" Monitor "Primary Monitor" DefaultDepth8 SubSection "Display" Depth 8 Modes "640x480" EndSubSection EndSection Section "Screen" Identifier "High Screen" Device "Configured Video Device" Monitor "Primary Monitor" DefaultDepth15 SubSection "Display" Depth 15 Modes "1024x768" EndSubSection EndSection Section "ServerLayout" Identifier "low" Screen "Low Screen" InputDevice "Generic Keyboard" InputDevice "Generic Mouse" EndSection Section "ServerLayout" Identifier "medium" Screen "Medium Screen" InputDevice "Generic Keyboard" InputDevice "Generic Mouse" EndSection Section "ServerLayout" Identifier "high" Screen "High Screen" InputDevice "Generic Keyboard" InputDevice "Generic Mouse" EndSection Section "Files" FontPath"unix/:7110"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/lib/X11/fonts/Type1" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/lib/X11/fonts/75dpi" EndSection ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the "### BEGIN DEBCONF SECTION" line above, and/or after the # "### END DEBCONF SECTION" line b
Re: Splitting packages of video drivers in XF4.2 ?
On Sat, 2002-04-27 at 11:39, Hendrik Sattler wrote: > > I have some kind of wish to discuss which would makes life much less hard for > users of non-Debian-files: > > It is fact that not all graphics hardware runs with the drivers supplied with > XF4.x, some examples are: > some NVidia cards (if you want any acceleration at all) > Matrox cards (if you need the mga_hal, e.g. for DRI) > 3Dfx-V3 on earlier XFree version (the YUV support) > maybe others, too > > The problem is: most of those drivers (best example is Matrox) simply replace > some original files in /usr/X11R6/lib/modules. As those are not marked and > config files (and they are no config files and this is no_ request to make > them), they silently get overwritten. > The surprise is then on a non-funtional X on restart :( > > I think the probably best solution would be to split off the video cards > drivers into one extra package, only keeping generic drivers in > xserver-xfree86. You don't have to overwrite package-controlled files in this case; the X server supports several module paths, just put them in /usr/local/X11R6 or wherever. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Splitting packages of video drivers in XF4.2 ?
On Sat, Apr 27, 2002 at 11:39:59AM +0200, Hendrik Sattler wrote: > The problem is: most of those drivers (best example is Matrox) simply replace > some original files in /usr/X11R6/lib/modules. As those are not marked and > config files (and they are no config files and this is no_ request to make > them), they silently get overwritten. > The surprise is then on a non-funtional X on restart :( > > I think the probably best solution would be to split off the video cards > drivers into one extra package, only keeping generic drivers in > xserver-xfree86. I think you need to read dpkg-divert(8). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Splitting packages of video drivers in XF4.2 ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have some kind of wish to discuss which would makes life much less hard for users of non-Debian-files: It is fact that not all graphics hardware runs with the drivers supplied with XF4.x, some examples are: some NVidia cards (if you want any acceleration at all) Matrox cards (if you need the mga_hal, e.g. for DRI) 3Dfx-V3 on earlier XFree version (the YUV support) maybe others, too The problem is: most of those drivers (best example is Matrox) simply replace some original files in /usr/X11R6/lib/modules. As those are not marked and config files (and they are no config files and this is no_ request to make them), they silently get overwritten. The surprise is then on a non-funtional X on restart :( I think the probably best solution would be to split off the video cards drivers into one extra package, only keeping generic drivers in xserver-xfree86. Sincerly... Hendrik Sattler PS: Actually, the problem that files get silently overwritten is also with other files likes Lepieds' wacom_drv.o but it should not address a majority of users. - -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.schulnetz.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8ynHzzvr6q9zCwcERAmrSAJ4npAaSbDjdev6tOZI+FzdpaW+bAQCfXdBG kCrEAGJLvaormhzACpGkVPM= =E+F1 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
