Posted: Wed 17 Jul 2019, 18:42
Open a terminal, type inxi -F.TiredPup, would you please tell how you got all that information?
READ-ONLY Archive
https://oldforum.puppylinux.com/
Open a terminal, type inxi -F.TiredPup, would you please tell how you got all that information?
Also, while in Pup-SysInfo, go to menu bar -> Sys-Apps -> InxiTiredPup wrote:Open a terminal, type inxi -F.TiredPup, would you please tell how you got all that information?
When I boot with grub4dos from pendrive (legacy boot) I do not have any problem either. The boot messages come at the normal pace.radky wrote: I boot with legacy grub and only one pupsave, so nothing in the boot process seems unusal to me.
I think recent updates of Peebee's Disco Dingo include the updated init. Do you observe the same behavior in Disco Dingo?
THANKS, TiredPup and radky!radky wrote:Also, while in Pup-SysInfo, go to menu bar -> Sys-Apps -> InxiTiredPup wrote:Open a terminal, type inxi -F.TiredPup, would you please tell how you got all that information?
System: Host: puppypc8744 Kernel: 4.19.56-buster i686 bits: 32 Desktop: JWM 2.3.7
Distro: Puppy 8.0
Machine: Type: Laptop System: Dell product: Latitude E6410 v: 0001 serial: BBSZSM1
Mobo: Dell model: 04373Y v: A03 serial: /BBSZSM1/CN1296112K0119/ BIOS: Dell v: A11
date: 11/30/2011
CPU: Topology: Dual Core model: Intel Core i5 M 560 bits: 64 type: MT MCP
L2 cache: 3072 KiB
Speed: 1526 MHz min/max: 1199/2667 MHz Core speeds (MHz): 1: 1323 2: 1302 3: 1313
4: 1320
Graphics: Device-1: Intel Core Processor Integrated Graphics driver: i915 v: kernel
Display: server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 1280x800~60Hz
OpenGL: renderer: Mesa DRI Intel Ironlake Mobile x86/MMX/SSE2 v: 2.1 Mesa 18.3.6
Audio: Device-1: Intel 5 Series/3400 Series High Definition Audio driver: snd_hda_intel
Sound Server: ALSA v: k4.19.56-buster
Network: Device-1: Intel 82577LM Gigabit Network driver: e1000e
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 5c:26:0a:3c:77:eb
Device-2: Qualcomm Atheros AR9285 Wireless Network Adapter driver: ath9k
IF: wlan0 state: up mac: 5c:ac:4c:75:28:12
IF-ID-1: tunl0 state: down mac: 00:00:00:00
Drives: Local Storage: total: 585.00 GiB used: 59.61 GiB (10.2%)
ID-1: /dev/sda vendor: Crucial model: M4-CT128M4SSD2 size: 119.24 GiB
ID-2: /dev/sdb vendor: HGST (Hitachi) model: HTS545050A7 size: 465.76 GiB
Sensors: System Temperatures: cpu: 63.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info: Processes: 142 Uptime: 2h 54m Memory: 3.73 GiB used: 1.02 GiB (27.3%) Shell: bash
inxi: 3.0.34
@cthisbear,Just to confirm that Simplecom (NW601 Wireless adapter) in Radky Buster Pup will not connect.
Thanks!For those with really old machines a series 3 kernel maybe better so here is one I made.
Thanks for the report!My thanks as I report I'm now starting day 7 of full-time-use of your BusterPup 8.0 CE (Beta-1) with not the slightest hint of a hitch here.
I just put Disco Dingo on the primary drive, did grub4dosconfig, and rebooted. All looked quite normal. I don't fully understand what foxpup was saying, sorry.radky (in part) wrote:foxpup wrote (in part):I think recent updates of Peebee's Disco Dingo include the updated init. Do you observe the same behavior in Disco Dingo?I've noticed that the text that comes just after grub, from init I suppose, kicks in only after switch root...
Code: Select all
# ls -l /initrd/mnt/dev_save/dingo/
total 228848
-rw-r--r-- 1 root root 1289947 Jul 13 17:04 initrd.gz
-rw-r--r-- 1 root root 203186176 Jul 13 17:07 puppy_upupdd_19.04.sfs
-rw-r--r-- 1 root root 5528448 Mar 14 23:46 vmlinuz
-rw-r--r-- 1 root root 24334336 Mar 15 00:43 zdrv_upupdd_19.04.sfs
In BusterPup Beta-1, foxpup describes a normal boot sequence when he utilizes a pendrive and grub4dos with 'one' or 'multiple' pupsave files.I just put Disco Dingo on the primary drive, did grub4dosconfig, and rebooted. All looked quite normal. I don't fully understand what foxpup was saying,
radky wrote:sheldonisaac wrote:In BusterPup Beta-1, foxpup describes a normal boot sequence when he utilizes a pendrive and grub4dos with 'one' or 'multiple' pupsave files.I just put Disco Dingo on the primary drive, did grub4dosconfig, and rebooted. All looked quite normal. I don't fully understand what foxpup was saying,
However, with recent iterations of the 4.19.X kernel, when foxpup boots his SSD drive (SAMSUNG MZYTY256) with EFI/grub2 and multiple pupsaves, the usual list of selectable pupsaves does not appear on screen, so no way to choose the desired pupsave file. He has no problem when booting with EFI/grub2 and one pupsave.
Interestingly, on his EFI/grub2 installation of BusterPup with multiple pupsaves, the list of selectable pupsaves appears as expected when he boots with the Dpup Stretch 4.9.X kernel (such as 4.9.149) or with older iterations of the 4.19.X kernel (such as 4.19.26).
Just my interpretation of what happens:Terry H wrote: With 1 save folder there is a noticeable pause on boot with a black screen then boot was successful.
Ah, thanks, radky; and Terry H and foxpup. I'll stand on the 'sidelines', and hope to see that the problems are solved.radky wrote:sheldonisaac wrote:In BusterPup Beta-1, foxpup describes a normal boot sequence when he utilizes a pendrive and grub4dos with 'one' or 'multiple' pupsave files.I just put Disco Dingo on the primary drive, did grub4dosconfig, and rebooted. All looked quite normal. I don't fully understand what foxpup was saying,
However, with recent iterations of the 4.19.X kernel, when foxpup boots his SSD drive (SAMSUNG MZYTY256) with EFI/grub2 and multiple pupsaves, the usual list of selectable pupsaves does not appear on screen, so no way to choose the desired pupsave file. He has no problem when booting with EFI/grub2 and one pupsave.
Interestingly, on his EFI/grub2 installation of BusterPup with multiple pupsaves, the list of selectable pupsaves appears as expected when he boots with the Dpup Stretch 4.9.X kernel (such as 4.9.149) or with older iterations of the 4.19.X kernel (such as 4.19.26).