Re: 2.4.3 SMP: nfs stale handle, fb dualhead hardlock, G400/450 misnaming
Elmer Joandi wrote: > 2. Hard lockup: > G450, I set con2fb, switch consoles some times and there it comes. > swithc between X and single console is OK. Did you boot with 'video=scrollback:0' ? You must ;-) > 3. seems that I have G450 and linux shows it as G400. > bash-2.04$ /sbin/lspci: > 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev >82) > /proc/pci: > VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 130). rev < 128 => G400, rev >= 128 => G450. Ask Matrox why they did so stupid thing. > G400 drivers also work, but matroxset aint switching second head > to monitor output, neither does anything else. It remains blank. Secondary output on G400 is in monitor mode by default. Are you sure that you insmodded all needed modules to kernel? i2c-matrox, matroxfb_maven, matroxfb_crtc2, ... If you do not know which ones, just build everything into kernel - and do not forget about i2c bit-banging as documented in documentation... Petr Vandrovec [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.3 SMP: nfs stale handle, fb dualhead hardlock, G400/450 misnaming
> 1. stale NFS file handle > 2.4.2-ac28 serving nfs3 from reiserfs > 2.4.3 being nfs3 client, You need additional patches for NFS serving from Reiserfs > 3. seems that I have G450 and linux shows it as G400. > bash-2.04$ /sbin/lspci: > 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 82) > The G450 and G400 use the same PCI identity, and different subids. So that is expected behaviour rather than a bug - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.3 SMP: nfs stale handle, fb dualhead hardlock, G400/450 misnaming
1. stale NFS file handle 2.4.2-ac28 serving nfs3 from reiserfs 2.4.3 being nfs3 client, nfs damn slow on 100Mbps p2p link. mounted nfs with rsize=8192,wsize=8192 nfs fast. soon got : bash-2.04$ls ls .: stale NFS file handle just about home directory it says so. 2. Hard lockup: G450, I set con2fb, switch consoles some times and there it comes. swithc between X and single console is OK. 3. seems that I have G450 and linux shows it as G400. bash-2.04$ /sbin/lspci: 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 82) /proc/pci: VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 130). /sbin/lspci -n 01:00.0 Class 0300: 102b:0525 (rev 82) at least when I finally, after a longlong braindamage, started using G450 stuff everywhere, it become more and more usable. for dual fb X it is stable and usable now. G400 drivers also work, but matroxset aint switching second head to monitor output, neither does anything else. It remains blank. elmer. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.4.3 SMP: nfs stale handle, fb dualhead hardlock, G400/450 misnaming
1. stale NFS file handle 2.4.2-ac28 serving nfs3 from reiserfs 2.4.3 being nfs3 client, nfs damn slow on 100Mbps p2p link. mounted nfs with rsize=8192,wsize=8192 nfs fast. soon got : bash-2.04$ls ls .: stale NFS file handle just about home directory it says so. 2. Hard lockup: G450, I set con2fb, switch consoles some times and there it comes. swithc between X and single console is OK. 3. seems that I have G450 and linux shows it as G400. bash-2.04$ /sbin/lspci: 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 82) /proc/pci: VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 130). /sbin/lspci -n 01:00.0 Class 0300: 102b:0525 (rev 82) at least when I finally, after a longlong braindamage, started using G450 stuff everywhere, it become more and more usable. for dual fb X it is stable and usable now. G400 drivers also work, but matroxset aint switching second head to monitor output, neither does anything else. It remains blank. elmer. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.3 SMP: nfs stale handle, fb dualhead hardlock, G400/450 misnaming
1. stale NFS file handle 2.4.2-ac28 serving nfs3 from reiserfs 2.4.3 being nfs3 client, You need additional patches for NFS serving from Reiserfs 3. seems that I have G450 and linux shows it as G400. bash-2.04$ /sbin/lspci: 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 82) The G450 and G400 use the same PCI identity, and different subids. So that is expected behaviour rather than a bug - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.3 SMP: nfs stale handle, fb dualhead hardlock, G400/450 misnaming
Elmer Joandi wrote: 2. Hard lockup: G450, I set con2fb, switch consoles some times and there it comes. swithc between X and single console is OK. Did you boot with 'video=scrollback:0' ? You must ;-) 3. seems that I have G450 and linux shows it as G400. bash-2.04$ /sbin/lspci: 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 82) /proc/pci: VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 130). rev 128 = G400, rev = 128 = G450. Ask Matrox why they did so stupid thing. G400 drivers also work, but matroxset aint switching second head to monitor output, neither does anything else. It remains blank. Secondary output on G400 is in monitor mode by default. Are you sure that you insmodded all needed modules to kernel? i2c-matrox, matroxfb_maven, matroxfb_crtc2, ... If you do not know which ones, just build everything into kernel - and do not forget about i2c bit-banging as documented in documentation... Petr Vandrovec [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
