As I wrote earlier, the EDID file I used came from edid-generator github
and it is called 1920x1080.bin . You want me to google that for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821533
I'm not sure this is a Linux problem. It may be that the panel is
reporting bad EDID data. I haven't investigated enough to say for sure.
In any case none of the more recent Linux releases fixed the problem in
my tests. Also no other open source OSs were able to deal with the
onboard LCD panel
I was able to display on an external monitor, or the internal monitor,
but not both simultaneously. I didn't spend too much time trying to
solve the problem and now the laptop is with a family member at another
location. If you work on this issue and find a solution please post it
here.
--
You
** Summary changed:
- failure to detect and use Intel 620 graphics pci id 3ea0
+ drm fails to accept edid version 2.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821533
Title:
drm fails to
I was able to get the onboard LCD panel working, finally, as follows:
First I extracted the edid file from the LCD panel using get-edid and
putting that in /lib/firmware/edid/ncp.bin, and then forcing the kernel
to take that using the kernel boot option
drm.edid_firmware=edid/ncp.bin. This
Below is the EDID information from the onboard panel. Why can't drm/i915
deal with it?
guest@guest-ZenBook-UX431FA:~$ sudo get-edid | parse-edid
This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 0
No EDID on bus 1
No EDID on bus 2
No EDID
Correction: last message should read "Why is the driver/module expecting
EDID major version *1* and getting *2*?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821533
Title:
failure to detect and
I think the problem is that the laptop's onboard LCD panel is reporting
EDID data with version 2 and the i915 driver can only deal with version
1 at the moment. How can this be fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Progress! Based on information in dmesg, pasted in at the end of this
message, I thought maybe the graphics device was found OK but the laptop
was trying to drive an external monitor instead of the onboard display.
Sure enough, when I boot without nomodeset option and with an external
HDMI monitor
Is it known whether any machines with Intel Graphics 620 with pci id
0x3ea0 have functioning graphics with any version of Ubuntu?
This is relatively new hardware, but it seems unlikely that I am the
only one in the world who has tried this combination, and if other
people with different machines
I tried booting 4.18.0-16-generic (which i believe is the hwe kernel)
with kernel option drm.debug=0xff. When the system came up of course it
had no video but I could ssh in and grab the dmesg output, which is
attached to this message. dmesg had many drm-related debugging messages
and i915-related
Just in case my addition of i915 to initramfs was causing a problem with
drm-intel-next, I removed i915 from initramfs and repeated the test. The
result was the same, no video after a certain point in the boot process
with nomodeset using the drm-intel-next kernel as in #8.
--
You received this
I installed kernel and modules and headers from
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/
and rebooted without nomodeset option. Same behavior: after the "loading
initramfs" message the screen blanks and never comes back.
--
You received this bug notification because
Based on a lead from an Arch Linux blog post, I tried adding the i915
module to the initramfs. This could possibly lead to earlier
initialization of the graphics device and it also seems consistent with
the DragonFlyBSD "probe early" patch I linked to in my initial bug
report which may have fixed
Also: booting without nomodeset kernel option for v5.1-rc2 kernel leads
to black screen, just as before. At that point the system cannot even be
switched to text console with ctrl-alt-Fn.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks for your help.
Unfortunately, no change after installing v5.1-rc2: Still stuck in
800x600 after booting with nomodeset kernel option.
Added kernel-bug-exists-upstream and marked confirmed.
dmesg output attached.
** Attachment added: "dmesg"
** Description changed:
Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
install (also 18.10, also 19.04 daily) leads to black screen. Adding
"nomodeset" to kernel boot parameter gives 800x600 video only and
permits installing OS to disk. Applying updates and
Public bug reported:
Booting very new laptop hardware (ASUS Zenbook UX431FA) from 18.04 usb
install (also 18.10, also 19.04 daily) leads to black screen. Adding
"nomodeset" to kernel boot parameter gives 800x600 video only and
permits installing OS to disk. Applying updates and hardware
Public bug reported:
While tracking down a problem related to upstart, I decided to check the
syntax of all my upstart init files. I wrote this simple script:
for a in /etc/init/*; do init-checkconf $a; done 21 | grep invalid
This script said that a number of files had syntax errors. When the
For example, here are two consecutive runs of the script showing
different results:
root@ladastra:/etc/init# for a in /etc/init/*; do init-checkconf $a; done 21
| grep invalid
ERROR: File /etc/init/alsa-state.conf: syntax invalid:
ERROR: File /etc/init/alsa-store.conf: syntax invalid:
ERROR:
Actually, it seems there isn't anything in particular about being in a
script that causes init-checkconf to return random results. If I repeat
the same command a number of times the results vary:
root@ladastra:/oldroot/home/drewes# init-checkconf /etc/init/tty5.conf
File
Mainline kernel 3.11.0-031100rc3-generic fixes the suspend/resume
problem for me. (Other late releases may also fix 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/1088721
Title:
The kernel built according to comment #33 does introduce a
suspend/resume problem, but a different one: the suspend/resume does
not succeed even once. The system appears to suspend but when resumed
it actually just boots.
According to the commit log, this suspend failure was noted and an
The kernel built using the commands in #31 does not show the problem. I
am able to suspend and resume multiple times with it. That is kernel
3.3.0-rc5-custom+ however, so I'm not sure it is testing what we want.
Remember that I reverted to 12.04.1 and I had been testing 12.10 kernels
on a
I am happy to do this bisection however I want to make sure we are not
duplicating efforts with this bug report:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1094800
Do you think it is worthwhile doing another bisection or should we wait
for their results?
--
You received this bug
It looks like the people in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1094800 have just
identified the specific patches that broke the suspend. From the text
descriptions of those patches, which specifically address suspend to RAM
issues, it seems to me highly likely that the problem
Some additional help would be good. Here is what I've done so far:
I followed the instructions on BuildYourOwnKernel and got the git
repository for the Quetzal kernel (3.5.0-22-generic), built it,
installed the .debs, booted into it, and verified the problem still
occurs (as expected).
What I
Tested 3.8-rc4-raring (again, within 12.04.1 base system). No fix,
problem still exists as before.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088721
Title:
[Toshiba Portege Z935-P390] Fn key
Tested v3.8-rc3-raring (on my 12.04.1 installation). Problem still
occurs, just as before.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088721
Title:
[Toshiba Portege Z935-P390] Fn key and
Short answer:
I have tested and the problem of suspend-resume working only once still
exists in 3.8-rc1-raring for me on my Toshiba Portege Z935-P390.
Long answer:
I attempted to test 3.8-rc1-raring on a persistent USB key installation
of 12.10 since I now have 12.04.1 installed on my hard disk
Public bug reported:
The usb-creator-gtk package creates a persistence file on the USB drive
when requested, and the copy-on-write filesystem is mounted on boot,
however the boot loader does not supply the persistent kernel boot
option therefore no data that is changed during the boot session
To clarify, editing the kernel boot option at each boot of the USB
installation and adding the persistent option to the end of the option
list, makes the changed data persist across boot sessions as it should.
Rich
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Tags added: apport-collected precise running-unity
** Description changed:
The usb-creator-gtk package creates a persistence file on the USB drive
when requested, and the copy-on-write filesystem is mounted on boot,
however the boot loader does not supply the
apport information
** Attachment added: AlsaDevices.txt
https://bugs.launchpad.net/bugs/1097041/+attachment/3476442/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097041
apport information
** Attachment added: AplayDevices.txt
https://bugs.launchpad.net/bugs/1097041/+attachment/3476443/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097041
apport information
** Attachment added: ArecordDevices.txt
https://bugs.launchpad.net/bugs/1097041/+attachment/3476444/+files/ArecordDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1097041/+attachment/3476445/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097041
apport information
** Attachment added: Card0.Amixer.values.txt
https://bugs.launchpad.net/bugs/1097041/+attachment/3476446/+files/Card0.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Card0.Codecs.codec.2.txt
https://bugs.launchpad.net/bugs/1097041/+attachment/3476447/+files/Card0.Codecs.codec.2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1097041/+attachment/3476448/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097041
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1097041/+attachment/3476449/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097041
Title:
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1097041/+attachment/3476450/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097041
Title:
apport information
** Attachment added: PciMultimedia.txt
https://bugs.launchpad.net/bugs/1097041/+attachment/3476451/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1097041/+attachment/3476452/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097041
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1097041/+attachment/3476453/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1097041/+attachment/3476454/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097041
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1097041/+attachment/3476455/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097041
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1097041/+attachment/3476456/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097041
Title:
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1097041/+attachment/3476457/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097041
Title:
apport information
** Attachment added: UserAsoundrcAsoundconf.txt
https://bugs.launchpad.net/bugs/1097041/+attachment/3476458/+files/UserAsoundrcAsoundconf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1097041/+attachment/3476459/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097041
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097041
Title:
persistent USB installs are not really persistent (missing kernel
The problem also exists in 3.8-rc2-raring (when installed on my 12.04.1
system). First suspend-resume is successful, second attempt fails.
Rich
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088721
One more thing:
I tried again to install 12.04.1 in EFI mode, since 12.04.1 does does
not have the suspend/resume problem that 12.10 does, and it created an
unbootable system as before. But this time I was able to make the
system bootable through the use of the amazing boot-repair tool
Some more information that may be helpful:
* The 64 bit version of 12.04.1 does actually have some preliminary
support for EFI, enough to boot from a USB stick. When I do boot this I
can suspend and resume many times without trouble. Recall that the 32
bit version of 12.04.1 has no support for
Thank you for your help.
I installed:
linux-headers-3.7.0-030700-generic_3.7.0-030700.201212102335_amd64.deb
linux-headers-3.7.0-030700_3.7.0-030700.201212102335_all.deb
linux-image-3.7.0-030700-generic_3.7.0-030700.201212102335_amd64.deb
Thanks for your help.
* I am running the mainline kernel 3.7.0-030700 (another one,
3.7-rc8-raring was suggested but that comment was apparently deleted, so
I stayed with 3.7.0-030700.
* Model is Toshiba Portege Z935-P390
* BIOS is latest available from Toshiba website
* /sys/power/pm_trace is
Here is the 2nd dmesg from the traced suspend attempt.
** Attachment added: dmesg2.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088721/+attachment/3457609/+files/dmesg2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Here is the 3rd dmesg from traced suspend attempt.
** Attachment added: dmesg3.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088721/+attachment/3457610/+files/dmesg3.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have this problem with 12.10 Quantal 64 bit installed on my new
Toshiba Portege Z935-P390 via EFI boot: After resuming from the first
suspend after clean boot, the mute Fn key (Fn-esc) no longer works and
neither do the screen brightness Fn keys nor the WIFI on/off Fn key nor
the suspend to RAM
penalvch, I thought it best to add information to this existing bug
report since my bug was very much like this one. Apologies if that was
not the right way to do it. I will resubmit with ubuntu-bug as you
suggest.
Thanks,
Rich
--
You received this bug notification because you are a member of
Public bug reported:
After resuming from the first suspend after clean boot, the mute Fn key
(Fn-esc) no longer works and neither do the screen brightness Fn keys
nor the WIFI on/off Fn key nor the suspend to RAM Fn key (I usually
suspend via the menu anyway). However, the volume up/down Fn keys
I ran into this problem while upgrading 8.04 to 10.04 for a system
running Domain Technologie Control (DTC) web admin panel. I fixed it by
getting the source package for courier-maildrop, editing the
configure.in in the maildrop directory as follows:
dnl if test $COURIERAUTHCONFIG !=
dnl then
I have a similar problem on my system with a Gigabyte GA-P55-UD4P
motherboard running 64 bit Ubuntu 9.04: periodically (every few hours)
all open gnome-terminal windows will freeze for a few minutes (usually
1-10 minutes) then unfreeze and return to normal. I haven't been able
to link the
Actually, it does happen in at least Firefox as well. Not as much as in
gnome-terminal though. When things unfreeze, all frozen apps seem to
unfreeze around the same time (at least both apps in my case).
--
Annoying freeze of some apps (gnome-terminal, xchat, audacious..)
65 matches
Mail list logo
