problem with new potato install
I'm having odd problems with a fresh potato install. I installed from the 2.2.7-2000-02-13 floppies yesterday (03/02/2000) and this is not an upgraded from Slink. System info: HP Vectra XA6 Series 5xx Via Rhine NIC (working fine, this doesn't appear to be a NIC problem) Custom kernel, not the stock Potato 2.2.14 synergy:~ ] uname -a Linux synergy 2.2.14 #2 Fri Mar 3 12:53:28 PST 2000 i686 unknown synergy:~ ] lsmod Module Size Used by sb 34708 0 (unused) uart401 6352 0 [sb] sound 58284 0 [sb uart401] soundcore 2788 6 [sb sound] nfs29408 1 (autoclean) lockd 32200 0 (autoclean) [nfs] sunrpc 54628 1 (autoclean) [nfs lockd] autofs 9440 1 (autoclean) via-rhine 9232 1 synergy:~ ] sudo ipchains -L Chain input (policy ACCEPT): Chain forward (policy ACCEPT): Chain output (policy ACCEPT): Telnet is not the only application exhibiting these symptoms, it just happens to illustrate them: synergy:~ ] telnet synergy Trying xxx.xxx.xxx.xxx... telnet: Unable to connect to remote host: No buffer space available synergy:~ ] telnet localhost Trying 127.0.0.1... [hangs untill I ^C out...] But, from another host: caliber:~ ] telnet synergy Trying xxx.xxx.xxx.xxx... Connected to synergy Escape character is '^]'. Debian GNU/Linux 2.2 (frozen) synergy synergy login: Or: synergy:~ ] rpcinfo -p synergy rpcinfo: can't contact portmapper: RPC: Remote system error - No buffer space available But from another host: caliber:~ ] rpcinfo -p synergy program vers proto port service 102 tcp111 rpcbind 102 udp111 rpcbind Of course, this means that lockd, statd and other RPC friends have been unable to register on synergy so my NFS is erratic at best. I'm also getting a lot of these: Mar 3 19:22:49 synergy kernel: neighbour table overflow Mar 3 19:23:02 synergy kernel: neighbour table overflow Mar 3 19:27:17 synergy kernel: neighbour table overflow Any ideas? Thanks in advance! PeeWee -- email: [EMAIL PROTECTED] - useless: http://www.scc.mi.org/peewee/ - efnet: Pwe I said you were a state of mind, I believe. I said that if you ran very swiftly and were acceptably violent, you would be admired. - The Era of Great Numbers
Re: oddlu corrupted file during slink upgrade
On Sun, Jan 17, 1999 at 11:39:39PM -0500, Brandon Mitchell spewed forth: gusgus:~ # ls -l /usr/man/man2/iopl.2.gz prw--ws--- 1 505 38296 0 Jan 2 1970 /usr/man/man2/iopl.2.gz And I can't delete it This looks familiar. I'd suggest: 1) e2fsck -cf /dev/hd? Haven't run 'fsck -cf', but badblocks does run clean on the partition, as does 'fsck -f'. 2) try to move the file gusgus:/usr/man/man2 # mv iopl.2.gz /tmp mv: cannot move `iopl.2.gz' to `/tmp/iopl.2.gz': Operation not permitted 3) make a ramdisk, move the file to the ramdisk, reboot (I get a sneaky and devilish feeling doing that) gusgus:/usr/man/man2 # df /mnt Filesystem 1024-blocks Used Available Capacity Mounted on /dev/ram0 3963 13 3746 0% /mnt gusgus:/usr/man/man2 # mv iopl.2.gz /mnt mv: cannot move `iopl.2.gz' across filesystems: Not a regular file 4) probably the one you will hear the most: debugfs This, however, worked. Thanks! PeeWee -- email: [EMAIL PROTECTED] - useless: http://www.scc.mi.org/peewee/ - efnet: Pwe Bad signs are everywhere coach. I tend to ignore them The Era of Big Numbers
oddlu corrupted file during slink upgrade
Howdy... I seem to have a corrupted file on this system which is preventing me from upgrading manpages-dev: gusgus:~ # apt-get install manpages-dev Updating package status cache...done Checking system integrity...ok 1 packages upgraded, 0 newly installed, 0 to remove and 165 not upgraded. Need to get 0b/611k of archives. After unpacking 20.0k will be used. Selecting previously deselected package manpages-dev. (Reading database ... 26203 files and directories currently installed.) Preparing to replace manpages-dev 1.18-1 (using manpages-dev_1.21-1.deb) ... Unpacking replacement manpages-dev ... dpkg: error processing manpages-dev_1.21-1.deb (--unpack): unable to make backup link of `usr/man/man2/iopl.2.gz' before installing new version: Operation not permitted dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: manpages-dev_1.21-1.deb E: Sub-process returned an error code It's obviously corrupted and bogus: gusgus:~ # ls -l /usr/man/man2/iopl.2.gz prw--ws--- 1 505 38296 0 Jan 2 1970 /usr/man/man2/iopl.2.gz And I can't delete it: gusgus:~ # rm /usr/man/man2/iopl.2.gz rm: remove `/usr/man/man2/iopl.2.gz', overriding mode 2630? y rm: /usr/man/man2/iopl.2.gz: Operation not permitted Or zero it out: gusgus:~ # cp /dev/null /usr/man/man2/iopl.2.gz cp: cannot create regular file `/usr/man/man2/iopl.2.gz': Permission denied I've booted the system from a hamm rescue disk and fsck'd the partition. There were no problems found. I was also unable to delete the file while booted from the rescue disk. I wrote a quit perl script to unlink(/usr/man/man2/iopl.2.gz), but got back 'operation not permitted'. I suppose I could try C's unlink() instead, but I doubt I'd get any better results. This machine is still running 2.0.31 - I was hoping to get the slink upgrade over and done with before bringing it up to something more modern. If a kernel upgrade will allow me to delete this file, then I'll do it now. Any ideas? Thanks! PeeWee -- email: [EMAIL PROTECTED] - useless: http://www.scc.mi.org/peewee/ - efnet: Pwe Bad signs are everywhere coach. I tend to ignore them The Era of Big Numbers
Re: timezone
On Wed, Jan 13, 1999 at 03:33:11PM -0500, [EMAIL PROTECTED] spewed forth: This has now been fixed in the latest(updated today(1/13/99)) slink packages, notice the new version numbers, not just the Debian revision. Woo. Looks like this fixes my problems with the hamm-beta system I'm trying to upgrade to slink: gusgus:~ # apt-get update Get ftp://ftp.debian.org slink/contrib Packages Get http://non-us.debian.org slink/non-US Packages Get ftp://ftp.debian.org slink/main Packages Get ftp://ftp.debian.org slink/non-free Packages Fetched 594k in 1m9s (8500b/s) Updating package file cache...done Updating package status cache...done Checking system integrity...dependency error You might want to run `apt-get -f install' to correct these. Sorry, but the following packages are broken - this means they have unmet dependencies: apt: Depends:libc6 gusgus:~ # apt-get -f install Updating package status cache...done Checking system integrity...dependency error Correcting dependencies...ok The following extra packages will be installed: libc6-dev libc6 2 packages upgraded, 0 newly installed, 0 to remove and 280 not upgraded. Need to get 1852k of archives. After unpacking 119k will be freed. Do you want to continue? [Y/n] n I'll do the actual upgrade tonight when I'm sitting in front of the machine. Thanks! PeeWee -- email: [EMAIL PROTECTED] - useless: http://www.scc.mi.org/peewee/ - efnet: Pwe Bad signs are everywhere coach. I tend to ignore them The Era of Big Numbers
Hamm beta upgrade to Slink
Howdy... I have a machine here running a beta of Hamm, probably from before Hamm was frozen. I'm trying to get apt going on this machine so that I can upgrade it to slink. I manually installed apt, libc6, libstdc++2.9 and such from slink and then resolved as many of the conflicts and such by hand as I could. However, I'm not sure what to do about this one: gusgus:~ # apt-get check Updating package file cache...done Updating package status cache...done Checking system integrity...dependency error You might want to run `apt-get -f install' to correct these. Sorry, but the following packages are broken - this means they have unmet dependencies: apt: Depends:libc6 Libc6 is, of course, installed: gusgus:~ # dpkg -s libc6 Package: libc6 Status: install ok installed Priority: required Section: base Installed-Size: 1582 Maintainer: Joel Klecker [EMAIL PROTECTED] Source: glibc Version: 2.0.7-19981211-1 Replaces: libc6-dev, ldso Pre-Depends: ldso (= 1.8.10-1) Recommends: timezone, locales Conflicts: libc5 ( 5.4.33-7), libpthread0 ( 0.7-10), libstdc++2.8 (= 2.90.29-1), libstdc++2.9 ( 2.91.59-2) Description: GNU Libc: shared libraries Contains the standard libraries that are used by nearly all programs on the system. This package includes shared versions of the standard C library and the standard math library among others. Any ideas how to get around this one? I'm using apt version 0.1.9. Thanks! PeeWee -- email: [EMAIL PROTECTED] - useless: http://www.scc.mi.org/peewee/ - efnet: Pwe Bad signs are everywhere coach. I tend to ignore them The Era of Big Numbers
libc6_2.0.7v-1? (was: Re: Hamm beta upgrade to Slink)
[I probably should have included much of this in my post last night, but I seemed to be dying of flu at the time...] On Sun, Jan 10, 1999 at 09:36:38PM -0700, Jason Gunthorpe spewed forth: On Sun, 10 Jan 1999, Jason Wright wrote: gusgus:~ # dpkg -s libc6 Version: 2.0.7-19981211-1 Ooops, this is the evil libc6 : Use aptv3 from http://www.debian.org/~jgg or use the slink libc6. This is kinda the problem. :) Steve Lamb also suggested the same thing, but this *is* the slink libc6: gusgus:/var/tmp ] lftp ftp.debian.org lftp ftp.debian.org:~ cd debian/dists/slink/main/binary-i386/base cd ok, cwd=/debian/dists/slink/main/binary-i386/base lftp ftp.debian.org:/debian/dists/slink/main/binary-i386/base ls -l libc6_* -rw-r--r-- 1 ftp ftp612652 Jan 9 23:46 libc6_2.0.7-19981211-1.deb Which I was working on this last night, I did think hey, 2.0.7u-1 2.0.7-19981211-1, but dpkg did let me install apt with libc6_2.0.7-19981211-1 installed on the system, so I didn't worry about it too much. Mark Wagnon posted a URL for libc6_2.0.7v-1 off of ftp.cdrom.com's mirror, but that file isn't there this morning. http://www.debian.org/Packages/frozen/base/libc6.html points to six different mirrors, none of which have the file. I looked in ftp://ftp.de.debian.org/incoming, but there was no libc6 there. Ivan Moore suggested that I do an 'apt-get -f install' and letting apt work everything out, but apt's solution to this is to uninstall itself: gusgus:~ # apt-get -f install Updating package status cache...done Checking system integrity...dependency error Correcting dependencies...ok The following packages will be REMOVED: apt 0 packages upgraded, 0 newly installed, 1 to remove and 278 not upgraded. Need to get 0b of archives. After unpacking 1068k will be freed. Do you want to continue? [Y/n] n Any idea where the new libc6 is living? Thanks for all the responses so far. PeeWee -- email: [EMAIL PROTECTED] - useless: http://www.scc.mi.org/peewee/ - efnet: Pwe Bad signs are everywhere coach. I tend to ignore them The Era of Big Numbers
Re: X hates me after hardware upgrade
On Tue, Jun 30, 1998 at 04:09:27PM -0700, Ian Eure spewed forth: (--) SVGA: S3 ViRGE chipset: please load libs3v.a module (--) SVGA: CHIPS: chip revision: 6 (--) SVGA: Chipset: ct65530 (--) SVGA: CHIPS: no monitor detected. (**) SVGA: CHIPS: 4096 kB VRAM (--) SVGA: CHIPS: TFT probed. (--) SVGA: CHIPS: CRT (--) SVGA: CHIPS: PI Bus (--) SVGA: CHIPS: Depth 16 only supported with linear addressing (--) SVGA: chipset: generic (**) SVGA: videoram: 4096k (--) SVGA: clocks: 25.18 (**) SVGA: 16bpp not supported for this chipset *** A configured device found, but display modes could not be resolved.*** A little summary, and then an update on my situation here. Ian Eure was kind enough to walk through the above errors for me and concluded that things were weird in that the SVGA server seemed to be detecting three video adapters when, in fact, only an STB Nitro 3D (ViRGE GX chipset) was installed. I previously had the Nitro working in my old machine and I had copied that XF86Config over to my new machine. I just pulled the Nitro, replaced it with a spare #9 Motion 771 (S3 968), installed the S3 server and told my XF86Config about it. I changed no other hardward, software of BIOS settings, but I have X again. Since the Nitro was easily outperforming the 771 for me, I'd like to get it working again in the new machine. Any ideas why it might not be working? The motherboard is an ASUS PE5NP4 with dual P133's installed. Thanks... PeeWee -- email: [EMAIL PROTECTED] - useless: http://www.scc.mi.org/peewee/ - efnet: Pwe Persons with names like Sierra or Sequoia will not be permitted to sing the blues no matter how many men they shoot in Memphis. -Mike Avery -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: X hates me after hardware upgrade
On Tue, Jun 30, 1998 at 04:09:27PM -0700, Ian Eure spewed forth: It looks to me like there might be an onboard ct adapter on the new motherboard, or a second card. Check under /proc/pci and see what devices it finds... Look and see if more than one display adapter is getting detected. For the record, what kind of video card do you have? The video board is an STB Nitro 3D and it is the only one in the machine. The new motherboard is an ASUS PE5NP4, which does not have onboard video. I essentially rescued the new MB from the junkpile, so when I got it, the BIOS was in unknown shape - the first thing that I did to it was reset the it to defaults. I just took the machine down to replace the SCSI controller (swapped a 2940W for a 2940UW) and when I brought it back up, I checked the BIOS and disabled the video BIOS shadow, which made no difference. I've also tried booting into 2.0.33 instead of 2.1.10[67], which didn't help. FWIW, the video is working just fine with svgalib and svgatextmode: 1024x768x16.7mil and 132x60x9, respectively. I'm about to wander off and load NT on the other disk, which I'm sure will work fine as well. PCI devices found: Bus 0, device 0, function 0: Host bridge: Intel 82434LX Mercury/Neptune (rev 17). Slow devsel. Master Capable. Latency=32. Bus 0, device 2, function 0: Non-VGA device: Intel 82375EB (rev 3). Medium devsel. Master Capable. No bursts. Bus 0, device 5, function 0: Ethernet controller: DEC DC21140 (rev 34). Medium devsel. Fast back-to-back capable. IRQ 9. Master Capable. Latency=80. Min Gnt=20.Max Lat=40. I/O at 0xe800 [0xe801]. Non-prefetchable 32 bit memory at 0xfbf9f000 [0xfbf9f000]. Bus 0, device 6, function 0: VGA compatible controller: S3 Inc. ViRGE/DX or /GX (rev 1). Medium devsel. IRQ b. Master Capable. Latency=80. Min Gnt=4.Max Lat=255. Non-prefetchable 32 bit memory at 0xf400 [0xf400]. Bus 0, device 7, function 0: SCSI storage controller: Adaptec AIC-7881U (rev 0). Medium devsel. Fast back-to-back capable. IRQ a. Master Capable. Latency=80. Min Gnt=8.Max Lat=8. I/O at 0xe400 [0xe401]. Non-prefetchable 32 bit memory at 0xf3fff000 [0xf3fff000]. While we're on the subject of my PCI bus, here's how I have it configured, since this is a custom kernel: CONFIG_PCI=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_QUIRKS=y CONFIG_PCI_OPTIMIZE=y CONFIG_PCI_OLD_PROC=y And here's how the kernel sees it on bootup: Jun 30 21:08:07 logos kernel: PCI: PCI BIOS revision 2.00 entry at 0xfb5e0 Jun 30 21:08:07 logos kernel: PCI: Using configuration type 2 Jun 30 21:08:07 logos kernel: PCI: Probing PCI hardware Jun 30 21:08:07 logos kernel: PCI: 00:00 [8086/04a3]: Bridge optimization (00) Jun 30 21:08:07 logos kernel: Cache L2: Not supported. Jun 30 21:08:07 logos kernel: CPU-PCI posted write: off - on. Jun 30 21:08:07 logos kernel: CPU-Memory posted write: off - on. Jun 30 21:08:07 logos kernel: PCI-Memory posted write: off - on. Jun 30 21:08:07 logos kernel: PCI burst: on. PeeWee -- email: [EMAIL PROTECTED] - useless: http://www.scc.mi.org/peewee/ - efnet: Pwe Persons with names like Sierra or Sequoia will not be permitted to sing the blues no matter how many men they shoot in Memphis. -Mike Avery -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
X hates me after hardware upgrade
Clue required, please. I've never had XF86 give me an error like this one. I just completed transferring my existing hardware to a new case/motherboard. If it matters, I went from a P90 to a dual P133. I moved over the disks, RAM and boards - everything but the P90 motherboard. Everything works fine after the move, except X - errors and my XF86config are attached. Prior to moving my hardware into the new case, I pulled out a spare SCSI controller and disk and did a fresh install of Hamm onto the new machine. I got X working using my main monitor (the XE17 referenced in the config) and a spare #9 Motion 771 I had lying around. I had the new machine running fine like that for a week and then I moved the hardware. After the move, I deleted the device section for the 771, copied over (from memory, I admit) the XE17's monitor section and made the appropriate changes to the screen section of the XF86config. In addition, I'd had the STB Nitro working (and very well at that) in the P90 for several months prior to the hardware move using the Dell VS17 referenced in the config. So, I've had both the XE17 and the Nitro working, but never both together. Other possibly useful info: logos:/misc/losers/peewee ] dpkg -s xserver-svga Package: xserver-svga Status: install ok installed Priority: optional Section: x11 Installed-Size: 2877 Maintainer: Branden Robinson [EMAIL PROTECTED] Source: xfree86 Version: 3.3.2.2-1 Replaces: xbase (= 3.3.2-4) Provides: xserver Depends: makedev (= 1.6-8), libc6, zlib1g logos:/misc/losers/peewee ] uname -a Linux logos 2.1.106 #1 SMP Sun Jun 14 14:17:44 PDT 1998 i586 unknown PeeWee -- email: [EMAIL PROTECTED] - useless: http://www.scc.mi.org/peewee/ - efnet: Pwe Persons with names like Sierra or Sequoia will not be permitted to sing the blues no matter how many men they shoot in Memphis. -Mike Avery XFree86 Version 3.3.2 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: March 2 1998 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: Linux 2.0.32 i686 [ELF] Configured drivers: SVGA: server for SVGA graphics adaptors (Patchlevel 0): NV1, STG2000, RIVA128, ET4000, ET4000W32, ET4000W32i, ET4000W32i_rev_b, ET4000W32i_rev_c, ET4000W32p, ET4000W32p_rev_a, ET4000W32p_rev_b, ET4000W32p_rev_c, ET4000W32p_rev_d, ET6000, ET6100, et3000, pvga1, wd90c00, wd90c10, wd90c30, wd90c24, wd90c31, wd90c33, gvga, ati, sis86c201, sis86c202, sis86c205, tvga8200lx, tvga8800cs, tvga8900b, tvga8900c, tvga8900cl, tvga8900d, tvga9000, tvga9000i, tvga9100b, tvga9200cxr, tgui9400cxi, tgui9420, tgui9420dgi, tgui9430dgi, tgui9440agi, cyber9320, tgui9660, tgui9680, tgui9682, tgui9685, cyber9382, cyber9385, cyber9388, cyber9397, cyber9520, 3dimage975, 3dimage985, clgd5420, clgd5422, clgd5424, clgd5426, clgd5428, clgd5429, clgd5430, clgd5434, clgd5436, clgd5446, clgd5480, clgd5462, clgd5464, clgd5465, clgd6205, clgd6215, clgd6225, clgd6235, clgd7541, clgd7542, clgd7543, clgd7548, clgd7555, ncr77c22, ncr77c22e, cpq_avga, mga2064w, mga1064sg, mga2164w, mga2164w AGP, oti067, oti077, oti087, oti037c, al2101, ali2228, ali2301, ali2302, ali2308, ali2401, cl6410, cl6412, cl6420, cl6440, video7, ark1000vl, ark1000pv, ark2000pv, ark2000mt, mx, realtek, AP6422, AT24, AT3D, s3_virge, s3_svga, ct65520, ct65525, ct65530, ct65535, ct65540, ct65545, ct65546, ct65548, ct65550, ct65554, ct6, ct68554, ct64200, ct64300, generic (using VT number 7) XF86Config: /etc/X11/XF86Config (**) stands for supplied, (--) stands for probed/default values (**) XKB: rules: xfree86 (**) XKB: model: pc101 (**) XKB: layout: us (**) XKB: keymap: xfree86(us) (overrides other XKB settings) (**) Mouse: type: MicroSoft, device: /dev/ttyS0, baudrate: 1200 (**) Mouse: buttons: 3 (**) SVGA: Graphics device ID: ViRGE GX (**) SVGA: Monitor ID: NEC XE17 (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc:unscaled,/usr/X11R6/lib/X11/fonts/75dpi:unscaled,/usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/,/usr/X11R6/lib/X11/fonts/cyrillic/ (--) SVGA: S3 ViRGE chipset: please load libs3v.a module (--) SVGA: CHIPS: chip revision: 6 (--) SVGA: Chipset: ct65530 (--) SVGA: CHIPS: no monitor detected. (**) SVGA: CHIPS: 4096 kB VRAM (--) SVGA: CHIPS: TFT probed. (--) SVGA: CHIPS: CRT (--) SVGA: CHIPS: PI Bus (--) SVGA: CHIPS: Depth 16 only supported with linear addressing (--) SVGA: chipset: generic (**) SVGA: videoram: 4096k (--) SVGA: clocks: 25.18 (**) SVGA: 16bpp not supported for this chipset *** A configured device found, but display modes could not be resolved.*** Fatal
Re: X hates me after hardware upgrade
Sorry to follow up on my own post. I did attach my XF86Config but I either screwed up, or something ate the second attachment to my previous message. Here's the config... PeeWee # ** # Files section. This allows default font and rgb paths to be set # ** Section Files RgbPath /usr/X11R6/lib/X11/rgb FontPath/usr/X11R6/lib/X11/fonts/misc:unscaled FontPath/usr/X11R6/lib/X11/fonts/75dpi:unscaled FontPath/usr/X11R6/lib/X11/fonts/100dpi:unscaled FontPath/usr/X11R6/lib/X11/fonts/Type1/ FontPath/usr/X11R6/lib/X11/fonts/Speedo/ FontPath/usr/X11R6/lib/X11/fonts/misc/ FontPath/usr/X11R6/lib/X11/fonts/75dpi/ FontPath/usr/X11R6/lib/X11/fonts/100dpi/ FontPath/usr/X11R6/lib/X11/fonts/cyrillic/ #FontPath /opt/applix/axfonts/all_pcf EndSection # ** # Server flags section. # ** Section ServerFlags #DontZap EndSection # ** # Input devices # ** # ** # Keyboard section # ** Section Keyboard ProtocolStandard AutoRepeat 500 5 XkbRulesxfree86 XkbModelpc101 XkbLayout us XkbKeymap xfree86(us) #ServerNumLock EndSection # ** # Pointer section # ** Section Pointer ProtocolMicroSoft Device /dev/ttyS0 #Protocol PS/2 #Device /dev/psaux #Emulate3Buttons EndSection # ** # Monitor section # ** Section Monitor Identifier NEC XE17 VendorName NEC ModelName XE17 BandWidth 85.0 HorizSync 31.0-65.0 VertRefresh 55.0-120.0 ModeLine 640x480 28.3 640 680 720 864 480 488 491 521 ModeLine 800x600 40 800 848 1000 1056 600 605 607 633 ModeLine 1024x768 65 1024 1032 1176 1344 768 771 777 806 ModeLine 1152x900 80 1152 1200 1280 1528 900 900 903 930 EndSection Section Monitor Identifier Dell VS17 VendorName Dell ModelName VS17 BandWidth 78.0 HorizSync 30.0-62.0 VertRefresh 50-90 ModeLine 640x480 28.3 640 680 720 864 480 488 491 521 ModeLine 800x600 40 800 848 1000 1056 600 605 607 633 ModeLine 1024x768 65 1024 1032 1176 1344 768 771 777 806 ModeLine 1152x900 80 1152 1200 1280 1528 900 900 903 930 EndSection # ** # Graphics device section # ** # Any number of graphics device sections may be present Section Device VendorName Number Nine Identifier #9 GXE 64 Pro BoardName 9GXE64 Pro VideoRam 2048 Option number_nine Option dac_8_bit EndSection Section Device VendorName STB Identifier ViRGE GX VideoRam 4096 Option fifo_aggressive Option pci_burst_on Option pci_retry EndSection Section Device Identifier #9 GXE 64 Shitty ChipSet generic ClockChip icd2061a RamDac ti3025 EndSection # ** # Screen sections # ** Section Screen #Driver accel Driver svga #Device #9 GXE 64 Pro Device ViRGE GX Monitor NEC XE17 #MonitorDell VS17 DefaultColorDepth 16 Subsection Display Depth 16 Modes 1152x900 1024x768 800x600 640x480 EndSubsection Subsection Display Depth 8 Modes 1152x900 1024x768 800x600 640x480 EndSubsection EndSection -- email: [EMAIL PROTECTED] - useless: http://www.scc.mi.org/peewee/ - efnet: Pwe Persons with names like Sierra or Sequoia will not be permitted to sing the blues no matter how many men they shoot in Memphis. -Mike Avery -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X hates me after hardware upgrade
On Tue, Jun 30, 1998 at 10:25:16AM -0500, Richard E. Hawkins Esq. spewed forth: try X :1 -bpp 8 -query localhost (assuming that you're using xdm. use similar arguments without the query for startx) No xdm here. If I try to start X in 8bpp, I get garbage and have to zap the server. Once, I had to reboot to get my video back. Setup from scratch for a very simple 8 bit display (you can now choose this), and start moving up from there. Fresh configs built with either XF86Setup or xf86config produce the same errors: (--) SVGA: S3 ViRGE chipset: please load libs3v.a module (--) SVGA: CHIPS: chip revision: 0 (--) SVGA: Chipset: ct65530 (--) SVGA: CHIPS: no monitor detected. (**) SVGA: CHIPS: 4096 kB VRAM (--) SVGA: CHIPS: TFT probed. (--) SVGA: CHIPS: CRT (--) SVGA: CHIPS: PI Bus (--) SVGA: CHIPS: Depth 16 only supported with linear addressing (--) SVGA: chipset: generic (**) SVGA: videoram: 4096k (--) SVGA: clocks: 25.18 I've tried selecting both generic S3 ViRGE GX and STB Nitro 3D. For teh record, SuperProbe reports the following: First video: Super-VGA Chipset: S3 ViRGE/GX (PCI Probed) Memory: 4096 Kbytes RAMDAC: Generic 8-bit pseudo-color DAC (with 6-bit wide lookup tables (or in 6-bit mode)) The other suggestion I've gotten thus far was to make sure that I had linear addressing for the board turned on. The readme for the board (README.S3V, which covers configs for both the S3V and SVGA servers for this chipset) specifically indicates that linear addressing is the default for the SVGA driver and that the 'nolinear' option is not supported. PeeWee -- email: [EMAIL PROTECTED] - useless: http://www.scc.mi.org/peewee/ - efnet: Pwe Persons with names like Sierra or Sequoia will not be permitted to sing the blues no matter how many men they shoot in Memphis. -Mike Avery -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
bogus SYN flood?
Howdy... I came home to find my workstation thrashing - errors are appended to this message. Kerneld was consuming over 50meg of memory, so I bounced it, which seems to have cleared the problem up. Overmind is a P90, 2.0.32 and is fairly well synced with Hamm. Modutils is 2.1.55-4. Current uptime is almost 13 days. The machine was idle at the time. I've been unsubscribed from linux-kernel since before 2.0.32 came out, so I don't know if this problem has been discussed over there. I just resubscribed. PeeWee Full transcript of errors from /var/adm/messages follows: Dec 5 14:30:01 overmind kernel: validated probe(127.0.0.1:726, 127.0.0.1:778, -580073059) Dec 5 14:45:01 overmind kernel: Warning: possible SYN flood from 127.0.0.1 on 127.0.0.1:778. Sending cookies. Dec 5 14:45:01 overmind kernel: validated probe(127.0.0.1:804, 127.0.0.1:778, 1528032577) Dec 5 15:00:02 overmind kernel: Warning: possible SYN flood from 127.0.0.1 on 127.0.0.1:778. Sending cookies. Dec 5 15:00:03 overmind kernel: validated probe(127.0.0.1:871, 127.0.0.1:778, -1098321254) Dec 5 15:05:05 overmind kernel: flushed 1084 old SYSVIPC messages1Ouch, no kerneld for message 2147442165 Dec 5 15:15:01 overmind kernel: flushed 1086 old SYSVIPC messages6Warning: possible SYN flood from 127.0.0.1 on 127.0.0.1:778. Sending cookies. Dec 5 15:15:01 overmind kernel: validated probe(127.0.0.1:942, 127.0.0.1:778, -1341543110) Dec 5 15:30:00 overmind kernel: flushed 1079 old SYSVIPC messages4flushed 1085 old SYSVIPC messages6Warning: possible SYN flood from 127.0.0.1 on 127.0.0.1:778. Sending cookies. Dec 5 15:30:01 overmind kernel: validated probe(127.0.0.1:1000, 127.0.0.1:778, 754024873) Dec 5 15:45:01 overmind kernel: flushed 1084 old SYSVIPC messages6Warning: possible SYN flood from 127.0.0.1 on 127.0.0.1:778. Sending cookies. Dec 5 15:45:01 overmind kernel: validated probe(127.0.0.1:640, 127.0.0.1:778, -2079395917) Dec 5 16:00:01 overmind kernel: flushed 1086 old SYSVIPC messages4flushed 1084 old SYSVIPC messages6Warning: possible SYN flood from 127.0.0.1 on 127.0.0.1:778. Sending cookies. Dec 5 16:00:01 overmind kernel: validated probe(127.0.0.1:696, 127.0.0.1:778, 521267003) Dec 5 16:05:01 overmind kernel: flushed 1084 old SYSVIPC messages6Warning: possible SYN flood from 127.0.0.1 on 127.0.0.1:778. Sending cookies. Dec 5 16:05:01 overmind kernel: validated probe(127.0.0.1:720, 127.0.0.1:778, -1748167046) Dec 5 16:05:07 overmind kernel: Ouch, no kerneld for message 2147442166 Dec 5 16:15:00 overmind kernel: flushed 1084 old SYSVIPC messages6Warning: possible SYN flood from 127.0.0.1 on 127.0.0.1:778. Sending cookies. Dec 5 16:15:01 overmind kernel: validated probe(127.0.0.1:766, 127.0.0.1:778, 891621602) Dec 5 16:30:00 overmind kernel: flushed 1083 old SYSVIPC messages4flushed 1080 old SYSVIPC messages6Warning: possible SYN flood from 127.0.0.1 on 127.0.0.1:778. Sending cookies. Dec 5 16:30:00 overmind kernel: validated probe(127.0.0.1:824, 127.0.0.1:778, 723969002) Dec 5 16:45:00 overmind kernel: flushed 1085 old SYSVIPC messages4flushed 1084 old SYSVIPC messages6Warning: possible SYN flood from 127.0.0.1 on 127.0.0.1:778. Sending cookies. Dec 5 16:45:00 overmind kernel: validated probe(127.0.0.1:887, 127.0.0.1:778, 29768560) Dec 5 17:00:01 overmind kernel: flushed 1086 old SYSVIPC messages4flushed 1084 old SYSVIPC messages6Warning: possible SYN flood from 127.0.0.1 on 127.0.0.1:778. Sending cookies. Dec 5 17:00:01 overmind kernel: validated probe(127.0.0.1:946, 127.0.0.1:778, 525624201) Dec 5 17:05:01 overmind kernel: Warning: possible SYN flood from 127.0.0.1 on 127.0.0.1:778. Sending cookies. Dec 5 17:05:01 overmind kernel: validated probe(127.0.0.1:970, 127.0.0.1:778, -1800602240) Dec 5 17:05:05 overmind kernel: Ouch, no kerneld for message 2147442167 Dec 5 17:15:01 overmind kernel: flushed 1082 old SYSVIPC messages6Warning: possible SYN flood from 127.0.0.1 on 127.0.0.1:778. Sending cookies. Dec 5 17:15:01 overmind kernel: validated probe(127.0.0.1:1016, 127.0.0.1:778, 1304971566) Dec 5 17:30:00 overmind kernel: flushed 1086 old SYSVIPC messages4flushed 1081 old SYSVIPC messages6Warning: possible SYN flood from 127.0.0.1 on 127.0.0.1:778. Sending cookies. Dec 5 17:30:00 overmind kernel: validated probe(127.0.0.1:650, 127.0.0.1:778, -1483188710) Dec 5 17:45:01 overmind kernel: flushed 1085 old SYSVIPC messages4flushed 1085 old SYSVIPC messages6Warning: possible SYN flood from 127.0.0.1 on 127.0.0.1:778. Sending cookies. Dec 5 17:45:01 overmind kernel: validated probe(127.0.0.1:714, 127.0.0.1:778, -1528760368) Dec 5 18:00:01 overmind kernel: flushed 1086 old SYSVIPC messages4flushed 1085 old SYSVIPC messages6Warning: possible SYN flood from 127.0.0.1 on 127.0.0.1:778. Sending cookies. Dec 5 18:00:01 overmind kernel: validated probe(127.0.0.1:770, 127.0.0.1:778, -2043635234) Dec 5 18:05:02 overmind
Re: dpkg error :-(
On Sun, Nov 30, 1997 at 12:14:45AM +0100, Vaclav Hula spewed forth: At home, when I tried to install some non-official package, I got this error: gzip: stdout: Broken pipe dpkg-deb: subprocess gzip -dc returned error exit status 1 dpkg: error processing /root/L3263TMP.deb (--install): subprocess dpkg-deb --fsys-tarfile returned error exit status 2 Errors were encountered while processing: /root/L3263TMP.deb When I tried to install this in my work, it worked well. Can anyone help? I've gotten this trying to install truncated or otherwise corrupted packages. PeeWee -- Learn to knit for all I care, but find something rhythmical to do before bed -Amanda Robinson -- personal: [EMAIL PROTECTED] http://www.scc.mi.org/peewee/ work: [EMAIL PROTECTED] finger [EMAIL PROTECTED] for pgp2.6.2 public key -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
xmcd_2.2-4.deb problems
Howdy... The current hamm xmcd package seems to not like running on my machine. First, it complains about having insufficient privlidges: overmind:/temple/sw/linux/debian ] /usr/X11R6/bin/xmcd xmcd Fatal Error: Xmcd binary permissions error: It should be setuid root. Please have your system administrator correct this. It's setgid cdrom, and /dev/scd0 is owned by group cdrom, so it should have sufficient permissions to read the device: overmind:/temple/sw/linux/debian ] ls -l /usr/X11R6/bin/xmcd -rwxr-sr-x 1 root cdrom 230572 Oct 13 08:12 /usr/X11R6/bin/xmcd overmind:/temple/sw/linux/debian ] ls -l /dev/scd0 brw-rw 1 root cdrom 11, 0 Dec 19 1996 /dev/scd0 I'm also in group cdrom, which shouldn't matter since the binary is setgid: overmind:/temple/sw/linux/debian ] grep cdrom /etc/group cdrom:*:24:peewee overmind:/temple/sw/linux/debian ] ypcat group | grep cdrom cdrom:*:24:peewee Setting the binary +s allowed it to run, and start sucking all available memory: overmind:/var/adm ] ps -auxww | grep xmcd peewee 28825 0.0 0.5 836 360 p0 S 19:17 0:00 grep xmcd root 28809 43.3 50.7 64088 32116 p1 D 19:16 0:24 /usr/X11R6/bin/xmcd If it matters, it was attempting to do a CDDB lookup at the time. PeeWee -- Learn to knit for all I care, but find something rhythmical to do before bed -Amanda Robinson -- personal: [EMAIL PROTECTED] http://www.scc.mi.org/peewee/ work: [EMAIL PROTECTED] finger [EMAIL PROTECTED] for pgp2.6.2 public key -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
ncurses3.0_1.9.9e-2?
I'd like to upgrade to unstable, following the howto, but I can't seem to find the package ncurses3.0_1.9.9e-2. The latest rev I can find is ncurses3.0_1.9.9e-1, which is what's already installed on my system. Where can I find -2? Thanks! Jason -- Learn to knit for all I care, but find something rhythmical to do before bed -Amanda Robinson -- personal: [EMAIL PROTECTED] http://www.scc.mi.org/peewee/ work: [EMAIL PROTECTED] finger [EMAIL PROTECTED] for pgp2.6.2 public key -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: alien problem (bo)
On Sat, Oct 25, 1997 at 11:35:21AM +0200, Wojtek Zabolotny spewed forth: Are you running alien from the RAW TEXT CONSOLE? (I mean: not an xterm nor Midnight Commander prompt) I got the same error running dpkg-gencontrol from debian build, when I was recompiling debian sorce packages. The reason was that I was running build from xterm or Midnight Commander. May be there is the same problem? I hope that this may help Hm...Oddly enough, that worked. PeeWee -- Learn to knit for all I care, but find something rhythmical to do before bed -Amanda Robinson -- personal: [EMAIL PROTECTED] http://www.scc.mi.org/peewee/ work: [EMAIL PROTECTED] finger [EMAIL PROTECTED] for pgp2.6.2 public key -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
alien problem (bo)
Howdy... Awhile back, I bought RedHat Motif when I thought that I'd be running their distribution. Well, I discovered that I liked Debian better and that alien, as shipped with Debian 1.2 would install the motif RPMs. I've since upgraded my installation by hand to 1.3 (without using deselect) and now alien seems unable to install the RPMs. I get the same error when trying to install other RPMs or .tar.gz's. Any ideas on why what formerly worked is now breaking would be most appreciated. PeeWee overmind:~ ] dpkg --list | egrep alien|dpkg|rpm|fileutils|shellutils|bash|perl ii alien 3.3Install RedHat and Slackware Packages with d ii bash2.0-3 The GNU Bourne Again SHell ii dpkg1.4.0.8Package maintenance system for Debian Linux ii dpkg-cross 0.1Tools for cross compiling Debian packages ii dpkg-dev1.4.0.8Package building tools for Debian Linux ii dpkg-ftp1.4.9 Ftp method for dselect. ii fileutils 3.16-2 GNU file management utilities. ii perl5.003.07-10Larry Wall's Practical Extracting and Report ii perl-debug 5.003.07-10Allow debugging perl scripts (and perl). ii perl-suid 5.003.07-10Runs setuid perl scripts. ii perl-tk b11.02-5 Perl module providing the Tk graphics librar ii rpm 2.3.8-1Red Hat Package Manager ii shellutils 1.16-2bThe GNU shell programming utilities. overmind:/tmp # alien -n rh-motif-2.0-2.i386.rpm -- Unpacking rh-motif-2.0-2.i386.rpm 3633 blocks -- Automatic package debianization -- Building the package rh-motif_2.0-3_i386.deb test -f debian/rules test root = `whoami` test -f debian/rules touch debian/build test -f debian/rules test -f debian/rules rm -rf debian/tmp install -d debian/tmp cp -a `ls | grep -v debian` debian/tmp debstd --- debstd processing -- -- Installing Documentation -- Looking for manpages in sourcepackage ** Main Package rh-motif -- Processing provided ELF libraries Sharable Library usr/X11R6/lib/libXm.so.2.0 Added ELF Library link libXm.so.2 -- Checking for executable binaries in package usr/X11R6/lib/libXm.so.2.0 ELF Binary Warning: Unusual executable location usr/X11R6/lib/libXm.so.2.0 DEBIAN/postinst Script -- Figuring out dependencies of ELF objects dpkg-shlibdeps.orig: warning: unknown output from ldd on `debian/tmp/usr/X11R6/lib/libXm.so.2.0': ` ./debian/tmp/usr/X11R6/lib/libXm.so.2.0 = ./debian/tmp/usr/X11R6/lib/libXm.so.2.0 (0x4000a000)' dpkg-shlibdeps.orig: warning: unknown output from ldd on `debian/tmp/usr/X11R6/lib/libXm.so.2.0': ` libc.so.5 = /lib/libc.so.5 (0x401d1000)' dpkg-shlibdeps.orig: warning: unknown output from ldd on `debian/tmp/usr/X11R6/lib/libXm.so.2.0': ` libXpm.so.4 = /usr/X11R6/lib/libXpm.so.4 (0x4028c000)' dpkg-shlibdeps.orig: warning: unknown output from ldd on `debian/tmp/usr/X11R6/lib/libXm.so.2.0': ` libXt.so.6 = /usr/X11R6/lib/libXt.so.6 (0x40299000)' dpkg-shlibdeps.orig: warning: unknown output from ldd on `debian/tmp/usr/X11R6/lib/libXm.so.2.0': ` libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x402db000)' dpkg-shlibdeps.orig: warning: unknown output from ldd on `debian/tmp/usr/X11R6/lib/libXm.so.2.0': ` libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x402e6000)' dpkg-shlibdeps.orig: warning: unknown output from ldd on `debian/tmp/usr/X11R6/lib/libXm.so.2.0': ` libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0x40384000)' dpkg-shlibdeps.orig: warning: unknown output from ldd on `debian/tmp/usr/X11R6/lib/libXm.so.2.0': ` libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0x4038d000)' dpkg-shlibdeps.orig: warning: ldd on `debian/tmp/usr/X11R6/lib/libXm.so.2.0' gave nothing on standard output dpkg-shlibdeps.orig: warning: unknown output from ldd on `debian/tmp/usr/X11R6/lib/libXm.so.2.0': ` ./debian/tmp/usr/X11R6/lib/libXm.so.2.0 = ./debian/tmp/usr/X11R6/lib/libXm.so.2.0 (0x4000a000)' dpkg-shlibdeps.orig: warning: unknown output from ldd on `debian/tmp/usr/X11R6/lib/libXm.so.2.0': ` libc.so.5 = /lib/libc.so.5 (0x401d1000)' dpkg-shlibdeps.orig: warning: unknown output from ldd on `debian/tmp/usr/X11R6/lib/libXm.so.2.0': ` libXpm.so.4 = /usr/X11R6/lib/libXpm.so.4 (0x4028c000)' dpkg-shlibdeps.orig: warning: unknown output from ldd on `debian/tmp/usr/X11R6/lib/libXm.so.2.0': ` libXt.so.6 = /usr/X11R6/lib/libXt.so.6 (0x40299000)' dpkg-shlibdeps.orig: warning: unknown output from ldd on `debian/tmp/usr/X11R6/lib/libXm.so.2.0': ` libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x402db000)' dpkg-shlibdeps.orig: warning: unknown output from ldd on `debian/tmp/usr/X11R6/lib/libXm.so.2.0': ` libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x402e6000)' dpkg-shlibdeps.orig: warning: unknown output from ldd on `debian/tmp/usr/X11R6/lib/libXm.so.2.0': ` libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0x40384000)' dpkg-shlibdeps.orig: warning: unknown
