driver-modul e100 intel etherexpress 100
by shrek-m＠gmx.de
hi,
are there known problems in severn with the
e100
intel-etherexpress 100 modul
i was trying now for 2 days to bring one of my severn into the lan.
i was not able to do a net-install wih the severn boot-disk,
tested once again with the rhl 9 boot-disk and the e100 on the same
maschine, no problems.
ok,
burning the severn cd #1, minimal english install
the e100 will be recognized and configured by kudzu
but ...
ifconfig = ok
lsmod = ok
modules.conf = ok
net-config = ok
no firewall = ok
# rpm -e iptables lokkit
tcpdump = nothing seems to go out only come in
route = ok ? 169.254.0.0 ??
added
/etc/syscongig/network
NOZEROCONF=1
route = ok
rebooted, 1000 x
network restarted, 100000 x
removed the nic, rebooted, 10 x
add the nic, rebooted, new config, 10 x
always the same
there is a link but nothing goes out
searched the old hdd with, rhl 7.2, rhl 8.0, win98, win2k, netware5
-> no problems, the intel works propper
replaced the intel with an old realtek 10baseT
alias eth0 ne2k-pci
1 minute later, the severn is in the lan :-)
$ ssh user@severn1
-->
$ uname -r
2.4.21-20.1.2024.2.1.nptl
# modinfo ne2k-pci
filename:
/lib/modules/2.4.21-20.1.2024.2.1.nptl/kernel/drivers/net/ne2k-pci.
o
description: "PCI NE2000 clone driver"
author: "Donald Becker / Paul Gortmaker"
license: "GPL"
parm: debug int, description "debug level (1-2)"
parm: options int array (min = 1, max = 8), description "Bit 5:
full dupl
ex"
parm: full_duplex int array (min = 1, max = 8), description "full
duplex
setting(s) (1)
# modinfo e100
filename:
/lib/modules/2.4.21-20.1.2024.2.1.nptl/kernel/drivers/net/e100/e100
.o
description: "Intel(R) PRO/100 Network Driver"
author: "Intel Corporation, <linux.nics(a)intel.com>"
license: "GPL"
parm: TxDescriptors int array (min = 1, max = 16), description
"Number of
transmit descriptors"
parm: RxDescriptors int array (min = 1, max = 16), description
"Number of
receive descriptors"
parm: XsumRX int array (min = 1, max = 16), description "Disable
or enabl
e Receive Checksum offload"
parm: e100_speed_duplex int array (min = 1, max = 16),
description "Speed
and Duplex settings"
parm: ...
--
shrek-m
20 years, 9 months
argh!! burned by buggy pcmcia init script again!
by Robert P. J. Day
i can't believe i've burned by the same buggy pcmcia init script
yet again. you think i'd learn. or something.
quite some time ago, after digging around trying to figure out
why my pcmcia was not starting properly after i'd built a new
2.4 kernel, i tracked the problem down to a weird condition
check in /etc/init.d/pcmcia (which i'd include here, except
pine has just decided to not let me import files. yeah, it's
been that kind of day.)
in a nutshell, if you want to check that file, the script
does two different things depending on the structure of the
/lib/modules directory.
in one case, if at the top level of a build's /lib/modules
directory, there's a .../pcmcia directory, the init script does
one thing. if not, then it checks for another directory,
.../kernel/drivers/pcmcia. depending on what it finds, it
executes some "modprobe" commands in slightly different ways.
check for yourself. (the difference involves whether or not
the module name to modprobe should have the .o suffix or not.)
for the original modules directory, there is *no* top-level
pcmcia/ directory, so the correct set of modprobes is called,
and my modules are loaded, and networking works, yee ha.
but after building a new kernel and modules directory, sure
enough, the "make modules_install" *does* install a top-level
pcmcia/ directory, which causes the wrong (and non-working)
set of modprobe's to be run. damn. damn damn damn. and
that would certainly explain why i had no pcmcia_core or ds
modules loaded. (side note: this new kernel was, in fact,
built with gcc 3.3, so that didn't seem to be a problem).
amazingly, the new /lib/modules directory still had the
lower-level kernel/drivers/pcmcia directory, so all i did was
to remove the top-level pcmcia/ directory to get the old
behaviour back upon reboot.
there's still a small problem with loading the pcmcia
modules, but i'll leave that until the next posting. but what's
the rationale behind this weirdness in /etc/init.d/pcmcia? it
seems *guaranteed* to cause a pcmcia failure if you build and
install a new kernel, because of the structure of the new
/lib/modules directory.
thoughts?
rday
20 years, 9 months
Mysql 4.x
by Max Clark
Hi all,
I was wondering if anyone out there could help me install mysql 4.x on a
redhat 10 beta system.
Are there rpms out there in the wild? What do I need to modify in order to
get the mysql rpm to install correctly?
Thanks in advance,
Max
20 years, 9 months
severn + 2.6.0-test1 kernel -- can't get wireless working
by Robert P. J. Day
the results of more experimentation: so far, i installed severn
on my laptop, then the 2.6.0-test1 kernel straight from www.kernel.org.
that built and booted. on top of that, i built the patched nvidia
driver and got that to work. so far, so good.
(side note: the 2.6.0-test2 kernel in this situation is an
unmitigated disaster. kernel panic every single time, even when
i build it based on the test1 .config file. so i've just given
up on that kernel.)
what's *not* good is that i've completely failed to get my linksys
WCF11 wireless pcmcia card working, and i'm at a complete loss.
as a test, i can reboot to the stock kernel (2.4 variation) that
comes with severn, and wireless comes up nicely (on eth0, via
DHCP from a linksys router here).
when i reboot to 2.6.0-test1, i can verify that the card is
visible with "cardctl ident". the modules hermes, orinoco and
orinoco_cs are loaded. but trying to activate that interface
accomplishes nothing.
the redhat-config-network tool does see the linksys pcmcia card
as the only device on the system, but when i try to configure a
wireless interface, the only choice i get is "other wireless card"
or something like that. (doing this from memory since i have to
reboot back to 2.4 just to get email. argh.)
anyone else got past this point? i'm definitely open to
suggestions.
rday
20 years, 9 months
package whichlist
by Farkas Levente
hi,
I'd like to see the following packages in the next rh release (of course
the latest from everything). these are required for a minimal working
soltion which can comparable with windows clients and servers.
on the client side:
- acrobatreader
- gtkdiff for visual diff
- ntfs driver
- keychain
- flash plugin
- infrared support (automatic recognition), and gprs support through
infrared connection.
on the server side:
- dovecot imap server (AFAIS is already in the beta), we alredy use it in
our production env. with 300 users.
- yum as the most usable and free package updater, we use it for a long time.
- mdadm since on all raid list everybody suggest to forget about raidtool
and use mdadm.
- rdiff-backup (with librsync and rsync compiled to use librsync) for
incretemntal backup.
- openldap
- latest nss_ldap and pam_ldap
- directory_administrator (support for samba 3 schema).
- samba 3 or at least both samba 2.x and 3.x.
- freeswan with x509 (since this is the only vpn solution which has linux
and windows clients). the best would be if rh kernel contains ipsec and we
no longer has to recompile the kernel for freeswan! I'd like to see
freeswan 2.01 with x509 or the best a with super freeswan.
- l2tpd-0.69-7jdl
just my 2c.
20 years, 9 months
BitTorrent not working ?
by Mark Guzzo
BitTorrent (the newest version) in Severn does not seem to work
anymore. I installed wxPythonGTK-py2.3-2.4.1.2-1.i386.rpm and set it up
just like in Shrike but no dice. Anyone else getting this?
20 years, 9 months
unhandled bugs in bugzilla
by Jay Berkenbilt
I'm concerned about bugs whose State in bugzilla remains NEW for a
long time. I'm afraid that these bugs aren't been noticed and my get
overlooked. This has happened to me before, though it happens in a
minority of cases.
Right now, if I go into bugzilla and click on "My Bugs", I have 11
bugs that come up. Of these, 7 have state "NEW". Two of those have
priority "High". I believe that I am very careful not to abuse
priority and severity. I set priority to "High" when the fix is
trivial (low cost, high value) and we're in a period such as this
(beta release before freeze) or when the consequences of the bug are
severe but not severe enough to cause a catastrophic failure. Of the
seven bugs whose status is NEW, only two are very recent, and those
are a few days old. The rest are much older. The oldest has been
"NEW" for almost a year, and I posted to it 5 months ago asking
politely why there hadn't been any activity.
Please understand that I am asking this as an honest question. I
sincerely appreciate the effort that goes into making these releases,
and understand that a lot of people are up to their ears in work. I
mean this message as an expression of concern and request for advice
rather than as a complaint or a nag. For example, could there be a
problem that certain products' default bug owners are no longer there
or are not as responsive as they should be? Could it be that some
people are in the habit of paying attention to their bugs but not
accepting them so that their state turns into ASSIGNED? We use
bugzilla in house for our own bug tracking. I encourage my people to
click on the "My Bugs" link regularly to make sure they haven't missed
anything. We don't have the daily nag messages for stale NEW bugs
enabled, but I bet enabling that would help somewhat. I'd like to
figure out a way of making sure bugs I report don't get ignored
without becoming a pest.
Thanks for any advice.
--
Jay Berkenbilt <ejb(a)ql.org>
http://www.ql.org/q/
20 years, 9 months
RE: Problem with IDE-CDRW drive
by Pavel Rosenboim
> -----Original Message-----
> From: Robert P. J. Day [mailto:rpjday@mindspring.com]
> Sent: Mon, July 28, 2003 1:11 PM
> To: rhl-beta-list(a)redhat.com
> Subject: RE: Problem with IDE-CDRW drive
>
>
> On Mon, 28 Jul 2003, Pavel Rozenboim wrote:
>
> > > -----Original Message-----
> > > From: Igor Gorbounov [mailto:igorbounov@voronezh.serw.ru]
> > > Sent: Mon, July 28, 2003 12:57 PM
> > > To: rhl-beta-list(a)redhat.com
> > > Subject: Problem with IDE-CDRW drive
> > >
> > >
> > > Under RH-9.093 can't use anymore the IDE CD-RW drive.
> > > Under RH-9 it worked fine. And now:
> > >
> > > "mount: wrong fs type, bad option, bad superblock on /dev/cdrom,
> > > or too many mounted file systems
> > > (could this be the IDE device where you in fact use
> > > ide-scsi so that sr0 or sda or so is needed?)"
> > >
> > > /dev/hdc is recognised during Linux startup.
> > > "hdc=ide-scsi" exists in grub.conf.
> > > So what became wrong?
> >
> > Where link /dev/cdrom points to? It should point to something like
> > /dev/scdX. Usually kudzu sets it up automatically.
>
> based on a previous thread, is there any compelling reason to
> use SCSI emulation for an ATAPI CD-RW any more, given that
> cdrecord can handle such devices directly?
>From what I understand, cdrecord code for handling ide devices is still
alpha quality. Also many gui based cd writing software still expects scsi
emulation or needs to be configured to use IDE devices. In fact, the only cd
writing program that recognized IDE CDRW for me was X-CD-Roast - which
somehow depends on dev=ATAPI option for cdrecord, which only works with 2.4
kernels.
>
> rday
>
>
> --
> Rhl-beta-list mailing list
> Rhl-beta-list(a)redhat.com
> http://www.redhat.com/mailman/listinfo/rhl-beta-list
>
20 years, 9 months
