Hi Beat, If you could break down your question on separate thread, I would probably answer more.
But here come to first one. those hostap-utils and madwifi under /etc/modprobe.d are installed from a deb package. Probably I have a fewer control over it but has to consult to package source.
The 70-persistent-net.rules should have been removed from daily. But the apt-update of udev will bring this back unfortunately.
Regards, Punky On 4/1/2011 5:14 AM, Beat Meier wrote:
Hello Some comments about voyage-0.7.0 1. /etc/modprobe.d/hostap-utils should be renamed to /etc/modprobe.d/hostap-utils.conf to prevent messages like WARNING: All config files need .conf: /etc/modprobe.d/madwifi, it will be ignored in a future release. WARNING: All config files need .conf: /etc/modprobe.d/hostap-utils, it will be ignored in a future release. by inserting a module with modprobe ath_pci and of course to be prepared for the future... 2. /etc/modprobe.d/madwifi should be rename to /etc/modprobe.d/madwifi.conf or removed if current /etc/modprobe.d/madwifi.conf should be active file but I think /etc/modprobe.d/madwifi is the right file (so it should be renamed) Same reasons as above :-) Now my Questions: 1. With which modules initrd was built? There are no modules in /etc/initramfs-tools/modules :-( Would be nice to insert all used modules of orig initrd of voyage 2. I have read a lot of the problem of renaming eth0 to eth1 etc. if you put a cfcard in an other board because the creation of /etc/udev/rules.d/70-persistent-net.rules but have not found a solution to disable it. I think this should be disabled on an system like voyage which will be used mostly on embedded systems (as the homepages already defines voyage :-)) 3. hwclock does not work anymore nor an alix nor on wrap boards so time is always wrong after power loss :-( root@voyage:~# hwclock Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. What is the clue? Is this also in 0.6 a problem or only with new kernel in 0.7? 4. How can I detect if I'm on wrap or alix board? In voyage-0.5 I could insert module geodewdt and if it was loaded I knew that i'm on alix if not on wrap (for my case of coures working only with this 2 boards) With this I could modify at startup /etc/voyage.conf and put VOYAGE_PROFILE=ALIX or VOYAGE_PROFILE=wrap And so to some wrap/alix spefici stuff at boot up. So I can interchange alix/wrap borads in case of failure of an AP with voyage running which is really nice Anybody using such en enviroment in voyage> 0.5? Ok I admit a lot of question ;-) but I'm still using 0.5.2 and really want to go as soon to 0.7 Greetings and thanks Beat _______________________________________________ Voyage-linux mailing list [email protected] http://list.voyage.hk/mailman/listinfo/voyage-linux
-- Regards, Kim-man "Punky" Tse * Open Source Embedded Solutions and Systems - Voyage Linux (http://linux.voyage.hk) - Voyage ONE (http://linux.voyage.hk/voyage-one) - Voyage MPD (http://linux.voyage.hk/voyage-mpd) * Voyage Store (http://store.voyage.hk) _______________________________________________ Voyage-linux mailing list [email protected] http://list.voyage.hk/mailman/listinfo/voyage-linux
