- This topic has 35 replies, 9 voices, and was last updated May 14-5:54 pm by ramchip.
-
Posts
-
ramchip
I repeated the download from the Danish mirror only to find that the checksum is the same (beginning “be12”) as my original file.
According to the mirror md5 file this is correct. So, my original download was also good.
I think the checksum beginning “14f3” must be wrong.
This means I’m ready to post the dmesg just as soon as I can get it off Athlon.
Now, where did I put that floppy disc?Okay, so to be clear on the current situation, these are my findings:
1) The slash screen now appears after every boot. N.B. This was the original fault and I’ve not tweaked anything to get this right, it just happened!
2) I have never seen the “Exit Session” window appear from the Menu logout option, but it can be accessed from terminal by entering desktop-session-exit.
3) In order to perform a clean shutdown I log-in as root and issue a shutdown command.When I try submitting the dmesg in full, I get this:
“403 Forbidden
A potentially unsafe operation has been detected in your request to this site.”
What next?
rokytnji
When I try submitting the dmesg in full, I get this:
“403 Forbidden
A potentially unsafe operation has been detected in your request to this site.”
What next?Use a site like this and paste the link to the file here
https://pastebin.com/You are getting hammered by the forum site spam filters is why you are getting the forbidden error. You can also make a text file and tar it up and upload here. tar works ok on upload here so far in my experience on this forum. Not sure about tar.bz2 or zip though since I don’t use those on this site.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsThanks rokytnji, the pastebin activation e-mail is slow in coming through, so I’ve had to send them a message about it.
Btw, just noticed my typo in #9884. Item one s/be splash screen.
I’ll get back when pastebin wake up.Decided to give tar a try.
Please see attached file.Okay, now I have a pastebin account, here’s the link to Athlon’s full dmesg:
https://pastebin.com/ZtfpR4NBA word about the name of this forum “New users”, which I find slightly misleading.
Am I new to AntiX? Yes, I discovered it only last month!
Am I new to Unix in general? No, I have around 35 years’ experience, if you count an excellent O/S called GCOS (Honeywell).
So, am I a new user? Yes and No!
Define “new user”.To get back on track with AntiX on Athlon, the main concern is the strange behaviour of the windows managers not displaying the “Exit Session” options.
Is the AGP error bogus in this respect? Probably, but I would like to see it working as expected, if possible.
sleekmason
Nvidia board detected. Ignoring ACPI timer override.
This is interesting . . . changed video card?
–
Anyway,
–
[ ` 45.559715] [drm:radeon_agp_init [radeon]] *ERROR* Unable to acquire AGP: -19
[ 45.559723] [drm] Forcing AGP to PCIE mode
[ 45.559733] radeon 0000:03:00.0: VRAM: 512M 0x0000000000000000 – 0x000000001FFFFFFF (512M used)
[ 45.559736] radeon 0000:03:00.0: GTT: 512M 0x0000000020000000 – 0x000000003FFFFFFF
[ 45.559741] [drm] Detected VRAM RAM=512M, BAR=256M
[ 45.559742] [drm] RAM width 256bits DDR
[ 45.559839] [TTM] Zone kernel: Available graphics memory: 433670 kiB
[ 45.559840] [TTM] Zone highmem: Available graphics memory: 1551850 kiB
[ 45.559841] [TTM] Initializing pool allocator
[ 45.559849] [TTM] Initializing DMA pool allocator
[ 45.559888] [drm] radeon: 512M of VRAM memory ready
[ 45.559890] [drm] radeon: 512M of GTT memory ready.`Looks like it has initialized using pci.
Look at:
lspci -kto list the kernel drivers in use. Look for your graphics card and the related modules/drivers.
–
–
Okie Dokie, let’s get on track here. Can you change your session to fluxbox window manager? Change to fluxbox, right click to open the menu, at the bottom is “Exit”. You should get a box with exit options. Does this work in fluxbox? (yes, I note you said managers, but thought I better double check:) This will certainly narrow it down if confined to IceWM.Okay sleek, I have not changed any hardware since the CPU and RAM upgrades just before installing AntiX. The video card is the same and the kernel driver and module are reported as “radeon” by the lspci command.
I confirm that fluxbox does not present an exit menu after right-clicking and selecting exit.
The screen flashes back to the system console momentarily, then the login screen is displayed with the familiar message “(Press F1 to toggle sessions)”.
It’s a strange one!Another point I would like to return to is the USB memory stick usage.
My Ubuntu machine mounts USB sticks automatically, so is there a special tweak needed for AntiX to do the same?sleekmason
The video card is the same and the kernel driver and module are reported as “radeon” by the lspci command.
Well, at least something good:) Sounds like a separate issue to be sure.
is there a special tweak needed for AntiX to do the same?
–
No, there shouldn’t be anything necessary as far as I know.
–
–
We are at the limit of my knowledge. The only things I would suggest at this point is doing a dist-upgrade as a parting shot. The antiX developers may have some info and/or better ideas.
Brian Masinick
Glad you spotted the incorrect checksum; that undoubtedly accounts for most, if not all of the issues.
For what it is worth, if you are able to get to a console or other “terminal interface”, typing in poweroff from a root or other administrative access point – or type in sudo poweroff from a user account, you can shutdown and turn off power – the “poweroff” is equivalent to a shutdown -P – halt and turn off power.
--
Brian Masinick
Dave
Could you provide links to the incorrect checksum location? I do see with both my copy from sourceforge and the head mirror server that the checksum is the be12 one.
Does pressing shutdown from desktop-session-exit in terminal successfully shutdown?
Could you post the ~/.(your-wm-here)/menu file? Also maybe a screenshot of the desktop when you are using the menu to try and shutdown?
Did you reuse the home directory at all from something else? If you make a new test user and login as that user, does the problem still exist under the new user account?
Maybe a copy of slim.conf, ~/.desktop-session/log, and ps -ef to see what is running and how it may be started?
It seems extremely odd that all menus configured to run a script are running a different program. Especially when you can run the program manually…..
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
Thanks Dave, et al.
Limited time today, so can’t say where incorrect checksum was seen at the moment.
I can confirm that shutdown is successful from desktop-session-exit in terminal.
This machine was host to Ubuntu 12 in January.
I was experiencing trouble with browsers and discovered that AntiX was reported as the best distro for this motherboard.
The reason given was that it avoids SSE2 instructions that are not executable on an Athlon processor.
The AntiX installation was supposed to overwrite everything in root.
Remember, I had to be cautious because this is a dual-boot machine and I didn’t want to harm the other O/S.I’m not sure what you are asking me to post.
Where is the icewm menu file?
What’s the easiest way to generate a screenshot?
Where is slim.conf?
A directory map for AntiX would help.
I know the generic Linux directory structure, circa 1995, but one particular to AntiX would be useful, if there are any significant variations.
I can live with the quirky shutdown procedure for now, but if a USB port works for a mouse, then why not for a memory stick?
What’s the file system listener daemon for USB ports?
Is there an installation log file anywhere on the system that might help trace these problems?Dave
The AntiX installation was supposed to overwrite everything in root.
In the installer did you check preserve home / root, or did you allow it to format the home / root directory?
Where is the icewm menu file?
/home/USER/.icewm/menu
What’s the easiest way to generate a screenshot?
antixscreenshot.sh I think it should be in the menu…
Where is slim.conf?
/etc/slim.conf
A directory map for AntiX would help.
I know the generic Linux directory structure, circa 1995, but one particular to AntiX would be useful, if there are any significant variations.In terminal as root
find / | less -S
Should make a pageable oneThe USB should work. Try spacefm session.
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
oldman
ramchip,
I mount usb sticks from the console command prompt, with sudo mount -t vfat /dev/sdf1 /mnt/usbdrive having first created the directory in /mnt.
But I expect that you are familiar with that method.Brian Masinick
Momentarily, I can see a console screen full of startup information (“Welcome to AntiX”, etc.) and a login prompt, before the login splash screen reappears.
The image displayed is a deserted station platform and a train with unnatural light beams.What next?
I’m not sure that any of us have actually solved the fundamental problem, but my conjecture on this, based on past experiences, though limited by not actually witnessing what is taking place, is that two things are likely to either be potential causes of the problem, or at least able to reduce potential cause, which will help find the actual culprit:
1. One of the first things I check – first at the user account level, then throughout the filesystems (being MUCH more careful about changing ANYTHING at the file system level unless I’m willing to scrap and replace the system entirely). Sometimes, something as simple as: sudo chown -R myuser:mygroup $HOME – that is making sure that ALL files within my user account are actually owned by me and managed by my groupID – solves my own most common problems; try it to see if it helps in any way for you.
2. The hardware you are using – for whatever reason – is not properly configured or supported by the installation or something got accidentally or indvertently altered during installation, configuration, or day to day use. If other distributions work fine and you know something about where certain capabilities are stored, you can compare configuration and setup scripts and data files to see if anything really obvious is changed. You can also save a particular file – copy it or back it up somewhere, then copy another distribution’s file in it’s place. If it fixes the issue, keep it; otherwise restore the original; make one change at a time. That’s another way to hack your way to a solution. The more practice you have doing this, the better you’ll be able to give an educated guess about what is wrong.
If you back up the entire system plus a separate backup of specific changes you make, you can get pretty crazy with what you change, yet recover from it if it doesn’t work. Of course you can also trash the entire setup and start over; unless you have a lot of difficult to replace information, it may be better to do this, copying back in the files and features you need. Trying out a completely replaced image and cleaned out data may help isolate issues too. I hope this helps with your diagnosis.
- This reply was modified 5 years ago by Brian Masinick.
--
Brian Masinick
- You must be logged in to reply to this topic.
