You are not logged in.
I've been unsuccessfully trying to build the custom kernel from AUR. Running Arch64 I wanted to compile in a 32bit chroot environment with a specific makepkg.conf (I'd like to compile all custom packages that way and then just transfer to the One). I'm however getting the following error when making of the kernel should start:
making the kernel!
CHK include/linux/version.h
UPD include/linux/version.h
CHK include/linux/utsrelease.h
UPD include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-x86
HOSTCC scripts/conmakehash
HOSTCC scripts/kallsyms
CC scripts/mod/empty.o
scripts/mod/empty.c:1: Error: code model »kernel« not supported in 32-bit mode
scripts/mod/empty.c:1: not implemented: 64-bit not not compiled in
make[2]: *** [scripts/mod/empty.o] Error 1
make[1]: *** [scripts/mod] Error 2
make[1]: *** Waiting for not yet finished processes...
make: *** [scripts] Error 2
==> ERROR: Build failed.
Aborting ...
My makepkg.conf has the following CFLAGS set "-march=prescott -Os -pipe -fomit-frame-pointer". Anyone got a clue what's the issue here? For I do not. I apparently must have something to do with 32 and 64bit modes...
On a side note, the config file distributed with PKGBUILD is no longer complete. make silentoldconfig requires several interaction by the compiler. (I know the package is already flagged as out of date.)
As I will be receiving my new One tomorrow along with a 8 GB SDHC card I was wondering if there was a way to have not only /home but also /var on the SD card. Can I create two partitions on the SD card? Or alternatively bind /var as a subdir in /home?
Last edited by Inkaine (2008-10-28 11:16:27)
Offline
lspci for the (wired) Ethernet gives me:
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E PCI Express Fast Ethernet controller (rev ff)
What exactly must I do to load it? modprobe r8169 hangs
If I am supposed to use a custom driver from the internet, how can I get it into my install environment?
Offline
Modprobe the right driver. I think the module is rtl8101.ko
Offline
zenix wrote:EDIT2: ethernet works, but wireless still reports nothing though I'm sure that something is there.
Did you ensure to run iwlist scan as root? Also try to connect to a known network, even if scanning does not find it.
No luck on either. Before hand anyways, calling iwlist as user or root would return nothing.
Offline
It appears that r8169 is the proper driver for my board: http://hardware4linux.info/component/36147/
Has anybody else experienced the "modprobe r8169" command hanging? Did y'all have to type this command at all to get the network working?
Offline
I think this situation is getting a bit out of hand.
The right module to load is indeed r8169 but for some reason it doesn't work in arch's stock kernel, so you'll need to download Realtek's. Or if you're brave enough use my build ( please, review it and compile it so mistakes can be detected).
Wireless works flawlessly with madwifi drivers and with some glitches with ath5k. If no wireless networks are in range, you're not root, you have RFkill switch on, you don't have a AP in range or you're device has malfunctioned.
About the CFLAGS in the middle is to grant those are used in compile and not other than the Aspire One can handle afterwards.
Yeah, the AUR isn't updated.... Sorry about that, I've been really busy lately
Offline
Oh, sorry, reading my previous post over I wasn't really clear. I'm running Arch64 on a Athlon64 X2. Then I chroot into my 32bit build environment and there I have two makepkg.conf's - one for the Athlon and another with the aforementioned march setting specifically for the One. So "prescott" might not run on my system even. The main difference between your CFLAGS are -Os instead of -O2/3 (I thought smaller size would be nice) and the addition of -fomit-frame-pointer, which according to the Gentoo wiki should work with the Atom. I wonder if -Os is really useful but still these value shouldn't be the compile issues. But I got no clue how to solve the 32bit/64bit conflict. Anyone else been successful compiling the kernel26-one in a arch32 chroot yet?
Edit: Oddly the kernel compiles successfully from Arch64 directly. Does the provision of CFLAGS in the PKGBUILD override the settings in my athlon64-tuned makepkg.conf?
Last edited by Inkaine (2008-10-29 03:15:31)
Offline
gothicknight: Thank you. On another PC I can easily download Realtek's driver, but how do I get it to the acer aspire one, assuming I'm installing from a USB drive I prepared with flashnul in Windows. I can't add files to the USB drive after being prepared by flashnul. Also, if this process is something that every AA1 user must do to install Archlinux, how could the AA1 installation guide in the wiki ignore this crucial step. I know it's not your job to update the wiki, but I'm wondering how the guide could be useful to anybody without this information to get the wired network working. Perhaps the guide assumes that you will be using the wireless network?
Offline
I think this situation is getting a bit out of hand.
The right module to load is indeed r8169 but for some reason it doesn't work in arch's stock kernel, so you'll need to download Realtek's. Or if you're brave enough use my build ( please, review it and compile it so mistakes can be detected).
Wireless works flawlessly with madwifi drivers and with some glitches with ath5k. If no wireless networks are in range, you're not root, you have RFkill switch on, you don't have a AP in range or you're device has malfunctioned.
About the CFLAGS in the middle is to grant those are used in compile and not other than the Aspire One can handle afterwards.
Yeah, the AUR isn't updated.... Sorry about that, I've been really busy lately
OMG! Oh wow... it was the kill switch... I'm so sorry Now, I have 3 questions:
How do I disable the switch? (e.g. shifting it won't do anything) I don't particulary like it.
After killing the switch, how do I disable/enable the wireless card? (to preserve power).
If I wanted to, could I rebind the killswitch to toggle something else? (say, the touchpad)
EDIT: I said 2 questions and asked 3...
Last edited by zenix (2008-10-29 02:40:58)
Offline
Regarding the r8169 issues with the stock kernel: I also have modprobe r8169 hanging when issued at some time when the system is booted. However, r8169 added to the modules array in rc.conf did work for me. I assume there are some problems with module order.
Offline
Regarding the r8169 issues with the stock kernel: I also have modprobe r8169 hanging when issued at some time when the system is booted. However, r8169 added to the modules array in rc.conf did work for me. I assume there are some problems with module order.
So you installed from CD/USB with no network connectivity but adding r8169 at the front of your modules list in rc.conf made wired networking work upon reboot?
Offline
thomasd wrote:Regarding the r8169 issues with the stock kernel: I also have modprobe r8169 hanging when issued at some time when the system is booted. However, r8169 added to the modules array in rc.conf did work for me. I assume there are some problems with module order.
So you installed from CD/USB with no network connectivity but adding r8169 at the front of your modules list in rc.conf made wired networking work upon reboot?
Well, I would try a different approach.
Install arch core system in the AA1 and boot with stock kernel (don't forget to disable blacklisted modules), compile the module and install it on the running ARCH instalation, blacklist r8169, insmod the new one from realtek, et voilá.... profit
Or you can try my kernel, either way should work.
Offline
Thank you for your reply and patience.
Install arch core system in the AA1 and boot with stock kernel (don't forget to disable blacklisted modules), compile the module and install it on the running ARCH instalation, blacklist r8169, insmod the new one from realtek, et voilá.... profit
Or you can try my kernel, either way should work.
Please humor me and correct me where I'm wrong. Install arch core. During installation disable blacklisted modules. -- Does this mean adding a ! before the module in rc.conf? Which modules need to be disabled during installation? r8169? ath_pci? ath5k? all of those? more?
After installation reboot. Reformat USB stick and download to it either the Realtek drivers from Realtek, or your special kernel.
Assuming I use the Realtek drivers, which modules would I blacklist at this point? I'm confused because you specify blacklisting modules twice. I already blacklisted them during installation, right? Even if I didn't blacklist during installation, just changing the rc.conf only affects which modules are loaded on startup, so I'd have to either restart or manually remove the modules, correct?
Assuming I want to use your kernel, is there a set of directions on how to properly compile and replace the kernel?
Of course I am a noob, but I don't mind reading through a guide and following directions. Thanks again.
Offline
You'll need to blacklist after installing the r8101 module the kernel's r8169 module. For that, please check the section 'Kernel >=2.6.27 '.
For compiling a AUR pkgbuild you'll need to refer to AUR wiki. It's mainly download the package to a folder, check the sources, do makepkg -i and update you're grub /boot/grub/menu.lst and add a entry for vmlinuz-one
If you really want to try my kernel without having to compile, check this forum thread for the URL of it. I haven't still got the time to update the latest build into AUR, as I'm currently testing the 2.6.27.4 and make a release for it.
Offline
maybe you should skip the 27 kernel serious and try the 28.rc2
Offline
thomasd wrote:Regarding the r8169 issues with the stock kernel: I also have modprobe r8169 hanging when issued at some time when the system is booted. However, r8169 added to the modules array in rc.conf did work for me. I assume there are some problems with module order.
So you installed from CD/USB with no network connectivity but adding r8169 at the front of your modules list in rc.conf made wired networking work upon reboot?
What I did is install the core image, install a newer stock kernel (>=2.6.26) from a usb flash drive and add r8169 to rc.conf. This did work for me.
However, some people are reporting problems with r8169. I had some problems that ethernet was only working on every other boot, but this has been solved for me in a later kernel version.
Offline
I think I'll leave 2.6.28 get a bit more stable, RC2 is still to early to be put to the test IMHO.
So here's the new 2.6.27.4 build: http://clientes.netvisao.pt/gtknight/ke … pkg.tar.gz
Offline
vegai wrote:schuay wrote:I'm using the stock kernel 2.6.27 with ath5k and haven't experienced any problems. Wireless works perfectly for me.
Maybe you still have ath5k blacklisted in rc.conf?Hmm, I didn't make any changes, but when I retried this today, the wireless works. With WPA/PSK and all. It's a bit more vulnerable to bad signal and recovers in a rather ugly way (cuts connections easier than madwifi did), but it is adequate for my needs.
And ath5k is statically compiled to the kernel in kernel26-one.
Not any longer
I've recompiled the kernel with both ath5k (kernel) and ath_pci (madwifi) in this new release as modules so you may blacklist/use whatever fits you the most.
Also the new kernel is compiled with -O3 (don't expect any notable speed, just for trying if it works smoother...).And here's the URL: http://clientes.netvisao.pt/gtknight/ke … pkg.tar.gz
I noticed that kernel26-one was updated in AUR. Just to confirm. Except ath5k and madwifi_hal (ath_pci, ath_hal).
There isn't anything compiled as module, right?
thanks.
Offline
I think I'll leave 2.6.28 get a bit more stable, RC2 is still to early to be put to the test IMHO.
So here's the new 2.6.27.4 build: http://clientes.netvisao.pt/gtknight/ke … pkg.tar.gz
Your last kernel build didn't have the "usbserial" and "option" modules I need for my 3G usb dongle, did you include them in this build? If not could you include them for your next build?
`Less importantly the xpad module for xbox controllers would be kind of useful.
Anyway, thanks for the kernel builds.
Offline
gothicknight wrote:I think I'll leave 2.6.28 get a bit more stable, RC2 is still to early to be put to the test IMHO.
So here's the new 2.6.27.4 build: http://clientes.netvisao.pt/gtknight/ke … pkg.tar.gz
Your last kernel build didn't have the "usbserial" and "option" modules I need for my 3G usb dongle, did you include them in this build? If not could you include them for your next build?
`Less importantly the xpad module for xbox controllers would be kind of useful.
Anyway, thanks for the kernel builds.
Humm... wierd, I've used the Kconfig from the last build. I'm not currently in my AA1, can you please confirm that those modules are really missing? Thanks
EDIT: There's a huge amount of modules compiled in kernel26-one package such as iptables, networking, USBserial,... Things a ultramobile laptop could need.
Last edited by gothicknight (2008-10-31 14:05:12)
Offline
Humm... wierd, I've used the Kconfig from the last build. I'm not currently in my AA1, can you please confirm that those modules are really missing? Thanks
EDIT: There's a huge amount of modules compiled in kernel26-one package such as iptables, networking, USBserial,... Things a ultramobile laptop could need.
Well, the modules definitely aren't there, but if they are built in, that would explain their non-existence, but the /dev/ttyUSB nodes are not being created even when I booted with the dongle plugged in. I haven't yet tried your new build, so I'll do that now.
EDIT: Just tried the new build, the modules are there and the device nodes get created and I can connect to the internet with my dongle.
Last edited by retsaw (2008-10-31 21:06:37)
Offline
Hm...googling didn't turn up anything, so, anyone know of a pragmatic way to turn off the wireless card or the touch pad? (and, be able to turn them back on.)
Offline
Hm...googling didn't turn up anything, so, anyone know of a pragmatic way to turn off the wireless card or the touch pad? (and, be able to turn them back on.)
You can disable the touchpad with Fn-F7, and of course enable it again. This key worked for me out of the box without configuring anything.
Offline
Any chance of compiling pciehp as a module for your next kernel26-one release, gothicknight? Having the card readers function properly off the bat with -one would be great
Offline
Any chance of compiling pciehp as a module for your next kernel26-one release, gothicknight? Having the card readers function properly off the bat with -one would be great
What do you mean by "function properly"? If you mean the hotpluging it doesn't work
Offline