Page 6 of 15 FirstFirst ... 45678 ... LastLast
Results 51 to 60 of 147

Thread: How To: ubuntu natty (11.04) on asus a53s (k53sv family)

  1. #51
    Join Date
    Oct 2010
    Beans
    35

    Re: How To: ubuntu natty (11.04) on asus a53s (k53sv family)

    try to run a memtest from grub menu. mine is "frozen" meaning that after i hit enter in grub menu of memtest86, it loads the blue&white screen, and nothing happens, any key wont work, i have to power off from the power button. i still think it might me related to the memory, give it a try see if it works or not.

  2. #52
    Join Date
    Jun 2011
    Beans
    4

    Cool Laggy Keyboard & Can't not enable desktop effect

    Anyone experienced the laggy keyboard? I usually get trouble with it. For example, when browsing Opera, the keys doesn't react my pressing, I have to click on the Search textbox and then can press key normally. This also happens with Netbeans. I keep typing and nothing appear. Don't know this is the popular problem of Ubuntu or only for these series of Asus laptop (SAndybridge). My laptop is K53SV.
    Another question, I'm using Bumblebee, but still don't know how to enable desktop effects. It seems that my onboard graphic card isn't recognized ?

  3. #53
    Join Date
    Jun 2006
    Location
    Vienna, Austria
    Beans
    87
    Distro
    Ubuntu

    Re: Laggy Keyboard & Can't not enable desktop effect

    qmater: memtest v4.1 seems to have troubles with intel sandybrdige, see http://forum.canardpc.com/threads/53....20-Released-!

    silentbang: for qmater and me, there is also heavy lagging but not that easy reproducable for the moment...
    i guessed it was the harddisk, which has some issues but is not the only reason. yesterday i discovered it seems to be related to wlan drivers...

    i start copying things over wlan with full speed for some hours and i feel it starts lagging.. do you also experience that?


    can anyone of you - when lagging starts and doesnt go away - do:
    Code:
    sudo rmmod ath9k
    to see if it stops?

    there have been issues with ath9k in the past.. i just want to rule that out.
    i guess everyone must/will use wlan on his laptop.. but a few days ago i was NOT using wlan cause there was none available to me and i didnt experience any lags or stability issues for exact THESE 3 days on LAN... i just want to try everything now

    i don't have the possibility to use a LAN connection for the next days
    Last edited by cucisan; July 9th, 2011 at 10:26 AM. Reason: memtest 4.2 final link added

  4. #54
    Join Date
    Jun 2006
    Location
    Vienna, Austria
    Beans
    87
    Distro
    Ubuntu

    Re: How To: ubuntu natty (11.04) on asus a53s (k53sv family)

    @silentbang: did it work before installing bumblebee ? have you updated nvidia driver recently? if nvidia driver gets updated AFTER installing bumblebee, unity will stop to work (know problem -> see post #48

  5. #55
    Join Date
    Apr 2011
    Location
    Netherlands
    Beans
    22
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: How To: ubuntu natty (11.04) on asus a53s (k53sv family)

    cucisan, thank you very much! I managed to get fn keys, bumblebee and touchpad features working properly. I have an Asus K53SV (K53SV-SX146V). Bumblebee recently added an ppa ( https://launchpad.net/~mj-casalogic/+archive/bumblebee/ ), which worked perfectly for me. I am not experiencing wlan/instability issues, so i think i'm pretty much all set Again, thank you very much!

  6. #56
    Join Date
    Jun 2011
    Beans
    4

    Re: How To: ubuntu natty (11.04) on asus a53s (k53sv family)

    Quote Originally Posted by cucisan View Post
    @silentbang: did it work before installing bumblebee ? have you updated nvidia driver recently? if nvidia driver gets updated AFTER installing bumblebee, unity will stop to work (know problem -> see post #48
    I experienced unable to use unity since the very first time installing Ubuntu. Everytime trying to click on Extra or NOrmal effect, it searched for Additional Driver and ended up "Desktop effects could not be enabled ". After installing Bumblebee, nvidia_current "is activated but not currently in used", which is normal as other's situation.

  7. #57
    Join Date
    Jun 2006
    Location
    Vienna, Austria
    Beans
    87
    Distro
    Ubuntu

    Re: How To: ubuntu natty (11.04) on asus a53s (k53sv family)

    everyone with WLAN issues of any kind PLEASE post your hardware, as there seem to be different wlan adapters (bluetooth, no bluetooth etc)

    Code:
    ~$ lspci | grep Network
    03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
    
    ~$ lspci -s 03:00.0 -vvnn
    03:00.0 Network controller [0280]: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01)
    	Subsystem: AzureWave Device [1a3b:1089]
    	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    	Latency: 0, Cache Line Size: 64 bytes
    	Interrupt: pin A routed to IRQ 17
    	Region 0: Memory at de200000 (64-bit, non-prefetchable) [size=64K]
    	Capabilities: <access denied>
    	Kernel driver in use: ath9k
    	Kernel modules: ath9k
    change the bold letters in case its different for you.


    sidenote: im currently using my umts stick, and no lags at all.... but i will not speak too soon.. need more time to observe...

  8. #58
    Join Date
    Jun 2006
    Location
    Vienna, Austria
    Beans
    87
    Distro
    Ubuntu

    Re: How To: ubuntu natty (11.04) on asus a53s (k53sv family)

    Quote Originally Posted by silentbang View Post
    I experienced unable to use unity since the very first time installing Ubuntu. Everytime trying to click on Extra or NOrmal effect, it searched for Additional Driver and ended up "Desktop effects could not be enabled ". After installing Bumblebee, nvidia_current "is activated but not currently in used", which is normal as other's situation.
    thats strange... it worked for me without bumblebee..

    please post your hardware.

    what does
    Code:
    glxgears
    do? (type in terminal)

    if it moans about DRI/GLX missing uninstall bumblebee and try again

    also do not use the gui to enable desktop effects - it will try to install nvidia driver...

    just open a terminal and type:

    Code:
    compiz --replace &
    this will start unity, there may be more error output to see there

  9. #59
    Join Date
    Jun 2006
    Location
    Vienna, Austria
    Beans
    87
    Distro
    Ubuntu

    Re: How To: ubuntu natty (11.04) on asus a53s (k53sv family)

    Quote Originally Posted by AureiAnimus View Post
    cucisan, thank you very much! I managed to get fn keys, bumblebee and touchpad features working properly. I have an Asus K53SV (K53SV-SX146V). Bumblebee recently added an ppa ( https://launchpad.net/~mj-casalogic/+archive/bumblebee/ ), which worked perfectly for me. I am not experiencing wlan/instability issues, so i think i'm pretty much all set Again, thank you very much!
    im glad at least some ppl have no stability issues

    the last time i checked on the bumblebee ppa there was no bumblebee package there (so no way to install without the scripts from git)

    guess i will switch soon and update the my post accordingly as soon as those stability issues are gone.

    care to share you wireless hardware? see commands above...

  10. #60
    Join Date
    Jun 2011
    Beans
    4

    Re: How To: ubuntu natty (11.04) on asus a53s (k53sv family)

    Srr. I didn't mean Unity. As I'm using Ubuntu 10.10. I meant desktop effects.
    Here is my hardware info:
    $lspci

    Code:
    00:00.0 Host bridge: Intel Corporation Sandy Bridge DRAM Controller (rev 09)
    00:01.0 PCI bridge: Intel Corporation Sandy Bridge PCI Express Root Port (rev 09)
    00:02.0 VGA compatible controller: Intel Corporation Sandy Bridge Integrated Graphics Controller (rev 09)
    00:16.0 Communication controller: Intel Corporation Cougar Point HECI Controller #1 (rev 04)
    00:1a.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #2 (rev 05)
    00:1b.0 Audio device: Intel Corporation Cougar Point High Definition Audio Controller (rev 05)
    00:1c.0 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 1 (rev b5)
    00:1c.1 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 2 (rev b5)
    00:1c.5 PCI bridge: Intel Corporation Cougar Point PCI Express Root Port 6 (rev b5)
    00:1d.0 USB Controller: Intel Corporation Cougar Point USB Enhanced Host Controller #1 (rev 05)
    00:1f.0 ISA bridge: Intel Corporation Cougar Point LPC Controller (rev 05)
    00:1f.2 IDE interface: Intel Corporation Cougar Point 4 port SATA IDE Controller (rev 05)
    00:1f.3 SMBus: Intel Corporation Cougar Point SMBus Controller (rev 05)
    00:1f.5 IDE interface: Intel Corporation Cougar Point 2 port SATA IDE Controller (rev 05)
    01:00.0 VGA compatible controller: nVidia Corporation Device 0df4 (rev ff)
    03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
    04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
    $lspci | grep Network
    Code:
    03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
    $lspci -s 03:00.0 -vvnn
    Code:
    03:00.0 Network controller [0280]: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01)
    	Subsystem: Device [1a3b:2c37]
    	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    	Latency: 0, Cache Line Size: 64 bytes
    	Interrupt: pin A routed to IRQ 17
    	Region 0: Memory at de200000 (64-bit, non-prefetchable) [size=64K]
    	Capabilities: <access denied>
    	Kernel driver in use: ath9k
    	Kernel modules: ath9k

    $glxgears
    Code:
    Mesa: Initializing x86-64 optimizations
    Running synchronized to the vertical refresh.  The framerate should be
    approximately the same as the monitor refresh rate.
    3 frames in 6.8 seconds =  0.441 FPS
    301 frames in 5.0 seconds = 60.069 FPS
    301 frames in 5.0 seconds = 60.011 FPS
    300 frames in 5.0 seconds = 59.991 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    300 frames in 5.0 seconds = 59.999 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    300 frames in 5.0 seconds = 59.999 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    300 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    300 frames in 5.0 seconds = 60.000 FPS
    300 frames in 5.0 seconds = 59.996 FPS
    301 frames in 5.0 seconds = 60.007 FPS
    301 frames in 5.0 seconds = 59.991 FPS
    301 frames in 5.0 seconds = 60.010 FPS
    301 frames in 5.0 seconds = 60.005 FPS
    300 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    301 frames in 5.0 seconds = 59.997 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.004 FPS
    300 frames in 5.0 seconds = 59.999 FPS
    300 frames in 5.0 seconds = 59.990 FPS
    301 frames in 5.0 seconds = 60.012 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    300 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.005 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    300 frames in 5.0 seconds = 59.997 FPS
    301 frames in 5.0 seconds = 60.005 FPS
    300 frames in 5.0 seconds = 59.998 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    300 frames in 5.0 seconds = 59.998 FPS
    300 frames in 5.0 seconds = 59.805 FPS
    300 frames in 5.0 seconds = 59.999 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.005 FPS
    300 frames in 5.0 seconds = 59.995 FPS
    301 frames in 5.0 seconds = 60.005 FPS
    300 frames in 5.0 seconds = 59.998 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 59.997 FPS
    301 frames in 5.0 seconds = 60.010 FPS
    301 frames in 5.0 seconds = 59.997 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.005 FPS
    300 frames in 5.0 seconds = 59.997 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    300 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.004 FPS
    300 frames in 5.0 seconds = 59.998 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.006 FPS
    300 frames in 5.0 seconds = 59.996 FPS
    300 frames in 5.0 seconds = 59.999 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    300 frames in 5.0 seconds = 59.999 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    300 frames in 5.0 seconds = 59.998 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    301 frames in 5.0 seconds = 59.999 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.005 FPS
    300 frames in 5.0 seconds = 59.995 FPS
    301 frames in 5.0 seconds = 60.006 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    300 frames in 5.0 seconds = 59.997 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.009 FPS
    300 frames in 5.0 seconds = 59.992 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 59.998 FPS
    301 frames in 5.0 seconds = 60.007 FPS
    300 frames in 5.0 seconds = 59.998 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    301 frames in 5.0 seconds = 59.999 FPS
    301 frames in 5.0 seconds = 60.005 FPS
    300 frames in 5.0 seconds = 59.996 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    301 frames in 5.0 seconds = 60.005 FPS
    301 frames in 5.0 seconds = 59.997 FPS
    301 frames in 5.0 seconds = 59.970 FPS
    301 frames in 5.0 seconds = 60.036 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    300 frames in 5.0 seconds = 60.000 FPS
    300 frames in 5.0 seconds = 59.999 FPS
    301 frames in 5.0 seconds = 60.004 FPS
    300 frames in 5.0 seconds = 59.998 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    300 frames in 5.0 seconds = 59.997 FPS
    301 frames in 5.0 seconds = 60.004 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    301 frames in 5.0 seconds = 60.005 FPS
    300 frames in 5.0 seconds = 59.996 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.004 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    300 frames in 5.0 seconds = 59.999 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.005 FPS
    300 frames in 5.0 seconds = 59.998 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.005 FPS
    301 frames in 5.0 seconds = 59.996 FPS
    301 frames in 5.0 seconds = 60.002 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    301 frames in 5.0 seconds = 59.999 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.012 FPS
    300 frames in 5.0 seconds = 59.992 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.001 FPS
    301 frames in 5.0 seconds = 60.006 FPS
    300 frames in 5.0 seconds = 59.990 FPS
    301 frames in 5.0 seconds = 60.010 FPS
    300 frames in 5.0 seconds = 59.999 FPS
    301 frames in 5.0 seconds = 60.004 FPS
    300 frames in 5.0 seconds = 59.999 FPS
    301 frames in 5.0 seconds = 60.004 FPS
    300 frames in 5.0 seconds = 59.998 FPS
    301 frames in 5.0 seconds = 60.000 FPS
    301 frames in 5.0 seconds = 60.003 FPS
    301 frames in 5.0 seconds = 60.005 FPS
    301 frames in 5.0 seconds = 60.030 FPS
    301 frames in 5.0 seconds = 60.032 FPS
    301 frames in 5.0 seconds = 59.984 FPS
    $compiz --replace
    Code:
    Blacklisted PCI ID 8086:0116 detected
    
    Launching fallback window manager
    Window manager warning: "" found in configuration database is not a valid value for keybinding "run_command_10"

Page 6 of 15 FirstFirst ... 45678 ... LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •