Re: NetBSD 10.0 installation cd boot hangs

2024-05-30 Thread RVP

On Thu, 30 May 2024, e...@tilde.team wrote:


On Tue, May 28, 2024 at 08:51:00PM +, RVP wrote:


In your BIOS, can switch the drive controller to `AHCI' instead of whatever
it is now (probably IDE)?

-RVP


It is a SATA drive, and no opportunities to change anything regarding
the drive in the BIOS.



Not the drive: change the drive-controller mode if possible. The `ahcisata'
driver should get used here rather than `viaide', I think.

-RVP


Re: NetBSD 10.0 installation cd boot hangs

2024-05-30 Thread esg
On Tue, May 28, 2024 at 01:26:53PM +0100, Stephen Borrill wrote:
> On Mon, 27 May 2024, e...@tilde.team wrote:
> 
> > On Sat, May 25, 2024 at 03:09:14PM +0200, Martin Husemann wrote: 
> I think Benny meant ? at the boot device: prompt, not the boot prompt. We
> know that the boot loader can read the CD as it has loaded the kernel. Your
> problem with this is the next paragraph though:
> 

OK, I understand now. I wasn't sure if the 'boot device:' was a prompt,
but it make sense.

> Yes, this has been a problem since I don't know when. USB keyboards often
> fail to operate at this point. Without a PS/2 keyboard (or serial console),
> you may be stuck.

I see. The computer is unfortunately to new to have any PS/2 ports, serial
console might be better. The amd64 installation CD does not have serial
console support by default it seems?

> 
> You could try an older installation CD for laughs. In the olden days, the
> installation ramdisk was embedded in the INSTALL kernel, so at least it
> would start even if you couldn't read the install sets from the CD.
> 
> You could try loading amd64/installation/miniroot/miniroot.kmod from the
> boot loader.
> 
> Or just boot from USB...
> 

I just did that. I cannot boot from a USB memory stick (the BIOS does not
seem to be able to?); but I can boot from a USB CD drive that I had lying
around. Booting from that progresses a bit further than the earlier impasse,
but eventually ends with a kernel panic. I'm happy to supply further details
if anyone is interested, but I don't think I can figure this out myself.


> > I don't know where 'fd1' comes from - there is only one floppy drive.
> 
> Not sure, but it wouldn't surprise if those were hard-wired in on the BIOS

That would make sense.

/Emil


Re: NetBSD 10.0 installation cd boot hangs

2024-05-30 Thread esg
On Tue, May 28, 2024 at 08:51:00PM +, RVP wrote:
> On Thu, 23 May 2024, e...@tilde.team wrote:
> 
> > [ 301.7983080] waiting for devices: atabus1 atabus2 atabus3
> > viaide0 channel 1: reset failed for drive 0
> > 
> 
> In your BIOS, can switch the drive controller to `AHCI' instead of whatever
> it is now (probably IDE)?
> 
> -RVP

It is a SATA drive, and no opportunities to change anything regarding
the drive in the BIOS.

Emil


Re: NetBSD 10.0 installation cd boot hangs

2024-05-28 Thread RVP

On Thu, 23 May 2024, e...@tilde.team wrote:


[ 301.7983080] waiting for devices: atabus1 atabus2 atabus3
viaide0 channel 1: reset failed for drive 0



In your BIOS, can switch the drive controller to `AHCI' instead of whatever
it is now (probably IDE)?

-RVP


Re: NetBSD 10.0 installation cd boot hangs

2024-05-28 Thread Stephen Borrill

On Mon, 27 May 2024, e...@tilde.team wrote:


On Sat, May 25, 2024 at 03:09:14PM +0200, Martin Husemann wrote:

On Sat, May 25, 2024 at 03:00:24PM +0200, Benny Siegert wrote:

This is technically not a hang. The kernel did not find the device to boot
from, so it is waiting for you to enter one. Are you expecting the device on
the SATA bus? -- Benny



I guess it should show up in the viaide controller, but:


viaide0 channel 1: reset failed for drive 0


says it did not work well.

You could try to list the available devices by entering

?

at the boot prompt (but I guess your CD will be missing).


Thanks both. My understanding of the boot process is rudimentary, so
I don't quite uniderstand this: Somehow it does find the boot device
(in some sense) since it does start the boot process - so why is it
complaining about the "boot device: "?


I think Benny meant ? at the boot device: prompt, not the boot prompt. We 
know that the boot loader can read the CD as it has loaded the kernel. 
Your problem with this is the next paragraph though:



Also: I don't know if it has technically hanged, but I cannot type
anything (even though there is a cursor at the end of "root device: "
and the computer is not responding to any keyboard input that I have
tried, so I have to hard restart it by pressing the power button
for a long time.


Yes, this has been a problem since I don't know when. USB keyboards often 
fail to operate at this point. Without a PS/2 keyboard (or serial 
console), you may be stuck.


You could try an older installation CD for laughs. In the olden days, the 
installation ramdisk was embedded in the INSTALL kernel, so at least it 
would start even if you couldn't read the install sets from the CD.


You could try loading amd64/installation/miniroot/miniroot.kmod from the 
boot loader.


Or just boot from USB...


typing 'dev' at the boot prompt gives the following output:

   disk hd0 size 223 GB
   disk fd0
 fd0a
   disk fd1
 fd1a
   default cd0a

I don't know where 'fd1' comes from - there is only one floppy drive.


Not sure, but it wouldn't surprise if those were hard-wired in on the 
BIOS.


--
Stephen



Re: NetBSD 10.0 installation cd boot hangs

2024-05-27 Thread esg
On Sat, May 25, 2024 at 03:09:14PM +0200, Martin Husemann wrote:
> On Sat, May 25, 2024 at 03:00:24PM +0200, Benny Siegert wrote:
> > This is technically not a hang. The kernel did not find the device to boot
> > from, so it is waiting for you to enter one. Are you expecting the device on
> > the SATA bus? -- Benny
> > 
> 
> I guess it should show up in the viaide controller, but:
> 
> > viaide0 channel 1: reset failed for drive 0
> 
> says it did not work well.
> 
> You could try to list the available devices by entering
> 
>   ?
> 
> at the boot prompt (but I guess your CD will be missing).

Thanks both. My understanding of the boot process is rudimentary, so
I don't quite uniderstand this: Somehow it does find the boot device
(in some sense) since it does start the boot process - so why is it
complaining about the "boot device: "?

Also: I don't know if it has technically hanged, but I cannot type
anything (even though there is a cursor at the end of "root device: "
and the computer is not responding to any keyboard input that I have
tried, so I have to hard restart it by pressing the power button 
for a long time.

typing 'dev' at the boot prompt gives the following output:

disk hd0 size 223 GB
disk fd0
  fd0a
disk fd1
  fd1a
default cd0a

I don't know where 'fd1' comes from - there is only one floppy drive.

/Emil


Re: NetBSD 10.0 installation cd boot hangs

2024-05-25 Thread Martin Husemann
On Sat, May 25, 2024 at 03:00:24PM +0200, Benny Siegert wrote:
> This is technically not a hang. The kernel did not find the device to boot
> from, so it is waiting for you to enter one. Are you expecting the device on
> the SATA bus? -- Benny
> 

I guess it should show up in the viaide controller, but:

> viaide0 channel 1: reset failed for drive 0

says it did not work well.

You could try to list the available devices by entering

?

at the boot prompt (but I guess your CD will be missing).

Martin


Re: NetBSD 10.0 installation cd boot hangs

2024-05-25 Thread Benny Siegert



Am 23.05.24 um 18:43 schrieb e...@tilde.team:


The installation hangs after a while; I'm copying the last bit of the
messages below:

[   2.6297051] ukbd0 at uhidev0
[   2.6297051] wskbd1 at ukbd0 mux 1
[  61.6629741] waiting for devices: atabus1 atabus2 atabus3
[ 121.6968080] waiting for devices: atabus1 atabus2 atabus3
[ 181.7306411] waiting for devices: atabus1 atabus2 atabus3
[ 241.7644750] waiting for devices: atabus1 atabus2 atabus3
[ 301.7983080] waiting for devices: atabus1 atabus2 atabus3
viaide0 channel 1: reset failed for drive 0
[ 311.2736479] WARNING: system needs entropy for security; see entropy(7)
[ 311.2736479] swwdog0: software watchdog initialized
[ 311.2736479] WARNING: 1 error while detecting hardware; check system log.
[ 311.2736479] boot device: 
[ 311.2736479] root device:

This is where it hangs. Happy to hear any suggestions.


This is technically not a hang. The kernel did not find the device to 
boot from, so it is waiting for you to enter one. Are you expecting the 
device on the SATA bus? -- Benny




NetBSD 10.0 installation cd boot hangs

2024-05-23 Thread esg
Hi,

I have some older hardware that I am currently trying to install NetBSD
on. In some cases I have not yet succeded; I'll describe one case here
and start another thread for a different computer.

The situation is that I have a Dell Optiplex 740 which happily ran NetBSD
for a long time, but the HDD failed, so I replaced it with an SSD, and
I'm trying to install NetBSD 10.0 (amd64) on it.

The installation hangs after a while; I'm copying the last bit of the
messages below:

[   2.6297051] ukbd0 at uhidev0
[   2.6297051] wskbd1 at ukbd0 mux 1
[  61.6629741] waiting for devices: atabus1 atabus2 atabus3
[ 121.6968080] waiting for devices: atabus1 atabus2 atabus3
[ 181.7306411] waiting for devices: atabus1 atabus2 atabus3
[ 241.7644750] waiting for devices: atabus1 atabus2 atabus3
[ 301.7983080] waiting for devices: atabus1 atabus2 atabus3
viaide0 channel 1: reset failed for drive 0
[ 311.2736479] WARNING: system needs entropy for security; see entropy(7)
[ 311.2736479] swwdog0: software watchdog initialized
[ 311.2736479] WARNING: 1 error while detecting hardware; check system log.
[ 311.2736479] boot device: 
[ 311.2736479] root device:

This is where it hangs. Happy to hear any suggestions.

/emil