Public bug reported:
This new laptop has a Samsung NVME SSD. The SSD (or the SSD controller)
sometimes fails to resume from standby. The probability of this goes up
with the time the laptop is on standby & I have to save all files when I
put the laptop on standby at the end of the day as most
Public bug reported:
The wifi has now crashed 3 times in as many hours on a clean new installation
of focal.
Unlike some other bugs here, I don't have to re-start. It's enough to
re-connect using the network manager UI.
The laptop is a Lenovo T495. The wifi controller is;
01:00.0 Network
Moving around between countries in Europe (UK <-> Belgium <-> France <->
Germany <-> Switzerland <-> Austria), I get all sorts of weird results
for locales when I change the timezone from UK to anything else and back
again.
--
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: AlsaDevices.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489719/+files/AlsaDevices.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You
apport information
** Tags added: apport-collected
** Description changed:
Having upgraded from Karmic to Lucid, the iwl3945 driver no longer works on
this laptop. Under karmic, perhaps every 1-2 days the wifi system would die
with a 'Microcode SW error'. The fix was to disable wifi, 'rmmod
apport information
** Attachment added: AplayDevices.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489720/+files/AplayDevices.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
apport information
** Attachment added: BootDmesg.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489721/+files/BootDmesg.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You
apport information
** Attachment added: Card0.Codecs.codec.0.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489723/+files/Card0.Codecs.codec.0.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
apport information
** Attachment added: Card0.Amixer.values.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489722/+files/Card0.Amixer.values.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
apport information
** Attachment added: Card0.Codecs.codec.1.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489724/+files/Card0.Codecs.codec.1.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489725/+files/CurrentDmesg.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
apport information
** Attachment added: IwConfig.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489726/+files/IwConfig.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489727/+files/Lspci.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You received
apport information
** Attachment added: Lsusb.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489728/+files/Lsusb.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You received
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489731/+files/ProcInterrupts.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
apport information
** Attachment added: PciMultimedia.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489729/+files/PciMultimedia.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489730/+files/ProcCpuinfo.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You
apport information
** Attachment added: ProcModules.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489732/+files/ProcModules.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You
apport information
** Attachment added: RfKill.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489733/+files/RfKill.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You received
apport information
** Attachment added: UdevLog.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489735/+files/UdevLog.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You received
apport information
** Attachment added: UdevDb.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489734/+files/UdevDb.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You received
I just booted this laptop off the Maverick Alpha 3 CDROM and left it while I
went shopping.
Firefox was running with a page loaded which refreshed every 5 minutes or so
and nothing else.
The output of dmesg shows that this problem still occurs.
--
iwl3945: immediately after boot goes into loop
apport information
** Attachment added: WifiSyslog.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489736/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Expired = New
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
apport information
** Description changed:
Having upgraded from Karmic to Lucid, the iwl3945 driver no longer works on
this laptop. Under karmic, perhaps every 1-2 days the wifi system would die
with a 'Microcode SW error'. The fix was to disable wifi, 'rmmod iwl3945',
suspend the laptop
apport information
** Attachment added: AlsaDevices.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489799/+files/AlsaDevices.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You
apport information
** Attachment added: AplayDevices.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489800/+files/AplayDevices.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
apport information
** Attachment added: BootDmesg.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489801/+files/BootDmesg.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You
apport information
** Attachment added: Card0.Amixer.values.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489802/+files/Card0.Amixer.values.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
apport information
** Attachment added: Card0.Codecs.codec.0.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489804/+files/Card0.Codecs.codec.0.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
apport information
** Attachment added: Card0.Codecs.codec.1.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489805/+files/Card0.Codecs.codec.1.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489806/+files/CurrentDmesg.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
apport information
** Attachment added: IwConfig.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489807/+files/IwConfig.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489808/+files/Lspci.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You received
apport information
** Attachment added: Lsusb.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489809/+files/Lsusb.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You received
apport information
** Attachment added: PciMultimedia.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489810/+files/PciMultimedia.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489812/+files/ProcInterrupts.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489811/+files/ProcCpuinfo.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You
apport information
** Attachment added: UdevDb.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489815/+files/UdevDb.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You received
apport information
** Attachment added: UdevLog.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489816/+files/UdevLog.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You received
apport information
** Attachment added: ProcModules.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489813/+files/ProcModules.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You
apport information
** Attachment added: WifiSyslog.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489817/+files/WifiSyslog.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You
apport information
** Attachment added: RfKill.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489814/+files/RfKill.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You received
And here's a second example of the problem running from the Maverick Alpha 3
CDROM.
I just rebooted the machine after the previous example and left it to go and
have lunch.
When I came back, the problem had happened.
--
iwl3945: immediately after boot goes into loop of Microcode SW error
apport information
** Description changed:
Having upgraded from Karmic to Lucid, the iwl3945 driver no longer works on
this laptop. Under karmic, perhaps every 1-2 days the wifi system would die
with a 'Microcode SW error'. The fix was to disable wifi, 'rmmod iwl3945',
suspend the laptop
apport information
** Attachment added: AlsaDevices.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489835/+files/AlsaDevices.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You
apport information
** Attachment added: AplayDevices.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489836/+files/AplayDevices.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
apport information
** Attachment added: BootDmesg.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489837/+files/BootDmesg.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You
apport information
** Attachment added: Card0.Amixer.values.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489838/+files/Card0.Amixer.values.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
apport information
** Attachment added: Card0.Codecs.codec.0.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489839/+files/Card0.Codecs.codec.0.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489841/+files/CurrentDmesg.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
apport information
** Attachment added: Card0.Codecs.codec.1.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489840/+files/Card0.Codecs.codec.1.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
apport information
** Attachment added: Lsusb.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489844/+files/Lsusb.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You received
apport information
** Attachment added: IwConfig.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489842/+files/IwConfig.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489843/+files/Lspci.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You received
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489846/+files/ProcCpuinfo.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You
apport information
** Attachment added: PciMultimedia.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489845/+files/PciMultimedia.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489847/+files/ProcInterrupts.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
apport information
** Attachment added: ProcModules.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489848/+files/ProcModules.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You
apport information
** Attachment added: RfKill.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489849/+files/RfKill.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You received
apport information
** Attachment added: UdevLog.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489851/+files/UdevLog.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You received
apport information
** Attachment added: WifiSyslog.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489852/+files/WifiSyslog.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You
And the same again - I've booted Maverick Alpha 3 times on this machine
and each time this happens. In this case before the boot process has
really completed.
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
apport information
** Attachment added: UdevDb.txt
https://bugs.edge.launchpad.net/bugs/581441/+attachment/1489850/+files/UdevDb.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You received
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
boot fails due to null pointer dereference in drm/radeon
https://bugs.launchpad.net/bugs/581633
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I'm seeing this exact problem with Lucid on an Aspire One AOA 150Ab and an SD
card.
A variant on #61 works for me - I only needed #1 and #2.
--
JMicron internal card reader recognizes SD only when inserted at startup
https://bugs.launchpad.net/bugs/258446
You received this bug notification
** Attachment added: Here's another log file extract showing this bug.
http://launchpadlibrarian.net/49160507/launchpad_581441.txt
--
iwl3945: immediately after boot goes into loop of Microcode SW error detected.
Restarting 0x8208
https://bugs.launchpad.net/bugs/581441
You received this
I've tried linux-image-2.6.33-02063304-generic and
linux-image-2.6.34-020634-generic as well as getting more experience with the
standard lucid kernel.
The behaviour of all 3 is closer to the karmic behaviour - perhaps every 1-2
days the wifi system would die with a 'Microcode SW error'. The
I've tried two upstream kernels - linux-image-2.6.33-02063304-generic and
linux-image-2.6.34-020634-generic.
Neither of these boots far enough to reproduce this problem due to a bug in the
dc395x driver.
** Tags removed: needs-upstream-testing
--
boot fails due to null pointer dereference in
Public bug reported:
9 times out of 10 on this PC, the boot process fails with a null pointer
dereference in DRM.
It boots as far as a login prompt and I can login but the whole system hangs
within a few minutes.
This sounds extremely similar to 549476 however I was asked to open a new bug
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/48594337/BootDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/48594338/Dependencies.txt
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/48594339/Lspci.txt
** Attachment added:
I see this in Lucid on my Dell D420.
--
Black screen + freeze when suspending or hibernating with mounted SD Card
https://bugs.launchpad.net/bugs/464712
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Having upgraded from Karmic to Lucid, the iwl3945 driver no longer works on
this laptop. Under karmic, perhaps every 1-2 days the wifi system would die
with a 'Microcode SW error'. The fix was to disable wifi, 'rmmod iwl3945',
suspend the laptop for some seconds, resume,
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/48570565/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/48570566/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/48570567/BootDmesg.txt
**
I get this bug with a brand new install of the Karmic release CD.
** Changed in: linux (Ubuntu)
Status: Invalid = New
--
[r100 drm] BUG: unable to handle kernel NULL pointer dereference in
r100_get_accessible_vram
https://bugs.launchpad.net/bugs/549476
You received this bug
Here is the kern.log file.
** Attachment added: kern.log
http://launchpadlibrarian.net/47217931/kern.log
--
[r100 drm] BUG: unable to handle kernel NULL pointer dereference in
r100_get_accessible_vram
https://bugs.launchpad.net/bugs/549476
You received this bug notification because you are
Public bug reported:
Binary package hint: pm-utils
Just installed karmic on this laptop. Now if I suspend to RAM with the
SD card mounted, the system just hangs some way down in the process.
It's 100% reproducible in my tests so far. It worked fine in previous
releases. It works fine if I
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34854104/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/34854105/XsessionErrors.txt
--
suspend to RAM crash when SD card filesystem mounted
https://bugs.launchpad.net/bugs/468298
** Attachment added: output of lspci -vvnn
http://launchpadlibrarian.net/34854420/lspci_vvnn
--
suspend to RAM crash when SD card filesystem mounted
https://bugs.launchpad.net/bugs/468298
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've tried the instructions in the DebuggingKernelSuspendHibernateResume
wiki under Suspending from text mode. The system hangs when I do pm-
suspend but no output is printed.
--
suspend to RAM crash when SD card filesystem mounted
https://bugs.launchpad.net/bugs/468298
You received this bug
*** This bug is a duplicate of bug 347587 ***
https://bugs.launchpad.net/bugs/347587
While digging around, I found that when I'm logged out, a logfile is
generated in /var/log/gdm which finishes with the following;
X: ../../src/i830_batchbuffer.h:78: intel_batch_emit_dword: Assertion
*** This bug is a duplicate of bug 347587 ***
https://bugs.launchpad.net/bugs/347587
** This bug has been marked a duplicate of bug 347587
[i4500MHD] Kubuntu: X asserts on pI830-batch_ptr != 0 on resume from
suspend (UXA bug)
--
logout on resume from suspend
Is there any chance of a Jaunty version of this fix appearing in
x-updates?
--
[i4500MHD] Kubuntu: X asserts on pI830-batch_ptr != 0 on resume from suspend
(UXA bug)
https://bugs.launchpad.net/bugs/347587
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've removed both UXA and virtual from Xorg.conf and I'm seeing if the problems
re-occur. So far they haven't but I'll need to give it more time to be
confident.
Also https://bugs.launchpad.net/bugs/385830 hasn't re-occurred either (logout
on resume from suspend).
--
[i945GM] screen goes
Public bug reported:
Sometimes when I resume from suspend, there's a long wait and then I get the
login screen and everything which was there when I suspended is lost.
I've not managed to find a reproducible set of circumstances for the first
occurence of the problem after a reboot however once
Ctrl+Alt+F1 does indeed add a drmDropMaster line each time I switch to a
VT.
** Attachment added: Xorg.0.log showing switch to VT and return
http://launchpadlibrarian.net/27769425/Xorg.0.log
--
[i945GM] screen goes black about once per day after upgrading to latest intel
drivers
The black screen just happened again.
Ctrl+Alt+F1 / Ctrl+Alt+F7 works to repeatedly switch between the VT and the
black screen.
The drmDropMaster line is added each time.
Attached is a copy of Xorg.log.0 taken after a Ctrl+Alt+F1.
It turns out that suspend / resume clears the problem until the
Public bug reported:
Binary package hint: xserver-xorg-video-intel
I was advised to upgrade to version 2.7.1 of the intel drivers from
x-updates in order to get dual-screen to work (see
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/379805). Since then, about once per
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/27638166/Dependencies.txt
** Attachment added: LsHal.txt
http://launchpadlibrarian.net/27638167/LsHal.txt
** Attachment added: LsMod.txt
http://launchpadlibrarian.net/27638168/LsMod.txt
** Attachment added: LsPci.txt
** Attachment added: The last 200 lines of syslog after the screen goes black
before reboot
http://launchpadlibrarian.net/27638201/syslog
--
screen goes black about once per day after upgrading to latest intel drivers
https://bugs.launchpad.net/bugs/384730
You received this bug notification
** Attachment added: Xorg.0.log - after the screen went black before reboot
http://launchpadlibrarian.net/27638215/Xorg.0.log
--
screen goes black about once per day after upgrading to latest intel drivers
https://bugs.launchpad.net/bugs/384730
You received this bug notification because you
Sorry for the delay in replying - work's been rather busy.
Switching to UXA solves this problem. The white screen is gone! Dual
screen behaves as expected.
Unfortunately somewhere in the set of updates which got installed
something else broke. About once per day, the entire screen just goes
Where should I find a suitable version of xorg-xserver-video-intel-dbg?
As far as I can see, it's not in regular jaunty, jaunty-proposed or the x-swat
PPA.
The laptop is a Dell Latitude D420.
--
[i945gm] virtual 2048 in xorg.conf causes blank white screen on login
I've managed to resolve the partially installed package problem. As part
of this, I've ended up running the kernel from jaunty-proposed.
Version 2.7.1 shows the same problem - a white screen after login. I've
checked both with and without an external screen connected.
I've attached the
** Attachment added: Xorg.0.log - not working
http://launchpadlibrarian.net/27168442/Xorg.0.log.old
--
[i945gm] virtual 2048 in xorg.conf causes blank white screen on login
https://bugs.launchpad.net/bugs/379805
You received this bug notification because you are a member of Ubuntu
Bugs,
1. Is it the external monitor, the laptop monitor or both that go white?
The LCD screen on the laptop.
2. With which desktop environment does this happen? (kde, gnome, xfce, etc...)
Does it happen with other desktop environment as well?
Gnome. I don't have any others installed.
3. Does the
Public bug reported:
Binary package hint: xserver-xorg-video-intel
I'm trying to configure the secondary output on this laptop for use with
projectors (etc).
When I go through system / preferences / display, it tells me that the virtual
keyword needs adding to my xorg.conf file and does it
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/27093431/Dependencies.txt
** Attachment added: LsHal.txt
http://launchpadlibrarian.net/27093432/LsHal.txt
** Attachment added: LsMod.txt
http://launchpadlibrarian.net/27093433/LsMod.txt
** Attachment added: LsPci.txt
I'm having the same problem having just installed Jaunty on a Dell Latitude
D420. It's happened twice today having installed Jaunty last night.
One of the questions asked if hal was running. Here's the output of ps aux |
grep hal
105 2555 0.0 0.1 6684 2768 ?Ss 13:54 0:12
I've just re-started hal (/etc/init.d/hal restart) and the problem is still
here.
Attached is the output of lshal after this.
** Attachment added: Output of lshal when keyboard input is not working -
after hal restart
** Attachment added: Output of lshal when keyboard input is not working
http://launchpadlibrarian.net/26825488/lshal-keyboard-not-working
--
[jaunty] Mouse and keyboard stop responding
https://bugs.launchpad.net/bugs/320173
You received this bug notification because you are a member of
1 - 100 of 104 matches
Mail list logo
