Menu
▾
▴
devil-linux-discuss — General Mailing List for all discussions
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(59) |
Sep
(57) |
Oct
(5) |
Nov
(45) |
Dec
(21) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(13) |
Feb
(22) |
Mar
(14) |
Apr
(7) |
May
(33) |
Jun
(57) |
Jul
(25) |
Aug
(40) |
Sep
(53) |
Oct
(58) |
Nov
(75) |
Dec
(22) |
| 2003 |
Jan
(101) |
Feb
(101) |
Mar
(103) |
Apr
(125) |
May
(85) |
Jun
(57) |
Jul
(62) |
Aug
(42) |
Sep
(76) |
Oct
(214) |
Nov
(290) |
Dec
(274) |
| 2004 |
Jan
(187) |
Feb
(172) |
Mar
(313) |
Apr
(209) |
May
(169) |
Jun
(147) |
Jul
(118) |
Aug
(193) |
Sep
(227) |
Oct
(125) |
Nov
(246) |
Dec
(191) |
| 2005 |
Jan
(244) |
Feb
(175) |
Mar
(165) |
Apr
(130) |
May
(217) |
Jun
(122) |
Jul
(188) |
Aug
(235) |
Sep
(165) |
Oct
(133) |
Nov
(209) |
Dec
(88) |
| 2006 |
Jan
(66) |
Feb
(89) |
Mar
(108) |
Apr
(91) |
May
(29) |
Jun
(45) |
Jul
(64) |
Aug
(42) |
Sep
(44) |
Oct
(81) |
Nov
(64) |
Dec
(9) |
| 2007 |
Jan
(24) |
Feb
(122) |
Mar
(55) |
Apr
(50) |
May
(84) |
Jun
(13) |
Jul
(80) |
Aug
(70) |
Sep
(78) |
Oct
(45) |
Nov
(56) |
Dec
(42) |
| 2008 |
Jan
(65) |
Feb
(3) |
Mar
(51) |
Apr
(151) |
May
(54) |
Jun
(72) |
Jul
(73) |
Aug
(47) |
Sep
(55) |
Oct
(123) |
Nov
(16) |
Dec
(4) |
| 2009 |
Jan
(23) |
Feb
(39) |
Mar
(27) |
Apr
(36) |
May
(35) |
Jun
(51) |
Jul
(11) |
Aug
(14) |
Sep
(40) |
Oct
(67) |
Nov
(38) |
Dec
(13) |
| 2010 |
Jan
(15) |
Feb
(35) |
Mar
(40) |
Apr
(11) |
May
(26) |
Jun
(10) |
Jul
(5) |
Aug
(50) |
Sep
(86) |
Oct
(67) |
Nov
(36) |
Dec
(11) |
| 2011 |
Jan
(50) |
Feb
(6) |
Mar
(13) |
Apr
(13) |
May
(29) |
Jun
(27) |
Jul
(26) |
Aug
(27) |
Sep
(21) |
Oct
(7) |
Nov
(27) |
Dec
(4) |
| 2012 |
Jan
(11) |
Feb
(20) |
Mar
(48) |
Apr
(18) |
May
(8) |
Jun
(19) |
Jul
|
Aug
(15) |
Sep
(3) |
Oct
(4) |
Nov
(5) |
Dec
(1) |
| 2013 |
Jan
(13) |
Feb
(7) |
Mar
(4) |
Apr
(25) |
May
(2) |
Jun
(8) |
Jul
(4) |
Aug
(8) |
Sep
(7) |
Oct
|
Nov
(5) |
Dec
(10) |
| 2014 |
Jan
|
Feb
|
Mar
(6) |
Apr
(20) |
May
(5) |
Jun
|
Jul
(2) |
Aug
|
Sep
(8) |
Oct
(21) |
Nov
(4) |
Dec
(7) |
| 2015 |
Jan
(10) |
Feb
(9) |
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(5) |
Sep
(11) |
Oct
|
Nov
(17) |
Dec
(32) |
| 2016 |
Jan
(10) |
Feb
(15) |
Mar
(4) |
Apr
(7) |
May
(10) |
Jun
(11) |
Jul
(15) |
Aug
(26) |
Sep
(13) |
Oct
(10) |
Nov
(16) |
Dec
(6) |
| 2017 |
Jan
(9) |
Feb
(3) |
Mar
|
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
(3) |
Sep
(3) |
Oct
(6) |
Nov
(8) |
Dec
|
| 2018 |
Jan
(12) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Dietmar R. <die...@gm...> - 2007-09-03 17:21:43
|
2007/8/28, Dietmar Rieder <die...@gm...>: > Am 28.08.07 schrieb "Rudner, Bj=F6rn" <br...@ba...>: > > Hi Didi, > > > > I've updated shorewall to Version 4.0.2 in DL 1.2.x and DL 1.3.x > > Thank you so much BTW 4.0.3 is out :-) Shorewall-perl now requires the FindBin Perl module Didi |
|
From: Dietmar R. <die...@gm...> - 2007-09-03 17:19:11
|
2007/8/31, Heiko Zuerker <he...@zu...>: > > On Fri, August 31, 2007 06:23, Dietmar Rieder wrote: > > 2007/8/23, Oliver Niesner <dig...@gm...>: > > > >> Hi, Heiko! > >> > >> > >> No good news from the new testing release - it crashed after the > >> bootmenu on my PIII 500 intel 440BX board with an "unable to handle > >> kernel paging request at virtual address d0000000" error and hangs. My > >> own iso crashed with the same error - it seems that the new kernel > >> doesn't like older hardware. On an slightly more modern PC (P4) it > >> starts like normal. > > > > The same happens here. After loading the initrd it crashes on my PIII > > 1000 (were it should finally run on). > > On a P4 or on my vmware it works. I build an iso for 486 and one for > > 686 but it doesn't make a difference... > > Can you swap out the memory on your PIII for a test? > If you tell me how to do that, I'll try... Didi |
|
From: Heiko Z. <he...@zu...> - 2007-09-03 13:51:47
|
On Mon, September 3, 2007 08:46, Martin Hotze wrote: > I'd put the energy in a DL w/Kernel 2.6 ... but this is only me. Quite a few people are currently working on it (DL 1.3 that is), including me. I'm sure things will be progressing faster once summer is over and people get bored. ;-) I will like to release a new 1.2 version in the next couple of weeks but we need to make a decision on this issue first. -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Martin H. <ma...@ho...> - 2007-09-03 13:47:42
|
I'd put the energy in a DL w/Kernel 2.6 ... but this is only me. martin > -----Original Message----- > From: dev...@li... [mailto:devil- > lin...@li...] On Behalf Of Heiko Zuerker > Sent: Monday, September 03, 2007 2:56 PM > To: dev...@li... > Subject: Re: [Devil-Linux-discuss] IPTables NAT module broken in DL 1.2 ? >=20 > Hey guys, >=20 > I got the feeling that we won't get a newer release of the pptp-conntrack > patch for kernel 2.4. >=20 > Should we just remove it? > Or does anyone here have the skill to fix the old pptp-conntrack patch? >=20 > Heiko >=20 > On Sun, September 2, 2007 16:53, Stefan Engel wrote: > > (...) |
|
From: Heiko Z. <he...@zu...> - 2007-09-03 13:30:27
|
Hey guys, I got the feeling that we won't get a newer release of the pptp-conntrack patch for kernel 2.4. Should we just remove it? Or does anyone here have the skill to fix the old pptp-conntrack patch? Heiko On Sun, September 2, 2007 16:53, Stefan Engel wrote: > Hi, > > > the problem is located in the pptp-conntrack-nat support code. Somewhere > on the mailing list are some other mails regarding this problem. Until a > new version of this patch can be found it is going to break nat support. > > If you don't need pptp-conntrack-nat support then go to > built/scripts/config and edit the file patch-o-matic.exclude. Locate a line > with > > #extra/pptp-conntrack-nat > > > in it and remove the leading '#' to tell the patch-o-matic build script to > ignore pptp-conntrack-nat support during build. > > At least this fixed the nat support for me ;-) > > > Regards, > Stefan > > > Jasper Siepkes wrote: > >> Hi everybody, >> >> >> I'm new to Devil Linux; I checkout and compiled a fresh 1.2 release. >> The >> only thing I modified was adding the new MPT fusion drivers, otherwise >> none of the SAS controllers in HP Proliants work. >> >> After that I installed devil linux on a USB stick and booted it. It >> works like a charm, except for iptables. When I try a simple NAT command >> like: 'iptables -t nat -A POSTROUTING -o eth0 -s 192.168.0.0/24 -j >> MASQUERADE' I get the dreaded 'iptables: Invalid argument' error. Which >> suggests the module is out of sync with the userland utils. However, >> since I compiled the whole thing from scrath, I dont see how this is >> possible. >> >> The iptable_nat module is loaded and other iptable rules work, for as >> far as I can tell its only the NAT table that misbehaves. >> >> Can anybody confirm this behavior ? Or am I just royally screwing >> up ? :-) >> >> Kind regards, >> >> >> Jasper >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > > -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Jasper S. <ja...@si...> - 2007-09-02 22:04:16
|
I will try it first thing tomorrow morning, sleeping time for now :-) Thanks for the info! Kind regards, Jasper -----Original Message----- From: dev...@li... [mailto:dev...@li...] On Behalf Of Stefan Engel Sent: zondag 2 september 2007 23:54 To: dev...@li... Subject: Re: [Devil-Linux-discuss] IPTables NAT module broken in DL 1.2 ? Hi, the problem is located in the pptp-conntrack-nat support code. Somewhere on the mailing list are some other mails regarding this problem. Until a new version of this patch can be found it is going to break nat support. If you don't need pptp-conntrack-nat support then go to built/scripts/config and edit the file patch-o-matic.exclude. Locate a line with #extra/pptp-conntrack-nat in it and remove the leading '#' to tell the patch-o-matic build script to ignore pptp-conntrack-nat support during build. At least this fixed the nat support for me ;-) Regards, Stefan Jasper Siepkes wrote: > Hi everybody, > > I'm new to Devil Linux; I checkout and compiled a fresh 1.2 release. The > only thing I modified was adding the new MPT fusion drivers, otherwise > none of the SAS controllers in HP Proliants work. > > After that I installed devil linux on a USB stick and booted it. It > works like a charm, except for iptables. When I try a simple NAT command > like: 'iptables -t nat -A POSTROUTING -o eth0 -s 192.168.0.0/24 -j > MASQUERADE' I get the dreaded 'iptables: Invalid argument' error. Which > suggests the module is out of sync with the userland utils. However, > since I compiled the whole thing from scrath, I dont see how this is > possible. > > The iptable_nat module is loaded and other iptable rules work, for as > far as I can tell its only the NAT table that misbehaves. > > Can anybody confirm this behavior ? Or am I just royally screwing > up ? :-) > > Kind regards, > > Jasper ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Devil-linux-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
|
From: Stefan E. <ste...@av...> - 2007-09-02 21:54:04
|
Hi, the problem is located in the pptp-conntrack-nat support code. Somewhere on the mailing list are some other mails regarding this problem. Until a new version of this patch can be found it is going to break nat support. If you don't need pptp-conntrack-nat support then go to built/scripts/config and edit the file patch-o-matic.exclude. Locate a line with #extra/pptp-conntrack-nat in it and remove the leading '#' to tell the patch-o-matic build script to ignore pptp-conntrack-nat support during build. At least this fixed the nat support for me ;-) Regards, Stefan Jasper Siepkes wrote: > Hi everybody, > > I'm new to Devil Linux; I checkout and compiled a fresh 1.2 release. The > only thing I modified was adding the new MPT fusion drivers, otherwise > none of the SAS controllers in HP Proliants work. > > After that I installed devil linux on a USB stick and booted it. It > works like a charm, except for iptables. When I try a simple NAT command > like: 'iptables -t nat -A POSTROUTING -o eth0 -s 192.168.0.0/24 -j > MASQUERADE' I get the dreaded 'iptables: Invalid argument' error. Which > suggests the module is out of sync with the userland utils. However, > since I compiled the whole thing from scrath, I dont see how this is > possible. > > The iptable_nat module is loaded and other iptable rules work, for as > far as I can tell its only the NAT table that misbehaves. > > Can anybody confirm this behavior ? Or am I just royally screwing > up ? :-) > > Kind regards, > > Jasper |
|
From: Jasper S. <ja...@si...> - 2007-09-02 21:26:01
|
Hi everybody, I'm new to Devil Linux; I checkout and compiled a fresh 1.2 release. The only thing I modified was adding the new MPT fusion drivers, otherwise none of the SAS controllers in HP Proliants work. After that I installed devil linux on a USB stick and booted it. It works like a charm, except for iptables. When I try a simple NAT command like: 'iptables -t nat -A POSTROUTING -o eth0 -s 192.168.0.0/24 -j MASQUERADE' I get the dreaded 'iptables: Invalid argument' error. Which suggests the module is out of sync with the userland utils. However, since I compiled the whole thing from scrath, I dont see how this is possible. The iptable_nat module is loaded and other iptable rules work, for as far as I can tell its only the NAT table that misbehaves. Can anybody confirm this behavior ? Or am I just royally screwing up ? :-) Kind regards, Jasper |
|
From: Heiko Z. <he...@zu...> - 2007-08-31 12:15:48
|
On Fri, August 31, 2007 06:23, Dietmar Rieder wrote: > 2007/8/23, Oliver Niesner <dig...@gm...>: > >> Hi, Heiko! >> >> >> No good news from the new testing release - it crashed after the >> bootmenu on my PIII 500 intel 440BX board with an "unable to handle >> kernel paging request at virtual address d0000000" error and hangs. My >> own iso crashed with the same error - it seems that the new kernel >> doesn't like older hardware. On an slightly more modern PC (P4) it >> starts like normal. > > The same happens here. After loading the initrd it crashes on my PIII > 1000 (were it should finally run on). > On a P4 or on my vmware it works. I build an iso for 486 and one for > 686 but it doesn't make a difference... Can you swap out the memory on your PIII for a test? -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: Dietmar R. <die...@gm...> - 2007-08-31 11:24:05
|
2007/8/23, Oliver Niesner <dig...@gm...>: > Hi, Heiko! > > No good news from the new testing release - it crashed after the > bootmenu on my PIII 500 intel 440BX board with an > "unable to handle kernel paging request at virtual address d0000000" > error and hangs. > My own iso crashed with the same error - it seems that the new kernel > doesn't like older hardware. On an slightly more modern PC (P4) it > starts like normal. The same happens here. After loading the initrd it crashes on my PIII 1000 (were it should finally run on). On a P4 or on my vmware it works. I build an iso for 486 and one for 686 but it doesn't make a difference... Didi |
|
From: Dietmar R. <die...@gm...> - 2007-08-28 14:33:28
|
Am 28.08.07 schrieb "Rudner, Bj=F6rn" <br...@ba...>: > Hi Didi, > > I've updated shorewall to Version 4.0.2 in DL 1.2.x and DL 1.3.x Thank you so much Didi |
|
From: <br...@ba...> - 2007-08-28 13:43:18
|
Hi Didi, I've updated shorewall to Version 4.0.2 in DL 1.2.x and DL 1.3.x Greets, Bj=F6rn -----Urspr=FCngliche Nachricht----- Von: dev...@li... = [mailto:dev...@li...] Im Auftrag = von "Rudner, Bj=F6rn" Gesendet: Donnerstag, 23. August 2007 15:39 An: dev...@li... Betreff: Re: [Devil-Linux-discuss] shorewall updates Hi, I will check to use the updated packages. Greets, Bj=F6rn -----Urspr=FCngliche Nachricht----- Von: dev...@li... = [mailto:dev...@li...] Im Auftrag = von Dietmar Rieder Gesendet: Donnerstag, 23. August 2007 12:17 An: dev...@li... Betreff: [Devil-Linux-discuss] shorewall updates Could you please consider to update the shorewall package to 3.4.6 or 4.0.2 including the errata? Thanks Didi _________________________________________________________________________= ___ baulogis GmbH Zamdorfer Str. 100 81677 M=FCnchen / Munich Deutschland / Germany www.baulogis.com Gesch=E4ftsf=FChrer / Managing Director: Thomas Bachmaier HRB 133832, Amtsgericht M=FCnchen Ust-ID: DE 212 020 193 Der Inhalt dieser E-Mail ist vertraulich und ausschlie=DFlich f=FCr den = bezeichneten Adressaten (dev...@li...) = bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen = Vertreter sein sollten, so beachten Sie bitte, dass jede Form der Kenntnisnahme, = Ver=F6ffentlichung,=20 Vervielf=E4ltigung oder Wiedergabe des Inhalts dieser E-Mail = unzul=E4ssig ist. Bitte setzen Sie sich in diesem Fall mit dem Absender der E-Mail in = Verbindung (br...@ba...). |
|
From: Vincent <vt1...@ho...> - 2007-08-28 09:43:55
|
Hi, dear all:
Does DL 1.2.14 support a D-Link DGE-530T card? I try sk98lin =
module is fail.
Does anybody to try success?
vt167098 |
|
From: Martin T. <mar...@gm...> - 2007-08-27 01:40:18
|
Yes, I know how to bring up the interface with an fixed IP address etc... Finally I got the eth0 up, and want to post it here for possible future readers with the same problem: The reference to the manual of ifconfig wasn't so bad. Reading this made me try "ifconfig eth0 up". This gave me the error message "SIOCSIFFLAGS: Device or resource busy". I gave this message to google and came on [http://www.fedoraforum.org/forum/showthread.php?t=21264]. So I tried this, and eth0 came up on the next reboot. In other words: The setting in my (ugly) AMI-BIOS below PCI/PnP called "Plug and Play Aware O/S: no" made my eth0 busy and not working under Linux. I just turned it to "yes" and eth0 (my PCI-NIC) came up and running. [to run with Windows it has to be in "no" mode] Btw: The pppoe-start is still not working, but that's another problem and maybe should not be discussed here... Thanks to all who tried to help me. -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer |
|
From: Ashwin M. <ash...@ya...> - 2007-08-24 17:55:21
|
Martin Teufel wrote:
> Of course it does!
> Every PCI-NIC I tried was recognized correctly.
That's not the matter...
>
>
Hope you know how to bring up the interface with an
fixed IP address or
use use dhcp to obtain an ip address for the interface
eth0.
You can also configure devil-linux with the IP
parameters to do the job
automatically too.
However, I have strong feeling reading the manual i.e.
"man ifconfig"
will surely help.
Further beyond this point continuing this thread would
be technically an
OT on this list.
You can definitely check some NET Howto's or email me
off the list.
with Regards,
ASHWIN
____________________________________________________________________________________
Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more.
http://mobile.yahoo.com/go?refer=1GNXIC
|
|
From: Martin T. <mar...@gm...> - 2007-08-23 23:42:42
|
Of course it does!
Every PCI-NIC I tried was recognized correctly. That's not the matter...
-------------
lspci:
[...]
00:08.0 SCSI storage controller: Adaptec AHA-7850 (rev 01)
00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
00:0a.0 VGA compatible controller: Cirrus Logic GD 5446
[...]
lspci -v:
[...]
00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
Subsystem: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
Flags: medium devsel
I/O ports at 1400 [size=32]
Expansion ROM at <unassigned> [disabled] [size=32K]
[...]
setup -> NIC:
Listing all known PCI Ethernet cards:
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS) (rev 0).
--
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
|
|
From: Oliver N. <dig...@gm...> - 2007-08-23 20:51:35
|
Hi, Heiko! No good news from the new testing release - it crashed after the bootmenu on my PIII 500 intel 440BX board with an "unable to handle kernel paging request at virtual address d0000000" error and hangs. My own iso crashed with the same error - it seems that the new kernel doesn't like older hardware. On an slightly more modern PC (P4) it starts like normal. I switched back to 2.4.34.4 which worked on my hardware, after all that trouble with cdrtools and NAT i hope that i have a working iso tomorrow. Oliver |
|
From: Heiko Z. <he...@zu...> - 2007-08-23 15:12:51
|
Hey everyone, I just uploaded a new testing release for 1.2.14 ftp://ftp.devil-linux.org/pub/devel/testing Would be great if some of you could test the latest updates. Thx -- Regards Heiko Zuerker http://www.devil-linux.org |
|
From: <br...@ba...> - 2007-08-23 13:39:36
|
Hi, I will check to use the updated packages. Greets, Bj=F6rn -----Urspr=FCngliche Nachricht----- Von: dev...@li... = [mailto:dev...@li...] Im Auftrag = von Dietmar Rieder Gesendet: Donnerstag, 23. August 2007 12:17 An: dev...@li... Betreff: [Devil-Linux-discuss] shorewall updates Could you please consider to update the shorewall package to 3.4.6 or 4.0.2 including the errata? Thanks Didi -------------------------------------------------------------------------= This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ = _______________________________________________ Devil-linux-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss _________________________________________________________________________= ___ baulogis GmbH Zamdorfer Str. 100 81677 M=FCnchen / Munich Deutschland / Germany www.baulogis.com Gesch=E4ftsf=FChrer / Managing Director: Thomas Bachmaier HRB 133832, Amtsgericht M=FCnchen Ust-ID: DE 212 020 193 Der Inhalt dieser E-Mail ist vertraulich und ausschlie=DFlich f=FCr den = bezeichneten Adressaten (dev...@li...) = bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser E-Mail oder dessen = Vertreter sein sollten, so beachten Sie bitte, dass jede Form der Kenntnisnahme, = Ver=F6ffentlichung,=20 Vervielf=E4ltigung oder Wiedergabe des Inhalts dieser E-Mail = unzul=E4ssig ist. Bitte setzen Sie sich in diesem Fall mit dem Absender der E-Mail in = Verbindung (br...@ba...). |
|
From: Dietmar R. <die...@gm...> - 2007-08-23 10:17:11
|
Could you please consider to update the shorewall package to 3.4.6 or 4.0.2 including the errata? Thanks Didi |
|
From: Ashwin M. <ash...@ya...> - 2007-08-23 08:07:51
|
Martin Teufel wrote:
> Btw: Meanwhile I tried a third NIC (a RTL8029AS),
and (what a wonder) it is exactly the same fault...
What does "lspci" or "lspci -v" says ? Does it
recognize the presence of
the card ?
with Regards,
ASHWIN
____________________________________________________________________________________
Need a vacation? Get great deals
to amazing places on Yahoo! Travel.
http://travel.yahoo.com/
|
|
From: Martin T. <mar...@gm...> - 2007-08-23 07:40:57
|
Sorry, now I realized what you want to know. Of course I (or better: Devil-Linux / the ne2k-pci module) loaded all dependencies, including 8390 and crc32, but they are not used, just as the ne2k-pci module itself. It is loading it, no comments, no errors (as you can see below). ------------- root@Devil:~ # modprobe 8390 root@Devil:~ # root@Devil:~ # modprobe ne2k-pci root@Devil:~ # root@Devil:~ # modprobe -d 8390 ============================================= Module crc32 kname crc32 objkey crc32 names: crc32 mode: NORMAL Module matching crc32: /lib/modules/2.4.34-grsec/kernel/lib/crc32.o ============================================= ============================================= Module 8390 kname 8390 objkey 8390 names: 8390 mode: NORMAL Module matching 8390: /lib/modules/2.4.34-grsec/kernel/drivers/net/8390.o ============================================= root@Devil:~ # root@Devil:~ # modprobe -d ne2k-pci ============================================= Module crc32 kname crc32 objkey crc32 names: crc32 mode: NORMAL Module matching crc32: /lib/modules/2.4.34-grsec/kernel/lib/crc32.o ============================================= ============================================= Module 8390 kname 8390 objkey 8390 names: 8390 mode: NORMAL Module matching 8390: /lib/modules/2.4.34-grsec/kernel/drivers/net/8390.o ============================================= ============================================= Module ne2k-pci kname ne2k-pci objkey ne2k-pci names: ne2k-pci mode: NORMAL Module matching ne2k-pci: /lib/modules/2.4.34-grsec/kernel/drivers/net/ne2k-pci.o ============================================= root@Devil:~ # Listing all loaded modules: [...] ne2k-pci 4608 0 8390 6288 0 [ne2k-pci] crc32 2896 0 [8390] [...] ------------- Btw: Meanwhile I tried a third NIC (a RTL8029AS), and (what a wonder) it is exactly the same fault... -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kanns mit allen: http://www.gmx.net/de/go/multimessenger |
|
From: Ashwin M. <ash...@ya...> - 2007-08-23 04:23:56
|
Martin Teufel wrote: > Hello, > > I don't have a utitity floppy disk supplied with the system/NIC to boot from, but I checked out the IO and IRQ under Win98, and tried to give them Devil-Linux resp. the ne2k-pci as options, but nothing had changed. > Then I tried some random (high) IRQs like 7, 8, 9, 10, 11, 12 and after that (undo that) I tried to load the module with autoprobe parameters check. It changed nothing... > > [...] > > Btw.: Thanks for the URL: > http://tldp.org/HOWTO/Module-HOWTO/individual.html > It helped a bit and is a good summary. Just wanted to check if you loaded the module 8390 by the command "modprobe 8390" before trying to load the ne module. Maybe if you read the sections 15.4.15 and 15.4.16 it may help. First load the 8390 module and check if that loads at all. with Regards, ASHWIN ____________________________________________________________________________________ Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545433 |
|
From: Martin T. <mar...@gm...> - 2007-08-23 03:42:05
|
Hello,
I don't have a utitity floppy disk supplied with the system/NIC to boot from, but I checked out the IO and IRQ under Win98, and tried to give them Devil-Linux resp. the ne2k-pci as options, but nothing had changed.
Then I tried some random (high) IRQs like 7, 8, 9, 10, 11, 12 and after that (undo that) I tried to load the module with autoprobe parameters check. It changed nothing...
As I had no further ideas, I changed the NIC and built in a 3Com 3C905b-TX (PCI) (instead of the Compex RL2000A) and loaded (as I read to be the suitable driver) the 3c59x module.
But: It's just the same!
Module loaded, but not used...
---------------
Listing all loaded modules:
Module Size Used by Not tainted
ppp_synctty 5544 0 (unused)
ppp_async 6976 0 (unused)
ppp_generic 23176 0 [ppp_synctty ppp_async]
slhc 4736 0 [ppp_generic]
p80211 18500 0 (unused)
ipv6 175956 -1
3c509 10324 1
3c59x 27216 0
lvm-mod 60608 0 (autoclean)
md 58400 0 (autoclean)
libata 38648 0 (unused)
loop 48688 0
eth0 Link encap:Ethernet HWaddr 00:50:04:65:55:4E
BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Base address:0x1400
---------------
I just don't understand that...
If it would be Windows (;-)), I would suppose that the NIC is disabled.
And while I looked in some .config files to search for the cause of the fault, I found something strange (not directly in a file):
modprobe --showconfig:
[...]
alias char-major-200 vxspec
alias char-major-206 osst
alias char-major-216 rfcomm
alias dos msdos
alias dummy0 dummy
alias dummy1 dummy
alias eth0 off
alias iso9660 isofs
alias md-personality-1 linear
alias md-personality-2 raid0
alias md-personality-3 raid1
alias md-personality-4 raid5
alias md-personality-7 multipath
[...]
Why "alias eth0 off"?? Where does this come from? Could that be the fault?
I'm confused... (and not a Linux-expert)
Is there anybody who understands what is going on at my Devil-Linux?
Btw.: Thanks for the URL:
http://tldp.org/HOWTO/Module-HOWTO/individual.html
It helped a bit and is a good summary.
If it can be helpful, I could place my etc.tar.bz2 on a server, if someone is interested in looking through it.
Thanks for any further suggestions.
--
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
|
|
From: Stefan E. <ste...@av...> - 2007-08-22 18:30:14
|
Hi, the problem seems to be that cdrtools were internally switched to use libsiconv in one of the latest releases (according to the release notes). make build and make install succeeded, but if you take a look at the generated log files (tmp/LOG/build/cdrtools) then you will see that ld cannot find some symbols for linking mkisofs. Strange that the cdrtools makefile silently ignores these errors and proceeds as if nothing has happened instead of propagating this error to the build script. Stefan Heiko Zuerker wrote: > Hey, > > I will replace the file with the a27 version. > > Heiko > > On Wed, August 22, 2007 09:48, Dietmar Rieder wrote: >> 2007/8/22, Oliver Niesner <dig...@gm...>: >> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> >>> Heiko Zuerker schrieb: >>> >>>> Not sure what the problem is, but if you don't want to wait for me >>>> try updating cdrtools. Remove the old one from tmp/ and unpack the new >>>> one in there. >>>> >>>> Then do a: >>>> rm tmp/.done_*_cdrtools rm tmp/.done_iso* make build install iso >>> Did you upgrade the cdrtools package in cvs? >>> If not i have to say that rebuilding/installing cdrtools doesn't solve >>> the problem - at least on my buildmachine :-/ >> It doesn't help here either. The latest version does not compile >> there is a warning text in cdrtools-2.01.01a34 (AN-2.01.01a34): >> >> NEW features of cdrtools-2.01.01a34: >> >> >> ---------> >> ******** WARNING! This is a release that introduces _massive_ changes >> ******** in mkisofs. These changes are not yet and cannot yet be complete >> ******** and are definitely not tested sufficiently already. >> ******** If you like to test the recent massive mkisofs enhencements, you >> ******** are welcome! If you lik a "stable" version, use mkisofs from >> ******** Cdrtools-2.01.01a27 >> <-------- >> >> >> ....so I tried cdrtools-2.01.01a27 which finally worked. >> >> >> Didi >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Devil-linux-discuss mailing list >> Dev...@li... >> https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
50 messages has been excluded from this view by a project administrator.
