You are not logged in.
Hello everyone,
I have Arch with kernel-eee on my EEE 900 but I am having trouble getting sound to work.
rc.conf
MOD_AUTOLOAD="yes"
MODULES=()
lsmod
ipv6
ath5k
mac80211
cfg80211
I thought this kernel included all the necessary modules. Did I miss something?
I got gnome-alsamixer and tested with a mp3 file using mplayer but no sound. I also tried inserting the option line in modprobe.conf explained in the wiki but it did not fix anything.
Offline
Offline
So I've gotten my 1000h to run well with the zen 4g or toofishes kernel. The only issue i'm having with both is that i can't get my USB drives to automount. I can mount them manually.
when I plug it in I get this:
sudo tail -f /var/log/messages.log
Password:
Jan 20 03:12:29 eee scsi 2:0:0:0: Direct-Access Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 2
Jan 20 03:12:29 eee sd 2:0:0:0: [sdb] 31506432 51-byte hardware sectors (16131 MB)
Jan 20 03:12:29 eee sd 2:0:0:0: [sdb] Write Protect is off
Jan 20 03:12:29 eee sd 2:0:0:0: [sdb] 31506432 512-byte hardware sectors (16131 MB)
Jan 20 03:12:29 eee sd 2:0:0:0: [sdb] Write Protect is off
Jan 20 03:12:29 eee logger: cannot find module scsi:t-0x00
Jan 20 03:12:29 eee logger: cannot find module sd_mod
Jan 20 03:12:29 eee sdb: sdb1
Jan 20 03:12:29 eee sd 2:0:0:0: [sdb] Attached SCSI removable disk
Jan 20 03:12:29 eee sd 2:0:0:0: Attached scsi generic sg1 type 0
I can't figure out how to find these modules... meh. I don't see them in the SCSI device section in menuconfig.
Anywyas. any help would be nice. it's a bit irritating to have to manually mount the device.
Offline
So I've gotten my 1000h to run well with the zen 4g or toofishes kernel. The only issue i'm having with both is that i can't get my USB drives to automount. I can mount them manually.
when I plug it in I get this:
sudo tail -f /var/log/messages.log Password: Jan 20 03:12:29 eee scsi 2:0:0:0: Direct-Access Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 2 Jan 20 03:12:29 eee sd 2:0:0:0: [sdb] 31506432 51-byte hardware sectors (16131 MB) Jan 20 03:12:29 eee sd 2:0:0:0: [sdb] Write Protect is off Jan 20 03:12:29 eee sd 2:0:0:0: [sdb] 31506432 512-byte hardware sectors (16131 MB) Jan 20 03:12:29 eee sd 2:0:0:0: [sdb] Write Protect is off Jan 20 03:12:29 eee logger: cannot find module scsi:t-0x00 Jan 20 03:12:29 eee logger: cannot find module sd_mod Jan 20 03:12:29 eee sdb: sdb1 Jan 20 03:12:29 eee sd 2:0:0:0: [sdb] Attached SCSI removable disk Jan 20 03:12:29 eee sd 2:0:0:0: Attached scsi generic sg1 type 0
I can't figure out how to find these modules... meh. I don't see them in the SCSI device section in menuconfig.
Anywyas. any help would be nice. it's a bit irritating to have to manually mount the device.
These drivers are built-in and are not modules. Sounds like some userspace program is too dumb to accommodate that?
Offline
Thanks toofishes, for pointing me in the right direction. Updated udev, downgraded hal-0.5.11-7 to hal-0.5.11-4 and it works perfectly with thunar-volman. ensured that user is in group storage. heh.
The modules thing was throwing me way off... YAY!
Offline
toofishes wrote:I guess it must be the cosmic rays hitting my machine that make it work when I use two fingers then.
LOL...
Using synclient -m 100 and touching the touchpad with more than 1 finger I only get "1" under the "f" field.
I'm going crazy trying to understand why you get the two-finger scrolling and I don't...EDIT: I've searched on the web and found other 701 which can't enable the two-fingers features...this seems something hardware related.
Did you try it out with the OEM installation or did you format immediately like I did?
Offline
punkeroso wrote:toofishes wrote:I guess it must be the cosmic rays hitting my machine that make it work when I use two fingers then.
LOL...
Using synclient -m 100 and touching the touchpad with more than 1 finger I only get "1" under the "f" field.
I'm going crazy trying to understand why you get the two-finger scrolling and I don't...EDIT: I've searched on the web and found other 701 which can't enable the two-fingers features...this seems something hardware related.
Did you try it out with the OEM installation or did you format immediately like I did?
The second one...:D
Offline
Does anyone here use the "boot booster" option ? There is nothing about it in the Arch Wiki, but it makes the startup really fast !
HowTo (French)
I would like to know if it works for you, and if I should add it to the Wiki ?
Offline
Hi,
this message is for toofishes:
I get this message while booting your kernel:
alg: cipher: Test 1 failed on encryption for aes-asm
Searching, I found that this is because aes has been built in the kernel, and not as module.
Regards
Offline
Hi,
this message is for toofishes:
I get this message while booting your kernel:alg: cipher: Test 1 failed on encryption for aes-asm
Searching, I found that this is because aes has been built in the kernel, and not as module.
Regards
Sounds like a broken implementation if it can't be compiled in?
Offline
I've been trying to get toofishes' kernel-eee to work on my EEE, but so far I keep getting No init found kernel panics. Any ideas as to why this is happening and how to fix it? I've reinstalled twice now, and have made sure my menu.lst was correct.
Offline
Want Arch, but not "install" it, have it be really fast on she SD card and have session saving?
See my post:
http://chakra-project.org/bbs/viewtopic … 1059#p1059
Last edited by bwh1969 (2009-01-24 16:06:51)
Offline
How do you overclock the EeePC with this new 2.6.27eee kernel? The package eeepc-linux seems to be removed and I couldn't compile it from myself, any tips?
I had a similar issue and solved it... see the last paragraph of my post here:
http://chakra-project.org/bbs/viewtopic … 1059#p1059
Last edited by bwh1969 (2009-01-24 16:08:03)
Offline
On my 701 I have most things working, but I can't get the Fn-F2 (the wifi toggle hotkey) or the sound hotkeys (Fn-F7, Fn-F8, or Fn-F9) working. Wifi works, and sound works, but I can't toggle wifi with the hotkeys nor can I mute or adjust sound levels with hotkeys. The other hotkey combos seem to work fine. Any ideas why this may be? Thanks!
Acer Aspire 3003LCi - Arch Linux + Fluxbox
ASUS EEE PC 701 4G - Arch Linux + Fluxbox
Offline
I saw an eee-control package on AUR, but have not tried it, I know that eeebuntu has this package and it fixes these issues,
Offline
Just to follow up: I had forgotten to install alsa-utils. Once I installed that, my volume and muting issues were eliminated. Now it's just toggling the wifi that remains an issue.
Last edited by gtalum (2009-01-27 02:52:50)
Acer Aspire 3003LCi - Arch Linux + Fluxbox
ASUS EEE PC 701 4G - Arch Linux + Fluxbox
Offline
I tried to use this to install eee-control. Kernel 2.6.27 on eee-pc 701
http://its.hip.googlepages.com/eee-control.tar.gz
I managed to create the package, and install it. When I launch the daemon, I get some errors that it is looking to start and stop daemons that are in /etc/init.d/ and that is a debian reference. In Arch, it would be /etc/rc.d and I changed the path in the setup file that was created in /usr/bin, only to find the referred to daemons don't even exist on my system, I.e. [acpid]
I deleted the references in the setup file and ran it again but it also tells me that it needs to unload a eee-module that is loaded, but then errors out that it can't unload it because it isn't loaded? A bit of a conundrum.
This issue might be because I have another module added and compiled (eee.ko) to allow for adjusting the front side bus. I might have to remove that first? I think I do, but since I am stuck with a native kernel for my Chakra-live setup, I need to make sure my FSB can go to 100 on my 701, so if I had to choose between the two, I am stuck using the eee.ko with the non-eee-pc modified kernel so that I can have this.* I would rather Wifi tap my battery... as generally when I am on battery, I am surfing the net somewhere anyway. I think I will see if alsa-utils is installed to sove the sound thing Fn+bright up and down do work and that is a battery saver.
If one brings down the interface and rmmod's the driver temporarily for the wifi, and the light stays on, it it still tapping a lot of juice, or being disabled with no driver, does it just "sit there" being on but not working and using much power?
*Only on the 701 would this be an issue:-(
Last edited by bwh1969 (2009-01-27 14:44:08)
Offline
If one brings down the interface and rmmod's the driver temporarily for the wifi, and the light stays on, it it still tapping a lot of juice, or being disabled with no driver, does it just "sit there" being on but not working and using much power?
I'd like the answer to this one too
I think I have read that even if the interface is down with "ifconfig wlan0 down", some crappy drivers might eat _more_ juice in that state. But this is because of crappy drivers, so probably the majority is fine.
Also, I think the best way to reduce power consumption is to use an rfkill switch. On my 1000, the wifi switch is /sys/class/rfkill/rfkill0/state while the bluetooth one is /sys/class/rfkill/rfkill1/state. But you need proper kernel support for this. I think 2.6.29 introduce some fixes for bluetooth/wifi rfkill switches on the eeepcs.
Offline
Hmm, I wonder though, if not only if you bring the interface down, you unload the driver, that it stops the unit from trying to transmit (ie, if I use ndiswrapper...
ifconfig wlan0 down
/etc/rc.d/networking stop **
rmmod ndiswrapper
** not using my own pc right now, does Arch have "networking" as a daemon in /etc/rc.d... Debian/Ubuntu has /etc/init.d/networking. This just keeps it from automatically loading the driver and bringing up the interface again. I know that network-manager tries to bring the driver and interface back up.
Offline
@toofishes
hi, it is possible to make rfkill as module?
If it's builtin I cant pass default_state parameter to get wifi off by default at startup,
it would be better to have a chance to change this parameter.
thanks for reply
Offline
We've seen above that you pass parameters to an LKM by specifying something like io=0x300 on the insmod command. For a module that is bound into the base kernel, you pass parameters to it via the kernel boot parameters. One common way to specify kernel boot parameters is at a lilo boot prompt. Another is with an append statement in the lilo configuration file.
The kernel initializes an LKM at the time you load it. It initializes a bound-in module at boot time.
Since there is only one string of kernel boot parameters, you need some way within that string to identify which parameters go to which modules. The rule for this is that if there is a module named xyz, then a kernel boot parameter named xyz is for that module. The value of a kernel boot parameter is an arbitrary string that makes sense only to the module.
Not necessary to compile rfkill as a module
Offline
I now about that, but I couldnt find right key to pass parameter, this article helps me thanks
Offline
It should probably look like this in you grub file:
kernel /vmlinuz26 root=/dev/sda6 ro rfkill.default_state=WHATEVER
Last edited by big_gie (2009-01-29 22:08:46)
Offline
can someone with eeepc 900 post his xorg.conf, please?
Offline
Here is my xorg.conf for my eeepc 900
Section "ServerLayout"
Identifier "ArchLinux"
Screen 0 "Screen0"
InputDevice "keyboard"
InputDevice "mouse"
InputDevice "synaptics"
EndSection
Section "Files"
# RgbPath "/usr/share/X11/rgb.txt"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
Load "glx"
Load "dri"
Load "dbe"
Load "extmod"
Load "synaptics"
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail"
Option "BlankTime" "5"
Option "AIGLX" "false"
Option "AutoAddDevices" "false"
EndSection
Section "InputDevice"
Identifier "keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbLayout" "us"
Option "XkbVariant" ""
EndSection
Section "InputDevice"
Identifier "mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "Protocol" "IMPS/2"
Option "Emulate3Buttons" "yes"
Option "ZAxisMapping" "4 5"
Option "CorePointer"
EndSection
#Section "InputDevice"
# Identifier "mouse"
# Driver "evdev"
# Option "Dev Name" "Logitech USB Optical Mouse"
# Option "Dev Phys" "usb-0000:00:1d.1-1/input0"
# Option "SendCoreEvents"
# Option "evBits" "+1-2"
# Option "keyBits" "~272-287"
# Option "relBits" "~0-2 ~6 ~8"
# Option "Pass" "3"
#EndSection
Section "InputDevice"
Identifier "synaptics"
Driver "synaptics"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "LeftEdge" "1000"
Option "RightEdge" "5400"
Option "TopEdge" "1000"
Option "BottomEdge" "4900"
Option "PalmDetect" "0"
Option "SHMConfig" "true"
Option "SendCoreEvents" "yes"
Option "HorizEdgeScroll" "1"
Option "VertEdgeScroll" "1"
Option "RBCornerButton" "0"
Option "RTCornerButton" "0"
Option "MaxSpeed" "0.9"
# You will also need the following 3 lines if you're using Xorg 1.5RC6 or newer
Option "TapButton1" "1"
Option "TapButton2" "2"
Option "TapButton3" "3"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "ASUS"
ModelName "eeePC 900"
Modeline "1024x600" 48.96 1024 1064 1168 1312 600 601 604 622 -hsync -vsync
EndSection
Section "Device"
Identifier "Card0"
Driver "intel"
VendorName "Intel Corporation"
BoardName "Mobile 915GM/GMS/910GML Express Graphics Controller"
BusID "PCI:0:2:0"
Option "AccelMethod" "EXA"
Option "MigrationHeuristic" "greedy"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection
Offline