Page 1 of 2
Barebones Puppy-4.00-dingo-alpha4
Posted: Wed 26 Dec 2007, 08:53
by cthisbear
Hooray she works on NTFS.
Just cleaned up my XP install with no hiccups.
Internet working.......but I cannot change the history to zero
in NetSurf .
I did not test sound.
Download....burn CD....boot...delete XP files....browsing the internet
in ten minutes total.
Pull up your socks young Barry....not quick enough.....Ha! ha!
Happy New Year....I hope you enjoy a break soonest.
Regards Chris.
Posted: Wed 26 Dec 2007, 12:15
by Lobster
Tried it on my main machine and a laptop. First thing I tried on my main machine (connection DHCP etc - fine) was installing Firefox from the Package Manager. It installed a link in the JWM menu but that link was incorrect and I run it by typing 'Firefox' from the console. The Firefox 2007 files are placed in the Opt directory . . .
On my main machine I only get the option up to 600x800 res (but it should and has gone higher with xvesa) Both the main machine and the laptop went straight in to display - which is great for beginners. The laptop went up to 1028 x768 and I was able to select and use that OK
An interesting thing . . .
If you change the icon set and then without restarting JWM, just move the mouse over the icons they change to the newly selected icons. Suits me - not sure why this happens though . . .
What I would like to try is adding xorg
but there are 3 sets of files in the package manager at iblio.
Which ones do I need?
Is xorgwizard gonna run?
Posted: Wed 26 Dec 2007, 13:23
by nic2109
Lobster wrote:An interesting thing . . .
If you change the icon set and then without restarting JWM, just move the mouse over the icons they change to the newly selected icons. Suits me - not sure why this happens though ....
Yeah, I noticed (and posted) this in Alpha 3, so it's not specific to the Barebones build.
Posted: Wed 26 Dec 2007, 18:33
by jediborger
Changing the JWM theme doesn't change the taskbar color, still orange. Also every time JWM is restarted an extra freememapplet is opened. Other than that I like this "barebones" idea.
Happy Boxing Day!
Dingo full hard drive install
Posted: Thu 27 Dec 2007, 02:08
by Firefox
Dingo4.00 alpha4
Full Hard Drive Install
1: Could not Install Dingo as a Full Hard Drive setup.
Repeating loop of
login (xxxxx) root login on tty
-sh /tmp/boot_kernel.log read only
touch cannot /tmp/bootint.txt read only file system
/usr/X11R7/bin/xwm read only file system
cat /tmp/...x no such file or directory
grep: /tmp/..x no such file or directory
2:
On poweroff, system did not switch off.
3: When tried with Frugal install and saving to MBR,
I was not able to find /boot to alter Menu.1st so had to use boot grubloader which worked but then saved a second 1Gb pup save file. Why does it ask if I wanted the file saved every time I close down, or is that normal in a frugal install? Also the text still uses hda1.
4: Pup Dial worked ok.
barebones dingo alpha 4
Posted: Thu 27 Dec 2007, 10:21
by eccentric
Seasons greetings to you all.. Is there a version of PPPoE that will function with barebones dingo a. 4 if some one could point me to it with instructions on how to install. as i would like to try this on the internet. Michael an eccentric. ( an eccentric is for life not just Christmas ).. this was sent using 3.01 seamonkey.
oops it should be a dog is for life.
Posted: Thu 27 Dec 2007, 23:58
by BarryK
Lobster wrote: Tried it on my main machine and a laptop. First thing I tried on my main machine (connection DHCP etc - fine) was installing Firefox from the Package Manager. It installed a link in the JWM menu but that link was incorrect and I run it by typing 'Firefox' from the console. The Firefox 2007 files are placed in the Opt directory . .
If I remember rightly, you have to reboot after installing Firefox, for the menu entry to work. I think that PETget does say that a reboot is required if any web browser, library or x server is installed.
What I would like to try is adding xorg
but there are 3 sets of files in the package manager at iblio.
Which ones do I need?
The minimum you need for Xorg is the 'xorg_xorg_base-7.3' PET package, but that will only give you the 'vesa' Xorg server. To add extra Xorg servers, also install 'xorg_xorg_servers-7.3' package -- though note, it only has a small number of Xorg servers in it, only ones that I have so far tested. What will happen is, if a Xorg server does not exist for your video hardware, Xorg will fallback to using the generic 'vesa' Xorg server.
Actually, I reckon I'll put those two Xorg packages in the next barebones, as they're not very big and the vast majority of users will prefer Xorg rather than Xvesa. Or, at least I should put in xorg_xorg_base, as the 'vesa' server is better than Xvesa in many ways.
Re: barebones dingo alpha 4
Posted: Fri 28 Dec 2007, 00:08
by BarryK
eccentric wrote:Seasons greetings to you all.. Is there a version of PPPoE that will function with barebones dingo a. 4 if some one could point me to it with instructions on how to install. as i would like to try this on the internet. Michael an eccentric. ( an eccentric is for life not just Christmas ).. this was sent using 3.01 seamonkey.
oops it should be a dog is for life.
I posted something to my blog sometime ago about this. I have left out Roaring Penguin pppoe as the 'ppp' package has a plugin for pppoe and I wanted to develop that. I recall that I posted some links on how to use ppp for pppoe, but noone took up the offer to investigate it.
Here is the blog post:
http://puppylinux.com/blog/?p=11
at home with new Compaq laptop
Posted: Fri 28 Dec 2007, 01:36
by raffy
(Forget about the difficult Compaq PC - John Doe already showed a HOWTO, just update its BIOS.)
Dingo feels at home in a new Compaq Presario laptop with SATA, and USB flash devices happily mount/unmount together with the SATA and DVD-RW drives.
The network devices were automatically detected: the broadcomm wifi as eth0 and the ethernet as eth1. (eth0 for wifi - that's new to me.) No way to test wifi now (no networks available), but in Win$, its lighted button shows that it works, and it is lighted in Dingo barebones.
Posted: Fri 28 Dec 2007, 05:33
by Lobster
BarryK wrote:
Actually, I reckon I'll put those two Xorg packages in the next barebones, as they're not very big and the vast majority of users will prefer Xorg rather than Xvesa. Or, at least I should put in xorg_xorg_base, as the 'vesa' server is better than Xvesa in many ways.
Good news.
Looking forward to a higher res . . .
I tried installing the suggested xorg drivers and then added the 3rd 'development' library, just in case. No luck, even with tweaking.
I am using a Nvidia Geforce 64MB card.
There is a command option (where it says -shadow) in xvesa
which might give me the option to type in 0x011A (which I believe is my higher xvesa res) but not quite sure if there is a prefix?
Netsurf works well enough to post this message from Dingo Alpha 4
Posted: Fri 28 Dec 2007, 05:52
by BarryK
Lobster, running your normal Puppy, not Dingo, what Xorg server is running? Look in /etc/X11/xorg.conf, at this line:
Driver "intel" #card0driver
...find what is in the quotes.
The 'xorg_xorg_servers' package currently only has:
i710, intel, neomagic, sis, trident and vesa
drivers at /usr/X11R7/lib/xorg/modules/drivers
so the correct driver for your Nvidia chip is not there.
Posted: Fri 28 Dec 2007, 06:17
by Lobster
Code: Select all
Identifier "Card0"
Driver "nv" #card0driver
VendorName "nVidia Corporation"
BoardName "NV18 [GeForce4 MX 440 AGP 8x]"
BusID "PCI:1:0:0"
Posted: Sat 29 Dec 2007, 00:02
by BarryK
Lobster, would you mind doing a little test.
1. Boot Barebones Dingo alpha4 with "puppy pfix=ram" boot parameter, then
2. choose 'Xvesa' for the video (not Xorg).
3. Place the attached file (gunzip it first) at /usr/X11R7/lib/xorg/modules/drivers/
4. Exit from X, run 'xorgwizard'.
You will probably need to download nv_drv.so.gz' now and place it somewhere local so you can use it after booting Barebones.
Find out if it works with the 'nv' driver. I mostly need to know if that driver will work as-is or whether it needs any other file. You can find out about this by examining the Xorg log file at:
/var/log/Xorg.0.log.
-- it will report if it tried to load something that is missing.
Also, if 'nv' was successfully chosen, then /etc/X11/xorg.conf will have it, as per your previous post.
Posted: Sat 29 Dec 2007, 00:29
by BarryK
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.
But, what about the eeePC? Raffy, would you mind trying it? I've attached it, run 'gunzip dmidecode', then maybe 'chmod 777 dmidecode', then just './dmidecode'.
Hopefully, in the "System" section it should identify manufacturer/product names. Any text string that has something like "eeePC" in it it would be great.
Also, Dougal mentioned using 'lspci -vv' to identify the eeePC. Raffy, would you also mind posting the result of running that?
Posted: Sat 29 Dec 2007, 02:02
by JustGreg
Hi Barry, Happy New Year to all!
Attach is the test results in gzip text file. I used Puppy 2.14R 1.01 with Eee PC Model 4G (701) for the test. Hope this helps.
Posted: Sat 29 Dec 2007, 02:16
by JustGreg
Here is the lspci information for your use. I have tested also Dougal's changes for 800 x 480 resolution with Puppy 2.14R 1.01 and had some success.
Posted: Sat 29 Dec 2007, 05:52
by Lobster
BarryK wrote:Lobster, would you mind doing a little test.
1. Boot Barebones Dingo alpha4 with "puppy pfix=ram" boot parameter, then
2. choose 'Xvesa' for the video (not Xorg).
3. Place the attached file (gunzip it first) at /usr/X11R7/lib/xorg/modules/drivers/
4. Exit from X, run 'xorgwizard'.
.
there was no
/modules/drivers/
in
/usr/X11R7/lib/xorg/
. . . so put it in
/usr/X11R7/lib/xorg/
and created /usr/X11R7/lib/xorg/modules/drivers/
and put in there too
Find out if it works with the 'nv' driver. I mostly need to know if that driver will work as-is or whether it needs any other file. You can find out about this by examining the Xorg log file at:
/var/log/Xorg.0.log.
no such file created
-- it will report if it tried to load something that is missing.
Also, if 'nv' was successfully chosen, then /etc/X11/xorg.conf will have it, as per your previous post
when running xorgwizard no horizontal or vertical hz was set
Code: Select all
#Special base config file used in Puppy Linux.
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"
# This loads the DBE extension module.
Load "dbe" # Double buffer extension
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
# This loads the font modules
Load "type1"
Load "freetype"
# This loads xtrap extension, used by xrandr
Load "xtrap"
# This loads the GLX module (if present)
Load "glx"
# This loads dri module (if present)
Load "dri"
EndSection
# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
RgbPath "/usr/X11R7/lib/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
FontPath "/usr/X11R7/lib/X11/fonts/misc/"
FontPath "/usr/X11R7/lib/X11/fonts/Type1/"
FontPath "/usr/X11R7/lib/X11/fonts/TTF/"
EndSection
# **********************************************************************
# Server flags section.
# **********************************************************************
Section "ServerFlags"
# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# Enables mode switching with xrandr
# There is a report that this can cause Xorg not to work on some
# video hardware, so default is commented-out...
# but i want to use it in xorgwizard so leave on...
Option "RandR" "on"
EndSection
#everything past here is auto-generated by Puppy's Xorg Wizard...
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
Subsection "Display"
Depth 24
Modes "1280x1024"
EndSubsection
EndSection
#PuppyHardwareProfile=NVIDIAAOCa780
that last bit is wrong
#PuppyHardwareProfile=NVIDIAAOCa780
it is NVIDIAAOCa940 (something like that with a 9 in it)
results
Posted: Sat 29 Dec 2007, 13:19
by raffy
Just back from trip. JustGreg's dmidecode is identical to what I got, but for lspci, i used "lspci -v" only (verbose option), attached.
Posted: Sun 30 Dec 2007, 00:56
by BarryK
there was no
/modules/drivers/
Lobster,
Oops, sorry, I made a mistake in my instructions. You needed to have the 'xorg_xorg_base' and 'xorg_xorg_servers' packages also installed.
Well, I'll put the 'nv' driver into the 'xorg_xorg_servers' package, so you can test the next release of Dingo and find out if the nv driver works okay, without having to install anything extra.
Posted: Sun 30 Dec 2007, 04:49
by Lobster
The Dingo is Wild!
added the two xorg files
and running in Firefox (had to add that from the .pet package installer) at 1024x1280 in Alpha 4 using xorg
enclosed xorg0 file