Re: [SLE] Gigabit ethernet on Intel D945GNTLKR mobo

From: Sid Boyce (sboyce_at_blueyonder.co.uk)
Date: 08/12/05

  • Next message: Sid Boyce: "Re: [SLE] Just installed 9.3 and having some problems with video card and monitor -- any ideas?"
    Date: Fri, 12 Aug 2005 19:47:59 +0100
    To: florin@hum.math.cmu.edu
    
    

    florin@hum.math.cmu.edu wrote:
    > On Thu, 11 Aug 2005, Sid Boyce wrote:
    >
    >
    >>>This driver is not mentioned directly on Intel's pages about the
    >>>D945GNT motherboard (they're afraid of Microsoft to say it loud,
    >>>I suppose), but google will eventually dig it out.
    >>>
    >>
    >>In my reply I mentioned I'd seen reference to it on the kernel mailing
    >>list last week, a post from someone at Intel.
    >
    >
    > Sid, I'm sorry I missed your reply. As far as I can tell, it didn't show
    > up on this list. Can you please resend it, or at least send me a copy of
    > it? Thank you.
    >
    I just noticed my reply (sent to you separately) was for the AMD64 list,
    someone else having e1000 problems, so when I saw your post I wondered
    if you had missed mine somehow, just a case of crossed x86/x86_64 wires.
    This the first I've seen a hardware topic collision on separate lists.

    >
    >>>1. It won't boot from a harddrive unless one of the partitions is marked
    >>>as bootable (Windows style) in the partition table. The BIOS (tested the
    >>>newest one - 1788) is quirky alltogether and many of the features are
    >>>twisted or don't work as described in the documentation.
    >>>Why in the world would somebody make the BIOS read the partition table?
    >>>
    >>
    >>I always thought a partition had to be made bootable in order to be able
    >>to boot from it. I've always done that since the days when we used Minix
    >> bootlace and shoelace to boot Linux. You'd also note that on any Linux
    >>install of any flavour, partitioning the drive takes care of that.
    >
    >
    > My point here is that its not the job of the BIOS to read the partition
    > table and decide if a partition is bootable or not. This is the job of the
    > boot loader. There are so many useful things that only the BIOS can do
    > and it doesn't, so why waste EPROM space for stuff like that and impose
    > some stupid un-necesarry (and un-documented) rules.
    >
    > Thank you,
    > Florin
    >
    >
    >
    True. I'll be glad when we can ditch the manufacturer's BIOS entirely,
    it doesn't do much for Linux and it's a pain. I needed to update the
    BIOS on my x86_64 laptop, no floppy, tried freebios which only supports
    a limited set of chipsets, win98-boot.img, freedos, wine and cxoffice
    which all failed to do the job, so I got out a 10G spare drive, bunged
    it in, restored XP (took forever and a good thing I didn't throw the
    CD's in with the weekly rubbish collection), flashed the BIOS, original
    HD in and back with Linux.
    Regards
    Sid.

    -- 
    Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot
    Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support 
    Specialist
    Microsoft Windows Free Zone - Linux used for all Computing Tasks
    -- 
    Check the headers for your unsubscription address
    For additional commands send e-mail to suse-linux-e-help@suse.com
    Also check the archives at http://lists.suse.com
    Please read the FAQs: suse-linux-e-faq@suse.com
    

  • Next message: Sid Boyce: "Re: [SLE] Just installed 9.3 and having some problems with video card and monitor -- any ideas?"

    Relevant Pages

    • Re: [SLE] Yast gets incorrect hard disk size during install
      ... >>format as well as partition the HD. ... Linux wants the BIOS to be in control of the hardware but what almost ... everybody who installs M$ does is answer YES to the question in the BIOS ... the first 256 bytes of the partition. ...
      (SuSE)
    • Re: Big HD-Small BIOS Problem. Need to edit registry in unbootable sy
      ... Linux kernels have their own disk drivers, they don't rely on the BIOS for 48-bit addressing, that is why it can see and use the whole drive but Windows cannot. ... Created large Second primary partition for Windows 2000. ...
      (microsoft.public.win2000.registry)
    • Re: problem with lilo on thinkpad
      ... Lilo was installed to the superblock of the Linux root partition, ... I get a boot-dialog on rebooting and after selecting Linux, ... The partitions before the Linux root on the disk are too large for the ... BIOS to address the LILO code therre. ...
      (comp.os.linux.setup)
    • Re: Dual boot Win XP Pro/FC3 again
      ... does the 1024 cylinder limitation apply to your Linux ... That is a bios limitation if it exists, and with a certain type of bios ... why do you say "second primary partition on slave ...
      (comp.os.linux.setup)
    • Re: problem with lilo on thinkpad
      ... Lilo was installed to the superblock of the Linux root partition, ... sectors of code is to use the BIOS disk drivers, ...
      (comp.os.linux.setup)