Ubuntu Wiki

• Contact: ["NicolòChieffo"]

• Brand: ASUS

• Model: M6800Ne

• Website: http://www.asus.com/products4.aspx?l1=5&l2=24&l3=128&model=39&modelmenu=1

• S/N:

Current Issues

• Battery not detected: please use at least Bios 208Ae

• System hangs at the end of halt/reboot process: This model does not support Local Apic. Edit /boot/grub/menu.lst find #kopt=/dev/hd...... (do NOT uncomment it!) add nolapic at the end of the line and run sudo update-grub. Now reboot OR disable it in your kernel config (Processor type and features --> [] Local APIC support on uniprocessors) and recompile

  • I believe it works without nolapic in dapper. - VincentUntz

  • yes, in fact I didn't write the magic word Dapper! should I remove averything about breezy and leave oinly dapper stuff to tidy up the page?

• Very rarely. Image heavily disturbed (flickering) if framebuffer is enabled: kind of resolution is to switch to console CTRL-ALT-F1 and switch back to X ALT-F7 every time you have this issue. Another fix may be disable framebuffer: add vga=normal to boot options, but you will lose splash screen at boot.

• SD/MMC Card reader not supported. there is a [http://mmc.drzeus.cx/wiki/ project] which is trying to develop some drivers but it's at a beginning stage.

  • Please can you test the MMC stuff again, I think some sdhci crack went in recently. -PaulSladen

  • RE: this is the output of inserting a RS-MMC in the reader (taken from /var/log/messages), please tell me if I have to do something else!

    Feb 22 18:43:45 localhost kernel: [4294884.426000] pccard: PCMCIA card inserted into slot 0 BR Feb 22 18:43:45 localhost kernel: [4294884.426000] pcmcia: registering new device pcmcia0.0

    Feb 22 18:46:34 localhost kernel: [4295053.141000] pccard: card ejected from slot 0

    • Does cardctl info show anything? Also, do you have an SD card you could test with? -PaulSladen

    • RE: here you are (again using RS-MMC), now I don't have any SD I'm sorry.. I'll ask a friend..

    PRODID_1="RICOH" BRPRODID_2="Bay1Controller" BRPRODID_3="" BRPRODID_4="" BRMANFID=0000,0000 BRFUNCID=254 BRPRODID_1="" BRPRODID_2="" BRPRODID_3="" BRPRODID_4="" BRMANFID=0000,0000 BRFUNCID=255

• Resume in Dapper seems to work now! temperature is normal, usb is running, sound is ok, eth is ok, wireless is ok, except that if I had wireless switched off I get it turned on after the resume! (in my opinion after having loaded the module, a script has to check if the last status was on or off! this opinion is also valid at a normal boot [https://launchpad.net/malone/bugs/37010 #37010] )

• Resume from Sleep in Dapper results in 2 errors: a hang at the end of runlevel 6 (reboot) with a debug message: [numbers.numbers] Rebooting System. (this might help: note that the laptop has no lapic support) [https://launchpad.net/malone/29695 #29695] and no ipw2200 enabled [https://launchpad.net/malone/bugs/36403 #36403]

  • Does this still occur with the BIOS update? -PaulSladen

  • RE: again, latest bios used

• Lid close in Dapper: only after waiting 10 seconds with the lid closed I get it locked

  • This means that a quick close/open doesn't lock the session, but if you put it down long enough for somebody else to get ahold of it, it'll be locked. -PaulSladen

  • yes, I know. I left this info to let the people know of this new behaviour!

• Networking not always enabled at startup in Dapper using dhcp: just execute sudo dhclient [https://launchpad.net/malone/bugs/36918 #36918]

  • Please file a bug against ifupdown. -PaulSladen

  • RE: done

  • Never had this issue. - VincentUntz

    • RE: well, I have this bug singe flight 1 and I can reproduce it at least 4-5 times a week (just try to reboot, reboot, reboot and sometimes unplug the cable and replug it after power on)! Anyway I didn't try to install flight 5 from the CD , I just download updates using apt... Could it this the problem? I don't think so...

• dhclient keeps sleeping for at least 5 minutes although a network cable is inserted in Dapper: if for a case dhclient don't find any dhcp offers it goes sleeping, but whenever a network cable is inserted it should be woken up!!! run sudo dhclient to refresh its state and obtain an address or wait 5 minutes. This issue might be related to the above one! [https://launchpad.net/malone/bugs/36918 #36918]

  • Probably the same issue -PaulSladen

• gnome-power-manager puts the display to sleep in Dapper if %m minutes (the number you set) are passed since the screensaver startup: so you have to add the screensaver time to the one specified in gnome-power-manager [https://launchpad.net/malone/36568 #36568]

• Multimedia hotkeys (except volume ones) are not handled in Dapper for now: go to Systm->Preferences->Keyboard Shortcuts and set them! [https://launchpad.net/malone/bugs/37225 #37225]

• Power4gear hotkey not handled in Dapper, anyway its functionality is not to lock the screen but to switch between some predefined power profiles (powersave, dynamic, performance...) [https://launchpad.net/malone/35791 #35791]

  • Please file a bug against hotkey-setup with the showkey -u (or ACPI) and dmidecode information from LaptopTestingTeam/HotkeyResearch -PaulSladen

  • already done and assigned to you, but now the discussion is stalled! I filed against acpi-support... should we change it to hotkey-setup?

• Don't press Fn+F8 in Dapper because it freezes the system at all [https://launchpad.net/malone/36885 #36885]

  • This is a major bug. What is this key supposed to do? Does it switch to external VGA and if so, does pressing it again once, or twice, bring the display back. Does the caps-lock key still work when it has frozen?. -PaulSladen

  • well... the key is supposed to switch between LCD/external monitor. I've tried to press it (once, twice, etc.) only without a monitor connected and the enteir system hangs (including the image on the monitor) so no caps lock :). I'll try with a monitor soon

Hardware details

• ATKD 00000041 (/etc/acpi/events/asus-media-next) runs /etc/acpi/nextbtn.sh which sends KEY_NEXTSONG (163), I guess it's a question of fixing totem and rhythmbox to listen for that key when they are active. Lock should send KEY_COFFEE which should be hooked by gnome-something-or-other. Both of these might temporaryily be broken because of [http://launchpad.net/bugs/32267 #32267] -PaulSladen

Notes

THESE NOTES ARE NOT FOR DAPPER!

• fglrx: To get it work do a sudo apt-get install xorg-driver-fglrx fglrx-control linux-686BR then edit /etc/X11/xorg.conf and replace Driver "ati" (might be radeon) with Driver "fglrx" BR add fglrx to the list of automated inserted modules /etc/modules BR now reboot! and test with sudo fglrxinfo (make sure your card appears in the output) BR if something goes wrong (typically xorg won't start) just replace fglrx with radeon in /etc/X11/xorg.conf to go back to normal config

• touchpad: I found the touchpad too much sensitive and unusable, especially when you move the finger and he thinks it's a tap! and then acceleration should be decreased... see my [http://xoomer.virgilio.it/yelo3/ubuntu/etc/X11/xorg.conf xorg.conf]BR

• Wireless: Wireless is on by default but the led is off! Please do one of the following thingsBRIf you have ipw2100 please replace ipw2200 with it!!!BR1. If you want led and wireless off by default create /etc/modprobe.d/ipw2200 with this content:BR install ipw2200 modprobe --ignore-install ipw2200 && /etc/acpi/wireless.shBR2. If you want led and wireless on by default create /etc/modprobe.d/ipw2200 with this content:BR install ipw2200 modprobe --ignore-install ipw2200 && /etc/acpi/wireless.sh && /etc/acpi/asus-wireless.shBR3. If you want led following wireless LAN status (LED on when wireless interface is up, LED off when wireless interface is down) (note: this does NOT mean "when wireless is powered ON/OFF" because if you just disable wireless interface with ifdown eth1 the radio is still on!), download [http://www.atworkonline.it/~bibe/ubuntu/wled this script] and install it withBR sudo install -m 755 wled /etc/network/if-up.d/ && sudo install -m 755 wled /etc/network/if-down.d/

  • The LED needs to be made to out of the box, the LED reflect radio activity---so should probably reflect the radio status rather than the interface status. We turn the wireless off by putting it into a power-saving mode so the radio should go off; /etc/acpi/asus-wireless.sh already handles setting the LED, but we need to set it on start up (which is the bug on your system!). Can you find a bug against linux-source-2.5.15 with only with the output from for s in system-{manufacturer,product-name} system-version ; do sudo dmidecode -s $s ; done so that this can be made an exception for your laptop model. -PaulSladen

  • RE: well, the third way wasn't put in this page by me, so I don't know if removing it is correct! Anyway I have to add a comment to what you said: first of all in ipw2200 and ipw2100 and maybe other cards there's a specific file to control the power state: /sys/class/net/eth1/device/rf_kill, then I think that it's more correct that the led have to go up not when the system starts, but only when the module loads correctly! (if the module can't load for some reason, the led must not be on!). The output of the command you gave me is

    ASUSTeK Computer Inc. BRM6Ne BR1.0

• DMA on CD/DVD drive: If you enable DMA you'll get fewer errors in writing CDs/DVDs and faster access!BREdit /etc/hdparm.conf and add at the bottom these linesBR/dev/cdrom {BRdma = onBR }

• Multiple Sound Streams: run gstreamer-properties and select as default sink out: ALSA

CategoryLaptop CategoryLaptop