|
|
Post by musicman on Dec 12, 2010 11:21:57 GMT -5
Item 1:
The first hard drive [drive 0] on my Primary IDE cable was not listed as detected. However, the second hard drive [drive 1] on the same cable was detected, as well as all external USB drives.
Item 2:
[this is the first time I have tried a UNIX-based OS, so please forgive my ignorance in having to ask this....]
I don't know how to translate my Windows internet setting. I am currently connecting to the internet through another computer - both are XP Professional - using "Internet Connection Sharing". In KNOS, I can access an external drive on the "ICS Host", so I know the networking is OK. I am NOT currently use DHCP on the computer I tested KNOS on [this computer], preferring to enter IP settings to the host and DNS settings manually.
I saw where you could connect through HTTP proxy; have never tried that. I was hoping that I would be able to just enter the IP address and Subnet Mask & DNS settings where needed. Is this possible? If so, how? Thank you.
|
|
|
|
Post by Kevin McAleavey on Dec 12, 2010 19:07:07 GMT -5
Item 1: The first hard drive [drive 0] on my Primary IDE cable was not listed as detected. However, the second hard drive [drive 1] on the same cable was detected, as well as all external USB drives. Item 2: [this is the first time I have tried a UNIX-based OS, so please forgive my ignorance in having to ask this....] I don't know how to translate my Windows internet setting. I am currently connecting to the internet through another computer - both are XP Professional - using "Internet Connection Sharing". In KNOS, I can access an external drive on the "ICS Host", so I know the networking is OK. I am NOT currently use DHCP on the computer I tested KNOS on [this computer], preferring to enter IP settings to the host and DNS settings manually. I saw where you could connect through HTTP proxy; have never tried that. I was hoping that I would be able to just enter the IP address and Subnet Mask & DNS settings where needed. Is this possible? If so, how? Thank you. Although it is possible to build a KNOS with any possible configurations desired, the current design is strictly a "no touch" DHCP configuration. The objective in our design here is reliable, no configuration needed operation. It is possible to manually configure even this KNOS, but it's challenging since manual command lines would be required in a terminal session to do so. For clients who would want a custom build, setting up hard-coded networking is a breeze, but the "general distribution" KNOS is designed to prevent diddling that would result in non-functionality, thus this limitation. What I'd recommend is setting up the Windows ICS to allow DHCP connection to the XP box in which case KNOS should find it automatically for you. If you still want to do it manually, I think we should take it to email since I will need a diagnostics printout from you (to determine what your ethernet hardware type is) and of course the gateway information from your XP box which I suspect you won't want to put out publicly. Any manual settings would not be retained however and would have to be redone each time KNOS is booted. That's why you might want to go the DHCP route, or use a hub to give KNOS its own feed. It should still be able to find the XP boxes on your subnet. As to your "missing" hard drive, interesting indeed. If you can go up to the "Applications" item up on top of your desktop there, select "System tools" and then hit up "KNOS-diagnostics" and send me a copy of the "diags" file that it creates, be happy to take a look at your hardware info and try to see why it's doing that. Drop me an email at support {at} knosproject.com with that attached, and let's see what we've got. |
|
|
|
Post by musicman on Dec 12, 2010 20:19:39 GMT -5
OK - will get the diagnostic for the hard drive.
The XP ICS host computer does have DHCP enabled, and the KNOS computer is seen on the subnet., and it also sees the XP ICS host.
The adapter in question on the KNOS computer is set up manually. I know I can set it up DHCP as well, but of course, that should affect only WINDOWS connectivity on the KNOS computer!
I will check more and let you know.
|
|
|
|
Post by Kevin McAleavey on Dec 12, 2010 20:55:01 GMT -5
OK - will get the diagnostic for the hard drive. The XP ICS host computer does have DHCP enabled, and the KNOS computer is seen on the subnet., and it also sees the XP ICS host. The adapter in question on the KNOS computer is set up manually. I know I can set it up DHCP as well, but of course, that should affect only WINDOWS connectivity on the KNOS computer! I will check more and let you know. Heh. OK, got my head spinning there.  I'm guessing that your connectivity out of KNOS is OK then ... Windows is not going to be allowed to see KNOS, that's part of our design philosophy of not putting Windows at risk. As to manual setup of the card in the KNOS machine, we don't touch anything on any underlying Windows machine in the box, so any settings you had in Windows will not be looked at, much less disturbed in any way. And while you COULD set things up manually, it's a pain in the butt to do so in the beta3 KNOS since we didn't expect anyone to want to do that. |
|
|
|
Post by musicman on Dec 12, 2010 23:44:42 GMT -5
Hi Kevin - first, a word of warning. I will probably be the worst - or one of the worst - pain-in-the-butt people you have ever met when it comes to computers. Since I am completely self-taught, I drive everyone absolutely nuts, always - it seems - getting into more or less impossible questions / areas.
OK - with that in mind -
I am now on the the KNOS project page while using KNOS!!!!! I did not change ANYTHING in ANY setting of KNOS!!!! I only had to make one change elsewhere - to change the setting "EDIT > FIREFOX PREFERENCE > ADVANCED > CONNECTION > NETWORK > SETTINGS" value from
"USE SYSTEM PROXY SETTINGS" to :"AUTO-DETECT PROXY SETTINGS FOR THIS NETWORK" - and I was immediately connected!!!
|
|
|
|
Post by Kevin McAleavey on Dec 13, 2010 0:35:30 GMT -5
Hi Kevin - first, a word of warning. I will probably be the worst - or one of the worst - pain-in-the-butt people you have ever met when it comes to computers. Since I am completely self-taught, I drive everyone absolutely nuts, always - it seems - getting into more or less impossible questions / areas. OK - with that in mind - I am now on the the KNOS project page while using KNOS!!!!! I did not change ANYTHING in ANY setting of KNOS!!!! I only had to make one change elsewhere - to change the setting "EDIT > FIREFOX PREFERENCE > ADVANCED > CONNECTION > NETWORK > SETTINGS" value from "USE SYSTEM PROXY SETTINGS" to :"AUTO-DETECT PROXY SETTINGS FOR THIS NETWORK" - and I was immediately connected!!! Heh. Glad to meet you ... I'm a hopeless perfectionist! Nothing I appreciate more than having anything not quite right spotted and doing everything I can to make it right. The whole point of our continuing beta testing is to try out new code and make sure we're not leaving anything behind that can cause problems for people later on. And having people willing to beat the hell out of our code to help us perfect it is something we really appreciate. So feel free to be the biggest PIA on the planet ... it can only improve things for everyone. I understand that you've been one of our customers for a very long time, so you know the drill with us ... we actually CARE if it works. I vaguely remember our changing our Firefox setting to the mode you found it in because it caused problems for other people in the distant past. So it's almost amusing that we'd eventually see a situation where the old default setting would end up working for somebody. Heh. Can you tell me a little more about your setup there as far as networking goes (with the Windows boxes and all) so I can try to figure out how to write up your situation for others should we encounter someone else who might run into this situation and would have to do what you did there? Glad to see you lit up ... will try to figure out if we can improve our own autodetecting based on any details I can find out about your situation there. The "normal" setting has worked reliably for everyone and there HAD to be some reason for the strange setting that's working for you. I'd like to pin that down. And PLEASE feel free to be a pain in the rump! We want KNOS to be trouble-free for everyone and its ability to self-configure properly no matter what it's run on means everything to us. |
|
|
|
Post by musicman on Dec 13, 2010 7:53:05 GMT -5
well - you're gonna love this one....when I booted up today, I first clicked on the link for seing new themes / desktops etc. when I clicked on that, something called GNOME WEB BROWSER came up - and I was connected - no settings change or anything! So I then tried Epiphany - same thing - instant connection! Lastly, I tried Firefox - and again - CONNECTION - and without having to change the settings as I did yesterday!!! It is currently still set to "Use System Proxy settings". So - don't know what happened yesterday - but today is even better!!!
|
|
|
|
Post by Kevin McAleavey on Dec 14, 2010 1:07:18 GMT -5
well - you're gonna love this one....when I booted up today, I first clicked on the link for seing new themes / desktops etc. when I clicked on that, something called GNOME WEB BROWSER came up - and I was connected - no settings change or anything! So I then tried Epiphany - same thing - instant connection! Lastly, I tried Firefox - and again - CONNECTION - and without having to change the settings as I did yesterday!!! It is currently still set to "Use System Proxy settings". So - don't know what happened yesterday - but today is even better!!! Just to keep this sane for the benefit of others who breeze through here, I'll handle the "missing drive" problem here and your sound card madness in the other thread. Got it all sorted, and it's amusing. From your diagnostics:
Dec 13 05:56:52 KNOS-32bit kernel: ata0-slave: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=80 wire
Dec 13 05:56:52 KNOS-32bit kernel: ata0: DMA limited to UDMA33, controller found non-ATA66 cable
Dec 13 05:56:52 KNOS-32bit kernel: ad1: setting UDMA33
Dec 13 05:56:52 KNOS-32bit kernel: ad1: 190782MB <WDC WD2000JB-00DUA065.13G65> at ata0-slave UDMA33
Dec 13 05:56:52 KNOS-32bit kernel: ad1: 390721968 sectors [387621C/16H/63S] 16 sectors/interrupt 1 depth queue
---
Dec 13 05:56:52 KNOS-32bit kernel: ata1: Identifying devices: 00030000
Dec 13 05:56:52 KNOS-32bit kernel: ata1: New devices: 00030000
Dec 13 05:56:52 KNOS-32bit kernel: ata1-slave: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire
Dec 13 05:56:52 KNOS-32bit kernel: ata1-master: pio=PIO4 wdma=WDMA2 udma=UDMA66 cable=40 wire
Dec 13 05:56:52 KNOS-32bit kernel: ata1: DMA limited to UDMA33, controller found non-ATA66 cable
Dec 13 05:56:52 KNOS-32bit kernel: acd0: setting UDMA33What that all means is that your FIRST drive has a ratty old 40 pin ATA cable while your second (detected) drive has a proper 80-pin ATA66 cable. Your controller in there wants to talk to KNOS at two separate speeds which is a no-no as a result of that older cable to your first drive. Replace that older cable with a proper 80 pin cable to match the one going to your second drive and all will be well. Windows deals with the problem by going into a special "sloooow" mode. KNOS doesn't expect to see such a slow cable unless all of your cables are slow. The faster cable is telling KNOS to ignore the other one to prevent errors. Net result of replacing that cable will make WIndows run a lot faster too, so it'll be worth the effort. But that's the problem there ... Whoops! Correction! All connectors are 40 pins, but the old connector style had 40 *wires* to it whereas the newer cables have 80 *wires*, not pins. When you look at the cables side by side, the 80 wire ones have more and much thinner wires than the old 40 wire jobs. For the speed of newer drives, each wire needs to have a ground on either side to keep the higher frequency signals from interfering with adjacent wires - that's why the need. All they sell these days are the 80 wire ATA cables, so anything "modern" will work. I was concerned about saying "80 pin" above because the connectors themselves are still 40 pins. |
|
|
|
Post by musicman on Dec 14, 2010 8:49:36 GMT -5
Yeah - I noticed that too in the diag., The 80-pin cables I have seen also have a blue connection to the ATA adapter and a green or blue color denoting pin 1. At the time I installed that drive, it was internatl drive #11, and I ws running out of cables. Have reconfigured, so will grab an old cable - 80-pin this time. Thanks!
|
|
