topic title: antiX-14R alpha3 available for testing
Posts: 4,164
rokytnji
Joined: 20 Feb 2009
#151
IBM T23. Link to kernel panic screen picture below. I am no photog guru. SHaky hands I guess.

Image

What I am currently running

Code: Select all

harry@biker:~
$ inxi -Fxz
System:    Host: biker Kernel: 3.7.10-antix.3-486-smp i686 (32 bit gcc: 4.7.3) 
           Desktop: IceWM 1.3.7 Distro: antiX-13_386-full Luddite 01 June 2013 
Machine:   Mobo: IBM model: 26474MU
           Bios: IBM v: 1AET64WW (1.20 ) date: 10/18/2006
CPU:       Single core Mobile Intel Pentium III - M (-UP-) cache: 512 KB
           flags: (pae sse) bmips: 1598 clocked at 800 MHz
Graphics:  Card: S3 SuperSavage IX/C SDR bus-ID: 01:00.0
           Display Server: X.Org 1.12.4 drivers: savage (unloaded: fbdev,vesa)
           Resolution: 1024x768@60.0hz
           GLX Renderer: Gallium 0.4 on softpipe
           GLX Version: 2.1 Mesa 8.0.5 Direct Rendering: Yes
Audio:     Card Intel 82801CA/CAM AC'97 Audio Controller 
           driver: snd_intel8x0 ports: 1c00 18c0 bus-ID: 00:1f.5 
           Sound: ALSA v: k3.7.10-antix.3-486-smp
Network:   Card-1: Intel 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller
           driver: e100 v: 3.5.24-k2-NAPI port: 6400 bus-ID: 02:08.0
           IF: eth0 state: down mac: <filter>
           Card-2: Ralink RT2800 802.11n PCI
           driver: rt2800pci v: 2.3.0 bus-ID: 07:00.0
           IF: wlan1 state: up mac: <filter>
Drives:    HDD Total Size: 80.0GB (46.1% used)
           ID-1: /dev/sda model: ST980815A size: 80.0GB
Partition: ID-1: / size: 73G used: 34G (49%) fs: ext4 dev: /dev/sda1 
           ID-2: swap-1 size: 1.12GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 47.0C mobo: 46.0C 
           Fan Speeds (in rpm): cpu: N/A fan-1: 4887 
Info:      Processes: 107 Uptime: 38 min Memory: 374.9/1007.8MB 
           Init: SysVinit runlevel: 5 Gcc sys: 4.7.2 
           Client: Shell (bash 4.2.371) inxi: 2.1.28
Like Bitjam said.
Can't win for losin'.
Sorry guys.
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#152
BitJam wrote:If the poweroff problem happens with both 32-bit (kernel 3.15) and 64-bit (kernel 3.17) then maybe it is due to something in our kernel config and not a problem upstream.
the 64 bit 3.17 kernel has not given me any problems so far. Both 3.15 versions give me fits.
BitJam wrote:This alpha has been particularly unkind to you. I'm very interested in the rootfs problems. I wouldn't be terribly surprised if you had problems like this with systemd because it bypasses our shutdown code but even then, if you do a manual persist-save and don't save on shutdown, the rootfs file should be okay.
When I have issues with rootfs, its when i boot with persistence on a pc with the intel driver issue (3.15 32bit kernel). It hangs during the boot process. I never get to a commandline. If I have to force a power off and reboot, and the rootfs will be unusable. No fsck is done as far as I can tell. choosing c=continue general just says something to the effect of"can't enable persist=root!" or some such. booting continues with the standard live and home persistence. Unfortunatley this happens alot because I forget to choose vesa on the Dell and I didn't expect the problem on the ThinkPad. The"save" feature on the liveUSB isn't holding onto the video setting or console resolution.

Interesting, you mentioned that we may move to bring up the video drivers earlier. Would that be perhaps before rootfs is mounted?

Note that while I've now tried on 4 different machines, they all use intel video chipsets.
BitJam wrote:Does the LiveUSB try to fsck the rootfs and inform you of problems at boot time?

Is it possible there is a hardware problem (usb stick starting to fail)?
I get informed of the problem and recieve the c=continue, r=reboot, p=poweroff choices. I'll have to mess up a stick and try again to see if fsck runs (luckily and I can mess up the rootfs on command!)

I haven't tried a different usb stick now that you mention it. That will be next.
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#153
back to the udev rules question:

I did delete 70-persist-net.rules, and upon reboot, the interface was reset to wlan0 and eth0. But 70-persist-net.rules returned! This is on the working 64 bit liveUSB.
Posts: 1,445
skidoo
Joined: 09 Feb 2012
#154
picture of the elusive . . . live antiX shutdown process
Could a line-by-line debug option be introduced?
Startup and / or shutdown script would source a helper script (call it echowait) and use that instead of echo.
echowait would: 1) echo, and 2) check presence of a bootline arg [return, if bootline arg NOT is set] else [echo"press [enter] to continue"][waitforkey][return]
-=-
I think I've seen such an option for line-by-line progression in (?) grml.org distro (and perhaps in knoppix)

a related thought / suggestion:
If boot is successful, can examine startup log from within session (yet currently only a colorcode escape sequence -peppered version is written, not plaintext?)
but following a live persistence shutdown (both normal or botched shutdown) we have no forensic log available. (Maybe it's written but I haven't found it?)
-=-
I wish a"lastlog" (log from prior session) was preserved, and (to cover the case of a failed shutdown)
suggest a liveboot/shutdown logfile should be written to the top level dir of the pendrive.
Posts: 1,445
skidoo
Joined: 09 Feb 2012
#155
might be helpful:
visit this refracta discussion and use the"search this thread" feature ( shutdown ) to read dzz's progress at wrestling with shutdown issue

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://refracta.freeforums.org/going-with-the-systemd-flow-or-not-t422-40.html"
linktext was:"http://refracta.freeforums.org/going-wi ... 22-40.html"
====================================
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#156
I haven't tried a different usb stick now that you mention it. That will be next.
unfortunately, my usb stick appears to be just fine.
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#157
dolphin_oracle wrote:the 64 bit 3.17 kernel has not given me any problems so far. Both 3.15 versions give me fits.
It took me a while to hearken to the fact that 32-bit and 64-bit use different kernels. Your problems with 3.15 are now a much lower priority for me because they should all be fixed by upgrading the kernel.
When I have issues with rootfs, its when i boot with persistence on a pc with the intel driver issue (3.15 32bit kernel). It hangs during the boot process.
Ah. That makes sense. Sort of.
Interesting, you mentioned that we may move to bring up the video drivers earlier. Would that be perhaps before rootfs is mounted?
Yes, they would load ASAP, before the"Welcome to xxx!" message. Anticapitalista is evaluating it now.
unfortunately, my usb stick appears to be just fine.
The"toram" option might help you avoid the destruction due to the crash. But if you could remember"toram" then you could also remember to change the video. I encourage you to use the"F6 Save" option and save the safe video setting. Let the LiveUSB remember for you.
I did delete 70-persist-net.rules, and upon reboot, the interface was reset to wlan0 and eth0. But 70-persist-net.rules returned! This is on the working 64 bit liveUSB.
That sounds like it is doing what it is supposed to do. We should be able to fix this problem by adding that file to the exclude list for root persistence and live-remaster. Thank you male for pointing out where the problem was!
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#158
The"toram" option might help you avoid the destruction due to the crash. But if you could remember"toram" then you could also remember to change the video. I encourage you to use the"F6 Save" option and save the safe video setting. Let the LiveUSB remember for you.
normally I would, but the save option doesn't seem to be functioning. I believe skidoo mentioned this as well somewhere earlier in the thread.


***yep,
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"antix.freeforu ms.org/post37359.html#p37359"
linktext was:"antix.freeforu ms.org/post37359.html#p37359"
====================================
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#159
skidoo wrote:a related thought / suggestion:
If boot is successful, can examine startup log from within session (yet currently only a colorcode escape sequence -peppered version is written, not plaintext?)
Use the -R option with less. In fact, add this line to your .bashrc file:

Code: Select all

LESS=-R
It might have been in there by default on previous versions. We used to have colored and non-colored log files using bash but we switched to the Dash shell (and perhaps there were other changes to the Debian sysVinit system) which caused us to simplify our code.
but following a live persistence shutdown (both normal or botched shutdown) we have no forensic log available. (Maybe it's written but I haven't found it?)
You can't log things without a file system to log to. There are ample debugging and verbosity options in our shutdown code via boot parameters. Use ubp=a to set a handful of breakpoints. use uverb=8 to increase what gets printed out. You can use ushow=XX to have the output of certain commands be printed out at various breakpoints. Here is a table of what it does that you might be able to decode with a little experimentation:

Code: Select all

        1) cmd=ps_no_kthreads ; show=2,3,4          ;;
        2) cmd="free -m"      ; show=2,3,5          ;;
        3) cmd=lsof           ; show=1,2,3,4        ;;
        4) cmd="df -h"        ; show=1,2,4          ;;
        5) cmd="df -ha"       ; show=1,2,4          ;;
       11) cmd=ps_no_kthreads ; show=2,3,4,10,11,12 ;;
These things were intended for internal development.

Since logging can be difficult at the end of the shutdown, I opted for breakpoints and verbosity instead.

As for debugging the systemd shutdown, I am holding out on wasting more time with it until it stops blanking the screen. With no log files and no display, experimenting and debugging gets tedious. I tried it for a day. Even without these debugging hurdles, it is a giant pain in the neck. It is like working with Windows. If what you want to do was already planned for by the devs and if there are absolutely no problems along the way then things are very easy. If there are any deviations then things veer quickly from easy to nearly impossible.
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#160
dolphin_oracle wrote:normally I would, but the save option doesn't seem to be functioning. I believe skidoo mentioned this as well somewhere earlier in the thread.

***yep,
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"antix.freeforu ms.org/post37359.html#p37359"
linktext was:"antix.freeforu ms.org/post37359.html#p37359"
====================================
I have not tested it here yet but skidoo only said:
I'm also confirming that F6 save is not preserving"console resolution". At next boot (and choosing"custom" menu line) it's back to 800x600
This is a far cry from it not working at all. It seems to imply that everything else is getting saved correctly.

If it turns out the save functionality is indeed broken then you can fall back to editing /live/boot-dev/boot/syslinux/syslinux.cfg manually. Add the"nomodeset" boot parameter.

I'm sorry 3.15 was such a lemon and that you have shouldered the brunt of the problems. I probably contributed by not realizing sooner that 32-bit was using 3.15.
Posts: 2,238
dolphin_oracle
Joined: 16 Dec 2007
#161
I have not tested it here yet but skidoo only said:
Quote:
I'm also confirming that F6 save is not preserving"console resolution". At next boot (and choosing"custom" menu line) it's back to 800x600
This is a far cry from it not working at all. It seems to imply that everything else is getting saved correctly.
you are right! I only tried the console and video menus.

So some quick testing...Save gets the F3 (timezone) and F4 menu ok (the one with toram), but is not saving the video menu (F5) nor the console menu (F6).

Don't worry about lemons...That's what alphas are for! I just hope whatever is wrong with 3.17 32 bit gets worked out, because 3.15 is a PITA.
Last edited by dolphin_oracle on 22 Oct 2014, 20:05, edited 1 time in total.
Posts: 325
male
Joined: 04 Nov 2011
#162
I can not understand what is written here partially.
I do not think is useful here the versions RV and RD to constantly mix.

To RD x86_64; with kernel 03.17; live-demo
This laptop Lenovo T500 running with an Intel card and has no problems with

Code: Select all

systemctl poweroff
or

Code: Select all

systemctl reboot
to shut down or restart.

Code: Select all

demo@antix1:~
$ inxi -F
System:    Host: antix1 Kernel: 3.17.0-antix.1-amd64-smp x86_64 (64 bit) Desktop: Fluxbox 1.3.5 
           Distro: antiX-14-a3-RD_x64-full Killah P 11 October 2014 
Machine:   System: LENOVO product: 20564QG v: ThinkPad T500
           Mobo: LENOVO model: 20564QG Bios: LENOVO v: 6FET83WW (3.13 ) date: 03/15/2010
CPU:       Dual core Intel Core2 Duo T9400 (-MCP-) cache: 6144 KB 
           Clock Speeds: 1: 800 MHz 2: 1600 MHz
Graphics:  Card: Intel Mobile 4 Series Integrated Graphics Controller
           Display Server: X.Org 1.16.1 drivers: intel (unloaded: fbdev,vesa) Resolution: 1680x1050@59.98hz
           GLX Renderer: Mesa DRI Mobile Intel GM45 Express GLX Version: 2.1 Mesa 10.2.6
Audio:     Card Intel 82801I (ICH9 Family) HD Audio Controller driver: snd_hda_intel 
           Sound: Advanced Linux Sound Architecture v: k3.17.0-antix.1-amd64-smp
Network:   Card-1: Intel 82567LM Gigabit Network Connection driver: e1000e
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
           Card-2: Intel PRO/Wireless 5100 AGN [Shiloh] Network Connection driver: iwlwifi
           IF: wlan0 state: down mac: <filter>
Drives:    HDD Total Size: NA (-) ID-1: /dev/sda model: HITACHI_HTS54501 size: 160.0GB
           ID-2: USB /dev/sdb model: TransMemory size: 7.8GB
Sensors:   System Temperatures: cpu: 40.0C mobo: 38.0C 
           Fan Speeds (in rpm): cpu: N/A fan-1: 0 
Info:      Processes: 124 Uptime: 13 min Memory: 389.9/3851.4MB Client: Shell (bash) inxi: 2.1.28
Posts: 325
male
Joined: 04 Nov 2011
#163
the forum software is to beep..

When I call error messages, then get this insignificant

Code: Select all

journalctl -b -p err
(--) Logs begin at Mi 2014-10-22 21:17:32 CEST, end at Mi 2014-10-22 21:31:21 CEST. (--)
Okt 22 21:17:32 antix1 kernel: sd 6:0:0:0: [sdb] No Caching mode page found
Okt 22 21:17:32 antix1 kernel: sd 6:0:0:0: [sdb] Assuming drive cache: write through
Okt 22 21:17:32 antix1 systemd-sysv-generator[824]: Failed to read configuration file ('/)etc(/)init.d(/)debian': Is a directory
Okt 22 21:17:37 antix1 ntpdate[2108]: Can't find host 0.debian.pool.ntp.org: Name or service not known (-2)
Okt 22 21:17:37 antix1 ntpdate[2108]: Can't find host 1.debian.pool.ntp.org: Name or service not known (-2)
Okt 22 21:17:37 antix1 ntpdate[2108]: Can't find host 2.debian.pool.ntp.org: Name or service not known (-2)
Okt 22 21:17:37 antix1 ntpdate[2108]: Can't find host 3.debian.pool.ntp.org: Name or service not known (-2)
Okt 22 21:17:37 antix1 ntpdate[2108]: no servers can be used, exiting
Okt 22 21:17:39 antix1 kernel: fbcondecor: picture dimensions mismatch
Okt 22 21:17:39 antix1 kernel: 1280x1024 vs 1680x1050
Okt 22 21:17:39 antix1 bluetoothd[2261]: Sap driver initialization failed.
Okt 22 21:17:39 antix1 bluetoothd[2261]: sap-server: Operation not permitted (1)
Okt 22 21:17:40 antix1 slim[2294]: PAM unable to dlopen(pam_gnome_keyring.so): ()lib()security()pam_gnome_keyring.so: cannot open shared object file: N
Okt 22 21:17:40 antix1 slim[2294]: PAM adding faulty module: pam_gnome_keyring.so
Where can I still help?
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#164
dolphin_oracle wrote:[...], but is not saving the video menu (F5) nor the console menu (F6).
I will add fixing that to my TODO list. Not saving the console setting was already on it.
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#165
@male, do plain old /sbin/reboot and /sbin/poweroff work with systemd? Are they deprecated? The systemctl program does not exist on non-systemd systems. I hope we are not going to need to add code to detect if systemd is running in order to poweroff or reboot from within a script.