Re: onboard ethernet on Tyan Thunder K8WE (s2895)

2006-03-31 Thread Sebastian Haase

David Liontooth wrote:

Sebastian Haase wrote:

Thanks for the replies.
sarge-amd64-2.6.12-netinst.iso did not auto-detect the NICs but after
manually choosing forcedeth it actually worked.
ONLY: that I did get some "timeout" kernel error messages (sorry, 
forgot the exact text)  and it only really worked after I switched the 
network cable between the two ports back and forth many times !!
Good to hear you got it going, but do upgrade your kernel -- the driver 
should work without problems.

How can I know which port is eth0 and which eth1  ?
And - if not - can I at least rely on the order staying the same 
between reboots ?? (I want to connect one port to the internet the 
other to a local (unroutable) private sub-net...
Yes, you can -- as usual in Linux, there are several ways. Check out 
http://www.science.uva.nl/research/air/wiki/LogicalInterfaceNames -- the 
script /share/usr/share/doc/ifupdown/examples/get-mac-address.sh comes 
with the ifupdown package.


Does that mean that the port assignment COULD potentially change after 
each reboot !? And I need a special script to adjust

/etc/network/interfaces !?  Hard to believe...

[[ OK - I just started reading the mentioned wiki web page and here is a 
quote just for documentation purposes:

"""
One of the problems of Linux is that the order of the network interfaces 
is unpredictable. Between reboots it does stay the same, but it is very 
well possible that after an upgrade to a new kernel or the addition or 
replacement of a network card (NIC) that the other of all network 
interface changes. For example, what used to be eth0 now becomes eth1 or 
eth2 or visa versa.

"""
]]




Is "forcedeth" the only possible driver ? Just curious ...

Yes -- and it works great!

Thanks, good to know.

Sebastian Haase


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Error in DMA - Help

2006-03-31 Thread Leopold Palomo Avellaneda
Santiago,

primero decirte que la lista es en ingles. Supongo que entre tanta instalación 
y tanto kernel te habrás despistado ;-)

Has probado a instalar un CD debian-amd64 testing, por ejemplo? Yo la Sarge, 
para una plataforma x64 la veo un poco justita 

Leo

A Divendres 31 Març 2006 05:04, Santiago Yegros va escriure:
> Bueno, tengo un problema al instalar una version nueva del kernel en
> mi Debian Sarge. La cosa es asi: tengo instalado el Debian con el
> kernel por default, el 2.4.x, este kernel no tiene soporte para discos
> SATA, memoria flash(pendrive), PCIexpress, y otras cosas. Bueno,
> entonces quise instalar un kernel mas nuevo, el 2.6.8, bueno el los
> CD's de debian encontre el 2.6 para todas las plataformas entre ellas
> 3 para amd64(mi plataforma), instale los packetes todo bien, y al
> tratar de iniciar con el nuevo kernel me sale este error:
>
> ide: Assuming 33 Mhz system bus speed fot PIO modes, override with
> idebus=xx NFORCE-CK804 : IDE controller at PCI slot :00:06.0
> NFORCE-CK804 : chipset revision 162
> NFORCE-CK804 : not 100% native mode: will prove irqs later
> NFORCE-CK804 : BIOS didn't set cable bits correctry. Enabling Workaround
> NFORCE-CK804 : :00:06.0 (rev a2) UDMA133 controller
>  ide0 : BM-DMA at 0x1000-0x1007, BIOS settings : hda:DMA, hdb:DMA
> NFORCE-CK804 : simplex device : DMA disable (BIOS)
> hda: ST380011A, ATA Disk drive
> ide0: at 0x1f0-0x177, 0x3f6 or irq 14
> hdc: HL-SL-STDVDRRW GWA-4161B, ATAPI CD/DVD-ROM drive
> ide0: at 0x1f0-0x177, 0x376 or irq 15
> hda: max request size: 512KiB
> hda: 156301488 sectors (80026 MB) w/2048 KiB Cache, CHS=16383/255/63,
> UDMA(100) hda: cache flushes supportes
> hda: <4>
> hda: dma_expiry : dma status ==0xff
> hda: dma_expiry : dma status ==0xff
> hda: dma_expiry : dma status ==0xff
> ...y
> sigue.
>
>  Obviamente es un error de DMA, ya entre en mi BIOS 4548541563 veces y
> el DMA esta habilitado, proBe cambiando todos los cable de hd y
> tampoco no pasaba nada.
>
> Bueno, busque informacion por ahi, por foros y demas, y me recomndaron
> recompilar el kernel en mi maquina, entonces, baje el kernel mas
> nuevo, recompile todo bien, instale el kernel, y que paso, el mismo
> error de mier
>
> OBS:
> Lo raro es que puedo instalar el UBUNTU, UBUNTU x64, KNOPPIX sin problema.
> Tambien probe ponerle los kernel's de los cd's de debian en el  ubuntu
> y me sale el mismo error.}
> Tambien hoy acabo de Probar el Nuevo Fedora Core 5, y insertar el DVD
> ya me dale el mismo error
>
> MI PC: es la sgte, si le sirve de algo la informacion:
> Proc AMD athlon 64 2800+
> MB Asus K8N4- Deluxe (chipset nvidia NFORCE 4)
> hd´s 1- SATA 80gb (Guindows)
>   2- Ide 80gb (linux, etc)
> RAM 512mb
> Vga ATI X300 128Mb PCIexprees
> Grabador DVD

-- 
Linux User 152692 
Catalonia


pgp00kuRue3nl.pgp
Description: PGP signature


Re: Upgrading to testing

2006-03-31 Thread Jurriaan Kalkman
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> Run apt-get -s update, then run apt-get -s dist-upgrade
>
> Then if there are no messages about incompatibilities, go ahead and do
> the real thing.
>
> Can someone tell me if this is the right path to take?
>
If you are afraid of breaking things, the correct path should probably
include the concepts 'backup' and 'test backup' somewhere!

Good luck,
Jurriaan



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Upgrading to testing

2006-03-31 Thread Sam Varghese
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

This is my first post to this list.

I am running Sarge at the moment but would like to upgrade to testing. I
have been using the 64-bit version for just two weeks. I have run
testing for about two years on a 32-bit box.

The first time I tried an upgrade, it broke due to Xorg. I couldn't fix
it no matter what I tried so I reinstalled. Now I am dead scared to
upgrade - but I need to do so in order to get my nForce-based sound card 
working as the module for the card is only available in the kernel
images in etch.

Having read some help pages, I think the following will help me check if
things will break again:

Change sources.list to testing

Run apt-get -s update, then run apt-get -s dist-upgrade

Then if there are no messages about incompatibilities, go ahead and do
the real thing.

Can someone tell me if this is the right path to take? 

Thanks,
Sam
- -- 
Sam Varghese
http://www.gnubies.com
My PGP key: http://www.gnubies.com/encryption/sign.txt
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFELQd5ZyXhknb+33gRAj1BAJ9AXjqPnQk7ZnHGrKwyuaLypl5UnQCePuJj
V2sXzfmdyw8K+alA8/KCp1k=
=0sse
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]