Re[2]: [Thinstation-general] Unresolved symbols on startup
Brought to you by:
doncuppjr
|
From: Hazil A. <haz...@ya...> - 2003-05-25 17:26:34
|
Hello Miles Roper you wrote: MR> when you do a major recompile of the kernel, (changing the math emulation) MR> will require you to replace all the kernel modules with the new ones as MR> well, check out a script in utils/update/update_modules.sh, this should do MR> it, make sue you modify for your site etc ... :o) MR> cheers MR> Miles MR> -----Original Message----- MR> From: Tiago de Aviz [mailto:Ti...@so...] MR> Sent: Friday, 23 May 2003 04:13 a.m. MR> To: thi...@li... MR> Subject: [Thinstation-general] Unresolved symbols on startup MR> Guys, MR> I just signed up to the discussion list, but i've been watching you =) MR> Here's the deal: I have a bunch of old IBM PC's here that are all 486SX's MR> with 16megs of RAM. I got Thinstation 0.91 here, compiled, but I got a whole MR> lot of missing math emulation problems. I recompiled the Kernel with math MR> emulation and that basically did the trick. MR> Now when the oooold IBM's are booting, I get a bunch of "insmod: unresolved MR> symbol" on startup, even on modules that I didn't select in build.conf. MR> Modules like 8139too, via, eepro100 and so forth. If I select the ne module MR> on build.conf, the module isn't included and the machine won't boot. So I MR> included ne on the kernel. That made the machine get an IP address... But MR> all these errors can't be normal. MR> My idea is to boot these babies on DOS, then call Thinstation via loadlin. MR> What's the problem? Outdated gcc? Which version do I need to build MR> Thinstation? MR> Thanks in advance, MR> Tiago de Aviz MR> IT Consultant MR> MCP-CNA-AIX-CCNA-CCDA MR> -------------------------------- MR> www.softsell.com.br MR> ti...@so... MR> -------------------------------- I'm using Thinstation 0.91 and it's look like that parameter ICA_INITIAL_PROGRAM in thinstation.conf should be filled with an IP address of the server or the client cannot connect to the server (I get an error 50: cannot connect to the server ""), although we have defined it in SESSION_x_SERVER params. But when I fill this parameter with the server IP address, the client can connect to the ICA server, but user cannot logon to the session. This is not Windows settings I think, because using same Windows setting, I can logon to the ICA server using Netstation. How can I fix this problem? Regards Hazil mailto:haz...@ya... |