On Wed, Dec 04, 2019 at 06:27:02PM -, InF3rN0 wrote:
> Hi, I could not imagine an OS installation could corrupt the BIOS
> (whether be Samsung's fault or Linux's).
> The problem happened to me with a NP300E4X-A04CO; don't know BIOS
> version. Ubuntu 18.04 (LTS).
You are responding to an old,
You seem to have responded to an old, closed bug that's unrelated to
your problem. You're much more likely to find help if you bring this
up on the forums or (if you can debug this further than "it doesn't
work") file a new bug report about your audio ordeals.
On 6 August 2015 at 15:28, BartaSzili
No. Despite not directly causing the bricking, the samsung-laptop driver
will only work in CMS mode and will cause random and potentially very bad
problems when running under UEFI. The driver support issue is separate from
this bug.
On 23 May 2014 22:59, Val <1040...@bugs.launchpad.net> wrote:
>
Hi,
I did the up date to the firmware in windows and have not up graded from 12.04.
Is there way from the Linux side, with bash, to see if the firmware, and all
others parts, are set
up right for doing the install, of 14.04?
Bbest regards,
keghn
--
You received this bug notification b
Blacklisting the samsung-laptop module in UEFI mode fixes the related but
separate issue of the kernel crashing on bootup. The root cause of the
bricking was that Samsung's firmware had an undocumented requirement of 5KB
of free UEFI variable space to be able to start up. The kernel crash would
cau
Hey Adrian,
Let me just quote what I wrote above 11 months ago:
"First of all, I have installed SAMSUNG BIOS upgrades from within Windows 8,
then reduced Windows partition to leave around 40–50 Gb of free space, the
remaining free space on a HDD was allocated for Ubuntu's "/home" directory.
Next
Andrea, it should work just fine. Which basically means: there were no new
reports of machines getting bricked that I know of since many months. For
example, I've been using np530U3C-A05 in UEFI mode just fine since June.
2014-05-09 11:24 GMT+02:00 Andrea Biolo :
> Hi! I have the ultrabook Samsu
Hello,
What model is you laptop?
Did you up date the bios in Windows?
Is the computer still under warranty?
I have 12.04 working on my laptop right now.
I believe 12.04.1 to 12.10* are bricks for My Samsung
notebook.
Wish you better luck,
keghn
.
--
You received this bug notification
And do not forget to get the latest Samsung BIOS updates from within
Windows first! This is of utmost importance.
2013/9/11 calant <1040...@bugs.launchpad.net>
> So I figure the safest thing to do is to wait for Ubuntu 13.10 release?
> Since this uses linux kernel 3.11 which contains the anti br
Calant, let me put it this way. There were no confirmations either from
SAMSUNG or from Ubuntu/kernel devs that the fixes released necessarily
solve those issues (no info from SAMSUNG at all). However, as you can see,
there are almost no new reports that people are still facing the issue.
If you a
I had to use boot repair on insulation of 11.04, 11.10,and 12.04 to make Ubuntu
visible on
My grub table. 11.04 and 11.10 I had on my Sony viao. Then I moved up to a
Samsung NP700Z5C
laptop.
Put 12.04 on that. When 12.10 came out I bricked my rig trying it out, on A
live usb thumb drive.
Ubun
I have been running Ubuntu 13.04 on SAMSUNG NP530U3C-A05EE for a good week
and a half. So far so good. Please note, that I am running a mainline 3.10
kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/ which among
other things contains Matthew Garrett's UEFI anti-bricking patches.
First of
On Tue, Jun 25, 2013 at 5:58 AM, stblack <1040...@bugs.launchpad.net> wrote:
> I'd like to have your suggestions about a possible temporary solution, at
> least for me, to this bug.
> I have a NP770Z5E and I wouldn't like to brick it.
> What about to install linux and place the /boot partition on
Just noting you don't have to use the i386 image on the 64bit i5 CPU,
unless you want to install the 32bit version of Ubuntu. Amd64 images is
what you should be using if you want to run a 64bit OS; it has nothing to
do with the AMD vs. Intel distinction.
By the way, I have also ordered a 530U3C-A0
I know where to get the packages, but thank you anyway. :)
My question was rather how to build an image with those packages or where
it would be possible to get one. So that people would be able to install
Ubuntu from such images containing a (hopefully) safe kernel, i.e. to boot
it right away ins
There's a mistake in the link above, it has caught an I as a part of the
link. The actual link is the following:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f8b8404337de4e2466e2e1139ea68b1f8295974f
2013/6/16 Žygimantas Beručka
> The aforementioned modified UEFI an
The aforementioned modified UEFI anti-bricking code has been released in
Linux 3.10-rc6, see:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f8b8404337de4e2466e2e1139ea68b1f8295974fI
hope it really works. :)
Hopefully, this kernel will be included in Saucy images/daily
Did you try to update Samsung provided BIOS from within Windows first?
Rumour has it that Samsung released an updated BIOS that has this issue
ironed out. (And yes, there indeed have been two or three BIOS updates from
Samsung on my sister's presumably affected laptop since I am following this
thr
On Mon, May 20, 2013 at 09:54:19PM -, Richard Fannin wrote:
> *According to
> https://help.ubuntu.com/community/UEFI#Creating_an_EFI_partition and
> some various askubuntu.com pages, you should select "manual
> installation" (whichever options lets you choose what gets installed
> where);
How do you know if it _really_ contains the fix for this particular
issue?
2013/5/3 SiM
> HI ALLL; I HAVE THE ULTIMATE SOLUTION BIOS UPDATE phoenix
> technologies motherfuking drivers
>
> http://support-
>
> us.samsung.com/cyber/popup/iframe/pop_troubleshooting_fr.jsp?idx=414320&modelname=N
On 21 March 2013 11:45, Arthur P. Meiners
wrote:
> Samsung have published a BIOS update, version 1.0.0.3, which should
> correct the underlying problem.
>
> So possibly the Linux installation procedure could now be amended to:
>
> a) check whether the computer has a samsung bios lower 1.0.0.3
>
On Tue, Feb 26, 2013 at 05:51:40PM -, hanishkvc wrote:
> I have a query related to the FIx. Shouldn't the right fix for this bug
> if one wants to use secure boot and uefi to boot their system be the
> noefi boot param related fix added to linux kernels around 15th Feb i.e
Using a 'noefi' boot
On Mon, Feb 25, 2013 at 6:16 AM, Ivo Roghair <1040...@bugs.launchpad.net> wrote:
> I found out about this bugreport _after_ installing Ubuntu 12.10 64-bit
> on my Samsung Ultrabook Series 5 530U3C-A09NL.
>
> I installed Ubuntu via usb (created via unetbootin on another 12.10
> machine), with secure
On Fri, Feb 22, 2013 at 03:58:49PM -, Andreas wrote:
> Same problem here. I haven't a Samsung notebook but a Lenovo Twist and
> used Ubuntu 12.04.2 and 12.10 in UEFI-Mode.
Then that's not the same problem. This bug report is about a bug in the
Samsung firmware that's triggered by the Linux k
On Wed, Feb 06, 2013 at 09:23:55PM -, Fabri Velas wrote:
> @Steve Langasek: is the samsung-laptop module fixed or did you mean that
> the kernels are not using it as of Colin's fix?
It is "fixed" in that it no longer triggers this problem. That doesn't mean
the samsung-laptop module will be
On Sun, Jan 20, 2013 at 06:37:45AM -, Arthur P. Meiners wrote:
> 1) This seems to be a BIOS bug in a small number of Samsung notebooks.
> Has it been brought to the attention of Samsung with a clear message
> that they should bring out an updated corrected BIOS immediately?
We have been in com
On Thu, Jan 17, 2013 at 08:02:18PM -, Val wrote:
> 'modprobe efivars' has no effect. Some googling reveals that in order to
> get it to work, one needs to boot in the UEFI mode; this modprobe
> command will not work while in the BIOS/CMS mode. I am stuck... I can't
> load UEFI because it's not
On Tue, Jan 15, 2013 at 03:11:37AM -, Val wrote:
> lsmod in Grub command line produces a long list of modules loaded;
> linuxefi is one of them. There is no 'grep' or 'more' or 'less' in Grub
> command line and obviously I can't scroll up to see the full list. I
> wish there were some kind of a
On Mon, Jan 14, 2013 at 02:58:44PM -, Val wrote:
> Steve, what does this all mean? If 'samsung-laptop' module is not loaded
> by Live CD 12.10 x86_64, then presumably I don't need to install the
> patched kernel with Colin King's modifications, right?
Colin King's change will have no effect fo
> It seems like i am having a similar issue with a Lenovo IdeaPad n585
> laptop...
That is entirely unrelated. Please don't use this bug report for
discussing issues with non-Samsung UEFI hardware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
On Mon, Jan 07, 2013 at 10:20:47AM -, Luis Henriques wrote:
> This bug is awaiting verification that the kernel for Precise in
> -proposed solves the problem (3.2.0-36.56). Please test the kernel and
> update this bug with the results. If the problem is solved, change the
> tag 'verification-ne
On Sun, Dec 23, 2012 at 11:13:55AM -, montini wrote:
> what are the actual benefits of booting UEFI way? Is it faster booting
> or what? Maybe the instant-on feature I now expirience on Win8?
Well, UEFI should boot faster than BIOS, yes. It is also, as you say, the
only way to boot the Window
On Sat, Dec 22, 2012 at 10:52:53AM -, montini wrote:
> Is there any information if it is safe to start 12.10 live USB flash in
> mode "UEFI and CMS" (mixed bootloader) on NP530U3C-A05EE? Or only the
> plain CMS is safe at the moment?
Only plain CMS is safe. Mixed bootloader options are speci
On Thu, Dec 20, 2012 at 11:40:36AM -, Colin King wrote:
> I've got a small fix that will disable samsung-laptop in EFI mode, and
> there are some 64 bit kernels available for testing here:
> http://kernel.ubuntu.com/~cking/samsung-1040557
> @Steve, are we able to get hold of Samsung to test t
On Wed, Nov 28, 2012 at 12:30:05AM -, Tristen wrote:
> Hey, not good news for some of you, but at least I finally found others,
> this is pretty much exactly what happened after I upgraded from 12.04.
> The difference is I have a Toshiba Satellite L505D-S5965.
This does not at all describe the
35 matches
Mail list logo
