search for: balducci

...ion `get_size': extlinux.c:285: error: `BLKGETSIZE64' undeclared (first use in this function) extlinux.c:285: error: (Each undeclared identifier is reported only once extlinux.c:285: error: for each function it appears in.) make[2]: *** [extlinux.o] Error 1 make[2]: Leaving directory `/home/balducci/tmp/install-us-d/syslinux/syslinux-3.01/extlinux' ... As a matter of fact, I can't grep any BLKGETSIZE64 declaration under my /usr/include directory tree. I guess this is due to the fact that my installed kernel headers are quite old (redhat-7.1, kernel 2.4.2). However, I keep my kernel...

...Bug ID: 58776 Assignee: nouveau at lists.freedesktop.org Summary: DRM NOUVEAU: cannot boot with kernel >=3.7 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: balducci at units.it Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: Driver/nouveau Product: xorg Created attachment 72129 --> https://bugs.freedesktop.org/attachment.cgi?id=72129&action=edit lspci output hello everybody,...

...eedesktop.org Summary: (bisected) kernel>=3.7 breaks nouveau with acceleration for GeForce 6150SE nForce 430 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: balducci at units.it Hardware: x86-64 (AMD64) Status: NEW Version: unspecified Component: Driver/nouveau Product: xorg Hello, I am experiencing X11 problems with kernel>=3.7 (including latest 3.8 release) with the following GPU: NVIDIA Corporatio...

...some problems all (seemingly) related to inaccurate paths in various Makefiles. I enclose a complete patch at the end of this email, which details the problems I found and how they got fixed for me. As an example, this is the first error I got: ---8<--- make[3]: Entering directory '/home/balducci/tmp/install-us-d/syslinux-6.03.d/syslinux-6.04-pre1/libinstaller' make[3]: *** No rule to make target '/home/balducci/tmp/install-us-d/syslinux-6.03.d/syslinux-6.04-pre1/libinstaller/../core/ldlinux.bss', needed by 'bootsect_bin.c'. Stop. make[3]: Leaving directory '/home/b...

...clude= broken for version>=3.0.0pre5? Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: balducci@units.it QAContact: rsync-qa@samba.org Hello, I'm probably missing something (apologies if so), but this has worked for me for years, and starting from 3.0.0pre5 has stopped working in a way that smells of some kind of bug. To reproduce the (possible) bug, set up the following scen...

...rovements, I'm glad to see and publicize a pre-release, 6.04-pre1 in https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.04/ Personally, I've already been working testing the pre-release as-is and my tests have been positive so far. I appreciate feedback like that from Gabriele Balducci and testing "make bios installer". Yes, there are a few patches I'd like to review for inclusion or feedback before a full release. At the moment, I've been reviewing/testing Pete Betard's patch set minus the minfatsize patch. Looking over my list of pending patches, here...

...clude= broken for version>=3.0.0pre5? Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: balducci@units.it QAContact: rsync-qa@samba.org Hello, I'm probably missing something (apologies if so), but this has worked for me for years, and starting from 3.0.0pre5 has stopped working in a way that smells of some kind of bug. To reproduce the (possible) bug, set up the following scen...

...and publicize a > pre-release, 6.04-pre1 in > https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.04/ > > Personally, I've already been working testing the pre-release as-is > and my tests have been positive so far. I appreciate feedback like > that from Gabriele Balducci and testing "make bios installer". > > Yes, there are a few patches I'd like to review for inclusion or > feedback before a full release. At the moment, I've been > reviewing/testing Pete Betard's patch set minus the minfatsize patch. > > Looking over my l...

...ome low-resources systems, the difference between building: _ only the installers or; _ all binaries under BIOS, can be relevant. I want to remind you about a proposed patch (that was later recanted) related to this target: http://www.syslinux.org/archives/2016-March/024907.html Although Mr. Balducci recanted his proposed patch, there might still be problems with the "(bios) installer" target(s), considering that I am not using any kind of script other than the Syslinux code / make files (which apparently was the reported reason for retracting back the proposed patch) and it is fa...

On Mon, Dec 24, 2012 at 09:26:17PM +0100, balducci at units.it wrote: > hello everybody, > > apologies if I am missing any blatant point; my knowledge about > KMS/DRM etc. is very poor, so I am asking for help here (hoping to be > at the right place) > > Starting with kernel-3.7 I am not able to boot any more in KMS: as >...

...and publicize a > pre-release, 6.04-pre1 in > https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.04/ > > Personally, I've already been working testing the pre-release as-is > and my tests have been positive so far. I appreciate feedback like > that from Gabriele Balducci and testing "make bios installer". > > Yes, there are a few patches I'd like to review for inclusion or > feedback before a full release. At the moment, I've been > reviewing/testing Pete Betard's patch set minus the minfatsize patch. > > Looking over my l...

Okay, I'm going to ask the gajillion-dollar question... I've been doing syslinux for 11 years now. From a very limited scope it has since grown and is now a very advanced boot loader. Unfortunately, it's not clear to me anymore to what extent the work I'm doing is useful. I personally dislike grub because of its monolithic design, and because the grub people have

hello > apologies if I'm missing something here I must really apologise for the noise I eventually found the origin of the problems mentioned in my previous post, and the culprit wasn't syslinux! I use a script to build and install syslinux and in this script I was exporting a FIRMWARE variable like this: export FIRMWARE="bios" A variable called FIRMWARE is also