Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux    |    Getting to be as bloated as Windows!    |    107,822 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 107,630 of 107,822    |
|    Carlos E.R. to Java Jive    |
|    Re: Strange cabled network fault when re    |
|    15 Nov 25 20:43:33    |
      XPost: uk.comp.os.linux, alt.comp.microsoft.windows, alt.comp.os.windows-11       From: robin_listas@es.invalid              On 2025-11-15 15:39, Java Jive wrote:       > In case it's helpful to anyone else ...       >       > I have some Dell Precision M6800s & M6700s dual-booting via Grub between       > various versions of Windows and Ubuntu 24, all cabled to the LAN. If I       > choose to move between any version of Windows and Ubuntu by rebooting,       > Ubuntu 24 cannot make a reliable cabled LAN connection, it keeps trying       > to connect but never succeeds. However, if I choose to move between any       > version of Windows and Ubuntu by shutting down the PC in between, Ubuntu       > 24 'just works', no networking problem at all. Reboot from U24 and go       > back into U24, the situation is unchanged - if it was working before       > the reboot, it's working now, if it wasn't working before the reboot, it       > isn't working now. Reboot from U24 and go back into Windows, no network       > problems in Windows at all. Reboot from Windows and go back into any       > version of Windows, no network problems at all.       >       > In summary, when rebooting ...       > Ubuntu 24 -> Ubuntu 24 No change       > Ubuntu 24 -> Windows No problem       > Windows -> Ubuntu 24 U24 cannot make cabled LAN connection       > Windows -> Windows No problem       >       > It seems to me from this that the cabled network hardware is not being       > properly initialised when booting Ubuntu 24. The cure is simply to       > actually power down the PC before launching Ubuntu 24              Similar problems have been described long before.               Booting Windows -> Linux, worked.        Booting Linux from scratch, did not work.              The reason was the Linux driver, developed by reverse engineering       probably, did not initialize the network hardware properly, they did not       know something that had to be done.              After they knew this, the developer wrote something else to the driver,       and it worked.              In your case, Windows leaves the eth hardware in a state the Linux       driver can not handle. Open a bug with the Ubuntu people, somehow.              --       Cheers, Carlos.       ES🇪🇸, EU🇪🇺;              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca