I'm running Gentoo with a 4.19.1 kernel on a macbook 3.1. If you want me
to revert that git, do bissects, etc, please just ask, I won't be able
to run debian/ubuntu kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Running kernel 3.6.2 here on Z77-UD5H as well, same problem. Jack sense
works but no output to front headphone socket (didn't test rear). I'll
give a try to hda-jack-retask workaround. Thanks all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Actually, last I read this datasheet, it said that we could obtain the
programming guide from our local NS vendor. I think that's what we are
missing to have a functional driver (like information about timings or
order to set registers to get the desired effect).
I managed to have a working X but
FTR, I confirm the problem appears to be fixed with linux 3.4 on my system.
Big thanks to whoever made this happen :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/760842
Title:
Natty Narwhal/Sandy
For the record, I'm still working on this from time to time.
I ported the patch to kernel land quite easily, but still can't figure out what
is the problem with register read failures.
Example from a 3.3.1 kernel booted with i915.modeset=1 drm.debug=0x04:
Apr 15 17:52:11 mobilix kernel:
Ok, I installed i2c-tools and here is what it sees:
# i2cdetect -l
i2c-0 i2c i915 gmbus disabled I2C adapter
i2c-1 i2c i915 gmbus ssc I2C adapter
i2c-2 i2c i915 GPIOB I2C adapter
Ok, forget that, I rebooted without kms disabled and now I get 28
i2c/smbus devices (most likely duplicates). Now scanning:
i2c-9 i2c i915 gmbus dpb I2C adapter
i2c-10 i2c i915 GPIOE I2C adapter
gives:
# i2cdetect
I pushed the current state of the code here:
https://github.com/EvaSDK/linux/commit/d590f8631a2421ba6bcef7041888b3aa382f87c7
I commented out dpms code for testing, but given the power of the
machine it was quite long to get that out already so I'll fix that
later.
--
You received this bug
I gave up on this for now. I'll try to switch to EFI booting in the next
months and see if it fixes anything but for traditional bios based boot,
looks like there is to do but to wait for asus to fix their mess or some
kernel dev to implement a workaround.
--
You received this bug notification
I tried applying the patch and building a kernel with them, but I got no
positive results. Running kernel 3.1 now and still having the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/760842
I'm not using ubuntu here, but since this is a BIOS problem I guess I'd
share my experience as well.
I own an Asus P8H67M-Pro with a i3-2100 running with no extra cards and using
integrated video.
The system is running a gentoo-sources 3.0.4 kernel.
The motherboard had BIOS revision 0806 and
This modification indeed makes mpb_backlight module available in
/sys/class/backlight, modifying brightness works as promised. This is on
macbook 3.1.
--
[i915][kms] kernel backlight interface missing for macbooks
https://bugs.launchpad.net/bugs/511965
You received this bug notification because
This problem is due to unsupported i830 variant since the rewrite of the
v2 of the intel driver. I am myself having such laptop (fujitsu-siemens
stylistic ST4000 series) and using gentoo. I have been trying to get the
attention and help of intel developers but since they couldn't get their
hands
hum forgot to say that the bug either results in a black screen or white
stripes getting brighter and brigther and kernel mode setting obviously
won't work for this hardware as well with the same symptoms. The only
way to get a working X on this hardware for me is to plug a screen on
the VGA
14 matches
Mail list logo
