It was indeed the Debian setup script that posed the problem, Ray.
I think we tried just every combination of including/excluding any of
the specific modules; doctored the X-configuration files etc. That was
now some month ago (March/April); in the meantime I've thrown away most
of the notes on all
At , Heimo Claasen wrote:
Geoff -
> Is there a simple reason why the "commercial distros" are able to do
> this ? Maybe they are using non-GPL software that we would not wish to
> see in Debian.
Me newbie cannot see the difference - it seems not a problem of proprietary
drivers (many of the vide
On Thursday 01 January 1970 01:00, Heimo Claasen wrote:
> Geoff -
>
> > Is there a simple reason why the "commercial distros" are able to do
> > this ? Maybe they are using non-GPL software that we would not wish to
> > see in Debian.
One would be well advised here to check for differanies in th
Geoff -
> Is there a simple reason why the "commercial distros" are able to do
> this ? Maybe they are using non-GPL software that we would not wish to
> see in Debian.
Me newbie cannot see the difference - it seems not a problem of proprietary
drivers (many of the video cards' are that in any
> Debian's hardware autodetect capability is close to
>nonexistant. That's why I suggested bypassing its X setup routines
>entirely, in favor of creating XF86Config-4 manually, based on the file a
>SuSE install produces.
Thank you for all the help. I will try doing it manually, but have had
t
>(After weeks of worktime wasted we gave up on making Debian/Woody work
>with a combine of a quite renowned video card and ditto high-res monitor;
>the "commercial" distros - Mandrake, SuSE, RH - hadn't any problem with
>that.)
Thanks to you both. I am sorry that your efforts were not rewarded.
I
At 09:37 AM 8/31/2003 +0200, geoff bagley wrote:
>(After weeks of worktime wasted we gave up on making Debian/Woody work
>with a combine of a quite renowned video card and ditto high-res monitor;
>the "commercial" distros - Mandrake, SuSE, RH - hadn't any problem with
>that.)
Thanks to you both. I
There#s a bug (sorry, Ray) win the Debian/Woody's standard "distro"
installation routine: When it comes to the video card's memory to
enter, anything else but "1024" (KB) wouldn't get you nowhere with
whatever of the not-listed brands of card/monitor combines.
Inputting that value would eventually
At 07:15 PM 8/30/2003 +0200, geoff bagley wrote:
>When SuSE "recognizes" it, what does it then "auto-configure" it *as*? SuSE
>will be writing an XF86Config-4 file that describes the configuration ...
>and, just possibly, setting up some kernel modules (a framebuffer, maybe)
>... and you should be
>When SuSE "recognizes" it, what does it then "auto-configure" it *as*? SuSE
>will be writing an XF86Config-4 file that describes the configuration ...
>and, just possibly, setting up some kernel modules (a framebuffer, maybe)
>... and you should be able to use its results to guide you in settin
At 05:20 PM 8/30/2003 +0200, geoff bagley wrote:
I have a TATUNG (Vibrant) VL7A 17" TFT LCD display.
It works very well on SuSE 8.0 Linux at 1280 by 1024 pixels.
SuSE recognizes it and auto-configures.
However, I can't find a way to make it work on Debian GNU/Linux 3.0
(Woody). As you may ima
I have a TATUNG (Vibrant) VL7A 17" TFT LCD display.
It works very well on SuSE 8.0 Linux at 1280 by 1024 pixels.
SuSE recognizes it and auto-configures.
However, I can't find a way to make it work on Debian GNU/Linux 3.0
(Woody). As you may imagine, it doesn't appear in the list of supported
12 matches
Mail list logo
