Menu
▾
▴
vectorlinux-devel
|
From: M0E L. <m0...@gm...> - 2009-09-21 20:39:16
|
New iso is up there. Please test the following features. ext4 support has been added to the installer and to the initrd/kernel as well as installed system. Please test and report your results with both bootloader choices on this. I have had success with both, LILO and GRUB. |
|
From: Robert L. <vec...@ya...> - 2009-09-22 08:03:17
|
results on A1.33 The problems I encountered with installer using previous versions are gone all was stable and worked well. I tried both ext3 and ext4 installs both went as planned no problems. There is a new bug which is critical new udev update has left the kde4 device notifier silent so no automount of usb device, cdroms etc. That needs to be figured out..........crucial!! My feeling is the installer is stable enough to release to public need to fix a few package kde bugs tho. looking good thnx again M0E you are my hero.............:) cheers, R Robert Lange vec...@ya... http://www.vectorlinux.com --- On Mon, 9/21/09, M0E Lnx <m0...@gm...> wrote: > From: M0E Lnx <m0...@gm...> > Subject: [Vectorlinux-devel] VL6.0-SOHO-A1.33 > To: "Vector Linux developer's list" <vec...@li...> > Received: Monday, September 21, 2009, 4:39 PM > New iso is up there. Please test the > following features. > > ext4 support has been added to the installer and to the > initrd/kernel > as well as installed system. > > Please test and report your results with both bootloader > choices on this. > I have had success with both, LILO and GRUB. > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer > Conference in SF, CA > is the only developer event you need to attend this year. > Jumpstart your > developing skills, take BlackBerry mobile applications to > market and stay > ahead of the curve. Join us from November 9-12, 2009. > Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > __________________________________________________________________ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/ |
|
From: Uel A. <ue...@gm...> - 2009-09-22 11:00:17
|
I think the GUI installer is looking great, but there are still problems with the bootloader that I think need to be fixed before a public release. Grub is unusable on most of my hardware because of the GPT partition table it throws an error and refuses to install. On another box with ati chipset it says it installs correctly but on reboot gives an out of bounds error that is supposed to be fixed in a later svn version. On a different box that requires 800x600 to boot I get a black screen because VGA=791 is hardcoded into the config. LILO gives me error default image does not exist Are we really thinking of going public without a CLI installer? On Sep 22, 2009, at 3:03 AM, Robert Lange <vec...@ya...> wrote: > results on A1.33 > The problems I encountered with installer using previous versions > are gone all was stable and worked well. > I tried both ext3 and ext4 installs both went as planned no problems. > There is a new bug which is critical new udev update has left the > kde4 device notifier silent so no automount of usb device, cdroms etc. > That needs to be figured out..........crucial!! > My feeling is the installer is stable enough to release to public > need to fix a few package kde bugs tho. > looking good thnx again M0E you are my hero.............:) > > cheers, > R > > Robert Lange > vec...@ya... > http://www.vectorlinux.com > > > --- On Mon, 9/21/09, M0E Lnx <m0...@gm...> wrote: > >> From: M0E Lnx <m0...@gm...> >> Subject: [Vectorlinux-devel] VL6.0-SOHO-A1.33 >> To: "Vector Linux developer's list" <vec...@li... >> > >> Received: Monday, September 21, 2009, 4:39 PM >> New iso is up there. Please test the >> following features. >> >> ext4 support has been added to the installer and to the >> initrd/kernel >> as well as installed system. >> >> Please test and report your results with both bootloader >> choices on this. >> I have had success with both, LILO and GRUB. >> >> --- >> --- >> --- >> --------------------------------------------------------------------- >> Come build with us! The BlackBerry® Developer >> Conference in SF, CA >> is the only developer event you need to attend this year. >> Jumpstart your >> developing skills, take BlackBerry mobile applications to >> market and stay >> ahead of the curve. Join us from November 9-12, 2009. >> Register now! >> http://p.sf.net/sfu/devconf >> _______________________________________________ >> Vectorlinux-devel mailing list >> Vec...@li... >> https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel >> > > > > __________________________________________________________________ > Looking for the perfect gift? Give the gift of Flickr! > > http://www.flickr.com/gift/ > > --- > --- > --- > --------------------------------------------------------------------- > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart > your > developing skills, take BlackBerry mobile applications to market and > stay > ahead of the curve. Join us from November 9-12, 2009. Register > now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel |
|
From: M0E L. <m0...@gm...> - 2009-09-22 12:59:10
|
from what I understand, grub should not use "vga=" flags. We should be using the "set gfxpayload" argument instead. For whatever reason, our configuration does not produce a bootsplash with that only, so in that case, you would have to use lilo. I'm still working on lilo and it's problems, however, keep in mind, that this is an area where most distros's installers fail anyway. Our goal is to present the user with the OS's located in the system. Most installers I have seen dont even do this, so we'll get it there, and my goal is to make it work, it'll just take a little longer to debug it. |
|
From: uel a. <ue...@gm...> - 2009-09-22 14:18:42
|
Maybe our grub prolems would go away with a new grub binary from a later svn? I know we will get there, I have seen a lot of progress so far, i'm just pointing out the last deficiencies that i have ran into. On Tue, Sep 22, 2009 at 6:58 AM, M0E Lnx <m0...@gm...> wrote: > from what I understand, grub should not use "vga=" flags. We should be > using the "set gfxpayload" argument instead. > For whatever reason, our configuration does not produce a bootsplash > with that only, so in that case, you would have to use lilo. > > I'm still working on lilo and it's problems, however, keep in mind, > that this is an area where most distros's installers fail anyway. > Our goal is to present the user with the OS's located in the system. > Most installers I have seen dont even do this, so we'll get it there, > and my goal is to make it work, it'll just take a little longer to > debug it. > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > |
|
From: Newt <gen...@gm...> - 2009-09-22 15:46:06
|
Hello, I have particular machine (graphics card) that does not play with vesa driver and last I tried I could not see anything once X started. Anyone with a similar card would be dead-in-the-water if there is not an alternative installer (CLI). I'm sure it's already planned but if not then I would definitely vote for an alternative installer - or a way to swap video drivers prior to X starting. Cheers, newt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Tuesday, September 22, 2009, 4:59:51 AM, Uel wrote: UA> Are we really thinking of going public without a CLI installer? |
|
From: M0E L. <m0...@gm...> - 2009-09-22 15:58:27
|
I have new code in the LILO department. Please try this setup if and report back. Especially if you have multiple OS's installed... I want to see how this plays along. Thanks |
|
From: Uel A. <ue...@gm...> - 2009-09-22 16:39:12
|
Newt, The CLI installer is being work on now. This is just a timing question more than anything. Can you post the specs on that machine. On Sep 22, 2009, at 9:45 AM, Newt <gen...@gm...> wrote: > Hello, > > I have particular machine (graphics card) that does not play with > vesa driver and > last I tried I could not see anything once X started. Anyone with a > similar card > would be dead-in-the-water if there is not an alternative installer > (CLI). I'm > sure it's already planned but if not then I would definitely vote > for an > alternative installer - or a way to swap video drivers prior to X > starting. > > Cheers, newt > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > Tuesday, September 22, 2009, 4:59:51 AM, Uel wrote: > > UA> Are we really thinking of going public without a CLI installer? > > > > > --- > --- > --- > --------------------------------------------------------------------- > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart > your > developing skills, take BlackBerry mobile applications to market and > stay > ahead of the curve. Join us from November 9-12, 2009. Register > now! > http://p.sf.net/sfu/devconf > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel |
|
From: Newt <gen...@gm...> - 2009-09-22 18:06:11
Attachments:
specs.txt
|
Hello Uel, That's great news about the CLI installer - it's a wonderful safeguard in case the GUI installer doesn't work for someone (albeit, not nearly as pretty but plenty functional :D). Attached is a text document with the specs from the problematic system. Hopefully you can find the meaningful information in all of that output. I went a little overboard but figured it's probably better to have too much than not enough. Cheers, newt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Tuesday, September 22, 2009, 10:38:38 AM, Uel wrote: UA> Newt, UA> The CLI installer is being work on now. UA> This is just a timing question more than anything. UA> Can you post the specs on that machine. |
|
From: M0E L. <m0...@gm...> - 2009-09-22 18:12:30
|
@ Newt Try booting the CD or ISO into text mode by parsing these arguments at boot time "gui 2" Without quotes. Log in as root, and look in /etc/X11/xorg.conf to see which driver is being used for X I wonder if we have the "nv" driver built into the initrd... you might try that. |
|
From: Newt <gen...@gm...> - 2009-09-22 20:37:34
|
Hello M0E and all, 'gui 2' gets me access to the shell prior to X starting which is what I've wanted to do - thanks M0E. It doesn't seem like the 'nv' driver is built into the initrd (X would not start), but 'fbdev' is and it works for this card. I will clean up some space on one of this systems hard drives and probably attempt the install later tonight. Thanks again for the 'gui 2' option. Just thinking out loud here: I'm certain someone else will run into a similar problem. I wonder, is there some kind of easy solution that would allow a user to start X using different drivers, if needed, without having to manually edit files and start X. I'm thinking of some kind of basic script that could be run which would start X using a different graphics driver (e.g. ./gui-fbdev.sh, ./gui-vesa.sh, ./gui-nv.sh), and those scripts would execute the 'Xorg' binary using a predefined xorg.conf file (e.g. xorg.conf-fbdev, xorg.conf-vesa, or xorg.conf-nv, respectively). The scripts could be held in /root such that if a user needed to use them they could 'gui 2', login as 'root', and run the script directly - and away they go with the installer. Cheers, newt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Tuesday, September 22, 2009, 12:12:20 PM, you wrote: ML> @ Newt ML> Try booting the CD or ISO into text mode by parsing these arguments at boot time ML> "gui 2" ML> Without quotes. ML> Log in as root, and look in /etc/X11/xorg.conf to see which driver is ML> being used for X ML> I wonder if we have the "nv" driver built into the initrd... you might try that. |
|
From: Newt <gen...@gm...> - 2009-09-24 18:05:28
|
Hello All, Just some notes from a vmware install: 1.35, r844: -only 3 language packs installed (es/fr/de), not the 4th -lilo timeout still not working -read-only option missing from -cli (safe mode) option again (it had been working before) -disabled 'next' button issue persists on bootloader (on failed install or by going 'back') KDM LOGIN: -vector 'V' bobbles on login - is this intentional? KDE: -vburn menu option still not working -still missing some menu icons (opera, wpa_gui, vburn, browser, etc) VASMCC: -cups fails to start from vasmcc -samba swat fails to start from vasmcc -bootloader option seems to be missing grub -format option missing some filesystems (jfs, ext4, etc) -cfdisk improperly identifies ext4 partitions as ext3 -bootsplash themes seem out-dated -vpackager does nothing -vcpufreq does nothing -hardinfo does nothing -gslapt does nothing -in general, vasmcc looks to need some updating for VL6 SOHO Cheers, newt |
|
From: M0E L. <m0...@gm...> - 2009-09-24 19:35:09
|
Could you tell me what type of install you did? I just did a custom install and selected each language pack individually and it did install all of them. I'm curious to find out why yours failed. |
|
From: Newt <gen...@gm...> - 2009-09-24 20:00:31
|
Hello M0E, I just booted up KDE and double-checked in the Language/Region section, and Russian is the language that is missing. I noticed it was not installed because I was watching the gambas console during this install step and noticed only three packs were installed. I did a custom install with all packages selected on every screen. I always play with the select_all/unselect_all buttons during each package selection screen along with individually clicking the selections, but in the end I make sure all packages are selected. I wish I had an explanation of why it was not installed. Best I can do it redo the install with same basic scenario: 1.35, r844. I'm using 1.34-cd2 if that makes any difference. Cheers, newt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Thursday, September 24, 2009, 1:34:57 PM, you wrote: ML> Could you tell me what type of install you did? ML> I just did a custom install and selected each language pack ML> individually and it did install all of them. ML> I'm curious to find out why yours failed. |
|
From: M0E L. <m0...@gm...> - 2009-09-24 20:02:24
|
Can you check if clicking on the language packs manually and individually makes a difference? I will try the massive selection toggle buttons. |
|
From: Newt <gen...@gm...> - 2009-09-25 03:34:07
|
Hello M0E, Okay, I gave both methods a shot and they both worked out fine this time. I can't explain why the russian language pack was not installed earlier, but everything went as expected my last 2 tests. I guess unless anyone else runs across that kind of an issue we can just ignore my previous findings - everything seems to be installing correctly now. Cheers, newt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Thursday, September 24, 2009, 2:02:10 PM, you wrote: ML> Can you check if clicking on the language packs manually and ML> individually makes a difference? ML> I will try the massive selection toggle buttons. |
×
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