bugGNU GRUB - Bugs: bug #1396, Tulip/2114X NIC netboot causes...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #1396: Tulip/2114X NIC netboot causes win2k lockup on boot

Submitter:  Invalid User ID <#11383>
Submitted:  Thu 10 Oct 2002 09:33:55 PM UTC
   
 
Category:  Network Severity:  Major
Priority:  5 - Normal Item Group:  Software Error
Status:  None Privacy:  Public
Assigned to:  None Originator Name: 
Open/Closed:  Closed Release:  None
Release:  0.92 Reproducibility:  Every Time
Planned Release:  None

Sat 15 Dec 2007 11:42:53 AM UTC, comment #1: 

We've moved to GRUB 2 as a development platform.  Unfortunately, GRUB 2 doesn't have network support yet, although there's ongoing work to implement it.  If you want to help on that, please contact <grub-devel@gnu.org>.

In the meantime, this bug doesn't apply.  I'm closing it.

Robert Millan <robertmh>
Group administrator
Thu 10 Oct 2002 09:33:55 PM UTC, original submission:  

Set up grub with --enable-tulip; loaded boot sector for win2k over tftp and chainbooted to it. As windows loads, it locks up as it tries to initialize its devices (progress bar about half way). Reproduced on different machines and slightly different NIC revisions. My guess is that the crappy windows driver is expecting the NIC to be in power-up state, but since grub has used the NIC, it confuses the windows driver and locks. Problem was resolved when I used a different chipset NIC. Perhaps reset the NIC or PCI bus or something just before booting to make sure the cards are in a power-up-like state that an OS or driver might expect?

Invalid User ID <#11383>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by robertmh (Posted a comment)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2007-12-15 robertmh Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-4b48.
    Corresponding source code