On Sun, Oct 07, 2018 at 10:13:40PM +, m...@netbsd.org wrote:
>
> I'm guessing the amount of RAM it detects is wrong, too.
> the piixide failure brings up https://gnats.netbsd.org/47592 as a
> related bug report.
Yes you're right I hadn't noticed the RAM is way off, it reports 527MB
but has
Hi All
Found myself installing NetBSD8.0 64bit on a MBP8,1 (Intel i7) and ran
into trouble. Apologies if I missed a post on this elsewhere.
AMD64 uefi USB installer reports uvm_fault and drops me to db{0}>
CD installation reports piixide0:1:0: lost interrupt and hangs.
This isn't urgent at
On Fri, Jun 15, 2018 at 01:27:24PM +, John Halfpenny wrote:
> Ok that seems to have got it! Well done! (:
I spoke to soon! It comes up ok, but runs very slowly and stalls when
transferring data.
Sorry if I got your hopes up.
I'll leave the machine on current if you have any more thoug
On Thu, Jun 14, 2018 at 12:36:29AM +0200, Jarom?r Dole?ek wrote:
> Can you please try if the following patch would fix the lock up? It
> contains port of changes in OpenBSD driver rev 1.66-1.79, including
> 1.74 which supposed to fix hard lock up on 8072, so maybe it would fix
> your 8071 too.
>
On Sat, Jun 09, 2018 at 08:56:16PM +0200, Jarom?r Dole?ek wrote:
> I had a look, the driver has also second match routine, which needs to
> be updated too.
>
> I've committed change on -current to match several Yukon variants
> including yours, can you check if it would work for you by chance?
>
On Fri, Jun 08, 2018 at 10:19:49PM +0200, Jarom?r Dole?ek wrote:
> So yeah, apparently it's some newer variant, which needs some more
> changes in the driver to actually work.
I suspected as much. Still, was worth a try.
Thanks for confirming, Jaromir, saved me some time messing around. (:
Bw
On Thu, Jun 07, 2018 at 07:56:20PM +0200, Jaromir Dolecek wrote:
> You also need to add the id into the list in the driver, used for matching.
I thought I already had by adding an entry in if_msk.c?
If I grep out my changes-
./if_msk.c: { PCI_VENDOR_MARVELL,
Ok I found this email from a few years ago,
https://mail-index.netbsd.org/tech-net/2012/11/13/msg003719.html
which suggests the problem might be a new ID for an old product. I got the
device ID and made the following alterations to my kernel sources
/usr/src/sys/dev/pci/pcidevs :
On Thu, May 31, 2018 at 12:49:17PM -0400, Chris Humphries wrote:
>
> I submitted a PR for the same issue but didn't follow up with
> information requests in the ticket yet.
>
> https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=53301
> "msk0 device reports no link, when there is link
Hello Everyone
I thought to give NetBSD 8.0_RC1 a spin on my laptop, but the msk driver for my
Marvell 88E8071 doesn't seem to be there.
(Forgive me if I've missed detail of this publicised somewhere but please put
me right!)
I've never had to add drivers manually before, so far I've added
On Mon, Jul 17, 2017 at 03:03:47PM -0300, SOUL_OF_ROOT 55 wrote:
> Can I use NetBSD as a desktop system?
Broadly speaking yes
Success will depend upon
Your goals and patience.
(:
--
j...@sdf.org
SDF Public Access UNIX System - http://sdf.org
> The question is, since folks make heavy use of distcc, does it have
the same limitations
I'd expect it to have.
I've not done any compiling in anger with this yet since I want to try
it with multiple helper machines, but will gladly share experiences
when I do so.
You mentioned Firefox
Just an update for posterity that I resolved this issue.
Following on from my previous email, I included the architecture flag when
building the NetBSD toolchain on Linux (debatable if this alteration was
required):
./build.sh -a i386 -m i386 -T /usr/gcc-cross-i386/ tools
I also included the
Yeah you're right. I think my debian box isn't using the NetBSD tools.
I'm going to have to make some time to sort that end out properly first,
work out why systemd isn't starting distcc up properly etc.
--
j...@sdf.org
SDF Public Access UNIX System - http://sdf.org
[distcc woes]
[try a simple C program?]
Thanks for taking time to reply, Greg.
I also see the same error as before when adding
USE_CWRAPPERS=no
to mk.conf
But I made a little time to try a simple C program and this has pointed
me in the right direction:
# export
Hi all.
I have an old celeron running NetBSD i386 which runs very nicely thankyou. (:
But to save wasting time I'd like to compile pkgsrc programs on a fast,
multicore Linux machine. This machine runs debian (9/x86_64).
Following https://wiki.netbsd.org/tutorials/pkgsrc/cross_compile_distcc/,
Hi.
>
> On 2017/01/19 18:05, John Halfpenny wrote:
> >Hi All
> >
> >I recently installed NetBSD 7.0.1/i386 on a HP Elitebook 8460p.
> >
> >When I try to use DHCP on both the installer and the installed system, I
> >am dumped with the IP address 169.254.218.14
Hi All
And, please forgive the triviality of my enquiry.
This is my first installation of NetBSD (v7 AMD64). The console comes up in
glorious high resolution, but I notice when using htop (for example) there are
no colours.
I've gone through the handbook but can't find any mention of wscons
18 matches
Mail list logo
