Re: No HDMI output on Lenovo V145, NetBSD 8.0

[Hauke Fath]

On 2019-12-09 14:25, Mayuresh wrote:

I have a NetBSD 8.0 installation on a USB stick, working fine on an asus
laptop.

Now I have another lenovo laptop[1] that boots fine using the same stick
but for HDMI not showing any output.


At this point, I would recommend giving netbsd-9 a spin, which is late 
in its release cycle and, if anything, more stable than -8.


You can download a snapshot from 
. And if you 
don't want to upgrade your installation right away, you can always just 
install a kernel (plus kernel modules, these days, unless you go with a 
MONOLITHIC kernel), and boot that with -8 userland.


Cheerio,
hauke

--
 The ASCII Ribbon CampaignHauke Fath
() No HTML/RTF in email Institut für Nachrichtentechnik
/\ No Word docs in email TU Darmstadt
 Respect for open standards  Ruf +49-6151-16-21344

Re: [netbsd-users] About using NetBSD as a guest, why, how etc.

[Malcolm Herbert]

Mayuresh - I find NetBSD in a VirtualBox VM under Ubuntu quite nice. In my case 
I also use encrypted zpools for my data which Linux supports now.

I like using VirtualBox+packer+vagrant with the bento[1] packer configs to spin 
out VMs of different types.  

My only gripe with VirtualBox is that it doesn't have native client tools 
support for the *BSD family and the vboxfs filesystem isn't available - 
ordinarily these provide file-level access to the host filesystem and vagrant 
heavily uses this.  Instead (for example), the packer+vagrant config for 
FreeBSD will use NFS which works but is a bit more fiddly to set up.

Unfortunately there is no bento recipe for NetBSD at all, so you'd have to 
build out the VM manually ...

I would like to create a bento recipe for NetBSD, however the bit that's 
preventing me doing this is understanding how to properly add disk labels and 
bootblocks from the command-line - one can stuff keys into the VM to drive 
sysinst but this is a nightmare to debug ... is doing a manual from-scratch 
install from the command-line documented anywhere?

Regards,
Malcolm

[1] https://github.com/chef/bento

-- 
Malcolm Herbert
m...@mjch.net

About using NetBSD as a guest, why, how etc.

[Mayuresh]

Considering this because I got a new hardware on which a few things don't
work on NetBSD (1. wifi: can live with using mobile with tethering; 2.
touchpad: I anyway prefer normal mouse and use that also very less, so ok;
3. hdmi: that's a deal breaker as I need laptop to connect to hdmi for my
normal usage).

To solve all these, could I make NetBSD a guest and what are some good
options? Is it Linux+VirtualBox, any specific Linux flavor would be good
to act merely as host by and large retaining NetBSD feel of the system?

Mayuresh

Re: How to create new partition from free space on a disk

[Robert Elz]

Date:Tue, 10 Dec 2019 09:32:41 +0530
From:Mayuresh 
Message-ID:  <20191210040241.GA20765@localhost>

  | My disklabel looks like this. Not sure how swap got created twice.

What exactly did you add with fdisk?  And what did you do with sysinst?
That's a very odd partition layout (just odd, not incorrect).

  | Shall I be using disklabel -e 

Yes, that's what NetBSD uses - the advice to use fdisk was well
intentioned I'm sure (and it is a good idea to make sure all space
NetBSD is using is allocated that way, so that some other system
you might add later doesn't overwrite NetBSD's data) but once the
disklabel exists and can be found (which the MBR (fdisk label) is
used for) what fdisk says is irrelevant to NetBSD.   The disklabel
controls everything.

Confirm what you are using with "df" and "swapctl -l" - change that
if it looks wrong (unmount anything unwanted, turn off swap), then edit
the disklabel adding new partitions - or deleting that 'e' partition if
it isn't being used, or it is, and you disable it (swapctl -d), and you
don't want to keep it.  Verify that you don't have any overlapping partitions,
(and ideally, nothing outside the space(s) allocated to NetBSD in the MBR
(fdisk label)) and you're done.   For new partitions you can just set the
fsize bsize cpg/sgs fields (the 3 columns after "4.2BSD" - see your 'a'
partition entry) as zero (but they must be present), those will get updated
when you use "newfs" to actually make a filesystem in the partition(s)
you make.

Once you have done newfs (see newfs(8)) (on /dev/rwd0X for whatever X
(in the range e..p) you have made a partition) you can mount (see mount(8))
it, and add it to /etc/fstab (see fstab(5) - add using an editor) (or add
it first, and then you can use a simplified form of the mount command).

Don't forget to mkdir the directory where you will mount the new partition,
and make sure its owner and permissions are set sanely before you mount
(weird things happen when the mounted-upon directory setup is strange, it
is no longer accessible (to be observed, or changed) after the mount has
been done).

kre

Re: How to create new partition from free space on a disk

[Mayuresh]

On Tue, Dec 10, 2019 at 08:53:31AM +0530, Mayuresh wrote:
> Now, where is it supposed to reflect as a device as /dev/wd0*?  disklabel
> still shows usual abcde.

My disklabel looks like this. Not sure how swap got created twice.

# /dev/rwd0:
type: unknown
disk: TOSHIBA MQ04ABF
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 1938021
total sectors: 1953525168
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0   # microseconds
track-to-track seek: 0  # microseconds
drivedata: 0

16 partitions:
#sizeoffset fstype [fsize bsize cpg/sgs]
 a: 18842644863 4.2BSD   2048 16384 0  # (Cyl.  0*- 186931*)
 b:   8160736 1945364432   swap # (Cyl. 1929925*- 
1938020)
 c: 20481262263 unused  0 0# (Cyl.  0*- 203187*)
 d: 1953525168 0 unused  0 0# (Cyl.  0 - 
1938020)
 e:  16384032 188426511   swap # (Cyl. 186931*- 203185*)

Shall I be using disklabel -e 

Mayuresh

Re: How to create new partition from free space on a disk

[Mayuresh]

On Mon, Dec 09, 2019 at 12:30:11PM -0800, Germain Le Chapelain wrote:
> Is it not running fdisk ?

Tried with fdisk -u. it shows Partition 1,2,3 as unused. Out of which
edited 1 to create partition of required size.

Now, where is it supposed to reflect as a device as /dev/wd0*?  disklabel
still shows usual abcde.

Mayuresh

Re: How to create new partition from free space on a disk

[Clay Daniels]

 Germain Le Chapelain wrote:

Mayuresh  wrote:


I have installed NetBSD on 100GB of a disk. Want to now create a 200GB
partition from free space available on the disk and use it as a cgd
device.

What is the recipe to do this?


Is it not running fdisk ?

--
Germain Le Chapelain 
Software Engineer
Lanvaux



The NetBSD fdisk Manual Page is a good start:
https://netbsd.gw.com/cgi-bin/man-cgi?fdisk++NetBSD-current

Also look at Chapter 14 of the The NetBSD Guide:
https://www.netbsd.org/docs/guide/en/chap-cgd.html

Good Luck,
Clay

Re: How to create new partition from free space on a disk

[Germain Le Chapelain]

On Tue, 10 Dec 2019 01:12:58 +0530
Mayuresh  wrote:

> I have installed NetBSD on 100GB of a disk. Want to now create a 200GB
> partition from free space available on the disk and use it as a cgd
> device.
> 
> What is the recipe to do this?

Is it not running fdisk ?

-- 
Germain Le Chapelain 
Software Engineer
Lanvaux

How to create new partition from free space on a disk

[Mayuresh]

I have installed NetBSD on 100GB of a disk. Want to now create a 200GB
partition from free space available on the disk and use it as a cgd
device.

What is the recipe to do this?

Mayuresh

Re: No HDMI output on Lenovo V145, NetBSD 8.0

[Mayuresh]

On Mon, Dec 09, 2019 at 08:12:35PM +0530, Mayuresh wrote:
> Attaching both.

I don't know whether it is related, but videos aren't playing well. They
are choppy and mpv says:

Audio/Video desynchronisation detected! Possible reasons include too slow
hardware, temporary CPU spikes, broken drivers, and broken files

Mayuresh

Re: No HDMI output on Lenovo V145, NetBSD 8.0

[Mayuresh]

On Mon, Dec 09, 2019 at 02:38:53PM +0100, Leonardo Taccari wrote:
> (to be on the safe side, please share it entirely if you can).
> 
> Can you please share /var/log/Xorg.0.log after X.org is started?

Attaching both.

[ Strangely ethernet re0 has stopped working. Says host is down when
pinging the router when the router LED blinks when running ping. But
that's for another thread. ]


Mayuresh

[37.699] 
X.Org X Server 1.18.4
Release Date: 2016-07-19
[37.699] X Protocol Version 11, Revision 0
[37.699] Build Operating System: NetBSD/amd64 8.0 - The NetBSD Foundation, 
Inc.
[37.699] Current Operating System: NetBSD asusnetbsd 8.0 NetBSD 8.0 
(GENERIC) #0: Tue Jul 17 14:59:51 UTC 2018  
mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64
[37.700] Build Date: 14 August 2016  01:29:29AM
[37.700]  
[37.701] Current version of pixman: 0.34.0
[37.701]Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
[37.701] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[37.701] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Dec 10 04:05:51 
2019
[37.710] (II) Loader magic: 0x79e92c20
[37.710] (II) Module ABI versions:
[37.710]X.Org ANSI C Emulation: 0.4
[37.710]X.Org Video Driver: 20.0
[37.710]X.Org XInput driver : 22.1
[37.710]X.Org Server Extension : 9.0
[37.717] (--) PCI:*(0:0:1:0) 1002:98e4:17aa:39f5 rev 234, Mem @ 
0xe800/134217728, 0xf080/8388608, 0xf040/262144, I/O @ 
0x4000/256, BIOS @ 0x/131072
[37.719] (==) Using default built-in configuration (30 lines)
[37.719] (==) --- Start of built-in configuration ---
[37.719]Section "Device"
[37.719]Identifier  "Builtin Default ati Device 0"
[37.719]Driver  "ati"
[37.719]EndSection
[37.719]Section "Screen"
[37.719]Identifier  "Builtin Default ati Screen 0"
[37.719]Device  "Builtin Default ati Device 0"
[37.719]EndSection
[37.719]Section "Device"
[37.719]Identifier  "Builtin Default fbdev Device 0"
[37.719]Driver  "fbdev"
[37.719]EndSection
[37.719]Section "Screen"
[37.719]Identifier  "Builtin Default fbdev Screen 0"
[37.719]Device  "Builtin Default fbdev Device 0"
[37.719]EndSection
[37.719]Section "Device"
[37.719]Identifier  "Builtin Default vesa Device 0"
[37.719]Driver  "vesa"
[37.719]EndSection
[37.719]Section "Screen"
[37.719]Identifier  "Builtin Default vesa Screen 0"
[37.719]Device  "Builtin Default vesa Device 0"
[37.719]EndSection
[37.719]Section "ServerLayout"
[37.719]Identifier  "Builtin Default Layout"
[37.719]Screen  "Builtin Default ati Screen 0"
[37.719]Screen  "Builtin Default fbdev Screen 0"
[37.719]Screen  "Builtin Default vesa Screen 0"
[37.719]EndSection
[37.719] (==) --- End of built-in configuration ---
[37.720] (==) ServerLayout "Builtin Default Layout"
[37.720] (**) |-->Screen "Builtin Default ati Screen 0" (0)
[37.720] (**) |   |-->Monitor ""
[37.723] (**) |   |-->Device "Builtin Default ati Device 0"
[37.723] (==) No monitor specified for screen "Builtin Default ati Screen 
0".
Using a default monitor configuration.
[37.723] (**) |-->Screen "Builtin Default fbdev Screen 0" (1)
[37.723] (**) |   |-->Monitor ""
[37.723] (**) |   |-->Device "Builtin Default fbdev Device 0"
[37.723] (==) No monitor specified for screen "Builtin Default fbdev Screen 
0".
Using a default monitor configuration.
[37.723] (**) |-->Screen "Builtin Default vesa Screen 0" (2)
[37.723] (**) |   |-->Monitor ""
[37.723] (**) |   |-->Device "Builtin Default vesa Device 0"
[37.723] (==) No monitor specified for screen "Builtin Default vesa Screen 
0".
Using a default monitor configuration.
[37.724] (==) Not automatically adding devices
[37.724] (==) Not automatically enabling devices
[37.724] (==) Not automatically adding GPU devices
[37.724] (==) Max clients allowed: 256, resource mask: 0x1f
[37.735] (==) FontPath set to:
/usr/X11R7/lib/X11/fonts/misc/,
/usr/X11R7/lib/X11/fonts/TTF/,
/usr/X11R7/lib/X11/fonts/Type1/,
/usr/X11R7/lib/X11/fonts/75dpi/,
/usr/X11R7/lib/X11/fonts/100dpi/
[37.735] (==) ModulePath set to "/usr/X11R7/lib/modules"
[37.737] (==) |-->Input Device ""
[37.737] (==) |-->Input Device ""
[37.737] (==) The core pointer device wasn't specified explicitly in the 
layout.
U

Re: No HDMI output on Lenovo V145, NetBSD 8.0

[Leonardo Taccari]

Hello Mayuresh, 

Mayuresh writes:
> [...]
> Now I have another lenovo laptop[1] that boots fine using the same stick
> but for HDMI not showing any output.
>
> $ uname -a
> NetBSD asusnetbsd 8.0 NetBSD 8.0 (GENERIC) #0: Tue Jul 17 14:59:51 UTC
> 2018  mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
> amd64 x86_64 AMD 686-class NetBSD
>
> Please the following dmesg message, also let me know if I should grep for
> more:
>
> $ dmesg  | grep -i hdmi
> hdafg0: HDMI00 2ch: Digital Out [Jack]
>
> [...]

The complete dmesg could be helpful, in particular I would grep for (via
`grep -E'):

 (drm|intelfb|radeon|nouveau)

(to be on the safe side, please share it entirely if you can).

> HDMI cable is connected right from boot time and it shows nothing during
> boot. I don't think it's an X11 matter. But just in case it matters I am
> using native X11 and xrandr shows:
>
> $ xrandr 
> xrandr: Failed to get size of gamma for output default
> Screen 0: minimum 1366 x 768, current 1368 x 768, maximum 1368 x 768
> default connected 1368x768+0+0 0mm x 0mm
>1366x768   0.00  
>1368x768   0.00* 
>
> Would appreciate help to get this work.
> [...]

Can you please share /var/log/Xorg.0.log after X.org is started?

No HDMI output on Lenovo V145, NetBSD 8.0

[Mayuresh]

I have a NetBSD 8.0 installation on a USB stick, working fine on an asus
laptop.

Now I have another lenovo laptop[1] that boots fine using the same stick
but for HDMI not showing any output.

$ uname -a
NetBSD asusnetbsd 8.0 NetBSD 8.0 (GENERIC) #0: Tue Jul 17 14:59:51 UTC
2018  mkre...@mkrepro.netbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
amd64 x86_64 AMD 686-class NetBSD

Please the following dmesg message, also let me know if I should grep for
more:

$ dmesg  | grep -i hdmi
hdafg0: HDMI00 2ch: Digital Out [Jack]

HDMI cable is connected right from boot time and it shows nothing during
boot. I don't think it's an X11 matter. But just in case it matters I am
using native X11 and xrandr shows:

$ xrandr 
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1366 x 768, current 1368 x 768, maximum 1368 x 768
default connected 1368x768+0+0 0mm x 0mm
   1366x768   0.00  
   1368x768   0.00* 

Would appreciate help to get this work.

Mayuresh

[1]
https://www.lenovo.com/in/en/laptops/lenovo/v-series/Lenovo-V145-15AST/p/88LG80V1181