devpts: called with bogus options
Hey guys, I can't figure this out. Any ideas? These messages in dmesg used to be harmless because devpts would be mounted anyway, ignoring bogus options: - [8.535397] devpts: called with bogus options - But since I upgraded to linux-image-2.6.29-1-amd64 in the latest 'sid', my devpts will not mount unless I manually mount it. This works: $ mount -t devpts devpts /dev/pts/ This does not: $ mount /dev/pts Thanks for any help! -s # /etc/fstab: static file system information. # # file system mount point type options dump pass /dev/sda1 /boot ext3 defaults,noatime,commit=60,user_xattr,acl 0 2 /dev/sda2 /x86 ext3 defaults,noatime,commit=60,user_xattr,acl 0 2 /dev/sda3 / ext3 defaults,errors=remount-ro,noatime,commit=60,user_xattr,acl 0 1 /dev/sda4 /home ext3 defaults,noatime,user_xattr,acl 0 2 /dev/hdc /ls120 ext2 defaults,user 0 0 /dev/hdc /floppy vfat defaults,user 0 0 /dev/cdrom /cdrom iso9660 user,ro 0 0 proc/proc proc defaults 0 0 sysfs /sys sysfs none 0 0 devpts /dev/pts devpts none 0 0 tmpfs /dev/shm tmpfs defaults 0 0 tmpfs /tmp tmpfs defaults 0 0 # x86 mounts /home /x86/home none bind0 0 /tmp/x86/tmp none bind0 0 /dev/x86/dev none rbind0 0 /sys /x86/sys none bind0 0 proc/x86/proc proc defaults0 0 -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: What is the best java for debian-amd64 ?
Allow me to unrecommend Blackdown JRE 1.4.2. Unfortunately, the maintainers of xul-runner have seen fit to conflict with every version of jre 1.4.2. Your choices are to force reinstallation of Blackdown 1.4.2 after every dist-upgrade or install it outside of package management. Those of us stuck with legacy applications on modern OS's are in a bind with this situation. -s On Thu, 2008-09-18 at 19:27 +0200, Simon Vos wrote: The java-6-openjdk is the one I use. It is the completely open version of the JDK released by sun under the GPL. In fact it is IcedTea, which is a project created to have a complete open JDK. The source release by Sun was not complete, since some parts of their source were not their intelectual property. For these parts of the source Sun added binaries, the IcedTea project re-implemented the non-open parts. For as far as I have used the java-6-openjdk it seems to me that it is complete. I think I read online that IcedTea had passed the TCK (the java compatibility test) and it is completely open-source. Also, it is the default default java alternative in debian I think.. With kind regards, Simon Hans-J. Ullrich wrote: Hi all, as there are many java versions installable, what is the best one to use in amd64-systems ? What are the differences ? I saw gcj, gij, gdk, java. Can someone tell me, which should be used ? Ia ma very confused. Update-alternatives is giving me these choices: There are 8 alternatives which provide `java'. SelectionAlternative --- 1/usr/bin/gij-4.1 2/usr/lib/jvm/ia32-java-6-sun/jre/bin/java 3/usr/lib/jvm/java-gcj/jre/bin/java 4/usr/bin/gij-4.3 * 5/usr/lib/jvm/java-6-sun/jre/bin/java 6/usr/bin/gij-4.2 7/usr/lib/jvm/ia32-java-1.5.0-sun/jre/bin/java +8/usr/lib/jvm/java-6-openjdk/jre/bin/java Press enter to keep the default[*], or type selection number: I choose 5. What is this +-sign meaning ? Questions, questions, questions Thanks for any help ! Kind regards Hans-J. Ullrich -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: What is the best java for debian-amd64 ?
On Thu, 2008-09-18 at 16:19 -0300, Fabricio Cannini - Yahoo wrote: On Thursday 18 September 2008 15:05:17 Stephen Olander-Waters wrote: Allow me to unrecommend Blackdown JRE 1.4.2. Unfortunately, the maintainers of xul-runner have seen fit to conflict with every version of jre 1.4.2. Your choices are to force reinstallation of Blackdown 1.4.2 after every dist-upgrade or install it outside of package management. Those of us stuck with legacy applications on modern OS's are in a bind with this situation. -s Hi Stephen! Have you tried to use /etc/apt/preferences' do disallow apt-get/aptitude of uninstalling Blackdown's jre ? No. I did not think that worked for conflicting packages. I thought it would make xulrunner uninstall or disable dist-upgrading. Is that not true? -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SNDCTL_TMR_TIMEBASE or TCGETS
On Wed, 2008-06-18 at 10:37 -0400, Lennart Sorensen wrote: On Tue, Jun 17, 2008 at 09:30:49PM +0200, Gudjon I. Gudjonsson wrote: Hi I am fighting to get some code written 13 years ago in several languages to run decently on my amd64. Making it run in 64 bit mode is a far future dream but I'm hoping to fix a chroot. Currently I get most success with an etch chroot. The program compiles and runs in 64 bit mode but without any sensible output but when I run it in the chroot, I get the following output to strace several times and then a segmentation fault. ioctl(5, SNDCTL_TMR_TIMEBASE or TCGETS, 0xffdb6f38) = -1 ENOTTY (Inappropriate ioctl for device) Since it runs in 64 bit mode I guess it has something to do with the chroot. Has anyone seen anything similar? Make sure /dev is bind mounted in your chroot, as well as proc and such. Is this some sort of OSS vs ALSA problem? I guess make sure the ALSA OSS compatibility module is loaded and make sure the /dev stuff is correct, per Lennart. Wild guess, -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Which kernel will Lenny likely use when it is released?
On Thu, 2008-06-12 at 14:16 -0500, Karl Schmidt wrote: I would think that they would fix the 2.6.24 4G bug if that is what they will release with? Hell, 2.6.24 wouldn't even boot on my dual Opteron box. I seriously hope they go ahead with 2.6.25. Sid forever! -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dvi vs vga etc and monitors.....
On Wed, 2008-05-28 at 13:22 +1000, simon wise wrote: On 28 May 2008, at 8:17 AM, Michael Fothergill wrote: Is it also true that if you switched it for a 50 meter DVI cable then everything would be perfect and the signal degradation would vanish? for long runs VGA is better, DVI doesn't work for long runs, although there are some (very expensive) longer DVI cables around, I think the maximum is much less than 50 meters. I cannot speak from experience, but the Wikipedia page says: --- The maximum length of DVI cables is not included in the specification since it is dependent on bandwidth requirements (the resolution of the image being transmitted). In general, cable lengths from 1-15 feet (4.5m) will work for displays at resolutions of 1920x1200. Cable lengths up to 50 feet (15m) can be used with displays at resolutions up to 1280x1024. For longer distances, to eliminate the video degradation, the use of a DVI booster is recommended. DVI boosters may or may not use an external power supply. --- http://en.wikipedia.org/wiki/Digital_Visual_Interface Having said that, I agree with Lennart that if money is no object, go for DVI for a clean, digital signal. However, Simon has a good point that, where possible, put the computer[s] as near to the display device as possible and control it remotely. Cheers, -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub Error 15 File not found
On Tue, 2008-02-19 at 11:40 -0600, Stephen Olander-Waters wrote: Debian unstable with latest updates Debian 2.6.24 amd64 kernel I can't seem to use the 2.6.24 Debian kernel. Whenever I boot up, grub reports Error 15 File Not Found. I can fall back on my old 2.6.23 kernel and it works just fine. Using tab-completion in the command line editor feature of grub, I can confirm that the files are there. They just won't load! I solved the problem. My /boot/grub/device.map file had the entries for hda and sda swapped. When you switch the boot partition from one drive to another, you should update that file. :) Cheers, -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dual-core system will not create NTP peers
On Wed, 2008-02-20 at 22:16 -0600, Moshe Yudkowsky wrote: I have discovered the source of the problem: the file /etc/default/adjtimex had a TICK value of 9750. That's 2.5% less than the standard value of 1 and accounts exactly for the clock skew I observed. Oh, I wish I'd remembered that file. I had that problem way back in 2003 when I switched from an old K7 system to a dual Opteron. I used the same hard drive and everything. I didn't reinstall. The old value was very different from the new value. Something to keep in mind when upgrading a motherboard. -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub Error 15 File not found
On Tue, 2008-02-19 at 15:53 -0500, Aaron M. Ucko wrote: Does your /boot/grub/menu.lst perhaps refer to a nonexistent initrd image? No... tab-completion in the grub bootloader confirms the initrd is there. Within the system, the file is non-zero and appears to be generated correctly when you do dpkg-reconfigure. Hrm... any other ideas? -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
grub Error 15 File not found
Debian unstable with latest updates Debian 2.6.24 amd64 kernel I can't seem to use the 2.6.24 Debian kernel. Whenever I boot up, grub reports Error 15 File Not Found. I can fall back on my old 2.6.23 kernel and it works just fine. Using tab-completion in the command line editor feature of grub, I can confirm that the files are there. They just won't load! More details: Dual opteron 244 system MSI K8T-Master2FAR motherboard recently switch from booting off hda to sda when I got a new drive old kernel boots fine update-grub runs fine tried turning on/off savedefault tab-completion finds the 2.6.24 kernel and initrd separate, small /boot partition. not full. Thank you for any help! -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: how to cleanly remove the chroot environment?
On Thu, 2007-06-21 at 09:51 -0400, Roberto C. Sánchez wrote: On Wed, Jun 20, 2007 at 07:23:57PM -, avishai wrote: /home on /var/chroot/sid-ia32/home type none (rw,bind) /tmp on /var/chroot/sid-ia32/tmp type none (rw,bind) /dev on /var/chroot/sid-ia32/dev type none (rw,bind) /proc on /var/chroot/sid-ia32/proc type none (rw,bind) These are all bind mounts. You can umount them by running this as root: for i in home tmp dev proc ; do umount /var/chroot/sid-ia32/$i ; done If you get any device busy (or similar) errors then that means that something is still accessing one of those partitions. You need to stop or kill that process and then try again. Or, remove them from /etc/fstab and reboot. Cat /proc/mounts. If none are left, you should be able to safely remove the directories. -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: confused about performance
On Thu, 2007-06-14 at 16:08 +0200, Leopold Palomo-Avellaneda wrote: really, reading you makes me doubt about the whole port. How many apps do we have in the debian pool that can win some kind of performance? Personally, I don't care. I went 64-bit for *FUN*, not performance, though I am hoping that World Community Grid will port its apps to 64-bit and take advantage of the new registers. Geek out, -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Random Crashes
On Mon, 2007-05-07 at 17:35 +, Jack Malmostoso wrote: On Mon, 07 May 2007 16:50:13 +0200, Eduardo M KALINOWSKI wrote: HARDWARE ERROR CPU 0: Machine Check Exception:4 Bank 4: b2070f0f TSC a38a02f0b This is not a software problem! Turn off Chipkill in the BIOS unless you know for a fact that your RAM is single rank (x4bit). -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
MSI forum runs Debian amd64
Apparently, the MSI forum server runs Debian amd64. Cool, eh? -s Forwarded Message From: MSI HQ User to User Forum [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: New announcement: MSI will replace all servers. Date: Sun, 01 Apr 2007 09:38:11 -0400 Date: Sun, 01 Apr 2007 13:38:06 + X-Mailer: SMF Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-Id: [EMAIL PROTECTED] Hi guys, Finally MSI and the forum team reached an agreement. As you know the current forum server is incredibly fast. MSI has done some testing the last few days with new fileservers for LiveUpdate and downloading various stuff but they where unable to match the speed of the forum server. Because they noticed we do such a good job of running the forum, they wanted us to takeover all other servers and put everything on the forum server. This includes their marketting/support websites, fileservers and all other forums. We think our server can handle all this traffic with ease. Our current traffic is between 100~200GB each month, but we think our connection can handle all the traffic and should give better results. MSI thinks that the current server can do all their other traffic as well. It might slowdown the forum a little bit, but we expect no major problems. This move will happen beginning of the second quarter this year. Our forum server is build with this stuff: 2x Xeon 2.8GHz 2x 15000 RPM SCSI drive's in RAID1 (but we are going to add 2 more for RAID5 to gain about 275MB/s speed) 2x 1GB memory reg ecc Debian AMD64 with all the latest updates. Tests so far has shown that we can handle MSI's traffic of 27TB/month isn't a problem. So please test the speed of everything the first day of next quarter, we are moving bits and pieces that day and hope to recieve reports on the speed. There might be a nice supprice for the best reporter on how the move is going, but I'm not allowed what that will be. I will post shortly the email address that can be used to send in reports. [Edit]The move has been done. You can use this link to test the new servers: http://www.msi.eu Also, you can sent in speed reports here: [EMAIL PROTECTED] To unsubscribe from these announcements, login to the forum and uncheck Receive forum announcements and important notifications by email. in your profile. You can view the full announcement by following this link: http://forum.msi.com.tw/index.php?topic=106503.0 Regards, The MSI HQ User to User Forum Team. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who have no sound in their 32bit chroot
On Fri, 2007-01-26 at 18:08 +1100, Hamish Moffatt wrote: Do you mind posting your /etc/fstab? I want to see if I'm mounting my /x86/dev similarly. # mounts for the i386 chroot /home /var/chroot/i386/home nonebind0 0 /tmp /var/chroot/i386/tmpnonebind0 0 proc /var/chroot/i386/proc procdefaults0 0 /dev /var/chroot/i386/devnonebind0 0 Nothing special. I am using rbind. I wonder if there is a difference between mounting rbind and bind. I will report back about this. What kernel are you using, Hamish? Thanks! -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who have no sound in their 32bit chroot
On Wed, 2007-01-24 at 08:24 -0500, Matthias Julius wrote: Gudjon I. Gudjonsson [EMAIL PROTECTED] writes: Yes, sorry, I sometimes forget to mention relevant information. I was only using the 64 bit kernel modules and 32 bit library in chroot and it did not work. But after porting the application to 64 bit it worked like charm. Then you should be able to debug the application and see wether the device file is actually opened or not. Could it be that this is some data type issue that both the kernel module and the application use a type for communication that has a different size on a 32 bit platform and on a 64 bit platform? This way the 32 bit application would only work with a 32 bit kernel and the 64 bit application only with a 64 bit kernel. It wouldn't surprise me. E.g., ALSA does not work in a 32-bit chroot, but the old OSS does. shrugs -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: For those who have no sound in their 32bit chroot
On Thu, 2007-01-25 at 08:14 +1100, Hamish Moffatt wrote: On Wed, Jan 24, 2007 at 08:42:59AM -0600, Stephen Olander Waters wrote: It wouldn't surprise me. E.g., ALSA does not work in a 32-bit chroot, but the old OSS does. ALSA works fine here in a 32-bit chroot. I sometimes use 32-bit mplayer as it has access to win32 codecs. Really??? You're sure it's not falling back on the OSS driver? Do you mind posting your /etc/fstab? I want to see if I'm mounting my /x86/dev similarly. Thanks, -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 show stoppers
On Tue, 2007-01-16 at 19:42 -0600, Karl Schmidt wrote: But the biggest problem for me is that there isn't a AMD64 nvu package. The author abandoned it to work on a replacement package, but in the mean time there isn't a good WYSIWYG html editor for web development. (Sorry, but quanta just isn't in the same league and OO makes bloat-code out of clean html). It would be nice, but I think we're stuck with an obsolete local of NVU until the author finishes his new project. I haven't tried bluefish, which another poster recommended. I will check it out. My biggest showstopper is the msync kernel bug: http://bugs.debian.org/401006 I'm having to fsck about every 5th reboot (this is a workstation so I reboot every day). The weird part about it is it's screwing up my kernel module files and nothing else. I think it must be triggered by something in the shutdown sequence (which is why I don't get segfaults running apt-get, etc.). -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.20 ext3 fix backported to Debian?
On Fri, 2007-01-12 at 22:32 +0100, Jean-Luc Coulon (f5ibh) wrote: Le 12.01.2007 22:21:08, Stephen Olander Waters a écrit : Anyone know if the ext3 patch in 2.6.20 to fix filesystem corruption was backported to the Debian 2.6.19? Is there a 2.6.19 in Debian? Oops, looks like it's linux-image-2.6.18-3-amd64 My mistake. I think I have this bug detailed on LWN under the title A nasty file corruption bug - fixed http://lwn.net/Articles/215868/ (This is a follow-up to my previous post about corrupted kernel module files.) -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
2.6.20 ext3 fix backported to Debian?
Anyone know if the ext3 patch in 2.6.20 to fix filesystem corruption was backported to the Debian 2.6.19? Thanks, -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: corrupted kernel module files with 2.6.18-3 on ext3
On Wed, 2006-12-20 at 05:35 -0800, Sal wrote: You might want to run a memory test. I had similar problems that I thought were being caused by a bad harddrive. It turned out to be faulty memory. I tried that but my memory appears to be perfect... -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel 2.6.19: system freeze with blinking CapsLock and ScrollLock leds
If you don't have a serial cable, but you do have another computer on the network, why don't you try netconsole? http://lisa.cs.uni-potsdam.de/lxr/source/Documentation/networking/netconsole.txt I usually boot into single user mode, load the module with appropriate options, then continue into multi user mode. The crash will appear on the other computer. It's fairly helpful. -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.6.19-rc4 custom debian package
On Thu, 2006-11-02 at 00:13 +0100, Jean-Michel Pouré wrote: * How do I enable console debugging in the kernel. I heard it was possible, after a crash, to hit a few keys and display an error message. I find the ethernet console to be most convenient if you have a second PC. 1. Boot into single user mode 2. load the netconsole module with appropriate parameters 3. on your other PC, run: netcat -u -l -p port 4. exit single user mode Crash/debug info should appear on the netcat terminal. $KERNEL/Documentation/networking/netconsole.txt $ modinfo netconsole filename: /lib/modules/2.6.18-1-686/kernel/drivers/net/netconsole.ko author: Maintainer: Matt Mackall [EMAIL PROTECTED] description:Console driver for network interfaces license:GPL vermagic: 2.6.18-1-686 SMP mod_unload 686 REGPARM gcc-4.1 depends: parm: netconsole: [EMAIL PROTECTED]/[dev],[tgt-port]@tgt-ip/[tgt-macaddr] (string) -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: strange network problem
On Wed, 2006-11-01 at 15:16 -0500, Douglas Tutty wrote: I just thought of something: those LAN-UDP modules specifically say that they do not work with gigabit ethernet. (and the switch is a 10/100, not a 10/100/1000). Even though the Athlon's port is connecting to the 486's 10 Mb/s NIC, could this be an issue? I agree with the poster before that you should manually set your gigabit to 10mbit before loading LAN-UDP or any other network modules. I think it's a kernel module parameter. -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: strange network problem
On Wed, 2006-11-01 at 19:19 -0500, Douglas Tutty wrote: I agree that limiting the gigabit to 10 Mb/s is probably a kernel module parameter but the forcedeth module is not mentioned in the kernel documentation that I can see. (rgrep forcedeth .) I don't see it in any of the generic networking kernel docs either. Hrm... the parameters don't look that helpful. You might contact the author, I guess. $ modinfo forcedeth filename: /lib/modules/2.6.18-1-amd64/kernel/drivers/net/forcedeth.ko author: Manfred Spraul [EMAIL PROTECTED] description:Reverse Engineered nForce ethernet driver license:GPL vermagic: 2.6.18-1-amd64 SMP mod_unload gcc-4.1 depends: alias: pci:v10DEd01C3sv*sd*bc*sc*i* alias: pci:v10DEd0066sv*sd*bc*sc*i* alias: pci:v10DEd00D6sv*sd*bc*sc*i* alias: pci:v10DEd0086sv*sd*bc*sc*i* alias: pci:v10DEd008Csv*sd*bc*sc*i* alias: pci:v10DEd00E6sv*sd*bc*sc*i* alias: pci:v10DEd00DFsv*sd*bc*sc*i* alias: pci:v10DEd0056sv*sd*bc*sc*i* alias: pci:v10DEd0057sv*sd*bc*sc*i* alias: pci:v10DEd0037sv*sd*bc*sc*i* alias: pci:v10DEd0038sv*sd*bc*sc*i* alias: pci:v10DEd0268sv*sd*bc*sc*i* alias: pci:v10DEd0269sv*sd*bc*sc*i* alias: pci:v10DEd0372sv*sd*bc*sc*i* alias: pci:v10DEd0373sv*sd*bc*sc*i* alias: pci:v10DEd03E5sv*sd*bc*sc*i* alias: pci:v10DEd03E6sv*sd*bc*sc*i* alias: pci:v10DEd03EEsv*sd*bc*sc*i* alias: pci:v10DEd03EFsv*sd*bc*sc*i* alias: pci:v10DEd0450sv*sd*bc*sc*i* alias: pci:v10DEd0451sv*sd*bc*sc*i* alias: pci:v10DEd0452sv*sd*bc*sc*i* alias: pci:v10DEd0453sv*sd*bc*sc*i* parm: dma_64bit:High DMA is enabled by setting to 1 and disabled by setting to 0. (int) parm: msix:MSIX interrupts are enabled by setting to 1 and disabled by setting to 0. (int) parm: msi:MSI interrupts are enabled by setting to 1 and disabled by setting to 0. (int) parm: poll_interval:Interval determines how frequent timer interrupt is generated by [(time_in_micro_secs * 100) / (2^10)]. Min is 0 and Max is 65535. (int) parm: optimization_mode:In throughput mode (0), every tx rx packet will generate an interrupt. In CPU mode (1), interrupts are controlled by a timer. (int) parm: max_interrupt_work:forcedeth maximum events handled per interrupt (int) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: System freeze
All of you with X system freezes, Check the top of your dmesg for any warnings about aperture size. I kept getting freezes because my AGP aperture was too small (32MB) for what Linux wanted (64MB) on a Radeon 9200 256MB. I hadn't noticed the warning because X didn't complain in Xorg.0.log and the kernel driver didn't complain when X was loading. HTH, -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bind mounts and shutdown sequence
On Mon, 2006-10-23 at 10:30 -0500, Stephen Olander Waters wrote: On 10/19/06, Stephen Olander Waters [EMAIL PROTECTED] wrote: I am running sid with amd64 architecture. I also have a chroot called /x86 to run openoffice, acroread, boinc, etc. In my /etc/fstab, I have several bind mounts into /x86. When I run shutdown -h now or shutdown -r now, the shutdown sequence stops with an error after stopping all the processes. I have to use Alt +SysRq to reboot. However, the shutdown sequence works OK if I manually unmount the bind mounts before executing shutdown. Is anyone else experiencing this problem? I can file a bug once I figure out what script is dying (it's hard for me to tell because the machine is unusable except Alt+SysRq!) Here is the error message I'm getting --- Asking non-system processes to terminate..done Killing non-system processes ...error: '/etc/init.d/rc' exited outside the expected codeflow. INIT: no more processes in this runlevel --- Here is my /etc/fstab --- # x86 mounts /home /x86/home none bind0 0 /tmp/x86/tmp none bind0 0 /dev/x86/dev none bind0 0 sysfs /x86/sys sysfs none0 0 proc/x86/proc proc defaults0 0 I found a workaround. I don't know if it counts as a fix but it does work. Change /x86/sys to a bind mount and shutting down works. /sys /x86/sys bind none0 0 HTH, -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[CORRECTION] Re: bind mounts and shutdown sequence
CORRECTION Here is my /etc/fstab --- # x86 mounts /home /x86/home none bind0 0 /tmp/x86/tmp none bind0 0 /dev/x86/dev none bind0 0 sysfs /x86/sys sysfs none0 0 proc/x86/proc proc defaults0 0 I found a workaround. I don't know if it counts as a fix but it does work. Change /x86/sys to a bind mount and shutting down works. /sys /x86/sys bind none0 0 Of course, that should be: /sys /x86/sys none bind0 0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel 2.6.18: agpgart-modules ???
On Wed, 2006-10-25 at 16:14 +0200, Hans-J. Ullrich wrote: I am missing some agpgart-modules in the kernel-sources. In earlier days, I could build them as modules, now I only find intel-agp, sis-agp and ali-agp. There is only one AGP module for the AMD64 architecture cleverly named amd64-agp -- however it is built-in on Debian kernels. I assume this is because it's built into all AMD64 CPUs or is required for AMD64 northbridges. -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bind mounts and shutdown sequence
On Tue, 2006-10-24 at 14:02 +0200, Gabor Gombas wrote: On Mon, Oct 23, 2006 at 10:30:34AM -0500, Stephen Olander Waters wrote: Here is the error message I'm getting --- Asking non-system processes to terminate..done Killing non-system processes ...error: '/etc/init.d/rc' exited outside the expected codeflow. INIT: no more processes in this runlevel --- Smells like bug #391375. Yes, I think you are right. I also tried changing /x86/dev to an rbind but that doesn't seem to make a difference. Furthermore, I am absolutely sure I am not shutting down inside the chroot. ;) -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: bind mounts and shutdown sequence
On 10/19/06, Stephen Olander Waters [EMAIL PROTECTED] wrote: I am running sid with amd64 architecture. I also have a chroot called /x86 to run openoffice, acroread, boinc, etc. In my /etc/fstab, I have several bind mounts into /x86. When I run shutdown -h now or shutdown -r now, the shutdown sequence stops with an error after stopping all the processes. I have to use Alt +SysRq to reboot. However, the shutdown sequence works OK if I manually unmount the bind mounts before executing shutdown. Is anyone else experiencing this problem? I can file a bug once I figure out what script is dying (it's hard for me to tell because the machine is unusable except Alt+SysRq!) Here is the error message I'm getting --- Asking non-system processes to terminate..done Killing non-system processes ...error: '/etc/init.d/rc' exited outside the expected codeflow. INIT: no more processes in this runlevel --- Here is my /etc/fstab --- # /etc/fstab: static file system information. # # file system mount point type options dump pass /dev/hda1 /boot ext3 defaults 0 2 /dev/hda2 /x86 ext3 defaults 0 2 /dev/hda3 / ext3 defaults,errors=remount-ro 0 1 /dev/hda4 /home ext3 defaults 0 2 /dev/hdc /ls120 ext2 defaults,user 0 0 /dev/hdc /floppy vfat defaults,user 0 0 /dev/cdrom /cdrom iso9660 user,ro 0 0 proc/proc proc defaults 0 0 sysfs /sys sysfs none 0 0 devpts /dev/pts devpts none 0 0 tmpfs /dev/shm tmpfs defaults 0 0 tmpfs /tmp tmpfs defaults 0 0 # x86 mounts /home /x86/home none bind0 0 /tmp/x86/tmp none bind0 0 /dev/x86/dev none bind0 0 sysfs /x86/sys sysfs none0 0 proc/x86/proc proc defaults0 0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
bind mounts and shutdown sequence
I am running sid with amd64 architecture. I also have a chroot called /x86 to run openoffice, acroread, boinc, etc. In my /etc/fstab, I have several bind mounts into /x86. When I run shutdown -h now or shutdown -r now, the shutdown sequence stops with an error after stopping all the processes. I have to use Alt +SysRq to reboot. However, the shutdown sequence works OK if I manually unmount the bind mounts before executing shutdown. Is anyone else experiencing this problem? I can file a bug once I figure out what script is dying (it's hard for me to tell because the machine is unusable except Alt+SysRq!) Thanks so much, -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: boinc-client
On Tue, 2006-09-12 at 23:00 +0200, Sythos wrote: Which project support amd64 / x86_64-pc-linux ? I run world community grid (fight aids at home and help defeat cancer) in a 32-bit chroot. I made my own init script to run it in the background at boot. -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: s2875 tyan kernel memory problem
On Sun, 2006-09-10 at 15:41 +1000, garrone wrote: On Sat, Sep 09, 2006 at 09:38:27PM -0700, Max A. wrote: I have updated it to 3.3 The bios with discrete mtrr and enabled software memory hole does work with ubuntu 2.6.11 locally compiled kernel. I see all the memory. It doesnt crash. It just crashes with 2.6.8-12-amd64-k8-smp debian package. That's an ancient kernel. You could try getting a newer image + dependencies from 'unstable' and using that. -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sun-java5-plugin on amd64
On Tue, 2006-05-23 at 21:04 +0200, Hans-J. Ullrich wrote: Please take a look: http://debian.geole.de/pool/non-free/s/ There is no sun-java5-plugin package in that repository. Here is the official 'sid' deb: http://ftp.debian.org/debian/pool/non-free/s/sun-java5/sun-java5-plugin_1.5.0-06-1_i386.deb Where can I find the amd64 version of the plugin? Thanks, -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
sun-java5-plugin on amd64
Anyone know when/if the sun-java5-plugin package will be supported under amd64? Thanks, -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: xfonts-utils missing?
I switched to the main debian.org archive. Fixed all of my xutils, etc. missing problems. FYI, -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: which motherboard for a debian server?
On Wed, 2006-03-08 at 16:56 -0600, Don Montgomery wrote: Has the K8T Master2-FAR changed since 2003? Mine has no fan except on the cpus. Speaking of, I've been looking into replacing my K8T Master2-FAR system with a laptop since I've migrated all my server functionality off-site. . MSI K8T Master2-FAR . Dual Opteron 240's . Enermax EG365AX-VE(W) FCA (PSU) . 4 x 512MB Buffalo Tech PC2700 (M/N: DD333L-R512/MC) . boring case PC case . NEC dual layer writer (4x) . 40gb udma hard drive If you're interested, drop me an email OFF-LIST with a *serious* offer. If you want buyer protection, I can also post it as Buy it Now on ebay -- you'd just need to be ready to click that item link. :) Cheers and be sure to reply to me off-list, -s signature.asc Description: This is a digitally signed message part
Re: nvidia-glx removes x-server???
On Thu, 2006-01-12 at 11:01 -0500, Lennart Sorensen wrote: On Thu, Jan 12, 2006 at 07:59:09AM -0500, Andrew Syrewicze wrote: Hey everyone. Having a wierd problem here. It's been awhile since i've run debian unstable, but i missed the updated packages and what not. Anyway, My install went as clean as usual, and i used module assistant to set up my nvidia driver. When i run apt-get install nvidia-glx it installs the package just fine, but it also removes all basic X packages. Packages like x-window-system x-server-xorg and x-window-system-core. Is this a problem with unstable right now, or is it a kernel thing??? I'm running with a 2.6.15 kernel. Any Ideas??? Which version of nvidia-glx? I believe xserver-xorg now conflicts with nvidia-glx less than version 7174. And the line is in fact: Conflicts: xlibs ( 6.8.2.dfsg.1-5), xserver-xfree86 ( 6.8.2.dfsg.1-1), nvidia-glx (= 1.0.7174-4) If you have a TNT or similarly old card, you have to use 7174. The maintainer is supposedly working on nvidia-legacy debs but I haven't seen anything yet. I got bit by this on an older K7 machine with a TNT2. -s p.s., No I can't run out and buy a new video card. signature.asc Description: This is a digitally signed message part
Re: 64/32 with DRI
On Wed, 2006-01-04 at 14:43 -0800, Andrew Sharp wrote: It looks to me to be 64-bit specific, like, it's iterating through a 4294967295 planes trying to do something the chip doesn't even support, instead of skipping that feature. So if you can live without DRI for a little while, they will probably have this fixed, or at least a patch available. I sure hope so. I just figure the squeaky wheel gets the grease is all. Wish their bugzilla had voting. Oh well. -s signature.asc Description: This is a digitally signed message part
Re: 64/32 with DRI
On Wed, 2006-01-04 at 10:58 -0800, Andrew Sharp wrote: Geez you guys sound like a couple of teenagers who just found their favorite football team. If the open source ATI Radeon driver has bugs you don't like, you are free to jump in and fix them. It works quite well for me on multiple systems including my amd64. As I understand it, the problem is localized to the R100 series of GPUs which includes the Radeon 7000/VE I have installed on my box. I think this started over DRI support for the ancient 7000 Radeon. However, I haven't seen any testing results posted. I know there is a comment in the code that it's experimental, but have you actually tried it and found it to be buggy? I believe this is the bug I am experiencing: https://bugs.freedesktop.org/show_bug.cgi?id=5104 Also, having dug around some, I believe it has to do with the dynamic clocking patch but I'm not a C coder, don't have access to a serial console, etc. There are no messages in the logs -- just a hard freeze of the system. I'm not using any driver options. I have turned off MTRR, which is also buggy, in the Screen section. I tried setting SWCursor as suggested in another bug in the Free Desktop bugzilla but that didn't help. -s signature.asc Description: This is a digitally signed message part
Re: 64/32 with DRI
On Mon, 2006-01-02 at 20:35 +1100, Hamish Moffatt wrote: On Mon, Jan 02, 2006 at 01:45:16AM -0600, Stephen Olander Waters wrote: Radeon 7000 DRI in xorg 6.8.2 is unstable apparently. See this message: [...] Man that sucks. That's ATI for you. I'm not using ATI's proprietary driver. I'm using the buggy open source driver maintained by X.org which used to work just fine... -s -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 64/32 with DRI
Radeon 7000 DRI in xorg 6.8.2 is unstable apparently. See this message: http://www.redhat.com/archives/fedora-announce-list/2005-September/msg0.html --- - DRI is now enabled by default on all ATI Radeon hardware except for the Radeon 7000/Radeon VE chipsets, which is known to be unstable for many users currently when DRI is enabled. Radeon 7000 users can re-enable DRI if desired by using Option DRI in the device section of the config file, with the understanding that we consider it unstable currently. --- Man that sucks. -s signature.asc Description: This is a digitally signed message part
Re: 64/32 with DRI
On Wed, 2005-12-28 at 17:56 +0300, Serge Belyshev wrote: I'm running linux-image-2.6.14-2-amd64-k8-smp on 32-bit 'sid' (haven't made the time to go all-64 yet). I have an old Radeon 7000 and I'm using the standard radeon driver. While DRI appears to initialize correctly in the Xorg.log.0, glxinfo reports that direct rendering is off and 32 bit DRI clients don't work with 64 bit kernel. You may want to look at: https://bugs.freedesktop.org/show_bug.cgi?id=943 OK, I've installed a 64-bit sid and it still freezes with DRI. What can I do to fix this? Do DRI and SMP conflict? Thanks, -s signature.asc Description: This is a digitally signed message part
Re: such a good news about flash...!!!
On Fri, 2005-12-30 at 16:00 -0500, Robert Isaac wrote: Some sites have an entry splash screen / menu that is a quite full screen flash. And quite many sites I need for professional use (suppliers) have such a banner. Without flash, it is not possible to enter it :-( Then that is bad web design. A good web designer would also do an html page without the flash or avoid flash entirely to allow everyone to enter his/her site. Unfortunately, the world is full of ne'er-do-wells and we must learn to work around them for our own gain. Setting up the dchroot thing in the Debian AMD64 How-to was immensely easy and helpful. https://alioth.debian.org/docman/view.php/30192/21/debian-amd64-howto.html Using flash with 32-bit Firefox works like a charm. -s signature.asc Description: This is a digitally signed message part
64/32 with DRI
Hi, I'm running linux-image-2.6.14-2-amd64-k8-smp on 32-bit 'sid' (haven't made the time to go all-64 yet). I have an old Radeon 7000 and I'm using the standard radeon driver. While DRI appears to initialize correctly in the Xorg.log.0, glxinfo reports that direct rendering is off and opening any GL app causes the machine to halt. Any ideas? Thanks for any help! -s signature.asc Description: This is a digitally signed message part
Re: iptables on amd64 kernel
On Mon, 2005-07-11 at 11:45 +0200, Jörg Ebeling wrote: Hi Jakub, I've the same on a server machine since weeks. I could solve the problem by installing the 'amd64-libs' and a manually install of 'iptables_1.2.11-10_amd64.deb' with '--force-architecture'. Well it works without any further problems (by me). The annoying thing is that apt/aptitude always tries to update the iptables package. I did the same thing except I put an = next to it in dselect to keep it from getting upgraded. -s signature.asc Description: This is a digitally signed message part
Re: [Fwd: Re: amd64 k8 smp 2.6.11 kernel-source-nonfree]
On Wed, 2005-06-29 at 19:14 +0200, Frederik Schueler wrote: In the meantime, a build of the kernel-nonfree-modules-2.6.11-9-* packages for the several amd64 flavours is available here: deb http://213.178.77.236/kernel/amd64/ ./ How do I fix apt-get update failing out with the signature problem? (no Release.gpg) Thank you!!! -s signature.asc Description: This is a digitally signed message part
Re: verification of packages with gnupg/apt-key
On Wed, 2005-06-29 at 08:02 -0400, Lennart Sorensen wrote: On Wed, Jun 29, 2005 at 12:52:47PM +0100, Andrei Mikhailovsky wrote: Has anyone anyone manage to make verification of packages/Release files work under amd64? Many thanks for any help I was under the impression the majority of packages in debian were not signed, since no one has come up with a way for the buildd to sign a package using a package maintainers key (and I imagine no one should try either). Perhaps the package maintainers could (maybe some already do, not sure) sign packages from the buildd when they are done, but I don't think that is the case at the moment. Certainly I know debsigs just didn't work very well before given how many packages were not signed. Why not give buildd its own user and gpg key, kept up-to-date by the debian sysadmins in the same way they maintain the root accounts, SSL certs, etc.? $0.02USD, -s signature.asc Description: This is a digitally signed message part
[Fwd: Re: amd64 k8 smp 2.6.11 kernel-source-nonfree]
Just wondering if anyone on this list has done this: -s Forwarded Message From: Andres Salomon [EMAIL PROTECTED] To: Stephen Olander Waters [EMAIL PROTECTED] Subject: Re: amd64 k8 smp 2.6.11 kernel-source-nonfree Date: Tue, 28 Jun 2005 11:38:20 -0400 On Mon, 2005-06-27 at 00:39 -0500, Stephen Olander Waters wrote: How can I talk you into making an amd64 k8 smp version of the 2.6.11 kernel nonfree modules? I tried to do it myself, but I couldn't figure out how to do it. I have 64-bit kernel, but 32-bit 'sid'. Cheers and thanks for the hard work, -s You could send me an amd64 machine; currently, I don't have a way to build them, as I don't have the hardware. I believe Frederik is work on it, though. signature.asc Description: This is a digitally signed message part
