(old)Puppy Linux Discussion Forum

Posted: **Tue 06 Aug 2013, 15:04**

don922 wrote: Why doesn't it boot?

What GRUB error code are you getting?

Is this a 64-bit computer? Have you run previous Fatdogs on it?

Posted: **Tue 06 Aug 2013, 16:30**

rcrsn51 wrote:What GRUB error code are you getting?

During the boot of Fatdog the computer crashes and locks up. I don't see any GRUB error code. How do I find it?

rcrsn51 wrote:Is this a 64-bit computer? Have you run previous Fatdogs on it?

[color=green]grep flags /proc/cpuinfo[/color] wrote:flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt pdpe1gb rdtscp *lm* 3dnowext 3dnow constant_tsc up nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt

The lm in the second line of this code indicates that this is a 64bit computer. I have not run any previous Fatdogs on it.
Hardinfo shows the processor to be a AMD Sempron(tm) 145 Processor which is advertised to be a 64bit processor.

Posted: **Tue 06 Aug 2013, 16:37**

This probably isn't a GRUB issue.

How much RAM?

Posted: **Wed 07 Aug 2013, 01:00**

Hardinfo shows memory as follows: Memory 1814MB (372MB used)

Posted: **Wed 07 Aug 2013, 02:45**

don922 wrote:I downloaded the Fatdog64-621.iso and the MD5sum is correct.
Using ISOMaster iso file editor I have extracted the following files from the Fatdog64-621.iso and put them in a new directory /mnt/home/puppy-fatdog-621:
fatdog.png
fix-usb.sh
initrd
vmlinuz
In a frugal installation the menulist is as follows:
title Puppy 528.005
rootnoverify (hd0,0)
kernel /puppy528.005/vmlinuz pmedia=satahd psubdir=puppy528.005 pfix=fsck nosmp
initrd /puppy528.005/initrd.gz

title Puppy 529
rootnoverify (hd0,0)
kernel /puppy529/vmlinuz pmedia=satahd psubdir=puppy529 pfix=fsck nosmp
initrd /puppy529/initrd.gz

title Fatdog 621
rootnoverify (hd0,0)
kernel /puppy-fatdog-621/vmlinuz pmedia=satahd psubdir=puppy-fatdog-621 pfix=fsck nosmp
initrd /puppy-fatdog-621/initrd
Initrd is shown as initrd.gz in Puppy 528.005 & Puppy 529. Fatdog 621 calls it just initrd.

The directories for Puppy 528.005 & Puppy 529 were prepared the same as Fatdog 621 and work fine.

What is wrong with what I've done with Fatdog 621? Why doesn't it boot?

For what it's worth,here's my menu.lst entry for Legacy Grub and Fatdog 621...in sda10,no directory , everything just in /mnt/home/ .

Code: Select all

title Fatdog 64 621 in sda10
root (hd0,9)
kernel /vmlinuz nouveau.noaccel=1
initrd /initrd

Posted: **Wed 07 Aug 2013, 07:21**

I have made some progress -- broke down and burned a cd. Can boot with cd by choosing the nvidia option to eliminate the nouveau driver in the cd boot menu.

Cannot boot from the frugal install. No Nvidia option to eliminate the nouveau driver.

Need an entry for menu.lst to eliminate the nouveau driver.

Code: Select all

kernel /puppy-fatdog-621/vmlinuz nouveau.noaccel=1

This menu.lst entry still allows the boot to kill any display on the monitor.

Need to find the Nvidia Driver Version 260.19.12 for 64bit similar to the one I use in puppy 528.005 and 529.

The video on the motherboard is a GeForce 6150SE.

Posted: **Thu 08 Aug 2013, 05:29**

DrDeaf wrote:
jamesbond wrote:This is what we have in the Fatdog-Next as of today. Still using the 600 as the base. I have this running for quite a while now. Let me know if anyone is interested.

Fatdog64-Next Release Notes
Changes from 621:
Updates:
-------------------
- Linux 3.9.4 with lxc support but without XFS support
-------------------
Maybe not the interest you wanted, but I am interested in XFS support.
Would that be possible?

621 and previous versions have XFS support right now, but the one I'm running is not. It is a choice because right now XFS conflicts with User Namespaces (that's the only filesystem left with a conflict, all others were resolved in 3.9). I will probably choose XFS over User Namespace for a public release. Waiting for 3.11 to go gold.

don922, just open the isolinux.cfg on the CD and you'll see the command to eliminate nouveau (it's "blacklist=nouveau"). Copy that into your boot loader config and that should work. I also found that "nouveau.noaccel=1" (suggested by James C) works for many cases. For GeForce 6150 SE I think you'll need to install the nvidia_legacy driver, but to be sure please check nvidia website.

Snail, when you click the "green checkbox", don't immediately move your mouse. Wait for a while. See if it helps to unmount your SD Card.

The USB safe-remove is mainly meant for mechanical portable disks, but they are safe to use for Flash drives too. Don't use them on "internal" card reader (ie Card reader built in to your laptop); otherwise after it has been removed you won't see them again until next boot. Using them on external card readers are fine because you can just unplug and plug them again to get the icons back.

Posted: **Thu 08 Aug 2013, 12:02**

jamesbond wrote:don922, just open the isolinux.cfg on the CD and you'll see the command to eliminate nouveau (it's "blacklist=nouveau"). Copy that into your boot loader config and that should work.

For GeForce 6150 SE I think you'll need to install the nvidia_legacy driver, but to be sure please check nvidia website.

The entry in menu.lst "blacklist=nouveau" has cleared up much of the booting from a frugal install problem.

EDIT the following is no longer correct! I have downloaded the nvidia-legacy.pet, the firefox-20.pet, and the numlockx.pet. Now I can't find these "pets" and I can't find the Puppy Package Manager to install them. I found the PPM hidden in the Control Panel and the downloads were in the PPM - go figure.

I don't understand this root/spot thing, I would be better off operating everything and everywhere as root. In my situation I don't really need the safety of being on the net as spot.

Posted: **Fri 09 Aug 2013, 02:27**

jamesbond wrote:
DrDeaf wrote:
jamesbond wrote:This is what we have in the Fatdog-Next as of today. Still using the 600 as the base. I have this running for quite a while now. Let me know if anyone is interested.

Fatdog64-Next Release Notes
Changes from 621:
Updates:
-------------------
- Linux 3.9.4 with lxc support but without XFS support
-------------------
Maybe not the interest you wanted, but I am interested in XFS support.
Would that be possible?
621 and previous versions have XFS support right now, but the one I'm running is not. It is a choice because right now XFS conflicts with User Namespaces (that's the only filesystem left with a conflict, all others were resolved in 3.9). I will probably choose XFS over User Namespace for a public release. Waiting for 3.11 to go gold.

I am willing to wait as well.

This is an enduring project for me. I am puzzled by the reference to earlier XFS support. Although I did not change to 621 since it was a bug fix release and I had no bugs I was concerned about, I have posted earlier about XFS and you were helpful to post attr-2.4.46-8.pet (Thanks again!)
After installing, everything appeared OK but gparted still did not offer the XFS format option and I could not successfully read XFS format done by another distro. I decided to wait. I have seen a mention of "XFS tools" but none were forthcoming and I do not know how that would be significant or not.

A new concern is your mention of a user namespace conflict. One of the reasons for my interest in XFS is the user namespace attribute enhancement offered by that file system.

I'll close with a mention of a minor quibble. I came to FD at 610 (Nov 2012) and every release has not recognized my eth0 chipset. No problem since my machine is a notebook and I am wireless normally. Still, Lighthouse64 & Knoppix64 find everything so maybe now is a good time to mention this.

I looked at a post I made when 611 arrived to copy over the info for the chipset (Hey! I found you and Smokey01 over there... you guys get around!). Here is the info I think you would want: Ethernet controller : Intel Corporation Device 1502 (rev 04)

This isn't a show stopper, just passing it along now.
Thanks again, jamesbond.

Posted: **Sat 10 Aug 2013, 03:36**

DrDeaf,

The XFS support is in kernel - which means if you have existing XFS disk, Fatdog will see it and can use it just like any other partition. But the support for creating new XFS partition through gparted isn't there (yet), because the tools aren't included.

Don't worry about the user namespaces conflict - what I'm talking about is different from XFS user namespace.

Your ethernet is supposed to be supported by e1000e module. Try loading it manually (modprobe e1000e) and see if there is any error message in dmesg?

don922,
Edit /usr/share/applications/Seamonkey-web-browser.desktop and change "seamonkey-spot" to "seamonkey" and you're good to go. For others (e.g. Firefox etc) explore other files and in /usr/share/applications and change those that contain "whatever-spot" to "whatever".

cheers!

Posted: **Sat 10 Aug 2013, 14:03**

There was a good mpg file header editor, Easytag, that was available under Lucid. The pets (easytag and library files) do not work with Fatdog.

Every so often, I need to edit the file header to include the track number in the title. I have found mpeg audio players sort the songs based on the title information. This prevents one from hearing the songs as on the album.

Is there a pet available for Fatdog that can edit the mpg audio file header information? Thanks for any help in advance!

Posted: **Sat 10 Aug 2013, 18:08**

JustGreg wrote:There was a good mpg file header editor, Easytag, that was available under Lucid. The pets (easytag and library files) do not work with Fatdog.

Every so often, I need to edit the file header to include the track number in the title. I have found mpeg audio players sort the songs based on the title information. This prevents one from hearing the songs as on the album.

Is there a pet available for Fatdog that can edit the mpg audio file header information? Thanks for any help in advance!

Just added to the repo: http://distro.ibiblio.org/fatdog/pets/6 ... .8-622.pet, only because you asked, Greg

Posted: **Sun 11 Aug 2013, 15:18**

H Jamesbond,

I tried your suggestion, to leave the mouse hovering over the green box after clicking. It has no effect. As noted in my previous post you get a Rox window every time you click but no unmount, even after pointer "hovering" over the box for 20 seconds. Moving the icon a quite small distance restores normal behaviour, this was at Smokey01's suggestion.

Moving the icon back to the bottom left corner causes the problem to come back. You don't have to be totally precise in positioning the icon there to reinstate the odd behaviour but you do have to be quite close.

I have a windows partition frugal install, set up by Fatdog's installer. When using webmail, I initially thought that you can't attach files from the windows partition, except for the Spot folder. The file Open Window behaves as if /mnt/sda2 is not mounted. Then I realised that, on the other hand, mnt/home, which is the same thing surely, works just fine. It's a bit confusing for a poor snail.

wpa-gui has a slightly odd behaviour. I'm in a hotel at the moment. When booting, it seems to be trying to connect to the correct wifi adapter but it stays stuck on "scanning". Disconnecting and reconnecting doesn't help. It took an awful lot of trying things before, quite by accident, I discovered that Manage Networks/Edit then Save(without changing anything since the network has already been set up) is enough to clear the logjam. Once this is done, connection takes a second or so and DHCP a few seconds more. The network is WPA2-PSK/TKIP+CCMP and the signal is good to excellent,

Another minor quirk is that closing the window by using it's tile bar or the menu is NOT what you want to do. You must just hide the window using the taskbar icon. This is a bit of a trap for us idiots.

Posted: **Sun 11 Aug 2013, 16:21**

A while ago, I asked a dumb question about why /usr/lib and /usr/lib64 seemed to be identical. Of course, if I had opened /usr in Rox the fact that lib64 was just a symlink would have been bleedingly obvious. However, the reason that I was confused is that gdmap shows the two using up space in /usr, one is displayed above the other. Surely gdmap shouldn't do that?

Anyway, as I was confused, I decided to check further. As gtkhash doesn't do directories, I tried to zip them and hash the zipfiles. This caused the file system to fill up and eventually trashed the savefile. Why would xarchive do that? Shouldn't temp be located separately from the savefile, since it's never saved?

Posted: **Sun 11 Aug 2013, 17:16**

Snail wrote:I tried your suggestion, to leave the mouse hovering over the green box after clicking. It has no effect. As noted in my previous post you get a Rox window every time you click but no unmount, even after pointer "hovering" over the box for 20 seconds. Moving the icon a quite small distance restores normal behaviour, this was at Smokey01's suggestion.

Moving the icon back to the bottom left corner causes the problem to come back. You don't have to be totally precise in positioning the icon there to reinstate the odd behaviour but you do have to be quite close.

Please post screenshots with icons positions "where it works" and "where it doesn't work".

I have a windows partition frugal install, set up by Fatdog's installer. When using webmail, I initially thought that you can't attach files from the windows partition, except for the Spot folder. The file Open Window behaves as if /mnt/sda2 is not mounted. Then I realised that, on the other hand, mnt/home, which is the same thing surely, works just fine. It's a bit confusing for a poor snail.

That's expected behaviour if you move the Download folder outside the savefile.

wpa-gui has a slightly odd behaviour. I'm in a hotel at the moment. When booting, it seems to be trying to connect to the correct wifi adapter but it stays stuck on "scanning". Disconnecting and reconnecting doesn't help. It took an awful lot of trying things before, quite by accident, I discovered that Manage Networks/Edit then Save(without changing anything since the network has already been set up) is enough to clear the logjam. Once this is done, connection takes a second or so and DHCP a few seconds more. The network is WPA2-PSK/TKIP+CCMP and the signal is good to excellent,

Yeah, there are just so many variations in wifi signalling

I sometimes have to kill the dhcpcd task manually and restart them to get the IP address :p

Another minor quirk is that closing the window by using it's tile bar or the menu is NOT what you want to do. You must just hide the window using the taskbar icon. This is a bit of a trap for us idiots.

I'm not sure I get what you mean.

Snail wrote:A while ago, I asked a dumb question about why /usr/lib and /usr/lib64 seemed to be identical. Of course, if I had opened /usr in Rox the fact that lib64 was just a symlink would have been bleedingly obvious. However, the reason that I was confused is that gdmap shows the two using up space in /usr, one is displayed above the other. Surely gdmap shouldn't do that?

I think I already answered that a couple of times. /usr/lib is a mirror image of /usr/lib64. In a more technical terms /usr/lib is a bind-mount of /usr/lib64. The reason we use bind-mount instead of mere symlink is because symlink can be accidentally erased.

Anyway, as I was confused, I decided to check further. As gtkhash doesn't do directories, I tried to zip them and hash the zipfiles. This caused the file system to fill up and eventually trashed the savefile. Why would xarchive do that? Shouldn't temp be located separately from the savefile, since it's never saved?

You are right, it shouldn't do that. How exactly did you do to zip the stuff again? "zip" command line or "xarchive"?

Posted: **Sun 11 Aug 2013, 18:08**

Installing the Peasy Media Apps in Fatdog

VLC is an excellent media player. But you might prefer something simpler, like PeasyMP3, PeasyCD or PeasyDVD.

1. Open the Fatdog Package Manager and install MPlayer. Do NOT install the Jack dependency!

2. Install the mplayer_extras_fd620-1.0.pet attached below.

3. Install the Peasy media apps as usual. Look for them in the Other menu.

4. ROX in Fatdog uses SendTo instead of OpenWith in its right-click menus. Drag a shortcut from /usr/sbin/peasymp3
to the folder /etc/xdg/rox.sourceforge.net/SendTo

Posted: **Sun 11 Aug 2013, 18:52**

Hello,

I would like to ask you, is it possible to install firmware for this wireless card? I am new to fatdog, and I don't know how to setup this wireless card. It is bcm 4313
Broadcom wireless device [14e4:4727]

Thank you

Posted: **Sun 11 Aug 2013, 22:07**

jamesbond wrote:
wpa-gui has a slightly odd behaviour. I'm in a hotel at the moment. When booting, it seems to be trying to connect to the correct wifi adapter but it stays stuck on "scanning". ...
Yeah, there are just so many variations in wifi signalling I sometimes have to kill the dhcpcd task manually and restart them to get the IP address :p ...

The process/steps to carry out these task; could you share them. Or, is there a script which might do same?

Thanks in advance.

Posted: **Mon 12 Aug 2013, 12:09**

Please post screenshots with icons positions "where it works" and "where it doesn't work".

Here they are jamesbond. As you can see, the amount of movement involved is subtle, within the precision that I can place the icons anyway.

The Doesn' work 1 screenshot shows the mmc icon in the original location straight after boot, i.e. it hasn't been moved, only clicked.

The second Rox windows in the two Doesn't work screenshots are the result of clicking the green box. In the "Does work" screenshot, the icon has been clicked to mount and then green-box clicked, exactly the same as for the two "Doesn't work" screenshots.

Posted: **Mon 12 Aug 2013, 13:26**

Hi jamesbond, I have some comments on your comments on my earlier post.

/mnt/sda1 visibility issues:

This may be "expected behaviour when you move the Download folder outside the savefile" to experts like yourself. It is a serious potential usability issue to non-geeks. This case occurs whenever Fatdog is installed into the Windows partition, using fatdog's own installer, which is likely to be a very common case given how damned awkward NTFS partitions have been made to partition nowdays. mnt/sda2 is the most obvious route to the newb, although even that's none too obvious. As a suggestion, could the Fatdog installer be made to set up a symlink to /aufs/devsave called "Windows Partition" in /root, so it is easy to find in the Open File window, in the case of FatdoginWin installs?

WPA-Gui issues:

Since the "fix" I stumbled upon is doing nothing more clever than driving WPA-Gui, Surely the program should be able to be smart enough to realise that it's locked and automatically do what I have to spend several seconds doing, after about a week discovering how to?

If you close the WPA-Gui window, by clicking File/exit, Not only does the WPA-Gui window close but the Taskbar icon also vanishes. There is no way of getting it back easier than running wpa-gui from the terminal, there are no icons in either the menu or the control panel. It also seems to loose any changes that you have just made in the Manage Networks tab. The wifi connection still persists however.

The cross on the WPA-Gui window header bar seems OK, it closes the window but does not kill the taskbar icon.

GDMap issues:

I know very little but I do know about symlinks

What confused me is that apparently, GDMap doesn't. Since the only point of using GDMap, apart from admiring the rather pretty graphic, is to find out what is eating your storage, surely it should ignore symlinks? At least as the default?

Zipfiles:

I did not use a terminal command, so it must have been xarchive from the menu that caused the problem. Fatdog started frantically warning me that I was eating the savefile but I couldn't come up with a solution in time to avert a smash.

By the way, I see Pupzip is still in there but there is no icon to access it??

(old)Puppy Linux Discussion Forum

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

Re: frugal installation problems

Re: frugal installation problems

Where are downloads? PPM? xorgwizard?

MMC icon green box not unmounting and other stuff

Problem with Xarchive

Broadcom 4313

MMC icon green box not unmounting and other stuff- pics

Other usability quirks.