I've heard reports of this too.
While I haven't had a chance to verify it myself, a user on IRC reported
that this used to work with Windows 7 build 7100, but now fails with
build 7600.
He was testing originally on jaunty on a netbook LiveUSB. An in-line
upgrade to karmic's ubiquity (1.99.28), nt
On 28/04/09 01:57 PM, jdeslip wrote:
> WPA still is a problem on my eee 901 with the final release of jaunty.
> Adam - will it be fixed in your kernel?
Yes, the rt2860 driver is upgraded to v1.8.1.1 in my netbook kernels,
WPA/WPA2 encryption is working for me on my 901. The kernel is available
tod
Troy... FWIW I've ported rt2860sta v1.7.1.1 to the v1.8 branch in the
upstream kernel staging driver.
I've supplied a patch to Greg KH, labelling this upgrade as v1.8.1.1.
This version works for me on my 901 with WPA, WPA2 and WEP encryption.
The patch itself is only available via the linux-next.
Interesting. Note the staging directory though. I think that this is a
preliminary step before full support is available.
I'm curious to see how the linux kernel will merge the rtl8187se's
ieee80211 stack with the existing kernel's stack.
I attempted such a merge once, but found that the rtl8187s
*** This bug is a duplicate of bug 301855 ***
https://bugs.launchpad.net/bugs/301855
Well, without the vbox-install.log, I can only assume that "Most
probably the kernel sources were not found" is your problem, in which
case, you need to install the headers. See bug #301855
** This bug has be
> options pciehp pciehp_force=1 pciehp_slot_with_bus=1
pciehp_slot_with_bus?? .. that is new to me, and not a standard pciehp
module parameter. (at least its not in 2.6.27.y.git or linux-tip.git)
Where/how did "pciehp_slot_with_bus" get added?
I have heard from EeePC >= 901 owners though that "p
Something funky's going on at ralink. They're obviously not following standard
release conventions.
If you crack open the code you'll find badly aligned spacing, spontaneous
switching between LF & CRLF, and poorly defined naming conventions.. even goto
statements Very sloppy, IMO.
Glad to hea
Got it:
http://www.array.org/ubuntu/dists/intrepid/eeepc/binary-i386/rt2860-dkms_1.7.1.1_all.deb
Note, this version does have the full EEEPC_SPECIAL_SETTING patch, as
described earlier. As well as the earlier patches to enable building on
2.6.24 and 2.6.27, so it should also work on hardy.
You m
I've posted the diff and diffstat of the major changes between v1.7.0.0,
v1.7.1.1 and v1.8.0.0 at
http://www.array.org/~adamm/rt2860/
--
Please include RaLink RT2860 driver
https://bugs.launchpad.net/bugs/210725
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Some very interesting developments over on eeeuser.com forums.
One of the users contacted ralink about the crappy encryption methods,
Ralink sent them v1.7.1.1 "specifically designed for the eeepc". The
most interesting changes here include major updates to
include/firmware.h
http://forum.eeeuse
I just got the rtl8187se wireless driver on the EeePC 701SD to work (bug
246141), pulling out good large chunks of hair in the process... I'd
like to get this new driver rt2860sta working in intrepid, too.
I've got some time to dedicate to this dkms module tonight;...
--
Please include RaLink RT
I'm working on building one with a colleague, actually.
Unfortunately my wife escalated the "Paint the fence" project this weekend.
I'll post something here when it's ready (and if it rains:)
--
Please include RaLink RT2860 driver
https://bugs.launchpad.net/bugs/210725
You received this bug noti
I'm reading through a diff of v1.7.0.0 and v1.8.0.0. They do not include
the "EEEPC_SPECIAL_SETTING" patch (which was originally released by
ralink) and linked earlier in this thread.
There may be a regression issue here.
Can someone who has installed v1.8.0.0 test both WPA and WEP encryption?
-
After applying the alsa_eeepc901_fix.diff patch, there are some specific
alsamixer settings that need to be set on those new channels, otherwise
the new channels wont actually record. (Note, most users cite Skype as
their software use-case, Skype just seems to do the "right thing" when
presented wi
BTW, I've added bluetooth control (a very minor change) to eeepc-
laptop.ko, based upon more recent (and deprecated) eeepc-acpi.ko code to
my local clone of ubuntu-intrepid.git:
commit e3c8316f0a41fdea91ee1e087578119000f24a9f
Author: Adam McDaniel <>
Date: Mon Sep 22 16:53:06
I've upgraded my 900 to Intrepid alpha5 and the sound card continues
works correctly with the "power_save=10" option.
Shutdown works correctly as well.
--
snd_hda_intel fails to unload (or unload correctly) on shut down; laptop fails
to halt
https://bugs.launchpad.net/bugs/126140
You received t
Any idea when/if Matthew Garrett's patch (re: Redhat bug 451182) will
make it in Intrepid's base kernel?
I'm in the midst of compiling it for my 900 now. I'll post a summary
with the results.
--
EeePC Volume and Wireless Hotkeys Do Not Function Out-Of-The-Box with Ubuntu
(8.04 Hardy LTS, Intrep
FWIW, Ubuntu-2.6.27-2.3 was tagged on 2008-08-28, 12 days after Daniel
Miles reported that Intrepid lacked 901 internal microphone support.
If he were to upgrade to the 2.6.27-3-generic kernel (latest version as
of today,) support should be available for his eeepc 901.
--
EeePC internal micropho
I just posted a patch to Daniel Miles' bug report that fixes the EeePC
1000's internal microphone.
>From my experience, as of tag "Ubuntu-2.6.27-2.3" in ubuntu-
intrepid.git, support exists for the 901 and earlier.
Support for the EeePC 1000's internal microphone (and headphone jack)
will be prov
Earlier, Intrepid used Alsa v1.0.16. Now, Intrepid uses Alsa v1.0.17.
Intrepid's alsa-kernel code does have support for the EeePC 901, However
support for the 1000 is not yet included.
According to git://git.alsa-project.org/alsa-kmirror.git this is provided by
commit:
231d8534cf252135646b47e45
This entire ticket might no longer be necessary.
According to the alsa-kmirror git repository, The release tagged
"v1.0.18rc3" contains the fix for the 901 and 1000
--
Please support EEEPC 901 Variant of the ALC269 snd_hda_intel
https://bugs.launchpad.net/bugs/259878
You received this bug notifi
Confirming what bedfojo results on my EeePC 900.
Also, another oddity experienced in Hardy still exists in Intrepid
related to ACPI hotkeys: Plugging in the AC adapter still triggers an
ACPI event similar to an 'E-Mail' hotkey; Evolution launches.
--
EeePC Volume and Wireless Hotkeys Do Not Fu
Really? ... I've noticed better reception with ath5k.
(5' from my AP I got ~80% from ath_pci, but 100% from ath5k)
--
Atheros wireless (AR5007) not working on various laptops, including the ASUS
Eee PC
https://bugs.launchpad.net/bugs/182489
You received this bug notification because you are a me
@captive
I believe you have to blacklist ath_pci first, then reboot.
Both ath_pci and ath5k are being auto-loaded on bootup because both
modules are matching the AR5007 vendor/device IDs.
--
Atheros wireless (AR5007) not working on various laptops, including the ASUS
Eee PC
https://bugs.launch
I've just found something odd...
After setting the power_save parameter to "10", there is no output from
the soundcard after 10 idle seconds.
I actually have to run "sudo alsa force-reload" before I get any sound
again. (Ofcourse, the process repeats itself because I have "options
snd_hda_intel p
Confirmed, Sitsofe ;)
I upgraded to 0802 and I can now reach C3 state with ease, regardless of
snd_hda_intel's status.
Also, the device powers off cleanly after setting
"/sys/module/snd_hda_intel/parameters/power_save" to "10" Neat!
Rather than running sysctl on bootup each time to set these par
Good carch. My 900 is running BIOS 0601.
I wonder if there's a difference in the sound card model too?
Attached is my "sudo lspci -v -nn". Note the system/vendor ID for the Audio
card: [8086:2668]
** Attachment added: ""lspci -v -nn" for EeePC 900"
http://launchpadlibrarian.net/17518344/lsp
@Sitsofe ... I just double checked. My 900 never reaches C3 with these
power settings after playing sound. Are you running Intrepid? .. I
cannot remember, has Intrepid upgraded to alsa 1.0.17?
If so, I know that snd_hda_intel's patch_realtek.c code has changed in
this version. The EeePC's 901/10
Tested on EeePC 900 (Realtek ALC62 rev1) using Hardy (Alsa 1.0.16) with
the powersaving technique quoted by Sitsofe.
This is still a problem. The device will not shutdown if snd_hda_intel
is still loaded.
Interesting side note #1: A known issue with snd_hda_intel is that the
CPU never reaches C3
That doesn't sound very golden. This is pretty important.
I'll have a word with Jon.
--
"apt-get update" failure: hash sum mismatch
https://bugs.launchpad.net/bugs/261022
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
There is a known issue where rt2860 does not support both WEP and WPA in
a single compiled module. (There is a config option to enable one or the
other, but not both, for some dumb reason.)
Asus has released a patch to one blogger who complained about this, but
AFAIK it's not on any Xandros reposi
Does the fix described here still work with RC2?
--
"apt-get update" failure: hash sum mismatch
https://bugs.launchpad.net/bugs/261022
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
An "apt-get update" is not sufficient to solve this problem. There is a
corruption in the cached package details delivered by the Live CD.
This problem can be resolved by deleting all files from the following
directories:
/var/lib/apt/lists
/var/lib/apt/lists/partial
(remember to keep the 'par
The "Capture" channel may not be properly set.
Have a look at this post:
http://forum.eeeuser.com/viewtopic.php?pid=347484#p347484
(BTW, since you're running 2.6.24-21-eeepc, check which version of
linux-ubuntu-modules-2.6.24-21-eeepc is installed. The latest is
2.6.24-21.30eeepc3, and its snd_hd
Once you've compiled your patched alsa modules, you only need to replace
snd_hda_intel.ko
You can probably get away with replacing the version under
/lib/modules/$(uname -r)/ubuntu/sound/alsa-driver/pci/hda/snd_hda_intel.ko with
the new version.
Once applied, you can probably get away with 'su
>From what I've found, the EeePC 901/1000/1000h devices also have a
similar problem with the internal microphone.
As of Alsa 1.0.17, the 900's internal mic has been fixed but the
901/1000/1000h's internal mic is still a problem.
These later devices were fixed in alsa-kmirror.git: commit
df5d0800
Yes, that 40-wire UDMA patch is already committed to ubuntu-intrepid.git
--
Wrong UDMA mode due to error in 40/80 wire cable detection
https://bugs.launchpad.net/bugs/195221
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This problem appears fixed in Alsa 1.0.17
--
snd_hda_intel fails to unload (or unload correctly) on shut down; laptop fails
to halt
https://bugs.launchpad.net/bugs/126140
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
The actual patch that fixes the microphone on eee 900 can be found here:
http://forum.eeeuser.com/viewtopic.php?pid=298419#p298419
This, as far as eeeuser.com user quickfire was able to determine, was
the only piece that was unique to the xandros snd_hda_intel driver that
was missing from ubuntu's
oops. 0.59.4 :P
--
Package 0.59.2 broken
https://bugs.launchpad.net/bugs/132941
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubu
Confirmed. 0.54.4 fixes the problem.
Thanks :)
--
Package 0.59.2 broken
https://bugs.launchpad.net/bugs/132941
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists
I just downloaded the deb source for update-notifier-0.59.3. Both
./debian/update-notifier.install and ./debian/update-notifier-
common.install still reference the file /usr/share/update-notifier
/notify-reboot-required
--
Package 0.59.2 broken
https://bugs.launchpad.net/bugs/132941
You received
The problem was originally discovered in Feisty (2.6.20), but Gutsy
(2.6.22) is also affected.
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
bcm203x firmware will not load
https://bugs.launchpad.net/bugs/85247
You received this bug notification beca
I just upgraded to gutsy (tribe4) running 2.6.22 and found that the
problem still exists. The only thing different that I noticed is the
dmesg failure error code
[19681.456000] bcm203x_complete: URB failed with status -108
I assume that my original patch still works (about to try the patch
now),
Success! .. I backported drivers/bluetooth/bcm203x.c from 2.6.20 to
2.6.18 and recompiled the module within the 2.6.20 source. My BT-120
device is back online in fiesty!
I'll attach a diff here of what I did, it's very straight forward.
I still need to test to see if 2.6.21-rc2 or later already a
I've had this same problem for a couple weeks now. After a little
digging I believe that the likely culprit was introduced in 2.6.19. From
that kernel's changelog:
> commit 3f5306927d800306ebba542438cfdf1a1c418376
> Author: Marcel Holtmann
> Date: Sun Oct 15 17:31:19 2006 +0200
>
>[Bluetooth
46 matches
Mail list logo
