(no subject)
Dear list, I have the following problem when using rmuser (freebsd 6.2) -- rmuser -v hana Matching password entry: hana:*:1091:1092::0:0:/usr/home/hana:/usr/sbin/nologin Is this the entry you wish to remove? yes Remove user's home directory (/usr/home/hanka)? yes Removing crontab for (hana):. Removing at(1) jobs owned by (hana): 0 removed. Removing IPC mechanismsipcs: sysctlbyname: kern.ipc.shmmax: No such file or directory ipcs: sysctlbyname: kern.ipc.shmmax: No such file or directory ipcs: sysctlbyname: kern.ipc.shmmax: No such file or directory . Terminating all processes owned by (hana): -KILL signal sent to 0 processes. Removing files owned by (hana) in /tmp: 0 removed. Removing files owned by (hana) in /var/tmp: 0 removed. Removing mail spool(s) for (hana): /var/mail/hana. Removing user (hana) (including home directory) from the system: Done. --- The problem started, when I accidentaly deleted /usr/home directory and I had to create a new one. I checked /etc/password file and the direcory existed before using rmuser. Can anybody help please? Lubos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: need help getting lpr/lpt working again.
On Fri, Feb 15, 2008 at 12:47:30PM -0800, Gary Kline wrote: People, Can anybody clue me in on getting my hp500 working? I don't care if I use CUPS or the old way with lpd and lpr. There is no /dev/lpt0 in /dev, and /etc/devfs.* does not create this file. So, first question is: how to create /dev/lpt0, mod 0666/ I've used /etc/printcap and postscript successfully for years. thanks, gary Have you put: lpd_enable=YES in /etc/rc.conf and tried starting up the daemon? -- Frank Contact info: http://www.esperance-linux.co.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Stuck on loader.conf
Hi All, As a newbie on freebsd I eagerly played this featureful OS, now my last one being the serial console, sure enough my two fsbd box can connect to each other console via com port/null-modem connection, unfortunately as I had already finished I revert but the old entry on /etc/ttys but forgot to take out the console=comconsole on /boot/loader.conf. As of of now I had lost connection via com port and worst stuck on boot at loader.conf section. Though erasing the whole OS would just take a minute, I look at this as an opportunity to learn how to approach, in case on a real production box. How shall I proceed? Stuck on loader at infinity, --joseph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Stuck on loader.conf
As a newbie on freebsd I eagerly played this featureful OS, now my last one being the serial console, sure enough my two fsbd box can connect to each other console via com port/null-modem connection, unfortunately as I had already finished I revert but the old entry on /etc/ttys but forgot to take out the console=comconsole on /boot/loader.conf. As of of now I had lost connection via com port and worst stuck on boot at loader.conf section. 1) connect the console back, boot single user and fix loader.conf 2) boot from install/live cd, mount root partition and fix loader.conf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem with network card in P35+ICH9
On Dec 9, 2007 4:00 PM, Playnet [EMAIL PROTECTED] wrote: I have a server based gigabyte MB with core2 quadro, P35+ICH9 From the below let me guess it is in the MSI Neo familiy of Mobo's you will want the following patches for re: http://people.freebsd.org/~yongari/re/re.HEAD.patch If I am right about the Mobo you should also be getting mismatching reports on your SATA drives as well the inablity to have SATA and PATA together you will want the following patches to fix that: http://www.flosoft-systems.com/patchs/ahci.diff http://www.flosoft-systems.com/patchs/i82801-marvell.diff Patch for RE not compiling.. When these pathes will be included in the kernel? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I own a MSI P35 Neo with following chips [1]: One Ultra DMA 66/100/133 IDE controller integrated in Marvell(R) 88SE6111 SATAII controller integrated in ICH9/ICH9R and Marvell(R) 88SE6111 chipest Supports AHCI controller with SATA RAID 0/1/0+1/5 or JBOD mode by ICH9R Supports one SATAII port by 88SE6111 Supports PCI Express LAN 10/100/1000 Fast Ethernet by Realtek 8111B 1st problem: PATA DVD drive: boots the kernel from install cd - can't mount root fs from cd for installation 2nd problem: PATA HDD drive: is not recognized too 3rd problem: I can't tell you if the nic works because i can't boot any FreeBSD Live CD (Linux too) nor install FreeBSD to a PATA drive The SATA ports are recognized by the system as far as i saw on the boot messages so the ICH9/ICH9R shouldn't be the problem. Google won't tell me much about the Marvell 88SE6111 so i wonder if someone's out there who can code or already has a compiled driver driver for this piece of hardware. Unfortunately I can't compile my own kernel because I only have this one computer... There was a conversation on current@ a few months ago [2] but i think it stopped without any result. Last but not least a few links I found while searching for help: - http://lists.freebsd.org/pipermail/freebsd-bugs/2007-August/025584.html - http://butcher.heavennet.ru/patches/kernel/ata/marvell/README.txt [1] http://www.msi-computer.de/index.php?func=proddescprod_no=1215maincat_no=1 [2] http://lists.freebsd.org/pipermail/freebsd-current/2007-October/077591.html -- ~ vb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem with network card in P35+ICH9
I own a MSI P35 Neo with following chips [1]: One Ultra DMA 66/100/133 IDE controller integrated in Marvell(R) 88SE6111 SATAII controller integrated in ICH9/ICH9R and Marvell(R) 88SE6111 chipest Supports AHCI controller with SATA RAID 0/1/0+1/5 or JBOD mode by ICH9R Supports one SATAII port by 88SE6111 Supports PCI Express LAN 10/100/1000 Fast Ethernet by Realtek 8111B 1st problem: PATA DVD drive: boots the kernel from install cd - can't mount root fs from cd for installation get 6 at boot loader and set hw.ata.atapi_dma=0 boot SATA works fine. i have similar motherboard, forget about Realtek 8111B it's terrible. buy some normal network card, or - use realtek but with hardware checksumming off. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Rebuild Problem
Hi: Strange problem here. /usr/local got wiped for no reason I can think of. I can´t even change the pw. Nothing on this build anyway. But went to rebuild (6.2) and got caught in a loop in these steps: -- Select Drive -- FDISK Partition Editor (Q) -- Install Boot Manager I would prefer to rebuild because I want to add X Windows and I´d rather not have to rebuild the kernel. How can I wipe the drive? If I cannot rebuild, can I just add the ports? What about changing pw? TIA, Tony More new features than ever. Check out the new AOL Mail ! - http://webmail.aol.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (no subject)
On Sat, 2008-02-16 at 09:11 +0100, Lubomir Matousek wrote: Dear list, I have the following problem when using rmuser (freebsd 6.2) -- rmuser -v hana Matching password entry: hana:*:1091:1092::0:0:/usr/home/hana:/usr/sbin/nologin Is this the entry you wish to remove? yes Remove user's home directory (/usr/home/hanka)? yes Removing crontab for (hana):. Removing at(1) jobs owned by (hana): 0 removed. Removing IPC mechanismsipcs: sysctlbyname: kern.ipc.shmmax: No such file or directory ipcs: sysctlbyname: kern.ipc.shmmax: No such file or directory ipcs: sysctlbyname: kern.ipc.shmmax: No such file or directory . Terminating all processes owned by (hana): -KILL signal sent to 0 processes. Removing files owned by (hana) in /tmp: 0 removed. Removing files owned by (hana) in /var/tmp: 0 removed. Removing mail spool(s) for (hana): /var/mail/hana. Removing user (hana) (including home directory) from the system: Done. --- The problem started, when I accidentaly deleted /usr/home directory and I had to create a new one. I checked /etc/password file and the direcory existed before using rmuser. Can anybody help please? Lubos Looks like the problem is that somewhere within there it's expected that the home directory isn't /usr/home/hana, it's /usr/home/hanka Have you checked /etc/master.passwd to make sure that there's no mis-entry in there? Or just try creating /usr/home/hanka and see if it works itself out. James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mysql client
Hi all, Just after upgrading the mysql client to mysql-client-5.1.23 on 6.3, it seems that it's completely ignoring ~/.my.cnf. Anyone else has this problem? Peter -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
disk error
Hi all, Just found these messages in my logfile. Is it something to worry about? I've never seen them before upgrading to 6.3. ra kernel: ad0: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=281550271 ra kernel: ad0: FAILURE - READ_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=281550271 ra kernel: g_vfs_done():ad0s1f[READ(offset=138248126464, length=16384)]error = 5 ra kernel: handle_workitem_freeblocks: block count ra kernel: handle_workitem_freeblks: got error 5 while accessing filesystem Peter -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: disk error
On Sat, 2008-02-16 at 17:59 +0100, Peter Boosten wrote: Hi all, Just found these messages in my logfile. Is it something to worry about? I've never seen them before upgrading to 6.3. ra kernel: ad0: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=281550271 ra kernel: ad0: FAILURE - READ_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=281550271 Yea -- normally that means a bad sector(*), and where there's one, there's bound to be more. Failed drive eventually. I would pull this server from rotation and run a full surface sector scan on it (download an ISO of Hiran's Boot CD) Or if its a geom mirror raid-1, test this component. If it was scsi, I would recommend camcontrol(8) to query the disk for a list of grown defect sectors. ~BAS *. If you've never seen it before and it developed. Bad cables/controllers/drives/interference can cause it too, but you would have seen it from inception. ra kernel: g_vfs_done():ad0s1f[READ(offset=138248126464, length=16384)]error = 5 ra kernel: handle_workitem_freeblocks: block count ra kernel: handle_workitem_freeblks: got error 5 while accessing filesystem Peter ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Shutdown anomaly
I am seeing the following messages, which appear to indicate a memory overwrite: Waiting (max 60 seconds) for system processs 'vnlru' to stop...done Waiting (max 60 seconds) for system processs 'bufdaemon' to stop...done a iStyinncgi n(gm adxi s6k0s ,s evcnoonddess) rfeomra isnyisntge.m. .pr0o cess 'syncer' to stop...0 0 done All buffers synced. Uptime: 8m9s Here's what the messages usually look like: Waiting (max 60 seconds) for system processs 'vnlru' to stop...done Waiting (max 60 seconds) for system processs 'bufdaemon' to stop...done Waiting (max 60 seconds) for system processs 'syncer' to stop... Syncing disks, vnodes remaining...3 2 1 0 0 0 done All buffers synced. Uptime: 4h23m18s I can reproduce this by simply rebooting to single user, mergemaster -p, make installworld, mergemaster, halt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (no subject)
James [EMAIL PROTECTED] wrote: On Sat, 2008-02-16 at 09:11 +0100, Lubomir Matousek wrote: Dear list, I have the following problem when using rmuser (freebsd 6.2) -- rmuser -v hana Matching password entry: hana:*:1091:1092::0:0:/usr/home/hana:/usr/sbin/nologin Is this the entry you wish to remove? yes Remove user's home directory (/usr/home/hanka)? yes Removing crontab for (hana):. Removing at(1) jobs owned by (hana): 0 removed. Removing IPC mechanismsipcs: sysctlbyname: kern.ipc.shmmax: No such file or directory ipcs: sysctlbyname: kern.ipc.shmmax: No such file or directory ipcs: sysctlbyname: kern.ipc.shmmax: No such file or directory . Terminating all processes owned by (hana): -KILL signal sent to 0 processes. Removing files owned by (hana) in /tmp: 0 removed. Removing files owned by (hana) in /var/tmp: 0 removed. Removing mail spool(s) for (hana): /var/mail/hana. Removing user (hana) (including home directory) from the system: Done. --- The problem started, when I accidentaly deleted /usr/home directory and I had to create a new one. I checked /etc/password file and the direcory existed before using rmuser. Can anybody help please? Lubos Looks like the problem is that somewhere within there it's expected that the home directory isn't /usr/home/hana, it's /usr/home/hanka Have you checked /etc/master.passwd to make sure that there's no mis-entry in there? Or just try creating /usr/home/hanka and see if it works itself out. Personally, I'm unsure where the problem is. The only suspicious thing I see is the inability to remove shared memory segments, which is a bit strange but not wholly unexpected. Did you build a kernel without shared memory? -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
IPv4 loopback address is missing, why?
HI, On my father's computer there isn't an IPv4 loopback address being assigned to the lo0 interface. What would cause this? I've looked at his configs and they're the same as on my system (obviously something is different, but I don't know what). I see in his /etc/defaults/rc.conf the ifconfig_lo0 line is *NOT* commented out or otherwise altered and his file looks the same as mine (at least on this point, I haven't contrasted the two entirely). So, why would his system not be configuring an IPv4 loopback address? After bootup, I can add the address manually using ifconfig. Andy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: disk error
On Sat, 16 Feb 2008, Peter Boosten wrote: Brian, thanks for your answer (and sugggestion). Isn't a drive supposed to mark a bad sector as bad and ignore it (that is: They ship with a certain number of unallocated sectors to reassign failed ones to (I dont think ATA/IDE disks have a way to ask this, maybe SMART). Once all of the silent allocations happen unbeknown to the user, then your suffering starts. Install smartutils and check these values: 5 Reallocated_Sector_Ct 0x0033 100 100 005Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067Pre-fail Always - 0 196 Reallocated_Event_Count 0x0032 100 100 000Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000Old_age Offline - 0 199 UDMA_CRC_Error_Count0x000a 200 200 000Old_age Always - 0 ~BAS not use it anymore)? -- http://www.boosten.org l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ Guilty? Yeah. But he knows it. I mean, you're guilty. You just don't know it. So who's really in jail? ~Maynard James Keenan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: disk error
Brian A. Seklecki wrote: On Sat, 2008-02-16 at 17:59 +0100, Peter Boosten wrote: Hi all, Just found these messages in my logfile. Is it something to worry about? I've never seen them before upgrading to 6.3. ra kernel: ad0: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=281550271 ra kernel: ad0: FAILURE - READ_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=281550271 Yea -- normally that means a bad sector(*), and where there's one, there's bound to be more. Failed drive eventually. I would pull this server from rotation and run a full surface sector scan on it (download an ISO of Hiran's Boot CD) Brian, thanks for your answer (and sugggestion). Isn't a drive supposed to mark a bad sector as bad and ignore it (that is: not use it anymore)? -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: To sourceforge or not to sourceforge
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Danny Pansters Sent: Thursday, February 14, 2008 5:24 PM To: freebsd-questions@freebsd.org Subject: To sourceforge or not to sourceforge Hi folks, II would like to sollicit opinions and advice on whether or not to put a project on sourceforge or perhaps somewhere else (better?) I have put kbtv1 on sourceforge as well as on my own website. Apart from getting to use sf.net as the first download location in its port I can't really say that it has been useful in any way. And updating it is a pain. Now that I'm starting to distribute kbtv2 (beta) I find myself wondering whether I should continue to use sf.net or just use my own site (and possibly some secondary location in one of our committers' webspaces under freebsd.org (easy to add to port). My primary objective with hosting my source (and to a lesser extend docs) elsewhere is availability (and to a lesser extend offloading data traffic). You know, just the simple thought what if I drop dead tomorrow. Are there better/simpler/faster alternatives to SF that people recommend? One thing I noticed with SF is that there's all sorts of me-too (that is marketing) websites that just scrape SF and then forever have outdated info and downloads. I don't find this desirable at all. And besides, if you're using FreeBSD you're going to use ports not some external stale copy of the source. BUT it appears that there *are* people downloading old crud from such sites. I tend to have the feeling that simply hosting it my damn self will work 99% of the time and cause fewest headaches, but I'm open to any suggestions. Hi Dan, Let me relate my own esperiences with http://www.freebsd-corp-net-guide.com When I wrote the book I mentioned in the forward I'd have a website setup for updates. I did set the site up, and had a pretty nice site for several years that got some use. But as time passed I updated the site less and less. Then the server the site was on crashed and lost some OS files. I got it back up and tarred up the site, fully intending to host it on different hardware. Well I hate to say it the site is still sitting in a tar file, despite that I have the hardware sitting here running BSD, doing nothing else, really. I agree that sf has attracted a really undesirable element, every bad thing you listed about it is true, plus it has gotten so big now that searching it for a particular project is terrible - Google is a better way to find projects on sf than sf's own search tools are. But, there is still one thing that sf does which can't be matched by hosting it yourself, and that is, to act as a historical archive. I have at least 6 different OSS projects that I've used on a semi-regular basis that were privately hosted at one time that are gone now, except for my personal archives. For example, take FreeIPdb. Sure, ipplan does the same thing and it is still available. But FreeIPdb had some advances in it that ipplan did not have. Furthermore, more importantly freeipdb's code (GPL) could serve as an excellent template for writing a similar program for some other developer. Sure, the drop dead factor is of a concern. But I think the liklihood is you personally will get tired of doing kbtv2 before the end of your own life. Hell, even George Lucas got tired of doing Star Wars, that's why we won't see any more Star Wars movies from him. But, other people aren't tired of it. The liklihood is that when you personally get tired or too old or whatever to stay interested in kbtv2, there will still be people interested in it. That is where sf becomes important. sf is one of these things that is more important to the community than to the developers who use it. Unless the project is really large and has a lot of participation, sf doesen't really offer the project developer much. But, a user picking up code from sf knows that even if the developer gets tired of it and loses interest, the code will still be there. One of the biggest loopholes in the various OSS licenses is that none of them guarentee the developer cannot extend control over the project. OSS licenses fundamentally assure the user that if the developer decides later he doesen't want the code out there, he cannot exercise control via copyright to snuff out the project and make it unavailable. But, the fundamental flaw all of them make is that if the project is a niche project, then if the developer decides to withdraw it, there's a good chance nobody will step up to the plate and fork the project. If that happens then a few years later you won't find the source for the project anywhere on the Internet, and there will be one more OSS project lost to the community. And if 10 years later someone comes along who needs a software package that did exactly what niche thing that this OSS package did, they won't have it. If the code is on sf, this sort
Re: disk error
On Sat, Feb 16, 2008 at 07:30:37PM +0100, Peter Boosten wrote: Brian A. Seklecki wrote: On Sat, 2008-02-16 at 17:59 +0100, Peter Boosten wrote: Hi all, Just found these messages in my logfile. Is it something to worry about? I've never seen them before upgrading to 6.3. ra kernel: ad0: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=281550271 ra kernel: ad0: FAILURE - READ_DMA48 status=51READY,DSC,ERROR error=4ABORTED LBA=281550271 Yea -- normally that means a bad sector(*), and where there's one, there's bound to be more. Failed drive eventually. I would pull this server from rotation and run a full surface sector scan on it (download an ISO of Hiran's Boot CD) Brian, thanks for your answer (and sugggestion). Isn't a drive supposed to mark a bad sector as bad and ignore it (that is: not use it anymore)? The drive can only remap bad sectors when you write to them. When you read from a bad sector the drive does not know what data was supposed to be there and thus can only return an error or return garbage data. Returning an error (which is what disks do) is a much better choice. -- Insert your favourite quote here. Erik Trulsson [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: FreeBSD6.2 What is the easiest Way to Capture RS-232 SerialData?
If that is SMDR phone system data your handling, once you get the program done would you mind posting a copy? Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Martin McCormick Sent: Thursday, February 14, 2008 11:02 AM To: freebsd-questions@freebsd.org Subject: Re: FreeBSD6.2 What is the easiest Way to Capture RS-232 SerialData? Warren Block writes: Depending on the switch, you may find that the /usr/ports/comms utilities atslog or cdr_read will do the work for you. Derek Ragona writes: You still need to handle when the cord is unplugged, or put the server in a secure location away from other people. If you want the program to be more capable of staying running you can have the program fork a child and if the child dies, fork a new child. This is the method used for many running services. Just be sure if the child dies the log file is closed and that same file is opened by the new child. Excellent ideas from both! Thank you. Martin McCormick ___ 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: Shutdown anomaly
On Sat, Feb 16, 2008 at 11:42:52AM -0500, Steven Friedrich wrote: I am seeing the following messages, which appear to indicate a memory overwrite: Waiting (max 60 seconds) for system processs 'vnlru' to stop...done Waiting (max 60 seconds) for system processs 'bufdaemon' to stop...done a iStyinncgi n(gm adxi s6k0s ,s evcnoonddess) rfeomra isnyisntge.m. .pr0o cess 'syncer' to stop...0 0 done All buffers synced. Uptime: 8m9s It's an interleaved buffer messages on SMP systems. The problem is known, but I haven't heard of a proposed solution yet. -- Jonathan Chen [EMAIL PROTECTED] -- The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem building loader in RELENG_7
Mike Clarke wrote: On Friday 15 February 2008, Erik Norgaard wrote: Hi: Just updated my source tree, I'm on FreeBSD bifrost 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #1: Tue Feb 12 09:52:32 CET 2008. Then I did [snip] /usr/src/sys/boot/i386/loader/../libi386/libi386.a(biosdisk.o)(.text+0xca9) : In function `bd_opendisk': : undefined reference to `uuid_is_nil' [snip] Anyone else experiencing similar problems? I tried this also a few days ago with the same problem, it seems it is persistent... Yes, I had the same problem with make buildworld in 6.3, and posted here earlier today. That is interesting, I have no problem with buildworld or buildkernel, only the loader. And the problem occurs when /usr/obj is empty. As I understand this is (or used to be?) how to build a loader with tftp support, has something changed? Thanks, Erik -- Erik Nørgaard Ph: +34.666334818 http://www.locolomo.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Shutdown anomaly
Jonathan Chen writes: I am seeing the following messages, which appear to indicate a memory overwrite: Waiting (max 60 seconds) for system processs 'vnlru' to stop...done Waiting (max 60 seconds) for system processs 'bufdaemon' to stop...done a iStyinncgi n(gm adxi s6k0s ,s evcnoonddess) rfeomra isnyisntge.m. .pr0o cess 'syncer' to stop...0 0 done All buffers synced. Uptime: 8m9s It's an interleaved buffer messages on SMP systems. The problem is known, but I haven't heard of a proposed solution yet. There is no fix. The workaround is to increase the size of the kernel printf() buffer. I don't remember how you do that ... but this is not a new issue - chech the archives for details. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Lockup on Boot due to ACPI (Freebsd 7.0-RC2 i386)
On Sun, Feb 10, 2008 at 11:49:20AM -0500, Jason Morgan wrote: I just upgraded a system from 6.3-RELEASE to 7.0-RC2 (both i386) only to discover that the system won't boot with ACPI enabled. ACPI was working fine in 6.3. The problems occur at boot-up -- the system simply stops loading at approximately the same place during each attempt (noted below in the dmesg). I have added `hint.acpi.0.disabled=1' to loader.conf to get around the issue automatically. I have tried building new kernels with various options added/removed, rebuilt world with updated source, etc. I have included my system information below. The dmesg output (a full boot with ACPI disabled) is `verbose' and I have edited it to show where the lockup happens. I am more than willing to help out with any debugging if needed. I just need some direction. [snip] This is still an issue. I updated my source today, rebuilt world and kernel (disabling SMP), and the system still freezes at boot with ACPI enabled. If anyone has any suggestions as to how I can work around the problem, they would be greatly appreciated. Cheers, ~Jason ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Shutdown anomaly
On Sat, Feb 16, 2008 at 05:43:17PM -0500, Robert Huff wrote: Jonathan Chen writes: I am seeing the following messages, which appear to indicate a memory overwrite: Waiting (max 60 seconds) for system processs 'vnlru' to stop...done Waiting (max 60 seconds) for system processs 'bufdaemon' to stop...done a iStyinncgi n(gm adxi s6k0s ,s evcnoonddess) rfeomra isnyisntge.m. .pr0o cess 'syncer' to stop...0 0 done All buffers synced. Uptime: 8m9s It's an interleaved buffer messages on SMP systems. The problem is known, but I haven't heard of a proposed solution yet. There is no fix. The workaround is to increase the size of the kernel printf() buffer. I don't remember how you do that ... but this is not a new issue - chech the archives for details. The PRINTF_BUFR_SIZE=128 workaround doesn't work on the few systems I've seen the issue on; but if you're interested, one way to do it is: include GENERIC ident GENERIC-1 options PRINTF_BUFR_SIZE=128 Cheers -- Jonathan Chen [EMAIL PROTECTED] -- If everything's under control, you're going too slow - Mario Andretti ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
question about xwindows
First let me say that I am quite new at freebsd or any other unix type system. My son helped me set up the xwindows (KDE) on this system. It has worked OK for quite a while and then yesterday I was trying to install a printer. Evidently I messed something up and now I get the following: hostname: not found dd: not found Couldn't create cookie I haven't a clue as to what is wrong, would someone help PLEASE? Thank you, Bob -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: question about xwindows
Hi, first of all, you used that bad letter. Just call it X. Never add an s at the end of the other word. Some people are real allergic to this. Robert Falanga wrote: First let me say that I am quite new at freebsd or any other unix type system. My son helped me set up the xwindows (KDE) on this system. It has worked OK for quite a while and then yesterday I was trying to install a printer. Evidently I messed something up and now I get the following: You must have some printing system installed on the machine. I would recommend CUPS for this purpose. Go to a console and enter this: pkg_info | grep cups You should get then some output like this: cups-base-1.3.3 Common UNIX Printing System libgnomecups-0.2.2_4,1 Support library for gnome cups admistration This error messages are too general for me. hostname: not found dd: not found Couldn't create cookie I haven't a clue as to what is wrong, would someone help PLEASE? If you have CUPS, you can use a web browser to administer the printer. What kind of rpinter do you have installed? Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
The FreeBSD Diary: 2008-01-27 - 2008-02-16
The FreeBSD Diary contains a large number of practical examples and how-to guides. This message is posted weekly to freebsd-questions@freebsd.org with the aim of letting people know what's available on the website. Before you post a question here it might be a good idea to first search the mailing list archives http://www.freebsd.org/search/search.html#mailinglists and/or The FreeBSD Diary http://www.freebsddiary.org/. -- Dan Langille BSDCan - http://www.BSDCan.org/ - BSD Conference ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
