Re: 5.4 install disc1 will not find hard drive
On Sat, 14 May 2005, fbsd_user wrote: I have seen this problem on the questions list since 5.0 first can out as development version. Here 5.4 is now stable release and this problem is still not fixed. I have been using the same pc to test installing stable versions from miniinst.iso every version since 3.4 without any problems. Even 5.3-miniinst.iso worked just 2 weeks ago. The 5.4 stable does not have a miniinst.iso file so this time I used the disc1.iso to burn the install cd from and when booting from this cd I now get no hard drive found message from sysinstall (standard install) menu. This sure looks very strange to me as I can put in the cd burned from the 5.3-miniinst.iso file and the system installs just fine. Only difference is using disc1 this time. Even though the md5 CHECKSUM matched I downloaded and reburned disc1.iso again just to verify it was good. What hardware (motherboard, cpus, memory, etc.) are you using? Power management and APIC have been bios disabled since version FreeBSD 3.4 version so that is not the problem. I tried selecting safe option to boot and still get same error 'no hard disk found. My hard drive is an western digital 310100 on ata0 as master. When using this 5.4 install cd on other pc/ motherboard/ hard drive combos I get same error. You can hit Scroll Lock and use the arrow keys or page up/down to look at the boot messages. Near the bottom of the output should be the disk probe -- this may have more details. If not, try booting and selecting the verbose boot option. I think there is something wrong with the build process of the disc1.iso file. The miniinst.iso must be build using a different canned script that does not incorporated the bug that is in the disc1 build. Maybe the .ISO builds team needs to take a look at this problem. The only difference is the files included in the mkisofs run. The exact same files are used. And to continue on with this thought why does 5.4 NOT have a miniinst.iso file? That's a good question :-) I didn't realize we hadn't made one. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kde kdm mouse
On Sun, 15 May 2005, Vittorio De Martino wrote: I have the latest installation of freebsd 5.4 on my laptop, kde kdm 3.4. The laptop has a synaptic mousepad endowed of two buttons that in normal conditions are not used at all being enough to double-hit on the pad to have the same effect as that of pressing the left button. Now at boot time I enabled moused # ps ax|grep moused 493 ?? Ss 0:00.54 /usr/sbin/moused -p /dev/psm0 -t auto And the following in /etc/X11/xorg.conf Section InputDevice Identifier Mouse0 Driver mouse Option Protocol Auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 EndSection . Now it happens that: 1) If I start kde as a user by means of the command startx (having put startkde into .xinitrc) the mouse(-pad) works as expected: I can move around the screen and select and launch programs just moving on the pad and double hitting the pad . No problems! In a nutshell no need to press the left button. 2) If at boot time I start kde by means of kdm having put in /etc/ttys: ttyv8 /usr/local/bin/kdm -nodaemon xterm on secure and modified /etc/pam.d as required to autologin, I immediatedly and automagically login into kde as a user and the mouse works BUT... with the pad I can only move around the screen and the double-hit doesn't work anymore so that I have to use the left button cumpulsorily (and annoyingly). Why in your opinion is that crazy behavior and what should I do? Are the startx-launched and kdm-launched X daemons using the same config file? Check the top of /var/log/Xorg.*.log for sure. If you ran X -configure at some point it might be using a config out of your home directory and not in one of the system locations. When kdm starts it it doesn't look in your homedir :) -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tcpwrappers problem
On Mon, 18 Apr 2005, Didier Wiroth wrote: Hi, (using freebsd5.4-stable) I'm trying to display a ftpd banner with hosts.allow, but it doesn't work. I'm using ftpd (/usr/libexec/ftpd) started through inetd. Ined is started with standard flags: /usr/sbin/inetd -wW -C 60 In hosts.allow I have: ALL : ALL : allow ALL : ALL : banners /usr/local/etc/banners/ ALL : PARANOID : RFC931 20 : deny I wouldn't use tcpwrapper banners if you're doing more than just bitching out the user before kicking them off. Some FTP clients will just ignore your banner since it won't conform to the FTP protocol specification. If you want it to display when the user logs into your FTP server, put it in /etc/ftpmotd. If you want your telnet client to see it, put it in /etc/motd. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (LONG) ATA Benchmark: 5.x Reads Slower than Writes
On Fri, 8 Apr 2005, Danny Howard wrote: I don't have the time and hardware to do very scientific tests, but I have been able to run a series of benchmarks using bonnie++ on some systems I have available to me. The ATA-based gmirror performs extremely well, compared to a few Adaptec RAIDs that we have, EXCEPT that the sequential and random reads are MUCH SLOWER than the hardware solution, and even *slower than the preceding write operations*. This is counter-intuitive, especially since RAID1 implies slowed writes and faster reads. I tried the benchmark on my workstation (single 2.5 IDE in a laptop) and got comparable write-faster-than-read results. The raw data can be viewed at http://dannyman.toldme.com/scratch/benchmarks/ Could you place the 'dmesg' output for each system in this directory? The output here is marginally useful since it shows the bonnie command line. However, 100MB as the test filesize is really small unless the systems have 64MB of RAM though -- otherwise you're testing how well FreeBSD manages memory (or how much crap the systems are running when you run this test). For recent I/O tests I was doing with iozone I was using 10GB filesizes. This blows out the cache on just about everything. Unfortunately, my hardware RAIDs are on FreeBSD 4, and gmirror is on 5. My hardware RAIDs are on dual CPU systems, with 2G RAM, and my gmirror is on a single hyperthreaded CPU with 512M. Yes, sorry, not especially scientific. Maybe the changes in FreeBSD make a big difference? Maybe RAM makes a big difference? Yes, lots. Both 4.x vs. 5.x and RAM :) Sequential Read laptop 2.5 ATA: avg 76/s # SLOWER than write! gmirror ATA RAID1: avg 251/s # SLOWER than write! Adaptec SCSI RAID1: avg 7862/s Adaptec SCSI RAID10: avg 7618/s I'd be really careful here... that is # of files read per second after the create, and as pointed out before, SoftUpdates usually gets you a big win until it has to flush the directories out then things suffer during the actual flush op since the disk gets hammered. Lots of free memory to use for the directory cache helps. The disk cache on the RAID controller is buying you even more. From your results you were getting 9ms latency which is spot-on so I think you are simply misinterpreting your results here. File creation tests are usually more for filesystem-specific benchmarking than for throughput benchmarking. I'd suggest something more like iozone for throughput testing. If the volumes have nothing on them you care about then rawio can also be instructive. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IBM eServer 346 ServeRaid is too slow
In the future, don't cross post -questions and other lists. I'm leaving the cc: on since we may have people watching the thread, but please remove -questions for any followups. Thanks. On Thu, 7 Apr 2005, Brian Behlendorf wrote: On Thu, 7 Apr 2005, Carl Makin wrote: I'd say you are seeing the same as I am with the same card in a Dell 1855. There is something wrong with the mpt driver and the disks when they are setup in a raid0 set. If you split the disks and use them as individual drives then you will get full performance. It's also a known problem, though not being tracked very well. http://lists.freebsd.org/pipermail/freebsd-scsi/2004-December/001577.html http://lists.freebsd.org/pipermail/freebsd-scsi/2004-December/001578.html Doesn't look like (from viewcvs.cgi) there's been any recent work on this. We're waiting on a driver update that is tied up in legalities at the moment. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld fails on: === bin/domainname
On Mon, 21 Feb 2005, bsdnooby wrote: Yes it does. When I run cvsup -g -L 2 stable-supfile I see a bunch of errors with Head in them. here is one of them: Server warning: RCS file error in /cvs/cvsupd/prefixes/FreeBSD.cvs/src/bin/sh/var.h,v: 1: head expected Then when I run make buildworld, that fails What cvsup server are you using? It appears to be corrupted. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: installation on CompaQ pro work 5000
Setting followup to [EMAIL PROTECTED] On Fri, 17 Sep 2004 [EMAIL PROTECTED] wrote: the freebsd sistem give me that error when install : the disk in your drive looks more like an audio disk than a freebsd release ...the server is a CompaQ professional workstation 5000 dual processor... i have recopy the iso of freebsd... and not work... change cd rom ... and not work why give that error?(only with bsd...)all other sistem WORK... Make sure you are buring the disc as a data/ISO image and not an audio image. This macine is also very old .. its a dual ppro. Its pssible it has some unsual cdrom setup that freebsd does not support. xompaqs are prone to somewhat nonstandard setups. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: AMD64 vs i386 for FreeBSD
On Tue, 29 Jun 2004, Kenneth Culver wrote: It runs OK, with some minor nits compared to x86 version. I'm not sure what the laptop maker is talking about... but if you boot the x86 version of FreeBSD, it'll work. I think they meant you can't switch from amd64 to x86 after already booting an OS. Me either. -current actually supports running i386 binaries in amd64 mode. Thats one of the processor's features. :-) You can't run amd64 binaries when booted into an i386 OS, of course. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: 11b/g PCMCIA
On Mon, 17 May 2004, Pratt, Benjamin E. wrote: Hello, I know this is coming a while after this original topic was posted but I just got the same PCMCIA card and did some searching and didn't find any info about the card being supported as of yet. I am also fairly new to FreeBSD but am interested in knowing what I could do to help. I've got the card, I've been using the FreeSBIE live CD on my laptop (install on other machines) and could install on my laptop for testing but would like some sort of guide (if available) for how I can contribute. You need to update the wi driver to talk to it, so for starters you need to know how to hack device drivers, and hardware. Second, you'll need to get information on how to program the card from Proxim or some other source. From my recollection Proxim doesn't exactly hand out programming specs to all comers, if at all. If you haven't done device drivers before, I don't think there's a lot you can contribute, unless you want to learn device drivers first :) Thanks, Ben -- Original message from FreeBSD-Current on Thu Oct 9 08:49:21 PDT 2003 -- On Thu, 9 Oct 2003 wintran at email.cz wrote: Hi, does it plan to support PCMCIA card Proxim Orinoco model 8471-WD in FreeBSD? If someone wants to work on it and can get specs, sure. Doug White| FreeBSD: The Power to Serve dwhite at gumbysoft.com | www.FreeBSD.org -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PCI WiFi card problem
On Wed, 24 Mar 2004, Brian Henning wrote: I just bought a card with the 'BCM4301 802.11b IEEE 802.11b WLAN client chipset. Has there been any advances in support for this card? These types of cards are supported by the ndis driver in 5.x, which provides emulation for Windows netowrk device drivers. Search for Project Evil for information. :) -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ssh no longer connecting automatically
On Sat, 21 Feb 2004, Jonathon McKitrick wrote: Any idea why updating to 4.9 stable would give me this error? I have to set it to protocol 1 and log in manually. The auto login with the id_rsa and authorized_keys doesn't seem to work anymore, but gives this error: neptune:~ ssh [EMAIL PROTECTED] key_verify failed for server_host_key ssh -v might help, but I suspect your host key changed and you've configured strict checking. Is your client ssh.com or OpenSSH? NOTE: Please CC me, as I am not currently subscribed. Thanks. jm -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems with Adaptec SCSI adapter and IBM harddrives
Please don't crosspost lists, particularyl -questions and something else. Thanks. On Sun, 15 Feb 2004, Anatoliy Dmytriyev wrote: Hello, everybody! I need to install a scsi system on my 4.9 freebsd box and used the scsi card Adaptec 29160 Ultra160 SCSI adapter and external cabinet with the IBM drive: IBM IC35L146UWDY10-0 S23C. After stratup FreeBSD detected Adaptec and hard drive, I did fdisk, label and newfs without any problems, but when I tried copy data on this scsi disk I got error messages: (da0:ahc0:0:6:0): SCB 0x3 - timed out The usual culprit hiere is a bad cable or termination. Recheck your connections and chain layouts. Adaptec's site has troubleshooting tips for SCSI chain issues. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Can't login to 5.2-RC1, must hard reboot
On Sat, 7 Feb 2004, sammy!!! wrote: I get the following error messages in my logfile, a lot. Feb 7 18:40:22 cooper sshd[806]: set class 'me' resource limit datasize: Operation not permitted Feb 7 18:40:22 cooper sshd[806]: set class 'me' resource limit stacksize: Operation not permitted Feb 7 18:40:22 cooper sshd[806]: set class 'me' resource limit maxproc: Operation not permitted Feb 7 18:40:22 cooper sshd[806]: set class 'me' resource limit openfiles: Operation not permitted Looks like you've configured a custom login class (in /etc/login.conf), and set the limits higher than you're allowed to as a user. Check that the limits set in /etc/login.conf are appropriate, then use cap_mkdb to rebuild the database. Considering you have an aac controller, you are probably hitting the getblk off-by-one bug that Scott fixed the other day. Update your -current or apply the patch from the lists. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem installing 5.2.1
On Sat, 7 Feb 2004, T. Green wrote: I am trying to install version #5.1, #5.2, and #5.2.1 on my computer. i have version # 4.9 installed and it work fine. my system have the intel motherboard D875PBZ,1024mb of memory, 1 seagate 80gb ata drive, and 1 seagate 80gb sata drive. Try taking the SATA controller out of native mode. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Install bug - 4.9 stable - post install circular reboot
On Tue, 17 Apr 2018, Kevin Berrien wrote: I can confirm an issue posted Dec 3rd, freebsd-stable maillist, titled 4.9 install buglet. I experience this bug running the install (various configurations) 100% of the time. After install, after system reboot, the boot loader comes up with F1: FreeBSD, and reboots continually forever. To test, I made 3 installs without issue using 4.8. So first, I'd like to confirm the bug report, and ask the following. Please qualify reboots continutally forever. It reboots after printing the F1: FreeBSD message, or after you press a key, or what? This sounds like a BIOS issue. boot0 uses only BIOS calls to do its work. Lots of problems like this are also caused by bad drive geometry. What is the partition layout on the disk(s) in the system? Hardware description? -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.1-CURRENT kernel compile error
On Thu, 1 Jan 2004, Philip M. Gollucci wrote: vegeta# cd /usr/share/example/cvsup vegeta# cvsup -g -L2 standard-supfile Did you check the standard-supfile before using it? You may have gotten source that you didn't think you did. In general you should copy this to a different location and edit it first to make sure you get the right thing. if_em.o: In function `em_process_receive_interrupts': if_em.o(.text+0x47f5): undefined reference to `vlan_tag_alloc' I think you have the wrong source. There is no vlan_tag_alloc in that entire file, or in the entire kernel (if fxr.watson.org is to be believed). Check standard-supfile, delete your compile directory, and try updating again. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-rc1 Install
On Mon, 22 Dec 2003, Lars [iso-8859-1] Köller wrote: - The disk images won't boot on my Adaptec 2940UW controller with the latest Firmware. I have to make an image by myself with mkisofs and cdrecord. After this all boots well. Odd... the Adaptec BIOS is known to have problems if you have missing or invalid DOS slice tables. Don't run using 'dedicated' mode with Adaptecs, at least with the first boot volume. Hmm, I don't really understand that, cause the downloaded image burn to a cdrw don't boot. If I use the same cd and rerecord it with mkisofs -b /cdrom/floppies/boot.flp /cdrom Ah, so the controller isn't picking up non-emulated cds. If its a separate controller you might check for a firmware update, or if its integrated check for a system BIOS update. The systems I have with embedded 2940s boot non-emulated discs fine. I've tracked it down. The problem was induced due to mess in the boot loader and BIOS disk order. The smart boot loader was not loaded from the first BIOS disk (ad0) but from the first SCSI disk. So it thinks the ad disk was BIOS HD3 .. After fixing that all runs well out of the box! Sorry! Cool. I've just trying to migrate my config and scripts from 4.9 to 5.2 so I'm able to fix the xperfmon3 compile problem. However, the usb mouse didn't work. Booting in 4.9 all runs well. In 5.2 the usbdev -v hangs about 5 seconds on the first hub. The mouse is recognized, but the cursor didn't move. (I've also cvsup to the latest sources and build my own kernel). Not sure here; the USB mouse on my home system (VIA KT400 chipset) works as expected. perhaps there are two mouseds running? -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2-rc1 Install
On Sat, 20 Dec 2003, Lars [iso-8859-1] Köller wrote: I'm trying to install a 5.2 system and have had a lot of trouble: - The disk images won't boot on my Adaptec 2940UW controller with the latest Firmware. I have to make an image by myself with mkisofs and cdrecord. After this all boots well. Odd... the Adaptec BIOS is known to have problems if you have missing or invalid DOS slice tables. Don't run using 'dedicated' mode with Adaptecs, at least with the first boot volume. - My installation isn't runable, cause the kernel don't find the rootfs Since you have FreeBSD installed twice and you are spanning IDE and SCSI disks, its entirely possible you're booting the wrong loader and its getting confused, or loader itself is getting confused because of the multiple FreeBSD installs. You should make sure that the 'rootdev' variable in the loader is set properly before jumping into the kernel. You can set it by dropping to the loader OK prompt and typing set rootdev=diskXs1a where X is the disk number, printed when loader starts up. Some BIOSes have lots of issues with booting across IDE and SCSI disks in the same system. - Disk configuration: - ad0 (s1: FreeBSD-4.0) - da0 (s1: FAT32, W98) - da1 (s1: FBSD-5.2) - da2 (s1: FAT32) -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dualbooting STABLE CURRENT
On Sat, 1 Nov 2003, Steve Wingate wrote: Nothing happens probably means its beeping but I can't hear it :) If that happens, its because boot0 and the BIOS can't figure out how to reach the partition, generally because the geometry is wrong. Try zeroing off the front end of the disk, partitioning it with DOS FDISK, then put FreeBSD on it. I don't like the sound of that. I'll just stick with STABLE until 5.x is really ready. -STABLE will have the same problem since its in boot0 and the BIOS, not the OS on the partition its trying to boot. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.1-RELEASE Windows XP dual-boot issues
On Mon, 30 Jun 2003, Andrew Boothman wrote: This seems to be a recurring problem after 5-RELEASE. I had exactly the same problem, and I know of others that are the same. For some reason -current doesn't seem to be inter-operating well with the WinXP/Win2k loader anymore. I'm not sure if it's only happening to some installations - but I was certainly in the same boat. I ended up having to re-install Win2k and I used Grub as my new bootloader. Can't say I'm having any boot0 issues here with -current and win2k pro sp3. Note windows is partition #2 and about 40GB in. -- Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
