rarraa AAmerica
Lets all be thankful as hell Because the statuue of the Liberty has began to smell. -- Regards Cliff [ Thi mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SCSI Bios complaints and Disk Slices
On Tue, Dec 17, 2002 at 10:59:37AM -0800, Nate Lawson wrote: On Tue, 17 Dec 2002, Cliff Sarginson wrote: Windows .. fine, I installed Linux .. fine. Then I installed FreeBSD...fine *but* the SCSI BIOS on bootup complains that the disk geometry is all cockeyed, and it looks that way from what it says. It warns any non-DOS O/S may have problems using it. Well I have had no problems, and fdisk makes no complaints. What has happened to upset the SCSI BIOS ? The thing it seems to hate is that it is getting 63 heads reported instead of 64. It is a Tekram 390 U/W controller, with an IBM 18MB U160 disk. There have never been any other complaints about the 1st SCSI disk. Diagnostics show no problems. One thing to check is that you should have 1GB drive support enabled. This needs to be done before installing. See the archives for freebsd-scsi list. I am not familiar with trm(4) so perhaps Oliver can fill in more. Yes, that is going to be a lot of work :( What is strange is that it is only the SCSI BIOS on the Tekram board that is complaining. Everything seems to be working fine. And I have never had complaints about the first SCSI disk, which is my main FreeBSD Stable system in constant use ! Well, I will have to think on how I am going to do this, it will I guess also affect the SCSI BIOS view of the first disk as well. Mmm. What Sherlock Holmes would call a 2 pipe problem. Thanks for the answer. -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SCSI Bios complaints and Disk Slices
On Thu, Dec 19, 2002 at 07:56:02PM +0600, Maxim M. Kazachek wrote: Tekram DC 390 works under sym(4)... Except 390T which is powered by AMD... Cliff Sarginson: Perhaps you need try to play with disk geometry in fdisk... Try to see what geometry is 1st disk and try set something same on 2nd. Actually, FreeBSD reports the correct geometry in the startup messages, but fdisk gives the insane geometry the SCSI BIOS complains about. So with due precaution I set the geometry in fdisk to what it should be and it is, or appears to all be fine. I think the 1GB option in the controller is not actually relevant, it has to do with the old 1GB--8GB limitations I think. Mmm. Well it *looks* like it should now. -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5.0-RC1: X server crash
On Mon, Dec 16, 2002 at 09:55:09PM +0100, Marc Fonvieille wrote: On Mon, Dec 16, 2002 at 07:07:01PM +0100, Paolo Pisati wrote: Please, try to run the memtest program (it's in the ports tree): i had a SERIOUS problem of memory corruption with my laptop (PIII, Intel815E, ATI Radeon M6, etcetc) with STABLE when i loaded the agp module. I reported this problem to the drm maintainer but he was unable to solve it... =P Run the memtest for a bit, and then report the result, maybe there's a strange bug floating around, or maybe i'm just drunk... =) We talked about a problem between X and -CURRENT, we had no problem with -STABLE. Btw I don't see how memtest can report memory corruption, I thought it was to test hardware problem. It is. Memtest will not tell you squat about this (unless you have real memory faults .. ). -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Sysinstall [ was Re: 5.0-RC1 install: disklabel editor ]
On Tue, Dec 17, 2002 at 12:39:32AM +0100, Harald Hanche-Olsen wrote: + Kevin Oberman [EMAIL PROTECTED]: | In any case, in the disklabel screen down-arrow until you get to the | partition you want to use as swap. Note the size and press 'D' to | delete it. Then up-arrow to the entry at the top of the screen for the | slice the swap will be created in. Press 'C', enter the value for the | size of the swap space, press enter, and then select Swap. Bingo! | You have swap. This fits my memory too, but now after entering the size, I get directly to the question on naming the mount point. Before that, if I remember right, there used to be a question whether I wanted swap or a file system. That question no longer appears. Yes and yes. With a fresh install I noted you do not get the Q about swap/fs. I noted as well you get swap if you select auto. I noted as well that if the sysinstall happens to find a swap area from a previous area it shows it as such, but will not use it without delete/create. Sysinstall is busted in other areas as well. Select all no-longer puts ticks in the boxes, if you tick each seperately it asks you every time if you want to install the ports, after every tick, and once again at the end. When I tried to configure an X-Server, it took me to the X-Client menu...sysinstall if that is posible has become more than a PITA than it always has been. -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
SCSI Bios complaints and Disk Slices
Hi, I installed a second SCSI disk on a system. For testing I installed Windows .. fine, I installed Linux .. fine. Then I installed FreeBSD...fine *but* the SCSI BIOS on bootup complains that the disk geometry is all cockeyed, and it looks that way from what it says. It warns any non-DOS O/S may have problems using it. Well I have had no problems, and fdisk makes no complaints. What has happened to upset the SCSI BIOS ? The thing it seems to hate is that it is getting 63 heads reported instead of 64. It is a Tekram 390 U/W controller, with an IBM 18MB U160 disk. There have never been any other complaints about the 1st SCSI disk. Diagnostics show no problems. -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 5.0 performance (was: 80386 out of GENERIC)
On Tue, Dec 17, 2002 at 03:45:22AM +0200, Giorgos Keramidas wrote: On 2002-12-17 10:57, Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Monday, 16 December 2002 at 10:09:48 -0800, Chris Doherty wrote: 2) I'm scared that 5.0 is going to be unpleasantly slow on my p2-366, let alone a 386. I'm running it diskless on a K6/233. I'm surprised how snappy it is. I still have the Pentium 133 with 64 MB or memory that I used to run 5.0-CURRENT until a few weeks ago. I haven't got any real numbers, but the general `feel' of the system was pretty good. Trying to build world kernel on a 386 though... now that's a very different story! :) Yup. But the slowness people are noting in general is explained in UPDATING, and is quite understandable at this point in 5.0's evolution. It certainly takes a *lot* longer than 4.7 (test machine 1GHZ Pentium III, 512MB memory, SCSI disk). Also didn't someone mention that GCC has got slower anyway ? -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: I'm impressed, but ...
On Sat, Dec 07, 2002 at 08:41:35PM +0100, Philip Paeps wrote: On 2002-11-25 01:49:34 (+0100), Philip Paeps [EMAIL PROTECTED] wrote: Perhaps someone can make sense of this? I'm happy I can read my mail now, without having to kick the power button every so often, but I'd prefer to store my mail here and have the mailserver write over NFS. (Mainly for speed reasons). I suspect file locks across NFS as a possible source of this kind of problem. -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Current and Stable and Disk Slice problems
Hello, I know there has been some exchanges over these problems, but I am not sure I yet understand if a problem remains (I am obviously writing because one seems to :) I have on one of the systems here Linux, FreeBSD-Stable and FreeBSD-Current. All upto-date as of a few days ago. They all seemed to be co-existing merrily on the same disk until today. I did some extensive setting-up of -current so it looks more like my current stable system (mail and cron jobs etc). I mounted some 4.7 FS'es to copy some scripts and stuff (read-only). However, I can no longer boot 4.7. Grub says the partition does not exist. However fdisk on all 3 systems say otherwise. I have tried forcing a re-write of the partition table on the system, but it makes no difference. Current complains like buggery about the disk geometry being wrong, but I get so used to seeing that in FreeBSD since I started using it, maybe I don't give it enough credence (since fdisk says it is going to use it's idea of the geometry anyway). Now before I do it, I want to ask is it wise under Current to fix the Geometry as per what the BIOS says or not. Since this is my experimental machine it is only a question of my time being needed (and what's time ?) there is no priceless data at stake. The disk is layed out: Slice 1 (0 for Grub) Linux, this is extended DOS LBA so Linux is on 5,6,7 etc within that. Slice 2 (1 for Grub) 4.7 Stable Slice 3 (2 for Grub) Current Rest is unallocated space, easily enough for another FBSD slice if experimentation is required. I am wondering if it is this pesky Linux extended partition that is the problem. I faintly recall long-ago reading that you should not put FBSD partitions after an extended DOS one. Is this still true ? I am sure I have done this before on other systems., easily enough for another FBSD slice if experimentation is required. I am wondering if it is this pesky Linux extended partition that is the problem. I faintly recall long-ago reading that you should not put FBSD partitions after an extended DOS one. Is this still true ? I am sure I have done this before on other systems...but never with Current in the frame. If it is true (and I do not understand why it should be) maybe I have either a)not studied enough or b)it is not a widely known problem. I can send precise geometric details if it helps. -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Current and Stable and Disk Slice problems ..corrected
On Sat, Dec 07, 2002 at 11:43:54PM +0100, Cliff Sarginson wrote: Hello, I know there has been some exchanges over these problems, but I am not sure I yet understand if a problem remains (I am obviously writing because one seems to :) I have on one of the systems here Linux, FreeBSD-Stable and FreeBSD-Current. All upto-date as of a few days ago. They all seemed to be co-existing merrily on the same disk until today. I did some extensive setting-up of -current so it looks more like my current stable system (mail and cron jobs etc). I mounted some 4.7 FS'es to copy some scripts and stuff (read-only). However, I can no longer boot 4.7. Grub says the partition does not exist. However fdisk on all 3 systems say otherwise. I have tried forcing a re-write of the partition table on the system, but it makes no difference. Current complains like buggery about the disk geometry being wrong, but I get so used to seeing that in FreeBSD since I started using it, maybe I don't give it enough credence (since fdisk says it is going to use it's idea of the geometry anyway). Now before I do it, I want to ask is it wise under Current to fix the Geometry as per what the BIOS says or not. Since this is my experimental machine it is only a question of my time being needed (and what's time ?) there is no priceless data at stake. The disk is layed out: Slice 1 (0 for Grub) Linux, this is extended DOS LBA so Linux is on 5,6,7 etc within that. Slice 2 (1 for Grub) 4.7 Stable Slice 3 (2 for Grub) Current Rest is unallocated space, easily enough for another FBSD slice if experimentation is required. snip of cut and paste mess I am wondering if it is this pesky Linux extended partition that is the problem. I faintly recall long-ago reading that you should not put FBSD partitions after an extended DOS one. Is this still true ? I am sure I have done this before on other systems...but never with Current in the frame. If it is true (and I do not understand why it should be) maybe I have either a)not studied enough or b)it is not a widely known problem. I can send precise geometric details if it helps. -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Any ideas at all about network problem?
On Mon, Dec 02, 2002 at 01:27:34AM -0800, Terry Lambert wrote: [ ... bad throughput on bad NICs ... ] Mmmm. I use these RTL cheapo nics. I accept the fact they have a bad reputation. However I have used them for some time, and they have behaved impeccably. I have noticed no change in throughput on 5.0 either, and since I have downloaded loads off stuff which comes through my firewall and then via the LAN to the 5.0 test machine I think I would have noticed if it was slower than normal. Having said that I have not checked the throughput, but then nothing has happened to make me want to check it. I run 4-7 Stable updated at least once a week, and the latest patched 5.0 from a few days ago. The network also runs through a fairly cheapo switch. Maybe I just get lucky, touch wood (or my anti-static wrist band :). My problem is that extensive use of my hoover sometimes makes some of the computers stop, but I don't think a slightly overloaded electrical system can be solved in software... -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
fdisk conflict between 4.7-stable and 5.0-DP2
Hello, I have 2 IDE masterd disks. On the 2nd disk I have a windows installation on the first slice, and a Release 5.0 on slice2. The rest of the disk is unallocated. Running fdisk on 5.0 reports this accurately. If I run fdisk on 4-7 Stable and look at the 2nd disk, it tells me that my 5.0 slice is slice 4 (which does not exist). All systems work fine using grub. Any explanation for this anomaly ? Thanks. -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
X11, KDE, WM, Gnome and current
I rebuilt the whole of KDE on DP2 (upto date as of a couple of days ago). Apart from me growing older in the process nothing worked well, despite using the same configuration as on 4.7. - It starts but no sound arises - The mouse moves, responds to clicks sometimes, but when I bring up the menu and move the mouse it brings up the box asking what command you want to run. - Lots of errors reported about bad file descriptors. - Gives a default resolution that is not the one I set. - I.e unusable. Windowmaker does not work, either...sort of similarly. Also says /dev/dsp does not exist. Gnome ... well it bitched about the window manager, but otherwise showed similar symptoms to KDE. I think the problem must lie in X itself. Well it exercised DP2 pretty well in building it. But it did not produce a usable GUI in all 3 cases. System is 512MB, PIII 1Ghz, Matrox G450 AGP, Soundblaster Live! Value. Plus Logitech Cordless USB Optical Mouse. Am I being premature, there does not seem to be a KDE Package for 5.0. When I tried to fetch it all I got was one file, that new groovy theme that KDE comes with. -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: more -current testers
On Wed, Feb 20, 2002 at 10:56:05AM +0200, Maxim Sobolev wrote: Michael Lucas wrote: I understand that we're getting to that stage where we need more -current testers. We all agree that the optimal thing would be to have hordes of very sophisticated users who can debug problems on their own and submit patches to fix all their issues. I would guess that we all also agree that that's not going to happen. It seems that the best we can hope for is to educate some of the braver users who are ready to take the next step and are willing to donate some time to us. I'm considering doing a series of articles on testing FreeBSD-current, including: setting up for kernel dumps, what to type at the debugger prompt after a crash, filing a decent bug report, what to expect from -current, and so on. I would also make it clear when to not bother filing a bug report (i.e., You crashed, but had no WITNESS? Sorry, enable WITNESS try again.). This would be (I suspect) three articles, running about a month and a half. The last time I checked, I get 12-15 thousand readers for each article. One half of one percent uptake would (hopefully) be quite a few bug reports. Has some kind of conclusion been arrived at on this ? It has gone quiet since Feb 20th, I am definitely interested. -- Regards Cliff Sarginson -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: NetBSD-style rc.d Project
On Wed, Feb 27, 2002 at 02:02:11AM -0800, Doug Barton wrote: On Tue, 26 Feb 2002, Crist J. Clark wrote: Looking at the repository, I have not really seen anything done with building a NetBSD-style rc.d system that will provide FreeBSD functionality for a long time. Several of us have started on this, and either run out of time, or interest (as you've seen described already). There are at least three problems I can see with this project, in no particular order. A) Everyone in the project thinks they know both the problems and the solutions. B) Everyone who is willing to do actual work on the project (myself included) has strong ideas about how it should go, often incompatible with other's strong ideas. C) The real problem of making this work is actually much bigger than the just do a straight port drum that most of the people who aren't actually willing to put the work into it beat rather loudly whenever the topic comes up. Currently I don't have nearly as much time to work on this project as I thought I would by now. I moved to the bay area in september and was hoping feverishly that the many hours of overtime required to get in the groove of my new job would slow down, and to some extent they have, but I'm barely getting back up to speed on current -current, which I personally think of as a pre-req for doing the rc work. What I have always said we need before people spend a lot of time on coding is discussion about what the project should look like. If people are interested in this, I set up a discussion list on Yahoo! groups, and a few people actually subscribed. If there is still interest in discussion about what the project should look like, I think I'm ready to go on that if people still think my experience with the existing rc system is worth including. I am interested. -- Regards Cliff Sarginson -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: more -current testers
On Tue, Feb 19, 2002 at 12:50:11PM -0500, Michael Lucas wrote: I understand that we're getting to that stage where we need more -current testers. We all agree that the optimal thing would be to have hordes of very sophisticated users who can debug problems on their own and submit patches to fix all their issues. I would guess that we all also agree that that's not going to happen. It seems that the best we can hope for is to educate some of the braver users who are ready to take the next step and are willing to donate some time to us. I'm considering doing a series of articles on testing FreeBSD-current, including: setting up for kernel dumps, what to type at the debugger prompt after a crash, filing a decent bug report, what to expect from -current, and so on. I would also make it clear when to not bother filing a bug report (i.e., You crashed, but had no WITNESS? Sorry, enable WITNESS try again.). This would be (I suspect) three articles, running about a month and a half. The last time I checked, I get 12-15 thousand readers for each article. One half of one percent uptake would (hopefully) be quite a few bug reports. My question to the community is: is it too early to do this? If I start now, the articles would probably appear April-May. I think this is an absolutely splendid idea :) I have enough resources to run a STABLE system for my day-to-day use and also have a -CURRENT system I am more than willing to spend some time on. I think some good pointers on what is required to provide useful feedback (as opposed to bug reports that are not adequately filled in) and some practical tips would really encourage people. My first question is who or what is WITNESS :) -- Regards Cliff Sarginson -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: fxp driver not reset after Windows reboot?
Hello I have the self same problem with my nics' Realtek 8139's. But on my '98 machine it is dual bootable with Linux. If I don't power cycle the PC between using windows and Linux my nic's are unusable, gaining a MAC address of as I see yours does. I have found no solution for it (even swearing doesnt help) but since it so similar to your problem and with both Linux and FreeBSD we have been Gate'd again Cliff On Sunday 10 December 2000 13:08, Mark Huizer wrote: Hello, On my VAIO laptop, I have trouble rebooting directly from Windows to FreeBSD (luckily enough I don't run Windows that often :-) I tried to look at the driver code, but it looks to me like it is doing resets when attaching the fxp driver, but somehow, Windows has left it in the state where it isn't recognized properly. Below I have dmesg output, stripped to the fxp0 part. Does anyone have an idea what the problem might be, or where to try to debug this? I have added some comments to the dmesg output, /* here */, to add the programs running there Mark FreeBSD 5.0-CURRENT #0: Wed Dec 6 09:34:39 CET 2000 [EMAIL PROTECTED]:/usr/src2/sys/compile/vaio Preloaded elf kernel "kernel" at 0xc042b000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc042b09c. Preloaded elf module "if_fxp.ko" at 0xc042b0ec. fxp0: Intel Pro 10/100B/100+ Ethernet port 0xfcc0-0xfcff mem 0xfed0-0xfedf,0xfecff000-0xfecf irq 9 at device 11.0 on pci0 fxp0: Ethernet address ff:ff:ff:ff:ff:ff, 10Mbps BRIDGE 990810, have 7 interfaces -- index 1 type 6 phy 0 addrl 6 addr ff.ff.ff.ff.ff.ff /* dhclient leads to the below */ fxp0: SCB timeout fxp0: SCB timeout fxp0: SCB timeout fxp0: DMA timeout fxp0: SCB timeout fxp0: DMA timeout fxp0: SCB timeout fxp0: SCB timeout fxp0: warning: unsupported PHY, type = 63, addr = 255 /* IPv6 router sollicitation below */ fxp0: SCB timeout fxp0: SCB timeout fxp0: SCB timeout fxp0: SCB timeout fxp0: DMA timeout fxp0: SCB timeout fxp0: DMA timeout fxp0: SCB timeout fxp0: SCB timeout fxp0: warning: unsupported PHY, type = 63, addr = 255 /* various stuff like apache etc below */ fxp0: SCB timeout fxp0: SCB timeout fxp0: SCB timeout fxp0: DMA timeout fxp0: SCB timeout fxp0: DMA timeout fxp0: SCB timeout fxp0: SCB timeout fxp0: warning: unsupported PHY, type = 63, addr = 255 fxp0: SCB timeout fxp0: SCB timeout fxp0: device timeout fxp0: SCB timeout fxp0: SCB timeout fxp0: SCB timeout fxp0: DMA timeout fxp0: SCB timeout fxp0: DMA timeout fxp0: SCB timeout fxp0: SCB timeout fxp0: warning: unsupported PHY, type = 63, addr = 255 fxp0: SCB timeout fxp0: SCB timeout fxp0: device timeout fxp0: SCB timeout /* etc etc */ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
