[Bug 45764] Re: cpufreq does not seem to work on G4 TiBook 667MHz
Not worth it. Probably there's no sane support in the hardware anyway. -- cpufreq does not seem to work on G4 TiBook 667MHz https://bugs.launchpad.net/bugs/45764 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 133786] Re: Bus error when running Firefox or Epiphany
I solved the problem by installing a custom kernel.org 2.6.23.8 kernel. Configured with ubuntu .22 default config as basis but disabled all suspicious new stuff, such as virtualization and tickless. No more XFS filesystem corruption and no more debsums corruption even after apt updates and new installs. I'd say there's a bug in ubuntu's kernel, either in the xfs fs or in something related to cache flushes. -- Bus error when running Firefox or Epiphany https://bugs.launchpad.net/bugs/133786 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 163354] Libquicktime crashes with SIGILL
Public bug reported: For example, lqt_transcode crashes with any task that tries to process audio. This happens on non-SSE2 enabled CPUs because libquicktime has been compiled with SSE2 enabled. At least, quicktime_init_audio_map function uses SSE2 instructions. Please, check the compilation flags and rebuild the binaries. ** Affects: libquicktime (Ubuntu) Importance: Undecided Status: New -- Libquicktime crashes with SIGILL https://bugs.launchpad.net/bugs/163354 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 133786] Re: Bus error when running Firefox or Epiphany
Reinstalling the packages that were reported by debsums to be corrupted fixed the situation so, that debsums doesn't find any corruption anymore. However, after a *clean* reboot to gentoo install cd, and running xfs_check from there for the root filesystem, yet again shows corruption similar to what Richard Ayotte reports above. Before updating anything, the filesystem was xfs_repair'ed and xfs_checked before boot into ubuntu, so, it definitely was ok. -- Bus error when running Firefox or Epiphany https://bugs.launchpad.net/bugs/133786 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 133786] Re: Bus error when running Firefox or Epiphany
Happens here, too. A Duron/VIA box. First boot after fresh 7.10 CD install seemed to work fine, but, after dist-upgrade and boot, things went south. Using XFS filesystems only. Firefox, gnome_terminal, others dying with bus error. Corruption shown by debsums and confirmed at the (root disk) filesystem level by xfs_check from gentoo 2007 CD. Another computer made useless until this is fixed. -- Bus error when running Firefox or Epiphany https://bugs.launchpad.net/bugs/133786 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 153594] Re: Very Slow Boot Up with Feisty on Notebook Computer
...that's on 7.10 release, of course. -- Very Slow Boot Up with Feisty on Notebook Computer https://bugs.launchpad.net/bugs/153594 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 153594] Re: Very Slow Boot Up with Feisty on Notebook Computer
I'm seeing the same on a ThinkPad T30. Boot takes many minutes when splash is enabled, but without splash boots in normal time. The ubuntu splash logo doesn't show up even when splash is enabled - on the install/livecd it does, though. -- Very Slow Boot Up with Feisty on Notebook Computer https://bugs.launchpad.net/bugs/153594 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 47447] Re: 3D screen saver crashes system
Herd-4 seems better, indeed. At least, the livecd does not crash like dapper did. -- 3D screen saver crashes system https://launchpad.net/bugs/47447 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60685] Re: radeonfb fails to probe EDID on a PowerBook G4 (TiBook)
Just upgraded to Edgy using the update-manager. Funnily, the first boot already has the sync issue, so, yes, the issue is still there after upgrade. However, now dmesg looks different: [ 25.211374] radeonfb (:00:10.0): Invalid ROM signature 0 should be 0xaa55 [ 25.211387] radeonfb: Retrieved PLL infos from Open Firmware [ 25.211397] radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=183.00 Mhz, Syst em=230.00 MHz [ 25.211405] radeonfb: PLL min 12000 max 35000 [ 26.145933] radeonfb: Monitor 1 type LCD found [ 26.145940] radeonfb: EDID probed [ 26.145946] radeonfb: Monitor 2 type no found [ 26.145963] radeonfb: Using Firmware dividers 0x0002008e from PPLL 0 [ 26.304930] radeonfb: Dynamic Clock Power Management enabled [ 26.362533] Console: switching to colour frame buffer device 160x53 Note that now it has probed the EDID, whereas the probing previously failed. The syncing isn't completely off, because the picture is there, but shivering - bit like there were two interlaced fields and the other field had a wrong x offset. Previously the problem also varied between good, this almost ok, and completely failed (as best described by the original report .) Second boot: synced ok. Unfortunately, no change in syslog compared to the previous failed attempt. cat /proc/version: Linux version 2.6.17-10-powerpc ([EMAIL PROTECTED]) (gcc version 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)) #2 Fri Oct 13 16:37:41 UTC 2006 (Ubuntu 2.6.17-10.33-powerpc) I don't see this giving any new info, but: cat /proc/cpuinfo: processor : 0 cpu : 7455, altivec supported clock : 667.00MHz revision: 0.1 (pvr 8001 0201) bogomips: 66.56 timebase: 2013 platform: PowerMac machine : PowerBook3,4 motherboard : PowerBook3,4 MacRISC2 MacRISC Power Macintosh detected as : 73 (PowerBook Titanium III) pmac flags : 001b L2 cache: 256K unified pmac-generation : NewWorld -- radeonfb fails to probe EDID on a PowerBook G4 (TiBook) https://launchpad.net/bugs/60685 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60685] radeonfb fails to probe EDID on a PowerBook G4 (TiBook)
Public bug reported: I have a 667 MHz PowerBook3,4, which has a Radeon Mobility M7 LW [Radeon Mobility 7500]. The default boot-up on Dapper, where radeonfb is used, fails very often and it _seems_ even more so after the 2.6.15-26.47 (after more than 20 boots I finally got a working console.) The failure manifests itself as a non-synced display, eg. the display shows a grey bar or random flickering trash. Now, I compared the dmesg output of a failed boot attempt (ssh'ing into the machine) and a successful boot attempt, and there is a difference: Successfull boot: [ 28.799644] radeonfb: Monitor 1 type LCD found [ 28.799652] radeonfb: EDID probed [ 28.799657] radeonfb: Monitor 2 type no found [ 28.799674] radeonfb: Using Firmware dividers 0x0002008e from PPLL 0 [ 28.958642] radeonfb: Dynamic Clock Power Management enabled Failed boot: [ 27.818747] radeonfb: Monitor 1 type LCD found [ 27.818756] radeonfb: Monitor 2 type no found [ 27.818767] radeonfb: Using Firmware dividers 0x0002008e from PPLL 0 [ 27.818776] radeonfb: Assuming panel size 8x1 [ 27.977745] radeonfb: Dynamic Clock Power Management enabled Notice that the failed boot finds the LCD monitor, but does not, for whatever reason, probe the EDID and goes on to assume a grand 8x1 panel! Additionally, any similar issue has NEVER happened when booting to Mac OS X and this problem has been around from at least 2.6.9 kernel, which I remember using with Debian before switching to Dapper. Usually booting between OS X and Linux corrects the problem, whereas successive attempts to boot Linux just fail in a row. ** Affects: linux-source-2.6.15 (Ubuntu) Importance: Untriaged Status: Unconfirmed -- radeonfb fails to probe EDID on a PowerBook G4 (TiBook) https://launchpad.net/bugs/60685 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60685] Re: radeonfb fails to probe EDID on a PowerBook G4 (TiBook)
Recompiled the kernel with Dapper default .config except enabled radeonfb debug. Here's a successful boot dmesg. ** Attachment added: Successful boot dmesg. http://librarian.launchpad.net/4290135/dmesgok -- radeonfb fails to probe EDID on a PowerBook G4 (TiBook) https://launchpad.net/bugs/60685 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
