Show all posts by user
Discuss all things Debian on your device
Re: Unicode/UTF-8 file names Oxnas - 8 years ago
Sadly, no joy w/4.0. :( I still get "?nima.jpg". I'm starting to think this is more than just some little issue. -JTby renojim - Debian
Re: Unicode/UTF-8 file names Oxnas - 8 years ago
Thanks bodhi. I was making my way throught the OXNAS kernel thread and noticed this: Quoterobert1968@gmail.com Hi Bodhi, You planned to make new kernel for V3 Oxnas in the future with some kernel modules enabled. -keyboard May I ask to enable also -nls_utf8 It is also not urgent at all... Im fine with the present 3.17. and my usb mouse button workaround. Regards, Robert I figuby renojim - Debian
Unicode/UTF-8 file names Oxnas - 8 years ago
So I got one each of the Mobile and Pro $5 Pogoplugs. The setup of each went pretty smoothly, but I cannot get the Pro to handle file names with Unicode characters. For example, I have a file on a share named "Ãnima.jpg". On the Mobile, a directory listing shows the proper file name, but on the Pro I get "?nima.jpg". I thought maybe it was a Samba issue, but even doing thby renojim - Debian
Re: Pogoplug sale! $5 after rebate - 8 years ago
grayman4hire Wrote: ------------------------------------------------------- > Try my tutorial I just published. It's still a > work in progress and your feedback would be > welcome. Thanks > > http://blog.qnology.com/2015/04/hacking-pogoplug-v > 3oxnas-proclassic.html I just got a Pro and a Mobile and haven't had a chance to try your tutorials yet (thanks, bby renojim - Debian
Re: Linux Kernel 3.16 Kirkwood package and rootfs (Non Flattened Device Tree) - 8 years ago
Yep, that seems to work! I compared the output of ethtool -k under 3.15 and 3.16 and the only difference was the tx-tcp-segmentation setting (off by default under 3.15 and on under 3.16). I guess it would be interesting to see if changing the setting under 3.15 causes the same data corruption, but I don't know how useful that information would be. Just out of curiosity, where should oneby renojim - Debian
Re: Linux Kernel 3.16 Kirkwood package and rootfs (Non Flattened Device Tree) - 8 years ago
QuotebodhiThis is normal if you have flash-kernel package installed in your system. Thanks! As you may recall, I had a problem when I initially tried to upgrade to the 3.16 kernel and I may be (and probably am) mistaken, but if I recall correctly I had to install the flash-kernel package to get past some error message in the kernel install script that halted installation before creating the fiby renojim - Debian
Re: Linux Kernel 3.16 Kirkwood package and rootfs (Non Flattened Device Tree) - 8 years ago
I haven't used NFS, but when I installed nfs-common I got the following somewhat worrisome message:[ ok ] Starting NFS common utilities: statd idmapd. Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.16.0-kirkwood-tld-1 Kernel suffix 1 does not match any of the expected flavors (kirkwood), therefore not writing it to flash. I went back to the 3by renojim - Debian
Re: Linux Kernel 3.16 Kirkwood package and rootfs (Non Flattened Device Tree) - 8 years ago
Ok, this got pretty convoluted pretty quickly. It looks like writing to a mapped drive works, but reading from a mapped drive may or may not (see the fsum note above). Additionally, the format/type of drive may make a difference. I had no problem transferring files from my ext2 formatted flash drive, but copying files from my NTFS formatted SATA hard drive failed with the occasional corruptedby renojim - Debian
Re: Linux Kernel 3.16 Kirkwood package and rootfs (Non Flattened Device Tree) - 8 years ago
Dang! It looks like there is a problem. If I copy a file (size doesn't seem to matter) to my Windows laptop from a mapped Dockstar connected drive, it doesn't match the original file. I don't know what it means, but if I use fsum to just calculate the MD5 checksum directly on the file without copying it to a local drive first, the checksum matches. If I copy the file to a localby renojim - Debian
Re: Linux Kernel 3.16 Kirkwood package and rootfs (Non Flattened Device Tree) - 8 years ago
Thanks for the heads-up. Looks like one more reason I'm glad I dumped Arch as I haven't seen any problems with Samba, but I guess now I'll have to do some more testing. -JTby renojim - Debian
Re: Not Booting with 2nd USB attached. - 8 years ago
I had a similar problem, but sometimes it would boot and sometimes it wouldn't. It's great to get the above information, but I just kept swapping USB cables until my boot drive always came up as 0:1. Seems like an easy thing to try. -JTby renojim - Debian
Re: Linux Kernel 3.16 Kirkwood package and rootfs (Non Flattened Device Tree) - 8 years ago
Ok, I have to apologize. I'm not sure what happened the first time I tried to install 3.16 (I thought I followed the same steps as when I installed 3.15), but after I upgraded to Wheezy the upgrade to 3.16 went smoothly. Now it's on to finishing installing everything and learning me some Debian! bodhi, thanks for all you do! -JTby renojim - Debian
Re: Dumping Arch Linux for Debian - 8 years ago
Thanks! Updating to Wheezy as we speak. I managed to update to the 3.15 kernel, but so far no luck in getting to 3.16. I'll try again once the Wheezy update is finished. -JTby renojim - Debian
Re: Linux Kernel 3.16 Kirkwood package and rootfs (Non Flattened Device Tree) - 8 years ago
There doesn't seem to be a initrd.img-3.16.0-kirkwood-tld-1 in the 3.16 package. -JTby renojim - Debian
Dumping Arch Linux for Debian - 8 years ago
Hello all, new here. So I had been happily running Arch Linux on my Dockstar for a couple of years when I made the mistake of upgrading the ntfs tools. That required me to do a full update of pretty much everything which resulted in days lost trying to unbork my system. Once I got the thing booting again, I was left in systemd hell. I wasted a couple more days just trying to get the freakinby renojim - Debian