Re: Userconf & DRM driver (Was Re: Panic: no console device)
Bob Bernstein writes: > I'm wondering now how best to bring the rest of the system into sync > with ver 8.0; it originated in my install of 7.1.2. I have managed > to get a lot of basic configuration chores completed. I'd like to > spare them destruction at the hands of a stupid upgrade, i.e. one > master-minded by ME. This is not the easy way to get started, but once set up it is easy to update. Install pkgsrc/sysutils/etcmanage, and read the README, probably 5 times in a row. Use "etcmanage --import" on an unpacked tree of the etc and xetc sets you used to install, or the latest netbsd-7 if you don't have that. Use BUILD-NetBSD to run the build, and use 'INSTALL-NetBSD installuser' to install (and update etc). It does what I want :-) Of course, back up first. Then, "etcmanage --up /usr/netbsd-etc", understand all differences, and reduce them unless you intend them to continue to be different. Do actually read the scripts in the package. They are written to be comprehensible, or at least I thought so at the time. This sounds bad and it will take you some hours the first time. But then, you can build and upgrade with almost no work. I have machines I have been upgrading in place since at least 2006 and probably earlier, with a few hw upgrades (dump/restore) in the middle. But not reinstalls. There are other approaches in pkgsrc, and there is the standard approach in the guide.
Re: Userconf & DRM driver (Was Re: Panic: no console device)
We have ver. 8.0 liftoff! On Thu, Mar 07, 2019 at 10:34:30PM +0100, Michael van Elst wrote: > The drivers are (for Intel, ATI and NVidia): > i915drmkms > radeon > nouveau Userconf very nicely complied with my requests to nuke those, and it mirrored back to me (a nice feature) when it succeeded in the second and third cases. But that did it; my version 8.0 kernel booted without a hitch. I'm wondering now how best to bring the rest of the system into sync with ver 8.0; it originated in my install of 7.1.2. I have managed to get a lot of basic configuration chores completed. I'd like to spare them destruction at the hands of a stupid upgrade, i.e. one master-minded by ME. I feel ok about changing my pkgsrc host and cvs-upping the /usr/pkgsrc tree. It's the userland I worry about. All suggestions will be accepted with great applause. Thank you, and the entire group here on the list! -- Bob Bernstein
Re: Userconf & DRM driver (Was Re: Panic: no console device)
On Thu, Mar 07, 2019 at 02:53:58PM -0500, Bob Bernstein wrote: > Hi Michael. I have taken the liberty of ressurecting this post in > order to get a tad more help with its suggestion. I hope I haven't > violated any list etiquette in the process. > > On Mon, Feb 25, 2019 at 12:34:25PM -, Michael van Elst wrote: > > > It's probably trying to use a graphics card that isn't supported. > > In that case you could try to intercept the bootloader to get a > > prompt and 'boot netbsd -c'. This will start in userconf mode where, > > assuming the keyboard works, you can disable the DRM driver for > > your graphics card. When you quit userconf mode, it will then > > fall back to use the plain VGA driver. > > How can I identify the specific driver in question? Perhaps userconf > itself has a way of doing this? Is there some hallmark token for > which I should search dmest? The drivers are (for Intel, ATI and NVidia): i915drmkms radeon nouveau You can enter the commands interactively or put them into /boot.cfg as userconf=disable i915drmkms userconf=disable radeon userconf=disable neouveau or create individual boot menu entries like this to chose how to boot: menu=Boot normally:rndseed /var/db/entropy-file;boot netbsd menu=Boot with VGA:rndseed /var/db/entropy-file;userconf disable nouveau;boot netbsd Greetings, -- Michael van Elst Internet: mlel...@serpens.de "A potential Snark may lurk in every tree."
Re: Userconf & DRM driver (Was Re: Panic: no console device)
Try 'disable nouveau'. In the past I also had to 'disable genfb' on my Intel/NVidia Optimus laptop. Now it works - with intel drm, still without 3D accelleration - without disabling anything. I have another laptop with only radeonfb, a FireGL mobile card, which otherwise should have worked, but any attempt to use it hard-restes the laptop, so I have 'userconf=disable radeon*' in /boot.cfg . On Thu, 7 Mar 2019 at 19:54, Bob Bernstein wrote: > > Hi Michael. I have taken the liberty of ressurecting this post in > order to get a tad more help with its suggestion. I hope I haven't > violated any list etiquette in the process. > > On Mon, Feb 25, 2019 at 12:34:25PM -, Michael van Elst wrote: > > > It's probably trying to use a graphics card that isn't supported. > > In that case you could try to intercept the bootloader to get a > > prompt and 'boot netbsd -c'. This will start in userconf mode where, > > assuming the keyboard works, you can disable the DRM driver for > > your graphics card. When you quit userconf mode, it will then > > fall back to use the plain VGA driver. > > How can I identify the specific driver in question? Perhaps userconf > itself has a way of doing this? Is there some hallmark token for > which I should search dmest? > > -- > Bob Bernstein --
Userconf & DRM driver (Was Re: Panic: no console device)
Hi Michael. I have taken the liberty of ressurecting this post in order to get a tad more help with its suggestion. I hope I haven't violated any list etiquette in the process. On Mon, Feb 25, 2019 at 12:34:25PM -, Michael van Elst wrote: > It's probably trying to use a graphics card that isn't supported. > In that case you could try to intercept the bootloader to get a > prompt and 'boot netbsd -c'. This will start in userconf mode where, > assuming the keyboard works, you can disable the DRM driver for > your graphics card. When you quit userconf mode, it will then > fall back to use the plain VGA driver. How can I identify the specific driver in question? Perhaps userconf itself has a way of doing this? Is there some hallmark token for which I should search dmest? -- Bob Bernstein
Re: mutt wants sasl
Bob Bernstein writes: > Please forgive a history review: > > Initially, I went to install ver. 8.0 on this nvidia-infested system > while it was still running Windows 7, seeking a "dual boot" setup. > No instance of ver 8 that I tried could run on it, complaining about > "panic" over "no console device found." > > The Windows system now is long gone, but I did not find a kernel > that would boot until this was tried: > > NetBSD 7.1.2 (GENERIC.201803151611Z) amd64 > > So that's what I have running now, which may go some way to explain > why am using pkgsrc 2018Q. I am quite willing to try an upgrade to > ver. 8 but my fear is that during the upgrade I will learn once > again that ver. 8 does not boot on this box, but in the process, > have undone the 7.1.2 that to at least runs, short of using X. NetBSD 7 X11 is definitely old. It may be possible to make things work, but some of the nouveau/drm stuff I think has kernel support (things were simpler with X10 and a QDSS in uVax II!). So, one option is to switch to X11_TYPE=modular and rebuild all packages. That should help. > Can I try the upgrade without harming what's running now? You try the first step, which is what matters. You can boot a netbsd-8 kernel without changing the system on the disk you have. Just drop it in /netbsd8, and then on booting, drop to single user and "boot -s /netbsd8". If that doesn't work, capture info and ask for help - it won't have written anything. If it does, boot multiuser, and if your system is ok, then upgrade the userland bits. Or, boot off cd or a USB stick. As long as you don't overwrite your existing disk, you should be fine.
