Re: Intel (s775) Johannesburg DQ35JOE mATX
On 23/01/2008 Steve Dobson wrote: > You don't need a backport of the kernel packages. They are stand alone > pieces of software that nothing depends upon and depend on nothing > themselves (in the packaging sense; I know the system needs a kernel to > run). You can just down load the kernel packages of your choice. Even though unstable kernel packages may work in etch, your statement is not true in general. Newer kernel needs newer udev at least, and I guess that some minimal glibc version is required as well. greetings, jonas signature.asc Description: Digital signature
Re: Intel Core2Duo (T7400)
On 07/11/2007 Jerome BENOIT wrote: > Douglas A. Tutty wrote: >> On Wed, Nov 07, 2007 at 12:05:26AM +0100, Bernd Petrovitsch wrote: >>> On Tue, 2007-11-06 at 13:35 -0500, Lennart Sorensen wrote: >>>> On Tue, Nov 06, 2007 at 06:58:15PM +0100, Jonas Meurer wrote: >>>>> Do you have any reasons for that suggestion? Which disadvantages does >>>>> the amd64 port have on system with up to 2GB of RAM? >>>> A few programs still don't compile or work on 64bit systems (not amd64 >>> Any real-world examples? >>> Even OpenOffice runs as 64bit since months. >>> The only which I remember rumors are "grub". But being a bootloader, >> >> Grub on Etch amd64 works just fine. > > the issue with grub is that it does not yet support EFI64 Can you point me to some documentation which explains EFI64? I searched for it with google, but the only real information I got, was that for booting a EFI64 kernel, the bootloader needs to support it. What is an EFI64 kernel? Is EFI64 a CPU flag? greetings, jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Intel Core2Duo (T7400)
On 06/11/2007 Basile STARYNKEVITCH wrote: > Jonas Meurer wrote: >> On 06/11/2007 Hartmut Manz wrote: >>> The correct debian port for INTEL Core2Duo is amd64 or i386. >>> If your system has not more than 2 GB of memory installed I would recommend >>> to still use the 32bit Linux (i386), If you have more memory installed use >>> the 64-bit Linux (amd64) >> >> Do you have any reasons for that suggestion? Which disadvantages does >> the amd64 port have on system with up to 2GB of RAM? > > a 64 bits system consume more memory than a 32 bits system for each pointer > and long (going from 32 bits = 4 bytes to 64 bits = 8 bytes) and also have > higher alignment requirements. Ok, the fact that pointers and long/double variables on 64bit systems do take twice as much RAM as on ia32 systems sounds reasonable. Thanks for information. > Rumors say that most processes consume about 30% more RAM > > Hence the hint (even if the 2Gb RAM threshold is arbitrary) 30% is quite a lot. Can you point me to postings/articles/etc. which claim to have discovered this? greetings, jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Intel Core2Duo (T7400)
On 06/11/2007 Lennart Sorensen wrote: > On Tue, Nov 06, 2007 at 06:58:15PM +0100, Jonas Meurer wrote: > > Do you have any reasons for that suggestion? Which disadvantages does > > the amd64 port have on system with up to 2GB of RAM? > > A few programs still don't compile or work on 64bit systems (not amd64 > specific, just 64bit system specific), but other than that generally no > disadvantages. but at least that doesn't depend on the RAM you use ;-) > I guess you could say that the fact the programs are slightly bigger > (since all pointers become 8 bytes rather than 4) is a disadvantage, but > on the other hand a lot of code runs slightly faster with 64bit, with a > few types of programs running much faster. A few very very pointer > heavy programs might run slightly slower, although I don't know of any > where this is the case. > > With 64bit you can memory map much bigger files than with 32bit which > can make implementing some programs much simpler and probably more > efficient too, so there seems to be many good reasons to move to 64bit. that's the relevant information here ;-) Thanks for pointing me to it. ... jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Intel Core2Duo (T7400)
On 06/11/2007 Hartmut Manz wrote: > The correct debian port for INTEL Core2Duo is amd64 or i386. > If your system has not more than 2 GB of memory installed I would recommend > to still use the 32bit Linux (i386), If you have more memory installed use > the 64-bit Linux (amd64) Do you have any reasons for that suggestion? Which disadvantages does the amd64 port have on system with up to 2GB of RAM? greetings, jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: keyboad leds not responding, kernel 2.6.22-2
On 27/10/2007 Wolfgang Mader wrote: > I think also that it is a problem of xorg. My Keyboard leds are working at > tty1 not but under X. > An other problem (perhaps relatet) is that I only can use an american > keyboard layout (under X). At tty1 I do have german layout (an configure). No > idea why. Hey Wolfgang, you need to configure the keyboard layout in /etc/X11/xorg.conf. Search for "XkbLayout" and "XkbVariant" and change the values to Option "XkbLayout" "de" Option "XkbVariant""nodeadkeys" after that you need to restart your xserver, and should be able to use your german keymap in X afterwards. greetings, jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: keyboad leds not responding, kernel 2.6.22-2
On 26/10/2007 Daniel van Eeden wrote: > It could be an issue with the kernel, Xorg server or both (the latter is > more likely). Since my last upgrade the leds on my Compaq PS/2 keyboard > stopped working under X11, but were working correctly on a linux console > (e.g. tty1). I guess that it is a bug in xorg server, see http://bugs.debian.org/446865 for an example. But that's not related to the issues with USB-keyboard in BIOS. Maybe that's a bug on the motherboard. At least documentation claims that USB-keyboard should work in BIOS/bootloader, but it doesn't. ... jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: keyboad leds not responding, kernel 2.6.22-2
On 16/10/2007 Dimitris Lampridis wrote: > > I have this problem since I moved from an old Compaq PS/2 keyboard to > > the new Logitech USB keyboard. Another drawback is that the keyboard > > doesn't work in the BIOS any longer. > > Check for something like "USB legacy mode" in your BIOS and enable it if > it is there. It worked for me. Hey Dimitris, I was able to choose between "all usb devices", "no mice" and "none" at USB legacy mode in BIOS. But unfortunately neither "all usb devices" nor "no mice" work for me. My USB-keyboard still doesn't work in BIOS and bootloader. At least the second one is quite annoying, as I'm not able to choose the kernel to boot any longer. > I hope you have a non-USB keyboard lying around to do this, otherwise > you'll have a tough time :) No problem about that, but i don't want to keep the PS/2 keyboard forever. For the record, I do have a MSI K8T-Neo Motherboard (VIA K8T800 Chipset) greetings, jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: keyboad leds not responding, kernel 2.6.22-2
On 16/10/2007 Hamish Moffatt wrote: > > > my keyboard leds does not respond any more. The NumLock led ist always on > > > the the other two are always off. I am running kernel 2.6.22-2. > > > The system is NOT looked up. Everything else runns nicely > > > Any hints? > > > > same problem for me... and same kernel, with Micro$oft Natural Keybord... > > Your keyboard is non-free; you should replace it. > > My Logitech works perfectly with 2.6.22-2-amd64 version 2.6.22-4. I've a Logitech keyboard as well, and in X, the leds don't work at all. On console, at least NumLock and ScrollLock work. The CapsLock led doesn't work there as well. I have this problem since I moved from an old Compaq PS/2 keyboard to the new Logitech USB keyboard. Another drawback is that the keyboard doesn't work in the BIOS any longer. greetings, jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: how to compile a recent xen dom0 kernel on amd64?
On 13/09/2007 Goswin von Brederlow wrote: > >> And indeed some patches seem to be applied (see below). But i still > >> don't see any xen options in menuconfig. Maybe the 2.6.22 xen patches > >> are for i386 only and not ported to amd64 yet? > > > > Based on the output those patches do not contain Xen. I don't know what > > they are for. > > The newest working patches I know are from RedHat and for 2.6.20. They > also have 2.6.21 but I heard that were instable. Are these patches for amd64 DomU only, or for Dom0 as well? And where do I get these patches? Do I need to use the redhat linux sources and patch them with the redhat xen patches, or how is it supposed to work? I guess that make-kpkg may be used from the linux source anyway, as it works with upstream linux sources as well. greetings, jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
how to compile a recent xen dom0 kernel on amd64?
hello, What is the current situation with xen on amd64? the debian/sid archive keeps no linux-image-2.6.22-2-xen-amd64, and I was not able to compile a 2.6.22 dom0 kernel with debian xen patches applied on my amd64 system. I have linux-source-2.6.22 and linux-patch-debian-2.6.22 installed, and followed the instructions from the workaround for http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=382699 Then I built the kernel: # make-kpkg --rootcmd fakeroot --initrd --append-to-version \ -1-amd64-xen --revision 2.6.22-4 --added-patches xen clean # make-kpkg --rootcmd fakeroot --initrd --append-to-version \ -1-amd64-xen --revision 2.6.22-4 --added-patches xen kernel_image And indeed some patches seem to be applied (see below). But i still don't see any xen options in menuconfig. Maybe the 2.6.22 xen patches are for i386 only and not ported to amd64 yet? That would also explain why no linux-image-2.6.22-2-xen-amd64 package exists in debian/unstable. output of 'make-kpkg ... --added-patches xen kernel_image': [...] test ! -f applied_patches || rm -f applied_patches for patch in /usr/src/kernel-patches/all/2.6.22/apply/xen ; do\ if test -x $patch; then\ if $patch; then \ echo "Patch $patch processed fine"; \ echo "$patch" >> applied_patches; \ else \ echo "Patch $patch failed."; \ echo "Hit return to Continue"; \ read ans; \ fi; \ fi; \ done Applying debian patch with xen parts Warning: Can't find series file for 3 (.) IGNORED bugfix/arm/nas100d-pata-artop-single-port.patch (.) IGNORED bugfix/m68k/falconide_intr_lock-reentrant.diff (.) IGNORED bugfix/m68k/633-atari_scc.diff (.) IGNORED bugfix/m68k/130-adbraw.diff (.) IGNORED bugfix/m68k/141-ide.diff (.) IGNORED bugfix/m68k/143-ioext.diff (.) IGNORED bugfix/m68k/149-mc68681.diff (.) IGNORED bugfix/m68k/152-pci.diff (.) IGNORED bugfix/m68k/448-ide.diff (.) IGNORED bugfix/m68k/478-serial.diff (.) IGNORED bugfix/m68k/atari-rom-isa.diff (.) IGNORED bugfix/m68k/atari-ethernec.diff (.) IGNORED bugfix/m68k/unnecessary-m68k_memoffset.diff (.) IGNORED bugfix/m68k/atari-aranym.diff (.) IGNORED bugfix/m68k/ethernec-work.diff (.) IGNORED bugfix/m68k/nfeth-virt_to_phys.diff (.) IGNORED bugfix/m68k/ethernec-kill-ETHERNEC_USE_POLL.diff (.) IGNORED bugfix/m68k/m68k-generic-io.diff (.) IGNORED bugfix/m68k/m68k-mvme-scsi-rename.diff (.) IGNORED bugfix/m68k/m68k-53c700-scsi.diff (.) IGNORED bugfix/m68k/via-pmu68k-dead-code.diff (.) IGNORED bugfix/m68k/dmasound_paula.diff (.) IGNORED bugfix/m68k/disable-mac-broken-config-options.diff --> 1 fully applied. (.) IGNORED bugfix/m68k/falconide_intr_lock-reentrant.diff (.) IGNORED bugfix/m68k/m68k-page.h-needs-compiler.h.diff (.) IGNORED bugfix/m68k/630-extern-cleanup.diff.1 (.) IGNORED bugfix/m68k/m68k-use-_AC.diff (.) IGNORED bugfix/m68k/m68k-amiga-z2ram-kill-TRUE-FALSE.diff (.) IGNORED bugfix/m68k/add-termios2.diff (.) IGNORED bugfix/m68k/m68k-arbitary-speed-tty-support.diff (.) IGNORED bugfix/m68k/m68k-do-not-include-RODATA-in-text-segment.diff (.) IGNORED bugfix/m68k/m68k-53c700-cleanups.diff (.) IGNORED bugfix/m68k/split-amiga7xx.diff (.) IGNORED bugfix/m68k/m68k-scsi-Kconfig-hickups.diff (.) IGNORED bugfix/m68k/zorro_config_attr-read-only.diff (.) IGNORED bugfix/m68k/zorro-module-device-table.diff (.) IGNORED bugfix/m68k/falconide_intr_lock-ratelimit.diff (.) IGNORED bugfix/m68k/debian-2.6.21-2-rom-isa.diff --> 2 fully applied. (.) IGNORED features/all/vserver/vs2.2.0.3.patch (.) IGNORED features/all/vserver/bindmount-dev.patch --> 4 fully applied. Patch /usr/src/kernel-patches/all/2.6.22/apply/xen processed fine echo done > stamp-patch [...] so how do you compile a xen dom0 host-kernel for amd64? is it possible with recent kernel sources at all? thanks in advance, jonas signature.asc Description: Digital signature
Re: Seeking Solution
On 10/08/2007 Hans-J. Ullrich wrote: > Problem: I am running Debian sid on an amd64-notebook with scsi-drive. > The problem is, I cannot standby the drive with hdparm -S 1 /dev/sda. Well, > it > is shutting down after 5 seconds, but something is writing permanently to the > drive so the drive is starting again. Hello Hans-J., > I suppose it is a log file. O.k.,lsof is telling me a lot of logfiles. Of > course, I could stop all the logging, but this is not the way I want to. I > want to stop only the logfile, which is responsible for the permannet > writing. > > So my question: How can I make Debian (Linux) to see, which file is written > to > the drive at the moment ? The only way I know of is fuser, which takes either device name or mount point as argument: # fuser -m /dev/mapper/mysql /var/lib/mysql: 6694c # ps 6694 PID TTY STAT TIME COMMAND 6694 ?Sl 0:00 /usr/sbin/mysqld --basedir=/usr \ --datadir=/var/lib/mysql --user=mysql \ --pid-file=/var/run/mysqld/mysqld.pid \ --skip-external-locking --port=3306 \ --socket=/var/run/mysqld/mysqld.sock greetings, jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
system freezes with Matrox G400 and GLX
Hello, I use a Matrox G400 DH as graphics controller, and i run debian/unstable on an amd64 system. Unfortunately this leads to system freezes when i try to use 3d rendering (GLX). Some examples which do always freeze my system are xmms visualisations, tuxkart and mixxx. Do you have any suggestions where to start debugging? Is this a glx/mesa bug, or a kernel mga driver bug, or a hardware problem? Here is my system information: [EMAIL PROTECTED]:~$ uname -a Linux resivo 2.6.18-8-amd64-resivo #1 Sat Feb 3 08:52:31 CET 2007 x86_64 GNU/Linux [EMAIL PROTECTED]:~$ lspci 00:00.0 Host bridge: VIA Technologies, Inc. VT8385 [K8T800 AGP] Host Bridge (rev 01) 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South] 00:06.0 USB Controller: NEC Corporation USB (rev 43) 00:06.1 USB Controller: NEC Corporation USB (rev 43) 00:06.2 USB Controller: NEC Corporation USB 2.0 (rev 04) 00:07.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 Encoder (rev 01) 00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) 00:0d.0 RAID bus controller: Promise Technology, Inc. PDC20378 (FastTrak 378/SATA 378) (rev 02) 00:0e.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) 00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80) 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:10.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) 00:10.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) 00:10.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) 00:10.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 81) 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South] 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400/G450 (rev 04) [EMAIL PROTECTED]:~$ glxinfo name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.2 server glx extensions: GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGIS_multisample, GLX_SGIX_hyperpipe, GLX_SGIX_swap_barrier, GLX_SGIX_fbconfig, GLX_MESA_copy_sub_buffer client glx vendor string: SGI client glx version string: 1.4 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory, GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap GLX version: 1.2 GLX extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig OpenGL vendor string: VA Linux Systems Inc. OpenGL renderer string: Mesa DRI G400 20050609 AGP 1x OpenGL version string: 1.2 Mesa 6.5.1 OpenGL extensions: GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_texture_compression, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_texture_rectangle, GL_ARB_transpose_matrix, GL_ARB_vertex_program, GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_logic_op, GL_EXT_clip_volume_hint, GL_EXT_compiled_vertex_array, GL_EXT_copy_texture, GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_multi_draw_arrays, GL_EXT_packed_pixels, GL_EXT_polygon_offset, GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_separate_specular_color, GL_EXT_stencil_wrap, GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, GL_EXT_texture_env_combine, GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_APPLE_packed_pixels, GL_ATI_texture_env_combine3, GL_IBM_r
amd64: sweep segfaults when changing the gain ratio in the record box
Package: sweep Version: 0.8.4-2 Severity: important Hello, recording audio with sweep works quite well, but when i try to record a second audio stream and sample it over the first one, i need to adjust the ratio from previous to recorded sound gain in the "record" box. this causes a segmentation fault on my amd64 debian/unstable system. i use a new file created at the start of sweep, and it doesn't matter whether i save this file before adjusting the gain ratio. the bug is obviously amd64 specific, as sweep in my i386 chroot doesn't segfault. ... jonas -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-5-amd64 Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages sweep depends on: ii libc62.3.5-7 GNU C Library: Shared libraries an ii libglib1.2 1.2.10-10 The GLib library of C routines ii libgtk1.21.2.10-18 The GIMP Toolkit set of widgets fo ii libmad0 0.15.1b-2.1 MPEG audio decoder library ii libogg0 1.1.2-1 Ogg Bitstream Library ii libsamplerate0 0.1.1-2 audio rate conversion library ii libsndfile1 1.0.12-3Library for reading/writing audio ii libspeex11.1.10-1The Speex Speech Codec ii libvorbis0a 1.1.0-1 The Vorbis General Audio Compressi ii libvorbisenc21.1.0-1 The Vorbis General Audio Compressi ii libvorbisfile3 1.1.0-1 The Vorbis General Audio Compressi ii libx11-6 6.8.2.dfsg.1-10 X Window System protocol client li ii libxext6 6.8.2.dfsg.1-10 X Window System miscellaneous exte ii libxi6 6.8.2.dfsg.1-10 X Window System Input extension li ii xlibs6.8.2.dfsg.1-10 X Window System client libraries m Versions of packages sweep recommends: pn cmt(no description available) pn fil-plugins(no description available) pn mcp-plugins(no description available) ii swh-plugins [ladspa-plugin] 0.4.14-1 Steve Harris's LADSPA plugins pn tap-plugins(no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Gnome 2.12
On 22/11/2005 Alex Malinovich wrote: > On Tue, 2005-11-22 at 21:26 +0100, antongiulio05 wrote: > > in AMD64 experimental there is gnome 2.12: > > > > # apt-cache policy gnome > > gnome: > > Installato: (nessuno) > > Candidato: 1:2.10.2.4 > > Tabella versione: > > 1:2.12.2 0 > > 1 http://giano.com.dist.unige.it experimental/main Packages > > 1:2.10.2.4 0 > > 500 http://mirror.switch.ch unstable/main Packages > > Some of the meta-packages are there, but it is not actually installable. > For example: > > gnome-desktop-environment depends on (among others) gnome-volume-manager > (>= 1.4.0) you should be able to build all gnome packages from experimental on your own though. sources are in experimental. they fail to build because they depend upon versions of other gnome components that are in experimental too. unfortunately most experimental buildds don't satisfy build-depends from experimental, and thus fail to build. ... jonas signature.asc Description: Digital signature
HP usb printing segfaults (Was: Parallel printing stopped working)
On 16/11/2005 Andrei Mikhailovsky wrote: > Hi, > > I've had a very similar issue with Parallel printer Samsung ML-4500. > Sending the data to the printer activated the printer for about 10 > seconds with light blinking. Nothing came out in the end. I've resolved > this issue by changing the parallel mode in the bios either to ECP or > EPP, I don't remember now and don't want to reboot my PC to find out. > Try changing the bios settings and see if it will work. i've the same issue with my HP Laserjet 1010 over USB. some software, like abiword, openoffice or gimp print without problems. others, like comandline lpr, firefox and everything that uses lpr, activate the printer for one second with light blinking, but don't produce any printout. if i use the commandline lpr directly, i get a segfault error: hpijs[8797]: segfault at 0001005a105b rip 0042e847 rsp \ 7fd3f4c0 error 4 does anybody have similar problems? ... jonas signature.asc Description: Digital signature
Re: nVidia, acpi, apic and PCI controller
On 01/11/2005 Dean Hamstead wrote: > i did update my bios but it had no effect on anything. i never > had that problem in the first place. > (btw im using a dfi-lanparty ut sli board, running sid) this motherboard is an ASUS K8N-DL (dual cpu) with two opteron cpus. let's see whether a bios update helps here. ... jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nVidia, acpi, apic and PCI controller
On 01/11/2005 Dean Hamstead wrote: > is that an nforce4? mine has ck804 also and is nforce4 but has nvraid > rather than sil. ok, i checked, and the chip finally is a nforce4 too. i'll check which bios it has installed next. if it's older than Version 1004, i'll do a bios update, and see if it helps. ... jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nVidia, acpi, apic and PCI controller
On 01/11/2005 Dean Hamstead wrote: > is that an nforce4? mine has ck804 also and is nforce4 but has nvraid > rather than sil. if you mean the mainboard, i've no idea. i didn't buy the hardware, i'm just an administrator. 'lspci -v -s 00:00.0' gives: :00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3) Subsystem: ASUSTeK Computer Inc.: Unknown device 8162 Flags: bus master, 66MHz, fast devsel, latency 0 Capabilities: [44] #08 [01e0] Capabilities: [e0] #08 [a801] it's an ASUS motherboard. > but anyway yes it is a known issue but im sure it should be solved, > my board doesnt have the same problem so i thought it was. did you do a BIOS update. I remember that i read something about problems with old ASUS bios versions. maybe that could help... do you have any links/articles about that problem? > that video card is comically old. it made me laugh thinking how > old that is compared to everything else. the video card in a server is perfectly irrelevant. ... jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
nVidia, acpi, apic and PCI controller
hello, i fail to boot my amd64 server (nVidia chip) with kernel 2.6.12 or 2.6.14 and ACPI plus APIC support. if i boot the kernel without any boot parameters, it hangs directly after the beginning of boot process at some problems with the PCI controller. it tells something like "PCI32 ... failed ...", but i don't remember the exact message. if i use acpi=off as boot-parameter, the boot process stops later, at detecting the sata harddisks. only with 'acpi=off noapic' the kernel boots without problems. is this a known issue? how can i fix it? lspci gives the following output: :00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3) :00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3) :00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2) :00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2) :00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3) :00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2) :00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3) :00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3) :00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2) :00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) :00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) :00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) :00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration :00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map :00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller :00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control :00:19.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration :00:19.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map :00:19.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller :00:19.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control :01:06.0 VGA compatible controller: S3 Inc. 86c764/765 [Trio32/64/64V+] :01:08.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) :01:09.0 RAID bus controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02) :02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 11) the full configuration in menu.lst for grub is: --- default 0 timeout 5 serial --unit=0 terminal --timeout=6 console serial color cyan/blue white/blue title Debian GNU/Linux, kernel 2.6.14-server03 without ACPI and APIC root(hd0,0) kernel /vmlinuz-2.6.14-server03 root=/dev/md1 ro bootkbd=qwertz/de acpi=off noapic savedefault boot --- do you have any suggestions or hints? ... jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: amd-64 vs Pure-64
On 27/09/2005 Marc F. Clemente wrote: > > Where might I find the sources and patches from which you compiled > > your version of OOo2? > > Patch: > http://mclemente.net/~marc/ooo2-marc.diff > > My sources: > deb-src http://mclemente.net/debian/ ./ > > The only changes I made were to the debian/rules file and to the > vbarange.cxx and vbarange.hxx files. hello, i just fetched ooo2 sources from experimental (1.9.125-1), and tried to build them on amd64 with your patch. unfortunately the build process breaks after an hour with the following error: ---snip--- [...] make[2]: Making `all' in `data' make[3]: Entering directory `/home/jonas/devel/openoffice.org2/openoffice.org2-1.9.125/ooo-build/build/src680-m125/icu/unxlngx4.pro/misc/build/icu/source/data' /bin/sh ../mkinstalldirs ../data/out ../data/out/build ../test/testdata/out ../test/testdata/out/build mkdir ../data/out mkdir ../data/out/build mkdir ../test/testdata/out mkdir ../test/testdata/out/build ICU_DATA=../data/out/build LD_LIBRARY_PATH=../common:../i18n:../tools/toolutil:../layout:../layoutex:../extra/ustdio:../tools/ctestfw:../data/out:../data:../stubdata/:$LD_LIBRARY_PATH ../tools/genpname/genpname -d ../data/out/build Inconsistency detected by ld.so: dl-minimal.c: 137: realloc: Assertion `new == ptr' failed! make[3]: *** [../data/out/build/icudt26l_pnames.icu] Error 127 make[3]: Leaving directory `/home/jonas/devel/openoffice.org2/openoffice.org2-1.9.125/ooo-build/build/src680-m125/icu/unxlngx4.pro/misc/build/icu/source/data' make[2]: *** [all-recursive] Error 2 make[2]: Leaving directory `/home/jonas/devel/openoffice.org2/openoffice.org2-1.9.125/ooo-build/build/src680-m125/icu/unxlngx4.pro/misc/build/icu/source' dmake: Error code 2, while making './unxlngx4.pro/misc/build/so_built_so_icu' '---* tg_merge.mk *---' ERROR: Error 65280 occurred while making /home/jonas/devel/openoffice.org2/openoffice.org2-1.9.125/ooo-build/build/src680-m125/icu make[1]: *** [stamp/build] Error 1 make[1]: Leaving directory `/home/jonas/devel/openoffice.org2/openoffice.org2-1.9.125/ooo-build' make: *** [debian/stampdir/build] Error 2 ---snip--- just wanted to report that, maybe it's an already known issue. ... jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: running ie6 using wine under amd64
On 16/08/2005 Simon Guerrero wrote: > Invoking /usr/lib/wine/wine.bin ie6setup ... > wine: Could not load graphics driver 'x11drv'. > Make sure that your X server is running and that $DISPLAY is set correctly. > Wine failed with return code 1 > > Any ideas? Thanks in advance. > > By the way, what should my $DISPLAY be? :0.0? How does it use the main > display when in a dchroot? looks like wine cannot connect to the X server. did you bind mount /tmp and /home to the chroot? if not, that might be the problem. wine needs the X socket from /tmp and maybe some Xauth configuration from /home/user/.Xauthority. if it still doesn't work try setting $DISPLAY: (in the chroot)# export DISPLAY=:0.0 bye jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Upgrading to current udev is disastrous if not on kernel 2.6.12
On 16/07/2005 Ed wrote: > Yes rebooting isn't good! Do the kernel upgrade and you won't have any > worries. > That is if you don't have heaps of myth/dvb patches to apply :) you have to patch your kernel for mythtv? which patches do you mean? is it only in connection with dvb? i use ivtv modules to use my winTV PVR-350 and i don't use any kernel patches. bye jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: cdrdao package for k3b
On 21/06/2005 Ross Urban wrote: > Tony, > Thanks for the info. Can you give me directions or point me to a site that > will tell me how to setup a i386 chroot. Sorry, I'm still a little green > behind the ears. hey ross, you don't need to setup a chroot for fetching sources. just add the following to your /etc/apt/sources.list: deb-src ftp://ftp2.de.debian.org/debian sid main then do the following # apt-get update # apt-get source cdrdao # apt-get build-dep cdrdao # [ patch and build the package as already described ] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sk98lin doesn't work on EM64T
On 17/06/2005 To Debian-AMD64 wrote: > On 17/06/2005 Sebastian Haase wrote: > > Ryan, > > Thanks for the quick reply. Are these older kernels s till available - > > where ? > > [ The official CDs have version 2.6.8-11 (is that _newer_ than 2.6.9 ??) ] > > yes, 2.6.8 is the upstream version, newer than upstream 2.6.9. oh, bad mistake. 2.6.8 is the upstream version, older than upstream 2.6.9. this one is correct. bye jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sk98lin doesn't work on EM64T
On 17/06/2005 Sebastian Haase wrote: > Ryan, > Thanks for the quick reply. Are these older kernels s till available - where > ? > [ The official CDs have version 2.6.8-11 (is that _newer_ than 2.6.9 ??) ] yes, 2.6.8 is the upstream version, newer than upstream 2.6.9. bye jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel-image-2.6.11-amd64 packages
On 28/03/2005 Jacob Larsen wrote: > Jonas Meurer wrote: > >finally i got this fixed by simply copying drivers/scsi/*.[ch] from > >kernel-source-2.6.10. > > I just grabbed v.2.6.11.6 from kernel.org. Seems like they already fixed > it. as kernel.org 2.6.11.6 Changelogs don't include anything regarding this, i believe that it's a debian relating bug, and was never included upstream. bye jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel-image-2.6.11-amd64 packages
On 28/03/2005 Jacob Larsen wrote: > >I have the same problem. I see this in the .config, but it is not shown > >in menuconfig: > > > >| CONFIG_SCSI_QLA2XXX=y this is the same for kernel-source-2.6.10, i compared both menuconfigs. the real problem is in the sources, drivers/scsi/qla2xxx is empty except Kconfig and Makefile in kernel-source-2.6.11: $ ll /usr/src/kernel-source-2.6.11/drivers/scsi/qla2xxx/ Kconfig Makefile $ ls /usr/src/kernel-source-2.6.10/drivers/scsi/qla2xxx/ Kconfig ql2322.c qla_def.h qla_inline.h qla_os.c Makefile ql6312.c qla_devtbl.h qla_iocb.c qla_rscn.c ql2100.c ql6322.c qla_gbl.h qla_isr.c qla_settings.h ql2200.c qla_dbg.c qla_gs.c qla_listops.h qla_sup.c ql2300.c qla_dbg.h qla_init.cqla_mbx.c qla_version.h i didn't find any information about the qla2xxx driver removal in the changelog, except one from 2.6.5-1 (long time ago): * Removed non-free firmware and disabled their drivers (see #239952): . QLA2XXX: drivers/scsi/qla2xxx/*_fw.c there is already a bugreport considering this issue: #301603: Compile fails linking drivers/scsi/qla2xxx/build.o i tried to comment out the entry in .config, but make-kpkg always reverts the modifications. finally i got this fixed by simply copying drivers/scsi/*.[ch] from kernel-source-2.6.10. bye jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel-image-2.6.11-amd64 packages
On 27/03/2005 Javier Kohen wrote: > El lun, 28-03-2005 a las 04:04 +0200, Jonas Meurer escribió: > > On 27/03/2005 Frederik Schueler wrote: > > > I am currently uploading the first release of kernel-image-2.6.11-amd64 > > > to alioth. > > > > the sources fail to build for me with the attached .config: > > the same .config builds clean with kernel-source-2.6.10. > > Did you update the config to the newer kernel release? "make oldconfig" > should help. sure, i did so. i used menuconfig, but that shouldn't matter. still, the build failture happens. bye jonas signature.asc Description: Digital signature
Re: kernel-image-2.6.11-amd64 packages
On 27/03/2005 Frederik Schueler wrote: > I am currently uploading the first release of kernel-image-2.6.11-amd64 > to alioth. the sources fail to build for me with the attached .config: --- # fakeroot make-kpkg --initrd --append-to-version -1-amd64 kernel_image [...] CC drivers/scsi/sg.o LD drivers/scsi/built-in.o ld: drivers/scsi/qla2xxx/built-in.o: No such file: No such file or directory make[3]: *** [drivers/scsi/built-in.o] Error 1 make[2]: *** [drivers/scsi] Error 2 make[1]: *** [drivers] Error 2 make[1]: Leaving directory `/usr/src/kernel-source-2.6.11' make: *** [stamp-build] Error 2 --- the same .config builds clean with kernel-source-2.6.10. bye jonas # # Automatically generated make config: don't edit # Linux kernel version: 2.6.11-1-amd64 # Mon Mar 28 03:56:34 2005 # CONFIG_X86_64=y CONFIG_64BIT=y CONFIG_X86=y CONFIG_MMU=y CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_CMPXCHG=y CONFIG_EARLY_PRINTK=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y # # General setup # CONFIG_LOCALVERSION="" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_LOG_BUF_SHIFT=14 CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y # CONFIG_IKCONFIG is not set # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_FUTEX=y CONFIG_EPOLL=y # CONFIG_CC_OPTIMIZE_FOR_SIZE is not set CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_OBSOLETE_MODPARM=y CONFIG_MODVERSIONS=y # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y # # Processor type and features # CONFIG_MK8=y # CONFIG_MPSC is not set # CONFIG_GENERIC_CPU is not set CONFIG_X86_L1_CACHE_BYTES=64 CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y CONFIG_MICROCODE=m # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set CONFIG_X86_IO_APIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_MTRR=y # CONFIG_SMP is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y # CONFIG_NUMA is not set # CONFIG_GART_IOMMU is not set CONFIG_DUMMY_IOMMU=y CONFIG_X86_MCE=y CONFIG_X86_MCE_INTEL=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y # # Power management options # CONFIG_PM=y # CONFIG_PM_DEBUG is not set # CONFIG_SOFTWARE_SUSPEND is not set # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y # CONFIG_ACPI_SLEEP is not set # CONFIG_ACPI_AC is not set # CONFIG_ACPI_BATTERY is not set CONFIG_ACPI_BUTTON=m CONFIG_ACPI_VIDEO=m # CONFIG_ACPI_FAN is not set CONFIG_ACPI_PROCESSOR=m CONFIG_ACPI_THERMAL=m # CONFIG_ACPI_ASUS is not set CONFIG_ACPI_IBM=m # CONFIG_ACPI_TOSHIBA is not set CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y # CONFIG_ACPI_CONTAINER is not set # # CPU Frequency scaling # # CONFIG_CPU_FREQ is not set # # Bus options (PCI etc.) # CONFIG_PCI=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y # CONFIG_UNORDERED_IO is not set # CONFIG_PCI_MSI is not set CONFIG_PCI_LEGACY_PROC=y CONFIG_PCI_NAMES=y # # PCCARD (PCMCIA/CardBus) support # # CONFIG_PCCARD is not set # # PC-card bridges # # # PCI Hotplug Support # # CONFIG_HOTPLUG_PCI is not set # # Executable file formats / Emulations # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=m CONFIG_IA32_EMULATION=y CONFIG_IA32_AOUT=y CONFIG_COMPAT=y CONFIG_SYSVIPC_COMPAT=y CONFIG_UID16=y # # Device Drivers # # # Generic Driver Options # CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=m # CONFIG_DEBUG_DRIVER is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # CONFIG_PARPORT=y CONFIG_PARPORT_PC=m CONFIG_PARPORT_PC_CML1=m # CONFIG_PARPORT_SERIAL is not set CONFIG_PARPORT_PC_FIFO=y # CONFIG_PARPORT_PC_SUPERIO is not set # CONFIG_PARPORT_OTHER is not set CONFIG_PARPORT_1284=y # # Plug and Play support # # CONFIG_PNP is not set # # Block devices # CONFIG_BLK_DEV_FD=y # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_CRYPTOLOOP=m CONFIG_BLK_DEV_NBD=m CONFIG_BLK_DEV_SX8=m # CONFIG_BLK_DEV_UB is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_LBD=y # CONFIG_CDROM_PKTCDVD is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONF
Re: [mythtv] Freezes on 64bit when starting recordings or LiveTV
On 27/03/2005 Isaac Richards wrote:
> On Sunday 27 March 2005 05:59 am, Adam Egger wrote:
> > Ok, I've found an old patch from Kyle Rose to replace all
> > pthread_rwlock_* calls with a mix of pthread_mutex_* and
> > pthread_cond_*:
> > http://www.gossamer-threads.com/lists/mythtv/users/107232?search_string=pth
> >read_rwlock;#107232
> >
> > Isaac, is it a bad solution to replace them permanently in RingBuffer.cpp?
>
> Yes. That patch isn't correct, and I'm not going to stop using standard
> functionality just because it's broken on one little-used platform. I'm
> fairly sure people are using native 64-bit stuff elsewhere, so it's just
> seems like Debian's behind as usual.
i upgraded the patch for mythtv 0.17 anyway, as i don't want to wait for
debian/pure64 to fix the glibc.
here it is, for all the people that like to run mythtv 0.17 on
debian/unstable pure64.
bye
jonas
diff -ru mythtv-0.17.orig/libs/libmythtv/RingBuffer.cpp
mythtv-0.17/libs/libmythtv/RingBuffer.cpp
--- mythtv-0.17.orig/libs/libmythtv/RingBuffer.cpp 2005-03-27
14:59:20.0 +0200
+++ mythtv-0.17/libs/libmythtv/RingBuffer.cpp 2005-03-27 15:00:11.396760584
+0200
@@ -490,14 +490,17 @@
numfailures = 0;
commserror = false;
-pthread_rwlock_init(&rwlock, NULL);
+pthread_mutex_init(&hammerlock, NULL);
+pthread_cond_init(&hammercond, NULL);
+readers = 0;
+writers = 0;
}
RingBuffer::~RingBuffer(void)
{
KillReadAheadThread();
-pthread_rwlock_wrlock(&rwlock);
+unlock();
if (remotefile)
{
delete remotefile;
@@ -525,7 +528,7 @@
void RingBuffer::Reset(void)
{
wantseek = true;
-pthread_rwlock_wrlock(&rwlock);
+write_lock_wait();
wantseek = false;
if (!normalfile)
@@ -552,7 +555,7 @@
numfailures = 0;
commserror = false;
-pthread_rwlock_unlock(&rwlock);
+unlock();
}
int RingBuffer::safe_read(int fd, void *data, unsigned sz)
@@ -616,12 +619,43 @@
return ret;
}
+void RingBuffer::read_lock_wait()
+{
+pthread_mutex_lock(&hammerlock);
+while (writers > 0)
+{
+pthread_cond_wait(&hammercond, &hammerlock);
+}
+readers++;
+pthread_mutex_unlock(&hammerlock);
+}
+
+void RingBuffer::write_lock_wait()
+{
+pthread_mutex_lock(&hammerlock);
+while (readers > 0 || writers > 0)
+{
+pthread_cond_wait(&hammercond, &hammerlock);
+}
+writers = 1;
+pthread_mutex_unlock(&hammerlock);
+}
+
+void RingBuffer::unlock()
+{
+pthread_mutex_lock(&hammerlock);
+if (readers > 0) readers--;
+else writers = 0;
+pthread_cond_signal(&hammercond);
+pthread_mutex_unlock(&hammerlock);
+}
+
#define READ_AHEAD_SIZE (10 * 256000)
void RingBuffer::CalcReadAheadThresh(int estbitrate)
{
wantseek = true;
-pthread_rwlock_wrlock(&rwlock);
+write_lock_wait();
wantseek = false;
fill_threshold = 0;
@@ -653,7 +687,7 @@
if (fill_min == 0)
fill_min = -1;
-pthread_rwlock_unlock(&rwlock);
+unlock();
}
int RingBuffer::ReadBufFree(void)
@@ -793,7 +827,7 @@
readaheadpaused = false;
-pthread_rwlock_rdlock(&rwlock);
+ read_lock_wait();
if (totfree > readblocksize && !commserror)
{
// limit the read size
@@ -901,7 +935,7 @@
}
availWaitMutex.unlock();
-pthread_rwlock_unlock(&rwlock);
+ unlock();
if ((used >= fill_threshold || wantseek) && !pausereadthread)
usleep(500);
@@ -1012,7 +1046,7 @@
int RingBuffer::Read(void *buf, int count)
{
-pthread_rwlock_rdlock(&rwlock);
+read_lock_wait();
int ret = -1;
if (normalfile)
@@ -1068,7 +1102,7 @@
{
if (stopreads)
{
-pthread_rwlock_unlock(&rwlock);
+ unlock();
return 0;
}
@@ -1087,7 +1121,7 @@
if (stopreads)
{
availWaitMutex.unlock();
-pthread_rwlock_unlock(&rwlock);
+ unlock();
return 0;
}
}
@@ -1118,7 +1152,7 @@
}
}
-pthread_rwlock_unlock(&rwlock);
+unlock();
return ret;
}
@@ -1126,11 +1160,11 @@
{
bool ret = false;
int used, free;
-pthread_rwlock_rdlock(&rwlock);
+unlock();
if (!tfw)
{
-pthread_rwlock_unlock(&rwlock);
+unlock();
return ret;
}
@@ -1139,7 +1173,7 @@
ret = (used * 5 > free);
-pthread_rwlock_unlock(&rwlock);
+unlock();
return ret;
}
@@ -1147,11 +1181,11 @@
{
int ret = -1;
-pthread_rwlock_rdlock(&rwlock);
+unlock();
if (!tfw)
{
-pthread_rwlock_unlock(&rwlock);
+unlock();
return ret;
}
@@ -1200,7 +1234,7 @@
availWaitMutex.unlock();
}
-pthread_rwlock_unlock(&rwlock);
+unlock();
return ret;
}
@@
Re: fbpanel from pool segfaults, rebuild helps
On 05/03/2005 Goswin von Brederlow wrote: > Jonas Meurer <[EMAIL PROTECTED]> writes: > > > for some reason, fbpanel from the pure64 pool segfaults on my pure64 > > system. if i fetch the package sources and rebuild it on my own, > > it works like a charm. > > it doesn't matter whether i build it with gcc-3.4 or gcc-3.3, both work > > well. > > > > any suggestions, why the package in the pool segfaults? btw. can you > > reproduce this anyway? > > Did you use the gcc-3.4 archive at some point? no, i use only the pure64 archives, my sources.list contains: deb ftp://ftp.de.debian.org/debian-amd64/pure64/ sid main deb-src ftp://ftp.de.debian.org/debian-amd64/pure64/ sid main do you have any suggestions? bye jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
fbpanel from pool segfaults, rebuild helps
hello, for some reason, fbpanel from the pure64 pool segfaults on my pure64 system. if i fetch the package sources and rebuild it on my own, it works like a charm. it doesn't matter whether i build it with gcc-3.4 or gcc-3.3, both work well. any suggestions, why the package in the pool segfaults? btw. can you reproduce this anyway? bye jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
fbpanel from pool segfaults, rebuild helps
hello, for some reason, fbpanel from the pure64 pool segfaults on my pure64 system. if i fetch the package sources and rebuild it on my own, it works like a charm. it doesn't matter whether i build it with gcc-3.4 or gcc-3.3, both work well. any suggestions, why the package in the pool segfaults? btw. can you reproduce this anyway? bye jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
testing buildd && gcc-3.4 transition
hello, i'm interested in the latest plans on creating a testing buildd, and if this will be realized. i like the idea, as it provides a somehow better and more secure distribution for (just as example) production servers, that don't like to be rebooted or unavailable in any case every now end then, because many people rely on them. second, i'dd like to know how gcc transition from 3.3 to 3.4 goes on, and if it will superseed the old 3.3 archive soon. when 3.4 includes much better amd64 support, that would be interesting for all amd64 port users. i'm asking as we have a dual cpu opteron system that will get setup as a server soon, and therefore a amd64 testing tree .oO(with gcc 3.4 compiled)Oo. would be very useful. bye jonas
Re: Migration from unstable to testing.
On 23/07/2004 Chris Wakefield wrote: > Ron Johnson wrote: > >You're already running pure-amd64? > > Well, I may have embarassed myself, but I assumed that installing from: > http://debian.inode.at/pure64/ > with the > http://debian-amd64.alioth.debian.org/install-images/sid-amd64-monolithic.iso > image, and that: > deb http://debian-amd64.alioth.debian.org/pure64 sid main contrib non-free > is listed in my sources.list, that it would be a pure64? your absolutely correct, and you're running a pure-amd64 install. i don't think, that migrating from unstable to testing once amd64 entered debian, and once it has a testing tree, will be a big deal. you just change your sources.list, and wait until all packages currently installed are superseded by never versions in testing, as downgrading isn't recommented in those general cases. > I have noticed that in the .config file of: vmlinuz-2.6.7-5-amd64-xeon > has this: > CONFIG_IA32_EMULATION=y > > Maybe I'm mistaken? Please inform me if I am. no, it just allows you to still run 32bit binarys on your 64bit install. is enables you to use software compiled for the (currently more widespread) i386 port of linux kernels. bye jonas
