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 <lsorense@csclub.uwaterloo.ca> wrote:
> From: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
> Subject: Re: Problems installing amd64 with Supermicro motherboard
> To: "Francesco Pietra" <chiendarret@yahoo.com>
> Cc: "Giacomo Mulas" <gmulas@ca.astro.it>, debian-amd64@lists.debian.org, "A J Stiles" <deb64@earthshod.co.uk>
> 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
> debian-amd64-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
Reply to: