VectorLinux 7.0 GOLD bug reports.

[stretchedthin]

Please post bug reports, suggestions, and comments for VectorLinux 7.0 GOLD

[hata_ph]

Installation when well but i notice if you install VL7-GOLD via the text installer, you cannot auto-mount your data cd in thunar...

below error show up in your $HOME/.xsession-errors

thunar-volman: could not detect the volume corresponding to the device

PS: mounting from terminal work and thunar can auto-mount my pendrive too...it seem only not working for data cd

[retired1af]

During GRUB setup, you cannot pick what OS is included in the menu. Switching to LILO allows you to uncheck OS entries, and the check boxes remain cleared when switching back to GRUB, but when it's written to the MBR, all system OS's are included in the boot menu. Bleh!

Syslog still filling up with the following:

Nov 28 12:57:19 bodacious kernel: [  996.695721] Raw EDID:
Nov 28 12:57:19 bodacious kernel: [  996.695749]
Nov 28 12:57:19 bodacious kernel: [  996.746247] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 152
Nov 28 12:57:19 bodacious kernel: [  996.746249] Raw EDID:
Nov 28 12:57:19 bodacious kernel: [  996.746276]
Nov 28 12:57:19 bodacious kernel: [  996.796607] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 152
Nov 28 12:57:19 bodacious kernel: [  996.796610] Raw EDID:
Nov 28 12:57:19 bodacious kernel: [  996.796636]
Nov 28 12:57:19 bodacious kernel: [  996.846966] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 152
Nov 28 12:57:19 bodacious kernel: [  996.846968] Raw EDID:
Nov 28 12:57:19 bodacious kernel: [  996.846995]
Nov 28 12:57:19 bodacious kernel: [  996.846999] radeon 0000:01:05.0: HDMI-A-1: EDID block 0 invalid.
Nov 28 12:57:19 bodacious kernel: [  996.847019] [drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID

And debug is filling up with this.

Nov 28 13:01:04 bodacious kernel: [ 1222.126781] <3>1f 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ................
Nov 28 13:01:04 bodacious kernel: [ 1222.126784] <3>07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ................
Nov 28 13:01:04 bodacious kernel: [ 1222.126787] <3>07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ................
Nov 28 13:01:04 bodacious kernel: [ 1222.126790] <3>07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ................
Nov 28 13:01:04 bodacious kernel: [ 1222.126793] <3>07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ................
Nov 28 13:01:04 bodacious kernel: [ 1222.126796] <3>07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ................
Nov 28 13:01:04 bodacious kernel: [ 1222.126799] <3>07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ................
Nov 28 13:01:04 bodacious kernel: [ 1222.126802] <3>07 07 07 07 07 07 07 07 07 07 07 07 07 07 07 07  ................

Ugh... >.<

nomodeset as a boot option kills the log spam.

[caieng]

http://forum.vectorlinux.com/index.php?topic=12938

Greetings to all.

Thank you for this release.  I hope to post, later, some specific comments, details, timing measurements, and so on, but, for now, I am stuck, and need some help.

There are a couple of small bugs in the installer, with fatal consequences, to those not attentive to detail.  On my fourth try, however, (the third try just halted, without explanation) I did manage to make it to the boot manager installation routine.

That is where I ran into the two bugs that held up the first two attempts--by my fourth attempt, I knew how to avoid those two errors.  More on those in a subsequent post.

This message concerns my fourth attempt, which had seemed to be moving along satisfactorily.

I had entered, when prompted, my user name and password, but, was informed, after hitting the "Enter" key,  that the single letter I had selected for a login was ALREADY TAKEN!!! That seems strange to me.  It is of course not correct, since I had reformatted the hard drive, and was now reaching this stage of the installation process for the first time.  In other words, that letter designation had never before been assigned to any user.

Regardless of whether or not it was appropriate, or inappropriate, the point is, that now, after rebooting, I reach a login screen that refuses to accept my user name and password, and also refuses to accept "root" with the password I had assigned.

In other words, I am stuck.  I can't proceed.  I would be obliged, for the fifth time, to start all over again.  This is really annoying.

There are two words at the bottom of the screen:  "session" and "activity", but I don't know, and the screen doesn't indicate, how one is supposed to change, adjust, or access either of those icons. 

Surely there must be some method to login?  By the way, some of the same problems, I encountered yesterday and today, had already been observed, and described by me, in years gone by....

CAI ENG

[hata_ph]

caieng,

You install VL7 using the GOLD or the LIVE cd?

[caieng]

Gold, because, in previous years, I had difficulty installing the "live" version.

[hata_ph]

caieng,

from your post you mention you having problem installing VL7 gold from the GUI installer, any error?
which part of installer broken for you?
can you post the spec of your install system?

[caieng]

sure, thanks for reminding me.

computer:  cpu = 1GHz Intel P3, chipset Intel 815, 0.5GB SDRAM, Seagate Sata II hard drive, video S3 AGP 2.0.

Monitor:  Vizio flat screen 26", HD 1920 x 1080.

Benchmarks:  GIPS: 2.3; GFLOPS 1.3; GBytes/sec 0.5.

Works well with several other distros, including Debian, PCLOS, & Puppy.

 

[hata_ph]

Thank for the hardware info...
ok...which part of installer fail you?

[caieng]

Thank you very much for your kindness, in helping me.

The errors in the installer, are a bit complex, and worth describing in considerable detail, right now, my hope is to find out how I can login.

Can you please tell me what is the password to login as root, since my user name is not recognized.

Once in, then, I can post from VL itself, instead of using xp as at present.

It is going to take me half an hour to write up the several problems with the installer.  I would like to get into VL first, and then explain where the bugs are, in detail.......

caieng

[hata_ph]

Since you install it from the GOLD cd, I cannot tell you what is the root password. Do you remember what root password you use? Do you key in wrongly?
So now is either to reset your root password via a live cd (http://linuxgazette.net/107/tomar.html) or reinstall it again...I would suggest the reinstall method...

[caieng]

Oh, sorry about that....

Umm, the root password is not accepted by the login, with user name as "root".

Ok, I made it in.  I typed in "root", and left the password blank!!!

haha.  remarkable.  Evidently the installer ignored my previous assignment of the proper password for root.  Wow.

Let me go play with the new distro, for a few minutes, then I will login using VL!!!  Yeah!!

caieng

[hata_ph]

Empty root password?
Are you sure you are using the GOLD cd to install?
As I know only the LIVE cd use empty root password...

[caieng]

I am in!

Hurrah!

 

Thanks for your patience.

General comments:  umm, the resolution remains mediocre (perhaps 800 x 600, not sure, don't know how to find out...)  I did run VASM and there set the resolution for 1280 x 1024 x 16 (crashes if one accepts 24 bit color, even though, both XP and Win98 run fine on this same computer at 1280 x 1024 x 32.)

Problems with the installer:
1.  This bug will not bother ANY sophisticated user, but, it trapped me...Haha, ok, so we know that I am unsophisticated.....
I prefer LILO, and when I reached the routine that asks the user to set up LILO, I clicked on the icon at the far right, to assign VL as the default, NOT XP.  
That's when I made my mistake.
The NEXT icon, on the lower half of the screen, asks the user whether or not to include XP in the boot menu.

FOOLISHLY, I disabled that option, i.e. I DISABLED it, so that ONLY VL would appear on the boot menu.  When I disabled XP, from the choices, the Installer automatically, i.e. without my doing anything, CHANGED the default setting, which I had JUST enabled, i.e. I had just assigned VL to be the default, but when I DISABLED XP from the menu, counterintuitively, the switch above it, RE-ENABLED XP as the default boot image, and, since I had not NOTICED that change, my attention being drawn, instead, toward the bottom of the screen, to click on "next", I created, unintentionally, an endless loop, a fatal error.  The system crashed of course.  

On my second attempt, I moved VERY slowly through that step of the installation, and as a result, noticed the bizarre behaviour of the software, changing my directive to regard VL as the default boot object.  
Thus, I was able to CHANGE AGAIN, that switch on the right hand side of the screen, i.e. to RE-RE-enable VL as default, after having eliminated XP from the menu.

So, now I have to figure out a lot of things here, I still don't have a user set up.  I haven't go a useable screen resolution, but, I noticed something else, just now, something which for me, represents a fatal error, one which will prevent my further testing.

There is no VLC media player.  I see a dozen other media players, but not the one I use.

 

regards,
CAI ENG

[hata_ph]

Ok...to make thing short are you saying the problem start at bootloader installation part?
You choose lilo and unmark XP...but the GUI installer will not allow you do unmark XP and the process go on continusly until it hang your entire installation process?

VLC is in the testing repo (pls remember to enable testing repo in gslapt)...you can use gslapt/slapt-get to install it...

For the screen resolution, can you check what video driver you using? Pls run lspci and lsmod as root from terminal and show the output