and a few other places, as well as searching the forums here, I'm still not sure howto use opkg to setup the driver for my atheros ar8151 lan card.
opkg update
seems like a good start...
but then opkg install what?
opkg install kmod-ath8151 doesn't seem to work..
Then once the drivers installed, is a reboot going to be enough? Or is everything I've read completely wrong, as all that stuff I've read is about atheros wifi?????
It's built into the motherboard, windows says
PCI\VEN_1969&DEV_1073&SUBSYS_04731028&REV_C0
PCI\VEN_1969&DEV_1073&SUBSYS_04731028
PCI\VEN_1969&DEV_1073&CC_020000
PCI\VEN_1969&DEV_1073&CC_0200
Which doesn't help in the Linux world much. What linux commands do you want thrown at it once I boot back up into openwrt??
I know linux mint detects and uses the card without difficulty..
I think the package for older Atheros gigabit wired LAN chips would be kmod-atl1. There is also kmod-atl1c and kmod-atl1e. It would not hurt to install them all and let the system probe and match the chip to the driver. Then you can examine the log to see which one actually seized the card and un-install the other ones that are not necessary.
1969:1073 is actually very helpful as it is what the driver will key off of. A Google search on "PCI 1069:1073" brings up several references, suggesting the atl1e driver is appropriate.
kmod install kmod-atl1e or c
error cannot satisfy the following dependents for either driver
kernel 4.14.63-1- long checksum
I'm not so sure the force option is the best here... But if its all I got then I'll try it. The weird thing is the opkg find command returns a packages that are the same version as my kernel..
oops ya, sorry. not kmod but opkg. Those commands you gave are what I used in my ssh session, but failed to replicate in my post. Even using
opkg --force-depends kmod-at1lc
or
opkg --force-depends kmod-at1lc
Install a release build (18.06.2) first. Kmods and other packages for snapshot builds are not kept on the server for long. When running a snapshot build you have to also install all the packages you need on the same day.
Hmm... Well looks like I'm stuck for not fully understanding how things get screwy with forks... Sorry for wasting everyone's time, as this wouldn't even be the right forum to post such a question. For my friends, the version of open-wrt that I'm trying to use is in fact the latest x86 version of goldenorb found here....https://www.ofmodemsandmen.com/firmware.html.
Since goldenorb is open-wrt, with 4g modem capabilities, I thought this the forum to ask, especially since the rooter folks don't even have an official forum, but I suppose that's like asking an ubuntu question in the debian forums. But even then it won't work.. https://www.ofmodemsandmen.com/package.html
I simply used rufus to write out the x86 goldenorb disk image to a usb that I boot off it. Thus I don't really understand "snapshot"? As far as I knew, I was working with a disk image that once restored to a drive, was capable of upgrading etc, just like any official dd-wrt x86 build / supported linux distribution.
There are many to choose from.. squashfs verses rootfs verses ext4 verses others. If I wanted to use an official build to get my lan card working, which one? And then how hard would it be for me to add emm7455 4g modem drivers.. I assume if I can even get that far that I'll need to then script my own modem at commands as I wouldn't expect the dd-wrt user interface to have any of that.
The one based on your preference of EXT4 or SquashFS. You then install the drivers, you will likely have to download them; and copy the IPK install file the partition for install.
Ddwrt has nothing to do with OpenWrt. Only come here if you're running official OpenWrt from downloads.openwrt.org.
Use either x86/generic for older Pentium 4 chips that are 32 bit only, or x86/64 if your chip supports 64 bit and there is more than 4GB of RAM.
The ext4 combined is like a desktop where you have one big filesystem that is completely read-write. The squashfs has a ROM section and a writeable overlay, as is common on smaller routers. The squashfs has options to "reset to default settings" and "upgrade and keep settings" which aren't possible with ext4.
"Snapshot" -- daily build from current master branch. Many of us run "official" snapshots on a daily basis, or ones that we build ourselves. Downside (and, arguably upside) is that packages have to "match" the build of the day.
"Release" -- Periodic "stable" builds -- Packages available "for a while" -- though 18.06 is getting to be close to a year old at this time and there are many improvements on master.
Note that, for all practical purposes, packages should never be "upgraded", but a new image and self-consistent set of packages flashed.
Though ROOTer may be based on OpenWrt, it is modified in ways that make its support the responsibility of that group.