Fatdog64 630rc2 (24 December 2013) [CLOSED]

[01micko]

In FatDog, if I try dmesg after plugging, let's say, a phone, I don't get any valuable output, just that a high speed usb device is detected as so n so bus etc, 1 line,
eg:

Code: Select all

usb 2-3: new high-speed USB device number 2 using ehci-pc

whereas in all other puppies I get nice output..
eg:

Code: Select all

[  322.283470] usb 2-3: new high-speed USB device number 2 using ehci-pci
[  322.408376] usb 2-3: New USB device found, idVendor=04e8, idProduct=6860
[  322.408390] usb 2-3: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[  322.408398] usb 2-3: Product: GT-I8150
[  322.408405] usb 2-3: Manufacturer: Samsung
[  322.408411] usb 2-3: SerialNumber: 0123456789ABCDEF

Is this a kernel config option?

Or is it a busybox config thing?

[kirk]

Is this a kernel config option?

Or is it a busybox config thing?

Looks like a module is getting loaded to support your phone in Puppy that Fatdog64 doesn't have. Or maybe a udev rule to support the Phone.

[jamesbond]

Looks like Fatdog's kernel doesn't have CONFIG_USB_ANNOUNCE_NEW_DEVICES enabled.

[Ted Dog]

try the MTP thread for 64 bit version. acts wierd for rc2 but works. If the developers here could fix the oddness there it would be a small but valued addition to fatdog64 base.

http://murga-linux.com/puppy/viewtopic.php?t=91442

[01micko]

try the MTP thread for 64 bit version. acts wierd for rc2 but works. I the developers here could fix the oddness there it would be a small but valued addition to fatdog64 base.

http://murga-linux.com/puppy/viewtopic.php?t=91442

See 3 posts ago, therein is the bug.. which may be overcome soon.

[Ted Dog]

oh so you are telling them why is acts wierd? did not see the name of the thread or program you where trying to fix. Sorry,

[01micko]

Anyway, I suppose I can grok the info out of /sys/bus/usb/devices/.

EDIT: yes that works fine.

[vflower]

Thanks to all of you. isolated the small initrd and the remaster successful finally.

Nowadays ram is cheaper and we can afford to buy more ram, so i prefer large initrd and also prefer booting iso files directly from grub4dos, that is, download and then boot.

[Ted Dog]

if you gots RAM to spare try expand2ram option from boot line.. forgot the actual line to use but it runs FATDOG64 totally uncompressed for max speed.

[gcmartin]

... booting iso files directly from grub4dos, that is, download and then boot.

Hi @VFlower.

This is an obvious method of booting, but, it is NOT used for several reasons in Puppyland (or anywhere else either). I wont go into the reasons, for this thread is NOT the place (maybe a new thread to list reason for and against), but I will share that @JamesBond has, in the past, provided instructions on doing this.

I would envision that someday, maybe, there will be an entry on an initial boot dialogue which might be set to allow you to tab, indicate the location of an ISO and thus boot it.

Also, I will share that there are already 2 Threads in Puppyland where the authors of those threads have produced 2 different methods and utilities to boot ISOs directly with NO NEED to burn a CD/DVD. They are designed for PCs which are NOT UEFI PCs. And, there is NO discussion on either about their use in UEFI systems. But, I can attest that BOTH approaches work and they work well on all of the non-UEFI PCs I've seen. And neither author take into account that one would want to use DVD/BluRay as the boot media. @Ted Dog is the ONLY person who has made attempts to address that as he's tested some methods with these. One of the main problems with any of this, the current PUP boots versus those utility's methods is that the boot-managers, themselves, are inconsistent. FATDOG uses one, they use another, etc. (No "standard" boot manager.)

Like you, I am one who wishes that a mechanism to do this becomes available in the future. This is a need because of the many distros that people test in Puppyland to assist the developers.

Hope this helps

[gcmartin]

Oracle Java JDK/JRE 7u51 is now available.
A Request
Latest JDK for 64bit in either the DEVX or as standalone.

Not a pressing priority but now that MTP has come of age in PUPs the need for current JDK serves both users and developers alike.

An idea.

[kirk]

Looks like Fatdog's kernel doesn't have CONFIG_USB_ANNOUNCE_NEW_DEVICES enabled.

Darn, Oh well. It will be in final with kernel 3.12.9.

[kitten]

On fresh CD install, (beautiful) Fatdog64 630rc2 & zarfy figure out they need...

Code: Select all

LVDS1 3f 0 48 1366 768 0 1200 1
VGA1 0 1 0 0 0 0 0 0
HDMI1 40 0 49 1920 1200 0 0 1
DP1 0 1 0 0 0 0 0 0
VIRTUAL1 0 1 0 0 0 0 0 0

and all is well, as recorded in

Code: Select all

/root/.zarfy/:0/outputs.conf

But when I return and cable up again, zarfy can only display the laptop screen, and mirror its image to the big screen, without acknowledging big screen's presence. By then the outputs.conf file only shows...

Code: Select all

default 17e 0 180 1366 768 0 0 1

Using Acer One 756 z, 4GB mem, similar to Acer Chromebook

[zaivala]

OK, so now I have booted to Fatdog64 630rc2 successfully twice.

You'd think the wireless connect profile would be saved and loaded automatically, but it wasn't. The modem profile was saved, the wireless connection protocol was not, had to use the Network Wizard to get it to connect.

Control Panel is, indeed, just where you said it was (in another FD64 topic) on the toolbar... but I still haven't found it in the menu. Doesn't mean it isn't there.

Fatdog's SFS handler is noticing some of the downloads for PP571, which I believe I read somewhere should NOT be used in FD630.

[Edit} I also note that the boot time is considerably longer than PP571, especially loading initfz <?> file. [/edit]

I thought I had downloaded the pet for SRWare Iron, but it's not here.

All in all, it's great that there is a 64-bit Puppy-based OS, but PP571 is a LOT easier to use. I'll check out the Final Release and keep up on this topic, but I guess I'm a 32-bit guy for the present..

[smokey01]

zaivala, this might be a silly question but have you manage to create a save file or save to a directory.

[p310don]

I have played with VLC and can't get it to play nice all the time.

Every now and then, a video doesn't play well, so I close VLC, and the icon stays open in the notification area. I cannot close the background vlc, cannot kill via htop. CPU usage goes through the roof to 100%. Only fix I can see so far is restart x server.

Any suggestions? Anyone else see same error?

[smokey01]

Have you tried changing the Video Output Module to X11.

I have played with VLC and can't get it to play nice all the time.

Every now and then, a video doesn't play well, so I close VLC, and the icon stays open in the notification area. I cannot close the background vlc, cannot kill via htop. CPU usage goes through the roof to 100%. Only fix I can see so far is restart x server.

Any suggestions? Anyone else see same error?

[p310don]

Will try that tonight, thanks for the suggestion smokey

[p310don]

Changing VLC to x11 output worked.

Now, for me Fatdog630rc2 is working fine

[zaivala]

zaivala, this might be a silly question but have you manage to create a save file or save to a directory.

Yep. I treat it just like I treat Puppy.