Re: [Voyage-linux] Voyage 0.10: Ethernet bug when moving CF-disks to other boards discovered
Hi Jon, > I don't think that this is a bug. Those rules keep your Ethernet port names > consistent over time. In my cloning notes I have a step to delete the > appropriate lines before moving the disk / CF card to a new system. Objection, your honour :) At least when we chose DHCP I guess everyone wants the device working at a new place in a new hardware. It's not even possible to swap a broken board this way. Everyone should know this at least, and I think this behaviour had been different in previous versions of voyage (which is fantastic BTW). So I think the installer could offer to add your modification.. And yes, I would have expected at least an eth1 popping up .. -- Andreas ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Voyage 0.10.0 on ALIX wants to fsck :-) - does that make sense?
Hi all, after having successfully installed Voage Linux 0.10.0 on a Compact Flash disk for an ALIX board, the startup messages are reminding me to use fsck as the data structure would be OK yet they recommend using fsck: Nov 24 15:10:58 xxx vmunix: [ 12.260186] EXT2-fs (sda1): warning: mounting unchecked fs, running e2fsck is recommended How do I do it? Or should I ignore that? Thanks -- Andreas ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Voyage 0.10: Ethernet bug when moving CF-disks to other boards discovered
Hi list,
I guess I have discovered a bug:
With an Alix board and Voyage Linux 0.10.0, I prepared a Compact Flash
with the usual script.
It started fine, I got ssh access etc., DHCP was working, Ethernet..
Then when I stopped the machine (orderly shutdown) and plugged the
CF-card into another ALIX board (with a different Ethernet MAC, the
Ethnernet interface eth0 did not even come up at boot - it was not
present even in "ifconfig".
The problem is, that when starting up and the following file does not
yet exist, the system "hardwires" the MAC address into the file, like
so:
xx:~# cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x1106:0x3053 (via-rhine)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:0d:b9:17:fc:d0", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
I think it is this problem.
http://unix.stackexchange.com/questions/110496/cloned-linux-system-and-etc-udev-rules-d-70-persistent-net-rules
Could the voyage code be adapted or is this a Debian thing? Come
something be done?
--
Cheers
Andreas
___
Voyage-linux mailing list
Voyage-linux@list.voyage.hk
http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Wiki
- I would really recommend giving it another try with Dokuwiki. It has very much improved (especially security) than some years ago when it has been apparently hacked. With the new vector template we'll have the exact same design as Wikipedia and it is very clean and usable. I've also installed Dokuwiki on four locations with hundreds of pages and it is one of the most versatile and easy-to-use open source packages that I know. The Media Manager and other parts have been redesigned with help from Google Summer of Code. It is AJAXy now but I feel it is also much more secure than before. -- Andreas ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Resolved (so far): Kernel panic at first reboot (ALIX, Voyage 0.7.5)
I have not had any problems with Alix boards. Other than two installs (and laptop and a soekris) all of my installs have been on Alix boards. Finally, i managed to install voyage 0.7.5 on my flashdrive with grub, not lilo. So i will stick with grub and we'll maybe never learn why lilo does or did not work.. Thanks for your help! -- Andreas ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] SOLVED: Voyage Linux Bug? Kernel panic at first reboot (ALIX, Voyage 0.7.5)
Dear Adrian, Voyage Linux. BTW: Why does grub not work at all on a normal ALIX board? It does here. It does as well here. I'm not sure where I was wrong, but I am the culprit. :) Thanks! -- Andreas ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Kernel panic at first reboot (ALIX, Voyage 0.7.5)
Dear list, I tried to install Voyage 0.7.5 on an ALIX 3C - no success, neither with lilo nor with grub, Next, I installled Voyage 0.7.5 successfully (with lilo, grub does not boot) on a ALIX 3D3 board. Only thing I did was remountrw, then nothing else than to add a german repository to sources.list, then successfully install gphoto2 and usbtools, managed to get a photo captured from a digicam, changed the hostname with hostname and in /etc/hostname, managed to open a remote session via ssh, changed root pw, - IP address was obviously obtained via DHCP, everything seemed to work fine until the first reboot: I got only a kernel panic: For brevity, I will list only the last lines: [1.124696] i8042: PNP: No PS/2 controller found. Probing ports directly. [1.127064] i8042: No controller found [1.129334] mousedev: PS/2 mouse device common for all mice [1.130666] cpuidle: using governor ladder [1.132012] cpuidle: using governor menu [1.135354] TCP cubic registered [1.136075] NET: Registered protocol family 17 [1.136522] Registering the dns_resolver key type [1.137706] Using IPI No-Shortcut mode [1.141690] Root-NFS: no NFS server address [1.143286] VFS: Unable to mount root fs via NFS, trying floppy. [1.144810] VFS: Cannot open root device LABEL=ROOT_FS or unknown-block(2,0) [1.145495] Please append a correct root= boot option; here are the available partitions: [1.146594] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) [1.148444] Pid: 1, comm: swapper Not tainted 2.6.38-voyage #1 [1.149952] Call Trace: [1.151357] [c1293e38] ? panic+0x5a/0x144 [1.152199] [c13a6c53] ? mount_block_root+0x161/0x175 [1.153164] [c1086818] ? sys_mknod+0x13/0x15 [1.153781] [c13a6cff] ? mount_root+0x98/0xa0 [1.154665] [c13a6e47] ? prepare_namespace+0x140/0x171 [1.155887] [c13a63d4] ? kernel_init+0x17a/0x189 [1.156551] [c13a625a] ? kernel_init+0x0/0x189 [1.157702] [c1002d36] ? kernel_thread_helper+0x6/0x10 Any ideas? -- Andreas ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Re: Re: Alix Power Button
Dear Edgar, I am a newbie, so maybe my question is a little stupid :( ... but anyone knows how to connect a power button to the alix2dX board? I have connected a hard drive to this board and would be great to shutdown the operating system gracefully. there is no such thing as a power button on the alix2 boards, they're intended to run 24/7. Well there IS an option (for ALIX 3D3 at least) to solder a power button to the ALIX as ALIX has a general purpose I/O. http://www.twam.info/linux/gpio-on-alix3d3 http://voyage-linux.34677.n3.nabble.com/Fwd-What-about-GPIO-support-for-ALIX-3D3-td875443.html You might then provide a daemon or something else to detect operation / processing interrupt (if possible?) of the switch and then shutdown -h now. The following is for the WRAP board, so maybe not useful for the ALIX: http://wiki.voyage.hk/dokuwiki/doku.php?id=wrap_switchess=gpio I did not try anything like that, I'm only using the LED and they work fine. I think this might be a useful option to implement or research in future voyage versions, as we might usw ALIX with VGA as a lightweight terminel (see LTSP project: https://wiki.kip.uni-heidelberg.de/KIPwiki/index.php/EDV:LTSP/alix3d3 - in German) -- Kind regards Andreas ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
Re: [Voyage-linux] LEDs, APT repository, MySQL in RAM questions
Dear Jordi, thank you for your friendly reply! We use adjtimex + ntpd in order to have a ALIX3D2 synchronized. I wrote how we configured it in http://code.google.com/p/wfrog/wiki/InstallOn_Alix3D2_voyageLinux0_6_2#Clock_sync Thanks, I've found that page already.. :-) I found out that I could install adjtimex package as soon as I changed the apt-sources to the german server.. Now the only buggy package that I need is ssmtp (smtp forwarder to a smarthost), but i works when ignoring errors when installing. I set up a read-write partition for the database and write a record each 5 min. So far the ALIX 3 D 2 with a 1Gb SLC Compact Flash has been working for half a year perfectly. We'll have to wait a couple of years to know how long the CF last!!! Yes.. If we think about wear leveling, there is a lot of options: Here, we will have only tens to hundreds of write updates per day, not thousands, and I have 4 GByte Flash memory, only 400 MB of which are used so far. The part where the changes appear (the database) is only 3 MB now and will 10 MB in some years. If we assume that every change rewrites 100 kByte (much less in the database's data, but with every update one or three flash blocks have to be rewritten..) we rewrite max. 10 MB per day = 3,65 GBytes per year - within one year, the free space on that disk is rewritten only once (statistically) that is, if we have a proper wear-leveling algorithm. If every flash block can be rewritten only 10.000 times, can we think of 10.000 years? I think that would be enough. :-) Or did I go wrong? Does th CF card know which blocks are free and use them automatically with a round-robin-method? If the CF knows nothing about filesystems, it would be much less: Assume we write always in the same 10 MB, the CF will last 10.000 days = 27,3 years. Shouldnt even that be enough? I see that if we have one small table in the DB which gets rewritten always in the same spot, things get worse: 10.000 operations would be accomplished after only a hundred days... maybe it is crucial to put only that table in RAM and let the rest of the database grow slowly without any concern? However, it would be great to be able to check the sanity of the CF-disk like with the smartmontools and in some years just swap the disk (they are inexpensive anyway). Or we could move that table from time to time to another location on the flash (Manual wear-leveling)? Lets say we create a copy of the full database every day and leave to old copy unattended until the free space is filled up so with every update a new spot is used? Then, with 3,5 GByte free space divided by 10 MByte a day we'd fill the disk within a year - but could we redo that 10.000 times? That would be enough as well. -- Kind regards Andreas ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] LEDs, APT repository, MySQL in RAM questions
Hi all, first of all: I'm happy I found Voyage Linux. Before, I've tried imedialinux and I must say they might just delete their website as it is completely abandoned and PCEngines should better not point to that flavor of Linux at all IMHO. It has many bugs and gave me hours of frustration. However, some questions remain - please pardon if they are FAQs for Deban users, but I think they might be interesting for other beginners too. 1. APT sources What other APT repositories than the taiwanese in /etc/apt/sources.list (http://ftp.tw.debian.org/debian lenny main contrib) can I use when living in Germany? Is it enough to keep the custom repository http://www.voyage.hl/dists/0.6 ./ ? Are you sure that stuff does not get mixed up? 2. Missing Packages (adjtimex) on hk.debian.org The current taiwanese repository does not contain adjtimex package. Seems the only way to me to tune the very unprecise internal clock speed without ntpdate'ing every hour (which could carry sideeffects) Can I add a second source in sources.list and will the package versions be mixed up then? 3. Heartbeat, LEDs When I was booting Voyage Linux for the first time, heartbeat LED etc. are working - but disappear after a reboot (only LED 1 is ON). I manage to start them again via echo heartbeat /sys/class/leds/alix:1/trigger etc but what is the best way to make this permanent? 4. MySQL database in RAM I'll use the ALIX board with mysql / lighttpd and php5, which works fine. I followed this guide: http://www.howtoforge.com/installing-lighttpd-with-php5-and-mysql-support-on-debian-lenny Now I am unsure whether I should move the /var/lib/mysql folder to the rw / ro mechanism so writing to the DB does not spoil the flash so fast. Does anyone have experiences on wearout when using a 4 GByte flash for about 500 MByte? My database is about 50 MB and will reach 100 MB. If I reserve 100 of 256 MByte for MySQL, maybe the RAM is not enough for the functioning of the rest of applications? 5. Turn off unused services If I have a static IP adress - is it safe to turn off dnsmasq? Is it safe to turn these services off (tcp:53, tcp:68, tcp:1723, tcp:111) when I only want to offer MySQL and http (and ssh) services? How can I do it safely? Sorry for asking so many questions but I guess that they might be easy ones for experienced users.. Thanks a lot! -- Kind regards Andreas ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
Re: [Voyage-linux] Resolved (somehow): eth0 link down on freshly installed ALIX 3D2 with voyage 0.5.2
Dear Jo, Seems like the fritzbox doesn't do auto MDI/MDIX on that port then? That's what I thought too at one point.. Have you already tried with a crossed cable instead of straight through? No, but I will, thanks! The funny thing is: I've been using imedialinux before (another Linux for ALIX boards, but with zero support) and there the exact same board worked fine with the exact same cable and router..so it might be a config option for the network card.. do you know where they sit? -- Andreas ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] eth0 link down on freshly installed ALIX 3D2 with voyage 0.5.2
Hi all, I have a local Ethernet TCP/IP network where a DHCP server is running fine (that is, other machines get internet access via the same cable). I managed to install Voyage Linux 0.5.2 via a Ubuntu 10.4 host system on a 4 GB CF flash disk. I see the device booting via serial console, /var/log/messages says something linke: eth0: VIA Rhine III etc., so assume I got the right driver, but I got eth0: link down as well. ifconfig shows eth0, but no IP address as DHCP goes into timeout. On the physical network there is one green LED constantly on with or withut a cable, nothing else happens when plugging the cable in. Looks as if there is no cable plugged in, but as I said the cable works. The switch on the other side sees no network adapter either. The LED next to the network socket blinks twice, about every 2 seconds. I get the same result when I take another ALIX board (of the same type). Any ideas what that means? -- Kind regards Andreas ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Resolved (somehow): eth0 link down on freshly installed ALIX 3D2 with voyage 0.5.2
Hi again - my ALIX board was connected to a Router (Fritzbox) whose port normally operates as a switch without problems for the other machines. Now as I took a real switch and connected it inbetween the ALIX board and the router, it worked. Hm. We'll see whether it will work when installed at my customers site.. -- Regards Andreas ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
