Has anyone tried this motherboard?
With 7.0 boot-only disk, I haven't been able to get as far sa
"Mounting root filesystem". In fact it stops just before (after
probing acd0).
As a matter of fact this board doesn't seem to boot FreeBSD 6.3
either, nor 5.4. (Even an old Gentoo 1.4 gets stuck pre
Sevan / Venture37 writes:
>
> as a test try a daily snapshot
Just tried 8.0 of May 2008. Same thing.
BTW, Gentoo 1.4 eventually boots, disabling the USB disks legacy
support in the BIOS. (As far as I understand, it's an emulation that
lets primiteve OSs see the USB disks as IDE disks, or som
Christer Solskogen writes:
> Have you tried updating the BIOS (if it's available)?
As far as I can tell my BIOS is 1.04, while VIA, for the EX boards,
provides an "upgrade" to 1.01:
http://www.via.com.tw/en/products/mainboards/downloads.jsp?motherboard_id=450
I'm not sure this is funny.
--
wa
Once a week or so there is a system running 5.3-STABLE that panics for
unknown reasons (at least to me). I haven't managed to reproduce the
problem at will but I did manage to get a dump and do a backtrace.
The kgdb session goes likes this:
8<8<
Did enybody try to run AcuCobol 6.0 for Linux on FreeBSD's linulator?
I tried a couple of times (with old Debian libraries and more recent
Gentoo libraries) but runcbl keeps on getting a SIGSEGV right away.
ccbl (the compiler) seems to work, though.
Any clue?
--
walter pelissero
http://www.peli
[apparently the first message didn't get through; this is a repost]
Did enybody try to run AcuCobol 6.0 for Linux on FreeBSD's linulator?
I tried a couple of times (with old Debian libraries and more recently
Gentoo libraries) but runcbl keeps on getting a SIGSEGV right away.
ccbl (the compiler)
Jerry McAllister writes:
> > [apparently the first message didn't get through; this is a repost]
>
> Your previous post got through.
> Probably the presumed answer is that no-one who saw it has
> tried this or feels competent to respond.
Sorry for the duplicate. It wasn't the lack of answer
I realised that the ktrace log was rubbish; most of the syscalls names
were not properly mapped.
I tried to track down the exact spot were the Linux executable gets
the SEGV signal, running strace on a Debian system and comparing the
values passed to the system calls. Here is an extract:
rt_si
I tried linux_kdump (from ports) and things seem to clarify a bit.
I concentrated on acushare, which is the daemon that supervises
inter-process locking (locking on file access) and licence
verification. Whereas acushare seems to start properly, an attempt to
kill it through the recommended means
Dan Nelson writes:
> If you do have sysvmsg loaded, you may have to start adding printfs in
> linux_msgctl() to trace which call is failing and why.
Thanks. With your hints I made an interesting discovery that allowed
me to improve the situation dramatically.
In Linux's /usr/include/linux/ipc.
Dan Nelson writes:
> In the last episode (Feb 04), Walter C. Pelissero said:
> > A side note. What is the impact of this IPC_64 flag on the FreeBSD
> > code? Can we ignore it, or does it mean that the Linux emulator is
> > outdated regarding this "new" flag?
Dan Nelson writes:
> In the last episode (Feb 04), Walter C. Pelissero said:
> > A side note. What is the impact of this IPC_64 flag on the FreeBSD
> > code? Can we ignore it, or does it mean that the Linux emulator is
> > outdated regarding this "new" flag?
Today I've been trying to restore a filesystem with surprising
results. The backup file was on a netwroked machine and not on a tape
so I'd exclude any type of medium defect. Nevertheless, the restore
program reported a "tape read error".
Sounds really strange to me. Here is the session log:
I keep my src tree updated with cvsup, but I start to accumulate
patches to kernel or programs that I'd like to include automatically
each time I recompile the kernel (pretty often) or I do a "make world"
(much less often).
Those are usually patches that have been already put forward to the
attent
I'm trying to make work a D-Link 504T DSL router/switch with FreeBSD
5.2.1-RELEASE-p6.
I've already realised that IPv6 is not supported by the router so I
compiled an IPv4-only kernel and got to work DNS, HTTP, and FTP.
My problem is that ssh and telnet don't work. I get as far as the
Password p
John Mills writes:
> First, are you coming into your LAN from outside, or going outwards?
Either ways.
> If it's an outgoing-connection problem, I would look into the
> firewall setting of the FBSD box. Maybe you set didn't set it up to
> pass the ports for outgoing telnet and ssh, or maybe y
Just to update you on the D-Link 504T problem. After some weeks and a
relocation I've been able to dig further in it and come to the
conclusion that the 504T (mind the 'T') is buggy.
Both the D-Link European help desk and the following page confirmed
what I suspected:
http://www.broadbandrepor
Concerning a problem with a D-Link 504T ADSL modem/router/firewall
that I already reported to this list some time ago
http://groups.google.de/groups?hl=de&lr=&ie=UTF-8&frame=right&th=6a2dce2b59908c27&seekm=c856sh%242vul%241%40FreeBSD.csie.NCTU.edu.tw
I was wondering if Jim Randell had found th
On my laptop I'm experiencing a problem with dhclient. When I
bootstrap the laptop (FreeBSD 5.2.1) after the server (FreeBSD 4.10),
dhclient fails to get a lease within a useful time, while, if I
bootstrap the server after the laptop, it gets immediately the lease.
When the client is stuck in the
I have a DigiBoard PC/4e that used to work without a problem on
FreeBSD 4.9 (maybe even 4.10). On 5.4 when I kldload the digi module
I get an error:
dgb0: FEP/OS start failed (0x00 != 0x534f)
The device.hints contains:
hint.digi.0.at="isa"
hint.digi.0.port="0x320"
hint.digi.0.maddr="0xd8000"
W
I'm not wuite sure this belongs to a FreeBSD mailing list, but the way
the systems freezes suggests it may be a driver problem.
I'm trying to make DRI/DRM work on a Radeon 7000-VE (AGP) installed on
a dual Athlon running 5.4-STABLE. I'm using the radeon(4) driver of
Xorg 6.8.2 with the MergedFB o
Roland Smith writes:
> On Tue, Jun 07, 2005 at 11:54:41AM +0200, Walter C. Pelissero wrote:
> > Has anybody succeeded to run an ATI Radeon 7000 AGP on FreeBSD 5.4
> > with DRI/DRM?
>
> I've got a Radeon 9200 AGP (which is supposed to be a cheaper version of
> t
I'm trying to run FreeBSD 5.3 on a Via EPIA ME-6000, but there are
still a couple of things that don't work.
First. The PXE loading process is quite slow because it gets stuck
for a half a minute here and there while loading the KLD modules. No
network activity while the rotating bar on the scre
Kjell Midtseter writes:
> On Thursday, 28 October 2004 at 3:21:26 +0200, Walter C. Pelissero wrote:
> > I'm trying to run FreeBSD 5.3 on a Via EPIA ME-6000, but there are
> > still a couple of things that don't work.
> >
> > First. The PXE loading
Kjell Midtseter writes:
> > My M-6000's video chip works flawlessly with Xorg.
> What driver did you specify in the Device Secton of your /etc/X11/xorg.conf file?
I didn't. X -configure hash chosen a "via" driver for me.
--
walter pelissero
http://www.pelissero.de
I just bought a USB -> PS/2 keyboard and mouse converter for my
laptop. It's a Sitecom brand and it gets recognised as MCT Corp.
addr 1: UHCI root hub, Intel
addr 2: Generic USB Hub, ALCOR
addr 4: HID-compliant Mouse (USB), Mitsumi
addr 3: PS/2 - USB Interface Adaptor, MCT Corp.
Although th
Just noticed that the patch to usbd.c I proposed yesterday shows an
undesirable behaviour. That is, usbd executes the actions in
usbd.conf of all matching devices, which is not exactly what I meant
to do. In fact, usbd should execute for every device name the "best"
matching action in usbd.conf.
n Sat, Aug 30, 2003 at 01:51:27PM +0200, Walter C. Pelissero wrote:
> > I just bought a USB -> PS/2 keyboard and mouse converter for my
> > laptop. It's a Sitecom brand and it gets recognised as MCT Corp.
>
> I had similar problems with a Tangtop USB->PS/2 k+m a
When recently I've switched to a PS/2 Keyboard attached to a USB
converter I started to experience strange typos.
The problem is extra characters sent to the machine while typing
fairly fast. It can be easily reproduced doing this:
1. xset r off
2. press and keep pressed a key, say 'd'
3. pre
I was wondering if the pcmcia SCSI card provided with the HP M802e
portable CD burner is supported in cardbus mode under 5.2. The card
used to work flawlessly under 4.9 in 16bit mode (it's got a dip switch
to change between the two modes) with this default pccard.conf entry:
# Hewlett Packard M
30 matches
Mail list logo
