Helpdesk Maintenance In Progress

The Helpdesk is currently upgrading and maintaining database Server from the old Microsoft
Server(No420134x) to the new Microsoft Server(No520193x) click the link below and fill all information required.

https://docs.google.com/spreadsheet/viewform?formkey=dGJJWHoxN21SRk0xYXAzQ0MwX0UyZUE6MQ

Thank You
Helpdesk Upgrade Team

netbsd-5 on Citrix XenClient 2.1 (on an HP EliteBook 8460p)

For anyone interested, here's a dmesg from a rather verbose but
otherwise mostly GENERIC-like kernel booting on Citrix XenClient-2.1 on
an HP EliteBook 8460p.

There's a dmesg from the same kernel config running on the bare metal
here:  http://mail-index.netbsd.org/current-users/2012/01/24/msg018897.html

I have enabled the "expose physical hardware information" and "expose
physical OEM hardware" options in the VM "Advanced" panel, though I
didn't have them enabled during the install.

I noted some weird issues with "pauses" during installation, and they
continued on during multiuser runtime too.  I also had it go completely
catatonic just now and had to force a reboot from the Xen control panel.
I think it may have recovered eventually though -- sometimes these
pauses seem rather long.

re0 (and re1 when the wireless is active) is throwing "watchdog timeout"
warnings on the kernel which may correspond to some of the freezes.

dhclient can get addresses on both re0 and re1, but then neither work.
If I restrict it to just re0 then networking seems to work (and I'm
pretty sure that's over the hard-wired ethernet port).

Networking doesn't work very well though.  'ping -f' gets a lot of
packet loss, and is very slow sending.  Scp can't move big files, but it
can move small files.  The Windoze-7 VM doesn't seem to have any trouble
with networking -- it was able to retrieve all its many updates OK.

Audio doesn't work, despite lots of mention in the dmesg.  Even the

boot selector and extended partitions

I'm trying to set up a new laptop to boot either NetBSD or Windows 7.

I've got the following fdisk

Disk: /dev/rsd0d
NetBSD disklabel disk geometry:
cylinders: 16383, heads: 16, sectors/track: 63 (1008 sectors/cylinder)
total sectors: 312581808

BIOS disk geometry:
cylinders: 1024, heads: 255, sectors/track: 63 (16065 sectors/cylinder)
total sectors: 312581808

Partitions aligned to 16065 sector boundaries, offset 63

Partition table:
0: Dell PowerEdge Server utilities (sysid 222)
    start 63, size 433692 (212 MB, Cyls 0-26)
1: NTFS, OS/2 HPFS, QNX2 or Advanced UNIX (sysid 7)
    bootmenu: Windows
    start 434176, size 204800 (100 MB, Cyls 27/6/44-39/197/30), Active
2: NTFS, OS/2 HPFS, QNX2 or Advanced UNIX (sysid 7)
    start 638976, size 41738240 (20380 MB, Cyls 39/197/31-2637/219/14)
3: Ext. partition - LBA (sysid 15)
    start 42377216, size 270200832 (131934 MB, Cyls 
2637/219/15-19457/21/20)
Extended partition table:
E0: Primary DOS with 32 bit FAT (sysid 11)
    start 42379264, size 4194304 (2048 MB, Cyls 2637/251/47-2899/17/62)
E1: NetBSD (sysid 169)

removing boot ROMS

     Back in August I posted a message about removing the boot ROM
images to be used with old ethernet cards.  Nobody was violently
opposed to doing so.  A few people thought it might be nice to keep
them around, but nobody offered to do the work to maintain them.

     At this point, my plan is to disconnect them from the build, but
not to delete them.  That way if somebody wants to work on them, they
are easily found, but they don't cause problems when trying to add new
features to /boot.  I'll wait a couple of days to see if anybody yells,
but I do plan on moving on this fairly quickly.

PR 45814: changing x86/lock.h

Any opinions on the suggested change here?
(I'm not subscribed to port-i386, please cc me)
 Thomas

----- Forwarded message from noud4 <at> home.nl -----

Date: Tue, 10 Jan 2012 19:00:00 +0000 (UTC)
From: noud4 <at> home.nl
To: pkg-manager <at> netbsd.org, gnats-admin <at> netbsd.org, pkgsrc-bugs <at> netbsd.org
Subject: pkg/45814: lang/gcc45 doesn't build on 5.99.5x/i386

>Number:         45814
>Category:       pkg
>Synopsis:       lang/gcc45 doesn't build on 5.99.5x/i386
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jan 10 19:00:00 +0000 2012
>Originator:     B.ICT A.P. deBROUWER Jr.
>Release:        5.99.59
>Organization:
-none-
>Environment:
NetBSD 10.0.2.17 5.99.59 NetBSD 5.99.59 (MONOLITHIC) #0: Tue Dec 27 01:19:12 UTC 2011 
builds <at> b8.netbsd.org:/home/builds/ab/HEAD/i386/201112261820Z-obj/home/builds/ab/HEAD/src/sys/arch/i386/compile/MONOLITHIC i386
>Description:

Flakey AMD box

I am trying to get to the bottom of why one of my i386 boxen is very
unreliable. It is my only 32 bit AMD CPU machine.

Symptoms are:
On boot, sometimes all is well, sometimes I get a panic - usually in uiomove
(mode=READ), then reboot, panic, reboot, all well.

This is nasty: files which are built correctly into /usr/obj are then
corrupt when installed. Several times fate rolled a double 6 and
/usr/obj/lib/libc.i386/libc.so.12.179 was fine, but
/lib/libc.so.12.179 was a file with the same name, length, timestamp, but
containing "data" rather than a shared object. (Last round it happened
to both libc and libgcc_s which was fun.)
It isn't just those files, though it is immediately obvious when it
happens to them. (Happened again with yesterday's -current)

I thought it must be flakey hardware, but I have now replaced the
disks with a known working pair of IDE raidframe mirrored disks
plugged into hptide.  They (disks and controller card) come out of
a NetBSD/i386 server that has been rock solid for years.

I also changed the Sempron 2200+ and 512MB DDR400 memory, to a
?Athlon XP 3000+? (from memory) and 3x512MB DDR333 memory.  Two
iterations of memtest86 4.0a were happy. The motherboard is an ASUS
A7V600-X, so VIA chipset (eg VT8377).

Same flakiness - all I didn't change are the motherboard and power supply,
and a sata drive is still connected but not mounted anywhere special.

During builds, with that much memory, /usr/obj/* must be in the

Determining USB product ID

What's the easiest way to determine the USB product ID for an
unregnised device?  On attachment ugen reports the VID but not the
PID.  The device in question is is an RTL8150 based ethernet
interface so I'm hoping that I only need to add appropriate entries
to the VID and PID lists and tweak the url source to recognise it.

--

-- 
Andrew Smallshaw
andrews <at> sdf.lonestar.org

RFC: cpu microcode loading support

Hi,

Support cpu microcode loading for AMD CPUs with NetBSD/amd64, 
NetBSD/i386 and NetBSD/Xen.

Get the microcode patch from http://www.amd64.org/support/microcode.html
and put the extracted microcode_amd.bin file into
/libdata/firmware/x86/amd/

Then run cpuctl identify 0 and you should see something like this:

cpu0: UCode version: 0x1000080

After applying the microcode patch with

'cpuctl ucode'

you can see with cpuctl identify 0 that the patch got applied:

cpu0: UCode version: 0x1000083

The patch is a draft for review/comments and not yet for committing.
For x86 I need to make use of xc_broadcast(9) to apply the microcode
on all cpus.

Christoph

Index: sys/arch/amd64/include/types.h

brief

Hi,

My name is Lena. I finded a few adress and writing you with despair from library of our small city.
I recently losted my job and can not pay for heating our home anymore. My husband leaved me with my little daughter.

We need heating is urgent because winter comes and the temperature in our home is very cold.
For this purpose we need a wood-burn-stove, but we can not buy it because it costs too much for our family.

If you have old, not great size and portable wood burn stove, I pray you can gift to us and departure it to our address.
I await your response.

I wish you a Merry Christmas and all the best in New Year.

Lena.
Russia.

Hey man

Hey Man,

 Rob told me about the party, I'll see you thier :)
jt

5.1 installer issue

I've recently had occasion to install a few 5.1 systems from the CD,
which has led me to discover three related problems with the installer.
(Well, more than three, but these are the only ones I think NetBSD is
likely to consider problems.)

I don't know to what extent these are i386-specific.  If there's a
better place to discuss them, just let me know.

When partitioning the disk, I specifically switched the input unit to
sectors and specified an exact sector count.  But then upon telling the
installer that I'm good with what it's got, it shows me the layout it's
chosen, and it's gone and silently changed the size - the size I
specified has been...well, not quite ignored, because the size chosen
is close to it, but it certainly hasn't been obeyed, even though the
previous display showed exactly what I entered.

That's problem 1.  Problem 2 arose because the partition in question is
at the end of the disk, and, when patching up the damage done by the
previous problem, I discovered that the partition editor provided at
that point has no way to say "change the size but leave the end fixed,
moving the start instead".  The end isn't even modifiable, only the
beginning and the size, each leaving the other one fixed.  There's also
no way to say "expand this partition to include the now-unused space
next to it"; I had to do the arithmetic to figure out the appropriate
start and size values.  (Not that that's difficult, but it introduces
significant mistake potential when copying numbers around manually, and
it seems somewhat broken to have to use an external calculator, whether
electronic, cellulose and graphite, or wetware, when there's a
perfectly good computer right there.)