Re: Headers please, Re: Kernel for woody
David Whedon [EMAIL PROTECTED] wrote:
I suggest you file a bug against kernel-source-2.2.19pre17.
Please don't. Matching kernel-header packages is the responsibility of
the kernel-image builders. Personally, I've started doing them for 2.4,
but at this point I have no plans to do any for 2.2. Please note that I
can only speak for the kernel images that I build.
--
Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmVHI~} [EMAIL PROTECTED]
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Boot problem with Penguin Relion
Hi, My Penguin Relion was running RedHat6.2 when I purchased the system. I upgraded to RedHat7.0 with no problems. I just purchased a Debian2.2_r2 CD set and booted directly off the CD. The boot process hangs after the last line shown here: megaraid:v1.11 (Aug. 23, 2000) megaraid: found 0x101e:0x1960:idx 0:bus 4:slot 0:func 0 scsi2: Found a MegaRAID controller at 0xfc804008, IRQ: 5 Any help or pointers would be appreciated. I can be reached toll-free 1-866-726-3674 if needed. -Kevin L. Gross Randori News Inc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
D-Link DFE-530TX+ rtl8139.o
I have obtained the latest source for rtl8139.c. I have never compiled a
module before and I am getting a number of errors. It appears the source is
relying on a number of files being in the right place and they are not.
It sounds like a lot of people are using the driver that is automatically
installed without problems. It makes me wonder if it is some other problem.
I'm concerned that I could spend a week rewriting the source and makefile to
work on Debian then find out it was some other problem...
Has anyone else run into this problem and if so, did they modify the source
to work with a Debian install? If so would you share it? Am I just being a
whiner, because modifying the source is easy and I just need to look at the
right documentaton?
-Original Message-
From: Jason Gunthorpe [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 19, 2001 6:23 PM
To: David Carlile
Cc: Debian Users List; [EMAIL PROTECTED]
Subject: Re: FW: FW: D-Link DFE-530TX+ via-rhine.o module
On Mon, 19 Mar 2001, David Carlile wrote:
I have been looking through the archive for references to the card and
driver but all I come up with are posts about how easy it is to get this
card running. People actually suggest this card to newbies because it is
so
Dlink changed the configuration of the realtek they were using during
later production runs. The particular card you have does not report itself
as a realtek, so the driver does not find it.
The only fix is to modify the kernel driver. The simplest route is to use
the donald becker drivers (http://www.scyld.com/network/) for the 8139
which has an entry, or you can modify the PCI probe of the linux drivers.
I would expect that the 2.4.2 kernels have this patch applied, but 2.4.0
did not..
It would be very nice if the next drop of the potato boot floopies
included an entry in the realtek driver code for this chip.
The update to the 2.4.0 8139too driver looks like this:
static struct pci_device_id rtl8139_pci_tbl[] __devinitdata = {
{0x10ec, 0x8139, PCI_ANY_ID, PCI_ANY_ID, 0, 0, RTL8139 },
{0x10ec, 0x8138, PCI_ANY_ID, PCI_ANY_ID, 0, 0, RTL8139_CB },
{0x1113, 0x1211, PCI_ANY_ID, PCI_ANY_ID, 0, 0, SMC1211TX },
/* {0x1113, 0x1211, PCI_ANY_ID, PCI_ANY_ID, 0, 0, MPX5030 },*/
{0x1500, 0x1360, PCI_ANY_ID, PCI_ANY_ID, 0, 0, DELTA8139 },
{0x4033, 0x1360, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ADDTRON8139 },
{0x1186, 0x1300, PCI_ANY_ID, PCI_ANY_ID, 0, 0, RTL8139 }, // dlink
{0,}
};
A fix for the 2.2 kernel should be similar in nature, but the table looks
different IIRC.
Jason
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.230 / Virus Database: 111 - Release Date: 1/25/2001
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.230 / Virus Database: 111 - Release Date: 1/25/2001
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: D-Link DFE-530TX+ rtl8139.o
FYI, I just got the driver (and pci-scan.o) to compile for me by reading the instructions at: http://www.scyld.com/network/updates.html You may need to install the appropriate kernel-headers-* package. No need to muck with makefiles. David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies by dwhedon
Repository: boot-floppies who:dwhedon time: Mon Mar 19 23:31:13 PST 2001 Log Message: if a package exists in $local_dir, don't try to download it with apt-get Files: changed:Tag: woody common.sh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
udma66 - ide
The new makefile setup for woody is really nice and clean, unfortunately is becomes less clean if we want to map the kernel-image-2.2.19pre17-ide to the 'udma66' flavour. Possible Solutions: 1. kernel-image-2.2.19pre17 is renamed to kernel-image-2.2.19pre17 - Herbet probably has a reason to call the package ide rather than udma66, and the makefile structure of boot-floppies isn't a very good reason to tell him to change it. 2. udma66 flavor is renamed to ide flavour - This is what I have temporarily done, feels reasonably clean, though it might confuse users. I haven't updated the documentation yet. 3. hack the nice makefiles and/or shell scripts so as to map udma66 to ide - ick. This is possible to do, not all that hard even, but I fear it will cause confusion and undo a lot of good reorganization that has gone on. Anybody care? David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
cvs commit to boot-floppies by dwhedon
Repository: boot-floppies who:dwhedon time: Tue Mar 20 00:05:52 PST 2001 Log Message: i386 uses 2.2.19pre17 now Files: changed:Tag: woody config -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: FW: FW: D-Link DFE-530TX+ via-rhine.o module
On Mon, 19 Mar 2001, David Carlile wrote:
I have been looking through the archive for references to the card and
driver but all I come up with are posts about how easy it is to get this
card running. People actually suggest this card to newbies because it is so
Dlink changed the configuration of the realtek they were using during
later production runs. The particular card you have does not report itself
as a realtek, so the driver does not find it.
The only fix is to modify the kernel driver. The simplest route is to use
the donald becker drivers (http://www.scyld.com/network/) for the 8139
which has an entry, or you can modify the PCI probe of the linux drivers.
I would expect that the 2.4.2 kernels have this patch applied, but 2.4.0
did not..
It would be very nice if the next drop of the potato boot floopies
included an entry in the realtek driver code for this chip.
The update to the 2.4.0 8139too driver looks like this:
static struct pci_device_id rtl8139_pci_tbl[] __devinitdata = {
{0x10ec, 0x8139, PCI_ANY_ID, PCI_ANY_ID, 0, 0, RTL8139 },
{0x10ec, 0x8138, PCI_ANY_ID, PCI_ANY_ID, 0, 0, RTL8139_CB },
{0x1113, 0x1211, PCI_ANY_ID, PCI_ANY_ID, 0, 0, SMC1211TX },
/* {0x1113, 0x1211, PCI_ANY_ID, PCI_ANY_ID, 0, 0, MPX5030 },*/
{0x1500, 0x1360, PCI_ANY_ID, PCI_ANY_ID, 0, 0, DELTA8139 },
{0x4033, 0x1360, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ADDTRON8139 },
{0x1186, 0x1300, PCI_ANY_ID, PCI_ANY_ID, 0, 0, RTL8139 }, // dlink
{0,}
};
A fix for the 2.2 kernel should be similar in nature, but the table looks
different IIRC.
Jason
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
