Re: [Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
Google for kernel ppa ubuntu and apt-get the new debs... Le 27 mars 2011 08:06, Ludovic 561...@bugs.launchpad.net a écrit : So according to comment 211, this bug is fixed as of version 2.6.38-5.32 of the package linux. I looked around a bit, and the latest build I can find of that package (for amd64) is https://launchpad.net/ubuntu/+source/linux/2.6.38-7.39/+buildjob/2344157. But all of those .deb files are built for Natty, not for e.g. Ubuntu 10.10 (which is what I'm using). So how can I get this fix on my system: - Just install them anyway and hope they'll work? - Wait for a backport of this fix to Ubuntu 10.10? If so, how can I see when (approximately) such a backport will be done? Thanks, Ludovic -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/561802 Title: [i915] blank screen on Latitude E6410 (NOT E6510) To unsubscribe from this bug, go to: https://bugs.launchpad.net/linux/+bug/561802/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/561802 Title: [i915] blank screen on Latitude E6410 (NOT E6510) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
I've been using kernel 2.6.38.2 since maybe 3 weeks, and I'm really happy about the stability with the video. However, I'm having issues now with the wireless, being really really slow and dropping out. Has anyone else had this type of issue ? david On 17 February 2011 22:26, Moustafa Chamli moustafa.cha...@canonical.comwrote: I have been working on a customer case about this exact issue. I have just asked him to try the natty kernel with 10.10, and will report his findings as soon as possible. -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/561802 Title: [i915] blank screen on Latitude E6410 (NOT E6510) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/561802 Title: [i915] blank screen on Latitude E6410 (NOT E6510) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
I will. Going skiing this evening so May not test soon... but i will. Le 18 févr. 2011 14:11, Jeremy LaCroix 561...@bugs.launchpad.net a écrit : Hi David, for the wireless speed issue, I reported the following bug: https://bugzilla.kernel.org/show_bug.cgi?id=29072 Right now I'm seemingly the only one with the problem, so if what happens to me is the same as what happens to you, please add your comments to that bug report, it would help alot. ** Bug watch added: Linux Kernel Bug Tracker #29072 http://bugzilla.kernel.org/show_bug.cgi?id=29072 -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/561802 Title: [i915] blank screen on Latitude E6410 (NOT E6510) To unsubscribe from this bug, go to: https://bugs.launchpad.net/linux/+bug/561802/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/561802 Title: [i915] blank screen on Latitude E6410 (NOT E6510) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
Do you have the apt:add link? On Feb 3, 2011 9:31 AM, Oddbjørn Hansen 561...@bugs.launchpad.net wrote: I have an E6410 ATG with i7-640M running Maveric with kernel and xorg from xorg-edgers. The 2.6.38-1 kernel seems to solve all the addressed issues. Oddbjørn Hansen 2011/2/2 Chris Halse Rogers r...@ubuntu.com Backporting the fix as an SRU to the Lucid or Maverick kernels is unlikely to fly, as there's simply been too many patches over too many kernel releases for it to be easy to extract a minimal safe fix. There should be no problems with using the Natty kernel on an otherwise Lucid or Maverick system, though, and for Lucid at least I think this should be possible with the lts-backport kernels. -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/561802 ... -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/561802 Title: [i915] blank screen on Latitude E6410 (NOT E6510) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/561802 Title: [i915] blank screen on Latitude E6410 (NOT E6510) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
yep : 2.6.37-5 2.6.37-7 2.6.37-8 from the lucid backports ... however, it still doesn't work every time (4 tries yesterday before it booted with screen) 2010/12/12 Philip Aston 561...@bugs.launchpad.net @aftertaf: please explain which kernel you are using from the ppa. (To what does 5/7/8 refer?) I tried 2.6.37-020637rc2, but no joy. The only kernel I've found that does not suffer from the black screen problem is 2.6.32-21 from the Lucid repository. I tried later versions of that kernel (-25, -26), but they failed too. FWIW, I'm separately using 2.6.32-25 on an e6400 to avoid the black screen after resume issue. (e6410, Intel i915, A06 BIOS, maverick). -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/561802 Title: [i915] blank screen on Latitude E6410 (NOT E6510) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/561802 Title: [i915] blank screen on Latitude E6410 (NOT E6510) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
i've updated the bios to A06, and am using kernel 2.6.37.x (5/7/8) from kernel ppa. From what I can tell, it works fine, but I need to test more... for now I have working screen when not in docking station, and I have cloned screen with both displays working when in docking station but i need to test more to confirm this isn't just a fluke david 2010/12/7 CVTECH 561...@bugs.launchpad.net Just an update to post #182, I was able to restore functionality only by reinstalling from the 10.04.1 ISO distribution image that had the 2.6.32-24 kernel. I used meld to compare my two machines running 2.6.32-25, the one that was broken had been updated to 2.6.32-26 by update manager, then I tried to go back to 2.6.32-25. This left slight differences (0.1 rev) in Xorg and Plymouth that maybe were related to this bug. Anyway, there was no way I could find to get back to the state where the internal monitor would come on without plugging in an external monitor, even under previous kernels linked by grub and the recovery modes. The version of plymouth on the working machine was 0.8.2-2ubuntu2, the broken was 0.8.2-2ubuntu2.1 the version of Xorg on the working machines was xserver-common 2:1.7.6-2ubuntu7.3 and broken version was 7.4. Similarly grub had slight differences version 1.98-1ubuntu7 to 1.98-1ubuntu8. From what I can tell by reading various wikis, hard to image much else video related other than plymouth and xserver is running at the time the splash screen goes dark after grub menu. Plugging in a monitor during the plymouth splash or the login screen instantly would restore the internal display. Looking forward to hearing some more test reports of the ppa kernel post and bios fix of previous two posts. I may be able to dedicate one machine to testing later this week. -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/561802 Title: [i915] blank screen on Latitude E6410 (NOT E6510) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/561802 Title: [i915] blank screen on Latitude E6410 (NOT E6510) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
Patrick / Partypooper: Where did you get this kernel from exactly? I can't find it on http://kernel.ubuntu.com/~kernel-ppa/mainline/ ... Or did you actually get it via apt ? in which case, what is the deb line in your sources.list that gets you this kernel... Im also very interested ;) david -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/561802 Title: [i915] blank screen on Latitude E6410 (NOT E6510) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
found it myself. deb http://ppa.launchpad.net/kernel-ppa/ppa/ubuntu lucid main Bear in mind this has been released under the lucid branch, not the maverick one . . . . David About to test 2010/12/2 partypooper 561...@bugs.launchpad.net Hi there! Kernel 2.6.37.5-generic that has been released today on kernel-ppa fixes all my issues. * I can boot without an external monitor and the laptop lcd screen works. Even after a reboot. * I can boot with an external monitor (attached either via VGA cable or a docking station) and the laptop detects the external monitor fine (although it does not detect it at the correct resolution (monitor is a DELL 24). Cherry on the top, I tested suspend and resume and it worked. I have an e6410/i5/intel video card Looks like I will be able to finally use my laptop. Could anyone confirm? Thanks, Patrick -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/561802 Title: [i915] blank screen on Latitude E6410 (NOT E6510) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/561802 Title: [i915] blank screen on Latitude E6410 (NOT E6510) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
wow :) i did this in the backwards manner : installed 10.10, which has the problem, and since downgraded a kernel to 2.6.32.11 which worked fine, but no wifi... From what I can tell from the forums, there is a kernel patch that fixed this and that may have been unpatched since.. hoping someone finds and fixes for good... david 2010/11/30 CVTECH 561...@bugs.launchpad.net I have access to qty3 E6410ATGs with the 1280x800 display (reports itself as seiko-epson corporation 14), only one is experiencing this issue and this is after update manager updating from the base Ubuntu 10.04.1 installation with 2.6.32-24 kernel. The machine having troubles is a core5-i540 vs core5-i520 on the other two machines not having troubles. The symptoms are very similar to post #168. The machine worked fine until updating a couple days ago. Included in the update was update from kernel 2.6.32-24 to 2.6.32-26 but I suspect this is not the issue for reasons I will explain. I am experiencing similar issues to post #168. At login screen after updates including the 2.6.32-26 kernel the blank screen happens. Plugging in any external monitor (on Dsub 15 pin, or DisplayPort) instantly the internal monitor will come to life. So the workaround is to pick the kernel from Grub, wait for the blank screen which would normally be the login/welcome screen on Ubuntu, quickly plug in a cable (there is about a 5 second window that this works), then unplug the cable and now you can take the laptop and walk around the house like you wanted to in the first place when you bought a laptop. This is very reliable, with about 96 of 100 reboots (hot or cold) able to start the internal display by plugging a monitor cable in (Dsub or Displayport, doesn't matter). The other 4 reboots vary from won't work (maybe took too long to plug) to about 1 in 100 will randomly just boot without needing the cable plug procedure! I note also that the monitor must be present but not required to be powered on, an unterminated cable does not have the same effect. So, something in the process sees the presence of a new external monitor connection and this then triggers the internal monitor to come on (at correct resolution) as DP1 and everything is good after that until the next reboot, even after disconnecting the external cable. I suspect something has changed unrelated to the kernel update. The reason is that the two machines I have that are working fine one is running 2.6.32-24, the other 2.6.32-25. The machine having problems was working fine on 2.6.32-24 and started having issues immediately after the update (via update manager) that included 2.6.32-26 amongst many other things. I removed (via package manager) the 2.6.32-26 kernel image and headers and installed the 2.6.32-25. This did not solve the issue and now even if I boot (from grub) the old previously working 2.6.32-24 or the 2.6.32-25 kernel that works on another machine the same issue happens on the problem machine, even in recovery mode! I am reasonably familiar with Ubuntu as a user, but no idea how to gather info to track this down. If someone has an idea of a path to follow, then let me know how to compile logs or config files I can gather info from the working (2.6.32-25) vs non-working (2.6.32.-25) machines, only difference being i520 vs i540 processors. These are live (not development) machines so unfortunately I can't try too much in the way of installing source code and patches but on the third machine if we can come up with a way to replicate the problem, it can be a total sandbox to test anything out. I note also that this is the Daylight Viewable E6410 ATG display which has a max resolution of 1280x800 and when working is correctly identified by xrandr on DP1. Dell makes the E6410 with at least 1 other display. Also intel graphics gma4500 (i915) on all machines and kernels noted are the -generic versions. -- [i915] blank screen on Latitude E6410 (NOT E6510) https://bugs.launchpad.net/bugs/561802 You received this bug notification because you are a direct subscriber of the bug. -- [i915] blank screen on Latitude E6410 (NOT E6510) https://bugs.launchpad.net/bugs/561802 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
can anyone give a status update on this problem ? or have a patched kernel .deb lying around for us to test? I havent built a kernel in ages, and i've never patched on before so i'm a bit screwed otherwise . . . :) david -- [i915] blank screen on Latitude E6410 (NOT E6510) https://bugs.launchpad.net/bugs/561802 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
about to try the kernel 2.6.32 mentioned in bug 554569 and the 2.6.37.rc2 from ubuntu.kernel.org all good fun :) -- [i915] blank screen on Latitude E6410 (NOT E6510) https://bugs.launchpad.net/bugs/561802 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
1) 2.6.37rc2 : first boot OK, but hung on plymouth. I dropped to TTY1, changed the plymouth screen with update-alternatives, to put back the original kubuntu one, restarted kdm and worked. reboot, NOK : same problem as before : black screen 2) then tried 2.6.32.11+drm33.2-x201 first boot OK : splash screen works, and on drop to console i see NO ERRORS mentioning i915 symbols etc... so to test with a reboot second boot OK : splash screen works only problem now is no Wireless . . . . . 3) back to .37rc2 first boot : OKish : I set nosplash in boot options, but got a plymouth theme anyway... Screen flashed black/white a couple of times then X popped up like nothing happened. drop to TTY shows the intel ips : failed to get i915 symbols, graphics turbo disabled message and drm:ironlake_crtc_disable *ERROR* failed to disable transcoder reboot the flashing happens when plymouth is being initialised , whether its on boot up or shutdown on reboot... flashing again, this time no plymouth shown and no X black screen :( i'm wondering if plymouth is messing with stuff . .. . or being messed with .. hard reset. third boot : same as before :( fourth boot : set verbose nosplash in boot options...no change ! so, if someone can briefly explain to me how to use the patches much mentioned above.i'm more than willing -- [i915] blank screen on Latitude E6410 (NOT E6510) https://bugs.launchpad.net/bugs/561802 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
me too... only hammering Fn F8 during boot makes it work 2010/11/8 namregzepol namregze...@hotmail.com I have downloaded http://kernel.ubuntu.com/~kernel-ppa/mainline/drm- intel-next/2010-11-08-maverick/linux- image-2.6.36-997-generic_2.6.36-997.201011080905_amd64.deb and installed with no luck. It's still in a blank screen. -- [i915] blank screen on Latitude E6410 (NOT E6510) https://bugs.launchpad.net/bugs/561802 You received this bug notification because you are a direct subscriber of the bug. -- [i915] blank screen on Latitude E6410 (NOT E6510) https://bugs.launchpad.net/bugs/561802 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
try this kernel http://kernel.ubuntu.com /~kernel-ppa/mainline/drm-intel-next/ 2010/11/5 namregzepol namregze...@hotmail.com I don't see much activity here yet. Is there any solution that i have miss? Has anybody all the information he needs yet? -- [i915] blank screen on Latitude E6410 (NOT E6510) https://bugs.launchpad.net/bugs/561802 You received this bug notification because you are a direct subscriber of the bug. -- [i915] blank screen on Latitude E6410 (NOT E6510) https://bugs.launchpad.net/bugs/561802 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
tried RC4 kernel, tried i915 gfx patch... nothing changed :( 2010/10/29 namregzepol namregze...@hotmail.com In my e5410 i'm with proposal updates. As i said before most of the times i got a blank screen, but sometimes i've got gdm. I don't know what triggers the screen to go on or blank. I hope the explanation help. -- [i915] blank screen on Latitude E6410 (NOT E6510) https://bugs.launchpad.net/bugs/561802 You received this bug notification because you are a direct subscriber of the bug. -- [i915] blank screen on Latitude E6410 (NOT E6510) https://bugs.launchpad.net/bugs/561802 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
in 2.6.36 64 bit maverick, I confirm that the touchpad is broken: not recognised and usable just as a mouse (moving cursor, tap = click) but no scrolling. -- Alps touchpad is recognized but synaptics clients and scrolling do not work https://bugs.launchpad.net/bugs/550625 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
and I also confirm that psmouse.ko patched above by bagl0312 enables scrolling :) -- Alps touchpad is recognized but synaptics clients and scrolling do not work https://bugs.launchpad.net/bugs/550625 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
it seems to be fixed with a kernel patch, that I don't know how to apply... Waiting for a newer kernel but in the meantime I may try the rc4 that has the patch (had been removed since...) david 2010/10/28 namregzepol namregze...@hotmail.com Same problem here on a dell e5410 i5 with intel graphics. I'm on Ubuntu 1.10 with kernel 2.6.35-22-generic and i got black screen after installing with alternate. I don't have a docking so i cannot try. I've tried xforcevesa and i915.modeset=0 as kernel parameters in grub with no luck. This way it show me console with an error telling 'failed to get i915 symbols, graphics turbo disabled. Is the same bug or i must report it in other one? If it's the same, what else can i try? -- [i915] blank screen on Latitude E6410 (NOT E6510) https://bugs.launchpad.net/bugs/561802 You received this bug notification because you are a direct subscriber of the bug. -- [i915] blank screen on Latitude E6410 (NOT E6510) https://bugs.launchpad.net/bugs/561802 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
and re-correction . . ; It's not working systematically What I do when I choose the kernel in grub is the following : I get a message about symbols missing... and one about the sd card reader... at this point I hammer Fn + F8, which is to switch external/internal monitor... I get on each press, then there is a message about i915, at which point my Fn + F8 shows ^P instead... I continue pressing, the screen goes blank, changes resolution then most of the time the same information reappears. This is good, my monitor is active. Sometimes it stays blank, so I power off and try again. it mostly works. Now, with a docking station and external monitor, most of the time it displays the normal screen on both monitors. Sometimes the internal monitor is off, so I press ALT+E when I see KDM is started, to restart X server. This works. Is there any more info/tests I can give anyone? -- [i915] blank screen on Latitude E6410 (NOT E6510) https://bugs.launchpad.net/bugs/561802 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
and I just find that file and (backup/)replace it with yours ? -- Alps touchpad is recognized but synaptics clients and scrolling do not work https://bugs.launchpad.net/bugs/550625 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
after...@tranquility:/lib/modules/2.6.36-020636rc8-generic/kernel/drivers/input/mouse$ sudo modprobe psmouse FATAL: Error inserting psmouse (/lib/modules/2.6.36-020636rc8-generic/kernel/drivers/input/mouse/psmouse.ko): Invalid module format Fixable? or not compatible with this kernel ? -- Alps touchpad is recognized but synaptics clients and scrolling do not work https://bugs.launchpad.net/bugs/550625 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
New information : booted up when plugged into Dell docking station, same behaviour as noted in bug (no laptop display, but external working fine) I also read that creating an xorg.conf and changing the Monitor section to this could help : Section Monitor IdentifierMonitor0 OptionDPMS HorizSync 30-96 VertRefresh 50-160 EndSection I tried this and rebooted PC still no laptop monitor display. I then opened KDE System Settings to see what screens/monitors were discovered or available . HDMI1 and DP1 were both affected to the external monitor. At this point, with the tool open, I undocked the PC. This must have tickled something somewhere because my laptop screen became active. I then replugged back into the docking station, and now I am writing from the Dell in question, with multiple monitor setup. both screens working, as an extended display. Its not a fix, but its working :) lspci - [code] 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) 00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 05) 00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05) 00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05) 00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 05) 00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 05) 00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5) 00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05) 00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05) 02:00.0 Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01) 03:00.0 CardBus bridge: Ricoh Co Ltd Device e476 (rev 02) 03:00.1 SD Host controller: Ricoh Co Ltd Device e822 (rev 03) 03:00.4 FireWire (IEEE 1394): Ricoh Co Ltd Device e832 (rev 03) 3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02) 3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02) 3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02) 3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02) 3f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02) 3f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02) [/code] I'm all ears for more testing... as this makes it easier to recover the display (work hours only though :) ) david -- [i915] blank screen on Latitude E6410 (NOT E6510) https://bugs.launchpad.net/bugs/561802 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
correction.. internal screen only comes back when i clip the dell back into the docking station -- [i915] blank screen on Latitude E6410 (NOT E6510) https://bugs.launchpad.net/bugs/561802 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
and finally (spamming as I go, sorry all :) ) i've just installed from kernel.ubuntu.com kernel version 2.6.36-rc7. When in docking station, defaults to external monitor. When disconnected, laptop mode by default... I have a nice working X screen :) yay !! -- [i915] blank screen on Latitude E6410 (NOT E6510) https://bugs.launchpad.net/bugs/561802 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561802] Re: [i915] blank screen on Latitude E6410 (NOT E6510)
Hi, I have a Dell E6410with intel i915 gfx chip. I have same issue after release of 10.10 kubuntu and updated kernel (2.6.35-22-generic) Release 10.04.1 did same, as did most recent updates using 64 bit all the way... when I specify nomodeset xforcevesa by editing grub on boot, I drop to console without, I boot to black, but when I plug in an external monitor I have a display. shame we didnt get a workaround into 10.10 release... :/ (not a criticism ;) ) I'm open to test if anyone has any suggestions David -- [i915] blank screen on Latitude E6410 (NOT E6510) https://bugs.launchpad.net/bugs/561802 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 422536] Re: EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded.
errr Dave, post #238 : i think I am in this case here's my dmesg as of 10 minutes ago . . . Linux version 2.6.31-20-generic (bui...@yellow) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu9) ) #57-Ubuntu ** Attachment added: karmic latest kernel :Linux version 2.6.31-20-generic (bui...@yellow) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu9) ) #57-Ubuntu http://launchpadlibrarian.net/38902858/dmesg.txt -- EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded. https://bugs.launchpad.net/bugs/422536 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 419054] Re: kdeinit4: plasma-desktop takes 60-90% of CPU
i have same issue on karmic. top shows these . . . 2173 aftertaf 22 2 359m 59m 27m R 46.9 3.0 3:01.18 plasma-desktop 1107 root 20 0 123m 39m 8016 R 21.5 2.0 1:56.79 Xorg 2167 aftertaf 20 0 286m 43m 20m R 8.9 2.2 0:41.93 kwin 67% of CPU, with nothing running . . . . I have no *exotic* plasmoid-widget-applets. Same thing, changing desktop settings, playing around with the system tray notification popup settings etc, brings it down to reasonable levels (until it triggers again . . . . for reasons unknown) PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 2217 aftertaf 20 0 166m 37m 21m S 5.3 1.9 0:15.94 yakuake 1107 root 20 0 137m 44m 8384 S 5.0 2.2 2:55.35 Xorg 2167 aftertaf 20 0 288m 45m 20m S 1.3 2.2 1:01.44 kwin 2173 aftertaf 22 2 365m 67m 29m S 0.7 3.4 4:44.02 plasma-desktop -- kdeinit4: plasma-desktop takes 60-90% of CPU https://bugs.launchpad.net/bugs/419054 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 429864] Re: X server nvidia crashes on startup
*** This bug is a duplicate of bug 429003 *** https://bugs.launchpad.net/bugs/429003 ** This bug has been marked a duplicate of bug 429003 [karmic] Xorg (and anything GLX) crashes on startup ** Changed in: rosetta Status: New = Fix Released -- X server nvidia crashes on startup https://bugs.launchpad.net/bugs/429864 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu (via bug 429003). -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 429003] Re: [karmic] Xorg (and anything GLX) crashes on startup
with -185 driver working ok now too. libc version-12 is good for me too :) thanks all -- [karmic] Xorg (and anything GLX) crashes on startup https://bugs.launchpad.net/bugs/429003 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 331750] Re: Nvclock crash (*** stack smashing detected ***)
Would like to open bug again for karmic koala. 0.8 beta4 in shell says cant find /dev/nvidia0, and both _qt and _gtk version core dump/seg fault. this is since update to karmic, using -185 nvidia drivers from repositories. lspci: 01:00.0 VGA compatible controller: nVidia Corporation NV40 [GeForce 6800] (rev a1) -- Nvclock crash (*** stack smashing detected ***) https://bugs.launchpad.net/bugs/331750 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 401689] [NEW] linuxvnc in console mode crashes randomly
Public bug reported: I have a bootable kubuntu 9.04 installed on a usb key. I use tty1 with a startup script in /etc/init.d/ to launch a text based menu and perform different actions. linuxvnc version installed : 0.9.3.dfsg.1-1ubuntu2 This may be done at a distance so for debugging and remote assistance I have included the linuxvnc package to have 'console-mode' vnc on tty1. I launch vnc in this manner in my script linuxvnc 1 Sometimes, after a screen refresh or something, the vnc server crashes : I can see the following error message with dmesg: linuxvnc[pid]: segfault at b7c87b70 ip b7d458aa sp bfb186fc error 6 in libc-2.9.so[b7ccc000+15c000] Maybe my way of launching isn't clean, I should run it as an isolated init.d script maybe? However this doesn't explain or fix the actual crashing. also, if i rerun the linuxvnc 1 command, it segfaults directly, so I cant even make it respawn if terminated... ** Affects: libvncserver (Ubuntu) Importance: Undecided Status: New ** Tags: libc linuxvnc vnc ** Description changed: I have a bootable kubuntu 9.04 installed on a usb key. I use tty1 with a startup script in /etc/init.d/ to launch a text based menu and perform different actions. + + linuxvnc version installed : 0.9.3.dfsg.1-1ubuntu2 This may be done at a distance so for debugging and remote assistance I have included the linuxvnc package to have 'console-mode' vnc on tty1. I launch vnc in this manner in my script linuxvnc 1 Sometimes, after a screen refresh or something, the vnc server crashes : I can see the following error message with dmesg: linuxvnc[pid]: segfault at b7c87b70 ip b7d458aa sp bfb186fc error 6 in libc-2.9.so[b7ccc000+15c000] Maybe my way of launching isn't clean, I should run it as an isolated init.d script maybe? However this doesn't explain or fix the actual crashing. also, if i rerun the linuxvnc 1 command, it segfaults directly, so I cant even make it respawn if terminated... -- linuxvnc in console mode crashes randomly https://bugs.launchpad.net/bugs/401689 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 112984] Re: Odd folder or file names cause amarok to incorrectly log duplicate entires in the collection database
for me, no... i still have some non conventional folder/filenames (from linux p.o.v) and 2.0.1 is cokking on gas :) crashed the copy to media devices sometimes (too long names it seems...) but I think even that is now ok. :) keep it coming!!! 2009/3/30 Jonathan Thomas echidna...@kubuntu.org Is this still a problem in Amarok 2.0.1? ** Changed in: amarok (Ubuntu) Status: Confirmed = Incomplete -- Odd folder or file names cause amarok to incorrectly log duplicate entires in the collection database https://bugs.launchpad.net/bugs/112984 You received this bug notification because you are a direct subscriber of the bug. -- Odd folder or file names cause amarok to incorrectly log duplicate entires in the collection database https://bugs.launchpad.net/bugs/112984 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to amarok in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 302026] Re: likewise-open prevents local passwords from being changed
I confirm this bug on kubuntu 8.10 and on current jaunty (as of today's date). I didnt realise it was due to likewise install 1) After editing the common-password file i was able to change passwords fine :) 2) I have also installed libpam-cracklib to make sure a new update doesn't recreate the problem thanks for the pointers ;) -- likewise-open prevents local passwords from being changed https://bugs.launchpad.net/bugs/302026 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to likewise-open in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 302026] Re: likewise-open prevents local passwords from being changed
I confirm this bug on kubuntu 8.10 and on current jaunty (as of today's date). I didnt realise it was due to likewise install 1) After editing the common-password file i was able to change passwords fine :) 2) I have also installed libpam-cracklib to make sure a new update doesn't recreate the problem thanks for the pointers ;) -- likewise-open prevents local passwords from being changed https://bugs.launchpad.net/bugs/302026 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 141005] Re: kopete auto connect don't work in gutsy
not present any more :) thanks :) 2009/1/7 Jonathan Thomas echidna...@kubuntu.org Is this bug still present in Intrepid? ** Changed in: kdenetwork (Ubuntu) Status: Confirmed = Incomplete -- kopete auto connect don't work in gutsy https://bugs.launchpad.net/bugs/141005 You received this bug notification because you are a direct subscriber of the bug. -- kopete auto connect don't work in gutsy https://bugs.launchpad.net/bugs/141005 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdenetwork in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 261433] Re: ipw2200 module can not be loaded after upgrade to kernel 2.6.24-21
I hate to disagree, but I have this or a similar problem with ipw2200 on intrepid. I'll write a new bug. -- ipw2200 module can not be loaded after upgrade to kernel 2.6.24-21 https://bugs.launchpad.net/bugs/261433 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 312656] [NEW] ipw2200 wireless symbol errors
Public bug reported: Kubuntu version 8.10 Wireless is broken on my IBM T43 Thinkpad, not sure since when, as used mostly with eth0 at office. i have booted to older kernel and using different iwconfig commands, was able to bring up the wifi... OK with : Linux version 2.6.24-19-generic (bui...@terranova) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed Aug 20 22:56:21 UTC 2008 (Ubuntu 2.6.24-19.41-generic) iwconfig: sudo iwconfig eth1 essid myessid sudo iwconfig eth1 ap any sudo iwconfig eth1 key MYHEXKEY my /etc/network/interfaces: da...@akf5573:~$ cat /etc/network/interfaces auto lo iface lo inet loopback auto eth1 iface eth1 inet dhcp essid mySSID key MYKEY restricted modules on working kernel: apt-cache policy linux-restricted-modules linux-restricted-modules: Installed: 2.6.27.11.14 Candidate: 2.6.27.11.14 Version table: *** 2.6.27.11.14 0 500 http://archive.ubuntu.com intrepid-proposed/restricted Packages 100 /var/lib/dpkg/status 2.6.27.9.13 0 500 http://archive.ubuntu.com intrepid-updates/restricted Packages 500 http://security.ubuntu.com intrepid-security/restricted Packages 2.6.27.7.11 0 500 http://archive.ubuntu.com intrepid/restricted Packages NOK with : Linux version 2.6.27-11-generic (bui...@palmer) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Fri Dec 19 16:29:52 UTC 2008 (Ubuntu 2.6.27-11.22-generic) same with 27-10 still installed too . . . . restricted-modules: dpkg -l | grep linux-rest | grep 27 ii linux-restricted-modules 2.6.27.11.14 Generic Linux restricted modules. ii linux-restricted-modules-2.6.27-10-generic 2.6.27-10.14 Non-free Linux kernel modules for version 2.6.27 on x86/ ii linux-restricted-modules-2.6.27-11-generic 2.6.27-11.15 Non-free Linux kernel modules for version 2.6.27 on x86/ ii linux-restricted-modules-common2.6.27-11.15 Non-free Linux 2.6.27 modules helper script ii linux-restricted-modules-generic 2.6.27.11.14 Restricted Linux modules for generic kernels removing ipw2200 and modprobing it shows this in dmesg logs: modprobe ipw2200 : [ 20.262055] ipw2200: disagrees about version of symbol ieee80211_wx_get_encodeext [ 20.262061] ipw2200: Unknown symbol ieee80211_wx_get_encodeext [ 20.262415] ipw2200: disagrees about version of symbol ieee80211_wx_set_encode [ 20.262418] ipw2200: Unknown symbol ieee80211_wx_set_encode [ 20.262505] ipw2200: disagrees about version of symbol ieee80211_wx_get_encode [ 20.262507] ipw2200: Unknown symbol ieee80211_wx_get_encode [ 20.262858] ipw2200: disagrees about version of symbol ieee80211_txb_free [ 20.262861] ipw2200: Unknown symbol ieee80211_txb_free [ 20.263008] ipw2200: disagrees about version of symbol ieee80211_wx_set_encodeext [ 20.263011] ipw2200: Unknown symbol ieee80211_wx_set_encodeext [ 20.263459] ipw2200: disagrees about version of symbol ieee80211_wx_get_scan [ 20.263461] ipw2200: Unknown symbol ieee80211_wx_get_scan [ 20.263646] ipw2200: disagrees about version of symbol ieee80211_freq_to_channel [ 20.263649] ipw2200: Unknown symbol ieee80211_freq_to_channel [ 20.264209] ipw2200: disagrees about version of symbol ieee80211_set_geo [ 20.264211] ipw2200: Unknown symbol ieee80211_set_geo [ 20.264665] ipw2200: disagrees about version of symbol ieee80211_rx [ 20.264667] ipw2200: Unknown symbol ieee80211_rx [ 20.264949] ipw2200: disagrees about version of symbol ieee80211_channel_to_index [ 20.264951] ipw2200: Unknown symbol ieee80211_channel_to_index [ 20.265610] ipw2200: disagrees about version of symbol ieee80211_rx_mgt [ 20.265612] ipw2200: Unknown symbol ieee80211_rx_mgt [ 20.265700] ipw2200: disagrees about version of symbol ieee80211_get_geo [ 20.265702] ipw2200: Unknown symbol ieee80211_get_geo [ 20.265868] ipw2200: disagrees about version of symbol free_ieee80211 [ 20.265870] ipw2200: Unknown symbol free_ieee80211 [ 20.266354] ipw2200: disagrees about version of symbol ieee80211_is_valid_channel [ 20.266356] ipw2200: Unknown symbol ieee80211_is_valid_channel [ 20.266581] ipw2200: disagrees about version of symbol alloc_ieee80211 [ 20.266583] ipw2200: Unknown symbol alloc_ieee80211 [ 1420.307064] ipw2200: disagrees about version of symbol ieee80211_wx_get_encodeext [ 1420.307078] ipw2200: Unknown symbol ieee80211_wx_get_encodeext [ 1420.307926] ipw2200: disagrees about version of symbol ieee80211_wx_set_encode [ 1420.307932] ipw2200: Unknown symbol ieee80211_wx_set_encode [ 1420.308171] ipw2200: disagrees about version of symbol ieee80211_wx_get_encode [ 1420.308177] ipw2200: Unknown symbol ieee80211_wx_get_encode [ 1420.309017] ipw2200: disagrees about version of symbol ieee80211_txb_free [ 1420.309023] ipw2200: Unknown symbol ieee80211_txb_free [
[Bug 312656] Re: ipw2200 wireless symbol errors
** Attachment added: lsp_txt http://launchpadlibrarian.net/20826422/lsp_txt -- ipw2200 wireless symbol errors https://bugs.launchpad.net/bugs/312656 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 312656] Re: ipw2200 wireless symbol errors
update... duh... :) i checked my installed packages and did a locate for ipw2200 . . . . I had the latest backports modules also installed. removed them and rebooted to 27-11 . . module now loaded ok. still have to invoke Wifi with iwconfig though :( ** Summary changed: - ipw2200 wireless symbol errors + ipw2200 wireless symbol errors with backports modules (intrepid) ** Tags added: backports intel intrepid wireless -- ipw2200 wireless symbol errors with backports modules (intrepid) https://bugs.launchpad.net/bugs/312656 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 270043] Re: intrepid - rm: cannot remove `md0-': Read-only file system
I have exact same error on install and also dpkg-reconfigure of mdadm on a fresh kubuntu 8.10 32 bit. I want to use it to 'mount' as RAID an existing RAID 1 fakeraid with Windows installed on it... -- intrepid - rm: cannot remove `md0-': Read-only file system https://bugs.launchpad.net/bugs/270043 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 267072] Re: Unable to move and/or resize KMM on Ubuntu 8.10 Alpha 5
Hi, the main window is too large to fit on a 1024*768 screen and i cannot resize it to shrink it down... Using kubuntu on KDE4: some kde3 remains on my system but most is gone with the upgrade to intrepid... Since the change to kde4 and the new version 0.9 of KMM, i have this problem And with compiz activated it makes the window jump all over the place making the app unuseable... about to see if i can remove the remaining few kde3 packages and see if it works better with pure kde4 (if it can) ---depends on kdelibs4c2a and kdelibs-data : both in version 4:3.5.10-0ubuntu6 ---half of kde apps still installed also dependant :( -- Unable to move and/or resize KMM on Ubuntu 8.10 Alpha 5 https://bugs.launchpad.net/bugs/267072 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 115702] Re: arrow keys and nav keys do not work
Intrepid beta on thinkpadT43 with KDE4 Upgraded from fresh hardy install. The left arrow no longer works in X, but it works in KDM ~/.Xmodmap has this: keycode 113 = Mode_switch I don't know how it got there :) put a # in front of it and all is good i can make typing mistakes again and correct them without complicated manoeuvres -- arrow keys and nav keys do not work https://bugs.launchpad.net/bugs/115702 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 270626] Re: libc6 update fails: stack smashing detected
I confirm the workaround above... modify the debconf/frontend to use Dialog instead of KDE and this enables a dpkg -i to work: 1st try without change: [EMAIL PROTECTED]:/# dpkg -i /var/cache/apt/archives/debconf_1.5.23ubuntu1_all.deb (Reading database ... 273978 files and directories currently installed.) Preparing to replace debconf 1.5.23ubuntu1 (using .../debconf_1.5.23ubuntu1_all.deb) ... Unpacking replacement debconf ... Setting up debconf (1.5.23ubuntu1) ... *** stack smashing detected ***: /usr/bin/perl terminated dpkg: error processing debconf (--install): subprocess post-installation script killed by signal (Segmentation fault) Errors were encountered while processing: debconf Here I followed the fix mentioned above: [EMAIL PROTECTED]:/# vim /var/cache/debconf/config.dat And 2nd try for installing debconf: [EMAIL PROTECTED]:/# dpkg -i /var/cache/apt/archives/debconf_1.5.23ubuntu1_all.deb (Reading database ... 273978 files and directories currently installed.) Preparing to replace debconf 1.5.23ubuntu1 (using .../debconf_1.5.23ubuntu1_all.deb) ... Unpacking replacement debconf ... Setting up debconf (1.5.23ubuntu1) ... Now i hope the beta of intrepid will install, because a lot of dependencies were stuck with this same error or because of packages concerned. 79 upgraded, 67 newly installed, 3 to remove and 62 not upgraded. 1272 not fully installed or removed. Need to get 0B/75.2MB of archives. After this operation, 193MB of additional disk space will be used. Do you want to continue [Y/n]? Say YES !!! :) -- libc6 update fails: stack smashing detected https://bugs.launchpad.net/bugs/270626 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 141005] Re: kopete auto connect don't work in gutsy or hardy
still present on 18/05/2007 with all latest updates applied in hardy -- kopete auto connect don't work in gutsy https://bugs.launchpad.net/bugs/141005 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 141005] Re: kopete auto connect don't work in gutsy
ok ill try and let you know. 2008/5/14 mcas [EMAIL PROTECTED]: Thank you for reporting this bug. Due to your comments i mark this bug as confirmed. Can you please try the newer Version of ubuntu /kopete to see if the bug is still there. ** Changed in: kopete (Ubuntu) Status: New = Confirmed -- kopete auto connect don't work in gutsy https://bugs.launchpad.net/bugs/141005 You received this bug notification because you are a direct subscriber of the bug. ** Attachment added: unnamed http://launchpadlibrarian.net/14521212/unnamed -- kopete auto connect don't work in gutsy https://bugs.launchpad.net/bugs/141005 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112984] Re: Odd folder or file names cause amarok to incorrectly log duplicate entires in the collection database
I have this problem too... with just about any album or group with a Space in the name... I ditched MySQL and 'removed' my comemction this way, then redeclared it. It rebuilt from scratch but duplicates are still there. All is on a local drive, ext3. I also note that amarok uses a lot more of processor than before, i'm not using equalisers, visualisation or moodbar... Just listening to music: amarok is always updating the collection though nothing has changed in the files structure or anything. -- Odd folder or file names cause amarok to incorrectly log duplicate entires in the collection database https://bugs.launchpad.net/bugs/112984 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112984] Re: Odd folder or file names cause amarok to incorrectly log duplicate entires in the collection database
duh, i meant SQLite, not mysql just deleted the .kde/share/apps/amarok/collection* files too and am rescanning to see if it works. (reticking which folders have the files i want...) I confirm the changing of db engine to force a rescan didn't fix it, the original file must have remained... will tell you if this is a lasting fix -- Odd folder or file names cause amarok to incorrectly log duplicate entires in the collection database https://bugs.launchpad.net/bugs/112984 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112984] Re: Odd folder or file names cause amarok to incorrectly log duplicate entires in the collection database
anyone know if this is a cause or not for amarok to use a lot of cpu? maybe due to excessive collection scanning? -- Odd folder or file names cause amarok to incorrectly log duplicate entires in the collection database https://bugs.launchpad.net/bugs/112984 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204357] Re: locate reports locate: can not open `/var/lib/mlocate/mlocate.db': No such file or directory
mlocate replaced by slocate . . and I didnt reboot once the change applied :) i dont like rebooting linux :) ** Changed in: mlocate (Ubuntu) Status: New = Invalid -- locate reports locate: can not open `/var/lib/mlocate/mlocate.db': No such file or directory https://bugs.launchpad.net/bugs/204357 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 206396] [NEW] kopete with meanwhile sametime protocol can't handle accents
Public bug reported: Binary package hint: kopete In all versions since feisty... I have the same behaviour.. in current kopete in hardy I use kubuntu in english language, setup for use in France. I have an azerty keyboard. When I send messages to sametime contacts if i use an accent ( é, à, ç, è ) the whole message I sent is badly handled . . . the receiver only gets an empty line in his chat window. And when someone sends me a message with an accent, i get @# type of characters instead of the letter with an accent... Is it kopete, or the meanwhile wrapper for sametime? how can I give you more information to help? ** Affects: kopete (Ubuntu) Importance: Undecided Status: New -- kopete with meanwhile sametime protocol can't handle accents https://bugs.launchpad.net/bugs/206396 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 204357] Re: locate reports locate: can not open `/var/lib/mlocate/mlocate.db': No such file or directory
hmmm. it works now. sorry :) 2008/3/23, Lars L [EMAIL PROTECTED]: Did you make sure that /etc/cron.daily/mlocate had been run at least once? -- locate reports locate: can not open `/var/lib/mlocate/mlocate.db': No such file or directory https://bugs.launchpad.net/bugs/204357 You received this bug notification because you are a direct subscriber of the bug. -- locate reports locate: can not open `/var/lib/mlocate/mlocate.db': No such file or directory https://bugs.launchpad.net/bugs/204357 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 141005] Re: kopete auto connect don't work in gutsy
i looked how pidgin connects, it overrides the default server settings and specifies the host also used in kopete... So i ticked the 'override' setting and managed to force a connection. When I send a message I dont get the error saying message not sent. -- kopete auto connect don't work in gutsy https://bugs.launchpad.net/bugs/141005 You received this bug notification because you are a member of Kubuntu Team, which is subscribed to kopete in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 141005] Re: kopete auto connect don't work in gutsy
correction when i start chat I get: : The following message has not been sent correctly (Connection closed): in kopete and in the console . . . kopete: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file jabberchatui.rc QFont::setPointSize: Point size = 0 (-1) QFont::setPointSize: Point size = 0 (-1) QObject::connect: No such signal JabberChatSession::typing(bool) QObject::connect: (sender name: 'editPart') QObject::connect: (receiver name: 'unnamed') libkopete: WARNING: Failed to cast view to QObject * kopete: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file jabberchatui.rc QFont::setPointSize: Point size = 0 (-1) QFont::setPointSize: Point size = 0 (-1) QObject::connect: No such signal JabberChatSession::typing(bool) QObject::connect: (sender name: 'editPart') QObject::connect: (receiver name: 'unnamed') libkopete: WARNING: Failed to cast view to QObject * QFont::setPointSize: Point size = 0 (-1) QFont::setPointSize: Point size = 0 (-1) -- kopete auto connect don't work in gutsy https://bugs.launchpad.net/bugs/141005 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 141005] Re: kopete auto connect don't work in gutsy
I confirm this bug is still present +1 I have just modified the connection section for my MSN account, changed it to HTTP method. Though I ran it from console, I have no other messages than the remote host one. I just sent a test message to a contact marked as Away, and the following logs were shown in the console... ection) KPopupMenu: title() called with non-title id 0. QObject::connect: No such slot MSNContact::slotWebcamReceive() QObject::connect: (sender name: 'msnWebcamReceive') QObject::connect: (receiver name: 'unnamed') QObject::connect: No such slot MSNContact::slotWebcamSend() QObject::connect: (sender name: 'msnWebcamSend') QObject::connect: (receiver name: 'unnamed') QFont::setPointSize: Point size = 0 (-1) QObject::connect: No such signal MSNChatSession::typing(bool) QObject::connect: (sender name: 'editPart') QObject::connect: (receiver name: 'unnamed') libkopete: WARNING: Failed to cast view to QObject * apart from that, I remained connected, though noone to talk to in order to check this . . . :) -- kopete auto connect don't work in gutsy https://bugs.launchpad.net/bugs/141005 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200154] Re: System freeze when selected automount on media device
Hardy Kubuntu up to date as of yesterday (19/3/08) I did same . . . I was running amarok too. But not an iPod, a usk disk was plugged in Amarok ran to the end of the current song then stopped, which made me notice a problem. No system response at all X wise, I had to Alt-F1. I tried my user account password, no login possible (hung where normally prompt appears). So i used root, which logged ok. ran top and 95.5% cpu was kdedkillall -9 kded brought everything back immediately. heres my dmesg : 934.895162] usb 4-6: new high speed USB device using ehci_hcd and address 4 [ 935.031297] usb 4-6: configuration #1 chosen from 1 choice [ 935.143745] usbcore: registered new interface driver libusual [ 935.201717] Initializing USB Mass Storage driver... [ 935.205116] scsi2 : SCSI emulation for USB Mass Storage devices [ 935.211319] usbcore: registered new interface driver usb-storage [ 935.211328] USB Mass Storage support registered. [ 935.212866] usb-storage: device found at 4 [ 935.212871] usb-storage: waiting for device to settle before scanning [ 940.202388] usb-storage: device scan complete [ 940.203152] scsi 2:0:0:0: Direct-Access USB DISK 28X PMAP PQ: 0 ANSI: 0 CCS [ 941.110456] sd 2:0:0:0: [sdb] 4030464 512-byte hardware sectors (2064 MB) [ 941.111454] sd 2:0:0:0: [sdb] Write Protect is off [ 941.111458] sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00 [ 941.111461] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 941.113824] sd 2:0:0:0: [sdb] 4030464 512-byte hardware sectors (2064 MB) [ 941.114449] sd 2:0:0:0: [sdb] Write Protect is off [ 941.114453] sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00 [ 941.114456] sd 2:0:0:0: [sdb] Assuming drive cache: write through [ 941.114463] sdb: sdb1 [ 941.115537] sd 2:0:0:0: [sdb] Attached SCSI removable disk [ 941.115594] sd 2:0:0:0: Attached scsi generic sg2 type 0 cant see anything unusual . . . -- System freeze when selected automount on media device https://bugs.launchpad.net/bugs/200154 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200154] Re: System freeze when selected automount on media device
forgot to say running kde3. -- System freeze when selected automount on media device https://bugs.launchpad.net/bugs/200154 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 196005] Re: kded halts on usb flash inserted
*** This bug is a duplicate of bug 194474 *** https://bugs.launchpad.net/bugs/194474 afaik, duplicate of other bug. I have same problem, just posted in other bug If any other logs etc can help just ask, i'll do the experiment again if needed. ** This bug has been marked a duplicate of bug 200154 System freeze when selected automount on media device -- kded halts on usb flash inserted https://bugs.launchpad.net/bugs/196005 You received this bug notification because you are a member of Kubuntu Team, which is subscribed to kdelibs in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 196005] Re: kded halts on usb flash inserted
*** This bug is a duplicate of bug 194474 *** https://bugs.launchpad.net/bugs/194474 ** This bug is no longer a duplicate of bug 200154 System freeze when selected automount on media device ** This bug has been marked a duplicate of bug 194474 [hardy] kded in loop (100%CPU) when using 'mount automatically' -- kded halts on usb flash inserted https://bugs.launchpad.net/bugs/196005 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200154] Re: System freeze when selected automount on media device
*** This bug is a duplicate of bug 194474 *** https://bugs.launchpad.net/bugs/194474 ** This bug has been marked a duplicate of bug 194474 [hardy] kded in loop (100%CPU) when using 'mount automatically' -- System freeze when selected automount on media device https://bugs.launchpad.net/bugs/200154 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 203526] Re: python-wxgtk2.8 uninstallable due to post-installation script error
Adrien, I confirm that sudo sed -i '/^\/usr\/lib\/python2.[4,5]\/site-packages\/wxaddons.*/d' /usr/share/pyshared-data/python-wxgtk2.8 works fine... though I know you know that :) -- python-wxgtk2.8 uninstallable due to post-installation script error https://bugs.launchpad.net/bugs/203526 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204357] [NEW] locate reports locate: can not open `/var/lib/mlocate/mlocate.db': No such file or directory
Public bug reported: Binary package hint: mlocate I'm not sure which one of these is the culprit (though I strongly suspect MLOCATE when I see the output error message . . . ___ [EMAIL PROTECTED]:/$ dpkg -l | grep locate ii kio-locate 0.4.5-0ubuntu2 kio-slave for the locate command ii mlocate0.18-2ubuntu1 quickly find files on the filesystem based o ii slocate3.1-1.1ubuntu3 Secure replacement of findutil's locate When i type locate, as user or with sudo, I get the following message: [EMAIL PROTECTED]:/$ sudo locate david* locate: can not open `/var/lib/mlocate/mlocate.db': No such file or directory release: ubuntu hardy, dist-upgraded 20/03/2008 @ 18h00 CET ** Affects: mlocate (Ubuntu) Importance: Undecided Status: New -- locate reports locate: can not open `/var/lib/mlocate/mlocate.db': No such file or directory https://bugs.launchpad.net/bugs/204357 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 202670] Re: [nvidia-glx-new] Nvidia restricted driver locks system with xserver launch
i use nvidia-glx . . . i dont have this bug, but I confirm that on upgrade to the version below of kernel, i lose nvidia driver unless I do the following ___ I'm using 2.6.24-12-generic upgraded from feisty fresh install to hardy dev version (as of todays versions). Same here, no nvidia. I followed the instructions on removing packages on page 1... in synaptic i removed with config also: nvidia-glx 1:96.43.05+2.6.24.11-12.31 linux-restricted-modules-generic 2.6.24.12.13 linux-image-2.6.24-12-generic 2.6.24-12.22 along with their 'virtual' dependencies. Then, I reinstalled directly, no reboot xorg had been changed to 'nvidia' in driver section so i rebooted, i got nvidia logo and normal accelerated X -- [nvidia-glx-new] Nvidia restricted driver locks system with xserver launch https://bugs.launchpad.net/bugs/202670 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 156127] Re: DMA not activated, not permitted
Hi, when I wrote that, it seemed clear to me . . . Basically, was having problems with all recent kernels from feisty upwards: since then, i've reinstalled on a sata drive, and problem no longer exists... So, hard to give more info. But, IIRC, my issue was the same as this google search shows http://www.google.fr/search?hl=enclient=firefox-arls=org.mozilla%3Afr%3Aofficialhs=B0gq=dropping+to+busybox+ubuntu+live+cdbtnG=Search And i found a lot of info in posts from Ben Collins about the fixes possible... Hope that helps... and not sure, therefore, if its fixed... If not, sure someone who knows VERY well debian based systems will be able to give 'useful' info... Thanks, and good work. Serious :D 2008/3/19, Andrew Ash [EMAIL PROTECTED]: I'm not quite sure what the issue is that you're having, aftertaf. If it's still a problem, could you please provide a more thorough description of what you're experiencing? Thanks ** Changed in: ubuntu Status: New = Incomplete -- DMA not activated, not permitted https://bugs.launchpad.net/bugs/156127 You received this bug notification because you are a direct subscriber of the bug. -- DMA not activated, not permitted https://bugs.launchpad.net/bugs/156127 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 156127] Re: DMA not activated, not permitted
no pb :) i think there are duplicates in launchpad anyway, so someone will have done something :) 2008/3/19, Andrew Ash [EMAIL PROTECTED]: I don't think I know enough about debian systems to help you here, and with your system switched to the SATA drive now it will be hard for you to give more info. I'm going to go ahead and close the bug then, but if it starts causing you trouble again, please open it back up. Thanks! ** Changed in: ubuntu Status: Incomplete = Invalid -- DMA not activated, not permitted https://bugs.launchpad.net/bugs/156127 You received this bug notification because you are a direct subscriber of the bug. -- DMA not activated, not permitted https://bugs.launchpad.net/bugs/156127 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 150859] Re: Prism Wifi connection losing packets and being slow
no probs :) thanks for the good tip ;) 2008/3/17, Caroline Ford [EMAIL PROTECTED]: Thanks for getting back to us! I'll close this bug now :) ** Changed in: linux-source-2.6.22 (Ubuntu) Status: Incomplete = Invalid -- Prism Wifi connection losing packets and being slow https://bugs.launchpad.net/bugs/150859 You received this bug notification because you are a direct subscriber of the bug. -- Prism Wifi connection losing packets and being slow https://bugs.launchpad.net/bugs/150859 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 150859] Re: Prism Wifi connection losing packets and being slow
not sure which is better way t report it, but the bug seemes gone. i have a constant reliable bandwidth and am happy with it :) thanks david 2008/3/7, Caroline Ford [EMAIL PROTECTED]: The Hardy Heron Alpha series is currently under development and contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . You should be able to test the new kernel using the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ . Thanks. ** Changed in: linux-restricted-modules-2.6.22 (Ubuntu) Status: New = Invalid ** Changed in: linux-source-2.6.22 (Ubuntu) Status: New = Incomplete -- Prism Wifi connection losing packets and being slow https://bugs.launchpad.net/bugs/150859 You received this bug notification because you are a direct subscriber of the bug. -- Prism Wifi connection losing packets and being slow https://bugs.launchpad.net/bugs/150859 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 150859] Re: Prism Wifi connection losing packets and being slow
I tried yesterday booting to the kernel 2.6.22 (25/01/2008) with all possible updates apt-got... Same symptoms... Downloading goes from 64kb/s to 5000bytes, up and down, up and down . . . . when i reboot to 2.6.20-15: constant 64kb/s ** Also affects: linux-restricted-modules-2.6.22 (Ubuntu) Importance: Undecided Status: New -- Prism Wifi connection losing packets and being slow https://bugs.launchpad.net/bugs/150859 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 150859] Re: Prism Wifi connection losing packets and being slow
when i boot from feisty kernel: 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux --i have this: $ sudo lshw -C network | grep driver | sed 's/ /\n/g' | grep driver= driver=tg3 driver=prism54pci and just lswh -C: *-network:1 description: Wireless interface product: ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] vendor: Intersil Corporation physical id: 9 bus info: [EMAIL PROTECTED]:05:09.0 logical name: wmaster0 version: 01 serial: 00:60:b3:1c:43:26 width: 32 bits clock: 33MHz capabilities: pm bus_master cap_list logical wireless ethernet physical configuration: broadcast=yes driver=prism54pci ip=192.168.0.13 latency=64 maxlatency=28 mingnt=10 module=prism54pci multicast=yes wireless=IEEE 802.11g I'll see what I get with gusty kernel -- Prism Wifi connection losing packets and being slow https://bugs.launchpad.net/bugs/150859 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 156127] DMA not activated, not permitted
Public bug reported: Contents of /etc/initramfs-tools/modules: ___ # egsudo update-initramfs -k 2.6.22-12-generic -c piix ide_generic ide_cd ide_disk # blacklist bad driver blacklist ata_piix # prevent unnecessary modules from being loaded (you don't need to do this) blacklist ata_generic blacklist libata blacklist scsi_mod __ Did this modification to regenerate my initramfs to allow me to boot, otherwise got no root system detected and dropout to busybox with the TTY1 message (found workaround on google) My System: hda/hdb 2 x IDE HDDn hdc IDE DVD Rom burner. I have a SATA controller that I can disable in BIOS, by not granting an IRQ slot to it and this I have done I have this in lsmod concerning chipset: ___ 00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02) 00:01.0 PCI bridge: Intel Corporation 82865G/PE/P PCI to AGP Controller (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2) 00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02) 00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02) 00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02) relevant (i think) part of dmesg output: __ [ 50.764851] checking if image is initramfs... it is [ 51.215975] Switched to high resolution mode on CPU 0 [ 51.422257] Freeing initrd memory: 7119k freed [ 51.422681] audit: initializing netlink socket (disabled) [ 51.422751] audit(1193130505.072:1): initialized [ 51.426053] VFS: Disk quotas dquot_6.5.1 [ 51.426168] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 51.426329] io scheduler noop registered [ 51.426385] io scheduler anticipatory registered [ 51.426440] io scheduler deadline registered [ 51.426510] io scheduler cfq registered (default) [ 51.426636] Boot video device is :01:00.0 [ 51.426819] isapnp: Scanning for PnP cards... [ 51.780404] isapnp: No Plug Play device found [ 51.812653] Real Time Clock Driver v1.12ac [ 51.812805] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled [ 51.814380] RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize [ 51.814678] input: Macintosh mouse button emulation as /class/input/input0 [ 51.814832] PNP: PS/2 Controller [PNP0303:KBD,PNP0f0e:PS2M] at 0x60,0x64 irq 1,12 [ 51.818232] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 51.818296] serio: i8042 AUX port at 0x60,0x64 irq 12 [ 51.818567] mice: PS/2 mouse device common for all mice [ 51.818753] EISA: Probing bus 0 at eisa.0 [ 51.818816] Cannot allocate resource for EISA slot 1 [ 51.818872] Cannot allocate resource for EISA slot 2 [ 51.818961] EISA: Detected 0 cards. [ 51.819120] TCP cubic registered [ 51.819184] NET: Registered protocol family 1 [ 51.819261] Using IPI No-Shortcut mode [ 51.819488] Magic number: 11:769:121 [ 51.820060] Freeing unused kernel memory: 364k freed [ 51.858933] input: AT Translated Set 2 keyboard as /class/input/input1 [ 53.103129] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 [ 53.103137] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx [ 53.103620] Probing IDE interface ide0... [ 53.516267] hda: IC35L060AVVA07-0, ATA DISK drive [ 53.795802] hdb: ST340014A, ATA DISK drive [ 53.851559] Probing IDE interface ide1... [ 54.714279] hdc: DVDRW IDE 16X, ATAPI CD/DVD-ROM drive [ 55.385039] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 [ 55.385067] ide1 at 0x170-0x177,0x376 on irq 15 [ 55.393477] hdc: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache [ 55.393488] Uniform CD-ROM driver Revision: 3.20 [ 55.399527] hda: max request size: 128KiB [ 55.409171] hda: 120103200 sectors (61492 MB) w/1863KiB Cache, CHS=65535/16/63 [ 55.409351] hda: cache flushes supported [ 55.409388] hda: hda1 hda2 hda3 [ 55.414767] hdb: max request size: 128KiB [ 55.414771] hdb: 78165360 sectors (40020 MB) w/2048KiB Cache, CHS=65535/16/63 [ 55.415169] hdb: cache flushes supported [ 55.415190] hdb: hdb1 hdb2 hdb3 hdb4 [ 55.489461] AppArmor: AppArmor initialized5audit(1193130509.072:2): type=1505 info=AppArmor initialized pid=1234 [ 55.496923] fuse init (API version 7.8) [ 55.502273]
[Bug 150859] wifi connection dropping
Public bug reported: System: Kubuntu i386 Fresh feisty upgraded 1st october to gutsy Prism Chipset ISL3890/ISL3886 Kernel: 2.6.22-12-generic (anything else useful?) Since upgrade to gutsy and 2.6.22-12-generic, my Wifi connection is best described as flaky : I have 512b/s ADSL - 64kb download max. And when i apt-get update it can take 30 minutes... i get speeds between 15kb/s and 2000b/s, with no error messages seen anywhere I dont have any messages about the connection dropping, nothing out of the ordinary in dmesg, but when i ping www.google.fr, for example, I get around 20% 50% packet loss, depending on tests... I didnt have this problem before with Feisty, and my ISP is functioning OK. When I plug in the ethernet cable to the router/modem, wifi is dropped and eth0 activated (nice :) ) and i have no loss with pings and I have a constant 64kb download, which rules out an upstream ISP problem. lspci -vv of my card: 05:09.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01) Subsystem: Z-Com, Inc. XG-900 and clones Wireless Adapter Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 64 (2500ns min, 7000ns max), Cache Line Size: 128 bytes Interrupt: pin A routed to IRQ 18 Region 0: Memory at f831 (32-bit, non-prefetchable) [size=8K] Capabilities: [dc] Power Management version 1 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- currently re dist-upgrading since my switch to gutsy last week, so If repaired afer, ill let you know. Otherwise, open to sugestions or how to get you guys more info. David ** Affects: ubuntu Importance: Undecided Status: New ** Tags: connection gutsy prism slow wifi ** Summary changed: - wifi connection dropping + Prism Wifi connection losing packets and being slow ** Tags added: connection gutsy prism slow wifi ** Description changed: - Prism Chipset: - Since upgrade to gutsy and 2.6.22-12-generic, my Wifi connection is best described as flaky : I have 512b/s ADSL - 64kb download max. And when i apt-get update it can take 30 minutes... i get speeds between 15kb/s and 2000b/s, with no error messages seen anywhere + System: Kubuntu i386 Fresh feisty upgraded 1st october to gutsy + Prism Chipset ISL3890/ISL3886 + Kernel: 2.6.22-12-generic + (anything else useful?) + + Since upgrade to gutsy and 2.6.22-12-generic, my Wifi connection is best + described as flaky : I have 512b/s ADSL - 64kb download max. And when i + apt-get update it can take 30 minutes... i get speeds between 15kb/s and + 2000b/s, with no error messages seen anywhere I dont have any messages about the connection dropping, nothing out of the ordinary in dmesg, but when i ping www.google.fr, for example, I get around 20% 50% packet loss, depending on tests... I didnt have this problem before with Feisty, and my ISP is functioning OK. When I plug in the ethernet cable to the router/modem, wifi is dropped and eth0 activated (nice :) ) and i have no loss with pings and I have a constant 64kb download, which rules out an upstream ISP problem. lspci -vv of my card: 05:09.0 Network controller: Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01) Subsystem: Z-Com, Inc. XG-900 and clones Wireless Adapter Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 64 (2500ns min, 7000ns max), Cache Line Size: 128 bytes Interrupt: pin A routed to IRQ 18 Region 0: Memory at f831 (32-bit, non-prefetchable) [size=8K] Capabilities: [dc] Power Management version 1 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- currently re dist-upgrading since my switch to gutsy last week, so If repaired afer, ill let you know. Otherwise, open to sugestions or how to get you guys more info. David -- Prism Wifi connection losing packets and being slow https://bugs.launchpad.net/bugs/150859 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 84964] Re: Crash from ide_pci from generic.ko for jmicron controllers
Hi, Since I switched to Feisty i've had this problem too. I have IDE Drives dvd, and an integrated S-ATA controlller that I do not yet use and cannot deactivate in BIOS. I have not yet tried any of the boot options specified, I will inform you when i test reboot with new kernel. A Question. How can I identify the S-ATA controller chip? other than dmesg with this line: 00:1f.2 IDE interface: Intel Corporation 82801EB (ICH5) SATA Controller (rev 02) Thanks, David -- Crash from ide_pci from generic.ko for jmicron controllers https://launchpad.net/bugs/84964 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
