Re: Kernel compilation problem
I did finally get the 4.17.11 kernel to compile so that my large drives are visible now, but I had to use a 'shotgun' approach in including as many SCSI/SATA/etc variables as possible. I do intend on comparing the non-functioning config for 4.17.11 against both the functioning config, as well as against the config for 4.9.0-7-amd. Thanks. Taren On 08/02/2018 10:30 AM, David Wright wrote: On Wed 01 Aug 2018 at 23:37:33 (-0600), Taren wrote: I'm running Stretch, with kernel 4.9.0.7, and am trying to compile a new kernel (preferably 4.17.11) into which I can boot. The kernel builds successfully, but whenever I try booting into the new kernel, I end up in emergency mode, with the error Unit dev-disk-by\x2duuid-.device has failed. The result is timeout. This device is anmd device, with two mirrors (each 2.7T in size). The submirrors are present when I boot into 4.9.0.7 (installed when the system was built). However, they do not appear to be visible under any kernel which I build and try to boot into. I've tried setting LBDAF in the kernel configuration, but that requires that a 32bit kernel be built (and x64 deselected), and I'm running on an AMD 8350 chip, which is x86_64. Kernel 4.9.0.7 does not have LBDAF set (and x64 is set), yet it's able to see my 2.7T drives, and my raid device mounts with no problem. I think this is a red herring. 32bit kernels need LBDAF for large disks because they have to be told to use 64bit addressing for them. Obviously 64bit kernels don't need telling, so that option is made unavailable. Would someone point me in the correct direction for configuring a new kernel, so that my 2T+ drives are visible? In the absence of other replies, I can only suggest (a) comparing /boot/config-4.9.0-7-amd64 with the one you've built to see whether something is missing, (b) compare the output of lsinitramfs /boot/initrd.img-4.9.0-7-amd64 with the one you've built to see likewise. I'm assuming with (b) that the disks have to be found by using the initramfs before the system can continue booting with the filesystem contained on those disks. Cheers, David.
Re: Kernel compilation problem
Correction: The kernel version I'm using (which sees my 2.7T drives) is 4.9.0-7-amd, not 4.9.0.7. I can provide the .config file for 4.17.11, if needed. On 08/01/2018 11:37 PM, Taren wrote: I'm running Stretch, with kernel 4.9.0.7, and am trying to compile a new kernel (preferably 4.17.11) into which I can boot. The kernel builds successfully, but whenever I try booting into the new kernel, I end up in emergency mode, with the error Unit dev-disk-by\x2duuid-.device has failed. The result is timeout. This device is anmd device, with two mirrors (each 2.7T in size). The submirrors are present when I boot into 4.9.0.7 (installed when the system was built). However, they do not appear to be visible under any kernel which I build and try to boot into. I've tried setting LBDAF in the kernel configuration, but that requires that a 32bit kernel be built (and x64 deselected), and I'm running on an AMD 8350 chip, which is x86_64. Kernel 4.9.0.7 does not have LBDAF set (and x64 is set), yet it's able to see my 2.7T drives, and my raid device mounts with no problem. Would someone point me in the correct direction for configuring a new kernel, so that my 2T+ drives are visible? Thanks Taren
Kernel compilation problem
I'm running Stretch, with kernel 4.9.0.7, and am trying to compile a new kernel (preferably 4.17.11) into which I can boot. The kernel builds successfully, but whenever I try booting into the new kernel, I end up in emergency mode, with the error Unit dev-disk-by\x2duuid-.device has failed. The result is timeout. This device is anmd device, with two mirrors (each 2.7T in size). The submirrors are present when I boot into 4.9.0.7 (installed when the system was built). However, they do not appear to be visible under any kernel which I build and try to boot into. I've tried setting LBDAF in the kernel configuration, but that requires that a 32bit kernel be built (and x64 deselected), and I'm running on an AMD 8350 chip, which is x86_64. Kernel 4.9.0.7 does not have LBDAF set (and x64 is set), yet it's able to see my 2.7T drives, and my raid device mounts with no problem. Would someone point me in the correct direction for configuring a new kernel, so that my 2T+ drives are visible? Thanks Taren
cfs broken / rpc.mountd getfh not implemented?
I've been using CFS successfully for half a year or more. (I had to switch from userspace NFS to kernel NFS, other than that the install went pretty smooth.) I did my first apt-get upgrade in a couple of months yesterday and it stopped working. Syslog says Sep 28 09:22:18 chee rpc.mountd: authenticated mount request from localhost:881 for /.cfsfs (/.cfsfs) Sep 28 09:22:18 chee rpc.mountd: getfh failed: Function not implemented Does that mean anything to anyone? Has anyone else had this problem?
Re: Linux on Desktops -- Are there stats anywhere?
The usual people (IDT?) quoted Linux at about 2-3% of desktop market last I remember (3-6 months ago), putting it #3 behind Windows and MacOS. Best I remember, about 6-8% server market penetration was where suddenly all the server people started supporting Linux, and 10-12% was the market penetration that Apple used to estimate that it needed to maintain to retain the support of third-party software providers. So it looks like desktop Linux is about 1-2 doublings away from the cross-over point where all the third party hardware and software vendors start scrambling to offe the best Linux support. (Makes sense: A 1-2% increase in market share isn't going to get anyone promoted. A 10% increase in market share, on the other hands, looks pretty good on the annual report.) Arcady Genkin <[EMAIL PROTECTED]> writes: > My bank rolled out a new version of web banking, which has a bug in > Java Script. I sent them a bug report, to which I got a polite reply > which boils down to ``Tough luck. We don't test on Linux.'' > > I'm writing a letter to them, and would like to include some > statistics as to how many desktop computers run Linux nowadays. > > Is anyone aware of any surveys on this subject? > > Thanks! > -- > Arcady Genkin > Thanks God I'm still an atheist! -- Luis Bunuel > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: Connection closed
> > When I connect to certain hosts via telnet (similar via ftp), I'll get a > messgae like this: > > Connected to site.whatever.edu > Escape character is '^]'. > > which is as usual > > then followed by: > > Connection closed by foreign host. > > Assume for the moment that it is not an ISP problem, is there anything > specific to my machine that is causing this? > > I'd love some hints. > > TIA, Richard > To my knowledge, this is caused by a refusal on the remote end to allow connections from random sites. I've seen the same 'behaviour' when I set my hosts.deny file to refuse connections to any site but the ones I specify in either that file, or in hosts.allow. Taren
Re: messages that jam mail readers
> In <[EMAIL PROTECTED]>, on 08/04/98 >at 02:15 PM, Taren <[EMAIL PROTECTED]> said: > > >I just went through the same exact situation with sendmail/procmail. The > >problem isn't with your system, or any software you're running on it. > >What is happening is that you're receiving email from either spoofed > >addresses which can't be resolved by your DNS server, or from site(s) on > >the net which are currently unreachable (which was my case). > > Why is the email program looking up the sender then? It seems unnecessry, > wasting time and bandwith like that. An attempt to avoid > fake mail? If so, it shouldn't hang but skip the offending message. My > current mail software (under os2) happily accept mail from anywhere - if > it gets to the ISP then it gets to me. > Mail from unreachable sites should definitely not be a problem. There are > still sites connected by UUCP that aren't reachable at all. > On my system, my email program(s) don't hang... I've no idea why fetchmail does. I use - as I indicated above - sendmail, procmail, and - I didn't mention before, mailx. When I get an email whose sender's domain won't resolve, the email sits in the 'inbox' area, and an error message is sent to the sendmail admin, as well as being logged in the mail error log. Once the domain is resolvable, the suspect email is then delivered as normal. The situation where fetchmail hangs is something which needs to be addressed with the package maintainer/software developer. Taren -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: messages that jam mail readers
> > On Tue, 4 Aug 1998, Peter Granroth wrote: > > > > Has anyone else had this problem with their mail? Could someone who > > > understands what is causing this problem explain it to me? > > > > Of course I forgot to write down the error message, but I also had problems > > getting fetchmail to get three messages (they were all from the same > > person). > > The error message was something like: > > > > SMTP error: hostname must resolve > > > > and it promptly refused to fetch any mail. > > I don't know if it's the same thing. Mine didn't bother to give me an > error message. Fetchmail just sat there in the middle of retrieving > the message like time was frozen. After waiting long enough to be quite > sure it wasn't going to continue, I hit Control C to get out of it. > I just went through the same exact situation with sendmail/procmail. The problem isn't with your system, or any software you're running on it. What is happening is that you're receiving email from either spoofed addresses which can't be resolved by your DNS server, or from site(s) on the net which are currently unreachable (which was my case). If it's the latter, wait a while (maybe up to several days), until the net problem is resolved. Taren -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: boot: unable to open initial console
There's no need to do that. Just cd /dev (or wherever your dev dir is), and type "./MAKEDEV *". That should recreate almost all the devices, with the correct permissions, afaik. > Perhaps I should just cd /mnt/dev; rm * and then remake the device > files. I've read about a command to make the devices. Can't remember > where nor what the command was. > > Anyone know where to go to get info on recreating the device files ? > > Thanks, > > Gerald > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: boot: unable to open initial console
> > VHS: Mounted root (ext2 filesystem) readonly. > > thenUnable to open an initial console > > > > Looks like /dev/tty0 isn't there. > > Are use sure you did copy the devices correctly (cp does not copy > devices correctly, use tar or cpio). > > Dirk > Or the permissions aren't set right. I've found that when copying files from /dev, the permissions rarely stay the way they were originally Taren -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: Hamm and 3com's 905 PCI.
> > > > > You need to mount whatever directory (read: file system) you were mounting > > on the RedHat system. If you are mounting it as root (which - I think - is > > the only way you /can/ mount a fs), then it doesn't matter where you mount > > it on your local system. The preferred place is /mnt. > > That wasn't my question, the question was what directory to mount ON THE > SERVER. > That's what I was referring to, with the '/debian' and '/pub/debian' paths. The command I would use is (for example): mount -t nfs ftp.kernel.org:/pub/mnt ^^^ remote server ^^ ^^ local mount point Taren -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: Hamm and 3com's 905 PCI.
> > > > I forgot to mension it before, but the reply I get is: > > mount: RPC: Port mapper failure - RPC: Timed Out > > > > Can you help? > > Liran. > > --- > > http://www.math.tau.ac.il/~liranz/ > > > > It sounds as if the problem is not with your modem, but with the nfs server. ^ (I meant ethernet card) > I've had that error when the file system I have been trying to mount hasn't > been properly exported on the far end (i.e., the nfs server's side). You > might > try bouncing your system, on the off chance the problem is on your end... but > I'd contact the administrator of the nfs server and make sure your DNS and/or > IP address is included in the /etc/exports file on the server. > > Taren > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null > -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: Hamm and 3com's 905 PCI.
> > BTW: When I get it to work (And it will work today, whether the machine > wants to or not), what is the directory to mount? (/dists, > /dists/hamm, /dists/hamm/hamm, /dists/hamm/hamm/binary-i386 , any other > locatoin?) - just to save my time... > You need to mount whatever directory (read: file system) you were mounting on the RedHat system. If you are mounting it as root (which - I think - is the only way you /can/ mount a fs), then it doesn't matter where you mount it on your local system. The preferred place is /mnt. Make sure you are mounting the file system with the exact name the nfs server specifies (such as /pub/debian, or /debian), and not /debian/dists, for example, assuming that /pub/debian, or /debian, is what has been exported. Taren -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: Hamm and 3com's 905 PCI.
> > I forgot to mension it before, but the reply I get is: > mount: RPC: Port mapper failure - RPC: Timed Out > > Can you help? > Liran. > --- > http://www.math.tau.ac.il/~liranz/ > It sounds as if the problem is not with your modem, but with the nfs server. I've had that error when the file system I have been trying to mount hasn't been properly exported on the far end (i.e., the nfs server's side). You might try bouncing your system, on the off chance the problem is on your end... but I'd contact the administrator of the nfs server and make sure your DNS and/or IP address is included in the /etc/exports file on the server. Taren -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: Hamm and 3com's 905 PCI.
> > The problem is that the installation floppies (the drv1440, I mean) > doesn't have 3com 90x PCI drivers, and I can't work. (I'm writing this > from my other computer that has RedHat (that will hopefully become > Debian as soon as I can get it to work with the network card)). > What you need to select is the 3c59x driver. It works equally well for 3c59x and 3c905 NICs. I've been using that driver for months now, with very little problem. Taren -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: Problems with kernels 2.1.110 & 2.1.111
> > > found that I am getting the following error(s) whenever I boot: > > > > VFS: Mounted root (ext2 filesystem) readonly. > > Freeing unused kernel memory: 40k freed > > ===> stuck on smp_invalidate_needed IPI wait (CPU#0) > > Adding Swap: 130748k swap-space (priority -1) > > > > I have exactly the same problem here (GA 686 LX2 Dual PII 266, NE2000 Clone, > NCR810, Matrox Mill. II AGP). > > My observations: > 2.1.10[3-9] seemed to have worked reliable. > 2.1.110 sometimes freezes badly (3 times in 2 days) during parallel > compilation > jobs (no log-file entry, only cold-start possible). Afterwards, the partitions > which were used during these compilation jobs are corrupted. > 2.1.111 hangs with the symptoms described above. > > Ralf. > I applied the pre-2.1.112-1 patch, and have not had this problem since. So... It appears they've fixed the problem in the pre-2.1.112 patch. Taren -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: Updated pidentd patch?
Look on ftp://ftp.lysator.liu.se, in /pub/unix/ident/servers. You'll find pidentd-2.7.4.tar.gz, pidentd--2.8.2.tar.gz, pidentd-2.8.3.tar.gz and pidentd-3.0b1.tar.gz there, as well as older versions. Taren > Does any one have or know where I can get an update pidentd patch. I got > the source for pidentd-2.7.4 and tried applying the pidentd-2.7*4 patches, > and neither were succesfull. Could someone tell me where I can get an > updated patch, or how I can go about patching pidentd to include socks5 > support? > > Thank you, > Tom > -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Previous posts
This is just to thank all of those who responded to my original post, and repost, about my problems with setting up ipchains... Your help was overwhelming. Taren -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
ipchains config problems
any 'ipchains -L' on both of the internal systems shows: Chain input (policy ACCEPT): Chain forward (policy ACCEPT): Chain output (policy ACCEPT): == The setup, despite the fact that I only have three systems (one of which is the gateway system), seems to be very complicated - especially for someone who is just starting to learn how to use masquerading and forwarding. My questions are: 1. Am I on the correct track for the rules on the gateway system? 2. Do I need rules forwarding packets from the internal NIC to the external NIC? 3. On the internal systems, do I need to specify where the packets are to be forwarded (using ipchains rules)? If so, what form do they take? 4. When using ipfwadm (on 2.0.xx kernels), I have the GS as an internal gate- way for the other two internal systems. Is this necessary for ipchains? Any help with this would be greatly appreciated. Thanks, Taren -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
dpkg-mountable
I have a (partial) mirror of the debian distribution maintained on my system, for my personal use, and keep both the 'frozen' and 'unstable' sections for upgrading both my main system, as well as a couple of smaller systems. I have tried using dpkg-mountable (from dselect) to install from my archives, yet the way it is currently set up, I am only able to set one main distribution, plus a non-us distribution and a 'local' area. It appears impossible to have dpkg-mountable (and this applies to the nfs method as well) use more than one major distribution at once, which pretty much makes the dual distributions I have useless as far as accessing them via dpkg-mountable goes. This strikes me as a rather poor choice in design of this installation method (my feeling also applies to the nfs method), since - for those of us who have more than one distribution they wish to install from - it limits us to using ftp, which can take hours to complete (the last time I tried using ftp, it took me over 12 hours, and I have a cable-modem connection - at, effectively, 10MB/sec transfer rate - to the internet). If there is a work-around to installing via either nfs or dpkg-mountable, or both (and especially dpkg-mountable), which would allow setting more than one main distribution source, I would greatly appreciate it if someone would let me know. Thanks, Taren -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: SMP, again
. . . > > and top still shows no signs of a second processor :( > > Am I still missing something? It's dual P-II's (gateway ns7000) > > rick > TOP, as it is normally shipped, does not show a second CPU. It is designed for single-CPU systems only. If you want to get a multiple-CPU top, look on http://www-isia.cma.fr/~forissie/smp_kernel_patch/index.html This site carries several patches for 2.0.x kernels, as well as patches and programs which will show multiple CPU's. Also, check out sunsite.unc.edu:/pub/Linux/system/status/xstatus for other programs which show multiple-CPU statistics. Taren -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: SyQuest
> Will the release of Debian 2.0 support SyQuest removable drives in any > way? I know there is a way to make the Iomega parallel port version of > the zip drive work in Linux, but not the SyQuest EZFlyer. Is there going > to be any support for the SyQuest parallel port drives and/or any other > SyQuest removable drives? > > Rob There is a driver available for the Syquest EZFlyer, as I used it with mine, until the drive went belly up. Actually... if you have an IDE parallel-port version of the EZFlyer, you can choose Parallel Port IDE device support, under 'Block Devices', and it will work. As far as SCSI or straight IDE support, I don't know if it is available or not. Taren -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: netscape 4.05
> KYL> I had installed Netscape 4.05 and setting up things but I cant > running > KYL> netscape to excute itself. it looks nothing > > KYL> How do user run the netscape to execute? > > You also need to be logged in on a regular user account. Netscape 4.05 > won't let you run it as root. > > Steve > To my knowledge, this applies only to Debian distributions; The wrapper program included in the Redhat distribution, at least, does not prohibit root from running Netscape. Taren -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
scsi drive recognition problems
I've been having problems when (re)installing the Debian distribution using the 2.0.8_1998-06-23 *14* installation disk images. On two different systems, with two different Adaptec controllers (AHA-2940AU and AHA-7880), I have had major problems getting the rescue disk to recognize my second scsi drive. I have not had this problem (at all) with the 2.0.6_1998-05-12 distribution disks. At times, I have had to revert to using the 2.0.6_1998-05-12 set, rather than use the newer 2.0.8 set (it's only been recently - and even then, with difficulty [I get timeout errors, if the second drive is recognized at all]) to get both disks to be 'seen' by the installation media. I am using one IBM DCAS-34330W, and one IBM DCAS-34330 (drives a and b in that order). I don't know what the problem is, other than maybe a 'newer and better' aic7xxx driver being used. There are no errors generated when the second drive isn't found; only when it is, and then (sometimes) timeout errors. If anyone has any suggestions about how to 'fix' this, I'd appreciate it if they'd let me know. Thanks, Richard Paynter ([EMAIL PROTECTED]) -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
hamm/contrib/binary-i386/Packages* files
Why are the hamm/contrib/binary-i386/Packages* files empty? There are files in that subtree which are needed to successfully install multiple programs from the main hamm distribution. I have switched to Redhat, and will continue using the Redhat distribution until this situation is rectified. Richard Paynter [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
