Fw: Re: Problems installing amd64 with Supermicro motherboard
Quickly added: I loaded Knoppix 5.3.1 (lenny, kernel 2.6.24.4) networking OK. When loading etch from the HDDD, command startx does not start X (it worked on previous machine). Errors no scree found X10 fatal IO error 104 on X server. I use the GNU driver, no nvidia driver for X. regards francesco Unfortunately I have duties at the moment to investigate deeper this issue. --- On Mon, 4/14/08, Francesco Pietra [EMAIL PROTECTED] wrote: From: Francesco Pietra [EMAIL PROTECTED] Subject: Re: Problems installing amd64 with Supermicro motherboard To: Lennart Sorensen [EMAIL PROTECTED] Cc: Giacomo Mulas [EMAIL PROTECTED], debian-amd64@lists.debian.org, A J Stiles [EMAIL PROTECTED] Date: Monday, April 14, 2008, 11:13 AM Hi reported at the bottom the output of dmesg gsemd --- On Mon, 4/14/08, Lennart Sorensen [EMAIL PROTECTED] wrote: From: Lennart Sorensen [EMAIL PROTECTED] Subject: Re: Problems installing amd64 with Supermicro motherboard To: Francesco Pietra [EMAIL PROTECTED] Cc: Giacomo Mulas [EMAIL PROTECTED], debian-amd64@lists.debian.org, A J Stiles [EMAIL PROTECTED] Date: Monday, April 14, 2008, 8:47 AM On Sat, Apr 12, 2008 at 10:17:03AM -0700, Francesco Pietra wrote: Hi I finally succeeded in entering BIOS (although the Intel Boot Agent is a pest that has still to be eliminated; thanks to ael for suggesting Freedos: not yet tried, Se please my previous answer: no chance to remove the Boot Agent. I first wanted to configure BIOS at least where I am sure what I am doing). In configuring the CPU (4 dual-core amd 875 Rev E1: cache L1 256KB, cache L2 2048KB) it is not clear to me how to set the MTRR mapping. The choice is between continuous (which makes the PCI hole noncacheable) and discrete (which places the PCI hole beloww the 4GB boundary). Oddly, the System Memory is reported 20480MB (which agrees with the result of command $ cat /proc/meminfo when Linux is launched. Actually, I installed aside each socket 2GB + 2GB + 1G + 1G Kingston DDR1 ECC, so I expected a total 24GB. All these memories were OK on a Tyan S2895, and insertion on the Supermicro H8QCE board seems correct. I did myself all the management of the 2GB, and I was carefully grounded. Should the filling of the slots be different? Is all the RAM the same speed? Is it all ECC? Is it all buffered? Like in the case of the CD-ROM, one slot was not well fixed. Now OK. The specs for the board seem to indicate it supports 32GB (16 x 2GB) of buffered 400MHz DDR, or 64GB (16 x 4GB) of buffered 333MHz DDR. What happens if you only install the 2GB modules and leave out the 1GB modules? So out of your 24GB you are only seeing 20GB? As far as I can tell from the manual the way to install the ram would be: CPU3 2GB in 1B 2GB in 1A 1GB in 2A1GB in 2B 1GB in 2B1GB in 2A 2GB in 1A 2GB in 1BCPU4 2GB in 1BCPU1 2GB in 1A 1GB in 2B1GB in 2A 1GB in 2A1GB in 2B 2GB in 1A CPU2 2GB in 1B Ypu are quite correct. In fact this is the order that I set after having edited the BIOS. Changing the position of the memory slots (or because one was badly fixed, has prevented my access to BIOS. It seems inescapable to clear CMOS. To this regard I posed the question to Supermicro Europe; You suggested to clear CMOS by removing the battery and shorting the battery socket. This is considered unsafe by most people. Why not shortening the JBT1 without removing the battery? They have just answered By shorting the battery socket you can be 100% sure the COMS has been cleared Could you post your 'dmesg' output, to see what the e820 tables and mtrr and such show as well as the kernel reserved memory? dmesg dsemd having loaded amd64 from the raid1 disks that were in use in my previous two-socket (dual-core opteron 265) machine. As you can see there is no correct driver for the embedded Gigabit. I have just got the right drived (module) from Supermicro and have to find the right way to load the module fro a diskette or usb key with modprobe (I never loaded a module before) Bootdata ok (command line is root=/dev/md2 ro ) Linux version 2.6.18-3-amd64 (Debian 2.6.18-7) ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)) #1 SMP Mon Dec 4 17:04:37 CET 2006 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000e8000 - 0010 (reserved) BIOS-e820: 0010 - bfff (usable) BIOS-e820: bfff
Re: Fw: Re: Problems installing amd64 with Supermicro motherboard
On Tue, Apr 15, 2008 at 12:46:12AM -0700, Francesco Pietra wrote: Quickly added: I loaded Knoppix 5.3.1 (lenny, kernel 2.6.24.4) networking OK. So the network works with the newer kernel, so it should work with a direct lenny install. When loading etch from the HDDD, command startx does not start X (it worked on previous machine). Errors no scree found X10 fatal IO error 104 on X server. I use the GNU driver, no nvidia driver for X. Ehm, doesn't that supermicro board have an ATI video chip? Try reconfiguring X with dpkg-reconfigure xserver-xorg and let it pick what it thinks is right. If you have an nvidia card added in, then I am pretty sure Etch can't run any 8xxx cards, only 7xxx and lower. You need lenny for 8xxx series cards. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Fw: Re: Problems installing amd64 with Supermicro motherboard
Hi: Grat! Please see below --- On Tue, 4/15/08, Lennart Sorensen [EMAIL PROTECTED] wrote: From: Lennart Sorensen [EMAIL PROTECTED] Subject: Re: Fw: Re: Problems installing amd64 with Supermicro motherboard To: Francesco Pietra [EMAIL PROTECTED] Cc: debian64 debian-amd64@lists.debian.org Date: Tuesday, April 15, 2008, 7:51 AM On Tue, Apr 15, 2008 at 12:46:12AM -0700, Francesco Pietra wrote: Quickly added: I loaded Knoppix 5.3.1 (lenny, kernel 2.6.24.4) networking OK. So the network works with the newer kernel, so it should work with a direct lenny install. When loading etch from the HDDD, command startx does not start X (it worked on previous machine). Errors no scree found X10 fatal IO error 104 on X server. I use the GNU driver, no nvidia driver for X. Ehm, doesn't that supermicro board have an ATI video chip? Try reconfiguring X with dpkg-reconfigure xserver-xorg and let it pick what it thinks is right. Reconfiguring (accepting automatic detection) worked fine indeed. Thanks. (ATI card) Not only. Now dhclient connects to network! At this point I can resume molecular dynamics with the machine. However, inf still wise to change to lenny, where to learn how to carry out correctly a debootstrap? Is it safe to save on another computer /usr/local where amber9 dock6 dms openmpi-1.2.3 nwchem are installed and /opt/intel where the intel compilers for the above programs are installed? Thanks for your precious instructions. Actually, I have acknowledged with thanks your great help in compiling mpqc with libint in a publication F. Pietra Why colchicine does not show mutarotation. With M05-2X density functional in the realm of tricky natural products J. Phys. Org. Chem. 2007, 20, 1102-1107 francesco pietra If you have an nvidia card added in, then I am pretty sure Etch can't run any 8xxx cards, only 7xxx and lower. You need lenny for 8xxx series cards. -- Len Sorensen Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Fw: Re: Problems installing amd64 with Supermicro motherboard
On Tue, Apr 15, 2008 at 09:49:02AM -0700, Francesco Pietra wrote: Reconfiguring (accepting automatic detection) worked fine indeed. Thanks. (ATI card) Not only. Now dhclient connects to network! Odd, not sure how those could be related. At this point I can resume molecular dynamics with the machine. However, inf still wise to change to lenny, where to learn how to carry out correctly a debootstrap? Is it safe to save on another computer /usr/local where amber9 dock6 dms openmpi-1.2.3 nwchem are installed If you have Etch installed, just upgrade normally to Lenny by changing /etc/apt/sources.list from etch or stable to lenny, then do apt-get update and apt-get dist-upgrade. debootstrap often doesn't work reliably except for stable anyhow, so you would essentially have to debootstrap etch, then dist-upgrade that to lenny anyhow. and /opt/intel where the intel compilers for the above programs are installed? Thanks for your precious instructions. Actually, I have acknowledged with thanks your great help in compiling mpqc with libint in a publication F. Pietra Why colchicine does not show mutarotation. With M05-2X density functional in the realm of tricky natural products J. Phys. Org. Chem. 2007, 20, 1102-1107 Neat (not that I can actually read it without buying it I guess). :) -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing amd64 with Supermicro motherboard
On Sat, Apr 12, 2008 at 03:56:58PM -0700, Francesco Pietra wrote: Hi Giacomo: I do have a fast internet connections, though the current installation of amd64 was for a RealTek. On the Supermicro there is an integrated Gigabit, which is not seen by Linux. This also means that I can't scp to the machine and from it, which spoils the possibility offered by running computational programs. Also the CDROM is not seen (by both Linux and BIOS): might it be that the 80-wire ATA 133 cable used is not compatible with the Pioneer DVD-110? No an 80 wire IDE cable should always work. It seems that the needed steps are: 1) Fix the hardware problem of the CDROM Or someone disabled IDE support in the BIOS. Or linux doesn't recognize the IDE controller. 2) Prevent Intel Boot Agent from initializing (which also takes time) There should be a BIOS option to turn of network boot support. 3) Deactivate from BIOS all that is not needed, such as parallel port, COM1/COM2 not to subtract resources. Usually not a bad idea. 4) Reinstall amd64, possibly lenny instead of etch (finally, this is not a server, it is a workstation) On a new board, lenny is much more likely to be successful. To get in to the BIOS, try just holding you hand on lots of keys on the keyboard while the system powers up. Often you can generate a keyboard error, and it will offer you something like F1 to continue, F2 to enter setup. Other keys to enter the BIOS are DEL, INS, F2, F10, F12. Some laptops only let you enter the BIOS after a power off, not a reboot, not sure if any server or desktop systems are like that. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing amd64 with Supermicro motherboard
On Sat, Apr 12, 2008 at 10:17:03AM -0700, Francesco Pietra wrote: Hi I finally succeeded in entering BIOS (although the Intel Boot Agent is a pest that has still to be eliminated; thanks to ael for suggesting Freedos: not yet tried, I first wanted to configure BIOS at least where I am sure what I am doing). In configuring the CPU (4 dual-core amd 875 Rev E1: cache L1 256KB, cache L2 2048KB) it is not clear to me how to set the MTRR mapping. The choice is between continuous (which makes the PCI hole noncacheable) and discrete (which places the PCI hole beloww the 4GB boundary). Oddly, the System Memory is reported 20480MB (which agrees with the result of command $ cat /proc/meminfo when Linux is launched. Actually, I installed aside each socket 2GB + 2GB + 1G + 1G Kingston DDR1 ECC, so I expected a total 24GB. All these memories were OK on a Tyan S2895, and insertion on the Supermicro H8QCE board seems correct. I did myself all the management of the 2GB, and I was carefully grounded. Should the filling of the slots be different? Is all the RAM the same speed? Is it all ECC? Is it all buffered? The specs for the board seem to indicate it supports 32GB (16 x 2GB) of buffered 400MHz DDR, or 64GB (16 x 4GB) of buffered 333MHz DDR. What happens if you only install the 2GB modules and leave out the 1GB modules? So out of your 24GB you are only seeing 20GB? As far as I can tell from the manual the way to install the ram would be: CPU3 2GB in 1B 2GB in 1A 1GB in 2A1GB in 2B 1GB in 2B1GB in 2A 2GB in 1A 2GB in 1BCPU4 2GB in 1BCPU1 2GB in 1A 1GB in 2B1GB in 2A 1GB in 2A1GB in 2B 2GB in 1A CPU2 2GB in 1B Could you post your 'dmesg' output, to see what the e820 tables and mtrr and such show as well as the kernel reserved memory? -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing amd64 with Supermicro motherboard
Hi Sorry for having posted fragmentarily. Some issues (mostly due to my faulty doing) have been fixed. Some are still unresolved (I'll post later about your second kind mail, I have to find the way to take the dmesg output as the scp to my desktop does not work) --- On Mon, 4/14/08, Lennart Sorensen [EMAIL PROTECTED] wrote: From: Lennart Sorensen [EMAIL PROTECTED] Subject: Re: Problems installing amd64 with Supermicro motherboard To: Francesco Pietra [EMAIL PROTECTED] Cc: Giacomo Mulas [EMAIL PROTECTED], debian-amd64@lists.debian.org, A J Stiles [EMAIL PROTECTED] Date: Monday, April 14, 2008, 8:30 AM On Sat, Apr 12, 2008 at 03:56:58PM -0700, Francesco Pietra wrote: Hi Giacomo: I do have a fast internet connections, though the current installation of amd64 was for a RealTek. On the Supermicro there is an integrated Gigabit, which is not seen by Linux. This also means that I can't scp to the machine and from it, which spoils the possibility offered by running computational programs. Also the CDROM is not seen (by both Linux and BIOS): might it be that the 80-wire ATA 133 cable used is not compatible with the Pioneer DVD-110? No an 80 wire IDE cable should always work. It seems that the needed steps are: 1) Fix the hardware problem of the CDROM Or someone disabled IDE support in the BIOS. Or linux doesn't recognize the IDE controller. The cable was not perfectly fixed. Now CD-ROM OK. 2) Prevent Intel Boot Agent from initializing (which also takes time) There should be a BIOS option to turn of network boot support. While I was planning to follow Intel's instructions how to prevent their Boot Agent to initialize, and wondering how my new SPM system can load DOS or FREEDOS, Supermicro Europe has just answered that: Regarding Intel Boot Agent: It is not possible to remove or disable the Intel Boot agent other then disabling onboard LAN via Jumper. This seems to be in contrast with what Intel says at: http://www.intel.com/support/network/adapter/pro100/bootagent/ General Information: To prevent the Boot Agent from executing, enter your systems BIOS configuration and find the boot device order settings. Move the boot agent further down the list, preferably after the hard drive or whatever device you prefer to boot from. The Boot Agent will initialize during the system startup, even if it is not the first boot device. During the time the initialization screen is displayed, you can press Control-S to configure the Boot Agent's internal settings. To prevent the Boot Agent from even initializing, you can turn it off completely. The Intel® Boot Agent can be completely turned off by using the IBAUtil.exe DOS utility found in the PROBOOT archive, using the command line IBAUTIL - FD (flashdisable). Incidentally, there is no option in the AMI BIOS to change the order settings. Because of this, may be Supermicro is correct on saying that the Boot Agent will always appear at my boots. 3) Deactivate from BIOS all that is not needed, such as parallel port, COM1/COM2 not to subtract resources. Usually not a bad idea. Actually I have deactivated parallel port only. I was unsure whether deactivating serial prevents PS/2 or some other basic device from working. 4) Reinstall amd64, possibly lenny instead of etch (finally, this is not a server, it is a workstation) On a new board, lenny is much more likely to be successful. If I succeed in setting the older etch installation on network, I plan to complete the task with a debootstrap to lenny. To get in to the BIOS, try just holding you hand on lots of keys on the keyboard while the system powers up. Often you can generate a keyboard error, and it will offer you something like F1 to continue, F2 to enter setup. Other keys to enter the BIOS are DEL, INS, F2, F10, F12. Some laptops only let you enter the BIOS after a power off, not a reboot, not sure if any server or desktop systems are like that. As it is AMI, the key is DEL. It worked and I carried out few - absolutely safe - modifications to the BIOS settings. Then I rearranged - correctly - the RAM modules with the result that all 24GB are detected and the interleaved (128-bit) memory conditions are satisfied. Oddly, however, the BIOS can no more be accessed, while debian amd64 loads correctly. Thanks francesco pietra -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
Re: Problems installing amd64 with Supermicro motherboard
On Mon, Apr 14, 2008 at 10:23:29AM -0700, Francesco Pietra wrote: Sorry for having posted fragmentarily. Some issues (mostly due to my faulty doing) have been fixed. Some are still unresolved (I'll post later about your second kind mail, I have to find the way to take the dmesg output as the scp to my desktop does not work) Make sure openssh-server is installed on the target machine or scp won't work. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing amd64 with Supermicro motherboard
Hi reported at the bottom the output of dmesg gsemd --- On Mon, 4/14/08, Lennart Sorensen [EMAIL PROTECTED] wrote: From: Lennart Sorensen [EMAIL PROTECTED] Subject: Re: Problems installing amd64 with Supermicro motherboard To: Francesco Pietra [EMAIL PROTECTED] Cc: Giacomo Mulas [EMAIL PROTECTED], debian-amd64@lists.debian.org, A J Stiles [EMAIL PROTECTED] Date: Monday, April 14, 2008, 8:47 AM On Sat, Apr 12, 2008 at 10:17:03AM -0700, Francesco Pietra wrote: Hi I finally succeeded in entering BIOS (although the Intel Boot Agent is a pest that has still to be eliminated; thanks to ael for suggesting Freedos: not yet tried, Se please my previous answer: no chance to remove the Boot Agent. I first wanted to configure BIOS at least where I am sure what I am doing). In configuring the CPU (4 dual-core amd 875 Rev E1: cache L1 256KB, cache L2 2048KB) it is not clear to me how to set the MTRR mapping. The choice is between continuous (which makes the PCI hole noncacheable) and discrete (which places the PCI hole beloww the 4GB boundary). Oddly, the System Memory is reported 20480MB (which agrees with the result of command $ cat /proc/meminfo when Linux is launched. Actually, I installed aside each socket 2GB + 2GB + 1G + 1G Kingston DDR1 ECC, so I expected a total 24GB. All these memories were OK on a Tyan S2895, and insertion on the Supermicro H8QCE board seems correct. I did myself all the management of the 2GB, and I was carefully grounded. Should the filling of the slots be different? Is all the RAM the same speed? Is it all ECC? Is it all buffered? Like in the case of the CD-ROM, one slot was not well fixed. Now OK. The specs for the board seem to indicate it supports 32GB (16 x 2GB) of buffered 400MHz DDR, or 64GB (16 x 4GB) of buffered 333MHz DDR. What happens if you only install the 2GB modules and leave out the 1GB modules? So out of your 24GB you are only seeing 20GB? As far as I can tell from the manual the way to install the ram would be: CPU3 2GB in 1B 2GB in 1A 1GB in 2A1GB in 2B 1GB in 2B1GB in 2A 2GB in 1A 2GB in 1BCPU4 2GB in 1BCPU1 2GB in 1A 1GB in 2B1GB in 2A 1GB in 2A1GB in 2B 2GB in 1A CPU2 2GB in 1B Ypu are quite correct. In fact this is the order that I set after having edited the BIOS. Changing the position of the memory slots (or because one was badly fixed, has prevented my access to BIOS. It seems inescapable to clear CMOS. To this regard I posed the question to Supermicro Europe; You suggested to clear CMOS by removing the battery and shorting the battery socket. This is considered unsafe by most people. Why not shortening the JBT1 without removing the battery? They have just answered By shorting the battery socket you can be 100% sure the COMS has been cleared Could you post your 'dmesg' output, to see what the e820 tables and mtrr and such show as well as the kernel reserved memory? dmesg dsemd having loaded amd64 from the raid1 disks that were in use in my previous two-socket (dual-core opteron 265) machine. As you can see there is no correct driver for the embedded Gigabit. I have just got the right drived (module) from Supermicro and have to find the right way to load the module fro a diskette or usb key with modprobe (I never loaded a module before) Bootdata ok (command line is root=/dev/md2 ro ) Linux version 2.6.18-3-amd64 (Debian 2.6.18-7) ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-20)) #1 SMP Mon Dec 4 17:04:37 CET 2006 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000e8000 - 0010 (reserved) BIOS-e820: 0010 - bfff (usable) BIOS-e820: bfff - bfffe000 (ACPI data) BIOS-e820: bfffe000 - c000 (ACPI NVS) BIOS-e820: fec0 - fec01000 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: ff70 - 0001 (reserved) BIOS-e820: 0001 - 00062000 (usable) DMI 2.3 present. ACPI: RSDP (v000 ACPIAM) @ 0x000fa1b0 ACPI: RSDT (v001 A M I OEMRSDT 0x07000631 MSFT 0x0097) @ 0xbfff ACPI: FADT (v002 A M I OEMFACP 0x07000631 MSFT 0x0097) @ 0xbfff0200 ACPI: MADT (v001 A M I OEMAPIC 0x07000631 MSFT 0x0097) @ 0xbfff0390 ACPI: OEMB (v001 A M I AMI_OEM 0x07000631 MSFT 0x0097) @ 0xbfffe040 ACPI: SRAT (v001 A M I OEMSRAT 0x07000631 MSFT 0x0097) @ 0xbfff5ab0 ACPI: DSDT (v001 1HQC8 1HQC8003 0x0003 INTL
Re: Problems installing amd64 with Supermicro motherboard
--- On Mon, 4/14/08, Lennart Sorensen [EMAIL PROTECTED] wrote: From: Lennart Sorensen [EMAIL PROTECTED] Subject: Re: Problems installing amd64 with Supermicro motherboard To: Francesco Pietra [EMAIL PROTECTED] Cc: Giacomo Mulas [EMAIL PROTECTED], debian-amd64@lists.debian.org, A J Stiles [EMAIL PROTECTED] Date: Monday, April 14, 2008, 10:59 AM On Mon, Apr 14, 2008 at 10:23:29AM -0700, Francesco Pietra wrote: Sorry for having posted fragmentarily. Some issues (mostly due to my faulty doing) have been fixed. Some are still unresolved (I'll post later about your second kind mail, I have to find the way to take the dmesg output as the scp to my desktop does not work) Make sure openssh-server is installed on the target machine or scp won't work. The server is correct. What is lacking if internet connection (se my mail of a few minutes ago) so that things do not pass through the router. Thanks francesco -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing amd64 with Supermicro motherboard
On Mon, Apr 14, 2008 at 11:13:18AM -0700, Francesco Pietra wrote: Hi reported at the bottom the output of So you have the CDROM, and you have all your ram. So what else was wrong with it other than the silly netboot agent making bootup take a while? -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Fw: Re: Problems installing amd64 with Supermicro motherboard
The CD-ROM issue was solved. Now CD-ROM detected. Concerning the aperture memory hole reported below, I forgot to mention: $ dmesg | grep -i memory your BIOS doesn't leave a aperture memory hole. As to network, dmesg reports e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection. As the raid1 is in order, like my applications (Amber Dock NEChem), is it worth while to try recognizing the Gigabit or is it better to reinstall the system? With my previous 2-socket system I had no problems in installing etch with raid1. Ciao francesco --- On Sat, 4/12/08, Francesco Pietra [EMAIL PROTECTED] wrote: From: Francesco Pietra [EMAIL PROTECTED] Subject: Fw: Re: Problems installing amd64 with Supermicro motherboard To: debian64 debian-amd64@lists.debian.org Cc: Giacomo Mulas [EMAIL PROTECTED] Date: Saturday, April 12, 2008, 3:04 PM Additional info related or not to continuous vs discrete and memory problems reported below, from running Debian and commanding # dmesg Checking aperture... CPU 0: aperture too small (32 MB) No AGP bridge found Your BIOS doesn't leave a aperture memory hole Please enable the IOMMU option in the BIOS setup This costs you 64 MB of RAM Mapping aperture over 65536 KB of RAM @ 800 Memory: 20545780k/22020096k available (1929 kernel code, 425288k reserved, 864k data, 176 init). As to peripherals, floppy is detected by both BIOS and dmesg, while cdrom is not detected by $ dmesg $ cat /proc/sys/dev/cdrom/info $ cat /proc/ide/drivers $ cat /proc/scsi/scsi The DVD Pioneer DVR-110 (which was OK on my previous Tyan S2895) was IDE connected through the 80-wire ATA 133 cable furnished with the Supermicro motherboard. Is any jumper setting needed? Thanks francesco --- On Sat, 4/12/08, Francesco Pietra [EMAIL PROTECTED] wrote: From: Francesco Pietra [EMAIL PROTECTED] Subject: Re: Problems installing amd64 with Supermicro motherboard To: Giacomo Mulas [EMAIL PROTECTED] Cc: debian-amd64@lists.debian.org, A J Stiles [EMAIL PROTECTED] Date: Saturday, April 12, 2008, 10:17 AM Hi I finally succeeded in entering BIOS (although the Intel Boot Agent is a pest that has still to be eliminated; thanks to ael for suggesting Freedos: not yet tried, I first wanted to configure BIOS at least where I am sure what I am doing). In configuring the CPU (4 dual-core amd 875 Rev E1: cache L1 256KB, cache L2 2048KB) it is not clear to me how to set the MTRR mapping. The choice is between continuous (which makes the PCI hole noncacheable) and discrete (which places the PCI hole beloww the 4GB boundary). Oddly, the System Memory is reported 20480MB (which agrees with the result of command $ cat /proc/meminfo when Linux is launched. Actually, I installed aside each socket 2GB + 2GB + 1G + 1G Kingston DDR1 ECC, so I expected a total 24GB. All these memories were OK on a Tyan S2895, and insertion on the Supermicro H8QCE board seems correct. I did myself all the management of the 2GB, and I was carefully grounded. Should the filling of the slots be different? Thanks gfrancesco --- On Sat, 4/12/08, Giacomo Mulas [EMAIL PROTECTED] wrote: From: Giacomo Mulas [EMAIL PROTECTED] Subject: Re: Problems installing amd64 with Supermicro motherboard To: Francesco Pietra [EMAIL PROTECTED] Cc: debian-amd64@lists.debian.org, A J Stiles [EMAIL PROTECTED] Date: Saturday, April 12, 2008, 12:20 AM On Fri, 11 Apr 2008, Francesco Pietra wrote: No success in entering BIOS. It seems that the Intel(R) Boot Agent should be eliminated, to get free of their PXE system. Does anyone know how to throw this agent away with Linux? The old amd64 installation is recognized on the new system. Though the original installation was for a dual socket machine, all new 875 CPUs are recognized by $ cat /proc/cpuinfo so that I can expect to be able to clean things with the previous Debian amd64 installation, edit BIOS, and then reinstalling amd64 in order that all new hardware is properly taken into account. What Intel suggests to eliminate their Boot Agent is to download a DOS program (subjected to property restrictions; curiously so because I want to get free of their intruding program, which let me think that individuals are not properly defended by the laws against intruders). DOS is something I am not familiar with and I don't want to get involved in. If not else I can't imagine how to get DOS on my amd64 installation. I am already irritated enough that to submit a letter to the principal journal of chemistry, JACS, one should have to deal with their Visual Basic macros, which require getting involved with Microsoft. I am also irritated by the Supermicro motherboard having a large
Fw: Re: Problems installing amd64 with Supermicro motherboard
The aperture memory hole issue was solved by changing the default AGP present for IOMMU Mode to 64 MB (the option was from 32 MB to 1GB). AGP is not present in this board. However the issue about memory Memory: 20079812k/22544384k available remains. Actually, there are 2 + 2 + 1 GB at each node, so it should be 2400k. I can't imagine if a fresh install of Debian can change the memory detection. francesco --- On Sun, 4/13/08, Francesco Pietra [EMAIL PROTECTED] wrote: From: Francesco Pietra [EMAIL PROTECTED] Subject: Fw: Re: Problems installing amd64 with Supermicro motherboard To: amd64 Debian debian-amd64@lists.debian.org Cc: Giacomo Mulas [EMAIL PROTECTED] Date: Sunday, April 13, 2008, 7:07 AM The CD-ROM issue was solved. Now CD-ROM detected. Concerning the aperture memory hole reported below, I forgot to mention: $ dmesg | grep -i memory your BIOS doesn't leave a aperture memory hole. As to network, dmesg reports e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection. As the raid1 is in order, like my applications (Amber Dock NEChem), is it worth while to try recognizing the Gigabit or is it better to reinstall the system? With my previous 2-socket system I had no problems in installing etch with raid1. Ciao francesco --- On Sat, 4/12/08, Francesco Pietra [EMAIL PROTECTED] wrote: From: Francesco Pietra [EMAIL PROTECTED] Subject: Fw: Re: Problems installing amd64 with Supermicro motherboard To: debian64 debian-amd64@lists.debian.org Cc: Giacomo Mulas [EMAIL PROTECTED] Date: Saturday, April 12, 2008, 3:04 PM Additional info related or not to continuous vs discrete and memory problems reported below, from running Debian and commanding # dmesg Checking aperture... CPU 0: aperture too small (32 MB) No AGP bridge found Your BIOS doesn't leave a aperture memory hole Please enable the IOMMU option in the BIOS setup This costs you 64 MB of RAM Mapping aperture over 65536 KB of RAM @ 800 Memory: 20545780k/22020096k available (1929 kernel code, 425288k reserved, 864k data, 176 init). As to peripherals, floppy is detected by both BIOS and dmesg, while cdrom is not detected by $ dmesg $ cat /proc/sys/dev/cdrom/info $ cat /proc/ide/drivers $ cat /proc/scsi/scsi The DVD Pioneer DVR-110 (which was OK on my previous Tyan S2895) was IDE connected through the 80-wire ATA 133 cable furnished with the Supermicro motherboard. Is any jumper setting needed? Thanks francesco --- On Sat, 4/12/08, Francesco Pietra [EMAIL PROTECTED] wrote: From: Francesco Pietra [EMAIL PROTECTED] Subject: Re: Problems installing amd64 with Supermicro motherboard To: Giacomo Mulas [EMAIL PROTECTED] Cc: debian-amd64@lists.debian.org, A J Stiles [EMAIL PROTECTED] Date: Saturday, April 12, 2008, 10:17 AM Hi I finally succeeded in entering BIOS (although the Intel Boot Agent is a pest that has still to be eliminated; thanks to ael for suggesting Freedos: not yet tried, I first wanted to configure BIOS at least where I am sure what I am doing). In configuring the CPU (4 dual-core amd 875 Rev E1: cache L1 256KB, cache L2 2048KB) it is not clear to me how to set the MTRR mapping. The choice is between continuous (which makes the PCI hole noncacheable) and discrete (which places the PCI hole beloww the 4GB boundary). Oddly, the System Memory is reported 20480MB (which agrees with the result of command $ cat /proc/meminfo when Linux is launched. Actually, I installed aside each socket 2GB + 2GB + 1G + 1G Kingston DDR1 ECC, so I expected a total 24GB. All these memories were OK on a Tyan S2895, and insertion on the Supermicro H8QCE board seems correct. I did myself all the management of the 2GB, and I was carefully grounded. Should the filling of the slots be different? Thanks gfrancesco --- On Sat, 4/12/08, Giacomo Mulas [EMAIL PROTECTED] wrote: From: Giacomo Mulas [EMAIL PROTECTED] Subject: Re: Problems installing amd64 with Supermicro motherboard To: Francesco Pietra [EMAIL PROTECTED] Cc: debian-amd64@lists.debian.org, A J Stiles [EMAIL PROTECTED] Date: Saturday, April 12, 2008, 12:20 AM On Fri, 11 Apr 2008, Francesco Pietra wrote: No success in entering BIOS. It seems that the Intel(R) Boot Agent should be eliminated, to get free of their PXE system. Does anyone know how to throw this agent away with Linux? The old amd64 installation is recognized on the new system. Though the original installation was for a dual socket machine, all new 875 CPUs are recognized by $ cat /proc/cpuinfo so that I can expect to be able to clean things with the previous Debian amd64
Re: Problems installing amd64 with Supermicro motherboard
Hi No success in entering BIOS. It seems that the Intel(R) Boot Agent should be eliminated, to get free of their PXE system. Does anyone know how to throw this agent away with Linux? The old amd64 installation is recognized on the new system. Though the original installation was for a dual socket machine, all new 875 CPUs are recognized by $ cat /proc/cpuinfo so that I can expect to be able to clean things with the previous Debian amd64 installation, edit BIOS, and then reinstalling amd64 in order that all new hardware is properly taken into account. What Intel suggests to eliminate their Boot Agent is to download a DOS program (subjected to property restrictions; curiously so because I want to get free of their intruding program, which let me think that individuals are not properly defended by the laws against intruders). DOS is something I am not familiar with and I don't want to get involved in. If not else I can't imagine how to get DOS on my amd64 installation. I am already irritated enough that to submit a letter to the principal journal of chemistry, JACS, one should have to deal with their Visual Basic macros, which require getting involved with Microsoft. I am also irritated by the Supermicro motherboard having a large portion dedicated to Microsoft to let them do raids, while I can better solve the problem with a software raid. I have now submitted the problem to Supermicro Europe but I expect the same answer I had a couple of years ago from Tyan Europe: We do not answer questions related to Debian Linux, although even then the problem was bnot such related. Thanks for help francesco --- On Fri, 4/11/08, A J Stiles [EMAIL PROTECTED] wrote: From: A J Stiles [EMAIL PROTECTED] Subject: Re: Problems installing amd64 with Supermicro motherboard To: debian-amd64@lists.debian.org Date: Friday, April 11, 2008, 10:00 AM On Friday 11 Apr 2008, Francesco Pietra wrote: The new system launches Debian Linux amd64 etch present on the disks. Before installing Debian amd64 anew, I wanted to configure BIOS. Unable to enter BIOS. What is entered is Intel(R) Boot Agent. Last time I worked on a Supermicro mobo, it was the usual DEL for BIOS setup. On some of the oddball machines I've seen, placing a large, heavy book on the keayboard (so all the typing keys are held down!) sort-of works, either by stopping the POST with a keyboard error or because the right key was held down (along with several wrong ones!) -- AJS delta echo bravo six four at earthshod dot co dot uk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing amd64 with Supermicro motherboard
On Fri, 11 Apr 2008, Francesco Pietra wrote: No success in entering BIOS. It seems that the Intel(R) Boot Agent should be eliminated, to get free of their PXE system. Does anyone know how to throw this agent away with Linux? The old amd64 installation is recognized on the new system. Though the original installation was for a dual socket machine, all new 875 CPUs are recognized by $ cat /proc/cpuinfo so that I can expect to be able to clean things with the previous Debian amd64 installation, edit BIOS, and then reinstalling amd64 in order that all new hardware is properly taken into account. What Intel suggests to eliminate their Boot Agent is to download a DOS program (subjected to property restrictions; curiously so because I want to get free of their intruding program, which let me think that individuals are not properly defended by the laws against intruders). DOS is something I am not familiar with and I don't want to get involved in. If not else I can't imagine how to get DOS on my amd64 installation. I am already irritated enough that to submit a letter to the principal journal of chemistry, JACS, one should have to deal with their Visual Basic macros, which require getting involved with Microsoft. I am also irritated by the Supermicro motherboard having a large portion dedicated to Microsoft to let them do raids, while I can better solve the problem with a software raid. I have now submitted the problem to Supermicro Europe but I expect the same answer I had a couple of years ago from Tyan Europe: We do not answer questions related to Debian Linux, although even then the problem was not such related. Ciao Francesco. A possible way around your problem, even if it will not remove the intel blob, could be the following. Since you can boot in a debian system, you can use it to do a fresh install as well. Use the debootstrap utility (contained in the debootstrap package) to do a fresh install. You just need a working debian system, with a working internet connection, and the target file systems mounted. The only problem is if you want to reinstall on top of your existing (and working) system. In that case, you may do it in two steps: first install just a base system + debootstrap in a small partition (e.g. the old swap partition would do); then reboot in that small partition and use it to clean up the old system and then start a fresh install using debootstrap again. It sounds long, but if you have a fast internet connection it will actually require a handful of minutes. Ciao Giacomo -- _ Giacomo Mulas [EMAIL PROTECTED] _ OSSERVATORIO ASTRONOMICO DI CAGLIARI Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA) Tel. (OAC): +39 070 71180 248 Fax : +39 070 71180 222 Tel. (UNICA): +39 070 675 4916 _ When the storms are raging around you, stay right where you are (Freddy Mercury) _ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing amd64 with Supermicro motherboard
Hi I finally succeeded in entering BIOS (although the Intel Boot Agent is a pest that has still to be eliminated; thanks to ael for suggesting Freedos: not yet tried, I first wanted to configure BIOS at least where I am sure what I am doing). In configuring the CPU (4 dual-core amd 875 Rev E1: cache L1 256KB, cache L2 2048KB) it is not clear to me how to set the MTRR mapping. The choice is between continuous (which makes the PCI hole noncacheable) and discrete (which places the PCI hole beloww the 4GB boundary). Oddly, the System Memory is reported 20480MB (which agrees with the result of command $ cat /proc/meminfo when Linux is launched. Actually, I installed aside each socket 2GB + 2GB + 1G + 1G Kingston DDR1 ECC, so I expected a total 24GB. All these memories were OK on a Tyan S2895, and insertion on the Supermicro H8QCE board seems correct. I did myself all the management of the 2GB, and I was carefully grounded. Should the filling of the slots be different? Thanks gfrancesco --- On Sat, 4/12/08, Giacomo Mulas [EMAIL PROTECTED] wrote: From: Giacomo Mulas [EMAIL PROTECTED] Subject: Re: Problems installing amd64 with Supermicro motherboard To: Francesco Pietra [EMAIL PROTECTED] Cc: debian-amd64@lists.debian.org, A J Stiles [EMAIL PROTECTED] Date: Saturday, April 12, 2008, 12:20 AM On Fri, 11 Apr 2008, Francesco Pietra wrote: No success in entering BIOS. It seems that the Intel(R) Boot Agent should be eliminated, to get free of their PXE system. Does anyone know how to throw this agent away with Linux? The old amd64 installation is recognized on the new system. Though the original installation was for a dual socket machine, all new 875 CPUs are recognized by $ cat /proc/cpuinfo so that I can expect to be able to clean things with the previous Debian amd64 installation, edit BIOS, and then reinstalling amd64 in order that all new hardware is properly taken into account. What Intel suggests to eliminate their Boot Agent is to download a DOS program (subjected to property restrictions; curiously so because I want to get free of their intruding program, which let me think that individuals are not properly defended by the laws against intruders). DOS is something I am not familiar with and I don't want to get involved in. If not else I can't imagine how to get DOS on my amd64 installation. I am already irritated enough that to submit a letter to the principal journal of chemistry, JACS, one should have to deal with their Visual Basic macros, which require getting involved with Microsoft. I am also irritated by the Supermicro motherboard having a large portion dedicated to Microsoft to let them do raids, while I can better solve the problem with a software raid. I have now submitted the problem to Supermicro Europe but I expect the same answer I had a couple of years ago from Tyan Europe: We do not answer questions related to Debian Linux, although even then the problem was not such related. Ciao Francesco. A possible way around your problem, even if it will not remove the intel blob, could be the following. Since you can boot in a debian system, you can use it to do a fresh install as well. Use the debootstrap utility (contained in the debootstrap package) to do a fresh install. You just need a working debian system, with a working internet connection, and the target file systems mounted. The only problem is if you want to reinstall on top of your existing (and working) system. In that case, you may do it in two steps: first install just a base system + debootstrap in a small partition (e.g. the old swap partition would do); then reboot in that small partition and use it to clean up the old system and then start a fresh install using debootstrap again. It sounds long, but if you have a fast internet connection it will actually require a handful of minutes. Ciao Giacomo -- _ Giacomo Mulas [EMAIL PROTECTED] _ OSSERVATORIO ASTRONOMICO DI CAGLIARI Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA) Tel. (OAC): +39 070 71180 248 Fax : +39 070 71180 222 Tel. (UNICA): +39 070 675 4916 _ When the storms are raging around you, stay right where you are (Freddy Mercury) _ __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Fw: Re: Problems installing amd64 with Supermicro motherboard
Additional info related or not to continuous vs discrete and memory problems reported below, from running Debian and commanding # dmesg Checking aperture... CPU 0: aperture too small (32 MB) No AGP bridge found Your BIOS doesn't leave a aperture memory hole Please enable the IOMMU option in the BIOS setup This costs you 64 MB of RAM. Memory: 20545780k/22020096k available (1929 kernel code, 425288k reserved, 864k data, 176 init). As to peripherals, floppy is detected by both BIOS and dmesg, while cdrom is not detected by $ dmesg $ cat /proc/sys/dev/cdrom/info $ cat /proc/ide/drivers $ cat /proc/scsi/scsi The DVD Pioneer DVR-110 (which was OK on my previous Tyan S2895) was IDE connected through the 80-wire ATA 133 cable furnished with the Supermicro motherboard. Is any jumper setting needed? Thanks francesco --- On Sat, 4/12/08, Francesco Pietra [EMAIL PROTECTED] wrote: From: Francesco Pietra [EMAIL PROTECTED] Subject: Re: Problems installing amd64 with Supermicro motherboard To: Giacomo Mulas [EMAIL PROTECTED] Cc: debian-amd64@lists.debian.org, A J Stiles [EMAIL PROTECTED] Date: Saturday, April 12, 2008, 10:17 AM Hi I finally succeeded in entering BIOS (although the Intel Boot Agent is a pest that has still to be eliminated; thanks to ael for suggesting Freedos: not yet tried, I first wanted to configure BIOS at least where I am sure what I am doing). In configuring the CPU (4 dual-core amd 875 Rev E1: cache L1 256KB, cache L2 2048KB) it is not clear to me how to set the MTRR mapping. The choice is between continuous (which makes the PCI hole noncacheable) and discrete (which places the PCI hole beloww the 4GB boundary). Oddly, the System Memory is reported 20480MB (which agrees with the result of command $ cat /proc/meminfo when Linux is launched. Actually, I installed aside each socket 2GB + 2GB + 1G + 1G Kingston DDR1 ECC, so I expected a total 24GB. All these memories were OK on a Tyan S2895, and insertion on the Supermicro H8QCE board seems correct. I did myself all the management of the 2GB, and I was carefully grounded. Should the filling of the slots be different? Thanks gfrancesco --- On Sat, 4/12/08, Giacomo Mulas [EMAIL PROTECTED] wrote: From: Giacomo Mulas [EMAIL PROTECTED] Subject: Re: Problems installing amd64 with Supermicro motherboard To: Francesco Pietra [EMAIL PROTECTED] Cc: debian-amd64@lists.debian.org, A J Stiles [EMAIL PROTECTED] Date: Saturday, April 12, 2008, 12:20 AM On Fri, 11 Apr 2008, Francesco Pietra wrote: No success in entering BIOS. It seems that the Intel(R) Boot Agent should be eliminated, to get free of their PXE system. Does anyone know how to throw this agent away with Linux? The old amd64 installation is recognized on the new system. Though the original installation was for a dual socket machine, all new 875 CPUs are recognized by $ cat /proc/cpuinfo so that I can expect to be able to clean things with the previous Debian amd64 installation, edit BIOS, and then reinstalling amd64 in order that all new hardware is properly taken into account. What Intel suggests to eliminate their Boot Agent is to download a DOS program (subjected to property restrictions; curiously so because I want to get free of their intruding program, which let me think that individuals are not properly defended by the laws against intruders). DOS is something I am not familiar with and I don't want to get involved in. If not else I can't imagine how to get DOS on my amd64 installation. I am already irritated enough that to submit a letter to the principal journal of chemistry, JACS, one should have to deal with their Visual Basic macros, which require getting involved with Microsoft. I am also irritated by the Supermicro motherboard having a large portion dedicated to Microsoft to let them do raids, while I can better solve the problem with a software raid. I have now submitted the problem to Supermicro Europe but I expect the same answer I had a couple of years ago from Tyan Europe: We do not answer questions related to Debian Linux, although even then the problem was not such related. Ciao Francesco. A possible way around your problem, even if it will not remove the intel blob, could be the following. Since you can boot in a debian system, you can use it to do a fresh install as well. Use the debootstrap utility (contained in the debootstrap package) to do a fresh install. You just need a working debian system, with a working internet connection, and the target file systems mounted. The only problem is if you want to reinstall on top of your existing (and working) system. In that case, you may do it in two steps: first install just a base system + debootstrap in a small partition (e.g. the old swap partition would do
Re: Problems installing amd64 with Supermicro motherboard
Hi Giacomo: I do have a fast internet connections, though the current installation of amd64 was for a RealTek. On the Supermicro there is an integrated Gigabit, which is not seen by Linux. This also means that I can't scp to the machine and from it, which spoils the possibility offered by running computational programs. Also the CDROM is not seen (by both Linux and BIOS): might it be that the 80-wire ATA 133 cable used is not compatible with the Pioneer DVD-110? It seems that the needed steps are: 1) Fix the hardware problem of the CDROM 2) Prevent Intel Boot Agent from initializing (which also takes time) 3) Deactivate from BIOS all that is not needed, such as parallel port, COM1/COM2 not to subtract resources. 4) Reinstall amd64, possibly lenny instead of etch (finally, this is not a server, it is a workstation) francesco --- On Sat, 4/12/08, Giacomo Mulas [EMAIL PROTECTED] wrote: From: Giacomo Mulas [EMAIL PROTECTED] Subject: Re: Problems installing amd64 with Supermicro motherboard To: Francesco Pietra [EMAIL PROTECTED] Cc: debian-amd64@lists.debian.org, A J Stiles [EMAIL PROTECTED] Date: Saturday, April 12, 2008, 12:20 AM On Fri, 11 Apr 2008, Francesco Pietra wrote: No success in entering BIOS. It seems that the Intel(R) Boot Agent should be eliminated, to get free of their PXE system. Does anyone know how to throw this agent away with Linux? The old amd64 installation is recognized on the new system. Though the original installation was for a dual socket machine, all new 875 CPUs are recognized by $ cat /proc/cpuinfo so that I can expect to be able to clean things with the previous Debian amd64 installation, edit BIOS, and then reinstalling amd64 in order that all new hardware is properly taken into account. What Intel suggests to eliminate their Boot Agent is to download a DOS program (subjected to property restrictions; curiously so because I want to get free of their intruding program, which let me think that individuals are not properly defended by the laws against intruders). DOS is something I am not familiar with and I don't want to get involved in. If not else I can't imagine how to get DOS on my amd64 installation. I am already irritated enough that to submit a letter to the principal journal of chemistry, JACS, one should have to deal with their Visual Basic macros, which require getting involved with Microsoft. I am also irritated by the Supermicro motherboard having a large portion dedicated to Microsoft to let them do raids, while I can better solve the problem with a software raid. I have now submitted the problem to Supermicro Europe but I expect the same answer I had a couple of years ago from Tyan Europe: We do not answer questions related to Debian Linux, although even then the problem was not such related. Ciao Francesco. A possible way around your problem, even if it will not remove the intel blob, could be the following. Since you can boot in a debian system, you can use it to do a fresh install as well. Use the debootstrap utility (contained in the debootstrap package) to do a fresh install. You just need a working debian system, with a working internet connection, and the target file systems mounted. The only problem is if you want to reinstall on top of your existing (and working) system. In that case, you may do it in two steps: first install just a base system + debootstrap in a small partition (e.g. the old swap partition would do); then reboot in that small partition and use it to clean up the old system and then start a fresh install using debootstrap again. It sounds long, but if you have a fast internet connection it will actually require a handful of minutes. Ciao Giacomo -- _ Giacomo Mulas [EMAIL PROTECTED] _ OSSERVATORIO ASTRONOMICO DI CAGLIARI Str. 54, Loc. Poggio dei Pini * 09012 Capoterra (CA) Tel. (OAC): +39 070 71180 248 Fax : +39 070 71180 222 Tel. (UNICA): +39 070 675 4916 _ When the storms are raging around you, stay right where you are (Freddy Mercury) _ __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problems installing amd64 with Supermicro motherboard
I have assembled a system with a H8QCE quad socket motherboard (amd dual opteron 875), attaching the two SATA HDs from my previous system dual socket on a Tyan S2895 motherboard (dual opteron 265). No additional card was added, i.e., I am using integrated VGA and JLAN (Gigabit Ethernet RJ45). The new system launches Debian Linux amd64 etch present on the disks. Before installing Debian amd64 anew, I wanted to configure BIOS. Unable to enter BIOS. What is entered is Intel(R) Boot Agent. From a search on internet, it seems that Inter Boot Agent is required by motherboards that incorporate a network system (the present one incorporates a Gibabit, see above). I have also seen that Intel Boot Agent can be suppressed using some extra Intel software. Initially my new system was not at the router, than it was attached to the router. Can't say if the Intel Boot agent only appeared when the system was at the router. Well, the hope is that some Debian user have familiarity with such affairs, or that I was grossly unable to find the way to enter BIOS (wath happens at boot goes on so rapidly that there is no time to read. The manual says to enter BIOS with ESC: either ESC or Ctrl + S bring to the Intel Boot Agent. Thanks francesco pietra __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing amd64 with Supermicro motherboard
On Friday 11 Apr 2008, Francesco Pietra wrote: The new system launches Debian Linux amd64 etch present on the disks. Before installing Debian amd64 anew, I wanted to configure BIOS. Unable to enter BIOS. What is entered is Intel(R) Boot Agent. Last time I worked on a Supermicro mobo, it was the usual DEL for BIOS setup. On some of the oddball machines I've seen, placing a large, heavy book on the keayboard (so all the typing keys are held down!) sort-of works, either by stopping the POST with a keyboard error or because the right key was held down (along with several wrong ones!) -- AJS delta echo bravo six four at earthshod dot co dot uk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
