Barebones Puppy-4.00-dingo-alpha4

Message

Dougal · #21 Post by **Dougal** » Sun 30 Dec 2007, 13:47

BarryK wrote:Dougal has suggested that 'dmidecode' be used to identify the Classmate and the eeePC.

However, Intel have used a standard BIOS without any product or vendor information, so dmidecode does not return anything that can be used to identify it as a Classmate.

What about biosdecode? nothing from that either?

Lobster · #22 Post by **Lobster** » Sun 30 Dec 2007, 14:27

If thinking of adding another set of icons for Dingo Beta . . .
Warren has reminded me of the stylish and background independent
glass icons . . .
http://puppyfiles.org/dotpupsde/dotpups/Icons/

JustGreg · #23 Post by **JustGreg** » Sun 30 Dec 2007, 20:29

Here is the bios decode text file from the ASUS Eee PC running Puppy 2.14R 1.01 for anyone use. It has been gzipped for posting to the forum.

BarryK · #24 Post by **BarryK** » Mon 31 Dec 2007, 01:11

Lobster, excellent! I've been stingy, only putting in X servers that I have tested, now also the 'nv' driver. So, /usr/X11R7/lib/xorg/modules/drivers now has these (in the xorg_xorg_servers PET package):

i740, intel, neomagic, nv, sis, trident, vesa.

Anyone else want their Xorg server included for the next Dingo release?

Note, if Xorg cannot find a specific server for the video hardware, it falls back to 'vesa', but that lacks hardware-acceleration, meaning your display will be a bit sluggish -- which you might not notice on a fast CPU.

Dougal, no, I don't see anything from biosdecode that is helpful either.

pakt · #25 Post by **pakt** » Mon 31 Dec 2007, 08:34

BarryK wrote:Anyone else want their Xorg server included for the next Dingo release?

Please add 'nsc' and 'amd' (if available) for the StarBox thin clients.

nic2109 · #26 Post by **nic2109** » Mon 31 Dec 2007, 12:48

BarryK wrote:Anyone else want their Xorg server included for the next Dingo release?

I think that vesa is sufficient for those of us "blessed" (!) with an ATi card that needs their propriety driver. But is there a solution to this screen resolution conundrum?

Before installing fglrx (via MU's 3DCC) all Puppies I have tried behave the same: the video probe detects that the correct resolution is 1440x900, it buils xorg.conf correctly but then displays at 1024x768!

Is this inevitable? Or is there something that might improve it?

The fact that things are bigger than they should be isn't as big an issue as the impact that the wrong aspect ratio has. I appreciate that until the correct driver is used that there'll be no acceleration, but looking right out of the box would be a real winner.

linuxcbon · #27 Post by **linuxcbon** » Mon 31 Dec 2007, 15:16

Can you also add driver "ati" ?

BarryK · #28 Post by **BarryK** » Tue 01 Jan 2008, 01:56

Okay, I've added 'nsc' and 'ati' and 'atimisc' -- I don't know what that last one is for, but it seems something to do with ati.

zygo · #29 Post by **zygo** » Tue 01 Jan 2008, 20:17

In the help page I have converted all the selection items to link anchors so that when javascript is not available they can be seen. When js is avaialble then it converts the anchors into a selection control as the original help page had. It works in opera, seamonkey, netsurf, dillo, elinks.

Elinks is now much more advanced than elinks-0.11.1.pet. Could some kind soul make a pet please.

mcewanw · #30 Post by **mcewanw** » Wed 02 Jan 2008, 00:23

BarryK wrote: So, /usr/X11R7/lib/xorg/modules/drivers now has these (in the xorg_xorg_servers PET package):

i740, intel, neomagic, nv, sis, trident, vesa.

Anyone else want their Xorg server included for the next Dingo release?

I don't know anything about video driver/needs really, but from your list of included drivers I might be lucky already! I'm hoping to download Dingo soon in order to test some software I'm developing.

The three pretty much ancient laptops my family use for everything (DVD playing, program development, whatever...) are:

Compaq Armada 110 with Trident Cyberblade il / AGP 2x
Dell Latitude CPx and CPt with NeoMagic 256ZX
IBM Thinkpad 240 with (I think) NeoMagic 128XD

So I guess the neomagic and trident Dingo inclusions should work?

Dougal · #31 Post by **Dougal** » Wed 02 Jan 2008, 13:36

BarryK wrote:Okay, I've added 'nsc' and 'ati' and 'atimisc' -- I don't know what that last one is for, but it seems something to do with ati.

the "ati" driver is not actually a driver: Xorg uses it to find out which of the different ATI driver should be used -- radeon, atimisc, r200 (or whatever) etc.
You should probably add all the ATI related drivers if you add "ati".

BarryK · #32 Post by **BarryK** » Fri 04 Jan 2008, 00:03

Okay, I've added 'r128' and 'radeon' drivers, so the complete list so far is:

ati, atimisc, i740, intel, neomagic, nv, r128, radeon, sis, trident, vesa.

I know this is still being too stingy.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Barebones Puppy-4.00-dingo-alpha4

help page that works with and without javascript