It could also be a combination between the USB and the UEFI firmware. rEFInd uses UEFI routines to load the huge initrd. Grub2 uses its own. Anyway, moral of the story is the sameJustGreg wrote:I have a 512 Megabyte Lexar drive that EFI-Stub boot works without any problems. However, a Kingston 1 Gigabyte drive will not boot using the EFI-Stub process
They are frozen at the release of the source code. I believe I speak correctly for kirk when I say that both of us never try to upgrade when we're using Fatdog versions of these.Thank you, Kirk, for the information. This explains the difference between the two. Will the Fatdog versions of FireFox and Thunderbird update to the latest versions or are they frozen at the release of the source code?
On the bright side, if you do need the updates, you can download and use the official 64-bit versions of firefox and thunderbird.
http://releases.mozilla.org/pub/mozilla ... ux-x86_64/
http://releases.mozilla.org/pub/mozilla ... ux-x86_64/
Get the tarball from your language, and extract the contents under /usr/lib64 (For firefox, delete the symlink /usr/lib64/firefox first)
and then symlink /usr/lib64/firefox/firefox and /usr/lib64/thunderbird/thunderbird to /usr/bin.
They work and they *should* upgrade cleanly (the keyword here is *should* )
Get the eudora tarball, extract it to /usr/lib64, symlink /usr/lib64/eudora/eudora to /usr/bin.Sage wrote:Update on Eudora OSE 1.
Good News:
Allegedly it is compatible with 64bit code, whatever that implies.
So, just needs a kind soul who does that sort of thing to do it for FD....
...maybe.
Might need some extra libs? ia32?
Then load 32-bit sfs, and start eudora like this: "start32 eudora". At least I got the menus and everything, I haven't tested beyond that. I agree a pet would be nicer
From the looks of it, you do get the connection correctly as ppp0 shows the correct IP address.spandey wrote:ppp0 Link encap:Point-to-Point Protocol
inet addr:117.197.237.72 P-t-P:117.197.232.1 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1460 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:176 (176.0 B) TX bytes:61 (61.0 B)
So it's not a kernel problem etc. The fact that you still can't connect after using Google's DNS means that somehow your IP routing may be troublesome.
Can you actually ping 8.8.8.8 when connected with pppoe? If you can't - can you paste the output of "route -n" when you're connected to pppoe?
Unfortunately, the open source drivers (radeon included) aren't well known for their "cool" performance. I'm forced to run with Catalyst driver here because if I use open source radeon driver, my temp will be 20 centigrade higher.gcmartin wrote:And, it seems my video is on-fire (see below) with nouveau.)
"ntp" service runs shortly at boot to set the clock, then exits. I need to check crond and samba, will get back to you later.Server Manager (SAMBA, et.al)
Further review of the Server manager shows that the server I "disabled" remained disabled while the servers I enable and started did not show enabled/restarted after save-session during reboot. Specifically crond, ntp, samba.