[Bug 183456] Re: Trying to load a sf2 file with asfxload returns "sfxload: no memory left"
I don't quite understand your comment. The above "fix" applies to the AMD64 platform. There is no such thing as a 32bit DMA zone on x86, but still the kernel might want to allocate physical addresses for the buffer memory beyond the 2GB barrier (bit 31 set), thus it is prone to failure in any system equipped with more than 2GB of RAM. Sure enough, a *small* soundfont could be loaded if enough memory is available in the 16MB DMA zone, but this depends on a lot of other factors (as, for example, which other devices require DMA memory). So long, Thomas -- Trying to load a sf2 file with asfxload returns "sfxload: no memory left" https://bugs.launchpad.net/bugs/183456 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 183456] Re: Trying to load a sf2 file with asfxload returns "sfxload: no memory left"
The problem with this goes a bit deeper. The reason for all this trouble is that the emu10k1 chipset requires DMA from main memory to pick up the samples, and - unfortunately - the DMA engine of the chip is broken. Instead of using the full range of 32 bit DMA available on the PCI bus, it only addresses 31 bit of the 32 available. To work around this problem, the kernel driver first allocates a page of main memory, signaling the 32 bit DMA memory "zone", i.e. indicating the kernel that it requires 32 bit memory in a 64 bit memory system. However, if now the returned memory happens to have bit 31 set, the emu10k1 wouldn't be able to address the memory. Then, the driver releases the memory again, and requests memory in the 16MB "ISA" memory region, which is clearly suitable for the chip. Unfortunately, this type of memory runs out easily, and then the chip is left with no usable memory at all. The problem is that the kernel isn't smart enough to provide memory that is "just right" for the chip, i.e. the "DMA zone" allocation isn't quite sufficient for this situation. There seem to be plans on the LKLM to address this, but it's unclear how long this will take - after all, the complete kernel page allocator must be re-structured to fix this. How to work around? Oh well, the easiest is to lower the 32bit PCI DMA zone from 4G to 2G. This means that some non-broken devices will require to allocate pages in the 2GB region (bad enough), and the memory layout might be sub-optimal for those devices, but at least the hack will work. For that, download the kernel, and edit arch/x86/include/asm/dma.h, locate the line: #define MAX_DMA32_PFN ((4UL * 1024 * 1024 * 1024) >> PAGE_SHIFT) and replace the 4UL by a 2UL, which will shrink the 32-bit DMA zone by half. This is not a permanent solution - it's an ugly bad hack that is "good enough for me". There is no kernel boot option to do this AFAIK. So long, happy hacking, Thomas -- Trying to load a sf2 file with asfxload returns "sfxload: no memory left" https://bugs.launchpad.net/bugs/183456 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 183456] Re: Trying to load a sf2 file with asfxload returns "sfxload: no memory left"
Well, simply re-allocating doesn't help since this will get it exactly the same memory as before - so it had to fetch memory over and over again until it succeeds, and then had to release all the unusable memory again. Possible, but would require it to fetch at most 2GB of memory (urgh!) just for nothing, plus the overhead, and the time needed to do the allocation and to loop for all that to happen. Remember, these are 2G/4K = 524288 allocations to be done! I'd say the problem should really fixed at its origin. For first, the emu10k1 is broken - too bad, a rather good card otherwise - I've two of them. And if replacing that is not an option (which it isn't for me), I'd say that the kernel should really provide better mechanisms to allocate the right memory. So long, Thomas -- Trying to load a sf2 file with asfxload returns "sfxload: no memory left" https://bugs.launchpad.net/bugs/183456 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 592749] [NEW] Ubuntu update kills boot loader
Public bug reported: Hi, I had the Windows 7 bootloader configured to dual boot either Windows 7 or Ubuntu 10.04. The Grub2 bootloader was installed to the Linux (ext4) partition while the Windows bootloader was installed to the MBR and first primary partition. Everything worked fine for about 5 weeks, i.e. in the Windows bootloader I could select either Windows or Linux. When selecting Linux, it would chain-load grub and boot into Ubuntu. Now I allowed Update Manager for the first time to update Ubuntu and guess what: it now boots into Ubuntu right away. The boot menu does not appear. Apparently the grub update has overwritten the MBR. WTF!! (Sorry, but this is really incredible!) br Tom P.S. This were all fresh installations on a newly built machine. ** Affects: ubuntu Importance: Undecided Status: New -- Ubuntu update kills boot loader https://bugs.launchpad.net/bugs/592749 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 1907701] [NEW] package elpa-magit 2.90.1-2 failed to install/upgrade: »installiertes elpa-magit-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 2 zurück
Public bug reported: installation failed but in could be reinstalled. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: elpa-magit 2.90.1-2 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 10 16:57:45 2020 ErrorMessage: »installiertes elpa-magit-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 2 zurück InstallationDate: Installed on 2020-11-08 (32 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: magit Title: package elpa-magit 2.90.1-2 failed to install/upgrade: »installiertes elpa-magit-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 2 zurück UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: magit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907701 Title: package elpa-magit 2.90.1-2 failed to install/upgrade: »installiertes elpa-magit-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 2 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magit/+bug/1907701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 183456] Re: Trying to load a sf2 file with asfxload returns "sfxload: no memory left"
Look, what else to say? The patch is there, it has been confirmed to work, and it still works here. See #10 on this list. If the Ubuntu team does not want to pick it up, nor the kernel team wants to pick it up, nothing will happen. If anyone is having a better fix, also go along. Until then, see #10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/183456 Title: Trying to load a sf2 file with asfxload returns "sfxload: no memory left" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awesfx/+bug/183456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 183456] Re: Trying to load a sf2 file with asfxload returns "sfxload: no memory left"
Raymond wrote: > you have to change max_buffer_size if you want to load a larger > soundfont as default value is 128Mb The issue is not with the size of the soundfont. The issue is that the kernel tries to put them into the 16MB ISA DMA zone, being short of memory below 2GB. Here's the technical explanation: The kernel first tries to allocate 32bit memory for the soundfont. It then checks whether the allocated memory is above the 2GB barrier. Having a hardware bug in the emu10k1, the hardware can only support DMA from the lowest 2GB of memory because it simply ignores bit 31 of the address. The memory allocator then comes back with memory which is, due to the memory allocation policy, *above* the 2GB barrier whenever more than 2GB is installed in the system. This, of course, won't work, and the kernel/emu10k1 driver notices this, releases the memory and then tries next to take the memory from the 16MB ISA zone. Of course, there isn't enough memory available to load the soundfont, which then fails. There is a fix, namely shorten the kernel 32bit DMA zone to 2GB, namely replace in arch/x86/include/asm.h the following line: #define MAX_DMA32_PFN ((2UL * 1024 * 1024 * 1024) >> PAGE_SHIFT) here the 4UL has been replaced by a 2UL, which does the indicated reduction of the 32bit DMA memory, and brings the emu10k1 back to work. It has no other drawbacks, i.e. the machine is working with correspondingly patched kernels for over a year by now. The true fix would be to make the memory allocation of the kernel a bit more flexible than it is now. Greetings, Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/183456 Title: Trying to load a sf2 file with asfxload returns "sfxload: no memory left" -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 183456] Re: Trying to load a sf2 file with asfxload returns "sfxload: no memory left"
Raymond wrote: > I can load more than 16Mb soundfont into my sb live! platinum ct4760p on > my 32bits machines, so Is this bug specific to 64bits machine only > No, it is specific to machines with more than 2GB memory. Please see my report. Merry Christmas Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/183456 Title: Trying to load a sf2 file with asfxload returns "sfxload: no memory left" -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 183456] Re: Trying to load a sf2 file with asfxload returns "sfxload: no memory left"
SnEptUne wrote: > Using gentoo-sources-2.6.36-r3. > > Changing arch/x86/include/asm/dma.h fixed it for me, but I don't know if > this change would affect system stability. Not for me, at least. I'm working with this configuration for more than a year now without any bad side effects. What will happen, of course, is that the kernel will copy data outside of the (then smaller) 2GB DMA region to the 2GB DMA region, even for hardware that is fully 32-bit DMA capable. Note that hardware that supports 64 bit addresses for DMA is unaffected. Greetings, Thomas -- Trying to load a sf2 file with asfxload returns "sfxload: no memory left" https://bugs.launchpad.net/bugs/183456 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 1429604] [NEW] Removing OpenSSL removes Ubuntu Desktop and print support
Public bug reported: On a fully updated, unmaniputed Ubuntu 14.04, Removing OpenSSL removes Ubuntu Desktop and print support. Looks like "dependency destater" strikes again. $ apt-get remove openssl Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: apturl bluez-cups ca-certificates checkbox-gui checkbox-ng checkbox-ng-service cups cups-core-drivers cups-daemon hplip nautilus-share oneconf oneconf-common openssl printer-driver-gutenprint printer-driver-hpcups printer-driver-postscript-hp printer-driver-splix python-cupshelpers python-httplib2 python-oneconf python-piston-mini-client python-requests python-ubuntu-sso-client python3-checkbox-ng python3-httplib2 python3-oneconf python3-piston-mini-client python3-requests software-center software-center-aptdaemon-plugins software-properties-common software-properties-gtk ssl-cert system-config-printer-common system-config-printer-gnome system-config-printer-udev ubuntu-desktop ubuntu-sso-client ubuntu-sso-client-qt 0 upgraded, 0 newly installed, 40 to remove and 14 not upgraded. After this operation, 20,2 MB disk space will be freed. Do you want to continue? [Y/n] n Abort. ** Affects: linux-source-2.6.15 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429604 Title: Removing OpenSSL removes Ubuntu Desktop and print support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/1429604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 183456] Re: Trying to load a sf2 file with asfxload returns "sfxload: no memory left"
If you have an idea how to activate the 16MB mode for the emu10k1, then this would be pretty helpful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/183456 Title: Trying to load a sf2 file with asfxload returns "sfxload: no memory left" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awesfx/+bug/183456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1034470] Re: Mouse pointer flicker or disappear when moving it with left mouse button down
Similar problem here: mouse flickering when moving over links or clicking, sometimes only re-appears when I move the mouse again. This problem first appeared when I installed a new ATI 7750 gfx card which forced me to switch from Unity 3D to Unity 2D. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1034470 Title: Mouse pointer flicker or disappear when moving it with left mouse button down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-fbdev/+bug/1034470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1098862] Re: Mouse cursor disappears on every redraw with VESA driver
I can confirm this bug also exists with Ubuntu 12.04 stock kernel on real hardware (no VM). I am using an ATI 7750 card which is not supported by any more specific driver yet. Please help. This is really annoying. Thanks/Tom -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1098862 Title: Mouse cursor disappears on every redraw with VESA driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vesa/+bug/1098862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362582]
Ok, so I now fiddled a little bit with the patched kernel and the i2c utilities. In fact, I do get "something like a picture" on this machine. By which I mean that the image is ripped apart, the borders aren't set correctly, but the LVDS is at least detected and the screen is not totally blank. Playing with the i2c utilities showed that on this Fujitsu Siemens the ns2501 (and yes, it really is one) is on chip address 0x38 on bus number 6. I played with i2cset here and there and could disable and enable the screen with register #8, bit #0, but I do not get a usable screen. I do not know enough about DVO chips to be of much help as far as the programming is concerned. What else can be done from here that would help you? I get the following from /var/log/messages: [7.272103] [drm:intel_opregion_setup], graphic opregion physical addr: 0x0 [7.272113] [drm:intel_opregion_setup], ACPI OpRegion not supported! [7.272140] [drm:i915_init_phys_hws], Enabled hardware status page [7.272156] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [7.272162] [drm] Driver supports precise vblank timestamp query. [7.272176] [drm:init_vbt_defaults], Set default to SSC at 66MHz [7.272414] [drm:parse_general_features], BDB_GENERAL_FEATURES int_tv_support 1 int_crt_support 0 lvds_use_ssc 0 lvds_ssc_freq 48 display_clock_mode 0 [7.272430] [drm:parse_general_definitions], crt_ddc_bus_pin: 2 [7.272441] [drm:parse_sdvo_device_mapping], different child size is found. Invalid. [7.272450] [drm:parse_device_mapping], different child size is found. Invalid. [7.272476] [drm:intel_dsm_pci_probe], no _DSM method for intel device [7.272516] [drm:intel_modeset_init], 2 display pipes available. [7.272539] [drm:intel_modeset_init], plane 0 init failed: -19 [7.272555] [drm:intel_modeset_init], plane 1 init failed: -19 [7.272570] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [7.272899] device: 'card0-VGA-1': device_add [7.272935] PM: Adding info for No Bus:card0-VGA-1 [7.274750] i2c i2c-6: master_xfer[0] W, addr=0x38, len=1 [7.274763] i2c i2c-6: master_xfer[1] R, addr=0x38, len=1 [7.275659] [drm:sil164_init], sil164 not detected got 5: from i915 gmbus dpb Slave 56. [7.275676] i2c i2c-6: master_xfer[0] W, addr=0x76, len=1 [7.275686] i2c i2c-6: master_xfer[1] R, addr=0x76, len=1 [7.275921] i2c i2c-6: NAK from device addr 0x76 msg #0 [7.275961] i2c i2c-6: master_xfer[0] W, addr=0x38, len=1 [7.275970] i2c i2c-6: master_xfer[1] R, addr=0x38, len=1 [7.276900] i2c i2c-6: master_xfer[0] W, addr=0x38, len=1 [7.276911] i2c i2c-6: master_xfer[1] R, addr=0x38, len=1 [7.291048] [drm:ns2501_init], init ns2501 dvo controller successfully! [7.291088] device: 'card0-DVI-I-1': device_add [7.291138] PM: Adding info for No Bus:card0-DVI-I-1 [7.295247] i2c i2c-6: master_xfer[0] W, addr=0x38, len=1 [7.295260] i2c i2c-6: master_xfer[1] R, addr=0x38, len=1 [7.296382] [drm:i915_get_vblank_timestamp], crtc 0 is disabled [7.301363] [drm:intel_update_fbc], [7.301375] [drm:i915_get_vblank_timestamp], crtc 1 is disabled [7.306349] [drm:intel_update_fbc], [7.311054] [drm] initialized overlay support [7.311268] i2c i2c-6: master_xfer[0] W, addr=0x38, len=1 [7.311279] i2c i2c-6: master_xfer[1] R, addr=0x38, len=1 [7.311520] i2c i2c-6: NAK from device addr 0x38 msg #0 [7.311556] [drm:ns2501_readb], Unable to read register 0x08 from i915 gmbus dpb:38. [7.311579] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:5:VGA-1] [7.311594] i2c i2c-3: master_xfer[0] W, addr=0x50, len=1 [7.311604] i2c i2c-3: master_xfer[1] R, addr=0x50, len=1 [7.311843] i2c i2c-3: NAK from device addr 0x50 msg #0 [7.311882] [drm:intel_get_load_detect_pipe], [CONNECTOR:5:VGA-1], [ENCODER:6:DAC-6] [7.311893] [drm:intel_get_load_detect_pipe], creating tmp fb for load-detection [7.311930] [drm:drm_crtc_helper_set_mode], [CRTC:3] [7.311944] i2c i2c-6: master_xfer[0] W, addr=0x38, len=1 [7.311954] i2c i2c-6: master_xfer[1] R, addr=0x38, len=1 [7.312229] i2c i2c-6: NAK from device addr 0x38 msg #0 [7.312265] [drm:ns2501_readb], Unable to read register 0x08 from i915 gmbus dpb:38. [7.319657] [drm:i9xx_crtc_mode_set], Mode for pipe A: [7.319667] [drm:drm_mode_debug_printmodeline], Modeline 0:"640x480" 0 31500 640 664 704 832 480 489 491 520 0x10 0xa [7.352750] [drm:i9xx_update_plane], Writing base 0002 0 0 2560 [7.352771] [drm:intel_update_fbc], [7.352781] [drm:i830_get_fifo_size], FIFO size - (0x00017e5f) A: 47 [7.352792] [drm:intel_calculate_wm], FIFO entries required for mode: 20 [7.352800] [drm:intel_calculate_wm], FIFO watermark level: 25 [7.352809] [drm:i830_update_wm], Setting FIFO watermarks - A: 25 [7.352823] [drm:drm_crtc_helper_set_mode], [ENCODER:6:DAC-6] set [MODE:0:640x480]
[Bug 362582]
Well, I do have a documentation from National Semiconductors, but there is nothing that would define frequencies or bandwidths - only the sync pulses can be set, and intput to syncs. So I played writing values into all other registers with i2cset, but with little success - not any change, actually, except for the mentioned register. Ok, and you could block off the screen as well by disabling the sync pulses (not much of a surprise, I guess). However, leaving all that aside - I'm no longer able to talk to the chip, upon rebooting i2cdetect gave me all blanks on bus #6. I really wonder what is going on. Could it be that there is some additional "gating" going on that blocks off access to this chip unless another register is set? Is that typical? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/362582 Title: [i830] [Needs DVO-LVDS] Installer unable to launch Xorg on Fujitsu Stylistic ST4120PW To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/362582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362582]
Sorry if this sounds like a stupid question - but how come that i2cdetect only sees one bus when booting with the vga frame buffer, but 7 with the i915drm module in place? Is there anything I need to do to activate the remaining busses (not devices! - that will be the next problem - it is also a problem that bus #6 does not always lists the ns2501). A second remark is that I found that the documentation I have on the ns2501 does not include the registers for the scaler (*sigh*), so that's my fault. I'll see what I can find. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/362582 Title: [i830] [Needs DVO-LVDS] Installer unable to launch Xorg on Fujitsu Stylistic ST4120PW To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/362582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362582]
But as the drm module is never loaded, the corresponding i2c devices are not exposed? Can I trigger this process manually without loading the drm module? The idea was to check which values the bios leaves behind, and then install the same (or similar) values. Concerning the scaler, the 2501 datasheet mentiones that it includes a built-in scaler, though its interface is not described. "OEM manufacturers please contact your NS representative". Hmm. Do you mean that the built-in scaler is present, though its interface is driven by pins that are controlled by the GPU, and thus are not exposed to its own i2c interface? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/362582 Title: [i830] [Needs DVO-LVDS] Installer unable to launch Xorg on Fujitsu Stylistic ST4120PW To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/362582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362582]
Well, I've got a bit futher: 1) One can get i2c access mostly reliable when the drm.debug option is set high. Thus, whether or not the i2c interface works is likely a matter of timing. Could it be that the bit-banging interface is too critical to reach the chip in all cases? If so, where could one set the timing? 2) I can get a stable picture by using the video bios to write the chip configuration for me. For this, use $ vbetool post $ vbetool vbemode set 280 I also performed an i2c dump with and without the mode set through the video bios: Properly initialized through the video bios: 0 1 2 3 4 5 6 7 8 9 a b c d e f0123456789abcdef 00: 05 13 26 67 01 a5 19 a2 35 95 81 ff 03 04 00 00??&g5??.??.. 10: 00 a0 02 02 02 02 02 02 07 00 00 11 54 03 02 40...?T??@ 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 03 ff 00 44 88 88 00 00 00 00 00 00?..D??.. 40: 80 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00?..? 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 11 00 00 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0?..? 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 18 00..?. 80: ff 07 3d 05 00 00 00 00 00 00 00 00 10 02 10 00.?=????. 90: ff 07 a0 02 00 00 05 00 00 00 88 00 24 00 25 03.???..?...?.$.%? a0: 28 01 28 05 84 00 00 00 00 04 70 4f 00 00 03 03(?(???pO..?? b0: 00 00 00 00 00 00 09 03 00 a0 00 20 33 33 33 33..??.?. c0: 01 90 00 0f 03 16 00 02 02 00 00 00 00 00 00 00??.???.??... d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 1a 00 80 00 00 00 80 00 00 00 00 00 00 00..?.?...?... f0: 86 eb ca 90 00 00 00 88 0a 00 0a 0a 0a 0a 0a 0a...??.?? Improperly initialized (initially): 0 1 2 3 4 5 6 7 8 9 a b c d e f0123456789abcdef 00: 05 13 26 67 01 a5 19 a2 31 95 81 ff 03 04 00 00??&g1??.??.. 10: 00 a0 02 02 02 02 02 02 07 00 00 11 54 03 02 40...?T??@ 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 03 ff 00 28 88 88 00 00 00 00 00 00?..(??.. 40: 80 00 00 80 00 00 00 00 00 00 00 00 00 00 00 00?..? 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 11 00 00 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0 f0?..? 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 18 00..?. 80: ff 07 3d 05 00 00 00 00 00 00 00 00 10 02 10 00.?=????. 90: ff 07 a0 02 00 00 05 00 00 00 88 00 24 00 25 03.???..?...?.$.%? a0: 28 01 28 05 84 00 00 00 00 04 70 4f 00 00 03 03(?(???pO..?? b0: 00 00 00 00 00 00 09 03 00 a0 00 20 33 33 33 33..??.?. c0: 05 90 00 0f 03 16 00 02 02 00 00 00 00 00 00 00??.???.??... d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 1a 00 80 00 00 00 80 00 00 00 00 00 00 00..?.?...?... f0: 8f 07 58 90 00 00 00 88 0a 00 0a 0a 0a 0a 0a 0a??X?...??.?? Differences are in registers 0x44 and 0xc0 which must contain 0x37 and 0x01, respectively. Just using i2cset to define these registers alone does not seem to help, though the "screen ripping" looks different. Register 0xc0 seems to be related to the screen scaler, at least bits 7,2 and 0 do have a function, though I do not know which. With a couple of vbemode calls issued from a remote console, I could play a round of tuxracer. Given that this is a 1Ghz Pentium III, 10 fps are quite acceptable and I believe that this means that this is accelerated video. So basically, the dvo chip kernel module should "just" call the video bios to set the screen to the proper dimensions, and should then the chip untouched - this might properly work. Of course, you wouldn't have xrandr support with all that as the resolution would stay fixed, but there would be hardware acceleration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/362582 Title: [i830] [Needs DVO-LVDS] Installer unable to launch Xorg on Fujitsu Stylistic ST4120PW To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/362582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 183456] Re: Trying to load a sf2 file with asfxload returns "sfxload: no memory left"
The problem is not which DMA mask the kernel assigns to the module. The problem is what the kernel does if the memory to be accessed via the emu10k1 DMA is *not* in range of the DMA mask. The emu10k1 reaches the 30 bit address space just fine, as my all-day experience tells me. What the kernel driver does is in principle correct - it goes for the 24 bit DMA space (the lowest 16 MB or so). This address range would be reachable by the emu10k1. The problem is just that this memory region is too small to hold a sound font, and then simply fails. The granularity offered by the kernel is too small - there is either the 64 bit space (which is not reachable by PCI anyhow), then the 4GB space, still too large for the emu10k1, and then the 16MB ISA space, which is reachable, but too small to be useful. Thus, the kernel memory architecture is too unflexible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/183456 Title: Trying to load a sf2 file with asfxload returns "sfxload: no memory left" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awesfx/+bug/183456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 183456] Re: Trying to load a sf2 file with asfxload returns "sfxload: no memory left"
Sorry, but I don't waste my time there. I believe I reported this problem already several years ago, and it was basically ignored or the patch wasn't accepted. To some degree, I understand this because it doesn't address the *real* problem (which is the unflexibility of the kernel memory allocation mechanism), but then again, I'm not knowledgable enough to provide a fix for that (namely a re-design of the kernel allocation). So no-go, and it went nowhere. If you want to make your own experiences with the helpfulness of the linux kernel team, you surely have my appreciation, please go ahead and report it. For all others that just want to have a working sound blaster and don't care about arguing with the kernel hackers, a patch is here, even instructions how to apply it thanks to Jakob. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/183456 Title: Trying to load a sf2 file with asfxload returns "sfxload: no memory left" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awesfx/+bug/183456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362582]
Now two weeks passed, I submitted five versions for a patch of this bug to the mailing list, one here in public, yet nothing shows up in the official git repository at all. Is it just me or is nobody actually interested in getting this working? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/362582 Title: [i830] [Needs DVO-LVDS] Installer unable to launch Xorg on Fujitsu Stylistic ST4120PW To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/362582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362582]
Now I also got the scaler "pseudo-working" by inspecting which values
the vesa BIOS leaves behind in the DVO and just copying these values. By
now I can support 640x480, 800x600 and the native resolution, which is
here 1024x768. Unfortunately, I do not have the right vesa BIOS data for
the latter, and for anything else, so your milage may vary. Also, the
scaler support is somehow hacky as the DVO first needs to be turned on
by enabling the PLL by poking into the chipset registers (yuck!). It's
really a beasty chip.
I will submit the patch to the mailing list later this day, here for
your records:
diff -rup linux-3.4.1-orig/drivers/gpu/drm/i915/dvo.h
linux-3.4.1/drivers/gpu/drm/i915/dvo.h
--- linux-3.4.1-orig/drivers/gpu/drm/i915/dvo.h 2012-06-01 09:18:44.0
+0200
+++ linux-3.4.1/drivers/gpu/drm/i915/dvo.h 2012-06-08 13:15:19.0
+0200
@@ -140,5 +140,6 @@ extern struct intel_dvo_dev_ops ch7xxx_o
extern struct intel_dvo_dev_ops ivch_ops;
extern struct intel_dvo_dev_ops tfp410_ops;
extern struct intel_dvo_dev_ops ch7017_ops;
+extern struct intel_dvo_dev_ops ns2501_ops;
#endif /* _INTEL_DVO_H */
diff -rup linux-3.4.1-orig/drivers/gpu/drm/i915/dvo_ns2501.c
linux-3.4.1/drivers/gpu/drm/i915/dvo_ns2501.c
--- linux-3.4.1-orig/drivers/gpu/drm/i915/dvo_ns2501.c 2012-06-08
17:59:20.0 +0200
+++ linux-3.4.1/drivers/gpu/drm/i915/dvo_ns2501.c 2012-06-08
17:52:21.0 +0200
@@ -0,0 +1,544 @@
+/**
+
+Copyright © 2012 Gilles Dartiguelongue, Thomas Richter
+
+All Rights Reserved.
+
+Permission is hereby granted, free of charge, to any person obtaining a
+copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sub license, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice (including the
+next paragraph) shall be included in all copies or substantial portions
+of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
+OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
+IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+**/
+
+#include "dvo.h"
+#include "i915_reg.h"
+#include "i915_drv.h"
+
+#define NS2501_VID 0x1305
+#define NS2501_DID 0x6726
+
+#define NS2501_VID_LO 0x00
+#define NS2501_VID_HI 0x01
+#define NS2501_DID_LO 0x02
+#define NS2501_DID_HI 0x03
+#define NS2501_REV 0x04
+#define NS2501_RSVD 0x05
+#define NS2501_FREQ_LO 0x06
+#define NS2501_FREQ_HI 0x07
+
+#define NS2501_REG8 0x08
+#define NS2501_8_VEN (1<<5)
+#define NS2501_8_HEN (1<<4)
+#define NS2501_8_DSEL (1<<3)
+#define NS2501_8_BPAS (1<<2)
+#define NS2501_8_RSVD (1<<1)
+#define NS2501_8_PD (1<<0)
+
+#define NS2501_REG9 0x09
+#define NS2501_9_VLOW (1<<7)
+#define NS2501_9_MSEL_MASK (0x7<<4)
+#define NS2501_9_TSEL (1<<3)
+#define NS2501_9_RSEN (1<<2)
+#define NS2501_9_RSVD (1<<1)
+#define NS2501_9_MDI (1<<0)
+
+#define NS2501_REGC 0x0c
+
+struct ns2501_priv {
+ //I2CDevRec d;
+ bool quiet;
+ int reg_8_shadow;
+ int reg_8_set;
+ // Shadow registers for i915
+ int dvoc;
+ int pll_a;
+ int srcdim;
+ int fw_blc;
+};
+
+#define NSPTR(d) ((NS2501Ptr)(d->DriverPrivate.ptr))
+
+/*
+** Include the PLL launcher prototype
+*/
+extern void intel_enable_pll(struct drm_i915_private *dev_priv, enum pipe
pipe);
+
+/*
+** For reasons unclear to me, the ns2501 at least on the Fujitsu/Siemens
+** laptops does not react on the i2c bus unless
+** both the PLL is running and the display is configured in its native
+** resolution.
+** This function forces the DVO on, and stores the registers it touches.
+** Afterwards, registers are restored to regular values.
+**
+** This is pretty much a hack, though it works.
+** Without that, ns2501_readb and ns2501_writeb fail
+** when switching the resolution.
+*/
+
+static void enable_dvo(struct intel_dvo_device *dvo)
+{
+ struct ns2501_priv *ns = (struct ns2501_priv *)(dvo->dev_priv);
+ struct i2c_adapter *adapter = dvo->i2c_bus;
+ struct intel_gmbus *bus = container_of(adapter,
+ struct intel_gmbus,
+ adapter);
+ struct drm_i915_private *dev_priv = bus->dev_priv;
+
+ DRM_DEBUG_KMS("%s: Trying to
[Bug 1005263] Re: Bug reporting pages is hidden
Confirmed, link is now working (it wasn't at the time of filing the bug). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005263 Title: Bug reporting pages is hidden To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1005263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362582]
Got a step further. What one can do to get a stable picture is simply to disable the scaler. For this, insert: in dvo_ns2501.c, in the function static void ns2501_mode_set the following line: ns2501_writeb(dvo, 0x08, NS2501_8_PD | NS2501_8_BPAS | NS2501_8_VEN | NS2501_8_HEN); ns2501_dpms should also et the NS2501_8_BPAS bit. Voila, I get a stable console at boot-up, and a 2D desktop. However, something still seems to be seriously broken outside of the control of the DVO driver. As soon as I start an X session, or a 3D application like tuxracer, the display vanishes. At that point, the DVO also vanishes from the i2c bus for reasons unclear to me. A vbetool post restores the i2cbus. So at least there seems to be something seriously broken with the i2c communication on this board. It also happenes that I could start the desktop, but something was wrong with EXA as characters were printed on top of each other (overlayed) instead of erased properly. glxgears seemed to work (at least once). So what is it with the i2c bus on this system? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/362582 Title: [i830] [Needs DVO-LVDS] Installer unable to launch Xorg on Fujitsu Stylistic ST4120PW To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/362582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362582]
Finally, success!
I'm not quite sure why, but for reasons unclear to me the DVO chip only
wants to talk if the PLL is enabled and running and the screen
resolution fits. In addition, the system has apparently a "fake" VGA
output that must be disabled to have the system working properly.
Otherwise, the KMS layer seems to want to redirect the output to the
VGA, and then drops dead, leaving an unusable screen (and DVO!) behind.
I do not know yet whether the physical VGA connector works, but
basically, here is the receipt:
1) Apply the patches I mentioned above. Especially, the bypass mode of
the scaler must be set as its function is unclear.
static void ns2501_dpms(struct intel_dvo_device *dvo, int mode)
{
struct ns2501_priv *ns = (struct ns2501_priv *)(dvo->dev_priv);
unsigned char ch;
DRM_DEBUG_KMS("%s: Trying set the dpms of the DVO to
%d\n",__FUNCTION__,mode);
if (ns->reg_8_set) {
ch = ns->reg_8_shadow;
} else {
ch = NS2501_8_PD | NS2501_8_BPAS | NS2501_8_VEN | NS2501_8_HEN;
}
if (mode == DRM_MODE_DPMS_ON)
ch |= NS2501_8_PD;
else
ch &= ~NS2501_8_PD;
ch |= NS2501_8_BPAS;
if (ns->reg_8_set == 0 || ns->reg_8_shadow != ch) {
ns->reg_8_set= 1;
ns->reg_8_shadow = ch;
ns2501_writeb(dvo, NS2501_REG8, ch);
}
}
Here I added a shadow register which is likely not exactly necessary,
though I wanted to avoid the i2c communication if not necessary.
2) There is still a bug in the ns2501 source in so far as the query function
returns something unitialized if reading from the DVO fails. And it fails quite
often.
static enum drm_connector_status ns2501_detect(struct intel_dvo_device *dvo)
{
uint8_t reg9;
enum drm_connector_status status = connector_status_unknown;
struct ns2501_priv *ns = (struct ns2501_priv *)(dvo->dev_priv);
DRM_DEBUG_KMS("%s: Trying to detect the connector
status\n",__FUNCTION__);
if (ns2501_readb(dvo, NS2501_REG9, ®9)) {
if (!(reg9 & NS2501_9_RSEN))
status = connector_status_connected;
else
status = connector_status_disconnected;
ns->reg_9_set= 1;
ns->reg_9_shadow = reg9;
} else if (ns->reg_9_set) {
if (!(ns->reg_9_shadow & NS2501_9_RSEN))
status = connector_status_connected;
else
status = connector_status_disconnected;
}
DRM_DEBUG_KMS("%s: Status is %d\n",__FUNCTION__,status);
return status;
}
Again a shadow register was added.
3) The following kernel arguments should be added to disable the VGA
output:
i915.modeset=1 video=VGA-1:1024x768d video=DVI-I-1:1024x768e
I'm not sure why the system behaives so strange otherwise, I'll try to
dig a bit deeper, but I believe that there is some limitation with the
i830 and its outputs. Probably I'll find a datasheet.
With the above modifications, you cannot, of course, scale the screen
(resolution is fixed), though 3D acceleration works nicely.
The same trick might also apply to the IBM R31, I'll check later next
week - it had similar issues.
(Is actually anyone reading this??? Is there a better way to supply
patches?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/362582
Title:
[i830] [Needs DVO-LVDS] Installer unable to launch Xorg on Fujitsu
Stylistic ST4120PW
To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/362582/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005263] [NEW] Bug reporting pages is hidden
Public bug reported: Goto to https://launchpad.net/ubuntu/+bugs click "Report a bug " near the top right. Now, where can I report a bug here? Your are wasting my time. Big deal! ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005263 Title: Bug reporting pages is hidden To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1005263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005261] [NEW] PS/2 peripherals fail in 10.04 and 12.04
Public bug reported: PS/2 connected mouse and keyboard stop working spontaneously in 12.04. Works again after a reboot. Hard to reproduce, happens rarely. Mainboard is ASUS P7P55D-E. Same problem was already there in 10.04. Really bad ... ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005261 Title: PS/2 peripherals fail in 10.04 and 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1005261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362582]
Ok, I managed to cross-compile the patched kernel sources on a much faster x64 machine, so I now have an initrd and a vmlinuz with the patch in it. I won't have access to the machine until tomorrow. Is this already supposed to do anything interesting, or would anyone just be interested in the debug output? I also found a datasheet from national semiconductor for the DS90C2501, is this the right one? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/362582 Title: [i830] [Needs DVO-LVDS] Installer unable to launch Xorg on Fujitsu Stylistic ST4120PW To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/362582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 912909] Re: gimp-2.6 crashed with SIGSEGV
Same problem still with the final version of 12.04 and all updates installed up to the current day. GIMP crashes pretty much all the time when doing the first or second Save. Save as... is not needed, just normal Save will make it crash pretty regularly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/912909 Title: gimp-2.6 crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/912909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 369567] Re: Google Earth crashes system in 9.04
I have a similar issue with 10.04, ATI 4670 OSS drivers: while using Google Earth, screen first turns black, then white with vertical black lines. Had to power-cycle the machine to get out of this state. System: Asus P7P55D-E, i5-750, HIS ATI 4670 iceQ, Lucid 64bit, Google Earth 5.1.x Last syslog msg before crash: Jul 3 10:32:23 five rtkit-daemon[1485]: Supervising 5 threads of 2 processes of 2 users. Jul 3 10:32:23 five rtkit-daemon[1485]: Sucessfully made thread 1701 of process 1685 (n/a) owned by '1000' RT at priority 5. Jul 3 10:32:23 five rtkit-daemon[1485]: Supervising 6 threads of 2 processes of 2 users. Jul 3 10:32:24 five rtkit-daemon[1485]: Sucessfully made thread 1723 of process 1685 (n/a) owned by '1000' RT at priority 5. Jul 3 10:32:24 five rtkit-daemon[1485]: Supervising 7 threads of 2 processes of 2 users. Jul 3 10:32:24 five rtkit-daemon[1485]: Sucessfully made thread 1726 of process 1685 (n/a) owned by '1000' RT at priority 5. Jul 3 10:32:24 five rtkit-daemon[1485]: Supervising 8 threads of 2 processes of 2 users. Jul 3 10:32:24 five kernel: [ 23.980575] eth0: no IPv6 routers present Jul 3 10:33:26 five AptDaemon: INFO: Initializing daemon Jul 3 10:33:32 five kernel: [ 91.63] [drm:radeon_info_ioctl] *ERROR* copy_to_user Xorg.0.log is attached. tnx/Tom ** Attachment added: "Xorg.log before/during the crash" http://launchpadlibrarian.net/51324336/Xorg.0.log.old -- Google Earth crashes system in 9.04 https://bugs.launchpad.net/bugs/369567 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 369567] Re: Google Earth crashes system in 9.04
Turns out to be reproducible; doesn't always happen, but frequently. I do like this: - start Google Earth, move to some 3D buildings and zoom in - iconify Google Earth - start Firefox, goto Google Maps - sometimes the crash happens immediately, else play with Google Maps and/or Google Earth for some time Tom -- Google Earth crashes system in 9.04 https://bugs.launchpad.net/bugs/369567 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 592749] Re: Ubuntu update kills boot loader
Ooops you did it again! MBR killed; had to boot from my Windows DVD to restore the Windows bootloader. Is nobody reading this? Does anybody care? Tom -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/592749 Title: Ubuntu update kills boot loader -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 183456] Re: Trying to load a sf2 file with asfxload returns "sfxload: no memory left"
It most certainly does. However: Current kernel hackers seem to prefer to work around the situation by reverting to a timidity based software emulation of midi. It is not exactly the same as the emu10k1 midi, and - if you ask me - is of lower quality. Thus, at least kernel developers have a reason to say "go away, we don't need to care". Second, fixing the issue requires a deeper modification of the kernel, namely providing a more flexible memory allocation, or more DMA zones. The above hack does the trick, and it doesn't affect stability, but it changes the DMA zones of course - and just doing that for a single card might not be a good argument. Instead, the kernel should provide means to allocate memory with more flexible constraints than just the DMA zones that exist now. However, the issue doesn't seem to be pressing enough to move forward - at least this is my impression. Any kernel developers reading this here and could comment on this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/183456 Title: Trying to load a sf2 file with asfxload returns "sfxload: no memory left" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awesfx/+bug/183456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 183456] Re: Trying to load a sf2 file with asfxload returns "sfxload: no memory left"
I would say so, yes. I just don't have any other concrete examples where this might be the case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/183456 Title: Trying to load a sf2 file with asfxload returns "sfxload: no memory left" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awesfx/+bug/183456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 183456] Re: Trying to load a sf2 file with asfxload returns "sfxload: no memory left"
Daniel Richard G. wrote:
> Thomas, thank you for your clear description of the issue.
>
> Given that the problem is memory beyond the 2GB barrier, something I
> wanted to try was mmap()'s MAP_32BIT flag. You can sort-of do a malloc()
> by making an anonymous mapping, and so I hacked up safe_malloc() and
> safe_free() (in awelib/malloc.c) accordingly. My patch against the
> awesfx-0.5.1a source (current Ubuntu version) is attached.
>
> The addresses returned are consistently 0x4[0-9a-f]{7}, yet I continue
> seeing the "no memory left" error. Do you think there is something in
> this approach that may allow a solution that doesn't require kernel
> modification, or are we still at the mercy of the kernel's memory
> allocation policy?
Not really, at least not according to my understanding of the situation.
Look,
obviously the kernel has to copy over the sound font from user memory to
kernel
memory anyhow - simply because the user memory where awelib initially
loads the sound font into is released by the Os as soon as the program
is unloaded.
Thus, any user space tools cannot, by construction, control where the
wavetable
will go. It is the kernel that runs out of memory when trying to
allocate persistent
kernel memory for the sound font, not the user space tools.
Thus, this really requires a modification of the kernel emu10k1 driver,
unfortunately.
Greetings,
Thomas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/183456
Title:
Trying to load a sf2 file with asfxload returns "sfxload: no memory left"
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 369567] Re: Google Earth crashes system in 9.04
Problem is gone with mainline kernel 2.6.34! Could someone kindly pick this up and merge the latest radeon driver into the Ubuntu 10.04 stock kernel line? By going for a mainline kernel I have cut myself off from future security updates (ureadahead stopped working as well). Without it, a popular application (Google Earth) crashes on popular hardware (ATI 4670). Not only does the application crash, it kills the whole OS. Neither of this should happen with a stable/LTS release! Thanks Tom -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/369567 Title: Google Earth crashes system in 9.04 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776907] Re: knetworkmanager dies when clicking on the icon
-- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-networkmanagement in Ubuntu. https://bugs.launchpad.net/bugs/776907 Title: knetworkmanager dies when clicking on the icon -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 776907] [NEW] knetworkmanager dies when clicking on the icon
Public bug reported: Binary package hint: plasma-widget-networkmanagement Thread 1 (Thread 0xb514f710 (LWP 3186)): [KCrash Handler] #7 0xb61dea68 in QString::operator=(QString const&) () from /usr/lib/libQtCore.so.4 #8 0xb7081707 in Knm::Connection::setOrigin(QString const&) () from /usr/lib/libknminternals.so.4 #9 0xb704d976 in ConnectionListPersistence::restoreConnection(QString const&) () from /usr/lib/libknmservice.so.4 #10 0xb704dc29 in ConnectionListPersistence::init() () from /usr/lib/libknmservice.so.4 #11 0x0805443b in _start () ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager-kde 1:0.9~svngit20110408-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2 Uname: Linux 2.6.38-8-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Wed May 4 07:47:24 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: plasma-widget-networkmanagement UpgradeStatus: Upgraded to natty on 2011-04-28 (5 days ago) ** Affects: plasma-widget-networkmanagement (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776907 Title: knetworkmanager dies when clicking on the icon -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 592749] Re: Ubuntu update kills boot loader
Here is the printout. BTW, the latest grub update killed the MBR again. br Tom $ sudo debconf-show grub-pc grub-pc/kopt_extracted: false grub2/kfreebsd_cmdline: * grub-pc/install_devices: /dev/disk/by-id/ata-SAMSUNG_HD103SJ_S246J90Z207883 grub-pc/postrm_purge_boot_grub: false grub-pc/disk_description: * grub2/linux_cmdline: grub-pc/install_devices_empty: false grub2/kfreebsd_cmdline_default: quiet grub-pc/partition_description: grub-pc/install_devices_failed: false grub-pc/install_devices_disks_changed: * grub2/linux_cmdline_default: quiet splash grub-pc/chainload_from_menu.lst: true grub-pc/hidden_timeout: false grub-pc/timeout: 0 $ -- Ubuntu update kills boot loader https://bugs.launchpad.net/bugs/592749 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 592749] Re: Ubuntu update kills boot loader
** Changed in: grub2 (Ubuntu) Status: Incomplete => Confirmed -- Ubuntu update kills boot loader https://bugs.launchpad.net/bugs/592749 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 369567] Re: Google Earth crashes system in 9.04
** Changed in: ubuntu Status: Incomplete => Opinion ** Changed in: ubuntu Status: Opinion => Confirmed -- Google Earth crashes system in 9.04 https://bugs.launchpad.net/bugs/369567 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
