What type of eReader do you have?Gnuxo wrote:I've tried to mount my e-reader but Fatdog won't detect it.
Even Calibre, *which I installed* doesn't detect it.
How do I get the ebook reader to be found?
Fatdog64-620 Final (17 April 2013) and 621 (9 May 2013)
usb stick install no boot
Installed on a USB stick using the FD installer and the 621 iso. No boot I'm afraid.
extlinux.conf sayeth:
default fatdog
timeout 50
prompt 1
label fatdog
kernel vmlinuz
initrd initrd
append
Attempts to boot say missing operating system.
Any ideas on getting to takeoff with this? Sorry, in a rush, and haven't researched issue. Must be some more magic required to get stick to boot? A file called ldlinux,sys is on the stick. Should this be there - thought it may have resulted from various abortive efforts to install a Puppy.
extlinux.conf sayeth:
default fatdog
timeout 50
prompt 1
label fatdog
kernel vmlinuz
initrd initrd
append
Attempts to boot say missing operating system.
Any ideas on getting to takeoff with this? Sorry, in a rush, and haven't researched issue. Must be some more magic required to get stick to boot? A file called ldlinux,sys is on the stick. Should this be there - thought it may have resulted from various abortive efforts to install a Puppy.
Re: usb stick install no boot
That message usually means that a bootloader was not installed.gnomic wrote:Attempts to boot say missing operating system.
Go to Control Panel > Utilities and run Grub4Dos Bootloader Config.
Make sure that you select your flash drive and not your main hard drive.
1. Use an UTF-8 locale (en_US.UTF-8 would do, or any other UTF-8 English locale).heywoodj wrote:Also, I was looking for something with Japanese language support for my client
<<... snip...>>
Right now, for example using FatDog and browsers to look at email with Japanese characters just shows rectangles. Is there a simple solution?
2. For reading, get a CJK font, for example from here: http://wenq.org/en
3. For writing, install fcitx-anthy from the Package Manager - it should pull all the necessary components.
4. Note: Fatdog isn't localised/internationalised, so after you have done that, all the menus are still in English. If you don't like the English locales you can get additional locales from the Package Manager (glibc_locales package) but this will not change the fact - menus and messages will be always be in English.
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]
Re: Delta file and bluray broken in 621
That's bad news I didn't change anything on the isolinux.bin, it may get patched by mkisofs itself during mastering process. All I did was to drop -J and increased iso-level to 4.Ted Dog wrote:Here is a delta file between 620 to 621 wish I had this option.
also the 58byte difference isolinux.bin breaks bluray support on fully populated iso (22Gs)
well sorry cant post a 2Meg delta zip anymore
what exactly is broken?
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]
a few backgrounds.
- Attachments
-
- fatdogmi13b.jpg
- http://www.mediafire.com/?7v1msw26s6chb
- (21.16 KiB) Downloaded 576 times
-
- fatdogmi13a.jpg
- http://www.mediafire.com/?7v1msw26s6chb
- (23.86 KiB) Downloaded 583 times
-
- fatdogmi13.jpg
- http://www.mediafire.com/?7v1msw26s6chb
- (18.53 KiB) Downloaded 580 times
wifi problems eeePC and 621
Got the FD621 on USB to boot following your advice above thanks.
But sadly haven't been having much fun with wifi. First used Pwireless which connected on an open network without difficulty. However the wpa-gui icon kept on popping messages about various access points it could see and disconnecting from the one it was actually connected to, then reconnecting, according to the messages at least. This was bearable for a while but eventually network connection became so intermittent as to be unusable. In the same live USB stick session I then tried the usual Puppy network centre procedure - this appeared to connect albeit with a different IP address, but then was unable to get anywhere on the web after the first greeting screen on this public library network, looked as if DNS was broken.
So this message comes from one of pemasu's versions, upup raring I think with Frisbee. The machine is an Asus eeePC 1005PX, and the wifi is Atheros AR2427. The hardware has been reliable with several Linux distros.
Any thoughts on what may be happening here? Without wishing to be rude, is Pwireless a best of breed software? I have been finding Frisbee reliable. Or even SNS.
But sadly haven't been having much fun with wifi. First used Pwireless which connected on an open network without difficulty. However the wpa-gui icon kept on popping messages about various access points it could see and disconnecting from the one it was actually connected to, then reconnecting, according to the messages at least. This was bearable for a while but eventually network connection became so intermittent as to be unusable. In the same live USB stick session I then tried the usual Puppy network centre procedure - this appeared to connect albeit with a different IP address, but then was unable to get anywhere on the web after the first greeting screen on this public library network, looked as if DNS was broken.
So this message comes from one of pemasu's versions, upup raring I think with Frisbee. The machine is an Asus eeePC 1005PX, and the wifi is Atheros AR2427. The hardware has been reliable with several Linux distros.
Any thoughts on what may be happening here? Without wishing to be rude, is Pwireless a best of breed software? I have been finding Frisbee reliable. Or even SNS.
Sorry, don't use Pwireless that should have been removed. Use Wpa_gui, if there are many open connections in the area you'll want to click "scan" to list the networks and double click on the one you want to create a new connection. Then select your newly created connection using the "Network" pull-down widget. See the FAQs on the home page or here:http://distro.ibiblio.org/fatdog/web/fa ... rking.htmlBut sadly haven't been having much fun with wifi. First used Pwireless which connected on an open network without difficulty. However the wpa-gui icon kept on popping messages about various access points it could see and disconnecting from the one it was actually connected to, then reconnecting, according to the messages at least.
Re: Delta file and bluray broken in 621
Unknown, at this time it takes longer to boot (find isolinux.bin ?) by 4X over last version if it finds it at all. But, I can not see any code difference that would explain this.jamesbond wrote:That's bad news I didn't change anything on the isolinux.bin, it may get patched by mkisofs itself during mastering process. All I did was to drop -J and increased iso-level to 4.Ted Dog wrote:Here is a delta file between 620 to 621 wish I had this option.
also the 58byte difference isolinux.bin breaks bluray support on fully populated iso (22Gs)
well sorry cant post a 2Meg delta zip anymore
what exactly is broken?
No, not possible. I think it's only co-incidence with bad timing.ally wrote:question: ran 621 live on a dell latitude e5430 at a linux club meet, no working touchpad
disc out, reboot to windows 7 and no working touchpad where is was working before
now getting blamed form breaking the laptop, is this possible
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]
Linux club street cred. destroyed, hope you blamed it on Ubuntually wrote:thanks all
I thought the same, was just checking, he wouldn't let me near the machine after so couldn't try the bios and he just didn't want to play!!
I've had mousepad stop working on the last dozen puppylinux versions (32bit) but not past reboot. Just got a new 64bit notebook with w8 (but without secure boot crap ) hope that will not be an issue.
hey sage
luckily another member had a usb mouse, when the machine was rebooted to windows the touchpad did not work and was not recognised in the hardware list
he had already tried ubuntu which had worked
been trying to convert peeps to puppy there for ages, more hard work ahead now
on the plus, it was FAST on his machine, very fast, booted in 9 secs to (nearly) working desktop
luckily another member had a usb mouse, when the machine was rebooted to windows the touchpad did not work and was not recognised in the hardware list
he had already tried ubuntu which had worked
been trying to convert peeps to puppy there for ages, more hard work ahead now
on the plus, it was FAST on his machine, very fast, booted in 9 secs to (nearly) working desktop
VirtualBox-4.2.4-fd64_610.sfs
I ran into some trouble with VirtualBox-4.2.4-fd64_610.sfs
-virtualbox says:# VirtualBox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (3.8.7) or it failed to load. Please recompile the kernel module and install it by
sudo /etc/init.d/vboxdrv setup
You will not be able to start VMs until the problem is fixed
I searched a lot for a solution but had to dig in to the problem myself.
Got VirtualBox-4.2.4-fd64_610.sfs running by doing:
Loading from system sfs loader:
fd64-devx_620.sfs
kernel-source-3.8.7.sfs
run from term:
/etc/init.d/vboxdrv setup
VirtualBox is functional.
Now kernel-source-3.8.7.sfs can be unloaded.
I assumed all code would be in devx, no kernel-source-3.8.7.sfs needed.
Sounds familiar to someone?
-virtualbox says:# VirtualBox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module available for the current kernel (3.8.7) or it failed to load. Please recompile the kernel module and install it by
sudo /etc/init.d/vboxdrv setup
You will not be able to start VMs until the problem is fixed
I searched a lot for a solution but had to dig in to the problem myself.
Got VirtualBox-4.2.4-fd64_610.sfs running by doing:
Loading from system sfs loader:
fd64-devx_620.sfs
kernel-source-3.8.7.sfs
run from term:
/etc/init.d/vboxdrv setup
VirtualBox is functional.
Now kernel-source-3.8.7.sfs can be unloaded.
I assumed all code would be in devx, no kernel-source-3.8.7.sfs needed.
Sounds familiar to someone?