unsubscribe

unsubscribe

upgrading to 3.1

Hello, I'm trying to upgrade to 3.1 and I'm a bit confused. A compaq, with an alpha chip, isn't booting the CDrom[ iso image] from the srm prompt. It complains about an invalid boot block. I can't seem to find any kernel source code greater than 2.6. Could some one point out what I'm doing wron

re: a NIC card gone bad.

Hi Marty and others, troubleshooting the network *is* part of his job description. I just like to make sure I've done my part. :) I've used a lot of systems over the years. I'm trying to make sure that this variant of linux/unix doesn't require that I do something else to make the NIC usable. re

re: a NIC gone bad

To Marty: Yes, I did trouble shoot. I tried to test the network via PING. Ping reports 100% packet loss, but I'm no longer getting error messages about data bytes and wrong size. The latter happened when we had a Linksys card with the Tulip driver. The network guy, when he's not putting blocks on

re: a NIC gone bad.

I'm running 2.4. Using the alternate intel driver. The becker driver didn't seem to work. Does the behavior I wrote about, seem indicative of a bad driver? If so, I would expect consistent behavior and I'm not getting that. Regards, Marc

replacing a NIC

Hello, We had a 3com NIC go bad and replaced it with and Intel card. I'm noticing odd behavior. The kernel/NIC runs a self-test and says that it's up in 100 Full Duplex mode. [ This is good. ] I try to ping some sites to verify and I get 100% packet loss. I did ping to the broadcast address

Re: problems with a new kernel

Hello, I'm runing linux-2.4.20. I created a kernel specifiying a 3com NIC. I was brought a linksys NIC. *sigh* How do I add the tuilip module to make this NIC work right? Regards, Marc

something odd

I downloaded the software 2.4.20 to build a new kernel on an alpha machine. It compiled and I have a working kernel. Oddly enough, after booting on the new kernel ... uname -a returned 2.2.20. Can anyone think of why this would happen? Also, I'm trying to get iptables to work. Within the dire

problems with a new kernel

Hello, I'm running debian linux on an Alpha machine. I've made a new kernel in order to support iptables. When I try to boot, using the new kernel, I get an error message about aboot not knowing the compression method. I checked in the config file and it's using gzip -9. I've seen this error m

converting old style ufs to ext2

Hello, I've connected a "j-bod" with to an Alpha running the latest stable release of Debian linux. I can mount the filesystems as "ufs" in /etc/fstab, but I can't write to them. In poking around, it seems as if there is no support for writing to UFS filesystems. Q1: is it possible to write to U