I can't get the boot process to get as far as running uname -a dmesg, so
I can't give you precise details of the build nor hardware found.
I have tried to recompile the 6.10 kernel with the
CONFIG_8139TOO_OLD_RX_RESET setting, but it still hangs looking for a
valid file system. This might be a nother issue with my kernel build
(built on a VMWare virtual PC) but I haven't had to much chance to
experiment.
I am more than happy to help with the testing of this new release as I
am reduced to running VMWare from Windows or struggling with FreeBSD
(which does boot).
Cheers
John
ChuckShort wrote:
> By the looks of it (research etc), its the 8139too module that is
> hanging the ethdetect. What happens if we enable
> CONFIG_8139TOO_OLD_RX_RESET?
>
> chuck
>
> ** Changed in: linux-source-2.6.20 (Ubuntu)
> Assignee: Cristian Aravena Romero => ChuckShort
>
>
Sorry I haven't got back to you.
I can't get the boot process to get as far as running uname -a dmesg, so
I can't give you precise details of the build nor hardware found.
I have tried to recompile the 6.10 kernel with the 8139TOO_ OLD_RX_ RESET setting, but it still hangs looking for a
CONFIG_
valid file system. This might be a nother issue with my kernel build
(built on a VMWare virtual PC) but I haven't had to much chance to
experiment.
I am more than happy to help with the testing of this new release as I
am reduced to running VMWare from Windows or struggling with FreeBSD
(which does boot).
Cheers
John
ChuckShort wrote: 8139TOO_ OLD_RX_ RESET?
> By the looks of it (research etc), its the 8139too module that is
> hanging the ethdetect. What happens if we enable
> CONFIG_
>
> chuck
>
> ** Changed in: linux-source-2.6.20 (Ubuntu)
> Assignee: Cristian Aravena Romero => ChuckShort
>
>