Fatdog64-620 Final (17 April 2013) and 621 (9 May 2013)

A home for all kinds of Puppy related projects
Message
Author
DrDeaf
Posts: 69
Joined: Sat 30 Dec 2006, 14:10

#401 Post by DrDeaf »

jamesbond wrote: @DrDeaf: please provide output of "lspci". I checked lenovo site for x320t and it doesn't tell me which ethernet card it uses.
cheers!
Hi there! Thank you for your reply!
First off, I hope I correctly typed that the notebook is a X230t...
I am now back in the USA for a couple of months and I can tell you that it appears (I just got in yesterday) that the router or something else may play a part. Here, I can "shop" connections easily and at first look I think there may not be a problem here.... There will be a very busy time for a bit but I will get back with more info.

Also, I will send the output you want.

Again, thank you very much! :D

youngk
Posts: 1
Joined: Sun 01 Sep 2013, 04:00

Creating Fatdog PET for AMD Catalyst drivers 13.8 beta

#402 Post by youngk »

I have a newer AMD chip that isn't supported in the 13.4 released version of AMDs proprietary catalyst drivers. It runs with the 13.4 pet for Fatdog 620/621, but not well (dual monitor setup).

I've been trying unsuccessfully to package the 13.8 beta version in a pet but haven't succeeded. Does anybody have instructions or a script for this?

When I run AMD's Catalyst installer it's recognizing Fatdog as a Slackware distro, not sure if that's correct or not. I noticed AMD's installer is putting files in different locations than the fatdog pet. I've tried building a pet but so far no luck.

DrDeaf
Posts: 69
Joined: Sat 30 Dec 2006, 14:10

#403 Post by DrDeaf »

jamesbond wrote: @DrDeaf: please provide output of "lspci".
Sorry about doubling the previous post... :oops: On screen it appeared that the first send stalled. So, I re-did it and now I see it up twice!

First, here is the output of lspci:

00:00.0 Host bridge: Intel Corporation Device 0154 (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Device 0166 (rev 09)
00:14.0 USB Controller: Intel Corporation Device 1e31 (rev 04)
00:16.0 Communication controller: Intel Corporation Device 1e3a (rev 04)
00:19.0 Ethernet controller: Intel Corporation Device 1502 (rev 04)
00:1a.0 USB Controller: Intel Corporation Device 1e2d (rev 04)
00:1b.0 Audio device: Intel Corporation Device 1e20 (rev 04)
00:1c.0 PCI bridge: Intel Corporation Device 1e10 (rev c4)
00:1c.1 PCI bridge: Intel Corporation Device 1e12 (rev c4)
00:1c.2 PCI bridge: Intel Corporation Device 1e14 (rev c4)
00:1d.0 USB Controller: Intel Corporation Device 1e26 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Device 1e55 (rev 04)
00:1f.2 SATA controller: Intel Corporation Device 1e03 (rev 04)
00:1f.3 SMBus: Intel Corporation Device 1e22 (rev 04)
02:00.0 System peripheral: Ricoh Co Ltd Device e823 (rev 07)
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device 8176 (rev 01)

Now that I have a quiet, more deliberate opportunity to test, I am thinking this situation is completely on the machine. The Thinkpad has a physical, slide switch which enables/disables wireless. So, when I write that wireless is “on

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

Fatdog64-620 Final (17 April 2013) and 621 (9 May 2013)

#404 Post by Billtoo »

I installed fatdog 621 to a 32gb MicroSDHC card which is plugged into
a usb card reader, computer is a Lenovo ThinkCentre.

video-info-glx 1.5.3 Sun 8 Sep 2013 on Fatdog64 620 Linux 3.8.7 x86_64
2.0 VGA compatible controller:
Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
oem: Intel(r)Eaglelake Graphics Chip Accelerated VGA BIOS
product: Intel(r)Eaglelake Graphics Controller Hardware Version 0.0
X Server: Xorg Driver: intel
X.Org version: 1.12.4
dimensions: 1920x1080 pixels (508x285 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) G41
OpenGL version string: 2.1 Mesa 9.1.1
Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
Core 0: @2003 1: @2003 MHz
Memory 4015MB (264MB used)
Linksys WUSB54GC 802.11g Adapter [ralink rt73]

It's working well.

EDIT:The wireless connection was giving problems so I moved my card
reader to another pc which is connected to the wired network.
I made use of zarfy as well, it's working fine now.

X Server: Xorg Driver: intel
X.Org version: 1.12.4
dimensions: 3840x1080 pixels (508x285 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Desktop
OpenGL version string: 3.0 Mesa 9.1.1
Attachments
screenshot2.jpg
(29.78 KiB) Downloaded 1278 times
screenshot.jpg
(59.85 KiB) Downloaded 1486 times

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#405 Post by jamesbond »

youngk wrote:I have a newer AMD chip that isn't supported in the 13.4 released version of AMDs proprietary catalyst drivers. It runs with the 13.4 pet for Fatdog 620/621, but not well (dual monitor setup).
Please do "lspci" when you're on terminal so we know what cards you're using and perhaps can include the firmware in next Fatdog release.
I've been trying unsuccessfully to package the 13.8 beta version in a pet but haven't succeeded. Does anybody have instructions or a script for this?
Unfortunately no, it is rather a manual process at the moment. I have my terse notes but my hand is currently too full to write a full-fledged FAQ on how to do this (you can have my terse notes but I'm sure it will only brings up more questions than answers).
When I run AMD's Catalyst installer it's recognizing Fatdog as a Slackware distro, not sure if that's correct or not. I noticed AMD's installer is putting files in different locations than the fatdog pet. I've tried building a pet but so far no luck.
Yes it will think that Fatdog is Slackware-based but it is *not* and it will install files to the wrong directories (mainly graphic driver files needs to be in /usr/X11R7/lib64 instead of /usr/lib64) which will require relocation.

If you can wait a little while, we'll get the next latest Catalyst driver out with the next Fatdog release.
DrDeaf wrote:Cold boot with eth0 not connected to the router:
With wireless on (not connected) eth0 fails as described before.
With wireless off, and after boot eth0 is then connected, Network Wizard loads module e1000e successfully.

Cold boot with eth0 connected to the router:
With wireless switched either way (on/off) the module e1000e loads successfully at boot.
After boot, subsequently removing the eth0 connection to router and then using wpa_gui to connect wireless works.
After then switching wireless to off, the eth0 reconnect to router is successful.
Thank you DrDeaf. This is the first time that I see that wireless and ethernet are dependent on each other - one has to be turned off for others to work. Usually what happens is that both connection will work but one has to configure the IP routing properly (as the computer will effectively become a dual-homed machine with both eth0 and wlan0 are connected).

cheers!
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

User avatar
Ted Dog
Posts: 3965
Joined: Wed 14 Sep 2005, 02:35
Location: Heart of Texas

Re: Fatdog64-620 Final (17 April 2013) and 621 (9 May 2013)

#406 Post by Ted Dog »

Billtoo wrote:I installed fatdog 621 to a 32gb MicroSDHC card which is plugged into
a usb card reader, computer is a Lenovo ThinkCentre.

video-info-glx 1.5.3 Sun 8 Sep 2013 on Fatdog64 620 Linux 3.8.7 x86_64
2.0 VGA compatible controller:
Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
oem: Intel(r)Eaglelake Graphics Chip Accelerated VGA BIOS
product: Intel(r)Eaglelake Graphics Controller Hardware Version 0.0
X Server: Xorg Driver: intel
X.Org version: 1.12.4
dimensions: 1920x1080 pixels (508x285 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) G41
OpenGL version string: 2.1 Mesa 9.1.1
Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
Core 0: @2003 1: @2003 MHz
Memory 4015MB (264MB used)
Linksys WUSB54GC 802.11g Adapter [ralink rt73]

It's working well.

EDIT:The wireless connection was giving problems so I moved my card
reader to another pc which is connected to the wired network.
I made use of zarfy as well, it's working fine now.

X Server: Xorg Driver: intel
X.Org version: 1.12.4
dimensions: 3840x1080 pixels (508x285 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Desktop
OpenGL version string: 3.0 Mesa 9.1.1

Looks just like my ranch... :wink:

gcmartin

#407 Post by gcmartin »

Having problems getting one of lappies to enable wireless and detect availables.
I could use some steering on enabling the Wireless in this system.

Here my system's info

Code: Select all

# ip addr > lspci.txt
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:23:8b:e1:21:93 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.3/24 brd 192.168.1.255 scope global eth0
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq qlen 1000
    link/ether 00:21:00:eb:2c:6e brd ff:ff:ff:ff:ff:ff

# lspci >> lspci.txt
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge
00:01.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (int gfx)
00:04.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 0)
00:05.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 1)
00:06.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 2)
00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode]
00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:12.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:13.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3a)
00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge
00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 11h HyperTransport Configuration (rev 40)
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 11h Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 11h DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 11h Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 11h Link Control
01:05.0 VGA compatible controller: ATI Technologies Inc RS780M/RS780MN [Radeon HD 3200 Graphics]
08:00.0 Network controller: Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)
09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)

# dmesg
	o
	o
	o
	o
	o
	o
ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
	o
I have already gone into FATDOG Services and enabled&started BC WL, but the scan for wireless is still coming up empty using FATDOG.

gcmartin

An idea for upcoming FATDOG's Service Manager

#408 Post by gcmartin »

I know and understand the reason development decided to NOT activate the SWAP partition when present. But, would it be in user best interest to include a setting in FATDOG service manager to Enable it for detection and use upon reboot?

This would help the many who missed this until too late when RAM fills. It would negate the need to constantly use the SWAPON command.

An idea for ease of use.
Edit; 2nd paragraph into 2 sentences
Last edited by gcmartin on Mon 09 Sep 2013, 23:38, edited 1 time in total.

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

Fatdog64-620 Final (17 April 2013) and 621 (9 May 2013)

#409 Post by Billtoo »

I used the fatdog installer to install to a 16gb SDHC card, computer
is an Acer desktop.
video-info-glx 1.5.3 Mon 9 Sep 2013 on Fatdog64 620 Linux 3.8.7 x86_64
0.0 VGA compatible controller:nVidia Corporation G84 [GeForce8600GT](rev a1)
oem: NVIDIA
product: G84 Board - p402h00 Chip Rev
X Server: Xorg Driver: nvidia
X.Org version: 1.12.4
dimensions: 1920x1080 pixels (513x292 millimeters)
depth of root window: 24 planes
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce 8600 GT/PCIe/SSE2
OpenGL version string: 3.3.0 NVIDIA 319.49
Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Core 0: @1603 1: @1603 2: @1603 3: @1603 MHz
Memory 8178MB (453MB used)
Ethernet controller Intel Corporation 82566DC-2 Gigabit Network Connection
(rev 02)
Attachments
screenshot.jpg
(55.47 KiB) Downloaded 1578 times

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

#410 Post by Billtoo »

jamesbond wrote:
youngk wrote:I have a newer AMD chip that isn't supported in the 13.4 released version of AMDs proprietary catalyst drivers. It runs with the 13.4 pet for Fatdog 620/621, but not well (dual monitor setup).
Please do "lspci" when you're on terminal so we know what cards you're using and perhaps can include the firmware in next Fatdog release.
I've got an ati card that isn't supported:

video-info-glx 1.5.3 Tue 10 Sep 2013 on Fatdog64 620 Linux 3.8.7 x86_64
0.0 VGA compatible controller:Advanced Micro Devices [AMD]nee ATI Device 6611
oem: AMD ATOMBIOS
product: OLAND 01.00

The 13.4 driver just said the card wasn't supported, the 13.8 beta2
driver compiled but after doing aticonfig --initial and rebooting it
gave several errors and wouldn't go to the desktup so I uninstalled it
and rebooted to get back to normal.

This is what it's using now:

X Server: Xorg Driver: vesa
X.Org version: 1.12.4
dimensions: 1920x1080 pixels (524x292 millimeters)
depth of root window: 24 planes

direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.0, 128 bits)
OpenGL version string: 2.1 Mesa 9.1.1

Radeon™ HD 8570 graphics card with 2GB DDR3 dedicated memory(Up to 7830MB)
Thanks

Gobbi
Posts: 255
Joined: Fri 09 Mar 2012, 14:01

#411 Post by Gobbi »

Billtoo , From your posted screenshot I can see you managed to make work Pwidgets with FD620 . Previously I did it on FD610 , but using the same pet didn't give the same result ( different kernel , I think ).
Did you use a new pet ?

User avatar
Billtoo
Posts: 3720
Joined: Tue 07 Apr 2009, 13:47
Location: Ontario Canada

#412 Post by Billtoo »

Gobbi wrote: Billtoo , From your posted screenshot I can see you managed to make work Pwidgets with FD620 . Previously I did it on FD610 , but using the same pet didn't give the same result ( different kernel , I think ).
Did you use a new pet ?
No, it's not a new pet, the only thing that would work is the clock which is all I really wanted so that was okay.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#413 Post by rcrsn51 »

Here is PeasyDisc v1.6 for Fatdog. I have also attached the Extras package for making DVD slideshows.

[Edit] Here is PeasyDisc v2.0 for Fatdog with Blu-ray support. Read here.
Attachments
peasydisc_fd620-2.0.pet
Updated 2013-10-16
(6.02 KiB) Downloaded 703 times
peasydisc_extras_fd620-1.0.pet
(66.04 KiB) Downloaded 743 times
Last edited by rcrsn51 on Thu 17 Oct 2013, 01:25, edited 4 times in total.

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#414 Post by jamesbond »

gcmartin wrote:

Code: Select all

# dmesg
ERROR @wl_cfg80211_scan : WLC_SCAN error (-22)
	o
I have already gone into FATDOG Services and enabled&started BC WL, but the scan for wireless is still coming up empty using FATDOG.
Try this one: https://bbs.archlinux.org/viewtopic.php ... 9#p1216309.
gcmartin wrote:But, would it be in user best interest to include a setting in FATDOG service manager to Enable it for detection and use upon reboot?
Fatdog Control Panel already has an applet to create a swapfile and configure it for use on the next boot automatically.
rcrsn51 wrote:Here is PeasyDisc v1.6 for Fatdog. I have also attached the Extras package for making DVD slideshows.
Much appreciated, this will be in Fatdog 630.
EDIT: Why the need for the extras? dvdauthor, pamscale and pnmpad are all in Fatdog already. Are they new versions?
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

Snail
Posts: 331
Joined: Sun 18 Oct 2009, 07:32

Time Zone won't reset

#415 Post by Snail »

I've just tried to reset the timezone, using Set System Timezone under Control Panel/Localization. It has no effect, either after restarting X, or rebooting. The symlink /etc/localtime gets reset correctly, but nothing else happens. I've tried several different time zones, none work. Oddly, I am sure that I have changed it at least once before. I'm dual-booting with win 7, so display time should = system time. So next I tried the option under Control panel/system/Set Date and Time. That worked, but very flakey. Initially I tried resetting by 1 hour and it worked after the expected brief black screen. Then I tried setting the exact time several times but nothing happened until I rebooted. Very weird!

I've just been playing with Radkey's Pupmenu. The program is supposed to start with [cntrl][shift][M] but doesn't. Works OK apart from that, except that the changes don't appear consistently in either the ghostly openbox menu or the LXPanel one. That may be because Pupmenu displays what is in the .desktop files and it seems that there are other factors involved, e.g. the openbox and lxpanel menus are not the same? PupMenu does have a way of getting stuff off the menu and onto the desktop though, which I was asking about earlier.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#416 Post by rcrsn51 »

jamesbond wrote:EDIT: Why the need for the extras? dvdauthor, pamscale and pnmpad are all in Fatdog already.
Pamscale and pnmpad are NOT in my copy of 621.

Dvdauthor is present, but it's broken. (I saw the same thing in Wary.) This is the version from Ubuntu Lucid 64-bit.

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#417 Post by jamesbond »

rcrsn51 wrote:
jamesbond wrote:EDIT: Why the need for the extras? dvdauthor, pamscale and pnmpad are all in Fatdog already.
Pamscale and pnmpad are NOT in my copy of 621.
My mistake, those two are in devx. I run with devx attached at all times, so I never miss them :)
Dvdauthor is present, but it's broken. (I saw the same thing in Wary.) This is the version from Ubuntu Lucid 64-bit.
Noted.

All in all, I'll get that in for 630. Thank you.
Snail wrote:I've just tried to reset the timezone, using Set System Timezone under Control Panel/Localization. It has no effect, either after restarting X, or rebooting. The symlink /etc/localtime gets reset correctly, but nothing else happens. I've tried several different time zones, none work. Oddly, I am sure that I have changed it at least once before. I'm dual-booting with win 7, so display time should = system time. So next I tried the option under Control panel/system/Set Date and Time. That worked, but very flakey. Initially I tried resetting by 1 hour and it worked after the expected brief black screen. Then I tried setting the exact time several times but nothing happened until I rebooted. Very weird!
Odd. Try rebooting without savefile and then change the timezone, see whether you get the correct result?
I've just been playing with Radkey's Pupmenu. The program is supposed to start with [cntrl][shift][M] but doesn't.
Haven't checked Pupmenu, but my guess the ctrl-shift-M hotkey is tied to JWM. Thus it has no effect on openbox. You can always re-configure the hotkey using sven if you wish (that little keyboard icon on the lxpanel).
Works OK apart from that, except that the changes don't appear consistently in either the ghostly openbox menu or the LXPanel one. That may be because Pupmenu displays what is in the .desktop files and it seems that there are other factors involved, e.g. the openbox and lxpanel menus are not the same?
In theory they should be identical although openbox's and lxpanel's menuing code are different, so expect some discrepancy. Can you give me an example of the discrepancy (using the standard out of the box programs if possible).

EDIT: In 620/621 the lxpanel and openbox menu is different. In 630 they will be the same again (the lxpanel menu will look like openbox's menu) (I forgot that I'm running FatdogNext in which the lxpanel menu has been "fixed", and this fix will be in 630).

cheers!
Last edited by jamesbond on Thu 12 Sep 2013, 18:32, edited 1 time in total.
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

User avatar
Ted Dog
Posts: 3965
Joined: Wed 14 Sep 2005, 02:35
Location: Heart of Texas

#418 Post by Ted Dog »

what happen to v622? Bigger changes? Any ETA on FD64-630..

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#419 Post by jamesbond »

Ted Dog wrote:what happen to v622? Bigger changes? Any ETA on FD64-630..
Last digit version number increase (620 to 621, 621 to 622) indicates bug-fix release, however in this case "622" is just a number we use to differentiate between the last public release (621) and the "testing stuff" (aka "Fatdog Next" aka "cooking" aka "trunk" aka "tip", etc). We could have stayed with 621 numbering but that would be confusing (to ourselves, see what I did to Snail's response above!) when our 621 isn't the same as public 621 8), and at the time we increased the version number there were no updates (other than bugfixes). There aren't any major bugs that warrants 622 release so it never got released.

Middle digit version number increase indicates updates, like 600 to 610, 610 to 620, etc. So the next planned release, which is an update to 620, is appropriately called 630. So from today onwards what we'll have is pre-630, no longer 622 8) (as if the name matters! :lol:)

630 would contain all changes so far, plus application, Xorg and kernel updates. ETA in about one month's time.

cheers!
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

User avatar
Ted Dog
Posts: 3965
Joined: Wed 14 Sep 2005, 02:35
Location: Heart of Texas

#420 Post by Ted Dog »

OK thanks for clearing that up. My very early IT job, my manager would use Alpha, Beta, Gamma etc as release ids but did so backward to the way IT releases are done today, Out first sample release where Alpha, next Beta, then Gamma, and a few Deltas ( most full releases where Delta )

Post Reply