NTFS 4 Terabyte drive problems on FreeBSD?
Hi, I'm trying to mount a 4 TB drive (The Seagate Backup-Plus) on FreeBSD 9.0 Generic, using mount -t ntfs /dev/da0s1 /mnt It fails with: g_vfs_done() da1s1[READ(offset=0, length=1042)]error=22 mount_ntfs: /dev/da1s1 bad argument However, I can mount a 2 TB ntfs drive with no problem, using the same command, and the 4TB drive checks out fine in Windows. Does anyone know if this limitation exists, and if there is a work-around? I only need READ access to this drive. Thanks a lot! Scott -- s...@ssr.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NTFS 4 Terabyte drive problems on FreeBSD?
In the last episode (Feb 12), Scott Ballantyne said: Hi, I'm trying to mount a 4 TB drive (The Seagate Backup-Plus) on FreeBSD 9.0 Generic, using mount -t ntfs /dev/da0s1 /mnt It fails with: g_vfs_done() da1s1[READ(offset=0, length=1042)]error=22 mount_ntfs: /dev/da1s1 bad argument That's a strange length (1042). I would have expected a multiple of the device blocksize (4096 in the case of the Backup Plus). However, I can mount a 2 TB ntfs drive with no problem, using the same command, and the 4TB drive checks out fine in Windows. Does anyone know if this limitation exists, and if there is a work-around? I only need READ access to this drive. You can try the sysutils/fusefs-ntfs port; the ntfs code in the base system hasn't had much work done on it lately. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Squid 3.2 Reverse Proxy Problems on FreeBSD
Is anyone running else running the Squid 3.2 branch on FreeBSD as a reverse proxy? Specifically using HTTPS and uploading data? The reason I ask, I have a server Running FreeBSD 9.0-p4 and Squid 3.1.21, all works I tried upgrading to a new server running FreeBSD 9.1 with Squid 3.2.6, thought everything was working, then we started getting complaints on to of the back end applications. Tracked the issue down to any submit forms on HTTPS, if somewhere between 2.2k and 3k it breaks, if the post is under that very small size instant success, if over that size the browser churns for a few minutes then returns a Bad Request Your browser sent a request that this server could not understand. On the Squid side there is a TCP_MISS_ABORTED log entry that gets logged. The problem doesn't show up on HTTP, I can upload large files, tested up to 50M. I just wanted to see if any one else is successfully doing this, maybe something specific to my server build and I just need to start over. Both servers have been built from source, both using clang, including ports, except on gcc, open-vm-tools, and squid. They are both running on the same cluster of ESX 4.1 servers. Other than the FreeBSD version and Squid version the other difference is ZFS used on the file system for the FreeBSD 9.1 and UFS used for the FreeBSD 9.0-p4. I have already started a thread on the Squid mailing list on the issue as well, but haven't gotten any help yet. But now that I have the production setup going through the old server again, I can do some more testing and enable debugging and possibly get some useful information as to whats happening. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
HPLIP 3.10.9 problems on FreeBSD 8.1
Hi FreeBSD people, I am trying to make my HP LaserJet P1102 work on FreeBSD 8.1 and towards that goal I installed HPLIP 3.10.9 from the Ports Collection. But there are two problems: 1.First, when I try to run HPLIP in the GUI (GNOME), it closes once it's opened. It remains open for less than a second. 2.Second, it does not recognize my printer. When I use the command-line tools it just simply does not recognize my printer. This is while the printer is recognized on the USB bus, I confirm it by using usbconfig. mail# uname -a FreeBSD mail.freebsdsystem.net 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jan 24 23:09:14 IRST 2011 r...@mail.freebsdsystem.net:/usr/obj/usr/src/sys/GENERIC i386 mail# usbconfig ugen0.1: EHCI root HUB Intel at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen1.1: EHCI root HUB Intel at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.2: product 0x0020 vendor 0x8087 at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.2: product 0x0020 vendor 0x8087 at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.3: Optical Mouse Genius at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen1.4: HID Keyboard Device vendor 0x0e6a at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen1.5: HP LaserJet Professional P1102 Hewlett-Packard at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON mail# Can you give me a little help? Has anyone ever managed to get this printer (HP P1102) working on FreeBSD? Good Luck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: HPLIP 3.10.9 problems on FreeBSD 8.1
2011-01-26 18:04, Bahman Kahinpour skrev: Hi FreeBSD people, I am trying to make my HP LaserJet P1102 work on FreeBSD 8.1 and towards that goal I installed HPLIP 3.10.9 from the Ports Collection. But there are two problems: 1.First, when I try to run HPLIP in the GUI (GNOME), it closes once it's opened. It remains open for less than a second. 2.Second, it does not recognize my printer. When I use the command-line tools it just simply does not recognize my printer. This is while the printer is recognized on the USB bus, I confirm it by using usbconfig. mail# uname -a FreeBSD mail.freebsdsystem.net 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jan 24 23:09:14 IRST 2011 r...@mail.freebsdsystem.net:/usr/obj/usr/src/sys/GENERIC i386 mail# usbconfig ugen0.1:EHCI root HUB Intel at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen1.1:EHCI root HUB Intel at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.2:product 0x0020 vendor 0x8087 at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.2:product 0x0020 vendor 0x8087 at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.3:Optical Mouse Genius at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen1.4:HID Keyboard Device vendor 0x0e6a at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen1.5:HP LaserJet Professional P1102 Hewlett-Packard at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON mail# Can you give me a little help? Has anyone ever managed to get this printer (HP P1102) working on FreeBSD? Good Luck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I've never used that specific printer, but the first thing that comes to mind is the lack of ulpt entries. Do you have device ulpt in your kernel config file, or ulpt_load=YES in your /boot/loader.conf ? If not, try one of them. Hm. I just checked the output of my usbconfig, and it also shows no ulpt, though I do have it. And I also checked the GENERIC config file, and it does include ulpt, at least for 8.2-PRERELEASE amd64. So, you may actually have it. But that's still the first thing I'd look for if I were you. Rolf Nielsen ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: HPLIP 3.10.9 problems on FreeBSD 8.1
On Wed, Jan 26, 2011 at 11:41 AM, Rolf Nielsen listrea...@lazlarlyricon.com wrote: I am trying to make my HP LaserJet P1102 work on FreeBSD 8.1 and towards that goal I installed HPLIP 3.10.9 from the Ports Collection. But there are two problems: 1.First, when I try to run HPLIP in the GUI (GNOME), it closes once it's opened. It remains open for less than a second. 2.Second, it does not recognize my printer. When I use the command-line tools it just simply does not recognize my printer. This is while the printer is recognized on the USB bus, I confirm it by using usbconfig. It seems to me hplip is in a lot of ways just an extension of CUPS. I've had mixed luck with hplip although not with your specific issue. I would try to run the hplip utility you're using from the command line to see where it is failing but you should be able to administer most functions from the cups web interface. I had one printer that was said to be supported which I spend approximately 6 months on and off trying to get to work and never did(the printer did work on a Mac, just not FreeBSD). After replacing it with a different model, it worked immediately and very smoothly. I have hplip installed at other locations and it works well. If not, try one of them. Hm. I just checked the output of my usbconfig, and it also shows no ulpt, though I do have it. And I also checked the GENERIC config file, and it does include ulpt, at least for 8.2-PRERELEASE amd64. So, you may actually have it. But that's still the first thing I'd look for if I were you. Easy way to check if module is in kernel is kldstat -v -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Lockup problems on FreeBSD disks
On Mon, Nov 16, 2009 at 06:39:15PM -0500, David Jackson wrote: I have a USB hard drive. Whenever I open two programs which utilise the USB hard drive simultaneously, these programs, i assume when they attempt to write to the hard drive lock up due to what i suspect must be snip This particular problem is one I haven't seen. But I've had problems with USB harddisks freezing when trying to write large files. It seems that not USB-ATA chipsets are created equal, and the 7.x USB stack seems to have problems with that. It seems most likely that this is a USB level problem involving the USB drivers. I am using FreeBSD 7.1. It is annoying behaviour to say the least and I wonder what can be done about it, Try 8.0-PRERELEASE. The USB stack has been rewritten for 8.x, and my limited testing so far indicates it to work better with quirky hardware. The problem of a panic when unplugging a mounted USB drive should also be fixed. And even if you still have problems with the 8.x USB stack, I suspect the USB stack in 8.x is more likely to receive TLC than the one in 7.x, so it would be best to check that out. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpiVipaJIKRi.pgp Description: PGP signature
Lockup problems on FreeBSD disks
I have a USB hard drive. Whenever I open two programs which utilise the USB hard drive simultaneously, these programs, i assume when they attempt to write to the hard drive lock up due to what i suspect must be some issue with the USB driver and perhaps a deadlock involving multiple concurrent accesses to the drive. When they attempt to access the drive the programs can lock up for several minutes before being unblocked. When only one program is using the drive this behaviour does not seem to occur. It seems most likely that this is a USB level problem involving the USB drivers. I am using FreeBSD 7.1. It is annoying behaviour to say the least and I wonder what can be done about it, and if this issue is being addressed, perhaps in the recent redesign of the USB code. It seems to be a pretty consistent issue, happening with multiple installs of FreeBSD and different drives. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with FreeBSD assembly
Mihai Don??u mihai.do...@gmail.com wrote: I don't think the kernel is the one that initializes the 0, 1 and 2 file descriptors (stdin, stdout and stderr). Correct so far. I think you have to open them yourself ... No, the shell does it. That's how it is able to set up pipes and redirection. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with FreeBSD assembly
Charlie Kester wrote: On Wed 11 Nov 2009 at 17:32:41 PST Charlie Kester wrote: One more thing: Notice that the system call number (or any other dword) should also be pushed onto the stack before the int 80h. The reason for this is given at the top of the page: although the kernel is accessed using int 80h, it is assumed the program will call a function that issues int 80h, rather than issuing int 80h directly. So the extra dword pushed onto the stack takes the place of the return address from the function the kernel expects to have been called. And since you're not actually using as a return address, it doesn't matter what value it actually has. The kernel doesn't use it for anything; it just expects it to be there in a properly arranged stack frame. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org The push eax is what made it work. So that was the problem. Stdin and stdout do not need to opened before they are used, as in C. Thank you everyone for your help on this, that solved it. Here is the code that works: section .data hello db 'Hello, World!', 0xa hbytes equ $ - hello section .text global _start _start: pushdword hbytes pushdword hello pushdword 1 mov eax,0x4 push eax int 0x80 add esp,16 pushdword 0 mov eax,0x1 push eax int 0x80 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with FreeBSD assembly
On Wed, 11 Nov 2009 14:43:21 -0500, David Jackson norsta...@gmail.com wrote: I am having great difficulty running a very simple assembler program on FreeBSD on x86 in my efforts to learn some assembly programming on FreeBSD. I have tried to compile the following with nasm, however i get nothing in response when I attempt to run this program: section .data hello db 'Hello, World!', 0xa hbytes equ $ - hello section .text global _start _start: pushdword hbytes pushdword hello pushdword 1 mov eax,0x4 int 0x80 add esp,12 pushdword 0 mov eax,0x1 int 0x80 nasm -f elf -o hello1s.o hello1.s ld -s -o hello1s hello1s.o ./hello1s prints nothing. What is wrong here? It should print hello world. Thanks in advance for your help, it is greatly appreciated. Hi David. The truss utility is your friend when you are trying to decipher system call problems. It can translate system call arguments to human-readable output; a very useful property when debugging issues like this. For example here's the output for your original code: $ truss ./hello write(134516904,0xe,1) ERR#9 'Bad file descriptor' process exit, rval = 1 Note how the arguments of write() are 'misplaced'? The answer is that you are not calling the system call with C-like conventions (including a function call return address). The calling conventions of system calls are described in the Developer's Handbook at: http://www.freebsd.org/doc/en/books/developers-handbook/x86-system-calls.html You are missing a dword push before interrupting. As the dev handbook says, you have to use C calling conventions or push an extra (ignorable) dword before interrupting: An assembly language program can do that as well. For example, we could open a file: | kernel: | int 80h ; Call kernel | ret | | open: | pushdword mode | pushdword flags | pushdword path | mov eax, 5 | callkernel | add esp, byte 12 | ret This is a very clean and portable way of coding. If you need to port the code to a UNIX system which uses a different interrupt, or a different way of passing parameters, all you need to change is the kernel procedure. But assembly language programmers like to shave off cycles. The above example requires a call/ret combination. We can eliminate it by pushing an extra dword: | open: | pushdword mode | pushdword flags | pushdword path | mov eax, 5 | pusheax ; Or any other dword | int 80h | add esp, byte 16 So by pushing *one* more dword before you interrupt should work fine (and it does, from a small test I ran just now): : keram...@kobe:/home/keramida$ cat hello.s : section .data : hello db 'Hello, World!', 0xa : hbytes equ $ - hello : : section .text : global _start : _start: : push dword hbytes : push dword hello : push dword 1 : push dword 0 ;or any other dword : mov eax, 4 : int 0x80 : add esp, byte 16 : : push dword 0 : push dword 0 ;ignored dword : mov eax, 1 : int 0x80 : add esp, byte 8 ;NOT REACHED : keram...@kobe:/home/keramida$ nasm -f elf -o hello.o hello.s : keram...@kobe:/home/keramida$ ld -s -o hello hello.o : keram...@kobe:/home/keramida$ truss ./hello : Hello, World! : write(1,Hello, World!\n,14)= 14 (0xe) : process exit, rval = 0 : keram...@kobe:/home/keramida$ HTH, Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Problems with FreeBSD assembly
I am having great difficulty running a very simple assembler program on FreeBSD on x86 in my efforts to learn some assembly programming on FreeBSD. I have tried to compile the following with nasm, however i get nothing in response when I attempt to run this program: section .data hello db 'Hello, World!', 0xa hbytes equ $ - hello section .text global _start _start: pushdword hbytes pushdword hello pushdword 1 mov eax,0x4 int 0x80 add esp,12 pushdword 0 mov eax,0x1 int 0x80 nasm -f elf -o hello1s.o hello1.s ld -s -o hello1s hello1s.o ./hello1s prints nothing. What is wrong here? It should print hello world. Thanks in advance for your help, it is greatly appreciated. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Problems with freebsd assembly
I am having great difficulty running a very simple assembler program on FreeBSD on x86 in my efforts to learn some assembly programming on FreeBSD. I have tried to compile the following with nasm, however i get nothing in response when I attempt to run this program: section .data hello db 'Hello, World!', 0xa hbytes equ $ - hello section .text global _start _start: pushdword hbytes pushdword hello pushdword 1 mov eax,0x4 int 0x80 add esp,12 pushdword 0 mov eax,0x1 int 0x80 nasm -f elf -o hello1s.o hello1.s ld -s -o hello1s hello1s.o ./hello1s prints nothing. What is wrong here? It should print hello world. Thanks in advance for your help, it is greatly appreciated. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with FreeBSD assembly
On Wednesday 11 November 2009 21:43:21 David Jackson wrote: I am having great difficulty running a very simple assembler program on FreeBSD on x86 in my efforts to learn some assembly programming on FreeBSD. I have tried to compile the following with nasm, however i get nothing in response when I attempt to run this program: section .data hello db 'Hello, World!', 0xa hbytes equ $ - hello section .text global _start _start: pushdword hbytes pushdword hello pushdword 1 mov eax,0x4 int 0x80 add esp,12 pushdword 0 mov eax,0x1 int 0x80 nasm -f elf -o hello1s.o hello1.s ld -s -o hello1s hello1s.o ./hello1s prints nothing. I don't think the kernel is the one that initializes the 0, 1 and 2 file descriptors (stdin, stdout and stderr). I think you have to open them yourself. I will know for sure when my nasm port finishes installing. :) -- Mihai Donțu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with FreeBSD assembly
On Wed 11 Nov 2009 at 11:43:21 PST David Jackson wrote: I am having great difficulty running a very simple assembler program on FreeBSD on x86 in my efforts to learn some assembly programming on FreeBSD. I have tried to compile the following with nasm, however i get nothing in response when I attempt to run this program: section .data hello db 'Hello, World!', 0xa hbytes equ $ - hello section .text global _start _start: pushdword hbytes pushdword hello pushdword 1 mov eax,0x4 int 0x80 add esp,12 pushdword 0 mov eax,0x1 int 0x80 nasm -f elf -o hello1s.o hello1.s ld -s -o hello1s hello1s.o ./hello1s prints nothing. What is wrong here? It should print hello world. Thanks in advance for your help, it is greatly appreciated. http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/x86.html You've seen this part of the handbook, yes? In particular: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/x86-system-calls.html Calling your attention to the example code shown just before section 11.3.2, which shows how to open a file: open: pushdword mode pushdword flags pushdword path mov eax, 5 pusheax ; Or any other dword int 80h add esp, byte 16 Notice that the system call number (or any other dword) should also be pushed onto the stack before the int 80h. So try this: pushdword hbytes pushdword hello pushdword 1 ; stdout mov eax,0x4 pusheax ; or any other dword int 0x80 add esp,16 ; don't forget to account for the extra dword! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with FreeBSD assembly
On Wed 11 Nov 2009 at 17:32:41 PST Charlie Kester wrote: One more thing: Notice that the system call number (or any other dword) should also be pushed onto the stack before the int 80h. The reason for this is given at the top of the page: although the kernel is accessed using int 80h, it is assumed the program will call a function that issues int 80h, rather than issuing int 80h directly. So the extra dword pushed onto the stack takes the place of the return address from the function the kernel expects to have been called. And since you're not actually using as a return address, it doesn't matter what value it actually has. The kernel doesn't use it for anything; it just expects it to be there in a properly arranged stack frame. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with FreeBSD installation
On Thu, Aug 6, 2009 at 1:47 AM, Mel Flynnmel.flynn+fbsd.questi...@mailing.thruhere.net wrote: Your best bet is to poll the mobile list (CC'd) to see if anyone was able to get FreeBSD working on this laptop (or even to know whether this is a lost cause till somebody makes some patches for this laptop). Since 7.2 also does not work and with 8.0-RELEASE being in it's final stages, it's unlikely you can get some priority from the developers for it being a regression bug. The acpi and missing disk can be related (most likely are), but unless you get at least a live FS working (even the USB image for 8.0-BETA2) it will be hard to get an acpidump(8). So this really depends on someone knowledgeable having this laptop or BIOS tricks that get you to a stage where more info can be gathered and saved/snapshot. Ok, I understand chances to have it running in the short term are not high :-) Anyway, and since I am replying to the mobile list, I am available to provide more information about the laptop. I have Linux running on it and I believe there is something similar to the acpidump (not sure if its the same tool as in FreeBSD or if their outputs are compatible) that I could use to provide some more details. Regards, Miguel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with FreeBSD installation
On Thu, Aug 6, 2009 at 7:16 PM, Ben Fallonbfal...@itbuildersinc.com wrote: Might want to take a look at this page as it may provide a bit more insight. The problem isn't with the Machine specifically but with the ATI Sata Controller/Chipset. Not sure if this has been fixed yet. http://www.mavetju.org/mail/view_message.php?list=freebsd-currentid=2740699 Uau! That's exactly the same problem with the same hardware, and I would be tempted to say that it _has not_ been solved yet. I'll try to contact those guys to try to get some more information. Thanks a lot for the pointer, Ben. Regards, Miguel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Problems with FreeBSD installation
Might want to take a look at this page as it may provide a bit more insight. The problem isn't with the Machine specifically but with the ATI Sata Controller/Chipset. Not sure if this has been fixed yet. http://www.mavetju.org/mail/view_message.php?list=freebsd-currentid=2740699 -Original Message- From: Miguel [mailto:luis.hen...@gmail.com] Sent: Thursday, August 06, 2009 1:53 PM To: Ben Fallon Cc: freebsd-mob...@freebsd.org; freebsd-questions@freebsd.org Subject: Re: Problems with FreeBSD installation On Thu, Aug 6, 2009 at 2:25 PM, Ben Fallonbfal...@itbuildersinc.com wrote: What model of laptop is it? I just subscribed to the list yesterday and may have missed the beginning of this thread. You can also check here http://laptop.bsdgroup.de/freebsd/ It provides details for a bunch of laptops and what the findings were for the models they tested. On Linux, a simple dmesg will help on seeing what devices were found by your os otherwise, like BSD, the lspci also works the same. Sorry I can't help more without a bit more information. The complete thread can be read here: http://lists.freebsd.org/pipermail/freebsd-questions/2009-August/203491.html My laptop is a Toshiba Satellite A210-1CE, and I am attaching the information you requested: the output from lspci -v and dmesg. Hope it helps :-) Regards, Miguel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Problems with FreeBSD installation
Hi, I've been trying to install FreeBSD in my laptop, but without success. I started with 7.2, but during installation i got the error: No disk found! Please verify that your disk controller... Looking at the logs, everything seems fine to me (although its my first time on the FreeBSD world). I get lines such as: atapci0: ATI IXP600 SATA300 controller [...] atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 4 ports detected ata2: ATA channel 0 on atapci0 ata2: [ITHREAD] ata3: ATA channel 1 on atapci0 ata3: [ITHREAD] ata4: ATA channel 2 on atapci0 ata4: [ITHREAD] ata5: ATA channel 3 on atapci0 ata5: [ITHREAD] [...] atapci1: ATI IPX600 UDMA 133 controller [...] ata0: ATA channel 0 on atapci1 ata0: [ITHREAD] [...] (Note that i wrote these logs manually -- got some photos that I can upload to some URL if needed.) So, could not find any issues in the logs, apart from some ACPI errors: acpi0_check: nexus0 attached acpi0_check: acpi0 not-present acpi0_check: acpi0 not-present acpi0_check: acpi0 not-present acpi0_check: acpi0 not-present ... in fact, I have some other ACPI-related errors at the beginning of the logs, but these are common also on Linux -- I believe these are due to a buggy BIOS, which unfortunately I am not able to upgrade since I have not windows installed (I have a Toshiba Satellite A210). Anyway, I decided to try a more recent version of FreeBSD and downloaded 8.0-CURRENT-200906-amd64-disc1.iso which was the most recent snapshot for my Turion64 processor. Tried to boot it but this time the installation just freeze before the install application event starts. Last log lines are: acpi0: Could not initialise SystemIO handler: AE_NOT_EXIST device_attach: acpi0 attach returned 6 Timecounters tick every 1.000 msec md0: Preload image /boot/mfsroot 4194304 bytes at 0x80fd8660 SMP: AP CPU #1 Launched! WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/md0 warning: no time-of-day clock registered, system time will not be set accurately And at this point... nothing else -- system freezes. Please let me know if anyone has any suggestions for me to have a FreeBSD installation on my laptop. I am, of course, available to provide any additional information you might need to debug the issue. Thanks! -- Miguel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with FreeBSD installation
On Wed, Aug 5, 2009 at 5:01 PM, Miguelluis.hen...@gmail.com wrote: Hi, I've been trying to install FreeBSD in my laptop, but without success. I started with 7.2, but during installation i got the error: No disk found! Please verify that your disk controller... Looking at the logs, everything seems fine to me (although its my first time on the FreeBSD world). I get lines such as: atapci0: ATI IXP600 SATA300 controller [...] atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 4 ports detected ata2: ATA channel 0 on atapci0 ata2: [ITHREAD] ata3: ATA channel 1 on atapci0 ata3: [ITHREAD] ata4: ATA channel 2 on atapci0 ata4: [ITHREAD] ata5: ATA channel 3 on atapci0 ata5: [ITHREAD] [...] atapci1: ATI IPX600 UDMA 133 controller [...] ata0: ATA channel 0 on atapci1 ata0: [ITHREAD] [...] (Note that i wrote these logs manually -- got some photos that I can upload to some URL if needed.) So, could not find any issues in the logs, apart from some ACPI errors: acpi0_check: nexus0 attached acpi0_check: acpi0 not-present acpi0_check: acpi0 not-present acpi0_check: acpi0 not-present acpi0_check: acpi0 not-present ... in fact, I have some other ACPI-related errors at the beginning of the logs, but these are common also on Linux -- I believe these are due to a buggy BIOS, which unfortunately I am not able to upgrade since I have not windows installed (I have a Toshiba Satellite A210). [snip] acpi0: Could not initialise SystemIO handler: AE_NOT_EXIST device_attach: acpi0 attach returned 6 Timecounters tick every 1.000 msec md0: Preload image /boot/mfsroot 4194304 bytes at 0x80fd8660 SMP: AP CPU #1 Launched! WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/md0 warning: no time-of-day clock registered, system time will not be set accurately And at this point... nothing else -- system freezes. Please let me know if anyone has any suggestions for me to have a FreeBSD installation on my laptop. I am, of course, available to provide any additional information you might need to debug the issue. Can you try booting with ACPI disabled? It should be option 2 from the loader menu. -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with FreeBSD installation
Hi Glen, On Wed, Aug 5, 2009 at 10:33 PM, Glen Barberglen.j.bar...@gmail.com wrote: On Wed, Aug 5, 2009 at 5:01 PM, Miguelluis.hen...@gmail.com wrote: Hi, I've been trying to install FreeBSD in my laptop, but without success. I started with 7.2, but during installation i got the error: No disk found! Please verify that your disk controller... Looking at the logs, everything seems fine to me (although its my first time on the FreeBSD world). I get lines such as: atapci0: ATI IXP600 SATA300 controller [...] atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 4 ports detected ata2: ATA channel 0 on atapci0 ata2: [ITHREAD] ata3: ATA channel 1 on atapci0 ata3: [ITHREAD] ata4: ATA channel 2 on atapci0 ata4: [ITHREAD] ata5: ATA channel 3 on atapci0 ata5: [ITHREAD] [...] atapci1: ATI IPX600 UDMA 133 controller [...] ata0: ATA channel 0 on atapci1 ata0: [ITHREAD] [...] (Note that i wrote these logs manually -- got some photos that I can upload to some URL if needed.) So, could not find any issues in the logs, apart from some ACPI errors: acpi0_check: nexus0 attached acpi0_check: acpi0 not-present acpi0_check: acpi0 not-present acpi0_check: acpi0 not-present acpi0_check: acpi0 not-present ... in fact, I have some other ACPI-related errors at the beginning of the logs, but these are common also on Linux -- I believe these are due to a buggy BIOS, which unfortunately I am not able to upgrade since I have not windows installed (I have a Toshiba Satellite A210). [snip] acpi0: Could not initialise SystemIO handler: AE_NOT_EXIST device_attach: acpi0 attach returned 6 Timecounters tick every 1.000 msec md0: Preload image /boot/mfsroot 4194304 bytes at 0x80fd8660 SMP: AP CPU #1 Launched! WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/md0 warning: no time-of-day clock registered, system time will not be set accurately And at this point... nothing else -- system freezes. Please let me know if anyone has any suggestions for me to have a FreeBSD installation on my laptop. I am, of course, available to provide any additional information you might need to debug the issue. Can you try booting with ACPI disabled? It should be option 2 from the loader menu. Yes, I tried that already with same results. Regards, Miguel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with FreeBSD installation
On Wed, Aug 5, 2009 at 5:35 PM, Miguelluis.hen...@gmail.com wrote: Hi Glen, Can you try booting with ACPI disabled? It should be option 2 from the loader menu. Yes, I tried that already with same results. Can you try the installation media on another machine (to rule out a bad CD or bad burn)? Also, is it possible to upgrade the BIOS on the problem machine? -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with FreeBSD installation
On Wed, Aug 5, 2009 at 10:37 PM, Glen Barberglen.j.bar...@gmail.com wrote: On Wed, Aug 5, 2009 at 5:35 PM, Miguelluis.hen...@gmail.com wrote: Hi Glen, Can you try booting with ACPI disabled? It should be option 2 from the loader menu. Yes, I tried that already with same results. Can you try the installation media on another machine (to rule out a bad CD or bad burn)? The CD image seems to be fine (both of them): I have installed them on a Linux kvm virtual machine and there were no problems -- both are able to do the complete installation and I am able to boot the resulting image. (Sorry, no other physical machines available at the moment.) Also, is it possible to upgrade the BIOS on the problem machine? I would love to upgrade my BIOS but I am unable to do that -- I have not Windows installed and my vendor requires Windows to be installed in order to perform the upgrade (yes, I know! I will never buy another laptop from them!) I have not tried 8.0-BETA (as someone on the IRC channel suggested) but not sure if it will make any difference. As far as I understand, the snapshot I tried is more recent than 8.0-BETA2. Or am I wrong? Is it worth downloading one more ISO just to try it? Regards, Miguel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with FreeBSD installation
On Wed, Aug 5, 2009 at 5:45 PM, Miguelluis.hen...@gmail.com wrote: On Wed, Aug 5, 2009 at 10:37 PM, Glen Barberglen.j.bar...@gmail.com wrote: On Wed, Aug 5, 2009 at 5:35 PM, Miguelluis.hen...@gmail.com wrote: Hi Glen, Can you try booting with ACPI disabled? It should be option 2 from the loader menu. Yes, I tried that already with same results. Can you try the installation media on another machine (to rule out a bad CD or bad burn)? The CD image seems to be fine (both of them): I have installed them on a Linux kvm virtual machine and there were no problems -- both are able to do the complete installation and I am able to boot the resulting image. (Sorry, no other physical machines available at the moment.) That's fine. At least you know the media / image are working. Also, is it possible to upgrade the BIOS on the problem machine? I would love to upgrade my BIOS but I am unable to do that -- I have not Windows installed and my vendor requires Windows to be installed in order to perform the upgrade (yes, I know! I will never buy another laptop from them!) No comment. :-) I have not tried 8.0-BETA (as someone on the IRC channel suggested) but not sure if it will make any difference. As far as I understand, the snapshot I tried is more recent than 8.0-BETA2. Or am I wrong? Is it worth downloading one more ISO just to try it? The -BETA, -BETA1, -BETA2 images are run the same way -RELEASE images are -- once the image is released, there are no further updates to it. That is why when you download a -RELEASE, any patches that may have been released afterwards are not reflected in the install image. For what it's worth, I tried the -BETA2 image on my laptop, and the ndis driver was causing panics. I used 7.2-RELEASE to install the OS, and rebuilt world/kernel from my build machine using NFS, and the panics went away. After rereading your original question, you were using a -CURRENT snapshot to install -- -BETA2 was released a few weeks ago. It may have the problem fixed, yes, but it is not guaranteed. To answer your question, is it worth downloading...: that depends. If you're willing to waste another CD if it fails, is up to you, but your problem may be fixed in -BETA2. -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with FreeBSD installation
On Wed, Aug 5, 2009 at 10:52 PM, Glen Barberglen.j.bar...@gmail.com wrote: I have not tried 8.0-BETA (as someone on the IRC channel suggested) but not sure if it will make any difference. As far as I understand, the snapshot I tried is more recent than 8.0-BETA2. Or am I wrong? Is it worth downloading one more ISO just to try it? The -BETA, -BETA1, -BETA2 images are run the same way -RELEASE images are -- once the image is released, there are no further updates to it. That is why when you download a -RELEASE, any patches that may have been released afterwards are not reflected in the install image. For what it's worth, I tried the -BETA2 image on my laptop, and the ndis driver was causing panics. I used 7.2-RELEASE to install the OS, and rebuilt world/kernel from my build machine using NFS, and the panics went away. After rereading your original question, you were using a -CURRENT snapshot to install -- -BETA2 was released a few weeks ago. It may have the problem fixed, yes, but it is not guaranteed. To answer your question, is it worth downloading...: that depends. If you're willing to waste another CD if it fails, is up to you, but your problem may be fixed in -BETA2. Yes, I understand -- just realised that BETA2 is more recent than the snapshot I tried. Most probably, I'll just wait until 8.0 is actually released. My problem with trying BETA2 is that it will take long time to get it (slow connection here) and most probably my problem will remain. Isn't there a way (an easy way, I mean!) to get a custom kernel from freebsd.org that I could replace in my ISO? Regards, Miguel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with FreeBSD installation
On Wed, Aug 5, 2009 at 6:10 PM, Miguelluis.hen...@gmail.com wrote: Yes, I understand -- just realised that BETA2 is more recent than the snapshot I tried. Most probably, I'll just wait until 8.0 is actually released. My problem with trying BETA2 is that it will take long time to get it (slow connection here) and most probably my problem will remain. Possible that it will remain - more probable that it has been fixed though. Isn't there a way (an easy way, I mean!) to get a custom kernel from freebsd.org that I could replace in my ISO? Not that I am aware of. -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with FreeBSD installation
On Wed, Aug 5, 2009 at 11:48 PM, Glen Barberglen.j.bar...@gmail.com wrote: On Wed, Aug 5, 2009 at 6:10 PM, Miguelluis.hen...@gmail.com wrote: Yes, I understand -- just realised that BETA2 is more recent than the snapshot I tried. Most probably, I'll just wait until 8.0 is actually released. My problem with trying BETA2 is that it will take long time to get it (slow connection here) and most probably my problem will remain. Possible that it will remain - more probable that it has been fixed though. Hmm... Ok, I will try it then. Not sure if I am able to do this today, but I try it. Isn't there a way (an easy way, I mean!) to get a custom kernel from freebsd.org that I could replace in my ISO? Not that I am aware of. Right, I could not find it too. Regards, Miguel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with FreeBSD installation
On Wed, Aug 5, 2009 at 11:48 PM, Glen Barberglen.j.bar...@gmail.com wrote: On Wed, Aug 5, 2009 at 6:10 PM, Miguelluis.hen...@gmail.com wrote: Yes, I understand -- just realised that BETA2 is more recent than the snapshot I tried. Most probably, I'll just wait until 8.0 is actually released. My problem with trying BETA2 is that it will take long time to get it (slow connection here) and most probably my problem will remain. Possible that it will remain - more probable that it has been fixed though. Ok, some updates: I downloaded 8.0-BETA2 ISO and the result was exactly the same, i.e., system freezes during CD boot in the same point as before. This time I did not actually tried to install the CD on a virtual machine, but I can not believe it is a problem with the CD image ;-) This time I disabled _everything_ I could disable in my BIOS and selected several options from the boot manager: the default option, the option with ACPI disabled, the option safe-mode (or something like that...) and finally the verbose option, which gave me some more information. Here's the last messages I see in the console before freeze: start_init: trying /sbin/init start_init: trying /sbin/oinit start_init: trying /sbin/init.bak start_init: trying /rescue/init start_init: trying /stand/sysinstall And that's all. Any ideas? :-( Regards, Miguel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with FreeBSD installation
On Wednesday 05 August 2009 13:01:30 Miguel wrote: Hi, I've been trying to install FreeBSD in my laptop, but without success. I started with 7.2, but during installation i got the error: No disk found! Please verify that your disk controller... Looking at the logs, everything seems fine to me (although its my first time on the FreeBSD world). I get lines such as: atapci0: ATI IXP600 SATA300 controller [...] atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 4 ports detected ata2: ATA channel 0 on atapci0 ata2: [ITHREAD] ata3: ATA channel 1 on atapci0 ata3: [ITHREAD] ata4: ATA channel 2 on atapci0 ata4: [ITHREAD] ata5: ATA channel 3 on atapci0 ata5: [ITHREAD] [...] atapci1: ATI IPX600 UDMA 133 controller [...] ata0: ATA channel 0 on atapci1 ata0: [ITHREAD] [...] (Note that i wrote these logs manually -- got some photos that I can upload to some URL if needed.) So, could not find any issues in the logs, apart from some ACPI errors: acpi0_check: nexus0 attached acpi0_check: acpi0 not-present acpi0_check: acpi0 not-present acpi0_check: acpi0 not-present acpi0_check: acpi0 not-present ... in fact, I have some other ACPI-related errors at the beginning of the logs, but these are common also on Linux -- I believe these are due to a buggy BIOS, which unfortunately I am not able to upgrade since I have not windows installed (I have a Toshiba Satellite A210). Anyway, I decided to try a more recent version of FreeBSD and downloaded 8.0-CURRENT-200906-amd64-disc1.iso which was the most recent snapshot for my Turion64 processor. Tried to boot it but this time the installation just freeze before the install application event starts. Last log lines are: acpi0: Could not initialise SystemIO handler: AE_NOT_EXIST device_attach: acpi0 attach returned 6 Timecounters tick every 1.000 msec md0: Preload image /boot/mfsroot 4194304 bytes at 0x80fd8660 SMP: AP CPU #1 Launched! WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/md0 warning: no time-of-day clock registered, system time will not be set accurately And at this point... nothing else -- system freezes. Please let me know if anyone has any suggestions for me to have a FreeBSD installation on my laptop. I am, of course, available to provide any additional information you might need to debug the issue. Your best bet is to poll the mobile list (CC'd) to see if anyone was able to get FreeBSD working on this laptop (or even to know whether this is a lost cause till somebody makes some patches for this laptop). Since 7.2 also does not work and with 8.0-RELEASE being in it's final stages, it's unlikely you can get some priority from the developers for it being a regression bug. The acpi and missing disk can be related (most likely are), but unless you get at least a live FS working (even the USB image for 8.0-BETA2) it will be hard to get an acpidump(8). So this really depends on someone knowledgeable having this laptop or BIOS tricks that get you to a stage where more info can be gathered and saved/snapshot. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Problems with FreeBSD 8-CURRENT as Xen domU
hi... I've managed to compile and setup a paravirtualized domU with FreeBSD 8 (SVN snapshot from 'head'). Currently I'm running into two mayor problems: - The system time is not behaving as expected. Example: I fired the domain up at 01:43 in the morning and watch the clock. Time passes normally within the maschine, and the suddenly jumps back to 01:30:VARIES. From there on time passes normally up to 15 minutes (the latest time I've seen is 01:44:52). Right now the domain is running for more than 18 hours, and the clock still says: Tue Jan 13 01:32:52 CET 2009 Running 'ntpd' inside the domU doesn't help to solve the problem. If found a lot of hints for linux domU's, which say that you need to set the sysctl 'xen.independent_wallclock' to '1' and run 'ntpd' in the domU to keep time correct. Does 'sysctl machdep.independent_wallclock=1' the same in FreeBSD? (If so, this doesn' work.) - 2-way SMP doesn't work. When I put the line vcpus=2 into my config file, I get the following output during boot, and the domU is destroyed after the reboot by the kernel: # xm create 00_template_8-CURRENT.XENconfig -c Using config file ./00_template_8-CURRENT.XENconfig. Started domain template_8-CURRENT WARNING: loader(8) metadata is missing! Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-CURRENT #3: Thu Jan 8 04:34:03 CET 2009 r...@template-8_current.localdomain:/usr/obj/usr/src/sys/freebsd8_XEN WARNING: WITNESS option enabled, expect reduced performance. Xen reported: 1600.056 MHz processor. Timecounter ixen frequency 10 Hz quality 0 CPU: AMD Athlon(tm) Processor (1600.06-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x662 Stepping = 2 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc0480800SYSCALL,MP,MMX+,3DNow!+,3DNow! real memory = 671088640 (640 MB) avail memory = 649625600 (619 MB) gdtpfn=3edd9 pdptpfn=3 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu=0 irq=0 vector=0 cpu=0 irq=0 vector=1 cpu=1 irq=0 vector=0 cpu=1 irq=0 vector=1 kbd0 at kbdmux0 xenbus0: Xen Devices on motherboard xc0: Xen Console on motherboard Timecounters tick every 10.000 msec xbd0: 8192MB Virtual Block Device at device/vbd/768 on xenbus0 xbd0: attaching as ad0 GEOM: ad0s1: geometry does not match label (15h,63s != 255h,63s). xn0: Virtual Network Interface at device/vif/0 on xenbus0 xn0: Ethernet address: 00:16:3e:06:c3:80 [XEN] netfront_backend_changed: newstate=2 Spanic: blockable sleep lock (sleep mutex) XCONS LOCK @ /usr/src/sys/dev/xen/console/console.c:290 cpuid = 1 Uptime: 1s Cannot dump. Device not defined or unavailable. Automatic reboot in 15 seconds - press a key on the console to abort -- Press a key on the console to reboot, -- or switch off the system now. Rebooting... I've attached my kernelconfig file to this mail, if someone sees a failure in it. Any hints on how to solve these 2 problems would be really great. Using FreeBSD in it's current state as domU really rocks. :-))) greetz olli # # XEN -- Kernel configuration for i386 XEN DomU # # $FreeBSD$ cpu I686_CPU ident XEN makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols makeoptions MODULES_OVERRIDE= options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption #optionsSCHED_4BSD options INET# InterNETworking #optionsINET6 # IPv6 communications protocols #optionsSCTP# Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories #optionsUFS_GJOURNAL# Enable gjournal-based UFS journaling #optionsNFSCLIENT # Network Filesystem Client #optionsNFSSERVER # Network Filesystem Server #optionsNFSLOCKD# Network Lock Manager #optionsNFS_ROOT# NFS usable as /, requires NFSCLIENT #optionsMSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660
Re: Problems installing FreeBSD 7.0
From: SDH Admin ad...@stardothosting.com How can I do this if the systeem freezes??? Good old fashioned pen + paper (as long as it's not too long). Never fails. Main problem is: ad0: FreeBSD check1 failed I googled but didn't find any solution. Does anyone have a clue where to find the solution? Jack ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems installing FreeBSD 7.0
Jack Raats j...@jarasoft.net writes: From: SDH Admin ad...@stardothosting.com How can I do this if the systeem freezes??? Good old fashioned pen + paper (as long as it's not too long). Never fails. Main problem is: ad0: FreeBSD check1 failed I googled but didn't find any solution. Does anyone have a clue where to find the solution? According to my quick look at the code, that message isn't necessarily a hint to the problem. Do you have a RAID array in the machine? -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems installing FreeBSD 7.0
On 2008-Dec-24 17:29:05 +0100, Jack Raats j...@jarasoft.net wrote: Main problem is: ad0: FreeBSD check1 failed This is produced when the ATA subsystem is trying to read RAID metadata off the disk and just means it failed to find any. It's not an error. Can you post more context please. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgpTdruFiT2UV.pgp Description: PGP signature
Re: Problems installing FreeBSD 7.0
On 2008-Dec-23 20:32:38 +0100, Jack Raats j...@jarasoft.net wrote: Can you try to paste exactly what was on the screen before the freeze for both 6.4 and 7.0? How can I do this if the systeem freezes??? Take a photo and put it up somewhere (http://imagebin.ca/ if nowhere else). If scroll lock still works, you can take pictures of earlier output (and if caps/scroll/num lock don't work, that is a useful piece of information). -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. pgp7MuaXmUzVi.pgp Description: PGP signature
Problems installing FreeBSD 7.0
Hi, At this moment I have problems installing FreeBSD 6.4 and FreeBSD 7.0. After booting from CD the system I get the menu. I have tried all possible options. The system starts checking all hardware but freezes after finding the CD-ROM drives printing the GEOM_LABLE (on FB 7.0, not 6.4) (acd0) The hardware is a Targa Visonary 2700XP, AMD 2700+ CPU, mem 1 GB Can anyone help me. I never had this problems before on other systems. Thanks Jack ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems installing FreeBSD 7.0
On Tue, Dec 23, 2008 at 1:30 PM, Jack Raats j...@jarasoft.net wrote: Hi, At this moment I have problems installing FreeBSD 6.4 and FreeBSD 7.0. After booting from CD the system I get the menu. I have tried all possible options. The system starts checking all hardware but freezes after finding the CD-ROM drives printing the GEOM_LABLE (on FB 7.0, not 6.4) (acd0) The hardware is a Targa Visonary 2700XP, AMD 2700+ CPU, mem 1 GB Can anyone help me. I never had this problems before on other systems. Have you tried disabling DMA or ACPI? hw.ata.ata_dma=0 -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems installing FreeBSD 7.0
- Original Message - From: SDH Admin ad...@stardothosting.com The system starts checking all hardware but freezes after finding the CD-ROM drives printing the GEOM_LABLE (on FB 7.0, not 6.4) (acd0) The hardware is a Targa Visonary 2700XP, AMD 2700+ CPU, mem 1 GB Can you try to paste exactly what was on the screen before the freeze for both 6.4 and 7.0? How can I do this if the systeem freezes??? Jack ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Problems installing FreeBSD 7.0
The system starts checking all hardware but freezes after finding the CD-ROM drives printing the GEOM_LABLE (on FB 7.0, not 6.4) (acd0) The hardware is a Targa Visonary 2700XP, AMD 2700+ CPU, mem 1 GB Can you try to paste exactly what was on the screen before the freeze for both 6.4 and 7.0? Thanks. --- Kevin K. Systems Administrator www.stardothosting.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Problems installing FreeBSD 7.0
How can I do this if the systeem freezes??? Good old fashioned pen + paper (as long as it's not too long). Never fails. --- Kevin K. Systems Administrator www.stardothosting.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problems with FreeBSD
On Tue, 4 Nov 2008 11:10:25 -0200, J MPZ [EMAIL PROTECTED] wrote:
Hi Paul,
When my connections freeze, I open the tcpdump in other terminal. If I type
something, type Enter, on the terminal frozen, the tcpdump show packets,
like that:
11:18:45.526256 IP (tos 0x0, ttl 51, id 651, offset 0, flags [DF], proto:
TCP (6), length: 112) 189.21.230.195.20787 201.57.5.2.2264: P 193:241(48)
ack 0 win 15136 nop,nop,timestamp 1556398494 745829191,nop,nop,sack 1
{1428:1664}
[...]
I'm using: tcpdump -nvvv -i ste0 host REMOTE_IP
Can you try capturing the connection setup packets, so we can look at
the TCP MSS negotiation values? Starting TCPDUMP *before* one of the
connections that stall is made should capture that.
There may be an intermediate router or firewall that blocks ICMP and
ends up breaking path MTU discovery. I've seen TCP connections
'stall' when path-mtu was broken by a setup like this and one of the
intermediate routers started dropping TCP packets that were too large
for one of its interfaces.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with FreeBSD
Jeremy, 2008/11/4, Jeremy Chadwick [EMAIL PROTECTED]: On Tue, Nov 04, 2008 at 11:11:15AM -0200, J MPZ wrote: Hi Jeremy, I tried without none rules on ipfw FreeBSD (just allow ip from any to any) and error continues occurring. Then I have no idea. How I can disable the TCP extensions? I tried to set this value on this sysctl (sysctl net.inet.tcp.rfc1323=0) but not work. Setting the sysctl to 0 disables TCP extesnsions. But by not work do you mean it didn't solve the problem, or setting the sysctl failed? I think you mean it didn't solve the problem, in which case, it's not the source of the problem. It didn't solve the problem. :-/ -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with FreeBSD
On Tue, Nov 04, 2008 at 11:11:15AM -0200, J MPZ wrote: Hi Jeremy, I tried without none rules on ipfw FreeBSD (just allow ip from any to any) and error continues occurring. Then I have no idea. How I can disable the TCP extensions? I tried to set this value on this sysctl (sysctl net.inet.tcp.rfc1323=0) but not work. Setting the sysctl to 0 disables TCP extesnsions. But by not work do you mean it didn't solve the problem, or setting the sysctl failed? I think you mean it didn't solve the problem, in which case, it's not the source of the problem. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with FreeBSD
Hi Paul,
When my connections freeze, I open the tcpdump in other terminal. If I type
something, type Enter, on the terminal frozen, the tcpdump show packets,
like that:
11:18:45.526256 IP (tos 0x0, ttl 51, id 651, offset 0, flags [DF], proto:
TCP (6), length: 112) 189.21.230.195.20787 201.57.5.2.2264: P 193:241(48)
ack 0 win 15136 nop,nop,timestamp 1556398494 745829191,nop,nop,sack 1
{1428:1664}
11:18:45.625839 IP (tos 0x10, ttl 64, id 23438, offset 0, flags [DF],
proto: TCP (6), length: 52) 201.57.5.2.2264 189.21.230.195.20787: ., cksum
0x4d03 (correct), 1664:1664(0) ack 241 win 65535 nop,nop,timestamp
745898173 1556398494
11:18:45.707825 IP (tos 0x0, ttl 51, id 652, offset 0, flags [DF], proto:
TCP (6), length: 112) 189.21.230.195.20787 201.57.5.2.2264: P 241:289(48)
ack 0 win 15136 nop,nop,timestamp 1556398704 745829191,nop,nop,sack 1
{1428:1664}
11:18:45.807839 IP (tos 0x10, ttl 64, id 23493, offset 0, flags [DF],
proto: TCP (6), length: 52) 201.57.5.2.2264 189.21.230.195.20787: ., cksum
0x4b4b (correct), 1664:1664(0) ack 289 win 65535 nop,nop,timestamp
745898355 1556398704
11:18:45.867181 IP (tos 0x0, ttl 51, id 653, offset 0, flags [DF], proto:
TCP (6), length: 112) 189.21.230.195.20787 201.57.5.2.2264: P 289:337(48)
ack 0 win 15136 nop,nop,timestamp 1556398903 745829191,nop,nop,sack 1
{1428:1664}
11:18:45.966840 IP (tos 0x10, ttl 64, id 23529, offset 0, flags [DF],
proto: TCP (6), length: 52) 201.57.5.2.2264 189.21.230.195.20787: ., cksum
0x49b5 (correct), 1664:1664(0) ack 337 win 65535 nop,nop,timestamp
745898514 1556398903
When I executed 'ls' on the terminal frozen, returns this on tcpdump:
11:19:35.738788 IP (tos 0x0, ttl 51, id 654, offset 0, flags [DF], proto:
TCP (6), length: 112) 189.21.230.195.20787 201.57.5.2.2264: P 337:385(48)
ack 0 win 15136 nop,nop,timestamp 1556448796 745829191,nop,nop,sack 1
{1428:1664}
11:19:35.788428 IP (tos 0x0, ttl 51, id 655, offset 0, flags [DF], proto:
TCP (6), length: 112) 189.21.230.195.20787 201.57.5.2.2264: P 385:433(48)
ack 0 win 15136 nop,nop,timestamp 1556448891 745829191,nop,nop,sack 1
{1428:1664}
11:19:35.788483 IP (tos 0x10, ttl 64, id 34519, offset 0, flags [DF],
proto: TCP (6), length: 52) 201.57.5.2.2264 189.21.230.195.20787: ., cksum
0xc3d4 (correct), 1664:1664(0) ack 433 win 65535 nop,nop,timestamp
745948332 1556448796
11:19:36.229773 IP (tos 0x0, ttl 51, id 656, offset 0, flags [DF], proto:
TCP (6), length: 112) 189.21.230.195.20787 201.57.5.2.2264: P 433:481(48)
ack 0 win 15136 nop,nop,timestamp 1556449351 745829191,nop,nop,sack 1
{1428:1664}
11:19:36.328854 IP (tos 0x10, ttl 64, id 34621, offset 0, flags [DF],
proto: TCP (6), length: 52) 201.57.5.2.2264 189.21.230.195.20787: ., cksum
0xbf5c (correct), 1664:1664(0) ack 481 win 65535 nop,nop,timestamp
745948873 1556449351
I'm using: tcpdump -nvvv -i ste0 host REMOTE_IP
2008/11/3, Paul A. Procacci [EMAIL PROTECTED]:
J MPZ wrote:
Hi guys,
I have some problem with my FreeBSD server. I have this:
#### #
# Linux1 # - ASA - Internet - # FreeBSD # - # Linux2 #
#### #
If I run a ssh for Linux1 to FreeBSD, my connection freeze when the return
of some command is a big text. Example:
I make a ssh connection in the from the Linux1 to FreeBSD server, then, I
execute some commands, like: 'pwd', 'whoami', 'ls /'... this work
perfectly.
But, if I run some command that return a big text, like as: 'ls /dev/', or
top, my connection freeze.
In other terminal, the tcpdump continues showing packets in this
connection
that was freeze.
If I try to access the Linux2, throught FreeBSD (redirect port on natd or
redirect port with rinetd), the same thing happens.
Is this a problem with FreeBSD? Someone know how I can fix it? Some
sysctl?
Regards,
J.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
The tcpdump that you say continues showing packets..are the packets
leaving the freeBSD machine or arriving at the FreeBSD machine.
My guess is you meant leaving the FreeBSD destined for your linux machine.
If this is the case, then the problem most likely lies with the ASA.
If you monitor the ASA's external interface during your testing, do you see
packets arriving? If so, do you see packets leaving the internal interface
going back to your Linux1 machine?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with FreeBSD
Hi Jeremy, I tried without none rules on ipfw FreeBSD (just allow ip from any to any) and error continues occurring. How I can disable the TCP extensions? I tried to set this value on this sysctl (sysctl net.inet.tcp.rfc1323=0) but not work. 2008/11/3, Jeremy Chadwick [EMAIL PROTECTED]: On Mon, Nov 03, 2008 at 10:43:52PM -0200, J MPZ wrote: Hi guys, I have some problem with my FreeBSD server. I have this: #### # # Linux1 # - ASA - Internet - # FreeBSD # - # Linux2 # #### # If I run a ssh for Linux1 to FreeBSD, my connection freeze when the return of some command is a big text. Example: I make a ssh connection in the from the Linux1 to FreeBSD server, then, I execute some commands, like: 'pwd', 'whoami', 'ls /'... this work perfectly. But, if I run some command that return a big text, like as: 'ls /dev/', or top, my connection freeze. In other terminal, the tcpdump continues showing packets in this connection that was freeze. Does the FreeBSD machine run a firewall at all, e.g. pf(4)? If so, you probably have some rules which are broken. (I've seen this problem on FreeBSD 6.x when using rules which are not correctly configured to match initiate state). Also, if a firewall is in use and you're blocking all forms of ICMP, that would impact path MTU discovery. Naughty. You might also try disabling TCP extensions on the FreeBSD box to see if it makes any difference. Note that this can impact performance (large TCP window sizes won't be negotiated), but it's worth disabling for a test case. sysctl net.inet.tcp.rfc1323=0 If I try to access the Linux2, throught FreeBSD (redirect port on natd or redirect port with rinetd), the same thing happens. Is this a problem with FreeBSD? Someone know how I can fix it? Some sysctl? -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with FreeBSD
Giorgos Keramidas wrote:
On Tue, 4 Nov 2008 11:10:25 -0200, J MPZ [EMAIL PROTECTED] wrote:
Hi Paul,
When my connections freeze, I open the tcpdump in other terminal. If I type
something, type Enter, on the terminal frozen, the tcpdump show packets,
like that:
11:18:45.526256 IP (tos 0x0, ttl 51, id 651, offset 0, flags [DF], proto:
TCP (6), length: 112) 189.21.230.195.20787 201.57.5.2.2264: P 193:241(48)
ack 0 win 15136 nop,nop,timestamp 1556398494 745829191,nop,nop,sack 1
{1428:1664}
[...]
I'm using: tcpdump -nvvv -i ste0 host REMOTE_IP
Can you try capturing the connection setup packets, so we can look at
the TCP MSS negotiation values? Starting TCPDUMP *before* one of the
connections that stall is made should capture that.
There may be an intermediate router or firewall that blocks ICMP and
ends up breaking path MTU discovery. I've seen TCP connections
'stall' when path-mtu was broken by a setup like this and one of the
intermediate routers started dropping TCP packets that were too large
for one of its interfaces.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Since the result set is so big, something else to try may be invoking
the ssh connection with compression on, -C is the flag. THis will allow
us to see if it really isnt working or is just slower than you'd like.
Brian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with FreeBSD
YSSS!!!
It's work! With the -C option work fine! :-)
Now, what I need to do to use it without -C? Do I need to change some
option?
The ssh was executed on Linux:
Linux (ssh -C host) - ASA - Internet - FreeBSD
Thanks!
2008/11/4 Brian Whalen [EMAIL PROTECTED]
Giorgos Keramidas wrote:
On Tue, 4 Nov 2008 11:10:25 -0200, J MPZ [EMAIL PROTECTED] wrote:
Hi Paul,
When my connections freeze, I open the tcpdump in other terminal. If I
type
something, type Enter, on the terminal frozen, the tcpdump show
packets,
like that:
11:18:45.526256 IP (tos 0x0, ttl 51, id 651, offset 0, flags [DF],
proto:
TCP (6), length: 112) 189.21.230.195.20787 201.57.5.2.2264: P
193:241(48)
ack 0 win 15136 nop,nop,timestamp 1556398494 745829191,nop,nop,sack 1
{1428:1664}
[...]
I'm using: tcpdump -nvvv -i ste0 host REMOTE_IP
Can you try capturing the connection setup packets, so we can look at
the TCP MSS negotiation values? Starting TCPDUMP *before* one of the
connections that stall is made should capture that.
There may be an intermediate router or firewall that blocks ICMP and
ends up breaking path MTU discovery. I've seen TCP connections
'stall' when path-mtu was broken by a setup like this and one of the
intermediate routers started dropping TCP packets that were too large
for one of its interfaces.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
Since the result set is so big, something else to try may be invoking the
ssh connection with compression on, -C is the flag. THis will allow us to
see if it really isnt working or is just slower than you'd like.
Brian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems with FreeBSD
Hi guys, I have some problem with my FreeBSD server. I have this: #### # # Linux1 # - ASA - Internet - # FreeBSD # - # Linux2 # #### # If I run a ssh for Linux1 to FreeBSD, my connection freeze when the return of some command is a big text. Example: I make a ssh connection in the from the Linux1 to FreeBSD server, then, I execute some commands, like: 'pwd', 'whoami', 'ls /'... this work perfectly. But, if I run some command that return a big text, like as: 'ls /dev/', or top, my connection freeze. In other terminal, the tcpdump continues showing packets in this connection that was freeze. If I try to access the Linux2, throught FreeBSD (redirect port on natd or redirect port with rinetd), the same thing happens. Is this a problem with FreeBSD? Someone know how I can fix it? Some sysctl? Regards, J. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with FreeBSD
J MPZ wrote: Hi guys, I have some problem with my FreeBSD server. I have this: #### # # Linux1 # - ASA - Internet - # FreeBSD # - # Linux2 # #### # If I run a ssh for Linux1 to FreeBSD, my connection freeze when the return of some command is a big text. Example: I make a ssh connection in the from the Linux1 to FreeBSD server, then, I execute some commands, like: 'pwd', 'whoami', 'ls /'... this work perfectly. But, if I run some command that return a big text, like as: 'ls /dev/', or top, my connection freeze. In other terminal, the tcpdump continues showing packets in this connection that was freeze. If I try to access the Linux2, throught FreeBSD (redirect port on natd or redirect port with rinetd), the same thing happens. Is this a problem with FreeBSD? Someone know how I can fix it? Some sysctl? Regards, J. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] The tcpdump that you say continues showing packets..are the packets leaving the freeBSD machine or arriving at the FreeBSD machine. My guess is you meant leaving the FreeBSD destined for your linux machine. If this is the case, then the problem most likely lies with the ASA. If you monitor the ASA's external interface during your testing, do you see packets arriving? If so, do you see packets leaving the internal interface going back to your Linux1 machine? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with FreeBSD
On Mon, Nov 03, 2008 at 10:43:52PM -0200, J MPZ wrote: Hi guys, I have some problem with my FreeBSD server. I have this: #### # # Linux1 # - ASA - Internet - # FreeBSD # - # Linux2 # #### # If I run a ssh for Linux1 to FreeBSD, my connection freeze when the return of some command is a big text. Example: I make a ssh connection in the from the Linux1 to FreeBSD server, then, I execute some commands, like: 'pwd', 'whoami', 'ls /'... this work perfectly. But, if I run some command that return a big text, like as: 'ls /dev/', or top, my connection freeze. In other terminal, the tcpdump continues showing packets in this connection that was freeze. Does the FreeBSD machine run a firewall at all, e.g. pf(4)? If so, you probably have some rules which are broken. (I've seen this problem on FreeBSD 6.x when using rules which are not correctly configured to match initiate state). Also, if a firewall is in use and you're blocking all forms of ICMP, that would impact path MTU discovery. Naughty. You might also try disabling TCP extensions on the FreeBSD box to see if it makes any difference. Note that this can impact performance (large TCP window sizes won't be negotiated), but it's worth disabling for a test case. sysctl net.inet.tcp.rfc1323=0 If I try to access the Linux2, throught FreeBSD (redirect port on natd or redirect port with rinetd), the same thing happens. Is this a problem with FreeBSD? Someone know how I can fix it? Some sysctl? -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with FreeBSD
I have some problem with my FreeBSD server. I have this: #### # # Linux1 # - ASA - Internet - # FreeBSD # - # Linux2 # #### # If I run a ssh for Linux1 to FreeBSD, my connection freeze when the return of some command is a big text. Example: I make a ssh connection in the from the Linux1 to FreeBSD server, then, I execute some commands, like: 'pwd', 'whoami', 'ls /'... this work perfectly. But, if I run some command that return a big text, like as: 'ls /dev/', or top, my connection freeze. ... If I try to access the Linux2, throught FreeBSD (redirect port on natd or redirect port with rinetd), the same thing happens. Is this a problem with FreeBSD? Someone know how I can fix it? Some sysctl? One possible cause of this behavior is an MTU problem. If something in the Linux1 == FreeBSD path is dropping packets larger than X (where X is something lower than the endpoints are expecting) you'll see exactly this sort of symptom. While the real solution is to fix whatever is dropping the packets, it may be easier to restrict the MTU. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Graphics problems with FreeBSD on Sun SPARC computer
Hi. I was trying to install FreeBSD 7.0 on an old Sun Blade 100 computer (from 2002) which has an UltraSPARC IIe 500MHz RISC CPU in it. But I can't get the graphics to come up (I've only got text-console right now on the OS.). How can I fix this? When I try to do a startx, the screen just goes to black and the monitor light to yellow. Hooking to a TV shows that at this point there is NO SIGNAL. I can ctrl-alt-backspace to shut down the X server and get a command prompt. The machine has an ATI chip of some sort inside, and I've tried configuring X to use several ATI drivers but all giving the same result. Xorg.0.log contained various warning (WW) messages, such as not being able to find fonts.dir, the OS not having counted the PCI devices and so was guessing wildly, that an accelerated framebuffer could not be shadowed, and that there was not enough video RAM (required 12.8MB, card has only 8MB) to allocate a DRI static buffer. Disabling acceleration with 'Option NoAccel true' in the X config file under the device section did not help, although it got rid of the warning about not having enough video RAM. However I then got warnings ATI(0): Acceleration disabled, not initializing the DRI and ATI(0): RENDER extension not supported with a shadowed framebuffer. What can I do to resolve this problem? Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems Installing FreeBSD 6.2 - No floppy devices found!
On Tuesday 20 November 2007 07:32:36 pm Cameron Stuart wrote: Hardware: Maxtron AMD opteron with 3ware 4 port PCI express SATA II raid 5 Problem Description: The 3ware driver must be loaded into the kernel using KLD, but the floppy device cannot be found However, the drive exists, and is configured correctly in the BIOS (IE, the system can boot from the floppy) Attempted Solutions: 1) Tried booting using APCI disabled 2) Tried set hint.fdc.0.flags=1 and the boot shell before continuing into the sysinstall 3) Tried enabling disabling the floppy device in the BIOS Any suggestions or solutions you may have would be greatly appreciated Cheers, Cam Which 3ware card do you have? I made 6.2 iso with working 96xx drivers on them so you can do a regular old install off the cd. I can give you a download link if you'd like, just need to know if you want amd64 or i386. -- Thanks, Josh Paetzel PGP: 8A48 EF36 5E9F 4EDA 5A8C 11B4 26F9 01F1 27AF AECB signature.asc Description: This is a digitally signed message part.
Problems Installing FreeBSD 6.2 - No floppy devices found!
Hardware: Maxtron AMD opteron with 3ware 4 port PCI express SATA II raid 5 Problem Description: The 3ware driver must be loaded into the kernel using KLD, but the floppy device cannot be found However, the drive exists, and is configured correctly in the BIOS (IE, the system can boot from the floppy) Attempted Solutions: 1) Tried booting using APCI disabled 2) Tried set hint.fdc.0.flags=1 and the boot shell before continuing into the sysinstall 3) Tried enabling disabling the floppy device in the BIOS Any suggestions or solutions you may have would be greatly appreciated Cheers, Cam ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X11 forwarding problems in FreeBSD 6.2 - no xauth data? [SOLVED]
On Thursday 12 July 2007 13:59:54 Andy Greenwood wrote: I had this same problem recently on my server. the sshd_config man page says that the default location for xauth is /usr/X11R6/bin/xauth, but mine was installed as /usr/local/bin/xauth. adding XAuthLocation /usr/local/bin/xauth to my sshd_config and restarting sshd fixed it for me. Interesting, because that was the first thing I did, but it did not solve the problem. What did solve the problem was to add the same line to my /etc/ssh/ssh_config in the Host * section. This only fixed one side of the connection, so I can connect from the FreeBSD host to the Linux hosts. On the Linux hosts, I put XAuthLocation /usr/bin/xauth in their /etc/ssh/ssh_config files but that did not fix the problem from the Linux hosts to FreeBSD. I believe it is because of the way that OpenSSH was compiled on FreeBSD but I am not certain. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X11 forwarding problems in FreeBSD 6.2 - no xauth data?
Le 10/07/2007 à 14:41:01-0700, Pollywog a écrit On Sunday 08 July 2007 18:03:49 Pollywog wrote: I am having some problems with X11 forwarding. I can do X11 forwarding via ssh between two machines running Linux, but if I try to do this from FreeBSD (KDE) to either of the Linux machines, it only works if I use startx to start KDE on the fbsd machine (a laptop). If I start KDE from kdm, I get errors that go like this when I start the KDE app on the remote host running Linux: [EMAIL PROTECTED]:~$ kate Xlib: connection to localhost:11.0 refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key kate: cannot connect to X server localhost:11.0 I just did 'ssh' to one of the Linux hosts and when the connection was made, I got this: Warning: No xauth data; using fake authentication data for X11 forwarding. Does this possibly have something to do with the problem I mentioned in my initial post in this thread? I am going to Google that error and see if I can find something. Check where is the xauth app on the Linux box, and make strings sshd|grep xauth to check if it's the same path. If don't you need to fix this with XAuthLocation in your sshd_config file on the Linux box Regards. -- Albert SHIH Observatoire de Paris Meudon SIO batiment 15 Heure local/Local time: Jeu 12 jul 2007 01:14:53 CEST ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X11 forwarding problems in FreeBSD 6.2 - no xauth data? [SOLVED]
On Wednesday 11 July 2007 23:17:42 Albert Shih wrote: Le 10/07/2007 à 14:41:01-0700, Pollywog a écrit On Sunday 08 July 2007 18:03:49 Pollywog wrote: I am having some problems with X11 forwarding. I can do X11 forwarding via ssh between two machines running Linux, but if I try to do this from FreeBSD (KDE) to either of the Linux machines, it only works if I use startx to start KDE on the fbsd machine (a laptop). If I start KDE from kdm, I get errors that go like this when I start the KDE app on the remote host running Linux: [EMAIL PROTECTED]:~$ kate Xlib: connection to localhost:11.0 refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key kate: cannot connect to X server localhost:11.0 I just did 'ssh' to one of the Linux hosts and when the connection was made, I got this: Warning: No xauth data; using fake authentication data for X11 forwarding. Does this possibly have something to do with the problem I mentioned in my initial post in this thread? I am going to Google that error and see if I can find something. Check where is the xauth app on the Linux box, and make strings sshd|grep xauth to check if it's the same path. If don't you need to fix this with XAuthLocation in your sshd_config file on the Linux box I tried that and it did not solve the problem, but you gave me an idea and it worked. I put 'XAuthLocation pathto_xauth' in my ~/.ssh/config on the FreeBSD box and that fixed the problem for both Linux boxes; I can connect to either of them and run X apps. I believe that if I do the same thing on each of the Linux boxes, I should be able to connect to the FreeBSD host and run X apps. Also, instead of each user having to do the above modification, I will put 'XAuthLocation' in /etc/ssh/ssh_config (instead of sshd_config) globally and that should take care of this issue. thank you for your help ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X11 forwarding problems in FreeBSD 6.2 - no xauth data?
On Sunday 08 July 2007 18:03:49 Pollywog wrote: I am having some problems with X11 forwarding. I can do X11 forwarding via ssh between two machines running Linux, but if I try to do this from FreeBSD (KDE) to either of the Linux machines, it only works if I use startx to start KDE on the fbsd machine (a laptop). If I start KDE from kdm, I get errors that go like this when I start the KDE app on the remote host running Linux: [EMAIL PROTECTED]:~$ kate Xlib: connection to localhost:11.0 refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key kate: cannot connect to X server localhost:11.0 I just did 'ssh' to one of the Linux hosts and when the connection was made, I got this: Warning: No xauth data; using fake authentication data for X11 forwarding. Does this possibly have something to do with the problem I mentioned in my initial post in this thread? I am going to Google that error and see if I can find something. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X11 forwarding problems in FreeBSD 6.2 - no xauth data?
On Tuesday 10 July 2007 14:41:01 Pollywog wrote: I just did 'ssh' to one of the Linux hosts and when the connection was made, I got this: Warning: No xauth data; using fake authentication data for X11 forwarding. Does this possibly have something to do with the problem I mentioned in my initial post in this thread? I am going to Google that error and see if I can find something. I found out that mcookie generates magic cookies for xauth, but I do not have the mcookie command in FreeBSD, though it exists on my Debian Etch system and is part of the util-linux package. If I can find mcookie or a command that is analogous to it in FreeBSD, I might be able to fix this problem: http://rocketcalc.com/bread.php?key=22 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X11 forwarding problems in FreeBSD 6.2 - no xauth data?
On Wednesday 11 July 2007, Pollywog wrote: I found out that mcookie generates magic cookies for xauth, but I do not have the mcookie command in FreeBSD, though it exists on my Debian Etch system and is part of the util-linux package. I think you need to generate a new cookie with $ xauth generate :0 . trusted See xauth(1) for more info. HTH, Pieter de Goeje ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X11 forwarding problems in FreeBSD 6.2 - no xauth data?
On 7/10/07, Pollywog [EMAIL PROTECTED] wrote: On Tuesday 10 July 2007 14:41:01 Pollywog wrote: I just did 'ssh' to one of the Linux hosts and when the connection was made, I got this: Warning: No xauth data; using fake authentication data for X11 forwarding. Does this possibly have something to do with the problem I mentioned in my initial post in this thread? I am going to Google that error and see if I can find something. I found out that mcookie generates magic cookies for xauth, but I do not have the mcookie command in FreeBSD, though it exists on my Debian Etch system and is part of the util-linux package. If I can find mcookie or a command that is analogous to it in FreeBSD, I might be able to fix this problem: http://rocketcalc.com/bread.php?key=22 From what I've read at http://www.linuxcommand.org/man_pages/mcookie1.html: mcookie generates a 128-bit random hexadecimal number for use with the X authority system. Typical usage: xauth add :0 . 'mcookie' Therefore, you should be able to use any random 128-bit hex number instead of mcookie. I'm not sure how secure it would be, but it should work just fine. Cheers Federico ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
X11 forwarding problems in FreeBSD 6.2
I am having some problems with X11 forwarding. I can do X11 forwarding via ssh between two machines running Linux, but if I try to do this from FreeBSD (KDE) to either of the Linux machines, it only works if I use startx to start KDE on the fbsd machine (a laptop). If I start KDE from kdm, I get errors that go like this when I start the KDE app on the remote host running Linux: [EMAIL PROTECTED]:~$ kate Xlib: connection to localhost:11.0 refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key kate: cannot connect to X server localhost:11.0 My configurations for ssh are similar on all hosts: sshd_conf has AllowTcpForwarding yes X11DisplayOffset 10 X11UseLocalHost yes XAuthLocation /usr/local/bin/xauth ssh_conf has Host slider HostName 192.168.0.1 ForwardAgent yes ForwardX11 yes ForwardX11Trusted yes PubkeyAuthentication yes Protocol 2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: X11 forwarding problems in FreeBSD 6.2
On July 8, 2007, Pollywog wrote: I am having some problems with X11 forwarding. I can do X11 forwarding via ssh between two machines running Linux, but if I try to do this from FreeBSD (KDE) to either of the Linux machines, it only works if I use startx to start KDE on the fbsd machine (a laptop). If I start KDE from kdm, I get errors that go like this when I start the KDE app on the remote host running Linux: [EMAIL PROTECTED]:~$ kate Xlib: connection to localhost:11.0 refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key kate: cannot connect to X server localhost:11.0 On your FreeBSD machine, try issuing % xhost +local: before you ssh to the Linux machines. Cheers. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
problems with freebsd-update
hello I have 2 servers with FreeBSD 6.2 rebuilt from sources. when I use freebsd-update it fetchs updates and install them. AFter rebooting I always have the old kernel booting. what's wrong ? thanks Rick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems with freebsd-update
On Fri, 15 Jun 2007, RJ45 wrote: hello I have 2 servers with FreeBSD 6.2 rebuilt from sources. when I use freebsd-update it fetchs updates and install them. AFter rebooting I always have the old kernel booting. what's wrong ? thanks Rick Did you compile your kernel? Building the world from the sources does not modify your kernel. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems installing freeBSD 6.2 on older comptuer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steve Bertrand wrote: It's great you resolved it, and now it's archived. We've all been there. That's why I always try to post my resolution to the listserve, newsgroup, or forum that was helping me out. I don't want someone to read along thinking yes, yesI have that problemhow did they solve it And the click on next message in thread in a vain attempt to find the answer that isn't there. That's happened to me more than I care to count. And it's so frustrating because I wonder if they figured it out and never told anyone or if they gave up. Of course, it's much worse for me to read, Oh, I figured it out and no explanation. I'd rather there be nothing than be left wondering what kind of magic the user conjured to solve his problem. - -- Eric Mesa [EMAIL PROTECTED] http://www.ericsbinaryworld.com Note: All emails from this address should have a GPG signature. If you have the proper setup you can use this to confirm my identity and that the email was not changed in transit. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFGTarMPvU+8ApmWXIRAs5gAJ9nzRhdC4cegI95mFvFhaUiZQ7MFQCfWhB2 0NGcYd4X8dXf8zjUWbeuBXY= =DBCn -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing freeBSD 6.2 on older computer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Slothouber wrote: On 2007-05-16 19:41, Eric Mesa wrote: Just acquired an old computer from someone and want to put freeBSD on it. (snip) acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 5. Then it gives me: Hi Eric, Have you tried disconnecting the CD drive and doing an FTP install? - Chris That still leaves me at mountroot prompt and I have no idea what to do there. - -- Eric Mesa [EMAIL PROTECTED] http://www.ericsbinaryworld.com Note: All emails from this address should have a GPG signature. If you have the proper setup you can use this to confirm my identity and that the email was not changed in transit. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFGTL/6PvU+8ApmWXIRAmhnAKC/jmL78x1zz6d/WLn/tTCmAQRACACgqVXJ H2b4Ftvh3s1eJeSh5kEmrWQ= =eMoN -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing freeBSD 6.2 on older computer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2007-05-17 16:50, Eric Mesa wrote: Chris Slothouber wrote: On 2007-05-16 19:41, Eric Mesa wrote: Just acquired an old computer from someone and want to put freeBSD on it. (snip) acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 5. Then it gives me: Hi Eric, Have you tried disconnecting the CD drive and doing an FTP install? - Chris That still leaves me at mountroot prompt and I have no idea what to do there. What are the errors presented before that? It sounds like it can't mount the kernel floppy image for whatever reason. I'd have to suggest that you've try other floppy disk drives and disks to rule out those as points of failure. Also think of the drive that you used to make the floppy diskettes. Since floppies rely on an magnetic medium, with heads to record a stream of data across the surface, certain types of alignment issues can occur. Think of this like a cassette tape recording that sounds fine in your stereo at home but has a horrible hissing sound in your car. Or even the white 'noise' with rented video cassettes, where one must adjust the 'tracking'. I wouldn't give up on this yet but certainly try other floppy drives in both ends and different diskettes. You could even try using the *same* floppy disk drive to make the floppy disks in another computer and re-transplant it back into the target machine. I hope these suggestions help! - -- Chris Slothouber ([EMAIL PROTECTED]) -=- Mercenary Sysadmin BIZ: http://www.hier7.com -=- building.better.ideas PGP: 7A83 F021 5AC3 4BD7 6738 21D8 B348 0B16 79C0 C27F -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGTMRSs0gLFnnAwn8RAgFZAKDUvCzvIuZKpLXwEYvmUuI10lSrNgCgkQL3 eiUTouaydZ/4Ymu0mFr7nRM= =RSJX -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing freeBSD 6.2 on older computer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Slothouber wrote: On 2007-05-17 16:50, Eric Mesa wrote: Chris Slothouber wrote: On 2007-05-16 19:41, Eric Mesa wrote: Just acquired an old computer from someone and want to put freeBSD on it. (snip) acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 5. Then it gives me: Hi Eric, Have you tried disconnecting the CD drive and doing an FTP install? - Chris That still leaves me at mountroot prompt and I have no idea what to do there. What are the errors presented before that? It sounds like it can't mount the kernel floppy image for whatever reason. I'd have to suggest that you've try other floppy disk drives and disks to rule out those as points of failure. Also think of the drive that you used to make the floppy diskettes. Since floppies rely on an magnetic medium, with heads to record a stream of data across the surface, certain types of alignment issues can occur. Think of this like a cassette tape recording that sounds fine in your stereo at home but has a horrible hissing sound in your car. Or even the white 'noise' with rented video cassettes, where one must adjust the 'tracking'. I wouldn't give up on this yet but certainly try other floppy drives in both ends and different diskettes. You could even try using the *same* floppy disk drive to make the floppy disks in another computer and re-transplant it back into the target machine. I hope these suggestions help! I don't want to declare victory too early, but I think I figured it out. You're probably right, but who the f- still has floppies lying around? I certainly couldn't use pristine ones as I was warned to. However, part of the problem with the cd is that at the mountroot prompt I kept typing ufs:acd0 and it barfed. While googling on mountroot, I found cd9660:acd0 (it'd be nice if a list of possible filesystems was provided along with the list of things you can boot from) it then booted off the cd (YAY!) it made like it was booting into freeBSD. Then at the amnesiatic login, I put root then sysinstall and it SEEMS to be going ok. I stopped to write this reply while it was fresh in my head. So it seems that potential crisis was averted. I can read from the cd, just not boot. I'll attempt a cd install and if that doesn't work, at least I can get far enough to do an ftp one. Thanks for your help, - -- Eric Mesa [EMAIL PROTECTED] http://www.ericsbinaryworld.com Note: All emails from this address should have a GPG signature. If you have the proper setup you can use this to confirm my identity and that the email was not changed in transit. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFGTMWsPvU+8ApmWXIRAjrjAKDGSzqG4A9CptRSUfJfO+ooEU997ACg1KXc x2Mikt1AbU9Pm/HF655D6SM= =+awy -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing freeBSD 6.2 on older computer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Slothouber wrote: On 2007-05-17 16:50, Eric Mesa wrote: Chris Slothouber wrote: On 2007-05-16 19:41, Eric Mesa wrote: Just acquired an old computer from someone and want to put freeBSD on it. (snip) acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 5. Then it gives me: Hi Eric, Have you tried disconnecting the CD drive and doing an FTP install? - Chris That still leaves me at mountroot prompt and I have no idea what to do there. What are the errors presented before that? It sounds like it can't mount the kernel floppy image for whatever reason. I'd have to suggest that you've try other floppy disk drives and disks to rule out those as points of failure. Also think of the drive that you used to make the floppy diskettes. Since floppies rely on an magnetic medium, with heads to record a stream of data across the surface, certain types of alignment issues can occur. Think of this like a cassette tape recording that sounds fine in your stereo at home but has a horrible hissing sound in your car. Or even the white 'noise' with rented video cassettes, where one must adjust the 'tracking'. I wouldn't give up on this yet but certainly try other floppy drives in both ends and different diskettes. You could even try using the *same* floppy disk drive to make the floppy disks in another computer and re-transplant it back into the target machine. I hope these suggestions help! That didn't quite work correctly. It apparently caused the CD to become the filesystem which meant I couldn't install. I couldn't figure out a way around it. - -- Eric Mesa [EMAIL PROTECTED] http://www.ericsbinaryworld.com Note: All emails from this address should have a GPG signature. If you have the proper setup you can use this to confirm my identity and that the email was not changed in transit. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFGTNNEPvU+8ApmWXIRAn85AJ0WyXG9NnI9k/3jiX4aw/XlT9gqtwCfWnG/ S9LgQzsRnukFyPYb45uU54s= =gR0R -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
re: problems installing freeBSD 6.2 on older comptuer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As Chris Slothouber said, it's probably an issue with the floppies. My resolution was to remove the hard drive, place it into a machine I knew was capable of installing freeBSD and installing it. Am now in the process of putting it back into its original case to make sure it all worked ok. I'm a bit frustrated, but what can you do? It would be impossible for the freeBSD team to cater to all the corner cases. - -- Eric Mesa [EMAIL PROTECTED] http://www.ericsbinaryworld.com Note: All emails from this address should have a GPG signature. If you have the proper setup you can use this to confirm my identity and that the email was not changed in transit. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFGTQYqPvU+8ApmWXIRAoZ+AJsEGBZaw+qtN/2ig4+0yugKeG18kACg5mC3 fbBuwCgDSaV1VEM7n33s18U= =ltyd -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems installing freeBSD 6.2 on older comptuer
I'm a bit frustrated, but what can you do? It would be impossible for the freeBSD team to cater to all the corner cases. You can move the HD as you did ;) Technically, if you really wanted, you could be the impossible FreeBSD team member who reaches into the corner you've needed catered to. That said, I'm sure it's widely known that Google usually solves all problems that are in the corner you've need catered to, but sometimes not the corner you are in. It's great you resolved it, and now it's archived. We've all been there. disclaimer I couldn't help but laugh at true realization/frustration when I read this post. /disclaimer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems installing freeBSD 6.2 on older computer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just acquired an old computer from someone and want to put freeBSD on it. It's a dual processor P2 200 Mhz with 128 MB ram. It has a DVD-ROM and a floppy drive. I was told by the former owner, who built it, that the computer would not install the latest types of Linux installs that required booting from CD. He also told me that the BIOS cannot be updated. He's pretty knowledgeable about computers so I believe him. Here's the procedure I've been following which has been failing for two days now. 1. Use the boot floppy to boot from A: then floppies kern1-kern3 2. After kern3 reinster boot then after hitting enter I get some text, including zf_read: fill error 3. It continues to the BSD Menu - I've tried nearly every option here from Default to ACPI to safe mode to logging mode. 4. it does the device probe - when it gets to the DVD-ROM, it prints out: acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 5. Then it gives me: Manual root filesystem specification mountroot I am stuck here no matter what I try. This is driving me nuts! If anyone can help me with this I'd be eternally grateful. Everything I found on google either referenced burning a CD or disabling the Zip drive. Oh, I know these CDs are good media because I've used them to install freeBSD 3 times already. Also, I have a commercial BSD CD from 4.5 and one from 5.0pre and neither of them work. Thanks, - -- Eric Mesa [EMAIL PROTECTED] http://www.ericsbinaryworld.com Note: All emails from this address should have a GPG signature. If you have the proper setup you can use this to confirm my identity and that the email was not changed in transit. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFGS5aVPvU+8ApmWXIRAvuRAJ9tFF7awUMHf9u3mnV0dF53JfGLcACg0a5R cF05pKUnEacQ9aajd4k7EtQ= =GIzQ -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing freeBSD 6.2 on older computer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jack Barnett wrote: Do you have another CD Drive you could use, just to get it installed? Another thing you could try is an FTP install.. I do that all the time and works good if you have faster internet connection. -J I'm not 100% sure, but I don't think it's the CD drive - I think it's related to the bios. Also, I can't get to the FTP part. It never even gets that far. - -- Eric Mesa [EMAIL PROTECTED] http://www.ericsbinaryworld.com Note: All emails from this address should have a GPG signature. If you have the proper setup you can use this to confirm my identity and that the email was not changed in transit. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFGS57yPvU+8ApmWXIRAu05AJ9/gZq/8/Fa6BMuWbcUg9Svfwe9NwCeOIfn Ojaj9Y9fysSdzn4Jc3XfLOg= =JoAl -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing freeBSD 6.2 on older computer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2007-05-16 19:41, Eric Mesa wrote: Just acquired an old computer from someone and want to put freeBSD on it. (snip) acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 5. Then it gives me: Hi Eric, Have you tried disconnecting the CD drive and doing an FTP install? - - Chris - -- Chris Slothouber ([EMAIL PROTECTED]) -=- Mercenary Sysadmin BIZ: http://www.hier7.com -=- building.better.ideas PGP: 7A83 F021 5AC3 4BD7 6738 21D8 B348 0B16 79C0 C27F -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGS67ds0gLFnnAwn8RAjd4AKCGKjhHk/upEP56f6JtR3Cc29m/bgCZAcVy 3AD1xFo8ettq3EvYLLFXUQ4= =7KGL -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PHP, pear, session problems on FreeBSD 6.2
Andrei Iarus wrote: After noticing that I get an php error (an Segmentation fault error), I reinstalled my php port. Than I got some errors related to the preg_match function = I reinstalled all php extensions (with portupgrade -rf php-5.2.1_3), including pcre. After this, my apache server didn't start (apachectl start didn't give me any errors, but after switching to the debug mode from the httpd.conf file, all I got was something like [Mon Apr 9 23:34:15 2007] [info] mod_unique_id: using ip addr 10.0.0.1). Then I discovered that it was because the php5-session extension (after commenting the line in the extensions.ini). Then I noticed that listing the installed pear/pecl packages gave me a lot of php errors (some errors in Command.php). Trying to install the pear package using the ports, it would stop with stop with an *** Signal 11 This may or may not help you: PHP is very (should probably say extremely) sensitive to the order its extensions are loaded. Due to the way portupgrade works, the order of extensions is not kept during upgrades (and is for-all-intents-and-purposes randomized). Thus, once perfectly working server may be unusuable after a portupgrade run. The solution: find the order of extensions that work for you (extensions.ini), and save it somewhere so you can restore it after portupgrade. You should search the archives and the web for more information - it's a common problem. signature.asc Description: OpenPGP digital signature
PHP, pear, session problems on FreeBSD 6.2
After noticing that I get an php error (an Segmentation fault error), I reinstalled my php port. Than I got some errors related to the preg_match function = I reinstalled all php extensions (with portupgrade -rf php-5.2.1_3), including pcre. After this, my apache server didn't start (apachectl start didn't give me any errors, but after switching to the debug mode from the httpd.conf file, all I got was something like [Mon Apr 9 23:34:15 2007] [info] mod_unique_id: using ip addr 10.0.0.1). Then I discovered that it was because the php5-session extension (after commenting the line in the extensions.ini). Then I noticed that listing the installed pear/pecl packages gave me a lot of php errors (some errors in Command.php). Trying to install the pear package using the ports, it would stop with stop with an *** Signal 11 Stop in /usr/ports/devel/pear. error, but it solved (in a way) the previous problem with that php errors (bringing another one: Segmentation fault: 11 (core dumped)). I don't know what else I can do... Details about my system: uname -a FreeBSD hostname 6.2-RELEASE-p2 FreeBSD 6.2-RELEASE-p2 #3: Thu Mar 8 10:01:45 EET 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/krnl_namel i386 pkg_info|grep php5 php5-5.2.1_3PHP Scripting Language (Apache Module and CLI) php5-bz2-5.2.1_3The bz2 shared extension for php php5-ctype-5.2.1_3 The ctype shared extension for php php5-gd-5.2.1_3 The gd shared extension for php php5-mbstring-5.2.1_3 The mbstring shared extension for php php5-mcrypt-5.2.1_3 The mcrypt shared extension for php php5-mysql-5.2.1_3 The mysql shared extension for php php5-openssl-5.2.1_3 The openssl shared extension for php php5-pcre-5.2.1_5 The pcre shared extension for php php5-session-5.2.1_3 The session shared extension for php php5-xml-5.2.1_3The xml shared extension for php php5-zlib-5.2.1_3 The zlib shared extension for php pear list Installed packages, channel pear.php.net: = Package Version State Archive_Tar 1.3.2 stable Console_Getopt 1.2.1 stable DB 1.7.11 stable PEAR 1.5.0 stable Structures_Graph 1.0.2 stable rar 0.3.1 beta Segmentation fault: 11 (core dumped) pecl list Fatal error: Call to undefined function preg_match() in /usr/local/share/pear/PEAR/Frontend/CLI.php on line 70 If these details are not enough, just let me know. Thank you in advance. - Need Mail bonding? Go to the Yahoo! Mail QA for great tips from Yahoo! Answers users. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems installing FreeBSD
Hi, I'm trying to install FreeBSD from ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/6.2 I downloaded all the files to a folder on my 2nd HD (Primary is C: 80 Gb Windows XP SP2, 2nd external 250 Gb HD has 2 partitons, G: which contains the entire C:drive for backup, and a partition H: for FreeBSD. Anyway, The Boot CD doesn't boot (yes, I changed the BIOS sequence), and the Disk1 and Disk2 won't fit on a CD. I'm new at this, but I do know Windows and DOS inside and out. Question is, what do I do next? everytime I try to 'open' the file(s) Roxio CD Creator opens up. Help! Thanks, Steve The only secure computer is one that's unplugged, locked in a safe, and buried 20 feet under the ground in a secret location... and I'm not even too sure about that one ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing FreeBSD
s.moyzis wrote: Hi, I'm trying to install FreeBSD from ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/6.2 I downloaded all the files to a folder on my 2nd HD (Primary is C: 80 Gb Windows XP SP2, 2nd external 250 Gb HD has 2 partitons, G: which contains the entire C:drive for backup, and a partition H: for FreeBSD. Anyway, The Boot CD doesn't boot (yes, I changed the BIOS sequence), and the Disk1 and Disk2 won't fit on a CD. I'm new at this, but I do know Windows and DOS inside and out. Question is, what do I do next? everytime I try to 'open' the file(s) Roxio CD Creator opens up. Help! Thanks, It sounds very much like you just haven't written stuff correctly to CD. 1) You only *need* disk 1 and it boots. Disk 2 contains pre-built packages which you might want. I expect the handbook covers this. (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-diff-media.html section on FreeBSD 5.X and above). 2) You need to write disk1 using Roxio or Nero or whatever *as an ISO*, *not* copy it as a file to the CD. The option might say something like image file instead of ISO. Same for disk2, to a different CD of course. Roxio opens up when you click on the ISO because an ISO is a special file format that is basically a dump of a CD. Nothing other than a CD writing program is likely to make much use of it. Forget the boot CD you don't need it. It is, I believe, used for network-only installs and using CD1 is easier for a beginner. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing FreeBSD
--- Alex Zbyslaw [EMAIL PROTECTED] wrote: s.moyzis wrote: Hi, I'm trying to install FreeBSD from ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/6.2 I downloaded all the files to a folder on my 2nd HD (Primary is C: 80 Gb Windows XP SP2, 2nd external 250 Gb HD has 2 partitons, G: which contains the entire C:drive for backup, and a partition H: for FreeBSD. Anyway, The Boot CD doesn't boot (yes, I changed the BIOS sequence), and the Disk1 and Disk2 won't fit on a CD. I'm new at this, but I do know Windows and DOS inside and out. Question is, what do I do next? everytime I try to 'open' the file(s) Roxio CD Creator opens up. Help! Thanks, It sounds very much like you just haven't written stuff correctly to CD. 1) You only *need* disk 1 and it boots. Disk 2 contains pre-built packages which you might want. I expect the handbook covers this. (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-diff-media.html section on FreeBSD 5.X and above). 2) You need to write disk1 using Roxio or Nero or whatever *as an ISO*, *not* copy it as a file to the CD. The option might say something like image file instead of ISO. Same for disk2, to a different CD of course. Roxio opens up when you click on the ISO because an ISO is a special file format that is basically a dump of a CD. Nothing other than a CD writing program is likely to make much use of it. Forget the boot CD you don't need it. It is, I believe, used for network-only installs and using CD1 is easier for a beginner. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Hello, Just like Alex has pointed out; you have to burn from an ISO / Image. If you are using Roxio 7 it is called: Burn from Disc Image File... Otherwise you may wind up burning the ISO as a single file. Regards, Paulette McGee Don't get soaked. Take a quick peek at the forecast with the Yahoo! Search weather shortcut. http://tools.search.yahoo.com/shortcuts/#loc_weather ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing FreeBSD
On Thu, Mar 08, 2007 at 04:30:43AM -0600, s.moyzis wrote: Hi, I'm trying to install FreeBSD from ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/6.2 I downloaded all the files to a folder on my 2nd HD (Primary is C: 80 Gb Windows XP SP2, 2nd external 250 Gb HD has 2 partitons, G: which contains the entire C:drive for backup, and a partition H: for FreeBSD. Anyway, The Boot CD doesn't boot (yes, I changed the BIOS sequence), and the Disk1 and Disk2 won't fit on a CD. I'm new at this, but I do know Windows and DOS inside and out. Question is, what do I do next? everytime I try to 'open' the file(s) Roxio CD Creator opens up. Help! Thanks, Steve The first thought is: did you burn the bood CD correctly. It is already an ISO and should be burned as a plain data file with no reforming or conversion to be bootable or etc. That is the first thing I would verify. If you can get your hands on a different machine, then try booting that with the CD. It won't hurt anything to just boot as long as you don't commit to modifying the disk - for which there are lots of warnings and 'are you really sure you want to do this' messages. You only need the disk1 for booting and installing or running a fixit. The disk2 has additional things you might want to install - ports, if you can't install them over the net. As for where to put the FreeBSD installation, you cannot put it in an MS drive such as h:. It has to go in to its own primary slice. MS does not know how to recognize, read or write a FreeBSD slice. So if it is something MS can see, then it is not a FreeBSD primary slice. If MS uses the whole drive, you will need to either wipe out the MS stuff or shrink those slices to make room for a FreeBSD slice. You can look at it with the FreeBSD fdisk routine in the fixit shell. - But, of course, you have to get it to boot to the CD first. Then, since the existing slices are probably NTFS, you may need a special utility to shrink them. There are freeware utilities that can handle FAT slices, but not NTFS. I have been quite successful using Partition Magic to manipulate disk slicing including NTFS. It is generally available for about $70 the last I checked. With that you create a Primary Partition of 'unknown' type in empty space obtained by either shrinking or deleting currently existing partitions.NOTE here that the MS world calls these primary partitions, but the BSD UNIX world calls them slices and uses the term partition for a different kind of disk division - those that further subdivide slices. So, do some more studying and check out that CD burn. jerry The only secure computer is one that's unplugged, locked in a safe, and buried 20 feet under the ground in a secret location... and I'm not even too sure about that one ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
3ware 9550SX RAID Card Problems w/ FreeBSD 5.5
Hi, I have a Dell Poweredge 1800, and was previously using FreeBSD 5.4 booted from a LSI MegaRAID SATA card. Things worked fine. However, this machine is going into production as a email server, so I purchased a 3ware 9550SX-4LP card to use instead of the LSI. I installed the 3ware card and configured it w/ the BIOS utility: default options, with 2 x 250GB drives set up in a RAID 1, with one hot spare. Then came to install FreeBSD 5.5 on it. The install CD saw the drive fine, and I set up partitions and such, but when it came time to write settings and perform the installation, I got a Error: Cannot write to disk da0, and install failed. The 3ware page says that for 5.4 and 6.0 a kernel module must be loaded separately (or the kernel recompiled), but as 5.5 includes the updated twa driver I didn't think this was necessary. Any thoughts would be much appreciated! Thanks, Ramsey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 3ware 9550SX RAID Card Problems w/ FreeBSD 5.5
Figured it out: I stupidly neglected to name the array in the 3ware BIOS config, which is apparantly what caused the failure. I rebuilt the array and everything works great now. Sorry to waste anyone's time. Ramsey On 8/8/06, Ramsey Tantawi [EMAIL PROTECTED] wrote: Hi, I have a Dell Poweredge 1800, and was previously using FreeBSD 5.4 booted from a LSI MegaRAID SATA card. Things worked fine. However, this machine is going into production as a email server, so I purchased a 3ware 9550SX-4LP card to use instead of the LSI. I installed the 3ware card and configured it w/ the BIOS utility: default options, with 2 x 250GB drives set up in a RAID 1, with one hot spare. Then came to install FreeBSD 5.5 on it. The install CD saw the drive fine, and I set up partitions and such, but when it came time to write settings and perform the installation, I got a Error: Cannot write to disk da0, and install failed. The 3ware page says that for 5.4 and 6.0 a kernel module must be loaded separately (or the kernel recompiled), but as 5.5 includes the updated twa driver I didn't think this was necessary. Any thoughts would be much appreciated! Thanks, Ramsey ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems running freebsd 6.0+
You should post with your dmesg output and uname -a as well. It would also help if you also included the task list from ps -ax -Derek At 08:16 PM 6/24/2006, Tom Cruickshank wrote: Hello, I'm hoping is the correct mailing list for this, if not, please feel free to direct me to a more appriopriate one. I have a box which I'm trying to run FreeBSD on. I can run FreeBSD 5.4 on it without any problems, but if I try run FreeBSD 6.0 or 6.1, at any point in time while the system is running (could be on load up or when system is already loaded), the computer just *freezes*. The only thing which can be done afterwards is a cold reboot. I hav checked the /var/log/messages file and haven't been able to find anything wrong. Hardware specs: Motherboard: A7N8X-X Has anyone ever had this kind of problem themselves or heard of it? Any help would be appreicated. Thanks! Tom Cruickshank ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: problems running freebsd 6.0+
Hello, Not a problem at all! Here is the info I get from a dmesg. This was done using FreeBSD 5.4 Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC mptable_probe: MP Config Table has bad signature: \^O8\^O ACPI APIC Table: Nvidia AWRDACPI Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Sempron(tm) (2004.56-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x681 Stepping = 1 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA, CMOV,PAT,PSE36,MMX,FXSR,SSE AMD Features=0xc048MP,AMIE,DSP,3DNow! real memory = 1610547200 (1535 MB) avail memory = 1568518144 (1495 MB) ioapic0 Version 1.1 irqs 0-23 on motherboard npx0: math processor on motherboard npx0: INT 16 interface acpi0: Nvidia AWRDACPI on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x4008-0x400b on acpi0 cpu0: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: NVIDIA nForce2 AGP Controller mem 0xd000-0xd7ff at device 0.0 on pci0 pci0: memory, RAM at device 0.1 (no driver attached) pci0: memory, RAM at device 0.2 (no driver attached) pci0: memory, RAM at device 0.3 (no driver attached) pci0: memory, RAM at device 0.4 (no driver attached) pci0: memory, RAM at device 0.5 (no driver attached) isab0: PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 pci0: serial bus, SMBus at device 1.1 (no driver attached) ohci0: OHCI (generic) USB controller mem 0xe5002000-0xe5002fff irq 22 at device 2.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: OHCI (generic) USB controller mem 0xe5003000-0xe5003fff irq 21 at device 2.1 on pci0 usb1: OHCI version 1.0, legacy support usb1: OHCI (generic) USB controller on ohci1 usb1: USB revision 1.0 uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered pci0: serial bus, USB at device 2.2 (no driver attached) pci0: network, ethernet at device 4.0 (no driver attached) pci0: multimedia, audio at device 6.0 (no driver attached) pcib1: ACPI PCI-PCI bridge at device 8.0 on pci0 pci1: ACPI PCI bus on pcib1 fxp0: Intel 82558 Pro/100 Ethernet port 0xc000-0xc01f mem 0xe400-0xe40f,0xe000-0xefff irq 17 at device 9.0 on pci1 miibus0: MII bus on fxp0 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:08:c7:b9:f6:5f atapci0: nVidia nForce2 UDMA133 controller port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 9.0 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib2 pci2: display, VGA at device 0.0 (no driver attached) fdc0: floppy drive controller port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: ECP parallel printer port port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: Parallel port bus on ppc0 plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 orm0: ISA Option ROMs at iomem 0xd2000-0xd27ff,0xd-0xd17ff on isa0 pmtimer0 on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 2004560508 Hz quality 800 Timecounters tick every 10.000 msec ad0: 76319MB WDC WD800JB-00CRA1/17.07W17 [155061/16/63] at ata0-master UDMA100 acd0: CDROM MATSHITA CR-594/YS0B at ata1-master PIO4 Mounting root from ufs:/dev/ad0s2a And yes I was using a generic kernel when using FreeBSD 6.0 and 6.1 The box froze before I could even think of tweaking it. Thanks for any assistance! Tom Cruickshank -Original Message- From: Subhro Kar [mailto:[EMAIL PROTECTED] Sent: Saturday, June 24, 2006 11:05 PM To: Tom Cruickshank Cc: freebsd-questions@freebsd.org Subject: Re: problems running freebsd 6.0+ Tom Cruickshank wrote: Hello, Hello Tom, I'm hoping is the correct
problems running freebsd 6.0+
Hello, I'm hoping is the correct mailing list for this, if not, please feel free to direct me to a more appriopriate one. I have a box which I'm trying to run FreeBSD on. I can run FreeBSD 5.4 on it without any problems, but if I try run FreeBSD 6.0 or 6.1, at any point in time while the system is running (could be on load up or when system is already loaded), the computer just *freezes*. The only thing which can be done afterwards is a cold reboot. I hav checked the /var/log/messages file and haven't been able to find anything wrong. Hardware specs: Motherboard: A7N8X-X Has anyone ever had this kind of problem themselves or heard of it? Any help would be appreicated. Thanks! Tom Cruickshank ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems running freebsd 6.0+
Tom Cruickshank wrote: Hello, Hello Tom, I'm hoping is the correct mailing list for this, if not, please feel free to direct me to a more appriopriate one. You are on the correct mailing list :-). I have a box which I'm trying to run FreeBSD on. I can run FreeBSD 5.4 on it without any problems, but if I try run FreeBSD 6.0 or 6.1, at any point in time while the system is running (could be on load up or when system is already loaded), the computer just *freezes*. The only thing which can be done afterwards is a cold reboot. I hav checked the /var/log/messages file and haven't been able to find anything wrong. Hardware specs: Motherboard: A7N8X-X The information you have provided is not complete. We would be requiring more information to understand what is going wrong. For a start can you show us a copy of dmesg and your kernel config file (if you are not running a GENERIC kernel). Thanks and Best Regards Subhro ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems Installing FreeBSD 5.4 6.0
Hi, I'm trying to install FreeBSD 5.4 6.0 on my intel Celeron 2.0 Pc, but every time i get the following error when the next installation process is Fdisk : no disks found! please verify that your disk controller is being properly probed please help. Regards, Mo. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems Installing FreeBSD 5.4 6.0
You need to provide more information on your system such as what disk controller(s) it has and what hard disks. -Derek At 07:24 AM 4/16/2006, Mohamad Babaei wrote: Hi, I'm trying to install FreeBSD 5.4 6.0 on my intel Celeron 2.0 Pc, but every time i get the following error when the next installation process is Fdisk : no disks found! please verify that your disk controller is being properly probed please help. Regards, Mo. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Problems Installing FreeBSD 5.4 6.0
try trying turn plug-n-play and power management in the pc bios. post the boot probe log here -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mohamad Babaei Sent: Sunday, April 16, 2006 8:24 AM To: freebsd-questions@freebsd.org Subject: Problems Installing FreeBSD 5.4 6.0 Hi, I'm trying to install FreeBSD 5.4 6.0 on my intel Celeron 2.0 Pc, but every time i get the following error when the next installation process is Fdisk : no disks found! please verify that your disk controller is being properly probed please help. Regards, Mo. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bandwidth Problems with Freebsd 5.x
Donald J. O'Neill a écrit : I guess you're right to say there's a misunderstanding. Ok I understand. I would want to say on this post that I made tests from the BSD box to a Debian box, both located on the 100 Mbits/s network. And I made others tests between the same BSD box (still located on the 100 Mbits/s network) and my home computer behind my ADSL Line. Regards, ptitoliv ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bandwidth Problems with Freebsd 5.x
Hello Everybody, I made lots of searches on the Internet and I found something about the option net.inet.tcp.inflight.enable. If I set this value to 0, my bandwitdh problems are resolved. Does anybody knows something about this options and why can it be the origin of this problem ? Regards, Ptitoliv ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bandwidth Problems with Freebsd 5.x
On Sunday 26 February 2006 08:10, ptitoliv wrote: Hello Everybody, I made lots of searches on the Internet and I found something about the option net.inet.tcp.inflight.enable. If I set this value to 0, my bandwitdh problems are resolved. Does anybody knows something about this options and why can it be the origin of this problem ? Regards, Ptitoliv ___ I made some quick check, there is some information available. Most of it seems to be pretty recent. I suggest joining freebsd-stable@ as there is some questions going on about it there. You can also google for information on: net.inet.tcp.inflight.enable There may be other things to look at and good reasons to have it enabled, or disabled. Take from chapter 11 of the handbook: = 11.13.2.2 TCP Bandwidth Delay Product The TCP Bandwidth Delay Product Limiting is similar to TCP/Vegas in NetBSD. It can be enabled by setting net.inet.tcp.inflight.enable sysctl variable to 1. The system will attempt to calculate the bandwidth delay product for each connection and limit the amount of data queued to the network to just the amount required to maintain optimum throughput. This feature is useful if you are serving data over modems, Gigabit Ethernet, or even high speed WAN links (or any other link with a high bandwidth delay product), especially if you are also using window scaling or have configured a large send window. If you enable this option, you should also be sure to set net.inet.tcp.inflight.debug to 0 (disable debugging), and for production use setting net.inet.tcp.inflight.min to at least 6144 may be beneficial. However, note that setting high minimums may effectively disable bandwidth limiting depending on the link. The limiting feature reduces the amount of data built up in intermediate route and switch packet queues as well as reduces the amount of data built up in the local host's interface queue. With fewer packets queued up, interactive connections, especially over slow modems, will also be able to operate with lower Round Trip Times. However, note that this feature only effects data transmission (uploading / server side). It has no effect on data reception (downloading). Adjusting net.inet.tcp.inflight.stab is not recommended. This parameter defaults to 20, representing 2 maximal packets added to the bandwidth delay product window calculation. The additional window is required to stabilize the algorithm and improve responsiveness to changing conditions, but it can also result in higher ping times over slow links (though still much lower than you would get without the inflight algorithm). In such cases, you may wish to try reducing this parameter to 15, 10, or 5; and may also have to reduce net.inet.tcp.inflight.min (for example, to 3500) to get the desired effect. Reducing these parameters should be done as a last resort only. Note: In 4.X and earlier releases of FreeBSD the inflight sysctl variables are directly under net.inet.tcp. Their names were (in alphabetic order): net.inet.tcp.inflight_debug, net.inet.tcp.inflight_enable, net.inet.tcp.inflight_max, net.inet.tcp.inflight_min, net.inet.tcp.inflight_stab. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Bandwidth Problems with Freebsd 5.x
It has already been suggested but obviously you have ignored it so I'll say it again - get the hosting provider on the horn and have them lock the switch port to 100baseT-half duplex, you then do the same, then try the test, then have them lock to 10base t full, you do the same, try the test again, then have them lock to 10base t half, you do the same, and try again. Report the results. Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of ptitoliv Sent: Saturday, February 25, 2006 2:35 PM To: [EMAIL PROTECTED] Cc: Mathieu CHATEAU; freebsd-questions@freebsd.org Subject: Re: Bandwidth Problems with Freebsd 5.x Danial Thom a écrit : It seems unlikely that he'd get good throughput in one direction if the link was hosed. One dropped packets and you're shot. The easy way to test this is to eliminate the switch..hook the Freebsd box directly to the linux box. Impossible to do that because the boxes are rented by an hosting company. ptitoliv ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 268.1.0/269 - Release Date: 2/24/2006 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Bandwidth Problems with Freebsd 5.x
Your testing is way to general to make the blanket statement that something is wrong with FreeBSD. You say you did a transfer between boxes but give no details how you did it or what operating system is on the sending and receiving boxes. Did you use FTP or ssh? Ssh has know buffer size problems between un-like operating system a each end that cause massive slowness. Check the list archives for the last 5 days for subject High Performance SSH/SCP - HPN-SSH to get the thread. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of ptitoliv Sent: Sunday, February 19, 2006 12:55 PM To: Mathieu CHATEAU; freebsd-questions@freebsd.org Subject: Re: Bandwidth Problems with Freebsd 5.x Mathieu CHATEAU a écrit : try this: ping -c 1000 -s 1500 IP_TO_PING wait for the 1000 ping to go trough. You should not have more than 0,5% of loss (is the servers aren't overload). If it's more or equal than 0,5%, it comes from the network (cables or switches fault). Each host would be in 100 full (via autoselect to be sure the conf is ok on the switch). I made the tests on the two boxes = 0 % packet loss. I man an other interesting test. I try to transfert between the BSD Box and a server located at home behind my 1MB/s ADSL Line. Here are the results : FreeBSD box = Workstation at home : 300 kB/s Debian box on the same network = Workstation at home : 950 kB/s. This test confirms cleraly that there is a problem with the BSD, I guess. Could it be a bug from the VR driver ? Regards, Ptitoliv ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bandwidth Problems with Freebsd 5.x
On Sunday 19 February 2006 11:54, ptitoliv wrote: Mathieu CHATEAU a écrit : try this: ping -c 1000 -s 1500 IP_TO_PING wait for the 1000 ping to go trough. You should not have more than 0,5% of loss (is the servers aren't overload). If it's more or equal than 0,5%, it comes from the network (cables or switches fault). Each host would be in 100 full (via autoselect to be sure the conf is ok on the switch). I made the tests on the two boxes = 0 % packet loss. I man an other interesting test. I try to transfert between the BSD Box and a server located at home behind my 1MB/s ADSL Line. Here are the results : FreeBSD box = Workstation at home : 300 kB/s Debian box on the same network = Workstation at home : 950 kB/s. This test confirms cleraly that there is a problem with the BSD, I guess. Could it be a bug from the VR driver ? Regards, Ptitoliv ___ Not hardly. I'll bet that 950kB/s for the Debian box was the peak download speed and it didn't maintain it through the entire download. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bandwidth Problems with Freebsd 5.x
If you are testing it through your home this test is irrelevant as there is a lot that could cause it to slow down if you test it from the freebsd box to another freebsd box on the same switch i bet it would be faster then the shity debian box the internet is a weird place one momment its quick another its slow try doing atraceroute on your DSL as i guarantee it's a problem with your DSL or whatever the box is connected to not the BSD box itself. On Sunday 19 February 2006 11:54, ptitoliv wrote: Mathieu CHATEAU a écrit : try this: ping -c 1000 -s 1500 IP_TO_PING wait for the 1000 ping to go trough. You should not have more than 0,5% of loss (is the servers aren't overload). If it's more or equal than 0,5%, it comes from the network (cables or switches fault). Each host would be in 100 full (via autoselect to be sure the conf is ok on the switch). I made the tests on the two boxes = 0 % packet loss. I man an other interesting test. I try to transfert between the BSD Box and a server located at home behind my 1MB/s ADSL Line. Here are the results : FreeBSD box = Workstation at home : 300 kB/s Debian box on the same network = Workstation at home : 950 kB/s. This test confirms cleraly that there is a problem with the BSD, I guess. Could it be a bug from the VR driver ? Regards, Ptitoliv ___ Not hardly. I'll bet that 950kB/s for the Debian box was the peak download speed and it didn't maintain it through the entire download. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bandwidth Problems with Freebsd 5.x
Mathieu CHATEAU a écrit : Are the debian freebsd on the same segment ? if so, are they using the same router/gateway ? No, there is the same CISCO Router between the two boxes. did you customize/set up things, like ipfw or set specific things via sysctl ? I tried to modify the tcp window size but the problem is stille here. What tcp trace will be useful to understand this problem ? Regards, ptitoliv ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bandwidth Problems with Freebsd 5.x
Donald J. O'Neill a écrit : Not hardly. I'll bet that 950kB/s for the Debian box was the peak download speed and it didn't maintain it through the entire download. Don The Debian Box is capable to make a 5 MB/s stable connection easily. Regards, Ptitoliv ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bandwidth Problems with Freebsd 5.x
Danial Thom a écrit : It seems unlikely that he'd get good throughput in one direction if the link was hosed. One dropped packets and you're shot. The easy way to test this is to eliminate the switch..hook the Freebsd box directly to the linux box. Impossible to do that because the boxes are rented by an hosting company. ptitoliv ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
