Re: Tulip chip Netgear card
Robert Waldner wrote: On Tue, 13 Nov 2001 18:37:22 PST, [EMAIL PROTECTED] writes: These are *not* new NICs, I've had them for a few years now. I am nearly certain that they are 310s. As I said, both will run on SuSE 6.3 using the standard tulip.c driver. I just need to know what to do to get them to work with Debian 2.2Rev4 Potato. They are already working fine with the 2.2.13 version of Linux (and were working as far back as 2.0.38, again using the standard tulip driver.) Have you tried the old_tulip-driver? I remember having to do something to that effect when switching from 2.0.x to 2.2.x-kernels. Aha! That's it. Robert, you were one of the people to suggest this. My new Debian boxen is now talking to both its gateway, and the Internet beyond. Simple as pie. If I had only known about old_tulip at the beginning... Indeed. The 310TX card by Netgear has the PNIC chip (on my card the chip is marked PNIC LC82C168). This card requires the module named old_tulip. Since I have a half duplex hub, I pass the parameter options=13 to set the module to MII 100baseTx. This works perfectly and avoids the periodic notification that the card is switching to half-duplex. A complete set of parameter documentation is on the Tulip driver page: http://www.scyld.com/network/tulip.html By the way, I like these cards. I've used them on all my old Linux boxen. They are fast a trouble free (once one has the proper driver). Thanks to one and all. Regards, Arne [EMAIL PROTECTED]
ARRGH!!! Tulip card again
HELP! This is driving me absolutely positively mad. I have a Netgear F? 310TX network card, which is a PNIC 82c168 (tulip clone). I *cannot* get this card to run reliably on the latest Debian stable (2.2.Rev4). I have used both the tulip.o and the old_tulip.o drivers. The old_tulip.o module worked last night, but not this morning. In between I installed some additional software, none of which had anything to do with the kernel or kernel modules. I configure the driver with options=13 which sets the card's mode to MII 100BaseTx. This is what was working last night. When I ping my gateway today, I get: eth0: Transmit error, Tx status 7fffc002. eth0: The transmitter stopped! CSR5 is 206803a, CSR6 816ec002. eth0: Transmit error, Tx status 7fffc000. eth0: The transmitter stopped! CSR5 is 206801a, CSR6 816ec002. eth0: Transmit error, Tx status 7fffc002. eth0: The transmitter stopped! CSR5 is 206803a, CSR6 816ec002. eth0: LC82C168 negotiated capability , CSR5 02660010. eth0: LC82C168 MII PHY status , Link partner report , csr6 816ec000/816ee002. If I let the module autoprobe, I get eth0: Changing PNIC configuration to half-duplex, CSR6 0186. eth0: Changing PNIC configuration to half-duplex, CSR6 0042. eth0: Changing PNIC configuration to half-duplex, CSR6 01868000. eth0: Changing PNIC configuration to half-duplex, CSR6 00428000. eth0: Changing PNIC configuration to half-duplex, CSR6 01868000. eth0: Changing PNIC configuration to half-duplex, CSR6 00428000. eth0: Changing PNIC configuration to half-duplex, CSR6 01868000. eth0: Changing PNIC configuration to half-duplex, CSR6 00428000. eth0: Changing PNIC configuration to half-duplex, CSR6 01868000. ... This is a common network card. I've had absolutely no problems with these cards with other Linux installations. Somebody who knows this driver, please help me. Thank you. Arne Flones flonesaw at longship dot net
Re: Way Confused about Version Numbers
Rafe, It's simple. 2.2Rev4 is the version number of the Debian distribution itself. And, since it is 2.2something, that makes it Potato. (As it says on the Debian site, each release has a code name from the movie, Toy Story.) Each of the four thousand-odd software packages which make up a Debian release has its own version number. In particular, the Linux kernel is a package. So are the Gnu Tools from the Free Software Foundation. These both form the core of Debian Gnu-Linux. When one specifies which Linux kernel is used with Debian, one has to reference a Linux kernel version number, e.g., 2.2.19. One could easily substitute another kernel version for the standard one. As long as all the other major components will work with the new kernel everything is usually okay. It's generally always okay (and very easy) to compile from source code. I hope this helps. Regards Arne flonesaw at longship dot net Gad, I'm real confused. I can roughly grok the difference between stable, unstable, etc. But what's this business of 2.2r3 and 2.2r4? How does this relate to the version number 2.2.18pre21. Where does potato leave off and woody begin? What's with the 2.4.x kernels? Where do they stand in relation to potato and woody? Is there a FAQ or URL that might help to understand any of this? Thanks! rafe b.
Tulip chip Netgear card
Hi, I'm fairly new to Debian, but not new to Linux. In particular, I know about configuring almost everything, but not much about the Debian way of doing things. I have a pair of Netgear FX-310TX NICs. (I'm uncertain of the precise model number; neither card has a model stenciled on the card.) The cards came in one of those networking kits; the price was right so I bought it. The card is a PCI card running the PNIC chip (marked LC82C169), which is a Tulip compatible. On a brand spanking new Debian 2.2Rev4 install, this card refuses to function. I get the following from the tulip module. * Device or resource busy. Hint: this error can be caused by incorrect module parameters including invalid IO or IRQ parameters I tested the card in another machine (SuSE 6.3 - 2.2.13 - using that installation's tulip driver with no options). It works flawlessly. I even switched the two cards. Still no go. The cards are good. Apparently my installation isn't. This is undoubtedly a silly thing. What am I doing wrong? Any suggestions? Thanks, Arne Flones [EMAIL PROTECTED]
Re: Tulip chip Netgear card
These are *not* new NICs, I've had them for a few years now. I am nearly certain that they are 310s. As I said, both will run on SuSE 6.3 using the standard tulip.c driver. I just need to know what to do to get them to work with Debian 2.2Rev4 Potato. They are already working fine with the 2.2.13 version of Linux (and were working as far back as 2.0.38, again using the standard tulip driver.) Switching them out is not an option. There's nothing wrong with the cards. But I'm dead in the water until I get them working in Debian. Tom Allison wrote: Interestingly enough I just talked to someone this morning who was using these netgear 310's and had trouble with a new NIC, it turns out that it was a 311. The difference being that the card when from several physical IC packages to one larger one. That and it didn't work with the debian distro he was using (2.2r2). He switched it out with an older 310 and was able to continue. Maybe this is relevant, maybe not. But if it is... If you can get the raw tulip driver for this newer card, the compile the source and load it in during the installation. As some point you will be prompted if you have any special drivers to load from a custom floppy. It is here you bring out the new tulip driver and have at it. From there, I suspect you will want to upgrade to a really new kernel that carries the new tulip.o file and carry on from there. At least that is what I would try... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, I'm fairly new to Debian, but not new to Linux. In particular, I know about configuring almost everything, but not much about the Debian way of doing things. I have a pair of Netgear FX-310TX NICs. (I'm uncertain of the precise model number; neither card has a model stenciled on the card.) The cards came in one of those networking kits; the price was right so I bought it. The card is a PCI card running the PNIC chip (marked LC82C169), which is a Tulip compatible.
2.2r3 CD Images
I've got rsynch revved up, ready to go. Will official Debian CD Images for the new 2.2R3 release be announced? Regards, Arne Flones
Re: ALSA sound modules not loading
Marshal, There is a Seg fault problem with the ALSA drivers. I have a Creative Ensoniq PCI64 (ens1371) soundcard and the ALSA drivers do the same thing to me. This is on a S.u.S.E. system with kernel 2.2.5. What I do is to put the modprobe command in a script in my /root/bin directory and run it manually until the driver catches and doesn't segfault. Then, everything works fine. Since I almost never reboot my machine, this works well for me. I have reported this to the ALSA people. They responded that it was a S.u.S.E. problem. Apparently it isn't. I would recommend you go to the ALSA site and report it yourself. Regards, Arne I'm using the latest potato right now. The ALSA source compiled fine. I used make-kpkg to install the modules. But for some reason the module won't start. Every time I run /etc/init.d/alsa start, I get the following. Starting sound driver: snd-card-interwave /etc/init.d/alsa: line 10: 7070 Segmentation fault /sbin/modprobe $line /dev/nul l 21 failed. To get this, I had to edit the file /etc/init.d/alsa to awk /etc/modules.conf as opposed to conf.modules, since the new potato has finally removed the old style conf.modules. a lsmod right after gives: Module Size Used by snd-cs4231 16876 0 (unused) snd-mixer 24768 0 [snd-cs4231] snd-pcm1 16604 0 [snd-cs4231] snd-timer 7772 0 [snd-cs4231 snd-pcm1] snd-midi 12524 0 (unused) snd-pcm 8844 0 [snd-cs4231 snd-pcm1] snd33612 0 [snd-cs4231 snd-mixer snd-pcm1 snd-timer snd-midi snd-pcm] soundcore 2340 0 [snd] ppp20012 0 (unused) slhc4280 0 [ppp] ne2k-pci4040 1 83906068 0 [ne2k-pci] parport_pc 5700 1 (autoclean) lp 5092 0 parport 7048 1 [parport_pc lp] vfat8956 0 (unused) fat28768 0 [vfat] I can manually modprobe snd-card-interwave and it gives me no error, so I have no idea what's going on. Any help would be appreciated. Thanks. Marshal -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: Printer suggestion
Manuel, I have an HP 540 and an HP 310, both of which just work out of the box with all of my Linux systems. However, all HP printers use the same control language, called PCL level 3. This means that any HP Inkjet will work with Linux as long as it isn't one of the Windows-only versions. This means that you should make sure that the printer specifications state that it will work on MS-DOS. If it works with MS-DOS, it will work with Linux. Getting any standard HP printer working is easy with apsfilter, which is the driver I personally prefer. Just select the HP printer which is closest to the model you have and everything should be just fine. These printers also work well with magicfilter. Once either one of these is configured, you should be able to print without hassles. The reason why I suggested the HP 970cxi was that it should work with Linux out of the box and that it has the nice feature of being able to automatically print on both sides of the paper. The price is also very good. If you have technical questions about this, I suggest that you contact HP. [EMAIL PROTECTED] wrote: Manuel, Hewlett-Packard, but avoid the Winprinters HP's *are* indeed very rugged. Plus, they have the advantage of replacing the print head every time you put in new ink. This alone makes the HP head-over-heals better than any of the other inkjets. If you have ever priced the cost of replacing a print head on a non-HP, you'd know what I'm talking about. They don't last forever. With HP, you don't have to worry about that. Best value for my money would be the HP 970cxi. It's 12 ppm in BW fast draft mode. It can do two-sided printing (!!!) and street prices are under $350. I don't know of any other inexpensive printer that will automatically print on both sides of the paper. That sells this one to me. First of all, apologies for writing directly to you. I am writing because I asked through the list about configuration issues of the HP 970cxi (magicfilter version, ghostscript version, lpd version, Debian version...) in a Debian linux box but I got no answer. From your mail I understand that you have this HP printer model working in your linux box. Could you please tell me if this is correct? In that case, could you please tell me which are the characteristics of your box? Please, reply to the debian-user-list because I know there are more people interested in this information. Thank you very much, Manuel Arenaz
Re: Creating/Moving a partition
David J. Kanter wrote: I'd like to make a new partition for /var because I don't have enough drive space where /var is currently mounted (/) to run apt-get dist-upgrade. What's the best way of doing this? I can create a new /var partition becaus e I've got plenty of available drive space, but what set-up files will I have to modify to make sure things go smoothly? I assume I'll have to change fstab. But then do I have to move all contents of the current /var to the new /var? Could I create the new partition using a temporary name, move all the /var stuff to it, then rename it to /var? Thats what I would suggest. Stop everything you can, copy the contents and do the final swapover in one line, just in case # mv /var /old_var ; mv /new_var /var NO, NO, NO, NO, NO Do *NOT* use mv. This will change the ownership and protection rights of the contents. This will most certainly break something. Instead, use cp -a to preserve everything. 1. Log in as root 2. Go to run level 1 (kills networking). Also kill all user processes. init 1 3. Add the following to your /etc/fstab /dev/??? /var ext2defaults1 2 (The ??? is the partition of your new /var) 4. Change the name of your old /var directory and make a new empty one. mv /var /oldvar mkdir /var chmod 755 /var 5. Mount your new var partition. mount /dev/??? /var 6. Now, use cp -a (or cp -av if you want to watch it) to copy your files, permissions and ownership to the new partition. cp -av /var/* /var If things don't work, you still have your old partition in pristine shape to go back to where you were. I wouldn't delete the old /var until I determined that everything works fine--maybe a week. The idea of just getting a bigger root partition is a bad idea. /var is a very, very good candidate for a separate partition.
Re: Creating/Moving a partition
I wrote: 6. Now, use cp -a (or cp -av if you want to watch it) to copy your files, permissions and ownership to the new partition. cp -av /var/* /var PS That command should be: cp -av /oldvar/* /var
Re: Enlightenment .16 segafaults.
Without having tried anything on my own system, I would suggest that you remove the .enlightenment directory in your home directory and try to load it again. It is very likely that an old configuration file is incompatible with the new version. This has happened in previous E releases. Please let us all know if this fixes the problem. Regards, Arne I have downloaded Enlightenment 0.16 .debs from www.debian.org/~ljlane. Well, when I start E... it gives me an indicator in terms of percentage. When it hits 91%... it segfaults. Anybody has a fix for this? regards, = == Andre M. Varon - Technical Head = = == Lasaltech, Inc. - http://andre.lasaltech.com = === = = = = If I cannot bend Heaven, I shall move Hell. = = -- Publius Vergilius Maro (Virgil) -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev /null
