Fatdog64-700/701 [April 22 2015] [CLOSED]
In the midst of a winter storm but managed to get an install done.....working well so far. Good job.
- Attachments
-
- Fatdog 700.jpg
- (88.09 KiB) Downloaded 1628 times
Fatdog64-700 FINAL [Feb 22 2015]
I installed fatdog64-700 to a 32gb SDHC card, installed the proprietary
nvidia driver:
video-info-glx 1.5.3 Mon 23 Feb 2015 on Fatdog64 700 Linux 3.18.7 x86_64
0.0 VGA compatible controller: NVIDIA Corporation GF110 [GeForce GTX 560 Ti OEM] (rev a1)
oem: NVIDIA
product: GF110 Board - 12630002 Chip Rev
X Server: Xorg Driver: nvidia
X.Org version: 1.16.3
dimensions: 3840x1080 pixels (1204x343 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 GTX 560 Ti/PCIe/SSE2
OpenGL core profile version string: 4.3.0 NVIDIA 340.76
Also using arandr to position the monitors.
nvidia driver:
video-info-glx 1.5.3 Mon 23 Feb 2015 on Fatdog64 700 Linux 3.18.7 x86_64
0.0 VGA compatible controller: NVIDIA Corporation GF110 [GeForce GTX 560 Ti OEM] (rev a1)
oem: NVIDIA
product: GF110 Board - 12630002 Chip Rev
X Server: Xorg Driver: nvidia
X.Org version: 1.16.3
dimensions: 3840x1080 pixels (1204x343 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 GTX 560 Ti/PCIe/SSE2
OpenGL core profile version string: 4.3.0 NVIDIA 340.76
Also using arandr to position the monitors.
- Attachments
-
- capture1715.jpg
- (186.09 KiB) Downloaded 1555 times
monitoring this
Looking at all the dual screen pictures in this thread I wonder why the drive icons are located on screen 1, while the task bar is on screen 2......
Just curious....
Just curious....
They are easy enough to make if you have a good camera.Ted Dog wrote:all so curious is that multi monitors or a 4K UHDTV and where do you get wide pics.
You can get some here: http://www.dualmonitorbackgrounds.com/? ... eight=1050
C720 and seabios
@proebler
At Fatdog 700 final grub screen pressed TAB, added mem=1950, and the boot process started. Everything looked good until "Booting the kernel".
There the process stalled. Waited some minutes, nothing happend.
Maybe this is why Kirk mentioned a different kernel is needed (I am still using Seabios). I hoped the 3.18.7 was recent enough, but apparently not.
At Fatdog 700 final grub screen pressed TAB, added mem=1950, and the boot process started. Everything looked good until "Booting the kernel".
There the process stalled. Waited some minutes, nothing happend.
Maybe this is why Kirk mentioned a different kernel is needed (I am still using Seabios). I hoped the 3.18.7 was recent enough, but apparently not.
Re: monitoring this
Hi,Volhout wrote:Looking at all the dual screen pictures in this thread I wonder why the drive icons are located on screen 1, while the task bar is on screen 2......
Just curious....
Right clicking on the panel brings up a configuration menu which allows
moving the panel.
- Attachments
-
- capture2116.jpg
- (58.95 KiB) Downloaded 1437 times
Touchscreen right click is working great, also in the webpage! Google chrome installed smoothly. Can't find any problems yet. Blowfish=5.81 fastest reading to date for my hardware.
But I fear very few British or American women would like to see their pc booting to such an accusing desktop! lol Guilty conscience or something. Maybe you should add the disclaimer ...'FATDOG ... NOT YOU!' However in the orient ...
Thanks James and Kirk
stemsee
EDIT: touchscreen pinch-to-zoom is working in browsers too!
But I fear very few British or American women would like to see their pc booting to such an accusing desktop! lol Guilty conscience or something. Maybe you should add the disclaimer ...'FATDOG ... NOT YOU!' However in the orient ...
Thanks James and Kirk
stemsee
EDIT: touchscreen pinch-to-zoom is working in browsers too!
@Kirk, one of FATDOG's features you made used to be its ability to discover and automatically use, during boot-time, the LAN adapter that has the ethernet cable plugged in. For years, since you introduced this in V5 days, this was a part of FATDOG, but appears to have been overlooked. And chance this would be put back in? (I know it still works on PCs with only a single adapter or if the cable is plugged in eth0. But, I only use eth0 for some of my security needs and have always used eth1 since you resolved this over 5 years ago.)
C720 Seabios
@Volhout
it is mem=1950m [NOT mem=1950]
With Grub4dos this worked for me:
it is mem=1950m [NOT mem=1950]
With Grub4dos this worked for me:
title FDog64_REMASTER_NO-save
find --set-root --ignore-floppies --ignore-cd /FDog64/initrd
kernel /FDog64/vmlinuz mem=1950m pmedia=usbflash pfix=fsck
initrd /FDog64/initrd
First off, FD700 works perfectly for me so far!
There was a dysfunction at bootup with b2 and although different in detail also with rc. The release version does not have this "problem" and I am very curious about what was different between the three versions to cause it.
I use a Thinkpad X230t with 16GB of RAM. No HD. I boot from a locked SD card mounted in a USB3 adapter. Very fast and clean. I do this two ways. My first preference is a card prepared with Easy2Boot and I just toss the pristine ISO to the MainMenu. This usually works with no problem, as in FD630 and now FD700 final.
However, FD700b2 failed at bootup with a message "not enough memory to load specified image". The screen would return to the "FD Live" screen and I could let it boot again with the same result.
FD700rc failed differently. The boot sequence would appear normal until the screen message "Booting the kernel". At this point the sequence would terminate and restart a cold boot from scratch. Untended, the system would do this endlessly.
My "Fallback" boot method is a partitioned card prepped by Grub4Dos. Unpacking the ISOs to each partition has always worked every time.
So, FD630 and FD700 final work great. the earlier versions did not, each in a unique way.
I hope these details help, but the question is simple. What changed among the versions to cause the differences at boot?
Thanks in advance!
There was a dysfunction at bootup with b2 and although different in detail also with rc. The release version does not have this "problem" and I am very curious about what was different between the three versions to cause it.
I use a Thinkpad X230t with 16GB of RAM. No HD. I boot from a locked SD card mounted in a USB3 adapter. Very fast and clean. I do this two ways. My first preference is a card prepared with Easy2Boot and I just toss the pristine ISO to the MainMenu. This usually works with no problem, as in FD630 and now FD700 final.
However, FD700b2 failed at bootup with a message "not enough memory to load specified image". The screen would return to the "FD Live" screen and I could let it boot again with the same result.
FD700rc failed differently. The boot sequence would appear normal until the screen message "Booting the kernel". At this point the sequence would terminate and restart a cold boot from scratch. Untended, the system would do this endlessly.
My "Fallback" boot method is a partitioned card prepped by Grub4Dos. Unpacking the ISOs to each partition has always worked every time.
So, FD630 and FD700 final work great. the earlier versions did not, each in a unique way.
I hope these details help, but the question is simple. What changed among the versions to cause the differences at boot?
Thanks in advance!
Fatdog64-700 FINAL [Feb 22 2015]
I installed fatdog64-700 to a 64gb SDXC card, running on my Acer touch
screen laptop.
Touch works in all the applications I tested, spacefm,google-chrome,
even dillo.
But in my opinion the mouse pointer works better than a large finger.
I changed the bios setting to legacy on this Windows 8.1 computer.
screen laptop.
Touch works in all the applications I tested, spacefm,google-chrome,
even dillo.
But in my opinion the mouse pointer works better than a large finger.
I changed the bios setting to legacy on this Windows 8.1 computer.
- Attachments
-
- capture29333.jpg
- (181.91 KiB) Downloaded 2124 times
Netflix working
Just installed Fatdog 700 to a 3 Gb usb stick using Universal USB Installer on my Intel Duo Core Desktop with 3 Gb of Ram.
Installed Chrome from the Fatdog control panel.
Logged into Netflix and it just worked without any problem whatsoever.
Everything else seems good.
-Dan
Installed Chrome from the Fatdog control panel.
Logged into Netflix and it just worked without any problem whatsoever.
Everything else seems good.
-Dan
I installed the final release version of 700. It works fine. I installed it to a partition on the hard drive with a new save directory. I installed MMEX, Chrome, LibreOffice (sfs) and some other items. No problems encountered. I am trying to get the latest version of the Ardunio IDE up and running correctly. If I do, then I will make an installation package for Fatdog64. Thanks for all the work!
Enjoy life, Just Greg
Live Well, Laugh Often, Love Much
Live Well, Laugh Often, Love Much
Yep. Take a look at the 631 thread for the c720: http://www.murga-linux.com/puppy/viewtopic.php?t=93747@Volhout
it is mem=1950m [NOT mem=1950]
I've uploaded a package for the c720 here:
http://distro.ibiblio.org/fatdog/packag ... 6_64-1.txz
This one includes a clickpad driver from here. which works better than the patched synaptics driver except for right clicks. The right button is disabled by default in /root/Startup/touchpad. So to right click you two finger tap. One finger tap is a left click. You can edit /root/Startup/touchpad to enable button right clicks and other things if you like. The old patched synaptics driver is in the repo if you want that instead, it's named xf86-input-synaptics-chromebook.
Nice to hear all the feedback.