No functional boot menu in 16.1, 16.2 x64 for a Fujitsu U772

Älas · posted: 2017-03-16 13:18

I have installed a laptop with 16_x64-full and Everything works.
Before I have tried 16.1_x64-full, 16.1_x64-net, 16.2_x64-net (and 17_x64-net).
I couldn't get a functional boot menu. You can see a Picture in my Other post:
how-to-go-from-16-2-net-to-full-install-t6897.html

I couldn't even get 16.1_x64-full started, but net versions got started after a while and was then fuctional in console mode.

Is there any interest in debugging?
If so, what is needed?

rokytnji · posted: 2017-03-16 16:36

If you are talking about a scrambled screen. Because I can't really tell from here.

Post what graphics chip you are using. Forget it. I found it.

Code: Select all

inxi -Fxz
System: Host: * Kernel: 4.4.10-antix.1-amd64-smp x86_64 (64 bit gcc: 4.9.2) Desktop: IceWM 1.3.8
Distro: antiX-16.2_x64-net Berta Cáceres 10 February 2017
Machine: Device: laptop System: FUJITSU product: LIFEBOOK U772 v: 10601581354
Mobo: FUJITSU model: FJNB247 v: B3 UEFI [Legacy]: FUJITSU // Phoenix v: Version 1.08 date: 12/14/2012
Battery CMB1: charge: 31.5 Wh 100.0% condition: 31.5/31.5 Wh (100%) model: Fujitsu CP579040-01 status: Full
CPU: Dual core Intel Core i5-3317U (-HT-MCP-) cache: 3072 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 6784
clock speeds: max: 2600 MHz 1: 815 MHz 2: 2413 MHz 3: 857 MHz 4: 2479 MHz
Graphics: Card: Intel 3rd Gen Core processor Graphics Controller bus-ID: 00:02.0
Display Server: X.Org 1.16.4 drivers: intel (unloaded: modesetting,fbdev,vesa)
Resolution: 1366x768@60.00hz
GLX Renderer: Mesa DRI Intel Ivybridge Mobile GLX Version: 3.0 Mesa 10.3.2 Direct Rendering: Yes
Audio: Card Intel 7 Series/C210 Series Family High Definition Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0
Sound: Advanced Linux Sound Architecture v: k4.4.10-antix.1-amd64-smp
Network: Card-1: Intel 82579LM Gigabit Network Connection driver: e1000e v: 3.2.6-k port: 3080 bus-ID: 00:19.0
IF: eth0 state: down mac: <filter>
Card-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi bus-ID: 02:00.0
IF: wlan0 state: down mac: <filter>
Drives: HDD Total Size: 532.1GB (0.7% used)
ID-1: /dev/sda model: WDC_WD5000LPVT size: 500.1GB
ID-2: /dev/sdb model: SanDisk_SSD_i100 size: 32.0GB
Partition: ID-1: / size: 9.8G used: 3.5G (38%) fs: ext3 dev: /dev/sda3
Sensors: System Temperatures: cpu: 55.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 174 Uptime: 2:03 Memory: 151.0/7831.2MB Init: SysVinit runlevel: 5 Gcc sys: 4.9.2
Client: Shell (bash 4.3.301) inxi: 2.3.8

Intel graphics chip is nothing exotic and is fully supported in AntiX. So your problem is either a bad md5sum, a bad read error from install medium, or even a Fujitsu setting that I have no clue about. I know Fujitsu laptops are weird because of online correspondence with friends who are deceased now who informed me of Fujitsu security locks on their corporate line of laptops.

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://www.google.com/search?q=Fujitsu+laptop+corp+security+settings&ie=utf-8&oe=utf-8"
linktext was:"Link"
====================================

Don't concentrate on the last thing I said because md5sum or bad read are more likely. I am just poking and hoping here.

You say grub menu screen is what is scrambled. Which is weird. My grub screen was clear to read and screen did not scramble till after the desktop loaded up when I tested and helped with the debugg on AntiX 15. Hence why I say install medium <usb/cd/dvd> is corrupted or the drive lens is dirty or bad.

Shay · posted: 2017-03-16 17:21

I use gparted and on UEFI rigs, I make a 100MB fat 32 partition. Now the rest can be ext4 or what ever you want to do with it.
Grub will install in the Fat32 and things will work right. Just my experience

skidoo · posted: 2017-03-16 18:46

Earlier (other topic?) I wondered whether you might be up against a legacy/uefi issue, but if that were the case, you would probably wind up with a simple white-on-black error message or an entirely black screen, eh?

Switching to an O/S release containing an earlier (or current, but differently-built) linux kernel might avoid the problem.

Älas · posted: 2017-03-16 22:00

Yes it's a scrambled screen. It's the boot meny, not grub. I don't think any of my media has a problem. I have used them on other computers. All are made with latest Rufus. If I started with a net version and hit enter it would go to text mode after a while, so would it do that if it was bad?
I could burn a cd if you think that would help. (The laptop has GPT and UEFI, so I'm not using grub2 in MBR. I'm using Win 10 as the primary OS, antix second and AndEX Nougat last.)

rokytnji · posted: 2017-03-17 01:15

Did you md5sum check your iso download 1st before using rufus?

I ask because as a release tester. I md5sum and checksum all my iso downloads to keep my problems to a minimum.
Because as a team dubugger. I wish to report my problems as legit and not have a corrupted file interfere with my problem reports.

I have used them on other computers.

Which may have different hardware. Hence why checking iso file integrity is so important.

Älas · posted: 2017-03-17 14:37

Well no, but I did checksum them now in PowerShell. (All files was left in downloads.)
One exampel:
$(CertUtil -hashfile antiX-16.1_x64-full.iso MD5)[1] -replace"",""
f4fed27008d7ff792650d7a201e8ac6b
cat .\antiX-16.1_x64-full.iso.md5
f4fed27008d7ff792650d7a201e8ac6b antiX-16.1_x64-full.iso

Only one I can't compare is for 16.2 since I can't find antiX-16.2_x64-net.iso.md5 in:

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://sourceforge.net/projects/antix-linux/files/Testing/antiX-17/"
linktext was:"https://sourceforge.net/projects/antix- ... /antiX-17/"
====================================

This is what I have on my downloaded file:
$(CertUtil -hashfile antiX-16.2_x64-net.iso MD5)[1] -replace"",""
d70a7e00e8d13e521544c356d9e7527e

Shay · posted: 2017-03-17 16:40

I have a Dell Latitude D630 that does not like the dash 1 either.
Nor a bunch of other BETA stuff I have tried. But Antix 16_x64-full works just fine.

Älas · posted: 2017-03-17 16:50

Just to clarify. I have installed my U772 with 16_x64-full and then updated it (as I implied in the first post). I'm fine with that.
It's the splash screen with the menu that is scrambled when I try to boot something newer.
Now I tested 16.1_x64-full again. If I hit enter 3 times, at the scrambled screen, it actually works too.
I got 16.1 up and running, but just didn't install.

I looked in bios for strange things, but I the only thing I can think of is that TPM is activated.

(If there is no time or interest in debugging, then I'm fine if this topic gets closed.)

Älas · posted: 2017-03-17 16:59

My Dell Latitude D630 works fine 16.1_x64-full Shay.
What is your problem?
Maybe I can help?

Shay · posted: 2017-03-17 22:51

I am not worried about it. Fact is, I even bought a replacement. which will run antiX-17.a2_386-net.iso. just fine.