Code: Select all
modprobe asus_eee
Code: Select all
modprobe asus_eee
Not yet.simargl wrote:Is it working?
Code: Select all
[root@archpup eeepc-linux]# ln -s /usr/src/linux-3.6.8 /lib/modules/3.6.8/build
ln: failed to create symbolic link '/lib/modules/3.6.8/build': File exists
[root@archpup eeepc-linux]# makepkg --asroot
==> Making package: eeepc-linux 0.39a1-8 (Fri Jan 18 19:48:32 CET 2013)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
warning: database file for 'core' does not exist
warning: database file for 'extra' does not exist
warning: database file for 'community' does not exist
==> Retrieving Sources...
-> Found asus_eee-0.39a1.tar.gz
-> Found asus_eee-0.39a1-spinlock-kernel-2.6.39.patch
==> Validating source files with md5sums...
asus_eee-0.39a1.tar.gz ... Passed
asus_eee-0.39a1-spinlock-kernel-2.6.39.patch ... Passed
==> Extracting Sources...
-> Extracting asus_eee-0.39a1.tar.gz with bsdtar
==> Starting build()...
==> Patching...
patching file asus_eee.c
Makefile:47: /lib/modules/3.6.8/build/.config: No such file or directory
make: *** No rule to make target `/lib/modules/3.6.8/build/.config'. Stop.
==> ERROR: A failure occurred in build().
Aborting...
[root@archpup eeepc-linux]#
Code: Select all
ln -s /usr/src/linux-3.6.8 /lib/modules/3.6.8/build
ln -s /usr/src/linux-3.6.8 /lib/modules/3.6.8/source
Code: Select all
rm -rf /lib/modules/3.6.8/build
ln -s /usr/src/linux-3.6.8 /lib/modules/3.6.8/build
Code: Select all
[[root@archpup eeepc-linux]# makepkg --asroot
==> Making package: eeepc-linux 0.39a1-8 (Fri Jan 18 20:39:28 CET 2013)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
-> Found asus_eee-0.39a1.tar.gz
-> Found asus_eee-0.39a1-spinlock-kernel-2.6.39.patch
==> Validating source files with md5sums...
asus_eee-0.39a1.tar.gz ... Passed
asus_eee-0.39a1-spinlock-kernel-2.6.39.patch ... Passed
==> Extracting Sources...
-> Extracting asus_eee-0.39a1.tar.gz with bsdtar
==> Removing existing pkg/ directory...
==> Starting build()...
==> Patching...
patching file asus_eee.c
make: nothing to be done for 'patch'.
make[1]: Entering directory `/tmp/eeepc-linux/src/asus_eee-0.39a1'
cd /lib/modules/3.6.8/build && make -C /lib/modules/3.6.8/build M=/tmp/eeepc-linux/src/asus_eee-0.39a1 modules
make[2]: Entering directory `/usr/src/linux-3.6.8'
CC [M] /tmp/eeepc-linux/src/asus_eee-0.39a1/asus_eee.o
Building modules, stage 2.
MODPOST 1 modules
LD [M] /tmp/eeepc-linux/src/asus_eee-0.39a1/asus_eee.ko
make[2]: Leaving directory `/usr/src/linux-3.6.8'
make[1]: Leaving directory `/tmp/eeepc-linux/src/asus_eee-0.39a1'
==> Tidying install...
-> Purging unwanted files...
-> Compressing man and info pages...
-> Stripping unneeded symbols from binaries and libraries...
==> Creating package...
-> Generating .PKGINFO file...
-> Adding install file...
-> Compressing package...
==> Finished making: eeepc-linux 0.39a1-8 (Fri Jan 18 20:39:34 CET 2013)
[root@archpup eeepc-linux]# pacman -U eeepc-linux 0.39a1-8
loading packages...
error: 'eeepc-linux': could not find or read package
[root@archpup eeepc-linux]#
Code: Select all
pacman -U /path/to/eeepc-linux.pkg.tar.xz
Code: Select all
[root@archpup eeepc-linux]# pacman -U /tmp/eeepc-linux/eeepc-linux-0.39a1-8-i686.pkg.tar
loading packages...
error: '/tmp/eeepc-linux/eeepc-linux-0.39a1-8-i686.pkg.tar': could not find or read package
[root@archpup eeepc-linux]# pacman -U /tmp/eeepc-linux/eeepc-linux-0.39a1-8-i686.pkg.tar.xz
loading packages...
resolving dependencies...
looking for inter-conflicts...
Targets (1): eeepc-linux-0.39a1-8
Total Installed Size: 0.02 MiB
Proceed with installation? [Y/n] Y
(1/1) checking package integrity [----------------------] 100%
(1/1) loading package files [----------------------] 100%
(1/1) checking for file conflicts [----------------------] 100%
(1/1) checking available disk space [----------------------] 100%
(1/1) installing eeepc-linux [----------------------] 100%
==> Remember to add 'asus_eee' to a file '/etc/modules-load.d/asus_eee.conf' to load it on boot.
[root@archpup eeepc-linux]#
simargl wrote:After you install package with pacman -U pkgname, typeto load module. Is it working?Code: Select all
modprobe asus_eee
Code: Select all
[root@archpup ~]# modprobe asus_eee
modprobe: FATAL: Module asus_eee not found.
[root@archpup ~]#
Code: Select all
install -Dm644 $srcdir/asus_eee-$pkgver/asus_eee.ko $pkgdir/usr/lib/modules/$(uname -r)/kernel/acpi/asus_eee.ko || return 1
Code: Select all
install -Dm644 $srcdir/asus_eee-$pkgver/asus_eee.ko $pkgdir/lib/modules/$(uname -r)/kernel/acpi/asus_eee.ko || return 1
Code: Select all
pacman -R eeepc-linux
makepkg --asroot
pacman -U eeepc-linux-0.39a1-8-i686.pkg.tar.xz
Code: Select all
(1/1) installing eeepc-linux
depmod: WARNING: could not open /lib/modules/3.6.8/modules.order: No such file or directory
depmod: WARNING: could not open /lib/modules/3.6.8/modules.builtin: No such file or directory
==> Remember to add 'asus_eee' to a file '/etc/modules-load.d/asus_eee.conf' to load it on boot.' to a file '/etc/modules-load.d/asus_eee.conf' to load it on boot.
[root@archpup eeepc-linux]#
if it's working fine then just ignore that. one thing u might want to do though is edit the /etc/rc.d/MODULESCONFIG file and add the module to the addlist line to look like this:anikin wrote:Redone.
It loads without a hitch and is working now. Sweet. Although, these 2 lines don't look good - should I be concerned? And there's no directory '/etc/modules-load.d', let alone 'asus_eee.conf' file. Should I create them?Code: Select all
(1/1) installing eeepc-linux depmod: WARNING: could not open /lib/modules/3.6.8/modules.order: No such file or directory depmod: WARNING: could not open /lib/modules/3.6.8/modules.builtin: No such file or directory ==> Remember to add 'asus_eee' to a file '/etc/modules-load.d/asus_eee.conf' to load it on boot.' to a file '/etc/modules-load.d/asus_eee.conf' to load it on boot. [root@archpup eeepc-linux]#
Code: Select all
modprobe asus_eee
how to using it in terminal step by step? please i am newbieciento wrote:Using wvdial for internet connection, required 2 steps,
(not unique to ArchPup):
rm /var/lock
then
mkdir /var/lock
(if the first lock is a file, not a folder)
Evidently wvdial wants to make it's own lock file,
and needs a lock folder to put it in, and if not found,
constantly seeks it, /dev/ttyACM0 used by some usb modems
will then report the device is busy.
Copy or create /etc/wvdial.conf
Thanks Simargl, for adding this crucial piece of net connectivity!