[Bug 1832182] Re: systemd unable to detect running apache if invoked via "apache2ctl graceful"
First, sorry if I'm in the slightly wrong issue here. The most recent comment before mine fits our situation perfectly and wasn't old, so I think it's an acceptable place for this discussion. > So we have a regression when `apache2ctl graceful` is called directly, which I think it's still a common thing I agreed. 'common thing' is more than true: apachectl resp. apache2ctl were here before init systems started to support 'reload', and propably before Debian's 'service' wrapper around several supported init systems. Hence 1. long-term admins are almost hard-wired to call apache2ctl directly 2. many many scripts do so 3. many many how-to guides, readmes, ..., do so too IMO the 'restart' and 'graceful' branch in apache2ctl should be split up. But I haven't investiagtes why graceful -> restart might make sense in the first place. At all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832182 Title: systemd unable to detect running apache if invoked via "apache2ctl graceful" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1832182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832182] Re: systemd unable to detect running apache if invoked via "apache2ctl graceful"
> Not being able to do a graceful apache restart is a bummer. That's putting it mildly, and it seems totally unnecessary because systemd can reload apache just fine, see below. First a note on the effect of restarting Apache: Everytime Apache restarts we kick out up to 100s of active client connections. On We also have tens of JK workers on some servers, connected to tens of Tomcat instances. This slows down the restart considerably. Secondly to the "unnecessary" part: SystemD is not unable to reload Apache! A simple systemctl reload apache2 does exactly what apache2ctl graceful used to do for decades, and it is reflected in Apache's error.log accordingly: [Wed Oct 13 13:23:23.248679 2021] [mpm_event:notice] [pid 20482:tid 140060367948864] AH00493: SIGUSR1 received. Doing graceful restart Wed Oct 13 13:23:23.295354 2021] [mpm_event:notice] [pid 20482:tid 140060367948864] AH00489: Apache/2.4.41 (Ubuntu) mod_jk/1.2.46 OpenSSL/1.1.1f configured -- resuming normal operations I also have verified that the PID of Apache's main process stays the same and only it's child processes are new. All done on Ubuntu 20.04 which currently would do an apache restart for "graceful" by mistake. So PLEASE, if you insinst on rerouting apache2ctl graceful to systemd make it reload and not restart Apache. Thanks, regards, Christoph Lechleitner -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832182 Title: systemd unable to detect running apache if invoked via "apache2ctl graceful" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1832182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561210] Re: Writing big files to NFS target causes system lock up
Is there a specific patch that addresses our problem? -- Writing big files to NFS target causes system lock up https://bugs.launchpad.net/bugs/561210 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 354717] Re: sky2 rx length error: status 0x2630100 length
This is another proof of Ubuntu's way of operation: Don't work on an issue, wait, close. There's nothing incomplete here except Ubuntu's manpower for following kernel problems. -- sky2 rx length error: status 0x2630100 length https://bugs.launchpad.net/bugs/354717 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 512200] Re: [Lucid] fails to host and to be hosted using LXC/OpenVZ containers
Excuse me!? How does a workaround for the next non-LTS release solve this for the current LTS release!? Besides, telling a few services not to start has nothing to do with a stable setup in the long term, because any update in the area of udev or upstarted will undo part of that and thereby make the guest unusable. -- [Lucid] fails to host and to be hosted using LXC/OpenVZ containers https://bugs.launchpad.net/bugs/512200 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 74179] Re: Ubuntu kernel doesn't support =4GB memory
by the way I also tried 64 bit ubuntu, but it also saw only ~3GB I see no way a 64-bit distro falls short of using every RAM there is. (Well maybe there are kernel params to restrict the RAM but I assume you have not done that) IMO you either have only 3 GB, or your mainboard and/or BIOS lack support for more. -- Ubuntu kernel doesn't support =4GB memory https://bugs.launchpad.net/bugs/74179 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 561210] Re: Writing big files to NFS target causes system lock up
Today I tried copying very large files to a NFS share mounted with rsize=64,wsize=64 and I could reproduce freezes of about 30 secs, but no 120-sec-freezes and nothing in dmesg' output. I am on lucid's amd64 kernel 2.6.32-22. -- Writing big files to NFS target causes system lock up https://bugs.launchpad.net/bugs/561210 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 561210] Re: Writing big files to NFS target causes system lock up
My Desktop also did freeze for those 120 seconds. I use a Gnome but there are KDE based widgets running, namely klipper. Ac. buffer size: Larger write buffers (backed by enough RAM) defer or eventually avoid the point at which the buffer runs full. I think we agree that's when the freeze occurs. Does the kernel allow some kind of temporary overbooking for wirite buffers, like it does for RAM? -- Writing big files to NFS target causes system lock up https://bugs.launchpad.net/bugs/561210 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 561210] Re: Writing big files to NFS target causes system lock up
If my assumption of the freeze trigger is correct, it should be possible to provoke the problem even against fast NFS servers by setting the buffer size extremly low, i.e. to the minimum allowed by the NFS driver. I 'll try this out, but due to a business trip I won't happen before the end of the upcoming week. -- Writing big files to NFS target causes system lock up https://bugs.launchpad.net/bugs/561210 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 561210] Re: Writing big files to NFS target causes system lock up
I only had the problem with an extremely slow NAS as target, I have given the damn thing away a wee ago. So I have no easy way of reproducing it now, sorry. -- Writing big files to NFS target causes system lock up https://bugs.launchpad.net/bugs/561210 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 512200] Re: [Lucid] fails to host and to be hosted using LXC/OpenVZ containers
I am not so sure if OpenVZ as a project is going to survive the fact that Ubuntu 10.04 LTS and RHEL6 both are switching to LXC, I am afraid it might starve to death. However it should become (a lot) easier to get a current distro (like lucid) running (and up to date) as guest under any kernel virtualization, at least under those kernel virtualizations officially supported, like LXC in lucid. Especially with the extremely young LXC many guest-specific details are far from clear, i.e. what parts of /dev/ should be bind-mounted, what services not to start or to remove, how to have apt-get update survive dpkg-reconfigure udev, and so on. Yes, LXC needs to do far more documentation for people other than kernel developers, and yes I kind of dislike both udev and upstart, but the distros should throw in more support, too. There are several HowTos across the web and it's possible to get it running somehow, but by far not as easy and stable as OpenVZ under hardy. We run 30 hardy guests on CentOS hosts, but at the moment I would'nt dare using lucid. Is there any chance of getting an official Lucid-as-LXC- guest.template? -- [Lucid] fails to host and to be hosted using LXC/OpenVZ containers https://bugs.launchpad.net/bugs/512200 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 354717] Re: sky2 rx length error: status 0x2630100 length
The bug still is here, I suffer from it on my failback terminal, a MacMini. I'll test some mainline kernels and then report back. -- sky2 rx length error: status 0x2630100 length https://bugs.launchpad.net/bugs/354717 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 354717] Re: sky2 rx length error: status 0x2630100 length
The problem still is there in 2.6.32-0206321203 (2.6.32.12.3-lucid) and 2.6.33-02063303 (2.6.33.3-lucid). But I noticed why it probably does not concern too many people: The errors only occur if at least one VLAN interface is stacked upon the ethX interface handled by the sky2 module, like eth0.18. -- sky2 rx length error: status 0x2630100 length https://bugs.launchpad.net/bugs/354717 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 354717] Re: sky2 rx length error: status 0x2630100 length
Architecture: i386 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100427.1) Package: linux (not installed) ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, user) LANG=de_AT.utf8 SHELL=/bin/bash Tags: lucid Uname: Linux 2.6.33-02063303-generic i686 UnreportableReason: The running kernel is not an Ubuntu kernel UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare ** Tags added: apport-collected -- sky2 rx length error: status 0x2630100 length https://bugs.launchpad.net/bugs/354717 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 354717] Re: sky2 rx length error: status 0x2630100 length
In other quite old sky/sky2 problem reports I found reports that it'd help to reduce the MTU to 1492 (default is 1500), so I tried MTUs of 1492 and 1400, that did'nt help though. -- sky2 rx length error: status 0x2630100 length https://bugs.launchpad.net/bugs/354717 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 354717] Re: sky2 rx length error: status 0x2630100 length
The problems occurs without VLAN too, if VirtualBox is running and using the ethX. It seems any logical interface stacked upon sky2's ethX provokes the problem. -- sky2 rx length error: status 0x2630100 length https://bugs.launchpad.net/bugs/354717 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 561210] Re: Writing big files to NFS target causes system lock up
I seem to suffer from the same problem in up-to-date lucid x86_64 with Ubuntu kernel 2.6.32-21-generic. I assume the problem only occurs when the target server is considerable slower than the local machine, like an ultra slow NAS serving for a SSD boosted developer machine. -- Writing big files to NFS target causes system lock up https://bugs.launchpad.net/bugs/561210 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 286823] Re: ERROR:terminal-tabs-menu.c:133:free_tab_id: assertion failed: (id = 0 id tabs_id_array-len * 8)
Just for the record: I confirm that upgrading to the latest intrepid packages (as of today) solved the problem for me, too. Thanks for the fast upstream upgrade. -- ERROR:terminal-tabs-menu.c:133:free_tab_id: assertion failed: (id = 0 id tabs_id_array-len * 8) https://bugs.launchpad.net/bugs/286823 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 286823] Re: ERROR:terminal-tabs-menu.c:133:free_tab_id: assertion failed: (id = 0 id tabs_id_array-len * 8)
I have the same problem and I think the crash only happens if gnome is started with multiple windows (--window parameter) and tabs, and if one closes a tab (or the most-right tab?) in another than the first window. -- ERROR:terminal-tabs-menu.c:133:free_tab_id: assertion failed: (id = 0 id tabs_id_array-len * 8) https://bugs.launchpad.net/bugs/286823 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 189462] Re: slocate cron job fails if /etc/updatedb.conf not found
Abel Cheung wrote: For those who need command line access, change your habit is the way to go. This ignorance against command line users is annoying, at best! Matt Zimmerman wrote in that link mailing list message: Today, at least, it doesn't seem to be used, and more featureful indexed searching is provided by tracker, and the overhead of re-indexing daily can be inconvenient for laptop users. Daily reindexing is not necessary! For years we used to call updatedb on demand only. As of laptop users (and not only them) the system load and power consumation and installation slowdown produced by trackerd and some other stuff (that scans the disc multiple time during installation) is much more disturbing than the simple filename scan of *locate! Seth wrote: Anyways, I consider this issue well-fixed, and I hope users/dev gap is a little more bridged on this one :) The issue is not fixed! Althought the fix would be very very easy, the hardy package is still broken! And hardy as a LTS is supposed to be maintained really well. Unfortunately it gets more and more clear that Ubuntu's interpretation of the term support is a joke. -- slocate cron job fails if /etc/updatedb.conf not found https://bugs.launchpad.net/bugs/189462 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 235284] Re: Suspend-to-ram broken on IBM/Lenovo Thinkpad T61p [FIXED]
When you say suspend works perfectly now, does that include both, suspend to ram (Fn+F4) and suspend to disk (Fn+F12)? What is your BIOS revision please? -- Suspend-to-ram broken on IBM/Lenovo Thinkpad T61p [FIXED] https://bugs.launchpad.net/bugs/235284 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 164819] Re: Can't Remove Scrollkeeper without trashing Gnome
Better way (still not recommended): sudo dpkg --force-all --remove scrollkeeper --purge -- Can't Remove Scrollkeeper without trashing Gnome https://bugs.launchpad.net/bugs/164819 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 164819] Re: Can't Remove Scrollkeeper without trashing Gnome
I strongly support this issue. This damn thing just eats resources, energy, ... and the only nice way to disable it is either hacking or removing it's binaries and/or cronjob. -- Can't Remove Scrollkeeper without trashing Gnome https://bugs.launchpad.net/bugs/164819 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 116842] Re: Generic 32 bit kernel should be compiled with 64 GB memory support
How about a PAE-enable kernel as option after installation? The bug sure isn't invalid. It exists already. It is the server kernel. At the time we came up with this issue (feisty), several module packages had not been available for the -server kernel, therefore some things (especially GPUs and WLAN cards) could not have been run easily on a server kernel ;-(( This did not change with gutsy, but with hardy seems to have changed. Was there an official change in the policies regarding e.g. the linux-restricted-modules and kernel packages? Anyway, did anybody actually try to use e.g. nvidia-glx-*, fglrx*, ... together with hardy's server kernel? -- Generic 32 bit kernel should be compiled with 64 GB memory support https://bugs.launchpad.net/bugs/116842 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 204996] Re: Linux kernel 2.6.24-12 lockup
1. Has anyone ssen this happen on the SERVER build of kernels, or is this just happening on the GENERIC build? I have seen this kind of crash with feisty's server kernel on my IBM x335 servers on a regular basis. I would not be surprised if the initial cause(s) are in since 2.6.20 (which seem to have started the deep fall of kernel stability). My problems vanished when I stepped back to edgy, in the meantime I have switched the host system to etch, while keeping the OpenVZ guests on feisty/gutsy. I get the impression that the problem only occurs on SMP systems, and my systems crashed when LAN (wired GBit) and CPU and HD were under some load, e.g. 2 rsyncs over SSH over GBit. HD and LAN IO produce a large number of interrupts which seem not to be trivial to handle on a multicore system. -- Linux kernel 2.6.24-12 lockup https://bugs.launchpad.net/bugs/204996 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 116842] Re: Generic 32 bit kernel should be compiled with 64 GB memory support
non-PAE supporting hardware will fail booting with the kernel Ouch, I admit that hurts. Especially for non-x64-hardware where you have no workaround in switching to the amd64 distro. I guest PAE cannot be loaded lateron or switched active with a kernel line parameter? So what's left is either to eventually provide a some generic-bigmem kernel (and all the accompaning packages, especially several module packages for GPUs, WLAN cards, ...). -- Generic 32 bit kernel should be compiled with 64 GB memory support https://bugs.launchpad.net/bugs/116842 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 156804] Re: generic kernels should support 4 GB RAM
*** This bug is a duplicate of bug 116842 *** https://bugs.launchpad.net/bugs/116842 For the record: After all one 3rd party software company learns 64 bit compilation: In the developer snapshot area ... http://my.opera.com/desktopteam/blog/ ... Opera provides a 64 binary package for several Linuxes including Ubuntu. -- generic kernels should support 4 GB RAM https://bugs.launchpad.net/bugs/156804 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 192605] Re: virt-manager does not detect bridge br0
...OK, we've set up another test system, where the bug occurred exactly as reported. The output of your shell script is: [EMAIL PROTECTED]:~# sh /home/lech/Desktop/test.sh eth0 Examining interface: eth0 udi for eth0 is /org/freedesktop/Hal/devices/net_00_16_cb_a6_f3_16 sysfs_path for eth0 is /sys/devices/pci:00/:00:1c.0/:01:00.0/net/eth0 drwxr-xr-x 2 root root 0 2008-03-07 18:13 /sys/devices/pci:00/:00:1c.0/:01:00.0/net/eth0/brport lrwxrwxrwx 1 root root 0 2008-03-07 18:14 /sys/devices/pci:00/:00:1c.0/:01:00.0/net/eth0/brport/bridge - ../../../../../../../devices/virtual/net/br0 [EMAIL PROTECTED]:~# -- virt-manager does not detect bridge br0 https://bugs.launchpad.net/bugs/192605 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 156804] Re: generic kernels should support 4 GB RAM
It's a known fact that 32-bit Linux only supports around 3.2 GB of RAM. ??? With PAE and HIGHMEM_4G/HIGHMEM_64G enabled and compiled for i686 or higher, a 32-bit Linux can see 4 GB resp. 64 GB without problems. (One could of course argue that these kernels are not pure 32-bit) In some PAE articles I fell over months ago, there were success reports for using 8 GB on some 32bit servers (HP or Dell I believe), and I can confirm 4 GB for a pure 32bit Dell 2600 running SuSE 9.2 with a kernel called 2.6.8-24.25-bigsmp. Obviously, cracking the 4 GB barrier requires certain things (address lines, PAE support, ...) from CPU, mainboard, memory and BIOS, but just a obviously there are 32bit servers fullfilling these requirements. And we still want HIGHMEM_64G for -generic kernels for using it on Desktops and Laptops, because the application situation for 64-bit is still far from satisfying, due to some large firms' ignorance (which might be broken by Microsoft's 64-bit-only policy for W2k8+). A precompiled firefox-ia32 package (and a bunch of firefox-plugin-*-ia32 packages) for the amd64 distro could provide a workaround for the most annoying lacks of amd64 ubuntu, but the increased memory usage of 64-bit binaries still recommends using a 32-bit distro. -- generic kernels should support 4 GB RAM https://bugs.launchpad.net/bugs/156804 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 156804] Re: generic kernels should support 4 GB RAM
Most restricted drivers are available es extra package, in versions sepcifically compiled against specific kernels. (nvida-glx-legacy, nvidia-glx, nvidia-glx-new) Putting restricted nvidia modules in the kernel will not happen and for good reasons: + the kernel should be kept small, It's awful big as it is. + no one wants to taint the 100% GPL kernel with questionable closed-source binary garbage. + there are several different versions of the nvidia kernel modul, all with the same name. this is because nvidia maintains 3 or 4 generations of it's driver (7xxx, 9xxx, 11xxx, 1xx.11.x, ...). there are even modules not needed always, e.g. nv_agp. -- generic kernels should support 4 GB RAM https://bugs.launchpad.net/bugs/156804 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 156804] Re: generic kernels should support 4 GB RAM
Ah, that you meant. The server kernel will never get X11 support ;- I used the server kernel (and nvidia's own installer) for some time myself, but that's really not the way it should be. I agree with your solution list and that #1 is the favourite. However I'd generally love to see more complete and better 64/32 bit compatibility work, because I sometimes do things that are impossible to do with 32bit software. Like: + opening a 2GB text file with gvim ;-) + rendering PDFs and HPGL files where the pixel representations becomes larger than 2GB Obviously, some small poor companies like Adobe, Google, Opera, Skype, RealMedia, ... really need to start providing 64bit binaries!!! -- generic kernels should support 4 GB RAM https://bugs.launchpad.net/bugs/156804 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
Has anybody tried the new 169.07 driver? -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 173686] Re: vmware-server break PAM
*** This bug is a duplicate of bug 112937 *** https://bugs.launchpad.net/bugs/112937 I can confirm the problem, however I cannot confirm the solutions. I still get this: Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (vmware-authd) illegal module type: @include Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM pam_parse: expecting return value; [...common-auth] Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (vmware-authd) no module name supplied Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM unable to dlopen(*unknown module path*) Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM [error: *unknown module path*: cannot open shared object file: No such file or directory] Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM adding faulty module: *unknown module path* Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (vmware-authd) illegal module type: @include Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM pam_parse: expecting return value; [...common-account] Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (vmware-authd) no module name supplied Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (other) illegal module type: @include Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM pam_parse: expecting return value; [...common-auth] Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (other) no module name supplied Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (other) illegal module type: @include Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM pam_parse: expecting return value; [...common-account] Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (other) no module name supplied Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (other) illegal module type: @include Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM pam_parse: expecting return value; [...common-password] Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (other) no module name supplied Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (other) illegal module type: @include Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM pam_parse: expecting return value; [...common-session] Dec 24 15:38:44 vz02 vmware-authd[19308]: PAM (other) no module name supplied Eventually my problem is caused by the fact that I had VMWare's tarball installed previously and eventually their uninstall script might have left some traces iiritating Canonical's packaged version. I switched back to the VMWare tarball and it's fine for me now. This is one of the apps where I like to stay at the bleeding edge anyway (Bleeding edge means being ahead of any distribution most of the time and using upstream tarballs all the time). -- vmware-server break PAM https://bugs.launchpad.net/bugs/173686 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 77470] Re: Initial install, RAID; use --assume-clean with mdadm, and prompt for chunk size
I just had the same expirience with gutsy. I absolutely support that the chunksize should be configurable in base-installer's partitioning section, and that the mke2fs call should be checked for optimization. -- Initial install, RAID; use --assume-clean with mdadm, and prompt for chunk size https://bugs.launchpad.net/bugs/77470 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 178450] base-installer fails to delete existing RAID devices due to wrong device path
Public bug reported: The software RAID section of the text based installer from gutsy's alternate amd64 CD fails to delete existing software RAID devices, because it uses the wrong device path, i.e. /dev/md/0 instead of /dev/md0, /dev/md/1 instead of /dev/md1. Creating according softlinks via console tty2 helps ;-)) I am not sure if the problem lies in the installer, or in mdcfg or mdadm, or eventually might even depend on what md-tools release created the md devices (in install situation it's difficult to trace those back), but if there's really is a / too many it should be easy to backcheck and fix, for someone familiar with the installer sources. ** Affects: base-installer (Ubuntu) Importance: Undecided Status: New -- base-installer fails to delete existing RAID devices due to wrong device path https://bugs.launchpad.net/bugs/178450 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
Eventually good news. After investing in a docking station and a 24 TFT, I had to try the nvidia driver again (the VESA driver does not support or not understand the up to 3 available monitors when using all external video connectors), and I have suspend to RAM perfectly working now on my T61p with NVidia Quadro FX 570M under gutsy amd64 with -generic kernel. Suspend to disk still kills everything, but suspend to RAM more or less does it for me, and external video plugs (activated through nvida- settings) and GLX resp. googleearth all work, too. I also don't know which of the many upgrades since gutsy's releases was the crucial one (probably more than one), after all this problem concerns at least the kernel modules, ACPI-support, thinkpad packages, nvidia's drivers and kernel modules, the thinkpad's BIOS, and the interaction of all these pieces. I would'nt wonder if the usage of a docking station (advanced mini dock in my case) causes some behaviour to change a tiny but crucial bit ;-)) Anyway, here is what I assume are crucial keys to success: + have nvidia-glx-new 100.14.19 installed + install all gutsy updates as of 2007-12-22 + in /etc/default/acpi-support have SAVE_VBE_STATE=false, POST_VIDEO=false, SAVE_VIDEO_PCI_STATE=true, ACPI_SLEEP=true + in /boot/grub/menu.list have the kernel option acpi_sleep=s3_mode, e.g. in defoptions= and your default kernel's line. + eventually have a boot time script (before gdm!) with e.g. rmmod nvidia ; insmod nvidia_new Merry X-mas ;*) -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 156804] generic kernels should support 4 GB RAM
Public bug reported: Binary package hint: linux-image-generic For some months now developer machines (desktop and laptop) are available and bought with more than 2 GB of RAM, say 4 GB. Unfortunately, the -generic kernel of Ubuntu x86 only uses up to 3 GB (at least that's /proc/meminfo tells), which is unsatisfying. As the -server kernel of the very same distribution does support 4 GB, this seems to be a kernel option issue. After a look in /boot/config* I believe the key options are CONFIG_PAE and/or CONFIG_HIGHMEM64G which are set to no or not at all for -generic. I believe this options should be enabled for -generic also. (This is obviously a wish, not a bug) Remark 1: As CONFIG_HIGHMEM4G is set to yes in -generic kernel, it might be that the kernel uses the 4th GB, for kernel space only (I once found a bigmem discussion that suggested this special memory split for 4 GB situations). Assuming this is true, sharing all 4 GB dynamically still would be better. Remark 2: Most of the new common 4 GB machines are amd64 capable, so one might suggest using the amd64 distribution. Unfortunately, many 3rd party applications are not available for amd64, and the ia32/linux32 subsystem is far from complete (yes, I'd like all libs beeing doubled), so this is not a real option, not even for servers where 4 GB are common for some time now, even on pure 32bit CPUs. Remark 3: Some manufacturers, including the small company continueing big blue's ThinkPad series, had obvious problems writing correct firmware for recent intel chipsets or don't know of PAE at all (or both) and therefore officially (!) (on their 4 GB laptops' product data sheets) claim that 32bit operating systems in general could only use 3 GB. I laugh at that now ... ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- generic kernels should support 4 GB RAM https://bugs.launchpad.net/bugs/156804 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 132399] Re: fancyheadings.sty disappeared
As it took me half an hour's research to follow the TEXMFLOCAL hint above, I decided to create a Mini-HowTo and took the liberty of making the two .sty files available: These steps make fancyheadings.sty (from Ubuntu feisty's tetex-extra package) available in Ubuntu gutsy and took the liberty of making the two .sty files available: sudo mkdir -p /usr/local/share/texmf/tex/latex/fancyheadings sudo chmod -R ugo+rx /usr/local/share/texmf cd /usr/local/share/texmf/tex/latex/fancyheadings sudo wget http://www.ibcl.at/files/fancyheadings/fancyheadings.sty sudo wget http://www.ibcl.at/files/fancyheadings/lastpage209.sty sudo texhash sudo chmod -R ugo+rx /usr/local/share/texmf Voila. This Mini-HowTo is also available in my BLog: http://www.ibcl.at//ibclweb/ibclweb?page=ShowBLogArticleservice=externalsp=l151 Norbert, do you see a legal problem with those two files beeing available from my server? -- fancyheadings.sty disappeared https://bugs.launchpad.net/bugs/132399 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 132399] Re: fancyheadings.sty disappeared
Such a redirect style could have been integrated to tex-live ;-)) But I can see that a new tex distribution won't care for all addons of all other tex distributions. For me and the other people with document bases uses fancyheadings.sty, the TEXMFLOCAL approach is far more convenient, even if we don't like encouraging the use of deprecated stuff. Regards Christoph -- fancyheadings.sty disappeared https://bugs.launchpad.net/bugs/132399 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
Found some more hints and a new thinkpad-acpi 0.17, so here are more test results: 1. with kernel parameter maxcpus=1 (hint in nvidia forum), nvidia 100.11.19 (.deb) suspend 2 ram works fine. hibernation does not work, but dies much later. 2. with new thinkpad-acpi 0.17-20071002 patched into ubuntu's linux-source-2.6.22: suspend 2 ram works fine. hibernation does not work, but dies much earlier. 3. with nvidia-diver .09 (hint in nvidia forum) (manual install): suspend 2 ram works fine. hibernation does not work, but dies much later. So, there are several ways now to get suspend to RAM working (with nvidia drivers active), but still only vesa or nv driver (might) allow hibernation. -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
Confirmed for Quadro 750 M: nvidia + acpi_sleep=s3_mode allows suspend to ram. Thanks for the hint. thinkpad_acpi is currently working on the backlight brightness, where the T61 introduced more levels. But as hibernation is very ACPI specific, I tried anyway. I'm gonna try combining s3_mode with maxcpus=1 and driver .09. -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
No I just said they are working in the area of brightness control in the current T61 generation. I am not sure this concerns the GPU driver at all, but brightness control seems not to be working yet on some T61 models. Details can be found in the mailing lists of linux-thinkpad.org. -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 102037] Re: [New Package Freeze Upstream] maven2-2.0.7
For know everyone is working on getting gutsy ready (especially for this damn hardware thrown on the market the last few months). Hardy development will start at an open kickoff meeting at the end of October (in the campus hotel of a certain US university I believe), we won't see even an alpha for some time. But an extract-and-set-a-softlink package that can be installed manually so easily is really far from a reason to go beyond a distro's bleeding edge ;-)) Besides, I am almost sure we will see a maven package in a PPA soon after gutsy's final release. -- [New Package Freeze Upstream] maven2-2.0.7 https://bugs.launchpad.net/bugs/102037 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
After those many upgrades today, I did more research testing - and have partial success! Calling the script attached (based on the one from ThinkWiki) as root now safely suspends to ram and I even have reasonable 2D and 3D performance after resuming. Suspend to disk or any suspend using Fn+F4 or Fn+F12 do not work yet. ** Attachment added: suspend2ram script working on T61 Quadro FX 570 M with today's gutsy amd64 http://launchpadlibrarian.net/9609860/suspend2ram -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
Because of the release of gutsy beta, I re-did most of my tests today. Still no change though: gutsy beta with nvidia driver (gutsy package nvida-glx-new 100.14.19) kills the machine during resume (although I sometimes was able to ping or even ssh it). gutsy beta with nv driver (the open source driver which now basically can operate my FX 750 M) kills the machine during resume. gutsy beta with vesa driver allows suspend/resume without problems. I even may leave the network and usb stuff active. -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 98641] Re: [nvidia-glx-new] Driver is missing libwfb breaking X on 8000 series cards
Is this fixed in Gutsy beta? Yes, more or less. At least libwfb.so is in the current nvidia-glx-new 100.14.19 package. Unfortunately there are many other unsolved problem with recent cards from all manufacturers. -- [nvidia-glx-new] Driver is missing libwfb breaking X on 8000 series cards https://bugs.launchpad.net/bugs/98641 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 132399] Re: fancyheadings.sty disappeared
I solved my performance problem with tex stuff run as non-root, using top and Google: In this article ... http://www.esm.psu.edu/mac-tex/MacOSX-TeX-Digests/2001/MacOSX-TeX_Digest_11-26-01.html ... from 2001 (!) I found: --- SNIP --- - Added '$HOME contains //' check to TeXGSInstaller installation script (if a directory ends on /, kpathsea can become extremely slow) --- SNIP --- Due to certain circumstances (see below) my home directory was set to /home/johndoe/./ After I removed the trailing /./ (and rebooted), latex and xdvi performed well again. Just in order not be declared crazy, I admit that such home directory settings are extremely rare. Such as: 1. Certain FTP daemons are taking /./ in a user's home dir as chroot-him-there hint. 2. When doing domain/mail/web/application hosting (even on our small level with some 20 customers) appending /./ to most user's home directory allows to easily chroot them for FTP access while still granting more freedom to a few trusted users. 3. To guarantee synchronity of uids, group memberships, passwords etc. we include most of our internal servers and workstations in the ISP administration system we created for ourselfes. Despite my extremely rare circumstances, adding a protection towards this problem would definitively be an enhancement after all ;-)) -- fancyheadings.sty disappeared https://bugs.launchpad.net/bugs/132399 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 132399] Re: fancyheadings.sty disappeared
fancyheadings.sty is present in feisty's tetex-extra package, but is missing from gutsy's TeX Live package. I googled some comment that said that fancyheadings.sty was removed from debian's TeX packages because it has been marked obsolete for some time. This is very ruthless youngster thinking and absolutly unacceptable! For several reasons: + TeX styles has never been removed from LaTeX ever, there is no reason to! + Millions of .tex documents use this style and nobody is going to adapt them (which is very difficult btw.!). + Thounsands of scripts of old TeX users at companies, academic organisations and so on produce tex documents using this style and it's almost impossible to adapt them! + We rather live with old LaTeX than some youngster's stuff that lacks backward compatibility!!! -- fancyheadings.sty disappeared https://bugs.launchpad.net/bugs/132399 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 132399] Re: fancyheadings.sty disappeared
The fact that fancyheadings.sty is missing in gutsy is obiously true and I therefore confirm it. ** Changed in: texlive-base (Ubuntu) Status: New = Confirmed -- fancyheadings.sty disappeared https://bugs.launchpad.net/bugs/132399 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 132399] Re: fancyheadings.sty disappeared
First, s/fancyheadings/fancyhdr/ does not help, the headings does not look correct then. Maybe it's not that much to change, but I still see no reason to kill fancyheadings.sty. We and at least on other firm I know use fancyheadings in script- generated documents for automatic invoice prodution. And btw., with 37 I consider myself grown up. And yes, of course I can just copy fancyheadings.sty from elsewhere, but at the moment TeX in gutsy needs 1 minute for a one-page document that processes in 1 sec. on feisty. -- fancyheadings.sty disappeared https://bugs.launchpad.net/bugs/132399 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 132399] Re: fancyheadings.sty disappeared
First let me apologize for my sour note above. In the first place I just wanted to know if anyone besides me is missing this fancyheadings style, too. Then I just wanted to confirm the simple fact, but sometimes my fresh angry thoughts fall in a feedback loop ;-(( Secondly, MANY THANKS for the tips, they work and I have put them in my 2nd brain, aka BLog: http://www.ibcl.at//ibclweb/ibclweb?page=ShowBLogArticleservice=externalsp=l150 As of the speed problem, I isolated this to some access rights problem. When I start latex or xdvi as root, they work usually fast, i.e. like a rocket. When I start them as normal user, they try to do something for a minute or so. I also have other minor problems of this kind, so I guess it is my fault somehow, and I will [s]trace this down myself tomorrow. My new ThinkPad is far too new for any OS, as it should seem, so I patched in newer ALSA and acpi_thinkpad drivers, tried several NVidia-drivers, produced umpsteen crashes during suspend/resume tests, and so on ... Somewhere along this path I might have killed some execute or sticky bit or something alike. I'll narrow it down, eventually cross check with a fresh gutsy i386 (it's amd64 here), and post any findings somewhere appropriate (and at least a link in here). Kind regards, Christoph -- fancyheadings.sty disappeared https://bugs.launchpad.net/bugs/132399 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
** Attachment added: xorg.conf for T61p NVidia Q570M in VESA mode http://launchpadlibrarian.net/9370024/xorg.conf -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
On the other hand, suspend to ram worked with nvidia 100.11.14 and kernel 2.6.22-10-generic, so it could be a two edged sword after all!? X have been unusable slow after resume with that combination, but according to the NVidia forum http://www.nvnews.net/vbulletin/showthread.php?t=94258 this seems fixed at least for the prior GPU NVS140M on an ThinkPad R61. -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
With today's update (or yesterday's, many traffic these days) I seem not to need the thinkpad_acpi update any more, as long as I use the VESA driver. I just did one suspend 2 ram, one hibernate, resume was ok both times. I use amd64 only, so if Robbob tests with i386 this issue could eventually be assigned to the nvidia-glx-new package. Let's just hope NVidia solves the problem soon. Fortunately, their driver is easy to install for expierienced users, so personally I could live with manual driver upgrades after gutsy release. One more observation: With nvidia drivers (and nvidia's NV-GLX), glx apps die immediately with a memory fault when started as normal user, but work when started as root. Looks like a wrong file mode, but I don't care for now. -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
Just FYI some anti-nvidia-confirmations: As suspected, no resume with manually installed brand new nvidia driver 100.14.19 (with neither 2.6.22-11-generic kernel nor our thinkpad_acpi upgraded 2.6.22.6) Nvidia*run --uninstall, apt-get install --reinstall libgl1-mesa-glx, back to VESA, resume ok again. I sincerely hope that gutsy gets enough time (a release postponement if necessary) to resolve all these NVidia problems and other Centrino Pro issues. I know it's NVidia fault (and Intel's fault as of the Centrino Pro problems), not any Linux developer's, but once again: If Ubuntu's tries to force the users to blame NVidia, it knowingly creates a loose-loose-loose situation! Especially we notebook users can't easily pull out the NVidia GPU and plug in an Intel or ATI GPU, and even worse, at the moment virtually all top laptop models (those with 64bit dualcores and 4 GB RAM) come with NVidia GPUs. -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
First a small success report: During the past 30 hours, I suspended to RAM 4+ times, and either the power manager or the BIOS induced one suspend to disk due to poor battery state (best CPU, 4 Gig RAM, best GPU, all so power consuming ...). I had no problem resuming, even with such evil circumstances as removing an USB device during suspension. The bad news: I just have to try the brand new NVidia driver right now ;-, reports follow. -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
Somehow the recent acpi* updates killed my resume capabilities ;-(( At the moment I don't have the time to track down details ... -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
I just resumed successfully again. It seems the kernel parameter acpi_sleep=s3_bios is crucial after all. I should not touch /boot/grub/menu.lst that often and use shift-D in vi that ofen ;-)) Sorry if I really bothered you because of my incautiousness, I am gonna add more experience reports as gutsy (hopefully) matures. -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
With vesa driver, suspend to ram works for me. However, I can't get the full 1920x1200 for now, fighting on it right now. Of course the only real solutions is a better nvidia driver, but suspend/resume is more important for me than the performance advantage of the nvidia driver. With AMD/ATI opening their drivers, Dell wanting to support linux on all laptops, and the current nvidia driver crashing with compiz for gutsy, I think they should begin to feel some pressure. -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
I just got vesa working with full res. 1920x1200. (I'll BLog how some day soon) Only remaing problem so far: GoogleEarth does not even run slow but crashes X ;-(( I think because xorg's software GLX, unlike the nvidia driver, does not provide 32bit compatibility on 64bit installations. Well, I can live with that for quite some time. For now, with new thinkpad_acpi and vesa drivers, all major stuff works: X, suspend/resume, sound, WLan, even VMWare and probably bluetooth (no time to test right now, but seems ok). Skype and Opera lack 64bit binaries, but that's their large fault and a major mistake (as the current generation of machines supporting 4-Gig- RAM will drive everyone to 64bit installations). -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
I do not think my (mini) BLog is that interesting, but there are some Ubuntu hints ;-)) I'd have published the VESA hints earlier this day, but due to a Tapestry 4.1 incompatibility in my website I had not been able to log in at all ;- Here's the deep Link to the VESA Mini-HowTo: https://secure.ibcl.at/ibclweb/ibclweb?component=%24DirectLinkpage=ShowBLogOverviewservice=directsession=Tsp=l148 -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
There is of course a non-secure BLog access also: http://www.ibcl.at/ibclweb/ibclweb?component=%24DirectLinkpage=ShowBLogOverviewservice=directsession=Tsp=l148 -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
As of decision making in Ubuntu development, I think there is plenty of room for improvement. This is one of the topics where SuSE is better and probably one reason for why SuSE's market share has grown again, despite Ubuntu's popularity. If gutsy really is published with thinkpad_acpi 0.15, I am gonna put kernel packages for i386+amd64 in my own archive http://deb.ibcl.at/ or in a PPA. However, according to the changelog of today's update of the acpi- support package, someone at Ubuntu is currently working on thinkpad stuff, and as the thinkpad_acpi 0.16 patch integrates in linux- source-2.6.22 without the sligthest problems there still is hope it's gonna make it into gutsy. -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
Sitsofe Wheeler, it seems you work too hard ;-)) As I read it, the new thinkpad_acpi 0.16 solved suspend/resume for Robbob. He uses VESA driver anyway because he did'nt know how to build an according linux-restricted-modules package (I wonder if this would be needed to rebuild at all?). I can confirm for current gutsy amd64 that with a patched kernel and vesa driver, suspend to ram and disk work perfectly on my T61p. I also can confirm that using the nvidia driver causes a crash during resume. With 2.6.22-10 suspend 2 ram was possible (using the script from thinkwiki, not using the fn-hotkeys), but X was unusable slow after resume. NVidia knows about this problem (crash on resume in some installations, X slow after resume on other installations) (and some other problems of the 100.11.14 driver). According to their forum they are working on a new driver with pressure, but it seems they need more time for this one; probably they try to solve too many things at a time: + there are suspend/resume problems, with almost every hot chip currently sold in top laptop + they to want to become compatible with the new ABI of just released xorg 7.3 without breaking with earlier xorg releases like 7.2 + your certainly know about the compiz patch that just became upstream but causes crashes when meeting the nvidia driver ... -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
Don't worry. 1. ThinkPads have always been a popular device for Linux users, including many professional developers. 2. The Centrino Pro chipset used in the most recent models are absolutely mainstream and also used by other manufacturers including HP and especially Dell who has chosen to sell and therefore support Ubuntu based notebooks. Therefore you can be sure every little feature will work well - in time. Still it might happen that Ubuntu 7.10 might come too early to cover everything. But there is hope suspend/resume might work with 7.10 eventually, because: In contradiction to what I wrote above, thinkpad-acpi 0.15 (and 0.16) is not restricted to kernel 2.6.23+, there are tarballs for older kernels, including some 2.6.22.x releases. See http://sourceforge.net/project/showfiles.php?group_id=117042package_id=230205 -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
Bad thing is, the patch did'nt work for me :-(( Do you have any special kernel parameters? What is the value of POST_VIDEO in your /etc/default/acpi-support? Which X driver are you using? -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 129125] Re: Please upgrade Thinkpad_acpi to 0.15-20070723 to solve problems for recent Thinkpads (X61's and T61's)
thinkpad_acpi 0.16 from http://sourceforge.net/project/showfiles.php?group_id=117042package_id=230205 can easily applied to Ubuntu's 2.6.22 kernel source. I am not sure what it does solve (e.g. for my T61p), I am still fighting for suspend/resume ;-)) Also, I still have two /proc/acpi/video/VID entries. -- Please upgrade Thinkpad_acpi to 0.15-20070723 to solve problems for recent Thinkpads (X61's and T61's) https://bugs.launchpad.net/bugs/129125 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
Thanks for the fast reply. So this seems to leave the nvidia driver as bad guy. Let's all hope they finish their next release really soon. -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
With kernel 2.6.22-10 I could suspend from tty1-6 using the script from http://thinkwiki.org/wiki/Installing_Ubuntu_7.04_%28Feisty_Fawn%29_on_a_ThinkPad_T61#Suspend However I am not sure if this is the same suspend operation that occurs when pressing Fn-F4 while in X. With my former ThinkPads, A31 (ACPI off, APM on) and T41 (APM as well as ACPI), and after rmmoding the network module and after unplugging the USB mouse, I was able to use both suspend hotkeys Fn-F4 and Fn-F12 while in X or text console, and of course that's what we'd like. In Debian discussions I found hints to use hibernation or swsusp package, which operate in user space only. I guess all of the script solutions just echo stuff to /proc/acpi/sleep. I'll continue my tests with vesafb driver tomorrow. It's late here ;- -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 139089] Re: Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p
With 2.6.22-10-generic suspend to ram sometimes worked (after setting POST_VIDEO=false in /etc/default/acpi-support). Unfortunatley, X was incredibly and unusable after resume, which seems to be an NVidia problem promised to be solved with the next driver after nvidia-glx-new 100.14.11. With 2.6.22-11-generic suspend went back to die-during-resume state. This is with T61p, NVidia Quadro FX 750M, current gutsy i386 and amd64. As thinkpad-acpi includes support for new T61/X61 models only for kernel 2.6.23 (and suspend/resume is of course in need of good interaction with a machine's ACPI implementation) I am afraid 7.10 might not allow us to use all features of our far-too-new ThinkToys. We might want to switch to 2.6.23 (and perhaps xorg 7.3) on our own, but I won't start that kind of work before I can be sure 7.10 won't satisfy my need to suspend/resume. -- Gutsy Gibbon : Suspend/Hibernate lock up on resume with Thinkpad T61p https://bugs.launchpad.net/bugs/139089 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 98641] Re: [nvidia-glx-new] Driver is missing libwfb breaking X on 8000 series cards
Two days ago the state (on the Austrian mirror) was a pain, but with current updates ... I confirm it works now with gutsy-amd64 on a Thinkpad T61p with Nvidia Quadro FX 570M. However, I had to explicitly uninstall the manual installation of NVidia's driver, I reinstalled nvidia-glx-new and restricted-modules. And I had to dpkg-reconfigure xserver-xorg and explicitly select the nvidia driver instead of nv. -- [nvidia-glx-new] Driver is missing libwfb breaking X on 8000 series cards https://bugs.launchpad.net/bugs/98641 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 136838] Re: wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time (manual install)
Confirming solution by package updates, and how-to undo workarounds ... With updates from today this problem does not exist any more. If a machine has traces of workaround described above, one needs to: + --uninstall any manual NVIDIA*run installation + remove nv* from DISABLED_MODULES (in /etc/default/linux-restricted-modules-common) + eventually add nvidia / nvidia_new to /etc/modules (not sure this is needed) + make sure there is no real stuff commented out in /etc/modprobe.d/lrm-video + reinstall linux-restricted-modules-2.6.22-11-generic and eventually nvidia-glx-new -- wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time (manual install) https://bugs.launchpad.net/bugs/136838 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 136838] Re: wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time (manual install)
Wether or not this bug was real (or only the siblings were), I set it to Fix Released so other people can find the knowledge collected here. ** Changed in: linux-restricted-modules-2.6.22 (Ubuntu) Status: Invalid = Fix Released -- wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time (manual install) https://bugs.launchpad.net/bugs/136838 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 50865] Re: dapper installer insists on partition table change
Btw., how do you define LTS? -- dapper installer insists on partition table change https://bugs.launchpad.net/bugs/50865 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 136838] Re: wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time (manual install)
Finally, the new 2.6.22-11 kernel packages and other update from the last 3 day breaks down restricted stuff completely. There are no loadable nvidia kernel modules!!?? The restricted manages tells us we would'nt need restricted drivers!!!??? The damn self-repair-function of gdm (or is it X) simply renames our nice working X11 config and produces only things that are much worse than our initial X experiences in early 1990s. Re-Running NVidia' s installer seems to solve this (and, together with some of the tricks above) leads to a working X11 again. -- wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time (manual install) https://bugs.launchpad.net/bugs/136838 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 136838] Re: wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time (manual install)
For now this problem only exists with (obviously unsupported) foreign software (NVidia driver installed manually). From a pure Ubuntu point of view it cannot be reproduced because of other problems of the current nvidia-glx-new package (see Bug #98641). Therefore I set this bug to invalid and assign it to me. Whenever untill nvidia-glx-new is fixed, I will retest the situation with a pure Ubuntu configuration and then decide either to close or to re-open this bug. ** Changed in: linux-restricted-modules-2.6.22 (Ubuntu) Assignee: (unassigned) = Christoph Lechleitner Status: New = Invalid -- wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time (manual install) https://bugs.launchpad.net/bugs/136838 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 136838] wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time
Public bug reported: Binary package hint: linux-restricted-modules-2.6.22-10-generic I have a Lenovo Thinkpad T61p with a nVidia Quadro FX 570M card (PCI-Id: 10de:040c) that needs up-to-date driver 100.11.14 to work at all. (It still has the problem of slowing down after suspend/resume, but X works with NV-GLX and all) Unfortunately, with up-to-the-second Gutsy something loads an old nvidia kernel module from somewhere ... $ dmesg |grep -i nvidia [ 17.384000] nvidia: module license 'NVIDIA' taints kernel. [ 17.488000] NVRM: loading NVIDIA Linux x86 Kernel Module 1.0-7185 Mon Apr 2 18:29:54 PDT 2007 ... which prevents X from starting. There is a workaround ... rmmod nvidia insmod /lib/modules/$(uname -r)/kernel/drivers/video/nvidia.ko ... to be called before X starts (e.g. in some /etc/init.d/boot.local script), but that's too difficult for the average user. I believe this problem is in the area of the linux-restricted- modules-2.6.22-10-generic, but I am not sure ;-)) Here is what I tried to solve the problem w/o the above module hack: I changed /etc/default/nvidia-kernel to NVIDIA_CARDS=0 I had only the nvidia-glx-new 100.14.11+2.6.22.3-10.1 installed, no other nvida-glx-* package). I even had xserver-xorg-video-nv removed, I even had the initrd images re-collected after the manual module change. After all this, the kernel still starts with the old 7185 module. I know it's Nvidia's fault to need kernel modules at all, and the existence of 4 driver branches, even with some overlapping concerning the lists of cards supported is a pain in the ass for all of us, but we need to avoid such a version mess if Ubuntu is to become usable for the next guy. I see two options: 1. /etc/default/nvidia could get an option to choose the driver version. or 2. Divide the linux-restricted-modules package into packages with specific versions (generations) of specific drivers for specific devices. E.g.: linux-restricted-modules-nvidia-7185-$(uname -r) linux-restricted-modules-nvidia-100.11.14-$(uname -r) But I think the ** Affects: linux-restricted-modules-2.6.22 (Ubuntu) Importance: Undecided Status: New -- wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time https://bugs.launchpad.net/bugs/136838 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 136838] Re: wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time
After hours of googling, I found the according OpenSuSE 10.3 bug: https://bugzilla.novell.com/show_bug.cgi?id=290385 -- wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time https://bugs.launchpad.net/bugs/136838 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 136838] Re: wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time
While searching for a solution to the X-slow-after-resume problem, I found, say another workaround: In NVidia's Forum, on http://www.nvnews.net/vbulletin/showthread.php?t=72490 gives some hints. As it is impossible to remove linux-restricted-modules-* without lateral damage, the crucial step seems to be to edit /etc/default/linux-restricted-modules-common and add the nvidia modules to the DISABLED_MODULES list: Despite NVida recommends... DISABLED_MODULES=nv nvidia_new ... I 'd rather use ... DISABLED_MODULES=nv nvidia nvidia_new I also clearied all NVidia traces from ubunut binary packages, as suggested (but did not remove linux-restricted-modules-* of course). Still, this is not a real solution for common ubuntu users. But I see a third solution now: Perhaps there is or should be a list of PCI IDs that maps NVidia cards to NVidia driver generation. Probably there are already some 100 lists of vendor and/or device IDs for PCI[e], USB, PCI, IEEE1394 and BlueTooth, but what's one more ;- -- wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time https://bugs.launchpad.net/bugs/136838 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 136838] Re: wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time
Voila: # ls -al /lib/linux-restricted-modules total 24 drwxr-xr-x 4 root root 4096 2007-09-02 22:27 . drwxr-xr-x 18 root root 12288 2007-09-01 19:52 .. drwxr-xr-x 17 root root 4096 2007-08-23 20:39 2.6.22-10-generic drwxr-xr-x 17 root root 4096 2007-08-23 20:29 2.6.22-9-generic I don't think modules from 2.6.22-9-generic could be loaded in 2.6.22-10-generic? I am gonna try puring the 2.6.22-9-generic stuff and boot again. -- wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time https://bugs.launchpad.net/bugs/136838 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 136838] Re: wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time
Sorry for the SuSE link, that one concerns the X-slow-after-resume problem, not this module related one. -- wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time https://bugs.launchpad.net/bugs/136838 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 136838] Re: wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time
Purging all 2.6.22-9-generic stuff did not prevent the loading of the 7185 driver. -- wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time https://bugs.launchpad.net/bugs/136838 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 136838] Re: wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time
One addition: I am currently with gutsy i386 usually, but the 100 Gig drive allows me to have installations of gutsy amd64, feisty i386 and feisty amd64 on the same machine. Due to the far-too-new hardware I don't start feisty often, I usually switch betwenn gutsy i386 (provides Opera, Skype, realplayer) and gutsy amd64 (uses the full 4 Gig, but VMWare does not work, some apps are missing). What I want to say: The problem is the same in my i386 and amd64 installations. -- wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time https://bugs.launchpad.net/bugs/136838 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 136838] Re: wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time
Initially I used the binary package nvidia-glx-new with NVIDIA*.run run over it (due to a .so file missing in the binary .deb). Now I am using _only_ a manual installed NVidia driver. All of these variants share the same problem, only adding nvidia to DISABLED_MODULES in /etc/default/linux-restricted-modules-common did the trick within the rules (manual module change kind of does not count). -- wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time https://bugs.launchpad.net/bugs/136838 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 136838] Re: wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time (manual install)
I did'nt go with both ways at the same time. But I could not go the .deb only way, because the nvidia-glx-new 100.11.14 package is still incomplete (#98641) and I can see this one kind of depends on #98641 and perhaps other nvidia-glx-* bugs. And there is of course the possibility that the final nvidia-glx-new package might fix this module problem, too. Is there (in launchpad) a way to let this issue depend on i.e. #98641 (and put this on hold) or do you prefer to close this bug and I just open a new bug in case an otherwise clean nvidia-glx-new/restricted- modules combination should not solve this old-module problem? -- wrong nvidia kernel module (7185 instead of 100.11.14) loads at boot time (manual install) https://bugs.launchpad.net/bugs/136838 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 122560] Re: no sound with 82801H (ICH8 Family) HD Audio Controller
I don't think the Tribe 5 CD can contain Tim's new packages which seems to work for most of us. (Yet one has to unmute the channels manually) Have you installed the updates form the net archives? -- no sound with 82801H (ICH8 Family) HD Audio Controller https://bugs.launchpad.net/bugs/122560 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 130325] Re: glxgears, 3d apps, crash X when using compiz-fusion (gutsy) (nvidia-glx-new 9755)
I had the same glx-crahses described above even without compiz. My solution (for i386 and for amd64 architecture) was to supress AIGLX (from Xorg 7.1 I think) and allow the Nvidia driver to use it's own NV-GLX: $ grep -i glx /var/log/Xorg.0.log (II) LoadModule: glx (II) Loading /usr/lib/xorg/modules/extensions//libglx.so (II) Module glx: vendor=NVIDIA Corporation (II) NVIDIA GLX Module 100.14.11 Wed Jun 13 18:58:58 PDT 2007 (II) Loading extension GLX (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is (==) NVIDIA(0): Disabling 32-bit ARGB GLX visuals. (II) Loading extension NV-GLX (II) Initializing extension GLX I am not sure which xorg.conf option is the crucial one, running NVIDIA-Linux-x86-100.14.11-pkg1.run resp. NVIDIA-Linux-x86_64-100.14.11-pkg2.run did something. I attach my xorg.conf (Gutsy i386, all updates), however it could be the crucial step is somewhere else. ** Attachment added: Xorg.conf leading nvidia driver to use NV-GLX instead of AIGLX http://launchpadlibrarian.net/9075917/xorg.conf -- glxgears, 3d apps, crash X when using compiz-fusion (gutsy) (nvidia-glx-new 9755) https://bugs.launchpad.net/bugs/130325 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 126369] Re: kernel disables irq after 10 minutes
It seems I do not have this problem on my T61p. However, when I turned it on for the very first time last week, I changed the BIOS settings (for PCI-IRQ assignment) from IRQ 11 (for every single one of the ~8 listed devices or channels) to Auto, just on an old Geek's instinct. If the BIOS is serious about running everything through IRQ11, any OS has the right to be irritated. What does your /proc/interrupts tell you? (Applies to all T6x users here) -- kernel disables irq after 10 minutes https://bugs.launchpad.net/bugs/126369 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 126369] Re: kernel disables irq after 10 minutes
The only USB device I use regular is an external mouse. It might even be that my kernel also disables the IRQ but lacks negative effects. I am gonna take a look to my logs when I am back in office some time tomorrow. -- kernel disables irq after 10 minutes https://bugs.launchpad.net/bugs/126369 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 122560] Re: no sound with 82801H (ICH8 Family) HD Audio Controller
This package solved the problem for me (1 week old Lenovo T61p). Many many thanks! -- no sound with 82801H (ICH8 Family) HD Audio Controller https://bugs.launchpad.net/bugs/122560 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 112702] Re: vmware-server : guest can't access server and vis-versa
I failed to reproduce the problem in a 32-bit environment (early Athlon 1.33 GHz). I suppose the problem is restricted to 64-bit installations. -- vmware-server : guest can't access server and vis-versa https://bugs.launchpad.net/bugs/112702 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 106649] Re: Restricted-Manager installs older nvidia-glx package (not -new)
Unfortunately there are cards that seem to work only with the nvidia- glx-new driver. I have a brand new 7600 GS, lspci says: VGA compatible controller: nVidia Corporation G70 [GeForce 7600 GS] (rev a1) From manual playing with feisty beta (apt-get dist-upgraded from edgy) I knew that only the -new package would work (although even that did not work really, I must have got a bad combination of beta packages; but at least the nvidia-glx-new driver did not refuse the device and the nvidia module did load). When re-installing the machine with feisty final (somehow the dist-upgraded state misbelieved to be up-to-date, perhaps just played around to close to the release), I tried out the restricted-manager (nice work by the way!), and although I had the nvidia-glx-new package installed already, the restricted-manager installed nvidia-glx (and of course removed nvidia-glx-new). X did not come up again of course, but xorg.conf has been modified correctly, so after I reinstall nvidia-glx-new via apt-get and without any other manual config of any kind , I now seem to have a perfect situation with 3D support and everything working. After installing some lib32 packages (with reinstallation unavoidable, I finally decided to give the amd64 release a try once again), GoogleEarth (My reference test for the graphics system, and 32bit) runs perfectly and is now not only usable but really fun to play with. -- Restricted-Manager installs older nvidia-glx package (not -new) https://bugs.launchpad.net/bugs/106649 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 50872] Re: aptitude update + aptitude upgrade on fresh dapper replaces grub with unconfigured lilo
Sorry for my delayed response, somehow I must have overlooked the mail about your question. As far as my virtual machine test shows, this problem also seems to have been solved in the meantime. -- aptitude update + aptitude upgrade on fresh dapper replaces grub with unconfigured lilo https://launchpad.net/bugs/50872 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50865] Re: dapper installer insists on partition table change
Sorry for my delayed response, somehow I must have overlooked the mail about your question. As all my edgy installations are dapper installations updated live, so I just made a quick test with a VMWare virtual machine (installed edgy, shutdown, pretended install again), and it seems the problem has gone away. -- dapper installer insists on partition table change https://launchpad.net/bugs/50865 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50865] dapper installer insists on partition table change
Public bug reported: If installing 6.06 (dapper) on a system with an already satisfying partition situation (e.g. when replacing another linux), (i.e. one does manual partitioning and only assigns mount points) the installer won't continue beyond the partitioning step. This problem seems to apply to any i386 and amd64 installation CD. There is an easy workaround: Doing some dummy change to the partition table, e.g. changing a boot flag and changing it back, satisfies the installer. Nevertheless, this bug is a very bad one, because many people trying to switch from whatever linux to Ubuntu might give up at that point and damn Ubuntu for some time. ** Affects: Ubuntu Importance: Untriaged Status: Unconfirmed -- dapper installer insists on partition table change https://launchpad.net/bugs/50865 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
