I have a wyse term 3150se system that I would like to install linuxbios on. Does any know the status of the CS55535? Also, what type of Geode is this, can I uses i686 with GCC, or will that give me errors? Trying to figure out what Cflags I can use. http://gentoo-wiki.com/Safe_Cflags
livecd ~ # lspci -vvv 00:01.0 Host bridge: National Semiconductor Corporation Geode GX2 Host Bridge (rev 21) Subsystem: National Semiconductor Corporation Geode GX2 Host Bridge Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 248, Cache Line Size: 32 bytes Region 0: I/O ports at ac1c [size=4]
00:01.1 VGA compatible controller: National Semiconductor Corporation Geode GX2 Graphics Processor (prog-if 00 [VGA]) Subsystem: National Semiconductor Corporation Geode GX2 Graphics Processor Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Region 0: Memory at 41000000 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at 40ffc000 (32-bit, non-prefetchable) [size=16K] Region 2: Memory at 40ff8000 (32-bit, non-prefetchable) [size=16K] Region 3: Memory at 40ff4000 (32-bit, non-prefetchable) [size=16K]
00:0d.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 22 Interrupt: pin A routed to IRQ 10 Region 4: I/O ports at eee0 [size=32] Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:0d.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 22 Interrupt: pin B routed to IRQ 10 Region 4: I/O ports at eec0 [size=32] Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:0d.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63) (prog-if 20 [EHCI]) Subsystem: VIA Technologies, Inc. USB 2.0 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 64, Cache Line Size: 32 bytes Interrupt: pin C routed to IRQ 5 Region 0: Memory at efe00000 (32-bit, non-prefetchable) [size=256] Capabilities: [80] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:0e.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) Subsystem: Realtek Semiconductor Co., Ltd. RT8139 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 64 (8000ns min, 16000ns max) Interrupt: pin A routed to IRQ 11 Region 0: I/O ports at ef00 [size=256] Region 1: Memory at eff00000 (32-bit, non-prefetchable) [size=256] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:0f.0 ISA bridge: National Semiconductor Corporation CS5535 ISA bridge (rev 13) Subsystem: National Semiconductor Corporation CS5535 ISA bridge Control: I/O+ Mem- BusMaster- SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Region 0: I/O ports at 1020 [size=8] Region 1: I/O ports at 6100 [size=256] Region 2: I/O ports at 6200 [size=64] Region 3: I/O ports at 1000 [size=32] Region 4: I/O ports at 9d00 [size=128] Region 5: I/O ports at 9c00 [size=64]
00:0f.2 IDE interface: National Semiconductor Corporation CS5535 IDE (prog-if 80 [Master]) Subsystem: National Semiconductor Corporation CS5535 IDE Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0, Cache Line Size: 32 bytes Region 4: I/O ports at eeb0 [size=16]
00:0f.3 Multimedia audio controller: National Semiconductor Corporation CS5535 Audio Subsystem: National Semiconductor Corporation CS5535 Audio Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin B routed to IRQ 5 Region 0: I/O ports at ee00 [size=128]
livecd ~ # cat /proc/cpuinfo processor : 0 vendor_id : Geode by NSC cpu family : 5 model : 5 model name : Geode(TM) Integrated Processor by National Semi stepping : 2 cpu MHz : 399.932 cache size : 32 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de pse tsc msr cx8 pge cmov mmx mmxext 3dnowext 3dnow up bogomips : 804.86
On Fri, Oct 26, 2007 at 05:37:11PM -0700, Adam Talbot wrote:
I have a wyse term 3150se system that I would like to install linuxbios on. Does any know the status of the CS55535? Also, what type of Geode
Should work AFAIK. Just try it...
is this, can I uses i686 with GCC, or will that give me errors? Trying to figure out what Cflags I can use. http://gentoo-wiki.com/Safe_Cflags
I guess a generic 686 kernel should work fine (as it does on GX1 boxes), if that's what you're asking.
livecd ~ # lspci -vvv
Please also post 'lspci -tvnn' and 'superiotool -dV' for reference. Does this box have a socketed PLCC (or DIP?) BIOS?
Uwe.
On 27/10/07 19:38 +0200, Uwe Hermann wrote:
On Fri, Oct 26, 2007 at 05:37:11PM -0700, Adam Talbot wrote:
I have a wyse term 3150se system that I would like to install linuxbios on. Does any know the status of the CS55535? Also, what type of Geode
Should work AFAIK. Just try it...
Actually, I don't think it will work.
is this, can I uses i686 with GCC, or will that give me errors? Trying to figure out what Cflags I can use. http://gentoo-wiki.com/Safe_Cflags
I guess a generic 686 kernel should work fine (as it does on GX1 boxes), if that's what you're asking.
You shouldn't use 686 - these are i586 instruction sets. But there are some native i686 instructions, and they do run the risk of tripping you up (as happened to OLPC last year when readhat put 686 native instructions into 'as', with the less then hilarious results).
Jordan
On 10/29/07, Jordan Crouse jordan.crouse@amd.com wrote:
You shouldn't use 686 - these are i586 instruction sets. But there are some native i686 instructions, and they do run the risk of tripping you up (as happened to OLPC last year when readhat put 686 native instructions into 'as', with the less then hilarious results).
Jordan
Jordan Crouse Systems Software Development Engineer Advanced Micro Devices, Inc.
-- linuxbios mailing list linuxbios@linuxbios.org http://www.linuxbios.org/mailman/listinfo/linuxbios
On 10/29/07, Jordan Crouse jordan.crouse@amd.com wrote:
You shouldn't use 686 - these are i586 instruction sets. But there are some native i686 instructions, and they do run the risk of tripping you up (as happened to OLPC last year when readhat put 686 native instructions into 'as', with the less then hilarious results).
don't know why gmail just sent that last message. Sorry
I wonder if this also broke grub. I have a grub from FC7 which won't work on qemu. Neat, eh? A bootloader that is cpu-specific.
ron
Strange, GCC just finished compiling. No errors and I have the system running i686 native. I tuned with CFLAGS="-Os -march=i686 -pipe" -Adam
ron minnich wrote:
On 10/29/07, Jordan Crouse jordan.crouse@amd.com wrote:
You shouldn't use 686 - these are i586 instruction sets. But there are some native i686 instructions, and they do run the risk of tripping you up (as happened to OLPC last year when readhat put 686 native instructions into 'as', with the less then hilarious results).
don't know why gmail just sent that last message. Sorry
I wonder if this also broke grub. I have a grub from FC7 which won't work on qemu. Neat, eh? A bootloader that is cpu-specific.
ron
On 29/10/07 15:11 -0700, Adam Talbot wrote:
Strange, GCC just finished compiling. No errors and I have the system running i686 native. I tuned with CFLAGS="-Os -march=i686 -pipe" -Adam
Most people will be happy. But the potential does exist, and so I have to go the safe route and recommend i586, lest somebody see my words on an e-mail archive somewhere and encounter real breakage and yell at me.
As always, your milage may vary, and if you get better mileage then the dealer says you do, I say go with it.. :)
Jordan
ron minnich wrote:
On 10/29/07, Jordan Crouse jordan.crouse@amd.com wrote:
You shouldn't use 686 - these are i586 instruction sets. But there are some native i686 instructions, and they do run the risk of tripping you up (as happened to OLPC last year when readhat put 686 native instructions into 'as', with the less then hilarious results).
don't know why gmail just sent that last message. Sorry
I wonder if this also broke grub. I have a grub from FC7 which won't work on qemu. Neat, eh? A bootloader that is cpu-specific.
ron
-
Adam Talbot -
Jordan Crouse -
ron minnich -
Uwe Hermann