Displaying 20 results from an estimated 2000 matches similar to: "make installworld fails : touch not found ?"
2003 Apr 22
1
installworld (touch: not found)
Hi All,
I just the "touch: not found" problem that seems to occur occaisonally
when installing world.
--------------------------------------------------------------
>>> Installing everything..
--------------------------------------------------------------
cd /usr/src; make -f Makefile.inc1 install
===> share/info
===> include
creating osreldate.h from newvers.sh
setvar
2003 May 14
0
System totally borked after installworld and mergemaster at 16:20:03 MSK
Well, 4 days after previous upgrade i cvs'ed RELENG_4 from
local cvs tree (updated hourly), made buildworld buildkernel
installkernel, rebooted into single user, made installworld
and mergemaster.
Mergemaster updated newsyslog.conf, syslogd.conf, ok, rebooted...
Wow...
All scripts from /usr/local/etc/rc.d refused to load.
And the system is in "Amnesiac" mode
Attempt to run
2006 Apr 12
7
help ith burncd (Input/output error, 6.1-RC, plextor PX-740a)
I have a new system which includes a Plextor PX-740a DVD+-R/RW CD-R/RW
drive attached to an Asus A8V-MX motherboard.
When I try to use burncd to burn a cd, it writes all of the data, says
"fixating CD, please wait.." and then reports
burncd: ioctl(CDRIOCFIXATE): Input/output error
Oddly enough, the CD seems to be usable.
I can successfully burn the same file if I use cdrecord.
The
2007 Dec 27
2
Failure of gvinum after panic
Hi all,
I have some problems with my gvinum setup after the system panic'ed.
Afterwards the system fails finding the plexes to the subdisks (or at
least that is what I can understand after having searched the gvinum
source code for the error string in the DMESG log..)
The machine is an IBM Netfinity 5000 and the internal HW self tests
does not find any errors in the hw.
Luckily my root is
2003 Jul 03
1
SCSI backup error
Hi,
Can someone please help me with this? I have just upgraded from 4.7 to 4.8-STABLE and
this is what I am getting when I try a tape backup. Please CC as I am not in the list. It was
working well before the upgrade (dump -0ua -f - / | gzip -c -9 | dd of=/dev/nsa0).
Thank you,
Lefteris Tsintjelis
Jul 3 22:55:18 ene /kernel:
2008 May 07
0
Kernel panic - em0 culprit?
Hello,
My server is experiencing occasional kernel panics when under moderate
load. I'm attaching a crash dump and the dmesg output. I'm not sure how
to read the kernel backtrace but it looks like the Intel NIC (em0)
caused the problem. Occasionally, I used to get a "em0: watchdog timeout
-- resetting" error message, but I never had a kernel panic. The problem
started last
2003 Aug 09
0
USB problems (I/O-Error => USB da(4) quirks, uscanner0)
Hi,
I have some problems with usb da and uscanner giving me I/O-errors.
This is on a ASRock K7VT2 board.
If there is anything else I could do (testing patches, providing further info),
please let me know.
4.8-STABLE from 04.08.2003:
- MBO USB-MultiCardReader 6-in-1 mount_msdos => Input/output error
- Epson Perfection 1260 Scanner scanimage --test => Error during device I/O
2003 Oct 03
1
4.9-rc + usb + asus a7n8x == bad news
Hi! Just before we start, this is not the "USB hang on boot" problem. OK?
This post got rather long, so I'll summaries it all in a sentence here:
With FreeBSD 4.9-rc on an ASUS A7N8X with a cheapo memory stick, simply
plugging it in and taking it out a couple of times is a guaranteed panic.
I use only one USB device, a cheapo USB memory stick, which I recently
bought on a
2003 Jul 09
3
[SAGE] FreeBSD 4.4-REL to FreeBSD 4.8-STABLE upgrade problem.
Before reading below: I am considering a new install rather than an upgrade
of our servers. However, now I just want to beat this problem. :)
At 02:19 PM 7/8/2003 +0000, Phil Pennock wrote:
>On 2003-07-08 at 14:09 +0000, Phil Pennock wrote:
> > There was a fairly major update to the IDE disk device handlers which
> > required new device nodes. Bringing in the new MAKEDEV script
2003 Sep 29
3
Frequent reboots...
Hello,
I am having a problem with a new server running FreeBSD 4.9-PRERELEASE.
Once every two days or so, it reboots itself.. there is no exact time of the day it reboots..
It rebooted itself at 4:25 PM EDT on 9/25, and 3:05 AM EDT on 9/29 (today).
I thought it's the bad memory or some sort, so I've been running memtest today and memtest reports no sign of trouble with the memory...
2007 Jun 08
2
Can't get if_txp(4) to attach to a 3CR990B-TXM NIC
Good morning,
I'm having a bit of an issue getting a 3CR990B-TXM NIC detected and
usable. Just wondering if anyone knows of any issues with this NIC
chipset and/or with the motherboard chipset.
The motherboard is a Biostar GeForce 6100 AM2 using an nVidia nForce 410
chipset and nVidia GeForce 6100 vide chipset.
I've tried FreeBSD 6.1, 6.2, 6-STABLE (from Wed), and 7-CURRENT (from
2009 Jan 12
2
bwi: no DS tssi no OFDM tssi
Hello,
I am attempting to get by broadcom wifi card up and running, am sick of
trying to get ndis working, and am attempting to use the bwi driver
(originating in dragonflyBSD). I'm hoping others here have tried to do the
same and have some pointers. I'm using 7.1-RELEASE (system/source are
in-sync) and my card is a BCM94306MP. My dmesg is posted below.
Bwi(4) is installed and it
2003 Apr 22
1
make installworld Error code 64
Hi,
I am a long time OpenBSD user trying FreeBSD. I am attempting to upgrade my
system from FreeBSD RELEASE 4.7 to "STABLE"
This is my first post to this list so please be gentle : )
I followed
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
But when I get to "21.4.9 Install the New System Binaries" This happens:
root@smeagol /usr/src # make
2003 Jul 17
1
device troubles after stable update
After updating my kernel from a 4.7-stable to 4.8-stable update, my SB PCI128 is no longer recognized by the pcm driver.
Here is my dmesg:
FreeBSD 4.8-STABLE #0: Thu Jul 17 14:13:52 CDT 2003
root@hautlos.stout.osu-res.okstate.edu:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz
CPU: AMD Athlon(tm) Processor (800.03-MHz 686-class CPU)
Origin =
2006 Mar 17
3
SETFEATURES SET TRANSFER MODE semaphore timeout on FreeBSD 6.0 RELEASE
Hi
I have a newly installed FreeBSD 6.0 release machine on which I am
getting the following error on the console:
"ad4: req=0xc23bc258 SETFEATURES SET TRANSFER MODE semaphore timeout !!
DANGER Will Robinson !!"
This is generally associated with heightened disk activity, but it
happens inevitably after a while (minutes or hours) if the machine is
running.
The atacontrol list shows:
2003 Aug 01
0
gdb coredumps
Hi,
After kernel panic I couldn't get gdb work properly.
msi$ uname -sr
FreeBSD 4.7-RELEASE
msi$ gdb -k /usr/src/sys/compile/MSINW/kernel.debug vmcore.0
GNU gdb 4.18 (FreeBSD)
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public
License, and you are welcome to change it and/or distribute copies of it under
certain conditions.
Type "show
2005 May 17
7
CUPDS reboot the whole system
Hello,
Before a couple of days ago I started /usr/local/sbin/cupsd manualy from
console. When I press CTRL+C to interrupt a program, the system change
runlevel and going to reboot. This was on FreeBSD V5.3, today I
installed fresh new 5.4 but the problem is the same.
cups-base-1.1.23.0_3
--
Todor Dragnev <todor.dragnev@gmail.com>
2003 Sep 03
0
System hanging in acpi during shutdown
This morning, I upgraded my main system to an up-to-date -STABLE
including acpi and it now hangs during shutdown after reporting:
Waiting (max 60 seconds) for system process `vnlru' to stop...stopped
If I set hw.acpi.disable_on_poweroff=0 then the shutdown completes but
poweroff fails with (hand copied):
ACPI-1287: ***Error: Method execution failed [\_PTS] (Node 0xc21ed450),
2003 Aug 13
6
5.1-R-p2 crashes on SMP with AMI RAID and Intel 1000/Pro
Dear Sirs.
It seems to me a never ending story. We run a box with a TYAN Thunder
2500 Dual SMP mainboard, 2GB ECC Tyan certified memory, AMI Enterprise
1600 RAID adapter and additional Intel 1000/Pro server type (64 bit)
GBit LAN NIC. With FreeBSD 4.8 this was stable, but to achive this
state was really hard! It is a story similar to that what happend when
we changed towards FreeBSD
2003 Sep 05
2
HEADS UP: ATA bus dma code MFC'd
If you start to experience problems with ata devices, please
direct your report this way.
Thanks
-lq