Puppy Linux Discussion Forum

[Colonel Panic]

[scsijon]

Folks, I am halting all testing for about one week while I rebuild a few packages that need updating for the new kernel, gtk problems are ocurring! This was not expected.

I shall report when it's fixed and will bring out a new Mage2 Alpha, numbered as 1.9.88

regards
scsijon

[Colonel Panic]

OK, fair enough but here's the xerrs.log file anyway;


X.Org X Server 1.11.4
Release Date: 2012-01-27
X Protocol Version 11, Revision 0
Build Operating System: Linux_2.6.38.8-server-10.mga Mageia
Current Operating System: Linux puppypc4828 3.3.8-mage2-p64gsw-i586 #1 SMP PREEMPT Sat Sep 1 16:47:42 GMT-8 2012 i686
Kernel command line: video=800x600
Build Date: 02 March 2012 06:41:02PM

Current version of pixman: 0.24.4
Before reporting problems, check http://bugs.mageia.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Sep 16 14:25:00 2012
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
FATAL: Module fbcon not found.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
cat: /sys/block/fd0/device/vendor: No such file or directory
cat: /sys/block/fd0/device/model: No such file or directory
/usr/bin/jwm
Playing Sparc Audio '/usr/share/audio/2barks.au' : Mu-Law, Rate 8000 Hz, Mono
Test if connected to internet...Network is ready.
sh: logger: command not found
mkdir: cannot create directory `/root/.config/cwallpaper': File exists
No config file found, using internal defaults (Hope you have fbsetbg ).
Loading
PING 8.8.8.8 (8.8.8.: 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=46 time=33.713 ms

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 33.713/33.713/33.713 ms
PING www.google.com (173.194.67.147): 56 data bytes
64 bytes from 173.194.67.147: seq=0 ttl=46 time=33.470 ms

--- www.google.com ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 33.470/33.470/33.470 ms
Setting the wallpaper to: /usr/share/backgrounds/wary_stu90.jpg
Using the program /usr/sbin/set_bg.
Quiting peaceablly
/usr/sbin/download_file: line 58: 22009 Terminated Xdialog --wmclass "gtkdialog2" --title "$(gettext 'Testing file exists:') ${URLSPEC}" --tailbox /tmp/download_file_spider.log1 30 100
tail: unrecognized file system type 0x61756673 for `/tmp/download_file_spider.log2'. please report this to bug-coreutils@gnu.org. reverting to polling

(abiword:23070): GdkPixbuf-WARNING **: Bug! loader 'png' didn't set an error on failure

(abiword:23070): GdkPixbuf-WARNING **: Bug! gdk-pixbuf loader 'png' didn't set an error on failure.

** (abiword:23070): WARNING **: Unable to load AbiWord icon: Failed to load image '/usr/share/icons/abiword_48.png': reason not known, probably a corrupt image file


(abiword:23156): GdkPixbuf-WARNING **: Bug! loader 'png' didn't set an error on failure

(abiword:23156): GdkPixbuf-WARNING **: Bug! gdk-pixbuf loader 'png' didn't set an error on failure.

** (abiword:23156): WARNING **: Unable to load AbiWord icon: Failed to load image '/usr/share/icons/abiword_48.png': reason not known, probably a corrupt image file


(abiword:23156): Gtk-CRITICAL **: gtk_window_set_title: assertion `GTK_IS_WINDOW (window)' failed

(abiword:23156): Gtk-CRITICAL **: gtk_label_set_text_with_mnemonic: assertion `GTK_IS_LABEL (label)' failed

(abiword:23156): Gtk-CRITICAL **: gtk_label_set_text_with_mnemonic: assertion `GTK_IS_LABEL (label)' failed

(abiword:23156): Gtk-CRITICAL **: gtk_button_set_use_underline: assertion `GTK_IS_BUTTON (button)' failed

(abiword:23156): Gtk-CRITICAL **: gtk_button_set_label: assertion `GTK_IS_BUTTON (button)' failed

(abiword:23156): Gtk-CRITICAL **: gtk_button_set_use_underline: assertion `GTK_IS_BUTTON (button)' failed

(abiword:23156): Gtk-CRITICAL **: gtk_button_set_label: assertion `GTK_IS_BUTTON (button)' failed

(abiword:23156): Gtk-CRITICAL **: gtk_button_set_use_underline: assertion `GTK_IS_BUTTON (button)' failed

(abiword:23156): Gtk-CRITICAL **: gtk_button_set_label: assertion `GTK_IS_BUTTON (button)' failed

(abiword:23156): Gtk-CRITICAL **: gtk_button_set_use_underline: assertion `GTK_IS_BUTTON (button)' failed

(abiword:23156): Gtk-CRITICAL **: gtk_button_set_label: assertion `GTK_IS_BUTTON (button)' failed

(abiword:23156): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(abiword:23156): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(abiword:23156): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(abiword:23156): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(abiword:23156): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(abiword:23156): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(abiword:23156): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(abiword:23156): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(abiword:23156): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(abiword:23156): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(abiword:23156): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(abiword:23156): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(abiword:23156): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(abiword:23156): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(abiword:23156): Gtk-CRITICAL **: gtk_tree_view_set_model: assertion `GTK_IS_TREE_VIEW (tree_view)' failed

(abiword:23156): Gtk-CRITICAL **: gtk_tree_view_insert_column_with_attributes: assertion `GTK_IS_TREE_VIEW (tree_view)' failed

(abiword:23156): Gtk-CRITICAL **: gtk_tree_view_get_column: assertion `GTK_IS_TREE_VIEW (tree_view)' failed

(abiword:23156): Gtk-CRITICAL **: gtk_tree_view_column_set_sort_column_id: assertion `GTK_IS_TREE_VIEW_COLUMN (tree_column)' failed

(abiword:23156): Gtk-CRITICAL **: gtk_tree_view_get_selection: assertion `GTK_IS_TREE_VIEW (tree_view)' failed

(abiword:23156): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(abiword:23156): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(abiword:23156): Gtk-CRITICAL **: gtk_widget_show_all: assertion `GTK_IS_WIDGET (widget)' failed

(abiword:23156): Gtk-CRITICAL **: gtk_dialog_set_default_response: assertion `GTK_IS_DIALOG (dialog)' failed

(abiword:23156): Gtk-CRITICAL **: gtk_window_set_modal: assertion `GTK_IS_WINDOW (window)' failed

(abiword:23156): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed

(abiword:23156): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(abiword:23156): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(abiword:23156): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(abiword:23156): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(abiword:23156): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(abiword:23156): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(abiword:23156): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(abiword:23156): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(abiword:23156): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed

(abiword:23156): Gtk-CRITICAL **: gtk_dialog_get_action_area: assertion `GTK_IS_DIALOG (dialog)' failed
Generating /root/.icewm/menu...
Generating /root/.jwmrc...

[scsijon]

YUP, another GdkPixbuf-WARNING problem, I thought so!

I'm going to use a couple of the old packages, which worked ok, and update a number of others to suit the kernel so were in a halt mode at present for mage2, a couple of weeks more should sort it all out. Depending on how much I do will decide whether another alpha is required or just a beta.

regards and thanks for everyone's patience with this.

scsijon

[scsijon]

I decided in the end to update my woof2 and start again with mage2 after it would not build a stable mage2 after the woof2 update. A lot of changes were needed to sort it out.

I plan on releasing an alpha this weekend and will leave notes on what's what at the time.

[scsijon]

We are up and running again after some changes.

Woof has been twice updated to the 18 Dec 1600 version

Mageia2's packages have been updated to the 20 Dec 2012 set

Build codes have been reset. I restarted as mage2-0000 (raw build with the old beta 1995 package dataset) and have so far got up to mage2-0002 with problem fixes.

At this point we have the following problems:

1- the old thumbnails problem (desktop icon switcher nor displaying icons of sets), a few trials of changes has done nothing and i'm considering rebuilding rox-filer next on the alpha to see if that fixes it.

2- ppm problem 1 (puppy-2 is stuck on and can't be unmarked in the config screen

3- ppm problem 2 (it's only displaying the mail mageia 2 sets, ie core and not also core-updates, even when core-updates is ticked in the configure screen and we are restarted

4- ppm problem 3 (downloading a new set of databases sets the 7th field in a xxx-updates as updates/release instead of xxx/updates

ppm problems I suspect may need a barryk fix

5- xorg autostart is turned off as i'm getting unreliability in the monitor mode being picked as default, however at least it's picking vesa if it can't work out what driver to use. However I think I do prefer setting it up manually.

My local 'primary' testers are reporting that this one seems to be faster than the old mage2-1995 beta and is definately using less memory and maybe less cpu, although i'm not sure that it's not in the mind.

We shall 'play' with it for another week before releasing a first alpha (mage2-0010) for 'open testing'.

regards and a merry christmas to all

ps using a 0002 frugal for this post

[futwerk]

here are a few backgrounds and a mobile.

[scsijon]

Announcement and release notes for Mage2 0.0.10

Mage2 is built from a "Puppy builder" system named Woof (http://bkhome.org/woof), which can build a Puppy Linux distribution from the binary packages of any other distro. There are many other "puppies" built with Woof, including Lucid, Wary, Racy, FatDog, and Slacko.
Each "Puppy distro" built by Woof is a distinctive distribution in its own right, with unique features. You should choose a puppy based on your particular needs, be it specific hardware, software, or access to and compatibility with the package repositories of a particular major distro. Woof highlights can be found here.

BETA Mage2 Puppy 0.0.10
Mage2 Puppy is built from Mageia2's packages, hence has binary compatibility with Mageia2 and access to the vast Mageia package repository. It's also built with the Designer and Packager in mind with a number of basic builder components already installed which is why it's not the smallest of Puppies.

This is hopefully the last Beta for the first full release of Mage2 Puppy. It is assigned version 0.0.10 to indicate it's a bugfix prerelease version rather than either a minor step up (2nd digit 1.x), or bugfix (3rd digit set 1.0.xx).

A lot of work has happened at the "Woof-level" since the original alpha releases of Mage2, especially with Woof2's creation and upgrades starting back in April 2012.

The murga-linux Thread for Mage2 can be found here, with Download links in the top Section of the first page and Mage2-0.0.10 starting from page 10.

EDIT: For those with nvidea video, please use vesa to start with and download a nvidea driver from either the nonfree or tainted repositories, I didn't add one into the default set by mistake. It will be added into the next beta.

Release Notes

Mage004 and Mage008 - Pre-May 2012 - The first stable builds of Mage2 and were built on the origonal Woof. There were a few others in this stream but...

Mage2-1881 to Mage2-1996 - Various builds using an early Woof2, some were ok while others were disasters, but problems were slowly worked through.

Mage2-0.0.01 to Mage2-0.0.08 - Various internal alpha builds using a Woof2 of 16 December 2012. Most of the problems had already been fixed in the last series, this was basically bringing Woof2 up to date, to fix woof related issues, change the release coding into puppy standard and dealing with the few problems that were still residing.

Mage2-0.0.10 - This Beta. I have no problems left, knock wood, in my problem list that have not been either resolved or a 'work-around' is in operation, this is why it's being released into the community for a wider range of testing. If nothing major has been found by the end of January 2013, it is planned to be the Mage2-1.0.0 Release base. Meanwhile I shall just be 'cleaning up' and working on my qtpy CutePuppy.

Theme
Mage2 has been built with the 'gradient-brown' GTK theme, 'gradient-bluish' JWM theme, 'Smooth-colour' desk icons and an old puppy Blue Waterglass 'default42.jpg' wallpaper (?can anyone remember where this origonated) to show it's pre-release. Futwerk, one of our wallpaper experts and with my many thanks for working over the hollidays, is working on a few Release wallpapers for me.

If you are curious how themes are created for Puppy, read the Themes Intro. page, lots of themes are already available for installation in the 'noarch' repository in the PPM as well as in individual repositories.

The Mage2 3.3.8-mage2-p64gsw-i586 Kernel

The 3.3.8 kernel used in Mage2 Puppy has been specifically built and configured with quite a lot of extra components. This was done to allow users to both 'play' with devices not normally considered for a computer, and expand what Puppy can do. The following is a rough list of what has been allowed for.

p - The Kernel is a preemptive one. This means that it can pre-load data blocks that it thinks are going to be used next into it's caches before they are actually asked for by the program running.

64 - The Kernel has been set as PAE, which means that if the CPU is an i686+ it gains access to the PAE functions, although it still works quite happily without. Be aware that some CPUs in the early days of the i686 architecture are none-PAE enabled, a very small percentage of the overall number of i686+ computers currently in use. Note: "PAE" also enables the kernel to support a computer with more than 4GB of RAM and in this case I have set it to handle up to 64GB.

i586 - The Kernel has been built for a i586 or later CPU. I had considered i486 but decided against it as it would make most of the other settings I wanted unuseable.

The Kernel is configured for multiple cores, in fact it's set to deal with a total of 16 so a motherboard capable of handling multi-processors with multiple cores should be able to use the 'rest of them' without any problems if the software can.

The Kernel has been set to directly interface with the Andrew (NAS) Filesystem, the BTRFS Filesystem, and Raid4 to Raid6, as well as the usual 'lot'.

g - The kernel has been enabled for USB Gadgets to work, so almost anything with a usb connection could be tried. I have also turned on most of the sub-sets so just about anything should 'work' after a 'modprobe', but you may need some interface software. It can also handle 16 usb monitors for those 'screen walls' and Barcode Readers for a POS System.

For Laptops, it has both Backlight and LED Contrast Level control enabled.

s - The Kernel has also been enabled to interface directly with Onboard Speach Synthesis Chips or control Speach Synthesis processor Plug-in Boards when installed.

w - And finally the kernel has been configured to handle both input and output Braile Devices so that the blind or those teaching blind people should be able to connect their devices through any of the standard serial, parallel, usb, ethernet and mouse/keyboard interfaces found on a computer. After running 'modprobe' to create and add the drivers for the new devices, installing any extra software plugins necessary, they should be able to use any of the braile enabled linux or puppy packages available.

These last two settings were two of the main reasons why I built Mage2.


Have fun
scsijon

[01micko]

No go for me I'm afraid with nvidia hardware.

There is no nouveau xorg driver or nv xorg driver. Vesa fails for me with either "out of range" on monitor or a system crash.

[xstylezx]

same exact error for me. i got it booted up from another computer though with an onboard intel. nowadays seems like its a must to have nouveau driver present

[James C]

Same results here too.

[davids45]

G'day,
I thought I'd try Mage-2.0.0.10, so did a manual frugal install (mounted the iso and copied the files to a fresh mage subdirectory).

Computer is a desktop (2-core) with a radeon HD5450 graphics card. It has an el-cheapo standard 1600x900 LED monitor.

I was unable to boot to X during video selection with the listed ati radeon driver when using "Choose" and selecting it.

Only working boot I managed was using vesa (of course, distorted to 1280x1050). Attempts to then use videowizard to upgrade failed, losing any X capability and no reboot to the original vesa display either. A 1600x900 option was not listed by the wizard.

Deleting the first, faulty video Save file and starting again with vesa at these wrong display dimensions, I re-booted to create a Save file, re-booted again and when the vesa display opened, I immediately installed a proprietary ATI-fglrx driver (using a Precise pet) which worked on restarting X - display now sharp and 1600x900 .
But on re-booting, no display, just the xorgwizard text and no success in getting any X display .

During the first vesa tests, I did get as far as loading Libre Office (sfs) but could not set the options for templates, temp and documents to my data partition (on sda5) - seemed stuck on /root despite apparently accepting /sda5/xxx as the location for the templates, temp and documents.
A freeze occurred which I put down to maybe an old jwm version in this Pup so on restarting, I installed the very latest jwm pet. Seemed to be OK.
Another minor issue was that I was also unable to get my seamonkey profile to load properly, which is also held on my sda5 data partition (mail wouldn't download). My Libre Office and Seamonkey set-ups work perfectly with almost all other Pups (Full and Frugal).

But the failure of any radeon graphics was the real problem in my frugal tests.

David S.

[01micko]

Ok, got nouveau driver downloaded beforehand, installed it and I got a nice desktop.

Couple of problems, no sound, but I have finicky sound anyway, if I had more time I could probably get it working.. no mplayer? Wasn't connected at boot, but easily connected.. ethernet.

One other thing, pfix=nox didn't work, must be a woof introduced bug.

[Billtoo]

I did a manual frugal install to my acer desktop.

Mage2, version 0.0.10 on Sun 6 Jan 2013
Chip description:
X Server: Xorg
Driver used: modesetting
X.Org version: 1.11.4
dimensions: 1440x900 pixels (380x238 millimeters)
depth of root window: 24 planes
Computer
Processor 4x Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Memory 8233MB (118MB used)
Operating System Unknown distribution
User Name root (root)
Date/Time Sun 06 Jan 2013 01:56:09 AM EST
Version
Kernel Linux 3.3.8-mage2-p64gsw-i586 (i686)
Compiled #1 SMP PREEMPT Sat Sep 1 16:47:42 GMT-8 2012
C Library GNU C Library version 2.14.1 (stable)
Default C Compiler Unknown
Distribution Unknown distribution
OpenGL
Vendor Unknown
Renderer Unknown
Version Unknown
Direct Rendering No

I did an install earlier and installed the proprietary nvidia driver
and made a bunch of pets, that went bad somehow with all the icons
turning to triangles with a ? in the center of them.
This install is just what I got when it went to the desktop and I
created a new save file and installed the pets that I had made earlier.
It seems to be working okay now after several reboots and increasing
the size of the save file etc.

I have two monitors attached to this computer but without the
proprietary nvidia driver monitor 2 is just a clone of monitor 1.

Monitors
Monitor 0 1440x900 pixels
Monitor 1 1440x900 pixels

My graphics card is an Nvidia Geforce 8600 GT

[scsijon]

OK, so I need to have a nv driver of some sort in the makeup!

Wierd that the vesa didn't work as it does with the nv card I have on a testbox, maybe it's the age. I shall upload one or two in the morning for people to test (please) and include one in the next beta.

ATI should have been ok as the driver is a 6.14.4 and works on both another of my test boxes as well as 2 of my alpha testers boxes. What version was your proprietry driver please?

Can all with video problems check /tmp/xerrs.log and if anything is there attach a copy.

I admit I didn't expect any video problems as we tested it on quite a range, both locally as well as a mix the local school.