Modify

Opened 5 years ago

Closed 3 years ago

Last modified 2 years ago

#13004 closed defect (fixed)

reboot hang on x86 PC engines WRAP platform

Reported by: osovskij.k@… Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: kernel Version: Trunk
Keywords: x86 PCEngines wrap reboot hang Cc:

Description

Reboot hangs on x86 PC engines WRAP platform with Attitude Adjustment. Tested on two devices I have: WRAP 2.C and WRAP 2.E. Both based on AMD Geode SC1100, 64 MB DRAM.
Tested with official Attitude Adjustment-rc1 and rev. r35531. Tried different custom builds as well:

  1. default config, selected WRAP target profile in make menuconfig: x86-Generic-PCEngines WRAP - reboot hangs.
  2. default config, WRAP target profile, make kernel_menuconfig: Processor type: GeodeGX1 and Enable X86 board specific fixups for reboot (CONFIG_X86_REBOOTFIXUPS <y>) - reboot hangs.
  3. default config, WRAP target profile, make kernel_menuconfig: Processor type: Pentium-MMX and CONFIG_X86_REBOOTFIXUPS <y> - reboot hangs.
  4. default config, WRAP target profile, make kernel_menuconfig: Processor type: 486 - reboot hangs.
  5. default config, WRAP target profile, make kernel_menuconfig: Processor type: 486 and CONFIG_X86_REBOOTFIXUPS <y> - reboot hangs.
  6. image from http://downloads.openwrt.org/attitude_adjustment/12.09-rc1/x86/generic/openwrt-x86-generic-combined-ext4.img.gz - reboot hangs.

I will gladly provide any additional information if needed.

Attachments (10)

dmesg.log (16.4 KB) - added by osovskij.k@… 5 years ago.
dmesg log
wrap_reboot_hang.txt (15.2 KB) - added by anonymous 5 years ago.
config.gz (23.3 KB) - added by sturgillbd 4 years ago.
kernel config that will allow reboot to work
config.2.gz (23.3 KB) - added by sturgillbd 4 years ago.
kernel config that will allow reboot to work
config.3.gz (23.3 KB) - added by sturgillbd 4 years ago.
kernel config that will allow reboot to work
config.4.gz (23.3 KB) - added by sturgillbd 4 years ago.
kernel config that will allow reboot to work
config.5.gz (23.3 KB) - added by sturgillbd 4 years ago.
kernel config that will allow reboot to work
config.6.gz (23.3 KB) - added by sturgillbd 4 years ago.
kernel config that will allow reboot to work
config.7.gz (23.3 KB) - added by sturgillbd 4 years ago.
kernel config that will allow reboot to work
kmod-hwmon-lm77_3.3.8-1_x86.ipk (3.5 KB) - added by anonymous 4 years ago.

Download all attachments as: .zip

Change History (72)

Changed 5 years ago by osovskij.k@…

dmesg log

comment:1 Changed 5 years ago by osovskij.k@…

tested with latest trunk r35643. Nothing happens past GRUB2 welcome screen. Selecting failsafe or main boot sequence I get no output to serial. Tried different serial speeds, didn't help.
Backfire boots and works fine.
Something related to kernel change from 2.6 to 3.x?

Changed 5 years ago by anonymous

comment:2 Changed 5 years ago by anonymous

Same problem here. Wrap 1C hangs on reboot at message "machine restart". Does not matter if I use "reboot=bios" or not. Attached log says tained kernel - that's due to madwifi. The result is the same without madwifi.

comment:3 Changed 4 years ago by anonymous

I can also confirm the problem on a WRAP.1C. And indeed reboot=b doesn't change the situation.

comment:4 Changed 4 years ago by anonymous

I have the same issue with OpenWrt AA 12.09 on VirualBox

comment:5 Changed 4 years ago by anonymous

I've noticed this defect on x86 generic builds. I've checked trunk(BB) revisions: 37917, 36486, 35664.

comment:6 Changed 4 years ago by sturgillbd

I also have this problem. I am using WRAP boards. I have two WRAP.1E1's and also 2 WRAP.2E1's. I have tried rebuilding the kernel etc. I also tried the latest generic from snapshots/trunk which is using 3.10.24. This version will not even boot. There seems to be a kernel regression in the 3.X kernels which seems to be getting worse as the kernel revisions climb. Has anyone posted these problems at the LMKL? Kamikaze and Backfire work fine. I just like the newer of features of AA and it works great except you have to power cycle the board when you reboot. Using the boards in a mesh network and running myself ragged during the testing phases of my mesh having to power cycle the boards for reboot. May just reinstall backfire for now. I have tried all of the reboot= command lines and none seem to help.

Last edited 4 years ago by sturgillbd (previous) (diff)

comment:7 Changed 4 years ago by sturgillbd

Just built a gentoo install and loaded on the wrap. It uses kernel 3.10.17-gentoo and all works fine. Going to dig through the kernel source for OpenWRT and try to rebuild myself. Will post my results and send findings here if anyone is still tracking this bug.

Changed 4 years ago by sturgillbd

kernel config that will allow reboot to work

Changed 4 years ago by sturgillbd

kernel config that will allow reboot to work

Changed 4 years ago by sturgillbd

kernel config that will allow reboot to work

Changed 4 years ago by sturgillbd

kernel config that will allow reboot to work

Changed 4 years ago by sturgillbd

kernel config that will allow reboot to work

Changed 4 years ago by sturgillbd

kernel config that will allow reboot to work

Changed 4 years ago by sturgillbd

kernel config that will allow reboot to work

comment:8 Changed 4 years ago by anonymous

What exactly did you changed?

comment:9 follow-up: Changed 4 years ago by sturgillbd

Download the config.gz , unzip it and compare to your config.

comment:10 in reply to: ↑ 9 Changed 4 years ago by anonymous

Replying to sturgillbd:

Download the config.gz , unzip it and compare to your config.

Seems too long file to read it all.
Since I'm a bieginner on this:

Is it safe to directly exchange your config over mine (I dont't have so much packages installed but if your config is only for the board settings, then it should work)?

If it's some specific line to change, and if it is not a secret to you, it will be more safer if you specify the exact line changed.

Tnak you for your work!
WRAPs are pretty capable devices, although old enough :)

comment:11 Changed 4 years ago by sturgillbd

The problem is the kernel config. When building the kernel for a WRAP board, the kernel needs to know it is a Geode processor. I changed everything in the kernel config that had an option for Geode from generic X86 to Geode. I then recompiled the whole Openwrt. It isn't a secret. I sat down and went through all of the kernel options. The kernel has a reboot fixup patch for Geode as part of the source. The kernel was not detecting it as a Geode, so I went into the kernel config and set it up as a Geode. If you do not want to go through the trouble of recompiling, Backfire works fine. If you recompile the kernel, you have to use your packages for drivers etc because of the changes you made to the kernel. Lets say you got a new wifi card, It is an atheros card. You will have to use the madwifi packages or the ath5k from the build you made instead of getting the packages from the net. My way of dealing with this is having a local packages directory on my CF card for the drivers etc. Normal packages such as pico or vi are no problem to use from the internet. I am not developer by any means. I am just a determined user :)

comment:12 Changed 4 years ago by sturgillbd

Here are some config lines to check. It has been a while since I got this working so I am just searching through the config file I posted.

CONFIG_X86_REBOOTFIXUPS=y
CONFIG_MGEODEGX1=y

Set those two in your config , recompile, and install.

comment:13 Changed 4 years ago by mikrostart

Ok, I have an installed and runnig generic ext4 x86 openwrt on my wrap 1e.
I added all drivers and programs as an opkg packages. Even I added the sensors' files to track the cpu temp :)
Is it possible to check that kernel configuration right now, or I have to get myself a tools to compile a new image? I'm not lazy but I don't have linux installed - only windows. Is this enough for me to try?
There should be a way to resolve the problem for adding the fixup without a whole new recompiling, and reinstalling.
Is the ext4 the best option for the WRAPs?

comment:14 Changed 4 years ago by anonymous

comment:15 Changed 4 years ago by anonymous

If you want, I can up load my built image somewhere and you can download it. Anything driver related you will have to use the files from the image to install. You can install applications like vi, nano etc from the internet packages. Let me know if you want me to do that. I will have to see if I can upload to mediafire or some other file sharing service. I can open up ftp into my network but would rather not. I doubt you will get any response from the developers.

comment:16 Changed 4 years ago by sturgillbd

I just uploaded a tar.gz of my packages and the base image. Let me know if this works for you. You will have to install the drivers for wifi etc from the local packages. opkg supports local package install. You can read the documentation on opkg to figure it out. I hope this helps. Let me know if it works or not. Been quite a while since I even had one of my WRAPs booted up. Too many projects at the moment to dedicate time to it.

http://www.mediafire.com/download/6abo013y4zayubk/Openwrt.WRAP.tar.gz

comment:17 Changed 4 years ago by anonymous

Thank you for your help.
I thin it should help me enough.
If I'm right the image taht you uploaded is without any packages? Yes, I can install them separately.
Anyway I'll give it a try and I'll let you know.
I'll give you feedback asap.

Thank you again.

comment:18 Changed 4 years ago by sturgillbd

The tarball has the install image and packages. Just doesnt have all packages that are available. Let me know when you get it downloaded. Ill pull it from mediafire then.

comment:19 Changed 4 years ago by anonymous

All done. You ca remove it.
I have everything up and running.
The board restarts without a problems.
You made the restart possible.

The only thing is because of the kernel i can not use the online package driver:

Collected errors:

  • satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-hwmon-lm77:
  • kernel (= 3.3.8-1-fa7af62e0ef1d529ecb7f7efccc706c3) * kernel (= 3.3.8-1-fa7af62e0ef1d529ecb7f7efccc706c3) * kernel (= 3.3.8-1-fa7af62e0ef1d529ecb7f7efccc706c3) *
  • opkg_install_cmd: Cannot install package kmod-hwmon-lm77.

comment:20 Changed 4 years ago by anonymous

By online I mean the openwrt repository.

The packages from your folder are working fine.

Thank you.

comment:21 Changed 4 years ago by anonymous

I came upon this also, how can I fix it:

  • opkg_install_pkg: Package kmod-hwmon-lm77 md5sum mismatch. Either the opkg or the package index are corrupt. Try 'opkg update'.
    • opkg_install_cmd: Cannot install package kmod-hwmon-lm77.

comment:22 Changed 4 years ago by sturgillbd

On my wrap install I set up two repos. One internet based and one local. I comment the line out that I am not going to use by putting a # at the beginning of the line of the config file /etc/opkg.conf

Example for local package use with the package dir as /packages

#src/gz snapshots http://downloads.openwrt.org/attitude_adjustment/12.09/x86/generic/packages
src/gz local file:////packages

After editing the config file and saving it, type opkg update.
Then run opkg install kmod-hwmon-lm77

I never used that kernel module so I cannot say if it is corrupt or not.
I will have to boot up one of my wrap boards to try it. I can then try the module on it.

Changed 4 years ago by anonymous

comment:23 Changed 4 years ago by sturgillbd

Above is the actual package that installed on my wrap with no issues. It was copied from my running wrap board and the lm77 module shows up when loaded using lsmod. No dependency or md5sum errors. I think you needed to set up the local repo by my instructions above. I am going to send my /etc/opkg.conf inline to give the example of how my config file looks.

src/gz local file:////packages
#src/gz attitude_adjustment http://downloads.openwrt.org/attitude_adjustment/12.09/x86/generic/packages
dest root /
dest ram /tmp
lists_dir ext /var/opkg-lists
option overlay_root /overlay

This example is for the local packages in the file system at /packages and the local packages as the active repo.
After the file edit, run "opkg update" without quotes
then run "opkg install kmod-hwmon-lm77_3.3.8-1_x86.ipk​" without quotes
It should work fine
You can also do this under the web interface under system and software. there is a config tab where you update the config file then click update lists. After that browse available packages and install

comment:24 Changed 4 years ago by sturgillbd

On a side note. Loaded driver and read temp on cpu. 38 deg C or 100 deg F. I know module works.
cat /sys/devices/i2c-1/1-0048/temp1_input and divide number by 1000.

comment:25 Changed 4 years ago by anonymous

yes, you're right again - lm77 is a temp driver to keep an eye for the CPU.
Through luci I changed the repo path, installed the lm77 driver from local and then changed the online openwrt repo to install the tools to get a cmd line for the driver - nice.

Do you know once I finish the configuration of the board how can I make an image of the CF card for a backup puroses? Like in windows you can make a system image wihich to "burn" to the CF card in case of problems?

comment:26 Changed 4 years ago by sturgillbd

Every time I get a router set up the way I want it to work, I pull the cf card or hard drive and make an image of it. I use dd in linux. I then store the images on backups and on my file server for quick retrieval. Glad it worked for you.

comment:27 Changed 4 years ago by anonymous

I'll go that way also. With the package system it's a fun to configure the openwrt on WRAP.
I have the following partition size (see bellow), is it normal for a 128MB CF card? Does that mean that the rest of the memory is no patitioned?
# df -h
Filesystem Size Used Available Use% Mounted on
rootfs 47.3M 35.9M 9.0M 80% /
/dev/root 47.3M 35.9M 9.0M 80% /
tmpfs 60.9M 580.0K 60.4M 1% /tmp
tmpfs 512.0K 0 512.0K 0% /dev

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 123M 0 disk

sda1 8:1 1 4.4M 0 part

`-sda2 8:2 1 48.2M 0 part /

comment:28 follow-up: Changed 4 years ago by sturgillbd

Yes. Openwrt is for embedded devices normally. If you want to resize the partitions to use all available space, you will have to use some utilities on the card to resize the partitions. I use Gparted. If I remember correctly, Gparted has a boot cd to booperform these tasks without having linux installed on a pc. Google search Gparted. Make a backup of your cf card in case you make a mistake when trying to resize the root partition

comment:29 Changed 4 years ago by anonymous

Can I create sda3 etc, which to contain only the rest of the space on the CF card?
Can be used for a SMB share etc.
Would prefer fdisk since it's directly available in opkg.

comment:30 Changed 4 years ago by sturgillbd

Yes. Create partition. Make filesystem. Set it to mount the new fs at boot

comment:31 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

comment:32 in reply to: ↑ 28 Changed 3 years ago by mikrostart

Replying to sturgillbd:

Yes. Openwrt is for embedded devices normally. If you want to resize the partitions to use all available space, you will have to use some utilities on the card to resize the partitions. I use Gparted. If I remember correctly, Gparted has a boot cd to booperform these tasks without having linux installed on a pc. Google search Gparted. Make a backup of your cf card in case you make a mistake when trying to resize the root partition

I've just made an attemp to backup the CF card with dd under Windows 7 :)
Well seemed to work good but always errors, and I was only adressing the parititons (the opn wrt nstallation has two partitions, so I opted for Acronis true image :)
Well I think I it did the job because I'm now able to boot the modded OpenWRT OS (for the Wrap) from a different CF card (I made a .tib image with Acronis and restore it to another CF).

Have you tried to use dd under windows os?
I'm asking çause I don't have a linux pc (neither linux live cd image).
Is it easier to do it under linux?

Regards!

comment:33 Changed 3 years ago by sturgillbd

I dont use windows at all so I wouldnt know.

comment:34 Changed 3 years ago by anonymous

Hi again.
I'm stuck with a need of advice:

The config of my WRAP was with 1 wlan card in client mode, delivering net.
I've added another with a similar chipset (ar5413) with the idea this second card to be an AP (I'm trying something like wireless relay/repeater with two separate interfaces).
Now the second card refuses to be in a AP mode and stays only in client mode, no matter where I'm trying to change the mode: in the LUCI; in etc/config/wireless; in console.

I tried to unmount the second card off the board and reboot but radio1 still exist and there're no interfaces on it. When I try to add some it is always in a client mode.

Do you have any idea how to reconfigure openwrt to have two cards installed: one client and one AP. With mikrotik it is pretty easy, but here I'm missing something.

Thanks in advance!
BR

comment:35 Changed 3 years ago by sturgillbd

You may try to remove the wireless config and start fresh. Install both cards in wrap board.
From console, type:
rm /etc/config/wireless
wifi detect > /etc/config/wireless

Then go back and try to reconfigure.

Brian

comment:36 follow-up: Changed 3 years ago by anonymous

I didn't work, I'll try to reflash with the firmware, you gave me.
It is somewhat problematic to change the interface configuration.
The kernell message for the new card is:
phy0 POST FAILED!!
reason (-11)

comment:37 in reply to: ↑ 36 Changed 3 years ago by anonymous

Replying to anonymous:

I didn't work, I'll try to reflash with the firmware, you gave me.
It is somewhat problematic to change the interface configuration.
The kernell message for the new card is:
phy0 POST FAILED!!
reason (-11)

no success again, here's the system log for the wifi cards:

[ 9.454195] ath5k 0000:00:0d.0: registered as 'phy0'
[ 9.475909] ath5k: phy0: POST Failed !!!
[ 9.488136] ath5k: probe of 0000:00:0d.0 failed with error -11
[ 9.506523] ath5k 0000:00:11.0: registered as 'phy1'
[ 10.251379] ath: EEPROM regdomain: 0x0
[ 10.251431] ath: EEPROM indicates default country code should be used
[ 10.251477] ath: doing EEPROM country->regdmn map search
[ 10.251536] ath: country maps to regdmn code: 0x3a[ 10.251580] ath: Country alpha2 being used: US
[ 10.251619] ath: Regpair used: 0x3a
[ 10.253349] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[ 10.257561] ath5k: phy1: Atheros AR5414 chip found (MAC: 0xa5, PHY: 0x61)

comment:38 follow-up: Changed 3 years ago by sturgillbd

I use madwifi for the atheros cards. You seem to be using ath5k. With Ath5k you have to use hostapd to set up the AP. According to your logs, your card may have a problem though. Have you tested both cards ie. tried one at a time and both work?

comment:39 in reply to: ↑ 38 ; follow-up: Changed 3 years ago by microstart

Replying to sturgillbd:

I use madwifi for the atheros cards. You seem to be using ath5k. With Ath5k you have to use hostapd to set up the AP. According to your logs, your card may have a problem though. Have you tested both cards ie. tried one at a time and both work?

I've just tried one at a time, and both worked one after another.
Then again I put them together and now it seems the board is detecting both properly, as you can see below.
Is the madwifi better than ath5k?

[ 9.501500] ath5k 0000:00:0d.0: registered as 'phy0'
[ 10.034126] ath: EEPROM regdomain: 0x0
[ 10.034170] ath: EEPROM indicates default country code should be used
[ 10.034210] ath: doing EEPROM country->regdmn map search
[ 10.034264] ath: country maps to regdmn code: 0x3a
[ 10.034303] ath: Country alpha2 being used: US
[ 10.034337] ath: Regpair used: 0x3a
[ 10.035997] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 10.040305] ath5k: phy0: Atheros AR5213A chip found (MAC: 0x59, PHY: 0x43)
[ 10.061197] ath5k: phy0: RF5112B multiband radio found (0x36)
[ 10.079560] ath5k 0000:00:11.0: registered as 'phy1'
[ 10.094938] cfg80211: Calling CRDA for country: US
[ 10.110196] cfg80211: Regulatory domain changed to country: US
[ 10.127964] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 10.152814] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[ 10.176362] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[ 10.199893] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 10.223424] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 10.246952] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 10.270483] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
[ 11.060855] ath: EEPROM regdomain: 0x0
[ 11.060898] ath: EEPROM indicates default country code should be used
[ 11.060937] ath: doing EEPROM country->regdmn map search
[ 11.060991] ath: country maps to regdmn code: 0x3a
[ 11.061028] ath: Country alpha2 being used: US
[ 11.061062] ath: Regpair used: 0x3a
[ 11.062623] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[ 11.066504] ath5k: phy1: Atheros AR5414 chip found (MAC: 0xa5, PHY: 0x61)

comment:40 in reply to: ↑ 39 Changed 3 years ago by microstart

Replying to microstart:

Replying to sturgillbd:

I use madwifi for the atheros cards. You seem to be using ath5k. With Ath5k you have to use hostapd to set up the AP. According to your logs, your card may have a problem though. Have you tested both cards ie. tried one at a time and both work?

I've just tried one at a time, and both worked one after another.
Then again I put them together and now it seems the board is detecting both properly, as you can see below.
Is the madwifi better than ath5k?

Yes, you were right - the AP mode with ath5k is really difficul. I can't get an idea how to use hostapd. In addition I installed some new kind of luci, and everything is a bit ... newer. Is it safe to change the wifi driver, and can I use the stock one from the repository, since I'm with your custom build?

[ 9.501500] ath5k 0000:00:0d.0: registered as 'phy0'
[ 10.034126] ath: EEPROM regdomain: 0x0
[ 10.034170] ath: EEPROM indicates default country code should be used
[ 10.034210] ath: doing EEPROM country->regdmn map search
[ 10.034264] ath: country maps to regdmn code: 0x3a
[ 10.034303] ath: Country alpha2 being used: US
[ 10.034337] ath: Regpair used: 0x3a
[ 10.035997] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 10.040305] ath5k: phy0: Atheros AR5213A chip found (MAC: 0x59, PHY: 0x43)
[ 10.061197] ath5k: phy0: RF5112B multiband radio found (0x36)
[ 10.079560] ath5k 0000:00:11.0: registered as 'phy1'
[ 10.094938] cfg80211: Calling CRDA for country: US
[ 10.110196] cfg80211: Regulatory domain changed to country: US
[ 10.127964] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 10.152814] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[ 10.176362] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[ 10.199893] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 10.223424] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 10.246952] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 10.270483] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
[ 11.060855] ath: EEPROM regdomain: 0x0
[ 11.060898] ath: EEPROM indicates default country code should be used
[ 11.060937] ath: doing EEPROM country->regdmn map search
[ 11.060991] ath: country maps to regdmn code: 0x3a
[ 11.061028] ath: Country alpha2 being used: US
[ 11.061062] ath: Regpair used: 0x3a
[ 11.062623] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[ 11.066504] ath5k: phy1: Atheros AR5414 chip found (MAC: 0xa5, PHY: 0x61)

comment:41 Changed 3 years ago by sturgillbd

You will have to use the drivers that I built. Anything that is a kernel driver, has to be built against the kernel it is used with. You still have the packages I sent?

comment:42 Changed 3 years ago by anonymous

Yes I have them. So I'll stay with ath5k.

comment:43 Changed 3 years ago by anonymous

Yes I have them. So I'll stay with ath5k.

comment:44 Changed 3 years ago by anonymous

Yes I have them. So I'll stay with ath5k.

comment:45 Changed 3 years ago by anonymous

Yes I have them. So I'll stay with ath5k.

comment:46 follow-up: Changed 3 years ago by sturgillbd

The packages I built have madwifi drivers. It is pretty easy to install. The madwifi drivers allow you to set the mode (station or master) from the web interface. A mikrotik license isnt terribly expensive either. Im considering going that route with my boards

comment:47 in reply to: ↑ 46 Changed 3 years ago by anonymous

Replying to sturgillbd:

The packages I built have madwifi drivers. It is pretty easy to install. The madwifi drivers allow you to set the mode (station or master) from the web interface. A mikrotik license isnt terribly expensive either. Im considering going that route with my boards

Just made it to work:
Got ird of the ath5k.
Reflash.
Installed to new luci.
With winscp I've installed your madwifi driver.
The two cards started successfully nad can be configured independantly.

Now the problems:

  1. I can't get higher tx power. Only 17dbm, no matter what country/regdomain I use.
  1. When setup the repo to be file:////packages, there is a message:

Downloading ​file:////packages/Packages.gz.
wget: not an http or ftp url: ​file:////packages/Packages.gz
Collected errors:

Thre is no file in my repo settings:

src/gz local ​file:////packages
#src/gz attitude_adjustment http://downloads.openwrt.org/attitude_adjustment/12.09/x86/generic/packages
dest root /
dest ram /tmp
lists_dir ext /var/opkg-lists
option overlay_root /overlay

P.S. I agree for MTikOS. I have two other devices working with it and carrying my internet connection - it's quite reliable. Openwrt is just a bit more flexible to play with. I mean the package system has a lot of apps to play with. But yes, you're right for work, MT is a logic choise.

comment:48 Changed 3 years ago by anonymous

somehow I fixed the repos. Only high tx power is still a trick.

comment:49 Changed 3 years ago by sturgillbd

Repos just needed to run opkg update. 17 dbm is just what madwifi does. Dont worry about the output power and just try the link. Seems like I remember the card will still work at full power even though it only reports 17 dbm. I am currently at work and have limited access to my s martphone to reply. Just try the AP when you get it configured. I believe it will work fine

comment:50 Changed 3 years ago by anonymous

I ran the updates 100 times, the problem was some unknown symbol mistaken in the command.

Here're the txpower lists:
root@WRAP:~# iwinfo ath1 txpowerlist

0 dBm ( 1 mW)
5 dBm ( 3 mW)
7 dBm ( 5 mW)
9 dBm ( 7 mW)

11 dBm ( 12 mW)
13 dBm ( 19 mW)
15 dBm ( 31 mW)

  • 17 dBm ( 50 mW)

root@WRAP:~# iwinfo ath0 txpowerlist

0 dBm ( 1 mW)
4 dBm ( 2 mW)
6 dBm ( 3 mW)
8 dBm ( 6 mW)

10 dBm ( 10 mW)
12 dBm ( 15 mW)
14 dBm ( 25 mW)

  • 16 dBm ( 39 mW)

I already configured the board:
the first card - 26dbm capable (ath1 reporting 17dbm up there) is connected to master AP (wan carier).
the second ar5213a is put in master ap for my home network - 20dbm capable CM9 (ath0 reporting 16dbm).

for some reason I can't use iw commands: nl80211 not found

Yes, the network is running normally.
I may stop here, or dig deeper with this:
https://forum.openwrt.org/viewtopic.php?id=45260

comment:51 Changed 3 years ago by anonymous

just fix the iw commands:

ath1 ESSID: "wan"

Access Point:
Mode: Client Channel: 2 (2.417 GHz)
Tx-Power: 17 dBm Link Quality: 29/70
Signal: -67 dBm Noise: -96 dBm
Bit Rate: 54.0 MBit/s
Encryption: WPA2 PSK
Type: madwifi HW Mode(s): 802.11abg
Hardware: 168C [Generic Atheros]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes

root@WRAP:~# iwinfo ath0 info
ath0 ESSID: "link2"

Access Point: 90:A4
Mode: Master Channel: 12 (2.467 GHz)
Tx-Power: 16 dBm Link Quality: 69/70
Signal: -27 dBm Noise: -96 dBm
Bit Rate: unknown
Encryption: none
Type: madwifi HW Mode(s): 802.11abg
Hardware: 168C[Generic Atheros]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes

comment:52 Changed 3 years ago by mikrostart

Greetings again,

just like before, I'm trying to make a wifi relay station with two minipci radio cards.
Thanks to you, I managed so far to make them work, even configured properly, but very often the link drops to 600 kbits/s with no reason.
Tried changing speeds, anntennas, tx powers, even enabled the geode_aes to work, but no luck, I've tried with no encryption also and this happens again.

Do you have any experience where to search for the problem?

comment:53 follow-up: Changed 3 years ago by bittorf@…

with r44331 i can comfirm (dd'ed the gunzipped ext4-image),
that the kernel-symbols

CONFIG_X86_REBOOTFIXUPS=y
CONFIG_MGEODEGX1=y

must be applied, otherwise the board hangs during reboot.
the other thing are working:

[    0.000000] Linux version 3.14.32 (automat@bittorf-wireless.de) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r44150) ) #1 Mon Feb 9 14:09:28 CET 2015
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000007ffffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000fff00000-0x00000000ffffffff] reserved
[    0.000000] Notice: NX (Execute Disable) protection missing in CPU!
[    0.000000] DMI not present or invalid.
[    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000000] e820: last_pfn = 0x8000 max_arch_pfn = 0x100000
[    0.000000] initial memory mapped: [mem 0x00000000-0x017fffff]
[    0.000000] Base memory trampoline at [c009b000] 9b000 size 16384
[    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
[    0.000000]  [mem 0x00000000-0x000fffff] page 4k
[    0.000000] init_memory_mapping: [mem 0x07c00000-0x07ffffff]
[    0.000000]  [mem 0x07c00000-0x07ffffff] page 4k
[    0.000000] BRK [0x015aa000, 0x015aafff] PGTABLE
[    0.000000] init_memory_mapping: [mem 0x00100000-0x07bfffff]
[    0.000000]  [mem 0x00100000-0x07bfffff] page 4k
[    0.000000] ACPI BIOS Error (bug): A valid RSDP was not found (20131218/tbxfroot-211)
[    0.000000] 128MB LOWMEM available.
[    0.000000]   mapped low ram: 0 - 08000000
[    0.000000]   low ram: 0 - 08000000
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
[    0.000000]   Normal   [mem 0x01000000-0x07ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x00001000-0x0009ffff]
[    0.000000]   node   0: [mem 0x00100000-0x07ffffff]
[    0.000000] On node 0 totalpages: 32671
[    0.000000] free_area_init_node: node 0, pgdat c150a640, node_mem_map c7ee7020
[    0.000000]   DMA zone: 32 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 3999 pages, LIFO batch:0
[    0.000000]   Normal zone: 224 pages used for memmap
[    0.000000]   Normal zone: 28672 pages, LIFO batch:7
[    0.000000] Using APIC driver default
[    0.000000] No local APIC present or hardware disabled
[    0.000000] APIC: disable apic facility
[    0.000000] APIC: switched to apic NOOP
[    0.000000] nr_irqs_gsi: 16
[    0.000000] e820: [mem 0x08000000-0xffefffff] available for PCI devices
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32415
[    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz root=/dev/sda2 rootfstype=ext4 rootwait console=tty0 console=ttyS0,38400n8 noinitrd
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Initializing CPU#0
[    0.000000] Memory: 123516K/130684K available (3759K kernel code, 243K rwdata, 1172K rodata, 336K init, 256K bss, 7168K reserved)
[    0.000000] virtual kernel memory layout:
[    0.000000]     fixmap  : 0xfffa2000 - 0xfffff000   ( 372 kB)
[    0.000000]     vmalloc : 0xc8800000 - 0xfffa0000   ( 887 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]       .init : 0xc1510000 - 0xc1564000   ( 336 kB)
[    0.000000]       .data : 0xc13ac0b6 - 0xc150fc00   (1422 kB)
[    0.000000]       .text : 0xc1000000 - 0xc13ac0b6   (3760 kB)
[    0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:2304 nr_irqs:256 16
[    0.000000] CPU 0 irqstacks, hard=c7806000 soft=c7808000
[    0.000000] Console: colour dummy device 80x25
[    0.000000] console [tty0] enabled
[    0.000000] console [ttyS0] enabled
[    0.000000] tsc: Fast TSC calibration using PIT
[    0.000000] tsc: Detected 266.571 MHz processor
[    0.030023] Calibrating delay loop (skipped), value calculated using timer frequency.. 533.14 BogoMIPS (lpj=2665710)
[    0.050058] pid_max: default: 32768 minimum: 301
[    0.060802] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.070090] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.083734] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
[    0.083734] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
[    0.083734] tlb_flushall_shift: -1
[    0.090044] CPU: NSC Unknown (fam: 05, model: 09, stepping: 01)
[    0.105422] Performance Events: no PMU driver, software events only.
[    0.139970] NET: Registered protocol family 16
[    0.154801] cpuidle: using governor ladder
[    0.160067] cpuidle: using governor menu
[    0.183274] PCI: PCI BIOS revision 2.10 entry at 0xfc44b, last bus=0
[    0.190063] PCI: Using configuration type 1 for base access
[    0.382975] bio: create slab <bio-0> at 0
[    0.393089] ACPI: Interpreter disabled.
[    0.416415] SCSI subsystem initialized
[    0.430946] libata version 3.00 loaded.
[    0.433531] usbcore: registered new interface driver usbfs
[    0.441426] usbcore: registered new interface driver hub
[    0.451401] usbcore: registered new device driver usb
[    0.464941] PCI: Probing PCI hardware
[    0.470068] PCI: root bus 00: using default resources
[    0.470113] PCI: Probing PCI hardware (bus 00)
[    0.471614] PCI host bridge to bus 0000:00
[    0.480106] pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
[    0.490104] pci_bus 0000:00: root bus resource [mem 0x00000000-0xffffffff]
[    0.500090] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[    0.510189] pci 0000:00:00.0: [1078:0001] type 00 class 0x060000
[    0.520691] pci 0000:00:0d.0: [168c:001b] type 00 class 0x020000
[    0.520818] pci 0000:00:0d.0: reg 0x10: [mem 0x80000000-0x8000ffff]
[    0.523043] pci 0000:00:0e.0: [100b:0020] type 00 class 0x020000
[    0.523165] pci 0000:00:0e.0: reg 0x10: [io  0x1000-0x10ff]
[    0.523252] pci 0000:00:0e.0: reg 0x14: [mem 0x80040000-0x80040fff]
[    0.523386] pci 0000:00:0e.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[    0.523532] pci 0000:00:0e.0: supports D1 D2
[    0.523589] pci 0000:00:0e.0: PME# supported from D0 D1 D2 D3hot
[    0.525692] pci 0000:00:10.0: [100b:0020] type 00 class 0x020000
[    0.525815] pci 0000:00:10.0: reg 0x10: [io  0x1400-0x14ff]
[    0.525903] pci 0000:00:10.0: reg 0x14: [mem 0x80080000-0x80080fff]
[    0.526041] pci 0000:00:10.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
[    0.526188] pci 0000:00:10.0: supports D1 D2
[    0.526246] pci 0000:00:10.0: PME# supported from D0 D1 D2 D3hot
[    0.528280] pci 0000:00:11.0: [168c:001b] type 00 class 0x020000
[    0.528407] pci 0000:00:11.0: reg 0x10: [mem 0x800c0000-0x800cffff]
[    0.530681] pci 0000:00:12.0: [100b:0510] type 00 class 0x060100
[    0.530793] pci 0000:00:12.0: reg 0x10: [io  0xf400-0xf43f]
[    0.530875] pci 0000:00:12.0: reg 0x14: [io  0xf600-0xf63f]
[    0.533091] pci 0000:00:12.1: [100b:0511] type 00 class 0x068000
[    0.533203] pci 0000:00:12.1: reg 0x10: [io  0xf000-0xf0ff]
[    0.535420] pci 0000:00:12.2: [100b:0502] type 00 class 0x010180
[    0.535575] pci 0000:00:12.2: reg 0x20: [io  0xfc00-0xfc0f]
[    0.537698] pci 0000:00:12.3: [100b:0503] type 00 class 0x040100
[    0.537813] pci 0000:00:12.3: reg 0x10: [mem 0x40011000-0x40011fff]
[    0.540125] pci 0000:00:12.5: [100b:0515] type 00 class 0x068000
[    0.540238] pci 0000:00:12.5: reg 0x10: [io  0xf200-0xf23f]
[    0.540321] pci 0000:00:12.5: reg 0x14: [mem 0x00000000-0x0000003f]
[    0.540402] pci 0000:00:12.5: reg 0x18: [mem 0x00000000-0x0000003f]
[    0.540482] pci 0000:00:12.5: reg 0x1c: [mem 0x00000000-0x0000003f]
[    0.540562] pci 0000:00:12.5: reg 0x20: [mem 0x00000000-0x0000003f]
[    0.540642] pci 0000:00:12.5: reg 0x24: [mem 0x00000000-0x0000003f]
[    0.542774] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 00
[    0.543428] PCI: pci_cache_line_size set to 32 bytes
[    0.550398] Switched to clocksource pit
[    0.563731] pnp: PnP ACPI: disabled
[    0.676143] pci 0000:00:0e.0: BAR 6: assigned [mem 0x08000000-0x0800ffff pref]
[    0.688151] pci 0000:00:10.0: BAR 6: assigned [mem 0x08010000-0x0801ffff pref]
[    0.690130] pci 0000:00:12.5: BAR 1: assigned [mem 0x08020000-0x0802003f]
[    0.700811] pci 0000:00:12.5: BAR 2: assigned [mem 0x08020040-0x0802007f]
[    0.711485] pci 0000:00:12.5: BAR 3: assigned [mem 0x08020080-0x080200bf]
[    0.722157] pci 0000:00:12.5: BAR 4: assigned [mem 0x080200c0-0x080200ff]
[    0.732830] pci 0000:00:12.5: BAR 5: assigned [mem 0x08020100-0x0802013f]
[    0.743488] pci_bus 0000:00: resource 4 [io  0x0000-0xffff]
[    0.743557] pci_bus 0000:00: resource 5 [mem 0x00000000-0xffffffff]
[    0.744251] NET: Registered protocol family 2
[    0.761888] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.773075] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.782399] TCP: Hash tables configured (established 1024 bind 1024)
[    0.791998] TCP: reno registered
[    0.801939] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.819767] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.840007] NET: Registered protocol family 1
[    0.853714] PCI: CLS 32 bytes, default 32
[    0.856957] platform rtc_cmos: registered platform RTC device (no PNP device found)
[    0.862559] NatSemi SCx200 Driver
[    0.872998] GPIO base 0xf400
[    0.882045] Configuration Block base 0x9000
[    0.905079] futex hash table entries: 256 (order: -1, 3072 bytes)
[    1.099068] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    1.109178] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    1.127733] msgmni has been set to 241
[    1.141546] io scheduler noop registered
[    1.153551] io scheduler deadline registered (default)
[    1.177447] isapnp: Scanning for PnP cards...
[    1.538728] isapnp: No Plug & Play device found
[    1.543976] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    1.555711] serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 921600) is a NS16550A
[    1.580255] Non-volatile memory driver v1.3
[    1.593085] Linux agpgart interface v0.103
[    1.607933] [drm] Initialized drm 1.1.0 20060810
[    1.641478] scsi0 : pata_sc1200
[    1.657669] scsi1 : pata_sc1200
[    1.670514] ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0xfc00 irq 14
[    1.681378] ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xfc08 irq 15
[    1.704390] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.714217] ehci-pci: EHCI PCI platform driver
[    1.728990] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.737798] uhci_hcd: USB Universal Host Controller Interface driver
[    1.750032] usbcore: registered new interface driver usb-storage
[    1.772258] i8042: PNP: No PS/2 controller found. Probing ports directly.
[    1.801984] i8042: No controller found
[    1.816283] mousedev: PS/2 mouse device common for all mice
[    1.829814] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
[    1.849262] rtc_cmos rtc_cmos: alarms up to one day, 114 bytes nvram
[    1.859962] enabling scx200 high-res timer (1 MHz +0 ppm)
[    1.876472] Switched to clocksource scx200_hrt
[    1.892338] TCP: cubic registered
[    1.902533] NET: Registered protocol family 17
[    1.916415] 8021q: 802.1Q VLAN Support v1.8
[    1.930579] Using IPI Shortcut mode
[    1.948824] rtc_cmos rtc_cmos: setting system clock to 2000-01-01 00:03:28 UTC (946685008)
[    1.976130] ata1.00: CFA: Hitachi XX.V.3.7.0.0, Rev 0.00, max PIO4
[    1.994948] ata1.00: 250368 sectors, multi 0: LBA
[    2.040439] ata1.00: configured for PIO4 (device error ignored)
[    2.060008] scsi 0:0:0:0: Direct-Access     ATA      Hitachi XX.V.3.7 Rev  PQ: 0 ANSI: 5
[    2.091769] sd 0:0:0:0: [sda] 250368 512-byte logical blocks: (128 MB/122 MiB)
[    2.116719] sd 0:0:0:0: [sda] Write Protect is off
[    2.131373] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    2.132152] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    2.170452]  sda: sda1 sda2
[    2.188704] sd 0:0:0:0: [sda] Attached SCSI removable disk
[    2.312279] EXT4-fs (sda2): mounted filesystem without journal. Opts: (null)
[    2.333772] VFS: Mounted root (ext4 filesystem) readonly on device 8:2.
[    2.356809] Freeing unused kernel memory: 336K (c1510000 - c1564000)
[    2.940673] Clocksource tsc unstable (delta = -84592661 ns)
[    3.382030] zram: Created 1 device(s) ...
[    3.475553] EXT4-fs (zram0): VFS: Can't find ext4 filesystem
[    4.592833] random: nonblocking pool is initialized
[    7.901062] EXT4-fs (sda2): re-mounted. Opts: (null)
[    8.018511] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null)
[   32.288771] NET: Registered protocol family 10
[   32.315617] natsemi dp8381x driver, version 2.1, Sept 11, 2006
[   32.315617]   originally by Donald Becker <becker@scyld.com>
[   32.315617]   2.4.x kernel port by Jeff Garzik, Tjeerd Mulder
[   32.383714] natsemi eth0: NatSemi DP8381[56] at 0x80040000 (0000:00:0e.0), 00:0d:b9:03:34:78, IRQ 10, port TP.
[   32.461898] natsemi eth1: NatSemi DP8381[56] at 0x80080000 (0000:00:10.0), 00:0d:b9:03:34:79, IRQ 11, port TP.
[   32.539661] tun: Universal TUN/TAP device driver, 1.6
[   32.555060] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[   32.662229] nsc_gpio initializing
[   32.700841] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   32.832834] scx200_wdt: timer margin 60 seconds
[   32.948407] u32 classifier
[   32.956756]     input device check on
[   32.967955]     Actions configured
[   33.018492] Mirror/redirect action on
[   33.230548] Loading modules backported from Linux version master-2014-11-04-0-gf3660a2
[   33.254583] Backport generated by backports.git backports-20141023-2-g4ff890b
[   33.356871] ip_tables: (C) 2000-2006 Netfilter Core Team
[   33.418611] nf_conntrack version 0.5.0 (1935 buckets, 7740 max)
[   33.583286] xt_time: kernel timezone is -0000
[   33.660691] cfg80211: Calling CRDA to update world regulatory domain
[   33.700274] cfg80211: World regulatory domain updated:
[   33.715921] cfg80211:  DFS Master region: unset
[   33.729154] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[   33.758747] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   33.783049] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   33.807358] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[   33.831667] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[   33.855986] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[   33.884721] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[   33.909278] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[   33.933586] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[   34.100835] PPP generic driver version 2.4.2
[   34.122108] NET: Registered protocol family 24
[   34.165298] ath5k 0000:00:0d.0: registered as 'phy0'
[   34.827893] ath: EEPROM regdomain: 0x37
[   34.827935] ath: EEPROM indicates we should expect a direct regpair map
[   34.827970] ath: Country alpha2 being used: AW
[   34.827998] ath: Regpair used: 0x37
[   34.831749] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   34.859025] ath5k: phy0: Atheros AR5414 chip found (MAC: 0xa5, PHY: 0x61)
[   34.880713] ath5k 0000:00:11.0: registered as 'phy1'
[   34.951133] cfg80211: Calling CRDA for country: AW
[   34.970462] cfg80211: Regulatory domain changed to country: AW
[   34.988209] cfg80211:  DFS Master region: ETSI
[   35.001181] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[   35.030773] cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   35.055079] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[   35.083822] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[   35.112572] cfg80211:   (5490000 KHz - 5710000 KHz @ 160000 KHz), (N/A, 2700 mBm), (0 s)
[   35.854339] ath: EEPROM regdomain: 0x0
[   35.854382] ath: EEPROM indicates default country code should be used
[   35.854410] ath: doing EEPROM country->regdmn map search
[   35.854456] ath: country maps to regdmn code: 0x3a
[   35.854486] ath: Country alpha2 being used: US
[   35.854513] ath: Regpair used: 0x3a
[   35.858466] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[   35.885658] ath5k: phy1: Atheros AR5414 chip found (MAC: 0xa5, PHY: 0x61)
[   35.907381] cfg80211: Calling CRDA for country: US
[   35.973132] cfg80211: Current regulatory domain intersected:
[   35.990358] cfg80211:  DFS Master region: unset
[   36.003583] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[   36.033175] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   36.057483] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 1700 mBm), (N/A)
[   36.086226] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[   40.418580] Adding 61436k swap on /dev/zram0.  Priority:0 extents:1 across:61436k SS
[   49.846120] eth0: DSPCFG accepted after 0 usec.
[   49.850058] eth0: link up.
[   49.850058] eth0: Setting full-duplex based on negotiated link capability.
[   49.943363] eth1: DSPCFG accepted after 0 usec.
[   49.958640] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   56.169906] IPv6: ADDRCONF(NETDEV_UP): wlan0-1: link is not ready
[   56.245292] IPv6: ADDRCONF(NETDEV_UP): wlan1-1: link is not ready
[   61.307974] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-1: link becomes ready
[   61.411325] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1-1: link becomes ready
[   61.965788] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   62.076314] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[   62.124678] wlan0: Created IBSS using preconfigured BSSID 02:ca:ff:ee:ba:be
[   62.145952] wlan0: Creating new IBSS network, BSSID 02:ca:ff:ee:ba:be
[   62.168161] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   62.298626] wlan1: Created IBSS using preconfigured BSSID 02:ca:ff:ee:ba:be
[   62.320669] wlan1: Creating new IBSS network, BSSID 02:ca:ff:ee:ba:be
[   62.342205] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready

comment:54 in reply to: ↑ 53 ; follow-up: Changed 3 years ago by anonymous

Replying to bittorf@…:

with r44331 i can comfirm (dd'ed the gunzipped ext4-image),
that the kernel-symbols

CONFIG_X86_REBOOTFIXUPS=y
CONFIG_MGEODEGX1=y

must be applied, otherwise the board hangs during reboot.
the other thing are working:

}}}

Yes, you're right, but to apply the fix a recompilation is needed. Correct me if I'm wrong, but in that case you need to point repos to local host and add driver / packages compiled for this exact version.
I'm wondering why OpenWRT comunity is not releasing a dedicated build for the WRAP boards (as for the Alix)?
It must have all fixes and geode/natsemi drivers good-to-go.

comment:55 in reply to: ↑ 54 ; follow-up: Changed 3 years ago by bittorf@…

I'm wondering why OpenWRT comunity is not releasing a dedicated build for the WRAP boards (as for the Alix)?
It must have all fixes and geode/natsemi drivers good-to-go.

somebody (you?) must send a proper patch to the mailinglist, thats all.

comment:56 Changed 3 years ago by russell

On a related note, I recently found booting (either a hang after GRUB or looping back to a reset after GRUB) problems with the Soekris net48xx. This has an AMD Geode SC1100. I bisected the booting problem and discovered the problem began at r42776. I just tried the two kernel config's suggested above with current trunk (r44496) still hung at boot.

comment:57 follow-up: Changed 3 years ago by russell

Thanks to a hint from groz on #openwrt-devel, I was able to determine that I could work around the problem by removing the first two lines in /boot/grub/grub.cfg, which say:

serial --unit=0 --speed=19200 --word=8 --parity=no --stop=1
terminal_input serial; terminal_output serial

It's not immediately clear why those lines were okay before r42776 and not okay after.

comment:58 in reply to: ↑ 55 Changed 3 years ago by mikrostart

Replying to bittorf@…:

I'm wondering why OpenWRT comunity is not releasing a dedicated build for the WRAP boards (as for the Alix)?
It must have all fixes and geode/natsemi drivers good-to-go.

somebody (you?) must send a proper patch to the mailinglist, thats all.

Isn't this ticket quite a bit of a long proper patch for the miling list?
Could you just tell me where and to who to send this two line of a FIXBOOT patch?
I mean - it's already inside the openwrt's kernel. I was just wondering why not implementing a dedicated image, since it's already ported on the WRAP boards.

comment:59 in reply to: ↑ 57 ; follow-up: Changed 3 years ago by mikrostart

Replying to russell:

Thanks to a hint from groz on #openwrt-devel, I was able to determine that I could work around the problem by removing the first two lines in /boot/grub/grub.cfg, which say:

serial --unit=0 --speed=19200 --word=8 --parity=no --stop=1
terminal_input serial; terminal_output serial

It's not immediately clear why those lines were okay before r42776 and not okay after.

So changing settings in grub will solve the problem with reboot?

comment:60 in reply to: ↑ 59 Changed 3 years ago by russell

Replying to mikrostart:

Replying to russell:

Thanks to a hint from groz on #openwrt-devel, I was able to determine that I could work around the problem by removing the first two lines in /boot/grub/grub.cfg, which say:

serial --unit=0 --speed=19200 --word=8 --parity=no --stop=1
terminal_input serial; terminal_output serial

It's not immediately clear why those lines were okay before r42776 and not okay after.

So changing settings in grub will solve the problem with reboot?

It solved my booting problem on Soekris net4826, no kernel config changes from stock OpenWrt.

comment:61 Changed 3 years ago by anonymous

Just noticed there's Alix 2 image folder:
https://downloads.openwrt.org/barrier_breaker/14.07/x86/alix2/

Is this somehow applicable to Wrap boards?
Could this be duplicated as for the Wrap boards? The same folder with bootfix and proprietary drivers for the Wrap?

comment:62 Changed 3 years ago by nbd

  • Resolution set to fixed
  • Status changed from new to closed

please use the new geode subtarget committed in r44809

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.