RE: xf86config for Toshiba satellite pro laptop
Robert, Thanks so much! You're right, I mixed the numbers up! It's a 4260dvd. Anyway, I got X up and running. It took a lot of trial and error. The problem was 2 fold. First, there's a bug in sysinstall. I was getting a fail error message every time because sysinstall was looking for the new XF86Config file somewhere in the /etc folder. However, the new file was being written and put in the /usr/X11R6/lib/X11 folder. If everything had been put in the file correctly then all I needed to do was type startx. However, that's where my second problem occurred. I noticed that when I changed settings for setting up X in the graphical interface for configuring X, some of the lines would not be overwritten. So, I would get a line like: Driver 'vga' Chipset 'savage IX' and vise versa. When I used the text version of the configuration program, it seemed to rewrite the whole file with consistent data. Anyway, I was finally able to get it up and running - thanks to a few encouraging words for the mailing list. Thanks so much for responding! Vaughan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Sunday, August 29, 2004 9:08 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: xf86config for Toshiba satellite pro laptop Aloha Vaughan, Vaughan Moore wrote: I'm a complete newbie and I'm trying to set up X server on a Toshiba Satellite pro 4620dvd laptop. Everytime I run through xf86cfg or xf86cfg -textmode I get the error message The XFree86 configuration process seems to have failed. Would you like to try again? Obviously, this is a bit frustrating. Did you mean a 4260dvd? I cannot find anything on a 4620dvd. If you had a slight case of dyslexia or maybe a little fat fingering, :o) I may be of some help. I have FreeBSD 5.3Beta1 loaded on a HP Pavillion N5310. I checked the specs on the Toshiba Pro 4260dvd (attached pdf) and it has the same video driver as my HP. i.e. s3 Savage IX. So, FWIW, Here are the important bits from my xorg.conf Section Monitor HorizSync 31.5 - 80 VertRefresh 55 - 61 Section Device Identifier Card0 Driver savage VendorName S3 Inc. BoardName 86c270-294 Savage/IX-MV BusID PCI:1:1:0 Section Screen DefaultDepth24 SubSection Display Viewport0 0 Depth 24 Modes 1024x768 800x600 I really hope this helps. At one time I had either Lindows (Linspire) or SuSE loaded on this computer. That is where I found the horizontal and vertical data. Plagarize whenever you can! You might also try pciconf -lv to see if your board name and bus id are correct. Best of luck Robert ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: xf86config for Toshiba satellite pro laptop
Thanks Kevin! One of my problems was the listing for the savage driver and chipset were not working well together. Using the text version of the configuration program took the chipset line out when I selected the generic Savage driver. That fixed it! Thanks so much for your help! Vaughan -Original Message- From: Kevin D. Kinsey, DaleCo, S.P. [mailto:[EMAIL PROTECTED] Sent: Sunday, August 29, 2004 7:10 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: xf86config for Toshiba satellite pro laptop Vaughan Moore wrote: I'm a complete newbie and I'm trying to set up X server on a Toshiba Satellite pro 4620dvd laptop. Everytime I run through xf86cfg or xf86cfg -textmode I get the error message The XFree86 configuration process seems to have failed. Would you like to try again? Obviously, this is a bit frustrating. Sounds like it. Wonder why? Are you running the program with root privileges? (You should be...) Here are what I think are the valid parts of the XF86Config file, but I may be missing something - please let me know. InputDevice Driver = mouse Option = Protocol Auto Option = Device /dev/sysmous InputDevice Driver Keyboard Option Skbmode1 pc101 (note: my laptop only has 85 keys Option XkbLayout us Monitor HorizSync 31.5-31.5 VertRefresh 50.0-70.0 Card Driver s3 VendorName S3 Inc. BoardName 86C270-294 Savage/IX-MV ChipSet SuperSavage/IX64 BusID PCI:1:0:0 Screen Default Depth 8 Display Depth 1 Display Depth 4 Display Depth 8 Modes 640x480 Display Depth 15 Display Depth 16 Display Depth 24 My main questions are: 1) The Toshiba documentation and Web site do not tell me what my internal monitor's horizontal sync or vertical refresh rate is. (although it does give me refresh rates for an external monitor - 60/75/85 @16M colors). Is there a place I can go to find this information? Well, this is pretty common. Many desktop monitors don't give such information, either, and you either Google for it or guess, usually. What happens if you call startx, or have you? 2) Are there other obvious reasons the configuration would fail other than the monitor? The most obvious one I can think of is that, IIRC, the driver for the Savage chipsets is savage, not s3. But I could be wrong; can't remember ever trying X with the savage driver. Have you tried the vesa driver? Might do something for ya... Secondly, your Horizontal sync range isn't a range. Perhaps opening that up a bit would allow you to try it out. Certainly there could be other issues as well. I mentioned permissions above, for one. If you have the above in /etc/X11R6/XF86Config, if you run startx you should get either a server running or some error output in /var/log that might help...OTOH, I've never set up X on any laptop; I don't know if it's unsafe to try with a relatively untested config file. But the values look sane enough for a CRT display ... 3) Are there any sites I can visit for more info? XFree's site at xfree86.org; the FreeBSD handbook at www.freebsd.org/handbook come to mind. Thanks so much! You are welcome. Vaughan Moore Also, did I post this to the right list? If not, please let me know where it should go. Works for me. Kevin Kinsey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
xf86config for Toshiba satellite pro laptop
I'm a complete newbie and I'm trying to set up X server on a Toshiba Satellite pro 4620dvd laptop. Everytime I run through xf86cfg or xf86cfg -textmode I get the error message The XFree86 configuration process seems to have failed. Would you like to try again? Obviously, this is a bit frustrating. Here are what I think are the valid parts of the XF86Config file, but I may be missing something - please let me know. InputDevice Driver = mouse Option = Protocol Auto Option = Device /dev/sysmous InputDevice Driver Keyboard Option Skbmode1 pc101 (note: my laptop only has 85 keys Option XkbLayout us Monitor HorizSync 31.5-31.5 VertRefresh 50.0-70.0 Card Driver s3 VendorName S3 Inc. BoardName 86C270-294 Savage/IX-MV ChipSet SuperSavage/IX64 BusID PCI:1:0:0 Screen Default Depth 8 Display Depth 1 Display Depth 4 Display Depth 8 Modes 640x480 Display Depth 15 Display Depth 16 Display Depth 24 My main questions are: 1) The Toshiba documentation and Web site do not tell me what my internal monitor's horizontal sync or vertical refresh rate is. (although it does give me refresh rates for an external monitor - 60/75/85 @16M colors). Is there a place I can go to find this information? 2) Are there other obvious reasons the configuration would fail other than the monitor? 3) Are there any sites I can visit for more info? Thanks so much! Vaughan Moore Also, did I post this to the right list? If not, please let me know where it should go. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FTP installation through a NAT on a DSL connection
Thanks for the suggestion. In this case, I don't think this is the problem. I took a look at the debugging messages and I see the installation program: Found ftp2.freebsd.org logged me in changed working directories to the 4.7-RELEASE then: Sending PASV Entering Passive Mode (130,94,149,162,215,188) Sending: RETR bin/bin.inf Opening BINARY mode data connection for 'bin/bin.inf' (4255 bytes) DEBUG: Parsing atributes file for distribution bin Then I get an error message Cannont parse information file for the bin distribuiton: I/O error. Please verify that your media is valid and try again. So, it seems that I'm able to log in to the FTP server, change directories, enter passive mode and request the bin.inf file. All those activities don't take much in the way of packet size. But the bin.inf is 4255 bytes so the packets will have to be broken down. As I said in my original message, I think the problem is my MTU setting. Does anyone know how to change the Max MTU size in the Network Configuration screen. It seems like I would be able to put a command in the options box. I experimented with this but I guess I'm not getting the syntax right. I've had to set the Max MTU on my Windows machine to 1330 so it makes sense that I would have to do the same on freebsd. Thanks for the help. Vaughan -Original Message- From: Terry J Dunlap Jr [mailto:[EMAIL PROTECTED] Sent: Saturday, February 22, 2003 10:14 PM To: Vaughan Moore Subject: Re: FTP installation through a NAT on a DSL connection If your install box is connecting through the Win98 box with Zone Alarm, did you add the FTP site as one of the authorized IPs you can connect with? And, have you tried connecting when Zone Alarm is disabled? I had the exact problem with my FreeBSD router. I could make the connection to the site, but packets coming back were blocked. After some research, I discovered I needed to add a dynamic rule that would allow it back in. The only way I know how to do that with Zone Alarm is to add the IP to the list of allowable hosts. Terry - Original Message - From: Vaughan Moore [EMAIL PROTECTED] To: Willie Viljoen [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, February 22, 2003 9:57 PM Subject: RE: FTP installation through a NAT on a DSL connection Well, at least now I'm getting packets back and forth. DNS: query 10.10.1.210:1024 - 199.45.32.43:53 for ftp2.freebsd.org DNS: query 151.200.238.11:45175 - 199.45.32.43:53 for ftp2.freebsd.org DNS: query 10.10.1.210:1025 - 199.45.32.43:53 for ftp2.freebsd.org DNS: query 151.200.238.11:45176 - 199.45.32.43:53 for ftp2.freebsd.org TCP: packet 5400, length 74, 10.10.1.210:1024 - 130.94.149.162:21, flags: SYN , seq:2842580946 ack:0 TCP: packet 5404, length 74, 151.200.238.11:45177 - 130.94.149.162:21, flags: SYN , seq:2842580946 ack:0 TCP: packet 5405, length 74, 130.94.149.162:21 - 151.200.238.11:45177, flags: SYN ACK , seq:1377839201 ack:2842580947 TCP: packet 5406, length 74, 130.94.149.162:21 - 10.10.1.210:1024, flags: SYN ACK , seq:1377839201 ack:2842580947 TCP: packet 5407, length 66, 10.10.1.210:1024 - 130.94.149.162:21, flags: ACK , seq:2842580947 ack:1377839202 TCP: packet 5408, length 76, 10.10.1.210:1024 - 130.94.149.162:21, flags: ACK , seq:2842580947 ack:1377839202 TCP: packet 5409, length 66, 151.200.238.11:45177 - 130.94.149.162:21, flags: ACK , seq:2842580947 ack:1377839202 TCP: packet 5410, length 76, 151.200.238.11:45177 - 130.94.149.162:21, flags: ACK , seq:2842580947 ack:1377839202 TCP: packet 5411, length 123, 130.94.149.162:21 - 151.200.238.11:45177, flags: ACK , seq:1377839202 ack:2842580947 TCP: packet 5412, length 123, 130.94.149.162:21 - 10.10.1.210:1024, flags: ACK , seq:1377839202 ack:2842580947 TCP: packet 5413, length 124, 130.94.149.162:21 - 151.200.238.11:45177, flags: ACK , seq:1377839259 ack:2842580957 TCP: packet 5414, length 124, 130.94.149.162:21 - 10.10.1.210:1024, flags: ACK , seq:1377839259 ack:2842580957 TCP: packet 5415, length 66, 10.10.1.210:1024 - 130.94.149.162:21, flags: ACK , seq:2842580957 ack:1377839317 TCP: packet 5416, length 99, 10.10.1.210:1024 - 130.94.149.162:21, flags: ACK , seq:2842580957 ack:1377839317 TCP: packet 5417, length 66, 151.200.238.11:45177 - 130.94.149.162:21, flags: ACK , seq:2842580957 ack:1377839317 TCP: packet 5418, length 99, 151.200.238.11:45177 - 130.94.149.162:21, flags: ACK , seq:2842580957 ack:1377839317 TCP: packet 5419, length 114, 130.94.149.162:21 - 151.200.238.11:45177, flags: ACK , seq:1377839317 ack:2842580990 TCP: packet 5420, length 114, 130.94.149.162:21 - 10.10.1.210:1024, flags: ACK , seq:1377839317 ack:2842580990 TCP: packet 5421, length 74, 10.10.1.210:1024 - 130.94.149.162:21, flags: ACK , seq:2842580990 ack:1377839365 TCP: packet 5422, length 74, 151.200.238.11:45177 - 130.94.149.162:21, flags: ACK , seq:2842580990 ack:1377839365 TCP: packet 5423, length 86, 130.94.149.162:21 - 151.200.238.11:45177, flags: ACK , seq
FTP installation through a NAT on a DSL connection
I'm installing 4.7 at home. The Intel box is behind a NAT running on a Win98 box with ZoneAlarm running. The point of installing 4.7 is so that I can replace the 98 box as my gateway to my Verizon DSL connection. My installation fails when the program tries to access one of the ftp servers. When the time-out occurs I get an installation media error message. I know that my subnet on the NAT works because when I plug a 2000 machine into the gateway I can access the Internet. However, I had to lower the Max MTU settings in the registry to do it. I understand that PPPoE requires a lower MTU setting, but I'm not sure how to set MTU in the installation program. Can anyone help me with the problem? Vaughan Moore To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: FTP installation through a NAT on a DSL connection
Thanks so much for the suggestion. When I use passive mode I get an error message Could not open ftp connection to ftp3.freebsd.org. Service not available, closing control connection. When I hit OK another error message comes up unable to initialize selected media. Would you like to adjust you media configuration and try again? When I do that, I go through the network configuration process again, but I get an immediate error message Cannot resolve host name ftp3.freebsd.org! Are you sure that your name server, gateway and network interface are correctly configured? I'm using DHCP, and it is pulling the correct IP's for these. Here's the log in my Winroute NAT. What do you think I'm doing wrong? Vaughan Interface Table: Interface Status Medium IP address NAT Index NETGEAR FA310TX Fast Ethe... UpEthernet10.10.1.1 50331652 NETGEAR FA311 Fast Ethern... UpEthernet10.10.1.0 67108869 Dial in adapter DownRAS 0.0.0.0 0 line1 Up RAS 151.200.238.11 on 16777218 dhcp TCP/IP stack's Routing Table: Net MaskGateway Interface Metric 0.0.0.0 0.0.0.0 line1 1 10.10.1.0 255.255.255.0 NETGEAR FA310TX Fast Ethe... 2 10.10.1.0 255.255.255.0 NETGEAR FA311 Fast Ethern... 2 151.200.0.0 255.255.0.0line1 1 DNS: query 10.10.1.210:1024 - 10.10.1.1:53 for ftp3.freebsd.org dns: query from 10.10.1.210:1024 id 41361 dns: question: A, ftp3.freebsd.org dns: reply: ftp3.freebsd.org has 198.82.184.28 DNS: query 10.10.1.210:1025 - 10.10.1.1:53 for ftp3.freebsd.org dns: query from 10.10.1.210:1025 id 41362 dns: question: A, ftp3.freebsd.org dns: reply: ftp3.freebsd.org has 198.82.184.28 TCP: packet 1278, length 74, 10.10.1.210:1024 - 198.82.184.28:21, flags: SYN , seq:4161382813 ack:0 TCP: packet 1282, length 74, 151.200.238.11:45050 - 198.82.184.28:21, flags: SYN , seq:4161382813 ack:0 - Snip - Repeats 8 times and drops down to a length of 60 after try number 3 DNS: query 151.200.238.11:45051 - 199.45.32.43:53 for 9.136.168.217.in-addr.arpa DNS: query 151.200.238.11:45052 - 199.45.32.38:53 for 9.136.168.217.in-addr.arpa TCP: packet 1323, length 74, 198.82.184.28:21 - 151.200.238.11:45050, flags: SYN ACK , seq:77305705 ack:4161382814 TCP: packet 1327, length 74, 198.82.184.28:21 - 10.10.1.210:1024, flags: SYN ACK , seq:77305705 ack:4161382814 TCP: packet 1328, length 60, 10.10.1.210:1024 - 198.82.184.28:21, flags: RST , seq:4161382814 ack:0 This is where the install program quit and asked if I wanted to retry. -Original Message- From: Willie Viljoen [mailto:[EMAIL PROTECTED] Behalf Of Willie Viljoen Sent: Saturday, February 22, 2003 11:26 AM To: Vaughan Moore Cc: [EMAIL PROTECTED] Subject: Re: FTP installation through a NAT on a DSL connection On Saturday 22 February 2003 16:55, Vaughan Moore wrote: I'm installing 4.7 at home. The Intel box is behind a NAT running on a Win98 box with ZoneAlarm running. The point of installing 4.7 is so that I can replace the 98 box as my gateway to my Verizon DSL connection. My installation fails when the program tries to access one of the ftp servers. When the time-out occurs I get an installation media error message. I know that my subnet on the NAT works because when I plug a 2000 machine into the gateway I can access the Internet. However, I had to lower the Max MTU settings in the registry to do it. I understand that PPPoE requires a lower MTU setting, but I'm not sure how to set MTU in the installation program. Can anyone help me with the problem? Vaughan Moore I'm almost sure MTU is not the problem in this case, the Windows machine should be taking care of that. Try setting FTP into passive mode in the installer's options screen, or turning off passive mode if that's the default on your version. Windows 98 NATs are not famous for handling FTP properly. -- Willie Viljoen Freelance IT Consultant 214 Paul Kruger Avenue, Universitas Bloemfontein 9321 South Africa +27 51 522 15 60 +27 51 522 44 36 (after hours) +27 82 404 03 27 (mobile) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: FTP installation through a NAT on a DSL connection
Well, at least now I'm getting packets back and forth. DNS: query 10.10.1.210:1024 - 199.45.32.43:53 for ftp2.freebsd.org DNS: query 151.200.238.11:45175 - 199.45.32.43:53 for ftp2.freebsd.org DNS: query 10.10.1.210:1025 - 199.45.32.43:53 for ftp2.freebsd.org DNS: query 151.200.238.11:45176 - 199.45.32.43:53 for ftp2.freebsd.org TCP: packet 5400, length 74, 10.10.1.210:1024 - 130.94.149.162:21, flags: SYN , seq:2842580946 ack:0 TCP: packet 5404, length 74, 151.200.238.11:45177 - 130.94.149.162:21, flags: SYN , seq:2842580946 ack:0 TCP: packet 5405, length 74, 130.94.149.162:21 - 151.200.238.11:45177, flags: SYN ACK , seq:1377839201 ack:2842580947 TCP: packet 5406, length 74, 130.94.149.162:21 - 10.10.1.210:1024, flags: SYN ACK , seq:1377839201 ack:2842580947 TCP: packet 5407, length 66, 10.10.1.210:1024 - 130.94.149.162:21, flags: ACK , seq:2842580947 ack:1377839202 TCP: packet 5408, length 76, 10.10.1.210:1024 - 130.94.149.162:21, flags: ACK , seq:2842580947 ack:1377839202 TCP: packet 5409, length 66, 151.200.238.11:45177 - 130.94.149.162:21, flags: ACK , seq:2842580947 ack:1377839202 TCP: packet 5410, length 76, 151.200.238.11:45177 - 130.94.149.162:21, flags: ACK , seq:2842580947 ack:1377839202 TCP: packet 5411, length 123, 130.94.149.162:21 - 151.200.238.11:45177, flags: ACK , seq:1377839202 ack:2842580947 TCP: packet 5412, length 123, 130.94.149.162:21 - 10.10.1.210:1024, flags: ACK , seq:1377839202 ack:2842580947 TCP: packet 5413, length 124, 130.94.149.162:21 - 151.200.238.11:45177, flags: ACK , seq:1377839259 ack:2842580957 TCP: packet 5414, length 124, 130.94.149.162:21 - 10.10.1.210:1024, flags: ACK , seq:1377839259 ack:2842580957 TCP: packet 5415, length 66, 10.10.1.210:1024 - 130.94.149.162:21, flags: ACK , seq:2842580957 ack:1377839317 TCP: packet 5416, length 99, 10.10.1.210:1024 - 130.94.149.162:21, flags: ACK , seq:2842580957 ack:1377839317 TCP: packet 5417, length 66, 151.200.238.11:45177 - 130.94.149.162:21, flags: ACK , seq:2842580957 ack:1377839317 TCP: packet 5418, length 99, 151.200.238.11:45177 - 130.94.149.162:21, flags: ACK , seq:2842580957 ack:1377839317 TCP: packet 5419, length 114, 130.94.149.162:21 - 151.200.238.11:45177, flags: ACK , seq:1377839317 ack:2842580990 TCP: packet 5420, length 114, 130.94.149.162:21 - 10.10.1.210:1024, flags: ACK , seq:1377839317 ack:2842580990 TCP: packet 5421, length 74, 10.10.1.210:1024 - 130.94.149.162:21, flags: ACK , seq:2842580990 ack:1377839365 TCP: packet 5422, length 74, 151.200.238.11:45177 - 130.94.149.162:21, flags: ACK , seq:2842580990 ack:1377839365 TCP: packet 5423, length 86, 130.94.149.162:21 - 151.200.238.11:45177, flags: ACK , seq:1377839365 ack:2842580998 TCP: packet 5424, length 86, 130.94.149.162:21 - 10.10.1.210:1024, flags: ACK , seq:1377839365 ack:2842580998 But, I get this error message: Cannot parse information file for the bin distribution: I/O error. Please verify that your media is valid and try again. My ip gateway is 10.10.1.1 My name server is 199.45.32.43 My ip is 10.10.1.210 My netmask is 255.255.255.0 Again, thanks so much for the help. Vaughan -Original Message- From: Willie Viljoen [mailto:[EMAIL PROTECTED] Behalf Of Willie Viljoen Sent: Saturday, February 22, 2003 5:15 PM To: Vaughan Moore Cc: [EMAIL PROTECTED] Subject: Re: FTP installation through a NAT on a DSL connection You're one step closer. When doing network configuration, make sure you list a valid and real DNS server. Try setting it up to use the DNS at your ISP, or the winroute if it provides DNS. On Sunday 23 February 2003 0:08, Vaughan Moore wrote: Thanks so much for the suggestion. When I use passive mode I get an error message Could not open ftp connection to ftp3.freebsd.org. Service not available, closing control connection. When I hit OK another error message comes up unable to initialize selected media. Would you like to adjust you media configuration and try again? When I do that, I go through the network configuration process again, but I get an immediate error message Cannot resolve host name ftp3.freebsd.org! Are you sure that your name server, gateway and network interface are correctly configured? I'm using DHCP, and it is pulling the correct IP's for these. Here's the log in my Winroute NAT. What do you think I'm doing wrong? Vaughan Interface Table: Interface Status Medium IP address NAT Index NETGEAR FA310TX Fast Ethe... Up Ethernet10.10.1.1 50331652 NETGEAR FA311 Fast Ethern... Up Ethernet10.10.1.0 67108869 Dial in adapter DownRAS 0.0.0.0 0 line1 Up RAS 151.200.238.11 on 16777218 dhcp TCP/IP stack's Routing Table: Net MaskGateway Interface Metric 0.0.0.0 0.0.0.0 line1 1 10.10.1.0
