[Voyage-linux] installation on vmware client
hi I try to install voyage linux as a client os on vmware and following the steps on the cd-rom guide on http://cvs.voyage.hk/cgi-bin/viewcvs.cgi/voyage-custom/src/live-cd/overlay_fs/README.live-cd?rev=1.5view=markup I have some problems to install voyage and the guide is not very detailed and. Therefore I thought I will go through it step be step to show you where the problems started. Maybe this descriptions can be used for a bit more extended (dummy proof) installation guide. On the wiki maybe? So here it goes: ~ From the guide: ~~~ | 1. Create distribution directory for installation | # mkdir /tmp/root | # mount -o loop /live_media/casper/filesystem.squashfs /tmp/root | # cd /tmp/root | 2. Make a mount point for installation disk | # mkdir /tmp/cf | OK done - no problems, but the next step let me wondering if things go alright ~ From the guide: ~~~ | ... | 3. Format target disk device | # /usr/local/sbin/format-cf.sh /dev/hda | ... here the issues start: There is no /dev/hda device, but /dev/hdc. Is that problem? Well I execute the command on step 3.) it anyway: $ /usr/local/sbin/format-cf.sh /dev/hda Press ENTER to continue to format flash memory on /dev/hda should I see /dev/hda now? Because the directory is not here: $ ls /dev/hda ls: /dev/hda: No such file or directory Is that a problem? ~ From the guide: ~~~ | ... | 4. Start voyage.update installation script | # /usr/local/sbin/voyage.update | | Following the instruction to select /tmp/root as distribution directory, and | /tmp/cf as mount point. After the installation complete, simple reboot the | board and Voyage will be started! | ... Here I wish the guide to be a bit more detailed. Here is what I see running step 4.): -- $ /usr/local/sbin/voyage.update 1 - Create new Voyage Linux disk 2 - Update existing Voyage configuration 3 - Exit (default=1 [Create new Voyage Linux disk]): $ 1 -- Where is the Voyage Linux distribution directory? (default=/tmp/root): $ /tmp/root -- What would you like to do? 1 - Specify Distribution Directory 2 - Select Target Profile 3 - Select Target Disk 4 - Select Target Bootstrap Loader 5 - Configure Target Console 6 - Copy Distribution to Target 7 - Exit (default=2 [ Select Target Profile]): $ 2 -- Please select Voyage profile: 1 - 4501 2 - 4511/4521 3 - 4801 4 - 5501 5 - ALIX 6 - Generic PC 7 - Notebook *pcmdia) 8 - WRAP (default=8 [WRAP]) $ 6 -- What would you like to do? 1 - Specify Distribution Directory 2 - Select Target Profile 3 - Select Target Disk 4 - Select Target Bootstrap Loader 5 - Confuigure Target Console 6 - Copy Distribution to Target 7 - Exit (default=3 [ Select Target Disk]): $ 3 -- Partitions information Major Minor #blocksname 8 08388608 sda 7 0 28228 loop0 7 128228loop1 Which device accesses the target disk [/dev/hde]? $ /dev/hda Error: /dev/hda is not a disk device! $ /dev/hde Error: /dev/hda is not a disk device! -- Ok - here is where the voyage ends for me. I think I have two connected problems here - not sure if /dev/hda is really really created - therefore could not choose /dev/hda/ as target disk Could somebody help me with this? Thanks a lot. Ben ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] vogage-lenny dhcp ntpdate?
When voyage-lenny boots with the /etc/network/interfaces config below... how does it obtain the DHCP lease for eth0? I can't find dhclient on the disk anywhere. Ultimately, I am trying to get ntpdate to run every time the eth0 lease is obtained or renewed. I don't need a full ntpd install. ---[snip /etc/network/interfaces ]--- auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp ---[/snip]--- The eth0 interface is getting a DHCP lease as it should, but how? Also, since this file exists shouldn't ntpdate be running after each DHCP event? /etc/dhcp3/dhclient-exit-hooks.d/ntpdate -parker ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
Re: [Voyage-linux] Experimental booting problems on WRAP board
Punky, I got this working. Thank you. I grabbed the voyage-lenny.iso and booted it under parallels on a MacBookPro. Inserted the CF card reader and successfully ran the voyage-linux installer. Now voyage-lenny is booting perfectly on my old WRAP board. -parker On Mon, Oct 13, 2008 at 9:39 AM, Punky Tse [EMAIL PROTECTED] wrote: Hi Frank, Sorry I forgot: http://www.punknix.com/?q=node/118 This is by design, you should use reply to all. - Punky Frank Parker wrote: Punky, can you give me a link to your blog post about booting voyage-lenny using qemu on ubuntu? I searched the bog but could not find it. Thanks! Also, I just noticed replies from the list are only going back to the sender, not to the list. Is this by design? Should I change the address to voyage-linux@list.voyage.hk on each reply so the list can archive our discussions? -parker On Mon, Oct 13, 2008 at 9:12 AM, Punky Tse [EMAIL PROTECTED] wrote: Hi, In your case, I still prefer you to install it using live CD + PXE. See my blog to see how to boot voyage-lenny using qemu on ubuntu. Then, read /README.pxe to see how to pxe boot and install. Honestly I have no clue on kernel too old problem. Regards, Punky Frank Parker wrote: I'm using an Ubuntu 7.10 Desktop system to write the voyage install to the CF card. The Ubuntu system has 2.6.22 kernel. I guess I need to install from a Debian Lenny host system. Is that correct? -parker On Sun, Oct 12, 2008 at 7:48 PM, Kim-man 'Punky' TSE [EMAIL PROTECTED] wrote: Hi Frank, I don't why this problem occurs: FATAL: kernel too old What is your host machine that run voyage.update? Another way is to install using live cd or pxe. Regards, Punky Frank Parker wrote: Duh! Sorry about that. OK, I downloaded voyage-lenny and the installer seems to be broken. Again, this is a WRAP board so I tried the WRAP profile during installation. I get: FATAL: kernel too old Removing dnsmasq.pxe.conf in /etc/dnsmasq.more.conf Fatal Error: Trouble running grub - dialog was: FATAL: kernel too old copyfiles.sh script completed I tried the Generic PC profile and I got: FATAL: kernel too old Removing dnsmasq.pxe.conf in /etc/dnsmasq.more.conf Fatal Error: Trouble running grub - dialog was: FATAL: kernel too old copyfiles.sh script completed I also tried using lilo instead of grub and I got: FATAL: kernel too old Removing dnsmasq.pxe.conf in /etc/dnsmasq.more.conf Running lilo chroot: lilo: No such file or directory Fatal Error: Failure during chroot to to run lilo Any clues? -parker -- Regards, Punky Voyage Solutions (http://solution.voyage.hk) * Embedded Solutions and Systems - Mesh Networking, Captive Portal, IP Surveillance, VoIP/PBX - Network Engineering, Development Platform and Consultation ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
Re: [Voyage-linux] installation on vmware client
thanks, that helped On Mon, Oct 13, 2008 at 9:08 AM, Punky Tse [EMAIL PROTECTED] wrote: Hi Ben, Step 3, use cat /proc/partitions to see all your disk details. VMWare by default create scsi disk, which would be /dev/sda. Or you should recreate your disk image using ide. Regards, Punky Ben Aurel wrote: hi I try to install voyage linux as a client os on vmware and following the steps on the cd-rom guide on http://cvs.voyage.hk/cgi-bin/viewcvs.cgi/voyage-custom/src/live-cd/overlay_fs/README.live-cd?rev=1.5view=markup I have some problems to install voyage and the guide is not very detailed and. Therefore I thought I will go through it step be step to show you where the problems started. Maybe this descriptions can be used for a bit more extended (dummy proof) installation guide. On the wiki maybe? So here it goes: ~ From the guide: ~~~ | 1. Create distribution directory for installation | # mkdir /tmp/root | # mount -o loop /live_media/casper/filesystem.squashfs /tmp/root | # cd /tmp/root | 2. Make a mount point for installation disk | # mkdir /tmp/cf | OK done - no problems, but the next step let me wondering if things go alright ~ From the guide: ~~~ | ... | 3. Format target disk device | # /usr/local/sbin/format-cf.sh /dev/hda | ... here the issues start: There is no /dev/hda device, but /dev/hdc. Is that problem? Well I execute the command on step 3.) it anyway: $ /usr/local/sbin/format-cf.sh /dev/hda Press ENTER to continue to format flash memory on /dev/hda should I see /dev/hda now? Because the directory is not here: $ ls /dev/hda ls: /dev/hda: No such file or directory Is that a problem? ~ From the guide: ~~~ | ... | 4. Start voyage.update installation script | # /usr/local/sbin/voyage.update | | Following the instruction to select /tmp/root as distribution directory, and | /tmp/cf as mount point. After the installation complete, simple reboot the | board and Voyage will be started! | ... Here I wish the guide to be a bit more detailed. Here is what I see running step 4.): -- $ /usr/local/sbin/voyage.update 1 - Create new Voyage Linux disk 2 - Update existing Voyage configuration 3 - Exit (default=1 [Create new Voyage Linux disk]): $ 1 -- Where is the Voyage Linux distribution directory? (default=/tmp/root): $ /tmp/root -- What would you like to do? 1 - Specify Distribution Directory 2 - Select Target Profile 3 - Select Target Disk 4 - Select Target Bootstrap Loader 5 - Configure Target Console 6 - Copy Distribution to Target 7 - Exit (default=2 [ Select Target Profile]): $ 2 -- Please select Voyage profile: 1 - 4501 2 - 4511/4521 3 - 4801 4 - 5501 5 - ALIX 6 - Generic PC 7 - Notebook *pcmdia) 8 - WRAP (default=8 [WRAP]) $ 6 -- What would you like to do? 1 - Specify Distribution Directory 2 - Select Target Profile 3 - Select Target Disk 4 - Select Target Bootstrap Loader 5 - Confuigure Target Console 6 - Copy Distribution to Target 7 - Exit (default=3 [ Select Target Disk]): $ 3 -- Partitions information Major Minor #blocksname 8 08388608 sda 7 0 28228 loop0 7 128228loop1 Which device accesses the target disk [/dev/hde]? $ /dev/hda Error: /dev/hda is not a disk device! $ /dev/hde Error: /dev/hda is not a disk device! -- Ok - here is where the voyage ends for me. I think I have two connected problems here - not sure if /dev/hda is really really created - therefore could not choose /dev/hda/ as target disk Could somebody help me with this? Thanks a lot. Ben ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Alix 3c2 Bundle For Sale
I hope emailing this doesn't bother anyone. I've got an Alix 3c2 bundle I'd like to get rid of. All works 100%. Here's what I've got, all comes as one package, not piecing it out. - Alix 3c2 board - Aluminum Alix 3c Case (no USB cutouts) - EnGenius EMP-8602 Plus-S Mini PCI Wireless Card (600mw) - 1 pair 9 dBi Rubber Duck Omni RP-SMA. I built an access point with this gear, and I've lost interest and have no time to continue playing. Asking $190 shipped to your door (Continental US). J. ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
Re: [Voyage-linux] vogage-lenny dhcp ntpdate?
Hi Frank, See /CHANGELOG. It mentioned that dhclient is replaced by pump. See /etc/network/if-up.d/ntpdate. It seems ntpdate would run when an interface is up. Regards, Punky Frank Parker wrote: When voyage-lenny boots with the /etc/network/interfaces config below... how does it obtain the DHCP lease for eth0? I can't find dhclient on the disk anywhere. Ultimately, I am trying to get ntpdate to run every time the eth0 lease is obtained or renewed. I don't need a full ntpd install. ---[snip /etc/network/interfaces ]--- auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp ---[/snip]--- The eth0 interface is getting a DHCP lease as it should, but how? Also, since this file exists shouldn't ntpdate be running after each DHCP event? /etc/dhcp3/dhclient-exit-hooks.d/ntpdate -parker ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux -- Regards, Punky Voyage Solutions (http://solution.voyage.hk) * Embedded Solutions and Systems - Mesh Networking, Captive Portal, IP Surveillance, VoIP/PBX - Network Engineering, Development Platform and Consultation ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Compiling drivers for VIA mini pci card ( solomon) vt6655
Hi ! I am getting the following errors when compiling the drivers for this Mini PCI card from VIA with Voyage 0.5.2. - symvers is missing - modules will have no dependencies or modversions then it go to building modules stage 2 MODPOST 1 modules /bin/sh : scripts/mod/modpost: No such file or directory and then Errror 127 then quits. what is this modpost ? what am I missing ? I tried compiling this in another pure debian etch it goes fine ? Please help ! Cheers Rad ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
[Voyage-linux] Re: Compiling drivers for VIA mini pci card ( solomon) vt6655
set -e; for d in driver ; do make -C $d install ; done make[1]: Entering directory `/boot/vt6655_v118_02/driver' make -C /lib/modules/2.6.23-486-voyage/build SUBDIRS=/boot/vt6655_v118_02/driver modules make[2]: Entering directory `/usr/src/linux-source-2.6.23-voyage' WARNING: Symbol version dump /usr/src/linux-source-2.6.23-voyage/Module.symver s is missing; modules will have no dependencies and modversions. Building modules, stage 2. MODPOST 1 modules /bin/sh: scripts/mod/modpost: No such file or directory make[3]: *** [__modpost] Error 127 make[2]: *** [modules] Error 2 make[2]: Leaving directory `/usr/src/linux-source-2.6.23-voyage' make[1]: *** [default] Error 2 make[1]: Leaving directory `/boot/vt6655_v118_02/driver' make: *** [install] Error 2 voyage: On Tue, Oct 14, 2008 at 1:05 AM, varadarajan narayanan [EMAIL PROTECTED] wrote: Hi ! I am getting the following errors when compiling the drivers for this Mini PCI card from VIA with Voyage 0.5.2. - symvers is missing - modules will have no dependencies or modversions then it go to building modules stage 2 MODPOST 1 modules /bin/sh : scripts/mod/modpost: No such file or directory and then Errror 127 then quits. what is this modpost ? what am I missing ? I tried compiling this in another pure debian etch it goes fine ? Please help ! Cheers Rad ___ Voyage-linux mailing list Voyage-linux@list.voyage.hk http://list.voyage.hk/mailman/listinfo/voyage-linux
