[iConnect] USB boot and Arch install without serial cable

Install Arch Linux ARM on other devices.

Re: [iConnect] USB boot and Arch install without serial cabl

Postby igorert » Sat Sep 01, 2012 4:20 am

Jef, if you followed patrice's instructions verbatim than please make sure you have/add "-B" option to the wpa_supplicant line in your rc.local; without it, rc.local never exits so your system startup is never properly completed (i.e., init process never finishes processing /etc/inittab).

BTW, it'd be really great if somebody with forum admin rights could edit patrice's post to include -B option so that other folks don't get stuck with this problem ;)

Other than that, your iconnect doesn't seem to be reachable; can you even ping it ("ping 192.168.0.106")? Also, take a look at /var/log/messages to check if the network is really brought up. And check that you don't have iptables in the DAEMONS line in your rc.conf (or make sure you allow port 22 in if you really want to run iptables right away).
igorert
 
Posts: 35
Joined: Sun Jun 26, 2011 5:31 pm
Location: aka chalkbag on irc

Re: [iConnect] USB boot and Arch install without serial cabl

Postby Jef » Sun Sep 02, 2012 6:04 am

Hello Igorert,

First off all I would like to thank You for Your reaction on my questions.
Meanwhile, I have restarted te whole process from scratch, beginning with
"Enable ssh on your Iomega iConnect"
.
Now I' m trying to get things fixed with Nicebloom's method http://archlinuxarm.org/forum/viewtopic.php?f=27&t=1472&p=12796#p12796, same thing is happening as with Patrice's method, I have discovered that the ip that was appearing in the Ui off my router, was from a former session with the native software from Iomega, for some reason the wireless connections appearing with delay in the UI.

I will invest some time trying to use your tips, as soon as I get some spare time (single Dad with tree kids) and I can't afford me in neglecting the education off them. I' m eager to get this thing working although.

I' m thinking in updating the archnumber, hoping this would solve my networkproblems, what do you think?

English is 'nt my native language, so from time to time I'm doubting if I understand all of it, have I understood clearly from Your explication that this method install a Linux distribution on the USB device, without opening the Iomega iconnect?

Greetings, Jef

ps: Forgot to mention that I'm using a normal router i.e. not a Gigabit-router!
Jef
 
Posts: 3
Joined: Thu Aug 30, 2012 3:44 pm

Re: [iConnect] USB boot and Arch install without serial cabl

Postby Jef » Sun Sep 02, 2012 9:43 am

Here is deamon.log

Code: Select all
Aug 31 22:40:41 alarm [   31.278145] systemd-udevd[91]: starting version 188
Aug 31 22:40:42 alarm dhcpcd[248]: version 5.6.0 starting
Aug 31 22:40:42 alarm dhcpcd[248]: all: configured as a router, not a host
Aug 31 22:40:42 alarm dhcpcd[248]: eth0: broadcasting for a lease
Aug 31 22:41:12 alarm dhcpcd[248]: timed out
Aug 31 23:19:09 alarm [   30.888801] systemd-udevd[91]: starting version 188
Aug 31 23:19:09 alarm dhcpcd[263]: version 5.6.0 starting
Aug 31 23:19:09 alarm dhcpcd[263]: all: configured as a router, not a host
Aug 31 23:19:10 alarm dhcpcd[263]: eth0: broadcasting for a lease
Aug 31 23:19:40 alarm dhcpcd[263]: timed out
Aug 31 23:19:41 alarm dhcpcd[365]: version 5.6.0 starting
Aug 31 23:19:41 alarm dhcpcd[365]: wlan0: carrier acquired
Aug 31 23:19:41 alarm dhcpcd[365]: wlan0: carrier lost
Aug 31 23:19:41 alarm dhcpcd[365]: wlan0: waiting for carrier
Aug 31 23:20:11 alarm dhcpcd[365]: timed out
Aug 31 23:34:04 alarm [   29.565444] systemd-udevd[91]: starting version 188
Aug 31 23:34:05 alarm dhcpcd[265]: version 5.6.0 starting
Aug 31 23:34:05 alarm dhcpcd[265]: all: configured as a router, not a host
Aug 31 23:34:05 alarm dhcpcd[265]: eth0: broadcasting for a lease
Aug 31 23:34:35 alarm dhcpcd[265]: timed out
Aug 31 23:34:36 alarm dhcpcd[367]: version 5.6.0 starting
Aug 31 23:34:37 alarm dhcpcd[367]: wlan0: carrier acquired
Aug 31 23:34:37 alarm dhcpcd[367]: wlan0: carrier lost
Aug 31 23:34:37 alarm dhcpcd[367]: wlan0: waiting for carrier
Aug 31 23:35:07 alarm dhcpcd[367]: timed out
Sep  1 00:32:53 alarm [   30.941428] systemd-udevd[91]: starting version 188
Sep  1 00:32:53 alarm dhcpcd[263]: version 5.6.0 starting
Sep  1 00:32:53 alarm dhcpcd[263]: all: configured as a router, not a host
Sep  1 00:32:54 alarm dhcpcd[263]: eth0: broadcasting for a lease
Sep  1 00:33:24 alarm dhcpcd[263]: timed out
Sep  1 00:33:25 alarm dhcpcd[365]: version 5.6.0 starting
Sep  1 00:33:25 alarm dhcpcd[365]: wlan1: interface not found or invalid
Sep  1 01:55:50 alarm [   30.985418] systemd-udevd[91]: starting version 188
Sep  1 01:55:50 alarm dhcpcd[264]: version 5.6.0 starting
Sep  1 01:55:50 alarm dhcpcd[264]: all: configured as a router, not a host
Sep  1 01:55:51 alarm dhcpcd[264]: wlan0: carrier acquired
Sep  1 01:55:51 alarm dhcpcd[264]: wlan0: carrier lost
Sep  1 01:55:51 alarm dhcpcd[264]: wlan0: waiting for carrier
Sep  1 01:56:21 alarm dhcpcd[264]: timed out
Sep  1 01:56:22 alarm dhcpcd[374]: version 5.6.0 starting
Sep  1 01:56:22 alarm dhcpcd[374]: wlan0: waiting for carrier
Sep  1 01:56:52 alarm dhcpcd[374]: timed out
Sep  2 03:56:18 alarm [   30.931565] systemd-udevd[91]: starting version 188
Sep  2 03:56:18 alarm dhcpcd[263]: version 5.6.0 starting
Sep  2 03:56:18 alarm dhcpcd[263]: all: configured as a router, not a host
Sep  2 03:56:19 alarm dhcpcd[263]: wlan0: carrier acquired
Sep  2 03:56:19 alarm dhcpcd[263]: wlan0: carrier lost
Sep  2 03:56:19 alarm dhcpcd[263]: wlan0: waiting for carrier
Sep  2 03:56:49 alarm dhcpcd[263]: timed out
Sep  2 03:56:50 alarm dhcpcd[374]: version 5.6.0 starting
Sep  2 03:56:50 alarm dhcpcd[374]: wlan0: waiting for carrier
Sep  2 03:57:20 alarm dhcpcd[374]: timed out
Sep  2 04:22:58 alarm [   30.706232] systemd-udevd[91]: starting version 188
Sep  2 04:22:58 alarm dhcpcd[266]: version 5.6.0 starting
Sep  2 04:22:58 alarm dhcpcd[266]: all: configured as a router, not a host
Sep  2 04:22:58 alarm dhcpcd[266]: eth0: broadcasting for a lease
Sep  2 04:23:28 alarm dhcpcd[266]: timed out
Sep  2 04:23:30 alarm dhcpcd[368]: version 5.6.0 starting
Sep  2 04:23:30 alarm dhcpcd[368]: wlan0: carrier acquired
Sep  2 04:23:30 alarm dhcpcd[368]: wlan0: carrier lost
Sep  2 04:23:30 alarm dhcpcd[368]: wlan0: waiting for carrier
Sep  2 04:24:00 alarm dhcpcd[368]: timed out


And her is errors.log;
Code: Select all
Aug 31 22:40:41 alarm kernel: [   18.374386] eth0[0]: could not detect attached switch
Aug 31 22:40:41 alarm kernel: [   18.379499] eth0[0]: couldn't create dsa switch instance (error -22)
Aug 31 22:40:41 alarm kernel: [   20.273877] sd 2:0:0:0: [sda] No Caching mode page present
Aug 31 22:40:41 alarm kernel: [   20.280309] sd 2:0:0:0: [sda] Assuming drive cache: write through
Aug 31 22:40:41 alarm kernel: [   20.288991] sd 2:0:0:0: [sda] No Caching mode page present
Aug 31 22:40:41 alarm kernel: [   20.294505] sd 2:0:0:0: [sda] Assuming drive cache: write through
Aug 31 22:40:41 alarm kernel: [   20.332489] sd 2:0:0:0: [sda] No Caching mode page present
Aug 31 22:40:41 alarm kernel: [   20.338001] sd 2:0:0:0: [sda] Assuming drive cache: write through
Aug 31 22:41:12 alarm dhcpcd[248]: timed out
Aug 31 22:41:12 alarm /usr/sbin/crond[310]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory
Aug 31 23:19:09 alarm kernel: [   18.384981] eth0[0]: could not detect attached switch
Aug 31 23:19:09 alarm kernel: [   18.390094] eth0[0]: couldn't create dsa switch instance (error -22)
Aug 31 23:19:09 alarm kernel: [   20.284476] sd 2:0:0:0: [sda] No Caching mode page present
Aug 31 23:19:09 alarm kernel: [   20.290905] sd 2:0:0:0: [sda] Assuming drive cache: write through
Aug 31 23:19:09 alarm kernel: [   20.299591] sd 2:0:0:0: [sda] No Caching mode page present
Aug 31 23:19:09 alarm kernel: [   20.305110] sd 2:0:0:0: [sda] Assuming drive cache: write through
Aug 31 23:19:09 alarm kernel: [   20.331963] sd 2:0:0:0: [sda] No Caching mode page present
Aug 31 23:19:09 alarm kernel: [   20.337479] sd 2:0:0:0: [sda] Assuming drive cache: write through
Aug 31 23:19:40 alarm dhcpcd[263]: timed out
Aug 31 23:19:40 alarm /usr/sbin/crond[323]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory
Aug 31 23:19:41 alarm kernel: [   66.410224] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
Aug 31 23:20:11 alarm dhcpcd[365]: timed out
Aug 31 23:34:04 alarm kernel: [   16.983858] eth0[0]: could not detect attached switch
Aug 31 23:34:04 alarm kernel: [   16.988976] eth0[0]: couldn't create dsa switch instance (error -22)
Aug 31 23:34:04 alarm kernel: [   18.883504] sd 2:0:0:0: [sda] No Caching mode page present
Aug 31 23:34:04 alarm kernel: [   18.889930] sd 2:0:0:0: [sda] Assuming drive cache: write through
Aug 31 23:34:04 alarm kernel: [   18.898741] sd 2:0:0:0: [sda] No Caching mode page present
Aug 31 23:34:04 alarm kernel: [   18.904262] sd 2:0:0:0: [sda] Assuming drive cache: write through
Aug 31 23:34:04 alarm kernel: [   19.242115] sd 2:0:0:0: [sda] No Caching mode page present
Aug 31 23:34:04 alarm kernel: [   19.247628] sd 2:0:0:0: [sda] Assuming drive cache: write through
Aug 31 23:34:35 alarm dhcpcd[265]: timed out
Aug 31 23:34:35 alarm /usr/sbin/crond[325]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory
Aug 31 23:34:36 alarm kernel: [   65.259082] phy1 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
Aug 31 23:35:07 alarm dhcpcd[367]: timed out
Sep  1 00:32:53 alarm kernel: [   18.348638] eth0[0]: could not detect attached switch
Sep  1 00:32:53 alarm kernel: [   18.353752] eth0[0]: couldn't create dsa switch instance (error -22)
Sep  1 00:32:53 alarm kernel: [   20.248247] sd 2:0:0:0: [sda] No Caching mode page present
Sep  1 00:32:53 alarm kernel: [   20.254687] sd 2:0:0:0: [sda] Assuming drive cache: write through
Sep  1 00:32:53 alarm kernel: [   20.263485] sd 2:0:0:0: [sda] No Caching mode page present
Sep  1 00:32:53 alarm kernel: [   20.269002] sd 2:0:0:0: [sda] Assuming drive cache: write through
Sep  1 00:32:53 alarm kernel: [   20.295733] sd 2:0:0:0: [sda] No Caching mode page present
Sep  1 00:32:53 alarm kernel: [   20.301249] sd 2:0:0:0: [sda] Assuming drive cache: write through
Sep  1 00:33:24 alarm dhcpcd[263]: timed out
Sep  1 00:33:24 alarm /usr/sbin/crond[323]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory
Sep  1 00:33:25 alarm dhcpcd[365]: wlan1: interface not found or invalid
Sep  1 01:55:50 alarm kernel: [   18.381503] eth0[0]: could not detect attached switch
Sep  1 01:55:50 alarm kernel: [   18.386618] eth0[0]: couldn't create dsa switch instance (error -22)
Sep  1 01:55:50 alarm kernel: [   20.280984] sd 2:0:0:0: [sda] No Caching mode page present
Sep  1 01:55:50 alarm kernel: [   20.287413] sd 2:0:0:0: [sda] Assuming drive cache: write through
Sep  1 01:55:50 alarm kernel: [   20.295973] sd 2:0:0:0: [sda] No Caching mode page present
Sep  1 01:55:50 alarm kernel: [   20.301486] sd 2:0:0:0: [sda] Assuming drive cache: write through
Sep  1 01:55:50 alarm kernel: [   20.328596] sd 2:0:0:0: [sda] No Caching mode page present
Sep  1 01:55:50 alarm kernel: [   20.334117] sd 2:0:0:0: [sda] Assuming drive cache: write through
Sep  1 01:55:51 alarm kernel: [   34.896698] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
Sep  1 01:56:21 alarm dhcpcd[264]: timed out
Sep  1 01:56:21 alarm /usr/sbin/crond[334]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory
Sep  1 01:56:52 alarm dhcpcd[374]: timed out
Sep  2 03:56:18 alarm kernel: [   18.405100] eth0[0]: could not detect attached switch
Sep  2 03:56:18 alarm kernel: [   18.410221] eth0[0]: couldn't create dsa switch instance (error -22)
Sep  2 03:56:18 alarm kernel: [   20.304499] sd 2:0:0:0: [sda] No Caching mode page present
Sep  2 03:56:18 alarm kernel: [   20.310928] sd 2:0:0:0: [sda] Assuming drive cache: write through
Sep  2 03:56:18 alarm kernel: [   20.319614] sd 2:0:0:0: [sda] No Caching mode page present
Sep  2 03:56:18 alarm kernel: [   20.325131] sd 2:0:0:0: [sda] Assuming drive cache: write through
Sep  2 03:56:18 alarm kernel: [   20.352236] sd 2:0:0:0: [sda] No Caching mode page present
Sep  2 03:56:18 alarm kernel: [   20.357753] sd 2:0:0:0: [sda] Assuming drive cache: write through
Sep  2 03:56:18 alarm kernel: [   34.760366] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
Sep  2 03:56:49 alarm dhcpcd[263]: timed out
Sep  2 03:56:49 alarm /usr/sbin/crond[333]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory
Sep  2 03:57:20 alarm dhcpcd[374]: timed out
Sep  2 04:22:58 alarm kernel: [   18.391218] eth0[0]: could not detect attached switch
Sep  2 04:22:58 alarm kernel: [   18.396329] eth0[0]: couldn't create dsa switch instance (error -22)
Sep  2 04:22:58 alarm kernel: [   20.290728] sd 2:0:0:0: [sda] No Caching mode page present
Sep  2 04:22:58 alarm kernel: [   20.297158] sd 2:0:0:0: [sda] Assuming drive cache: write through
Sep  2 04:22:58 alarm kernel: [   20.305719] sd 2:0:0:0: [sda] No Caching mode page present
Sep  2 04:22:58 alarm kernel: [   20.311233] sd 2:0:0:0: [sda] Assuming drive cache: write through
Sep  2 04:22:58 alarm kernel: [   20.349342] sd 2:0:0:0: [sda] No Caching mode page present
Sep  2 04:22:58 alarm kernel: [   20.354859] sd 2:0:0:0: [sda] Assuming drive cache: write through
Sep  2 04:23:28 alarm dhcpcd[266]: timed out
Sep  2 04:23:29 alarm /usr/sbin/crond[326]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory
Sep  2 04:23:30 alarm kernel: [   66.226476] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no response from hardware
Sep  2 04:24:00 alarm dhcpcd[368]: timed out
Jef
 
Posts: 3
Joined: Thu Aug 30, 2012 3:44 pm

Re: [iConnect] USB boot and Arch install without serial cabl

Postby igorert » Tue Sep 04, 2012 3:43 pm

Updating the arcNumber should indeed fix your wireline issue, which will hopefully make it easier for you to set up wireless. You can always restore the original arcNumber if you need to boot into the stock iomega kernel again.
igorert
 
Posts: 35
Joined: Sun Jun 26, 2011 5:31 pm
Location: aka chalkbag on irc

Previous

Return to [Please read announcement] Community-Supported Devices

Who is online

Users browsing this forum: No registered users and 2 guests