Menu
▾
▴
vectorlinux-devel
|
From: Masta M. <mas...@gm...> - 2009-09-29 18:14:53
|
Looks like we're back to having operating systems listed in the selection
page of the installer again. This is great, no "Tab0" filled with empty
space.
Grub:
Installs ok according to installer, but upon first reboot I am
presented with the grub command line "sh:grub>" .
Ran through installer again. Selected Lilo instead of grub. Lilo returns an
error. No vmlinuz
Importing users:
I did have an issue with importing users made via
the kde4 system control. However I was always able to import my "Masta" user
account which was originally created via installer. This time, I am not able
to import any users. Fails and says to read output, which simply says failed
(I'll try running log from terminal on next install attempt/test to
hopefully get better output on this particular part).
That's it for this testing session.
|
|
From: M0E L. <m0...@gm...> - 2009-09-29 18:22:38
|
I'm still working out issues that arose from the migration to a new config file for the ISO. It's not all sorted out yet, but it will be soon. |
|
From: paul m. <pa...@wa...> - 2009-09-29 19:26:15
|
:( Installer looked ok, but failed to create a user (I didn't import, since I couldn't remember the user name I'd been using for the alphas...). At that point the installer fell over. I had skipped the bootloader install (already have Grub legacy installed). When I attempted to boot, I found no vmlinuz and no kernel modules had been installed. One observation - moving to .txz packages will break MC's ability to view package contents. The svn version of MC that is being used by Slackware is badly broken - from my point of view, the most important problem with it being the fact that Fish no longer works properly. I use Fish far too much to be able to move to any version of MC that doesn't support it properly. This one is far more broken on my hardware than most of the ones I've tried recently. paul. Masta MCF wrote: > Looks like we're back to having operating systems listed in the > selection page of the installer again. This is great, no "Tab0" filled > with empty space. > Grub: > Installs ok according to installer, but upon first reboot I am > presented with the grub command line "sh:grub>" . > > Ran through installer again. Selected Lilo instead of grub. Lilo returns > an error. No vmlinuz > > Importing users: > I did have an issue with importing users made > via the kde4 system control. However I was always able to import my > "Masta" user account which was originally created via installer. This > time, I am not able to import any users. Fails and says to read output, > which simply says failed (I'll try running log from terminal on next > install attempt/test to hopefully get better output on this particular > part). > > That's it for this testing session. |
|
From: M0E L. <m0...@gm...> - 2009-09-29 19:29:13
|
The installer is crashing when creating a new user because of the netdev group issue. It attemps to add the user to a group that does not exist. As a temporary work around, I have added code to create this group before the user creation window even shows up, but this really needs to be addressed in the vlconfig2 package. The no kernel problem is related to the switching of config files... I'm brushing that out now. |
|
From: Newt <gen...@gm...> - 2009-09-30 19:26:48
|
Hello,
Just some installer notes. I will file these as bugs later:
1.38 (non-txz), r869:
-reiser4 is available in gparted but fails to work
-at cd switching time:
-Step9.install_kernels.117: Installing /mnt/source/isolinux/kernel/sata as /mnt/target/vmlinuz-2.6.27.34
-The actual location is /mnt/target/boot/
Bootloader:
-'next' button issue persists (either going back to bootloader page or on fail_but_remain_at_page)
-both bootloader config files point to the actual full kernel name rather than the symlink 'vmlinuz' - just an observation
Lilo:
-'initrd =' and 'read-only' are missing from safe mode option
-timeout has no effect
-any label that is 15 characters and ends with '-cli' cause a lilo failure. Is there a way to make 15 character labels ending in '-cli' unusable?
-points to
Grub:
-nowhere in grub.cnf do I see where the resolution is set. I see where the background is chosen based on the user's resolution choice, but no where is the actual framebuffer resolution set. Seems like I recall this being explicitly set in previous testing.
-the background image always stays with the silent-800x600.jpg; is that supposed to be that way?
-recovery mode does an 'insmod ext2'; is that supposed to be there?
Cheers, newt
|
|
From: M0E L. <m0...@gm...> - 2009-09-30 19:36:22
|
Nothing I can do about the reiser4 option in gparted. The kernel does not support it, but we seem to have libraries for it, which explains the option being available. The kernel copying debug line is just that...debugging. Can you make sure it's getting installed to the correct place? I've checked here and it does copy it to /boot, not /. Let me know if you find otherwise. I will address the lilo label issues soon, as well as the timeout issue. The next button issue is kind of a side effect to a safety net that I put in place there. The button becomes active once you click on a bootloader option. the kernel line is supposed to point to the actual kernel name.. I did that on purpose. Keeps me from generating double entries, and getting invalid filenames. About grub. You will not find the resolution choice in grub.cfg. It does not go there. Look in /etc/default/grub The background image will stay at 800x600 unless a bigger one is provided. Grub does not resize the image. All the grub configuration is automatically generated. I only control the vga mode, and time out. HTH |
|
From: Newt <gen...@gm...> - 2009-09-30 20:32:24
|
Hello, Notes from first boot of 1.38(non-txz): First boot: -Grub failure: "error: You need to load the kernel first. Failed to boot default entries. Press any key to continue..." -both entries have insmod ext2 -both entries request that kernel comes first -after making kernel first, it complained about device uuid; luckily I had installed lilo to sector and was able to use grub command to chainload lilo which booted the system Cheers, newt |
|
From: M0E L. <m0...@gm...> - 2009-09-30 20:37:52
|
I know the grub package just got updated. This may be related to the upgrade. @ Newt Please update your installer source/binary and try now for the lilo timeout. I think I got it fixed. |
|
From: Newt <gen...@gm...> - 2009-10-02 03:11:17
|
Hello All,
More notes from install:
1.39, r879:
-disc partitioning options wavered: first time there both options available (this is correct), clicked back,
clicked search again, clicked next - this time only 'Help me resize my partitions' option was available.
Note: I already have partitions sda1/reiser, sda2/reiser, sda3/swap
-restarted installer: If I do not ever click 'search again' then both partitioning options remain available.
It has something to do with clicking the 'search again' button
-restarted installer: this time I started off by clicking the 'search again' button three times before moving
forward and only got the one disc partitioning option ('Help me resize my partitions').
-restarted installer: just clicked next through the first couple pages and was able to use existing paritions
-flash of black when scroller starts
-I did not play with the bootloader much other than to put lilo on sector and grub on mbr; both worked out
fine with default values
M0E: I didn't notice your email about lilo timeout working until after this
install. I'll be sure to play with the bootloader installation section on my next
test.
Cheers, newt
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X