Can't install from install70.iso on to a Sun t5120
Hi everyone,
I have this error trying to install sparc64 on to a Sun t5120 via cd
written with install70.iso
Enter #. to return to ALOM.
{0} ok boot cdrom
SPARC Enterprise T5120, No Keyboard
Copyright (c) 1998, 2017, Oracle and/or its affiliates. All rights reserved.
OpenBoot 4.33.6.h, 16256 MB memory available, Serial #85158202.
Ethernet address 0:21:28:13:69:3a, Host ID: 8513693a.
Boot device: /pci@0/pci@0/pci@1/pci@0/pci@1/pci@0/usb@0,2/storage@2/disk@0
:f File and args:
OpenBSD IEEE 1275 Bootblock 2.1
..>> OpenBSD BOOT 1.21
ERROR: /iscsi-hba: No iscsi-network-bootpath property
Trying bsd...
Booting /pci@0/pci@0/pci@1/pci@0/pci@1/pci@0/usb@0,2/storage@2/disk@0
,0:f/bsd
4102856@0x100+1336@0x13e9ac8+3247500@0x1c0+946804@0x1f18d8c
OF_map_phys(ffc6e000,8192,fecea000,-1) failed
no space for symbol table
Program terminated
{0} ok
Has anyone any idea of how to proceed with a sparc install?
Kind regards John
Re: Can't install from install70.iso on to a Sun t5120
Dnia Tue, Nov 02, 2021 at 09:13:55AM +, John Gould napisał(a):
> Hi everyone,
>
> I have this error trying to install sparc64 on to a Sun t5120 via cd
> written with install70.iso
>
> Enter #. to return to ALOM.
>
>
> {0} ok boot cdrom
>
>
>
> SPARC Enterprise T5120, No Keyboard
>
> Copyright (c) 1998, 2017, Oracle and/or its affiliates. All rights reserved.
>
> OpenBoot 4.33.6.h, 16256 MB memory available, Serial #85158202.
>
> Ethernet address 0:21:28:13:69:3a, Host ID: 8513693a.
>
>
>
>
> Boot device: /pci@0/pci@0/pci@1/pci@0/pci@1/pci@0/usb@0,2/storage@2/disk@0
> :f File and args:
>
> OpenBSD IEEE 1275 Bootblock 2.1
>
> ..>> OpenBSD BOOT 1.21
>
>
> ERROR: /iscsi-hba: No iscsi-network-bootpath property
>
> Trying bsd...
>
> Booting /pci@0/pci@0/pci@1/pci@0/pci@1/pci@0/usb@0,2/storage@2/disk@0
> ,0:f/bsd
>
> 4102856@0x100+1336@0x13e9ac8+3247500@0x1c0+946804@0x1f18d8c
>
> OF_map_phys(ffc6e000,8192,fecea000,-1) failed
>
> no space for symbol table
>
> Program terminated
>
> {0} ok
>
> Has anyone any idea of how to proceed with a sparc install?
>
> Kind regards John
Hello,
You are saying that you are using install70.iso, but this line:
> Booting /pci@0/pci@0/pci@1/pci@0/pci@1/pci@0/usb@0,2/storage@2/disk@0
> ,0:f/bsd
suggests that you are booting from USB stick. If that's the case,
you should use .img files, not .iso. It may not matter on sparc, but
in my expirience, you couldn't boot freebsd iso from usb stick on amd64.
Maybe look at this thread:
https://www.mail-archive.com/tech@openbsd.org/msg61403.html
It looks like in some cases compressing bsd.rd helps, and
the error message is almost identical to yours.
Also, if you can get solaris running, you could try running
openbsd in LDOM first.
Kind regards,
Lukasz
lpr woes printing a broken pdf
This is current/amd64 on a PC, using lpr with this /etc/printcap: lp::lp=:rm=pr.stare.cz:rp=lp:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs:sh: which is a Brother DCP9055CDN via ethernet. Now, I have this pdf file (attached), broken in a way that puzzles me. When viewed with mupdf or gv, it shows one thing, when printed with lpr, it shows something else. I don't mean a missing glyph when an exotic language is used; it is in Czech, but it's not the rendering of Czech letters that's strange: it has 11 printed instead of 10 (line 1), 22 instead of 29 (line 2), 7000 instead of 7084 and 5222 instead of 5268 (line 4), 3 h 33 mm instead of 3 h 30 min (line 5.1), etc. Agonizing moments have been spent looking at the page, making sure it is actualy the file. Vaguely speaking, in these examples, some chars/glyphs seem to be repeated in the print, instead of the next one that should have been printed: 11 not 10 (repeating the 1) 22 not 29 (repeating the 2) 7000 not 7084 (repeating the 0) 33 mm not 30 min (repeating the 3 and the m) Is that an indication of some particular kind of breakage in a pdf file? Inside the pdf, I see file.pdf Description: Adobe PDF document
Re: lpr woes printing a broken pdf
On Tue, Nov 02, 2021 at 04:10:44PM +0100, Jan Stary wrote: > This is current/amd64 on a PC, using lpr with this /etc/printcap: > lp::lp=:rm=pr.stare.cz:rp=lp:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs:sh: > which is a Brother DCP9055CDN via ethernet. > > Now, I have this pdf file (attached), broken in a way that puzzles me. > When viewed with mupdf or gv, it shows one thing, when printed with lpr, > it shows something else. > > I don't mean a missing glyph when an exotic language is used; it is > in Czech, but it's not the rendering of Czech letters that's strange: > it has 11 printed instead of 10 (line 1), 22 instead of 29 (line 2), > 7000 instead of 7084 and 5222 instead of 5268 (line 4), > 3 h 33 mm instead of 3 h 30 min (line 5.1), etc. > > Agonizing moments have been spent looking at the page, > making sure it is actualy the file. > > Vaguely speaking, in these examples, some chars/glyphs > seem to be repeated in the print, instead of the next one > that should have been printed: > > 11 not 10 (repeating the 1) > 22 not 29 (repeating the 2) > 7000 not 7084 (repeating the 0) > 33 mm not 30 min (repeating the 3 and the m) > > Is that an indication of some particular kind > of breakage in a pdf file? > > Inside the pdf, I see > > /CreationDate(D:20150306075816) > /ModDate(D:20150306075816) > /Title(klic_5_tridy.xlsx) > /Creator(PScript5.dll Version 5.2.2 > > so I suppose the file was produced as a pdf export of > a xlsx file by some awful office package or another, > probaly on windows (dll). > > When printed from gv, it prints what gv and mupdf show. > When printed at a corporate myq print system, it prints the same; > but when printed with lpr, it prints these strange alterations. > > I don't think it's lpr's fault, so this might not even be the list, > for lpr just sends what it gets (except wrapping it in the cf, df files > of the lpr protocol, right?), but I would still like to know: > is it that gv can somehow interpret the broken pdf in the right way, > sending the right bits to the printer to print, but the Brother printer > (i.e., the printer's pdf interpreter?) can not? > Please excuse my pdf/ps ignorance. > > gv also says > > Warning: Missing charsets in String to FontSet conversion > > when viewing the file, but not with LC_CTYPE=C; > normally my env has LC_CTYPE=en_US.UTF-8. > There are some Czech letters printed wrong, > but surely every FontSet (whatever that is) > has glyphs for the digits. > > Thank you > > Jan > Hi Jan FWIW, I cannot reproduce this on my Brother HL-L3270CDW with lpr, file prints fine. This is on a -current (well, current-ish, October 5) amd64 machine, without cups, foomatic or anything like that. /etc/printcap: lp:\ :lp=:rm=10.17.19.134:\ :sh:\ :lf=/var/log/lpd-errs: --
KVM vlan-per-user guest
Hello
My VPS provider uses KVM with vlan-per-user network environment.
They oficially dont support openbsd but they allow to boot from custom iso.
Im trying to install 7.0 release.
Network interface name appears as vio0.
To set up networking they suggest to do the following:
# ifconfig if_name ${public_ip}/32
# route add -host 10.0.0.1 -interface if_name
# route add default 10.0.0.1
i tried
# route add 10.0.0.1 -iface vio0
route: vio0: bad address
i tried
# route add -host 10.0.0.1 -iface ${public_ip}
route was added with console message
arp_rtrequest: bad gateway value: vio0
and after
# route add default 10.0.0.1
default route was added with console messages (~1 per second)
arpresolve: 10.0.0.1: route contains no arp information
cant ping anything after that
how can i set up a route to 10.0.0.1 ?
Re: lpr woes printing a broken pdf
Jan Stary: > I don't think it's lpr's fault, so this might not even be the list, > for lpr just sends what it gets (except wrapping it in the cf, df files > of the lpr protocol, right?), but I would still like to know: Exactly. lpr/lpd is just a transport protocol. > is it that gv can somehow interpret the broken pdf in the right way, > sending the right bits to the printer to print, but the Brother printer > (i.e., the printer's pdf interpreter?) can not? Well, my HP LaserJet Pro M252dw occasionally refuses to print a PDF, declaring it corrupt. My usual workaround is to view to file with xpdf and print from there, which sends a PostScript conversion to the printer. So, yes, there are definitely malformed PDFs that a PDF viewer might cope with but a printer might not. (FWIW, my M252 prints your document correctly according to your description.) -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: lpr woes printing a broken pdf
On 2021-11-02 16:10:44, Jan Stary wrote: > This is current/amd64 on a PC, using lpr with this /etc/printcap: > lp::lp=:rm=pr.stare.cz:rp=lp:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs:sh: > which is a Brother DCP9055CDN via ethernet. > > Now, I have this pdf file (attached), broken in a way that puzzles me. > When viewed with mupdf or gv, it shows one thing, when printed with lpr, > it shows something else. > > [snip] > > Is that an indication of some particular kind > of breakage in a pdf file? > > [snip] > I have no idea if this is the same issue affecting you, but it reminded me of how JBIG2 compression can alter text. To quote Wikipedia [1], "When used in lossy mode, JBIG2 compression can potentially alter text in a way that's not discernible as corruption. ... Since JBIG2 tries to match up similar-looking symbols, the numbers "6" and "8" may get replaced, for example." This issue first came to light when it was found that scanned documents had different numbers in the digital representation than were on the original. In one case, an engineer reported that the size of a room on a technical blueprint changed from 21.11 m^2 down to 14.13 m^2 due to the way that the compression was being erroneously applied. However, this was reported when *scanning* documents. Your issue is with *printing* documents. I have no idea if this is the same issue as what you're experiencing, but I thought it still might be worth pointing out in case there's some connection between the two. [1] https://en.wikipedia.org/wiki/JBIG2#Disadvantages -- Bryan
