[Bug 137686] Re: [gutsy] [regression] (regression from edgy to feisty and to gutsy) tifm_sd module not working and not producing any message in logs
I inserted it after a hibernate, it did not trigger a mount. I removed it then inserted it again, and it did mount and open a window. After trying a few times, it seems that the first one only is the problem (not mounting), but subsequent ones work fine. I did not reboot and try yet (too disruptive to my work). -- [gutsy] [regression] (regression from edgy to feisty and to gutsy) tifm_sd module not working and not producing any message in logs https://bugs.launchpad.net/bugs/137686 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/ubuntu-bugs
[Bug 137686] Re: [gutsy] [regression] (regression from edgy to feisty and to gutsy) tifm_sd module not working and not producing any message in logs
I have two quite similar Toshiba laptops, one on Kubuntu Feisty (A100-TA6) and the other on Kubuntu Gutsy (A200-TR6). On the Feisty one, SD cards work fine, and automatically gets mounts and Konqueror will open a window for it. All I had to do in Feisty was to either modprobe tifm_sd, or add it to /etc/modules. On Gutsy, none of the above suggestions work. The kernel does detect the insertion, but no device is associated with it, the card is not mounted. As a side note, I am starting to get frustrated with breakage on upgrades. This SD card is the third case. The first two were the slmodem on the HDA audio device, and the second is an Intersil chipset Wireless card. All of them worked on one release and did not work on the next. -- [gutsy] [regression] (regression from edgy to feisty and to gutsy) tifm_sd module not working and not producing any message in logs https://bugs.launchpad.net/bugs/137686 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/ubuntu-bugs
[Bug 137686] Re: [gutsy] [regression] (regression from edgy to feisty and to gutsy) tifm_sd module not working and not producing any message in logs
I have an update on this issue. The way I use the laptop is to hibernate it and then restart it. I rarely reboot it. This is a Toshiba A200-TR6 with Gutsy on it. So, I removed all the stuff I had before from the above trials, and only had one change in /etc/modules, by adding the line tifm_sd to it. And then I rebooted. Now, when I insert an SD card, the partition is detected and Dolphin launches automatically. [ 1442.056000] tifm_core: MMC/SD card detected in socket 0:1 [ 1442.208000] mmcblk0: mmc1:b1c6 SU02G 1985024KiB [ 1442.208000] mmcblk0: p1 This is exactly the same way I had it working on Edgy and Feisty on the other laptop (A100-TA6), as I described here last year. http://baheyeldin.com/technology/linux/kubuntu-6-10-edgy-eft-on-a -toshiba-laptop-satellite-a100-ta6.html Not sure why it did not work earlier until I added the above line and rebooted, but glad it does work now. -- [gutsy] [regression] (regression from edgy to feisty and to gutsy) tifm_sd module not working and not producing any message in logs https://bugs.launchpad.net/bugs/137686 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/ubuntu-bugs
[Bug 28326] Re: i810 Xv crashes after suspend - infinite resprawn
I reported this above in comment 62 last year on a Toshiba A100-TA6. I tried the Gutsy live CD. It allows suspend, but not hibernate. When I tried suspend, the video was fine after and the desktop appeared again unharmed. So, I can say that Gutsy fixed it with suspend. Unsure about hibernate, but it probably is the same. I am tempted to upgrade to Gutsy and see what happens. -- i810 Xv crashes after suspend - infinite resprawn https://bugs.launchpad.net/bugs/28326 You received this bug notification because you are a member of Kubuntu Team, which is a subscriber of a duplicate bug. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 28326] Re: i810 Xv crashes after suspend - infinite resprawn
The first sentence I posted above may be confusing. I had the problem initially on Edgy. When I upgraded to Feisty, I installed an alternative driver, and it works fine. See comment 94. Now with Gutsy, there seems to be solution, based on the live CD test in my comment above this one. I will confirm it when I upgrade to Gutsy soon. -- i810 Xv crashes after suspend - infinite resprawn https://bugs.launchpad.net/bugs/28326 You received this bug notification because you are a member of Kubuntu Team, which is a subscriber of a duplicate bug. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 105357] Re: Feisty wireless broken after update
I am having the same problem, on a Dell Latitude CPxJ. It has a PCMCIA Prism54 card (Gigafast WF728-AEX) worked fine on Edgy. Upon upgrading to Feisty, the card is recognized, and can scan for APs, but does not associate. dmesg shows: [ 42.764000] p54: LM86 firmware [ 43.80] wmaster0: Selected rate control algorithm 'simple' [ 43.992000] wiphy0: hwaddr 00:0a:e9:08:69:86, isl3880 Then several occurrences of this error as well: [ 142.42] eth0: starting scan [ 142.48] wiphy0: frequency change failed [ 142.54] wiphy0: frequency change failed [ 142.60] wiphy0: frequency change failed [ 142.66] wiphy0: frequency change failed [ 142.72] wiphy0: frequency change failed [ 142.84] wiphy0: frequency change failed [ 142.90] wiphy0: frequency change failed [ 142.96] wiphy0: frequency change failed [ 143.02] wiphy0: frequency change failed [ 143.08] eth0: scan completed I will attach the relevant info in subsequent comments. ** Attachment added: dmesg.txt http://librarian.launchpad.net/7563338/dmesg.txt -- Feisty wireless broken after update https://bugs.launchpad.net/bugs/105357 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/ubuntu-bugs
[Bug 105357] Re: Feisty wireless broken after update
iwlist scan output ** Attachment added: iwlist.txt http://librarian.launchpad.net/7563340/iwlist.txt -- Feisty wireless broken after update https://bugs.launchpad.net/bugs/105357 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/ubuntu-bugs
[Bug 105357] Re: Feisty wireless broken after update
lsusb ** Attachment added: lsusb.txt http://librarian.launchpad.net/7563345/lsusb.txt -- Feisty wireless broken after update https://bugs.launchpad.net/bugs/105357 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/ubuntu-bugs
[Bug 105357] Re: Feisty wireless broken after update
lspci -vv output ** Attachment added: lspci-vv.txt http://librarian.launchpad.net/7563341/lspci-vv.txt -- Feisty wireless broken after update https://bugs.launchpad.net/bugs/105357 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/ubuntu-bugs
[Bug 105357] Re: Feisty wireless broken after update
dmidecode ** Attachment added: dmidecode.txt http://librarian.launchpad.net/7563349/dmidecode.txt -- Feisty wireless broken after update https://bugs.launchpad.net/bugs/105357 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/ubuntu-bugs
[Bug 28326] Re: i810 Xv crashes after suspend - infinite resprawn
As I mentioned previously, my laptop is a Toshiba Satellite A100-TA6, using the Intel 945GM chip. Following my test using Kubuntu Feisty Herd5 (see a href=https://bugs.launchpad.net/ubuntu/+source/xserver-xorg- video-i810/+bug/28326/comments/77this comment above/a), I upgraded to Feisty, hoping everything would work out. However, after the upgrade, whenever I changed the xorg.conf file to use i810 or intel (instead of vesa), the screen is messed up. The best way to explain the problem is to say that the font is way too big. Here is a a href=http://baheyeldin.com/click/833/0;link to a screen shot/a. I also noted that the source tar.gz for the xserver-xorg-video-intel has this in the README: Common issues not caused by the driver - Font sizes (DPI) are wrong. Some displays incorrectly report their physical size, which is harmless on most OSes that always assume 96dpi displays. This can be fixed through quirks for specific monitors in the X Server, and the output of xrandr --prop along with a physical measurement of the screen size in a bug report against the server can help get that fixed. I tried setting DisplaySize 338 212 in xorg.conf Monitor section to fix the DPI, but that did not work either. I noticed that Feisty has a new package name a href=https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel /xserver-xorg-video-intel/a which replaces the older a href=https://launchpad.net/ubuntu/+source/xserver-xorg-video-i810 /xserver-xorg-video-i810/a (note the version numbers). So, what I did was a) Install xserver-xorg-video-i810 (2:1.7.4-0ubuntu1). The install of the i810 package automatically removed the -intel package. b) Uninstall 915resolution c) Then in /etc/default/acpi-support, I set POST_VIDEO=false d) In /etc/X11/xorg.conf, I now have: Section Device Identifier Intel i945 Driver i810 Option VBERestoreTrue Option Dri True BusID PCI:0:2:0 EndSection The good news is after I did this, I am able to: a) Cycle through the resolutions using Ctrl-Alt-+/- b) Send the output to the external VGA port by the Fn key combo. c) Resuming from hibernate works well too. The only drawback is that I am not sure if this is a sustainable solution though, since the -i810 package is replaced by the -intel package which does not work, and will be the only package in Gutsy. -- i810 Xv crashes after suspend - infinite resprawn https://bugs.launchpad.net/bugs/28326 You received this bug notification because you are a member of Kubuntu Team, which is a subscriber of a duplicate bug. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 28326] Re: i810 Xv crashes after suspend - infinite resprawn
Timo Thanks for the info. I assume that the Herd5 of Kubuntu would also have that, since I am not using Ubuntu. I don't know if hibernate would from the live CD or does it need to be installed on the hard disk. Will check. -- i810 Xv crashes after suspend - infinite resprawn https://launchpad.net/bugs/28326 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 28326] Re: i810 Xv crashes after suspend - infinite resprawn
I downloaded Kubuntu Feisty Herd5, and tested using the Live CD. I can say it is promising. Issuing the following commands on my Toshiba laptop: # sudo bash # /etc/acpi/sleep.sh Causes the blue power LED to become flashing amber (meaning it did go to suspend). Pressing it makes it go back normally to a functioning desktop. No more hourglass/respawn problem. On a whim, I tried with the Kubuntu Edgy CD as a live CD. Doing the same steps above causes the screen to blank, but the LED stays blue (i.e. power on), and nothing happens. This means I cannot reproduce the problem with Edgy as a live CD, but there sure is hope with Feisty. I will wait till Feisty is officially released before I plunge into an upgrade. -- i810 Xv crashes after suspend - infinite resprawn https://launchpad.net/bugs/28326 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 28326] Re: i810 Xv crashes after suspend - infinite resprawn
The comment from Kaleo above says that he tested 1.7.4 and it is not yet fixed. The upstream package did not fix this problem. See Alan Hourihane's comment here https://bugs.freedesktop.org/show_bug.cgi?id=5774#c46, saying it is fixed, but the driver on his web site (dated a few days after his comment) does not fix the problem for me. -- i810 Xv crashes after suspend - infinite resprawn https://launchpad.net/bugs/28326 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 28326] Re: i810 Xv crashes after suspend - infinite resprawn
If you are referring to the i810_drv.so that is available on Alan Hourihan's site (link above), then this is still the old one, dated 2006-11-24 07:06. I tested this one, and it did not solve the problem. Moreover, the bugzilla report above is now closed with Alan asking people to open a new report. Or are you referring to some other place for upload? If so, then where? -- i810 Xv crashes after suspend - infinite resprawn https://launchpad.net/bugs/28326 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 53216] Re: BUG() report in getnstimeofday: soft lockup
I have the same problem. Kubuntu edgy 6.10 on a Centrino Duo with ipw3945 wireless. Full configuration of the hardware is here: a href=http://baheyeldin.com/click/782/5;Toshiba Satellite A100-TA6 with Kubuntu/a. Occasionally, when an incoming call from Skype comes in, (and perhaps when I am on battery), the machine will hang for 30 seconds or so, then everything comes back to normal. Plain vanilla kernel, with only kqemu tainting it (and perhaps the ipw3945) $ uname -a Linux somehost 2.6.17-10-generic #2 SMP Tue Dec 5 22:28:26 UTC 2006 i686 GNU/Linux Here are two occurances. [17509010.604000] BUG: soft lockup detected on CPU#0! [17509010.604000] c01491cf softlockup_tick+0x9f/0xf0 c012bee1 update_process_times+0x31/0x80 [17509010.604000] c0139320 hrtimer_get_res+0x0/0x60 c0114d13 smp_apic_timer_interrupt+0x53/0x60 [17509010.604000] c010413c apic_timer_interrupt+0x1c/0x30 c0139320 hrtimer_get_res+0x0/0x60 [17509010.604000] c01172c8 hpet_readl+0x8/0x10 c010e98a get_offset_hpet+0xa/0x30 [17509010.604000] c0106959 do_gettimeofday+0x19/0xc0 c0139320 hrtimer_get_res+0x0/0x60 [17509010.604000] c0126f3d getnstimeofday+0xd/0x30 c0135697 sys_clock_gettime+0x77/0x90 [17509010.604000] c0102fbb sysenter_past_esp+0x54/0x79 [17509010.86] BUG: soft lockup detected on CPU#1! [17509010.86] c01491cf softlockup_tick+0x9f/0xf0 c012bee1 update_process_times+0x31/0x80 [17509010.86] c0114d13 smp_apic_timer_interrupt+0x53/0x60 c010413c apic_timer_interrupt+0x1c/0x30 [17509042.70] ipw3945: Microcode SW error detected. Restarting. [17509042.768000] ipw3945: Microcode HW error detected. Restarting. [17509043.272000] ipw3945: Error sending LEDS_CMD: time out after 500ms. [17509043.772000] ipw3945: Error sending ADD_STA: time out after 500ms. [17509043.772000] ipw3945: Can't stop Rx DMA. [17509045.184000] ipw3945: Detected geography ABG (11 802.11bg channels, 13 802.11a channels) [17509055.344000] BUG: soft lockup detected on CPU#1! [17509055.344000] c01491cf softlockup_tick+0x9f/0xf0 c012bee1 update_process_times+0x31/0x80 [17509055.344000] c0114d13 smp_apic_timer_interrupt+0x53/0x60 c010413c apic_timer_interrupt+0x1c/0x30 [17509055.344000] c01172c8 hpet_readl+0x8/0x10 c010e98a get_offset_hpet+0xa/0x30 [17509055.344000] c0106959 do_gettimeofday+0x19/0xc0 c0139320 hrtimer_get_res+0x0/0x60 [17509055.344000] c0126f3d getnstimeofday+0xd/0x30 c0135697 sys_clock_gettime+0x77/0x90 [17509055.344000] c0102fbb sysenter_past_esp+0x54/0x79 [17510957.904000] ipw3945: Microcode SW error detected. Restarting. [17510958.424000] ipw3945: Error sending LEDS_CMD: time out after 500ms. [17510959.42] ipw3945: Can't stop Rx DMA. [17510960.416000] psmouse.c: TouchPad at isa0060/serio4/input0 lost synchronization, throwing 1 bytes away. [17510960.86] ipw3945: Detected geography ABG (11 802.11bg channels, 13 802.11a channels) Second occurance. [17576818.04] BUG: soft lockup detected on CPU#1! [17576818.04] c01491cf softlockup_tick+0x9f/0xf0 c012bee1 update_process_times+0x31/0x80 [17576818.04] c0114d13 smp_apic_timer_interrupt+0x53/0x60 c010413c apic_timer_interrupt+0x1c/0x30 [17576818.04] c01172c8 hpet_readl+0x8/0x10 c010e98a get_offset_hpet+0xa/0x30 [17576818.04] c0106959 do_gettimeofday+0x19/0xc0 c0139320 hrtimer_get_res+0x0/0x60 [17576818.04] c0126f3d getnstimeofday+0xd/0x30 c0135697 sys_clock_gettime+0x77/0x90 [17576818.04] c0102fbb sysenter_past_esp+0x54/0x79 [17576818.208000] BUG: soft lockup detected on CPU#0! [17576818.208000] c01491cf softlockup_tick+0x9f/0xf0 c012bee1 update_process_times+0x31/0x80 [17576818.208000] c0114d13 smp_apic_timer_interrupt+0x53/0x60 c010413c apic_timer_interrupt+0x1c/0x30 [17576818.208000] c013007b sys_reboot+0x1b/0x1d0 c0102fae sysenter_past_esp+0x47/0x79 [17576849.984000] BUG: warning at drivers/scsi/libata-core.c:3266/ata_pio_complete() [17576849.984000] f8885145 ata_pio_task+0x745/0x7c0 [libata] c011cdf8 __wake_up+0x38/0x50 [17576849.984000] c0132702 run_workqueue+0x72/0xf0 f8884a00 ata_pio_task+0x0/0x7c0 [libata] [17576849.984000] c01332e7 worker_thread+0x117/0x140 c011bde0 default_wake_function+0x0/0x10 [17576849.984000] c01331d0 worker_thread+0x0/0x140 c0135f8b kthread+0xab/0xe0 [17576849.984000] c0135ee0 kthread+0x0/0xe0 c0101005 kernel_thread_helper+0x5/0x10 [17576849.984000] ipw3945: Microcode SW error detected. Restarting. [17576849.988000] ata2: command 0x58 timeout, stat 0x50 host_stat 0x0 [17576850.488000] ipw3945: Error sending LEDS_CMD: time out after 500ms. [17576850.988000] ipw3945: Error sending ADD_STA: time out after 500ms. [17576850.988000] ipw3945: Can't stop Rx DMA. -- BUG() report in getnstimeofday: soft lockup https://launchpad.net/bugs/53216 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63365] Re: [Edgy] xorg incorrectly detects lv3:ralt_switch option
I can confirm the same problem on a Toshiba A100-TA6, where in Edgy the right Alt key does not work, and gives ISO_Level3_Shift. Commenting out the XkbOptions line in /etc/X11/xorg.conf solved this problem. -- [Edgy] xorg incorrectly detects lv3:ralt_switch option https://launchpad.net/bugs/63365 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64070] Re: suspend/resume porblems with centrino duo
I found another problem. Even though the above fix takes care of the CPU speed, the fan keeps going at high speed after a resume (from suspend or hibernate). Anyone got that solved? -- suspend/resume porblems with centrino duo https://launchpad.net/bugs/64070 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64070] Re: suspend/resume porblems with centrino duo
Here is a solution that worked for me. Create the following script. in /etc/acpi/resume.d/75-dual-core-cpu- freq.sh #!/bin/sh SYS_DIR=/sys/devices/system/cpu #POLICY=performance ### # POLICY can be any of: # userspace powersave ondemand conservative performance # POLICY=ondemand for CPU in `ls $SYS_DIR` do echo -n $POLICY $SYS_DIR/$CPU/cpufreq/scaling_governor done #== Now the policy will be set correctly after a resume from hibernate or suspend state. -- suspend/resume porblems with centrino duo https://launchpad.net/bugs/64070 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 28326] Re: i810 Xv crashes after suspend - infinite resprawn
It depends on what you do with the video. For someone who uses the machine for development, browsing, email, IM, ...etc, this is acceptable. Of course, if you want multimedia intensive applications, then you are stuck. The latest driver from A Hourihane did not work for me. It is dated Nov 24, so that path is also a dead end. -- i810 Xv crashes after suspend - infinite resprawn https://launchpad.net/bugs/28326 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 64070] Re: suspend/resume porblems with centrino duo
I have the same exact problem, so it is confirmed. This is a kubuntu Edgy 6.10 install on a Toshiba A100-TA6. It has T2250 Centrino Duo. When the laptop is rebooted, both CPUs are running at 800MHz most of the time, and one or the other goes up to the full 1733MHz. This happens upon resuming from suspend, or from hibernate. The fan also goes fast and I can feel air coming out of the vents. It goes back to normal if I reboot the laptop. See this: $ grep MHz /proc/cpuinfo cpu MHz : 800.000 cpu MHz : 1733.000 The puzzling part is that both CPUs are in the same ACPI state regardless: $ diff /proc/acpi/processor/CPU? diff /proc/acpi/processor/CPU0/info /proc/acpi/processor/CPU1/info 1,2c1,2 processor id:0 acpi id: 0 --- processor id:1 acpi id: 1 diff /proc/acpi/processor/CPU0/power /proc/acpi/processor/CPU1/power 6c6 *C2: type[C2] promotion[--] demotion[C1] latency[001] usage[01822333] duration[007367703269] --- *C2: type[C2] promotion[--] demotion[C1] latency[001] usage[01743842] duration[007432976070] -- suspend/resume porblems with centrino duo https://launchpad.net/bugs/64070 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64070] Re: suspend/resume porblems with centrino duo
Were you able to manually reduce the speed of the second cpu? If so, how? I could not use acpi (echo to /proc/...) to do that. -- suspend/resume porblems with centrino duo https://launchpad.net/bugs/64070 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 28326] Same problem on Toshiba Satellite with suspend or hibernate
I am facing this exact same issue with Ubuntu 6.10 (Edgy). This is a laptop, Toshiba Satellite A100-TA6, which has an Intel 945. lspci says: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03) When I hibernate or suspend the computer, it comes back fine, except for the display and keyboard. By fine, I mean I can ssh to the laptop, and do command line things. The screen goes from clock pointer to mouse pointer to nothing and keeps cycling into that loop. The keyboard does nothing, so I can't even go to a VT and do stuff. I tried Alan Hourihane's driver (dated Nov 24, 2006), but it did not solve the problem. One person above mentioned Toshiba as well. Can anyone confirm whether they still have the issue with Edgy or was the problem solved? -- i810 Xv crashes after suspend - infinite resprawn https://launchpad.net/bugs/28326 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 28326] Re: i810 Xv crashes after suspend - infinite resprawn
Here is a workaround that may work for some. Since the problem is in the i810 driver, replacing that by another driver would avoid the problem. Some high end features of the hardware may not be available, but for general use, this works for me. What you need to do is replace the i810 entry in the X.org configuration file with the vesa driver. So, edit /etc/X11/xorg.conf and find the word i810. Replace that with vesa. Before: Driver i810 After: Driver vesa Reboot, and then you would be able to suspend/hibernate the computer. -- i810 Xv crashes after suspend - infinite resprawn https://launchpad.net/bugs/28326 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
