TS3.3ce - New X-Wizard

A home for all kinds of Puppy related projects
Message
Author
User avatar
paulh177
Posts: 975
Joined: Tue 22 Aug 2006, 20:41

#16 Post by paulh177 »

No , that was when it was connected! And here's another one, right off the screen!

Code: Select all

vbe: VESA 3.0 detected.
oem: Brookdale-G Graphics Chip Accelerated VGA BIOS
vendor: Intel Corporation
product: Brookdale-G Graphics Controller Hardware Version 0.0
memory: 8000kb
mode: 1280x1024x256
mode: 640x480x16m
mode: 800x600x16m
mode: 1024x768x32k
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
mode: 132x25 (text)
mode: 132x43 (text)
mode: 132x50 (text)
mode: 132x60 (text)
mode: 640x480x256
mode: 800x600x256
mode: 1024x768x256
mode: 640x480x64k
mode: 800x600x64k
edid: 
edidfail
thanks for you attention

Paul

User avatar
paulh177
Posts: 975
Joined: Tue 22 Aug 2006, 20:41

#17 Post by paulh177 »

OK I experimented a little with ddcprobe. if I run it "ddcprobe" I get the output I posted. If I run "ddcprobe -" (or with -h -v - or whatever) it gives the following:

Code: Select all

 vbe: VESA 3.0 detected.
oem: Brookdale-G Graphics Chip Accelerated VGA BIOS
vendor: Intel Corporation
product: Brookdale-G Graphics Controller Hardware Version 0.0
memory: 8000kb
mode: 1280x1024x256
mode: 640x480x16m
mode: 800x600x16m
mode: 1024x768x32k
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
mode: 132x25 (text)
mode: 132x43 (text)
mode: 132x50 (text)
mode: 132x60 (text)
mode: 640x480x256
mode: 800x600x256
mode: 1024x768x256
mode: 640x480x64k
mode: 800x600x64k
edid: 
edid: 1 3
id: 7002
eisa: DEL7002
serial: 42304144
manufacture: 2 2002
input: sync on green, analog signal.
screensize: 30 23
gamma: 2.870000
dpms: RGB, active off, suspend, standby
timing: 640x480@60 Hz (VGA)
timing: 640x480@75 Hz (VESA)
timing: 800x600@60 Hz (VESA)
timing: 800x600@75 Hz (VESA)
timing: 1024x768@75 Hz (VESA)
ctiming: 1024x768@85
ctiming: 800x600@85
ctiming: 640x480@85
ctiming: 1280x1024@60
dtiming: 1024x768@93
monitorserial: 93CUR219B0AD
monitorname: DELL  E771p
monitorrange: 30-70, 50-160

User avatar
paulh177
Posts: 975
Joined: Tue 22 Aug 2006, 20:41

#18 Post by paulh177 »

OK I experimented a little with ddcprobe. if I run it "ddcprobe" I get the output I posted. If I run "ddcprobe -" (or with -h -v - or whatever) it gives the following:

Code: Select all

 vbe: VESA 3.0 detected.
oem: Brookdale-G Graphics Chip Accelerated VGA BIOS
vendor: Intel Corporation
product: Brookdale-G Graphics Controller Hardware Version 0.0
memory: 8000kb
mode: 1280x1024x256
mode: 640x480x16m
mode: 800x600x16m
mode: 1024x768x32k
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
mode: 132x25 (text)
mode: 132x43 (text)
mode: 132x50 (text)
mode: 132x60 (text)
mode: 640x480x256
mode: 800x600x256
mode: 1024x768x256
mode: 640x480x64k
mode: 800x600x64k
edid: 
edid: 1 3
id: 7002
eisa: DEL7002
serial: 42304144
manufacture: 2 2002
input: sync on green, analog signal.
screensize: 30 23
gamma: 2.870000
dpms: RGB, active off, suspend, standby
timing: 640x480@60 Hz (VGA)
timing: 640x480@75 Hz (VESA)
timing: 800x600@60 Hz (VESA)
timing: 800x600@75 Hz (VESA)
timing: 1024x768@75 Hz (VESA)
ctiming: 1024x768@85
ctiming: 800x600@85
ctiming: 640x480@85
ctiming: 1280x1024@60
dtiming: 1024x768@93
monitorserial: 93CUR219B0AD
monitorname: DELL  E771p
monitorrange: 30-70, 50-160

User avatar
ecomoney
Posts: 2178
Joined: Fri 25 Nov 2005, 07:00
Location: Lincolnshire, England
Contact:

Congratulations

#19 Post by ecomoney »

Thanks for releasing this project Leachim, it will bring the standard of "polish" to puppy that other distro's have. Perhaps you would post "easy" instructions on how to gather the technical feedback that you need from system? That way a lot more people will be able to help.

The segment which i get the impression puppy would be aimed at would be computers of around a 200mhz to where the other main distros start to become useful (800mhz and up). Im not sure about the default resolution for the wizard to boot into. There are still a great many computers with graphics cards that are unable to display more than 16k colour in 1024x768. They are incapable of displaying higher, and often the monitors from this period would not cope in any case. 640x480 (the current default for the xvesa system on the current xorgwizard) I think is a bad choice because, to a "linux newbies" eyes (who is used to setting up windows), 640x480 automatically gives the bad first impression that the display drivers are not present and they need to go hunting around registering on websites to find them!!! an 800x600 screen would at least re-assure new linux users that their graphics were working better than in windows failsafe mode (640x480x16).
Puppy Linux's [url=http://www.murga-linux.com/puppy/viewtopic.php?p=296352#296352]Mission[/url]

Sorry, my server is down atm!

User avatar
SirDuncan
Posts: 829
Joined: Sat 09 Dec 2006, 20:35
Location: Ohio, USA
Contact:

#20 Post by SirDuncan »

I think 800x600 is a good idea. I don't know of any monitors still in use that can't support it (not saying that there aren't any, of course). Besides, no matter what drivers you are using, nothing looks good on 640x480.
Be brave that God may help thee, speak the truth even if it leads to death, and safeguard the helpless. - A knight's oath

Leachim
Posts: 229
Joined: Sun 27 May 2007, 23:04

#21 Post by Leachim »

The default screen resolution if the monitor does not report its capabilities is 800x600.

The wizard currently uses silly refresh rates under certain circumstances. I hope I can fix this tomorrow.

It would be nice if somebody would take care about integrating the current versions of nVidia's, ATI's and Intel's propriatary drivers. To save space in the basic distribution they might be added as a separate sfs-file.

My aims are the wizard running elder and newer hardware equally well. (I use my Puppy-derived Linux on everything from Pentium II, first generation Athlons up to state-of-the-art multi-core processors.)

User avatar
cb88
Posts: 1165
Joined: Mon 29 Jan 2007, 03:12
Location: USA
Contact:

#22 Post by cb88 »

an enhanced zdrv would be the best option it could be downloaded buy lobster's wizard or even petget(there would have to be a script that copies it to the right place) or psi

all the more reason for a generic script that installs sfs modules to the right place depandant on instalation type
Taking Puppy Linux to the limit of perfection. meanwhile try "puppy pfix=duct_tape" kernel parem eater.
X86: Sager NP6110 3630QM 16GB ram, Tyan Thunder 2 2x 300Mhz
Sun: SS2 , LX , SS5 , SS10 , SS20 ,Ultra 1, Ultra 10 , T2000
Mac: Platinum Plus, SE/30

raffy
Posts: 4798
Joined: Wed 25 May 2005, 12:20
Location: Manila

1280

#23 Post by raffy »

The script told me nothing in console, and when I ran xwin, I got 1280 resolution (must be the default of my monitor). If presented with choice, like in xorgwizard, I usually choose the lower resolution.

User avatar
cb88
Posts: 1165
Joined: Mon 29 Jan 2007, 03:12
Location: USA
Contact:

#24 Post by cb88 »

Is it possible that this could support directfb? would be interesting if not prectical since gtk in puppy is compiled not compiled for it......
Taking Puppy Linux to the limit of perfection. meanwhile try "puppy pfix=duct_tape" kernel parem eater.
X86: Sager NP6110 3630QM 16GB ram, Tyan Thunder 2 2x 300Mhz
Sun: SS2 , LX , SS5 , SS10 , SS20 ,Ultra 1, Ultra 10 , T2000
Mac: Platinum Plus, SE/30

User avatar
ecomoney
Posts: 2178
Joined: Fri 25 Nov 2005, 07:00
Location: Lincolnshire, England
Contact:

zdrv

#25 Post by ecomoney »

An enhanced zdrv might not be a bad idea full stop, as its the one that dictates if puppy works at all! I like the idea of automatic accelleration (and whatever the fb is) but would prefer this to be an extra feature to be added later once the base is complete. Good to bear in mind for the future. I would doubt that *most* computers that puppy would need to be used on could cope with accelleration.

I found these statistics

1024x768 is by far the most common screen size, but the problem with laptops is they sometimes look wierd if you dont use the default resolution. Difficult one this.
Last edited by ecomoney on Tue 13 Nov 2007, 23:21, edited 1 time in total.

Leachim
Posts: 229
Joined: Sun 27 May 2007, 23:04

#26 Post by Leachim »

This time I really updated the X-Wizard in the download-link in the first post of this thread! (I'm still fighting with the upload-feature of this forum!)

The improved wizard should now choose reasonable refresh rates on nearly all displays - trying to guess whether a display is a CRT or a TFT. It prefers refresh rates about 85 Hz for CRTs and about 60 Hz for TFTs.

I also added a testsuite-feature that allows for "bulk-testing". So I can check each new version of the wizard against my whole "database" of ddcprobe-output-files.

Leachim
Posts: 229
Joined: Sun 27 May 2007, 23:04

Re: zdrv

#27 Post by Leachim »

ecomoney wrote:1024x768 is by far the most common screen size, but the problem with laptops is they sometimes look wierd if you dont use the default resolution. Difficult one this.
The problem with most notebooks is that they are not telling their screen size!

My proposal for handling this and similar problems:

The X-Wizard can categorize xorg.conf-files into 3 states

* autogenerated with complete information

* autogenerated with incomplete information

* user configured

When X starts up a X-startup-script will check the state of the xorg.conf-file. If it is "autogenerated incomplete" it will launch a configuration dialog presenting the user a selection of possible resolutions (and refresh rates). If the user closes the box with the Okay-button the selected values are entered into the xorg.conf-file and the file's state is switched to "user configured".

User avatar
cb88
Posts: 1165
Joined: Mon 29 Jan 2007, 03:12
Location: USA
Contact:

#28 Post by cb88 »

@ecomoney the directfb project aims to replace X if i am not misstaken and is currently more lightweight...but less mature...seems to be an active project though

the frame buffer is a memory buffer that holds frames the frames are then rendered to the screen...

a graphics card is a fancy frame buffer....

Yes ecomoney I did mean that the enhanced zdvr would be downloaded not default. However, contrary to what you would think many older computers would run better with video acceleration because it takes the load off the processor especially for webbrowseing and video.

so perhaps accelerated drivers should be included for very old cards (riva tnt matrox neomagic or an cards that have small drivers) so that it makes old PC's usable by default....

obviously nvidia cards have huge dirvers and they could be included without affecting proformance (would improve performance actaully) but also driving up the size of the ISO....

since you are aiming to get this running well by default I would lean toward building 2 versions one with the standared "fulldrivers" set and another with all the drivers we can find....."megadrivers" or what ever you wanna call it

the "megadrivers" may boot a little slower on say an nvidia machine but that would be due to the drivers loading it would/should run faster after booting....

on top of all that it would allow more wide spread testing of the #d drivers available for puppy

sorry for the long winded reply......im like that ;)
Taking Puppy Linux to the limit of perfection. meanwhile try "puppy pfix=duct_tape" kernel parem eater.
X86: Sager NP6110 3630QM 16GB ram, Tyan Thunder 2 2x 300Mhz
Sun: SS2 , LX , SS5 , SS10 , SS20 ,Ultra 1, Ultra 10 , T2000
Mac: Platinum Plus, SE/30

User avatar
ecomoney
Posts: 2178
Joined: Fri 25 Nov 2005, 07:00
Location: Lincolnshire, England
Contact:

cb88

#29 Post by ecomoney »

Thanks cb88 for filling in one of the many the gaps in my knowledge. Auto detection of 3d graphics cards would be great, but after my recent experiences with it (and a project called "envy") I would imagine it would be a separate project and a half just to get this going (Leachim please correct me if Im wrong). I can imagine it could be a feature added to this at a later date, but I am worried about the timescales. It is better to get something that "just works" in the majority of cases and is useable for now, and worry about the special cases later. A standard detection routine would be great, and a "mega-sfs" version as a second project, adding on to the standard one.
Puppy Linux's [url=http://www.murga-linux.com/puppy/viewtopic.php?p=296352#296352]Mission[/url]

Sorry, my server is down atm!

Leachim
Posts: 229
Joined: Sun 27 May 2007, 23:04

#30 Post by Leachim »

The wizard itself checks what hard- and software (drivers) are available.

Currently the wizard mainly checks the monitor's capabilities if possible and tries to use the proprietary nVidia- or ATI-drivers if possible.

To further improve the wizard I need more feeback! (It now works fine on all PCs I have access to.)

Everitt
Posts: 331
Joined: Tue 19 Dec 2006, 21:59
Location: Leeds,UK or Birmingham, UK

#31 Post by Everitt »

The new version works fine with my hardware, outputing

Code: Select all

hardware profile:  NVIDIAGSM3b41
keymap:            gb
screen resolution: 800x600
refresh rate:      85
monitor model:     ambiguous
graphics adapter:  nv43 Board - 21602013 Chip Rev
X-driver:          nvidia
This is technically correct, but I can't help but feel that 800x600@80Hz is a bit low when 1024x768@75 is avaliable.

Code: Select all

ctiming: 640x480@60
ctiming: 640x480@75
ctiming: 640x480@85
ctiming: 720x450@70
ctiming: 800x600@75
ctiming: 800x600@85
ctiming: 1024x768@75
dtiming: 1024x768@74
Just a personal preference really, but maybe something to think about?

Leachim
Posts: 229
Joined: Sun 27 May 2007, 23:04

#32 Post by Leachim »

Everitt wrote:This is technically correct, but I can't help but feel that 800x600@80Hz is a bit low when 1024x768@75 is avaliable.

Just a personal preference really, but maybe something to think about?
As you say this has to do with personal taste. I also do know people who would prefer refresh rates of 100 Hz! So I had to find some compromise.

But I could add a configuration file (/etc/xwizard.conf or ~/.xwizard.conf) with personal settings where one could set one's preferred refresh rate.

User avatar
HairyWill
Posts: 2928
Joined: Fri 26 May 2006, 23:29
Location: Southampton, UK

#33 Post by HairyWill »

are you interested in results from intel cards i810
Will
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]

Leachim
Posts: 229
Joined: Sun 27 May 2007, 23:04

#34 Post by Leachim »

HairyWill wrote:are you interested in results from intel cards i810
yes!!!

I do not have access to any PCs with Intel graphics hardware! I would be interested in the output of ddcprobe and lspci.

Thanks in advance!

User avatar
HairyWill
Posts: 2928
Joined: Fri 26 May 2006, 23:29
Location: Southampton, UK

#35 Post by HairyWill »

After liberally sprinkling pci.ids and pci.ids.gz in random combinations around my system I still can't get names out of lspc so I've given you elspci -l as well so you can see the associated modules

This is on a thinkpad x30 with a puny 830m graphics card
xorg currently uses the i810 driver

Code: Select all

# lspci -n  
00:00.0 Class 0600: 8086:3575 (rev 04)
00:02.0 Class 0300: 8086:3577 (rev 04)
00:02.1 Class 0380: 8086:3577
00:1d.0 Class 0c03: 8086:2482 (rev 02)
00:1d.1 Class 0c03: 8086:2484 (rev 02)
00:1d.2 Class 0c03: 8086:2487 (rev 02)
00:1e.0 Class 0604: 8086:2448 (rev 42)
00:1f.0 Class 0601: 8086:248c (rev 02)
00:1f.1 Class 0101: 8086:248a (rev 02)
00:1f.3 Class 0c05: 8086:2483 (rev 02)
00:1f.5 Class 0401: 8086:2485 (rev 02)
00:1f.6 Class 0703: 8086:2486 (rev 02)
01:00.0 Class 0607: 1180:0476 (rev a8)
01:00.1 Class 0607: 1180:0476 (rev a8)
01:00.2 Class 0c00: 1180:0552
01:02.0 Class 0280: 8086:4220 (rev 05)
01:08.0 Class 0200: 8086:1031 (rev 42)
# ddcprobe
vbe: VESA 3.0 detected.
oem: Almador Graphics Chip Accelerated VGA BIOS
vendor: Intel Corporation
product: Almador Graphics Controller Hardware Version 0.0
memory: 8000kb
mode: 1280x1024x256
mode: 640x480x16m
mode: 800x600x64k
mode: 800x600x16m
mode: 1024x768x32k
mode: 1024x768x64k
mode: 1024x768x16m
mode: 1280x1024x64k
mode: 1280x1024x16m
mode: 640x480x256
mode: 800x600x256
mode: 1024x768x256
mode: 640x480x64k
edid: 
edidfail
# elspci -l 
01:08.0 020000 8086:1031 <eepro100>
01:02.0 028000 8086:4220 <ipw2200>
01:00.2 0C0010 1180:0552 <>
01:00.1 060700 1180:0476 <yenta_cardbus>
01:00.0 060700 1180:0476 <yenta_cardbus>
00:1f.6 070300 8086:2486 <slamr>
00:1f.5 040100 8086:2485 <Intel ICH>
00:1f.3 0C0500 8086:2483 <>
00:1f.1 01018A 8086:248A <PIIX_IDE>
00:1f.0 060100 8086:248C <>
00:1e.0 060400 8086:2448 <>
00:1d.2 0C0300 8086:2487 <uhci_hcd>
00:1d.1 0C0300 8086:2484 <uhci_hcd>
00:1d.0 0C0300 8086:2482 <uhci_hcd>
00:02.1 038000 8086:3577 <>
00:02.0 030000 8086:3577 <>
00:00.0 060000 8086:3575 <agpgart-intel>
# 
Will
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]

Post Reply