Installation Problem on Sun Fire V240
Hi, I have a Sun Fire V240 with 1GB Ram, i get this msg when i try to boot up with debian installation cd, ok boot cdromBoot device: /[EMAIL PROTECTED],60/[EMAIL PROTECTED]/[EMAIL PROTECTED],0:f File and args:SILO Version 1.4.9\boot:Allocated 8 Megs of memory at 0x4000 for kernelLoaded kernel version 2.4.27Loading initial ramdisk (3041649 bytes at 0x3F80 phys, 0x40C0 virt)...-Remapping the kernel... Fast Instruction Access MMU Missok appreciate your prompt of reply. Thank You. Regards, Lee
Re: tg3 driver fails
On Wed, 6 Jul 2005, David S. Miller wrote: I would like to personally thank the Debian project for making life miserable for it's users and making many platforms totally uninstallable and unusable due to this decision. I am sure every user who can't use Debian on his system out of the box because of this firmware problem will not mind because the high moral standards of the Debian project are much more important than a properly working system. Hi Dave, This decision is indeed unpopular with a lot of people, users and developers alike. I am not too happy with the way things turned out myself. However, I completely disagree with the statement that this situation is a result of some kind of Debian's tantrum, as you present it. In almost all cases the removal of firmware has nothing to do with Debian's "moral standards". In fact, the Debian kernel currently contains a number of firmware files, possibly violating the DFSG. Main reasons why the files are removed are the lack of _any_ license, licenses explicitly forbidding (!) the redistribution, or licenses whose conditions cannot be satisfied (like binary-only firmware licensed as GPL). And redistributing the intellectual property without an explicit permission is a liability Debian can't subject itself or its users to. Perhaps, if the kernel maintainers were a little bit more proactive examining the licenses, this whole mess could have been avoided. In fact, Debian is actively working on resolving this situation. Members of the Debian kernel team have actually made an effort of contacting Broadcom [0] (and other vendors) and clarifying the terms of their licenses. After the response from Broadcom's legal team the updated license, now explicitly permitting the redistribution of tg3 firmware, has been merged upstream [1] and Debian is going to distribute the uncrippled driver again starting with 2.6.12. The status of other communication with vendors may be found at [2]. [0] http://lists.debian.org/debian-kernel/2005/05/msg00203.html [1] http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=49cabf49abd7676d026a61baabf5aae9337a82be;hp=9beb1d587f690d5b2f9087f8f10c0ff9f6b66886 [2] http://wiki.debian.net/?KernelFirmwareLicensing Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
The next generation online pharmacy.
eSecure Online Pharmacies http://ackpeuem.9ou2dsrkojrhva9.spurternj.com The trouble with computers, of course, is that they're very sophisticated idiots. What you are is a question only you can answer. A man who builds his own pedestal had better use strong cement. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Configuring keyboard type5 and sunmouse - kernel 2.6.8-2-sparc64
Team, I have a problem on my new Debian Sparc 3.1r0 instalation using kernel 2.6.8-2-sparc64 on my Ultra10. I can't configure my keyboard type5 and sunmouse on X. They are working fine on console. Does anyone know anything about this ? Thanks a lot. Marcelo Lopes -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.8.10/43 - Release Date: 6/7/2005 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: execution file compiled on x86 on sparc64
Good point. Mmmm, foot. David S. Miller wrote: No. They're totally different architectures. Actually, indirectly you can with something like qemu which does work on Sparc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: info about df -h
What kernel are you running? On Thu, Jul 07, 2005 at 12:18:48AM +0200, gaspo wrote: > i have make this Command for upgrade my Debian...stable > apt-get update > " upgrade after 5 minutS my debian finish the upgrade.. > but when I make > "df -h" > for see the free space on my Disk... i have how reply: > [00:17:51] [EMAIL PROTECTED]:~] $ df -h > FilesystemSize Used Avail Use% Mounted on > /dev/hda1 84T 63T 17T 79% / > > > BEFORE the upgrade > i have > [00:17:51] [EMAIL PROTECTED]:~] $ df -h > FilesystemSize Used Avail Use% Mounted on > /dev/hda1 4GB2gb EC... > the size Was GigaBite > ... > What is the difference? > -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ SwissDisk - http://www.swissdisk.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: execution file compiled on x86 on sparc64
From: Patrick Morris <[EMAIL PROTECTED]> Date: Wed, 06 Jul 2005 15:50:06 -0700 > No. They're totally different architectures. Actually, indirectly you can with something like qemu which does work on Sparc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: execution file compiled on x86 on sparc64
No. They're totally different architectures. gaspo wrote: i want to know somthing about deBiansparc 64... is possible the eXecution of Binary file compiled ON x86 pc? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tg3 driver fails
On 07/06/05 10:22:06PM +0200, Hendrik Sattler wrote: > Am Mittwoch, 6. Juli 2005 22:11 schrieb David S. Miller: > > > However, I agree that all firmware should be removed from the kernel and > > > provided externally (like done with the AVM B1 ISDN cards). > > > However, Debian _must_ tell then, where to find the firmware (means: > > > don't let the user alone with this)! > > > > This doesn't work either. What if the tg3 card is your only > > network access? How might you get that magic firmware file? > > Does initrd or the like work with network boot? How does the card actually do > network boot when not being able to operate without firmware (chicken-egg > problem)? > If the network card cannot handle network boot: why would you want such a > crap? > > > This scheme doesn't work, firmware belongs in the kernel tree > > so that at boot time, regardless of your internet access, you > > can get a working device. > > I could give you various reasons why firmware does _not_ belong into a > compiled driver. A clean interface in driver development and easy firmware > replacement are just two things. > I think he meant packaged with the kernel and not built statically into the kernel binary; although if the firmware is sufficiently separate and the build process just links it in I don't see why that would be a problem either, sort of like how nVidia does their driver. Even barring that, you could easily throw it in an initrd or initramfs image to make it available for early initialization. > > What if I want to use NFS root over the tg3 device? > > See above. > > I find it strange that there are network cards that need a firmware > uploaded :-/ > It's good for ISDN cards as there are many modes to operate in but for an > ethernet card? > > HS > Jim. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Prices You Can Afford - Quality You Can Trust
Identical to the brandname drugs, low prices, international shipping. http://candler.bestmedz4healt.info/?LabradorxtvuySyracusezvtbloodstained The humble suffer when the mighty disagree. Thought is the fountain of speech. If you chase two rabbits, both will escape. Never underestimate your own ignorance. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
info about df -h
i have make this Command for upgrade my Debian...stable apt-get update " upgrade after 5 minutS my debian finish the upgrade.. but when I make "df -h" for see the free space on my Disk... i have how reply: [00:17:51] [EMAIL PROTECTED]:~] $ df -h FilesystemSize Used Avail Use% Mounted on /dev/hda1 84T 63T 17T 79% / BEFORE the upgrade i have [00:17:51] [EMAIL PROTECTED]:~] $ df -h FilesystemSize Used Avail Use% Mounted on /dev/hda1 4GB2gb EC... the size Was GigaBite ... What is the difference?
execution file compiled on x86 on sparc64
i want to know somthing about deBiansparc 64... is possible the eXecution of Binary file compiled ON x86 pc?
Re: tg3 driver fails
From: Hendrik Sattler <[EMAIL PROTECTED]> Date: Wed, 6 Jul 2005 22:22:06 +0200 > Does initrd or the like work with network boot? How does the card > actually do network boot when not being able to operate without > firmware (chicken-egg problem)? If the network card cannot handle > network boot: why would you want such a crap? The openfirmware forth code on the card is executed by the system boot firmware. > It's good for ISDN cards as there are many modes to operate in but for an > ethernet card? It's been happening for a long time. Way back in the Acenic days, the firmware is used to work around a bug in the DMA unit of the card. This is not uncommon. Many current generation cards also do TCP Segmentation Offload in firmware as well. Although gradually most of this stuff is being done in the chip itself, but bugs are harder to fix as a result. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tg3 driver fails
Am Mittwoch, 6. Juli 2005 22:11 schrieb David S. Miller: > > However, I agree that all firmware should be removed from the kernel and > > provided externally (like done with the AVM B1 ISDN cards). > > However, Debian _must_ tell then, where to find the firmware (means: > > don't let the user alone with this)! > > This doesn't work either. What if the tg3 card is your only > network access? How might you get that magic firmware file? Does initrd or the like work with network boot? How does the card actually do network boot when not being able to operate without firmware (chicken-egg problem)? If the network card cannot handle network boot: why would you want such a crap? > This scheme doesn't work, firmware belongs in the kernel tree > so that at boot time, regardless of your internet access, you > can get a working device. I could give you various reasons why firmware does _not_ belong into a compiled driver. A clean interface in driver development and easy firmware replacement are just two things. > What if I want to use NFS root over the tg3 device? See above. I find it strange that there are network cards that need a firmware uploaded :-/ It's good for ISDN cards as there are many modes to operate in but for an ethernet card? HS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: v210 installation
From: Dave Love <[EMAIL PROTECTED]> Date: Wed, 06 Jul 2005 18:02:40 +0100 > It looks about time to give up on this. There are some PCI controller fixes I've made for UltraSPARC-IIIi systems recently in the 2.6.x tree, but since Debian can't even get one-liner device ID changes into the releases in less than 2 months time, I've stopped submitting fixes like that here. I also don't have V210/V240 systems at my disposal, so things are very hard to test, and these two system types seem to be the most problematic UltraSPARC-IIIi platforms to support :-/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tg3 driver fails
From: Hendrik Sattler <[EMAIL PROTECTED]> Date: Wed, 6 Jul 2005 18:25:04 +0200 > They removed that code without actually testing that the driver still works > or > without providing any method to make it working again? Why didn't they remove > the whole driver, then? Because they have commited an entirely irresponsible act by breaking people's systems like this. > However, I agree that all firmware should be removed from the kernel and > provided externally (like done with the AVM B1 ISDN cards). > However, Debian _must_ tell then, where to find the firmware (means: don't > let > the user alone with this)! This doesn't work either. What if the tg3 card is your only network access? How might you get that magic firmware file? This scheme doesn't work, firmware belongs in the kernel tree so that at boot time, regardless of your internet access, you can get a working device. What if I want to use NFS root over the tg3 device? This whole situation is utterly rediculious and does nothing other than hurt users. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tg3 driver fails
From: Jurij Smakov <[EMAIL PROTECTED]> Date: Wed, 6 Jul 2005 11:09:55 -0400 (EDT) > Yes, this is a known problem. The firmware has been removed from the > driver due to unclear licensing information and failure to comply with > DFSG (Debian Free Software Guidelines). I would like to personally thank the Debian project for making life miserable for it's users and making many platforms totally uninstallable and unusable due to this decision. I am sure every user who can't use Debian on his system out of the box because of this firmware problem will not mind because the high moral standards of the Debian project are much more important than a properly working system. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
v210 installation [was Re: tg3 driver fails]
Jurij Smakov <[EMAIL PROTECTED]> writes: > Yes, this is a known problem. Is there any possibility of documenting it, then? I think it would be better to leave the driver out rather than (on a 2.6 kernel) appear to have set it up and leave you wondering what's wrong with the network. > I am afraid that the only feasible solution for Sarge kernels is to > rebuild your kernel (or, at least, the tg3 module) using the > pristine kernel source from kernel.org. If I did that, how would I install it? Anyway, is there any indication it will work in view of the below? Meanwhile, I've found a card with an hme interface and done an install with that. On the reboot after the initial install on a disk with Solaris on for dual boot, it boots Solaris, not silo, which then reports that the disk label is screwed. Starting again with a freshly-partitioned disk, sigh, the reboot fails with VFS: Disk quotas vdquot_6.5.1 Fatal Error Reset CPU ... AFSR 0210.9000.. JETO PRIV OM TO AFAR .0760.2e00.4a00 With either a 2.4 or 2.6 kernel. It looks about time to give up on this. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tg3 driver fails
Am Mittwoch, 6. Juli 2005 17:09 schrieb Jurij Smakov: > Yes, this is a known problem. The firmware has been removed from the > driver due to unclear licensing information and failure to comply with > DFSG (Debian Free Software Guidelines). I am afraid that the only feasible > solution for Sarge kernels is to rebuild your kernel (or, at least, the > tg3 module) using the pristine kernel source from kernel.org. The efforts > to make it work in future installer and kernel versions are under way. They removed that code without actually testing that the driver still works or without providing any method to make it working again? Why didn't they remove the whole driver, then? However, I agree that all firmware should be removed from the kernel and provided externally (like done with the AVM B1 ISDN cards). However, Debian _must_ tell then, where to find the firmware (means: don't let the user alone with this)! HS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tg3 driver fails
On Wed, Jul 06, 2005 at 11:09:55AM -0400, Jurij Smakov wrote: > On Wed, 6 Jul 2005, Dave Love wrote: > > >I got an install going on a v210 by replacing its 1GB memory with > >512MB. However, I can't get the network interfaces working. They > >appear to require the tg3 driver, which fails (see additions to bug > >#315978 for details). Is this a known problem, and is there any way > >round it? > > Hi Dave, > > Yes, this is a known problem. The firmware has been removed from the > driver due to unclear licensing information and failure to comply with > DFSG (Debian Free Software Guidelines). I am afraid that the only feasible > solution for Sarge kernels is to rebuild your kernel (or, at least, the > tg3 module) using the pristine kernel source from kernel.org. The efforts > to make it work in future installer and kernel versions are under way. > > I'll try to have a look whether there is a simple way to produce a > functional driver without rebuilding the entire kernel. Since the firmware loading works, I suspect that simply getting the firmware file and putting it in the right place, will suffice. -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ SwissDisk - http://www.swissdisk.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tg3 driver fails
On Wed, 6 Jul 2005, Dave Love wrote: I got an install going on a v210 by replacing its 1GB memory with 512MB. However, I can't get the network interfaces working. They appear to require the tg3 driver, which fails (see additions to bug #315978 for details). Is this a known problem, and is there any way round it? Hi Dave, Yes, this is a known problem. The firmware has been removed from the driver due to unclear licensing information and failure to comply with DFSG (Debian Free Software Guidelines). I am afraid that the only feasible solution for Sarge kernels is to rebuild your kernel (or, at least, the tg3 module) using the pristine kernel source from kernel.org. The efforts to make it work in future installer and kernel versions are under way. I'll try to have a look whether there is a simple way to produce a functional driver without rebuilding the entire kernel. Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: tg3 driver fails
On Wed, Jul 06, 2005 at 03:24:59PM +0100, Dave Love wrote: > I got an install going on a v210 by replacing its 1GB memory with > 512MB. However, I can't get the network interfaces working. They > appear to require the tg3 driver, which fails (see additions to bug > #315978 for details). Is this a known problem, and is there any way > round it? I suggest recompiling the kernel with this firmware. -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ SwissDisk - http://www.swissdisk.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tg3 driver fails
I got an install going on a v210 by replacing its 1GB memory with 512MB. However, I can't get the network interfaces working. They appear to require the tg3 driver, which fails (see additions to bug #315978 for details). Is this a known problem, and is there any way round it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
