Menu
▾
▴
vectorlinux-devel — Vector Linux developer's list
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
(40) |
Apr
(76) |
May
(31) |
Jun
(39) |
Jul
(44) |
Aug
(87) |
Sep
(32) |
Oct
(23) |
Nov
(36) |
Dec
(10) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(49) |
Sep
(14) |
Oct
|
Nov
|
Dec
(1) |
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(63) |
Aug
(95) |
Sep
(39) |
Oct
(61) |
Nov
(75) |
Dec
(118) |
| 2009 |
Jan
(25) |
Feb
(37) |
Mar
(20) |
Apr
(15) |
May
(14) |
Jun
(48) |
Jul
(82) |
Aug
(160) |
Sep
(94) |
Oct
(55) |
Nov
(59) |
Dec
(4) |
| 2010 |
Jan
(5) |
Feb
(17) |
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
(1) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
(1) |
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: Newt <gen...@gm...> - 2009-08-20 19:52:36
|
Hello, Testing 1.14 on older Dell Dimension 4100: Pentium III 1ghz, ATI Rage 128 video (16mb), 128mb ram After hitting 'enter' at the ascii art screen to start the framebuffer splash screen the display goes blank/black. I've let it sit for 20+ minutes and nothing changes. I know the machine is pretty low specs but thought I'd mention this. I have at least one more low spec machine to try this on. Cheers, newt |
|
From: Roy S. <nig...@ci...> - 2009-08-20 19:50:48
|
May have been a good thing we went down this road testing new kernel. Further testing indicates a bit must have got flipped between B3 and B4, because I have wicd problems in B4 that did not appear earlier. Starting over. |
|
From: uel a. <ue...@gm...> - 2009-08-20 16:41:20
|
New ISO's ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.14.iso ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.14-CD2.iso we need to test Intel and nv drivers for composting in kde on this one |
|
From: Newt <gen...@gm...> - 2009-08-20 04:36:44
|
Hello, Here are my notes with testing 1.13 install and KDE: >> Eject worked but I noticed this in console: >> eject error: unable to eject, last error: Input/output error >> >> did not require me to reboot this time after creating partitions - perhaps >> because hda was not overwriting ntfs this time??? Could not test fixed functionality >> >> no install to bootrecord option available for lilo, only mbrs (note: / is xfs I think) >> >> no windows/hfs+ found on sata drives by lilo installation >> >> strange instance can bypass root password creation: enter valid root passwords, >> click back, click next - 'next' (bypassing root password) is now avialable >> >> First boot: >> using nvidia proprietary driver >> kde menu working - i.e. not fully transparent with propri driver - good thing >> >> I notice that Openoffice has a grayish page color. I'm used to white. Is gray normal for ooo? >> >> Openoffice Writer extension manager: broken as mentioned, zombied processes if try to close >> >> Background color (behind wallpaper) could be something different than the >> blue - something to better match the wallpaper or more subdued (charcoal maybe) >> >> KDE panel does not extend across full width of screen - perhaps by design? >> >> KDE bug manager opens with error but then seems to work fine >> >> Opera not capitalized in Internet menu >> >> wpa_gui command cannot be found but is in the menu >> >> hdspconf and hdspmixer do nothing visual. Is this correct? >> >> vburn-iso does nothing. run from terminal I get: This script is intended >> to be called from filemanager via file association >> >> database access properties does nothing visual. Is this correct? >> >> printing does nothing visual, but I do not have a local or network >> printer connected/configured. >> >> xscreensaver issues a warning that it's not running on display 0:0 and >> if I should start it now. I choose OK and it seems to work fine. >> >> browser does not have an associated icon >> >> slapt-update-notifier does nothing visual. Is this correct? >> >> Manage Printing does nothing, but I have not printer configured. >> >> kpackage requires smart package manager to be installed That's all. Otherwise a very responsive release on this machine. Nothing that was a show stopper in my opinion; though the 'bypass root password creation' should be looked into. Cheers, newt |
|
From: uel a. <ue...@gm...> - 2009-08-20 01:15:07
|
installing all kernel and module packages reboot into the new kernel, run depmod -aq then reboot On Wed, Aug 19, 2009 at 6:44 PM, Roy Stefanussen <nig...@ci... > wrote: > More testing brainstorming: > > I upgraded kernel on a system with Light 6. > Rebooted, and no network. > Rebooted again, and now network was back to normal. > > Maybe I just didn't give it enough time and reboots? > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > |
|
From: Roy S. <nig...@ci...> - 2009-08-20 00:44:58
|
More testing brainstorming: I upgraded kernel on a system with Light 6. Rebooted, and no network. Rebooted again, and now network was back to normal. Maybe I just didn't give it enough time and reboots? |
|
From: Newtor <gen...@gm...> - 2009-08-19 17:46:33
|
Hello All, My definition of a live distro is two: 1) it's either the only release format for a distro and acts as the primary install medium, or 2) it's a supplemental release for a distro and acts as a way to "try out" the distro prior to installing from a more standard install-only medium. I think VL falls into the second category and, as such, should not be required to make sure the live environment is as up-to-date as the standard install medium (let alone, _more_ up-to-date). As an example of what I said above, if someone liked the live light but was having troubles getting it installed we would recommend them to download the primary non-live install iso to install the system, and then recommend that they upgrade the kernel after installation. I don't see why the live distro can't fall under the same criteria; install and upgrade the kernel. I tend to be in agreement with Roy regarding getting the Light Live iso out-the-door with the old (unpatched) kernel. Based on my test runs, and what I've gathered from others, it has run very smoothly for folks. A new kernel, regardless of how unimpacting it's supposed to be, always has some sort of impact and we'd have a hard time knowing what the impacts will be without extensive testing. Based on Roy's couple of test machines he's run across problems on both machines with the newer/patched kernel. To help support this, I just upgraded the kernel on my standard gold install on my laptop which was working great. After the upgrade my wireless no longer worked. All I needed to do was modprobe the module to get it working again, but how am I to know what else might not work as it was prior to the upgrade. I really can't until I actually come across the problem, and most likely it will be easy to fix, but perhaps not - and 'easy' to me may not be so easy to someone else. Common sense tells me that if all I'm doing is swapping a kernel for a same-version-kernel (same config) then everything should work as it was, but I would be wrong, and I think this might be where Roy's coming from. I certainly see the other side as well: We should provide an iso that's as up-to-date as possible, especially in regards to security concerns, if we have the ability. The problem basically comes down to manpower and testing. How long do we wait to release something? How up-to-date is sufficient? For instance, soho took a several day hit because it was upgraded from kde 4.2.x to 4.3.x. At some point we need to say that this will be what it is and move on; put the upgrade in the repo for testing but not worry about making them work on the release. VL6 is based on SW12.1. SW12.2 has been released for quite some time, and 13.0 is (I think) nearing it's final release. Overall, I'm just thinking that we should get the live distro out the door in it's unpatched_but_well_working form so that we can concentrate on finishing SOHO6. After all, SW13.0 will be here soon and we can start this whole rigamarole again in a few months :D. Not to mention the spread out spacing of releases to help our standing on the all_unimportant_but_important distrowatch rankings :D That's all. If this seemed like I was being critical or harsh, I wasn't. Just trying to help shed some light on my take on the release of Light Live. I'm okay either way, just prefer the sooner release than the later. Cheers, newt |
|
From: Roy S. <nig...@ci...> - 2009-08-19 16:12:44
|
On Tuesday 18 August 2009 14:15:37 Uel Archuletta wrote: > You need to upgrade the broadcom-wl and ndiswrapper packages > They are in the driver dir in the 6.0 repo Installed and tested new packages. No change. I can connect manually or using VLwifi. wicd sees nothing. Separate problem: The "e1000" module loads on machine that needs "sky2" for operation. Same thing on computer that uses "e100" module. This causes eth0 to be unavailable. eth1 can be brought up manually. If these issues are unique to the LiveCD, again I would suggest turning it loose using the old kernel. If not, they may affect other machines running Light or Standard, and should be pushed to the forefront for fixing. |
|
From: Roy S. <nig...@ci...> - 2009-08-19 03:06:37
|
On Tuesday 18 August 2009 21:54:15 uel archuletta wrote: > root:$ ls /var/log/packages/*2.6.27.12* > /var/log/packages/alsa-driver-1.0.19_2.6.27.12-i586-1vl60 > /var/log/packages/broadcom-wl-5.10.27.6_2.6.27.12-i586-1vl60 > > the alsa drivers are in the kernel-modules package so you dont need the > alsa-drivers package anymore > Ah, the learning continues, thanks for the patience. Guess this is good testing too, so consider this feedback. Next issue: Compaq iPaq Desktop P3-866, Intel 82801 all integrated machine. Before upgrade, it would load module e100, bring up eth0, and configure with dhcp on live boot. After upgrade, no network. I see both e100 and e1000 loaded. eth0 will not come up eth1 does come up and will connect. |
|
From: M0E L. <m0...@gm...> - 2009-08-19 03:03:25
|
I think you got an old installer. The new ISO's dont have networking enabled... I would suggest you keep a fresh copy of the installer in a separate partition where available and run it from there. |
|
From: uel a. <ue...@gm...> - 2009-08-19 02:16:02
|
here are the drivers ftp://vectorlinux.osuosl.org/pub/vectorlinux/veclinux-6.0/packages/drivers/broadcom-wl-5.10.27.6_2.6.27.29-i586-1vl60.tlz ftp://vectorlinux.osuosl.org/pub/vectorlinux/veclinux-6.0/packages/drivers/ndiswrapper-1.55_2.6.27.29-i586-1vl60.tlz On Tue, Aug 18, 2009 at 7:54 PM, uel archuletta <ue...@gm...> wrote: > root:$ ls /var/log/packages/*2.6.27.12* > /var/log/packages/alsa-driver-1.0.19_2.6.27.12-i586-1vl60 > /var/log/packages/broadcom-wl-5.10.27.6_2.6.27.12-i586-1vl60 > > the alsa drivers are in the kernel-modules package so you dont need the > alsa-drivers package anymore > > On Tue, Aug 18, 2009 at 7:26 PM, Roy Stefanussen < > nig...@ci...> wrote: > >> On Tuesday 18 August 2009 14:18:52 Uel Archuletta wrote: >> > Sorry for the afterthought, but you should search for the old kernel >> > version in /var/log/packages whenever you upgrade kernel >> > >> >> Not sure what you mean. After installing and verifying new kernel, >> I removed old by specifying full package name in /var/log/packages, >> as well as the old kernel-modules and kernel-source. >> >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >> 30-Day >> trial. Simplify your report design, integration and deployment - and focus >> on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> Vectorlinux-devel mailing list >> Vec...@li... >> https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel >> > > |
|
From: uel a. <ue...@gm...> - 2009-08-19 01:54:28
|
root:$ ls /var/log/packages/*2.6.27.12* /var/log/packages/alsa-driver-1.0.19_2.6.27.12-i586-1vl60 /var/log/packages/broadcom-wl-5.10.27.6_2.6.27.12-i586-1vl60 the alsa drivers are in the kernel-modules package so you dont need the alsa-drivers package anymore On Tue, Aug 18, 2009 at 7:26 PM, Roy Stefanussen <nig...@ci... > wrote: > On Tuesday 18 August 2009 14:18:52 Uel Archuletta wrote: > > Sorry for the afterthought, but you should search for the old kernel > > version in /var/log/packages whenever you upgrade kernel > > > > Not sure what you mean. After installing and verifying new kernel, > I removed old by specifying full package name in /var/log/packages, > as well as the old kernel-modules and kernel-source. > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > |
|
From: Roy S. <nig...@ci...> - 2009-08-19 01:26:57
|
On Tuesday 18 August 2009 14:18:52 Uel Archuletta wrote: > Sorry for the afterthought, but you should search for the old kernel > version in /var/log/packages whenever you upgrade kernel > Not sure what you mean. After installing and verifying new kernel, I removed old by specifying full package name in /var/log/packages, as well as the old kernel-modules and kernel-source. |
|
From: Paul M. <pa...@wa...> - 2009-08-18 22:16:33
|
uel archuletta wrote: > new iso's are up with updated installer > ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.12.iso > > ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.12-CD2.iso Downloaded and installed ( :) I do like xdelta...). Installer works pretty well. Still getting minor problems with screen resolution (same places as before - extra software shows 'ye', the 's' scrolls off to the right hand side of the screen). The installer is sluggish in a couple of places - entering passwords and user details, plus at that stage, it is slow coming up with the text in message boxes - the box appears, pause, then the text appears. I'm still not getting the first CD ejecting when the system wants the second CD - have to click ok, manually eject the CD (which can't be done until I've clicked ok), then click ok again once the second CD is in the drive. In addition, when the system reboots at the end of the install, the second CD is not ejected. I _think_ it was with a1.11. Once installed, I'm still seeing exactly the same problem with OpenOffice - as soon as I attempt to use the extension manager, ooo locks up. I seem to be able to close the extension box, but it doesn't really close. If I attempt to exit multiple times, I get multiple zombie entries for kdefilepicker in the process list. I also hit the same video problem. First time the system booted (just after install), the desktop came up fine. Second time, I got a blank white screen, then a blank grey screen with only a mouse pointer. Used CTL-ALT-BackSpace to kill X and logged back in using the safe kde option from the KDM session selector. That worked, and I was then able to log in using the normal KDE option. Don't know if this is related to Intel video drivers, but this time, I didn't even attempt to enable the desktop effects. More later.... paul. |
|
From: M0E L. <m0...@gm...> - 2009-08-18 21:27:40
|
Also, I just commited a change that implements the same countdown from the end of the installer over to the restart needed right after partitioning. That should take care of it. Let me know if it does not |
|
From: M0E L. <m0...@gm...> - 2009-08-18 20:59:12
|
I think I finally got the cd eject code to work. try that out guys please. I might need help with that lilo/grub thing... I'll get on that tomorrow. |
|
From: Newtor <gen...@gm...> - 2009-08-18 20:39:01
|
Hello all, Here's my first installation test on physical hardware and notes: >> System: Intel Pentium D 2.8ghz (820), 3gb ram, dell deimension 9150, nvidia >> gf7300le, Acer X213w 2.16/22" monitor, multiboot system (4 hard drives: 3 >> sata, 1 ide), installed to ide, bios boot order is sata then ide >> >> Restart Now not working: dualboot system with windows partitions, after >> partition creation, recommends rebooting. Click 'restart now' button and get >> message that system will reboot in 10 seconds with an OK button, wait 10 >> nothing happens. Click 'OK' button on restart message and wait 10 more >> seconds, nothing happens. Click 'restart now' button again and then 'ok' >> button, wait 10 seconds nothing happens. I end up having to manually reboot. >> >> Bootloader: bootloader section did not identify windows or hfs+ partitions >> >> Bootloader: lilo installation does not work for bootsector option. It lists >> 'bootsector for' but does not actually list a partition number (i.e. it only >> says 'bootsector for' - that's it). I try it and get a message that lilo >> failed to install, but installer still moves me forward in process. I think >> it should not move me forward without warning me about the risks of moving >> forward with an incomplete lilo installation. I click 'back' and the lilo >> installation screen is stuck with the blue progress bar showing, and the >> partition listings below (lower half) are all grayed out and cannot be modified. >> >> Major: kde menu is fully transparent and I cannot see anything but outline >> around where the menu should be. However, it still responds. I luckily was >> able to click the shutdown option but the transparency is the same with the >> shutdown window - outline only nothing inside the outline. >> >> Major: kde taskbar does not extend fully across bottom on 1400x900. Stops about 2/3 way. >> >> Minor: finding installation cd dropdown box looks cut off at bottom by a couple pixels >> >> Minor: root password entry information box looks cut off at bottom by a couple pixels >> >> Minor: 1680x1050 resolution is not present as option (Acer 21.6/22" monitor) >> >> Minor: wallpaper too small for 1400x900 option. Also, background behind >> wallpaper is like a windows classic/xp blue - perhaps a color that compliments the wallpaper would be better. >> Hope this helps. Cheers, newt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Monday, August 17, 2009, 5:20:48 PM, you wrote: ua> new iso's are up with updated installer ua> ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.12.iso ua> ftp://vectorlinux.osuosl.org/pub/vectorlinux/Uelsk8s/test/VL6.0-SOHO-A1.12-CD2.iso |
|
From: Uel A. <ue...@gm...> - 2009-08-18 18:19:59
|
Sorry for the afterthought, but you should search for the old kernel version in /var/log/packages whenever you upgrade kernel On Aug 18, 2009, at 1:08 PM, Roy Stefanussen <nig...@ci...> wrote: > On Tuesday 18 August 2009 12:21:02 John B wrote: >> Roy, >> >> Depending on which version of the bcm43 chip your wireless rig has, >> you may >> need to modprobe either b43 or b43legacy to see which one works for >> you. I >> have a bcm43 in an old Belkin PCI wireless adapter and have found >> that the >> b43 module works for me. >> > > I'm sure you're right, John. > > My concern is not really this specific issue, rather the fact that > 30 minutes > worth of testing after upgrading kernel revealed two significant > changes in > the behavior of the system. > > I had spent a lot of time testing the prior version, on several > different > machines. I had clicked through and verified operation of every item > on the > menu, and felt that it was good to go. The kernel change sets the > process > back several steps, probably weeks worth of time. > > I can see using Light Live as a test bed for the new kernel, but if > so it > needs to be presented as such, in alpha form. > > Roy > > --- > --- > --- > --------------------------------------------------------------------- > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and > focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel |
|
From: Uel A. <ue...@gm...> - 2009-08-18 18:16:47
|
You need to upgrade the broadcom-wl and ndiswrapper packages They are in the driver dir in the 6.0 repo I'll get you a link later today if you don't find it first On Aug 18, 2009, at 1:08 PM, Roy Stefanussen <nig...@ci...> wrote: > On Tuesday 18 August 2009 12:21:02 John B wrote: >> Roy, >> >> Depending on which version of the bcm43 chip your wireless rig has, >> you may >> need to modprobe either b43 or b43legacy to see which one works for >> you. I >> have a bcm43 in an old Belkin PCI wireless adapter and have found >> that the >> b43 module works for me. >> > > I'm sure you're right, John. > > My concern is not really this specific issue, rather the fact that > 30 minutes > worth of testing after upgrading kernel revealed two significant > changes in > the behavior of the system. > > I had spent a lot of time testing the prior version, on several > different > machines. I had clicked through and verified operation of every item > on the > menu, and felt that it was good to go. The kernel change sets the > process > back several steps, probably weeks worth of time. > > I can see using Light Live as a test bed for the new kernel, but if > so it > needs to be presented as such, in alpha form. > > Roy > > --- > --- > --- > --------------------------------------------------------------------- > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and > focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel |
|
From: Roy S. <nig...@ci...> - 2009-08-18 17:08:42
|
On Tuesday 18 August 2009 12:21:02 John B wrote: > Roy, > > Depending on which version of the bcm43 chip your wireless rig has, you may > need to modprobe either b43 or b43legacy to see which one works for you. I > have a bcm43 in an old Belkin PCI wireless adapter and have found that the > b43 module works for me. > I'm sure you're right, John. My concern is not really this specific issue, rather the fact that 30 minutes worth of testing after upgrading kernel revealed two significant changes in the behavior of the system. I had spent a lot of time testing the prior version, on several different machines. I had clicked through and verified operation of every item on the menu, and felt that it was good to go. The kernel change sets the process back several steps, probably weeks worth of time. I can see using Light Live as a test bed for the new kernel, but if so it needs to be presented as such, in alpha form. Roy |
|
From: M0E L. <m0...@gm...> - 2009-08-18 17:07:14
|
Go for it. I'm trying to finish up some extra packages for KDE that did not build in the batch build myself. FWIW, I find go-oo to be better than the upstream release ;) |
|
From: John B <joh...@gm...> - 2009-08-18 16:28:56
|
There was some traffic about a package of OpenOffice that was built from source using the go-oo building method. I think that the reason it's not working with the KDE 4 SOHO is that unlike "traditional" builds of OpenOffice, the go-oo method uses KDE 4's file picker, etc, as some patches were made to test for the presence of KDE 4. When I built the package that is in the testing repo, it was build against VL 6.0 standard, which doesn't have KDE 4. Thus, --disable-kde4 was passed to the configure script for the bulid. If we want to use OpenOffice built from source in SOHO 6.0, it will need to be built against the kdelibs from KDE 4 so that files can be opened, etc. I'm willing to embark on this tonight when I get home from work. Thoughts anybody? John |
|
From: John B <joh...@gm...> - 2009-08-18 16:21:09
|
Roy, Depending on which version of the bcm43 chip your wireless rig has, you may need to modprobe either b43 or b43legacy to see which one works for you. I have a bcm43 in an old Belkin PCI wireless adapter and have found that the b43 module works for me. HTH, John On Tue, Aug 18, 2009 at 12:18 PM, Roy Stefanussen < nig...@ci...> wrote: > On Monday 17 August 2009 23:49:44 Robert Lange wrote: > > I think you should update to the patched kernel no difference except > > vunerability patch so there will be no problems. > > > > I made a version with the 2.6.27.29 kernel. > Found some problems already, which did not exist using old kernel: > - On my laptop, with a Linksys wireless card (bcm43), wicd-client does not > see any wireless networks. VLwifi connects without problems. > - On an Intel 82801 integrated machine, the NIC is not working. > > Maybe I did something wrong in the kernel upgrade. I'll keep hacking away, > but would appreciate some input. The ISO is in my contrib. > > Roy > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Vectorlinux-devel mailing list > Vec...@li... > https://lists.sourceforge.net/lists/listinfo/vectorlinux-devel > |
|
From: Roy S. <nig...@ci...> - 2009-08-18 16:18:54
|
On Monday 17 August 2009 23:49:44 Robert Lange wrote: > I think you should update to the patched kernel no difference except > vunerability patch so there will be no problems. > I made a version with the 2.6.27.29 kernel. Found some problems already, which did not exist using old kernel: - On my laptop, with a Linksys wireless card (bcm43), wicd-client does not see any wireless networks. VLwifi connects without problems. - On an Intel 82801 integrated machine, the NIC is not working. Maybe I did something wrong in the kernel upgrade. I'll keep hacking away, but would appreciate some input. The ISO is in my contrib. Roy |
|
From: Vanger <fa...@gm...> - 2009-08-18 11:26:38
|
>> We have a problem in the works here >> guys. >> I discovered this while trying to get some eye-candy out of >> KDE. I >> noticed it would not enable some stuff like transparency, >> etc. >> >> so I did glxinfo | grep render and it gave me this: Failed >> to >> initialize TTM buffer manager. Falling back to >> classic. >> >> If you google that, you'll find a lot of hits suggesting >> it's due to >> missing GEM support from the kernel. >> http://kernelnewbies.org/Linux_2_6_28#head-b957b19f6139b6bbbfabaf790bf643b1746985d6 >> >> I dont know what would be easier, downgrade to an older >> xorg|intel >> driver or enabling support fo this in the kernel, which >> also requires >> a newer kernel. >> >> GEM support is still in development from what I see. >> Just thought I'd throw this out there. I can see this being >> a problem >> flooding the forums with "OMG I can't run compiz on this" >> threads. My two cents - I've been researching this problem half a year ago. I wanted EVE-Online run on my desktop at work, which had intel X3100 (VL 5.9). I've tried intel drivers from 2.1.0 to 2.5.1 (2.6 and higher require xorg-server 1.4) with no luck in getting 3D effects work. As we stick to Xorg 1.4.2 that has xorg-server 1.3, I advice not to spend much time on this. I still have some knowledge of building libdrm, x11proto and xorg-server itself, but, honestly, I solved it by buying GF9400GT. I'd also suggest asking folks from SuSE or Fedora - they have it just working. -- ++luck |
14 messages has been excluded from this view by a project administrator.
